macOS 14 Sonoma on Unsupported Macs Thread

[davidlv]

I tried it. The User (Dawn) has No Admin privileges. That is my issue.
It is a Standard account from which I launch Terminal.

This is a copy and paste from Terminal:

Dawn@Dawns-iMac-21 ~ % cd /var/db/
Dawn@Dawns-iMac-21 db % rm .AppleSetupDone
override rw-r--r-- root/wheel for .AppleSetupDone? y
rm: .AppleSetupDone: Permission denied
Dawn@Dawns-iMac-21 db %

You see I entered the: cd /var/db/
Then I entered: rm .AppleSetupDone
and Terminal Returned with:
override rw-r--r-- root/wheel for .AppleSetupDone?
To which I answered with a y
Then Terminal returned with:
rm: .AppleSetupDone: Permission denied

Now what?

Try
cd /var/db
sudo rm .AppleSetupDone

Another;

1. Boot into Single User Mode: Start/restart your Mac. As soon as you hear the startup tone, press and hold ⌘ + S until you see a black screen with white lettering. (If you end up back on the login screen after a flash of the black screen with white lettering, enter your password and it will return to the black screen.)
2. Check and repair the drive by typing /sbin/fsck -fy then ↩ enter - as directed by the on-screen text.
3. Mount the drive as read-write by typing /sbin/mount -uw / then ↩ enter.
4. Remove the Apple Setup Done file by typing rm /var/db/.AppleSetupDone then ↩ enter.
5. Reboot by typing reboot then ↩ enter.
6. Complete the setup process, creating a new admin account.

did you try deleting that file using the other Mac and target disk mode?

or this:

 

[BuffyzDead]

Try
cd /var/db
sudo rm .AppleSetupDone

Another;

1. Boot into Single User Mode: Start/restart your Mac. As soon as you hear the startup tone, press and hold ⌘ + S until you see a black screen with white lettering. (If you end up back on the login screen after a flash of the black screen with white lettering, enter your password and it will return to the black screen.)
2. Check and repair the drive by typing /sbin/fsck -fy then ↩ enter - as directed by the on-screen text.
3. Mount the drive as read-write by typing /sbin/mount -uw / then ↩ enter.
4. Remove the Apple Setup Done file by typing rm /var/db/.AppleSetupDone then ↩ enter.
5. Reboot by typing reboot then ↩ enter.
6. Complete the setup process, creating a new admin account.

did you try deleting that file using the other Mac and target disk mode?

or this:

I really appreciate you responding so quickly
But

I tried it with the Sudo command and it asks for an Admin Password.
Thus back to my quandary.
I am doing all of this from a Standard account, ...Not an Admin account.

And Try after try after try,
to boot into Recovery Mode OR Single User Mode,
Fails 100% of the time. I've literally tried about 30 times now.

 

[grumpy_Garrett]

Sonoma 14.1 beta 3 reverting patches comes in under 900mb same bugs as before no different than the others bugs everyone is experiencing on 14.0 all went ok on mid 2014 MacBook Pro credit to the Devs , Thankyou with OCLP 1.1n not experiencing the widgets crash or memories photo crash in the photos app.

how did you download oclp 1.1.0?

 

[davidlv]

how did you download oclp 1.1.0?

See post 2,199 and ... use the search function next time

 

[davidlv]

I really appreciate you responding so quickly
But

I tried it with the Sudo command and it asks for an Admin Password.
Thus back to my quandary.
I am doing all of this from a Standard account, ...Not an Admin account.

And Try after try after try,
to boot into Recovery Mode OR Single User Mode,
Fails 100% of the time. I've literally tried about 30 times now.

Call Apple or take the computer in?
I can't understand why Single User Mode doesn't work.
Are you sure you are holding the Command + s keys at boot?

Have you tried;
Option+Command+r: Start up from macOS Recovery over the internet. Or use this key combination to reinstall macOS and upgrade to the latest version of macOS that's compatible with your Mac. Option+Shift+Command+r:

If nothing else, why can't you startup from a USB installer disk and wipe the internal drive, then install the OS again.
Backup your data first of course. Carbon Copy Cloner has a 30 day trial option, so you can make a good backup on and external disk, SSD or HDD.

 

