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

[glasgood]

1 minute ago, AudioGod said:

Thanks buddy I will get right on that one in a moment and report back after im done.

Brilliant stuff

 

There is a lot of changes, so just copy over the info needed for working iMessages from your old config.plist. If you removed USB cable from Corsair H100i then wake should work with mouse and keyboard or power button. But if you want to keep USB cable connected to Corsair then just enable the patch. If not using patch then you can delete SSDT-GPRW.aml from Clover.

 

[AudioGod]

1 hour ago, glasgood said:

 

There is a lot of changes, so just copy over the info needed for working iMessages from your old config.plist. If you removed USB cable from Corsair H100i then wake should work with mouse and keyboard or power button. But if you want to keep USB cable connected to Corsair then just enable the patch. If not using patch then you can delete SSDT-GPRW.aml from Clover.

 

I did it all and it's working but on finding some very strange behaviour now regarding shut down.

Ok so if I manually put the system to sleep and then wake it back up a little later and then a few mins later again shut down the system it doesn't fully shut down now and when it does the boards lights are staying on a few seconds and then cutting out and then if I hit the power button weird things happen and it takes a few presses on the power button before it starts up again.

 

Can you see if the same thing is happening to you if you do the same pattern I did?

 

Also from post bios boot to clover is taking alot longer now.

 

P.s I'm using the patch to enable sleep as I have a few internal usb bits that effect it other then the h100i

Edited June 7, 2019 by AudioGod

[glasgood]

53 minutes ago, AudioGod said:

I did it all and it's working but on finding some very strange behaviour now regarding shut down.

Ok so if I manually put the system to sleep and then wake it back up a little later and then a few mins later again shut down the system it doesn't fully shut down now and when it does the boards lights are staying on a few seconds and then cutting out and then if I hit the power button weird things happen and it takes a few presses on the power button before it starts up again.

 

Can you see if the same thing is happening to you if you do the same pattern I did?

 

Also from post bios boot to clover is taking alot longer now.

 

P.s I'm using the patch to enable sleep as I have a few internal usb bits that effect it other then the h100i

 

 

@AudioGod

 

Set shutdown fix to false fixes it 

 

[AudioGod]

1 hour ago, glasgood said:

 

 

@AudioGod

 

Set shutdown fix to false fixes it 

 

Spot on buddy, now it's all working as it should thank you

[AudioGod]

Hello again buddy,

I got brave and updated Clover to stable version 4945 and I'm happy to report it upgraded with no problems and seems slightly faster at booting now (could be placebo).

 

 

It also added an extra file to drivers64UEFi (AptioMemoryFix-64.efi) that is listed as an upgrade in the install options on clover. I'm guessing that's got something to do with the speed up I'm seeing. still no fix for the purple lines of annoyance though..lol

Edited June 7, 2019 by AudioGod

[glasgood]

2 hours ago, AudioGod said:

Hello again buddy,

I got brave and updated Clover to stable version 4945 and I'm happy to report it upgraded with no problems and seems slightly faster at booting now (could be placebo).

 

 

It also added an extra file to drivers64UEFi (AptioMemoryFix-64.efi) that is listed as an upgrade in the install options on clover. I'm guessing that's got something to do with the speed up I'm seeing. still no fix for the purple lines of annoyance though..lol

 

AptoMemoryFix-64.efi and osxaptiofix2drv-free2000.efi should not be used together. 

Using AptoMemoryFix-64.efi can cause intermittent kernal panic's, it recommended to just use osxaptiofix2drv-free2000.efi to avoid runtime allocation errors.

 

[AudioGod]

1 hour ago, glasgood said:

 

AptoMemoryFix-64.efi and osxaptiofix2drv-free2000.efi should not be used together. 

Using AptoMemoryFix-64.efi can cause intermittent kernal panic's, it recommended to just use osxaptiofix2drv-free2000.efi to avoid runtime allocation errors.

 

So should I delete the file then or should I wait for you to update clover and see for yourself?

I just watched it boot up with -v as is and it's all correct. 

 

I've just noticed that I have to select headphones in the audio list to get sound out of my speakers and theres longer an option for internal speakers smymore. 

 

