Database Users

(Q) Root with Super User

So I'm rooted and downloaded Super User app from market. I have a bunch of root apps but the only app listed in the super user app is Titanium. Any reason why the other rooted apps (Set Cpu, Minfree Manager, etc.) aren't listed?

Have they asked for superuser?
Via EVO on 4G with XDA App

awenthol said:
Have they asked for superuser?
Via EVO on 4G with XDA App
Click to expand...
Click to collapse
No it doesn't
Sent from my CM6 powered device

krazyflipj said:
No it doesn't
Sent from my CM6 powered device
Click to expand...
Click to collapse
We managed to fix this problem the other night on the irc channel. I didn't post anything because it doesn't seem like many people are using superuser.apk. The problem is that superuser needs to install it's own version of the su program to run properly. The current root method replaces su every reboot. When you lose the su that superuser.apk installs it can't control root access anymore and basically any program can request root without a prompt to you. The fix is to just replace the jk-su file in /system/bin/ with the superuser su. Then every reboot it will just use the one that works with the superuser app. I did this a few days ago and haven't had any problems.
The procedure is as follows (you need to use adb):
Go into the superuser app, go to the "settings" tab and at the very bottom choose to update su (it should change from saying original to something like "su v2.3.1-ef").
Plug the phone into usb and make sure you have USB debugging enabled.
Open a command prompt on the computer and goto your android sdk tools folder to run these commands (IMPORTANT NOTE - Make sure you have the phone screen on and unlocked when you run the su command below because superuser will ask you for permission and you need to click yes. It wont prompt if the screen is off or locked and the adb shell will just sit there waiting for a response. As soon as you click yes on the phone you should get a # in the adb shell):
adb shell
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
cp /system/bin/su /system/bin/jk-su
exit
Now you should just reboot the phone and check that it worked by running any program that needs root access that isn't already listed with superuser. I suggest shootme or wifi tether. tether asks when you start or stop tethering and when you allow a mac address in the access control.

richse said:
We managed to fix this problem the other night on the irc channel. I didn't post anything because it doesn't seem like many people are using superuser.apk. The problem is that superuser needs to install it's own version of the su program to run properly. The current root method replaces su every reboot. When you lose the su that superuser.apk installs it can't control root access anymore and basically any program can request root without a prompt to you. The fix is to just replace the jk-su file in /system/bin/ with the superuser su. Then every reboot it will just use the one that works with the superuser app. I did this a few days ago and haven't had any problems.
The procedure is as follows (you need to use adb):
Go into the superuser app, go to the "settings" tab and at the very bottom choose to update su (it should change from saying original to something like "su v2.3.1-ef").
Plug the phone into usb and make sure you have USB debugging enabled.
Open a command prompt on the computer and goto your android sdk tools folder to run these commands (IMPORTANT NOTE - Make sure you have the phone screen on and unlocked when you run the su command below because superuser will ask you for permission and you need to click yes. It wont prompt if the screen is off or locked and the adb shell will just sit there waiting for a response. As soon as you click yes on the phone you should get a # in the adb shell):
adb shell
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
cp /system/bin/su /system/bin/jk-su
exit
Now you should just reboot the phone and check that it worked by running any program that needs root access that isn't already listed with superuser. I suggest shootme or wifi tether. tether asks when you start or stop tethering and when you allow a mac address in the access control.
Click to expand...
Click to collapse
Hmmm cp /system/bin/su /system/bin/jk-su didn't work. I ls /system/bin and don't see jk-su listed just su...

krazyflipj said:
Hmmm cp /system/bin/su /system/bin/jk-su didn't work. I ls /system/bin and don't see jk-su listed just su...
Click to expand...
Click to collapse
What root did you use? I did mine manually so there may be some differences if you used a one click.
Edit: I just looked at noobnl's one click root and it uses the same script that contains the line:
#copies busybox su
cat /system/bin/jk-su > /sdx/su
so it should definitely be there even if you used his one click.
When you run the command "ls -l /system/bin/jk-su" what do you get?
I get this:
ls -l /system/bin/jk-su
-rwsr-sr-x root root 26264 2010-09-18 06:10 jk-su

Please delete

krazyflipj said:
Please delete
Click to expand...
Click to collapse
Did you get it working? After you updated su through the superuser app then it started working so that is why it asked you for permission when you were in terminal. The problem is that if you reboot without applying the rest of the fix to replace jk-su then you will lose the updated su and it will stop working.

richse said:
Did you get it working? After you updated su through the superuser app then it started working so that is why it asked you for permission when you were in terminal. The problem is that if you reboot without applying the rest of the fix to replace jk-su then you will lose the updated su and it will stop working.
Click to expand...
Click to collapse
Hey Richse, I'm trying to get this to work but it isn't.

rose1 said:
Hey Richse, I'm trying to get this to work but it isn't.
Click to expand...
Click to collapse
can you give me more information, what errors are you getting or what exactly is happening?

richse said:
can you give me more information, what errors are you getting or what exactly is happening?
Click to expand...
Click to collapse
Okay, I did the one click root method that is stickied. Then I did
adb shell
su
after doing su, I initially saw on the phone that unknown user was asking for superuser access. Of course, "unknown user" is me so I granted it. Then I saw the # then I went ahead and did
mount -t rfs -o remount,rw /dev/block/stl9 /system
That worked fine . The line repeated itself which indicates that it worked. When I do
cp /system/bin/su /system/bin/jk-su
it then says cp: not found.
Just to give you a little more info, I just restored my phone with odin to factory defaults, then I updated to the DI07 update. Then I installed the final clockwork mod recovery, then I did the one click root method. Then I installed superuser in the system/app folder.

rose1 said:
Okay, I did the one click root method that is stickied. Then I did
adb shell
su
after doing su, I initially saw on the phone that unknown user was asking for superuser access. Of course, "unknown user" is me so I granted it. Then I saw the # then I went ahead and did
mount -t rfs -o remount,rw /dev/block/stl9 /system
That worked fine . The line repeated itself which indicates that it worked. When I do
cp /system/bin/su /system/bin/jk-su
it then says cp: not found.
Just to give you a little more info, I just restored my phone with odin to factory defaults, then I updated to the DI07 update. Then I installed the final clockwork mod recovery, then I did the one click root method. Then I installed superuser in the system/app folder.
Click to expand...
Click to collapse
I'm not sure why cp doesn't work, it just means copy. An alternative to try is to delete jk-su and replace it with the su you updated. Use these commands in place of the cp command:
rm /system/bin/jk-su
cat /system/bin/su > /system/bin/jk-su
Make sure you do this after updating su in the superuser app and without rebooting in between. Let me know if you have any problems.

followed instructions. no errors but i still have no programs asking for permission. i had wifi tether downloaded before and it worked. I downloaded shootme to see if it would ask for permission and it didnt - but it works. neithe one is lited in superuser either.
listed is:
adfree / quickboot / root manager / startup manager ( 3 of them) / super manager / unknown ( spawned right after i followed instrution)
any ideas
uninstall supersuser and reinstalled:
listed apps now:
adfree / busybox installer / root explorer / rootmanager / sufbs / tit backup
again not sure is it is correct. but seems to work "I THINK"

spdwiz18 said:
followed instructions. no errors but i still have no programs asking for permission. i had wifi tether downloaded before and it worked. I downloaded shootme to see if it would ask for permission and it didnt - but it works. neithe one is lited in superuser either.
listed is:
adfree / quickboot / root manager / startup manager ( 3 of them) / super manager / unknown ( spawned right after i followed instrution)
any ideas
uninstall supersuser and reinstalled:
listed apps now:
adfree / busybox installer / root explorer / rootmanager / sufbs / tit backup
again not sure is it is correct. but seems to work "I THINK"
Click to expand...
Click to collapse
When you go to update su in the superuser app does it say "original" and then change or does it stay updated after you reboot?

richse said:
When you go to update su in the superuser app does it say "original" and then change or does it stay updated after you reboot?
Click to expand...
Click to collapse
what i have:
cwm 2.5.1
root 2.1.1
di07
now for the long and skinny:
i checked. went to superuser and it told me 2.3.1 -ef i then HARD rebooted, came back with no root.and superuser told be original, hard reboot again, still no root. So one more time- third time is a charm - i have root and superuser told me 2.3.1 -ef
thanks again for the help.
i think my phone might not be total stable.. lol
any ideas.
also - i thought about upping root to most recent but unsure if i need to unroot or if i can install over it. your thoughts on this matter!!!!

spdwiz18 said:
what i have:
cwm 2.5.1
root 2.1.1
di07
now for the long and skinny:
i checked. went to superuser and it told me 2.3.1 -ef i then HARD rebooted, came back with no root.and superuser told be original, hard reboot again, still no root. So one more time- third time is a charm - i have root and superuser told me 2.3.1 -ef
thanks again for the help.
i think my phone might not be total stable.. lol
any ideas.
also - i thought about upping root to most recent but unsure if i need to unroot or if i can install over it. your thoughts on this matter!!!!
Click to expand...
Click to collapse
I doubt you need to update root. The root I used was the original manual method by joeykrim. The one click just automates that method. There is no reason why you should have to reboot multiple times to get this working. You basically just replaced a file with a similar file and the script that was installed when you rooted uses that file to create a new su every time you reboot. Personally, I would wipe to stock with Odin and then use the manual root method to make sure nothing funny is going on with your phone. When you rebooted and the su was "original" you didn't lose root, it just meant that superuser wouldn't work. For now, as long as the 2.3.1 -ef sticks around superuser will work just fine. As an alternative you could try noobnl's newest stuff. Looks like he made it compatible with superuser, so I think that would negate the need to use this type of fix. I'm not sure what he did to add the compatibility but you could probably ask him.

if you flash noobnl's latest kernel, it includes superuser and it works perfectly.

rose1 said:
if you flash noobnl's latest kernel, it includes superuser and it works perfectly.
Click to expand...
Click to collapse
The only issue I see with that is you have to use a DG27 kernel. If you want to use a DI07 kernel you still need to use this fix.

richse said:
The only issue I see with that is you have to use a DG27 kernel. If you want to use a DI07 kernel you still need to use this fix.
Click to expand...
Click to collapse
Very true. I didn't think about that.

I have latest Noobls kernel flashed on top of DI07 and this fix did not work.First thing that dint work is i never got SuperUser prompt after i typed su in adb shell,i got su in windows but no prompt on the phone.
To make it short i did the whole procedure from BetterTerminal(now i got su prompt) rebooted and back to same problem.Man,this been bugin me for two days now,sometimes i reboot the phone and i have root permissions then i reboot again and they are gone!
Big question is:is everybody on Epic have same issue or is it just on certain phones,kernels or roms?

[Q] Do I have "real" root?

So I have a Samsung Vibrant with the following specs :
Firmware : 2.1-update 1
Baseband : T959UVJI6
Kernel version : 2.6.29
Build : ECLAIR.UVJI6
I used the Samsung Vibrant 1 click root application, have since verified I do have SuperUser installed as well as BusyBox, with quite a few different root based applications such as ClockWorkMod Recovery, One-Click Lag Fix, Set CPU, Titanium Backup, etc., and I have verified that ADB does work from a command prompt, however when I try to access su through ADB by doing the following commands, this happens :
C:/>adb shell
$ su
su
Permission denied
$
I have also tried to use Android Commander from my PC as a kind of root explorer and the program does detect my device and starts, but shows "Root Access : NO". From all threads I have investigated, this would almost seem as though I don't have "true" root access. Can anyone assist me and let me know what I am doing wrong?

bretjrodgers said:
So I have a Samsung Vibrant with the following specs :
Firmware : 2.1-update 1
Baseband : T959UVJI6
Kernel version : 2.6.29
Build : ECLAIR.UVJI6
I used the Samsung Vibrant 1 click root application, have since verified I do have SuperUser installed as well as BusyBox, with quite a few different root based applications such as ClockWorkMod Recovery, One-Click Lag Fix, Set CPU, Titanium Backup, etc., and I have verified that ADB does work from a command prompt, however when I try to access su through ADB by doing the following commands, this happens :
C:/>adb shell
$ su
su
Permission denied
$
I have also tried to use Android Commander from my PC as a kind of root explorer and the program does detect my device and starts, but shows "Root Access : NO". From all threads I have investigated, this would almost seem as though I don't have "true" root access. Can anyone assist me and let me know what I am doing wrong?
Click to expand...
Click to collapse
When you do "Adb shell" > "su" you have to allow it on your phone. A little popup will appear.

If you can su in a terminal on the phone itself then you can be certain you have root.
Are you sure there is not a prompt on the phone when you are attempting su from ADB? It might be asking for su permissions but timing out and showing denied.

bretjrodgers said:
So I have a Samsung Vibrant with the following specs :
Firmware : 2.1-update 1
Baseband : T959UVJI6
Kernel version : 2.6.29
Build : ECLAIR.UVJI6
I used the Samsung Vibrant 1 click root application, have since verified I do have SuperUser installed as well as BusyBox, with quite a few different root based applications such as ClockWorkMod Recovery, One-Click Lag Fix, Set CPU, Titanium Backup, etc., and I have verified that ADB does work from a command prompt, however when I try to access su through ADB by doing the following commands, this happens :
C:/>adb shell
$ su
su
Permission denied
$
I have also tried to use Android Commander from my PC as a kind of root explorer and the program does detect my device and starts, but shows "Root Access : NO". From all threads I have investigated, this would almost seem as though I don't have "true" root access. Can anyone assist me and let me know what I am doing wrong?
Click to expand...
Click to collapse
So after installing SU Terminal & Root Explorer from Android Market, when I did the following :
C:/>adb shell
$ su
su
#
I have verified that SuperUser permissions through ADB are obviously working. However when I do the following command...
C:/>adb root
adbd cannot run as root in production builds
...is displayed. It seems as though, yes, I do have SuperUser access, I don't have root access through ADB and Android Commander still does not recognize root. Is this because I am running the stock ROM, and if so, is there a general thread with all available/recommended Vibrant ROMs to install?

bretjrodgers said:
So after installing SU Terminal & Root Explorer from Android C:/>adb root
adbd cannot run as root in production builds
...is displayed. It seems as though, yes, I do have SuperUser access, I don't have root access through ADB and Android Commander still does not recognize root. Is this because I am running the stock ROM, and if so, is there a general thread with all available/recommended Vibrant ROMs to install?
Click to expand...
Click to collapse
Just to clarify, you realize adb root has nothing to do with your phone?
adb root restarts the adb daemon on the computer you are on as root (something I usually don't recommend).
When you start Android Commander make sure it has permissions on your phone when it makes the request.

d01100100 said:
Just to clarify, you realize adb root has nothing to do with your phone?
adb root restarts the adb daemon on the computer you are on as root (something I usually don't recommend).
When you start Android Commander make sure it has permissions on your phone when it makes the request.
Click to expand...
Click to collapse
Ok so I now understand the purpose of the adb root command after some additional research. I guess the issue is that when I run Android Commander, even though it does detect my device on the PC, it does not ask for/request SU permissions on my device

The FAQ thread for Android Commander:
http://forum.xda-developers.com/showthread.php?t=628138
** If you using Win7/Vista run Program as Administrator or disable UAC, otherwise this function will fail!
Click to expand...
Click to collapse
Guess I never needed for something like this since I'm comfortable with the command line.

d01100100 said:
The FAQ thread for Android Commander:
http://forum.xda-developers.com/showthread.php?t=628138
Guess I never needed for something like this since I'm comfortable with the command line.
Click to expand...
Click to collapse
I am running the program with both UAC disabled, and running as administrator and still the program does not recognize as root. I am only worried not just about Android Commander, but the possibility for functionality of other programs that require root as well.

Type adb shell
You'll see '$' as your prompt, type 'su'
$ su
You'll see '#' as your prompt, type 'id'
# id
uid=0(root) gid=0(root)
That means you have root.
Further proof you can remount /system from ro to rw.
You have root, Android Commander isn't the standard to judge whether your root is working correctly. Just a cursory glance at the app thread, it requires quite a bit of finesse to get working and it's touchy about which rom you're using. If yours doesn't work and you've actually followed the directions, send the developer your logs in the proper thread.

Why not just download the app Terminal Emulator and just type "su".... you'll either get the # or Permission Denied.
Based off everything you said, yes, you have root... ^ easiest way to test though. No need to deal with adb.

s-off but not super user acces!? help please :)

hey well i got to this point :
# # /data/local/tmp/root
Click to expand...
Click to collapse
anyhow when i run this it says:
cp: can't stat '/sdcard/superuser.apk': no such file or directory
then is the same but with su
Click to expand...
Click to collapse
i went ahead and put sync anyhow and when i restart and run 'su' but is says: unknown user root
any ideas what i did wrong? :/
oh and btw somehow i have S-off...
i followed each step, but i just notices this... for some reason it wont let me push superuser.apk or su, all of the other files can be pushed... any ideas?

no one?

http://www.youtube.com/watch?v=tU9zn_BEth4 i did that way and it works for me.

but i have s-off i supposed to be rooted already but i do not have super user powers... what do i do

Did you copy the Superuser.apk file to the root of your SDcard?

yes i did, and su too and now when i put su on my phone it says unknown user root :/
i can get temporal rooting tough.

Use visionary r13 ... had same issue... worked for me
Get it from pauls visionary thread on Modaco.
Sent from my HTC Vision using XDA App

i had the same situation with u few days ago. just follow http://forum.xda-developers.com/showthread.php?t=834228 and u only need do the temp root part.
Delete visionary and superuser first, install terminal emulator from market.
on you pc:
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
Then on you G2, open a terminal emulator
Launch Terminal Emulator---/data/local/tmp/rage----Wait for the message: "Forked #### childs."------Menu > Reset Term - Terminal Emulator will exit.-----Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell----- run the /data/local/tmp/root script here.---sync.
In the last step, u can find the origin thread dose not let u do this. but, if you've got s-off, trust me, just do the last step "/data/local/tmp/root", and when u see a feedback "****files exist",then "sync",

I got s-off, flashed clockwork recovery and baconbits
setcpu is also working
but when I try typed su then reboot in terminal
it says not permitted
and when I want to get rid of the bloatware ie Finance
root explorer refuses to switch to r/w in data folder
any suggestions

u can also do what i suggested in the 8th floor.

o>c said:
I got s-off, flashed clockwork recovery and baconbits
setcpu is also working
but when I try typed su then reboot in terminal
it says not permitted
and when I want to get rid of the bloatware ie Finance
root explorer refuses to switch to r/w in data folder
any suggestions
Click to expand...
Click to collapse
r u rspt in Gfan? since u can read chinese, just look at here. http://www.hiapk.com/thread-631413-1-3.html
I made this thread to help solve such problem.

After I got S-off, I didn't have root either. I just jumped on visionary (made sure run on boot wasn't checked), clicked root now. And boom, that was it. Then I deleted visionary and I've had root ever since...

[Q] Su: Permission Denied

i cant enable superuser..
i followed the instruction from
link = wiki.cyanogenmod.com/index.php?title=HTC_Tattoo:_Full_Update_Guide
and when im installing the clockworkmod,
adb shell
$ su
$ su: permission denied
Someone please help me..
this is my first time flashing,
i already read lots of forum, but they doesnt help..
uhm, btw there is no pop up that says "allow" when i type $ su and adb shell..

Are you referring to this? Did you successfully push image to /data/local/bin
adb push flash_image /data/local/bin/
adb shell
su
cd /data/local/bin/
chmod 755 flash_image
flash_image recovery /sdcard/recovery-clockwork-3.0.0.6-click.img

androidcues said:
Are you referring to this? Did you successfully push image to /data/local/bin
adb push flash_image /data/local/bin/
adb shell
su
cd /data/local/bin/
chmod 755 flash_image
flash_image recovery /sdcard/recovery-clockwork-3.0.0.6-click.img
Click to expand...
Click to collapse
yes i successfully push image.
i took a screenshot.
look.
i544.photobucket.com/albums/hh334/yanyan4u2008/Supermissiondenied.jpg
(can't post a image link because im still new in here)
but still, super user denied.

Im sure youve tried stuff -- did you try clearing superuser cache -- refresh the slate and confirmed you did not miss the SU popup? just be sure the screen is on and look for it like 2 seconds after you hit enter after "adb shell"

yanyan4u2008 said:
i cant enable superuser..
i followed the instruction from
link = wiki.cyanogenmod.com/index.php?title=HTC_Tattoo:_Full_Update_Guide
Click to expand...
Click to collapse
The cyanogenmod update guide assumes that you have a rom with tattoo-hack loaded, and the path to su is not set.
Look in this post:
http://forum.xda-developers.com/showthread.php?t=716282
in the sections
1.3 Tools you need
1.5 The manual way (recommended by the author)
2.3 How to flash/tools needed
Do the steps in 1.5, use the rom image and recovery from cyanogenmods wiki, in 2.3, do the second line, for flashing recovery. After that you can flash cyanogenMod from the recovery menu (Accessed by booting to recovery by holding home+power)
regards

T.I.A.
Thanks in advance, although i haven't tried it already.
I'll try it maybe on Wednesday..
Hope to flash the CyanogenMod 7.0.0-RC1.7003 2.3.3 Gingerbread..
More powers to all of you guys, keep up the good work!

finnk said:
The cyanogenmod update guide assumes that you have a rom with tattoo-hack loaded, and the path to su is not set.
Look in this post:
http://forum.xda-developers.com/showthread.php?t=716282
in the sections
1.3 Tools you need
1.5 The manual way (recommended by the author)
2.3 How to flash/tools needed
Do the steps in 1.5, use the rom image and recovery from cyanogenmods wiki, in 2.3, do the second line, for flashing recovery. After that you can flash cyanogenMod from the recovery menu (Accessed by booting to recovery by holding home+power)
regards
Click to expand...
Click to collapse
works for me

it worked for me too

Guide
Works for me too
im currently running Gingerbread, thanks!

yanyan4u2008 said:
Works for me too
im currently running Gingerbread, thanks!
Click to expand...
Click to collapse
Glad to help Credit goes to TheSSJ who made the guide

[q] help needed on 6.2.1

Hi all,
I got my KF few days back, Rooted it, before I could install the android market, got forced update to 6.2.1. 2 days ago saw this new root method using BurritoRoot. Tried rooting it, seems successful, however, now when I arrived at the home page, I cant even open the Superuser app at all. It goes the same for the Root Explorer - prompting:
"Root Explorer has not yet managed to obtain root access. Because of issues with Superuser, this often happens the first time the app is run but is usually fine from then on. Click ok and restart the app and try again. Make sure u respond correctly to the Superuser prompt." Then it comes with a force close.
Seriously I do not know whats wrong with it, now i cant even use the root explorer for me to install Android Market.
Anybody can help me with it?
Million Thanks.

did you use the superuser-2.apk ?
http://forum.xda-developers.com/showthread.php?p=20645033&highlight=superuser-2+apk#post20645033

b63 said:
did you use the superuser-2.apk ?
http://forum.xda-developers.com/showthread.php?p=20645033&highlight=superuser-2+apk#post20645033
Click to expand...
Click to collapse
Im using the ROOT INSTALL - Method 1 and I downloaded the file from Rootzwiki, apparently the file is named "com.noshufou.android.su-1.apk". and I used the following commands:
adb root
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb install com.noshufou.android.su-1.apk
adb reboot
So which means I should use the Superuser -2.apk instead?
What should I do now? Download the Superuser-2 file and repeat the whole process again???
thanks.

yes - the new version seems to be the only one working with burritoroot
consider to use KFU to make things easier:
http://forum.xda-developers.com/showthread.php?t=1399889
should be option 2 (permanent root with superuser)