Database Users

help - can't enter TWRP anymore

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. Booting normally into the OS with the new password works fine, just not for TWRP.
TL;DR: Changed password in Cyanogenmod on encrypted 6P, 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 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. Booting normally into the OS with the new password works fine, just not for TWRP.
TL;DR: Changed password in Cyanogenmod on encrypted 6P, 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
Flashing the recovery even 'n' number of times won't do any bad to the ROM. It seems like an issue with decryption itself. If you don't bother backing up and restoring your data, I would advise you to decrypt the complete partition manually.

DJBhardwaj said:
Flashing the recovery even 'n' number of times won't do any bad to the ROM. It seems like an issue with decryption itself. If you don't bother backing up and restoring your data, I would advise you to decrypt the complete partition manually.
Click to expand...
Click to collapse
How can I decrypt it? And normally I backup a nandroid, but I can't do that now because I can't enter the recovery, or is there another way?

jb91 said:
How can I decrypt it? And normally I backup a nandroid, but I can't do that now because I can't enter the recovery, or is there another way?
Click to expand...
Click to collapse
The process will not wipe the ROM, but all the apps and data. Since your data is encrypted, I am not sure if Nandroid will work, backing up the /data partition. You can give a try to Flashfire app, to backup your parition data though.
---------- Post added at 10:29 PM ---------- Previous post was at 10:27 PM ----------
About decryption, you can reboot into bootloader, and enter the following commands consecutively.
Code:
fastboot format userdata
fastboot reboot

jb91 said:
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. Booting normally into the OS with the new password works fine, just not for TWRP.
TL;DR: Changed password in Cyanogenmod on encrypted 6P, 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
What version of TWRP are you using? There is an issue with decryption on version 3.0.1-0. See here: http://forum.xda-developers.com/nex...y-twrp-2-8-7-0-touch-recovery-t3234976/page83
Solution seems to be use the previous version 3.0.0-1.

garrettsessions said:
What version of TWRP are you using? There is an issue with decryption on version 3.0.1-0. See here: http://forum.xda-developers.com/nex...y-twrp-2-8-7-0-touch-recovery-t3234976/page83
Solution seems to be use the previous version 3.0.0-1.
Click to expand...
Click to collapse
Holy ****, I actually did update to the latest TWRP the other day. If this will be this simple to fix, that would be really great. I'm not sure how to flash the older TWRP now though. I used to always just download the TWRP img file on my phone directly, then install it directly within TWRP itself, to update TWRP. Now that I can't enter TWRP because it's unable to decrypt, I have no idea how to flash the old TWRP version. Is there an adb command so I can flash this from my PC?
EDIT: It worked! Thank you so much! I downgraded to the TWRP 3.0.0.1 with ADB and it decrypted again without any problems. You possibly spared me hours of setting up everything from scratch again.

jb91 said:
Holy ****, I actually did update to the latest TWRP the other day. If this will be this simple to fix, that would be really great. I'm not sure how to flash the older TWRP now though. I used to always just download the TWRP img file on my phone directly, then install it directly within TWRP itself, to update TWRP. Now that I can't enter TWRP because it's unable to decrypt, I have no idea how to flash the old TWRP version. Is there an adb command so I can flash this from my PC?
Click to expand...
Click to collapse
Fastboot is used to flash/modify partitions on Android devices.
Have a look at this thread: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

jb91 said:
Holy ****, I actually did update to the latest TWRP the other day. If this will be this simple to fix, that would be really great. I'm not sure how to flash the older TWRP now though. I used to always just download the TWRP img file on my phone directly, then install it directly within TWRP itself, to update TWRP. Now that I can't enter TWRP because it's unable to decrypt, I have no idea how to flash the old TWRP version. Is there an adb command so I can flash this from my PC?
Click to expand...
Click to collapse
If you are rooted, download the 3.0.0-1 version and flash with Flashfire or Flashify. I'm sure there's an adb command, but I always install through fastboot.

TWRP can not decrypt system partition on an encrypted Oneplus 2, Oxygen OS 3.0.1.

