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.
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.
Okay... So Here Is Whats Up... The Digitizer On My Lg Optimus L9 Is Broken, Cant Touch The Screen Or Anything... But I Would Still Like To Use My Phone, I Can Can View My Screen But Thats All I Can Do,I Wish To Use The Keyboard And Mouse To Control My Screen,I Know This Is Possible Apperantly The Only Way To Do This Is To Access The ADB Shell, Okay,But What The Problem? Well When I Attempt To Gain Access To The ADB Shell... Super SU Gets In The Way, I Cant Grant Access To The ADB Shell Because I Cant Touch The Screen Do To The Broken Digitizer, And I Cant Click It When It Appears On The Display Because I Dont Have Super SU Permision To Use The Controlls Do To Being Denied Access Of The ADB Shell, If You Under Stand My Cicumstances Please Assist Me In Any Way, The Only Stipulation, No Factory Reset! Please And Thank You!
savagemessiah97 said:
Okay... So Here Is Whats Up... The Digitizer On My Lg Optimus L9 Is Broken, Cant Touch The Screen Or Anything... But I Would Still Like To Use My Phone, I Can Can View My Screen But Thats All I Can Do,I Wish To Use The Keyboard And Mouse To Control My Screen,I Know This Is Possible Apperantly The Only Way To Do This Is To Access The ADB Shell, Okay,But What The Problem? Well When I Attempt To Gain Access To The ADB Shell... Super SU Gets In The Way, I Cant Grant Access To The ADB Shell Because I Cant Touch The Screen Do To The Broken Digitizer, And I Cant Click It When It Appears On The Display Because I Dont Have Super SU Permision To Use The Controlls Do To Being Denied Access Of The ADB Shell, If You Under Stand My Cicumstances Please Assist Me In Any Way, The Only Stipulation, No Factory Reset! Please And Thank You!
Click to expand...
Click to collapse
You should still be able to access adb shell at the shell level, what is likely happening is that you are dropping into a root shell and this is causing SuperSU to prompt if you want to allow adb shell to have root access. What are the exact steps you are taking when you go to use adb shell?
shimp208 said:
You should still be able to access adb shell at the shell level, what is likely happening is that you are dropping into a root shell and this is causing SuperSU to prompt if you want to allow adb shell to have root access. What are the exact steps you are taking when you go to use adb shell?
Click to expand...
Click to collapse
I Use Android Screencast Plus Android SDK, Then I Use Command Prompt
.Adb Shell
.Su
At That Point Super Su Is Prompted
savagemessiah97 said:
I Use Android Screencast Plus Android SDK, Then I Use Command Prompt
.Adb Shell
.Su
At That Point Super Su Is Prompted
Click to expand...
Click to collapse
I would recommend try starting adb shell (adb shell command) and not dropping into a root shell then skip the su command. So just do
Code:
adb shell
To start adb shell, and then skip the su command.
shimp208 said:
I would recommend try starting adb shell (adb shell command) and not dropping into a root shell then skip the su command. So just do
Code:
adb shell
To start adb shell, and then skip the su command.
Click to expand...
Click to collapse
If I Skip su The cmd Says Not Permited
Code:
•adb shell
•su
•chmod 777 /data/dalvik-cache
•cd /data/dalvik-cache
•chmod 777 ./
This Is My Attempt, Is There An Alternative
savagemessiah97 said:
If I Skip su The cmd Says Not Permited
Code:
•adb shell
•su
•chmod 777 /data/dalvik-cache
•cd /data/dalvik-cache
•chmod 777 ./
This Is My Attempt, Is There An Alternative
Click to expand...
Click to collapse
Trying using adb shell from the command line, instead of Android Screencast. Also what are you trying to do with the device extract your personnel information?
Any progress with this? I'm in the same situation
Hi~
I have been trying to gain root privileges on the Samsung Note4 stock recovery mode.
I want to do several things to adb commands. But I can not gain root permission.
e.g, adb shell mount ...
I had to enter the adb shell su command, confirmed that normally are handled.
But when I enter a command that requires root privileges, permission denied message was output.
Is there any other way in the recovery mode to obtain root privileges?
I'll wait for answers.