yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] wolfedude88:
So is it safe to flash that on our build though? I haven't rooted yet so I assume I need to do that and probably install cwm? Kind of sucks that we will probably have to void our warranty just to get updates.
[Samsung Galaxy Nexus] Luxferro:
No need to root or flash CWR. Just use fast boot to OEM unlock and flash new images.

Also who knows maybe we will get updates. I planned to flash custom from eventually so unlocking doesn't bother me at all.
[Samsung Galaxy Nexus] f231f:
FWIW, I got mine from Expansys USA on Saturday from their Friday shipment (the batch after yours shipped) and it has the correct google build.

ro.build.fingerprint=google/yakju/maguro:4.0.1/ITL41F/228551:user/release-keys
[Samsung Galaxy Nexus] El Daddy:
Hmmm... so it must only be the batch expansys shipped on 12/1
[Samsung Galaxy Nexus] waylo:
No, also the Negri batch shipped 11/30.
[Samsung Galaxy Nexus] El Daddy:
Well there goes that idea! :/
[Samsung Galaxy Nexus] brian85:
How do you guys check the build?
[Samsung Galaxy Nexus] El Daddy:
Easiest way is download astro or any other file manager and navigate to /system and view build.prop with document viewer.
[Samsung Galaxy Nexus] ianwood:
Given the accelerated development schedules and down to the minute bug fixing that goes on before new devices are released, it is not uncommon for devices to be shipped out to the major distributor locations without the final release build on them.

In those cases, they get re-flashed at the distributor and final bundling is done before shipping out to retailers. Some devices will slip through the cracks on that final flash as the process is not as automated as at the factory. That might explain what happened here.
[Samsung Galaxy Nexus] brian85:
Mine shows yakjuxw. What does this mean?

---------- Post added at 05:46 AM ---------- Previous post was at 05:45 AM ----------

Does this mean my phone won't get updates? This is ridiculous.
[Samsung Galaxy Nexus] Luxferro:
I bit the bullet and just flashed the 4.0.1 (ITL41F) factory image. It was easy enough if you have fastboot installed and working, and you phone unlocked.

Just grab the Factory Image yakju-itl41f-factory-192e5c67.tgz from google

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

open the file with you zip program (i use 7-zip), pull out the image-yakju-itl41f.zip file. Then all you need to do is

fastboot -w update image-yakju-itl41f.zip

You don't need to bother with the other files in the package cause you already have latest bootloader, and radio. This will wipe your whole phone, so backup if you need to.
[Samsung Galaxy Nexus] waylo:
Exactly. No updates for you! One year!

Or, until you decide to flash the factory images.

Or, they release an OTA that includes the yakjuxw build.

I'm just letting mine be for now.

(Of course, I'm still transferring data from my Nexus One to my Gnex, and haven't used it extensively as an actual phone yet. My opinion might change).

Sounds like you and I got the same batch from Negri.

---------- Post added at 09:54 PM ---------- Previous post was at 09:54 PM ----------

Does this wipe the "sdcard" partition?

Oh, looks like the recovery will also be replaced with that method.
[Samsung Galaxy Nexus] Luxferro:
Yeah, it wipes it all.
[Samsung Galaxy Nexus] brian85:
This doesn't make sense. Google just can't let these phones not get updates, they need to fix it somehow.

Obviously if there are some of us on this forum with this issue, there are MANY of these out there (since we on the forum are a small percentage of people who buy it).
[Samsung Galaxy Nexus] LordGrahf:
Got same crap. Got mine on Friday from negri
[Samsung Galaxy Nexus] waylo:
Negri now has a presence on these forums. Well, one post at least, in the Negri experience thread.

I haven't had any real issues with the phone yet, so I'm not going to formally complain.
[Samsung Galaxy Nexus] EErez:
Can anyone who has certain recently purchased this phone on either expansys or negri confirm that newer batches ship with the Google firmware? I'm going to take this into consideration when purchasing my phone. Maybe these were just phones that left the UK during the alarmist for week of the volume bug discussion.
[Samsung Galaxy Nexus] noobdeagle:
So far this is only happening from American retailers right ? Mine was from handtec after the supposed reflash and its fine
[Samsung Galaxy Nexus] aimetti:
Got my replacement device yesterday and noticed my volume going crazy. Switching from all the different options.

Figured it was the same bug as before and sure enough came on here and saw this thread.

Looks like I am in the same boat as you guys. Expansys batch shipped on last thursday.

