I8160XXLK5 (CSC: I8160BTULK5) PRE-ROOTED
United Kingdom, 2012 November, Android 2.3.6
The warranty will be kept (i.e binary counter remains untouched).
Download: http://d-h.st/Bg4
To install a custom kernel without avoiding your warranty just use a dd command:
Code:
su
dd if=/sdcard/kernel.bin of=/dev/block/mmcblk0p15
reboot
More info
build.prop:
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.XXLK5
ro.build.version.incremental=XXLK5
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.6
ro.build.date=Thu Nov 15 17:09:29 KST 2012
ro.build.date.utc=1352966969
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-49
ro.build.tags=release-keys
ro.product.model=GT-I8160
ro.product.name=GT-I8160
ro.product.device=GT-I8160
ro.product.brand=samsung
ro.product.board=codina
ro.product.cpu.abi=armeabi-v7a
# Samsung Specific Properties
ro.build.PDA=I8160XXLK5
ro.build.hidden_ver=I8160XXLK5
ro.build.changelist=1211379
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=ux500
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I8160
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I8160-user 2.3.6 GINGERBREAD XXLK5 release-keys
ro.build.fingerprint=samsung/GT-I8160/GT-I8160:2.3.6/GINGERBREAD/XXLK5:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I8160XXLK5
ro.build.hidden_ver=I8160XXLK5
ro.build.changelist=1211379
ro.tether.denied=false
ro.flash.resolution=1080
# end build properties
Click to expand...
Click to collapse
Available system languages:
Samsung keyboard languages:
Swype languages:
what about performances than I8160XXLI2?
thanks
mkel91,
Nothing miraculous in this part, it will not bring 2 extra cores or something like
More or less the same as in previous firmwares.
Superuser works well or you must install superSU?
I've just installed it, everything is working well..
antsm said:
I8160XXLK5 (CSC: I8160BTULK5) PRE-ROOTED
[
To install a custom kernel without avoiding your warranty just use a dd command:
Code:
su
dd if=/sdcard/kernel.bin of=/dev/block/mmcblk0p15
reboot
Click to expand...
Click to collapse
wanted to know;
where do i perform these commands? ADB on Windows? or in Terminal Emulator via phone?
a little noobie steps would be great
yethz said:
where do i perform these commands? ADB on Windows? or in Terminal Emulator via phone?
Click to expand...
Click to collapse
Both methods are acceptable, choose on your own.
yethz said:
a little noobie steps would be great
Click to expand...
Click to collapse
Simply put kernel.bin to /sdcard and perform the commands, nothing more
antsm said:
Both methods are acceptable, choose on your own.
Simply put kernel.bin to /sdcard and perform the commands, nothing more
Click to expand...
Click to collapse
where is this kernel.bin from? I download your CWM Kernel from your other threads but it is .tar.md5 format...
yethz said:
where is this kernel.bin from? I download your CWM Kernel from your other threads but it is .tar.md5 format...
Click to expand...
Click to collapse
You have to remove an *.md5 extension and extract kernel from the *.tar file. Or just use Odin (it's a simplier way) if you don't want to care about the warranty
antsm said:
You have to remove an *.md5 extension and extract kernel from the *.tar file. Or just use Odin (it's a simplier way) if you don't want to care about the warranty
Click to expand...
Click to collapse
Oww.. Thank you. that clear things out more
Yeah Odin is more easier and these steps for not loosing warranty is more helpful..
Related
Thanks to Designgears, there is a new leak for I777 ROM:
Odin One-Click downloader: http://rootzwiki.com/topic/11366-firmware-i777uckk6-galaxy-s-ii-att/
CWM Flashable i-777 UCKK6 modem extracted from this leak: http://www.multiupload.com/KA01Q9AHX2
System partition dump with Superuser embedded: http://www.victorlara.net/system.img.zip (thanks to vlara)
Code:
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.UCKK6
ro.build.version.incremental=UCKK6
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.6
ro.build.date=Tue Nov 29 19:49:45 KST 2011
ro.build.date.utc=1322563785
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-74
ro.build.tags=release-keys
ro.product.model=SAMSUNG-SGH-I777
ro.product.brand=samsung
ro.product.name=SGH-I777
ro.product.device=SGH-I777
ro.product.board=SGH-I777
ro.product.cpu.abi=armeabi-v7a
# Samsung Specific Properties
ro.build.PDA=I777UCKK6
ro.build.hidden_ver=I777UCKK6
ro.build.changelist=770444
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=s5pc210
# ro.build.product is obsolete; use ro.product.device
ro.build.product=SGH-I777
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SGH-I777-user 2.3.6 GINGERBREAD UCKK6 release-keys
ro.build.fingerprint=samsung/SGH-I777/SGH-I777:2.3.6/GINGERBREAD/UCKK6:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I777UCKK6
ro.build.hidden_ver=I777UCKK6
ro.build.changelist=770444
ro.tether.denied=false
ro.flash.resolution=1080
# end build properties
#
# system.prop for asop5000
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
dalvik.vm.heapsize=64m
# Samsung USB default mode
persist.service.usb.setting=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
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.locationfeatures=1
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=2.3_r8
media.stagefright.enable-player=false
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
media.stagefright.enable-rtsp=false
dev.sfbootcomplete=0
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.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.locationfeatures=1
keyguard.no_require_sim=true
ro.config.ringtone=ATT_tone.ogg
ro.config.notification_sound=S_Sherbet.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.monkey=0
ro.opengles.version=131072
ro.error.receiver.default=com.samsung.receiver.error
ro.secdevenc=true
ro.wtldatapassword=true
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Anyone try it?
Sent from my GT-I9100 using xda premium
Ill give it a shot.
Noticed its an exe. How would you flash that?
I presume this will put in the new bootloader... This file is a one-click-odin archive that I'm not aware how to dissect onto separate pieces to get rid of bootloader, add root, etc.
NJGSII said:
Ill give it a shot.
Noticed its an exe. How would you flash that?
Click to expand...
Click to collapse
it's self-flashable, odin-like wrapper. Be warned that it may overwrite the bootloader to the newer version that is known to be jig-immune. However there was a post on how to revert it back.
558 megabytes!
So you put the phone into download and use odin to load it.
Correct?
^^ Yessir.
You can use mobileodin app to install it also. MobileOdin WILL NOT flash the bootloaders in case it has them.
Sent From My KickAss ATT SGS2 SPORTING CM7
Anyone try it out yet?
RockRatt said:
You can use mobileodin app to install it also. MobileOdin WILL NOT flash the bootloaders in case it has them.
Sent From My KickAss ATT SGS2 SPORTING CM7
Click to expand...
Click to collapse
So to use mobile Odin, I first dl this to computer, then put in root of SD? Run Odin app and let it do it's thing?
Sent from my SAMSUNG-SGH-I777 using XDA App
What's new in this update?
Sent from my SAMSUNG-SGH-I777 using XDA App
Qortez1 said:
What's new in this update?
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
+1
Anyone who has flashed let us know if the sporadic wifi issue has been fixed from KK5.
Cdub5 said:
So to use mobile Odin, I first dl this to computer, then put in root of SD? Run Odin app and let it do it's thing?
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Yes that will work. I just download it to my phone, open mobile Odin, choose the downloaded rom, flash away.
I have not had a chance to download it yet as I didn't go home from work yesterday and for the first time I am being throttled. So once it downloads on this slow ass Starbucks wireless I will let you know how it goes/feels. I am ONLY doing it so I can pull out the modem so I probably wont stay long.
Sent From My KickAss ATT SGS2 SPORTING CM7
I would like to know if this fixes the wifi not syncing problem...
Beware, this is probably infested with that thing called Carrier IQ...
Longcat14 said:
Beware, this is probably infested with that thing called Carrier IQ...
Click to expand...
Click to collapse
So that's the only thing that was updated. HMMMMM
*puts on tin foil hat*
Seriously though the 2.3.6 leak that I'm currently running doesn't have it.
NJGSII said:
So that's the only thing that was updated. HMMMMM
*puts on tin foil hat*
Seriously though the 2.3.6 leak that I'm currently running doesn't have it.
Click to expand...
Click to collapse
Wait, this leak doesn't have it?
Could've been stripped out... good thing though.
Longcat14 said:
Wait, this leak doesn't have it?
Could've been stripped out... good thing though.
Click to expand...
Click to collapse
No, I'm talk about the 2.3.6 leak that's here.
http://forum.xda-developers.com/showthread.php?t=1353513
Not sure about the one in this thread as I haven't got around to putting it on the phone yet.
Anyone that has actually installed would they be willing to pull the UCKK6 modem.bin from it?
In adb or terminal emulator, must be rooted:
Code:
dd if=/dev/block/mmcblk0p8 of=/sdcard/modem.bin bs=4096
hi
I uninstall some Sony Apps via Titanium Backup and i think i deleted some important Apps accidentialy.
When i'm trying to reset my device i get an error.
When i'm trying to root my device the screen with the "restore my data" doesn't come any more, so an rooting is not possible.
When i'm trying to install a zip via recovery i get a Error because my SKU seems not to be the same like in the zip.
What can i do?
Thanks!
hmonadjem said:
hi
I uninstall some Sony Apps via Titanium Backup and i think i deleted some important Apps accidentialy.
When i'm trying to reset my device i get an error.
When i'm trying to root my device the screen with the "restore my data" doesn't come any more, so an rooting is not possible.
When i'm trying to install a zip via recovery i get a Error because my SKU seems not to be the same like in the zip.
What can i do?
Thanks!
Click to expand...
Click to collapse
have you applied "rescue-backdoor" before any system modification?
what region is your device?
Hi,
i used your AIO Tool.
I didn't apply anything like rescue-backdoor manually ...
The Device is German (only WiFi) but i changed it to US and changed it back to German ...
This is a part of my build.prop on the device right now:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=TISU0R0110
ro.build.display.id=TISU0R0110
ro.build.version.incremental=120803055
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Aug 3 20:53:29 JST 2012
ro.build.date.utc=1343994809
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build9
ro.build.tags=release-keys
ro.product.model=Sony Tablet S
ro.product.brand=Sony
ro.product.name=SYS_017
ro.product.device=nbx03
ro.product.board=nbx03
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Sony
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=nbx03
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SYS_017-user 4.0.3 TISU0R0110 120803055 release-keys
ro.build.fingerprint=Sony/SYS_017/nbx03:4.0.3/TISU0R0110/120803055:user/release-keys
ro.build.characteristics=tablet
I don't know if this can help .... i hope so.
Thanks!
hmonadjem said:
Hi,
i used your AIO Tool.
I didn't apply anything like rescue-backdoor manually ...
The Device is German (only WiFi) but i changed it to US and changed it back to German ...
This is a part of my build.prop on the device right now:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=TISU0R0110
ro.build.display.id=TISU0R0110
ro.build.version.incremental=120803055
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Aug 3 20:53:29 JST 2012
ro.build.date.utc=1343994809
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build9
ro.build.tags=release-keys
ro.product.model=Sony Tablet S
ro.product.brand=Sony
ro.product.name=SYS_017
ro.product.device=nbx03
ro.product.board=nbx03
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Sony
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=nbx03
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SYS_017-user 4.0.3 TISU0R0110 120803055 release-keys
ro.build.fingerprint=Sony/SYS_017/nbx03:4.0.3/TISU0R0110/120803055:user/release-keys
ro.build.characteristics=tablet
I don't know if this can help .... i hope so.
Thanks!
Click to expand...
Click to collapse
try this fw via recovery, if it will fail, then there is no way to fix it now.
you will have to wait for R5 to be released - maybe in middle of december
br
condi
Thanks,
i tried it, but it failed.
Is it possible to install the deleted APKs manually?
Thanks!
hmonadjem said:
Thanks,
i tried it, but it failed.
Is it possible to install the deleted APKs manually?
Thanks!
Click to expand...
Click to collapse
if you would have adb shell access - then yes.
Hi,
i have adb shell access very good!
How can i get the apk files? I would download the android 4.0.3 SDK and extract all APKs ... than i would have the most important apps. Is this ok? Or do i have to get the original Sony 4.0.3 Stock APKs?
Thanks!
hmonadjem said:
Hi,
i have adb shell access very good!
How can i get the apk files? I would download the android 4.0.3 SDK and extract all APKs ... than i would have the most important apps. Is this ok? Or do i have to get the original Sony 4.0.3 Stock APKs?
Thanks!
Click to expand...
Click to collapse
gooood DO NOT wipe device! you will loose adb.
ok, so run AiO go to tweaks, use "rescue-backdoor" function.
then use update firmware which I gave you before.
Hi,
but i have no root any more ... because i wiped it yesterday.
hmonadjem said:
Hi,
but i have no root any more ... because i wiped it yesterday.
Click to expand...
Click to collapse
wipe doesnt remove root. so once again - you've got no adb shell access?
Hi,
i had root!
I wiped my device and i got an error from the device itself that this wipe was not completly successfull.
I habe adb access and when i make the command "adb shell" i get access to the shell. But i have no "su" command or something like that. and no superuser app is installed on my device.
hmonadjem said:
Hi,
i had root!
I wiped my device and i got an error from the device itself that this wipe was not completly successfull.
I habe adb access and when i make the command "adb shell" i get access to the shell. But i have no "su" command or something like that. and no superuser app is installed on my device.
Click to expand...
Click to collapse
most probably you've been switched to 2nd system partition.
you could try to make few wipes, it could get back to the 1st,
but after that you will loose adb shell access for sure..
the best way would be wait few days, when new update will be rolled out. info here
br
condi
Hi,
i see there is R5A now out. But the Problem is, when i clock on "Update System" in the Device Settings, my Device Crashes.
I think you are right, it switched to 2nd partition because there is no recovery.log or /tmp. i wiped the device about 10 times.
I have adb shell access but don't know wthat to do now ...
hmonadjem said:
Hi,
i see there is R5A now out. But the Problem is, when i clock on "Update System" in the Device Settings, my Device Crashes.
I think you are right, it switched to 2nd partition because there is no recovery.log or /tmp. i wiped the device about 10 times.
I have adb shell access but don't know wthat to do now ...
Click to expand...
Click to collapse
From the looks of it, it was java.lang.NullPointerException java error due to the system updater is not there anymore.
Sent from my Sony Tablet S using xda premium
Hi,
i don't know, but what can i do now?
Thanks!
hmonadjem said:
Hi,
i don't know, but what can i do now?
Thanks!
Click to expand...
Click to collapse
ok, now update with this firmware, and post results
Worked! Thank you!
my sk17 (bootloader unlocked using flashtool) worked perfectly fine. I could flash kernels and ftf files fine on windows 7. Now my computer is running on windows 8 consumer preview (32 bit) and I've got a BUNCH of problems.
1. PC Companion recognizes my phone as Xperia Arc (LT15). The build prop file shows my phone as SK17i.
Merging of the /util/data/semc_kernel_time_stamp.prop file ##### ro.build.date=Tue Apr 24 11:57:09 2012 ro.build.date.utc=1335261429 ro.build.user=BuildUser ro.build.host=BuildHost
### ## Final patch of properties ##### ro.build.product=SK17i ro.build.description=SK17i-userdebug 4.0.4 4.1.B.0.431 UL5_3w test-keys
ro.product.brand=SEMC ro.product.name=SK17i_1247-1046 ro.product.device=SK17i ro.build.tags=release-keys ro.build.fingerprint=SEMC/SK17i_1247-1046/SK17i:4.0.4/4.1.B.0.431/UL5_3w:userdebug/release-keys
### ############## Updating of the SW Version ################# ro.semc.version.fs_revision=4.1.B.0.43 1 ro.build.id=4.1.B.0.431 ro.build.display.id=4.1.B.0.431
### ## Values from product package metadata ##### ro.semc.product.model=SK17i ro.semc.ms_type_id=AAD-3880097-BV ro.semc.version.fs=WORLD-1-8 ro.semc.product.name=Xperia Mini Pro ro.semc.product.device=SK17 ro.product.model=SK17i
# begin build properties # autogenerated by buildinfo.sh ro.build.version.incremental=UL5_3w ro.build.version.sdk=15 ro.build.version.codename=REL ro.build.version.release=4.0.4 ro.build.type=userdebug ro.product.board= ro.product.cpu.abi=armeabi-v7a ro.product.cpu.abi2=armeabi ro.product.manufacturer=Sony Ericsson ro.product.locale.language=en ro.product.locale.region=GB ro.wifi.channels= ro.board.platform=msm7x30 # ro.build.product is obsolete; use ro.product.device # Do not try to parse ro.build.description or .fingerprint ro.build.characteristics=default # end build properties # # system.prop for mango
2. When I try to run flashtool, it says that drivers for my phone are not installed. When I try to install flashtool drivers, the installation fails at the device driver installation wizard.
3. When I try to manually install the drivers from device manager (after using advanced startup to disable driver signing), I get an error message about Windows not finding the file specified for Android ADB Interface.
I'm using kamarush's rom and his kernel. And I can access my sd card on my pc just fine. But I can't flash any kernel (because the drivers are not installed according to flashtool) and I can't manually install the drivers because of the adb interface. I've searched for DAYS and nothing has worked so far. Any help would be appreciated.
Maybe flashtool n drivers not compatible for win 8.
Sent from Hubble Telescope
What happens when you connect your phone in fastboot mode and connect it to the pc? Does it ask for drivers?
Make sure you are using flashtool for 32bit and not 64
Rudjgaard said:
What happens when you connect your phone in fastboot mode and connect it to the pc? Does it ask for drivers?
Make sure you are using flashtool for 32bit and not 64
Click to expand...
Click to collapse
The led light is blue but it doesn't ask for drivers. And I'm sure I'm using the right flashtool version.
i too had a hard time to use fastboot in windows 8... When you install the drivers from the drivers folder of the flashtool, then it will not install the fastboot drivers, soo when we connect our phone in fatboot mode, the pc cannot detect our phone... there is a guide somewhere in the xda which says how to install fastboot drivers in windows 8.. hope you can do a gentle search..
See link
Androxyde wrote: disable driver signature check from windows 8 and you will be able to install fastboot drivers.
I have no idea why but disabling driver signature doesn't help at all. It doesn't install the drivers. I guess I won't be flashin any of those jellybean roms anytime soon.
Download vmware if you don't already have it, download any os img and use that, this could be a workaround if nothing else works..
I have a Samsung Galaxy S6, model number SM-920F, provider T-mobile Netherlands,.
My phone is stuck in a bootloop but TWRP is still accessable, and I want to know the build number so I can download the right firmware and use Odin to put back to stock firmware.
Bdazzled said:
I have a Samsung Galaxy S6, model number SM-920F, provider T-mobile Netherlands,.
My phone is stuck in a bootloop but TWRP is still accessable, and I want to know the build number so I can download the right firmware and use Odin to put back to stock firmware.
Click to expand...
Click to collapse
First of all, I assume that you're using TWRP 3.0 or above
Boot into TWRP, go to Mount, check System, go back to TWRP's main menu, go to Advanced > Terminal and type this line in it:
Code:
cat /system/build.prop
And press Enter when you typed that line in Terminal
(Scroll around, and you'll see some lines
starting with G920F (Copy one of these, because that's your build number)
Sent from my Pixel XL using Tapatalk
DodoGTA said:
First of all, I assume that you're using TWRP 3.0 or above
Boot into TWRP, go to Mount, check System, go back to TWRP's main menu, go to Advanced > Terminal and type this line in it:
Code:
cat /system/build.prop
And press Enter when you typed that line in Terminal
(Scroll around, and you'll see some lines
starting with G920F (Copy one of these, because that's your build number)
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Thank you, I found it.
Bdazzled said:
Thank you, I found it.
Click to expand...
Click to collapse
Glad that it worked ?
Sent from my Pixel XL using Tapatalk
Same problem but with an Honor 9 (STL-AL09):crying:
---------- Post added at 06:02 PM ---------- Previous post was at 05:41 PM ----------
DodoGTA said:
First of all, I assume that you're using TWRP 3.0 or above
Boot into TWRP, go to Mount, check System, go back to TWRP's main menu, go to Advanced > Terminal and type this line in it:
Code:
cat /system/build.prop
And press Enter when you typed that line in Terminal
(Scroll around, and you'll see some lines
starting with G920F (Copy one of these, because that's your build number)
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I did it and it worked:good: but I can't find the build number. Can you help me ?
Please.
jacquesallet said:
Quote removed to prevent spam
Click to expand...
Click to collapse
That method only works on Samsung phones on stock ROMs or on non-stock ROMs with stock build fingerprint (aka ro.build.fingerprint property in build.prop)
So how can I find my build number? Please.
PS: when I do the manipulation, I can see:
"MacBook-Pro-de-Jacques:~ jacquesallet$ adb shell cat /system/build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=NRD90M
ro.build.version.incremental=eng.jslave.20170604.040710
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=2017-05-05
ro.build.version.base_os=
ro.build.date=Sun Jun 4 04:07:10 CST 2017
ro.build.date.utc=1496520430
ro.build.type=user
ro.build.user=jslave
ro.build.host=LFG1000749994
ro.build.tags=test-keys
ro.build.flavor=generic_a15-user
ro.product.model=generic_a15
ro.product.brand=Huawei
ro.product.name=generic_a15
ro.product.device=generic_a15
ro.product.board=
# 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=unknown
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=generic_a15
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=generic_a15-user 7.0 NRD90M eng.jslave.20170604.040710 test-keys
ro.build.fingerprint=Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave06040407:user/test-keys
ro.build.characteristics=default
# end build properties
# begin huawei emui properties
# autogenerated by build_emui_info.sh
ro.build.hw_emui_api_level=13
# end huawei emui properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.carrier=unknown
ro.setupwizard.require_network=any
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=7.0_r5
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm64.variant=generic
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.variant=cortex-a15
dalvik.vm.isa.arm.features=default
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.build.display.id=System 5.1.0.78(055I)
ro.comp.sys_support_vndk=VA7.0-E5.0-B00005
ro.comp.sys_need_sndk=SA7.0-E5.0-B00005
MacBook-Pro-de-Jacques:~ jacquesallet$"
"ro.build.fingerprint=Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave06040407:user/test-keys"
So it works isn't it?
Hi - so I am only posting as a last result and 4 days of stumbling around rooting, ROMs, and different devices I've finally reached a wall.
I have several LG Aristo 2's that I use on an ESX server for various development machines. They work terrific for what I have them for but the problem is I have particular phones for particular servers and I cannot pick one out of 8 devices because they are all named the same. For the past year or so I have kind of limped but now my environments are a bit more fluid and I need to be able to pick an offending perp out of the line up.
So I have been hacking around on a test phone for the past few days and have driven myself crazy trying to get the model number to change. I have tried several different ROMs, assuming this might be a problem but I just can't seem to change the model name that the devices connects over USB with.
I have updated the build.prop and changed model name, device name, and even added ro.mtp.label and ro.ptp.label.
About to give up thinking this is impossible I had a spare Blu Vivo sitting around and I went through the same process and have been successful in renaming the device doing the things in the line above.
Is this just not possible on the LG Aristo 2?
Android Version: 8.1.0
Model Number: LM-X210MA
Here is a section of my build.prop
Can anyone point me in the right direction? Beer money will be sent!
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=OPM1.171019.026
ro.build.display.id=OPM1.171019.026
ro.build.version.incremental=1832618554af2
ro.build.version.sdk=27
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=8.1.0
ro.build.version.security_patch=2018-11-01
ro.build.version.base_os=
ro.build.date=Thu Nov 22 18:55:26 KST 2018
ro.build.date.utc=1542880526
ro.build.type=user
ro.build.user=jenkins
ro.build.host=LGEACI6R1
ro.build.tags=release-keys
ro.build.flavor=cv1_lao_com-user
ro.build.ab_update=false
ro.product.model=HulkHappy
ro.product.brand=lge
ro.product.name=HulkHappy
ro.product.device=cv1
# 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=LGE
ro.product.locale=en-US
ro.wifi.channels=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=cv1
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=cv1_lao_com-user 8.1.0 OPM1.171019.026 1832618554af2 release-keys
ro.build.fingerprint=lge/cv1_lao_com/cv1:8.1.0/OPM1.171019.026/1832618554af2:user/release-keys
ro.build.characteristics=default
# end build properties
# begin build properties
# autogenerated by vendor_buildinfo.sh
ro.product.board=QC_Reference_Phone
ro.board.platform=msm8937
ro.vendor.product.manufacturer=LGE
ro.vendor.product.model=LM-X210
ro.vendor.product.brand=lge
ro.vendor.product.name=cv1_lao_com
ro.vendor.product.device=cv1
ro.ptp.label=HulkHappy
ro.mtp.label=HulkHappy
@WelpImStuck
Not sure it will solve your problem: you can programmatically change an Android device's name and its ID by means of ADB:
If OS is Android 7.1 and higher to change device's name
Code:
adb devices
adb shell settings put global <DEVICE_NAME>
If OS is Android 8 and higher to change device's ID
Code:
adb devices
adb shell settings put secure <ANDROID_ID>
@jwoegerbauer
Awesome, thank you for the information. I had been using a version of the first one and it did not get me as far along as what you just shared. So using
Code:
adb shell settings put secure global device_name "device name"
I have now at least been able to differentiate on the direct server what device is connected. In my ESX host it still shows the Model LG LM-X210G. I'd share some images but I guess my n00b status, rightly so, won't allow that.
But using my eyes:
ESX shows the USB device as: LG LM-X210G
Easy Tether shows the devices as: LMX210G1db3... (stripping the rest, but guessing its part of the serial)
Windows shows the device as: HulkHappy
... since HulkSmash destroyed the first phone I was trying this on.
Is there any where else I can look? My biggest desire is to get my ESX host in line.
jwoegerbauer said:
@WelpImStuck
Not sure it will solve your problem: you can programmatically change an Android device's name and its ID by means of ADB:
If OS is Android 7.1 and higher to change device's name
Code:
adb devices
adb shell settings put global <DEVICE_NAME>
If OS is Android 8 and higher to change device's ID
Code:
adb devices
adb shell settings put secure <ANDROID_ID>
Click to expand...
Click to collapse