Develop Bugs

[Q] GSM GNex hasn't upgraded to 4.0.2?

First, 4.0.2 is the latest version for the GSM GNex, right?
I thought it was... anyway. I got my phone yesterday and unloced the bootloader and rooted, but didn't install CWM or do anything else that actually required root. The phone did apply an OTA update, but I don't remember if it was before or after I rooted.
Anyway, it is now saying 4.0.1 and 'check for updates doesn't find anything'.
...so, that's wrong, isn't it? Any idea why? I thought rooting didn't mess with OTA (unless you start messing with things too much, of course).
Thanks in advance!

Oh, and it is yakju.

No only updated builds of 4.0.1 have been pushed to the GSM version.

4.0.2 was for the Verizon version.

Ah ha!
Thanks guys!

Just thought I'd mention that I am on a GSM GN and got asked to update to 4.0.2. today. There is a thread in general about it. I took screenshot too. But the update didn't apply right. I downloaded it and hit install and restart but nothing happened. hmmm...
Maybe I was offered it by mistake...
The thread is here http://forum.xda-developers.com/showthread.php?t=1395047

Given that JBQ posted factory images of 4.0.2 for the Maguro/Tuna build I think it's safe to say it's going to OTA. Multiple GSM owners have received the update notification.
Updates roll out SLOWLY and are flagged by IMEI. If your IMEI isn't flagged to get the update yet there is no number of checkins that will prompt you to download it. Normally updates have rolled out over a few weeks. This process was explained by someone at Google a while back. The OTA goes to a small group during which time they can ensure that it isn't causing issues. If that goes well it's expanded to a larger group and then subsequently all devices as it scales up.

GSM version has 4.0.2 update, but not pushed over.
i have manually downloaded the stock image from google and manualy flash it.
i am now running 4.0.2
http://code.google.com/android/nexus/images.html
what i did was,
backup my system (just incase).
Factory Images "yakju" for Galaxy Nexus "maguro" (GSM/HSPA+)
(all file extract from the 4.0.2 (ICL53F) image)
flash bootloader
flash radio
flash recovery
flash system
and reboot, and presto. you are on 4.0.2.
my experience, this does not remove all your data.
just similar to a upgrade for me.
a side note. i am running everything stock..

[Q] Avoiding OTA updates

Hi all, I've rooted,unlocked and installed clockwork mod using mskips nexus toolkit (which worked brilliantly by the way) and the other night I recieved the 4.0.2 update request. Stupidly, in my moment of joy at a new update, I hit go without thinking about my newly unlocked and rooted phone. It hung on the android man/ exclammation mark screen and I had to do a battery pull. Thankfully it booted up fine and as far as my limited knowledge can tell its still rooted,still has clockwork recovery and is still 4.0.1. Having battered the search box I've discovered the problems lies at having clockwork recovery and not standard recovery.
I've yet to install a custom ROM (but probably will shortly) but I keep getting the 'Update available' thing pop up and even when I hit 'remind later' it seems to pop up every 30 mins or so.
So, my question is if I put a custom ROM with 4.0.3 will I still get the update notifications or will they realise I'm running 4.0.3 and leave me alone?
How does the google servers know what version I'm running - does it just go on their history of what updates they have sent you ?
Thanks in advance for anyone who can enlighten me......

Once you install a custom rom you won't get any OTA updates anymore. Even if they'd push 4.0.4.
Not sure how to fix your issue without installing a CR, but since you're saying you'll do it shortly your issue should be resolved soon I guess.

I thought that would be the case but having never installed a custom ROM I wasn't sure, kind of forces my hand into a custom rom now I've got clockwork recovery..... Need to do it ASAP cos every time I pick up the phone its got that damn update screen !
Cheers Tanith

To make sure you don't get the OTA update notification in a stock ROM, change the ro.build.fingerprint line in your build.prop file to the following:
ro.build.fingerprint=google/yakju/maguro:4.0.2/ICL53F/235179:user/release-keys

efrant said:
To make sure you don't get the OTA update notification in a stock ROM, change the ro.build.fingerprint line in your build.prop file to the following:
ro.build.fingerprint=google/yakju/maguro:4.0.2/ICL53F/235179:user/release-keys
Click to expand...
Click to collapse
Thanks for that tip, I'm keen to flash my first ROM now(got the XDA bug hard !) so won't be needing to worry about that now, just flashed up my radio to XXKK6 and will be sticking bigxie's ROM on shortly.......
cheers anyway efrant.