Edited June 7, 2019 by AudioGod

[AudioGod]

Update - I've just finished doing some work on the system and have noticed a few things.

I do alot of audio work using external hard drives and it seems that all my transfers took alot longer then normal via the my usb drives (3 hours long) it seems like USB 3.1 isn't running at full speed anymore. Il run some speed tests on the ports tomorrow and see if it was the system or my drives but they were fine a few days ago.

Also I shut down the system just now and it restarted itself instead of shutting down. Maybe I selected restart instead of shutdown but I could swear I didn't. Il keep my eye on that il let you know if it happens again.

One last thing, is there anyway to make the power button on the system work to shut down or sleep?

If I press my power button nothing happens.

[glasgood]

6 hours ago, AudioGod said:

Update - I've just finished doing some work on the system and have noticed a few things.

I do alot of audio work using external hard drives and it seems that all my transfers took alot longer then normal via the my usb drives (3 hours long) it seems like USB 3.1 isn't running at full speed anymore. Il run some speed tests on the ports tomorrow and see if it was the system or my drives but they were fine a few days ago.

Also I shut down the system just now and it restarted itself instead of shutting down. Maybe I selected restart instead of shutdown but I could swear I didn't. Il keep my eye on that il let you know if it happens again.

One last thing, is there anyway to make the power button on the system work to shut down or sleep?

If I press my power button nothing happens.

 

@AudioGod

 

Try removing AptoMemoryFix-64, and see if problem persists. As far as I know Clover should not have more than one memory fix driver.  As far as I know sleep is just working within macOS and will wake with power button, will have a look into power button though. Initially sleep worked with power button when I used a dsdt, but macOS would not wake with mouse or keyboard. In System Information panel, what are the reported speeds you have for USB ?  

 

 

 

Edited June 8, 2019 by glasgood

[AudioGod]

Morning buddy, AptoMemoryFix-64 was already removed when it happened but like I said yesterday unless it happens again il put it down to being tired and making a mistake. I've got my eye on it.

I have just ran a test on my usb ports and the speeds of the usb 3.0/3.1 are reporting correctly. My drive must need a scan disk I guess.

Whats going with the audio layout though buddy?

I have to select headphones to get sound out of my speakers and theres no internal speakers option anymore???

[glasgood]

6 minutes ago, AudioGod said:

Morning buddy, AptoMemoryFix-64 was already removed when it happened but like I said yesterday unless it happens again il put it down to being tired and making a mistake. I've got my eye on it.

I have just ran a test on my usb ports and the speeds of the usb 3.0/3.1 are reporting correctly. My drive must need a scan disk I guess.

Whats going with the audio layout though buddy?

I have to select headphones to get sound out of my speakers and theres no internal speakers option anymore???

 

 

 

Morning 

 

Using spoof Device Audio ID results in the loss of Internal Speakers. When creating the patch via Hackintool, Hackintool suggested that Spoof Audio Device ID may be required, so went with that. I did notice audio very briefly distorted on some sound playback, so I removed the spoof Device ID and sound went back to normal including reappearance of Internal Speakers.

 

So here is Audio Patch without spoof Device Audio ID:

 

<key>PciRoot(0x0)/Pci(0x1f,0x3)</key>
			<dict>
				<key>AAPL,slot-name</key>
				<string>Internal</string>
				<key>device_type</key>
				<string>Audio device</string>
				<key>hda-gfx</key>
				<string>onboard-2</string>
				<key>layout-id</key>
				<data>
				AQAAAA==
				</data>
				<key>model</key>
				<string>Cannon Lake PCH cAVS</string>
			</dict>

Here is what it looks like in Clover Configurator

 

 

 

 

 

 

 

 

 

 

[AudioGod]

1 hour ago, glasgood said:

 

 

 

Morning 

 

Using spoof Device Audio ID results in the loss of Internal Speakers. When creating the patch via Hackintool, Hackintool suggested that Spoof Audio Device ID may be required, so went with that. I did notice audio very briefly distorted on some sound playback, so I removed the spoof Device ID and sound went back to normal including reappearance of Internal Speakers.

 

