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

[kernel_void]

8 minutes ago, AudioGod said:

Open hackintool and it will tell you and you can correct it via there too and it will set it correctly all for you.

Ok this is my value

 

[Olas]

4 hours ago, Olas said:

Hello dear brothers,

 

I would like to connect a fenvi card via a USB port on Motherbord z390 aorus pro wifi but all USB ports are used as follows:

1- NZXT KRAKEN X62 in F_USB2

2- GC-TITAN RIDGE in F_USB1 

3- Where to connect fenvi card usb cable on motherboard ?????

Or what is the solution

 

Thank you for your cooperation

 

Thanks dear AudioGod for your reply

use a external usb2 port instead  

pls show me image for this 

 

Buy a internal usb hub

is this good ( NZXT Internal USB Hub ) 

 

 

[AudioGod]

@Olas sorry my mistake you can’t do it using a T919 because you can’t buy the Cable like I say for that device. you would have to solder on A usb Type A yourself so forget it.

 

The choices are the hub or remove the kraken that you should remove anyway tbh as it has no use what so ever unless you use the cam software in windows (completely pointless but up too you)

i can’t tell you what ones work and don’t but anytime I’ve used one it’s been as cheap and simple as you can get. No idea about the NZXT hub, things like that have no interest value to me at all and bore me to sleep....lol...take your best guess as it will be as good as mine. 

Edited April 26, 2020 by AudioGod

[howiethed]

On 4/11/2020 at 11:30 PM, AudioGod said:

Clover Z390 Pro Polaris 19,1 EFI 060420.zip Polaris is the name of your gpu model. 
 

@howiethed I rewrote what EFI is what on page one.
Is it clearer now as to what one is what?  
thanks buddy

Worked a charm. Thanks for all your work. Very much appreciated. First hack build and was straightforward thanks to you guys. All STD bits as per guide. 

 

Only thing is I stupidly went into autopilot and put in my WiFi details when setting up catalina (should have followed the idiot proof instructions) it hung for a bit then I reset and it worked fine. And all set up great. Then thought about it and checked out my serial number to realise that I actually had one (with HAC in the middle). I'm guessing I don't need to do anything or worry about it? 

 

Thanks again all for a brilliant trouble free guide and file set. 

 

 

[Olas]

14 minutes ago, eSaF said:

 

 

Absolutely on this one! Got one in my rig connected to one of the USB headers and completely worry free from day one. 

Plus it has a magnetic base so it can be installed inside the case without it moving around.

Hi dear brother eSaF 

thank you very much for your reply 

you mean NZXT Internal USB Hub

32 minutes ago, AudioGod said:

@Olas sorry my mistake you can’t do it using a T919 because you can’t buy the Cable like I say for that device. you would have to solder on A usb Type A yourself so forget it.

 

The choices are the hub or remove the kraken that you should remove anyway tbh as it has no use what so ever unless you use the cam software in windows (completely pointless but up too you)

i can’t tell you what ones work and don’t but anytime I’ve used one it’s been as cheap and simple as you can get. No idea about the NZXT hub, things like that have no interest value to me at all and bore me to sleep....lol...take your best guess as it will be as good as mine. 

Thank you very much dear AudioGod 

[AudioGod]

7 minutes ago, Olas said:

Hi dear brother eSaF 

thank you very much for your reply 

you mean NZXT Internal USB Hub

Yes buddy that’s what he meant. 
 

9 minutes ago, howiethed said:

Worked a charm. Thanks for all your work. Very much appreciated. First hack build and was straightforward thanks to you guys. All STD bits as per guide. 

 

Only thing is I stupidly went into autopilot and put in my WiFi details when setting up catalina (should have followed the idiot proof instructions) it hung for a bit then I reset and it worked fine. And all set up great. Then thought about it and checked out my serial number to realise that I actually had one (with HAC in the middle). I'm guessing I don't need to do anything or worry about it? 

 

Thanks again all for a brilliant trouble free guide and file set. 

 

 

Good to hear it’s all working for you. That’s great.

I don’t understand your details comment though..

Did you use clover configurator to generate yourself new details for smbios 19,1 (serial number, uuid and mlb)? If you didn’t then do so otherwise your iCloud services won’t work and your get kernel panics and problems down the line.

However If you did that then just enjoy.  

Edited April 26, 2020 by AudioGod

[kernel_void]

I used hackintool cleaned the cache, made the cancellation of the nvram and fixed the power values but at each sleep it does not turn on again but restarts giving me this screen.

Edited April 26, 2020 by kernel_void

[howiethed]

1 hour ago, AudioGod said:

