Glasgood's macOS Mojave [SUCCESS][GUIDE] for Aorus Z390 Pro

[larabee]

15 minutes ago, tasc said:

 

@AudioGod I'm up and running on your EFI, and everything seems to be working as expected (including iMessage). I'll keep an eye on things to see if any weirdness creeps back in - thanks for putting this together.

 

@glasgood I can't remember if you included your SMBIOS serial/ROM in your downloads, but other people may just be using those as-is and duplicating the serial. I've run into iMessage activation issues before where I think Apple starts blacklisting the serial because of too many activation attempts across different machines. You may try generating a fresh set of SMBIOS values if all else fails...

 

I've kept my own serial and all of the rt variables unique. That's why I don't have any problem activating imessage. If Apple sees too many activation using the same serial, you will need to generate different ones and worst case you may get your apple ID blacklisted. 

[tasc]

@AudioGod I did notice one error/warning in the ACPI bootup from VirtualSMC about VirtualSMC EFI module broken. I'm not sure if this module is required for reading temps/speeds/etc, but I've added it in previous builds to get rid of that warning. I don't monitor temps or anything, so probably don't need it.

 

 

[AudioGod]

11 minutes ago, larabee said:

 

I've kept my own serial and all of the rt variables unique. That's why I don't have any problem activating imessage. If Apple sees too many activation using the same serial, you will need to generate different ones and worst case you may get your apple ID blacklisted. 

 

I do exactly the same thing and its also why I removed all info from my EFI before uploading it onto here. Some people dont read though and make sure or change the details...THAT'S JUST PLAIN LAZY....lol

 

 

6 minutes ago, tasc said:

@AudioGod I did notice one error/warning in the ACPI bootup from VirtualSMC about VirtualSMC EFI module broken. I'm not sure if this module is required for reading temps/speeds/etc, but I've added it in previous builds to get rid of that warning. I don't monitor temps or anything, so probably don't need it.

 

 

 

I just checked and no warnings for me on the VirtualSMC. Try and keep that kext folder down to a minimum buddy.

FakeSMC will work too if you prefer.

Edited August 16, 2019 by AudioGod

[pkdesign]

28 minutes ago, AudioGod said:

 

Thats awesome buddy, are all the USB ports working and are you able to run usb2 devices on usb3 ports ok?

 

 

 

@larabee

All the USB Patching is done in SSDT-6-A M L to make it native, I think that's just purely a backup method just in case in clover.

 

 

Ah. I always understood the USB patches in Clover were temporary. It actives all ports so you can create a custom SSDT or USBPorts.kext. Enabling all ports was a bad thing I thought.

 

So the SSDT-6-A M L is only activating USB ports, correct? Nothing else? I will have to try and not have my customized USBPorts.kext installed.

15 minutes ago, tasc said:

@AudioGod I did notice one error/warning in the ACPI bootup from VirtualSMC about VirtualSMC EFI module broken. I'm not sure if this module is required for reading temps/speeds/etc, but I've added it in previous builds to get rid of that warning. I don't monitor temps or anything, so probably don't need it.

 

 

Do I have to record my screen to see these warnings? Is there a log I can look at after the fact?

[AudioGod]

14 minutes ago, pkdesign said:

Ah. I always understood the USB patches in Clover were temporary. It actives all ports so you can create a custom SSDT or USBPorts.kext. Enabling all ports was a bad thing I thought.

 

So the SSDT-6-A M L is only activating USB ports, correct? Nothing else? I will have to try and not have my customized USBPorts.kext installed.

Do I have to record my screen to see these warnings? Is there a log I can look at after the fact?

 

@pkdesign Just use my.efi folder and dont add any extra USB ssdt or kexts of any sort and try mine vanilla (as is) just remember to copy all your info from your old config to the new one. (Where I have blanked out the details) and your be golden

 

And not exactly no, SSDT-6-A M L is to fix ACPI warnings and give you a perfect log and its also what's used to patch the USB to make it native. 

Edited August 16, 2019 by AudioGod

[panosru]

4 hours ago, pkdesign said:

You can now wake from sleep using the mouse or keyboard,

 

@AudioGod Could you please let me know how to disable this feature and wake up the computer with power button?

 

Also, why to disable hibernate?

 

Thanks!

Edited August 16, 2019 by panosru

[AudioGod]

3 hours ago, panosru said:

@AudioGod that is looking promising! I haven't tried it yet, and most probably I will hold a bit on it just to give it a little time, is it possible to disable the wakeup with input devices and wake up the computer only though power button?

 

Also, why to disable hibernate? 

 

Thanks!

 

It is possible yes by changing the DSDT slightly but how I have it now you.can only wake the hack by clicking on the mouse or pressing the power button so theres no real reason to change it to any other way really.

 

