I installed a custom rom, said rom gave me problems so I was going to revert back to old rom. I removed my fingerprint and pin from security and I rebooted to twrp. Twrp asks for a pin so I tried to put in the one I had before and it says password invalid and nothing is working. My old pin doesn't work, default_password doesn't work. Both slots are encrypted and I can't decrypt my internal storage to backup my files. Is there any work around I can do?
Zure said:
I installed a custom rom, said rom gave me problems so I was going to revert back to old rom. I removed my fingerprint and pin from security and I rebooted to twrp. Twrp asks for a pin so I tried to put in the one I had before and it says password invalid and nothing is working. My old pin doesn't work, default_password doesn't work. Both slots are encrypted and I can't decrypt my internal storage to backup my files. Is there any work around I can do?
Click to expand...
Click to collapse
The quick fix is format data. The other is hoping you have an otg cable to flash drive to reinstall that custom rom you have to access your data for backup.
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 folks, I searched wide and large, it seems I cannot access TWRP anymore after having encrypted my phone.
I have a Mi4C, with the 7.4 weekly ROM (MIUI 8.3).
I set the encryption in order to use the company eMail app.
When I tired to enter TWRP I was asked the encryption password, but it did not work, so I tried to:
Remove the encryption altogether
Encrypt with a new Password
Encrypt with PIN
I have installed the latest TWRP 3.1.1. via the TWRP APP, same issue.
Nothing has worked.... Can I just remove TWRP and install a newer version?
How do I overwrite the file that has that TWRP encryption record?
You can try flashing updated twrp, but I doubt it will remove encryption without wiping data.
Anyway, if you wanna remove encryption you've to wipe data via TWRP.
Thanks for answering, I did try to upgrade TWRP, no success. I will wipe.
Hello, been running twrp with encryption on Lineage OS 16 without problems for 6 months. But yesterday I flashed new android Q factory image and was unable to decrypt my data in twrp, even when I put the right password in it says ''password failed, please try again''. I tried flashing various factory images, custom roms even Lineage 16 but problem persists. I had this same problem back then when I first bought this phone but managed to solve it, I can't remember how I did it. TWRP is up to date. Any ideas? thanks.
It's TWRP issue. Sadly TWRP 3.3.1 is not available in zip format. Only in .img format. In 3.3.1 this problem is resolved.
As workaround you can remove any PIN, fingerprint and set security to none in setting and you won't have to enter anything in TWRP. Do whatever you want in TWRP and then set up PIN and fingerprint again.
matusala said:
It's TWRP issue. Sadly TWRP 3.3.1 is not available in zip format. Only in .img format. In 3.3.1 this problem is resolved.
As workaround you can remove any PIN, fingerprint and set security to none in setting and you won't have to enter anything in TWRP. Do whatever you want in TWRP and then set up PIN and fingerprint again.
Click to expand...
Click to collapse
Yeah I know this, but why did it started to do this after flashing Q factory image? TWRP worked without any problem on various custom roms. Actually now I remembered that while flashing Q factory image there was a problem mounting vendor and system partition, so I went back and flashed Lineage 16 and there this TWRP password thing started if I remember correctly.
I came here looking for the answer to this very issue.
I shot off an email to TWRP if they were going to update the latest zip to 3.3.1 because fastbooting to the img works fine.
I might try the trick of removing pin and security and try again.
I have the same problem but with 9.0, if I have a pin it's ok it decrypts just fine but when I have the fingerprint set up I get this problem, it kinda blows, I'm not using twrp everyday but it still blows that you have to disable security Everytime you want to use it, also, last night I used twrp with the security on it could not decrypt so and when i tried to reboot into system, I got the prompt to install the twrp app, I screwed up and used the slider instead of the button to cancel the installation and it messed up the system, so watch out for that crap.
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
I've just got my Realme 5i returned after repair (replacement main board) and I've unlocked the bootloader, flashed TWRP and vbmeta9, flashed Magisk and enabled MagiskHide but I can't set a PIN. Whenever I try, after confirming the PIN it returns to the settings screen and shows "Lock Screen Password - Off".
I know I managed to set a PIN before it needed repairing, as when my brother received it from me from his Birthday, he phoned me to ask for the PIN to access it but I can't remember what I did then to get it working.
I tried to install "Realme 5i Magisk Fix for ColorOS by IT&AUTOS.zip" in Magisk as I did that before but now it isn't working and the log says "copying to temp, error unzipping file". Would installing this be what got the screen lock working before?
I've got a TWRP backup of all the partitions from before it was repaired but I can't seem to access them to restore, as when I select the Storage option from Restore it shows the SD card is only 6GB, when it fact it's 128GB and the only file it shows is "257eee4a" which is actually the folder above the dated folders containing the backups.. From the Install option, I can browse the SD card normally and I flashed Magisk from a folder on the card, so I don't know why it's not accessible from the Restore option. If I could, then maybe restoring the System and Data partitions would get me back to the state where the PIN was set but I'd be a bit nervous about restoring the System partition after then main board has been replaced, in case any files are tied to the old hardware.
I thought what I might have done to get it working last time is to relock the bootloader (after flashing the stock recovery to prevent bootloop) and then unlock it again but if that is what I did before, it isn't working now.
First I updated to A.20 via the stock recovery, as the service center had flashed A.15. It kept booting to stock recovery after that until I did Format Data and then it booted OK and after locking the bootloader I was able to set a PIN.
Then I unlocked the bootloader and it automatically wiped data but I still had to Format Data to stop it booting into stock recovery and now I can't set the PIN again.
I see there's a 5i Decryption (COs).zip. What does this do? I tried flashing that via TWRP before I tried the above steps but it didn't get the PIN working.
I just flashed TWRP and then installed 5i Decryption (COs).zip and wiped Cache/Dalvik Cache and now it gets stuck on the yellow realme logo when I try and boot. Can't even power it off when it's like that but thankfully volume up and power gets me to bootloader and TWRP and doing a factory reset wipe got it booting again.
I still can't turn on the PIN/Lock Screen password though.
I tried restoring my TWRP System and Data backup from last August when the Lock Screen password was working but it still doesn't work, so it must be something in one of the other partitions that affects this and I'm reluctant to try restoring those in case it bricks the phone because the main board has been changed.
Can anyone help me please? Does anyone have the lock screen password working with unlocked bootloader, or is everyone who has installed custom recovery/rooted their 5i just using it without any password to protect it?