Yesterday, my phone started to freeze randomly. I would hit the wake button and nothing would happen, I would have to hold power for about 15s or remove the battery to reboot. The times between freezes got shorter and shorter until today when it would never make it to the OS. It would either go to a reboot loop or sit stuck with the Galaxy S III logo on screen.
I was able to boot into recovery, I wiped the Dalvik Cache and then rebooted. The phone got into the part where it updated apps but after waiting for than 20 minutes for it to update app 29 of 29, I pulled the battery and rebooted to recovery.
This time I wiped the normal cache and rebooted but it didn't make it to android.
I rebooted to recovery and did a factory reset, then rebooted. The phone powered off and would not power back on at all. The battery was at about 40% when this happened, I think. It was plugged in for the last 4 hours but it still won't start.
Is there anything I can do?
super6logan said:
Yesterday, my phone started to freeze randomly. I would hit the wake button and nothing would happen, I would have to hold power for about 15s or remove the battery to reboot. The times between freezes got shorter and shorter until today when it would never make it to the OS. It would either go to a reboot loop or sit stuck with the Galaxy S III logo on screen.
I was able to boot into recovery, I wiped the Dalvik Cache and then rebooted. The phone got into the part where it updated apps but after waiting for than 20 minutes for it to update app 29 of 29, I pulled the battery and rebooted to recovery.
This time I wiped the normal cache and rebooted but it didn't make it to android.
I rebooted to recovery and did a factory reset, then rebooted. The phone powered off and would not power back on at all. The battery was at about 40% when this happened, I think. It was plugged in for the last 4 hours but it still won't start.
Is there anything I can do?
Click to expand...
Click to collapse
Flash the stock firmware.
Can you get into download mode?
Sent from my SGH-T999 using Tapatalk
serio22 said:
Can you get into download mode?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
No, I even took it to someone with a USB jig. I've mailed it off to someone on ebay with a Riff box to see if they can fix it. In the mean time, I bought a Nexus 5 on craigslist and couldn't be happier.
Related
I brought my Nexus Prime from Korea last month.
A few hours ago I was listening to music on my phone when it rebooted. After that it came back on for roughly 10 seconds before rebooting again.
I uninstalled a game from my phone roughly 30 minutes before this error happened.
I cannot use my phone now, I get a few seconds of use out of it before its stuck in a continuous reboot cycle.
I have tried letting it cool down (it was a hot day), removing the simcard and changing batteries. Not sure what else I can do with only a few seconds of use.
Model number - SHW-M420S
Is anyone able to help me get out of this reboot cycle?
Try to back up important things and do factory reset. Is your phone rooted? CWM recovery installed? If so, before doing factory restore you could try wiping cache/dalvik cache first.
Sent from my super Galaxy Nexus plus®
Luckily its still a new phone, so there isn't much on it.
The phone is rooted in that I cannot access it in any way. Even connecting to a computer is useless as its only on for a few seconds before it reboots itself.
CWM recovery isn't installed, will be when the phone is working again though!
Is there a way to wipe the cache/dalvik cache or factory reset while the phone is off?
fastboot will allow you to erase data,userdata, as well as flash a custom recovery like cwm or a full rom.
bk201
edit: boot your device with POWER+VOLUP+VOLDOWN into fastboot. search google and/or xda for some fastboot tutorials.
I had this problem awhile back. It was a bum phone with hardware issue. I had to exchange it. Yours may be in the same boat.
I will try a fastboot later today and let you know the outcome, thank you.
If all else fails I'll send it back to Korea for new hardware I guess.
I ran into this problem a while ago. I had to restore the phone to stock using the image from Google. Haven't had a problem since
I was on my phone, checking XDA, reading news and so forth. I put the phone down to grab some dinner. When I got back after eating I picked up my phone and it was unresponsive.
I held down the power button for a while and nothing.
I did a battery pull and I was able to boot to the Google splash screen with the unlock symbol. Unfortunately it just hung there.
I pulled the battery again, this time I booted in fastboot, then recovery. The clockworkmod recovery main menu came up in recovery, but when trying to do a restore or anything… The blue menu would disappear and not come back. I can get to recovery, but I am unable to do anything with it.
Last night I flashed to AOKP B26 from AOKP B25. I wiped cache and dalvik. I did not do a full wipe, but according to the dev you do not need to. This morning I flashed Morphic’s kernel TNP138-RD-FUV. I used this kernel on B25 with no issues for several days as well. I wiped cache and dalvik before flashing the kernel as well. CPU was set to the default 1190 and default voltages, with the on demand governor.
It is weird that I didn’t have any issues until hours later and the phone wasn’t even in use. It is as if it wiped itself. I am wondering how and why.
At this point I am going to do a full factory ODIN restore. I don’t think there are any other options.
EDIT, as posted below:
I was getting ready to do the ODIN restore when for the heck of it I decided to let it boot normally one last time. What do I have to lose.
I booted to the Google splash screen and set it down. I got a drink and took out the trash. When I came back I noticed it was at the boot animation! It sat at the boot animation for another couple of minutes but 10 minutes after pressing the power button I was booted up.
I let it sit for another 10 before I played with it. But now its like nothing ever happened. And it boots regularly now. I even booted into recovery and it is functioning as normal.
Any ideas what happened?
Dakota0206 said:
I was on my phone, checking XDA, reading news and so forth. I put the phone down to grab some dinner. When I got back after eating I picked up my phone and it was unresponsive.
I held down the power button for a while and nothing.
I did a battery pull and I was able to boot to the Google splash screen with the unlock symbol. Unfortunately it just hung there.
I pulled the battery again, this time I booted in fastboot, then recovery. The clockworkmod recovery main menu came up in recovery, but when trying to do a restore or anything… The blue menu would disappear and not come back. I can get to recovery, but I am unable to do anything with it.
Last night I flashed to AOKP B26 from AOKP B25. I wiped cache and dalvik. I did not do a full wipe, but according to the dev you do not need to. This morning I flashed Morphic’s kernel TNP138-RD-FUV. I used this kernel on B25 with no issues for several days as well. I wiped cache and dalvik before flashing the kernel as well. CPU was set to the default 1190 and default voltages, with the on demand governor.
It is weird that I didn’t have any issues until hours later and the phone wasn’t even in use. It is as if it wiped itself. I am wondering how and why.
At this point I am going to do a full factory ODIN restore. I don’t think there are any other options.
Click to expand...
Click to collapse
In cwm is there a 'go back' option at the bottom? If not scroll up and down a few times passing from bottom to top (looping) until it says like back button activated. If back is not active power button makes screen go off and on and does not select.
This is if you are not using touch enabled cwm.
Sent from my Galaxy Nexus using Tapatalk
if you can get into cwm then try fastboot and flash the factory images from the boot screen
_Dennis_ said:
In cwm is there a 'go back' option at the bottom? If not scroll up and down a few times passing from bottom to top (looping) until it says like back button activated. If back is not active power button makes screen go off and on and does not select.
This is if you are not using touch enabled cwm.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I am not using the touch enabled. I know that if you cycle through the menu too much it will disable the select button, but if you keep cycling it will enable it. This isn't that.
The screen is on, I can see the clockworkmod recovery & version in the middle of the screen. Just the ICS blue menu disappears completely. no go back or anything. just a black screen with the clockworkmod info in the middle. It is as if its thinking but it just hangs.
id suggest you try to use ADB from recovery to try and at least pull the sdcard files first of all
second id try to flash another recovery from fastboot then boot to recovery and flash a rom or restore backup
if the above doesnt work then factory image from fastboot is it
I was getting ready to do the ODIN recovery when for the heck of it I decided to let it boot normally one last time. What do I have to lose.
I booted to the Google splash screen and set it down. I got a drink and took out the trash. When I came back I noticed it was at the boot animation! It sat at the boot animation for another couple of minutes but 10 minutes after pressing the power button I was booted up.
I let it sit for another 10 before I played with it. But now its like nothing ever happened. And it boots regularly now.
Any ideas what happened?
Sent from my Samsung Galaxy Nexus - Verizon 4G LTE.
So, last night I was out and about - just having a good time. Noticed that the battery on my GSM Galaxy Nexus was getting low. Went "Meh, wasn't the first time it's died." It got to 1% battery power and shut-off, like it normally does. Me being who I am, I turned it back on to see just how much more juice I could get out of it.
Phone booted up alright. Finished the boot animation, and then a couple seconds later turned off.. not a big deal. I get home, plug it in, and the charge screens cycle..... and then they cycle again. And again. And again. Basically just looping. I turn the phone ON, finishes the boot animation and... turns off again riight away? Goes back to the charge screen loop.
I'm not talking about the regular charge screen. After the battery gets 'filled' twice, it completely restarts. Black screen for 2 or so seconds, and then it goes through the charge animations as it would if you had just pluggied it in. I CAN get into bootloader, but that's about it. I'm just curious.. has anyone seen this before? Or know what my problem might be?
I'm unable to turn USB Debugging on in the system settings, so I'm at a loss as to how I can fix this issue WITHOUT bringing it into Bell.
Try going into recovery and wiping cache and dalvik. If that doesn't work reflash your rom
My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..
i.vt3c.d0hc said:
My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..
Click to expand...
Click to collapse
The "Broken android" IS stock recovery. I believe that when you push Volume Up seeing that image it takes you to the stock recovery menu. But you can always reflash Yakju or any other ROM through fastboot mode (see the tutorials here on the forum).
i.vt3c.d0hc said:
[snip]
I get home, plug it in, and the charge screens cycle..... and then they cycle again. And again. And again. Basically just looping. I turn the phone ON, finishes the boot animation and... turns off again riight away? Goes back to the charge screen loop.
Click to expand...
Click to collapse
Turn it off. Leave it charging for a few hours before turning it on.
i.vt3c.d0hc said:
[snip] I'm unable to turn USB Debugging on in the system settings, so I'm at a loss as to how I can fix this issue WITHOUT bringing it into Bell.
Click to expand...
Click to collapse
You do not need to have USB debugging enabled to use fastboot.
i.vt3c.d0hc said:
My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..
Click to expand...
Click to collapse
It doesn't take long at all to install the drivers. Look for a thread with "universal" in the title. I think it is in GN General. Once you do install the fastboot driver, download the fastboot.exe file and reflash the stock ROM.
Diger36 said:
The "Broken android" IS stock recovery. I believe that when you push Volume Up seeing that image it takes you to the stock recovery menu. But you can always reflash Yakju or any other ROM through fastboot mode (see the tutorials here on the forum).
Click to expand...
Click to collapse
It's volume up and the power button.
Sent from my Galaxy Nexus using Tapatalk
The problem I have is that the charge animation doesn't change... i.e. It'll constantly refill the battery and all, but it always starts from the bottom (While when a phone is say... half charged, the little battery is half filled and the animation continues.
I'm not sure it's even charging at all.
Update time!
Got it into the stock recovery. Wiped the cache and all of my data. Rebooted, and.... it turns on! No longer reboots on regular startup. That's the good news. So at least it's somewhat useable now..
Now for the BAD news.
-It still does that retarded charging bootloop that doesn't seem to get me anywhere
-....When it's on. Like, running, it doesn't charge. Nadda. Zip. Zilch. Computer, wall charger, android dock, nothing. It just won't charge when it's on. However when I got it to power on, it said I had 14% remaining - which means it was likely charging inside the Bootloader, as I had it on that for quite a bit.
I think this just went from a software to a hardware issue. Thoughts?
i.vt3c.d0hc said:
Update time!
Got it into the stock recovery. Wiped the cache and all of my data. Rebooted, and.... it turns on! No longer reboots on regular startup. That's the good news. So at least it's somewhat useable now..
Now for the BAD news.
-It still does that retarded charging bootloop that doesn't seem to get me anywhere
-....When it's on. Like, running, it doesn't charge. Nadda. Zip. Zilch. Computer, wall charger, android dock, nothing. It just won't charge when it's on. However when I got it to power on, it said I had 14% remaining - which means it was likely charging inside the Bootloader, as I had it on that for quite a bit.
I think this just went from a software to a hardware issue. Thoughts?
Click to expand...
Click to collapse
Power down phone, do a long battery pull, place it inside again, let it charge for a few hours without powering it on, when it is fully charged (or after a few hours) pull battery again and then take charger out the phone. After a few minutes, place battery inside phone again and start it up without the charger.
Hope that works.
Sent from my Galaxy Nexus using xda premium
And that might fix this charging bootloop? Because the LCD doesn't even turn off..
i.vt3c.d0hc said:
And that might fix this charging bootloop? Because the LCD doesn't even turn off..
Click to expand...
Click to collapse
You could always try a new battery
Sent from my Galaxy Nexus using xda premium
+1 for the new battery thought.
Battery test
I am having a similar problem, I get the boot loop.
Difference is that I had started with a new battery so that could be your problem or unrelated. I went to a mobile shop yesterday and they let me use a new battery to see if the loop would start. It did not so there seems to be at least one other failure path. I have avoided a factory reset as I was hoping to pull some pictures but coming to the realization that I will have to try factory reset as a last resort
I posted to this thread #192
http://forum.xda-developers.com/showthread.php?t=1490815
My Galaxy Nexus phone from WIND went into a reboot loop yesterday. It had been charged to 98%, used to make a call and then put away. Wireless was enabled. Noticed vibration periodically and say it was rebooting every 6 - 7 seconds. Pulled battery to stop reboot. Saw references to fully charged battery via USB stops reboot loop so tried that. Battery voltage was 4.17V and still went into reboot loop.
Tried to boot into safe mode but still goes into a loop
I went into recovery mode and tried all options but factory reset because I am hoping to recover some pictures
reboot system now
apply update from cache (but did not have an update to install as only options were ../ lost+found/ recovery and when I selected these was in a loop as well)
wipe cache partition
Can't tell what version of Andorid I have as the phone never finishes booting.
Boot console gives the following information
Product Name – tuna
Variant – maguro
HW version – 9
Bootloader version – PRIMEKK14
Baseband version – I9250UGKL1
Have installed SMS backup because I was planning to do a backup after a trip. Also have two GPS tracker apps installed.
GNMO15 said:
[snip]
I have avoided a factory reset as I was hoping to pull some pictures but coming to the realization that I will have to try factory reset as a last resort
Click to expand...
Click to collapse
If you can boot into recovery, you may be able to get your pictures off your device.
1) Make sure you have the drivers for your device properly installed on your computer.
2) Download the attachment and unzip it to a directory on your computer.
3) Open a command prompt in the same directory.
4) Reboot your device into recovery and plug into your computer.
5) Make sure your computer sees your device by typing: adb devices
6) Pull the data off your device by typing: adb pull /data/media
Note: depending on how much data you had on /sdcard, this could take a while, so be patient.
So this has happen twice. My gnex has just restarted and get stuck at the bootloader in an endless loop.
I have a stock, rooted, 4.0.4 gnex.
Last time this happen I had to completely wipe my phone and start over. Dont want to do that again.
Has this happen to anyone else?
Thanks
-J
When I load in to recovery I cant even see the CWM menu.
Can you run fastboot commands
Sent from my Galaxy Nexus using xda premium
I could but now the phone wont turn on at all. Im actually one the phone with google right now to try to figure this out.
charge the phone (plug it in).
unplug it, press and hold both volume buttons, and press and hold power
bootloader comes up, plug it into computer
in this screen, flash the latest cwm file using the command:
fastboot flash recovery clockworkfilenamehere.img
press vol buttons to restart the bootloader, then select recovery, should pull up cwm.
Go wipe cache and dalvik cache (in advance), then pick restart, see if phone boots up.
If not, you'll need to reflash stock google image.
Charged phone over night and still wouldnt turn on.
Have you tried reseating the battery?
jp555soul said:
Charged phone over night and still wouldnt turn on.
Click to expand...
Click to collapse
Funny, my CDMA gnex just started doing exactly the same thing. Verizon is overnighting me another one, with Saturday delivery even.
you must factory restore your phone
you need to restore your phone to the factory image, use wugs toolkit,
galaxynexusforum.com/forum/galaxy-nexus-hacking-mods-lte-cdma/1445-wugs-galaxy-nexus-root-toolkit.html
it will download the 4.0.2 factory img for you. then use the same tool to root your phone. then install your rom. Install Liquid rom 1.4. i have tried them all it is by far the most stable and the fastet. coupled with franco or imoseyon kernel i am getting 20+ hrs of battery life and a smokin fast phone.
stuck in bootloader
My GSM nexus running aokp milestone 4 randomly got stuck in the bootloader the other day. It was working fine and after hitting my snooze button on my alarm and waiting a few minutes I realized it was off. when i turned it on it was stuck. I tried clearing cache and dalvik cache which wouldnt work so I was forced to do a factory reset. Came right back to life (with none of my data obviously).
This happened to me last night after trying to restore a nandroid. Wouldn't go past the Google screen when trying to boot the rom and wouldn't go past the team win recovery plash screen.
Luckily I have basic fastboot and adb command skills. Flashed fully back to stock, boot loader, radios, from, kernel. Booted up fine after that and no issues since.
I purchased a note 10 + off ebay broken screen so I replaced the screen and a couple of ribbon cables and new charger port. But now I turned it on and its stuck in a boot loop. Only main screen comes on where it says note 10 plus 5g and then it goes to nothing and then back on again and it will continue i guess forever. But I can access the recovery boot am I screwed or is it an issue that can be fixed by a flash or firmware? Thanks
try going into recovery and flashing stock rom
Mine did that (2X) from an app conflict and I eventually got it booted into Safe mode.
See if you can pull up the boot menu and do a hard reset.
Are all the cables properly connected and connectors undamaged?
blackhawk said:
Mine did that (2X) from an app conflict and I eventually got it booted into Safe mode.
See if you can pull up the boot menu and do a hard reset.
Are all the cables properly connected and connectors undamaged?
Click to expand...
Click to collapse
I did a hard reset from boot menu and it stayed in the loop. I cleared the cache and then reset and it stayed in the loop. When reset factory from boot it didn't even cycle through outside of boot menu it just went loop immediately. Could it be damaged board making it malfunction?
SMASHuFACE78 said:
I did a hard reset from boot menu and it stayed in the loop. I cleared the cache and then reset and it stayed in the loop. When reset factory from boot it didn't even cycle through outside of boot menu it just went loop immediately. Could it be damaged board making it malfunction?
Click to expand...
Click to collapse
Way past my level of experience... there are people here that can help you though. Be patient.
At least it's powering up.
What version do you have? Find out. Once you do, get the firmware for your device and flash with Odin. If you are having problems getting into download mode, try to power down. Open odin on computer. Once powered down, hold volume up and down at same time as you plug device into computer. You should now be in download mode and able to flash firmware...flash BL..AP..CP...CSC
Sent from my SM-N986U using Tapatalk