macOS Tahoe 26 on Unsupported Macs Discussion

[deeveedee]

I was looking at Jazzzny's seemingly trivial commit here to figure out why he would have done this. His comment "Bump for CI" gives us a clue. It appears to me that Jazzzny posted this commit simply to trigger the automated build process. I haven't been following this too closely, but the nightly 2.5.0 is now available here. I think this nightly build link ( GUI (Graphical Based App) ) was broken before. If not broken, then it needed to be updated.

 

[basslik]

It's easier than you think, but I understand. Tahoe 26.6.2 is now running as well as Sequoia on my hacks. Apple is doing a great job with its Tahoe refinements. Something to look forward to.

EDIT: Here are the OCLP 3.0.0 nightly build steps posted earlier in this thread.

I'm truly surprised no one has done a YouTube clip for the process, with a disclaimer at your own risk of course.

Thanks deeveedee.

 

[deeveedee]

@basslik I'm sure someone will take your challenge and turn a 2 minute explanation into a 20-minute, monetized video.

 

[deeveedee]

@basslik If you think your MP5,1 Tahoe journey will help others (while you figure this out), start a thread with your MP5,1 Tahoe experiment and post the link here. I and others can offer help in that thread.

 

[basslik]

I do have an extra 5,1, and it does sound like something I would like to tackle.

Can this be attempted if I create a new container?

Also, steps 1, etc. Pyton and all the glory to help guide me will be cool.

Currently have a 5,1 identical as the one on my signature. Has Sequoia 15.8.9. FRESH INSTALL

 

[paalb]

I do have an extra 5,1, and it does sound like something I would like to tackle.

I am away from my 5,1's for some months, but please give us the link if you decide to do it.

 

[basslik]

I am away from my 5,1's for some months, but please give us the link if you decide to do it.

Will do, I'll have to first reread post on what I first have to do regarding pyton, and so on.

 

[macinfo]

PatcherSupportPkg in OCLP 2.5.0n has been updated to 1.9.7

 

[hvds]

PatcherSupportPkg in OCLP 2.5.0 has been updated to 1.9.7

View attachment 2655178

Thanks, good! So there will also be a new nightly build of 2.5.0 (not yet at the moment).

 

[macinfo]

A new nightly build is also produced, at least pkg.zip SHA is different from the last one. Haven’t tried it yet, though.
Latest #1850: sha256:90e304d4a2ca5aea0e613e0e797c99dbe4c7167fc9e5af4fbe6665a692bdae04

 

[deeveedee]

A new nightly build is also produced, at least pkg.zip SHA is different from the last one. Haven’t tried it yet, though.
Latest #1850: sha256:90e304d4a2ca5aea0e613e0e797c99dbe4c7167fc9e5af4fbe6665a692bdae04

Impossible. The OCLP Devs aren't working on OCLP. 😉

 

[Lucky736]

Impossible. The OCLP Devs aren't working on OCLP. 😉

That's what I've heard. 🙃🤣

 

[hvds]

A new nightly build is also produced, at least pkg.zip SHA is different from the last one. Haven’t tried it yet, though.
Latest #1850: sha256:90e304d4a2ca5aea0e613e0e797c99dbe4c7167fc9e5af4fbe6665a692bdae04

(Sorry this post belongs to Sequoia not Tahoe, but here it is)

There was a time window when the .pkg was available, then gone, and it is there again now.
I downloaded and installed it, runs OK *.
The OpenCore-Patcher.app was created on "Montag, 24. August 2026 um 01:36" CEST.
This should be the up-to-date nightly of 2.5.0n.

*edit: running this 2.5.0n on my MBP11,1 with 15.7.9, for EFI and root patching which uses the Metallib support package belonging to 15.7.9.

 

[Albert Müller]

