Database Info

Lost root and TWRP recovery doesn't recognize my encryption PIN

While attempting to flash the latest unofficial MIUI build yesterday, I got stuck at the animation logo, so I gave up. Instead, I flashed the Android L developer build, which did boot up completely for me. However, when I attempted to boot back into recovery, I got prompted to enter my encryption passcode, which I did. However, TWRP keeps telling me that decryption failed and to try again. The issue isn't an incorrect passcode, so I'm at a loss to try to figure out what's going on. Also, because TWRP won't decrypt my storage, I can't flash anything (despite the fact that I'm able to access SD card files from a file manager app when the phone is on). Any way I can get TWRP to decrypt my storage without having to wipe everything completely? Has anyone else experienced this?

tattedupboy said:
While attempting to flash the latest unofficial MIUI build yesterday, I got stuck at the animation logo, so I gave up. Instead, I flashed the Android L developer build, which did boot up completely for me. However, when I attempted to boot back into recovery, I got prompted to enter my encryption passcode, which I did. However, TWRP keeps telling me that decryption failed and to try again. The issue isn't an incorrect passcode, so I'm at a loss to try to figure out what's going on. Also, because TWRP won't decrypt my storage, I can't flash anything (despite the fact that I'm able to access SD card files from a file manager app when the phone is on). Any way I can get TWRP to decrypt my storage without having to wipe everything completely? Has anyone else experienced this?
Click to expand...
Click to collapse
Reflash recovery

Lethargy said:
Reflash recovery
Click to expand...
Click to collapse
I can't without root access.

tattedupboy said:
I can't without root access.
Click to expand...
Click to collapse
Recovery is flashed in fastboot/bootloader...
Unless you used Towelroot, then you'll have to unlock the bootloader, which will wipe.

Really what I need is to figure out why TWRP isn't recognizing my encryption PIN. My storage is encrypted, but whenever I input my encryption PIN, I get an error message. How do I get it TWROP to recognize my encryption PIN?

Doesn't flashing L mess with your sdcard anyway?
Sent from my Nexus 5 using Tapatalk

tattedupboy said:
Really what I need is to figure out why TWRP isn't recognizing my encryption PIN. My storage is encrypted, but whenever I input my encryption PIN, I get an error message. How do I get it TWROP to recognize my encryption PIN?
Click to expand...
Click to collapse
Encryption always causes issues. I suggested to reflash TWRP with fastboot to rule out TWRP itself being the issue.

This is why I never encrypt. I just don't trust it.
Sent from my Nexus 5 using Tapatalk

rootSU said:
This is why I never encrypt. I just don't trust it.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
slightly running off topic but .. i have the same issues ... so i pushed twrp 2711 via adb .. now I did a factory reset .. still the request for the encryption password, and i cant seem to get rid of it.
Really frustrating, to the point where i want to smash my phone on the wall.
How can i get rid of it? im just confused,

Onecton said:
slightly running off topic but .. i have the same issues ... so i pushed twrp 2711 via adb .. now I did a factory reset .. still the request for the encryption password, and i cant seem to get rid of it.
Really frustrating, to the point where i want to smash my phone on the wall.
How can i get rid of it? im just confused,
Click to expand...
Click to collapse
Flash factory images lol

Lethargy said:
Flash factory images lol
Click to expand...
Click to collapse
hahaha, i nearly went ballistic on that thing yesterday ... i have no idea how i managed to get rid of it .. first i updated to 2.7.1.1. Twrp... Then i reflashed the Rom ...
Then i did a factory reset .. then i whiped data .. and reflashed rom .. anyways encryption is gone .. but i cant copy stuff from my pc to the handset well ... not that i care .. but kind of inconvenient

Was this resolved?
I am facing the same issue with the AOSP builds of L. I wanted to take new Nandroid backups and realized that TWRP cannot decrypt the partition.
tattedupboy said:
While attempting to flash the latest unofficial MIUI build yesterday, I got stuck at the animation logo, so I gave up. Instead, I flashed the Android L developer build, which did boot up completely for me. However, when I attempted to boot back into recovery, I got prompted to enter my encryption passcode, which I did. However, TWRP keeps telling me that decryption failed and to try again. The issue isn't an incorrect passcode, so I'm at a loss to try to figure out what's going on. Also, because TWRP won't decrypt my storage, I can't flash anything (despite the fact that I'm able to access SD card files from a file manager app when the phone is on). Any way I can get TWRP to decrypt my storage without having to wipe everything completely? Has anyone else experienced this?
Click to expand...
Click to collapse

nirudha said:
I am facing the same issue with the AOSP builds of L. I wanted to take new Nandroid backups and realized that TWRP cannot decrypt the partition.
Click to expand...
Click to collapse
No it cannot.

URGENT Google Pixel struck in bootloops, can't access recovery mode!

Ok so never mind i got into teamwin TWRP phew. But Alpha2 but isn't it suggested that you don't recover using twrp? I don't know what to DO.

silvernirvash said:
Ok so never mind i got into teamwin TWRP phew. But Alpha2 but isn't it suggested that you don't recover using twrp? I don't know what to DO.
Click to expand...
Click to collapse
Download TWRP RC1 and flash it with TWRP alpha. Then download PN and follow the flashing instructions OR use your PC to flash back to stock and start over.
Edit: if you've made a backup using TWRP alpha, you can try to restore it using TWRP alpha.

k.s.deviate said:
Download TWRP RC2 and flash it with TWRP alpha. Then download PN and follow the flashing instructions OR use your PC to flash back to stock and start over.
Edit: if you've made a backup using TWRP alpha, you can try to restore it using TWRP alpha.
Click to expand...
Click to collapse
I don't have ADB or USB debugging enabled on my device. I can't DO anything. And i go and mount my storage onto my PC it just shows a **** ton of folders with random letters and numbers. i can't copy any files onto the device nor will minimal ADB and fastboot work when i type adb devices to detect the device. i don't know what to do!

silvernirvash said:
I don't have ADB or USB debugging enabled on my device. I can't DO anything. And i go and mount my storage onto my PC it just shows a **** ton of folders with random letters and numbers. i can't copy any files onto the device nor will minimal ADB and fastboot work when i type adb devices to detect the device. i don't know what to do!
Click to expand...
Click to collapse
ADB debugging does not need to be enabled on the device. All fastboot commands will work when you're in bootloader.
The files/folders with random names are showing up because TWRP didn't decrypt properly, reboot TWRP until the files/folders show up properly on the device then the files will show up properly on your PC and enable you to transfer files.
What's the background here, were you running stock rooted or a custom ROM?

k.s.deviate said:
ADB debugging does not need to be enabled on the device. All fastboot commands will work when you're in bootloader.
The files/folders with random names are showing up because TWRP didn't decrypt properly, reboot TWRP until the files/folders show up properly on the device then the files will show up properly on your PC and enable you to transfer files.
What's the background here, were you running stock rooted or a custom ROM?
Click to expand...
Click to collapse
stock rooted with substratum installed. i had a substratum theme that worked for the most part perfectly fine but then i found orange kittens and the colored kittens addon to change the color to something i wanted people told me it would work just fine on the pixel 7.1 and when it rebooted BAM bootloop. i didn't have adb or usb debugging enabled when i did it and i wasn't thinking because i've done this kinda stuff in the past so i thought i'd be fine. but i guess i wans't.

k.s.deviate said:
ADB debugging does not need to be enabled on the device. All fastboot commands will work when you're in bootloader.
The files/folders with random names are showing up because TWRP didn't decrypt properly, reboot TWRP until the files/folders show up properly on the device then the files will show up properly on your PC and enable you to transfer files.
What's the background here, were you running stock rooted or a custom ROM?
Click to expand...
Click to collapse
I GOT ACCESS TO MY FILES AGAIN! I THINK I CAN MOVE STUFF OVER TO IT PERFECTLY NOW! Oh so could i just copy over the stock 7.1 zip flash it with twrp and i'll be set? or should i just flash the latest OTA update image? and whichever i have to do do i do it using the install option or do i do it using the advanced ADB sideload?

also what is PN? i'm confused by that one.

silvernirvash said:
stock rooted with substratum installed. i had a substratum theme that worked for the most part perfectly fine but then i found orange kittens and the colored kittens addon to change the color to something i wanted people told me it would work just fine on the pixel 7.1 and when it rebooted BAM bootloop. i didn't have adb or usb debugging enabled when i did it and i wasn't thinking because i've done this kinda stuff in the past so i thought i'd be fine. but i guess i wans't.
Click to expand...
Click to collapse
ok, bootloop form theme. After TWRP has successfully decrypted, this might take a few reboots.. Go to sd card, you will see a folder named Substratum, in there are two zip files, flash the SubstratumRescue_Legacy.zip then reboot.
IF that does not work, go back into TWRP and go to mount - system. back out and go to advanced - file manager navigate to /system/vendor/overlay and delete the entire folder. Ive done that only once on the Pixel, you might have to go to /system/system/vendor/overlay and delete the folder then reboot.

silvernirvash said:
I GOT ACCESS TO MY FILES AGAIN! I THINK I CAN MOVE STUFF OVER TO IT PERFECTLY NOW! Oh so could i just copy over the stock 7.1 zip flash it with twrp and i'll be set? or should i just flash the latest OTA update image? and whichever i have to do do i do it using the install option or do i do it using the advanced ADB sideload?
Click to expand...
Click to collapse
That is interesting, my first experience with the Pixel I had bought it close to when Best Buy was closing (they were offering the $10.00/month promotion) and the device had not finished updating. However, the person checking me out let me go before it had completely finished and said it "will finish the updates shortly and be usable". Well, i guess in his haste to get blackout drunk and attempt lame pick up lines, he did something wrong. After the update finished, The phone was stuck in a constant boot loop. My first experience with my beloved Pixel was a nightmare. Of course, I had it replaced with a new one in the store the next day, but it was very strange. I had not even got into the OS at all and it was stuck in this strange bootloop.
Glad your situation worked out, when I saw the title to this post my heart sunk a little bit because I certainly know the look.

silvernirvash said:
I GOT ACCESS TO MY FILES AGAIN! I THINK I CAN MOVE STUFF OVER TO IT PERFECTLY NOW! Oh so could i just copy over the stock 7.1 zip flash it with twrp and i'll be set? or should i just flash the latest OTA update image? and whichever i have to do do i do it using the install option or do i do it using the advanced ADB sideload?
Click to expand...
Click to collapse
No, just read my post and see if that works.

k.s.deviate said:
ok, bootloop form theme. After TWRP has successfully decrypted, this might take a few reboots.. Go to sd card, you will see a folder named Substratum, in there are two zip files, flash the SubstratumRescue_Legacy.zip then reboot.
IF that does not work, go back into TWRP and go to mount - system. back out and go to advanced - file manager navigate to /system/vendor/overlay and delete the entire folder. Ive done that only once on the Pixel, you might have to go to /system/system/vendor/overlay and delete the folder then reboot.
Click to expand...
Click to collapse
ZOMG it rebooted! i already did a restore so i have to set up my phone again in terms of apps and stuff but that's fine. but now it keeps saying android.process.acore keeps stopping. i'm assuming it has to do with the substratum theme and i guess that means i should just delete that folder huh?

silvernirvash said:
ZOMG it rebooted! i already did a restore so i have to set up my phone again in terms of apps and stuff but that's fine. but now it keeps saying android.process.acore keeps stopping. i'm assuming it has to do with the substratum theme and i guess that means i should just delete that folder huh?
Click to expand...
Click to collapse
How did you restore? I've never seen that process stop before.
It might be best to (since you have to set up your apps again) flash a factory image and start over.
---------- Post added at 05:02 AM ---------- Previous post was at 04:56 AM ----------
And if your going to be playing with themes.. PN is the way to go. PN is Pure Nexus rom. Follow the instructions word for word and you won't have any troubles. It is as stable as stock with some extra goodness baked in.

k.s.deviate said:
How did you restore? I've never seen that process stop before.
It might be best to (since you have to set up your apps again) flash a factory image and start over.
Click to expand...
Click to collapse
oh i did a quick cache and data wipe. it's what you're supposed to do when flashing new or updated roms in the first place. at the top right of TWRP it says wipe. i thought that would restore it back to default settings including substratum theme application but it seems all it did was set me back to stock settings with apps uninstalled lol. gotta set up my device again sadly. but now like i said now i keep getting this stupid android.process..acore keeps crashing error.
and i restored using the legacy zip you told me to use in the substratum folder using the install option at the top left.

Just hit the thanks button. ?

and by recovering i lost root....great....now i need to reroot.....damn it all =w=;;

k.s.deviate said:
Just hit the thanks button.
Click to expand...
Click to collapse
oh hey can i download and flash the latest version of android 7.1.1 manually using TWRP with out losing TWPR or my locked bootloader? just curious. i'm about to go back and reroot but i know updating to 7.1.1 = losing root and requiring me to root again after the fact which is why i'm holding off for NOW until i get an answer.

silvernirvash said:
oh hey can i download and flash the latest version of android 7.1.1 manually using TWRP with out losing TWPR or my locked bootloader? just curious. i'm about to go back and reroot but i know updating to 7.1.1 = losing root and requiring me to root again after the fact which is why i'm holding off for NOW until i get an answer.
Click to expand...
Click to collapse
No you can't flash factory images using TWRP, I would however highly suggest flashing the factory image to stop that crashing process.

k.s.deviate said:
No you can't flash factory images using TWRP, I would however highly suggest flashing the factory image to stop that crashing process.
Click to expand...
Click to collapse
so i gotta flash using minimal adb and fastboot huh? :/ damn lol. wouldn't that in turn remove TWRP tho? or am i mistaken on that one?

silvernirvash said:
so i gotta flash using minimal adb and fastboot huh? :/ damn lol. wouldn't that in turn remove TWRP tho? or am i mistaken on that one?
Click to expand...
Click to collapse
It would remove TWRP, but after the flash-all.bat is done.. set up your phone. Reboot to bootloader, fastboot boot TWRP install TWRP via zip and flash super su.
Then going forward to update every month, download the newest factory image, right click on the flash-all.bat click edit, scroll over and remove the -w. Then boot into bootloader and run the flash-all.bat, when it's done your still in bootloader, fastboot boot TWRP, flash TWRP zip and flash super su. Reboot.

k.s.deviate said:
It would remove TWRP, but after the flash-all.bat is done.. set up your phone. Reboot to bootloader, fastboot boot TWRP install TWRP via zip and flash super su.
Then going forward to update every month, download the newest factory image, right click on the flash-all.bat click edit, scroll over and remove the -w. Then boot into bootloader and run the flash-all.bat, when it's done your still in bootloader, fastboot boot TWRP, flash TWRP zip and flash super su. Reboot.
Click to expand...
Click to collapse
this would in fact wipe my phone every time i do it tho right? like EVERYTHING including music and photos and stuff right?

TWRP failed data decryption

I had TWRP 3.1.1.0 installed on my device and I upgraded to android 8.1 developer preview by dirty flashing via flashfire and after few days I tried rebooting into TWRP. TWRP was not there so I booted into TWRP using "fatboot boot recovery_file" command. TWRP prompted me to insert my pattern for data decryption but even when entering correct data decryption pattern, TWRP says I have entered incorrect pattern. I am able to boot into TWRP but my internal storage is encrypted and I cannot perfrom any action from TWRP.
Any solution guys?
Thanks

marmeak7 said:
I had TWRP 3.1.1.0 installed on my device and I upgraded to android 8.1 developer preview by dirty flashing via flashfire and after few days I tried rebooting into TWRP. TWRP was not there so I booted into TWRP using "fatboot boot recovery_file" command. TWRP prompted me to insert my pattern for data decryption but even when entering correct data decryption pattern, TWRP says I have entered incorrect pattern. I am able to boot into TWRP but my internal storage is encrypted and I cannot perfrom any action from TWRP.
Any solution guys?
Thanks
Click to expand...
Click to collapse
Wait for twrp team to update for compatability
Sent from my Google Pixel using XDA Labs

Sgace said:
Wait for twrp team to update for compatability
Click to expand...
Click to collapse
Is this a TWRP issue? Are you also facing similar problem?

marmeak7 said:
Is this a TWRP issue? Are you also facing similar problem?
Click to expand...
Click to collapse
Yes. It needs an update. Put whatever you want to install on a USB drive, use the adapter that came with your phone and plug it in. The switch storage in TWRP to USB OTG and install from there.

marmeak7 said:
Is this a TWRP issue? Are you also facing similar problem?
Click to expand...
Click to collapse
Yep, exactly like in the comment above.
Sent from my Galaxy Tab S2 8.0 using XDA Labs

I don't use screen lock nor a password or pin, works fine on 8.1 I have backed up and restored 3 times for testing purposes.
Sent from my Pixel using XDA-Developers Legacy app

I can confirm, google pixel (sailfish) with Oreo 8.1.0 , fastboot boot twrp-3.2.1-0-sailfish.img, decryption works now.

TWRP for OOS9.0.2

Hey there, I've tried installing the blu_spark TWRP, I've temporarily installed v9.86 .img file via fastboot, then tried flashing the zip for blu_spark TWRP, however every time I reboot into recovery it becomes the default OnePlus recovery. I don't get a "slide to allow system modifications" at the start, is that a problem? Thanks in advance!

If this can help, i fastbooted the Blu_Spark, flashed what i needed (magisk) and then flashed the official TWRP, i have the official now installed, not the Blu_Spark (i still prefer use the Blu_spark anyway for every official update, just in case)

Ok
Perfect
NeroNext said:
If this can help, i fastbooted the Blu_Spark, flashed what i needed (magisk) and then flashed the official TWRP, i have the official now installed, not the Blu_Spark (i still prefer use the Blu_spark anyway for every official update, just in case)
Click to expand...
Click to collapse

I have a big problem… On my op6 i have android pie version 9.0.2 ( the last one ) and already I have unlocked the bootloader but when i charge by fastboot mode any versions of twrp.img ( blu spark and the last one of enchilada, version 3.2.3 ) when I tap on "Install" go directly on sdcard and here I see many folders with strange name….like "oPgjjhFrhgh65bfgHg"... and there aren't the normal folder's names into sdcard… so I don't see also the zip file for install Twrp or Magisk...Can you help me please?

Fastboot to Recovery using the blu_spark Image. In twrp Flash the zip and the twrp should be still there after a reboot

unrated87 said:
Fastboot to Recovery using the blu_spark Image. In twrp Flash the zip and the twrp should be still there after a reboot
Click to expand...
Click to collapse
Thank you for your answer!! But the problem that I have is when I fastboot to recovery using The Blu Spark Image: when I have done this when i push on " Install " I can see only strange folders with strange names like " 0fjhsgegfjhjskhgf".... and I can not see the normal folders with the normal name into sdcard... How I said already I have the bootloader unlocked and I have the stock rom 9.0.2 on my op6.

data corrupted

more_than_hater said:
data corrupted
Click to expand...
Click to collapse
So, what I have to do?

Format data probably?

unrated87 said:
Format data probably?
Click to expand...
Click to collapse
Thank you unrated! I try and I say you. Only another little question : I format data by twrp, is it correct? and after I reboot without to reinstall the stock rom, is it correct?

scarface77 said:
Thank you for your answer!! But the problem that I have is when I fastboot to recovery using The Blu Spark Image: when I have done this when i push on " Install " I can see only strange folders with strange names like " 0fjhsgegfjhjskhgf".... and I can not see the normal folders with the normal name into sdcard... How I said already I have the bootloader unlocked and I have the stock rom 9.0.2 on my op6.
Click to expand...
Click to collapse
No data is corrupted. Before doing this remove any screen lock (pin or swipe) and your data will not show up as encrypted anymore. It is twrp bug afaik.

roel1976 said:
No data is corrupted. Before doing this remove any screen lock (pin or swipe) and your data will not show up as encrypted anymore. It is twrp bug afaik.
Click to expand...
Click to collapse
This night I try to root my op6 by fastboot TWRP without any pin or facelock or swipe ( without any kind of screen lock ) and if I solve my problem you'll become my hero!!!!!

roel1976 said:
No data is corrupted. Before doing this remove any screen lock (pin or swipe) and your data will not show up as encrypted anymore. It is twrp bug afaik.
Click to expand...
Click to collapse
Roel1976 you are my hero!!!! Thank you so much!!!!!! You have solved my problem!!! Thanks thanks thanks thanks…..I was going to be crazy because i tried many and many time to root my op6 reinstalling many and many time the stock rom pie and at last you arrived….and you solved my problem!!!
So there is a bug into the last versions of all TWRP, enchilada and blu spark: if we have a lock screen (PIN , Sequence, facial lock screen) into the sdcard of TWRP we see strange folder's names like "OFgsjdhdfkeiu564sflk"...
If we disable all lock screen (PIN, Sequence, facial lock…) and reboot in fastboot and load TWRP, how a kind of magic, we can see all folders with the normal name and all zip and .img that we have copied into!!!
So is not a data corrupted and so we have not to format data, but we have only to disable all kind of lock screen!!!
Roel 1976 thank you so much everywhere you are!!!

haha thanks mate, happy to be of assistance. I just found someone who suggests a solution to the encrypted data problem:
https://forum.xda-developers.com/showpost.php?p=78100903&postcount=3150

Boot to twrp gives me encrypted files

Hi guys,
I have a pretty weird problem.
I was running LineageOS 17.1, tried to go on 18.
Don't know what I screwed up but when I try to reboot to recovery as I do usually to flash, twrp boots but acts as if my files were encrypted.
I took care to remove pin lock before upgrade.
Weird thing is that when I boot twrp from fastboot, I can see my files.
My twrp is latest official 3.4.0-3
My system now can't boot (I think that it sees the data as encrypted also)
Would anyone know what's happening here ?

Try your lockscreen password.

outlawmodzz said:
Try your lockscreen password.
Click to expand...
Click to collapse
I'm not asked for a password, and I removed lockscreen before upgrade

Just bite the bullet and full wipe back to stock and try again.

outlawmodzz said:
Just bite the bullet and full wipe back to stock and try again.
Click to expand...
Click to collapse
That's what I made but I would have liked to know why so I can avoid it happening again

It happens sometimes could be anything.

was your device encrypted or decrypted before?

Cygnust said:
Hi guys,
I have a pretty weird problem.
I was running LineageOS 17.1, tried to go on 18.
Don't know what I screwed up but when I try to reboot to recovery as I do usually to flash, twrp boots but acts as if my files were encrypted.
I took care to remove pin lock before upgrade.
Weird thing is that when I boot twrp from fastboot, I can see my files.
My twrp is latest official 3.4.0-3
My system now can't boot (I think that it sees the data as encrypted also)
Would anyone know what's happening here ?
Click to expand...
Click to collapse
Have you solved it?
If you switch over to the other slot in twrp, is it different? My files appear encrypted on slot b (no password asked like with you) on slot a twrp asks for a password and all is fine and I can boot into my phone normally

pjotrski1000 said:
Have you solved it?
If you switch over to the other slot in twrp, is it different? My files appear encrypted on slot b (no password asked like with you) on slot a twrp asks for a password and all is fine and I can boot into my phone normally
Click to expand...
Click to collapse
No, I made a full reset with msm..

Cygnust said:
No, I made a full reset with msm..
Click to expand...
Click to collapse
Ok, thanks.
My slot B got messed up yesterday going from twrp-mauronofrio to the latest official twrp. Luckily slot A still readable, but not sure how to go forward