yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] neilalexander:
Vodafone UK 'jakyu' Galaxy Nexus, 4.0.2, no update notification so far.
[Samsung Galaxy Nexus] jendrassik:
Wind ITA - Yakju No 4.0.4 OTA . Still on (laggy) 4.0.2
[Samsung Galaxy Nexus] skychan:
In Hong Kong on Smartone / yakju 4.0.2 - nothing yet ...
[Samsung Galaxy Nexus] ChrisAG:
No 4.04 OTA for anyone anywhere.
[Samsung Galaxy Nexus] rootusr:
Mexico Stock YAKJU.. nothing yet
[Samsung Galaxy Nexus] Orion4048:
Mine is yakjuxw and it says ICL53F, too. I've checked it with several apps.
[Samsung Galaxy Nexus] efrant:
So when you go into Settings->About phone->Build number, it says ICL53F (i.e, nothing else attached to the "ICL53F"), and not something like ICL53F.I9250XXKL1 or something like that?

If you are on yakju, the build number will only show something like ICL53F.

If you are not on yakju, the build number will show something like ICL53F.I9250XXKL1.
[Samsung Galaxy Nexus] ray3andrei:
In the settings it says ICL53F

Sent from my Gnex :)
[Samsung Galaxy Nexus] efrant:
Based on your screenshot, your device should say ICL53F.I9250XWKL2 in settings, which is your build number.

Does your About phone screen look like this?

http://xdaforums.com/showpost.php?p=22051561&postcount=45

That's what it should look like if you are on yakjuxw...
[Samsung Galaxy Nexus] ray3andrei:
The image doesn't load :(

Sent from my Gnex :)
[Samsung Galaxy Nexus] efrant:
Fixed it! :)
[Samsung Galaxy Nexus] ScarabJsy:
Update info

In Tenerife on Movistar, deleted google framework cache and restarted which prompted me to update

4.0.4

I9250XXLA2

3.0.8-g034fec9

android-build@vpbs1 #1

SMP PREEMPT Tue Mar 13 15:46:20 PDT 2012

IMM76D

Looks legit, nice and slick now too
[Samsung Galaxy Nexus] ray3andrei:
Yup it looks like that thanx :P

Sent from my Samsung GNexus <3
[Samsung Galaxy Nexus] efrant:
All non-yakju builds will have something after the ICL53F (or IMM76D or ITL41D/F), starting with .I9250. That is how you can quickly tell if you are running yakju or not.

If you are running a non-yakju build, in your build number, you will see

BBBBBB.I9250RRDDD

Where:

BBBBBB is the build number (to-date it can be: IMM76D, IMM48, ICL53F, ITL41F, ITL41D)

RR is the region (can be UX, XW, DV, KR, SC, ZS and there maybe one or two I'm missing)

DDD is the last three digits of the radio version.

If you are running a yakju build, in your build number, all you will see is

BBBBBB

Where:

BBBBBB is the build number (to-date it can be: IMM76D, ICL53F, ITL41F, ITL41D)
[Samsung Galaxy Nexus] pacosanchezsantana:
I'm still on 4.0.1 and have been trying the frameworks trick for 2 days. Has anyone been updated from 4.0.1 to 4.0.4 ?

Yakjuux in Canada!
[Samsung Galaxy Nexus] efrant:
This guy: http://xdaforums.com/showthread.php?p=24282012
[Samsung Galaxy Nexus] 1simonlo1:
I'm in the UK on 4.0.2 stock yakju.. and to date STILL don't have the update!

Is there anyone else out there that doesn't have the update?

Bought SIM free from Amazon.co.uk
[Samsung Galaxy Nexus] ray3andrei:
I'm just bumping this post

Sent from my Samsung GNexus <3
[Samsung Galaxy Nexus] zolah:
I wasnt getting the update either mate when everyone else was.

Just clear the google service framework data and check again and you will get it.

I got it 1st time with the wifi turned on.
[Samsung Galaxy Nexus] Reeebo:
still haven't gotten it... on 4.0.2 yakjuzs
[Samsung Galaxy Nexus] galaxy3-i5800:
same here, in finland. im on yakjuxw and nothing.
[Samsung Galaxy Nexus] dendirk:
Belgium here still no update on yakjuxw

---

I am here: http://tapatalk.com/map.php?tepjnh
[Samsung Galaxy Nexus] vesu:
changed from yakjuxw to yakju and still nothing after hammering google framework thing +20 times. Finland
[Samsung Galaxy Nexus] Mojochief:
Same for me here in Austria :(

Even tried with US proxy...
[Samsung Galaxy Nexus] axellink:
Got my galaxy nexus unlocked yesterday to t-mobile. haven't received the update even though I got it for my nexus s last week. UK user here
[Samsung Galaxy Nexus] sidhaarthm:
Any one else in the same boat as me?

I own an Unlocked (SIM Free) GN running on Three network UK. I am running a stock build of 4.0.2 with root and an unlocked bootloader. I can confirm that my device is a proper 'yakju' build.

Can someone please confirm if the OTA is Carrier based because I read on this forum that several UK GN owners on Three network have received the 4.0.4 OTA update?

I have tried the 'clear Google Services Framework data' method in a number of different ways including changing SIM Cards, several reboots (with/without SIM Card) and continuous 'clear data/check for update' cycle. All to no avail.

I guess I am amongst the ones who are still waiting for 4.0.4 OTA rather eagerly in the UK.
[Samsung Galaxy Nexus] omrij:
I think they pulled the update for now

maybe because of the radio issue
[Samsung Galaxy Nexus] sidhaarthm:
I believe you may be right. A lot of pissed off customers here with the disappearing radio issue in standby mode for the GSM GN running on 4.0.4:

http://code.google.com/p/android/issues/detail?id=28133

Oh well, that gives me some time off from the 'clear data/check now' cycle.
[Samsung Galaxy Nexus] juniorbattle:
I can confirm OTA 4.0.4 for Three, UK. Sadly, people here may be right and OTA may be stopped for now because of that radio issue. I haven't had any problems with this OTA. Good luck
[Samsung Galaxy Nexus] E15i:
I cross fingers , hope to hear a good news, it always stops me of buying GNEX because of that bugs, you always can revert to 4.0.2 or 4.0.1, but it's annoying because if you need do downgrade, you always need to backup apps and so on :mad:
[Samsung Galaxy Nexus] SKYLINESSUCK:
Crap. I finally got fed up and installed a new 4.0.4 image this afternoon. None of the issue mentioned yet though.
[Samsung Galaxy Nexus] shimsim:
In China, GN purchased from HK unlocked and converted to YAKJU.

Still on 4.02, tried VPN, tried UK (t-mobile) SIM.

Been trying the framework trick for a few days, no luck, no maybe the update has been suspended for now.
[Samsung Galaxy Nexus] E15i:
you can know it there some change of you check MD5 and SHA-1

from time to time

http://code.google.com/android/nexus/images.html#yakjuimm76d

anyway many users do have problems according to news,

you can cheer up at least, that 4.0.4 work with the Car/Desktop dock that Samsung keep postpone due to software problems.
[Samsung Galaxy Nexus] orphamiel:
No update =(

Still no update here in Singapore :(
[Samsung Galaxy Nexus] The Apostle:
4.0.2 in USA on Verizon and no updates yet. I tried the Google framework "trick" to no avail.

Sent from the Galaxy via XDA Premium
[Samsung Galaxy Nexus] big_mike_aka_mike:
not here,

uk

orange unlocked

4.0.1
[Samsung Galaxy Nexus] tokyojay70:
Hi

UK

Galaxy Nexus on 4.0.2

Three Network

I received the 4.0.2 update without any problems months ago but I still have not received the 4.0.4 update and yet a friend of mine who is also on Three received his 4.0.4 Nexus update about 10 days ago. So I cannot understand why he has received his update and I have not as we are on the same network. I have also tried the google framework reset/update check but it makes no difference.

I am not sure what criteria Google uses to decide when and who gets the updates.

TJ.
[Samsung Galaxy Nexus] aindow:
I'm on Three UK, got my Galaxy Nexus from them about 4 days after release. I'm on 4.04 and got it by clearing the Google framework cache. It all seems fine to me.

Rik.

Sent from a Galaxy Nexus in a ZT, far, far away.
[Samsung Galaxy Nexus] stockerx10a:
yeah I am also on a stock unlocked gnex, 4.0.2. no update yet. but other than occasional reboot and somewhat weak radio, the phone runs flawlessly. so I an not concerned when it shows up.
[Samsung Galaxy Nexus] kupuguy:
I'm on stock 4.0.2, virgin mobile UK, and despite clearing the framework data several times no sign of an update.

My phone has an uptime of 2082 hours so I wonder whether rebooting might help it find the update but on the other hand I kind of like having a phone that hasn't rebooted for nearly 3 months. I think I'll wait at least another 4 days before trying anything else.
[Samsung Galaxy Nexus] jstierman:
Still nothing, 4.0.2 on unlocked UK (flashed to yakju). T Mo in US
[Samsung Galaxy Nexus] gunner1937:
As I mentioned in another post, when I received my GN last Friday I had no time to finish my settings and call AT&T for a data plan that I got an update notification. It turned out that it was the upgrade to 4.0.4.:)
[Samsung Galaxy Nexus] TheCarl:
Nothing for me.

Telenor in Norway.
[Samsung Galaxy Nexus] Pentium:
me too still waiting, I'm on 4.0.2
[Samsung Galaxy Nexus] G2_Gordon_G1:
Hi all,

I am running 4.0.2 Yakju but have since flashed the UGLA4 radio.

If I want 4.0.4 to land OTA, which radio do I need to flash now, and does it need to be from an official source?
[Samsung Galaxy Nexus] athome93:
I'm on stock 4.0.2 Yakju, FreeMobile FR, and despite clearing the framework data several times no sign of an update.
[Samsung Galaxy Nexus] Absolut3k:
I'm on stock 4.0.2 Yakju, Vodafone IT, and despite clearing the framework data several times no sign of an update.
[Samsung Galaxy Nexus] android.slovenia:
I'm on stock 4.0.2 Yakju, Mobitel SI. No no spirit of update.
[Samsung Galaxy Nexus] Duncs:
I'm on stock 4.0.2 Yakju, Vodafone UK, and despite clearing the framework data several times no sign of an update.
[Samsung Galaxy Nexus] onthecouchagain:
Maybe they paused it again? To address that nasty Tmobile signal dropping issue?

: shrug :
[Samsung Galaxy Nexus] sidhaarthm:
I don't believe the signal drop issue is on T-Mobile alone. It can occur on any network.

I am also waiting for my share of some fresh 4.0.4 Ice Cream. Running stock yakju (XXKK6) 4.0.2 on a rooted GN with an unlocked Bootloader on Three UK. I am tired of clearing Google Framework cache and hitting the 'Check Now' button. I must've done it over 40-50 times already. :(
[Samsung Galaxy Nexus] dendirk:
Google MUST send out better information on this matter.

Some devices have 4.02 some devices are on 4.04 some are yakju some are yakjuxw...etc

I bought a Galaxy Nexus only for the reason to get all the updates as soon it comes out. I didn't asked for so many differant versions.
[Samsung Galaxy Nexus] efrant:
I don't understand why people here don't just apply the OTA update manually? It does the same thing as having it install OTA.

http://xdaforums.com/showpost.php?p=20843237&postcount=1
[Samsung Galaxy Nexus] heartblasts:
On stock 4.0.2 yakju no notification yet
[Samsung Galaxy Nexus] dendirk:
Because i have a Yakjuxw
[Samsung Galaxy Nexus] sidhaarthm:
For few reasons:

1. I do not want to install any Third Party Recoveries, i.e. CWM etc.

2. I do not want to lose all my data, apps and texts etc - because manually flashing means wiping the device.

I have been a Nexus One owner in past where I experimented with several different ROMs, Recoveries etc whilst finally settling with CM7; but the Galaxy Nexus is just too gorgeous to be mucking around. I want it to remain as stock as possible - that is why I run the stock ROM with just a Root and unlocked Bootloader.

If you have an alternative method where I can circumvent the above mentioned inconveniences, then I'd be grateful :)
[Samsung Galaxy Nexus] efrant:
That is a good reason! :) I was actually directing my question towards the ones running a yakju build.
[Samsung Galaxy Nexus] dendirk:
im with you!
[Samsung Galaxy Nexus] efrant:
1) You do NOT have to install any third-party recoveries to manually update.

2) Updating manually will NOT wipe anything.

3) Read the link I posted above, or look in my signature for instructions.
[Samsung Galaxy Nexus] sidhaarthm:
Thanks very much for pointing out. I am more than willing to give it a try, but I still can't seem to understand which of your methods would apply in my case? Also, I see that you do need CWM installed in almost all cases.

I am running stock yakju (4.0.2) with root and an unlocked bootloader.
[Samsung Galaxy Nexus] dendirk:
Are those instructions also for a Yakjuxw version?
[Samsung Galaxy Nexus] efrant:
For you, given that you have root, it is extremely simple. Download the update from the post, copy it to /cache (need root for this), reboot into your stock recovery and update. Note you will lose root unless you use something like OTA Rootkeeper, or, just re-root afterwards - no big deal with an unlocked bootloader.

EDIT: And actually no, you do not need CWM installed in most cases.

---------- Post added at 12:44 PM ---------- Previous post was at 12:42 PM ----------

Yes, they are. But the problem with yakjuxw right now, is that the update to 4.0.4 is not released yet (it is only released for yakju and yakjuux), so you are out of luck until Google releases the update for yakjuxw.
[Samsung Galaxy Nexus] sidhaarthm:
Excellent! I will give it a go tonight. If it works, I buy you beer! :D

PS* I had already installed Voodo OTA Rootkeeper in anticipation of the OTA ;) My SU binaries are backed up.
[Samsung Galaxy Nexus] efrant:
It will work! :D

