OK! I did it. Leave it on at night (about 8 hours) and the same result as before: it hangs exactly at the same point as before, still with the caps lock LED off. The USB HDD with the installation was not spinning anymore.I hear you. If you're not certain it is still chugging away, bite the bullet and start again. What have you go to lose? Another 4 hours? Take the plunge
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
Sorry for very stupid question but how does one roll-back after installing Ventura 13.3 beta4 and then running OCLP which then doesn't work and just gives rubbish on the screen on boot up?
Safe boot into macOs (Hold shift right instantly after starting up), then run OCLP and revert changes.
It will run without patches but there is no hardware acceleration.
Thanks Justperry, but that maybe supposes that the installation is on the native SSD, I have installed on an external SSD so as not to break my Macbook. Does your advice hold water for external disks as well?
It is not a matter of "holding water" as that advice leads to a system without graphics acceleration, and which is not even barely usable. The whole point of installing OCLP is to achieve a system "just like before" when the Mac concerned was not on the disabled list. Depending on your intent, it might be best to wipe that external disk and try to install 13.6.1, or even Monterey/Big Sur, using 0.6.1.
Developers do not want to give a link to the nighties. Please delete.
@coolio2004 - the page concerned says:
"For developers wishing to validate mainline changes, you may use these nightly links:"
Warning: These binaries should not be used without first consulting the CHANGELOG. Do not distribute these links in forums, instead direct to this file."
"Direct to this file" means posting links to the change log is OK. The developers are concerned that people will try the nightly version, and after getting in trouble, ask for support, which of course would put an undue load on their time.
So if you read the change log, and still decide to use the nightly, don't complain if things don't work, and just go back to the official release (0.6.1 at this time). The nightly version works for many, but there is still some problematic hardware that will require some time and effort to assure good results. Patience is required is those cases.
I actually had, at one time, a computer that was one of those problematic machines. In order to ensure that it was still usable in this modern day and age, it was necessary to install Big Sur, rather than Ventura, on that machine. It ran OK on that OS. I have since given that computer away. I cannot understand why people insist on running the 13.3 betas. The 13.2.1 version of Ventura runs great on my two computers, and many more too, all thanks to the devs of OCLP!
Last edited:
It's not as bad as you say (in my opinion), it is useable to some extent, it runs fine on my Mac Mini, slower...yes and some bugs, otherwise it isn't that bad.
13.6.1...🤔...Time Machine
Apple Seeds macOS Ventura 13.3 RC (22E252) to Developers
Last edited:
Using OCLP 0.6.1, I've successfully installed macOS Ventura 13.2.1 on my mid-2012 MacBook Pro (9,1), and Windows 10 using BootCamp Assistant. And to date, I'm delighted with the outcome and the lack of issues. But I'm in search of "safety nets" for both my Mac and Windows partitions. Specifically, what can and for that matter can't be achieved using MacOS Time Machine? I don't expect to be able to do a full system restore from the recovery environment. Or if Time Machine just isn't viable, is Carbon Copy Cloner a potential option?
And, with regard to my BootCamp partition, does anyone know of any feasible disk imaging options? I have a current license for WinClone, but I've raised the issue with them, and their response was that under OCLP, WinClone can back up the BootCamp partition, users are having issues with restoring. I don't know what the issues are, and I don't know whether these users were trying to restore UEFI or legacy Windows.
For the record, the Boot Camp partition on my vintage Mac is legacy MBR, using a hybridized GPT. Would a Windows imaging utility like Acronis or Macrium be able to back up the partition and restore it while running from a Windows PE bootable USB?
Thanks for looking
And, with regard to my BootCamp partition, does anyone know of any feasible disk imaging options? I have a current license for WinClone, but I've raised the issue with them, and their response was that under OCLP, WinClone can back up the BootCamp partition, users are having issues with restoring. I don't know what the issues are, and I don't know whether these users were trying to restore UEFI or legacy Windows.
For the record, the Boot Camp partition on my vintage Mac is legacy MBR, using a hybridized GPT. Would a Windows imaging utility like Acronis or Macrium be able to back up the partition and restore it while running from a Windows PE bootable USB?
Thanks for looking
of course, but the point of running it from source is so you don't have to dl a new binary (currently 650 MB) everytime a change has been pushed. You can just do a git pull, dl whatever changes were made, often small code adjustments, and run it in python. Much more convenient when a lot of changes are being made. OCLP has been updated 5-6 times in the last few days.
Macpro5,1 Ventura 13.2.1 with latest night build OCLP v0.6.2N. NVidia GT640 rom flashed for visible boot screen. The install was Tuff several freezes and restarts eventually completed the install. Only issue is every other boot in verbose mode just freezes at a certain point and all text look broken up maybe the equivalent of the prohibitory symbol non verbose boot not sure? Any clues what might be causing this maybe BlueTooth? BT is working fine but remember reading something about random kernel panics with native BT?
Hi... I hope everyones having a great day. I encountered an issue recently with my mid-2011 iMac with k3100m GPU running latest stable ventura on OCLP 0.6.1. The issue is that when i try connecting my airpods pro 2, all other bluetooth connected device/devices are disconnected. Then the airpods pro 2 will connect for a while then keeps disconnecting. I have stock BT/Wifi but Im not sure if thats the cause. This is the only reason why I mostly use my M1 MBA instead of this iMac. I hope someone could point me to the right direction. TIA!
Ventura RC 13.3 2015 13" MBP OCLP 0.62n smooth buttery update.
An important cautionary tip before install macOS 13.3!
If our unsupported Macs work fine with Ventura 13.2.1 and OCLP, before installing Ventura 13.3 I suggest everyone read what happened to Josh Hill, CEO of the famous “Koingo Software, Inc.” who suffered extremely catastrophic data loss a due to Ventura 13.3 Beta, using Foto.app and even using a supported Mac.
https://mjtsai.com/blog/2023/03/20/photos-data-loss-with-macos-13-3-beta/
So Photos.app deleted years of work and synced the deletion with iCloud backup too.
As now been advisable with the new Apple systems (obviously this is a my personal opinion) in my opinion it is always better to wait for version .1 of major releases (in this case 13.3.1).
For some time, in fact, the “x.x.1” suffix has proven to be the number that represents the truly stable version and which, therefore, is no longer the x.x.0
After all, what's the hurry?...
If our unsupported Macs work fine with Ventura 13.2.1 and OCLP, before installing Ventura 13.3 I suggest everyone read what happened to Josh Hill, CEO of the famous “Koingo Software, Inc.” who suffered extremely catastrophic data loss a due to Ventura 13.3 Beta, using Foto.app and even using a supported Mac.
https://mjtsai.com/blog/2023/03/20/photos-data-loss-with-macos-13-3-beta/
So Photos.app deleted years of work and synced the deletion with iCloud backup too.
As now been advisable with the new Apple systems (obviously this is a my personal opinion) in my opinion it is always better to wait for version .1 of major releases (in this case 13.3.1).
For some time, in fact, the “x.x.1” suffix has proven to be the number that represents the truly stable version and which, therefore, is no longer the x.x.0
After all, what's the hurry?...
Last edited:
Thank you OKonnel;
Yep, rule number one is never to put beta OS software on a production/main Mac.
After both MacOS 13.3 GM and the latest OCLP patcher are released to the public, then I'll update my unsupported Macs.
Yep, rule number one is never to put beta OS software on a production/main Mac.
After both MacOS 13.3 GM and the latest OCLP patcher are released to the public, then I'll update my unsupported Macs.
Read back through the posts here 13.3 is not supported in betas or RC should stick to 13.2.1 this has been mentioned many times you could try safe mode to unpatch system if you have data you need .
Also: can’t install 13.2.1 due to downgrade limit.
Attachments
Yes got a backup on 13.2.1 ? wipe the drive and start again or wait it out and hope for a patch could install 13.2.1 on a separate partition.
I’m hoping with the security updates option in Ventura separately from full installers you might still get security updates on 13.2.1 anyway which might work ? This happened before on a Big Sur beta update I think where it deleted random photos from the library so not the first time it’s happened if I remember rightly .
I downloaded the OCL 0.6.2 Nightly build, reinstalled OpenCore and post installed the Root Patch on my MacBookPro13,3 (late 2016 MacBook Pro 15") with macOS Ventura 13.2.1. Unfortunately I still can't play HEVC (x265) encoded videos (like these ones on a sample page https://x265.com/hevc-video-files/ ). The QuickTime Player hangs and has to be Forced Quit. VLC player takes a very long time to start playing using, I think, software based rendering of HEVC files. Also, using (copy right protected) streaming video services hangs/crashes the computer. x264 videos play without problems in Quicktime and VLC. So, this means that Hardware decoding/encoding of HEVC files (including all videos/photos shot on iPhones) is still not supported by the drivers in 0.6.2. Hardware decoding/encoding of x264 works. Unfortunately this means I (and many others I think) still can't switch from Monterey to Ventura yet. Hopefully the mighty developers of OCL will find a solution for this annoying and quite serious driver problem.
P.S. Would be nice if other forum members could test the same sample page for trying to play HEVC videos with their newest installs.
P.S. Would be nice if other forum members could test the same sample page for trying to play HEVC videos with their newest installs.
