Database Info

[Q] "su" permission denied -superuser not denying Terminal Emulator

I im attempting to install this bootanimation with sound. With the direct instructions from the op here
When i type "su" in terminal emulator permission is denied.
I am setting the system folder as read/write using root explorer.
I tried it with just root set as read/write
I tries it with both as read/write
Still no go -permission denied
Superuser does not have any apk listed as being denied root access. Superuser has never prompted me to allow or deny terminal emulator root access.
Inspire (obviously) running CM7.0.3
Am I doing something wrong? or missing something? or could this be a error with terminal emulator and/or the ROM?
Thanks for any insight or ideas.

you should be getting a pop-up from super user right after you type su in the term emulator and hit enter.

i have this problem too

I had a similar problem like this when I first started out.......I ended up downloading root checker...which not only checks for root...but makes sure you have a recent version of busybox installed....in my case I didn't. I downloaded and installed busy box and it fixed everything.
Not sure if this will help you, but thought I would try.

Thanks S.Reno9. I installed root checker and I did have busybox installed and still no dice. I dont know what the deal is.
I really hope we can get some more help on this.

Reading this post confirmed the issue came from using Root Tools. What I did was move the cache back to data and SU started working again.

I also have this problem. How did you "move cache back to data." (sorry for the noob question)

same here
after type "su" dont get any pop window only permission denied
what to do now?

A couple things to try -
1 - Clear data from Terminal and Superuser and try again
2 - Uninstall and Reinstall Terminal and Superuser
I have had success with both of these suggestions and different times with this issue
Whoa - just noticed how old this thread was before you posted. Guess it's better than opening a new one.

Solved!
I tried installing busybox but no luck.
I copied the executable (in your case sh script) to root, and now it works fine

It's Super User issue
For me it was because of Super User updates and the problem solved after I had uninstalled the last updates for Super User
recommended from Google Play.
Thanks for the tips.

busybox not installed properly

i have a samsung epic 4g. iused super1click but it is saying that busybox was not installed properly and now rooted apps are saying i do not have root access but root checker says i have root access please help

download "busybox installer" from the android market. you can install the latest busybox from it

i installed busybox installer but it is sayin it is already installed but not installed correctly

go into /system/xbin and /system/bin and look for the file "busybox." delete it and try installing it again with busybox installer

i have tried that in both system/bin and system/xbin but it will not delete. do i need a specific file management app

nalanotae said:
i have tried that in both system/bin and system/xbin but it will not delete. do i need a specific file management app
Click to expand...
Click to collapse
i forgot to mention that you will need to mount your system as read/write. to do this, a file management app would be very helpful. root explorer in particular (a paid app, but as you may already know there are always ways to get apps for free; that is all i will say about warez as it is prohibited on xda). in root explorer, you can mount your phone between r/w (read/write) and r/o (read only). once you mount it as r/w, i believe you can now delete those files

one other thing i forgot to mention, i keep getting a notification that my su binary is outdated when i click to update it says fail.
ok so i was able to delete the busybox files out of the 2 folders but when i went to install it with the busybox app it says "it looks like busybox is installed but it does not appear to be the version that you selected to have installed, you may want to try the intalation again but this using a different istalation location." i try a different location and check my root checker and it keeps telling me that busybox is installed incorrectly

as i have not used superoneclick before, i have no knowledge about the su binary being updated. i used z4root to root my phone.
your best bet is to do one of the following:
a) if you can unroot your phone, then do so (i believe superoneclick allows you to unroot your phone). then try rooting it again using z4root. download z4root from here and tell me what options it gives you when you open the app (it should say either temporary root and permanent root; select permanent root). z4root should work on your phone as it has the same requirements as superoneclick (which is having android version 2.2/2.2.1)
b) if step a didnt work, post in the superoneclick thread for help. but step a should work

Nexus 5
Rooted
Stock image
Used nexus root toolkit
Busy box crashes when attempting to install from within busybox
Says not installed
Used root explorer to check system/bin
And
System/xbin
No filename that says busybox
Not sure what to do.
---------- Post added at 10:47 AM ---------- Previous post was at 10:35 AM ----------
Resolved
Set system to r/w at boot as root.
Launched bb
Says installed

mjs1231 said:
Nexus 5
Rooted
Stock image
Used nexus root toolkit
Busy box crashes when attempting to install from within busybox
Says not installed
Used root explorer to check system/bin
And
System/xbin
No filename that says busybox
Not sure what to do.
---------- Post added at 10:47 AM ---------- Previous post was at 10:35 AM ----------
Resolved
Set system to r/w at boot as root.
Launched bb
Says installed
Click to expand...
Click to collapse
I have this same issue on my Nexus 6, i also used Nexus Root Toolkit, how did you set your system to r/w at boot as root?

I am not able to install buzybox due to "try to installing to a different location that may resolve isuue..please help me

I know this is old!
Hello readers,
I am aware that my resolution might not help everyone but it will definitely help some. This might only help if you are rooted and using the SuperSu app..
I know this is a really old thread. But there might still be people out there that have this problem and are having a hard time finding the the answer for it. I was just 5 mins prior searching on google for an answer but could not find one.
And so how did I fix it you may ask? (I hope)
Well long story short I turned the following option of in the SuperSu application: "Mount namespace separation"
I thought of this because I had seen a pop-up message when using Titanium Backup that if I experience problems, I should disable that option. And it was probably referring to the Titanium Backup app alone and not any other. But I gave it a shot and it worked.
In detail for those who need it:
It does not matter if you have the Busybox (by Stephen (Stericson)) application installed during this or not. (I had it uninstalled during)
Open the SuperSu app, swipe left on the screen twice so you get to the Settings page (or just click the Settings tab)
Scroll down until you see the option "Mount namespace separation".
If it is activated, disable it.
Reboot
Go ahead and install Busybox if you haven't.
Open Busybox and wait for it to load completely
Click install
Hurray!

Hello, i have bought busybox pro but i can't manage to install it through the app, in /system/xbin, i only have one file named "dexlist" and in /system/bin i have many files but none named busybox, when i try to install busybox on /su/bin, i get a message: "it looks like the installation of busybox was not successful / try installing it to a different location that may resolve the issue", but i tried differ'ent locations and it didn't work
---------- Post added at 09:03 PM ---------- Previous post was at 08:53 PM ----------
don't forget to reboot after unchecking "mount namespace separation" !! if not it won't work. my phone was quite long to reboot though...
it still doesn't work for me... on huawei p8 lite 2017 (PRA-LX1)

I'm still using the old version not BusyBox V+ .. anyone tried the latest version? it seems quite confusing and I couldn't execute scripts

Busybox
Example if use custom rom viper10 you can set system r/w in tweak > misc

lovemajj said:
Hello readers,
I am aware that my resolution might not help everyone but it will definitely help some. This might only help if you are rooted and using the SuperSu app..
I know this is a really old thread. But there might still be people out there that have this problem and are having a hard time finding the the answer for it. I was just 5 mins prior searching on google for an answer but could not find one.
And so how did I fix it you may ask? (I hope)
Well long story short I turned the following option of in the SuperSu application: "Mount namespace separation"
I thought of this because I had seen a pop-up message when using Titanium Backup that if I experience problems, I should disable that option. And it was probably referring to the Titanium Backup app alone and not any other. But I gave it a shot and it worked.
In detail for those who need it:
It does not matter if you have the Busybox (by Stephen (Stericson)) application installed during this or not. (I had it uninstalled during)
Open the SuperSu app, swipe left on the screen twice so you get to the Settings page (or just click the Settings tab)
Scroll down until you see the option "Mount namespace separation".
If it is activated, disable it.
Reboot
Go ahead and install Busybox if you haven't.
Open Busybox and wait for it to load completely
Click install
Hurray!
Click to expand...
Click to collapse
Hey, really glad you posted this even though you said it was old, and I'm still on it :laugh: but the combo of your solution, and mounting my /system as "r/w" through Root Explorer worked on my 6P on Oreo!! (OPR6)
Thanks again!! :good:

Williquah said:
Hey, really glad you posted this even though you said it was old, and I'm still on it :laugh: but the combo of your solution, and mounting my /system as "r/w" through Root Explorer worked on my 6P on Oreo!! (OPR6)
Thanks again!! :good:
Click to expand...
Click to collapse
What exactly do you mean by "and mounting my /system as "r/w" through Root Explorer" can you explain further? I can't get Busybox to install after OPR6 update

