Yes, a Garminfone! I only got it for the GPS, so when I upgrade, I can unlock and continue to use it for just that. And it was my first Android phone, so jokes on me.
I was playing around trying to modify framework-res.apk, just replacing some of the system status icons with NinjaMorph. NM prompt'd for a restart(which I figured), restarted and got stuck on boot. With the little android popping out of the bottom left corner. The initial boot logo.
During that initial reboot, I managed to adb reboot recovery, and get to the recovery screen, but I couldn't select any of the options. So I pulled the battery(yes, my first mistake.), turned it back on, and now I can't access it with ADB.
The only 'mode' I can get it into is USB POLLING MODE. Which I have no clue what to do with.
Performing a hard reset does nothing, it just sticks at ** WIPE USER DATA ** and I let that sit overnight.
I also tried adb shell to try and copy the recovery img, but couldn't get SU privs(not sure if needed.).
I had this weird feeling that it wasn't going to work, so I made backups of all the partitions, boot, recovery, etc. and my SD.
Luckily it's under warranty, and they're sending a replacement. So I'm not at a complete loss, but I am curious if anyone has any ideas on how to get this back in working order, for future reference, because I have a bad habit of playing with fire... And I still have it for the next 3 to 5 days, so =)
Thanks to anyone who has any input!
Related
Alright. This is a 100% stock Nexus S- nothing "development" wise was done to the device, no system tools installed that could cause issues, basically nothing but basic apps loaded on the device.
It just started today. I was working on my bf's Vibrant (another, more successful story) and grabbed my Nexus and hit the power button and it did not turn the screen back on. Holding the power button down did not reboot the device, and none of the buttons would light up or function.
So, I pulled the battery. Now every time I try to boot, it hits the "Google" screen and stays put. I left it alone for 5 minuets hoping it would finish booting and nothing. The soft buttons will light up, and if I touch them they register the touch but it does not help the phone to boot.
I do know that the phone was basically dead right before this happened, and at first I thought it was just dead. However, its been on the charger for at least 30 minuets- which should have given it enough of a charge to boot up, and still nothing.
What could cause this issue?
I did install a couple of new applications today, and I know the market updated a bunch of them but they're all apps that I've had on several phones (minus the two new ones today) and have never had an issue with any of them. The two new ones I downloaded were OS Monitor, and a 2G/3G toggle for hopes of improving some battery life.
But those are the only two things I've done differently. I've only been using the phone for a week but I haven't had any problems at all, before this.
Now- if worst comes to worst I can seem to get into the bootloader, and through that, stock recovery. So I can try to do a factory reset and wipe cache but without a backup I really kinda hope thats a last resort.
Please help, and let me know if you need any more information.
Thank you!
I understand that you're fully stock which I assume means you have a locked bootloader (everything I say from here on out assumes as such)? First, I'm going to also assume that you didn't update to 2.3.3? If not, then follow the steps in this guide to boot into a custom recovery and from there go to backup and restore and do a NANDroid backup. Now go to mounts and storage and mount USB storage (or whatever its called, don't have my phone right here). Plug your phone into your comp and copy over whatever you'd rather not lose from your SDcard (just in case you have to wipe). Now download the 2.3.3 update from here and put it on the root of your SD card. Now go back and flash this. Reboot and see if you're golden. If so, great, if not try a factory reset.
If that doesn't work go through the steps again to boot into a custom recovery, you might have to unlock your bootloader and wipe all your data (again) and restore your backup and try doing a factory reset with that. Don't worry about unlocking the bootloader, it can be relocked with a simple command and it won't wipe anything to relock it.
Here is the command just in case:
Code:
fasboot oem lock
I got all the way to having clockwork recovery booted up on the phone, but nothing would mount. Everything gave me an error, and factory reset froze...
I don't think there is anything I can even do from here, is there?
Hey guys,
On Friday my Nexus S started acting buggy, freezing up on me periodically. I woke up Saturday to find the phone (charging) completely unresponsive with the four face buttons lit up. I did a hard reset, but it just loads up the start "GOOGLE" screen and stays there, won't actually load the operating system.
I've booted into recovery mode, done a factory reset, wiped the cache partition, but nothing seems to work. The bootloader is not unlocked and I can't seem to get it unlocked because ADB won't even acknowledge that the phone is plugged in.
I'm completely stumped here and I now seem to own a real expensive paper-weight. I haven't done any customizations, just used the phone completely stock since I bought it in December.
Any advice would be greatly appreciated!
Thanks
Check this out ...same problem i think
Danchr said:
Hey guys,
On Friday my Nexus S started acting buggy, freezing up on me periodically. I woke up Saturday to find the phone (charging) completely unresponsive with the four face buttons lit up. I did a hard reset, but it just loads up the start "GOOGLE" screen and stays there, won't actually load the operating system.
I've booted into recovery mode, done a factory reset, wiped the cache partition, but nothing seems to work. The bootloader is not unlocked and I can't seem to get it unlocked because ADB won't even acknowledge that the phone is plugged in.
I'm completely stumped here and I now seem to own a real expensive paper-weight. I haven't done any customizations, just used the phone completely stock since I bought it in December.
Any advice would be greatly appreciated!
Thanks
Click to expand...
Click to collapse
Can you get to fastboot?
Danchr said:
Hey guys,
On Friday my Nexus S started acting buggy, freezing up on me periodically. I woke up Saturday to find the phone (charging) completely unresponsive with the four face buttons lit up. I did a hard reset, but it just loads up the start "GOOGLE" screen and stays there, won't actually load the operating system.
I've booted into recovery mode, done a factory reset, wiped the cache partition, but nothing seems to work. The bootloader is not unlocked and I can't seem to get it unlocked because ADB won't even acknowledge that the phone is plugged in.
I'm completely stumped here and I now seem to own a real expensive paper-weight. I haven't done any customizations, just used the phone completely stock since I bought it in December.
Any advice would be greatly appreciated!
Thanks
Click to expand...
Click to collapse
Is this guy posting under different usernames?
Anyways here's what I wrote to another person, pretty much the same thing:
If you can get into bootloader and recovery, you're not bricked.
ADB is used when Android is booted up.
Fastboot is used in bootloader.
Get Fastboot working (proper drivers etc)
Go into bootloader on your phone.
run 'fastboot devices' if your phone and serial number shows up, fastboot is working.
run 'Fastboot oem unlock'
then flash clockworkmod recovery 'fastboot flash recovery filenameofrecovery.img'
boot into recovery.
mount the internal sd. search for a stock nandroid backup in the forums, copy it over to the internal sd.
umount, go back to main menu of cwm recovery and restore that nandroid backup.
reboot. if it boots up and stuff, shut down phone, go back to bootloader and 'fastboot oem lock' to relock bootloader and you should be at stock.
So i saw a lot of random reboot threads, but none like my problem. I'm running Embryo 6.11. I was using my phone today to take pictures and then the phone rebooted itself, but would not get past the Samsung glow logo. I waited about a minute and nothing, so I pulled the battery, waited about 5 minutes for the phone to cool down, just in case it was an overheating issue. Then I tried to reboot and the same thing happened, it got stuck at the glow logo. So i rebooted again, this time I got to my home screen, as soon as I tried to open an app, the phone rebooted and then it wouldn't get past the glow logo again. I pulled the battery, then put it back in and just charged the phone up while off, just in case i had to do a lot of stuff to it. So after i charged it up, I tried booting up again, no luck. So i booted into recovery, tried flashing the ROM over the current installation, in hopes that that would just fix the broken areas causing it not to boot, but it didn't, so i went back into recovery and did a full wipe and now i'm starting from scratch again. This happened a week ago today (the 15th) and it also happened on the 1st. I don't know what is going on, do I have a bad partition from doing the Sean 3x wipes in the past when i used skyICS (I don't do that anymore, just one wipe now), or maybe from using Darkside superwipe in the past?
fishlipsboy said:
So i saw a lot of random reboot threads, but none like my problem. I'm running Embryo 6.11. I was using my phone today to take pictures and then the phone rebooted itself, but would not get past the Samsung glow logo. I waited about a minute and nothing, so I pulled the battery, waited about 5 minutes for the phone to cool down, just in case it was an overheating issue. Then I tried to reboot and the same thing happened, it got stuck at the glow logo. So i rebooted again, this time I got to my home screen, as soon as I tried to open an app, the phone rebooted and then it wouldn't get past the glow logo again. I pulled the battery, then put it back in and just charged the phone up while off, just in case i had to do a lot of stuff to it. So after i charged it up, I tried booting up again, no luck. So i booted into recovery, tried flashing the ROM over the current installation, in hopes that that would just fix the broken areas causing it not to boot, but it didn't, so i went back into recovery and did a full wipe and now i'm starting from scratch again. This happened a week ago today (the 15th) and it also happened on the 1st. I don't know what is going on, do I have a bad partition from doing the Sean 3x wipes in the past when i used skyICS (I don't do that anymore, just one wipe now), or maybe from using Darkside superwipe in the past?
Click to expand...
Click to collapse
I had a similar issue on Embryo 7... ROM installed fine, worked fine for about a week then reboot and not going past the Samsung logo. What I found out was that the data and system partition were bad... running an e2fsck from adb shell while in recovery turned out a lot of logical errors (most of them were about inodes allocated to more files if I remember correctly but not only those). I found out while working on it that wiping these partitions from recovery is not fixing these errors.
What I did was I wiped everything (cache, data, system), ran e2fsck on each individual partition to fix the errors until no more were showing up then started from scratch (install ROM, restore apps, etc). So far, no more issues.
How do I run e2fsck? I'm not familiar with adb shell. I am a flasher and slight modder, but not a dev.
fishlipsboy said:
How do I run e2fsck? I'm not familiar with adb shell. I am a flasher and slight modder, but not a dev.
Click to expand...
Click to collapse
Reboot phone in recovery since you need those partitions unmounted. Connect phone to PC with USB then connect from PC with adb (run "adb shell"). If partitions (data, system, cache) are mounted you can unmount them from recovery.
Once you are in adb shell then you can run "e2fsck -fnv /dev/block/mmcblk0p24" to scan system partition. Repeat for data partition (mmcblk0p25), efs (mmcblk0p21), cache (mmcblk0p26), preload (mmcblk0p27). That will tell you only if you have errors; it will not fix them.
To fix them, run "e2fsck -fcyv /dev/block/<part name as above>".
You can also run "e2fsck" (with no parameters) to see the help and what each parameter means.
Also, see this great thread regarding the list of partitions in Skyrocket... http://forum.xda-developers.com/showthread.php?t=1629508
Hope this helps you. Let me know if you need more detailed instructions.
---------- Post added at 11:31 PM ---------- Previous post was at 11:27 PM ----------
fishlipsboy said:
How do I run e2fsck? I'm not familiar with adb shell. I am a flasher and slight modder, but not a dev.
Click to expand...
Click to collapse
BTW, if you find errors on your data and/or system partitions and choose to fix them, it does not mean that you phone will boot fine right away. Depending on how bad it is, you might need to reinstall the ROM.
Also, fixing the errors takes space (as *nix saves the recovered files under "lost+found" folder) so in my case, I chose to wipe the partitions from recovery first, then fix the errors and then re-install the ROM.
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.
My wife was using her phone (completely stock, no mods whatsoever) and it started shutting down processes (contacts, calendar, etc). She held the power button down to manually shutdown and then rebooted shortly after. The next day, it started to do it again, so she did the same thing only this time it stuck on the "M" logo screen. When she brought it home, I held the power & vol down buttons in for 2 minutes and the phone began to reboot but still stuck on the "M" logo screen.
I began searching vigorously online for a solution and have tried everything. **NOTE** - I am completely unsure what version of software the phone was running before this happened. The first thing I tried was RSD Lite with the JB Stock file from Team US Cellular. The flashing fails during certain lines of the .XML file. I took suggestions from other users to delete the lines it fails on and let the file continue the flash. Once it reboots, it is still stuck on the "M" logo screen. I then tried all the other stock firmware files I could and the same result each time.
Next, I tried using ADB and Fastboot tools. My PC recognizes the phone when plugged in and running command "adb devices" shows the phone listed, but whenever I try to run a pull or other command, I get error:closed. I've tried all the solutions of making sure ADB files are updated, running the list of commands to get the daemon connection reset, etc. I can't push/pull anything using adb. I tried using mFastboot with no luck either.
I tried the above steps over and over for 3 days straight, hoping I missed something simple. My final option was to boot into Recovery Mode and run Wipe Data/Factory Reset. When I select that option, about 3 lines of command begin to run and the phone reboots and goes back to being stuck on the "M" logo screen. The command lines and reboot literally happen within 2 seconds. That tells me Factory Reset is corrupted, but I'm not 100% at this point.
Does anyone have any insight on if there is anything I can do at this point? It wouldn't be such a big deal to lose the phone, but we have pics/videos of our 2 year old that we never got backed up at home or in the cloud and they're very important to us. Unfortunately, the phone did not have and SD card. I'm honestly out of ideas at this point and have never felt so defeated.
Thanks in advance.
mwc104 said:
My wife was using her phone (completely stock, no mods whatsoever) and it started shutting down processes (contacts, calendar, etc). She held the power button down to manually shutdown and then rebooted shortly after. The next day, it started to do it again, so she did the same thing only this time it stuck on the "M" logo screen. When she brought it home, I held the power & vol down buttons in for 2 minutes and the phone began to reboot but still stuck on the "M" logo screen.
I began searching vigorously online for a solution and have tried everything. **NOTE** - I am completely unsure what version of software the phone was running before this happened. The first thing I tried was RSD Lite with the JB Stock file from Team US Cellular. The flashing fails during certain lines of the .XML file. I took suggestions from other users to delete the lines it fails on and let the file continue the flash. Once it reboots, it is still stuck on the "M" logo screen. I then tried all the other stock firmware files I could and the same result each time.
Next, I tried using ADB and Fastboot tools. My PC recognizes the phone when plugged in and running command "adb devices" shows the phone listed, but whenever I try to run a pull or other command, I get error:closed. I've tried all the solutions of making sure ADB files are updated, running the list of commands to get the daemon connection reset, etc. I can't push/pull anything using adb. I tried using mFastboot with no luck either.
I tried the above steps over and over for 3 days straight, hoping I missed something simple. My final option was to boot into Recovery Mode and run Wipe Data/Factory Reset. When I select that option, about 3 lines of command begin to run and the phone reboots and goes back to being stuck on the "M" logo screen. The command lines and reboot literally happen within 2 seconds. That tells me Factory Reset is corrupted, but I'm not 100% at this point.
Does anyone have any insight on if there is anything I can do at this point? It wouldn't be such a big deal to lose the phone, but we have pics/videos of our 2 year old that we never got backed up at home or in the cloud and they're very important to us. Unfortunately, the phone did not have and SD card. I'm honestly out of ideas at this point and have never felt so defeated.
Thanks in advance.
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. Please consider asking your question here:
Android Q&A, Help & Troubleshooting
You'll find expert advice there. Good luck!