Yes buddy that’s what he meant. 
 

Good to hear it’s all working for you. That’s great.

I don’t understand your details comment though..

Did you use clover configurator to generate yourself new details for smbios 19,1 (serial number, uuid and mlb)? If you didn’t then do so otherwise your iCloud services won’t work and your get kernel panics and problems down the line.

However If you did that then just enjoy.  

I ran configurator after I tried to sort out my apple account access. I didn't set anything in configurator as when I went to look in system report I seem to have imac19,1 apple rom info bios id, board id and a note saying powered by clover5108 and a serial number and hardware UUID all already there so I just stopped there.  iMessage and sidecar all seem to work fine. 

 

Not sure how it did it!  

[AudioGod]

22 minutes ago, kernel_void said:

I used hackintool cleaned the cache, made the cancellation of the nvram and fixed the power values but at each sleep it does not turn on again but restarts giving me this screen.

Hang on a second there buddy, did you say your using my NDK Oc EFI and one of my separate DSDTs that’s actually only for clover?

if you have done this then it explains everything and what your meant to do is use the NDK OC EFI as it is as it already has the correct dsdt inside it made for NDK OpenCore ONLY.

 

Download one more time and try again and this time don’t add a single thing to the Efi other then your sn uuid and mlb and rom (rom is your MAC address) Nothing more nothing less.

 

NDK OC 057 19,1 Z390 Pro Navi Vega 060420.zip

 

p.s don’t forget to clear your nvram between EFI changes. Very important.

Edited April 26, 2020 by AudioGod

[hansik]

hi, I use your perfect build since 4 month now. And today i  patched my build to new update (10,15,3 -> 10,15,4) with the F12b + Efi + profile. The installation had work perfecly, the system boot and works until i type my password of my account after that i have a blackscreen and sometime one flick on my main 2k 32 "benq 144hz screen. I tried an other screen low res + 60 hz who work perfectly. So I do a dualscreen to change the frequency of the benq 144 to 60. and now dualscreen wont work. both are black. I can only use my old 60 hz screen. I would like to change the res of the benq but how can I do it if my screen is black ! ! ? if someone have any idea

Edited April 26, 2020 by hansik

[AudioGod]

6 minutes ago, hansik said:

hi, I use your perfect build since 4 month now. And today i  patched my build to new update (10,15,3 -> 10,15,4) with the F12b + Efi + profile. The installation had work perfecly, the system boot and works until i type my password of my account and i after that i have a blackscreen on my main 2k 32 "benq 144hz screen. I tried an other screen low res + 60 hz who work perfectly. So I do a dualscreen to change the frequency of the benq 144 to 60. and now dualscreen wont work. both are black. I can use only 60 hz screen. I would like to change the res of the benq but how can I do it if my screen is black ! ! ? if someone have any idea

sounds to me like you have a age old macOS problem where it sets the wrong colour pallet up and trips out the monitors. It could of been always there and only just started happening now. Could be wrong but from your description that’s what it sounds like to me.

try this.....

https://spin.atomicobject.com/2018/08/24/macbook-pro-external-monitor-display-problem/

 

This problem is not a hackintosh problem it’s a Apple one. 

 

Edited April 26, 2020 by AudioGod

[kernel_void]

20 minutes ago, AudioGod said:

Hang on a second there buddy, did you say your using my NDK Oc EFI and one of my separate DSDTs that’s actually only for clover?

if you have done this then it explains everything and what your meant to do is use the NDK OC EFI as it is as it already has the correct dsdt inside it made for NDK OpenCore ONLY.

 

Download one more time and try again and this time don’t add a single thing to the Efi other then your sn uuid and mlb and rom (rom is your MAC address) Nothing more nothing less.

 

NDK OC 057 19,1 Z390 Pro Navi Vega 060420.zip

 

I thought those DSTDs were also for opencore, my mistake. Now I put the one you posted as unchanged without any modification. If I don't set sn, uuid, and rom besides not being able to use facetime or imessage what problems could you have?

 

[AudioGod]

5 minutes ago, kernel_void said:

 

I thought those DSTDs were also for opencore, my mistake. Now I put the one you posted as unchanged without any modification. If I don't set sn, uuid, and rom besides not being able to use facetime or imessage what problems could you have?

 

Kernel panics, failed boot ups, lag on the system. Basically you have to have those details in there. It’s as vital as the bootloader itself.

would you like me to create a set of details for you and fill in a config.plist and send it to you??

Edited April 26, 2020 by AudioGod

[hansik]

{censored} no It was the {censored} hdr mode activate on Screen / system preference. Everything seems come back in normal now. thanks for your answer !

