I'm just wonder is there android custom recovery that come with password security built in.
Related
I was able to enable Android encryption (/user partition) under a stock ROM, but I've tried several ROMs that where encryption fails. Specifically, when enabling encryption on AICP 4.4.4, the system reboots (as usual), then completely forgets that I asked it to get encrypted.
Semi-related, I'm having trouble installing TWRP onto the Xperia Z2. AFAIK it's the only recovery that supports encrypted partitions, and XZDualRecovery bundles a version of TWRP that may be too old to use the KK4.4 encryption.
(After installing TWRP based on directions from the site, booting into recovery via power + volume up buttons just hangs on a black screen.)
My phone is a Sony Xperia Z2 D6503, with unlocked bootloader.
Has anyone gotten this to work?
I have gotten this to work (sort of) with a two-kernel solution.
This post contains a stock kernel that has been modified to include TWRP 2.8.1.0 as its recovery (17.1.2.A.0.314-based, by Desperanto86). In combination with the TWRP image, encrypted partitions can be backed up:
Code:
fastboot flash boot boot.img
fastboot flash recovery openrecovery-twrp-2.8.1.0-sirius.img
If you enable encryption on top of this, the system no longer boots (I used custom ROM cm-11-20141206-NIGHTLY-sirius.zip). Flashing the CM boot.img allows the device to boot, but TWRP is no longer accessible.
It's probably possible to integrate TWRP into CyanogenMod's boot.img, but for now, I'm okay with just re-flashing the kernel at times when I need to back up my device (hopefully I don't burn through the flash memory with all the writes). So the process looks like this:
flash FTF firmware with Flashtool
enable developer options, then enable ADB in settings
install XZDualRecovery for root + recovery
copy custom ROM to /sdcard
boot into recovery, factory reset and install custom ROM
boot custom ROM, enable passcode, enable encryption
And when making backups:
power off phone
flash modded kernel + TWRP
take backup
flash original kernel boot.img from ROM (to restore boot ability)
Update for CM12/Lollipop: AOSP seems to enable hardware encryption for Qualcomm-based platforms, but this is not supported with TWRP (GitHub issue). Since hardware support is needed to decrypt storage, TWRP needs to load proprietary Qualcomm binaries to talk to the hardware (which are undocumented).
It seems like there will be no support for encrypted Lollipop backups, so I'll be sticking with 4.4.4.
I've got a strange problem on my Nexus 6P.
I've changed my password on the 6P (running Cyanogenmod), and ever since then, I can't enter my TWRP recovery, because it can't decrypt anymore. I've tried both the old and the new password in TWRP, but it can't decrypt it. The new password works without any problems to decrypt the phone when booting it normally into the OS, just not for TWRP.
TL;DR: Changed password in Cyanogenmod on encrypted phone, now can't enter TWRP recovery anymore, but can still enter the phone OS.
Any ideas? Perhaps I could somehow reflash TWRP without losing data? Or will this mess up the encryption even more, so that I possibly also couldn't enter the OS anymore?
jb91 said:
I've got a strange problem on my Nexus 6P.
I've changed my password on the 6P (running Cyanogenmod), and ever since then, I can't enter my TWRP recovery, because it can't decrypt anymore. I've tried both the old and the new password in TWRP, but it can't decrypt it. The new password works without any problems to decrypt the phone when booting it normally into the OS, just not for TWRP.
TL;DR: Changed password in Cyanogenmod on encrypted phone, now can't enter TWRP recovery anymore, but can still enter the phone OS.
Any ideas? Perhaps I could somehow reflash TWRP without losing data? Or will this mess up the encryption even more, so that I possibly also couldn't enter the OS anymore?
Click to expand...
Click to collapse
I see that bug too so I've reverted back to a working 2.x.x.x version. Flashing recovery has no effect on your data.
Wakamatsu said:
I see that bug too so I've reverted back to a working 2.x.x.x version. Flashing recovery has no effect on your data.
Click to expand...
Click to collapse
So how do I do this exactly? I can't enter the recovery at all. Do I have to do something in ADB? And you're saying, just installing an older TWRP version will fix this, without having to do anything else?
I am currently unable to decrypt my internal storage for access in recovery after installing Android 6.0.1. I updated to UL-ASUS_T00N-WW-13.6.5.35-user.zip from rooted Lollipop. Previously, I had no issues with encrypted Lollipop and twrp_2.8.7.8_v5.img recovery.
TWRP 2.8.7.8 and 3.0.0 both give me the prompt to enter my decryption PIN, but fail with the correct PIN. CWM doesn't give a prompt.
Presumably, the only solution I'm aware of is to do a factory reset from within the OS to turn off decryption. Is there a custom recovery that will work with encryption on this build?
can you have the files on the device encrypted when you have a rooted the device with magisk and installed twrp for better backups?
Right now i do not have to enter my pin at all in twrp.
Is there a custom revoery that can decrypt data if you flashed a cutsom ROM without diabling DM Verity?
The current pitch black revovery asks my for a password, that I don't have. default_password also doesn't work. So I assume that's not working as intended?
My screen lock is a pattern, if that matters.