The OCLP-Plus 3.x (Tahoe Patch Set).

[MakAsrock]

OCLP-Plus (Tahoe Patch Set) for now it will be like this:

🏔️ Full macOS Tahoe Support

• Modern root patching support for macOS Tahoe 26.0 (25A5316i) through macOS 26.4.1 (25E253) and later versions.

• 📖 `Readme`

•  🔖`Changeling`

• Supported native or spoofed models (SMBIOS) in macOS Tahoe:
•   iMac: iMac20,1, iMac20,2
•   MacBook Pro: MacBookPro16,1, MacBookPro16,2, MacBookPro16,4
•   Mac Pro: MacPro7,1

• This set creates only draft templates for manual configuration and does not generate ready-made EFI folders.

• Legacy root patching support for macOS Sequoia 15.7.5 (24G624) and earlier, as in OpenCore Legacy Patcher 2.4.1.

• Note: For macOS Sequoia and earlier, compatibility and SMBIOS requirements follow the standard limits of each respective operating system.

Edited April 28 by MakAsrock

[MakAsrock]

OCLP-Plus 3.2.1 (Tahoe Patch Set):

Edited April 28 by MakAsrock

[Jessy Lou]

First, thank you for your work on OCLP-Plus!

I'm struggling with my Z390 ASUS ROG Hackintosh on Tahoe only. I have no issue with Sequoia. On Tahoe everything is Ok, except the Wi-Fi based on a BCM43602CS.
What I did:
1). Install fresh Tahoe 26.4
2). Install KDK
3). Install OCLP-Plus 3.2.1 (started earlier with 3.1.9)
4). Run Root Patch (detecting both Sound and Wi-Fi).
5) Once applied, reboot with 2 x NVRAM clear.

Outcome: sound Ok, everything Ok except Wi-Fi.

Here is my config.plist (KGP already helped me weeks ago to clean-up my config file), but I fear there's still something missing.

config.plist

Edited May 4 by Jessy Lou

[MakAsrock]

4 hours ago, Jessy Lou said:

First, thank you for your work on OCLP-Plus!

I'm struggling with my Z390 ASUS ROG Hackintosh on Tahoe only. I have no issue with Sequoia. On Tahoe everything is Ok, except the Wi-Fi based on a BCM43602CS.
What I did:
1). Install fresh Tahoe 26.4
2). Install KDK
3). Install OCLP-Plus 3.2.1 (started earlier with 3.1.9)
4). Run Root Patch (detecting both Sound and Wi-Fi).
5) Once applied, reboot with 2 x NVRAM clear.

Outcome: sound Ok, everything Ok except Wi-Fi.

Here is my config.plist (KGP already helped me weeks ago to clean-up my config file), but I fear there's still something missing.

config.plist 25.21 kB · 4 downloads

1. What your full DeviceProperties section for that card should look like:
(Note: I used PciRoot(0x0)/Pci(0x1D,0x3)/Pci(0x0,0x0) just as an example).

Go to the PCI path of your Wi-Fi card in config.plist and make sure it has these entries:
(Note: Internal@0,29,3/0,0 is just a cosmetic string, but its values should also preferably match your actual slot).
<dict>
    <key>AAPL,slot-name</key>
    <string>Internal@0,29,3/0,0</string>
    <key>device_type</key>
    <string>Network controller</string>
    <key>model</key>
    <string>BCM43602 802.11ac Dual Band Wireless Network Adapter</string>
</dict>
Since your Wi-Fi works perfectly fine on Sequoia, boot into it, open System Information -> PCI, find your Broadcom card, and check the actual path there!
2. You need to check if your current USB kext is already compatible with Tahoe, or if it needs to be adapted. 
3. For adaptation, you can use USBMap from here then run USBMapInjectorEdit.command and drag and drop the old kext into the terminal window, selecting the desired option.
The result will appear in the Results folder.

Edited May 4 by MakAsrock

[Jessy Lou]

Done with the PCI path I got from Hackintool on Sequoia.
Just booted on Tahoe... Same.

I checked with Hackintool, the card is present on PCIe.

When I open OCLP-Plus, to run Post-Install Root Patch, I always get:
Available patches for your system:
All applicable patches already installed
Cannot patch due to the following reasons:
Root volume dirty, unpatch to continue.

I have this since days, without finding the solution.

Shall I try to rebuild the EFI partition? Honestly I don't know how to fix this, while many others get success on the 1st shot.

PS: while my Sequoia partition is vital for me, I'm booting Sequoia based on the following config.plist (I didn't manage to use only one, even after the helpful help from KGP)... and I can't boot on Tahoe with this config.plist: crash.

 

My install: first SSD (NVMe) dedicated to Sequoia with its dedicated EFI partition. Second SSD (Samsung on SATA) dedicated to Tahoe with its dedicated EFI partition. While I boot on Tahoe quite quickly and while everything (including Ethernet) is working except my Wi-Fi, I'm not that convinced the Tahoe EFI partition is broken. But I don't know what "Root volume dirty" means.

 

