macOS 14 Sonoma on Unsupported Macs Thread

[MacinMan]

I just purchased a 2017 MacBook Pro 2 thunderbird 3 model from someone at my job who needed the money to get his personal vehicle out of impound, think it is pretty crappy the city towed his vehicle when we were providing assistance for the eclipse event in Chicago, but that's for another place. Got it for $200.00 in mint condition. Just wondering if there is any known issues updating it to Sonoma, with the intel iris plus graphics 640. It supports Ventura, so I wouldn't think there would be any problems doing Sonoma, especially since I got 14.4.1 running on my mid 2010 MacBook Pro and it works very nicely. Just figured it might be a good idea to have a newer more modern MacBook Pro and he needed help to get his vehicle out of impound...... good time to have extra cash on me.

I think I remember seeing a post a while back suggesting that if a Mac natively supports Ventura, Sonoma won't need as much patching depending on the mac as a lot of the drivers may still be in. Sonoma. Kind of like Monterey on a Mac that natively supports Big Sur, it needs OCLP to boot but it doesn't need to be root patched. Not sure if Ventura and Sonoma officially share the same type of thing, but I thought I saw something suggesting it was similar,.

 

[deeveedee]

Not sure if Ventura and Sonoma officially share the same type of thing, but I thought I saw something suggesting it was similar,.

The 'leap' from Ventura to Sonoma may be bigger than from Big Sur to Monterey, because Apple removed the Wi-Fi framework for our unsupported Macs. Those who had Wi-Fi in Ventura and now that Wi-Fi is no longer supported in Sonoma will need to apply OCLP post-install root patches if they still want their unsupported Broadcom Wi-Fi to work in Sonoma.

That said, I think @chevyboy60013 will find that his 'new' MBP has lots of useful life left in it, even if it remains on Ventura for a while.

 

[safh_dev]

Hello everyone, I'm prety new to the stuff but not new to hackintosh.
So far opencore is installed but the root patcher is failing due to error 71.
Due to this, I do not have the write kex and cannot use the display properly nor the network. Just a heads up.
I also tried an Upgrade instead of an reinstall, maybe this was an errror?
Hardware: MacbookPro13,2 8GB i5
OCLP: 1.4.3

The error contains this message(s):
No variant specified, falling back to release
Error Domain=KMErrorDomain Code=71 "Invalid argument:
Unable to read contents of file at /System/Volumes/Update/mnt1/System/Library/KernelCollections/BootKernelExtension.kc"
UserInfo={NSLOcalizedDescription=
Invalid argument:
Unable to read contents of file at /System/Volumes/Update/mnt1/System/Library/KernelCollections/BootKernelExtension.kc}

 

[paardenkapper]

Hello everyone,...

Usually an upgrade would not mess up your whole system if it was working properly just before that.
If you still have your install drive just create a new APFS container and install to that - then move your stuff there.

To all - I'm very disappointed with Sonoma performance on older Mac devices. Especially Dual Core macs without dedicated graphics. It just feels sluggish and terrible to the point that I'd rather go back to Monterey.

 

[safh_dev]

Usually an upgrade would not mess up your whole system if it was working properly just before that.
If you still have your install drive just create a new APFS container and install to that - then move your stuff there.

To all - I'm very disappointed with Sonoma performance on older Mac devices. Especially Dual Core macs without dedicated graphics. It just feels sluggish and terrible to the point that I'd rather go back to Monterey.

Hi, so I got everything in iCloud and got a Backup I just reinstalled the whole thing now. Its still going but I keep you updated.

 

[safh_dev]

Usually an upgrade would not mess up your whole system if it was working properly just before that.
If you still have your install drive just create a new APFS container and install to that - then move your stuff there.

To all - I'm very disappointed with Sonoma performance on older Mac devices. Especially Dual Core macs without dedicated graphics. It just feels sluggish and terrible to the point that I'd rather go back to Monterey.

Okay so Fun fact: I freshly installed it via USB Drive and it gives me the same error ...

 

[PropClear]

Usually an upgrade would not mess up your whole system if it was working properly just before that.
If you still have your install drive just create a new APFS container and install to that - then move your stuff there.

To all - I'm very disappointed with Sonoma performance on older Mac devices. Especially Dual Core macs without dedicated graphics. It just feels sluggish and terrible to the point that I'd rather go back to Monterey.

Seems pretty clear that a core2duo will not transform to a up2date cpu 🤣 with OCLP and Sonoma, the dev teams work is outstanding! 👌🏻

 

[MacinMan]

The 'leap' from Ventura to Sonoma may be bigger than from Big Sur to Monterey, because Apple removed the Wi-Fi framework for our unsupported Macs. Those who had Wi-Fi in Ventura and now that Wi-Fi is no longer supported in Sonoma will need to apply OCLP post-install root patches if they still want their unsupported Broadcom Wi-Fi to work in Sonoma.

