Database Users

~# ???

hey all
so i was one of the lucky ppl who was able to get my phone rooted in the beginning. everything worked perfect, wireless teather, adfree ...
last night i unrooted and installed the OTA then used unrevoked3 to reroot, everything went fine but now when i am in recovery if i type adb shell i get:~# and if i type su its not found in /system/bin...whats going on? i have Superuser.apk all my root aps work but i dont know what the "~#" and why i cant get into su in recovery...

ezy1022 said:
hey all
so i was one of the lucky ppl who was able to get my phone rooted in the beginning. everything worked perfect, wireless teather, adfree ...
last night i unrooted and installed the OTA then used unrevoked3 to reroot, everything went fine but now when i am in recovery if i type adb shell i get:~# and if i type su its not found in /system/bin...whats going on? i have Superuser.apk all my root aps work but i dont know what the "~#" and why i cant get into su in recovery...
Click to expand...
Click to collapse
clockworkmod recovery is root by default, there is no su cause you don't need it. # = su prompt versus $ = user prompt...

Shadowmite said:
clockworkmod recovery is root by default, there is no su cause you don't need it. # = su prompt versus $ = user prompt...
Click to expand...
Click to collapse
So all is good?

Yes....all is good. Reported.

I'm not issuing warnings yet for questions posted in development which may fall under that scope. I have requested a Q&A sub-forum be created for DI. We'll see how that pans out. Until then, please post questions in the thread where you believe your issue is coming from. Otherwise, please post questions in the DI/General sub-forum until a Q&A forum is created. Thanks!

ezy1022 said:
hey all
so i was one of the lucky ppl who was able to get my phone rooted in the beginning. everything worked perfect, wireless teather, adfree ...
last night i unrooted and installed the OTA then used unrevoked3 to reroot, everything went fine but now when i am in recovery if i type adb shell i get:~# and if i type su its not found in /system/bin...whats going on? i have Superuser.apk all my root aps work but i dont know what the "~#" and why i cant get into su in recovery...
Click to expand...
Click to collapse
i have that problem right now. i have the original root(via loop.bat) in place, nothing else. i get the symbol "~#" too when i try to enter the adb shell while in recovery. adb devices show that my phone is attached and i am able to execute most commands. but there are some commands like "cd" that only work in the shell.
so we are going to need to resolve this eventually.
yes, you do not need su in recovery but you will need adb shell.
if there's anyone out there who can help us with this "~#" when typing adb shell in recovery, it would be greatly appreciated.

If you see that then that means you are using adb shell. No need for Su, but if you're removing apps etc mount the /system in the partitions menu of clockworkmod. Then cd /system/app to edit your apps.
Sent from my ADR6300 using XDA App

Adb remount help

When i try to do a adb remount i get operation not permitted.

It looks like you dunt have superuser
Sent from my DROID2 using Tapatalk

See if your phone is asking to allow superuser permission. It does not stay on screen very long, so just glance at it and see if it pops up and then push the grant permission button.

i got it. i just had to put the bootstap on it.

driverx125 said:
i got it. i just had to put the bootstap on it.
Click to expand...
Click to collapse
Without bootstrap you do not have a constant root adb shell. In order to get root in adb shell, you would have to type su. Bootstrap patches adbd on the phone to allow for a constant root adb shell.

How does one get su in ADB?

I am rooted with S-OFF on the phone. But, unlike the Vibrant, adb denies me su access when I enter "su" at the $ prompt. Anyone else see this?

Once you enter ADB through the SDK tools if I remember right, just start out with the 'su' command- I just caught it a couple days ago in one of the mt4g rom threads under the android development section- maybe a search for 'su' in those threads- I can't take the time to look right now- I'm @ work

Some roms connect by default as Su over adb... if you see a $ your regular user, # is root prompt...
If you have a $ and you get denied still, go to your Su app and confirm that adb has Su permission or at least isn't denied...
Sent from my Desire HD using XDA App

ESKIMOn00b said:
Some roms connect by default as Su over adb... if you see a $ your regular user, # is root prompt...
If you have a $ and you get denied still, go to your Su app and confirm that adb has Su permission or at least isn't denied...
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Thanks for the replies so far. ADB is not listed in the su app. How do I add that? Wouldn't it be the daemon that needs root access?
EDIT: Got it. Duh! It would help if I look at the phone while requesting root access. Thanks!

yes it should.... i was wanting you to check that it was not in there with specific permission to deny...
youll need to hit allow on the phone just like any SU call BTW...

Editing my post while you posted. Thanks!

Confused me too the first time.... I got it figured out pretty quick tho....
Give a look at wireless adb its super sweet! Market wireless adb...
Sent from my Desire HD using XDA App

Guys need help adb is driving me crazy!!!

Right guys,
Im trying to list the apk's in /data/app through adb so i can pull one of them!
I keep getting an error opendir failed permission denied!
BUT!!! I can get into /system/app fine with no problems.
Im running darkyy's 9.5 with his new kernel. Could this be a problem?
Its strange how i can get in system/app but not data/app
I have never had this problem in the past.
Code:
C:\Users\Paul>cd c:\AndroidSDK\platform-tools
c:\AndroidSDK\platform-tools>adb shell ls /data/app
opendir failed, Permission denied
c:\AndroidSDK\platform-tools>

