Jump to content
thehaus

Clover wont Install to the hidden EFI Partition on SSD OSX Install

13 posts in this topic

Recommended Posts

Update (4/25/16):

 

With the guidance of Slice, I was able to reset the flags on my EFI(disk0s1) partition. Now Clover installer/updater correctly mounts and updates the bootloader in the EFI partition.

 

1. I dowloaded the most current gparted (v2016) and there is now a new flag called ESP in addition to the boot flag on the disk0s1 EFI partition. 

2. Apparently, the older gparted (v2009-2010) I was using wasn't showing me all the flags on the partition. 

3. I double checked the technical specs for OSX EFI partitions and there is supposed to be those two flags (boot and ESP) when using gparted to view the drive. 

4. I turned both flags off and then rewrote them both back by turning them back on within gparted for the EFI partition (disk0s1). That seemed to do the trick. There may have been some data corruption on the boot sector area.

5. The most current version of clover installer/updater v3438 was able to now mount my EFI partition and update the bootloader correctly. The other possibility is that there was a slight change to the clover installer that resolved my drive mounting issue within the clover installer package. Either way, I am relieved.---------------------

I have been having issues with Clover (most current and slightly older versions) not wanting to install to my hidden EFI partition on my SSD OSX installation drive (disk0s1).

I didn't have this issue when i was running Yosemite. Clover updated as it should to my hidden EFI partition and I used UEFI boot without problem.

I decided to update my system to El Capitan doing a clean install. I wiped my SSD using Disk Utility. I first errased the drive, reformatted to a new partition (GUID HFS) and created my UEFI USB El Capitan loader. I installed El Capitan to the SSD without issue.

 

After installation, both the EFI and the OSX partition where created properly along with the recovery partition.

 

I rebooted using the UEFI USB and configured OSX after the welcome screen. I then tried to run the latest version of Clover for the UEFI installation and it failed as it couldn't open the EFI hidden partition and install the kexts and Clover. It basically failed to mount the EFI partition and install to the EFI partition. I even mounted the EFI partition on disk0s1 where my OSX install was on my SSD and it didnt create any files or folders in the partition. I did create an EFI folder with everything in my root OSX partition instead (very odd). I double and triple checked that i selected UEFI as I always do and that the drive was indeed the OSX SSD installation drive.

I manually mounted disk0s1 EFI partition and it had nothing from clover in it. 

I wiped the EFI partition and tried again without success.

I reloaded my GA-Z97MX Gaming5 firmware v6 again and it still failed to load clover into the EFI partition. It did create a EFI folder in my root directory for OSX with all the correct files but i couldn't boot to it using UEFI (YES- i was selecting UEFI from the menu, i have done this successfully on Mavericks and Yosemite many times before)

If I move the folder and files from the root EFI folder to the EFI partition, I can boot OSX using UEFI

I used gparted to reformat the SSD and try to do another fresh install of OSX again thinking that Disk Utility didn't get rid of all the old bootloader info. Clover couldn't mount the hidden EFI partition on disk0s1. I could do it manually though.

I manually mounted the EFI boot partition for my SSD and moved all the clover/mulitbeast files over there. I was able to again boot UEFI SSD El Capitan.

When I try to update clover, it doesn't open the hidden EFI partition or update the files in it. It does, however, create an EFi folder in my OSX root with the new Clover bootloader files there.

 

------------------------------------------------

 

Original post:

 

Background facts:

I have done this successfully many times with both Mavericks and Yosemite in the past using the Clover UEFI booloader

1. I clicked uefi

2. The hidden EFI partition exists on my SSD (disk0s1) OSX install

3. I tried reformatting the drive using gparted and Disk Utility as was outlined in the guides

4. I tried erasing just the EFI partition and changing the file structure

5. I reloaded my GA-Z97MX Gaming5 v6 firmware

6. I did check off the box for loading Clover as uefi

7. I told Clover to install into the ssd OS X drive (I doubled and triple checked this)

8. I booted everything using Uefi from both my F12 option and BIOS option - I don't Legacy boot

9. I tried the most recent versions of Clover. I also tried an older version of Clover for curiosity. 
----------------------

Nothing I do can seem to get Clover to load to the hidden EFI partition on my SSD OSX install (disk0s1)

 

Does anyone have an idea what I need to fix to get Clover to recognize, mount, open, and install to my EFI partition on my SSD (disk0s1)?

Share this post


Link to post
Share on other sites
Advertisement

i tried all many of the older clover installers and none of them could mount the EFI partition. They all create an EFI folder in the root of the OS X partition.

 

I just reformatted my SSD again and tried a fresh install but no luck.

 

I ran terminal "diskutil list" and disk0s1 is EFI as it should be.

 

Here is my clover install log:

 

Clover EFI installer log - Tue Apr 12 19:14:33 PDT 2016

Installer version: v2.3k r3320 EFI bootloader
======================================================
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *256.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:          Apple_CoreStorage El Capitan              255.2 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
/dev/disk1 (internal, virtual):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS El Capitan             +254.8 GB   disk1
                                 Logical Volume on disk0s2
                                 87062435-B34A-4B60-87A5-BDF4C72E52A5
                                 Unencrypted
/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *16.0 GB    disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS El Capitan USB Insta... 15.7 GB    disk2s2
======================================================
Installing BootSectors/BootLoader
 
Stage 0 - Don't write any of boot0af, boot0md, boot0ss to /
Stage 1 - Don't write any of boot1h2, boot1f32alt, boot1xalt to /
 
======================================================
=========== Clover EFI Installation Finish ===========
======================================================

Share this post


Link to post
Share on other sites

Please read my first post so you understand that I formatted my drives properly, ran Clover properly, Check the terminal commands to check for proper mapping of OSX partitions. I also followed all the plist changes for SIP. IF that wasnt the case, my copy of OSX not only wouldn't install, it also wouldnt boot into OSX. This is not my issue.

 

In plist, among other minor changes, I set:

 

rootless=0

 

<key>RtVariables</key>
<dict>
<key>CsrActiveConfig</key>
<string>0x3</string>
<key>BooterConfig</key>
<string>0x28</string>
</dict>

 

For curiosity, i reformatted my SSD again and loaded Yosemite to see if I could get Clover to install to the EFI partition and it couldn't. For some reason, Clover can't mount my EFI partition on my SSD no matter which OS version I load or which Clover version I use.

 

If i check or uncheck ESP in Clover, it always creates a EFI root folder in OSX. I have to move the contents over to the EFI partition manually to get UEFI functionality. It makes updating Clover a real pain every time I update Clover and should be automated in its functionality.

 

My SSD drive must have a flag set somewhere that makes Clover not mount the EFI partition. I have no issues mounting the EFI partition manually using Clover Configurator, EFI Mounter, and Terminal commands.

 

It doesn't seem due to the OS or the SSD drive partition formats and disk #'s

I reflashed my BIOS firmware many times also.

I tried to reflash my Crucial M4 SSD firmware but it says it is the latest and I cant make it repush the firmware.

 

Anyone else have any ideas how to get Clover to recognize and mount my EFI partition so it will load the booloader there automatically?

Share this post


Link to post
Share on other sites

AFAIK rootless=0 doesn't work in 10.11, it's done through CsrActiveConfig (which you have). I would just try setting it to 0x67 instead of 0x3. See if that makes any difference. :)

 

FYI: You don't have to install Clover in the EFI for UEFI to work. In fact, I think it works better installed to / if your BIOS will support it. ;)

 

You also might want to try changing your Clover install from "CloverEFI 64-bits SATA" to "CloverEFI 64-bits BiosBlockIO". I know it makes a difference on the drives that are recognized by Clover on bootup for my system (Gigabyte X79-UD5).

Share this post


Link to post
Share on other sites

Update (4/25/16):


 


With the guidance of Slice, I was able to reset the flags on my EFI(disk0s1) partition. Now Clover installer/updater correctly mounts and updates the bootloader in the EFI partition.


 


1. I dowloaded the most current gparted (v2016) and there is now a new flag called ESP in addition to the boot flag on the disk0s1 EFI partition.


2. Apparently, the older gparted (v2009-2010) I was using wasn't showing me all the flags on the partition. 


3. I double checked the technical specs for OSX EFI partitions and there is supposed to be those two flags (boot and ESP) when using gparted to view the drive.


4. I turned both flags off and then rewrote them both back by turning them back on within gparted for the EFI partition (disk0s1). That seemed to do the trick. There may have been some data corruption on the boot sector area.


5. The most current version of clover installer/updater v3438 was able to now mount my EFI partition and update the bootloader correctly. The other possibility is that there was a slight change to the clover installer that resolved my drive mounting issue within the clover installer package. Either way, I am relieved.


Share this post


Link to post
Share on other sites

I have this issue as well, and have always had it since using Clover.

 

I can mount the EFI partition myself and copy the Clover files to it and boot from it without issue, but Clover never sees the partition itself when I choose Installation Location whether I have the EFI partition mounted or not.

 

I've checked the partition flags and both boot and ESP are set, but I haven't yet tried re-setting them yet (I had to use PARTED on the SysRescue live CD as the GPARTED live CD wouldn't boot for me)

Share this post


Link to post
Share on other sites

I have this issue as well, and have always had it since using Clover.

 

I can mount the EFI partition myself and copy the Clover files to it and boot from it without issue, but Clover never sees the partition itself when I choose Installation Location whether I have the EFI partition mounted or not.

 

I've checked the partition flags and both boot and ESP are set, but I haven't yet tried re-setting them yet (I had to use PARTED on the SysRescue live CD as the GPARTED live CD wouldn't boot for me)

 

I am also having the same issue. What is odd to me is that the Clover installation was working correctly, but I reformatted the drive to start fresh and now I cannot get Clover to install my second time around. I've even went through GParted Live USB and reset the "ESP" and "Boot" flags but still can't get the machine to find it. I'm kicking myself now... :wallbash:

 

Edit: I had to have GParted Live on my USB as just the FAT partition type. FAT32, which it says is compatible, wouldn't boot it.

 

2nd Edit: Does your system have CoreStorage when you type out 'diskutil list' in Terminal?

Share this post


Link to post
Share on other sites

 

2nd Edit: Does your system have CoreStorage when you type out 'diskutil list' in Terminal?

 

Apologies for the delay, have a guest visiting and not been at the comp much.

 

Just ran the command and no, CoreStorage is not mentioned. Here are my results:

[01:59][rob@iMac:~]$ diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS MacPC                   499.1 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

The EFI partition is currently mounted and I can access it via Finder but the Clover installer doesn't see it. (Just tried the 3726 release)

Share this post


Link to post
Share on other sites

Apologies for the delay, have a guest visiting and not been at the comp much.

 

Just ran the command and no, CoreStorage is not mentioned. Here are my results:

[01:59][rob@iMac:~]$ diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS MacPC                   499.1 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

The EFI partition is currently mounted and I can access it via Finder but the Clover installer doesn't see it. (Just tried the 3726 release)

 

 

If you use this clover

there are no such problems with installation on the SSD or HDD.

post-617057-0-14349800-1472967881_thumb.jpg
 
SSD disk.


Clover EFI installer log - Sun Sep  4 09:40:44 OMST 2016
Installer version: v2.3k r3726 EFI bootloader
======================================================
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *256.1 GB   disk0
   1:                        EFI UEFI                    209.7 MB   disk0s1
   2:                  Apple_HFS OSX10.9.5               201.1 GB   disk0s2
   3:                  Apple_HFS PlextorArch             54.0 GB    disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *750.2 GB   disk1
   1:                       0x1C                         23.1 GB    disk1s1
   2:               Windows_NTFS OS                      187.5 GB   disk1s2
   3:               Windows_NTFS DATA                    539.5 GB   disk1s5
======================================================
Backing up EFI files
 
Backing up stage2 file /Volumes/OSX10.9.5/EFIROOTDIR/boot  to /Volumes/OSX10.9.5/EFI-Backups/r3728/2016-09-04-09h40/boot
Backing up /Volumes/OSX10.9.5/EFIROOTDIR/EFI folder to /Volumes/OSX10.9.5/EFI-Backups/r3728/2016-09-04-09h40/EFI
======================================================
Installing BootSectors/BootLoader
 
Stage 0 - Don't write any of boot0af, boot0md, boot0ss to /
Stage 1 - Don't write any of boot1h2, boot1f32alt, boot1xalt to /
Stage 2 - Written boot7 (x64) to /Volumes/ESP/boot
======================================================
Installing RC Scripts
 
Installing RC scripts on target volume '/'
 
Activating /etc/rc.boot.d/70.disable_sleep_proxy_client.local rc script
 
======================================================
=========== Clover EFI Installation Finish ===========
================================================

0:723  0:000  Now is 4.9.2016,  4:6:24 (GMT)
0:723  0:000  Starting Clover revision: 3726 on CLOVER EFI
0:723  0:000  Build with: [Args: ./ebuild.sh -fr -D NO_GRUB_DRIVERS_EMBEDDED | Command: build -D NO_GRUB_DRIVERS_EMBEDDED -D USE_LOW_EBDA -p Clover/Clover.dsc -a X64 -b RELEASE -t XCODE5 -n 5 | OS: 10.12 | XCODE: 7.3.1]
0:723  0:000  SelfDevicePath=PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,80)\HD(1,GPT,F61211C5-87B9-4CDD-BE33-9DC9BD4A478E,0x28,0x64000) @1F44E698
0:723  0:000  SelfDirPath = \EFI\CLOVER

HDD disk.

 


Clover EFI installer log - Sun Sep  4 10:19:34 OMST 2016
Installer version: v2.3k r3726 EFI bootloader
======================================================
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *240.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS OS_X10.11.xssd          190.2 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:                  Apple_HFS archssd                 48.9 GB    disk0s4
 
/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                  Apple_HFS 12x                     499.6 GB   disk1s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
   4:                  Apple_HFS arch12x                 499.6 GB   disk1s4
 
======================================================
Backing up EFI files
 
Backing up stage2 file /Volumes/12x/EFIROOTDIR/boot  to /Volumes/12x/EFI-Backups/r3728/2016-09-04-10h19/boot
Backing up /Volumes/12x/EFIROOTDIR/EFI folder to /Volumes/12x/EFI-Backups/r3728/2016-09-04-10h19/EFI
======================================================
Installing BootSectors/BootLoader
 
Stage 0 - Don't write any of boot0af, boot0md, boot0ss to /
Stage 1 - Don't write any of boot1h2, boot1f32alt, boot1xalt to /
Stage 2 - Written boot7 (x64) to /Volumes/ESP/boot
======================================================
Installing RC Scripts
 
Installing RC scripts on target volume '/'
 
Activating /etc/rc.boot.d/70.disable_sleep_proxy_client.local rc script
 
======================================================
=========== Clover EFI Installation Finish ===========
======================================================
 

 
0:834  0:000  Now is 4.9.2016,  4:24:17 (GMT)
0:834  0:000  Starting Clover revision: 3726 on CLOVER EFI
0:834  0:000  Build with: [Args: ./ebuild.sh -fr -D NO_GRUB_DRIVERS_EMBEDDED | Command: build -D NO_GRUB_DRIVERS_EMBEDDED -D USE_LOW_EBDA -p Clover/Clover.dsc -a X64 -b RELEASE -t XCODE5 -n 5 | OS: 10.12 | XCODE: 7.3.1]
0:834  0:000  SelfDevicePath=PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,80)\HD(1,GPT,FBA19309-7C18-433A-9A9C-33D50952839D,0x28,0x64000) @DD442098
0:834  0:000  SelfDirPath = \EFI\CLOVER

