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
Does the boot loop happen on 14.1.1? I’m on 14.1 on an 11,4 with 1.2.1 and it’s working good but I get a random shutdown every 5-7 days. Maybe I should stay on 14.1 or or 14.1.1 worth it and a easy update?
In my case I had to do a clean install after trying 14.1.1. The problems were multiple and so weird I don't remember what-all went on. I went back to 14.1 + OCLP 1.2.1 and regained stability.
Given that 14.1.1 only includes fixes for apple silicon macs, enterprise stuff and no security fixes, I'd suggest staying on 14.1 personally. Give the OCLP devs time to find and fix issues for a new release of OCLP
I had a kernel panic just now on MBP11,1, the first unexpected thing I see with 14.1.1. 14.1 was perfectly stable.
OCLP 1.2.1 used for EFI and root patches.
Last edited:
Ventura 13.6.1 is my "production" macOS and I patch it with OCLP 0.6.8. I do my main work in Ventura 13.6.1, so my upgrade strategy for Ventura 13.6.1 remains very conservative (reliability and availability is most important to me for my production volume and I still prefer to work without Wi-Fi root patches - just my preference). Ventura 13.6.1 is my only Time Machine backed volume.
I currently maintain two APFS volumes for Sonoma on my MBP6,2 (in addition to APFS volumes for Big Sur, Monterey and Ventura). My "Sonoma release" volume (not enrolled in the Beta channel) remains on 14.1.1 patched with OCLP 1.2.1. My "Sonoma beta" volume is enrolled in the Beta channel (currently running 14.2 Beta 3) and I experiment with beta versions of Sonoma and OCLP, fully accepting that I may need to wipe my Sonoma beta volume and start over if I screw it up.
With Open Core's boot picker and the ease of launching multiple versions of macOS, I see no reason to treat versions of macOS and versions of OCLP post-install patches as mutually exclusive.
My currently installed versions of macOS and post-install patches (each combination in its own APFS volume) are currently as follows:
EDIT: When I switch from one version of macOS to another, I select "Reset NVRAM" from Open Core's extended boot menu before booting the new version of macOS.
I currently maintain two APFS volumes for Sonoma on my MBP6,2 (in addition to APFS volumes for Big Sur, Monterey and Ventura). My "Sonoma release" volume (not enrolled in the Beta channel) remains on 14.1.1 patched with OCLP 1.2.1. My "Sonoma beta" volume is enrolled in the Beta channel (currently running 14.2 Beta 3) and I experiment with beta versions of Sonoma and OCLP, fully accepting that I may need to wipe my Sonoma beta volume and start over if I screw it up.
With Open Core's boot picker and the ease of launching multiple versions of macOS, I see no reason to treat versions of macOS and versions of OCLP post-install patches as mutually exclusive.
My currently installed versions of macOS and post-install patches (each combination in its own APFS volume) are currently as follows:
- Big Sur (latest) - OCLP 0.6.8
- Monterey (latest) - OCLP 0.6.8
- Ventura (13.6.1) - OCLP 0.6.8
- Sonoma (14.2 Beta 3) - OCLP 1.2.1
- Sonoma (14.1.1 Release) - OCLP 1.2.1
EDIT: When I switch from one version of macOS to another, I select "Reset NVRAM" from Open Core's extended boot menu before booting the new version of macOS.
Last edited:
The complexity of the Open Core EFI generated by OCLP greatly depends on the Mac Model (SMBIOS) and the age of the Mac. It would have taken me much longer (if ever) to generate the required OC EFI for my MBP6,2 if I didn't have OCLP. I had already given up on anything beyond the DosDude patches for Catalina until OCLP made it possible to install Big Sur +. The Open Core kernel patches, kext injections (with Min/Max kernel), NVRAM injections, ... represent a monumental effort and accomplishment. I'm sure that those much smarter and dedicated than me could have done it, but not easily. In all of the Open Core / Hackintosh community, there are a handful of people that could have done with Open Core what the OCLP Devs have done.
Read the recent "reverting" posts more closely. We're discussing the differences between 1.2.1 and 1.3.0n which at the time of this post have no significant differences (including kexts). Besides, it is generally a mistake to oversimplify the OCLP-generated EFI differences to be simple differences in OC version and kext versions.
Long story: Because it relies on AMFI. But if SIP is lowered, AMFI does not work. And if AMFI does not work, the pop-ups to grant 3rd party apps access to peripherals like mics and camers don't pop-up, so you can't grant the permissions so they are not shown. Usually, the AMFIPass.kext should take care of this. But if AMFI is disabled by a boot-arg, this does not work.
Short story: Check boot-args and delete: amfi=0x80 if present. Or disable it: #amfi=0x80
Hello to All,
Some data points;
iMac 13,2 - updating internal (original fusion) drive to Sonoma 14.2 resulted in "login loop".
This behavior is reminiscent of the Monterey beta updates which elicited the same login loop, with underlying Window Server crash and ultimately related to Nvidia GPU driver problems (see https://github.com/dortania/OpenCore-Legacy-Patcher/issues/1004).
The external drive attached to the iMac 13,2 had 14.1.1 installed, and it seemed to function well, until iMac was left in sleep mode for 24 hrs; when reactivated, the finder had issues accessing applications. No kernel panics, as reported above by HVDS, but reboot did not completely eliminate the problem. I inadvertently updated the external drive to 14.2 beta3 (via injudicious use of update function within Silent Knight application [not an app. issue]) and, predictably, got stuck in login-loop.
Reinstalled 14.2 beta 3 to said external drive by connecting it to the MacBook Pro 5,2 via USB port, then launching 14.2 beta3 installer resident on the MacBook Pro's internal drive. External SSD (Samsung T7) was selected as the target drive. I was able to boot iMac 13,2 from external SSD, but did not apply post-install patches. While iMac boots fine, and I have access to all data on internal and external drives, there is no graphic acceleration. Applying patches causes the login-loop. Sonoma 14.2 beta3 package was downloaded via OCLP download function.
MacBook Pro 5,2 (late 2009) runs on Sonoma 14.2 beta 3 well, within hardware capabilities.
Exceptions are Safari, which is near unusable with Activity Monitor showing high CPU usage by Window server and application itself. Firefox is slow, but usable. I use Chromium for genera browsing; it is fast if not compatible with all websites and media types.
Hope above information may be of help.
Some data points;
iMac 13,2 - updating internal (original fusion) drive to Sonoma 14.2 resulted in "login loop".
This behavior is reminiscent of the Monterey beta updates which elicited the same login loop, with underlying Window Server crash and ultimately related to Nvidia GPU driver problems (see https://github.com/dortania/OpenCore-Legacy-Patcher/issues/1004).
The external drive attached to the iMac 13,2 had 14.1.1 installed, and it seemed to function well, until iMac was left in sleep mode for 24 hrs; when reactivated, the finder had issues accessing applications. No kernel panics, as reported above by HVDS, but reboot did not completely eliminate the problem. I inadvertently updated the external drive to 14.2 beta3 (via injudicious use of update function within Silent Knight application [not an app. issue]) and, predictably, got stuck in login-loop.
Reinstalled 14.2 beta 3 to said external drive by connecting it to the MacBook Pro 5,2 via USB port, then launching 14.2 beta3 installer resident on the MacBook Pro's internal drive. External SSD (Samsung T7) was selected as the target drive. I was able to boot iMac 13,2 from external SSD, but did not apply post-install patches. While iMac boots fine, and I have access to all data on internal and external drives, there is no graphic acceleration. Applying patches causes the login-loop. Sonoma 14.2 beta3 package was downloaded via OCLP download function.
MacBook Pro 5,2 (late 2009) runs on Sonoma 14.2 beta 3 well, within hardware capabilities.
Exceptions are Safari, which is near unusable with Activity Monitor showing high CPU usage by Window server and application itself. Firefox is slow, but usable. I use Chromium for genera browsing; it is fast if not compatible with all websites and media types.
Hope above information may be of help.
Last edited:
Because of this from Dortana in nightly commit #3467670.
| Due to the usage of amfi_get_out_of_my_way=1, macOS will fail to prompt users for special permissions upon application start as well as omit the entries in System Preferences. To work around this, we recommend users install tccplus to manage permissions. |
| Download TCCPlus](https://github.com/jslegendre/tccplus) |
I share with you guys my latest theme Flavours-ShadowRing
65 Linux distro included on that themes with 4 Windows Icons choicesSetup Flavours themes in config.plist ⬇︎
- Misc -> Boot -> HideAuxiliary: false
- Misc -> Boot -> PickerVariant: chris1111\Flavours-ShadowRing
- Misc -> Boot -> PickerAtributes: 145
- Misc -> Boot -> Picker Mode :-> External
- Misc -> Boot -> Timeout -> : 5
- Misc -> Boot -> ShowPicker: true
Every theme from chris111 is here on Github
Last edited:
Hi I successfully installed on my 2012 MBP but I get an out of device space error when trying to install OCLP to EFI partition on the hard drive. I mounted the EFI partition and it has a file named BootRecord and three folders named Apple, Boot and OC. I have no idea what I can safely delete in order to free some space. Any advice would be very much appreciated as right now I have to keep the USB thumb drive in the computer at all times.
"[Errno 28] No space left on device: '..../Build-Folder/OpenCore-Build/EFI/OC/config.plist' -> '/Volumes/EFI/EFI/OC/config.plist'")]
"[Errno 28] No space left on device: '..../Build-Folder/OpenCore-Build/EFI/OC/config.plist' -> '/Volumes/EFI/EFI/OC/config.plist'")]
What macOS version? What version of OCLP did you use to install that EFI folder on the hard drive? Same version as the OCLP installed to the USB?
That error message may be in error itself, as the EFI partition has very little copied to it, maybe 37MB?
My EFI has no Boot Record. Try deleting that and then run OCLP again to Build and Install to disk.
Well, you can create a small 100mb or so FAT volume , name it OCLP and put OCLP on that. That is what I do and is recommended for multi boot anyway.
By default, the EFI partition is 200 MB in size. Maybe there's some leftovers that are in the trash bin. But it can only be deleted if the volume is mounted. You can us MountEFI script to mount the partition: https://github.com/corpnewt/MountEFI
Then empty the trash bin if something is in there and check the size of the EFI/OC Folder.
Hello all.
I had Sonoma 14.0 working in a Mac Pro 2013 trashcan (6.1) with OCLP 1.0.1.
I wanted to update to Sonoma 14.1.1 and before doing the update, I wanted to first update the OCLP version 1.2.1, then restart and try to update later to Sonoma 14.1.1. The problem was that when I restarted, the mac no longer started, and it stayed stuck at the boot Apple logo.
What I can do?
Should I downgrade OPCLP to version 1.0.1?
Thank you very much for your help
all the best
I had Sonoma 14.0 working in a Mac Pro 2013 trashcan (6.1) with OCLP 1.0.1.
I wanted to update to Sonoma 14.1.1 and before doing the update, I wanted to first update the OCLP version 1.2.1, then restart and try to update later to Sonoma 14.1.1. The problem was that when I restarted, the mac no longer started, and it stayed stuck at the boot Apple logo.
What I can do?
Should I downgrade OPCLP to version 1.0.1?
Thank you very much for your help
all the best
Rather than downgrading, reboot in safe mode, reapply patches and boot again normally.
Last edited:
Hi Amaze1499.
I've tried rebooting in safe mode, but it doesn't boot in safe mode. I've press shift button while I select the Macintosh HD, but it still stuck with apple logo, and it does not boot in safe mode.
Restart. Hold Alt. Select bootvolume press and hold shift and press enter. Would that work perhaps?
There was a post on here or Discord that 14.1.1 and 14.2 was having issues with safe mode on certain systems as well as the login loop it broke both .
No. It does not work. I can't boot on safe mode.
Is it possible that this could work?
Thank you
Best regards
If you hold Alt on a patched Mac, you bypass OpenCore and load the native Apple Boot Loader instead. And of course it can't safe boot into an unsupported macOS version!
So you need to boot into Safe Mode from within OpenCore by holding Shift and pressing Enter. But depending on the drivers required to boot into the patched OS it might get stuck (especially when graphics drivers were patched in).
If you cannot revert the patches with the OCLP app itself, you could use online recovery as a last resort: Press space bar in the OpenCore menu to show Recovery and then reinstall the OS. This restores the system volume so all patching becomes undone, basically.
So you need to boot into Safe Mode from within OpenCore by holding Shift and pressing Enter. But depending on the drivers required to boot into the patched OS it might get stuck (especially when graphics drivers were patched in).
If you cannot revert the patches with the OCLP app itself, you could use online recovery as a last resort: Press space bar in the OpenCore menu to show Recovery and then reinstall the OS. This restores the system volume so all patching becomes undone, basically.
How do you press Alt on a Mac? It doesn't have an Alt key. Are you talking about a Hackintosh with a Windows keyboard?
You do not bypass OpenCore by holding down the Option key at boot up, that is how you get the Open Core boot picker.
In fact you have to press the Option key to get the Open Core boot picker, then first select (Tab key) the EFI icon and hit Enter (or mouse click) to boot the unsupported Mac. Then when the screen shows your bootable disks, choose the target disk (Tab key again) and hit Enter (or mouse click). When you hit Enter to boot the target disk, hold down the Shift key to get into safe mode. Unfortunately, the latest OCLP versions seem to have trouble with that function, depending on the hardware, as seen in this thread so many times. My iMac 15,1 is immune there (Whew!).