Develop Bugs

adb remount permission denied

I am getting a permission denied when I try to run "adb remount".
I am running the netarchy rooted ROM.
I am Unrevoked3 and Unrevoked Forever.
So my NAND is unlocked and I am rooted. Why does it still say Permission Denied?

Install the latest version of SuperUser (look in the Market). When you try to do adb remount, or su in adb shell, look at your phone. There'll be a popup asking for permission.

AzN1337c0d3r said:
I am getting a permission denied when I try to run "adb remount".
I am running the netarchy rooted ROM.
I am Unrevoked3 and Unrevoked Forever.
So my NAND is unlocked and I am rooted. Why does it still say Permission Denied?
Click to expand...
Click to collapse
In Netarchy's kernel thread he mentions something about unrevoked 3 not giving full access to root, not sure if he was just referring to the NAND or what but that may have something to do with it. If all else fails you can always go back and try rooting it manually without unrevoked.
just out of curiosity, what does your name mean? The last part looks like coder but what is azn 1337?

xHausx said:
In Netarchy's kernel thread he mentions something about unrevoked 3 not giving full access to root, not sure if he was just referring to the NAND or what but that may have something to do with it. If all else fails you can always go back and try rooting it manually without unrevoked.
just out of curiosity, what does your name mean? The last part looks like coder but what is azn 1337?
Click to expand...
Click to collapse
My leetspeak is a little rusty, but I think 1337 is 'leet' as in "elite"....and I'm guessing the young man is of Asian descent.

drmacinyasha said:
Install the latest version of SuperUser (look in the Market). When you try to do adb remount, or su in adb shell, look at your phone. There'll be a popup asking for permission.
Click to expand...
Click to collapse
Installed latest version of SuperUser.
"adb remount" still saying permission denied.
"adb shell su" did ask me for permission however.
xHausx said:
In Netarchy's kernel thread he mentions something about unrevoked 3 not giving full access to root, not sure if he was just referring to the NAND or what but that may have something to do with it. If all else fails you can always go back and try rooting it manually without unrevoked.
Click to expand...
Click to collapse
I thought Unrevoked Forever took care of the NAND not getting unlocked. It says on their website that it unlocks NAND.
Anyways, the whole reason why I went with unrevoked is because I could keep PRI 1.40_003. I had lost it when I manually rooted and had to go back to stock and then unrevoked to get it back.

I am having the same issues. I am unrevoked3 and unrevoked forever. It is always telling me either device not found or remote not allowed. As far as I can tell all of my drivers are up to date, I am fully rooted with nand unlocked, and the problem didn't start until just recently. Everything worked fine before. I will try to download an updated Superuser app and give some feedback on that when I get off work.
On a side note, does Busybox have anything to do with this sort of matter?
Sent from my regaw rooted EVO.

My problem appears to be a software/OS issue. When I wipe everything and install a stock 2.2 system, I am able to "adb remount".
My guess is that something is continually accessing the /system partition and holding a lock on it.
Does anyone know how I might check for this?

Just to clarify: yes, Unrevoked Forever does unlock NAND.
The issue must be with the rom? Try a different superuser/su...

AzN1337c0d3r said:
Installed latest version of SuperUser.
"adb remount" still saying permission denied.
"adb shell su" did ask me for permission however.
Click to expand...
Click to collapse
Mmmkay, your problem is either:
1) NAND is locked still (unlikely).
2) ROM is not set up to have shells be root by default (likely).
To test, open adb shell. If you see a $, then it's #2. If you see a #, then it's probably #1. To be extra sure, if you're seeing a $, type "su" then enter, approve the su request, then do "mount -o remount,rw /system", followed by "mkdir /system/testymctest". If you get a permission error, then your NAND is not unlocked.

drmacinyasha said:
Mmmkay, your problem is either:
1) NAND is locked still (unlikely).
2) ROM is not set up to have shells be root by default (likely).
To test, open adb shell. If you see a $, then it's #2. If you see a #, then it's probably #1. To be extra sure, if you're seeing a $, type "su" then enter, approve the su request, then do "mount -o remount,rw /system", followed by "mkdir /system/testymctest". If you get a permission error, then your NAND is not unlocked.
Click to expand...
Click to collapse
Thank you so much for the info. I have been searching high and low for a straight answer on this. Even though its not fixed I am much happier knowing what the issue is. Again thank you.
When I ran your test I got a $ which as you said means it is a conflict with my current ROM. So, if I flash a different ROM than I should be squared away yes? Again many thanks.
Sent from my regaw rooted EVO.

