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.
15inch MacBook Pro 2012 upgrading from Big Sur via USB using the latest OCLP version, install is fine and I can get to the desktop after I install the root patch though and restart the machine I’m pronoted to enter a password to unlock the drive then I get stuck on a progress bar at about 50%, I have gone round in this circle twice now as I can reinstall venturea and get stuck in the same place any ideas ?
first of all, if you don't put punctuation marks you don't understand the logical sense well and the progression of events appears confused…. I think you will solve it by doing a clean installation from zero… in this procedure with oclp you have to anticipate the possibility the failure of a simple upgrade from previous macos, then make backups and if necessary in case of errors reinstall macos directly from zero…
 
  • Like
Reactions: TheStork and makra
Thanks not that I should have to justify myself but I am recovering from a serious accident and have enough trouble trying !

A clean install is always a simple answer, and I wouldn’t be asking a question if I didn’t want to try and save my current install as I said I was upgrading.

I wonder if some one else has had a similar problem to me ?
 
Thanks not that I should have to justify myself but I am recovering from a serious accident and have enough trouble trying !

A clean install is always a simple answer, and I wouldn’t be asking a question if I didn’t want to try and save my current install as I said I was upgrading.

I wonder if some one else has had a similar problem to me ?
Ok sorry… the first time i installed monterey with oclp on macbook pro 2012 13” i had some freezes/stalls that i solved with forced restarts… for my experience with macbook pro 2012 and imac 2011, various clean installs or upgrades i understood that the procedure is very delicate but “powerful” for what it allows to do on “old” Macs… the 2 last upgrades to ventura from monterey on MacBook Pro 9.2 and iMac 12.1 went smoothly but I was ready to start from zero… but I would not recommend, except if you are forced, to do a restore because it is known that errors can continue in the os files… every time I have done a clean install I have reinstalled the apps and copied my personal files as well as were and redone some forgiveness configuration ... often it takes more time but you have the certainty that then everything works correctly at 99.99%
 
Last edited:
every time I have done a clean install I have reinstalled the apps and copied my personal files
Yep.

Always have a backup when mucking around patching unsupported OS.

SOP, really.

With Ventura being .0 release and OCLP for Ventura being beta of sorts, makes a lot of sense to do a fresh start.
 
I'm in a fair amount of trouble here - I installed Ventura 13.0.1 on my late 2015 iMac 17.1 with 1 TB fusion drive, and it was working very well. During setup, I ignored the option to transfer backup files from TM, thinking I could do so later. Later, I attempted to transfer the TM files - about 2.5 TB - but not the system files. Four hours later the transfer was complete, but the Mac "locked up" and refused to boot into Ventura. I then tried rebooting from the OCLP USB stick - unsuccessfully. In summary, I can't boot from either the fusion drive or the USB stick, I can't boot from Recovery, and it looks for all the world that I have a bricked machine. Can anyone offer any help please?
 
Yep.

Always have a backup when mucking around patching unsupported OS.

SOP, really.

With Ventura being .0 release and OCLP for Ventura being beta of sorts, makes a lot of sense to do a fresh start.
Thanks I have backups and still have access to my data on the disk I am upgrading, I have not lost my data ?

Again looking for people with similar issues ?
Have upgrade can boot Ventura, and then fail to boot after root patching …

I am trying to solve the issue I have ….
 
I'm in a fair amount of trouble here - I installed Ventura 13.0.1 on my late 2015 iMac 17.1 with 1 TB fusion drive, and it was working very well. During setup, I ignored the option to transfer backup files from TM, thinking I could do so later. Later, I attempted to transfer the TM files - about 2.5 TB - but not the system files. Four hours later the transfer was complete, but the Mac "locked up" and refused to boot into Ventura. I then tried rebooting from the OCLP USB stick - unsuccessfully. In summary, I can't boot from either the fusion drive or the USB stick, I can't boot from Recovery, and it looks for all the world that I have a bricked machine. Can anyone offer any help please?
Recovery from internet, install original macos and then directly in monterey or Ventura with oclp???
 
Not urgent or important, just as FYI: Safari intermittent graphical issue persists. It vanishes once I toggle or exit full screen mode.
 

Attachments

  • Screenshot 2022-11-30 at 15.47.34.png
    Screenshot 2022-11-30 at 15.47.34.png
    30.9 KB · Views: 85
Hi everybody,
I have an iMac 27" late 2013, with Monterey installed via OCLP. Now I'm trying to upgrade it to Ventura, using OCLP 0.5.2, but the system fails to make the bootable USB drive. With OCLP I downloaded Ventura 13.0.1 imatge disk. But then trying to make the bootable USB drive it gets stuck around 100-200Mb written... and finally fails to make it. I tried OCLP 0.5.1 and also failed. Any ideas what to do?
 