You don't use hibernate when you put the system to sleep and as MaLd0n says a perfect hack is one with hibernate disabled. If you use file vault though then don't disable it.

Edited August 16, 2019 by AudioGod

[panosru]

I'm not using File Vault

 

In regards to the wake up thing, could you point me on which file I should look to try make the appropriate changes so that the computer will wake only from power button and not from any other input device?

 

Thanks!

[AudioGod]

19 minutes ago, panosru said:

I'm not using File Vault

 

In regards to the wake up thing, could you point me on which file I should look to try make the appropriate changes so that the computer will wake only from power button and not from any other input device?

 

Thanks!

 

I would have to edit the dsdt for you pal.

try it the way it is first as I’m not with my hack now.

[AudioGod]

On 3/6/2019 at 9:58 AM, glasgood said:

SLEEP  – Resolving Instant Wake ( Corsair H100i v2 AIO )

 

 

  Reveal hidden contents

 

Resolve Instant Wake From Sleep caused by the Corsair H100i V2 AIO Cooler

 

To enable wake using mouse and keyboard the Corsair H100i v2 USB cable must be disconnected from motherboard header F_USB1 

 

 

If you want to keep the Corsair H100i v2 USB cable connected then enable the patch in config.plist, instruction below. 

Hackintosh will then sleep, but can only wake using power button.

 

IF USING CORSAIR H100i v2, OR IF YOU HAVE INSTANT WAKE FROM SLEEP PROBLEM 

THEN

ENABLE PATCH --> XPRW change Method(GPRW...

and download --> SSDT-GPRW.aml and place inside EFI/Clover/ACPI/Patched 

 

 

Credit: Patch by Rehabman

 

 

 

 

 

 

 

 

 

 

 

 

 

 

@panosru after you have converted to my efi and if you still want to block the mouse button to wake from sleep then follow the above guide

Edited August 16, 2019 by AudioGod

[panosru]

@AudioGod I just finished a small project, so before moving to the next one, I will now try the EFI and let you know my results

[panosru]

@AudioGod and now what?

 

 

Could it be because I forgot to generate a serial before restart? 

 

I just deleted my efi folder and added yours 

 

{censored}, I cannot even boot from my flash disk that I used when I installed my hackintosh.. What can I do now?? Please don't tell me that I have to reinstall everything I prefer to go and buy a real mac... 

Edited August 16, 2019 by panosru

[AudioGod]

8 minutes ago, panosru said:

@AudioGod and now what?

 

 

Could it be because I forgot to generate a serial before restart? 

 

I just deleted my efi folder and added yours 

 

{censored}, I cannot even boot from my flash disk that I used when I installed my hackintosh.. What can I do now?? Please don't tell me that I have to reinstall everything I prefer to go and buy a real mac... 

When you get to clover boot page press space and select slide=0  and once you enter Mojave’s go into your config and add slide=0 to your boot arguments 

 

or just disable the igpu in the bios

[panosru]

@AudioGod I selected slide=0 but I'm getting the same screen as before. 

 

This is what verbose says 

 

[AudioGod]

1 minute ago, panosru said:

@AudioGod I selected slide=0 but I'm getting the same screen as before. 

 

Select it and then press space so it ticks and then  select return and then boot into macOS 

[panosru]

@AudioGod, obviously I did all that... I made a photo so that you can see what I have selected, I pressed return and tried to boot and I got the same page as before. 

[AudioGod]

4 minutes ago, panosru said:

@AudioGod, obviously I did all that... I made a photo so that you can see what I have selected, I pressed return and tried to boot and I got the same page as before. 

 

Ok if you have your igpu enabled then disable it in the bios and test if not then pull the power from the mains and then remove the battery for a few mins from the motherboard and then put it back and load up your bios setting as per glasgoods guide and you should be fine.

boot back up using your USB key and then  go into the config of the new efi and make sure you have copied across all your details. And that is vital buddy, don’t leave it blank 

 

jumping from efi to efi can mess up the bios from time to time but it’s nothing major and easily fixed.

also if your not already then update the bios to f10 as that’s what mine and glasgood dsdt is based on

Edited August 16, 2019 by AudioGod

[panosru]

Buddy, just for you to know, you owe me new underwear... I disabled igpu and it boot I forgot that the new efi requires it to be disabled... 

 

 

@AudioGod Can I use my Serial from my previous EFI which is iMac19,1 ?

[AudioGod]

6 minutes ago, panosru said:

Buddy, just for you to know, you owe me new underwear... I disabled igpu and it boot I forgot that the new efi requires it to be disabled... 

 

 

No you should be able to boot into the system with the igpu enabled just go into your config and add slide=0 to the boot arguments and then in the bios enable the igpu and set it to its default settings and it should work fine using imacpro1,1 

 

And no generate a new serial and follow glasgoods guide on how to enable iMessage.

 

Personally I prefer the igpu disabled but I'm a overclocker so I would....lol

Edited August 16, 2019 by AudioGod

[panosru]

Ok! I will generate new ones now, also, in Boot options, can I check "Fast" in order to skip Clover boot screen on boot?

Ah another question regarding Rt Variables, should I also generate new values there or leave it as is?

[AudioGod]

2 minutes ago, panosru said:

Ok! I will generate new ones now, also, in Boot options, can I check "Fast" in order to skip Clover boot screen on boot?

Ah another question regarding Rt Variables, should I also generate new values there or leave it as is?

 

You can select fast if you.like sure

 

Generate new values for everything buddy as its.like owning a brand new mac when you change the smbios. Again follow glasgoods guide on how to fix imessage as its extremely.clear and accurate on what you need to fill in and how

[panosru]

@AudioGod So far so good, I can say it works much better than the previous iMacPro1,1 EFI.

 

One minor thing that I have is that my iStats Menus does not recognise my GPU (also a few other programs like VideoProc) and I'm not getting temperature value from GPU sensor  I had the same issue with the previous iMacPro1,1 EFI, but I do not have it with iMac19,1 EFI

 

 

But About this Mac recognises the GPU but for my CPU it shows i9 instead of i7

 

Those are minor issues, not being able to see the temperature of my GPU is a bit annoying though.

 

I will monitor it to see if it solves my freezes that I'm getting quite often lately.

 

Thanks!

 

 

PS: With igpu enabled in the BIOS it will not boot even with slide=0 boot option.

PS2: I may be wrong, but I guess iStatus Menus relies on FakeSMC in order to show GPU temperature... just a theory though..

Edited August 16, 2019 by panosru

[AudioGod]

16 minutes ago, panosru said:

@AudioGod So far so good, I can say it works much better than the previous iMacPro1,1 EFI.

 

One minor thing that I have is that my iStats Menus does not recognise my GPU (also a few other programs like VideoProc) and I'm not getting temperature value from GPU sensor  I had the same issue with the previous iMacPro1,1 EFI, but I do not have it with iMac19,1 EFI

 

 

But About this Mac recognises the GPU but for my CPU it shows i9 instead of i7

 

Those are minor issues, not being able to see the temperature of my GPU is a bit annoying though.

 

I will monitor it to see if it solves my freezes that I'm getting quite often lately.

 

Thanks!

 

 

PS: With igpu enabled in the BIOS it will not boot even with slide=0 boot option.

 

Your getting there buddy, Are your bios setting in line with this guide?

also is your bios at revision F10?

not not then make sure you do both and see if that improves your result.

for the gpu you try injecting it in the clover config and see if that helps. See glasgoods guide on framebuffers on how to do it if your unsure.

 

 

On 3/6/2019 at 9:58 AM, glasgood said:

PART 10 – FRAMEBUFFERS  FOR RADEON AMD RX580, VEGA CARD's
 

  Reveal hidden contents

 

 

The default Framebuffer used after installing macOS is the ATY,AMD,RadeonFramebuffer.

A slight improvement in performance can be had by specifying the framebuffer used by your AMD Graphics card see benchmarks below.

 

 

In the EFI folders attached to guide, I have included SSDT's for AMD RX580 and AMD Vega 56 to enable Orinoco and  Kamarang Framebuffers.

However the framebuffer can be done changed without SSDT, the framebuffer can also be changed in config.plist using Clover Configurator below.

 

 

FRAMEBUFFERS

 

RX 580 = Orinoco

Vega 56 = Kamarang or Iriri

Vega 64 = Kamarang or Iriri

 

 

EXAMPLE

 

Changing from ATY,AMD,Radeon Framebuffer to Orinoco framebuffer for AMD RX 580. 

 

 

 

 

 

 

Benchmark result using ATY,AMD,RadeonFramebuffer

 

 

 

 

Benchmark result using Orinoco Framebuffer

 

 

 

 

 

 

 

 

 

 

 

 

 

@panosru try the above

Edited August 16, 2019 by AudioGod

[panosru]

I'm on F10, my settings are exactly as shown in first page instructions, also there glasgood suggests to disable internal graphics, maybe for the same reason? 

 

I will try checking with frame buffer and let you know, for now I'm testing for freezes. 

 

Thanks! 

[AudioGod]

1 minute ago, panosru said:

I'm on F10, my settings are exactly as shown in first page instructions, also there glasgood suggests to disable internal graphics, maybe for the same reason? 

 

I will try checking with frame buffer and let you know, for now I'm testing for freezes. 

 

Thanks! 

 

I noticed your memory is running at its base speed, turn on your memory XMP profile in the bios buddy.