I'm just wondering when us SGN owners in Denmark will get the OTA..
Sent from my Galaxy Nexus using xda premium

efrant said:
To make sure you don't get the OTA update notification in a stock ROM, change the ro.build.fingerprint line in your build.prop file to the following:
ro.build.fingerprint=google/yakju/maguro:4.0.2/ICL53F/235179:user/release-keys
Click to expand...
Click to collapse
Hello, this is exactly what I need..
Kan you maybe explain how I can do this taking into account I am a total noob?
Do I need a program or something to do this?
Thanks for any help!!
John

If you don't know how to do it then don't even try until you've read up on it...Google 'edit build.prop Android' and see what you get

efrant said:
To make sure you don't get the OTA update notification in a stock ROM, change the ro.build.fingerprint line in your build.prop file to the following:
ro.build.fingerprint=google/yakju/maguro:4.0.2/ICL53F/235179:user/release-keys
Click to expand...
Click to collapse
I'm on a 4.1 ROM and it's popping up an update over and over for 4.1............. yeah....wtf?
Anyways, can I edit my build.prop the same way as above? (but I change 4.0.2 to... I dunno, 4.1.1 so it stops asking?)

MitchRapp said:
I'm on a 4.1 ROM and it's popping up an update over and over for 4.1............. yeah....wtf?
Anyways, can I edit my build.prop the same way as above? (but I change 4.0.2 to... I dunno, 4.1.1 so it stops asking?)
Click to expand...
Click to collapse
See here.

thanks dude (and +thanks to your post heh)
rebooting phone now.... 4.1 is just so smooth and I've seen bad posts about 4.1.1 so I won't bother yet!

I guess it's because of different build fingerprints, but I'm also being offered the 4.1 update although I'm already on 4.1 (according to About System).

[Q] Question for Canadian Users who switched to yakju

This has probably been answered before by one or two people, but I'd rather know from the whole lot of you brave souls who have switched from yakjuux to yakju.
I'm specifically wondering from those of you that have done the COMPLETE switchover to the yakju build... that includes ALL things that come with it, including it's radio.
I know we can flash the KL1 radio on top, but I'm not looking to do that. I want the entire thing to be from Google, and keep it as such. From what I understand, when you have the yakju build, and the KL1 radio, you will not get OTA updates automatically, thus having to flash manually. On the flip side, if its a complete yakju, including the radio that comes with it, you will get the OTA updates automatically.
So here's the questions:
1. Have any of you flashed the yakju build on your phones KEEPING THE RADIO that is a part of that build? If so, what are your experiences with reception/data specifically on the Bell Network? Any difference that you've noticed?
2. Am I wrong in my thinking? If you did flash yakju, then the KL1 radio, will you definitely receive OTA updates automatically? As in no real user intervention other than clicking "update"?
I want to be sure before I do this, because I cannot find a complete image of the yakjuux build that includes everything including the bootloader in case something goes wrong/or doesn't update the way a true Google experience should.
Please let me now.
Thanks

I am running stock 4.0.2 with everything from the official image. No problem with signal. What is your worry?
Sent from my Galaxy Nexus using XDA App

superlj said:
I am running stock 4.0.2 with everything from the official image. No problem with signal. What is your worry?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Just want to make sure the radio from the official build works properly with Bell.
Don't really want to create a Frankenstein build so too speak by adding different radios
Sent from my Galaxy Nexus using Tapatalk

I changed mine to yakju shortly after I got the phone, about two weeks ago.
I haven't noticed any difference with the radio, good or bad. Still no issues with reception or anything dropping out.
Can't tell you about the OTA updates though, haven't received anything yet to go past 4.0.2. If/when I do, I'll update my reply to help everyone else out.

torradan said:
I changed mine to yakju shortly after I got the phone, about two weeks ago.
I haven't noticed any difference with the radio, good or bad. Still no issues with reception or anything dropping out.
Can't tell you about the OTA updates though, haven't received anything yet to go past 4.0.2. If/when I do, I'll update my reply to help everyone else out.
Click to expand...
Click to collapse
Thank you for your reply. Just to clarify, you are using the stock radio that came with yakju? I think its KK or something? Or did you change over to KL1?

greeced said:
Thank you for your reply. Just to clarify, you are using the stock radio that came with yakju? I think its KK or something? Or did you change over to KL1?
Click to expand...
Click to collapse
bump. bump.

why are you so worried about receiving ota automatically? since you are on xda and know how to flash you will always have the latest build. Being in canada we usually are slow to get updates(Galaxy Nexus is still on 4.0.1 here) so whats the point in waiting for ota. if you are planning to flash an update now why not do it again when a new one comes out.
btw to answer your questions about the radio, the stock one,XXKK6, will work fine with bell although UGKL1 seems to work better for me on Fido. UGKL1 is probably the radio that your phone has now. it was on my stock fido GN.

I flashed the entire package, including the xxkk6 radio.. Works perfectly fine on Rogers, no comment for Bell but should be fine. Just try it, flash it back if you don't like it. Takes all of 2 minutes.

From what I understand (and I'm still new to this as well) you need to use the radio that comes with the official image otherwise you won't get OTA updates associated with that rom.
Newbie account so I can't post links yet but search "galaxy nexus upgrade to official roms yakju build" and its the leemn wordpress blog that says:
"After flashing to yakju build, you can still receive notification of the OTA updates.If you have flashed the radio, system, userdata and boot partitions, and you still have the stock recovery (or have flashed it) from the 4.0.2 image, you will be able to install the updates. However, if you flash a different radio, or different kernel , or a custom recovery, you will need to flash back the stock ones first before being able to install the update."

That's the whole thing.
When I was on the SGS, I tried a while slew of custom roms as well as the European beta builds.
I wasn't worried about doing that because there was always a way to go back to KG3, by spoofing the firmware to make KIES think it was on JL2. KIES would download KG3 officially back to the phone.
I always seemed to revert back to stock because none of the beta or custom roms seemed to work efficiently for me the way the stock one did.
I know, I'm strange.
So that experience brings me here. Without an official download of the yakjuux build available (bootloader image), there really is no going back if something just doesn't work as intended. (remember, we all use our phones differently).
That's why the fright. I just don't want to get to the point that this Canadian incarnation starts having an identity crisis.
Sent from my Galaxy Nexus using Tapatalk

I flashed it all.
Works great. No issues. I also wanted 100% stock and so far, i am very happy with it.

greeced said:
Thank you for your reply. Just to clarify, you are using the stock radio that came with yakju? I think its KK or something? Or did you change over to KL1?
Click to expand...
Click to collapse
Sorry missed your question, but I'm using the KL1 radio.

I am with Fido and have complete 4.0.2 stock rom. I had some strange issues with signals but everything is fine after I changed to a new SIM.
Sent from my Galaxy Nexus using XDA App

greeced said:
That's the whole thing.
When I was on the SGS, I tried a while slew of custom roms as well as the European beta builds.
I wasn't worried about doing that because there was always a way to go back to KG3, by spoofing the firmware to make KIES think it was on JL2. KIES would download KG3 officially back to the phone.
I always seemed to revert back to stock because none of the beta or custom roms seemed to work efficiently for me the way the stock one did.
I know, I'm strange.
So that experience brings me here. Without an official download of the yakjuux build available (bootloader image), there really is no going back if something just doesn't work as intended. (remember, we all use our phones differently).
That's why the fright. I just don't want to get to the point that this Canadian incarnation starts having an identity crisis.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I'm not sure what the problem is. When you unlock your bootloader, you just do a nandroid backup, and it backups up your system, data, recovery and boot partitions. The radio is already available. So you can always go back to "stock" yakjuux in case yakju doesn't work (which it obviously does for Canadian users). I've even posted a nandroid backup of my yakjuux build before I flashed yakju. There is a thread in the general section. And to address your concern about "always reverting to stock", yakju IS the stock ROM, it is not a beta or a custom ROM.
The bootloader has nothing to do with yakju or yakjuux or whatever. It will not affect anything related to getting an OTA update or installing an OTA update. Keep your current bootloader if you are worried about not having a backup, and go ahead and flash all of the other images (after backing up your originals of course). That way, you can always return to your yakjuxx if you think there is a problem. Just because you didn't flash the bootloader that came with the latest yakju image does not at all mean you are not using yakju, and I would not call it a "frankenbuild" -- think of the bootloader as the BIOS in a computer. You computer is running Windows regardless if you are using an ASUS P5Q motherboard, or an ABIT IP5 motherboard -- both have different BIOS, but the OS is still Windows. Same with a GN -- you are running yakju regardless of whether you bootloader is 10, 14, 15, etc.
EDIT: To specifically address your question number 2 -- if you flash the system, data and boot images from yakju, you are running yakju, and you will receive the notification for an OTA update when it is available. However, you will not be able to have it install automatically if you don't have the radio image that came with the yakju build and a stock recovery (they are all the same). You can, however, flash those back as soon as you receive the OTA update notification and it will install automatically. Bootloader has no relevance whatsoever.

Great explanation. Thank you efrant. You've answered everything I've needed to know
Sent from my Galaxy Nexus using Tapatalk

Well finally took the plunge and went to yakju from yakjuux. Although my experience wasn't as seemless as everyone elses, so I thought I'd tell everyone just in case someone else runs in to the same problem.
For starters: I followed efrants excellent procedure from this exact post. However it also must be noted that I decided to use the 41F (4.0.1) firmware from Google's images instead of the 53F (4.0.2) image. I did this because I wanted to experience an update. lol
Now, at first I had to try several drivers in order for my Windows 7 laptop to even see the phone with the "fastboot devices" command. I finally found one that works. Coincidentally, one driver will work on one machine, but won't on the next, I have no idea why. After finally getting the right one, I proceeded:
I did all steps to the letter, but skipped steps 4,5 and 12, as the post says they were optional and I didn't really want to lose my bootloader and recovery in case I wanted to revert back to yakjuux.
After completing all steps but those, I did the final "fastboot reboot" and the phone restarted.
Here's where the ride began:
When it restarted, it seemed like everything was fine. It took a while to find Bell's settings, but it was ok. It then said an update to 4.0.2. was available.
Upon the reboot and install, the phone shut off, and rebooted twice, after the second time, I had an android on the ground with its chest open and a RED exclamationed triangle above it. My thoughts were "uh oh". I waited and waited, and nothing was happening. Pressing power and holding it down, wouldn't help.... After approx 5 mins I was about to do a battery pull, and it restarted itself, but remained on the 41F update.
Each restart would say it was upgrading, but never did.. always stayed on 41F.
So I went back and did everything in the procedure, not omitting anything this time (goodbye yakjuux bootloader!) and it went off without a hitch... This time my android figure was standing up, very much alive and getting a heart transplant.
So here I am.. Yakju configured and using the yakju KK6 radio. All seems well. Haven't decided if I'm going to put the KL1 radio on as yet, but thats for another day.
Thanks again efrant for all your help and patience with me.

@greeced Welcome to yakju. I doubt you will ever go back to yakjuux.
Sent from my Galaxy Nexus using Tapatalk

Well, I have been on yakju for a few days now and I can say no problems whatsoever.
At first I felt as if it was slightly Laggy, but that seemed to correct itself after a day or so. Not sure why, but the phone is just as quick as before now.
As for the radio, I wanted to stay completely stock, and that included the radio. So my phone is running the stock KK6 that came with the update, and I noticed my DBM levels are just as good as before if not better. So I don't feel the need to flash KL1.
Overall very happy that I'm now Pure Google.
One thing to note:
When I was on my SGS, I always factory reset after every flash, which always seemed to speed up the experience of the new ROM.
I think that should be the case for all firmware updates, including googles.
It's a painful process to redo everything, but well worth it in my opinion.
I mean think about it, installing a fresh copy of windows always performs better than doing an upgrade of windows, so that should be the same here.
We are dealing with computers after all.
At any rate. Just thought I'd update my experience in case anyone else who is on bell felt apprehensive like me.
Sent from my Galaxy Nexus using Tapatalk

greeced said:
Well, I have been on yakju for a few days now and I can say no problems whatsoever.
At first I felt as if it was slightly Laggy, but that seemed to correct itself after a day or so. Not sure why, but the phone is just as quick as before now.
Click to expand...
Click to collapse
I think the general consensus is that ICL53F is more laggy that ITL41F or ITL41D, so it is not a yakju vs yakjuux issue, it is a 4.0.1 vs 4.0.2 issue.
greeced said:
As for the radio, I wanted to stay completely stock, and that included the radio. So my phone is running the stock KK6 that came with the update, and I noticed my DBM levels are just as good as before if not better. So I don't feel the need to flash KL1.
Click to expand...
Click to collapse
Radio performance varies with a huge number of factors. If you are happy with how one radio works, use it. If you want to see if another one is better, try it. If you don't like it, flash back. It takes all of 30 secs to flash a radio.
greeced said:
[snip]
When I was on my SGS, I always factory reset after every flash, which always seemed to speed up the experience of the new ROM.
I think that should be the case for all firmware updates, including googles.
It's a painful process to redo everything, but well worth it in my opinion.
I mean think about it, installing a fresh copy of windows always performs better than doing an upgrade of windows, so that should be the same here.
Click to expand...
Click to collapse
If you believe this, then I suggest that you do not flash older builds and OTA update to a newer ones. This process adds more files to your ROM, and is not as clean as flashing the latest build from Google's factory image site.
When the next version of Android is released, the full version will likely be available on Google's factory image site shortly before OTA's for yakju start rolling out.* If you don't mind redoing your settings, apps, etc., it is better (and faster) to flash the full build, instead of updating your current build.
*My assumption based on release dates for previous versions.

Question efrant.
I relocked my bootloader purposely.
If I wanted to test other radios does the bootloader need to be unlocked?
If it does, no big deal, I just won't do it
Sent from my Galaxy Nexus using Tapatalk

Yakju not getting OTA update

Hi guys,
I used the GNEX toolkit to unlock my bootloader and then flash to 4.0.2 yakju. I'm just wondering why I'm not getting an OTA for 4.0.4 or 4.0.3. I've tried clearing the data in GoogleFrameWorkServices. I've also flashed stock recovery.
Did I do something wrong, or is there actually no update?. P.S I'm in Australia.
Any help would be greatly appreciated.

Im in the same boat.
I have flashed the completely stock 4.0.4 ROM from Google Code. I have not received the IMM76I update yet.
I have cleared the framework cache too and still nothing.
I live in Melbourne (australia) and I am assuming that the update to yakju devices works on a country-by-country basis.
IF I don't receive it soon, I am just going to hope Google Code gets updated and I will just reflash a the newer version.
I do not want to root the phone or using work-around methods to install an update. I like having a completely stock phone with a locked bootloader.
(Marshallaw.. Why not just download the 4.0.4 update from Google Code and flash using Fastboot? Atleast that way, you know your on the latest Android version and have a better chance of receiving the IMM76I update, or if worst comes to worst, just wait until Google Code is updated to the latest version and flash that?)
The way Google updates their devices is pretty pathetic. You would think they would push the update to every stock YAKJU device everywhere and not be so selective. My old Nexus S received 4.0.4 update and my stock Galaxy Nexus never received it, so I had to manually flash. Very stupid.

Simmo3D said:
[snip]
IF I don't receive it soon, I am just going to hope Google Code gets updated and I will just reflash a the newer version.
I do not want to root the phone or using work-around methods to install an update. I like having a completely stock phone with a locked bootloader.
Click to expand...
Click to collapse
I think you are confusing a few things:
1) What is posted on Google Code (as you put it), are NOT updates -- they are complete, full ROMs.
2) What is posted here are incremental update that UPDATE your existing ROM.
There is a difference between the two, despite the end result being the same.
3) Having an unlocked bootloader or a locked bootloader does not mean you are stock or are not stock -- it has nothing to do with it at all. You are not adding or taking away anything from the firmware on the device...
4) You say you do not want to use a work around to flash the update, but you are using a work around to flash a full ROM? Something there doesn't compute for me.
5) Flashing a stock update file does not make you any less/more stock than flashing a full ROM.

