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.
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.
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 have large, non-graphical application that I want to run on my N9. I have successfully built the application using ndk-build, and I can 'adb push' the binary to the N9. However, with 'adb shell' I am unable to figure out the magic incantation to make the binary executable and run it.
My N9 is unlocked, and has the chainfire superSU; and I installed SElinuxModeChanger, but I have been beating my head against the N9 all day: "./foo: no permission".
Any suggestions?
-- unused0
Found it...
Ah, found it...
http: //kevinboone.net/ android_native.html
Thanks,
Charles
Hello!
I have an iPhone (6S Plus) clone with a MT6735P
but I can't root it. I tried many tools.
KingRoot, Kingo Root, iRoot and a chinese tool --> This chinese tool shows me root, I click on it, it stops at 15% and then gives me a message with one button (for retry the root I suppose) and sometimes an other message with two buttons.
USB Debugging is enabled, the drivers are correctly installed..
I tried the root with ADB (with this -> http://forum.xda-developers.com/showthread.php?t=2684210) but it doesn't work because when I type "adb devices", nothing appear in "List of devices attached".
EDIT : I tried UsbDriverTool and adb shows "offline device"... What should I do?
EDIT 2 : Resolved thanks to Wondershare Mobile GO. But when I try to root it with adb, it says :
adb push su /data/local/tmp
cannot stat 'su': No such file or directory
adb push busybox /data/local/tmp
cannot stat 'busybox': No such file or directory
adb push Superuser.apk /data/local/tmp
cannot stat 'Superuser.apk': No such file or directory
EDIT 3 : Resolved too. Idk how.
.
I have an issue with the rear camera. It's blurry in the center and distorted but when I put something in front of it, it focus verry well... There's no dust or scratches...
Thank you.