Database Info

Type password to decrypt storage?

I've had my Nexus S for a year now and it's been pretty problem free... When it had Gingerbread it had the odd reboot glitch but since ICS it's been solid. I have the bootloader unlocked and had root. I had tried out a couple of custom ROMs and had gone back to stock ICS in anticipation of JB rolling out in July. I got the OTA push of JB in mid July and after a factory refresh have had no problems with the phone until yesterday.
I was typing a text message and my phone rebooted in my hand. It never did complete booting and left me at a prompt that stated "Type password to decrypt storage" and nothing would make this phone boot! Also, since the JB update I no longer had root and Clockwork Recovery no longer worked because I didn't have root... which I wasn't worried about up until now. I had to tether the phone to my laptop reset Recovery using the SDK tools and then wipe everything and reset the phone and reinstall all my apps. Funny thing is I've not been able to find much about this from any of the forums I read frequently... seems there aren't many who have experienced this.
Just wondering if anyone else has run into it...

it's happend for me too. i had to wipe cache and fixed.

Same thing happened to my Nexus S. I have no idea how it came into this "type password to decrypt storage" damned state. I'm trying all passwords and PINs I know but none is working! I'm trying to avoid a factory reset.... Isn't there a way to log in and override this thing, something like forgotten password in emails???

still no solution for this? i've wiped data and cache and still no fix!

I'm facing the same issue: woke up this morning to find my phone asking for a password in order to decrypt storage. Very annoying, since I don't have a very recent backup.
Running CM10.1 nightly 0210 with stock CM kernel. I tried reinstalling CM and wiping cache, but that didn't help. I'll see if I can fix it and and will repost here if/how I fixed it.

gearjunkeez said:
still no solution for this? i've wiped data and cache and still no fix!
Click to expand...
Click to collapse
If you can boot into bootloader (fastboot), try to flash Google factory image.
untar (unrar/7-zip) the tar file and flash the update zip within. This should wipe everything including system.
Code:
fastboot -w update image-soju-jzo54k.zip

kooske said:
I'll see if I can fix it and and will repost here if/how I fixed it.
Click to expand...
Click to collapse
It seems that there is no other solution for this other than a wipe data/factory reset. It's the solution offered in a googleGroups discussion as well. (Can't post links yet, not enough posts...)
Luckily after re-installing ROM and gapps all my apps were restored, and I was able to extract all my pictures and some backups on the sdcard using the mount USB option in CWM. So no big data loss for me.
It's a strange issue though, and should've been solved long ago. First occurrence I found was somewhere in February 2012, that's a year ago!

HELP!
I just had the same thing happen to my phone. Can you please dumb down what you just said for me? The only part I care about is how to recover my pictures. I haven't done the factory reset yet as I've been trying every password I can think of and now see that it is a bug and not something I have done. Anyway, I have 3 gigs of pictures of my 18 month old that I will cry if I lose so if you can help me recover them I would really appreciate it. I have tried hooking my phone up to my computer in it's encrypted state and it does not register. Please explain what you did in simplified terms for me as I have no idea what ROM or CWM means. Thanks!
kooske said:
It seems that there is no other solution for this other than a wipe data/factory reset. It's the solution offered in a googleGroups discussion as well. (Can't post links yet, not enough posts...)
Luckily after re-installing ROM and gapps all my apps were restored, and I was able to extract all my pictures and some backups on the sdcard using the mount USB option in CWM. So no big data loss for me.
It's a strange issue though, and should've been solved long ago. First occurrence I found was somewhere in February 2012, that's a year ago!
Click to expand...
Click to collapse

Ampe A85 A31S - 0.00kbs, format and factory reset every boot

