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

[LockDown]

A bit OT... Does cloning breaks OCLP?

[kgp]

6 hours ago, LockDown said:

A bit OT... Does cloning breaks OCLP?

 

I would recommend reverting the root patches before cloning and applying them again after the cloning process.

 

I cloned my Sequoia system disk once and had to reinstall the root patches afterward anyway.

 

I’m not sure what you mean exactly by “cloning”, but in my case I simply used:

 

sudo asr restore --source /Volumes/Tahoe --target /Volumes/NVMeTahoe --erase --noprompt

 

Carbon Copy Cloner (CCC) can no longer be used to create bootable system disk clones.

[miliuco]

@LockDown  @MakAsrock

 

I've done a few clones without loosing OCLP root patch in this way:

• SuperDuper! beta Tahoe version
• run on Tahoe
• cloning a root patched Sonoma disk to a different disk
• new disk boots fine with enabled root patch.

Don't know if it's valid for Tahoe too because my Tahoe disk is not root patched (I use AX210 in this disk).

[Thebes Knossos]

Still same situation for my Haswell, only Audio is ready. No Wifi legacy nor iGPU metal. This version seems more complex...

Edited January 16 by Thebes Knossos

[kgp]

2 minutes ago, Thebes Knossos said:

Still same situation for my Haswell, only Audio seems ready. No Wifi legacy nor iGPU metal. This version seems more complex...

 

What is your Wi-Fi card? Neither OCLP 3.0.0 Nightly nor OCLP-Mod 3.1.3 contain any GPU or iGPU patches! However Wi-Fi should work depending on the Wi-Fi interface at your deposit.   

[Thebes Knossos]

My Wifi is an Atheros chip, patched correctly with OCLP 2.41 up to (and including) Sequoia, I don't use Bluetooth. I think metallib is a real problem.

[deeveedee]

is it possible that OCLP 3.0.0 Experimental doesn't patch Legacy Wi-Fi (only patches Modern Wi-Fi).  Sorry for the remedial question, but I have not inspected OCLP 3.0.0 Experimental source.

[kgp]

59 minutes ago, Thebes Knossos said:

My Wifi is an Atheros chip, patched correctly with OCLP 2.41 up to (and including) Sequoia, I don't use Bluetooth. I think metallib is a real problem.

I have no experience with Atheros Wi-Fi chipsets and I don’t know whether it would work with OCLP 3.0.0. The only thing I could offer is to inspect your EFI-folder to see if everything is properly set for OCLP 3.0.0 Nightly or OCLP-Mod 3.1.3. I don’t know if there is any sense for such investigation without GPU or iGPU acceleration. 

[Thebes Knossos]

My EFI is common from Big Sur to Tahoe and Tahoe is booting correctly.

For Legacy Wifi I use IOName spoofing in device properties.

If necessary I can provide my EFI, not sure it can help for this patching

Detection is OK, then:

 

I don't know where to post for this issue (Main OCLP or Labomac, I have a Github account) 

[kgp]

1 hour ago, Thebes Knossos said:

My EFI is common from Big Sur to Tahoe and Tahoe is booting correctly.

For Legacy Wifi I use IOName spoofing in device properties.

If necessary I can provide my EFI, not sure it can help for this patching

Detection is OK, then:

 

I don't know where to post for this issue (Main OCLP or Labomac, I have a Github account) 

 

Apparently the code is still missing a library for your approach. You will have to wait for the official release of OCLP 3.0.0, which will hopefully also have iGPU support. 

[Thebes Knossos]

I agree with you, I think Wi-Fi should be completed with modern Wi-Fi at the title of thread.

Edit:

I've asked question here : https://github.com/laobamac/OCLP-Mod/issues/65

Edited January 14 by Thebes Knossos

[Thebes Knossos]

I've got a response from Labomac, no Wi-Fi legacy at the moment.

[dREAmCaTCHeR]

