Go Back   Android Forums > Android Phones > Samsung Galaxy Nexus

New Forums: Nexus Player | Nexus 9
Like Tree3Likes
  • 1 Post By umataro42
  • 1 Post By Benjamin Crist
  • 1 Post By jeff442

test: Reply
 
LinkBack Thread Tools
Old June 4th, 2012, 11:33 PM   #1 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Nov 2011
Location: Valencia, CA
Posts: 18
 
Device(s): ASUS Transformer TF-101, Verizon Galaxy Nexus
Carrier: Not Provided

Thanks: 7
Thanked 3 Times in 2 Posts
Default (VZW) Nexus 4.0.4 Update - wont install

So I've had no trouble getting the IMM76K downloaded more than a dozen times (I haven't actually counted.) I got it downloaded the first day; and every time it always goes the same. Download it, verifies it, then asks me to install it. I tell it yes, it reboots after about 10 seconds. Then instead of any kind of installation, the phone boots back into 4.0.2 and asks me to accept the Google terms for location services.

I've tried downloading the update Seventeen ways from Sunday but I don't think that has anything to do with it. So my next thought is to backup the phone, wipe it and try the install when it's all fresh.

My phone is 100% stock, the bootloader is still locked and nothing custom at this point. Though I feel like if I'm going through all the trouble to wipe it and install this update I may as well unlock it and install a custom ROM.

So any good ideas as to why it wont install before I start playing with one of my most important tools for work?

Also, anyone else have a similar issue? I can't be the ONLY ONE who's had this exact issue!

Advertisements
BlackHawk1776 is offline  
Reply With Quote
sponsored links
Old June 4th, 2012, 11:45 PM   #2 (permalink)
Member
 
Join Date: Aug 2010
Location: San Pedro, CA
Gender: Male
Posts: 301
 
Device(s): Nexus 5, Nexus 7 (2012), Galaxy Nexus, Motorola Droid
Carrier: T-Mobile

Thanks: 58
Thanked 63 Times in 49 Posts
Default

Are you seeing the Android lying on its back with a red triangle above an open panel? Because it seems like a couple people on here (myself included) are getting that problem when it tries to install the update.
umataro42 is offline  
Reply With Quote
Old June 4th, 2012, 11:56 PM   #3 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Nov 2011
Location: Valencia, CA
Posts: 18
 
Device(s): ASUS Transformer TF-101, Verizon Galaxy Nexus
Carrier: Not Provided

Thanks: 7
Thanked 3 Times in 2 Posts
Default

No, I don't even get that displeasure - it goes straight to the normal boot animation. (Which is nice, but it's better when it's 4.04 after it's done booting!)
BlackHawk1776 is offline  
Reply With Quote
Old June 5th, 2012, 04:48 AM   #4 (permalink)
Senior Member
 
trophynuts's Avatar
 
Join Date: Jul 2010
Location: SouthEastern US
Posts: 5,625
 
Device(s): Iphone 6 Moto G LTE
Carrier: T Mobile

Thanks: 1,844
Thanked 1,885 Times in 1,207 Posts
Default

try doing a factory reset and then grabbing the update.
trophynuts is offline  
Reply With Quote
Old June 5th, 2012, 06:15 AM   #5 (permalink)
New Member
 
Join Date: Jan 2012
Location: illinois
Posts: 2
 
Device(s): Galaxy Nexus cdma
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via AIM to sommd
Default

i received my update this morning 4.04 i515.09 v fc04 i515.fc05 no problems i'll check it out today
sommd is offline  
Reply With Quote
Old June 5th, 2012, 07:23 AM   #6 (permalink)
New Member
 
Join Date: Mar 2011
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default (VZW) Galaxy Nexus 4.0.4 wont update

I am also having trouble updating to 4.0.4...But my situation is a little different.

I am rooted with and have an unlocked boot loader. No MODS or anything special. I have actually rooted my girlfriends Galaxy Nexus the exact same way that I have rooted mine and some how hers updated fine on the first try. I guess the only difference is that I have "Nova Launcher" and she does not.

I have been trying to update my phone 2 ways now.

First, i actually get a pop up prompting me that there is a new update. It asks me if I want to (Install later/Not Now/Install Now). Of course I choose the NOW!! So, it downloads, reboots, Google pops up with an unlocked lock, and then I find myself at a screen with my little android is standing up with some Blue squiggly stuff in his stomach and then about 1/4 the way through the install, he lies down on his back with a red exclamation mark...

Secondly, I have tried forcing the update by clearing the data through Google Framework. The process goes well at first; In the Google Framework I clear the data, force stop, shut down, battery pull (I have also tried not pulling the battery), then going to Settings\About Phone\System Update. At this point it's already downloading when I get here (I have tried on Wifi and on 4G as well). Once downloaded, it prompts me to restart. Once again, my little android is standing up with some Blue squiggly stuff in his stomach and then about 1/4 the way through the install, he lies down with a red exclamation mark...

Any advice or guidance would be much appreciated
Zaborowski is offline  
Reply With Quote
Old June 5th, 2012, 10:38 AM   #7 (permalink)
Junior Member
 
Join Date: Dec 2009
Posts: 26
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 1 Time in 1 Post
Default

I'm having the same issue as Zaborowski.

My phone is rooted, bootloader unlocked, and everything else, including launcher, is stock.
Benjamin Crist is offline  
Reply With Quote
Old June 5th, 2012, 12:32 PM   #8 (permalink)
Some say...
 
Stigy's Avatar
 
Join Date: Nov 2009
Gender: Male
Posts: 4,100
 
Device(s): Verizon LG G2 Retired: Galaxy Nexus, OG Droid, TMobile G1
Carrier: Verizon Wireless

Thanks: 1,688
Thanked 3,604 Times in 1,624 Posts
Default

Hmmm I remember this being an issue with the GSM variant and not having a recovery installed for some reason.

For those facing the problem, please try these steps:
1. Let’s turn off our Galaxy Nexus then boot into Fastboot mode by holding down Volume Down, Volume Up, and Power button together for about 10 seconds.
2. Choose “Recovery mode” using the Volume Down button. Then hit the Power button to enter recovery.

If something is borked with your recovery you will find out here. I will look for the post that explains how to flash it, but this may be a lead in the right direction.
__________________
It's kind of fun to do the impossible. - Walt Disney

If someone's out in left field, the /!\ Report button is to the left of their post.
If someone gives you right-on advice or positively contributes, the Thanks button is to the right.
Stigy is offline  
Reply With Quote
The Following 2 Users Say Thank You to Stigy For This Useful Post:
BlackHawk1776 (June 6th, 2012), iowabowtech (June 5th, 2012)
Old June 5th, 2012, 12:51 PM   #9 (permalink)
root@android:/ #
 
iowabowtech's Avatar
 
Join Date: May 2010
Location: Iowa|USA
Posts: 10,678
 
Device(s): LG G2
Carrier: VZW

Thanks: 5,459
Thanked 7,741 Times in 4,097 Posts
Default

Quote:
Originally Posted by Stigy View Post
Hmmm I remember this being an issue with the GSM variant and not having a recovery installed for some reason.

For those facing the problem, please try these steps:
1. Let’s turn off our Galaxy Nexus then boot into Fastboot mode by holding down Volume Down, Volume Up, and Power button together for about 10 seconds.
2. Choose “Recovery mode” using the Volume Down button. Then hit the Power button to enter recovery.

If something is borked with your recovery you will find out here. I will look for the post that explains how to flash it, but this may be a lead in the right direction.
Yeah I saw something about that on xda. Supposedly the stock recovery image was borked or something. Also, it'd be nice to verify that the people above don't boot into cwm...that'd explain it too.

Edit:
HERE is the one I was thinking about Stigy. May be different from what you were referring to, not sure.
iowabowtech is online now  
Last edited by iowabowtech; June 5th, 2012 at 12:58 PM.
Reply With Quote
The Following User Says Thank You to iowabowtech For This Useful Post:
umataro42 (June 5th, 2012)
Old June 5th, 2012, 01:05 PM   #10 (permalink)
Some say...
 
Stigy's Avatar
 
Join Date: Nov 2009
Gender: Male
Posts: 4,100
 
Device(s): Verizon LG G2 Retired: Galaxy Nexus, OG Droid, TMobile G1
Carrier: Verizon Wireless

Thanks: 1,688
Thanked 3,604 Times in 1,624 Posts
Default

Quote:
Originally Posted by iowabowtech View Post
Yeah I saw something about that on xda. Supposedly the stock recovery image was borked or something. Also, it'd be nice to verify that the people above don't boot into cwm...that'd explain it too.

Edit:
HERE is the one I was thinking about Stigy. May be different from what you were referring to, not sure.
Yup that would be it, thanks. Verizon Nexus users shouldn't flash that though as that is the GSM recovery, I believe.
Stigy is offline  
Reply With Quote
sponsored links
Old June 5th, 2012, 01:25 PM   #11 (permalink)
root@android:/ #
 
iowabowtech's Avatar
 
Join Date: May 2010
Location: Iowa|USA
Posts: 10,678
 
Device(s): LG G2
Carrier: VZW

Thanks: 5,459
Thanked 7,741 Times in 4,097 Posts
Default

Yeah for any vzw rooted gnexer's the easiest way on the face of the earth would be to use Scary Alien's free app. It has an option to flash stock recovery. Doesn't get any easier than that:

https://play.google.com/store/apps/details?id=sa.root.toolkit
iowabowtech is online now  
Reply With Quote
Old June 5th, 2012, 02:28 PM   #12 (permalink)
Junior Member
 
Join Date: Dec 2009
Posts: 26
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 1 Time in 1 Post
Default

I'm pretty sure it has to do with ClockWork Recovery, but I haven't played with that since I got my phone months ago, so not sure if the issue is due to setting up clockwork recovery to be the default recovery - I'm guessing that is it.
Benjamin Crist is offline  
Reply With Quote
Old June 5th, 2012, 02:42 PM   #13 (permalink)
Member
 
Join Date: Aug 2010
Location: San Pedro, CA
Gender: Male
Posts: 301
 
Device(s): Nexus 5, Nexus 7 (2012), Galaxy Nexus, Motorola Droid
Carrier: T-Mobile

Thanks: 58
Thanked 63 Times in 49 Posts
Default

Quote:
Originally Posted by iowabowtech View Post
Yeah for any vzw rooted gnexer's the easiest way on the face of the earth would be to use Scary Alien's free app. It has an option to flash stock recovery. Doesn't get any easier than that:

https://play.google.com/store/apps/details?id=sa.root.toolkit
Thanks for the link, since it does look like my problem is with the recovery, even though I never switched from stock recovery. Hopefully this will fix it.

If anyone else downloads the app to try this, it wasn't recognizing root. I e-mailed Scary Alien and he said it was doing the same on his phone and would look into it after work.
iowabowtech likes this.
umataro42 is offline  
Reply With Quote
The Following User Says Thank You to umataro42 For This Useful Post:
BlackHawk1776 (June 6th, 2012)
Old June 6th, 2012, 12:50 AM   #14 (permalink)
Member
 
Join Date: Aug 2010
Location: San Pedro, CA
Gender: Male
Posts: 301
 
Device(s): Nexus 5, Nexus 7 (2012), Galaxy Nexus, Motorola Droid
Carrier: T-Mobile

Thanks: 58
Thanked 63 Times in 49 Posts
Default

Scary Alien was kind enough to send me an updated apk, and I was able to use Flash a Stock Recovery, but the update still won't install.

