macOS 13 Ventura on Unsupported Macs Thread

[davidlv]

For the world of me, I cannot get OCLP installed onto the EFI of my internal SSD.

I have installed it repeatedly, but the iMac 10,1, will not take it.
I have to boot the machine with the OCLP-USB stick.

Late 2009 iMac 10,1 with SSD

What is the solution, please?

When you tried to install to the EFI partition on the SSD, did you do the following?
1. Copy the OCLP app to the Application folder?
2. Run the OCLP app, and select the "Build and Install Open Core" option?
3. When prompted, did you select the internal SSD disk?
4. After clicking on the internal SSD disk, did you click on the next partition menu choice?
Those last two items are where many people go wrong, only choosing the disk, and forgetting to click on the partition too.

 

[TigerA]

OTA loading (11.4 GB) and preparation of the update went well but the system couldn't restart for the next installation phase. Hang with processes apparently stopped, desktop cleared but keeping background photo.

Also, ordinary shutdown of running system didn't proceed, same type of hang so forced power off.

I am having a similar issue with Big Sur 11.7.7 beta installed via OTA (from 11.7.6) on an iMac10,1 with OCLP_064. The last installation phase did not go smoothly (can't recall the details by now) and the system now can't restart / shutdown / sleep: "hang with desktop cleared but keeping the background photo". I also need to do a "forced power off". But it can still boot up to 11.7.7 without any issue. I am waiting for the public release of 11.7.7 so that I can make an OCLP generated installation USB.

 

[adrianlondon]

Well that was easy. Nice job, OCLP team!

I was using my late-2013 15" Macbook Pro with Ubuntu for a project I was working on. That's now done.

So I downloaded OCLP v0.6.4 and have just installed Ventura. After that was done I ran Migration Assistant to clone my current MBA (ignoring the version mismatch) and then loaded the relevant profile and updated my MBP to the latest dev beta (Ventura 13.4).

All running well after some quick testing. I'm surprised how performant it is; it's hardly slower than my Intel 2020 MBA.

As an aside:

I bought the MBA in 2020 as I smashed the MBP screen by closing it with a pencil inside. D'oh. I used it connected to an HDMI monitor (I opened the casing to disconnect the internal display so the external one becomes the primary display).

I've just enabled filevault and now I use it by booting up (with no monitor connected), waiting around 30 seconds, typing my password, and then just assuming/hoping it boots as I can't see anything. Then i use screen sharing to connect to it. Working well. Of course, I can always connect the monitor to it as before.

 

[RogueB]

Hello to all.

Report on installing Ventura 13.4.beta2 on Mac 13,2 and MacBook Pro 5,2.

iMac 13,2 (late 2012):

Used OTA (Over The Air) method to upgrade from 13.4 beta1 to 13.4 beta2.
After applying OCLP 0.6.4n variants to both Ventura updates, most applications worked as expected, except video streaming; Apple TV would crash when trying to stream content.

Installed OCLP 0.6.5n (dated 4.18.23) onto the disk with Ventura 13.4.beta2 and applied root patches.
On reboot all applications in-my-use were fully functional, including Apple TV streaming service and Drop Box.

There were reports by other posters of various other application (e.g., power point) failing with OS patched by OCLP 0.6.4 and 0.6.4n variants.
___________________

MacBook Pro 5,2 (Mid 2009). (Successful recovery and Ventura 13.4 beta2 installation)

Installed Ventura 13.4 beta1 over 13.3.2 via OTC, and it functioned adequately, but computer would only reboot if key combination was used; using menu selection to restart (or sleep) would not work. Resetting SMC or NVRAM had no effect on that behavior.
Installed Ventura 13.4 beta2 (OTC) over the beta1, but the install failed with black screen on reboot. Power button method was required to shut down the computer. Restarting the computer brought me back to EFI boot picker, but selecting the Ventura icon resulted in same frozen state. Booted into Monterey partition, without issues, and run disk utility on Ventura partition; no file system problems were found. Ventura partition was also available for file access. Copied all “important” files onto Monterey partition, reinstalled OCLP and rebooted to disk picker (option key on reboot), then selected Ventura partition again, but it remained inaccessible. I have a USB thumb drive with Ventura 13.3.1, but it is not possible to downgrade OS without partition erasure. PRAM and SMC resets did not change the outcome. Mounted the (OCLP) EFI boot volume (while in Monterey) and attempted to “refresh” the EFI file via erasure and reinstallation. However, instead of deleting the whole EFI folder I inadvertently erased its contents (i.e, leaving an empty directory). Rebooted, got disk picker, chose partition, but boot stopped (not surprisingly) at appearance of progress bar; that was true of Ventura, Monterey and even Catalina. Reset of NVRAM and SMC had no effect.

Tried to boot viaThumb drive containing “latest” Catalina installer ( Dosdude1’s installer patched), but got message: “disk damaged or files corrupted.” That drive was fully functional in past tests.
An SMC and NVRAM reset resulted in a boot to a white screen with flashing folder (again, not too surprising)

Left with little recourse (for non-data or Monterey loss recovery), I attached an old Firewire 800 HDD with partitions containing Snow Leopard and Maverick (OSs “native” to the CPU); both showed as bootable options in “boot picker”, which replaced the “flashing folder” on the screen. Machine booted into Maverick.
Plugged my least-complicated Thumb drive, (with Catalina installer) into the USB port, lunched Disk Utility and applied “first aid”. The utility did not find any errors, but did something I had not seen using current disk utility; it showed a message that “it made repairs to make drive bootable”. Plugged Catalina-installer thumb drive into USB port, rebooted, and this time Catalina installer showed as viable boot. Reinstalled Catalina onto its partition (dosdude1 patched). Booted into Catalina, downloaded latest OCLP, installed it onto main drive, and booted into Monterey. OCLP patches were applied while in Monterey. Rebooted, erased Ventura partition, then installed Ventura 13.3.1 (via USB thumb drive) on the existing (empty) Ventura partition. Booted into 13.3.1 partition and installed (OTA) Ventura 13.4beta2. Applied patches, and rebooted without any further issues. No files or data were lost on Monterey or Catalina partitions.

All partitions are also fully bootable and without operational issues (other than those related to Non-Metal GPU status when booted in Ventura and Monterey (no direct video streaming or maps functionality)

Ventura 13.4beta2 with OCLP 0.6.5n runs well, and is very responsive on the MacBook Pro 5,2.

Hope above recovery report may be helpful.

Fantastic job by the developers and thread contributors.

 

[TigerA]

For the world of me, I cannot get OCLP installed onto the EFI of my internal SSD.

Check the EFI partition type and size: Try FAT32/DOS, 209MB. If still not good, have a look of the /Library/Audio/Plug-Ins/Components folder: Delete all the files in that folder. If still not working, you will need to reformat the SSD to APFS and reinstall the Ventura ...

 

[RogueB]

MBP5,2: tried to update from 13.4b1 to b2.

OTA loading (11.4 GB) and preparation of the update went well but the system couldn't restart for the next installation phase. Hang with processes apparently stopped, desktop cleared but keeping background photo.
That was the case with OCLP 0.6.4 release as well as with 0.6.5n latest, on internal and external disk.
Also, ordinary shutdown of running system didn't proceed, same type of hang so forced power off.

Didn't really matter as the system remains bootable and running with 13.4b1. I'll probably wait for a 13.4 InstallAsiistant.pkg and install from USB.

Question - I didn't find back where the OTA downloaded Ventura is stored after load/prep. There is only very little under /Library/Updates. If you remember, please let me know so I can delete files and try again.

Hello hvds,

I was able to install Ventura 13.4 bet2 on my MacBook Pro 5,2 (a near twin to yours). Please see post #5124
Hope the process will work for you as well.

 

[Dubman]

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 :

...
Any ideas?

My MacBook Pro 10,1 is running macOS 13.3.1 with Xcode 14.3 using OCLP 0.6.4 as well as 0.6.2, and I'm having the exact same problem. Others have reported the same issue on Apple Developer Forums. Not sure when and how this will be fixed, but with OCLP, I've learned it's best not to be too eager with the OS and Xcode upgrades.

 

[chris1111]

Spare time to update latest beta my MacBookPro-retina-late-2013​

Using OCLP 0.6.5 with OpenCore 0.9.2
No issue update smooth

 

[dictoresno]

the only issue I'm having that still persists is that unlocking my Mac mini 2014 with my Apple Watch won't work however authorizing app installs or admin prompts via apple watch work just fine. anyone else?

I'm on 13.2.1, OCLP 0.6.4.

on my external NVMe drive, I installed Ventura 13.3.1 and it seems to work fine so far. haven't tested the Apple Watch yet.

 

[ChrisOSX]

Any issues with dual monitors?

One persistent issue I've faced since Monterey and now Ventura is when a app or system alert tries to display itself, if I have a second monitor turned on, sometimes it can't figure out which screen to send it to.

I find myself having to click (middle mouse button is Mission Control), drag alert or app to correct screen and proceed as I would. I could also, click window, move to etc. But that doesn't always work either. I usually have to turn off my external monitor, it gathers everything, do what I need to do and power the monitor back on.

Its monotonous to say the least.

Thoughts?

 

[Nebealand]

Добрый день, подскажите, пожалуйста, на настоящике macbook pro 2012 retina opencore начиная с 0,6,2 по 0,6,4 система не запрашивает доступ к контактам, календарям и т.д.

Good afternoon, tell me, please, for real macbook pro 2012 retina opencart starting from 0,6,2 to 0,6,4, the system does not request access to contacts, calendars, etc.

 

[deeveedee]

Any issues with dual monitors?

One persistent issue I've faced since Monterey and now Ventura is when a app or system alert tries to display itself, if I have a second monitor turned on, sometimes it can't figure out which screen to send it to.

I find myself having to click (middle mouse button is Mission Control), drag alert or app to correct screen and proceed as I would. I could also, click window, move to etc. But that doesn't always work either. I usually have to turn off my external monitor, it gathers everything, do what I need to do and power the monitor back on.

Its monotonous to say the least.

Thoughts?

I'm not observing this on my rig (SMBIOS model MBP6,2). Is this for your MBP6,2? Do you mind posting your OC config.plist? An IORegistryExplorer dump (with IORegistryExplorer 2.1 attached) would be very helpful, too.

EDIT: I am patching with OCLP 0.6.4 [RELEASE].

 

[phaser32]

Добрый день, подскажите, пожалуйста, на настоящике macbook pro 2012 retina opencore начиная с 0,6,2 по 0,6,4 система не запрашивает доступ к контактам, календарям и т.д.

Good afternoon, tell me, please, for real macbook pro 2012 retina opencart starting from 0,6,2 to 0,6,4, the system does not request access to contacts, calendars, etc.

I don't understand what you mean if the system requires access to contacts, calendars etc... What do you mean? You decide what to sync your account with. If you are not willing to link your apple account, you can avoid it by skipping the integration step.

 

[shafez]

Добрый день, подскажите, пожалуйста, на настоящике macbook pro 2012 retina opencore начиная с 0,6,2 по 0,6,4 система не запрашивает доступ к контактам, календарям и т.д.

Good afternoon, tell me, please, for real macbook pro 2012 retina opencart starting from 0,6,2 to 0,6,4, the system does not request access to contacts, calendars, etc.

No, Opencore does not require access to contacts or calendar or any personal data.

Нет, Opencore не запрашивает доступ к контактам, календарю или любым личным данным.

 

[Sagitas]

I had a bit of an issue. My SSD in my MacPro has been having issues. I have made a direct clone of the SSD with CCC of the Data partition. Once that was done I then reinstalled Ventura. Before making a copy I rolled back the root patches. After starting up the first time into Ventura I get the notice from Open Core to install the root patches, which I do. It moves through the process and then at the end I get an error:

- Unable to build new kernel cache


Reason for Patch Failure (71):


Error Domain=KMErrorDomain Code=71 "Unable to resolve dependencies: 'com.apple.driver.AppleHIDKeyboardEmbedded' names a dependency on 'com.apple.iokit.IOHIDFamily', which was not found." UserInfo=(NSLocalizedDescription=Unableto resolve dependencies:


'com.apple.driver.AppleHIDKeyboardEmbedded' names a dependency on 'com.apple.iokit.IOHIDFamily', which was not found.) checking collections...


Warning: com.apple.driver.KextExcludeList was not found! updated kernel binaries (macho-o UUID changed from <unknown> to <unknown>)


rebuilding release collections: boot, system rebuilding release collections:


boot kernel collection system kext collection


failed to build release collection:


Unable to resolve dependencies:


'com.apple.driver.AppleHIDKeyboardEmbedded' names a dependency on 'com.apple.iokit.IOHIDFamily', which was not

I've tried rolling back the root patches again and then tried to reapply them. Removing and reapplying them works on the old drive which this drive is a clone of in the data partition. Would rolling back to a previous version of OCLP resolve the issue?

Hi. I’m still curious to see if you found a solution to this issue. I’m having the same problem. I’m trying to clone my ssd (with has OCLP Ventura on my MacBook Pro 2015 11 inch) and I can’t get the clone properly patched as I get this error you’ve mentioned. Thanks for any insights here!

 

[Nebealand]

No, Opencore does not require access to contacts or calendar or any personal data.

Нет, Opencore не запрашивает доступ к контактам, календарю или любым личным данным.

Я мастер объяснять 😀 когда я обновляю OLCP до версии 0,6,4 и в любой системе будет она монтерей или вентура, при установки любой программы работающую с контактами, календарем и т.д. не происходит запрос.

I am a master of explaining 😀 when I update OLCP to version 0,6,4 and in any system it will be Monterey or Ventura, when installing any program that works with contacts, calendar, etc. no request occurs.

 

[shafez]

Я мастер объяснять 😀 когда я обновляю OLCP до версии 0,6,4 и в любой системе будет она монтерей или вентура, при установки любой программы работающую с контактами, календарем и т.д. не происходит запрос.

I am a master of explaining 😀 when I update OLCP to version 0,6,4 and in any system it will be Monterey or Ventura, when installing any program that works with contacts, calendar, etc. no request occurs.

Check below post for instructions.

https://forums.macrumors.com/threads/macos-13-ventura-on-unsupported-macs-thread.2346881/post-32095978

 

[Kirkafur]

Just upgraded Ventura to the latest, and when it booted up the resolution was set too high. I manually applied OCLP’s post-install patches, though did not update to the latest version of OCLP first (it was 0.6.3), as it said there was one available that said something about graphics. After this, when I boot it will prompt me for my password, but about a third of the way through the progress bar it freezes.
I have another volume I can boot from. To repair my main boot drive, though, what’s my best option?
(2014 13” MBP)

 

[coolio2004]

MBP5,2: tried to update from 13.4b1 to b2.

OTA loading (11.4 GB) and preparation of the update went well but the system couldn't restart for the next installation phase. Hang with processes apparently stopped, desktop cleared but keeping background photo.
That was the case with OCLP 0.6.4 release as well as with 0.6.5n latest, on internal and external disk.
Also, ordinary shutdown of running system didn't proceed, same type of hang so forced power off.

Didn't really matter as the system remains bootable and running with 13.4b1. I'll probably wait for a 13.4 InstallAsiistant.pkg and install from USB.

Question - I didn't find back where the OTA downloaded Ventura is stored after load/prep. There is only very little under /Library/Updates. If you remember, please let me know so I can delete files and try again.

I will find 13.4b2 full installer usb within oclp 0.65n. With usb installer you can repair ota upgrade issues.

 

[hvds]

I will find 13.4b2 full installer usb within oclp 0.65n. With usb installer you can repair ota upgrade issues.

Thank you. Just downloading it via gibMacOS, and will use it for my internal SSD.
(The external one is fixed by fresh install from 13.3.1 USB installer, then 13.4b2 OTA.)

 

[hvds]

Hello to all.

Report on installing Ventura 13.4.beta2 on Mac 13,2 and MacBook Pro 5,2.

iMac 13,2 (late 2012):

Used OTA (Over The Air) method to upgrade from 13.4 beta1 to 13.4 beta2.
After applying OCLP 0.6.4n variants to both Ventura updates, most applications worked as expected, except video streaming; Apple TV would crash when trying to stream content.

Installed OCLP 0.6.5n (dated 4.18.23) onto the disk with Ventura 13.4.beta2 and applied root patches.
On reboot all applications in-my-use were fully functional, including Apple TV streaming service and Drop Box.

There were reports by other posters of various other application (e.g., power point) failing with OS patched by OCLP 0.6.4 and 0.6.4n variants.
___________________

MacBook Pro 5,2 (Mid 2009). (Successful recovery and Ventura 13.4 beta2 installation)

Installed Ventura 13.4 beta1 over 13.3.2 via OTC, and it functioned adequately, but computer would only reboot if key combination was used; using menu selection to restart (or sleep) would not work. Resetting SMC or NVRAM had no effect on that behavior.
Installed Ventura 13.4 beta2 (OTC) over the beta1, but the install failed with black screen on reboot. Power button method was required to shut down the computer. Restarting the computer brought me back to EFI boot picker, but selecting the Ventura icon resulted in same frozen state. Booted into Monterey partition, without issues, and run disk utility on Ventura partition; no file system problems were found. Ventura partition was also available for file access. Copied all “important” files onto Monterey partition, reinstalled OCLP and rebooted to disk picker (option key on reboot), then selected Ventura partition again, but it remained inaccessible. I have a USB thumb drive with Ventura 13.3.1, but it is not possible to downgrade OS without partition erasure. PRAM and SMC resets did not change the outcome. Mounted the (OCLP) EFI boot volume (while in Monterey) and attempted to “refresh” the EFI file via erasure and reinstallation. However, instead of deleting the whole EFI folder I inadvertently erased its contents (i.e, leaving an empty directory). Rebooted, got disk picker, chose partition, but boot stopped (not surprisingly) at appearance of progress bar; that was true of Ventura, Monterey and even Catalina. Reset of NVRAM and SMC had no effect.

Tried to boot viaThumb drive containing “latest” Catalina installer ( Dosdude1’s installer patched), but got message: “disk damaged or files corrupted.” That drive was fully functional in past tests.
An SMC and NVRAM reset resulted in a boot to a white screen with flashing folder (again, not too surprising)

Left with little recourse (for non-data or Monterey loss recovery), I attached an old Firewire 800 HDD with partitions containing Snow Leopard and Maverick (OSs “native” to the CPU); both showed as bootable options in “boot picker”, which replaced the “flashing folder” on the screen. Machine booted into Maverick.
Plugged my least-complicated Thumb drive, (with Catalina installer) into the USB port, lunched Disk Utility and applied “first aid”. The utility did not find any errors, but did something I had not seen using current disk utility; it showed a message that “it made repairs to make drive bootable”. Plugged Catalina-installer thumb drive into USB port, rebooted, and this time Catalina installer showed as viable boot. Reinstalled Catalina onto its partition (dosdude1 patched). Booted into Catalina, downloaded latest OCLP, installed it onto main drive, and booted into Monterey. OCLP patches were applied while in Monterey. Rebooted, erased Ventura partition, then installed Ventura 13.3.1 (via USB thumb drive) on the existing (empty) Ventura partition. Booted into 13.3.1 partition and installed (OTA) Ventura 13.4beta2. Applied patches, and rebooted without any further issues. No files or data were lost on Monterey or Catalina partitions.

All partitions are also fully bootable and without operational issues (other than those related to Non-Metal GPU status when booted in Ventura and Monterey (no direct video streaming or maps functionality)

Ventura 13.4beta2 with OCLP 0.6.5n runs well, and is very responsive on the MacBook Pro 5,2.

Hope above recovery report may be helpful.

Fantastic job by the developers and thread contributors.

View attachment 2191397View attachment 2191399

Thank you for the encouragement.

MBP5,2 running well now with 13.4b2 on external SSD.
Using OCLP 0.6.5n latest (last commit "Merge pull request #1058 from TechEnthusiasm/main").

Recovery was easier in my case.
Running from my production MBP16,1 (with native 13.3.1), erased the external SSD to be used for MBP5,2. Then with CCC, populated it with the up-to-date user data etc. from the MBP16,1.
With this SSD plugged into the MBP5,2, installed 13.3.1 using USB installer. Applied 0.6.5n post-install patches (system was unstable without this).
Updated to 13.4b2 OTA which went well now. Applied post-install patches.

Runs quite well, including Safari Version 16.5 (18615.2.5.11.2) which I am using here.

Big thank you to OCLP and non-metal developers indeed!


Added: same good result also on the internal SSD.
Erased it and cloned the data from external SSD to it (CCC).
Installed 13.4b2 on it using „USB“ installer (in fact a 20GB HFS+ partition on the internal SSD)
Applied OCLP 0.6.5n post-install patches.

Forgotten to mention that as always on these machines, running the installer, or Ventura before patches applied, requires external keyboard and mouse connected via USB2 hub.

 

[Kirkafur]

I got it running by booting from different OS and redoing all the OCLP steps.

 

[roysterdoyster]

MBP5,2: tried to update from 13.4b1 to b2.

OTA loading (11.4 GB) and preparation of the update went well but the system couldn't restart for the next installation phase. Hang with processes apparently stopped, desktop cleared but keeping background photo.
That was the case with OCLP 0.6.4 release as well as with 0.6.5n latest, on internal and external disk.
Also, ordinary shutdown of running system didn't proceed, same type of hang so forced power off.

Didn't really matter as the system remains bootable and running with 13.4b1. I'll probably wait for a 13.4 InstallAsiistant.pkg and install from USB.

Question - I didn't find back where the OTA downloaded Ventura is stored after load/prep. There is only very little under /Library/Updates. If you remember, please let me know so I can delete files and try again.

I encountered the exact same problem you described during an OTA update on my MBP4,1.
I ran Daisy Disk for a visual map and found 20GB of "hidden space", with no way to delete that.
I ran Disk Uitilty for diagnostics and found, my entire disk structure altered, which left no other way out than a fresh installation after a disk wipe. I then ran Migration assistant, and everything is back to normal, all issues gone.

 

[Dilli]

@hvds You can go to /private/var/folders/zz and delete the largest size folder or file. This is the update file downloaded OTA. Cheers

 

[davidlv]

@hvds You can go to /private/var/folders/zz and delete the largest size folder or file. This is the update file downloaded OTA. Cheers

Tried that, resulted in a "Permissions error". Tried to set the permissions and can't get access to anything in /private, SIP related? Suggestions?