Develop Bugs

Still on 4.0.1

Dears,
I'm still using my galaxy nexus on the 4.0.1 version, I bought Mine from handtec and now using it in Bahrain
Sent from my Galaxy Nexus using xda premium

Still on 4.0.1 sim free in UK
Sent from my Galaxy Nexus using Tapatalk

I'm still using 4.0.1, imported from Clove to Spain

Still on 4.0.1, Bell Canada.

Still on 4.0.1, using an imported GSM model in the U.S. It originally came with yakjuwx, so I flashed the yakju 4.0.1 build. The phone successfully checks in for updates, but keeps displaying the "Your phone is up to date" message. Perhaps our IMEI numbers just haven't come up yet?

Germany, yakju 4.0.1 build. Still on 4.0.1. Checks for updates but it says its up to date.
Guess Ill have to wait ...

Poerger said:
Germany, yakju 4.0.1 build. Still on 4.0.1. Checks for updates but it says its up to date.
Guess Ill have to wait ...
Click to expand...
Click to collapse
same 4 me.
And ota updates are working for me.got the volume-fix per ota.
no root, no open bootloader
shame on google.i was thinking the new Superphone Galaxy Nexus by google, get direct updates.
but for now the old nexus s are two steps ahead.... on 4.0.3

i have unlocked my device and rooted it, will it affect the OTA?

Still on 4.0.1 (ITL41D) yakju sim free UK. I may manually flash tonight, been waiting too long. Never had any OTA updates yet.

NoEnd said:
i have unlocked my device and rooted it, will it affect the OTA?
Click to expand...
Click to collapse
no
only when you change your bootlader,install cwm or a custom rom.
rooting and bootloader unlocking are fine for otas
---------- Post added at 03:13 PM ---------- Previous post was at 03:10 PM ----------
btw
is there a Email adress or something else to get in contact with google?
I think they have forgoten to bring the updates to all phones because 4.0.3 is arrived and 4.0.2 is "old"

lurchie85 said:
only when you change your bootlader,install cwm or a custom rom.
Click to expand...
Click to collapse
Installing CWM recovery breaks OTA updates? I could swear I got the volume fix after I did this, but I might be mistaken. The update screen acts as though it is successfully checking for updates, but showing me up to date.

if you dont want to wait just get the rom from here http://code.google.com/android/nexus/images.html
and flash with fastboot you can do it with out wiping the phone

If your phone is yakju and you have an unlocked bootloader you can just manually apply the update yourself. That's what I did and it works great. Here's a step by step: http://www.androidcentral.com/how-manually-update-your-gsm-galaxy-nexus-android-402-ota
Also having root or an unlocked bootloader won't stop you from getting OTA updates. You will lose root if you update OTA but the bootloader will remain unlocked until you lock it again yourself. Some custom roms have OTA's turned off but if you're still stock, you'll get the update if you wait. Give them some time, they're pushing this to all the Gal Nex phones plus 4.0.3 to the Nexus S. That's a lot of data floating around out there.

qreffie said:
Give them some time, they're pushing this to all the Gal Nex phones plus 4.0.3 to the Nexus S. That's a lot of data floating around out there.
Click to expand...
Click to collapse
no problem to wait.so far everything works with 4.0.1. but it makes me a little bit angry that the nexus s get 4.0.3 earlier as my super new Smartphone galaxy nexus which is titled as new superphone by google and for ics.
and that i wait 5 or 6 days maybe longer to geht a update to a old version!

lurchie85 said:
no
only when you change your bootlader,install cwm or a custom rom.
rooting and bootloader unlocking are fine for otas
Click to expand...
Click to collapse
I'm pretty sure installing CWM doesn't break OTAs because the OTA would just write over the custom recovery. That's happened to me before on my Nexus S when I had it rooted with CWM recovery. After receiving an OTA it overwrote everything and I just chose to keep it that way.

