Database Info

[Q] Can't use phone -- Type password to decrypt message

I'm at a loss here. I was using my phone as normal today, no issues all day. When I tried loading Facebook to respond to a comment I suddenly started getting a lot of stopped process errors. Pretty much all were GAPPS processes. Then my phone rebooted. After it booted back up (no issues, no subsequent reboots, saw the HTC screen and the ViperXL screen), my phone loads to an empty lock screen with the default ViperXL background and just the ring. The phone is also now in Airplane mode and showing the time to be 5 hours ahead. When I unlock the phone, I am met with a screen that tells me to "Type password to decrypt". I have never created a password. Nothing works. I can only make emergency calls. No amount of rebooting or wiping cache or dalvik in TWRP works. I have not updated this phone recently and when I try to restore from backup none of my backups show up in the TWRP folder. I cannot do a factory reset as I receive errors when attempting to mount the SD card. I've read several other forum posts for similar issues for different devices but none of what they try works. My computer recognizes when the phone is connected, but it does not mount the SD Card and I cannot put the ROM .zip file back onto it to reinstall from recovery. I cannot adb as it doesn't recognize the device as being connected. I can initiate fastboot and it does see my device, but when I try to erase the userdata partition or anything else I receive an error that states "failed (remote: not allowed)". All instincts would lead me to believe it's a locked bootloader, but the bootloader screen still shows as UNLOCKED. I am S-Off on HBOOT 1.14.0002. Currently ViperXL 3.2.6 is installed with ElementalXL 5.4 for the kernel and the AT&T 3.18 Radio. Again, I have not TOUCHED my setup in over 3 weeks, with the last update being the updated radio. I am freaking out without any means to communicate with my family and just want an operational phone again. Any ideas/thoughts/suggestions would be greatly appreciated.

Pdj7969 said:
I'm at a loss here. I was using my phone as normal today, no issues all day. When I tried loading Facebook to respond to a comment I suddenly started getting a lot of stopped process errors. Pretty much all were GAPPS processes. Then my phone rebooted. After it booted back up (no issues, no subsequent reboots, saw the HTC screen and the ViperXL screen), my phone loads to an empty lock screen with the default ViperXL background and just the ring. The phone is also now in Airplane mode and showing the time to be 5 hours ahead. When I unlock the phone, I am met with a screen that tells me to "Type password to decrypt". I have never created a password. Nothing works. I can only make emergency calls. No amount of rebooting or wiping cache or dalvik in TWRP works. I have not updated this phone recently and when I try to restore from backup none of my backups show up in the TWRP folder. I cannot do a factory reset as I receive errors when attempting to mount the SD card. I've read several other forum posts for similar issues for different devices but none of what they try works. My computer recognizes when the phone is connected, but it does not mount the SD Card and I cannot put the ROM .zip file back onto it to reinstall from recovery. I cannot adb as it doesn't recognize the device as being connected. I can initiate fastboot and it does see my device, but when I try to erase the userdata partition or anything else I receive an error that states "failed (remote: not allowed)". All instincts would lead me to believe it's a locked bootloader, but the bootloader screen still shows as UNLOCKED. I am S-Off on HBOOT 1.14.0002. Currently ViperXL 3.2.6 is installed with ElementalXL 5.4 for the kernel and the AT&T 3.18 Radio. Again, I have not TOUCHED my setup in over 3 weeks, with the last update being the updated radio. I am freaking out without any means to communicate with my family and just want an operational phone again. Any ideas/thoughts/suggestions would be greatly appreciated.
Click to expand...
Click to collapse
You're s-off. Boot bootloader/fast boot and ruu
Sent from my One X using xda app-developers app

We're you connected to an exchange server? It is the only thing that I know of that could wipe or encrypt your phone.
Sent from the HOXL dimension of S-OFF