config-sequoia.plist

Edited May 4 by Jessy Lou

[MakAsrock]

28 minutes ago, Jessy Lou said:

Done with the PCI path I got from Hackintool on Sequoia.
Just booted on Tahoe... Same.

I checked with Hackintool, the card is present on PCIe.

When I open OCLP-Plus, to run Post-Install Root Patch, I always get:
Available patches for your system:
All applicable patches already installed
Cannot patch due to the following reasons:
Root volume dirty, unpatch to continue.

I have this since days, without finding the solution.

Shall I try to rebuild the EFI partition? Honestly I don't know how to fix this, while many others get success on the 1st shot.

PS: while my Sequoia partition is vital for me, I'm booting Sequoia based on the following config.plist (I didn't manage to use only one, even after the helpful help from KGP)... and I can't boot on Tahoe with this config.plist: crash.

 

My install: first SSD (NVMe) dedicated to Sequoia with its dedicated EFI partition. Second SSD (Samsung on SATA) dedicated to Tahoe with its dedicated EFI partition. While I boot on Tahoe quite quickly and while everything (including Ethernet) is working except my Wi-Fi, I'm not that convinced the Tahoe EFI partition is broken. But I don't know what "Root volume dirty" means.

 

config-sequoia.plist 37.65 kB · 1 download

The "Root volume dirty" error happens when OCLP detects that previous patches were interrupted or the system volume flag wasn't cleared. You don't need to rebuild your EFI partition!

To fix this, you just need to revert the root patches and apply them again. Here is how:

Open OCLP-Plus in macOS Tahoe.

Click on Post-Install Root Patch.

Look for the "Revert Root Patches" button (or it might be under the "Unpatch" option depending on your version) and click it.

Once it finishes, reboot your computer.

After the reboot, open OCLP-Plus again, go back to Post-Install Root Patch, and run the patcher normally.

[kgp]

1 hour ago, Jessy Lou said:

Done with the PCI path I got from Hackintool on Sequoia.
Just booted on Tahoe... Same.

I checked with Hackintool, the card is present on PCIe.

When I open OCLP-Plus, to run Post-Install Root Patch, I always get:
Available patches for your system:
All applicable patches already installed
Cannot patch due to the following reasons:
Root volume dirty, unpatch to continue.

I have this since days, without finding the solution.

Shall I try to rebuild the EFI partition? Honestly I don't know how to fix this, while many others get success on the 1st shot.

PS: while my Sequoia partition is vital for me, I'm booting Sequoia based on the following config.plist (I didn't manage to use only one, even after the helpful help from KGP)... and I can't boot on Tahoe with this config.plist: crash.

 

My install: first SSD (NVMe) dedicated to Sequoia with its dedicated EFI partition. Second SSD (Samsung on SATA) dedicated to Tahoe with its dedicated EFI partition. While I boot on Tahoe quite quickly and while everything (including Ethernet) is working except my Wi-Fi, I'm not that convinced the Tahoe EFI partition is broken. But I don't know what "Root volume dirty" means.

 

config-sequoia.plist 37.65 kB · 1 download

Your config.plist is heavily misconfigured and would never work such with OCLP under Tahoe! Please don’t go around saying this config.plist is something I came up with for OCLP on Tahoe. 😉

 

1.) For Tahoe, set MaxKernel to 25.99.99! You have actually 24.99.99!

 

 

 

 

2.) Enable Kernel Quirk "DisableIOMapper" (i.e. Apple-VTD off)

3.) Add boot argument -amfipassbeta

4.) Use csr-active-config = 03080000

 

Simply use the revised config.plist attached below!

 

Good luck,

 

KGP 👍

 

 

P.S: I did not check your onboard ethernet controller but I have seen that you are using IntelMausi.kext V1.0.8. You might want to try IntelMausiEthernet.kext v3.0.0 instead.  

 

IntelMausiEthernet.kext.zip

config-sequoia-revised.plist

Edited May 4 by kgp
Adding inconsistency 4.)

[kgp]

@Jessy Lou, I found another inconsistency! See 4.) in my post above and reload the attached config-sequoia-revised.plist. 

Edited May 4 by kgp

[MakAsrock]

2 hours ago, Jessy Lou said:

Done with the PCI path I got from Hackintool on Sequoia.
Just booted on Tahoe... Same.

I checked with Hackintool, the card is present on PCIe.

When I open OCLP-Plus, to run Post-Install Root Patch, I always get:
Available patches for your system:
All applicable patches already installed
Cannot patch due to the following reasons:
Root volume dirty, unpatch to continue.

I have this since days, without finding the solution.

Shall I try to rebuild the EFI partition? Honestly I don't know how to fix this, while many others get success on the 1st shot.

PS: while my Sequoia partition is vital for me, I'm booting Sequoia based on the following config.plist (I didn't manage to use only one, even after the helpful help from KGP)... and I can't boot on Tahoe with this config.plist: crash.

 

My install: first SSD (NVMe) dedicated to Sequoia with its dedicated EFI partition. Second SSD (Samsung on SATA) dedicated to Tahoe with its dedicated EFI partition. While I boot on Tahoe quite quickly and while everything (including Ethernet) is working except my Wi-Fi, I'm not that convinced the Tahoe EFI partition is broken. But I don't know what "Root volume dirty" means.

 

config-sequoia.plist 37.65 kB · 2 downloads

I was totally gonna slack off until tomorrow because that config was heavily misconfigured and it's Lag BaOmer BBQ time here today! But kgp did all the heavy lifting for me! Tausend Dank, Kumpel! 🇩🇪 🤗

Edited May 4 by MakAsrock

[Jessy Lou]

Quick tests done this morning:
1). Took the config-sequoira-revised.plist from KGP (without replacing with IntelMausiEthernet.kext yet).
2). Boot on Tahoe = OK

3); Boot on Sequoia = OK

Details on Sequoia: 100% Ok. Everything is working as expected.

Details on Tahoe: Wi-Fi device is seen (not only from Hackintool) but the network remains yellow without being able to grab any network.

 

What I did on Tahoe:

1). Run OCLP and revert the root patches + Boot

2). Run again OCLP and run Post-Install Root Patches (everything seemed Ok, as during all my tests) + Boot

3). Wi-Fi is greyed and yellow in Network details, without seeing any network to connect to.
4). Run OCLP to check to status: still Cannot patch due to the following reasons:
Root volume dirty, unpatch to continue.

I have to confess I didn't clear the NVRAM twice as this config.plist is designed to work on both Sequoia and Tahoe.

Thanks again for your help which is really very appreciated.

 

 

[kgp]

7 hours ago, Jessy Lou said:

Quick tests done this morning:
1). Took the config-sequoira-revised.plist from KGP (without replacing with IntelMausiEthernet.kext yet).
2). Boot on Tahoe = OK

3); Boot on Sequoia = OK

Details on Sequoia: 100% Ok. Everything is working as expected.

Details on Tahoe: Wi-Fi device is seen (not only from Hackintool) but the network remains yellow without being able to grab any network.

 

What I did on Tahoe:

1). Run OCLP and revert the root patches + Boot

2). Run again OCLP and run Post-Install Root Patches (everything seemed Ok, as during all my tests) + Boot

3). Wi-Fi is greyed and yellow in Network details, without seeing any network to connect to.
4). Run OCLP to check to status: still Cannot patch due to the following reasons:
Root volume dirty, unpatch to continue.

I have to confess I didn't clear the NVRAM twice as this config.plist is designed to work on both Sequoia and Tahoe.

Thanks again for your help which is really very appreciated.

 

 

 

1.) Dirty root volume:

After reverting the root patches, you must reboot your system before reapplying them.

This also allows you to switch between different OCLP variants for root patching.

2.) My revision of your config.plist is designed to work with both Sequoia and Tahoe. For Sequoia, however, I recommend using OCLP 2.4.1.

3.) In your config.plist (Kernel -> Add), make sure AMFIPass.kext is placed before IOSkywalkFamily.kext, IO80211FamilyLegacy.kext, and IO80211FamilyLegacy.kext/Contents/PlugIns/AirPortBrcmNIC.kext.

4.) For Tahoe, use OpenCore 1.0.6 or 1.0.7.

 

5.) Try to use IntelMausiEthernet 3.0.0 instead of IntelMausi 1.0.8

 

6.) Make sure you are using the correct kext versions for OCLP. You can use my Broadcom EFI folder as a reference. I was not able to verify this, as you only provided your config.plist and not the full EFI folder.

 

7.) We’re talking about a Broadcom Wi-Fi chipset here, not an Intel one, right?

 

8.) As another option delete Wi-Fi in System Settings-> Network and Add Service -> Wi-Fi subsequently (Wi-Fi reset). Alternatively you could test your EFI-Folder on a separate disk with OCLP after a clean install. 

Edited May 5 by kgp

[MakAsrock]

16 hours ago, Jessy Lou said:

Done with the PCI path I got from Hackintool on Sequoia.
Just booted on Tahoe... Same.

I checked with Hackintool, the card is present on PCIe.

When I open OCLP-Plus, to run Post-Install Root Patch, I always get:
Available patches for your system:
All applicable patches already installed
Cannot patch due to the following reasons:
Root volume dirty, unpatch to continue.

I have this since days, without finding the solution.

Shall I try to rebuild the EFI partition? Honestly I don't know how to fix this, while many others get success on the 1st shot.

PS: while my Sequoia partition is vital for me, I'm booting Sequoia based on the following config.plist (I didn't manage to use only one, even after the helpful help from KGP)... and I can't boot on Tahoe with this config.plist: crash.

 

