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!
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..
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..
Hello !
Could anyone please post the build.prop values for the Sony Tablet S 16GB Wifi only Model (SGPT111US/S) Running ICS ??
I'm unable to restore my build.prop values after modifying it through an app on the PlayStore Called Allwinner Mod, which promised to provide access to more apps on the market by altering build.prop values. It really wasn't of any use
Now that my build.prop has been altered, I'm unable to revert back to the default values. I've tried to restore it from build.prop.bak in root explorer, but somehow the values still remain the same even after replacing.
My tab is currently running on Android 4.0.3 r5a, and is rooted. (Thanks to Bin4ry's method )
I've checked the entire forum for the values, but couldn't find any for ICS 4.0.3 r5a, i could only find values for honeycomb 3.2.1. Hence I'm creating this post.
Have always trusted XDA when it comes to any issue regarding Android, and I've never been let down.:good:
Thanks in advance:good:
audiophile_adi said:
Hello ! Could anyone please post the build.prop values for the Sony Tablet S 16GB Wifi only Model (SGPT111US/S) Running ICS ??
Click to expand...
Click to collapse
Here is build.prop from a Sony Tablet S 32 GB WiFi Only model SGPT112US/S with 4.0.3r5a install via Condi's [FLASHER] tool. I hope you find it useful.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=TISU0143
ro.build.display.id=TISU0143
ro.build.version.incremental=121116032
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Nov 16 04:09:27 JST 2012
ro.build.date.utc=1353006567
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build8
ro.build.tags=release-keys
ro.product.model=Sony Tablet S
ro.product.brand=Sony
ro.product.name=SYS_001
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_001-user 4.0.3 TISU0143 121116032 release-keys
ro.build.fingerprint=Sony/SYS_001/nbx03:4.0.3/TISU0143/121116032:user/release-keys
ro.build.characteristics=tablet
# end build properties
ro.opengles.version = 131072
wifi.interface=wlan0
ro.ethernet.interface=eth0
ro.ethernet.autoEnable=yes
rild.libargs=-d /dev/ttyACM1 -i rmnet0
windowsmgr.max_events_per_sec=120
ro.tether.denied=true
ro.sony.sound.enabled=true
ro.sony.display.release=release5a
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.product-res-path=vendor/framework/SemcGenericUxpRes.apk
ro.sony.autovolume.threshold=10
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
drm.service.enabled=true
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.sony.wifisleep=0
ro.semc.xloud.supported=true
ro.somc.clearphase.supported=true
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=4.0_r3
ro.com.google.clientidbase=android-sony
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.sony.wan.ipv6.enable=false
ro.sony.dlna_dms.enabled=false
ro.somc.social_product_model=PRODUCT_MODEL_TABLET
ro.sony.irremote.protocol_type=1
ro.sony.ols.eula=0
Thanks a ton Cat McGowan ! Cheers
Sent from my Sony Tablet S
audiophile_adi said:
Thanks a ton Cat McGowan ! Cheers
Sent from my Sony Tablet S
Click to expand...
Click to collapse
So, you'd better hold your interest if your tab is rooted.
Could you be a bit clear as to what u want mate ?
Topery Chiang said:
So, you'd better hold your interest if your tab is rooted.
Click to expand...
Click to collapse
If its the method of rooting that you're asking for,
Here's what I did.
1. Backup all ur data, and factory reset the tab, preferably with erase USB option checked.
2. Download Root_with_Restore_by_Bin4ry
3. Once ur tab is reset, complete the initial setup, go to settings, and make sure USB debugging (Developer Options), Unknown Sources (Security) is checked
4.Now to run Bin4ary's script, follow the instructions given in this video tutorial.
5. Instruction for rooting the tab appear from 6:00mins after start of the video.
6. Though the video shows instructions for Xperia Tablet S, the method for the older Sony Tablet S is the same. The only catch being which version of the script to use. As I've mentioned in this thread before, v10 of Bin4ary's script did the job for me.
7. If all the steps are followed as shown in the video, you will be able to root your tablet successfully.
Don't forget to thank WonderEkin for translating the rooting method from japanese, and also Bin4ry for making the rooting procedure so much simpler through his script !!
audiophile_adi said:
If its the method of rooting that you're asking for,
Here's what I did.
1. Backup all ur data, and factory reset the tab, preferably with erase USB option checked.
2. Download Root_with_Restore_by_Bin4ry
3. Once ur tab is reset, complete the initial setup, go to settings, and make sure USB debugging (Developer Options), Unknown Sources (Security) is checked
4.Now to run Bin4ary's script, follow the instructions given in this video tutorial.
5. Instruction for rooting the tab appear from 6:00mins after start of the video.
6. Though the video shows instructions for Xperia Tablet S, the method for the older Sony Tablet S is the same. The only catch being which version of the script to use. As I've mentioned in this thread before, v10 of Bin4ary's script did the job for me.
7. If all the steps are followed as shown in the video, you will be able to root your tablet successfully.
Don't forget to thank WonderEkin for translating the rooting method from japanese, and also Bin4ry for making the rooting procedure so much simpler through his script !!
Click to expand...
Click to collapse
What I mean is that you'd better not easily modify your system files, if your is rooted.
I don't want to know the process of root.
~hold=restrain~
Sorry for my unclear words.
Thanks mate ! Appreciate your concern.
Topery Chiang said:
What I mean is that you'd better not easily modify your system files, if your is rooted.
I don't want to know the process of root.
~hold=restrain~
Sorry for my unclear words.
Click to expand...
Click to collapse
I Appreciate your concern Topery Chiang:good:
My bad, I mistook what you meant, I thought u needed the method of root as ur list of devices mentions a Sony Tablet S 4.0.3 R5 not rooted.
Peace Out !:angel:
audiophile_adi said:
I Appreciate your concern Topery Chiang:good:
My bad, I mistook what you meant, I thought u needed the method of root as ur list of devices mentions a Sony Tablet S 4.0.3 R5 not rooted.
Peace Out !:angel:
Click to expand...
Click to collapse
I don't like the “Peace Out”, it's a ambivalent word.
Need build prop for iball slide twinkle i5
Please !!!
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 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