I also tried flashing Clockwork Mod Recovery, and got the same error (but at least I didn't see the red triangle until the very end).

In case it helps to figure out what's wrong, here is the error message in its entirety. I also posted this on XDA-forums and someone said the problem is the system/bin/gzip, the original file being replaced by a new one from busybox.

assert failed: apply_patch_check("system/bin/gizp", "51086995a674ab78fd63b49aa7207df466624897", "5ba3b3ecd509cf6cee37b2f27110310a1f55045")
E: Error in /cache/12f767e7a5d0.incremental.zip
(status 7)
Installation aborted
umataro42 is offline  
Reply With Quote
Old June 6th, 2012, 01:35 AM   #15 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Nov 2011
Location: Valencia, CA
Posts: 18
 
Device(s): ASUS Transformer TF-101, Verizon Galaxy Nexus
Carrier: Not Provided

Thanks: 7
Thanked 3 Times in 2 Posts
Default

I assume when attempting to boot into recovery mode it should have done something other than booting normally? I was able to get the menu, selected recovery mode, hit the power button to select it, then the phone appeared to reboot (Google logo came up again) then proceeded to boot into ICS 4.0.2.

So it sounds like my stock recovery image is borked, that probably explains why I couldn't do a factory reset on my phone a while back when I tried.

My phone is 100% stock, not rooted, not unlocked.

So what's the best way to attack this issue on a 100% stock phone?

I'm still surprised that no one else in the world is having the same issue as me; it really makes a person feel special...ed.
BlackHawk1776 is offline  
Reply With Quote
Old June 6th, 2012, 07:53 AM   #16 (permalink)
Junior Member
 
Join Date: Dec 2009
Posts: 26
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 1 Time in 1 Post
Default

I figured it out....

When I got my GNexus phone, I rooted it and made Clockwork my default recovery.

So last night I looked in the cache folder and found the OTA update and moved it to the sd card folder and renamed it to update.zip and used clockwork to apply it. However, it failed and gave me an error about not finding a file: VZWBackupAssistant.apk

So I used root explorer to rename the file (I didn't delete it, I simply renamed it) back to VZWBackupAssistant.apk and everything worked fine.
iowabowtech likes this.
Benjamin Crist is offline  
Reply With Quote
Old June 6th, 2012, 10:22 AM   #17 (permalink)
root@android:/ #
 
iowabowtech's Avatar
 
Join Date: May 2010
Location: Iowa|USA
Posts: 10,678
 
Device(s): LG G2
Carrier: VZW

Thanks: 5,459
Thanked 7,741 Times in 4,097 Posts
Default

Quote:
Originally Posted by BlackHawk1776 View Post
I assume when attempting to boot into recovery mode it should have done something other than booting normally? I was able to get the menu, selected recovery mode, hit the power button to select it, then the phone appeared to reboot (Google logo came up again) then proceeded to boot into ICS 4.0.2.
So when you select recovery, you don't see the android dude laying down? For the stock recovery, you need to press and hold the power button, then press volume up to access the recovery menu options but if you're not even getting to that point before the reboot then there's something else going on.

Also, have you been unlocked/rooted in the past or stock since day 1?
iowabowtech is online now  
Last edited by iowabowtech; June 6th, 2012 at 10:25 AM.
Reply With Quote
Old June 6th, 2012, 01:01 PM   #18 (permalink)
Some say...
 
Stigy's Avatar
 
Join Date: Nov 2009
Gender: Male
Posts: 4,100
 
Device(s): Verizon LG G2 Retired: Galaxy Nexus, OG Droid, TMobile G1
Carrier: Verizon Wireless

Thanks: 1,688
Thanked 3,604 Times in 1,624 Posts
Default

Quote:
Originally Posted by iowabowtech View Post
So when you select recovery, you don't see the android dude laying down? For the stock recovery, you need to press and hold the power button, then press volume up to access the recovery menu options but if you're not even getting to that point before the reboot then there's something else going on.

Also, have you been unlocked/rooted in the past or stock since day 1?
If he doesn't see anything after selecting Recovery there is no recovery installed on the device.

I will wait until he responds about the unlocked/rooted question and then we can proceed from there. Depends on whether he deleted the reboot-from-recovery.p file or not.
Stigy is offline  
Reply With Quote
Old June 6th, 2012, 04:40 PM   #19 (permalink)
New Member
 
Join Date: Jan 2012
Posts: 12
 
Device(s):
Carrier: Not Provided

Thanks: 2
Thanked 4 Times in 4 Posts
Default

Quote:
Originally Posted by BlackHawk1776 View Post
I assume when attempting to boot into recovery mode it should have done something other than booting normally? I was able to get the menu, selected recovery mode, hit the power button to select it, then the phone appeared to reboot (Google logo came up again) then proceeded to boot into ICS 4.0.2.

So it sounds like my stock recovery image is borked, that probably explains why I couldn't do a factory reset on my phone a while back when I tried.

My phone is 100% stock, not rooted, not unlocked.

So what's the best way to attack this issue on a 100% stock phone?

I'm still surprised that no one else in the world is having the same issue as me; it really makes a person feel special...ed.
Sorry, you're not special! The only "modifications" I've made to my phone is using Nova Launcher. Mine is stock, not rooted, not unlocked. This is what I posted in the main 4.04 thread:

I forced the update again today, it showed downloading "IMM76K" which was about 39 mb. It finished downloading and then set the phone would have to reboot for the install to complete. Once again, I check the android version after reboot and it says "4.02". What the hell?
BlackHawk1776 likes this.
jeff442 is offline  
Reply With Quote
Old June 6th, 2012, 05:24 PM   #20 (permalink)
root@android:/ #
 
iowabowtech's Avatar
 
Join Date: May 2010
Location: Iowa|USA
Posts: 10,678
 
Device(s): LG G2
Carrier: VZW

Thanks: 5,459
Thanked 7,741 Times in 4,097 Posts
Default

If you guys are having that much trouble, I would do one of two things:

1.) Return it
2.) Fastboot flash stock 4.0.4