idbl_fanatic said:
What exactly do you mean by "and mounting my /system as "r/w" through Root Explorer" can you explain further? I can't get Busybox to install after OPR6 update
Click to expand...
Click to collapse
I'd be happy to help. It's been a little while and I haven't repeated the process yet so forgive me if I'm not super clear, even though I think I should be.
So what I meant was get the app Root Explorer ($3.99 on the app store) I don't know how 'piracy' is really looked at on XDA, though I can't imagine well, but you can download the Root Explorer 'pro' apk, and then - as long as it helps - purchase the app from GPlay to make sure to support the devs, which is what I did.
So to get to the actual process - should be quite easy as I did this on OPR6 myself - open Root Explorer, navigate to the "root" tab at the top. Then you should see "Mounted as r/o" and right next to it, a button that says "Mount R/W". Toggle that button, and the text on the left should state "Mounted as r/w", then try to install busybox (however you prefer - I used BusyBox Free by Stephen (Stericson) like I always do).
Hope you are successful with that method, please keep me updated with your outcome so I can help as best as I can.

Williquah said:
I'd be happy to help. It's been a little while and I haven't repeated the process yet so forgive me if I'm not super clear, even though I think I should be.
So what I meant was get the app Root Explorer ($3.99 on the app store) I don't know how 'piracy' is really looked at on XDA, though I can't imagine well, but you can download the Root Explorer 'pro' apk, and then - as long as it helps - purchase the app from GPlay to make sure to support the devs, which is what I did.
So to get to the actual process - should be quite easy as I did this on OPR6 myself - open Root Explorer, navigate to the "root" tab at the top. Then you should see "Mounted as r/o" and right next to it, a button that says "Mount R/W". Toggle that button, and the text on the left should state "Mounted as r/w", then try to install busybox (however you prefer - I used BusyBox Free by Stephen (Stericson) like I always do).
Hope you are successful with that method, please keep me updated with your outcome so I can help as best as I can.
Click to expand...
Click to collapse
Well that didn't work
Update, I had to change the path to /system/bin instead of /system/xbin

[Q] Rooted 2.3.4 Mesmerize; Now what...?

I'll try to keep this as short and simple as possible:
I am a total newb to the touchscreen, smart-phone, I just got a USCC Samsung Mesmerize SCH-i500, came installed w/ 2.3.4 Gingerbread & I just had to reflash it w/ USCC EH09 root using Odin 3 v1.85, now, everything I have "hacked" in the past (PSP (both fat & slim), iPod Touch, etc) I've always had to use step-by-step instructions (I am not a dev & know absolutely nothing about programming) & the same applies here.
So, it has root access & BusyBox (I don't even know what that is) installed, so my question is what was the point?
What exactly can/should I do from here? Any suggestions?

well, with a rooted android device you can
*remove bloatware (you're wasting your root if you don't do this)
*system-wide adblock (my personal fav)
*change boot animations
*flash custom ROM
*free wifi tethering
*overclock the CPU
and more!

Thank you for the answer, I'll look into these things but on a side note: my su app keeps saying that theres an update available for my su binary & every time I tap update it goes through the process & less than half-way through it pops up a message saying: "This updater cannot update the su binary on phones that have some kind of write protection on the system partition like S-ON. You can continue to use Superuser with your outdated binary, or update su with ROM Manager."
I have tried to use ROM Manager, I even bought the Premium version, either way it gives me the same message, even after doing the Fix Permissions option, is there a way to manually allow su access to the files it needs to overwrite/update?
Oh, and, yes, I have allowed it when su asked, so now I'm at a loss....

Xeno Templar said:
Thank you for the answer, I'll look into these things but on a side note: my su app keeps saying that theres an update available for my su binary & every time I tap update it goes through the process & less than half-way through it pops up a message saying: "This updater cannot update the su binary on phones that have some kind of write protection on the system partition like S-ON. You can continue to use Superuser with your outdated binary, or update su with ROM Manager."
I have tried to use ROM Manager, I even bought the Premium version, either way it gives me the same message, even after doing the Fix Permissions option, is there a way to manually allow su access to the files it needs to overwrite/update?
Oh, and, yes, I have allowed it when su asked, so now I'm at a loss....
Click to expand...
Click to collapse
I had the same issue today, couldn't update SU.
but after I had updated the terminal emulator, I was able to update SU.

Fixed the Problem with updating SU Binary
Recently updated my device with a new rom and was unpleasantly surprised to not be able to update my SU binary with either the application itself or CWM. I am not sure that this is the best way to handle the problem, but I found a solution that worked for me.
1. Open "System/XBin" in RootExplorer (or a similar app)
2. Mount the drive as R/W using the button up at the top left
3. Open the superuser app and update the binary from within the app
4. There may be an error in the log about the device not being able to remount the drive properly, but the update WILL occur.
5. Use RootExplorer to open the directory again and mount as R/O.
I hope this helps!

[Q] Can't w to /system, can't update busybox, wifi not working, MotoDroid, CM 6.1.2

Device: Motorola Droid
ROM: CyanogenMod 6.1.2
Let me know if you need any other info other than this.
1. Cannot update su binary without flashing it from CWM recovery. I am currently up to date with 3.0.3 binary and 3.0.6 apk. See #2 for possible explanation.
2. Everything that calls for root access works except for, what I've noticed, apps that need /system/ and/or its subdirectories to be mounted as rw. *Superuser grants them the privileges, but the apps swear up and down that that isn't the case. Examples: ROM Toolbox, root file managers, etc. *Also, I cannot update busybox. It actually accepts the su privileges, but then fails. I can, however, install it to /mnt/sdcard/, not that that helps me. *There is also an app that has the option of mounting /system/ as rw, and while it says it works, I can't write to the directory or any of its subdirectories from any program. *I have Terminal Emulator, but I don't know enough about it to know what to do if that could help. I've gotten su privileges for it, but it won't let me access /system/. (side note: is there a way to flash busybox from CWM recovery and replace the WLAN files that I need to replace in /system/xbin/ and/or /system/bin/? In other words, since this worked for the su binary, would it work for those? If so, do u know of existing zip files or how I would go about making one?)
3. My wifi connects, tries to establish an ip address, and then is marked disabled and doesn't connect. I currently have it inactive. This has been happening since shortly after installing the CyanogenMod 6.1.2 -- not directly afterwards, but likely after installing and updating all my apps (I didn't install or update any system apps, as I knew not to).
Please let me know if you need to know anything else. I have searched and searched and searched for the answers to this problem, but I can't find it. In a nutshell I can't write to /system unless in recovery, and I can't use wifi at all. I did find some WLAN, etc files to replace the ones in /system with (a supposed wifi fix), but I obviously can't so that without write permissions.
Thank you so much in advance! I've figured out all my other previous issues on my own, but this one is a doozy!
Best,
SNJ

