Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS Tahoe 26 on Unsupported Macs Discussion
- Thread starter jshayya0184
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
MBP11,1: updated to 26.0b5 from b3, external SSD, with USB installer.
OCLP 3.0.0n used with slight source modifications to disable patching of Haswell graphics, wifi, audio so only Facebook camera patched (which works).
Also manually put the two kexts for HD5000 and Framebuffer into /Library/Extensions (auxiliary kernel collection) where they live in Sequoia and earlier for this MBP11,1. This "clearly seems" to speed up graphics. If that impression reflects reality, part of the Haswell graphics patches may still be fine in Tahoe.
Installation was not so smooth this time: didn't reboot to the next step, so force powered-off then manually booted each time, but that proceeded to a bootable system. The public b2 has a slightly different build number as developer b5, will repeat with this one when InstallAssistant becomes available.
But good enough to write tihis in Safari 26.0. System quite usable overall. Thanks developers!
PS: system doesn't power off the normal way, consistent with the observation during installation.
OCLP 3.0.0n used with slight source modifications to disable patching of Haswell graphics, wifi, audio so only Facebook camera patched (which works).
Also manually put the two kexts for HD5000 and Framebuffer into /Library/Extensions (auxiliary kernel collection) where they live in Sequoia and earlier for this MBP11,1. This "clearly seems" to speed up graphics. If that impression reflects reality, part of the Haswell graphics patches may still be fine in Tahoe.
Installation was not so smooth this time: didn't reboot to the next step, so force powered-off then manually booted each time, but that proceeded to a bootable system. The public b2 has a slightly different build number as developer b5, will repeat with this one when InstallAssistant becomes available.
But good enough to write tihis in Safari 26.0. System quite usable overall. Thanks developers!
PS: system doesn't power off the normal way, consistent with the observation during installation.
Attachments
Last edited:
@ronton3 You're going to need to monitor this yourself based on your own criteria. There are likely going to be commits that are not relevant to you (and so you won't need to test). My suggestion would be to monitor commits to the macos-next branch (at the time of this post). At the time of this post, the last commit to macos-next branch was 3 weeks ago.
EDIT: At the time of this post, almost all of the changes to main branch have been documentation updates.
EDIT: At the time of this post, almost all of the changes to main branch have been documentation updates.
For suppose, if Apple Releases macOS Tahoe 26 in September, will OpenCore Legacy Patcher manage to release v3.0.0 on that day for all devices. And one more question, where is the nightly version of OCLP v3.00 ? Because Opencore Legacy Patcher always used to roll a preliminary support for all macOSes ? But depends upon the issues .
That's like a good news for me ! It will be pleasure for me to install macOS Tahoe on my unsupported Macbook Pro Late 2013 13 inch.
Hello Guys ! i hope everyone out here is doing well. I have talked to one of the developers of OCLP development team. He told me that work is going on in private even though commits aren't resumed on Github webpage. If you guys want to make me an estimate so in my opinion, 75% is completed ! I guess we will get OpenCore Legacy Patcher v3.0.0 in September 16 when iPhone 17 Pro will release or in October. Depends upon OCLP and Apple !
similarly MBP5,2: updated to 26.0b5 from b4, external SSD, with USB installer.
OCLP 3.0.0n used with slight source modifications (see 2nd text file below) to disable patching of wifi and audio. USB1.1, keyboard backlight and non-metal graphis patching left in place.
So internal keyboard/trackpad, backlight, facebook camera work.
Graphics is fast enough to write this (Firefox) but maybe slower than it was with b4. There are occasional window server crashes.
Anyway patched system boots (for this it needs the EFI with legacy USB map, installer and system without USB patches need EFI without legacy map).
Had difficulty to get a valid KDK so made the change to kdk_handler as shown. Maybe I was not waiting for long enough at the beginning of root patching (took more than 1/2hr for kdk finding).
No problems like with MBP11,1/26.0b5 during installation and power-off.
Still enjoying the MBP5,2 from 2009.
And the 2013 MBP11,1 is still my production system (with Sequoia).
Thanks developers!
Attachments
Last edited:
Not iPhone 17 as September is the month when iOS 26 iPadOS 26 will release along with macOS Tahoe so OCLP will release it hopefully 😀
No. Speed-wise the graphics-patched Tahoe on the MBP5,2 is much faster than unpatched, but much slower than patched Sequoia. Patched Tahoe on 5,2 is about as slow/fast as unpatched Tahoe on my MBP11,1 (where graphics patches aren't available to me). The MBP5,2 Dock looks OK while it has the line around it without graphics patches.
The real surprise for me was that the existing non-metal patches work in Tahoe for the MBP5,2. Formally at least in that it still boots, but also in speedup.
(you can estimate my skills level from me not knowing what QE/CI means..)
As someone part of the team and a moderator on the Discord server, I'm asking you to avoid spreading misinformation. Nobody has told you an ETA, they will release when they are ready.
The only part being true is the development happening in private.
Last edited:
I am so sorry for this inconvenience! I will make sure to confirm the news next time. I don't know but a random user from that server told me it's happening. If you mind, I will make sure to delete this post and spread truth next time. I am extremely sorry again.
Hello guys. I hope everyone here are in the best of their health. The post I created on Saturday was based on half information. I actually interpreted the info in a wrong manner. I will be careful next time. Please ignore this post as it will be deleted in few minutes. Let's move on and keep waiting for OpenCore Legacy Patcher. I call everyone to keep following #Tahoe-Info on discord server! Thanks for your patience and cooperation.
And I would like to say one more thing. Do not try OCLP-Mod from InsanelyMac unless you know how to troubleshoot and make your own patches. The best thing is to wait until OCLP v3.0.0 rolls out. I am running macOS Sequoia 15.6 on my unsupported MacBook Pro Late 2013 and it works like a dream ! Let's see if Tahoe works on my mac too.
I tried to install macOS Tahoe on a seperate volume named Tahoe HD. Surprisingly, it only took 16 seconds for my Macbook Pro Late 2013 to boot on Tahoe. Although setting Region and other stuff was painful without graphics acceleration. When I clicked on Post-Install-Root Patches, some were available for me because patches are private. However, the mac was running a bit efficient with some patches on, which made me hopeful for what's about to come. Metal-3802 is problematic and all developers are exhausted while fixing it's issues, but by the end of the day, it will work. I have never seen failure in any project of OpenCore Legacy Patcher. It will work but after some time.
Thank you for being respectful.
Anyway, yeah the reason why ETAs are not given is to not put pressure on the developers and set the public for a disappointment if it doesn't release on the given date due to unforeseen circumstances. This can for example be a new beta breaking already somewhat working patches that have to be fixed again and so on.
Hence why "releases when it's ready" is the best way to go about it, so there's at least some assurance things should work without major issues. Depending on the progress the release may be sooner or later.
No Problem! Mistake was on my side, so why I should be proud on that ?