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.
Screenshot 2023-12-26 at 10.52.47 PM.png


Anyone experience this?
 
well, if you did, you were at least aware that there was a name bug but luckily OCLP was smart enough not to fall for it...and if people watch those videos they won't need to ask same questions here again and again....
I don’t see the point of making/watching a video for each point release.
It’s always the same !
Humanity eats amounts of disk space, bandwidth and energy for videos …
I am fed up of videos that takes 5mn to explain how to add a line in a text file, where to find the file explorer or notepad …
People are getting lazy and don’t want or know how to read.
 
I don’t see the point of making/watching a video for each point release.
It’s always the same !
Humanity eats amounts of disk space, bandwidth and energy for videos …
I am fed up of videos that takes 5mn to explain how to add a line in a text file, where to find the file explorer or notepad …
People are getting lazy and don’t want or know how to read.
I understand your point and personal discomfort with such channels. But please don't let us enter into an offtopic discussion within this thread please....
 
This forum is for Macs running macOS and OSX, and this thread in particular, is for unsupported Macs installing and running macOS Sonoma, not for promoting "the other OS that shall not be named"!
for sure ;-) may read the post my post belongs to ;-) and of course the "😂" at the end!
 
  • Like
Reactions: olad
Just wanted to share that its possible to replace the OCLP 1.30 0.96 opencore.efi file in the EFI volume with the latest Opencore 0.97 version without issues as far as I can tell. Was able to reboot with out issues. Perhaps this may provide protection against whatever update apple throws our way before a new version of OCLP comes out.
 
Just wanted to share that its possible to replace the OCLP 1.30 0.96 opencore.efi file in the EFI volume with the latest Opencore 0.97 version without issues as far as I can tell. Was able to reboot with out issues. Perhaps this may provide protection against whatever update apple throws our way before a new version of OCLP comes out.
I reviewed the commits and don't see any OC 0.9.7 improvements over OC 0.9.6 that are important for our unsupported Macs. See OC 0.9.6 -> 0.9.7 commits here.
 
When using OCLP v1.3.0, to Create a macOS installer,
WHY does it say that the local copy (located in the Applications folder)
of Sonoma v14.2.1 (23C71), is Sonoma v14.2 (23C64) ???

It is creating confusion and making me wonder, what installer, am I actually creating.

I have factually verified that I have downloaded Sonoma v14.2.1 (23C71), direct from Apple Developer site.
 
Last edited:
I reviewed the commits and don't see any OC 0.9.7 improvements over OC 0.9.6 that are important for our unsupported Macs. See OC 0.9.6 -> 0.9.7 commits here.
If you read the OC 0.9.7 Change log you can see that it solves an issue not being able to boot into recovery mode. Replacing the opencore.efi file is a bright idea. Now you don't need to have the OCLP 1.1.0 EFI (OC 0.9.3) installed on an external drive any longer. Bootkicker.efi still does not work, that is per other posts blamed on a bug in the Apple boot loader.
 
I reviewed the commits and don't see any OC 0.9.7 improvements over OC 0.9.6 that are important for our unsupported Macs. See OC 0.9.6 -> 0.9.7 commits here.
On the Dortania/Github site, they state that there is no reason to update the OCLP on your device unless something goes wrong; I take that to mean that if it works for updates it works and if there is any element that doesn't then you'd soon find out. Speculative on my part though; in the absence of clear information it's tempting to "futureproof" by replacing the OCLP; at least on occasion. I haven't done the forensic search that's probably required but I haven't seen any place to sign up for important news either e.g. some forewarning should a new update be likely to not allow OCLP to work.
 
If you read the OC 0.9.7 Change log you can see that it solves an issue not being able to boot into recovery mode. Replacing the opencore.efi file is a bright idea. Now you don't need to have the OCLP 1.1.0 EFI (OC 0.9.3) installed on an external drive any longer. Bootkicker.efi still does not work, that is per other posts blamed on a bug in the Apple boot loader.
I don't know how to "read" the change log; saw a mention of recovery url text or some such - but either way; wouldn't this only apply during or after the install process and not once installation / updates have been successful? When I updated to Sonoma 14.2.1 I was only able to get into safe mode; by some unknown means I only once got into Recovery from there and my backup Monterey install drive didn't come up - so things were looking grim and presumably there were other similar reports. I was following the Dortania/Github guide so without Recovery it looked like my device was near useless unless I could find and uninstall anything related to OCLP.
 
Last edited:
If you read the OC 0.9.7 Change log you can see that it solves an issue not being able to boot into recovery mode. Replacing the opencore.efi file is a bright idea. Now you don't need to have the OCLP 1.1.0 EFI (OC 0.9.3) installed on an external drive any longer. Bootkicker.efi still does not work, that is per other posts blamed on a bug in the Apple boot loader.
Good catch. I didn't see the commit reference to MBP14,1. Has anyone confirmed that this OC 0.9.6 -> 0.9.7 fixes recovery booting on their unsupported Mac?
 
I reviewed the commits and don't see any OC 0.9.7 improvements over OC 0.9.6 that are important for our unsupported Macs. See OC 0.9.6 -> 0.9.7 commits here.

My intention was just to share that your not going to break your system replacing the opencore.efi file with 0.97. As far as any benefits vs not who knows.
 
  • Like
Reactions: deeveedee
My intention was just to share that your not going to break your system replacing the opencore.efi file with 0.97. As far as any benefits vs not who knows.
I'm running OC 0.9.7 on my MBP6,2, so our thoughts are aligned. I just haven't found any benefits in the OC 0.9.6 -> 0.9.7 upgrade on my MBP6,2, but the Recovery Boot is something I didn't catch (doesn't apply to my MBP6,2). When upgrading from OC 0.9.6 -> 0.9.7, the following binaries are usually upgraded:

