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.
Updated my 2012 MacBook Air just fine to 13.2 RC but there is a problem. I had activated advanced data protection for my iCloud account. Now on this patched machine I get an error saying can’t use this account on this machine because need MacOS 13.1 or higher and the machine can’t be updated? Weird because I’m on 13.2. My hackintosh accepted the data protection just fine. Any ideas?
 
If I wanted to changed my sidecar settings on my installation where OCLP was already installed using its defaults, what's the best way? im having the memory issue/crash (the command +V and arrow keys crashing apps). someone advised me to adjust my sidecar/airplay settings from "enabled" to "partially disabled" in the OCLP menu. I did this, rebuilt OCLP and viewed in the logs it was set to partially disabled, then installed and rebooted. the enabled menu continues to come back. must OCLP be entirely uninstalled to complete this or is there an easier way?

Thanks for this tip. Seems to have done the job for me (MBP 9,1 and 10,2) - had quite a few app crashes before.

The OCLP app starts with default settings every time, but that doesn't mean to say that your OC EFI does as well. You build and install OC based on the settings you've chosen just before. So you should be fine.
 
Updated my 2012 MacBook Air just fine to 13.2 RC but there is a problem. I had activated advanced data protection for my iCloud account. Now on this patched machine I get an error saying can’t use this account on this machine because need MacOS 13.1 or higher and the machine can’t be updated? Weird because I’m on 13.2. My hackintosh accepted the data protection just fine. Any ideas?
I take it that ADP won't work with OCLP? Good to know it works on Hackintosh, though.
 
  • Like
Reactions: tennisproha
No, just that I cannot downgrade my system to 13.1 but likely to 13.2 beta 1 from beta 2.
How are updates, i.e. 13.0 to 13.1 or 13.1 to 13.2, etc handled with this patcher ? I thought I read on OCLP's website that they take care of it and I presumed that meant our machines will get a notification that an update is available, just like normal. I've got a new MBA and one of our kids is using my old MBA that I used OCLP to get it running Ventura but I don't know if I need to tell her to not update it if it prompts her and so on, so I was wondering what to do.
 
How are updates, i.e. 13.0 to 13.1 or 13.1 to 13.2, etc handled with this patcher ? I thought I read on OCLP's website that they take care of it and I presumed that meant our machines will get a notification that an update is available, just like normal. I've got a new MBA and one of our kids is using my old MBA that I used OCLP to get it running Ventura but I don't know if I need to tell her to not update it if it prompts her and so on, so I was wondering what to do.

You can’t expect OCLP to automatically support apples next update to be safe the safest route would be to click off all automatic os updates because it’s a patcher at the end of the day Apple can change there code which means the patcher would also need changing safest bet would be to wait look here and see people that report safe update to next release Ventura support is extremely good at the moment but it didn’t support as good as it does now took the developers time to get to this level of support so the next OS update could break certain ways OCLP patches it would be best if it’s a important machine to never jump straight into a update and always keep a backup.
 
Last edited:
Gotta Love khronokernel and the oclp Team.
Updated to 13.2 RC no issues.
No BT of course and I didn't update my iCloud.
(iMessage works, FaceTime works, Ect...)
Cheers!
Screenshot 2023-01-20 at 4.42.11 AM.png
 