Hey guys. Forgive my noobity but I could do with some help and might have a unique problem although I dare say someone has had this or similar.
Firstly, after putting a 64GB stick in my tablet the other day, it all went badly wrong. I had done it before with my previous 64GB that had been playing up so I sent it back and got a new one. The new one seems to be where it all went pear shaped. I might add, the 64GB is for my phone really but my phone cam was playing up so I was swapping it over and stuff... anyway the card itself seems fine in my phone.
Anyways... now my ampe tablet is suffering some strange effects that have changed. initially it would not boot up unless I redone it with the official firmware.. but then wouldn't boot up again, unless I did the same thing over and over. then one time it just refused to boot up past the initial boot screen. I gave up for weeks then picked it up again two days ago.
Now I give it the firmware installed using pheonix again and it booted up. Ahh I thought... lets play. Now I plug it into the pc but the pc says I need to format the 5GB internal partition. So I did. I then looked how to fix the fact that the tab still says it has 0.00kbs internal storage in settings. Then after a while it came up saying 5GB so i copied some files onto it.. great. But I still can't install apps as I found when trying to do this tested working fix http://www.youtube.com/watch?v=sJlpek6w624
I then read about using android commander to move busybox from xbin to bin in the system folder but mine is already there.
So now I am stuck. I can't test if my tab is rooted for the youtube link fix above although this is what I said to Nayeem on youtube:
================
Hi Nayeem. I'm really struggling with this. At first my tab was staying at the 2nd initial boot up screen after I put in a 64GB SD card. Using pheonix I managed to get it to boot by reinstalling the updated official rom from szampe but every reboot back to square one. I left it alone for weeks and came back to it, reinstalled the factory rom again and now it will boot up everytime but it has factory reset every time. I cant run the apps you supply for some reason. Everytime I have rebooted the tab, and connected back to pc it says I need to format the internal 5GB partition. I don't know if I have rooted it properly as I can't check. The commands you give above, work as it changes the location proven when I 'get' it. I'm really stumped. I'm trying out a method someone said about moving busybox from sys/xbin to sys/bin but it's already there (using android commander) so I am really stumped now. When I format the partition, it allows me to copy files to it.
================
So far I am stuck with boot up being a factory reset and the partition needs formatting and although the tablet seems a little laggy, everything I have tried works including wifi and incoming email alerts after logging into google account for playstore but no apps will install or update. the best warning I get is there is no memory to install anything and Nayeems method of moving the install location to the sd card seems to work but nothing will install still saying NOT INSTALLED when I try.
Sorry for the long winded thing but I am really new to all of this.
My hat is off to you if you read all of this and can offer a solution so i can give this tablet back to the kids.

Do you have an installed recovery
Try installing a recovery and wipe data and cache. If it does not work u have to repartition ur tablet

nelsontky said:
Try installing a recovery and wipe data and cache. If it does not work u have to repartition ur tablet
Click to expand...
Click to collapse
I am gonna look into this tonight and see what I can find out. I really don't know exactly what I am doing outside of getting pheonix up and sending a standard rom back to it as previously mentioned.
How would I repartition it ? Sounds stupid asking as i can build pcs... just want to make sure I am doing the correct method.

[Q] Recovery is broken??? I Don't Know.. Please Help

So I bought a Nexus 5 off of craigslist for a pretty good price about a week ago and he had already rooted and installed a custom recovery onto the phone. He had some sort of rom that I didn't like so I decided to flash my own. So I downloaded cyanogen mod (the latest nightly build at the time) and flashed it along with g apps and rebooted the phone. When I it was turning on it said "upgrading apps xxx out of xxx." I was very confused because coming from a Nexus 4 and flashing many ROMs I have never seen this before. When the phone finally powered on it started giving me errors every 5 seconds and I realized soon after that I had my previous apps from the old rom still installed and everything else was in place. I managed to get into settings after clicking ok to errors every 5 seconds and saw that my ROM did indeed change to Cyanogen Mod. I decided to try to factory reset the phone through the settings menu and that fixed the phone seemingly until today. I tried installing another rom but this one is giving me multiple errors and then rebooting my phone. I could not get into the settings to factory reset the phone through there.
I was thinking that maybe the recovery was broken but I'm not sure of how to fix it. I tried to find a flashable recovery but only found IMG versions which I don't know how to install. Is there a possibility of any other issues? I am resetting/wiping cache/wiping dalvik cache every time in that order. When I'm installing the roms it says something about e:/ volume not existing or not being found could that be the problem? I don't recall ever seeing this on my nexus 5. If anyone knows how I could fix this issue I would greatly appreciate your help.
Thanks, Alex:laugh::laugh:

alexdzk said:
So I bought a Nexus 5 off of craigslist for a pretty good price about a week ago and he had already rooted and installed a custom recovery onto the phone. He had some sort of rom that I didn't like so I decided to flash my own. So I downloaded cyanogen mod (the latest nightly build at the time) and flashed it along with g apps and rebooted the phone. When I it was turning on it said "upgrading apps xxx out of xxx." I was very confused because coming from a Nexus 4 and flashing many ROMs I have never seen this before. When the phone finally powered on it started giving me errors every 5 seconds and I realized soon after that I had my previous apps from the old rom still installed and everything else was in place. I managed to get into settings after clicking ok to errors every 5 seconds and saw that my ROM did indeed change to Cyanogen Mod. I decided to try to factory reset the phone through the settings menu and that fixed the phone seemingly until today. I tried installing another rom but this one is giving me multiple errors and then rebooting my phone. I could not get into the settings to factory reset the phone through there.
I was thinking that maybe the recovery was broken but I'm not sure of how to fix it. I tried to find a flashable recovery but only found IMG versions which I don't know how to install. Is there a possibility of any other issues? I am resetting/wiping cache/wiping dalvik cache every time in that order. When I'm installing the roms it says something about e:/ volume not existing or not being found could that be the problem? I don't recall ever seeing this on my nexus 5. If anyone knows how I could fix this issue I would greatly appreciate your help.
Thanks, Alex:laugh::laugh:
Click to expand...
Click to collapse
Did you wipe data and cache before flashing the new rom?

