Develop Bugs

[ROM][2.2.1] ZSJPJ [MAR 12] DOWNLOAD - Newest ROM for HK/Taiwan

newest ROM out there. build info: Sat Mar 12 16:37 2011
Here is the firmware divided on 3 files, no bootloaders are included, so it's safe and you can choose CSC for your region before flashing.
Multiupload link: Download (157.5 MB)
Credits to Ramad for this!!!!
PDA: ZSJPJ
Modem: ZSJPG
CSC: ZSJPG
official firmware for North Asia, available via Kies
buid info: Sat Mar 12 16:37 2011
languages: Chinese (3), Korean, eng UK, eng US

Tks, but what I'm about to do, and hope you don't mind
/RANT MODE ON
WHAT THE **** IS SAMSUNG DOING????
This is the 2nd release for North Asia, and yet nothing for South East Asia!!!!
Go stuff it, SAMSUNG!!!
/RANT MODE OFF
Sorry for crashing into your thread, and thanks for this release.
Sent from my GT-I9000

alelas said:
Download link http://www.multiupload.com/9TL2UOTP0B
ZSJPJ/ZSJPG/ZSJPG
was posted a while ago here http://forum.xda-developers.com/showpost.php?p=12211910&postcount=383 , so I thought I'd put it in separate thread.
If anybody wants to flash with odin and give more info on built date etc?
Click to expand...
Click to collapse
buid info: Sat Mar 12 16:37 2011
modem ZSJPG
and contains strange languages out of Eng US and Eng UK....6 in total
kernel 2.6.32.9 [email protected] #8
froyo 2.2.1

this is a rom for taiwan,hk,china,those language are chinese
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=FROYO
ro.build.display.id=FROYO.ZSJPJ
ro.build.version.incremental=ZSJPJ
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2.1
ro.build.date=Sat Mar 12 16:37:36 KST 2011
ro.build.date.utc=1299915456
ro.build.type=user
ro.build.user=root
ro.build.host=avad-server
ro.build.tags=release-keys
ro.product.model=GT-I9000
ro.product.brand=samsung
ro.product.name=GT-I9000
ro.product.device=GT-I9000
ro.product.board=GT-I9000
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=zh
ro.product.locale.region=HK
ro.wifi.channels=
ro.board.platform=s5pc110
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I9000
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9000-user 2.2.1 FROYO ZSJPJ release-keys
ro.camera.sound.forced=1
ro.build.fingerprint=samsung/GT-I9000/GT-I9000/GT-I9000:2.2.1/FROYO/ZSJPJ:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I9000ZSJPJ
ro.build.hidden_ver=I9000ZSJPJ
ro.build.changelist=951673
ro.tether.denied=false
# end build properties
#
# system.prop for smdkc110
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
dalvik.vm.heapsize=48m
dalvik.vm.execution-mode=int:jit
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version=131072
#
# ADDITIONAL_BUILD_PROPERTIES
#
windowsmgr.max_events_per_sec=55
keyinputqueue.use_finger_id=true
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
keyguard.no_require_sim=true
ro.config.ringtone=01_Samsung_tune.ogg
ro.config.notification_sound=01_Sherbet.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.opengles.version=131072
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Sent from my GT-I9000 using XDA App

and available from kies
Sent from my GT-I9000 using XDA App

sorry for misleading, that is 3 chinese and 1 korean, and 2 english
Sent from my GT-I9000 using XDA App

Any major performance change in this firmware, Is the browser bug fixed?
How is the overall performance of the firmware compare JSJPG and JS8.
As its new firmware and couple of hours back its Released, Kindly check the battery performance and post the feedback.
Thanks

quadrant score are nearly the same, but whole system seems more responsive when compare to jpg, browser bug not fix
Sent from my GT-I9000 using XDA App

Any more feedback as to how this base feels after JS8 or JPG? Makes sense to upgrade?
Swyped from another GALAXY

What about input languages?

input language is the same as jpg
something strange about this firmware:
1. phone get much hotter, I never feel this before. (JPG 41C, JPJ 44C when using xda app)
2. I don't know if this is a feature of xda app or not, I active screen capture function when I am using xda app, and I don't have any screen capture app install
update: same as galaxy tab, it got screen capture feature itself, is this the same for other firmware?
Sent from my GT-I9000 using XDA App

