Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
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.
 
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?
 
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.
 
Last edited:
  • Like
Reactions: olad
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.
 
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.
 
  • Like
Reactions: K two
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.
 
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.
 
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.
 
Last edited:
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
 

Attachments

  • Screenshot 2023-10-11 at 2.08.04 PM.png
    Screenshot 2023-10-11 at 2.08.04 PM.png
    53.7 KB · Views: 75
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}
<<<]
 

Attachments

  • Screenshot 2023-10-11 at 08.13.19.png
    Screenshot 2023-10-11 at 08.13.19.png
    36.2 KB · Views: 95
  • Screenshot 2023-10-11 at 08.37.41.png
    Screenshot 2023-10-11 at 08.37.41.png
    33.1 KB · Views: 117
Last edited:
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?
 
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…?
 
Last edited:
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.
 
  • Like
Reactions: Sven G
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.
 
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?
Yep, well done :)
That's it… Hold on ALT key at each restart and works !
Thanks
 

Attachments

  • sonoma-CMP3.1.jpg
    sonoma-CMP3.1.jpg
    110.8 KB · Views: 127
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}
<<<]
Patched OTA full installer update to 14.1b3 23B5067a using 1.0.1 worked fine.

However, in hindsight upgrading to Sonoma was somehow not worth it after all. This is not a complaint, just a quick reflection on what the "ROI" of this hobby actually is. Groundhog Day.

In this build Notes, Mail, Messages search won't work. Photos still crashing constantly when selecting Memories, it's reproducible. Keychain folder is filling up with 10s of GB temporary files. This is not a OCLP or beta issue, I saw the problems popping up for many users out there already in 14.0.

Doing this for fun, as kind of a hobby, its just fine. From a productivity point of view, there is not much of a difference to Ventura or even BigSur. Stock apps have still the same performance. Photos is slow even on an M2. And unless you need to stay uptodate with Xcode, why switching to a new hardware? Performance in Sonoma is still the same ish as it was in HighSierra, at least on this machine, a 9,2. Bottom line: Upgrading to Sonoma is actually not worth the hassle.

Surely, widgets are neat, all the other small improvements are very welcome, keeping the MacOS secure is also important, but it's not worth putting those in a major update. A movie running as desktop background. New emojis, well. You name it. There is no main feature apart from including latest technologies and security standards, that are truly necessary.

After all, being an Apple user since Performa 6200 / OS7.5.3 I feel the MacOS/hardware update cycles became way too small. Every 2 or 3 years would be totally fine. The problem Apple has is obvious. Newer, faster and more powerful hardware every year won't cut it anymore for the average user. A new OS neither. New is not better anymore and the broad customer base has caught up learning this lesson. It doesn't make sense spending money on a new machine/phone every or even two years. OCLP delivered the proof. Sonoma even runs on a two decades old MacBookPro... was it a G4? 23 years old. With questionable performance of course. Switching to a new architecture, faster this and that seems to be the only way to keep the update cycle and cashflow alive (higher prices need justification).
New true invention is a true dilemma for Apple indeed. They are running behind. I don't see the Apple Vision Pro solving that problem. If there is a "being on top" at all. Every other tech company faces the same situation. Thoughts?

Still I am grateful for the amazing work the developers put into this project. Thank you!
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.