Database Info

using adb

I feel like an idiot. I keep reading posts and instructions on how to use the adb/adb shell. Everything I read seems to indicate that the knowledge on how to open the adb command window is something that any idiot should be able to do... So much so, that no one explains how! I must be missing something!
I have installed eclipse and the sdk, the ADT plugin, etc. I run adb.exe and a command window flashes on my screen and immediately fades away. I can't even read what was posted in the window.
I know I am missing something but I guess I am just too inexperienced to know what that is. I can't find anything on the web that will tell me what file to open or sequence of files to open to access the adb command window.
Someone please help out a hopeless nuub!
Thanks
I am running Windows Vista 64 and have installed the 64bitUSB drivers. I can open an emulator, I can run the terminal on my G1, have installed the JK modified r30 on my phone.

add the whole path to your sdk/tools folder to your windows environment path: (right click my computer, click properties, select "advanced" select "environment variables" and look for "Path" in the bottom list, select "Path" and click "edit" then at the end of the existing path info, add a semicolon, and then paste in the complete path to your sdk/tools folder, click save, and close all the windows.
now, goto start, run, and type cmd.exe, a command line window will appear, type "adb" and it should work.
cheers,
-- michael

you can also use google to search the forum when you are looking for 3 letter terms (the forum search function is 4+ characters)
http://www.google.com/search?hl=en&q=site:http://forum.xda-developers.com/+android+adb
--M

you don't use adb by pressing adb.exe in the tools folder you use it with command prompt go to programs and to accessories and look for command prompt now you can use adb like adb remount and pull push so on with your phone connected to the pc can you see your phone in ddms you open it from the sdk tools folder where the adb.exe is and if you can use adb.exe to open command prompt it don't work for me ether

I'm guessing that when I get all the ADB info after typing "adb" in the command window that it is working correctly?

If you run adb with no args, it will simply return a short summary of available args and terminate. In Windows if the window is opened by a program using the command line rather than directly calling cmd.exe, it will automatically close when the program terminates. The solution is to use cmd and then adb from within that.

Jashsu - Thanks! that was what I needed to know! LOL I am such a noob!!!
I had access to adb all the damn time! I just didn't know it! DUH!
I now have Koush's auto rotating browser installed! AWESOME.
Thanks to all who responded! I am learning pretty quick. But, some things are just so commonly known by dev's that they just aren't explained very well.
I found a couple of books I'm going to purchase so I don't have to keep bugging all of you. But, you guys are the greatest. Thanks for the help!

[Q] Rooting?

How come nothing happens when I try to start adb?
A cmd window pops up then vanishes just as quick...

sounds like you are launching adb from explorer or run command. Open a cmd window first and navigate to adb location and run adb.

adb is launched by opening a regular cmd window, then navigate to the android sdk tools folder as such:
cd android-sdk-windows\tools
if you didn't extract it to the root of the C: drive edit the path accordingly.
if you extracted it to the root of another drive type #: (# being the drive letter) first then use cd android-sdk-windows\tools command. From there use ADB commands.

thanks.
now lets hope I don't break something!

still have so much trouble
C:\Program Files (x86)\Android\android-sdk\platform-tools is the location.
what should I type...

type cd /Program Files (x86) then type cd android-sdk\tools, then run your commands.

You can hold shift and right click the folder and go to open command window here
Sent from my LG-VM670 using Tapatalk

Having troubles with the command prompt stages of the rooting process

Hi there,
I have an HTC Magic and am trying to root it by following this guide http://forum.xda-developers.com/wiki/HTC_Sapphire_Hacking#Known_Hackable_SPL_revisions
I have the Android SDK package installed, but am having troubles getting any further because I'm having troubles with the command line prompts.
For instance, I added ;C:\AndroidSDK\tools\ to the end of the Path in my Environment Variables, just like the guide said, but I don't know if I did it correctly. When I open up the command prompt, it still gives me C:\Windows\System32> as my starting directory. What should I be seeing instead?
Also, when I type in "adb devices", it doesn't recognize the command. I'm assuming that's because I'm typing it into the wrong directory, but I don't understand how to navigate to the right one.
Any suggestions?

You need to add the path to the directory that CONTAINS the adb.exe file.
If you did it correct the command "adb" should be recognized.
You may need to restart the computer after adding the path i'm not 100% sure.
Adding something to the PATH variable does not change where you start out when you open the command prompt.

Yea that's what I did. I added ;C:\AndroidSDK\platform-tools\ (my adb file is in the platform tools folder) but when I type adb in the command line, it doesn't recognize the command.

[Resolved] ADB not recognized command Windows 8 - Help

I've been trying to get adb to work and it just will not. I've installed all the correct sdk tools, java se, and added the path environment successfully for java, but apparently not for sdk or adb. With Java I entered a "new" path JAVA_HOME then the directory, but with sdk I am getting a multitude of different responces in searches for what to place and where. I currently added "C:\Program Files (x86)\Android\android-sdk" to the end of the "path" along with several variations of this from different search results, all to no avail. I just want to open the command prompt and type adb....and have it work!! I was able to successfully connect to my device by first entering "cd C:\Program Files (x86)\Android\android-sdk\platform-tools" and then "adb devices", but no go on just "adb devices" without the entire path. Can someone please be very concise as to what I need to do here??
Edit:
Solved!!!!
I was adding a \ instead of a ; to the end of the path
Sorry for the post

annoyingduck said:
I've been trying to get adb to work and it just will not. I've installed all the correct sdk tools, java se, and added the path environment successfully for java, but apparently not for sdk or adb. With Java I entered a "new" path JAVA_HOME then the directory, but with sdk I am getting a multitude of different responces in searches for what to place and where. I currently added "C:\Program Files (x86)\Android\android-sdk" to the end of the "path" along with several variations of this from different search results, all to no avail. I just want to open the command prompt and type adb....and have it work!! I was able to successfully connect to my device by first entering "cd C:\Program Files (x86)\Android\android-sdk\platform-tools" and then "adb devices", but no go on just "adb devices" without the entire path. Can someone please be very concise as to what I need to do here??
Edit:
Solved!!!!
I was adding a \ instead of a ; to the end of the path
Sorry for the post
Click to expand...
Click to collapse
same issue. dont know what ; or / has to do with anything

Fix "unable to load" using fastboot and windows 10

I have been frustrated trying to use fastboot commands, especially the "flash" command on my windows 10 laptop. I continually got an "unable to load' message. I have reloaded the drivers manually as recommended by some, which still did not work. Well, it turns out that you need the complete path in the fastboot command line when using 10. Put your img, bin files in a folder you will be using. Open the command prompt using the windows-x keys. Select the command prompt from the menu.. It does not need to be the administrator. Use the fastbooot devices command to make sure the computer can see your device. I then issue the fastboot command I want: fastboot flash logo and then drag the file from the folder you are in and drop it on the command line. In this case I used, nowarning.bin. When it populated the complete path starting with the c: prompt shows up. Make sure there is a space before the C: and the previous command. Hit enter. I have searched everywhere and have not found an answer to this problem. I did see a video on youtube where the fellow dragged a file from the folder and dropped it in the command prompt window. So thanks to him for that simple yet effective trick.. Hopefully this will work for you if your having the same problem I had...