Did you guys get a normal USA power adapter too? I got a square one instead of the euro model with an adapter. I also noticed I didnt have a sticker holding the two boxes together like my first nexus came. Box was just free to open.

yakjuxw is on mine as well
[Samsung Galaxy Nexus] brian85:
I also got a standard USA samsung charger which I thought was weird.
[Samsung Galaxy Nexus] waylo:
I did too. But my box was sealed with 2 clear circular stickers.

Obviously not completely tamper proof packaging, but it appeared new to me.
[Samsung Galaxy Nexus] aeox:
Is the sticker on the outside of the box on the back instead now? And says Phone Made in Korea. But the sticker on the back of the phone itself say Korean Product without any FCC logos and such?
[Samsung Galaxy Nexus] aimetti:
ya that sticker is now on the back.

on my other one it is on the side. There was also a sticker that went over the edge so it sealed the package that said dont accept if seal broken. That sticker is not on the new device I received.
[Samsung Galaxy Nexus] brian85:
Has anyone tried contacting google on this? They need to have a fix for this or something.
[Samsung Galaxy Nexus] El Daddy:
So I have the yakjuxw build on my phone. I also have the box you guys are describing with the sicker on the back and both english and spanish legal text.

Underneath the battery is not the FCC sticker shown on most of the unboxing videos but it is one in spanish.

I asked Dan Morrill of Google if he knew what the yakjuxw was and he forwarded the question to Jean-Baptiste Queru this was his response:

"Jean-Baptiste Queru - This is a region-specific build specific for I forgot which region (might be Europe plus SE Asia - I don't remember the codes by heart)."

I have asked him if as a US owner I should flash the factory image from the code.google site and I'm awaiting a reply. I'll update this post if he replies.
[Samsung Galaxy Nexus] brian85:
I'm pretty sure we (myself included obviously) are just freaking out a little on the updates thing. OP tried to manually flash an update and it didn't work...we probably just have to wait for one that works for our build. Google acknowledged they know about that build type, so they'll obviously put out the same updates as the other nexus phones.
[Samsung Galaxy Nexus] Luxferro:
Jean-Baptiste Queru was who I got my initial info from on twitter. He's the one who told me I had a region specific build after he asked around. But when I asked if it was an older build with the volume bug, or if it would get OTA updates in the future he wasn't sure. So I figured I used up my one question.

Maybe he'll find out the answers from someone who knows for you :)

Yeah, that will probably be the case. I got tired of the unknowns surrounding it and just flashed the google factory images. No issues whatsoever.
[Samsung Galaxy Nexus] aeox:
I wonder where ours came from or was suppose to be marketed to.
[Samsung Galaxy Nexus] LordGrahf:
I thought that was one of the biggest selling points for the nexus, getting the OTA updates first :p
[Samsung Galaxy Nexus] Luxferro:
Well I guess this build wasn't a one-off. There's updates to the yakjuxw builds it seems..

http://android.modaco.com/topic/349407-odin-firmware-i9250xwkk8-itl41f/

I wonder if these are really some kind of samsung development builds (but then why would they use release keys, and not dev?), or are indeed region specific. Seems odd pretty odd to have both google and samsung releasing their own builds.
[Samsung Galaxy Nexus] brian85:
What I got from that is that our samsung build is just one of the newer updates, but the one on the link is the newest update.

So, the order sounds like this (oldest to newest):

people with the google build > people with the samsung build > newest build in link above (and the OTA that some have gotten already)
[Samsung Galaxy Nexus] El Daddy:
Thanks for finding this. I would assume it would be better to run the Google builds rather than the Samsung ones.
[Samsung Galaxy Nexus] Luxferro:
Yeah, probably. Who knows if the samsung ones will get OTA updates. I doubt it if there are already newer builds out and none of us got any updates. I don't have an account on those forums, maybe someone that does can ask the OP there what the differences between the builds are (since he seems to have some samsung connections).
[Samsung Galaxy Nexus] omrij:
Anyone with XWKK8 can upload SS of the language available in settings?
[Samsung Galaxy Nexus] El Daddy:
So I heard back from JBQ.

This is what he said:
[Samsung Galaxy Nexus] Luxferro:
secany, who released the newer build on modaco forums basically confirmed what we were already told.

I asked him if he could tell me what region our phones were intended to be for. Hopefully he knows and can tell us. I'm just curious. It doesn't really matter much to me. My phone works great. And I already flashed latest google factory image, and no problems with that either. Still working great!
[Samsung Galaxy Nexus] El Daddy:
Yeah i've been watching that modaco thread and saw you had posted.

I'm curious where the intended locale is as well. I think I'm just going to leave my current build on my phone until there is a reason to change or I decide to flash a custom ROM.

I'm having zero problems now so I'll just ride it out.
[Samsung Galaxy Nexus] brian85:
All I want to know is if we will get the same updates as everyone else. Unless I skipped over it, I haven't seen a clear answer to that.
[Samsung Galaxy Nexus] Grant H:
I got a GN from the orginial batch from Expansys-USA. It updated within minutes of powering it on to the volume fix.
[Samsung Galaxy Nexus] LordGrahf:
Thanks for the info. When I run the command it stops at the : <waiting for device> step

What am I missing?
[Samsung Galaxy Nexus] Luxferro:
Well if you have never used fastboot before, I'd make sure your drivers are setup correctly and everything is working.

try

fastboot devices

and see if it lists your device. If not, you have a communication problem (drivers) between computer and phone.

Also, you need to have your phone unlocked before you can flash or boot images with fastboot.

But this will erase everything (including SD card)... so backup if you have photos, ect, you want to keep.

fastboot oem unlock
[Samsung Galaxy Nexus] waylo:
Doesn't sound like you have fastboot drivers installed. What happens if you type in "fastboot devices"?

Edit : luxferro you beat me to it!
[Samsung Galaxy Nexus] brian85:
I think it's pretty sad that we have to do this just to get updates.

We better get updates on our damn phone lol
[Samsung Galaxy Nexus] enumBoss:
Wish I had noticed this earlier. Just checked my build file and I also have the yakjuxw (Samsung) build on my device. I ordered it from Popular Electronics and have had it for about 4 days now. I was wondering why I had yet to receive the OTA update. I don't mind sticking with this version as long as I don't have to wait longer for updates in the future. Hopefully the next OTA update will bring all GSM Galaxy Nexus users to the same build.

Also kind of curious as to why there are region specific builds in the first place. What exactly is different?
[Samsung Galaxy Nexus] waylo:
I'm having two strange issues, so I'm going to flash the factory "stock" ITL41F provided by google over my "yakjuxw" build.

Whether or not the build is the reason I guess I'll find out.

1. Account sync keeps turning itself OFF. Not useful! WTF.

2. Rotate keeps re-enabling itself.

Not exactly sure how the I9250XWKK9 build link provided earlier fits into all of this.

EDIT: Nevermind. Both issues due to user error.
[Samsung Galaxy Nexus] LordGrahf:
Thanks. Yeah the devices doesn't show my phone so I guess I'll Google around to find drivers for this phone.

What do you mean by unlocked btw?
[Samsung Galaxy Nexus] enumBoss:
Unlocked meaning unlocking the bootloader. When you boot (if it's unlocked) at the Google logo screen, you should see an unlocked padlock at the bottom of the screen.

When he posted you type the command "fastboot oem unlock", that unlocks the bootloader. But you need the drivers to do that. It will wipe all the data on your phone.

I had the same issue as you. As mentioned elsewhere on this forum, the best way to do this is make sure you already installed the Samsung USB drivers, then install PDANet (google it). If you follow the installation instructions, it should install the necessary drivers, then you can uninstall PDANet after it's done. After that, it should show up when you do "fastboot devices" while in recovery.
[Samsung Galaxy Nexus] waylo:
Okay, finished the flash.

After setting up my phone again, for the umpteenth time in a few days (so much fun being an early adopter!), both reasons are decidedly UNRELATED to the build. Haha.

EDIT: Nevermind for all. User error.
[Samsung Galaxy Nexus] kara mustafa:
So is it possible to flash google image over samsug one via bootloader?
[Samsung Galaxy Nexus] bfroehlich:
Yes, as long as you wipe userdata and cache first. But running the fastboot command with the -w flag will wipe them automatically.
[Samsung Galaxy Nexus] LordGrahf:
Thanks!!!

Can the bootloader be locked again after I'm done?
[Samsung Galaxy Nexus] dnlsmy:
Yes, just

fastboot oem lock
[Samsung Galaxy Nexus] LordGrahf:
Thank you sir. I'll give this process another try now :)
[Samsung Galaxy Nexus] TroyBoy30:
i dont have a sim to start using my phone yet but didnt someone say something about the safety sticker being in the wrong spot?

heres mine. ordered from expansys on dec 1st. got it today
[Samsung Galaxy Nexus] enumBoss:
Mine didn't even have a sticker. But I didn't get it from Expansys.
[Samsung Galaxy Nexus] cunter:
Just to let you know. The first batch of galaxy nexus in germany came with ITL41F.I9250XWKK8 and bootloader already unlocked.

People who bought one from the new batch that just came out today say that they are having ITL41F.

There is already a issue open at http://code.google.com/p/android/issues/detail?id=22435

I am really curious what Samsung messed up here.
[Samsung Galaxy Nexus] Luxferro:
Good to know we weren't alone in this. Hopefully they straighten it out for the people who didn't want to flash the google factory images (I already did :) )
[Samsung Galaxy Nexus] LordGrahf:
ok just flashed and it works like a charm!

