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.
Hello, I am trying to install Sononma 14.0 on my CMP 3.1 (updated wifi and Vidéo card) with an installer on USB key made from OCLP 1.0.
The installer is well created, I restart on the USB key with the ALT key and launch the installation which starts... but it blocks on the first restart around 12 minutes and comes back to the recovery window all the time.
What did I miss? Thanks
 
Valid point, I don't need Sonoma on the Mac Pro. But in a couple of years, Monterey browser and app support will start to break. I'd rather give it another two years of life!

Thanks for the 1.1 tip. I'm in no hurry so maybe I'll wait for the public release of 1.1 and give it another shot. Just seems weird I can get Monterey on there no problem. But I have been paying enough attention to understand that Ventura/Sonoma presented way more dev difficulties.
I don't know the details, but I have heard that Ventura caused a lot of headaches, and that comparatively, Sonoma was much easier for the developers of OCLP. I am sure that it wasn't easy, but they did get the final version of OCLP out in good time! I suspect that was in spite of Apple's strange ways. I have OCLP 1.1 running on my iMac 15,1 and it feels like a supported machine, very stable. Granted I do not do anything demanding on that computer, just word processing and net stuff using Brave. Monterey will get security updates until the end of next year, so why worry now? Who knows what the world will be like in 2024 anyway, considering the escalating events in Ukraine and Israel, it sure doesn't bode well!
 
Last edited:
Hello, I am trying to install Sononma 14.0 on my CMP 3.1 (updated wifi and Vidéo card) with an installer on USB key made from OCLP 1.0.
The installer is well created, I restart on the USB key with the ALT key and launch the installation which starts... but it blocks on the first restart around 12 minutes and comes back to the recovery window all the time.
What did I miss? Thanks
You should see and select the EFI icon when you start up holding the OPTION key down (Alt key is the equivalent on a Windows keyboard), the select the macOS USB installer.
In some cases, you have to hold down the Option key again when the installer reboots and select the EFT icon and then the macOS installer icon again (the order sometimes gets out of sync).
Also, the OCLP HP has an update out to version 1.0.1, so why not use that?
 
I don't know the details, but I have heard that Ventura caused a lot of headaches, and that comparatively, Sonoma was much easier for the developers of OCLP. I am sure that it wasn't easy, but they did get the final version of OCLP out in good time! I suspect that was in spite of Apple's strange ways. I have OCLP 1.1 running on my iMac 15,1 and it feels like a supported machine, very stable. Granted I do not do anything demanding on that computer, just word processing and net stuff using Brave. Monterey will get security updates until the end of next year, so why worry now? Who knows what the world will be like in 2024 anyway, considering the escalating events in Ukraine and Israel, it sure doesn't bode well!
I think Sonoma is not easier to patch than Ventura, but the most difficult step was to go from Monterey to Ventura.
The next step is probably lower, with less under the hood changes and similar patching methods
 
  • Like
Reactions: olad and K two
Sonoma 14.1 beta 3 reverting patches comes in under 900mb same bugs as before no different than the others bugs everyone is experiencing on 14.0 all went ok on mid 2014 MacBook Pro credit to the Devs , Thankyou with OCLP 1.1n not experiencing the widgets crash or memories photo crash in the photos app.
 
  • Like
Reactions: grumpy_Garrett
Hello RogueB,
it looks to me that at least the first patching failure for your iMac 13,2 has to do with KDK not working correctly (this assumption can of course be wrong). The Python code which invokes KDK for rebuilding the kernel cache etc is on Github under resources/sys_patch/sys_patch.py lines 287 ff if I read it correctly.

Did the post-install patch try to load a KDK at all? (it should have used the one from 14.0b7 as closest match as the proper one for 14.0 release seems to be not yet there).
Maybe the problem goes away once the proper KDK is available and thus freshly loaded by the patcher.
Otherwise you could have a look at your /Library/Developer/KDKs and delete the KDK... folders which are in there, to force the patcher to freshly load whatever KDK seems appropriate.
I'm not sure I've seen this error before, but could be, in the early days of KDK usage by the patcher.
Hello hvds,

