[OP5] Full-Disk-Encryption Enabler for OP5

[Fif_]

You miss Full-Disk Encryption on your OnePlus 5?
Here's a fix.
Flash the zip below after flashing your kernel (which means after every ROM update as well!).
The very first time you flash this mod, you'll have to format userdata, or bad things will happen.

First-time Install instructions:

• Flash your ROM
• Flash the attached Zip
• (Optional) Flash Magisk
• Format userdata. In TWRP, go to Wipe -> Format Data
• Reboot
• You are now unencrypted.
• To encrypt in Full-Disk Encryption mode, go to Settings -> Security -> Encrypt
• You're now in FDE mode!
• Profit!

And don't forget to reflash this module every time you flash a new boot image.

XDA:DevDB Information
Full-Disk-Encryption Enabler for OP5, Device Specific App for the OnePlus 5

Contributors
Fif_

Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2017-09-12

Created 2017-09-13
Last Updated 2017-09-13

 

[Fif_]

Here's the Zip.

 

[dragoi90]

@Fif_ should i erase "internal storage" or just data partition!Thank You!

Sent from my ONEPLUS A5000 using Tapatalk

 

[Fif_]

@Fif_ should i erase "internal storage" or just data partition!Thank You!

Sent from my ONEPLUS A5000 using Tapatalk

You need to format the data partition. That all also nuke the internal storage by the way, so your phone will be back to factory reset.

 

[BlueEffect]

Is this used for people who decrypted their devices and wish to go back to encrypted so that they can flash roms that only works with encrypted?

 

[Fif_]

Is this used for people who decrypted their devices and wish to go back to encrypted so that they can flash roms that only works with encrypted?

No this is for people that want to run FDE rather than FBE. Eg. to have Xposed working.

 

[alukarulz]

No this is for people that want to run FDE rather than FBE. Eg. to have Xposed working.

You can have Xposed working with FBE by just soft rebooting using Xposed installer.

 

[Fif_]

You can have Xposed working with FBE by just soft rebooting using Xposed installer.

You are right, but I don't want to have to do that, I want Xposed on the first boot...

 

[ndarkside93]

Is this used for people who decrypted their devices and wish to go back to encrypted so that they can flash roms that only works with encrypted?

If you want the go under settings and security and encrypt your phone

 

[Fif_]

Is this used for people who decrypted their devices and wish to go back to encrypted so that they can flash roms that only works with encrypted?

If you want the go under settings and security and encrypt your phone

This is used to change encryption type from FBE to FDE. You can also use it to run decrypted.

 

[ndarkside93]

This is used to change encryption type from FBE to FDE. You can also use it to run decrypted.

I know.I was just answering his question.

 

[sjamie]

You can have Xposed working with FBE by just soft rebooting using Xposed installer.

You are right, but I don't want to have to do that, I want Xposed on the first boot...

Ahh... I see... I am getting tired of having to soft reboot after each reboot. It looks like this FDE mod/hack would resolve this problem, right? Are there any real drawbacks to using FDE over FBE? What about if/when I decide to switch to another ROM?

 

[alukarulz]

Ahh... I see... I am getting tired of having to soft reboot after each reboot. It looks like this FDE mod/hack would resolve this problem, right? Are there any real drawbacks to using FDE over FBE? What about if/when I decide to switch to another ROM?

I downside is you have to flash the fde flash file Everytime you flash an update. Plus the first time you need to erase data.

 

[sjamie]

I downside is you have to flash the fde flash file Everytime you flash an update. Plus the first time you need to erase data.

Would I have to also erase my data when switching to a different ROM?

 

[Fif_]

I downside is you have to flash the fde flash file Everytime you flash an update. Plus the first time you need to erase data.

I'm already flashing Magisk after every ROM update, so it's just one more zip to flash.
Actually stock OOS doesn't seem to care, you only have to flash this mod once, before you convert to FDE.
OOS 4.5.10 will happily boot in FDE even without the mod, provided that the data partition is already FDE.
That's not the case for every ROM.

Another downside is that no unattended boots are possible. You have to type in the FDE password to boot into Android.

 

[alukarulz]

Would I have to also erase my data when switching to a different ROM?

No. Only once.

 

[sjamie]

I'm already flashing Magisk after every ROM update, so it's just one more zip to flash.
Actually stock OOS doesn't seem to care, you only have to flash this mod once, before you convert to FDE.
OOS 4.5.10 will happily boot in FDE even without the mod, provided that the data partition is already FDE.
That's not the case for every ROM.

Another downside is that no unattended boots are possible. You have to type in the FDE password to boot into Android.

Thanks! I'll definitely give this mod a try if I truly get tired of having to soft boot after each normal boot. Is there a tasker profile or some other way to automate that?

 

[Fif_]

Thanks! I'll definitely give this mod a try if I truly get tired of having to soft boot after each normal boot. Is there a tasker profile or some other way to automate that?

Yes you can, run in a root shell:

setsid sh -c 'stop; start'

But I always run into strange things in Xposed if it's not running at boot, so YMMV.

Be careful not to just restart the system UI but the full zygote stack.

 

[sjamie]

Yes you can, run in a root shell:

Thank you. What exactly is that command doing? Do I have to run it after each boot?

 

[Fif_]

Thank you. What exactly is that command doing? Do I have to run it after each boot?

"stop" stops all Android services.
"start" starts them again.
The "setsid sh" wrapper is there so that the commands will survive the Android shutdown and run to completion even if the parent process calling root is killed (which will happen as soon as "stop" runs).
Yes you'd have to run this after every boot.
But be careful that the second time Android starts after a boot is not detected as a second boot event or you'll end up in a restart loop.