macOS 13 Ventura on Unsupported Macs Thread

[Audit13]

I use a MacBook Pro 15" 9,1 as my main computer still, great machine, and you can upgrade it up to 16Gb RAM, works flawlessly, recommended.

As for the OCLP, I'm on v1.5 with Ventura, and don't plan to change anytime soon, very stable and smooth. I've tried Sonoma, but it wasn't as snappy. I don't recommend OCLP 2+ yet, it's in active devolpment and focused on Sequoia.

I also dual boot with the official Catalina installation, for fail safe reasons.

Keep trying installing it, it's worth it. You have to select the EFI boot option first then the install drive. On my system, don't know why but the first time it booted into Catalina recovery and asked to login, but after that Ventura installation proceed normally.

If anything fails you can always return to Catalina and run OCLP from there to rebuild the EFI partion.

I hope this helps!

Yes, this is helpful.

I will be getting a 2011 15" with the higher-resolution screen and will take the motherboard from the 2012 15" which has a lower-resolution screen to wind up with a 2012 i7 in a 2011 body. Once I confirm the swap is successful, I will replace the DVD drive with a hard drive caddy and dual-boot as you suggested.

Thanks for the tip!

 

[johnrak]

I installed Ventura but camera is not working except on Facetime. I searched the forum and I found that I have to use tttplus to give access on each app I need. Is that the only solution?

 

[HotMrmt]

Not familiar with your MBP, so a wild guess... if you've upgraded your Wi-Fi/Bluetooth (so it's not the original), you may benefit from changes made in OCLP 2.0.2. You'll need to install OCLP 2.0.2, Build and Install Open Core and apply OCLP 2.0.2 post-install patches.

I don't think the wifi/bt card is not the original, but I'm not 100% sure as this MBP is of a friend of mine which gave it to me. Anyway I installed the 2.0.2 but the BT continues to not work (as AirPlay, which is the thing I need most)..

 

[deeveedee]

@HotMrmt I don't have Airplay suggestions for you since it doesn't work on my MBP6,2. You may want to review known OCLP Issues, including this. Not sure why Bluetooth isn't working for you. What is the latest version of macOS that you can install on your MBP that produces working Bluetooth?

 

[HotMrmt]

@HotMrmt I don't have Airplay suggestions for you since it doesn't work on my MBP6,2. You may want to review known OCLP Issues, including this. Not sure why Bluetooth isn't working for you. What is the latest version of macOS that you can install on your MBP that produces working Bluetooth?

I had a MBP 6,2 and on Sonoma everything were working perfectly, even BT and AirPlay.. on this I upgraded from El Capitan to Ventura.. I read on reddit that changing the port type to 255 should solve the problem, but I’ve no idea on how to do that!

 

[deeveedee]

I had a MBP 6,2 and on Sonoma everything were working perfectly, even BT and AirPlay.. on this I upgraded from El Capitan to Ventura.. I read on reddit that changing the port type to 255 should solve the problem, but I’ve no idea on how to do that!

If your USB port type isn't set to "Internal" (255), I'd be very surprised if the OCLP Developers missed that and didn't correct it with a port map.

The way that OCLP Developers modify the USB Port map that defines USB Connector types is by using a USB port mapping kext. The OCLP Developers name their USB port mapping kext "USB-Map.kext." If you look in your Open Core EFI/OC/Kexts folder, you should see the USB-Map.kext file.

View the Contents of the USB-Map.kext and drill down to the Info.plist. Expand IOKitPersonalities_x86_64 and view the mapped USB Ports. You'll need to know the USB identifier of Bluetooth so that you can find it in the USB-Map.kext/Contents/Info.plist.

EDIT: I'm not sure how well the tool will work on your old MBP, but you can try using Hackintool to view your current USB port mapping. When you run Hackintool (v 4.0.3 at the time of this post), click on the USB Tab. Look in the "Connector" column to see if your Bluetooth USB port is "Internal."

 

[HotMrmt]

I’m not sure to be able to try these steps.. so I ask you: I’ve also a BT dongle, I Connect to the MBP but nothing changes.. maybe I have to abilitate something to use that? Thanks!

 

[makra]

I installed Ventura but camera is not working except on Facetime. I searched the forum and I found that I have to use tttplus to give access on each app I need. Is that the only solution?