Please beware, the firmware posted at post #1 does include bootloaders.
I'm now uploading the 3 file firmware with no bootloaders.
Edit.
Here is the firmware divided on 3 files, no bootloaders are included, so it's safe.
Multiupload link: Download (157.5 MB)
PDA: ZSJPJ
Modem: ZSJPG
CSC: ZSJPG
Good luck flashing your devices.

post deleted

I was experiencing increased heat on the blackplate around the camera with JS8 and had posted that experience to the thread. Pretty sure I experienced that with an earlier ROM, can't recall which though.
DummyPLUG said:
input language is the same as jpg
something strange about this firmware:
1. phone get much hotter, I never feel this before. (JPG 41C, JPJ 44C when using xda app)
2. I don't know if this is a feature of xda app or not, I active screen capture function when I am using xda app, and I don't have any screen capture app install
update: same as galaxy tab, it got screen capture feature itself, is this the same for other firmware?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse

[Ramad] said:
Please beware, the firmware posted at post #1 does include bootloaders.
I'm now uploading the 3 file firmware with no bootloaders.
Edit.
Here is the firmware divided on 3 files, no bootloaders are included, so it's safe.
Multiupload link: Download (157.5 MB)
PDA: ZSJPJ
Modem: ZSJPG
CSC: ZSJPG
Good luck flashing your devices.
Click to expand...
Click to collapse
Thanks Ramad, I can always count on you for 3 files

The kernel in this firmware is interesting. It should let us download apps bigger than 30MB (/cache partition) from the Market.

DummyPLUG said:
input language is the same as jpg
something strange about this firmware:
1. phone get much hotter, I never feel this before. (JPG 41C, JPJ 44C when using xda app)
2. I don't know if this is a feature of xda app or not, I active screen capture function when I am using xda app, and I don't have any screen capture app install
update: same as galaxy tab, it got screen capture feature itself, is this the same for other firmware?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I figured they were the same as JPG but I cannot find a list of input languages for JPG either so I thought this was as good a place as any to ask... Is there at least english, spanish and korean as inoput langs? thanks a bunch.

hardcore said:
The kernel in this firmware is interesting. It should let us download apps bigger than 30MB (/cache partition) from the Market.
Click to expand...
Click to collapse
Perhaps an OTA?
Mandado desde el móvil usando los dedos

Someone said that this JPJ has fixed the bug that JPG will format your internal SD card when you change the battery. Is it true?

Swype got english, chinese and korean only

[ROM][2.2.1] JPJPM Arabic-Urdu-Persian [Download]

Froyo 2.2.1 I9000JPJPM: (No bootloaders)
PDA: JPJPM
MODEM: JXJPF
CSC: OJPJPL (MultiCSC: EGY, JED, KSA, MAT, MED, MID, MMC, MWD, PAK, THR, WAN, XSG, XSS)
Multiupload Link: Download (147.6 MB) (Double-Click to extract)
The firmware is ultra compressed 7zip SFX-file to save your time and bandwidth, the firmware is a 3 files firmware, flash with or without re-partition.
The firmware has been passed to me by a member at XDA.
Build.prop:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=FROYO
ro.build.display.id=FROYO.JPJPM
ro.build.version.incremental=JPJPM
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2.1
ro.build.date=2011. 02. 17. (목) 14:41:30 KST
ro.build.date.utc=1297921290
ro.build.type=user
ro.build.user=root
ro.build.host=SE-S606
ro.build.tags=release-keys
ro.product.model=GT-I9000
ro.product.brand=samsung
ro.product.name=GT-I9000
ro.product.device=GT-I9000
ro.product.board=GT-I9000
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=ar
ro.product.locale.region=AE
ro.wifi.channels=
ro.board.platform=s5pc110
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I9000
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9000-user 2.2.1 FROYO JPJPM release-keys
ro.build.fingerprint=samsung/GT-I9000/GT-I9000/GT-I9000:2.2.1/FROYO/JPJPM:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I9000JPJPM
ro.build.hidden_ver=I9000JPJPM
ro.build.changelist=913489
ro.tether.denied=false
# end build properties
#
# system.prop for smdkc110
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
dalvik.vm.heapsize=48m
dalvik.vm.execution-mode=int:jit
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version=131072
#
# ADDITIONAL_BUILD_PROPERTIES
#
windowsmgr.max_events_per_sec=55
keyinputqueue.use_finger_id=true
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
keyguard.no_require_sim=true
ro.config.ringtone=01_Samsung_tune.ogg
ro.config.notification_sound=01_Sherbet.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.opengles.version=131072
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

