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!
I downloaded this for tethering but whenever I click on the adb program the window doesnt stay up, it just flashes and dissapears. My question is how do I change ports using this to tether via azlink or tetherbot?
Little help?
You don't click on it. It's a command line utility. You have to drop to the faux DOS prompt.
Start > Run > Type "cmd", hit enter > cd to the sdk\tools\ directory > type "adb ...." etc.
Ok I got the android sdk file on my desktop now for tethering how do I run a cd command to access it.
I'm running windows 7 x64 and i'm trying to run "nandroid-mobile.sh restore" on an EVO 4g via adb, but adb isn't working and never has on my computer. I believe i've downloaded and installed all the required programs for adb. am I missing something or should I use an xp desktop as my adb repair station?
edit: when trying to run adb from the sdk/tools directory it just opens and closes a command prompt.
edit 2 (resolution): right click inside sdk/tools folder, click "open command prompt here"
So basicly im trying to follow a tutorial to get my screen working in ubuntu touch, which involves using adb shell, nano to modify a file.
the little tutorial goes like this:
thecosmicfrog said:
Sure thing. Boot up your device, then plug in a USB cable. Open a terminal and run "adb devices". Make sure that a device shows up. If not, unplug and plug in again. I find that it never works the first time for me.
Next, run "adb shell". This will connect you to your phone and open a shell session on it. Open the /etc/rc.local file in a text editor using the following command:
"nano /etc/rc.local"
Scroll down to the bottom using your keyboard's arrow keys and on the line before "exit 0", insert the following:
./system/bin/sensorservice &
Save and exit the file using Ctrl+X then reboot your phone by running the command "reboot".
This should fix the black screen problems.
Click to expand...
Click to collapse
well when im in adb shell, and type nano /etc/rc.local my adb (or cmd window) screws up completely (see attachement)
what is going on and how do i fix it?
this isn't normal i think!
j
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...