Database Info

[ROM] I9003DDKP2 [29.11.2011][Android 2.3.6]

I9003DDKP2:
PDA: I9003DDKP2
Phone: I9003DDKP4
CSC: I9003ODDKPH
Code:
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.DDKP2
ro.build.version.incremental=DDKP2
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.6
ro.build.date=Tue Nov 29 22:10:12 KST 2011
ro.build.date.utc=1322572212
ro.build.type=user
ro.build.user=root
ro.build.host=DELL83
ro.build.tags=release-keys
ro.product.model=GT-I9003
ro.product.brand=samsung
ro.product.name=GT-I9003
ro.product.device=GT-I9003
ro.product.board=GT-I9003
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=omap3
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I9003
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9003-user 2.3.6 GINGERBREAD DDKP2 release-keys
ro.build.fingerprint=samsung/GT-I9003/GT-I9003:2.3.6/GINGERBREAD/DDKP2:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I9003DDKP2
ro.build.hidden_ver=I9003DDKP2
ro.build.changelist=765780
ro.flash.resolution=720
# end build properties
Download:
http://hotfile.com/dl/137639190/7f30c1f/GT-I9003_INU_I9003DDKP2_I9003ODDKPH_I9003DDKP4.rar.html
Pass: sampro.pl

What region is this? GB? Great Britain? European ROM?

inciongd said:
What region is this? GB? Great Britain? European ROM?
Click to expand...
Click to collapse
DD is Indian Version

Thank 4 share

Mirrors (same password) :
http://www.multiupload.com/ERY6N4JQY7
http://www.mediafire.com/?vgmhb642ahrtggp

Is this update available through keys?

Surprisingly, exact same size "362,411KB" for both DDKP1 and DDKP2.
Don't know what is the change?
Also lets see if Amit universal root works on this also or not?
---------- Post added at 10:02 PM ---------- Previous post was at 10:00 PM ----------
shardul_seth said:
Is this update available through keys?
Click to expand...
Click to collapse
btw It's Samsung Kies not Keys and if you are here, then why looking for **** Kies?

Universal root works fine
Sent from my GT-I9003 using XDA App

anyone tested this??

Installed and touchscreen is smooth.....will update later...
Sent from my GT-I9003 using XDA App

Yes, the ROM is very smooth and fast!!

jaskiratsingh said:
Universal root works fine
Sent from my GT-I9003 using XDA App
Click to expand...
Click to collapse
push mail?

fengjia1313 said:
push mail?
Click to expand...
Click to collapse
Not fixed
Sent from my GT-I9003 using XDA App

Good Rom
This is a nice and smooth Indian Rom..Installed KPE and then DDKP2
- ROM is very smooth..even after installing over 100 apps/games and having many widgets, the home screen scrolling is smooth..
- Quadrant in the range of 1200-1300
- Antutu around 2700
- Stock video player plays 720p smoothly
- Battery life yet to check

kirankowshik said:
This is a nice and smooth Indian Rom..Installed KPE and then DDKP2
- ROM is very smooth..even after installing over 100 apps/games and having many widgets, the home screen scrolling is smooth..
- Quadrant in the range of 1200-1300
- Antutu around 2700
- Stock video player plays 720p smoothly
- Battery life yet to check
Click to expand...
Click to collapse
I am currently on DDKP1 & in last week i made a purchase of some apps from android market. So if i flash this will i be able to restore those purchased apps?
Anyone can please shed some more light on usability of DDKP2 in comparison to DDKP1.
PS. My phone is NOT rooted.
Regards,

harshaldesai said:
I am currently on DDKP1 & in last week i made a purchase of some apps from android market. So if i flash this will i be able to restore those purchased apps?
Anyone can please shed some more light on usability of DDKP2 in comparison to DDKP1.
PS. My phone is NOT rooted.
Regards,
Click to expand...
Click to collapse
Yes, the market restores your apps automatically. Kies will be safer for you.
The new Rom is much smoother.

kirankowshik said:
This is a nice and smooth Indian Rom..Installed KPE and then DDKP2
- ROM is very smooth..even after installing over 100 apps/games and having many widgets, the home screen scrolling is smooth..
- Quadrant in the range of 1200-1300
- Antutu around 2700
- Stock video player plays 720p smoothly
- Battery life yet to check
Click to expand...
Click to collapse
what have u done after KP2? root? ext4?
if it's not in ext4 format than having 2700pts in antutu, this rom is awesome.
stock KPQ with ext4 reaches 2500-2600.

On DDKP2 now...smoothest rom i ever experienced
with UC kernel V6, no ext4 convert
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

plz convert to ext4 and benchmark then!

maxoooo said:
plz convert to ext4 and benchmark then!
Click to expand...
Click to collapse
Above benchmark is with ext4. I testes this on rfs and is about 1500-1600

optimus black KU5900 ICS is out

This phone has the same specs as the i9003: CPU 1 GHz Cortex-A8 processor, PowerVR SGX530 GPU, TI OMAP 3630 chipset
ICS rom is out, --> http://csmg.lgmobile.com:9002/swdata/RNDTESTSW/LGKU5900/KTF/V30g_00/V30G_00.kdz
This means fully functional ICS will be possible on i9003, waiting for Dhiru.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IMM76L
ro.build.display.id=IMM76L.LG-KU5900-V30g.48103277
ro.build.version.incremental=LG-KU5900-V30g.48103277
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Sun Sep 2 10:47:23 KST 2012
ro.build.date.utc=1346550443
ro.build.type=user
ro.build.user=ilnam.yu
ro.build.host=ics-server4
ro.build.tags=release-keys
ro.product.model=LG-KU5900
ro.product.brand=lge
ro.product.name=black_kt_kr
ro.product.device=black
ro.product.board=black
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LGE
ro.product.locale.language=ko
ro.product.locale.region=KR,en
ro.wifi.channels=
ro.board.platform=omap3
# ro.build.product is obsolete; use ro.product.device
ro.build.product=black
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=black_kt_kr-user 4.0.4 IMM76L LG-KU5900-V30g.48103277 release-keys
ro.build.fingerprint=lge/black_kt_kr/black:4.0.4/IMM76L/LG-KU5900-V30g.48103277:user/release-keys
ro.build.characteristics=default
# end build properties
rild.libpath=/system/lib/lge-ril.so
rild.libargs=-d /dev/ttyspi0
alsa.mixer.playback.master=DAC2 Analog \
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.build.target_operator=KT
ro.build.target_country=KR
ro.build.target_region=KR
ro.lge.swversion=LG-KU5900-V30g
ro.com.google.clientidbase=android-lge
ro.com.google.clientidbase.ms=android-kt-kr
ro.com.google.clientidbase.am=android-kt-kr
ro.com.google.clientidbase.gmm=android-lge
ro.com.google.clientidbase.yt=android-lge
ro.afwdata.LGfeatureset=KTBASE
ro.com.android.dateformat=MM-dd-yyyy
ro.lge.audio_soundexception=true
ro.lge.audio_soundprofile=true
ro.config.ringtone=[LG]_01_Honey_Honey_Baby.ogg
ro.config.notification_sound=01_AcousticGuitar.ogg
ro.config.alarm_alert=01_Classmate.ogg
ro.com.android.dataroaming=false
ime_vibration_pattern=0:15
wlan.chip.vendor=brcm
wlan.chip.version=bcm43291
wifi.supplicant_scan_interval=20
wifi.lge.patch=true
wifi.lge.hanglessid=false
ro.build.target_ril_platform=ifx
persist.radio.rr.enable=1
ro.sf.lcd_density=240
com.ti.omap_enhancement=true
opencore.asmd=0
ro.config.nocheckin=yes
wifi.interface=wlan0
alsa.mixer.capture.master=Analog
ro.opengles.version=131072
jpeg.libskiahw.decoder.enable=1
jpeg.libskiahw.decoder.thresh=100000
ro.tether.denied=false
persist.service.main.enable=0
persist.service.system.enable=0
persist.service.radio.enable=0
persist.service.events.enable=0
persist.service.kernel.enable=0
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
keyguard.no_require_sim=true
ro.cdma.home.operator.alpha=KT
ro.cdma.home.operator.numeric=311220
rild.libpath=/system/lib/lge-ril.so
ro.telephony.default_network=0
ro.radio.use-ppp=yes
ro.lge.capp_optimusui=true
ro.lge.capp_core=true
ro.lge.capp_drm=true
ro.lge.capp_divx_drm=true
ro.lge.capp_almond=true
ro.lge.capp_resource=true
ro.lge.capp_wapservice=true
ro.lge.capp_osp=true
ro.lge.capp_quickclip_key=true
ro.lge.lazy_service_bringup=true
ro.lge.capp_touch_scroller=true
ro.lge.capp_touch_ldi=true
ro.lge.capp_key_light_off=true
ro.lge.capp_key_exception=true
ro.lge.capp_keyled_timeout=true
ro.lge.capp_valid_batteryid=false
ro.lge.capp_mdm=true
ro.lge.capp_lockscreen=true
ro.lge.capp_app_preinstall=true
ro.lge.fonts=true
ro.lge.capp_bubble_popup=true
ro.com.google.gmsversion=4.0_r2
ro.setupwizard.mode=DISABLED
ro.livewallpaper.map=DISABLED
ro.lge.capp_tdmb=true
drm.service.enabled=true
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt# begin build properties
LG P970 Optimus Black User.
THANKS

