Installing new macOS on unsupported hardware (OCLP patcher and others)

[Matgen84]

3 hours ago, deeveedee said:

Just curious - what happens if you remove boot-arg amfi=0x80 and the "Disable Library Validation" kernel patches from your config.plist (leaving AMFIPass.kext enabled).

 

@deeveedee I try ASAP without patches, boot args and report. Nevertheless, according to the guide: Here. Only AMFIPass.kext is necessary for Ivybridge.


REPORT: my Ivybridge (SMBIOS macPro6,1) can boot Sequoia 15.0.1 without "Disable AMFI" and "Disable Library Validation", idem for amfi=0x80.
 

Spoiler

 

Edited October 25, 2024 by Matgen84

[Matgen84]

Hi @deeveedee and all users.

I just read  OCLP commit 6780fe3 about post-install.md : "SIP settings can be accessed from the Security tab shown in the images. To change SIP settings, make the changes here, return in main menu and rebuild OpenCore using the first option." "All Metal capable systems from 2012 onward (incl. NVIDIA Kepler and Intel HD 4000) as well as Mac Pros with upgraded GPU can run with full SIP enabled."

 

So, It seems that OCLP generate an Opencore-mod for root-patches. I don't understand. It's unclear for me. Need help for explanation ! Please.
 

[deeveedee]

@Matgen84  Unless I'm misunderstanding your question, I believe that you are misinterpreting the OCLP documentation.  The OCLP SIP settings are not applied in the root patches.  They are applied in the OCLP-generated Open Core EFI (config.plist). 

 