And no need for a beer. I don't accept donations - all I ask is that you share the knowledge -- pay it forward.

And no more untrue postings like:

:D

By the way, just out of curiosity, why do you not want to use a custom recovery? There is more functionality than the stock one (and don't forget that a recovery is completely and absolutely separate from the ROM). Any if you are using the "I want a stock recovery so that I can get the next OTA" excuse, you will, 99.99% of the time, find the update here before you get it pushed OTA to your device, so it makes having a stock recovery irrelevant (because if you have the link, it will install with either the stock recovery or a custom recovery).
[Samsung Galaxy Nexus] sidhaarthm:
Much thanks for your assistance. You've given me some insight into Recovery and I believe I might even install CWM when I get home in about 20mins. Hey, I just tried to get into stock recovery (before downloading and placing the OTA update in the /cache folder) and I faced a fallen Android with a red exclamation on his tummy. Is this normal?i.e. would the stock Recovery only work if I place the update in the cache folder?

Please let me know if you want me to PM you instead. I don't want to spam this thread and take it off topic..
[Samsung Galaxy Nexus] efrant:
The Android with a red exclamation on his tummy IS the stock recovery. To access the menu, you need to push Vol up and Power together -- it is a little finicky, so you may have to do it repeatedly before it actually takes you to the menu.
[Samsung Galaxy Nexus] sidhaarthm:
Okay, you are damn right. It is soo tricky to get that menu to appear! I tried every combination of Vol Up/Down and Power and somehow managed to make it appear. I shall now flash the OTA and get back to you with some good news. Just hope I'm not plagued with the signal death issue a lot of users are reporting. What is your take on that?

Also, could you please send me a link to install (with instructions) the latest CWM? Hope that doesn't need a wipe! ;) just kidding.
[Samsung Galaxy Nexus] LexKas:
But you will need root and/or an unlocked bootloader. In both cases you avoid the warranty, right?

In this case, I'm with sidhaarthm... I would like to keep my GN as stock as possible.

I honestly don't understand why in the GN we can't apply the manual updates just like the Nexus S, that requires none modification on phone to find the update.zip file.
[Samsung Galaxy Nexus] efrant:
I don't have the issue at all. You should always backup everything using CWM before doing any update, just in case you want to go back to 4.0.2 -- otherwise, you will have to wipe to go back to 4.0.2.

All you have to download CWM from here to your PC in the same folder as your fastboot file (rename it to cwm.img to make it easier), boot into fastboot mode, open a command prompt in that folder, and type: fastboot flash recovery cwm.img

That's it. HOWEVER, if you have ever applied an update (like what your are doing now), or received one OTA, there is something else you have to do BEFORE you flash it.

What happens is that any OTA update file places two files (which are not there on a non-updated stock ROM) that re-flash the stock recovery on EVERY reboot. So if you flash CWM without deleting those two files, the stock recovery will magically over-write CWM the next time you boot. So, in order for CWM to "stick", you need to delete them (using Root Explorer or any file manager with root access). The files are:

/system/recovery-from-boot.p

/system/etc/install-recovery.sh

One thing you are forgetting, is that you can eliminate all traces of root and re-lock your bootloader, so no one will be able to tell the difference. You cannot tell the difference between a bootloader that has never been unlocked, and one that was unlocked and re-locked.

But sidhaarthm is rooted with an unlocked bootloader... :)

