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.
I manually installed KDK 15.7.4 in Sequoia 15.7.4 on my HackBookPro6,2 (non-metal NVidia Tesla graphics). <Shift> <Command> screen captures are working again. The problem was the missing KDK and not OCLP. For some reason, the Dortania KDK mirror did not pull KDK 15.7.4 from Apple.
I rebooted and <Shift><Command> screenshots are not working again. Not sure what happened, but the KDK isn't the whole story.
 
Last edited:
I fine tuned Sequioa install but... I face weird sound problem not sure it is related to OCLP.

I hear startup sound but when imac 2013 21,5" boots sound output turns to Digital output and no sound.
I tried all AI tricks. SMC, PRAM reset, midi devides setup, cleaning audio jack, reset core audio and other terminal hacks.
What I have not tried is disconecting broken display. I would bet i played youtube videos on both imacs and sound was working in some stage of messing with installation.

I have no clue whether it can have relation to OCLP as I said.
Cherry on top is that it already happened that display has came co life twice but goes off after reboot again 😀 Not sure it is related to display itself or cables or some chips on board.
😃 And I can answer to myself again. I may accidentally disconnected audio jack connector from motherboard so system was confused and turned to digital output. It is weird but that is life.
 
when it worked for me, I only needed to perform TM Restores without OCLP root patches. Backups with OCLP root patches were ok. At some point, TM restores stopped working for me even without OCLP root patches as mentioned here.

Oh, I get the problem with restores from TM--I had that issue trying it in Sequoia, but my original question stands: why should just TM backups be done without root patches?
 
Oh, I get the problem with restores from TM--I had that issue trying it in Sequoia, but my original question stands: why should just TM backups be done without root patches?
After OCLP TM backup from MP 5,1 Ventura, I could not restore successfully to either 2017 MB or MP 6,1, both OCLP Sonoma. Root patches were uninstalled for restore on both. Neither would boot successfully. I have been successful multiple times backing up and restoring the 2017 MB using TM. Root patches are uninstalled before manual TM backups and before any restore attempted.

My experience certainly isn’t conclusive, as I did not try every combination of OCLP, macOS, or hardware. My take away - if you want to use TM for backups, which implies you will eventually want to restore/migrate to either an OCLP or non-OCLP Mac in the future, your most likely chance of success is to have backups taken when root patches are uninstalled. But, as with all things OCLP, YMMV.
 
  • Like
Reactions: roronl
After OCLP TM backup from MP 5,1 Ventura, I could not restore successfully to either 2017 MB or MP 6,1, both OCLP Sonoma. Root patches were uninstalled for restore on both. Neither would boot successfully. I have been successful multiple times backing up and restoring the 2017 MB using TM. Root patches are uninstalled before manual TM backups and before any restore attempted.

My experience certainly isn’t conclusive, as I did not try every combination of OCLP, macOS, or hardware. My take away - if you want to use TM for backups, which implies you will eventually want to restore/migrate to either an OCLP or non-OCLP Mac in the future, your most likely chance of success is to have backups taken when root patches are uninstalled. But, as with all things OCLP, YMMV.
Again, (as I keep saying) *aside from restores*, what would be the problem with TM backups?
 
Again, (as I keep saying) *aside from restores*, what would be the problem with TM backups?
If you want to hyper-focus on just the TM backup process itself, then, yes, TM backups will succeed with OCLP patches installed/applied. However, backups exist for when restore is necessary, do they not? Do you need that restore to be successful when the fateful day comes? If you are planning to use TM backups for a different goal then restore, now would be the time to say, and we can move on.
 
  • Love
Reactions: roronl
Smooth upgrade to Sequoia 15.7.6 RC on my HackBookPro6,2.

Screenshot 2026-04-13 at 9.40.52 PM.png

Unfortunately, OCLP 2.5.0n does not detect NVidia Tesla graphics as available patches. I'll be waiting for an OCLP release before patching Sequoia 15.7.6.
Screenshot 2026-04-13 at 9.40.02 PM.png

