Sidebar Sidebar
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

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.
olad said:
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.
Click to expand...
Just ignore it. The 9999... is because you are spoofing another model. It is a failsafe used by OCLP so there is no firmware update attempt during the next macOS update. You must use Big Sur to update the firmware on your model but only after resetting PRAM back to 476.0.0.0.0.
 
  • Like
Reactions: olad
For those that installed the security update and got stuck in a loop did you unpatch first ? I wonder if this would make a difference. Yet I’m sure in the original documents of OCLP for Ventura it recommended turning off the small updates for those that read it.
 
macpro_mid2014 said:
Just ignore it. The 9999... is because you are spoofing another model. It is a failsafe used by OCLP so there is no firmware update attempt during the next macOS update. You must use Big Sur to update the firmware on your model but only after resetting PRAM back to 476.0.0.0.0.
Click to expand...
Thanks. Will do as you suggest
 
rehkram said:
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.

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.
Click to expand...

Nice of you to write such long reply.👍

In my experience, above 3 are most important. Should be done in the order of 7, 1 and then edited 6.
 
  • Like
Reactions: rehkram
mwidjaya said:
Nice of you to write such long reply.👍

In my experience, above 3 are most important. Should be done in the order of 7, 1 and then edited 6.
Click to expand...
I take your points there. It was a "stream of consciousness" post. The actual workflow is different to the order. In other words, I presented them as things to consider before rolling one's own workflow.

And yes, definitely do a clean install at some point, particularly if you encounter glitches.
 
  • Like
Reactions: olad
tadafumi said:
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.
(^^;)
Click to expand...

A volume called "Update" is created during installation, and there is an install log in it.
The last 3 lines of the log are below;

Dec 16 23:00:55 MacBook-Air Installer Progress[58]: Status is "残り約14分…"
Dec 16 23:01:54 MacBook-Air OSInstaller[208]: ------- Install Failed -------
Dec 16 23:01:54 MacBook-Air OSInstaller[208]: Operation: Install Mobile Software Update failed, Failure Reason: Error Domain=com.apple.osinstall Code=-81 "ソフトウェアアップデートの準備中にエラーが起きました。" UserInfo={NSLocalizedDescription=ソフトウェアアップデートの準備中にエラーが起きました。, NSUnderlyingError=0x600003520510 {Error Domain=MobileSoftwareUpdateErrorDomain Code=53 "Splat global ticket failed to verify" UserInfo={target_update=22C65, NSLocalizedDescription=Splat global ticket failed to verify, NSUnderlyingError=0x600003520db0 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}}}

By the way,
"ソフトウェアアップデートの準備中にエラーが起きました。" ==> "an error occurred preparing the software update"


Does anyone know the solution?
 
MacBook Pro 2014
after upgrade from Ventura 13.0 to Ventura 13.1 I have display issue, it's shows only resolution 2880x1800 (Default) and is Unknown display.
Could someone advise how to fix this?

Update: just installed again latest OpenCore Legacy Patcher and voila!:)
 
Last edited:
olad said:
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.
Click to expand...
It´s completely normal. It´s a spoofed system version modified by OCLP.
 
  • Like
Reactions: olad
tadafumi said:
Does anyone know the solution?
Click to expand...
Time to try from a clean slate. Assume your files are copied/backup already.

Reset NVRAM, option-boot, select boot.efi, select installer, select disk utility, erase internal SSD, choose GUID/APFS, proceed with installing Ventura.
 
A combination of Mr Macintosh on YT and these forums have been invaluable in guiding me through the installation of Ventura on my Late 2013 21inch iMac.

Thanks!

However, I cannot seem to get Airplay running at all. I've followed the tutorials, checked the settings, and it is just not appearing. However, I think the computer is supported with OCLP.

Has anyone got any tips?
 
Command V is killing almost everything, including Messages and Safari, both on internal keyboard and external Magic Keyboard. Right click paste works fine. Full fresh install on Macbook Air 2017 using latest OCLP and Ventura 13.1.

Any ideas?

Edit: Rebooting using EFI in the bootloader menu and then choosing Ventura might have fixed it. Is something I should do every time I reboot?
 
Last edited:
daabido said:
Rebooting using EFI in the bootloader menu and then choosing Ventura might have fixed it. Is something I should do every time I reboot?
Click to expand...
I see the same. Both with som key commands and arrows, and also some apps that sometimes quit unextepectadly.
A straight reboot fixes it every time. Can live with it.
 
  • Like
Reactions: daabido
SPJones said:
A combination of Mr Macintosh on YT and these forums have been invaluable in guiding me through the installation of Ventura on my Late 2013 21inch iMac.

Thanks!

However, I cannot seem to get Airplay running at all. I've followed the tutorials, checked the settings, and it is just not appearing. However, I think the computer is supported with OCLP.

Has anyone got any tips?
Click to expand...
You can only use airplay from your unsupported device to a supported device - not the other way round atm.
 
Good news!
With Ventura 13.1 and the latest OCLP 0.5.3 on my iMac 14,2 (see my signature for full specs) finally AirPlay also works with iPhone mirroring and Chromecast streaming of YouTube videos and more.
It worked before but, now, I can use OCLP in standard mode and without having to select the "Minimal" SMBIOS option.

Bad news.
They still concern the issues of "Continuity Camera" and also the alternative “Camo Studio” applications.
So… yesterday I discovered that the automatic selection of subjects from the background does not work in my Mac and the option is disabled both in Preview and in Photos.
If I try to act through the "Quick actions" of the contextual menu (right mouse button or CTRL click on selected images or photos) it seems to work but, in fact, nothing happens.

A good weekend at all! :)
 
Last edited:
  • Like
Reactions: NataliaC and coolio2004
New 0.53 fixes some errors:
  • Resolve AirPlay to Mac support on Ventura with VMM
  • Resolve WindowServer crashing on KDK-less with macOS 13.2 and Rapid Security Response updates
Now we have fully airplay support and no more boot loop with 13.2 security response update.
Thanx so much to the developers.
 
Last edited:
  • Like
Reactions: macpro_mid2014, Sanmiguel71, NataliaC and 1 other person
Hello,
I have just installed Ventura on my rMBP 2014 and it is working perfectly. I am new to OpenCore Legacy Patcher.

Can you please advise what I shall do when there is an update of the OCLP?

Thanks for helping,
Daniele
 
mwidjaya said:
Old kexts not compatible. Need to remove them from /Library/Extensions. Boot safe mode. Remove all except these 3. Apply root patch, reboot.

View attachment 2129053
Click to expand...
Thank you very much for your reply and your willingness to help, @mwidjaya ! Your post was exactly the right advice for my Error Domain=KMErrorDomain Code=71 "Unable to resolve dependencies" OCLP problem.

I had indeed used Apple's Migration Wizard twice on OS upgrades, once from Mojave (w/ Dosdude1's patcher) to Big Sur on my former MacBookPro5,2, then from Big Sur to Ventura (both OCLP-based installations). That has obviously lead to KEXTs from the former OS versions being preserved in /Library/Extensions, which - as far as I understand (?) - have now interfered with OCLP's attempt to rebuild the kernel cache in the process of applying its patches to the root volume.

So to troubleshoot the problem in accordance to your advice, I've moved all KEXTs from /Library/Extensions to a backup location except for the three you've mentioned above, of course. Applying OCLP's root patching did no longer trigger the Error Domain=KMErrorDomain Code=71 "Unable to resolve dependencies" problem afterwards and my MacBookPro9,1 is booting normally again.

So to cut a long story short, you've probably saved me hours, if not days to recover my MacBook Pro Mid 2012 from being stuck at regular boot. Thank you really very much!
 
  • Like
Reactions: mwidjaya
I have now done a clean install of macOS Monterey, macOS Ventura 13.0.1 and macOS Ventura 13.1 on a late 2016 MacBook Pro 15" (Skylake CPU and AMD Radeon 460). The last supported macOS for this laptop is Monterey. It seems HEVC video support (and some HEIC support for images) is missing in macOS Ventura with OpenCore Legacy 0.5.3. This means you can't open and watch HEVC videos (H.265 codec) in Ventura, but you could in Monterey. H.264 videos work in Ventura though. It also means you can't watch videos made on iPhones/iPads since they are all in HEVC. Also Photos will hang when importing or watching your iPhone videos/photos. I hope the wonderful team of OpenCore Legacy will re-enable HEVC and HEIC support in their upcoming releases of OpenCore Legacy for my 2016 MacBook Pro model and other Skylake Macs. Anyone has more information on this issue???????????
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back