Share this post


Link to post
Share on other sites

--EDIT Deleted everything.

 

*sigh* Was operator error. I was (wrongly) assuming that the EFI installer would appear in the list of drives which it wasn't. I had to choose the drive with the EFI partition. Then Select Customise and then Install clover in ESP for it to install on the EFI partition.

post-1462892-0-45227900-1472982868_thumb.png

post-1462892-0-58032300-1472982879_thumb.png

Edited by tarasis

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
      Clover r4961 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.14 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4961 for VMware.zip". Mount Clover-v2.4k-4961-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 gengik84
      Ciro82==>>Thanks
      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
      ShowAllfiles 
      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.
      “CONDIZIONI OBBLIGATORIE”
      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”.
      Immagine 
      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
      Immagine  
      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"
      Immagine 
       
      =====================
        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
      Esempio
      ===========================
      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.... 
      BENE…IL PROCESSO DI CREAZIONE E’ INIZIATO…
      AVREMO CIRCA 20/30 MINUTI DI TEMPO LIBERO A CUI DEDICARSI A CIO’ CHE VOGLIAMO………………………………………..  
      COLGO L’OCCASIONE PER FARVI NOTARE LA VELOCITA’ E LA SICUREZZA DI QUESTO METODO
      CONFRONTATE QUESTO CON IL TERZO METODO E NOTERETE CHE CON UN SOLO PASSAGGIO, OSSIA IL COMANDO DATO AL TERMINALE, FACCIAMO IN UNA SINGOLA OPERAZIONE TUTTI I VARI STEP DESCRITTI SULL’ ALTRO METODO.
      DETTO QUESTO, MOLTO IMPORTANTE E’ SOTTOLINEARE CHE COSI’ FACENDO EVITEREMO ERRORI  DI DISTRAZIONE RIGUARDO AI PASSAGGI O FRAINTENDIMENTI.
      Immagine 
      Potete adesso passare ad installare il bootloader Clover sulla vostra usb.
      *NOTA*:
      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)
      ==========================
      Bootloader
      **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.
      Immagine 

       
      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) 
                               : 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:
       informazioni 
       
      Proseguite con l’installazione.
      Immagine 
      ** Ricordate che avrete accesso a questa cartella dopo aver montato la partizione EFI**
      ===========================
      Per installazione Legacy
      Immagine 
      ===========================
      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”
      Immagine 
      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
      Immagine 
      5) Sezione BOOT: Sole se si sta installando Yosemite mettete il flag su kext-dev-mode=1
      Immagine 
      6) Sezione RT Variables: Se si sta installando El Capitan oppure Sierra, aggiungere i valori: BooterConfig= 0x28, CsrActiveConfig= 0x67
      Immagine 
      7) Sezione System Parameters: Su inject kext mettete YES
      Immagine 
      ===========================
      Nota: Su El Capitan, è stato introdotto SIP (System Integrity Protection)
      Info:
      ===========================
      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
      Immagine 
      
      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.zip
      Pacchetto-2.zip
      Pacchetto-Fake+Sensors 6.26.1440.zip
      C_I_M.zip
       
      apfs.efi-10.14-beta1_No_Log.zip





       

×