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.
reneroeten said:
well I have fix the bluetooth issue with my iMac 2011 this is what I did:
- I took OLCP version 0.6.9n and did a build and install to disk
- installed the root patches and did a reboot
- And yes bluetooth is working again
- downloaded the latest OLCP 1.0.1 and installed the root patches

bluetooth is still working I'm very happy this worked..
I hope that people with the same issues can use this too to get it working again
Click to expand...
I tried your solution but didn’t worked for me, the Bluetooth toogle don’t stay on, please is there any other solution I can try?
 
liltysha said:
I tried your solution but didn’t worked for me, the Bluetooth toogle don’t stay on, please is there any other solution I can try?
Click to expand...
sorry to hear that I would not know any other solution, it's got something to do how Sonoma sees the bluetooth adapter. it's different then in Ventura for sure
 
After the installation of Sonoma via OCLP 1.0.1 I have recently the problem that I can no longer call the boot picker of the Mac (not the one of OCLP!) with the pressed Alt/Option key when booting the computer.
Normally I can select there with which EFI of a drive I want to boot.

If I now press the Alt/Option key when starting the Mac, the OCLP Boot Picker appears immediately. If I don't press the key, the Mac boots immediately without the OCLP boot picker. In the OCLP Settings "Show OpenCore Boot Picker Picker" was not activated during the installation of OpenCore.

If anyone has had this and knows a workaround, I'd appreciate a hint. Thanks!

Edit: I was able to solve the problem in the meantime. I have a display here with an integrated active USB3 hub. This hub, which is connected to my wired keyboard, was previously connected to a native USB2 port on the Mac. I recently had the corresponding cable from the hub connected to the PCIe USB3 card built into the Mac. So the keyboard's Alt/Option keystroke was not transmitted at startup. With the original cable connections it now works again.
 
Last edited:
  • Like
Reactions: K two
deeveedee said:
Agreed. Unless one needs XCode, this is a perfectly good option as Monterey is still receiving Apple security updates.
Click to expand...
Well, I only use Xcode to get the tools that natively come with Linux, or a BSD system. As far as needing newer, I really don't except for the Apple Pro Apps, but it seems like Apple is no longer the platform to go to anymore for production.

When I did production we used final cut studio 6, and 7.
 
BuffyzDead said:
I have a strange issue. After using an OCLP v 1.0.1 USB key, to update a Late 2009 iMac, from Monterey to Sonoma, I have lost the Admin account. Not actually lost the account, but it has reverted the admin account to a standard account, thus Not Allowing me to install the post install patches, or to install or admin this iMac in anyway, whatsoever.

How do I add a new admin account or change the standard account to an admin account?
Thank you
Click to expand...

You need to delete a hidden file ‘.AppleSetupDone’ in /Volumes/Sonoma/var/db/

—————————————————————————————————————————-

Boot the Mac into Recovery Mode

At the macOS Utilities screen, open Disk Utility

Select “Sonoma – Data” from the side bar and choose to “Mount” the Data drive

Exit out of Disk Utility

Pull down the ‘Utilities’ menu and choose “Terminal”

Enter the following command into the Terminal: cd /Volumes/Sonoma/var/db/

Next enter the following command: rm .AppleSetupDone

Restart the Mac and it will go through the Setup Assistant procedure as if the Mac was new to create a new admin user account on the Mac, this will be an administrator account.

You can use this admin user account to modify the original user account to become an admin account again.
 
I am on an iMac 12,1 and macOS 14.0
After updating OLCP to 1.0.1 and root patching, the finder window does lost focus
permanently (Left side greyed out) and I have no access to any disks, folders etc.
Anyone else ?

(I did revert to 1.0.0 in the meantime ...)
 
Today, while updating Qt, my Sonoma machine suddenly “froze” in a strange way: the mouse worked, but both the Menu Bar and the Dock were completely unresponsive (not possible to click on items and no tooltips showing when hovering over them); so I had to force reboot. Well, yet another strange thing, among others… :)o_O

Edit (see below): KDE’s Qt: https://www.qt.io.
 
Last edited:
  • Like
