Jump to content
frankiee

[Guide] How to add additional UEFI apps to the Clover menu (updated)

15 posts in this topic

Recommended Posts

Hi there, time for my first guide after asking so many things ;)

 

Updated for newer Clover versions and with additional instructions for more apps: gdisk and RU.

 

So what may be overlooked sometimes in the whole boot loader discussion is the ability of UEFI to do more than just loading an OS. This is why I see ".efi" files as "apps" because in fact they just are, built on a special kind of API: UEFI. So, you can actually do stuff like editing, diagnosing, testing certain stuff at the lowest possible system level without booting to any OS.

 

DISCLAIMER: Use this guide at your own risk! For educational purposes only! Should do not any harm, but remember you are dealing with rather low level stuff. But at least for me everything went flawless.

 

Prerequisites:

  • Working clover installation
  • Clover Configurator or some app to edit the config.plist

 

1) Memtest

 

This is how to install the UEFI version of Memtest with Clover:

  1. Download memtest, I used this link: Image for creating boot-able USB Drive
  2. Open the archive by double clicking on it.
  3. Mount the file memtest86-usb.img within by double clicking again.
  4. Now, you should see a folder named EFI in this volume, containing a folder BOOT. Open it.
  5. The files containing it are the actual app, in 32 and 64 bit versions. Think in almost all cases we want to use the 64 bit version.
  6. Now, mount your EFI partition, using Clover configurator.
  7. Create a folder named MemTest86 in the EFI folder on your main drive.
  8. Copy all files in the EFI/BOOT folder from the mounted image to your newly created folder.

That ends the basic setup! Now, we add the correct Menu entry to the clover boot menu, so that we can actually start this app.

 

Get into clover configurator, open your standard config.plist from your boot drive and go to the GUI section. Under "Custom Entries", add an entry like this:

 

IDxDDKb.jpg

 

Please note while the path you enter is not case sensitive, you must make sure you use the backslash "\" for entering paths, and not a slash. So basically what we do is tell clover where it can find the app, give it a name, and tell clover it is a "Windows" app. Note: with older Clover versions we had to set this to "Linux", but for now "Windows" is the setting that works.

 

If you prefer to do a manual config, add this entry to your config.plist, under GUI/Custom/Entries:

<dict>
    <key>CustomLogo</key>
    <true/>
    <key>Disabled</key>
    <false/>
    <key>FullTitle</key>
    <string>MemTest86</string>
    <key>Hidden</key>
    <false/>
    <key>Ignore</key>
    <false/>
    <key>Image</key>
    <string>\EFI\CLOVER\themes\Icons\os_mint.png</string>
    <key>Path</key>
    <string>\EFI\MemTest86\BOOTX64.efi</string>
    <key>Type</key>
    <string>Windows</string>
    <key>VolumeType</key>
    <string>Internal</string>
</dict>

Now, save and reboot and you should see the newly created entry. Note that I also used a custom Icon - this is optional - in case you don't you will just see a generic windows icon instead:

 

uxzSDIE.jpg

 

And this is how it looks like:

 

Xx9iSWF.jpg

 

DvmExI9.jpg

 

PS: also noticeably faster and you get also more features with this version than with the older version, for example it does now write a log file. For more Information, see: http://www.passmark.com/forum/showthread.php?4315-Memtest86-Version-5-Beta-%28Pure-UEFI%29

 

 

2) gdisk

 

Another app you can use is the UEFI version of gdisk (aka GPT fdisk), which you can use to edit and change your partitions.

 

Warning! Install and use this app at your own risk! If you do something wrong here you might nuke your drive(s), so only use that if you know what you are doing.

 

This is how to do it (even easier):

  1. Download here: https://sourceforge.net/projects/gptfdisk/files/gptfdisk/1.0.1/gdisk-binaries/gdisk-efi-1.0.1.zip/download
  2. Mount your EFI partition
  3. Unzip the file and copy the resulting folder to your EFI Folder, so your path goes like this "/Volumes/EFI/EFI/gdisk-efi"
  4. Get into clover configurator, open your standard config.plist from your boot drive and go to the GUI section. Add an entry like this:
TVHAikU.jpg

 

If you prefer to do a manual config, add this entry to your config.plist, under GUI/Custom/Entries:

<dict>
    <key>CustomLogo</key>
    <false/>
    <key>Disabled</key>
    <false/>
    <key>FullTitle</key>
    <string>GDisk</string>
    <key>Hidden</key>
    <false/>
    <key>Ignore</key>
    <false/>
    <key>Image</key>
    <string></string>
    <key>Path</key>
    <string>\EFI\gdisk-efi\gdisk_x64.efi</string>
    <key>Type</key>
    <string>Windows</string>
    <key>VolumeType</key>
    <string>Internal</string>
</dict>

When everything went OK you should see this after selecting the respective entry in Clover:

 