And there’s an issue with MacBookPro7,1 not booting into Tahoe: https://github.com/albert-mueller/OpenCore-Legacy-Patcher-T2/issues/206 . This issue is reported by @Gandolf243 .
If anyone can find and fix the issue can come to the repo and suggest what to do next, create a fork and then push a PR, or ask to add as a contributor. To be exact, it stops at ("EB:EBS:START: %d", date) according to @Gandolf243 .

 

[deeveedee]

@Albert Müller Tahoe boots without issues on my HackBookPro6,2 (no root patches). It's a hackintosh that emulates MBP6,2 (with non-metal NVidia Tesla graphics). I have taken the Open Core EFI generated by OCLP 3.0.0 nightly, upgraded Acidanthera kexts, upgraded Open Core (to Open Core 1.0.7) and confirmed that USB Map is correct for Tahoe.

EDIT: I'm currently running Tahoe 26.7 Beta.

EDIT2: @Albert Müller I saw your explanation here. Thank you for your thorough attention to detail and your clear explanations.

 

[Outface]

Source-review note for Legacy USB 1.1 systems using OCLP 3.0 nightlies

The Legacy USB 1.1 KDK/primary-Kernel-Collection issue described in the linked report is also present in Dortania’s current macos-next source as of August 26, 2026. USB11Controller still does not override requires_kernel_debug_kit(), so it inherits False from BaseHardware. On Ventura and newer this can allow the AuxKC-only path and separate the downgraded IOUSBHostFamily/AppleUSBHub parent from the restored UHCI/OHCI plugins.

The proposed one-method fix makes USB11Controller require the KDK on Ventura and newer, keeping the parent and plugins together in the primary Boot/System Kernel Collections.

Important limitation: I have live-tested this change only with OCLP 2.5 source on a MacPro5,1 running macOS Sequoia 15.7.9 build 24G830. I have not tested Tahoe or an OCLP 3.0 nightly. This is therefore a source-code finding relevant to macos-next, not a Tahoe success claim. No custom or nightly binaries are being distributed.

Current macos-next USB11 source:

https://github.com/dortania/OpenCore-Legacy-Patcher/blob/macos-next/opencore_legacy_patcher/sys_patch/patchsets/hardware/misc/usb11.py

BaseHardware default:

OpenCore-Legacy-Patcher/opencore_legacy_patcher/sys_patch/patchsets/hardware/base.py at macos-next · dortania/OpenCore-Legacy-Patcher

Experience macOS just like before. Contribute to dortania/OpenCore-Legacy-Patcher development by creating an account on GitHub.

github.com

Tested source commit:

sys_patch: require KDK for legacy USB 1.1 · stephandeutsch/OpenCore-Legacy-Patcher@a53c7e9

Keep IOUSBHostFamily and its UHCI/OHCI plugins together in the primary Boot/System Kernel Collections.

github.com

Full technical report:

https://forums.macrumors.com/threads/oclp-2-2-0-macpro-5-1-wifi-but-no-bluetooth-on-sequoia.2448535/post-34743943

Outface S.D.

 

[Pri-est]

Source-review note for Legacy USB 1.1 systems using OCLP 3.0 nightlies

The Legacy USB 1.1 KDK/primary-Kernel-Collection issue described in the linked report is also present in Dortania’s current macos-next source as of August 26, 2026. USB11Controller still does not override requires_kernel_debug_kit(), so it inherits False from BaseHardware. On Ventura and newer this can allow the AuxKC-only path and separate the downgraded IOUSBHostFamily/AppleUSBHub parent from the restored UHCI/OHCI plugins.

The proposed one-method fix makes USB11Controller require the KDK on Ventura and newer, keeping the parent and plugins together in the primary Boot/System Kernel Collections.

Important limitation: I have live-tested this change only with OCLP 2.5 source on a MacPro5,1 running macOS Sequoia 15.7.9 build 24G830. I have not tested Tahoe or an OCLP 3.0 nightly. This is therefore a source-code finding relevant to macos-next, not a Tahoe success claim. No custom or nightly binaries are being distributed.

Current macos-next USB11 source:

