Troubleshooting Sierra Boot Failures with Clover

If a Sierra installer appears in Clover but sends you back to the boot menu, the firmware has already found a bootloader. That is a different failure from a machine that never shows Clover. Reinstalling macOS to fix either symptom may waste time—or disturb a disk that was working. Find the last successful handoff first: firmware to bootloader, bootloader to macOS kernel, or kernel to the installer or desktop.

This guide covers macOS Sierra 10.12 on historically compatible PC hardware, mainly Clover-era UEFI and legacy BIOS setups. Chameleon and Chimera use different configuration files and boot paths; Clover file locations do not apply to them. Before changing firmware settings, partitions, EFI drivers, kexts, or ACPI files, make a verified backup of the installation and its EFI partition. Record the motherboard firmware version, disk layout, graphics hardware, and Clover version. Use a legitimately obtained Sierra installer, and check support for your components against the exact Sierra release. Another board’s successful installation does not establish compatibility with yours.

Locate the failing stage before editing the EFI

Have a known-good USB installer or recovery stick ready. At startup, note whether firmware lists the intended disk as a UEFI boot option, whether Clover appears, which macOS volume is selected, and the last readable line of verbose output. Photograph the screen if the text disappears quickly. A dark display after verbose output calls for different checks than a firmware message reporting no boot device.

Start with Clover’s -v boot option so you see text instead of the Apple logo. If a known-good USB boots the same installed Sierra volume, the installation itself may be fine. Compare the USB and internal EFI partitions: boot modes, config files, drivers, and kext directories. Do not copy the entire USB EFI onto the internal disk yet. It may contain temporary graphics options or a different disk driver.

When firmware cannot launch the bootloader

Match firmware mode to the disk’s boot path

A UEFI Clover installation usually starts from a FAT32 EFI System Partition on a GPT disk. Clover sits under EFI/CLOVER, with a UEFI executable at EFI/BOOT/BOOTX64.EFI or a registered firmware boot entry. Legacy BIOS Clover uses boot code and legacy boot files instead. Changing a board from legacy or CSM boot to UEFI-only does not convert the installation, and changing it back does not either. See how the known-good USB starts, then compare that path with the target disk before adjusting CSM or boot priority.

Some boards lose a boot entry after a firmware reset while leaving the EFI files intact. Check whether firmware can launch the disk’s UEFI entry or its fallback BOOTX64.EFI. If the disk is not detected at all, check the SATA connection, port, controller mode, and drive health before touching Clover. A controller mode change can make a healthy Sierra installation inaccessible, so record the original setting before testing.

Mount only the EFI partition you mean to inspect. Confirm the physical disk and partition identifiers: several drives may each have a volume named “EFI.” Copy the whole EFI directory tree separately so you can undo an edit without rebuilding the original Clover setup from memory.

Keep UEFI and legacy components separate

Clover’s UEFI drivers belong in the UEFI driver directory for the installed version; legacy BIOS setups use their own drivers and boot components. Directory names changed between Clover releases. Follow the layout of the build on the disk rather than dropping downloaded drivers into every folder, and do not mix binaries from unrelated Clover packages. If Clover stopped appearing after an update, restoring the backed-up EFI is a cleaner test than adding drivers at random.

When Clover cannot see the Sierra volume

A volume missing from the picker might point to an undetected drive, an unreadable partition, or a Clover setting that hides it. First see whether Clover shows the physical drive or any of its other partitions. Then inspect scan and hide entries in the active config.plist. A copied configuration may still hide a volume whose name has since changed.

Encryption introduces another requirement: Clover needs appropriate support to expose an encrypted macOS volume at boot. Filesystem driver needs also depend on the Clover release. Sierra normally boots from HFS+; APFS became central in later macOS versions. Adding an APFS driver is therefore a poor first move for an ordinary Sierra HFS+ detection problem. If the Sierra volume was converted or combined with another macOS installation, check its filesystem directly instead of trusting its displayed name.

Use a trusted installer or recovery environment to confirm the partition and files are readable. If Disk Utility finds filesystem errors, back up recoverable data before attempting repairs. No Clover setting can make up for a failing drive, damaged partition map, or missing macOS installation.

When the volume starts but Sierra will not reach the desktop

Capture a meaningful verbose failure