They keep blocking any holes they can find. :)
[Samsung Galaxy Nexus] sidhaarthm:
Thank you!!

You sir are amazing and a true source of knowledge and inspiration. Based on your guidance I first flashed CWM 5.5.0.2 and performed a full back up of 4.0.2 (just in case). Then simply flashed the 4.0.4 OTA and voila! I am now running 4.0.4 smoothly and I have not been able to detect the network issue so far.:):D

I will keep an eye out though.

Hearty thank you for all your help and advice.:)

Cheers!
[Samsung Galaxy Nexus] LexKas:
Hmmm, I didn't know about that... Thanks for the informations! :)

So, if I root the GN, apply the 4.0.4 update manually (which will un-root the system) nobody will be able to tell that the nexus has ever been rooted before?
[Samsung Galaxy Nexus] efrant:
This is what you will have to do if your bootloader is locked and you are not rooted (and assuming you are currently running yakju ICL53F):

1) Download the yakju-IMM76D-from-ICL53F update from here, and place it in /sdcard on your device.

2) Follow steps 1 through 6 (inclusive) from here, but in step 3, you only need to push the mempodroid file, not all three files.

3) Once you see the #, there are two commands that you have to type:

cat /sdcard/7f97fbc19417.signed-yakju-IMM76D-from-ICL53F.7f97fbc1.zip > /cache/7f97fbc19417.signed-yakju-IMM76D-from-ICL53F.7f97fbc1.zip

rm /data/local/tmp/mempodroid

4) Close the command prompt and reboot your device into your stock recovery.

5) When you see the Android lying down, push volume up and power together repeatedly until you see the recovery menu.

6) Navigate the menu to apply the update.

Notes:

1) You are not rooting your ROM doing this. mempodroid just grants the shell user temporary root access to your system, that is all. You will have no root as soon as you close the command prompt.

2) Doing it this way (i.e., with a locked bootloader and no root), you CANNOT create a backup of your current ICL53F ROM, in case you do not like the IMM76D ROM.

3) I highly recommend to everyone to unlock the bootloader and be done with it. You can always re-lock it (unless you break your USB port) in case you need to return the phone to the store. An unlocked bootloader has no impact on the running of the ROM, nor on receiving updates, nor Google Wallet, nor anything else. But it does give you the ability to use fastboot commands which are EXTREMELY useful and can save your butt in many cases.
[Samsung Galaxy Nexus] LexKas:
Thanks a lot efrant!

That is exactly what I needed... I'll try on the weekend!