Has anyone tried this yet compared to others? I mean, surely they will focus on gingerbread from now on.
Sent from my ever changing Galaxy S

Is this a stock Rom or custom Rom ? the first jpm rom was custom rom and it was rooted !!

arashkhaan said:
Is this a stock Rom or custom Rom ? the first jpm rom was custom rom and it was rooted !!
Click to expand...
Click to collapse
This is not a costume firmware, it's good, it's fast.

Thanks Ramad... I'm using the pre-rooted & deodexed version of JPJPM... Is this one the original one? I mean non-rooted and not deodexed?
By the way it is still not available on KIES...

buntoo said:
Thanks Ramad... I'm using the pre-rooted & deodexed version of JPJPM... Is this one the original one? I mean non-rooted and not deodexed?
By the way it is still not available on KIES...
Click to expand...
Click to collapse
This is a leaked original firmware, it's why I did not write that it was a release.
I'm now deodexing this firmware, adding the final touches before adding it to deodexed stock firmware collection.

Do you mind providing the modem file? Cwm preferable but bin file is fine.
Is there a modem repository in this i9000 forum? I know there's one in the captivate forum, just seeing if this is a new or old modem here. Thanks
Sent from my SAMSUNG-SGH-I897 using Tapatalk

zerkai said:
Do you mind providing the modem file? Cwm preferable but bin file is fine.
Is there a modem repository in this i9000 forum? I know there's one in the captivate forum, just seeing if this is a new or old modem here. Thanks
Click to expand...
Click to collapse
Pick the Modem you like : http://forum.xda-developers.com/showpost.php?p=11256537&postcount=2

This rom have phone.apk force close bug ??

CF-root
hi
I need cf-root
plz help

ArmaN70 said:
hi
I need cf-root
plz help
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=788108

Naeem786 said:
http://forum.xda-developers.com/showthread.php?t=788108
Click to expand...
Click to collapse
Which I use for JPJPM ?

Naeem786 said:
This rom have phone.apk force close bug ??
Click to expand...
Click to collapse
everything works fine and there's no force close bug sofar (it's not like that one! )
ArmaN70 said:
hi
I need cf-root
plz help
Click to expand...
Click to collapse
there's no cf-root for the kernel of this rom at the moment
you can go to this topic and ask Chainfire to make that! (btw I asked him )
http://forum.xda-developers.com/showthread.php?t=788108

ArmaN70 said:
hi
I need cf-root
plz help
Click to expand...
Click to collapse
If you only want to root then try SuperOneClick

[Ramad] said:
If you only want to root then try SuperOneClick
Click to expand...
Click to collapse
thx but i need cf-root for 2e recovery
So we have to wait

ArmaN70 said:
thx but i need cf-root for 2e recovery
So we have to wait
Click to expand...
Click to collapse
Flash a kernel like voodoo 5.5 or speedmod...

ArmaN70 said:
thx but i need cf-root for 2e recovery
So we have to wait
Click to expand...
Click to collapse
Flash CF-Root XWJS8 kernel, that will do it.

Works great!!! Thanks a lot! The only minor thing that I've noticed battery is draining quickly... I don't know if there is a patch for this... but so far so good...Thanks again!

This Rom has problem when it connects to my bluetooth audio system after sometime it just disconnect !!!

I've not a single problem with this ROM...

[ROM][ICS Firmwares] T989UVLE1 [06.05.2012][Android 4.0.3]

