Share this Story

Galaxy Nexus Android 4.0.4 Build IMM30B Released, Get Your Update on Early


Folks with a Galaxy Nexus, a treat popped up for you online today. Android 4.0.4 is now in the wild and available for you to install via custom recovery. The new build is IMM30B and like I said, brings you to 4.0.4 rather than the 4.0.3 that many were hoping for. There is no official changelog, but this appears to update the radios and bootloader at the very minimum. Funny thing is, I now get 3 bars of 4G LTE at my house, a place that I used to get just 1 or 2 bars. I’d say that bar calculation that Verizon had mentioned is included. Will be digging into it throughout the night to see what else has changed – for now, get to flashing.  

Download Link [mirror] [Google Link]


*These instructions use Clockwork Recovery.

*Reminder: If  you would like to keep root, feel free to try Voodoo RootKeeper before updating.

1.  You will need to be running stock Android 4.0.2 (ICL53F) in order to update to this.

*You will likely have to have stock radios, bootloader, and have made no system changes as well. If you need to flash those, you can get them from our Galaxy Nexus guide.

2.  Download the file from above and rename to update.zip.
3.  Reboot into Clockwork Recovery.
4.  Choose “install zip from sdcard” and then find the file and select it.
5.  Let it flash, reboot and enjoy 4.0.4.

*Note – Rooting instructions here.

And if someone has instructions for updating without using CWM, please let us know. I was unsuccessful in my attempts.

Via:  XDA, AC Forums