OC 0.9.6 -> OC 0.9.7
  • EFI/OC: Update OpenCore.efi
  • EFI/OC/Drivers: Update OpenRuntime.efi and other .efi driver files
  • EFI/OC/Tools: Update .efi tools files
  • EFI/OC/config.plist - No required changes
 
yeah, looked at 11 but it is so picky about hardware kind of like buying tires and then the car.
Sorry that was just a little friendly joke, you may get me wrong - sorry, here is all about Sonoma 😂 thankfully working due to OCLP Dev Team on legacy hardware 😍
 
  • OCLP:: Advanced > FeatureUnlock: Partial (change setting, "Build and Install Open Core", reboot)
I can't find a description of the exact effect of the different FeatureUnlock settings anywhere. Do you have detailed information on this if you keep recommending it?


Seems like its related to the AvatarPickerMemojiPicker component.
The OCLP issues page state:
Memoji's Freezing/Crashing​
Non-Functional​
Intel Ivy, Haswell iGPUs and Nvidia Kepler GPUs​
Don't set Memoji as Profile Picture. Last functional on 13.0 Beta 1 (22A5266r)​

So not sure how to fix because I didn't set any memoji's as far as I know.
Have a look at my next post - directly below this one - it might help you.


Another strange issue happened today. Was doing a backup last night and closed the lid in the morning. Took the macbook pro to work and when I took it out of my carry case all the fans were going full speed and it was hot as hell and unresponsive! Had to force shut down and got kp at boot first try. Second try booted into Sonoma. Makes me wonder if power management is working at all. Will roll back to Big Sur. Can't be too safe.
I had the same problem with my rMBP 11.2.
After I stopped setting the screensaver to Sonoma Horizon or other graphics-intensive screensavers (I now use the "macOS Ventura" screensaver) and now use an equally graphics-friendly background image on all desktops (!no Sonoma backgrounds), I no longer have this problem. Thanks goes to @deeveedee
 
👉🏻 *HOW 2 Update/Upgrade macOS with OCLP* 😃

Since some of you are still having problems with Sonoma, here are my tips:
  1. ❗️ *NEVER use Memoji* as User Pic / iCloud User Pic with OCLP
    👉🏻 ATTENTION❗️ iOS 17.1+ your Contact Photo in adress book sync to iCloud and so to your Login pic. 😱
    *** So DON'T use Memoji there either❗️***
  2. ❗️ *First install OCLP* (if upgrading i.e. macOS 13 ➡️ 14 ALWAYS❗️"Create macOS Installer")
    OR IF you're on macOS "Sonoma" then first❗️check if there's a NEW version of OCLP and install this *INCLUDING* new "Build and Install Opencore" to you start disk + check/install "Post-Install Root Patch"
  3. Now you could use the system updater to get the latest macOS 14.x version – but better is to wait till OCLP developers push out a new OCLP patcher version that includes the corresponding macOS update.😉
  4. ❗️ *Install the root patches* – in "secure boot mode" always the best

⚠️⚠️⚠️ 👉🏻Currently, it *seems to be safest to always perform the updates* - not just the upgrade to macOS Sonoma 14.x.x - *using the OCLP USB installer.* ⚠️⚠️⚠️


Hope this helps you! 👍🏻


With macOS 14.1 I had freezing Lock Screen but since installing root patches in secure boot – no freezing Lock Screen anymore.
Since now no issues with the macOS 14.2+ and OCLP 1.3.0 🥳 - except for the "Memories" function in the Photos app (Photos app crashes)😢
👉🏻 my system: 15" MacBook Pro [rMBP 11,2 Mid 2014 / only Intel Iris Pro] macOS 14.2.1 + OCLP 1.3.0



PS:
*Pls read this infos from OCLP developers:*
Sonoma issueshttps://dortania.github.io/OpenCore-Legacy-Patcher/SONOMA-DROP.html#issues
Troubleshootinghttps://dortania.github.io/OpenCore-Legacy-Patcher/TROUBLESHOOTING.html

***

Please follow EXACTLY the corresponding step-by-step tutorial for macOS Sonoma or Ventura (video length approx. 30-60 min), which "Mr. Macintosh" explains on Youtube. It is also worth watching the other videos on his channel - especially the latest videos!
https://www.youtube.com/@Mr.Macintosh/videos


Jesse's videos are also very helpful - especially when it comes to special cases and bugs.
Just have a look at his videos from the last 3 months:
https://www.youtube.com/@JessiesFlying/videos
 
Last edited:
Installed Sonoma on a 2015 15" Macbook Pro. All the normal tasks runs smoothly, but :

1. I can not import images/scans from my iPhone (is an Iphone 6 SE, a little old, but in Catalina this feature runs well, and I think also in Monterey)
2. No continuity camera at all in Facetime
3. Universal Control not available

In general, the speed of all the system is surprisingly faaaast, perhaps more than in Monterey, that is his OS from factory.

Any ideas/tricks to solve the 3 problems ? I think I could live without them, but I prefer an OS that is capable 100% with all his features available and running.

Thanks in advance,

J.
 
1. I can not import images/scans from my iPhone (is an Iphone 6 SE, a little old, but in Catalina this feature runs well, and I think also in Monterey)
2. No continuity camera at all in Facetime
3. Universal Control not available
1. What do u mean exactly with "import"? You'd like to import scans from iPhone to notice app?

2.+3. See my post above yours or the snip below


Edit:
What 15" Macbook Pro 2015 do you have exactly?
 
Last edited:
  • Like
Reactions: luckyduke23
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.