Develop Bugs

[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!

Android update!

Disclaimer: This worked on my phone. I am not responsible if your phone turns into an expensive brick.
I know this isn't quite the update everyone was waiting for I managed to pull the 2.3.6 OTA files. I also managed to figure out how to flash them. Turns out CWM 5 offers root adb access, everything we need to update and root this phone. Note I tried CWM 6 but it said "possible loss of root" so apparently CWM 6 likes to reside on an already rooted phone.
Note this is not the most elegant solution. The most elegant would be a signed update.zip. The second most elegant would be something flashable with CWM or Odin. Too bad I don't know how to do those. I do know how to do this.
The first thing to do is make sure you are on the AT&T stock firmware. It doesn't matter if you've already flashed something else. No need to wipe cache or factory reset or anything (although if you run into problems you should try to do that step). Download it from samfirmware.com. Flash it with Odin. This will put you on stock 2.3.5. Even if you were already on 2.3.6, or rooted, or on Rogers, this will work. After the flash, boot the phone normally, wait a minute or so, and shut it down.
Now for the fun part. AT&T will not push the OTA to a non AT&T customer. The flash will also not work with a modified phone (hence the reflash to stock). How to gain root access to manually flash the OTA? If we install root, it will not install. If we install CWM, we will not have the stock recovery which is required to process the OTA. So...
How about this? We install CWM 5. You can find it here http://forum.xda-developers.com/showthread.php?t=1458153
Then we adb into the phone, and push the OTA files, and then reflash the stock recovery over CWM, and then manually reboot into OTA mode. That sounds crazy... crazy enough to work.
After you've flashed CWM, reboot into it and make sure your phone is still connected to your computer. We won't actually be using CWM, just the root access it provides over adb. Unzip the two zip files below (why use external hosting, I can store zips up to 11 MB on here) into a folder and run fota.bat. Ooo and ahh over your Gingerbread.
But what about root? Well, I posted in another thread a complicated method for rooting 2.3.6 using the root access from CWM, but how about easy? Boot your phone into 2.3.6 and let it sit for a minute or so, and shut it down. Reboot into Odin mode, and reflash CWM over the stock recovery (again). Copy the Superuser zip from the folder you made earlier to your SD card. Flash this with CWM. This is the beta of Superuser 3.2, courtesy of Rom Manager. Download the stericson busybox app from the Market if you want busybox as well.
This was a fun way to kill a weekend

Throws a signature verification failed error.

Try again with the new method

Had a few mild scares. After flashing CWM on stock, it refused to boot into it but after 3 tries and my screen acting up upon boot, it finally booted into CWM. Launched the bat file and it went well. Upon booting up and entering the update process, it froze up at 74% and refused to continue. Rebooted the phone and it once again entered the update process and this time it managed to finish. Phone rebooted and after checking "About phone", my phone is on 2.3.6 stock. When you initially provided the OTA files and the sig check failed, I had a good feeling this would be the only other way to do it as I tried to sign it and it also failed. Thanks for taking the time to post all of this.

Why go to 2.3.6? It´s better than 2.3.5 customized?

Better question: we're getting ICS within the month, so why bother with 2.3.6 when you can just upgrade to 4.x.x when it comes down?
-Ara

AraDreamer said:
Better question: we're getting ICS within the month, so why bother with 2.3.6 when you can just upgrade to 4.x.x when it comes down?
-Ara
Click to expand...
Click to collapse
Because there are some people who will want to stick with 2.3.5/6 . He made this so that those who do, can update to 2.3.6 even when they aren't with AT&T, almost hassle free.

narume said:
Had a few mild scares. After flashing CWM on stock, it refused to boot into it but after 3 tries and my screen acting up upon boot, it finally booted into CWM. Launched the bat file and it went well. Upon booting up and entering the update process, it froze up at 74% and refused to continue. Rebooted the phone and it once again entered the update process and this time it managed to finish. Phone rebooted and after checking "About phone", my phone is on 2.3.6 stock. When you initially provided the OTA files and the sig check failed, I had a good feeling this would be the only other way to do it as I tried to sign it and it also failed. Thanks for taking the time to post all of this.
Click to expand...
Click to collapse
When I was testing this, I saw that behavior if you didn't completely boot up the phone between steps (ie, flash stock firmware, boot phone, flash CWM, boot phone). I don't know what would cause it otherwise. Glad to see your phone made it.

narume said:
Because there are some people who will want to stick with 2.3.5/6 . He made this so that those who do, can update to 2.3.6 even when they aren't with AT&T, almost hassle free.
Click to expand...
Click to collapse
Actually I did it because I've owned this phone for exactly two weeks and discovered all the available ROMs are based on 2.3.5 even though 2.3.6 has been out since December. CWMR with root has been out since January, and since then nobody else has rooted 2.3.6 or found a way to flash it. And I thought, it couldn't be that hard? And even more amazed when I discovered CWMR comes with root out of the box, without even touching /system. The only other missing piece was the stock recovery, which also wasn't out in the wild. 3 birds for one stone
On a side note, if you want to do some cleaning after the OTA and you decide to root, you can delete /cache/fota and /data/fota safely.

Nardholio said:
Actually I did it because I've owned this phone for exactly two weeks and discovered all the available ROMs are based on 2.3.5 even though 2.3.6 has been out since December. CWMR with root has been out since January, and since then nobody else has rooted 2.3.6 or found a way to flash it. And I thought, it couldn't be that hard? And even more amazed when I discovered CWMR comes with root out of the box, without even touching /system. The only other missing piece was the stock recovery, which also wasn't out in the wild. 3 birds for one stone
On a side note, if you want to do some cleaning after the OTA and you decide to root, you can delete /cache/fota and /data/fota safely.
Click to expand...
Click to collapse
Ah, I see. Well, still, being able to flash to 2.3.6 is nice because if anyone ever decides to stick with 2.3.6 they can easily flash the update now. Maybe more people like you will pop up and start pushing out more useful content like this for the Glide so it won't be a dead area of development anymore.

Error while applying update

For a while now I've been getting system updates but they've always failed during application (ie the red exclamation icon after reboot). This wasn't bothering me too much but now that Sprint has finally decided to roll out Jellybean I'm trying to figure out what the issue is. I've never rooted the phone (although I nearly did yesterday before hearing the news re:Sprint). I've gone so far as backing up everything on my phone and doing a factory reset and I still have this happening. Does anyone have any possible idea what might be wrong or what I could check to see what is wrong, like an error log or something similar. The build is IMM76D if that helps.

becktionary said:
For a while now I've been getting system updates but they've always failed during application (ie the red exclamation icon after reboot). This wasn't bothering me too much but now that Sprint has finally decided to roll out Jellybean I'm trying to figure out what the issue is. I've never rooted the phone (although I nearly did yesterday before hearing the news re:Sprint). I've gone so far as backing up everything on my phone and doing a factory reset and I still have this happening. Does anyone have any possible idea what might be wrong or what I could check to see what is wrong, like an error log or something similar. The build is IMM76D if that helps.
Click to expand...
Click to collapse
That is the stock recovery image. You are probably seeing it because you have something that is not stock (i.e., something that you change), whether it be a radio, a kernel, or a system file. If you remember what you change, change it back. Otherwise flash everything back to stock.

efrant said:
That is the stock recovery image. You are probably seeing it because you have something that is not stock (i.e., something that you change), whether it be a radio, a kernel, or a system file. If you remember what you change, change it back. Otherwise flash everything back to stock.
Click to expand...
Click to collapse
Ok, since then I had rooted my phone but decided to reverse it. I've since used WugFresh's Nexus Root Toolkit to flash back to stock, unroot and lock the phone.
Even after doing all of that I'm still getting the same stock recovery image. I haven't done anything since flashing it back to the stock image aside from setting up my google account on it.

Even when returning to stock you likely didn't flash all parts of the image, so you're missing something like the proper bootloader, radio, or recovery for that specific build. This is another great example of why toolkits are a bad idea. You have no idea what you've flashed.

op, go and ask your question in that toolkit thread
Sent from my i9250

workaround to the OTA 4.1.2 with red triangle signal

My phone prompted me to update to 4.1.2. Everytime I press install, it would boot and then stops half way with a red triangle icon. A few minutes later it will boot to 4.1.1. Someone suggested that it may be due to build.prop file. I mucked around with the build.prop trying to get google wallet to work. I don't care about the wallet anymore. All I want is to upgrade to 4.1.2 with no data loss.
Someone on this forum suggested using the GNex TOOLKIT V9.1 to flash Google Stock Image to phone and then the OTA update would work. If I do that, will I lost any data on the phone?
Sorry, NB to android. Thanks.

you messed with system files, the OTA will not install because of that.
you need to replace the files you modified with the original build.prop and any other files that you modified
if you want to go to stock: http://forum.xda-developers.com/showthread.php?t=1626895

Ahh ... it took me a while to get my gnex configured to the way I want. That method sounds like a clean method but at the same time will wipes everything I have configured so far.
I should probably create a second thread to ask a different question, is there a way to disable the 4.1.2 OTA notification nag? I will keep this phone for another month or so before I pass it to someone else.

If you don't care about any changes you've made to the system partition, you can just flash the boot and system images. This will keep your data.
I upgraded this way before the official OTA was out. It will, of course, blow any changes you've made to /system away, but it will keep your user data and all your settings, etc. You normally don't upgrade by "dirty flashing" over top of another system, but nobody I've seen has reported any issues with going from stock 4.1 to stock 4.1.2 this way. I did it, and have had zero issues. Always take a nandroid backup if possible, just in case.
Follow efrant's guide, just only flash boot and system (and NOT userdata)

How to update from stock root 4.1.1 to current?

I'm sure this has been addressed but I can't seem to find a definitive answer. I am bone stock (stock recovery and no custom rom) with just root on AT&T.
There are no missing deleted apps, as I replaced them previously but I still have never been able to do any of the OTA updates. It's starts and then fails.
Is there a way to unroot and the do an OTA update? I am trying to avoid Odin so I dont have to wipe everything and then have to start all over and adjust settings to my liking an also reinstall all of my apps.
I seen there is an option in the Super User app to "completely unroot and uninstall". Will choosing this option allow me to finally do OTA?
I've never installed a custom recovery or a custom rom so I don't know why OTA's always fail. At this point, I dont really care about having root since the only reason I previously wanted it was to remove at&t bloatware but I'd rather have OTA's at this point.
Any advice or direction would be greatly appreciated! Please speak slowly and in layman's terms as I am an old fart that is still a bit of a n00b, lol.
Thanks!!
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

n01un0 said:
I'm sure this has been addressed but I can't seem to find a definitive answer. I am bone stock (stock recovery and no custom rom) with just root on AT&T.
There are no missing deleted apps, as I replaced them previously but I still have never been able to do any of the OTA updates. It's starts and then fails.
Is there a way to unroot and the do an OTA update? I am trying to avoid Odin so I dont have to wipe everything and then have to start all over and adjust settings to my liking an also reinstall all of my apps.
I seen there is an option in the Super User app to "completely unroot and uninstall". Will choosing this option allow me to finally do OTA?
I've never installed a custom recovery or a custom rom so I don't know why OTA's always fail. At this point, I dont really care about having root since the only reason I previously wanted it was to remove at&t bloatware but I'd rather have OTA's at this point.
Any advice or direction would be greatly appreciated! Please speak slowly and in layman's terms as I am an old fart that is still a bit of a n00b, lol.
Thanks!!
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
If you are on stock and have a valid AT&T SIM card in the device with full access to Wi-Fi and the AT&T network, you should be able to get an OTA update. Root could, however, indeed prevent an OTA update so your best bet may be to unroot. You could unroot and uninstall SuperSU from the SuperSU app just as you suggested. This should do it. However, if it doesn't and you would really want to avoid Odin and custom recovery, then you could do a 2-step manual update to 4.3 via stock recovery - first to 4.1.2 and then to 4.3. This will naturally update your phone to (full) stock 4.3 and we can then see if the phone will take the Kit-Kat OTA update from there.
You can see the instructions for the 2-step update via stock recovery in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2387423
1) Download the 2 zip files under update412.zip and update43.zip respectively to your computer
2) Copy the zip files to a good quality (micro) SD card
3) Place the card in your phone and boot to recovery mode by simultaneously holding down the Volume Up, Home and Power buttons
4) Hold the buttons until you see a blue message flash across the screen. Then release the Power button but continue to hold the Volume Up and Home button until you see the Android image appear. Then release the buttons
5) Use the volume up/down key to scroll to <mount from external storage> and the power button to select
6) Navigate to the first zip file (update412.zip) and install. Wait for installation to finish and your phone to reboot.
7) Complete set up. Check your phone settings. Then power off and reboot to recovery again.
8) Repeat the process for the second update file.

