Contribute
Register

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

How about the OpenCore version of your guide ? Just kidding ;)
Clover still works with Mojave. It's not mandatory.
LOL

I figured that because I waited so long to upgrade that my (eventual?) upgrade to Catalina on this machine down the road may just be clicking update like a real Mac. The kexts and clover should already be updated to new versions created after Catalina anyway, so it might be a smooth upgrade to Catalina as well. (famous last words...) :)
 
I did not do a clean/virgin install. I just updated If anyone wants me to update the guide here on how I exactly went about updating this exact system to macOS Mojave, I'll be happy to do so a step-by-step and include my EFI folder if that helps anyone.
I’d be surprised if there wouldn’t be quite a few people interested. :)

Be sure to keep the original how-to in tact though. Wouldn’t it make more sense to start a separate thread about it?




I looked a lot at your specs for my build at that time. Needed Mojave already 1,5 years ago though, so I had to find my info elsewhere. I can’t mention the site because I suspect it’d be against tony policy, however, I’d be happy to contribute my EFI / experiences with you / others if you’d do a ‘virgin’ setup.

Also, besides that I’m curious for your EFI because I sometimes encounter a glitch after waking from sleep. A restart always fixes it but still..
 
By the way I had quite problem when I wanted to update from 10.14.x to 10.14.6 and wanted to re-install, because kexts were changed and Clover had also changed.
 
HackaShaq's "2018 Mac Pro Replacement" Build: 10.14.6 Mojave Update

Ok guys, OP here. I’m back. I have had this build running flawlessly on High Sierra ever since I built it, and I wasn’t planning on upgrading macOS for the life of the machine. However, I needed Mojave for certain software like Lightroom 10, so I did the deed and updated macOS on this machine.

Let me start by saying, as you may already know, I’m not an expert at Hackintoshing at all. In fact, that’s why I wrote this build guide in the most basic straightforward terms possible to help the even the most beginners see a step-by-step of how to build this build. I’ll do the same thing for this Mojave update guide for this machine, and show exactly what I did to help people who may want to upgrade. Let’s get started:

1. Create a Bootable backup.

Don’t skip this step. This should already be the norm, but it’s worth noting. These days Samsung 500GB SSDs are only $65, so be sure to have a bootable backup ready in case something goes wrong. How exactly do you so this? It’s easy and here are the steps for beginners. Feel free to blaze past this if you know how:

A. Insert your brand new 500GB SSD into an external USB enclosure or connect directly inside your machine. (My boot drive is called “Mac Pro” and my backup drive is called “Mac Pro Backup”…original, I know.) :)
B. Use software like Carbon Copy Cloner or SuperDuper! to mirror your current bootable startup drive to your backup drive. (I personally use SuperDuper!)​
superduper.jpg
C. After the hard drive data has been mirrored to your backup. Launch Clover Configurator. In the “Mount EFI” sidebar under “Tools” select your source boot drive from the list of EFI partitions in the bottom portion of the screen, then repeat the process for your backup drive.​
EFI mount.jpg
D. You will now have two mounted EFI virtual drives on your desktop. You want to copy the complete EFI folder from your boot drive to your backup drive (this will make it bootable).​

Please pay attention to this step to ensure you’re copying the correct EFI folder from your source drive.

This can be somewhat difficult to tell the difference between the two EFI “drives”. So to confirm which one is which, double click and open the drive named EFI and the hold down the command key and click on the drive icon. It will show you the exact drive you’re looking at. Also, the source drive will have a CLOVER folder inside the EFI folder where as the backup drive would not if this was a freshly formatted backup drive.

efi_bootdrive.jpg