Well this is a new one on me. Not sure what happened or how I did it, but as you can see below, I managed to get my phone working again. I left it alone for a bit while I had dinner. Once done, I tried once again to do a factory reset in TWRP and all indications led me to believe that it had failed once again (received a failed notification). I then rebooted the phone and this time it brought me to the HTC setup screens where I was to enter all my info. I got past that and connected to my wifi. I then noticed my phone wouldn't get a network connection with AT&T so I downloaded and refreshed the 3.18 radio and after reboot it connected to LTE without issue. Since I lost all my data I am now in the process of reinstalling my apps. I had been meaning to do a full wipe eventually as things were getting a little sluggish, so I guess this just kicked me in the pants a bit. Bummed I lost my photos I took today, but what can you do?
To answer your question, no, I do not have it setup with Exchange. My company does not allow Android devices to connect to Exchange, only iPhones via ActiveSend so that wasn't it. This has happened to several others, but they were always in the act of flashing something or making changes when it happens, never just normal use and a magical reboot kills everything. This of course makes me nervous that it'll happen again, but seeing as I am in the market for the One, I might not have to worry much longer. Thanks for the suggestions.
Sent from my HTC One X using xda app-developers app

As long as you can get into bootloader you can always run the ATT 3.18 RUU.
Sent from the HOXL dimension of S-OFF

Stuck at "erasing" when doing a factory reset?

Anyone else had issues performing factory resets? My Nexus 5 seems incapable of completing it. So far I have tried doing a factory reset from the settings menu 4 times. Every single time it locks up on the erasing step. I don't mean it takes a little longer. I have let it sit for almost half an hour and the little android robot sits there taunting me.
Every time I have had to manually go into the bootloader and sideload a factory image, which works fine.
Any ideas why this problem is occurring? Faulty memory maybe?

Same issue here, phone is getting nice and warm but the little robot just sits there twiddling his antennae. Forced restart either normally or into recovery mode lands me right back on the erasing screen, looks like nothings going to happen unless I intervene another way. Any ideas?

Try pushing the system.img using fastboot. Might be best to start over and do a clean install.

Have you tried doing a factory reset in recovery instead?
Sent from my Nexus 5 using Tapatalk

Same problem
I have the same problem with the loop at the erasing screen. It will not go into recovery so that I can fix it. I tried flashing the Stock Rom again but no use. Please help me or at least give me some pointers what to try next.
jizkidjnr said:
Same issue here, phone is getting nice and warm but the little robot just sits there twiddling his antennae. Forced restart either normally or into recovery mode lands me right back on the erasing screen, looks like nothings going to happen unless I intervene another way. Any ideas?
Click to expand...
Click to collapse

martinancevski said:
I have the same problem with the loop at the erasing screen. It will not go into recovery so that I can fix it. I tried flashing the Stock Rom again but no use. Please help me or at least give me some pointers what to try next.
Click to expand...
Click to collapse
I have the same problem

I'm sure you wait a long time...but if not, mine probably took 10-15 minutes to finish...
Sent from my Nexus 5 using xda app-developers app

i have the same problem

What is your recovery? Version # also? How did you root? <--- this goes to the rest of you guys too because it seems like its happening to more than one person.
Follow this: Maybe flash the stock recovery found in here http://forum.xda-developers.com/showthread.php?t=2513701
fastboot flash recovery C:/image-hammerhead-krt16m/recovery.img
^^ the command
edit: on second thought start over.

lpforte said:
Anyone else had issues performing factory resets? My Nexus 5 seems incapable of completing it. So far I have tried doing a factory reset from the settings menu 4 times. Every single time it locks up on the erasing step. I don't mean it takes a little longer. I have let it sit for almost half an hour and the little android robot sits there taunting me.
Every time I have had to manually go into the bootloader and sideload a factory image, which works fine.
Any ideas why this problem is occurring? Faulty memory maybe?
Click to expand...
Click to collapse
hello
I have the same exact problem
I'm completely stock and I want to reset all so I do factory reset from menu setting, backup & reset
And since, my nexus stucked in "erasing...."
I have tried flashing factory image according to this guide, succeeded, but then still stucked in android logo with endless progress bar (but this time without "erasing....")
Need help how to restore it
All I want is to factory reset
How did you actually sideload factory image?
thanks

iori said:
hello
I have the same exact problem
I'm completely stock and I want to reset all so I do factory reset from menu setting, backup & reset
And since, my nexus stucked in "erasing...."
I have tried flashing factory image according to this guide, succeeded, but then still stucked in android logo with endless progress bar (but this time without "erasing....")
Need help how to restore it
All I want is to factory reset
How did you actually sideload factory image?
thanks
Click to expand...
Click to collapse
ADB sideload: place the rom you want to flash in the fastboot folder and in the phones recovery select adb sideload, then on the pc in cmd type: adb sideload namerom.zip and it will start flashing.