You can’t expect OCLP to automatically support apples next update to be safe the safest route would be to click off all automatic os updates because it’s a patcher at the end of the day Apple can change there code which means the patcher would also need changing safest bet would be to wait look here and see people that report safe update to next release Ventura support is extremely good at the moment but it didn’t support as good as it does now took the developers time to get to this level of support so the next OS update could break certain ways OCLP patches it would be best if it’s a important machine to never jump straight into a update and always keep a backup.
That is exactly right! While I also appreciate the hard work the developers have put into this project, they are now occupied with getting the older machines running well. On my iMac 15,1 (late 2014 model i5 with a AMD Radeon R9 M290X 2 GB GPU, Ventura 13.1 runs fine with OCLP 0.53 and also with the latest nightly. However, with the RC 13.2 22D49 system, the Root Patches seem to go OK, but they are not fully implemented. The UI is slow in response, the Dock has a white line around it (not seen with 13.1 after the root patches) and the Display settings are off, with the "default" resolution shifted to the right. Opening folders etc. is slow and it can take several seconds to recognize a mouse click. All in all, I am afraid to upgrade the OS! I have tried the 13.2 betas too, same bad result. Reverting to 13.1 can take a long time too. I tried to log in at the Discord site to report this situation, but that process was beyond me. I can only hope the Developers get a report from someone else.
 
  • Like
Reactions: NataliaC and hvds
That is exactly right! While I also appreciate the hard work the developers have put into this project, they are now occupied with getting the older machines running well. On my iMac 15,1 (late 2014 model i5 with a AMD Radeon R9 M290X 2 GB GPU, Ventura 13.1 runs fine with OCLP 0.53 and also with the latest nightly. However, with the RC 13.2 22D49 system, the Root Patches seem to go OK, but they are not fully implemented. The UI is slow in response, the Dock has a white line around it (not seen with 13.1 after the root patches) and the Display settings are off, with the "default" resolution shifted to the right. Opening folders etc. is slow and it can take several seconds to recognize a mouse click. All in all, I am afraid to upgrade the OS! I have tried the 13.2 betas too, same bad result. Reverting to 13.1 can take a long time too. I tried to log in at the Discord site to report this situation, but that process was beyond me. I can only hope the Developers get a report from someone else.
Root patches for GPU accel are actually working right for 13.2 RC, but you might have to install the appropriate KDK for 22D49 yourself before patching. I would guess this will be corrected with one of the newer OCLP versions (0.6.0 and upwards).
What you describe is missing GPU acceleration, no big deal and not a problem with neither 13.2 or root patch of 0.5.4n
 
Root patches for GPU accel are actually working right for 13.2 RC, but you might have to install the appropriate KDK for 22D49 yourself before patching. I would guess this will be corrected with one of the newer OCLP versions (0.6.0 and upwards).
What you describe is missing GPU acceleration, no big deal and not a problem with neither 13.2 or root patch of 0.5.4n
Sorry to jump in, but I have a similar system (2014 iMac Retina i7) and was concerned when I read about the issues this poster was having. Are you saying this should work, and it's just an issue installing the GPU patches? Keen to know before I try the update from 13.1

Thanks
 
Root patches for GPU accel are actually working right for 13.2 RC, but you might have to install the appropriate KDK for 22D49 yourself before patching. I would guess this will be corrected with one of the newer OCLP versions (0.6.0 and upwards).
What you describe is missing GPU acceleration, no big deal and not a problem with neither 13.2 or root patch of 0.5.4n
I was about to say the same…
to others with KDK issue, you may need to uninstall the root patch and delete/move/rename the 13.1 KDKs folder before installing the 13.2 KDK.
 
  • Like
Reactions: Larsvonhier
Root patches for GPU accel are actually working right for 13.2 RC, but you might have to install the appropriate KDK for 22D49 yourself before patching. I would guess this will be corrected with one of the newer OCLP versions (0.6.0 and upwards).
What you describe is missing GPU acceleration, no big deal and not a problem with neither 13.2 or root patch of 0.5.4n
Thanks for the info! I have seen the link for the AutoPkg-Assets on the 0.5.3 release page, is that what you mean by "install the appropriate KDK for 22D49"? Or is there another link you can post? I intend to try the update again after the 13.2 version is released. Thanks again.
 
  • Like
Reactions: Larsvonhier
Thanks for the info! I have seen the link for the AutoPkg-Assets on the 0.5.3 release page, is that what you mean by "install the appropriate KDK for 22D49"? Or is there another link you can post? I intend to try the update again after the 13.2 version is released. Thanks again.
KDK = Kernel Debug Kit
They are available at https://developer.apple.com/download/more/ Search for "Kernel Debug Kit"

You need to remove any previous KDKs that got installed by OCLP and install the KDK for your version of macOS instead. This is generally only needed for systems with AMD dGPUs if my knowledge is right. But that's the case for you, so yeah... :) Good luck!
 
How are updates, i.e. 13.0 to 13.1 or 13.1 to 13.2, etc handled with this patcher ? I thought I read on OCLP's website that they take care of it and I presumed that meant our machines will get a notification that an update is available, just like normal. I've got a new MBA and one of our kids is using my old MBA that I used OCLP to get it running Ventura but I don't know if I need to tell her to not update it if it prompts her and so on, so I was wondering what to do.
The question you asked whether you should allow your daughter to update the Ventura installation you had on the old MBA (version? year?). The answer to that is that she can. It is straightforward (she may need to update the OCLP first), but other than having to download the 11 gb version (if the post-install root patch has been done), nothing should go wrong. After the install of whichever version, OCLP will ask to redo the root patch again. I hope this answer is OK.
 
Sorry to jump in, but I have a similar system (2014 iMac Retina i7) and was concerned when I read about the issues this poster was having. Are you saying this should work, and it's just an issue installing the GPU patches? Keen to know before I try the update from 13.1

Thanks
Yes. Should work, no reason why not - if done right... ;-)
 
Long story short, I upgraded my MacBookPro 9,1 and MacPro 5,1 and all went well on MBP, but cMP 5,1 I can only SSH, no video, so stupid me read on _________ that AMD RX 6600 worked natively with OCLP and Ventiura so I rushed and ordered 2 for my MacPro 4,1 and MacPro 5,1 machines. I then found a post that you have to update VBIOS? Or will OCLP take care of all of that? If not, what are good recommendations to get it working? Also, I've read that there are BT issues? What about USB per-se? I upgraded my Wi-Fi with a BCM94360CD which upgraded my stock BT to the built-in on the Wi-Fi adapter. Will my BCM94360CD's BT work out of the box? Any other issues I should be aware of?

Thanks!

Any ideas? With RX580 it upgraded but no video. I could still SSH but didn't have any xcode tools after upgrade so I couldn't try the post-install/patches. I am going to try to install 0.6.0 TUI to see if I can run it after upgrade.

I ordered the AMD RX 6600 (non-XT) to try next.

WiFi / BT upgraded to BCM94360CD - I did see where BT is being wired to another USB controller?
 
Root patches for GPU accel are actually working right for 13.2 RC, but you might have to install the appropriate KDK for 22D49 yourself before patching. I would guess this will be corrected with one of the newer OCLP versions (0.6.0 and upwards).
What you describe is missing GPU acceleration, no big deal and not a problem with neither 13.2 or root patch of 0.5.4n
While I appreciate your help, I have to disagree about this issue not being a big-deal. It is a show stopper. I can't update the iCloud settings, there is a dialog box prompting for agreeing to new conditions, but clicking on that button does nothing. In general, the slow response timing makes using the system for work impossible.
I tried downloading the KDK installer for 13.2 from the developer page, but it runs and errors out.
Deleting the KDKs folder in /Library/Developers doesn't work either as OCLP nightly 6.0 Jan. 20 version downloads a new KDK and then stops during the Post Install patching with an error, shown below.

Process failed with exit code 1
Please report the issue on the Discord server
- An internal error occurred while running the Root Patcher:
[Errno 30] read-only file system: '/var/folders/lc/dbgnkt1j5yz0tsb6p3gzcsjw0000gn/T/tmp5ft9mtbl/KernalDebugKit.pkg'

Now, I am back to my backup Monterey system, running off the small internal 128GB Apple SSD (formerly a part of the stock fusion drive. This system is also very stable at version 12.6.3 21G417 B2. However, I do like using Ventura 13.1 more than Monterey.
In short, for the Ventura system on an external Crucial 512GB MX500 SSD, it's punt and erase time, then reinstall 13.1 which works very well indeed, thanks to the devs at OCLP.
 
3bebdd6bb7cf6d2bf9745390fbdebbeb.jpg

b4c7b40108a670ebbf611785bb3542f9.jpg

May have missed this but for some people on the mid 2014 the news widget works? Yet completely stalls on my other one I know it was a bug in the non - functional list. Confused why one has no problems with it all.
 
You need to delete/rename/move the existing KDKs folder and uninstall the OCLP post-install root patch first, then reboot and reset PRAM, before installing the 13.2 KDK dmg file downloaded from the Apple Developer site.
Thanks, will try that neck week after 13.2 is released. Now I am just back to 13.1, which works very well indeed.
Actually I did delete the KDKs folder prior to try the KDK downloaded pkg, but I didn't uninstall the root patch or do the PRAM reset. Thanks again.
 
Folks,

running my 11.3 MacBook with OCLP since Ventura was released. Some minor issues, nothing important.

Since I updated to OCLP 0.5.3 sleep doesn't work anymore.
Have ran it twice, checked kext - no changes.

Anyone who faces the same situation?

Thanks.

BIM
 
Last edited:
Hello to all,

**2012 iMac 13,2, updated via OTA to 13.2 RC. Used OCLP 0.5.4n and installation proceeded without any problems.
After applying post install patches there did not appear to be any obvious deficits.

**MacBook Pro 5,2, late 2009, C2D, 17 inch, EVO 860 SSD Updated to 13,2 RC. Method: OTA with OCLP 0.5.4n patches.

First login, after update, does require an external keyboard and mouse to be plugged into a USB hub, with the latter connected directly to computer. Without such setup there is no way to type in the password; internal keybaord and trackpad will not function, nor will external keyboard or mouse if plugged directly to computer’s USB ports (originally reported by HVDS). **See post #2959 on page 119.
Once logged-in, and after applying patches, the external USB hub and accessories are no longer necessary; internal keyboard, track-pad and all ports become functional.

For certain older Macs, including mine, a KDK Kit from Apple needs to be installed before final root patching. There are several posts above which provide instructions. No doubt future versions of OCLP will automate both, the KDK-kit download and install process.

Machine runs really well on 13.2 RC; the only casualty of this update is SIRI. While system settings for SIRI function, the application will not launch.

Hope this note is of help,

Thank you to all the great OCLP and non-metal patch developers.

*Update to SIRI issue. I activated "type to SIRI" function (System settings -> accessibility -> SIRI).
Once set, I could type commands to SIRI and application would respond correctly with audio output. I checked the microphone and it is working correctly. Using Keyboard shortcut would bring "type to SIRI" "typing bar" for command input. It seems direct voice activation and keboard shortcut for voice activation are not functioning correctly, rather than application itself.
 
Last edited:
As i read, and asking me in private about some way to become beta tester.
Try to check this out, in béta test 0.7.0, surely a rumor in macrumors or probably a joke.
 

Attachments

  • Capture d’écran 2023-01-21 à 13.52.55.png
    Capture d’écran 2023-01-21 à 13.52.55.png
    41.8 KB · Views: 104
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.