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.
Succesfully installed on my main mini L2012 (Ivybridge) external SSD Ventura 13.4 by an USB stick (no OCLP) OCLP 0.6.2 un main internal disk and root patches 0.6.6n.
All works perfectly including Blender, Safari, Photo, Preview, Powerpoint 16.72.
I don't like to change bootloader so every time I close window.
 

Attachments

  • OCLP.jpg
    OCLP.jpg
    28 KB · Views: 81
If I have OPLP 0.6.5 and 13.2.1 Ventura, how do I install 13.4 (B4)? Do I simply download it to my SSD from Mr Macintosh's site then install via? I've only done the installs (all/previous) via USB boot disk but was wondering if I could do it another way on the Beta versions.
 
If I have OPLP 0.6.5 and 13.2.1 Ventura, how do I install 13.4 (B4)? Do I simply download it to my SSD from Mr Macintosh's site then install via? I've only done the installs (all/previous) via USB boot disk but was wondering if I could do it another way on the Beta versions.
I downloaded it from Mr. Macintosh's site on my iMac 15,1 late 2014, put it in the Application folder and ran it from there. some half hour later I was running the latest beta. Had to redo the post install root patches of course.
Used OCLP 0.6.6n.
 
I downloaded it from Mr. Macintosh's site on my iMac 15,1 late 2014, put it in the Application folder and ran it from there. some half hour later I was running the latest beta. Had to redo the post install root patches of course.
Used OCLP 0.6.6n.
Thanks---I'll try this tomorrow...
 
@amaze1499 I interpretted "Revert" to imply a return to a previously installed version of the patches (and not a complete removal of the patches). I will test to see if "Revert" is in fact a complete uninstall. Thank you!

EDIT: @amaze1499 I used "Revert Root Patches" on my Monterey Volume patched with OCLP 0.6.3. I then used OCLP 0.6.5 to apply root patches. As shown by this OCLP 0.6.5 status , "Revert" did not complete remove the OCLP post-install patches (note "Found existing ... overwriting")

View attachment 2196908

however, OCLP 0.6.5 was able to apply post-install patches. I was unable to directly upgrade 0.6.3 patches to 0.6.5 patches, but by "reverting" 0.6.3 root patches first and rebooting, I was then able to apply 0.6.5 root patches.

I had a Monterey test volume that was patched with OCLP 0.6.5n (I think 20 April 2023). I tried to apply OCLP 0.6.5 [RELEASE] Post-Install patches, but patching failed with "... unable to build kernel cache." I tried "Revert Root Patches" and rebooted, but I still could not apply OCLP 0.6.5 post-install patches. Fortunately, installing Monterey to a new APFS Volume and Migrating from the original Monterey volume allowed me to then apply the 0.6.5 [RELEASE] patches to the new Monterey Volume.

EDIT: I have looked for clues in /Library/Logs/DiagnosticReports and in ~/Library/Logs/DiagnosticReports and don't see anything to indicate the cause of this OCLP post-install patching problem.
 
Last edited:
If I have OPLP 0.6.5 and 13.2.1 Ventura, how do I install 13.4 (B4)? Do I simply download it to my SSD from Mr Macintosh's site then install via? I've only done the installs (all/previous) via USB boot disk but was wondering if I could do it another way on the Beta versions.
No offence meant, but why do you want to do this? This thread has a plethora of mishaps and trouble with the betas. You'd be better off being patient until the formal release of Ventura 13.4, when problems and issues that many have had would have been resolved (or should have).
 
My opinion, only go with an OCLP nightly if it might solve a particular problem you're having, and at least two posts on here indicate it will solve that problem you're having. Try to stick with public releases of OCLP. It puts unfair pressure on the devs if you're expecting an undocumented fix for every problem you're having just by grabbing each nightly version. That's not how it works.

At the same time, acting as sacrificial guinea pigs for the dev process may provide useful data for the devs. But please don't complain too loudly when it doesn't fix your problem. Just my experience-backed opinion.
 
Last edited:
upgraded my Late 2014 Mac mini to OCLP 0.6.5, then updated to 13.3.1. then this morning updated to the RSR successfully OTA, reapplied patches and all seems well.

still can't get my Apple Watch to unlock my computer, but I can use to to approve passwords or Apple Pay. is that a known thing or is it working for anyone else. someone mentioned it won't work, but it should if I were on Monterey. is this related to the continuity issue that's been discussed?
 
Last edited:
No offence meant, but why do you want to do this? This thread has a plethora of mishaps and trouble with the betas. You'd be better off being patient until the formal release of Ventura 13.4, when problems and issues that many have had would have been resolved (or should have).
I totally agree.
 
  • Like
Reactions: ofeyvi
As a community update, see signature file for current status of machines I have.
All working for my usual workflow: MS Office suite, Brave, Mail, Zoom, MSTeams, Adobe Acrobat Pro, Music, Spotify...