My install: first SSD (NVMe) dedicated to Sequoia with its dedicated EFI partition. Second SSD (Samsung on SATA) dedicated to Tahoe with its dedicated EFI partition. While I boot on Tahoe quite quickly and while everything (including Ethernet) is working except my Wi-Fi, I'm not that convinced the Tahoe EFI partition is broken. But I don't know what "Root volume dirty" means.

 

config-sequoia.plist 37.65 kB · 2 downloads

1. Create an issue on my GitHub.
2. Attach your EFI folder to it.
3. Describe in detail what's working for you in Sequoia.
And I'll try to configure everything for Tahoe.
Large files cannot be attached here.

[Jessy Lou]

@MakAsrock, I'm going to reinstall a fresh Tahoe 26.4 to restart the process. Then, I'm going to describe each step of my test, and I'm going to prepare the issue on your GitHub with my EFI folder, without forgetting to describe what does work on Sequoia. I might be able to do that during the weekend due to my daily work on Sequoia.

@KGP, let me take each of your points bellow:
1). For sure I did boot at each step (following OCLP-Plus is telling on the screen in addition to MakAsrock advices). As the root still seems dirty, I'm going to reinstall Tahoe to clean-up the current mess.
2). On Sequoia I work exclusively with OCLP 2.4.1. I'm using OCLP-Plus only on Tahoe.

3). I'm now working with your revised config.plist on which I moved up AMFIPass.kext to be placed before IOSkywalkFamily.kext, IO80211FamilyLegacy.kext, and IO80211FamilyLegacy.kext/Contents/PlugIns/AirPortBrcmNIC.kext. This is the 1st deviation to your revised config.plist.
4). As I boot from the same EFI partition thanks to your revised config.plist, I'm booting from the same OpenCore Boot Loader 1.0.7 on both Sequoia (15.7.5) and on Tahoe (26.4).

5). Thanks for the original package! I've now replaced the older IntelMausi 1.0.8 (dec '24) with the recent IntelMausiEthernet 3.0.0 (dec '25). Even if I'm rarely using LAN, I trust expert advices. . This is the 2nd and last deviation from your revised config.plist.

6). On Sequoia with OCLP 2.4.1, everything works for months. I'm now working with the revised config.plist (including the 2 deviations mentioned above). So far, the system works like a charm.
On Tahoe, I focus on using the latest release of OCLP-Plus which is now 3.2.1 (the first release I tested was 3.1.8). As I'm using same EFI, here is the list of kexts and releases I'm using in the exact same order as it is in the config.plist file:

1. Lilu.kext -> 1.7.2
2. VirtualSMC.kext -> 1.3.7
3. WhateverGreen.kext -> 1.7.0
4. AppleALC.kext -> 1.9.7
5. USBMap.kext (build for ASUS ROG Maximus XI Hero following Dortania guide) for MacPro7,1 SMBIOS
6. SMCProcessor.kext -> 1.3.3
7. SMCSuperIO.kext -> 1.3.3
8. IntelMausiEthernet.kext -> 3.0.0
9. RestrictEvents.kext -> 1.1.6 (to follow your advices when using MacPro7,1 in a previous chat, and to follow the "EFI-KGP-public-v.1.1.5-OCLP-Broadcom" EFI folder you're sharing also on another post, I'm using it to ensure Tahoe is running in best conditions).
10. AMFIPass.kext -> 1.4.1
11. IOSkywalkFamily.kext -> 1.0
12. IO80211FamilyLegacy.kext -> V1200.12.2b1
13. IO80211FamilyLegacy.kext/Contents/PlugIns/AirPortBrcmNIC.kext -> V1400.1.1

This is the list of added kexts.
As for com.apple.iokit.IOSkywalkFamily to block, I updated the MaxKernel to 25.99.99)

 

7). I'm dealing with a real BCM43602CS (I've been helped previous by you the this. At this time, I was cheated by the vendor... until I bought a real BCM: vendor as 0x14E4 and device as 0x43BA). Since November last year, on Sequoia I have AirDrop, AirPlay, Screen Sharing... working as with a real Mac. I don't have any Intel Wi-Fi!

 

Next step for me:

A). Reset NVRAM twice to test the brand new config.plist for Sequoia to run a few tests. For Sequoia CSR is 7F080000 for one particular app that needs this. I can confirm that so far this CSR allowed my to run OCLP 2.4.1 and a few previous releases with no issue at all. When running OCLP, it tells me about the last Root Patch, I don't have the dirty root in there.
B). Reset NVRAM twice to test the brand new config.plist for Tahoe with CSR as 03080000.
C). Reinstall from scratch Tahoe 26.4 to then use OCLP-Plus 3.2.1 and report the details as asked by MakAsrock.

 

Anyways: thank you both for your time.

Edited May 5 by Jessy Lou

[kgp]

50 minutes ago, Jessy Lou said:

@MakAsrock, I'm going to reinstall a fresh Tahoe 26.4 to restart the process. Then, I'm going to describe each step of my test, and I'm going to prepare the issue on your GitHub with my EFI folder, without forgetting to describe what does work on Sequoia. I might be able to do that during the weekend due to my daily work on Sequoia.

@KGP, let me take each of your points bellow:
1). For sure I did boot at each step (following OCLP-Plus is telling on the screen in addition to MakAsrock advices). As the root still seems dirty, I'm going to reinstall Tahoe to clean-up the current mess.
2). On Sequoia I work exclusively with OCLP 2.4.1. I'm using OCLP-Plus only on Tahoe.

3). I'm now working with your revised config.plist on which I moved up AMFIPass.kext to be placed before IOSkywalkFamily.kext, IO80211FamilyLegacy.kext, and IO80211FamilyLegacy.kext/Contents/PlugIns/AirPortBrcmNIC.kext. This is the 1st deviation to your revised config.plist.
4). As I boot from the same EFI partition thanks to your revised config.plist, I'm booting from the same OpenCore Boot Loader 1.0.7 on both Sequoia (15.7.5) and on Tahoe (26.4).

5). Thanks for the original package! I've now replaced the older IntelMausi 1.0.8 (dec '24) with the recent IntelMausiEthernet 3.0.0 (dec '25). Even if I'm rarely using LAN, I trust expert advices. . This is the 2nd and last deviation from your revised config.plist.

6). On Sequoia with OCLP 2.4.1, everything works for months. I'm now working with the revised config.plist (including the 2 deviations mentioned above). So far, the system works like a charm.
On Tahoe, I focus on using the latest release of OCLP-Plus which is now 3.2.1 (the first release I tested was 3.1.8). As I'm using same EFI, here is the list of kexts and releases I'm using in the exact same order as it is in the config.plist file:

1. Lilu.kext -> 1.7.2
2. VirtualSMC.kext -> 1.3.7
3. WhateverGreen.kext -> 1.7.0
4. AppleALC.kext -> 1.9.7
5. USBMap.kext (build for ASUS ROG Maximus XI Hero following Dortania guide) for MacPro7,1 SMBIOS
6. SMCProcessor.kext -> 1.3.3
7. SMCSuperIO.kext -> 1.3.3
8. IntelMausiEthernet.kext -> 3.0.0
9. RestrictEvents.kext -> 1.1.6 (not that sure this is necessary for my MB, but as I'm following your config.plist from the "EFI-KGP-public-v.1.1.5-OCLP-Broadcom" EFI folder you're sharing on another post, I'm using it to ensure Tahoe is running in best conditions)
10. AMFIPass.kext -> 1.4.1
11. IOSkywalkFamily.kext -> 1.0
12. IO80211FamilyLegacy.kext -> V1200.12.2b1
13. IO80211FamilyLegacy.kext/Contents/PlugIns/AirPortBrcmNIC.kext -> V1400.1.1

This is the list of added kexts.
As for com.apple.iokit.IOSkywalkFamily to block, I updated the MaxKernel to 25.99.99)

 

7). I'm dealing with a real BCM43602CS (I've been helped previous by you the this. At this time, I was cheated by the vendor... until I bought a real BCM: vendor as 0x14E4 and device as 0x43BA). Since November last year, on Sequoia I have AirDrop, AirPlay, Screen Sharing... working as with a real Mac. I don't have any Intel Wi-Fi!

 

Next step for me:

A). Reset NVRAM twice to test the brand new config.plist for Sequoia to run a few tests. For Sequoia CSR is 7F080000 for one particular app that needs this. I can confirm that so far this CSR allowed my to run OCLP 2.4.1 and a few previous releases with no issue at all. When running OCLP, it tells me about the last Root Patch, I don't have the dirty root in there.
B). Reset NVRAM twice to test the brand new config.plist for Tahoe with CSR as 03080000.
C). Reinstall from scratch Tahoe 26.4 to then use OCLP-Plus 3.2.1 and report the details as asked by MakAsrock.

 

Anyways: thank you both for your time.

 

Everything looks properly set up in your EFI, my friend.

 

You need to get rid of the dirty root volume; otherwise, you won’t be able to install the root patches. This is usually done by reverting the root patches and then rebooting the system.

 

If that does not help, try a clean install. You can also try running OCLP-Mod 3.1.9 or OCLP 3.0.0 Nightly (amfipassbeta variant) for testing purposes without any changes to your EFI-folder. You can also try to revert the root patches applied with OCLP-Plus using one of the latter two OCLP variants. Maybe this helps in cleaning your dirty root volume.

 

If you are still experiencing issues with Wi-Fi, try the Wi-Fi reset in System Settings I mentioned in my post above (see point 8).

 

By the way, what about modern audio root patches? Do you have audio working, or is OCLP-Plus not working at all on your system?

 

