Hi XDA,
I'm new to Android (first Android phone), and have never done any unlocking/rooting/etc. I've been working in iOS-land for 4 years, but wanted to try something new and refreshing.
I'm trying to figure out why my TELUS GSM Galaxy Nexus is stuck on 4.0.1? If my searching/reading is correct, it sounds as though the factory build they put on isn't eligible (yet) for the update, so you have to put on a different ROM entirely? (the yaku...something).
I thought the updates were pushed out by Google, not the carrier (e.g. TELUS/Rogers/Fido/etc). Why is everyone else running 4.0.2 or later (I know CDMA is even farther ahead) and I'm stuck at 4.0.1? And if CDMA is all the way up at 4.0.4, why isn't GSM? Wouldn't the people implementing bug fixes, etc, be updating for both platforms simultaneously?
I was oping factory updates would come quicker? I never wrecked any of my iOS devices (came pretty close, but eventually mastered DFU mode, pwning, and worst case scenario, rolling back to stock iOS 4 or 5). If I brick my Nexus though, I'm going to be in a world of hurt.
jasphair said:
Hi XDA,
I'm new to Android (first Android phone), and have never done any unlocking/rooting/etc. I've been working in iOS-land for 4 years, but wanted to try something new and refreshing.
I'm trying to figure out why my TELUS GSM Galaxy Nexus is stuck on 4.0.1? If my searching/reading is correct, it sounds as though the factory build they put on isn't eligible (yet) for the update, so you have to put on a different ROM entirely? (the yaku...something).
I thought the updates were pushed out by Google, not the carrier (e.g. TELUS/Rogers/Fido/etc). Why is everyone else running 4.0.2 or later (I know CDMA is even farther ahead) and I'm stuck at 4.0.1? And if CDMA is all the way up at 4.0.4, why isn't GSM? Wouldn't the people implementing bug fixes, etc, be updating for both platforms simultaneously?
I was oping factory updates would come quicker? I never wrecked any of my iOS devices (came pretty close, but eventually mastered DFU mode, pwning, and worst case scenario, rolling back to stock iOS 4 or 5). If I brick my Nexus though, I'm going to be in a world of hurt.
Click to expand...
Click to collapse
Id like to know this too. Im on Rogers and have the Rogers version of the GNEX and it too came with v4.0.1
I have since rooted, etc and flashed a custom 4.0.3 ROM (see signature for info) but I seem to be having some network issues (bug in 4.0.3 custom ROMS) which may FORCE me to go back to stock and if I do then Id definitely like to know WHY we have not received any Official updates to our devices as of yet...
Your updates are coming from google not your carriers. However Samsung is in charge of ensuring the update works in certain regions hence the delay.
Sent from my Galaxy Nexus using XDA App
yiannisthegreek said:
Id like to know this too. Im on Rogers and have the Rogers version of the GNEX and it too came with v4.0.1
I have since rooted, etc and flashed a custom 4.0.3 ROM (see signature for info) but I seem to be having some network issues (bug in 4.0.3 custom ROMS) which may FORCE me to go back to stock and if I do then Id definitely like to know WHY we have not received any Official updates to our devices as of yet...
Click to expand...
Click to collapse
Google hates Canada.
For what it's worth when I got this phone from Virgin Mobile just before Xmas it was yakjuyx or whatever and 4.0.1. Minutes after turning it on it upgraded OTA to 4.0.2 so they are pushing updates in Canada, even 'Samsung controlled' builds.
That said it's not a concern after installing a custom yakju ROM already at 4.0.3. So either you wait patiently for OTAs that may or may not come or take control of your own device ;-). Remember, it can all be put back where it was!
rAy
Sent from my Galaxy Nexus using xda premium
ray2jerry said:
For what it's worth when I got this phone from Virgin Mobile just before Xmas it was yakjuyx or whatever and 4.0.1. Minutes after turning it on it upgraded OTA to 4.0.2 so they are pushing updates in Canada, even 'Samsung controlled' builds.
That said it's not a concern after installing a custom yakju ROM already at 4.0.3. So either you wait patiently for OTAs that may or may not come or take control of your own device ;-). Remember, it can all be put back where it was!
rAy
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks for the info but as I mentioned, I am already running a Custom 4.0.3 ROM but I seem to be having signal drop issues with it so I may have to flash something else to fix that as I have read that these signal drop issues are 4.0.3 AOSP ROM related...
ray2jerry said:
For what it's worth when I got this phone from Virgin Mobile just before Xmas it was yakjuyx or whatever and 4.0.1. Minutes after turning it on it upgraded OTA to 4.0.2 so they are pushing updates in Canada, even 'Samsung controlled' builds.
That said it's not a concern after installing a custom yakju ROM already at 4.0.3. So either you wait patiently for OTAs that may or may not come or take control of your own device ;-). Remember, it can all be put back where it was!
rAy
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That can't be right. The only OTA update that went out for yakjuux was the volume fix update. I've never heard of anyone getting 4.0.2 that had yakjuux. The first batch of phones that came out in December received that volume update but it stayed 4.0.1. Any phones bought recently already came with the volume update applied.
Related
I went to check my email on my GSM Galaxy Nexus today and got a notification that there's *finally* an update available. This is the first since I've owned the device (two months now?). I wanted to track and see where it's coming from. I want to see if I can get the IP and tell whether the update is from Google's server or Samsung's on the yakjuxw build. But I have no idea how to do this. Anyone with experience willing to help me out? I'll post the results here, as well. Should bring some clarity to the different builds.
I won't be able to reply or check back until after work later today, but really want to find out before applying the update. Thanks.
Sent from my Galaxy Nexus using XDA App
First of all, you have to install it and see if the build number has changed in order to confirm that the update is a system update and not something else.
Have you updated it yet? Did it update to 4.0.2 or 4.0.3?
It says in your signature that you still have ITL41D, so it might just be the update to ITL41F that jsut fixes the volume bug.
Got the first update!
Hi, first, let me tell you that english is not my main language.
Got the first update today, installed it. I am still on 4.0.1, but there were some changes. I moved from a GN yakjuxw I9250XWKK5_ITL41D to ITL41F.I9250XWKK9.
Two questions:
1- Do you know what's changed?
2- I do not have the improve facial recognition feature. Is it only to the 4.0.2 update?
Tiga Jr.
tigajr said:
Hi, first, let me tell you that english is not my main language.
Got the first update today, installed it. I am still on 4.0.1, but there were some changes. I moved from a GN yakjuxw I9250XWKK5_ITL41D to ITL41F.I9250XWKK9.
Two questions:
1- Do you know what's changed?
2- I do not have the improve facial recognition feature. Is it only to the 4.0.2 update?
Tiga Jr.
Click to expand...
Click to collapse
Your update was for the volume control problem.
You probably need to factory reset your phone to get face unlock to show.
Sent from my Galaxy Nexus using XDA App
Hi, thank you for the answer. I already have the face unlock, but not the "improve face matching". What I want to know is if this feature is only for the 4.0.2 update.
I was investigating and found out that the 4.0.2 was pulled from the Google binaries (can not put links yet, because I am new here). There, we can find only two versions: 4.0.1 and 4.0.3.
Maybe, our next update we'll be the 4.0.3. Hope It will be the one that will put everybody in the same boat.
Tiga Jr.
obs. english is not my main language
kangxi said:
You probably need to factory reset your phone to get face unlock to show.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
iconicpaul said:
First of all, you have to install it and see if the build number has changed in order to confirm that the update is a system update and not something else.
Click to expand...
Click to collapse
Right, but I don't care so much about what the update is. I want to know where it's coming from.
Sent from my Galaxy Nexus using XDA App
I recieved the update this morning as well and it said it was coming from Samsung.
i also got the update this morning. phone is still 4.0.1 and build number is now ITL41F.xxxxxxxxxx
i wonder why my phone is at the end of the queue :-(
and why the f### is my wife's Nexus S running 4.0.3 and my GNex 4.0.1 ?!?!?!?!?!?
mvorbrodt said:
i wonder why my phone is at the end of the queue :-(
and why the f### is my wife's Nexus S running 4.0.3 and my GNex 4.0.1 ?!?!?!?!?!?
Click to expand...
Click to collapse
And I wonder why people don't stop crying and start enjoying their phone
If you want the latest update just install the latest image from http://code.google.com/android/nexus/images.html
It's amazing how a 0.01 update can confuse people...
Lemim0uth said:
And I wonder why people don't stop crying and start enjoying their phone
If you want the latest update just install the latest image from http://code.google.com/android/nexus/images.html
It's amazing how a 0.01 update can confuse people...
Click to expand...
Click to collapse
and I wonder why, after so many years of mod banning, there are still trolls like you on the forums
Welcome to the club, I was wondering the same thing about you
Seriously, why don't you install the latest factory image from http://code.google.com/android/nexus/images.html and stop whining ?
I think XDA is NOT the right place to cry on why you don't get the xx.yy.zz update
2 months? The phone has been out 5 weeks.
Sent from my Galaxy Nexus using xda premium
a lot of us that bought the unlocked gnexus got the "yakjuxw" device not the "yakju" device so we CAN'T update!!
I also got a notice for update and clicked update ... still on 4.0.1 but didn't see if it was from samsung or google!
skarenboo said:
a lot of us that bought the unlocked gnexus got the "yakjuxw" device not the "yakju" device so we CAN'T update!!
I also got a notice for update and clicked update ... still on 4.0.1 but didn't see if it was from samsung or google!
Click to expand...
Click to collapse
You can update no matter what. Just because you have a yakjuxw doesn't mean you'll be stuck on 4.0.1 forever. This has been blown way out of proportion it is stupid.
Sent from my Galaxy Nexus using xda premium
Yes, I know i will get an udpate... just MUCH SLOWER since SAMSUNG is known for releasing their updates uber slow!!
isn't one of the biggest perks owning a nexus = FAST UPDATES, FIRST TO UPDATE, NO BLOATWARE... so owning a SAMSUNG update device kinda defeat the purpose... we want GOOGLE to update us
Guys, if you are getting the OTA updates for yakjuxw, please post the update URL if you don't mind, so that others on yakjuxw who have yet to receive it, can flash it. Thanks.
skarenboo said:
Yes, I know i will get an udpate... just MUCH SLOWER since SAMSUNG is known for releasing their updates uber slow!!
isn't one of the biggest perks owning a nexus = FAST UPDATES, FIRST TO UPDATE, NO BLOATWARE... so owning a SAMSUNG update device kinda defeat the purpose... we want GOOGLE to update us
Click to expand...
Click to collapse
You're just not getting it, do you ? All updates come from Google, and even mysid for Verizon CDMA still gets tested by Verizon before rollout. The same applies to yakju and yakjuxw, etc. They are tested by Samsung/carriers, then updated. Does it really matter if you get the update 1 week later than other versions of the phone ? It's not like you're waiting 2 months. Sheesh....
lambda30 said:
You're just not getting it, do you ? All updates come from Google, and even mysid for Verizon CDMA still gets tested by Verizon before rollout. The same applies to yakju and yakjuxw, etc. They are tested by Samsung/carriers, then updated. Does it really matter if you get the update 1 week later than other versions of the phone ? It's not like you're waiting 2 months. Sheesh....
Click to expand...
Click to collapse
I'm pretty sure you're wrong there. Google is only handling the builds done by google (yakju, and mysid), samsung seems to be handling all the regional builds. Every variant of yakju__ is compiled by samsung.
And yeah, it's been forever since the volume bug was discovered. And the update should have gone out a lot sooner then it has for the variant builds.
edit: I stand corrected
So I just bought the GSM version of the Galaxy Nexus. It is yakju and I am using it with AT&T. No matter how many times I've tried I cannot get the phone to do an OTA update to at least 4.0.2, let alone 4.0.4. So I have a couple questions, keeping in mind that I am not particularly interested in rooting and would rather just do an OTA update.
1. Will the 4.0.2 update eventually come through if I wait? I don't mind waiting, but I don't want to wait indefinitely without making any progress.
2. If I do want to or need to do a manual update, can I go straight from 4.0.1 to 4.0.4?
Like I said, I would prefer to wait for the OTA update as I'm having no issues with 4.0.1 right now.
On a completely unrelated note, I have 14 days to return this phone. If you were me, would you return it and wait for the One X. I like the idea of having a raw android Google phone, but the One X seems attractive.
I think you should get an iphone.
iphone. helping computer illiteracy become popular since 2007.
I received my Nexus about a week ago. Within 5 minutes of turning it on I received the 4.02 OTA update. 10 minutes later I was rooted and running CM9 so I can't say if I would have received the 4.04 OTA update.
Sent from my Galaxy Nexus using xda premium
get stock images and flash to 4.0.4.
search the forums on how to do that.
rsawlani said:
Like I said, I would prefer to wait for the OTA update as I'm having no issues with 4.0.1 right now.
Click to expand...
Click to collapse
Then just wait for the OTAs.
On a completely unrelated note, I have 14 days to return this phone. If you were me, would you return it and wait for the One X. I like the idea of having a raw android Google phone, but the One X seems attractive.
Click to expand...
Click to collapse
There are already lots of spammy nerd bashing threads on this topic. No one can make this decision for you.
You have a few options....
1. Download Factory images for 4.0.4 from Google and use Galaxy Nexus Toolkit to flash (you will lose all your data and pictures, videos, music)
2. Root your phone (you'll still lose your data because you have to unlock your bootloader)
3. Wait for the 4.0.2 update than the 4.0.4 update
Your choice
When you get the HTC One X you gonna be saying how much you wish you had AOSP
Sent from my GT-P7510 using xda premium
YoungAceAtlanta said:
You have a few options....
1. Download Factory images for 4.0.4 from Google and use Galaxy Nexus Toolkit to flash (you will lose all your data and pictures, videos, music)
2. Root your phone (you'll still lose your data because you have to unlock your bootloader)
3. Wait for the 4.0.2 update than the 4.0.4 update
Your choice
When you get the HTC One X you gonna be saying how much you wish you had AOSP
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Or when Android 5.0, "when will One X be getting Android 5.0?!"
Same Here
I guess were both on the same boat Except i am on Tmobile. As soon as i unboxed and setup my Gnex this past friday i was expecting an OTA update to 4.0.4. But appearantly that wasn't the case as i am still stuck on 4.0.1 two days later. I am really hoping i get that OTA soon...there is no way i am rooting ever again. My last phone which was a Samsung Vibrant had a custom ICS rom...everything was well until i was greeted by the deadly "Encryption Unsuccessful" screen not knowing what to do i hit reset phone. 1 min later my phones only use was as a door stop.
I know this may sound kind of silly but maybe we haven't received our updates because its the weekend . Im waiting till monday to see if i get the OTA update. Hopefully it arrives soon.
Merio90 said:
I guess were both on the same boat Except i am on Tmobile. As soon as i unboxed and setup my Gnex this past friday i was expecting an OTA update to 4.0.4. But appearantly that wasn't the case as i am still stuck on 4.0.1 two days later. I am really hoping i get that OTA soon...there is no way i am rooting ever again. My last phone which was a Samsung Vibrant had a custom ICS rom...everything was well until i was greeted by the deadly "Encryption Unsuccessful" screen not knowing what to do i hit reset phone. 1 min later my phones only use was as a door stop.
I know this may sound kind of silly but maybe we haven't received our updates because its the weekend . Im waiting till monday to see if i get the OTA update. Hopefully it arrives soon.
Click to expand...
Click to collapse
Most OTAs roll out in groups. Well at least from the last time I did a OTA .. I guess thats how they still work. Only so many users get them at a time. Not everyone who has a gnex get it at once
Sent from my Galaxy Nexus using xda premium
YoungAceAtlanta said:
Most OTAs roll out in groups. Well at least from the last time I did a OTA .. I guess thats how they still work. Only so many users get them at a time. Not everyone who has a gnex get it at once
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Now that I see other people having this problem, I think OTA updates for 100% stock Android 4.0.1 Samsung i9250 Galaxy Nexus are just not happening at all for now... (verbiage/garbiage deleted
As for my Nexus One(s)... (I'll just say I never saw this happen)
EDIT:
At about 8pm MDT (GMT-06:00) in the US, my i9250 finally updated from 4.0.2 to 4.0.4. I consider this an important validation of the integrity of my device. Earlier today I flashed 4.0.2 but still had to wait.
So clearly there was a period of days (March 30 to April 2 at least) that OTA updates where not happening for the i9250. This was alarming because I've rolled my i9250 back to 100% stock Android 4.0.1 several times after playing with different ROMs. Each time it quickly updated to 4.0.2. This time it took a few days. For a while I was worried my phone had a problem.
I just rolled back to a stock ROM 4 days ago.
But did only get 1 OTA update immediately after first boot. The one from ITL41D to ITL41F (4.0.1).
No OTA to 4.0.2 or even 4.0.4 yet. (All imgs are stock ITL41F with locked bootloader of course)
Have had my nexus now for several months. Its a uk simfree direct from amazon.co.uk. yakju, gsm, Its stock, un rooted.
Originally it was running 4.0.2 and ran perfectly. But since the it picked up the 4.0.4 ota update (just after the release) i get freezing and random reboot issues while its in standby (never happens when i am using it). After reboot there is often a hole in my battery log (see attached pic).
The freezing is a big issue has i have to take out the battery to bring it back to life.
If this is a common issue then i will stick with it, but if not them i will have to return it. I don't want to root or load an alternative rom because i don't think i should have to just to get a reliable phone.
I have removed most of my apps to see if that helps, but i didn't have that many anyway and most of those are google own.
I would appreciate thoughts!
Sent from my Galaxy Nexus using xda premium
i have a samsung galaxy nexux with 4.0.4, too and it works perfect. it sounds like a hardware defect for me..
No other opinions?
Sent from my Galaxy Nexus using xda premium
Easiest way to find out if it is hardware related, is to start from scratch: flash the factory image and see if you still have the freezing. If not, it is some app or some setting you changed. If you still have the freezing, it's probably hardware related.
Well since i had jelly bean ota, no freezing or reboots :thumbup:
/touchwood
Sent from my Galaxy Nexus using xda premium
I feel better after finding this thread--at least now I know my experience is not totally unique.
The same thing happened to my wife's Galaxy Nexus, which came as a yakjuwx 4.0.2. After applying the OTA update to 4.0.4, the phone will invariably reboot by itself within 30-40s in standby. The Samsung service centre (in Singapore) even took the trouble to change the motherboard (so they claimed) but that didn't resolve issue. But since they only have the 4.0.2 ROM on hand and will always flash the device back to that, and since the phone does not exhibit the problem in 4.0.2, the problem is solved as far as they are concerned. After discussing a bit with one of their engineers, he even advised me to hold off updating to 4.0.4.
The amazing thing is that the same pattern of problems persist even if I flash the phone to the Google factory images (yakju). The phone will be fine in yakju 4.0.2, but not after the OTA update to either 4.0.4, or 4.1.1. This suggests that there is something hardware related involved, but there's no way for me to prove it.
Currently, the phone is running Google factory image yakju 4.0.2 without problems. To stop the OTA notification from shoping, I've rooted the device, used Root Explorer to (1) delete the OTA update file in /cache and (2) renamed system/etc/security/otacerts.zip to otacerts.zip.bak. After one restart, I said "yes" to the update notification, which then immediate shows that the phone is up to date, and it has not been bothering since. Since my wife is not big on the 'latest and biggest' upgrades, this seems an acceptable solution for her.
This obviously happens only to some Galaxy Nexus. My own device, an identical yakjuwx 4.0.2 model, updated OTA to 4.0.4 without any issues. It was subsequently upgraded unofficially to yajku 4.1.1 and ran well for a week. But something else happened--it heats up while simply refusing to charge--and it's also returned for servicing. Sad to say this but I'm slightly regretting going with the two Nexus...
(*Incidentally, for all their inability to solve the problem at a more fundamental level, and more strangely, their lack of the facility to install the yakjuwx 4.0.4 update themselves, the Samsung service centre people in Singapore have been very friendly and helpful. They were also very lenient with the warranty--I didn't have a proper receipt as the phone was purchased second hand but they accepted it on the basis of the serial number. Furthermore, they didn't make any comment about the fact that the bootloader was unlocked. It seems their policy to simply flash any phone given to them for servicing back to factory yakjuwx 4.0.2 no questions asked, before proceeding with further tests. I was warned, of course, that any phones left with them will be wiped.)
I had no issues with 4.0.2, it was only 4.0.4 that seemed to be a problem for my device.
Uptime now 275 hours on 4.1.1 :thumbup:
Sent from my Galaxy Nexus using xda premium
Hey everybody. So I've had this device since December and when the 4.0.4 update was released for VZW users, I was not able to update. Upon further research, I found out that there was a mistake in the factory and the recovery image was not flashed, meaning I could not update software or perform factory resets. I brought it into Verizon and got a replacement, but I got a refurb with terrible signal issues. I went back to Verizon and they told me I could get a new phone. I am now eligible to get a new phone for free as a replacement. I purposely kept the Gnex until now so I could swap it out for the SIII that is releasing tomorrow. I actually fixed my Gnex on my own by flashing stock images of the 4.0.4 manually. So the question is, should I revert my phone back to 4.0.2 and leave out the recovery image when flashing in order to get the SIII, or keep my Gnex which is now working perfectly fine?
jttate04 said:
Hey everybody. So I've had this device since December and when the 4.0.4 update was released for VZW users, I was not able to update. Upon further research, I found out that there was a mistake in the factory and the recovery image was not flashed, meaning I could not update software or perform factory resets. I brought it into Verizon and got a replacement, but I got a refurb with terrible signal issues. I went back to Verizon and they told me I could get a new phone. I am now eligible to get a new phone for free as a replacement. I purposely kept the Gnex until now so I could swap it out for the SIII that is releasing tomorrow. I actually fixed my Gnex on my own by flashing stock images of the 4.0.4 manually. So the question is, should I revert my phone back to 4.0.2 and leave out the recovery image when flashing in order to get the SIII, or keep my Gnex which is now working perfectly fine?
Click to expand...
Click to collapse
Keep the gnex and flash jellybean or cm9/aokp
Sent from my Galaxy Nexus using xda premium
If you want the extra RAM and locked bootloader, take it back and get the SIII.
If you want a phone with 4.1.1 today keep the Nexus, go to development section and flash jellybean already
Really wish people would grow a pair and just choose the device that they want, rather than asking a bunch of strangers that know nothing about them.
martonikaj said:
Really wish people would grow a pair and just choose the device that they want, rather than asking a bunch of strangers that know nothing about them.
Click to expand...
Click to collapse
It's perfectly valid for someone to seek the opinions of others to help them in their decision.
Do mods matter to you
If you want to be able to easily load mods to your phone keep the Galaxy Nexus. If you want a painless, but Verizon-controlled environment get the SIII. If I was in your position I'd keep the Gnex, but your priorities may be different.
It really depends on what you're going to do with your phone. If you go the GS3 route, just be aware that given the current situation with the locked bootloader, your ability to customize the phone will be compromised, until devs really find an effective way to bypass the bootloader. There is the Developer Edition of the Verizon Galaxy Nexus, but that seems to be only available through Samsung and not Verizon.
At least by sticking with the Nexus, you have access to all the available custom roms now, as well as JB and so forth.
Sent from my Nook Color using Tapatalk
CKTurbo128 said:
It really depends on what you're going to do with your phone. If you go the GS3 route, just be aware that given the current situation with the locked bootloader, your ability to customize the phone will be compromised, until devs really find an effective way to bypass the bootloader. There is the Developer Edition of the Verizon Galaxy Nexus, but that seems to be only available through Samsung and not Verizon.
At least by sticking with the Nexus, you have access to all the available custom roms now, as well as JB and so forth.
Sent from my Nook Color using Tapatalk
Click to expand...
Click to collapse
Don't forget the wonderful gift of touchwiz
Has Google released the links for JellyBean for LTE Devices yet? I'm not using a GSM
jttate04 said:
Has Google released the links for JellyBean for LTE Devices yet? I'm not using a GSM
Click to expand...
Click to collapse
No. There's no Verizon or Sprint OTAs yet. Source is out for GSM and Verizon though.
I'd get the GS3. If you find out you made the wrong choice you can sell the GS3 and re-buy a Nexus and make $.
You fixed terrible signal issues by flashing the phone? That's weird as signal issues have been reported as hardware related all over this forum.
But as its now fixed and working for you, I'd certainly keep it..There's a reason why you bought it in the first place, since its working why not keep it and save your upgrade.
For me, after having the freedom of a unlocked bootloader I'm not sure I can ever own a non-nexus device again!
title says it all, when does imm76k gsm model get the jb ota? i know you dunno the day but you know do i have to wait days weeks or months?
Go to Google Maps>settings>about. what does it say under "Device" ?
Android-samsung-maguro Galaxy Nexus
Samsung yakjuxw
Sent from my Galaxy Nexus using xda premium
Based on past history probably months. Or you can switch to yakju/takju.
Sent from my Galaxy Nexus using xda premium
Akizella said:
Android-samsung-maguro Galaxy Nexus
Samsung yakjuxw
Click to expand...
Click to collapse
You won't get it for a while.
Rip the bandaid off (so to speak), and switch to yakju or takju, and get updates from Google from here on out. Stop waiting for Samsung yakju** updates.
I had yakjuxw originally on my Nexus (4.0.1 and then updated it to 4.0.2) I didn't want to wait 4.0.4 update and at then i flashed Jelly Bean "takju" and day or few days later yakjuxw got IMM76K update for ICL53F.. for my Galaxy Nexus the "takju" builds are much better than "yakju" build so if you want jelly bean then flash jb-takju.zip via CWM, then LC03 bootloader via fastboot and XXLF1 radio via fastboot and then wait OTA update and then you can update it to 4.1.1 "takju" (it's much better than yakjuxw/yakju builds)
So I recommend the "takju" Jelly Bean because it takes maybe half year to get Jelly Bean update to yakjuxw if yakjuxw build even gets the JB update..
Not that I mind flashing other builds or rooting personally, I did it a long time ago, but it seems like Google/Samsung don't really care about variants like the yakjuxw (the model we get in Scandinavia). These models have been left in a grey area with very slow updates, if any at all. And with little or no info about what level of support to expect. It seems the OTA update process has been as slow as on UI branded phones.
This simply does not live up to what people expect from the Nexus brand and I've seen a lot of disappointed users here in Denmark. Many people I know of, bought the GNex to get stock Google UI and fast updates without having to modify anything.
volapyk said:
Not that I mind flashing other builds or rooting personally, I did it a long time ago, but it seems like Google/Samsung don't really care about variants like the yakjuxw (the model we get in Scandinavia). These models have been left in a grey area with very slow updates, if any at all. And with little or no info about what support to expect. It seems the official update process has been as slow as on ui branded phones. This simply does not live up to the Nexus brand and I've seen a lot of disappointed users here in Denmark. Many people I know of, bought the GNex to get stock Google UI and fast updates without having to modify anything.
Click to expand...
Click to collapse
Yes its quite unfortunate and you gotta hope that Google will work to make every GSM nexus on the same build for the next time around.
Fortunately there's a quick fix for this that will put your phone on the right update path and let you get OTAs ASAP from now on. Doesn't require any hacking or unofficial methods. Just flash to stock takju and let it go from there. Google provides the method and the files to do it. Sucks that it comes down to that, but at least there is a way to do it.
martonikaj said:
Yes its quite unfortunate and you gotta hope that Google will work to make every GSM nexus on the same build for the next time around.
Fortunately there's a quick fix for this that will put your phone on the right update path and let you get OTAs ASAP from now on. Doesn't require any hacking or unofficial methods. Just flash to stock takju and let it go from there. Google provides the method and the files to do it. Sucks that it comes down to that, but at least there is a way to do it.
Click to expand...
Click to collapse
I agree, and it's not that I mind doing it personally. I unlock and root my Nexus devices anyway, as I want to enjoy the full potential. But I see a lot of users who didn't expect having to change things at all on a Nexus device. Less tech savy people, people who are worried about breaking stuff, the warranty etc. It seems these people (e.g. European buyers) have been left with little support from Google and no support from Samsung.
Extremely disappointing to read the above posts. I bought my Nexus just a couple of days ago from Telenor Norway solely to get the OTA update to Jelly Bean, and find I have a 'Scandinavian version' which may not be updated for months.. hells bells!
Beats head against wall
Thanks for the info though guys
I
Cintra2 said:
Extremely disappointing to read the above posts. I bought my Nexus just a couple of days ago from Telenor Norway solely to get the OTA update to Jelly Bean, and find I have a 'Scandinavian version' which may not be updated for months.. hells bells!
Beats head against wall
Thanks for the info though guys
Click to expand...
Click to collapse
It may not be months. It could be tomorrow. No one knows. We only know it doesn't get the fast OTA's like the US models, yakju, takju...
AFAIK 4.04 isn't even out for yakjuxw yet (someone correct me if I'm wrong). It's been weeks since Google released it for yakju.
volapyk said:
I
It may not be months. It could be tomorrow. No one knows. We only know it doesn't get the fast OTA's like the US models, yakju, takju...
AFAIK 4.04 isn't even out for yakjuxw yet (someone correct me if I'm wrong). It's been weeks since Google released it for yakju.
Click to expand...
Click to collapse
Thanks volapyk, I hope you are right
Ref. 4.0.4, my Nexus was updated (twice) almost before I had finished installing apps on the phone, so I do have 4.0.4 at least..
Mvh
gf
Cintra2 said:
Thanks volapyk, I hope you are right
Ref. 4.0.4, my Nexus was updated (twice) almost before I had finished installing apps on the phone, so I do have 4.0.4 at least..
Mvh
gf
Click to expand...
Click to collapse
Thanks, great to know. I'm rooted, takju so I can't follow the progress of the yakjuxw OTA updates myself.
If you get the JB update on yakjuxw then don't forget to let us know.
Hello I bought today a brand new Nexus: it has ICS 4.0.4 yakju IMM76K firmware but unfortunately, no way to update to JB!! :crying:
It always says it 4.0.4 is up to date.
indago said:
Hello I bought today a brand new Nexus: it has ICS 4.0.4 yakju IMM76K firmware but unfortunately, no way to update to JB!! :crying:
It always says it 4.0.4 is up to date.
Click to expand...
Click to collapse
I believe there's a trick you can try. It involves clearing the cache of a Google framework file under settings/apps or something like that. It's been posted a lot, try searching for it.
volapyk said:
I
It may not be months. It could be tomorrow. No one knows. We only know it doesn't get the fast OTA's like the US models, yakju, takju...
AFAIK 4.04 isn't even out for yakjuxw yet (someone correct me if I'm wrong). It's been weeks since Google released it for yakju.
Click to expand...
Click to collapse
Hey volapyk.
Im a danish user as well and i just installed yakju yesterday even though i have waited soo long for the 4.1 OTA update. So far i havnt encountered any problems.
Frankly i was pissed when i heard that Samsung was in charge of the OTA on my phone. I almost returned the phone back to the dealer.
But im now running yakju and everything is very simple and easy to install. Look under Galaxy Nexus Q&A there is a simple guide to flash.
Cheers
---------- Post added at 09:53 AM ---------- Previous post was at 09:46 AM ----------
volapyk said:
I believe there's a trick you can try. It involves clearing the cache of a Google framework file under settings/apps or something like that. It's been posted a lot, try searching for it.
Click to expand...
Click to collapse
This trick didnt work for me - on yakjuxw :-/
Hi, I had the same issue, I tried forcing the update by clearing the Google Services Framework many times and this never worked for me. I came across this thread and flashed my phone to Yakju then I received the JB update.
http://forum.xda-developers.com/showthread.php?t=1626895
Sent from my Galaxy Nexus using xda app-developers app
NINE stiapch
volapyk said:
I believe there's a trick you can try. It involves clearing the cache of a Google framework file under settings/apps or something like that. It's been posted a lot, try searching for it.
Click to expand...
Click to collapse
Yes I read of this trick and tried several times already but no way ;-(
Googling around, I seems that, although pure yakju, ALL IMM76K devices are NOT being updated (while IMM76I are).
volapyk said:
I
It may not be months. It could be tomorrow. No one knows. We only know it doesn't get the fast OTA's like the US models, yakju, takju...
AFAIK 4.04 isn't even out for yakjuxw yet (someone correct me if I'm wrong). It's been weeks since Google released it for yakju.
Click to expand...
Click to collapse
Is that just the OTA update?
Was looking at factory images today and only JB is for the Nexus7
Where did you get your phone in Norway?
Cintra2 said:
Extremely disappointing to read the above posts. I bought my Nexus just a couple of days ago from Telenor Norway solely to get the OTA update to Jelly Bean, and find I have a 'Scandinavian version' which may not be updated for months.. hells bells!
Beats head against wall
Thanks for the info though guys
Click to expand...
Click to collapse
I can't find the Nexus Galaxy anywhere on the Telenor Web Site. I'm in Stavanger. Any ideas where I might find one?