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.
Do you mean delete revpatch=sbvmm (NVRAM > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102)? Clever.

Would this need to be manually edited after each OCLP > "Build and Install Open Core"?
Yes that is the line that tells OCLP to emulate a Virtual Machine, which is the mechanism for enabling updates OTA. Yes, each time you Build and Install Open Core it replaces the revpatch line so get everything the way you want it first, then edit out the line. When you are ready to install updates, just Build and Install, reboot and its back.

Also, I see lots of talk of keeping an old MacOS version on an external drive so you can install Firmware Updates, but I have done hundreds of Macs in the last few years and you can easily update the firmware from within an OCLP booted non-supported MacOS version as long as you extract the .scap files from the newest MacOS installer. Takes just a few minutes and no need for a backup OS or external drive to apply updates to.
 
Updated to 1.1.0 and then tried updating to 14.1 - Now I'm stuck at about 50% loading bar at boot at the end of the updating process, and it won't progress. It's been over an hour. Any ideas on how to fix?

Mac Mini 2012
 
macOS 14.1 (23B74) and KDK_14.1_23B5067a.pkg works like a charm with newest 1.2.0n on MP5,1 | RX580 | 990 Pro NVMe - big hug to the OCLP Dev - Team as always ;-) 😍 (OTA Update from 14.0 - reapplied OCLP patches after).
Update: KDK_14.1_23B74.pkg is also online so patched again with newest 1.2.0n without glitches...

(Some of my Macs esp. MacMini 6,2 and MacBookPro 12,1 need a safe Boot Shift+Enter in OCLP Boot Menu to finish the update and installing root patches in safe mode again - don't know the reason yet but it works in safe mode without problems)
 
Last edited:
  • Like
Reactions: deeveedee
you can easily update the firmware from within an OCLP booted non-supported MacOS version as long as you extract the .scap files from the newest MacOS installer.
@jowaju
How Exactly, please? and the newest MacOS installer? ...so from Sonoma 14.1??
 
  • Like
Reactions: olad
Same after reboot?

Shift+alt+cmd+ctrl + powerbutton

Hold alt reboot/start to select the right volume
Yes. Everything installed now hanging on reboot. Typically I’ll hit that screen then it will go to log in…I thought was there but it hangs at that point. Seems like video drivers aren’t loading
 
14.1 final runs as expected :cool:
14.1 final.jpg
 
Macbook pro 12,1 was running good on 14.1RC, updated to today's build and now its stuck booting, downgrading back to 14.0. also using oplc 1.2.0 nightly
 
Same after reboot?

Shift+alt+cmd+ctrl + powerbutton

Hold alt reboot/start to select the right volume
Okay thanks...but what I did was reboot, held down the shift key and it must have bypassed the video drivers (safe mode). Immediately there was an error stating "Microsoft server not responding". I believe this is from Office 2021. I should have closed that down completely but I forgot. I was able to reinstall 1.1.0 and then reboot. All seems good...
 
Memories seems to be working for me, I was able to view them and then I double clicked on one and it started playing a slideshow with music. 14.1, 1.1.0 patcher iMac 17,1
Everything else is fine in photos--I can edit, view locations, etc. But this is what I get for "memories" (I'm on a MBP 11,4)

ranslated Report (Full Report Below)
-------------------------------------

Process: Photos [1411]
Path: /System/Applications/Photos.app/Contents/MacOS/Photos
Identifier: com.apple.Photos
Version: 9.0 (610.3.110)
Build Info: Photos_Apps-610003110000000~44
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2023-10-25 16:21:10.9624 -0400
OS Version: macOS 14.1 (23B74)
Report Version: 12
Anonymous UUID: 367B6810-04F5-4D49-F6CC-8FF0D6118A0D


Time Awake Since Boot: 1500 seconds

System Integrity Protection: enabled

Crashed Thread: 14 Dispatch queue: com.apple.photos.metalrenderer-compile

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000

Termination Reason: Namespace SIGNAL, Code 4 Illegal instruction: 4
Terminating Process: exc handler [1411]

Application Specific Backtrace 0:
 
Everything else is fine in photos--I can edit, view locations, etc. But this is what I get for "memories" (I'm on a MBP 11,4)

ranslated Report (Full Report Below)
-------------------------------------

Process: Photos [1411]
Path: /System/Applications/Photos.app/Contents/MacOS/Photos
Identifier: com.apple.Photos
Version: 9.0 (610.3.110)
Build Info: Photos_Apps-610003110000000~44
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2023-10-25 16:21:10.9624 -0400
OS Version: macOS 14.1 (23B74)
Report Version: 12
Anonymous UUID: 367B6810-04F5-4D49-F6CC-8FF0D6118A0D


Time Awake Since Boot: 1500 seconds

System Integrity Protection: enabled

Crashed Thread: 14 Dispatch queue: com.apple.photos.metalrenderer-compile

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000

Termination Reason: Namespace SIGNAL, Code 4 Illegal instruction: 4
Terminating Process: exc handler [1411]

Application Specific Backtrace 0:
I have an 11,1 MBP 13" late 2013. I had Sonoma on it, but decided to put the stock install of Mavericks on it until I decied what I wanted to do with it.
 
  • Like
Reactions: mikelets456
Okay thanks...but what I did was reboot, held down the shift key and it must have bypassed the video drivers (safe mode). Immediately there was an error stating "Microsoft server not responding". I believe this is from Office 2021. I should have closed that down completely but I forgot. I was able to reinstall 1.1.0 and then reboot. All seems good...
Thanks! I got stuck at bootup and did what you said and held down shift for Safe Mode. That got me to login and received the same exact error of "Microsoft server not responding". After it finished updating, I installed and ran 1.2.0n OCLP and post install patches and rebooted. Now it boots into OS without getting stuck at startup. Much appreciated!
 
Cannot DL 14.1 final using 1.1.0 without this error (both Ethernet and Wi-Fi)
 

Attachments

  • Screenshot 2023-10-26 at 5.19.22.png
    Screenshot 2023-10-26 at 5.19.22.png
    388.4 KB · Views: 77
Updated from 14.1 RC (23B73) to 14.1 Release using full installer 12.89GB.


Screenshot 2023-10-25 at 19.02.06.png


All seemed to go well until the last installer window hung at 50%, as others have reported. I re-booted holding shift down to reach Safe Mode and uninstalled OCLP 1.20.Nightly EFI and installed new EFI using OCLP 1.1.0 release. Re-booted again holding shift and uninstalled patches. Re-booted again holding shift and installed 1.1.0 patches. Final re-boot as normal into Sonoma 14.1 (23B74) was successful.

I'm not sure whether my iMac 13,2 didn't like the GPU drivers in 1.2.0 Nightly or it was a coincidence!

Screenshot 2023-10-25 at 22.03.15.png
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.