Well I tried the unroot feature in SuperSU and then uninstalled it.
I then tried the OTA update again and as usual, it failed about 30-40% in.
Ive never installed a custom recovery or a ROM so I don't get it. All I did was use Mr.Robinsons thread/directions on "how to root without tripping...." just for root only in the sticky.
I give up.:banghead:
Thank you though for responding. I may try the alternative way you suggested when I get time tomorrow and see what happens. Either that or screw it, im stuck with 4.1.1 and now I don't even have root. :banghead:
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

n01un0 said:
Well I tried the unroot feature in SuperSU and then uninstalled it.
I then tried the OTA update again and as usual, it failed about 30-40% in.
Ive never installed a custom recovery or a ROM so I don't get it. All I did was use Mr.Robinsons thread/directions on "how to root without tripping...." just for root only in the sticky.
I give up.:banghead:
Thank you though for responding. I may try the alternative way you suggested when I get time tomorrow and see what happens. Either that or screw it, im stuck with 4.1.1 and now I don't even have root. :banghead:
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
There have been several reports of failed OTA update so you may not be alone here. The process I advised is sure to take you to 4.3 JB without hassle. There is, of course, a manual update process from 4.3JB to 4.4.2 Kit-Kat (the latest OS). You will, however, require custom recovery for this ...
http://forum.xda-developers.com/showthread.php?t=2788357