So here is Audio Patch without spoof Device Audio ID:

 

<key>PciRoot(0x0)/Pci(0x1f,0x3)</key>
			<dict>
				<key>AAPL,slot-name</key>
				<string>Internal</string>
				<key>device_type</key>
				<string>Audio device</string>
				<key>hda-gfx</key>
				<string>onboard-2</string>
				<key>layout-id</key>
				<data>
				AQAAAA==
				</data>
				<key>model</key>
				<string>Cannon Lake PCH cAVS</string>
			</dict>

Here is what it looks like in Clover Configurator

 

 

 

 

 

 

 

 

 

 

Yes I noticed a touch of distortion too. Thank you il make the changes in a moment as I'm doing a huge 600gb data transfer now via the 3.1 port and I've done 360gb in just over an hour so we are 100% at full speed on the ports. 

 

Have you changed over to the new version of clover yet by any chance and see it force upgrade the AptoMemoryFix-64 file?

Edited June 8, 2019 by AudioGod

[glasgood]

21 minutes ago, AudioGod said:

Yes I noticed a touch of distortion too. Thank you il make the changes in a moment as I'm doing a huge 600gb data transfer now via the 3.1 port and I've done 360gb in just over an hour so we are 100% at full speed on the ports. 

 

Have you changed over to the new version of clover yet by any chance and see it force upgrade the AptoMemoryFix-64 file?

 

 

Just changed over to Clover_v2.4k_r4945 , but no force upgrade to AptoMemory-64.efi. Regarding the boot graphics glitch, hopefully someone will sort a patch  soon 

 

 

 

 

[glasgood]

08/06/2019

 

POST-INSTALL Aorus Pro Z390 EFI - RX580

 

Updated to Clover v 4945

 

[AudioGod]

Hey Buddy,

I have had an idea, why not instead of disconnecting the h100i cable from the usb 2 0 internal header you turn off the usb2 internal port its connected to instead?

That way if you want to make changes to it you can just boot into windows and it will be ready to go?

Wouldn't it be a simple exclude command in clover?

If you give me instructions il give a go and report back?

Might be the perfect Answer and a way of not having to use the patch.

What do you think? 

 

Update - looking at the usb layout it would be hs11 but then it would shut off both internal ports not just the one stopping the usb connection to the wifi/bluetooth card so unless that could be routed somewhere else that's not really gonna work is it? LoL oh well I tried!

Edited June 8, 2019 by AudioGod

[glasgood]

29 minutes ago, AudioGod said:

Hey Buddy,

I have had an idea, why not instead of disconnecting the h100i cable from the usb 2 0 internal header you turn off the usb2 internal port its connected to instead?

That way if you want to make changes to it you can just boot into windows and it will be ready to go?

Wouldn't it be a simple exclude command in clover?

If you give me instructions il give a go and report back?

Might be the perfect Answer and a way of not having to use the patch.

What do you think? 

 

Update - looking at the usb layout it would be hs11 but then it would shut off both internal ports not just the one stopping the usb connection to the wifi/bluetooth card so unless that could be routed somewhere else that's not really gonna work is it? LoL oh well I tried!

 

It’s a pitty  HS11 is connected to both usb headers on motherboard,  Otherwise it could have been disabled via uia_exclude boot argument in config.plist 

 

Edited June 8, 2019 by glasgood

[telepati]

10 hours ago, glasgood said:

 

 

Just changed over to Clover_v2.4k_r4945 , but no force upgrade to AptoMemory-64.efi. Regarding the boot graphics glitch, hopefully someone will sort a patch  soon 

 

 

 

 

 

Which glitch are you talking about? is it purple lines glitch or a different one?

[glasgood]

16 minutes ago, telepati said:

 

Which glitch are you talking about? is it purple lines glitch or a different one?

 

@telepati the purple lines glitch just before booting to macOS. 

[Ziadantosh]

Thanks for the amazing guide.

 

I am using latest Clover and followed the guide still have iMessage and FaceTime not working.

 

I get a system freeze, how can I troubleshoot what is causing it?

 

