From 204eab1d6a2a329e7fcb6b0dc8e381db5ef973ca Mon Sep 17 00:00:00 2001 From: khronokernel <48863253+khronokernel@users.noreply.github.com> Date: Tue, 16 Mar 2021 19:44:20 +0000 Subject: [PATCH] =?UTF-8?q?Deploying=20to=20gh-pages=20from=20=20@=203fd08?= =?UTF-8?q?803d63a373f1dbd33e4ee69eab2cff7c2a0=20=F0=9F=9A=80?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- 404.html | 4 ++-- BOOT.html | 6 +++--- BUILD.html | 6 +++--- DEBUG.html | 6 +++--- ICNS.html | 6 +++--- INSTALLER.html | 6 +++--- MODELS.html | 6 +++--- PATCH-EXPLAIN.html => PATCHEXPLAIN.html | 8 ++++---- POST-INSTALL.html | 6 +++--- START.html | 6 +++--- TERMS.html | 8 ++++---- TROUBLESHOOTING.html | 6 +++--- UNINSTALL.html | 6 +++--- assets/js/{16.76db4cab.js => 16.d5ec2ab1.js} | 0 assets/js/{app.c473618a.js => app.c84d36e0.js} | 6 +++--- index.html | 6 +++--- 16 files changed, 46 insertions(+), 46 deletions(-) rename PATCH-EXPLAIN.html => PATCHEXPLAIN.html (87%) rename assets/js/{16.76db4cab.js => 16.d5ec2ab1.js} (100%) rename assets/js/{app.c473618a.js => app.c84d36e0.js} (92%) diff --git a/404.html b/404.html index aa7e59b6a..d7dd68206 100644 --- a/404.html +++ b/404.html @@ -11,13 +11,13 @@ - +

404

Looks like we've got some broken links.
Take me home.
- + diff --git a/BOOT.html b/BOOT.html index d6dfab574..0c59788a0 100644 --- a/BOOT.html +++ b/BOOT.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# Booting OpenCore and macOS

Now we finally get to boot OpenCore!

Reboot machine while holding Option to select the EFI Boot entry with the OpenCore icon:

Now that you've loaded OpenCore, now select Install macOS!:

After plenty of verbose booting, you will reach the installer screen! From there it's just like any normal macOS install. For an example of how the boot process looks, see the following video:

# Once installed and booting, head to Post-Installation

+ (opens new window)

# Booting OpenCore and macOS

Now we finally get to boot OpenCore!

Reboot machine while holding Option to select the EFI Boot entry with the OpenCore icon:

  • This will be the Mac Boot Picker

Now that you've loaded OpenCore, now select Install macOS!:

  • This will be the OpenCore Picker

After plenty of verbose booting, you will reach the installer screen! From there it's just like any normal macOS install. For an example of how the boot process looks, see the following video:

# Once installed and booting, head to Post-Installation

⟵ ⟶

- + diff --git a/BUILD.html b/BUILD.html index 99a655440..ecdadb617 100644 --- a/BUILD.html +++ b/BUILD.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# Building and installing OpenCore

Now that we have a macOS installer, lets now build our OpenCore configuration!

First Download the latest release:

Next, run the OpenCore-Patcher.app:

From here you have a couple important options:

  • Build OpenCore
  • Install OpenCore to USB/internal drive
  • Change Model
  • Patcher Settings

If you're patching for a different machine than you're running, please select "Change Model" and enter the updated SMBIOS. For more advanced users, you may also tweak the patcher's build settings via "Patcher Settings"

Now lets enter "Build OpenCore":

The process should be quite quick to build, once finished you'll be plopped back to the main menu.

Next lets run Install OpenCore to USB/internal drive:

Select Drive Select EFI/FAT32 Partition
  • If you have issues, please ensure you install OpenCore onto a FAT32 partition to ensure your Mac is able to boot it. You will need to format your drive as GUID/GPT in Disk Utility

# Once finished, head to Booting OpenCore and macOS

+ (opens new window)

# Building and installing OpenCore

Now that we have a macOS installer, lets now build our OpenCore configuration!

First Download the latest release:

Next, run the OpenCore-Patcher.app:

From here you have a couple important options:

  • Build OpenCore
  • Install OpenCore to USB/internal drive
  • Change Model
  • Patcher Settings

If you're patching for a different machine than you're running, please select "Change Model" and enter the updated SMBIOS. For more advanced users, you may also tweak the patcher's build settings via "Patcher Settings"

Now lets enter "Build OpenCore":

The process should be quite quick to build, once finished you'll be plopped back to the main menu.

Next lets run Install OpenCore to USB/internal drive:

Select Drive Select EFI/FAT32 Partition
  • If you have issues, please ensure you install OpenCore onto a FAT32 partition to ensure your Mac is able to boot it. You will need to format your drive as GUID/GPT in Disk Utility

# Once finished, head to Booting OpenCore and macOS

⟵ ⟶

- + diff --git a/DEBUG.html b/DEBUG.html index dedce02da..496a9bb44 100644 --- a/DEBUG.html +++ b/DEBUG.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# How to debug with OpenCore

For those who've hit an odd bug and unsure if it's user error or patcher, the below will tell you how to get more verbose debug information as well as logs to help file issues with us (opens new window)

# Debugging yourself

The easiest way to debug yourself is via Patcher Settings. Here there are many different settings however the 3 main options that will help are:

  • "Enable Verbose Mode"
  • "Enable OpenCore DEBUG"
  • "Enable Kext DEBUG"

