macOS Tahoe 26 on Unsupported Macs Discussion

[Muhammad Arham]

Fair play to the devs for stopping the donations, and another huge thanks for all they've done with this project. ♥️

I guess Sequoia is still a supported OS until late next year, so fingers crossed there'll be one last OCLP miracle performed with Tahoe by then, even just for a limited number of Metal-supported/non-T2 machines. But if not, it's been a hell of a ride. 🫡

I guess, it's time from us to help OCLP devs. If anyone knows about Tahoe and commit to oclp, please try to enroll for Tahoe-Development. It's a last OS and we as a people should do anything to help OCLP warriors to keep the project alive !

 

[Significant1]

Isn't checkm8 firmware independent? It uses an exploit in the A7-A11 BootROM.

Something about the hack is iBridgeOS affected and 10.2+ is not supported.

 

[5T33Z0]

Find attached: macOS Tahoe compatible USBMap.kext for iMac12,2.

I created a new USB Port kext for my iMac12,2 since the one currently included in the EFI provided by OCLP does no longer work (no mouse nor keyboard interaction possible). I created it in USB Tool Box in Windows (using native classes) and then modified it with USBMapInjectorEdit to add the neccessary properties for macOS Tahoe compatibility.

Might be compatible with iMac12,1 by changing the "model" property.

Disclaimer: this does not mean that you should install macOS Tahoe on your legacy iMac!

 

[sinbad21]

Find attached: macOS Tahoe compatible USBMap.kext for iMac12,2.

I created a new USB Port kext for my iMac12,2 since the one currently included in the EFI provided by OCLP does no longer work (no mouse nor keyboard interaction possible). I created it in USB Tool Box in Windows (using native classes) and then modified it with USBMapInjectorEdit to add the neccessary properties for macOS Tahoe compatibility.

Might be compatible with iMac12,1 by changing the "model" property.

Disclaimer: this does not mean that you should install macOS Tahoe on your legacy iMac!

It saved me! I couldn't start macOS 26.4 on my MBP9.1, your kext allows me to restart. Thank you!

 

[hvds]

Installed successfully on my late 2013 MBP 11,1 but unfortunately no support for Iris graphics, every thing seem to work fine except for WIFI and Graphics.

Also here on MBP11,1: updated to 26.4 release from b2 on external SSD from USB installer, with OCLP 3.0.0n EFI.
Working well enough for this post with ethernet cable.
I stil have the effect that the system KPs while shutting down, then needs a power-off and reboot. This since first Tahoe betas in my case, no problem really.

 

[deeveedee]

OCLP Devs, where could I find the source for your new RestrictEvents.kext 1.1.7? Thank you.

 

[chris1111]

OCLP Devs, where could I find the source for your new RestrictEvents.kext 1.1.7? Thank you.

Its here RestrictEvents

 

[deeveedee]

@chris1111 No, it isn't. OCLP Dev's RestrictEvents.kext Version 1.1.7 includes the patch for non-AVX platforms.

 

[chris1111]

@chris1111 No, it isn't. OCLP Dev's RestrictEvents.kext Version 1.1.7 includes the patch for non-AVX platforms.

Yes see latest commits bump to version 1.1.7

 

[deeveedee]

Yes see latest commits bump to version 1.1.7

I found this source in the OCLP payloads commits. See here.

EDIT: The comment for RestrictEvents.kext 1.1.7 in OCLP Payloads indicates that the AVX patch is moved to the RestrictEvents.kext.

EDIT2: According to this commit, RestrictEvents.kext 1.1.7 accepts revpatch=jsc for patching javascript on non-AVX platforms. revpatch=jsc does not exist anywhere in the Acidanthera RestrictEvents repo.

 

[Pri-est]

I found this source in the OCLP payloads commits. See here.

EDIT: The comment for RestrictEvents.kext 1.1.7 in OCLP Payloads indicates that the AVX patch is moved to the RestrictEvents.kext.

EDIT2: According to this commit, RestrictEvents.kext 1.1.7 accepts revpatch=jsc for patching javascript on non-AVX platforms. revpatch=jsc does not exist anywhere in the Acidanthera RestrictEvents repo.

RestrictEvents.kext 1.1.7

 

[deeveedee]

@Pri-est Thank you.

I missed the fact that there was a new branch created for the javascript modification.

EDIT: This is an impressive way to solve the problem. For those who want to be further amazed by the OCLP Devs, take a look at the javascript patch for non-AVX Macs/Hacks.

 

[macinfo]

I wonder if there would be a possibility to emulate AVX2 with AVX machines, or would that be to far-fetched? For example I am thinking of most, if not all of the current adobe apps that do now require AVX2 for their latest versions.

 

[Mandaraxa]

