Jump to content
vit9696

FileVault 2

496 posts in this topic

Recommended Posts

Advertisement

:thumbsup_anim:  Great work everyone, many thanks I am excited to try it  :thumbsup_anim:

 

Can I please ask at what point of reboot is the password requested as I generally skip the Clover GUI (Login = 0 in Config.plist), would this be a problem?

 

I also use the Apple bluetooth Keyboard, Mouse and Trackpad which work fine both in the BIOS and Clover GUI as they connect with the Apple Broadcom Bluetooth would they be compatible?

Share this post


Link to post
Share on other sites

The pw is requested by boot.efi, clover ui has nothing to do with it. You should choose the right boot entry at least once though.

(Boot macOS from Recovery HD)

 

As for your input devices that needs testing. I would say that they should work almost certainly though.

Share this post


Link to post
Share on other sites

Thanks vit9696, it has been a while since FileVault was first tested with Clover (Back on ProjectOSX and it didn't work) so I will have to familiarise myself with the process again at the weekend when I get home.

Share this post


Link to post
Share on other sites

Thanks vit9696, it has been a while since FileVault was first tested with Clover (Back on ProjectOSX and it didn't work) so I will have to familiarise myself with the process again at the weekend when I get home.

Yes, it never worked before.

Share this post


Link to post
Share on other sites

Just wanted to say thanks to everyone involved here for reaching this milestone. Fantastic work! FV2 up and running here

Cheers!

Share this post


Link to post
Share on other sites

If anyone can spare the time would you be able to document the process of enabling it please (Nothing too fancy obviously) for example which of the options did you choose etc?

Share this post


Link to post
Share on other sites

I just tested it. It works as described.

You should choose recovery HD on that drive to be able to boot, which make sense if you think how file vault works.

One minor issue is, I had to replug my usb keyboard to be able to type my password, even though I've booted via legacy clover, as described in recommendation. I'll try the AppleKeyAggregator from Apple Firmware, just for test (I mean who would use closed source programs and want to encrypt the drive with it or better decrypt with that?!).

 

Everything else is perfect. Thanks again to all who contributed...

 

Edit: I've tried the original AppleKeyMapAggregator from Apple firmware, even the AptioInputFix. Nothing changed though, I still have to replug my keyboard :(

 

Edit2: Just had the idea, locking from find my mac should theoretically work, right?

Share this post


Link to post
Share on other sites

with legacy Clover, remove the EDK2 UsbKbDxe driver and use mine... also best to use Apple's AppleKeyMapAggregator.

Do not use AmiShim.

Is there a guide to build your UsbKbDxe?

Share this post


Link to post
Share on other sites

I'm using Intel+AMD (black screen during boot) solution for a working sleep. When I enable FV2 Will I have black screen while typing password ?

Share this post


Link to post
Share on other sites

I'm using Intel+AMD (black screen during boot) solution for a working sleep. When I enable FV2 Will I have black screen while typing password ?

Yes, you will have black screen while typing password.

Moreover, there can be one caveat. I initially have two users on the screen and I have to choose one of them by mouse and only then type password.

But you can't use mouse on black screen.

I also using Intel+AMD for working sleep. And I have a monitor with two entry. First entry for Intel, second for AMD with a simple switch between two screens.

Share this post


Link to post
Share on other sites

Does Clover now install all the files required in Drivers64UEFI meaning I just have to enable FileVault via System Preferences > Security and Privacy and reboot letting Clover do it's thing?

 

Files currently in Drivers64UEFI:

post-499606-0-83368100-1477804460.png

Share this post


Link to post
Share on other sites

Does Clover now install all the files required in Drivers64UEFI meaning I just have to enable FileVault via System Preferences > Security and Privacy and reboot letting Clover do it's thing?

 

Files currently in Drivers64UEFI:

attachicon.gifScreen Shot 2016-10-30 at 05.19.07.png

No, UsbKbDxe or other special keyboard driver needed.

FV2 uses own keyboard interface and can't use UEFI BIOS keyboard driver.

Share this post


Link to post
Share on other sites

Good morning Slice and thanks, I added this one...

 

post-499606-0-90159300-1477805476.png

 

 

If I have a password enabled when logging into Sierra, will I get two password prompts when FileVault is enabled?

Share this post


Link to post
Share on other sites

Ok, that didn't go so well. I can't get past the Recovery screen now having let FileVault reboot the computer.

 

How do I access the Clover GUI if timeout is set to 0 please?

Share this post


Link to post
Share on other sites

How does it work with Bluetooth keyboards (for example Apple Magic Keyboard)?

 

You have to have AptioInputFix.efi present for Apple Bluetooth Keyboards to work, I just tested this (Not tested the alternative keyboard driver).

 

Once FV2 is enabled do you have to always boot from the "Boot macOS from Recovery HD" option that appears in the Clover menu?

Share this post


Link to post
Share on other sites

Once FV2 is enabled do you have to always boot from the "Boot macOS from Recovery HD" option that appears in the Clover menu?

 

Yes.

 

EDIT: Do I see it wrong or is UsbKbDxe placed in drivers64 for legacy boot? What sense does that make? Just replace the TianoCore one in the DUET image, that will solve the issue of having to reconnect the keyboard on every boot...

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.

Announcements

  • Similar Content

    • By ludufre
      Since the Catalina beta 9, FileVault takes about 3 minutes to request the password.
       
      I am currently in a final version 19A602 and the problem continues.
       
      If anyone can take a look, I have attached "gen_debug" before and after disabling FileVault.
      I noticed that if I boot in verbose, the login screen takes the same time, but at left o screen a lot of lines pop up:
      ERROR: LWSmcUINT8ForKey smcProtocol-> SmcReadValue failed for key '... Important: In attachments the Kexts are in /EFI/CLOVER/kexts/10.15/ but the behavior in /Library/Extensions is the same.
       
      Important 2: Tried without UsbKbDxe.efi, UsbMouseDxe.efi, Ps2MouseDxe.efi and same issue.
       
      My laptop is from this guide that I wrote: 
       
      gen_debug.zip
       
       
      [EDIT]
       
      Solved with https://www.reddit.com/r/hackintosh/comments/cre5da/filevault_howto
       
      Basically removes:
       
      AppleImageCodec.efi
      AppleImageLoader.efi
      AppleKeyAggregator.efi
      AppleUITheme.efi
      AptioInputFix.efi
      Ps2MouseDxe.efi
      FirmwareVolume.efi
      SMCHelper.efi
       
      And, add:
       
      AppleGenericInput.efi
      AppleUiSupport.efi
      VirtualSmc.efi
       
      Of course, replace FakeSMC kexts with VirtualSMC kexts.
       
      Now, just 5 seconds to ask password.
    • By antonioruri
      Buongiorno, ho da poco messo a posto quasi tutto sulla mia prima configurazione hackintosh che va benissimo. In questi giorni è apparso l'aggiornamento di sicurezza di High Sierra come da titolo e me lo ha scaricato ma prima di partire con l'installazione vorrei avere delle delucidazioni riguardo agli aggiornamenti in generale soprattutto ai minor, per ora non ho bisogno di aggiornare a Mojave.
      Si corrono dei rischi ad eseguire aggiornamenti di questo tipo (sicurezza come in questo caso) o ad esempio a versioni piu nuove dello stesso sistema MacOS? Se sì quali sono e come si prevengono? 
      Non vorrei ritrovarmi a dover re installare tutto formattando il disco partendo da zero. Qualche tempo fa ad mio amico succedeva che il disco veniva crittografato con "Filevault" e diventava inaccessibile, questo dopo un minor update, al che ha dovuto ricominciare da 0. Cos'è il Filevault? Potrebbe capitare questo anche a me? Vorrei sapere tutto prima di andare a fare delle minchiate.
      Grazie in anticipo a chi vorrà e avrà la pazienza aiutarmi. 
    • By JLMOX
      I think, at this point converting to hfs+ is out of the question, Apple has been pushing the apfs file policy very aggressively, so does anybody solved the missing "Boot macOS from Mojave " (this last word may be different). I have installed the latest clover in HDD and USB, but I can only see 3 Mac Os related tabs but not the one for actually loading the Mojabe mac OS. I updated high sierra to Mojave and everything went fine. My laptop (Dell E6530) booted up normally, Mojave system loaded up, I finished the setup and spent sometime exploring. I updated clover to the latest version and turned of machine. When I restarted, I noticed Clover did not have an option for booting into the system like High sierra had it. I tried adding the apfs.efi or the ApfsDriverLoader-64.efi driver to the clover efi folder in the HDD and also tried with a USB clover installation and the result is the same: No boot option for the Mojave OS. I used the recovery option and I was able to explore the partion where the system is located but that´s as far as I could go. Does anybody has an idea of what happened?

×