That said, I think @chevyboy60013 will find that his 'new' MBP has lots of useful life left in it, even if it remains on Ventura for a while.

Thanks for the clarification. My only personal experience was my Late 2013, 13" MBP 11,1. It stops official support at Big Sur, but while Monterey requires OCLP on that machine, it didn't require root patching. As with my late 2015 iMac 17,1 , it stops at Monterey for official support, and requires root patching for both Ventura, and Sononoma. Since I don't currently own a Mac with native support for newer, i wasn't sure, and only thought i had seen something mentioned on one of the threads suggesting what I said above.

 

[webg3]

Hello everyone! Finally, armed with courage, I successfully upgraded my 13" MacBook Pro 7,1 (Mid 2010) to Sonoma.
I started out from macOS High Sierra and to install Sonoma I used a USB Key created via OCLP 1.5.0 Nightly .

I REPORT AN ERROR NOT TO MAKE
I created the USB Key with my iMac (14,2 27-inch, late 2013, with Sonoma 14.4.1 & OCLP 1.5.0n) but forgot to select that the Mac to be simulated was the MBP 7.1.
Therefore, at the end of the installation, I recreated the EFIBoot and redid the Post Install Patch from the MBP itself, indicating well that I wanted to create the EFIBoot for the MacBook Pro 7.1

FIRST problem I encountered after the installation was with the WiFi not connecting which, after several attempts, I solved this way:
- I turned off the Mac, turned it back on, and held down the three ALT P R keys, until I heard the Chime sound (Gong!) FOUR TIMES, in order to clear the NVRAM.
- after which, holding down only ALT, I selected the EFIBoot icon to reload OCLP.
- after logging in and rebooting, I disassociated the Network with the automatic connection that was in the list of my WiFi connections
- I connected an Ethernet cable to the Router
- I connected by re-choosing the Network from the list and entering the Password
CAUTION since it is apparently the issue resolving to have, initially, an Ethernet connection although I don't understand why.

PROBLEM
The fans are almost always running.
Can anyone tell me if this is normal?
Mainly it happens if I use Internet connections with updates, downloads, browser use while the fan slows down or seems to turn off while using applications, even heavy ones.

View attachment 2366120​

I have equipment like yours, but with C2D 2.4GHz, and I can guarantee you, the best system with a patcher, which works as it should, is macOS Catalina, Google Chrome will have to remove the updates part because the latest version compatible is 116 (non-metal), other than that, dosdude1's patcher makes the AppleTV work as it should, and Apple applications (non-metal) all work.

You can even run Big Sur, Monterey, Ventura and Sonoma on this hardware, it's excellent, but you'll have to live without the aforementioned applications, there are a lot of broken things that no longer work on this hardware. If it's just navigation and Office, it's a device for another 10 years, easily.

About the fans always running and overheating, it is due to the lack of support for the metal API, for example Youtube H.265/60 fps, to resolve this, install the extension Enhancer for Youtube (Google Chrome) and set the settings to use the old H.264 and 30fps.

2 cents:

Dosdude1 Catalina Patcher (non-metal):
macOS 10.13-10.14 (ver. 116.0.5845.187, universal)
https://dl.google.com/dl/chrome/mac/legacy10_13/GGRO/googlechrome.dmg

Open Google Chrome\Contents\Info.plist and remove :

https://tools.google.com/service/update2

com.google.Chrome.UpdaterPrivilegedHelper
identifier com.google.Chrome.UpdaterPrivilegedHelper

Save and Exit

Open Terminal, type commands:

sudo xattr -lr /Applications/Google\ Chrome.app
sudo xattr -cr /Applications/Google\ Chrome.app
sudo codesign -f -s - /Applications/Google\ Chrome.app


one more thing

Dosdude1 Patcher makes it work on APFS RAID-0.
It is another piece of equipment that, when used in RAID-0, performs at its maximum.

 

[Macdctr]

This is my Early 2015 i5 13-inch updated to Sonoma 14.5 (23F5049f) using OCLP 1.5.0n

 

[paardenkapper]

Okay so Fun fact: I freshly installed it via USB Drive and it gives me the same error ...

Does your MBP run just fine with Monterey? Maybe you should install that, create a new installer and try again?

Just a sidenote for the trolls who misquoted me - I never talked about a Core2Duo but an i5 mac mini 2014 or MBP 2015. The subjective performance drops quite a bit. Nevertheless I'm extremely thankful for the development of OCLP. In the end it's down to Apple.

As soon as the support for Intel macs is dropped that's the end of the line anyways.

 

[Macdctr]

As soon as the support for Intel macs is dropped that's the end of the line anyways.

Even then you should still have a few years of OS support regarding security patches before the eventual end of all intel support. Yes . . . the writing is already on the wall regarding this.

 

[jon8214]

