pastrychef's Asus ROG Strix Z370-G Gaming (WI-FI AC) build w/ i9-9900K + AMD 6600 XT

[hamzab]

Sorry @pastrychef, photo attached

I'm using a WD Black 1TB NVME drive BTW because I've also seen the 'AppleNVMe Assert failed' error.

Rest of specs are 8700K and a Vega 56 Sapphire, 550W Corsair PSU and 8GB Corsair Vengeance RAM

 

[pastrychef]

Sorry @pastrychef, photo attached

I'm using a WD Black 1TB NVME drive btw because I've also seen the 'AppleNVMe Assert failed' error.

Rest of specs are 8700K and a Vega 56 Sapphire, 550W Corsair PSU and 8GB Corsair Vengeance RAM

Please try the latest Clover EFI from post #1.

 

[hamzab]

Please try the latest Clover EFI from post #1.

@pastrychef Copied your EFI folder over successfully, I'm now however getting these errors (which I think are continuously looping) when I boot with -v

In regards to the EFI folder I used from post #1, I downloaded 'EFI Clover r5104 Z370G (Catalina)'. Is that correct?

There is another folder called 'EFI Clover r5107 Z390G (Catalina)' but I thought that was for the Z390G?

 

[pastrychef]

@pastrychef Copied your EFI folder over successfully, I'm now however getting these errors (which I think are continuously looping) when I boot with -v

In regards to the EFI folder I used from post #1, I downloaded 'EFI Clover r5104 Z370G (Catalina)'. Is that correct?

There is another folder called 'EFI Clover r5107 Z390G (Catalina)' but I thought that was for the Z390G?

Use the 5107.

Did you install kexts in /Library/Extensions/? It looks like it's just tell you that it's rejecting those unsigned kexts.

 

[hamzab]

Use the 5107.

Did you install kexts in /Library/Extensions/? It looks like it's just tell you that it's rejecting those unsigned kexts.

Thanks, I used 5107 and I booted with -v. It's been running for quite some time now and I think it's looping again. I've attached some screenshots.

I have done no extra steps or install any other kexts. I am however using the latest UniBeast from this website which is 10.1.0 and I'm also installing the latest downloaded version of Catalina if that also makes a difference?

I've just followed your guide sir. I'm going to leave this running until you reply just in case it finishes, but I have a feeling it's looping again as it's been going on for more than 30 minutes

 

[pastrychef]

Thanks, I used 5107 and I booted with -v. It's been running for quite some time now and I think it's looping again. I've attached some screenshots.

I have done no extra steps or install any other kexts. I am however using the latest UniBeast from this website which is 10.1.0 and I'm also installing the latest downloaded version of Catalina if that also makes a difference?

I've just followed your guide sir. I'm going to leave this running until you reply just in case it finishes, but I have a feeling it's looping again as it's been going on for more than 30 minutes

I don't know why you are getting code signing errors on standard macOS files. Did you get the installer from Apple? Maybe try recreating your USB installer.

 

[hamzab]

I don't know why you are getting code signing errors on standard macOS files. Did you get the installer from Apple? Maybe try recreating your USB installer.

Yup downloaded from Apple on my legit MacBook 12" 2017.

I'll delete Mac OS X Catalina and Unibeast and download both again. Will report back in 30mins or so!

 

[hamzab]

I don't know why you are getting code signing errors on standard macOS files. Did you get the installer from Apple? Maybe try recreating your USB installer.

Hmm I've got a feeling it may be a faulty Mobo/RAM. In the mean time as OS X Catalina is downloading again, I tried to install Windows, and am getting serious errors which may point to hardware failure (getting Windows 10 Critical Process Died error)

Going to try one more time with the new Catalina Unibeast USB with 5107 EFI folder, and if it still doesn't work, I'll RMA the board and RAM and try again in the middle of the week.

Will report back shortly on what happens with this latest USB install.

 

[hamzab]

I don't know why you are getting code signing errors on standard macOS files. Did you get the installer from Apple? Maybe try recreating your USB installer.

I think I'm getting the same errors as before (please check screenshot). This is with a brand new download of OS X Catalina from the legit Apple Store on my MacBook 12" and a fresh install of UniBeast. Also, I'm using the Z370-G Gaming (the non Wi-Fi model) if that makes a difference. Furthermore, my MacBook is running Mojave, does that make a difference?

I'll wait for you to respond but I think the next course of action is going to be RMA. I'll start again on Tuesday!

 

[pastrychef]

I think I'm getting the same errors as before (please check screenshot). This is with a brand new download of OS X Catalina from the legit Apple Store on my MacBook 12" and a fresh install of UniBeast. Also, I'm using the Z370-G Gaming (the non Wi-Fi model) if that makes a difference. Furthermore, my MacBook is running Mojave, does that make a difference?

I'll wait for you to respond but I think the next course of action is going to be RMA. I'll start again on Tuesday!

You're still getting a lot of code signing errors but for different processes. I don't know why...

Non Wi-Fi version of the motherboard shouldn't make any difference. MacBook on Mojave doesn't matter.

Can you try creating your USB installer using the directions from my Z390 build thread? Link is below in my signature.