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!

Re-Encrypt?

So I just flashed DP5 and I have been out of the loop on DP stuff since I haven't used the others since the original. Anyways, I wanted root for a few reasons but I was unaware how hard it would be to install TWRP so I could flash SuperSU. I am sure there are easier ways than how I did it, but after wiping userdata 3 times tonight I'd like to avoid that again.
So I flashed DP5, I flashed TWRP, Stuck on TWRP splash screen
So then I flashed Marshmellow Vendor, still stuck on splash screen
So then I flashed the modified boot image, twrp and viola I got into TWRP, I installed SuperSU, re-loading my data as I type this.
My question, can I flash the stock boot.img to re-encrypt my device? Is there a way to do it? I don't think i'll need TWRP necessarily so I am ok if it doesn't work so long as I keep root.

Just go into Settings>Security and select "Encrypt phone", and follow the prompts. There's no need to flash another boot image. The one you have now just doesn't force encryption, it doesn't mean you can't encrypt if you want to encrypt.
Sent from my Nexus 6P using Tapatalk

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.

OP5 bootloop with every ROM

Hey fellas,
so I rooted my phone and tried to install some Magisk modules, but after rebooting it got stuck in the TWRP bootloop. So I flashed the Nandroid backup and it got stuck in the OOS boot animation. After that I tried reflashing OOS, but it didn't change anything, so I tried Lineage OS and now it won't even get past the Oneplus logo at the beginning and keeps restarting.
Thanks in advance
EDIT: when I flash the stock ROM through TWRP it installs normally, but then when I try to reboot it says there is no OS. So I flashed the stock OS to try adb sideload, but my pc says it cannot read the zip.
I also decrypted my phone through the OP5 Decrypt App, before the bootloop it worked for some time.
Of course I wiped everything before every action.

if you can bootup into recovery, try go into advanced and format data and system.
if you can't your last chance is using adb - flash a default rom.

Is it any different than wiping everything? Because it didn't do anything. I can access both twrp and fastboot so I guess it's not that bad

sounds like you went from unencrypted to an encrypted rom and your data is encrypted, or visa versa.

yep, it's vice versa, I used the OP5 Decrypt App after rooting. Is OP5 encrypted by default?

If you've tried the Android 8.0 Rom, just go to the official OP5 support site and download stock rom, flash it via ADB sideload if you can. (Don't forget to format data etc etc..) and restart from scratch.
Unlock BL if it's relock, then flash TWRP and go for a custom ROM. That's what I did, happened to me 2 days ago.f
EDIT : Oh you just flashed Magisk.. Well, try this anyway.

I tried flashing Lineage, but I can't install Oxygen

Ok, so apparently OOS boots up only after relocking the bootloader. And I had to make adb use more RAM to get sideload to work.

TWRP install impossible, phone doesn't make it past fastboot splash screen

Hey guys,
I just oem unlocked my new 6T and have access to the bootloader. As I try to install TWRP with
HTML:
fastboot boot imagename.img
my computer says that it pushes the image just fine, but my phone restarts and then never makes it past the fastboot splash screen instead of loading up TWRP.
I was following the fajita (6T) instructions from the lineage OS website.
The first time I did it it worked, but following the instructions on installing lineage and telling me to wipe and format data, both the recovery seems to be gone and i cannot fastboot boot into TWRP.
Can you help?

Seems the same with what i experienced. Have you tried installing a fastboot rom? I had my oneplus 6t bootlooped into fastboot mode even if i try to turn it off, it just boots back automatically to fastboot mode. Last resort was to flash a fastboot rom. That worked for me.

thalesian2020 said:
Hey guys,
I just oem unlocked my new 6T and have access to the bootloader. As I try to install TWRP with
HTML:
fastboot boot imagename.img
my computer says that it pushes the image just fine, but my phone restarts and then never makes it past the fastboot splash screen instead of loading up TWRP.
I was following the fajita (6T) instructions from the lineage OS website.
The first time I did it it worked, but following the instructions on installing lineage and telling me to wipe and format data, both the recovery seems to be gone and i cannot fastboot boot into TWRP.
Can you help?
Click to expand...
Click to collapse
What TWRP version are you trying to install?

jp0469 said:
What TWRP version are you trying to install?
Click to expand...
Click to collapse
I tried 3.3.1.1. and 3.2.3.0.

What you are describing, I'm going to assume you are trying to install Lineage 17. You can't install TWRP if you are going Android 10, at least that's the conclusion I've come to at this point in time. It will fail to boot or end up in crash dump mode every time you try and enter recovery if you are on a custom ROM. If you are on Android 9, it's not an issue. I believe it's OK stock as well, but I don't know haven't tried, haven't been stock in a long time.
For LOS 17, only boot the TWRP image, never boot to recovery, never run the TWRP installer. You will likely still have to format data.
I have a post here, from when I had a similar issue. (instructions)
You'll notice the OmniRom instructions don't mention installing TWRP, only booting it.
Once I was in your spot, I always went back to stock using the fastboot ROM, installed TWRP, updated (still using TWRP), then started over with my install.

Well no, i was actually trying to install Lineage 16, which is Android 9 I believe.
The problem for me is that I do not get to the point where TWRP opens after "fastboot boot"ing it. So I understand, I should use a fastboot stock ROM? Is there such a thing? Where would I find it? Or would it be an OnePlus Oxygen ROM that I can fastboot?

Quickest way to start over:
To get back straight your gonna need to access a Windows PC, and run the MSM tool. Make sure you install both OnePlus and Qualcomm drivers. ( Don't wait for Windows, just pre install the drivers) here are some links. Not my work. Please be sure to thank the developers for creating and hosting these tools ?
MSM Tool:
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
OnePlus Drivers:
https://androidfilehost.com/?fid=11410963190603879743
Qualcomm drivers:
https://androidfilehost.com/?fid=11410963190603879743

thalesian2020 said:
Well no, i was actually trying to install Lineage 16, which is Android 9 I believe.
The problem for me is that I do not get to the point where TWRP opens after "fastboot boot"ing it. So I understand, I should use a fastboot stock ROM? Is there such a thing? Where would I find it? Or would it be an OnePlus Oxygen ROM that I can fastboot?
Click to expand...
Click to collapse
Were you on Android 10 before (OOS)? That will do that. LOS 16 is Android 9 and should have no problems installing TWRP or booting to it.. For LOS 16 I'd go back to 9.0.17, then install LOS 6T.
I posted these LOS install instructions a long time ago for another user.
Remember the MSM Tool will relock your bootloader so if something goes wrong the MSM Tool is your only choice. That is why it is always the last thing I resort to.
Thread to get Fastboot stock Roms if you want to try that route first.

Hey guys,
thank you so much for all your help. I've managed to use mauronofrios workaround here on xda to put my phone in a 9.0.17 state again (no idea what i had originally), and this way i could fastboot the twrp image again. so that worked fine, but so far flashing lineage hasnt worked, for whatever reason it seems to boot into a lineageos kind of recovery only (which i didnt even know existed).
So i guess in terms of this thread the problem is solved. Thank you again!

thalesian2020 said:
Hey guys,
thank you so much for all your help. I've managed to use mauronofrios workaround here on xda to put my phone in a 9.0.17 state again (no idea what i had originally), and this way i could fastboot the twrp image again. so that worked fine, but so far flashing lineage hasnt worked, for whatever reason it seems to boot into a lineageos kind of recovery only (which i didnt even know existed).
So i guess in terms of this thread the problem is solved. Thank you again!
Click to expand...
Click to collapse
Did you see my Lineage install instructions above? LOS installs its on Recovery when you flash the ROM. When om Android 9, boot TWRP, flash the TWRP installer, reboot to Recovery, install LOS 16, flash the TWRP installer again (replaces the LOS recovery that was installed), reboot to Recovery, install gapps / magisk if desired, reboot.
Read my instructions post though, the first time install is different, as you need LOS on both slots. Updating is different as well, its much easier.
It should go smoothly.

OhioYJ said:
Did you see my Lineage install instructions above? LOS installs its on Recovery when you flash the ROM. When om Android 9, boot TWRP, flash the TWRP installer, reboot to Recovery, install LOS 16, flash the TWRP installer again (replaces the LOS recovery that was installed), reboot to Recovery, install gapps / magisk if desired, reboot.
Read my instructions post though, the first time install is different, as you need LOS on both slots. Updating is different as well, its much easier.
It should go smoothly.
Click to expand...
Click to collapse
Do I need to be on Android 9 Stock when I start that process? What I did was boot into TWRP, flash TWRP installer, reboot into recovery, then format and wipe ALL partitions (except USB), then reboot into recovery again and then flash LOS, flash TWRP, reboot into recovery, flash LOS, flash TWRP, reboot system. Still no luck...

thalesian2020 said:
Do I need to be on Android 9 Stock when I start that process? What I did was boot into TWRP, flash TWRP installer, reboot into recovery, then format and wipe ALL partitions (except USB), then reboot into recovery again and then flash LOS, flash TWRP, reboot into recovery, flash LOS, flash TWRP, reboot system. Still no luck...
Click to expand...
Click to collapse
Wiping, Dalvik / ART, System, and Vendor is generally a bad idea. You can do them in certain situations, this isn't one of those situations you should be wiping those though. Factory reset, means the slider on the main page of the wipe screen that says swipe to factory reset, format data is the button that says format data. Don't do anything extra. If you did, yeah I would go back to 9.0.17 using the fastboot rom again, that will put everything back on both slots.

like OhioYJ stated, don't use advanced wipe. re-run the msm tool. Then follow his instuctions. You shouldn't need to preform any manual data wiping. The process of flashing will do everything required. looks like you're almost there

Thanks guys. I will try it out and let you know.
Edit: So I finally managed to properly install LOS - OhioYJ, your instructions worked! I installed 9.0.17 and went from there without wiping any additional partitions.
One questions remains: in your instructions you mention that after installing LOS once, you can update LOS as normal and you mention doing it via the recovery with flashing TWRP or GAPPS later again. Is it possible to do the update via the normal update function of LOS as well? Or will that overwrite TWRP?
You guys are awesome. Thank you so much for your help!

I seem to be stuck on the fastboot screen as well. Being on a MAC, anytime i try to do something in fastboot it goes straight back to the fastboot screen. I Thought I was on Android 10.0 trying to install recovery for that lead to bootloop of fastboot, tried using the Pie recovery and same thing. I am open to suggestions.
Thanks.

OhioYJ said:
What you are describing, I'm going to assume you are trying to install Lineage 17. You can't install TWRP if you are going Android 10, at least that's the conclusion I've come to at this point in time. It will fail to boot or end up in crash dump mode every time you try and enter recovery if you are on a custom ROM. If you are on Android 9, it's not an issue. I believe it's OK stock as well, but I don't know haven't tried, haven't been stock in a long time.
For LOS 17, only boot the TWRP image, never boot to recovery, never run the TWRP installer. You will likely still have to format data.
I have a post here, from when I had a similar issue. (instructions)
You'll notice the OmniRom instructions don't mention installing TWRP, only booting it.
Once I was in your spot, I always went back to stock using the fastboot ROM, installed TWRP, updated (still using TWRP), then started over with my install.
Click to expand...
Click to collapse
Twrp is working fine with Android 10, using mauronofrio version and magisk 20.2

callumbr1 said:
Twrp is working fine with Android 10, using mauronofrio version and magisk 20.2
Click to expand...
Click to collapse
Yeah it starting to seem like it maybe isolated to Lineage. You cant install TWRP with LOS 17. Someone else mentioned in the Omni thread that it worked. This thread is about Lineage, but that should be clarified, or clearer.