Reactions: Dilli
Sven G said:
Today, while updating Qt, my Sonoma machine suddenly “froze” in a strange way: the mouse worked, but both the Menu Bar and the Dock were completely unresponsive (not possible to click on items and no tooltips showing when hovering over them); so I had to force reboot. Well, yet another strange thing, among others… :)o_O
Click to expand...
QT as in Qiuicktime, or KDE's the Cute Toolkit ?
 
rehkram said:
Update on the rMBP10,1 fan activity. Installed 14.0 + 1.0.1 yesterday and, as we discussed, the fans were going immediately after first login, as expected. Went to bed around 9PM, no fans at that point.

I was unable to sleep and checked the rMBP at around 4AM. Fans were going noticeably fast. Checked Activity Monitor, no explanation there; CPU & Disk both nominal.

Left it running and went back to bed. Got up around 9AM, fan activity had stopped and is still silent after an hour or so of use.

My current SWAG / theory is Apple have built-in "smarts" into some aspects of the post install workflow to only run when 99%+ of users would be asleep and the m/c otherwise idle. That would be easy enough for Apple to do and a perfectly logical move. But it's just a guess on my part.
Click to expand...
I wanted to bring back the fan issue. I think the issue may be more OLCP 1.0.x rather than Sonoma itself. I upgrade OLCP on my Mac 3,1 without going to Sonoma. Now the fan cycles between medium to loud which it never did before with previous versions.
 
  • Like
Reactions: rehkram
I just wanted to clarify with everyone , so installing Sonoma on the 2017 MacBook Pro permanently destroys the T1 chip in the MacBook making it impossible to restore functionality if downgrading back to Ventura ?
 
liltysha said:
I tried your solution but didn’t worked for me, the Bluetooth toogle don’t stay on, please is there any other solution I can try?
Click to expand...
I had similar bluetooth problems when I upgraded to Sonoma from Ventura on both a 2011 and 2010 iMac.
This is what I did to get bluetooth back.
Download Ben Baker's Hackintool.app. Use the app to edit NVRam directly. Look for the entries:
bluetoothExternalDongleFailed
bluetoothActiveControllerInfo
bluetoothInternalControllerinfo
Delete all the entries, and wait for the NVRam to refresh itself. At least one of the entries (bluetoothExternalDongleFailed) should come back with value of <00>. If not, repeat deleting the entries.
For me bluetooth worked again when I performed the above steps, bluetooth settings will show all previously paired devices, and auto connect to them just as before the update.
 
  • Like
Reactions: philippemarques, Heindijs, BuffyzDead and 4 others
jonnyv34 said:
I have a huge problem. Open the app updated to 1.0.1.
The app updated, then built open core and removed the previous installation, but when copying to disk it just freezes there. I though it might be taking longer because it is a slow machine ( 2012 MacBook Air) but surely after more than 30 minutes still have not copied to disk.
To make matter worse, my Finder crashed and doesn't open at all, meaning when I reboot the machine I will lose my Open core EFI.
Trying to install open core on a external USB drive to at least be able to boot from there, same problem it just doesn't write to disk.

Anyone can think of any solution to avoid having to restart? Forgot to mention , I am on Sonoma.
Click to expand...
It looks (suspiciously) a lot like what happened to me (here, here, and here). Which version of Sonoma are you running? I had the issue up until RC1 and it solved itself on upgrading to RC2, but it was with the 0.6.9 version of OCLP (even though I cannot be sure it was OCLP's fault).

The issue is that for some reason the Finder crashed whenever I mounted either a FAT32 or ExFAT volume, making it impossible to do anything in those types of volumes. Of course, the EFI partition falls into that category and you get the issue mentioned. The Finder lasts just enough to delete the EFI folder, but locks up and you lose your ability to boot Sonoma.

To restore my system, what I did was start in internet recovery, install Catalina to an external drive and use that fresh install to download OCLP and build/install onto the internal drive.

I thought I'd have to keep doing that ad infinitum, but somehow RC2 fixed the issue and now I can mount and work normally with FAT32/ExFAT volumes (and update OCLP too).

Hope this helps. Ping me if I can be of more help.
 
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