Database Users

TWRP cannot decrypt after March security update

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!

Nougat recovery partition connected to the boot image?

I flashed the magisk uninstaller which puts the original stock boot image on. However doing this has also removed my twrp recovery (my phone is now on stock recovery image). Are the partitions now directly linked in nougat?
Sent from my Nexus 6P using XDA-Developers mobile app

Guitarboarder28 said:
I flashed the magisk uninstaller which puts the original stock boot image on. However doing this has also removed my twrp recovery (my phone is now on stock recovery image). Are the partitions now directly linked in nougat?
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
No. Nougat automatically overwrites your recovery. If you want TWRP, then you either need a modified boot image, or after you flash TWRP on stock boot image, immediately boot into recovery and root your phone with Super SU.

ultyrunner said:
No. Nougat automatically overwrites your recovery. If you want TWRP, then you either need a modified boot image, or after you flash TWRP on stock boot image, immediately boot into recovery and root your phone with Super SU.
Click to expand...
Click to collapse
Ah thank you!
Sent from my Nexus 6P using XDA-Developers mobile app

TWRP Stuck after upgrade to Nougat

Hello everyone,
i just flashed the newest Pure Nexus Rom and everything went fine.
I forgot to flash the SuperSU Zip so i tried to got back into TWRP, but now it stuck.
The System boots normally, only TWRP wont boot.
Anyone had that problem too?

if anyone else has the same issue, here is the answer:
I forgot to erase the userdata or cache.
If you have the same problem use fastboot!
fastboot format cache
fastboot format userdata
Then it should work again.
(Everything on your own risk)

If you dont flah SuperSU asap, TWRP will not stick on reboot (w nougat). That was the issue.

No SuperSU was not the problem.
It happened before i flashed the SuperSU zip.
As far as i know, there is a problem if you upgrade to Nougat and dont format the userdata and cache because of the encryption or sth like that.

kaufikauf said:
No SuperSU was not the problem.
It happened before i flashed the SuperSU zip.
As far as i know, there is a problem if you upgrade to Nougat and dont format the userdata and cache because of the encryption or sth like that.
Click to expand...
Click to collapse
Exactly. It happened before you flashed SuperSU zip. Not flashing SuperSU caused your problem. It needs to be flashed the first time you go into TWRP or you won't be able to boot back into TWRP. The previous poster is correct.

Maybe we talk about different problems
Ive formatted cache and userdata yesterday,
now i can go back into twrp.
(SuperSU is not flashed now).
Just tried it, works perfectly!

kaufikauf said:
No SuperSU was not the problem.
It happened before i flashed the SuperSU zip.
As far as i know, there is a problem if you upgrade to Nougat and dont format the userdata and cache because of the encryption or sth like that.
Click to expand...
Click to collapse
I never, ever flash userdata, and never had an issue.
We can agree to disagree. Either the other poster and I arent understanding your question, or you arent understanding our reply. It's cool, it happens.
But TWRP not sticking is due to not running SuperSU at the end of the install process. It wont stick.

And now i know the misunderstanding!
My sentence was a little bit silly formulated:
It didnt stuck by flashing SuperSU. I just forgot to do that and when i recognized this, i want to boot into recovery. Then i recognized the bootloop.
So SuperSU as itself was not involved. By the way BeansTown wrote in the Thread for PureNexus Rom that you have to format your userdata (normally over TWRP).
Shame on me that i didnt read before start flashing

kaufikauf said:
And now i know the misunderstanding!
My sentence was a little bit silly formulated:
It didnt stuck by flashing SuperSU. I just forgot to do that and when i recognized this, i want to boot into recovery. Then i recognized the bootloop.
So SuperSU as itself was not involved. By the way BeansTown wrote in the Thread for PureNexus Rom that you have to format your userdata (normally over TWRP).
Shame on me that i didnt read before start flashing
Click to expand...
Click to collapse
You should take a look at this post in the official TWRP thread for a clearer reason why.

SlimSnoopOS said:
You should take a look at this post in the official TWRP thread for a clearer reason why.
Click to expand...
Click to collapse
So I followed the guide and updated to 7.1.1 and did the normal "fastboot flash recovery xxx" then "fastboot reboot bootlader" then rebooted it via phone I go to "Recovery" from my phone and I get a screen saying "No Command" I tried to flash twrp-3.0.3-0-angler.img
Did I miss something?