I don't think you understand what I meant.. Im hoping Google updated their full ROM with the IMM76I kernel and bug fixes...
hence, I am waiting for an updated full ROM that 'includes' the latest kernel update.
e.g. Google Code features :
4.0.1 (ITL41D) and 4.0.1 (ITL41F). I am waiting for
4.0.4 (IMM76D) and 4.0.4 (IMM76I) to be posted on their site.
I also know that having a locked bootloader does not make it stock, but my point was I am on stock 4.0.4 with a locked bootloader, so I am waiting for an OTA so I don't need to re-install all my files/apps.
But if I don't receive the OTA update, I will be reflashing the entire ROM once its available on Google Code.

Simmo3D said:
I don't think you understand what I meant.. Im hoping Google updated their full ROM with the IMM76I kernel and bug fixes...
hence, I am waiting for an updated full ROM that 'includes' the latest kernel update.
e.g. Google Code features :
4.0.1 (ITL41D) and 4.0.1 (ITL41F). I am waiting for
4.0.4 (IMM76D) and 4.0.4 (IMM76I) to be posted on their site.
I also know that having a locked bootloader does not make it stock, but my point was I am on stock 4.0.4 with a locked bootloader, so I am waiting for an OTA so I don't need to re-install all my files/apps.
But if I don't receive the OTA update, I will be reflashing the entire ROM once its available on Google Code.
Click to expand...
Click to collapse
Well, I'm not sure if this is it but here's the OTA package for IMM76I from IMM76D. It might just be a test build which was only pushed to small portion of users to test it which would explain not everyone getting it.
And Marshalllaw, you've already begun to flash things and mess around, why not just flash the stock build of 4.0.4 straight away rather than relying on an OTA?

