So here is my situation:
I am bootloader unlocked.
I am rooted.
I have TWRP installed and operational.
The phone is exactly how I want it and it is running beautifully.
But I now have to encrypt the phone due to work regulations.
1) Is there a way to encrypt the phone and still have TWRP able to decrypt the phone so I can flash new builds, backup, etc.
2) If the phone is encrypted, does that mean that the SD-Card is also encrypted?
3) If I encrypt the phone, but can still access an unencrypted SD-Card, can I flash files from it, or does encryption block all that?
If anyone has some answers, I would appreciate it greatly.
[NG]Owner
Related
Hello,
Thought I would share my recent bad experience and the resulting solution.
My phone was on a GPE ROM, and I encrypted it for work reasons, encryption went smoothly, but once encrypted, it was impossible to go into recovery with the encrypted partitions visible (hence impossible to flash a new rom or even do a factory reset which is the only - or so I thought - way to remove encryption).
After many attempts including flashing the latest TWRP (not solved yet, they say 2.7 should include a solution) I was still getting the "unable to decrypt phone" error after entering the password (which works perfectly on regular boot) in TWRP.
Eventually, through a lucky mistake, I found the solution, at one point I mistakenly re-locked my phone (fastboot oem lock), later when I was trying to flash a stock recovery I realized I had to unlock it again... well, unlocking it through HTCdev automatically does a factory reset, regardless of the encryption!
viola, problem solved!
I know this has been asked a lot but, I see any of different info. I see there are kernels and boot images that basically decrypt. I'm going for the boot img and was wondering if I have a nandroid backup can it be restored after it has been decrypted? I haven't seen any info on it for the boot img , just the kernel way. Are the backups encrypted or just raw data and when it boots or booting it encrypts?
Anything?
bryantjopplin said:
Anything?
Click to expand...
Click to collapse
Please use the main thread:
http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
I've already read that and was not pertaining to my situation. I was already setup and running with root and unlocked boot loader and didn't want to loose anything. I have figured it out though, FYI. But thanks for not paying attention to the full question
If you backed up whilst encrypted then the data will be encrypted.
Your need to back up by connecting to computer and copy/paste all your needed data. Then decrypt then restore data back on.
flashing these kernels will not decrypt. They just dont force encryption, meaning if you factory reset and then wipe /sdcard, you wont be forced to encrypt on next boot.
Hi.
I have bootloader unlocked.
Latest miui8 installed and rooted.
And my brother that keep stealing my phone to get into my stuff, even if my phone is locked by a pin. He doesn't know the pin but with twrp he can connect to a pc and easely get whatever he wants.
So I need to encrypt my phone and still use TWRP to keep update it and to install SuperSu.
Now my miui is rooted. How cand I encrypt it and decrypt when I use TWRP ?
And is possible to use TWRP on an ecrypted phone? How I get the password to decrypt it from there?
I really need help, guys. thanks
Hi all,
I'm coming over from a Nexus 6p to this phone and have been a long time ROMaholic. I am having a ton of problems flashing and restoring nandroids on the 3t however. I'm hoping that someone smarter than I about these things could give me some insight. The issue I have is many times when I flash a new ROM or restore a nandroid backup I'm asked for a password when I boot. If I reboot to TWRP for some reason it wants a password in recovery as well. I never add any security password to my ROMs at anytime so I confused as to why it suddenly would ask me for one. When this happens I'm literally forced to format the phone and re-install everything. Does it have something to do with dm-verity or something? Why is it encrypting my phone when I install a new ROM?
Thanks for any responses.
It is likely due to encryption. TWRP seems to have trouble decrypting after flashing different ROMs. You might be able to restore a backup if you sideload the same ROM as the one on the backup, flash TWRP, then restore the nandroid.
Decrypting your phone will make it much easier to jump between different ROMs frequently, at the cost of security of course..
After having a simular problem with twrp I post this question in the twrp thread and never got an answer. Mysteriously twrp was asking for a password but i was able to continue without the password. but was unable to wipe dalvik or anything.
So decryption is the problem. If so if you have a stock backup it will be difficult to re-install?
Anova's Origin said:
It is likely due to encryption. TWRP seems to have trouble decrypting after flashing different ROMs. You might be able to restore a backup if you sideload the same ROM as the one on the backup, flash TWRP, then restore the nandroid.
Decrypting your phone will make it much easier to jump between different ROMs frequently, at the cost of security of course..
Click to expand...
Click to collapse
Thanks for the response! How am I able to decrypt? It seems like most ROMs have forced encryption. Am I just a noob and am missing a setting in the ROM or recovery.
To respond to the person that was having the same problem...It will allow you to cancel out of the decryption password but that portion of the internal storage is then inaccessible it seems, which would include any backups you previously made. That's why I've literally had to format my phone when switching or restoring from backup. It sucks!
You are going to have to format your data partition (complete wipe of both /data and Internal Storage).
Afterwards, flash your ROM and either immediately root, or flash a custom kernel. Root or custom kernels will prevent OOS from encrypting the phone again on first boot.
While there's no way to save the data on your phone as decrypting mandates a wipe, you can store all of the data on your computer and move it back to the phone after decrypting by following this guide.
Since I never had a problem with an update in years, and I'm also a very stupid person, I didn't backup my data before my latest custom rom (Pixel Experience Plus) update.
I got the notification for the November security patch updates, and I downloaded the zip as usual. For the actual installation I usually reboot my Mi 9T Pro into TWRP, flash both the OS update and Magisk, etc. and reboot. Everything seemed to go smoothly as usual: TWRP asked me to input my unlock sequence, then the usual stuff. Problem is, when I tapped 'Reboot system', it didn't reboot normally: it went into Recovery mode again, and from that moment on there's been no way to do otherwise. But now TWRP doesn't ask me the unlock sequence anymore and looks like there's no way to access the data. I tried injecting the recovery from fastboot, I wiped everything except internal storage (I don't give a damn about the OS anymore at this point); I also tried to reinstall the same old rom from OTG after wiping System, but nothing. Whatever I do, it always boots up in Recovery, and it doesn't ask me the unlock sequence. I know my stuff is still there, it's just that the contents of sdcard aren't accessible and look like random alphanumeric sequences from the TWRP file manager. And yes, that's the whole point of encryption, but I was used to TWRP asking me to unlock/decrypt so in the worst case scenario I would be able to access my data and copy via OTG. But now, with the system unable to boot and the recovery not decrypting my stuff, I'm starting to losing hope. I'm sure here on XDA there are much smarter / knowledgeable people than me, and I hope somebody can help me find a way to break the cycle and return in possession of the data that I stupidly didn't backup.
Any help would be greatly appreciated!
Try reflashing the boot image. Failing that, you should be able to ADB sideload the update via TWRP.
V0latyle said:
Try reflashing the boot image. Failing that, you should be able to ADB sideload the update via TWRP.
Click to expand...
Click to collapse
I think I tried both. I say 'I think' since my knowledge could fail here.
I tried re-flashing the TWRP img from OTG, nothing changed.
I successfully sideloaded the OS through ADB, but I'm still stuck.
Should I try both? (In which order)?
Thanks a lot.