How nice of you! And how did you learn, hmm? Probably by doing searches and asking questions. So why can't someone less knowledgeable come to this thread to ask for help? Or maybe is it that you feel empowered that you got things to work and you now feel a sense of bragging rights?
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
Let's not turn this so far very informational thread into an arguing thread. It isn't worth it. Let's just help everyone, and if you don't want to help less experienced persons, don't. We are a big enough community, there are other persons who will.
Just because the development team decided not to waste another summer on helping new users installing the next macOS beta - which just broke features fixed with the most recent internal development patcher version. This is a rat race you cannot win.
The team has less than ten members, the active community here with the needed skill set is about of the same size but we have several hundred thousands of different OCLP installations. It simply does not scale any longer. We cannot reverse engineer macOS, explain the patcher, help new users, have a normal living, perform at our jobs at the same time. So we decided to block any requests until a working OCLP release has been published. Even then you would experience the usual banana software effect - it ripes only in the hands of the end user.
There are simply no resources to satisfy requests. Just wait a few more days…
Best course of action would be simply ignoring any new user request until both Apple and the OCLP team have released their supported software.
No, it is apparently not big enough. You only drag inexperienced users into an experiment which may end in data loss and frustration. When things break seriously users reach out on all official and private channels to get help, but they certainly do not ask for your help - unless you can fix the patcher yourself.
OCLP 0.6.9 09/27/23 02:51 broke the support to my external BT dongle (Hideez USB Smart BT dongle). In addition the internal BT is broken since initial Sonoma testing.
Went back to OCLP 0.6.9 09/26/23 15:49 and restored the dongle functionality.
Could this issue be related to OC 0.9.5 introduction ?
Went back to OCLP 0.6.9 09/26/23 15:49 and restored the dongle functionality.
Could this issue be related to OC 0.9.5 introduction ?
If you read my post and interpreted it that way, then I am sorry that you interpreted it that way.
Last edited:
Etiquette evolves... to really benefit from this thread and the other 'unsupported Mac' threads one needs to go back through them and read, preferably before making the decision to start one's own unsupported Mac project. Don't forget you can also search those threads if you keep the search terms simple.
Also, putting your Macs' basic specs in your forum signature will save everyone a lot of time. No-one is going to spend much time going back through your previous posts where you might have mentioned it.
Also, putting your Macs' basic specs in your forum signature will save everyone a lot of time. No-one is going to spend much time going back through your previous posts where you might have mentioned it.
You may be able to diff the config.plists and the kext versions generated by each OCLP to answer this yourself. I don't see anything about OC 0.9.5 that would affect the BT dongle, so I suspect it is a kext version change or an OC config.plist change. If the diff doesn't help, then possibly something in the post-install patch, but probably not OC 0.9.5.
EDIT: Also look at the OCLP recent commits to see if you can identify the change that may have caused this. Before you start questioning OCLP, you may want to revert post-install patches and then reapply post-install root patches.
Much truth in this.
Many got tired of helping (over and over). I reached that point a while back and only visit the non-help channel of the discord.
No, it isn't related to post install patches. OCLP broke the dongle support with or without post-install. Thanks.
The problem can be illustrated like that:
If someone who is not able to check oil level on an engine ask you how to completely disassemble the engine, do you think it's a good idea to explain him ?
Learning is important, but it's step by step, if you are a complete beginner, it's not a good idea to install an unsupported OS with an unsupported tool on an unsupported hardware.
Someone who is not able to navigate and understand Github repos is probably not skilled enough to manage this kind of activity and the problems that will occur.
Ok - just to make sure you understood me, I suggested more than just post-install patches. You may be able to figure this out by comparing config.plists and kext versions from the different OCLP versions.
EDIT: Also review the OCLP Sonoma-development commits for clues.
I need to find the photo I took of my completely disassembled 1995 Maxima engine. Amazingly, the car ran for another 100K miles after I reassembled it.
MacBook 15" 2017... upgrade from 13.6 to Sonoma 14 with sonoma installer USB stick and latest OCLP September 27th with OpenCorePkg 0.9.5... everything works well except, obviously, the touchID and also the bluetooth which, although it seems active, does not detect no devices and has not inherited devices previously installed on the Ventura
Attachments
Had a hard time to update Sonoma to RC 2, OTA did not work, the download did not finish even though macOS reported so, it later could not verify.
So, I created a USB installer, that worked, this was only a few days ago.
So, next I tried it the same way, OTA did not work, recreated the USB installer multiple times but the install got bogged.
Update installer couldn't verify, it took quite a bit of time after starting to get to this point.
Not able to start from Sonoma either, and, the original disk (name = MacMini) vanished, I could only choose the MacMini-Data disk.
Eventually I decided to use a slow (128GB) SD card, now, that worked.
Wow, now it seems...no, it is a lot faster than before, all seems to work, even Bluetooth, had trouble last few day, Trackpad and Keyboard did not show up.
Thanks to the great developers, cheers to them.
So, I created a USB installer, that worked, this was only a few days ago.
So, next I tried it the same way, OTA did not work, recreated the USB installer multiple times but the install got bogged.
Update installer couldn't verify, it took quite a bit of time after starting to get to this point.
Not able to start from Sonoma either, and, the original disk (name = MacMini) vanished, I could only choose the MacMini-Data disk.
Eventually I decided to use a slow (128GB) SD card, now, that worked.
Wow, now it seems...no, it is a lot faster than before, all seems to work, even Bluetooth, had trouble last few day, Trackpad and Keyboard did not show up.
Thanks to the great developers, cheers to them.
Out of curiosity, I tried OCLP 0.6.8 to install macOS Sonoma non-beta public release...
I was able to install macOS Sonoma on my MacBook Pro 2015, however, Wi-Fi is not working (disabled)... I guess I'll just wait for OCLP 1.0 to use Sonoma and go back to Ventura for now... It's just a few days of wait anyway...
I was able to install macOS Sonoma on my MacBook Pro 2015, however, Wi-Fi is not working (disabled)... I guess I'll just wait for OCLP 1.0 to use Sonoma and go back to Ventura for now... It's just a few days of wait anyway...
OCLP 0.6.8 doesn't support Sonoma. Did you mean 0.6.9 (and specifically the Sonoma-development version)?
EDIT: Leaving this post in case someone has another explanation, but some reported on Discord that Bluetooth was broken during recent OCLP 0.6.9 development. Apparently this commit fixes the breakage.
-----------------------------------------------------
The latest commit to OCLP 0.6.9 development "syncs RestrictEvents.kext" to version 1.1.3.
The OCLP 0.6.9 Sonoma-development builds that I have been downloading already have RestrictEvents.kext 1.1.3. Can someone with more GitHub experience than me explain what this commit actually does? thank you.
EDIT: BTW, I'm not certain, but I think it was the upgrade from RestrictEvents.kext 1.1.2 -> 1.1.3 combined with revpatch=sbvmm in config.plist that fixed macOS upgrades and installs on my MBP6,2. Prior to this RestrictEvents.kext change, I had to make some manual changes to my config.plist to facilitate macOS installs and upgrades.
-----------------------------------------------------
The latest commit to OCLP 0.6.9 development "syncs RestrictEvents.kext" to version 1.1.3.
The OCLP 0.6.9 Sonoma-development builds that I have been downloading already have RestrictEvents.kext 1.1.3. Can someone with more GitHub experience than me explain what this commit actually does? thank you.
EDIT: BTW, I'm not certain, but I think it was the upgrade from RestrictEvents.kext 1.1.2 -> 1.1.3 combined with revpatch=sbvmm in config.plist that fixed macOS upgrades and installs on my MBP6,2. Prior to this RestrictEvents.kext change, I had to make some manual changes to my config.plist to facilitate macOS installs and upgrades.
Last edited:
@winxmac Read this entire page. Find the link titled 'Nightly.link: OpenCore-Patcher.app (Sonoma Development)' and click it to download the latest pre-built OCLP 0.6.9 for Sonoma. Devs do not want us to share the direct link (which is why I'm not sharing the direct link).
If you are uncomfortable with using the Beta version of OCLP 0.6.9 for Sonoma (which has not yet been released by the Devs), then wait for OCLP 1.0.0 which is scheduled to be released on Oct 2.
If you are uncomfortable with using the Beta version of OCLP 0.6.9 for Sonoma (which has not yet been released by the Devs), then wait for OCLP 1.0.0 which is scheduled to be released on Oct 2.
I don't like helping people, but for you, I made an exception.
EDIT: Now that we're introduced, I've been told that my humor is too dry and too subtle.
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.
Well, I have very little to no sense of humor... You could say I'm not sociable, although I prefer to be alone most of the time and learn and do things on my own, but of course, at some point we will need to ask for someone's help...
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.
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.
Last edited: