I rooted my device with Z4Root
activated debug mode
correctly connected the device to my pc...
but when I type the command adb remount, this is the error reported:
remount failed: operation not permitted
Any way to fix it?
Thanks in advance to all!
You have to use su command for become a root user
Yes, I knew
Anyway, PROBLEM SOLVED, I just went over that step and all went fine...
Solved.
Closing this one...
Related
hey guys i'm having problem in adb when i put the remount command
it gives this message : opreation remount not prometted
why is that??? i'm rooted on ba023 and a lot of programs that use su is working correctly
h.boushi1987 said:
hey guys i'm having problem in adb when i put the remount command
it gives this message : opreation remount not prometted
why is that??? i'm rooted on ba023 and a lot of programs that use su is working correctly
Click to expand...
Click to collapse
Try typing 'su' (without inverted commas) before that command, when using your phone, and on a PC, do 'adb shell su' or 'adb shell' then 'su'. The command should now work.
You have to do this, if you followed the 'secure root' instructions before.
thanks man it works!!!!!
Sent from my X10i using the XDA mobile application powered by Tapatalk
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.
So I don't use adb push/install all that often but since I deleted mobile hotspot on my phone (I thought I had it frozen but apparently I didn't) I cannot upgrade my system.
I am rooted, and have tried installing from an emulator on the phone (and shell) as well as installing from and adb on the PC.
When I try to adb remount I get the following error:
remount failed: Operation not permitted
I have re-rooted thinking that an early version of root wasn't rooted for adb and also hoping that would let me install via shell. How can I get Mobile Hotspot back on?
Ok, so I was able to run a mount from terminal and copy the files and get the upgrade to go through.
So does anyone know why adb remount doesn't work? Is it because of the Moto Blur?
Hello.
I'm trying to install adb on my tablet so that I might issue adb/fastboot commands to my Android phone.I downloaded this file which is a zip of the platform-tools directory. I put it on my internal memory' but I also tried it from /data/. The problem is that when I enter that directory and enter "adb" I get a permission denied error. OK, so I enter a root shell and try again, only to get a not found error. "./adb" also returns a permission error even from a root shell.
Anyone have any ideas?
You are trying to run an Intel binary on an ARM processor.
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.