Database Develop

Encryption Unsuccessful

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.

[OP3T] From stock to Nougat then flash TWRP & root

Hi all,
What happens if you take a stock 3T, upgrade it all the way to Nougat the normal way, then proceed to unlock the bootloader, flash TWRP and supersu?
Does the TWRP 3.0.3.0 build have an issue with decrypting and mouting the sdcard? Is that even a problem in the sense of waiting until a fixed version of TWRP is released? The point is to just flash supersu for the moment. No other need to access that partition from recovery, is there? Or does it directly impact my ability to upgrade TWRP in the future?
And another question: would decrypting the phone after the stock to Nougat update, and only then flashing TWRP&root be of any use? Is this even possible at the moment? I can hold on without encryption until there's a proper version of TWRP, kernel sources are released etc.
I don't seem to find any info on these scenarios. Has anyone tried any of this?
Thank you!

Good questions.
Does the TWRP 3.0.3.0 build have an issue with decrypting and mouting the sdcard?
Click to expand...
Click to collapse
I can confirm 3.0.3.0 has problems with decrypting and mounting sdcard. A new version of TWRP should fix this.
No other need to access that partition from recovery, is there?
Click to expand...
Click to collapse
Well, the need to access partition from recovery depends. You won't be able to flash anything from TWRP. I could sideload different recoveries without decrypting but had to decrypt (with the format userdata command from cmd prompt) to revert to 3.5.4 from TWRP. In the end I mostly downgraded due to bluetooth issues.

I am having the same decryption issue... TWRP shows 0MB as the storage
What should be done now..?

you can get past encryption by formating data in twrp, though that deletes all your data, back ups and everything, but with that you have the phone completely rooted and then you can download or transfer data via mtp to storage, flash super su and verity.

Amar97 said:
you can get past encryption by formating data in twrp, though that deletes all your data, back ups and everything, but with that you have the phone completely rooted and then you can download or transfer data via mtp to storage, flash super su and verity.
Click to expand...
Click to collapse
Did that already but did not work.. Even tried the setting up of pattern method.. that too did not work...
Also force decrypted with Toolkit but still the same

just to make sure. flash twrp via fastboot( I flashed the 3.0.2.0 version) then when booting to twrp you get get the screen where it asks you for a password, skip that , just swipe to continue then go to wipe, then format data, type "yes" to confirm, the at the next booting it shouldn't​ ask you for the password anymore. That did it for me. Maybe you should try adb sideload to flash verity.img and supersu

Amar97 said:
just to make sure. flash twrp via fastboot( I flashed the 3.0.2.0 version) then when booting to twrp you get get the screen where it asks you for a password, skip that , just swipe to continue then go to wipe, then format data, type "yes" to confirm, the at the next booting it shouldn't​ ask you for the password anymore. That did it for me. Maybe you should try adb sideload to flash verity.img and supersu
Click to expand...
Click to collapse
why not use 3.0.3.0?

Solnir said:
why not use 3.0.3.0?
Click to expand...
Click to collapse
Don't really know, probably tried solving the problem by trying with the older version and then didn't feel like upgrading to the newer 3.0 after fixing the problem.

Stucked in Encryption Unsuccesful help!

I need help, I was trying to root my Oneplus 3T, with stock OOS 4.0.2. After following all the steps, I flashed the dm-verity to keep with the steps, and that worked. But after formatting data, as it was suggested, it gave me an error. It showed like everything was encrypted which shouldn't due to the flash of the dm-verity and now I'm stucked in not a bootloop because the phone actually boots but I cant do anything because the encryption error takes me back to the recovery, which shows an error etc. Is there any tutorial to fully recover the phone from this point? Thank you very much in advance.

Did you try flashing SuperSU after flashing dm-verity? If the zip isn't on your phone at this point, you can go into bootloader mode and use adb to push the SuperSU zip on and flash it that way.
You can use the toolkit to push the files if you want, it'll be easier that way: https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
If all else fails, flashing a clean rom always works.

Anova's Origin said:
Did you try flashing SuperSU after flashing dm-verity? If the zip isn't on your phone at this point, you can go into bootloader mode and use adb to push the SuperSU zip on and flash it that way.
You can use the toolkit to push the files if you want, it'll be easier that way: https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
If all else fails, flashing a clean rom always works.
Click to expand...
Click to collapse
Now I'm stuck in a bootloop after reflashing stock recovery. If i reflash the boot.img via fastboot from the .zip of the official OOS 4.0.1, will it work? Thank you very much

Not sure why flashing recovery would cause a bootloop. Might be safer just to sideload a fresh ROM. If you're worried about losing files, you can use adb to pull whatever you need first from sdcard prior to flashing.

What I did in a similar situation was to reflash the stock recovery first using the unbrick-toolkit. When booting into recovery then, there is an option "forget password" when it asks you to enter the password. If you select that, it will simply wipe your phone completely and you can start over again.

Stuck on TWRP after attempted restore

