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
Related
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
folks i really dont know the difference between all these firmware as they all sound the same so try yourself!
Firmware: I9003JPKPE_I9003OJPKPC_XSG (XSG=UAE)
http://hotfile.com/dl/138739744/cb4c074/GT-I9003_XSG_I9003JPKPE_I9003OJPKPC_I9003JXKP3.rar.html (credits Prezket)
pass - sampro.pl
mirror
http://www.hotfile.com/dl/138734905/a4f5c26/I9003JPKPE_I9003OJPKPC_XSG.zip.html
PASS- samfirmware.com
Firmware:I9003JPKPE_I9003OJPKPC_MID.zip (MID=UAE)
http://www.hotfile.com/dl/138921439/3990577/I9003JPKPE_I9003OJPKPC_MID.zip.html
pass-samfirmware.com
Firmware: I9003JPKPE_I9003OJPKPC_PAK (PAK=PAKISTAN)
http://www.hotfile.com/dl/138734881/9692cb5/I9003JPKPE_I9003OJPKPC_PAK.zip.html (DEAD )
pass- samfirmware.com
I9003JPKPE
Android 2.3.6
Phone: I9003JXKP3
CSC: I9003OJPKPC
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.JPKPE
ro.build.version.incremental=JPKPE
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.6
ro.build.date=Wed Dec 14 20:44:29 KST 2011
ro.build.date.utc=1323863069
ro.build.type=user
ro.build.user=root
ro.build.host=DELL132
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=ar
ro.product.locale.region=AE
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 JPKPE release-keys
ro.build.fingerprint=samsung/GT-I9003/GT-I9003:2.3.6/GINGERBREAD/JPKPE:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I9003JPKPE
ro.build.hidden_ver=I9003JPKPE
ro.build.changelist=811961
ro.flash.resolution=720
# end build properties
Download:
http://hotfile.com/dl/138739744/cb4c074/GT-I9003_XSG_I9003JPKPE_I9003OJPKPC_I9003JXKP3.rar.html
Pass: sampro.pl
soory its 2.3.6
@Przekret
is there any difference between the two links i posted?
Is it persian stock rom ?
What is it update from this rom?
I use jxkp3 2.3.4 . This rom is better?
Dear Akashsgpgi,
Compressed file for I9003JPKPE_I9003OJPKPC_PAK (PAK=PAKISTAN) is corrupted. it doesn't ask any password. i tried many times to download and always download complete 204mb but still it is corrupt. can u please check this. thanks
please, is the "I9003JPKPE_I9003OJPKPC_XSG (XSG=UAE)" ROM is an arabic support one?
please, I need the answer quickly
iwih said:
please, is the "I9003JPKPE_I9003OJPKPC_XSG (XSG=UAE)" ROM is an arabic support one?
please, I need the answer quickly
Click to expand...
Click to collapse
Yeah this one supports arabic. UAE is an arabic country
alidogar said:
Yeah this one supports arabic. UAE is an arabic country
Click to expand...
Click to collapse
UAE is an arabic country?! Really??!!!!
hahaha... I'm just joking man, I knew it's an arabic country, but I wanted to be sure whether the rom supports arabic or not. Thank you man for your post, I do appreciated it
{
"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"
}
iwih said:
UAE is an arabic country?! Really??!!!!
hahaha... I'm just joking man, I knew it's an arabic country, but I wanted to be sure whether the rom supports arabic or not. Thank you man for your post, I do appreciated it
Click to expand...
Click to collapse
ya its arabic
Sent from my GT-I9003 using Tapatalk
iwih said:
please, is the "I9003JPKPE_I9003OJPKPC_XSG (XSG=UAE)" ROM is an arabic support one?
please, I need the answer quickly
Click to expand...
Click to collapse
i downloaded it and it asks for the password but fails in the extraction
sorry i will try to find another link
Przekret said:
I9003JPKPE
Android 2.3.6
Phone: I9003JXKP3
CSC: I9003OJPKPC
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.JPKPE
ro.build.version.incremental=JPKPE
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.6
ro.build.date=Wed Dec 14 20:44:29 KST 2011
ro.build.date.utc=1323863069
ro.build.type=user
ro.build.user=root
ro.build.host=DELL132
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=ar
ro.product.locale.region=AE
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 JPKPE release-keys
ro.build.fingerprint=samsung/GT-I9003/GT-I9003:2.3.6/GINGERBREAD/JPKPE:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I9003JPKPE
ro.build.hidden_ver=I9003JPKPE
ro.build.changelist=811961
ro.flash.resolution=720
# end build properties
Download:
http://hotfile.com/dl/138739744/cb4c074/GT-I9003_XSG_I9003JPKPE_I9003OJPKPC_I9003JXKP3.rar.html
Pass: sampro.pl
Click to expand...
Click to collapse
Alternate With Resume:
http://www.multiupload.com/E5NXOTZNZX
http://www.uploadhere.com/GYL982NEX0
http://www.uploadbaz.com/t5zokw7v1pub
http://www.sharebees.com/qr2x9smvwwh1.html
zied_dab said:
ya its arabic
Click to expand...
Click to collapse
Thank you for your efforts, I do appreciate it.. The main thanks go to "akashsgpgi", thank you so much .
Working smoothly so far, just wipe cache and factory reset after flashing, thanks to uploaders...
one more JPKPE added in op
akashsgpgi said:
one more JPKPE added in op
Click to expand...
Click to collapse
There is a problem in the Wi-Fi (Error ) and hi dont Work....? help
hshu80 said:
There is a problem in the Wi-Fi (Error ) and hi dont Work....? help
Click to expand...
Click to collapse
Restart ur phone...it helps,but i have no idea why this happens
Sent from my GT-I9003 using xda premium
Guys im having a problem with this rom (XSG)
when I leave the phone for a while, i find it turned off and when I start it i find it formatted, this happened three times, any one have the same issue?
AbuS3ood said:
Guys im having a problem with this rom (XSG)
when I leave the phone for a while, i find it turned off and when I start it i find it formatted, this happened three times, any one have the same issue?
Click to expand...
Click to collapse
I works smoothly . What is the previous rom you had on your device before flashing it?
Try to flash I9003JPKP5(2.3.4) rom first and then flash the current I9003JPKPE(2.3.6) rom.
iwih said:
I works smoothly . What is the previous rom you had on your device before flashing it?
Try to flash I9003JPKP5(2.3.4) rom first and then flash the current I9003JPKPE(2.3.6) rom.
Click to expand...
Click to collapse
I was on JPKPA 2.3.5 it was restarting randomly, but this one was doing hard-reset if the device left for an hour, after long struggle, now Im on XXKPQ with arabic patch to see where is the error,if the device kept resetting then I think its bricked!
AbuS3ood said:
I was on JPKPA 2.3.5 it was restarting randomly, but this one was doing hard-reset if the device left for an hour, after long struggle, now Im on XXKPQ with arabic patch to see where is the error,if the device kept resetting then I think its bricked!
Click to expand...
Click to collapse
Ummmm... I can't judge for sure what your problem is , as I'm not an expert . But, in case the problem keeps happening on XXKPQ too, then you may try to install XXKPE with latona.pit to re-partition the phone memory (!!! BE CAREFUL TO NOT CHECK "RE-PARTION" IN ODIN MANUALLY, ODIN WILL CHECK IT AUTOMATICALLY !!!) ==> then re-install XXKPQ. You may visit Misledz's thread for detailed guide to install XXKPQ (the first part of it) and kkrraazzyy's thread for the required packages.
You may already know all these information (and even more than me ), but, I'm just trying to help .
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;
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
Hello, good news for the Z users!!
At this lik you can download the Android N ROM of your device: https://pan.baidu.com/s/1geEnxmF
{
"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"
}
Here an part of the build.prop
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=NCC25.73
ro.build.version.incremental=282
ro.build.version.sdk=24
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=7.0
ro.build.version.security_patch=2016-10-01
ro.build.date=Fri Oct 7 12:59:29 CDT 2016
ro.build.date.utc=1475863169
ro.build.type=userdebug
ro.build.user=hudsoncm
ro.build.host=ilclbld119
ro.build.tags=intcfg,test-keys
ro.product.model=XT1650-05
ro.product.brand=motorola
ro.product.name=griffin_retcn
ro.product.device=griffin
ro.product.board=QC_Reference_Phone
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=motorola
ro.product.locale=zh-CN
ro.wifi.channels=
ro.board.platform=msm8996
# ro.build.product is obsolete; use ro.product.device
ro.build.product=griffin
# Do not try to parse description, fingerprint, or thumbprint
ro.build.thumbprint=7.0/NCC25.73/282:userdebug/intcfg,test-keys
ro.build.characteristics=default
# end build properties
#
# from device/qcom/msm8996/system.prop
#
#
# system.prop for msm8996
#
Why is everyone saying that the xt1650-05 is the moto z force? its the dual sim moto z (Chinese version)
The moto z force code name is xt1650-02
Moto z Driod xt1650-01
Hmm... This is signed with test-key... Wonder if we can use that to our advantage, considering it's not the release-key.
karendar said:
Hmm... This is signed with test-key... Wonder if we can use that to our advantage, considering it's not the release-key.
Click to expand...
Click to collapse
Inviato dal mio Z2plus utilizzando Tapatalk
vzdragon said:
Why is everyone saying that the xt1650-05 is the moto z force? its the dual sim moto z (Chinese version)
The moto z force code name is xt1650-02
Moto z Driod xt1650-01
Click to expand...
Click to collapse
Right, haven't the same hardware?
Inviato dal mio Z2plus utilizzando Tapatalk
Did anyone manage to download it? The link doesn't seem to work for me anymore.
karendar said:
Did anyone manage to download it? The link doesn't seem to work for me anymore.
Click to expand...
Click to collapse
Working have an Baidu account?
Naphtha said:
Working have an Baidu account?
Click to expand...
Click to collapse
It's working now, had a 404 before. But I can't for the life of me download this off Baidu. Horrible that to download you have to use an app that's only in chinese.
***Edit*** Using Baidou is like pulling teeth... I've managed to get the files.
karendar said:
It's working now, had a 404 before. But I can't for the life of me download this off Baidu. Horrible that to download you have to use an app that's only in chinese.
***Edit*** Using Baidou is like pulling teeth... I've managed to get the files.
Click to expand...
Click to collapse
You flash them yet?
bignazpwns said:
You flash them yet?
Click to expand...
Click to collapse
Don't think I'm gonna flash it, I own a Z Force droid... Don't really want to mess up my phone.
I'm curious though considering this has a lot of references of having private keys and test-keys, so might help us unlock the phone? I don't know.
karendar said:
Don't think I'm gonna flash it, I own a Z Force droid... Don't really want to mess up my phone.
I'm curious though considering this has a lot of references of having private keys and test-keys, so might help us unlock the phone? I don't know.
Click to expand...
Click to collapse
Im thinking open doors. Something feels shady about this rom.
Impossible to download from the side. Hopefully someone upload that ..
It can't be done
Enviado desde mi XT1650 mediante Tapatalk
Khanov said:
It can't be done
Enviado desde mi XT1650 mediante Tapatalk
Click to expand...
Click to collapse
Please upload the some where else. Thanks
Khanov said:
It can't be done
Enviado desde mi XT1650 mediante Tapatalk
Click to expand...
Click to collapse
Have dual sim version? If not don't flash all. Try only system-boot, modem partition can erase your IMEI.
Inviato dal mio Z2plus utilizzando Tapatalk
I'm curious if flashing the bootloader can help us out in unlocking the phone... Only issue is that if the bootloader fails, you effectively kill your phone.
janjan said:
Please upload the some where else. Thanks
Click to expand...
Click to collapse
Seconded. This is a forum for the Moto Z Force, currently a Verizon exclusive. This ROM is not for this phone. This should be removed before someone breaks their phone thinking this is relevant to the Moto Z Force.
They
rmonjay said:
Seconded. This is a forum for the Moto Z Force, currently a Verizon exclusive. This ROM is not for this phone. This should be removed before someone breaks their phone thinking this is relevant to the Moto Z Force.
Click to expand...
Click to collapse
I don't believe this is what the person meant. They probably wanted the file uploaded elsewhere in order to download it, because source is from Baidu.
The XT1650-05 is close enough to the XT1650-02, so there's a chance this could be used positively with the Z-Force Droid with a little tinkering. I think the OP needs to be modified with BIG RED FLAGS to mention that you brick your phone at your own risk though.
I've flashed this ROM on my 1650-03 dual sim and works flawlessly, just had to erase the gpt flash lines and modem ones and is ready (but No Google apps).
Enviado desde mi XT1650 mediante Tapatalk
Khanov said:
I've flashed this ROM on my 1650-03 dual sim and works flawlessly, just had to erase the gpt flash lines and modem ones and is ready (but No Google apps).
Enviado desde mi XT1650 mediante Tapatalk
Click to expand...
Click to collapse
So does this mean the bootloader was flashed as well? And is it truly a Nougat ROM?
**edit** Is your phone bootloader unlocked or is it locked?