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
Related
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..
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!
Q&A for [ToolKit] Acer Iconia v0.8.5 ***New: Supporting A1-810 with Kitkat***
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Question
First thank you for the Iconia Toolkit... it's awesome and has helped a lot, now I have a question, swap makes able moving apps to my sd card? and can i make swap in my Iconia B1-720 with android kitkat? Thank you!
Trying to download img
I am trying to download my system.img from my Acer A1-810 (KitKat 4.4.2) this is what I get from "toolkit -d"
Creating system.img.gz (this will take about 7 minutes) ...
[email protected]:/ $ /data/local/tmp/busybox telnet 127.0.0.1 1234
telnet: can't connect to remote host (127.0.0.1): Connection refused
96 skip=17664 count=262144 | gzip > /cache/system.img.gz <
/system/bin/sh: can't create /cache/system.img.gz: Permission denied
/dev/block/mmcblk0: cannot open for read: Permission denied
Any help would be appreciated
system image a1-810
Does anyone have a prerooted system image RV0BRC01_WW_GEN1? I need it for rooting my a1-810 with my windows pc. Thanks for everybody in advance!
Pulling the system.img
I am trying to download my system.img from my Acer A1-810 (KitKat 4.4.2) this is what I get from "toolkit -d"
Creating system.img.gz (this will take about 7 minutes) ...
[email protected]:/ $ /data/local/tmp/busybox telnet 127.0.0.1 1234
telnet: can't connect to remote host (127.0.0.1): Connection refused
96 skip=17664 count=262144 | gzip > /cache/system.img.gz <
/system/bin/sh: can't create /cache/system.img.gz: Permission denied
/dev/block/mmcblk0: cannot open for read: Permission denied
Any help would be appreciated
remove Superuser
Hello,
a few months ago I rooted my A1-810 (Acer_AV052_A1-810_RV27RC03_WW_GEN1) by the Toolkit version 0.8.3 (Android 4.2.2, method: from scratch).
Rooting was successful. Superuser app was automatically installed by the toolkit.
Later, before KitKat update, I have unrooted my tablet using the Toolkit, because I have heard, that an upgrading a rooted device could lead to a problems.
Update (OTA) to KitKat version was successful, but since then, I often see a message in the notification bar that the superuser app requests for su binary update.
Seems, the Superuser app remained in the system after unrooting and survived the KitKat update also.
I am on unrooted device now, so I don't need Superuser app anymore, but I can't uninstall it ordinarily from OS menu.
Is there a way to remove relics of the Superuser app?
Do I have to root the tablet again to be able to do remove the Superuser app?
Thank you in advance for help!
Help unrooting with [ToolKit] Acer Iconia v0.8.5
Hi I have an Acer Iconia B1-710 I rooted it a few months ago and need to unroot it as an app I am trying to use will not work with a rooted device, I followed the instructions for unroofing within the Tool kit listed above in the title, but for some reason even though Toolkit reports that an unroot has been successful when Irun a check it sshows as still rooted and the app will not run still.
Does anyone have this problem and or some advice for me on this problem? Thank you
Brian
Does anyone have an idea how to get mount permission fix on A1-810 (4.2.2 rooted). I'm trying to install Xposed but it keeps on failing to install framework due to failing to mount /system writable....
Sent from my Galaxy Nexus using Tapatalk
RV02RC20 for Acer A1-811 is down
Hi there
Is there any chance to get the RV02RC20 system.img.gz rooted and stock (including xposed) for the Acer A1-811 because the link is down and my tablet also I would be glad for any help
Thx
Toolkit root function not working
I tried rooting my Acer Iconia B1-710 Tablet, but got this issue (see attachments) after I selected the "Root" function on the toolkit.
Error for root on B1-710
I have the same problem as the Guy upper me:
NameError: global name 'selection' is not defined
Annoying, but thanks for your work.
Sorry for my poor english.
Acer Iconia B1-730HD
Hello. Can you please add Rooting instructions and [ToolKit] Acer Iconia v0.8.5 *** for Acer Iconia B1-730HD?
I see request of /proc/dumchar_info AND /system/build.prop to do so, but there isn't any dumchar_info file anywhere on the phone.
BUILD.PROP is:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=Acer_AV0K0_B1-730HD_1.013.00_WW_GEN1
ro.build.version.incremental=331
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=Thu Sep 11 15:11:56 CST 2014
ro.build.date.utc=1410419516
ro.build.type=user
ro.build.user=builder
ro.build.host=buildserver06
ro.build.tags=release-keys
ro.product.model=B1-730HD
ro.product.brand=acer
ro.product.name=b1-730hd_ww_gen1
ro.product.device=vespa
ro.product.board=clovertrail
ro.product.cpu.abi=x86
ro.product.manufacturer=Acer
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=clovertrail
# ro.build.product is obsolete; use ro.product.device
ro.build.product=vespa
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=redhookbay-user 4.4.2 KOT49H 331 release-keys
ro.build.fingerprint=acer/b1-730hd_ww_gen1/vespa:4.4.2/KOT49H/331:user/release-keys
ro.build.characteristics=tablet
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.streaming.video.drs=true
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.4_r4
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=Proxima.ogg
ro.carrier=unknown
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=2m
dalvik.jit.code_cache_size=1048576
ro.hwui.texture_cache_size=24.0f
ro.hwui.text_large_cache_width=2048
ro.hwui.text_large_cache_height=512
drm.service.enabled=true
ro.blankphone_id=1
persist.sys.dalvik.vm.lib=libdvm.so
ro.ril.status.polling.enable=0
ro.product.cpu.abi2=armeabi-v7a
ro.config.personality=compat_layout
rs.gpu.renderscript=0
rs.gpu.filterscript=0
rs.gpu.rsIntrinsic=0
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.build.pandora.id=Acer_AV0K0_B1-730HD_RV03RC01_WW_GEN1
ro.build.sku=WW_GEN1
ro.error.receiver.system.apps=com.acer.android.acernidus
ro.com.google.clientidbase=android-acer
ro.product.image_pn=FM.NPAA0.01G
ro.product.sku=Wi-Fi
config.volumekey.delay=150
Popartic said:
Hello. Can you please add Rooting instructions and [ToolKit] Acer Iconia v0.8.5 *** for Acer Iconia B1-730HD?
I see request of /proc/dumchar_info AND /system/build.prop to do so, but there isn't any dumchar_info file anywhere on the phone.
Click to expand...
Click to collapse
Sorry, but Intel-based Iconias are still not (and never will be) supported (see post 1 of this thread)
Root for Acer Iconia Tab 10 A3-A20 FHD possible?
Not wanting to hijack this thread but hoping that someone might be able to shed some light on my issue, and some of you out there might be able to point me in the right direction.
I recently updated my A1-810 (PA_CA Model) to KitKat using the recovery bootloader and the image obtained from the Acer support site; Now my unit is stuck in a reboot loop where it doesn't get past the loading 'Acer' logo and just keeps rebooting.
I updated to RV0BRC05 for the PA_CA (canadian) model, and have tried everything to get it past this reboot loop without any success (such as a system/cache wipe, reinstalling the OS, etc). The KitKat update never fails when reinstalling it, but the boot loop will NOT go away, and unfortunatly I am now getting a assert failed: getprop("ro.product.name") == "a1-810_pa_ca" error when trying to downgrade to any previous version than the KitKat release.
Really really REALLY disappointed and frustrated with Acer and their feeble attempt at getting KitKat running on this unit, and am hoping that someone out there might be able to help me get this sucker up and running again.
Any suggestions?
Update: Fixed it!!
I basically followed the guide at: http://forum.xda-developers.com/showpost.php?p=55501253&postcount=53
and downloaded the A1-810 files and Drivers package from there as well.
Then my unit managed to get past the reboot loop and boot into KK successfully!
CWM didn`t actually install, but there is a note at the bottom of the link regarding that, but I`m not going to bother for now as I am more than happy to have a working tablet again!
Hope this helps anyone else!
Problem with Toolkit B1-A71
I also got the "script-problem" as you can see below. Like nikagl posted in the main Thread, i came across those lines in the Python-Script and tried some fixes, but it seems, the .exe doesn't apply them. Does it need an update from you or can we do this ourselves?
================== Root =================
Before we can start, please do following:
1. Make sure drivers for your Acer Iconia B1-A71 are installed, you can find the
m here: goo.gl/doR8L
2. Plug-In your Acer Iconia B1-A71 into this PC.
3. Enable USB Debugging Mode by going into Settings -> Developer Tools.
4. Put prerooted system.img.gz into folder: system_image of this toolkit.
5. Keep your device plugged in until it's finally rooted, or this procedure is a
borted!
If you sucessfully applied the steps above, we can now start.
You can always abort by pressing Ctrl+C
[ENTER] Continue
[Q] Quit
Enter a selection:
Traceback (most recent call last):
File "<string>", line 1405, in <module>
File "<string>", line 147, in main
File "<string>", line 186, in menu
File "<string>", line 683, in root
NameError: global name 'selection' is not defined
A3-A11
Hi,
what about root Acer Iconia Tab A3-A11 device with Android 4.4.2 KitKat?
A3-A11 root error
I set up proper driver for A3-A11 and toolkit got system.image!
(Composite ADB Interface from Google)
But I got error when I start root:
Composite ADB Interface
Traceback (most recent call last):
File "<string>", line 1405, in <module>
File "<string>", line 147, in main
File "<string>", line 186, in menu
File "<string>", line 683, in root
NameError: global name 'selection' is not defined
Problem upgrading my Acer Iconia tablet to Android 4.4 KitKat A1-810. Help!!
My tablet has installed Android 4.2.2 Jelly Bean. My version of the image is Acer_AV052_A1-810_RV26RC06_PA_CUS1.
I went to the official website of Acer and locate the OS 4.4 KitKat for my tablet which is:
Acer.AV0K0.A1-810.RV0BRC02.PA.CUS1
I've tried updating several times and I've even searched the forum to see if it says anything about this but I find nothing.
Each you see I'm trying to upgrade starts and then I get the error:
- Install / sdcard ...
Installing update ...
Warning: No file_contextRemove last update te_finish_update.txt ...
set_metadata_recursive: some failed Changes
check.partition.size + [__ PROP_UNDEFINED__]
instalation aborted
Can anyone tell me how to fix this.
Thank you.
rooting acer iconia a1 810 tablet
Hi! Is there a chance to unroot this tablet? i mean, if i need to send it back to acer, how do I unroot it? thanks
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 ..
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