sure it will be definatly helpful to devs to make fully functioned ics rom and kernel 3.0 for our device....

Really waiting for dhriu
Sent from my GT-I9003 using xda premium

gabwerkz said:
The kernel is 3.0.8 http://bbs.gfan.com/android-4953013-1-1.html
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Sent from my GT-I9003

yes it has kernel 3.0.8 but we must wait until source code has released. then we shall have fully stable ics and jb roms!

wowowowowowo!!
ICS 100% stable coming very soon! i hope

We have to wait for the source codes !
DONT FORGET TO PRESS THE THANKS BUTTON IF HELPED YOU IN ANY WAY

Mebin Robin said:
We have to wait for the source codes !
DONT FORGET TO PRESS THE THANKS BUTTON IF HELPED YOU IN ANY WAY
Click to expand...
Click to collapse
hopefully coming soon :good:

Chris089 said:
hopefully coming soon :good:
Click to expand...
Click to collapse
don't think so but i hope it too

Let's assume that it is more likely that Samsung would release the source if the i9003 will is viewed as a "paid off" development and you have a closer look at the strategy behind releasing it with ICS then I'd suggest: yes it us likely.
The ICS is just a product "face lift" trying to attract customers with an up-to-date software and old but working hardware (with existing and productive factories).
That's just my stupid view as a marketeer.
Gesendet von meinem GT-I9003 mit Tapatalk 2

clumsynick said:
Let's assume that it is more likely that Samsung would release the source if the i9003 will is viewed as a "paid off" development and you have a closer look at the strategy behind releasing it with ICS then I'd suggest: yes it us likely.
The ICS is just a product "face lift" trying to attract customers with an up-to-date software and old but working hardware (with existing and productive factories).
That's just my stupid view as a marketeer.
Gesendet von meinem GT-I9003 mit Tapatalk 2
Click to expand...
Click to collapse
Samsung won't release any ICS rom nor source code. We are waiting for the LG Optimus Black one which has same specs as i9003.

Fingers crossed..
chriz74 said:
Samsung won't release any ICS rom nor source code. We are waiting for the LG Optimus Black one which has same specs as i9003.
Click to expand...
Click to collapse
I'm just waiting for the Stable ICS for out phone model, its been months by waiting for it.:fingers-crossed:

Samsung called a stop to update our device so yeah optimus black seems to be our hope.. much anticipated!
Sent from my GT-i9003 with CM10 Alpha 1

Now there is a source is out of OB...
Now waiting for Dhiru to do his magical work n bring a stable ROM.for us...
Sent from my GT-I9003 using xda app-developers app

[ROM] I727RUXUMA7 [30-01-2013][Android 4.1.2]

I727RUXUMA7
Base Firmware: I727RUXUMA7(4.1.2)
CSC: I727ROYAMA7
Build Date: 30-01-2013
Changlist: 885181
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JZO54K
ro.build.display.id=JZO54K.I727RUXUMA7
ro.build.version.incremental=I727RUXUMA7
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Wed Jan 30 20:11:13 KST 2013
ro.build.date.utc=1359544273
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-127
ro.build.tags=release-keys
ro.product.model=SGH-I727R
ro.product.brand=samsung
ro.product.name=SGH-I727R
ro.product.device=SGH-I727R
ro.product.board=MSM8660_SURF
ro.chipname=MSM8660_SURF
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product_ship=true
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-I727R
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SGH-I727R-user 4.1.2 JZO54K I727RUXUMA7 release-keys
ro.build.fingerprint=samsung/SGH-I727R/SGH-I727R:4.1.2/JZO54K/I727RUXUMA7:user/release-keys
ro.build.characteristics=default
# Samsung Specific Properties
ro.build.PDA=I727RUXUMA7
ro.build.hidden_ver=I727RUXUMA7
ro.build.changelist=885181
# end build properties
Download:
https://hotfile.com/dl/194996397/6512b87/SGH-I727R_RWC_I727RUXUMA7_I727ROYAMA7_I727RUXUMA7.zip.html

Omg is this the Rogers final official release or another leak?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

What is this?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

mindmajick said:
What is this?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
This is official Rogers jellybean, I just finished doing Kies Update
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yep its finally out
http://samsung-updates.com/7707-galaxy-s-2-lte-from-rogers-canada-gets-jelly-bean-update/

Oh wow you guys have 4.1.2 officially before 3 of the U.S. S3s.
Sent from my SGH-I747 using xda premium

I'm not getting Google Now from this update?!? I was under the impression it came automatically with JB?
Any one else?

