My dad the other day bought two cheap, generic tablets. They're running kitkat (4.4.2), have a quad-core, 1.8 ghz processer and 2 gigs of ram, it also has Android System Recovery 3e. The problem is that I can't seem to root it! I've tried multiple ways of rooting it including(but not limited to): vRoot, towelroot, root with restore by Bin4ry. The weird thing is that adb shell has root, but the device doesn't, and supersu keeps saying the su binary isn't installed and it cannot install. I have supersu installed as a system app and su and busybox in /system/xbin and /system/bin. I've tried doing adb shell chmod 777 /system/, but that won't even allow me to do anything. PLEASE HELP!!!!
CalebQ42 said:
My dad the other day bought two cheap, generic tablets. They're running kitkat (4.4.2), have a quad-core, 1.8 ghz processer and 2 gigs of ram, it also has Android System Recovery 3e. The problem is that I can't seem to root it! I've tried multiple ways of rooting it including(but not limited to): vRoot, towelroot, root with restore by Bin4ry. The weird thing is that adb shell has root, but the device doesn't, and supersu keeps saying the su binary isn't installed and it cannot install. I have supersu installed as a system app and su and busybox in /system/xbin and /system/bin. I've tried doing adb shell chmod 777 /system/, but that won't even allow me to do anything. PLEASE HELP!!!!
Click to expand...
Click to collapse
Well, try to use Framaroot (or smth like that, forgot the name). It should succeed because as are You describing, it have the "3e" recovery which i think is using MTK SoC. If Framaroot fails, find "MTK Droid Tools". Hope that solved Your problem
david19au said:
Well, try to use Framaroot (or smth like that, forgot the name). It should succeed because as are You describing, it have the "3e" recovery which i think is using MTK SoC. If Framaroot fails, find "MTK Droid Tools". Hope that solved Your problem
Click to expand...
Click to collapse
Tried both, framaroot give me error #6 and all MTK Droid Tools did was (it seemed) got rid of SuperSU. Another piece of information I forgot to add was: to edit system files in adb I have to do adb remount before it would work or else it'd say that it was a read-only file system.
Another piece of information that might be helpful is that when I try to execute su from a terminal emulator, all that happens is a 1| appears in front of the device name.
Sent from my Nexus 5 using XDA Premium HD app
CalebQ42 said:
Tried both, framaroot give me error #6 and all MTK Droid Tools did was (it seemed) got rid of SuperSU. Another piece of information I forgot to add was: to edit system files in adb I have to do adb remount before it would work or else it'd say that it was a read-only file system.
Click to expand...
Click to collapse
Did You tried to do "adb remount" leave the terminal and use Framaroot?
Yep, didn't make a difference. Even tried adb shell -o remount,rw for / and /system
Sent from my Nexus 5 using XDA Premium HD app
Related
Okay, my Atrix is rooted and USB Debugging is on, but when I try to remount adb, it says "remount failed: Operation not permitted". Since I can't get adb shell to the # to come up, I type "adb shell su" and I get a Permission denied. I originally rooted with SuperOneClick and enabled sideloading with it and today I rerooted, unrooted, then used DesignGears' new root script to reroot and clean up SuperOneClick's root. Still no adb root access. I have TitaniumBackup, Superuser, and RootExplorer installed and even downloaded Root Checker to check if i really had root. I've spent almost all day looking this up and the closest I've found is the thread that talks about adb showing the device offline with the fix of copying over another adbd to the sbin folder(which I also tried) and adb still doesn't seem to recognize my root. The only time I can get the # prompt is when I do a shell root with SuperOneClick, but that is just a temporary root. Is anyone else experiencing this?
Edit: forgot to mention that adb works fine when I connect my NexusOne, so it's probably not the computer.
I've followed the following thread CF-root 4.1.
Everything went fine and the kernel is rooted.
I can use apps which require root, like TitaniumBackup.
I also can use su to gain root privileges and also adb shell and then su. To make this more clear. I first get $ (user priv) and then with "su" i get # (root priv).
For this reason i can't use the adb push method, because i'm not root directly.
adb root which is suggested in a couple of threads isn't helping me. I get the following output. "adbd cannot run as root in production builds".
How can i fix it, so i can have root privileges directly when connecting via the adb shell?
You need an "insecure kernel" for that.
There are several for download in a thread in the dev section.
Why do you need ADB to be running as root for pushing, if you don't mind asking?
bla
HellcatDroid said:
You need an "insecure kernel" for that.
There are several for download in a thread in the dev section.
Why do you need ADB to be running as root for pushing, if you don't mind asking?
Click to expand...
Click to collapse
Many thanks for illuminating people in this situation!
Cuz it's obviously more comfortable to do stuff using the computer's keyboard.
Hello everyone!
I've recently purchased a Vodafone Smart Tab 10 running Honeycomb 3.2.
I would like very much to root the device and kill the bloat a bit.
The hardware is good, but it seems that Honeycomb + bloatware is not the best way to go for a smooth experince...
Maybe the process would be similar for the Vodafone Smart Tab 7, too:
[Q] How to root Vodafone Smart Tab 7
Smart Tab on Vodafone's site:
Vodafone Smart Tab 7/10
Thanks.
We need a compatible CW recovery. There is the 3e recovery onboard like in Samsung devices. We have a working adb and fastboot. Bootloader is unlocked.
Sent from my SmartTab10 using Tapatalk
You can get source on
HTML:
http://www.vodafone.com/content/index/about/what/devices/vodafone_smart_tab.html
You can pull config from device.
Yeah, this device is cheap and good, but we need root for it. Come on, I'm sure that someone can make custom recovery and root for this device.
I would go and try this.
But downloading of the source would take me years on my sucky hotel internet now. Maybe when I get home.
Yes but you'll need a rooted devices to dump recovery.img and to read the partition layout. We need to root it first. I have tried the gingerbreak with gingerbreak.apk and oneclickroot but without success. Any ideas?
Sent from my SmartTab10 using Tapatalk
Does anyone know the password to bluez package of the source?
Noup. Whay they set the password at all? Any progress with the recovery buildup?
Sent from my SmartTab10 using Tapatalk
BlueZ
Unless I'm mistaking, BlueZ is a package dealing only with bluetooth functionality.
It should be of no concern in the early stages of root/custom ROM implementation.
sangemaru said:
Unless I'm mistaking, BlueZ is a package dealing only with bluetooth functionality.
It should be of no concern in the early stages of root/custom ROM implementation.
Click to expand...
Click to collapse
You are right about BlueZ. Any idea of the method we could use to root this device?
Sent from my SmartTab10 using Tapatalk
To my understanding, it's possible to perform a root through ADB.
Since the device is unlocked in just about every other possible way, it shouldn't be too much of a chore.
I'll be having a look over possible ways to do that tonight.
$ adb shell /system/bin/cmdclient ec_micswitch ‘`mount -o remount,rw /system`’
adb shell /system/bin/cmdclient ec_micswitch '`mount -o remount,rw /system`'
liuyuanyuan prjName is <V11A>
liuyuanyuan exit adbd if usb_mass_storage is enabled on V66 or V68
error: device not found
What the f this liuyuanyuan wants from me He is good o yes
EDIT: This device does not have cmdclient & cmd_server_daemon running!
mobilx said:
$ adb shell /system/bin/cmdclient ec_micswitch ‘`mount -o remount,rw /system`’
adb shell /system/bin/cmdclient ec_micswitch '`mount -o remount,rw /system`'
liuyuanyuan prjName is <V11A>
liuyuanyuan exit adbd if usb_mass_storage is enabled on V66 or V68
error: device not found
What the f this liuyuanyuan wants from me He is good o yes
EDIT: This device does not have cmdclient & cmd_server_daemon running!
Click to expand...
Click to collapse
I think it's more likely that you don't have the proper device drivers on your computer.
I have the links at work, I'll try to see about them tomorrow. Were you in Recovery or Development mode?
I'm using a pached by myself drivers from ZTE 3g phone archive that I found somewhere. ADB works fine. This is a root method for the Acer iconia 100 but it doesn't work because our device does not have cmdline binary in /sys/bin. I tried to pull it out from some Iconia ROM and adb pushed it to /data/local but there is the catch also. Cmd_server_daemon needs to be started which is impossible without the root permissions.
If you have the original drivers for this device please provide us a link.
Sent from my SmartTab10 using Tapatalk
Here's a link to the original V71 drivers, which I'm assuming would be the same for the V11 here.
For my device, the daemon runs properly with these drivers, but I need to have no drivers installed first, connect the device, then install the drivers with the device connected. The drivers came included on the device.
You should first try uninstalling all drivers relating to tablets/phones, then connecting the device and seeing if any drivers show up in a new detected "CD Drive" (ZTE loves doing this).
Also, any owners of the SmartTab7/SmartTab10 a.k.a v71a or v11a please vote for these devices on the new device voting thread. We need all the effort we can spend if we're going to see these devices properly supported.
mobilx said:
I'm using a pached by myself drivers from ZTE 3g phone archive that I found somewhere. ADB works fine. This is a root method for the Acer iconia 100 but it doesn't work because our device does not have cmdline binary in /sys/bin. I tried to pull it out from some Iconia ROM and adb pushed it to /data/local but there is the catch also. Cmd_server_daemon needs to be started which is impossible without the root permissions.
Click to expand...
Click to collapse
For me, i could push files to /data/local just fine, i can perform apk installations through adb, however i can't execute almost any command.
Everything would have been fine if we could do $adb shell su, but i get permissions error even with modified su file, so i have no idea what to do.
The weird thing is that cmd_server_daemon runs just fine for me, however i can't get any permissions at all.
Using adb root tells me that root is not available for production models.
Do you have the cmd_server_daemon listed in ls -l /system/bin ?
If you have you can use this Method
Sent from my SmartTab10 using Tapatalk
No, i don't have it listed. Which is weird, because I've seen mentions of it booting and running successfully... i think.
We are pretty stuck. If someone could get stock firmware. We need a boot.img or a hc 3.2 exploit.
We're not stuck at all, actually.
We have the source code, remember?
If i can find any instructions on how to integrate root with it, I can just build the rom.
Is there any way to root Toshiba excite at300se ?.Or Stock ROM link .I try to find the adb driver and CWM for the this tablet.:crying:
Don't worry bro.....
We will find the solution (one day)
did anyone find a way to root the AT300SE (Excite 10SE), or the AT305, they are the same as far as I know
the AT305 is the US edition.
Check this below link for ABD driver from Toshiba
hxxp://support.toshiba.com/support/viewContentDetail?contentId=4001725
Hope there will some more development for this device..
Finally rooted !!!
Hopelessly I tried the Motochopper and it WORKED !!!
My AT300SE is rooted.
You need:
a PC,
the motochopper http://forum.xda-developers.com/showthread.php?t=2228613
and
ADB driver http://support.toshiba.com/support/viewContentDetail?contentId=4001725
*edit*
Attention please: only for 4.1 JB (not 4.0.3 ICS)
tasos66 said:
Finally rooted !!!
Hopelessly I tried the Motochopper and it WORKED !!!
My AT300SE is rooted.
You need:
a PC,
the motochopper http://forum.xda-developers.com/showthread.php?t=2228613
and
ADB driver http://support.toshiba.com/support/viewContentDetail?contentId=4001725
Click to expand...
Click to collapse
Thank man for the update..
Did u try CWM or TWRP For recovery .To make stock backup
are you sure that it worked???
Doesn't seem to work on the Excite 10LE aka At200 :crying:
ftomas said:
are you sure that it worked???
Doesn't seem to work on the Excite 10LE aka At200 :crying:
Click to expand...
Click to collapse
For at300se it worked perfectly.
What exactly is the problem?
Did the pc recognized the device, as an adb connection?
tasos66 said:
For at300se it worked perfectly.
What exactly is the problem?
Did the pc recognized the device, as an adb connection?
Click to expand...
Click to collapse
I don't have the at200 here....
i didn't get any errors from the script, if i didn't have the correct drivers should have been an error on the script, no?
the script runs... and then i ask for enter to reboot.... the at200 reboots but no working SU
ftomas said:
I don't have the at200 here....
i didn't get any errors from the script, if i didn't have the correct drivers should have been an error on the script, no?
the script runs... and then i ask for enter to reboot.... the at200 reboots but no working SU
Click to expand...
Click to collapse
Sorry to hear that
there are several Motochopper versions out there, how many Mb is the zip file that you downloaded?
I downloaded four or five of them, maybe one of them will work for you.
tasos66 said:
Sorry to hear that
there are several Motochopper versions out there, how many Mb is the zip file that you downloaded?
I downloaded four or five of them, maybe one of them will work for you.
Click to expand...
Click to collapse
+/- 2mb
where can i find those files?
ftomas said:
+/- 2mb
where can i find those files?
Click to expand...
Click to collapse
I will send you the file I used and worked for at300se, later today (about 22:00 Greek time)
---------- Post added at 03:01 PM ---------- Previous post was at 02:13 PM ----------
ftomas said:
+/- 2mb
where can i find those files?
Click to expand...
Click to collapse
O.K. I found the link.
http://mirror21.downloadandroidrom.com/download/GalaxyS4/root/motochopper.zip?token=
Good Luck!
tasos66 said:
Finally rooted !!!
Hopelessly I tried the Motochopper and it WORKED !!!
My AT300SE is rooted.
You need:
a PC,
the motochopper http://forum.xda-developers.com/showthread.php?t=2228613
and
ADB driver http://support.toshiba.com/support/viewContentDetail?contentId=4001725
Click to expand...
Click to collapse
Did not work for me either. I own an AT300SE-101
Click for details here.
http://forum.xda-developers.com/showthread.php?p=42700267#post42700267
Worked fine.No problem for rooting device (at300se).......:good: After the root superSu got update and as well as binary.
Is any update on Recovery and stock ROM....
dashu42332 said:
Worked fine.No problem for rooting device (at300se).......:good: After the root superSu got update and as well as binary.
Is any update on Recovery and stock ROM....
Click to expand...
Click to collapse
I dont know whats the problem.... but dont work
ftomas said:
I dont know whats the problem.... but dont work
Click to expand...
Click to collapse
Disable antivirus software and firewall.
tasos66 said:
Disable antivirus software and firewall.
Click to expand...
Click to collapse
Hummm, did you see the photo i post?
ADB seems to be working... or not? the push command seem to be successful... its fails when installing superuser.apk?
Other thing... this is part of the the run.bat with some notes in front, because i don't know linux can you see if the notes are right?:
adb push pwn /data/local/tmp/ - send the pwn (exploit) to the tablet
adb shell chmod 755 /data/local/tmp/pwn - change pwn permissions
echo [*] Pushing root tools...
adb push su /data/local/tmp/ - send SU to the tablet
adb push busybox /data/local/tmp/ send busybox to the tablet
adb install Superuser.apk - install superuser on the tablet (where scrip seem to give the error)
echo [*] Rooting phone...
adb shell /data/local/tmp/pwn - WHATS THIS COMMAND DOES?
echo [*] Cleaning up...
adb shell rm /data/local/tmp/pwn - delete pwn
adb shell rm /data/local/tmp/su - delete SU
adb shell rm /data/local/tmp/busybox - delete busybox
echo [*] Exploit complete
ftomas said:
Hummm, did you see the photo i post?
ADB seems to be working... or not? the push command seem to be successful... its fails when installing superuser.apk?
Other thing... this is part of the the run.bat with some notes in front, because i don't know linux can you see if the notes are right?:
adb push pwn /data/local/tmp/ - send the pwn (exploit) to the tablet
adb shell chmod 755 /data/local/tmp/pwn - change pwn permissions
echo [*] Pushing root tools...
adb push su /data/local/tmp/ - send SU to the tablet
adb push busybox /data/local/tmp/ send busybox to the tablet
adb install Superuser.apk - install superuser on the tablet (where scrip seem to give the error)
echo [*] Rooting phone...
adb shell /data/local/tmp/pwn - WHATS THIS COMMAND DOES?
echo [*] Cleaning up...
adb shell rm /data/local/tmp/pwn - delete pwn
adb shell rm /data/local/tmp/su - delete SU
adb shell rm /data/local/tmp/busybox - delete busybox
echo [*] Exploit complete
Click to expand...
Click to collapse
It looks like the adb driver works fine but I am afraid your tablet can not be rooted by this method .
I am IT engineer and manager but not Android developer so I cannot help you any furthermore.
Maybe this is a good reason for a tablet upgrade
Good luck!
regards
Tasos
Please check your Android version in your tab. Because above steps will work only for Android version 4.1 or above. ....
dashu42332 said:
Please check your Android version in your tab. Because above steps will work only for Android version 4.1 or above. ....
Click to expand...
Click to collapse
hum......
I only have ICS 4.0.3
Hello,
Veteran SW guy here; but newbie at Android.
I have three tablets. All of them are Ematic Model EGS004. All three were bought for the sole purpose of being used by children to watch educational videos (in mp4 and flv formats) and read PDF documents. Absolutely nothing else. No games. No internet access whatsoever. Etc.
Two of the tablets are still in the box and have not been touched. I'm hoping that they may be useful for making/restoring an original image of the tablets.
To implement the requirements of this project, I did the following to one of the tablets:
1) Used the instructions at http://forum.xda-developers.com/showthread.php?t=2495069 to get root access with Cydia Impactor and Chainfire SuperSU.
2) Installed Titanium Backup (root). Using this, I uninstalled most of the Google applications (excluding Google Play), messager, YouTube, games, etc.
3) Installed File Manager (Explorer) by Rhythm Software.
4) Installed Shell Terminal Emulator by MobilDev. Using the shell, I went to the /system/lib directory and renamed libwifidisplay.so
and libwpa_client.so to libwifidisplay.disabled and libwpa_client.disabled.
Unfortunately, upon reboot, the tablet gets stuck in the bootup screen (with the ematic logo). Obviously, something about Android causes a hang if an expected kernel module is missing...
I tried using the shell in Cydia Impactor. But, the file system was read only. I tried:
mount -o rw,remount /system
But, I get an "Operation not permitted" since I am not root.
I downloaded the ADB bundle for windows at http://developer.android.com/sdk/index.html#download and successfully installed adb on my PC. I could get into a shell with the "adb shell" command. But, the /system/lib directory still is read only and I can't seem to remount it since I am not root.
I tried "adb remount". "Operation not permitted" was the result, again.
Cydia Impactor installs its "su" binary in /system/xbin. I tried running it from there using various invocations like "su -c mount -o rw,remount /system" Each time, the shell hung and I never got a shell prompt afterwards.
Questions:
1) Surely there's a way that I can get back in to rename these files now... I can "ls" them from the adb shell. I can pull them to my PC with adb pull. (adb put doesn't work either since the file system is read only.) Ideas?
2) Once I get this solved, what is the best way to get rid of the wireless capability so that children can never use it? I would like to move videos and PDF's between it and a PC strictly via USB.
3) Is there a way to image/restore one of the untouched tablets - or, for that matter, this one once its up and running like it needs to be?
Thanks everyone!
Jim
Let's try a simpler question since there have been no responses:
Once I get into a shell (non-root) using ADB or Cythia Impactor, I believe I can rename the files if I can only get SuperSU to work. However, when I invoke su, the shell hangs:
su -c ls
su
etc. All of these hang. I assume that SuperSU is waiting for a confirmation from the android display. But, since I'm stuck at the startup screen, there's never an opportunity. How can I get the shell to interact with me as root so that I can remount the file system as RW and rename files?
Thanks,
Jim
rivkah613 said:
Hello,
Veteran SW guy here; but newbie at Android.
I have three tablets. All of them are Ematic Model EGS004. All three were bought for the sole purpose of being used by children to watch educational videos (in mp4 and flv formats) and read PDF documents. Absolutely nothing else. No games. No internet access whatsoever. Etc.
Two of the tablets are still in the box and have not been touched. I'm hoping that they may be useful for making/restoring an original image of the tablets.
To implement the requirements of this project, I did the following to one of the tablets:
1) Used the instructions at http://forum.xda-developers.com/showthread.php?t=2495069 to get root access with Cydia Impactor and Chainfire SuperSU.
2) Installed Titanium Backup (root). Using this, I uninstalled most of the Google applications (excluding Google Play), messager, YouTube, games, etc.
3) Installed File Manager (Explorer) by Rhythm Software.
4) Installed Shell Terminal Emulator by MobilDev. Using the shell, I went to the /system/lib directory and renamed libwifidisplay.so
and libwpa_client.so to libwifidisplay.disabled and libwpa_client.disabled.
Unfortunately, upon reboot, the tablet gets stuck in the bootup screen (with the ematic logo). Obviously, something about Android causes a hang if an expected kernel module is missing...
I tried using the shell in Cydia Impactor. But, the file system was read only. I tried:
mount -o rw,remount /system
But, I get an "Operation not permitted" since I am not root.
I downloaded the ADB bundle for windows at http://developer.android.com/sdk/index.html#download and successfully installed adb on my PC. I could get into a shell with the "adb shell" command. But, the /system/lib directory still is read only and I can't seem to remount it since I am not root.
I tried "adb remount". "Operation not permitted" was the result, again.
Cydia Impactor installs its "su" binary in /system/xbin. I tried running it from there using various invocations like "su -c mount -o rw,remount /system" Each time, the shell hung and I never got a shell prompt afterwards.
Questions:
1) Surely there's a way that I can get back in to rename these files now... I can "ls" them from the adb shell. I can pull them to my PC with adb pull. (adb put doesn't work either since the file system is read only.) Ideas?
2) Once I get this solved, what is the best way to get rid of the wireless capability so that children can never use it? I would like to move videos and PDF's between it and a PC strictly via USB.
3) Is there a way to image/restore one of the untouched tablets - or, for that matter, this one once its up and running like it needs to be?
Thanks everyone!
Jim
Click to expand...
Click to collapse
Erratic Ematic
rivkah613 said:
Let's try a simpler question since there have been no responses:
Once I get into a shell (non-root) using ADB or Cythia Impactor, I believe I can rename the files if I can only get SuperSU to work. However, when I invoke su, the shell hangs:
su -c ls
su
etc. All of these hang. I assume that SuperSU is waiting for a confirmation from the android display. But, since I'm stuck at the startup screen, there's never an opportunity. How can I get the shell to interact with me as root so that I can remount the file system as RW and rename files?
Thanks,
Jim
Click to expand...
Click to collapse
I rooted my son's EGS004, installed busybox, and played around with it without any apparent problem. When I rebooted it, I was prompted to set up the device then and every subsequent time I rebooted it. I could not install any apps and could not redo the Cydia Impactor rooting procedure. The reason was that /data was reporting itself as 0.00B in size. Factory reset didn't change anything. Ematic wants me to return it.
Your issue sounds different, but it could be something as simple as the device being very unforgiving. There's a pinhole with a reset button (never worked for me but tech support suggested it) which may help.