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

[AudioGod]

19 minutes ago, Olas said:

Yes you're right 
The possibility of this card working

ABWB 802.11AC WI-FI With Bluetooth 4.0 PCI-Express (PCI-E) BCM94360CS2 Combo Card For Hackintosh (MAC OS X) Airport Computers, Supports Hands-off

This card works great yes.

[Olas]

12 minutes ago, Project 2501 said:

 

All I know is that AudioGod is using a "ABWB BCM943602CS 802.11AC WI-FI With Bluetooth 4.0 PCI-Express (PCI-E)" card and it is working for him. Again, see the first post of this thread.

 

Ok 

Thank you very much

[cvince]

Hello @AudioGod, Hello All,

 

I hope you are well !

 

Back with good news and some bad one also

 

The good :

• Windows 10 has been installed without issue.
• Catalina has also been installed almost without error (iMessage doesn't work and probably facetime - I did not check FT)
• Both has been installed on a separate NVMe SSD (Windows on M2A and Catalina on M2M) and each time with only one NVMe on the board

To finish my installation, I have installed both NVMe in order to work at the same time (without modifying the boot order).

On the first boot, Clover has boot Catalina without error.

On the second boot, I choose to boot on Windows from Clover also without error.

 

The bad:

• Clover still displayed...
• But now, I can nomore boot on Catalina as it immediately display a stop sign
• Booting on Windows still ok
• The only way to boot on Catalina is to choose to boot from my USB key that I used to install Catalina.

 

Questions:

• How can I repair Clover ?
• How can I have a dual boot with Catalina by default and Windows 10 both on Clover ?

 

 

Best regards and stay safe mates !

 

[Project 2501]

20 minutes ago, cvince said:

Hello @AudioGod, Hello All,

 

I hope you are well !

 

Back with good news and some bad one also

 

The good :

• Windows 10 has been installed without issue.
• Catalina has also been installed almost without error (iMessage doesn't work and probably facetime - I did not check FT)
• Both has been installed on a separate NVMe SSD (Windows on M2A and Catalina on M2M) and each time with only one NVMe on the board

To finish my installation, I have installed both NVMe in order to work at the same time (without modifying the boot order).

On the first boot, Clover has boot Catalina without error.

On the second boot, I choose to boot on Windows from Clover also without error.

 

The bad:

• Clover still displayed...
• But now, I can nomore boot on Catalina as it immediately display a stop sign
• Booting on Windows still ok
• The only way to boot on Catalina is to choose to boot from my USB key that I used to install Catalina.

 

Questions:

• How can I repair Clover ?
• How can I have a dual boot with Catalina by default and Windows 10 both on Clover ?

 

 

Best regards and stay safe mates !

 

 

This worked for me when I got the stop sign (circle with a slash?), but I can't guarantee it since I don't know why it worked. Try resetting the BIOS by either taking out the battery for 1 minute (turn of the computer first, of course) and replacing it, or you can use a flat head screwdriver to short the CLR_CMOS for 5 seconds (known as connector 21, Clear CMOS Jumper in the Pro WiFi manual).

 

Reboot while pressing DEL to get into BIOS. You'll have to redo all your BIOS settings and save. Good luck. I'm going to get some sleep.

 

[hungrywallet]

Just want to throw this out there in terms of WiFI/Bluetooth.  Over the past few weeks I've messed with a gang of different configurations and have landed on a TP-Link T6E card for WiFi and a BT400 dongle for bluetooth.  All works as it should with the exception of needing to use the AircomBrcmFixup.kext.  I stuck with this solution due to it being nearly half the costs ($33) of a Fenvi T919 and a cleaner look in the rig.  I didn't like having to disappear the USB cable / connector on the T919 nor having 4 antennas sticking out the back of my case..lol

[cvince]

3 hours ago, Project 2501 said:

 

This worked for me when I got the stop sign (circle with a slash?), but I can't guarantee it since I don't know why it worked. Try resetting the BIOS by either taking out the battery for 1 minute (turn of the computer first, of course) and replacing it, or you can use a flat head screwdriver to short the CLR_CMOS for 5 seconds (known as connector 21, Clear CMOS Jumper in the Pro WiFi manual).

 

Reboot while pressing DEL to get into BIOS. You'll have to redo all your BIOS settings and save. Good luck. I'm going to get some sleep.

 

Hi,

 

Thank you for your reply.

I tried what you suggested with no chance.

 

Please find attached the verbose boot of catalina.

Don't know what to do.

 

[Praetorianus]

23 hours ago, alboz83 said:

I'm sorry, i read your post but I was just trying to understand. These are new things for me and I don't want to risk making a mess, because touching the bios is a delicate operation. 
I'll read github and i try to unlock

Dear alboz83,

 

Did you succeed in unlocking cfg?

[Olas]

 

Please if you have a driver for this bluetooth

[alboz83]

Dear alboz83,
 
Did you succeed in unlocking cfg?

Ehi, after a few research I unlocked CFG. With grub tool and setup_var

Inviato dal mio vivo 1805 utilizzando Tapatalk

[Praetorianus]

Dear alboz83,

 

unfortunately I could not understand how to make this unlocked

 

[Praetorianus]

Dear alboz83,

 

unfortunately I could not understand how to make this unlocked

 

[Tiem]

[cvince]

4 hours ago, cvince said:

Hi,

 

Thank you for your reply.

I tried what you suggested with no chance.

 

Please find attached the verbose boot of catalina.

Don't know what to do.

 

 

 

 

Finnaly, I reload the "CFG Unlock (MSR) F12d BIOS Profile" and it has boot again on Catalina !

Seriously I don't know what I missed because the configuration was exactly the same. Maybe the unlock part was gone while I used it before installation...

Then regarding the unlock part, can anyone explain me what is the point ?

 

Thanks to all.

By the way I also resolved the iMessage issue (don't know for FT because I don't have webcam )

 

Next step, check that all is good and create a backup !

 

[Project 2501]

5 hours ago, cvince said:

Hi,

 

Thank you for your reply.

I tried what you suggested with no chance.

 

Please find attached the verbose boot of catalina.

Don't know what to do.

 

 

This way beyond me. At this point I start doing guesswork like booting into safe mode, reinstalling the EFI, deleting kernel caches etc. So you are better off waiting for somebody more knowledgeable about the inner workings of the OS on the forum.

 

Sorry I can't be of more help.

 

* However, if I had to guess, because I can only recognize the term "prelinked kernel" (I have no idea if that is the problem), I would try booting into safe mode using clover. I think you get the menu option using the space bar or manually passing the "-x" to the bootloader. If you can get in that way you can try to delete the kernel cache and let it rebuild. I'm not a whiz at the command line, so I like using a GUI utility like OnyX (v3.7.9 for Catalina) to delete the caches.

 

** Disclaimer: this is a total guess, but rebuilding your cache shouldn't hurt your system. You're probably better off waiting for another answer before you try this

Edited March 31, 2020 by Project 2501
Added total guesswork...

[pkdesign]

1 hour ago, Praetorianus said:

Dear alboz83,

 

unfortunately I could not understand how to make this unlocked

 

You literally just boot using modGRUBShell.efi, enter the command and you are done. Links to all these tools and instructions are in this forum. Search for them.

[Project 2501]

4 hours ago, cvince said:

 

 

Finnaly, I reload the "CFG Unlock (MSR) F12d BIOS Profile" and it has boot again on Catalina !

Seriously I don't know what I missed because the configuration was exactly the same. Maybe the unlock part was gone while I used it before installation...

Then regarding the unlock part, can anyone explain me what is the point ?

 

Thanks to all.

By the way I also resolved the iMessage issue (don't know for FT because I don't have webcam )

 

Next step, check that all is good and create a backup !

 

 

Sorry, I didn't realize you were using an unlocked BIOS. My advice of resetting the BIOS without reloading the unlocked profile made it worse.

 

[panosru]

@AudioGod thank you for the update of EFI! I've updated my EFI and I installed latest macOS updates (10.15.4) without any issues, it's been a few days now and everything works smoothly! Today I realised that my WiFi is not working (I'm using Ethernet all the time but I had to connect via WiFi today because of an unrelated to this topic issue), I quickly realised that after updating my EFI folder I did not include AircomBrcmFixup.kext (v2.0.6), which is required for my ARCHER T6E to properly work. 

 

My issue is that I used to connect to WiFi without any issue, and most likely it might be an issue of the kext itself, now I cannot connect to any WEB/WPA2 password-protected network, even though that I'm entering the proper password, it still pops up a message of incorrect password. I have my MacBook next to me and another windows laptop and also three mobile phones (I had to be sure :P) and I can connect to the network without any issues, using the WiFi password I'm entering to in my Hackintosh, but the second reject's my password.

 

I changed the password a few times, and while all the other devices can connect, my Hackintosh cannot.

 

When I remove the password, then my Hackintosh can connect.

 

I tested both 2.4GHz and 5GHz, I got the same behaviour in both bands.

 

Is anyone else facing the same or similar issue? I will try tomorrow with version 2.0.3 which I know that it used to work properly because I have in my EFI backups in earlier version when I was using glasgood's EFI.

 

Thanks to all and stay safe & healthy @ home!

Edited April 1, 2020 by panosru

[AudioGod]

8 hours ago, panosru said:

@AudioGod thank you for the update of EFI! I've updated my EFI and I installed latest macOS updates (10.15.4) without any issues, it's been a few days now and everything works smoothly! Today I realised that my WiFi is not working (I'm using Ethernet all the time but I had to connect via WiFi today because of an unrelated to this topic issue), I quickly realised that after updating my EFI folder I did not include AircomBrcmFixup.kext (v2.0.6), which is required for my ARCHER T6E to properly work. 

 

My issue is that I used to connect to WiFi without any issue, and most likely it might be an issue of the kext itself, now I cannot connect to any WEB/WPA2 password-protected network, even though that I'm entering the proper password, it still pops up a message of incorrect password. I have my MacBook next to me and another windows laptop and also three mobile phones (I had to be sure :P) and I can connect to the network without any issues, using the WiFi password I'm entering to in my Hackintosh, but the second reject's my password.

 

I changed the password a few times, and while all the other devices can connect, my Hackintosh cannot.

 

When I remove the password, then my Hackintosh can connect.

 

I tested both 2.4GHz and 5GHz, I got the same behaviour in both bands.

 

Is anyone else facing the same or similar issue? I will try tomorrow with version 2.0.3 which I know that it used to work properly because I have in my EFI backups in earlier version when I was using glasgood's EFI.

 

Thanks to all and stay safe & healthy @ home!

Hey Buddy,

i did a google search on your WiFi card and it’s coming back as being incompatible with macOS as of 10.14.6 so I’m not sure what to suggest. Is it possible that it hasn’t been working for you since you went to 14.6 and you have only just noticed now?  

Edited April 1, 2020 by AudioGod

[GIOMGIO]

Thank you for the awesome guide AudioGod, Glasgood and all the other people who contributed! 

It helped me a lot!

 

Unfortunately I cannot get CFG unlocked..  (Aorus Pro WiFi)

Although this is something easy to do, I still cannot get it to work after hours of trying.

I get this GUID error (image below) when I do the setup_var_3 with the modified grub shell.

 

First I was thinking this was normal, but when I check the file it still says:

CFG Lock, VarStoreInfo (VarOffset/VarName): 0x5C1, VarStore: 0x1

I dit this checkup this way:

-Save BIOS

-UEFITool --> IFR Extractor

-Look for CFG lock in text file: VarStore still says 0x1

--> I don't know if this is the correct method?

 

What am I doing wrong?

Thanks in advance!

 

*Another question:

When I try the N-D-K OpenCore EFI it won't boot. (circle with slash)

Has this something to do with no CFG unlock?

I can boot the Clover EFI perfectly fine.

 

Edited April 1, 2020 by GIOMGIO
Added question about OpenCore

[AudioGod]

1 hour ago, GIOMGIO said:

Thank you for the awesome guide AudioGod, Glasgood and all the other people who contributed! 

It helped me a lot!

 

Unfortunately I cannot get CFG unlocked..  (Aorus Pro WiFi)

Although this is something easy to do, I still cannot get it to work after hours of trying.

I get this GUID error (image below) when I do the setup_var_3 with the modified grub shell.

 

First I was thinking this was normal, but when I check the file it still says:

CFG Lock, VarStoreInfo (VarOffset/VarName): 0x5C1, VarStore: 0x1

I dit this checkup this way:

-Save BIOS

-UEFITool --> IFR Extractor

-Look for CFG lock in text file: VarStore still says 0x1

--> I don't know if this is the correct method?

 

What am I doing wrong?

Thanks in advance!

 

*Another question:

When I try the N-D-K OpenCore EFI it won't boot. (circle with slash)

Has this something to do with no CFG unlock?

I can boot the Clover EFI perfectly fine.

 

Hello and thanks for the kind words.

the real problem going on for you is the igpu being enabled with OpenCore,

I only just fixed it in clover and have also fixed it in OpenCore but I am awaiting the release of version 0.5.7 Togo public before l let it out in the wild so for now just stick with clover until I post the new Oc EFIs.

 

about Unlocking your MSR, that’s been coming up a lot in the past few days for the pro WiFi model so just read though from a few pages back and there’s all sorts of solutions posted. The simplest way to unlock it is to do it yourself via a grub.  
 

p.s if your desperate to get OC going then you can do by removing all power from the system and then removing the motherboards battery for a few minutes, put it all back together and dial back in your bios settings and away you should go.  

Edited April 1, 2020 by AudioGod

[frankintosh]

On 3/24/2020 at 2:43 PM, AudioGod said:

I’m looking into it for you guys.

 

Today I had again the problem that all USB ports are frozen at once. 

I had the problems with both Clover and OpenCore. I am currently using your latest EFI with Clover.

 

I have a LED keyboard, but it was still lit, so I don't assume that this is a power problem. 
I also use a USB DAC, which just stopped working, but the LED stays on.

 

However, no more input via mouse or keyboard is possible. Plugging or replugging the USB ports of the mouse did not solve the problem. 
Only a reboot solves the problem. 

 

Unfortunately I can't find any information in the system logs that points to this error. 
If you need my support, I can provide you with log files, maybe I'm just looking in the wrong place. 

Best regards

[AudioGod]

2 minutes ago, frankintosh said:

Today I had again the problem that all USB ports are frozen at once. 

I had the problems with both Clover and OpenCore. I am currently using your latest EFI with Clover.

 

I have a LED keyboard, but it was still lit, so I don't assume that this is a power problem. 
I also use a USB DAC, which just stopped working, but the LED stays on.

 

However, no more input via mouse or keyboard is possible. Plugging or replugging the USB ports of the mouse did not solve the problem. 
Only a reboot solves the problem. 

 

Unfortunately I can't find any information in the system logs that points to this error. 
If you need my support, I can provide you with log files, maybe I'm just looking in the wrong place. 

Best regards

Hi,

 

yep we are still looking into it as it only happens to a few isolated users and fortunately one of them does tests for me so we are currently looking for a solution to it. It’s a difficult one as it’s not happening to many people at all myself included so it makes it harder to pin down fully.

Also what makes it even harder is the fact it rarely happens so each change and retest can take a week before the usb fails slowing the fault finding process right down. 

 

Its very random and we don’t really think it’s EFI related anymore but still we are trying to solve it.

Please bare with me and rest assured you haven’t been forgotten about.

[frankintosh]

2 minutes ago, AudioGod said:

Hi,

 

yep we are still looking into it as it only happens to a few isolated users and fortunately one of them does tests for me so we are currently looking for a solution to it. It’s a difficult one as it’s not happening to many people at all myself included so it makes it harder to pin down fully.

Also what makes it even harder is the fact it rarely happens so each change and retest can take a week before the usb fails slowing the fault finding process right down. 

 

Its very random and we don’t really think it’s EFI related anymore but still we are trying to solve it.

Please bare with me and rest assured you haven’t been forgotten about.

Thank you very much, AudioGod. 

Due to the current Corona Pandemic I currently spend about 10 working hours a day in front of my hackintosh. So if you need more testers for debugging, feel free to contact me.  

And again, thanks for you great work anyway. 

Just now, AudioGod said:

 

@frankintosh Are you using the Pro or the Pro WiFi Version of the board?

I'm using the Pro Version not the Wifi-Version. 

[AudioGod]

 

@frankintosh Are you using the Pro or the Pro WiFi Version of the board?

 

Let me know and il PM you a new beta bios and EFI to try.
 

update - just saw your reply. Give me a moment pal

 

Edited April 1, 2020 by AudioGod

[GIOMGIO]

3 hours ago, AudioGod said:

Hello and thanks for the kind words.

the real problem going on for you is the igpu being enabled with OpenCore,

I only just fixed it in clover and have also fixed it in OpenCore but I am awaiting the release of version 0.5.7 Togo public before l let it out in the wild so for now just stick with clover until I post the new Oc EFIs.

 

about Unlocking your MSR, that’s been coming up a lot in the past few days for the pro WiFi model so just read though from a few pages back and there’s all sorts of solutions posted. The simplest way to unlock it is to do it yourself via a grub.  
 

p.s if your desperate to get OC going then you can do by removing all power from the system and then removing the motherboards battery for a few minutes, put it all back together and dial back in your bios settings and away you should go.  

Thank you for the fast response.

Oh ok, no problem mate! I will wait for OC 0.5.7 and will use Clover for the moment.

 

Haha yes I know, I watched these posts on previous pages multiple times and even then it was hard to understand if you are doing this for the first time. (Noob )

I was doing this with Grub, but my checking method was wrong I think.

 

Now I did the check with: VerifyMsrE2 and it says unlocked? (see image)

So I think it's all good now?

Or is this only for checking if this motherboard has possibility to unlock? 

 

*Ok I think I found the right way to check if it's unlocked:

-setup_var_3 0x5C1 0x00 <- to set it
-setup_var_3 0x5C1 <-to check it

-result with checking method: offset 0x5C1 is: 0x00

--> It think it's working now 

 

Edited April 1, 2020 by GIOMGIO
check with setup_var_3 0x5C1