Cheers gerry, Jamie and everyone else!

  • Paul Harper

    How are the ROMs thus far I been out to the ROM market since the OG but think I might be interested in a good one soon. Any ideas?

  • Tom

    I’m just going to wait for a rom… Preferably the upgrade to my current (Codename Android)

  • Upgraded from stock 4.0.2 (no root, no cwm) using temporary fastboot of CWM.  No problems whatsoever.  My #1 pet peeve is fixed.  That slight graphics hitch when flipping pages in the app drawer.  Smooth and super fast now.

    And is the “Android OS” calculation in Battery usage much reduced now?  I had 3-4 hours on battery and it’s claiming only 9%, instead of in the 30-40% range.  (My eyes might be deceiving me though)

  • Jslafarr

    why is anyone even trying to f*ck with this? its not official, might break root, and doesnt have ANY features any roms have that are out right now.

    why are people trying to put a leaked 4.0.4 on here without even a changelog!? 

    then this guy “running completely stock” has trouble booting into recovery ???!!!

    i dont even have words.

    • Paul Harper


    • angermeans

      Break root? You have a lot to learn. This is a nexus my friend the oem is google and they know this phone will be rooted. Someone didnt have to find an exploit for root just fastboot oem unlcok and flash superuser. Plus the rest of your post really makes no sense as again this is a nexus and most by this phone so they can tinker. You can always go back. I figured that the galaxy nexus wpuld bring a lot of popularity to the nexus platform and people would not knoww what to do but this is whu we buy nexii is this is how android is supposed to be we arebt fighting the oems to root our phones. Root and nexus go hand in hand its a dev phone.

      • TheRealBeesley

        It actually does “break root”.   So… yeah…  

      • Jslafarr

        Oh boy. Lol.
        What u just said makes absolutely no sense. At least if you’re replying to my post.
        It is possible to brick this phone. Unless you have the sbf files and sdk it. Do you know what that means.
        This is a developers device.
        So let the devs come out with a stable – rooted. – feature packed rom and then flash it.
        Or you can be like all the other bozos and waste your time.

        • Anonymous

          Contrary to what you might think there are folks who want to keep the stock rom. Not some crappy rom full of useless mods that no one wants.

          Also it doesn’t much matter in this instance that it isn’t official, it works just fine.

          Though I do have to laugh at “completely stock recovery” guy. That was funny.

      • Jslafarr

        And learn how to spell

    • Junior Youngman

      Alot of people want to flash this to fix “bugs” from earlier ICS builds. I myself have had the “mic cut out” issue first hand with several of these devices. So if others are having issues that have been reported then they as well are hoping this fixes them. And obviously your running custom roms which 98% of them are built off a leaked 4.0.3 build which actually is a build number for the nexus s 4g. So whats wrong with flashing one leaked build or another?

  • Paul Harper

    You will need to follow these steps again if using temp root after installing the update.
    1.  Download ClockworkMod Recovery for the G-Nex. [Download]
    2.  Place that file in your SDK/Tools folder (same place as your adb.exe).
    3.  Download the superuser file aka the root file. [Download]
    4.  Place that file in your SDK/Tools folder.
    5.  Open a command prompt from within your Tools folder and type the following:

    adb push su.zip /sdcard/

    6. Then reboot into the bootloader:

    adb reboot bootloader

    7.  When the boot menu loads, flash the new recovery image:

    fastboot flash recovery recovery-clockwork-

    8.  When that finishes, use the volume keys to highlight “Recovery mode,” press power to select it.

    9.   From recovery, scroll to “Install zip from sdcard.”

    10.  Then “choose zip from sdcard.”

    11.  Choose the “su.zip” file and install it.

    12.  When that finishes, back out of recovery and reboot the system.

    13.  Enjoy being rooted with a temporary recovery.

    • In step 7, I chose to not flash CWM.      Use fastboot boot recovery-clockwork-    to do a one-time CWM.   You’ll keep your stock recovery, if you want to keep your phone as close to stock as possible.

      C:Program Files (x86)Androidandroid-sdkplatform-tools>fastboot boot recovery-clockwork- ‘boot.img’…OKAY [  0.507s]booting…OKAY [  0.326s]finished. total time: 0.834s

      • Paul Harper

        Never thought about that but yeah that should work just as well. CWM just makes it a bit easier is all.

      • It doesn’t actually matter if you flash CWM or not. As soon as you boot AndroidOS, the stock recovery will be reflashed unless you remove recovery-from-boot.p

  • Gnexus

    DOES THIS WIPE DEVICE??? Should i worry about creating a TiBu??

    • Paul Harper

      Its does not require full wipe and does not wipe the device, however dalvik cache should be cleared.

  • anyone else get an error in CWM when trying to install the update? Mine says something about systemUI.apk then aborts.. weird. Im stock 4.0.2 but rooted/unlocked.hmm

    •  sooo.. i cant install this for some reason when it is verifying current system it says assert failed: apply_patch_check (“/system/app/SystemUI.apk then a lot of numbers and letters and then E: Error in /sdcard/ROMS/update.zip (Status 7) Installation aborted. .. any thoughts? never had this or any problems before

      •  arrrrggg what the hell.. someone help please.. all i get is an installation aborted when i do this… its freaking bothering me i cant figure this out at all.

        • Paul Harper

          Are you unlocked and rooted and running stock 4.02 and using CWM recovery?

          •  yes unlocked, rooted, and just flashed the updated CWM … i havent messed with anything else.. just running NOVA Launcher .. it keeps giving me the same error about the systemUI .. im pretty well versed in flashing and rooting android.. this just has my mind boggled though. really pissing me off now.

          • Paul Harper

            I downloaded the file on my pc and placed it to the phone then went to CWM and said install from SD card had it wipe dalivk cache and create a recovery it then rebooted did both and was working fine all but root. I had to follow the steps to re root and all is working fine here.

          • And re-delete recovery-from-boot.p, so that you keep CWM!

          • [[[…babysmoker…]]]

            Did you flash the Nova .zip in recovery as a system file? If so that’s most likely the issue & you’ll have to uninstall it first. I’ve been debating flashing this & that was one of the big concerns floating around in my mind.

          •  that actually may be the problem.. didnt even think of that… smart thinking! forgot it wasnt just a regular app. .. i got around the problem but you may just be right. thanks!!

          • Coldness

            Yep, that was my problem as well. I ended up just re-flashing a stock system 4.0.2 over the top of it to clear up anything else my root apps have done and then flashing 4.0.4. Same error you were getting. It was pretty maddening for a few minutes though. 

          • Paul Harper

            i use adwlauncherex it works pretty well an doesnt require changing system files not sure what Nova is all about.

          • Anonymous

            Nova Launcher ( http://goo.gl/GrPAo ) is a Serious Polished ICS Launcher, the Best for ICS thus far.

          • I have NovaLauncher in system

            Not only did the update work fine – it didn’t even get rid of Nova!

          • [[[…babysmoker…]]]

            Edit: As Jeff stated, Nova is not the culprit. Just flashed the update without so much as a hiccup.

            Re-flashed the 4.0.2 radios (I was on 4.0.3), was otherwise already stock rooted so I just renamed the update .zip “update” & copied it to the root of my SD, flashed stock recovery, installed the .zip & it did it’s freaky, sexy Android thang.

            Upon rebooting I got the “Android Updating” screen (which told me it was “optimizing” a substantial number of my apps) which then it brought me to my beautiful homescreen. The only thing that I lost was root – Nova remained happily intact, invisible folder mod & all – so I flashed CWM recovery, re-installed SU & got my root back on. The whole process (nandroid back-up excluded) took no more than 10 minutes.

            New sh*t, as others have noted:
            Better signal & much faster hand-offs
            Portrait to landscape is sped up
            Browser now has much more intuitive quick controls
            New power-off screen
            “Dock” settings now added to the settings menu (unless that was there before & I simply didn’t notice)… functional docking station headed to a retailer near you in the near future?
            Things are generally snappier

            &…… not a single frackin bug as far as I can tell, but then again I never had any issues with this sexy beast to begin with 😉

          •  eh forget this method.. i just used P3Droid’s stock ROM from the TBH App and that worked fine.

          • Im getting this error cause i modified my softkeys. Still aearching for a fix.

  • Cchandler66

    I am having trouble with this. I boot into recovery mode using the volume and power keys. then i get the dead android with an explanation point. from there I can get the settings menu to come up, but there is no option for instal zip from sdcard. instead mine says instal from /cache. any idea on what I am doing wrong? running complete stock

    • Anonymous


      Try using ClockworkMod recovery. Not the stock one

      • Cchandler66

        still having trouble with this. I tried this method also and still got an error it said. I am locked and not rooted. I use to do this on the OG droid but am having problems with this now. any other ideas?

        • ramifications

           You need to first unlock your phone. It comes locked from the factory. Check out xda-developers (forum on the CDMA galaxy nexus development) for instructions.

        • Cpomike13

          I am unlocked and rooted, and I’m also having trouble flashing this also. I have tried many times

    • Anonymous

       Download Rom Manager from the Market and flash ClockworkMod (at the top of the list when you open Rom Manager).  Then you should have the ability to flash the update.

  • how do you get clockwork recovery when you are stock?

  • 103 down to 93

  • love the better signal got a huge boost down to 73dBm

  • Boston

    Does this break root? Also, does it require a data wipe?

    • It undoes root, but you can just redo it the same way. No data wipe required.

  • Anonymous

    The “rename to update.zip” part of step 2 is unnecessary if you’re pointing CWM to the zip you’re installing. I think at least, correct me if I’m wrong.

  • I’m pretty sure this works: if the file is named update.zip, you can turn your phone off, hold Power and Volume Up to boot into the stock recovery, and then flash it from there. Feel free to check this.

    • Anonymous

      this is for stock people right? unrooted etc

    • Dennard70


  • I’m on 4.0.2 with updated radios. How do i go about getting this update without losing all my stuffs?

  • Glitchy

    Listen, I care about one thing only. Does this fix the dang glitches with hi bit rate streaming music and long podcasts?  I am ready to bite the bullet and buy a Rezound on Ebay rather than put up with the dang stuttering and glitching in my music streams whenever the screen goes dark!   My Gnex burps on streams that my OG Droid has no problem with!   Grrrr!

    • never heard this problem i listen to podcasts all day with zero problem…

    • Marvin de Pano

       Mine doesn’t only do that on streaming, even music stored on the flash partition is stuttering for me, regardless of what app I use (Winamp, Google Music, etc.) My OG didn’t do this either, and it’s supposed to be waaaaayyyy slower than the GNex. Ya, it’s annoying for a frigging flagship device and OS.

      • none

        didnt you get the memo its not a flagship phone anymore

        • Marvin de Pano

           At the time it came out it was. Were you hiding under a rock?

    • Charles Daly

      I was having those issues with Google Music until I unchecked “Cache music” in the “Music settings”. Since I did that it’s been smooth sailing.

  • Anonymous

    youtube videos now actually play in hd!

  • Just did update thru CWM and I have OTA Rootkeeper.  Update worked but lost root.

    • Gnexus

      are you able to re-root with the same su.zip?

      • Paul Harper


        • Just did re-root and seems to have worked, OTA Rootkeepr and CWM work fine..although Titanium Backup seems to believe there is no root..so go figure.

          • Huh?

            OTA Rootkeeper was supposed to keep root, and you lost root. So OTA Rootkeeper DOESN’T work fine…at all!

          • You are correct…I was not even close on this one.

          • Nick

            Well, this isn’t an OTA update. We’d best wait and see whether the final update pushed out breaks root or not.

  • SuperMario

    Don’t mean to troll but droid-life is the last website to report the story.. kind of disappointing as droid-life is usually my primary source for Verizon/Droid related news.

    • Magnious

      Droid Life doesnt really report much news on the weekends. That would be why.

    • I’m guessing Droid Life tested the update for a little bit before reporting… maybe. But yes, I had already flashed it by the time this article came out.

    • they don’t report much on weekends….

    • tlspatt

      yeah, probably because Kellen tries to have a life on the weekends. besides, we’ve had gorgeous weather up here in the PacNW yesterday–between 55 and 65 in Seattle. I’d be out doing other things too. If you lived without the update for this long then an extra couple hours won’t matter much…

      • I both agree and disagree with you. We had a couple of 60 degree days this January (in Ohio of all places), and I sure as hell did not want to do anything on those days except go outside and have fun. But, if one of the servers at my work crashed, and I said “too bad, it’s 60 outside”, I would have quickly found my way out of a job — and in fact, this happened on one of those days and I had to spend 5 hours in a windowless basement. Kellen depends on this blog and it’s readers, so when something big happens, he should be on it regardless of his whimsy.

        • Anonymous

          What an idiot. Your servers crashing is not the same as putting up an article.  Your boss should tell you that you have to come in on Sat and Sundays and work. I don’t think you will do it for long.

          • Wait, how does Kellen pay his bills again? Oh, that’s right; HE HAS A BLOG. Explain to me the difference again. And you really must not have a job if you think people don’t work Saturdays and Sundays.  That’s just how exploitation… I mean employment works these days.

          • Calm down everyone. Let’s start the week off being happy. 🙂

            It’s true, we disappear on weekends as most people should. With that said, we were the 2nd site to report it and we actually gave you full instructions on how to install it, something no other site did.

          • That’s fair enough. And don’t get me wrong, we support you nonetheless. I had gotten the update in am email that morning, so for me, if would have been old news regardless of who reported it. I was just pointing out the fallacy of a “good weather” argument for anyone with a service job, even less for someone in a service career.

  • Does this do ANYTHING to the damn landscape/portrait transitions?

    • Paul Harper

      Seems that it improved the responsiveness of the transitions

    • Higbiz

      The transition delay is built in to android. Some custom ROMs (AOKP, for one) let you drop the delay down to only 10ms (from 200ms) which speeds them up quite a bit.

      • Anonymous

        I like the longer delay, it unwanted rotation drives me nuts.

  • Anonymous

    YES, finally!

  • Aarhed263

    anybody know if battery life is improved with this??

    • There’s no way to tell yet. It just broke a couple hours ago.

  • Anonymous

    Does this fix the auto brightness?

  • Kaoiv

    What about the multi-touch issue?

    • Anonymous

      I’ve never had any multi-touch issues with mine, but its probably hardware related

    • Multitouch Issue is fixed, according to some of the posts in the XDA unofficial changelog thread. There are some screenshots posted from a multitouch test app showing all 4 corners being activated.

  • Anonymous

    Dang, just rooted yesterday… yeah, anyone know if you need to unroot to do this?

    • Gnexus

      same boat as you, i just rooted last night (or you could say very early this morning). I should work with root but the question is whether it maintains root. Will anyone please let us know if this breaks root and if so if OTA Rootkeeper will work with this?????

      • Paul Harper

        Root is not affected at all in doing this update

        • Gnexus

          Thanks Paul!! is this a personal account? also did you flash through COW? and lastly do you know if wireless tether stil works with this update?

          • Paul Harper

            I stand corrected it seems I dont have root access upon trying wifi tether
            Edit Reply

          • Paul Harper

            What method of root did you do permanent or the temp method? I had the temp method so it does not surprise me that I had to redo it. Took less than 5 mins to reroot no big deal.

          • Paul Harper

            Wifi tether is working perfectly and yes I am using CWM. Just reroot after install using sdk tools and reflash the recovery and su and you will be all set.

          • Gnexus

            i rooted with adb, and used root explorer to rename my /system recovery from boot file. Therefore im guessing i could just remove the extension to reboot with stock recovery to flash CWM and apply update? did the same su.zip file root the 4.0.4?

          • Paul Harper

            you possibly may not need to remove just install and see if your root sticks. and yes I used the same su.zip

          •  it’s CWM not COW,
            COW say MOOOOO but CWM make you say WOOOOO because it’s AWESOMEEEEE.

      • It’s very easy to unroot.Why dont you make a nandroid and a titanium backup and unroot it?

        • Paul Harper

          I lost no apps or data just root always a good idea to back up but really not necessary.

      • Paul Harper

        Using the temp root method I had to reroot after installing the update. No biggie just rerooted using sdk tools and reflashed recovery and su took a whole 5 mins and was honostly good practice lol

  • Christopher Riner

    Do you have to unroot?  Or will you lose root?

    • no need to unroot – but you will lose it and have to redo it. you will also probably need to reflash cwm

    • Anonymous

      no you need root in order to have clockwork recovery

  • Gnexus

    Can anyone confirm if this breaks Root? Will my OTA Rootkeeper app maintain the root with this update?

    • Yes it will “break” root.
      But you can just re-root without any problems.

      From the sounds of it, OTA Rootkeeper doesn’t work at all.

  • Garett

    Does anyone know if this fixes the wifi/infinite boot glitch? Haven’t been able to use wifi for a month now and it would be nice if I could.

  • Jslafarr

    rom devs will prob have their next batch on 4.0.4 – as that is how the game has gone since the OG droid.
    “id like to see google push official updates to the phone” LOL – as these clueless people are saying with rooted / roms gnex’s that BLOCK ota’s. who gives a sh*t. cant get the update anyway and even if you did youd have to re root all over again.
    pointless complaining that makes me waste time complaining myslef

  • Anonymous

    Yeah, I’m just gonna wait until this goes into AOSP, or an official ota is sent out by Google. 4.0.3 works fine for me anyway on GummyNex so it’s not a huge deal.

  • vtcapsfan

    Can you flash this if youre unlocked bootloader/root but on stock 4.0.2

    • reversal

      I’m in the same boat, can someone answer this, and will you lose root?

      • Ahmed Said

        Yes I cant seem to root on 4.0.4 but on 4.0.2 it works fine.. SU can’t access root for some reason on 4.0.4

        • You lose root when you install the update, but putting su and Superuser.apk back on works the same as it did in 4.0.2.


      Yes as long as your on the stock recovery

      • vtcapsfan

        what if im on CWM

        • NEXUSSSSSS

          No must be stock recovery, otherwise you’ll have to wait for a ROM update

          • vtcapsfan

            The instructions above are for CWM..

          • NEXUSSSSSS

            Oh good look, flash away

        • Anonymous

          You can flash just the bootloader and radios if want on custom recovery.  You have to be on 4.0.2 bootloader and radios before upgrading though.

          If you are already on 4.0.3 you simply flash the stock bootloader and radios from your custom recovery and boot back up. Then go back into recovery and flash the upgrade.  I just did this myself and it works great, and only takes a few minutes.


          If you need the stock bootloader and radios just go to the second page in this thread above and download. Very simple

          • tlspatt

            thanks, now THAT was the answer I’ve been looking for–thanks Kleen and Timoh. no sense messing with an otherwise perfectly good ROM until we know the details of the update. only glitch I’ve noticed on AOKP or CND is that my panoramic mode on my camera sucks since flashing a 4.0.3 custom ROM. wonder if they did anything about the camera on this update? any dev’s dig through the contents of this update yet?  

  • Christopher Riner

    so FA02 and V.FA02 are the new radios? not ek04 and ek06?

  • Marvin de Pano

    Hoping Franco’s kernel gets updated to this soon too. Would like to couple that with stock 4.0.4.

  • NexusBRO

    My vagina hurts….stop your bitching.

  • ddevito

    I’ll wait for an updated Bugless Beast

  • Anonymous

    Since most are already on 4.0.3 roms it would be easier to wait until the roms update to this which will only take a few days rather than going back to stock for this.

    • A lot of 4.0.3 roms actually run the 4.0.2 radios. The link I put up also has a link to a zip to revert your radios and bootloader back to 4.0.2. Then you can flash the 4.0.2 to 4.0.4 radio zip.

      • Anonymous

        Yes this is what I ended up doing. It only took a few minutes…. Thanks.

  • Benjamin Landwehr

    Hopefully a ROM will have this soon, don’t want to redo everything yet again. Hope it fixes multi touch. Kind of sad how this is leaked before the real 4.0.3 update came.

    • They just skipped 4.0.3. no G-Nex got it

      • Gerrysafford86

        4.0.3 was designed for the nexus s…

  • The radios are updates, so it’s stronger signal, but can anyone who installs this tell if theres any sign of an update for the speaker? it needs to be louder

  • I’ll wait for it to hit the new build of AOKP.

    • Boblevel

      And then a day later on CodeName..lol..

      • Thus why I’m running AOKP and not Codename!

        • Anonymous

          I feel like I’m missing something here.. is codename kanging AOKP?

          • Ish…just replied above with my understanding of the whole thing. I meant it as much jokingly as serious, I guess, I don’t get worked up about it or anything, but I do prefer to support the devs actually doing the work.

        • Anonymous

          What’s wrong with Codename versus AOKP? I run Codename 1.2 and I think it’s pretty good, is there any reason I should switch? Haven’t been following the development of different roms that closely and genuinely curious.

          • Nothing wrong with it, I mean the dev does give credit for everything he put in, but the sour note seems to come from the idea that he didn’t put anything original in at all, just a “remix” of AOKP and some other things without any code or work of his own.

          • I just tried them both back to back this week… I started on codename 1.1.4 then went to 1.2.0.. then tried aokp milestone 3 for a bit, got curious and went back to codename to see what 1.3.0 was all about. codename seems to run ever so slightly faster, but AOKP has more polish as far as the mods and cusomization goes. I ended up back on AOKP.

  • looking forward to the OTA update for this.



    • Anonymous

      Reboots? more like complete damn shutdowns…. very much looking forward to a fix.

      • Anonymous

        Yeah, same here about the mysterious random freezes/reboots. In the first two or so months since I’ve had my Nexus, nothing like that ever happened, but then a few weeks ago, when my phone was idle for longer than an hour, then I attempt to use the phone, it hung up, froze, then automatically rebooted.

        Hopefully this new Android update fixes these and other issues.

      • Anonymous

        Are you guys with these issues on stock or running roms?  Only reason I ask is I am running roms and have never had a reboot or shutdown. But I have read of those on stock that have had some reboots.

        P.S. this new set of radios do seem to be an improvement so far.

        If you are having some problems on stock, why not upgrade?

        • Anonymous

          Imm still stock/ Not Rooted. I just dont really feeling like doing the custom Rom dance just yet. Reason I got the Nexus was so that I didnt have to root to get updates quickly.

          • angermeans

            Hmm I got the Nexus so I could experience the excellent developer community and the great things that are sure to happen for the platform. The Nexus One still has a great life because of devs and there is no phone out there that is as popular in the community. The idea of a Nexus sure has changed in the past couple years. Then again I can understand your feeling as ICS does look and run great. I’m sure you will get there, but I can see your logic as if I was someone that didnt want to have to root (or have the time as I am noticing I rarely have the time with college classes and full time work) the promise of updates from Google would be a huge selling point. I can’t imagine owning this phone and not rooting it and running custom roms. I’ve been waiting years since getting my original Nexus One and being on Verizon (I refuse to leave as the network is light years ahead of the competition). To me the idea of a Nexus means rooting and roms and I couldn’t imagine not using it for that. 

          • Anonymous

            Thats the difference ivee seen. Folks have been screaming in the past for manufacturers tto just give us stock android. Especially because of the updates from google. The they get a stock device and root it and run custom roms on anyway. You can root and run custom roms on 99% of android phones. If I was just interested in Roms I would have just gotten the GS2. Sure its easier to ropt and Rom a Nexus… but its not much harder on most other phomes.

        • I’ve been running custom roms and still get the random shutdowns

          • babadush

            Are you using nova launcher? I noticed that hangs every now and then. Then reboots

        • Whenever I read about the reboot/shutdown issue, they’re always on 4.0.1.  Not saying it doesn’t happen with 4.0.2, but I’ve never seen one reboot/shutdown I didn’t request.

        • Rsmith Nikon

          I am unlocked and rooted… no custom rom. Today i was sitting at my kitchen table working on my computer when i noticed my phone rebooting next to me. I mentioned it to my wife and she said that her phone… stock… does the same thing. First time i evrr noticed it.

        • Totally retail stock, never had one single problem.  waiting for more awesome before I bother rooting.

    • John

      no issues here. has been solid

  • Anonymous

    where’s the google.com download link?

    • Anonymous

      it’s a leak… not an official release

  • Anonymous

    So much for getting direct updates from Google on the Galaxy Nexus. First no update to 4.0.3 and now a new update with no signs of an OTA push, still.

    • Madcow06

      Chill, there’s not going to be an update every month.

    • if you’re serious, then Stop posting. We do get direct updates from Google. This was a developer only release. they pulled the package and posted it online. 4.0.3 didn’t go to any galaxy nexus’. This might have a few bugs, which is why it hasn’t been pushed out yet

      • Anonymous

        Let’s see here Alex – there have been two separate OS updates to Android now since the Galaxy Nexus was released, including one that updated the base OS version (to 4.0.3), and yet there have been zero OTA pushes to the device.  Combine this with the recently released information about the CDMA devices basically being pulled from Google’s list of “officially supported devices”, and I say they are falling down on their promise with this phone.

        It’s easy to say “We do get direct updates from Google”, but until it actually happens, ever, then my comment stands.  I am very fond of my Galaxy Nexus, and actually have not had any real problems with it, but things definitely smell fishy coming from the direction of Google.

        • Madcow06

          Actually there was one, update pushed when you activated the phone.

        • 4.0.2 was pushed to the phone, it was done on launch day. 4.0.3 didn’t really go on any phones. They started to push it to the Nexus S but then halted deployment after bugs were found.

        • Nick

          You do realize that 4.0.3 was only for the nexus s. Unlocked gnex is still on 4.0.2

        • Tim242

          There was an OTA on day of release. It released with 4.0.1, updated to 4.0.2 15 minutes after activating. Be patient, damn!

        • vvvvvvvv ziiiiing. Dude, no one got the 4.0.3 update! they’re skipping and going to 4.0.4. We got 4.0.2 on the day we activated the phone, and the GSM version got that update after us.

    • Anonymous

      I also would like to see an official update of some sort. However the updates always leak out early for those that want to upgrade ahead of time. And this is the way I always want to keep it. 

      For instance most of us with the Thunderbolt were running Gingerbread months before the official ota. 

      But I would like to start seeing official updates.

  • xxdesmus

    so I assume this will screw with my root and unlock?

    • Nope, it’s all good.

      It will undo root, but you can just redo it easily enough. (just copy su and Superuser.apk back in).

      Unlock stays unlocked

  • Gerrysafford86

    your welcome kellex!!!! ;P

  • Marvin de Pano

    I’m sure someone (Peter Alfonso) will put out a stock rooted rom out there. #patienceisavirtue

    • Boblevel

      Yep, on Twitter he said it will be included in the next version soon..

      • Marvin de Pano

         Cool! I knew it.

  • Is the signal strength any different or does it just fake a stronger signal with more bars?

    • I had someone else post some screen shots for me and the signal to bar representation looks the same as always.

      I also just flashed them and I went from 113dBm to 93dBm. It appears that this does increase reception.

      I flashed only the bootloader and radios. Still running AOKP milestone 3.


      Do NOT flash this over anything but the 4.0.2 radios and bootloader. It patches the LTE radio and replaces the CDMA.

      • this was the news I was hoping to hear. I’ve been sitting tight on my Nexus waiting to really do anything with it but the signal improvement may be worth it. Besides stock ICS is beautiful so who can really complain?

        • huzzah! it definitely seems to boost reception. 

      • My 4G went from -90 dBm (3 bars) to -95 dBm (4 bars), so there’s that.

        • Maybe they changed it with the whole ROM/update. I only flashed the radio and had -93dBm with 2 bars.

        • Anonymous

          Thats strange since -95 is worse than -90

      • TLW

        I flashed it over the 4.0.3 radios/bootloader just fine.  

        • A lot of 4.0.3 ROMs actually run the 4.0.2 radios. Most ROMs don’t flash the radio.

          If you had EK05 EK02 then you already had the 4.0.2 radios.

          If you were running 4.0.3 radios(EK06/EK04) it will only change the botloader and the CDMA radio.

          It does it this way: Bootloader:replace, LTE:patch, CMDA:replace. Check your radios in the system info(baseband version), they should both end in FA02.

          If they don’t you should flash the 4.0.2 zip found on the second page of the thread that I linked, then flash the 4.0.4 upgrade.

          • Anonymous

            Good info to have, thanks!

    • Anonymous

      The browser quick controls have gained many new functions…there’s something new!

      • I don’t see anything new under the browser’s quick controls?

        • Anonymous

          They now include a Bookmarks button and Add a Tab. If you are using Browser+ you already had these but stock didn’t.

          • I bet that was already added in 4.0.3 because I’ve had both of those options in the stock browser.  I’ve been using 4.03 based ROMs for a while and must have forgotten that those options weren’t included in 4.0.2.

        • Anonymous

          There are more options now

    • My reception in my apartment was horrible I was lucky to get 1 bar of 4G (and i’m in the NYC market) but after this update I’ve been seeing 2 or 3 bars pretty consistently. +1 for this.

       I was actually at -140dBm before I did this (which was abnormally low I’m usually around 120) and afterwards it’s jumping from about 93 to 103 dBm

      edit – I tried changing my soft keys back to how they were with 4.0.2 where I had the roboto text….well that doesn’t appear to work right now as I got a systemui force close.

      Also it seems I have to keep flashing clockwork in order to get into it’s recovery mode. I’m sure this could be fixed by the permanent method but I haven’t tried it yet. Anyone else have this issue?

      • Softkeys can be rewritten, still. I used Zipthemer, updated Edify (giving it this update file as a source).

        SystemUI changes with Android version, so if you’re just using CWM to flash a zip file to change the softkeys, you’ll need to re-generate that zip file to use the new version of SystemUI.

        Android will keep re-flashing the stock recovery on every boot unless you remove /system/recovery-from-boot.p (the update restores this file)

        • oooh i hadn’t thought of giving it this update as a source. Good call!

  • Qbanito1967

    Great news

  • If the battery bar designation is the only thing they changed, then I almost see no point in moving up from 4.0.3

    • Anonymous

      I mean there is no change log yet… Kellex is just assuming. We’ll see soon enough I guess

      • There’s an unofficial changelog on XDA. It’s just full of changes known to be in the source code and observed by people testing it

  • All I want is for this to fix the multitouch.

    • Mike Wadsten

      I’ve read that it does fix the multitouch.

    • Anonymous

      what issue have you had with Multi-touch?

  • Anonymous

    Any guides to flash this on stock recovery?

    • Madcow06

      This is also what I want to know, can I rename it update.zip and use the stock recovery to flash?

      • No, do not do this. It’s not the same as a normal system update, it’s just a bunch of patches.

        • Madcow06

          Damn, I figured as much.

          • Someone will come up with a different method soon I’m sure.

    • 1). Install CWM
      2). Make a Backup
      3). Install this update
      4). Boot it back up

      When you boot it back up, it will put the stock recovery back in automatically.

      Maybe somebody can shed some light on this: Why are people willing to install updates without the safety net of a backup, but they aren’t willing to install a tried-and-true, trusted recovery image? Flashing clockworkmod recovery is COMPLETELY reversible!