Regret the late response, and thank you for the insight.
I was under the impression that the iMac13,2 does not need KDK, but that might no be the case.

May I preamble with a cautionary tail regarding new(?) features in the Disk Utility, which allow erasure off all groups in an APFS container with one "click". I had to erase portions of the drive that did not involve Catalina (last natively supported OS), but inadvertently (or carelessly) I clicked on the selection in the Disk Utility (pop-up window) to Erase Group, rather then specific Volume. There was no "You sure" reminder. The "now" obvious result of that action was erasure of Sonoma and Monterey Volumes, which shared same container. The latter was an "unexpected" event.
The need to erase the volumes resulted from an error message from OCLP which, in a nut shell, advised that APFS structures needed to be rebuild (erased) in order for the root patch to be applies to any OS installation. The root cause of the (never before experienced error) was an attempt to update a beta installation, via a delta update, which required use of OCLP to revert root patching. The delta update worked, but caused APFS damage(?) which caused root patching via OCLP to fail.
Please, see post #1,203 on page 49 for screen shots of error messages.

I reinstalled only Sonoma, as there was no point in resurrecting Monterey; the latter had no advantages over Sonoma.
I used a USB thumb drive with fulll installer to install Sonoma 14.0 (official release), which was uneventful, then upgraded via OTA to Sonoma 14.1 beta1 and finally beta2. Both installed via latest OCLP 1.01n and OCLP 1.1n releases respectively. All seem well except the right side of the menu bar is missing some icons. Those icons become visible after clicking in the "empty" space, on the menus bar, where the icons would usually be located.

The MacBook Pro 5,2 was another matter. Upgrading to Sonoma 14.0 OTA was not an issue, though I needed USB thumb drive to install 14.1 beta1. However, I can not install 14.1 beta2 whether via OTA or full installer routes.
I tried multiple permutations of OCLP and install method, but it would not install. It fails on first reboot into the installer (chosen from boot picker) with progress bar stalling at the very beginning of the process. It is always followed by Kernel Panic message on reboot. Reminiscent of some of the early install processes when AMFI and "compat_check" had to be disabled.
This may be a fallout from having four operating systems on my MacBook Pr 5,2: Catalina, Monterey, Ventura and Sonoma - all fully functional within the hardware defined capabilities. I will wait for 14.1.Beta3 release and see if it may facilitate successful installation.

Finally, everyone(?) on this forum knows the risks of utilizing cutting edge "benevolent hacks" on our old machines.
Tremendous work by the developers of the OCLP - thank you to all.
 
Last edited:
I think Sonoma is not easier to patch than Ventura, but the most difficult step was to go from Monterey to Ventura.
The next step is probably lower, with less under the hood changes and similar patching methods
You contradict yourself.;)

-------------------------------------------------

BTW, is it safe now to do the OTA to 14.1b3
 
  • Like
Reactions: K two
Beta3 OTA much the same as b2 OTA on the Mini7,1 via OCLPv1.0.1, rock solid!! 🥳
Beta3.jpg
 
  • Like
Reactions: rehkram and hvds
I am still not able to change a Standard account, to an Admin account.

Recall, after updating a 2009 iMac from Monterey to Sonoma, using a OCLP v1.0.1 USB Key, ...the Admin account was somehow reverted to a Standard account. So I am simply not able to apply post install patches, which require an Admin password. And in General, I am not able to administrate this iMac.

I was able to use Target Disk Mode, and "I believe", successfully apply the OCLP v1.0.1 to the EFI of the Macintosh HD in that late 2009 iMac.

I believe this to be the case, since I can now booting the 2009 iMac without the USB Key, and directly off the EFI/Macintosh HD inside the 2009 iMac.

But again,
Attempt after attempt, to boot into Recovery Mode, still does not work.

Are there ANY Terminal Commands I can use from the Host MacBook Pro, targeting that now external Macintosh HD drive (while in Target Disk Mode), To ADD an Administration account to that iMac?

