Related
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.
Hey guys. I've been around since the OG Droid, and I've never posted because I've been able to find the information by searching usually. But now I have a problem that I haven't been able to solve, and I was hoping someone could puzzle it out.
Right now I have a Nexus 5. I got it at launch and it's been perfect, with none of the issues others have had that required RMA. I unlocked the bootloader when I got it and loaded TWRP and rooted, but left it stock beyond that. About a week or so ago, I rebooted into recovery. While I was there, out of habit, I cleared cache and Dalvik. The thing is, it took 5-10 minutes to clear, and during that time I remembered that i had ART enabled. Now, I know others have had trouble with TWRP messing them up on a wipe, but this is where it gets interesting.
I rebooted when TWRP finished wiping. The boot animation spins the balls in once, then on the second time, there is color bleed forming a line across screen on the top and bottom of the boot animation. Again it spins, and it's fine, and then it does it again. Every second spin of the boot animation.
Eventually it booted in and I used the phone. An hour later, I got some force closes, it locked up, and then it rebooted into a bootloop. With the boot animation bleeding every second spin. When I got sick of that, I started trying to fix it by flashing factory images, locking and unlocking bootloader, fastboot erasing cache, userdata and system, fastboot formatting cache, userdata and system, trying TWRP again and wiping, trying CWM and wiping, wiping in stock recovery, anything and everything. I don't know how this is lasting past flashing factory images after an erase or a format, but every time I try to boot my Nexus 5, it either gets caught in a bootloop with varying amounts of boot animation graphics glitches, or it boots into Android and then after I spend a few hours setting up again, it will randomly hit me with graphical glitches in the OS or reboot, and then I'm stuck in the exact same boot loop.
Does anyone have any ideas that I haven't tried? I've done all of these multiple times, checked MD5's and SHA's, used different downloads of factory images, applied or not applied the update to 4.4.1, and nothing seems to work. Sometimes it's right away, sometimes it takes hours or even a day, but eventually I end up with force closes and a boot loop with bleeding graphics.
Thanks in advance for any possible help. I'll sit here quietly and wait for someone to tell me to just flash the factory image.
Kal5el said:
Hey guys. I've been around since the OG Droid, and I've never posted because I've been able to find the information by searching usually. But now I have a problem that I haven't been able to solve, and I was hoping someone could puzzle it out.
Right now I have a Nexus 5. I got it at launch and it's been perfect, with none of the issues others have had that required RMA. I unlocked the bootloader when I got it and loaded TWRP and rooted, but left it stock beyond that. About a week or so ago, I rebooted into recovery. While I was there, out of habit, I cleared cache and Dalvik. The thing is, it took 5-10 minutes to clear, and during that time I remembered that i had ART enabled. Now, I know others have had trouble with TWRP messing them up on a wipe, but this is where it gets interesting.
I rebooted when TWRP finished wiping. The boot animation spins the balls in once, then on the second time, there is color bleed forming a line across screen on the top and bottom of the boot animation. Again it spins, and it's fine, and then it does it again. Every second spin of the boot animation.
Eventually it booted in and I used the phone. An hour later, I got some force closes, it locked up, and then it rebooted into a bootloop. With the boot animation bleeding every second spin. When I got sick of that, I started trying to fix it by flashing factory images, locking and unlocking bootloader, fastboot erasing cache, userdata and system, fastboot formatting cache, userdata and system, trying TWRP again and wiping, trying CWM and wiping, wiping in stock recovery, anything and everything. I don't know how this is lasting past flashing factory images after an erase or a format, but every time I try to boot my Nexus 5, it either gets caught in a bootloop with varying amounts of boot animation graphics glitches, or it boots into Android and then after I spend a few hours setting up again, it will randomly hit me with graphical glitches in the OS or reboot, and then I'm stuck in the exact same boot loop.
Does anyone have any ideas that I haven't tried? I've done all of these multiple times, checked MD5's and SHA's, used different downloads of factory images, applied or not applied the update to 4.4.1, and nothing seems to work. Sometimes it's right away, sometimes it takes hours or even a day, but eventually I end up with force closes and a boot loop with bleeding graphics.
Thanks in advance for any possible help. I'll sit here quietly and wait for someone to tell me to just flash the factory image.
Click to expand...
Click to collapse
What kind of FC's? Random apps you have on your phone or specific apps? Also, do you have any kinds of system mods or complete stock? Do the weird graphical glitches on the bootanimation happen on the boot right after you flash the factory images? Or subsequent boots after the OS graphical glitches start?
As for right now, try running a factory image without installing anything apart from apps that come stock (don't install anything from the Play Store). If you can't live without some apps, try keeping them to the top 100 downloaded apps (ie. ones that have huge userbases and most definitely do not cause system issues).
Reason I say this is because the only three reasons I can think of are 1) app you have installed doesn't play nicely with stock Kitkat 2) something borked your EFS partition 3) your GPU is screwed.
thattypicalnerd said:
What kind of FC's? Random apps you have on your phone or specific apps? Also, do you have any kinds of system mods or complete stock? Do the weird graphical glitches on the bootanimation happen on the boot right after you flash the factory images? Or subsequent boots after the OS graphical glitches start?
As for right now, try running a factory image without installing anything apart from apps that come stock (don't install anything from the Play Store). If you can't live without some apps, try keeping them to the top 100 downloaded apps (ie. ones that have huge userbases and most definitely do not cause system issues).
Click to expand...
Click to collapse
Thanks for the reply.
The force closes are Google Search, or other Google stuff. I had the build.prop edited for 400 LCD density before this all started, but I haven't changed it back on subsequent flashes. So it is completely stock, not even rooted, and sometimes not even a custom recovery. 100% stock. The glitches happen on a clean flash from factory images, immediately on first boot. They get worse on subsequent boots after OS glitches start. In terms of what they look like, they are red or blue or white. Never other colors. On boot, they form dash lines bordering the boot animation. On the OS, they form lines above the default Google folder or vertical or horizontal lines mostly.
I've tried running just factory image with nothing installed except stock. I get the same results. Either I get glitches and force closes followed by a reboot right away, or it starts within a few hours of booting. If it reboots and gets back to OS without boot looping, the glitches in OS will be worse, and it will reboot into boot loops within a few minutes.
I still have my GNex, so I can afford to keep this phone stock until I resolve this. But it is basically unusable, and I don't want to RMA since I seem to have gotten one of the good ones, you know? This has to be a software problem, possibly a partition problem caused by TWRP. I was paying close attention to Metal_Head's thread, but he resolved his problems by wiping in TWRP, and that hasn't worked for me.
Kal5el said:
Thanks for the reply.
The force closes are Google Search, or other Google stuff. I had the build.prop edited for 400 LCD density before this all started, but I haven't changed it back on subsequent flashes. So it is completely stock, not even rooted, and sometimes not even a custom recovery. 100% stock. The glitches happen on a clean flash from factory images, immediately on first boot. They get worse on subsequent boots after OS glitches start. In terms of what they look like, they are red or blue or white. Never other colors. On boot, they form dash lines bordering the boot animation. On the OS, they form lines above the default Google folder or vertical or horizontal lines mostly.
I've tried running just factory image with nothing installed except stock. I get the same results. Either I get glitches and force closes followed by a reboot right away, or it starts within a few hours of booting. If it reboots and gets back to OS without boot looping, the glitches in OS will be worse, and it will reboot into boot loops within a few minutes.
I still have my GNex, so I can afford to keep this phone stock until I resolve this. But it is basically unusable, and I don't want to RMA since I seem to have gotten one of the good ones, you know? This has to be a software problem, possibly a partition problem caused by TWRP. I was paying close attention to Metal_Head's thread, but he resolved his problems by wiping in TWRP, and that hasn't worked for me.
Click to expand...
Click to collapse
"One of the good ones"? You clearly don't have "one of the good ones".
I think this doesn't have anything to do with anything you might have done wrong, I think the phone needs to be RMA...can you relock it?
Kal5el said:
Thanks for the reply.
The force closes are Google Search, or other Google stuff. I had the build.prop edited for 400 LCD density before this all started, but I haven't changed it back on subsequent flashes. So it is completely stock, not even rooted, and sometimes not even a custom recovery. 100% stock. The glitches happen on a clean flash from factory images, immediately on first boot. They get worse on subsequent boots after OS glitches start. In terms of what they look like, they are red or blue or white. Never other colors. On boot, they form dash lines bordering the boot animation. On the OS, they form lines above the default Google folder or vertical or horizontal lines mostly.
I've tried running just factory image with nothing installed except stock. I get the same results. Either I get glitches and force closes followed by a reboot right away, or it starts within a few hours of booting. If it reboots and gets back to OS without boot looping, the glitches in OS will be worse, and it will reboot into boot loops within a few minutes.
I still have my GNex, so I can afford to keep this phone stock until I resolve this. But it is basically unusable, and I don't want to RMA since I seem to have gotten one of the good ones, you know? This has to be a software problem, possibly a partition problem caused by TWRP. I was paying close attention to Metal_Head's thread, but he resolved his problems by wiping in TWRP, and that hasn't worked for me.
Click to expand...
Click to collapse
HIGHLY doubt its a software issue at this point. Considering your phone is completely stock, the crashes are unrelated to the phone app, that takes out app interference/EFS issues. Also, considering it happens on first boot, 99.99% sure it's hardware. Relock and send it back to Google. If you really want to, try CWM and see if that does anything, but I doubt it. In my experience, CWM causes more trouble than TWRP. Computers are complex little devices, it could be a bad CPU that has a small sector of the transistors not working or something like that. Bad RAM even?
So you guys think it's a hardware issue? It's possible, I guess. But it started after TWRP messed up on wiping Dalvik, so I figured it was a partition problem. I can relock it, I'll just have to reset the tamper flag. Was really hoping this was a fixable software problem.
I think you don't have the latest TWRP, which causes some issues on cache partition, and takes ages to wipe
2.6.3.4 is the latest
I'm running 2.6.3.4 TWRP. Thanks for the suggestion though.
Okay, just posting the solution in case this happens to anyone else. Wiping in stock recovery, CWM, or TWRP didn't work. Fastboot erase, fastboot format, and fastboot oem lock/unlock didn't work. Factory images didn't work, with multiple downloads and md5 checking. What ended up somehow fixing it after trying everything I could think of was pretty simple.
In the Android OS, in settings, under backup and reset, I clicked reset. That's it. So far, graphical glitches gone. It's been almost 2 days, far longer than it's gone without a bootloop since it started these shenanigans.
No idea why recovery and fastboot and all that business didn't work. Just posting the solution for those who come after.
Funny thing is the reset in android settings uses recovery
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
I know, I can't figure it out. It rebooted into recovery exactly like I had done before, and I watched the robot's polygon spin exactly like I had done 20 times. I can't explain why it worked.
Same thing that happened to me. What I finally got done to resolve it was:
1) Completely wiped the device and I mean all partitions so there is no OS and no internal files
2) Get the refresh zip file from Google to flash the device back to stock 4.4 while in the bootloader
3) Boot up, skip the setup, place CM11 files on the phone, then turn it off, reboot to bootloader
4) Flash CWM with fastboot
5) Boot to recovery
6) Do a factory reset
7) Wipe cache
8) Install CM11 & gapps
9) Wipe cache again
10) Reboot
So far for me no more issues. I did the same steps as you when mine started acting up. Now cache wipes super fast as expected no more reboots.
Sent from my Nexus 5 using xda app-developers app
I was wrong. The reset fixed it for 2 days or so, then it started showing the same problems. Graphical glitches and rebooting. I'm RMAing it. This thread can be ignored from now on. Further discussion of this particular problem can go in ssconceptz's thread linked below.
http://forum.xda-developers.com/showthread.php?t=2547863
That sucks. Mine works great now. I'll remove the first method.
Sent from my Nexus 5 using xda app-developers app
---------- Post added at 11:41 PM ---------- Previous post was at 11:41 PM ----------
Maybe you could try the method I show before RMA?
Sent from my Nexus 5 using xda app-developers app
So, got the 4.4.2 update , downloaded it and then it asked for a reboot. I did reboot. I am completely stock , no root nothing. Now the update was installing but in the end I got error :/ the image was robot kinda looking like he had heart attack... anyways, it gave me 4 options, so i cliked volume button .. I don't know all the options but from the 2 of them, one was reboot and other was clear cache or something. I thought clearing cache may **** up something on phone so I tried scrolling back on the top.. but to my surprise from volume buttons phone didn't let me go up at all :/
I didn't had any choice but to choose clear cache.. I thought it may help. But it didn't... so I forced reboot it with power button hold for 10 seconds.. Now phone is working but no sim on it starts.. no signal whatsoever. If I try to open my gallery, it doesn't open. says "No storage, no external storage available" .. when I try to connect usb to phone and try to backup my pics and stuff from pc it doesn't open anything. PC does show "Internal memory" but there's nothing in it. My phone doesn't let me even use wifi. So I thought it was time to factory reset, but to my surprise when I click erase everything, it does nothing. So, I thought of rebooting and clicking "power+volume down" , still nothing.. it shows the same robot pic having heart attack... I doesn't have knowledge of root and stuff for now, I am a simple user of nexus 5 who is still on stock. Any help please? I am worried here now
Think you're gonna need to follow one of the guides to flash stock system again
Sent from my Nexus 5 using Tapatalk
nevermind. Working again.
What did you do to get it Woking I got mine in a box ready to RMA if you got a suggestions I'm open to try one more time beforrv I be without my phone for s long time
Sent from my Inspire 4G using Xparent Green Tapatalk 2
How did you get it working?? F**k mine has no signal at all too! Damn I am really pissed!
---------- Post added at 04:09 AM ---------- Previous post was at 03:59 AM ----------
I did a factory reset and its working now. What a headache Google!
Mistake 1: not allowing the phone adequate time to clear the cache when finished installing the ota. If you force the phone to restart during this process, it will corrupt your cache which causes all of those issues listed above (loss of signal, no baseband info, loss of access to mountable storage, etc).
Cache clearing takes considerably longer than on any other device I've owned prior to this phone, so messing with the phone during that important cache clearing process is the issue.
Mistake 2: reflashing the entire phone to stock. In the event you become impatient and decide to force your device to restart, you DONT HAVE TO revert to stock to get the phone working. What you have to do is restore functionality to the cache portion of the phone. All of your files are in fact still on the phone and accessible, you just have to unbreak your phone. You do this by procuring cache.IMG from the stock image of the phone (available on googles websites), and then you fastboot flash the file in the boot loader (look up adb commands to do this). Once this is done, reboot the phone and everything should be hunky dory after your applications cache is rebuilt and android boots.
Note: you might need to check for root again. Also if you corrupted your cache you will have to set all of your ringtones and notifications again because this cache corruption process unlinked the ability of yours apps that use notifications to "see" the sound files you have on your SD card.
Sent from my Nexus 5 using xda app-developers app
delete
What a savior ... wiped the cache again , gave adequate time this time and it booted again fine
I had the exact same problem! Cleared cache in recovery mode in 4.4.4 and then thought it stalled because it was running for 1 minute (which normally took 2 seconds in previous devices) so I forced a restart. Then I had all sorts of errors: couldn't connect with my SIM card, couldn't download our see my pictures, screen rotation but working, constant Google Playstore crash popups, and more.. I thought I'd bricked it. A few more attempts to clear cache in recovery mode, still took longer than 1 minute (also the same errors in my recovery mode like stated above: "E: failed to mount /cache" ... that sort of things)
A few days later I'd had it. My steps for the SOLUTION:
1. Cleared cache in my settings: settings -> storage -> cache (don't know if this has influenced the outcome but I did it).
2. Went back to recovery mode, errors still displaying, but tried again to clear cache. The only difference now was that I left it running without touching my Nexus 5 for about 10 MINUTES(!).
..........To my surprise it ended with "clearing cash complete" WOW! So I rebooted and everything worked fine again! The only thing was that I had to set some notification sound again. That wasn't too hard
Let me know if it helped in your case
xybur said:
Mistake 1: not allowing the phone adequate time to clear the cache when finished installing the ota. If you force the phone to restart during this process, it will corrupt your cache which causes all of those issues listed above (loss of signal, no baseband info, loss of access to mountable storage, etc).
Cache clearing takes considerably longer than on any other device I've owned prior to this phone, so messing with the phone during that important cache clearing process is the issue.
Mistake 2: reflashing the entire phone to stock. In the event you become impatient and decide to force your device to restart, you DONT HAVE TO revert to stock to get the phone working. What you have to do is restore functionality to the cache portion of the phone. All of your files are in fact still on the phone and accessible, you just have to unbreak your phone. You do this by procuring cache.IMG from the stock image of the phone (available on googles websites), and then you fastboot flash the file in the boot loader (look up adb commands to do this). Once this is done, reboot the phone and everything should be hunky dory after your applications cache is rebuilt and android boots.
Note: you might need to check for root again. Also if you corrupted your cache you will have to set all of your ringtones and notifications again because this cache corruption process unlinked the ability of yours apps that use notifications to "see" the sound files you have on your SD card.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I did that. The fastboot flash cache.img and still have the error...
Try flashing a stock rom, including the userdata.img file. Flash the userdata file last, right after flashing, boot into recovery and perform a factory reset.
. You do this by procuring cache.IMG from the stock image of the phone (available on googles websites),
where to get the cache.img from.
i have searched the folder of the stock rom after extraction,couldn't find one.
and my phone is soft bricked.
also its a asus zenfone 5(501 cg) with 4.4.2 not a nexus but with similar problem(rebooted phone without waiting for cache wipe to finish )
please reply asap
thanks
Hello, I'm having some problems with my Nexus 5 LG-D820 32GB
Here is everything I did in order:
1 - Was using stock 4.4.4
2 - Tried to install OTA lollipop following this:
1) Install Minimal ADB and Fastboot.. This will allow you to run commands on your phone.
2) Install Android USB Drivers. This will add the proper driver to recognize your device.
3) Install Universal Android USB Driver. This will automatically add the driver when you go into recovery mode. It's a different driver than the one above.
4) Open Minimal ADB and Fastboot (your phone should be plugged into your USB now)
5) Make sure your phone is recognized (enter 'adb devices'. A long number plus the word "device" should show up).
6) enter "adb reboot bootloader"
7) Use the volume rockers on your phone until it says "recovery mode," then hit the power button.
8) When you get the android with the exclamation, hold power and tap volume up. Don't hold, just tap it.
9) Use the volume rocker to choose "apply update from adb."
10) Go back to the minimal adb and fastbook command prompt, and enter "adb sideload filename.zip". Filename should be the path and the name of the zip file. You can rename the zip file so it's easier to type in. You can also type in "adb sideload" then just drag and drop the zip file into the command prompt if you'd prefer.
11) It should now sideload. Once it finishes on your screen, it will go back to the bootloader and you should reset your system once it's finished.
12) Watch in anticipation as your apps get optimized.
13) Play with your phone.
Click to expand...
Click to collapse
3 - It apparently worked, no errors or anything. But, when the phone tried to boot, it got to the upgrading android screen, with the optimizing apps list (1 of 82), it kept freezing, crashing, showing graphical glitches, and rebooting.
4 - I went into recovery and did a full reset/wipe, thinking it might have been because of an app it was trying to optimize. It still did the same thing.
5 - I thought it might have been happening because I was trying to upgrade OTA instead of a clean full install, so I got the factory image from the google page and tried to flash it following this:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
Click to expand...
Click to collapse
6 - Apparently it went ok, no errors or anything. But the same thing kept happening, it got to the optimizing app screen and would glitch up
7 - I got scared and tried to flash 4.4.4 back with the method in number 5. It worked, the phone was finally usable again. Thinking I had a way to always reset, I decided to keep trying to flash 5.0
8 - Tried again method number 5 with android 5.0, still glitched at optimizing apps
9 - Tried using Nexus Root Toolkit v1.9.4 to flash android 5.0, no apparent error, but got the same results at the optimizing apps screen
10 - Tried using Nexus Root Toolkit v1.9.4 to flash back to 4.4.4, and this time it froze at the twirling balls loading screen
11 - Tried using the method in number 5 to flash back to 4.4.4, and this time it froze at the twirling balls loading screen
12 - ??? I don't know what to do now. I was thinking of trying to flash 4.4.3 using the method in number 5 to see what happens >_>
Any help is appreciated, does anyone know why it kept freezing and showing graphical glitches at the optimizing app screen? Am I doing something wrong? The thing that bugs me is that every attempt went nicely, it isn't like I couldn't flash the images. I did flash them with no apparent error but they didn't work..
Thanks for any help
Hi,
I still have not been able to successfully boot into any usable version of android, they keep freezing and restarting the phone, but no errors appear during the flashing process. Can anyone shed some light?
Thanks
Are you seeing the same boot animation after trying to flash 4.4.4 & 5.0?
Since you used fastboot to flash the factory images, it should have worked. Only thing I can think of is your eMMC died.
This happened to me once on my old Galaxy Nexus. Basically no matter what ROM I would try to flash it would boot to Paranoid Android. Even after flashing factory images with fastboot (encountering no errors) I'd be greeted with the old JellyBean PA boot animation. Never got any errors, but nothing actually worked.
That's why I asked if you're seeing the different boot animation between KK & LP. To me it kind of sounds like your eMMC fried.
RoyJ said:
Are you seeing the same boot animation after trying to flash 4.4.4 & 5.0?
Since you used fastboot to flash the factory images, it should have worked. Only thing I can think of is your eMMC died.
This happened to me once on my old Galaxy Nexus. Basically no matter what ROM I would try to flash it would boot to Paranoid Android. Even after flashing factory images with fastboot (encountering no errors) I'd be greeted with the old JellyBean PA boot animation. Never got any errors, but nothing actually worked.
That's why I asked if you're seeing the different boot animation between KK & LP. To me it kind of sounds like your eMMC fried.
Click to expand...
Click to collapse
The animation is different, twirling pseudo 3D balls for 5.0 and 4 2D balls meeting in the centre for 4.4.4
And every time it stops at a different point. Right after I flash is when it goes the furthest, and then it goes less and less each subsequent boot
I really don't know I think I'll try flashing using the LG Flashtool to see if anything changes
It didn't work... I'm basically out of ideas
Guess I'll try the same things I've already done but with another computer, in the off chance the pc was corrupting something
I'm having the exact same issue. I received the OTA and it failed on install. I tried to install the update through toolkit and it installed fine, but it kept freezing on the initial phone setup. I went back to 4.4.4 through the toolkit and again received the OTA. This time the OTA installed without issue, and I was able to actually get the phone set up, but it kept having graphical glitches, would freeze and requiring a reboot. Went back to 4.4.4 and then followed the procedures on the Google factory images page and installed the update without issue. Again, it won't get through the initial setup without the graphics issues and freezing. I wiped the cache, did a factory reset, and installed the factory image again, with no change. 4.4.4 is working without an issue. I have a friend that is also experiencing similar issues. I'm out of ideas how to get the update to work.
mr2620 said:
I'm having the exact same issue. I received the OTA and it failed on install. I tried to install the update through toolkit and it installed fine, but it kept freezing on the initial phone setup. I went back to 4.4.4 through the toolkit and again received the OTA. This time the OTA installed without issue, and I was able to actually get the phone set up, but it kept having graphical glitches, would freeze and requiring a reboot. Went back to 4.4.4 and then followed the procedures on the Google factory images page and installed the update without issue. Again, it won't get through the initial setup without the graphics issues and freezing. I wiped the cache, did a factory reset, and installed the factory image again, with no change. 4.4.4 is working without an issue. I have a friend that is also experiencing similar issues. I'm out of ideas how to get the update to work.
Click to expand...
Click to collapse
At least you can revert to 4.4.4, mine freezes on the balls/once it did on the initial screen
Using another PC just made things worse, it froze while writing the system image and now the usb recognition is flimsy, sometimes it says the pc can't recognize the device when plugged in and sometimes it works, but now I can't flash things anymore
Welp. It's a less than a month old phone too, and I really think it's gone
Mine has froze a couple of times at that screen as well. I was able to force it into recovery mode with the power and volume down buttons and I was able to use the soft brick function in the toolkit to get it back to 4.4.4.
Sent from my Nexus 5 using XDA Free mobile app
Well I was able to flash 4.4.4 again ( I guess it's really hard to get it completely bricked, always when I thought it was gone it was able to get to fastboot mode)
But it still freezes on the balls / starter config screens
I'm at a loss as to how to fix this and I'm not seeing much online about others having this issue.
Sent from my Nexus 5 using XDA Free mobile app
You said you tried LG Flashtool and that didn't solve the problem either?
I haven't tried the LG flash tool. I'll have to try that tomorrow.
Sent from my Nexus 5 using XDA Free mobile app
mr2620 said:
I'm at a loss as to how to fix this and I'm not seeing much online about others having this issue.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, most problems are people receiving errors/not being able to complete flashing the images. What's crazy about this is that we follow the correct procedure, get no errors or anything, but it doesn't work
I'm still unable to boot. Will try contacting Google soon.
I still have been unsuccessful as well. I'm getting a replacement phone from Google. Should have it next week.
Sent from my Nexus 5 using XDA Free mobile app
moto g 2015 with stock rom goes into boot loop after "optimizing apps" phase
I rebooted my Moto G 2015 after an app began behaving erratically. The device then went into a boot loop. The first thing wrong with the boot is that it goes through the "Optimizing apps" stage, but as I had not wiped cache I wouldn't expect it to do that. After it gets through my 117 apps it says "Starting apps" and then reboots - I get the spool of thread and the stitching animation and the whole process starts over.
I've tried going into recovery mode and telling it to wipe cache there - I would expect cache wipe to take just several seconds like on other phones I've used (haven't ever done it with this one), but here it prints "formatting /cache..." and sits there, and sits there, and every 10 minutes, is still sitting there.
Is there any way from the recovery mode to get data copied off the device's internal memory? I have a few things there that weren't backed up. I tried running "Apply update from ADB" in recovery mode, then trying the "adb backup" command, but I got the error "adb: unable to connect for backup: closed".
My guess is that this phone has bad memory and I'll have to eat my lost data and send the phone back to Lenovo for warranty service. But if anyone has any ideas for things to try, let me know!
droidlesswonder said:
I rebooted my Moto G 2015 after an app began behaving erratically. The device then went into a boot loop. The first thing wrong with the boot is that it goes through the "Optimizing apps" stage, but as I had not wiped cache I wouldn't expect it to do that. After it gets through my 117 apps it says "Starting apps" and then reboots - I get the spool of thread and the stitching animation and the whole process starts over.
I've tried going into recovery mode and telling it to wipe cache there - I would expect cache wipe to take just several seconds like on other phones I've used (haven't ever done it with this one), but here it prints "formatting /cache..." and sits there, and sits there, and every 10 minutes, is still sitting there.
Is there any way from the recovery mode to get data copied off the device's internal memory? I have a few things there that weren't backed up. I tried running "Apply update from ADB" in recovery mode, then trying the "adb backup" command, but I got the error "adb: unable to connect for backup: closed".
My guess is that this phone has bad memory and I'll have to eat my lost data and send the phone back to Lenovo for warranty service. But if anyone has any ideas for things to try, let me know!
Click to expand...
Click to collapse
Wiping cache in recovery takes a long time on this device... really long, maybe even 20-30 minutes sometimes. Try the cache wipe again. If that fails do a full factory reset and give it time to finish. I don't know why recovery wipes take so long in this device, but they take a ridiculously huge amount of time. (Cache wipe in my Moto X Pure Edition takes about 30 seconds, which is also a 3rd gen Moto device).
You cannot access the files via stock recovery or fastboot unless you have an unlocked bootloader and boot a third party recovery like TWRP.
cache wipe successful but no joy
After my post above I tried wiping the cache and waited patiently, and as you predicted it did eventually complete. But the phone still goes into the boot loop.
I am kicking myself for not rooting this thing on day 1 and installing TWRP. I need to have a solemn moment alone with the phone to say goodbye to my data and I'll try full factory reset, if that doesn't work it's off to warranty service.
Thanks for the response!
droidlesswonder said:
After my post above I tried wiping the cache and waited patiently, and as you predicted it did eventually complete. But the phone still goes into the boot loop.
I am kicking myself for not rooting this thing on day 1 and installing TWRP. I need to have a solemn moment alone with the phone to say goodbye to my data and I'll try full factory reset, if that doesn't work it's off to warranty service.
Thanks for the response!
Click to expand...
Click to collapse
Well... On a good note, since your not rooted then system is still intact, a factory reset will likely work.
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Well... On a good note, since your not rooted then system is still intact, a factory reset will likely work.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
Yes, it did work, phone is back to where is was six months ago. Since the data has been wiped, I'm going to unlock and install TWRP so I'll be in a better place when this happens again. Thanks again for your help!