Thank you @Pri-est. Restrict events 1.1.7 allows me back to run VMWare Fusion virtual machines on my Hackintosh Tahoe.

 

[Bigwaff]

I wonder if there would be a possibility to emulate AVX2 with AVX machines, or would that be to far-fetched? For example I am thinking of most, if not all of the current adobe apps that do now require AVX2 for their latest versions.

AVX2 is an instruction set baked into the processor. It used to speed up calculations. Emulating it would defeat its purpose. The squeeze isn’t worth the juice.

 

[deeveedee]

Thank you @Pri-est. Restrict events 1.1.7 allows me back to run VMWare Fusion virtual machines on my Hackintosh Tahoe.

I don't use VMWare Fusion on macOS, so forgive a naive question. I wasn't aware that VMWare Fusion has a javascript dependency. What about VMWare Fusion wasn't working with RestrictEvents.kext 1.1.6? What RestrictEvents (revpatch) arguments are you using in your config.plist?

 

[bombardier10]

For AVX2 support we must use CryptexFixup.kext. It works ok up to Tahoe too. But it not works
with Radeon GPU - here need OCLP to revert GPU drivers not ready at this moment.
You should also be aware that the lack of AVX2 instructions means that some programmes,
such as ACDSee, will not work properly. This is just an AVX2 emulation only.

 

[Mandaraxa]

I don't use VMWare Fusion on macOS, so forgive a naive question. I wasn't aware that VMWare Fusion has a javascript dependency. What about VMWare Fusion wasn't working with RestrictEvents.kext 1.1.6? What RestrictEvents (revpatch) arguments are you using in your config.plist?

Hi. Sorry for opposite time zone. I use revpatch=sbvmm. I had problems with VMWare Fusion before. Could not initiate any guest OS. I have macOS Tiger and Snow Leopard as guest OS's.

 

[deeveedee]

@Mandaraxa Thanks for the reply. revpatch=sbvmm makes sense (as it would affect VMWare Fusion) and was available in RestrictEvents.kext 1.1.6. revpatch=jsc (javascript patch) is the new capability in RestrictEvents.kext 1.1.7 (javascriptcore branch). I'd be surprised if RestrictEvents.kext 1.1.6 did not work for you (but stranger things have happened).

Thank you for clarifying.

 

[Daniel Pascoal]

Hi. Sorry for opposite time zone. I use revpatch=sbvmm. I had problems with VMWare Fusion before. Could not initiate any guest OS. I have macOS Tiger and Snow Leopard as guest OS's.

For VMWare Fusion forget about using the current version, you must find out the last version compatible with your hardware. Don't go by the oficial compatibility list, that list was not thinking about OCLP Macs. Previous versions works well on newer MacOses.

For instance, on my 2012 MBP 15 with Sonoma I use Fusion 13.0.2, last version that has 3D support on this Mac. For my 2015 iMac 4k with Sequoia I use Fusion 13.5.2, the last version that works.

Older versions can be found here: https://archive.org/details/vmware-softwareupdate-archive-20250318

 

[Mandaraxa]

Thank you @Daniel Pascoal. But when I replaced RestrictEvents 1.1.6 with 1.1.7 the current version works.

 

[deeveedee]

@Daniel Pascoal That's good info. Thank you.

 

[deeveedee]

Thank you @Daniel Pascoal. But when I replaced RestrictEvents 1.1.6 with 1.1.7 the current version works.

I don't see any reason that RestrictEvents.kext 1.1.7 would change the behavior of VMWare Fusion for you. Is it possible that your "1.1.6" version was not the latest release of 1.1.6? If so, then you may have had a pre-released version of 1.1.6 that was not yet updated for macOS Tahoe. Without the use of revpatch=jsc, the release version of RestrictEvents.kext 1.1.6 and the javascriptcore branch of 1.1.7 are no different.

RestrictEvents commits show that the kext version was incremented to 1.1.6 in Dec 2024, but was not updated for Tahoe until Jun 2025. Before the Tahoe update in Jun 2025, boot-arg -revbeta or -lilubetaall was required for Tahoe.

Spoiler

 

[deeveedee]

OCLP Devs - is something wrong with your KDK Mirror? KDK 26.4.1 is missing. See here.

EDIT: Also, maybe I'm missing it, but it appears that KDK 15.7.4 is missing, too.

EDIT2: I just noticed that Apple spelled Kernel wrong 🤣

Spoiler

 

[Sven G]

^^^ And it isn’t the first time: they also did it with KDK 14.6 build 23G5061b. One wonders how such mistakes are even possible and not corrected immediately (?!?). So, probably, the OCLP KDK mirror didn’t sync the latest 26.4.1 KDK because of this “Kernal” spelling error…?