LG Aristo 2: Change Model Name - Android Q&A, Help & Troubleshooting

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

Related

[Q] Cyanogen Mod Market Weirdness

Hello everyone,
I was using VeganTab as my ROM of choice for a long time, and recently switched to CyanogenMod7 for a change and a more traditional Android feel.
With VeganTab, I had no issues using the Market. Every app I wanted to download was available in the market. Using CyanogenMod7, when I go to download apps I get a "this application is not available for your device" message on several apps. Firefox being one of them, which the gTablet should be able to support.
Why would one ROM work and the other doesn't on the same device? Has anyone else encountered this and know how to fix it?
Hello, I have one Gtab running CM7 what version/build are you on? Which apps are not showing up other than Firefox? Have you modified anything (build.prop)? If I remember right I had to modify the build.prop to get some apps to show up.
The apps in the market are set up to show only to devices that they are designed to be run on. When you change roms, your device shows up differently to the Market, so some apps might appear that weren't there before and some may dissappear. Read through the thread where you got the rom from and you may find some tips. Also as a temp. solution you can download the .apk files for many apps either to your PC or the the tablet and "side load" it (go to file manager and tap the downloaded .apk to install). Open a root file explorer and go to /system and open build.prop. Let me know what is says for product board, region and lcd density.
Thanks for the quick response Dave.
So far, Agenda Widget and Firefox are the two I can't get through the market. I haven't tried a ton of others yet.
I've been playing with the bool.prop file a little bit, based on tutorials I've seen here and at other forums. This thread seems to offer the best advice, but didn't work for me.
Below are my build.prop values at current time:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GRI40
ro.build.display.id=GRI40
ro.build.version.incremental=eng.cyanogenmod.20110505.210139
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.3
ro.build.date=Thu May 5 21:02:03 CDT 2011
ro.build.date.utc=0
ro.build.type=user
ro.build.user=cyanogenmod
ro.build.host=scout73
ro.build.tags=test-keys
ro.product.model=GTablet
ro.product.brand=passion
#ro.product.brand=nvidia
ro.product.name=passion
#ro.product.name=harmony
ro.product.device=olympus
#ro.product.device=harmony
ro.product.board=harmony
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=malata
ro.product.locale.language=mdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=harmony
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=passion-user 2.3.3 GRI40 102588 release-keys
ro.build.fingerprint=nvidia/harmony/harmony/harmony:2.2/FRF91/20101123.172729:eng/test-keys
# end build properties
#
# system.prop for harmony
#
# density in DPI of the LCD of this board. This is used to scale the UI
# appropriately. If this property is not defined, the default value is 160 dpi.
# Density set to 161 to allow market to function properly
ro.sf.lcd_density=161
wifi.interface = wlan0
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
wifi.supplicant_scan_interval = 45
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072
# This is a high density device with more memory, so larger vm heaps for it.
dalvik.vm.heapsize=32m
# For emmc phone storage
ro.phone_storage = 1
# Add external mount points
ro.additionalmounts=/mnt/emmc;/mnt/usbdisk
# Add reference RIL
rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/ttyS0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.setupwizard.enable_bypass=1
keyguard.no_require_sim=1
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.rommanager.developerid=cyanogenmod
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.modversion=CyanogenMod-7.0.3-Harmony
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Looks from your build.prop file that you are on an older build of CM7. The apps you mentioned, Firefox and Firefox Beta, and the Agenda Widget show up and work on mine. You could try using some of the values in my .prop file here, or update to a newer version of CM7. You might be able to install over your current build without wiping your data, but back up first of course.
Thanks Dave. Can you link me to a stable, updated version of CM7?
There is a CM7 rom hosted here at XDA:
CYANOGENMOD7.2.0-RC0-BUILD98-REPACK
Or you can go to Cyanogenmod Wiki. Don't forget to download the Gapps separately from the bottom of the same page and install them too.
I apologize in advance if it is not allowed to post a link to their wiki page .
Actually I have had this problem ALOT, no matter what version of CM7 I use on it. Its even worse when the new Market gets pushed to it, I usually have to downgrade it back and remove the MarketUpdater.apk so it stays on the old one.
I am running the ICS Alpha/Beta (forget which) right now so everything works, albeit very slow.
I had the same issue it's the odd LCD density of 161 that market doesn't like. I changed mine to 200 then do the standard market fix reboot and it should be fine.
Sent from my HTC Glacier using xda premium

[Q] SDK Emulator Build.prop for games not working

