Worked well under 15.3.1 (have not yet used it on 15.3.2).
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 15 Sequoia on Unsupported Macs Thread
- Thread starter flagers
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
On my MBP 15" 2015, upgraded to Sequoia via OCLP, I've found two things that annoy me:
1) After a cold boot, my dock often disappears. I have to go into System Settings>Desktop & Dock>Automatically Hide and Show the Dock. If I toggle that option, the dock reappears.
2) The latest "Swift Playgrounds" application from the App Store isn't working properly. For some reason, the graphics part of the playground won't display and I keep getting an error message saying my code is wrong Even if I haven't written any code. Yes, I've deleted the app and reinstalled but I keep getting an error.
I haven't explored many details of why "Swift Playgrounds" won't work. But it runs fine on my MBP 2017 w/ Ventura and my old Mac Pro running Big Sur. This may have nothing to do with the underlying hardware, though. May be some weird software configuration issue.
Xcode 16.2 and the newest Xcode Beta both seem to be working fine on this MPB 15" 2015 Sequoia via OCLP.
1) After a cold boot, my dock often disappears. I have to go into System Settings>Desktop & Dock>Automatically Hide and Show the Dock. If I toggle that option, the dock reappears.
2) The latest "Swift Playgrounds" application from the App Store isn't working properly. For some reason, the graphics part of the playground won't display and I keep getting an error message saying my code is wrong Even if I haven't written any code. Yes, I've deleted the app and reinstalled but I keep getting an error.
I haven't explored many details of why "Swift Playgrounds" won't work. But it runs fine on my MBP 2017 w/ Ventura and my old Mac Pro running Big Sur. This may have nothing to do with the underlying hardware, though. May be some weird software configuration issue.
Xcode 16.2 and the newest Xcode Beta both seem to be working fine on this MPB 15" 2015 Sequoia via OCLP.
Last edited:
I'd like to update my mid 2015 macbook pro (15 inch/16 GB RAM/2.5 GHz) to macOS Sequoia. I assume it'll work fine using OpenCore Legacy Patcher. What I do wonder is if Xcode 16.2 will work as well? I'd like to do some iOS development on this machine.
I've seen some reports about XCode not working properly after updating with OpenCore LP with regards to the graphics card acting up, e.g when trying to run iphones/ipads on the built-in simulator
I've seen some reports about XCode not working properly after updating with OpenCore LP with regards to the graphics card acting up, e.g when trying to run iphones/ipads on the built-in simulator
I believe this is an update for 2.3
OpenCore Legacy Patcher changelog
2.3.0
Disable crash analytics
Disabled server side for years, removing client side
OpenCore-Patcher-GUI.app.zip removed from release
Deprecated in 1.5.0, use OpenCore-Patcher.pkg for installation
Sync copyright label to 2025
Increment binaries:
OpenCorePkg 1.0.4 - release
Lilu 1.7.0 - release
WhateverGreen 1.6.9 - release
AirPortBrcmFixup 2.1.9 - release
NVMeFix 1.1.2 - release
RestrictEvents 1.1.5 - release
FeatureUnlock 1.1.7 - release
DebugEnhancer 1.1.0 - release
CPUFriend 1.2.9 - release
BlueToolFixup 2.6.9 - release
CryptexFixup 1.0.4 - release
OpenCore Legacy Patcher changelog
2.3.0
Disable crash analytics
Disabled server side for years, removing client side
OpenCore-Patcher-GUI.app.zip removed from release
Deprecated in 1.5.0, use OpenCore-Patcher.pkg for installation
Sync copyright label to 2025
Increment binaries:
OpenCorePkg 1.0.4 - release
Lilu 1.7.0 - release
WhateverGreen 1.6.9 - release
AirPortBrcmFixup 2.1.9 - release
NVMeFix 1.1.2 - release
RestrictEvents 1.1.5 - release
FeatureUnlock 1.1.7 - release
DebugEnhancer 1.1.0 - release
CPUFriend 1.2.9 - release
BlueToolFixup 2.6.9 - release
CryptexFixup 1.0.4 - release
...hopefully also for 15.4. on old GPUs.
We´ll see!
No, they still have a lot of problems fixing the PatcherSupportPkg. Among other things, the problem with the T1 chip, etc. I think it will take some time. So don't expect it anytime soon.
Smooth upgrade of my HackBookPro6,2 from 15.3.1 -> 15.3.2. Applied Nvidia Tesla and Wi-Fi post-install patches with OCLP 2.2.0. Safari 18.3.1 works fine in my limited use cases with Sequoia.
15.4 release candidate dropped today.
www.macrumors.com
Apple Seeds macOS Sequoia 15.4 Release Candidate With Mail Categorization
Apple today provided developers with the release candidate version of an upcoming macOS Sequoia 15.4 update for testing purposes. The new beta is...
www.macrumors.com
15.4 beta 4 reverting patches updating to 15.4 RC was 1.06gb using latest OCLP nightly as mentioned above OCLP 2.3n no issues updating MacBook Pro 2014
15.4 release candidate dropped today.
Apple Seeds macOS Sequoia 15.4 Release Candidate With Mail Categorization
Apple today provided developers with the release candidate version of an upcoming macOS Sequoia 15.4 update for testing purposes. The new beta is...
I had already updated to the newest 2.3n and now with 15.4(24E246) things seem fine, a small annoyance with the progress bar being blackened out through the center with only a small white dot on each end seems to be fixed. When OCLP asked to repatch the KDK was the same.
A while back we were speculating for how long macOS will be supported.
Appleinsider posted an article today:
“At the same time, Apple has issued release candidates for older operating systems. An RC build of iOS 17.7.6 is out with build 21H423, while macOS 14.7.5's RC is build 23H527, and the RC for macOS 13.7.5 is build 22H527”
Appleinsider posted an article today:
“At the same time, Apple has issued release candidates for older operating systems. An RC build of iOS 17.7.6 is out with build 21H423, while macOS 14.7.5's RC is build 23H527, and the RC for macOS 13.7.5 is build 22H527”
MBP5,2: installation of 15.4b4 succeeded, using OCLP 2.3.0n from 23 March. Clean installation to internal SSD, not patched.
Had no luck with 2.2.0 and earlier 2.3.0ns, installations ended with error popup at rather late stage. Then installed ElCapitan (the last supported OS for MBP5,2) to verify hardware still OK. Now installed over ElCap.
Running migration assistant at present.
Had no luck with 2.2.0 and earlier 2.3.0ns, installations ended with error popup at rather late stage. Then installed ElCapitan (the last supported OS for MBP5,2) to verify hardware still OK. Now installed over ElCap.
Running migration assistant at present.
Last edited:
OCLP 2.3.0n new nightly - fyi
- Resolve MetallibSupportPkg failing to be cached on units without Kernel Debug Kit requirements
🫶
- Resolve MetallibSupportPkg failing to be cached on units without Kernel Debug Kit requirements
🫶
Hi all, my OCLP installs and machine specs can be seen in the signature file below.
What I have realised that has happened since moving to 15.3.2 and 2.3.0N is that from login to actually being able to run a command in spotlight takes a significant longer amount of time. The CPU usage for at least the first minute is a solid 100%
Is there anyway I can speed this up?
What I have realised that has happened since moving to 15.3.2 and 2.3.0N is that from login to actually being able to run a command in spotlight takes a significant longer amount of time. The CPU usage for at least the first minute is a solid 100%
Is there anyway I can speed this up?
15.4 RC is out - will test it soon on MM 7,1.
OTA upgrade went fine with oclp 2.3n. Normally I upgrade with usb full installer but there is no RC full installer as always.
OTA upgrade went fine with oclp 2.3n. Normally I upgrade with usb full installer but there is no RC full installer as always.
Last edited:
I patched my 2011 iMac a few years back with Monterey - all works fine (mostly). I am considering the Sequoia update but I'm pretty sure when I looked at doing a recent re-install of the then currently available patch OS there were some incompatibilities with the wifi adapter?
I've checked the docs but cant find this info, am I not looking in the right place or is this no longer a current issue?
Presumably a fresh install on a different SSD is the way to go - as tempting as the update via the OTA notification is to click!
Thanks!
I've checked the docs but cant find this info, am I not looking in the right place or is this no longer a current issue?
Presumably a fresh install on a different SSD is the way to go - as tempting as the update via the OTA notification is to click!
Thanks!
This is off-topic, but just for your information:
With the updated version of Microsoft Autoupdate released on March 20 for Intel processors, the automatic updates for all software updated by that tool (MS Word, MS Excel, etc.) are working again for me on my MBP11,2.
Thanks
With the updated version of Microsoft Autoupdate released on March 20 for Intel processors, the automatic updates for all software updated by that tool (MS Word, MS Excel, etc.) are working again for me on my MBP11,2.
Thanks
This also solves a small issue on my MBP11,1 which is patched "KDK-less". I always had to remove AppleIntelHD5000Graphics.kext manually from /Library/Extensions prior to updating/installing macOS.
The code change in sys_patch.py now enables auto patcher demon also if KDK is not needed, and the demon takes care of deleting that file.
Updating 15.4b4 to 15.4RC OTA on that machine's external SSD worked well now without manual deletion. Using OCLP 2.3.0n from 24 March for bootloader and patching. Resulting system works well.
Thank you developers for this improvement!
Edit 27 March: updated OTA from RC to RC2 (24E247). Metallib 24E246 was used in patching.
Same positive result.
Edit 28 March: repeated root patching. Now the direct match metallib 24E247 is used.
Last edited:
I've been complaining about this for a while and have already mentioned it here. Also, some apps crash or won't start at all. Touch ID doesn't work because something needs to be changed in the PatcherSupportpkg. But nobody here seems to care.
@Ghosthengst77 I don't have Touch ID, but I have seen it mentioned. Have you experimented with OCLP's SMBIOS Spoofing to fix Touch ID?
Yes, I tried it. I've tried everything. It doesn't change the fact that something needs to be changed or updated in the PatcherSupportPKG. As long as the problem isn't resolved there, the Touch ID function won't work.The function of the T1 chip in the PatcherSupportPKg must be updated for the 15.4 version