Tried an NVRam & PRam reset? After that try to boot an OCLP bootstick, it always make sense to have ab OCLP bootstick configured and matching your mac hardware for safety reasons. Your hardware should be not a problem with sonoma - choose oclp 1.4.3 or better 1.5.0n if you familiar with nightly oclp builds, as always use dortania's docu.

In that scenario you described, are you booting from an USB stick? Do the volumes in question appear in disk utility? What volumes show up in boot picker?

Hi Both I managed to get the Mac mini sorted by creating a Mountain Lion installer and reinstalled that and updated it, however I now think the Mac air has a hardware issue with the ram as I'm getting kernel panics trying to install any OS or recovery

 

[amaze1499]

You may consider to run AHT / Diagnostics to know for sure.

Use Apple Diagnostics to test your Mac - Apple Support

Apple Diagnostics, formerly known as Apple Hardware Test, can check your Mac for hardware issues.

support.apple.com

Intel processor​

1. Turn on your Mac, then immediately press and hold the D key on your keyboard as your Mac starts up.
2. Release when you see a progress bar or you're asked to choose a language.

If using the D key doesn't work, press and hold Option (⌥)-D at startup instead. If neither method works, review the guidelines for using key combinations at startup.

 

[trancerr]

Hello. I have iMac 2012 21’ A1418
I have tried all unsupported operating systems. Monterey is working steadily. There are problems with Ventura and Sonoma - screen flashes and a complete display failure randomly occur. And I'm attaching a screenshot.
What could be the reason, RAM, ssd?

 

[amaze1499]

Hello. I have iMac 2012 21’ A1418
I have tried all unsupported operating systems. Monterey is working steadily. There are problems with Ventura and Sonoma - screen flashes and a complete display failure randomly occur. And I'm attaching a screenshot.
What could be the reason, RAM, ssd?

Same issue when booted from USB or in safe mode? Which OCLP did you use to patch?

 

[trancerr]

Same issue when booted from USB or in safe mode? Which OCLP did you use to patch?

By the way, yes, first I took into account the sonoma on an external USB ssd. Everything works fine with it. Now the mac has an ssd via a 7+17 adapter on m2. I worked with him for a long time on Big Sur and Monterey without failures.

OCLP is latest version

 

[yafflehk]

I just updated my 2011 mac mini to sonoma, primarily to use as a way of consolidating several disparate iphoto/photos libraries. However I'm running into a problem: The "Library" option is missing from the sidebar. I can see all the pictures in the library only by making a smart album that shows all pictures after a certain date. Searching the web shows that this is a problem, but not one that has happened often or with a definite solution. Has anyone encountered this problem and found a way to fix it?

edit: I also suspect that Photos is not searching for duplicates or faces.

 

[Mystere65]

Hello. I have iMac 2012 21’ A1418
I have tried all unsupported operating systems. Monterey is working steadily. There are problems with Ventura and Sonoma - screen flashes and a complete display failure randomly occur. And I'm attaching a screenshot.
What could be the reason, RAM, ssd?

Same thing for me, but since I installed OCLP 1.5.0 it hasn't happened anymore

 

[madmind]

OK strange was worth a try... (May also check the firmware of your device etc., i don't think that it's an oclp related issue)

I confirm that the firmware is up to date… it seems there may be an issue with the current OCLP root patches in this case, as the M6 IS RECOGNIZED until the root patch is applied… I want to be clear that I am extremely grateful to the OCLP developers for ALL of their work… just doing my part to alert them to the issue…

 

[PropClear]

I confirm that the firmware is up to date… it seems there may be an issue with the current OCLP root patches in this case, as the M6 IS RECOGNIZED until the root patch is applied… I want to be clear that I am extremely grateful to the OCLP developers for ALL of their work… just doing my part to alert them to the issue…

Then may try to file your issue on the OCLP discord channel (esp. when you also tried the 1.5.0n build?).

 

[trancerr]

Same thing for me, but since I installed OCLP 1.5.0 it hasn't happened anymore

Oh, wow
I thought the latest version was 1.4.3 is latest here

Releases · dortania/OpenCore-Legacy-Patcher

Experience macOS just like before. Contribute to dortania/OpenCore-Legacy-Patcher development by creating an account on GitHub.

github.com

 

[trancerr]

Same thing for me, but since I installed OCLP 1.5.0 it hasn't happened anymore

Have you reinstalled sonoma after the oclp update?

 

[Mystere65]

Have you reinstalled sonoma after the oclp update?

Not just OCLP and Patcher

 

[K two]

Oh, wow
I thought the latest version was 1.4.3 is latest here

Releases · dortania/OpenCore-Legacy-Patcher

Experience macOS just like before. Contribute to dortania/OpenCore-Legacy-Patcher development by creating an account on GitHub.

github.com

OCLP v1.5.0 Nightly is here: https://github.com/dortania/OpenCore-Legacy-Patcher/blob/main/SOURCE.md read everything including the CHANGELOG before you try the .DMG