[Success] GIGABYTE Z370 Gaming 7 + Intel Core i7-8700K + RX 580 + (2x) Dell P2715Q 4k @ 60Hz

[jiffyslot]

Hi @jiffyslot. "But I won't return to the Thunderbolt card-killing F7. I'm fresh out of spare Thunderbolt cards."
I honestly think it was an issue when you updated using the Gigabyte BIOS utility within Windows that caused your issue, but I can understand your reluctance. F6, F7 work great for me, but I updated using the BIOS and the new BIOS file on a FAT32 formatted disk, without the thunderbolt card installed (I didn't have it at that stage).

This is what I do to get it all going, yes there are multiple ways to do this, but I'll keep it simple as I can.

Assuming you already have HS 10.13.6 installed on a drive as per this guide by @Hackalot :

• Disable in the BIOS all of the drives, other than your HS drive (precautionary in case things go wrong and you delete something on wrong drive!)
• Make sure your BIOS is configured correctly to boot as per this guide.
• Remove TB3 and any other drives until you get it all going properly.
• Create a Unibeast 8.3.2 USB drive (UB) on a USB 2.0 Stick with HS 10.13.6 on your real Mac. Do not modify the config.plist on this Unibeast stick. The config.plist on this disk will be sufficient to boot your system.
• Once booted from your UB drive into HS, download and install Multibeast 10.4 (MB) from this site.
• Run MB with the following initial options only, to make your HS disk bootable with just the basics to get it going.
  Quick Start - UEFI Boot Mode
  Drivers - Network - AtherosE2200Ethernet v2.2.2 & IntelMausiEthernet v2.4.0
  USB - USBInjectAll
  BootLoaders - Clover UEFI Boot Mode (Our Mobo has NVRAM, so don't need 'Emulated NVRAM')
  Build - Select the Install option.

• Hopefully! you will be able to reboot into the Clover menu and be able to boot into HS.

Once in HS:

• Install Clover Configurator (CC), available from here.
• Using CC to mount your hidden EFI partition, follow this:
  View attachment 352074
• Finder should open and before copying my two config.plists, right click on the existing config.plist and select duplicate from the menu. This will create a copy of your initial config.plist that will be called 'config copy.plist'. You should keep this as you can tell the Clover boot menu to use different configs.plists in case you have a problem down the track. See below for my EFI folder.
  View attachment 352075
• Copy over the two config.plist files into this directory EFI/EFI/Clover/ (my config.plist is setup to tell the system that it is a iMac 18,3. The config.original.plist is a copy of my original UB config.plist that identifies the system as a iMac 14,2
• Reboot

Note:
You can have multiple configxxx.plists in this folder, but it will always default to the one named config.plist. By having multiple config.plist files, Clover has an option where you can select which config.plist file to use to boot from. This is very handy if you stuff up a setting in the config.plist, as it will allow you to select another from the Clover boot 'Option' menu. Press F1 will give you Clover options. Here is how you can select different config.plist files.

1. Hit the 'o' key to bring up the Options menu and then Select Configs...
2. Then you can select any of the configs in you EFI/EFI/Clover folder
   
3. Then keep on selecting the Return option until you are back at the main clover screen. Clover will then boot using this alternate config??? plist option and will revert back to the default config.plist option upon the next reboot. This will allow you to fix/change options in your default config.plist file using CC.

View attachment 352077
View attachment 352078
View attachment 352079

@MysticalOS replied to your post whilst I was typing all this, so depending where your understanding of all this is, both methods will/should work. I'm not 100% sure as to what state you HS disk is at, ie is it bootable from your UB boot disk?

Thanks for this! You all have been more help than I could find anywhere! A+! It's great news in a way that I can confirm that I have been following the directions to the letter, except I was going with the vanilla 14,2 iMac. Just bad luck? IDK. I've started installing to a spinner to force HFS+ to avoid APFS problems. I'll then clone onto a prepared Angelbird 512 WRK SSD.

I use no exterior drives except for the USB OS HS installer. Before I connect the power and SATA cable for my little Samsung 2.5" spinner for a HS install into the PC, all other internal SSDs used in the Windows setup are disconnected from their SATA cable. It sounds like I should be trying to make my CCC clone right after that first Multibeast setup, but before I restart to go into Clover Configurator. Or should I run Clover Configurator immediately after Multibeast without restarting first?

FWIW, when a HS install fails, everything gets wiped. -Another reason I disconnect the drives used with Windows. I don't want Win 10 64 to boot and start seeing alien stuff. I keep everything separated. So, I'll try today and report back. Thanks again!

 

[jb007]

@jiffyslot its getting late here and I've just come back from my Birthday dinner and a few drinks.
What I'd do is do a clean install on your SSD in the PC using a clean install of unibeast from your real iMac and then run Multibeast.
Once you have a bootable HS install, then connect your external SSD and using the transfer app ( cant remember name ATM, as typing this on my mobile phone) that's in your new HS installation Utilities directory, import your user settings settings and apps from the external drive. This way you have a clean install, but it won't be tainted by any inherited problems from your CC drive which I suspect may be causing your booting issues... maybe just a hunch.
One thing to note, is when you create the new install, is to create it with a temporary user name different from your normal user name. The reason for this is when you use the transfer utility, it will also import your user details etc. One transferred, and you are happy with the setup, you can login (after giving your user admin rights from the temp user) as your old user name, and then delete the temp user. I usually leave the temp user though, as it helps if you have a admin user in case something goes wrong down the line.
Hope this is clear, as I said I've had a few drinks!
Must go have a 5am rise to go to work.
Jim

 

[SoundEdiTor]

Hey! Great instructions. Is it possible to use this config for Mavericks?

 

[trs96]

Hey! Great instructions. Is it possible to use this config for Mavericks?

No, you can't install Mavericks. You'd need an older Haswell Z87/97 or Ivy Bridge Z77 system.
See: https://www.tonymacx86.com/threads/...versions-of-os-x-using-older-chipsets.141225/

 

[jiffyslot]

@jiffyslot its getting late here and I've just come back from my Birthday dinner and a few drinks.
What I'd do is do a clean install on your SSD in the PC using a clean install of unibeast from your real iMac and then run Multibeast.
Once you have a bootable HS install, then connect your external SSD and using the transfer app ( cant remember name ATM, as typing this on my mobile phone) that's in your new HS installation Utilities directory, import your user settings settings and apps from the external drive. This way you have a clean install, but it won't be tainted by any inherited problems from your CC drive which I suspect may be causing your booting issues... maybe just a hunch.
One thing to note, is when you create the new install, is to create it with a temporary user name different from your normal user name. The reason for this is when you use the transfer utility, it will also import your user details etc. One transferred, and you are happy with the setup, you can login (after giving your user admin rights from the temp user) as your old user name, and then delete the temp user. I usually leave the temp user though, as it helps if you have a admin user in case something goes wrong down the line.
Hope this is clear, as I said I've had a few drinks!
Must go have a 5am rise to go to work.
Jim

Hey JB, Happy belated birthday!

Your instructions are good. It's too bad that I can't just install (HFS+) Sierra (Skylake and Z370 chipset)and then update to High Sierra in Terminal:

"/Applications/Install macOS High Sierra.app/Contents/Resources/startosinstall" --converttoapfs NO

The Apple utility you were thinking of before was probably Migration Assistant, but it won't clone the OS. I'm sure it's possible in Terminal or Disk Utility, I just don't know how. CCC has been very reliable for me. -Even better than Time Machine. Especially when I clone and archive media drives. I'll try to try today.

 

[jb007]

[

Hey JB, Happy belated birthday!

Your instructions are good. It's too bad that I can't just install (HFS+) Sierra (Skylake and Z370 chipset)and then update to High Sierra in Terminal:
"/Applications/Install macOS High Sierra.app/Contents/Resources/startosinstall" --converttoapfs NO
The Apple utility you were thinking of before was probably Migration Assistant, but it won't clone the OS. I'm sure it's possible in Terminal or Disk Utility, I just don't know how. CCC has been very reliable for me. -Even better than Time Machine. Especially when I clone and archive media drives. I'll try to try today.

Hi @jiffyslot, back from work. Yes, it's Apples Migration Assistant that I'm talking about. To quote Apple, this app allows you to "Use Migration Assistant to copy all of your documents, apps, user accounts, and settings to a new Mac from another computer.". This can be via WiFi, ethernet, TimeMachine or in my example your Sierra installation on an external disc or even attached to your Internal SATA ports.

One of the reasons I like and have used this method (I used the external disk method) is it allows you to build a brand new High Sierra installation with none of the previous non Apple kexts in /System/Library/Extensions & /Library/Extensions etc. Trying to boot your old Sierra install on I assume different hardware, could or can be the cause of all your woes. Using CCC will just be transferring the old kexts that might be causing your problems. Once you have a plain Jane install of HS working then you can use the Migration Assistant to bring over all your documents, apps, user accounts, and settings.

Just remember when you create the new HS install, to create it with a different user account so as to allow you to bring in your old user account details from using the Migration Assistant.

Some questions, sorry if I'm asking silly questions, but I'm trying to help you by remote control and the 17 hours time difference between us is also getting in the way!

1. Are you only trying to install/ copy Sierra or can you use High Sierra. If Sierra only, why?
2. Is there any reason you can't do this method?
3. I gather you have created a new High Sierra Unibeast 8.3.2 High Sierra disk, if not can you?
4. Do you have the HS 10.13.6 installation file to allow you to create this disc? See Step 1 here for info on getting this on your one of your other Macs.

Cheers Jim

 

[hueybui]

Thanks for sharing your Build. Great instructions! Much appreciated...I'll be following these instructions for my upcoming Build.

 

[jiffyslot]

Hi jb,

Yes, I have installers for Tiger (PPC), Leopard, Snow Leopard -Discs. I have multiple safeties of bootable USB sticks and/or partitioned bootable SSDs that hold Mavericks 10.9.x, Sierra 10.12.6, and High Sierra 10.13.6. I even have OS 7.1, 8.6, and 9.2.x around here somewhere. All legit.

Sierra won't install with this chipset/mobo/CPU. I've tried to get around it, but I think there's more to it than simply spoofing the CPU. I've never heard of a sucessfull spoofing of a mobo's chipset. I only wanted to install Sierra onto an SSD (then update using that special command (see me previous reply) to retain HFS+ –all without fail.
The Terminal command: /Volumes/Image\ Volume/No-Convert (from https://www.tonymacx86.com/threads/...-any-supported-intel-based-pc.235474/#install) during a clean install of 10.13.6 often leaves one with an APFS boot disk, so I cannot trust it. That's why I'm installing 10.3.6 onto an internal SATA spinner for the OS, Multibeast, and Clover Configurator portions of the build. Only when it's fully configured and rebootable will I clone it to an SSD.

Big question is: Which version of Clover Configurator should I use when I have "sealed the deal" with Multibeast 10.4? The cover's off of the Fractal case and I await the group's advice... Please and thank you!

 

[jb007]

Hi jb,

Yes, I have installers for Tiger (PPC), Leopard, Snow Leopard -Discs. I have multiple safeties of bootable USB sticks and/or partitioned bootable SSDs that hold Mavericks 10.9.x, Sierra 10.12.6, and High Sierra 10.13.6. I even have OS 7.1, 8.6, and 9.2.x around here somewhere. All legit.

Sierra won't install with this chipset/mobo/CPU. I've tried to get around it, but I think there's more to it than simply spoofing the CPU. I've never heard of a sucessfull spoofing of a mobo's chipset. I only wanted to install Sierra onto an SSD (then update using that special command (see me previous reply) to retain HFS+ –all without fail.
The Terminal command: /Volumes/Image\ Volume/No-Convert (from https://www.tonymacx86.com/threads/...-any-supported-intel-based-pc.235474/#install) during a clean install of 10.13.6 often leaves one with an APFS boot disk, so I cannot trust it. That's why I'm installing 10.3.6 onto an internal SATA spinner for the OS, Multibeast, and Clover Configurator portions of the build. Only when it's fully configured and rebootable will I clone it to an SSD.

Big question is: Which version of Clover Configurator should I use when I have "sealed the deal" with Multibeast 10.4? The cover's off of the Fractal case and I await the group's advice... Please and thank you!

Hi @jiffyslot. I thought I'd upset you, since I had not heard back from you. Hope all's well?

OK, I'm using Clover Configurator version 5.2.0.1 available from here, with my High Sierra 10.13.6 and now my Mojave 10.14 (18A391) installation which I'm trialing ATM on a seperate SSD.

If I iron out the problem I'm having getting my 10GB ethernet going, I'll overwrite my High Sierra installation using Carbon Copy. CC does not change the file system on the destination disk, so It will keep the HFS+ format.

Earlier today I updated my Clover Configurator version from r4630 to r4674 using Clover Configurator in High Sierra. As per my previous posts, HS would then boot into a black screen. I found the answer to this problem in this post by @Tom012 here. I had to add the missing files that he mentions into the drivers64UEFI folder. See my file directory pic. Then all was well and HS booted fine. Then I CC it to a spare SSD, ran the Mojave install file that I had downloaded in HS earlier, and after 3 boots and roughly 25 minutes, the spare disk is now running Mojave!

Edit: Nearly forgot! The version of Clover that's on my High Sierra Install USB Disk is r4428 if that is of interest to you. Hit the 'a' key at the Clover boot menu to get the revision number of Clover.





Hope this helps.

 

[jb007]

Hi all.

I updated to Mojave earlier today on a separate SSD from my High Sierra install, and thought I'd share my experiences.

Before installing I updated my Clover from r4630 (the one that comes in the MultiBeast 10.4 install) to r4674, using the update facility in Multibeast. See my reply to @jiffyslot for further details on how to make this work without the dreaded black screen (at least on my rig!).

The installation took around 25 minutes, and on the 3rd reboot, it booted into the Mojave desktop.

The only issue I have is the Aquantia Aqtion 10GBe card I have is now not being recognised, most probably Apple have changed something e.g. the AppleEthernetAquantiaAqtion kext... to be continued.

It also appears that the AMD RX 580 GPU drivers are now slightly faster, CPU is around the same. I'm running @4.9GHz OC.
I'm getting in Geekbench 4.30 (High Sierra in brackets):
OpenCL 146,445 (142,231)
Metal 140749 (136974)
CPU Single Core 6736 (6705)
CPU Multi Core 32983 (32285)