Me too - no mounting rw, busybox pro fails
Hi, I have the same problem on a Galaxy S with CM7.1. It just happened after I updated the last version of busybox pro. My wifi can't connect, everything which needs to mount system as rw fails, root explorer can't even start, and so the installation of busybox pro as well. It shows a huge list of apps which I need to symlink (never asked that before), and after trying installation it says that it appears as a different version of busybox than the one I selected was installed. I wonder if removing all the symlinked apps could do some good instead of leaving the overwrite option checked.
Anyone can help?
thanks
---------- Post added at 12:57 PM ---------- Previous post was at 12:24 PM ----------
just a small add-on. I tried a different busybox installer, and even if superuser indicated root access was granted, the app shut down telling it didn't detect root access.
???

OK, not really....I decided to do a system restore....bang, now I can only boot in recovery mode, not even the previous version but v.3.0.0.5, and I can't mount a thing, I get messages as unknown volume for path, unable process volume!....Now, how can I in any way wipe all and try to reinstall CM 7.1? phone doesn't get in download mode either.

Try flashing and moving files through adb.

Mounting the filesystem for r/w, adb remount issues

All I want to do is replace my hosts file with a larger, more robust one to reduce the ads I see when browsing the internet and running apps.
It seems like no matter what I do, I can't mount the filesystem on my Note 10.1 N8013 to make changes to /system. I am rooted, I have SU, and whether I use ES File Explorer, give access to root and permission to mount filesystem as r/w, or I use Root Explorer, browse to /etc and click the Mount r/w button, or I use adb remount or adb shell, su, and remount rw, I absolutely cannot get r/w access.
Please tell me someone has figured out how to make this work for the Note 10.1.

Bumping.

Did you gain root access using the root injected method. This is a known problem by using that method. The only way to fix this (temporarly) is to boot into cwm and fix permissions. This should allow you to do what you please. Also use a different root browser because i noticed certain ones like root explorer borks it again which makes you have fix the permissions again. That is why i said its a temporary fix. But ever since i started using the paid version of Root Browser (which is very well worth the 99 cents btw) I have not seen this problem pop up since.
Sent from my GT-N8013 using Tapatalk 2

I was about to ask the same question.
Rooted using injection.
Deleted a few apps using Root Explorer, but for some reason I had to fix permissions and reboot every time.
I used Root Explorer [paid] but the problem still persists.
I also used Solid Explorer- I can only modify once until needing to fix permission.
Anyone found a solution yet?