\EFI\Microsoft\Boot\bootmgfw.efi
instead of \EFI\BOOT\BOOTX64.EFI
, and this to lock the computer (somewhat) to M#x27;s botnet OS. To fix that you can:bootmgfw.efi
in EFI > Microsoft > Boot
to anything else than bootmgfw.efi
(like bootmgfww.efi or something). Remember that naming. Now, the computer will not find bootmgfw.efi
and look for bootx64.efi
or whatever is the next boot option.CLOVERX64.EFI
to bootmgfw.efi
then rename M#x27;s bootmgfw.efi
to anything else, then copy the fake bootmgfw.efi
to EFI > Microsoft > Boot
. On some laptops it is needed to force load anything named bootmgfw.efi
to boot anything.map
to see itbcfg boot dump
it will output your actual boot entries. bcfg boot add XX FSX:\EFI\CLOVER\CLOVERX64.EFI "CloverBoot"
, where FSX
is your macOS/OSX EFI, XX
is the new entry and "CloverBoot"
is the name of the entry, can be changed to anything as long as it's between " "
bcfg
entry that points to /BOOT/BOOTX64.EFI
with bcfg boot rm XX
where XX
is the number identifier seen when you do bcfg boot dump
efibootmgr
guide too, most linux users know how to use google tho)bootmgfw.efi
will be replaced by a new one, or if you renamed it, a new one will be copied over, so you will need to rename/replace that file.Custom Entry
to clover's config.plist
as shown here:bootmgfw.efi
renamed to bootmgfww.efi
\EFI\grub\grubx64.efi
to load GRUB2 or look where lilo
file is located and add it too.