@headkaze,
Not sure if you have already considered it but there is one sure fire way to find the
UUID of the
EFI partition Clover was booted from on ALL systems and boot configurations by using the output of
bdmesg :-
Toward the top of the output there is the property named
SelfDevicePath which contains the
Partition UUID that Clover was booted from, here is an example output from my desktop system ...
Code:
0:100 0:000 SelfDevicePath=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,0FBD5BD2-AE6A-4F30-BDD6-F8ABABD7E795,0x28,0x64000) @B259DB98
0:100 0:000 SelfDirPath = \EFI\BOOT
We can parse the output of
bdmesg for the EFI/Clover boot
Partition UUID with the following command :-
Code:
bdmesg | grep -i "SelfDevicePath=" | cut -d "," -f 6
Which will return just the
Partition UUID :-
Code:
0FBD5BD2-AE6A-4F30-BDD6-F8ABABD7E795
I've run that bdmesg grep command on all my different MacOS Hackingtosh systems and it appears to always return the correct
Partition UUID that Clover was booted from.
Its not a pretty or elegant method for sure but it should it would work for all systems booted with Clover and would get around unusual boot configurations such as mine (and others) ... you would only have to execute and parse
bdmesg once when EFI Agent or Hackingtool initialises.
Note: bdmesg is a Clover utility that is installed by the Clover installer and is not a standard MacOS command so I guess you would need to check that it is installed first in /usr/local/bin ... if it is then you could use that as the primary method to find the EFI Boot Partition .. if its not installed then fall back to using one of the other methods.
Just a suggestion ...
Cheers
Jay