I am pulling my hair out. I have SDK installed and whatever I was instructed to install on SDK, for the life of me I can't get the command shell to work. When I open a command shell and type adb. I get a message 'adb' is not a recognized as an internal or external command, operable batch or program file.
My phone is plugged in debugging checked, I have it set to mass storage, not kies. What am I doing wrong.
Sorry for the noob question. I have been reading every forum I can find, every document I can find. I am trying to learn and I like to mess with my phone and should know how to use adb command shells.
Can someone tell me what I am doing wrong?
Thanks.
Rhiannon224 said:
I am pulling my hair out. I have SDK installed and whatever I was instructed to install on SDK, for the life of me I can't get the command shell to work. When I open a command shell and type adb. I get a message 'adb' is not a recognized as an internal or external command, operable batch or program file.
My phone is plugged in debugging checked, I have it set to mass storage, not kies. What am I doing wrong.
Sorry for the noob question. I have been reading every forum I can find, every document I can find. I am trying to learn and I like to mess with my phone and should know how to use adb command shells.
Can someone tell me what I am doing wrong?
Thanks.
Click to expand...
Click to collapse
PC or mac?
On a PC cd /Android/Tools then use adb commands
on a Mac: cd /Android/Tools then use ./adb then the command
PC. Thanks I will try that.
update
system cannot find the path specified
I am ready to delete everything and start over, maybe the path is wrong and I borked something in the download. There should be an Android for dummy's book or something, for us noobs.
where did you install the files? You had to download the SDK and unzip it.
Then you use a command window to change directories to where ever you installed it. Then run the commands.
If you don't know how to move around directories using DOS commands, you better find a tutorial on that first.
Your problems sound like you are not in the tools directory - CMD issues not Adroid - CMD is the windows shell btw.
alphadog00 said:
where did you install the files? You had to download the SDK and unzip it.
Then you use a command window to change directories to where ever you installed it. Then run the commands.
If you don't know how to move around directories using DOS commands, you better find a tutorial on that first.
Your problems sound like you are not in the tools directory - CMD issues not Adroid - CMD is the windows shell btw.
Click to expand...
Click to collapse
downloaded and upzipped. It's in a folder named Android, in my c;/drive. I watched a tutorial and put it where I thought I was supposed to, then I made sure to edit the path. I can undo that. I know it's a CMD issue. Great DOS commands, this is a little over my head.
I's probably easier for me to delete everything and start over.
Is there an ADB for dummies or anything. I find them for other devices not Captivate?
if you change directories to the tools directory, do you see adb.exe listed? I am not sure which tutorial you used, but there is no reason to edit the path if you change directly into the android sdk/tools directory.
In a CMD window, change to the tools directory and do a DIR and see if the first file is adb.exe
Deleting and starting over is not going to change things at this point. Also ADB is a command that works the same regardless of which phone you have. The only things that are different is if you can mount the system partition - depends on your kernel - is it custom. Not phone dependent though.
alphadog00 said:
if you change directories to the tools directory, do you see adb.exe listed? I am not sure which tutorial you used, but there is no reason to edit the path if you change directly into the android sdk/tools directory.
In a CMD window, change to the tools directory and do a DIR and see if the first file is adb.exe
Deleting and starting over is not going to change things at this point. Also ADB is a command that works the same regardless of which phone you have. The only things that are different is if you can mount the system partition - depends on your kernel - is it custom. Not phone dependent though.
Click to expand...
Click to collapse
Thanks I did this and no it isn't listed. the Android folder is, that is where I extracted all the files. Should I move from the folder. After extracting the files did I need to install anything from it?
Rhiannon224 said:
Thanks I did this and no it isn't listed. the Android folder is, that is where I extracted all the files. Should I move from the folder. After extracting the files did I need to install anything from it?
Click to expand...
Click to collapse
You should have extracted everything. You should have a folder that extracted:
android-sdk-windows and in that a tools folder. In the tools folder is ADB.exe
It is one big zip file - nothing to install - just unzip where you want it.
hold shift and then right click on that tools folder(wherever you put it), select open command window here from the menu, then type adb to make sure it worked
Kagoshema said:
hold shift and then right click on that tools folder(wherever you put it), select open command window here from the menu, then type adb to make sure it worked
Click to expand...
Click to collapse
Thank you. That did the trick. It is there and it worked. So I am guessing that when I want to open a command shell and use ADB this is how I will be able to do it. Thank you so much for all of your help everyone.
I am very new to Android and smart phones, 7 weeks now and I am trying to learn as much as I can and I try to find the information without asking too many questions.
Last night with SRE and it's sleeping death made me realize that I need to know how to use ADB and a command shell should things go wrong.
Again, thanks to everyone for the help.
This is some easy stuff, but I thought I'd share one of my old "tricks" to work faster for the 'lazy' people .
So let's say if you work a lot with adb within the SDK tools folder this might come in handy if you currently cd to the folder each time you open a command prompt window.
Just download and extract the batch file to your desktop or where ever you like and open it with notepad then change the directory in the last line after cd.
The first lines makes sure the command prompt window stays open after you execute the batch file so you can start inputting. So don't worry, it does not include harmful codes for those who don't know batch commands.
Hope you will find this useful.
You could always copy "adb.exe", "AdbWinApi.dll", and "AdbWinUsbApi.dll" to "C:\windows\system32" and then you can use adb from any folder in command prompt. If I'm using any adb commands use them straight from the windows 7 search/run box on the start menu.
I am trying to get adb to work. I am doing it on a x64 vista system and I think I am getting the Path wrong. I am trying to get it to run like the page says to initialize it to read the device so I know it is working.
I can't get it to start from command prompt with out navigating to the directory it resides in. Is that right for the newer versions of ADB or am I just a monkey and can't figure out simple pathing?
I just made a folder in my c drive called ADB, and placed the entire folder with adb and the dll files required in it, along with superuser, busybox, etc.
Right click on command prompt and run as administrator.
once at system32 type: cd C:\ADB
then you will have navigated to the folder containing your ADB files.
your command prompt should now read: C:\ADB
then you can type: adb devices
it will say something about starting daemon services, and then list attached devices.
you are free to proceed with whatever instruction or operation you are doing after that.
also, make sure you have the drivers for the phone installed, or your computer wont recognize the android debugging bridge.
LowRentTechGuy said:
I am trying to get adb to work. I am doing it on a x64 vista system and I think I am getting the Path wrong. I am trying to get it to run like the page says to initialize it to read the device so I know it is working.
I can't get it to start from command prompt with out navigating to the directory it resides in. Is that right for the newer versions of ADB or am I just a monkey and can't figure out simple pathing?
Click to expand...
Click to collapse
Android Development is not for questions or Problems
Please post in the correct Forums
Moving to General
Well thanks for moving it, I will keep a closer eye on which forum I am browsing when I post.
Sent from my SCH-I510 using Tapatalk
I am new to all this and completely lost. I am trying to be able to access adb shell through command prompt. I have done everything here:
http://forum.xda-developers.com/showthread.php?t=500196
And it still doesn't work. I'm lost. I'm not sure where it was downloaded to. I can find it in my program files under Android. But when I try to put C:\android... it doesn't actually come up. But if I go to explore and go find it, it is... so I think maybe the path isn't set up the same or something. i dunno. I dont get it lol.
Any help would be awesome!
Thanks,
Kimberly.
Hi,
So after you downloaded the zip file did you unzip / install it? as you will need to unzip the file. So for example you may have downloaded it to your download folder so double click the zip and unzip. The you should see a Android folder like "android-sdk-windows".
Once you know where it is you can then either add this to the envrioment varables or could can navigate to the adb program via the command prompt and run it there.
I.e. cd C:\Users\yourname\Downloads\android-sdk-windows\
then type adb shell
There is a guide here: - http://developer.android.com/sdk/installing.html
So have a look in your C drive (Go to My computer, C drive) then look for a folder called "android-sdk-windows"
C:\android-sdk-windows
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 I Follow this guide but cant get to Command Prompt... I Do Shift-Right Clic and Nothing. I Have a Windows XP.
First stop creating new threads for every issue you have please. Just use the thread you've already started or lumins thread that you linked to.
Second make sure your just in the folder when you do this. Nothing in the folder should be selected.
Click start
Click run
Type cmd or command.
Now in widows xp you cant open a command prompt from within a folder so you will need to change directories to the folder you have heimdall in.
Normally it will be something like this
Code:
cd c:/computer/username/downloads