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.
justperry said:
Try a different USB stick, I had troubles with some.
Click to expand...
that's gonna be a challenge if there's not a working Mac to plug an new USB into - 14.1 and 14.2 are still throwing up lots of issues with the OCLP builds 1.1.0 and 1.2.0 (nightly) I've managed to get my 2016 15' MB Pro 13,3 working nicely with 14.1 beta (23B5067a) and I'm not even attempting an update during the current state of play. I've finally got a MacBook Pro 12,1 running 14.2 beta (23C5030f) but that was a nightmare journey of repeated USB builds of installer disk and multiple attempts to install, and one out of a dozen safe boot attempts that worked and suddenly it worked - still no idea what the magic sauce was but its running sweet now. Attempting for probably 10th time to update 2013 15" MacBook Pro but so far it hangs every time I attempt to log in - worked a treat on 14.0, but forgot to turn off the auto update of the OS and so it updated itself to 14.1 and broke itself. Now on a new USB build and we shall see if 14.2 and 1.2.0 might work from a fresh download of everything... progress bar 1/3rd along, cursor on screen and active, keyboard shift lock responsive so it's not died ye...t well there she goes - screen blanked - went to boot picker and restarted on the boot disk but 5-10% progress bar and temperature rising, fan noise and what looks like an unresponsive Mac - cannot get safe boot :/ bootefi-last-snapshot trick also not taking this now forwards..
 
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...
What video card is on your computer?
 
  • Like
Reactions: Ausdauersportler
idenis42 said:
What video card is on your computer?
Click to expand...
AMD RX 5700XT Anniversary Edition.

One more data point - my EFI build from OCLP 1.1 can support a Monterey 12.7 installation, no problem. I just re-installed.

So, it must have something to do with the 14.1 build from OCLP being not quite right.
 
amfi.png


Please send me CONFIG.PLIST.

First, you tick these as shown in the screenshot. And check it out.
 
deeveedee said:
Just curious - why?
Click to expand...
well if there are problems in the previous configuration that could have caused the failure to update or other problems in macOS, you could find them in the new update with critical consequences, possible malfunctions, etc...

if you find yourself faced with any problem in macOS, it is ADVISABLE not to restore from time machine but to do a clean installation and manual reconfigurations... you waste a little more time but you are sure of excluding any malfunctions due to old configurations

It is better to proceed like this, for me but not only, when significant problems arise
 
  • Like
Reactions: olad
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...
Since you're not using FileVault, this explains why things work for you. So far, I have not been able to find any users with active FileVault and OCLP who can confirm that they have the clock and a custom wallpaper on the boot login screen. So it is becoming increasingly clear that this combination is causing the "problem". I will check with more users. Any contrary feedback is highly appreciated.


UPDATE:
I meanwhile found somebody who deactivated FileVault and confirmed that suddenly the clock and customized wallpaper were available on the boot login screen again. Same applies to login list settings. This confirms that OCLP causes this issue when FileVault is activated.
 
Last edited:
hyperions said:
well if there are problems in the previous configuration that could have caused the failure to update or other problems in macOS, you could find them in the new update with critical consequences, possible malfunctions, etc...

if you find yourself faced with any problem in macOS, it is ADVISABLE not to restore from time machine but to do a clean installation and manual reconfigurations... you waste a little more time but you are sure of excluding any malfunctions due to old configurations

It is better to proceed like this, for me but not only, when significant problems arise
Click to expand...

the problem was fixed: I read a post here in forum, that a few old Macs have a problem with Sonoma 14.1 if the iCloud userpicture is an mimoji.

that was so simple, change the picture, and all problems are done. no restore, no new data install per hands :)
 
  • Like
Reactions: perez987 and hvds
luckyduke23 said:
Since you're not using FileVault, this explains why things work for you. So far, I have not been able to find any users with active FileVault and OCLP who can confirm that they have the clock and a custom wallpaper on the boot login screen. So it is becoming increasingly clear that this combination is causing the "problem". I will check with more users. Any contrary feedback is highly appreciated.
Click to expand...
If you don't have any top secret data, don't use FileVault.
 
  • Like
Reactions: olad and luckyduke23
EDIT: never mind - my issue likely stems from my Navi GPU - AMD Radeon RX 5700XT Anniversary Edition.
 
Last edited:
BeatCrazy said:
AMD RX 5700XT Anniversary Edition.

One more data point - my EFI build from OCLP 1.1 can support a Monterey 12.7 installation, no problem. I just re-installed.

So, it must have something to do with the 14.1 build from OCLP being not quite right.
Click to expand...
Have you ever checked the known legacy metal issues?
 
  • Like
Reactions: K two
BeatCrazy said:
EDIT: never mind - my issue likely stems from my Navi GPU - AMD Radeon RX 5700XT Anniversary Edition.
Click to expand...
It's so important! I didn't just ask you about the video card. And it's related to setting up OCLP. I need your CONFIG.PLIST file. I'll take a look!
 
I own a MacBook Pro 11,3 with Bigsur and I am looking to install Sonoma. I have heard that creating an external disk is necessary for the installation. However, I remember doing it over the air (OTA) once before. Is it possible to install Sonoma without an external disk?

Additionally, in case I need to format everything, how can I restore my data using Time Machine?
 
megaholti said:
the problem was fixed: I read a post here in forum, that a few old Macs have a problem with Sonoma 14.1 if the iCloud userpicture is an mimoji.

that was so simple, change the picture, and all problems are done. no restore, no new data install per hands :)
Click to expand...
yes, ok.. I also read that post and thought that might be the problem... sometimes problems are caused by trivial things but it is often difficult to identify them
 
  • Like
Reactions: andyorkney
Ok I solved my problem and boy do I feel a wee bit thick! So when I built the install file I didn’t specify the destination Mac, MacBook Pro 10,1 in this case as I interpreted the “host machine” label to be a generic build as opposed to building for the current “host” machine. Rebuilt the USB14.2 installer and the OCLP EFI for the specific MacBook Pro, booted from the new USB EFI and installed the 10,1 specific build of MacOS 14.2. Updated the Mac EFI rebooted, installed the OCLP patches and it’s all working.
 
  • Like
Reactions: hvds, K two and roronl
New question, different Mac (11,1) already running Monterey via OCLP.

I see that OCLP 1.1 support for Sonoma lists Kepler GPU compatibility as:
  • Kepler (GTX 6xx, GTX 7xx)
Is this exhaustive for Kepler support or is the K2100M also supported for Sonoma?
 
BeatCrazy said:
New question, different Mac (11,1) already running Monterey via OCLP.

I see that OCLP 1.1 support for Sonoma lists Kepler GPU compatibility as:
  • Kepler (GTX 6xx, GTX 7xx)
Is this exhaustive for Kepler support or is the K2100M also supported for Sonoma?
Click to expand...
If it is an MBP11,1, also have a look at https://forums.macrumors.com/thread...unsupported-macs-thread.2391630/post-32665367
There could be leftover kexts in /Library/Extensions which are cleared by 1.2 nightlies not 1.1.
 
  • Like
Reactions: K two and BeatCrazy
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