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 14 Sonoma on Unsupported Macs Thread
- Thread starter dhinakg
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Here is a new thread for Sonoma-compatible Wi-Fi that does not require OCLP. Please post your proven/tested Wi-Fi alternatives in this new thread before the thread fills up. 
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:
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?
Releases · dortania/OpenCore-Legacy-Patcher
Experience macOS just like before. Contribute to dortania/OpenCore-Legacy-Patcher development by creating an account on GitHub.
github.com
I don't know either, but I suspect the "comparatively easy" Sonoma development was because the Devs had already tackled the hard stuff with Ventura (Wi-Fi excluded).
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
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.
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:
You contradict yourself.
-------------------------------------------------
BTW, is it safe now to do the OTA to 14.1b3
NoYou contradict yourself.
-------------------------------------------------
BTW, is it safe now to do the OTA to 14.1b3
Beta3 OTA much the same as b2 OTA on the Mini7,1 via OCLPv1.0.1, rock solid!! 🥳
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....
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.
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:
OK, what's a good section on Macrumors to get help with Linux. I did some searching and found a guide on Dortainia for setting up OpenCore to boot linux but need to find people who can help me with the process.
This is the article I found, and am referencing and looking for help with. https://dortania.github.io/OpenCore-Multiboot/oc/linux.html#method-a-openlinuxboot
This is the article I found, and am referencing and looking for help with. https://dortania.github.io/OpenCore-Multiboot/oc/linux.html#method-a-openlinuxboot
Last edited:
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).
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:
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.
What are you charging to certify our Macs with the official "Works on my machine" certificate of approval
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.
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?
Try
cd /var/db
sudo rm .AppleSetupDone
Another;
- Boot into Single User Mode: Start/restart your Mac. As soon as you hear the startup tone, press and hold ⌘ + S until you see a black screen with white lettering. (If you end up back on the login screen after a flash of the black screen with white lettering, enter your password and it will return to the black screen.)
- Check and repair the drive by typing /sbin/fsck -fy then ↩ enter - as directed by the on-screen text.
- Mount the drive as read-write by typing /sbin/mount -uw / then ↩ enter.
- Remove the Apple Setup Done file by typing rm /var/db/.AppleSetupDone then ↩ enter.
- Reboot by typing reboot then ↩ enter.
- Complete the setup process, creating a new admin account.
did you try deleting that file using the other Mac and target disk mode?
or this:
Last edited: