SSDTTime VS MountEFI

Build SSDT-EC, SSDT-USBX, SSDT-XOSI, SSDT-PLUG, and SSDT-HPET from SSDTTime instead of manually https://github.com/corpnewt/SSDTTime

I'm trying to do a fresh install of Ventura. I tried using SSDTTime from my Catalina at first, only to discover that the option to dump DSDT is disabled by design because that'll not give me the unadulterated DSDT which makes sense.

Precisely, I went through the guide once more, discovered some new tools (like USBToolBox for example) then I did USB mapping + SSDTs (using SSDTTime) by hand (I was not sure that I did them properly in the first place, 3 years ago). Then with those clean SSDTs & kext, I used my old EFI and OCAT to merge everything together. Double checked everything at the end just to be sure that I did not forget a thing and that OCAT did not mess up anything.

I couldn't get past this point in mine without running https://github.com/corpnewt/SSDTTime and enabling `SetupVirtualMap` in Booter Quirks

It's a must though. Every PC is different, even 2 identical models might not have the same ACPI tables.. I would Start here.. There's only a few things you'll really need, especially on these machines. While there's many methods, a clean install of windows NOT booted through OpenCore, using SSDTime is the easiest for most.

I built my own SSDTs using SSDTTime.

OpenCore 0.8.7 / Dumping DSDT use SSDTTime for generate ACPI Tables / Use genSMBIOS for generate MLB (Board Serial), ROM (Mac Address), SystemSerialNumber (Serial), SystemUUID (SmUUID)

[1]: https://www.youtube.com/watch?v=DhN35HNsYDg [2]: https://dortania.github.io/Getting-Started-With-ACPI/ssdt-methods/ssdt-long.html [3]: https://dortania.github.io/Getting-Started-With-ACPI/ssdt-methods/ssdt-easy.html [4]: https://dortania.github.io/Getting-Started-With-ACPI/ssdt-methods/ssdt-easy.html#running-ssdttime [5]: https://github.com/corpnewt/SSDTTime [6]: https://dortania.github.io/Getting-Started-With-ACPI/Universal/ec-methods/manual.html#pnp0c09-already-has-an-sta-method

try mapping usb drive on windows first using USBToolBox as USBInjectAll isn't fully working anymore on Monterey. Also I suggest creating your own SSDT/acpi patches via SSDTTime.

If so, switch back to AppleALC and add SSDT-HPET.aml with the patches in the patches.plist generated in SSDTTime (https://github.com/corpnewt/SSDTTime).

You need to manually copy the EFI folder from your pendrive to your system's EFI partition. Use MountEFI made by u/CorpNewt to mount your system's EFI partition.

Use MountEFI, and follow the instructions from this guide.

It's a red flag that GUID_partition_scheme is not displayed under Type on diskutil list for my Ventura install (but it's displayed in Disk Utility, I can see GUID Partition Map on Device Information => Scheme for Ventura partition). The EFI partition is also not displayed in my Ventura partition on diskutil list, which is weird, because I'm able to use Mount EFI on it.

Once I added the "BlueToolFixup.kext" in the EFI folder (using MountEFI: https://github.com/corpnewt/MountEFI), it was time to update from macOS Catalina to Monterey. The update process was successful, and after disabling SIP (as instructed by chris1111 -author of Wireless-USB-BigSur-Adapter-.), everything worked fine.

MountEFI

For booting without USB stick i just mounted the EFI partition of my boot drive and pasted there my entrire EFI folder from the USB. To mount the EFI partition i used MountEFI script. Link to MountEFI : https://github.com/corpnewt/MountEFI

If you currently have MacOS installed : https://github.com/corpnewt/MountEFI follow this

Or you can download mount efi script

Use tools like Mount EFI script or what you prefer.

You need to mount your EFI partition (find a tool online or use command line). In it you should find "EFI/OC/config.plist". Open the file with Propertree or another plist editor and make the changes.