Larry2999 said:
There have been several reports of failed OTA update so you may not be alone here. The process I advised is sure to take you to 4.3 JB without hassle. There is, of course, a manual update process from 4.3JB to 4.4.2 Kit-Kat (the latest OS). You will, however, require custom recovery for this ...
http://forum.xda-developers.com/showthread.php?t=2788357
Click to expand...
Click to collapse
Well I finally was able to update via OTA. I had to actually use Kies and reinstall firmware and then go through all the updates, starting from scratch and took forever. What an absolute pain in the ass. Plus, after all this work to go from 4.1 to 4.4..........I can't see where it was worth it. I am now going through the tedious task of setting up all the settings and widgets and everything else the way it was or the way I like. So much for Kies actually backing up and "restoring" anything.
I have a couple of questions though....
1. Now that I am on 4.4..........how do I root this version (that works). I was reading the thread saying to use towelroot but it's not confirmed if this is still working after I guess you do the OTA after a certain date and it's now patched. I DO NOT want to install custom roms or anything else. All I want is root so that I can remove the AT&T crapware that is now even worse with this phone on 4.4.
2. I have a battery percentage that is in the LEFT upper corner that I can not figure out what program or app it is associated with and I can not get rid of it. This is not the % indicator that is part of Android and next to the battery icon on the right which is on and is okay, this is one the left.
3. I hate the new PIN lockscreen because the keypad/numbers are so small compared to old version. Any way to fix this?

n01un0 said:
Well I finally was able to update via OTA. I had to actually use Kies and reinstall firmware and then go through all the updates, starting from scratch and took forever. What an absolute pain in the ass. Plus, after all this work to go from 4.1 to 4.4..........I can't see where it was worth it. I am now going through the tedious task of setting up all the settings and widgets and everything else the way it was or the way I like. So much for Kies actually backing up and "restoring" anything.
I have a couple of questions though....
1. Now that I am on 4.4..........how do I root this version (that works). I was reading the thread saying to use towelroot but it's not confirmed if this is still working after I guess you do the OTA after a certain date and it's now patched. I DO NOT want to install custom roms or anything else. All I want is root so that I can remove the AT&T crapware that is now even worse with this phone on 4.4.
2. I have a battery percentage that is in the LEFT upper corner that I can not figure out what program or app it is associated with and I can not get rid of it. This is not the % indicator that is part of Android and next to the battery icon on the right which is on and is okay, this is one the left.
3. I hate the new PIN lockscreen because the keypad/numbers are so small compared to old version. Any way to fix this?
Click to expand...
Click to collapse
Glad to know you were finally able to update. To try to answer your questions ....
1. Towelroot indeed comes well recommended for rooting on Kit Kat. You could, however, first try CF Auto Root which is one of the simplest approaches to rooting. If this doesn't work, you could try Option 2 in the thread below ... The thread also contains instructions to CF Auto Root.
http://forum.xda-developers.com/showthread.php?t=2538991
2. I'm not sure what that battery indicator is. I run 4.4.2 also on my S3 but I cant see this. Can you try a reset to see if it would go away?
3. You can try removing this from settings.

Im glad you asked this...
I too noticed Im on 4.1.1 stock but rooted. I wondered if you could go to 4.4.2 as my phone tried to OTA update on its own last week and failed. I did not know if it was worth it to try or not another way. About the only thing I see that would want me to try is Google Wallet now working with S3 on 4.4.2 without having to jump through all kinds of hoops, mine used to work fine, but now GW will not open up all the way. Im not sure its worth doing if I have to re setup all my crap as I will be upgrading my phone whenever I want, just holding out to see if the Nexus 6 will be out end of the year and on AT&T..Im not liking that all the new phones are getting so freakin big, the S3 is just right and I dont want to have to end up with a damn Note sized phone but that is a whole other discussion

If you're still on 4.1.1, BEFORE ANYTHING ELSE, UNLOCK YOUR PHONE IF HASN'T ALREADY
otherwise you'll regret it
then the rest, tbh, you don't need to unroot at all to upgrade, just flash the firmware in ODIN or recovery..
edit: nvm it seems like you've already upgrade yours to KitKat