Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 13 Ventura on Unsupported Macs Thread
- Thread starter 0xCUBE
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
First of all a big 'thank you' to the OCLP developers once again who have made running a macOS with an active supply of security fixes possible on 10 year old machines!
Unfortunately I've to report failure to update a MacBook Pro Mid 2012 (MacBookPro9,1) with OCLP 0.5.2 from macOS 13.0.1 to 13.1: I've tried to apply the 11 GB OTA update and while the update itself seems to have been applied successfully, the step of patching the root volume with OCLP 0.5.2 has resulted in a stalled progress bar on reboot.
I've then booted into safe mode (via shift key) and tried to unpatch the root volume via OCLP. This results in a black screen on boot some time around half of the boot screen's progress bar. Only booting into safe mode (via shift key) remains possible. Patching the root volume again now repeatedly fails with
Any help how to resolve the problem is highly appreciated, of course.
Unfortunately I've to report failure to update a MacBook Pro Mid 2012 (MacBookPro9,1) with OCLP 0.5.2 from macOS 13.0.1 to 13.1: I've tried to apply the 11 GB OTA update and while the update itself seems to have been applied successfully, the step of patching the root volume with OCLP 0.5.2 has resulted in a stalled progress bar on reboot.
I've then booted into safe mode (via shift key) and tried to unpatch the root volume via OCLP. This results in a black screen on boot some time around half of the boot screen's progress bar. Only booting into safe mode (via shift key) remains possible. Patching the root volume again now repeatedly fails with
Any help how to resolve the problem is highly appreciated, of course.
Last edited:
Does OCLP now auto-apply root patches? I upgraded from 13.0.1 to 13.1 with no issues and didn't have to re-apply the root patches on my iMac 13,2. Is this a recent thing?
Thank you for your reply.
I also press the option button when rebooting, and choose again the efi of usb stick to boot and then choose disk named "macOS Installer".
But no matter how many times I try reboot this method, the same error occurs and I can't proceed from there.
(^^
Did you use USB flash drive to update? I did a clean install of 13.0 with USB flash drive and no post install patch needed.
Hello,
my MacBook Pro 2014 does not officially support latest macOS Ventura.
I know OpenCore Legacy Patcher allows to install Ventura onb older macs. My question is simple, has anyone installed Ventura on a 20114 MacBook Pro?
How are the performances, is it usable or better to stay with an older macOS?
Thanks for helping.
my MacBook Pro 2014 does not officially support latest macOS Ventura.
I know OpenCore Legacy Patcher allows to install Ventura onb older macs. My question is simple, has anyone installed Ventura on a 20114 MacBook Pro?
How are the performances, is it usable or better to stay with an older macOS?
Thanks for helping.
Old kexts not compatible. Need to remove them from /Library/Extensions. Boot safe mode. Remove all except these 3. Apply root patch, reboot.
Hi, I got a free 2012 MacBook Pro Retina (10,1) with Catalina 10.15.7 from my friend today.
I know that MacOS Ventura can be install on my 2012 MBP with OCLP 0.5.2.
I want to know if I can update from Catalina to Ventura directly without going through Big Sur and Monterey on this MBP.
I know that MacOS Ventura can be install on my 2012 MBP with OCLP 0.5.2.
I want to know if I can update from Catalina to Ventura directly without going through Big Sur and Monterey on this MBP.
I could install it quite easily on my MBP 13.2, I just had to reinstall the postinstall patches.
But I couldn't install it on my iMac 13.2, and I got this strange error message : check your internet connection, which is very good by the way...
Attachments
Same story.
P.S.: why won't you add your configs to a signature?
This type of verification is the standard for Ventura and part of the "onion" style security features of macOS. In Monterey, the extended attribute which forces such verification is cleared after the first run. This intentionally does not happen in Ventura.
With an unsealed system because of the root patches installed by OCLP and a lowered SIP, I don't think preventing that verification is a good idea. But, this is my opinion.
As I said - boot loop. I couldn't boot Ventura 13.2 Beta1 Volume. I could repair with an USB installer 13.2 beta1. So don't use the small secure update.
Attachments
I've caught it about the loop. I just wanna know have you got some message of error (see vendini post above) or update had installed successfully?
Maybe start again from scratch and with 13.0.1?Thank you for your reply.
I also press the option button when rebooting, and choose again the efi of usb stick to boot and then choose disk named "macOS Installer".
But no matter how many times I try reboot this method, the same error occurs and I can't proceed from there.
(^^
Installation went fine in verbose mode. But boot sequence went in a loop. I couldnˋt see an error within the loop.(verbose mode)
I could repair the volume with an USB Full installer Ventura 13.2 Beta 1 on this volume.
Congratulations, the rMBP10,1 is a fine machine. Mine is working perfectly with Ventura 13.1 + OCLP 0.5.2
You ask if you can jump directly from Catalina 10.15.7 to Ventura. There are a few things to consider.
1. It's good that your machine is on 10.15.7 because your firmware is probably up to date, you should be at 429.0.0.0.0. You can check this using SilentKnight, or go into About This Mac > System Report > Hardware.
2. Personally, my strategy is to not 'jump over' a release. If I do, I'll only jump over a dot release, not to a whole major release. The one time I did jump to a new major release I missed a firmware update and had to backtrack.
3. Keep it simple. The OCLP developers can't test every possible permutation. We know it works upgrading progressively, and so that's what I do.
4. If you do decide to attempt installing Ventura over the top of Catalina, please post your results here so we can all learn something. But, as I mentioned, personally I'd get Big Sur going smoothly with OCLP 0.5.2, then Monterey, then Ventura.
5. The rMBP10,1 requires the OCLP post install root patches.
6. Consider doing a clean install; it's a new (to you) machine and you would benefit from starting with a clean slate.
7. I know it's a lot of reading but dive into the OCLP documentation, and the unsupported Mac threads on here.
i am sure. updated to 22D5027d almost immediately and have had no issues.
strange that i could connect to the shares and ssh. rebooted from cli with install usb for 5027d, went thru the install and back in system. there was a welcome "windowserver issue" notification.
closed it and moved on.
My MBP11,4 (spoofed to 14,3 in order to upgrade to Ventura, as recommended by OCLP 0.5.2) works perfectly well, except SilentKnight shows the EFI version as 9999.999.999.999.999, and - reportedly - up to date. I went the route of installing Big Sur on an external Apple Drive and doing an update; so the EFI on that drive reports 476.0.0.0.0. However, when I re-boot from the internal disk which has been modified by OCLP, and all patches done, the EFI is reported as the 9999.... The machine is working well - everything seems OK except the OS update file is not the expected 2.5 gb (or thereabouts), but 11.4 gb. Should I leave well alone, and ignore the weird EFI firmware number or...? The first picture is from Silent Knight on the external SSD Big Sur, and the second from the internal SSD. Suggestions/opinions will be welcome.