There may be a silver bullet somewhere but being stock, the options are limited. ESPECIALLY when you can't even access recovery.
iowabowtech is online now  
Reply With Quote
sponsored links
Old June 6th, 2012, 06:57 PM   #21 (permalink)
Member
 
Join Date: Aug 2010
Location: San Pedro, CA
Gender: Male
Posts: 301
 
Device(s): Nexus 5, Nexus 7 (2012), Galaxy Nexus, Motorola Droid
Carrier: T-Mobile

Thanks: 58
Thanked 63 Times in 49 Posts
Default

Quote:
Originally Posted by iowabowtech View Post
If you guys are having that much trouble, I would do one of two things:

1.) Return it
2.) Fastboot flash stock 4.0.4

There may be a silver bullet somewhere but being stock, the options are limited. ESPECIALLY when you can't even access recovery.
There's a couple more options.
3) Just stick with 4.0.2 - I know this is mostly unthinkable, but I haven't had most of the problems with my phone I've seen others report, so its a better option for me than returning it for a different GNex that might have those problems.

4) I've also been looking / asking for help on XDA and there's a few suggestions there.

This FAQ mentions an option of removing the patch check and installation from the installer-script in the ota zip, but I'm not sure I want to try that.
[FAQ]Installing Verizon 4.0.4 OTA, Rooting, Etc. - xda-developers

Here's a link for the more recent article with other people having this problem, but basically its because when the check is run, there's a file that doesn't match with stock. In my case its because when I installed Busybox, it replaced some of the system/bin files with the Busybox version.
umataro42 is offline  
Reply With Quote
Old June 6th, 2012, 08:34 PM   #22 (permalink)
root@android:/ #
 
iowabowtech's Avatar
 
Join Date: May 2010
Location: Iowa|USA
Posts: 10,678
 
Device(s): LG G2
Carrier: VZW

Thanks: 5,459
Thanked 7,741 Times in 4,097 Posts
Default

The patch check thing is a nice trick but IMO if you're going to have fastboot installed anyway (required for that method also), then might as well just fastboot flash the partitions and you're done. That method would come in handy though for leaks where the source may not be available. But now that Google has made the 4.0.4 files public, there's really no need for workarounds.
iowabowtech is online now  
Reply With Quote
Old June 6th, 2012, 10:44 PM   #23 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Nov 2011
Location: Valencia, CA
Posts: 18
 
Device(s): ASUS Transformer TF-101, Verizon Galaxy Nexus
Carrier: Not Provided

Thanks: 7
Thanked 3 Times in 2 Posts
Default

When I hold the buttons I do get the green android laying down with the red arrow pointing to the power button with the given options list.
As soon as I hit the power button to select recovery mode it reboots. (Within a moment I see the Google logo then Boot Animation)

My phone has never been unlocked or rooted, ever.

So it sounds as if some of the various items that were supposed to come pre-packaged didn't make it onto this phone (or got damaged somehow) thus it wont boot into anything but the 'normal' mode. Seems like some files needed for the alternative boot method would be the missing link.

For the most part 4.0.2 does work rather well; not having 4.0.4 though the grass always looks (or sounds) greener. The talk of improved radios sounds like something I wouldn't mind having (my reception isn't super great when sitting at my desk at home - a slight improvement there would always be nice.) My phone only does the 'random reboot' maybe once a month if that so I'm not terribly worried about that. Since an in depth change log is impossible to come by it's hard to know what would be better - also the theory that if all of the changes had to be visible we might as well be on Android 1 still.

Returning it to the store / ordering up a replacement is an option but it seems silly to replace hardware that works fine for a software problem.

So if fixing this in stock form is a real pain, then how tough is it to go the root / unlocked bootloader / custom rom route or some alternative method of installing stock 4.0.4? I don't have any special desire for anything other than snappy performance, the best battery life possible (I go through 2-3 batteries a day) and the ability to use my work apps.
BlackHawk1776 is offline  
Reply With Quote
Old June 6th, 2012, 11:57 PM   #24 (permalink)
root@android:/ #
 
iowabowtech's Avatar
 
Join Date: May 2010
Location: Iowa|USA
Posts: 10,678
 
Device(s): LG G2
Carrier: VZW

Thanks: 5,459
Thanked 7,741 Times in 4,097 Posts
Default

Quote:
Originally Posted by BlackHawk1776 View Post

So if fixing this in stock form is a real pain, then how tough is it to go the root / unlocked bootloader / custom rom route or some alternative method of installing stock 4.0.4? I don't have any special desire for anything other than snappy performance, the best battery life possible (I go through 2-3 batteries a day) and the ability to use my work apps.
I don't blame you, that's the route I would take too, I just didn't want to push you into it. Who knows what you're going to get with a refurb is what I always say.

So basically, you first need to decide how far you want to take it. Do you want to unlock the bootloader, then root and install custom roms from here on out or do you want to unlock the bootloader temporarily, flash the new stock 4.0.4 files and then relock the bootloader as if nothing ever happened? Those are basically your options. There is great flexibility with this phone since it can easily be unlocked/relocked.
iowabowtech is online now  
Reply With Quote
Old June 7th, 2012, 12:19 AM   #25 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Nov 2011
Location: Valencia, CA
Posts: 18
 
Device(s): ASUS Transformer TF-101, Verizon Galaxy Nexus
Carrier: Not Provided

Thanks: 7
Thanked 3 Times in 2 Posts
Default

Right now I'm thinking of going with the stock 4.0.4 - going to custom roms would mean I'd have to play with / research each rom and see if it did anything interesting for me.

As I recall unlocking then locking the boot loader on the next is pretty easy, right? IS there any particular reason to re-lock the bootloader? Does leaving it unlocked stop OTA updates from installing properly?

So the process to do this is to first backup the 'sdcard,' unlock the boot loader, restore the stock recovery and lastly install 4.0.4?
BlackHawk1776 is offline  
Reply With Quote
Old June 7th, 2012, 09:30 AM   #26 (permalink)
root@android:/ #
 
iowabowtech's Avatar
 
Join Date: May 2010
Location: Iowa|USA
Posts: 10,678
 
Device(s): LG G2
Carrier: VZW

Thanks: 5,459
Thanked 7,741 Times in 4,097 Posts
Default

Quote:
Originally Posted by BlackHawk1776 View Post
Right now I'm thinking of going with the stock 4.0.4 - going to custom roms would mean I'd have to play with / research each rom and see if it did anything interesting for me.

As I recall unlocking then locking the boot loader on the next is pretty easy, right? IS there any particular reason to re-lock the bootloader? Does leaving it unlocked stop OTA updates from installing properly?

So the process to do this is to first backup the 'sdcard,' unlock the boot loader, restore the stock recovery and lastly install 4.0.4?

Yep, unlocking/relocking is easy. No, there's no reason to relock bootloader if you're going to root and run custom roms. I only mentioned that idea if you were wanting to get to 4.0.4 "under the radar" and be all stock and locked again afterward. You have the option though to stay unlocked if you're cool with that. The added benefit to that is if you decide to run custom roms later, you don't have to unlock again to do it which means you don't have to go through the BS of backing up the sd card again. Having a custom recovery is what stops OTA's from loading in the future. Also, many roms have code that won't allow OTA's period. But if you just fastboot load the stock 4.0.4 img files, you will end up with true stock including recovery so you WOULD still be prompted for future OTA's even if the bootloader is unlocked still. So that would leave you in a situation where you could just do the very same thing once the next batch of code is released from Google OR you could try to intall via OTA next time around but you have the added option of using the fastboot flash method again if the OTA fails to load like is happening now.