Uhs8HUD.jpg

 

 

3) RU

 

I recently found one more app that might be interesting to some, and thats "Read Universal" or in short "RU". This is a tool that enables you to debug your BIOS and read (and modify!) every imaginable data, including UEFI variables, ACPI Tables etc.

 

Warning, again! I think blindly messing around with this app is even more dangerous, but on the other hand it gives you access to a lot of potentially interesting stuff.

  1. Download here: http://ruexe.blogspot.de/
  2. The next steps are basically the same as above so make a folder in your EFI partition, copy the .EFI files and make another custom entry in your config.plist

Here are some screens:

 

EfIvc9P.jpg

 

HWKGeQ5.jpg

 

1P2QwT8.jpg

 

 

So this is what you also can do with UEFI and clover. I am curious which other useful applications might exist!

 

Anybody who knows, maybe post it here?

Edited by frankiee

Share this post


Link to post
Share on other sites
Advertisement

This almost worked for me,

 

Was able to start MemTest86 with the Clover bootloader, but my screen turned black when I started te test.

I don't have this problem when I use a bootable USB.

 

Does it have something to do with environment variables that Clover sets to boot things? Can I disable this for certain boot entries?

 

A good partition tool would be a nice application to add to the list :D

Share this post


Link to post
Share on other sites

So you see the Memtest menu?

 

Not sure why you are having problems, but since you managed to load it via Clover it might not be Clovers fault. And AFAIK the version used with the USB stick and the EFI version are not exactly the same.

 

At least I can tell you that I did nothing but the steps I outlined above in the guide.

Share this post


Link to post
Share on other sites

This almost worked for me,

 

Was able to start MemTest86 with the Clover bootloader, but my screen turned black when I started te test.

I don't have this problem when I use a bootable USB.

 

Does it have something to do with environment variables that Clover sets to boot things? Can I disable this for certain boot entries?

 

A good partition tool would be a nice application to add to the list :D

 

 

I have this same problem.

But If I go to clover shell and run the memtest EFI file from there it runs perfectly...

What might be the problem?

Share this post


Link to post
Share on other sites

I have this same problem.

But If I go to clover shell and run the memtest EFI file from there it runs perfectly...

What might be the problem?

 

I have run MemTest recently again, and now i have the same problem. Running it from a dedicated boot stick worked. So yeah, good question! Since this occured with the same old version I used when I wrote this guide, and with the updated one as well, it seems like something in Clover has changed, but right now I am unable to tell what it is.

Share this post


Link to post
Share on other sites

I have this same problem.

But If I go to clover shell and run the memtest EFI file from there it runs perfectly...

What might be the problem?

 

The problem was that the Type was set to Linux. Set it to "Windows" and it runs again.

 

 

A good partition tool would be a nice application to add to the list :D

 

Yeah sure! What about this: https://sourceforge.net/projects/gptfdisk/files/gptfdisk/1.0.1/gdisk-binaries/gdisk-efi-1.0.1.zip/download ;)

 

PS: I have updated this guide accordingly

Share this post


Link to post
Share on other sites
Posted (edited)

I have managed to get memtest working with clover. now i want to get my windows 10 pocket edition to work and also acronis true image. they are both efi bootable. the thing is. i dont get it to boot.

do you guys know how to get it to work. i have set it up in clover configurator and i see it in the clover bootloader only when i click the windows 10 pe i get a error and with acronis i can chose it but then also i get a error that the files cant be found.

here are some screenshots. the top one is acronis and the bottom one is windows 10 pe

Knipsel.PNG

Knipsel2.PNG

Edited by TheIronShadow

Share this post


Link to post
Share on other sites

Sorry, I have no experience with neither Windows PE nor Acronis. But what you have to do anyways is to find the correct ".efi" application and make an corresponding entry in clover (just like with the memtest entry under GUI > Custom > Entries), like this:

<dict>
	<key>Disabled</key>
	<false/>
	<key>FullTitle</key>
	<string>Windows 10</string>
	<key>Hidden</key>
	<false/>
	<key>Ignore</key>
	<false/>
	<key>Path</key>
	<string>\EFI\Microsoft\Boot\bootmgfw.efi</string>
	<key>Type</key>
	<string>Windows</string>
	<key>VolumeType</key>
	<string>Internal</string>
</dict>

So this would be an entry for a common windows installation, maybe you have to adapt the path for "bootmgfw.efi" for windows 10 PE?

As for the acronis thing, I see a folder called "efi" in your screen, so maybe the app you are looking for is found there?

Also I have found that the "type" needs to be adapted as well. I mean for windows it is actually "Windows", but maybe you will need to adapt this as well for the acronis entry.

Hope this helps!

Share this post


Link to post
Share on other sites
On 12/6/2013 at 7:22 AM, frankiee said:

