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
Hey guys, this has been happening to me since I first installed Sonoma on my 2017 MBA 7,2 back in August. (since Sonoma beta 4 and OCLP 0.6.9n). Sometimes, after the machine boots up, I get a black screen. No lock screen. Nothing. But, if I type in my password and press enter at that black screen, after a while, it takes me to the desktop. This doesn't happen all the time, sometimes I get the lock screen, sometimes I get that black screen. Sometimes I get several boot-ups in a row with the lock screen, and vice versa. And no, I'm not using the aerial wallpapers, although the issue persists on both kinds. Haven't tried a clean install, but I have re-installed macOS. And I should note, when the system isn't root patched, this never happens. I really have no idea what might be causing this. If anyone has had a similar problem and has resolved it, please enlighten me. Thanks guys!
Thanks again for the test.
Tried it right now and no more then 1080p... but maybe is a limit of the screen, and YouTube doesn't go automatically above my maximum resolution.
This evening I will try with a 4k external monitor and see if it goes to higher resolution.
In any case, thanks again!
I have a question about FileVault. Recently I started an attempt to encrypt my startup volume with FileVault. It is a very long process depending on the volume size. In between, when encryption was already enabled, I had to reboot. But then the shock: The gray prohibitory sign appeared with the link support.apple.com/mac/startup on a black screen during the boot process and I could not boot from the disk anymore.
Fortunately I had backups and so by reinstalling Sonoma and restoring my backup I am back to the status quo.
What could have gone wrong? Normally a volume is not locked until the encryption is complete. What else could be done when something like this happens?
Fortunately I had backups and so by reinstalling Sonoma and restoring my backup I am back to the status quo.
What could have gone wrong? Normally a volume is not locked until the encryption is complete. What else could be done when something like this happens?
The OCLP devs made some very effective changes on 10-15-23, and again on the 16th, so you might try that if you haven't already. That last change finally enabled my iMac 15,1 to install Sonoma 14.1 b3 correctly, where before that, it always crashed after the post install root patches. Some very impressive reverse engineering going on out there!
Your situation must be machine specific.
MBP11,5 OCLP1.1.0n (16Oct) just updated to Sonoma 14.1b3 - upon running boot update now will not load desktop after selecting EFI - totally black screen and never comes back. Can anyone suggest a solution - do I try a USB update using a USB boot disk? Would that work?
On an iMac 15,1, with that situation before I finally had success, I had to boot from an external drive with Ventura installed, wipe the affected internal SSD, use CCC to copy a Somoma backup to the internal SSD and re-install Sonoma 14.0 using an Apple OS installer in the application folder on the internal SSD. Sounds complicated but it was actually easy and not so time consuming.
Do you have a CCC backup?
Thanks - that is most probably what I will have to do. I think I screwed up by doing a Sonoma 14.1b3 update via OTA. Therefore trying a new install via OCLP and USB installer. Might have to do exactly what you suggested. Thanks again.
You could also try booting into safe mode by holding down shift. It has saved my oclp installs countless of times.
As already mentioned USB installer 14,1b3 now works with MBP5,1 and latest oclp 1,1n. But big surprise. Final boot of 14,1b3 comes with USB support - no more need of usb2.0 hub and graphic hardware support without post patches. Post patches make no difference.
Thanks, tried reinstalling the b3 via OCLP and it worked - all OK now. Having tried all applications but now it is booting to desktop I doubt if too many problems. Thanks for your advice.
Hello to All,
MacBook Pro 5,2 (mid 2009) report
Successful installation of Sonoma Beta 2 via a USB Thumb drive, and subsequent attempt to install Sonoma Beta3 via OTA method.
USB thumb drive contained previously created Sonoma Beta2 installer , however, I mounted its EFI partition, deleted the contents within, and used latest OCLP 1.1n from 10.15.23 to install new EFI. Laptop was connected to internet via Ethernet port, which remains active, unlike WiFi, throughout the process.
Latest OCLP now “requires” that external keyboard and mouse be attached to the computer USB port, via an external hub, from the beginning of the boot process into the thumb drive which has Sonoma installer. Icons representing keyboard and mouse flash on black screen until external hub, with both items attached, is plugged into USB port of the laptop. Previously the external hub solution (credit HVDS) was needed only after installation of the OS, in order to log into the new installation and apply OCLP patches. Once external USB hub setup was completed, the Thumb drive booted into standard recovery partition and allowed selection of Sonoma Beta2 to install onto internal disk. Installation took some time, with short periods of time where it appeared to stall, but in fact was parsing through installation files and continued in short order. On completion of the installation process I was able to log into Beta2 and successfully apply patches. Note: during patching process OCLP automatically downloaded latest KDK from Apple and integrated it in the patching process. Hence, importance of Ethernet connection during patching process.
Sonoma 14.1 beta#3 OTA install:
I tried to install Beta3 via OTA method (there is no full installer available). That installation seemed to proceed fine, and completed through multiple reboots, but on final reboot installation stalled with screen showing folder and blinking question mark; a sure sign of boot disk (EFI?) corruption. This was reminiscent of another time (Monterey installation) where same problem occurred. Diskutil list showed fractured container system, but viable pre-boot partitions.
Recovery:
Re-Installed Catalina via Dosdude1’s patcher, which is not reliant on the OCLP. Catalina was fully re-installed onto its old partition (the latter was still visible in recovery mode while booted into Catalina Install thumb drive). Installation process itself went well, as did subsequent patching. Next step was to download OCLP patcher; newest available on 10.15.23 (OCLP 1.1 n). Once downloaded, I was able to build and install OCLP onto the internal disk. This process replaced EFI content, which appeared to be corrupted. On reboot all partitions and OS installations, Monterey, Ventura, Sonoma 14.1 beta2 and Catalina were accessible and fully functional. There was no data loss on any of the partitions. OCLP Patching process went without issues. I keep Catalina on the MacBook Pro 5,2 because it does not need OCLP for installation, and as evidenced above, is an immeasurable help in recovering from EFI misadventures. Catalina is also (currently) the only OS X iteration which allows direct content streaming, e.g. via Apple TV, on non-metal machines(?)
Hope this may be of help to someone in similar circumstances; consider recovery process before formatting the whole drive.
Thank you to the developers for constantly evolving the OCLP.
There may be a new OCLP 1.1n version(s), which may alleviate or prevent Beta3 install problems noted above.
P.S. There were no issues installing Sonoma 14.1 betas 1-3 on iMac 13,2.
MacBook Pro 5,2 (mid 2009) report
Successful installation of Sonoma Beta 2 via a USB Thumb drive, and subsequent attempt to install Sonoma Beta3 via OTA method.
USB thumb drive contained previously created Sonoma Beta2 installer , however, I mounted its EFI partition, deleted the contents within, and used latest OCLP 1.1n from 10.15.23 to install new EFI. Laptop was connected to internet via Ethernet port, which remains active, unlike WiFi, throughout the process.
Latest OCLP now “requires” that external keyboard and mouse be attached to the computer USB port, via an external hub, from the beginning of the boot process into the thumb drive which has Sonoma installer. Icons representing keyboard and mouse flash on black screen until external hub, with both items attached, is plugged into USB port of the laptop. Previously the external hub solution (credit HVDS) was needed only after installation of the OS, in order to log into the new installation and apply OCLP patches. Once external USB hub setup was completed, the Thumb drive booted into standard recovery partition and allowed selection of Sonoma Beta2 to install onto internal disk. Installation took some time, with short periods of time where it appeared to stall, but in fact was parsing through installation files and continued in short order. On completion of the installation process I was able to log into Beta2 and successfully apply patches. Note: during patching process OCLP automatically downloaded latest KDK from Apple and integrated it in the patching process. Hence, importance of Ethernet connection during patching process.
Sonoma 14.1 beta#3 OTA install:
I tried to install Beta3 via OTA method (there is no full installer available). That installation seemed to proceed fine, and completed through multiple reboots, but on final reboot installation stalled with screen showing folder and blinking question mark; a sure sign of boot disk (EFI?) corruption. This was reminiscent of another time (Monterey installation) where same problem occurred. Diskutil list showed fractured container system, but viable pre-boot partitions.
Recovery:
Re-Installed Catalina via Dosdude1’s patcher, which is not reliant on the OCLP. Catalina was fully re-installed onto its old partition (the latter was still visible in recovery mode while booted into Catalina Install thumb drive). Installation process itself went well, as did subsequent patching. Next step was to download OCLP patcher; newest available on 10.15.23 (OCLP 1.1 n). Once downloaded, I was able to build and install OCLP onto the internal disk. This process replaced EFI content, which appeared to be corrupted. On reboot all partitions and OS installations, Monterey, Ventura, Sonoma 14.1 beta2 and Catalina were accessible and fully functional. There was no data loss on any of the partitions. OCLP Patching process went without issues. I keep Catalina on the MacBook Pro 5,2 because it does not need OCLP for installation, and as evidenced above, is an immeasurable help in recovering from EFI misadventures. Catalina is also (currently) the only OS X iteration which allows direct content streaming, e.g. via Apple TV, on non-metal machines(?)
Hope this may be of help to someone in similar circumstances; consider recovery process before formatting the whole drive.
Thank you to the developers for constantly evolving the OCLP.
There may be a new OCLP 1.1n version(s), which may alleviate or prevent Beta3 install problems noted above.
P.S. There were no issues installing Sonoma 14.1 betas 1-3 on iMac 13,2.
Last edited:
MBP5,2: used latest 1.1.0n for new EFI and root patching (last commit Synch PatcherSupportPkg to 1.4.2). NVRAM cleared afterwards.
All fine, except:
- no "show desktop" functionality as before (windows won't go away)
- Photos always crashes with illegal instruction, log attached.
No intention to use this machine in earnest anymore, just for verification.
Last edited:
In regard to "installing Beta3 via OTA method (there is no full installer available)", If you start up OCLP 1-16-23 and choose the "Create USB Installer" function, then the "Download macOS installer" and put a tick on the "Older versions and Betas" you will see the "macOS Sonoma Beta 3 23B5067a" there. Just follow the prompts!
My Mac Pro 5.1 just updated to Sonoma via OCLP 1.1, everything so far looking good.
I have two seperate drives, one for running the Sonoma and another is High Sierra.
Yesterday, something wrong with the High Sierra drive and needed to replace a new HD with OS reinstalled.
However, I tried to boot the Sonoma drive by pressing OPTION key during the boot, I saw Sonoma DATA (instead of Sonoma System) and EFI Drives, I clicked the EFI, but did not see any Sonoma Start up disk there.
I did a Reset NVRAM, and did not solve the issue, and needed to reinstall the Sonoma OS.
Now it is back to normal, I just would like to know is it normal ?
Thank you, and sorry if this question has been asked before, I did couple searches and did not see any.
I have two seperate drives, one for running the Sonoma and another is High Sierra.
Yesterday, something wrong with the High Sierra drive and needed to replace a new HD with OS reinstalled.
However, I tried to boot the Sonoma drive by pressing OPTION key during the boot, I saw Sonoma DATA (instead of Sonoma System) and EFI Drives, I clicked the EFI, but did not see any Sonoma Start up disk there.
I did a Reset NVRAM, and did not solve the issue, and needed to reinstall the Sonoma OS.
Now it is back to normal, I just would like to know is it normal ?
Thank you, and sorry if this question has been asked before, I did couple searches and did not see any.
You wouldn't be the first to find that Sonoma and High Sierra DO NOT play well together. Best not to have a High Sierra disk/volume in your MP5,1 at the same time as your Sonoma disk. Same is true for Big Sur, Monterey, Ventura - I have found that they also do not play nice with High Sierra. That's based on my limited experience - YMMV.
EDIT: I have also found that HS has different disk "preferences" than Big Sur, Monterey, Ventura and Sonoma. SSDs that work with HS for me do not work with Big Sur+ and vice versa. Never bothered to figure out why - just found working SSDs through trial and error.
If you're interested, you can search for the technical explanation.
EDIT2: If you need 32-bit apps, I think you should be safe with Mojave.
Last edited:
Known issue with High Sierra booting on systems with other post Catalina installations. High Sierra corrupts the preboot partition, on reboot the image chosen by OC to display those installations is set to the High Sierra image and sometimes the name points to the Data container. You can fix this either manually (look up the older GitHub issue from 2021, it is a complex fix) or just re-install the same post Catalina version on top of the existing one - this will fix the preboot, again. This is not an OCLP or OC issue, it is a High Sierra bug which will never be fixed.
There are only two (three) permanent solutions:
Do not boot High Sierra or pull all (OCLP) discs before doing so.
Or simply use Mojave instead of High Sierra - it is the last supported macOS on your Mac!
Last edited:
I've wondered about the High Sierra image/boot thing for a while. Good to get more insight on it. I've been just opening the preboot volume and manually replacing the image via right click + Get info.
I've always had High Sierra on a OWC SSD, and have maintained that as the OEM OS while I do whatever tinkering I do with unofficial versions just incase when the error happen. Most errors were because of me rushing things, some were because of betas and such.
Ultimately with that said, I'm surprised I haven't had more issues with booting. I routinely switch back and forth, for updates and or troubleshooting. It just works 🤷♂️
UPDATE:
While it "just works" lol, I do have the black screen from wake issue still, even in the new nightly. Entering password like normal logs me in. Not a huge hassle.
Last edited:
Thanks Olad, have been able to get it right now by loading an old Ventura drive and then updating the Mac SSD with a OCLP generated Sonoma 14.1 b3 image - works perfectly now. Thanks for your input
Succesfully installed on a partition of my main internal ssd, Mac mini late 2012, Sonoma 14.1.b3 OCLP 1.1.0