Jump to content
Frank Nitty

[GUIDE] How To Install High Sierra On EVGA Z97 With Clover in UEFI Mode

7 posts in this topic

Recommended Posts

This thread is a walkthrough on how to install High Sierra. These are fully detailed instructions to make it easier for newbs. PLEASE DO NOT PM ME FOR HELP. REPLY TO THIS GUIDE BELOW. THANKS


       MY SPECS:

1.  Intel Core i7-4770K (De-lidded)

2.  EVGA Z97 FTW (ATX)

3.  Western Digital VelociRaptor 1TB

4.  Corsair Vengeance Pro 16GB DDR3 2400MHz

5.  OCZ Vertex 4 512 GB

6.  Patriot Dual Bay 2.5" SATA 3.5" drive bay (for SSD)

7.  Noctua NH-U12S

8.  My case: Modified Apple Powermac G5

9.  ASUS BW-12B1ST

10. ASUS GeForce GTX 1070

11. Silverstone SST-ST1200-G Evolution Strider Gold 1200W



1.  macOS 10.13 High Sierra [from Mac App Store]

2.  A computer running an Intel Processor

3.  Access to OS X on VMWare (for Windows), Mac, or Hackintosh

4.  1x supported graphics card

5.  Clover v2.4k r4220 and up

6.  A USB flash drive at least 8 GB

7.  Update your system with the latest BIOS



1.  AHCI mode and CD/DVD first boot priority are set in the BIOS by default. Ensure your settings match these in your Z97 BIOS:

a. Go to ADVANCED→ SATA Configuration→ All settings should set at default; notice that your disks won't show up here if they're connected to black Marvell SATA ports.


b. Go to BOOT→ Speaker Beep; switch to 'Off'. Change Boot mode select to 'UEFI'. Continue to FIXED Boot ORDER Priorities→ Check if CD/DVD is 1st Boot (Note that your CD drive will not appear unless there is an UEFI enabled CD inside; Scroll down to Hard Disk Drive BBS Priorities to set the boot sequence of the available hard disks (Note that if at least one hard disk is not configured with EFI bootloader then 'Hard Disk Drive BBS Priorities' menu will not show up). Go to CSM ConfigurationLaunch CSM = 'Disabled'; This enables the bootloader menu screen to load with native HD as specified by your monitor.

NOTE: If you are multi-booting with Windows 7, it is MANDATORY that Launch CSM = 'Enabled' (Launch PXE OpROM policy = 'Do not launch', Launch Storage OpROM policy = 'UEFI only', Other PCI device ROM priority = 'UEFI OpROM'); The lack of these settings can cause the following error when starting up your Windows 7 boot drive:

Windows failed to start. A recent hardware or software change might be the cause. 
File: \EFI\Microsoft\Boot\BCD
Status: 0xc000000d
Info: An error occurred while attempting to read the boot configuration data
It will also prevent any non-UEFI boot disks from appearing in the UEFI BIOS (e.g. CD/DVD, Windows 7 USB Keys, etc.)





c. Go to ADVANCED→ Power Management→ ACPI Sleep State is S3 only (Suspend to RAM).


d. Go to ADVANCED→ Graphics Configuration→ Disable internal graphics.


e. Go to ADVANCED→ CPU Configuration; there is no option for Vt-d, so disable Intel Virtualization Technology (during installation).


f. Go to ADVANCED→ USB Configuration→ Disable XHCI Mode.


g. [OPTIONAL] Go to MEMORY; Under Memory Multiplier Configuration, set Performance Memory Profiles to XMP Profile 1.


h. [OPTIONAL] Go to ADVANCED→ H/W Monitor Configuration→ Set all fan speeds to 50%. Save and Reset.




1.  Clover and the macOS installer are placed on separate partitions on the USB stick. This guide will use 'diskutil list' in Terminal instead of Disk Utility to format the USB with GPT partitioning for Clover UEFI support.

2.  You must determine its disk identifier before you can partition the USB. Plug the USB stick into a Mac (or Hackintosh), run Terminal and type 'diskutil list'.

The following screenshot will serve as a reference:


As you can see the the USB stick’s identifier is /dev/disk4.

3.  Type the following entry into Terminal to format the USB stick (two partitions, via GPT):

diskutil partitionDisk /dev/disk4 1 GPT HFS+J "OS X" R

During the process the following occurred:

  • /dev/disk4 GPT partitioning initiated
  • by default EFI was automatically created
  • remainder "OS X", HFS+J is partitioned

4.  It resulted in the following screenshot:


Close Terminal


5.  We need to download and install the latest version of Clover r4220+ (here) on the USB stick.

a.  Run the pkg, "Change Install Location" by selecting "OS X" (partition name) as the target of the install. Use the following settings below:



Make sure that it shows "Installation Complete."

NOTE: When installing to HDD select "Install RC scripts on target volume" and/or "Install all RC scripts on all other boot volumes" and "Install Clover Preference Pane".


6.  You must copy your kexts to the EFI/ Clover folder. You can use EFI Mounter v1.2.3 when necessary to mount the EFI partition, just use "diskutil list" first to ensure you chose the right one for the USB stick.


a. Remove EFI/CLOVER/kexts/10.6, 10.7, 10.8, 10.9, 10.10, 10.11, 10.12 leaving just 'Other'.

b. Copy the required kexts Slice’s FakeSMC.kext, VoodooPS2Controller.kext (for PS/2 keyboard), and your ethernet kext (Intel I219-V) IntelMausiEthernet-V2.3.0 or AppleIntelE1000e v3.3.3 to the following directory: /EFI/CLOVER/KEXTS/Other.

NOTE: If you are having trouble getting Ethernet to work you can also try copying IONetworkingFamily.kext from S/L/E to /EFI/CLOVER/KEXTS/Other with your networking kext.


7.  Use a text editor/plist editor like PlistEdit Pro to modify your config.plist manually. We must apply the following mandatory patches:

a. You must add line ACPI/SSDT/DropOem=false in config.plist in order to boot without "Still waiting for root device" error. Add this <dict> entry to EFI/CLOVER/config.plist:


b. Use Clover’s built-in kernel patch to automatically apply the code to patch the (new) kernel after each OS X update to prevent reboot loop:


c.  AppleAHCIPort Clover patch disables orange drive icons. Add this <dict> entry to the config.plist:

                <string>External icons patch</string>

d. SMBIOS. With the config file still opened in your text/plist editor, scroll down to SMBIOS section to add the following SMBIOS system definition:

        <string>Apple Inc.</string>

NOTE: Macmini6,2, iMac13,2 and iMac13,1 support speedstep.You can also do this using Clover Configurator: In the SMBIOS section, click the magic wand to select a SMBIOS relevant to your hardware (e.g. iMac14,2) – and close the screen and File/Save.


e. GUI. Here you indicate the theme you want to use that you installed by entering the title in the string. I chose to use "random" as shown below:


f. Boot Flag. It is necessary to use "-v" to monitor if any problems arise. Add this <dict> entry to the config.plist:


g. NVIDIA graphics cards especially 'Maxwell' & 'Pascal' currently lack support natively in macOS. To correct this problem, it requires System Parameter/NvidiaWeb entry. It must be disabled during installation by adding this <dict> entry to the config.plist:


h. SIP. Apple has implemented 'rootless' security or System Integrity Protection (SIP) which restricts users from modifying system folders/files, and as a result it locks down system folders and files against hacks and root attacks, making the system safer. SIP must be partially disabled at the least, to install anything (i.e., kexts) into protected system folders, but as of High Sierra beta, the old string "0x3" has resulted in errors later on in boot. Add this <dict> entry to the config.plist:


i. Audio Fix. This Haswell board comes with a Realtek ALC898 audio chip. In order to use AppleALC/CloverALC (discussed further in this guide), you must add the following patch in the config.plist:

        <string>t1-10.9-10.11-AppleHDA/Realtek ALC898</string>

j. Drop ACPI MATS/DMAR tables. Drop the DMAR table if VT-d isn’t disabled in UEFI settings. MATS has been known to prevent some from booting into 10.13 so it can be dropped as well:


NOTE: Without dropping the tables the following error may occur: Attempting System Restart...MACH Reboot


8.  Preparing OS X partition. Download macOS v10.13.0 High Sierra [17A365] [Mac App Store] and Right-click "Install macOS High Sierra" will be in /Applications.

a. Go to Show Package Contents Contents SharedSupport.

b. You will now see an image called "BaseSystem.dmg" appear in the folder. Mount it by right-clicking and opening it with DiskImageMounter...

NOTE: The version of Disk Utility found in El Capitan+ has been stripped down of its most essential features to proceed with the following instructions. Your next best option is to use a pre-modified version of the old Disk Utility. After downloading it, extract and copy it to the Desktop and type the following line in Terminal to take ownership, enabling the app to run:

sudo chown -R 0:0 ~/Desktop/Disk\ Utility.app

c. Open Disk Utility. Select and highlight the volume "OS X Base System", click "Restore" at the top-right, drag the volume into "Source" field, and drag the USB [OS X] partition (you already created) to the "Destination" field where you will restore the image: click the "Restore" button then "Erase"...

d. After the process is complete, you'll now have (2) "OS X Base System" present in Finder. Eject the image "BaseSystem.dmg" and close Disk Utility.

e. Open "SharedSupport" folder and copy BaseSystem.chunklist, BaseSystem.dmg, AppleDiagnostics.chunklist, and AppleDiagnostics.dmg to the volume root.

f. Remove the "Install macOS High Sierra.app" from the volume root and replace it with the full version (>5GB) in the Applications folder where it downloaded.

NOTE: Skipping this step causes the following error when booting the installation: The path /System/Installation/Packages/OSInstall.mpkg appears to be missing or damaged

g. Create a new folder named "Kernels" in System/Library on the USB stick. Use Pacifist v.3.2.17+ to extract "kernel" from " SharedSupport /InstallESD/Packages/Core.pkg [/system/Library/Kernels/kernel]" and place "kernel" into System/Library/Kernels/ location.

h. With the USB installer ready, remember before restarting system to change boot priority of USB stick to first to install High Sierra on the hard disk of choice.

i. Highlight and select the USB installer from the bootloader menu screen to begin the installation.

j. Once the installer has finished, it will automatically restart the system. Boot from the USB installer and select the drive where you installed High Sierra to continue the rest of the installation.


       STEP 3: macOS 10.13 Post-Installation

1.  As the system is loading, you'll be prompted to the macOS Welcome screen.

a. Select your country then click "right arrow" to go to the next screen.

b. Select "My computer does not connect to the Internet."

c. Select "Don’t transfer any information now."

d. Agree to "Terms and Conditions."

e. Enter your name, password, and hint and Continue.

f. On "Express Set Up" access "Customize Settings."

g. Do not "Enable Location Services on this Mac."

h. Set your time zone, do not "Share Mac Analytics with Apple", and do not "Enable Siri".

i. Wait a moment for the macOS desktop to load.

j. When prompted to backup any disk with Time Machine, click on the "Don't Use" button.


       STEP 4: macOS 10.13 Post-Installation (Continued)

1. Install macOS 10.13 Supplemental and reboot.

2. macOS High Sierra doesn’t allow unsigned apps to run that did not come from the App Store or identified developer. You can re-enable this function by running the following in Terminal:

sudo spctl --master-disable

Go to System Preferences  Security & Privacy and disable GateKeeper to allow installation of software by unidentified developers.

3.  Mount the EFI partition of the USB stick with EFI Mounter v1.2.3 and copy the 'EFI' folder to the EFI partition of High Sierra boot disk.

4.  Install Clover v2.4k on the High Sierra install HDD partition you plan to boot from. In addition to the settings configured earlier, select "Install RC scripts on target volume" and "Install Clover Preference Pane" when installing to the HDD.  Installing RC scripts enables nvram variables required for iCloud and other services. It processes logs that are located in /Library/Logs/CloverEFI. You can also type bdmesg > Desktop/boot.txt in Terminal to get them manually.

5.  Edit the config.plist from your boot disk in EFI/CLOVER/ by adding the following <dict> entries:

a. Method for Enabling NVIDIA Web Drivers. Boot flag nvda_drv=1 doesn't work in config.plist to enable Web Drivers. The setting under System Parameter in Clover called "NvidiaWeb" is what's used to fulfill this instead.


Remove Boot/Arguments/nvda_drv=1 if necessary.

b. Hide UEFI partitions. To hide internal UEFI (i.e., "Boot Windows from Recovery", "Boot Windows from EFI") you have to use Scan/Legacy=false:


c. Designate name of boot menu entries (Renaming Mac/Windows). In the Clover bootloader menu you will notice all EFI Windows partitions labeled "Boot Microsoft EFI boot menu from EFI [or SYSTEM]". The Windows partition is called EFI but there's also a Mac partition called EFI which is hidden by default in the Clover boot menu so it's a nonfactor. The volume names are what Clover shows by default. In order to change what the Clover boot menu shows your volume name to be you will have to specify its details under GUI/Custom/Entries section in your config.plist. There are 3 <key> tags necessary to edit in this section: Volume, FullTitle, and Type. You can refer to my personal settings below for help.

E.g., in my config.plist, my macOS volume is called "HISIERRA" because that's what I named the partition I installed macOS on. It can also be seen as a bootloader screen entry as "Boot Mac OS X from XXXXXXXX" where XXXXXXXX is the volume name. "FullTitle" is the name you want the entry to say, i.e.: macOS 10.13 High Sierra. "Type" is where you indicate what type of OS it is, i.e.: OSX (or Windows). Tags such as "Hidden" and "Disabled" are self-explanatory, while the "NoCaches" tag designates whether you want to boot without caches.

NOTE: Adding "InjectKexts" causes infinite loading on the Apple logo screen: YOU HAVE BEEN WARNED.

NOTE: Having more than one Windows installation will cause multiple "Boot Microsoft EFI boot menu from EFI" items to appear In the Clover bootloader menu. To change its volume name that Clover shows it requires identifying its individual GUID and adding it as a 'string' under the Volume <key> tag.

Launch the Terminal and type the following into the command line:

diskutil list

A list of drives will populate along with sublist of its partition scheme. Now look for the partition generally listed under your Windows disk as "EFI - NO NAME". E.g., my disk is "0" and the EFI partition is "2". I would type the following into terminal:

diskutil info disk0s2 [replace 0 and 2 according to your drive and partition number]

It will then printout all the info specific to that partition. All you need to use is the "Disk / Partition UUID", NOT the Volume UUID.

                        <string>Windows 8</string>
                        <string>Windows 10</string>
                          <string>macOS 10.13 High Sierra</string>

d. USB patch. High Sierra 10.13 requires the port limit to be raised in order for USB 3.0 ports to be recognized. This process involves installing FakePCIID.kext as well. Add this <dict> entry to the config.plist:

            <string>change 15 port limit to 20 in XHCI kext (9-series) 10.12</string>

Be sure to copy FakePCIID.kext and FakePCIID_XHCIMux.kext to /EFI/CLOVER/KEXTS/Other.

NOTE: Set 'XHCI Mode' to Smart Auto in the BIOS to enable USB 3.0.


6.  Remove Recovery partition. Deleting and merging a partition with 'diskutil' from the command line is the most precise method to remove the partition since it targets the recovery disk directly and merges it with the full High Sierra partition.

Launch the Terminal and type the following into the command line:

diskutil list

This will print out your drives partition scheme and look something like this:


Look for "Recovery HD" and see which identifier it uses. In this screenshot it’s disk2s4.

To remove that partition we use the following command (you can also use the volume name):

diskutil eraseVolume HFS+ Blank /dev/disk2s4

The partition will be erased. You’ll now have a blank partition sitting around, so you’ll want to merge that with your other High Sierra partition:

diskutil mergePartitions HFS+ HISIERRA disk2s3 disk2s4

This will merge the two partitions, with disk2s3 absorbing the space from disk2s4 and expanding, it causes data loss so don’t expect this to preserve anything.

7.  NVIDIA graphics cards 'Maxwell'+ currently lack native support in macOS 10.13.

a. Install NvidiaGraphicsFixup.kext and latest version of Lilu; Temporarily enable SIP to update drivers to avoid error and Web Driver installation failure.

NOTE: Skipping this step may cause a black screen and/or the following error when booting the installation: IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, nov 0, sm 0x0 flashing at the top of the screen when restarting after installing NVIDIA Web Drivers.

b. Download and install NVIDIA Web Driver 378. / NVIDIA Web Driver 378. to enable NVIDIA Graphics Cards because they won't work OOB without them.

NOTE: Remember to go to the NVIDIA Driver Manager menu bar at the top, change the settings to use Web drivers. Changes will take effect after restart.

8.  Reboot using the USB installer and choose the High Sierra install drive.

9.  Download CUDA 9.0.197 / CUDA 9.0.214 drivers (increases GPU computing performance) needed for 10.13 support and install.

10.  [OPTION 1] Install AppleALC to enable native audio by injecting the layout id supported for ALC898 through dynamic patching without modifying any kexts. Audio will no longer be affected after each macOS update and SIP can remain enabled. More details here.

NOTE: AppleHDA must be native, original and unpatched.

a. Mount EFI partition and add the following entry under Devices/Audio in the config.plist to inject working layout id 1 (or 2 or 3).


b. Download the latest version of AppleALC (v1.2.0) and copy it to CLOVER/kexts/Other.

NOTE: Rebuild kext cache if you have removed a modded AppleHDA to replace it with a native one by using Kext Utility or 'force rebuild cache' in Terminal:

sudo –s
sudo touch /System/Library/Extensions

10. [OPTION 2] Install the following patch associated with Realtek ALC898 AppleHDA Audio (by Toleda):

a. Mount EFI partition, verify "Disable SIP" entry CsrActiveConfig=0x3FF is in config.plist.

b. Download audio_cloverALC-120.command.zip and extract "audio_cloverALC-120_v1.0d.command".

c. No edits made to any native AppleHDA.kext file, 2-4 files added to Resources folder.

NOTE: There may be noticeable pops before starting playback which is caused by macOS putting the audio codec to sleep. Disable AFGLowPowerState in config.plist with following <dict> entry:


If popping is still exists after using the method above, try using antipop.


NOTE: There may be noticeable distortion after around 2 minutes of audio playback. Update to the latest version of Clover and add UseARTFrequency=false entry in the config.plist:


11. Creating a DSDT (Refer to MaLd0n)

12. Create a SSDT (Secondary System Description Table) to configure the maximum clock speed.

a. Download Pike's ssdtPRGen.sh script which should auto-copy into your home directory, 'Volumes/Users/<username>' folder. Open Terminal and type the following:

curl -o ~/ssdtPRGen.sh https://raw.githubusercontent.com/Piker-Alpha/ssdtPRGen.sh/Beta/ssdtPRGen.sh 

b. Next, set the execute/search bits:

chmod +x ~/ssdtPRGen.sh

c. Run ssdtPRGen.sh script for first time without any arguments and let it download all the data that you need:


d. The Haswell.cfg should have already downloaded.

e. Once finished you will have the ssdt.aml on the ~/library/ssdtPRGen/. Move it to /EFI/CLOVER/ACPI/patched.

NOTE: If you come across issues try the following:

  Use Terminal to ensure Haswell.cfg is in the 'Data' folder by typing: open ~/library/ssdtPRGen/Data

  You can remove any previously generated and downloaded script file by typing: sudo rm -R ~/Library/ssdtPRGen

  You can rerun another freshly downloaded ssdtPRGen.sh script with your processor type: ./ssdtPRGen.sh

  For additional help see also: ./ssdtPRGen.sh -help

14. Installing the following kexts/widget is optional. Mount the EFI partition to copy the kexts into the /EFI/CLOVER/KEXTS/Other folder. Install the widget using Launchpad  Dashboard:

  HWSensors 6.23.1417: Helps you monitor CPU, memory, disks, network, temperatures, fans, load/uptime, and processes. NO COMPATIBLE VERSION FOR 10.13 I KNOW OF!

15. Install iStat Pro 4.9, a highly configurable widget that lets you monitor every aspect of your Mac including CPU, memory, disks, network, battery, temperatures, fans, load & uptime and processes.


       OPTIONAL: Fixing Time Sync issue with macOS/Windows – Registry Fix Method

NOTE: Only works for Vista/Windows 7, 8 & 10

1.  Press the Win + R keyboard combination to bring up a run box, then type "regedit" followed by Enter. Confirm "yes" once UAC prompt appears.

2.  When the registry editor opens, navigate to:




3.  Right-click on the empty space right below 'TimeZoneKeyName' and create a new DWORD (32-bit). It will appear as D-WORD On 32-bit versions of Windows 7/Vista.



4.  Rename it "RealTimeIsUniversal" (without quotes and it’s case-sensitive). Double-click on the new DWORD and change its value data "0" (zero) to "1" (one) as a hexadecimal.



5.  Save everything. Reboot to macOS, set the time properly and now boot back to Windows. You should notice it adjusted the correct time.

NOTE: Avoid changing the time in macOS if you are running a multi-boot system. You only have to modify the time in the BIOS and in Windows followed by enabling the setting to sync the clock with online time.

Share this post

Link to post
Share on other sites

Fantastic, Frank!!!

I upgraded to High Sierra 10.13.2 my z97-hd3 build and I’m having trouble with my USB 3.0 and the Broadcom 94331CD WiFi icon is showing a message saying that no hardware is installed. Could anyone advise what should I do to make these two things working again? Sorry for not posting (don’t shoot at me) the clover folder and the Ioreg file, but I live in Puerto Rico and I don’t have the regular high speed Internet at home, the country electric system is still down and so I have not been able to setup another WiFi device in my build.

Share this post

Link to post
Share on other sites

Happy Holidays Frank!  I recently upgraded to High Sierra and I would like to have correct DSDT patches. Also, my build is booting and behaving very slow, the USB 3.0 is not working (it is reported with a speed of 480), and the wifi is not working (however, BT is working). My build is a Z97-HD3 with a Nvidia 1050 Ti SSC gpu with 16GB RAM and a BRCM94331CD wifi-BT combo card. Lastly, sometimes the PC is out of the blue turned off/shut down. I attached the clover folder and my  ioreg file. I used the post installation clover folder that you posted in this thread. To fix the wifi, I tried the AirportBrcmFixup.kext and the FakePCIID_Broadcom_WiFi.kext with the country code boot arguments and the Airport fix in config.plist without success. I'll appreciate if you can help me with the DSDT patches and also share some recommendations and tips about how to fix the slow behavior, USB 3.0 and wifi issues as well as the sudden turn-off.



Share this post

Link to post
Share on other sites

Fantastic, Frank!!!

Thanks MaLd0n, you're the man.

I upgraded to High Sierra 10.13.2 my z97-hd3 build and I’m having trouble with my USB 3.0 and the Broadcom 94331CD WiFi icon is showing a message saying that no hardware is installed. Could anyone advise what should I do to make these two things working again? Sorry for not posting (don’t shoot at me) the clover folder and the Ioreg file, but I live in Puerto Rico and I don’t have the regular high speed Internet at home, the country electric system is still down and so I have not been able to setup another WiFi device in my build.

My apologies for not responding sooner. I don't get notifications for this post unfortunately. Hopefully PR finally has running electricity by now. Regarding your USB 3.0 issue, be sure to follow Step 4, #5d in my guide. I don't own the Broadcom Wifi device you're referring to so I'm unable to advise you of what to do there

Happy Holidays Frank!  I recently upgraded to High Sierra and I would like to have correct DSDT patches. Also, my build is booting and behaving very slow, the USB 3.0 is not working (it is reported with a speed of 480), and the wifi is not working (however, BT is working). My build is a Z97-HD3 with a Nvidia 1050 Ti SSC gpu with 16GB RAM and a BRCM94331CD wifi-BT combo card. Lastly, sometimes the PC is out of the blue turned off/shut down. I attached the clover folder and my  ioreg file. I used the post installation clover folder that you posted in this thread. To fix the wifi, I tried the AirportBrcmFixup.kext and the FakePCIID_Broadcom_WiFi.kext with the country code boot arguments and the Airport fix in config.plist without success. I'll appreciate if you can help me with the DSDT patches and also share some recommendations and tips about how to fix the slow behavior, USB 3.0 and wifi issues as well as the sudden turn-off.

When it comes to DSDT patches, MaLd0n is your man, I'd suggest giving him a holler. He was the one who provided mine for me. Unless suggested otherwise please do not use any DSDT's posted unless you know it's specific to your motherboard

Share this post

Link to post
Share on other sites
Posted (edited)

You are saying to put DropOem=false under ACPI/SSDT. Then your code example says to put DropOEM_DSM (instead of DropOem) to ACPI/DSDT (instead of ACPI/SSDT) and set it to false.


Well. DropOEM_DSM under ACPI/DSDT is a dictionary, not a key.


There is a key called #DropOem under ACPI/SSDT. Is this it? Should I remove the '#'? What does the '#' mean there? It disables the key?


I am editing the config.plist put in place by the newest Clover installer.


Also, with KernelPm (in the next code example), where should one put the "Memory" key? There is none in my plist.conf. Or is it just for context?



Edited by Thinkcat

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By cvad
      Small tool to download, compile and build the latest Clover X64 package,
      possible include HFSPlus-64.efi.

      The script inside is editable.

      Many thanks to the comrade SunKi for help with creating the script.
      Best thanks - click "Rate File".
    • By gengik84
      Uno dei tre Requisiti:
      Hack funzionante Mac vero Macchina virtuale Impostazioni Bios per il boot:
      Cercate una voce  del tipo “Sata Mode”e settatela  in AHCI
      Secure Boot: disabilitare o altri sistemi operativi
      CSM: UEFI o LEGACY, oppure a secondo del tipo di installazione
      VT-x / VT-d disable
      *Nota: Secure boot e csm valido solo per bios UEFI
      Materiale Occorrente 
      "OS X (Versione App.Store)”
      USB 8GB  *nota: nel caso di usb superiori dovrà essere partizionata, in modo da avere una partizione su cui "lavoreremo,di questa dimensione
      kext Wizard 
      Bootloader Clover_2.3k_r xxx:                   http: //sourceforge.n.../cloverefiboot/
      Clover Configurator:                                    http: //mackie100proj...a.org/download/
      FakeSmc.kext:                                            https://github.com/kozlek/HWSensors/releases
      In allegato,a fondo pagina troverete un "pacchetto" contenente : ShowAllfiles, Kext Wizard, FakeSmc.kext: 
      App alternative:
      ESP Mounter Pro: per montare la partizione EFI
      Vi illustrerò tre metodi per creare la usb, ma sono ben distinti… quindi usatene soltanto uno
      Metodo 1: “Install Mac_OS_X.command” Metodo 2: “Create Install Media di Apple” Metodo 3:  Metodo Manuale Alla fine delle preparazione dell’installer, tutti i metodi necessitano l’installazione del Bootloader Clover sulla a vostra USB.
      PUNTO 1: che la vostra usb sia stata preventivamente nominata USB (caratteri maiuscoli) Tabella di partizione GUID e la formattazione in  Mac esteso Journaled.
      PUNTO 2: che l’installer di OSX si trovi in Applicazioni
      Utility Disco 
      Selezionate la pendrive, andate su “partizione”, selezionate “1 partizione”, impostate Mac OS esteso journaled e date il nome USB, poi in basso cliccate su opzioni e scegliete Tabella partizione (GUID), poi “applica”.
      Riporto nuovamente l’operazione sopra citata adoperando dal nuovo Utility Disco introdotto su El Capitan.
      Rimane ovviamente invariato nome della usb in ==>> USB (maiuscolo), la formattazione in Mac esteso Journaled e sia la mappa partizione in GUID
      Da utility disco selezionate la usb, cliccate su inizializza.
      dal menù a tendina scegliete la relative impostazioni
      Procedura effettua da High Sierra è la stessa della precedente, l'unica attenzione e operazione da aggiungere in primis  è cliccare nel menù a tendina in alto sulla sinistra di utility disco e selezionare "mostra tutti i dispositivi"
        METODO 1: "Install_Mac_OS_X.Command" Lo script che trovate allegato in fondo alla guida permette la creazione dell’installer in maniera automatica
      Include la possibilità di scelta di tre versioni di osx
      Yosemite El Capitan Sierra Il risultato finale è come quello del metodo "manuale" descritto nella guida, per cui l'installazione avverrà in un solo passaggio, non in due come con il metodo createinstallmedia. 
      Offre inoltre la possibilità di inserire un kernel patchato, utile, per esempio, per chi usa AMD.
      Rimane invariato il nome dato alla usb in USB, mappa partizione e tipo di formattazione
      Se la vostra usb non sarà rinominata nel modo corretto, verrete avvisati dal terminale, quindi non dovrete far altro che apportare la relativa modifica e rilanciare nuovamente lo script
      Metodo 2 
      L'intento è quello di usare la procedura fornitaci direttamente da Apple, "createinstallmedia", introdotta  con Mavericks. 
      Tale metodo prevede l’uso del terminale che via via se ne sta perdendo il “valore e l’uso”
      Inizialmente per i neofiti potrà sembrare problematico ma alla fine non è così.
      Durante il post installazione alcune operazioni ne richiedono l’ uso.
      Perciò mi sono chiesto perchè, qualora uno volesse, non far conoscere da subito un po’ questo “strumento”???
      Per favorirvi vi ho allegato i comandi già  “pronti”, i quali li potrete copiare ed incollare sul terminale.
      A questo punto aprite il terminale, copiate ed incollate il comando sottostante e premete invio, digitate la vostra password e premete nuovamente invio.
      Comando per creare USB con Yosemite:
      sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction  
      Comando per creare USB con El Capitan
      sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction Comando per creare USB con Sierra 
      sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ Sierra.app/ --nointeraction Per creare USB con Hight Sierra o Mojave usate --> C_I_M (aggiornato per 10.14)
      Funziona con il drag & drop sul terminale, in questo caso non vi è necessità che la usb sia nominata in un determinato modo ed essendo basato su create install media ovviamente funziona da 10.9 a 10.14.... 
      Potete adesso passare ad installare il bootloader Clover sulla vostra usb.
      Avendo usato questo metodo l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      METODO "MANUALE"....  (lascio per futura memoria-Compatibile fino a 10.12)
      **Nota:** Installazione in UEFI  dipenderà dalla scheda madre in vostro possesso, quindi se non supporta tale opzione , il bootloader dovrà essere installato in  modalità Legacy.
       Vi invito, qualora non sapeste questa informazione, a recarvi nel sito ufficiale del produttore e controllare le informazioni a riguardo
      Fatto questo dobbiamo installare  Clover sulla usb.
      A seconda del tipo di Bios o al tipo di installazione che vogliamo fare UEFI o Legacy avremo ovviamente configurazioni diverse in questa fase.
      Lanciate il pkg.

      Cambiate la destinazione di installazione ad USB oppure Install Mac_OS_X (a secondo del tipo di creazione eseguita)
      Successivamente clicchiamo su "Ad Hoc"
      Per Installazione UEFI
      Mettete i flag   : Installazione solo per avvio UEFI
                               : installare Clover nella ESP
                               : Driver64UEFI  selezionate OsxAptioFixDrv-64
                             *  :Se nel vostro sistema è presente una scheda grafica (discreta) della serie 9xx nVidia selezionate OsxAptioFix2Drv-64 al posto di  OsxAptioFixDrv-64 *
      ** OsxAptioFix2Drv :E' necessario per poter impostare CsrActiveConfig= 0x3 **
      ***OsxAptioFix3Drv oppure AptioMemory --> (consigliato) devono essere usati su hardware Skylake o successivi perché permettono alla nvram di lavorare correttamente
           (mi raccomando o uno o l'altro)
      Proseguite con l’installazione.
      ** Ricordate che avrete accesso a questa cartella dopo aver montato la partizione EFI**
      Per installazione Legacy
      Impostazione per config.plist:
      Con clover configurator “montate” la partizione EFI della usb.
      1) Per fare questo nel menù di sinistra, cliccate su “Mount EFI”
      2) individuate la partizione relativa alla vostra usb, a questo punto montiamo la relativa partizione EFI  selezionando l’apposito pulsante “Mount Partition”
      3) Successivamente cliccate su “Open Partition”.. recatevi in EFI/Clover ed aprite il config.plist
      4) Sezione ACPI: Disabilitate tutti i fix sia del menù 1 che del menù 2
      5) Sezione BOOT: Sole se si sta installando Yosemite mettete il flag su kext-dev-mode=1
      6) Sezione RT Variables: Se si sta installando El Capitan oppure Sierra, aggiungere i valori: BooterConfig= 0x28, CsrActiveConfig= 0x67
      7) Sezione System Parameters: Su inject kext mettete YES
      Nota: Su El Capitan, è stato introdotto SIP (System Integrity Protection)
      Recatevi in EFI/Clover/kext/10.x 
      X= alla versione di osx che state installando. Per esempio se installerete Yosemite dovrete recarvi nella cartella 10.10, con El Capitan in 10.11….ecc
      Se non ci fosse tale cartella, createla e nominatela voi a “modo”.
      Copiatevi all’interno FakeSmc.kext
      *Nota se venite già da altre vostre configurazioni, oltre kext sopra citato ,potete mettere gli altri necessari per il vostro hardware
      Stessa cosa se avete DSDT e/o SSDT potete copiarli in EFI/Clover/Acpi/Patched
      Per High Sierra:
      Scaricare il driver apfs.efi a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
      Per chi volesse continuare ad usare HFS vi rimando a questo post:
        Come installare High Sierra in HFS direttamente dalla usb  
      Utenti Laptop:  Nel 99% è obbligatorio disattivare la grafica discreta Nvidia/Amd per installare questo nuovo osx
                                     Quindi aggiungete --> SSDT-Disable_DGPU.aml.zip
                                     in EFI/Clover/acpi/Patched della usb
      Per Mojave:
      Scaricare il driver apfs.efi per 10.14 a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
      Versione di clover non antecedente a V_4015
      Volete usare HFS?
      E' possibile fare un installazione diretta su altro disco o partizione
      nel caso guardate...
       Mojave in HFS 
      Fatto questo avrete la vostra USB bootable per installare OSX.
      ………Non scordatevi Fakesmc.kext da mettere nella relativa cartella…. senza il quale non farete mai il Boot......
      *NOTA: se usato il terminale per la creazione della usb, l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      **NOTA** Se avete processori Broadwell,Skylake o Kabylake...usate FakeSmc.kext e relativi sensors che trovate all'interno del secondo pacchetto.. (potete usarlo anche sui precedenti senza problemi, essendo una versione più aggiornata ha ulteriore supporto per le cpu più recenti)
      Update: Fakesmc e sensors versione 6.26
      Post installazione... post #2           
       Buon Hack….. 
      Aggiornamento:Install_Mac_OS_X.command.zip (compatibile da 10.10 a 10.12)
      le info le trovate a questo post
      Ringrazio @Ciro82 che mi ha aiutato nel preparare questa guida.
      Pacchetto-Fake+Sensors 6.26.1440.zip
    • By Angelo_
      ho recentemente acquistato un ssd crucial mx500 (arrivato stamattina) e non ho idea di come trasferire il sistema operativo e clover dal mio attuale wd black 500 (2.5" che ho preso da un portatile a caso in casa) su questo nuovo ssd per vedere se questo rende il sistema più reattivo, sul sito crucial dicono solo come copiare i dati e os sul disco ma niente (ovviamente), cosa devo fare per sostituire bootloader, os, programmi e dati su questo nuovo disco? Ho in dualboot win 10 pro (che avvia da un altro 128gb ssd) quindi posso usare anche programmi da win, da una distro linux o da pennetta, non ho usato un granchè osx in quanto l'hdd credo lo renda lento quindi non sono molto esperto in queste cose su osx
      Inoltre mi conviene rimanere su hfs+ o usare apfs come file system?
    • By fusion71au
      Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VirtualBox 5.x.x on a Windows Host
      Following on from my previous guide on how to create a VMware virtual machine running Vanilla OS X El Capitan in Windows, I’ve decided to write a similar guide for creating a VirtualBox El Capitan VM. 
      The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
      There are other tutorials and videos on the net about running OS X on Windows machines using pre-made VMDK disk images but you can never guarantee what else is in there….
      I’ve gathered info for this guide from several threads in the Multibooting and Virtualisation section of this forum and also the wider internet eg
      @colt2 HOW TO: Create a bootable El Capitan ISO for VMware
      @dsmccombs comment on faking Ivybridge Processor
      @E:V:A http://forum.xda-developers.com/showpost.php?p=55572430&postcount=6
      @Tech Reviews video tutorial https://www.youtube.com/watch?v=t7X07U63lwg.
      VirtualBox Forum: Status of OSX on OSX
         Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X)    4GB or more RAM (2GB or more will be needed for OS X)    Hard Disk with at least 40GB free for Virtual Machine    Oracle VM VirtualBox v 5.0.34    Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#75    16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC  
      Prepare Installation ISO on your Mac or Hack
      1.  On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder.
      2.  Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes.  Note: you will need approx 16GB of free space on your hard disk for the script to complete.
      3.  Open OS X terminal, then run the following commands to execute the script:
      cd downloads chmod +x CECI.tool ./CECI.tool 4.  At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later.
      Create an El Capitan Virtual Machine in VirtualBox
      1.  Open the VirtualBox program and click the "New" button to create a new VM.

      2.  Select Mac OS X and Mac OS X 10.11 El Capitan (64 -bit) for Operating System type and version.  I named my Virtual Machine "El_Capitan", then clicked next...

      3.  Leave the Memory size at the recommended 2048 MB, then click next.

      4.  Choose to "Create a virtual hard disk now", then click the create button.

      5.  For the hard disk file type, the default is VDI (VirtualBox Disk Image) but I have selected VMDK for inter-operability with VMWare.  Click next...

      6.  For Storage on physical hard disk, I have chosen the default Dynamically allocated (grows larger to a set limit as you need more disk space).

      7.  On the File location and size screen, you can set the location of the new virtual hard disk and its size - I recommend changing disk size to 40GB or larger.  When you click the create button, you will now see your new VM in the VirtualBox main GUI.

      8.  Click the settings button on the Main Menu to tweak a few settings....
         a.  On the System/Motherboard tab in Boot Order, you can uncheck the Floppy Drive (who has these now?)

         b.  On the System/Processor tab, you can increase the allocated CPU cores to 2

         c.  On the Display tab, you can increase the allocated Video Memory to 128MB

         d.  On the Storage tab, click on the icon of the Optical Drive and select "Choose Virtual Optical Disk File". 

      Navigate and select the El Capitan ISO we created earlier...

         e.  Click the OK button to finalise the VM settings.
      Patch El Capitan vbox configuration file with DMI Settings from a Mac
      1.  From the start menu, type cmd and click run as administrator to open an administrative command prompt. 

      2.  Choose a Mac Model similar to your host system, then type the following lines, followed by <enter>  after each line.  Make sure you first close all VirtualBox Windows and the VirtualBox program, otherwise any changes you make won't stick...
      Eg iMac11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F2238BAE" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 MacBookPro11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-2BD1B31983FE1663" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 Macmini6,2
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "Macmini6,2" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F65AE981FFA204ED" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 3.  Optional- For some host systems eg those with Haswell and newer CPUs, you might have to spoof an older CPU to avoid VirtualBox errors.  You can try from one of the following if this happens:

      To spoof Lynnfield i5 750 CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000106e5 06100800 0098e3fd bfebfbff To spoof IvyBridge CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff or
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 00020800 80000201 178bfbff 4.  Close the command prompt window.
      Installation of El Capitan
      We are now ready to start the El_Capitan Virtual Machine....

      Installation should be relatively straight forward, just following the prompts of the OS X installer:
      1.  Select language, agree to legal terms

      2.  Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended.  I named my drive "Macintosh HD" but you can enter whatever you like eg El_Capitan.

      3.  Quit DU and choose Macintosh HD to install El Capitan on.
      4.  After 20-30 min (depending on how fast your system is), the installation will complete.  At this point, unmount the El Capitan ISO by clicking the Devices menu from the VM window, click Optical Drives, then choose Remove disk from virtual drive.  The VM is now ready to reboot into OS X from the virtual hard drive.
      5.  At the welcome screen, choose your country and keyboard layout.  You can skip transfer information, location services and logging in with your Apple ID if you wish…
      6.  Create a User Account and select your Time Zone.  You can skip sending diagnostics and usage data to Apple….
      7.  Finally, you will arrive at the El Capitan Desktop.

      8.  Network/internet and audio should work OOB but on my system, the sounds were distorted.  Unfortunately, there is no QE/CI and the VM resolution will be fixed without the ability to dynamically resize the VM window (no VirtualBox additions for OS X guests atm). 
      Customization with VBoxManage
      1.  You can change the default resolution of 1024*768 (after shutting down the VM) with the VBoxManage command from the Windows Administrative Command Prompt:
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" VBoxInternal2/EfiGopMode N (Where N can be one of 0,1,2,3,4,5) referring to the 640x480, 800x600, 1024x768, 1280x1024, 1440x900, 1920x1200 screen resolution respectively.
      Update:  For VirtualBox 5.2.x, the command for changing screen resolution has changed...
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution XxY (where X=Horizontal screen resolution, Y=Vertical screen resolution)
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution 1280x1024 2.  Adding serials and other SMBIOS details for the System Information Screen
      VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "W8#######B6" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardSerial" "W8#########1A" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVendor" "Apple Inc." VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemFamily" "iMac" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBIOSVersion" "IM112.0057.03B" A listing of known issues with Mac OS X guests can be found in the VirtualBox Manual - link https://www.virtualbox.org/manual/ch14.html.
      Vanilla Mavericks and Yosemite, Snow Leopard from Retail DVD
      The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite .  Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware.
      With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie
      To create a Mavericks ISO on your desktop
      cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop
      cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5...

      Finally, those without a Mac/Hack to prepare the install media can purchase a retail Snow Leopard DVD directly from Apple and install OSX 10.6.3 on their virtual machines (Snow Leopard, Lion and Mountain Lion run quite happily in VirtualBox with 1 CPU, 1-2 GB of RAM and the rest of the settings unchanged from above).  Once you update by combo update to SL 10.6.8, you can directly download El Capitan from the App Store for free .

      UPDATE macOS Sierra 10.12 to 10.12.6: For macOS Sierra, use CSI.tool in post#51.
      UPDATE macOS High Sierra 17A365:  For macOS High Sierra, use CHSI.tool in post#73.
      UPDATE macOS Mojave Beta:  For macOS Mojave Beta, use CMJI.tool on page 4 of thread.
      Good luck and enjoy
    • 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 Settings
      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.14beta
      Browse Apple's Public Beta 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