This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?

I see your doing a clean install. I'd return it to stock and start over, especially considering you bought the phone used. Who knows what's been on it. See this http://forum.xda-developers.com/showthread.php?p=47156064

mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
jd1639 said:
I see your doing a clean install. I'd return it to stock and start over, especially considering you bought the phone used. Who knows what's been on it. See this http://forum.xda-developers.com/showthread.php?p=47156064
Click to expand...
Click to collapse
I'll try this then if it doesnt work ill try the factory reset/ relock whatever, thanks.

mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
no its CWM

You didn't wipe/factory reset.
Sent from my Nexus 5 using Tapatalk

mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
housry23 said:
You didn't wipe/factory reset.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, I did. I said it in my post.

alexdzk said:
Yes, I did. I said it in my post.
Click to expand...
Click to collapse
I see. Well, if you really did do a factory reset before flashing a new Rom, then maybe you have an old version recovery, or something is borked with your phones partitions. Honestly, buying a used one like that, I would do a full factory restore by flashing the stock images(sticky in general for directions) but don't relock the bootloader. This will erase everything and repartition the phone. Then install recovery and flash away.
Sent from my Nexus 5 using Tapatalk

housry23 said:
I see. Well, if you really did do a factory reset before flashing a new Rom, then maybe you have an old version recovery, or something is borked with your phones partitions. Honestly, buying a used one like that, I would do a full factory restore by flashing the stock images(sticky in general for directions) but don't relock the bootloader. This will erase everything and repartition the phone. Then install recovery and flash away.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I fixed the issue by flashing a new recovery through adb already and it works fine now thank you. I guess it was really my recovery that was broken.

alexdzk said:
I fixed the issue by flashing a new recovery through adb already and it works fine now thank you. I guess it was really my recovery that was broken.
Click to expand...
Click to collapse
Good. Glad you got it worked out. Was probably an old build of whatever recovery and because of the way KitKat changed things, there were a lot of problems wiping when the phone first came out. If you find any more good deals on your local Craigslist, PM me. I want a black n5 instead of my white one.
Sent from my Nexus 5 using Tapatalk

[Q] No External Storage error after flashing Modem

Hey guys,
I searched through here and online, and can't seem to find a solution or REASON for this to have happened, so I made an account! Woo.
I flashed my rooted, cyanogenmod running N5's modem from 4.4.4 to KOT49E and after rebooting the phone, it proudly states I have low storage, that the external storage can't be found, and then swiftkey loses its ****, google play store crashes over and over even though I've not opened it etc etc.
I've wiped the partition cache and the dalvik cache, but it's still not doing ****. I'd really like to avoid reloading a rom on there if I can help it as I've not backed up in a week or so, and I'm sure you all know how much of a ballache THAT is!
so...Thoughts?

First, your should always make a nandriod before flashing anything new.
Can you flash the same modem as you had before?
Sent from my Nexus 5 using XDA Free mobile app

myles_dobson said:
Hey guys,
I searched through here and online, and can't seem to find a solution or REASON for this to have happened, so I made an account! Woo.
I flashed my rooted, cyanogenmod running N5's modem from 4.4.4 to KOT49E and after rebooting the phone, it proudly states I have low storage, that the external storage can't be found, and then swiftkey loses its ****, google play store crashes over and over even though I've not opened it etc etc.
I've wiped the partition cache and the dalvik cache, but it's still not doing ****. I'd really like to avoid reloading a rom on there if I can help it as I've not backed up in a week or so, and I'm sure you all know how much of a ballache THAT is!
so...Thoughts?
Click to expand...
Click to collapse
Are you using CWM recovery? CWM has a bug that reduce your storage to 250mbish size. If that is the case then switch to twrp or philz touch and do a factory reset.

Nexus 5 less storage than it should be

Hi, I find it strange to ask this question because i don't even know how this thing is possible, but here's the thing: I don't really know when exactly it happend, but now if I check my device storage I can see that I have 12.5 GB to use (total, not just available)
The device I bought is 32GB originally. I know that the OS should take few GB of the total storage because I checked it when i bought the device and found that before I did anything - I had less than 32 GB, something like 26 and it's normally.
as i said, i dont know how it's even possible. maybe there's a problem with the sd card or something but i don't know what to do and how to solve this situation.
thanks from above!

All you need to do is flash the stock recovery, if you're not already using it, and then wipe cache and do a factory reset in it. It's not that uncommon of a problem if you've recently flashed the factory image and didn't do a full wipe.
Sent from my Nexus 9 using XDA Free mobile app