Recently Browsing
0 members

Announcements

Similar Content

I have been working to move my Late 2009 Xserve MacOS Server onto Ubuntu 18.04 LTS QEMU/KVM based virtual machine using OVMF and Clover.

After much effort and testing based on the following information from: Kraxel's, Kholia, Gordon Turner and Clover site:
https://www.kraxel.org/blog/2017/09/running-macos-as-guest-in-kvm/
https://github.com/kholia/OSX-KVM
https://gist.github.com/gordonturner/2a2e5ecde5e7860b52e2
https://clover-wiki.zetam.org/Home

I have now managed to get OVMF/Clover boot and install of MacOS Sierra.

I started with Ubuntu 16.04 initially but this required download and compile of QEMU to get update of machines to: pc-q35-2.9 or better, so I moved to Ubuntu 18.04, which has pc-q35.2.11 available as standard.

So I am now working with standard Ubuntu 18.04 LTS based systems with following packages: kvm/qemu/libvirt/bridge-utils/ovmf/virt-manager

As I want to use PCIe Passthrough for a number of PCIe card currently installed in the server (SmallTree 10GbE & Areca ARC-1883 SAS RAID) I set up my machine with linux kernel boot configuration (/etc/default/grub) of:
GRUB_CMDLINE_LINUX_DEFAULT="iommu=1 intel_iommu=on" (as my machine is intel VT-d based HW virtualisation)

This resulted in creation of a number of iommu groups (see /sys/kernel/iommu_group directory for this and this posting for information: https://forum.level1techs.com/t/ubuntu-17-04-vfio-pcie-passthrough-kernel-update-4-14-rc1/119639 , noting that Ubuntu 18.04 LTS has kernel version: 4.15.0-22-generic so there is no need to do kernel update for iommu to work).

Using bare minimal Clover config.plist:

And following Clover UEFI drivers:

I can boot MacOS, but it is very very slow... it sits on the apple boot logo for over a minutes before finally moving onto the progress bar.
The other problem I have is that no PCI or Network devices appear in the "About This Mac" System Information Report and I cannot get any network connectivity from bridged E1000 network device.

Here is my virtlib.xml dump for the virtual machine:

Can any one advise of whether I need to update the CLOVER config.plist to add extra items in to allow network and PCI Passthrough to work.

Installing macOS® Sierra® on Gigabyte GA-Z170X-Gaming 5 rev 1.0
Intel® Core i7 6700K
nVidia® Graphics Maxwell® or Pascal®
Disclaimer:
This guide will assume that you know what you are doing and also assumes that you have already made a backup of your data before making any changes to your hardware or software. If you have not made a backup STOP HERE! and create one.
I will not be held responsible for any data loss or any damage you might cause to your computer in the process of installing macOS® on your computer.
By following this guide, you acknowledge that installing Mac OS X® and macOS® on any hardware that is not produced by Apple® is illegal and you will be responsible if you break any laws.
All the trademarks and copy rights belong to their respective owners.
This guide is only for your personal use and your information, therefore if you break any laws by using this manual you will be responsible for it not me. Any commercial use of the contents of this guide is prohibited.
If I forget to mention your name or someone else’s name in the credits section forgive my negligence and feel free to contact me and I will add your name/s.
This guide is written specifically for the hardware specifications I’m using, but the principal in general might apply to other hardware with similar specs with the exception of DSDT and SSDT files.
Important Notes:
1. Always backup your data before making any changes to your hardware or software.
2. Always keep a bootable Clover USB disk with the latest working configurations just in case.
3. I suggest you use another bootable USB for testing and not to edit the EFI folder on the hard drive.
4. Preferably use the latest BIOS (F21 at the time of writing) version and the latest version of Clover EFI bootloader (4077 at the time of writing).
5. There are two main versions of Clover EFI bootloader available in this package. One for the users with a nVidia GPU and the other one is for the users with IntelHD 530 GPU.
6. So many parts of this tutorial are universal and they apply to all Hackintosh and Apple computers, like creating the Bootable USB disk drive or mounting the EFI partition. So, you can use them on all the computers that run macOS or even use them for installing macOS on other Hackintosh computers.
7. The config.plist, the DSDT.aml file and the SSDT tables are specifically created for the GA-Z170X-Gaming 5 motherboard so do not use them on other hardware because they simply won’t work or even if they do you might experience some problems and errors.
8. This tutorial is based on my personal experience. So, you might need to make some extra adjustments.

Downloading the macOS® Sierra installer from App Store:
Download the version of macOS® you want to install on your computer from App Store, macOS® Sierra. For downloading the macOS® installer you’ll need an Apple® computer or a working Hackintosh and a valid Apple ID. Although downloading macOS® Sierra® doesn’t require an Apple ID but if you are going to use your Hackintosh for day to day use you’re going to need a valid Apple ID.
You can download the macOS® Sierra® installer by using the link below:
macOS® Sierra® 10.12.5:
https://itunes.apple.com/us/app/macos-sierra/id1127487414?mt=12&ls=1
You can also use App Store directly for downloading it. The “Install macOS® Sierra.app” will be saved to the following path once downloaded: /Applications/

Creating bootable USB Disk for macOS®:
Plug in a USB flash drive (8Gb or larger) and launch disk utility to format the flash drive.
To create a bootable USB drive for macOS®, everything must be exactly as shown in the picture below.
Once you successfully formatted the flash drive, open Terminal from /Applications/Utilities:
Copy and paste the following command into terminal without the “”:
For macOS® Sierra®:
“sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --applicationpath /Applications/Install\ macOS\ Sierra.app —nointeraction”
Press return/enter to run the command. You’ll be asked to give your password and once you type your password press return/enter and the process will start.
Depending on the speed of the USB drive you are using it will take about 5 to 30 minutes to complete the process. It took about 5 minutes on my computer to create the bootable disk on a USB 3.0 flash drive.

How to mount the EFI partition using command line:
Launch the terminal application again if you closed it previously.
Type “diskutil list” and press return/enter
You’ll see list of all the Internal and the external hard drives
Type “diskutil mount /dev/diskXsX” and press return/enter
First X is the number of the disk and the second X is the number of the partition
In this case the command will be:
e.g. diskutil mount /dev/disk2s1
Now you can see the EFI partition of disk6 is mounted on the desktop, if you can’t see the partition on the desktop you can find it in finder window’s “Sidebar” under “Devices”

BIOS Settings:
Now it’s time to configure the BIOS before installing macOS®.
First of all, it’s better to “Load Optimized Defaults” settings on the BIOS so we could start from scratch without having any misconfigurations.
You need to make the following changes to get macOS® working on your pc:
BIOS:
Fast Boot = Disabled
Windows 8/10 = Windows 8/10 WHQL or Other OS
CSM Support = Disabled
Secure Boot = Not Active
Attempt Secure Boot = Disabled
Peripherals
Initial Display Output = PCIe 1 Slot (Only If you are using a nVidia GPU, if you are using an AMD GPU you’ll need to enable IGFX and set it to primary in order to boot into macOS® Sierra®)
Trusted computing, Security Device Support = Disable
Super IO Configuration, Serial IO = Disable
USB Configuration, Legacy USB Support = Enabled
USB Configuration, XHCI Hand-off = Enabled
USB Configuration, USB Mass Storage Drive Support = Enabled
USB Configuration, Port 60/64 Emulation = Enabled
SATS And RST Configuration = AHCI
Chipset
VT-d = Disabled (If you need it add “dart=0” flag to config.plist under Boot section)
Internal Graphics = Disabled (Only If you are using a discreet GPU if you are using an AMD GPU you’ll need to enable IGFX and set it to primary in order to boot into macOS® Sierra®)
In Chipset, IOAPIC 24-119 Entries = Disable
If you are using Intel Graphics or IGFX
In Chipset, Internal Graphics = Enabled
In Chipset, DVMT Pre-Allocated = set it to 64
In Chipset, DVMT Total Gfx Mem = set it to max
Save and Exit.

Installing Clover EFI Bootloader:
In order to boot successfully into macOS® you’ll need to install a Bootloader on the drive you are using as the main bootable device whether is a flash drive or a hard disk drive.
There are number of bootloaders that could be used to boot up the macOS® on a PC computer or a Hackintosh but we will only use Clover EFI Bootloader and here is how to properly install and configure Clover EFI Bootloader on your computer.
In this section, we will be installing the UEFI version of the Clover so if you are using the Legacy BIOS version for whatever reason this guide is not for you.
You can download the latest version of Clover EFI Bootloader from:
https://sourceforge.net/projects/cloverefiboot/
As I mentioned before in the first page of this manual the latest version of the Clover EFI Bootloader is Clover_v2.4k_4077.

Stage 1:
Once you have downloaded the bootloader double click the installer package to start the installation process. The process will only take few minutes and after that you need to customize or optimize the contents of the EFI partition which you’ve installed clover into. Please make sure you select the USB drive you created earlier as shown below and not the HDD of the computer you are using.
If you see the following dialog after double clicking the installer package, all you need to do is to right click on the Clover_v2.4k_r4077.pkg and from the menu select open and once more click the open button.
Click continue and read the “Important Information” or not and then click continue once more.
You need to select the location that you want to install Clover EFI Bootloader to.
Make sure that you are installing clover to the right location, basically you must choose the drive that you have installed macOS® Sierra® onto unless you want to install the bootloader on another drive, say a flash drive.
Now you need to customize which components of the bootloader to be installed, if not you won’t be able to boot into macOS® at all.
Check the following items and then click install:
1. Install for UEFI booting only (Unified Extensible Firmware Interface)
2. Install Clover in the ESP (EFI System Partition) or (Extensible Firmware Interface System Partition)
3. Install can also choose a theme for your clover bootloader and the CloverThemeManager.app to change or modify the themes later.
4. Install Drivers64UEFI that apply to your system you will need at least these two drivers:
1. EmuVariableUefi-64
2. OsxAptioFix2Drv-64
You can also choose other drivers if they apply to your computer and if you need them, otherwise you’re good to go.
5. You can also install the RC script on the target volume to enable the shell command prompt in clover’s boot screen.
Once the installation is started, the EFI partition of the hard disk or USB drive that you are installing clover to will be mounted on the desktop, if you can’t see the partition on the desktop you can find it in the finder window’s “Sidebar” under “Devices”

Stage 2:
In this stage, you need to configure the config.plist and the other components on the EFI partition either by modifying the config.plist inside the /EFI/Clover/ folder using “TextEdit” or any other text editor application that you like or using “Clover Configurator” (recommended) application which has a GUI for editing the config.plist and it has some other useful built-in apps such as EFI mounter or a Base64 to HEX converter etc. or you can just simply replacing the “Clover” folder with the one that is provided with this guide.
At this moment you might not be familiar with all the settings and options inside the config.plist file and Clover Configurator, no need to worry.
You can easily replace the whole “Clover” folder inside the “EFI” folder on the EFI partition of your bootable disk (hard disk drive or USB flash drive) with the folder included with this guide and you’ll be good to go as along as your main components specifically your CPU and GPU are the same as mine.
Otherwise you might need some additional settings and flags to be added to the config.plist.
For instance, if you are using a NVMe SSD disk drive you’ll need to add proper patches in order to get it to work.
You can find more about clover and its settings at:
https://clover-wiki.zetam.org/Home

and you can find “Clover Configurator” at:
http://mackie100projects.altervista.org

How to enable kext using Clover EFI Bootloader:
In this section I will briefly explain how to install kexts that are needed to make your macOS® work more properly and efficiently.
As you know all the hardware components in a computer need a so called “Driver” to operate correctly in the operating system.
The same principle applies to macOS® and Mac OS X®. We call them “Kext” files or “Extension” files.
By default, Apple provides all the required kext files with the operating system to run on a legitimate Apple computer.
On the other hand, on a Hackintosh you need to install some extra kext files created by the community to obtain full functionality of your computer. You can either install them directly to “System/Library/Extensions” folder of macOS® Drive or you can place them into the EFI folder on the EFI partition of your bootable drive, which is a better way because if those files are the modified version of an original kext file that Apple is provided after each major update they will be replaced is the OS and you’ll lose the functionality of that particular component or more components.
For example, Maxwell and Pascal GPUs have the “Boot to black screen” issue with some SMBIOS settings like iMac17,1, iMac15 and MacPro 6,1 system definitions. It means if you use one of those system definitions your computer will show a black screen after loading macOS® even after installing the nVidiaWebDrivers.
So, you’ll need to either change the SMBIOS definition or you need to patch the “AppleGraphicsDevicePolicy.kext” to avoid the black screen.
Once you patch the file with whatever method, if you install macOS® update you’ll need to apply the patch all over again.
Besides changing the system files in macOS® will mix up the file permission of the files and if it’s not properly installed or if you forget to fix the permission of the files you might render the whole operating system useless and you’ll need to either fix the permissions on the /System/Library/Extensions or for short /S/L/E or you might need to reinstall the whole operating system from scratch.
For each version of macOS®, there is a folder inside the following path:
/EFI/Clover/kext/
So, you can copy the kexts you need inside the folder that correlates with the version of macOS® you are using.
Even if you update the OS, the files inside that path won’t get changed.
How to properly adding kext file to /System/Library/Extensions:
There are several ways to install additional kexts on macOS, but I will only discuss two methods that are the easiest ways to install kext without having to type any commands in terminal.

Using Kext Utility:
By using kext utility you can easily install kext files inside /System/Library/Extension.
All you have to do is to open the Kext Utility app, type in your password and drag the kext file you want to install into the app’s window and it will install them in to the path give above. The good thing about this app is that it will automatically repairs the permission of the /System/Library/Extension folder and the kext files inside it.
Once the process is done you can reboot the system and see the results.

Kext Wizard:
Kext wizard is another handy tool with more functions built into it, you can select the path for installing the kexts files even to another operating system on another volume.
You can repair the permissions and rebuild system kext cache. You can even load kexts files and test them or list the kext that are already loaded in the system.

Post Installation:
To have a fully functional Hackintosh you need to add the following kext files and DSDT/SSDT files and tables.
Kexts:
FakeSMC.kext https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek/downloads/
Audio:
AppleALC.kext
https://github.com/toleda/audio_CloverALC
Lilu.kext
https://github.com/vit9696
CodecCommander.kext v2.4.0 for Audio after sleep
https://bitbucket.org/RehabMan/os-x-eapd-codec-commander/downloads/RehabMan-CodecCommander-2015-0522.zip

Note:
Install CodecCommander.kext v. 2.4.0 inside /System/Library/Extensions/ and set darkwake=8 in config.plist to solve the audio after sleep issue.
I tried installing it inside /EFI/Clover/kexts/10.12 and /EFI/Clover/kexts/Other and it didn’t work.
I also tried other versions of CodecCommander.kext but none of them worked except for the v. 2.4.0.
If you don’t want to use Lilu.kext and AppleALC.kext and see the read the “Other methods for activating audio section”.
realtekALC.kext with https://github.com/toleda/audio_RealtekALC/blob/master/audio_realtekALC-120.command.zip
audio_cloverHDMI-120_v1.0d.command for HDMI Audio: https://github.com/toleda/audio_CloverHDMI/blob/master/audio_cloverHDMI-120.command.zip

Graphics:
IntelGraphicsFixup.kext https://sourceforge.net/projects/intelgraphicsfixup/ if you are using the Intel Integrated Graphics
Lilu.kext https://github.com/vit9696
NVidaiGraphicsFixup.kext https://sourceforge.net/projects/nvidiagraphicsfixup/

Note:
I also tested the system without USBInjectAll.kext and all my USB 2.0 and USB 3.0 ports were fully functional so it’s up to you whether to use it or not.

VERY IMPORTANT NOTE:
Before you start using macOS® Sierra®, you need to change the SMBIOS of the config.plist:
You have to change the SMBIOS settings before starting to use macOS® Sierra®, because the config.plist that is included in this guide doesn’t have a serial number for your Hackintosh, so you won’t be able to use any of Apple’s services without a serial number and a hardware UUID. It’s imperative to do so specially if you are going to use your Hackintosh for daily use. If you don’t change the serial number you won’t be able to use App Store, iCloud, iMessage etc. It’s highly recommended that you use iMac 17,1 SMBIOS as your default. iMac 17,1 and iMac 17,2 models use Skylake processors in Apple's original iMacs.
For changing the SMBIOS you can use the built-in wizard inside “Clover Configurator” under SMBIOS Section. To open the wizard, click the small magic wand on the right side of the window to use the wizard.

Audio:
By using the EFI folder included with this guide and by using the patched DSDT/SSDT tables, “AppleALC.kext” and “Lilu.kext” you won’t need to do much to make the audio active on your Hackintosh.
Just install the macOS® Sierra®, copy the EFI folder and audio is activated by default, HDMI audio will be active once you install nVidiaWebDrivers and restart the computer.
If the audio didn’t work, you can rebuild prelinked kernel and kexts cache by using the following commands in terminal:
1. sudo nvram -c
2. sudo purge
3. sudo rm -f /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache && sudo touch /System/Library/Extensions && sudo kextcache -u /
sudo update_dyld_shared_cache -force
Or you can use “Kext Utility” to repair permissions on /System/Library/Extensions and /Library/Extensions and also it will also rebuilds the system cache for you.
Kext Utility could be found at:
http://www.insanelymac.com/forum/index.php?app=core&module=attach&section=attach&attach_id=186603

Note:
If you see the following output in terminal it means that you forgot to mount the EFI partition, mount it and run the command again.
EFI partition not mounted
Boot/EFI not found
EFI/CLOVER folder not available to install audio
No system files were changed
To save a Copy of this Terminal session: Terminal/Shell/Export Text As ...
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
[Process completed]

Other methods for activating the Audio:
1. audio_codecdetect.command
This command will give you useful information about the audio chipsets and devices that are available on the system, after you run the command, the output will be like this:
cdetect_v2.2.command ; exit;
File: audio_codecdetect.command_v2.2
HDMI audio codec(s)
Nvidia: 0x10de0083
Onboard audio codec
Realtek: 0x10ec0900
Name: Realtek ALC1150
Audio ID: 1
Valid audio codec, audio device and Audio ID; audio injection is working
Finished
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
[Process completed]

This means that the audio chipset is supported and you can go to the next step of installing the audio using Toleda's scripts.

3. HDMI Audio
For activating the HDMI Audio for you need to run audio_cloverHDMI-120.command
This command will detect the audio codec for you integrated graphics and discrete GPU and will add the proper SSDT table to /EFI/Cover/ACPI/patched folder
Agreement
The audio_cloverHDMI script is for personal use only. Do not distribute
the patch, any or all of the files for any reason without permission.
The audio_cloverHDMI script is provided as is and without any warranty.
File: audio_cloverHDMI-120.command_v1.0d
Release Mode
EFI partition is mounted
No HDMI audio codec(s) detected, continue (y/n): y
HDMI audio codec(s)
Integrated Graphics is not installed/enabled
Install AMD/Nvidia HDMI audio (y/n): y
Nvidia discrete graphics card 10de1b81 found on PEG0@1/PEGP@0
Nvidia HDMI audio is not enabled
Install Nvidia HDMI audio ssdt (y/n): y
Download SSDT-HDMI-NVIDIA-PEG0 ...
Password:
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 44888 100 44888 0 0 39094 0 0:00:01 0:00:01 --:--:-- 39101
/Volumes/EFI/EFI/CLOVER/ACPI/patched/SSDT-HDMI-NVIDIA-PEG0.aml installed
Install finished, restart required.
To save a Copy of this Terminal session: Terminal/Shell/Export Text As ...
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
[Process completed]

Audio Troubleshooting:
If after running the audio_cloverHDMI-120_v1.0d.command you see the following statement
“Agreement
The audio_cloverHDMI script is for personal use only. Do not distribute
the patch, any or all of the files for any reason without permission.
The audio_cloverHDMI script is provided as is and without any warranty.
File: audio_cloverHDMI-120.command_v1.0d
Release Mode
EFI partition is mounted
Error: no IOReg/HDEF; BIOS/audio/disabled or ACPI problem
Continue without HDEF/onboard audio (y/n): y
No audio codec detected
No system files were changed

It means you either don’t have a patched DSDT.aml file or SSDT tables and no patches are present inside the config.plist so you need to either add the DSDT/SSDT tables or add patches yourself.
Don’t be alarmed it’s so easy.
Open clover configurator and after mounting the EFI partition, open the config.plist and add the following patch :
Under ACPI, DSDT patches select “change HDAS to HDEF” from “List of Patches” and this will add the following code in the config.plist
</dict>
<key>Comment</key>
<string>change HDAS to HDEF</string>
<key>Disabled</key>
<false/>
<key>Find</key>
<data>
SERBUw==
</data>
<key>Replace</key>
<data>
SERFRg==
</data>
</dict>
or
Comment: change HDAS to HDEF
Find*[HEX] 48444153
Replace*[HEX]48444546

Graphics:
This section will be dedicated to nVidia GPUs specially Maxwell and Pascal. If you are using any other nVidia or AMD graphics you can skip this section.
We tested these instructions on an EVGA 1070 Superclocked GPU and a Gigabyte nVidia GeForce GTX960 GAMING-4GB (Please include the brand for reference).
As you might know the 10 series nVidia GPUs or Pascal are not compatible with Mac OS X El Capitan and earlier versions of macOS® but 9 series and Maxwell are compatible and they both need nVidiaWebDrivers to be fully functional.
For macOS® Sierra® 10.12.5 you’ll need to download 378.05.05.15f01
https://images.nvidia.com/mac/pkg/378/WebDriver-378.05.05.15f01.pkg
Solution 1:
If you are looking for an easy way to get the GPU working all you have to is to copy the Lilu.kext and nVidaiGraphicsFixup.kext inside the kext folder in clover EFI bootloader.
The full path is /EFI/Clover/kext/10.12
Once you finished installing macOS® and nVidiaWebDrivers you’ll need to add the following flags and setting to the config.plist
Under “Boot” section add or remove nvda_drv=1 if necessary. I don’t need to use it on my computer.
You don’t need to inject anything in “Graphics” section
Under “System Parameters” check “NvidiaWeb”
When installing Clover EFI bootloader under “Drivers64UEFI” install “EMUVariableUefi-64” // I also use OsxAptioFix2Drv.efi, never tested without it.
and that’s it!

Solution 2:
If you don’t want to use nVidaiGraphicsFixup.kext you only have two options:
1. Run AGDP-fix.app to edit the “AppleGraphicsDevicePolicy.kext” to fix “Boot to Black Screen” issue
2. Or you can edit the “AppleGraphicsDevicePolicy.kext” manually using terminal.
If you choose the second solution for any reason remember after each major update you need to apply the patch all over again.

Wi-Fi:
TP-Link WDN4800 works out of the box without any hassle.
The only problem that you might encounter with it is "ATHR: unknown locale: 21" error in the verbose boot.
The Atheros patch is to avoid the series of "ATHR: unknown locale: 21" messages in the verbose boot which they will be registered in message console's logs and they will make the log file bigger. The patch will fix the WiFi location and will stop the error and therefore there will be no more logs.
Without the patch, the WiFi will work just the same but with lots of messages in the log.
If you don’t use the TP-Link WDN4800 you can remove the patch or simply leave it as disabled.

USB 3.0:
Under Kernel and Kext Patches add the following to “KextsToPatch”:
This patch will raise the limit of the USB ports from 15 to 26.
For macOS® Sierra
Name*: AppleUSBXHCIPCI
Find* [HEX] : 83bd74ff ffff10
Replace [HEX] : 83bd74ff ffff1b
Comment: Raise change 15 port limit to 26 in XHCI kext (100-series)
MatchOS: 10.12.x
You also might need to add RehabMan’s “USBInjectAll.kext” to the following path under “/EFI/Clover/kexts/10.12” for macOS® Sierra
Note:
If you are using a patched DSDT or SSDT tables you don’t need to use any DSDT patches in clover and the “USBInjectAll.kext” you will have full functional USB 2.0 and USB 3.0 ports. I didn’t test USB 3.1 ports because I have no USB 3.1 device to test it!
The port limit patch must only be temporary, you will need to create your own custom SSDT-UIAC to only inject the ports you use.

The USBInjectAll.kext provided in this guide needs to be and stay installed.
Download ioregistryexplorer Version 3.0.3 from http://mac.softpedia.com/get/System-Utilities/IORegistryExplorer.shtml
or download IOJones which is an alternative to IORegistryExplorer at: https://sourceforge.net/projects/iojones/
Download MaciASL from https://bitbucket.org/RehabMan/os-x-maciasl-patchmatic/downloads/RehabMan-MaciASL-2017-0117.zip and extract, drag MaciASL.app into /Applications. (Credit RehabMan)
Download OS-X-USB-Inject-All Master from: (Credit RehabMan)
https://github.com/RehabMan/OS-X-USB-Inject-All/archive/master.zip
and extract the zip file.
Inside the OS-X-USB-Inject-All-master folder you will find SSDT-UIAC-ALL.dsl, copy it to your desktop.
Open ioregistryexplorer and find your device id by typing XHC in the search field.
Open SSDT-UIAC-ALL.dsl with MaciASL and find your appropriate device id section.
Remove all other sections in the SSDT-UIAC-ALL.dsl that do not correspond with your device id leaving just the one section. Skylake does not have a EHCI controller so “HUB1”, ”HUB2”, ”EH01”, "EH02" can be removed and in my case I can also remove "8086_1e31", "8086_8xxx", "8086_9xxx", "8086_9cb1", "8086_9d2f" and "8086_a2af".
Compile the file to make sure there are no errors in the code and then save the file with “ACPI Machine Language Binary”.
Now we turn our attention to ioregistryexplorer, while you have ioregistry open go to the XHC section and take note of the HSxx or SSxx locations that have devices attached. Now plug in a USB 2.0 device into all USB 2.0 you NEED and do the same with USB 3.0 ports with USB 2 and 3 devices and take note of them all.
Returning back to the SSDT-UIAC-ALL.dsl you will see all ports listed, you need to remove the ones you did not take note of and you can also add a comment to the ones you keep.
UsbConnector values = USB 2.0 = 0, USB 3.0 = 3. Internal = 255
USB 2.0 devices plugged into USB 3.0 ports HSxx are still marked as USB 3.0 = 3.
Internal devices such as Bluetooth etc are marked as 255
Once you gone through and done this to all the devices you need and removed the ones you don’t you can save your SSDT-UIAC-ALL.dsl in MaciASL. Make sure you rename it to SSDT-UIAC and that the file format is ACPI Machine Language Binary
Copy and paste the resulting SSDT-UIAC.aml into your EFI/EFI/CLOVER/ACPI/patched folder.
Disable the port limit patch in config.plist and add SSDT-UIAC.aml into SortedOrder if needed.
Reboot.

Open ioregistryexplorer and test the ports you left enabled USB 2 & 3.
The number of ports you should see in ioreg should be significantly reduced as they are not being injected anymore.

Special Thanks to:
I would like to thank MaLd0n for providing the patched version of DSDT and SSDT tables and SavageAUS for doing such a great work on helping me to write this tutorial and testing the files and also writing the “Custom SSDT-UIAC” section.
I also would like to thank:
Vit9696 for Lilu.kext
RehabMan for CodecCommander.kext FakeSMC.kext, IntelMausiEthernet.kext, USBInjectAll.kext.
Toleda for AppleALC.kext, Audio commands and kexts
netkas for FakeSMC.kext
lvs1974 for IntelGraphicsFixup.kext and NvidiaGraphicsFixup.kext
hnak for AppleIntelE1000e.kext
Mieze for IntelMausiEthernet.kext
apianti, blackosx, blusseau, dmazar, slice2009 for Clover EFI Bootloader
http://mackie100projects.altervista.org for Clover Configurator
Apple Inc. for macOS® and great many other products.
And many other great people whom make Hackintosh possible!

Hi guys, this thread is to show you a new and open source app, created by me, that I called TINU:

The name means: TINU Is Not #####, the U refers to a popular software that is used to create Mac OS hackintosh installers (that for good reasons is banned on this forum), but the aim of the name is to explain that this app is a totally different thing from that software and works in a totally different way.

This app basically is a graphical interface for the createinstallmedia executable that is inside the Mac OS installer apps, it is capable to create a Mac OS installer on a drive completely vanilla like what you do using the command line method, and also this method is recommended by apple itself.

Allows you to create easily a macOS install media without messing around with command line stuff and without using disk utility, all you need to do is use the app and then install clover on the usb drive once TINU has finished or leave it as is you want to use it on a Mac.

Features:
- Simple to use UI that allows you to easily start the macOS install media creation process
- It can work with every Mac OS installer app that has the createinstallmedia executable inside of it's resources folder (including also beta and newly released installers)
- You can use any drive or partition you want that can be erased and is at least 7 GB of size
- Works on Mac OS recovery, so you can create a macOS install media from a bootable macOS installer or from the macOs recovery
- All vanilla, the macOS install medias created with this tool are 100% vanilla, just like you created them using the command line "createinstallmedia" method
- Open source, you will know what this program does on your computer and also you can create your own version by downloading and playing with the source code
- Does not requires to do anything of special first, just open the program
- No need to go in disk utility first, TINU can format your drive for you
- Uses recent and more modern APIs and SDKs and Swift 3 language
- Transparent graphics style available (use alt + s on the keyboard or View->Use transparent style)
- Works using the latest versions of macOS and will also support newer Mac installers out of the box without needing for an update
Features that I'd like to add in the future:
- Advanced section, to customize your macOS install media
- Installer customization: Kernelcache/prelinkedknerel and boot files replacement (a feature that can be handy while dealing with old Macs or with beta installers when you need to mod or change the boot files some times)
- Install clover and configure clover
- Install kexts inside the kexts folder of clover
- Clover drivers customization
- Use custom dsdt in clover
- integrated pre-made clover config templates database from a remote and open repository
- Support for other languages, at least Italian
Rquirements:
- A computer that runs Mac OS X Yosemite or a more recent version (Mac OS X El Capitan is required to use TINU in a macOS recovery or installer)
- A drive or a free partition of at least 7 GB that you want to turn into a macOS/Mac OS X installer
- A copy of a macOS/Mac OS X installer app (Maveriks or newer versions are supported) in the /Applications folder or in the root of any storage drive in your machine (excepted the drive or volume you want to turn into your macOS install media)
Note that this app is under the GNU GPL v3 license so any reuse of the source code must follow the license's terms
TINU 1.1 Stable release:
- Download available here:
https://github.com/ITzTravelInTime/TINU/releases
- Source code:
https://github.com/ITzTravelInTime/TINU
TINU 2.0 pre-release:
- Source code:
https://github.com/ITzTravelInTime/TINU/tree/development
- Download available here:
https://dl.dropboxusercontent.com/s/nvzss51qcieynve/TINU.zip
Frequently asked questions about TINU:
https://github.com/ITzTravelInTime/TINU/wiki/FAQs
NOTE: if you have problems with your USB installer of 10.13.4 or newer version not being detected by clover you have to use the latest clover and if it still does not detectets your usb installer you have to remove the invivible file called .IAPhysicalMedia located into the root of the usb installer. This issue is caused by a changement in the apple's createinstallmedia, don't blame TINU for that, tinu does only uses the installer creation method from apple, which has been changed, causing this problem for hackintosh users, this issue should be resolved in the latest versions of clover which will no longer require that you do changements to let your usb dive to be detected, a setting to do this fix automatically in tinu is also comeing in a new pre-release of TINU 2
I leave also some screenshots as well

Updated for newer Clover versions and with additional instructions for more apps: gdisk and RU.

So what may be overlooked sometimes in the whole boot loader discussion is the ability of UEFI to do more than just loading an OS. This is why I see ".efi" files as "apps" because in fact they just are, built on a special kind of API: UEFI. So, you can actually do stuff like editing, diagnosing, testing certain stuff at the lowest possible system level without booting to any OS.

DISCLAIMER: Use this guide at your own risk! For educational purposes only! Should do not any harm, but remember you are dealing with rather low level stuff. But at least for me everything went flawless.

Prerequisites:
Working clover installation
Clover Configurator or some app to edit the config.plist
1) Memtest

This is how to install the UEFI version of Memtest with Clover:
Download memtest, I used this link: Image for creating boot-able USB Drive
Open the archive by double clicking on it.
Mount the file memtest86-usb.img within by double clicking again.
Now, you should see a folder named EFI in this volume, containing a folder BOOT. Open it.
The files containing it are the actual app, in 32 and 64 bit versions. Think in almost all cases we want to use the 64 bit version.
Now, mount your EFI partition, using Clover configurator.
Create a folder named MemTest86 in the EFI folder on your main drive.
Copy all files in the EFI/BOOT folder from the mounted image to your newly created folder.
That ends the basic setup! Now, we add the correct Menu entry to the clover boot menu, so that we can actually start this app.

Get into clover configurator, open your standard config.plist from your boot drive and go to the GUI section. Under "Custom Entries", add an entry like this:

Please note while the path you enter is not case sensitive, you must make sure you use the backslash "\" for entering paths, and not a slash. So basically what we do is tell clover where it can find the app, give it a name, and tell clover it is a "Windows" app. Note: with older Clover versions we had to set this to "Linux", but for now "Windows" is the setting that works.

If you prefer to do a manual config, add this entry to your config.plist, under GUI/Custom/Entries:
<dict>
<key>CustomLogo</key>
<true/>
<key>Disabled</key>
<false/>
<key>FullTitle</key>
<string>MemTest86</string>
<key>Hidden</key>
<false/>
<key>Ignore</key>
<false/>
<key>Image</key>
<string>\EFI\CLOVER\themes\Icons\os_mint.png</string>
<key>Path</key>
<string>\EFI\MemTest86\BOOTX64.efi</string>
<key>Type</key>
<string>Windows</string>
<key>VolumeType</key>
<string>Internal</string>
</dict>
Now, save and reboot and you should see the newly created entry. Note that I also used a custom Icon - this is optional - in case you don't you will just see a generic windows icon instead:

