AudioGod's Aorus Z390 Pro Patched DSDT Mini Guide and Discussion

[DoYouBelieveInMiracles]

4 minutes ago, MaLd0n said:

Use this EFI folder and generate ur serials. Stay with MacPro7,1 smbios.

EFI AudioGod Topic OC 1.0.1.zip

Generate USB kext with USB Tool Box. 

https://github.com/USBToolBox/tool/releases/tag/0.1.1

I generated the USB kext by selecting Discover Ports, Select ALL and then Build UTBMap.kext (don't know if that is the correct way)

I just put it on the Kexts folder and replace my current EFI folder with this one? 

[MaLd0n]

1 minute ago, unknownharris said:

I generated the USB kext by selecting Discover Ports, Select ALL and then Build UTBMap.kext (don't know if that is the correct way)

KEYS Order

-Press D key
-Press B key
-Press S key
-Press A key
-Press K key

 

Use UTBMap with USBToolBox USBToolBox.kext.zip

Remove USBInjectAll and XHCI-unsupported

[DoYouBelieveInMiracles]

1 hour ago, MaLd0n said:

KEYS Order

-Press D key
-Press B key
-Press S key
-Press A key
-Press K key

 

Use UTBMap with USBToolBox USBToolBox.kext.zip

Remove USBInjectAll and XHCI-unsupported

Alright, I wanna try see if it will boot from the USB to test this new EFI and not break my configuration.

I formatted my USB drive to FAT-32 with GUID, mounted its EFI partition and copied the EFI folder inside.

But when I try to boot from it (USB drive) on startup it doesn't even show up, what's wrong?

[MaLd0n]

Just follow procedure

-Delete old EFI folder and paste new. Don't use merge files
-Don't use Drag and Drop into EFI partition. Use Copy/Paste instead
-Reset NVRAM one time - with OpenCore use entry "Reset Nvram" / with Clover use F11 key on boot screen

Use one USB stick macOS bootable or direct on SSD EFI partition

Bios/UEFI options just disable CSM and secure boot if need. Set ur XMP.

[DoYouBelieveInMiracles]

On 5/24/2024 at 1:27 AM, MaLd0n said:

Just follow procedure

-Delete old EFI folder and paste new. Don't use merge files
-Don't use Drag and Drop into EFI partition. Use Copy/Paste instead
-Reset NVRAM one time - with OpenCore use entry "Reset Nvram" / with Clover use F11 key on boot screen

Use one USB stick macOS bootable or direct on SSD EFI partition

Bios/UEFI options just disable CSM and secure boot if need. Set ur XMP.

Unfortunately your EFI didn't work for me.

I replaced my old one in my SSD with yours, changed my serials, reset NVRam and now I get verbose printouts when booting, Configuring MDM services... on every boot and the Bluetooth and Wifi drivers no longer work.

Your finished EFI with my configuration is attached if you wanna check what I tried. I don't know what went so wrong. (serials etc replaced with 00000)

EFI.zip

 

Edit: I made it work by updating the kexts with OCAT and the USB configuration is even better than before! Thanks @MaLd0n !

Edited May 26, 2024 by unknownharris

[benjiolino]

On 5/14/2024 at 12:53 PM, eSaF said:

Hi - I have taken a look at your EFI Folder and found all within including OC version needs updating (see included pics).

I don't know if this is the cause of the problem you're having but I have Updated all for you within the attached revised EFI Folder for you to try.

Good luck.

2024-05-14 EFI - Snowwhite Prep.zip 4.78 MB · 3 downloads

where did you get the 1.0.1 version of OCAT? I can only find the version for OCAT 0.95 from December 2023.

[Anto65]

Download OC 1.0.1 from here

https://dortania.github.io/builds/?product=OpenCorePkg&viewall=true&version=1.0.1&sha=7af12eca7814565a66a2fc9bb260c817f0952e65

 

Import then to OCAT 

https://drive.google.com/file/d/1pdSfFr6zN-vpQ-WhPoERUWqZ3tuTu1Cq/view?usp=drive_link

[DoYouBelieveInMiracles]

Hello everyone, I set up a triple boot between Windows, macOS and Linux and unfortunately my Linux installation comes up on boot as Nobara-0.39-Linux-latest-whatever instead of a simple Linux label.
How would I go about to change its boot label?

Edited May 26, 2024 by unknownharris

[ctguru]

Anyone had any issues updating to Sonoma 14.5 from 14.4.1?

[saCULar]

Just updated to 14.5 yesterday, after updating opencore and a few kexts.  Just had to reapply the root patch to get my wifi working after the installation had completed

 

saCUL

[dredhorse]

On 5/14/2024 at 12:53 PM, eSaF said:

Hi - I have taken a look at your EFI Folder and found all within including OC version needs updating (see included pics).

I don't know if this is the cause of the problem you're having but I have Updated all for you within the attached revised EFI Folder for you to try.

 

 

Thanks a lot. It works like a charm for Ventura.

But booting to Sonoma on a copy of my maindisk fails after upgrading.

It get's stuck at the middle of the progress bar. (I know that doesn't help a lot most of the time).

Need to figure out how to display the messages again.

[DoYouBelieveInMiracles]

Hello again,

after my last EFI update I see that my Bluetooth is no longer working.

I can enable/disable it and can scan for BT devices, but when I try to connect to a BT device it automatically switches off.

I don't have native Bluetooth, just a USB bluetooth adapter. 

Does anybody know how to fix?

[Anto65]

What for device ? 

Broadcom , Intel ?

Try add BlueToolFixup.text

 

Edit : i see  TP-Link UB400 ?!

It should work with the kext mentioned above
My Asus ub-400 works

 

Spoiler

 

Edited June 4, 2024 by Anto65

[DoYouBelieveInMiracles]

1 hour ago, Anto65 said:

What for device ? 

Broadcom , Intel ?

Try add BlueToolFixup.text

 

Edit : i see  TP-Link UB400 ?!

It should work with the kext mentioned above
My Asus ub-400 works

 

  Reveal hidden contents

 

Unfortunately, BlueToolFixup.kext is already in my current EFI as per previous iterations..

I checked config.plist it's also there as you can see. What else could it be?

[Anto65]

From your signature you have
TP-LINK Archer T2U Plus (rtwlanu.kext ok )
TP-Link UB400 (should go with BlueToolFixup.kext)

Spoiler

 

 

I would try disabling these kexts

 

Spoiler

I don't think they're useful
Reboot reset nvram and see

[Anto65]

On 5/26/2024 at 11:52 AM, unknownharris said:

Hello everyone, I set up a triple boot between Windows, macOS and Linux and unfortunately my Linux installation comes up on boot as Nobara-0.39-Linux-latest-whatever instead of a simple Linux label.
How would I go about to change its boot label?

You can try adding custom entries

https://www.insanelymac.com/forum/topic/348097-how-to-custom-entry-in-opencore-to-boot-windows/

( Also valid for Linux, just find the PciRoot ... of the grub in the Nobara EFI )

 

There is no need to add Linux drivers with this method

 

Spoiler

 

 

 

 

Edited June 4, 2024 by Anto65

[DoYouBelieveInMiracles]

1 hour ago, Anto65 said:

You can try adding custom entries

https://www.insanelymac.com/forum/topic/348097-how-to-custom-entry-in-opencore-to-boot-windows/

( Also valid for Linux, just find the PciRoot ... of the grub in the Nobara EFI )

 

There is no need to add Linux drivers with this method

 

  Reveal hidden contents

 

 

 

 

My man, your messages fixed both my BT issues and the Linux custom entry I had been searching all over the internet for days. I don't know how to thank you.

I followed the guide you linked and added a custom entry for Nobara-39 as you did in the photo.

My only problems now are that I have like 3 different entries for each kernel version plus my new custom entry.

Do you have any idea how I can remove the "per Linux kernel" entries?

[Anto65]

Well 👍, you can name it as you like, same thing you have to do for the icon in the theme

 

Try setting in
Misc -> Boot -> HideAuxiliary=True

( To Hide Kernel )

[DoYouBelieveInMiracles]

32 minutes ago, Anto65 said:

Well 👍, you can name it as you like, same thing you have to do for the icon in the theme

 

Try setting in
Misc -> Boot -> HideAuxiliary=True

( To Hide Kernel )

I undid the LinuxDriver method since I now have a custom entry to boot Nobara from, but this somehow created one more NONAME entry in my boot picker. So now I have EFI and NONAME as additional entries

I have HideAuxilliary = True set forever.

[Anto65]

Set in misc -> security -> scanpolicy = 2687747

 

you're almost there 😀 

 

ops probabily Windows Will now Hide ... I remember that now , it s so ?

Edited June 4, 2024 by Anto65

[DoYouBelieveInMiracles]

6 minutes ago, Anto65 said:

Set in misc -> security -> scanpolicy = 2687747

 

you're almost there 😀

That did the trick but also hid the Windows partition (due to hiding NTFS drives) 

That is no problem though, as I can just create a custom boot entry for Windows like you taught me above!

Thank you so much man and sorry for the annoyance! :/

[Anto65]

yes in fact I remembered later sorry (I wrote above in fact)
That's right, or inserted a custom entry for Win too,

or put the scanpolicy back to 0 and download and replace the Boot folder from the Opencore pkg, you're probably missing the .contentvisibility files (they're hidden)

 

In fact, personally I only use custom entries for all bootloader...I find it to be the best solution

Edited June 4, 2024 by Anto65

[DoYouBelieveInMiracles]

Unfortunately all of this tinkering (and my itch to have everything perfect) compromised my macOS installation.

I tried to change the .VolumeIcon.icns in the Preboot volume, tried through macOS Recovery to replace the icon there with one in my Desktop (also named .VolumeIcons.icns) but only got error that there is no such file in my Desktop.

So when I left my recovery and tried to boot back into macOS I now get the Opencore loader again and again with no sign of booting macOS.

I tried booting directly to macOS through the BIOS but I got some 3 line error like OCSB: No suitable signature - Security Violation.

Please tell me what to do, I'm freaking out as this was my main work OS...

 

Edit: I modified my Opencore EFI through Windows and set SecureBootModel to Disabled and now when I select macOS It shows the Apple logo, starts loading but then restarts.

[Anto65]

Check your bios settings , that UEFI Secure Boot is disabled 🤷‍♂️

 

 

[DoYouBelieveInMiracles]

It’s disabled as expected. I don’t understand if I did something with the Preboot volume, since no changes were made.

 

Edit: if we go into last resort method how can I reinstall macOS without losing Opencore or the other OS partitions?