Hello,
Thought I would share my recent bad experience and the resulting solution.
My phone was on a GPE ROM, and I encrypted it for work reasons, encryption went smoothly, but once encrypted, it was impossible to go into recovery with the encrypted partitions visible (hence impossible to flash a new rom or even do a factory reset which is the only - or so I thought - way to remove encryption).
After many attempts including flashing the latest TWRP (not solved yet, they say 2.7 should include a solution) I was still getting the "unable to decrypt phone" error after entering the password (which works perfectly on regular boot) in TWRP.
Eventually, through a lucky mistake, I found the solution, at one point I mistakenly re-locked my phone (fastboot oem lock), later when I was trying to flash a stock recovery I realized I had to unlock it again... well, unlocking it through HTCdev automatically does a factory reset, regardless of the encryption!
viola, problem solved!
Related
Hi all. Just got my shiny new HTC One dev edition this week. What I learned is I should have done more reading on here before I even turned on my device - for example I went and upgraded to OTA 4.4 before getting S-Off and Super CID - my bad... in any case absolutely loving the device with one exception and bad experience that I can hopefully help others recover from or avoid.
I unlocked by bootloader, got root, flashed custom recovery and flashed a KitKat based customer ROM - all the usual stuff. That was all good - here's where the fun starts. My exchange server requires device encryption as one of its policies and of course encryption with KitKat on the HTC One is flat out broken. The device refuses to boot after you've etered your dycryption password and it just hangs on boot screen forever. This is the case with KitKat whether you are on stock OTA or custom - did I mention KitKat encryption is broken on the One?
I tried everything:
1. Wiping in custom recovery doesn't work because it cannot decrypt
2. RUU fails
3. RUU.zip via fastboot fails
4. Tried flashing back to stock recovery and that factory reset also fails
I was contemplating what to do with my shiny new brick and remembered that the HTCDev unlock process does a wipe, so I relocked the bootloader (fastboot oem lock) and unlocked again using the Unlock_Code.bin file I got from HTC. This process was the only method that I found to work in this situation to remove encryption.
To summarize, if you have upgraded to KitKat (Stock or Custom ROM) and you go and encrypt your device, do the following to recover:
1. Relock the bootloader (if not unlocked - go to step 2)
2. Unlock the bootloader again using the Unlock_Code.bin from HTCDev
3. Select Yes during the process to erase all data on the device.
I hope this helps save someone the3 hours I spent on this.
Cheers.
I encrypted my phone with ACIP 10 Rom with a 4 digit pin. Now I wanted to change back to a sense based rom, ARHD 93 to be precise, and performed a fullwipe including internal storage after flashing rom and kernel. After rebooting the rom asks for a password to decrypt the phone and even though the pw works perfectly fine to decrypt the phone in TWRP, it won't work on the sense dialogue. I entered settings and enabled usb debugging but the device won't show up on my pc (still decrypted). Unfortunatly fastboot is broke on my phone.
Has anyone had similar problems with decrypting or knows if it is possible to decrypt the device from TWRP?
Relixx said:
I encrypted my phone with ACIP 10 Rom with a 4 digit pin. Now I wanted to change back to a sense based rom, ARHD 93 to be precise, and performed a fullwipe including internal storage after flashing rom and kernel. After rebooting the rom asks for a password to decrypt the phone and even though the pw works perfectly fine to decrypt the phone in TWRP, it won't work on the sense dialogue. I entered settings and enabled usb debugging but the device won't show up on my pc (still decrypted). Unfortunatly fastboot is broke on my phone.
Has anyone had similar problems with decrypting or knows if it is possible to decrypt the device from TWRP?
Click to expand...
Click to collapse
Do a factory reset using the stock recovery (not twrp), then wipe and clean install your rom again and you should be fine. But first, fix your fastboo problem since you'll need it to flash the stock recovery.
alray said:
Do a factory reset using the stock recovery (not twrp), then wipe and clean install your rom again and you should be fine. But first, fix your fastboo problem since you'll need it to flash the stock recovery.
Click to expand...
Click to collapse
Thanks for your help! I'm still stuck on the fastboot issue. Tried it on several different pcs with win 7,8 & 10. ADB command boot to fastboot mode works, after the phone enters the mode the connection is lost. Could this be the result of a faulty microusb port on the phone? Or is the problem soley on the software side?
Solved:Didn't fix the fastboot problem, but this wasn't necessary. Instead of a factory rest go twrp Wipe - >Format Data. This completely removed the encryption and thus I can use the phone again
So I just recently received a new (to me) Nexus 6. Going through the process of unlocking the bootloader I forgot to do the command "fasboot reboot". I then installed TWRP and then booted into it. From there I rebooted the system and was brought to a screen that says encryption unsuccessful. I hit the reset button which brought me to twrp and asked for a password. I typed in "default_password", it did it's thing and rebooted to the same "encryption unsuccesful". I tried searching XDA as well as Google to no avail. When searching Google I found some threads for other devices but I didn't want to get into a worse situation than I'm already in so I thought I'd ask here before trying anything else. Any help would be greatly appreciated!
Update: I flashed the stock image (manually as the flash-all didn't work) and I was able to get the phone to boot up into Android. But whenever I reset the device it gives me the "Your device is corrupt" screen before booting into the system. And it seems like whenever I try to flash supersu or anything I'll get that message and then it just goes to a black screen and never boots into Android. I even tried to restore a TWRP backup and it still just went to the corrupt screen and then black. I was only able to get it to boot into Android after reflashing the stock images again. Is this a problem with the hardware or is there something I can do to fix it?
Edit: I've also noticed under internal storage it's only showing 23 GB available but this is the 64 GB model.
Prozart said:
Update: I flashed the stock image (manually a.
Click to expand...
Click to collapse
Did you format/wipe the system, data and caches - a complete factory reset ?
There are several things going on here.
1. Your device is corrupt message: This is a normal message that appears whenever you attempt to customize the device. It may also appear if there is an issue with the internal storage in general.
2. SuperSU: What version? You should be using the latest (2.76) or you risk having a bootloop.
3. TWRP: What version? Latest is 3.0.2-0. Older versions will offer to flash SuperSU. Don't accept the offer or you will enter a bootloop.
4. Internal storage: When you flashed the stock ROM you also flashed the userdata image in it, which caused you to lose half your storage. Simply wipe internal storage in TWRP to fix.
Your first thing is to fix your internal storage, which should be done through TWRP. From there, you will need to do a complete factory reset, as the failed encryption is the main reason you're getting a corrupt device warning. After the factory reset, restore the stock image, but do not flash userdata.img.
Thanks guys! Doing the factory data reset in stock recovery fixed it for me. It took about 30 minutes to complete, but now I've got root, twrp, and custom ROM and kernel with no issues.
I noticed a couple of weeks ago after updating to OOS 4.5.1 that the phone no longer asked for my decryption password at boot time. It just boots through to the system and asks for the the password at first boot, making it appear that storage is no longer encrypted. The bigger problem, though, is that TWRP doesn't ask for a password anymore either - it just goes straight to the TWRP splash screen and never goes farther. I'm running version 3.1.1-0 of TWRP - not the BlueSpark version, but it has worked up to now, and newer versions caused me no end of problems in the past that corrupted my partitions and forced me to reflash the entire phone.
Should I reflash TWRP - this version or a newer one? I've seen the BlueSpark one recommended, but I don't want to kill the phone by causing encryption problems. I've had this phone almost a year and have had problems with the encryption scheme at virtually every OS upgrade I've done. I'm tired of doing full wipes and going back to Marshmallow. Advice?
**UPDATE** After reading some other posts, I realized I might just not be waiting long enough for TWRP to boot, so I gave it time. After about 10 minutes, I got the TWRP menu and had full access to all my files. This is good news and bad news - since I never provided a decryption password, my disk is apparently unencrypted, although I don't know when that would have happened. So I can do a nandroid backup and proceed with the Oreo update, but I still have the issue of how to restore encryption. Again, advice?
I had another problem - TWRP didn't accept my password, but I could boot to OS with the same pass. Unfortunately full data wipe was needed.
PS Marshmallow is kind of deprecated nowadays
I had a similar problem when I tried to update to 4.5.0. I could get into TWRP but I couldn't mount system, so I couldn't take a backup. Turned out the file system was corrupted. It would boot and run anyway, but recovery was useless. I eventually bricked the phone and restored using the utility that rewrites the original factory image, which is Marshmallow. As soon as the phone connects to the network, it applies the latest patch, so Marshmallow doesn't last long, but it's really nice to have a fail-safe way to restore the phone from any problem.
mobilityguy said:
I had a similar problem when I tried to update to 4.5.0. I could get into TWRP but I couldn't mount system, so I couldn't take a backup. Turned out the file system was corrupted. It would boot and run anyway, but recovery was useless. I eventually bricked the phone and restored using the utility that rewrites the original factory image, which is Marshmallow. As soon as the phone connects to the network, it applies the latest patch, so Marshmallow doesn't last long, but it's really nice to have a fail-safe way to restore the phone from any problem.
Click to expand...
Click to collapse
Did you tried removing password protection from rom ...
My daughter unwittingly performed an OTA update with an unlocked bootloader and now gets the error "Decryption unsuccessful, the password you entered is correct, but unfortunately your data is corrupt." at startup. Before I wipe the device I'm wondering why when I boot with the stock recovery the password seems to decrypt properly if I use the correct password (no errors but there is no way to mount or backup the data partition) but if if temporarily boot with TWRP via fastboot the password does not seem to decrypt the device (I do receive a password failed error). Any information is appreciated.
In my view, there are some issues with the pie build which detects that the bootloader is unlocked. After this you may see decryption unsuccessful.
When I was on oreo 5.0.8, I had flashed nougat ROMs too by just flashing the nougat fw but now when I was using pie 9.0.2; I tried to flash sultan ROM which resulted in decryption unsuccessful.
In that case, we need to format the phone.
qizbot said:
My daughter unwittingly performed an OTA update with an unlocked bootloader and now gets the error "Decryption unsuccessful, the password you entered is correct, but unfortunately your data is corrupt." at startup. Before I wipe the device I'm wondering why when I boot with the stock recovery the password seems to decrypt properly if I use the correct password (no errors but there is no way to mount or backup the data partition) but if if temporarily boot with TWRP via fastboot the password does not seem to decrypt the device (I do receive a password failed error). Any information is appreciated.
Click to expand...
Click to collapse
Flash the modded firmware. See firmware thread for details: https://forum.xda-developers.com/showpost.php?p=79690946&postcount=592