Thanks but....Try the Mr. Macintosh site.
macOS Sonoma Full Installer Database. Download Directly from Apple! - Mr. Macintosh
Download macOS Sonoma full installer with one click straight from Apple! Every version of Sonoma Beta & Final available all in one place!!mrmacintosh.com
Yes it’s metal 2isn't the 11,1 metal compatible? I would think your 11.4 is also and shouldn't have the non metal related issues.
I have a Late 2012 Mac mini (quad core i7; 16GB; 500GB SSD), running OCLP 1.1.0 and Sonoma 14.0. I never tried betas, nor the nightly builds. My goal was to do the OTA upgrade to 14.1 in place. At first I tried reverting root patches, but couldn’t download the update (not via Ethernet nor wifi) so I reapplied the root patches and was able to download and install.Updated to 1.1.0 and then tried updating to 14.1 - Now I'm stuck at about 50% loading bar at boot at the end of the updating process, and it won't progress. It's been over an hour. Any ideas on how to fix?
Mac Mini 2012
Thanks for the Mist suggestion. That works but there is an oddity (see screenshot). The Mist download says it is 23B74 but when OCLP 1.2n selects the resulting local macOS Installer in Applications, it "thinks" it is 23B69!Hi, Try using Mist available on GitHub. I've just downloaded 14.1 23B74 with it to update my other Mac.
View attachment 2302074
It did hang on a Mac Mini M2 too, power off and power on did work, it did finish installation. So the update is not smooth.Updated to 14.1 on a rMBP 10,1 2012. As others have reported, install hung at 30 % or so on last reboot.
Needed to safe boot to finish the install. All good after finishing the install in safe mode and applying patches in safe boot also.
Same here with iMac 14,1 - 21,5 inch late 2013. (OTA Update) OCLP 1.1.0 (Update Sonoma 14 to Sonoma 14.1).Updated to 14.1 on a rMBP 10,1 2012. As others have reported, install hung at 30 % or so on last reboot.
Needed to safe boot to finish the install. All good after finishing the install in safe mode and applying patches in safe boot also.
I had to follow the same basic procedure to get my MBP 9,1 to finish the update. I used the OTA update from system preferences and came back to find it stuck half way through startup. I ended up doing the same safe mode dance using 1.1.0 to install a fresh EFI and then revert patches and then install new 1.1.0 patches. Seems to be good now.I re-booted holding shift down to reach Safe Mode and uninstalled OCLP 1.20.Nightly EFI and installed new EFI using OCLP 1.1.0 release. Re-booted again holding shift and uninstalled patches. Re-booted again holding shift and installed 1.1.0 patches. Final re-boot as normal into Sonoma 14.1 (23B74) was successful.
same (machine) here...On my iMac 14.2 - 27 inch late 2013, i did the OTA update via system preferences from Sonoma 14 to Sonoma 14.1. Everything is ok and unlike my iMac 14,1- 21,5 inch late 2013, i was not forced to do a Safe Boot to finish the installation after the progress bar was blocked under the apple logo. The installation was quick despite the complete download of the update (more than 12 GB) and everything is OK.👌🏻 (OCLP 1.1.0)
This saved me. Thank you so much for this info. You saved me hours of work!I have a Late 2012 Mac mini (quad core i7; 16GB; 500GB SSD), running OCLP 1.1.0 and Sonoma 14.0. I never tried betas, nor the nightly builds. My goal was to do the OTA upgrade to 14.1 in place. At first I tried reverting root patches, but couldn’t download the update (not via Ethernet nor wifi) so I reapplied the root patches and was able to download and install.
I got to the reboot phase of the installation, and (having Verbose mode on), things seemed to go into an endless loop with a failed Setting BTCoex Config. This is a wifi module failure, so I guess the existing patch hadn’t carried forward and somehow it got stuck in the loop.
I let it run for quite a while since sometimes the screen would flash a longer message, but eventually gave up and powered off (hard reboot via power switch). A quick power on reboot showed the same behaviour.
So I next did a power cycle reboot, pressing Shift key to boot into Safe Mode. That took a while, but it finished booting. The About This Mac showed 14.1 so I figured the installation was finished. I then used OCLP to re-do the post-install root patches and that showed that there were two things waiting, including the wifi and graphics. I ran that, rebooted and things seem to be working again.
I created this account to share my experience, which is related to yours, but also to thank the Devs for a really amazing thing. I have been playing around with this on my old Mac mini for the past few weeks, first getting Sonoma running under 0.6.8 and then following through with the updates. Incredible effort, and a great job. Much appreciated and thank you. I hope my experience report is useful to others.
I checked and saw the oddity but the download was definitely 23B74. Guess it's down to OCLP 1.2.0 not knowing about the latest version because Apple published it after the Nightly was built.Thanks for the Mist suggestion. That works but there is an oddity (see screenshot). The Mist download says it is 23B74 but when OCLP 1.2n selects the resulting local macOS Installer in Applications, it "thinks" it is 23B69!
And it is not just the Mist download. When I finally got OCLP 1.2n to successfully download what it claimed to be 23B74, OCLP 1.2n then goes on to build 23B69 as above.Thanks for the Mist suggestion. That works but there is an oddity (see screenshot). The Mist download says it is 23B74 but when OCLP 1.2n selects the resulting local macOS Installer in Applications, it "thinks" it is 23B69!
I re-booted holding shift down to reach Safe Modeand uninstalled OCLP 1.20.Nightly EFIand installed new EFI using OCLP 1.1.0 release. Re-booted again holding shift and uninstalled patches. Re-booted again holding shift and installed 1.1.0 patches. Final re-boot as normal into Sonoma 14.1 (23B74) was successful.
Are you sure you installed OCLP to the internal disk?HI all, I've successfully installed Sonoma on a Macbook Pro 2017 (MacBookPro14,1) using OpenCore Legacy patcher 1.1.0 but when I want to boot from the internal NVMe drive instead of the USB key, the internal EFI partition doesn't show up at bootup with the OPTION key pressed even though I've installed OpenCore onto the internal hard drive (I think) with the post-install steps provided. Once installed onto the internal hard drive, it asks me to reboot with the OPTION key pressed but then there is no EFI partition to boot from?! I've tried MountEFI to no avail, etc. What could be the problem? SPI? Thanks all for your support and please redirect me elsewhere if this question should be asked elsewhere.