[Propwash0]

Hi there!
Since I installed the latest OCLP nighly for Sonoma development (from today:29/09/2023), the Bluetooth doesn't work anymore with my iMac 13.2. The Magic Trackpad is not recognized anymore, and I have only a mouse option in the Control Settings. The Bluetooth can be activated but is not working. Same behavior with my MBP 13.2. With the previous OCLP, everything was working fine. Does anyone encounter the same Bluetooth issue?

Hey there. I’m somewhat new to OpenCore. I currently have an Early 2014 MacBook Air and have Sonoma running on it using 1.0.1. Everything seems to be running pretty great except for an issue with the Bluetooth very similar to yours. My trackpad works fine but when I turn on BT it still doesn’t work. I’m still trying to figure out what a nightly build is and how to download and install it so I can run the patcher to see if it solves the issue. With Ventura on my 2009 iMac the Bluetooth worked fine. Your help would be much appreciated. You’re the only other person who’s encountered such a similar issue.

 

[davidlv]

Hey there. I’m somewhat new to OpenCore. I currently have an Early 2014 MacBook Air and have Sonoma running on it using 1.0.1. Everything seems to be running pretty great except for an issue with the Bluetooth very similar to yours. My trackpad works fine but when I turn on BT it still doesn’t work. I’m still trying to figure out what a nightly build is and how to download and install it so I can run the patcher to see if it solves the issue. With Ventura on my 2009 iMac the Bluetooth worked fine. Your help would be much appreciated. You’re the only other person who’s encountered such a similar issue.

See post # 2199 for a link to the page describing the Nightly versions (not every night BTW). you can download the latest build there too or compile it yourself. Basically the nightly version is the beta of OCLP 1.1.
The latest version works great on my hardware, iMac 15,1 late 2014 27". It might help with your Bluetooth issues, not sure about that of course, as every hardware configuration is different.

 

[Propwash0]

See post # 2199 for a link to the page describing the Nightly versions (not every night BTW). you can download the latest build there too or compile it yourself. Basically the nightly version is the beta of OCLP 1.1.
The latest version works great on my hardware, iMac 15,1 late 2014 27". It might help with your Bluetooth issues, not sure about that of course, as every hardware configuration is different.

Thank you so much for your response. I’ll go ahead and try it now and see what happens. I’ll reply my results and hopefully this can help someone else with issues with this model.

 

[WurzelGnOOm]

After updating my iMac 14.2 to macOS 14 with OCLP 1.1n same apps are not working.

Here a sample

IDE 2023.2 crashes on macOS (at MTLLayer

After adding “-Dsun.java2d.metal=false” in the /Library/Application Support/JetBrains/PhpStorm2023.2/phpstorm.vmoptions

PhpStorm 2023.2.2 could be started.

 

[nekton1]

Just OTA-updated iMac 12,2 running 14.0 final with OCLP 1.0.1 to 14.1b3 with OCLP 1.1n and root patches. No problems other than BT still MIA. Wi-Fi working OK.
Straightforward OTA update without manual intervention. Zoom shows a pink/green screen that becomes normal by starting FaceTime. Stays normal after quitting FaceTime until Zoom restarted.

 

[wylhkg]

My 2014 and 2017 MacBook Pro FaceTime camera still disconnected, we need to wait for new OCLP or it has other method to connect it? Both MacBook Pro is running on OCLP 1.0.1 14.1 beta 2

 

[amaze1499]

FYI: Tried update to 14.1b3 through OTA incremental update without Wifi using the iPhone USB internet connection (obviously a sufficient data plan is necessary).

While this this works to stay connected with an unpatched system (OCLP1.0.1), preparing the update failed eventually.

Errorlog:
[FSM(SUMacControllerStateMachine)] >S> PreparingUpdate >E> UpdateAttemptFailed >A> PrepareFailed info:[>>>

BridgeOS(shouldPerformBridgeOSUpdate:NO|bridgeOSVersionToInstallnull)|bridgeOSDownloadSizeBytesnull)|bridgeOSExtractedSizeBytesnull)|bridgeOSDownloadDirectorynull))

