Root patching: what OCLP adds after the install

#How to run root patching

1. Open OpenCore Legacy Patcher and click Post-Install Root Patch. The screen lists the patches for your Mac, or says “No patches required”.
2. Connect to the internet, ideally by Ethernet.
3. Click Start Root Patching, enter your password, wait, and restart when asked.
4. To undo, click Revert Root Patches (macOS Monterey and newer).

If you created the USB installer with OCLP for the right model, root patching runs automatically after the install. The screen also shows “Root Volume last patched:” with the date and OCLP version.

#Every patch set

Generated by running each patch set's own detection code against every supported Mac's stock hardware, for macOS Big Sur through Tahoe.

Generated by running each hardware patch set class from the OCLP 3.0.0 source (commit a1c74ce) against every supported model's stock hardware. “Files” counts the items the patch set installs, merges or removes on the system volume.

#Graphics: three families

Non-Metal

GPUs without Metal support: Intel GMA X3100, Iron Lake and Sandy Bridge (HD 3000), NVIDIA Tesla, AMD TeraScale 1 and 2. Found in most 2007–2011 Macs. OCLP restores OpenGL acceleration; apps that require Metal do not work.

Metal 3802 (legacy Metal)

Intel Ivy Bridge (HD 4000), Haswell, and NVIDIA Kepler. Found in 2012–2014 Macs and the 15-inch 2012–2014 MacBook Pros. Their Metal drivers were removed in Monterey (Ivy Bridge, Kepler) and Ventura (Haswell). From Sequoia they also need MetallibSupportPkg.

Metal 31001

Intel Broadwell, Skylake, AMD GCN and Polaris (and Vega or Navi in upgraded Mac Pros without AVX2). Found in 2015–2017 Macs. The closest to a native experience.

#What each graphics and audio patch replaces, and why

OCLP does not just switch drivers on. It copies old versions of specific files from earlier macOS releases into the system volume. Dortania documents the file list for each on-disk patch and the reason for the awkward ones, such as why Metal and the shader compilers are downgraded to 13.2.1 on 3802-based GPUs. This is that documentation, in full, one block per patch.

#Every kext OCLP loads, and why

OpenCore loads kernel extensions (kexts) at boot. We built OpenCore for every supported Mac and counted which kexts each build loads. Where Dortania explains a kext, the reason is quoted; the few it does not explain are marked.

#Patch sets that need a download

Two kinds of packages are too large or too build-specific to ship inside the app. OCLP downloads them during patching, which is why you need internet then:

• Kernel Debug Kit (KDK): Apple's kernel debug files, which OCLP needs to rebuild the kernel collection with its drivers. Fetched through Dortania's KdkSupportPkg. Needed by AMD GCN and Polaris graphics from Ventura, every non-Metal patch set from Ventura, and on Tahoe by the Modern Audio patch set (so every patched Mac on Tahoe).
• MetallibSupportPkg: Metal libraries rebuilt for Ivy Bridge, Haswell and Kepler GPUs on Sequoia. It must match your exact macOS build.

Without a connection, OCLP installs only the Wi-Fi patch first, so you can get online, then asks you to patch again (Dortania, Post-Installation).

#Why root patching needs lowered SIP

System Integrity Protection blocks changes to system files. OCLP lowers the flags it needs through OpenCore: on Ventura and newer, CSR_ALLOW_UNTRUSTED_KEXTS, CSR_ALLOW_UNRESTRICTED_FS and CSR_ALLOW_UNAUTHENTICATED_ROOT (from sip_data.py). The security trade-off is explained in Is OCLP safe?.

#Common questions

Something wrong or out of date on this page? Email hello@oclp.dev and we will fix it (see our corrections policy).