qreffie said:
I'm pretty sure installing CWM doesn't break OTAs because the OTA would just write over the custom recovery. That's happened to me before on my Nexus S when I had it rooted with CWM recovery. After receiving an OTA it overwrote everything and I just chose to keep it that way.
Click to expand...
Click to collapse
mhhh ok. my fail

Me too, i'm still in 4.0.1
France
XXKK1
ITL41F
google brand
YAKJU
bootload open + root
What's wrong?
Why don't we had the upgrade ?

Everyone with a Nexus will get the update, just have to be a little patient. There has never been a roll out that didn't last for a couple weeks. They just started the roll out not even 72 hours ago.

I am in the netherlands and nothing yet.

Unfortunately, still on 4.0.1 sim-free in Poland...

[Q] Backup Bootloader and Radio?

I will be getting my Galaxy Nexus soon and I am pretty sure it will not be a Yakju model. I would like to flash Google's build for quick OTA updates but would also like a backup of the shipping Bootloader and Radio for Warranty purposes. Does anybody know how I can go about this? I know the Radio Images are available in the Development section but I can't seem to find any different Bootloaders available for flashing. Thanks in advance.

If you're using official updates then there is no need to worry about warranty or anything like that. If you're worried then when you get the phone, bout into the bootloader and take note of the numbers. There are threads in the development forum that have radios and what not to flash anyway.

Thanks for the quick reply, I know how to flash radios but how would I go about flashing my original bootloader? I don't think there are a list of flashable bootloaders in the Dev section...

dnlsmy said:
I will be getting my Galaxy Nexus soon and I am pretty sure it will not be a Yakju model. I would like to flash Google's build for quick OTA updates but would also like a backup of the shipping Bootloader and Radio for Warranty purposes. Does anybody know how I can go about this? I know the Radio Images are available in the Development section but I can't seem to find any different Bootloaders available for flashing. Thanks in advance.
Click to expand...
Click to collapse
All the radios can be found in this thread. Most, but not all, of the bootloaders are also floating around. I haven't figured out how to dump the bootloader yet, and no one seems to have provided any info on how-to.

Thanks anyway, I guess I'll just note the bootloader and radio for now.

are you worried that you can restore the bootloader if you have to send it back to warranty or for a soft brick? with the galaxy nexus toolkit you can relock the bootloader. flashing back to stock google image and then locking the boot will return your phone to stock if you need to return/warranty it.

neotekz said:
are you worried that you can restore the bootloader if you have to send it back to warranty or for a soft brick? with the galaxy nexus toolkit you can relock the bootloader. flashing back to stock google image and then locking the boot will return your phone to stock if you need to return/warranty it.
Click to expand...
Click to collapse
A couple of points:
1) You certainly don't need any toolkit to relock the bootloader. It can be done by entering one command in fastboot mode (i.e., fastboot oem lock), that is it.
2) Not all GN devices came with the stock Google image (yakju), and therefore, flashing that image will not take everyone back to their "stock". For example, those that bought a GN in Canada had yakjuux installed on their devices. Those devices also had the 14 bootloader. So far, a flashable image of that bootloader has not surfaced.

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!.

[Q] [JB][OTA] Will rooted Phones get OTA ?

Hi,
I got a Gnex from Singapore singtel.
I didn't want to wait for OTA to 4.1.1 so I rooted and flashed JB 4.1.1
I am running the stock rom from google..
Now that 4.1.2 is released and lot of people seem to have got the OTA, I am yet to get my OTA ...
I am wondering if it is because of the Unlocking and rooting done to my device...
Does Unlocking bootloader and Rooting the device stop OTA update to 4.1.2?
Also pls tell me if you have got your OTA yet or not ...

