macOS 13 Ventura on Unsupported Macs Thread

[K two]

macOS 13.6.5 RC installed atop 13.6.4 via USB, OCLP v.1.4.0n. Runs better than expected, didn't have to install the root-patch! Behaves like a supported Mac. YMMV
Important edit! Upon acquiring the Install Assistant from the Discord OCLP Paradise updates, when building the macOS 13.6.5RC installer USB w/OCLP v.1.4.0n, OCLP mis-identified the OS version as macOS 13.6.2, a Apple Silicon ONLY version of macOS. Yet, proceeding to build the USB yielded a perfectly functional macOS 13.6.5RC build 22G619 installer. So, this may be a bug in the Create macOS Installer function of OCLP v.1.4.0n? In case anyone else may be deterred by this in-process mis-identification bug.

 

[jrumball]

See this SSD guide which indicates problems with hackintoshes booting with Open Core and Hynix P31. The same issues would likely apply to your real Mac. After this thread was created, others reported that Hynix released firmware for the P31 that fixed the problem. You may need to boot Windows on your P31 (or install the NVMe SSD in a system running Windows) to check the firmware version and update if necessary.

EDIT: See this.

I have a P31 Gold which seems to not have the same issues according to recent reports and the addendum to the bottom of the first post here and is actually recommended because of its low power draw.

Upgrading 2013-2015 Macbook Pro SSD to M.2 NVMe

This thread is about upgrading MacBook Airs & Macbook Pros (2013-2015) with new high speed and/or high capacity NVMe SSDs. This thread was one of the first to talk about MacBook Pro NVMe SSD upgrades on Macrumors, and was started by user "maxthackray", which we can thank and give tribute for...

forums.macrumors.com

 

[deeveedee]

I have a P31 Gold which seems to not have the same issues according to recent reports...

Exactly. The P31 works with a Hynix firmware update as both of our posts indicated. If your P31 works, then its firmware is up-to-date.

 

[jrumball]

Exactly. The P31 works with a Hynix firmware update as both of our posts indicated. If your P31 works, then its firmware is up-to-date.

Sorry I have a P31 Gold which is different from a P31 ? I would assume the firmware is up to date as it was purchased from Amazon which has a high throughput of cards the reports are from 2021 of the firmware issues not letting the machine even recognise the SSD which mine does.

i think the issue is actually OCLP related I deleted a number of windowserver preference files and also set the feature unlock to disabled and rebuilt OCLP I then re enabled feature unlock and rebuilt it this seems to have solved the issues I’m now 24hrs without a crash.

interestingly the last app I was having issues with copy and paste was notes and this resolved itself after a couple of crashes I was presented with the upgrade notes/new features splash screen after seeing this there has been no more issues.

i wonder if there were a bunch of background tasks that were being crunched through or left over cache files from copy paste etc that were causing issues that were eventually deleted…

 

[deeveedee]

@jrumball Maybe your issue is different. I only posted what I knew to be a potential issue with Hynix P31 NVMe SSD. If that doesn't apply to you, hopefully it helps others with that SSD.

 

[dymac]

Can't seem find any answers to this.

With OpenCore patcher can an existing boot drive with Ventura that is running on a supported Mac be patched to run on a unsuported Mac? It would be one to keep all the apps and setting as Migration Assistant seem to fail making a clean install on unsupported Macs unbootable.

 

[K two]

Can't seem find any answers to this.

With OpenCore patcher can an existing boot drive with Ventura that is running on a supported Mac be patched to run on a unsuported Mac? It would be one to keep all the apps and setting as Migration Assistant seem to fail making a clean install on unsupported Macs unbootable.

With clean installs, Migratiom Assistant has always worked as intended whether the Migrated source is from a supported or unsupported Mac.

 

[dymac]

Opencore and Ventura on a MP5.1 with multiple boot drives was a no go for me. As soon as I went back to one of the other boot drives the Ventura drive would no longer mount and I could not boot from it. I wasted I whole day trying to see if this was a workable solution for me. Probably would be fine for a single boot drive machine though. If I could have found a way to migrate the apps and setting from an old volume that may have been usable. So in the end after all this trouble I will be better off just buying a new Mac.

 

[makra]

Opencore and Ventura on a MP5.1 with multiple boot drives was a no go for me. As soon as I went back to one of the other boot drives the Ventura drive would no longer mount and I could not boot from it. I wasted I whole day trying to see if this was a workable solution for me. Probably would be fine for a single boot drive machine though. If I could have found a way to migrate the apps and setting from an old volume that may have been usable. So in the end after all this trouble I will be better off just buying a new Mac.

Not quite sure, whether I understand your issue. Could you describe a bit more precisely (OS versions), what you have now and what you intend to do?

 

[trifero]

macOS 13.6.5 RC installed atop 13.6.4 via USB, OCLP v.1.4.0n. Runs better than expected, didn't have to install the root-patch! Behaves like a supported Mac. YMMV
View attachment 2351790 Important edit! Upon acquiring the Install Assistant from the Discord OCLP Paradise updates, when building the macOS 13.6.5RC installer USB w/OCLP v.1.4.0n, OCLP mis-identified the OS version as macOS 13.6.2, a Apple Silicon ONLY version of macOS. Yet, proceeding to build the USB yielded a perfectly functional macOS 13.6.5RC build 22G619 installer. So, this may be a bug in the Create macOS Installer function of OCLP v.1.4.0n? In case anyone else may be deterred by this in-process mis-identification bug.

Nice!

 

[trifero]

With clean installs, Migratiom Assistant has always worked as intended whether the Migrated source is from a supported or unsupported Mac.

With OCLP, only unistall root patches and works like a charm. I make perfect bootable clones this way also.

 

[MacinMan]

macOS 13.6.5 RC installed atop 13.6.4 via USB, OCLP v.1.4.0n. Runs better than expected, didn't have to install the root-patch! Behaves like a supported Mac. YMMV
View attachment 2351790 Important edit! Upon acquiring the Install Assistant from the Discord OCLP Paradise updates, when building the macOS 13.6.5RC installer USB w/OCLP v.1.4.0n, OCLP mis-identified the OS version as macOS 13.6.2, a Apple Silicon ONLY version of macOS. Yet, proceeding to build the USB yielded a perfectly functional macOS 13.6.5RC build 22G619 installer. So, this may be a bug in the Create macOS Installer function of OCLP v.1.4.0n? In case anyone else may be deterred by this in-process mis-identification bug.

This happens with 1.3.0 and Ventura as well. When I did a Ventura 13.6.4 install on my iMac 17,1 it also identified it as 13.6.2 Seems to haven't been addressed yet. I still have that Ventura install on one of my external drives and it runs as expected, but I went back to Monterey for my internal install so I have a supported OS installed in the event I still decide to call apple support for my issue mentioned earlier in the thread, or anything else that may come up.

 

[RK78]

With OCLP, only unistall root patches and works like a charm. I make perfect bootable clones this way also.

Please, more details, directions in making bootable clones. With CCC 6 I can restore via system migration, but unable to produce a bootable clone, as I could with CCC 5 and High Sierra. Would really like to know more.

 

[wantanimac]

Picked up an Imac late 2013 16gb and 1tb ssd. Problem is, it is on Catalina. Wondering if I should chance trying OCLP to Ventura or just leave it alone. Not any sort of production system. Thinking about selling even though I just bought it.

 

[shafez]

Picked up an Imac late 2013 16gb and 1tb ssd. Problem is, it is on Catalina. Wondering if I should chance trying OCLP to Ventura or just leave it alone. Not any sort of production system. Thinking about selling even though I just bought it.

Yes you should update to Ventura using OCLP, I have the 8gb version and Ventura runs great.

 

[LookingOut]

Picked up an Imac late 2013 16gb and 1tb ssd. Problem is, it is on Catalina. Wondering if I should chance trying OCLP to Ventura or just leave it alone. Not any sort of production system. Thinking about selling even though I just bought it.

Absolutely patch it. Ventura will keep your machine running with system updates and security releases for a couple more years. Plus there are more modern software releases available.

 

[dandeco]

This happens with 1.3.0 and Ventura as well. When I did a Ventura 13.6.4 install on my iMac 17,1 it also identified it as 13.6.2 Seems to haven't been addressed yet. I still have that Ventura install on one of my external drives and it runs as expected, but I went back to Monterey for my internal install so I have a supported OS installed in the event I still decide to call apple support for my issue mentioned earlier in the thread, or anything else that may come up.

I wonder if that's why I've been getting that problem I mentioned. Once a week now, my MacBookPro11,4 running any version of OCLP since 1.0.0 starts to have trouble booting, and when it does, it's all sluggish and the buttons and text fields are greyed out like this, as if there were no root patches...

And if I try to apply the root patches, the loading bar moves to the bottom ala Mac OS 14 Sonoma and the volume is bricked! But now when I see it grayed out like I mentioned, I reboot right to my patched USB installer and re-install Ventura, temporarily fixing the problem.
I think it's trying to force an upgrade to an Apple Silicon version of Sonoma! So for now I am downgrading it to 0.6.8 and will have to suck up having the weather widget not working.

 

[MacinMan]

I wonder if that's why I've been getting that problem I mentioned. Once a week now, my MacBookPro11,4 running any version of OCLP since 1.0.0 starts to have trouble booting, and when it does, it's all sluggish and the buttons and text fields are greyed out like this, as if there were no root patches...
View attachment 2353711
And if I try to apply the root patches, the loading bar moves to the bottom ala Mac OS 14 Sonoma and the volume is bricked! But now when I see it grayed out like I mentioned, I reboot right to my patched USB installer and re-install Ventura, temporarily fixing the problem.
I think it's trying to force an upgrade to an Apple Silicon version of Sonoma! So for now I am downgrading it to 0.6.8 and will have to suck up having the weather widget not working.

I've never had any of those issues with either Mac MBP 11,1, or iMac 17,1. It was simply identified as the wrong version of Ventura for the USB installer.

 

[Surf2bikes]

Root patching failure on MacBook Pro 10,2 (OCLP 0.6.8)​

Can someone pls point me into the right direction about this following issue?
I installed Ventura 13.6.4 with OCLP 0.6.8. Installation was smooth. However I cannot apply root patch for IVY Bridge. See screen shot. "Unable to build kernel chache. Reason for patch failure (71)"

 

[Surf2bikes]

Root patching failure on MacBook Pro 10,2 (OCLP 0.6.8)​

Can someone pls point me into the right direction about this following issue?
I installed Ventura 13.6.4 with OCLP 0.6.8. Installation was smooth. However I cannot apply root patch for IVY Bridge. See screen shot. "Unable to build kernel chache. Reason for patch failure (71)"
View attachment 2353763

I found myself a solution here: https://www.reddit.com/r/OpenCoreLegacyPatcher/comments/13ppexb

 

[trifero]

Please, more details, directions in making bootable clones. With CCC 6 I can restore via system migration, but unable to produce a bootable clone, as I could with CCC 5 and High Sierra. Would really like to know more.

#396

 

[creatorofmatrix]

Hello everyone, Just posting this message to help other community members. I have Mac Book air 11 inches i7 Intel 2015 Early model and I have successfully upgraded my storage from 128gb to 1TB. I have used Samsung 980 ssd name m.2 Hope this information will help someone. I have also upgraded my system to Ventura and my air is now good to go for another 5 years. ;-)

 

[K two]

macOS 13.6.5 RC2 installed atop 13.6.5 RC1 via USB, OCLP v.1.4.0n. Runs better than expected, didn't have to install the root-patch! Behaves like a supported Mac. YMMV Please note: OCLP Build USB function still mis-identifies installer as macOS 13.6.2!

 

[PhoneandPad]

macOS Mojave iMac 10.14.6 on a late 2015 iMac with 16GB RAM.

I've tried OCLP 0.6.8, 1.2.1 and 1.3.0. Creating the bootable IOS Ventura installed seems to go OK. But it always get stuck exactly here at exactly 14 mins when attempting to install the OS to an external SSD drive. I've tired one brand of 32GB USB stick and another of 64 GB stick as the installer drive.

Syncing extracted data to disk
Could not verify trust (5)...

Then it hangs with mouse and keyboard still working for about 5 mins, then they freeze with the above on screen.

The target is a Crucial 2TB SSD with no faults that Disk Utility can detect. I'm wondering where I'm going wrong.

 

[K two]

.

macOS Mojave iMac 10.14.6 on a late 2015 iMac with 16GB RAM.

I've tried OCLP 0.6.8, 1.2.1 and 1.3.0. Creating the bootable IOS Ventura installed seems to go OK. But it always get stuck exactly here at exactly 14 mins when attempting to install the OS to an external SSD drive. I've tired one brand of 32GB USB stick and another of 64 GB stick as the installer drive.

View attachment 2354583

Syncing extracted data to disk
Could not verify trust (5)...

Then it hangs with mouse and keyboard still working for about 5 mins, then they freeze with the above on screen.

The target is a Crucial 2TB SSD with no faults that Disk Utility can detect. I'm wondering where I'm going wrong.

Why installing macOS onto Data? 🤷‍♂️