Database Users

Remove CityID after root and recovery flash

So I've rooted and installed the new recovery on my incredible. I want to remove CityID now, forgot to after root. When I launch recovery and run adb devices it shows my device. I then run adb shell, immediately getting the # for su (instead of the $ prompt for non su access). I execute /system/bin/rm /system/app/CityID.apk as instructed by the wiki and get /sbin/sh: /system/bin/rm: not found. I browse to /system/bin and do a listing and see nothing. So am I doing something wrong?
**EDIT**
Forgive my ignorance, but I forgot to mount system in the partitions menu of recovery. Doubtful this would be of any help to anyone, but there ya go.

Also in the How To:
StirCwazy said:
So I've rooted and installed the new recovery on my incredible. I want to remove CityID now, forgot to after root. When I launch recovery and run adb devices it shows my device. I then run adb shell, immediately getting the # for su (instead of the $ prompt for non su access). I execute /system/bin/rm /system/app/CityID.apk as instructed by the wiki and get /sbin/sh: /system/bin/rm: not found. I browse to /system/bin and do a listing and see nothing. So am I doing something wrong?
**EDIT**
Forgive my ignorance, but I forgot to mount system in the partitions menu of recovery. Doubtful this would be of any help to anyone, but there ya go.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=709220 - It's a few posts down, but will update first post later today.

[Q] Rooted but adb says I am not?

I searched around several threads and saw a few people with the same issue but no fixes.
I rooted my phone using this and it worked great.
I then installed clockwork manager from here and then installed the clockwork recovery and made my nandroid.
So far so good.
I booted up and then checked the terminal emulator app i had installed and did:
Code:
$su
and got
Code:
#
So, all good.
I then went to remove some of the bloatware by using adb.
When I do adb shell I get the $ prompt.
I type in "su" without quotes and after a few seconds i get "Permission denied".
Seems like i fudged something somewhere but I am not sure what.
Anyone able to offer some constructive help?

Make sure your phone is unlocked when you type su in adb shell, and a superuser permission should pop up.

many thanks for that!
i have been on a rooted G1 with CM for so long that i forgot to even look at my phone when i "adb shell...su" into it =)
did it just now and looked at the phone and the superuser permissions window came up. all set.
thanks again!

(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?

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] ADB "Permission Denied"

hey guys need help so my Mytouch 4G updated and perm rooted, and i keeep gettin gthe permission denied everytime i try and execute a command thru adb thru my pc or on the Terminal Emulator. Did something not go thru on root or am i missing something simple? any help would be greatly appreciated. Thanks

mrpanic7 said:
hey guys need help so my Mytouch 4G updated and perm rooted, and i keeep gettin gthe permission denied everytime i try and execute a command thru adb thru my pc or on the Terminal Emulator. Did something not go thru on root or am i missing something simple? any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
You may have to run visionary and reboot a few more times to make root privileges stick.
My MyGlacier 4G MINE!!!

Try this:
: adb shell (this should give $)
:$ su (next line type su, this should give you prompt on Super user to allow permission)
:# ( once you get this your good)
Sent from my HTC Glacier using Tapatalk

Try to install visionary and then re install open click temp root then permoot super user should ask to approve click yes. After that restart
Sent from my HTC Glacier using XDA App

Please post questions in Q&A forum. Thank you

ok everytime i try adb shell in terminal emulator it says the permission denied, im gonna try the first reply again and then see....any other ideas?

also guys, when i try and run visionary again it says your device is already rooted, along with when i type su in TE, it gives # with superuser permissions quote showing on bottom of screen, but i was trying to run adb commands from pc or from te and they still show permission denied. SetCPU works.

mrpanic7 said:
also guys, when i try and run visionary again it says your device is already rooted, along with when i type su in TE, it gives # with superuser permissions quote showing on bottom of screen, but i was trying to run adb commands from pc or from te and they still show permission denied. SetCPU works.
Click to expand...
Click to collapse
Ok, go into adb shell and type su + enter. Watch your phone when you do this. Superuser should ask if you want to allow "unknown" root privileges. "unknown" is adb. Click allow and your problems should go away.
My MyGlacier 4G MINE!!!

So typing su works and the message terminal emulator is granted permissions, but then any other commands dont work
Sent via MyTouch 4G