I haven't had any issues with cameras for a long time, but if that's the case for you, I guess, tccplus (tccplus!) would be your friend.

 

[johnrak]

I haven't had any issues with cameras for a long time, but if that's the case for you, I guess, tccplus (tccplus!) would be your friend.

It might not be a permissions issue. The apps ask for permissions but the camera view is black. I found on another post that if I open Facetime (which is working fine) while the other app shows a black view, the camera starts working on both apps. Then I can close Facetime. The weird thing happens if I have Facetime open before opening the other app. Then the camera view becomes black on both apps.

 

[makra]

It might not be a permissions issue. The apps ask for permissions but the camera view is black. I found on another post that if I open Facetime (which is working fine) while the other app shows a black view, the camera starts working on both apps. Then I can close Facetime. The weird thing happens if I have Facetime open before opening the other app. Then the camera view becomes black on both apps.

I remember that my pre-metal MBP 8,1 acted up like that a couple of years ago (used FaceTime or PhotoBooth to get Zoom started). And I think I used tccplus to solve that - but I'm not sure... I would give it a try anyway.

 

[trifero]

Alwau

I installed Ventura but camera is not working except on Facetime. I searched the forum and I found that I have to use tttplus to give access on each app I need. Is that the only solution?

Have you tried to activate the root user and run those apps?

 

[deeveedee]

@HotMrmt The Bluetooth "fix" mentioned here used to be an issue for Macs patched with OCLP, until fixes were introduced in the Open Core EFI. Does this "fix" work for you?

 

[dcaccount]

Hello,
I have been using Ventura on my unsupported rMBP2014 with no issues for over one year. However continuity is not supported and I have read that I should change the SMBIOS Spoof Level to make it work.

So I wonder, if I backup the machine with TimeMachine, can I restore everything including the working OCLP patches in the case I mess something changing the SMBIOS Spoof Level?

Please advise, thanks

 

[deeveedee]

@dcaccount Have you considered adding an APFS volume and installing a new instance of macOS Ventura there? You could then create a bootable USB thumb drive with your spoofed SMBIOS Open Core EFI and boot the new macOS Ventura with the USB thumb drive.

