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.
Related
ok so on most roms this happens. i need a SU request but my phone freezes obn a black screen and on the top in gray it says SU request. i wait paciently and maybe 1-2 mins later is asks to FC because its not responding. is there a fix or what am i doing wrong. usb debugging is on and so is install nonmarket apps idk wtf im doing wrong or if somthing is just not working. any input??
I've heard su is not working properly until you activate it once via adb. In your teriminal (cmd or similar)
Code:
adb shell
$su
You should get a working super user request after which all other su requests should work fine.
Marisa said:
I've heard su is not working properly until you activate it once via adb. In your teriminal (cmd or similar)
Code:
adb shell
$su
You should get a working super user request after which all other su requests should work fine.
Click to expand...
Click to collapse
yes same thing happens to me
plug in your phone
goto your android sdk tools
and input adb shell
now go back to your phone and try it while still plugged
thats what i have been doing...
the same thing is happening for me and the instructions of simply input adb shell into terminal arent helping really. if someone could tell me exactly where to be aiming the command prompt and what the exact commands are in order to fix this I would greatly appreciate it.
WalkingTaco said:
the same thing is happening for me and the instructions of simply input adb shell into terminal arent helping really. if someone could tell me exactly where to be aiming the command prompt and what the exact commands are in order to fix this I would greatly appreciate it.
Click to expand...
Click to collapse
Are you getting the same crshes and things, but when you do the adb shell # pops up instead of $?
whenever i do adb shell I get #, so that means SU is already activated, but it's actually not on my phone, so i have no idea what's going on and no one seems to know how to fix it.
no. my Su permissions always force close after a minute of black screen. there is a fix posted above but my nerd level is not high enough to.infer the rest
Sent from my Eris using the XDA mobile application powered by Tapatalk
I don't know the exact command prompt setup, I'm running linux. However, when you originally rooted your phone you used the Android SDK correct?
With your phone plugged in, and USB Debugging enabled on your phone (Settings -> Applications -> Development -> USB Debugging) Open command prompt and get to the tools directory you used during rooting, I don't know where you installed it, so I cannot guide you through that part. If you used Ivan's guide http://forum.xda-developers.com/showthread.php?t=647707 it's probably best to refresh yourself there.
Once you've found your SDK /tools/ in command prompt, it should be as easy as running the code I mentioned earlier
Code:
adb shell
$su
in the command prompt.
The superuser prompt should show up on your phone, tell it to allow it and it should work without fail until you flash a new ROM that has the bug.
thanks very much. I used Ivans guide. I rooted it yesterday when o got my replacement from Verizon in store. I had been using the 2.1 leak on my old one and complained in store for thirty seconds. they didn't even look at it gave me a replacement in ten minutes
Sent from my Eris using the XDA mobile application powered by Tapatalk
Rock out thanks for the Super Help
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.
Has anyone had a successful root on a plt7602g. I have tried a couple different methods.
Rooting the PLT7602G
sallanm said:
Has anyone had a successful root on a plt7602g. I have tried a couple different methods.
Click to expand...
Click to collapse
Here is a procedure to root the Curtis Proscan PLT7602G tablet (Build number PLT7602G-ANDROID4.2.2-v1.0.0).
1. Install adb on your computer and enable adb on the tablet. http://developer.android.com/tools/help/adb.html
2. Enable ADB on the tablet:
Settings > About Tablet > tap build number 7 times until it says "You are now a developer!"
Developer options > switch On > OK
Check "USB Debugging" > OK
3. Connect USB and wait for ADB drivers to load on the PC. Using the Google drivers installed with ADB, your system may need manual help to find the right drivers: Go into Windows device manager > Update Driver Software > browse My Computer for driver software > 'Let me pick from a list of devices drivers...' > Pick Android ADB Interface from the model list.
4. You will see a notification "USB Debugging Connected" on the tablet.
5. If this is the first time, you will next see a dialog on the tablet asking "Allow USB debugging?" Check "Always allow from this computer" and click OK.
6. At the command prompt on the computer enter "adb devices". You should see the device listed. If not, reboot the PC and repeat steps 1 through 5 as necessary to get everything working together.
C:\Users\entropy>adb devices
List of devices attached
CD1LBROR50 device
C:\Users\entropy>7. Download pwn.zip here: http://forum.xda-developers.com/showpost.php?p=53407127
8. Unzip "pwn" from the zip file to your windows current directory
9. At the command prompt on the computer enter the following sequence of commands:
C:\Users\entropy> adb push pwn /data/local/tmp/pwn
C:\Users\entropy> adb shell chmod 755 /data/local/tmp/pwn
C:\Users\entropy> adb shell /data/local/tmp/pwn
Beaups and jcase were here
donations may go here, pleaes say what it was for -> [email protected]
10. After a few seconds, you should hear the USB disconnect sound, followed by the USB connection sound again.
11. At the command prompt, enter “adb devices” and ensure the device is listed as before. If not, wait a few seconds and then repeat this step.
C:\Users\entropy> adb devices
12. At the command prompt, enter:
C:\Users\entropy> adb shell
7. At the shell prompt, enter "su". You should now have a root prompt.
[email protected]:/ $ su
[email protected]:/ #
8. Exit back out to the command prompt:
[email protected]:/ # exit
[email protected]:/ $ exit
C:\Users\entropy>
9. On the tablet, go to the play store, download and install the latest SuperSU, or use the Google Play link in this thread: http://forum.xda-developers.com/show....php?t=1538053
10. Open the SuperSU that you just installed. SuperSU will prompt you to install a newer su binary when you run it, so click “Continue” do that, then “Normal”, then “OK”.
11. Reboot the tablet.
The tablet should now be fully rooted. Please let me know if you find any errors or if anything is unclear. I hope you find this useful!
I've downloaded the "Unrevoked" USB driver but the device is not being installed...
Marco Dufal said:
I've downloaded the "Unrevoked" USB driver but the device is not being installed...
Click to expand...
Click to collapse
It has been a while since I got this working and I honestly don't remember exactly what I did to make it work.
Try this... install the official Google driver and reboot:
http://developer.android.com/sdk/win-usb.html
If i still doesn't work, download the adb_usb.ini from here and replace the adb_usb.ini in c:\users\<yourusername>\.android\adb_usb.ini with this one, then reboot and try again. I verified that this adb_usb.ini contains the necessary device ID, so that should definitely do the trick.
https://github.com/apkudo/adbusbini
If you get it working, please post here so others can benefit.
Sice I had already installed the official Google drivers I proceeded with the adb_usb.ini method, but even after rebooting my pc it didn't work... What worked for me was:
Going into window device manager -> Update Driver Software -> browse my computer for driver software -> 'let me pick from a list of devices drivers...' -> Picked Android ADB Interface (from the model list).
I don't get why it did't install it automatically since the driver is actually compatible; did the same thing with another device (Sony experia E1). I got two of them, the first one got recognized while I had to do this process for the second one... Maybe it's my pc fault..
Anyway thank you very much for your replies and the guide. Am I risking to brick the device by following it ?
P.S.
For those who have android studio installed, to run the guide prompt commands you can set an environment variable called 'adb' with this value 'C:\Users\{USERNAME}\AppData\Local\Android\sdk\platform-tools\adb.exe' and easily replacing 'adb' with '%adb%' .
For example : 'C:\Users\{any directory}>%adb% devices'
Marco Dufal said:
Sice I had already installed the official Google drivers I proceeded with the adb_usb.ini method, but even after rebooting my pc it didn't work... What worked for me was:
Going into window device manager -> Update Driver Software -> browse my computer for driver software -> 'let me pick from a list of devices drivers...' -> Picked Android ADB Interface (from the model list).
I don't get why it did't install it automatically since the driver is actually compatible; did the same thing with another device (Sony experia E1). I got two of them, the first one got recognized while I had to do this process for the second one... Maybe it's my pc fault..
Anyway thank you very much for your replies and the guide. Am I risking to brick the device by following it ?
P.S.
For those who have android studio installed, to run the guide prompt commands you can set an environment variable called 'adb' with this value 'C:\Users\{USERNAME}\AppData\Local\Android\sdk\platform-tools\adb.exe' and easily replacing 'adb' with '%adb%' .
For example : 'C:\Users\{any directory}>%adb% devices'
Click to expand...
Click to collapse
I'm glad you got ADB working. Thanks for the additional tips, I'm sure they will be useful to others.
I don't think there is any significant risk of bricking unless you make a horrible mistake, like deleting everything in /system instead of shifting the new file into place. Anything else, like accidentally picking the wrong su binary to install, should be easily recoverable by just rebooting if necessary and then trying again.
maximumentropy said:
I'm glad you got ADB working. Thanks for the additional tips, I'm sure they will be useful to others.
I don't think there is any significant risk of bricking unless you make a horrible mistake, like deleting everything in /system instead of shifting the new file into place. Anything else, like accidentally picking the wrong su binary to install, should be easily recoverable by just rebooting if necessary and then trying again.
Click to expand...
Click to collapse
Quick info. I am rooting because of the low storage. Currently this is my storage situation :
total 4GB
Firmware 2.04GB
---------------------
Total space 1.96GB
197MB Available
232MB Apps
few KB Cached data & Misc.
There must be something wrong... Anyway my question is. Should I flash a custom rom to free some of the firmware allocated memory ? How is the external card going to be used (can I install app on it) ?
EDIT
I get
`su: not found`
Marco Dufal said:
Quick info. I am rooting because of the low storage. Currently this is my storage situation :
total 4GB
Firmware 2.04GB
---------------------
Total space 1.96GB
197MB Available
232MB Apps
few KB Cached data & Misc.
There must be something wrong... Anyway my question is. Should I flash a custom rom to free some of the firmware allocated memory ? How is the external card going to be used (can I install app on it) ?
Click to expand...
Click to collapse
I haven't found any custom ROMs for this tablet. If you know of some, please speak up. You could try reflashing the original ROM but that might be overkill. You can use an app like DiskUsage to help you identify what's eating the most space.
Marco Dufal said:
EDIT
I get
`su: not found`
Click to expand...
Click to collapse
I can't help you if you give me an error message but no hint of what you entered that caused the message.
maximumentropy said:
I haven't found any custom ROMs for this tablet. If you know of some, please speak up. You could try reflashing the original ROM but that might be overkill. You can use an app like DiskUsage to help you identify what's eating the most space.
Click to expand...
Click to collapse
Thanks I will check it up.
maximumentropy said:
I can't help you if you give me an error message but no hint of what you entered that caused the message.
Click to expand...
Click to collapse
C:\Users\Marco\AppData\Local\Android\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
Marco Dufal said:
Thanks I will check it up.
C:\Users\Marco\AppData\Local\Android\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
Click to expand...
Click to collapse
Please try entering it with full path:
[email protected]:/ $ /system/xbin/su
maximumentropy said:
Please try entering it with full path:
[email protected]:/ $ /system/xbin/su
Click to expand...
Click to collapse
Still negative result :
[email protected]:/ $ /system/xbin/su
/system/xbin/su
/system/bin/sh: /system/xbin/su: not found
127|[email protected]:/ $ ls /system/xbin/
ls /system/xbin/
dexdump
io
[email protected]:/ $
Marco Dufal said:
Still negative result :
Click to expand...
Click to collapse
What is your build number in Settings > About Tablet?
maximumentropy said:
What is your build number in Settings > About Tablet?
Click to expand...
Click to collapse
PLT7602G-ANDROID4.2.2-v1.0.0
Marco Dufal said:
PLT7602G-ANDROID4.2.2-v1.0.0
Click to expand...
Click to collapse
Well, I apologize for being an idiot. That's what I get for trying to document a root procedure I did last year, from memory. I have several similar cheap tablets and I misremembered this one as being pre-rooted as I described.
I just re-flashed from stock and re-rooted it. Fortunately, I had left enough breadcrumbs on my computer that I was able to reconstruct the right procedure.
I will do another full run-through within the next few days as soon as I have some time, to make sure I have everything 100% straight, and will clean this up to update the OP. Meanwhile, if you're feeling brave, here's the notes I took as I did it:
Settings > About Tablet > tap build number until it says you are a developer
Developer options > switch On > OK
USB Debugging > OK
Connect USB
see "USB Debugging Connected" notification
Wait for "Allow USB debugging?" dialog, check "Always allow from this computer" and click OK
adb devices
Download pwn.zip here: http://forum.xda-developers.com/showpost.php?p=53407127
Unzip "pwn" from the zip file to your windows current directory
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
Hear USB disconnect sound
Wait about 1 minute (may or may not need to disconnect and reconnect USB cable)
adb wait-for-device
adb shell
su (should give a root shell)
exit
Install SuperSU from Play Store
Run it
The SU binary needs to be updated. Continue?
Continue > Normal > OK
Reboot
Don't worry it's ok.. Anyway I am not felling brave at all so I think that I will wait for now...
Marco Dufal said:
Don't worry it's ok.. Anyway I am not felling brave at all so I think that I will wait for now...
Click to expand...
Click to collapse
No guts, no glory!
I updated the instructions in post #2 and did another trial run through. Give it a shot at let me know if you run into any trouble. You already have ADB functioning, so you can just skip to step 6 and go from there.
http://forum.xda-developers.com/showpost.php?p=59530490&postcount=2
maximumentropy said:
No guts, no glory!
Click to expand...
Click to collapse
Just did it and every thing worked ! It was fast and clear... Now I wonder, how many devices can I root with the same procedure ?
Marco Dufal said:
Just did it and every thing worked ! It was fast and clear... Now I wonder, how many devices can I root with the same procedure ?
Click to expand...
Click to collapse
Great, I'm glad it worked for you!
The pwn exploit will work with many JellyBean devices. Many of the cheap Chinese tablets don't even need it though, as they will either give you a root prompt immediately when you connect using ADB, or after entering "su" to ADB. The trick then is just to use that access to install an "su" from SuperSU or another full SU package, so that you get full root from the user interface as well as from ADB. You could still use the pwn method on such a device, but I personally prefer to use the least invasive method to get the required access.
maximumentropy said:
Great, I'm glad it worked for you!
The pwn exploit will work with many JellyBean devices. Many of the cheap Chinese tablets don't even need it though, as they will either give you a root prompt immediately when you connect using ADB, or after entering "su" to ADB. The trick then is just to use that access to install an "su" from SuperSU or another full SU package, so that you get full root from the user interface as well as from ADB. You could still use the pwn method on such a device, but I personally prefer to use the least invasive method to get the required access.
Click to expand...
Click to collapse
Sorry if this is a newb question but can this be done if your microusb port is broken? I can get the file on the tablet via sd card but I can't seem to perform the steps with Terminal Emulator like I had hoped. This is using the same ProScan PLT7602G as in the OP.
Thanks
Ian1331 said:
Sorry if this is a newb question but can this be done if your microusb port is broken? I can get the file on the tablet via sd card but I can't seem to perform the steps with Terminal Emulator like I had hoped. This is using the same ProScan PLT7602G as in the OP.
Thanks
Click to expand...
Click to collapse
I don't think it will work in a terminal emulator because you need to run with uid 2000 (shell) for permission on the /data/local/tmp directory.
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
I'm really enjoying remix OS, So much so, I seldom use my windows partition at all any more except for one thing. Bootloader updates and firmware installations on my various android devices. (Most Nexus Player android TV boxes)
Remix shipped with adb support and I have been using it to push bulk installs onto my own and customer devices, I would like to perform the firmware updates as well and found remix does not ship with fastboot installed in system/bin. There is a fastboot file but it is for the Intel 915 graphics support libs.
Is there a way I can add it? been looking at a few pre compiled bin packages for linux but can't seem to get any of them to work correctly. can't seem to get the fastboot.bin to be executable.. even with root.
Any help would be appreciated. Asked the remix folks as I am on the beta program but have not gotten an answer.
Thanks!
MrJinx123 said:
I'm really enjoying remix OS, So much so, I seldom use my windows partition at all any more except for one thing. Bootloader updates and firmware installations on my various android devices. (Most Nexus Player android TV boxes)
Remix shipped with adb support and I have been using it to push bulk installs onto my own and customer devices, I would like to perform the firmware updates as well and found remix does not ship with fastboot installed in system/bin. There is a fastboot file but it is for the Intel 915 graphics support libs.
Is there a way I can add it? been looking at a few pre compiled bin packages for linux but can't seem to get any of them to work correctly. can't seem to get the fastboot.bin to be executable.. even with root.
Any help would be appreciated. Asked the remix folks as I am on the beta program but have not gotten an answer.
Thanks!
Click to expand...
Click to collapse
Try the one here: it's seems to show the help page fine. Haven't checked any of the command though;
alternatively you could compile a version from source
Thanks for the lead
Looking around thru XDA , I found a few fastboot packages that should have worked. My device filesystem is RW and root is obviously present. I copy the file and chmod it as executable but still get access denied trying to execute it as root, Most the versions I found expect you to adb copy it into the device, With remix OS, I'm not sure how to to do that since there is no OTG port. If the filesystem is RW, Should I need to use adb to copy the file in? Looking at compiling a copy since the remix install I'm using is x64 on intel and maybe the fastboot executable needs to be for this specific target?
MrJinx123 said:
Looking around thru XDA , I found a few fastboot packages that should have worked. My device filesystem is RW and root is obviously present. I copy the file and chmod it as executable but still get access denied trying to execute it as root, Most the versions I found expect you to adb copy it into the device, With remix OS, I'm not sure how to to do that since there is no OTG port. If the filesystem is RW, Should I need to use adb to copy the file in? Looking at compiling a copy since the remix install I'm using is x64 on intel and maybe the fastboot executable needs to be for this specific target?
Click to expand...
Click to collapse
Definately at least executes for me; will check tomorrow if it can detect a fastboot device. One from @osm0sis : http://forum.xda-developers.com/showthread.php?t=2239421 also seems to run fine and I think its a different one; some of the others posted are a copy of that first one I posted without giving credit.
Looks like you did point me to the right one.
Since remix OS on a laptop doesn't support an OTG adb transfer... I manually copied adb, adb.bin and fast boot to the system/xbin directory as root.
Then used
chown 0:0 on all 3 files, As found in the included install script (adb shell script)
then chmod +755 (all 3 files) also tried chmod +777
No errors or complaints from the command line..
attempt to execute as user or root, Get permission denied..
"ls" the file shows -rwxrwxrwx root root ?
When I compare against other files in xbin, they all have lrwxrwxrwx. I'm assuming the "l" is a symbolic link pointing to the busybox install.
Am I missing something? that is preventing fastboot from being executable? I don't claim to be a linux expert in any way...
MrJinx123 said:
Since remix OS on a laptop doesn't support an OTG adb transfer... I manually copied adb, adb.bin and fast boot to the system/xbin directory as root.
Then used
chown 0:0 on all 3 files, As found in the included install script (adb shell script)
then chmod +755 (all 3 files) also tried chmod +777
No errors or complaints from the command line..
attempt to execute as user or root, Get permission denied..
"ls" the file shows -rwxrwxrwx root root ?
When I compare against other files in xbin, they all have lrwxrwxrwx. I'm assuming the "l" is a symbolic link pointing to the busybox install.
Am I missing something? that is preventing fastboot from being executable? I don't claim to be a linux expert in any way...
Click to expand...
Click to collapse
adb is already installed (/system/bin/adb); other than that I have it as 777 root:root as well, any chance you have forgotten to execute fastboot as root [su]?
Screenshot attached; and just checked if device detected in fastboot and it is.
NB with adb you might have to use adb -s 0123456789ABCDEF reboot bootloader for example as theres an emulator device running on RemixOS.