Know that I can see the entire file Structure of that iMac Macintosh HD, in the Finder, of the Host MacBook Pro.
 
Last edited:
I am still not able to change a Standard account, to an Admin account.

Recall, after updating a 2009 iMac from Monterey to Sonoma, using a OCLP v1.0.1 USB Key, ...the Admin account was somehow reverted to a Standard account. So I am simply not able to apply post install patches, which require an Admin password. And in General, I am not able to administrate this iMac.

I was able to use Target Disk Mode, and "I believe", successfully apply the OCLP v1.0.1 to the EFI of the Macintosh HD in that late 2009 iMac.

I believe this to be the case, since I can now boot the 2009 iMac without the USB Key, and directly off the EFI/Macintosh HD inside the 2009 iMac.

But again,
Attempt after attempt, to boot into Recovery Mode, still does not work.

Are there ANY Terminal Commands I can use from the Host MacBook Pro, targeting that now external Macintosh HD drive (while in Target Disk Mode), To ADD an Administration account to that iMac?

Know that I can see the entire file Structure of that iMac Macintosh HD, in the Finder, of the Host MacBook Pro.
Did you try this? From the terminal, and desktop of the target Mac, not in traget mode;
cd /var/db/
and
rm .AppleSetupDone <--- note there is no s after Apple, as in your previous post.

You can also get to /var/db/ using the Go menu in Finder, Go to Folder ... /var/db/

From the other Mac, in target disk mode: if you can see the entire file structure as you said.
Run Tinkertool (Google it) a free utility and use it to make invisible files visible. (requires relaunching Finder and is easily reversable.)
Then go to /var/db/ on the target Mac and delete the" .AppleSetupDone" file.
Boot the iMac and you should be able to make an admin account.
 
Last edited:
Here I have posted a Sonoma-compatible Wi-Fi solution that does not require root patching or any extra drivers / software. It works as long as your Mac has an Ethernet port.

Using instructions here, I build OCLP to patch Sonoma without Wi-Fi post-install patches (since I don't need and don't want the Wi-Fi post-install patches).
 
Last edited:
On the contrary, on my iMac 15,1, the beta 3 install gets a black screen with the white Apple symbol shining bright, and frozen. Had to bail out and reinstall 14.0 from a CCC backup, which was painless but took an hour. um....
Boot into any macOS other tha Sonoma - go to the Sonoma install in question> Library/Extensions ƒ, delete everything which begins with Apple, reboot and let the installation complete. OCLP will prompt to install Post-Install patches, do so and reboot as instructed. :cool:

works on mine.png
 
And if they didn't they do now.

Flagging myself for this OT post.
My intent was to share, that I was fully aware what likely trouble I was getting into when I entered the world of OCLP.
There is no room for complaint in my message; just a thought that others may learn in most harmless way possible, that is, from other users' mistakes.
However, from your context: Touché. Humor with a dose of cynicism.
 
  • Like
Reactions: deeveedee
Did you try this? From the terminal, and desktop of the target Mac, not in traget mode;
cd /var/db/
and
rm .AppleSetupDone <--- note there is no s after Apple, as in your previous post.

You can also get to /var/db/ using the Go menu in Finder, Go to Folder ... /var/db/
I tried it. The User (Dawn) has No Admin privileges. That is my issue.
It is a Standard account from which I launch Terminal.

This is a copy and paste from Terminal:

Dawn@Dawns-iMac-21 ~ % cd /var/db/
Dawn@Dawns-iMac-21 db % rm .AppleSetupDone
override rw-r--r-- root/wheel for .AppleSetupDone? y
rm: .AppleSetupDone: Permission denied
Dawn@Dawns-iMac-21 db %

You see I entered the: cd /var/db/
Then I entered: rm .AppleSetupDone
and Terminal Returned with:
override rw-r--r-- root/wheel for .AppleSetupDone?
To which I answered with a y
Then Terminal returned with:
rm: .AppleSetupDone: Permission denied

Now what?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.