This would allow you to test with minimal risk to your primary Ventura installation (and you don't need to backup/restore TimeMachine for your continuity test). If the test works and if you still don't want to risk your original Ventura installation, restore to your new APFS volume with Time Machine.

With a separate APFS volume and a USB thumb drive, you can perform your test without affecting your primary Ventura installation.

EDIT: @dcaccount If your test is successful, you could also perform a Migration to your new Ventura volume from your old Ventura volume (you don't need to restore from TM). When you Migrate to your new Ventura volume, you should first "Revert" OCLP post-install patches on the target volume BEFORE migrating to the target. After migration is complete, re-apply OCLP post-install root patches to the target volume.

 

[HotMrmt]

@HotMrmt The Bluetooth "fix" mentioned here used to be an issue for Macs patched with OCLP, until fixes were introduced in the Open Core EFI. Does this "fix" work for you?

Hey thanks! I tried but nothing happened.. BT still don't recognize any device, Airplay doesn't work, and in system infos the BT continues to be showed as "third_party_dongle".
I tried also with Hackintool and the BT Hub is set to internal, so u're right that's not the problem..

 

[deeveedee]

@HotMrmt "third_party_dongle" is expected because OCLP injects BluetoolFixup.kext in the Open Core EFI for your Mac. Probably more than you wanted to know and probably a discussion that would quickly go off-topic. If you want to learn more about Open Core, see if you can figure out how to test with BluetoolFixup.kext disabled in your Open Core config.plist. Explaining how is way off-topic here, but would be a great learning experience.

EDIT: If you do feel bold enough to experiment with your Open Core EFI, I'd recommend making OC EFI changes on a USB thumb drive and not on your SSD. This way if you screw up the EFI on the thumb drive, you can boot from your SSD EFI to recover.

 

[RK78]

Some help needed please:

Just installed newly formatted and partitioned SSD to replace old HDD in this iMac.

Three partitions: High Sierra (HFS+), Catalina 10.15.7 dosdude (APFS), and Ventura (APFS) on different paritions - exactly how it was set up previously with the HDD.

Can option-boot to the Ventura from a restart to the EFI, and when booted to the Ventura I can select either the High Sierra, the Catalina, or the Ventura as startup disk. Except when booted to the High Sierra, I am no longer offered the Ventura as a startup disk option. Only the HS and the Catalina. The Ventura volume, along with Update, does show on the High Sierra Desktop and in Disk Utility.

Wondering if anyone knows what to try to get the High Sierra-> Sys Prefs->Startup Disk to see the Ventura as a startup disk option, or what might be preventing it from showing?

 

[deeveedee]

@RK78 Not sure I understand your question, so I'll just explain what I do. I never install High Sierra and Big Sur or later on the same drive. Search to learn more about the compatibility issues. When I need to go back to HS, I boot from a different physical disk.

 

[RK78]

From early days here have been hearing not to run on same disk. However, this has never been a problem in any way at all before the SSD install. The reason I have it configured this way is that it is very convenient to access files from the HS to the Ventura and vice versa. And therefore, no reason to bring everything over to the Ventura from the HS, which goes back many years.

EDIT: Just booted to the Mini, (Mini,4,1) which likewise doesn't show the Ventura volume as a startup disk option. So guessing the Ventura at the iMac may never been available before the SSD install. What may have thrown me though, is that the iMac does show the Catalina in Startup Disk. Can't be completely certain that the Catalina wasn't present in Startup Disk before the SSD upgrade, but don't think it was there. In any case, nothing tragic if the Ventura doesn't show in the HS startup disk, since I can always option-boot to the Ventura via the EFI.

 

[HotMrmt]

@HotMrmt "third_party_dongle" is expected because OCLP injects BluetoolFixup.kext in the Open Core EFI for your Mac. Probably more than you wanted to know and probably a discussion that would quickly go off-topic. If you want to learn more about Open Core, see if you can figure out how to test with BluetoolFixup.kext disabled in your Open Core config.plist. Explaining how is way off-topic here, but would be a great learning experience.

EDIT: If you do feel bold enough to experiment with your Open Core EFI, I'd recommend making OC EFI changes on a USB thumb drive and not on your SSD. This way if you screw up the EFI on the thumb drive, you can boot from your SSD EFI to recover.

Thanks for the advice! I'll try to update to Sonoma instead...it seems like a more within my competences.. it's something I've wanted to try for a while, I don't have any documents or other important things to save, so I can go... and maybe the BT will start working!

 

[HotMrmt]

I updated to Sonoma, but BT doesn't work . Airplay now shows devices but when I try to stream it says "unable to connect to -device-". I have an Asus BT-500 dongle that worked with my MBP 6,2 , but if I connect that to this MBP it doesn't change anything.. Maybe I have to disable the internal BT? How? Thanks!

 

[johnrak]

What browser are you using. I was using Brave on my previous setup with Big Sur and it was flawless. Now I'm on Ventura and I start to notice lag when I type in webpages.
Could it be related to the kepler patch? I tried to change the graphics backend in brave://flags/ from OpenGL to Metal but it didn't fix it.

 

[RK78]

Can someone please tell me, re. Library Validation (not talking about Patcher Settings with option to disable): what should be the default, disabled or enabled? (Long story: ran sudo nvram boot-args=amfi_get_out_of_my_way=0x1, which appears to have disabled Library Validation, and which I have tried reversing so far with no luck).

Wondering if Library Validation disabled is needed to run OCLP

Seeing com.apple.security.libraryvalidation.plist set to disabled in /Library/Preferences

 

[tennisproha]

I'm randomly having issues playing Youtube on Safari today. Youtube works on Firefox but Safari is intermittent. Anyone else having his issue?

 

[natus.w]

I updated to Sonoma, but BT doesn't work . Airplay now shows devices but when I try to stream it says "unable to connect to -device-". I have an Asus BT-500 dongle that worked with my MBP 6,2 , but if I connect that to this MBP it doesn't change anything.. Maybe I have to disable the internal BT? How? Thanks!

Does airplay work on the MBP with that dongle? (you may have to force the system to use the external BT controller)

Even then from what I can recall that dongle did use a Realtek chipset (which was not supported by MacOS), you’ll have to switch to a Broadcom/Cyprus based dongle, or swap your NIC assembly for one from a later model Mac..