T989UVLE1
Base Firmware: T989UVLE1(4.0.3)
Modem: T989UVLE1
CSC: T989TMBLE1
Build Date: 06-05-2012
Changlist: 508451
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.display.id=IML74K.UVLE1
ro.build.version.incremental=UVLE1
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Sun May 6 15:02:39 KST 2012
ro.build.date.utc=1336284159
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEI-46
ro.build.tags=release-keys
ro.product.model=SGH-T989
ro.product.brand=samsung
ro.product.name=SGH-T989
ro.product.device=SGH-T989
ro.product.board=MSM8660_SURF
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=msm8660
# ro.build.product is obsolete; use ro.product.device
ro.build.product=SGH-T989
ro.tether.denied=false
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SGH-T989-user 4.0.3 IML74K UVLE1 release-keys
ro.build.fingerprint=samsung/SGH-T989/SGH-T989:4.0.3/IML74K/UVLE1:user/release-keys
ro.build.characteristics=default
# Samsung Specific Properties
ro.build.PDA=T989UVLE1
ro.build.hidden_ver=T989UVLE1
ro.build.changelist=508451
# end build properties
Download:
https://hotfile.com/dl/159499514/0d5b11c/SGH-T989_TMB_T989UVLE1_T989TMBLE1_T989UVLE1.zip.html

Awesome dude

Flash in recovery? Or odin?
Sent from my SGH-T989D using xda premium

I assume this is just stock and if I install it, it will unroot my phone?

It should only unroot if you used Kies like I did. If you use ODIN or CWM, it should not undo root. If it does, re-install CWM and install the latest SU 3.0.7 (I believe) from the internal flash. I've already been debloating the 4.0.3 with root explorer and it only took me 15 min max after ICS was done installing via KIES.

anyone tried it?

Im guessing this is for odin right?
Sent from my SGH-T989D using xda premium

casonswag said:
Im guessing this is for odin right?
Sent from my SGH-T989D using xda premium
Click to expand...
Click to collapse
yeah, oh well

You should be able to drag it to your internal SD as a zip and install via CWM.

Downloading now, currently on CM9 ICS. Will report back
Sent from tmobile GSII running Android 1.6 beta

Anyone Recommend Doing The Update Thru Kies Even Tho Im On Juggernaut 5.0?
Or Should I Just Flash the File Attached To This Thread, i Dont Mind If It Unroots... (UNroot Method Preferable)
Thanks In Advance...

Any reports so far ? About to flash but was wondering if anybody encounter any issues?
Artificial Intelligence is no match for natural stupidity....

VictorNYC said:
Any reports so far ? About to flash but was wondering if anybody encounter any issues?
Artificial Intelligence is no match for natural stupidity....
Click to expand...
Click to collapse
Not thread jacking but the odin file i posted in development has been tested by me and at least 3 other people and is working.

Couldn't tell from reading the thread, is this a flashable zip or one extracts it to flash a Odin tar?
Sent from the Darkside, ICS style

xsteven77x said:
Not thread jacking but the odin file i posted in development has been tested by me and at least 3 other people and is working.
Click to expand...
Click to collapse
Problem is I'm away from my computer for another two days so unless I buy a cheap laptop I have nothing until I get back to NYC Thursday morning...
Artificial Intelligence is no match for natural stupidity....

xsteven77x said:
Not thread jacking but the odin file i posted in development has been tested by me and at least 3 other people and is working.
Click to expand...
Click to collapse
But thanks anyway, I have been monitoring your thread since last night .
Artificial Intelligence is no match for natural stupidity....

Why does the date say 6/5
if this is the new file?

have you had any troubles with screen calibration on this? i did the update over odin and now after i turn on the screen for like 3 seconds the calibration goes off on my phone. when i touch my thumb at the bottom of the screen it thinks it's in the middle

Link is dead. All hotfile links are dead. Hotfile got shut down.

Samsung Galaxy Nexus Yakjuzs ICL53F 4.0.2 build.prop

Hello
Anyone can upload a unmodified stock build.prop file from Samsung Galaxy Nexus Yakjuzs ICL53F 4.0.2?
The file is under /system
You can access the file by using Root Browser.
I need it to update my phone from 4.0.2 to 4.0.4.
Thank you

antchee said:
Hello
Anyone can upload a unmodified stock build.prop file from Samsung Galaxy Nexus Yakjuzs ICL53F 4.0.2?
The file is under /system
You can access the file by using Root Browser.
I need it to update my phone from 4.0.2 to 4.0.4.
Thank you
Click to expand...
Click to collapse
use YAKJUXW ICL53F..i9250xwkl2 build.prop and edit the device information to Yakjuzs..