gee2012 said:
ADB sideload: place the rom you want to flash in the fastboot folder and in the phones recovery select adb sideload, then on the pc in cmd type: adb sideload namerom.zip and it will start flashing.
Click to expand...
Click to collapse
thanks
but i finally found out that the stock recovery was somehow corrupted after factory reset
then I unlocked the bootloader and flashed TWRP recovery, and voila! my device booted normally

Nexus 5 hung at reset
iori said:
hello
I have the same exact problem
I'm completely stock and I want to reset all so I do factory reset from menu setting, backup & reset
And since, my nexus stucked in "erasing...."
I have tried flashing factory image according to this guide, succeeded, but then still stucked in android logo with endless progress bar (but this time without "erasing....")
Need help how to restore it
All I want is to factory reset
How did you actually sideload factory image?
thanks
Click to expand...
Click to collapse
Exactly the same problem here. Nexus 5 running 4.4.2 kept powering off randomly roughly once a day. Attempted a factory reset and it got stuck at erasing. Having unlocked the bootloader and following the steps to unlock and reboot, I have a progress bar with the animated android icon, apparently stuck at the same stage, but without the "erasing" caption.
As far as I'm concerned, I can nothing with the phone at present short of taking it back, though they'll likely take issue with my attempts to rectify myself

mannschaftpag said:
Exactly the same problem here. Nexus 5 running 4.4.2 kept powering off randomly roughly once a day. Attempted a factory reset and it got stuck at erasing. Having unlocked the bootloader and following the steps to unlock and reboot, I have a progress bar with the animated android icon, apparently stuck at the same stage, but without the "erasing" caption.
As far as I'm concerned, I can nothing with the phone at present short of taking it back, though they'll likely take issue with my attempts to rectify myself
Click to expand...
Click to collapse
I'll add that I've also tried the Nexus Root Toolkit v1.8.0 to flash stock. Appears to go fine, recreating the file system and loading software, then as soon as it gets to the "erasing cache" step it just sits there for hours and makes no progress.

I know I probably shouldn't promote toolkits but you can always try this. Seems to have worked for a lot of people.
http://forum.xda-developers.com/showthread.php?t=2513937
Sent from The Deathstar

Same thing happened to me yesterday. My N5 is rooted, running stock rom and recovery. I had some corrupted app date showing in Titanium that I could not remove that were causing a Play store issue for me. I backed up my phone with TB and ran a factory reset in settings. The phone was stuck on the 'erasing' screen for maybe 20 minutes, so I put the phone in fastboot and from there back into recovery. This took me back to the 'erasing' screen to my dismay. I put the phone down and started searching for a solution online, but then I noticed after about 7 minutes the erase process had finally finished on its own and the phone rebooted normally again.
Based on what others are saying in this thread it appears the factory reset process via settings or stock recovery can hang sometimes. If you power off, start the phone in fastboot and select recovery again, I'm guessing the factory reset process restarts and hopefully it will then work properly the next time, like it did for me.

Well when I did a factory reset from settings, it took nearly 20-25 minutes to finish. The next time I did a reset, it completed within 10 minutes
I guess this problem occurs randomly.

Be patient
My guess is that you just need to be patient -- my device took nearly 45 minutes to reset. It seems to me that the time required is proportional to either the amount of data or the number of files you have on the device. My device had a mix of large files (such as musics and photos) and many many small files (sensor data log files), so it's hard for me to say which of those contributed more to the long reset time.

Based on what others are saying in this thread it appears the factory reset process via settings or stock recovery can hang sometimes. If you power off, start the phone in fastboot and select recovery again, I'm guessing the factory reset process restarts and hopefully it will then work properly the next time, like it did for me.
Click to expand...
Click to collapse
This worked for me too. On the initial 'Return to factory defaults' it got stuck for about 45 minutes. I then follow the advice above:
- Put the N5 in Fastboot by pressing: Vol. Up + Vol. Down + Power
- Select: Recovery and press on Power to proceed
- Phone reboots, still into the 'Androidman' but it seems that the 'Return to factory defaults' also restarts.
- Wait about 10 minutes and the Phone powers down automatically. Upon startup you enter the 'Initial configuration menu' so the factory reset has been completed.