Here's a MegaUpload mirror.
That's weird. Have they forgot to update their forums?
http://communityforums.rogers.com/t5/forums/forumtopicpage/board-id/GeneralCareSupport/thread-id/355
stoopendis said:
U need gapps.
Click to expand...
Click to collapse
You get google now by updating/installing google search from play store.
This rom already has google now btw, i don't know why alexvtr doesn't see it.
For anyone needing root, this root method works.
And for everyone who only wants the radio you can get it below
I have tested this myself on my own i727r and it worked perefctly.
USE AT YOUR OWN RISK
Download radio-rogers-UXUMA7-no-csc-no-ril-cwm.zip

4.2.1 >
Sent from my SAMSUNG-SGH-I727 using xda

I assume you can install the rogers 4.1.2 ROM on the AT&T sgh i727? =) Can't wait to see what custom ROM's may come though.

Febby said:
I assume you can install the rogers 4.1.2 ROM on the AT&T sgh i727? =) Can't wait to see what custom ROM's may come though.
Click to expand...
Click to collapse
probably none.. We really only got one out of the leaks 2 if you include jedi but i mean idk if mohan will even change bases because theirs probably no real changes from the leaks.. All of our devs are about cm10 and 10.1 nothing is touchwiz anymore

Guitarboarder28 said:
probably none.. We really only got one out of the leaks 2 if you include jedi but i mean idk if mohan will even change bases because theirs probably no real changes from the leaks.. All of our devs are about cm10 and 10.1 nothing is touchwiz anymore
Click to expand...
Click to collapse
Mohan can't do much more until he can access kernel source for it that's where he will do his thing. Most of the devs choose aosp because they can actually modify it we don't get source for tw stuff so you can mod the kernel and theme it so meh.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

So i finally was able to connect to hotfile. Flashed this, forgot about wiping first and it's nice to see that all my apps are intact
And, once again, how come rogers still say this update isn't out yet?

lingowistico said:
So i finally was able to connect to hotfile. Flashed this, forgot about wiping first and it's nice to see that all my apps are intact
And, once again, how come rogers still say this update isn't out yet?
Click to expand...
Click to collapse
So I'm gonna finish downloading this and I can flash it using twrp? And it works on the skyrocket?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Smash2Bash said:
So I'm gonna finish downloading this and I can flash it using twrp? And it works on the skyrocket?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
For future reference all Rogers/Telcel/AT&T roms work on any i727/i727r. You can't flash this zip with custom recovery, you'll need Odin to flash it from Windows.
1 Unzip the file into it's own folder.
2 Run Odin.
3 In Odin click PDA and select the the tar.md5 file.
4 Put phone in download mode:
4.1 ATT PHONES - Press and keep down both Volume Up and Volume Down keys simultaneously.
ROGERS PHONES - Press and keep down only the Volume Down key.
4.2 While holding above said button(s) press the power button.
5 Now click Start in Odin and leave your computer alone. Go for a walk.
6 Your phone will restart when it's done, after it booted up leave it alone for 5 minutes.
7 Done.
Also look at this picture.

Can you root with su-busybox?
God promised men that he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round

lingowistico said:
For future reference all Rogers/Telcel/AT&T roms work on any i727/i727r. You can't flash this zip with custom recovery, you'll need Odin to flash it from Windows.
1 Unzip the file into it's own folder.
2 Run Odin.
3 In Odin click PDA and select the the tar.md5 file.
4 Put phone in download mode:
ATT PHONES - Press and keep down both Volume Up and Volume Down keys simultaneously.
ROGERS PHONES - Press and keep down only the Volume Down key.
5 Now click Start in Odin and leave your computer alone. Go for a walk.
6 Your phone will restart when it's done, after it booted up leave it alone for 5 minutes.
7 Done.
Also look at this picture.
Click to expand...
Click to collapse
Thank you man I completely understand. I haven't used Odin since installed the ICS leak on day one of getting my phone lol
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

jd1639 said:
Can you root with su-busybox?
Click to expand...
Click to collapse
You silly bugger, i just said that it doesn't work a couple of posts above
But, you could try for yourself. I just flashed old cwm in odin, then updated cwm to latest and my phone got stuck again at the glowing samsung logo. I realized it wasn't because of su-busybox. Removed battery, put it back in and it booted up. So maybe i should've done this with su-busibox too.

Hours of stupid kies
Backed up. Flashed back to stock. let Kies update itself for a long time... couldn't see the phone
Tried most of the above again still no phone...
Odin flashing it now.
Does the flash of SU and CWM root it? I don't want to have to reinstall everything when I have a fresh new TiBu on my SD card...