When you've enabled these 3 options, rebuild OpenCore and install to your drive. This will provide much greater debug information as well as write logs to the EFI Partition.

# Obtaining OpenCore logs from disk

With "Enable OpenCore DEBUG" set, every boot there will be a .txt file generated in your disk. To grab these logs, download and run MountEFI (opens new window):

Once you've mounted the EFI Partition of the drive you have macOS on, you should see some nice logs:

# Obtaining Kernel logs from macOS

With "Enable Kext DEBUG" set, every boot will now have much more detailed logs stored in the OS. To get these logs, simply run the below command:

sudo dmesg > ~/Desktop/DMESG.txt
+     (opens new window)    
 
# How to debug with OpenCore
 
For those who've hit an odd bug and unsure if it's user error or patcher, the below will tell you how to get more verbose debug information as well as logs to help file issues with us (opens new window)
  
# Debugging yourself
 
The easiest way to debug yourself is via Patcher Settings. Here there are many different settings however the 3 main options that will help are:
 
  • "Enable Verbose Mode"
    •  
  • "Enable OpenCore DEBUG"
    •  
  • "Enable Kext DEBUG"
 
When you've enabled these 3 options, rebuild OpenCore and install to your drive. This will provide much greater debug information as well as write logs to the EFI Partition.
 
# Obtaining OpenCore logs from disk
 
With "Enable OpenCore DEBUG" set, every boot there will be a .txt file generated in your disk. To grab these logs, download and run MountEFI (opens new window):
 
 
Once you've mounted the EFI Partition of the drive you have macOS on, you should see some nice logs:
 
 
# Obtaining Kernel logs from macOS
 
With "Enable Kext DEBUG" set, every boot will now have much more detailed logs stored in the OS. To get these logs, simply run the below command:
 
sudo dmesg > ~/Desktop/DMESG.txt
 
From there, you'll have a log on your desktop.
 
# Filing an issue with us
 
Now that you have proper logs, you can now file issues with us (opens new window). Reminder we want the following info:
 
  • Model patching for (ie. MacBookPro10,1)
    •  
  • Target OS (ie. macOS 11.2.3)
    •  
  • Host OS (ie. macOS 10.15.7)
    •  
  • Upload of your OpenCore Build Folder
    •  
  • Upload of your OpenCore log (if applicable)
    •  
  • Upload of your Kernel log (if applicable)
 
Additionally, please search whether the issue has been reported before. This avoids having duplicate issues.
  

       ⟵
       
       ⟶
- + diff --git a/ICNS.html b/ICNS.html index 63f005ed7..b5e384c16 100644 --- a/ICNS.html +++ b/ICNS.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# Creating custom icons for OpenCore and Mac Boot Picker

For users who want to customize your setup to be more personal, OpenCore does allow for custom icons and images in the boot picker.

# Custom OpenCore icons

To generate custom OpenCore icons, you'll need the following:

  • Images in PNG format
  • Each image, with the following res: + (opens new window)

    # Creating custom icons for OpenCore and Mac Boot Picker

    For users who want to customize your setup to be more personal, OpenCore does allow for custom icons and images in the boot picker.

    # Custom OpenCore icons

    To generate custom OpenCore icons, you'll need the following:

    • Images in PNG format
    • Each image, with the following res:
      • Cursor — Mouse cursor (mandatory, up to 144x144).
      • Selected — Selected item (mandatory, 144x144).
      • Selector — Selecting item (mandatory, up to 144x40).
      • Left — Scrolling left (mandatory, 40x40).
      • Right — Scrolling right (mandatory, 40x40).
      • HardDrive — Generic OS (mandatory, 128x128).
      • Background — Centred background image. (Recommended max size 1920x1080)
      • Apple — Apple OS (128x128).
      • AppleRecv — Apple Recovery OS (128x128).
      • AppleTM — Apple Time Machine (128x128).
      • Windows — Windows (128x128).
      • Other — Custom entry (see Entries (opens new window), 128x128).
      • ResetNVRAM — Reset NVRAM system action or tool (128x128).
      • Shell — Entry with UEFI Shell name for e.g. OpenShell (128x128).
      • Tool — Any other tool (128x128).

    Note, for each image we recommend having one of double the size. This ensures that icons are scaled correctly since .icns support dedicated images depending on HiDPI or not.

    Once you have a custom image you want to use(for example, as a background), download the latest release of OpenCorePkg (opens new window) and enter the Utilities/icnspack/ folder:

    Now cd this folder in terminal and run the following:

    ./icnspack Background.icns <insert_x1_image> <insert_x2_image>

    Once done, you'll see your custom icon generated in icnspack's folder:

    # Custom Mac Boot Picker icons

    Custom boot picker icons is much more complicated on Legacy Macs, on late 2013+ Macs the Custom OpenCore icons method will work just fine. However on many 2012 and older Macs, the icons generated will be incompatible with the firmware.

    To generate legacy icons, you'll need the following:

    • A machine running macOS 10.4 through 10.11
    • Icon Composer.app (Requires Apple Developer Account for official download)
      • Users without the developer account can find a mirrors here: @@ -32,6 +32,6 @@ ⟶

- + diff --git a/INSTALLER.html b/INSTALLER.html index e6e5620d1..412ca47f7 100644 --- a/INSTALLER.html +++ b/INSTALLER.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# Download and build macOS Installers

This doc is centered around downloading and writing the macOS installer to a USB. If you're already familiar with how to do this, you can skip.

  • Note: 16GB+ USB will be required for the installer

# Downloading

The simplest way to download macOS installs would be to use installinstallmacos:

