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"
Related
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!
Guys I need help, I for the life of me cant get that thing to work. Its installed in my programs files (x86), that is where it was put when I hit install.
I got into command and get to the C:\Program File (X86)\Android\android-sdk>tools
I get tools is not recognized as an internal or external command, operable program or batch file.
I type in adb devices and I get the same error.
Any ideas or can anyone help me. I never need to do the androidsdk for the captivate, but it looks like I need it for the inspire.
tools is another directory
so add /tools to your command
adb should work from there
You need to unzip it to your c drive and then open up cmd and type something along the lines of
cd c:/sdk /tools
The file names have to match it you will get that error
sent from my HTC Inspired Desire HD 4G
milleirish said:
Guys I need help, I for the life of me cant get that thing to work. Its installed in my programs files (x86), that is where it was put when I hit install.
I got into command and get to the C:\Program File (X86)\Android\android-sdk>tools
I get tools is not recognized as an internal or external command, operable program or batch file.
I type in adb devices and I get the same error.
Any ideas or can anyone help me. I never need to do the androidsdk for the captivate, but it looks like I need it for the inspire.
Click to expand...
Click to collapse
Change name to androidsdk. Then run as administration for windows. Type cd c:\androidsdk/tools
Inspire 4G / Desire HD
Depending on the country
it is unzipped, and installed. I will try those commands thats
Yea - so you'd wanna run a command prompt as admin, then type:
cd c:\program file (x86)\android\android-sdk\tools
hit enter
This will put you in the tools directory. NOTE: If you've installed the newest version of SDK, adb is no longer in tools, it's in platform-tools, so you'd want to navigate to:
cd c:\program file (x86)\android\android-sdk\platform-tools
hit enter
adb devices
hit enter
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
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
Description
After always having to search for the latest versions of Android's ADB and Fastboot tools instead of downloading the whole Android SDK for just 1 mb in a few files, I decided to make my own MSI installer using the latest versions of ADB and Fastboot.
You can install it wherever you want and it will work from any path in the command prompt. The installer will append the installation folder location to the system PATH variable, allowing you to run ADB or Fastboot without you having to change the command prompt path to where they are installed.
This installer is 32-bit and 64-bit compatible.
Usage
The default installation path is C:\ADB so you can easily add your flashable files in there.
After installing Android ADB Fastboot you can open a command prompt and type adb or fastboot commands right away, you don't need to change paths. Keep in mind that you need admin privileges, though.
To open a command prompt with administrator rights on Windows 8, just right click on the bottom left corner of the screen or use the Win+X shortcut and then click on Command Prompt (Admin).
Click to expand...
Click to collapse
If you have Windows 7 or Vista, the quickest way to do it is to type CMD on the Start Menu search box and press Ctrl+Shift+Enter instead of just pressing Enter.
Click to expand...
Click to collapse
Requisites
You need to have ADB Debugging under Developer Options on your device. You also need the drivers for every device you want to use with ADB installed and working.
You can type adb devices on a command prompt. If your device is listed, the drivers are working and good to go for ADB and Fastboot use.
Click to expand...
Click to collapse
Download
I will always check the ADB version whenever a new Android SDK is released and I will update my installer when needed.
The download link and screenshots are on my website.
http://rubenalamina.mx/custom-installers/android-adb-fastboot/
Latest version of the installer: 1.5 (ADB 1.0.36) updated on 2016.09.21
Thanks mate, it really help people with lacks internet connection like mine
Sent from my WT19i using xda app-developers app
Installer updated to version 1.2 with the new ADB and Fastboot included in Android SDK 23.0.2.
Installer updated to version 1.3 based on the Android SDK 24.0.2.
no matter what i do it stills says ABD is not reconizedf as an internal or external command. i even downloaded the whole stinking dev kit to make sure nothing missing in these little installers. made sure that a path was put still dose NOT work :/. and yes im running cmd prompt as adminastrator.
Nightmare-Rex420 said:
no matter what i do it stills says ABD is not reconizedf as an internal or external command. i even downloaded the whole stinking dev kit to make sure nothing missing in these little installers. made sure that a path was put still dose NOT work :/. and yes im running cmd prompt as adminastrator.
Click to expand...
Click to collapse
Have you tried running it from the C:\ADB path just in case? Maybe try PowerShell instead of the command prompt. I don't really know what else you can try if even the SDK is not working for you.
ajua said:
Have you tried running it from the C:\ADB path just in case? Maybe try PowerShell instead of the command prompt. I don't really know what else you can try if even the SDK is not working for you.
Click to expand...
Click to collapse
yes ive been trying both Shift open command prompt here, and aslso left click run as adminastrator and CD c:/abd both still says abd not reconized.
Nightmare-Rex420 said:
yes ive been trying both Shift open command prompt here, and aslso left click run as adminastrator and CD c:/abd both still says abd not reconized.
Click to expand...
Click to collapse
Try using PowerShell. Also, see if you are able to run the ADB that comes with the SDK but run it from the folder where it is located.