Related
Hello, for the first time I used Flashfire to update my phone to the latest security update. This did install the system properly, but now if I try to boot into TWRP it will ask for my password to decrypt. I have tried entering both my Google password and my PIN key and neither are accepted. I have also tried changing my PIN key in the Android system settings but this still does not allow TWRP to decrypt my data. Am I missing something?
Same issue! I don't want to factory reset....
Edit: For now, I just flashed my kernel and SuperSU through the USB-OTG feature in TWRP... Fine for the moment.
Having the same issue as well. I updated to MHC19I through fastboot and everything went well. Installed TWRP 3.0.0 and it installed without any problems, but when I attempted to decrypt with my pattern it doesn't work. Booting to Android after decrypting it with the pattern works fine though. I wonder if this is just a TWRP issue?
I am having this same issue as well. However, I have noticed that whenever I boot into the system then try to go back into TWRP recovery it appears that the recovery is missing. The only way I have found to get back into recovery is to re-flash through fastboot.
dkflint723 said:
I am having this same issue as well. However, I have noticed that whenever I boot into the system then try to go back into TWRP recovery it appears that the recovery is missing. The only way I have found to get back into recovery is to re-flash through fastboot.
Click to expand...
Click to collapse
When you flash a boot and system image, if you dont root and patch it with SuperSU, the moment you reboot to android, it will replace recovery. Thats why after flashing is important to boot straight into TWRP, flash the SUperSU zip to patch and root and it wont revert it
But i am on the same boat... went to 19I version... saw the password message from TWRP... i even tried back 29V and took off security, reflashed 19I and still... So i figured it was TWRP needing update... So i flashed 29V and will wait a day or so
chaco81 said:
When you flash a boot and system image, if you dont root and patch it with SuperSU, the moment you reboot to android, it will replace recovery. Thats why after flashing is important to boot straight into TWRP, flash the SUperSU zip to patch and root and it wont revert it
But i am on the same boat... went to 19I version... saw the password message from TWRP... i even tried back 29V and took off security, reflashed 19I and still... So i figured it was TWRP needing update... So i flashed 29V and will wait a day or so
Click to expand...
Click to collapse
So, if you look over at the TWRP thread it is mentioned that it is possible to sideload SuperSU as well as kernels. I was able to do this just fine myself. I think TWRP just needs to be updated by the dev.
I can confirm I have Root access (Flashed SuperSU v2.68 zip) via OTG. Also flashed Xposed Framework v80 and ElementalX Kernel via the same method. I had to download v1.14 zip manually to my OTG as the auto flash method via ElementalX Kernel Manager saves the downloaded zip file to Data and TWRP has no access to it. Bit annoying
What's worse is that TWRP doesn't save any of its' own settings (Time Zone, Haptic Feedback, Display Brightness etc). Guessing this would've normally been saved on Data partition as well. So everytime you boot into recovery, its' like the first time you flashed TWRP Anyway, all working well now and I didn't have to wipe anything.
Confirmed that after the mhc19i TWRP can't decrypt.
adb sideloaded twrp again(for fun), supersu, francokernel v12.
Just getting a ton of app crashes now. Might need to format system and start over :-/
*edit* was able to transfer my /sdcard/ to computer while apps were crashing.
Rebooted to fastboot and did as follows
fastboot update -w image-angler-mhc19i.zip to format everything and start over.
fastboot flash recovery twrp-angler-3.0.0.0.img
reboot to recovery
Enable twrp to write to system
adb sideload franco kernel r12 and supersu
Now everything is decrypted (i have nothing to hide), I ahve root, I have kernel I want, and TWRP is happy because it doesnt' have to decrypt anything
I use WugFresh NRT to root my phone. I unrooted it this morning to get the OTA March update. Everything went fine until I tried to reroot. I can't get past the TWRP screen asking for a password. How can I reroot without TWRP or will this encryption problem always crop up? I do not want to factory reset.
Hey Guys, on Reddit a user suggested flashing the previous builds Vendor image. That should allow twrp decrypt.
flashcity90 said:
Hey Guys, on Reddit a user suggested flashing the previous builds Vendor image. That should allow twrp decrypt.
Click to expand...
Click to collapse
What if I'm already decrypted and using systemless root?
Sent from my Nexus 6P using Tapatalk
brianjking said:
What if I'm already decrypted and using systemless root?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
TWRP 3.0 works as normal if you are already decrypted. The issue, which is in the process of being resolved, only pertains to people using encryption.
Sent from my Nexus 5X using Tapatalk
TWRP 3.0.0-1 is out now. The issue is fixed. You can download from here: https://dl.twrp.me/angler/
Sent from my Nexus 6P using Tapatalk
dkflint723 said:
TWRP 3.0.0-1 is out now. The issue is fixed. You can download from here: https://dl.twrp.me/angler/
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Thanks for posting this info - saved me a headache updating CM today!
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.
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
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.
I'm on MIUI 12, I'm not able to install TWRP recovery properly.. internal storage is encrypted.. not able to flash anything. anyone has a solution ? thanks in advance !
Harshadd30 said:
I'm on MIUI 12, I'm not able to install TWRP recovery properly.. internal storage is encrypted.. not able to flash anything. anyone has a solution ? thanks in advance !
Click to expand...
Click to collapse
When, entering TWRP, it asks you for PIN/password.
You have to enter your pin/password you have defined in Android for unlocking the screen.
TWRP must then confirm that it successfully decrypted for user 0 (for user 999 it would fail, do not wory about)
This is really nothing new, but you must not use an outdated TWRP that does not ask or does not support it properly
If having problems, reboot to Android and reset your pin/password.
Some TWRP versions may not support properly if you use pattern in Android - hence better switch to pin.
However, if you cannot make it with pin, reboot again to Android, redefine to pattern and try
zgfg said:
When, entering TWRP, it asks you for PIN/password.
You have to enter your pin/password you have defined in Android for unlocking the screen.
TWRP must then confirm that it successfully decrypted for user 0 (for user 999 it would fail, do not wory about)
This is really nothing new, but you must not use an outdated TWRP that does not ask or does not support it properly
If having problems, reboot to Android and reset your pin/password.
Some TWRP versions may not support properly if you use pattern in Android - hence better switch to pin.
However, if you cannot make it with pin, reboot again to Android, redefine to pattern and try
Click to expand...
Click to collapse
i have tried, i swiped to allow modification but it does not asked for password, goes straight in recovery mode & i can not access my files from there, i also tried removing password completely to unlock phone but still got the same issue.. i have heard that files are encrypted on android 11, so i posted this question..
thank you
Harshadd30 said:
i have tried, i swiped to allow modification but it does not asked for password, goes straight in recovery mode & i can not access my files from there, i also tried removing password completely to unlock phone but still got the same issue.. i have heard that files are encrypted on android 11, so i posted this question..
thank you
Click to expand...
Click to collapse
Make sure you use the latest official TWRP for davinci
Which "notifications" - it's about Passwords and Security in Android. You can try by removing Android unlock pin/pass, reboot to Android and set it again and then try with TWRP.
Again, make sure you use up-to-date TWRP, best the official
twrp-3.5.2_9-0-davinci.img (if you were not familiar with and TWRP does not ask, maybe you are on an ancient and maybe some unofficial TWRP)
HI, I updated to V12.1.4.0.RFJMIXM and tried to install the latest TWRP but booting into recovery mode TWRP is in this like read only mode and dosnt bring up the usual thing to decrypt your files. It says unmodified system partition. Keep system read only? TWRP can leave your system partition unmodified to make it easier for you to take official updates. TWRP will be unable to prevent the stock ROM from replacing TWRP and will not offer to root your device. Then it says keep read only or swipe to allow modifications. Any suggestions? Tried removing and adding security pin but didnt work
I need it to install magisk. I tried patching a recovery image with magisk which worked. But trying to boot to magisk with recovery dosnt work. I hold the keys and then when it vibrates let go but it always goes to stock recovery. Not system with magisk as it talks about.
Harshadd30 said:
i have tried, i swiped to allow modification but it does not asked for password, goes straight in recovery mode & i can not access my files from there, i also tried removing password completely to unlock phone but still got the same issue.. i have heard that files are encrypted on android 11, so i posted this question..
thank you
Click to expand...
Click to collapse
This seems like a bootloop. Did you change any roms before this happened? You might have to format (not wipe) your data partition which unfortunately will also delete all your files from the phone's internal storage.