[GUIDE] Remove extra Clover BIOS boot entries & prevent further problems

[jrhjrhjim]

Not really! One thing to watch out for is if you use iMac 17,1 SMBIOS (best for skylake), you need to boot with nv_disable=1 and run this:
https://www.tonymacx86.com/threads/...-imac-15-or-imac-17-system-definition.183113/

and then nvidia graphics should work as expected

weezul--the thread you referred me to great, but it also referred to another that deals with GPU injection. Do I also need to do that?
P.S. Are do still able to restart/re-boot without creating the extra boot entries? Thank you--Jim

 

[weezul]

weezul--the thread you referred me to great, but it also referred to another that deals with GPU injection. Do I also need to do that?
P.S. Are do still able to restart/re-boot without creating the extra boot entries? Thank you--Jim

I have a gtx 750ti so I just booted with nv_disable, installed nvidia drivers, ran the patch and rebooted. On reboot run with nvda_drv=1 or there's a newer NvidiaWeb. Not sure which works but I had both on. Been a couple of days and still no multiple entries. Also had to disable SIP to run that patch. Can't remember the command but it's a clover setting if you Google it it'll come right up.

 

[herrschultzz]

I have solved the problem of multiple entries, but now clover, does not start Sierra automatically.
I have no more timeout, so i have to select manually the icon of mac os and press Enter.
Any help?
Thanks!

If you haven't fixed this yet, I fixed it by re-running Multibeast and only selecting the Clover EUFI bootloader, then hit Build. You can adjust the timeout value in the config.plist file by editing it with TextEdit - Edit/Find/timeout and change the value to however many seconds you want, I think the default value is 3.

 

[herrschultzz]

THIS WORKS (If you have Windows installed as well on a different drive):
In OSX:
1. Use EFI Mounter (download from Tonymacx86 downloads section) utility to open EFI and go to the BOOT folder.
2. Rename BOOT folder to LAUNCHER
3. Reboot to Windows
In Windows:
1. Download and use EasyUEFI utility to delete any extra boot options.
2. Use EasyUEFI to add a new boot entry, select other OS, name it what you want (I just called it El Capitan) so you can identify it when you boot, and click Browse and go through the file directory \EFI\LAUNCHER\BOOTX64.efi
3. Done
Reboot to OSX then restart several times and make sure you aren't getting extra boot options

I struggled with this problem for a few days and found these instructions above to be the perfect, easiest solution to the multiple BIOS entries problem.

If you have a board with Thunderbolt capabilities like mine; Z170X-UD5 TH then you already need to have a Windows hard drive ready in order to get the Thunderbolt / USB 3.1 ports activated by downloading and installing the Gigabyte Thunderbolt drivers for Windows. You don't need to do this for Thunderbolt v1 but for v2, v3 or USB 3.1 you do.

The instructions above absolutely work, however by renaming the Boot folder I suspect you might have to rename it back to Boot if you do any Clover or OS X upgrades as I found that unsuccessfully using other techniques to solve the multiple entries issue and deleting or renaming the folder without updating the bootx64.efi folder created a no-boot situation.

I did all of these tests with a cloned copy of my good Sierra install, therefore I was able to recover when I made this type of mistake. With a working gold version you can boot to it with the clone as an extra non-boot drive, call up the EFI partition and correct the renaming of the Boot folder quite easily if necessary.

 

[UtterDisbelief]

A few things to note:

Going into my BIOS there was a very obvious pause - around 5 seconds - before the boot section window would come up. Clearly it was scanning the boot options. This seemed to be pointing-up a potential problem so I booted into the Clover Shell to check status. It's been a while since I last did it.

I had 111 entries in there. 1 for my SSD, 1 for my data HD and 1 for my DVD.

To clear them I used the #1 post of this guide BUT with so many the screen just scrolls past way too fast. The command-line option to pause at screen-break is "-b"

All three of my actual drives were in the last three slots - 6D, 6E and 6F, so I started to delete from '00' expecting I'd have to repeat some 108 times to get to my drives. No. The order is clearly not as per the screen enumeration because they disappeared from the list early on before I'd noticed. So I carried on and deleted everything. Nothing to lose now.

Once complete, booted into BIOS again, all was back to normal. Just my three drives. Booted fully using F12 to choose boot device just in case but still all was fine. Here I am.

The help guide for the shell (just type "help -b" at the prompt, explains that the boot entries are stored in NV Ram, so I guess this problem is with the fake NVR Hackintoshes have? I'm no expert but wonder if this can be addressed?

I'm pretty sure I've booted my Hack' more than 112 times so guess the BIOS or NVR can only hold so much.

We do need a permanent fix though. It's an invisible problem that doesn't actually seem to affect the running of a Hack but could potentially cause a big problem somewhere further down the line.

 

[wstrohm]

Unfortunately for me, I updated my motherboard's BIOS version from F4 to F20 in hopes that the multi boot-entries problem would go away. Now booting won't go past the Apple logo (no progress bar) AND F20 prohibits re-flashing to an earlier BIOS firmware version. Now I have a beautiful brick that can enter the new pretty BIOS but won't boot at all. Great if you like continuous restarts ad nauseam.

 

[eledu71]

A few things to note:

Going into my BIOS there was a very obvious pause - around 5 seconds - before the boot section window would come up. Clearly it was scanning the boot options. This seemed to be pointing-up a potential problem so I booted into the Clover Shell to check status. It's been a while since I last did it.

I had 111 entries in there. 1 for my SSD, 1 for my data HD and 1 for my DVD.

To clear them I used the #1 post of this guide BUT with so many the screen just scrolls past way too fast. The command-line option to pause at screen-break is "-b"

All three of my actual drives were in the last three slots - 6D, 6E and 6F, so I started to delete from '00' expecting I'd have to repeat some 108 times to get to my drives. No. The order is clearly not as per the screen enumeration because they disappeared from the list early on before I'd noticed. So I carried on and deleted everything. Nothing to lose now.

Once complete, booted into BIOS again, all was back to normal. Just my three drives. Booted fully using F12 to choose boot device just in case but still all was fine. Here I am.

The help guide for the shell (just type "help -b" at the prompt, explains that the boot entries are stored in NV Ram, so I guess this problem is with the fake NVR Hackintoshes have? I'm no expert but wonder if this can be addressed?

I'm pretty sure I've booted my Hack' more than 112 times so guess the BIOS or NVR can only hold so much.

We do need a permanent fix though. It's an invisible problem that doesn't actually seem to affect the running of a Hack but could potentially cause a big problem somewhere further down the line.

So, after all the work to get rid of the entries, they keep appearing?
TNX!

 

[eledu71]

Unfortunately for me, I updated my motherboard's BIOS version from F4 to F20 in hopes that the multi-boot entries problem would go away. Now booting won't go past the Apple logo ( no progress bar) AND F20 prohibits re-flashing to an earlier BIOS firmware version. Now I have a beautiful brick that can enter the new pretty BIOS but won't boot at all. Great if you like continuous restarts ad nauseam.

OH MAN! Somebody has to make a BIG warn sign about this!

 

[herrschultzz]

A few things to note:

Going into my BIOS there was a very obvious pause - around 5 seconds - before the boot section window would come up. Clearly it was scanning the boot options. This seemed to be pointing-up a potential problem so I booted into the Clover Shell to check status. It's been a while since I last did it.

I had 111 entries in there. 1 for my SSD, 1 for my data HD and 1 for my DVD.

To clear them I used the #1 post of this guide BUT with so many the screen just scrolls past way too fast. The command-line option to pause at screen-break is "-b"

All three of my actual drives were in the last three slots - 6D, 6E and 6F, so I started to delete from '00' expecting I'd have to repeat some 108 times to get to my drives. No. The order is clearly not as per the screen enumeration because they disappeared from the list early on before I'd noticed. So I carried on and deleted everything. Nothing to lose now.

Once complete, booted into BIOS again, all was back to normal. Just my three drives. Booted fully using F12 to choose boot device just in case but still all was fine. Here I am.

The help guide for the shell (just type "help -b" at the prompt, explains that the boot entries are stored in NV Ram, so I guess this problem is with the fake NVR Hackintoshes have? I'm no expert but wonder if this can be addressed?

I'm pretty sure I've booted my Hack' more than 112 times so guess the BIOS or NVR can only hold so much.

We do need a permanent fix though. It's an invisible problem that doesn't actually seem to affect the running of a Hack but could potentially cause a big problem somewhere further down the line.

I think the Windows UEFI solution is so far the only one that I've found completely eliminates future boot entries in BIOS.
It does require having a Windows 8, or 10 installed HD or SSD disk around, but it's fairly easy to follow the guide I've quoted from earlier - thread #121. It's my experience that just deleting the entries in Clover EFI Shell does nothing to prevent them from reappearing. Others in this long thread report success just using the bcfg boot dump method and edits to the config.plist, but none of those methods held permanent fixes for me.

The Windows EasyUEFI method does however seem to create one problem which I'm still struggling to remedy which is that once you rename your BOOT folder in the EFI partition to LAUNCHER and save it in Windows EasyUEFI as a new boot option, then the cloned drives (backup drives) won't boot any longer, even when you change the priority in BIOS to their partition, they just don't boot any longer. So I'm not sure what gets written to where in the Windows scenario, but it does affect the ability to boot from a different boot drive - at least in my experience. I've tried copying the EFI from the hero boot drive to the EFI of a clone, and copied the original BOOT folder (which I did save before doing the UEFI routine) where the BOOT folder is an original - but nothing so far allows the cloned backups to boot completely, they hang on the progress bar below the Apple logo. This happens even when I have done the Windows UEFI routine on a boot drive - it boots immediately afterwards, but then won't boot once I do it to another drive, as in working with a clone to make sure it works prior to doing the routine on your hero (permanent) drive - even after changing the default boot #1 option in BIOS to it. Still stumped by this, but perhaps someone will chime in with a solution of sorts.

If having a bootable backup is not an issue, then the Windows UEFI is the best permanent solution that I've gotten to work to keep multiple BIOS entries from appearing.

 

[wstrohm]

OH MAN! Somebody has to make a BIG warn sign about this!

OK, I'll post a new thread. Thanks for reading!