manumanfred said:
use YAKJUXW ICL53F..i9250xwkl2 build.prop and edit the device information to Yakjuzs..
Click to expand...
Click to collapse
Or download the stock ROM and pull the build.prop from it.

manumanfred said:
use YAKJUXW ICL53F..i9250xwkl2 build.prop and edit the device information to Yakjuzs..
Click to expand...
Click to collapse
How is he going to know what to change? If he knew that, he prob wouldn't be asking for the file.
JaiaV said:
Or download the stock ROM and pull the build.prop from it.
Click to expand...
Click to collapse
Where is a stock yakjuzs ICL53F ROM?
Sent from my Galaxy Nexus using Tapatalk 2

manumanfred said:
use YAKJUXW ICL53F..i9250xwkl2 build.prop and edit the device information to Yakjuzs..
Click to expand...
Click to collapse
I have already tried that, it failed.
If the build.prop file been edited, update will failed.
Because I have changed the DPI before, and have changed it back,
now any update will fail.
If someone create a backup of the ROM using CWM it will help.

JaiaV said:
Or download the stock ROM and pull the build.prop from it.
Click to expand...
Click to collapse
There is no stock ROM for 4.0.2 Yakjuzs.

The build.prop file cannot be edited.
If it has been edited, any update to the phone will failed.
Now my phone will stay on 4.0.2 until I flashed ot with Yakju.
But my phone has to be running Yakjuzs as other builds do not have the Samsung Chinese input.
And if I flashed my phone, my warranty will be voided .

