Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/lzhoang2801/OpCore-Simplify/llms.txt

Use this file to discover all available pages before exploring further.

Some hardware that worked perfectly in an older version of macOS is no longer supported by Apple in newer releases. OpenCore Legacy Patcher (OCLP) addresses this by applying low-level patches directly to the macOS root volume after installation, restoring drivers and frameworks that Apple removed. If OpCore Simplify flagged your system as needing OCLP during the build process, this page explains what that means, what risks are involved, and exactly how to apply the patches.

​
What Is OpenCore Legacy Patcher?

OpenCore Legacy Patcher is a post-installation tool that patches the macOS root volume to re-introduce hardware support that Apple dropped in newer macOS releases. Rather than modifying your EFI or kexts, it injects legacy drivers directly into the sealed system volume — a technique called root patching. After patching, macOS behaves as if the original drivers were present, restoring graphics acceleration, Wi-Fi, and other functionality.

​
When Is OCLP Required?

OpCore Simplify’s Compatibility Checker scans every device in your hardware report for a compatibility range. When a device is natively supported only up to a certain macOS version, the checker flags it with an OCLP compatibility range and marks that macOS version as Requires OpenCore Legacy Patcher in the version selection screen. Common hardware categories that trigger the OCLP requirement include:
  • Older AMD and NVIDIA discrete GPUs — Polaris, Vega, Kepler, Maxwell, Pascal, and Fermi architectures dropped from macOS Monterey, Ventura, Sequoia, or Tahoe
  • Broadcom Wi-Fi cards (e.g., BCM94360, BCM943602) — dropped from macOS Sonoma and newer
  • Intel integrated GPUs beyond Ice Lake — some iGPU families lose acceleration support in newer macOS versions
  • AppleHDA audio on macOS Tahoe 26 — requires OCLP to restore the legacy audio stack

​
OCLP Warning Dialog in OpCore Simplify

Before proceeding with a build that requires OCLP, OpCore Simplify displays the OpenCore Legacy Patcher Warning screen. This dialog presents three points that you must acknowledge:
  1. OpenCore Legacy Patcher is the only solution to re-enable dropped GPU and Broadcom Wi-Fi support in newer macOS versions, as well as to restore AppleHDA audio in macOS Tahoe 26.
  2. OpenCore Legacy Patcher disables macOS security features, specifically SIP (System Integrity Protection) and AMFI (Apple Mobile File Integrity). This can lead to consequences including: needing full macOS installers (rather than delta updates) for OS updates, application crashes in security-sensitive software, and general system instability.
  3. OpenCore Legacy Patcher is not officially supported for Hackintosh systems. The tool is maintained for real Mac hardware and its behaviour on Hackintosh configurations is not guaranteed.
You are asked to type yes to proceed or no to return to macOS version selection and choose a version that does not require OCLP.
Enabling OCLP permanently disables SIP and AMFI on your system volume. This means the root file system is no longer cryptographically verified by macOS. Security-sensitive applications (some VPNs, endpoint protection agents, and developer tools) may refuse to run or behave unexpectedly. Evaluate this trade-off before proceeding, particularly on machines used for work or handling sensitive data.

​
macOS Tahoe 26: Use the lzhoang2801 Fork

For systems targeting macOS Tahoe 26, you must use the fork of OpenCore Legacy Patcher maintained at lzhoang2801/OpenCore-Legacy-Patcher, version 3.0.0 or newer. The official Dortania releases of OCLP do not support macOS Tahoe 26. Using the official release on Tahoe will result in missing patches or a broken system.
OpCore Simplify’s build output and config.plist are pre-configured to work with OCLP 3.0.0+ from the lzhoang2801 repository. The NVRAM entries required for OCLP compatibility (including the bypass for the internal Bluetooth controller check) are added automatically to your config.plist by OpCore Simplify when OCLP is required — you do not need to add them manually.

​
Applying Root Patches

Root patches are applied after macOS is installed and running. You cannot apply them from the installer environment.
1

Boot into macOS with the generated EFI

Use the EFI built by OpCore Simplify to complete your macOS installation. Reach the macOS desktop (Setup Assistant or existing install). At this point, graphics acceleration and Wi-Fi may not be working — this is expected and will be resolved after patching.
2

Download OpenCore Legacy Patcher 3.0.0

Download the OCLP application from the lzhoang2801 fork:https://github.com/lzhoang2801/OpenCore-Legacy-Patcher/releases/tag/3.0.0Download the .dmg or the .app archive for macOS. If your internet connection is not working yet (because Wi-Fi needs OCLP to function), use a USB Ethernet adapter or tether from another device to download the file.
3

Open OCLP and navigate to Post-Install Root Patch

Open the OpenCore-Patcher application. From the main menu, click Post-Install Root Patch. OCLP will scan your system and present a list of patches it will apply based on detected hardware.Review the list to confirm the patches match your hardware (e.g., AMD Legacy GCN, Broadcom Wi-Fi, Intel Ivy Bridge iGPU, etc.).
4

Apply patches and reboot

Click Start Root Patching. OCLP will disable SIP/AMFI, patch the system volume, and prompt you to reboot. After rebooting, graphics acceleration, Wi-Fi, and any other patched hardware should be fully functional.
If OCLP reports that no patches are needed, verify that you downloaded version 3.0.0 from the lzhoang2801 repository, not the official Dortania release.

​
AMD GPU: Remove the VESA Boot Argument After Patching

For systems with an AMD discrete GPU, OpCore Simplify adds a boot argument (-radvesa or -amd_no_dgpu_accel) to your config.plist to force the GPU into VESA (framebuffer-only) mode during installation. This is intentional — it prevents a black screen before GPU acceleration is available — but it must be removed after OCLP root patches have been applied, otherwise GPU acceleration will remain disabled. After applying OCLP root patches:
  1. Mount your EFI partition and open EFI/OC/config.plist in ProperTree.
  2. Navigate to NVRAM → Add → 7C436110-AB2A-4BBB-A880-FE41995C9F82.
  3. Find the boot-args string value and remove -radvesa or -amd_no_dgpu_accel from it (leave any other boot arguments intact).
  4. Save the file and reboot.
If you reboot after OCLP patching without removing the VESA boot argument, your screen will display only a basic framebuffer with no GPU acceleration, even though OCLP applied its patches correctly. The two steps — patching and removing the boot argument — are both required for GPU acceleration to function.

​
NVRAM Bluetooth Controller Bypass

Some systems have an internal Bluetooth controller that OCLP checks before applying patches. OpCore Simplify automatically adds the required NVRAM entry (bluetoothExternalDongleFailed or equivalent) to your config.plist when OCLP support is enabled at build time. This ensures OCLP does not refuse to patch because it detects an unsupported internal Bluetooth device. No manual action is required on your part.

​
Subsequent macOS Updates

After applying OCLP root patches, keep the following in mind for future macOS updates:
  • Delta (incremental) updates may fail or revert the root patches. If a system update removes GPU acceleration or Wi-Fi, simply re-run OCLP Post-Install Root Patch after updating.
  • Full installer updates (using a downloaded macOS installer) are more reliable when root patches are in place.
  • Always download OCLP 3.0.0+ from lzhoang2801 when re-patching — do not use an older or official Dortania release.

​
Next Steps

Kext Customization

Review and customise the kexts included in your EFI

Troubleshooting

Diagnose boot failures, missing acceleration, and other post-install issues

Build docs developers (and LLMs) love

Get started for freeTalk to us