Simmo3D said:
[snip]
I also know that having a locked bootloader does not make it stock, but my point was I am on stock 4.0.4 with a locked bootloader, so I am waiting for an OTA so I don't need to re-install all my files/apps.
But if I don't receive the OTA update, I will be reflashing the entire ROM once its available on Google Code.
Click to expand...
Click to collapse
Ok, but you do realize that manually installing the IMM76I update (which you can do right now, although requires an unlocked bootloader) ends you up at the exact same place the flashing the IMM76I image when it comes out (and it will still require an unlocked bootloader). So whether you install the update, or what for the full image, you will still wipe, and you will end up at the same place -- you will just get there sooner with the update.

OK but how do you flash this with fastboot once I unlock my boot loader. I need to boot with CWM don't I?
Sent from my Galaxy Nexus using xda premium

Simmo3D said:
OK but how do you flash this with fastboot once I unlock my boot loader. I need to boot with CWM don't I?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Correct, you do. But booting CWM is different from flashing CWM. When you boot it, you are not "writing" anything to your device - you are only loading the kernel and ramdisk into your device's RAM. It only boots CWM one time - as soon as you reboot, it is no longer there, as it was never flashed - it just existed in RAM.
Additionally, even if you did flash it, it still wouldn't be there when you rebooted, because EVERY OTA update adds two files to your device that automatically re-flash the stock recovery on EVERY boot of your device.

