macOS 13 Ventura on Unsupported Macs Thread

[fernando.c.neves]

Update OTA to Official macOS Ventura 13.1 - Brick my EFI - Build another EFI with OCLP 0.5.3 Official Release spoofed to MacBookPro14,1 from MacBookPro12,1 (My real Mac) - MacBook Pro Retina 13'' Early 2015.

Now system boot perfectly.



Everything is working like a charm.
Safari is fast! Play's Youtube Video's at 4k 60fps smooth.

No issues at all.

 

[iMac-Oldschool]

Hello, I've a problem with macos security response 13.2 (a), it fails to install. Here is the response in Terminal :

softwareupdate -ir

Software Update Tool



Finding available software

Downloading macOS Security Response 13.2 (a)

Downloading: 100.00%

Failed to download & prepare update: Error Domain=SUOSUErrorDomain Code=201 "La préparation de la mise à jour logicielle a échoué. Veuillez réessayer." UserInfo={NSLocalizedRecoverySuggestion=Une erreur est survenue lors du téléchargement des mises à jour sélectionnées. Vérifiez votre connexion à Internet puis réessayez., NSLocalizedDescription=La préparation de la mise à jour logicielle a échoué. Veuillez réessayer., NSUnderlyingError=0x6000027299e0 {Error Domain=SUMacControllerError Code=7740 "[SUMacControllerErrorPrepareFailed=7740] Failed to perform Prepare operation: [MobileSoftwareUpdateErrorDomain(MSU):56_1_NSPOSIXErrorDomain:2]" UserInfo={NSLocalizedDescription=La préparation de la mise à jour logicielle a échoué. Veuillez réessayer., SUMacControllerErrorIndicationsMask=0, NSDebugDescription=[SUMacControllerErrorPrepareFailed=7740] Failed to perform Prepare operation: [MobileSoftwareUpdateErrorDomain(MSU):56_1_NSPOSIXErrorDomain:2], NSUnderlyingError=0x600002738bd0 {Error Domain=MobileSoftwareUpdateErrorDomain Code=56 "Failed to stage splat boot objects in preboot" UserInfo={NSUnderlyingError=0x600002738e40 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory" UserInfo=0x6000029393c0 (not displayed)}, NSLocalizedDescription=Failed to stage splat boot objects in preboot, target_update=22D7750270d}}}}}

Same problem with my iMac 13,1 late 2012.
See post 35 on the new thread:

Apple Releases Rapid Security Response Update for macOS Ventura 13.2 Beta​

 

[binarysmurf]

I'm getting an intermittent error when I right-click and copy some text. This only started happening after I upgraded from 13.0.1 to 13.1 using OCLP 0.5.2. It's no big deal, but is there an easy fix?

 

[amaze1499]

FYI: OTA update to 22D5027d done using 0.5.3. No issues.

However trying to install macOS Security Response 13.2 (a)-22D7750270d fails repeatedly.

{"restore_payload_version":"22D7750270d","restore_type":"OTAUpdate","os_version":"22D5027d","itunes_version":"22D5027d","bug_type":"183","restore_error":"56","name":"iPhoneRestore"}
5544be00 XXXX>>>>>>>>>>>>>>>> main() started
5544be00 : setSystemTargetUUID will use / as the target
5544be00 : Found update container: LPAPFSContainer: AppleAPFSMedia, UUIDXXXX>>>>>>->>>>>54E9
5544be00 : Found update volume: LPAPFSVolume: Update, Mount: /System/Volumes/Update
5544be00 : Will open restore file at: /System/Volumes/Update/restore.log
45690e00 XXXX>>>>>>>>>>>>>>>> main() started
45690e00 : setSystemTargetUUID will use / as the target
45690e00 : Found update container: LPAPFSContainer: AppleAPFSMedia, UUIDXXXX>>>>>>-03D0-4F39-8AD1XXXX>>>>>54E9
45690e00 : Found update volume: LPAPFSVolume: Update, Mount: /System/Volumes/Update
45690e00 : Will open restore file at: /System/Volumes/Update/restore.log
45690e00 : Brain operations will run at their default(UTILITY) QOS
036f8000 : Running event handler at QoS 0x11
0377b000 : Running event handler at QoS 0x11
0377b000 : setSystemTargetUUID will use 00000000-0000-0000-0000XXXX>>>>>0000 for target UUID
0377b000 : Failed to find target media.
0377b000 : Did find: (

"LPMedia: EFI System Partition, UUIDXXXX>>>>>>>>>>>3EBB",
"LPAPFSPhysicalStore: Untitled 2, UUIDXXXX>>>>>>>>>>>C2E1",
"LPMedia: EFI System Partition, UUIDXXXX>>>>>>>>>>>A90D",
"LPMedia: External, Mount: /Volumes/External",
"LPAPFSContainer: AppleAPFSMedia, UUIDXXXX>>>>>>>>>>>54E9",
"LPPartitionMedia: SanDisk Ultra Fit Media",
"LPMedia: EFI System Partition, UUIDXXXX>>>>>>>>>>>65DC",
"LPMedia: Install macOS Ventura beta, Mount: /Volumes/Install macOS Ventura beta",
"LPAPFSVolume: Monterey - Data, Mount: /Volumes/Monterey - Data",
"LPAPFSVolume: Preboot, Mount: /System/Volumes/Preboot",
"LPAPFSVolume: Recovery, UUIDXXXX>>>>>>>>>>>5C5C",
"LPAPFSVolume: Ace Ventura - Data, Mount: /System/Volumes/Data",
"LPAPFSVolume: Monte Rey, Mount: /Volumes/Monte Rey",
"LPAPFSVolume: Update, Mount: /System/Volumes/Update",
"LPAPFSVolume: Ace Ventura, UUIDXXXX>>>>>>->>>>>D007",
"LPAPFSVolume: VM, Mount: /System/Volumes/VM",
"LPAPFSVolume: Ace Ventura, Mount: /",
"LPPartitionMedia: Apple UDIF read-only Media",
"LPMedia: EFI System Partition, UUIDXXXX>>>>>>->>>>>2353",
"LPMedia: Shared Support, Mount: /Volumes/Shared Support"
)
0377b000 : mountAndGetUpdateVolumeMountPoint update volume mount failed with error: (null)
0377b000 XXXX>>>>>>>>>>>>>>>> event recorder update volume mount point: (null), NVRAM shadow path: /System/Volumes/Update/nvram.plist
0377b000 : initializing new event recorder with options: (null)
0377b000 : start
0377b000 : NVRAM dictionary from IODeviceTree will be used since dictFileSystem is nil

0377b000 : Permanent update volume present..supportDir will be placed there
0377b000 : -[UMEventRecorder _supportDirectoryWithMountPoint:]: mountPoint is nil...Using /System/Volumes/Update as the mountPoint
0377b000 : NVRAM variable ota-uuid has unexpected value '(null)'
0377b000 : NVRAM variable ota-submission-url has unexpected value '(null)'
0377b000 : NVRAM variable ota-os-version has unexpected value '(null)'
0377b000 : NVRAM variable ota-context has unexpected value '(null)'

 

[coolio2004]

Exactly same issue here. See my previous post 2587.

Strange - with oclp 0.53 final efi boot no problems.

 

[vendini]

Strange - with oclp 0.53 final efi boot no problems.

It seems to be model dependant. No problems with my MBP 13.2 (13" 2016) either. But with my iMac, it's impossible to install the macOS Security Response 13.2 (a). It fails to install repeatedly, even if the internet connection is perfect. It's the same with or without post-install patches.

 

[Tockman]

It seems to be model dependant. No problems with my MBP 13.2 (13" 2016) either. But with my iMac, it's impossible to install the macOS Security Response 13.2 (a). It fails to install repeatedly, even if the internet connection is perfect. It's the same with or without post-install patches.

Did you try to reboot after the install attempt?

 

[zfrogman]

Hello all,
Running very smoothly on installed Ventura 13.1 update with Opencore v.0.5.2. All apps (MS Office, Adobe Acrobat Photoshop, etc.) opening and working even better or more quickly than 13.0x for some reason. All good. What an amazing job the Opencore group has done to keep our reliable "old Betsies" running as smoothly as the first time out of the box.... Kudos and more to the devs.

 

[Larsvonhier]

To all cMP4,1 and 5,1 owners who miss BT on Ventura 13.x (even when using upgraded BRCM combo module like the BCM94360CD):

The question came up a few posts earlier here if re-connecting the USB data lines from Broadcom combo wifi/BT module might re-enable it for correct driver usage in Ventura.
I tried it today and yes, successfully have all the functionality back like Airdrop and connection of wireless keyboard / trackpad etc. - see screenshot.

What I did as a preliminary solution: I cut a standard USB cable (A to B style) and connected the green wire of the A-side to the BRCM module´s USB+ and the white wire to USB- that before (as a working solution up to Monterey) went to the old 4pin BT connector on the MP4,1/5,1 mainboard. I then plugged in the type A connector of the cable into a 2.0 hub to one of the external USB jacks.

Next step is to try to strap the USB hub to the internal conn. on the mainboard to see if that would also work (making a more permanent routing of cables internal-only then possible).

Update: It is also working with the internal USB+ and USB- data signals from the 4pin socket on the mainboard!
Seems to be an appropriate Xmas project to do some miniature piggy-back PCB with a USB hub chip and additional 3.3V to 5V converter for external port usage. The idea is to provide 2 extra USB 2.0 ports for wired keyboards and mice for i.e. boot selection and other purposes... Stay tuned for results!

 

[vendini]

Did you try to reboot after the install attempt?

Yes, I did, without success

 

[Tockman]

Yes, I did, without success

You mean you couldn't boot at all or just finish installing update?

 

[PeterHolbrook]

It is also working with the internal USB+ and USB- data signals from the 4pin socket on the mainboard!
Seems an appropriat Xmas project to do some miniature piggy-back PCB with a USB hub chip and additional 3.3V to 5V converter for external port usage. The idea is to provide 2 extra USB 2.0 ports for wired keyboards and mice for i.e. boot selection and other purposes... Stay tuned for results!

That's great. Can you provide one or more photos and/or schematics of your working BT custom cabling solution?

 

[vendini]

You mean you couldn't boot at all or just finish installing update?

I could install Ventura 13.2 b1 and the post install patches, but it's impossible to install the small macOS security response. It's always the same error message : "Failed to prepare the software update. Please try again. An error occurred while downloading the selected updates. Please check your internet connection and try again". I'm able to reboot, everything is working, except this security update.

 

[Tockman]

I could install Ventura 13.2 b1 and the post install patches, but it's impossible to install the small macOS security response. It's always the same error message : "Failed to prepare the software update. Please try again. An error occurred while downloading the selected updates. Please check your internet connection and try again". I'm able to reboot, everything is working, except this security update.

So you're a lucky man! 'Cause I can see here a plenty of guys who fell down into a boot loop after dealing with that.

Rapid Security Response with legacy Macs · Issue #1019 · dortania/OpenCore-Legacy-Patcher

With the initial beta of macOS 13.2 (22D5027d), Apple has seeded a test update using the new Rapid Security Response System, generally abbreviated as RSR. RSR relies on the Cryptex system, where co...

github.com

 

[crystall1nedev]

For those who wanna try it I took the kernel from ventura build 22A5311f and replaced it with the Mach kernel that ships in 13.0.1. Full acceleration on 320m and 5770 not sure about other chips..

Please don’t spread misinformation to such a large userbase. Swapping the kernel would have had no effect as the kexts are still not there and not compatible.

 

[alphascorp]

To all cMP4,1 and 5,1 owners who miss BT on Ventura 13.x (even when using upgraded BRCM combo module like the BCM94360CD):

The question came up a few posts earlier here if re-connecting the USB data lines from Broadcom combo wifi/BT module might re-enable it for correct driver usage in Ventura.
I tried it today and yes, successfully have all the functionality back like Airdrop and connection of wireless keyboard / trackpad etc. - see screenshot.

What I did as a preliminary solution: I cut a standard USB cable (A to B style) and connected the green wire of the A-side to the BRCM module´s USB+ and the white wire to USB- that before (as a working solution up to Monterey) went to the old 4pin BT connector on the MP4,1/5,1 mainboard. I then plugged in the type A connector of the cable into a 2.0 hub to one of the external USB jacks.

Next step is to try to strap the USB hub to the internal conn. on the mainboard to see if that would also work (making a more permanent routing of cables internal-only then possible).

Update: It is also working with the internal USB+ and USB- data signals from the 4pin socket on the mainboard!
Seems to be an appropriate Xmas project to do some miniature piggy-back PCB with a USB hub chip and additional 3.3V to 5V converter for external port usage. The idea is to provide 2 extra USB 2.0 ports for wired keyboards and mice for i.e. boot selection and other purposes... Stay tuned for results!

Hi @Larsvonhier
I thought about trying that this but I haven't had the time yet, you were faster than me, bravo!
I had also thought of trying to connect to pins 27 or 33 (USB Data-) and 28 or 34 (USB Data+) of the 44 pin connector on the backplane that comes from the front panel board, in order to stay inside the Mac Pro.
(It is on this connector that I connected to get 5V to power a small fan placed on the Northbridge.)

 

[Larsvonhier]

That's great. Can you provide one or more photos and/or schematics of your working BT custom cabling solution?

Yes, of course I´ll be happy to provide more detailed info, pls. give me 1-2 days... ;-)

 

[Larsvonhier]

Hi @Larsvonhier
I thought about trying that this but I haven't had the time yet, you were faster than me, bravo!
I had also thought of trying to connect to pins 27 or 33 (USB Data-) and 28 or 34 (USB Data+) of the 44 pin connector on the backplane that comes from the front panel board, in order to stay inside the Mac Pro.

View attachment 2130378

Now the good thing is that we can stay inside with the complete cabling by using the "original" two pins D+/D- from the old BT socket...

 

[vendini]

So you're a lucky man! 'Cause I can see here a plenty guys who fell down into a boot loop after dealing with that.

Rapid Security Response with legacy Macs · Issue #1019 · dortania/OpenCore-Legacy-Patcher

With the initial beta of macOS 13.2 (22D5027d), Apple has seeded a test update using the new Rapid Security Response System, generally abbreviated as RSR. RSR relies on the Cryptex system, where co...

github.com

Yes, you are right, I know it. It’s just irritating for the mind 😉 but thank you for the link, it makes things more clear!

 

[alphascorp]

Now the good thing is that we can stay inside with the complete cabling by using the "original" two pins D+/D- from the old BT socket...

@Larsvonhier, when you refer to the 4-pin connector, do you mean the connector of the original Bluetooth card?
Because Data- and Data+ of my BCM94360CD are already connected on this 4 pin connector but Bluetooth does not work for me.

 

[Larsvonhier]

That's great. Can you provide one or more photos and/or schematics of your working BT custom cabling solution?

Here is a quick draft:
Red and green paths are alternatives, only hook up one or the other USB data source!
As most USB hubs require +5V supply, the catch now is that at least that has to be taken from **somewhere** inside off-mainboard or from std. USB externally.
As said, that is a good Xmas project to get all on one little nifty PCB! Stay tuned... ;-)

 

[Larsvonhier]

@Larsvonhier, when you refer to the 4-pin connector, do you mean the connector of the original Bluetooth card?
Because Data- and Data+ of my BCM94360CD are already connected on this 4 pin connector but Bluetooth does not work for me.

View attachment 2130381

Yes, the trick is to route it through a USB hub! Otherwise, it won´t work - that is new behaviour in Ventura.

 

[alphascorp]

Yes, the trick is to route it through a USB hub! Otherwise, it won´t work - that is new behaviour in Ventura.

Put a USB hub, why didn't I think of it...
As for the 5V power supply, it can easily be obtained on the 44-pin connector I mentioned above (I think 26 or 32 for +5v and 29 or 36 for GND) but it remains to be checked...

 

[Larsvonhier]

Put a USB hub, why didn't I think of it...
As for the 5V power supply, it can easily be obtained on the 44-pin connector I mentioned above (I think 26 or 32 for +5v and 29 or 36 for GND) but it remains to be checked...

Good info, as I only found 3,3V so far...

 

[TOM1211]

installed security update Ventura security update on mid 2014 rebooted normally then slowed to a crawl completely unusable for a few minutes like it had stalled but it hasn’t I guess it looks like a half patched system depending on what it updates in the smaller patches oclp popped up saying needed to patch even though display card still showed correctly patch reboot and working fine on oclp 5.4n probably better to unpatch first I would think ? .