One thing to add to nubs like myself: you'll need to boot your phone under fastboot mode which is done by holding both volume buttons + power button
[Samsung Galaxy Nexus] waylo:
Also you will need to re-root the phone, if it was previously so.
[Samsung Galaxy Nexus] Luxferro:
A good thing to do if you're rooted, is tar/zip/gzip the /factory folder. this contains important data such as your IMEI number. If somehow you mess up or lose this folder you'll end up with a generic # and a lot of problems.

/factory is basically the /efs folder on other samsung phones. nandroids don't back up this folder, so you need to do it manually. If you plan on messing with roms, overclocking, trying 3rd party kernels, ect. Or you just like to randomly delete or edit files on your phone :p then backing up is probably the wise thing to do. Also save a bunch of copies off your phone. Email it to yourself, put in your home PC, or NAS.

If you don't root, or mess with stuff, then probably best you leave it alone.
[Samsung Galaxy Nexus] kevink817:
Just got the Galaxy Nexus in Japan from NTT DoCoMo and the product name is even different from anything else posted here: 'yakjusc'. I guess this is so we only get updates directly from DoCoMo? :confused:

Also they were nice enough to remove the tethering features :mad:

Guess ill try flashing the factory 'yakju' as well, at some point...
[Samsung Galaxy Nexus] enumBoss:
Isn't the DoCoMo version not GSM?
[Samsung Galaxy Nexus] kevink817:
No, it is the GSM version
[Samsung Galaxy Nexus] brian85:
That's actually good to know because now we know the samsung build that a lot of us have isn't just some messed up thing. So looks like we will all still get the same updates..
[Samsung Galaxy Nexus] EErez:
So basically these are all phones that did not originate in the UK? Has anyone who purchased their phone from handtec or clove have this issue?
[Samsung Galaxy Nexus] joeykrim:
Purchased from Negri on Dec 6th - Same build.prop fingerprint:

ro.build.fingerprint=samsung/yakjuxw/maguro:4.0.1/I9250XWKK5_ITL41D/163402:user/release-keys

To find this information I just did ./adb shell cat build.prop and scrolled through for the fingerprint line. Not that many lines in the file.

I'm also tempted to flash the stock images from Google, but might wait to hear more about the "differences" either hardware or software.

Thanks for all the information so far!
[Samsung Galaxy Nexus] aimetti:
i had to flash to the stock google rom for anything to work.

Wasnt getting OTA updates and for some reason my phone was getting the volume bug here in the states. Would cycle through vibrate / mute / sound like a madman.
[Samsung Galaxy Nexus] TroyBoy30:
mine asked to be updated as soon as I set it up, so I guess i'm all goo
[Samsung Galaxy Nexus] Lcrkz0023:
FWIW, I got mine from Negri..1st batch shipped out Nov25th and it has the correct google build. Received update on Dec. 3rd.

ro.build.fingerprint=google/yakju/maguro:4.0.1/ITL41F/228551:user/release-keys
[Samsung Galaxy Nexus] brian85:
Has someone brought this issue up to google yet? I wonder if they'll give us an answer about updates.
[Samsung Galaxy Nexus] enumBoss:
Just an update about different builds. I posted this information on the Android Building Google Group. Here's the reply I got from a Google Android Engineer:

Can see the full post here: http://groups.google.com/group/android-building/browse_thread/thread/2dde45a058a737b9

It sounds like those of us with Samsung builds get our updates from Samsung, not Google. If this is the case, it also looks like the LTE phone will be through Verizon or Samsung instead of Google, as well. But the really interesting thing here is that he mentioned possible hardware differences.
[Samsung Galaxy Nexus] brian85:
That actually pisses me off.

