Jump to content

17 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
On 4/20/2018 at 12:51 AM, midi-sama said:

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. 


You can use the free trial to do it.

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 shinho73
      Hello everyone. I managed to install AMD Sierra V5(10.12.6) on my old AMD A8 7600 PC(Mother Board-A58M-E, GPU- Palit Geforce GT730 DDR3). Everything is working except the GPU. The GT730 DDR3 GF108 is natively supported on Sierra, but for some reason, it is not working. On Clover Config, "Inject Nvidia" is selected, no Nvidia Web, and nv_disable=1. On "About This Mac" it just says " NVIDIA Chip Model 3 MB".
      I have attached config.plist. Can someone look at it please? Any help will be greatly appreciated. Thank you. 

    • By fusion71au
      Clover r5050 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
      1. Download and unzip "EFI_Clover_r5050 for VMware.zip". Mount Clover-v2.5k-5050-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
    • By MaLd0n

      --Original Post--
      --Bios/UEFI Settings--
      *Update bios/uefi to F7+*
      1- Go to M.I.T./Advanced Frequency Settings tab
      Extreme Memory Profile (X.M.P.) - Profile 1
      2- Go to BIOS tab
      CSM Support - Disabled
      3- Go to Peripherals/Thunderbolt(TM) Configuration tab
      Security Level - No Security
      Thunderbolt USB Support - Enabled
      GPIO3 Force Pwr - Enabled
      4- Go to Chipset tab
      Internal Graphics - Enable
      ---CLOVER FOLDER---
      *Use this folder with FULL DSDT PATCHED
      *Use this folder with FULL DSDT PATCHED
      ---DSDT patch requests is here---



      Intel Core i9-9900K


      CORSAIR H100i RGB PLATINUM AIO Liquid CPU Cooler


      Corsair CMW32GX4M2C3200C16 Vengeance RGB PRO 32GB (2x16GB) DDR4 3200 (PC4-25600)


      MSI RX Vega 64 AIR Boost 8G OC


      Samsung 970 EVO 1TB SSD (MZ-V7E1T0BW) NVMe M.2 V-NAND


      EVGA Supernova 1000 P2 80+ Platinum, 1000W ECO Mode Fully Modular 


      TP-Link Archer T9E


      Thermaltake Core P5 Tempered Glass Black Edition ATX Open Frame Panoramic Viewing

      --DSDT Patches--

      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Thanks to KGP for SSDT Thunderbolt
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
    • By kylon
      Cloud Clover Editor is an open source application that allows you to manage various Hackintosh Bootloaders configs everywhere.

      Open Cloud Clover Editor
      Cloud Clover Editor Wiki
      Cloud Clover Editor Sources
      Supports Clover EFI, Ozmosis, Chameleon, OpenCore GUI and Text Editor Mode CCE Bank Mobile friendly  
      Officially supported browsers
      Chrome 42+ Microsoft Edge 14+ Firefox 39+ Safari 10+ Opera 29+ Opera Mobile 12+ Chrome for Android 75+ Firefox for Android 67+  
      mackie100 - took some ideas from his app Clover EFI dev team Eric Slivka - new serial number Virtual1 - new serial number cecekpawon - PHP 5.3.3 patch, , help with the ACPI Loader Mode flag and more Micky1979 - Clover flying editor  (Discontinued) crusher. - Help with the ACPI Loader Mode flag Download-Fritz - Help with the ACPI Loader Mode flag Pavo - Ozmosis fields and values stehor - Ozmosis fields and values Sherlocks - General help and support gujiangjiang - General help and support  
      Please let me know if i forgot you!
    • 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  AptioMemory --> (consigliato) ->  Link download
       Può essere solo aggiunto manualmente scaricando dal link sopra e collocandolo nella rispettiva cartella
       NOTA: in questo caso non selezionare nessun OsxAptioFixDRV durante l'installazione di clover oppure rimuovetelo                        successivamente. 
                               : Driver64UEFI  ApfsDriverLoader --> (consigliato) --> sostituisce l'uso del driver apfs.efi
                               : Selezionate l'altri driver come da successiva immagine,
      *Nota: Altri driver che si possono usare  al suo posto  sono:
      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 può essere usato anche per effettuare aggiornamenti...
      nel caso guardate...
       Mojave in HFS 
       Oppure direttamente da usb  
      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