drmacinyasha said:
Mmmkay, your problem is either:
1) NAND is locked still (unlikely).
2) ROM is not set up to have shells be root by default (likely).
Click to expand...
Click to collapse
It says clearly SHIP S-OFF on my bootloader. This is the way to tell if you are Unrevoked Forever.
To test, open adb shell. If you see a $, then it's #2. If you see a #, then it's probably #1. To be extra sure, if you're seeing a $, type "su" then enter, approve the su request, then do "mount -o remount,rw /system", followed by "mkdir /system/testymctest". If you get a permission error, then your NAND is not unlocked.
Click to expand...
Click to collapse
Everything is as you described. It is #2. and when I do the "mount -o remount,rw /system" I get permission denied.
I'm not sure how Root Explorer works, but I assume it obtains root permissions and then run the mount command as you have described above.
My NAND is unlocked, I can get to it via Root Explorer and mount it as r/w and then access it through shell. However, if I don't use Root Explorer and try the command through the shell, it doesn't work.
It seems almost like I am not getting SU permissions even though my shell changes to a #.

AzN1337c0d3r said:
It says clearly SHIP S-OFF on my bootloader. This is the way to tell if you are Unrevoked Forever.
Everything is as you described. It is #2. and when I do the "mount -o remount,rw /system" I get permission denied.
I'm not sure how Root Explorer works, but I assume it obtains root permissions and then run the mount command as you have described above.
My NAND is unlocked, I can get to it via Root Explorer and mount it as r/w and then access it through shell. However, if I don't use Root Explorer and try the command through the shell, it doesn't work.
It seems almost like I am not getting SU permissions even though my shell changes to a #.
Click to expand...
Click to collapse
Hrm... Are you sure you have the latest version of ChrisDD's SuperUser from the Market, and then opened up its settings tab to make sure there's the latest su executable? That's the only thing I can think of.

drmacinyasha said:
Hrm... Are you sure you have the latest version of ChrisDD's SuperUser from the Market, and then opened up its settings tab to make sure there's the latest su executable? That's the only thing I can think of.
Click to expand...
Click to collapse
Yup I did exactly that.
It's some app I installed that is doing this. I nandroided my current config, reflashed the netarchy 2.2 rooted rom and was able to get access.
Then when I installed all the rest of my apps, I suddenly lost access.
Tommorow I will start fresh again and try apps one by one.

now i got # what else

Titanium Backup says "error could not acquire root", yet I "am" rooted???

Titanium Backup says "error could not acquire root", yet I "am" rooted???
Ok, so my v2.1 evo was rooted using Unrevoked 3.21, I install Titanium Backup this morning and when I launch it an error comes up that says "Sorry, I could not acquire root privileges. This application will not work. Please verify that your rom is rooted and includes busy box and try again."
Whats the deal wit this error? Unrevoked said it was succesful.

did you download busybox? when you open TB hit the problems? button. download busy box and try again.
you can also verify root by downloading terminal emulator and opening it. when its open type SU and hit enter. # means root. $ means no root.

Be weary. I used unrevoked3 for mac on a froyo Evo. I'm having some issues currently. Be careful before you proceed. You should download ROM manager as well. Once you download busybox perform your backup. A friend recommended Appbrain over Titanium Backup. Once your done with your back up, reboot into the bootloader and try to go into recovery to perform a nandroid backup. If you select recovery and it takes you to the htcevo 4g white screen and nothing happens, you're having the same issue as i am. I wouldn't recommend flashing any radios or roms yet. I'm working with some other members to try to figure this issue out. Apparently this is why other experts don't like unrevoked3.
There might be a missing pc36img or unrevoked forever might need to be install, but I don't want to lock my phone into root with unrevoked. From my understanding, if you use unrevoked forever, you wont be able to unroot.

jontorres said:
Ok, so my v2.1 evo was rooted using Unrevoked 3.21, I install Titanium Backup this morning and when I launch it an error comes up that says "Sorry, I could not acquire root privileges. This application will not work. Please verify that your rom is rooted and includes busy box and try again."
Whats the deal wit this error? Unrevoked said it was succesful.
Click to expand...
Click to collapse
[highlight]Mod Edit: If you have nothing useful to say, say nothing at all. The question in the correct section this time.[/highlight]

