macOS 13 Ventura on Unsupported Macs Thread

[deeveedee]

ok I injected, with opencore configurator, the new kext "BlueToolFixup.kext" version 2.67 dated June 12th 2023, 2.66 was present, but it didn't work, it seems to me, the problem with the partial functioning of the bluettoth remained.

I don't know if what I did was right... in the new packages there are also other kexts concerning bluetooth "BrcmBluetoothInjector.kext" and "BrcmBluetoothInjectorLegacy.kext" also version 2.6.7 but I didn't inject these

Look closely at the link I sent you. The commits were updates after version 2.6.7. The updates will appear in the release version 2.6.8. You can find Acidanthera nightly builds here. That's not a guarantee that the updates address your issue, but just make sure you're testing with the fixes.

EDIT: You are correct - you only need the updated BluetoolFixup.kext from the BrcmPatchRAM 2.6.8 package.

EDIT2: Keep in mind that if you do test anything from the nightly builds, you're testing at your own risk. Nightly build may not be fully tested and should only be used if you can't wait for the release.

 

[hyperions]

Look closely at the link I sent you. The commits were updates after version 2.6.7. The updates will appear in the release version 2.6.8. You can find Acidanthera nightly builds here. That's not a guarantee that the updates address your issue, but just make sure you're testing with the fixes.

EDIT: You are correct - you only need the updated BluetoolFixup.kext from the BrcmPatchRAM 2.6.8 package.

EDIT2: Keep in mind that if you do test anything from the nightly builds, you're testing at your own risk. Nightly build may not be fully tested and should only be used if you can't wait for the release.

Thanks.. ok i test it tomorrow…

 

[deeveedee]

Thanks.. ok i test it tomorrow…

I don't use any open core configurators (just my preference not to), so I'm not certain, but you should be able to enable the [DEV] channel in your configurator so that BrcmPatchRAM 2.6.8 appears as an installable option. You can always download the BlueToolFixup.kext (in BrcmPatchRAM package) from the nightly builds and manually copy it to your Open Core EFI. I would suggest doing your EFI modifications on a USB drive (not your SSD) so that you can easily recover if you make a mistake. Boot from the USB drive when you want to test your changes. Before booting with a different EFI, Reset NVRAM.

 

[lplammas]

I mean alt key, left to the command key.

Yea I did

 

[mikelets456]

My iMac os is 12,2, still in high sierra! Yes I made that usb installer according to the instructions, and luckily I do backup everything! But still, I want to fix it and hope there’s a chance to save it

I don’t think you can go from High sierra to using any of the methods on this thread. I believe you have to get to Catalina via “dosdude1” website and method then make a OCLP boot usb with Big Sur through Ventura.

 

[mikelets456]

Yea I did

macOS Catalina Patcher

 

[lplammas]

I don’t think you can go from High sierra to using any of the methods on this thread. I believe you have to get to Catalina via “dosdude1” website and method then make a OCLP boot usb with Big Sur through Ventura.

Nah, I read through quite a lot of people who actually could do the same

 

[lplammas]

macOS Catalina Patcher

I can’t even see the screen from black

 

[OKonnel]

Late 2013 iMac 27" 14,2 Kepler running 13.4 no apparent issues in 0.6.6/13.4.

Upgraded to 0.6.7 and computer freezes on wake within a day of boot - screen indicates it's going to wake (backlit black screen with a cursor that can be moved for a second or two), then cursor freezes, but SSH session from another computer continues to be interactive for a short time before total freeze.

I left the post-install patches from 0.6.7 (primarily for Kepler support) in place and it's working fine.

Still very happy to have 13.4 on this machine at all

But why, dear friends who your have an iMac 14,2 like me, don't you go back to using Ventura 13.2.1 and for a few more months (or maybe forever) forget the later Ventura upgrades?…

With Ventura 13.2.1 and OCLP 0.6.7 (or 0.6.8 Nightly) our iMacs work perfectly with all Ventura’s features and with all Apple and third-party Apps, exactly as if they were iMac 2020 and supported!

Especially since macOS Sonoma and Ventura has now arrived, therefore, it will not have anything new to add compared to version 13.2.1.