Still stuck on Erasing screen, running out of options
Hello,
I am a newbie with zero developer knowledge and received my Nexus 5 in the mail yesterday. I liked the phone specs and that is the only reason I got it. I left it alone while it charged up and the first thing I did once it was finished was perform a Factory Reset (it was a "like new" phone so I just wanted to be safe) and have been stuck on the Erasing screen ever since. Pressing Vol- and Power button does take me to the bootloader screen, however, any option I choose by pushing the power button, such as Recovery Mode, sends me back to the Erasing screen. Pushing Vol+, Vol-, and Power shuts the phone off completely. Holding the Power button down does nothing more than restart the phone into the Erasing screen. I have also let the phone die twice and as soon as it has enough juice to come back on, it goes straight to the Erasing screen. Everything on the phone is stock and it is completely unrooted. The bootloader screen also indicates it is unlocked. I have attempted to flash it as per instructions I have found on here but I am unable to download the stock factory images. It gets to about 90% before the install fails and I have tried to install three times already. I do have the 15 Second ADB installed, however. I assumed the install of the factory images failed because I don't have WiFi and I'm running completely off of limited 3G data (I live in the middle of no where with no high speed internet to speak of). So in lieu of all that I have attempted, is there ANYTHING at all that can be done to get the phone off of this Erasing screen? Or do I just need to try and return it because it's useless at this point? I did at first let the process run but it's now been 24 hours stuck on this Erasing screen with no improvement. I'm fairly certain it runs KitKat 4.4.0.

Freezing/bootloop even after stock RUU