USFguy said:
So I followed the guide and updated to 7.1.1 and did the normal "fastboot flash recovery xxx" then "fastboot reboot bootlader" then rebooted it via phone I go to "Recovery" from my phone and I get a screen saying "No Command" I tried to flash twrp-3.0.3-0-angler.img
Did I miss something?
Click to expand...
Click to collapse
After flashing TWRP from the bootloader, go directly into recovery and flash SuperSU 2.78 or newer to make it stick permanently.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
After flashing TWRP from the bootloader, go directly into recovery and flash SuperSU 2.78 or newer to make it stick permanently.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
It won't boot into recovery, I flash recovery, unplug device hit recovery boot and it boot loops once then boots normally....

USFguy said:
It won't boot into recovery, I flash recovery, unplug device hit recovery boot and it boot loops once then boots normally....
Click to expand...
Click to collapse
Hmm. If you are on stock, reflash the boot, system, recovery, and vendor from the factory image that matches your stock, security update. Restart the phone and boot into Android. Restart into the bootloader then fastboot flash recovery TWRP-angler.img. See if it lets you boot into TWRP then. If not, try an older version of TWRP and see if that will flash and allow you to boot into it.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Hmm. If you are on stock, reflash the boot, system, recovery, and vendor from the factory image that matches your stock, security update. Restart the phone and boot into Android. Restart into the bootloader then fastboot flash recovery TWRP-angler.img. See if it lets you boot into TWRP then. If not, try an older version of TWRP and see if that will flash and allow you to boot into it.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Tried that, ended up going down an update in TWRP and it worked, weird....

I had a similar issue and I had to go back in and reflash Recovery image to recovery partition and all was well

Pixel XL will not boot after TWRP mishap

Already been unlocked and running pure nexus for a while, during flashing paranoid android I ran into some trouble and tried to reboot into TWRP, it did not load into TWRP because I forgot to flash the recovery again the last time before rebooting, no biggie.
I fastboot boot TWRP.img from my PC and then flashed rc2 zip from my internal storage, restore my backup and reboot. No luck, I get sent right back to TWRP every time and it never ask me to decrypt my partition.
So now I'm stuck with and encrytpted partition that I can't access, and even trying to fastboot boot TWRP and then flash rc2 from OTG is not fixing the issue, sends me right back to TWRP without decrypt prompt no mater if I choose power off, reboot, bootloader.
I can get to boot loader running adb bootloader from cli.
I'm not sure what to do from here, am I really bricked?
Any help is really appreciated.
Thank you.

Just try to flash TWRP, reboot recovery only, then go to wipe, advanced, and format internal storage, wipe everything once more and restore and boot your nandroid. RC2 has issues with restoring nandroid by the way, use RC1. You probably just have corrupt storage.

It's not possible to fastboot boot twrp and install twrp when you are not on stock boot on both slots. This will always leeds you to a twrp bootloop.
Just fastboot stock boot to slot a and b and then install twrp again and you should be fine.

mikaole said:
It's not possible to fastboot boot twrp and install twrp when you are not on stock boot on both slots. This will always leeds you to a twrp bootloop.
Just fastboot stock boot to slot a and b and then install twrp again and you should be fine.
Click to expand...
Click to collapse
I just did the same darn thing. I was trying to flash PN July update and I always knock it out no problem. However, for some reason, I rebooted right after flashing the July PN and forgot to reflash twrp. I'm rebooted into the ROM, but how do I get twrp recovery back on the device?

whodatfan said:
I just did the same darn thing. I was trying to flash PN July update and I always knock it out no problem. However, for some reason, I rebooted right after flashing the July PN and forgot to reflash twrp. I'm rebooted into the ROM, but how do I get twrp recovery back on the device?
Click to expand...
Click to collapse
The same way you got it on there the first time....

I booted RC1 and flashed RC2. I mistyped fastboot an it failed first go. Lol
Sent from my Pixel XL using Tapatalk

boostedduece said:
Already been unlocked and running pure nexus for a while, during flashing paranoid android I ran into some trouble and tried to reboot into TWRP, it did not load into TWRP because I forgot to flash the recovery again the last time before rebooting, no biggie.
I fastboot boot TWRP.img from my PC and then flashed rc2 zip from my internal storage, restore my backup and reboot. No luck, I get sent right back to TWRP every time and it never ask me to decrypt my partition.
So now I'm stuck with and encrytpted partition that I can't access, and even trying to fastboot boot TWRP and then flash rc2 from OTG is not fixing the issue, sends me right back to TWRP without decrypt prompt no mater if I choose power off, reboot, bootloader.
I can get to boot loader running adb bootloader from cli.
I'm not sure what to do from here, am I really bricked?
Any help is really appreciated.
Thank you.
Click to expand...
Click to collapse
Just flash a factory image and start over.

[How-To] Restore OOS from Oreo 8.1 | Restore factory encryption | Re-lock bootloader

You need to do this if you've flashed an Oreo 8.1 ROM and find that you can't get back to OOS because...
The ROM can't read /data so it hangs on the boot animation or reboots to recovery, even on a clean flash.
TWRP won't recognize your PIN/password or "default_password".
You've tried re-formatting /data from TWRP several times and it doesn't solve your problem.
Here is how to get back to 100% stock and/or restore factory encryption, which is different than Oreo 8.1 encryption:
1. Back up /sdcard to your PC as it will be erased with all of your files, pictures, music, etc.
2. Flash the stock recovery from bootloader.
Code:
fastboot flash recovery [I]stock_recovery.img[/I]
Latest OOS official stock recovery
Latest OOS beta stock recovery
3. Restore system setting in recovery.
This step is necessary to restore factory formatting and encryption of /data.
If a password/PIN is set, click “I forgot my password.”
Boot into stock recovery. Once there, go to Wipe data and cache > Reset system setting and Erase everything(Music, pics, etc.).
Note: If you don't do the "Erase everything..." option, factory encryption will not be reset.
4. Boot TWRP from bootloader.
You could flash TWRP and reboot to recovery, but TWRP will get overwritten with the stock recovery when OOS boots anyway. It's faster just to boot TWRP from a command prompt. Use the command:
Code:
fastboot boot [I]twrp-recovery.img[/I]
I recommend using using:
[RECOVERY][dumpling] TWRP 3.2.1-0 for Oreo (8.0 and 8.1) by codeworkx
5. While in TWRP, move “OOS...ROM.zip” to the SD card.
In Windows File Explorer, copy OOS...ROM.zip to the device.
Alternately, you may use the following ADB command from a command prompt
Code:
adb push [I]OOS...ROM.zip[/I] /sdcard/
Since OOS is a very large file (1.6GB), this will take 5-10 minutes.
Latest OOS signed flashable zip
Latest OOS beta (Oreo) flashable zip
6. Flash OOS...ROM.zip from TWRP.
7. Reboot system.
Your device will be formatted, encrypted and loaded with the stock recovery and ROM as it came from the factory. You may need to find the OOS...ROM.zip you pushed to /sdcard and delete it from emulated storage (/storage/emulated) if you don't see it at /sdcard after booting the ROM.
8. Optional: To re-lock your your bootloader, follow these additional steps:
This can only be done from a factory-supplied OOS ROM (including Oreo) with no modifications or the phone will not boot!
Enable USB debugging under Developer options.
Reboot to bootloader.
Unlock the bootloader with the following command:
Code:
fastboot oem lock
Return to Developer options and turn off "OEM unlocking"

Thank you for the write up .. nicely done :good:
Sent from my OnePlus5T using XDA Labs

It gave me an error 1 in TWRP. I had to do the following:
1) Make sure the bootloader remains unlocked
2) Back your apps up in TitaniumBackup
3) Back your /sdcard partition up on your computer so you don't lose anything
4) Reflash stock recovery in the bootloader
5) Boot into stock recovery and hit "forgot password" when it asks for your lock code
6) Boot back into bootloader and reflash TWRP
7) Place stock OOS zip onto the /sdcard partition
8) While you're in TWRP, flash stock recovery through its image flasher then reboot into recovery
9) Flash stock OOS, reboot, and then mod however you want
Click to expand...
Click to collapse

blackknightavalon said:
It gave me an error 1 in TWRP. I had to do the following:
Click to expand...
Click to collapse
Will in 9th last step restoring from nandroid OB-1 work ?
It should I guess
Sent from my ONEPLUS A5010 using Tapatalk

Bump!
I made a big update to the OP today with more explanation, more detail and download links.

Thanks buddy, that tutorial worked perfectly!

The other way is to flash rollback image to Nougat in stock recovery.
https://goo.gl/YRyrt6

there are no other ways to revert back to stock OOS without affecting internal sd /sdcard ?
thanks for the guide above.

Ok I'm a bit Rusty. Flash from bootloader? Meaning adb? Then adb TWRP then boot to TWRP then flash stock room(s)?

Ippolito1971 said:
Ok I'm a bit Rusty. Flash from bootloader? Meaning adb? Then adb TWRP then boot to TWRP then flash stock room(s)?
Click to expand...
Click to collapse
Please do not quote the whole OP just to get someone's attention. A mention (@the Doctor) would suffice.
To answer your question, flash the stock recovery with the fastboot command:
Code:
fastboot flash recovery [I]stock_recovery.img[/I]
The only ADB command involved is "push" to get the ROM onto the sdcard in step 5.

Thx @the Doctor. My apologies.

Thanks for the writeup, I'll probably try soon and report back.

Thanks for this, may need it. Plan to flash DU 8.1 tomorrow. So you can't just restore an ob1 or ob2 nandroid from a custom ROM?

tcat007 said:
Thanks for this, may need it. Plan to flash DU 8.1 tomorrow. So you can't just restore an ob1 or ob2 nandroid from a custom ROM?
Click to expand...
Click to collapse
You can, but TWRP will not recognize your PIN or password while in OOS, so you'll have to set lockscreen security to none or swipe. Or you could do the procedure in the OP, then restore only data from your nandroid. You'll have to re-flash Magisk or any other mods after that.

I don't use a pin for backups or restores. Since I seem to have to format internal storage to get a custom ROM to boot, was just wondering if restore of oos nandroid works once on DU.
Sent from my OnePlus5T using XDA Labs

hello thanks for the guide just did this when i boot i cant connect to any wifi network thanks

How can I get my wifi back after reverting to 4.7.6? Ive tried EFS backup and everything possible but the only way to get wifi back is to flash an Oreo zip.

forty9er said:
hello thanks for the guide just did this when i boot i cant connect to any wifi network thanks
Click to expand...
Click to collapse
Did you restore to 4.7.6 or Oreo Beta 1/2?
Dazed No More said:
How can I get my wifi back after reverting to 4.7.6? Ive tried EFS backup and everything possible but the only way to get wifi back is to flash an Oreo zip.
Click to expand...
Click to collapse
Have you flashed OOS Oreo Beta? My theory is that the firmware won't downgrade back to OOS 4.7.6, but I'm not sure. I've only restored back to OOS OB1/2, and wifi has worked perfectly every time.

the Doctor said:
Did you restore to 4.7.6 or Oreo Beta 1/2?
Have you flashed OOS Oreo Beta? My theory is that the firmware won't downgrade back to OOS 4.7.6, but I'm not sure. I've only restored back to OOS OB1/2, and wifi has worked perfectly every time.
Click to expand...
Click to collapse
Flashing Oreo beta is the only way to get it back as myself and others have found in the thread that was started on the subject. I hadn't seen that initially when I posted in here.
I was hopeful that following your method to a T would get me my wifi back on 4.7.6 but it wasn't meant to be. Absolutely nothing I have tried in the last 24 hours has worked to get it working on 4.7.6 including multiple clean and dirty flashes of the full 4.7.6 zip, twrp, stock recovery, restoring multiple backups, restoring EFS, factory reset, wipes, etc.
You might want to add that to the OP that if you revert to 4.7.6 that wifi will not work.

Dazed No More said:
You might want to add that to the OP that if you revert to 4.7.6 that wifi will not work.
Click to expand...
Click to collapse
Thank you, and done. :good: