Greetings
I searched the forums but nothing related to my issue was found
I recently got an android PC stick MK809IV (Unbranded) with Kitkat 4.4.2 Rom which has Rockchip RK3188T / 1.4-1.6GHz Quad core as CPU
I managed to try at least two rooting methods (plus some hacking through adb) but failed to have proper root.
The drivers for the stick are properly installed and I get "root@rk3188:/ #" while using "adb shell" and root with id command
root@rk3188:/ #
id
uid=0(root) gid=0(root) context=u:r:shell:s0
root@rk3188:/ #
The method TPSparkyRoot with the batch file from here (Modified to work properly) has showed confirmation that root is ok, as there was no errors during process
I checked file system in read only mode (with xPlore) : su and busybox binaries are in /system/bin, SuperSU also installed in /system/app with 644 permission and root.shell ownership but no ROOT.
The SuperOneClick method tells me that device is rooted but in fact nothing
I think it is permissions and ownership issue or an incompatible su binary (I have tried many ones, sometimes SuperSU says there is no binary, other times says it have to be updated but fails) but have not any clue on how to solve it.
This stick is driving me crazy !
Any idea is welcome
I searched the forums but nothing related to my issue was found
I recently got an android PC stick MK809IV (Unbranded) with Kitkat 4.4.2 Rom which has Rockchip RK3188T / 1.4-1.6GHz Quad core as CPU
I managed to try at least two rooting methods (plus some hacking through adb) but failed to have proper root.
The drivers for the stick are properly installed and I get "root@rk3188:/ #" while using "adb shell" and root with id command
root@rk3188:/ #
id
uid=0(root) gid=0(root) context=u:r:shell:s0
root@rk3188:/ #
The method TPSparkyRoot with the batch file from here (Modified to work properly) has showed confirmation that root is ok, as there was no errors during process
I checked file system in read only mode (with xPlore) : su and busybox binaries are in /system/bin, SuperSU also installed in /system/app with 644 permission and root.shell ownership but no ROOT.
The SuperOneClick method tells me that device is rooted but in fact nothing
I think it is permissions and ownership issue or an incompatible su binary (I have tried many ones, sometimes SuperSU says there is no binary, other times says it have to be updated but fails) but have not any clue on how to solve it.
This stick is driving me crazy !
Any idea is welcome
Written by dd
We are Creative Blogger Theme Wavers which provides user friendly, effective and easy to use themes. Each support has free and providing HD support screen casting.
0 commentaires:
Enregistrer un commentaire