antchee said:
The build.prop file cannot be edited.
If it has been edited, any update to the phone will failed.
Now my phone will stay on 4.0.2 until I flashed ot with Yakju.
But my phone has to be running Yakjuzs as other builds do not have the Samsung Chinese input.
And if I flashed my phone, my warranty will be voided .
Click to expand...
Click to collapse
If I am not mistaken, takju JRN84D has Chinese input.
As for your warranty, if you do a backup of you yakjzs build, you can always restore it. Besides, I have never heard of Samsung refusing warranty service because of yakju or takju being used...
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
How is he going to know what to change? If he knew that, he prob wouldn't be asking for the file.
Where is a stock yakjuzs ICL53F ROM?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
How he's going to change:
Yakjuzs is not Yakjuwx but if editing the device information in build .prop for Yakjuzs device it might work, just device name needs modifying, other texts should be really similar in all GSM GNex 4.0.2 ROMs..
(it's easy, but might not work if something is badly edited..)

manumanfred said:
How he's going to change:
Yakjuzs is not Yakjuwx but if editing the device information in build .prop for Yakjuzs device it might work, just device name needs modifying, other texts should be really similar in all GSM GNex 4.0.2 ROMs..
(it's easy, but might not work if something is badly edited..)
Click to expand...
Click to collapse
Build.prop files are not similar enough across different builds to just change "yakjuxw" to "yakjuzs" where ever it appears.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
Build.prop files are not similar enough across different builds to just change "yakjuxw" to "yakjuzs" where ever it appears.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
example:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=ICL53F
ro.build.display.id=ICL53F
ro.build.version.incremental=235179
ro.build.version.sdk=14
ro.build.version.codename=REL
ro.build.version.release=4.0.2
ro.build.date=Thu Dec 8 01:24:15 UTC 2011
ro.build.date.utc=1323307455
ro.build.type=user
ro.build.user=android-build
ro.build.host=vpbs3.mtv.corp.google.com
ro.build.tags=release-keys
ro.product.model=Galaxy Nexus
ro.product.brand=google
ro.product.name=yakju
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=yakju-user 4.0.2 ICL53F 235179 release-keys
ro.build.fingerprint=google/yakju/maguro:4.0.2/ICL53F/235179: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
#
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.config.ringtone=Girtab.ogg
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Cesium.ogg
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.com.android.wifi-watchlist=GoogleGuest
ro.error.receiver.system.apps=com.google.android.feedback
ro.setupwizard.enterprise_mode=1
keyguard.no_require_sim=true
drm.service.enabled=true
camera.flash_off=0
ro.com.google.mcc_fallback=262
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
To ---->
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=ICL53F
ro.build.display.id=ICL53F
ro.build.version.incremental=235179
ro.build.version.sdk=14
ro.build.version.codename=REL
ro.build.version.release=4.0.2
ro.build.date=Thu Dec 8 01:24:15 UTC 2011
ro.build.date.utc=1323307455
ro.build.type=user
ro.build.user=android-build
ro.build.host=vpbs3.mtv.corp.google.com
ro.build.tags=release-keys
ro.product.model=Galaxy Nexus
ro.product.brand=google
ro.product.name=yakjuzs
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=yakjuzs-user 4.0.2 ICL53F 235179 release-keys
ro.build.fingerprint=google/yakjuzs/maguro:4.0.2/ICL53F/235179: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
#
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.config.ringtone=Girtab.ogg
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Cesium.ogg
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.com.android.wifi-watchlist=GoogleGuest
ro.error.receiver.system.apps=com.google.android.feedback
ro.setupwizard.enterprise_mode=1
keyguard.no_require_sim=true
drm.service.enabled=true
camera.flash_off=0
ro.com.google.mcc_fallback=262
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
if you check Yakjuxw build.prop (stock 4.0.2) it is same, only the device information is different..
EDIT: also if the build is not only ICL53F and it is icl53f.i9250#### then you have to add it to build.prop too..
UTC time text and other maybe not needed to edit because it should still update 4.0.2 if it has the system/etc/updatecmds folder ...?

manumanfred said:
example:
if you check Yakjuxw build.prop (stock 4.0.2) it is same, only the device information is different..
EDIT: also if the build is not only ICL53F and it is icl53f.i9250#### then you have to add it to build.prop too..
UTC time text and other maybe not needed to edit because it should still update 4.0.2 if it has the system/etc/updatecmds folder ...?
Click to expand...
Click to collapse
Not sure what build.prop files you are looking at, but I just looked at yakju 4.0.4 and yakjukr 4.0.4, and there are many differences. See the attachments... And although I don't have yakjuzs or yakjuxw build.prop files handy, I am confident that it applies to those as well...
You cannot just make a few changes without knowing what goes in the fields.

efrant said:
Not sure what build.prop files you are looking at, but I just looked at yakju 4.0.4 and yakjukr 4.0.4, and there are many differences. See the attachments... And although I don't have yakjuzs or yakjuxw build.prop files handy, I am confident that it applies to those as well...
You cannot just make a few changes without knowing what goes in the fields.
Click to expand...
Click to collapse
on those build.prop:s is not really much difference..
but whatever...
I don't think that there is many users with yakjuzs so I don't have yakjuzs build.prop but i know it it is GSM Galaxy Nexus and yakju/yakjuxw/other buil build.prop file (ICL53F) can be edited for yakjuzs which still works and then it should let to update it whatever does the build.prop look like the stock yakjuzs build.prop, only the device information matters if want to flash update, but I'm not pretty sure can it flash the OTA update then, it should let flash it because it overwrites the build.prop to the newer build.prop.. ?
I'm not really Android expert but I've edited build.prop file on ZTE Blade, Samsung Jet (JetDroid), and on Gnex many times and still should have to let update GNex if the build.prop doesn't look 100% same as it have to be..
and my English is not so good, so I don't know did you understood what I wrote..

manumanfred said:
on those build.prop:s is not really much difference..
but whatever...
I don't think that there is many users with yakjuzs so I don't have yakjuzs build.prop but i know it it is GSM Galaxy Nexus and yakju/yakjuxw/other buil build.prop file (ICL53F) can be edited for yakjuzs which still works and then it should let to update it whatever does the build.prop look like the stock yakjuzs build.prop, only the device information matters if want to flash update, but I'm not pretty sure can it flash the OTA update then, it should let flash it because it overwrites the build.prop to the newer build.prop.. ?
I'm not really Android expert but I've edited build.prop file on ZTE Blade, Samsung Jet (JetDroid), and on Gnex many times and still should have to let update GNex if the build.prop doesn't look 100% same as it have to be..
and my English is not so good, so I don't know did you understood what I wrote..
Click to expand...
Click to collapse
Not much difference? Are you joking? They are completely different.
And I can tell you the an update will NOT work if the build.prop file is not EXACTLY the same. The updater-script file checks the MD5 hash of the build.prop. It it does not match, the update will fail.

efrant said:
Not much difference? Are you joking? They are completely different.
And I can tell you the an update will NOT work if the build.prop file is not EXACTLY the same. The updater-script file checks the MD5 hash of the build.prop. It it does not match, the update will fail.
Click to expand...
Click to collapse
Okay!..

One yakjuzs buildprob coming. I have it, just give me couple of hours and I'll post it.
One question though. What changes the values in build prop? Beside changing dpi.

efrant said:
If I am not mistaken, takju JRN84D has Chinese input.
As for your warranty, if you do a backup of you yakjzs build, you can always restore it. Besides, I have never heard of Samsung refusing warranty service because of yakju or takju being used...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Flashing the phone will void the warranty in HK.
I read a lot of posts (Chinese websites) that people got the warranty voided becuase of flashing their Samsung phones.
I found someone have uploaded a 4.0.4 Yakjuzs CWM backup image, if I can't the build.prop file for 4.0.2, I will restore my phone using the backup image.

Emhalwis said:
One yakjuzs buildprob coming. I have it, just give me couple of hours and I'll post it.
One question though. What changes the values in build prop? Beside changing dpi.
Click to expand...
Click to collapse
All I have changed was the DPI, I changed it back and now I can't update to 4.0.4.
I can't wait for your build.prop file. Just make sure it is from 4.0.2 Yakjuzs (GMS) and the file must be unedited/untouched.
You are my only hope!!

now, what are you willing to give in return, since i had to charge my phone, backup my rom, restore my backup then restore my rom again?
kidding, here is your file, good luck updating.

Emhalwis said:
now, what are you willing to give in return, since i had to charge my phone, backup my rom, restore my backup then restore my rom again?
Click to expand...
Click to collapse
Why did you have to do that????
You could have just extracted the one file from your backup without restoring the whole backup...

I927UCLG9 - "Official" Leak - 4.0.4 ICS

WARNING:
This contains bootloaders, is for the AT&T Captivate Glide only, will wipe your internal sdcard... Flash at your own risk! No one but you can be held responsible for your actions.
Thanks to Roeni for taking the plunge as the first to flash!
How to Root:
Flash CWM or TWRP with odin, boot into recovery and flash a SuperUser zip.
Download:
http://www.gigashare.in/40e09
MD5: E04C404651BB7E0ED3BF0CD65C24BC9A
Other info:
This is considered beta software until it is officially pushed out by AT&T/Samsung. Leaks do NOT come with changelogs, so don't ask, no one knows. I won't be providing any other versions of this leak, use the oneclick exe or wait for someone else to build a cwm/twrp flashable.
FLAMING or TROLLING:
The thread will be closed and links deleted.
Build.prop
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IMM76D
ro.build.display.id=IMM76D
ro.build.version.incremental=UCLG9
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Fri Jul 27 23:37:33 KST 2012
ro.build.date.utc=1343399853
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-121
ro.build.tags=release-keys
ro.product.model=SGH-I927
ro.product.brand=samsung
ro.product.name=SGH-I927
ro.product.device=SGH-I927
ro.product.board=SGH-I927
ro.product.cpu.abi=armeabi-v7a
# Samsung Specific Properties
ro.build.PDA=I927UCLG9
ro.build.hidden_ver=I927UCLG9
ro.build.changelist=970642
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=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=SGH-I927
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SGH-I927-user 4.0.4 IMM76D UCLG9 release-keys
ro.build.fingerprint=samsung/SGH-I927/SGH-I927:4.0.4/IMM76D/UCLG9:user/release-keys
ro.build.characteristics=default
# end build properties
dalvik.vm.heapsize=64m
ro.opengles.version = 131072
wifi.interface=wlan0
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
#rild.libpath=/system/lib/libril-icera.so
#rild.libargs=-e wwan0
persist.sys.storage_preload=1
#ril.fastdormancy_to=50
# Icera fild
#modem.fild.rootdir=/data/rfs
#modem.fild.blocksize=65528
#modem.fild.baudrate=3500000
#modem.fild.hif=0
#modem.fild.coredump=enabled
#modem.fild.coredumpdir=/data/rfs/data/debug
#modem.powercontrol=disabled
#modem.power.device=/sys/class/gpio/gpio169/value,0,1
#ro.ril.devicename=/dev/ttyACM1
#
# ADDITIONAL_BUILD_PROPERTIES
#
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.com.google.clientidbase=android-samsung
ro.com.google.clientidbase.ms=android-att-us
ro.com.google.clientidbase.am=android-att-us
ro.com.google.clientidbase.yt=android-samsung
ro.com.google.clientidbase.gmm=android-samsung
ro.error.receiver.default=com.samsung.receiver.error
ro.monkey=0
ro.com.google.gmsversion=4.0_r3
ro.config.ringtone=ATT_Firefly.ogg
ro.config.notification_sound=S_Sherbet_Default_message.ogg
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.kernel.qemu=0
ro.secdirenc=true
ro.secsddecryption=true
ro.secfulldirenc=true
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

Nice. Darn on vacation an cant flash on my glide but directing dman right away...
---------- Post added at 03:52 PM ---------- Previous post was at 03:48 PM ----------
Will post a superuser zip tonight.
DO NOT FLASH YET IF YOU NEED ROOT!

I really want to try it, but i am affraid of bricking my device!

I'm literally on the other side of the world right now and cannot afford to take the risk. And I've got the Rogers' version, so it might backfire if it does some kind of strict device ID checking(even if there is no hardware difference!).
I can say the download seems legit/safe. No viruses and when you run it you get an Odin-like interface! So excited, wish I could take the plunge...!

HELL YEAH!
Tested working so far:
- GSM Network (Germany)
- Edge
- Wifi
- Camera
- Audio
See this thread for a full list of the things i've tested so far: http://forum.xda-developers.com/showpost.php?p=30184848&postcount=17

Roeni said:
https://www.dropbox.com/s/z1re33jg5of55fs/2012-08-14%2000.25.28.jpg
HELL YEAH!
Click to expand...
Click to collapse
Thanks for the image! I will put it in the op!
Is it running smooth?

designgears said:
Thanks for the image! I will put it in the op!
Is it running smooth?
Click to expand...
Click to collapse
So far there are no issues.
I'm connected to my wifi, downloaded some updates from play store, successfully sent an sms. for some other tests see my post above.
---
...a LOT of Blot is installed xD

Excellent, looking forward to installing this tonight.

I'm about to try. Thank you!

The only thing holding me back is lack of root. I can't wait.

antharr said:
The only thing holding me back is lack of root. I can't wait.
Click to expand...
Click to collapse
lack of root?
just flash cwm recovery with odin and flash the ICS superuser zip.

designgears said:
lack of root?
just flash cwm recovery with odin and flash the ICS superuser zip.
Click to expand...
Click to collapse
Sorry. I was under the impression that this was leaked and stock. Thank you for providing this. You sir......are awesome!

It boots on i927r (Rogers) and everything seems to be working properly!

Just a question for those who have flashed
Is it touchwiz 4 or UX ( the tw that comes on the gsiii?)
Hopefully this is all dman needs to get stock aosp... or better yet my favorite on my gsiii aokp
Sent from my SGH-I747 using xda premium

designgears said:
lack of root?
just flash cwm recovery with odin and flash the ICS superuser zip.
Click to expand...
Click to collapse
Where can i find this superuser.zip?

Aquethys said:
Just a question for those who have flashed
Is it touchwiz 4 or UX ( the tw that comes on the gsiii?)
Hopefully this is all dman needs to get stock aosp... or better yet my favorite on my gsiii aokp
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Settings -> Applications says: TwLauncher Version 4.0.4-UCLG9
Did you mean this?

Gab1288 said:
Where can i find this superuser.zip?
Click to expand...
Click to collapse
I Second This!

superuser zip
Worked on my galaxy s 3...should work on you guys. If not Google is your friend. If it does work OP feel free to add it
MAKE A NANDROID Backup!
By the by, can someone pull the proprietary files so dman can finish aosp ICS?
Feel free to hit thanks
Sent from my SGH-I747 using xda premium

Aquethys said:
superuser zip
Worked on my galaxy s 3...should work on you guys. If not Google is your friend. If it does work OP feel free to add it
MAKE A NANDROID Backup!
By the by, can someone pull the proprietary files so dman can finish aosp ICS?
Feel free to hit thanks
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
How do i extract them?

If it helps, I could flash this leak, and then make a back-up using CWM and provide it somehow? Could the drivers be pulled from that? Just let me know!