Jump to content

16 posts in this topic

Recommended Posts

Manually install Clover for UEFI booting and configure boot priority with EasyUEFI in Windows


This tutorial will show how to manually install Clover in the EFI system partition of a pre-existing install of UEFI Windows.  In the process, you will also learn how to mount the EFI partition and add Clover as a UEFI boot option (using the EasyUEFI program) in Windows.


1.  CloverISO from Sourceforge.
2.  7-Zip for Windows
3.  EasyUEFI
4.  Existing UEFI install of Windows X64 (7,8,8.1 or 10)

Obtain Clover
1.  Download the CloverISO.tar.lzma file from Sourceforge and open the file with 7-Zip.



2.  Extract the Clover subfolder to your \Downloads with 7-Zip.



3.  Copy the Clover folder by right clicking on its icon in Windows File Explorer.



Mounting the EFI System Partition and installing Clover
1.  Open an administrative command prompt by clicking the Windows start button, typing cmd and right clicking on the search result as shown below...



2.  Type the following commands, followed by <Enter> after each line:

list disk
select disk # (where # is the disk number of the disk with UEFI Windows)
list partition
select partition x (where x is the partition number of the EFI system partition.  By default, it is usually the 100MB second partition)
assign letter=s


3.  Open Windows Task Manager as administrator by clicking the Windows start button, typing taskmgr and right clicking on the search result as shown below...



4.  Click Run new task



5.  Click Browse and in the Browse window, navigate to the EFI folder in the System Partition (which is mapped to drive S:) and also select "All files" from the drop down menu...



6.  Right click inside the EFI folder to "paste" the Clover folder we downloaded earlier.  If necessary, you can make edits to Clover's default config.plist with Wordpad or add OSX kexts like FakeSMC into the \kexts\other folder while still in the Task Manager browse window.  For UEFI booting into OSX, you will most likely need the OsxAptioFix2Drv-64.efi or OsxAptioFixDrv-64.efi driver in EFI\CLOVER\drivers64UEFI (copy from the \CLOVER\drivers-Off\drivers64UEFI folder).




7.  Quit Task Manager.


Add Clover as a UEFI Boot Option using the EasyUEFI Program
1.  Open EasyUEFI and click on the small icon with the plus sign (second from top) to add a new entry.



2.  In the Create Boot Entry Window, choose "Linux or other OS" as the entry type, click to select the EFI System partition as the target and browse to the CLOVERX64.efi file (file path \EFI\CLOVER\CLOVERX64.efi) as shown below...




3.  Type Clover in the Description field then the OK button.



4.  You will now see the new Clover entry on the main GUI of EasyUEFI.  Click on the entry and then click the small up arrow icon to move Clover to the top so it will get priority over the Windows Boot Manager on boot up.  Note on this screen, you can also delete/edit/disable boot entries or move them down the boot order.




5.  Click the power menu and select reboot to restart your system (use your system's boot device selection key to choose the drive with CLOVER installed if necessary eg F12 for Gigabyte motherboards, F8 for ASUS motherboards, F11 for ASrock motherboards) ---> will now be presented with the Clover Main Menu GUI to boot Windows (or OSX).




Enjoy and Good Hack :) !

Share this post

Link to post
Share on other sites

Im the first  :P . Looks good but all our guides are not pinned and no noob can reach them easily  :rofl:

Share this post

Link to post
Share on other sites

Manually Install Legacy Clover and prepare GPT disk in Windows (for dual boot UEFI Windows and OSX)


1.  GPT FDisk aka "GDisk"
2.  7-Zip
3.  Windows X64
4.  Bootice program
5.  Clover ISO downloaded from Sourceforge



Erase Hard Disk to RAW state with Diskpart.exe
Open an administrative command prompt and type the following lines, followed by the <Enter> key after each line....

list disk
sel disk # (where # is the disk number of the disk you wish to erase)



Microsoft Windows [Version 10.0.10586]
© 2015 Microsoft Corporation. All rights reserved.


Microsoft DiskPart version 10.0.10586

Copyright © 1999-2013 Microsoft Corporation.
On computer: XPSM1530

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          465 GB  1024 KB        *
  Disk 1    Online          931 GB   871 GB

DISKPART> sel disk 1

Disk 1 is now the selected disk.


DiskPart succeeded in cleaning the disk.


Leaving DiskPart...





Use GDisk to convert the Hard Drive to GPT and create partitions for dual booting UEFI Windows and OSX
In this example, I have a 1 TB hard disk which I plan to divide up as follows....


  • Partition 1: 200MB EFI System Partition
  • Partition 2: 128MB Microsoft Reserved Partition
  • Partition 3: 60GB NTFS Partition for Windows
  • Partition 4: 871GB HFS+ Partition for OSX

Notes -

  • EFI System Partition is preferably made the first partition for compatibility with OSX.
  • I usually leave 128MB of free space before and after the HFS+ partition or OSX Disk Utility will complain about a lack of "loader space".

1.  Open an administrative command prompt and cd to the gdisk installation folder
2.  Type gdisk64 #: (where # is the disk number of the disk you are creating partitions on - in this example it is disk 1)
3.  Use the following gdisk options:
     n to create a new partition
     x to access the experts menu
     a to change partition special attributes (needed for EFI System Partition)
     m to return to the main gdisk menu
     p to print the partition table
     w to finalize and write changes to the disk





C:\WINDOWS\system32>cd \gdisk

C:\gdisk>gdisk64 1:
GPT fdisk (gdisk) version 1.0.0

Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present

Creating new GPT entries.
Most versions of Windows cannot boot from a GPT disk except on a UEFI-based
computer, and most varieties prior to Vista cannot read GPT disks. Therefore,
you should exit now unless you understand the implications of converting MBR
to GPT or creating a new GPT disk layout!

Are you SURE you want to continue? (Y/N): y

Command (? for help): ?
b back up GPT data to a file
c change a partition's name
d delete a partition
i show detailed information on a partition
l list known partition types
n add a new partition
o create a new empty GUID partition table (GPT)
p print the partition table
q quit without saving changes
r recovery and transformation options (experts only)
s sort partitions
t change a partition's type code
v verify disk
w write table to disk and exit
x extra functionality (experts only)
? print this menu