The OCLP 0.6.7 version (or 0.6.8 Nightly) and the respective Post Install Patch, with the macOS 13.2.1 version also activate the Continuity Camera with my iPhone XS and our iMacs 14,2 (I specify that I have an i7 CPU and the nVidia GTX780M with 4 GB of VRAM).
But attention! Using OCLP 0.6.7 or 0.6.8 Nightly just ENABLE AMFI from the OCLP’s settings before creating the EFIBoot and activating it on boot with Option key.

The only thing missing in macOS 13.2.1 is the latest version of Disk Utility which can finally run SOS without having to deactivate the disks first. But honestly who uses this feature?...

After that you can update to the Ventura 13.5 or it latest update if in the future you read that OCLP’s Developers fixed all the problems that appeared from Ventura 13.3 onwards.

I especially feel sorry for new OCLP users who weren't lucky enough to discover OCLP with Ventura 13.2.1 and unfortunately started from macOS 13.3 onwards.

 

[roysterdoyster]

@OKonnel while I second your advice from my side, I stay on Ventura 13.3.1 by OCLP 0.6.7 Release. The 13.4 update left my MBP4,1 Early 2008 in an unusable state, so I decided to skip all Ventura updates in spite of upcoming Sonoma.

The problems I encountered in 13.3.1:
#1 Calculator not working. Does anyone know, how to fix it? Calculator accepts input, but then produces something along the lines of "No Number".
#2 Maps not working, displaying black/blank page
#3 Find my not working, displaying black/blank page
#4 Stage Manager cannot be enabled
#5 AirDrop not working, although it can be enabled in Control Center

 

[deeveedee]

@OKonnel while I second your advice from my side, I stay on Ventura 13.3.1 by OCLP 0.6.7 Release. The 13.4 update left my MBP4,1 Early 2008 in an unusable state, so I decided to skip all Ventura updates in spite of upcoming Sonoma.

The only problem I encountered in 13.3.1 is the Calculator not working. Does anyone know, how to fix it? Calculator accepts input, but then produces something along the lines of "No Number".

The Calculator works without issues for me in 13.2.1, 13.3.1 and 13.4 in Scientific Mode. My MBP6,2 has NVidia Tesla non-metal, so I think our Macs are patched with the same OCLP patches. I am using OCLP 0.6.7 (AMFIPass Beta 2 branch) with AMFI and Library Validation ENABLED (AMFIPass.kext injected). I also have no issues with Weather App.

EDIT: I modified this post to specify Scientific Mode for the Calculator. If I first use Scientific Mode and then switch back to Basic Mode, I have no issues. It's a work-around that works for me.

EDIT2: I just discovered that tapping C to clear the display in Basic Mode also fixes the Calculator display (without needing to toggle modes between Scientific and Basic).

 

[Earl Urley]

Was having an issue on a 13-inch 2014 rMBP upgraded to Ventura 13.4 from Big Sur 11.7.7 using release OCLP 0.6.7

Encrypted HTML 5 streams refused to load / play (certain vids on FuboTV, MAX, Disney+)

Issue fixed by switching SMBIOS spoof level from none to Minimal and overwriting previous EFI boot.

 

[mcdmaster]

Hello guys, please accept my posting a screenshot which indicates that macOS 13.5 beta is installed on mid-2012 MacBook Pro 9,1. Yes, although it is a hard-to-read one because it is in Japanese, I am confident that it adumbrates that I am enjoying this brand-new macOS upon my Old School platform without any flaws now!

Until I got these things done, I had been unsuccessful with this upgrade using the latest OCLP version at that time...0.6.7, indeed.
Based on my further previous upgrades (a DIY fashion) from whose issues unexpectedly taken place I had suffered, particularly I needed to work on two (2) remediations on my own end:
1. Use older OCLP releases e.g. 0.5.x to enable manipulating some switch values that are currently grayed out,
2. Replace the AirPort device-related Kernel Extensions (kext's) from current and to-be at the original timing.

Other facts, such as insights that have been given and/or shared among us already, were also followed. I much appreciate your efforts and contributions!

 

[JoinMeinHeaven]

Was having an issue on a 13-inch 2014 rMBP upgraded to Ventura 13.4 from Big Sur 11.7.7 using release OCLP 0.6.7

Encrypted HTML 5 streams refused to load / play (certain vids on FuboTV, MAX, Disney+)

Issue fixed by switching SMBIOS spoof level from none to Minimal and overwriting previous EFI boot.

Do you have 0.6.7 with amfi pass ?

 

[Earl Urley]

Do you have 0.6.7 with amfi pass ?

not enabled, would that fix it also?

 

[JoinMeinHeaven]

So you have installed 0.6.7 AMFI pass 2, and your settings look like this

 

[georgeimac]

I have the same Macbook as you---However, I stayed 0.6.6 OCLP and have zero problems. I have an Intel SSD with an adapter.

Thank you for the reply. I tried with 0.6.6 but still get stuck.

 

[JoinMeinHeaven]

Attempted to update a MBP mid 2015 11,4 with OCLP 0.6.7 to Ventura 13.4, but I get stuck on progress bar and apple logo everytime. I erased entire drive, but still no luck. Anyone else have this problem? I did upgrade original Apple SSD to OWC Aura 1Gb, otherwise, it's a stock system. Any help is appreciated.

I have the exact same issue. Verbose mode reveals a kernel panic. I have the original apple SSD

 

[georgeimac]

I have the exact same issue. Verbose mode reveals a kernel panic. I have the original apple SSD

I hope someone can help us

 

[olad]

It seems to me that 13 has been unlucky for macOS. It has been beset by more problems than it's worth. Not that I am superstitious, but... I hope Sonora turns out better.

 

[olad]

I have the exact same issue. Verbose mode reveals a kernel panic. I have the original apple SSD

I am using a MBP11,4. It is functioning very well. I don't use the Thunderbolt 2 ports, preferring to use the USB3 ports, so I can't find out if they work or not. But I have had no problems so far, with the OCLP 0.6.x series. From the get-go, I followed the instructions that said that the 11,4 was one of the series specifically 'banned' by Apple (I can't remember the exact phrase now). It meant that I had to SPOOF it to MBP14,3 - which is supported by Apple for upgrading to Ventura. Once I did that, there were no issues. As you can see from the attached, it is supposed to be a MBP14,3 whereas it is actually a MBP11,4. It is also using the original SSD. There is a provision in OCLP for the aberrations encountered when one changes to OWC (1 Terabyte I think was meant).

 

[georgeimac]

I am using a MBP11,4. It is functioning very well. I don't use the Thunderbolt 2 ports, preferring to use the USB3 ports, so I can't find out if they work or not. But I have had no problems so far, with the OCLP 0.6.x series. From the get-go, I followed the instructions that said that the 11,4 was one of the series specifically 'banned' by Apple (I can't remember the exact phrase now). It meant that I had to SPOOF it to MBP14,3 - which is supported by Apple for upgrading to Ventura. Once I did that, there were no issues. As you can see from the attached, it is supposed to be a MBP14,3 whereas it is actually a MBP11,4. It is also using the original SSD. There is a provision in OCLP for the aberrations encountered when one changes to OWC (1 Terabyte I think was meant).

Thank you, so much. Do I have to make a setting change in OCLP for the OWC 1Tb drive or is it automatic? Also, can you please direct me to the instructions that said 11,4 was banned and how to spoof?

 

[olad]

thank you so much. Do I have to make a setting change in OCLP for the OWC 1Tb drive or is it automatic?

Sorry, I wasn't paying attention. I misspoke (euphemism for I was wrong). In the older versions of OCLP (none of which I have presently (I will change that situation soon), there was a distinct *enabled* feature regarding NVMe drives, of which the OWC 1Tb is one (they are/were prone to kernel panics for no reason. This was supposed to change that I suppose). The nearest thing I can see - in the new OCLP interface is Settings/Extras 3rd Party NVMe PM. Perhaps that's it; I don't know. More knowledgeable people on the forum can tell you if that's what it does. It is normally enabled by default, so, if it the correct thing, you don't need to do anything.
Using word 'banned' is wrong - I just couldn't remember what it was that the real thing was. Suffice to say that the MBP11,4 was excluded for some reason (my memory fails me), and you had to spoof it to imitate a supported MBP, in this case MBP14,3.

 

[mikelets456]

Thank you, so much. Do I have to make a setting change in OCLP for the OWC 1Tb drive or is it automatic? Also, can you please direct me to the instructions that said 11,4 was banned and how to spoof?

I have an 11,4 with an 1 TB Intel SSD and adapter and no problems. I didn’t do anything with Monterrey or Ventura. It was simply recognized.

 

[JoinMeinHeaven]

The kernel panic seems to be amfi related. I can’t disable it no matter what I do. I really would like if someone could help me. I have booted into recovery and unable it but it still causes issues