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.

 

Prerequisites
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.

 

post-846696-0-43352700-1451035731_thumb.png

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

 

post-846696-0-24546100-1451035750_thumb.png

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

 

post-846696-0-33202600-1451035779_thumb.png

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...

 

post-846696-0-80106900-1451035804_thumb.png

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

diskpart
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
exit

post-846696-0-42695000-1451035849_thumb.png

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...

 

post-846696-0-98469900-1451035903_thumb.png

4.  Click Run new task

 

post-846696-0-53196700-1451035929_thumb.png

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...

 

post-846696-0-92956500-1451035973_thumb.png

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).

 

post-846696-0-56017700-1451036024_thumb.png

 

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.

 

post-846696-0-22133300-1451036124_thumb.png

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...

 

post-846696-0-33853800-1451036154_thumb.png

post-846696-0-82792200-1451036173_thumb.png

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

 

post-846696-0-25737000-1451036230_thumb.png

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.

 

post-846696-0-85566700-1451036268_thumb.png

post-846696-0-98971400-1451036299_thumb.png

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).

 

post-846696-0-67383700-1451036345_thumb.png

post-846696-0-31170000-1451036369_thumb.png

Enjoy and Good Hack :) !

Share this post


Link to post
Share on other sites
Advertisement

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)

 

Prerequisites
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....

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

 

 

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

C:\WINDOWS\system32>diskpart

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> clean

DiskPart succeeded in cleaning the disk.

DISKPART> exit

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

Eg

 

 

 

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
PARTITIONS!!

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....

 

 

 

C:\gdisk>diskpart

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.
DISKPART> exit

 

 

 

Install legacy Clover bootsectors in Windows

 

Overview
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

Procedure
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

 

post-846696-0-11393200-1455486159_thumb.png

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

 

post-846696-0-24359500-1455486181_thumb.png

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

 

post-846696-0-25810500-1455486220_thumb.png

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

 

post-846696-0-13825000-1455486236_thumb.png

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

 

post-846696-0-15547900-1455486261_thumb.png

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

 

post-846696-0-59456100-1455486304_thumb.png

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

 

post-846696-0-35281700-1455486331_thumb.png

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.

 

post-846696-0-05841700-1455486350_thumb.png

 

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).

 

post-846696-0-55147400-1455486372_thumb.png

post-846696-0-18318900-1455486396_thumb.png

 

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).

 

post-846696-0-98469900-1451035903_thumb.

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".

 

post-846696-0-09360100-1455487178_thumb.png

 

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

24GB DDR3 RAM

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!

 

