Decryption failed - ONE Q&A, Help & Troubleshooting

I'm running an encrypted device. I went in to recovery, did a nandroid backup, then did a wipe data to test something. The phone booted fine after the wipe. Then I went back in to recovery and restored my nandroid. Now the phone won't decrypt and says I need to factory reset. Says something like "Your password is correct but decryption failed" ... Is there a way to recover my data, or am I screwed?

Related

Unsuccessful decryption

Okay, I'm not sure if this entirely the right place. Have updated to Viper 2.1.0. Rebooted my phone, as I do each morning. It came up with needing to to enter a decryption key, ie; my password. Did said & it failed saying that data is corrupt. TWRP can no longer read the data portion either. Therefore can't wipe it in TWRP.
Is there a way to format or wipe the data partition through either fastboot or adb?
Factory reset but your data will be gone.
Random Pinenut Joy said:
Okay, I'm not sure if this entirely the right place. Have updated to Viper 2.1.0. Rebooted my phone, as I do each morning. It came up with needing to to enter a decryption key, ie; my password. Did said & it failed saying that data is corrupt. TWRP can no longer read the data portion either. Therefore can't wipe it in TWRP.
Is there a way to format or wipe the data partition through either fastboot or adb?
Click to expand...
Click to collapse
Try this, Venom helped with it a while ago and it worked, you will just have to re activate smart lock in google setting.
TWRP-Advanced-File Browser.
Navigate to /data/system and delete the locksettings.db.
I got my phone back from HTC after repair my phone screen and they wiped my custom rom and recovery but still have unlocked bootloader and restore oreo 8.0.
I managed to re-install twrp and tried to install a customed rom and experienced the same "decryption unsuccessful". But there is no lockingsettiings.db in the folder.
I will later try this method and report.... been a frustrating day....
=https://forum.xda-developers.com/showpost.php?p=59685278&postcount=3

Encrypting device gone wrong, android and recovery broken now, seems softbricked?

So, I made a big mistake.
I tried to encrypt my device, but it got stuck at 100%, so i rebooted it and now it's completely messed up.
When i boot it, it asks me for a password, when i enter it, it says decryption unsuccesful and my data is corrupt.
It gives me the option to reset the phone, which is fine, but it reboots the phone into recovery.
But i can't get into recovery, i can't read it properly but as far as i understand it fails to mount /data 5-ish times and then reboots again and tries to boot android again, bringing me to the password screen once again.
I don't care about data, i have backups, but i just want my phone working again.
TL : DR: phone boots, asks password, says data is corrupted, reset phone, goes into recovery, fails to mount partition, reboots, back to ask password.
If i have to do something in ADB let me know, i'm far from good with it but i can at least get it working...
Edit: RECOVERY WORKS! I got that one working again! Problem is that it still can't mount the /data partition so i can't seem to reset/wipe the phone properly.
Edit 2: Device is up and running again. I re-flashed the recovery via the bootloader and ADB, did a full wipe with the recovery because the re-flash fixed it and the wipe fixed the mount problem. After the /data partition could finally be mounted again i just flashed a ROM as usual with gapps and problem solved!
The microSD was broken too but after formatting that with a PC the phone could use it properly again. Did take a few tries tho, no idea why.

If I completely wipe phone can I restore TWRP Back up

If I use the tool to reset OP6 to factory and root it again. Then update to latest could i restore old twrp backup from same phone?
Yes you can if you stored that twrp backup in your PC.
I think that you can't. I tried few times and never got it right. There are always some errors. Maybe something changed in the meantime tho...
AciDB said:
I think that you can't. I tried few times and never got it right. There are always some errors. Maybe something changed in the meantime tho...
Click to expand...
Click to collapse
Just backup data in TWRP. Install everything else normally. Full ROM zip, TWRP zip, reboot recovery, flash magisk, boot. Data will be in tact regardless, unless you wipe it or factory reset.

Need Help to restore backup with TWRP