Unlawful said:
Well, I'm not sure if this is it but here's the OTA package for IMM76I from IMM76D. It might just be a test build which was only pushed to small portion of users to test it which would explain not everyone getting it.
And Marshalllaw, you've already begun to flash things and mess around, why not just flash the stock build of 4.0.4 straight away rather than relying on an OTA?
Click to expand...
Click to collapse
Hi Unlawful. Yeah I can always flash it directly to 4.0.4, its more that this is my first Android phone / first experience messing with bootloaders and roms. I was more so just wondering if the lack of OTA update to either 4.0.3 or 4.0.4 was that i've screwed something up or that the update has not been pushed to all devices.
My device info is: 19250XXKK6, ICL35F. Its basically the same as when I first bought it but not Yakjuwx. I more or less flashed to Yakju because people were saying that you could get OTA updates faster or something.
Thanks for the help, sorry if this is a noob question.

I wouldn't be too sure though I would really doubt it's something that you did. Have you pressed 'Check Now' somewhere in settings to check whether there's an update?

Unlawful said:
I wouldn't be too sure though I would really doubt it's something that you did. Have you pressed 'Check Now' somewhere in settings to check whether there's an update?
Click to expand...
Click to collapse
Yeah I hit check now and it always says I'm the most up to date. I tried clearing data in google services framework and then hitting check now. Nothing changed.
I just find it odd that I wouldn't get an OTA for 4.0.3.
I used the GNEX toolkit to flash the stock rom which I got from developers.google.com/android/nexus/images. I read online that someone thought that 4.0.4 was pulled from OTA, but I would have thought I would get 4.0.3. I'm nervous that I've messed something up lol