Boot once with -v and record the last lines that remain on screen. The last visible line is not necessarily the cause; the next subsystem may have failed without printing anything. An instant reset, prohibited symbol, kernel panic, and dark display each warrant different checks. If a panic names an extension, save a photograph or panic report and check that extension’s Sierra compatibility before removing it.

Temporary Clover boot options let you test without immediately rewriting the EFI. Try one at a time and record the result. Piling on flags copied from old forum posts can obscure the failure: a setting useful for one graphics card or kernel build may be wrong for another. Also confirm that Clover loads the intended config.plist, especially when its menu offers several configurations.

Check kext placement and Sierra version

If Clover injects extensions from EFI, inspect the relevant EFI/CLOVER/kexts subdirectory. A setup may use the version-specific 10.12 folder or the cross-version Other folder; do not assume every Clover release loads both in the same way. Confirm the active configuration and test a small set of kexts known to suit that setup, rather than leaving duplicate extensions in multiple locations.

A 10.12 point update can change how a previously working kext loads or behaves. An older USB installer may also carry a Clover configuration unlike the one on the internal disk. Compare versions and file locations before rebuilding caches or changing the system volume. If an extension must be replaced inside macOS instead of on the EFI, verify your backup and recovery boot path first. A bad replacement may take away the only working way in.

A driver dependency can masquerade as a bootloader fault. Clover might see a storage device, for example, only for macOS to fail when its own controller drivers initialize. By contrast, a desktop that boots through the USB stick but not the internal disk usually calls for an EFI comparison before a reinstall.

Separate display loss from a stalled kernel

If verbose text gets well into startup and the monitor goes dark, find out whether the machine keeps booting. Keyboard response, disk activity, or a reachable network service can help separate lost video from a full hang. Try another port on the same supported graphics device before altering several graphics properties. Sierra-era Intel integrated and discrete GPUs differ by generation and device ID. Some require matched framebuffer settings; a generic boot flag will not make unsupported hardware reliable.

Save the EFI before removing graphics injection settings inherited from an older OS X build. A copied SMBIOS profile, unsupported GPU, or conflicting integrated and discrete graphics setup may also affect initialization. Test each possibility separately rather than applying a bundle of patches.

Installer loops, wrong selections, and multi-disk confusion

Sierra installation has more than one restart. The next stage may appear in Clover as an installer-related entry rather than the finished system volume. If you land back at the first installer screen, check which entry Clover selected automatically before declaring the installation failed. Temporarily change an incorrect default or select the appropriate installer stage by hand. Once installation is complete, choose the finished macOS volume and confirm it starts without the USB installer.

With multiple disks, firmware can start Clover from one drive while Clover starts Sierra from another. Each drive may have an EFI partition with different files. Disconnecting unrelated drives can make a controlled test easier, provided you have accounted for their contents and backups. Otherwise, trace the selection from firmware through Clover to the target volume. Do not erase an apparently unused EFI partition; it may be the machine’s only working boot path.

A controlled repair sequence

1. Preserve the baseline. Back up user data and copy the working or partly working EFI. Record firmware settings and photograph the failure.
2. Prove a recovery route. Boot a trusted USB installer or existing recovery environment and confirm it sees the Sierra disk before editing its EFI.
3. Identify the boundary. Find the first stage that fails: firmware, Clover, volume discovery, kernel, or display initialization.
4. Change one item. Test one boot entry, driver, kext, configuration setting, or temporary boot option. Keep the previous file ready to restore.
5. Test twice. Restart, then shut down fully and cold-boot. Firmware boot entries can behave differently between the two.
6. Document the result. Note the Sierra and Clover builds, changed file, symptoms before and after, and whether boot came from USB or the internal disk.

Do not update firmware or overwrite partition boot code as a speculative first fix. Both carry wider consequences than restoring a backed-up Clover configuration, and a failed firmware change could eliminate your recovery path. Persistent ACPI or power-management faults that appear after the kernel loads belong to a different stage; the guide to CPU power management on an Intel Hackintosh covers that narrower problem.

For the final check, remove the installer USB, explicitly select the intended internal drive in firmware, and cold-boot twice. If Sierra starts only with the USB attached, mount both EFI partitions and compare the Clover executables, driver directories, config.plist files, and kext folders. Identify the difference responsible before copying a component to the internal EFI.