macOS 13 Ventura on Unsupported Macs Thread

[m4v3r1ck]

Good morning everyone,

Update: My latest attempt to install macOS Ventura won't surpass its last booting stage:

Sorry for the bad photography.

During the last reboot, I let my Mac run all night: no luck.

Disk Utils this morning after forced shut down:

SSD - first and successfully completed install

/dev/disk8 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +499.9 GB   disk8
                                 Physical Store disk2s2
   1:                APFS Volume Macintosh HD - Data     8.7 GB     disk8s1 <===
   2:                APFS Volume Preboot                 4.7 GB     disk8s2
   3:                APFS Volume Recovery                1.2 GB     disk8s3
   4:                APFS Volume macOS Ventura           10.9 GB    disk8s4
   5:                APFS Volume VM                      1.1 MB     disk8s6

SSD - third and (seems to be) failed install

/dev/disk5 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +499.9 GB   disk5
                                 Physical Store disk3s2
   1:                APFS Volume Macintosch HD - Data    3.6 GB     disk5s1 <===
   2:                APFS Volume Preboot                 4.7 GB     disk5s3
   3:                APFS Volume Recovery                1.2 GB     disk5s4
   4:                APFS Volume Macintosch HD           10.9 GB    disk5s5
   5:                APFS Volume VM                      1.1 MB     disk5s6

1st install 1: APFS Volume Macintosh HD - Data 8.7 GB disk8s1 <===
2nd install 1: APFS Volume Macintosch HD - Data 3.6 GB disk5s1 <===


Screencap of just now:

This really puzzles me, yesterday I installed perfect and the third try seems to be a no-go. Confused...

 

[m4v3r1ck]

FYI - the current OCLP069n Sonoma Branch EFI boots Supported Catalina, Big Sur and Monterey as well as, Unsupported Ventura and Sonoma with perfection. Fear not. 😎

Thanks for the heads-up.

 

[samiqa]

I've MacBook 11,3 mid 2014 with Nvidia 750m gpu and with NVME ssd

I'm on big sur 11.7.10 with oclp 0.6.8 installed , but I don't receive any Monterey or Sonoma updates,nothing shows in settings .
Also when trying to install manually , it's says my mac isn't supported .


can someone explain to me why I'm having this problem , I tried to reinstall oclp but no fix.

another question , if I remove oclp according to this , will I boot to big sur without prloblems ? like the prohibited symbol problem ? my mac support big sur natiavly , it should boot without problems after removing the oclp and doing nvram reset ?

 

[m4v3r1ck]

Turned on Verbose Mode during install boot with Command + V while applying to ENTER on the Macintosh HD in the boot picker, to troubleshoot my ever failing (5th try) install of macOS Ventura 13.6. (Only once I succeeded to install but using Migration Assistant after the install, wrecked the installation.)

AbortConmands::5381:Port 0 - called, devicewithError 0, errCode = 0x0030005

is repeatedly printed during verbose boot and is the last line printed in the CLI.

Searched and found a corresponding thread on GitHub.

Anyone having this same issue /output?

 

[in.e.motion]

In terminal, type 'kextstat | grep -i bluetool' If the result doesn't show version 2.6.8 (as.acidanthera.BlueToolFixup (2.6.8)) then get the latest BlueToolFixup.kext (inside BrcmPatchRAM) here. If you don't know how to upgrade the kext, wait for OCLP 0.6.9 release which will be out soon (Devs say the release of OCLP 0.6.9 is anticipated for the release date of Sonoma 14.0). If you don't want to wait for the official 0.6.9 release, use the 0.6.9 nightly sonoma-development build and refer to the Sonoma thread for help.

% kextstat | grep -i bluetool
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
59 0 0xffffff80043bb000 0xa000 0xa000 as.acidanthera.BlueToolFixup (2.6.6) 8816945F-3FA8-3830-9F2B-77A892176E46 <55 9 7 6 3 2 1>

have the 2.6.8 files:
% ls -al BrcmPatchRAM-2.6.8-RELEASE
total 24
drwx------@ 13 j staff 416 Sep 25 09:27 .
drwx------+ 7 j staff 224 Sep 25 13:38 ..
-rw-r--r--@ 1 j staff 10244 Sep 25 09:27 .DS_Store
drwxr-xr-x@ 3 j staff 96 Jun 15 22:39 BlueToolFixup.kext
drwxr-xr-x@ 3 j staff 96 Jun 15 22:39 BrcmBluetoothInjector.kext
drwxr-xr-x@ 3 j staff 96 Jun 15 22:39 BrcmBluetoothInjectorLegacy.kext
drwxr-xr-x@ 3 j staff 96 Jun 15 22:39 BrcmFirmwareData.kext
drwxr-xr-x@ 3 j staff 96 Jun 15 22:39 BrcmFirmwareRepo.kext
drwxr-xr-x@ 3 j staff 96 Jun 15 22:39 BrcmNonPatchRAM.kext
drwxr-xr-x@ 3 j staff 96 Jun 15 22:39 BrcmNonPatchRAM2.kext
drwxr-xr-x@ 3 j staff 96 Jun 15 22:39 BrcmPatchRAM.kext
drwxr-xr-x@ 3 j staff 96 Jun 15 22:39 BrcmPatchRAM2.kext
drwxr-xr-x@ 3 j staff 96 Jun 15 22:39 BrcmPatchRAM3.kext