marshalllaw said:
Yeah I hit check now and it always says I'm the most up to date. I tried clearing data in google services framework and then hitting check now. Nothing changed.
I just find it odd that I wouldn't get an OTA for 4.0.3.
I used the GNEX toolkit to flash the stock rom which I got from developers.google.com/android/nexus/images. I read online that someone thought that 4.0.4 was pulled from OTA, but I would have thought I would get 4.0.3. I'm nervous that I've messed something up lol
Click to expand...
Click to collapse
4.0.3 was never released in OTA form.

Unlawful said:
I wouldn't be too sure though I would really doubt it's something that you did. Have you pressed 'Check Now' somewhere in settings to check whether there's an update?
Click to expand...
Click to collapse
That does not work. You will have to wait until Google decides it's time for your IMEI to receive it...
marshalllaw said:
Yeah I hit check now and it always says I'm the most up to date. I tried clearing data in google services framework and then hitting check now. Nothing changed.
I just find it odd that I wouldn't get an OTA for 4.0.3.
I used the GNEX toolkit to flash the stock rom which I got from developers.google.com/android/nexus/images. I read online that someone thought that 4.0.4 was pulled from OTA, but I would have thought I would get 4.0.3. I'm nervous that I've messed something up lol
Click to expand...
Click to collapse
You did not mess anything up. As martonikaj said, there was never any 4.0.3 update.
Updates are not rolled out to everyone all at once. It could take seconds or MONTHS before you get the OTA, after the first person gets it.

Awesome . Thanks for the help guys.
Having an Android is great for all the exploring you can do, finding out how it works though can be a bit daunting.
Sorry for the noob question!.

Virgin Canada GNex JB OTA to 4.1.1 today!

I woke up this morning to find an OTA waiting for my Canadian Yakjuux GNex. I was a bit apprehensive as I had my first OTA since launch last week which bumped me up from 4.0.1 to 4.0.2. After applying & rebooting I'm now on 4.1.1. So far I'm loving it, my phone is faster, smoorher & more responsive than ever.
My baseband saw an update too, for anyone interested, on 4.0.2 I had version UGLA4 and now I'm on version UGLH1. I'm really interested to see how my reception is now in rural areas as I haven't been out to the country since I was still on 4.0.1 with baseband version UGKL1. I had my GNex for 4 months before i moved to the city & my reception in the country was just awful.
I'm still fairly new to Android as my GNex is my first Android device, I'm technically inclined tho a little rusty with Linux. I'm still a virgin to both flashing & rooting, a little resistant as I have no landline so my GNex is my daily driver. I've been lurking on here to get to learn what tools are out there as well as get a basic understanding on the basics of rooting & flashing. Despite now having my wish of JB love on my GNex, at some point I'd still like to jump over to yakju or takju so I can get updates as they come direct from Google rather than whoever (Samsung or Virgin) pushes them to yakjuux.

If anyone else in Canada gets the update and is able, can you pull the name of the OTA update file for us please?
Open up the log files in /cache/recovery using a text editor and find the name of a file ending in zip. (Root required of course.)

I'm on Bell, I got my update early last week. I was going to flash this weekend. Mine is the same as the efrant posted earlier.

CASz said:
I'm on Bell, I got my update early last week. I was going to flash this weekend. Mine is the same as the efrant posted earlier.
Click to expand...
Click to collapse
I haven't posted any update. If you can get the file name, it would be much appreciated.

I got you mixed up with jz687. I'm not rooted so I can't look at the file name, I was just going off the screen capture posted by jz687. Since the radio was posted I thought you got the file name as well.

CASz said:
I got you mixed up with jz687. I'm not rooted so I can't look at the file name, I was just going off the screen capture posted by jz687. Since the radio was posted I thought you got the file name as well.
Click to expand...
Click to collapse
He never posted any update either. He received his phone with that build on it. That's why I was asking for the file name, as no one has posted it here at XDA.