Here's a MegaUpload mirror.
Smash2Bash said:
Thank you man I completely understand. I haven't used Odin since installed the ICS leak on day one of getting my phone lol
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Oh, lol, no problem :good:
robinsonj said:
Backed up. Flashed back to stock. let Kies update itself for a long time... couldn't see the phone
Tried most of the above again still no phone...
Odin flashing it now.
Does the flash of SU and CWM root it? I don't want to have to reinstall everything when I have a fresh new TiBu on my SD card...
Click to expand...
Click to collapse
You need to be on stock recovery too for Kies to find the phone, sometimes you need the Kies debug drivers. You can try the su-busybox flash, it may work. Read the whole thread for more info on root .
On a sidenote has anyone tested the mods for UCLL3 on this yet?

[ROM] I8160PXXME1 [01.05.2013][Android 4.1.2][Germany]

I8160PXXME1
Base Firmware: I8160PXXME1(4.1.2)
Modem: I8160PXXME1
CSC: I8160PDBTME1
Build Date: 01.05.2013
Changlist: 1106830
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JZO54K
ro.build.display.id=JZO54K.I8160PXXME1
ro.build.version.incremental=I8160PXXME1
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Wed May 1 23:49:01 KST 2013
ro.build.date.utc=1367419741
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-102
ro.build.tags=release-keys
ro.build.changelist=1106830
ro.product.model=GT-I8160P
ro.product.brand=samsung
ro.product.name=GT-I8160P
ro.product.device=GT-I8160P
ro.product.board=montblanc
ro.product.cpu.abi=armeabi-v7a
# Samsung Specific Properties
ro.build.PDA=I8160PXXME1
ro.product.cpu.abi2=armeabi
ro.product_ship=true
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=montblanc
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I8160P
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I8160P-user 4.1.2 JZO54K I8160PXXME1 release-keys
ro.build.fingerprint=samsung/GT-I8160P/GT-I8160P:4.1.2/JZO54K/I8160PXXME1:user/release-keys
ro.build.characteristics=default
# end build properties
Download:
https://hotfile.com/dl/222928094/cd0d710/GT-I8160P_DBT_I8160PXXME1_I8160PDBTME1_I8160PXXME1.zip.html

it's for GT-I8160P look at the download link https://hotfile.com/dl/222928094/cd0d710/GT-I8160P_DBT_I8160PXXME1_I8160PDBTME1_I8160PXXME1.zip.html
EDIT 1:
Another hotfile link: http://hotfile.com/dl/222922682/38a...GT-I8160P-DBT-I8160PXXME1-1367419741.zip.html
EDIT 2:
Another hotfile link: http://www.hotfile.com/dl/222919379/f5c8dfe/I8160PXXME1_I8160PDBTME1_DBT.zip.html

Why create a new thread for every new rom.

ddikodroid said:
it's for GT-I8160P look at the download link https://hotfile.com/dl/222928094/cd0d710/GT-I8160P_DBT_I8160PXXME1_I8160PDBTME1_I8160PXXME1.zip.html
EDIT 1:
Another hotfile link: http://hotfile.com/dl/222922682/38a...GT-I8160P-DBT-I8160PXXME1-1367419741.zip.html
EDIT 2:
Another hotfile link: http://www.hotfile.com/dl/222919379/f5c8dfe/I8160PXXME1_I8160PDBTME1_DBT.zip.html
Click to expand...
Click to collapse
Useless...It has value if u give a mediafire link...
Sent from my GT-I8160 using xda app-developers app

I've installed the new german jelly bean firmware. All went ok, but i have only 550MB of ram available. Went from official gingerbread to JB. Was I supposed to tick repartition in odin to get the maximum ram available (625MB)??

Glpcha said:
I've installed the new german jelly bean firmware. All went ok, but i have only 550MB of ram available. Went from official gingerbread to JB. Was I supposed to tick repartition in odin to get the maximum ram available (625MB)??
Click to expand...
Click to collapse
do you have i8160P model?

Can i install this rom for gt i8160p (with nfc) on my gt i8160 (without nfc) ?? I can have hardbrick???
Inviato dal mio GT-I8160 con Tapatalk 2

b0g said:
do you have i8160P model?
Click to expand...
Click to collapse
Yes, I have the i8160P model.

Glpcha said:
I've installed the new german jelly bean firmware. All went ok, but i have only 550MB of ram available. Went from official gingerbread to JB. Was I supposed to tick repartition in odin to get the maximum ram available (625MB)??
Click to expand...
Click to collapse
Have you put a single file in PDA ? Or 3 different files in Phone, PAD and CSC ?
What about the bootloader ? Have you ticked the box ?

Nessuno1 said:
Have you put a single file in PDA ? Or 3 different files in Phone, PAD and CSC ?
What about the bootloader ? Have you ticked the box ?
Click to expand...
Click to collapse
I have put only a sigle file in the PDA. Only thing ticked was Auto reboot and F. reset time

Glpcha said:
Yes, I have the i8160P model.
Click to expand...
Click to collapse
maybe for the new firmware jelly bean the 550mb is corect, for more optimization

b0g said:
maybe for the new firmware jelly bean the 550mb is corect, for more optimization
Click to expand...
Click to collapse
Maybe it is, we'll see when someone updates it through kies or OTA.

Glpcha said:
I've installed the new german jelly bean firmware. All went ok, but i have only 550MB of ram available. Went from official gingerbread to JB. Was I supposed to tick repartition in odin to get the maximum ram available (625MB)??
Click to expand...
Click to collapse
It should 624MB of RAM if u use Kies or OTA, Coz in the latest Kies Software there's included new feature called " Firmware Managament Update"...
Sent from my GT-I8160 using xda app-developers app

info
if you want you can try to flash the new firmware for i8160P with "GT-I8160_EUR_XX_4G.pit" from first firmware "I8160XXMB2"
please check my attash

Glpcha said:
I have put only a sigle file in the PDA. Only thing ticked was Auto reboot and F. reset time
Click to expand...
Click to collapse
Ok thanks for the answer. because with previous JB versions (for th I8160), doing so could lead to hardbrick the device when coming from official JB.
EDIT : byt the way, do you have an "easy mode" that displays big icons and widgets in the settings ? Or contacts and favorite apps widgets ? Like
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and
as can be seen on this page : http://www.samsung.com/be_fr/articl...la-facilité-d-utilisation-de-votre-smartphone

b0g said:
if you want you can try to flash the new firmware for i8160P with "GT-I8160_EUR_XX_4G.pit" from first firmware "I8160XXMB2"
please check my attash
Click to expand...
Click to collapse
Thanks, but i'll wait for now. Wouldn't want to hardbrick it...

Nessuno1 said:
byt the way, do you have an "easy mode" that displays big icons and widgets in the settings ? Or contacts and favorite apps widgets ?
Click to expand...
Click to collapse
It has to be enabled from within framework. Decompile framework-res and change "easy_mode_enabled" boolean value to "true"
Sent from my GT-I8160 using xda app-developers app

It will be working on 8160? (without P)

michal89chz said:
It will be working on 8160? (without P)
Click to expand...
Click to collapse
i am also thinking of that
anybody tested it ? Or flashing kernel will be fine

info
- it is possible that firmware from i8160p model to work in i8160; because pcb from i8160P (like the picture from attach) is the same with pcb from i8160 (like my model i8160 coa): - pcb from my i8160 has even 2 pins for nfc;

Samsung devices running CM13/12.1 can't pair with Gear S2..I have a fix!

Bought my Gear S2 after reading Samsung's requirements that it could sync to any Android device running 4.4+ and 1.5gb of RAM only to find out I couldn't under CM. I searched and searched for a fix and nothing worked. I went out on a limb and tried something, editing the build.prop and it worked. The only consequence to this is that the IR blaster is now inoperable and once you update to a new nightly you must edit the build.prop once again which would cause you to save and reboot. I'd rather do that than return my S2 Note this guide is for CM12.1 but the process is the same under CM13.
1. Install the Gear Manager from the Play Store. Naturally you'll receive the dreaded message saying your operating system is blah blah blah.
2. Go into settings/Security and enable the install from unknown sources.
3. Navigate to your build.prop using whatever file manager you choose. I use ES. Ensure you're navigating under root rights.
4. Edit any entry that says Samsung and edit to htc all lowercase.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. Save and reboot.
6. Once you reboot open your Gear Manager. You'll be prompted to install a couple of apps but you'll be unable to install from the Play Store because you'll get an error that your device is not compatible.
7. First one should be the gear plugin that can be found here: https://apkpure.com/gear-plugin/com.samsung.android.gearoplugin
8. Install and you'll be prompted to install a second apk and that can be found here: https://apkpure.com/samsung-accessory-service/com.samsung.accessory
9. Your device should now go through the process of installing apps from your Gear Manager.
10. As stated above anytime you update to a new nightly you must redo step number 3,4 and 5. The apps will still be installed so none of the other steps are needed.
11. Enjoy

I'm having the same issue but on a Samsung S4 running 6.0.1. I presume I need to replace htc with something else since my brand is not HTC? Or am I misunderstanding?

mswal2846 said:
I'm having the same issue but on a Samsung S4 running 6.0.1. I presume I need to replace htc with something else since my brand is not HTC? Or am I misunderstanding?
Click to expand...
Click to collapse
That is correct. Otherwise you'll get the message that the operating system is unauthorized.