This is a nexus...we should get updates from google no matter what. We shouldn't have to "hack" the phone just to get the proper build on there.
[Samsung Galaxy Nexus] enumBoss:
I agree. And there's no indication on the box before you buy it whether you're getting a Google or Samsung device.

Now, I'm not gonna get too worked up yet. Going to wait on more information because there may be no hardware differences at all. I don't mind flashing once if it means timely updates from Google instead of Samsung. But I don't want to hastily flash it right now when it could cause issues later.
[Samsung Galaxy Nexus] brian85:
You would think they could just put out an OTA to get everyone on the proper build.
[Samsung Galaxy Nexus] enumBoss:
I wish. But according to this Google developer, these builds were handled internally by Samsung and the yakju devices were handled internally by Google. This Google developer doesn't even know all of the different builds or what (if anything) is different hardware-wise. So it looks like Samsung is in charge of handling region specific updates (Verizon, DoCoMo, yakjuwx, etc) and Google handles the rest.
[Samsung Galaxy Nexus] El Daddy:
Just some FYI. I had the yakjuxw build on my phone and I flashed the yakju build on code.google.com I have not had any problems.

This is the type of thing that can happen when importing devices. I'm sure places like expansys, negri, etc. were scrambling to fill their orders and getting any Galaxy Nexus they could get their hands on. I'm sure they had no idea the builds were different considering the lead of AOSP had no idea as well.
[Samsung Galaxy Nexus] enumBoss:
I'm sure they had no idea. And I don't blame the import shops. I just wish it was more clearly indicated where each device was coming from.

Also, just because you haven't had issues yet doesn't mean it's not possible for some people. Not to scare you or anything, but I'd rather know from Google that it's safe to do before I mess with it.
[Samsung Galaxy Nexus] aldo37:
I bought mine from Expansys last night and it shipped today. Will let you guys know which I get.

Just to clarify, yakju is the correct Google one right?
[Samsung Galaxy Nexus] enumBoss:
Yes. yakju is Google. But when you check the build file in /system, it will say Google or Samsung right before the build name, as well.
[Samsung Galaxy Nexus] TroyBoy30:
any other way to check it?
[Samsung Galaxy Nexus] enumBoss:
Not really. But it's pretty simple. Just use a file browser like ASTRO and go to /system. Then open the file build.prop with a text editor.
[Samsung Galaxy Nexus] cjeremy:
will everything be alright if I just order straight from UK?

i'm planning on ordering from Clove or Handtec..

is that the safest choice?
[Samsung Galaxy Nexus] jhuynh:
Looks like Canada got a different product name than the two previous known names. I haven't seen any update since I bought the phone on Wed. Here's my build.prop from a Bell phone:

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=ITL41D
ro.build.display.id=ITL41D.I9250UGKK7
ro.build.version.incremental=I9250UGKK7
ro.build.version.sdk=14
ro.build.version.codename=REL
ro.build.version.release=4.0.1
ro.build.date=Fri Nov 18 20:54:44 KST 2011
ro.build.date.utc=1321617284
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-82
ro.build.tags=release-keys
ro.product.model=Galaxy Nexus
ro.product.brand=samsung
ro.product.name=yakjuux
ro.product.device=maguro
ro.product.board=tuna
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=maguro
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=yakjuux-user 4.0.1 ITL41D I9250UGKK7 release-keys
ro.build.fingerprint=samsung/yakjuux/maguro:4.0.1/ITL41D/I9250UGKK7:user/release-keys
ro.build.characteristics=nosdcard
# end build properties
#
# system.prop for maguro
#

rild.libpath=/vendor/lib/libsec-ril.so
rild.libargs=-d /dev/ttys0
telephony.lteOnCdmaDevice=0

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.error.receiver.system.apps=com.google.android.feedback
ro.error.receiver.default=com.samsung.receiver.error
ro.setupwizard.mode=ENABLED
ro.setupwizard.enterprise_mode=1
ro.config.ringtone=Girtab.ogg
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Cesium.ogg
keyguard.no_require_sim=true
drm.service.enabled=true
wifi.interface=Alan
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
ro.sf.lcd_density=320
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.com.google.gmsversion=4.0_r1
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
[Samsung Galaxy Nexus] demzzy:
i have kk7 as well... and no issues..