Sidebar Sidebar
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

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.
Just checking back in with more (bad) news. Still no luck getting Sonoma on my Mac Pro 5,1 even with OCLP 1.1 and 14.1 official built straight from the same machine running Monterey. I did several PRAM resets. I can get most of the way through the Sonoma install, even the second count-down black screen with xx minutes left. But it always ends up hanging 1/3rd of the way through the black screen/white Apple progress bar. Basically some of the very last steps hang at the same spot every time.

Monterey = works every time, very stable. I haven't tried Ventura.

After the failed Sonoma install, you can see in Recovery how it got most of the way there. I stuck a Monterey USB back in there, because I'm going to have to head on back to 12.7, unless you guys have other ideas?
SCR-20231029-qegm.png
 
Last edited:
BeatCrazy said:
Just checking back in with more (bad) news. Still no luck getting Sonoma on my Mac Pro 5,1 even with OCLP 1.1 and 14.1 official built straight from the same machine running Monterey. I did several PRAM resets. I can get most of the way through the Sonoma install, even the second count-down black screen with xx minutes left. But it always ends up hanging 1/3rd of the way through the black screen/white Apple progress bar. Basically some of the very last steps hang at the same spot every time.

Monterey = works every time, very stable. I haven't tried Ventura.

After the failed Sonoma install, you can see in Recovery how it got most of the way there. I stuck a Monterey USB back in there, because I'm going to have to head on back to 12.7, unless you guys have other ideas?
View attachment 2304075
Click to expand...
Since you have a couple of very good modern Macs, why not just run Monterey for a year, and later install Ventura to get further security updates. Many have succeeded though installing Sonoma on cMac Pros so we know it can be done. If you are willing to try again, download the latest OCLP nightly links (posted all over this thread). Use the bold phrase to search for that. That version has some applicable changes.
You may need to boot into safe mode to get the root patches done, but often a regular reboot is enough if you get stopped at that last stage. Make sure you have a good USB installer, and good luck.
 
Last edited:
  • Like
Reactions: BeatCrazy
MacinMan said:
I don't use FieVault, and yes I'm assuming you're referring to the image displayed with the clock after the apple and progress bar finishes and you come to the login screen. I am able to change that on both macs. at least I could on 14.0. I never tried 14.1 on my rMBP 11,1, so, I can only speak for the iMac 17,1.
Click to expand...
Yes, that screen...but clock? The bootscreen only shows the two user logins in front of the vineyard wallpaper to me. I know how that new clock looks like from the other login screens and screensaver but it's not on my bootscreen.
 
BeatCrazy said:
Just checking back in with more (bad) news. Still no luck getting Sonoma on my Mac Pro 5,1 even with OCLP 1.1 and 14.1 official built straight from the same machine running Monterey. I did several PRAM resets. I can get most of the way through the Sonoma install, even the second count-down black screen with xx minutes left. But it always ends up hanging 1/3rd of the way through the black screen/white Apple progress bar. Basically some of the very last steps hang at the same spot every time.

Monterey = works every time, very stable. I haven't tried Ventura.

After the failed Sonoma install, you can see in Recovery how it got most of the way there. I stuck a Monterey USB back in there, because I'm going to have to head on back to 12.7, unless you guys have other ideas?
View attachment 2304075
Click to expand...
I have 4 Mac Pro 5,1 working perfectly fine with 14.1 and oclp 1.1... Please see this video:
 
  • Like
Reactions: 0134168
luckyduke23 said:
Yes, that screen...but clock? The bootscreen only shows the two user logins in front of the vineyard wallpaper to me. I know how that new clock looks like from the other login screens and screensaver but it's not on my bootscreen.
Click to expand...
If you're not seeing the clock at the top of the login window, then you have more than a wallpaper problem.
 
  • Like
Reactions: luckyduke23
MacRumors3590 said:
I have 4 Mac Pro 5,1 working perfectly fine with 14.1 and oclp 1.1... Please see this video:
Click to expand...
I actually watched that vid earlier today :)

I'm not sure if any of this tips are applicable to me, as I can't even get to 14.0. I'm also only using Ethernet, not Wi-Fi.

I haven't tried applying the root patches while in Safe Mode per @davidlv so I will give that a shot next.
 
BeatCrazy said:
Just checking back in with more (bad) news. Still no luck getting Sonoma on my Mac Pro 5,1 even with OCLP 1.1 and 14.1 official built straight from the same machine running Monterey. I did several PRAM resets. I can get most of the way through the Sonoma install, even the second count-down black screen with xx minutes left. But it always ends up hanging 1/3rd of the way through the black screen/white Apple progress bar. Basically some of the very last steps hang at the same spot every time.

Monterey = works every time, very stable. I haven't tried Ventura.

After the failed Sonoma install, you can see in Recovery how it got most of the way there. I stuck a Monterey USB back in there, because I'm going to have to head on back to 12.7, unless you guys have other ideas?
View attachment 2304075
Click to expand...
What's the issue exactly?
 
  • Like
Reactions: MacRumors3590 and K two
MacinMan said:
If you're not seeing the clock at the top of the login window, then you have more than a wallpaper problem.
Click to expand...
yes, it seems all being connected to the same problem even if my machine runs normally....it's just the strange behaviour with the bootscreen...I have it with my two computers but will check if my brother has same situation...
 
Hey everyone, I’ve been having the problems with flashing login screen on iMac 13,1. This is what finally worked for me:

* Start in safe mode (shift +return at boot picker)
* Log in, go to settings >lockscreen>uncheck “show username and photo”
* reboot.

(For some models, there seems to be an issue with memojis on the lock screen.)
 
  • Like
Reactions: amaze1499
amaze1499 said:
Please be more specific, in case you want directions on how to solve the issue. Any error messages? What's the situation?
Click to expand...
No error messages and I literally outlined exactly where things got stuck and all possible relevant info in the post you quoted. Please re-read and TIA.
 
BeatCrazy said:
No error messages and I literally outlined exactly where things got stuck and all possible relevant info in the post you quoted. Please re-read and TIA.
Click to expand...
Are you able to proceed in safe mode (alt select volume to boot from then shift enter)? Or if possible, please provide a screenshot of the point of failure/hang booting in verbose mode (cmd + v).
 
amaze1499 said:
Are you able to proceed in safe mode (alt select volume to boot from then shift enter)? Or if possible, please provide a screenshot of the point of failure/hang booting in verbose mode (cmd + v).
Click to expand...
I have not been able to boot in safe mode (just hangs) but I was able to boot in verbose, screenshot attached.
Thanks for any guidance.
IMG_0207.jpeg
 
deeveedee said:
Upgrading Open Core requires the replacement of files in the Open Core EFI and a modification of the Open Core config.plist. After modifying the Open Core config.plist, you'll run Open Core's ocvalidate to confirm your config.plist changes.

You can perform the OpenCore upgrade manually (which is my preference) or you can use OCAT (search for it).

Files to be upgraded when upgrading Open Core are:
  • EFI/OC/Drivers/*.*
  • EFI/OC/OpenCore.efi
  • EFI/OC/Tools/*.*
  • EFI/OC/config.plist
In addition to upgrading Open Core, there may be Acidanthera kext upgrades for the kexts located in
  • EFI/OC/Kexts
OCAT will upgrade these kexts as well. You can look here to see which Acidanthera kexts have been upgraded. Note that OCLP intentionally does not upgrade AppleALC.kext for some Mac Models for compatibility reasons.

When you "Build and Install Open Core" with OCLP, you may lose Open Core and kext upgrades that you performed on your own (without OCLP) if OCLP has not yet upgraded OC and kexts.

EDIT: I recommend testing your new EFI on a bootable USB thumb drive before replacing the EFI on your SSD. After you confirm proper operation of your Mac with the new EFI, transfer your new EFI to your SSD.
Click to expand...
Hi Deeveedee, thanks for helping me but it seems I am more of a newbie than I originally thought.
You beginning by telling me to modify the config.plist, but which config.plist and what modification is necessary - I am totally at sea. The list of updates kexts isn't easy to determine either. Thanks
 
rob.shaw said:
Hi Deeveedee, thanks for helping me but it seems I am more of a newbie than I originally thought.
You beginning by telling me to modify the config.plist, but which config.plist and what modification is necessary - I am totally at sea. The list of updates kexts isn't easy to determine either. Thanks
Click to expand...
Best to stick with the Open Core EFI generated by OCLP.
 
  • Like
Reactions: olad
rob.shaw said:
Thanks, but that was what I did when I first started using the OCLP. In the meanwhile though it hasn't upgraded from 0.9.3 to 0.9.5
Click to expand...
Just a sanity check:

Some components used with OC are (co-)developed by OCLP developers. If there would be a good reason to upgrade OC within OCLP these developers would know and would certainly do so.

This is no Hackintosh thread, we are not doing this fix my EFI madness and we certainly do not encourage users to deviate from the standardized OpenCore setup created automatically by the OCLP app.

Support is limited to unchanged configurations. Experiences can only be shared when users have a common technical software base.
 
  • Like
Reactions: olad, perez987, Tockman and 4 others
Ausdauersportler said:
Just a sanity check:

Some components used with OC are (co-)developed by OCLP developers. If there would be a good reason to upgrade OC within OCLP these developers would know and would certainly do so.

This is no Hackintosh thread, we are not doing this fix my EFI madness and we certainly do not encourage users to deviate from the standardized OpenCore setup created automatically by the OCLP app.

Support is limited to unchanged configurations. Experiences can only be shared when users have a common technical software base.
Click to expand...
Thanks - makes a great deal of sense. Will wait on devs to upgrade via OCLP.
 
  • Like
Reactions: macpro_mid2014, K two and INK1
Noticed in OCLP v.1.2.0n, the removal of kexts in System/Library/Extensions which do not begin w/ HighPoint or SoftRAID during a macOS or OCLP Upgrade. Something I had been doing manually, to prevent the hang at 1/5th progress during the final progress bar and the need to boot into Safe Mode to complete an update. There are other effective changes to the update in v.1.2.0n. This version may greatly reduce the number of completion issues observed in previous versions. FWIW 😎
 
Last edited:
justperry said:
Fairly simple actually.
Panic CPU, that's game over for booting.
It misses a file, in your screenshot see
Reason: Tried: "blahblah...(No such file)
The system needs that file, without it it can't boot.
Click to expand...
I made the installer via the same machine. How do I fix?
 
Tried to install 14.1 OTA, bogged, next a full download and then install from
USB, bogged..
Get the screen below, refreshes every ten seconds or so from the top, it normaollyt
scrolls down the screen.
Any suggestions, tried AMFI On/Off, PRAM reset, no result, same outcome.

Pretty sure it's something to do with Bluetooth.
Heard there were problems before with macs on Sonoma, didn't have this before until now.


Solution:

I held down the Shift Key while booting up, that did the trick.


1234567890.jpg
 
Last edited:
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back