Hello,
I'm running out of ideas to solve my problem with my Sensation, maybe you can help. I was on my beloved ViperS5 ROM and it crashed while browsing due to memory overload or something. After several boot attempts and removing the battery I managed at least to get into bootloader/recovery (ended up with a black screen or freeze 8/10 times). Reinstalled the ROM and it kept crashing at the configuration screen, resulting in a boot loop. So I tried a few other ROM's, exactly the same results.
My last hope was going back to stock using RUU, same problem at the configuration screen, but I managed to boot after few reboots. The phone still crashes after few minutes, when I try to start any app, resulting in a boot loop/black screen/HTC logo freeze. (tried to remove the SD card, it didn't help)
Any ideas how to fix this?

did you leave the device switched off for a long time?
if not do it and then try to switch it on
probably it is still overheated when you are trying to boot it
leave it for 10-15 minutes
best wishes

Maybe it's really damaged from overheat, cause it even crashed in recovery once, so I guess I'm ****ed. I will try to leave it switched off for a few hours, but I doubt it will help. Thanks so far.

Now I get random crashes even in recovery (4EXT, also tried TWRP), I managed to install some custom ROM's, but can't even boot properly after flashing (keeps freezing or restarting in the boot process). My Sensation is JuopunutBear S-OFF, had no problems with flashing ROM's before that. So I guess it is a hardware failure.

frgntz said:
Now I get random crashes even in recovery (4EXT, also tried TWRP), I managed to install some custom ROM's, but can't even boot properly after flashing (keeps freezing or restarting in the boot process). My Sensation is JuopunutBear S-OFF, had no problems with flashing ROM's before that. So I guess it is a hardware failure.
Click to expand...
Click to collapse
If memory serves correctly you should be able to get a logcat from the phone while its in recovery. it might shed come light on what is producing the failures, but its definitely sounding like a hardware failure. Were you overclocked?

How do I get a logcat?
I'm able to stay in recovery for enough time to wipe data, then it randomly crashes or when I try to flash a rom (-> black screen, remove battery to get it back on).
I couldn't even install stock RUU at the first attempt - freezing the whole installation process. No overclocking, also tried the original battery (bought a new one), with/without sdcard/sim -> still crashing.
Edit: Ok, there's a guide for logcat on xda. I will post results after work as soon as I get back home .

How is your sensation going on?
frgntz said:
How do I get a logcat?
I'm able to stay in recovery for enough time to wipe data, then it randomly crashes or when I try to flash a rom (-> black screen, remove battery to get it back on).
I couldn't even install stock RUU at the first attempt - freezing the whole installation process. No overclocking, also tried the original battery (bought a new one), with/without sdcard/sim -> still crashing.
Edit: Ok, there's a guide for logcat on xda. I will post results after work as soon as I get back home .
Click to expand...
Click to collapse
hello, may i know how is your sensation device condition? recently my device having the same issue as yours and out of idea to solve it. before i send device to repair i hope can get some other solution which i miss. thanks in advance if able to provide further infomation.

Cwm-Based 6.0.5.0 Can't Mount Data After 0703 Nightly Boot Fail

Dudes,
I was running CM 0701 nightly fine and decided to boot to CWM-based recovery and flash latest nightly from 0703. It got about 2/3 the way through updating apps after boot and froze. Then screen stayed black, but would backlight. Was unresponsive to touch, but I could get it to take screenshots (at least I could hear the sound made by triggering one). I longpressed the power button to force reboot and entered bootloader. Finally I could see the screen again. I thought all was better and it just needed a reboot so I reboot again and let it boot. Still no screen. So I longpressed to reboot, got into bootloader, then revovery... and tryed to reflash nightly from 0701 but it won't access my "/sdcard" because it won't mount. Same error ("Error mounting /data!) when I try to fatory reset or mount/unmount.
WTH?!
Anybody have any ideas what broke this? What it a change in last two nightlies? A change to the recovery?
I'm going to try http://forum.xda-developers.com/google-nexus-5/help/help-e-mount-sdcard-cwm-6-0-4-5-trying-t2802715 when I get home... in way too many hours. Sadface.
I also posted this in CM Forums: http://forum.cyanogenmod.com/topic/...cant-mount-data-after-0703-nightly-boot-fail/

Firstly try and fastboot flash a stock cache.img

rootSU said:
Firstly try and fastboot flash a stock cache.img
Click to expand...
Click to collapse
Thanks @rootSU. Ultimately and unexpectedly the phone came back to life before I could get to a computer with adb access. I had tried rebooting several times before, but magically after about 6 hours of downtime (no charge or anything) it rebooted up fine. It was a little shaky and slow at first, and ran the update apps process again on the next boot but has since be stable. No flashing. A couple reboots. All fine.
Thanks to the XDA community for existing and providing such a reassuring resource for knowledge and problem solving!

[Update 4/3: Logs] N5 works normally -> stuck on splash screen -> have to reflash ROM

[Update 4/3: Logs] N5 works normally -> stuck on splash screen -> have to reflash ROM
My Nexus 5 is having a problem that is just confusing the hell out of me.
To summarize the issue...
1. Phone will get stuck on "Google" splash screen (written in white) on bootup.
-at this point, I can reach bootloader and recovery
-clear cache/format cache does not alleviate problem
-factory reset does not alleviate problem
-fastboot flash-all does not normally alleviate problem
-only flashing a ROM via TWRP works
2. ROM flashed via TWRP, things work like normal for ~4-24 hours. At some point, there will be a random reboot. Usually, this is while under stress (playing a game, updating apps). It will reboot normally and continue to work like normal for some time. But it's a ticking time bomb. There will be another random reboot at some point, often while idle - definitely not workload-related. This second one will get me stuck on the Google splash screen again, with the only way of fixing being re-flashing the ROM via TWRP.
These symptoms are basically the same regardless of the ROM - I've tried factory images, a stock-ish ROM with Gapps removed from XDA, and CyanogenMod. It seems like it could be a hardware problem, but I don't have a clue what it would be since it is so consistently fixable, albeit temporarily. Does anyone have any troubleshooting suggestions or a clue as to what part of the phone is likely failing?

Post logs.

Elluel said:
Post logs.
Click to expand...
Click to collapse
Okay, so this afternoon I went to check on it after spending some time on the charger. The LED was lit, so I thought things would be fine. It just wouldn't wake up. It wasn't responding to various button presses, but the LED turned off after I held the power button. It took a lot more attempts than normal to get to fastboot, but eventually got there. I used fastboot boot to get to TWRP and retrieved last_kmsg, kernel_log, and logcat. Logcast was empty. Here are pastebins for the other outputs.
last_kmsg: http://pastebin.com/z2KG2aHW
kernel_log_output: http://pastebin.com/v7TZZKeb
Thanks for the help!

I'm going to bump this one time, since there are now logs posted which I think might provide some clear insights to those who know how to interpret them.