zolah said:
Right guys,
Im trying to list the apk's in /data/app through adb so i can pull one of them!
I keep getting an error opendir failed permission denied!
BUT!!! I can get into /system/app fine with no problems.
Im running darkyy's 9.5 with his new kernel. Could this be a problem?
Its strange how i can get in system/app but not data/app
I have never had this problem in the past.
Code:
C:\Users\Paul>cd c:\AndroidSDK\platform-tools
c:\AndroidSDK\platform-tools>adb shell ls /data/app
opendir failed, Permission denied
c:\AndroidSDK\platform-tools>
Click to expand...
Click to collapse
Either :
adb root
adb shell ls /data/app
or
adb shell
su
ls /data/app
Reason /system is accessible is because system is ro by default. So they allow you to browse it knowing u won't be able to do anything w/o root. Whereas /data is rw and hence they restrict you, unless you have root.
Fyi : Wrong section to ask questions.

Daneshm90 said:
Either :
adb root
adb shell ls /data/app
or
adb shell
su
ls /data/app
Reason /system is accessible is because system is ro by default. So they allow you to browse it knowing u won't be able to do anything w/o root. Whereas /data is rw and hence they restrict you, unless you have root.
Fyi : Wrong section to ask questions.
Click to expand...
Click to collapse
I am rooted with superuser...

zolah said:
I am rooted with superuser...
Click to expand...
Click to collapse
The default superuser timeout is 10 secs, either increase it or keep looking at your screen.
PS : Have you tried a an app called Mount R/W? works great.

zolah said:
I am rooted with superuser...
Click to expand...
Click to collapse
Im confused, what are you implying by that response ?
To me that statement was equivalent to "The sky is blue"

Daneshm90 said:
Im confused, what are you implying by that response ?
To me that statement was equivalent to "The sky is blue"
Click to expand...
Click to collapse
..... sigh
You was telling me that i have to have root and su to be able to poke around in /data... i said i am rooted with su obviously as im on custom rom...

zolah said:
..... sigh
You was telling me that i have to have root and su to be able to poke around in /data... i said i am rooted with su obviously as im on custom rom...
Click to expand...
Click to collapse
Yes, but by default, if u dont run
adb root....ur not running the shell in root mode
Also on most roms if u run :
adb shel
u'll see $......
when u type su
u see #
So to enter # mode u need root but still need to execute either adb root or adb shell n then su.
Hope that clears it.

install android commander and forget about command line for simple listing and coping tasks
Sent from my GT-I9000 using Tapatalk

This is what i get ...
Code:
C:\Users\Paul>cd c:\AndroidSDK\platform-tools
c:\AndroidSDK\platform-tools>adb root
adbd cannot run as root in production builds
c:\AndroidSDK\platform-tools>adb shell
/ $ su
su
ls /data/app
ls /data/app
Permission denied
/ $ ls /data/app
opendir failed, Permission denied
/ $

zolah said:
This is what i get ...
Code:
C:\Users\Paul>cd c:\AndroidSDK\platform-tools
c:\AndroidSDK\platform-tools>adb root
adbd cannot run as root in production builds
c:\AndroidSDK\platform-tools>adb shell
/ $ su
su
ls /data/app
ls /data/app
Permission denied
/ $ ls /data/app
opendir failed, Permission denied
/ $
Click to expand...
Click to collapse
I dont see a # anywhere in there...
Are u accepting the dialog on ur phone when u type su ?
There shud b a popup on ur phone once u do that.

Am I being daft or is root explorer 10 times easier than using adb for this?
Sent from my GT-I9000 using XDA Premium App

woolf clubs said:
Am I being daft or is root explorer 10 times easier than using adb for this?
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Maybe he's trying to learn how to navigate using adb. Very useful skillset to acquire imho.
But yes for general purpose, a gui is better.

the plot thickens...
Ill fill you guys in from the start in a short story..
Updated to darkyy v9.5 from v9.3
I thought the phone went a bit funny when it loaded the first boot as on the boot animation it vibrated like crazy and the animation started again as it was going to loop but then the phone loaded...
Been using the phone a few days and everything fine and wanted to pull an app from /data/app
All the above stuff happened and it wouldnt let me.
I thought something wasnt right so i took out the battery for a few minutes and put it back in and went into download mode and plugged my phone into computer to see of odin would still recognise it ok...
My windows vista computer started installing device drivers???? ive had this phone 7 months and plugged in about 100,000,000 times lol
Odin recognised my phone so i rebooted and tried again and now it works fine...
Something weird going on there which is concerning me with it installing new drivers...
This is what i get now and used to get before when i used adb...
Code:
C:\Users\Paul>cd c:\AndroidSDK\platform-tools
c:\AndroidSDK\platform-tools>adb shell ls /data/app
FasterFix.apk
Vending.apk
com.adobe.flashplayer-1.apk
com.android.wallpapersetandsave-1.apk
com.darkyrom.darkyconfig-1.apk
com.ebproductions.android.launcher-1.apk
com.google.maps.apk
com.google.youtube.apk
org.projectvoodoo.controlapp-1.apk
circular_battery_indicator.apk
com.androidapps.spareparts.apk
com.haxor-1.apk
com.sgsinfo.apk
com.sgstoolbox.apk
de.Fr4gg0r.SGS.Tools-1.apk
neldar.bln.control.free-1.apk
ymst.android.homeswitcherfroyo-1.apk
com.android.vending-1.apk
com.handcent.nextsms-1.apk
com.keramidas.TitaniumBackup-1.apk
com.pants.sc.lite-1.apk
com.navigon.navigator_select-1.apk
org.adwfreak.launcher-1.apk
com.speedsoftware.rootexplorer-1.apk
com.anddoes.fancywidget.pro-1.apk
adw.creativethemez.gingerbread-1.apk
com.quoord.tapatalkxda.activity-1.apk
c:\AndroidSDK\platform-tools>
Thank you for all the responses by the way...
Any one have any idea what could have happened?