Hi guys.
So after developing an audio bug on Lineage OS 15.1 (a story for another day) I decided to restore one of my old backups via TWRP (unofficial decrypt-friendly version).
I press restore, get some sort of error about mounting /system and then on reboot I get a message asking me to factory reset which takes me to TWRP. Not too surprised by this point because the Huawei bootloader is quirky.
However, when I go into TWRP, it simply gets stuck on the loading screen endlessly. I left it for several hours and it didn't budge. Rebooted several times.
I tried reflashing TWRP via fastboot, no dice, same result. I flashed the official recovery too. That loads fine, but obviously I can't restore with that because it doesn't support encryption.
So I'm a bit stuck here. I've read somewhere that it takes ages to load when you have plenty in the data and cache folders, which I do, but I really don't want to wipe because I have a full week of precious holiday photos and videos I wasn't able to back up (No access to a PC at the time).
Any advice?

Not sure how to fix the TWRP restore problem, but have you tried connecting to your PC while in TWRP? If I remember correctly, it'll allow you to connect to a computer so you could access your storage and backup the files you need.

frost_icewind said:
Not sure how to fix the TWRP restore problem, but have you tried connecting to your PC while in TWRP? If I remember correctly, it'll allow you to connect to a computer so you could access your storage and backup the files you need.
Click to expand...
Click to collapse
Problem is that everything is encrypted, so even if it does show up it will be gobbledygook (nonsense).

Lesson to learn from this: always backup before trying to update ROM or flash something new.
I guess what you can do is to try to flash Lineage again and see if you can make that boot.

mrabcx said:
Lesson to learn from this: always backup before trying to update ROM or flash something new.
I guess what you can do is to try to flash Lineage again and see if you can make that boot.
Click to expand...
Click to collapse
Yeah, there's a few reasons that happened. Usually I autobackup everything but I had been away from wifi for a week. I backed stuff up via Titanium but obviously that got encrypted too. Restores also have never given me problems in the past so I didn't expect anything to go wrong (still not sure what did).
Anyway, I'm not sure how to flash lineage without TWRP, especially with everything encrypted. To have any chance of getting it to work I'm guessing I'd need to flash it the same way I did originally, which was with everything decrypted which makes the issue moot. Maybe I'm wrong though.

Try flashing a treble rom via fastboot. Then wipe data and cache.
fastboot flash system "GSI. img"
fastboot erase userdata
fastboot erase cache
fastboot reboot

side_flip15 said:
Try flashing a treble rom via fastboot. Then wipe data and cache.
fastboot flash system "GSI. img"
fastboot erase userdata
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Thanks, but I'm trying to prevent loss of data. I'd probably just use e-recovery if I don't mind losing data and want to reset to start again from scratch.

Erasing userdata and cache is just factory reset. It won't wipe your internal storage which where your photos are kept.

Ok, turns out once I chose the "download latest firmware and stock recovery" from erecovery it didn't wipe the internal sd data!
Everything is still there and I can access it now from the huawei stock ROM even though I came from lineage OS. It thankfully does not reset the encryption keys or the pattern lock, so you'll be just fine once you do a system boot and go through the regular setup process.
I recommend this approach because it's pretty hassle free.

Armand Bernard said:
Ok, turns out once I chose the "download latest firmware and stock recovery" from erecovery it didn't wipe the internal sd data!
Everything is still there and I can access it now from the huawei stock ROM even though I came from lineage OS. It thankfully does not reset the encryption keys or the pattern lock, so you'll be just fine once you do a system boot and go through the regular setup process.
I recommend this approach because it's pretty hassle free.
Click to expand...
Click to collapse
Glad you found a way to keep your files, mate

I got stuck in a 'recovery bootloop' and I'm desperately trying to rescue my data

Since I never had a problem with an update in years, and I'm also a very stupid person, I didn't backup my data before my latest custom rom (Pixel Experience Plus) update.
I got the notification for the November security patch updates, and I downloaded the zip as usual. For the actual installation I usually reboot my Mi 9T Pro into TWRP, flash both the OS update and Magisk, etc. and reboot. Everything seemed to go smoothly as usual: TWRP asked me to input my unlock sequence, then the usual stuff. Problem is, when I tapped 'Reboot system', it didn't reboot normally: it went into Recovery mode again, and from that moment on there's been no way to do otherwise. But now TWRP doesn't ask me the unlock sequence anymore and looks like there's no way to access the data. I tried injecting the recovery from fastboot, I wiped everything except internal storage (I don't give a damn about the OS anymore at this point); I also tried to reinstall the same old rom from OTG after wiping System, but nothing. Whatever I do, it always boots up in Recovery, and it doesn't ask me the unlock sequence. I know my stuff is still there, it's just that the contents of sdcard aren't accessible and look like random alphanumeric sequences from the TWRP file manager. And yes, that's the whole point of encryption, but I was used to TWRP asking me to unlock/decrypt so in the worst case scenario I would be able to access my data and copy via OTG. But now, with the system unable to boot and the recovery not decrypting my stuff, I'm starting to losing hope. I'm sure here on XDA there are much smarter / knowledgeable people than me, and I hope somebody can help me find a way to break the cycle and return in possession of the data that I stupidly didn't backup.
Any help would be greatly appreciated!

Try reflashing the boot image. Failing that, you should be able to ADB sideload the update via TWRP.

V0latyle said:
Try reflashing the boot image. Failing that, you should be able to ADB sideload the update via TWRP.
Click to expand...
Click to collapse
I think I tried both. I say 'I think' since my knowledge could fail here.
I tried re-flashing the TWRP img from OTG, nothing changed.
I successfully sideloaded the OS through ADB, but I'm still stuck.
Should I try both? (In which order)?
Thanks a lot.