AudioGod's Aorus Z390 Master Patched DSDT EFI for Catalina Mini Guide and Discussion

[AudioGod]

48 minutes ago, pl4n__b said:

If I'm not mistaken i download the top one ( i saw clover file there ) and i replace everything one by one except my config.plist . But I have made a copy of my EFI, what should i do now buddy ?

What were you using before you tried my EFI?

 

not using my plist and copying everything else over is simply not going to work unless you have been using my EFI from the start.

 

you need to redownload my EFI and copy your serial number, uuid and MLB over to my plist and use the whole EFI replacing every part of you old one. No 2 configs are the same buddy and that’s where you have gone wrong,

Edited April 9, 2020 by AudioGod

[gibbo592]

Happy Easter hope everyone is safe.

 

Anyone got dual boot on seperate hard drives with open core to work?

[AudioGod]

13 minutes ago, gibbo592 said:

Happy Easter hope everyone is safe.

 

Anyone got dual boot on seperate hard drives with open core to work?

Yes absolutely, it’s working flawlessly via any of my OC EFIs

 

happy Easter buddy

[gibbo592]

Just now, AudioGod said:

Yes absolutely, it’s working flawlessly via any of my OC EFIs

 

happy Easter buddy

Thanks it’s lock down so a bit of tinkering today

[gibbo592]

Just now, AudioGod said:

Yes absolutely, it’s working flawlessly via any of my OC EFIs

 

happy Easter buddy

Thanks it’s lock down so a bit of tinkering today

[AudioGod]

ANYBODY PLAYING AROUND WITH MY EFIs AND JUMPING FROM VERSION TO VERSION TRYING THEM OUT THEN PLEASE REMEMBER THAT NO 2 EFIs ARE THE SAME SO IF YOUR TRYING OPENCORE AND THEN CHANGE OVER TO MY NDK VERSION OF OPENCORE YOU MUST REPLACE THE ENTIRE FOLDER INCLUDING THE CONFIG.PLIST AND THE EFIs ENTIRE CONTENTS. 

 

THERE IS SIMPLY NO LAZY WAY AROUND THIS AS UNLIKE CLOVER OPENCORE AND NDK OPENCORE ARE UNDER DEVELOPMENT AND STILL IN THERE BETA PHASE. THIS MEANS THAT HOW THEY WORK AND HOW THEY ARE CONFIGURED IS ALWAYS CHANGING WITH EVERY VERSION THAT PASSES SO THIS MEANS THERE IS NO LAZY SOLUTION AND COPYING YOUR CONFIG.PLIST FROM OPENCORE TO NDK OPENCORE OR FROM A OLDER VERSION OF OPENCORE IS SIMPLY NOT AN OPTION.

 

I HOPE THIS CLEARS THINGS UP FOR ALL THEM PEOPLE OUT THERE WONDERING WHY NDK OPENCORE DOESN'T WORK FOR THEM OR WINDOWS WONT BOOT. 

 

IT'S YOUR OWN FAULT FOR BEING LAZY!!!!!!!!!!!!

[lygi]

Ok - after few days of testing newest EFI together with BIOS (clean profile without any tweaks), I have some display issues. 

 

almost every time I switch on my computer first thing I see is login srenn - before this is NO SIGNAL, sometimes it has no signal at all  and have to reset the whole machine.

When I simply restart from already booted system - I can see everything from the beginning (post etc)

 

All above is when only DP I connected

 

So I realised, that my machine is selecting my HDMI port first for some reason, so I decided to leave it on HDMI - but here is another problem - when the system is fully loaded, colours are completely OFF (and this  is not a profile issue - My screen I calibrated and  the right profile is loaded)

 

Problem exists only on OSX and only on  HDMI port. 

 

Does anyone have something similar?

 

Master + Vega 64

 

one pic is from DP one is from HDMI

[AudioGod]

@lygi That’s got nothing to do with the bios or the EFI, I would say that’s probably WEG related as that’s the kext in charge of your GPU.

have you tried rolling WEG back to 1.3.7 to see if it helps?

 

One other thing a next user noticed and reported on here is that MacOS hates colour profiles for monitors and they tend to cause all sorts of problems when used so to see if this is happening to you too stop using a colour profile made for the monitor and return to apples preset one.