Can anybody help?
My HTC U11 still run on Nougat.
Yesterday I want to update with the newer version of Nougat (Not Oreo)
I already make a data backup with TWRP, big backup 22Gb.
Then I update the new stock Rom from PC, it had no problem.
Go to download mode, and then install TWRP again with ADB from PC.
Go to TWRP Recovery, it still works.
The last thing I do is to try to restore the 22Gb data back to my phone.
And it always get error on 9% with "extractTarFork() process ended with ERROR: 255"
I already change with difference TWRP from 3.1.1.0 to 3.2.3.0, still the same.
Restore to previous version of Nougat with TWRP (system, system image, boot image, recovery). Try to restore backup data again with no luck.
Try to check MD5 with the backup data, and it said matched, no corrupt.
Already try searching in the web, but with no solution too.
Do anyone ever have the same problem and solved it?
A San said:
Can anybody help?
My HTC U11 still run on Nougat.
Yesterday I want to update with the newer version of Nougat (Not Oreo)
I already make a data backup with TWRP, big backup 22Gb.
Then I update the new stock Rom from PC, it had no problem.
Go to download mode, and then install TWRP again with ADB from PC.
Go to TWRP Recovery, it still works.
The last thing I do is to try to restore the 22Gb data back to my phone.
And it always get error on 9% with "extractTarFork() process ended with ERROR: 255"
I already change with difference TWRP from 3.1.1.0 to 3.2.3.0, still the same.
Restore to previous version of Nougat with TWRP (system, system image, boot image, recovery). Try to restore backup data again with no luck.
Try to check MD5 with the backup data, and it said matched, no corrupt.
Already try searching in the web, but with no solution too.
Do anyone ever have the same problem and solved it?
Click to expand...
Click to collapse
Did u try a format in twrp before installing the backup? Just thought
No, not format anything. Afraid did something would make the phone brick.
A San said:
Can anybody help?
My HTC U11 still run on Nougat.
Yesterday I want to update with the newer version of Nougat (Not Oreo)
I already make a data backup with TWRP, big backup 22Gb.
Then I update the new stock Rom from PC, it had no problem.
Go to download mode, and then install TWRP again with ADB from PC.
Go to TWRP Recovery, it still works.
The last thing I do is to try to restore the 22Gb data back to my phone.
And it always get error on 9% with "extractTarFork() process ended with ERROR: 255"
I already change with difference TWRP from 3.1.1.0 to 3.2.3.0, still the same.
Restore to previous version of Nougat with TWRP (system, system image, boot image, recovery). Try to restore backup data again with no luck.
Try to check MD5 with the backup data, and it said matched, no corrupt.
Already try searching in the web, but with no solution too.
Do anyone ever have the same problem and solved it?
Click to expand...
Click to collapse
Try to restore os without data , restart system, and if it works restore data
fabrizio b92 said:
Try to restore os without data , restart system, and if it works restore data
Click to expand...
Click to collapse
I have 2 backup. One is for system and one is data. I can restore system feom TWRP recovery, but can't restore data
After restore system,reboot to twrp and restore data
I had this problem and it took me two days to resolve it. I had a good backup and I know it was good because I had used it several times and it worked. But then after doing some system installs I got the error 255 when I tried to restore it. I tried several things to fix it and nothing worked and I really did not want to lose my backup. What did work for me was to use TWRP wipe function to FORMAT the phone. Wiping or factory reset did not work. I lost the contents of my internal SD card but I was able to transfer most to my external SD card. You could also connect the phone with a cable to a computer and use the pull command in ADB to backup the contents f the internal SD card. Given the choice between losing the SD card and the data files I come to lose some of the SD card. Anyway, a FORMAT worked when nothing else did. I read that this error is caused by a lack of space. When I checked the log it seemed that the restore was failing with a particular file which misled me to thinking I had to remove the corrupt file, but since after the format I was able to restore without any problem, it would seem that there was no corrupt data. Hope this helps someone.

"Phone is Starting" Loop after Restore from TWRP 3.6.0_11-0

Installed Lineage 18.1 OS, TWRP 3.6.0_11-0 and Magisk, booted system, added PIN and fingerprints, all was good. Booted back into TWRP and made a full backup of all partitions. Tried a test restore of Super and Data partitions. Upon reboot, I get the lineage splash/boot screen, then "phone is starting" forever. From reading around, this is due to the system trying to access encrypted data. Questions: 1) I'd like to be able to use TWRP for two things: a) restoring to a new device should this one break, and b) reverting back to previously backed up state of operation on the same device. What partitions should I be restoring for each of these? 2) Is there a fix or proper method to make restorable backups using TWRP?
Exactly the same situation. And have exactly the same questions.
Had the same problem, wiped data, repaired data file system, rebooted into system to disable the pin. Then restored my TWRP data backup again, now it boots into system, just had to reboot twice because the gestures and staturbar didn't work first. Now I just have to tweak some little details again to get it how it was.
Didn't solve my main problem though, SMS not working. Wiped and repaired data again, now it works. Welp, guess I have to set it all up again from here.

Categories

Resources