yes
I don’t see the point of making/watching a video for each point release.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 understand your point and personal discomfort with such channels. But please don't let us enter into an offtopic discussion within this thread please....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.
for sure ;-) may read the post my post belongs to ;-) and of course the "😂" at the end!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"!
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.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.
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.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.
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.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?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.
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: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.
yeah, looked at 11 but it is so picky about hardware kind of like buying tires and then the car.You may like eleven and https://answers.m 😂
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 😍yeah, looked at 11 but it is so picky about hardware kind of like buying tires and then the car.
Please cease encouraging OT posts. Much thanks.for sure ;-) may read the post my post belongs to ;-) and of course the "😂" at the end!
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?
- OCLP:: Advanced > FeatureUnlock: Partial (change setting, "Build and Install Open Core", reboot)
Have a look at my next post - directly below this one - it might help you.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.
I had the same problem with my rMBP 11.2.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.
1. What do u mean exactly with "import"? You'd like to import scans from iPhone to notice app?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
PS:
*Pls read this infos from OCLP developers:*
Sonoma issues – https://dortania.github.io/OpenCore-Legacy-Patcher/SONOMA-DROP.html#issues
Troubleshooting – https://dortania.github.io/OpenCore-Legacy-Patcher/TROUBLESHOOTING.html
***