This repo is actually just documentation about How to install Clover EFI Bootloader using manual methods under Linux (eg. Ubuntu). Clover binary used on this repo is similar to Official GitHub here; except additional configs, kexts, etc.
But if you prefer using simpler methods with automated (or guided) steps, I guess you use this clover-linux-installer script by m13253. DWYOR..!!! (Do With Your Own Risk).
What is Clover?
Clover is one of bootloaders developed by Slice, Apianti, BlackOSX, Dmazar, Blusseau, and other devs with great community for booting OS X, Windows and Linux on Mac or PC with UEFI / BIOS firmware.
Some of Clover features are:
- Supports for booting OS X, Windows and Linux (Android x86 as well)
- Running on Legacy BIOS (MBR, GPT) or UEFI firmware (GPT only)
- Customizable GUI including themes, icons, fonts, background images, animations, and mouse pointers.
- ... and much more. Here's for details.
However, following this method you have to meet conditions below:
- Desktop PC or Laptop with Legacy or UEFI (GPT partition scheme is recommended)
- Pre-installed Ubuntu Linux (and it's flavours), Debian or Live Mode
- Basic knowledge about BIOS (Firmware) configuration, partition scheme, OS Installation
- Make sure that your PC is able to boot Clover. For testing purpose; create USB Clover with this Tool via Windows. Then boot from it
- Make a Backup of "Internal EFI Partition" on a safe place.
Before You Begin
Clone or Download whole repo: $
git clone https://github.com/badruzeus/CloverEFI-4MU
My Clover Themes collection: $
git clone https://github.com/badruzeus/MyCloverThemes(Optional). Go to docs for Theming how to
Follow provided "Video Tutorial" below, or skip to "Manuall Installation" methods on next steps:
If you're not sure; install it to EFI Partition on USB FlashDisk with GPT scheme. Using gParted create 200MB partition, Manage Flags as: boot,esp.
Manual Installation on GUID Partition Table (GPT)
Assummed "Target_Disk" is /dev/sda (Whole Disk) and "Target_Partition" is /dev/sda1 (EFI System Partition).
Check with Terminal:
$ sudo blkid or
sudo fdisk -l
Set /dev/sda1 as Primary Boot Record / PBR (for Legacy and GPT)
sudo dd if="/dev/sda1" bs=512 count=1 >origPBR
sudo dd if="/dev/sda" bs=512 count=1 >origMBR
cp boot1f32 newPBR
cp origMBR newMBR
sudo dd if=newPBR of="/dev/sda1" bs=512 count=1
sudo dd if=newMBR of="/dev/sda" bs=512 count=1 conv=nocreat,notrunc
sudo dd if=origPBR of=newPBR skip=3 seek=3 bs=1 count=87 conv=notrunc
sudo dd if=boot0af of=newMBR bs=440 count=1 conv=notrunc
Placing Clover on EFI System Partition (ESP)
(Please note that
\EFI\BOOTdir is not always empty, some linux distros maybe placing
grub, kernel, etc.here. If this is your case, just copy
BOOTX64.efifile, not replacing a whole dir).
a. Option 1 via Command Line // Mounting EFI System Partition
sudo mount -t vfat /dev/sda1 ~/esp
// Copying Clover required files
sudo cp boot ~/esp
sudo cp -r EFI/BOOT ~/esp/EFI
sudo cp -r EFI/CLOVER ~/esp/EFI
b. Option 2 via File Manager (GUI)
- Mount ESP as Option (1) first
- Terminal: $
sudo [FileManager]// File manager could be nautilus, pcmanfm, thunar, etc.
- Manually copy-paste required files as point (a), be careful!
- Terminal: $
sudo umount ~/esp(if all have done).
Bugs & Troubleshooting
Press "F1" for Clover Help (Shortcut keys, Functions, etc.)
Depends on your UEFI firmware, for adding CLOVER as "New Boot Entry" is usually:
fsX:\efi\clover\cloverx64.efi// (fsX = fs0, fs1, fs2, etc), or just
Phoenix or InsydeH2O maybe not including "Boot" Entry Option on it's firmware (BIOS). On this case, you need manually adding Entry via UEFI Shell. For example adding Clover Entry located on FS0 (could be FS1, FS2 etc. depends on ESP):
bcfg boot dump
02is last Boot Entry, add Clover on
bcfg boot add 03 FS0:\EFI\CLOVER\CLOVERX64.efi "Clover EFI Bootloader"
// OFC, you could add another entries eg. Windows Boot Manager, Linux Grub2, etc. on 04, 05..
If Clover is not set as 1st boot order, you need pressing StartUp key (could be F12, Esc, etc.) and manually select it once computer powered on. Most AMI Aptio BIOS has "Entry Override" option.
If you're unable to "Launch EFI Shell" from BIOS, place "shellx64.efi or SHELLX64.EFI" on your ESP root (not EFI dir).
Some old AMI Aptio firmwares (eg. v2.00) need this.
Still having trouble accessing Shell via Firmware? Install Clover to Bootable USB FlashDisk using BDUtility.exe under Windows then boot from it. Run UEFI Shell provided by Clover.