Hello...
My question is simple. Why I get permission denied on rooted phone?
When I type: adb shell, I get $. Then I type su and I get this message: Permission Denied.
I followed this how-to (http://forum.xda-developers.com/showthread.php?t=792016) to root my phone and everything was fine. I get root privilegies and installed Superuser.apk, su, busybox...
But now, when I try to get root privilegies, I get the message above. Why?
Thanks and sorry for my english.
Because your phone isn't rooted. Either you didn't do it right or it's unrooted somehow, perhaps you got an OTA.
I think my phone is rooted, because there are many apps that use root permissions installed and working normally.
Sent from my Nexus One using XDA App
Then su isn't set up properly, or isn't asking for superuser permissions, or has been denied superuser permissions? Look in your Superuser app, maybe clear settings in it and let su ask again.
So, I cleared the settings in Superuser.apk and tried open Adfree apps that needs su permissions... and it opened and got permissions normally. I really don't understand what is the problem...
Sent from my Nexus One using XDA App
You do have usb debugging enabled right?
Related
All others rooted phones have a message showed when an application asks root, why don't we have this on Tattoo ?
On Tattoo root permissions are always enabled
Ok, it's nice but we can't see which application ask root :/
Like Terminal Emulator, when you launch it, the shell is always in normal user "$", not in root :/
JoOoSs said:
Ok, it's nice but we can't see which application ask root :/
Like Terminal Emulator, when you launch it, the shell is always in normal user "$", not in root :/
Click to expand...
Click to collapse
This is true, but I dont know how, after isntalling 5faif ROM, terminal emulator shows me the #, id command shows me that I'm root.
I'm on stock ROM, this is the problem i think!
Anybody has SetCPU ?
The problem with this is that every application can obtain root without our knowledge.
It is a serious security flaw.
Not really. Android is pretty secure. Even if you get a brick from a Andirus (Virus + Android), it's a piece of cake to undo the damage.
Netbuster said:
This is true, but I dont know how, after isntalling 5faif ROM, terminal emulator shows me the #, id command shows me that I'm root.
Click to expand...
Click to collapse
Because that rom you've flashed contains custom boot.img by mainfram3 that gives to you root at startup and loads tattoo-hack.ko (partition r/w always mounted)
Coburn64 said:
Not really. Android is pretty secure. Even if you get a brick from a Andirus (Virus + Android), it's a piece of cake to undo the damage.
Click to expand...
Click to collapse
Actually i wasn't having viruses in mind. More like keyloggers and such. SU prompt wasn't invented for no reason...
I think the OP was asking about SuperUser.apk.
It's a modified su plus a service that asks for user intervention when a program calls /system/bin/su. It's nifty and it should be used by everyone.
Android apps are prevented from looking into other apps data. If su is readily available, a app can escalated it's privileges and steal your personal info, by reading data from other apps.
mainfram3 said:
I think the OP was asking about SuperUser.apk.
It's a modified su plus a service that asks for user intervention when a program calls /system/bin/su. It's nifty and it should be used by everyone.
Android apps are prevented from looking into other apps data. If su is readily available, a app can escalated it's privileges and steal your personal info, by reading data from other apps.
Click to expand...
Click to collapse
Exactly my point.
MoDaCo Custom ROM 1 includes Superuser apk for root access.
P
Anyone know how to fix Superuser Permissions manually?
I have Tattoo with rooted boot.img (mainfram3)
I pushed su into /system/bin/
Made chmod 4577 /system/bin/su
Pushed superuser.apk from Modaco Rom to /system/app/
Restart sure...
SuperUser Permissions can be executed (list is clear)
But any app doesn't send request to Superuser Permissions.
What i could forget?
Finally, I solved it partially.
Sure, i have rooted boot.img
I extracted from Modaco Custom ROM for Tattoo:
su
Superuser.apk
copied su to: /system/bin/su
copied Superuser.apk to: /system/app
run in terminal: chmod 4577 /system/bin/su
restarted and everything works fine now... Superuser Permissions shows all root-requests, Titanium Backup works, other root-things works too
But i notice, that su-binary from Modaco ROM is about 34-36 kb, but
su-binary from guide of getting root is about 80-85 kb.
1-2 months ago we faced with difference in size of su. We choosed bigger su in case, what it can run "flash_image", smaller su can't run.
But maybe it fixed already? I did not test it yet.
Thanks @5[Strogino]
I was trying to use Titanium today to back up my apps but it didn't work.
lukic said:
Thanks @5[Strogino]
I was trying to use Titanium today to back up my apps but it didn't work.
Click to expand...
Click to collapse
What exactly wrote TB?
Did you download busybox via TB?
I don't remember exactly.
It did ask me to download busybox and I did that, but still it didn't work.
Can i unroot if necessarry
Is there a way yet
Sent from my DROID3 using XDA App
If you don't install the su binary to /system/xbin all you have to do is reboot and the root access from adb is gone until you do the exploit again.
Wait so if i do the one click root can i unroot that
Sent from my DROID3 using XDA App
You would have to delete the su binary from /system/xbin and uninstall superuser.apk for it to be considered unrooted.
wat if you factory reset it doesnt unroot
esp if you install superuser from the market, its in /data vs. /system right?
but that would leave /xbin intact right? so youd kinda be stuck rooted rofl idk
whoopsiedaisy said:
wat if you factory reset it doesnt unroot
esp if you install superuser from the market, its in /data vs. /system right?
but that would leave /xbin intact right? so youd kinda be stuck rooted rofl idk
Click to expand...
Click to collapse
I'm not sure if a factory reset leave xbin intact or not but even if it did you could just adb in, use the exploit and remove su manually.
Just keep in mind...SuperUser.apk is not root. You can install that on a non-rooted phone, it just doesn't do anything.
Root is su, having (s)uper(u)ser access to the system. SuperUser.apk is just your (you the user) control over what is granted su rights. Without the SuperUser.apk, anything and everything that wanted superusers permissions would have it, definitely something you don't want.
I'm not sure a factory reset would remove su from /system/xbin but it would remove SuperUser.apk from /data/app. This would mean you'd have no control over what apps would want to take superuser permissions and access your filesystem.
While you have superuser permissions...just delete the /system/xbin/su and reboot.
Root also doesn't prevent OTA updates.....though you will probably lose root after an OTA update and have to redo the exploit.
Hey guys,
Long story short, I rooted using this guide (zergrush)
rootgalaxynote.com/galaxy-note-root/how-to-root-galaxy-note-gt-n7000method-1/
Everything went fine, it said it was successful, rebooted and seemed to work,
However, Superuser wasn't installed, so I went to the market and downloaded it.
It was missing the SU binary, so I found it online,
I'm just wondering where do I place the SU binary file?
---------------------------------------
I'm not sure if its rooted or not, as root explorer shows all the hidden system folders etc,
however if I go to the command line and type SU I get "$SU not found" not "#"
It makes sense that I'm not getting # as Superuser wasn't installed (the SU binary anyway)
So In short, how do I check for root (without using command line or another app to check for Superuser)
and second, where do I place the SU binary if I download it from the internet?
Thanks,
James
First thing Which ROM is installed on your device?(can see under setting - about phone)
Simple thing, if you dont have superuser or superSU application in drawer, you are not rooted.
When first time use SuperSU, it will ask to update binary N it will place automatically if you are rooted.
There's an app on the market/play store that will tell you if you're rooted or not. It's called Root Checker Basic. However, I had SU installed so I'm not sure if that's a factor or not.
Sent from my HTC Desire Z using XDA
So when I open up terminal emulator there is a '$' sign and I input the command "su". It says that super user granted permission. After that the '$' disappears and I can't do any other commands. If I enter one it will just skip to the next line with no effect. Can anyone help? Thanks.
NanoNoodle said:
So when I open up terminal emulator there is a '$' sign and I input the command "su". It says that super user granted permission. After that the '$' disappears and I can't do any other commands. If I enter one it will just skip to the next line with no effect. Can anyone help? Thanks.
Click to expand...
Click to collapse
TiBu wipe Terminal Emulators data and reboot...
BNaughty said:
TiBu wipe Terminal Emulators data and reboot...
Click to expand...
Click to collapse
I really want to try it out but for some odd reason none of my apps that require root works now. It must be something wrong with my Super user
Uninstall superuser apk and reinstall from market? Or try clearing the data of it
Sent from my Nexus 7 using Tapatalk 2
NanoNoodle said:
I really want to try it out but for some odd reason none of my apps that require root works now. It must be something wrong with my Super user
Click to expand...
Click to collapse
Try updating the su binary. Or try installing super su switching to super su's binary AND THEN uninstall super user. Or the opposite if your already using super su. You must NOT just uninstall the su app though. You must install the other, update the binary (instructions can be found in super su's thread in android apps and games (IIRC) the app itself, or Google it.
And THEN uninstall the other one.
Worth a shot.
Snowflake approved this message.
Babydoll25 said:
Try updating the su binary. Or try installing super su switching to super su's binary AND THEN uninstall super user. Or the opposite if your already using super su. You must NOT just uninstall the su app though. You must install the other, update the binary (instructions can be found in super su's thread in android apps and games (IIRC) the app itself, or Google it.
And THEN uninstall the other one.
Worth a shot.
Snowflake approved this message.
Click to expand...
Click to collapse
I tried to update the Superusers binary but it gets stuck on trying to get root access. I installed Super su and it tried to install the binary but it doesn't seem to be able to finish updating. Any other alternatives?
NanoNoodle said:
I tried to update the Superusers binary but it gets stuck on trying to get root access. I installed Super su and it tried to install the binary but it doesn't seem to be able to finish updating. Any other alternatives?
Click to expand...
Click to collapse
http://download.chainfire.eu/204/SuperSU/CWM-SuperSU-v0.94.zip
Download and flash in recovery. Boom, root.
Hello all,
A friend gave me his Droid 3 which was successfully rooted (Superuser version 3.13 is installed). When I look at the log I can see many past "Allowed" entries. However, I attempted to install Safestrap (version 3.05), and it was denied Superuser access (can see the denial in the log). I then attempted to grant other apps Superuser permissions and I get a "[App Name] has been denied Superuser permissions" message (and it shows "Denied" in the Superuser Log).
The really odd things are that (1) it doesn't prompt to allow or deny (despite the setting saying to prompt), and (2) if I select Superuser funcitons within the Superuser App, it will allow them. For example, if I select "temp unroot", it says "Superuser has been granted Superuser permissions".
I know I can SBF the phone and start over, but there are lots of paid Apps on the phone and I just assume try to work on getting Superuser working again if it's possible.
Please help!
Try setting to always allow
Sent from my DROIDX using XDA Free mobile app
Solved! Ok, with the device connected to my computer and playing around in adb, I noticed that the permissions for the SU binary were all goofed up. So I issued the command: adb shell "chmod 6755 /system/bin/su" and that solved the problem. Hope this helps someone else.
Shadow: Thank you sir for your reply. I should have mentioned in my original that I did try "always allow" in addition to prompting and it didn't make a difference. However, I solved it by changing the su binary's permissions (see above). Thanks again for takinig the time to reply.