I have a FDE enabled on my Android. However on JellyBean when device restarts I never get a boot password prompt,just regular unlock screen.
I remember on 4.0 ICS, after reboot Android would ask me for decryption key so it can mount the /data filesystem.
My device is Moto Droid 4.
I verified from command line that /data mounted with encryption, however I cant figure out where it gets the key from,if I never have to enter it on boot.
Related
As per the title. I have an S4 Active, humming along happily with "activeroot" applied when it first became available. I realized this morning that I never deleted the activeroot app itself, but when long-pressing the icon to get to the uninstall menu, my finger slipped. I really like geohot and his work, a whole lot, but the fact that there isn't at least a confirmation screen before overwriting important system files really grates on me. The instant the tap happened, the screen went black, and became immediately stuck on the AT&T logo at reboot.
If I power the phone up normally, I only see the AT&T logo for as long as I care to stare at it before powering it down. I can reboot into the stock recovery, but because the phone doesn't ask me for the disk-encryption password as in a normal boot, I see the error "Can't mount /data (Invalid argument)". The only non-destructive thing I could do at that menu was to wipe the cache, which obviously did nothing for my bootloader or encrypted disk. I feel pretty sure I haven't lost any data on that encrypted disk yet, and I know I could do a full factory wipe, but I'm hoping I have a better option:
1) Could it possibly be as simple as trying to send "towelroot", the newest root, to the phone via adb and execute it?
2) Without the ability to write to the disk, can I get a log file for further troubleshooting / ideas?
3) Is there a way to decrypt the disk over usb to at least pull over any non-backed-up files before performing a factory wipe?
4) Can I install a different recovery which might give me more or better options?
Thanks for any help you can provide! = )
In the past I've used CWM but with my new Moto G 2014 Dual SIM, I wanted to use encryption and I read that TWRP works with that, so I installed it but when I boot into it, it doesn't ask me for my password and /data is inaccessible (naturally!). I couldn't see any option to select to enter my password to decrypt it either. I flashed it with TWRP2801-titan-motog-2014.img
I understand that TWRP doesn't support Lollipop encryption yet but thought it did KitKat?
doveman said:
In the past I've used CWM but with my new Moto G 2014 Dual SIM, I wanted to use encryption and I read that TWRP works with that, so I installed it but when I boot into it, it doesn't ask me for my password and /data is inaccessible (naturally!). I couldn't see any option to select to enter my password to decrypt it either. I flashed it with TWRP2801-titan-motog-2014.img
I understand that TWRP doesn't support Lollipop encryption yet but thought it did KitKat?
Click to expand...
Click to collapse
My twrp support kitkat and lollipop encryption
http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2979149
luca020400 said:
My twrp support kitkat and lollipop encryption
http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2979149
Click to expand...
Click to collapse
Thanks, that's great. I can't get it to install though, as it shows I already have TWRP 2.8.0.1 installed and when I tap Recover Version to Install it doesn't list anything under Choose Version to Install and if I tap Install Recovery, that doesn't do anything either.
OK, I've installed it via the manual fastboot method now and it shows v2.8.3.0 but I still can't access /data. If I go to Mount and tap /data it doesn't do anything and if I tap /system it restarts TWRP, then locks itself and turns off the screen and when I press the volume buttons to turn it back on, it shows a padlock and a swipe to unlock. When I do that and check Mount, /data and /system are still not mounted.
The log screen shows:
Unable to mount /data
Unable to mount storage
Unable to mount /data/media during GUI startup
Full SELinux support is present
Failed to get default contexts and file mode for storage files
Unable to mount /data/media/TWRP/.twrps when trying to read settings file
doveman said:
Thanks, that's great. I can't get it to install though, as it shows I already have TWRP 2.8.0.1 installed and when I tap Recover Version to Install it doesn't list anything under Choose Version to Install and if I tap Install Recovery, that doesn't do anything either.
OK, I've installed it via the manual fastboot method now and it shows v2.8.3.0 but I still can't access /data. If I go to Mount and tap /data it doesn't do anything and if I tap /system it restarts TWRP, then locks itself and turns off the screen and when I press the volume buttons to turn it back on, it shows a padlock and a swipe to unlock. When I do that and check Mount, /data and /system are still not mounted.
The log screen shows:
Unable to mount /data
Unable to mount storage
Unable to mount /data/media during GUI startup
Full SELinux support is present
Failed to get default contexts and file mode for storage files
Unable to mount /data/media/TWRP/.twrps when trying to read settings file
Click to expand...
Click to collapse
Flash this one
https://s.basketbuild.com/filedl/devs?dev=luca020400&dl=luca020400/Motorola/recovery/twrp.img
The official one is bugged
luca020400 said:
Flash this one
https://s.basketbuild.com/filedl/devs?dev=luca020400&dl=luca020400/Motorola/recovery/twrp.img
The official one is bugged
Click to expand...
Click to collapse
Thanks but I get the same results with that I'm afraid.
Just checking if there's any news on this? I'm not sure where TWRP is meant to prompt for the decryption password but I haven't seen any prompt or option for that anywhere.
I've flashed the Kali Nethunter .zip on top of the Chrome ROM. It didn't boot correctly and after that I wanted to go back to TWRP and restore my back-up. And it suddenly is asking for a decryption password. When I fill in: "default_password" it starts decrypting with alot of error messages.
Mainly being: E: Unable to stat /data/xxx/xxx/xxxx. xxx
When it's done it brings me back to the TWRP screen. I'm able to access /system but not /sdcard or /data.
Does anyone have an idea?
Is default password your password or the twrp default password?
MAybe you should reflash your ROM.over usb and see if it boots.
You said "did not boot correctly" vs "did not boot"
If you can get into your system, turn off lock screen passwords and your phone will not require a password to decrypt at boot, and TWRP won't need a password to access your userdata partition.
I have a Moto X2 with Android 6.0 and TWRP 3.0.2
I just turned on full disk encryption and set a pattern screen lock.
The first time I enter TWRP, it asked me for the pattern. However, after that, when I reboot into TWRP, it doesn't ask for pattern anymore.
I can't find any option about forget password or ask every time in twrp.
I am afraid others can just enter TWRP and copy my files through ADB or MTP. So is there a way to solve that?
BTW. I read the principle of Android full disk encryption. I guess TWRP already stored my master key somewhere, but I can't find it.
I recently bought an unlocked Pixel 5 from Amazon, only to discover it is (apparently) a VZW that was carrier unlocked, and so the OEM Unlock is not available. I am slowly making my peace with that fact, but am curious how much leeway I have to get at lease *some* more control.
When I boot into stock recovery, I have the option to mount /system. I am hoping this means I can pull, edit, and then push the build.prop and possibly other files as well. Perhaps also push the superuser binary. However, I am unable to detect my phone when I mount /system.
My system specs:
Windows 10 Pro
Version 21H2
OS Build 19044.2728
I have installed the latest drivers from Google.
I am able to detect and interact with my device in both ADB and Fastboot.
I was hoping being able to mount /system in the recovery menu meant I could use ADB shell and browse around the /system folder and tweak a few things. However, my computer behaves as though NOTHING is attached when I go into recovery. No "drivers not found" messages, no mysterious unidentified anything showing up in device manager.
Can anyone give me guidance as to how to get this working? Or am I not understanding how this is supposed to work?
Pixels do not have a recovery partition.; recovery lives in /boot alongside ramdisk and system kernel. Recovery is largely unnecessary from a modding perspective because of the ease of which we can directly flash device partitions.
Ok, but I can boot into stock recovery via "adb reboot recovery". From there I have the option to "Mount /system". I am hoping to be able to do that, then use adb to pull and then alter the build.prop file.
I can not flash device partitions because I cannot unlock the bootloader (I apparently have a Verizon phone.)