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!

Telus update to JB. Can I switch sims?

I cannot get JB still. I bought the phone from rogers and just use it on Telus.
Always when I try it gets stuck on bootloop.
Could I just borrow somebodies sim from rogers or fido and let them get the OTA?
not really sure how to get JB. Nothing has worked so far.

The OTA has absolutely nothing to do with what SIM you have in your device.

martonikaj said:
The OTA has absolutely nothing to do with what SIM you have in your device.
Click to expand...
Click to collapse
then howcome it won't let me update my phone?
I've tried roms, I've tried stock.
Not sure what's holding me back.

Mackie011 said:
then howcome it won't let me update my phone?
I've tried roms, I've tried stock.
Not sure what's holding me back.
Click to expand...
Click to collapse
If the OTA update bootloops your stock phone, you've likely changed something (knowingly or unknowingly) that's causing a conflict when the update applies. Also, you haven't indicated how you're trying to update.
What do you mean you've tried ROMs? That'll have nothing to do with OTA updates. Custom ROMs are a completely different path.

martonikaj said:
If the OTA update bootloops your stock phone, you've likely changed something (knowingly or unknowingly) that's causing a conflict when the update applies. Also, you haven't indicated how you're trying to update.
What do you mean you've tried ROMs? That'll have nothing to do with OTA updates. Custom ROMs are a completely different path.
Click to expand...
Click to collapse
Okay so at first I had paranoid android running fine and I had AOKP.
When JB was released I tried to just try a new rom but it would always go to the boot screen and just sit there forever.
I gave up and decided to factory reset everything completely and just went back to stock to try to get the over the air update. It constantly pops up, every 5 minutes. Update available! This has been happening for a long time I just decided I will use 4.0.4 for now because I couldn't figure out what I did wrong or what I was missing.
And that is pretty much where I am at right now.
Not really sure how to make it work.

Mackie011 said:
Okay so at first I had paranoid android running fine and I had AOKP.
When JB was released I tried to just try a new rom but it would always go to the boot screen and just sit there forever.
Click to expand...
Click to collapse
Likely didn't wipe properly, chose the wrong ROM, or tried to switch between ROM makers unsuccessfully.
I gave up and decided to factory reset everything completely and just went back to stock to try to get the over the air update. It constantly pops up, every 5 minutes. Update available! This has been happening for a long time I just decided I will use 4.0.4 for now because I couldn't figure out what I did wrong or what I was missing.
Click to expand...
Click to collapse
When you flashed back to stock it didn't flash properly, or missed part (like recovery, bootloader or radio), so the OTA won't install properly.
If you want stock 4.1.1, just flash it completely. Stop trying to mess with an OTA.
This is the only guide I'd recommend: http://forum.xda-developers.com/showthread.php?t=1626895
Factory images... including 4.1.1 are right here: https://developers.google.com/android/nexus/images

As well, some have reported issues trying to flash JB if they had an old bootloader. Make sure you flash the LC03 bootloader before trying to flash a JB ROM. (It's already part of the guide mentioned above.)
Sent from my Galaxy Nexus using Tapatalk 2

[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

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)

Phone stuck on splash screen after security patch update

Hi all,
I have an HTC One M8 which is SOFF, Rooted, and bootloader unlocked via Sunshine but otherwise completely stock. Today I installed the new security update that's supposed to fix the Stagefright MMS vulnerability, and now the phone won't boot past the HTC splash screen.
I did some searching and found out how to power down the phone and get back into recovery, which I can do, but clearing the cache didn't seem to fix the problem. Anything else I can try while I'm away from my PC to get the phone to boot? I also tried removing the SD card in case that was the problem, but that didn't work either.
Once I get home from work I can do things with ADB if necessary.

I haven't seen the update, though I did see a weird notification yesterday. However, I would point out that rooted means you are not stock, and Lollipop updates seem to never work unless you are 100% bone stock.

yea i haven't really researched it, but if not mistaken stock lollipop does a sort of hash check on the system partition and if it doesn't match to what they have on file ie. being rooted which causes system changes. It becomes problematic so your best bet is to either restore from a backup or reflash which ever rom you have. Hopefully you can reflash without loosing all your data (custom rom instead of an RUU).
As for the patch. Wait until a rom developer incorporates it into their own roms. Or if its as simple as a system apk update or file change you can extract it from the update and replace it yourself.
If you were using a nonstock/custom kernel. Try reflashing just that kernel since maybe its as simple as that update containing a boot.img which you can reflash without much fuss. Unless the stagefright fix is within the kernel itself.

Balls!
The update was only 40MB or so, so I figured it wouldn't mess with anything major. However during the process it rebooted back into I assume recovery and/or the upgrading screen with the little progress bar and pic of the phone in it, so it must've been reworking something.
Hopefully I can mount the volume and pull my pictures and whatnot off when I get home. I should've known better not doing a backup first!
If I have to reflash, maybe I'll try the GPE ROM for a while or go back to good ole fashioned CM.

Firehawk989 said:
Balls!
The update was only 40MB or so, so I figured it wouldn't mess with anything major. However during the process it rebooted back into I assume recovery and/or the upgrading screen with the little progress bar and pic of the phone in it, so it must've been reworking something.
Hopefully I can mount the volume and pull my pictures and whatnot off when I get home. I should've known better not doing a backup first!
If I have to reflash, maybe I'll try the GPE ROM for a while or go back to good ole fashioned CM.
Click to expand...
Click to collapse
if anything you should be able to use twrp to make a back up of your data partition and reflash your current rom, install the update (while fully stock) and restore your backed up data partition on top of your stock build (kernel/ true cause depending) without much issue. But thats a 50/50 shot.
If the update did a reboot to RUU mode (black screen HTC logo with progress bar) it more than likely updated a partition whether it was a new stock recovery or boot partition.
haha balls... I'm slight intoxicated

Tachi91 said:
if anything you should be able to use twrp to make a back up of your data partition and reflash your current rom, install the update (while fully stock) and restore your backed up data partition on top of your stock build (kernel/ true cause depending) without much issue. But thats a 50/50 shot.
If the update did a reboot to RUU mode (black screen HTC logo with progress bar) it more than likely updated a partition whether it was a new stock recovery or boot partition.
haha balls... I'm slight intoxicated
Click to expand...
Click to collapse
Thanks for that! I'll throw TWRP on there and back that data up.
And now I just got this song stuck in my head:
www.youtube.com/watch?v=WL2txMU50CI