RESPECT!

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 fusion71au
      Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VMware Workstation on a Windows Host
       
      I wanted to make a simple guide on how to create a vanilla OS X El Capitan virtual machine running on a Windows host.  The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
       
      There are many guides and videos on the net about running OS X on Windows machines using pre-made VMWare disk images but you can never guarantee what else is in there….
       
      I’ve gathered info for this guide from various threads in the Multibooting and Virtualisation section of this forum eg
       
      Workstation 11/12, Player 7/12, Fusion 7/8 and ESXi 6 Mac OS X Unlocker 2 by @Donk How to Install OS X 10.x from Snow Leopard to El Capitan in VMware Workstation 10/12, Player 6/8 or ESXi 5/6 by @MSOK HOW TO: Create a bootable El Capitan ISO for VMware Credit and thanks to @Donk, @Albert Nietsnie and @MSOK for all their hard work in creating and testing the VMware Unlocker program.
       
      Requirements
      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 VMware Workstation 12 or later VMware Unlocker 2.0.7 or later 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#41 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.  Unmount any attached install image/InstallESD.dmg (if currently mounted) by rebooting the system or running the hdiutil unmount command in terminal eg
       
      3.  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….
       
       
       
      4.  Open OS X terminal, then run the following commands to execute the script:
      cd downloads chmod +x CECI.tool ./CECI.tool 5.  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.
       
      Updates:
      @shela has created an ISO generating script compatible with OS X 10.6-10.12: create_osx_iso post #362.
      See post#30 for macOS_iso_cim.tool script to create ISO for macOS 10.13+ using Apple's createinstallmedia utility.
       
      Install and Patch VMware Workstation 12 on your PC
      1.  Download and install VMWare Workstation Player 12 or later
      2.  Download and extract Unlocker 2.0.7 or later to your USB stick…
      3.  Run the win-install.cmd as administrator by right clicking the file in Windows explorer or run it from an Administrative Command Prompt.
       



       
      Create an El Capitan Virtual Machine
      1.  Double click on the VMware Workstation 12 Player icon on your desktop and click “Create a New Virtual Machine”.  Choose “I will install the operating system later” at the How will you install screen….
       

      2.  Select Apple Mac OS X as the Guest operating system and OS X 10.11 as the version.  By default, an OS X 10.11 folder will be created in your Documents\Virtual Machines folder.
       


      3.  Under Specify Disk Capacity, you can leave the default 40GB or set a larger value.  I personally store the virtual disk as a single file.  Click Finish and you will see OS X 10.11 on the Main Screen of Workstation 12.
       


      4.  Next, we need to edit the virtual machine settings to map the virtual SATA CD/DVD drive to the El Capitan installation iso we created earlier.
       


       
      5.  To prevent the virtual machine from crashing in Windows, the virtualHW.version set in the vmx configuration file needs to be changed from 12 to 10 (alternatively, the line smc.version = "0" can be added to the file).  The OS X 10.11.vmx file can be edited with the WordPad program (navigate to the OS X 10.11 virtual machine folder with Windows Explorer and right click on the file to open in WordPad).
       


       
      6.  For HW10, set USB compatibility to USB 2.0, otherwise your mouse and keyboard might not work in the virtual machine.
       

      7.  Finally click “Play virtual machine”
       

      Installation of El Capitan
      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’ve named the 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 and the VM will automatically reboot…
       

      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.  You should eject the Installation iso now by right clicking and selecting “Eject OS X Base System”.  This will allow you to install VMware Tools….
       



      8.  After rebooting, the VM can now be resized or run at full screen resolution.  Audio and network/internet should also work OOB.
       

       
      SMBIOS Customization and iMessage Vars
      To make the Virtual Machine more "Mac like", you can edit the vmx file to add unique identifiers from a real Mac's SMBIOS -
      eg for an iMac 11,3 SMBIOS, you can enter the following lines....
      smbios.reflectHost = "FALSE" board-id.reflectHost = "FALSE" board-id = "Mac-F2238BAE" hw.model.reflectHost = "FALSE" hw.model = "iMac11,3" serialNumber.reflectHost = "FALSE" serialNumber = "W80#######6" Refer How to spoof real Mac in VMware - Multi-booting and Virtualisation.
       
      The critical variables for iMessage/Facetime activation are MLB & ROM.  By default, VMware "reflects" the host's MLB and ROM since it assumes you are running the OSX guest on a real Mac host - see post#42 by @Donk.
       
      If the host is a Windows PC, the following lines need to be added to the vmx file (requires virtualHW.version 12 and smc.version = "0")....
      efi.nvram.var.ROM.reflectHost = "FALSE" efi.nvram.var.MLB.reflectHost = "FALSE" system-id.enable = "TRUE" and the MLB, ROM and optionally system-id entered manually eg
      efi.nvram.var.MLB = "W80######BA1A" (MLB can be 13 or 17 characters long, alphanumeric string) efi.nvram.var.ROM = "<=>?@A" (ROM is entered here as a 6 character ASCII string) uuid.bios = "## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##" <---Optional (if you want to inject a given system-id hexadecimal value) Note the output for ROM from imessage_debug is a 12 character hexadecimal that needs to be entered here as a 6 character ASCII string eg using an Hex to ASCII converter we find that "3c3d3e3f4041" hex is equivalent to   "<=>?@A".
       
      Vanilla Mavericks and Yosemite
      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...
       

       
      Enjoy
       
      Update for macOS 10.12 Sierra
      The above settings still work for macOS Sierra after upgrading to VMware Workstation 12.5 and unlocker 2.0.8 - see post #13.
       
      Update for macOS 10.13 High Sierra and 10.14 Mojave
      See post#30 for macOS_iso_cim.tool script to create ISO for macOS using Apple's createinstallmedia utility.
      Post#41 describes how to build "Install macOS ******.app" on the fly from installer files downloaded beforehand in /SharedSupport folder.
       
       
      CECI.zip
      CYI.tool.zip
      CMI.tool.zip
    • 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
       
      Requirements
         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)
      eg
      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 18A391:  For macOS Mojave or High Sierra, use macOS_iso_creator.tool on page 4 of thread.
       
      Good luck and enjoy
      CECI.tool.zip
      CYI.tool.zip
      CMI.tool.zip
    • By Masha24
      Hi guys, I've been lurking in the shadows for months trying to learn how to hackintosh this laptop.  Perhaps if anyone has the time, I could use some help getting it to install 
       
      Trying to install High Sierra on this Laptop:
       
      Lenovo Ideapad 110-171KB-80VK (2017)
      Intel Core i5 7200U
      Intel HD 620 Graphics
      Resolution: 1600x900
       
      Elan PS2 Track Pad - [ACPI\VEN_ETD&DEV_0675 - system device -PCI\VEN_8086&DEV_9D23&SUBSYS_383117AA&REV_21]
      Realtek Network    - [PCI\VEN_10EC&DEV_8136&SUBSYS_383317AA&REV_07]
      Realtech audio
       
      SATA Controller    - [PCI\VEN_8086&DEV_9D03&SUBSYS_382F17AA&REV_21]
      USB 3.0 XHC        - [PCI\VEN_808
       
      --- Using Clover *
      --- I'll attach it below.
       
      I can't quite get it to install, and i've been going in circles for months now ...
      I'll attach everything I have so far including, verbose pics, clover preboot, Clover folder, etc.
       
      Here are some photos of the verbose text leading up to the installer, if maybe there is something useful in here?
       

       
       
       
      And now photos of the installer
       
       
       

       
       

       
       
      Above is an image of the Installer log, (the main pop up window loads from about 10 mins and stops arbitrarily at 2 minutes left, every time) of the nearly hundred attempts i have made, this is the final screen i get, pretty much no matter what i do.
      Sometimes the the order of what it says is different , but the main things of interest are:
       
      "Target is not convertible to APFS: This volume is not formatted as Mac OS Extended journaled."
      "Warning: Couldn't find Board ID, Chip ID, & ECID in new namespace, falling back"
      "Unable to get fs for null"
      " NO native mechanism to verify Applediagnostics.chunklist"
      " NO native mechanism to verify Installfa.plist"
      " NO native mechanism to verify Basesystem.dmg"
      " NO native mechanism to verify AppleDiagnostics.dmg"
      " NO native mechanism to verify InstallESD.dmg"
      " NO native mechanism to verify Basesystem.chumklist"
       
      I have tried many many ... many .. different combinations of kexts, drivers, copies of clover, forks of clover - different copies of drivers and kexts from different sources.. including from all the official repositories.
       
      * I am not trying to install with APFS - the drive i am using is a spinning HDD - so i don't understand the first line quote above.
      * I am using a usb2 slot - there is only two on this machine - 1- usb2 and 1- usb3
      * As you'll see in the Clover folder i'm using APFSdriverloader. - so the installer should detect the installer-APFS-thing - and see it should be HFS+ ?? no?
       
      I'll detail the procedures:
       
      I wiped the Target HDD drive with a live linux USB.
      i prepair the USB with Createinstallmedia method, install clover to the EFI on usb, load kexts and drivers (I've been recently attempting with the Plist from a 'certain other site' Ton*****86) As it has the dvmt preallocation patch and other bits - i'm of course open to ANY other files/pLists .. this is just the one i've been experimenting with lately.)
      Add ' -v ' in clover options to see the verbose output
      in the installer (acts sketchy sorta, delayed and sluggish) i use DiskUtility to erase the drive 'Macos extended journaled'
      Make initial selections, agree to license and begin install.
      it proceeds to 2 minutes left every time, and hangs. many times i've left it for hours, and even overnight.
      I'm honestly not kidding, it's nearly 100 times ive' tried this, i've downloaded high sierra from the app store 5 times to rule out that, i've used countless combinations of everything .. i'm almost completely burned out.
       
       
      If anyone can shed some light i'll be VERY thankful!... I'm ready to go in a completely new direction...please please please help
       
      I'll put the Clover in the next post because i ran out of space in this one......
       
       
       
       
       
       
       
      Here is the latest clover i've been using, with the preboot, and DSDT/SSDT (F2 & F4) in it.
       
      CLOVER-Oct15.zip
       
      Thank you very much for ANY help you can provide
    • By DarkHarthur
      DH67CL
      R7 250
      2 discos duros
      En el 1: Windows 10 y una partición de datos
      En el 2: High Sierra y una particion de datos
       
      Hola, mi problema es el siguiente Clover ya no me muestra EFI Windows; Tenia todo funcionando bien con High Sierra 10.13.6, quise actualizar a Mojave y como tuve muchos problemas decidí volver a High Sierra con el disco duro USB en el que había hecho una copia con Carbon Copy;
      La situacion es algo así, en la carpeta EFI si dejo la carpeta Microsoft, al encender la PC entra directo a Windows, si elimino la carpeta Microsoft si entra con Clover pero no aparece la entrada EFI Windows, ya active legacy en Clover Configurator pero solo me aparecen otras entradas de Windows pero no EFI, todo esto desde el disco duro supuestamente restaurado a como lo tenia antes.
      Si entro con el disco duro USB que tiene la copia que había hecho, me aparecen todas las opciones.
      Si conecto un pendrive tampoco me aparece la opción EFI Windows. 
      Probablemente paso después de desconectar el disco duro de Windows, pero recuerdo que me seguía apareciendo EFI Windows después de haberlo desconectado. Saludos
    • 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...
       

      Pre-Requisites
      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_18A391
      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.
       
       
      startosinstall.command.zip
      InstallInfo.plist_edited_10.13.6.zip
      InstallInfo.plist_edited_10.14.zip
×