This is a Mac problem not a Hack problem. 

Edited April 11, 2020 by AudioGod

[lygi]

2 minutes ago, AudioGod said:

@lygi That’s got nothing to do with the bios or the EFI, I would say that’s probably WEG related as that’s the kext in charge of your GPU.

have you tried rolling WEG back to 1.3.7 to see if it helps?

That is weird, as when I load bios defaults I see post screen every time - but when I load your profile the issues are starting. I think Kext has nothing to do as I canst see aorus logo when starting my computer on DP port. I can see it this when the screen is connected to HDMI - but then - colours are off (and at this point IT COULD BE WEG)

 

Let me change next and I will leave it on HDMI. brb

 

[AudioGod]

10 minutes ago, lygi said:

That is weird, as when I load bios defaults I see post screen every time - but when I load your profile the issues are starting. I think Kext has nothing to do as I canst see aorus logo when starting my computer on DP port. I can see it this when the screen is connected to HDMI - but then - colours are off (and at this point IT COULD BE WEG)

 

Let me change next and I will leave it on HDMI. brb

 

Ah ok I see I got you now sorry. Change win 8/10 whql to plain old win 8/10 in the bios .

 

still nothing to do with the EFI, it’s actually the GPUs firmware getting it wrong via DisplayPort (my sapphire vega56 was a pig with bios res via a dp too).

changing the bios setting above should correct it though.

Edited April 11, 2020 by AudioGod

[lygi]

14 minutes ago, AudioGod said:

Ah ok I see I got you now sorry. Change win 8/10 whql to plain old win 8/10 in the bios .

 

still nothing to do with the EFI, it’s actually the GPUs firmware getting it wrong via DisplayPort (my sapphire vega56 was a pig with bios res via a dp too).

changing the bios setting above should correct it though.

Boom!

 

DP is fixed now  With huge ugly aorus on post but I don't mind WEG didn't help for HDMI, but at this point I'm not using it ( I observed tho, when rebooting the system on HDMI with weird colours, there is a screen flick and colours are ok for 5 seconds, and after that computer restarts) 

 

 

[AudioGod]

@Igor fix for the colour flicks on shut down and reason behind it to save me explaining is here my friend.

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

 

one more Mac problem that’s not a hack problem.  

Edited April 11, 2020 by AudioGod

[lygi]

Ok, as promised a bit of update:

 

Fenvi 1200M - actually work OOB - my sleep issues are completely gone. Handoff, continuity, airdrop etc everything is working. Apple watch unlock work only from screensaver mode - from sleep mode doesn't even try to unlock - password prompt straight away. 

 

 

 

 

Edited April 14, 2020 by lygi

[AudioGod]

@Igor I’m guessing your still using the beta bios I sent you still as the unlock feature will not work on any older bios firmwares. If your not using airportfixup then use it as that’s what cured it for me and since using that kext I can not break the unlock feature on my watch anymore and I change my bootloader more then once a day so I was constantly breaking the unlock before the kext. If it’s already in there then do the reverse and remove it and see if it kicks in then. It should work one way or the other buddy.

 

Other things to do if by chance it’s not the above is untick the unlock feature then reapply it or sign out of your iCloud on the hack and reset Bluetooth and WiFi on the phone and the watch and the hack and then sign back into your iCloud account on the hack or the last horrid one is resetting the watch and then restoring it. (Last resort style)

 

Edited April 14, 2020 by AudioGod

[pl4n__b]

On 4/9/2020 at 11:23 PM, AudioGod said:

What were you using before you tried my EFI?

 

not using my plist and copying everything else over is simply not going to work unless you have been using my EFI from the start.

 

you need to redownload my EFI and copy your serial number, uuid and MLB over to my plist and use the whole EFI replacing every part of you old one. No 2 configs are the same buddy and that’s where you have gone wrong,

Not buddy I have been following your threads using your EFI since January and everything work great until this update. what should I do now to boot into the system ? Install clover on a usb stick and put your refi there again and try to boot ?

[AudioGod]

1 minute ago, pl4n__b said:

Not buddy I have been following your threads using your EFI since January and everything work great until this update. what should I do now to boot into the system ? Install clover on a usb stick and put your refi there again and try to boot ?