On 1/6/2026 at 10:16 AM, KGP-iMacPro said:

Intel AX210 (AirportItlwm) vs Broadcom BCM943602CDP under macOS Tahoe

 

Tested with OCLP 3.0.0 Nightly and OCLP-Mod 3.1.2

 

After extensive testing of an Intel AX210 using AirportItlwm together with OCLP 3.0.0 Nightly / OCLP-Mod 3.1.2, I observed some functional differences compared to a Broadcom Wi-Fi card. All tests were performed on a stable Hackintosh system where Broadcom Wi-Fi works reliably.

 

1) Hackintosh is not always shown as “Online” in Find My

Observation:

On other Apple devices (iPhone, iPad, MacBook Pro), the Hackintosh does not always appear as online in the Find My app when using Intel AX210.

Technical note:

Find My presence seems to rely on Apple-specific AirPort firmware behavior. Broadcom cards implement this fully.

Intel AX210 (AirportItlwm), even with Broadcom spoofing, does not appear to provide the same integration, so Find My status is inconsistent.

 

2) Hidden Network UI behavior differs

Observation:

With Broadcom, macOS sometimes displays the network as “Hidden Network”.

With Intel AX210 + AirportItlwm, the network shows its real SSID, even if it is broadcast.

Technical note:

Broadcom firmware may report the network as hidden based on Apple-specific heuristics.

AirportItlwm reports only the actual SSID.

Conclusion:

Connectivity works with both cards.

The difference seems purely cosmetic / UI-level.

 

3) Instant Wake on Sleep

Observation:

With Intel AX210 installed, the system sometimes wakes immediately after entering sleep.

The issue disappears when the AX210 is physically removed or replaced with Broadcom.

Technical note:

macOS expects Wi-Fi hardware to enter low-power sleep states (D3cold) and mask wake events.

Broadcom cards seem to handle this correctly; Intel AX210 appears to generate spurious wake signals.

Disabling Wi-Fi or adjusting pmset does not reliably prevent the wake.

Conclusion:

Instant Wake seems to be a hardware/firmware limitation of Intel AX210 under macOS, based on my tests. Other users may experience different behavior depending on system configuration.

 

Based on my testing, Broadcom currently provides the most reliable macOS integration in terms of Find My, UI behavior, and sleep/wake.
Other users are welcome to share their experiences, as setups may vary.

 

EDIT: Point 2.) is now obsolete: “Hidden Network” also works with the AX210.

 

 

 

How can I get the AX210 to work on Sequoia manually without Root patching? Is it possible to do the tasks manually without install the mod?

Edited January 18 by dREAmCaTCHeR

[deeveedee]

@dREAmCaTCHeR I use itlwm (not airportitlwm).  It requires no root patches and works well in Tahoe.

[kgp]

Thanks, @deeveedee, for answering the question.

@dREAmCaTCHeR: yes, itlwm.kext together with HeliPort.app works not only under Tahoe but also under Sequoia without any root patching.

That said, this solution exposes Wi-Fi as a virtual Ethernet interface, so AWDL and native Apple Wi-Fi features are not available.

 

 

Edited January 18 by KGP-iMacPro

[Allan]

Hello everyone! 

 

Good news: the topic has been reopened! Now the project started by users @KGP-iMacPro and @MakAsrock can move forward again.

 

As a brief announcement, both of these users have tried to reach out to the main developers involved in this project such as DhinakG, but so far, they haven’t received any replies. Hopefully, if we do get a response soon, it will be a positive one.

 

With that in mind, please avoid making false accusations such as project theft or copyright infringement.

 

So, without further delay, let’s keep enjoying ourselves and learning from one another!  

[MakAsrock]

16 hours ago, Allan said:

Hello everyone! 

 

Good news: the topic has been reopened! Now the project started by users @KGP-iMacPro and @MakAsrock can move forward again.

 