EDIT: The behavior of patch detection appears to be different with OCLP 2.5.0n and Sequoia 15.7.6 (24G711) RC... I reverted patches, rebooted and re-ran OCLP patcher. OCLP 2.5.0n detected the need for both Modern Wireless and Nvidia Tesla patches. Patches were applied using KDK 15.7.4 (manually installed).
Screenshot 2026-04-14 at 8.12.57 AM.png

After applying root patches, all that I have tested is working with the exception of <Shift><Command> screenshots (as was the case with Sequoia 15.7.5).

EDIT2: Sequoia 15.7.6 is incredibly responsive on this old 2010 laptop. Thank you OCLP Devs for keeping our old systems alive. What a fun hobby this has become.

EDIT3: Maybe OCLP 2.5.0n patch detection determined that Nvidia Tesla patches did not need to be re-applied after updating macOS Sequoia from 15.7.5->15.7.6. If that is the case, it would be the first time I can recall that the graphics patches did not need to be re-applied after a macOS update.
 
Last edited:
I was able to apply both Modern Wireless and Nvidia Tesla graphics patches to Sequoia 15.7.6 RC after reverting root patches. I have modified my previous post with the revised update status.
 
  • Like
Reactions: rehkram and jgleigh
I manually modified my OC EFI to include the new RestrictEvents.kext 1.1.7 (javascriptcore branch) and revpatch=jsc. macOS Sequoia 15.7.6 still boots 🙂. I don't test many websites with OCLP, but MacRumors and InsanelyMac are working just fine in Sequoia 15.7.6 with Safari Version 26.4 (20624.1.16.18.1).
 
  • Like
Reactions: macinfo and K two
It sure gets confusing, more so when there's no official record of exactly what the two 15.7.6 drops were. Their build numbers imply they are RCs 1 & 2, following hard on the heels of the final drop of the 15.7.5 RTM

Anyway, the latest one, 24G711, seems to be running OK on the two Macs here, details are in my spoiler. Both Macs are running Safari 26.5 (20624.2.1.19.2)
 
Last edited:
@Sven G Did you ever resolve your FileVault issues? I'm not testing FileVault with OCLP, but I am using FileVault with Open Core 1.0.7 and macOS Tahoe. If you are still having difficulties with FileVault, you may want to try upgrading your Open Core EFI to Open Core 1.0.7.
 
  • Like
Reactions: macinfo and Sven G
I found an easy solution to the missing button images in LibreOffice's toolbar (which I noticed last September).

Open LibreOffice, click on Preferences, then go to View. Check Force Skia software rendering and restart LibreOffice and the button graphics will show properly.

P.S. it's ok that "Use hardware acceleration" is grayed out at the top - LibreOffice 7.x uses Skia rendering so they should probably remove that hardware acceleration line from the preferences window.


Also, Microsoft accounts now work in Outlook (at least as of this current version, version 16.108). OneNote still can't connect to a Microsoft account.
 
Last edited:
@Sven G Did you ever resolve your FileVault issues? I'm not testing FileVault with OCLP, but I am using FileVault with Open Core 1.0.7 and macOS Tahoe. If you are still having difficulties with FileVault, you may want to try upgrading your Open Core EFI to Open Core 1.0.7.
It still prompts for the password twice, at boot and at login: and this second prompt shouldn’t be there, if FileVault works as it should. Is it easy to install a new version of OpenCore on top of OCLP 2.5.0n (never done that)…? Maybe it would be better to wait for the final version of OCLP 2.5.0…
 