Yes and you have to use the new config.plist if your using opencore too as to much has changed between now and previous versions.

nothings wrong with the new EFI’s though as hundreds of users are now using it with zero complaints. 

Edited April 15, 2020 by AudioGod

[pl4n__b]

Ohh maybe the the problem was the config.plist, I should have use your new config.plist and past my serial there too, I replace everything but not the config.plist. I will try now

[AudioGod]

4 minutes ago, pl4n__b said:

Ohh maybe the the problem was the config.plist, I should have use your new config.plist and past my serial there too, I replace everything but not the config.plist. I will try now

Always,

especially with OpenCore as it changes with every revision so much that the config totally changes with it.

 

On 4/10/2020 at 10:43 PM, AudioGod said:

ANYBODY PLAYING AROUND WITH MY EFIs AND JUMPING FROM VERSION TO VERSION TRYING THEM OUT THEN PLEASE REMEMBER THAT NO 2 EFIs ARE THE SAME SO IF YOUR TRYING OPENCORE AND THEN CHANGE OVER TO MY NDK VERSION OF OPENCORE YOU MUST REPLACE THE ENTIRE FOLDER INCLUDING THE CONFIG.PLIST AND THE EFIs ENTIRE CONTENTS. 

 

THERE IS SIMPLY NO LAZY WAY AROUND THIS AS UNLIKE CLOVER OPENCORE AND NDK OPENCORE ARE UNDER DEVELOPMENT AND STILL IN THERE BETA PHASE. THIS MEANS THAT HOW THEY WORK AND HOW THEY ARE CONFIGURED IS ALWAYS CHANGING WITH EVERY VERSION THAT PASSES SO THIS MEANS THERE IS NO LAZY SOLUTION AND COPYING YOUR CONFIG.PLIST FROM OPENCORE TO NDK OPENCORE OR FROM A OLDER VERSION OF OPENCORE IS SIMPLY NOT AN OPTION.

 

I HOPE THIS CLEARS THINGS UP FOR ALL THEM PEOPLE OUT THERE WONDERING WHY NDK OPENCORE DOESN'T WORK FOR THEM OR WINDOWS WONT BOOT. 

 

IT'S YOUR OWN FAULT FOR BEING LAZY!!!!!!!!!!!!

@pl4n__b can I just bring your attention to this notice I posted shortly after the updates.   

Edited April 15, 2020 by AudioGod

[pl4n__b]

1 hour ago, AudioGod said:

Always,

especially with OpenCore as it changes with every revision so much that the config totally changes with it.

 

@pl4n__b can I just bring your attention to this notice I posted shortly after the updates.   

That's strange buddy, I install clover on a new usb stick, pass your EFI there and it boot into the system, I tried to edit your new config.plis and pass my serial and replace it in my main Catalina EFI, but after restart it still show the same problem. Maybe I need to reinstall Clover ? how to ?

Edited April 15, 2020 by pl4n__b

[YcF2]

hello,my best friend.

I've been following you for a long time.

My computer configuration is the same as you.  Flashed Z390 MASTER bios to revision F11c.

When you load the bios unlock profile, select the file and return to the main page. Do you know what happened?

Thanks a Ton.

[eSaF]

Ok I will assume you updated your BIOS to 11c and then download the CFG (MSR) 11c BIOS Profile from here, but did you remember to save the Profile before you exit and reboot?

[YcF2]

2 minutes ago, eSaF said:

Ok I will assume you updated your BIOS to 11c and then download the CFG (MSR) 11c BIOS Profile from here, but did you remember to save the Profile before you exit and reboot?

There is no response after I select the file. All the configuration items are still the original ones.

[eSaF]

Before you reboot you need to save the settings -'SAVE AND EXIT'.

[YcF2]

 

6 minutes ago, eSaF said:

Before you reboot you need to save the settings -'SAVE AND EXIT'.

Of course，saved.

I just tried it again.Still the default configuration item.

But now the question is, when loading configuration items, is there no prompt?

[eSaF]

Sorry but AG put up clear instructions to the procedure at the beginning of this thread, just have a read through, you can't go wrong the way it is simplistically written for us. Good luck.