One USB installer for all your hacks.
Have you been bitten by the bug and have gotten addicted to hackintoshing and have multiple hacks? Do you keep a USB macOS installer with EFI folders for each of your hacks?
I like keeping USB installers with known working EFI folders around in the event that something goes horribly wrong with my boot drive so that I can boot and make repairs. The problem was that I had multiple USB installers all serving the same purpose. But there's a better alternative. Make a single USB installer with an EFI folder with all the kexts and ACPI patches needed to boot each of my systems. Here's how to do it...
1. Create a USB macOS installer using UniBeast.
2. On your working hack, boot up and, at the Clover boot menu, press F2.
3. Navigate to /EFI/CLOVER/misc/.
4. You will find a file named preboot.log. Open this file with TextEdit (any text editor will work but, for simplicity, I will just use TextEdit in these directions).
5. Search (Command+F) for "Running on:"
6. Here, we will find the name used by the manufacturer of the motherboard for this particular model.
7. Copy (Command+C) this name without the parentheses.
8. Create a new folder on your desktop and paste the name.
9. Navigate to /EFI/CLOVER/ and copy (Command+C) the (1) ACPI folder, (2) config.plist, and (3) kexts folder.
10. Paste (Command+V) those 3 items to the folder you just created on your desktop.
11. Repeat Steps 2-10 on all your hacks.
12. Copy these folders from each of your hacks to the /EFI/CLOVER/OEM/ folder on your USB installer.
Congratulations. You now have a single USB macOS installer that can be used on all of your hacks.
*Notes:
- This will only work if all your hacks use UEFI Clover and can boot from the same files in /EFI/CLOVER/Drivers64UEFI/.
This will only work if all your hacks use the standard macOS (as opposed to the special macOS builds for iMacPro1,1). It will also work if all of your hacks use the iMacPro1,1 build. As of macOS 10.13.4, Apple has unified the iMac Pro builds with the regular builds.
- Sometimes the system product name will look like the following. Try with product name or board name. Either should work:
Update:
If your systems require different sets of Clover drivers, please follow the directions outline
here.