Is it easy to install a new version of OpenCore on top of OCLP 2.5.0n ...
Yes, but it helps to know Open Core. You replace files in the OCLP-generated Open Core EFI with those from Open Core 1.0.7. Then you make sure that the Open Core config.plist is updated by validating with the ocvalidate utility. Alternatively, you could use OCAT (which I don't use) to do the Open Core upgrade for you. Once you learn how, the upgrade from one Open Core version to another is fairly simple.
 
  • Like
Reactions: Sven G
Yes, but it helps to know Open Core. You replace files in the OCLP-generated Open Core EFI with those from Open Core 1.0.7. Then you make sure that the Open Core config.plist is updated by validating with the ocvalidate utility. Alternatively, you could use OCAT (which I don't use) to do the Open Core upgrade for you. Once you learn how, the upgrade from one Open Core version to another is fairly simple.

OCAT is easiest way and will also update your kexts *wink lol I thought that when you on about RestrictEvents.kext lol
 
I'd be very surprised if OCAT updated RestrictEvents.kext to the javascriptcore branch created by Dhinakg. The javascript enhancement (requiring revpatch=jsc) is not yet merged with the main RestrictEvents.kext branch (which only increments the build version number).
 
Last edited:
OCLP is not dead:

Yeah I saw he put that out earlier.. I watched most of it. I knew it wasn't totally dead. I just thought maybe he might have some inside info. If he does, he's not saying. He specifically said he was keeping everything publicly known or something similar. I think he knows more.
 
I put Sequoia back on this again just to see if the HDCP issue was fixed. I went to go back to Monterey again and my TM backup would NOT work. What pain. The data was there but Migration Assistant just would NOT start the restore. Picked the TM drive and the backup on it and it just sat there for hours.. overnight.. just sat there. On both TM drives I use. I gave up and just setup the machine manually and copied all the apps and data over manually and had to setup everything manually. I think I only did that once before on my Air. Never had an issue on this MBP. I wonder what happened.
 
I put Sequoia back on this again just to see if the HDCP issue was fixed. I went to go back to Monterey again and my TM backup would NOT work. What pain. The data was there but Migration Assistant just would NOT start the restore. Picked the TM drive and the backup on it and it just sat there for hours.. overnight.. just sat there. On both TM drives I use. I gave up and just setup the machine manually and copied all the apps and data over manually and had to setup everything manually. I think I only did that once before on my Air. Never had an issue on this MBP. I wonder what happened.
"I wonder what happened?" There have been many posts on the various forums here saying, essentially, that a TM backup didn't work when someone had relied on TM, and only TM. Then there are posts saying it is best to have, or also have, a Carbon Copy Cloner <https://bombich.com/> or similar backup <https://www.maclab.tokyo/document/superduper/16800/>. What actually happened may never be revealed in detail, but is clear that TM doesn't alsways work, and it also seems clear that you didn't have that other, or alternative, backup. At least in this case you were lucky to have avoided a total "No Data" situation, and a manual copy restoration was possible. You could use the free 30 day trial of CCC to make a backup, just in case it ever becomes necessary. Personally, I think CCC is well worth the cost of a license, as it has saved me many such "manual copy hours" over the years. To be clear, I have no connection whatsoever with Bombich Software, the makers of CCC, just a very satisfied customer.
 
"I wonder what happened?" There have been many posts on the various forums here saying, essentially, that a TM backup didn't work when someone had relied on TM, and only TM. Then there are posts saying it is best to have, or also have, a Carbon Copy Cloner <https://bombich.com/> or similar backup <https://www.maclab.tokyo/document/superduper/16800/>. What actually happened may never be revealed in detail, but is clear that TM doesn't alsways work, and it also seems clear that you didn't have that other, or alternative, backup. At least in this case you were lucky to have avoided a total "No Data" situation, and a manual copy restoration was possible. You could use the free 30 day trial of CCC to make a backup, just in case it ever becomes necessary. Personally, I think CCC is well worth the cost of a license, as it has saved me many such "manual copy hours" over the years. To be clear, I have no connection whatsoever with Bombich Software, the makers of CCC, just a very satisfied customer.
Yeah. I've known about CCC for years. Just didn't think I'd have to start looking at it.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.