Heya,
I decided to nuke my beloved OP2 and start anew, this time including encryption. As I read in the encryption Q&A, the device should not be rooted when doing the encryption, as this can cause havoc.
If you want, you can skip the Italic part. Lets just say, all went well until I rebooted into recovery after setting my encryption password.
- I wiped everything, installed Oxygen OS 3.0.1, flashed the TWRP recovery image (which was recommended in the "how to install oxy 3 on OP2" guide. So it should be a compatible version).
- I boot up my phone and go to the android security settings. I put my phone on the charger and let it encrypt my system with the on-board encryption function. Everything goes well, device reboots fine, now encrypted.
- I went to the security settings again to set my password. I check "ask this password before booting". Now that the encryption is dealt with, I want to have my device rooted. I boot up into TWRP and, as expected, TWRP asks for the password that I just configured.
BUT TWRP won't accept my password, telling me it was wrong. I tried several times, checked that I didn't mess it up because of a foreign language (english) keyboard. When I rebooted the device, it accepted my password on the first try, booting normally afterwards.
I went into the security settings and chose a pattern instead of a password, to make sure the keyboard wasn't the cause of the failure. When booting into TWRP, it asks about my pattern now. But it doesn't accept it.
So I went back into the security settings and unchecked the "ask pattern before boot" part, hoping that TWRP might not need the pattern anymore. When I boot into TWRP now, it asks for a password again, although I have enabled a pattern only.
I rooted my devices several times already, without any problems. This is the first time that I use encryption, so I have no Idea what could be the cause of this problem. It just seems that TWRP has problems decrypting the OxyOs. Please keep in mind that I used the TWRP image that was recommended for OxyOS 3.0.1 in the official Oneplus Forum install guide, so it should be compatible with all the Software and Hardware.
Now that I can't access anything with my TWRP, I haven't installed my SuperSU yet. I can't see how I can gain root access without using TWRP. If I rooted the device first and then encrypted it, the TWRP problem would not matter, but that's exactly the thing that causes HAVOC.
Looking forward to ideas
Fennec
Edit: My progress:
- tried adb sideload the supersu.zip over the stock recovery (update from usb). Protocol error. Installation failed.
- tried all kinds of TWRP versions, starting at the newest 3.0.2. TWRP 3.0.2 claims to have solved the encryption issue, but when flashed I get a bootloop whenever I try to enter the recovery.
- I realized that my adb sideload failed because I used an old version of adb which I found on my laptop. The newest version managed to sideload the supersu and the xposed framework, giving me root rights. TWRP still does not work but at least I got root now :/

same: TWRP can not decrypt system partition on One Plus One, CM-13 and TWRP 3.0.2-0
I remember TWRP said: installation was not successful although it can boot into recovery...

Try fastboot official twrp-3.0.2-2 for me is working fine.
Remember to boot in recovery after flash
Sent from my ONE A2005 using Tapatalk

TWRP Encryption password

Hey guys,
I recently flashed to cm13 from the Android N Developer Preview and I formatted the userdata partition in order to decrypt the phone afterwards so TWRP could access /data but each time I boot up it's reencrypted. Any thoughts? I can't use TWRP at all to install zips or anything like that while the device is encrypted - it requires a password to decrypt /data. I've tried default_password, my pin, and rebooting before setting a password and none have worked. Please help I'm slowly dying without xposed. Also I'm not coming straight from the Android N Preview; I downgraded to M in order to get the right vendor image via the OTA update because when I tried to flash cm straight from the preview I got in a boot loop due to not having the right vendor.img if that makes any difference.
Alex

touchmywillis said:
Hey guys,
I recently flashed to cm13 from the Android N Developer Preview and I formatted the userdata partition in order to decrypt the phone afterwards so TWRP could access /data but each time I boot up it's reencrypted. Any thoughts? I can't use TWRP at all to install zips or anything like that while the device is encrypted - it requires a password to decrypt /data. I've tried default_password, my pin, and rebooting before setting a password and none have worked. Please help I'm slowly dying without xposed. Also I'm not coming straight from the Android N Preview; I downgraded to M in order to get the right vendor image via the OTA update because when I tried to flash cm straight from the preview I got in a boot loop due to not having the right vendor.img if that makes any difference.
Alex
Click to expand...
Click to collapse
You have to flash a modified boot img. The official one automatically encrypts your phone.

Where would I find one? I found one but it just put me in a boot loop. Is there a thread for that on here or any good places you know of?

