[Solved] UEFI clover boot option gone after BIOS update

[alexjibcam]

Hi there, For the life of me i cannot get this to work. Ive followed all your steps and I just keep getting 'bcfg: Cannot open file'.

I definitely have the correct directory of FS2 and my location to my directory has been double checks with EFI mounter and is the same as OP: FS2:\EFI\CLOVER\CLOVERX64.EFI

Any ideas on anything I may have missed?

Thanks.

 

[alexjibcam]

Hi there, For the life of me i cannot get this to work. Ive followed all your steps and I just keep getting 'bcfg: Cannot open file'.

I definitely have the correct directory of FS2 and my location to my directory has been double checks with EFI mounter and is the same as OP: FS2:\EFI\CLOVER\CLOVERX64.EFI

Any ideas on anything I may have missed?

Thanks.

This is a more detailed post on the issue which solved my problem:

[Guide] How to keep Clover working when installing Windows and Linux

A very common issue when multibooting macOS/OS X with Windows and Linux is that after installing the latter the computer will only boot to them. The reason for this is that Clover does not automatically add itself to the UEFI firmware boot menu that is accessible by pressing F12 or another...

www.tonymacx86.com

 

[AndrezinhoCosta]

Tracked down a solution that didn't require new apps - and this worked for me.

Pre - get your system booted up off the USB and mount the system EFI drive (not the USB EFI drive) - check your directories and copy down the path to the \CLOVER\CLOVERX64.EFI file (I noticed this differs some amongst varying install procedures on the net). Also, doesn't hurt to open Terminal and run "disk util" - note the /dev/disk# location of the drive that has the EFI installed in it. Now, restart and proceed.

• Boot into clover off of the USB
• Start up the Clover EFI shell
• Pull the USB (saves confusion in the next step)
• Type "map" (no quotes)
• Look at the drives and apply some thinking about which one is the drive where your Clover EFI drive is - the drive# from disk util will help if you have several drives/partitions showing up. Once you've got it, note the drive - e.g. mine was "FS2"
• Type "bcfg boot dump" (no quotes)
• You'll see each boot entry proceeded with a number. For the love of Pete, don't use any of those - determine the next number up. My highest was 03, so I used 04 in the next step.
• Type the following to create the boot entry:
  bcfg boot add 04 FS2:\EFI\CLOVER\CLOVERX64.EFI CloverUEFI
• In the above step, the path is helped out by having checked my mounted EFI drive on my system. The last part, "CloverUEFI" above is how the boot entry will appear in BIOS - name this as you will.
• Type "bcfg boot dump" again to be sure your new entry made it.
• Exit, shut down, pull the USB if you didn't already.
• Hold down DEL to open BIOS settings - and in my case - CloverUEFI was in the Boot options. I set it as primary, and everything was back to normal with no more need to use the USB.

Can't find ':' in my keyboard. I don't know if I laugh or cry...
Ok! I found it and got do the procedure!

 

[AndrezinhoCosta]

Sorry, but I don't know what to do again...
Got do all the steps, and all HD's are back again in my BIOS.
But there's no UEFI and I can't access no one of them to install the MacOs...
What am I doing wrong?

 

[NorthAmTransAm]

Hello all. I was about to start Shell procedure to get my boot entries sorted when I noticed my disk3 (OS) doesn't have an EFI Partition. Instead it's under dev/disk1 below. Is that normal for this or should it be under dev/disk/3 like the others?

/dev/disk0 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         1.0 TB     disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk2         1.0 TB     disk0s2

/dev/disk1 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         256.1 GB   disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                 Apple_APFS Container disk3         255.9 GB   disk1s2

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +1.0 TB     disk2
                                 Physical Store disk0s2
   1:                APFS Volume Session                 597.6 GB   disk2s1

/dev/disk3 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +255.9 GB   disk3
                                 Physical Store disk1s2
   1:                APFS Volume Mojave                  220.5 GB   disk3s1
   2:                APFS Volume Preboot                 46.3 MB    disk3s2
   3:                APFS Volume Recovery                510.3 MB   disk3s3
   4:                APFS Volume VM                      2.1 GB     disk3s4

/dev/disk7 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk7
   1:                        EFI EFI                     209.7 MB   disk7s1
   2:                  Apple_HFS Olson Fam               999.9 GB   disk7s2

/dev/disk8 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *4.0 TB     disk8
   1:                        EFI EFI                     209.7 MB   disk8s1
   2:                  Apple_HFS Gerard Way              4.0 TB     disk8s2

 

[NorthAmTransAm]

Hello all. I was about to start Shell procedure to get my boot entries sorted when I noticed my disk3 (OS) doesn't have an EFI Partition. Instead it's under dev/disk1 below. Is that normal for this or should it be under dev/disk/3 like the others?

/dev/disk0 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         1.0 TB     disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk2         1.0 TB     disk0s2