Yeah, you definitely want to back up the sd card because it'll be completely wiped when you run the unlock command.

You can find all the steps you need in the root forum sticky. The most difficult thing of the whole process will be getting the sdk/fastboot set up as it requires additionaly drivers to what you probably have now. Once that's funcional though, it's just a matter of downloading the stock files from Google and flashing them to your phone using known commands. The command set listed in that thread will need to be altered though because it references the stock 4.0.2 filenames.
iowabowtech is online now  
Reply With Quote
The Following User Says Thank You to iowabowtech For This Useful Post:
BlackHawk1776 (June 9th, 2012)
Old June 7th, 2012, 11:00 AM   #27 (permalink)
Junior Member
 
Join Date: Dec 2009
Posts: 26
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 1 Time in 1 Post
Default

So I've had the one-way audio issue twice already with 4.04 - I thought that was supposed to be fixed in this version...anyone else?
Benjamin Crist is offline  
Reply With Quote
Old June 8th, 2012, 01:34 PM   #28 (permalink)
Member
 
Join Date: Aug 2010
Location: San Pedro, CA
Gender: Male
Posts: 301
 
Device(s): Nexus 5, Nexus 7 (2012), Galaxy Nexus, Motorola Droid
Carrier: T-Mobile

Thanks: 58
Thanked 63 Times in 49 Posts
Default Finally updated to 4.0.4!

Finally got the update to work, no more red triangle!

Using the links from XDA ([REF] [HOW-TO] [GSM & CDMA] Official Google OTA update URLs - xda-developers) I got the factory system.img file, extracted it and copied over all the files in the bin folder. The one giving me the error was the "gzip", but another member on XDA mentioned also having to replace "ip" and "ping", which I also ended up having to do. They're files that were re-written by Busybox.

