fusion71au Posted February 17, 2023 Share Posted February 17, 2023 (edited) This is a summary of the process used to clean install macOS Ventura 13.2 on my legacy BIOS (non UEFI, no hardware NVRAM) based system: a Gigabyte P55A-UD3/Intel i5-750/ATI HD 5770 or desktop 2 in my signature. Thanks in large part to @pac-man and @TheBloke for discovering the msu-product-url NVRAM key requirement for Big Sur, the same method also works in Monterey and Ventura. I highly recommend reading @khronokernel's explanation for the various patches used in OpenCore Legacy Patcher and also the specific changes needed to boot Ventura. Thanks to him and all the OpenCore/OCLP developers that keep our ancient hacks running. Pre-requisites 1. Ventura USB installer created with Apple’s createinstallmedia command line utility. 16GB or larger size preferred. 2. Plist editor eg XCODE, PlistEDPlus for easy editing of OC config.plist 3. EFI Agent or similar app to easily mount EFI partitions 4. OpenCore Legacy Patcher (OCLP) 0.6.1 or newer 5. Working OC 0.8.8+ EFI to boot the above USB Installer. I based my config.plist on one generated with OCLP 0.6.1 (using the Mac SMBIOS most closely matching my hardware ie iMac11,3). Note Kernel/Add/CryptexFixup is enabled to provide “back door” non-AVX2.0 CPU support through Rosetta dyld shared cache. Attached is the EFI folder for the Gigabyte P55A-UD3:OC 0.8.9 for iMac11,3 6. Completely disable SIP and AMFI (I used csr-active-config=EF0F0000, amfi=0x80 in config.plist boot-args) 7. A “rescue” macOS eg High Sierra or newer to determine the Ventura volume’s UUID and to mount its Preboot volume to copy files back and forth. Note: It sometimes helps to show hidden files in macOS Finder by pressing <Windows Key><Shift><.> simultaneously. Overview of Clean installation process for Ventura 1. Clean APFS volume to install Ventura. Use Disk Utility to erase whole disk (or partition) and format as APFS. Use terminal to determine target volume’s UUID… Spoiler iMac:~ fusion71au$ diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *120.0 GB disk0 1: DOS_FAT_32 SYSTEM 104.9 MB disk0s1 2: Windows_NTFS WIN7_X64SSD 119.9 GB disk0s2 /dev/disk1 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *2.0 TB disk1 1: EFI EFI 209.7 MB disk1s1 2: Microsoft Basic Data DATA_TSH 1.7 TB disk1s2 3: Apple_HFS Macintosh HD 133.6 GB disk1s3 4: Apple_Boot Recovery HD 650.0 MB disk1s4 5: Microsoft Reserved 134.2 MB disk1s5 6: Microsoft Basic Data WIN10 133.5 GB disk1s6 7: Windows Recovery 564.1 MB disk1s7 /dev/disk2 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *320.1 GB disk2 1: EFI EFI 209.7 MB disk2s1 2: Apple_APFS Container disk4 59.9 GB disk2s2 3: Microsoft Basic Data MACRIUM Backups 166.4 GB disk2s3 4: Apple_APFS Container disk3 53.8 GB disk2s4 5: Linux Swap 4.3 GB disk2s5 6: Microsoft Basic Data 314.6 MB disk2s6 7: Linux Filesystem 35.1 GB disk2s7 /dev/disk3 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +53.8 GB disk3 Physical Store disk2s4 1: APFS Volume macOS_13 954.4 KB disk3s1 /dev/disk4 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +59.9 GB disk4 Physical Store disk2s2 1: APFS Volume 15.3 GB disk4s1 2: APFS Volume macOS_11 - Data 30.0 GB disk4s2 3: APFS Volume Preboot 1.1 GB disk4s3 4: APFS Volume Recovery 620.3 MB disk4s4 5: APFS Volume VM 1.1 MB disk4s5 6: APFS Volume Update 1.1 MB disk4s6 /dev/disk5 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *31.6 GB disk5 1: EFI EFI 209.7 MB disk5s1 2: Apple_HFS Install macOS Ventura 31.3 GB disk5s2 iMac:~ fusion71au$ diskutil info disk3s1 | grep UUID Volume UUID: 7CA4AD3E-3AB0-4BDF-BF0A-29DE99DF1FCD Disk / Partition UUID: 7CA4AD3E-3AB0-4BDF-BF0A-29DE99DF1FCD Mount your OC EFI Use a plist editor to edit the OC config.plist: under /NVRAM/Add/7C436110-AB2A-4BBB-A880-FE41995C9F82, add a new key, msu-product-url ,Type=string, Value=msu-product-url://UUID/macOS%20Install%20Data where UUID is the Volume UUID of the Ventura target volume Spoiler For upgrade installs of Catalina or newer, the UUID of the OS volume with the -Data suffix should be used Save the plist 2. Boot with OC to Ventura USB Installer… Choose Install macOS Ventura entry from OC menu Select Install macOS Ventura from the macOS Installer main screen Choose the clean Ventura volume created from step 1 as the target install disk eg “macOS_13” Installation phase 1 will proceed, copying files to “macOS Install Data” folder, then reboot with approx 12-14 minutes remaining shown Spoiler 3. Boot to macOS Installer from OC menu. This second installation phase extracts compressed files from the first phase and prepares a Preboot volume. Apple removed non-AVX2.0 support for Intel CPUs (pre Haswell) in Ventura so in order to boot macOS 13 on legacy Intel CPUs, we need to install Rosetta/Apple Silicon’s dyld shared cache through a backdoor method —> this is the job of CryptexFixup.kext. Unfortunately on my system, this second installation phase never completes to 100% (“An error occurred preparing the software update” message appears with less than a minute remaining!) with CryptexFixup.kext enabled. All is not lost however - if we mount the Preboot volume, we find that CryptexFixup has already extracted the dyld shared cache (4.32GB os.dmg file) that is required to boot the full OS later —> can be copied eg to your installer USB or “rescue” macOS partition. In the screenshots below, I have chosen to reboot into my High Sierra “rescue” OS to mount Ventura’s Preboot volume and copy the 4.32GB OS.dmg file over to the Installer USB. I also mounted the OC EFI partition to edit the config.plist to temporarily disable CryptexFixup.kext for the next 2 boots into the macOS Installer. Use the apple menu to reboot again… Spoiler 4. At the OC menu, choose macOS installer again. This time (with CryptexFixup.kext disabled), the second installation phase completes to 100% without errors, rebooting automatically… Spoiler 5. At the OC menu, choose macOS installer to start the third installation phase. You may see messages from patchd copying files to create the root volume, then the ramrod process finally sealing the root volume. The system automatically reboots after some time… Spoiler 6. At the OC menu, select to boot your rescue macOS again. We need to replace the 1.55GB os.dmg with the saved 4.32GB one for our legacy non AVX2.0 CPU to boot the newly sealed Ventura volume. In the screenshots below, I have mounted Ventura’s Preboot volume from High Sierra to copy over the 4.32GB os.dmg. Also mounted the OC EFI to edit config.plist to re-enable CryptexFixup kext injection… Use the apple menu to reboot again… Spoiler 7. At the OC menu, choose to boot the Ventura volume (in this eg, shows as macOS_13 -Data) to start the fourth, relatively short installation phase, followed by the system automatically rebooting Spoiler 8. At the OC menu, choose the finalised Ventura volume (in this eg, shows as macOS_13 -Data -Data) to start the final fifth installation phase and setup a new user. Note you can change the Ventura volume name with Disk Utility. The OC main menu name for the Ventura volume can also be changed by copying the hidden text files .contentDetails &/or .disk_label.contentDetails (in /Preboot/System/Library/CoreServices folder) to your desktop for editing with a text editor, then copying the edited files back with the sudo cp terminal command… Spoiler 9. Apply post install OCLP 0.6.1 root patches for legacy Atheros wireless and AMD Terascale 2 graphics patches for my ATI HD5770 —> reboot to fully working system! Spoiler Edited February 18, 2023 by fusion71au formatting 7 Link to comment Share on other sites More sharing options...
MacNB Posted February 17, 2023 Share Posted February 17, 2023 Nice write up. Thanks. 3 hours ago, fusion71au said: This is a summary of the process used to clean install macOS Ventura 13.2 on my legacy BIOS (non UEFI, no hardware NVRAM) based system: a Gigabyte P55A-UD3/Intel i5-750/ATI HD 5770 or desktop 2 in my signature. Thanks in large part to @pac-man and @TheBloke for discovering the msu-product-url NVRAM key requirement for Big Sur, the same method also works in Monterey and Ventura. Interesting. On my Legacy Hack 2 (Dell 530), I Cloned my Catalina to a new APFS Container and "upgraded" the clone to Big Sur and had to use msu-product-url NVRAM trick. But I did a clean install of Monterey on another APFS Container and did not use that trick and Monterey installed fine. 3 hours ago, fusion71au said: 8. At the OC menu, choose the finalised Ventura volume (in this eg, shows as macOS_13 -Data -Data) to start the final fifth installation phase and setup a new user. Note you can change the Ventura volume name with Disk Utility. The OC main menu name for the Ventura volume can also be changed by copying the hidden text files .contentDetails &/or .disk_label.contentDetails (in /Preboot/System/Library/CoreServices folder) to your desktop for editing with a text editor, then copying the edited files back with the sudo cp terminal command… For completeness, the label images files (.disk_label & .disk_label_2x) should be changed too. You can use the macOS BLESS command. This is what I did recently when I upgraded a cloned High Sierra (named HS-HDD) to Mojave on an SSD: # Change volume label using BLESS command MacNB@iMac-530-BS ~ % cd /volumes/preboot/D265E848-D8BE-4762-85F3-CD1D03C4E025/system/library/coreservices MacNB@iMac-530-BS coreservices % sudo bless --folder . --label "Mojave SSD" MacNB@iMac-530-BS coreservices % printf "Mojave SSD" | sudo tee .disk_label.contentDetails; echo Mojave SSD MacNB@iMac-530-BS coreservices % printf "Mojave SSD" | sudo tee .contentDetails; echo Mojave SSD MacNB@iMac-530-BS coreservices $ sudo chown 0:0 .disk* MacNB@iMac-530-BS coreservices $ sudo chown 0:0 .con* MacNB@iMac-530-BS coreservices $ Some clever folks can easily turn the above commands into a script : chlabel <UUID> <label> 1 1 Link to comment Share on other sites More sharing options...
ilovefifa Posted March 8, 2023 Share Posted March 8, 2023 @fusion71au Hi there, i need your help, i have a HD6770,similar to HD 5770, after finished OCLP patched,Ventura Run through all processes，finally reboot. i think the question is my OC NVRAM is incorrect setting .because my other vga card GT1030 and GTX1050 able boot to Ventura with full acceleration. would you please give me a hand thanks EFI.zip Juniper6770.rom SSDT-GPU-SPOOF.aml Link to comment Share on other sites More sharing options...
ovidoi Posted April 2, 2023 Share Posted April 2, 2023 Hi, good work and thanks. For me work's for Dell Alienware M17xR3 with Intel HD3000, but I have an issue with amd radeon hd6850m with patched OCLP 06x, after patching and restart and boot verbose, until slider and apple logo system is get blocked "ioconsoleusers xxxxxxxx" how to patch or spoof my amd card, any help please, I see another Ventura users to patch an inferior amd card, now use hd3000. Thank you! Link to comment Share on other sites More sharing options...
analise Posted April 19, 2023 Share Posted April 19, 2023 Hi, great job here. I tried my self make a new install of Ventura, but in the first phase it always stops at 12 minutes to go with this error "An error occurred loading the update". Does anyone have a clue? Any help would be great, thanks Link to comment Share on other sites More sharing options...
ilovefifa Posted May 4, 2023 Share Posted May 4, 2023 @analisemake ventura install USB by OCLP 1 Link to comment Share on other sites More sharing options...
ilovefifa Posted May 12, 2023 Share Posted May 12, 2023 Hi there, HD5770 working now and very good.HD6770 still reboot again and again 1 Link to comment Share on other sites More sharing options...
datafeedexpert Posted May 12, 2023 Share Posted May 12, 2023 1 hour ago, ilovefifa said: Hi there, HD5770 working now and very good.HD6770 still reboot again and again Can you Please share your EFI Here ....? Link to comment Share on other sites More sharing options...
ilovefifa Posted May 12, 2023 Share Posted May 12, 2023 Patched Ventura by OCLP0.6.2 817656068_H170-HD3HD5770OC0.8.8Ventura.zip 1 Link to comment Share on other sites More sharing options...
oSxFr33k Posted June 16, 2023 Share Posted June 16, 2023 (edited) On 2/17/2023 at 7:52 AM, MacNB said: Nice write up. Thanks. Interesting. On my Legacy Hack 2 (Dell 530), I Cloned my Catalina to a new APFS Container and "upgraded" the clone to Big Sur and had to use msu-product-url NVRAM trick. But I did a clean install of Monterey on another APFS Container and did not use that trick and Monterey installed fine. For completeness, the label images files (.disk_label & .disk_label_2x) should be changed too. You can use the macOS BLESS command. This is what I did recently when I upgraded a cloned High Sierra (named HS-HDD) to Mojave on an SSD: # Change volume label using BLESS command MacNB@iMac-530-BS ~ % cd /volumes/preboot/D265E848-D8BE-4762-85F3-CD1D03C4E025/system/library/coreservices MacNB@iMac-530-BS coreservices % sudo bless --folder . --label "Mojave SSD" MacNB@iMac-530-BS coreservices % printf "Mojave SSD" | sudo tee .disk_label.contentDetails; echo Mojave SSD MacNB@iMac-530-BS coreservices % printf "Mojave SSD" | sudo tee .contentDetails; echo Mojave SSD MacNB@iMac-530-BS coreservices $ sudo chown 0:0 .disk* MacNB@iMac-530-BS coreservices $ sudo chown 0:0 .con* MacNB@iMac-530-BS coreservices $ Some clever folks can easily turn the above commands into a script : chlabel <UUID> <label> Have you ever managed to install Ventura on your Acer Laptop i5-440m? I have an Asus G51JX that I updated the processor from the i7-720M to the i7-920XM gets kind of hot but cannot get through the boot stage stops and never moves forward. I took my real MacBookPro6,2 installed Ventura using OCLP and Post Installs Nvidia tesla drivers works like a charm even gets the old legacy leopard initial login with the window that moves like a Cube I miss that. I took out that SSD and put into the G51JX made some changed to the config now trying to boot the Asus Laptop. I even have a good DSDT with all edits that EmilyDinesh from osxlatitude threads helped me eons ago. Edited June 16, 2023 by oSxFr33k Link to comment Share on other sites More sharing options...
MacNB Posted June 17, 2023 Share Posted June 17, 2023 18 hours ago, oSxFr33k said: Have you ever managed to install Ventura on your Acer Laptop i5-440m? I have an Asus G51JX that I updated the processor from the i7-720M to the i7-920XM gets kind of hot but cannot get through the boot stage stops and never moves forward. I took my real MacBookPro6,2 installed Ventura using OCLP and Post Installs Nvidia tesla drivers works like a charm even gets the old legacy leopard initial login with the window that moves like a Cube I miss that. I took out that SSD and put into the G51JX made some changed to the config now trying to boot the Asus Laptop. I even have a good DSDT with all edits that EmilyDinesh from osxlatitude threads helped me eons ago. No sorry. My Acer with i430M is confined in my Hackintosh Museum Cabinet and occasionally powered on to recharge the battery. If your Asus laptop does not have UEFI then you will need to install OC Duet (a.k.a Legacyboot in the OC's Utilities Folder) to boot anything that's EFI based. Link to comment Share on other sites More sharing options...
oSxFr33k Posted June 18, 2023 Share Posted June 18, 2023 (edited) On 6/17/2023 at 10:45 AM, MacNB said: No sorry. My Acer with i430M is confined in my Hackintosh Museum Cabinet and occasionally powered on to recharge the battery. If your Asus laptop does not have UEFI then you will need to install OC Duet (a.k.a Legacyboot in the OC's Utilities Folder) to boot anything that's EFI based. Yes all that is done it just stopes here: Will Edit post in a whilw with photo. It boots and stops nothing happens verbose mode last message is about USB EH01 and EH02 something Bios I know they are renamed in DSDT and I have CrytpexFixup. DSDT was created centuries ago all fixes in place. DO you use VirtualSMC or FakeSMC since it older hardware? Actually people running Core2Duo on OCLP Ventura, not even i7 yet and our Laptop is first generation i7. I have a real MacPro6,2 with i7-640M and it installed and running flawlessly Ventura, same graphics card to Nvidia GTX 330M. I never see the graphics driver Tesla being loaded is this possibly the hang up or the SSD boot not starting or both? Also uploaded my Config and Debug log. config.plist.zip opencore-2023-06-18-215324.txt.zip Edited June 18, 2023 by oSxFr33k upload config file Link to comment Share on other sites More sharing options...
MacNB Posted June 18, 2023 Share Posted June 18, 2023 21 hours ago, oSxFr33k said: Yes all that is done it just stopes here: Will Edit post in a whilw with photo. It boots and stops nothing happens verbose mode last message is about USB EH01 and EH02 something Bios I know they are renamed in DSDT and I have CrytpexFixup. DSDT was created centuries ago all fixes in place. DO you use VirtualSMC or FakeSMC since it older hardware? Actually people running Core2Duo on OCLP Ventura, not even i7 yet and our Laptop is first generation i7. I have a real MacPro6,2 with i7-640M and it installed and running flawlessly Ventura, same graphics card to Nvidia GTX 330M. I never see the graphics driver Tesla being loaded is this possibly the hang up or the SSD boot not starting or both? Also uploaded my Config config.plist.zip 6.42 kB · 0 downloads One thing you have to remember is that OCLP was designed for real Mac's and not hackintosh's and so it's not obvious what Post install Root patches it is applying to your Hackintosh. Even if your Hack appears to be similar to a real macbook6,2 it is not of course. Your config.plist file is OCLP generated file and it has been generated for a real MacBook and for your Hack which has subtly different H/W. I do not have great experience of using OCLP and have so far stayed at Monterey because I can configure OC without OCLP as it does not need Post install Root parches. I do not use VirtualSMC but FakeSMC because the latter works with iStat App and the former does not. That is not your problem. You don't see the Tesla driver being loaded because the hang happens before it gets that far. There appears to be a "hang" and not a panic. Your DSDT.aml file is not enabled to be loaded by OC in your config.plist (probably because of OCLP does not load any DSDT's for a real Mac). Also, you could try setting Root::UEFI::Quirks::ReleaseUsbOwnership = TRUE in your config.plist and see if boot progresses further. 1 Link to comment Share on other sites More sharing options...
oSxFr33k Posted June 18, 2023 Share Posted June 18, 2023 (edited) 5 hours ago, MacNB said: One thing you have to remember is that OCLP was designed for real Mac's and not hackintosh's and so it's not obvious what Post install Root patches it is applying to your Hackintosh. Even if your Hack appears to be similar to a real macbook6,2 it is not of course. Your config.plist file is OCLP generated file and it has been generated for a real MacBook and for your Hack which has subtly different H/W. I do not have great experience of using OCLP and have so far stayed at Monterey because I can configure OC without OCLP as it does not need Post install Root parches. I do not use VirtualSMC but FakeSMC because the latter works with iStat App and the former does not. That is not your problem. You don't see the Tesla driver being loaded because the hang happens before it gets that far. There appears to be a "hang" and not a panic. Your DSDT.aml file is not enabled to be loaded by OC in your config.plist (probably because of OCLP does not load any DSDT's for a real Mac). Also, you could try setting Root::UEFI::Quirks::ReleaseUsbOwnership = TRUE in your config.plist and see if boot progresses further. Very true I took the config file and a base starting point then modified it for the PC hack, although I left all the kernel patching in place under section Kernel/Patch I wonder if something there is causing the hang I will trial and error disable each one and enable one at a time to see. I stopped loading DSDT.aml because it did not make a difference I had the same results. I attached config and a debug file, maybe after you replied? Not sure why [EB] shows up at the end of the file again when it usually starts the process and not ends unless when I forced powered it off? The UEFI/Quirk didn't seem to help but I think that should be enabled according to Dortania guide? I don't know if that guide is updated for Ventura is there another source with a more updated guide? Edited: Normally that’s what I do as you said install it native and then patch it as necessary but being this laptop is very old. I thought this might work this way and you know what I’m gonna go back and install it fresh and see if I can boot it before it gets patched. I thought the bulk of OCLP patching normally only patches the graphic drivers and frameworks, and most times everything is installed in Library/Extensions but in this case the Nvidia Tesla drivers installed in System/library/extensions for real MacBookPro6,2 and not sure how it was able to install into a read only image? How would you patch without OCLP for graphics drivers framework files etc? Edited June 19, 2023 by oSxFr33k Link to comment Share on other sites More sharing options...
MacNB Posted June 19, 2023 Share Posted June 19, 2023 (edited) 10 hours ago, oSxFr33k said: and not sure how it was able to install into a read only image? How would you patch without OCLP for graphics drivers framework files etc? That's all done via post-install Root patches Option. That's one of the "issues" with OCLP...it's all hidden behind the App...unless you are willing to learn to read the source code of the app to find out how it works. I gave up trying to understand it to patch without OCLP. Sorry I can't help. EDIT: Try this thread for hints. Edited June 19, 2023 by MacNB 1 Link to comment Share on other sites More sharing options...
mrmacdi2 Posted September 29, 2023 Share Posted September 29, 2023 On 2/17/2023 at 12:27 PM, fusion71au said: Attached is the EFI folder for the Gigabyte P55A-UD3:OC 0.8.9 for iMac11,3 Hi, thanks for your guide! Are all kexts should be used? I have a similar system, except MB model is UD4, but I use just a few kexts in Monterey and curious if Ventura is so different. I have CPU PM working without AppleIntelCPUPowerManagement.kext and AppleIntelCPUPowerManagementClient.kext at least it drops and rises freq according to utilization. These kext are in question. Quote AppleIntelCPUPowerManagement.kext AppleIntelCPUPowerManagementClient.kext ASPP-Override.kext AutoPkgInstaller.kext BlueToolFixup.kext Bluetooth-Spoof.kext CatalinaBCM5701Ethernet.kext corecaptureElCap.kext CSLVFixup.kext FeatureUnlock.kext HWInfo.kext IntelCPUMonitor.kext IO80211ElCap.kext RestrictEvents.kext RSRHelper.kext Thanks! Link to comment Share on other sites More sharing options...
mrmacdi2 Posted October 1, 2023 Share Posted October 1, 2023 What about FileVault? Is it working after running OCLP? I've had issues turning it on again after OCLP. Link to comment Share on other sites More sharing options...
Recommended Posts