SuperSU works fine and grants permission to Root Explorer which also works fine.
But 'getprop: permission denied' is shown in front of most of the headings in 'Phone information' tab in MTK Droid Tools.
And when I click 'Root' button in MTK Droid Tools the following message is shown 'ERROR: SU inaccessible'.
I have granted permission to ADB Shell in SuperSU.
If I manually open adb shell I get $ prompt and then I type su to get # prompt.
I think that maybe permissions of some files are not ok.
Please help!
threatalive said:
SuperSU works fine and grants permission to Root Explorer which also works fine.
But 'getprop: permission denied' is shown in front of most of the headings in 'Phone information' tab in MTK Droid Tools.
And when I click 'Root' button in MTK Droid Tools the following message is shown 'ERROR: SU inaccessible'.
I have granted permission to ADB Shell in SuperSU.
If I manually open adb shell I get $ prompt and then I type su to get # prompt.
I think that maybe permissions of some files are not ok.
Please help!
Click to expand...
Click to collapse
I know I am bumping this thread, but someone recently asked me the solution for this issue.
So, for anyone who might face the same problem: this error occurs due to broken symlinks of toolbox or busybox etc.
To fix it, you need to create the missing symlinks.
A simple solution is to re-root your mobile.
Related
I tried loading the Aria into an adb shell, then tried the reboot command (just "reboot"). It replies "reboot: no such tool".
I also wrote a quick script with GScript and ran it with su permissions (my phone is rooted with clockworkmod, and liberated), and the same message showed on screen.
I also made a separate script that just runs "ls /system/bin" and I can clearly see the "reboot" command in the directory. Again, when I try to run /system/bin/reboot with su priveleges, it gives the same message.
I'm tempted to think that the reboot command in /system/bin simply runs the command "echo reboot: no such tool". Does anyone have any more information about this? I'd like a script that would use the reboot command to reboot into recovery mode.
I believe you should be able to use "shutdown /r" to reboot the phone.. probably needs to be done with sudo though..
jleehey said:
I tried loading the Aria into an adb shell, then tried the reboot command (just "reboot"). It replies "reboot: no such tool".
I also wrote a quick script with GScript and ran it with su permissions (my phone is rooted with clockworkmod, and liberated), and the same message showed on screen.
I also made a separate script that just runs "ls /system/bin" and I can clearly see the "reboot" command in the directory. Again, when I try to run /system/bin/reboot with su priveleges, it gives the same message.
I'm tempted to think that the reboot command in /system/bin simply runs the command "echo reboot: no such tool". Does anyone have any more information about this? I'd like a script that would use the reboot command to reboot into recovery mode.
Click to expand...
Click to collapse
I can reboot the phone using ADB by typing adb reboot... Or in terminal on the phone itself I su and then enter reboot and voila...
Not sure if this helps or not.
Edit: I am also running CM6 which has busybox installed.
The way I do it from shell is to type 'exit', this takes you out of shell. Then I type 'adb reboot'
Your path is probably not correct on the device. To change the path you need to edit init.rc and add the correct path.
I have had this same problem and now think that the tool unrevoked is messing the path variable up.
Let me know what you discover.
Same
I also have the same problem. I checked init.rc and i didnt find something about reboot. I run S5 Sensenation ROM. I will check again, But i happy to see that im not the only one who have the problem.....
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 have a Motorola Droid X on Android 2.3.3.
Motorola One Click Root goes all the way through and says that the phone should be rooted, but it never is. Here is the alternate method I attempted:
First I used SuperOneClick 2.2 in "Shell Root" mode to get the superuser (#) prompt in adb shell. From there I was able to mount the /system folder for read/write access.
I then copied, "chmodded" and --installed busybox to /system/xbin/.
Next I copied su to /system/bin and changed its permissions to 0755.
Finally, I installed a Superuser.apk
I still get no superuser prompts when I run a root app or type "su" in adb.
What am I missing?
U need to reset your phone and try all over again
Try to wipe/erase the application data of your root app and/or Superuser app, and try again to see if Superuser prompt will popup.
Several days ago, I upgrade ROM of my phone, and restored data and applications, then rooted, but when I type 'su' in Terminal Emulator application, it will wait for a few seconds and failed with "permission denied" error. I use strace to try to figure out why, I noticed that the real UID (10083) of Terminal Emulator application is not as same as the one (10069) send to Superuser. So I wiped the application data and Superuser application data (in fact, I also reinstalled them), then Superuser will prompt when executing 'su' command.
Hey Guys, So I'll Start off By Saying That Im Still Pretty New to Android, and I May not Understand Whatever You Are Trying to Tell Me, So Guide Me along The Way Yeaaaa? Pardon My Noob-ness...
Anyway, So I Just Tried Editting My Systemui.apk File, So Now I'm Trying to Use ADB to Push it back to My Phone. So I Go to ADB and Type the ADB Command " ADB Push systemui.apk /system/app " And It Says Permission Denied...
- It Seems Like I Need to Grant ADB root Permissions, So How Do I That? Some su Command Right ? What Exactly Is It
- My Phone Is Rooted, and im Using Super SU
So, I wanna Ask, How do i bypass this permission denied thing? Help Would Be Appreciated
Sup
AW: [Q] ADB Permission Denied
Under developer options you have to grant superuser rights to adb. Under root access you have to choose adb and apps.
Then you should be able to type in terminal adb su. And then your command.
sent from a slim bean with max memory
Thank You For The Reply Haha
Anyways,There isnt Such An Option in My Super SU App, So Where is it Found?
Lol Okay... i got it working already... I Managed to Grant ADB superuser rights now. Thanks Haha:laugh:
Now Im In # After Typing su... However, When I Use ADB Push Command, Its Says ADB not found, So I Still Cant Use The Push Command.. How Do I Use It in # mode ?
Im using Lyf wind 7s LS5016 im try to root many times and many methods but no on cannot root my device and im try to install su binary using adb but it says permission denied and
antes de usa el comando adb root para dar root a tu ADB xD
any solution to similar problem for unrooted device?
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.