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
No issues with Mojave or High Sierra. Boot firmware is the latest available for this machine.
ABSOLUTETLY no. Moreover, you will not be able to use Migration Assistant. It works to migrate to same or newer macOS. Never older.
What is your operating system right now? What’s your set up? If on Catalina or higher then download OCLP , install then open and click “create installer”. There’s plenty of information online or with Mr Macintosh’s site. When creating the usb installer you can pick which operating system to install.
Installer created within OCLP on the host machine. Have tried reformatting in both HFS+ and APFS. Current OS is Monterey. I’ve tried the same with Mojave.
Have done all that. My setup is listed earlier in the thread. Have been using a 2014 iMac 5K on Sonoma without issues. The 5,1 Mac Pro has been a fussy journey, though.
Have you tried resetting the RAM? Really can´t tell what´s happening. I have two Mac Pro 5,1 , and I have installled so many times different macOs´s with OCLP and never a single error...
Try also pressing Alt and force to boot from the EFI partition.
Yep, I’ve tried all that. Multiple NVMe resets, removal of all PCIe cards except the GPU, different RAM, unplugged internal BT and Airport, multiple drive configurations, I’ve had the 1.3.0 Legacy Patcher install OpenCore is on its own dedicated drive in Bay 1, so the boot picker always loads first thing. After multiple different OpenCore configs, I finally ran the bootloader in verbose/debug mode to see if there would be any additional clues in the boot process. These lines are where things start to go sideways, and the boot process completely halts:
AAPL: #[EB.LD.LF|IN] 0 1 <"usr\\standalone\\OS.dmg.root_hash"> <"0">
AAPL: #[EB.LD.OFS|OPEN!] Err(0xE)
<"usr\\standalone\\OS.dmg.root_hash">
AAPL: #[EB.RH.LRH|P!] Err(0xE) <- EB.LD.LF
No, nothing of the sort, but I finally had success this evening!
Started by reformatting all internal drive containers to ExFAT, clean installed Mojave, then installed OCLP back to my OpenCore drive.
This time I configured OCLP with the 5,1 profile vs. defaulting to the Host Model. The SIP and security settings were much different with the 5,1 profile. Built a Ventura install disk from there, connected an Apple Extended USB KB to my hub, restarted, and… Ventura booted! Installed straight to a spare SSD, and ran with no issues.
Placed Sonoma on my McFiver drive after that, and no issues either, with the exception that my internal Broadcom WiFi/BT card is dead. Need to figure that one out, as I understand there are root patches which were supposed to address this?
Altogether, a huge pain, but happy I figured out the right set of options to FINALLY get things running and set up for testing! Hoping to squeeze a good year or two out of this old 5,1!
Same. I’m running a Broadcom AC/BT 4.2 card for Handoff; not the originals. I’ll rebuild my OpenCore and reinstall root patches to see if that can trigger it active in Sonoma.
@******* 🤔 Sure?
I have managed to downgrade within Ventura while keeping my data volume.
To do this, I simply deleted the volume containing the system in the hard disk utility.
❗️ DO NOT delete the volume group and/or data volume.
Then reinstalled macOS as normal using OCLP macOS Installer.
🤔 Maybe this also work for downgrades...
What about Carbon Copy Cloner – can we use it to restore the data volume on a clean install after a downgrade?
You can also simply use Disk Utility
Last edited:
@*******Sure?
I have managed to downgrade within Ventura while keeping my data volume.
To do this, I simply deleted the volume containing the system in the hard disk utility.
️ DO NOT delete the volume group and/or data volume.
Then reinstalled macOS as normal using OCLP macOS Installer.
What about Carbon Copy Cloner – can we use it to restore the data volume on a clean install after a downgrade?
Sure?
️ DO NOT delete the volume group and/or data volume.Normally on a downgrade your messages , photo library won’t be compatible after because it’s used in a newer version of the app even emails so you have to delete that database and resync with iCloud if you have it.
Oh yes, there is also this option.👍🏻
HOWEVER, the video shows the cloning of the entire volume group instead of just the data volume.
Isn't the problem that this doesn't work properly from macOS 13+ during migration? I have something in the back of my mind that this is why bootable clones can no longer be created by CCC.🤔
Okay, thanks for the hint!👍🏻
I don't know about others, but I have everything in iCloud. So there should be no problem with Messages, Mail and the photo library.😉
What other libraries are there that could cause problems? I'm thinking in particular of "Music Library.musiclibrary", for example, which is not saved in iCloud.🤔
OCLP Bugs
Photo App
⁉️ Are these bugs already known and are there any solutionsPlease note that my MacBook Pro is a base model, i.e. it is only equipped with an integrated graphics card.
👉🏻 my system: 15" MacBook Pro [rMBP 11,2 Mid 2014 / only Intel Iris Pro] / https://everymac.com/systems/apple/...-iris-only-mid-2014-retina-display-specs.html
👉🏻 macOS 14.2.1 + OCLP 1.3.0 / 1.4.0 Nightly
- Memories
Crashing by clicking on Reminders
👉🏻 since upgrade to Sonoma (can't remember if this was already a problem with Ventura)
- Portrait Pics
Crashing by click edit button
👉🏻 I only recently noticed this for the first time🤔.
I have now installed OCLP 1.4.0 nightly incl. root patches
(previously uninstalled root patches from 1.3.0 / reboot / 4x NVRAM reset / installed 1.4.0 / reboot / 4x NVRAM reset / post install / reboot / 4x NVRAM reset).
Unfortunately this did not solve the issue!😔
Last edited:
It is time to do a fresh instal when we change support , you Win stability, rapidity ...With Mac muliboot is very easy an the application don't need install except for some
Sorry for posting this to more than one unsupported Mac OS threads, but this is notable for all those OS:
Booting High Sierra with completely disabled s.i.p.
Fix and description: #1
Booting High Sierra with completely disabled s.i.p.
csrutil disable could possibly corrupt other OS' Preboot folders.Fix and description: #1
I'm having the same issue with some of my Mac Pro installs here. Added in the popular Fenvi T919 that has the newer Broadcom chipset that has worked fine in the past. BT seems to work, likely because it's a separate part of the chipset - but in System Info I just see unsupported network card and no wifi support...