jontorres said:
Ok, so my v2.1 evo was rooted using Unrevoked 3.21, I install Titanium Backup this morning and when I launch it an error comes up that says "Sorry, I could not acquire root privileges. This application will not work. Please verify that your rom is rooted and includes busy box and try again."
Whats the deal wit this error? Unrevoked said it was succesful.
Click to expand...
Click to collapse
What about any other app requesting root? Like setCPU or ShootMe? I'd install one of those to confirm root. If it works then you might you need to reinstall TB if not well then root was not properly achieved.

TruSlide said:
did you download busybox? when you open TB hit the problems? button. download busy box and try again.
you can also verify root by downloading terminal emulator and opening it. when its open type SU and hit enter. # means root. $ means no root.
Click to expand...
Click to collapse
Thanks for the suggestions, will try those out and report back what happened.

Sporkman said:
take the time to read the info it tales you have to fix said issue
Click to expand...
Click to collapse
MOD PM'd, apparently you are following my threads now to post the same "ignorant" response, your sanction from the mod will follow, enjoy.
Everyone else, thanks for actually offering helpful suggestions.

TruSlide said:
did you download busybox? when you open TB hit the problems? button. download busy box and try again.
you can also verify root by downloading terminal emulator and opening it. when its open type SU and hit enter. # means root. $ means no root.
Click to expand...
Click to collapse
Ok, so I did update BusyBox, and now Titanium Backup doesnt show the error, also installed Terminal Emulator when you launch it the 1st line of text says"
$ export PATH=/data/local/bin:$PATH
$
On the 2nd line where the $ i typed SU and hit enter and it goes to the next line and displays # is this what its suppose to do?
Thanks

Ok, here is some things for you to try.
1. Make sure you are using the latest version of TB.
2. Make sure you hit Problems? and download Busybox 1.60 (whether or not the ROM you have is using 1.60 or not, do it anyhow.)
I assume you did those two based on what I read. So here is what else to try.
Upgrade Superuser to the latest version, then update the binary. Make sure Titanium backup is not blocked by going to Superuser and there should be a green circle next to TB, if it is red that means it is blocked. If it still doesn't work, remove it from Superuser and then have it ask for permissions again.
If STILL not working, take out your battery for around 10 seconds, plug it back in and try again. Lastly, uninstall and reinstall TB then do these steps all over again.
That is a bunch of stuff to try, see what happens and hope this helps

jontorres said:
Ok, so I did update BusyBox, and now Titanium Backup doesnt show the error, also installed Terminal Emulator when you launch it the 1st line of text says"
$ export PATH=/data/local/bin:$PATH
$
On the 2nd line where the $ i typed SU and hit enter and it goes to the next line and displays # is this what its suppose to do?
Thanks
Click to expand...
Click to collapse
That's exactly what it's supposed to do. $ is the prompt you get when you are a regular user. You get # when you are root.
If you type 'id' (without the quotes) now, you should get:
uid=0(root) gid=0(root)

ricsim78 said:
Upgrade Superuser to the latest version, then update the binary. Make sure
Click to expand...
Click to collapse
I launched Superuser, the one with the little niña guy, and it showed TB and the emulator both with green on the right side, but no idea how to "update" superuser, seeing as all appears to be ok should I still update it? If so, hoe would I do that? If not then I guess now my next step s finding the best 2.2 ROM that still keeps HTC Sense, any recommendations?

timdsmith72 said:
That's exactly what it's supposed to do. $ is the prompt you get when you are a regular user. You get # when you are root.
If you type 'id' (without the quotes) now, you should get:
uid=0(root) gid=0(root)
Click to expand...
Click to collapse
the prompt b4 I typed anything was $, after typing SU and enter it went to #

jontorres said:
the prompt b4 I typed anything was $, after typing SU and enter it went to #
Click to expand...
Click to collapse
Yep. That's what is supposed to happen. You are root when you have the # prompt.

Problem
I just flashed CM 7.1 stable version, i cant launched TB couldt aquire root privileges i read this post and typed SU in the terminal emulator and it came up with a $ sign. So that means im not rooted?
Any cure to get my phone rooted again but i want to keep CM 7.1 what should i do?

aks1081 said:
I just flashed CM 7.1 stable version, i cant launched TB couldt aquire root privileges i read this post and typed SU in the terminal emulator and it came up with a $ sign. So that means im not rooted?
Any cure to get my phone rooted again but i want to keep CM 7.1 what should i do?
Click to expand...
Click to collapse
Flash the super user zip from http://androidsu.com/superuser/
Should fix you up, not sure how you lost it, but this souls fix it nevertheless.

Gfree_Verify Not Working, Not Sure if Root Worked