Finally, regarding your kext versions: if I remember correctly, you should be using SMCProcessor.kext 1.3.7 and SMCSuperIO.kext 1.3.7 in line with VirtualSMC.kext 1.3.7 although this is not relevant for OCLP anyway

Edited May 5 by kgp

[Jessy Lou]

Many thanks dear KGP!

As I was looking forward to getting the outcome of my very quick tests, I couldn't resist any longer.

A: everything works as expected. I still have the same Sequoia before struggling with Tahoe! 

B: I guess you know already --> everything works! I couldn't believe when I entered my Wi-Fi pass... This works! . Thanks god, I didn't have to go to your point 8 you mentioned earlier.
To reply to your question: sound is also Ok, based on an early release of OCLP-Plus I was using, certainly from 3.1.8. I tested Ethernet: also Ok.
I did another test beside B: working with the CSR I'm using on Sequoia: 7F080000 instead of 03080000. OCLP-Plus is not complaining when launching with this CSR.

As for C: I'm going to take time for that. 1st I don't like having some unstable system... I did so many tests I don't know what is clean and what isn't. I keep my own documentation, therefore I need to do this fresh install anyway.
So far, what I see in my within my App Background Activity (General Settings, Login Items & Extensions), 3 entries for OCLP-Plus! It certainly come from my multiple tests, including one (dirty) working with both OCLP-Plus and OCLP Nightly 3.
Before bothering too much MakAsrock, I need to see if the dirty root is coming from my numerous tests (certainly yes).

This success is yours! Thank you very much! 

[kgp]

24 minutes ago, Jessy Lou said:

Many thanks dear KGP!

As I was looking forward to getting the outcome of my very quick tests, I couldn't resist any longer.

A: everything works as expected. I still have the same Sequoia before struggling with Tahoe! 

B: I guess you know already --> everything works! I couldn't believe when I entered my Wi-Fi pass... This works! . Thanks god, I didn't have to go to your point 8 you mentioned earlier.
To reply to your question: sound is also Ok, based on an early release of OCLP-Plus I was using, certainly from 3.1.8. I tested Ethernet: also Ok.
I did another test beside B: working with the CSR I'm using on Sequoia: 7F080000 instead of 03080000. OCLP-Plus is not complaining when launching with this CSR.

As for 😄 I'm going to take time for that. 1st I don't like having some unstable system... I did so many tests I don't know what is clean and what isn't. I keep my own documentation, therefore I need to do this fresh install anyway.
So far, what I see in my within my App Background Activity (General Settings, Login Items & Extensions), 3 entries for OCLP-Plus! It certainly come from my multiple tests, including one (dirty) working with both OCLP-Plus and OCLP Nightly 3.
Before bothering too much MakAsrock, I need to see if the dirty root is coming from my numerous tests (certainly yes).

This success is yours! Thank you very much! 

 

Glad to hear everything is working now 

Three entries for OCLP under “General Settings” → “Login Items & Extensions” are normal. Nothing to worry about.

All OCLP variants will warn you if a dirty root volume is detected and will not apply root patches in that state. In such cases, the root patches need to be reverted using any OCLP variant, followed by a reboot.

After rebooting, any of the OCLP variants should be able to apply the root patches properly without triggering the “dirty root volume” warning. If root patching succeeds, there is no need to worry about a dirty root volume, as OCLP would not apply any root patches on a dirty system volume.

[MakAsrock]

1 hour ago, Jessy Lou said:

@MakAsrock, I'm going to reinstall a fresh Tahoe 26.4 to restart the process. Then, I'm going to describe each step of my test, and I'm going to prepare the issue on your GitHub with my EFI folder, without forgetting to describe what does work on Sequoia. I might be able to do that during the weekend due to my daily work on Sequoia.

@KGP, let me take each of your points bellow:
1). For sure I did boot at each step (following OCLP-Plus is telling on the screen in addition to MakAsrock advices). As the root still seems dirty, I'm going to reinstall Tahoe to clean-up the current mess.
2). On Sequoia I work exclusively with OCLP 2.4.1. I'm using OCLP-Plus only on Tahoe.

3). I'm now working with your revised config.plist on which I moved up AMFIPass.kext to be placed before IOSkywalkFamily.kext, IO80211FamilyLegacy.kext, and IO80211FamilyLegacy.kext/Contents/PlugIns/AirPortBrcmNIC.kext. This is the 1st deviation to your revised config.plist.
4). As I boot from the same EFI partition thanks to your revised config.plist, I'm booting from the same OpenCore Boot Loader 1.0.7 on both Sequoia (15.7.5) and on Tahoe (26.4).

5). Thanks for the original package! I've now replaced the older IntelMausi 1.0.8 (dec '24) with the recent IntelMausiEthernet 3.0.0 (dec '25). Even if I'm rarely using LAN, I trust expert advices. . This is the 2nd and last deviation from your revised config.plist.

6). On Sequoia with OCLP 2.4.1, everything works for months. I'm now working with the revised config.plist (including the 2 deviations mentioned above). So far, the system works like a charm.
On Tahoe, I focus on using the latest release of OCLP-Plus which is now 3.2.1 (the first release I tested was 3.1.8). As I'm using same EFI, here is the list of kexts and releases I'm using in the exact same order as it is in the config.plist file:

1. Lilu.kext -> 1.7.2
2. VirtualSMC.kext -> 1.3.7
3. WhateverGreen.kext -> 1.7.0
4. AppleALC.kext -> 1.9.7
5. USBMap.kext (build for ASUS ROG Maximus XI Hero following Dortania guide) for MacPro7,1 SMBIOS
6. SMCProcessor.kext -> 1.3.3
7. SMCSuperIO.kext -> 1.3.3
8. IntelMausiEthernet.kext -> 3.0.0
9. RestrictEvents.kext -> 1.1.6 (to follow your advices when using MacPro7,1 in a previous chat, and to follow the "EFI-KGP-public-v.1.1.5-OCLP-Broadcom" EFI folder you're sharing also on another post, I'm using it to ensure Tahoe is running in best conditions).
10. AMFIPass.kext -> 1.4.1
11. IOSkywalkFamily.kext -> 1.0
12. IO80211FamilyLegacy.kext -> V1200.12.2b1
13. IO80211FamilyLegacy.kext/Contents/PlugIns/AirPortBrcmNIC.kext -> V1400.1.1

This is the list of added kexts.
As for com.apple.iokit.IOSkywalkFamily to block, I updated the MaxKernel to 25.99.99)

 

7). I'm dealing with a real BCM43602CS (I've been helped previous by you the this. At this time, I was cheated by the vendor... until I bought a real BCM: vendor as 0x14E4 and device as 0x43BA). Since November last year, on Sequoia I have AirDrop, AirPlay, Screen Sharing... working as with a real Mac. I don't have any Intel Wi-Fi!

 

Next step for me:

A). Reset NVRAM twice to test the brand new config.plist for Sequoia to run a few tests. For Sequoia CSR is 7F080000 for one particular app that needs this. I can confirm that so far this CSR allowed my to run OCLP 2.4.1 and a few previous releases with no issue at all. When running OCLP, it tells me about the last Root Patch, I don't have the dirty root in there.
B). Reset NVRAM twice to test the brand new config.plist for Tahoe with CSR as 03080000.
C). Reinstall from scratch Tahoe 26.4 to then use OCLP-Plus 3.2.1 and report the details as asked by MakAsrock.

 

Anyways: thank you both for your time.

At first glance, everything looks good.

However, the "dirty" root volume error must be corrected; otherwise, you won't be able to install patches for the root partition. This is usually accomplished by rolling back the patches and then rebooting the system.

If that doesn't help, try a clean installation. You can also try OCLP-Mod 3.1.9 or OCLP 3.0.0 Nightly (amphipassbeta version) to test without making changes to the EFI folder, or use them to undo root patches.

That said, I was planning to make a few important changes to your configuration, such as a USB port remapping kext, a patch to prevent forced partition encryption, and a few other minor tweaks.

But as you wish — you can certainly handle this yourself.

[kgp]

8 minutes ago, MakAsrock said:

At first glance, everything looks good.

However, the "dirty" root volume error must be corrected; otherwise, you won't be able to install patches for the root partition. This is usually accomplished by rolling back the patches and then rebooting the system.

If that doesn't help, try a clean installation. You can also try OCLP-Mod 3.1.9 or OCLP 3.0.0 Nightly (amphipassbeta version) to test without making changes to the EFI folder, or use them to undo root patches.

That said, I was planning to make a few important changes to your configuration, such as a USB port remapping kext, a patch to prevent forced partition encryption, and a few other minor tweaks.

But as you wish — you can certainly handle this yourself.

 

My dear friend,

His last reply was a bit ambiguous, but if he hadn’t successfully cleaned the dirty root volume by reverting the patches, he wouldn’t have been able to reinstall OCLP and get Wi-Fi and audio working under Tahoe.

That said, feel free to further refine his EFI folder if you think additional improvements are still necessary.

 

Looks like my part here is done — over and out 🙂

All the best, 

KGP 🤗

   

Edited May 5 by kgp

[Jessy Lou]

I confirm despite the dirty root, I was able to reapply root patches successfully, having both sound and Wi-Fi working well.

I still schedule to reinstall on fresh install to avoid keeping dirty things coming ONLY from my numerous (and undocumented) tests.

Thanks for the information about the 3 entries for OCLP under “General Settings” → “Login Items & Extensions” that are normal. I'm therefore stoping diving in this direction.

Next step: reinstall to keep MakAsrock posted as he advised me to.

So far: thanks again KGP for this huge step forward for me!

[kgp]

21 minutes ago, Jessy Lou said:

I confirm despite the dirty root, I was able to reapply root patches successfully, having both sound and Wi-Fi working well.

I still schedule to reinstall on fresh install to avoid keeping dirty things coming ONLY from my numerous (and undocumented) tests.

Thanks for the information about the 3 entries for OCLP under “General Settings” → “Login Items & Extensions” that are normal. I'm therefore stoping diving in this direction.

Next step: reinstall to keep MakAsrock posted as he advised me to.

So far: thanks again KGP for this huge step forward for me!

 

If your root volume were still dirty, you wouldn’t have been able to reapply the root patches, and OCLP would have warned you again that root patches cannot be applied due to a dirty system volume — so I wouldn’t worry too much about it at this point 😉

The final game changer may have been IntelMausiEthernet.kext 3.0.0. There could be issues with the com.apple.iokit.IOSkywalkFamily replacement when using IntelMausi.kext 1.0.8 😉

Anyway, glad everything is working now. 👍

And now really — over and out        

 

Edited May 5 by kgp

[Jessy Lou]

I'm also convinced that, in addition to your clean config.plist, that IntelMausiEthernet.kext remains the game changer.

Thanks

[Jessy Lou]

Dear MakAsrock,

I just opened the issue on GitHub with the zipped EFI folder, with details on tests I just did from a fresh Tahoe 26.4.1 install.
I'm keeping other screen shots when OCLP-Plus is patching just in case. But the process itself does work 100% perfect. The only minor issue is the 'dirty root volume'.

I just noticed that the startup disk shall be the one OCLP-Plus runs.
I didn't notice such issue when using OCLP 2.4.0 on Sequoia.

On Sequoia, I'm not using OCLP-Plus at all, keeping OCLP 2.4.0.

Thanks to KGP, I now have only one EFI!

Good luck for your investigations.
Once again, this is a minor issue, because OCLP-Plus 3.2.1 is doing the job. Even when I revert, I can apply the root patches again with full success.

Anyway: thank you for OCLP-Plus! 

 

[MakAsrock]

On 5/8/2026 at 2:44 PM, Jessy Lou said:

Dear MakAsrock,

I just opened the issue on GitHub with the zipped EFI folder, with details on tests I just did from a fresh Tahoe 26.4.1 install.
I'm keeping other screen shots when OCLP-Plus is patching just in case. But the process itself does work 100% perfect. The only minor issue is the 'dirty root volume'.

I just noticed that the startup disk shall be the one OCLP-Plus runs.
I didn't notice such issue when using OCLP 2.4.0 on Sequoia.

On Sequoia, I'm not using OCLP-Plus at all, keeping OCLP 2.4.0.

Thanks to KGP, I now have only one EFI!

Good luck for your investigations.
Once again, this is a minor issue, because OCLP-Plus 3.2.1 is doing the job. Even when I revert, I can apply the root patches again with full success.

Anyway: thank you for OCLP-Plus! 

 

Hello, my friend.
I looked at your EFI and I have no remark on it, except that I would place AMFIPass.kext, IOSkywalkFamily.kext, IO80211FamilyLegacy.kext and IO80211FamilyLegacy.kext/Contents/PlugIns/AirPortBrcmNIC.kext immediately after AppleALC.kext.

EFI-Fixed.zip

1. The test showed that everything is fine.

Dirty root volume is just a term. It means that root patches have already been applied (successfully or not) and for repeat required to revert them.

Suggest your own version of the warning bat it should not be longer than the previous one.

2. Test B Test B

It showed the same result because the program determined that the minimum conditions were met.

3. Test C

Same as Test A, except for the audio patch, which isn't required anywhere except in the Tahoe.

The only error is here:

Subprocess failed. Command: ['/Library/PrivilegedHelperTools/com.dortania.opencore-legacy-patcher.privileged-helper', 'Isbin/mount, '-o', 'nobrowse', '-t', 'apfs', '/dev/
disk11s2', '/System/Volumes/Update/mnt1']
Return Code: 66
Standard Output:
mount: /System/Volumes/Update/mnt1: invalid file
system.
Standard Error:
None

It's possible that com.dortania.opencore-legacy-patcher.privileged-helper was already in the destination folder. However, this isn't fatal.
When I have time, I'll check it on my RIG.

Hugs,
MakAsrock 🤗

Edited May 9 by MakAsrock

[MakAsrock]

OCLP-Plus 3.2.2 — Change Log

📸 Screenshots

This release fixes a serious bug.

 

Edited May 11 by MakAsrock

[Jessy Lou]

Well, my dear friend MakAsrock, you just did it!

With this new release 3.2.2, reverting and reapplying the Root Patches works just great even on my exotic configuration (KGP knows where I'm coming from with my multiples EFI folders 😁).

 

 I can't stop saying MANY THANKS to you MakAsrock for this great valuable tool, as I can't stop THANKING VERY MUCH you KGP to your great support on my EFI nightmares. . 

Edited May 10 by Jessy Lou