[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

[fakejosh]

Asus ThunderboltEX 3 ASUS-THUNDERBOLT-EX-3.zip. This contains: 1. AlpineRidgeEX3-NVM18-NATA.bin 2. AlpineRidgeEX3-NVM26-NATA.bin 3. SSDT-TBOLT3-RP21-ASUS-TB-EX3.aml PCIe Card Use NVM18 for Rev B boards. Use NVM26 only for Rev C boards. Adapt the SSDT to the root port of your system. Credit: @NorthAmTransAm (NATA)

Sorry, for the ASUS EX 3, how does one determine if a board is Rev B or Rev C? Mine is labelled "Rev 1.00" on the PCB

Thank you!

 

[jwpb]

Hi everyone! This is my first post here, but I read this great forum not from today. Thanks to mindblowing Rehabman's work here I have build my first hackintosh on Probook 4540s few years ago. It works fine, and I'm writing to you from it. Last month I decided to build another one. This time on desktop with Thunderbolt (for Universal Audio devices). Pretty fast I found, that this thread gives a lot of detailed information and realized that its Founder is another hackintosh superhero. Thank you CaseySJ! So to make my life easier I decided to go well described path and I bought:

Gigabyte Z390 Designare (F8)
Intel i5-9600K
Corsair Vengeance LPX 32GB (2x16GB) ddr4-3200
Samsung EVO 970 M.2 NVMe (500GB)
CoolerMaster MPX 5501
(no graphics card, no WiFi/BT)

I put it all together and for testing I used one of Linux liveUSB distro. It looks like there is no hardware issues.

But this post is not only for thanksgiving. I have a problem, which I can't solve on my own despite spending hours and days on googling, reading, trying and.. frustrating. That's why I decided to bother you.

I tried many times to go through exact every point of tutorial from first post of this thread checking twice every step to install MacOs 10.14.6. And every time I stuck at black screen (on -v boot) with words: "End randomseed" as last info.

Current state:
UniBeast-prepared USB pluged in "blue" port on MoBo
Monitor on HDMI port
Ethernet cable in i219 port
UEFI settings as described in spoiler of this tutorial (Post#1)
config.plist as described in spoiler of this tutorial (Post#1)
kexts and .efi files on its place

I have read that it this problem can be caused by incorrect "memory fix" file but I followed the tutorial and used OsxAptioFix2Drv-free2000.efi in combination with slide=0.

What I'm doing wrong? What information should I add to make your help possible? Please help.

 

[CaseySJ]

** Gigabyte Beta BIOS F9g **​

Thanks again to @nightmac for informing us of BIOS F9g and in particular the option to enable or disable CFG-LOCK (MSR 0xE2). Although F9g is still in beta, it is digitally signed by Gigabyte and appears safe to use. After installing it this morning I found that CFG-LOCK is actually disabled by default. How nice.

 

[CaseySJ]

Hi everyone! This is my first post here, but I read this great forum not from today. Thanks to mindblowing Rehabman's work here I have build my first hackintosh on Probook 4540s few years ago. It works fine and I'm writing to you from it. Last month I decided to build another one. This time on desktop with thunderbolt (for Universal Audio devices). Pretty fast I found, that this thread gives a lot of detailed informations and realized that its Founder is another hackintosh superhero. Thank you CaseySJ! So to make my life easier I decided to go well described path and I bought:

Gigabyte Z390 Designare (F8)
Intel i5-9600K
Corsair Vengeance LPX 32GB (2x16GB) ddr4-3200
Samsung EVO 970 M.2 NVMe (500GB)
CoolerMaster MPX 5501
(no grafic card, no WiFi/BT)

I put it all together and for testing I used one of Linux liveUSB distro. It looks like there is no hardware issues.

But this post is not only for thanksgiving. I have a problem, which I can't solve on my own despite spending hours and days on googling, reading, trying and.. frustrating. That's why I decided to bother you.

I tried many times to go through exact every point of tutorial from first post of this thread checking twice every step to install MacOs 10.14.6. And every time I stuck at black screen (on -v boot) with words: "End randomseed" as last info.

Current state:
Unibeast-prepared USB pluged in "blue" port on MoBo
Monitor on HDMI port
Ethernet cable in i219 port
UEFI settings as described in spoiler of this tutorial (Post#1)
config.plist as described in spoiler of this tutorial (Post#1)
kexts and .efi files on its place

I have read that it this problem can be caused by incorrect "memory fix" file but I followed the tutorial and used OsxAptioFix2Drv-free2000.efi in combination with slide=0.

What I'm doing wrong? What informations should I add to make your help possible? Please help.

Hello @jwpb,

Welcome to the forum. End randomseed is generally very easy to fix, but it may require one or both of the following:

• Confirm that only 1 memory fix driver is present in the CLOVER/drivers/UEFI folder. If you unsure, just post a screenshot of that folder.
  • Ideally, however, we should replace OsxAptioFix2Drv-free2000 with OcQuirks/FwRuntimeServices (on Mojave). Instructions are here.
• If problem persists, then we need to perform a CMOS Reset by following the procedure in Designare owner's manual.
  • CMOS Reset will also set BIOS parameters to factory defaults so it's a good idea to either:
    • Save BIOS settings to a profile (from "Save & Exit" screen) before doing CMOS Reset, then load the profile after CMOS Reset, OR
    • Configure all BIOS parameters again starting with Load Optimized Defaults.

 

[gandem]

** Gigabyte Beta BIOS F9g **​

Thanks again to @nightmac for informing us of BIOS F9g and in particular the option to enable or disable CFG-LOCK (MSR 0xE2). Although F9g is still in beta, it is digitally signed by Gigabyte and appears safe to use. After installing it this morning I found that CFG-LOCK is actually disabled by default. How nice.

Same for the Aorus Master beta I installed a couple of days ago. Looks like Gigabyte is moving in that direction for the next round of finals. One less step to take!

 

[Ponkass]

*** Mini-Guide: Using Hackintool to Set Headless Platform ID 0x3E980003 ***

Step 1:
View attachment 411253
Step 2:
Mount EFI partition of your Mojave SSD.

Step 3:
View attachment 411252

Step 4:
Select the existing config.plist in the EFI/CLOVER folder. Don't worry, Hackintool will backup the existing file and insert the patch in a non-destructive manner.

Step 5:
In Clover Configurator open the modified config.plist and uncheck/blank-out all entries in the Graphics page.

Reboot.

I'm desperately trying to get Quicksync / IGPU working with this and other guides, but to no avail. Would be super grateful for some input before I've pulled all my hair out.

I'm on a 9900K, so presumably a UHD-630? And a RX Vega 64 is dgpu.

• I've followed your full installation guide.
• I've followed this guide: https://www.tonymacx86.com/threads/an-idiots-guide-to-lilu-and-its-plug-ins.260063/#Headless.
• Internal Graphics is Enabled in Bios.
• I have the latest version of Lilu (1.4.4) and WEG (1.3.9) installed.

Since the Hackintool application has changed a bit since these guides, it helps to confuse things for me.

PNG #1
"Intel CPU Generation" is listed as "???", which should be part of what I need to fix, right? As well as "Metal Headless", which should say "Yes" I suppose? I don't understand how to do this.

PNG #2
I'm supposed to make the "Current Framebuffer" be replaced by the "Selected Framebuffer, right? How do I do that? As far as I can tell I've set the "Intel Generation" in the left corner manually to Coffee Lake, and the "Platform-ID" to 0x3E980003. Is this correct? Why is Hackintool still not recognising it?

PNG #3 VRAM tab

PNG #4 Frambuffer tab

PNG #5 Connectors Tab

PNG #6 When I apply your Patch settings, it seems no actual input is added?


I've attached Config.plist and IOReg as well. I cannot see the iGPU showing up in the ioreg-file.

Thanks for any help!

 

[jrebergen]

@CaseySJ Some 1000 new pages since my last visit! My hack was running smoothly, and with work piling up and there were to many posts to follow I stopped reading. But I had 10.15.4 waiting, so I started reading again. I read about the MSR unlock, but figured I'll try first without. Update went smoothly until the bless support program 'error'.

Even-tough my hack seemed to have updated to 10.15.4, I still had a macOS Install icon when starting up. So I did the MSR unlock. I had to combine 3 posts, because I didn't want to do a fresh install. All went well, again thanks to the great guides. But I still have the macOS Install icon. Clicking on this didn't help because the update package is already deleted. Should I download the 10.15.4 update (or combo) from Apple and run it again?

 

[pure.wisdom]

Hello @jwpb,

Welcome to the forum. End randomseed is generally very easy to fix, but it may require one or both of the following:

• Confirm that only 1 memory fix driver is present in the CLOVER/drivers/UEFIfolder. If you unsure, just post a screenshot of that folder.
  • Ideally, however, we should replace OsxAptioFix2Drv-free2000 with OcQuirks/FwRuntimeServices (on Mojave). Instructions are here.
• If problem persists, then we need to perform a CMOS Reset by following the procedure in Designare owner's manual.
  • CMOS Reset will also set BIOS parameters to factory defaults so it's a good idea to either:
    • Save BIOS settings to a profile (from "Save & Exit" screen) before doing CMOS Reset, then load the profile after CMOS Reset, OR
    • Configure all BIOS parameters again starting with Load Optimized Defaults.

Hi @CaseySJ,
Why we do not remove VirtualSmc.efi because it is a part of OpenRuntime?. I also think slide=0 conflicts with the OcQuirks fixes

 

[aitor451]

Just a quick question. I'm installing Catalina from scratch. The Unlocking MSR 0xE2 should be done at destination Catalina machine or in the machine I'm buildign the USB?

Destination has a z390 designare MB, The other machine I'm using to build the USB has an aorus pro z390 MB.

 

[NCMacGuy]

Just a quick question. I'm installing Catalina from scratch. The Unlocking MSR 0xE2 should be done at destination Catalina machine or in the machine I'm buildign the USB?

Destination has a z390 designare MB, The other machine I'm using to build the USB has an aorus pro z390 MB.

@aitor451

The Designare mobo is the one to be unlocked.