About the bootloader... as long as I would have to backup all my stuff before unlock it, I prefer to do it in a near future... When I will have more time available. But I really appreciate your tips and I will think about it. Thanks again!
[Samsung Galaxy Nexus] efrant:
The thing is, you are better off unlocking it now, because you are able to root 4.0.2 without unlocking, do a complete backup, unlock your bootloader, and then restore the backup, with no loss of data. Then you can apply the 4.0.4 update.

If you update to 4.0.4 without unlocking your bootloader, you will not be so lucky. You cannot root 4.0.4 without unlocking your bootloader, so it will be much more difficult to backup everything on your device. It may not even be possible to back up everything.
[Samsung Galaxy Nexus] onthecouchagain:
Efrant, isn't there a way to manually update it without having to root or unlock the bootloader?

I recall on the Nexus S I would always see very simple instructions to manually update it. I did those fine, and easily. It was always something along the lines of "download this package" then put it in your SD, then reboot into the weird screen (sorry I don't know the name), and select it and install and it was done.

Is this the method you're referring to because the link you provided seems to require root/unlocking to manually update 4.04.

EDIT: Just caught up on the thread. Obviously not the same as what I'm talking about. Anyway... my head's spinning a tiny bit. X_X
[Samsung Galaxy Nexus] efrant:
On the GNex, the stock recovery will only flash files that are located in /cache (unlike the stock recovery on the Nexus S or N1, which can also flash files located in /sdcard). The problem is that you can't access /cache without root.

The instructions I posted three posts above yours are how to update without rooting your device. It just uses an exploit to temporarily access /cache.
[Samsung Galaxy Nexus] eevans23:
Has anyone received the OTA notification in the last few days or has it been pulled due to the network drops issue?
[Samsung Galaxy Nexus] sidhaarthm:
I was with you on this uptil a day ago.. as I had been waiting for the OTA for a couple of weeks since it was announced. I am on Three UK, and I got tired of clearing framework cache and checking for updates.

However, 'efrant' opened my eyes (by providing guidance and clearing some misconceptions) last evening and I manually updated my GN with the OTA 4.0.4 files. Happy to say that I do not have the signal drop issue and I am loving the refined Ice Cream Sandwich experience :) No loss of data or root (I restored ROOT using Voodoo OTA Rootkeeper)

Keep in mind I already had Root and an Unlocked Bootloader.
[Samsung Galaxy Nexus] tianshengqii:
nope,and it's not necessary for me.:)
[Samsung Galaxy Nexus] jstierman:
Nope, still waiting for OTA... if they pulled it, then I'll just wait for 4.0.5. Or Jelly bean. Or if I ever get an update...

I don't care enough to flash/manually upgrade it, since I'm happy with 4.0.2, so no big deal. It'd be nice if there's some battery boost though.
[Samsung Galaxy Nexus] onthecouchagain:
I'm on a Mac. What should be changed? The way I input commands, right? I just add a slash in front of every single one while in Terminal? / ?
[Samsung Galaxy Nexus] efrant:
Yeah, I believe the only thing that would change is this command:

adb push mempodroid /data/local/tmp/mempodroid

should be:

./adb push mempodroid /data/local/tmp/mempodroid

Everything else should be identical I think (me not being a MacOS user and all... :) )
[Samsung Galaxy Nexus] tokyojay70:
G Nexus

4.0.2

UK 3 Network

Hi

Just a quick update since my last post.. I still have no 4.0.4 update notification, tried the google framework trick so many times I have lost count but still no update.

I still cannot understand why I received the 4.0.2 update without any problems but 4.0.4 just does not get detected. I cannot understand why the actual check fails if it has been released, as I mentioned in an ealier post, my friend ( same phone, same network ) had his 4.0.4 update over 2 weeks ago now.

Can anyone clarify this for me... I am thinking of doing a manual update using the firmware and Odin download method. I have all my pictures etc backed up but will the phone lose all the network settings like APN's, MMS etc. ? or will it still have the settings for the 3 network after the update.

Thanks

TJ
[Samsung Galaxy Nexus] dendirk:
Google has pulled back the update because of radio problems

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] tokyojay70:
I suppose that makes sense, thanks for the info.

TJ.