Whats a test command I could try?
Sent via MyTouch 4G

mrpanic7 said:
So typing su works and the message terminal emulator is granted permissions, but then any other commands dont work
Sent via MyTouch 4G
Click to expand...
Click to collapse
I ran into this same issue and it drove me crazy. I would not get prompted by the phone to allow su permissions when going through ADB- kept getting "permission denied"
I did finally get SU permissions through ADB, but I dont recall exactly what I did to get prompted to allow access.
I will try to retrace what I did... believe I had ADB shell running (without su permissions "$"), but I also had terminal emulator running on my phone. I entered the su command on my phone, then I did the same from ADB shell.
Finally the phone prompted me to allow access - accepted - and no problems from that point.
Basically, I just had to keep f'n with it.

Yeah thats my problem exactly. Yeah I appreciate any assistance you can provide. I mean my pc reads my device when I adb devices command, but it wont allow nothing past that. Please keep me informed on anything I can try, also im not thag most fluent with using sdk/adb stuff so any additional info with using that is much appreciated thanks again fellow enthusiasts!
Sent via MyTouch 4G

Have you tried to bacup su, then uninstall su. Reinstall su, Then try it again. MIGHT work
Sent from my HTC Glacier using XDA App

yeah i re-installed su and didnt help, @dbiggs-what can i do thru adb to initiate the su permissions to the device like you did?

I wish I could help more specifically, but I dont remember exactly what I did that allowed me access- just kept trying
Maybe try this...(dont be offended if any of these steps are ones that you already know or have tried, I am just trying to be as thorough as I can from memory)
Open up super user, then go back to the terminal emulator and enter the "su" command to gain superuser permissions.
Plug the phone into the computer, select charge only, enter ADB through tools (probably "C:\Android\tools" if your Android folder is in the root of your harddrive).
from the prompt C:\Android\Tools, enter:
adb shell
then you will get the "$" that you mentioned.
enter the "su" command, and hopefully you will get prompted to allow superuser permissions for ADB.
I am pretty sure these are the steps that I took, just had to keep trying.
Lemme know how it works out.

I see some people here asking about getting su privileges in adb, however I do have SU and I can run su in adb shell. My problem is that I am trying to push some files and use Android Commander. I can't run "adb remount" (remount failed: Operation not permitted), I can't copy files in Android Commander (it's says that I do not have ROOT)
How can I get Read-Write in ADB ??
Edit: Oh, now I got it, I don't have root in ADB, when i type "adb root" it says "adbd cannot run as root in production builds"

Did anyone figure this out? I'm being denied on TE and PC also.

I have managed to be able to get around this issue by going into recovery mode on my phone.
If the end result that you are looking for is to adb push files, then the easier way to do this is to flash clockwork recovery to your phone, then start your phone into recovery mode, mount system and you should be able to push files no problem.
Lemke know if this helps.
Sent from my HTC Glacier using XDA App

mrpanic7 said:
hey guys need help so my Mytouch 4G updated and perm rooted, and i keeep gettin gthe permission denied everytime i try and execute a command thru adb thru my pc or on the Terminal Emulator. Did something not go thru on root or am i missing something simple? any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
I'm pretty sure your issue has nothing to do with SU access. Most likely, your phone is simply mounting as r/o (read only) when it boots up, so ADB is unable to change anything to the system folder. The easiest way to mount as r/w (Read/Write) is to go into Root Explorer and click the r/w button in the top right corner, and then go to ADB and see if it will allow you to do the same commands that it previously denied.
I have the same issue with my phone mounting as r/o by default, but I haven't been able to figure out how to automount as r/w on the MT4G. If anyone knows how, please share.

I had this same issue, on several android phones including MT4G. Here is how I fixed it.
1. Connect phone via usb (I was in "charge only" mode, not disk drive mode)
2. Open command prompt and navigate to the android tools folder
3. type "adb shell"
4. MAKE SURE YOUR PHONE SCREEN IS ON AND UNLOCKED
- The above step is very important otherwise you will not get the SU prompt
5. At the "$" prompt type "su"
6. Your phone should now display the SU screen asking you to allow the connection root access.
7. Once you allow it, you are golden.
I did this on a windows pc. Hope it helps.