Experimental Fork of OCLP 3.0.0 Nightly – modern Wi-Fi, AWDL and AppleHDA Fully Working under Tahoe

[tikizondo94]

4 hours ago, miliuco said:

Doing exactly what @KGP-iMacPro describes in the first post, I have working wifi with the Fenvi T919 on Tahoe 26.1.

Performance seems to be the same of Sequoia, Sonoma or Ventura.

It's surprising how easy it's been.

Tahoe's start-up times haven't changed.

 

EDIT: -amfipassbeta with AMFIPass.kext doesn't work, kernel panic at boot.

 

 

Anything else specific you did to get your Fenvi T919 working? We have similar setups. Still after this branch of OCLP "No wifi". 

[tikizondo94]

7 minutes ago, tikizondo94 said:

Anything else specific you did to get your Fenvi T919 working? We have similar setups. Still after this branch of OCLP "No wifi". 

Disregard.. Min Max kernel was set wrong on my part. All working normal. Brilliant! 

[HyperX7]

Broadcom BCM94331CD 802.11a/b/g WiFi card + Bluetooth 4.0 for Apple A1418 A1419 (0x14E4 0x4331)

 

This wifi/bt card doesn't work with this patch. In addition Without "amfi=0x80" bootarg the system doesn't boot after patch.

 

Edited December 4, 2025 by HyperX7

[LockDown]

4 hours ago, fabiosun said:

In the meantime, I repeat my question... is anyone trying out the Clover bootloader (i mean with this OCLP)?

 

Aye aye Sir.. No issue here

[LockDown]

15 hours ago, KGP-iMacPro said:

Prerequisites  and Setup:

3.) AppleVTD disabled, i.e. DisableIOMapper=true

 

14 hours ago, LockDown said:

i dont need to disable AppleVTD. 

 

14 hours ago, KGP-iMacPro said:

What might be the difference in our settings?

 

12 hours ago, LockDown said:

I have to verify my setting in DisableIOMapper tomorrow, but pretty sure VT-D is enabled in bios.

 

VT-D=enabled in Bios. DisableIOMapper=true.

@KGP-iMacPro Probably successfully booted with these settings due to DisableIOMapper override the VT-D value in bios 🤔

Edited December 5, 2025 by LockDown

[chris1111]

I have fork this project for testing, then Building OpenCore-Patcher.pkg from CLI

It Work on HP Elitebook 840 G4 with a BCM94360NG Wi-Fi and Bluetooth Card

Big Thanks to Hoang Hong Quan lzhoang2801

 

Testing and working on macos Tahoe 26.1 Beta (25B5042k)

 

 

 

 

Edited December 5, 2025 by chris1111

[kgp]

1 hour ago, LockDown said:

 

 

 

 

VT-D=enabled in Bios. DisableIOMapper=true.

@KGP-iMacPro Probably successfully booted with these settings due to DisableIOMapper override the VT-D value in bios 🤔

 

If I properly understand what you are writing, we have the same settings:  VT-D=enabled in Bios. DisableIOMapper=true. In my originating post I just state: AppleVTD disabled, i.e. DisableIOMapper=true

[chris1111]

 

Updating to Tahoe 26.2 (25C56) ✌️

 

 

[XanthraX]

7 hours ago, HyperX7 said:

Broadcom BCM94331CD 802.11a/b/g WiFi card + Bluetooth 4.0 for Apple A1418 A1419 (0x14E4 0x4331)

 

This wifi/bt card doesn't work with this patch. In addition Without "amfi=0x80" bootarg the system doesn't boot after patch.

 

Damn it! This was the culprit. The problem was between my chair and my screen. I forgot to add "amfi=0x80" bootarg. Now it working flawlessly. Thank you @KGP-iMacPro and all devs of Dortania.

[fabiosun]

Also clover is working well with this OCLP:

https://macos86.it/topic/6463-oclp-il-wi-fi-è-tornato-in-macos-sonoma/?do=findComment&comment=157541

Thanks @Anto65 for testing

 

On my AMD No wifi for now but researching mode is on!

 

[deeveedee]

I'm using Intel Wi-Fi on my HackBookPro6,2, so it only needs audio patches.  I created an experimental Tahoe 26.2 RC1 volume and applied AppleHDA post-install patch with lzhoang2801's Experimental Patcher.  Since I only applied audio patches, my config is as follows:

• csr-active-config = <03080000>
• AMFIPass.kext 1.4.1 (No need for boot-arg amfi=0x80, since I'm not applying Wi-Fi patches)
• Open Core 1.0.6
• Tahoe 26.2 (25C56)
• Multi-booting with grub: Windows 11, Ubuntu 24.04, macOS Monterey, Sequoia, Tahoe - with grub, SIP settings are different for each macOS depending on my testing needs (e.g. SIP fully enabled for Sequoia, but partially disabled for Tahoe / patches)

Detected need for Audio Patching

Spoiler

 

Download KDK

Spoiler

 

Thank you KGP-iMacPro for renaming this thread and inserting warnings to avoid confusion with the official OCLP.  Thank you lzhoang2801 for your effort and for modifying the labeling and adding a warning to your GitHub repo to make it clear that this is not OCLP from the original Devs.

 

Spoiler

 

EDIT: After testing, I have completely removed the patcher and patches from my hack by doing the following:

• In Tahoe
  • run OpenCore-Patcher-Uninstaller.pkg
  • Remove OCLP .plist from /Library/LaunchDaemons and /Library/LaunchAgents
  • Remove OCLP .plist from /Volumes/'Tahoe - Data'/Users/Shared
  • Disable AMFIPass.kext
• Boot Tahoe Recovery and do the following in terminal:
  • mount -uw /VolumesTahoeTest (where TahoeTest is my test macOS Volume)
  • bless --mount /Volumes/TahoeTest --bootefi --last-sealed-snapshot
  • rm -rf /Volumes/TahoeTest/System/Library/Extensions/AppleHDA.kext
• Boot Tahoe and re-install VoodooHDA.kext in /Library/Extensions (if using VoodooHDA for audio)
• Edit OC/config.plist to restore SIP csr-active-config to <01000000> (if using VoodooHDA for audio)

Edited December 10, 2025 by deeveedee

[fabiosun]

2 hours ago, MakAsrock said:

Unfortunately, on Mac OS Tahoe, my BCM4360 802.11ac Dual Band Wireless Network Adapter (0x14E40x43A0 Broadcom Inc.) did not work.
.

it is weird i have the same of yours card ( it seems)

 

 

and it works well

 

I had to modify a kernel patches useful for AMD system

Edited December 5, 2025 by fabiosun
Add images

[kgp]

2 hours ago, MakAsrock said:

Unfortunately, on Mac OS Tahoe, my BCM4360 802.11ac Dual Band Wireless Network Adapter (0x14E40x43A0 Broadcom Inc.) did not work.
.

 

If you want, you can upload your EFI-Folder, thus we can have a look to it and likely help if there is some issue. 😉  

[sam298]

Including amfipass.kext only causes panic during boot. Use only amfi=0x80 boot arg.

OP instructions need to be fixed. Even for sequoia and earlier OS, the options are either amfi=0x80 or including amfipass.kext but not both. 

[deeveedee]

@sam298 You are correct for patching Wi-Fi.  When patching only AppleHDA (not Wi-Fi), only AMFIPass.kext is required (not boot-arg amfi=0x80).  The boot-arg amfi=0x80 (disabling AMFI) is temporary until the official OCLP is released or a modified version of AMFIPass.kext is provided for this Experimental patcher.

Edited December 5, 2025 by deeveedee

[kgp]

34 minutes ago, sam298 said:

Including amfipass.kext only causes panic during boot. Use only amfi=0x80 boot arg.

OP instructions need to be fixed. Even for sequoia and earlier OS, the options are either amfi=0x80 or including amfipass.kext but not both. 

 

I can fix this, but I use AMFIPass.kext 1.4.1 (enabled) and boot-arg amfi=0x80 and everything works without issues

[fabiosun]

4 minutes ago, KGP-iMacPro said:

 

I can fix this, but I use AMFIPass.kext 1.4.1 (enabled) and boot-arg amfi=0x80 and everything works without issues

Yep the same here..but i think you can avoid to use amfipass.kext till when devs will fix it for tahoe use

 

Edited December 5, 2025 by fabiosun

[deeveedee]

@KGP-iMacPro Even if you're not experiencing the panic, AMFIPass.kext is not needed when amfi=0x80 boot-arg is added.

[kgp]

15 minutes ago, deeveedee said:

@KGP-iMacPro Even if you're not experiencing the panic, AMFIPass.kext is not needed when amfi=0x80 boot-arg is added.

 

Yes that's just obvious but the additional AMFIPass.kext did not harm either .. Just disabled AMFIPass.kext without any change regarding the functionality of my system. For the sake of consistency, I am going to change the OP.

Edited December 5, 2025 by KGP-iMacPro

[laobamac_yyds]

Maybe it's not AMFIPass that is invalid, just because AMFIPass does not include all self-signed binary documents in the exemption list？

 

It seems that it just intercepts the AMFIGetLocalSigningPublicKey method and uses the public key corresponding to the self-signed certificate to pass the AMFI verification.

But AMFIPass is only built-in with the public key of Dortania Software Signing.

 

This is a very interesting Lilu plug-in... I especially want to learn how it bypasses AMFI. I don't know if @dhinakg will open source his code, haha.

Edited December 5, 2025 by laobamac_yyds

[kgp]

9 minutes ago, laobamac_yyds said:

Maybe it's not AMFIPass that is invalid, just because AMFIPass does not include all self-signed binary documents in the exemption list？

 

It seems that it just intercepts the AMFIGetLocalSigningPublicKey method and uses the public key corresponding to the self-signed certificate to pass the AMFI verification.

But AMFIPass is only built-in with the public key of Dortania Software Signing.

 

This is a very interesting Lilu plug-in... I especially want to learn how it bypasses AMFI. I don't know if @dhinakg will open source his code, haha.

 

Moreover Izhoang2801 clearly states now in his repository: These builds are unsigned (which is why you may need to use the amfi=0x80 bootarg instead of the AMFIPasskext). 

Edited December 5, 2025 by KGP-iMacPro

[deeveedee]

Happy to see that Izhoang2801 is reading this thread 😄

[fabiosun]

Maybe i misunderstood @MakAsrock i tought you used that build to have it working on your system as many of us

 

Sorry

[fabiosun]

6 hours ago, MakAsrock said:

Unfortunately, on Mac OS Tahoe, my BCM4360 802.11ac Dual Band Wireless Network Adapter (0x14E40x43A0 Broadcom Inc.) did not work.
.

i am referring to this

if it is working in my rig...could work also in all rigs

 

[chris1111]

36 minutes ago, MakAsrock said:

All current EFI folders are in my profile repository on GitHub. Wi-Fi doesn't work because this fork isn't from Dortania at all. I used the OCLP 3.0.0 nightly build from here. By the way, if anyone needs it, hurry up to download (It does not require amfi=0x80 boot-arg).

what is the exact model wifi card brand you have?