And this is how it looks like:

PS: also noticeably faster and you get also more features with this version than with the older version, for example it does now write a log file. For more Information, see: http://www.passmark.com/forum/showthread.php?4315-Memtest86-Version-5-Beta-%28Pure-UEFI%29

2) gdisk

Another app you can use is the UEFI version of gdisk (aka GPT fdisk), which you can use to edit and change your partitions.

Warning! Install and use this app at your own risk! If you do something wrong here you might nuke your drive(s), so only use that if you know what you are doing.

This is how to do it (even easier):
Download here: https://sourceforge.net/projects/gptfdisk/files/gptfdisk/1.0.1/gdisk-binaries/gdisk-efi-1.0.1.zip/download
Mount your EFI partition
Unzip the file and copy the resulting folder to your EFI Folder, so your path goes like this "/Volumes/EFI/EFI/gdisk-efi"
Get into clover configurator, open your standard config.plist from your boot drive and go to the GUI section. Add an entry like this:
If you prefer to do a manual config, add this entry to your config.plist, under GUI/Custom/Entries:
<dict>
<key>CustomLogo</key>
<false/>
<key>Disabled</key>
<false/>
<key>FullTitle</key>
<string>GDisk</string>
<key>Hidden</key>
<false/>
<key>Ignore</key>
<false/>
<key>Image</key>
<string></string>
<key>Path</key>
<string>\EFI\gdisk-efi\gdisk_x64.efi</string>
<key>Type</key>
<string>Windows</string>
<key>VolumeType</key>
<string>Internal</string>
</dict>
When everything went OK you should see this after selecting the respective entry in Clover:

3) RU

I recently found one more app that might be interesting to some, and thats "Read Universal" or in short "RU". This is a tool that enables you to debug your BIOS and read (and modify!) every imaginable data, including UEFI variables, ACPI Tables etc.

Warning, again! I think blindly messing around with this app is even more dangerous, but on the other hand it gives you access to a lot of potentially interesting stuff.
Download here: http://ruexe.blogspot.de/
The next steps are basically the same as above so make a folder in your EFI partition, copy the .EFI files and make another custom entry in your config.plist
Here are some screens:

So this is what you also can do with UEFI and clover. I am curious which other useful applications might exist!

Hello everybody,
I occasionally have system crashes and suspect that it is related to RAM. However, this RAM is completely new, and a run with MemTest86+ from the USB stick showed no errors. However, if I use Memtest on MacOS, I get a bunch of error messages, but sometimes none (I restart the computer between tests).
As I just discovered, my RAM is not on the recommended vendor list of my motherboard, nor is it on the manufacturer side of the RAM. I have read several times that the RAM may not have been tested by the manufacturer on this platform. Not a single X99 motherboard is listed for this RAM.
So I also suspect that my RAM is not compatible.
But if that were the case, how could it sometimes work completely error-free?

During RAM tests in summer 2017 (a slightly different setup, 4x8GB but still G.Skill Ripjaws V) I had no errors at Memtest under MacOS, if I remember correctly. At that time it ran under Sierra 10.12.6. AptioMemoryFix.efi could also cause problems.
I am appreciative for any help!