Cdub1976 said:
That is correct. Otherwise you'll get the message that the operating system is unauthorized.
Click to expand...
Click to collapse
Ok, got it ... I need to replace "Samsung" with "htc" in my /System/build.prop file and reboot. I will give that a try later tonight.

mswal2846 said:
Ok, got it ... I need to replace "Samsung" with "htc" in my /System/build.prop file and reboot. I will give that a try later tonight.
Click to expand...
Click to collapse
Correct. Just remember when you update to a new nightly you'll have to edit the build prop again.

Cdub1976 said:
Correct. Just remember when you update to a new nightly you'll have to edit the build prop again.
Click to expand...
Click to collapse
Is it just the change to "build.prop and reboot" or do I need to go back through reinstalling everything again?

mswal2846 said:
Is it just the change to "build.prop and reboot" or do I need to go back through reinstalling everything again?
Click to expand...
Click to collapse
Please refer to step 10. You won't need to install anything after the initial install.

Cdub1976 said:
Please refer to step 10. You won't need to install anything after the initial install.
Click to expand...
Click to collapse
It works!! Thank you so much!!

mswal2846 said:
It works!! Thank you so much!!
Click to expand...
Click to collapse
Anytime. Glad I could provide something useful for the community.

It works! Thanks for sharing this useful info.

I am trying to pair my Gear 2 Neo with S5 duos running CM13.
I was able to open the Gear Manager (after editing build.prop) , strangely it did not ask for additional files to be installed. So I did install Gear Plugin and Accessory Service form the Play Store - all no problem.
Now I am able to open the Gear Manager and I can get to the point where it can connect over Bluetooth with the Neo - and it will ask to reset the watch (but I believe the reset request is initiated by the Bluetooth pairing and not by the gear manager). After reset - it will not show any available devices.:crying:
I did try this many many times...
Did try deleting and installing all 3 applications. I did try installing only the gear manager - still it did not request additional applications - just it will not show any devices.
This is my current build.prop:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MMB29X
ro.build.display.id=cm_klteduos-userdebug 6.0.1 MMB29X f841775067 test-keys
ro.build.version.incremental=f841775067
ro.build.version.sdk=23
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=6.0.1
ro.build.version.security_patch=2016-04-02
ro.build.version.base_os=
ro.build.date=Mon Apr 18 15:04:47 PDT 2016
ro.build.date.utc=1461017087
ro.build.type=userdebug
ro.build.user=jenkins
ro.build.host=cyanogenmod
ro.build.tags=test-keys
ro.build.flavor=cm_klteduos-userdebug
ro.product.brand=htc
ro.product.name=cm_klteduos
ro.product.board=MSM8974
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=htc
ro.product.locale=en-US
ro.wifi.channels=
ro.board.platform=msm8974
ro.build.characteristics=default
ro.cm.device=klteduos
# end build properties
#
# from device/htc/klteduos/system.prop
#
# Radio
rild.libargs=-d /dev/smd0
rild.libpath=/system/lib/libsec-ril.so
ro.ril.telephony.mqanelements=6
# RIL
persist.radio.multisim.config=dsds
ro.multisim.simslotcount=2
ro.multisim.set_audio_params=true
ro.telephony.ril.config=simactivation
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.error.receiver.system.apps=org.cyanogenmod.bugreport
ro.rommanager.developerid=cyanogenmod
ro.com.google.clientidbase=android-google
keyguard.no_require_sim=true
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.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.build.selinux=1
persist.sys.dun.override=0
media.sf.omx-plugin=libffmpeg_omx.so
media.sf.extractor-plugin=libffmpeg_extractor.so
persist.sys.root_access=0
ro.cm.version=13.0-20160418-SNAPSHOT-ZNH0EAO2NL-klteduos
ro.cm.releasetype=SNAPSHOT
ro.modversion=13.0-20160418-SNAPSHOT-ZNH0EAO2NL-klteduos
ro.cmlegal.url=https://cyngn.com/legal/privacy-policy
ro.cm.display.version=13.0-20160418-SNAPSHOT-ZNH0EAO2NL-klteduos
ro.cm.build.version.plat.sdk=4
ro.cm.build.version.plat.rev=1
ro.config.notification_sound=Argon.ogg
ro.config.alarm_alert=Helium.ogg
ro.config.ringtone=Orion.ogg
ro.carrier=unknown
dalvik.vm.dex2oat-swap=false
af.fast_track_multiplier=1
audio.offload.video=true
persist.audio.fluence.speaker=true
persist.audio.fluence.voicecall=true
persist.audio.fluence.voicerec=false
ro.qc.sdk.audio.fluencetype=fluence
use.voice.path.for.pcm.voip=false
use.dedicated.device.for.voip=true
audio.deep_buffer.media=true
camera2.portability.force_api=1
ro.hdcp2.rx=tz
ro.qualcomm.cabl=1
ro.secwvk=144
ro.sf.lcd_density=480
persist.gps.qc_nlp_in_use=0
ro.gps.agps_provider=1
ro.qc.sdk.izat.premium_enabled=0
ro.qc.sdk.izat.service_mask=0x0
ro.nfc.port=I2C
ro.vendor.extension_library=/vendor/lib/libqti-perfd-client.so
persist.data.netmgrd.qos.enable=true
persist.data.qmi.adb_logmask=0
persist.radio.add_power_save=1
persist.radio.lte_vrat_report=1
ro.telephony.mms_data_profile=5
ro.telephony.ril_class=KlteRIL
debug.sensors=1
net.tethering.noprovisioning=true
wifi.interface=wlan0
dalvik.vm.heapstartsize=16m
dalvik.vm.heapgrowthlimit=192m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
ro.hwui.texture_cache_size=72
ro.hwui.layer_cache_size=48
ro.hwui.r_buffer_cache_size=8
ro.hwui.path_cache_size=32
ro.hwui.gradient_cache_size=1
ro.hwui.drop_shadow_cache_size=6
ro.hwui.texture_cache_flushrate=0.4
ro.hwui.text_small_cache_width=1024
ro.hwui.text_small_cache_height=1024
ro.hwui.text_large_cache_width=2048
ro.hwui.text_large_cache_height=1024
audio.offload.buffer.size.kb=32
audio.offload.gapless.enabled=false
av.offload.enable=true
ro.opengles.version=196608
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
persist.timed.enable=true
debug.sf.hw=1
debug.mdpcomp.logs=0
persist.hwc.mdpcomp.enable=true
ro.telephony.call_ring.multiple=0
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm.variant=krait
dalvik.vm.isa.arm.features=default
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.expect.recovery_id=0xf4b0196b013fc6045196d1609fccb5df63a96106000000000000000000000000

Sorry I don't have experience with the 2neo. Have you tried to reset the watch before you try to connect to your phone?
Sent from my SM-G900T using XDA-Developers mobile app

Cdub1976 said:
Sorry I don't have experience with the 2neo. Have you tried to reset the watch before you try to connect to your phone?
Sent from my SM-G900T using XDA-Developers mobile app
Click to expand...
Click to collapse
I did... Still the same...
I also followed the instructions to Fix "Galaxy Gear Connecting" forever here:
http://www.knowyourmobile.com/mobile-phones/samsung-gear-2/22110/how-connect-samsung-gear-2-any-android-phone
Installed the bunch of additional apps (provided in Connecting-Fix.zip) - all installed fine, except weather provider, still no connection.

This worked nicely for me!
But it also "breaks" the IR blaster.... Any ideas on that front?
Thanks in advance and great little tip!

Cdub1976 said:
Sorry I don't have experience with the 2neo. Have you tried to reset the watch before you try to connect to your phone?
Sent from my SM-G900T using XDA-Developers mobile app
Click to expand...
Click to collapse
I got it working - but by porting Android Wear 5.1.1 to it - following this guide:
http://forum.xda-developers.com/gear-2/development/please-help-kernel-compiling-android-t2992953
It even became more functional, but it is now loosing charge much faster then when it was on tizen OS (it was lasting me 5-6 days of use (only during business hours), I guess now it will last about 2 business days)- still, so far I am quite happy with the trade off!

Drag-On said:
This worked nicely for me!
But it also "breaks" the IR blaster.... Any ideas on that front?
Thanks in advance and great little tip!
Click to expand...
Click to collapse
Sorry. Once you edit the build prop no chance at using your ir blaster. Tradeoffs
Sent from my SM-G900T using XDA-Developers mobile app

Should this also work with the original Gear S ? Only reason i asked because i do not see one for the gear S on note 4

It's not working anymore
Since a couple of days this method is not working anymore for me. Gear Manager is unable to connect to my S2 classic.

hey guys!!! i have samsung s3 with 6.0.1 cyanogenmod and o can't install samsung gear cause of the unauthorized firmware!!! i did the steps above ... i change everything says samsung to htc and i9300 to ktle but i can't save the changes...!!! so i can't go on with the other steps...!!! what else can i do???

BULLIT GR said:
hey guys!!! i have samsung s3 with 6.0.1 cyanogenmod and o can't install samsung gear cause of the unauthorized firmware!!! i did the steps above ... i change everything says samsung to htc and i9300 to ktle but i can't save the changes...!!! so i can't go on with the other steps...!!! what else can i do???
Click to expand...
Click to collapse
Did you grant your file manager root rights?
Sent from my XT1575 using Tapatalk