There will be different preferences and opinions. That sounds like a good choice for your needs.
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
MacBook Pro 13 (Early 2015), base model.
I tried a clean install of Sonoma a few days ago - it was horrible. A lot of lags, freezes, and warming up. I used the latest OCLP nightly at that moment. So, I returned to Ventura via clean install, which runs fine and smoothly on my Mac. Today, I decided to try another method of Sonoma installation. I made the latest OCPL via Python, reverted patches in Ventura OCPL 0.6.8, and then installed OCLP 0.6.9n to EFI. I downloaded and updated Sonoma via the Sonoma installer from OCLP 0.6.9n on Ventura without root patches. Then, I logged in and installed the latest root patches on Sonoma. In the end, I reset NVRAM for clarity. Now Sonoma runs as good as Ventura was, perfect! On Monday, I'll update OCLP to release version and update to release patches with reverting old ones. Everything works, including Wi-Fi and Bluetooth.
I tried a clean install of Sonoma a few days ago - it was horrible. A lot of lags, freezes, and warming up. I used the latest OCLP nightly at that moment. So, I returned to Ventura via clean install, which runs fine and smoothly on my Mac. Today, I decided to try another method of Sonoma installation. I made the latest OCPL via Python, reverted patches in Ventura OCPL 0.6.8, and then installed OCLP 0.6.9n to EFI. I downloaded and updated Sonoma via the Sonoma installer from OCLP 0.6.9n on Ventura without root patches. Then, I logged in and installed the latest root patches on Sonoma. In the end, I reset NVRAM for clarity. Now Sonoma runs as good as Ventura was, perfect! On Monday, I'll update OCLP to release version and update to release patches with reverting old ones. Everything works, including Wi-Fi and Bluetooth.
Attachments
Last edited:
This is exactly what happened over two separate computers (my extra 2015 13-inch MBP and 2015 11-inch MBA). OS 14.1 seemed to install and work as expected w/o root patches (no wifi or graphics acceleration w/ limited graphics) then when root patches was applied, the computer would either freeze at the Apple logo while booting up or go into repeated boot cycling once the initial display came up to allow you to enter your password.
I have since erased the storage drive and reinstalled 14.0 on these computers and will remain at this version until a fix has been put out. Currently using OCLP 0.6.9n.
For those who like privacy, there is an option in OCLP GUI that lets you control whether analytics are shared with OCLP Devs. I have nothing against the Devs and have only the highest respect for them and what they have accomplished. It's just that I am generally paranoid about privacy. I opt out of Apple Analytics for macOS Betas and I also opt out of OCLP analytics (when I remember). At one time, a version of the OCLP GUI defaulted to collecting and reporting the OCLP analytics. I think the default is now "Disable Reporting." If you care about this kind of stuff, examine the App Settings in OCLP GUI and make your selection before you apply post-install patches. I assume that OCLP post-install patches respect this setting.
EDIT: ... and no offense intended, but if you have to ask "Is my Mac secure when I use OCLP and OC ...?," you probably don't really care much about computer security.
EDIT2: ... and if you convince yourself that you really care about computer security and you need to do your online banking in a secure environment. Buy a new Mac. Just my opinion - others will have differing views.
EDIT3: ... sorry to burden you with more details, but I'm having a parallel conversation that's relevant to this. Let me shed some light on this and illustrate in a way that might make sense. By using OCLP to enable macOS on unsupported devices, we are "rooting" our Macs. This means that we are giving the most sensitive access possible to others we trust. No matter how trustworthy, people, processes and software can be hacked. And by the way, all the hackers I've met are dumb and unsophisticated. And you can recognize them immediately, because they are mean.
EDIT4: ... yup, my side conversation is still going... security vulnerabilities don't have to be intentional. They can be exposed because of software bugs. But of course, as we have seen, OCLP and OC never have any bugs. Especially the beta versions.
EDIT: ... and no offense intended, but if you have to ask "Is my Mac secure when I use OCLP and OC ...?," you probably don't really care much about computer security.
EDIT2: ... and if you convince yourself that you really care about computer security and you need to do your online banking in a secure environment. Buy a new Mac. Just my opinion - others will have differing views.
EDIT3: ... sorry to burden you with more details, but I'm having a parallel conversation that's relevant to this. Let me shed some light on this and illustrate in a way that might make sense. By using OCLP to enable macOS on unsupported devices, we are "rooting" our Macs. This means that we are giving the most sensitive access possible to others we trust. No matter how trustworthy, people, processes and software can be hacked. And by the way, all the hackers I've met are dumb and unsophisticated. And you can recognize them immediately, because they are mean.
EDIT4: ... yup, my side conversation is still going... security vulnerabilities don't have to be intentional. They can be exposed because of software bugs. But of course, as we have seen, OCLP and OC never have any bugs. Especially the beta versions.
Last edited:
Saw this one literally last minute before restarting to install 14.1. Pheew. Thanks for the heads up!
Okay, I got Sonoma up on my 2017 iMac 18,3, but I get a failure doing the root patch install:
Everything appears to be working, but WiFi, which I can live with using an ethernet cable, but it would be rad to get it fully up. Any suggestions on how to get this moving?
Everything appears to be working, but WiFi, which I can live with using an ethernet cable, but it would be rad to get it fully up. Any suggestions on how to get this moving?
Are you maintaining a wired Ethernet connection during the patching? If so, you may want to wait for another OCLP pre-built version to be issued.
The first time I attempted patching I was not. This most recent time, from that screenshot, I had it cabled up. It. tossed me the same error either way.
Edit - Should I try reverting the root patches and doing it again while maintaining a wired connection?
Edit 2 - My MacBook was on a cabled link the entire time I root patched, so maybe that's why it went with no issue?
Not sure. Maybe wait for another pre-build OCLP or try building some earlier versions yourself.
EDIT: You can also try Reverting patches before you apply them.
YOLO! I got a time machine backup of this thing before I started messing with it anyway...
Good idea. In addition to TM, I do all my testing in separate APFS volumes, so I don't touch working volumes.
Did a revert, reboot, apply, all while connected to cable and no dice. Same error rebuilding the kernel cache. I know I'm playing in untested waters, so I'll just hang tight. I can use my iMac fine over the wire for now, so it's not like I'm dead in the water. Everything but the wifi adapter works. Any place I should submit logs/bugs to in order to help these excellent devs out?
I just learned! Here's the config.plist. The adapter in question is a BCM43602.
Edit - Holy crap I didn't think it would paste like that.
Edit 2 - Here's a link to the config.plist. I know it looks sussy but I swear it's a legit link to my Nextcloud instance:
@plentyoftimeto69 - @perez987 may know how to contruct your EFI and kexts to enable BCM43602. Not sure.
EDIT: According to Dortania Docs, your Wi-Fi is natively supported by OCLP. We should be able to figure this out.
EDIT: According to Dortania Docs, your Wi-Fi is natively supported by OCLP. We should be able to figure this out.
Last edited:
That's what I figured. The BCM4360 (not BCM43602) in my MacBook Air came right up without a hitch.
Nope. Too late. Rendered my machine useless. I got three backups, a second ssd with sonoma RC installed, can’t get my machine to boot whatsoever.
I even created a new volume with a Sonoma installer official release, but immediately after the reboot, it tells me a certain firmware update can’t be installed.
I even created a new volume with a Sonoma installer official release, but immediately after the reboot, it tells me a certain firmware update can’t be installed.
My recommendation: keep your hands off 14.1beta for now.
Attachments
If you are trying to convince us that we should be careful when playing with Beta, you have finally convinced us.
@amaze1499 It's easy to become mired in the weeds between 14.0 and 14.1. This is a more important issue when considering the use of OCLP and Beta Software.
EDIT: @amaze1499 I just read my post and decided I won't be doing anything on my OCLP-rooted Mac that needs any degree of computer security or password privacy. But that's just my preference. This view has changed for me from my earlier "trusting" posture, now that OCLP is rooting Wi-Fi and all data is moving through the rooted network.
Last edited: