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.
Related
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.
Hi all,
I had everything unlocked and running fine, TWRP was working and I was running 9.0 (OTA 25), and when booting to TWRP it would prompt me for my password and booting to either A or B I was able to see the contents of my Internal Storage from TWRP. I updated via TWRP to the 9.0.1 OTA 26 (Full, flashable zip). The update completed and booted fine. Fastbooted to TWRP, flashed blu_spark.
Now when I boot into the TWRP I flashed, it no longer asks for an encryption key. The A partition can see the SDCard without problems, but booting to the B slot sees gibberish. A slot boots fine, B slot is obviously dead.
What did I mess up here? Should I just be doing the incrementals? Guides seem to indicate I should do a full flash (not a Fastboot flash however). My XDA searching is not finding anything, but I may be looking for the wrong thing.
electroblood said:
Hi all,
I had everything unlocked and running fine...
Click to expand...
Click to collapse
I think I found it. Should have taken the lockscreen password off first before updating right? I have seen other people mention that.
That would seems strange to me since it doesnt 'decrypt' storage when you do that does it?
electroblood said:
I think I found it. Should have taken the lockscreen password off first before updating right? I have seen other people mention that.
That would seems strange to me since it doesnt 'decrypt' storage when you do that does it?
Click to expand...
Click to collapse
Yes this is what I do now every time (except when I forget). It's a known bug in TWRP afaik.
the black twrp should be able to decrypt from the fastboot img now, it might save you a format!
Changelog:
Fix boot.img not being able to decrypt
Click to expand...
Click to collapse
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
I didn't do any password or tried to do encryption for my data, because of that reason i cant see any files on twrp but i have no issues on booting into system, what i cant do is not able to backup files and i cant see any files if i look through twrp. How to get rid of this issues please
Maybe you set before a password when you firs setup the phone, but even if you remove it later, i think in the twrp it still needs it
use USB-C stick, save to it twrp instalation zip, in running twrp change storage source to USB, flash twrp from USB, then reboot to recovery
this happened to me after the last update
You can try to disable the password from the phone settings & then reboot in twrp, it won't ask for the password.
Sent from my ONEPLUS A6003 using Tapatalk
jabs said:
use USB-C stick, save to it twrp instalation zip, in running twrp change storage source to USB, flash twrp from USB, then reboot to recovery
this happened to me after the last update
Click to expand...
Click to collapse
i did same already .still not solved
sam180881 said:
You can try to disable the password from the phone settings & then reboot in twrp, it won't ask for the password.
Click to expand...
Click to collapse
i didnt use any password or lock screen
Chinaroad said:
Maybe you set before a password when you firs setup the phone, but even if you remove it later, i think in the twrp it still needs it
Click to expand...
Click to collapse
jabs said:
use USB-C stick, save to it twrp instalation zip, in running twrp change storage source to USB, flash twrp from USB, then reboot to recovery
this happened to me after the last update
Click to expand...
Click to collapse
sam180881 said:
You can try to disable the password from the phone settings & then reboot in twrp, it won't ask for the password.
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
Suppose if we swt password or lock screen the entire data on TWRP will Encrpted?
Yep
Chinaroad said:
Yep
Click to expand...
Click to collapse
Then what is benifit of flashing no-dm verity zip?
i never tried it, but as i know you need to flash that zip to decrypt the phone each time you flash a rom , not only one, ( that's what i know, and as i told you i never tried it)
@alwynjoshy
you need a new fresh TWRP installation, if you tried my procedure via USB-C and didn't work, install twrp * .img from your computer via fastboot procedure
Just boot into UI then remove any security options like face lock, fingerprint, pattern And pin.
jabs said:
@alwynjoshy
you need a new fresh TWRP installation, if you tried my procedure via USB-C and didn't work, install twrp * .img from your computer via fastboot procedure
Click to expand...
Click to collapse
Even after flashing dm verity zip am I able to use screenlock or pin without being effected of encryption
Have a nice day. I tried installing Pixel Experience. The installation went without any problems, the system is fast without any stuttering. Phone calls without problems, the problem is with the sound of the ringtone and the sound is distorted in games. And that's why I wanted to go back to the original EU-ROM from xiaomi. But there was a problem while recovering from TWRP. TWRP says cannot recover data from internal storage. I had TWRP set up fine. After rebooting into the system, TWRP is still loading me, I don't know what the problem is.
Benoni1 said:
Have a nice day. I tried installing Pixel Experience. The installation went without any problems, the system is fast without any stuttering. Phone calls without problems, the problem is with the sound of the ringtone and the sound is distorted in games. And that's why I wanted to go back to the original EU-ROM from xiaomi. But there was a problem while recovering from TWRP. TWRP says cannot recover data from internal storage. I had TWRP set up fine. After rebooting into the system, TWRP is still loading me, I don't know what the problem is.
Click to expand...
Click to collapse
You must have done something wrong.
Factory reset your phone with:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Don,t relock the bootloader.
NOSS8 said:
You must have done something wrong.
Factory reset your phone with:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Don,t relock the bootloader.
Click to expand...
Click to collapse
I did all this and did a clean install via MiFlash. But I was confused by the error after the flash, the red error field was lit on the right in MiFlash. But the ROM booted without any problems. After that I did a factory reset just to be sure. All ok, installing TWRP as well. However, in TWRP it shows me data without internal storage. This means it won't load on app refresh and nothing from internal storage. I don't know where the error really is.
Benoni1 said:
I did all this and did a clean install via MiFlash. But I was confused by the error after the flash, the red error field was lit on the right in MiFlash. But the ROM booted without any problems. After that I did a factory reset just to be sure. All ok, installing TWRP as well. However, in TWRP it shows me data without internal storage. This means it won't load on app refresh and nothing from internal storage. I don't know where the error really is.
Click to expand...
Click to collapse
The error is normal since you don't lock the bootloader.(mentioned in my tutorial)
It was useless to do a reset after Miflash had done it.
Details on which rom and TWRP?
NOSS8 said:
The error is normal since you don't lock the bootloader.(mentioned in my tutorial)
It was useless to do a reset after Miflash had done it.
Details on which rom and TWRP?
Click to expand...
Click to collapse
Cupid_eea_global_images_V13.0.24.0.SLCEUXM_20220927
TWRP-3.7.0_12-v6.5_A12-cupid-skkk.img
Benoni1 said:
Cupid_eea_global_images_V13.0.24.0.SLCEUXM_20220927
TWRP-3.7.0_12-v6.5_A12-cupid-skkk.img
Click to expand...
Click to collapse
No problem on that side.
Try security on the lock screen to see if TWRP asks you for the code to decrypt.
NOSS8 said:
No problem on that side.
Try security on the lock screen to see if TWRP asks you for the code to decrypt.
Click to expand...
Click to collapse
I'm already reinstalling everything including TWRP. Otherwise, TWRP never asked me for a decryption code, but in the phone settings it is written that it is encrypted. Apparently that's the mistake. I'm doing a clean install. If the mistake wasn't that I did a factory reset after installing the ROM.
Benoni1 said:
I'm already reinstalling everything including TWRP. Otherwise, TWRP never asked me for a decryption code, but in the phone settings it is written that it is encrypted. Apparently that's the mistake. I'm doing a clean install. If the mistake wasn't that I did a factory reset after installing the ROM.
Click to expand...
Click to collapse
Factory reset just erases your data.
After installing the TWRP, reboot on the twrp and do not put any security on the lock screen.
I just installed the ROM, in phone settings I see - phone encrypted. I did not provide any security.
Benoni1 said:
I just installed the ROM, in phone settings I see - phone encrypted. I did not provide any security.
Click to expand...
Click to collapse
Where do you see this?
in the settings I go to encryption and credentials and under that it says Phone encryption: encrypted
Benoni1 said:
in the settings I go to encryption and credentials and under that it says Phone encryption: encrypted
Click to expand...
Click to collapse
You can try:
TWRP
wipe/format data type yes(if errors ,red lines,reboot twrp ant try again).
reboot twrp
flash a recovery rom
check if still the same.
ok I will try
I did as you wrote no error in TWRP nothing red. After installing TWRP, it's a mystery that TWRP won't boot automatically, I have to boot it via hardware buttons. However, the phone still lights up encrypted in the ROM. It's interesting.
Which pixel rom do you flashed, i didnt find it
venezolano69 said:
Kterou pixelovou rom jsi flashoval, nenašel jsem to
Click to expand...
Click to collapse
Pixel Experience Plus 12.1 v416
Benoni1 said:
Pixel Experience Plus 12.1 v416
Click to expand...
Click to collapse
Is it a gsi rom?
venezolano69 said:
Je to gsi rom?
Click to expand...
Click to collapse
Releases · ponces/treble_build_pe
Script and patches for building PHH-Treble Pixel Experience - ponces/treble_build_pe
github.com
Thought, there still isn't any Custom Rom out for Xiaomi 12 atm, except unofficial Lineage.
Yes this is a big problem