After replacing them, the update worked (using clockwork recovery, didn't have to flash back to stock). The red triangle nightmare is finally over, and getting the update to work will probably be the highlight of my day - not saying that as a bad thing either, it was just a big hassle to finally get this to work.
umataro42 is offline  
Reply With Quote
The Following User Says Thank You to umataro42 For This Useful Post:
BlackHawk1776 (June 9th, 2012)
Old June 8th, 2012, 10:12 PM   #29 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Nov 2011
Location: Valencia, CA
Posts: 18
 
Device(s): ASUS Transformer TF-101, Verizon Galaxy Nexus
Carrier: Not Provided

Thanks: 7
Thanked 3 Times in 2 Posts
Default

So I need to start with step #1 - backup of the device. What is the proper way to backup and be able to recover my settings / program crap (if possible) after I unlock the bootloader (leaving it unlocked) and then manually install the update?

I believe I have the tools needed to unlock the bootloader installed and ready as I followed this article when it came out (12/05/2011) in preparation:
How to: Unlock the Galaxy Nexus Bootloader – Droid Life
as well as this one I believe for one of the components:
Howto: Install the Android SDK - CyanogenMod Wiki

I would have unlocked it as soon as I got the phone but Verizon waited until the 15th and the next day or two after I was headed out of town for a short vacation and never got the chance to unlock then promptly forgot once I returned.

So once I'm done backing up I've got the unlock thing ready to go. Then I need to find the IMM76K image to install - this appears to be the correct image:

mysid IMM76K from ICL53F: http://android.clients.google.com/pa...F.12f767e7.zip OR http://android.clients.google.com/pa...ncremental.zip (both files are identical)

Referenced here:
[REF] [HOW-TO] [GSM & CDMA] Official Google OTA update URLs - xda-developers

So I've got the ability to unlock and presumably the correct image and the instructions provided seem pretty straightforward.
BlackHawk1776 is offline  
Reply With Quote
Old June 9th, 2012, 12:57 AM   #30 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Nov 2011
Location: Valencia, CA
Posts: 18
 
Device(s): ASUS Transformer TF-101, Verizon Galaxy Nexus
Carrier: Not Provided

Thanks: 7
Thanked 3 Times in 2 Posts
Default

So I was searching around for backup info and found that without root it sounds like a 'good' backup is hard or impossible to come by. So I went to start the process by unlocking the bootloader. Much to my surprise when I tried to do that - it was already unlocked. How would Samsung / Verizon release a device into the wild with the bootloader already unlocked? <Shrug> it saved me any labor in re-setup so I'm happy.

I then used the corresponding instructions in the previously mentioned link and it's up and running 4.0.4 now.

Thanks to everyone who helped; much appreciated.

jeff442,

Reboot your phone into the boot options and look CLOSELY (Look more closely than *I* ever did! - it says locked / unlocked at the very bottom in very small text) to see if your bootloader is locked or not; if you're lucky like I apparently was yours may not be locked. If it is then you'll have to go through the extra trouble of re-setting everything up. But basically the process is to install the developer tools (properly,) download a couple of files and rename them (so you don't have to type out mile long names) run a couple of commands from a dos prompt and you'll have your update installing.
BlackHawk1776 is offline  
Last edited by BlackHawk1776; June 9th, 2012 at 01:02 AM.
Reply With Quote
sponsored links
Old June 11th, 2012, 08:37 PM   #31 (permalink)
New Member
 
Join Date: Apr 2012
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by Stigy View Post
Hmmm I remember this being an issue with the GSM variant and not having a recovery installed for some reason.

For those facing the problem, please try these steps:
1. Let’s turn off our Galaxy Nexus then boot into Fastboot mode by holding down Volume Down, Volume Up, and Power button together for about 10 seconds.
2. Choose “Recovery mode” using the Volume Down button. Then hit the Power button to enter recovery.

If something is borked with your recovery you will find out here. I will look for the post that explains how to flash it, but this may be a lead in the right direction.
Quote:
Originally Posted by iowabowtech View Post
There may be a silver bullet somewhere but being stock, the options are limited. ESPECIALLY when you can't even access recovery.
My phone was rooted & had unlocked bootloader and stock rom. My update was fine. My wife's phone was not rooted and had a locked bootloader. Recovery went straight into the OS, so I installed TWRP 2.1.1 and reran the update. Worked.

Try installing a custom recovery. I know CWM is popular but I prefer TWRP. TeamWin Projects - TWRP 2.1 | TeamWin
potestasx is offline  
Reply With Quote
Old September 27th, 2012, 11:25 PM   #32 (permalink)
New Member
 
Join Date: Oct 2010
Posts: 7
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by Benjamin Crist View Post
I figured it out....

When I got my GNexus phone, I rooted it and made Clockwork my default recovery.

So last night I looked in the cache folder and found the OTA update and moved it to the sd card folder and renamed it to update.zip and used clockwork to apply it. However, it failed and gave me an error about not finding a file: VZWBackupAssistant.apk

So I used root explorer to rename the file (I didn't delete it, I simply renamed it) back to VZWBackupAssistant.apk and everything worked fine.
What file did you rename to VZWBackupAssistant.apk? I followed you all the way up to where you moved the update file to the SDCARD folder and renamed it to update.zip. I did the same thing but that's where I got stuck. Can you elaborate a little on this VZWBackupAssistant.apk you're referring to?
Majestyk is offline  
Reply With Quote
Old September 28th, 2012, 10:40 PM   #33 (permalink)
Senior Member
 
colchiro's Avatar
 
Join Date: Jun 2010
Gender: Male
Posts: 8,886
 
Device(s): HP TouchPad, HTC One Max, Dell Venue 11 Pro
Carrier: Verizon

Thanks: 840
Thanked 1,820 Times in 1,413 Posts
Default

That's the Verizon backup assistant that he renamed to disable it and had to rename back to what it was before, to get the install to work. if you didn't mess with backup assistant, your problem would be something different.

Do you get an error message that might indicate what's breaking your install?
colchiro is offline  
Reply With Quote
Reply

Galaxy Nexus
Current Rating:
Rate this Phone:

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



Go Back   Android Forums > Android Phones > Samsung Galaxy Nexus
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 06:02 PM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.