Command (? for help): n
Partition number (1-128, default 1): 1
First sector (34-1953525134, default = 40) or {+-}size{KMGTP}: 40
Last sector (40-1953525134, default = 1953525134) or {+-}size{KMGTP}: +200M
Current type is 'Microsoft basic data'
Hex code or GUID (L to show codes, Enter = 700): L
0700 Microsoft basic data 0c01 Microsoft reserved 2700 Windows RE
3000 ONIE boot 3001 ONIE config 4100 PowerPC PReP boot
4200 Windows LDM data 4201 Windows LDM metadata 4202 Windows Storage Spac
7501 IBM GPFS 7f00 ChromeOS kernel 7f01 ChromeOS root
7f02 ChromeOS reserved 8200 Linux swap 8300 Linux filesystem
8301 Linux reserved 8302 Linux /home 8303 Linux x86 root (/)
8304 Linux x86-64 root (/ 8305 Linux ARM64 root (/) 8306 Linux /srv
8400 Intel Rapid Start 8e00 Linux LVM a500 FreeBSD disklabel
a501 FreeBSD boot a502 FreeBSD swap a503 FreeBSD UFS
a504 FreeBSD ZFS a505 FreeBSD Vinum/RAID a580 Midnight BSD data
a581 Midnight BSD boot a582 Midnight BSD swap a583 Midnight BSD UFS
a584 Midnight BSD ZFS a585 Midnight BSD Vinum a601 OpenBSD data
a800 Apple UFS a901 NetBSD swap a902 NetBSD FFS
a903 NetBSD LFS a904 NetBSD concatenated a905 NetBSD encrypted
a906 NetBSD RAID ab00 Apple boot af00 Apple HFS/HFS+
af01 Apple RAID af02 Apple RAID offline af03 Apple label
af04 AppleTV recovery af05 Apple Core Storage be00 Solaris boot
bf00 Solaris root bf01 Solaris /usr & Mac Z bf02 Solaris swap
bf03 Solaris backup bf04 Solaris /var bf05 Solaris /home
bf06 Solaris alternate se bf07 Solaris Reserved 1 bf08 Solaris Reserved 2
bf09 Solaris Reserved 3 bf0a Solaris Reserved 4 bf0b Solaris Reserved 5
Press the <Enter> key to see more codes:
c001 HP-UX data c002 HP-UX service ea00 Freedesktop $BOOT
eb00 Haiku BFS ed00 Sony system partitio ed01 Lenovo system partit
ef00 EFI System ef01 MBR partition scheme ef02 BIOS boot partition
f800 Ceph OSD f801 Ceph dm-crypt OSD f802 Ceph journal
f803 Ceph dm-crypt journa f804 Ceph disk in creatio f805 Ceph dm-crypt disk i
fb00 VMWare VMFS fb01 VMWare reserved fc00 VMWare kcore crash p
fd00 Linux RAID
Hex code or GUID (L to show codes, Enter = 700): EF00
Changed type of partition to 'EFI System'

Command (? for help): x

Expert command (? for help): a
Using 1
Known attributes are:
0: system partition
1: hide from EFI
2: legacy BIOS bootable
60: read-only
62: hidden
63: do not automount

Attribute value is 0000000000000000. Set fields are:
No fields set

Toggle which attribute field (0-63, 64 or <Enter> to exit): 0
Have enabled the 'system partition' attribute.
Attribute value is 0000000000000001. Set fields are:
0 (system partition)

Toggle which attribute field (0-63, 64 or <Enter> to exit):

Expert command (? for help): m

Command (? for help): n
Partition number (2-128, default 2): 2
First sector (34-1953525134, default = 409640) or {+-}size{KMGTP}:
Last sector (409640-1953525134, default = 1953525134) or {+-}size{KMGTP}: +128M
Current type is 'Microsoft basic data'
Hex code or GUID (L to show codes, Enter = 700): 0c01
Changed type of partition to 'Microsoft reserved'

Command (? for help): n
Partition number (3-128, default 3): 3
First sector (34-1953525134, default = 671784) or {+-}size{KMGTP}:
Last sector (671784-1953525134, default = 1953525134) or {+-}size{KMGTP}: +60G
Current type is 'Microsoft basic data'
Hex code or GUID (L to show codes, Enter = 700): 0700
Changed type of partition to 'Microsoft basic data'

Command (? for help): n
Partition number (4-128, default 4): 4
First sector (34-1953525134, default = 126500904) or {+-}size{KMGTP}: +128M
Last sector (126763048-1953525134, default = 1953525134) or {+-}size{KMGTP}: -128M
Current type is 'Microsoft basic data'
Hex code or GUID (L to show codes, Enter = 700): AF00
Changed type of partition to 'Apple HFS/HFS+'

Command (? for help): p
Disk 1:: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 584D0F77-3CE2-43C7-8663-CE867C61149D
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 8-sector boundaries
Total free space is 524294 sectors (256.0 MiB)

Number Start (sector) End (sector) Size Code Name
1 40 409639 200.0 MiB EF00 EFI System
2 409640 671783 128.0 MiB 0C01 Microsoft reserved
3 671784 126500903 60.0 GiB 0700 Microsoft basic data
4 126763048 1953262990 870.9 GiB AF00 Apple HFS/HFS+

Command (? for help): w

Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING

Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to \\.\physicaldrive1.
Disk synchronization succeeded! The computer should now use the new
partition table.
The operation has completed successfully.




4.  Use Diskpart to assign drive letters and format the EFI and Windows Partitions to FAT32 and NTFS respectively....





Microsoft DiskPart version 10.0.10586

Copyright © 1999-2013 Microsoft Corporation.
On computer: XPSM1530

DISKPART> sel disk 1

Disk 1 is now the selected disk.

DISKPART> list part

Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 System 200 MB 1024 KB
Partition 2 Reserved 128 MB 201 MB
Partition 3 Primary 60 GB 329 MB
Partition 4 Primary 871 GB 60 GB

DISKPART> sel part 1

Partition 1 is now the selected partition.

DISKPART> assign letter=s

DiskPart successfully assigned the drive letter or mount point.

DISKPART> format quick fs=fat32 label="EFI"

100 percent completed

DiskPart successfully formatted the volume.

DISKPART> sel part 3

Partition 3 is now the selected partition.

DISKPART> assign letter=w

DiskPart successfully assigned the drive letter or mount point.

DISKPART> format quick fs=ntfs label="Windows"

100 percent completed

DiskPart successfully formatted the volume.




Install legacy Clover bootsectors in Windows


The Clover wiki describes the legacy booting process:

Essentially BIOS--->MBR--->PBR--->boot--->CLOVERX64.efi--->OSLoader

In terms of the bootsectors we will be using in this tutorial
BIOS--->boot0af in MBR--->boot1f32alt in the PBR of the EFI System Partition--->boot6 in ESP--->CLOVERX64.efi in ESP--->OSLoader

1.  Download the CloverISO tar.lzma file from Sourceforge and extract the ISO with 7 Zip
2.  Copy the following boot files from \usr\standalone\i386 folder
     boot0af, boot0ss, boot1f32, boot1f32alt



    and boot6, boot7 from \usr\standalone\i386\x64 to somewhere convenient



    The EFI folder will also be needed later....



3.  Open the Bootice program and click Process MBR from the main menu



4.  At the Master Boot Record screen, click restore MBR



5.  For the Restore file, browse to the boot0af or boot0ss file we extracted in step 2



6.  Click the Restore button and you should get a confirmation that the operation completed successfully.  Click the close button.



7.  Click Process PBR from the main menu

8.  At the Partition Boot Record screen, select the FAT32 EFI System Partition as the destination and click the Restore PBR button.




9.  For the Restore file, browse to the boot1f32 or boot1f32alt file we extracted in step 2.  In this example, I used the alternate booting PBR (boot1f32alt), which gives a 3 second pause to enable the user to input his/her choice of boot file during bootup (default is boot6).





10. Click the Restore button and you should get a confirmation that the operation completed successfully.  Click the close button and exit the program.
11. Open Task Manager as administrator and open a new task.  Browse "all files" and navigate to the EFI System Partition (which we assigned the drive letter S: earlier).



You should now be able to copy the EFI folder from the Clover ISO (as well as boot6 and boot7) into the EFI System partition.  If you used boot1f32 for your PBR, rename "boot6" to "boot".




12. Make the necessary edits to the EFI\CLOVER\config.plist for your system and make sure you have FakeSMC.kext in EFI\Clover\kexts\Other.  If you have a DSDT &/or SSDTs that works for your system, place them in /EFI/CLOVER/ACPI/patched.

13. Reboot the computer and it should boot to the Clover Main Menu :) .

