With clover installed with Unibeast for Sierra.What shell is this? The version that comes with Clover or built in?
You'd likely need to have UEFI enabled and be booted UEFI, not legacy to manipulate the boot menu from Clover's shell. If your boot menu has a built in shell you could also try from there.With clover installed with Unibeast for Sierra.
already created my usb installer with Legacy and setup the multibeast with Legacy also. i can't all this things again for nothing. because with UEFI enabled or disabled is the same result. I don't think UEFI has something to do with this issueYou'd likely need to have UEFI enabled and be booted UEFI, not legacy to manipulate the boot menu from Clover's shell. If your boot menu has a built in shell you could also try from there.
Those are EFI boot menu entries for sure, no idea how your firmware enables/disables UEFI - probably running DUET on top of BIOS.already created my usb installer with Legacy and setup the multibeast with Legacy also. i can't all this things again for nothing. because with UEFI enabled or disabled is the same result. I don't think UEFI has something to do with this issue
EFI doesn't boot from internal 'disks' it boots from .EFI files in vendor folders. There is an 'EFI boot menu' containing boot options that point to these files. e.g. 'Microsoft Boot Manager' points to /EFI/Microsoft/Boot/bootmgfw.efi1, 2, 3 working fine, but in Harddrive 4 skip to 5. I tried right now Harddrive SSD as the first one, skip again to the second one. The only order can't be accepted is the SSD hard, which i install EFI and MacosX on it.
On Aptio, it's not enough to rename Cloverx64.efi on HDD to BootX64.efi to enable it to start