As before, I've now turned off all updates on my macs for the moment.
Thanks to the DEV Team for the tremendous work done.

So just to confirm, as reported, the 13.3.1(a) RS update doesn't run on the pre-2015 machines.
 
As a community update, see signature file for current status of machines I have.
All working for my usual workflow: MS Office suite, Brave, Mail, Zoom, MSTeams, Adobe Acrobat Pro, Music, Spotify...

As before, I've now turned off all updates on my macs for the moment.
Thanks to the DEV Team for the tremendous work done.

So just to confirm, as reported, the 13.3.1(a) RS update doesn't run on the pre-2015 machines.
I donˋt need Rs. 13.4b4 run fine on all my devices.
 
No offence meant, but why do you want to do this? This thread has a plethora of mishaps and trouble with the betas. You'd be better off being patient until the formal release of Ventura 13.4, when problems and issues that many have had would have been resolved (or should have).
Okay. However, The nerd in me sometimes likes a change and challenge. You’re correct though…
 
  • Like
Reactions: hvds and olad
You have to go the full way from USB installer - look here for details:
Ok so it's a run the OCLP again, that's fine and I'm in no rush to update to Monterey to Ventura aseverything I needed fixed seems to be working again in Monterey thankfully, so I think I can hold out there for some time... you really miss that iMessage integration. Really liking the new more contrasted backer blacks in the dark mode, I wasn't expecting that.
 
I had a Monterey test volume that was patched with OCLP 0.6.5n (I think 20 April 2023). I tried to apply OCLP 0.6.5 [RELEASE] Post-Install patches, but patching failed with "... unable to build kernel cache." I tried "Revert Root Patches" and rebooted, but I still could not apply OCLP 0.6.5 post-install patches.

In the recent past, I have always done quite well with this method for problems of this kind:

I remove the root patches in OpenCore-Patcher (no restart) and quit the program.

  • I start the app Terminal and enter this command:
diskutil list

  • I search the list for the correct name of the EFI with the OpenCore installation.
  • Then I mount the EFI via the terminal with
sudo diskutil mount [the name of the EFI here, for example disk0s1]

and remove the complete OC folder in EFI/EFI/.​

  • Then I restart the current OpenCore-Patcher, install OpenCore (no restart) and patch directly afterwards. Now the reboot takes place.
With this method I had so far no error messages, neither with the OpenCore installation, nor with patching.
 
In the recent past, I have always done quite well with this method for problems of this kind:

I remove the root patches in OpenCore-Patcher (no restart) and quit the program.

  • I start the app Terminal and enter this command:
diskutil list

  • I search the list for the correct name of the EFI with the OpenCore installation.
  • Then I mount the EFI via the terminal with
sudo diskutil mount [the name of the EFI here, for example disk0s1]

and remove the complete OC folder in EFI/EFI/.​

  • Then I restart the current OpenCore-Patcher, install OpenCore (no restart) and patch directly afterwards. Now the reboot takes place.
With this method I had so far no error messages, neither with the OpenCore installation, nor with patching.
Thanks. This was posted by @mwidjaya in the "Monterey on Unsupported Macs" thread.
 
Sigh! Don't I wish I were... You are not alone in wanting the challenge. There must be some nerd in one to be on this forum/thread.
That's how I learned to build/rebuild PCs...then I was able to use it when times were tough a while back for some extra money on the side. But I am new to Macs so it would be best for me to save experimentation for my older MacBook Pro.

Using 0.6.5 right now on 13.2.1 and all is running very well. I have to reboot every 3 weeks because the mouse and keyboard gets a bit wonky. BTW, is there a way to set up a scheduled reboot (weekly) without using terminal?
 
Hello to all,

My MacBook Pro 11,3 is running macOS 13.3 patched with OCLP 0.6.2, and I'm using Xcode 14.3. The issue is I can't debug any app with Xcode and its default debugger LLDB, everytilme I try to debug an app, I get the following :

Code:
Message from debugger: The LLDB RPC server has crashed. You may need to manually terminate your process. The crash log is located in ~/Library/Logs/DiagnosticReports and has a prefix 'lldb-rpc-server'. Please file a bug and attach the most recent crash log.

There seems to be an infinite loop in thread 6:

Code:
Thread 6 Crashed:: <lldb.process.internal-state(pid=30877)>
0   LLDB  0x12030cfb4 ParseTrieEntries(....) + 20
1   LLDB  0x12030d653 ParseTrieEntries(....) + 1715

Any ideas?

I have this too, since updating from 13.2 to 13.3.1, MBP 11,1 (2013), OCLP 0.6.5. Xcode 14.3 was fine on 13.2, so it does seem to be an OS issue. Have you tried reinstalling Xcode?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.