Using the installer

What was the installer made for? To install the program! Why do all the work manually when it can be done by the installer more accurately. The only requirement is having Mac OS X installed. One variant is to boot the installer DVD with another boot loader and to start the installer. Depending on the OS language, the installer will be presented in your preferred language, may it be Russian, English or Chinese. Currently the installer was translated to 17 languages, including Indonesian - who knows, someone might need it. Following instructions are for the English language.

Press Continue, read the information, Continue again. Now you can choose what you install, where and why.

Change Install Location... - Choose where you install Clover

Customize on the previous page - Boot loader options

A detailed description is available in the lower text field when clicking on an option.

Install for UEFI motherboards - This option disables the installation of boot files. They seem to bother someone greatly.

Install Clover in the ESP - Best option when such an EFI partition is available (GPT partitioned drive). This partition is not seen by the installer, you need to point it to another partition on the same drive, which contains the ESP. Let's assume that Mac OS X is on this partition and we will install RC scripts and the preference panel.

Bootloader - This is valid for BIOS booting (option A) when CloverEFI is used or for UEFI booting (option B) * Don't update MBR and PBR sectors - Do not update these sectors because they either already exist or are not needed for option B * Install boot0af in MBR - Boot utilising boot0af, i.e. searching an active partition. The previously selected partition will be flagged as active. * Install boot0ss in MBR - Boot utilising boot0ss, i.e. searching an HFS+ partition, even if it is not active. No active flag will be set. Useful for dual-boot configurations with Windows where Windows needs to be on an active partition.

User alternative booting PBR - As written in the section What is what, the PBR sector may be set up to pause for keyboard input 1-9. This option enables the pause.

CloverEFI - Choose the loader's bit depth: 32-bit or 64-bit. Additionally there is a BiosBlockIO option. This is a CloverEFI-64 variant with a special boot7 file targeted for computers with a non-standard SATA controller. This driver operates through the BIOS and usually works with any controller (as the BIOS needs to support them!). However it not always works, for instance with the Dell Inspiron 1525.

Drivers64UEFI - The specific drivers are described in section What is what

Install RC scripts on target volume - These are the scripts rc.local and rc.shutdown.local that are executed while starting and while exiting OS X. They play a necessary role in the concept of Clover. You may not install them if you have no plans to use Clover (what are you doing here anyway then?).

Install all RC scripts on all other bootable OSX volumes - For the case when multiple Mac OS X systems are installed. The installer will automatically determine them. Windows and Linux systems, for instance, will remain unaffected.

You may skip the script installation if you know what you are doing.

Optional RC Scripts - Install additional RC scripts * disable sleep proxy client - ???

>> missing description <<

Install Clover Preference Pane - This is a preference panel that helps with updating Clover, with choosing a theme and with setting NVRAM variables.

>> missing pref panel screenshot <<

Manual installation

It is useful in two cases: ~~when catching fleas or having diarrhea.~~ First of all you may know what you are doing and want to control every step, not trusting the installer (you should!), and second for installing from another OS where running the installer is not possible.


It is really not recommended to follow the steps in this section if you are not familiar with the terminal.

Installation on an HFS+ partition

The installation will be made on an HFS+ partition located on an MBR or hybrid GPT/MBR partitioned disk. Why MBR? This is a very common situation, when a disk already contains information, which must not be lost. In this case it is only possible to setup a new boot loader.

MBR sector installation
cd BootSectors
sudo fdisk440 -f boot0 -u -y /dev/rdisk0

fdisk440 - special version of the fdisk utility, corrected to use just 440 byte of the boot sector. Useful for compatibility with Windows that is not granted by Apple's version

boot0 - file, which is described in What is what

rdisk0 - physical devices, which is used for installation. Verify that it really has the numbering 0

These files are shipped with Clover.

PBR sector installation
sudo dd if=boot1h2 of=/dev/rdisk0s9

boot1h2 - PBR sector file for HFS+ file systems. Supports big boot files and the selection of loaders with number keys. More in What is what

rdisk0s9 - Ninth partition on the chosen device. Why ninth? To avoid corruption caused by fools who just execute the written commands. Such a partition probably will not exist. Needs to be adjusted to a correct digit, for example 1 to match the first partition.

After having written MBR & PBR sectors on the chosen device & partition, you should mark the partition as active:

fdisk440 -e /dev/rdisk0
>f 9

The 9 in the second line - again - represents the partition number. Make a conclusion.

Now you can copy the boot file and the EFI directory to this partition.

Installation on a FAT32 partition

Unlike the previous method there is a small catch. The PBR sector must contain the partition's geometry. This data is written when partitioning the drive and losing it will have consequences. The sector installation method gets more complicated:

dd if=/dev/rdisk1s9 count=1 bs=512 of=origbs
cp boot1f32alt newbs
dd if=origbs of=newbs skip=3 seek=3 bs=1 count=87 conv=notrunc
dd if=newbs of=/dev/rdisk1s9 count=1 bs=512

boot1f32alt - Mentioned in section What is what. Sector for installation on a FAT32 partition. Does not work with FAT16, keep this in mind!

rdisk1s9 - Again the ninth partition on the first device. Replace with your own digits.

The rest of the letters and digits in the command was discussed and is not subject to change. The rest of the commands is similar to the installation on an HFS+ partition.


Linux also has a terminal and the commands are nearly identical. The installation, however, is probably only possible on a FAT32 partition. These are the differences:

  • Instead of rdisk1 use sdb or another definition your Linux version may use
  • Instead of fdisk440 for MBR setup use dd
dd if=/dev/sdb count=1 bs=512 of=origMBR
cp origMBR newMBR
dd if=boot0 of=newMBR bs=1 count=440 conv=notrunc
dd if=newMBR of=/dev/sdb count=1 bs=512


In Windows it also only makes sense to install the boot loader on a FAT32 partitioned USB flash drive. Start the script:

makeusb.bat E:

E: - The letter of your USB flash drive

Having multiple partitions is not offered, it is Windows after all!

All files required by the script are bundled with Clover. However, you will need to unpack the installer first or obtain the files from the repository at edk2/Clover/CloverPackage/CloverV2/BootSectors. After executing the script you need to remove the flash drive and insert it again. Afterwards copy the boot file and the EFI directory.

A better option is to use BootDiskUtility.exe by cVaD that will help you to format a flash drive on Windows.