5,603,981 Members 44,256 Now Online
XDA Developers Android and Mobile Development Forum

My Galaxy Nexus came with Samsung ICS build rather then google...

Tip us?
 
Luxferro
Old
(Last edited by Luxferro; 14th December 2011 at 05:05 AM.)
#1  
Senior Member - OP
Thanks Meter 310
Posts: 1,058
Join Date: Nov 2009
Location: Long Island, NY
Default My Galaxy Nexus came with Samsung ICS build rather then google...

I just went to update my gnex manually, and both stock recovery and CWR told me that the signature was wrong.

So I looked in the update zip and saw the following

Code:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/yakju/maguro:4.0.1/ITL41D/223971:user/release-keys" ||
       file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/yakju/maguro:4.0.1/ITL41F/228551:user/release-keys");
Then I looked in my build.prop and saw that I have a different fingerprint, and that is why I won't let me manually update.

Code:
ro.build.fingerprint=samsung/yakjuxw/maguro:4.0.1/I9250XWKK5_ITL41D/163402:user/release-keys
looks like mines from samsung rather then google.

edit: just to clear up for what region this build is meant for
Quote:
XW = Austria, Belgium, France, Germany, Hungary, Italy, Spain, United Kingdom
The Following 3 Users Say Thank You to Luxferro For This Useful Post: [ Click to Expand ]
 
matt2053
Old
#2  
Senior Member
Thanks Meter 299
Posts: 2,059
Join Date: Dec 2010
Location: Clearwater, FL

 
DONATE TO ME
Will you post the rest of your build.prop?

Sent from my Galaxy Nexus using XDA App
 
Chirality
Old
#3  
Senior Member
Thanks Meter 129
Posts: 649
Join Date: Sep 2008
Location: Cambridge, MA
Quote:
Originally Posted by Luxferro View Post
I just went to update my gnex manually, and both stock recovery and CWR told me that the signature was wrong.

So I looked in the update zip and saw the following

Code:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/yakju/maguro:4.0.1/ITL41D/223971:user/release-keys" ||
       file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/yakju/maguro:4.0.1/ITL41F/228551:user/release-keys");
Then I looked in my build.prop and saw that I have a different fingerprint, and that is why I won't let me manually update.

Code:
ro.build.fingerprint=samsung/yakjuxw/maguro:4.0.1/I9250XWKK5_ITL41D/163402:user/release-keys
looks like mines from samsung rather then google.
Looks like it's also running an older baseband - XWKK5 rather than XXKK1. Perhaps, like the first person who got the GN in the UK, you got a prerelease phone that was never meant to be sold at retail?
 
xHausx
Old
#4  
xHausx's Avatar
Forum Moderator / Recognized Developer
Thanks Meter 4460
Posts: 6,732
Join Date: Jul 2010
Location: Central Florida

 
DONATE TO ME
Quote:
Originally Posted by Chirality View Post
Looks like it's also running an older baseband - XWKK5 rather than XXKK1. Perhaps, like the first person who got the GN in the UK, you got a prerelease phone that was never meant to be sold at retail?
Is it normal for Samsung to use release keys on their test software though?
The Following User Says Thank You to xHausx For This Useful Post: [ Click to Expand ]
 
Luxferro
Old
#5  
Senior Member - OP
Thanks Meter 310
Posts: 1,058
Join Date: Nov 2009
Location: Long Island, NY
My baseband is K1, just says otherwise in the fingerprint. Here's the build.prop

Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=I9250XWKK5_ITL41D
ro.build.display.id=I9250XWKK5_ITL41D
ro.build.version.incremental=163402
ro.build.version.sdk=14
ro.build.version.codename=REL
ro.build.version.release=4.0.1
ro.build.date=Sun Nov 13 04:05:52 KST 2011
ro.build.date.utc=1321124752
ro.build.type=user
ro.build.user=dpi.sec
ro.build.host=DELL159
ro.build.tags=release-keys
ro.product.model=Galaxy Nexus
ro.product.brand=samsung
ro.product.name=yakjuxw
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=yakjuxw-user 4.0.1 I9250XWKK5_ITL41D 163402 release-keys
ro.build.fingerprint=samsung/yakjuxw/maguro:4.0.1/I9250XWKK5_ITL41D/163402: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=wlan0
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
I guess I'll have to use the full system images to update my phone, as I'll never get the update.
 
Chirality
Old
#6  
Senior Member
Thanks Meter 129
Posts: 649
Join Date: Sep 2008
Location: Cambridge, MA
The product name is different, it's yakjuxw instead of yakju, which means it's meant to be a different device than the normal release device that most people got (though that doesn't necessarily mean there are any hardware differences.)
 
Luxferro
Old
#7  
Senior Member - OP
Thanks Meter 310
Posts: 1,058
Join Date: Nov 2009
Location: Long Island, NY
Quote:
Originally Posted by Chirality View Post
The product name is different, it's yakjuxw instead of yakju, which means it's meant to be a different device than the normal release device that most people got (though that doesn't necessarily mean there are any hardware differences.)
Yeah, I initially noticed that too. Hopefully the hardware is the same and I won't run into any further issues once I flash the latest images. I created a nandroid just in case though.
 
Luxferro
Old
#8  
Senior Member - OP
Thanks Meter 310
Posts: 1,058
Join Date: Nov 2009
Location: Long Island, NY
Quote:
Originally Posted by xHausx View Post
Is it normal for Samsung to use release keys on their test software though?
The odd thing is I only got the phone Friday from Expansys. Appeared to be brand new
 
waylo
Old
(Last edited by waylo; 5th December 2011 at 06:36 AM.)
#9  
waylo's Avatar
Senior Member
Thanks Meter 128
Posts: 723
Join Date: May 2010
I have the same thing on mine! No wonder... I've been waiting forever for the OTA update.

Shipped to me Thursday from Negri, here in the US. Picked it up at the Fedex depot on Saturday.

Galaxy S4 T-Mobile
[ROM] Wicked v5.1
[Recovery] TWRP 2.5.0.2
------------
Galaxy Nexus GSM
[ROM] XenonHD vXVIII
[Build] JZO54K 4.1.2
[Kernel] Leankernel 4.7exp2-180/interactive/deadline
[Recovery] TWRP 2.3.3.0
[Radio] I9250XXLF1
[Bootloader] PRIMELC03
------------
HP Touchpad 32gb
[ROM] Jcsullins 7/14/13 build with battery fix
 
Chirality
Old
#10  
Senior Member
Thanks Meter 129
Posts: 649
Join Date: Sep 2008
Location: Cambridge, MA
Hmm...maybe Samsung pushed out their own update to fix the volume bug because they thought Google was taking too long. Perhaps this is what those retailers meant when they said that Samsung did additional testing and fixed some batches?

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes