ok thanks a million mate. this is a SUCCESS !!!
the above procedure i done it before but with no luck. This time with more clear mind, although it still doesn't work out of the box, i added one more step which was the solution!
so a break down of the steps that worked for me:
step1: Make sure your efi can run macOS 12 Monterey at ivy bridge + a non AVG2 GPU.
step2: Download and add the
CryptexFixup.kext to kexts folder and config.plist.
step3: Add
CryptexFixup to the config.plist so that it loads.
step4: Add the boot-args below to the config.plist without delete any of the ones already there
-amd_no_dgpu_accel -cryptbeta amfi=0x80 ipc_control_port_options=0 amfi_get_out_of_my_way=1
step5: set csr-active-config to 03080000
step6: set SecureBootModel to Disabled
step7: set Dmgloading to Any
<!-- The Solution (at least for my case) -->
step8: If the SMBIOS used for the Monterey installation does not support Ventura, naturally it shouldn't since we are on Ivy Bridge, we must change to a Ventura compatible SMBIOS.
My SMBIOS was MacPro6,1 so i changed it to MacPro7,1. This is did via OCAT taking a backup of the whole folder before.
step9:reboot and start your computer from the USB installer. Once its starts up open Disk Utility and wipe clean where ever you're going to install to. Erase using apfs.
step10: Install macOS Ventura (Without step 8 i got a "This mac is not compatible with MacOS Ventura" or similar message)
<!-- Post install steps -->
step11: Login Ventura and download OCLP. Root Patch for dGPU
step12: Remove boot-arg -amd_no_dgpu_accel
step13: Mount the EFI of the disk that Ventura is installed on and completely delete folder "EFI". Unmount. Mount EFI from USB stick and copy/paste on a folder. Unmount. Mount the EFI of the disk that Ventura is installed on and copy paste the EFI from the USB
Post install notices/thoughts
- After the root patch i need two continuous reboots + 2 NVRAM resets in order to boot without getting stuck to Apple error(support.apple.com/mac/startup)
- I believe most of the above boot-args that we added can be avoided if we follow the suggestions of the
Ventura on Ivy bridge guide
- I don't see how you guys managed to finish installation without changing your SMBIOS.
Why i couldn't make it to ventura until today?
I made many many many attempts, I followed and done ALL the changes that the guide suggests.
The error i was getting (the libSystem.B.dylib one) i found it in 2 threads. Both were about installing Ventura on Vm. This leads only to one thought...
The guide says:
Add and enable both Booter Patches from OCLP's
Board-ID VMM spoof: "Skip Board ID check" and "Reroute HW_BID to OC_BID"
This way it skips board-id checks in macOS virtualizes the used board-id → Makes macOS "believe" it's running in a VM. This allows booting macOS with unsupported, native SMBIOS best suited for your CPU.
Conclusion should be that the VMM trick triggers the error.
I avoided that by using MacPro7,1 SMBIOS so the above patch is not necessary.
Isn't it though?
Should i go back to MacPro6,1?
Based on theory and ..THE Guide, i should. This means i must revert back to my previous SMBIOS settings and use the VMM spoofing Patches.
So i will update this as i go. For now i just want to enjoy my fresh cup of ventura.
cheers all, you've been wonderful as always.