mkdir ~/macOS-installer && cd ~/macOS-installer && curl -O https://raw.githubusercontent.com/munki/macadmin-scripts/main/installinstallmacos.py && sudo python installinstallmacos.py
+     (opens new window)    
 
# Download and build macOS Installers
  
This doc is centered around downloading and writing the macOS installer to a USB. If you're already familiar with how to do this, you can skip.
 
  • Note: 16GB+ USB will be required for the installer
 
# Downloading
 
The simplest way to download macOS installs would be to use installinstallmacos:
 
mkdir ~/macOS-installer && cd ~/macOS-installer && curl -O https://raw.githubusercontent.com/munki/macadmin-scripts/main/installinstallmacos.py && sudo python installinstallmacos.py
 
 
As you can see, we get a nice list of macOS installers. If you need a particular versions of macOS, you can select it by typing the number next to it. For this example we'll choose 10:
 
 
This is going to take a while as we're downloading the entire 12GB+ macOS installer.
 
Once finished, you'll find in your ~/macOS-Installer/ folder a DMG containing the macOS Installer, called Install_macOS_11.1-20C69.dmg for example. Mount it and you'll find the installer application.
 
  • Note: We recommend to move the Install macOS.app into the /Applications folder, as we'll be executing commands from there.
    •  
  • Note 2: Running Cmd+Shift+G in Finder will allow you to easily jump to ~/macOS-installer
 
 
 
# Building
 
Now we'll be formatting the USB to prep for both the macOS installer and OpenCore. We'll want to use macOS Extended (HFS+) with a GUID partition map(Using GUID is important for the patcher). This will create two partitions: the main MyVolume and a second called EFI which is used as a boot partition where your Mac's firmware will check for boot files.
 
  • Note: By default, Disk Utility only shows partitions – press Cmd/Win+2 to show all devices (alternatively you can press the View button)
 
Formatting the USB
 
Next run the createinstallmedia command provided by Apple (opens new window). Note that the command is made for USB's formatted with the name MyVolume:
 
sudo /Applications/Install\ macOS\ Big\ Sur.app/Contents/Resources/createinstallmedia --volume /Volumes/MyVolume
 
  • Note: You can also replace the createinstallmedia path with that of where your installer's located (same idea with the drive name).
 
 
# Once finished, head to Building and installing OpenCore
  

       ⟵
@@ -30,6 +30,6 @@
       
       ⟶
- + diff --git a/MODELS.html b/MODELS.html index 74bafcbf6..ec0153120 100644 --- a/MODELS.html +++ b/MODELS.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# Supported Models

Any hardware supporting SSE4.1 CPU and 64-Bit firmware work on this patcher. To check your hardware model, run the below command on the applicable machine:

system_profiler SPHardwareDataType | grep 'Model Identifier'
+     (opens new window)    
 
# Supported Models
 
Any hardware supporting SSE4.1 CPU and 64-Bit firmware work on this patcher. To check your hardware model, run the below command on the applicable machine:
 
system_profiler SPHardwareDataType | grep 'Model Identifier'
 
The below table will list all supported and unsupported functions of the patcher currently:
  
Note: In this patcher, Brightness Control is tied to GPU acceleration
 
# MacBook
 
SMBIOS Year Supported Comment
 
MacBook1,1 Mid-2006  NO  32-Bit CPU limitation
 
MacBook2,1 Late 2006 32-Bit Firmware limitation
 
MacBook3,1 Late 2007
 
MacBook4,1 Early 2008
 