woolf clubs said:
Am I being daft or is root explorer 10 times easier than using adb for this?
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
For what i was doing no because i wanted to just quickly pull an apk, decompile it and edit something and compile it and push it back...
Daneshm90 said:
Maybe he's trying to learn how to navigate using adb. Very useful skillset to acquire imho.
But yes for general purpose, a gui is better.
Click to expand...
Click to collapse
I know how to navigate with adb very well. I just couldnt figure out why i was being blocked from entering /data/app...
I even have a video tutorial in my sig that i made showing how to use adb and its commands...
Seems a quick battery pull did the trick although i still now dont know why new drivers where auto installed on reboot to my pc

Cant reboot via terminal.

Hey gius Im trying to reboot via terminal but I cant seem to get it to work. Keep getting "Nor premited!" error.
I tried with both commands and am using a rooted G2 with stock rom.
su reboot - same error
su reboot now- same error.
any ideas? I know there are apps to do it but why is it not working via terminal?

Any reason why you can't just hold the button in and press reboot?

$ su -
# shutdown -r now
it shoulda outta do it then
for just turning off:
# shutdown -h now

ohgood said:
$ su -
# shutdown -r now
it shoulda outta do it then
for just turning off:
# shutdown -h now
Click to expand...
Click to collapse
Hmm Tried that right now and it says shutdown: not found.

I'm getting the same error! I only tried terminal when Gscript Lite gave me a "not permited". Don't know if it's related, but terminal always starts with $ rather than #. The weirdest part is that it DID work through ADB.
I'm S-OFF, root verified. Has anyone else seen this? I've been searching the forums for a while now...

Try
$ su
# busybox killall system_server
Sent from my HTC Vision using Tapatalk

I get busybox: not found, but since I initially thought it was a busybox issue, I have already updated busybox. Per Titanium Backup, I have version 1.18.4-Titanium. Could it be the titanium busybox?
PanCubano said:
Try
$ su
# busybox killall system_server
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse

Having a similar problem with rebooting from terminal "not permitted", I am using Virtuous Unity,and my phone is rooted etc,anybody having any joy getting reboot from terminal working?double checked busybox permissions and are RWX so whats going on???????????????????

Ok restored my nandroid backup of CM7 and reboot from terminal works so for the problem is connected to Virtuous Unity.

got it ! command is:
$su
#reboot -f
hay presto!!!!!!!
EDIT BUT when using a gscripts reboot doesnt work???????????
I have to use the command busybox killall system_server in the script????
I dont get it,what is the problem !!!!!!!!!!!!!!!!

xsteven77x said:
Any reason why you can't just hold the button in and press reboot?
Click to expand...
Click to collapse
This.
Sent from Space using Tapatalk Pro

I know I could, just trying to understand the android system,how it works and why the reboot command works on CM 7 but not on Virtuous Unity, the search for a solution continues...........................

bombadier said:
I know I could, just trying to understand the android system,how it works and why the reboot command works on CM 7 but not on Virtuous Unity, the search for a solution continues...........................
Click to expand...
Click to collapse
I had the same problem on rooted stock, and it has since gone away since I put on CM7. The reason is that it is not just reboot that didn't work. Almost no scripts would run either, and those can be quite helpful. I believe it's a symptom of something larger, but I can't quite place my finger on what.

mjasmin said:
I had the same problem on rooted stock, and it has since gone away since I put on CM7. The reason is that it is not just reboot that didn't work. Almost no scripts would run either, and those can be quite helpful. I believe it's a symptom of something larger, but I can't quite place my finger on what.
Click to expand...
Click to collapse
I can get reboot -f which works but I have to use busybox killall_server to get it work from a script,have tried a few things but literature on the subject is pretty sparse,its not so important but would still like to understand the whole process, but I seem to be in the minority trying to solve this.......
Why I have to use reboot -f on Unity where reboot will do on CM is a mystery,have found a file that seems to define functions on Unity(virtuous-functions.sh), have tried adding REBOOT="$BUSYBOX reboot" to this but doesn't help.
reboot -f it is then!