I followed all the steps from the Wiki: (http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD).
Now the problem is when I go to verify the root. On the Wiki, where it says run "su' in computer ADB shell, I get access denied. When I run "./gfree_verify" in computer ADB shell, I get
Error: Could not open modem device; /dev/****
Error: Verify could not initialize device
But in my apps on the G2 I see an icon for superuser permissions. So did the root take or not?
Thanks for any help, new to Android.

Go in to terminal on your phone and type SU
After pressing enter if it says permissions denied, you have no root, if a Su message pops up click allow... that means you have root
Edit: I think you have no root

MacaronyMax said:
Go in to terminal on your phone and type SU
After pressing enter if it says permissions denied, you have no root, if a Su message pops up click allow... that means you have root
Edit: I think you have no root
Click to expand...
Click to collapse
After typing Su in the terminal on the phone, I get a message pop that says either allow or deny. I click allow and it gives me root permission.

Then it`s OK!
After reboot/or try again,open terminal emulator on your phone and type "su".
If you get a superuser prompt, you have root!
After "su" you should see a line with "#".

Ganii said:
Then it`s OK!
After reboot/or try again,open terminal emulator on your phone and type "su".
If you get a superuser prompt, you have root!
After "su" you should see a line with "#".
Click to expand...
Click to collapse
After a reboot (two actually) after I enter su into terminal I dont get the popup anymore asking allow or deny. I get "#." I actually went through the whole rooting Wiki steps again, to root the phone (just cause I wasn't sure if I was rooted). Same results, the gfree-verfiy doesnt work and neither does the "older" method. But I get "#" after entering su in terminal on G2.
I also installed Rom Manager, I clicked Flash ClockworkMod Recovery and then chose Backup Current ROM. It asked for superuser permissions and I allowed it. It rebooted the phone and went to a ClockworkMod Recovery screen where I selected reboot device. Does this mean I backed up my current Tmobile ROM?
Another question, is it okay to delete the files I had to push to /data/local to root? How would I delete them?
I want to really thank you guys for all the help.

boost3d23 said:
After a reboot (two actually) after I enter su into terminal I dont get the popup anymore asking allow or deny. I get "#." I actually went through the whole rooting Wiki steps again, to root the phone (just cause I wasn't sure if I was rooted). Same results, the gfree-verfiy doesnt work and neither does the "older" method. But I get "#" after entering su in terminal on G2.
I also installed Rom Manager, I clicked Flash ClockworkMod Recovery and then chose Backup Current ROM. It asked for superuser permissions and I allowed it. It rebooted the phone and went to a ClockworkMod Recovery screen where I selected reboot device. Does this mean I backed up my current Tmobile ROM?
Another question, is it okay to delete the files I had to push to /data/local to root? How would I delete them?
I want to really thank you guys for all the help.
Click to expand...
Click to collapse
# sign means your rooted or have su access.
Go under manage and restore backups in rom manager, you should have a copy of the rom you just backed up. Unless you renamed the back up its probably a date.
Its ok to delete the files you pushed to data/local use a file manager like root explorer.
Sent from my HTC Vision using XDA App

After a reboot (two actually) after I enter su into terminal I dont get the popup anymore asking allow or deny. I get "#." I actually went through the whole rooting Wiki steps again. Same results, the gfree-verfiy doesnt work and neither does the "older" method. But I get "#" after entering su in terminal on G2.
Click to expand...
Click to collapse
You get "#" then it`s right,the app don`t ask you again about allow or deny!
About gfree-verify,I don`t know.Maybe something wrong with Script
or you have done something wrong with the commands!
I also installed Rom Manager, I clicked Flash ClockworkMod Recovery and then chose Backup Current ROM. It asked for superuser permissions and I allowed it. It rebooted the phone and went to a ClockworkMod Recovery screen where I selected reboot device. Does this mean I backed up my current Tmobile ROM?
Click to expand...
Click to collapse
If you choose "Backup ROM" you phone boot into Recovery,then you have
to choose "backup/restore option to backup you current ROM.
Otherwise you don`t have a backup

Again thanks guys.
Now i downloaded Astro and ES file Managers but I cant find the files. Do I need specifically need root manager? Im guessing the ones I downloaded cant access root files.

boost3d23 said:
Again thanks guys.
Now i downloaded Astro and ES file Managers but I cant find the files. Do I need specifically need root manager? Im guessing the ones I downloaded cant access root files.
Click to expand...
Click to collapse
I use Root Explorer or SUFBS (Super User File Manager and Terminal).

boost3d23 said:
Now i downloaded Astro and ES file Managers but I cant find the files. Do I need specifically need root manager? Im guessing the ones I downloaded cant access root files.
Click to expand...
Click to collapse
You should really have posted up in the existing thread about gfree on this, or otherwise in the Q&A forum
But anyway, yes, those file managers don't handle root. Well, ES does have an option to do so, but it doesn't work on the Vision. So you'll need a root-capable file manager, as joemm said.
On the backup, that sounds a bit odd, but you'll know that it's doing a backup because it'll take a while. You'll get a different screen where it shows you it's backup up the main phone partitions, and even which file is being backed up. When it's done, make sure you copy this backup somewhere else, like your PC (i.e. so you don't just have a single copy, in case something happens to it - e.g. corrupt SD card).

Thanks to everyone who provided insight. I had the same problem and was worried about bricking my phone, but this worked and I'm happily rooted!

[Q] su permission denied

Hello there,
I just flashed a new ROM (Gingerbread 2.3.7) last night. After signing in the Google account everything is great; the old apps got redownloaded and all. I noticed that there is no apps listed in the superuser. I tried 'su' command in the emulator terminal & I got permission denied.
Luckily all the apps are working in perfect harmony. However, how do I get the superuser permission back? It seems like my device is not rooted. Do I need to root my phone again? Fingers crossed I don't.
Initially, I tried to flash the Ice Cream Sandwich. I tried multiple times but to no avail. I even tried to change the HBOOT (from CM7 > downgrader > Stock HBOOT) but the process failed. I afraid that this might be the cause my root access got lost. Anyone can verify this?
Thanks!

Su app will be built into the ROM so you should still rooted. Sounds like Su settings are just defaulting to deny. Open Su, menu > settings and check its set at prompt (safer than allow). After flashing new Rom you'll need to launch apps that require root access to allow them permission again. You might need to update the Su app or binaries if permissions don't stick.
Sent from my HTC Desire using Tapatalk 2

beachcomber said:
Su app will be built into the ROM so you should still rooted. Sounds like Su settings are just defaulting to deny. Open Su, menu > settings and check its set at prompt (safer than allow). After flashing new Rom you'll need to launch apps that require root access to allow them permission again. You might need to update the Su app or binaries if permissions don't stick.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
beachcomber,
1. my Superuser is set at prompt.
2. I am not sure which app that require root access. Could you give me some examples so that I can run them?
3. I tried to update the su binaries, but I got this:
" checking current install path...FAIL!"
" failed to find currently installed su binary. Update cannot continue."
Therefore, what do you suggest?
Thanks.

xuminarc said:
beachcomber,
1. my Superuser is set at prompt.
2. I am not sure which app that require root access. Could you give me some examples so that I can run them?
3. I tried to update the su binaries, but I got this:
" checking current install path...FAIL!"
" failed to find currently installed su binary. Update cannot continue."
Therefore, what do you suggest?
Thanks.
Click to expand...
Click to collapse
Take a backup. Download this. Flash it through recovery. Reboot and check if it works.

Alaa said:
Take a backup. Download this. Flash it through recovery. Reboot and check if it works.
Click to expand...
Click to collapse
Thank you! It works!

Lost shell root access

Hi,
i have a rooted Desire Z currently running CM9 RC2, and I've noticed recently that my # shell has been replaced by a [email protected]:/ and it seems like I don't have root access there. I can't ls in /data/ for example, and su throws a permission denied error. However, apps that require root access(such as Titanium Backup) still seem to work. I noticed this happen right after I installed and ran Busybox. I did not even install busybox from the app as I already have it. I was just trying to get the apk file for another device with no internet access. I'm not sure if this app is what caused it, but it was when I noticed it.
In any case, short of a nandroid restore how do I get back shell root access and the proper shell?
Thanks.

Most likely your root access under System Settings -> Development was changed from "ADB and Apps" to "Apps Only".
PS: why would you be installing busybox, CM9 came with it (likewise with superuser and su).

Thanks. That worked.
Like I mentioned in my original post
I did not even install busybox from the app as I already have it. I was just trying to get the apk file for another device with no internet access.
Click to expand...
Click to collapse

goister said:
Thanks. That worked.
Like I mentioned in my original post
Click to expand...
Click to collapse
Though your quote here conflicted so wasn't sure :
I noticed this happen right after I installed and ran Busybox.
Click to expand...
Click to collapse

Sorry for the confusion, by running busybox I meant simply launching the Busybox app(which is just an installer, not busybox itself), but not clicking the "install busybox" button in the app to actually install busybox on my phone.