/dev/disk1 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         256.1 GB   disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                 Apple_APFS Container disk3         255.9 GB   disk1s2

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +1.0 TB     disk2
                                 Physical Store disk0s2
   1:                APFS Volume Session                 597.6 GB   disk2s1

/dev/disk3 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +255.9 GB   disk3
                                 Physical Store disk1s2
   1:                APFS Volume Mojave                  220.5 GB   disk3s1
   2:                APFS Volume Preboot                 46.3 MB    disk3s2
   3:                APFS Volume Recovery                510.3 MB   disk3s3
   4:                APFS Volume VM                      2.1 GB     disk3s4

/dev/disk7 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk7
   1:                        EFI EFI                     209.7 MB   disk7s1
   2:                  Apple_HFS Olson Fam               999.9 GB   disk7s2

/dev/disk8 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *4.0 TB     disk8
   1:                        EFI EFI                     209.7 MB   disk8s1
   2:                  Apple_HFS Gerard Way              4.0 TB     disk8s2

Ah, I should have read elsewhere first. This is normal.

 

[pedrosilva13]

Hey! When i type ``map``on the sheel it does nothing, why?

 

[woozaer]

Another hackintosh user saved by this topic!
In my particular situation where my computer is full of drives, (more than 10 bootable units!) when I typed "bcfg boot dump" I got drive 1,2,3,...,1A,1B,1C <-- with 1C last one

where 1A was 10, 1B was eleven and so on

So to add one more to the list I had to type "bcfg boot add 1D SF.."

 

[ugokind]

Tracked down a solution that didn't require new apps - and this worked for me.

Pre - get your system booted up off the USB and mount the system EFI drive (not the USB EFI drive) - check your directories and copy down the path to the \CLOVER\CLOVERX64.EFI file (I noticed this differs some amongst varying install procedures on the net). Also, doesn't hurt to open Terminal and run "disk util" - note the /dev/disk# location of the drive that has the EFI installed in it. Now, restart and proceed.

• Boot into clover off of the USB
• Start up the Clover EFI shell
• Pull the USB (saves confusion in the next step)
• Type "map" (no quotes)
• Look at the drives and apply some thinking about which one is the drive where your Clover EFI drive is - the drive# from disk util will help if you have several drives/partitions showing up. Once you've got it, note the drive - e.g. mine was "FS2"
• Type "bcfg boot dump" (no quotes)
• You'll see each boot entry proceeded with a number. For the love of Pete, don't use any of those - determine the next number up. My highest was 03, so I used 04 in the next step.
• Type the following to create the boot entry:
  bcfg boot add 04 FS2:\EFI\CLOVER\CLOVERX64.EFI CloverUEFI
• In the above step, the path is helped out by having checked my mounted EFI drive on my system. The last part, "CloverUEFI" above is how the boot entry will appear in BIOS - name this as you will.
• Type "bcfg boot dump" again to be sure your new entry made it.
• Exit, shut down, pull the USB if you didn't already.
• Hold down DEL to open BIOS settings - and in my case - CloverUEFI was in the Boot options. I set it as primary, and everything was back to normal with no more need to use the USB.

hi. I'm trying to follow your guide but the shell give me errors it cant add any entry. I've tried all the FS and BLK from 01 to 05

 

[goober296]

Tracked down a solution that didn't require new apps - and this worked for me.

Pre - get your system booted up off the USB and mount the system EFI drive (not the USB EFI drive) - check your directories and copy down the path to the \CLOVER\CLOVERX64.EFI file (I noticed this differs some amongst varying install procedures on the net). Also, doesn't hurt to open Terminal and run "disk util" - note the /dev/disk# location of the drive that has the EFI installed in it. Now, restart and proceed.

• Boot into clover off of the USB
• Start up the Clover EFI shell
• Pull the USB (saves confusion in the next step)
• Type "map" (no quotes)
• Look at the drives and apply some thinking about which one is the drive where your Clover EFI drive is - the drive# from disk util will help if you have several drives/partitions showing up. Once you've got it, note the drive - e.g. mine was "FS2"
• Type "bcfg boot dump" (no quotes)
• You'll see each boot entry proceeded with a number. For the love of Pete, don't use any of those - determine the next number up. My highest was 03, so I used 04 in the next step.
• Type the following to create the boot entry:
  bcfg boot add 04 FS2:\EFI\CLOVER\CLOVERX64.EFI CloverUEFI
• In the above step, the path is helped out by having checked my mounted EFI drive on my system. The last part, "CloverUEFI" above is how the boot entry will appear in BIOS - name this as you will.
• Type "bcfg boot dump" again to be sure your new entry made it.
• Exit, shut down, pull the USB if you didn't already.
• Hold down DEL to open BIOS settings - and in my case - CloverUEFI was in the Boot options. I set it as primary, and everything was back to normal with no more need to use the USB.

Thank You!! Had an Asrock z77m that I finally got working properly because of your tip! Well done my friend!!