macOS 14 Sonoma on Unsupported Macs Thread

[MacinMan]

Hey all, I've run into an issue with the september 26th nightly of 0.6.9. On my late 2013, 13" rMBP Macbook Pro 11.1
I updated open core and now it won't boot, it just hangs at the progress bar, the one thing I noticed is, in the boot picker I just see the standard hard drive icon vs the OS icon. If I revert to the 24th of sept build it works again. Since this isn't a mission critical mac i'm using to test, I expect problems so there is nothing to be lost in using it as a test machine. With this said, is there a way to fix this?

Thanks.

EDIT: I wanted to add that the September 26th nightly works fine with the install of Ventura I have on an external hard drive connected to my iMac 17,1. It's just the Sonoma install on the MBP that won't boot with this version.

 

[Ausdauersportler]

I'm sorry, I didn't want to upset you or anybody else. Your work is amazing, you know that, and almost everybody is thankful for everything you and the whole team does. We can only imagine how much work it is, and you're surely not even profiting of it financially in any way. I just didn't want this very useful thread having the same fate as so many others (not on this forum) had in the past, that's all.

Do not worry, just wanted to explain the situation from the other side. Hell will break loose - or the party will begin - on Monday, if the team publishes the 1.0.0 version. If we all spend some time into the support here and there during the next weeks we will get it done.

 

[deeveedee]

Well, I have very little to no sense of humor...

If you want to preserve your sanity while you test Beta versions, then you will need a sense of humor. In fact, it should be listed as a prerequisite on the OCLP Sonoma-development download page.

 

[deeveedee]

Hey all, I've run into an issue with the september 26th nightly of 0.6.9.

Did you review the OCLP commits to try to determine the culprit? Some have reported that the latest RestrictEvents.kext commit fixes some things (like Bluetooth). Maybe you should get and build OCLP 0.6.9 again.

EDIT: For the less experienced who are monitoring Sonoma progress and may be wondering why being an early-adopter may be less than desirable for you, this is what happens. The Devs are building the engine while we're driving the car. The engine may stop working and then start working again while we're driving and we must adapt and persist. It's just the nature of Beta software (which OCLP 0.6.9 still is).

 

[MacinMan]

Did you review the OCLP commits to try to determine the culprit? Some have reported that the latest RestrictEvents.kext commit fixes some things (like Bluetooth). Maybe you should get and build OCLP 0.6.9 again.

I've tried to build it, but for whatever reason even following the instructions, I got errors. So I use the nightly link to get the latest pre-compiled nightly.

 

[deeveedee]

I've tried to build it, but for whatever reason even following the instructions, I got errors. So I use the nightly link to get the latest pre-compiled nightly.

Then you won't get the latest commit. Wait until tomorrow to download again and test.

 

[MacinMan]

Then you won't get the latest commit. Wait until tomorrow to download again and test.

I can do that, nothing critical to do with that machine anyway.

 

[MacinMan]

@deeveedee : the instructions on the site say to make sure it's Python from Python.org. I use Homebrew to manage Python, from what I gather they use the source from python.org, should I be ok? I have 3.11.5 instaled.

 

[ImpetuousRacer]

Just a heads up - I have a MacMini 2012 and a MacBook Pro Early 2013. I installed 0.6.9n and upgraded to Sonoma. The upgrade "worked", but everything was extremely slow, NO external drives are recognized, and I couldn't install root patches because the "OS wasn't supported". THIS IS BECAUSE I DID NOT DOWNLOAD 0.6.9 SONOMA DEVELOPMENT BRANCH.

With no WiFi and no drives being recognized, I yanked the drive out of my Mac Mini, plugged into Windows, and used MacDrive 11 to have r/w access with APFS drives with snapshots so I could transfer the correct OCLP, reassembled and installed the correct OCLP Sonoma branch and installed root patches.

For the MacBook, I started with 0.6.8 official and 80% through the upgrade to Sonoma it would hang. I installed 0.6.9n efi and got it to boot. I was about to do the same process of pulling the drive but found that a USB to ETHERNET adapter still works to get internet to download and install the 0.6.9n SONOMA BRANCH to get things going.

Bluetooth doesn't work on either machine currently but to be expected.

Note - Wait until at least 1.0.0 release on ETA 10/2/2023 before upgrading, or if you MUST do now, make sure you know the correct link for the Sonoma Development. I went to the source.md page and selected Sonoma development in the dropdown, but that DID NOT download Sonoma Development branch of OCLPn.

Big Thanks to the developers and community for everything! Excited to still be using these old macs.

 

[deeveedee]

@deeveedee : the instructions on the site say to make sure it's Python from Python.org. I use Homebrew to manage Python, from what I gather they use the source from python.org, should I be ok? I have 3.11.5 instaled.

At the risk of incurring wrath, here are the OCLP 0.6.9 build steps that I use:

• Download and install Python 3.11.5 from python.org. Do not use Homebrew.
• In terminal, execute git clone https://github.com/dortania/OpenCore-Legacy-Patcher -b sonoma-development
• In terminal, cd OpenCore-Legacy-Patcher
• In terminal, pip3 install -r requirements.txt
• In terminal, pip3 install pyinstaller
• In terminal, python3 Build-Binary.command

The resulting OCLP binary is in OpenCore-Legacy-Patcher/dist

I think it's important to say that for anyone who finds these steps to be too complicated to follow, then you probably shouldn't be building your own OCLP.

 

[MacinMan]

At the risk of incurring wrath, here are the OCLP 0.6.9 build steps that I use:

• Download and install Python 3.11.5 from python.org. Do not use Homebrew.
• In terminal, execute git clone https://github.com/dortania/OpenCore-Legacy-Patcher -b sonoma-development
• In terminal, cd OpenCore-Legacy-Patcher
• In terminal, pip3 install -r requirements.txt
• In terminal, pip3 install pyinstaller
• In terminal, python3 Build-Binary.command

The resulting OCLP binary is in OpenCore-Legacy-Patcher/dist

I think it's important to say that for anyone who finds these steps to be too complicated to follow, then you probably shouldn't be building your own OCLP.

I can wait, I was just asking about Homebrew because they didn't say not to use it specifically

 

[deeveedee]

 

[floral]

I wonder when all Intel macs will lose support for the latest macOS (even unofficially)... version 20?

 

[air.man]

The BT dongle support is back! Thanks Devs!

 

[mohkg]

why are yall buiding your own from source? i just download the newest build and check the date it was uploaded

 

[MacinMan]

@deeveedee Just a FYI, i got the python installer directly from python.org installed 3.11.5 followed instructions, got the same build errors that I got with the Python 3.11.5 installed by homebrew. I made sure that I was using the python from python.org and yes, that was what was in the path. So, not sure. Just thought I would share

 

[aespana]

Anyone tested Sonoma with a MacBook Pro 2015?

How it feels? I'm thinking on install Sonoma once the update is available on OC but don't know. The Mac is the base model so, don't know if worth it

 

[headlessmike]

I wonder when all Intel macs will lose support for the latest macOS (even unofficially)... version 20?

My guess is 16 or 17.

 

[deeveedee]

why are yall buiding your own from source? i just download the newest build and check the date it was uploaded

I think you answered your own question, but for those of us who still want to download and build from source, it's because the "nightly" builds are just that ... nightly. If we want recent changes not yet captured in the nightly build, then we need to build ourselves. This is the nature of the OCLP changes and why some have discouraged newbies from testing until OCLP is officially released as version 1.0.0 on Oct 2.

EDIT: And if you want to build OCLP from source, pay attention to the GitHub commits so that you know what you're building and what has changed. You'll waste a lot of time if you keep blindly building the latest source and then wonder why something that was working is no longer working. Github doesn't lie.

 

[deeveedee]

@deeveedee Just a FYI, i got the python installer directly from python.org installed 3.11.5 followed instructions, got the same build errors that I got with the Python 3.11.5 installed by homebrew. I made sure that I was using the python from python.org and yes, that was what was in the path. So, not sure. Just thought I would share

Only thing I can think is that you need to completely remove/uninstall all traces of your old python and start clean. I haven't seen your issue reported, so its rare.

 

[headlessmike]

Only thing I can think is that you need to completely remove/uninstall all traces of your old python and start clean. I haven't seen your issue reported, so its rare.

Or at least make sure to use the right version. I’ve built OCLP many times using Python from MacPorts without any issues. But just running “python” from the command line will usually default to the system Python unless one actively sets it up to find the new version.

 

[Bmld]

Hello ,I install Sonoma on my iMac 2012. The install stop with an error 'don"t find drive ...". I restart and it is the same result. I try an instal Sonoma directly and it don't do it , normal but when I try to restart, the Mac boot directly on a drive Sonoma.data and Sonoma is ok. After the post-instal everything work correctly, wifi, bluetooth ... I don't understand.

Very good job, I congratulate the whole team.

To make my small contribution I write a GUI to schedule the power manager (replace PMSET). my site. Th source code is on Github.

 

[mohkg]

your building it from this source right? https://github.com/dortania/OpenCore-Legacy-Patcher/tree/sonoma-development

 

[fyrefly]

I see a lot of issues with the 2016/17 MacBook Pros, especially with SSDs not being recognized and Touch ID not working earlier in this thread.

Anyone given it a shot with the stable build? Wondering if I should pull the trigger on my 13,3.

My MacBookPro13,3 from 2017 is on the RC2 build (same at the Release Build). No Touch ID, and weirdly no Watch screen Unlock but everything else is working great.

 

[Bmld]

your building it from this source right? https://github.com/dortania/OpenCore-Legacy-Patcher/tree/sonoma-development

That right.