• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help adb: not found

reilus

Android Enthusiast
When I am in terminal, I type su and everything goes fine. Then I type adb, and it says "adb: not found". What is going on? How can I get this thing to recognize adb?
 
When I am in terminal, I type su and everything goes fine. Then I type adb, and it says "adb: not found". What is going on? How can I get this thing to recognize adb?
I could be wrong but if your in terminal your in adb, you would not be able to do it from within itself.

I think the adb is only for when your typing commands on your computer to go into the phone thats plugged in.
 
Okay, that's all well and good, but so far the only thing the Android SDK pack seems able to do is download more files that take up more space on my HD and then anytime I run any of the tools or platform tools, it just scrolls a command prompt window for a minute that force closes.

So I downloaded a bunch of java shit and an sdk pack that does nothing but force close command prompt windows and download more files? What am I doing wrong?
 
Okay, that's all well and good, but so far the only thing the Android SDK pack seems able to do is download more files that take up more space on my HD and then anytime I run any of the tools or platform tools, it just scrolls a command prompt window for a minute that force closes.

So I downloaded a bunch of java shit and an sdk pack that does nothing but force close command prompt windows and download more files? What am I doing wrong?
I am not an expert, I just started messing around with this stuff myself.
But when you downloaded the sdk you should click on everyone of the things it wants to download and hit reject its a pain in the ass though.
You only need platform tools and sdk tools.
Then after those are downloaded you need to open command prompt, usually by going to the start menu then run then type cmd it opens the command prompt box then you will need to change directory's use the command "cd" and the location, usually it will be c:\android-sdk-windows\platform-tools
that will change your command prompt to that directory from there you type adb shell
it will change the prompt to $ then you type in su and the prompt changes to #
 
Of course! How stupid of me. Legacy applications used to do that same thing and I had to run them through the command prompt. Thank you, that works great! I have not used the command prompt for any serious work since windows XP.

I'm glad that I am getting into my phone. I finally have something to motivate me to learn programming languages and remember commands. I tried C++, Python, Java, C#, and could never stick with it because I had nothing I was passionate about programing. My phone is changing all that.

Thank you for your help. Your contribution is one of many that help keep me interested and passionate about working with my phone. Eventually, I am going to develop applications. I got a book on it. Thank you for your help. =)

I am not an expert, I just started messing around with this stuff myself.
But when you downloaded the sdk you should click on everyone of the things it wants to download and hit reject its a pain in the ass though.
You only need platform tools and sdk tools.
Then after those are downloaded you need to open command prompt, usually by going to the start menu then run then type cmd it opens the command prompt box then you will need to change directory's use the command "cd" and the location, usually it will be c:\android-sdk-windows\platform-tools
that will change your command prompt to that directory from there you type adb shell
it will change the prompt to $ then you type in su and the prompt changes to #
 
Your welcome, I made my post as simplistic as I could so if anyone that is unfamiliar with command line would have an idea. I know when I first got started I would hear go to command prompt and think what the hell is that, how do I do that.
 
I am going to include this point in any tutorials I write later. I had no idea how to get adb to work and that is necessary for a custom recovery and all the stuff I need to do to fix my phone. It's all messed up now.
 
ADB is only when you run command prompt from windows. like it was said above you have to CD into the platform-tools directory of it. and even in adb. your phone must be connected, must have USB debugging enabled, and must allow "unknown" thats adb to run as a root user.

also if you type adb shell. once it shows $ on the screen you won't be able to type "adb" into it for commands.
 
Back
Top Bottom