[GUIDE] Galaxy Nexus Firmware Guide: Variations, Who Updates What, etc. - Samsung Galaxy Nexus
With the Galaxy Nexus, there are a LOT of different firmware variants, most of which are updated by Samsung, not Google. This guide attempts to sort all of this out for the beginner and help you make sense of it all.
WHAT IS ALL THIS TALK ABOUT FIRMWARE VARIATIONS?
With every Nexus phone, there has been a "master" firmware, plus other localized firmware variants for certain regions or carriers. Sometimes these variants will contain language packs, additional ringtones, slightly different baseband (radio) firmware to make it work better for a particular carrier's network, etc.
In the case of the Nexus S, Google maintained the master and all the local variants. On the Nexus One and the Xoom, Google only maintained the master firmware while carriers and/or OEMs maintained the local variants. In the case of the Galaxy Nexus, there are three Google-maintained master firmware variants, and many more Samsung-maintained local variants.
WHAT ARE THE DIFFERENT VARIANTS AND WHAT DO THEY MEAN?
Below is a definitive list of all known firmware variants for the Galaxy Nexus, and what models they shipped on:
GSM/HSPA+ Models
takju - USA region- and carrier-independent firmware released on models sold in the USA through the Google Play Store
yakju - International region- and carrier-independent firmware released on models sold throughout western Europe.
yakjudv - Variant for Australia
yakjujp - Variant for the Middle East
yakjujt - Variant for Turkey
yakjukr - Variant for South Korea
yakjusc - Variant for Japan
yakjuux - Variant for Canada
yakjuvs - Variant for Brazil
yakjuxe - Variant for Russia and the former Eastern Bloc
yakjuxw - Variant for certain carriers in Western Europe
yakjuzs - Variant for China and Hong Kong
CDMA/LTE Models
mysid - Variant for Verizon in the USA
mysidspr - Variant for Sprint in the USA
HOW CAN I TELL WHICH FIRMWARE I HAVE ON MY DEVICE
Using any file manager app, go into your /system folder and open the file called "build.prop". Find the line that starts with ro.product.name. Whatever comes after the equals sign (=), that's the firmware you have.
WHICH FIRMWARE IS UPDATED BY GOOGLE AS OPPOSED TO SAMSUNG?
Google updates the following firmware variants:
takju
yakju
mysid
Every other variant is updated and maintained by Samsung.
SO YOU'RE TELLING ME THAT THE SPRINT GALAXY NEXUS GETS UPDATES FROM SAMSUNG AND NOT GOOGLE?!?!
Yep.
WHY DOES IT MATTER WHERE MY UPDATES COME FROM ANYWAY?
For all practical purposes, it probably doesn't. However, this becomes an issue if you want timely updates. When Google drops a new OTA update for the Galaxy Nexus, they always announce it through official Android channels. When they announce a Galaxy Nexus OTA, they are only referring to devices running the firmware that they control.
This means that if you have a Sprint Galaxy Nexus, or a GSM model running one of the yakju(xx) firmware variants, your device is not included in the OTA rollout from Google. Your update will instead come from Samsung sometime in the future after they make whatever region- and/or carrier-specific changes they need to make for the firmware.
I HAVE A VERIZON GALAXY NEXUS. THE FIRMWARE IS UPDATED BY GOOGLE SO WHY DOES IT ALWAYS TAKE LONGER FOR UPDATES TO HIT MY DEVICE THAN THE GSM/HSPA+ DEVICE
Even though Google maintains and updates the mysid firmware on the Verizon Galaxy Nexus, Verizon must test and approve the updates before Google is allowed to roll them out. This introduces delays, sometimes lengthy ones. For instance, Android 4.0.4 began rolling out to the Galaxy Nexus GSM model on March 28, 2012. The Verizon device didn't get the update until two months later, on May 31, 2012 due to testing delays. That's not to say that all future OTAs will occur on a two month delay, but it's best to be prepared for the worst.
WHAT'S THIS I'VE HEARD ABOUT BEING ABLE TO FLASH YAKJU FIRMWARE ON A DEVICE RUNNING YAKJU(XX)? IF I DO THIS, WILL MY UPDATES COME FROM GOOGLE?
You can flash yakju firmware onto any Galaxy Nexus GSM device that's running a yakju(xx) variant. This is outside the scope of this guide, but instructions can be found here on XDA with a little searching. Once you're up and running on yakju, your updates will come from Google rather than Samsung.
DOES THE SAME THING GO FOR CDMA? COULD I FLASH THE VERIZON MYSID FIRMWARE TO MY SPRINT MODEL AND GET UPDATES FROM GOOGLE?
No, No, No and NO! If you tried this, you'd probably risk hard bricking your phone, and even if it did boot, you'd have no mobile data and probably wouldn't be able to make calls either.
WHAT IF I HAVE FIRMWARE-RELATED QUESTIONS THAT AREN'T ADDRESSED IN THIS GUIDE?
Post them here and I'm sure someone can answer it for you.
+1 Nice guide. Should get a sticky.
Thread stuck
FNM
Thanks! What does FNM mean? haha
Sent from my Galaxy Nexus using Tapatalk 2
oldblue910 said:
Thanks! What does FNM mean? haha
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Friendly Neighborhood Moderator I believe.
Also, gratz on the sticky. Excellent thread.
http://www.youtube.com/watch?v=mCnZqg1RgGA
Nice guide dude, you're gonna be thanked a lot.
I have a question, what hapens with my GN?
I just got it and It was originally Sprint, now its flashed to Iusacell, the CDMA carrier here in Mexico.
Where the hell are coming my updates from? D:
I'm not really worried, Im rooted runing stock 4.0.4, but if an important update comes, ill flash a rooted rom from here and be up to date.
But anyway I'm curious about that.
Damian8a said:
Nice guide dude, you're gonna be thanked a lot.
I have a question, what hapens with my GN?
I just got it and It was originally Sprint, now its flashed to Iusacell, the CDMA carrier here in Mexico.
Where the hell are coming my updates from? D:
I'm not really worried, Im rooted runing stock 4.0.4, but if an important update comes, ill flash a rooted rom from here and be up to date.
But anyway I'm curious about that.
Click to expand...
Click to collapse
It sounds like you're still running the stock mysidspr firmware that came on your Sprint device originally, you just have it running on the Mexican carrier. That means you'll get any update any other Sprint device gets, which would come from Samsung.
Sent from my Galaxy Nexus using Tapatalk 2
thanks for the info...
I have a hong kong version of the galaxy nexus...
from this post I understand updates are managed by samsung.
the only OTA update I got until now was from 4.0.1 to 4.0.2. never got anything else. this did not really bother me up until now that jellybean will probably roll out soon for google managed versions.
Is there some place where I can search to see if my version will ever get jelly bean at all? and if it wil than when?
thanks in advance!
Thank you very much wish to continue your work
Damian8a said:
Nice guide dude, you're gonna be thanked a lot.
I have a question, what hapens with my GN?
I just got it and It was originally Sprint, now its flashed to Iusacell, the CDMA carrier here in Mexico.
Where the hell are coming my updates from? D:
I'm not really worried, Im rooted runing stock 4.0.4, but if an important update comes, ill flash a rooted rom from here and be up to date.
But anyway I'm curious about that.
Click to expand...
Click to collapse
Hola!, oye yo tambien vivo en mexico y tengo iusacell
tuviste algun problema para configurarlo o activarlo con cdma iusa?
ya esta dada de alta el ESN?
saludos
Hi, I'm a little confused. Here in Brazil our Galaxy Nexus is called Galaxy X. It's basically the same phone, but we haven't recieved 4.0.4 update yet. We are stuck on 4.0.2.
How an I flash the yakju firmware on my device? I searched for tutorials here on XDA but I couldn't find anything conclusive.
MaKTaiL said:
Hi, I'm a little confused. Here in Brazil our Galaxy Nexus is called Galaxy X. It's basically the same phone, but we haven't recieved 4.0.4 update yet. We are stuck on 4.0.2.
How an I flash the yakju firmware on my device? I searched for tutorials here on XDA but I couldn't find anything conclusive.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1626895
This was exactly what I needed. Thanks! :victory:
Update Galaxy Nexus
Thanks for the great guide.
I recently got my Phone from the US i.e. Galaxy Nexus. It shows the Android version as 4.0.1. How can i update it to Jelly bean or be eligible for the update?
Best.
Prasad
pbhojak said:
Thanks for the great guide.
I recently got my Phone from the US i.e. Galaxy Nexus. It shows the Android version as 4.0.1. How can i update it to Jelly bean or be eligible for the update?
Best.
Prasad
Click to expand...
Click to collapse
Did you look at the link two posts above yours??
Sent from my Galaxy Nexus using Tapatalk 2
oldblue910 said:
With the Galaxy Nexus, there are a LOT of different firmware variants, most of which are updated by Samsung, not Google. This guide attempts to sort all of this out for the beginner and help you make sense of it all.
WHAT IS ALL THIS TALK ABOUT FIRMWARE VARIATIONS?
With every Nexus phone, there has been a "master" firmware, plus other localized firmware variants for certain regions or carriers. Sometimes these variants will contain language packs, additional ringtones, slightly different baseband (radio) firmware to make it work better for a particular carrier's network, etc.
In the case of the Nexus S, Google maintained the master and all the local variants. On the Nexus One and the Xoom, Google only maintained the master firmware while carriers and/or OEMs maintained the local variants. In the case of the Galaxy Nexus, there are three Google-maintained master firmware variants, and many more Samsung-maintained local variants.
WHAT ARE THE DIFFERENT VARIANTS AND WHAT DO THEY MEAN?
Below is a definitive list of all known firmware variants for the Galaxy Nexus, and what models they shipped on:
GSM/HSPA+ Models
takju - USA region- and carrier-independent firmware released on models sold in the USA through the Google Play Store
yakju - International region- and carrier-independent firmware released on models sold throughout western Europe.
yakjudv - Variant for Australia
yakjujp - Variant for the Middle East
yakjukr - Variant for South Korea
yakjusc - Variant for Japan
yakjuux - Variant for Canada
yakjuxe - Variant for Russia and the former Eastern Bloc
yakjuxw - Variant for certain carriers in Western Europe
yakjuzs - Variant for China and Hong Kong
CDMA/LTE Models
mysid - Variant for Verizon in the USA
mysidspr - Variant for Sprint in the USA
HOW CAN I TELL WHICH FIRMWARE I HAVE ON MY DEVICE
Using any file manager app, go into your /system folder and open the file called "build.prop". Find the line that starts with ro.product.name. Whatever comes after the equals sign (=), that's the firmware you have.
WHICH FIRMWARE IS UPDATED BY GOOGLE AS OPPOSED TO SAMSUNG?
Google updates the following firmware variants:
takju
yakju
mysid
Every other variant is updated and maintained by Samsung.
SO YOU'RE TELLING ME THAT THE SPRINT GALAXY NEXUS GETS UPDATES FROM SAMSUNG AND NOT GOOGLE?!?!
Yep.
WHY DOES IT MATTER WHERE MY UPDATES COME FROM ANYWAY?
For all practical purposes, it probably doesn't. However, this becomes an issue if you want timely updates. When Google drops a new OTA update for the Galaxy Nexus, they always announce it through official Android channels. When they announce a Galaxy Nexus OTA, they are only referring to devices running the firmware that they control.
This means that if you have a Sprint Galaxy Nexus, or a GSM model running one of the yakju(xx) firmware variants, your device is not included in the OTA rollout from Google. Your update will instead come from Samsung sometime in the future after they make whatever region- and/or carrier-specific changes they need to make for the firmware.
I HAVE A VERIZON GALAXY NEXUS. THE FIRMWARE IS UPDATED BY GOOGLE SO WHY DOES IT ALWAYS TAKE LONGER FOR UPDATES TO HIT MY DEVICE THAN THE GSM/HSPA+ DEVICE
Even though Google maintains and updates the mysid firmware on the Verizon Galaxy Nexus, Verizon must test and approve the updates before Google is allowed to roll them out. This introduces delays, sometimes lengthy ones. For instance, Android 4.0.4 began rolling out to the Galaxy Nexus GSM model on March 28, 2012. The Verizon device didn't get the update until two months later, on May 31, 2012 due to testing delays. That's not to say that all future OTAs will occur on a two month delay, but it's best to be prepared for the worst.
WHAT'S THIS I'VE HEARD ABOUT BEING ABLE TO FLASH YAKJU FIRMWARE ON A DEVICE RUNNING YAKJU(XX)? IF I DO THIS, WILL MY UPDATES COME FROM GOOGLE?
You can flash yakju firmware onto any Galaxy Nexus GSM device that's running a yakju(xx) variant. This is outside the scope of this guide, but instructions can be found here on XDA with a little searching. Once you're up and running on yakju, your updates will come from Google rather than Samsung.
DOES THE SAME THING GO FOR CDMA? COULD I FLASH THE VERIZON MYSID FIRMWARE TO MY SPRINT MODEL AND GET UPDATES FROM GOOGLE?
No, No, No and NO! If you tried this, you'd probably risk hard bricking your phone, and even if it did boot, you'd have no mobile data and probably wouldn't be able to make calls either.
WHAT IF I HAVE FIRMWARE-RELATED QUESTIONS THAT AREN'T ADDRESSED IN THIS GUIDE?
Post them here and I'm sure someone can answer it for you.
Click to expand...
Click to collapse
- I have question: If i flash yakju firmware on yakjuxx model, my GN change to yakju mode or not? Thank you for support.
Thanks in advance!
Hello there,
Sorry to bother you all; first post!
I saw the noob video, so I'll be quick.
I've figured out what version of Nexus I have finally through your guide (yakjuux for Canada), but what I'm trying to figure out is if my Canadian Nexus is a GSM, VZW....or the other one I can't remember.
If you could help me out with that, I'm sure I'll be able to find the rest of the info on my own.
Thanks so much in advance!
EDIT: My phone is under Virgin Mobile's network, if this helps any.
RyanMZ said:
Hello there,
Sorry to bother you all; first post!
I saw the noob video, so I'll be quick.
I've figured out what version of Nexus I have finally through your guide (yakjuux for Canada), but what I'm trying to figure out is if my Canadian Nexus is a GSM, VZW....or the other one I can't remember.
If you could help me out with that, I'm sure I'll be able to find the rest of the info on my own.
Thanks so much in advance!
EDIT: My phone is under Virgin Mobile's network, if this helps any.
Click to expand...
Click to collapse
Well, let's think about this for a minute: Sprint and Verizon do not operate in Canada, so... if you bought a Canadian phone, what version do you think it has to be?
Sent from my Galaxy Nexus using Tapatalk 2
Hello Efrant,
I have galaxy nexus with phone about as attach file, could you tell me about my phone model: yakju or yakjuxx. Thank you very much.
Related
Galaxy Nexus Not Finding Updates
Hi I purchased my Galaxy Nexus when it first launched back in November from Handtec, the current firmware on my device is version 4.0.2. But for some reason it does not get the notification for OTA updates. I understand from reading the forums that the current version is 4.0.4 and that was pushed over two weeks ago. My device has not gotten the notification to update, I tried the framework suggestion that was suggested on another thread but I got no result I also tried the "check in" code and had no luck. My current carrier is AT&T, is my Nexus defective? Can somebody please help? Thank you
MEGABYTEPR said: Hi I purchased my Galaxy Nexus when it first launched back in November from Handtec, the current firmware on my device is version 4.0.2. But for some reason it does not get the notification for OTA updates. I understand from reading the forums that the current version is 4.0.4 and that was pushed over two weeks ago. My device has not gotten the notification to update, I tried the framework suggestion that was suggested on another thread but I got no result I also tried the "check in" code and had no luck. My current carrier is AT&T, is my Nexus defective? Can somebody please help? Thank you Click to expand... Click to collapse If your phone is anything but yakju then your in for a wait. Also the 4.0.4 roll out has stopped until google fixes the signal issues some people have.
How can I identify if my phone is a yakju ?
MEGABYTEPR said: How can I identify if my phone is a yakju ? Click to expand... Click to collapse Dude please read a bit. This exact thread exists every single day of the last week. Check your version with this: https://play.google.com/store/apps/details?id=de.cbruegg.officialupdate But the thing is that even if it is "yakju" (updated by Google). The 4.0.4 update has been stopped because it causes radio-related signal drop issues for some users. They recently issued a small 4.0.4 "fix" for it. Once things are sorted out, presumably 4.0.2 users will get moved straight up to the latest 4.0.4.
[Q] Embarrassing noOb question!
I'm not new to Android, just knew to the Galaxy Nexus/Stock Android World. I ordered one from NewEgg before learning many are receiving unlocked DoCoMo units, not true factory unlocked i9250's. Made a bit nervous! Got it in yesterday and luckily the sticker in the battery cavity says i9250 and IMEI's match just fine. Once signed into the phone I received an OTA update to 4.0.2. However, the update said this was an update direct from Samsung, not Google? So my question is, is that normal or do I have a Samsung build and not the Google Yakju build? I'm honestly not sure how you know if you have Yakju or not. Here is what I have under "About Phone" Model Number Galaxy nexus Android version 4.0.2 Baseband version I9250XXKK6 Kernel version 3.0.8-gaaa2611 [email protected] #1 Build number ICL53F.I9250XWKL2 Thanks in advance!
Check your build.prop, that'll tell you if you have yakju or not
there is an app in the market to detect which device build u have GN Official Update Checker
Gforce083 said: I'm honestly not sure how you know if you have Yakju or not. ! Click to expand... Click to collapse Install GN Official Update Checker or Android System Info. You will be able to check it.
Thanks for the help!
Still stuck on the 4.0.2. Been swapped with work and life and finally found out my device is a yakjuXW. Meaning, it gets updated by Samsung. With the soon to be Jelly Bean OTA, I have to change this.
[Q] Galaxy Nexus stuck on 4.02
I am using gNexus but i have still not recieved official update to 4.04. I was wondering why is thwt? My baseband version is I9250XXKK6 Kernel version 3.0.8-gaaa2611 [email protected] #1 Build # ICL53F.I9250JPLA1 Please let me know if i need to manually update it or do i need to stay calm n wait for the update? Any further sources will be helpfull.
Faadiz said: I am using gNexus but i have still not recieved official update to 4.04. I was wondering why is thwt? My baseband version is I9250XXKK6 Kernel version 3.0.8-gaaa2611 [email protected] #1 Build # ICL53F.I9250JPLA1 Please let me know if i need to manually update it or do i need to stay calm n wait for the update? Any further sources will be helpfull. Click to expand... Click to collapse I gave up with OTA's takes too long. I usually just wait until someone has a stock update zip and just do that. Im on 4.0.4 now and so far so good! Hope that helps.
Please refer to my post here and it'll answer your question You could wait but that would be an indefinite timeframe OR you could just flash the stock yakju images (I'm not sure if you can do this if you are using CDMA though). If you're on a CDMA network, you might have to wait for your carrier to update it.
Hey man. This "Problem" has been fixed a few times already around the forums here. You will most likely have the "samsung-updated" version of the galaxy nexus. I had that to. There are a few types of Stock Roms on the Galaxy nexus right now. - The stock ROM powered and updated by google (also known as Galaxy Nexus with yakju builds) - Other ROMS that are powered and updated by Samsung or your cellphone provider This basically means that you live in a place were not all functions accessible to Android are available (government rules) or you got a phone from such a batch by accident. - What you need to do is unlock your OEM (you can re-lock it after the change to keep your warranty). - Wipe your complete phone so it can become a dev phone (the OEM unlock) your phone does this by itself on unlock. - Flash an official ROM from Galaxy Nexus itself. - Re-lock the OEM again (or not. I have it unlocked and my phone still works) - update if you haven't flashed the newest version (normal updates). Your phone will be a Google Powered phone after that! Here the instructions on how to do it: http://forum.xda-developers.com/showthread.php?t=1626895 Don't hesitate to send me a private message if this stuff is to hard for you. We can Skype or something and Ill help you set-up your phone.
Unlawful said: Please refer to my post here and it'll answer your question You could wait but that would be an indefinite timeframe OR you could just flash the stock yakju images (I'm not sure if you can do this if you are using CDMA though). If you're on a CDMA network, you might have to wait for your carrier to update it. Click to expand... Click to collapse No I am using GSM Version!
amonfog said: Hey man. This "Problem" has been fixed a few times already around the forums here. You will most likely have the "samsung-updated" version of the galaxy nexus. I had that to. There are a few types of Stock Roms on the Galaxy nexus right now. - The stock ROM powered and updated by google (also known as Galaxy Nexus with yakju builds) - Other ROMS that are powered and updated by Samsung or your cellphone provider This basically means that you live in a place were not all functions accessible to Android are available (government rules) or you got a phone from such a batch by accident. - What you need to do is unlock your OEM (you can re-lock it after the change to keep your warranty). - Wipe your complete phone so it can become a dev phone (the OEM unlock) your phone does this by itself on unlock. - Flash an official ROM from Galaxy Nexus itself. - Re-lock the OEM again (or not. I have it unlocked and my phone still works) - update if you haven't flashed the newest version (normal updates). Your phone will be a Google Powered phone after that! Here the instructions on how to do it: http://forum.xda-developers.com/showthread.php?t=1626895 Don't hesitate to send me a private message if this stuff is to hard for you. We can Skype or something and Ill help you set-up your phone. Click to expand... Click to collapse Thx Alot Buddy! I am much aware of the instructions you provided. I shall try them If i get stuck, i will surelly bug you Whats your twitter handle? mine is @Faadi
It's @amonfog ;-)
amonfog said: Hey man. This "Problem" has been fixed a few times already around the forums here. You will most likely have the "samsung-updated" version of the galaxy nexus. I had that to. There are a few types of Stock Roms on the Galaxy nexus right now. - The stock ROM powered and updated by google (also known as Galaxy Nexus with yakju builds) - Other ROMS that are powered and updated by Samsung or your cellphone provider This basically means that you live in a place were not all functions accessible to Android are available (government rules) or you got a phone from such a batch by accident. - What you need to do is unlock your OEM (you can re-lock it after the change to keep your warranty). - Wipe your complete phone so it can become a dev phone (the OEM unlock) your phone does this by itself on unlock. - Flash an official ROM from Galaxy Nexus itself. - Re-lock the OEM again (or not. I have it unlocked and my phone still works) - update if you haven't flashed the newest version (normal updates). Your phone will be a Google Powered phone after that! Here the instructions on how to do it: http://forum.xda-developers.com/showthread.php?t=1626895 Don't hesitate to send me a private message if this stuff is to hard for you. We can Skype or something and Ill help you set-up your phone. Click to expand... Click to collapse Hello: Thanks for the info. I have a google nexus phone with the problems described in this thread. I have a question before I try to go through the steps outlined in the instructions. When you say "Your phone will be a Google Powered phone after that", does that mean that the google nexus phone will be able to get updates over the air and become like google nexus phones from the play store. Any info on this will be appreciated. Again thanks.
WHOA! Toroplus AOSP binaries posted on Nexus Drivers Page!
Wow, the moment we never thought we'd see...it's listed as Archived, Reference Only, but Google has posted binaries, including CDMA/LTE blobs for toroplus at http://developers.google.com/android/nexus/drivers. These are binaries for Android 4.1.2/JZO54K. Go, build, be merry!
stock flash images are available too (GSM version that is, CDMA is still missing)
zephiK said: stock flash images are available too (GSM version that is, CDMA is still missing) Click to expand... Click to collapse We won't see factory images for toroplus because Sprint's Galaxy Nexus gets updates from Samsung, not Google. This thread is more to talk about the AOSP binaries which many, including myself, thought we'd never see for that exact same reason. Normally Google only releases binaries for devices that they update directly.
oldblue910 said: We won't see factory images for toroplus because Sprint's Galaxy Nexus gets updates from Samsung, not Google. This thread is more to talk about the AOSP binaries which many, including myself, thought we'd never see for that exact same reason. Normally Google only releases binaries for devices that they update directly. Click to expand... Click to collapse I wasn't asking when factory images for toroplus is coming out. I was just stating that the GSM flash images are available (as non-toroplus users will also visit the thread). Thanks for your input.
Anyone flashed it yet? Do we get a landscape homescreen as well?
MoosDiagramm said: Anyone flashed it yet? Do we get a landscape homescreen as well? Click to expand... Click to collapse Flash what? Fastboot flash factory images? ... if you want landscape homescreen just get a alternative launcher such as Apex or Nova and you can do the same. In terms of binaries, you can't flash binaries.
zephiK said: Flash what? Fastboot flash factory images? ... if you want landscape homescreen just get a alternative launcher such as Apex or Nova and you can do the same. In terms of binaries, you can't flash binaries. Click to expand... Click to collapse You seem kind of jumpy. I apologize for discussing the factory images in a thread that is clearly dedicated to the binaries alone. And no, I don't care much about a possible landscape homescreen, I just wanted to sparkle a friendly discussion about any noticeable changes in this release.
oldblue910 said: We won't see factory images for toroplus because Sprint's Galaxy Nexus gets updates from Samsung, not Google. This thread is more to talk about the AOSP binaries which many, including myself, thought we'd never see for that exact same reason. Normally Google only releases binaries for devices that they update directly. Click to expand... Click to collapse I'd be willing to bet that they will post factory images whenever Sprint gets around to pushing the 4.1.2 OTA. Which of course will probably be a while but is still very cool.
jesusice said: I'd be willing to bet that they will post factory images whenever Sprint gets around to pushing the 4.1.2 OTA. Which of course will probably be a while but is still very cool. Click to expand... Click to collapse That would be cool, but I'd be surprised. Historically Google has only released factory images for firmware that they update and maintain. The mysidspr firmware that runs on toroplus comes from Samsung, so if they were to provide factory images, that would be a real first.
oldblue910 said: That would be cool, but I'd be surprised. Historically Google has only released factory images for firmware that they update and maintain. The mysidspr firmware that runs on toroplus comes from Samsung, so if they were to provide factory images, that would be a real first. Click to expand... Click to collapse I'm gonna have to disagree with you here. I'm pretty sure that Google doesn't update the Verizon Galaxy Nexus or the Sprint Nexus S 4G yet they both have their factory images. Note that both the NS4G and the Toro have their 4.1.2 binaries posted but not the 4.1.2 factory images. This is because for AOSP devices that are not updated by Google they wait until the offical OTA to release the factory images.
jesusice said: I'm gonna have to disagree with you here. I'm pretty sure that Google doesn't update the Verizon Galaxy Nexus or the Sprint Nexus S 4G yet they both have their factory images. Note that both the NS4G and the Toro have their 4.1.2 binaries posted but not the 4.1.2 factory images. This is because for AOSP devices that are not updated by Google they wait until the offical OTA to release the factory images. Click to expand... Click to collapse For CDMA devices, Google updates the Verizon Xoom, Verizon Gnex, and NS4G. The "trygon", "mysid", and "sojus" firmware that run on those devices respectively all come from Google, they're just subject to carrier approval. You can tell due to the build numbers: On trygon, mysid and sojus, the build numbers follow normal Google conventions (IMM76D, JRO03H, etc.). The Sprint Galaxy Nexus uses Samsung conventions (IMM76D.L700FG01 for instance). You can also tell by the kernel build dates. On mysid and sojus, the kernels match AOSP. On the Sprint Galaxy Nexus, the kernel has a build date in KST (Korean Standard Time) and was built by [email protected] Clearly the Toroplus (Sprint Gnex) kernel is built by Samsung. Another way to tell is in the OTA file naming conventions. Any (except the Nexus S as of Ice Cream Sandwich for some reason) has OTA files that follow the naming convention <12-character-sha1-hash>.signed-<firmware name>-<new build>-from-<old build>.<8-character-sha1-hash>.zip...so like abcdef012345.signed-mysid-JRO03O-from-IMM76K.abcdef01.zip. Updates for NS4G, Verizon Gnex, and Verizon Xoom all have these naming conventions. The OTA files for the Sprint Galaxy Nexus follow Samsung's naming convention of abcdef012345.update-IMM76K-to-JRO03O.zip. In the end though, just look at the build number. If the build number is 5 or 6 characters, it's a Google firmware. Otherwise, it comes from the OEM.
oldblue910 said: For CDMA devices, Google updates the Verizon Xoom, Verizon Gnex, and NS4G. The "trygon", "mysid", and "sojus" firmware that run on those devices respectively all come from Google, they're just subject to carrier approval. You can tell due to the build numbers: On trygon, mysid and sojus, the build numbers follow normal Google conventions (IMM76D, JRO03H, etc.). The Sprint Galaxy Nexus uses Samsung conventions (IMM76D.L700FG01 for instance). You can also tell by the kernel build dates. On mysid and sojus, the kernels match AOSP. On the Sprint Galaxy Nexus, the kernel has a build date in KST (Korean Standard Time) and was built by [email protected] Clearly the Toroplus (Sprint Gnex) kernel is built by Samsung. Another way to tell is in the OTA file naming conventions. Any (except the Nexus S as of Ice Cream Sandwich for some reason) has OTA files that follow the naming convention <12-character-sha1-hash>.signed-<firmware name>-<new build>-from-<old build>.<8-character-sha1-hash>.zip...so like abcdef012345.signed-mysid-JRO03O-from-IMM76K.abcdef01.zip. Updates for NS4G, Verizon Gnex, and Verizon Xoom all have these naming conventions. The OTA files for the Sprint Galaxy Nexus follow Samsung's naming convention of abcdef012345.update-IMM76K-to-JRO03O.zip. In the end though, just look at the build number. If the build number is 5 or 6 characters, it's a Google firmware. Otherwise, it comes from the OEM. Click to expand... Click to collapse Pfft. Facts. You can prove anything with facts
jesusice said: Pfft. Facts. You can prove anything with facts Click to expand... Click to collapse Two words for you, sir. Well played!
oldblue910 said: For CDMA devices, Google updates the Verizon Xoom, Verizon Gnex, and NS4G. The "trygon", "mysid", and "sojus" firmware that run on those devices respectively all come from Google, they're just subject to carrier approval. You can tell due to the build numbers: On trygon, mysid and sojus, the build numbers follow normal Google conventions (IMM76D, JRO03H, etc.). The Sprint Galaxy Nexus uses Samsung conventions (IMM76D.L700FG01 for instance). You can also tell by the kernel build dates. On mysid and sojus, the kernels match AOSP. On the Sprint Galaxy Nexus, the kernel has a build date in KST (Korean Standard Time) and was built by [email protected] Clearly the Toroplus (Sprint Gnex) kernel is built by Samsung. Another way to tell is in the OTA file naming conventions. Any (except the Nexus S as of Ice Cream Sandwich for some reason) has OTA files that follow the naming convention <12-character-sha1-hash>.signed-<firmware name>-<new build>-from-<old build>.<8-character-sha1-hash>.zip...so like abcdef012345.signed-mysid-JRO03O-from-IMM76K.abcdef01.zip. Updates for NS4G, Verizon Gnex, and Verizon Xoom all have these naming conventions. The OTA files for the Sprint Galaxy Nexus follow Samsung's naming convention of abcdef012345.update-IMM76K-to-JRO03O.zip. In the end though, just look at the build number. If the build number is 5 or 6 characters, it's a Google firmware. Otherwise, it comes from the OEM. Click to expand... Click to collapse Needs to be stickied somewhere.
oldblue910 said: That would be cool, but I'd be surprised. Historically Google has only released factory images for firmware that they update and maintain. The mysidspr firmware that runs on toroplus comes from Samsung, so if they were to provide factory images, that would be a real first. Click to expand... Click to collapse How cool is this!? https://developers.google.com/android/nexus/images#mysidspr
jesusice said: How cool is this!? https://developers.google.com/android/nexus/images#mysidspr Click to expand... Click to collapse That's about as cool as it gets!
jesusice said: How cool is this!? https://developers.google.com/android/nexus/images#mysidspr Click to expand... Click to collapse Where were you yesterday when I posted that? Nobody cared, LOL.
The build is FH05 but the radios are FC12 so you have to update the radios if you restore the factory image Sent from my Galaxy Nexus
adrynalyne said: Where were you yesterday when I posted that? Nobody cared, LOL. Click to expand... Click to collapse Lol, not checking General! That place gives me eye cancer.
Hopefully this is the beginning of some cool stuff. Hopefully we will have 4.2 images shortly after they release the code to it. I know we will have custom ROMs but stock images would be nice too.
June 19's ROM update, Verizon-specific
All my Pixels have been Google-branded. Over the years, there have been carrier-specific builds during some updates. I have seen it for Verizon and T-Mobile. I have used both the generic version and carrier-specific builds and they work fine in the Google-branded Pixels. I am still curious, though, what is Google's intent for these carrier-specific builds? Should the Google-branded Pixel always run the generic build, or if I am using a Verizon SIM, I should use the Verizon-specific build? My phone is rooted, so I never OTA.
The carrier specific builds usually have either different bootloader or radio images than the Google stock build. My guess as to why Google does this is that the carrier submitted their changes somewhat late in the cycle and Google doesn't want to risk rolling them out to everyone until they are sure it works as intended, since they usually go back to a single stock build the next month that includes the carrier specific items. As to which build to use my experience has been that a Google branded phone with a Verizon sim will try to take a Stock OTA if the difference is the bootloader and the Verizon OTA if it is the radio. I have downloaded and looked at both versions and the bootloader is the difference so I would use the Google stock image.
DougMG said: I have downloaded and looked at both versions and the bootloader is the difference so I would use the Google stock image. Click to expand... Click to collapse To confirm my understanding -- you compared the June firmware between the Google and VZ version, and the only difference is the bootloader? Thanks.
snovvman said: To confirm my understanding -- you compared the June firmware between the Google and VZ version, and the only difference is the bootloader? Thanks. Click to expand... Click to collapse Correct.
june 19?
I honestly don't think it matters. I didn't even notice that there was a Verizon version and was in a rush getting ready to leave work. I accidentally downloaded and flashed the Verizon version to my Google branded 3XL on AT&T and it's doing fine. I've had no issues.