[AudioGod]

Just now, hansik said:

{censored} no It was the {censored} hdr mode activate on Screen / system preference. Everything seems come back in normal now. thanks for your answer !

Ah ha yes you didn’t mention hdr, that only activates if the monitors are capable and still leads back to the wrong colour pallet if it’s not working. 
Awesome I’m glad your all ok again now. 

[kernel_void]

2 minutes ago, AudioGod said:

Kernel panics, failed boot ups, lag on the system. Basically you have to have those details in there. It’s as vital as the bootloader itself.

would you like me to create a set of details for you and fill in a config.list and send it to you??

 

I'm glad, because I think my problem is the lack of this kernel panic information You're very kind

[AudioGod]

6 minutes ago, kernel_void said:

 

I'm glad, because I think my problem is the lack of this kernel panic information You're very kind

 

@kernel_void Here you go dude. I have generated new details for you. Replace the plist in the efi with this one.

I will only keep this download up until I see you have downloaded it and then I will pull it so nobody else uses the details. 

 

 

Let me know how you get on now buddy. Ive pulled the File now but if it wasn't you who downloaded it then please do let me know.

Edited April 26, 2020 by AudioGod

[kernel_void]

7 minutes ago, AudioGod said:

 

@kernel_void Here you go dude. I have generated new details for you. Replace the plist in the efi with this one.

I will only keep this download up until I see you have downloaded it and then I will pull it so nobody else uses the details. 

 

config.plist

Just tried it, it gets stuck on the apple unfortunately 

[AudioGod]

5 minutes ago, kernel_void said:

Just tried it, it gets stuck on the apple unfortunately 

What do you mean?

its the exact same plist just with added details.

did you clear the nvram?

powerdown and cold boot with a nvram reset and try again. 
 

7 minutes ago, kernel_void said:

Just tried it, it gets stuck on the apple unfortunately 

What do you mean?

its the exact same list just with added details.

did you clear the nvram?

powerdown and cold boot with a nvram reset and try again. 

Edited April 26, 2020 by AudioGod

[kernel_void]

2 minutes ago, AudioGod said:

What do you mean?

its the exact same list just with added details.

did you clear the nvram?

powerdown and cold boot with a nvram reset and try again. 
 

 

When opening I choose to start catalina it remains stuck on the apple and there is no loading bar. I loaded the config.plist into my EFI, then I restarted the clear NVRAM from opencore and restarted but managed the startup does not go on

[AudioGod]

@kernel_void Are you using my MSR Unlocked profile as I haven’t accounted for it if your not so just adjust the plist if you have a locked MSR.

Edited April 26, 2020 by AudioGod

[kernel_void]

1 minute ago, AudioGod said:

@kernel_void Are you using my smart Unlocked profile as I haven’t accounted for it if your not so just adjust the plist if you hav e a locked MSR.

In your config.plist you set CFG/MSR locked right? I had uploaded your profile with unlocked CFG/MSR

 

[AudioGod]

6 minutes ago, kernel_void said:

In your config.plist you set CFG/MSR locked right? I had uploaded your profile with unlocked CFG/MSR

 

my ndk Oc EFI is set up for a Unlocked MSR (to be used with my bios profile) you only need to adjust if it’s locked still.
I put diagrams up to make it easy to do if needed.

 

Just try and boot again as it could of just been a allocation failed boot up and a cold boot will usually work. It happens, more so when your messing with the EFI

Edited April 26, 2020 by AudioGod

[kernel_void]

1 minute ago, AudioGod said:

my ndk Oc EFI is set up for a Unlocked MSR (to be used with my bios profile) as Need to a just if it’s locked still only. I put diagrams up to make it easy to do if needed.

 

Just try and boot again as it could of just allocation failed on boot up and a cold boot will usually work. It happens, more so when your messing with the EFI

Maybe I understood the problem, when I load the profile, unfortunately I have to modify XMP by disabling it because my ViperStell with my mobo do not get along so I think it cannot unlock the CFG / MSR. How can I solve it?

[AudioGod]

36 minutes ago, kernel_void said:

Maybe I understood the problem, when I load the profile, unfortunately I have to modify XMP by disabling it because my ViperStell with my mobo do not get along so I think it cannot unlock the CFG / MSR. How can I solve it?

 

PLEASE NOTE - These EFIs are setup to be used with your msr Unlocked so make sure you use the F12d Unlocked Profile but if for any reason you can not unlock MSR then just modify following in the OpenCore config.plist :



 

 

Edited April 26, 2020 by AudioGod