Sidebar Sidebar
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

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
So, the OCLP is reporting that it can't continue with the patching, until your Mac has completed a system update.
OCLP on my Mac reports a new OCLP update 2.1.2, so, it's a quick update that may be related to your issue.
 
  • Like
Reactions: Giovamille959 and rm5
Bigwaff said:
What version of macOS did you install w/ OCLP?
Click to expand...
14.6.1, which it is currently running.
DeltaMac said:
So, the OCLP is reporting that it can't continue with the patching, until your Mac has completed a system update.
OCLP on my Mac reports a new OCLP update 2.1.2, so, it's a quick update that may be related to your issue.
Click to expand...
I'll try that tomorrow. Only way I'll be able to do that is to use my iMac to download the OCLP app since the MBA cannot connect to WiFi. I just don't understand why it's saying it expects 14.6.1 (and that it's not running that) when 14.6.1 is literally the version on here. So strange. Also what's strange is that this happened completely out of the blue.
 
This happened to me because my Mac was automatically downloading system updates.
rm5 said:
Hi!! I have a 2013 11” MacBook Air that I use as a spare machine. After updating to OCLP version 2.1.1, everything completely broke. No GPU acceleration, no WiFi, nothing. What’s even more concerning is that the root patches refuse to apply at all. Since I have no internet on the computer, I literally don’t know how to solve this. I’m completely lost. Any help is appreciated! I’ve attached a photo of the error I get when applying the root patches.

EDIT: The machine is running Sonoma 14.6.1.

View attachment 2447592
Click to expand...
I had that message appear on a Mac mini last month and it turned out that the cause was that I had Settings / General / Software Update, tap the info circle to the right of Automatic Updates, Download New Updates turned on. (It may be that I had "Install MacOS Updates" on as well.) Apparently MacOS "helpfully" starts updating the system in a way that blocks OCLP from patching again.

I found a YouTube video that explained this (sorry, I can't find the link again) and it suggested removing a couple of files in a folder in the /library folder. Unfortunately turning off those two settings doesn't help at this point - it's too late by then and the update has already started installing. For me it was trying to install Sequoia and I didn't want to go there yet, and unfortunately removing the files didn't work for me and I had to reinstall MacOS from scratch. But perhaps allowing system update to install whatever update is installing and then letting your existing version of OCLP re-patch after boot might work.

The first thing I did after the reinstall is turn those two settings off.

If I find that YT link I'll post it.
 
  • Like
Reactions: Giovamille959 and rm5
doogm said:
This happened to me because my Mac was automatically downloading system updates.

I had that message appear on a Mac mini last month and it turned out that the cause was that I had Settings / General / Software Update, tap the info circle to the right of Automatic Updates, Download New Updates turned on. (It may be that I had "Install MacOS Updates" on as well.) Apparently MacOS "helpfully" starts updating the system in a way that blocks OCLP from patching again.

I found a YouTube video that explained this (sorry, I can't find the link again) and it suggested removing a couple of files in a folder in the /library folder. Unfortunately turning off those two settings doesn't help at this point - it's too late by then and the update has already started installing. For me it was trying to install Sequoia and I didn't want to go there yet, and unfortunately removing the files didn't work for me and I had to reinstall MacOS from scratch. But perhaps allowing system update to install whatever update is installing and then letting your existing version of OCLP re-patch after boot might work.

The first thing I did after the reinstall is turn those two settings off.

If I find that YT link I'll post it.
Click to expand...
This is my thought as well. Sounds like it downloaded and staged 14.7.1 in a snapshot. I'm not entirely familiar with OCLP, so not sure if you can just let this particular update finish and then redo the patching again, or if you need to revert back.

I'm guessing this is probably the video you're thinking of:
 
  • Like
Reactions: Giovamille959, m4v3r1ck, doogm and 1 other person
That’s gotta be what happened then!! I don’t have any tools up here at my university to do a complete reinstall, but I’ll bring this MacBook back home with me at semester’s end where I have thumb drives, etc. I reckon I’ll need to do a complete wipe, especially since the machine has no internet.
 
rm5 said:
Hi!! I have a 2013 11” MacBook Air that I use as a spare machine. After updating to OCLP version 2.1.1, everything completely broke. No GPU acceleration, no WiFi, nothing. What’s even more concerning is that the root patches refuse to apply at all. Since I have no internet on the computer, I literally don’t know how to solve this. I’m completely lost. Any help is appreciated! I’ve attached a photo of the error I get when applying the root patches.

EDIT: The machine is running Sonoma 14.6.1.
Click to expand...
Upgrading OCLP or the major OS version is always risky business. The suggestion I have is do not upgrade to the major OS version until x.4, and then install a new OCLP version that works with the major OS version. Keep doing OS security updates with the same OCLP until the next OS version is ready.
 
  • Like
Reactions: rm5
Well all, I just was able to finally update this mid 2012 MBP to OCLP2.1.2/Sonoma from Catalina and it seems the ability to play Apple purchased movies on an External Monitor has been resolved?... It's currently working! I can't believe this!. I've tried this on every version on this 2012 since 2.0 I think.. I tried it on my 2015 since 1.0.5-2.0.1 and it never worked and I've had to go back to Monterey. I'm really leery of trying it on my 2015 again. I hate having to put it all back together again when that doesn't work. Obviously there are hardware differences there. I also just tested Comcast Xfinity Streaming and that still doesn't work..pita.. Anyone else get that to work somehow?

Update: Downloaded Firefox... that works fine. Must be a mix of Safari/OCLP-Sonoma.
 
Last edited:
deeveedee said:
@xboxbml Just to confirm, you tested another browser as mentioned here (other than Safari) and it's working for you now?
Click to expand...
Yup.. bad thing is I've done unlikes.. this time I did a full wipe and reload as well, whereas all previous attempts were an upgrade from last supported version..So I really don't know what "fixed" it.. I'm wondering if I should attempt a full wipe and reload on the 2015... it's just so time consuming and we're in middle of remodeling bedroom...
 
FYI* I fired up this mid 2012 MBP with OCLP/Sonoma this morning and had a movie playing on really low volume in the office... I noticed the fans were a bit loud overpowering the audio.. I brought up iState menus and was putting things in my menu bar that weren't there and I noticed that bluetoothd or similar named process was up over 120% per iStat and CPU was over 200F... I shutoff bluetooth and the process disappeared and the fans went right down to almost nothing. I turned BT back on and the issue hasn't come back. Really interesting.. I guess that's what you get when you mess with stuff. Oh well, hopefully that doesn't come back. Other than that, this OCLP/Sonoma on this is working well. I did take a TimeMachine backup of this on its own external drive I had. I may do a wipe/reload on this up to Sequoia and see if that works. Almost done with the bedroom remodel so I should have time to play.
 
xboxbml said:
FYI* I fired up this mid 2012 MBP with OCLP/Sonoma this morning and had a movie playing on really low volume in the office... I noticed the fans were a bit loud overpowering the audio.. I brought up iState menus and was putting things in my menu bar that weren't there and I noticed that bluetoothd or similar named process was up over 120% per iStat and CPU was over 200F... I shutoff bluetooth and the process disappeared and the fans went right down to almost nothing. I turned BT back on and the issue hasn't come back. Really interesting.. I guess that's what you get when you mess with stuff. Oh well, hopefully that doesn't come back. Other than that, this OCLP/Sonoma on this is working well. I did take a TimeMachine backup of this on its own external drive I had. I may do a wipe/reload on this up to Sequoia and see if that works. Almost done with the bedroom remodel so I should have time to play.
Click to expand...
Well, looks like BT doesn't want to turn back on now.. has a slash thru the icon on menu bar. I switch it on and it shows blue on the switch then switches itself back off.. I'm assuming the driver is messed up? Thoughts?..
 
xboxbml said:
Well, looks like BT doesn't want to turn back on now.. has a slash thru the icon on menu bar. I switch it on and it shows blue on the switch then switches itself back off.. I'm assuming the driver is messed up? Thoughts?..
Click to expand...
If it were me I'd be doing the following. It will stop- and restart bluetooth. In terminal:

sudo kill -9 $(pgrep bluetoothd)
 
Smooth upgrade from Sonoma 14.7 -> 14.7.1 on my HackBookPro6,2. Still patching Sonoma with OCLP 1.4.3.
Screenshot 2024-11-14 at 5.30.57 PM.png
 
  • Like
Reactions: m4v3r1ck
xboxbml said:
Wouldn't a reboot do the same thing?.. I've rebooted several times..
Click to expand...
Not necessarily. The boot loader starting bluetooth during the boot sequence is different than restarting it while already booted, obviously. Plus, if bluetoothd throws an error on restart you might get diagnostic messages in real time in terminal.

Another thing worth trying, booting in safe mode. If it (bluetooth) seems to work OK while logged-in in safe mode it would tend to indicate that an auto-start app could be the culprit.
 
Last edited:
  • Like
Reactions: 0134168
rehkram said:
Not necessarily. The boot loader starting bluetooth during the boot sequence is different than restarting it while already booted, obviously. Plus, if bluetoothd throws an error on restart you might get diagnostic messages in real time in terminal.

Another thing worth trying, booting in safe mode. If it (bluetooth) seems to work OK while logged-in in safe mode it would tend to indicate that an auto-start app could be the culprit.
Click to expand...
Well, killing the processes didn't help...
rehkram said:
Not necessarily. The boot loader starting bluetooth during the boot sequence is different than restarting it while already booted, obviously. Plus, if bluetoothd throws an error on restart you might get diagnostic messages in real time in terminal.

Another thing worth trying, booting in safe mode. If it (bluetooth) seems to work OK while logged-in in safe mode it would tend to indicate that an auto-start app could be the culprit
Click to expand...
Still has same issue in safe mode.. I think perhaps the card got fried... or something really amiss.. This is really just the free machine I got out of the recycle bin and upgraded.. it's my knock around take in the garage for watching movies and football games etc.. not my daily. I guess I'll just live with it.. I might load Catalina back on just to see if it comes back, but I'm guessing it's fried. oh well.. Thanks for the info.
 
rehkram said:
Not necessarily. The boot loader starting bluetooth during the boot sequence is different than restarting it while already booted, obviously. Plus, if bluetoothd throws an error on restart you might get diagnostic messages in real time in terminal.

Another thing worth trying, booting in safe mode. If it (bluetooth) seems to work OK while logged-in in safe mode it would tend to indicate that an auto-start app could be the culprit.
Click to expand...
Yeah BT is fried...I just reloaded last supported OS Catalina on this and no BT showing anywhere... oh well... it also has an intermittent usb port...everything else seems to work.. spent 100$ upgrading ram to 16gb and 1tb SSD install... oh well.. good outside/garage machine..lol
 
xboxbml said:
Yeah BT is fried...I just reloaded last supported OS Catalina on this and no BT showing anywhere... oh well... it also has an intermittent usb port...everything else seems to work.. spent 100$ upgrading ram to 16gb and 1tb SSD install... oh well.. good outside/garage machine..lol
Click to expand...
The BT card is the original, or integrated with the wifi?
 
******* said:
The BT card is the original, or integrated with the wifi?
Click to expand...
It's a mid 2012 MBP.. I think it had Yosemite or Mavericks on it when I pulled it out of the bin.. So I'm guessing whatever stock was/is on this. I'm not sure how to tell.. I pulled the bottom off a few min ago to check to make sure I hadn't knocked any cable loose when I upgraded the ram and SSD when I got it. Didn't see anything obvious. Pushed down on all the ribbon cables I found. All seemed fine.
 
xboxbml said:
It's a mid 2012 MBP.. I think it had Yosemite or Mavericks on it when I pulled it out of the bin.. So I'm guessing whatever stock was/is on this. I'm not sure how to tell.. I pulled the bottom off a few min ago to check to make sure I hadn't knocked any cable loose when I upgraded the ram and SSD when I got it. Didn't see anything obvious. Pushed down on all the ribbon cables I found. All seemed fine.
Click to expand...
15" or 13"? I suppose it´s the 15" on your sign...
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back