Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Thank you for the years with OCLP Edu, take care of yourself and wishing the best for your new endeavors.


All patches in OCLP-Mod are from the original OCLP devs. OCLP-Mod is just a fork of OCLP with removed root patch block that OCLP had deliberately set.

Well, not quite. Let's take the modern wireless patch as an example.
The nightly version of OCLP requires VT-d disabled and must disable AMFI at all times.
OCLP-mod by Laobamac - VT-d can be enabled and AMFI not disabled - need amfipass.kext.
So OCLP-mod has solutions that are not in the original OCLP and currently works better.
Also for Tahoe audio patch we can use MykextInstaller app. This is an simple application
that restores AppleHda.kext from a Sequoia system.
Very interesting is AppleBCMWLANCompanion project that support some Broadcom WiFi
without root patches...
So, contrary to appearances, independent solutions are available and that's very good.
 
Last edited:
  • Like
Reactions: perez987 and olad
Yeah everything in it already existed in OCLP. WiFi patches are public and the AppleHDA.kext is from the 26.0 Beta 1 KDK, anyone can take it and put it into the OS if you know how to add kexts to the snapshot i.e. do a manual root patch.

I'm not the best one to comment on how the project will move forward, so I won't.
Okay, thank you so much for answering my question 🙂
 
Also for Tahoe audio patch we can use MykextInstaller app. This is an simple application
that restores AppleHda.kext from a Sequoia system.
Very interesting is AppleBCMWLANCompanion project that support some Broadcom WiFi
without root patches...
It’s not to deny that there are many good things coming from the broader Hackintosh community, but many of us being spoiled by the highly integrated and almost foolproof workflow that OCLP and the former dosdude1 patches provided over the years for our older Macs.

On the topic of kext installer tools, this one came to my mind instantly, but I have no idea if that could still be of use with more current macOS iterations:

kextutility.png


That nice Kext Utility never let me down, where most others routinely failed. ;-)
 
Last edited:
  • Like
Reactions: olad
While I did not read every word of every post in this thread, I don't think anyone mentioned OpenCore Legacy Patcher from Git Hub. It was my intention to try this with the successor to Tahoe before giving my my 2020 iMac, 500 GB SSD, 27” monitor, macOS 26.3

 
  • Haha
Reactions: olad and rehkram
While I did not read every word of every post in this thread, I don't think anyone mentioned OpenCore Legacy Patcher from Git Hub. It was my intention to try this with the successor to Tahoe before giving my my 2020 iMac, 500 GB SSD, 27” monitor, macOS 26.3
That's actually what most of this thread is about. It won't work with the "successor to Tahoe". It requires an Intel build of macOS to start with, and there will never be an Intel build of macOS 27.
 
  • Like
Reactions: olad
Well, not quite. Let's take the modern wireless patch as an example.
The nightly version of OCLP requires VT-d disabled and must disable AMFI at all times.
OCLP-mod by Laobamac - VT-d can be enabled and AMFI not disabled - need amfipass.kext.
So OCLP-mod has solutions that are not in the original OCLP and currently works better.
Also for Tahoe audio patch we can use MykextInstaller app. This is an simple application
that restores AppleHda.kext from a Sequoia system.
Very interesting is AppleBCMWLANCompanion project that support some Broadcom WiFi
without root patches...
So, contrary to appearances, independent solutions are available and that's very good.
Nightlies aren't meant to be for regular use, so hence they can include binaries that aren't signed for AMFIPass which of course means AMFI has to be disabled. They're only for testing, so there's no point in signing them until release. You've probably noticed the forks only do WiFi and audio, that is because that's all there has been publicly available.

That Broadcom companion thing however is separate from OCLP entirely and is not from OCLP devs. It looks like a nice project for sure, especially if they can pull off full WiFi support (incl. AWDL) without root patches.
 
Last edited:
Last edited:
Well you can see the early accelerated graphics patches working in the issue post, however it's possible later versions of Tahoe have broken them again since it's always an uphill battle with macOS updates. I also personally tested a few of them last year, for example GCN 1.0 was mostly working in 26.0 with few glitches.
Just a question, where the glitches like system breaking? Or is it visual glitches? Regardless, hopefully we see some good news about this project. ( I actually donated a couple of hours ago)
 
  • Like
Reactions: K two
I want to say that I can't work on OCLP anymore for a few reasons, mostly due to serious mental health conditions. There will be no new patches or updates coming from me.
You've done a good job over these past few years, and I say "ditto" to dhinak's words. Your work has changed OCLP forever, and we wouldn't be here without you.

Take care of yourself, will ya?
 
Tahoe 26.4 (25E5207k) Beta feels more responsive on my Intel-based platforms than previous versions of Tahoe.
I continue to run Tahoe with the following System Settings:
  • Accessibility > Display > Reduce Transparency: Enabled
  • Accessibility > Motion > Reduce Motion: Enabled
  • Terminal: defaults write -g com.apple.SwiftUI.DisableSolarium -bool YES
EDIT: Changing Wall Paper to a color may also help Tahoe performance on older Macs
  • System Settings > Wall Paper > Colors
 
Last edited:
I must say, I am getting really irritated by Apples communication policies. They are becommung really "euphemistic" to put it mildly.

Example 1, from the Developer Notes of macOS 26.4: "HFS external media might fail to mount automatically. (168672160)"

In reality: they deleted HFS+ support completely!