https://github.com/dortania/OpenCore-Legacy-Patcher/blob/macos-next/opencore_legacy_patcher/sys_patch/patchsets/hardware/misc/usb11.py

BaseHardware default:

OpenCore-Legacy-Patcher/opencore_legacy_patcher/sys_patch/patchsets/hardware/base.py at macos-next · dortania/OpenCore-Legacy-Patcher

Experience macOS just like before. Contribute to dortania/OpenCore-Legacy-Patcher development by creating an account on GitHub.

github.com

Tested source commit:

sys_patch: require KDK for legacy USB 1.1 · stephandeutsch/OpenCore-Legacy-Patcher@a53c7e9

Keep IOUSBHostFamily and its UHCI/OHCI plugins together in the primary Boot/System Kernel Collections.

github.com

Full technical report:

https://forums.macrumors.com/threads/oclp-2-2-0-macpro-5-1-wifi-but-no-bluetooth-on-sequoia.2448535/post-34743943

Outface S.D.

USB 1.1 patchset for classic configuration(GTX 680/legacy Bluetoth+WIFI) broken since OCLP 2.x.x.

And little of my experience with macOS Tahoe on CMP 5,1

 

[deeveedee]

.

 

[olad]

.

@deeveedee rendered speechless? Only a punctuation? Noooo! 😉🫡

 

[Albert Müller]

@deeveedee rendered speechless? Only a punctuation? Noooo! 😉🫡

Likely wrote something by accident, and couldn’t delete it and replaced with a dot. I had the same issue in MacRumors and had to replace the message with a dot instead of deleting because that function is missing entirely in MacRumors.

 

[olad]

Likely wrote something by accident, and couldn’t delete it and replaced with a dot. I had the same issue in MacRumors and had to replace the message with a dot instead of deleting because that function is missing entirely in MacRumors.

Yeah, I know. It's happened to many of us. (I did find a way round, but it's a long time ago, and I don't remember what I did then.) But she's got a lovely sense of humour and I doubt she'd mind being ribbed once in a while.

 

[deeveedee]

Might be one of the more intelligent things that I've said: 🤣

 

[hackintosh_user]

Now a year into 2.4.1! Very nice to see it still very stable even a year after it's release! But i do wish to see Tahoe OCLP soon but that's a dream now more than something happening soon sadly.

 

[Drivemysaab]

Dear friends, I think we have to accept that this project has effectively been abandoned. Apple seems to have killed it by hiring its lead developer.

At this point, I don't think we should expect anything more from OCLP. Continuing to wait for a solution is, sadly, becoming a waste of time.

It's a real shame, because OCLP has been an extraordinary project. It has given many perfectly capable Macs a much longer life and, in doing so, has helped fight against planned obsolescence.

😥

 

[hackintosh_user]

Dear friends, I think we have to accept that this project has effectively been abandoned. Apple seems to have killed it by hiring its lead developer.

At this point, I don't think we should expect anything more from OCLP. Continuing to wait for a solution is, sadly, becoming a waste of time.

It's a real shame, because OCLP has been an extraordinary project. It has given many perfectly capable Macs a much longer life and, in doing so, has helped fight against planned obsolescence.

😥

I still hold some hope for an OCLP update for Tahoe. But that is just fading away now.. I personally think we should take a look at how insane that 5 years of OCLP really is.. 5 macOS releases ported to macs old as 2007 & 2008 that alone is an insane feat of modern human developement & engineering. I do still hope to see an update for OpenCore Legacy Patcher. but its not as likely nowadays, unlike in this time of last year we were basically waiting for them to "do their magic" as we all have grown to say. But as much as the developers fight macOS, apple has always planned on killing intel Cpus the moment they put apple silicon on their devices. macOS Tahoe is the literal product of this. it runs great on an M1 CPU but the top of the line MacBookPro 2019 16inch that costed over 4 thousand dollars runs it like ****! So in alll cases, Thank you devs but i really do hope to see atleast an small update about progress.