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.
When you have the bootable installer complete - Launch OCLP app. Click Build and Install OpenCore to that external drive. If you have multiple volumes on that external, OCLP will show only the external device, and not each individual volume that you might have. If you have only one external drive, just choose that one. (if you have multiple external storage devices, you want to make sure that you add OCLP to only that drive, the one with the partition that you want to use for a bootable installer.
And, then you need to remember to hold Option when you boot to that installer, choosing the EFI partition first, then press return to load that EFI, and then choose your installer partition to boot to your installer.
It will be simple, after you do that a time or two.
 
  • Like
Reactions: RK78
When you have the bootable installer complete - Launch OCLP app. Click Build and Install OpenCore to that external drive. If you have multiple volumes on that external, OCLP will show only the external device, and not each individual volume that you might have. If you have only one external drive, just choose that one. (if you have multiple external storage devices, you want to make sure that you add OCLP to only that drive, the one with the partition that you want to use for a bootable installer.
And, then you need to remember to hold Option when you boot to that installer, choosing the EFI partition first, then press return to load that EFI, and then choose your installer partition to boot to your installer.
It will be simple, after you do that a time or two.
It will be simple, after you do that a time or two. Hope it won't be too many times ;)

Many thanks for your invaluable help, a true godsend!
 
Try the Safe Boot method? 😎
Thanks, Safe Boot helped me get back into the system a couple of times, but I haven't been able to migrate my Monterey account yet. I am trying now with a temporary admin user to transfer everything except the system settings. I have root patched the Ventura installation as well. Hopefully things will go through this time.
 
  • Like
Reactions: K two
Thanks, Safe Boot helped me get back into the system a couple of times, but I haven't been able to migrate my Monterey account yet. I am trying now with a temporary admin user to transfer everything except the system settings. I have root patched the Ventura installation as well. Hopefully things will go through this time.
Not sure I completely understand what you're doing, but be aware that you can't use Migrate Assistant to a volume that has already been patched with OCLP (you can migrate from a patched volume, but you can't migrate to a patched volume).

Use OCLP to revert root patches on your new volume, migrate to the new volume and then apply OCLP post-install root patches after migration is complete.
 
  • Like
Reactions: K two
Not sure I completely understand what you're doing, but be aware that you can't use Migrate Assistant to a volume that has already been patched with OCLP (you can migrate from a patched volume, but you can't migrate to a patched volume).

Use OCLP to revert root patches on your new volume, migrate to the new volume and then apply OCLP post-install root patches after migration is complete.
Thanks, that may well be it. Migration Assistant got stuck again, so I reverted the root patches and am going to have another try now.

Edit: of course removing the root patches disables the system, so I will try an alternate route by installing Monterey on the new disk, migrating my old installation there, and upgrading that one to Ventura with OCLP.
 
Last edited:
A question: For OCLP purposes, is an i7 2013 MacBook Air the same as an i5 2013 MBA? Oddly enough I have one of each, and I'm wondering if I can use the same USB installer build for both.
 
You can always perform the migration as the last step of a new macOS install. See this.
Thanks. That was more or less what I originally did (minus the creation of a new volume, as my original install is on my old SSD and I am trying to do the upgrade on a fresh new SSD). Initially, I successfully installed Ventura on the new SSD with OCLP. But migrating my data to that volume failed, as the system would hang towards the end. Your previous post reminded me that I should not try to restore Time Machine to a patched volume, so I wiped the SSD and installed Monterey from scratch. However, now migrating my data from the original SSD hung the system after a while. I cancelled the migration, but was not able to boot the new Monterey install after that, so I have started from scratch again. I may just need to give up on my old install, which I have on the other boot disk anyway and which still works.
 
A question: For OCLP purposes, is an i7 2013 MacBook Air the same as an i5 2013 MBA? Oddly enough I have one of each, and I'm wondering if I can use the same USB installer build for both.
Are you asking whether you can use the same Open Core EFI for both? If so, OCLP generates the OC EFI based on the detected SMBIOS model (or based on the target model that you manually set in OCLP > Settings). If both your Macs are the same SMBIOS model, then the OC EFI for both is the same.

The "USB installer build" (macOS installer) is the same for both.
 
Are you asking whether you can use the same Open Core EFI for both? If so, OCLP generates the OC EFI based on the detected SMBIOS model (or based on the target model that you manually set in OCLP > Settings). If both your Macs are the same SMBIOS model, then the OC EFI for both is the same.

The "USB installer build" (macOS installer) is the same for both.
I've never heard the phrase "SMBIOS model" but suspect you're referring to what I think of as the Apple comma notation for models. In this case both MBAs are 6,2, so no worries there.

It was my impression, as someone new to OCLP, that I'd need to make a fresh USB installer for every (model dissimilar) machine, since the OCLP app seemed to customize its build based on the host machine. If I'm understanding you correctly I won't need to do that, which is good to know.
 
I've never heard the phrase "SMBIOS model" but suspect you're referring to what I think of as the Apple comma notation for models. In this case both MBAs are 6,2, so no worries there.

It was my impression, as someone new to OCLP, that I'd need to make a fresh USB installer for every (model dissimilar) machine, since the OCLP app seemed to customize its build based on the host machine. If I'm understanding you correctly I won't need to do that, which is good to know.
You are misunderstanding the role of OCLP in this process. You only ever need to make 1 installer for as many macs as you wish to install that particular version of macOS onto. OCLP goes on a separate partition of the actual USB installer and will need to be updated (and installed to the EFI partition) in order to load the macOS present on the rest of the installer drive to your specific mac computer at the time of installation. Once macOS is installed, you can run OCLP and put the files needed to boot successfull onto the internal drive of the mac itself, then you will never need the installer USB to boot that particular mac computer up again, it can boot standalone from that point on. You may then run OCLP for a different mac computer, install it to the USB EFI folder, and use that same installer USB to put macOS on the mac computer that you just created an OCLP config file for.

OCLP is simply a loader for a full, unmodified macOS Installer USB. You can use the installer USB to install to a supported Mac, bypassing OCLP completely, or use OCLP to allow you to install that same macOS to a natively unsupported mac.
 
Aaaaand I've decided to give that double APFS volume idea a shot! A slightly smaller volume with a Monterey install (the highest this MacBookPro11,4 officially supports) and a bigger one I will install Ventura on. I even downloaded OCLP 1.1.0 just to be safe, and don't plan to update it to 1.2.1 at all.
NOOOOOO! IIIII TRIIIIIIED 1.1.0, and it STILL broke and tried to upgrade to Sonoma without my consistent! What happens is that when booting it into Ventura, the graphics act as if the root patches haven't been installed, so I have to re-installed. This time, I tried reverting the root patches and re-installing them. But when rebooting, the loading bar moved back to the down and froze! Meaning OCLP installed a SONOMA setup!
1701542807976.jpeg

Fortunately since I have a Monterey APFS boot volume, at least I can still use it without having to re-install EVERYTHING. But I think I'm through with trying to use Ventura on this MacBookPro11,4. I might just leave it on Monterey. Besides, I've already switched to using my M1 MacBook Air at my workplace, until we can get a late 2010s MacBook Pro for me to use there.
 
When you first boot to the new (Ventura) system - before doing any setup with OCLP, (first step) go to System Settings, then General, then Software Update. Click on the settings for Automatic Updates, and make sure to turn OFF: Download Updates, Install macOS Updates, and Install Application Updates from the App Store.
That will take care of your concerns about your Mac downloading/installing Sonoma, unless you choose to do that manually...
 
I have installed Ventura on a 2012 MacBook Pro 15, and the import of scans/photos crashes the Pages/Notes always. Do you have any problems with this feature ? Any idea if it works in Ventura on this old machine ? Perhaps to downgrade to Monterey or Catalina to have this feature again ?
 
Just to update on my own situation: I have Ventura 13.6.1 running smoothly now on my Macbook Pro 11,5. To preserve my data, I installed Monterey on a fresh disk, transferred everything using Migration Assistant, and then upgraded to Ventura with OCLP. There were some issues with the Migration Assistant, also transferring my data between Monterey installs, but that probably has something to do with it going back all the way to a Snow Leopard install a few MBPs and startup disks ago. At least it's nice I can finally change my iCloud settings to advanced data protection.
 
  • Like
Reactions: deeveedee and paalb
NOOOOOO! IIIII TRIIIIIIED 1.1.0, and it STILL broke and tried to upgrade to Sonoma without my consistent! What happens is that when booting it into Ventura, the graphics act as if the root patches haven't been installed, so I have to re-installed. This time, I tried reverting the root patches and re-installing them. But when rebooting, the loading bar moved back to the down and froze! Meaning OCLP installed a SONOMA setup!
View attachment 2320183
Fortunately since I have a Monterey APFS boot volume, at least I can still use it without having to re-install EVERYTHING. But I think I'm through with trying to use Ventura on this MacBookPro11,4. I might just leave it on Monterey. Besides, I've already switched to using my M1 MacBook Air at my workplace, until we can get a late 2010s MacBook Pro for me to use there.
I have the Macbook Pro 11,4 and 14.1 was fine but 14.1.1 I had to enter safe mode and reinstall root patches and all has been very stable. However, 1.3.0 (when it comes out) should fix this problem.
 
I have installed Ventura on a 2012 MacBook Pro 15, and the import of scans/photos crashes the Pages/Notes always. Do you have any problems with this feature ? Any idea if it works in Ventura on this old machine ? Perhaps to downgrade to Monterey or Catalina to have this feature again ?
This problem has existed for quite some time. Fingers crossed that it will be fixed, but it’s been like a year now of people reporting this problem, so signs point to that for HD4000 Macs and such, we just have to live with it….. The problem you mention does not exist on Monterey for that machine.

Still pretty amazing to be using Ventura, Sonoma, etc. on 2012 Macs even if there are a few quirks…
 
Your ability to upgrade will probably depend on your graphics and you will need to upgrade OCLP if plan to install Sonoma.

Just to check this too: I see users update their OCLP to 1.2.1 when they're even still on Monterey / Ventura. I suppose staying on OCLP 0.6.8 is still valid atm? Thanks
 
it’s still valid
You can check the change log to see if some of your specific issues has been fixed.
But the last versions don’t change a lot for Ventura it’s more focused on Sonoma support .
 
  • Like
Reactions: m4v3r1ck
That's likely what happened in my case. I had OCLP 1.1.0., but then it apparently updated itself to 1.2.1. Maybe once 1.3.0 is out I'll try a Ventura install again, like @mikelets456 mentioned.
I have read where a few people were on one version of Mac-OS and it updated to another on its own or accidentally. Mine keeps reminding me to update to 14.1.2 even though I have everything in updates set to "off". If it updates while on 1.2.1 and not 1.3.0 it's fogging to be a pain getting it to boot. I prefer to keep OCLP updated in case this updates without my approval.
 
View attachment 2149437

My 12 years old MacPRO 4.1-5.1 with AMD XFX Radeon RX 580 8GB has also installed very smoothly in about an hour Ventura 13.2 using OCLP 0.6.2.

It seems to works as fluently as Monterey but boot process is faster.
My Bluetooth BCM94360CD AirPort Express is not working but wifi is ok. I will study the USB 2.0 hub procedure but it seems difficult in my hands.

Thank you so much to all the people here and specially all the amazing OCLP team.
Hi, I'm taking advantage of this fantastic forum to try to solve a problem, I thank in advance everyone who will try to help me.
I purchased a 2009 MacPro 4.1>5.1
240Gb SSD on PCI card (first slot from top 4x)
4 TB of HHD
24 GB of RAM
OCLP 1.2.1 and Ventura 13.6.1
The video card is the original one, the NVIDIA GeForce GT 120 (second slot from the top 4x)
Apart from the rear speaker output, everything works fine, including the USB 3.0 hub (in the last slot at the bottom).
I tried to install a Spphire RX580 8Gb (first slot from the bottom 16x) with the following results:
1) both cards, with only the nvidia connected to the monitor with the Apple logo and the loading bar always stopped at the beginning
2) both cards connected to the monitor nothing
3) only the RX580: 2 startup attempts and finally a message appears on the monitor saying that Ventura must be reinstalled.

How can I solve it? Is there a way to configure OCLP? Do you need to downgrade to HighSierra, install the RX and then (possibly) do an Upgrade again?
 

Attachments

  • Screenshot 2023-12-05 alle 19.30.45.png
    Screenshot 2023-12-05 alle 19.30.45.png
    49.8 KB · Views: 49
  • Screenshot 2023-12-03 alle 17.31.37.png
    Screenshot 2023-12-03 alle 17.31.37.png
    64.3 KB · Views: 50
  • Wow
Reactions: K two
I have read where a few people were on one version of Mac-OS and it updated to another on its own or accidentally. Mine keeps reminding me to update to 14.1.2 even though I have everything in updates set to "off". If it updates while on 1.2.1 and not 1.3.0 it's fogging to be a pain getting it to boot. I prefer to keep OCLP updated in case this updates without my approval.

No issues at all with (non-consented) auto-updates here, macOS 14.x.x. is presenting itself in the update tab of my two macOS SSD's. I have a dual macOS 12.7.1 / macOS 13.6.1 SSD's install, waiting for any dot-dot updates to come.

OCLP is notifying in both macOS versions about the later OCLP 1.x.x releases, but I ignore these for now. They both work good, but I need switching for some applications.
 
  • Like
Reactions: mikelets456
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.