If flashing zips is the only thing you are concerned about you could give flash fire a try. It worked great for me to flash some zips in nougat.

Android 7.1.2 Encryption

Hi,
sorry if that question has been already answered, but I cannot find an clear answer
I need to encrypt my cell phone, however each time I try I get an error telling that the encryption
did not finished correctly, and my cell phone is corrupteur and need to Factory reset
Is there a 7.1.2 Rom that exists with encryption working ?
if not do you know if a 6.x Rom exist that's support encryption.
Many thanks for your help.

I finely found a way to have ZUK Z1 encrypted under 7.1.2.
Below steps used:
Factory restore using All in One tool
Flash TWRP Official 3.0.2
Using TWRP installation of a 6.0 ROM
After boot and setup, enter Preference/Security/Encrypt
At this point ZUK Z1 appears encrypted
The issues are that under TWRP unable to mount or see files
I flashed lineage and open_gapps using the “adb sideload” option.
After a reboot, ZUK Z1 appears as encrypted
For the time being all is working fine, except the fact that TWRP cannot mount the device, because it’s encrypted. I guess that’s an issue with TWRP itself. I don’t know if a version exists to fix this ….

I tried to do it same way with several 6.0 ROMs still available here (a lot of dead links...) but each try using device encryption ends with an
automatic reboot and back to welcome screen without encryption.
At the moment I am using TWRP 3.1.0 (comming fomr 3.0.2) with 7.1.2 Nuclear ROM.
Any ideas? Device Encryption is important for me.

Ecoka said:
I tried to do it same way with several 6.0 ROMs still available here (a lot of dead links...) but each try using device encryption ends with an
automatic reboot and back to welcome screen without encryption.
At the moment I am using TWRP 3.1.0 (comming fomr 3.0.2) with 7.1.2 Nuclear ROM.
Any ideas? Device Encryption is important for me.
Click to expand...
Click to collapse
The 6.0 ROM that's worked for me was " Temasek-20160217-NIGHTLY-ham "
Make sure you fully factor restore using the All In One tool
boot your phone on V5 and setup your cell phone account
Then using TWRP install V6 ROM with the Temasek one.
then Encrypt your phone .... that's should work ok
then us "adb sideload" to inject the V7 Lineage ROM
Let me know at which step you are stuck !

Hey, sorry for long delay ...
It will work up to "Temasek-20160217-NIGHTLY-ham", flashing AOSP 4.6 (Android 7) by sideload will cause "Password wrong" problems while booting
decrypting data partition. Still hope to get a way working zu install AOSP 5.1 (Android 8.1) with full encryption. Tried TWRP 3.02 and newer 3..2.1.

no worry about "password", I already installed nightly build of Lineage without issues using sideload.
Of course I got the message about password, I just ignore it
the only point is that I had to install TWRP V2.8.7 and not 3.x. because with 3.x sometimes I was not able
to boot recovery mode.
Before each install I fully backup my cell phone in case of .... SMS, Pictures etc...
Good luck,

