Develop Bugs

Help, Nexus keeps rebooting non stop

My coworker has the Galaxy-Nexus, as do I, we have the Verizon version. Both phones rooted back in January, mine has been rock solid table running Android Revolution HD ROM, I have zero issues.
My friend is running same ROM, says FaceBook app, or Alex Jones podcast make his phone act weird. Well over the weekend it just started rebooting to the Google start up screen, and constantly repeats. Today I tried pulling battery, then going into recovery, did Wipe factory data / reset, and reinstalled the ROM fresh, but same thing, the phone keeps rebooting in a loop.
What else can I do to try and fix this ?

Interesting coincidence?!
http://forum.xda-developers.com/showthread.php?t=1533576
See my update, but you will perhaps have some data loss!
I got no reboots so far anymore.

lighthammerhh said:
Interesting coincidence?!
http://forum.xda-developers.com/showthread.php?t=1533576
See my update, but you will perhaps have some data loss!
I got no reboots so far anymore.
Click to expand...
Click to collapse
Thanks for the link, where can I get the original Google stock image ?

Install the ToolKit from here: http://forum.xda-developers.com/showthread.php?t=1392310
Set up the needed driver properly and be sure everything works.
Than select the option 8:
Extract and Flash Google Factory Stock Rom [Fastboot Mode]
It tells you where to download the file and what you have to do with it.

lighthammerhh said:
Install the ToolKit from here: http://forum.xda-developers.com/showthread.php?t=1392310
Set up the needed driver properly and be sure everything works.
Than select the option 8:
Extract and Flash Google Factory Stock Rom [Fastboot Mode]
It tells you where to download the file and what you have to do with it.
Click to expand...
Click to collapse
thanks, this really helped me out. back to 4.1

[SOLVED] Completely stock GSM Galaxy Nexus -- 4.0.4 update stuck at Google screen

Update (5/2/2012):
I think I've isolated the issue as a broken recovery image. It appears that some of us received a broken 4.0.2 OTA and are now suffering for it.
This issue can be completely fixed by manually installing the 4.0.4 update. For reasons stated in my post below (message #9 in this thread), I do not think this issue can be fixed with an OTA update, so don't wait for Google to fix this. Fix it yourself or send it back for a refund.
----
Title says it all.
I have a completely stock GSM Nexus running 4.0.2, YAKJU build. Several times, I have received the notification that the 4.0.4 OTA update is available. Each time when I try to take the update, the phone reboots and gets stuck at the "Google" screen indefinitely.
At this point, the only way to shut the phone off is to remove the battery.
Has anyone else had this problem? I can't believe Google is unable to deliver a working update to a stock phone, especially after the months of delay this has been. (My phone is nearly unusable on 4.0.2 due to the keyboard lag, random reboots and other issues.)
I really don't want to mess with the bootloader due to warranty issues.

Same thing is happening here. Completely stock on 4.02, receive notification for 4.04, downloads, reboots to install, doesn't get past "Google". Not sure what's going on there...

Same here, tried twice now. Left it for about an hour and it went through a stage of the back of the phone getting warm (antenna location, I believe... at the top by the camera) then cooled down later. I thought maybe it was downloading the update? Not sure if it normally downloads before or after the reboot.
Additional info:
Mine's wasn't originally yakju, but I flashed to yakju 4.0.1 from yakjuux (or whatever) when I got it months ago, and was able to get the 4.0.2 update OTA just fine.

Mine was yakju out of the box, so I don't think it's a flashing issue.

Yep, mine too. YAKJU out of the box. I haven't done anything to mod this phone.

I'm going to try to manually update it in the next day or two and share results

No factory reset either
Huh. I thought maybe doing a factory reset from the Settings menu would help. In fact, I can't do that either!
After clicking through all of the confirmation dialogs, the phone reboots and.... get stuck at the Google screen. I have to pull the battery out, just as when applying the 4.0.4 update. Luckily the phone will start up again, but the wipe never happened.
It looks like there's a problem with some Galaxy Nexuses being able to go into recovery, perhaps?

Hi All
I got the exact same problem. Out-of-the-box, no mods, no root, 4.0.2. Got the OTA to 4.0.4 the third time this morning. Still can't pass the "Google" screen.

Solved -- sort of.
Hey all,
I spent some time investigating this issue. Here's what I've determined: for those of us affected with this problem, it appears that we somehow received a botched installation of 4.0.2 (the version we're running currently). What's the botch? Our phones don't have a working recovery image.
You can test this by trying to enter recovery. Turn off your phone. Then, simultaneously press and hold volume-UP, volume-DOWN, and POWER until a screen with an Android on his back appears. This is the fastboot screen. From here, you can choose 'Recovery'. If your phone is like mine, any attempt to go to Recovery will just put you in the dreaded Google logo loop.
So, what's the solution? I'm afraid the only way to resolve this yourself is to unlock the bootloader and do a complete install of the 4.0.4 image yourself. One step of that process is to flash an updated recovery image; this will cure the issue. Fortunately, on the Galaxy Nexus, you can easily re-lock the bootloader with a single command. I have done all of this and can confirm that it works.
If you're not comfortable unlocking the bootloader, the only other way to fix this is to send it back to the vendor. I have a strong suspicion that phones affected by this bug are unable to receive any further OTAs at all. This means Google can't fix your phone by pushing out a different OTA.
Final warning: until this is fixed, you can't do a factory reset, either -- that process will fail because it, too, uses the recovery. So don't plan on selling your phone on eBay until you get this fixed.

Your research is much appreciated modenastradale. It seems this is a fairly big **** up on Google's part. But I guess these things happen. I don't have any particular problems with unlocking the bootloader, I just didn't feel like wiping the phone right now and having to reinstall and set everything back up again which is why I've remained stock this whole time.
Unlike previous phones, this one has felt great out of the box, so I've never had the need to root it to get more performance out of it.
I guess this will be the project for the weekend. Yay!

Looks like a good opportunity for me to switch to the US version (takju).. even though it's 99.9% the same right now. Just in case they give us a better radio for the region.

Idea:
What if I flash the recovery only? (like step D.12 here: http://forum.xda-developers.com/showthread.php?t=1626895)
I already have an unlocked bootloader, so it looks like I wouldn't need to wipe the system to unlock it. I guess I would get the 4.0.2 full image and flash that recovery (not the 4.0.4), though I'm not sure it would made a difference anyway.
I might try it out, but still interested in maybe switching to Takju anyway. I thought about anything that I'd lose by wiping, and since almost everything is on google's cloud (gmail, google music, coctacts, pics on google+, etc) it's not a big deal to wipe.

Fixed
The method I suggested in the last post worked!
You need to be able to flash a recovery image though, which I think would mean you need an unlocked bootloader? The benefit of doing this over just flashing the complete 4.0.4 image is that you don't need to wipe the phone (assuming you already were unlocked)
In more detail, here are the steps I took.
- Preparation (I already had this done) - have Samsung drivers installed on your PC, ADB, fastboot, etc. - check other threads for how to, such as: LINK
- Follow this post's how-to for flashing the recovery image - the poster also has the stock 4.0.2 link, which I can't find on google's site anymore: LINK
- The only command I ended up using is
Code:
fastboot-windows.exe flash recovery F:\recovery.img
Where F:\ was the location I extracted the image file to.
- Restart via:
Code:
fastboot reboot
- When it restarted, it gave me the OTA notification and was able to install fine.
I don't know if the OTA notification would automatically show for everyone, if not you can try to check for updates in the settings or try some of the step on the thread: LINK

related issue
I found and issue on code.google.com that seems related to this.
I'm linking them in the hopes of getting some official response about this.
Just search for number 29954 on code.google.com as I'm not allowed to post links here yet.

This worked perfectly for me. Glad to have that done with. Didn't lose any data at all.

I have this issue also. Stock Galaxy Nexus from the Spain, no mods, not unlocked.
Its necesary unlock bootloader to flash a recovery image

I can reboot my Nexus after going through the install of 4.0.4 (my phone don't get stuck at the Google logo), but the version stays at 4.0.2 however.
Do I also have to unlock bootloader and flash 4.0.4 etc. or is there another way to work around the update problem?
Stock and unlocked Galaxy Nexus bought (and in use) in The Netherlands.
Thanks!

JB Stuck on X-Symbol in bootup

Hi guys,
did not find any related problem, so i open this new thread:
I flashed my Samasung Galaxy Nexus GT-i9250 with the stock google factory firmware image yakju maguro IMM76I.
This worked really well and I was good to go with the ICS system.
Then i recieved the OTA update from that 4.0.4 version to the jelly bean 4.1.1
The installtion worked well and the patches/updates were applied.
To that point everything looks good. BUT, after the reboot i'm stuck in the boot up procedure on the point
where the 4 color X symbol appears. I tried that stock-flash then update method in combination with and without
the CWM tools and with/without wiping of cache, data and so on.
I can not pass that boot screen and i am already waiting for 1 hour. Restarting does not help either. Wiping also
does not help. Delvik wipe also does not help ...
Radio, System and everything was on stock before i applied the update to jb. What could be the problem here,
i run out of ideas...plz help

xpawellx said:
Hi guys,
did not find any related problem, so i open this new thread:
I flashed my Samasung Galaxy Nexus GT-i9250 with the stock google factory firmware image yakju maguro IMM76I.
This worked really well and I was good to go with the ICS system.
Then i recieved the OTA update from that 4.0.4 version to the jelly bean 4.1.1
The installtion worked well and the patches/updates were applied.
To that point everything looks good. BUT, after the reboot i'm stuck in the boot up procedure on the point
where the 4 color X symbol appears. I tried that stock-flash then update method in combination with and without
the CWM tools and with/without wiping of cache, data and so on.
I can not pass that boot screen and i am already waiting for 1 hour. Restarting does not help either. Wiping also
does not help. Delvik wipe also does not help ...
Radio, System and everything was on stock before i applied the update to jb. What could be the problem here,
i run out of ideas...plz help
Click to expand...
Click to collapse
This is happening to a few Verizon users like myself who are flashing to a JB rom and still can't get past the Google X screen. It's a shame that it is happening to someone updating through an OTA. I don't have any help for you because I have tried everything, but I want to try and keep this thread alive in hopes that someone out there has had a greater than 30 minute boot time and was able to get past it. So far I haven't found anyone.

nothingshocking said:
This is happening to a few Verizon users like myself who are flashing to a JB rom and still can't get past the Google X screen. It's a shame that it is happening to someone updating through an OTA. I don't have any help for you because I have tried everything, but I want to try and keep this thread alive in hopes that someone out there has had a greater than 30 minute boot time and was able to get past it. So far I haven't found anyone.
Click to expand...
Click to collapse
I really can not believe, that a stock ics image + update to jb does not work. And i do not see any possibility to dump get access to the
boot log information. That way i could at least try to find the point where the boot procedure stops/waits.
Hopy anybody knows a solution for this. If not, i will have to wait for the official stock image for 4.1.1 from google.

Same here I can flash ics rom..restore without problem.. but every time I flash jb rom it always stay in nexus logo.. I've waited for an hour to 2hrs... nothing only infinite boot loop.
Sent from my Galaxy Nexus using XDA Premium App

landrian18 said:
Same here I can flash ics rom..restore without problem.. but every time I flash jb rom it always stay in nexus logo.. I've waited for an hour to 2hrs... nothing only infinite boot loop.
Sent from my Galaxy Nexus using XDA Premium App
Click to expand...
Click to collapse
As far as i can image, this must be due to some hardware revision differences between the devices. Since the whole firmware+software package
is exactly the same on every device after a clean flash to the factory image, this is the only difference left i can think of.
If that is true, google has to do some work on the jelly bean sources to fix that problem. And again ... i know no way to get debug information from a device taht is stuck in the boot logo... :crying:

i need to re-flash the stock takju 4.1.1 on my phone.

could someone post the link to where i can download the actual file. i did a manual update from ics to jb through the toolkit, but something got messed up. my phone has not been working properly. i was just going to flash the entire clean JB rom again, but i'm a complete noob and can't find it. i've searched the forum, but i get super confused with the multiple rom/files threads.
can i just downloand the factory image of the jb 4.1.1, boot into cwm and just flash that file. I believe it will wipe everything and lock my bootloader again. i've been trying to sort things out, but it's driving me crazy, especially my contact search. normally, the people you call most frequently show up right away as you type or two letters of the name and at the top of the search. for me, it's always at the bottom of the list. it's super annoying. i have to scroll all the way down to select them. also, the pics that i take with my camera only appear as files on my comp. there's no preview of the actual pictures. for work, i always need to select/pick out a couple, but now without seeing the image, i have to manually click through each picture, open each one until i find the one i need.

http://forum.xda-developers.com/showthread.php?t=1626895

i used the nexus toolkit to flash the google factory image. is that the same thing as flashing the stock rom?

wasya152 said:
i used the nexus toolkit to flash the google factory image. is that the same thing as flashing the stock rom?
Click to expand...
Click to collapse
You know adb and fastboot controls? If so, you can easily reflash... assuming that you got stock recovery, do fastboot boot cwm.img (you need to download clockwork recovery and put it into the fastboot directory)
Then just flash the zip file of stock Jelly Bean.
You can find stock ROM in Google developer site I believe.
Sent from my Galaxy Nexus using xda app-developers app

well, i now believe my issue was not a update problem, but instead a jb issue. i got a new galaxy nexus for my wife last week and when it came in i set it up for me first. tried using it and same issues as i'm having. i guesss it's a coding issue, than an update. the phone has same issue with contacts. when you use search bar to look for contacts, the most frequent ones come up all the way at the bottom of list, instead of up top. it's like it's reversed for some reason. also, when i took a picture with the phone, i could not see a preview on the computer either. tried same thing on my nexus 7. i really hope google fixes this, it's really annoying.

[Q] How to get back to Stock ?

Just recently purchased an almost new Nexus that was originally purchased from Google.
Just got the notification that there was an update avail, 4.1.2 but it failed with an error and I see CWM listed.
How can I remove ClockWorkMod and get back to stock android?
Thanks

If you really are running stock 4.1.1 but with CWM (I highly doubt that), then yes flashing stock recovery would let that OTA install.
The reason why I say that's unlikely is that the only reason someone would flash CWM and have it on the device is to use it as a way to modify the device further. I highly doubt that the phone is 100% stock other than recovery. Other things are likely modified that would cause the OTA to fail even if you had a stock recovery on it.
Considering you bought the phone used and it's been modified by the previous owner, I'd 100% flash it back to stock with Google factory images. I would never trust a previous owner's firmware that they flashed. If they were "smart" enough to mess around with it, then they're likely "dumb" enough to put something on there you don't want.
http://forum.xda-developers.com/showthread.php?t=1626895

martonikaj said:
If you really are running stock 4.1.1 but with CWM (I highly doubt that), then yes flashing stock recovery would let that OTA install.
The reason why I say that's unlikely is that the only reason someone would flash CWM and have it on the device is to use it as a way to modify the device further. I highly doubt that the phone is 100% stock other than recovery. Other things are likely modified that would cause the OTA to fail even if you had a stock recovery on it.
Considering you bought the phone used and it's been modified by the previous owner, I'd 100% flash it back to stock with Google factory images. I would never trust a previous owner's firmware that they flashed. If they were "smart" enough to mess around with it, then they're likely "dumb" enough to put something on there you don't want.
http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Thank you very much for the link. I'll have to make sure I don't loose anything since it's my wife's phone. I should have looked more closely when the install bombed out but I saw CWM and there was the typical list of things that you have to increment thru to get to what you want to install. Maybe the big system in the sky will try to do another OTA update before I get around to reinstalling.

All stock but cannot update
martonikaj said:
Other things are likely modified that would cause the OTA to fail even if you had a stock recovery on it.
Click to expand...
Click to collapse
What else can cause it to fail? I was originally on the samsung version of yakju, but I flashed takju (4.0.2) following instructions from XDA. I have everything stock, but I am unlocked and rooted, and my system has updated OTA all the way till 4.1.1. Whenever I get the "Update to 4.1.2" thing, though, I restart and install.
I see:
Android standing with a spinning blue-edged thing (Installing)
The blue bar at the bottom reaches about 1/4 to 1/3 of the way to the end
Android is on its back with an exclamation mark above (Recovery)
Trying to use the menu just lets me restart, install from ADB or USB, revert to factory settings, or wipe cache
Not doing anything causes it to reboot back into 4.1.1
I've looked around, and I couldn't find anyone with the same problem. (It's usually having CWM installed etc.)
Not sure if this is the right place to post it. Should I make a new thread?
Note: I have no access to computers right now. My laptop charger short-circuited and started a small fire. I have a new one ordered, which should arrive sometime these two weeks.

masasin said:
What else can cause it to fail? I was originally on the samsung version of yakju, but I flashed takju (4.0.2) following instructions from XDA. I have everything stock, but I am unlocked and rooted, and my system has updated OTA all the way till 4.1.1. Whenever I get the "Update to 4.1.2" thing, though, I restart and install.
I see:
Android standing with a spinning blue-edged thing (Installing)
The blue bar at the bottom reaches about 1/4 to 1/3 of the way to the end
Android is on its back with an exclamation mark above (Recovery)
Trying to use the menu just lets me restart, install from ADB or USB, revert to factory settings, or wipe cache
Not doing anything causes it to reboot back into 4.1.1
I've looked around, and I couldn't find anyone with the same problem. (It's usually having CWM installed etc.)
Not sure if this is the right place to post it. Should I make a new thread?
Note: I have no access to computers right now. My laptop charger short-circuited and started a small fire. I have a new one ordered, which should arrive sometime these two weeks.
Click to expand...
Click to collapse
2nd post of this thread
http://forum.xda-developers.com/showthread.php?t=1419170
Read it. Part of it is true for official (directly from gservers to the device) updates. If you want, you can then update yourself (read also 1st post) like instructed or put it like it needs to be and use normal update from within android again.
Read the stickies people, before pressing the "new thread/reply to" button.
Sent from my i9250