Recently Browsing 0 members
No registered users viewing this page.
MOJAVE HACKINTOSH GUIDE
**FOR** GIGABYTE Z390 AORUS PRO
CREDITS & THANKS
His help with EFI configuration and DSDT
Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, rehabman, Download-Fritz, Zenit432, cecekpawon Et al
autumnrain, slice2009, zenith432
ESP PRO MOUNTER
JoniVR & theOneyouseek
• Intel I7 8700
• Gigabyte Z390 AORUS PRO
• Gigabyte AORUS RADEON RX 580 8GB ( connected to monitor with DisplayPort )
• Corsair Vengeance LPX 16GB ( 2 x 8GB ) 2666MHz – CMK16GX4M2A2666C16 In this build, both memory modules are installed in memory slots DDR4_A1 and DDR4_B1
• Corsair RM650x 80 Plus Gold Power Supply Unit
• Corsair H100i V2 AIO Hydro/Water RGB LED CPU Cooler
• Samsung EVO 500GB SSD (2.5) macOS Mojave
• Samsung EVO 250 GB SSD (2.5) Windows 10 Pro
• NZXT H500 Mid Tower ATX Case
• RECOMMENDED WIFI CARD → ABWB 802.11AC WI-FI With Bluetooth 4.0 PCI-Express (PCI-E) BCM943602CS
• WIFI and Bluetooth with BCM94331CD with PCI-e adapter (but will require AirportBrcmFixup.kext for AirDrop.. )
** Avoid Samsung EVO 970 PLUS as Hackintosh has problem with that device **
• HDMI Port on AMD RX580 / 590 ( Ensure you disable BIOS CSM if using HDMI on RX580 / RX590 )
• HDMI Port on Aorus Z390 Motherboard ( Ensure you have correct BIOS settings as per this guide for Intel only)
• Ethernet Port
• SSD Trim
• USB 3.0 & 2.0
• Hardware Acceleration
PART 1 - DOWNLOAD
Download the following:
• PRE-INSTALL Aorus Pro Z390 EFI - RX580.zip
• POST-INSTALL Aorus Pro Z390 EFI - RX580.zip
// INTEL UHD 630 EFI Aorus Pro Z390 EFI's below. For those who do not have a Graphics Card Installed in PCIe Slot, requires Initial Display Output BIOS setting to be changed to IGFX spoiler below!
• PRE-INSTALL Aorus Pro Z390 EFI - Intel UHD630.zip
• POST-INSTALL Aorus Pro Z390 EFI - Intel UHD630.zip
• ESP MOUNTER PRO v1.9
• macOS MOJAVE
• CLOVER CONFIGURATOR
• EmuVariableUefi-64.efi ( Used only to initialise iMessages. It then must be removed from Clover drivers64UEFI folder as will cause intermittent memory allocation errors on boot, explained in guide)
• Native Display Brightness with MonitorControl
PART 2 - BIOS SETTINGS (version F5 )
Here is a list of the BIOS settings that I have used ( Screenshots in spoiler below )
• Enter BIOS → Press F12 → Enter Setup
• Save & Exit → Load Optimized Defaults
• BIOS → Windows 8/10 Features → Other OS
• BIOS → CSM Support → Enabled
• Peripherals → Initial Display Output → PCIe 1 Slot
• Peripherals → Trusted Computing → Security Device Support → Disable
• Peripherals → Intel(R)Bios Guard → Intel BIOS Guard Support → Disable
• Peripherals → USB Configuration → Legacy USB Support → Enabled
• Peripherals → USB Configuration → XHCI Hand-off → Enabled
• Peripherals → Network Stack Configuration → Network Stack → Disabled
• Peripherals → SATA And RST Configuration → SATA Mode Selection → AHCI
• Chipset → Vt-d → Enabled
• Chipset → Internal Graphics → Enabled
• Chipset → DVMT Pre-Allocated → 256M
• Chipset → DVMT Total Gfx Mem → 256M
• Chipset → Audio Controller → Enabled
• Chipset → Above 4G Decoding → Disabled
• Power → ErP → Disabled
• Power → RC6 (Render Standby) → Enabled
// IF USING CORSAIR H100i V2 AIO CPU WATER COOLER
• MIT → Smart Fan 5 Settings → CPU Fan Control mode → PWM
• Save & Exit → Save & Exit Setup
SCREEN DUMP SPOILERS
PART 3 – CREATE A MOJAVE USB FLASH INSTALLER
Prepare USB Installer for Mojave ( Video below )
• Insert USB drive
• Launch /Applications/Utilities/Disk Utility
• Disk Utility → View → Show All Devices
• On Left-hand panel → External →(Identify your USB device in left hand panel)
• Click and highlight your USB device in the left-hand panel.
• Click erase button.
• Name: USB
• Format: Mac OS Extended (Journaled )
• Scheme: GUID Partition Map
• Click Erase button.
• Place the downloaded MacOS Mojave app into Applications folder.
• Open Terminal copy and paste:
sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --nointeraction && say Mojave Drive Created • Enter
PART 4 – INSTALL CLOVER ON THE MOJAVE USB INSTALLER
Make Mojave USB flash drive installer bootable.( Video below )
• Launch Clover application, double click.
• Click Continue → Continue → Continue
• Click Change Install Location button.
• Click Install macOSMojave USB installer → Continue
• Click Customise button
Clover for UEFI booting only Install Clover in the ESP Themes UEFI Drivers Install RC scripts on target volume NO NEED TO INSTALL RC SCRIPTS ON USB INSTALLER • Click Install button
• Installation Complete!
PART 5 – CUSTOMIZE MOJAVE USB INSTALLER FOR AORUS Z390 PRO
Replace Clover EFI folder with PRE-INSTALL Aorus Pro Z390 EFI - RX580.zip OR if NO graphics card installed in PCIe slot, then use PRE-INSTALL Aorus Pro Z390 EFI - Intel UHD630.zip( Video below )
• Install ESP Mounter Pro v1.9
• Using ESP Mounter Pro, Mount ESP on disk2s1 ( Your disk name may be different )
• Open mounted EFI partition found on desktop
• Copy all the contents from Aorus 390 Pro EFI folder
• Replace USB EFI folder with all the contents inside the Aorus 390 Pro EFI folder.
PART 6 – INSTALL MAC OS MOJAVE ON INTERNAL DRIVE
ENSURE BIOS: Above 4G Decoding is set to Disabled
if Above 4G decoding is set to enabled then macOS Mojave install will freeze at 2 mins remaining and will not shut down properly!!!!
Please be patient during install, so when install gets to 2 or 3 mins remaining then it may take extra time. Be ready to boot from UEFI USB installer by pressing F12 when install initiates restarts.
• INSERT USB INSTALLER INTO THE USB 2.0 PORT
Here is a walkthrough of the full process using the macOS Mojave USB Installer on the Aorus Z390 Pro.
• Power on PC and press F12• Choose bootable USB drive from boot menu.
• Install macOS Mojave to internal solid state or hard drive.
When system returns to the Clover boot menu choose:
• Boot macOS Install from Macintosh
At next restart, press F12 and boot from external UEFI USB device and choose:
• Boot macOS Install from Macintosh
Proceed with macOS Mojave install
macOS Mojave is now installed, but it can only boot at this moment thanks to FakeSMC and Clover on the Mojave USB flash drive installer.
PART 7 – MAKE AORUS Z390 PRO INTERNAL DRIVE BOOTABLE
Make internal drive bootable ( Video below )
So far, the Aorus Pro can only boot the internal system drive with the aid of the Mojave USB Installer.
To boot from the internal system drive without the installer:
Download and install Clover with RC Scripts on target volume.
If your Aorus Pro Z390 has AMD RX 580 then copy the EFI folder from inside POST-INSTALL Aorus Pro Z390 EFI - RX580.zip folder and paste it inside the the System Drive EFI partition. OR
If your Aorus Pro Z390 has no graphics card installed in PCIe slot, then copy the EFI folder from inside POST-INSTALL Aorus Pro Z390 EFI - Intel UHD630.zip folder and paste it inside the the System Drive EFI partition.
• Remove USB Mojave installer and shut down and restart.
Aorus Hackintosh should now be able to boot to macOS Mojave, Done, well almost !
PART 8 – ENABLE IMESSAGES & FACETIME
Configure Config.plist for iMessages. ( Video below )
• SMBIOS = Mac Mini 8.1
• Rt Variables —> ROM —> is your MAC address (delete colons from Mac address)
• MLB field = Enter serial number generated and append 5 random characters
• SmUUID = in Terminal run command “uuidgen” and copy it to SmUUID field
• Board Serial is same as MLB field.
• Clover Configurator —> Save
• Mount internal drive EFI/ESP partition
• Go to folder CLOVER → drivers64UEFI
• Delete AptoMemoryFix-64.efi
• Place both EMUVariableUefi-64.efi and OsxAptoFix2Drvfree2000.efi inside → drivers64UEFI
Using Clover Configurator, add the following argument to config.plist using Clover Configurator.
• Slide = 0
Shutdown and then press power on button on PC.
• You should now be able to Log into iCloud, iMessages and FaceTime
• NOW delete EMUVariableUefi-64.efi from CLOVER → drivers64UEFI Folder
• Shutdown and restart Aorus Pro hackintosh. iMessages etc is now operational without EMUVariableUefi-64.efi ( EMUVariableUefi-64.efi only needed to initialise iMessages )
• It is important to delete EMUVariableUefi-64.efi, this will avoid very intermittent boot errors such as: “Couldn’t allocate runtime area” post errors.
PART 9 – ENABLE TRIM for Solid State Flash Drives
Open Terminal and enter the following command:
sudo trimforce enable
DEFAULT SSDT – USB PORTS FIX CONFIGURATION WITH FRONT USB-C - SSDT ALREADY INSIDE AORUS Z390 EFI FOLDER – Provided by @AudioGod
If you have USBC on Computer Chassis / Case, then SS01 and SS02 is mapped to that USB C port
------------ GUIDE FINISHED YOU SHOULD NOW HAVE WORKING AORUS Z390 PRO HACKINTOSH WITH SSDT USB FIX ------------
OPTIONAL: Set Wi-Fi Country Code
OPTIONAL: System Information - PCI
OPTIONAL: Enable HDMI Audio on RX580
OPTIONAL: Native Display Brightness - with MonitorControl
OPTIONAL: Dual Boot macOS Mojave & Windows 10
OPTIONAL: Replace the default "About This Mac" Apple Logo with RED AORUS APPLE
OPTIONAL - ALTERNATIVE SSDT 1 – SSDT Ports configuration below - replace SSDT inside Clover /ACPI/PATCHED folder
OPTIONAL - ALTERNATIVE SSDT 2 - SSDT Ports configuration below - replace SSDT inside Clover /ACPI/PATCHED folder
OPTIONAL - ALTERNATIVE SSDT 3 – Create your own SSDT
FRAMEBUFFER PATCHING – For working Intel UHD 630 Graphics, working HDMI Port, working HDMI Audio on Aorus Z390 Pro
FOR MORE HACKINTOSH INFORMATION SUCH AS USB PORTS FIX, CLOVER CONFIGURATOR, HACKINTOSH BACKUP WITH CARBON COPY CLONER ..... THEN SEE MY PREVIOUS GUIDE FOR ASUS Z370-G Strix
Framebuffer patching in Mojave
Binary patching framebuffers using KextsToPatch in Clover is no longer a viable method in Mojave for Skylake and above. Now you need to use Lilu + WhateverGreen.
Not just for Mojave
This method of framebuffer patching is not only required for Mojave we recommend it for all previous and future releases of macOS.
Coffee Lake Users
Please note that the new WhateverGreen will not work with fake Kaby Lake platform-id's. You will need to have either macOS 10.14 Beta 4 (18A336e) or macOS High Sierra 10.13.6 (17G2112). The latter is a special build only available to MacBookPro15,1 or MacBookPro15,2 board id's. You can create a macOS High Sierra 10.13.6 (17G2112) installer by running installinstallmacos.py. (Update: vit9696 added back ability to fake Kaby Lake platform-id's)
Lilu + WhateverGreen
WhateverGreen is going to replace all the other video patching plugins for Lilu (it currently has merged WhateverGreen, IntelGraphicsFixup, NvidiaGraphicsFixup, Shiki and CoreDisplayFixup). Others will likely follow (such as AppleALC, HibernationFixup and IntelGraphicsDVMTFixup). This is aiming to be the all-in-one solution for video.
2. Turn off all graphics injections in Clover:
3. Disable DSDT Clover fixes:
4. Disable UseIntelHDMI
5. Remove boot argument: -disablegfxfirmware
6. Remove any IGPU and HDMI entries from:
7. Remove any IGPU and HDMI related SSDT and DSDT from:
8. Renaming GFX0 -> IGPU
- WhateverGreen will do this automatically (see caveat below)
- Be aware that WhateverGreen does not rename all instances of GFX0 -> IGPU but should be okay in most cases
- You may need to include Clover GFX0 -> IGPU rename for other kexts or ACPI patching that require it
Compile Lilu + WhateverGreen
Download WhateverGreen. Make sure you place the debug version of Lilu into the root of WhateverGreen before you compile. Install Lilu and WhateverGreen kext's into the usual place. Compile WhateverGreen as debug if you want to view debug output.
Having trouble compiling?
If you're having trouble compiling you can download the official release binaries or download my (unsupported) build_lilu.sh shell script and run it in a folder to download and build Lilu + WhateverGreen using Xcode automatically. I recommend you try the debug versions first (place them into Clover's EFI/Clover/kexts/Other folder).
Get the device path of your IGPU:
Download and use the gfxutil tool like so:
$ ./gfxutil -f IGPU DevicePath = PciRoot(0x0)/Pci(0x2,0x0) ig-platform-id
For the AAPL,ig-platform-id (AAPL,snb-platform-id for Sandy Bridge) entry Clover requires this value to be in Data format so you need to reverse the bytes. So if you want your platform-id to be 0x3EA50009 first reverse the bytes (0900A53E) then use Xcode's plist editor to add the values to Clover's config.plist.
What ig-platform-id should I use for my system?
You should choose one that is the closest match to your system. I recommend you do some research on this before choosing one. See post #2 for available options. More info can be found here.
You can determine the generation of your CPU by the first digit after the hyphen.
- Intel(R) Core(TM) i5-2760QM (Gen 2)
- Intel(R) Core(TM) i7-5257U CPU @ 2.70GHz (Gen 5)
- Intel(R) Core(TM) m3-6Y30 (Gen 6)
- Intel(R) Core(TM) i5-8350U (Gen 8)
Spoofing Intel CPU Gen
If you need to spoof a different Intel CPU generation you can use the lilucpu=N boot flag. The N refers to the following Intel generations:
4 SandyBridge 5 IvyBridge 6 Haswell 7 Broadwell 8 Skylake 9 KabyLake 10 CoffeeLake To spoof a CPU you will need to set a valid device-id in your GPU entry in Devices/Properties for the appropriate Intel generation.
Eg. Spoofing Skylake (lilucpu=8 boot flag with device-id=0x16190000), Kaby Lake (lilucpu=9 boot flag with device-id=0x12590000).
Here are some recommended frames:
Gen 2: Sandy Bridge (Intel HD Graphics 2000/3000)
- Support started with OS X 10.7.x and ended with macOS 10.13.6
- Metal support is not available
- device-id: 0x0102 0x0106 0x010A 0x0112 0x0116 0x0122 0x0126
- AAPL,snb-platform-id (desktop): 0x00030010 (default)
- AAPL,snb-platform-id (laptop): 0x00010000 (default)
Gen 3: Ivy Bridge (Intel HD Graphics 2500/4000)
- Support started with OS X 10.8.x
- device-id: 0x0152 0x0156 0x0162 0x0166
- AAPL,ig-platform-id (desktop): 0x0166000A (default), 0x01620005
- AAPL,ig-platform-id (laptop): 0x01660003 (default), 0x01660009, 0x01660004
Gen 4: Haswell (Intel HD Graphics 4200-5200)
- Support started with OS X 10.9.x
- device-id: 0x0D26 0x0A26 0x0A2E 0x0D22 0x0412
- AAPL,ig-platform-id (desktop): 0x0D220003 (default)
- AAPL,ig-platform-id (laptop): 0x0A160000 (default), 0x0A260005 (recommended)
Gen 5: Broadwell (Intel HD Graphics 5300-6300)
- Support started with OS X 10.10.2
- device-id: 0x0BD1 0x0BD2 0x0BD3 0x1606 0x160E 0x1616 0x161E 0x1626 0x1622 0x1612 0x162B
- AAPL,ig-platform-id (desktop): 0x16220007 (default)
- AAPL,ig-platform-id (laptop): 0x16260006 (default)
Gen 6: Skylake (Intel HD Graphics 510-580)
- Support started with OS X 10.11.4
- device-id: 0x1916 0x191E 0x1926 0x1927 0x1912 0x1932 0x1902 0x1917 0x193B 0x191B
- AAPL,ig-platform-id (desktop): 0x19120000 (default)
- AAPL,ig-platform-id (laptop): 0x19160000 (default)
Gen 7: Kaby Lake (Intel HD Graphics 610-650)
- Support started with macOS 10.12.6
- device-id: 0x5912 0x5916 0x591B 0x591C 0x591E 0x5926 0x5927 0x5923 0x87C0
- AAPL,ig-platform-id (desktop): 0x59160000 (default)
- AAPL,ig-platform-id (laptop): 0x591B0000 (default)
Gen 8: Coffee Lake (Intel UHD Graphics 630)
- Support started with macOS 10.13.6 (17G2112) / 10.14 beta 4 (18A336e)
- device-id: 0x3E9B 0x3EA5 0x3EA6 0x3E92 0x3E91 0x3E98
- AAPL,ig-platform-id (desktop): 0x3EA50000 (default), 0x3E9B0007 (recommended)
- AAPL,ig-platform-id (laptop): 0x3EA50009 (default)
WhateverGreen does most of the work automatically for you and in most cases you do not need any extra Framebuffer Patching. At the minimum though you should choose an ig-platform-id suitable for your system and place it in config.plist/Devices/Properties like this:
Here are some reasons why you might need extra Framebuffer Patching:
- Setting DVMT for those who can't set it above 32 MB in BIOS (framebuffer-stolenmem / framebuffer-fbmem)
- Setting higher VRAM for 4K users who experience graphical glitches (framebuffer-unifiedmem)
- Disabling eGPU (disable-external-gpu)
- Enable pixel clock patch for 4K support (enable-hdmi20)
- Disabling connectors to enable sleep (framebuffer-pipecount / framebuffer-portcount / framebuffer-conX-type=-1)
- Removing CNConnectorAlwaysConnected flag for eDP laptop screens on < 10.13.6 (framebuffer-con0-flags=0x00000090)
- Changing connector types to match your systems ports (framebuffer-conX-type)
Framebuffer Patching Types
We have three different types of patches:
1. Arbitrary (Recommended)
framebuffer-patch-enable (required to enable below) framebuffer-framebufferid (optional; defaults to current platform-id) (all below are optional) framebuffer-mobile framebuffer-pipecount framebuffer-portcount framebuffer-memorycount framebuffer-stolenmem framebuffer-fbmem framebuffer-unifiedmem framebuffer-cursormem (Haswell only) framebuffer-camellia framebuffer-flags framebuffer-conX-enable (required to enable below) framebuffer-conX-index framebuffer-conX-busid framebuffer-conX-pipe framebuffer-conX-type framebuffer-conX-flags 2. All Data
framebuffer-conX-enable (required to enable below) framebuffer-conX-alldata 3. Find / Replace
framebuffer-patchX-enable (required to enable below) framebuffer-patchX-framebufferid (optional; defaults to current platform-id) framebuffer-patchX-find framebuffer-patchX-replace framebuffer-patchX-count (optional; defaults to 1) You should place your patches in config.plist/Devices/Properties in Clover config.plist.
Here are some example patches:
- 32MB BIOS, 19MB stolen (framebuffer) 9MB fbmem (cursor) 2048MB unifiedmem (vram)
- Pipe / Port Count 3 to 2
- Connector 1 DP to HDMI
- Connector 2 Disable
Here is an example of the All Data method:
Here is an example of the Find / Replace method:
There are two ways to dump your framebuffer data (both require WhateverGreen + Lilu debug versions):
1. Using -igfxdump boot flag to dump IGPU framebuffer kext to /AppleIntelFramebuffer_X_Y (root of your boot drive)
There are several ways of reading this dump:
- Using 010 Editor along with the IntelFramebuffer.bt template
- Using Hackintool File->Open menu
2. Using -igfxfbdump boot flag to dump native and patched framebuffer table to ioreg at IOService:/IOResources/WhateverGreen
There are several ways of reading this dump:
- Using dump_platformlist.sh shell script
- Using Hackintool File->Import->IOReg Dump menu
3. Using Hackintool Framebuffer->macOS 10.14 menu
To get debug output from Lilu use the -liludbgall liludump=60 boot flags. You will need to compile Lilu and WhateverGreen as debug for both of these flags to work. Log files should be located at /var/log/Lilu_*.
To view debug paste the following into Terminal (weglog.txt will output to your home directory):
log show --predicate 'process == "kernel" AND (eventMessage CONTAINS "WhateverGreen" OR eventMessage CONTAINS "Lilu")' --style syslog --source --last boot >weglog.txt Getting Help
To help the users of this forum diagnose issues with your configuration please generate a Lilu debug log and then run gen_debug.sh to generate a folder of debug files you can attach to a forum post requesting help.
- vit9696 and lvs1974 for WhateverGreen (Full Credits) and Lilu (Full Credits)
- Andrey1970 for his guide on applelife.ru
- RehabMan for all data patching method, ioreg framebuffer dump and other contributions
Making a bootable High Sierra USB Installer Entirely From Scratch in Windows or Linux Mint (without access to Mac or App Store Installer.app)By fusion71au
Making a High Sierra USB Installer Entirely From Scratch in Windows
This is a proof of concept tutorial, to show it's possible to create a vanilla High Sierra installer, entirely from scratch, in Windows (even without App Store downloaded "Install macOS High Sierra.app" from a real Mac ). @PikeRAlpha's link to Apple's Software Catalog provides us with all the URLs necessary to download the needed files directly from Apple instead of some dubious source from the internet...
8GB or larger USB drive Boot Disk Utility v2.1.2017rev021b from @CVAD TransMac (free 15 day trial) Paragon Hard Disk Manager Free Download Installer Files Directly from Apple
1) Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist (Hint - search page for "InstallESD" to find its URL and others nearby)
to a folder named "SharedSupport" on your Windows NTFS drive. A browser download manager (eg Chrono for Chrome, dTA for FireFox) is handy since InstallESD is >4GB ---> allows you to pause/resume interrupted download...
2) Rename InstallESDDmg.pkg to InstallESD.dmg
3) Edit InstallInfo.plist with WordPad/text editor to remove the chunklistURL and chunklistid keys for InstallESD, and renaming it from InstallESDDmg.pkg to InstallESD.dmg (example of edited file attached to this post)...
Note: You can verify the SHA1 checksum of your InstallESD.dmg and BaseSystem.dmg with the correct ones at this website.
Boot Disk Utility to format the Installer USB and Restore OS X Base System HFS partition
1. Format USB with BDU & latest Clover ---> creates boot files in CLOVER partition + second FAT partition
2. Extract 4.hfs from \SharedSupport\BaseSystem.dmg with BDU --> save to it's local folder
3. Restore 4.hfs to USB second partition with BDU ---> 2nd partition becomes bootable "OS X Base System"
Paragon Hard Disk Manager to extend HFS Partition to its Full Extent
Open Paragon Partition Manager Free and resize the second partition of the USB drive to the full size allowed. Don't forget to apply the changes at the end...
Transmac to Copy "SharedSupport" folder to OS X Base System
1. Open the TransMac program and navigate to the HFS+ Volume/Install macOS High Sierra.app/Contents folder. Right click anywhere in the empty space on the RHS pane and select "Copy Here"...
2. In the next stage, select the "SharedSupport" folder we created above as the "Files and Folders to be copied to the Mac Volume"...
Clover configuration is required now. The default config.plist (in the Clover FAT32 partition of the USB) maybe sufficient to boot your machine if you’re lucky. If not, look at the Clover Wiki, Clover Instructions and Clover Configuration Thread for pointers and edit /EFI/Clover/config.plist accordingly with Wordpad or Notepad.
The location of the important configuration files for Clover are summarized below
config.plist--->EFI/CLOVER folder DSDT.aml with or without SSDT.aml--->EFI/CLOVER/ACPI/patched (don't need one if your DSDT is auto patched by Clover in config.plist) Kexts eg FakeSMC, NullCPUPowerManagement --->EFI/CLOVER/kexts/<osx version> or /Other. NB BootDiskUtility by default already has FakeSMC.kext installed here. You may need to add VoodooPS2Controller for your laptop keyboard/trackpad to work. If UEFI booting, you will most likely need one of the OsxAptioFixDrv-64 drivers copied from /EFI/CLOVER/drivers-off/drivers64UEFI to /EFI/CLOVER/drivers64UEFI. If you want to use the installer to run High Sierra in Windows on VMware, you can follow my guide to set up the Virtual Machine and replace Clover's default config with EFI_Clover for VMware (which is compatible to run in VMware). In the screenshots below, I have attached the USB Installer (in this case PhysicalDrive7) to my macOS Virtual Machine. Reboot the system to the USB installer to install High Sierra ...
What happens if we don't have access to TransMac or Paragon Hard Disk Manager?
Not a problem, as long as we get "OS X Base System" bootable, we can launch terminal from the Utilities Menu to copy the SharedSupport folder over to the Installer app. In essence, we will build the full installer app = 5GB+ on the target HD eg "Macintosh HD", by copying both the "small" installer app = 15MB (on "OS X Base System") and the SharedSupport folder from the NTFS volume (mounted in this example on /Volumes/DATA)...
-bash-3.2# cd / -bash-3.2# cp -R Install\ macOS\ High\ Sierra.app /Volumes/Macintosh\ HD/ -bash-3.2# cp -R /Volumes/DATA/SharedSupport /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/
...then start installation with the startosinstall utility...
-bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD --converttoapfs NO --applicationpath /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app
The above steps can be automated with the attached "startosinstall.command" script, which will assemble "Install macOS High Sierra.app" on "Macintosh HD" and launch the startosinstall utility targeting the "Macintosh HD" volume. Copy/download to "Macintosh HD", then run in terminal (after attaching DATA USB with /Shared Support folder)...
cd "/Volumes/Macintosh HD" chmod +x startosinstall.command ./startosinstall.command Updated Download Links for macOS Mojave 10.14.5_18F132
Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist
Note: In Mojave, Apple has removed the --converttoapfs NO and --applicationpath arguments from the startosinstall utility....
eg to use startosinstall for the above section "What happens if we don't have access to TransMac or Paragon Hard Disk Manager?", the syntax is now
-bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ Mojave.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD
This basically means that for Mojave, the default installation will always convert the target volume to the apfs file system.
• Adds AirPlay 2 support for sharing videos, photos, music and more from your Mac directly to your AirPlay 2-enabled smart TV
• Adds the ability to follow a magazine from the Apple News+ catalog browsing view
• Includes support for the Reiwa (令和) era of the Japanese calendar
• Improves audio latency on MacBook Pro models introduced in 2018
• Fixes an issue that prevented certain very large OmniOutliner and OmniPlan documents from rendering properly
View full article