MacBook5,1 Late 2008  YES  - No GPU Acceleration in Big Sur
- No AppleHDA(Audio) Patching implemented(#76 (opens new window))
 
MacBook5,2 Early 2009
 
MacBook6,1 Late 2009 - No GPU Acceleration in Big Sur
- No AppleHDA(Audio) Patching implemented(#76 (opens new window))
 
MacBook7,1 Mid-2010
 
# MacBook Air
 
SMBIOS Year Supported Comment
 
MacBookAir1,1 Early 2008  NO  Requires SSE4.1 CPU
 
MacBookAir2,1 Late 2008  YES  - No GPU Acceleration in Big Sur
- No AppleHDA(Audio) Patching implemented(#76 (opens new window))
- No Wifi Patches implemented(#102 (opens new window))
 
MacBookAir3,1 Late 2010 - No GPU Acceleration in Big Sur
- No AppleHDA(Audio) Patching implemented(#76 (opens new window))
 
MacBookAir3,2
 
MacBookAir4,1 Mid-2011
 
MacBookAir4,2
 
MacBookAir5,1 Mid-2012  Everything is supported
 
MacBookAir5,2
 
# MacBook Pro
 
SMBIOS Year Supported Comment
 
MacBookPro1,1 Early 2006  NO  32-Bit CPU limitation
 
MacBookPro1,2
 
MacBookPro2,1 Late 2006 32-Bit Firmware limitation
 
MacBookPro2,2 Late 2006
 
MacBookPro3,1 Mid-2007 - Requires SSE4.1 CPU
 
MacBookPro4,1 Early 2008  YES  - No GPU Acceleration in Big Sur
- No AppleHDA(Audio) Patching implemented(#76 (opens new window))
- No Wifi Patches implemented(#102 (opens new window))
 
MacBookPro5,1 Late 2008 - No GPU Acceleration in Big Sur
- No AppleHDA(Audio) Patching implemented(#76 (opens new window))
 
MacBookPro5,2 Early 2009
 
MacBookPro5,3 Mid-2009
 
MacBookPro5,4
 
MacBookPro5,5
 
MacBookPro6,1 Mid-2010
 
MacBookPro6,2
 
MacBookPro7,1 - No GPU Acceleration in Big Sur
- No AppleHDA(Audio) Patching implemented(#76 (opens new window))
- Ethernet Connection Issues(#45 (opens new window))
 
MacBookPro8,1 Early 2011
 
MacBookPro8,2
 
MacBookPro8,3
 
MacBookPro9,1 Mid-2012  Everything is supported
 
MacBookPro9,2
 
MacBookPro10,1 Mid-2012, Early 2013
 
MacBookPro10,2 Late 2012, Early 2013
 
# Mac mini
 
SMBIOS Year Supported Comment
 
Macmini1,1 Early 2006  NO  32-Bit CPU limitation
 
Macmini2,1 Mid-2007 32-Bit Firmware limitation
 
Macmini3,1 Early 2009  YES  - No GPU Acceleration in Big Sur
- No AppleHDA(Audio) Patching implemented(#76 (opens new window))
 
Macmini4,1 Mid-2010
 
Macmini5,1 Mid-2011 - No GPU Acceleration in Big Sur
- No AppleHDA(Audio) Patching implemented(#76 (opens new window))
- Ethernet Connection Issues(#45 (opens new window))
 
Macmini5,2
 
Macmini5,3
 
Macmini6,1 Late 2012  Everything is supported
 
Macmini6,2
 
# iMac
 
SMBIOS Year Supported Comment
 
iMac4,1 Early 2006  NO  32-Bit CPU limitation
 
iMac4,2 Mid-2006
 
iMac5,1 Late 2006 32-Bit Firmware limitation
 
iMac5,2
 
iMac6,1
 
iMac7,1 Mid-2007  YES  - Requires an SSE4.1 CPU Upgrade
- No GPU Acceleration in Big Sur
- No AppleHDA(Audio) Patching implemented(#76 (opens new window))
 
iMac8,1 Early 2008 - No GPU Acceleration in Big Sur
- No AppleHDA(Audio) Patching implemented(#76 (opens new window))
- No Wifi Patches implemented(#102 (opens new window))
 
iMac9,1 Early 2009 - No GPU Acceleration in Big Sur
- No AppleHDA(Audio) Patching implemented(#76 (opens new window))
 
iMac10,1 Late 2009
 
iMac11,1 - No GPU Acceleration in Big Sur
- No AppleHDA(Audio) Patching implemented(#76 (opens new window))
- Ethernet Connection Issues(#45 (opens new window))
 
iMac11,2 Mid-2010
 
iMac11,3
 
iMac12,1 Mid-2011
 
iMac12,2
 
iMac13,1 Late 2012  Everything is supported
 
iMac13,2
 
iMac14,1 Late 2013
 
iMac14,2
 
iMac14,3
 
# Mac Pro
 
SMBIOS Year Supported Comment
 
MacPro1,1 Mid-2006  NO  32-Bit Firmware limitation
 
MacPro2,1 Mid-2007
 
MacPro3,1 Early 2008  YES  - Requires an SSE4.1 CPU Upgrade
- No AppleHDA(Audio) Patching implemented(#76 (opens new window))
 
MacPro4,1 Early 2009  Everything is supported as long as GPU is Metal capable 
 
MacPro5,1 Mid-2010, Mid-2012
 
# Xserve
 
SMBIOS Year Supported Comment
 
Xserve1,1 Mid-2006  NO  32-Bit Firmware limitation
 
Xserve2,1 Early 2008
 
Xserve3,1 Early 2009  YES   Everything is supported as long as GPU is Metal capable 
 
# Once you've verified your hardware is supported, head to Download and build macOS Installers
  

       ⟵
       
       ⟶
- + diff --git a/PATCH-EXPLAIN.html b/PATCHEXPLAIN.html similarity index 87% rename from PATCH-EXPLAIN.html rename to PATCHEXPLAIN.html index c2bb2ce59..1d92a3f97 100644 --- a/PATCH-EXPLAIN.html +++ b/PATCHEXPLAIN.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# Explaining the patches in OpenCore Legacy Patcher

In our patcher, there are numerous patches used to ensure a stable system. Here we're going to go over what patches are used and why we recommend or even require them.

# OpenCore Settings

# ACPI -> Patch

  • EHCx and XHC1 Patches + (opens new window)

    # Explaining the patches in OpenCore Legacy Patcher

    In our patcher, there are numerous patches used to ensure a stable system. Here we're going to go over what patches are used and why we recommend or even require them.

    # OpenCore Settings

    # ACPI -> Patch

    • EHCx and XHC1 Patches
      • Reason: Required for proper USB operation
      • Logic: Avoids USB maps of newer models attaching and breaking USB port functionality
      • Models: All models require

    # Booter -> Quirks

    • ForceBooterSignature
      • Reason: Required to ensure Hibernation support
      • Logic: Tricks boot.efi into thinking OpenCore is Apple's firmware
      • Models: All models require

    # DeviceProperties -> Add

    • PciRoot(0x0)/Pci(0x15,0x0)/Pci(0x0,0x0)
    • PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)
    • PciRoot(0x0)/Pci(0x1C,0x3)/Pci(0x0,0x0)
    • PciRoot(0x0)/Pci(0x1C,0x5)/Pci(0x0,0x0)
    • PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x0)
    • PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)
    • PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)
      • Reason: Required to ensure Brightness Control works on upgraded iMacs
      • Logic: Sets AppleBackLight properties
      • Models: iMac11,x and iMac12,x with upgraded Nvidia Metal GPUs
    • PciRoot(0x0)/Pci(0x2,0x0)
      • Reason: Disables internal GPU to fix sleep issues on upgrades iMacs
      • Logic: Tricks macOS into thinking iGPU is a generic PCI device
      • Models: iMac12,x with upgraded Metal GPUs

    # Kernel -> Patch

    • SMC Patch
      • Reason: Required to avoid SMC Firmware updates
      • Logic: Patches out smc-version in AppleSMC.kext, requires SMC-Spoof.kext for full functionality
      • Models: All models require
    • IOHIDFamily Patch @@ -43,11 +43,11 @@
      • Reason: Fix IDE support on MacPro3,1
      • Models: MacPro3,1
    • AppleIntelMCEDisabler
      • Reason: Fix dual socket support in Catalina and newer
      • Models: Mac Pros and Xserves
    • NightShiftEnabler
      • Reason: Enables NightShift support on unsupported models
      • Models: 2011 and older, MacBookPro9,x included
    • SMC-Spoof -
      • Reason: Spoofs SMC version to 9.9999
      • Models: All models require

    +

    • Reason: Spoofs SMC version to 9.9999
    • Models: All models require

⟵

- + diff --git a/POST-INSTALL.html b/POST-INSTALL.html index e2d45a13f..555ec26d1 100644 --- a/POST-INSTALL.html +++ b/POST-INSTALL.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# Post-Installation

# Booting without USB drive

Once you've installed macOS through OpenCore, you can boot up and go through the regular install process. To boot without the USB drive plugged in is quite simple:

  • Download OpenCore Legacy Patcher
  • Change Patcher settings as you'd like
  • Build OpenCore again
  • Install OpenCore to internal drive
  • Reboot holding Option, and select the internal EFI

And voila! No more USB drive required

# Booting seamlessly without Verbose or OpenCore Picker

To do this, run the OpenCore Patcher and head to Patcher Settings:

Here you can change different patcher settings, however the main 2 of interest are:

  • Enable Verbose Mode
  • Set ShowPicker Mode

Once you've toggled them both off, build your OpenCore EFI once again and install to your desired drive. Now to show OpenCore picker, you can simply hold the "Esc" key.

+ (opens new window)

# Post-Installation

# Booting without USB drive

Once you've installed macOS through OpenCore, you can boot up and go through the regular install process. To boot without the USB drive plugged in is quite simple:

  • Download OpenCore Legacy Patcher
  • Change Patcher settings as you'd like
  • Build OpenCore again
  • Install OpenCore to internal drive
  • Reboot holding Option, and select the internal EFI

And voila! No more USB drive required

# Booting seamlessly without Verbose or OpenCore Picker

To do this, run the OpenCore Patcher and head to Patcher Settings:

Here you can change different patcher settings, however the main 2 of interest are:

  • Enable Verbose Mode
  • Set ShowPicker Mode

Once you've toggled them both off, build your OpenCore EFI once again and install to your desired drive. Now to show OpenCore picker, you can simply hold the "Esc" key.

⟵ ⟶

- + diff --git a/START.html b/START.html index b4c18713b..0a0e635c7 100644 --- a/START.html +++ b/START.html @@ -11,7 +11,7 @@ - + @@ -19,11 +19,11 @@ GitHub (opens new window)

# What is OpenCore?

This is a sophisticated boot loader used to inject and patch data in memory, instead of on disk. This means we're able to get near-native experience on many unsupported Macs with Metal GPUs. This includes many of the long desired features of other patchers such as:

  • System Integrity Protection, FileVault 2, .im4m Secure Boot and Vaulting
  • Native OTA OS DELTA updates on all Macs
  • Recovery OS, Safe Mode and Single-user Mode booting

While many PC users from the Hackintosh community are familiar with OpenCore, OpenCore was designed as Mac and PC agnostic ensuring both platforms can use it easily. And with OpenCore Legacy Patcher, we help automate the process making running with OpenCore that much easier.

# How do I get started?

  1. The first step of ensuring whether your model is support is checking here:
  1. Download and build macOS Installer
  2. Run the OpenCore-Patcher.app
  3. Reboot and boot OpenCore

+ (opens new window)

# What is OpenCore?

This is a sophisticated boot loader used to inject and patch data in memory, instead of on disk. This means we're able to get near-native experience on many unsupported Macs with Metal GPUs. This includes many of the long desired features of other patchers such as:

  • System Integrity Protection, FileVault 2, .im4m Secure Boot and Vaulting
  • Native OTA OS DELTA updates on all Macs
  • Recovery OS, Safe Mode and Single-user Mode booting

While many PC users from the Hackintosh community are familiar with OpenCore, OpenCore was designed as Mac and PC agnostic ensuring both platforms can use it easily. And with OpenCore Legacy Patcher, we help automate the process making running with OpenCore that much easier.

# How do I get started?

  1. The first step of ensuring whether your model is support is checking here:
  1. Download and build macOS Installer
  2. Run the OpenCore-Patcher.app
  3. Reboot and boot OpenCore

Supported Models ⟶

- + diff --git a/TERMS.html b/TERMS.html index 8a1820900..c59ebc3b6 100644 --- a/TERMS.html +++ b/TERMS.html @@ -11,7 +11,7 @@ - + @@ -19,15 +19,15 @@ GitHub (opens new window)

# OpenCore Patcher Terminology

With OpenCore Legacy Patcher, we use a lot of different terms to refer to hardware including SSE4.1, 32-Bit Firmware, etc. This page is to help users understand what all these confusing words mean.

# Terminology

Term Description
macOS Apple's own UNIX based OS used for Mac machines and "What makes a Mac a Mac".
Windows Microsoft's proprietary OS that is used and supported on a wide range of devices (stay with this OS if you don't want headaches)
Linux Family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991, by Linus Torvalds. Linux is typically packaged in a Linux distribution. Note that while macOS and Linux may be UNIX-based, they're vastly different.
Bootloader Piece of software that loads an OS, usually made by the OS creators. OpenCore is technically not a bootloader per se (see boot manager explanation down below). Apple's Boot.efi would be the actual boot loader in a Mac.
Boot Manager Piece of software that manages bootloaders – we have many of these: Clover, systemd-boot, OpenCore, rEFInd, rEFIt... These are generally seen as prepping the system for the actual boot loader.
Term Description
OpenCore The new hotness on the scene, made with security in mind by the Acidanthera team (opens new window), has faster booting and lighter weight than previous boot managers. Supports many native Mac features such as SIP, FileVault, Secure Boot, etc
XNU Also known as X is Not Unix, XNU is referred to as macOS's "kernel" and the heart of what makes macOS tick
Kexts Also known as Kernel Extensions, are macOS's drivers. They're used to perform different tasks like device drivers or for a different purpose (in this patcher) like patching the OS, injecting information or running tasks.
KernelCollection Also known as the ImmutableKernel and PrelinkedKernel, this is a bundle of the kernel(XNU) and kernel extensions(Kexts) that we use to boot macOS. This is also what OpenCore patches in memory to allow us to have a seamless experience
- PrelinkedKernel: Default caching system since 10.7
- ImmutableKernel: Secure Boot based caching system since 10.13
- KernelCollection: Merge of both Prelinked and ImmutableKernel's since macOS 11, Big Sur
Term Description
EFI It can denote two things:
- Mac's firmware, which is the same as UEFI, but pretty modified for Macs only, so not so "Universal"
- The partition on your hard drive that stores software read by the UEFI to load OSes (like the Windows bootloader) or UEFI Applications (like OpenCore), it's FAT32 formatted and has an ID type of EF00 (in hex). It can be named ESP or SYSTEM, and it's usually from 100MB to 400MB in size but the size doesn't reflect upon anything.
32 and 64-Bit CPU The bit number of a CPU determines how much data a CPU can address.
- 32-Bit CPUs were only supported up-to Mac OS X 10.6, Snow Leopard.
32-Bit Firmware The bit number of a Firmware determines how much data the firmware can address. In some older Macs, it's common to have a 64-Bit CPU can have a 32-Bit firmware
- 32-Bit Firmwares were only supported up-to Mac OS X 10.7, Lion.
SSE Instructions Also known as SIMD Single-Precision Floating-Point Instructions, these are defined as instruction sets supported by your CPU. In macOS, there are a certain number of instruction sets required for normal operation:
- SSE3: Required for all Intel CPUs since Mac OS X 10.4, Tiger
- SSSE3: Required for all Intel 64-Bit CPUs since Mac OS X 10.6, Snow Leopard
- SSE4.1: Required for all Intel CPUs since macOS 10.12, Sierra

+ (opens new window)

# OpenCore Patcher Terminology

With OpenCore Legacy Patcher, we use a lot of different terms to refer to hardware including SSE4.1, 32-Bit Firmware, etc. This page is to help users understand what all these confusing words mean.

# Terminology

Term Description
macOS Apple's own UNIX based OS used for Mac machines and "What makes a Mac a Mac".
Windows Microsoft's proprietary OS that is used and supported on a wide range of devices (stay with this OS if you don't want headaches)
Linux Family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991, by Linus Torvalds. Linux is typically packaged in a Linux distribution. Note that while macOS and Linux may be UNIX-based, they're vastly different.
Bootloader Piece of software that loads an OS, usually made by the OS creators. OpenCore is technically not a bootloader per se (see boot manager explanation down below). Apple's Boot.efi would be the actual boot loader in a Mac.
Boot Manager Piece of software that manages bootloaders – we have many of these: Clover, systemd-boot, OpenCore, rEFInd, rEFIt... These are generally seen as prepping the system for the actual boot loader.
Term Description
OpenCore The new hotness on the scene, made with security in mind by the Acidanthera team (opens new window), has faster booting and lighter weight than previous boot managers. Supports many native Mac features such as SIP, FileVault, Secure Boot, etc
XNU Also known as X is Not Unix, XNU is referred to as macOS's "kernel" and the heart of what makes macOS tick
Kexts Also known as Kernel Extensions, are macOS's drivers. They're used to perform different tasks like device drivers or for a different purpose (in this patcher) like patching the OS, injecting information or running tasks.
KernelCollection Also known as the ImmutableKernel and PrelinkedKernel, this is a bundle of the kernel(XNU) and kernel extensions(Kexts) that we use to boot macOS. This is also what OpenCore patches in memory to allow us to have a seamless experience
- PrelinkedKernel: Default caching system since 10.7
- ImmutableKernel: Secure Boot based caching system since 10.13
- KernelCollection: Merge of both Prelinked and ImmutableKernel's since macOS 11, Big Sur
Term Description
EFI It can denote two things:
- Mac's firmware, which is the same as UEFI, but pretty modified for Macs only, so not so "Universal"
- The partition on your hard drive that stores software read by the UEFI to load OSes (like the Windows bootloader) or UEFI Applications (like OpenCore), it's FAT32 formatted and has an ID type of EF00 (in hex). It can be named ESP or SYSTEM, and it's usually from 100MB to 400MB in size but the size doesn't reflect upon anything.
32 and 64-Bit CPU The bit number of a CPU determines how much data a CPU can address.
- 32-Bit CPUs were only supported up-to Mac OS X 10.6, Snow Leopard.
32-Bit Firmware The bit number of a Firmware determines how much data the firmware can address. In some older Macs, it's common to have a 64-Bit CPU can have a 32-Bit firmware
- 32-Bit Firmwares were only supported up-to Mac OS X 10.7, Lion.
SSE Instructions Also known as SIMD Single-Precision Floating-Point Instructions, these are defined as instruction sets supported by your CPU. In macOS, there are a certain number of instruction sets required for normal operation:
- SSE3: Required for all Intel CPUs since Mac OS X 10.4, Tiger
- SSSE3: Required for all Intel 64-Bit CPUs since Mac OS X 10.6, Snow Leopard
- SSE4.1: Required for all Intel CPUs since macOS 10.12, Sierra

⟵ + Explaining the patches in OpenCore Legacy Patcher ⟶

- + diff --git a/TROUBLESHOOTING.html b/TROUBLESHOOTING.html index 32739880f..af199db9a 100644 --- a/TROUBLESHOOTING.html +++ b/TROUBLESHOOTING.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# Troubleshooting

Here are some common errors users may experience while using this patcher:

# Stuck on This version of Mac OS X is not supported on this platform

This means macOS has detected a SMBIOS it does not support, to resolve this ensure you're booting OpenCore before the macOS installer in the boot picker. Reminder the option will be called EFI Boot

Once you've booted OpenCore at least once, your hardware should now auto boot it until either NVRAM reset or you remove the drive with OpenCore installed.

# Cannot boot macOS without the USB

By default, the OpenCore Patcher won't install OpenCore onto the internal drive itself during installs. Instead, you'll need to either manually transfer (opens new window) OpenCore to the internal drive's EFI or run this patcher's Option 2 again but select your internal drive.

Reminder that once this is done, you'll need to select OpenCore in the boot picker again for your hardware to remember this entry and auto boot from then on.

# Infinite Recovery OS Booting

With OpenCore Legacy Patcher, we rely on Apple Secure Boot to ensure OS updates work correctly and reliably with Big Sur. However this installs NVRAM variables that will confuse your Mac if not running with OpenCore. To resolve, simply uninstall OpenCore and reset NVRAM (opens new window).

  • Note: Machines with modded root volumes will also result in infinite recovery until integrity is restored

# Reboot when entering Hibernation (Sleep Wake Failure)

Known issue on some models (opens new window), temporary fix is to disable Hibernation:

sudo pmset -a hibernatemode 0
+     (opens new window)    
 
# Troubleshooting
 
Here are some common errors users may experience while using this patcher:
  
# Stuck on This version of Mac OS X is not supported on this platform
 
This means macOS has detected a SMBIOS it does not support, to resolve this ensure you're booting OpenCore before the macOS installer in the boot picker. Reminder the option will be called EFI Boot
 
Once you've booted OpenCore at least once, your hardware should now auto boot it until either NVRAM reset or you remove the drive with OpenCore installed.
 
# Cannot boot macOS without the USB
 
By default, the OpenCore Patcher won't install OpenCore onto the internal drive itself during installs. Instead, you'll need to either manually transfer (opens new window) OpenCore to the internal drive's EFI or run this patcher's Option 2 again but select your internal drive.
 
Reminder that once this is done, you'll need to select OpenCore in the boot picker again for your hardware to remember this entry and auto boot from then on.
 
# Infinite Recovery OS Booting
 
With OpenCore Legacy Patcher, we rely on Apple Secure Boot to ensure OS updates work correctly and reliably with Big Sur. However this installs NVRAM variables that will confuse your Mac if not running with OpenCore. To resolve, simply uninstall OpenCore and reset NVRAM (opens new window).
 
  • Note: Machines with modded root volumes will also result in infinite recovery until integrity is restored
 
# Reboot when entering Hibernation (Sleep Wake Failure)
 
Known issue on some models (opens new window), temporary fix is to disable Hibernation:
 
sudo pmset -a hibernatemode 0
 
# Booting with a non-flashed GPU
 
For Mac Pro, Xserve and iMac users with non-flashed GPUs, you can still easily boot OpenCore and view the entire boot process. To do so, make sure SIP is disabled(to allow NVRAM write access) and run the following:
 
sudo bless --verbose --file /Volumes/VOLNAME/EFI/OC/OpenCore.efi --folder /Volumes/VOLNAME/EFI/OC --setBoot
 
  • Note you will need to replace VOLNAME with the Volume name of your USB or hard drive with OpenCore
    •  
  • Note 2: Once done, you can re-enable SIP
 
Once you boot OpenCore for the first time, LauncherOption will install itself as the top boot priority making OpenCore always launch. Combined with RequestBootVar, all boot options must go through OpenCore ensuring seamless usage even with OS installation and updates.
 
# How to Boot Big Sur Recovery
 
By default, the patcher will try to hide extra boot options such as recovery from the user. To make them appear, simply press the "Spacebar" inside OpenCore's Picker to list all boot options.
 
# Stuck on "Your Mac needs a firmware update"
 
Full error: "Your Mac needs a firmware update in order to install to this Volume. Please select a Mac OS Extended (Journaled) volume instead."
 
This error occurs when macOS determines the firmware to not have full APFS support. To resolve is quite simple, when building OpenCore head to "Patcher Settings" and enable "Moderate SMBIOS Patching" or higher. This will ensure that the firmware reported will show as supporting full APFS capabilities.
  

       ⟵
@@ -30,6 +30,6 @@
       
       ⟶
- + diff --git a/UNINSTALL.html b/UNINSTALL.html index 94d860080..2fe1537f9 100644 --- a/UNINSTALL.html +++ b/UNINSTALL.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@ GitHub (opens new window)

# Uninstalling OpenCore

To remove OpenCore is actually quite simply:

  1. Remove OpenCore either from the USB or internal drive
  1. Reset NVRAM

Know that if you are on Big Sur when you remove the EFI folder, your Mac will no longer boot and show the prohibited symbol. Be ready to install an older version of macOS before you uninstall OpenCore.

+ (opens new window)

# Uninstalling OpenCore

To remove OpenCore is actually quite simply:

  1. Remove OpenCore either from the USB or internal drive
  1. Reset NVRAM

Know that if you are on Big Sur when you remove the EFI folder, your Mac will no longer boot and show the prohibited symbol. Be ready to install an older version of macOS before you uninstall OpenCore.

⟵ ⟶

- + diff --git a/assets/js/16.76db4cab.js b/assets/js/16.d5ec2ab1.js similarity index 100% rename from assets/js/16.76db4cab.js rename to assets/js/16.d5ec2ab1.js diff --git a/assets/js/app.c473618a.js b/assets/js/app.c84d36e0.js similarity index 92% rename from assets/js/app.c473618a.js rename to assets/js/app.c84d36e0.js index 12687c119..968e2b5ce 100644 --- a/assets/js/app.c473618a.js +++ b/assets/js/app.c84d36e0.js @@ -1,9 +1,9 @@ -(window.webpackJsonp=window.webpackJsonp||[]).push([[0],[]]);!function(t){function e(e){for(var r,a,c=e[0],u=e[1],s=e[2],l=0,p=[];l0?o(r(t),9007199254740991):0}},function(t,e){var n=Array.isArray;t.exports=n},function(t,e,n){var r=n(33),o=n(19);t.exports=function(t){return r(o(t))}},function(t,e,n){var r=n(142),o="object"==typeof self&&self&&self.Object===Object&&self,i=r||o||Function("return this")();t.exports=i},function(t,e,n){var r=n(6),o=n(1),i=n(7),a=Object.defineProperty,c={},u=function(t){throw t};t.exports=function(t,e){if(i(c,t))return c[t];e||(e={});var n=[][t],s=!!i(e,"ACCESSORS")&&e.ACCESSORS,f=i(e,0)?e[0]:u,l=i(e,1)?e[1]:void 0;return c[t]=!!n&&!o((function(){if(s&&!r)return!0;var t={length:-1};s?a(t,1,{enumerable:!0,get:u}):t[1]=1,n.call(t,f,l)}))}},function(t,e,n){var r=n(114),o=n(2),i=function(t){return"function"==typeof t?t:void 0};t.exports=function(t,e){return arguments.length<2?i(r[t])||i(o[t]):r[t]&&r[t][e]||o[t]&&o[t][e]}},function(t,e){t.exports=function(t){if(null==t)throw TypeError("Can't call method on "+t);return t}},function(t,e){t.exports=!1},function(t,e,n){var r=n(6),o=n(80),i=n(35),a=n(15),c=n(34),u=n(7),s=n(109),f=Object.getOwnPropertyDescriptor;e.f=r?f:function(t,e){if(t=a(t),e=c(e,!0),s)try{return f(t,e)}catch(t){}if(u(t,e))return i(!o.f.call(t,e),t[e])}},function(t,e){var n={}.toString;t.exports=function(t){return n.call(t).slice(8,-1)}},function(t,e){t.exports=function(t){if("function"!=typeof t)throw TypeError(String(t)+" is not a function");return t}},function(t,e,n){var r=n(231),o=n(234);t.exports=function(t,e){var n=o(t,e);return r(n)?n:void 0}},function(t,e,n){"use strict";function r(t,e,n,r,o,i,a,c){var u,s="function"==typeof t?t.options:t;if(e&&(s.render=e,s.staticRenderFns=n,s._compiled=!0),r&&(s.functional=!0),i&&(s._scopeId="data-v-"+i),a?(u=function(t){(t=t||this.$vnode&&this.$vnode.ssrContext||this.parent&&this.parent.$vnode&&this.parent.$vnode.ssrContext)||"undefined"==typeof __VUE_SSR_CONTEXT__||(t=__VUE_SSR_CONTEXT__),o&&o.call(this,t),t&&t._registeredComponents&&t._registeredComponents.add(a)},s._ssrRegister=u):o&&(u=c?function(){o.call(this,(s.functional?this.parent:this).$root.$options.shadowRoot)}:o),u)if(s.functional){s._injectStyles=u;var f=s.render;s.render=function(t,e){return u.call(e),f(t,e)}}else{var l=s.beforeCreate;s.beforeCreate=l?[].concat(l,u):[u]}return{exports:t,options:s}}n.d(e,"a",(function(){return r}))},function(t,e,n){"use strict";var r=n(0),o=n(31).filter,i=n(54),a=n(17),c=i("filter"),u=a("filter");r({target:"Array",proto:!0,forced:!c||!u},{filter:function(t){return o(this,t,arguments.length>1?arguments[1]:void 0)}})},function(t,e){t.exports=function(t){return null!=t&&"object"==typeof t}},function(t,e,n){var r,o=n(5),i=n(189),a=n(78),c=n(36),u=n(113),s=n(75),f=n(49),l=f("IE_PROTO"),p=function(){},d=function(t){return" +