OCLP-Mod Release/Issue/Discussion

[spakk]

1 hour ago, laobamac_yyds said:

@spakkPlease download the latest Pre-release and install OCLP-Mod.pkg

Not in Github Actions.

Hi laobamac_yyds,

do you have a link to the current OCLP‑Mod ver.3 for me?

[laobamac_yyds]

10 minutes ago, spakk said:

Hi laobamac_yyds,

do you have a link to the current OCLP‑Mod ver.3 for me?

https://github.com/laobamac/OCLP-Mod/releases/download/push-e02886b6697775a95b14dae10e16684c6bdb9c24/OCLP-Mod.pkg

[deeveedee]

@laobamac_yyds Continuing from here ... 

 

I repeated my previous test with the following three kernel patches enabled and USB2 continued to work without issues.  Just to clarify, I am applying your kernel patches on a hack that has fewer than 15 USB ports in its USB port map, so it does not need to override the USB port limit.  I hope this helps.

 

• __ZN16AppleUSBHostPort15setPortLocationEv
• __ZN12AppleUSBXHCI11createPortsEv
• __ZN16AppleUSBHostPort14portDictionaryEj16tUSBHostPortTypej

[laobamac_yyds]

Just now, deeveedee said:

@laobamac_yyds Continuing from here ... 

 

I repeated my previous test with the following three kernel patches enabled and USB2 continued to work without issues.  Just to clarify, I am applying your kernel patches on a hack that has fewer than 15 USB ports in its USB port map, so it does not need to override the USB port limit.  I hope this helps.

 

• __ZN16AppleUSBHostPort15setPortLocationEv
• __ZN12AppleUSBXHCI11createPortsEv
• __ZN16AppleUSBHostPort14portDictionaryEj16tUSBHostPortTypej

tyvm,these information is helpful.

[schrup21]

Hi @laobamac_yyds It appears that the root patch (AppleHDA) with OCLP-Mod 3.0 in 26.2 Beta 3 is causing a graphics glitch in the weather app and the AppStore. 

Serveral users in the German Hackintosh-Formum have reported this and I can confirm it - see my screenshot from the AppStore.app: 

Spoiler

 

Could you please look into this?

 

Thanks!

 

Edit: without the Root Patch:

Spoiler

 

Edited November 20, 2025 by schrup21

[laobamac_yyds]

@eSaF@schrup21

Hi, I just finished school.

 

This problem cannot be solved temporarily because it was not caused by us.

 

This is because Apple has not released the KDK for 25C5048a, and the current matching strategy automatically installs the KDK for 25C5037j.The KDK of 26.2B2 is not fully compatible with 26.2B3.

 

The only thing we can do is wait.

[mnfesq]

I haven't seen anyone raise the issue I'm having with OCLP-Mod.  I'm not exactly sure what the problem is but I can only describe it as a loss of USB function due to a USB kext not loading (I think).  Here's what I'm talking about.

 

Here's what my USB in System Information looks like without the USB patch in OCLP-Mod.

 

, 

 

Of course, I don't have working sound or USB WiFi but I am able to mount my iPhone/iPad to my laptop.  When I apply the OCLP-Mod USB patch, this is what I get:

 

 

I get some USB function.  My internal camera works, I can mount Flash drives and my USB WiFi dongle works.  But I can't mount any Apple devices (but they will charge their batteries via USB.). Am I doing something wrong or is this the patch not working well with my hardware?

[deeveedee]

1 hour ago, mnfesq said:

I haven't seen anyone raise the issue I'm having with OCLP-Mod. ...But I can't mount any Apple devices (but they will charge their batteries via USB.). Am I doing something wrong or is this the patch not working well with my hardware?

 

EDIT: Sorry if I'm confused, but I keep re-reading your post and want to clarify...  Are you saying that when using macOS Tahoe without OCLP-Mod patches, you can mount USB-connected Apple Devices, but you can no longer mount the same USB-connected Apple Devices after installing OCLP-Mod patches?

Edited November 21, 2025 by deeveedee

[mnfesq]

4 hours ago, deeveedee said:

 