Share this post

Link to post
Share on other sites

Had to do this without guides when my hack suddenly deleted the partition table after running out of battery in sleep mode on Mac OS X. Now at least people know how to do it with this very detailed guide. Thanks.

Share this post

Link to post
Share on other sites

Thanks a lot for the guide! After messing with dual installation, I couldn't load MAC OS X without USB. Your guide helped, only had to download EasyUEFI and copy Clover folder from my USB.

Share this post

Link to post
Share on other sites

Thanks a lot for the guide! After messing with dual installation, I couldn't load MAC OS X without USB. Your guide helped, only had to download EasyUEFI and copy Clover folder from my USB.

If you need the USB, then that means you're missing the EFI folder in SSD/HDD's root EFI partition: Installing Clover to EFI root

Share this post

Link to post
Share on other sites

If you need the USB, then that means you're missing the EFI folder in SSD/HDD's root EFI partition: Installing Clover to EFI root

Yeah, I know. I stumbled upon ways to fix it in the Mac OS X and got a lot of helpful advice in another thread, but couldn't make anything work regarding this issue(now I get why, I did some steps wrong).

Using this guide for Windows I fixed everything. Thanks anyway, the link can come handy someday.

Share this post

Link to post
Share on other sites

Quick tip for mounting and unmounting the EFI partition in WIndows - open elevated Command Prompt (right-click and Run as Administrator) and use the following:


-for mounting

mountvol H: /s

this one will mount the EFI partition as H: (you may use whatever drive letter you want, as long as it's available).


for unmounting

mountvol H: /d

Share this post

Link to post
Share on other sites

Oh damn it! I never thought that it would be possible to install Clover from Windows (until I happened to search for it and found this post). I was there man, Sierra was properly installed on its partition and booting, the only problem was I couldn't install Clover from it and booting from the USB would be hassle. Ironically I {censored}ed up the USB installation drive and spent the whole weekend trying to prepare it again, which is quite difficult since I don't have access to a Mac right now and I couldn't manage to run it on VirtualBox.... The only option left is to connect my old drive and boot Mac from there.

Share this post

Link to post
Share on other sites

Nice work fusion71au!


I am looking for solution for dualboot, but first, short explanation what i have done till now:


My HW Specs:


 HP Z800 Workstation  BIOS V.3.60

2 x Intel® Xeon® processor X5650 2.66 GHz, 12MB cache 1333 MHz memory, 6-Core


GFX: Nvidia QUADRO 6000

Windows 10 on RAID0 LSILogic RAID SAS 1068E Controller ( 3 x 420GB SAS HD)

Backup SAS HD 1TB on LSILogic RAID SAS 1068E Controller

Sierra on Kingston 120GB SSDNow  on SATA port 1


First installed Win10 on RAID0 (LUN0). The Apple Xserves, possibly the Mac Pro RAID Card, use the LSI SAS1068E controller chip as well.

 Second installed OS-X Sierra on SSD  with Clover. Aplied EFI to Windows EFI Systempartition, but cannot boot in to the Windows!

Analyzing my system, I noticed that under the system information Sierra recognizes LSILogic RAID controller and single  HD 1TB connected on it, but does not recognize the Windows partition on raid0. Which leads to the conclusion that clover does not recognize Raid0. I spent time searching for a possible solution to identify Raid0 in sierra, but due to specific configuration of my system, there are not many solutions on the net.


I've been thinking about a solution to install the bootloader (Clover, or EasyBCD) on to Windows  EFI partition and boot from it, and to add OS-X Sierra as second entry.


Then I found this post and I think that would be the solution to my problem.


I have only one question:

If I install the  Clover on Windows efi partition, could come to conflict with Clover installed on the OS-X partition ?


PS: this is my first post on InsanelyMac after 6 years of hibernation, where a lot of things happened and changed. I'm glad to be back again and see how the "new kids on the block" rule the matter!



Share this post

Link to post
Share on other sites

Thanks for this guide @fusion71au this helped me finally solve my issue of only being able to boot from installer usb! :thumbsup_anim:   I used Clover 3333 because the newer versions didn't have the CLOVER folder (only pkg).  Btw love your Tintin avatar! :D

Share this post

Link to post
Share on other sites

Just going to jump here: sadly EasyUEFI now requires a paid license to add/edit/remove UEFI entires, basically it's useless in its "Free" form. 

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 glasgood

      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
      STEP 1 - Clover dual boot configuration 
      Open config.plist with Clover Configurator
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )

      So at boot you will have two options: boot macOS Mojave or Windows 10 
      STEP 2 - Using a drive without Windows 10 installed
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
      STEP 2 - Using a drive with Windows 10 already installed
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 

      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
      Video summary:
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
      After conversion Windows 10 is ready to use at the Clover boot menu 
      STEP 3 - Stop Windows Boot manager from overriding Clover boot manager
      How to stop Windows boot manager from overriding your Hackintosh Clover boot manager when using dual booting between macOS and Windows
    • 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.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.
    • By SoThOr
      This was spurred on from a discussion in the Clover General thread. Where there was a debate on bcdedit being able create/read/edit (U)EFI Boot entries. I didn't think it appropriate to post all this information there and somebody may want to make use of this and its likely to get lost in that massive thread.
      Out of curiosity I decided to see if I could create an EFI entry using bcdedit. What can I say I like a challenge.  Whilst is not a documented method by Microsoft, as it turns out in a round about way it IS possible to create an EFI entry using bcdedit and these are the steps I went through to add UEFI Shell located on a USB stick to the EFI entries. 
      Third party software is available that can create and edit UEFI entries from Windows with better support and more features. I'm just making this information available in case those options are unavailable. 
      DISCLAIMER - This is not a supported method. Use at your own risk. I recommend backing up your BCD/Firmware variables/settings beforehand.
      1) Copy {bootmgr} entry.
      C:\Windows\System32>bcdedit /copy {bootmgr} /d "UEFI Shell" The entry was successfully copied to {34e8383c-73a7-11e9-9cb0-94de8078a7b5}. 2) Edit the new entry using the new GUID bcdedit generated in the copy step.
        a) Set the device and path for UEFI shell on my USB stick.
      bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} device partition=G: bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} path \EFI\SHELL\SHELLX64.efi   b) Clean up some of the stuff that was copied from {bootmgr} (optional as far as I can tell, just makes things tidier in bcdedit)
      3) Put the new EFI entry first in boot order. (optional)
      After completing the steps above, here is what "bcdedit /enum firmware" shows:
      I shutdown my computer and when I turned my computer back on it booted up into UEFI Shell. After exiting the shell my PC went on to boot Windows.
      Here is the resulting dump using "bcfg boot dump -v" from that shell:
      You may notice that the shell shows as "Windows Boot Manager" in the bcdedit output. This I believe is because of the "WINDOWS" at the beginning of the option data that bcdedit added to the EFI Boot entry. I also believe this why bcdedit shows my Windows 8 installation as "Firmware Application" because it has no option data. I don't know how to remove this data using bcdedit nor do I know how the option data, that bcdedit adds, will affect other EFI applications.

      There might be a way to create the EFI entry without copying the Windows entry but if there is I'm unable to find any documentation on how one would do so. If you use the create command then it just puts it in the BCD and I'm unaware of a way to tell it to create it in EFI instead, other than by doing the above.
    • By cvad
      Small tool to download, compile and build the latest Clover X64 package.

      The script inside is editable.

      Many thanks to the comrade SunKi for help with creating the script.
      Best thanks - click "Rate File".
    • By blxkspell
      As I have 3 Monitors connected, my RX 570 gets arround 50°C while ideling/ web browsing etc. The problem is, that this temp is apparently just the threshold, when the fans start to spin. So the fans start spinning for a minute then they stop for a while again... This is very annoying for me as the rest of my hackintosh is nearly quiet (SSD, 120mm low RPM cpu fan, nearly silent PSU,...), especially when Im using the pc to revise for school. Does somebody know wether its possible to "change" the threshold till the fans start spinning? Like it would probably not be a problem for the gpu at all, if the temp rises to 55°C but therefore be soundless....