Last edited:
What is next, now, for OCLP 0.5.3+…? Personally, I think that, among other things, also this one should be addressed, in future releases, thus avoiding the need to disable LV (AMFI already doesn’t need to be disabled, anymore), if possible:

Library Validation and AMFI changes

With Ventura, our _cs_require_lv patch broke which we rely on to pass our shim'd binaries as allowable in macOS under their security policy. In addition to our patch breaking, Apple has modified the requirements for disabling AMFI outright.

With Ventura, AMFI can no longer be disabled in Safe Mode, as well when CSR_ALLOW_UNTRUSTED_KEXTS is not toggled (we assume this is related to DriverKit). Thus to disable Library Validation and AMFI in general, you'll need:


  • Bit 0x1 flipped in SIP
  • amfi_get_out_of_my_way=0x1 in boot-args
We will be researching what other patches can be used in the future to alleviate this.

More in general, it would be cool if Ventura could be OCLP’d more or less as Monterey, with the least possible limitations on SIP (enabled as much as possible) and other basic security features - but of course only the core developers will be able to investigate and know if this will even be possible.

Still hoping, anyway, if and when it will be possible, in a more evolved Ventura “2.0” OCLP (sofar, still on Monterey, at this time)… :cool:o_O
 
  • Like
Reactions: macinfo and shafez
I'm in a fair amount of trouble here - I installed Ventura 13.0.1 on my late 2015 iMac 17.1 with 1 TB fusion drive, and it was working very well. During setup, I ignored the option to transfer backup files from TM, thinking I could do so later. Later, I attempted to transfer the TM files - about 2.5 TB - but not the system files. Four hours later the transfer was complete, but the Mac "locked up" and refused to boot into Ventura. I then tried rebooting from the OCLP USB stick - unsuccessfully. In summary, I can't boot from either the fusion drive or the USB stick, I can't boot from Recovery, and it looks for all the world that I have a bricked machine. Can anyone offer any help please?

Big sur usb? What options are you getting when holding alt on boot?
 
Thanks not that I should have to justify myself but I am recovering from a serious accident and have enough trouble trying !

A clean install is always a simple answer, and I wouldn’t be asking a question if I didn’t want to try and save my current install as I said I was upgrading.

I wonder if some one else has had a similar problem to me ?
I'm sorry to hear you're recovering from an injury. I literally just received my mid-2012 MacBook Air Airport/Bluetooth upgrade kit from you. I'm about to install it later tonight, I think.
 
  • Like
Reactions: jrumball
I have a 13,3 (MBP 15inch 2015 touchbar), installed Ventura, used OCLP 0.5.2. Everything works great, even the patches and hibernation and all. But, any time I have to use the file picker, I get the rainbow loading cursor for a few mins and the file picker does not load. For example, if I want to attach a file to an email, I’ll click on the attach button and it’ll give the rainbow cursor for a few mins and then nothing. Same if let’s say I wanted to upload something, or browse for an image to burn using Balena. As soon as I hit browse, spinny rainbow for a few mins and then nothing. Anyone got any suggestions?
 
installed beta Ventura 13.1 beta 4 and is working great for me using oclp 5.2 around a 700mb update from beta 3.
 
Update to Beta 4 no problem except i've download the Kernel debug kit manually....tank's to developers
 
Last edited:
Can somebody help me please? I tried to install the new beta 4 update OTA on my MBP 13.2 (Intel Skylake) and i'm stuck in the booting process. Only the safe boot is working, and I cannot install the post patch. I receive a strange error concernant a com.makemkv.kext.daspi, and a patch failure code 31. Any idea?
 

Attachments

  • Image 2-12-22 à 08.20.JPG
    Image 2-12-22 à 08.20.JPG
    95.1 KB · Views: 70
  • Capture d’écran 2022-12-01 à 21.38.25.PNG
    Capture d’écran 2022-12-01 à 21.38.25.PNG
    82.2 KB · Views: 74
  • Image 2-12-22 à 08.22.jpg
    Image 2-12-22 à 08.22.jpg
    80.7 KB · Views: 71
Last edited:
Can somebody help me please? I tried to install the new beta 4 update OTA on my MBP 13.2 (Intel Skylake) and i'm stuck in the booting process. Only the save boot is working, and I cannot install the post patch. I receive a strange error concernant a com.makemkv.kext.daspi, and a patch failure code 31. Any idea?


Why using oclp 5.3 ? and not 5.2?
 
Recovery from internet, install original macos and then directly in monterey or Ventura with oclp???
Thanks Hyperion (and later Tom1211) - that’s what I did, so next time I rebooted and it locked up, I left the machine running and went to bed. Next morning I discovered that Ventura was up and running, so perhaps I was just a little impatient! Nevertheless your responses May help others. Thanks.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.