1/15/2015 UPDATE: So it looks like I have a few ideas so far ..
* version of SDK does not matter long as its JB +
* the APKs are all basicly the same what I think is tripking me up is wrong or old play store or google servbices , google games,services framework etc ... if you install google games it asks for update then says it can't because the device is not supported ... so i still have the issue with the play store not having jack @#$% on it .. build.prop seems to take no effect too..I still think its more a google issue then Clash of clans APK blocking SDK's etc ...IE CoC is trying to hook google and it dies because of incompat device or wrong versionts of google sdks ...
10:37 PM 12/22/2014 UPDATE: So build.prop seems to have NO ****ING effect on google play store ... I have tried http://apcmag.com/how-to-fake-an-android-device.htm with verious builds and even after time and deleting the userdata-qemu.img userdata.img cache.img / reboot still nothing ...
I have spent about 3 full days now ****ing with this .. and the only thing that still appears to work is bluestacks pile of ****... I have also copied bluestacks build.prop stings and also removed/changed them to match my build and no ****ing effect ... its almost like build.prop is no doing anything I also tried to remove the last part of the build.prop in BS still it works fine so its nothing that I can tell in the 2nd part of build.prop ...
I have go the Market Helper to work and actually install Clash of Clans but the game *****es about needing to be reinstalled ... I got it to work on NON X86 arm build some how ..... but with HAXM I get **** ... maybe my gapps ? gapps-jb-20130812-signed
* I have tried wiping data from playstore
* removed userdata-qemu.img userdata.img cache.img
* rebooted and setup google play and still no Clash of clans or any games for that matter ... its like its not even listing to the build.prop ?
* google plays still says clash of clans is incompatible.
* I also tried "market Helper" with no luck
* I have tried forcing run of from working build on real phone and it works so its build.prop ... or something else...
* not going to use Bluestacks or any other pile of crap like Jarofbeans ( jar of beans has the same @#$ing issue with no games in play store )... see my prev post http://forum.xda-developers.com/chef-central/android/google-play-store-filtering-bypass-wtf-t2927108
* is it more then just build.prop ? IE I have seen some edits to hardware excel etc .. ?
* notes /ref http://www.androidtablets.net/threads/lets-settle-the-google-play-compatible-issue.46327/
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MASTER
ro.build.display.id=cm_ancora_tmo-userdebug 4.1.2 JZO54K eng.camcory.20121126.063112 test-keys
ro.build.version.incremental=495790
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Tue Oct 9 20:03:51 UTC 2012
ro.build.date.utc=1349813031
ro.build.type=eng
ro.build.user=android-build
ro.build.host=vpbs30.mtv.corp.google.com
ro.build.tags=test-keys
ro.product.model=SGH-T679
ro.product.brand=Samsung
ro.product.name=cm_ancora_tmo
ro.product.device=ancora_tmo
ro.product.board=ancora_tmo
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=generic
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SGH-T679-user 2.3.6 GINGERBREAD UVLE1 release-keys
ro.build.fingerprint=samsung/SGH-T679/SGH-T679:2.3.6/GINGERBREAD/UVLE1:user/release-keys
ro.build.characteristics=default
ro.cm.device=ancora_tmo
# end build properties
#
# system.prop for ancora_tmo
#
rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/ttyS0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
xmpp.auto-presence=true
ro.config.nocheckin=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
So I am the only person with this issue .. BUMP
I found a workaround for now using NOX app player ... but I tried ripping the build.prop from it and it's more then that .. it has dll's and stuff I think its a portable vbox image and some custom dll's etc .. I can't figure it out ... NOX seems a bit China for me but works for testing apps so I dont care too much ..

[Q] Using emulator, missing many Play Store apps

Hi All!
I'm running emulator with clean avd and installed Google Play Store on it (tried with ARM api-18, and ARM api-19).
When I'm accessing play store to browse around, I'm missing many apps- games, utils, etc. If I search directly for a specific app (eg, clash of clans)- I'm showing "your device isnt compatible with this version".
Why is that? Am I missing certain permissions or abilities on the emulator?
If I download the apk and use adb to install to emulator, it works fine- so what am i missing here?
I even tried taking a vanilla nexus-5 build.prop, placed it on the avd, but still- same behaviour.
isn't there a way to browse all apps on play store, and install it directly from there?
thanks!
avivz said:
Hi All!
I'm running emulator with clean avd and installed Google Play Store on it (tried with ARM api-18, and ARM api-19).
When I'm accessing play store to browse around, I'm missing many apps- games, utils, etc. If I search directly for a specific app (eg, clash of clans)- I'm showing "your device isnt compatible with this version".
Why is that? Am I missing certain permissions or abilities on the emulator?
If I download the apk and use adb to install to emulator, it works fine- so what am i missing here?
I even tried taking a vanilla nexus-5 build.prop, placed it on the avd, but still- same behaviour.
isn't there a way to browse all apps on play store, and install it directly from there?
thanks!
Click to expand...
Click to collapse
You havr extension for Google chrome on pc to download apps from playstore.
Go to playstore with google chrome, and go to app which ypu want to download, and download with that extension.
Next when you download it, just launch that .APK and that will be installed on emulator.
Give feedback.
Check the build.prop of the device you are emulating. You might change it to something more universal, like a Nexus 5 or something.
es0tericcha0s said:
Check the build.prop of the device you are emulating. You might change it to something more universal, like a Nexus 5 or something.
Click to expand...
Click to collapse
Thanks es0tericcha0s.
I changed the build.prop to a very standard nexus-5. Here it is - but I still dont get market apps...
Any help would be greatly greatly appreciated. Here's my build.prop:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JB_MR2
ro.build.display.id=JB_MR2
ro.build.version.incremental=wpef12.hot.corp.google.com
ro.build.version.sdk=18
ro.build.version.codename=REL
ro.build.version.release=4.3
ro.build.date=Mon Aug 12 17:40:30 UTC 2013
ro.build.date.utc=1376329230
ro.build.type=user
ro.build.user=android-build
ro.build.host=vpbs16.mtv.corp.google.com
ro.build.tags=release-keys
ro.product.model=Nexus 5
ro.product.brand=google
ro.product.name=hammerhead
ro.product.device=hammerhead
ro.product.board=hammerhead
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LGE
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=hammerhead
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=hammerhead-user 4.3.1 JB_MR2 937116 release-keys
ro.build.fingerprint=google/hammerhead/hammerhead:4.3.1/JB_MR2/937116:user/release-keys
ro.build.characteristics=default
# end build properties
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/ttyS0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
xmpp.auto-presence=true
ro.config.nocheckin=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Could it be related to parameters that are external to the build.prop file-
eg, IMEI, Android ID, SIM Card, or even- the actual google account used to sign in to play store?
This is so frustrating, I dont get how play store decides which apps you see...
avivz said:
Could it be related to parameters that are external to the build.prop file-
eg, IMEI, Android ID, SIM Card, or even- the actual google account used to sign in to play store?
This is so frustrating, I dont get how play store decides which apps you see...
Click to expand...
Click to collapse
It's possible that the emulator might just not be able to run certain kinds of apps. Which emulator are you using?
es0tericcha0s said:
It's possible that the emulator might just not be able to run certain kinds of apps. Which emulator are you using?
Click to expand...
Click to collapse
I'm using the standard sdk emulator- both arm and x86 versions behave the same.
I dont think it's that the emulator can't run the apps- when I manually install apk via adb, it works fine ..

How to find build number on a (soft)bricked phone?

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?

[Solved] Get root on MSTAR Smart TV (Android 5.1.1 Userdebug (Philips 55PUT6002S))

Hi all,
I'm in a mind loop since 10 days now, i search search search and I'm still unable to achieve the root access of the recently purchased Philips 55PUT6002S...
I'm pretty sure this will sound familiar to you..
I have a root access through adb to the "5.1.1" (userdebug build 5.0.8) philips android system (provided to them by MSTAR), I won't list all the try I made (and how many arguments I had with my wife because i've been very late to go bed every night since 10 days...) but the situation is now :
- kingroot and kingoroot unable to root the device
- full root access (rw) to the system through adb
- su (already present from factory in /system/bin) updated from SuperSU-v2.82-201705271822.zip arm64
- busybox present from factory
- unable to su with TerminalEmulatorforAndroid_v1.0.70 (in one of my previous attemp, i was able to use su in this terminal, but unable to use it to launch an app (system returns something same "user who request the am isn't the same as the one logged in the ui)
- i tried to launch the update-binary from supersu from the adb shell, but even renaming it as update-binary.sh i'm unable to make it works..
any suggestion or advice that could help to get out from this "boring's loop"
ro.build.id=LMY47V
ro.build.display.id=aosp_philips_asia-userdebug 5.1.1 LMY47V 5.0.8 test-keys
ro.build.version.incremental=5.0.8
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1.1
ro.build.version.security_patch=2015-11-01
ro.build.date=Tue Sep 19 09:19:08 CST 2017
ro.build.type=userdebug
ro.build.user=yzy
ro.build.host=TD47111
ro.build.tags=test-keys
ro.build.flavor=aosp_philips_asia-userdebug
ro.product.model=TV638_DVB
ro.product.brand=PHILIPS_ASIA
ro.product.name=aosp_philips_asia
ro.product.board=arbutus
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=PHILIPS_ASIA
ro.product.locale.language=zh
ro.product.locale.region=CN
ro.wifi.channels=
ro.board.platform=monet
ro.build.description=aosp_philips_asia-userdebug 5.1.1 LMY47V 5.0.8 test-keys
ro.build.fingerprint=PHILIPS_ASIA/aosp_philips_asia/philips_asia:5.1.1/LMY47V/5.0.8:userdebug/test-keys
ro.build.characteristics=tv
nobody have rooted such hardware and could give me some clues ? ..
Here's the answer to my question... strange that I wasn't able to find the answer on xda..
API21+ & user-debug (root adb shell) :
https://github.com/spff/install-supersu-via-adb
which his the script that helps to do what was explained here 4 years ago :
https://selvaline.blogspot.com/2015/...droid-via.html
woow..thanks for posting this!
I am in the process of trying this same steps

Categories

Resources