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

[dsynos80]

11 hours ago, dsynos80 said:

Can anyone explain why with 19.1 profile autologin is not working? Tried tick untick reboot no change... any help on that?

 

P.S. Audiogod, 19.1 is the correct smbios. System feels snappier.

Anyone can help with that? Why it happens to me on 19.1?? On 1.1 autologin works. It is something in config plist but i cant find it...

[AudioGod]

2 minutes ago, dsynos80 said:

Anyone can help with that? Why it happens to me on 19.1?? On 1.1 autologin works. It is something in config plist but i cant find it...

Nope nothing wrong here, auto login works for me under 19,1 as it should do.

 

[dsynos80]

6 minutes ago, AudioGod said:

Nope nothing wrong here, auto login works for me under 19,1 as it should do.

 

AHHH Solved.

 

Choosed my 1.1 plist, changed Smbios to 19.1 and pressed two 2-3 times generate etc.. Replaced, restart,cleared nvram. booted A OK!

[alboz83]

 
The file is the profile, you have to save it and then load it.

Strange, i formatted pendrive in fat32 but I get invalid profile. I don't understand why your profile file is about 16mb (full firmware seems) and profile file from first page is about 2kb.
Anyway for now I boot Catalina with plist tips for MSR

Inviato dal mio vivo 1805 utilizzando Tapatalk

[Praetorianus]

Same here. After I select load profile I have the same mistake. 

[Praetorianus]

5 minutes ago, alboz83 said:

Strange, i formatted pendrive in fat32 but I get invalid profile. I don't understand why your profile file is about 16mb (full firmware seems) and profile file from first page is about 2kb.
Anyway for now I boot Catalina with plist tips for MSR

Inviato dal mio vivo 1805 utilizzando Tapatalk
 

 

2 hours ago, eSaF said:

 

The file is the profile, you have to save it and then load it.

same here when I load the profile I have the same mistake. I suppose the file kindly sent  is a complete BIOS and not just the profile, especially the size of the file when displayed with the profile file when only has a few kb

[alboz83]

same here when I load the profile I have the same mistake. I suppose the file kindly sent  is a complete BIOS and not just the profile, especially the size of the file when displayed with the profile file when only has a few kb

Yes I also think that is a full firmware. But I'm afraid to flash

Inviato dal mio vivo 1805 utilizzando Tapatalk

[AudioGod]

11 minutes ago, alboz83 said:

Yes I also think that is a full firmware. But I'm afraid to flash

Inviato dal mio vivo 1805 utilizzando Tapatalk
 

if it is a patched Firmware then be very careful as if you use it you might find when you next goto update an official firmware it won’t work directly though the bios and your have to create a usb flash key to put it right, I’m not saying that will be the case but it generally is and it’s one of two reasons I post a MSR unlocked profile instead of a patched firmware.

 

Edited March 29, 2020 by AudioGod

[AudioGod]

MESSAGE TO ANYBODY FEELING HELPFUL,

 

Could somebody that’s using a Z390 Pro WiFi using bios F12c with the MSR Unlocked kindly save a MSR Profile with my Bios settings listed on page one to a USB key and zip it up post it on here for the people that need it????

 

Thanks Guys and stay safe  

Edited March 29, 2020 by AudioGod

[dsynos80]

That would be very helpful for us wifi users!

+ how to remove MSR clover patches after that.

[AudioGod]

1 minute ago, eSaF said:

 

Guys to be totally honest I used the file to unlock my board with AG's steps which was successful after two attempts but not knowing exactly what impact it would have on future BIOS updates, I deactivated the change by reflashing the BIOS with the original Gigabyte version and that's the state of my board right now. I am not casting any dispersions or ill intent towards member Hungrywallet desire to help me out to aid the trial of Opencore on my rig which was kind of hit and miss. I plan at some time in the near future to purchase another board (non wifi) possibly one of the new TRX boards but waiting confirmation how they perform as Hacks. Sorry if the file did not work out for you guys, I was hoping Hungrywallet would see the thread and offer some insight.

Ah ok if he did it then he did it via a patched bios.

you can still save your profile with all the correct settings to a USB key as a profile though and send that across instead of the patched firmware. 

[AudioGod]

@eSaF did you try the version of OC I sent you yet?

[Tiem]

1 hour ago, eSaF said:

 Yea I was a little uncomfortable when I decided to reflash to the original, to say my butt was clenched tight during the process is an understatement  but all's well that ends well . Maybe our firebrand friend Tiem (please don't hurt me ) having the same board would pitch in and help out here as this is definitely above my pay grade or i'm just too lazy to faff around .

I would just use the modified grub method rather than loading someone else’s profile. The nice thing about AG’s patched bios is that the MSR lock is unlocked, permanently. If you rely on a profile, it’s exactly the same as using the grub method. Resetting that profile, reflashing the bios will all but wipe out your unlock.

 

https://github.com/datasone/grub-mod-setup_var

 

just make sure to use the setup_var_3. The value to unlock for this board is: 0x5C1

[hungrywallet]

4 hours ago, eSaF said:

 

Guys to be totally honest I used the file to unlock my board with AG's steps which was successful after two attempts but not knowing exactly what impact it would have on future BIOS updates, I deactivated the change by reflashing the BIOS with the original Gigabyte version and that's the state of my board right now. I am not casting any dispersions or ill intent towards member Hungrywallet desire to help me out to aid the trial of Opencore on my rig which was kind of hit and miss. I plan at some time in the near future to purchase another board (non wifi) possibly one of the new TRX boards but waiting confirmation how they perform as Hacks. Sorry if the file did not work out for you guys, I was hoping Hungrywallet would see the thread and offer some insight.

 

What's going on?  I'm a bit out of the loop. 

 

edit:  Oh I see, people I guess thought the bios file was a profile.  Nope, it's the full bios with MSR unlocked by default.  No need for loading profiles or doing weird tricks to get it unlocked.

Edited March 29, 2020 by hungrywallet

[AudioGod]

40 minutes ago, hungrywallet said:

 

What's going on?  I'm a bit out of the loop. 

 

edit:  Oh I see, people I guess thought the bios file was a profile.  Nope, it's the full bios with MSR unlocked by default.  No need for loading profiles or doing weird tricks to get it unlocked.

Apart from a patched bios carries a risk and can have a consequence when it comes to wanting to do a official firmware update. the profile way is 100% risk free and easy for a noob and not scary for a noob too do. If it was 100% risk free then I would of posted patched firmwares instead of profiles from day one. 
One other problem with patching a firmware is that is it voids your warranty and that’s not the biggest deal unless your board goes down with the firmware in place.

 

Better safe then sorry I reckon in every department I mentioned. 
 

Edited March 29, 2020 by AudioGod

[hungrywallet]

11 minutes ago, AudioGod said:

Apart from a patched bios carries a risk and can have a consequence when it comes to wanting to do a official firmware update. the profile way is 100% risk free and easy for a noob and not scary for a noob too do. If it was 100% risk free then I would of posted patched firmwares instead of profiles from day one. 
One other problem with patching a firmware is that is it voids your warranty and that’s not the biggest deal unless your board goes down with the firmware in place.

 

Better safe then sorry I reckon in every department I mentioned. 
 

Having dual bios kind of negates the risks but to each their own.  Bios flashing is the least risky thing I do with my hardware...lol

 

Also, in my opinion flashing  a bios is 20x easier than getting Hackintosh running for the first time so “Noobs” should fear not.

[Praetorianus]

1 minute ago, hungrywallet said:

Having dual bios kind of negates the risks but to each their own.  Bios flashing is the least risky thing I do with my hardware...lol

 

Also, in my opinion flashing  a bios is 20x easier than getting Hackintosh running for the first time so “Noobs” should fear not.

Dear Hungrywallet,

 

thank you so much for the modified firmware with cfg unlock. Could you kindly share your bios profile from the modified firmware unlocked?

 

thank you so much

[hungrywallet]

8 minutes ago, Praetorianus said:

Dear Hungrywallet,

 

thank you so much for the modified firmware with cfg unlock. Could you kindly share your bios profile from the modified firmware unlocked?

 

thank you so much

 

I would if I had the board. Sorry  

[tazevedo317]

Hey guys, thank you for all the help so far. This thread has been great. 

Im running an Aorus Pro Wifi with BIOS 12c on Catalina 15.4 

Core i7 9700k. I have my bios set to AGs guide on page 1, with the latest Clover EFI Folder. SMBIOS set to iMac 19,1. RX570. 

My hack doesn't properly sleep. it goes to sleep and immediately wakes up, fans go on full speed for a few secs, then just stays on normal.

have not unlocked the board. have not set up my own DSDT (not sure how) and have not mapped USB keys (also unsure)

 

What should I do next and how?

 

 

[AudioGod]

20 minutes ago, eSaF said:

 

Guys all I can say is my old GA-Z87-OC FORCE was a piece of cake to manipulate in every which way from Sierra, H/Sierra to Mojave compared to this Z390 AORUS PRO WIFI (was pretty excited at the time about this board - now not so much). I am seriously in the market for a less troublesome board and may even consider moving away from Gigabyte but I've been a Gigabyte man from way back to my trusty GA-EX58-UD3R so will have to do some serious research to find a board that tick all the boxes and also has native NVRAM support. As I've mentioned previously if I do stay with Gigabyte, I am eyeing the new TXR40 line but I'm in the dark as to how they stand up as Hacks.

the Gigabyte Z390 Master is my personal favourite and most trouble free board nvram wise I have worked with so far. Great VRMs and a overclockers dream to work with.

it ticks every box in my eyes.

 

ive also worked with just about every Z390 board out there. And b450, x470 and x570 amd the list goes on and on and I always have a cheeky go at hacking it if I’ve never done it before. 

 

Edited March 29, 2020 by AudioGod

[AudioGod]

You know saying all of that though now with the new r20 quirks and Oc 057 I think the nvram being a problem on the z390 pro is finished now (or for the time being at least).

 

it all works much more like when we were using MemoryAllocation.efi I reckon.

[AudioGod]

6 minutes ago, eSaF said:

 

Now you've put me in a bit of a pickle - do I switch up to a z390 Master or wait for reports on the TX40 line up - decisions, decisions 

Threadripper or any ryzen hackintosh doesn’t work fully so if you get one don’t count on it as your daily driver cos as much as you can get it working really well with macOS the same can’t be said for some important apps and functions,

no AMD Code = A rubbish Hack
 

ive hacked a 3950x on a x570  master and photoshop plugins crash, logic audio or any other DAW works like {censored} and the list goes on and on and on.

 

I tried Pure OC and I tried with Mal and a dsdt and the results were the same. Gutting but true.

as a hobby hack though it’s outstanding.

 

 

Edited March 29, 2020 by AudioGod

[Tiem]

1 hour ago, eSaF said:

 Yea I was a little uncomfortable when I decided to reflash to the original, to say my butt was clenched tight during the process is an understatement  but all's well that ends well . Maybe our firebrand friend Tiem (please don't hurt me ) having the same board would pitch in and help out here as this is definitely above my pay grade or i'm just too lazy to faff around .

I would just use the modified grub method rather than loading someone else’s profile. The nice thing about AG’s patched bios is that the MSR lock is unlocked, permanently. If you rely on a profile, it’s exactly the same as using the grub method. Resetting that profile, reflashing the bios will all but wipe out your unlock.

 

https://github.com/datasone/grub-mod-setup_var

 

just make sure to use the setup_var_3. The value to unlock for this board is: 0x5C1

[AudioGod]

3 minutes ago, eSaF said:

 

Ah yes my friend that is the fly in the ointment, I came across one or two success stories but unfortunately not enough for serious consideration hence the holding off decision so I value your knowledgeable input.

your find with the it worked story’s that the people claiming it ain’t doing anything other then tinkering. 
As long as there’s no code written into the apps themselves for AMD CPUs there really is no way around it. You can make Catalina perfect using a ryzen but that’s not enough.

 

Lets get something straight here too. I can’t stand intel and I think there CPUs are second rate compared to a Ryzen 3000 series and even more so the upcoming 4000 series and if I didn’t need macOS my build wouldn’t have a intel inside.  

[AudioGod]

3 minutes ago, eSaF said:

 

Totally agree on the intel score, they have lost their way compared to AMD new CPUs, don't know how they will see their way back at this moment in time.

By sticking 2 more cores on the same old fabric then stick some extra +++++++++ and giving it a new name that nobody can remember like 10900kxdhtiasz1 and 100w more juice to go with it. We bring you FireLake!  

 

Edited March 29, 2020 by AudioGod