macOS 14 Sonoma on Unsupported Macs Thread

[TOM1211]

Random post really but I update my garmin satnav which seems to be dropping support for Big Sur in November which seems crazy to me needing a new os to update a satnav anyhow thanks to OCLP I don’t need a new Mac to update my satnav lol .

 

[wwise]

Apologize if this has been covered already - if so please just refer me but does OCLP 1.1.0 allow upgrading to Sonoma 14.1 via the System preferences? Or do I need to create a USB installer? I seem to recall mixed responses with 1.0.1.

I'm currently on a cMP 5,1 running Monterey 12.7.1 and just upgraded to 1.1.0.

Thanks so much

 

[davidlv]

Apologize if this has been covered already - if so please just refer me but does OCLP 1.1.0 allow upgrading to Sonoma 14.1 via the System preferences? Or do I need to create a USB installer? I seem to recall mixed responses with 1.0.1.

I'm currently on a cMP 5,1 running Monterey 12.7.1 and just upgraded to 1.1.0.

Thanks so much

You probably would be best advised to create a USB installer using OCLP.
First make sure you have a backup, CCC, SuperDuper, Time Machine etc.
You can try the OTA method, and if it doesn't work, boot from the OCLP USB and wipe the target disk, then install and use the Migration Asssitant app at the end of the install to get your data installed.
If you have the space on your internal SSD, make a new Volume and use that as the target destination when booting from the USN installer.
There have been many posts related to installs on the cMP 5,1. Look for them for reference before doing anything.
That machine is a special machine, and it has its special characteristics (I had a CMB 4,1 once).

 

[deeveedee]

Apologize if this has been covered already - if so please just refer me but does OCLP 1.1.0 allow upgrading to Sonoma 14.1 via the System preferences? Or do I need to create a USB installer? I seem to recall mixed responses with 1.0.1.

I'm currently on a cMP 5,1 running Monterey 12.7.1 and just upgraded to 1.1.0.

Thanks so much

If you want to keep your current Monterey macOS while you test a new one, add an APFS volume and install the new macOS there. This allows you to leave your working Monterey untouched while you experiment. Also be sure to confirm Sonoma support for your graphics.

EDIT: Read this.

 

[macpro_mid2014]

Clever. What made you think to do this? Do you know what feature you lost when you changed FeatureUnlock from Enabled to Partial? Well done.

I found a two pages macrumors thread from 2021 where some OCLP developers (I don't remember who, sorry) discuss about a possible memory issue in Haswell Macs causing similar issues that I was having and that those issues could be eliminated by setting FeatureUnlock to Partial.

 

[amiromari]

just successfully updated my late 2015 27" iMac from Sonoma 14.0 to Sonoma 14.1 with OCLP 1.1.0.... Had to hold down the shift key when rebooting to put it into safe mode then it successfully completed the update process.....once completed the machine was very slow initially as the root patches needed to be reapplied, once patches reapplied works perfectly. **please note I was connected to to my router via LAN cable during the process as wifi will not work without root patches**

 

[David403]

You probably would be best advised to create a USB installer using OCLP.
First make sure you have a backup, CCC, SuperDuper, Time Machine etc.
You can try the OTA method, and if it doesn't work, boot from the OCLP USB and wipe the target disk, then install and use the Migration Asssitant app at the end of the install to get your data installed.
If you have the space on your internal SSD, make a new Volume and use that as the target destination when booting from the USN installer.
There have been many posts related to installs on the cMP 5,1. Look for them for reference before doing anything.
That machine is a special machine, and it has its special characteristics (I had a CMB 4,1 once).

I have a cMP 5,1 (specs In Signature below), original hardware for WiFi and Bluetooth with OCLP 1.1.0 Sonoma runs perfectly - everything working perfectly. Installed with USB over freshly formatted 1Tb SSD after copying data only from previous Ventura installation using “SuperDuper”. Used ’host machine ‘setting. It’s been running since whenever OCLP 1.1.0 was released without a single hiccup.

 

[ymp01]

I have a MB Pro 9.2 with Sonoma 14.1 and OCPL 1.1.0. Everything works perfectly. I wanted to install 1.2.0(Nightly) to upgrade Sonoma to 14.2 and when I try to patch I get the following error:

Reason for Patch Failure (71):
No variant specified, failing back to release
Error Domain=KMErrorDomain Code=71 "invalid argument:
Unable to read contents of file at /System/Volumes/Update/mt1/System/Library/KernelCollections/BootKernelExtensions.kc”
UserInfo={NSLocalizedDescription=Invalid argument: Unable to read contents of file at /System/Volumes/Update/mnt1/System/Library/KernelCollections/BootKernelExtensions.kc}

I ran in safe mode and the same error. So, out of curiosity, I decided to reinstall the OCPL 1.1.0 patch and the same error happened again. What could this be about, how to fix it? So far I haven't had any problems with OCPL on this computer.

 

[davidlv]

I have a MB Pro 9.2 with Sonoma 14.1 and OCPL 1.1.0. Everything works perfectly. I wanted to install 1.2.0(Nightly) to upgrade Sonoma to 14.2 and when I try to patch I get the following error:

Reason for Patch Failure (71):
No variant specified, failing back to release
Error Domain=KMErrorDomain Code=71 "invalid argument:
Unable to read contents of file at /System/Volumes/Update/mt1/System/Library/KernelCollections/BootKernelExtensions.kc”
UserInfo={NSLocalizedDescription=Invalid argument: Unable to read contents of file at /System/Volumes/Update/mnt1/System/Library/KernelCollections/BootKernelExtensions.kc}

I ran in safe mode and the same error. So, out of curiosity, I decided to reinstall the OCPL 1.1.0 patch and the same error happened again. What could this be about, how to fix it? So far I haven't had any problems with OCPL on this computer.

Use the "Revert Patches" in the "Post Install Root Patches" menu and reboot.
Then run the Root Patches again.

 

[ymp01]

Use the "Revert Patches" in the "Post Install Root Patches" menu and reboot.
Then run the Root Patches again.

It does not work. I am currently left with Sonoma without the patch installed and cannot reinstall it.

 

[deeveedee]

I found a two pages macrumors thread from 2021 where some OCLP developers (I don't remember who, sorry) discuss about a possible memory issue in Haswell Macs causing similar issues that I was having and that those issues could be eliminated by setting FeatureUnlock to Partial.

Since I don't use SideCar/AirPlay/UniversalControl on my MBP6,2, I've added boot-arg -disable_sidecar_mac (equivalent to setting FeatureUnlock = Partial in OCLP) to see if it makes a difference in CPU fan activity with Sonoma. Power management is great on the MBP6,2 (Devs did a great job), but I'm curious to see if there's an improvement. Thanks for the suggestion.

EDIT: I'm currently running Sonoma 14.1 (Release) patched with OCLP 1.2.0n (built 11/5/2023 with Python3.11.5) on my MBP6,2. Now that I've identified my own acceptable insecure use cases (my preferences) for this old Mac, I'm having fun with Sonoma which runs great! Well done Devs.

 

[deeveedee]

It does not work. I am currently left with Sonoma without the patch installed and cannot reinstall it.

Assuming that @davidlv is on the right track, maybe you need to manually remove patches and try again? I'm guessing, but can't hurt (famous last words).

Manually remove patches:

Spoiler

 

[davidlv]

It does not work. I am currently left with Sonoma without the patch installed and cannot reinstall it.

Last ditch effort: try the OCLP nightly (search on the phrase in this thread for the link). The devs have made some great improvements in that version. So it might help.

 

[ymp01]

Last ditch effort: try the OCLP nightly (search on the phrase in this thread for the link). The devs have made some great improvements in that version. So it might

Unfortunately, nothing works. I'm looking for a clean installation. This is a very strange situation. Everything always worked very nicely.

 

[deeveedee]

Unfortunately, nothing works. I'm looking for a clean installation. This is a very strange situation. Everything always worked very nicely.

Some have reported (including me) that Sonoma install and OCLP patching issues are resolved by maintaining a network connection during install. Are you able to maintain a wired-Ethernet connection with your Mac while you apply the post-install patches? Note that you can't have Wi-Fi without the OCLP post-install patches in Sonoma.

 

[deeveedee]

Upgrading Sonoma 14.1 (Release) to 14.2 Beta (patched with OCLP 1.2.0n built 11/5/2023 with Python3.11.5). This is the first time I'm seeing this:

 

[davidlv]

Unfortunately, nothing works. I'm looking for a clean installation. This is a very strange situation. Everything always worked very nicely.

Did you try the latest nightly, dated 11-5-2023 21:20? That staement, "Nothing works" implies that you did try it. BUt really?

 

[rob.shaw]

Upgrading Sonoma 14.1 (Release) to 14.2 Beta (patched with OCLP 1.2.0n built 11/5/2023 with Python3.11.5). This is the first time I'm seeing this:

View attachment 2307536

Saw that sort of notice when upgrading to the 14.1 final - just said ok and allowed it to install the necessary. Worked perfectly after a couple of switch offs and reboots.

 

[deeveedee]

Upgrade from Sonoma 14.1 (Release) to 14.2 (Beta 23C5030f) proceeded without issues on my MBP6,2 (non-metal Nvidia Tesla) patched with OCLP 1.2.0n (built 11/5/2023 with Python3.11.5). I first patched 14.1 with OCLP 1.2.0n and then performed the macOS upgrade via OTA (which downloaded the full macOS installer). My Open Core EFI is configured with AMFI and Library Validation fully enabled and FeatureUnlock = Partial.

When I initiated the macOS upgrade, OCLP detected the upgrade and asked permission to "prepare the system for updates." Not being familiar with this new prompt, I clicked "Cancel" to the OCLP prompt and then manually applied OCLP 1.2.0n post-install patches after the macOS upgrade was complete. I did not revert root-patches at any time during this upgrade.

EDIT: I established and maintained a wired-Ethernet connection during the entire macOS upgrade and OCLP post-install patching process.

 

[amiromari]

I have a cMP 5,1 (specs In Signature below), original hardware for WiFi and Bluetooth with OCLP 1.1.0 Sonoma runs perfectly - everything working perfectly. Installed with USB over freshly formatted 1Tb SSD after copying data only from previous Ventura installation using “SuperDuper”. Used ’host machine ‘setting. It’s been running since whenever OCLP 1.1.0 was released without a single hiccup.

sorry I should've mentioned I created a bootable USB with Sonoma 14.0 as a plan B should the OTA update fail, luckily did not need to use it, also I backed up files to an external Drive before starting the process

 

[K two]

On the Macmini7,1 macOS 14.2b1 and OCLP v.1.2.0n v.11/2 1:22PM build; the persistant inability to get the Stocks app and Widget to work was finally solved after trying a NVRAM reset from OCLP start-up option, the traditional power-on and option+command+p+r for three bongs reset method which did not solve the problem. Neither did a plethora of safe-boots, root patcn manipulations via OCLP and manual methods. Finally realizing a full SMC reset had not been performed in awhile, the power plug was detached for 30 secs. the ON-button was depressed for 5 secs., the power-plug was re-attched and 10 secs. later, power-on followed by the traditional NVRAM method reset was applied on a wired KB which fixed the issue. (whew)! YMMV (Never seen SMC effect a specific Mac app, before?) Now, flawless and worth every penny! 🤑

 

[MacRumors3590]

I have a MB Pro 9.2 with Sonoma 14.1 and OCPL 1.1.0. Everything works perfectly. I wanted to install 1.2.0(Nightly) to upgrade Sonoma to 14.2 and when I try to patch I get the following error:

Reason for Patch Failure (71):
No variant specified, failing back to release
Error Domain=KMErrorDomain Code=71 "invalid argument:
Unable to read contents of file at /System/Volumes/Update/mt1/System/Library/KernelCollections/BootKernelExtensions.kc”
UserInfo={NSLocalizedDescription=Invalid argument: Unable to read contents of file at /System/Volumes/Update/mnt1/System/Library/KernelCollections/BootKernelExtensions.kc}

I ran in safe mode and the same error. So, out of curiosity, I decided to reinstall the OCPL 1.1.0 patch and the same error happened again. What could this be about, how to fix it? So far I haven't had any problems with OCPL on this computer.

Sorry but start over reinstalling 14.1 with oclp 1.1.0. Wipe the drive.

 

[ymp01]

Sorry but start over reinstalling 14.1 with oclp 1.1.0. Wipe the drive.

I updated to 14.1 from the USB installer. This completely cleared the remnants of the previous OCPL. Then I installed the OCPL 1.2.0 patch in safe mode and everything works. Wi-Fi worked in safe mode even before the patch was installed. I didn't have to connect it to ethernet.

 

[Larsvonhier]

Help needed for a strange metal problem on 3802 based GT630 / Kepler on Sonoma 14.0. patched with OCLP1.1.0.

All the usual rendering does work (Maps et al., system-wide acceleration, metalinfo reports ok, metal benchmarks run),
but we run into trouble now with MySQL Workbench (versions 8.0.x upwards):
The frontend starts, but when connecting to the data base server it reports via console "Couldn´t get metal kernel: (NUL)".

Also to be noted: The same app runs and connects perfectly fine on patched OpenGL Sonoma Macs and also on M1 Air and on patched Mac Pro with AMD R9 280X.

Also tried to start the app with --force opengl parameter via command line, but it seems to ignore it and still tries metal on the GT630.

Is this related to the 3802 implementation of the metal functionalities?
Any ideas what could be tried to resolve this...?

 

[mathewgx]

Can someone send me the link for the latest OCLP nightly ?