Example 2: Recently, Logic Pro 12 was released. I've downloaded it on my Intel Mac from the App Store but it failed to install. I got notfied about it via a Pop-Up: "Instalation failed – try again later"

In reality: Logic Pro 12 is Apple Silicon only! But they don't inform you about it. I even had to spend a considered amount of time which I shouldn't have to do just to figure out the system requirements of an App like that.
 
  • Like
Reactions: perez987 and olad
I must say, I am getting really irritated by Apples communication policies. They are becommung really "euphemistic" to put it mildly.

Example 1, from the Developer Notes of macOS 26.4: "HFS external media might fail to mount automatically. (168672160)"

In reality: they deleted HFS+ support completely!

Example 2: Recently, Logic Pro 12 was released. I've downloaded it on my Intel Mac from the App Store but it failed to install. I got notfied about it via a Pop-Up: "Instalation failed – try again later"

In reality: Logic Pro 12 is Apple Silicon only! But they don't inform you about it. I even had to spend a considered amount of time which I shouldn't have to do just to figure out the system requirements of an App like that.
About the logic pro one, apple in Tahoe 26.4 beta added a charging limit but they literally don't tell you it's apple silicon only!! Same with 26.2, they added a kinda of a screen ring light (i don't know if you heard of it) and didn't tell you it's apple silicon only. Some documentation about these would be really appreciated
 
Doesn't seem so, users have reported success mounting these drives from the terminal. HFS+ support is still there.
I can mount my HFS+ volumes with 'diskutil mount'. We've seen this before in previous Beta versions of macOS.

On the bright side, Apple just released updates for Big Sur and Catalina that allow users of those old OSes to continue using their Macs.
 
Last edited:
Quick question if the recent “expired” certificates that have just been extended for older devices did end would it be possible to side load a current one ? I think that’s where my Mac will end when iCloud support does (I get that’s along way off)
 
Quick question if the recent “expired” certificates that have just been extended for older devices did end would it be possible to side load a current one ? I think that’s where my Mac will end when iCloud support does (I get that’s along way off)

I hope that Apple makes this difficult... If you could side-load any certificate on your own, then malicious actors could install their own certificates and open the door to man-in-the-middle attacks.

(If it is simply a certificate swap and nothing else like changes to the encryption algorithms being used, then it's probably technically possible, but it would require elevated privileges, plus disabling SIP on systems that use that.)
 
I must say, I am getting really irritated by Apples communication policies. They are becommung really "euphemistic" to put it mildly.

Example 1, from the Developer Notes of macOS 26.4: "HFS external media might fail to mount automatically. (168672160)"

In reality: they deleted HFS+ support completely!

Example 2: Recently, Logic Pro 12 was released. I've downloaded it on my Intel Mac from the App Store but it failed to install. I got notfied about it via a Pop-Up: "Instalation failed – try again later"

In reality: Logic Pro 12 is Apple Silicon only! But they don't inform you about it. I even had to spend a considered amount of time which I shouldn't have to do just to figure out the system requirements of an App like that.

Running here on my iMac 2012 15.7.5. with Logic 12.0.1, INTEL.
 
Yes Logic Pro 12 is available on Intel too.I can't verify HFS+ 100% right now. But it would seem
completely foolish not to support it on Tahoe. Preparing an installation USB drive for Tahoe requires
the HFS+ system.
 
Yes Logic Pro 12 is available on Intel too.I can't verify HFS+ 100% right now. But it would seem
completely foolish not to support it on Tahoe. Preparing an installation USB drive for Tahoe requires
the HFS+ system.

Reading about Logic 12 being available on Intel systems in various posts made me think. I was wondering why it wouldn't install. The download was always completed but then the installation failed. I was wondering if this could be related to the VMM-board-id injected by the Restrict Events kext. So I disabled it, rebooted and voilà: Logic Pro 12 would install on my Intel system immediately.

My hypothesis is: when Restict Events is active and is injecting the VMM-board-ID, App Store detects the machine as a VM running on M-Mac and then it serves the ARM version of Logic instead of the Intel version. And installation fails in this case.

I also checked the HFS+ situation: my macOS Extended disk is still recognized in disk utilty but as stated in the dev log it, it won't auto-mount. But there was a strange notification on the desktop: "Disk could not be repaird" or something similar.
 
Last edited:
My hypothesis is: when Restict Events is active and is injecting the VMM-board-ID, App Store detects the machine as a VM running on M-Mac and then it serves the ARM version of Logic instead of the Intel version. And installation fails in this case.
That's an interesting theory. If your theory is sound, wouldn't that suggest that our Intel-based Macs would download ARM versions of macOS updates (which I have never observed)? I'm not saying your theory is wrong - I'm just wondering why App updates would be affected while macOS updates are not.
 
Well haven't been on much, and was hoping for better news.... but none the less take care of yourself, that is more important.

macOS Sequoia works well and does what I want it to, just was looking forward to Tahoe
 
  • Like
Reactions: 5T33Z0
Yes Logic Pro 12 is available on Intel too.I can't verify HFS+ 100% right now. But it would seem
completely foolish not to support it on Tahoe. Preparing an installation USB drive for Tahoe requires
the HFS+ system.
There is a thread that discusses the HFS+ mounting issue in the Tahoe 26.4Beta: Does Tahoe 26.4 deprecate HFS+?
Summary: It is listed as a known bug in the release notes of that developer version.
 
Last edited:
  • Like
Reactions: hvds
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.