error: Error Domain=MobileSoftwareUpdateErrorDomain Code=3 "'./usr/sbin/bluetoothd' does not verify" UserInfo={target_update=23B5067a, NSUnderlyingError=0x7fcbb1a87bd0 {Error Domain=MobileSoftwareUpdateBOMErrorDomain Code=1 "contents of '/usr/sbin/bluetoothd' don't match bom (51750e1b vs 1a374e0)" UserInfo={NSLocalizedDescription=contents of '/usr/sbin/bluetoothd' don't match bom (51750e1b vs 1a374e0)}}, MSUFullReplacementRecommened=true, NSLocalizedDescription='./usr/sbin/bluetoothd' does not verify}
<<<]

 

[iMac-Oldschool]

See post 2,199 and ... use the search function next time

Unfortunately, a search for "1.1.0" does not lead to post 2,199. The post refers to "1.1 nightly".

 

[headlessmike]

Unfortunately, a search for "1.1.0" does not lead to post 2,199. The post refers to "1.1 nightly".

The nightly is the only version of 1.1.0 currently available. It's effectively a beta version and should be treated as such.

 

[davidlv]

Unfortunately, a search for "1.1.0" does not lead to post 2,199. The post refers to "1.1 nightly".

I didn't suggest doing a search for 1.1.0, I suggested doing a search for the nightly version of OCLP rather than asking for help, The nightly version of OCLP was the subject of the post I was answering. Why are you complaining about that?

 

[Sven G]

Anyone has the glitch that the Agree window never appears when doing a software update in System Settings…? I have this in my MBP11,3, but don’t know if it’s some wrong hidden setting, if it’s related to iCloud or the Developer account, or finally if it’s (also?) OCLP-related…?

 

[MacinMan]

Anyone has the glitch that the Agree window never appears when doing a software update in System Settings…? I have this in my MBP11,3, but don’t know if it’s some wrong hidden setting, if it’s related to iCloud or the Developer account, or finally if it’s (also?) OCLP-related…?

I had the issue where the agree to terms didn't show up in Mojave when setting it up as a VM in VMware fusion, but haven't had issues with a host os, even if patched.

 

[mikelets456]

Beta3 OTA much the same as b2 OTA on the Mini7,1 via OCLPv1.0.1, rock solid!! 🥳
View attachment 2292666

Are you using 1.0.1? Is it more stable than 14.0?

 

[skenchand503]

My 2017 MBP upgraded to 14.1 beta 3 w/ OCLP 1.1n, and find a problem.

If I launch apps that heavy-used graphics resources such as FCPX or Parallels Desktop, it freeze. Maybe the problem is the graphic switching to dedicated GPU.

Do anyone have this problem?

And, sorry for my poor English.

 

[0134168]

Anyone can be so kind to postOpencore Legacy Pstcher v. 1.0.0? NOt 1.0.1.

 

[K two]

Are you using 1.0.1? Is it more stable than 14.0?

Yes, using the release version of OCLPv1.0.1. And b3 OTA runs much the same as 14.0, flawless on this Mini, ymmv. Have not tried v1.1n.

 

[Tockman]

Anyone can be so kind to postOpencore Legacy Pstcher v. 1.0.0? NOt 1.0.1.

https://github.com/dortania/OpenCore-Legacy-Patcher/releases/download/1.0.0/OpenCore-Patcher-GUI.app.zip

 

[philk34]

You should see and select the EFI icon when you start up holding the OPTION key down (Alt key is the equivalent on a Windows keyboard), the select the macOS USB installer.
In some cases, you have to hold down the Option key again when the installer reboots and select the EFT icon and then the macOS installer icon again (the order sometimes gets out of sync).
Also, the OCLP HP has an update out to version 1.0.1, so why not use that?

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

Yep, well done
That's it… Hold on ALT key at each restart and works !
Thanks

 

[K two]

Anyone can be so kind to postOpencore Legacy Pstcher v. 1.0.0? NOt 1.0.1.

https://github.com/dortania/OpenCore-Legacy-Patcher/releases - scroll down to the v1.0 release. 🧐

 

[coolio2004]

Unfortunately, a search for "1.1.0" does not lead to post 2,199. The post refers to "1.1 nightly".

There is no 1.1 -only 1.1n