Drag the folder “EFI” from the source drive to the backup drive and when the Finder asks, you want to Replace not merge. (i.e. you want to completely replace the EFI folder to make this new backup SSD bootable.

E. Play it safe and test your backup. Connect it to your external USB enclosure, reboot, and at the clover boot loader, select your backup to ensure it boots up and you have a viable backup.​


2. Update macOS to Mojave.

Ok, I know you’re probably supposed to update Clover and all kexts beforeupdating macOS, but I didn’t. I thought to myself, “What if I just update macOS to Mojave and it works fine?” so I felt like trying. It didn’t. I mean, it booted, but I lost audio functionality and other things like USB connectivity, so I had to re-examine things and do it right. So yeah, it’s best to do it right. Here’s how to update macOS.

A. Download macOS Mojave direct from Apple.​

I went to this link:​

Then, simply scroll down to the “Download macOS” section and click on the macOS Mojave 10.14 link. This will pop up the download option for Mojave.

A nice thing about waiting this long to update to Mojave is that the download is the final combo OS installer which is 10.14.6.

B. Click to download and install. This will take time based on your internet connection, and it will reboot, etc. You will likely need to select the “mac OS Install” partition at the Clover boot loader after the first main reboot to allow Apple to continue to download the necessary files.​


3. Update Clover Boot Loader.

Update your Clover Boot Load by launching Clover Configurator, selecting Install/Update Clover from the “Tools” left-hand sidebar, then clicking the “Update” bottom in the bottom right corner.

Once you click “Update” you will see a list of available bootloaders. Since Mojave came out in September of 2018, it’s 2 years old now and I figured I didn’t want the latest Clover boot loader just in case. So for my needs, I selected revision 5122 from the pull-down menu.

clover-boot-loader.jpg

I took this screen shot after already updating to Mojave. But my original version of Clover was revision 4359 as per my original build for High Sierra.

Once selected, click the “Update” button to download and install Clover.

NOTE: If you use Little Snitch, you may see a malicious/suspicious warnings pop up that will prevent you from downloading/installing this package. I did. And it was an issue even when I clicked to proceed from the warning. (This is because the Little Snitch message doesn’t truly allow all when it detects something malicious.)

If you use Little Snitch, launch Little Snitch Configuration.app and manually add the app “Clover Configurator.app” to Little Snitch and allow the app to “Allow Any Outgoing Connection” before even attempting to download the clover update within Clover Configurator.app:

little_2.jpg

little_1.jpg


Click the “+” to manually add Clover Configurator.app and then you will see Clover Configurator in the list highlighted above, and it will download the Clover update just fine after that.


4. First download the updated Kexts for this build.

There are very few kexts needed for this build. The three main Kexts needed to upload for this build are:

Download AppleALC.kext
Download Lilu.kext
Download FakeSMC.kext

Should you use the latest versions of these kexts? Probably. Did I actually do that? No. I just grabbed versions 1.3.6 of AppleALC.kext and 1.3.9 of Lilu.kext.

Why? Well, they were released in 2019, and I figured they were new enough to be primed and ready for Mojave, yet old enough to hopefully not introduce any issues due to edits perhaps needed for Catalina or Big Sur. Is this the wise approach? No clue, but this is what I did and it worked. :)

For FakeSMC.kext I did use the latest version from that link which was from 9-15-2018.


5. Remove USBInjectAll.kext for Mojave.

You're not going to need USBInjectAll.kext anymore.

This is located on your boot machine’s hard drive, not inside the EFI folder. If you remember from my original High Sierra build, I used “USBInjectAll.kext” and this kext was placed on the boot drive in the following folder:

Library > Extensions > USBInjectAll.kext

usb-inject-moojave.jpg



For Mojave, you will want to remove USBInjectAll.kext. We’re not going to need it. Remove the kext above and send it to the trash.


6. Add AppleALC.kext for Mojave.

Add AppleALC.kext to this same directory for macOS Mojave:

AppleALC-Extensions.jpg




Again, this is added to the computer's hard drive, not the EFI folder. Please see the screen shot above for the exact location inside Library > Extensions


7. Reorganize the kext placement for Mojave.


Launch Clover Configurator.app, and mount the EFI partition for your boot drive:

EFI mount.jpg


On the previous High Sierra setup for this build, I had kexts in both the 10.13 folder and the “Other” folder. This was not ideal, but it worked, and if it ain’t broke, I didn’t fix it.

You will want to rearrange the placement of the kexts to be correct for Mojave

BEFORE (Old High Sierra Setup):

kexts_before.jpg


AFTER (Mojave 10.14.6 setup):

kexts_mojave.jpg


8. USB Fix for Mojave (Patch your Kexts).

With each version of macOS, there are tweaks needed to properly access/mount USB devices. Here is the tweak that I found online for updating the USB info correctly for macOS Mojave 10.14.6:

A. Mount your EFI partition with Clover Configurator​
B. Navigate to /Volumes/EFI/EFI/Clover/​
C. Right-click open config.plist with Clover Configurator (or drag your config.plist file onto the Clover icon in your dock.​
D. Click Kernel and Kext Patchesunder SECTIONS left side bar of Clover Configurator​
F. There are two patches here you are going to Disable. You need to disable these two entries as they are High Sierra patches which only apply to macOS 10.13.x High Sierra. We don’t need these for Mojave. Disable the following entries: com.apple.driver.usb.AppleUSBXHCIand com.apple.driver.usb.AppleUSBXHCIPCI.​

kext-patch.jpg


Please see the two checkboxes above to disable the macOS 10.13.x patches. I couldn’t capture the entire lines without scrolling the window, so I just mocked up this screen cap to show all relevant info.

G. There are four patches you will make here to have USB working smoothly. You will want to ADD the kext patch by clicking the small “+” icon at the bottom left portion of the window, and then add the following information as per the screen cap above.​

Mojave 10.14.6 Kext Patches: (4 Patches)


Patch #1:
Name*: com.apple.iokit.IOUSBHostFamily​
Find* [HEX]: 83FB0F0F​
Replace* [HEX]: 83FB3F0F​
Comment: USB Port Limit Patch 1 PMHeart/DalianSky​
MatchOS: 10.14.x​
Patch #2:
Name*: com.apple.iokit.IOUSBHostFamily​
Find* [HEX]: 83E30FD3​
Replace* [HEX]: 83E33FD3​
Comment: USB Port Limit Patch 2 PMHeart/DalianSky​
MatchOS: 10.14.x​
Patch #3:
Name*: com.apple.driver.usb.AppleUSBXHCI​
Find* [HEX]: 83FB0F0F​
Replace* [HEX]: 83FB3F0F​
Comment: USB Port Limit Patch 3 PMHeart/DalianSky​
MatchOS: 10.14.x
Patch #4:​
Name*: com.apple.driver.usb.AppleUSBXHCI​
Find* [HEX]: 83FF0F0F​
Replace* [HEX]: 83FF3F0F​
Comment: USB Port Limit Patch 4 PMHeart/DalianSky​
MatchOS: 10.14.x​


H. Be sure you save you config.plist file, and now all USB devices should work properly with Mojave.

usb-tree.png



USB is alive and well now.


9. Audio Fix for Mojave

Walk to your fridge, grab a drink, pause, smile and do nothing. You’re done!

The reason I brought this section to your attention is that I read many many notes online that showed that new to Mojave, that you can no longer inject “11“ into the devices area of Clover Configurator to get audio working. (This is Step Seven: Fix Audio in my main Guide post.)

From the High Sierra build guide I made, to setup audio, you just had to go to Clover Configurator, choose Devices from the sidebar under SECTIONS, and then under the “Audio” section check “ResetHDA” and then enter the magic number “11” in the Inject pull-down menu. This was for High Sierra. However, I read many things saying this no longer works for Mojave, and how people needed to add PCI device IDs, guess the numbers to use from a range of numbers at the bottom and change properties, etc.

Well, thankfully this wasn’t the case for this build, and the previous High Sierra setup works great with audio. No changes need. Whew. All done.



10. I’m attaching my working EFI folder

It’s best to get this working on your own just to be safe, but what the heck, this build has been pretty popular so if people want or need to see my EFI folder, I’m attaching it to this post.

A. The only edit I made to this EFI folder is my computer’s serial number. You’ll want to open the config.plist file and enter your computer’s serial number. Look for the text on line 391:​
<key>SerialNumber</key>​
<string>CXXXXXXXXXXXX-PUT-YOUR-SERIAL-HERE</string>​
Just update the text “CXXXXXXXXXXXX-PUT-YOUR-SERIAL-HERE” with your computer’s serial number by editing the text file in BBEdit, etc.​

(You can find your serial number for your machine by just going under the Apple Menu and choosing About This Mac.)


B. My boot drive is called “Mac Pro” so you may also want to change line 162 of the config.plist file to the name of your computer to startup to this by default.​

C. I actually added the “AtherosE2200Ethernet.kext” into the “Other” folder of my kexts as well. It’s not needed, but it didn’t mess anything up, so it’s there too. You probably don't need it.​
D. I’m including this EFI for educational purposes only. Not responsible for anything that may happen to your system. YMMV. Operators are standing by. Not valid in Guam. You get the idea.​


That’s all, folks.

Hope this Mojave update addendum helps someone, and if it does, please circle back and post here as it always makes me happy to hear that this guide build has helped people.

If things don’t work, I can do my best to assist, but there are people far smarter than me on this forum that are more likely to give you better info.
 

Attachments

  • EFI.zip
    31 MB · Views: 109
Last edited:
YES Please! I'm still having sleep issues with Mojave and I have the exact same hardware

I’d be surprised if there wouldn’t be quite a few people interested. :)

Be sure to keep the original how-to in tact though. Wouldn’t it make more sense to start a separate thread about it?




I looked a lot at your specs for my build at that time. Needed Mojave already 1,5 years ago though, so I had to find my info elsewhere. I can’t mention the site because I suspect it’d be against tony policy, however, I’d be happy to contribute my EFI / experiences with you / others if you’d do a ‘virgin’ setup.

