ADB Question

kumite2010

Senior Member
Dec 12, 2010
147
33
0
San Antonio, TX
So I 'm getting brave and decided I want to learn more about modding so that means I need to know at least the most basic of ADB commands.

Well I set up the Android SDK several weeks ago and to my best knowledge it was/is working i.e. from the command window (I'm using Win 7 so I use Shift-Right click to access in the Android sdk tools folder) I can type

adb devices

and my phone shows up.

From there I can type

adb shell

Now here is where it gets wonky

I can't use any adb commands or else I'll get an
"adb: not found" error

I can use the -ls command and a2sdcheck commands without any issues. I can even use the reboot and reboot recovery commands ONCE I don't use ADB in front of it.

So simple commands such as adb push/pull is off limits.

I have also tried in recovery mode but the same thing happens.

I'm sure I'm just missing something small but this is turning out to be really frustrating

And yes I do connect with Charge Only and USB debugging is checked.

Thanks in advance for any help


Sent from my PC36100 using XDA App
 

kumite2010

Senior Member
Dec 12, 2010
147
33
0
San Antonio, TX
I just read the the SU log and didn't see a request resembling anything from adb or my computer. I also didn't notice a prompt to do so but wasn't really paying attention. I need to check on that but if someone else can clarify or tell me how to grant access that would be great. Thx for the response

Sent from my PC36100 using XDA App
 

kumite2010

Senior Member
Dec 12, 2010
147
33
0
San Antonio, TX
Reconnected my phone and typed adb shell and there was no prompt for SU permissions. I'm thinking this may not be applicable or else you wouldn't be able to connect adb in recovery mode right?

Sent from my PC36100 using XDA App
 

kumite2010

Senior Member
Dec 12, 2010
147
33
0
San Antonio, TX
Thx pulsar for the move. Sorry about that.

Housry thx for all your input.

I did read that link before and there was a link that confirmed that my ADB is set up correctly.

At the very first cmd prompt I can do adb devices and see my phone.
Then I can type adb shell and I get the # prompt
From there I can't issue anymore adb commands or else I get "adb: not found" error

I can issue reboot or reboot recovery commands BUT without adb in front of it and my phone will respond accordingly.

I can use the ls commands and search the subdirectories. Pushboot even works when I need to change my bootanimations. All this leads me to believe that adb is indeed set up correctly including the drivers so why doesn't the other adb commands work?!

This is really frustrating because I can't even begin to experiment with ADB if I can't get the most basic commands to function.

I know it's probably something small I'm missing and I hope someone will be able to point me in the right directions. Thanks again

Who knows, maybe this is a good thing. I might be able to get in all kind of trouble with my phone otherwise.
 

dkdude36

Senior Member
Aug 5, 2010
3,924
705
0
los angeles
ok, you are making a simple yet solvable mistake:

once you type adb shell, you are inside the phone's linux terminal. of course, your phone doesnt have adb in it. a shell is a great tool, and is used very, very often to diagnose problems, make stuff, incorperate stuff, test stuff. if you are in a shell, just type

exit

to get back out. then your adb commands should work.