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
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
Where did you possibly get an idea for this? This may come as a surprise to most of you: I created a post in Sven G's new thread.
Agreed. Unless one needs XCode, this is a perfectly good option as Monterey is still receiving Apple security updates.
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:
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.
have you tried using the reminders widget? does it show you texts or just blank?
This will be my last OCLP-security-related post in this thread. I have summarized my concerns and Ball of Neon's courteous and professional responses here.
@deeveedee there is a new security minded thread for OCLP concerns have you found it? the link is earlier in this thread.
I may have just discovered someone with humor more dry and subtle than my own.
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 ...)
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… 
Edit (see below): KDE’s Qt: https://www.qt.io.
Edit (see below): KDE’s Qt: https://www.qt.io.
Last edited:
QT as in Qiuicktime, or KDE's the Cute Toolkit ?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…
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.
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 ?
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.
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.
The most simple solution is a PRAM reset on boot to delete some Bluetooth related variables left from older macOS versions. Manually deleting them via terminal or app is another way.