The OCLP documentation is simply saying that some real Macs can run with SIP fully enabled if they do not require OCLP post-install patches (just as many hackintoshes can run with SIP fully enabled if they don't require OCLP root-patches).  The documentation also says that users can manually override OCLP's default SIP settings in the OCLP GUI.  When a user overrides default SIP settings in the OCLP GUI and then generates an OC EFI (using "Build and Install Open Core"), the OCLP SIP settings dictate the value of csr-active-config in the OC config.plist.

[Matgen84]

Hi All

On my old Ivybridge (SMBIOS macPro6,1 Opencore Nightly 1.0.3 + OCLP), I can't update Sequoia:

• 15.0 to 15.0.1: SoftwareUpdate in System Settings,  is showing up the update. But click on button do nothing
• 15.0.1 to 15.1: same issue

To update Sequoia, I download Full Installer to update my system.  @Stefanalmare who have the same issue,  tell to me, it's because (maybe)  OCLP. 

Any solutions ? Please.

 

Note: there is an alert on "About my Mac". Do you know why ?
 

Edited October 31, 2024 by Matgen84

[LockDown]

failed on incremental update but full works?

Edited October 31, 2024 by LockDown

[miliuco]

@Matgen84

Are you on MacPro7,1 SMBIOS? If yes, the alert in About This Mac can't be removed on Sonoma and Sequoia. All work fine with RestrictEvents but this alert can't be removed.

Anyway try these commands but as far as I know they only work up to Ventura.

defaults delete com.apple.SlotNotificationsPref memoryBadgeCount
defaults delete com.apple.SlotNotificationsPref expansionBadgeCount

 

Edited October 31, 2024 by miliuco
Typo

[Matgen84]

8 hours ago, miliuco said:

@Matgen84

Are you on MacPro7,1 SMBIOS? If yes, the alert in About This Mac can't be removed on Sonoma and Sequoia. All work fine with RestrictEvents but this alert can't be removed.

Anyway try these commands but as far as I know they only work up to Ventura.

defaults delete com.apple.SlotNotificationsPref memoryBadgeCount
defaults delete com.apple.SlotNotificationsPref expansionBadgeCount

 

 

@miliuco I'm using  MacPro6,1 SMBIOS (my old Ivybridge). Yes, RestricEvents do the job. This two commands do not working on Sequoia..

About SoftwareUpdate (System/Settings) do nothing, have you got an idea ?

Edited November 1, 2024 by Matgen84

[Slice]

On 10/31/2024 at 9:59 AM, Matgen84 said:

Hi All

On my old Ivybridge (SMBIOS macPro6,1 Opencore Nightly 1.0.3 + OCLP), I can't update Sequoia:

• 15.0 to 15.0.1: SoftwareUpdate in System Settings,  is showing up the update. But click on button do nothing
• 15.0.1 to 15.1: same issue

To update Sequoia, I download Full Installer to update my system.  @Stefanalmare who have the same issue,  tell to me, it's because (maybe)  OCLP. 

Any solutions ? Please.

 

Note: there is an alert on "About my Mac". Do you know why ?
 

As usual:

1. Revert OCLP patch

2. Update the system

2. Apply OCLP again.

[Renard45]

On 10/30/2024 at 8:59 PM, Matgen84 said:

Hi All

On my old Ivybridge (SMBIOS macPro6,1 Opencore Nightly 1.0.3 + OCLP), I can't update Sequoia:

• 15.0 to 15.0.1: SoftwareUpdate in System Settings,  is showing up the update. But click on button do nothing
• 15.0.1 to 15.1: same issue

To update Sequoia, I download Full Installer to update my system.  @Stefanalmare who have the same issue,  tell to me, it's because (maybe)  OCLP. 

Any solutions ? Please.

 

Note: there is an alert on "About my Mac". Do you know why ?
 

on my old Lenovo for update i can not have only update i need to download the full installer too to update my laptop.

Edited August 21, 2025 by Renard45

[Renard45]

Someone has black screen with mouse cursor after install? can not have the finish setup on Tahoe

setup:

Asus Z97-C

intel i7 4470

Nvidia GT 720 2GB

 

works very well on sequoia 15.6 with OCLP

[mnfesq]

I hope someone actually sees this post as I am posting it where it belongs rather than in the Tahoe prerelease thread that has hundreds of pages by now.

 

I have been trying to get an update on the status of developers' work on a WiFi patch for Broadcom chips in OCLP.  The OCLP GitHub page only shows a single entry from June of this year.  I read @laobamac_yyds's post somewhere that the development of a WiFi patch will be much more difficult than in prior years but that also was said back when his first OCLP-Mod with the AppleHDA fix was released.  Since then, there has been virtual if not actual radio silence on efforts to develop the patch.  I'm not impatient for the result but it would be nice to get a status update from time-to-time about the issues that have been encountered and the ideas that have been generated to address them, at least in general, layman's terms.

 

If anyone can give a status report or has seen a link to anything related to WiFi patch development, I would appreciate being let into the loop.  Thanks.

Edited August 27, 2025 by mnfesq

[miliuco]

@mnfesq

I'm pretty sure that OCLP devs are working on it, in a private mode for now. Nothing to do on our side at the moment. 

[Matgen84]

To all:

 

I'm using OCLP 2.4.1 on my old Ivybridge (Sequoia 15.6.1, MetalLibSupport 15.6.1 24G90). Now I want to update to Sequoia 15.7.  But It seems that MetalLibSupportPkg 15.7. 24G222 and OCLP 2.4.2 doesn't exist (or never exist).

So my question: can I use OCLP 2.4.1 with MetalLibSupport 15.6.1 24G90 on Sequoia 15.7 or not. Let me know, please.

[Matgen84]

On 9/22/2025 at 1:10 PM, Matgen84 said:

To all:

 

I'm using OCLP 2.4.1 on my old Ivybridge (Sequoia 15.6.1, MetalLibSupport 15.6.1 24G90). Now I want to update to Sequoia 15.7.  But It seems that MetalLibSupportPkg 15.7. 24G222 and OCLP 2.4.2 doesn't exist (or never exist).

So my question: can I use OCLP 2.4.1 with MetalLibSupport 15.6.1 24G90 on Sequoia 15.7 or not. Let me know, please.

 

To all: I use OCLP 2.4.1 with MetalLibSupport 15.6.1 24G90 on Sequoia 15.7 : OK, working. 😊

[naiclub]

2 hours ago, Matgen84 said:

 

To all: I use OCLP 2.4.1 with MetalLibSupport 15.6.1 24G90 on Sequoia 15.7 : OK, working. 😊

This version of OCLP 2.4.1 I can use it in Sequoia 15.6.1 24G90 with gt730 2gb QE/Cl graphics acceleration smoothly.

 

[FirstCustomac]

Anyone had success with OLCP 3.0 nightly from the macos-next branch? It seems like AMFIPass.kext is not affective even with -amfipassbeta.

 

Edit: Oops scratch that. I've had set Maxkernel to 24.9.9 for AMFIPass.kext

Edited December 4, 2025 by FirstCustomac

[deeveedee]

@FirstCustomac No.  At the time of this post, the nightly still has "maxOS = Sequoia" so it won't even patch Tahoe without modifications.  See this.

 

EDIT: earlier today, I built OCLP 3.0.0 from source after seeing this commit:

 

Unfortunately, that commit only unblocks Tahoe for downloading macOS installers - not for applying patches.  I manually unblocked Tahoe for patching and found that I couldn't apply the AppleHDA patch because AppleHDA.kext is not yet included in UniversalBinaries.  I then manually added AppleHDA.kext to UniversalBinaries and found that OCLP was placing AppleHDA.kext in /Library/Extensions instead of /System/Library/Extensions.

 

As of this post, the "official" OCLP 3.0.0 source is not ready.

Edited December 4, 2025 by deeveedee

[Slice]

Check unofficial OCLP tuned for Tahoe

https://github.com/lzhoang2801/OpenCore-Legacy-Patcher

[MakAsrock]

Check unofficial OCLP-Plus (Tahoe Patch Set).
https://github.com/YBronst/OCLP-YBronst

Edited May 29 by MakAsrock

[Matgen84]

1 hour ago, MakAsrock said:

Check unofficial OCLP-3.1.7 Tahoe Patch Set
https://github.com/YBronst/OCLP-YBronst

 

Great job. Thank a lot. @MakAsrock  Question about your changeling: Please forgive me. But according to the release notes, the bug preventing HFS volumes from opening has been fixed in macOS 26.4 Beta 2. This would mean that the HFS+ format is once again supported natively. If I well understood.

[MakAsrock]

49 minutes ago, Matgen84 said:

 

Great job. Thank a lot. @MakAsrock  Question about your changeling: Please forgive me. But according to the release notes, the bug preventing HFS volumes from opening has been fixed in macOS 26.4 Beta 2. This would mean that the HFS+ format is once again supported natively. If I well understood.

Yes, you understood correctly that the HFS+ format is supported natively again. But just in case, I left the APFS format in the unofficial OCLP-3.1.7 Tahoe Patch Set, just to be on the safe side.

[Max.1974]

Hello my dear friends, for some time now I have noticed that my Apple devices—even on the Mac Mini M4 Pro and on my other Hackintosh machines that still use Broadcom Bluetooth—require pressing a key on the keyboard, especially, to “activate” the keyboard during boot. And it is even worse in sleep mode. The Apple Mouse is not as affected, but after waking from sleep it would not connect in Hackintoshes.

 

I developed a tool that solved this issue for me, and I think it could also be useful for people who use OCLP, although that is not my case. So soon, after completing the tests, the application Bluetooth Root Jumper will be available, God willing. It works wonderfully well and is a program fully built around modern macOS APIs, running from Ventura all the way up to Tahoe.

 

I do not use Intel Bluetooth with this program because I have not tested it yet. And as I have always done, I do not use BlueToolFixup.kext, and everything works perfectly after sleep and in all other situations.

 

Here is a preview of it running on the M4 Pro, and it works perfectly on Hackintosh systems as well. For now, I am testing devices such as the mouse and the keyboard, and I will begin testing Bluetooth audio soon.

 

 

 

 

  

 

 

 

 

 

 

 

 

 

Edited March 15 by Max.1974

[MakAsrock]

On 3/15/2026 at 3:56 PM, Matgen84 said:

 

Great job. Thank a lot. @MakAsrock  Question about your changeling: Please forgive me. But according to the release notes, the bug preventing HFS volumes from opening has been fixed in macOS 26.4 Beta 2. This would mean that the HFS+ format is once again supported natively. If I well understood.

Yes, you understood everything correctly.

[deeveedee]

OCLP Devs have provided an update starting here.  Highlights are

• Dhinakg is going to be interning at Apple this summer
• Remaining Devs are continuing to make progress, slowly but surely, on OCLP 3.0.0