Contribute
Register

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

Joined
Mar 30, 2018
Messages
2
Motherboard
MSI
CPU
I5-7400
Graphics
GTX 1060
Clover is a great boot loader, and tonymacx86 has developed some great tools to get you up and running. 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:​
4. At the Shell> prompt type
Code:
bcfg boot dump
the results should look something like this:​
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.​
The code to remove an entry looks like this:
Code:
bcfg boot rm XX
where XX is the Option number. In this example, I remove Option 02 with
Code:
bcfg boot rm 02
.​
If you have a LOT of bogus entries, it is best to do just a few, and then type the command
Code:
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
Code:
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 on InsanelyMac
The bcfg command doesn't exist on the UEFI shell, what do I do?
 
Joined
Sep 17, 2012
Messages
88
Motherboard
GA-Z97X-UD3H
CPU
Intel Core i7-4770K Quad-Core
Graphics
GTX 750 TI
you have to type it in like bcfg boot dump...Then choose page up and page down to view the dump. Then go by the tutorials in 1st post.

Here is something weird. I shutdown my hack this morning, went to church, come home and whenever I rebooted a totally different version of Clover Bootloader loaded!!!! This is on my main boot drive. The rest of my other 9 HDDs do not have any EFI bootloader or Clover on them, I made sure of this. So how did a totally different version show up like that? I had previously updated my Clover Bootloader but the newer version just would send me to a panic screen, so I deleted the EFI directory and replaced with the previous on. How did the newer one get back on there is beyond me!!!
 
Joined
Dec 30, 2018
Messages
4
Motherboard
GA-Z87X-UD7-TH
CPU
Intel i7 4770K Quadcore 4x3,5Ghz 8MB L3 Turbo
Graphics
GeForce GTX 980
Mac
MacBook Pro, Mac mini
So do i understand right: For internal Data Storage i can remove the boot entries without any issue?
My Internal Backup Drive is a Time Machine Drive too, so i guess better not to remove the entrie?
And when i use remove, is it only removed or is the boot partition deleted too?

Thank u all for your great work and help.
 
Joined
Jan 29, 2012
Messages
140
Motherboard
GA-Z97-HD3
CPU
i5-4690K
Graphics
RX 580
Mac
iMac, MacBook, Mac mini
Mobile Phone
Android, iOS
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 tried this except that I deleted the PCIroot boot entries in clover shell and now if I connect a second monitor to my discrete Gigabyte AMD RX 580 GPU through the HDMI, no image appears in the second monitor (black screen). I'm connecting a Samsung UHD TV as second monitor. I renamed the CLOVER\LAUNCHER back to CLOVER\BOOT but it didn't make a different, no luck with the second screen. Does anybody know how I can fix this?
 
Joined
Oct 15, 2011
Messages
907
Motherboard
ASUS Gryphon Z87
CPU
i7-4770K
Graphics
HD 4600 & RX 580
Mac
MacBook Pro
Classic Mac
Apple
Is there something like EasyUEFI available for macOS ? Even a cli app would be ok
 
Joined
Oct 15, 2011
Messages
907
Motherboard
ASUS Gryphon Z87
CPU
i7-4770K
Graphics
HD 4600 & RX 580
Mac
MacBook Pro
Classic Mac
Apple
I found a iso which can be used to make a usb stick bootable with windows pe inclusive EasyUEFI :)

No longer Windows required to easily edit the UEFI boot menu.
 
Joined
Jul 26, 2018
Messages
752
Motherboard
Asus Z370-A Prime II
CPU
i7-8700
Graphics
RX 580
Mac
MacBook Pro
Mobile Phone
iOS
@Anachronaut Just wanted to say thanks for this quick guide. I had tons of stuff in there. I ended up updating my bios either way but I liked the learning process.
 
Joined
Oct 9, 2011
Messages
44
Motherboard
Gigabyte GA-Z170X-Gaming-5
CPU
i7 6700
Graphics
GTX 970
Hi all, I have an emergency :( I cleaned it using this method one year ago and I tried it again but everything went wrong.

I have removed one registry that says DevPath BBS (UEFI Samsung Evo 960) then now I can't see Clover anymore or boot from this drive (SSD nvme). It is like it doesn't exists

I didn't delete anything called HD(1, etc) or anything that says HD, only PCIroot and BBS stuffs.

I have boot from emergency USB and I have tried to install Clover again on that drive (ESP) but it fails... Even if I install on root (not ESP) this drive won't boot anymore. If I go to BIOS it says "Windows UEFI (Samsung EVO 960)" while it should say "Clover UEFI (Samsung EVO 960)".

I guess I could start formating totally from by emergency boot and try to install again everything from scratch, but I would like to know what happened really. Could you help to understand what happened here? Is there any method to recover UEFI registry like I had or at least, re-install Clover at ESP (I guess this would fix this).

Thanks a lot for your advice and help,
 
Joined
Apr 5, 2012
Messages
115
Motherboard
MSI Z270 Gaming Pro Carbon
CPU
i5-7600
Graphics
RX 580
Mobile Phone
Android
Despite being the one that started this thread, I am no expert on this. I would try resetting the CMOS on the board. If you decide to do this, make sure that your check your UEFI settings so that you can change them back manually after the CMOS reset.
 
Joined
Oct 9, 2011
Messages
44
Motherboard
Gigabyte GA-Z170X-Gaming-5
CPU
i7 6700
Graphics
GTX 970
Hi all, I have an emergency :( I cleaned it using this method one year ago and I tried it again but everything went wrong.

I have removed one registry that says DevPath BBS (UEFI Samsung Evo 960) then now I can't see Clover anymore or boot from this drive (SSD nvme). It is like it doesn't exists

I didn't delete anything called HD(1, etc) or anything that says HD, only PCIroot and BBS stuffs.

I have boot from emergency USB and I have tried to install Clover again on that drive (ESP) but it fails... Even if I install on root (not ESP) this drive won't boot anymore. If I go to BIOS it says "Windows UEFI (Samsung EVO 960)" while it should say "Clover UEFI (Samsung EVO 960)".

I guess I could start formating totally from by emergency boot and try to install again everything from scratch, but I would like to know what happened really. Could you help to understand what happened here? Is there any method to recover UEFI registry like I had or at least, re-install Clover at ESP (I guess this would fix this).

Thanks a lot for your advice and help,
Despite being the one that started this thread, I am no expert on this. I would try resetting the CMOS on the board. If you decide to do this, make sure that your check your UEFI settings so that you can change them back manually after the CMOS reset.
Thank you for replying me... I have solved it anyway.

The problem was on EFI that was broken due my Clover terminal deletion (by my fault). I mean that deleting the wrong registry (BBS in my case) may break your EFI boot!

The solution was to install again CLOVER, but this is a problem if you don't have another bootable Mac USB flashdrive or rescue partition. I had, apart of this, another extra problem because CLOVER failed to install to ESP partition... The workaround is very simply. Just mount that EFI partition manually (I did it using Clover configurator), then I tried to install CLOVER again on that ESP and it worked... Finally, muy BIOS / UEFI detected it again and showed me that option for boot: UEFI: Samsung 960 EVO...
 
Top