My build is:

 

i9 9900K - Gigabyte z390 Pro - Sapphire Nitro+ RX 480 8GB - 16GB Corsair Vengeance RGB 3200 Mhz

Mac disk Samsung Evo 840 SSD 250GB

Windows 10 disk Samsung Evo plus 500GB M.2

 

config.plist.zip

[telepati]

1 hour ago, glasgood said:

 

@telepati the purple lines glitch just before booting to macOS.  

 

Yes, I know, but which boot graphics glitch are you talking about to related AptioMemoryFix-64.efi. I was just curious.

[Hifi33]

Im not sure if this was covered before, but in CC/Devices/Properties, under PciRoot(0x0)/Pci(0x2,0x0) I'm getting 0900A53E for my AAPL,ig-platform-id in pcidevices.plist when I updated the PCIIDs through Hackintool instead of 0300923E, would this be due to the 9700K?  I had a few panics on reboot, and I apart from PciRoot(0x0)/Pci(0x2,0x0) I also edited PciRoot(0x0)/Pci(0x1f,0x3):hda-gfx to onboard-2 from onboard-1 to match my PCIID output of Hackintool. Maybe I should have done a full shutdown and startup.  As it eventually booted on the third try.

 

Update: Switched it back to 0300923E , and re-inserted device-id 70A10000 and back to onboard-1.  Not sure which was the problem for me, but it boots normally again for my setup.

Edited June 9, 2019 by Hifi33
Update

[glasgood]

6 hours ago, telepati said:

 

Yes, I know, but which boot graphics glitch are you talking about to related AptioMemoryFix-64.efi. I was just curious.

 

No boot graphics glitch related to AptioMemoryFix-64.efi.  Was mentioning that it is recommended to use osxaptiofix2drv-free2000.efi rather than AptioMemoryFix-64.efi with Aorus Pro because AptioMemoryFix-64.efi can cause errors on boot.

 

Hence osxaptiofix2drv-free2000.efi replacing AptioMemoryFix-64.efi in this Aorus Pro guide.

 

[glasgood]

6 hours ago, Hifi33 said:

Im not sure if this was covered before, but in CC/Devices/Properties, under PciRoot(0x0)/Pci(0x2,0x0) I'm getting 0900A53E for my AAPL,ig-platform-id in pcidevices.plist when I updated the PCIIDs through Hackintool instead of 0300923E, would this be due to the 9700K?  I had a few panics on reboot, and I apart from PciRoot(0x0)/Pci(0x2,0x0) I also edited PciRoot(0x0)/Pci(0x1f,0x3):hda-gfx to onboard-2 from onboard-1 to match my PCIID output of Hackintool. Maybe I should have done a full shutdown and startup.  As it eventually booted on the third try.

 

Update: Switched it back to 0300923E , and re-inserted device-id 70A10000 and back to onboard-1.  Not sure which was the problem for me, but it boots normally again for my setup.

 

@Hifi33

 

i7-9700K platform ID is 3E980003 better to use:

 

device-id 983E0000

 

AAPL,ig-platform-id 0300983E 

 

 

[glasgood]

8 hours ago, blueman2010 said:

Thanks for the amazing guide.

 

I am using latest Clover and followed the guide still have iMessage and FaceTime not working.

 

I get a system freeze, how can I troubleshoot what is causing it?

 

My build is:

 

i9 9900K - Gigabyte z390 Pro - Sapphire Nitro+ RX 480 8GB - 16GB Corsair Vengeance RGB 3200 Mhz

Mac disk Samsung Evo 840 SSD 250GB

Windows 10 disk Samsung Evo plus 500GB M.2

 

config.plist.zip

 

@blueman2010

 

Hello, what Wireless / Blutooth device do you have ? When and where does the system freeze happen, does system freeze happen when you are using any specific application in macOS?  Do you have CPU / Memory overclocks ? Have you checked temperature of CPU when system freezes,  does system freeze in Windows ? 

 

 

[glasgood]

@blueman2010

 

Replace your EFI folder with --> POST-INSTALL Aorus Pro Z390 EFI - RX580.zip