macOS 13 Ventura on Unsupported Macs Thread

[hyperions]

From the OCLP instructions:

How to Boot Recovery through OpenCore Legacy Patcher​

By default, the patcher will try to hide extra boot options such as recovery from the user. To make them appear, simply press the Spacebar key while inside OpenCore's Picker to list all boot options.

General troubleshooting | OpenCore Legacy Patcher

So you may actually have a recovery partition, but you will rarely need to use it.

ok thanks... spacebar is ok...

 

[amaze1499]

MBP4,1 Early 2008 on Ventura 13.3.1 by OCLP 0.6.7.
Out of nowhere, the optical drive started spinning and does not stop.
How can this be solved?

Same issue when booting from USB installer or another good known system? Possible quick fix: PRAM reset.

 

[Larsvonhier]

MBP4,1 Early 2008 on Ventura 13.3.1 by OCLP 0.6.7.
Out of nowhere, the optical drive started spinning and does not stop.
How can this be solved?

Again, not the case here on my MBP4,1 (17" glossy). Did not do it with 13.3.1 and not on current 13.4.1.
Is there any disc inserted in the drive? Otherwise, it could not spin by itself or you would probably not hear anything.

 

[georgeimac]

@trifero I also have an MBP11,4. BUT, it did not work well until it was spoofed to MBP14,3 - there was a reason given by the developers of OCLP about a year or so ago why one had to spoof the 11,4 and present it as 14,3... something about support but I forget. In any case, every time I do an update, I first unpatch the boot, reboot, do the macOS update, reboot, then repatch the boot. I am using MBP11,4 spoofed to seem as MBP14,3 to macOS, and I am using the OCLP AMFI pass beta 4 (that allows me to use VMWare Fusion to run Windows 11), on Ventura 13.5 Beta (Build 22G5059d). I haven't tried to use the 11,4 without spoofing; perhaps other have had success without it, I don't know.

Can you please go over the process to spoof this machine. I’m confused with unpatching boot etc… I appreciate your help.

 

[georgeimac]

I have a 11,5 mid 2015 MBP running Ventura 13.4 with OCLP 0.6.7 without problems.

I think there maybe something with MBP 11,4. Did you do anything different, such as spoofing the OCLP to MBP14.3?

 

[roysterdoyster]

Same issue when booting from USB installer or another good known system? Possible quick fix: PRAM reset.

Thanks for the suggestion, it didn‘t work

 

[roysterdoyster]

Again, not the case here on my MBP4,1 (17" glossy). Did not do it with 13.3.1 and not on current 13.4.1.
Is there any disc inserted in the drive? Otherwise, it could not spin by itself or you would probably not hear anything.

No, there is n o disc inside the Superdrive. It d o e s spin and it d o e s make noise. I can take it out of the MBP4,1, if that is possible?

 

[K two]

Yes .
Mount efi.
Edit config.plist with OpenCore Configurator
Click device properties
Change region e.g. USA
Save
Reboot.
Try Apple TV.
Keep your working config just in case so you can just copy back if things go wrong.
Repeat process when you update Opencore several people I messaged on the forum to test for me had zero issues with Apple TV after this , obviously Opencore team would be better to see if there’s a more permanent fix but only matters when you update really and have to do it again.

This from Mr. Grymalyuk - (OpenCore Configurator is another tool but is heavily outdated and the Mackie version is known for corruption. Please avoid these kinds of tools at all costs!). https://dortania.github.io/OpenCore-Install-Guide/installer-guide/

Why would "the boss" put this in the docs?

 

[StefanAM]

This from Mr. Grymalyuk - (OpenCore Configurator is another tool but is heavily outdated and the Mackie version is known for corruption. Please avoid these kinds of tools at all costs!). https://dortania.github.io/OpenCore-Install-Guide/installer-guide/

Why would "the boss" put this in the docs?

Use https://github.com/ic005k/OCAuxiliaryTools. Never failed me; easy OC config and update.

 

[Larsvonhier]

No, there is n o disc inside the Superdrive. It d o e s spin and it d o e s make noise. I can take it out of the MBP4,1, if that is possible?

Very strange. Normally the drive electronics does not start the motor without disc detection. This is not done by the OS, but autonomously.
You can take the drive out (ppl normally then replace it by a 2nd SSD, there were adapters for such).
Have you also checked if the noise is really macOS dependent (by i.e. booting some older macOS again)? Just to rule out your drive has developed some other defect in the meantime...
(btw. 13.4.1 is very strongly recommended due to security issues that have been addressed since 13.4 and older).

 

[amaze1499]

Very strange. Normally the drive electronics does not start the motor without disc detection. This is not done by the OS, but autonomously.
You can take the drive out (ppl normally then replace it by a 2nd SSD, there were adapters for such).
Have you also checked if the noise is really macOS dependent (by i.e. booting some older macOS again)? Just to rule out your drive has developed some other defect in the meantime...
(btw. 13.4.1 is very strongly recommended due to security issues that have been addressed since 13.4 and older).

Or something is stuck inside

 

[TOM1211]

This from Mr. Grymalyuk - (OpenCore Configurator is another tool but is heavily outdated and the Mackie version is known for corruption. Please avoid these kinds of tools at all costs!). https://dortania.github.io/OpenCore-Install-Guide/installer-guide/

Why would "the boss" put this in the docs?

I do also have OpenCore Auxiliary Tools as mentioned above to edit the config.plist .
I sometimes just edit the config.plist myself when making changes was just giving a quick fix that was user friendly (in my opinion) and easy,
again have asked some members to test and before posting by messaging them directly.
I also stated in every post from here to Discord to keep a backup of config.plist for any issues.

 

[roysterdoyster]

Very strange. Normally the drive electronics does not start the motor without disc detection. This is not done by the OS, but autonomously.
You can take the drive out (ppl normally then replace it by a 2nd SSD, there were adapters for such).
Have you also checked if the noise is really macOS dependent (by i.e. booting some older macOS again)? Just to rule out your drive has developed some other defect in the meantime...
(btw. 13.4.1 is very strongly recommended due to security issues that have been addressed since 13.4 and older).

Thank you for your help. Can I take out the superdrive and leave the slot empty?
I did not yet update to 13.4.1 as trying to go from 13.3.1 to 13.4 was a total desaster. It tooks me weeks to get a working 13.3.1 back, had to build up from scratch.
Is 13.4.1 on the MBP4,1 fully functional?

 

[davidlv]

Thank you for your help. Can I take out the superdrive and leave the slot empty?
I did not yet update to 13.4.1 as trying to go from 13.3.1 to 13.4 was a total desaster. It tooks me weeks to get a working 13.3.1 back, had to build up from scratch.
Is 13.4.1 on the MBP4,1 fully functional?

I think you can remove the optical unit and just leave the bay empty. OWC (macsales.com) sells a data doubler unit designed to replace the optical drive with an SSD, but your model MBP is not listed as compatible. You might want to connact them to see if it would work in your MBP.

OWC Data Doubler - Replace Mac Optical Drive with an SSD

Get all the tools needed to safely replace the optical drive of your MacBook Pro, Mac mini, or iMac with a 2.5-inch HD or SSD. Includes DIY install videos.

eshop.macsales.com

More important, try to get an external drive loaded with a CarbonCopy Cloner backup. If you have one, reverting back to a clone of your working drive is simple and only takes a short while even after wiping the drive.

 

[Larsvonhier]

Thank you for your help. Can I take out the superdrive and leave the slot empty?
I did not yet update to 13.4.1 as trying to go from 13.3.1 to 13.4 was a total desaster. It tooks me weeks to get a working 13.3.1 back, had to build up from scratch.
Is 13.4.1 on the MBP4,1 fully functional?

13.4.1 was not a problem to get my MBP4,1 onto. (But I remember your 4,1 seems a bit special in some aspects ;-)
You can just unplug the snap-in connector of the DVD/combo drive or take out the ribbon cable between mainboard and drive. I´d let the drive itself in its place, otherwise you get a weakened top cover spot there and also the weight distribution will be different without the drive in place.

 

[roysterdoyster]

13.4.1 was not a problem to get my MBP4,1 onto. (But I remember your 4,1 seems a bit special in some aspects ;-)
You can just unplug the snap-in connector of the DVD/combo drive or take out the ribbon cable between mainboard and drive. I´d let the drive itself in its place, otherwise you get a weakened top cover spot there and also the weight distribution will be different without the drive in place.

Thanks alot, Lars, I will do as per your advice, highly appreciating it.

 

[macpro_mid2014]

MacBookPro11,2 and Ventura 13.4.1 and AMFIbeta4: Just updated to Parallels Version 18.3.2 (53621) (Released today) from 18.3.1. It screws up with root patching. After reapplying root patching, Parallels refuses to start unless I allow the System Extensions on Privacy & Security AGAIN, and this screws up with root patching again.

SO - DO NOT UPDATE PARALLELS

EDIT: I solved that by installing OCLP 0.6.7, rebooting, allowing Parallels System Extensions, rebooting, and reinstalling AMFIbeta4.
After all of this, root patching is still working.
Even with amfi=0x80 in boot-args, Parallels still started while I was at OCLP 0.6.7.

 

[Sven G]

^^^ Strange, that you had those difficulties: personally, on a similar machine (MBP11,3), I updated Parallels Desktop to 18.3.2; then, when opening a VM with the Parallels hypervisor (which I use for Windows and Linux VMs with nested virtualization), I got prompted to approve the kexts, rebooted and then everything was fine, without the need to touch OCLP (amfipass-b4)…

 

[ipadawan]

Don't know why, but since yesterday, I have issues to log in on the MBP (mid 2015) to get access to the cloud.
I can log in to the iCloud using the browser, but the system itself can not. I keep getting "I need to log in to get access to several services." Photo's, agenda, notes e.t.c doesn't synchronize with the cloud. Also, not every time, but often Dropbox is crashing.

Any suggestions? Ventura 13.3. OCLP

 

[mikelets456]

Don't know why, but since yesterday, I have issues to log in on the MBP (mid 2015) to get access to the cloud.
I can log in to the iCloud using the browser, but the system itself can not. I keep getting "I need to log in to get access to several services." Photo's, agenda, notes e.t.c doesn't synchronize with the cloud. Also, not every time, but often Dropbox is crashing.

Any suggestions? Ventura 13.3. OCLP

Have you tried a reboot? Are your other Apple products syncing? Maybe try this?

Can't log into iCloud on my Mac - Apple Community

discussions.apple.com

 

[houser]

Any suggestions? Ventura 13.3. OCLP

Maybe a long shot but are you paying attention to what password it is asking for? Sometimes it is the Mac user PW, sometimes the iCloud PW.

 

[ipadawan]

Have you tried a reboot? Are your other Apple products syncing? Maybe try this?

Can't log into iCloud on my Mac - Apple Community

discussions.apple.com

Yes, several times. All other devices doesn't have any issue's. I did use Etrecheck, but no issues that are linked to the cloud.

Maybe a long shot but are you paying attention to what password it is asking for? Sometimes it is the Mac user PW, sometimes the iCloud PW.

Defiantly the AppleId PW.


I didn't see this before but I saw a error "An internal error occurred while running the Root Patcher:Argument of type bool is not iterable". Some connection with this?

Should I update to 0.6.7 instead of staying at 0.6.2?

 

[the1010boy]

Hi folks, I am running macOS Ventura on my Mac Pro 5,1 using OCLP version 0.6.7. It's running well so far as I can tell.

However, just today I noticed the inability to edit 4K HEVC videos in Photos.app that were taken by my iPhone 12 Pro. Curious if anyone else has seen this or experienced this. 🤔

Here's the error I get...

"Edit" button greyed out in upper right hand corner of the photos.app (see attached images)

An exclamation mark inside a triangle is present in the upper right of the photo.

When the exclamation mark inside a triangle is clicked on, a popup with "Unsupported Video Format. The full-resolution video is unsupported" appears (see also attached images).

I am successfully signed into iCloud and iCloud Photos is enabled in the Photos.app with "Download Originals to this Mac" selected with "Shared Albums" also enabled (see attached photos). And all photos and videos taken on my iPhone have been automatically syncing to my Mac Pro's Photos app successfully for some time now (or rather ever since my successful install of Venture on this Mac Pro last month).




Lastly, when I click on the "More Info..." button in the "Unsupported Video Format" popup dialog it takes me to this website at support.apple.com which states, among other thing: "Support for HEIF and HEVC is built into iOS 11 and later and macOS High Sierra and later..." so technically this should be working, true? ...since last I checked Ventura is a later macOS than High Sierra 😉.

So could this be a OpenCore Legacy Patcher issue or something else?

 

[didily]

Hello everyone, I installed instead of an optical drive on iMac 12.2, installed an SSD on reboot, it gives an error, but if you turn off the poppy and turn it on, everything loads without problems, tell me what could be the problem OCLP 0.6.7

 

[Ara_Sarat]

Hello guys. I finally installed my MacOS Ventura on my 13-inch MacBook Pro 2015. It works perfect but I have a strange bug. When I use hotkeys like cmd + с or cmd + v or using arrows to scroll web sites or change pictures in telegram, app just crashes and offering to reopen it. anyone have same problem? how I can solve this? thanks in advance!
P.S. while I typing this message, I accidentally use arrows couple times, and safari crashes.. I rewrite this text 3 times, so that bug is pretty painful.