I have an Android device, that is a Chinese TV that runs on Android 4.4.4. I'm developing an app that needs root access to properly function which I will then install on the device.
I can connect to the devices via ADB over WiFi and gain root access too.
But I cannot gain root access from the app. A quick check by RootChecker app revealed that the "root access is not properly installed on the device". When my app tries to gain root access the error "uid xxx not allowed to su" occurs.
Turns out that the device is only stock root/systemless root.
So far, I've copied the su binary from my rooted Xiaomi Redmi 2 into the TV and replaced the /system/xbin/su with that file and changed the permissions. For some reason this did not work.
CPU model name of TV = ARMv7 Processor rev 5 (v7l)
CPU model name of phone = ARMv7 Processor rev 0 (v7l)
Since stock root is available, there must be a very straightforward way for me to root the device. Is it maybe possible to install TWRP on a device like this so that I can flash the SuperSU?
prashand said:
I have an Android device, that is a Chinese TV that runs on Android 4.4.4. I'm developing an app that needs root access to properly function which I will then install on the device.
I can connect to the devices via ADB over WiFi and gain root access too.
But I cannot gain root access from the app. A quick check by RootChecker app revealed that the "root access is not properly installed on the device". When my app tries to gain root access the error "uid xxx not allowed to su" occurs.
Turns out that the device is only stock root/systemless root.
So far, I've copied the su binary from my rooted Xiaomi Redmi 2 into the TV and replaced the /system/xbin/su with that file and changed the permissions. For some reason this did not work.
CPU model name of TV = ARMv7 Processor rev 5 (v7l)
CPU model name of phone = ARMv7 Processor rev 0 (v7l)
Since stock root is available, there must be a very straightforward way for me to root the device. Is it maybe possible to install TWRP on a device like this so that I can flash the SuperSU?
Click to expand...
Click to collapse
How can you have resolved the access root up CPU model name of TV = ARMv7 Processor rev 5 (v7l)? Thanks
Related
i am trying to root some cheap tablet. its based on arm9 wm8800 dual core ,running android 4.4. in developers options there is option to set super user permission (always ask,etc) but it doesnt do anything,when i ran root checker it shows its not rooted,and when i installed superuser from play store it says something about SU binary also apps that require root wont work etc.. so i tried several other options.. after running z4root there's no more su binary problem. root checker shows its not properly rooted,it shows that su binary is there in system/xbin/su but there's red text with some permissions .like i need to fix them,but dont know what to do.. i have rooted many devices,but this is hard.. any help??
Hi,
I've been trying to root my Argos Bush MyTablet 10.1" running Android 4.4.4 for a while now, but all the rooting methods I have tried didn't work.
Framaroot (The exploit didn't work)
Key Root Master (I don't understand, since it's Indonesian, but some kind of error popped up.)
Root Master (Failed to root.)
iRoot (Failed to root.)
TowelRoot (device not supported. I tried using different modstrings, but they all turned my screen gray and rebooted my device.)
I have no access to a computer.
Argos ac101bu
Hi,
Really struggling to root this tablet. I have spent around 4 days trying.
I first altered the boot.img and set it up for adb.
ro secure = 0
allowmock location = 1
constant usb device = adb
ro debuggable = 1
This stops the "cant use adb root on production builds".
However, when I do adb root, it just says restarting adb as root.
It disconnects and then adb cant see the device, I have checked the drivers and its still there.
The device changes to "class for rk device", I tried lots of different drivers, but nothing seems to work after using "adb root".
I then also altered the system.img and made these changes.
ro factory location = 2 <-- which should use external SD (also added media,rw to permissions).
ro rkadb root = 1
ro secure = 0
I also manually installed SuperSU and set all the correct permssions. chown 0.0 and 06755 (in both xbin and bin).
SU works but SuperSU apk cant see the SU binary for some reason and doesnt show grant permission option. So its bassically useless.
Very frustrating, can anyone help?
EDIT:-
Got it rooted now, adb root still wont work. However I managed to manually root by following SuperSU v1.93 update script. Had to mount system.img in linux and edit that way.
Hi .. I also have got one of these... how did you manage to get it rooted???
Cheers
tron1275 said:
Hi .. I also have got one of these... how did you manage to get it rooted???
Cheers
Click to expand...
Click to collapse
Sorry for not answering sooner. I have the custom system image, if you still need it.
Its around 1.6gb, you have to flash it via rockchip flash tools. I also tweaked it some more and added init.d support.
After rooting we instal busybox and SuperSU (or Superuser) and avail the benefits of rooting. When we unroot through SuperSU, is it possible that 'su' still remains inside '/system' folder? I came across a strange phenomenon : I rooted my Celkon Q 500 ( by Root Genius or One-click method or something else, I do not remember) and installed many root apps. After somedays, I decided to unroot, I uninstalled super su, busybox. Then, I tried to root it again. But, I noticed that one root checker says ur device is rooted(specifically through Root Genius PC software I got the message rooted and pressed the 'unroot' button, but it said failed), 2nd root checker says it is non-rooted, 3rd one says it has root access through ADB. I checked 'su' is present in some folder inside '/system', which could not be deleted , because I think, I do not have RW privilege. I had tried many method to root it again, but all failed. When I open Supersu, it throws an immediate message that 'su binary' needs to be updated and when I try it fails everytime. Can anyone meke me understand, what is the real proble.? Celkon Q 500 is Broadcom chip based, running android 4.4.2. Also I found One message in the root checker that "SELinux enforced".
Eversmile23 said:
After rooting we instal busybox and SuperSU (or Superuser) and avail the benefits of rooting. When we unroot through SuperSU, is it possible that 'su' still remains inside '/system' folder? I came across a strange phenomenon : I rooted my Celkon Q 500 ( by Root Genius or One-click method or something else, I do not remember) and installed many root apps. After somedays, I decided to unroot, I uninstalled super su, busybox. Then, I tried to root it again. But, I noticed that one root checker says ur device is rooted(specifically through Root Genius PC software I got the message rooted and pressed the 'unroot' button, but it said failed), 2nd root checker says it is non-rooted, 3rd one says it has root access through ADB. I checked 'su' is present in some folder inside '/system', which could not be deleted , because I think, I do not have RW privilege. I had tried many method to root it again, but all failed. When I open Supersu, it throws an immediate message that 'su binary' needs to be updated and when I try it fails everytime. Can anyone meke me understand, what is the real proble.? Celkon Q 500 is Broadcom chip based, running android 4.4.2. Also I found One message in the root checker that "SELinux enforced".
Click to expand...
Click to collapse
reinstall super su from play store go to settings in super su app and unroot there
selinux enforced means that your kernel is not permissive. has nothing to do with root
Hello Friends,recently I purchased a Datamini TWG10 Tablet whose ,
Build No :--> inet_phone_32-userdebug 5.1.1 LMY47V eng.inet_xch.20151009.121200 release-keys
This Tablet comes with Dual OS,i.e., Windows-10 & Android-5.1.1
Both are performing fully O.K.
Except that the root can't be accessed in Android-5.1.1.
The "su" shows Root : no root access
"superuser" does not function ,and it shows to manually re-root and update again.
The file directory for "su" is under /system/xbin/su
and permission for "su" is as : -rws--x---
How do I access the root ???????????
Please Help,Friends.
Moreover If I downgrade to Android-4.4.4(KitKat),to flash and re-root,can I apply this ???:--->(ONDA V891 Tablet ROM)
inet_phone_32-userdebug 4.4.4 KTU84P eng.inet_rance.20150129.210119 dev-keys
CPU of my Tablet is Intel Atom Z3735F Quad Core processor.
I had downloaded and installed Kingroot / Kingoroot ,both tools separately,but at the end of nearly 90% processing ,both the tools shows "no root access" as error in statement.
PLEASE HELP ME FRIENDS.
Also, how do I unlock the bootloader???
I'm new to Android. My chinese JTY Model N111 (KT107) only has 1GB of RAM which e.g. causes choppy playback of iOS mov files.
Besides this it has lots of china chunk that can't be disabled properly
Therefore I'd like to use Roehsoft RAM-Expander (SWAP) which requires root.
My specs:
http://specdevice.com/showspec.php?id=00de-2520-ffff-fffff1109570
Mediathek MT6592, 8x ARM cortex A7 @2Ghz,
Device: Manufact JTY, Model N111 (KT107)
Kernel 3.10.72+
I'm currently trying this without success:
How to Root every MTK China Phone - Readback With SP-Flash - Root + CWM on INEW V8 [HD]
https://www.youtube.com/watch?v=s66e-kwvKUU
I could solve these problems:
- PDAnet ADB driver didn't recognize device. I used VCOM usb driver for win 10 (worked)
- Mtk_Droid_Tool_v2.5.3 didn't recognize phone, I used MTKDROIDTOOLS-FIX-1.1 from here https://forum.xda-developers.com/android/general/fix-impossible-to-start-adb-error-t3582571 (worked)
However I've the following problems:
1. Error messages
--- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!
ATTENTION! File /system/recovery-from-boot.p which restore factory recovery in case of phone switching on in a normal mode Is Found!
(see attachment)
I tried different MTKdroidtool versions from different sources, there is plenty of internal mem and SD card mem
2.
Blocks map displays create scatter file greyed out: I'm unable to create a scatter file to store my current rom on HD
3.
engineering mode: user2root missing
*#*#3646633#*#*
shows engineering mode but Log and Debugging there is user2root button!
I tried to update Engineering Mode from playstore without success
4.
A desparate trial of RootGenius_en_3.1.3 caused me an unable to root error.
--> What can I do to store my current rom on a laptop to restore it if something happens?
--> How can I gain root access for my device?
--> Is there a faster alternative to add some RAM than with Roehsoft RAM-Expander?
Thank you very much for your help!
MediaTex K107 KT107N
I am in the same boat. New to rooting, and I have this device. I have tried all sorts of tutorials and keep running into roadblocks.
At this point I am not sure if the device is rootable (most likely) and I just don't know enough to get it done, or if it is not rootable.
There is probably some key piece of information I am missing, like "oh that is the same as a such and such device, just a different name."
I have a similar bmxc k900 device (mt6582), (possibly the same thing in a slightly different chassis) i cannot root it , cannot flash it , cannot put a custom ported recovery on it , nothin