Running a stick galaxy nexus on 4.2.2. Had it in airplane mode in an area without service and when I went to take it out, the option to turn airplane mode off was greyed out. After rebooting, it says that its back to normal, but I can't connect to the network, gps,etc. Cleared cache and did a factory reset, but the problem is the same.
Anything else I should try or any other suggestions?
Thanks
Pull battery
Wait a few minutes
Put in battery
Cross your fingers
Boot
I had and sometime have this problem. Usually I power down fully and then boot instead of rebooting the phone. Works for me.
faxed from my nexus
Never was able to get it to work. Flashed radios...switched to CM. Gave up and ended up upgrading to a S4
Thread abandoned by op, reported for closing.
a manta wrote this.
Related
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
This is the hspa version.
svntsvn said:
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
Click to expand...
Click to collapse
The android icon you're referring to sounds like the stock recovery. In order to flash a ROM (even stock) from recovery mode, you'll need to load a custom recovery. This requires the device to be unlocked.
Not very often a stock setup needs to be restored. Generally, with the stock setup, only the /data partition is wiped (revert to factory default) and the issues are cleared. Not sure why a stock setup would need to be restore.
If you're still going to pursue reloading the system, without access to the normal android mode, the best route will be using fastboot. This can be done on a mac and the fastboot commands should be the same.
Hope that helps get a start!
This happened me earlier. I was able to factory reset it, which, unfortunately really annoyed me because I hadn't saved a backup..
Before the "Google" logo shows up, press and hold the power button and the volume up and down buttons.
Then go into recovery mode using the volume buttons.
When it reboots, you get that Droid with the hazard sign (which I know you're at, but just for the sake of others who need help) all you have to do is hold down the power button and WHILE it's held, press the volume up or down button and move to "Factory Reset". When you hold down the power button and press the volume rocker, a little menu will appear. It should only take a few minutes then.
Hope this helps. Apparently this is a WiFi issue. I'll definitely be keeping backups as of now..
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
svntsvn said:
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
Click to expand...
Click to collapse
I had the exact same problem happen last night with UI crashing and then the getting stuck at the boot animation. I was desperately searching online, looking to find a solution that didn't involve rebooting to factory setting and came across this post and did exactly what you did and it WORKED, very strange, I really wanna know what caused that!!!!
I've had the same problem with my Galaxy Nexus. I received it on December 21st, with stock 4.0.1 build. No root or unlock attempt at any time. On January 2nd I experienced this problems (UI process crash, screen not responding, reboot and stuck in boot animation).
The only solution was to do a factory reset and start over.
On January 10th same problem, same solution. Second factory reset.
I got the 4.0.2 OTA just two days after that. I thought that would resolve the problem. The phone seemed more stable, with less FC's and no trace of the UI crash. Indeed it lasted long...
Exactly until January 24th when I picked up the phone and seemed in the sleep of dead. Removed the battery, restarted the phone... and stuck in the boot animation.
Do you have any advice? Should I return the phone? Aside from those specific problems I am quite happy with the SGN and Android 4 in general. And I use it quite a lot (I have a very long train commute) without other problems.
Again...
It happened again!!
I don't know what to do anymore, this is not a usable phone when I have to reinstall and reconfigure every 3 weeks.
I may have found the problem
Well, not me exactly, but this bug report seems to fit the problem and the charging workaround. Seems to be a problem the file used to store the battery stats and draw the charge graph.
It also fits my usage (I try not to charge it up until 100%).
I can't post links to the forum, the issue is id number 24518 which you can find in code.google.com/p/android/
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
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 tonight out of the blue, my Rogers Galaxy S3 restarted itself. This isn't totally unusual, as sometimes this will happen once or twice a day, but never has it been too bad.
First off, I've been running Cyanogenmod 10.0, and again, has been relatively problem free. The first major issue I had was a week or so ago when I woke up to my phone having seemingly restored it's default settings on its own. Apps and all my other data were intact, but widgets, app settings, etc, were all cleared.
Now tonight, my phone can rarely boot into CM, and when it does, the power menu will appear shortly thereafter before restarting itself once again. If the phone is plugged in, I can't get anything other than the charge indicator to come on the screen for more than a second. The phone also does this when trying to boot into recovery mode or download mode.
I'm at a total loss as to what to do here, so I'm going to be leaving the phone off with the battery out over night. Appreciate any feedback in the meantime.
Also having a similar problem: phone boots up, will barely enter the bootloader/TWRP/boot animation for hyperdrive ROM. Also with rogers. I believe it might be SDS but I need to re install the stock firmware and can barely boot into the bootloader without the phone dying (battery is charged though). Any help greatly appreciated!
EDIT: managed to boot up for long enough to install "eMMC check" and apparently I have a 'sane chip'.
There have been issues with the power button getting stuck. Maybe you have that issue?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Domoo said:
There have been issues with the power button getting stuck. Maybe you have that issue?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Well, after pulling most of my hair out, that does seem to be the issue. Would explain why the power menu would come up the few times it did manage to boot. I managed to get it working for a while, but the button seems to be really delicate since picking my phone up and barely touching it reset it again.
I guess now I need a solution to the power button sticking, but at least it doesn't seem to be SDS.
Okay, that makes sense. When I leave the phone completely stable it's fine.
However, I have tried unrooting and reinstalling stock firmware. However, my system status in bootloader is still custom, when I boot up the rom I still have superuser installed. I tried installing two different stock firmwares for Rogers and the same problem. Any help would be great, I really want to send this in for warranty ASAP.
EDIT: After using ODIN to install stock rom, I still had Superuser. I installed SuperSU and then preformed it'sfull unroot. After that i cleared data and cache from stock recovery and the phone is now at original status and seems to not be randomly rebooting/dying. Weird.
So, I was busy doing some things, when my phone ran out of battery, so I decided to turn on the ultra power saving, after that, I turned off the phone. When I came back to my home, I charged my phone and started it again. Now, it reboots but first it gets on the menu of ultra power saving mode and after 3-5 seconds, it reboots, and its looping for forever. I tried to fix it by getting on recovery mode and wiping cache partition, but it didn't work. I know that I may fix it by doing a factory reset, but I would like to know if there is another way to resolve this.
P.S: 5 days ago, the phone did the same for the first time, but I could fix it (idk how, I only turned on the phone.)
Anyways, thank you for the help.