Q: how to build ?
Thks

 

[dandeco]

You shut down your computer because of a problem" never stops​

#46

That's not really the problem. It only happens when my MacBook Pro fails to boot via OCLP and I have to restart. Even if it's once, I often get the whole kit and caboodle, as I call it.

 

[deeveedee]

Q: how to build ?
Thks

Not trying to be unhelpful, but if you're asking "how to build," you should probably wait for OCLP 0.6.9.

That said, if you want to learn, you will need to replace the BlueToolFixup.kext in your OC EFI with version 2.6.8 that you found in the BrcmPatchRAM package from Dortania. I don't think I should explain anything else, because learning how to do that is important to actually doing it.

EDIT: The current Release Notes indicate that the next release of OCLP will be 1.0.0 on Oct 2. The release date is a target that could change.

 

[deeveedee]

@m4v3r1ck Could you please type the following in terminal after you boot a working version of macOS and then report the response?

nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:OCLP-Version

 

[m4v3r1ck]

@m4v3r1ck Could you please type the following in terminal after you boot a working version of macOS and then report the response?

nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:OCLP-Version

Thanks for your help.

❯ nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:OCLP-Version
4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:OCLP-Version    0.5.0%00

The OCLP version 0.5.0 upon which I build my current macOS Monterey 12.7 on another internal SSD.

 

[deeveedee]

Thanks for your help.

❯ nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:OCLP-Version
4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:OCLP-Version    0.5.0%00

The OCLP version 0.5.0 upon which I build my current macOS Monterey 12.7 on another internal SSD.

A lot has improved in OCLP for Ventura since 0.5.0.

Not telling you what to do, but here's what I would do...

• Build and Install Open Core using OCLP 0.6.8 (Release): build Open Core to a bootable USB
• Boot your Mac using the EFI on the USB and do your Ventura testing
• When you've proven to yourself that 0.6.8 works for your Ventura and Monterey volumes, update your SSD EFI to the OC EFI generated by OCLP 0.6.8
• Do not have more than one OC EFI in your Mac (except in cases where you're testing with an OC EFI on a bootable USB thumb drive) (way too confusing for most users)

 

[m4v3r1ck]

A lot has improved in OCLP for Ventura since 0.5.0.

I downloaded the 0.6.8 OCLP to my macOS 12.7 SSD to create the macOS Ventura Installer. As shown earlier, I successfully installed macOS 13.6 on a fresh erased SSD. After using Migration Assistant in Ventura I lost the installation completely. Not booting through and halting @30%.

Reinstalling gives me the error posted above.

 

[deeveedee]

I downloaded the 0.6.8 OCLP to my macOS 12.7 SSD to create the macOS Ventura Installer. As shown earlier, I successfully installed macOS 13.6 on a fresh erased SSD. After using Migration Assistant in Ventura I lost the installation completely. Not booting through and halting @30%.

Reinstalling gives me the error posted above.

Ok - I apologize for my confusion. I thought you were using OCLP 0.5.0. When you are installing Ventura, are you absolutely certain that you are booting with an OC EFI generated by OCLP 0.6.8?

 

[m4v3r1ck]

Ok - I apologize for my confusion. I thought you were using OCLP 0.5.0. When you are installing Ventura, are you absolutely certain that you are booting with an OC EFI generated by OCLP 0.6.8?

Not sure, how can I check?

 

[deeveedee]

Not sure, how can I check?

You just did by running the OCLP-Version command that I gave you. It reported 0.5.0.

 

[m4v3r1ck]

Ok - I apologize for my confusion. I thought you were using OCLP 0.5.0. When you are installing Ventura, are you absolutely certain that you are booting with an OC EFI generated by OCLP 0.6.8?

NP! Thanks for the help.

You just did by running the OCLP-Version command that I gave you. It reported 0.5.0.

Oh OK. I just don't understand that I was able to install macOS Ventura 13.6 yesterday using OCLP 0.6.8, but by using MA screwed the installation as mentioned earlier. Reinstalling failed many times now.

Is there a way to correct this?

 

[deeveedee]

@m4v3r1ck I think there are too many variables at play ...

• Create a USB installer for macOS Ventura 13.6
• Use OCLP 0.6.8 to "Build and Install Open Core" to the USB installer
• Boot your Mac with the USB installer (and continue booting with the USB installer during the entire installation and testing of Ventura)
• Perform a clean installation of Ventura 13.6 to your new SSD
• As the last step of the Ventura 13.6 installation (when prompted by the macOS installer), Migrate data/apps/settings from your Monterey Volume. Do NOT apply any post-install patches before the migration
• Use your USB installer to boot your newly installed/migrated 13.6
• Apply OCLP 0.6.8 post-install patches to 13.6 (it is Ok to have 0.6.8 post-install patches on your new Ventura volume and 0.5.0 post-install patches on your old Monterey volume)
• Continue to boot with the OC EFI on your USB installer as long as you are testing Ventura (do not boot with the existing OC EFI on your Monterey SSD)

If all this works, then you just need to test Monterey with OCLP 0.6.8. You can do this safely (without touching your old Monterey volume) by creating another APFS volume, install Monterey to the new APFS volume and migrate data/apps/settings from your old Monterey Volume to your new Monterey volume. Use OCLP 0.6.8 to patch your new Monterey volume.

There's more, but this is getting too long. I think you can figure out the rest.

 

[m4v3r1ck]

There's more, but this is getting too long. I think you can figure out the rest.

Thank you very much! I have a to-do-list to be done with & checked.

 

[rbart]

I have small question.
With OCLP 0.6.9n, on my iMac 17,1, I can't play DRM content in Safari from sources like MyCanal (France).
It's not crashing, but I get a black window after a couple of seconds of content playing.
I get an error about HDCP not compatible.
Is there any solution ?

 

[MacinMan]

I have small question.
With OCLP 0.6.9n, on my iMac 17,1, I can't play DRM content in Safari from sources like MyCanal (France).
It's not crashing, but I get a black window after a couple of seconds of content playing.
I get an error about HDCP not compatible.
Is there any solution ?

Since it's a localized source, it sounds like I don't think I can test it for you, but I will, if i can if it will work in the US. I have OCLP 0.6.9n installed to my Ventura external install for this iMac. So far, I haven't had any media issues.

 

[rbart]

Same issue with Disney+ (more international service)
Another precision about this DRM issue: I can use another browser like ARC without any issue (OCLP Ventura & Sonoma).
The problem only occurs with Safari.
It's not a big issue, but I just wanted to know if it's a known bug ?

 

[m4v3r1ck]

@m4v3r1ck I think there are too many variables at play ...

• Create a USB installer for macOS Ventura 13.6
• Use OCLP 0.6.8 to "Build and Install Open Core" to the USB installer
• Boot your Mac with the USB installer (and continue booting with the USB installer during the entire installation and testing of Ventura)
• Perform a clean installation of Ventura 13.6 to your new SSD
• As the last step of the Ventura 13.6 installation (when prompted by the macOS installer), Migrate data/apps/settings from your Monterey Volume. Do NOT apply any post-install patches before the migration
• Use your USB installer to boot your newly installed/migrated 13.6
• Apply OCLP 0.6.8 post-install patches to 13.6 (it is Ok to have 0.6.8 post-install patches on your new Ventura volume and 0.5.0 post-install patches on your old Monterey volume)
• Continue to boot with the OC EFI on your USB installer as long as you are testing Ventura (do not boot with the existing OC EFI on your Monterey SSD)

If all this works, then you just need to test Monterey with OCLP 0.6.8. You can do this safely (without touching your old Monterey volume) by creating another APFS volume, install Monterey to the new APFS volume and migrate data/apps/settings from your old Monterey Volume to your new Monterey volume. Use OCLP 0.6.8 to patch your new Monterey volume.

There's more, but this is getting too long. I think you can figure out the rest.

Starting fresh installation sequence.

Is my OCLP becoming a sinkhole... What the heck is happening?

Creating new USB installer:

First time seen error:

Reboot indexing:

mds_stores running high on CPU:

OCLP 0.6.8 message:

This is getting so far out of my own reach.

 

[deeveedee]

@m4v3r1ck Maybe there's a problem with the new SSD or USB thumb drive you're using. The steps in the procedure are solid.

 

[m4v3r1ck]

@m4v3r1ck Maybe there's a problem with the new SSD or USB thumb drive you're using. The steps in the procedure are solid.

I do NOT doubt your procedure, if my writing may have given you that impression, I apologize for that.

It's just reporting back after all the time you spend reading and giving me feedback. Also sharing my experience for the good of the MR community. I think there might have occurred a major glitch after the MA procedure.

I'll try again later after a fresh reboot using a different SSD and report back.

Enjoy your day!

 

[deeveedee]

@m4v3r1ck And I'm sorry I gave you the impression that I thought you doubted me. Takes way more than that to offend me. . Just keep reporting your findings and don't worry about what I think. You're doing great.

 

[MacinMan]

Same issue with Disney+ (more international service)
Another precision about this DRM issue: I can use another browser like ARC without any issue (OCLP Ventura & Sonoma).
The problem only occurs with Safari.
It's not a big issue, but I just wanted to know if it's a known bug ?

OK, I use some of those services, but I typically don't watch them in a browser. I use the mobile app, or app on a streaming box. I use safari mainly for creating accounts so I can use the icloud keychain password generator. Beyond that, I typically use Firefox, or Chrome for a more cross platform solution. I may prefer macOS for some things, but I like to try to keep what I use cross platform as much as possible as not to lock myself into one platform.