EDIT: Sorry if I'm confused, but I keep re-reading your post and want to clarify...  Are you saying that when using macOS Tahoe without OCLP-Mod patches, you can mount USB-connected Apple Devices, but you can no longer mount the same USB-connected Apple Devices after installing OCLP-Mod patches?

 

Yes, exactly.

[laobamac_yyds]

@mnfesq

Hi, my friend. If you install the old USB patch of OCLP-Mod, it will indeed cause the inability to connect to devices such as iPhone, and the system information will no longer display the device tree normally, but "Other Bus".

 

I still haven't found a better solution (because if you want to support USB wireless network cards, you must downgrade the USB-related system extension).

 

Remarks: The old version of the USB patch of OCLP-Mod is only to repair the USB wireless network card on macOS Tahoe. If you don't use it for this purpose, you don't need to install this patch.

[mnfesq]

2 hours ago, laobamac_yyds said:

@mnfesq

Hi, my friend. If you install the old USB patch of OCLP-Mod, it will indeed cause the inability to connect to devices such as iPhone, and the system information will no longer display the device tree normally, but "Other Bus".

 

I still haven't found a better solution (because if you want to support USB wireless network cards, you must downgrade the USB-related system extension).

 

Remarks: The old version of the USB patch of OCLP-Mod is only to repair the USB wireless network card on macOS Tahoe. If you don't use it for this purpose, you don't need to install this patch.

 

Thank you for your reply.  Since I have a laptop, I prefer to use WiFi to Ethernet for networking so I will continue to use the OCLP-Mod USB patch until a solution is found for my Broadcom internal WiFi card.  In the meantime, it's good to know that all I need to do to connect my iPhone to my laptop in order to change the music I have stored on my phone is to revert the patch. I was tearing out the little hair I have left on my head trying to figure out how to connect my iPhone to my laptop. 

[asdfghjklzxcvbnm]

Can you make intel wifi work on tahoe (airportitlwm) with the new oclp mod?

[deeveedee]

@asdfghjklzxcvbnm Intel Wi-Fi works in Tahoe with itlwm and Heliport.  I need to manually start Heliport after login to Tahoe, but other than that, it works without issues (within the known limitation of Intel Wi-Fi running on macOS).

[asdfghjklzxcvbnm]

moreover the new oclp mod seems to have introduced a display bug in some apple apps

[kgp]

@laobamac_yyds, my friend!

 

It seems that OCLP-Mod 3.0.0 has disappeared from your repository. At the moment, OCLP-Mod 2.6.7 is listed first, followed by some pre-release builds. For clarity, it would be very helpful if the pre-built version 3.0.0 for macOS Tahoe could be listed at the top of the repository — and clearly labeled as such — followed by version 2.6.7.

 

 

Could you please confirm this and clearly indicate in your repository whether these are indeed the pre-release builds of version 3.0.0 for macOS Tahoe? This would help users immediately identify the correct pre-release.

 

As always, many thanks for any clarification and help in this issue. 👍

 

All the best,

 

KGP

Edited November 24, 2025 by KGP-iMacPro

[Matgen84]

14 hours ago, deeveedee said:

@asdfghjklzxcvbnm Intel Wi-Fi works in Tahoe with itlwm and Heliport.  I need to manually start Heliport after login to Tahoe, but other than that, it works without issues (within the known limitation of Intel Wi-Fi running on macOS).

 

Hi my dear friend @deeveedee I also use Heliport with my Intel Wifi card on Tahoe. To avoid manual start, I add  the app in System Setting / Open at launch session. Sorry for my poor English.

Below screenshot from Sequoia, the settings is the same on Tahoe of course.
 

Spoiler

 

[miliuco]

@KGP-iMacPro

I guess is the pre-release with the long number.

[deeveedee]

1 hour ago, Matgen84 said:

..  I also use Heliport with my Intel Wifi card on Tahoe. To avoid manual start, I add  the app in System Setting / Open at launch session...

 

That works!  Thank you!  (Your English is excellent - better than mine )

 

EDIT: @Matgen84 I had only tried enabling "Launch at Login" from within the Heliport 1.5.0 menu.  Your solution works perfectly.  Thank you again.

Edited November 24, 2025 by deeveedee

[kgp]

21 minutes ago, miliuco said:

@KGP-iMacPro

I guess is the pre-release with the long number.

 

@miliuco, yes, I agree. However, I still believe it would be much more helpful for less experienced users if the pre-release of OCLP-Mod 3.0.0 had a clear entry in the repository, rather than being almost hidden under that long-number entry after version 2.6.7 (latest). As it stands, many users end up downloading version 2.6.7 instead.

Edited November 24, 2025 by KGP-iMacPro

[Matgen84]

@KGP-iMacPro @miliuco

Pre-Release with long number come from main branch (it is not pre-release 3.0.0). It refers to the yesterday commit 1e26f61. Just my opinion, this pre-release was published by mistake at the same time as release 2.6.7.

See screenshot below
 

Spoiler

 

[kgp]

47 minutes ago, Matgen84 said:

@KGP-iMacPro @miliuco

Pre-Release with long number come from main branch (it is not pre-release 3.0.0). It refers to the yesterday commit 1e26f61. Just my opinion, this pre-release was published by mistake at the same time as release 2.6.7.

See screenshot below
 

  Reveal hidden contents

 

 

So, did OCLP-Mod 3.0.0 just disappear? 🤔 I think it’s better to wait for @laobamac_yyds's answer instead of speculating. Interestingly, both version 2.6.7 and the pre-release seem to have the same file size, which supports your assumption. 👍

Edited November 24, 2025 by KGP-iMacPro

[deeveedee]

There are issues with GitHub.  If there are any unexpected changes, it could be related to the GitHub problems which are currently being assessed.

 

[laobamac_yyds]

6 hours ago, KGP-iMacPro said:

@laobamac_yyds, my friend!

 

It seems that OCLP-Mod 3.0.0 has disappeared from your repository. At the moment, OCLP-Mod 2.6.7 is listed first, followed by some pre-release builds. For clarity, it would be very helpful if the pre-built version 3.0.0 for macOS Tahoe could be listed at the top of the repository — and clearly labeled as such — followed by version 2.6.7.

 

 

Could you please confirm this and clearly indicate in your repository whether these are indeed the pre-release builds of version 3.0.0 for macOS Tahoe? This would help users immediately identify the correct pre-release.

 

As always, many thanks for any clarification and help in this issue. 👍

 

All the best,

 

KGP

Hi friend, thank you for your reply.

 

Pre release 3.0.1 has indeed been pushed down by Release 2.6.7, and I will make adjustments in the next push submission.

 

The current version 2.6.7 can also install sound card patches and old USB patches.These two emergency updates are for the normal use of users in Chinese Mainland. For well-known reasons, Github cannot be accessed normally in China, so I migrated all resources that need to be downloaded online to my own server and built an OCLP Mod API for OCLP Mod calls. Yesterday, the API server was completely rebuilt, and the old API nodes used before 3.0.0/2.6.4 will no longer be able to use.

 

Best regards.

[Matgen84]

Hi @laobamac_yyds

Thanks for renaming long number name for pre-release on GitHub repo. But I don't understand: this pre-release is related to commit 1e26f61 Update OMAPI url (main branch) instead of commit 8ff59f3 Update OMAPI url (Tahoe-test branch).

 

Let me know if I misunderstood something wrong.

 

[kgp]

21 minutes ago, Matgen84 said:

Hi @laobamac_yyds

Thanks for renaming long number name for pre-release on GitHub repo. But I don't understand: this pre-release is related to commit 1e26f61 Update OMAPI url (main branch) instead of commit 8ff59f3 Update OMAPI url (Tahoe-test branch).

 

Let me know if I misunderstood something wrong.

 

 

There was a general error in the repository two days ago. Version 2.6.7 had been published twice under 2.6.7 and Pre-Release. He might have pushed accidentally the code from the main branch to the tahoe test branch. After PM for clarification, he rolled back his commit to before the last push. Now we have the 2.6.7 entry with the 2.6.7 files and additionally the correct Pre-release entry with the 3.0.1 files. I verified everything and it works as expected. What you are pointing out might be a relict of the accidental push and rollback process? I am sure laobamac can explain this better.