[email protected]$#eR said:
Hi,
I got a Gnex from Singapore singtel.
I didn't want to wait for OTA to 4.1.1 so I rooted and flashed JB 4.1.1
I am running the stock rom from google..
Click to expand...
Click to collapse
If you're running the stock ROM images from Google, then you didn't have to root. All you did was unlock the bootloader to flash those. If you rooted after, that was completely unnecessary to the process of switching.
(Sorry just a little pet peeve. People apparently have trouble grasping the difference between rooting and unlocking a bootloader, and the difference between a custom ROM and an official Google factory image.)
Now that 4.1.2 is released and lot of people seem to have got the OTA, I am yet to get my OTA ...
I am wondering if it is because of the Unlocking and rooting done to my device...
Does Unlocking bootloader and Rooting the device stop OTA update to 4.1.2?
Click to expand...
Click to collapse
NO. Unlocking your bootloader and rooting does not at all stop your device from notifying you that an OTA is ready to download and install. I don't know how many times this has to be posted in these forums before people understand...
Unlocked bootloader does nothing to the OTA process.
Rooting on its own does nothing to the OTA process. If you've kept a custom recovery, the OTA will not install automatically. The custom recovery does give you the option to flash it manually if you'd like, and keep the custom recovery. If you've changed/removed any system files or flashed a different radio, that will prevent the OTA from applying both automatically and manually. If you've started to modify the device this much, you shouldn't be expecting OTAs to work (this is where a lot of "status 7" errors occur).
If you've rooted and returned to a stock recovery, you can let the OTA automatically install, but you will lose root. It takes ~5min to root again, no big deal. You can also try one of the popular apps that "saves" root while you OTA, like OTA Rootkeeper.
Also pls tell me if you have got your OTA yet or not ...
Click to expand...
Click to collapse
Just because a couple dozen people on a forum have gotten the OTA doesn't mean that you should have gotten it already. Its a tad frustrating, but the OTA has a staggered roll out. It doesn't depend on your location or carrier (assuming you've got takju or yakju firmware from Google), and will get to all devices eventually.
If you'd simply point your browser to the general forum, you'll already see several threads talking about the 4.1.2 update.

Got my OTA update
I got my OTA update yesternight ...

Not getting OTA 4.2.1 Update

I recently got my galaxy nexus and it came with 4.1.1 installed and when I go to check for updates it says that I'm running the latest version. Help? Is there any way to push the update? I don't want to flash a custom ROM yet.

Depends on you're carrier. Nothing you can really do. Could be next week, could be next year (Verizon). I know you don't want to root but by the time you're carrier pushes any form of 4.2 we will all be on whatever is next and new anyways.

AustinsGalaxy said:
I recently got my galaxy nexus and it came with 4.1.1 installed and when I go to check for updates it says that I'm running the latest version. Help? Is there any way to push the update? I don't want to flash a custom ROM yet.
Click to expand...
Click to collapse
It depends upon your carrier..Your carrier(Sprint,Verizon,Samsung) decides when to push the ota.For ex-Takju gets the latest update first and then to yakju..
To get 4.2.1(currently latest) you should unlock bootloader in order to flash custom roms and enjoy 4.2.1:good:

That's the thing I have the yakju and my brother has the takju, they are both factory unlocked and they are both not getting the update. I had another galaxy nexus about a month ago and it got the update immediately, someone let me know if you're not getting the update either.

clear the google services framework and then check for the update.

Thanks, I've already tried that but no luck. Any more tips like that? The only thing that I can think of is that Google took off there factory image for download...?

try what i said before, but on wifi. just to be sure... unless you were already on wifi.
the next thing you could do is just flash the factory images without flashing userdata.. that should work without any problems.

Still no luck, could it be that my CID is on fido even though it's a factory unlocked unit? Is there any way to remove or get around CID limitations.

be sure that your Nexus I9250 is not rooted and have stock recovery and the bootloader is locked (not necessary but in case...) in order to receive update. if so, go to app. clear data and force stop "google service framework" then go to setting---->about phone and click on update. repeat these steps many time until you receive the ota update

Unfortunately I've already tried that too and still no luck .

AustinsGalaxy said:
Unfortunately I've already tried that too and still no luck .
Click to expand...
Click to collapse
do u have a superuser application in the drawer??
any way u can unlock bootlaoder and flash factory image of 4.2.1 yakju or takju link