Also, besides that I’m curious for your EFI because I sometimes encounter a glitch after waking from sleep. A restart always fixes it but still..
Just made an add-on post here (currently post #1985 with the info on exactly how I updated my system from High Sierra to Mojave.)

EFI folder is also included for reference.

Just letting you both know since you posted you were interested in this earlier today. Hope this helps. Cheers.
 
Cudo's for this! :clap: I can hardly believe how fast en clear you can make a how-to like that! It takes me ages to do a hackintosh build, let alone document it properly along the way.

Even though I'm already on Mojave and even though I know that everything can be fixed, as long as you keep a backup of your personal / 'unique' data, I'm always anxious that one day something will break and that I'll not be able to fix it again. Or at least not in a reasonable amount of time. That's why I always keep two Macs and keep most stuff in iCloud.

I had the idea to make a how-to myself, for a Mojave hackintosh, but from a 'fresh' / virgin install. For worst-case scenarios. However, I know so little about the matter that I feel like a total noob when it comes to this. Nowhere near up to it. Like I already said, I had to reach out for help to a total stranger last time. After years of reading and my own hackintosh I still don't even get what the exact differences between different hackintosh approaches are.

Thank you for this and please do make a 'virgin install Mojave Hackintosh how-to' if you can. I'll even tip you for it, not kidding.
 
With this hardware I would consider upgrading to macOS Catalina and/or Big Sur. Both are very stable using OpenCore.
 
@HackaShaq

Your build inspired me to duplicate it in June 2018, as reported in my Post #92. Without your detailed instructions I probably would have never attempted it. Since then I had upgraded the CPU to a i9-9900K, replaced the BeQuiet with a Corsair H115i Pro Cooler, installed a Fenvi card for WiFi and Bluetooth, and installed a flashed GC-Titan Ridge TB3 card.

I've also changed to using OpenCore instead of Clover, and currently have OC 0.6.6 installed running Big Sur on my build.

Over the past nearly three years I've built several more hackintoshes, all currently using OpenCore.

"If it ain't broken don't fix it." But you might want to consider moving to OpenCore as it seems to be a viable replacement for Clover and probably the go-to boot loader for hackintoshers.

The attached file is the EFI I use with this build. It works with both Big Sur and Mojave. I have removed my serial numbers, and disabled two SSDTs involved with TB3. You would need to use OpenCore Configurator, or other plist editor, to enter your own serial numbers in the PlatformInfo section of the config.plist file.

You could install the EFI folder in the EFI partition of a thumb drive, hold down the F12 key on boot and boot from the thumb drive to try it out without messing with your current setup.
 

Attachments

  • EFI_Z370_GAMING_7_OC_066.zip
    4.7 MB · Views: 90
@HackaShaq

Your build inspired me to duplicate it in June 2018, as reported in my Post #92. Without your detailed instructions I probably would have never attempted it. Since then I had upgraded the CPU to a i9-9900K, replaced the BeQuiet with a Corsair H115i Pro Cooler, installed a Fenvi card for WiFi and Bluetooth, and installed a flashed GC-Titan Ridge TB3 card.

I've also changed to using OpenCore instead of Clover, and currently have OC 0.6.6 installed running Big Sur on my build.

Over the past nearly three years I've built several more hackintoshes, all currently using OpenCore.

"If it ain't broken don't fix it." But you might want to consider moving to OpenCore as it seems to be a viable replacement for Clover and probably the go-to boot loader for hackintoshers.

The attached file is the EFI I use with this build. It works with both Big Sur and Mojave. I have removed my serial numbers, and disabled two SSDTs involved with TB3. You would need to use OpenCore Configurator, or other plist editor, to enter your own serial numbers in the PlatformInfo section of the config.plist file.

You could install the EFI folder in the EFI partition of a thumb drive, hold down the F12 key on boot and boot from the thumb drive to try it out without messing with your current setup.

@NCMacGuy this is great info and extremely helpful! Thank you!

I looked at the config file, and edited my serial and UUID that I found from "About This Mac" but the only difference was the "MLB" (board serial number) which needed to be replaced in your config file.

Since I still use Clover, I didn't have anything entered here (it's listed as blank "N/A" in the Clover parameters) and not included in my Clover config file at all. After googling, it looks like this is a 17 digit number with the first 12 being my Mac's serial number, and the last five being random. Is this correct?

I have a feeling I may be able to simply leave this blank, but I entered my Mac's serial + "12345" for the MLB.
Either that, or I could enter "Oakland Athletics" as my favorite "MLB" team. :)

Just wanted to check before editing this config file and testing things out.

Your info and EFI folder are much appreciated, and I sincerely thank you. Hard to believe that my build inspired you way back when, and I'm glad it did and I'm glad this community exists to keep helping people, including myself. Cheers!
 
With this hardware I would consider upgrading to macOS Catalina and/or Big Sur. Both are very stable using OpenCore.
I'm running 10.15.7/CLover using this same build without any issues and I upgraded my video card to an 5700XT Nitro+ about a month ago flawlessly.

I cannot, for the life of me, get OC to work with this board after several attempts.

Have you been successful?
 
Back
Top