Did you use OCLP from the sonoma-branch? Looks like OCLP assumes your machine is still supported.
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
My MacBookPro14,2 is from 2017, 13", Touch Bar, 4 Thunderbolt 3 ports. Ventura (the current installed OS) will be the last macOS natively supported with this machine. So Sonoma is out without OCLP.
Last edited:
@coasterOneEightThree There certainly could be a bug in OCLP 0.6.9n (it is Beta). Are you certain that you are using the OCLP 0.6.9 Nightly build for Sonoma from here. When I run OCLP 0.6.9n, it lists your MBP14,2 as one of the target models for patching.
If you're not certain of the origin of your specific OCLP 0.6.9 (and even if you are), download it again from here (click the link labeled "Nightly.link: OpenCore-Patcher.app (Sonoma Development)".
If you're not certain of the origin of your specific OCLP 0.6.9 (and even if you are), download it again from here (click the link labeled "Nightly.link: OpenCore-Patcher.app (Sonoma Development)".
Last edited:
Now I see! I totally missed the separately developed OC Patcher for Sonoma.
Thank you @deeveedee and @hvds . Really appreciate this ...
Last edited:
The Sonoma and OCLP installation works with my MacBookPro14,2!
Of course, I have not yet been able to thoroughly test the system in its current form, but it looks very good so far. Bluetooth and WiFi work, AirDrop too. That's all I've checked yet. But that's some good news, right?
Good!
In case you would like to dive abit in how OCLP works, you could look at the source in Github. E.g. this /data/model-array.py
OpenCore-Legacy-Patcher/data/model_array.py at sonoma-development · dortania/OpenCore-Legacy-Patcher
Experience macOS just like before. Contribute to dortania/OpenCore-Legacy-Patcher development by creating an account on GitHub.
github.com
I find OCLP very well structured and readable Python code.
Where did you get an OCLP version dated 9.01.23? The current Sonoma branch version is dated 8.23.23 and the Ventura branch is dated 8.21.23.
It's the date I downloaded the nightly build. Sorry - thought that was obvious. Given that OCLP Devs have provided us with a mechanism for building our own, the only way I see to define a build is by the date downloaded/created. Downloads and self-builds with different dates may be the "same" if there have been no dev changes in the interim.
Right; the date of the last commit (23 Aug) rather than the build from source, may be an extra option.
Last edited:
I won't claim to be a version numbering expert and will defer to the experts. I'm naive enough that I would never have had two branches numbered 0.6.9. I promise I'll screw it up the next time, too and hope for an official release to save me.
Guys, after I installed Sonoma on my MacBookAir7,2, it isn't able to connect to WPA2 Enterprise networks. Work on my Catalina partition, but not on Sonoma. Anyone know what could be causing this? TIA. P.S: Been happening since Sonoma beta 4, now I'm on Beta 7
Hello,
Anyone has tested it on a MacBookPro14,3 ?
I'm having continuous problems with the built-in display as well as with external ones... sometimes the screen starts flickering after login, others it does it after resume from sleep... and most of the time, the built-in display stops being detected and only the external one works.
I updated it from Ventura, could this be the cause of the problem? I thought it was not necessary to make a clean install.
Thank you !
Anyone has tested it on a MacBookPro14,3 ?
I'm having continuous problems with the built-in display as well as with external ones... sometimes the screen starts flickering after login, others it does it after resume from sleep... and most of the time, the built-in display stops being detected and only the external one works.
I updated it from Ventura, could this be the cause of the problem? I thought it was not necessary to make a clean install.
Thank you !
I've seen this issue solved with previous versions of macOS (some reported solving it by resetting PRAM). Google might be your friend.
Also, have you tested Big Sur, Monterey or Ventura? Sonoma is still an unreleased Beta OS.
Thing is, if I create a new user account, the wifi works normally, but if I restart, or turn the wifi off then on, it won't work, and tell's me it couldn't connect to the network. It's really odd. Reseted PRAM and SMC, did nothing.
You'll have to forgive me for not wanting to debug a Beta OS. Did you conduct any testing in Big Sur, Monterey or Ventura?
This is what it looks after wake up from sleep as well as 50% of times when it turns on:
And when I connect an external display, most of the times the built-in screen stops working (it looks like it is turned off, I mean, it doesn't look to be a brightness adjustment problem); some times it is still present on the display settings section (like in the photo), and some others only the external display appears.
Am I the only one with this problems on a MacbookPro 14,3 (2017, 15" touchbar, 4TB ports)?
Today I downloaded OCLP from the well-known location and installed it on my cMac Pro 5.1 2010.
After the reboot & postinstall, I was surprised about the color display on my Nvidia 680 GTX, which had been working normally until recently.
I then re-installed the patcher from August 23rd. and now the color reproduction is correct.
Has anything changed about OCLP in the last few days?
By the way: BT (original module) still doesn't work properly. I can activate it, it waits briefly for BT devices, finds nothing and switches off automatically after seconds. Can missing USB1.1 be the reason?
After the reboot & postinstall, I was surprised about the color display on my Nvidia 680 GTX, which had been working normally until recently.
I then re-installed the patcher from August 23rd. and now the color reproduction is correct.
Has anything changed about OCLP in the last few days?
By the way: BT (original module) still doesn't work properly. I can activate it, it waits briefly for BT devices, finds nothing and switches off automatically after seconds. Can missing USB1.1 be the reason?
Last edited:
How do you re-install the older version? I downloaded it (0.6.8) but it says there are no available patches for my system, even if I revert them from the 0.6.9 app.
Hi,
This happened to me. It happens with the DMGs that have the quarantine attribute set at download (for me, all of them xD):
Code:
-[DiskImageMounterDelegate application:openURLs:]_block_invoke: Failed to attach <private>: Error Domain=com.apple.DiskImages2.ErrorDomain Code=153 "Disk image operation failed with error code 153" UserInfo={DIErrorVerboseInfo=Failed to quarantine device, error=0xe00002c2, NSLocalizedDescription=Disk image operation failed with error code 153}You can check the attributes with xattr -l <DMG name>:
Code:
xattr -l Additional_Tools_for_Xcode_12.5.dmg
com.apple.FinderInfo:
com.apple.diskimages.fsck: <9?H @???*vP???34.
com.apple.diskimages.recentcksum: i:71352412 on 93EC4DB0-2A8F-4B9C-AF0C-D126DB62AA45 @ 1621629960 - CRC32:$B9BE333F
com.apple.metadata:kMDItemDownloadedDate: bplist00?3A?,)?>?
com.apple.metadata:kMDItemWhereFroms: bplist00?_xhttps://download.developer.apple.com/Developer_Tools/Additional_Tools_for_Xcode_12.5/Additional_Tools_for_Xcode_12.5.dmg_7https://developer.apple.com/download/more/?=for%20Xcode
?
com.apple.quarantine: 0083;60a81c08;Safari;F591962B-D7BD-4A9E-A5E0-D250C8E6429BIf the file has it, as in this case you can just remove it with unqt, like so:
Code:
unqt Additional_Tools_for_Xcode_12.5.dmgAfter that, the DMG will mount normally.
Cheers!