The problem is not the password while starting to recovery 3.x.x, its the password while booting...
1. Factory restore using All in One tool (okay, works)
2. Setup Phone and encrypt (works, okay - Password will be accepted)
3. Flash TWRP (3.02 / 3.2.1.0) - tried both (okay, works - Password for encryption Recovery will not be accepted
4. I skip that and sideload flash (clearing cache etc.) "Temasek-20160217-NIGHTLY-ham.zip" (okay, Recovery = not, While Booting = Password accepted) (I choosed PIN and something like : OfferMe#1963ZU several times)
5. I skip Password in Recovery and sideload flash (clearing cache) "lineage-14.1-20180124-nightly-ham-signed.zip" (okay, Recovery still not, While Booting = Password NOT accepted)
Seems no matter if Lineage ROM 14.1 or higher...
Still confused

I am not using password at boot. I only set a password to unlock the phone after boot.

How to root on stock 7.1.1 using Magisk

So I installed TWRP recovery using tuliptool and all that, but didn't bother with bootloader unlocking since it said it's not needed. So I tried to install Magisk using the instructions on their thread but after booting it asks me to reset my phone because the data got corrupted.
Luckily I had backed everything up beforehand, so I restored boot image and everything works fine again. Just wanted to know what I did wrong here. Did I miss any steps?

auxillium said:
So I installed TWRP recovery using tuliptool and all that, but didn't bother with bootloader unlocking since it said it's not needed. So I tried to install Magisk using the instructions on their thread but after booting it asks me to reset my phone because the data got corrupted.
Luckily I had backed everything up beforehand, so I restored boot image and everything works fine again. Just wanted to know what I did wrong here. Did I miss any steps?
Click to expand...
Click to collapse
You probably didn't miss anything if it's the "Your device is corrupt. It can’t be trusted and may not work properly” error, I get the same thing. You messed with the files in the boot partition so ZTE's "safety" features in the stock ROM automatically call them corrupted. I simply hit the power button and continue to boot, my device works fine (actually much better than before being rooted with Magisk). I'm the one who "corrupted" the phone on purpose, so I'm comfortable it's fine. If you're getting another message, I'm not entirely sure why. Maybe try ADB sideloading Magisk in TWRP, it's what "worked" for me.

marvelljones said:
You probably didn't miss anything if it's the "Your device is corrupt. It can’t be trusted and may not work properly” error, I get the same thing. You messed with the files in the boot partition so ZTE's "safety" features in the stock ROM automatically call them corrupted. I simply hit the power button and continue to boot, my device works fine (actually much better than before being rooted with Magisk). I'm the one who "corrupted" the phone on purpose, so I'm comfortable it's fine. If you're getting another message, I'm not entirely sure why. Maybe try ADB sideloading Magisk in TWRP, it's what "worked" for me.
Click to expand...
Click to collapse
What do you mean by "hitting the power button and continue to boot"? When I hit the power button on the "Decryption unsuccessful" screen it just locks and unlocks like normal, but stays there.

Ok I managed to install Magisk after factory reset, but after that my sdcard is not being recognized anymore (but is recognizable in TWRP). So I decided to restore the backup i had, and rebooted. But now I'm stuck on the ZTE logo during boot. I can still open TWRP, though. I've tried wiping system, data, and cache, then restoring the backup, also no good. For now I'm downloading the stock firmware and will try that. Any ideas on how I can fix this before I flash the stock firmware?
EDIT: Ok I managed to fix it by installing the no verity boot image instead. Boots again. I'll probably refrain from trying to root for now. Thanks for the help.

auxillium said:
Ok I managed to install Magisk after factory reset, but after that my sdcard is not being recognized anymore (but is recognizable in TWRP). So I decided to restore the backup i had, and rebooted. But now I'm stuck on the ZTE logo during boot. I can still open TWRP, though. I've tried wiping system, data, and cache, then restoring the backup, also no good. For now I'm downloading the stock firmware and will try that. Any ideas on how I can fix this before I flash the stock firmware?
EDIT: Ok I managed to fix it by installing the no verity boot image instead. Boots again. I'll probably refrain from trying to root for now. Thanks for the help.
Click to expand...
Click to collapse
Well, I wasn't much help, but it sounds like your overall problem was different than mine. My only advice is if you attempt to root with Magisk again, is to connect to your PC/Mac/etc with a cable, use the Advanced menu in TWRP, choose ADB sideload, and sideload Magisk from your PC/Mac/etc. You can find a more advanced explanations on various websites how to use ADB if you don't already know how. For some reason that worked for me and gave me full Magisk and phone functionality when nothing else did.

marvelljones said:
Well, I wasn't much help, but it sounds like your overall problem was different than mine. My only advice is if you attempt to root with Magisk again, is to connect to your PC/Mac/etc with a cable, use the Advanced menu in TWRP, choose ADB sideload, and sideload Magisk from your PC/Mac/etc. You can find a more advanced explanations on various websites how to use ADB if you don't already know how. For some reason that worked for me and gave me full Magisk and phone functionality when nothing else did.
Click to expand...
Click to collapse
Will this allow me to install magisk without a factory reset?

auxillium said:
Will this allow me to install magisk without a factory reset?
Click to expand...
Click to collapse
I didn't have to, but I can't guarantee it will work for you. I had previously factory reset my phone but at the time I sideloaded Magisk I had been using the phone for at least a week. Just make a backup of everything first to be safe. *edit* I am using the beta version of Magisk (16.4), not sure if that's making a difference.