1) Memtest

    8. Copy the three files from the mounted image to your newly created folder.

 

What 3 files?

Benchmark (Folder)
blacklist.cfg
BOOTIA32.efi
BOOTX64.efi
mt86.png
unifont.bin

Share this post


Link to post
Share on other sites
Posted (edited)

hello. I currently have a dual boot setup using Systemd bootloader and Clover as subordinate to it with Sierra.  I believe I need to update CLOVERX64.efi while booted into my Linux partition to update Clover but then I'm having trouble finding it, although I'm able to find the installer easily. I had tried to start a new topic but for some reason, I can only set the title and no content/body and posted in this thread due to its relatedness.  Thanks.

Edited by dawntodon

Share this post


Link to post
Share on other sites

 

On 4/18/2018 at 2:50 AM, ellaosx said:

What 3 files?

Benchmark (Folder)
blacklist.cfg
BOOTIA32.efi
BOOTX64.efi
mt86.png
unifont.bin

 

I see that the image now contains additional files. Basically, you can copy the the contents of the whole EFI/BOOT folder contained in memtest86-usb.img.

Share this post


Link to post
Share on other sites
On 5/12/2018 at 4:33 AM, ellaosx said:

Figured....What are those 3 files from previous release?

 

Not sure but does it matter anyways? I guess it was BOOTX64.efi, mt86.png and unifont.bin. BOOTIA32.eif should not be needed, not sure about unifont.bin and blacklist.cfg. But as I said, it cannot hurt to copy all files. When I have some time, I will update my own memtest install and take another look at it.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By thomaspetersen
      Hi All
       
      I'm trying to start a Hackintosh High Sierra 10.13.5 installation:
      - MSI B350 PC Mate
      - Ryzen 5 - 2600
      - Radeon Pro 580 GPU
      - 4 x 8GB DDR4
      (Have a working clover bootloader for HS 10.13.3 - but for some reason, I can't use that setup with the 10.13.5) 
       
      Have tried different bootloader setup, with different outcomes...
      ATM. I get this error/hang - "Unknown CPU: family = 0x17, model = 0x8, Stepping = 0x2"
      Have search google, and can see that the threads ppl. are getting this, is when they look at "About this mac", I haven't yet installed the OSX.
       
      So can someone help...

      I'm running the newest Kexts: AppleALC, FakeSMC, Lilu, RealtekRTL8111, USBInjectAll and WhateverGreen.
      In Bootloader setup, i'm running: -v, -s, -f, -no_compat_check, busratio=34, PCIRootUID=1, npci=0x2000, dart=0 and nv_disable=1
      In SMBIOS i'm using the iMac18,2 and in RT i'm using BooterConfig: 0x28 and CsrActiveConfig: 0x67
      In installed drivers i'm using: AptioMemoryFix, EmuVariableUefi-64, OsxAptioFixDrv-64 (Have tried Fix2 as well)
       
      But i'm, keep getting the Unknown CPU hang/error, can someone help...
      Or do someone have a setup with the same CPU and GPU, that can show me his/her setup for Bootloader/Kexts...
    • By Teress
      I get a lot of questions about HOW TO BACKUP A HACKINTOSH. So I decided to create Complete Guide with 5 methods described in detail, how to easily make bootable clones of Hackintosh system disks, or backup your data. Full step by step tutorial is here:
       
       
    • By tlefko
      macOS-Mojave-XPS13-9350
      Hello, this is a simple guide to get OS X 10.14 working on any XPS 13 9350 model
      This guide uses files from (@syscl) (albeit edited) and full credit to him for the Deploy.sh and DSDT patches. However, his Clover folder is unbootable with Mojave and thus has been redone.
      However, his Deploy is still retained but edited to remove some DSDT patches that break things on Mojave
      I did my best to keep the guide simple and for the most part it is, it's inteded for the 6200U non iris but should work with others. (credit @syscl)
      Issues
      Wake up via lid is hit or miss (sometimes needs key press) SD Card slot Restarts don't work (endless black screen while turning off but still on) Usage Notes
      USB Devices eject upon sleep (USB Patches via Deploy were major issue) Changing board number via Clover Config doesn't work always unless serial is changed (No idea..) Audio is controlled via VoodooHDA however prefpane is not nessacary. Never tested USB C anything. Charging should be fine however I'm not sure about others, don't personally use it) What Works
      Everything else! Setup Notes
      The new AFPS file system must be used, there is no way to avoid it. Has no noticeable adverse effects except slower boot time It is difficult to repartition AFPS drives and resize them, recommend clean install or you could have one partition smaller than your hard drive that can't be increased unless reformatted Although Volumes will be converted, keep drive as GUID BIOS Settings
      Set all SATA operation as AHCI Disable Secure Boot, Fast Boot For Coil Whine improvement disable C-States Enable UEFI Booting (Disable Legacy if easily confused) Recommended: Clean Install (Preinstall steps)
      Download latest Mojave version from Mac App store (Register AppleID as developer, enroll your mac, download the preview from the link onsite or google for detailed instructions. Make Bootable media (google how or download app to do it, it's just a terminal command) Download the Latest Clover revision (currently using r4568) and install it to your USB as UEFI and ESP (no need for drivers) Copy The contents of this Github repository into your EFI folder on the USB (Mount the EFI Partition via clover config, efi mounter, etc.) (No Boot Folder in EFI) If you have the same XPS Model as me you can use stock ACPI patched files (6200u, hd 520, 3200x1800,) if not delete contents of both folders (origin, patched) and will fix later via @syscls modified deploy) Installing Mojave (Clean Install)
      Boot PC off the USB, select your Installer as your Boot drive from clover menu config is currently set to FAKESERIAL and -v. I believe (@syscl's) deploy generates serial # information Once installer is loaded, go to disk utility and format as a GUID Partition Table with whatever partitions you want (Don't format whole drive to afps make sure it's GUID) Run the Mojave installer to the drive wait for it to finish, then turn off) From Clover, select the name of the Mojave Partition (not preboot, recovery, etc.) and not your USB stick either From here the installation will continue. DO NOT CLICK ON MOUSE OR KEYBOARD (crashes installer shortly after at least for me) Post Install (Clean Install)
      Reboot off your USB once again, load up your Mojave drive. First Boot will take long, if your using my ACPI files (from @sysl's deploy, edited) and have same model you should have everything out of box (except wifi) Regardless, run through the installer and set it all up. (without acpi) At this point screen should be fine, mouse, keyboard, no wifi should be present or bluetooth. No brightness control as well. go to terminal to mount EFI or via clover Config, EFI Mounter, etc, of both USB and the internal disk Copy and REPLACE the EFI folder from the USB into your hard drive. Unplug your USB and reboot and you should be able to boot without the USB now Turn off PC, boot into clover. Don't select a drive and press F4 and Fn+F4 a few times, wait a few seconds, then boot back to the drive Plug back in the USB, mount it's EFI, and run the modified Deploy Script on your Hard Drive EFI partition After deploy is finished, there will be VoodooI2C error as I deleted it from Kexts, for me it breaks Trackpad and Keyboard. For now will be using VoodooPS2. After Modded Deploy
      You should have no Internet at this point, the following next steps should resolve that. However, your Brightness, lidsleep, USB, bluetooth should be working Using your favourite Kext Installer (Put it on a USB or something to get it on the PC), install (credit @Rehabman's) FAKEPCIID and FAKEPCIID_Broadcomm texts that are included in the ManualKexts Folder Then run "Sudo kextcache -i /" from terminal, reboot, then run it again. By this point your wifi should be fixed, and everything should be done Post Install Notes
      Your welcome to transfer whatever other kexts you want to S/L/E, personally I leave them in the CLOVER Folder injected. Doing upgrade via mac app store is similar, just partitioning hard drive is harder. Apart from that same process essentially, not recommended Credits
      Credit Hackintosher.com for basic patches (although @syscl) covered some Credit to @syscl (clearly...) Credit to @Rehabman Credit to @syscl Kexts, and his contributers. ex. Lidwake.kext (although not fully compatible) Support
      Your welcome to open any issues on this thread, I personally have little DSDT knowledge so I will do my best to help! Thanks for Reading!
      - This is a clone from my GitHub, the link to the repository is below with all files
       
      https://github.com/tlefko/macOS-Mojave-XPS13-9350
       
      - I would really like to hear everyone's experience trying this guide so please let me know in the comments how it worked for you, if you plan to try it, etc.
    • By STLVNUB
      Reviving my old INSTAHackintosh, it's been a while....
      Purpose:
      Create User Custom Install iso/dmg with bootloader, apps and user-settings.
      Create Live iso/usb.
      What Versions:
      Tiger-Current ( bit ambitious but hey I like a challenge ).
      Why:
      Because I can!
      I'm not too impressed with the way Apple and others handle their installs.
      Support for 4 Bootloaders:
      Chameleon
      Clover Legacy
      Refit Ozmosis
      Clover UEFI
      Keep you informed as I progress from scratch.
      This could take a while, it's NOT my priority.
      Will probably release in Os versions, starting at Mojave and working backwards.
    • By FernandoCoverdale
      Buenas!
      recuerdo que cuando empece a instalar el clover para hacer mi hackintosh el boot de clover tenia una cuenta atrás en la que pasado “no se si eran 5 o 6 segundos”se iniciaba la opcion de arranque de high sierra del disco duro que es la que se marca por defecto, seguramente habré instalado un theme que me lo deja fijo y no recuerdo como volver activarlo.
      gracias de antemano!!!
      adjunto foto

×