Problem: I have an Aishon A19 tablet, which it is very hard to find information about. It is an RK3288 tablet running Android 5.1.1.
It is not really rooted in the normal sense. However, "adb root" works; I can get a root shell and mount /system as writeable, I can push any app I want to the device, etc.
Things that will not work:
-- I tried to put on a /system/xbin/su (from SuperSU 2.76), with mode 6755 (rwsr-sr-x) and it didn't work. I also made symbolic links to /system/bin/su and /system/xbin/daemonsu. Running it from a non-root shell in adb prints a 1 and doesn't give me root. Running it from a non-root shell on the tablet does the same thing. Running it from a root shell gives me no error, but that obviously isn't much use.
-- Running SuperSU as an app gives me the error message about "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 5....." I have no idea if it actually can't see the ./system/xbin/su or if the error message just isn't that good.
-- Trying to use "adb reboot bootloader" or getting into the bootloader using buttons doesn't work. It reboots the tablet into a blank screen, with the same vendor ID and a new product ID; however, "fastboot devices" shows nothing. This happens both under Windows and Linux, and even when run as root under Linux (thus not having to worry about udev rules). This means that I cannot install TWRP unless someone can explain to me how to install TWRP without using the bootloader.
I *can* use "adb reboot recovery" and get into the recovery menu. And as I mentioned, I can get root access to the tablet and a root shell using "adb root", and push any file I want to it.
Is it possible to use this root shell and/or recovery to install SuperSU somehow, even if I have to just copy files one at a time?
It is not really rooted in the normal sense. However, "adb root" works; I can get a root shell and mount /system as writeable, I can push any app I want to the device, etc.
Things that will not work:
-- I tried to put on a /system/xbin/su (from SuperSU 2.76), with mode 6755 (rwsr-sr-x) and it didn't work. I also made symbolic links to /system/bin/su and /system/xbin/daemonsu. Running it from a non-root shell in adb prints a 1 and doesn't give me root. Running it from a non-root shell on the tablet does the same thing. Running it from a root shell gives me no error, but that obviously isn't much use.
-- Running SuperSU as an app gives me the error message about "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 5....." I have no idea if it actually can't see the ./system/xbin/su or if the error message just isn't that good.
-- Trying to use "adb reboot bootloader" or getting into the bootloader using buttons doesn't work. It reboots the tablet into a blank screen, with the same vendor ID and a new product ID; however, "fastboot devices" shows nothing. This happens both under Windows and Linux, and even when run as root under Linux (thus not having to worry about udev rules). This means that I cannot install TWRP unless someone can explain to me how to install TWRP without using the bootloader.
I *can* use "adb reboot recovery" and get into the recovery menu. And as I mentioned, I can get root access to the tablet and a root shell using "adb root", and push any file I want to it.
Is it possible to use this root shell and/or recovery to install SuperSU somehow, even if I have to just copy files one at a time?
No comments:
Post a Comment