2 hour old Nexus. Ran a few apps (already installed stock apps) then downloaded and began watching something on Netflicks. Phone appeared to crash, and then began rebooting.
Black screen with Google in white letters, then a fancy animated graphic. Keeps alternating between the two. Popping out battery and then putting it back in does nothing. As soon as I try to boot it up it goes immediately into loop.
i would recommend a factory reset. pull your battery. put it back in. hold volume down + volume up and then the power button (hold all at the same time) until you feel a vibrate. you're now in fastboot mode. use the volume rocker to select recovery. from here you should be able to factory reset, iirc.
__________________
Galaxy Nexus i9250 unlocked and rooted
The Following 2 Users Say Thank You to mrvirginia For This Useful Post:
Seriously mine did this last night and again this morning.
Last night I was able to boot from recovery mode.
This morning nothing worked. I had to reformat the phone from revovery.
I wonder how many people are having this issue. I dont thinks it a wifi issue, but in both cases, it didnt start until i left my house and went out of wifi range.
I have to see if it will duplicate it again now that im reformatted.
Ok I have figured out that my wifi button does like a mini-self destruct of my phone and starts bootlooping. The only fix I have come across is by factory resetting it.
Like the above guy said you hold the Up+Down volume buttons + power button and it brings to you a screen. You use the volume control to get to recovery mode then you press power button to start. Once you get to the little droid laying down with the red hazard box / exclamation point you have to hold the power + up volume to scroll through the list to factory reset.
This time after I reset my phone the wifi was enabled when i started my phone and it connected no problem. I'm scared to turn off my wifi because it might die again. For now I'll just leave my wifi on and see what happens from here.
I just got home from a restaurant where I tried to use their wifi and got this exact problem. I couldn't even restore the image successfully there. I got home and went straight to restoring the image again, and it worked. In hindsight, I wish I had just tried to boot first, just to check.
I'm concerned that there is a defect when interacting with certain types of wifi bands/modes/?? If that is the case, the problem will never be resolved in a specific location until the bug is fixed.
Sounds like a hardware issue. Depth, you are correct to return for replacement as any others with this problem. Fortunately it does seem pretty isolated. We had a reboot problem with a few of the Motorola A855 handsets. There's always going to be a few defective ones.
So i don't ever post on blogs but as i had the same issue and may have come across a fix i figure i will share it.
when you first boot up the phone, and fill out the google account info it asks if you want google to to collect information about your location using wifi, to help with searches or something. I clicked yes to the requests to do so, and everytime i turned on wifi it would boot loop. I reset several times same problem. I have since turned that option off, and it seems to work just fine. I will update if that changes.
So i don't ever post on blogs but as i had the same issue and may have come across a fix i figure i will share it.
when you first boot up the phone, and fill out the google account info it asks if you want google to to collect information about your location using wifi, to help with searches or something. I clicked yes to the requests to do so, and everytime i turned on wifi it would boot loop. I reset several times same problem. I have since turned that option off, and it seems to work just fine. I will update if that changes.
Good luck all.
While that might be a good fix, I still stand by the fact that there is a hardware problems with some of these handsets. Otherwise, that setting would have been causing all the other android handsets to go boot-looping with that setting enabled. It is enabled on my A855 without problems.
So near as i can tell, so far, and i have been playing with this issue for about a day it is not the phone hardware but either the wifi in your neighborhood or something along those lines. I could be entirely mistaken but here is the full story:
I got the phone delivered yesterday tried to boot it up but was having issues remembering my billing code, so i figured while i was on the phone with Verizon i would set it up on wifi, it all worked fine for a minute, then when i got verizon to release the code i tried to activate the phone and it went into a boot loop. I thought this was a hardware issue so i took it to the store and after 2 hours of them trying to fix it, they gave me a new one, and sent me on my way, this one we activated in the store, it worked perfectly. When I got home i turned on the wifi, and poof same boot loop. I have since removed the wifi feature that let's google track me, and it works fine, when i put it back on it crashes, HOWEVER it does not do this when i am in a place with public free wifi, or my friends place. I thought this was weird, so today i googled the issue specific to router, and i found that several other blogs post about wirelss router N issues causing this boot loop.
I will try to exchange again, but i think it will have the same result.
So near as i can tell, so far, and i have been playing with this issue for about a day it is not the phone hardware but either the wifi in your neighborhood or something along those lines. I could be entirely mistaken but here is the full story:
I got the phone delivered yesterday tried to boot it up but was having issues remembering my billing code, so i figured while i was on the phone with Verizon i would set it up on wifi, it all worked fine for a minute, then when i got verizon to release the code i tried to activate the phone and it went into a boot loop. I thought this was a hardware issue so i took it to the store and after 2 hours of them trying to fix it, they gave me a new one, and sent me on my way, this one we activated in the store, it worked perfectly. When I got home i turned on the wifi, and poof same boot loop. I have since removed the wifi feature that let's google track me, and it works fine, when i put it back on it crashes, HOWEVER it does not do this when i am in a place with public free wifi, or my friends place. I thought this was weird, so today i googled the issue specific to router, and i found that several other blogs post about wirelss router N issues causing this boot loop.
I will try to exchange again, but i think it will have the same result.
That sounds like a pretty horrible bug to have. So in short if you leave the wifi setting on (with the google location stuff enabled) your phone may take a fatal dump just from being in the proximity of a certain wireless router?
It recognized my home network. Again, once I leave the network with my wi-fi toggle on, it began boot looping. Once I return to home, the boot looping stopped.
If I turn the wi-fi on away from home it will begin boot looping until I return to a remembered network.
I tried this with the Google location services off like mentioned above, but it does not matter.
My final assessment after two days and 2 phones, is that it is a software glitch with the remembered access points backed up to your Google account.
I believe it's possible that so many people haven't recognized it yet because Google backs up your remembered networks, and most people only use their wi-fi in those same areas they were using before getting the Nexus.
I could be completely wrong. It could be a hardware glitch, in which case, getting two phones from the same batch at Costco didn't change anything for me.
In which case, those of you that are getting replacements directly from Verizon (Depth Afield, Poop Monster, Cooper0101) could verify if a different phone really fixes it and it's a bad hardware batch. I'm in Northern Virginia/DC area, if it helps associate the batch shipments.
With that said, if William T Riker or others could test this out on other wi-fi networks, it would be greatly helpful. I noticed that William said he's been using the wi-fi on and off at home, but if his home was a remembered access point, then the issue wouldn't show up.
I hope we can get more people on here to test this based on what I've noticed in the last couple of days. Seems like we're close to isolating the issue.
had the same issue twice (2 phones were returned back 2 the store) on my 1st day in less than 4hrs, no issues with the 3rd one after more than 24hrs after the first 2 fiascos...
It recognized my home network. Again, once I leave the network with my wi-fi toggle on, it began boot looping. Once I return to home, the boot looping stopped.
If I turn the wi-fi on away from home it will begin boot looping until I return to a remembered network.
I tried this with the Google location services off like mentioned above, but it does not matter.
My final assessment after two days and 2 phones, is that it is a software glitch with the remembered access points backed up to your Google account.
I believe it's possible that so many people haven't recognized it yet because Google backs up your remembered networks, and most people only use their wi-fi in those same areas they were using before getting the Nexus.
I could be completely wrong. It could be a hardware glitch, in which case, getting two phones from the same batch at Costco didn't change anything for me.
In which case, those of you that are getting replacements directly from Verizon (Depth Afield, Poop Monster, Cooper0101) could verify if a different phone really fixes it and it's a bad hardware batch. I'm in Northern Virginia/DC area, if it helps associate the batch shipments.
With that said, if William T Riker or others could test this out on other wi-fi networks, it would be greatly helpful. I noticed that William said he's been using the wi-fi on and off at home, but if his home was a remembered access point, then the issue wouldn't show up.
I hope we can get more people on here to test this based on what I've noticed in the last couple of days. Seems like we're close to isolating the issue.
I haven't encountered this problem yet, but it's scary enough that you need to get in direct contact with google and/or Samsung to report this issue. Hopefully, 4.0.3 will not have the same problem?
I've used the WiFi on mine a few times so far, and I have not seen this issue. I'm connecting through the access point that was remembered in my Google account, and I turn off WiFi when I am finished using it.
I've used the WiFi on mine a few times so far, and I have not seen this issue. I'm connecting through the access point that was remembered in my Google account, and I turn off WiFi when I am finished using it.
You're like me on my first day. Only used a remembered access point, then the second day I forgot to turn it off.
Hey guys. I havnt noticed this on my phone but i wanted to point something out i noticed to see if it could be relevent. My first nexus came with the red yellow green blue wallpaper, had screen banding, and already knew my home wifi password. I swapped it though due to a very bad buzz in the earpiece speaker on phonecalls.
The new one i got came with the live wallpaper phase beam, had no banding, and DID NOT know my wifi password. I wonder whats going on
I turned on my wifi last night with 4g, everything was ok. Is this where you guys are running into problems?
Try turning on the wifi in public, away from any remembered wireless networks. See if it goes into a boot loop.
Then turn on the wifi at your home or somewhere you have a remembered network and leave it on. Then walk away from your wifi network until the wifi completely falls out and the phone flips completely to 3g or 4g. See if it starts to reboot.
Happened to me yesretday, turned on wifi then phone crashed. Continued to bootloop until i factory reset the phone. Has not done it again but im going to call and get a replacement just in case.
Happened to me yesretday, turned on wifi then phone crashed. Continued to bootloop until i factory reset the phone. Has not done it again but im going to call and get a replacement just in case.
You dont have to factory reset the phone.
If it starts boot looping, just return to a remembered network and the boot loops stop.
Device(s): dumped the bionic. now have galaxy nexus!
Carrier: Not Provided
Thanks: 47
Thanked 66 Times in 55 Posts
Quote:
Originally Posted by ymDroid
Try turning on the wifi in public, away from any remembered wireless networks. See if it goes into a boot loop.
Then turn on the wifi at your home or somewhere you have a remembered network and leave it on. Then walk away from your wifi network until the wifi completely falls out and the phone flips completely to 3g or 4g. See if it starts to reboot.
If it doesn't, your one of the fortune few.
Yeah wifi was on at the store where i got tge phone, didnt turn it off till i got home. No probs.
Device(s): Samsung Galaxy Nexus and Motorola Droid X2
Carrier: Not Provided
Thanks: 0
Thanked 0 Times in 0 Posts
I had the first one sold in Las Vegas and it had the boot loop problem. took it back and they replaced it. the second one had the same issue. they replaced it again and now my third on has been fine but I am happy to know that I am not the only one with that problem. I keep bring the phone back and they were thinking that I was trying to run a scam. Also I noticed it does do that also when you plug it into a charger that is not purchased from verizon themselves
People need to call VZW tech support and Samsung and report it, this will force them to fix it.
According to Samsung, I was the first people to ever call it in, but they created a ticket for it. The tech made it seem that the issues with the most calls or trouble tickets take the priority.
I think everyone should call both in as soon as possible.
When I called it was 2PM on release day, and the young lady who helped me said I was the first one to call (at least on her personal line) about an issue with the SGN. Did not call samsung/google. Witholding further judgement until I get the replacement.
I walk in to a Verizon store, and get with the tech and flip on the wifi, and all the techs gather in amazement because they've never seen a Galaxy boot loop.
So the tech thought it is being caused by the hardware. The demo in the store dis not boot loop when we turned on the wifi.
I factory reset the store demo, and turned the wifi on, and surely, it did not reboot.
The tech pulled out a phone form the brand new batch that came in today, and replaced my phone for the 3rd time. We reinstalled everything from my Google account, and turn on the wifi.....and the reboots began.
SO BASED ON THIS, I BELIEVE I HAVE A FIX...
So far, I have the my phone up and running, and wifi switched with no problem.
HERE'S WHAT I DID...IN THIS ORDER...
***I would get a replacement phone form VZW first, but fell free and try this on your current phone before replacing.
***Make a list of all your apps...you'll have to manually reinstall them.
1) I factory reset the phone.
2) I booted it back up, and let the phone activate.
3) I DID NOT back up my data from my Google.
4) I DID NOT back up my contacts from VZ Backup Assistant.
5) Phone the phone is fully booted up, I turned on the wifi. The phone should NOT boot loop.
6) Add your home wifi network. Your phone should not boot loop.
**At this point, I walk a half black from my house to make the wifi flip to 3g. It did not boot loop.
7) I installed the 4.0.2 update. Your may already have it.
**At this point, I walk a half black from my house to make the wifi flip to 3g. It did not boot loop.
8) I added my Google account, this only added my contacts. (everytime, and walk away and make sure the wifi flip doesn't force it to boot)
9) I added VZ Backup Assistant, and still good.
SO...right now, the Nexus is running with no problem, and it does not boot loop.
Over the rest of the night , I will being to reinstalling each app one by one and see if the boot loop happens at any point.
But as of right now, it's definitely a software issue related to my backed up account. But what exactly, I don't know.
Hope this works for you if you decide to try it. Remember to make a list of your apps.
The Following User Says Thank You to ymDroid For This Useful Post:
The Galaxy Nexus is the third official phone contracted by Google and the first phone to come with Android 4.0 Ice Cream Sandwich. Specs include a 1.2GHz dual-core processor, 1GB of RAM, 16/32GB of internal storage, a 4.65 inch 720p HD Super AMOLED... Read More
1Likes
Stuck in boot loop
