Database Info

decryption unsuccessful

today i tried to use my tablet and it completely locked up on the unlock screen, so i powered it off and upon powering it back on it said data unsuccessful and tried taking me into the recovery, which for me is twrp.. however, i cant seem to do anything here, it asks me for a password to decrypt the data, but i do not have such a password, im not sure if im able to reformat these partitions in any way, or reinstall a new ROM.. i dont have a microSD card, just a regular SD card i use on the dock
any ideas?

in trying to work out the problem ive managed to wipe almost all the data and attempted to install a new rom.. however, rom stops when it tries to format... from twrp, it wont let me format the data either... so theres something blocking me from formatting now, and this is stopping me from continuing, any ideas?

jason41987 said:
in trying to work out the problem ive managed to wipe almost all the data and attempted to install a new rom.. however, rom stops when it tries to format... from twrp, it wont let me format the data either... so theres something blocking me from formatting now, and this is stopping me from continuing, any ideas?
Click to expand...
Click to collapse
Did you ever encrypt it? What bootloader are you on? Have you recently updated TWRP?
If not I would try to reinstall TWRP 2.5.0.0. The only time I have ever seen this error is an incompatible TWRP and bootloader.

[Q] TWRP cannot read my sdcard (encrypted?)

So, my previous post was a bit too optimistic. I've managed to get TWRP onto my phone, but when I went to actually load a custom ROM into it, I found that it couldn't read anything from my sdcard.
I'm having what appears to be a common problem: when I boot into Recovery, TWRP asks for a password. When I cannot provide it (because I have no idea what it is), TWRP is unable to access the data partition. Apparently, the partition is encrypted and I have no way to de-crypt it.
I've found dozens of other posts by users having this problem and the solution everyone is giving is to fully wipe the data partition and start over. But I *can't* wipe the data partition, because TWRP can't access it and fails almost immediately. I have tried a multitude of options, including:
* Installing old versions of TWRP - same behavior; asks for a password, fails to wipe/format the data partition.
* Installing ClockWork's recovery - same thing; fails to format/wipe the data partition
* Flashing back to stock recovery, using that to format my data partition; this worked fine but as soon as I put TWRP back, the problem came back.
On my last attempt, I used the stock recovery to completely wipe the data partition, and made absolutely sure that it never booted into anything but Download or Recovery modes after that. I was hoping that would prevent the stock software from ever re-encrypting the data, but somehow, when I booted TWRP, it still can't read my partitions. Note that my phone itself is not "encrypted" as far as the Settings application is concerned, but apparently Android is doing something behind the scenes anyway. There doesn't seem to be any option in the stock settings to turn off this encryption.
Is there any hope for getting a custom ROM onto this phone?
Thanks for the help!

Any solution? I'm running into the same issue where TWRP is asking for a password.

Undo Format Data?

I am a relatively new android user but do enjoy flashing roms, kernels etc
My problems began when i was trying to flash a new rom on my Nexus 5
I was trying to flash this rom http://forum.xda-developers.com/showthread.php?t=2655722 but despite doing a factory reset and wiping the dalvik cache and cache it refused to boot in to the new rom
I tried to flash the rom multiple times but without success, eventually when trying to boot into recovery to try again i was greeted with an unthemed TWRP recovery asking for a password despite the fact that i had a custom theme and multirom installed I tried to proceed anyways but was greeted with E: unable to mount storage
In desperation i tried to solve this problem and found this
UsoftTech :: WwW.UsoftTech.CoM ::
TWRP asking for password
After unboxing my Nexus 5, here's what I did:
1. Booted into bootloader
2. fastboot oem unlock
3. Flashed TWRP v2.6.3.0
4. Booted to recovery
The screen that greeted me says "Please Enter Your Password".
I can hit the cancel button below this which takes me to the normal TWRP screen. I then pushed SuperSU to /sdcard, but when I flash it it fails because it's unable to mount /cache or storage.
When I reboot to the system, it takes an awfully long time (approximately 30s) to progress past the "Google" screen, and then it just seems to sit on the booting animation forever.
Any help?
EDIT: Solved my own problem.
Hit cancel at the password screen, then go into Wipe and then do a factory reset by swiping. Then go back into Wipe and press the 'Format data' button. You have to type 'Yes', and it will take a few seconds. After that everything should work normally.
TWRP asking for password
Click to expand...
Click to collapse
I now fear that i maybe without both a rom and all my files such as my music that was stored on my phone.
Is there any way for me to undo the damage i may have done to to my phone?

You can't recover the data. But you can push files over with ADB.
Sent from my Nexus 7 using Tapatalk

JoJostar said:
I am a relatively new android user but do enjoy flashing roms, kernels etc
My problems began when i was trying to flash a new rom on my Nexus 5
I was trying to flash this rom http://forum.xda-developers.com/showthread.php?t=2655722 but despite doing a factory reset and wiping the dalvik cache and cache it refused to boot in to the new rom
I tried to flash the rom multiple times but without success, eventually when trying to boot into recovery to try again i was greeted with an unthemed TWRP recovery asking for a password despite the fact that i had a custom theme and multirom installed I tried to proceed anyways but was greeted with E: unable to mount storage
In desperation i tried to solve this problem and found this
Wrong thread.
d
Click to expand...
Click to collapse

[SOLVED] Google Apps Not Working And Recovery Refusing To Open

About two weeks ago just before CyanogenMod's announcement of its closure I updated my Moto G2015 (1GB) to the latest nightly, which was CM14.1 released on the 25th of December, with its corresponding GAPPS version also released on the 25th of December (ARM, android 7.1, Full)
Yesterday the 7th of January my Google Apps decided that they didn't want to open, at first I thought it was just updating and since my battery was low I plugged in my device, I later realised that my device randomly went to a boot loop and stayed there. I grew impatient so I restarted the phone and went to the Recovery Mode (To Re-Flash the ROM), but to my annoyance the recovery (TWRP) just stayed on the 'Teamwin' logo forever, it would randomly go black then return to that logo. infuriated I turned on my phone and went to backup/reset and clicked 'factory reset'. it annoyingly booted me into recovery to reset the device, which of course I couldn't do.
Now the simple answer would have been for me to go and wipe the cache and data from 'google play services' and or 'launcher3' but I did, either it always shows 'calculating' preventing me from clicking 'manage space' or clearing 'cache' or when it did finally show, after I did click the button for the cache and or data to be cleared it would say 'calculating', and a quick check would discover that nothing was actually cleared.
Kind Regards, and Thank You to any help recieved,
NotSoGreat

Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.

acejavelin said:
Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.
Click to expand...
Click to collapse
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.

NotSoGreat said:
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.
Click to expand...
Click to collapse
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...

acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
I'll try now.

acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
Right, so I reinstalled and flashed the latest version TWRP, when I opened into it, it took about 1 minute before it opened up, it ran a quick operation that I just glimpsed, it looked like it was wiping cache and user data, my phone was rebooted and I was right, my phone had been reset for the second time today (I'm almost a pro at reinstalling all my apps). I rebooted into the recovery and Look and Behold, it was working.
Thanks slot for your help and time.

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.