As a brief announcement, both of these users have tried to reach out to the main developers involved in this project such as DhinakG, but so far, they haven’t received any replies. Hopefully, if we do get a response soon, it will be a positive one.

 

With that in mind, please avoid making false accusations such as project theft or copyright infringement.

 

So, without further delay, let’s keep enjoying ourselves and learning from one another!  

Everything is fine, my friends. My fork is back online. I don't want to criticize anyone anymore, but I'll simply collect statistics as best I can and make improvements if I can. 🙂

[Max.1974]

On 1/18/2026 at 4:01 AM, KGP-iMacPro said:

Thanks, @deeveedee, for answering the question.

@dREAmCaTCHeR: yes, itlwm.kext together with HeliPort.app works not only under Tahoe but also under Sequoia without any root patching.

That said, this solution exposes Wi-Fi as a virtual Ethernet interface, so AWDL and native Apple Wi-Fi features are not available.

 

 

 

I really appreciate all the work from the coders and developers. Even without any patches, HeliPort works with itlwm.kext 

 

 

[MakAsrock]

They say that OpenCore Legacy Patcher Version 3.0.0 (Nightly), OCLP 3.0.0 Nightly, and OCLP-Mod 3.1.4 are deprecated. ☹️

[MakAsrock]

I am pleased to present you the 3.1.6 release of Tahoe patchset.
Added a toggle to the 'Root Patches' sector to disable the 'Modern Audio' patch for AppleHDA restoration.
This prevents unrecoverable kernel panics in macOS Tahoe without an installed KDK.

Corrected the alignment.
It was like this:

 

And it became like this:

 

Edited February 22 by MakAsrock

[kgp]

Post 1 of this thread has been completely revised and restructured.

 

Due to the continued development of the Tahoe patchset and the release of OCLP 3.1.6, parts of the original information from late 2025 were outdated and potentially confusing.
 

The new Post 1 now clearly separates the preserved OCLP 3.0.0 Nightly reference snapshot from the actively developed patcher by YBronst (MakAsrock) and explains which one should be used depending on the macOS Tahoe version.

 

This update does not introduce new patches or change the behaviour of the patchset itself.

It is a documentation clarification and a reorganisation of the referenced resources.

 

Please read the updated Post 1 carefully before asking questions or applying root patches.

 

 

Good luck and enjoy! 

 

KGP

 

[Oyecomova]

OpenCore Legacy Patcher 3.1.6 didn't work. I had to boot from another disk with Sequoia and apply the following to recover Tahoe:

sudo mount -uw "/Volumes/Macintosh HD"
and then
sudo bless --mount "/Volumes/Macintosh HD" --bootefi --last-sealed-snapshot

[MakAsrock]

On 2/20/2026 at 6:05 PM, Oyecomova said:

OpenCore Legacy Patcher 3.1.6 didn't work. I had to boot from another disk with Sequoia and apply the following to recover Tahoe:

sudo mount -uw "/Volumes/Macintosh HD"
and then
sudo bless --mount "/Volumes/Macintosh HD" --bootefi --last-sealed-snapshot

It doesn't work, so why is everything OK with my RIG?
I need precise information:

What version of macOS 26.3 was installed?
What settings were made to the 3.1.6 Tahoe patchset?
Was the KDK for macOS 26.3 (25D5087f) installed?
Was the boot argument AMFI=80 included in the config?
Was there Internet access while running 3.1.6 Tahoe patchset?
Once I hear all this from you, I'm sure I can fix the issues. 
Cheers,
MakAsrock. 😉

Edited February 21 by MakAsrock

[MakAsrock]

A new button has been added to the help menu to download the kernel debug kit.

Edited February 22 by MakAsrock

[carlo_67]

On 2/17/2026 at 2:27 PM, MakAsrock said:

and OCLP-Mod 3.1.4 are deprecated. ☹️

And who says this? OCLP-MOD 3.1.4 works great with 26.2/3 and already has the features to download the KDK. We just have to wait for the 26.4 beta release.