Jump to content
Anachronaut

[How To] Remove Extra Clover BIOS Boot Entries & Prevent Further Problems

27 posts in this topic

Recommended Posts

Clover is a great boot loader, however, some people are still having problems. I think a lot of this has to do with the design of the systems. Many have extra backup internal hard drives or partitions with legacy boot loaders or previous Clover systems. While this may have been fine in the past, with Clover and the newer OS X's, this does not work on many motherboards. 
 
Often it happens that Clover and El Capitan (or Yosemite) will install and seem to work fine, but then degenerate to an unusable state. I chased this problem for quite a while before I found the solution (see Source #1 below).
 
Look at the boot options list in your BIOS. If you see entries that are not physical drives, it is likely that you are encountering some form of this problem.
 
First, remove all of the extra boot entries.
 
0. You COULD try to reflash the BIOS and you MAY be done. This worked on my 6 series board, but not on my current 9 series. If it works for you, skip to the second section on preventing the problem from happening again. If this does not work, or if you really don't want to have to flash the BIOS, then continue.
 
1. Disconnect all drives except one with only one instance of Clover. If you only have a partitioned drive with ANY backups on the partitions, it is probably best to boot with only the Clover Install USB stick and no other drives attached.
 
2. Boot your system and press the right arrow key when the Clover boot loader appears.
 
2b. If you cannot get to Clover, reset your CMOS and try again, this time going into the BIOS and selecting your physical drive for boot override. DO NOT touch any other entries at this point as it may lock the BIOS and you will need to reset the CMOS and start over again. It SHOULD work, so keep trying – I don't know another way.
 
3. Use the right and left arrow keys to select the Clover UEFI Shell and hit enter. The following screen should appear, and either let it time out, or press a key:
 
post-985174-0-35168800-1444628002_thumb.jpg
 
4. At the Shell> prompt type

bcfg boot dump
the results should look something like this:
 
post-985174-0-61046600-1444628004_thumb.jpg
 
5. You need to remove any entry that is not a physical hard drive. As far as I know, if it is a real physical disk, it will list as DevPath - HD.
 
 
post-985174-0-61704000-1444628006_thumb.jpg
 
The code to remove an entry looks like this:

bcfg boot rm XX
where XX is the Option number. In this example, I remove Option 02 with

bcfg boot rm 02
post-985174-0-58902700-1444628008_thumb.jpg
 
 
 
If you have a LOT of bogus entries, it is best to do just a few, and then type the command

bcfg boot dump
again before repeating the process. When I first did this on my ASUS H97 board, I had at least 10 entries to clear so it took several iterations of this process.
 
6. When your have removed all entries that are not physical hard drives, type

exit
and press the return key. This will get you back to the main Clover screen. At this point, I would choose restart from the Clover choices and enter the BIOS to check if your work was successful.
 
 
 
Second, rethink your system design and backup scheme to prevent this from happening again.
 
• Design your system so that there is only one disk (an SSD if you like speed) that has an EFI partition that contains the Clover boot loader. Of course in OS X, all (I think) formatted drives will have an EFI partition, but you do not want two EFI partitions that contain ANY boot loader – that includes Clover, Chameleon, Chimera or whatever.
 
• On some boards, it may help to set the boot options for all devices to UEFI Only (didn't make a difference on my board, but did speed up boot time).
 
• Currently, I have a 250 GB M.2 SSD as my boot disk, and the others are just for data. For backups I use EXTERNAL DISKS, so that I don't reencounter the same problems. The external drives are connected only when I need to backup. [i am working on a GUIDE for Clonezilla.] External USB 2.0 or USB 3.0 drive enclosures are quite reasonably priced at the moment, so I encourage you to do this as well. I think you could use Time Machine for data backup, but I have no experience with this.
 
• Currently I am only running Mac OS X 10.11 El Capitan. It would be great to hear about successful system designs in the same way I am discussing here from others who are also running Windows, Linux or other versions of Mac OS X
 
 
 
Source #1 - Thanks to trioset

Share this post


Link to post
Share on other sites
Advertisement

THAT ^^^^^  bit of detective work SO totally rocks, sir... I've been running down this ghost-in-the-machine for over two years...

 

I knew there was something goofy going on - (besides myself - mea culpa)...

 

thanks for that!!!... thank you, thank you... anachronaut... THANK YOU !!!!...

 

everybody/anybody else?  - comments?...

Share this post


Link to post
Share on other sites

Can't claim expertise on this subject, but what I found is that:

 

- you select "Disabled" under "Boot Priority" for all, except the boot disk

- under Clover, you remove the entries, as per Anachronaut's advice

- you reboot, enter BIOS and sure enough they are disabled

- retry "bcfg" in Clover, and the entries are back!

 

What am I doing wrong? How can one make this stick?

 

TIA

 

Xen

Share this post


Link to post
Share on other sites

Can't claim expertise on this subject, but what I found is that:

 

- you select "Disabled" under "Boot Priority" for all, except the boot disk

- under Clover, you remove the entries, as per Anachronaut's advice

- you reboot, enter BIOS and sure enough they are disabled

- retry "bcfg" in Clover, and the entries are back!

 

What am I doing wrong? How can one make this stick?

 

TIA

 

Xen

 

I think you misunderstood. You do not disable all of the internal hard drives except one in the BIOS. To make this work, you need to physically disconnect the drives, leaving only one drive with a boot loader connected to the system. Then you need to look at your boot list in the BIOS. If you still have entries there other than your hard disk, then remove them.

 

To make it stick, you need to remove the boot loaders from the other disks before you connect them back to your system. This probably means saving the data elsewhere, reformatting the disks and then restoring the data (probably other methods, but I am no expert on this). Or, you could put the drives in an external USB 2.0 or 3.0 case with the boot loaders intact and connect them only when you need them. You shouldn't have a problem with either method.

 

Here is what my BIOS looked like after doing this. The only real boot drive is my M.2 Samsung. [Well, except the other Samsung at the sata1 port - but this is and IDENTICAL CLONE to the boot M.2 drive at sata5, so I think the BIOS is ignoring it in the boot list.] The other "boot" entry is a blank MS-DOS formatted 8GB flash drive that the BIOS thinks for some reason is bootable - this does go away when it is removed. (The 2TB drive is about to be removed and the Samsung at sata1 normally sits in an external case now.)

 

post-985174-0-36261200-1444793495_thumb.png

 

 

post-985174-0-52241000-1444793504_thumb.png

Share this post


Link to post
Share on other sites

Thanks for taking the time to respond. I'll try to figure this out - the part about physical removal, I don't like at all...

Share this post


Link to post
Share on other sites

Thanks for taking the time to respond. I'll try to figure this out - the part about physical removal, I don't like at all...

 

Great. Here is a bit more on this. After messing about with this, I noticed that the entries that I had on the above screen shots did not all look like physical disks. "UEFI OS(238475MB)" is not a physical disk. So I removed the Samsung SSD from sata1, and put it back in its external case. Since it is about to be removed anyway when I get the chance, I disconnected the SATA  and power connectors to the 2TB drive at the same time (it is blank at the moment anyway, and I do not need the storage space). After boot, here is what the relevant parts of the BIOS looked like:

 

post-985174-0-94809400-1444795919_thumb.png

 

 

After the first attempt to remove the offending items, it looked like this:

 

post-985174-0-71947000-1444795926_thumb.png

 

 

This time there was no physical drive listed with bcfg boot dump, so I deleted all entries and restarted. This is the final result:

 

post-985174-0-71604300-1444795933_thumb.png

 

 

Now the system is happy again and back to its stable state.

 

If I had kept everything connected on my system, it would have just kept adding another "UEFI OS(238475MB)" to the system every time I rebooted. Eventually (as happened before) it would "lock" the BIOS requiring me to go through the "reset CMOS" and then delete the extra entries.

Share this post


Link to post
Share on other sites

Now the system is happy again and back to its stable state.

Still, it's hard to swallow that one must remove storage disks from a personal computer in order to achieve stable function.

 

Based on your experience about this procedure, does it resolve the infamous "wake after sleep reboot" issue? If so, can one re-attach the disks and get away with it?  Prevent Clover from populating the damn bcfg list, maybe? What about the meaning of life - do we get any closer?

 

Thanks for documenting your efforts on this one.

Share this post


Link to post
Share on other sites

Still, it's hard to swallow that one must remove storage disks from a personal computer in order to achieve stable function.

 

Based on your experience about this procedure, does it resolve the infamous "wake after sleep reboot" issue? If so, can one re-attach the disks and get away with it?  Prevent Clover from populating the damn bcfg list, maybe? What about the meaning of life - do we get any closer?

 

Thanks for documenting your efforts on this one.

 

You just need to remove the storage disks until they have the boot loader removed, at least on my system. If there is no boot loader installed on the drives, they should cause no problems.

 

My system never had the "wake after sleep reboot" problem, but it did have a black screen after sleep that required a hard reset (with the switch). This has mostly solved this problem (still shows up once in a while, and I don't know why).

Share this post


Link to post
Share on other sites

You're right. I was hoping that this Clover bcfg procedure was the elusive fix for the freeze you mentioned in your other thread.

 

Can't hurt to hope.

 

On the EFI boot loader issue: all Disk Utility-formatted disks have an (empty) EFI partition, which, I guess, does not cause BIOS trouble, unless a bootloader resides there. In my case, I had a genuine Apple /EFI/BOOT folder (containing a "firmware" file), on one of my backup disks, and I promptly removed it.

 

Clover's "bcfg dump" lists all disks, even ones I have disabled under BIOS Boot Priority.

 

Trivial issues aside, I think that your statement that Clover Z97 systems may "degenerate to an unusable state" is an important one.

Share this post


Link to post
Share on other sites

You're right. I was hoping that this Clover bcfg procedure was the elusive fix for the freeze you mentioned in your other thread.

 

Can't hurt to hope.

 

On the EFI boot loader issue: all Disk Utility-formatted disks have an (empty) EFI partition, which, I guess, does not cause BIOS trouble, unless a bootloader resides there. In my case, I had a genuine Apple /EFI/BOOT folder (containing a "firmware" file), on one of my backup disks, and I promptly removed it.

 

Clover's "bcfg dump" lists all disks, even ones I have disabled under BIOS Boot Priority.

 

Trivial issues aside, I think that your statement that Clover Z97 systems may "degenerate to an unusable state" is an important one.

 

It actually might be the solution to the freeze issue, but that other post was with my Gigabyte Z68 board. I have put that aside for now, as I originally thought it was broken. When I have time (and buy a new cheap case to house it) I will try to resurrect it. I will post the results of my efforts when (if) I get them.

 

My current computer did not wake the display from sleep this morning, requiring a reset. Since then, however, sleep is working properly. 

 

My Z97 board certainly did degenerate into an unusable state. Resetting the CMOS, I was just able to boot Clover and fix the problem. If I touched any of the "phantom" items in the boot priority list, the BIOS would freeze and I would have to start over. There were so many of the "phantom" items in the boot list it was "full", and I think it was almost overwriting itself, causing the problem.

 

A side note. With the Samsung SSD attached to sata1, Mac OS X would choose this as the boot drive, no matter which drive I chose in Clover. My main boot drive, the Samsung M.2 SSD was attached at sata5 due to the design of the motherboard. It seems that on this system, Mac OS X prioritizes to the drive with the lowest sata number, given that all other things are equal. There are certainly some strange things going on that should be researched by people who know a lot more about these things than I do.

Share this post


Link to post
Share on other sites

@Anachronaut I'm on a non uefi motherboard and I need to remove some entries, if I choose uefi shell at clover boot screen nothing happens, the screen turns into black and I have to force shut down....

Share this post


Link to post
Share on other sites

Exactly what I'm need. I'm curious why my boot entry like "Mac OS X" is always show even I'm remove all physical disk. Have several identical entry is bit annoying. Windows easy UEFI looks make this job easier, but my windows still legacy, so i'll try clover UEFI shell  instead. Thank you for this solution ♪

Share this post


Link to post
Share on other sites

@Anachronaut I'm on a non uefi motherboard and I need to remove some entries, if I choose uefi shell at clover boot screen nothing happens, the screen turns into black and I have to force shut down....

 

I don't know much about using this with a non uefi motherboard. It is likely that this method will not work without a uefi bios. I would try reflashing the bios and see if that does the trick. Make sure to make note of any particular bios settings before the reflash.

Share this post


Link to post
Share on other sites

Thank you for your replay. You said << Make sure to make note of any particular bios settings before the reflash. >> True. My Bios has tons of settings, many of them have been modified to make the machine stable and reliable after Overclock, for sure I've better to skip unwanted entries with arrow keys than doing a reflash and redoing all those settings.... Moreover if I'll upgrade the system from Apple Store installer I'll get unwanted entrie(s) again, as the Installer icon at Clover bootscreen will stay even after upgrade is done. This is the downside of an old X58 motherboard (non Uefi) like mine, but it's not that deal breaker, the machine still runs like a champ!

 

GA-X58A-UD7 Xeon W3680 @4,40Ghz 24Gb GTX760 Geekbench 19500pts

Share this post


Link to post
Share on other sites

Just wondering if there is any update on the solution  matter??? I have windows legacy on my SSD and MacOs in another hardrive, Reinstalling windows is not an option for me.... Is there any other way to fix the multiple volumes problem (multiple boot entries)?    

Share this post


Link to post
Share on other sites

I have done this method and I still end up getting a new phantom every reboot from osx. I removed all physical drives and only left the one with clover (ssd) and removed all entries via clover rebooted then shut down and added my drives back and it's still happening. Could this be because I have a windows 10 install on another ssd? Windows is on port 0, osx on port 1.

I'm wondering if I need to reinstall both operating systems and if I do in which order should I do it to stop these entries from reoccurring?

Share this post


Link to post
Share on other sites

I have done this method and I still end up getting a new phantom every reboot from osx. I removed all physical drives and only left the one with clover (ssd) and removed all entries via clover rebooted then shut down and added my drives back and it's still happening. Could this be because I have a windows 10 install on another ssd? Windows is on port 0, osx on port 1.

I'm wondering if I need to reinstall both operating systems and if I do in which order should I do it to stop these entries from reoccurring?

 

This behavior is apparently due to a bug in the bios, as it reportedly also affects Linux machines. The Windows drive contains its own boot loader on the boot partition of the drive from the install of Windows. This is probably why it still adds entries after reconnecting the drives. From my understanding, the solution is to remove the boot loader from the Windows drive, and just let Clover handle everything. I have no idea how to do this and still keep the Windows drive bootable. If you try something like this and are successful, please post your method so others can benefit. Apparently, you need to have only one installed boot loader (Clover) for all of your operating system drives.

Share this post


Link to post
Share on other sites

This behavior is apparently due to a bug in the bios, as it reportedly also affects Linux machines. The Windows drive contains its own boot loader on the boot partition of the drive from the install of Windows. This is probably why it still adds entries after reconnecting the drives. From my understanding, the solution is to remove the boot loader from the Windows drive, and just let Clover handle everything. I have no idea how to do this and still keep the Windows drive bootable. If you try something like this and are successful, please post your method so others can benefit. Apparently, you need to have only one installed boot loader (Clover) for all of your operating system drives.

Yeah I thought as much but I have no idea how to remove the windows bootloader and keep it bootable. Would it help to install osx on one drive first then keep it connected and install windows on the other? Maybe windows will then use the efi partition on the osx drive?

Just a thought.

Share this post


Link to post
Share on other sites

Hey guys, I just wanted to bump this thread to see if there was any new information on this and/or how to fix it. I'm getting the same thing - A duplicate Boot Option entry every time I reboot OSX. I'm up to 46 entries now. - I have a GA-Z170X-UD5-TH motherboard and a 256GB SSD for Windows and 512GB SSD for OSX in the machine with a bunch of other drives as well. I've attached some picts. Any advice would be appreciated.

Thanks!

 

2016-02-11%2011.40.32.jpg

Share this post


Link to post
Share on other sites

I have exactly the same Motherboard as isotropy, and am having exactly the same issues. Surely there has to be some way to prevent all these extra boot option entries so it only reflects drives with bootable operating systems on them. The other solutions offered such as only using external drives.. No use to me. i need to dual boot to windows, and i need to have large amounts of storage. Surely the coders of clover have more than 1 drive attached to there rigs. and have included this in there code.

Share this post


Link to post
Share on other sites

@Cerberus73, @isotropy,

 

My suggestion would be to set your BIOS to boot from only the one hard drive and keep all the EFI boot-loaders in that drive's EFI System Partition

 

The easiest approach would be to set the Windows Hard Drive as the boot drive and only use its EFI to boot:

 

1.  Move the EFI folder containing Clover from the OSX hard drive over to the EFI Partition on the Windows Hard Drive - see Manually install Clover in Windows.

2.  Boot to Windows and install EasyUEFI

3.  Use EasyUEFI to create an entry for CLOVERX64.efi and give it first priority in UEFI booting

4.  Delete all the other duplicate entries

5.  Reboot and use Clover to launch OSX or UEFI Windows

 

Good Luck!

Share this post


Link to post
Share on other sites

I also had this issue on my Z170 mobo, used EasyUEFI to remove the existing entries, added one pointing to CLOVERX64.efi, and renamed the BOOT folder in my EFI partition and the extra entries stopped appearing.

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





       

    • By kushwavez
      Acer Aspire V15 V5-591G - Mojave 10.14.5
       
      (Note: mine is 55TU version, but the bootpack will work fine with another versions of 591G, for example: V5-591G-71K2, -764Z, -59PU, etc.)
      Specifications:
      - Motherboard: USOPP_SLS (Skylake-H PCH)
      - BIOS:Insyde Corp. v 1.15
      - CPU:Intel Core i5-6300HQ 2.3 GHz (Skylake)
      - GPU: NVIDIA GeForce GTX 950M 2 GB (Optimus) & Intel HD Graphics 530
      - RAM:SK hynix 4 GB DDR4 (Later I bought + KINGSTON 4 GB) 2133 MHz
      - WiFi + Bluetooth:Qualcomm Atheros QCNFA344A 5 GHz (Later -> Broadcom BRCM94352Z M.2 5 GHz WiFi + 4.0 Bluetooth)
      - Audio:Realtek HD Audio: ALC 255 
      - Ethernet: Realtek RTL8168/8111
      - Card Reader:Realtek USB 2.0 Card Reader (USB2.0-CRW)
      - Webcam:HD Webcam
      - HDD:TOSHIBA MQ01ACF032 320 GB HDD
      - SSD:SPCC M.2 230 GB SSD
      - Display:1366x768 (15.6", Matte)
      - Battery: 6 cell 56Wh / 5040mAh
      - Connectors: 
      1x SD Card Reader 2x USB 3.0 (1x USB Charging), 1x USB 2.0 1x VGA 1x HDMI 1x 3.5mm microphone/audio combined jack connector 1x Ethernet (Rj-45) - Keyboard & Touchpad:Multi-Touch & Multi-gestures ELAN 501 Touchpad, Backlight Keyboard.
      Working:  
      - Wi-Fi (with BCM94352Z)
      - Bluetooth hand-off (With BCM94352Z)
      -Full Graphics enabled on HD 530: ig-platform-id: 0x191b0000 (HD 530 Mobile)
      - Display: if default colour profile is corrupted (blue is not actual blue but purplish) Use "Rec. ITU-R BT. 709-5" Color Profile (System Pref. -> Displays -> Color)
      -HDMI & VGA Outputs: AppleGraphicsDevicePolicy.kext Clover patch
      - Audio (ALC 255):(Internal Speakers, Internal Microphone, Headphone jack with AppleALC, ALCPlugFix -> layout-id=17)
      - Ethernet Realtek 8168/8111: RealtekRTL8111.kext
      - App Store, Messages, FaceTime, Siri, iCloud(native)
      - Integrated webcam(native)
      - 3.0 USB (native)
      - Touchpad and Keyboard(ELAN501): Fn keys are good, the weird thing is the Brightness key. On my keyboard it's Pause Break:Br-up, Fn+F12:Br-dwn-> To fix this try Karabiner (VoodoPS2Controller.kext), - for gestures try SmartTouchpad drivers
      - Battery info:Install ACPIBatteryManager.kext with Kext Utility or other installer.
      - Sleep Mode
      - SSD with TRIM enabled (to enable trim, open Terminal and write "sudo trimforce enable")
      Not working:
      - Original Wi-Fi (Qualcomm Atheros QCNFA344A):  unsupported, you need switch to BCM94352Z or just use a mini usb wifi dongle.
      - NVIDIA GeForce GTX 950M: Optimus not supported.
      - Card Reader: Unsupported -> Can't really fix because I don't have any SD Card at the moment, maybe can be fixed by adding Prod & Ven IDs to AppleStorageDevices.kext, I never used it anyway. name: "USB2.0-CRW" Prod ID: "0x0129" Ven ID: "0x0bda  (Realtek Semiconductor Corp.)"
      For Wi-Fi:
      - 1st method:You can choose an external USB wifi dongle (I used TP-Link Archer T1U (5GHz support), TP-Link has official macOS drivers, you just need to install it
      -2nd and I think the best method:Replace your M.2 Qualcomm Card with a compatible BCM94352Zcard (you will have hand-off Bluetooth too), just install the kexts (enabled with BrcmFirmwareData.kext, BrcmPatchRAM2.kext, FakePCIID.kext, FakePCIID_Broadcom_WiFi.kext, they're all in my attached zip). You could buy this card from ebay, aliexpress, or amazon
       
      Issues:
      - None
      BIOS Settings:
      - BIOS version 1.15 (irrelevant)
      - Secure Boot: Disabled
      - Touchpad: Advanced
      - Boot mode:UEFI
      Getting ready for Installation:
      - Download the install zip (bootpack & postinstall): Click here -> acer_aspire_v591g_installfiles.zip
      Installation:
      - Create an installer with any method you know (- Mac: createinstallmedia - Windows: Transmac, Vmware, Win32diskimager)
      - Copy my Clover folder to the USB's EFI folder
      - Boot with the Installer USB
      - If you stuck in boot, reboot and in the Clover bootloader select "config_debug.cfg" -> you'll have more informations about the freeze
       
      Please open the README.rtf in my install zip for more informations about the USB Installer & Post installation!
      If you have a single RAM and getting panic at boot, then you need to edit the "config.plist" with these (SMBIOS->after "Version 1.0"):
      ->Edit "Frequency" and "Size" to match your RAM values
      <key>Version</key> <string>1.0</string> <key>Memory</key> <dict> <key>Channels</key> <integer>1</integer> <key>SlotCount</key> <integer>1</integer> <key>Modules</key> <array> <dict> <key>Slot</key> <integer>0</integer> <key>Size</key> <integer>8192</integer> <key>Frequency</key> <integer>2133</integer> <key>Type</key> <string>DDR4</string> </dict> </array> </dict> </dict>  
      PowerManagement  fix:
      Set HWPEnable=YES in Clover (already set), CPUFloor to "700", Frequency to "2300" and "3200"(Normal and Turbo, if you have i7-6700HQ version then it should be "2600", "3500") and "FrequencyVectors" from "0x0d000000" to "0x07000000" in "S/L/E/IOPlatformPluginFamily.kext/Contents/PlugIns/X86PlatformPlugin.kext/Contents/Resources/Mac-A5C67F76ED83108C.plist", MSR _xcpm_idle Patch to KernelToPatch in Clover (If you have High Sierra, change "MatchOS" to 10.13):

      <key>KernelToPatch</key> <array> <dict> <key>Comment</key> <string>MSR 0xE2 _xcpm_idle instant reboot(c) Pike R. Alpha</string> <key>Disabled</key> <false/> <key>Find</key> <data> ILniAAAADzA= </data> <key>MatchOS</key> <string>10.14</string> <key>Replace</key> <data> ILniAAAAkJA= </data> </dict> </array> Reboot, and it's 800MHz in idle state, same on Windows.
       

       
      Elan SmartTouchpad
      I only use scrolling, one-, double- & tripletap
      If you want to try other gestures go to this link for more informations, options (v4.7 beta 5) ->  DETAILS ABOUT THE SMART TOUCHPAD DRIVER FEATURES
      Fn Brightness keys not working with this, tried several things without success. With VoodoPS2Controller it's working, but you'll have no gestures (neither scrolling).
       
       
      Before updating to a new version of Mojave please update kexts (and clover if necessary) to newer versions to avoid kernel panics.
      Generate a serial number with Clover Configurator.app (open up your config.plist with CC then -> SMBIOS -> Serial Number -> Generate New)
       
      Mojave & Windows 10 Dual-Boot:
      Dual-boot clean install (on one drive), UEFI Only:
       
       Boot into your Mac installer, Create 2 partitions in GUID table (1 for Win (I used FAT32 but I think it doesn't matter what you choose), 1 for Mac),   Install Mac, boot with your USB, mount your EFI partition (use terminal or an EFI mounter app), create an EFI folder (if there is no folder), copy the CLOVER folder I attached to the EFI folder, restart,  Boot into your Win installer, Format the partition you created for Win, install.   Now, it's automatically booting into Windows. To use Clover open cmd in administrator, type:  bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.efi       5.  You're done! It will booting into Clover when you start the system, and you can select Win or Mac (or another OS if installed on a 3rd partition).
       
      Dual-boot with Windows installed first (on one drive), UEFI Only:
      If you already have Windows and you don't want to lose all your data there is a hope:
      I created a video from this restore method: [Hackintosh] Dual-Boot High Sierra & Windows - when Windows already installed - no data waste - UEFI
      You need bootable Mac Installer and a full system restore image (link is in my video's description).
      (You may see errors if your EFI partition is not 200 MB)
       Boot into your Windows, resize your partition or create one for Mac.  Boot into your Mac installer and in Disk Utility format the partition you created.  Restore from image: select your full system restore image.  When it's finished restoring you just need to restart, then boot to the system with your usb.  When you successfully booted to Mac desktop, mount your EFI partition (use terminal or an EFI mounter app), open EFI, you will see there is a Microsoft folder already (don't touch that!). Copy my CLOVER folder to the EFI folder then Restart.  Now, it's automatically booting into Windows. To use Clover open cmd in administrator, type:  bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.efi       7.  You're done! You can select your old Windows and your new macOS!
      (Only tried with Windows 8/8.1/10. I don't know Windows 7,etc.)
       
      IF YOU GETTING ERRORS DURING MAC RESTORE:
      - Make sure you have partitions in GPT
      - Windows using 100 MB EFI and will annoy the Mac restore. Don't worry, just ignore the errors.
       
      IF YOU GETTING ERRORS DURING WINDOWS INSTALLATION (could not be formatted, etc):
      - Make sure you have GPT partitions, and GPT (UEFI) installer, also disconnect all external storage drives (except the installer USB)
       
      IF YOU USED RESTORE METHOD THEN CAN'T MOUNT YOUR EFI PARTITION (No EFI partition found):
      - It's because your EFI is not 200 MB or not an "Apple" original EFI,  but do not worry, try another EFI mounter, or mount from terminal (I used EFI mounter v3: Getting errors, but you can mount and use without problem)
      - You also could "mount" the EFI from Windows:
      1st method: open cmd in administrator mode and type:
      diskpart
      list vol (Now select the "System" volume,(FAT 32) For example I select 4)
      sel vol 4
      list part(Select System type partition, for example 2)
      sel part 2
      assign letter=b(This will "mount" your EFI partition)
      Open Explorer++ or TotalCommander in administrator mode to manage EFI
      remove letter=b (This will "unmount" your EFI)
      2nd method: open cmd in administrator mode and type:
      mountvol b: /s (This will mount your EFI)
      Open Explorer++ or TotalCommander in administrator mode to manage EFI
      mountvol b: /d (This will unmount your EFI)
      Thanks to all OSXLatitude members for helping me out! (Jake Lo, Hervé, Bronxteck, black.dragon74)!
      Notes:
      2019.06.05: Updated to 10.14.5 -> no problem when/after installing
      2019.04.25: Optimized touchpad scrolling -> updated install files
      2019.03.30: Fixed USB 3.0 ports, fixed Bluetooth crashes after sleep -> updated bootpack
      2019.03.28: Updated to 10.14.4. Unexpected crashes while updating to 10.14.4 -> fixed by updating Clover to the latest (v4910) version. Bluetooth crashes appeared -> fixed by downgraded Brcm*.kexts. Updated bootpack.
      2019.02.24: Bluetooth crashes after sleep -> fixed, updated bootpack. 
      2019.02.22: Updated to 10.14.3. Fixed HDMI Audio by installing "FakePCIID_Intel_HDMI_Audio.kext" -> fixed freezing during boot. Fixed brightness levels by installing "AppleBacklightFixup.kext". Also updated bootpack & postinstall zip down in attachments.
      2019.01.21: Removed FakeSMC.kext, SMCHelper-64.efi, replaced by VirtualSMC.kext, VirtualSMC.efi because I got random freezes when booting system (kextd stall[0], (120s): 'AppleACPICPU' -> CPU is at 100%, fans are spinning fast), also updated bootpack in the attachments "acer_aspire_v591g-55tu_clover.zip"-> Freeze continued, brought back FakeSMC, deleted VirtualSMC (caused BT crashes).
      2019.01.18: HDMI Audio is fixed, I didn't do anything HDMI Audio is not fixed, sometimes it worked but most likely not. (no idea why)
      2018.12.09: Updated to 10.14.2 -> did without any complication
      2018.11.28: Fixed combo-jack garbage sound output by installing ALCPlugFix and CodecCommander.kext
      2018.11.01: Updated to 10.14.1 -> HDMI & VGA ports are gone again. -> Fixed by "AppleIntelSKLGraphicsFramebuffer.kext" rollback from 10.14.
      2018.09.28: Updated to Mojave 10.14 -> Fixed HDMI & VGA Outputs by adding "AppleGraphicsDevicePolicy.kext" patches to config.plist, HDMI audio not working
    • By cvad
      View File Bootdisk Utility
      Make bootable USB Flash Disk for MAC OS X with Latest Clover bootloader revision fast and easy by one click! under OS Windows.
      Special utility from cvad & russian MAC community for new hackintosh users.
       
      Enjoy...
       
      For more information and complete instructions please see this topic.
       
       
       
       
      Feel free to "Rate File"
      Submitter cvad Submitted 04/28/2013 Category Bootloaders  
×