Hello, everybody.
As the title says, I would like to know if our device is capable of having file-based encryption, in order to have Direct Boot enabled in custom ROMs. This would be helpful in an encrypted device that had a random reboot.
Thanks in advance.
I don't know :'v
Related
After receiving my beloved 1+2, I rooted it, installed TWRP and flashed Xposed. Then I encrypted the phone. After wanting to update the rom, I realized TWRP doesn't yet support encryption. I reflashed the stock recovery, which I found here. This didn't help either, no encryption supported.
How can you safely remove the encryption? Does anyone have a functioning setup with stock recovery an encrypted device? Or is it possible to flash new firmware throught fastboot leaving it encrypted?
I made my Htc M7 useless trying to remove it's encryption, so i'm really careful one the 1+2...
Does really nobody know how to reverse this prominent feature in android???
A simple factory reset from the settings menu completely removed the encryption
Hello all!
Just a quick question ( I did search the forum, sorry if I missed it), can you encrypt a Android 7.0 with file-based encryption? If so, how?
I have tried to use Nexus Root Toolkit, but each time it fails when transferring the SU zip over. I cannot copy the file over manually through MTP, I see folders with jumbled names (So I'm guessing the write-ability is encrypted too?)
Any help would be appreciated!
Thanks,
Gordon
I am encrypted and rooted. Works fine
When u have an unlocked bootloader, u need to flash TWRP, boot to it, then Flash SU 2.77+
My x727 fails to encrypt itself. After the reboot it did not start the encryption but got stuck for several hours.
Has anyone managed to encrypt the phone? Thank you.
(On my phone, Magisk v8, TWRP, PHH's Superuser and xposed is installed.)
Now that more people have the phone and more ROM versions (including first custom ROMs) are available: has anyone managed to encrypt the phone?
(Device encryption is very important to me because my employer does not allow me to connect an unecrypted phone to the firm network. Therefore, the phone is currently almost useless to me.)
Thanks!
I suppose x727 data partition it's already factory encrypted because during unlocking tests some users said the device asks for a key.
I have now managed to encrypt the phone with the latest ROM: http://forum.xda-developers.com/le-pro3/how-to/5-9-020s-update-x720-t3506829
are you using airwatch ?
As far as I can see, it appears that all custom roms disable encryption. I understand that twrp doesn't support decryption, but I would like to have it regardless.
I have some questions about device security running with an unlocked bootloader.
I am somewhat experienced and comfortable with flashing custom ROMs, mostly LineageOS,
and flashing back the original stock ROMs for Pixel and Samsung devices.
I have recently experimented with running LineageOS 20 (Android 13) on a Samsung Galaxy
Tab S5e with Magisk (and a few Magisk modules). Within several of the XDA forums, and also at
other web sites, it's recommended with custom ROMs the bootloader not be re-locked since
this can create problems.
I use my S5e for steaming videos, basic web browsing and other things. I don't do banking or
have anything I would consider a huge security risk. My intent is to understand what risks
exist with an unlocked bootloader so I can make more informed decisions what I should/should
not install.
With later versions of Android, including 13, the built in storage is encrypted by default.
If the device is powered off filesystems are at rest in an encrypted state so is it possible
for someone else to gain access to my data if they power on the device or flash
their own recovery and/or custom OS? If someone boots into recovery mode encrypted
filesystems should not be mounted and remain unavailable. I'm wanting to understand where
there are weaknesses that could be exploited to access data.
If the device is powered on and the OS has been screen unlocked the first time after boot
(so encrypted filesystems are mounted and available) is access to my data at increased risk,
assuming USB debugging is disabled?
Can apps be sideloaded in recovery mode that an attacker could use to gain access to data
in other ways even if encrypted filesystems have not been mounted.
Any other security issues to be aware of?
If risks I haven't considered are too great I can also go back to stock ROM, but would consider
ways of mitigating or reducing any risks with a custom ROM and unlocked bootloader.
Please let me know if there is a more appropriate place for this posting.
Thanks,
Rodney
Samsung encryption not supported in TWRP recovery, but I have seen Samsung device running LineageOS on AOSP encryption.
of course on unlocked bootloader attacker can enable adb, inject scripts and gain root access easy. however, still it requires lock screen credentials for decrypting, so your personal data remains secured.
for some devices it's possible to set user-settable root of trust, this would allow to compile LineageOS with avb/dm-verity and re-lock bootloader.
Thanks for the reply, would be great to figure out a way to be able to lock the bootloader with LineageOS.
I do notice the "OEM Unlocking" option does not exist in Developer Settings in LineageOS 20.
lol have fun!
How to properly ENABLE dm-verity and FEC for /system on Motorola X4 with LineageOS 17.1?