Jump to content

FileVault Setup for Clover Need Extra Help V 5145


makk
 Share

11 posts in this topic

Recommended Posts

FileVault enabled and does not want to disable.

In Clover what drivers are needed to boot into Big Sur and Monterey?

 

There's a few in there, but which ones are actually needed?


Just the drivers and something else needs to be enabled in the config.plist? 

Clover 5145

Clover 5144

 

Much appreciated

Edited by makk
Link to comment
Share on other sites

I didn't check the FileVault ability many years. As in past you need drivers:

AppleImageCodec.efi, AppleKeyAggregator.efi, AppleKeyFeeder.efi,  AppleUITheme.efi, EnglishDxe.efi, FirmwareVolume.efi, SMCHelper.efi, HashServiceFix.efi, UsbKbDxe.efi (this is special version for FileVault).

As well as usual ApfsDriverLoader.efi, Fat.efi, HFSPlus.efi, OpenRuntime-v12.efi.

Nothing to change in config.plist.

Hope you will have success

  • Like 1
Link to comment
Share on other sites

19 hours ago, Slice said:

I didn't check the FileVault ability many years. As in past you need drivers:

AppleImageCodec.efi, AppleKeyAggregator.efi, AppleKeyFeeder.efi,  AppleUITheme.efi, EnglishDxe.efi, FirmwareVolume.efi, SMCHelper.efi, HashServiceFix.efi, UsbKbDxe.efi (this is special version for FileVault).

As well as usual ApfsDriverLoader.efi, Fat.efi, HFSPlus.efi, OpenRuntime-v12.efi.

Nothing to change in config.plist.

Hope you will have success

 

Wow that is quite a few more than a 12 pack...

Thank you.

 

Clover 5144 

 

Should I duplicate for BIOS and UEFI?

 

 

 

Screen Shot 2022-03-15 at 4.23.26 AM.png

Link to comment
Share on other sites

14 hours ago, Slice said:

Boot if you boot as a drive (legacy boot).

UEFI if you boot as Clover64.efi (UEFI boot).

Should you double or not it is your decision.

 

Thank you.

 

Apology, I am not well versed on Clover boot up choice scheme and please correct me if incorrect?

IN the Boot Section if  I want UEFI I should place CLOVERX64.efi in the config.plist for Boot >

--> DefaultLoader String CLOVERX64.efi

 

If this is a BIOS/UEFI boot cannot tell you since I see both legacy and UEFI.

Windows boots UEFI. and as far as I know, this boots through the sequence of

BIOS > UEFI> Mac or Windows.

 

Where I am confused is with CSM Hybrid enabled in BIOS, the response given is legacy when enabling( had to check to make sure what boot sequence)

But in boot logs I see reference to x86legacy.

 

from Log on Clover App:::703  0:000 Result of bootcode detection: bootable unknown (legacy)

 

And then on boot up Clover would look in the UEFI folder instead of BIOS folder?

 

Is this the correct sequence and logic?

I have NTFS.efi in the UEFI folder and BIOS folder.

 

I wasn't sure which boot this uses.  How to determine in the log if it is actually using BIOs and then passing to UEFI?

Or if UEFI doesn't look in BIOS ?

 

Still learning here

Edited by makk
Link to comment
Share on other sites

3 hours ago, makk said:

 

Thank you.

 

Apology, I am not well versed on Clover boot up choice scheme and please correct me if incorrect?

IN the Boot Section if  I want UEFI I should place CLOVERX64.efi in the config.plist for Boot >

--> DefaultLoader String CLOVERX64.efi

 

If this is a BIOS/UEFI boot cannot tell you since I see both legacy and UEFI.

Windows boots UEFI. and as far as I know, this boots through the sequence of

BIOS > UEFI> Mac or Windows.

 

Where I am confused is with CSM Hybrid enabled in BIOS, the response given is legacy when enabling( had to check to make sure what boot sequence)

But in boot logs I see reference to x86legacy.

 

from Log on Clover App:::703  0:000 Result of bootcode detection: bootable unknown (legacy)

 

And then on boot up Clover would look in the UEFI folder instead of BIOS folder?

 

Is this the correct sequence and logic?

I have NTFS.efi in the UEFI folder and BIOS folder.

 

I wasn't sure which boot this uses.  How to determine in the log if it is actually using BIOs and then passing to UEFI?

Or if UEFI doesn't look in BIOS ?

 

Still learning here

No. Boot process go as follow:

1. Legacy computer (Core2Duo for example)

BIOS->Hard Drive #0->first sector from the drive->start the small program from the sector, it is Clover's boot0-> it looks MBR partition 0 and find here file "boot" which is Clover's boot6

->start it-> it searches the file CloverX64.efi which is the Clover. SHow GUI on screen where we can choose OS.

2. New UEFI computer:

BIOS->search for BOOT0000 entry in NVRAM and analyze it. Otherwise it knows the name EFI\BOOT\BOOTX64.EFI -> Clover can create own BIOS entry named EFI\CLOVER\CLOVERX64.EFI->

start chosen efi application.

You can press F12 and see the list of EFI applications to start, for example

\EFI\BOOT\BOOTX64.EFI which can be Clover, OC, Windows or Linux depending on history.

\EFI\CLOVER\CLOVERX64.EFI is you want

\EFI\OC\OpenCore.efi

\EFI\Microsoft\boot\bootmgfw.efi

\EFI\***\grubx64.efi

and so on.

Link to comment
Share on other sites

1 hour ago, Slice said:

No. Boot process go as follow:

1. Legacy computer (Core2Duo for example)

BIOS->Hard Drive #0->first sector from the drive->start the small program from the sector, it is Clover's boot0-> it looks MBR partition 0 and find here file "boot" which is Clover's boot6

->start it-> it searches the file CloverX64.efi which is the Clover. SHow GUI on screen where we can choose OS.

2. New UEFI computer:

BIOS->search for BOOT0000 entry in NVRAM and analyze it. Otherwise it knows the name EFI\BOOT\BOOTX64.EFI -> Clover can create own BIOS entry named EFI\CLOVER\CLOVERX64.EFI->

start chosen efi application.

You can press F12 and see the list of EFI applications to start, for example

\EFI\BOOT\BOOTX64.EFI which can be Clover, OC, Windows or Linux depending on history.

\EFI\CLOVER\CLOVERX64.EFI is you want

\EFI\OC\OpenCore.efi

\EFI\Microsoft\boot\bootmgfw.efi

\EFI\***\grubx64.efi

and so on.

 

Thank you,

Is this HP considered legacy?  It boots UEFI.

 

Ok I understand that portion of the boot.

For Clover to continue to proceed,  pass over, I don't need BIOS drivers?  because this is UEFI strictly.

So I deleted the BIOS folder F11 cleannvram, reboot start up boot into Monterey, Windows, success.

 

Is it safe to delete the BIOS folder in Clover? Does it use this folder at all?

 

F12 nice!  learning more!  

 

Thank you

 

 

Edited by makk
Link to comment
Share on other sites

 Share

×
×
  • Create New...