im using windows 7 64bit and trying to learn adb and cmd
i was watch how to install adb and following..
after installing adb and drivers and added adb on system variables
i type cmd and then typed C:\android-sdk-windows\platform-tools
after that i typed adb devices but got an error
C:\android-sdk-windows\platform-tools\adb.exe is not a valid Win32 application.
what do i have to do here?? T.T
If I'm not mistaken in Win7 64, the Android SDK installs ADB to c:\Program Files(x86)\Android\android-sdk\platform-tools\adb.exe
feedhead said:
If I'm not mistaken in Win7 64, the Android SDK installs ADB to c:\Program Files(x86)\Android\android-sdk\platform-tools\adb.exe
Click to expand...
Click to collapse
that is correct. i'm on win 7 x64 and its there.
Type cd then space in front of C:\....
That changes directories.
Sent from my ADR6400L using XDA Premium App
qudwis said:
im using windows 7 64bit and trying to learn adb and cmd
i was watch how to install adb and following..
after installing adb and drivers and added adb on system variables
i type cmd and then typed C:\android-sdk-windows\platform-tools
after that i typed adb devices but got an error
C:\android-sdk-windows\platform-tools\adb.exe is not a valid Win32 application.
what do i have to do here?? T.T
Click to expand...
Click to collapse
First confirm that adb installed where you think it did.
Code:
C:\android-sdk-windows\platform-tools
Hit the start button in Windows and copy and paste your path from above into the Search programs and files box. If the path is valid, Windows Explorer will open to that directory.
If the path is not valid, try typing adb.exe in the search box to see if Windows knows where it is. If it comes up in the search results, right click on it and select "Open file location" and Explorer will open to where it is installed.
Once you have verified where adb is, you should be able to pick up from where you ran into a problem.
I attached the .pdf that I followed when I first installed adb ... I wish I remembered where I got it so I could credit them appropriately. The screen-shots might be helpful to you.
(Note: there is a typo on page 8 where the System Variables are setup paltform should be platform)
Oops the file was too big.
It is zipped and attached to this post.
Edit: I found where I got the document from. http://forum.xda-developers.com/showthread.php?t=1009419
http://forum.xda-developers.com/showthread.php?p=9959449
Related
i downloaded the sdk and i downloaded a samsung galaxy driver and when i look for my phone in the command line it just doesnt show up. theunlockt just isnt helping. anybody got a good link for dummies?
antonio91282 said:
i downloaded the sdk and i downloaded a samsung galaxy driver and when i look for my phone in the command line it just doesnt show up. theunlockt just isnt helping. anybody got a good link for dummies?
Click to expand...
Click to collapse
Did you put your phone in debug? Settings>Applications>Development
yes. and i been going over the directions repeatedly on theunlockr. im running xp 32 i believe
ADB for Dummies: Download http://de.codeplex.com/
- Once installed... open command prompt:
cd C:\Program Files\Droid Explorer\SDK\tools
Click to expand...
Click to collapse
- <type your ADB command here> e.g.
adb shell
Click to expand...
Click to collapse
^ yeah...
adb devices
Click to expand...
Click to collapse
should show your device...
To the OP, I don't know if this is the case for you but I changed my path on my Windows PC like the guides said to and that didnt completely work. (Maybe neede a restart). But in any case if you go to the command prompt, change directories to were you have adb and run your commands from there, it works like a charm.
For example if you unzip the the SDK in your download directory, open up the command line and type:
cd C:\Documents and Settings\<your user name>\Downloads\<whatever-you-named-the-unzipped-folder>\tools
ADB is in the tools directory you just went to. From here you can run the adb command without having to set up the system paths. This is a quick and dirty explanantion and might not even work for you. I was running this on Windows XP when I had this problem. Same thing had to be done on my Ubuntu Linux box b/c I'm to lazy to set up paths on that one, lol.
zephiK said:
ADB for Dummies: Download http://de.codeplex.com/
- Once installed... open command prompt:
- <type your ADB command here> e.g.
Click to expand...
Click to collapse
Oops, didnt see that you allready posted this. Yea do what zephiK says and it should work.
i have not been able to get adb to work no matter what i did (i am using xp) and i have been trying since i had the htc magic last year. here is how i recently got it working.
i downloaded the one-click root zip file and unzipped it. inside there is a adb.exe file. i clicked it and then then made sure my phone was in debugging mode and connected to my pc and used the command prompt to point to where adb is in my android sdk which for me is cd\androidsdk\tools
adb devices
i hit enter after tools and enter after devices and now it works. not sure why but it does. i couldnt get my magic, my nexus one or even the galaxy to work until i did this.
i got everything done. i think? only problem is im getting $ sign instead of # sign. any ideas?
i got adb working. thanks everyone.
A thread success story without any casualties. Almost makes me weep.
Got a new computer and Im having trouble getting my ADb setup. When I try to run adb devices I get
adb is not recognized as an internal or external command, operable program or batch file.
I have adb setup on C, JDK is installed. Downloaded drives from htc sync, but did not install htc sync. Under Device Manager, the phone is listed as
-Android USB Devices
-My HTC. the monitor has a lilttle yellow triangle with an !. I tried to update the drives, but it says I have the most recent installed.
Any help would be greatly appreciated. Thanks.
Edit.....need to use the platform-tools folder, not tools.
+1
I have tried to run ADB on my Inc, Nook Color and now the TBolt.
I just cant get it to work.
It would be easy to just say I am a dope, but I have had a highly successful run with the Inc. I have flashed/installed/performed/restored every worthwhile mod available for the INC and Nook with no trouble. I just cant get ADB to run.
ive just helped someone with this.
they HTC Sync software has the ADB drivers
download
install
then cancel HTC sync instalation
http://forum.xda-developers.com/showthread.php?t=1000751
It sounds to me like your problem is that the adb executable is not in your path and you're not trying to run it from within the directory it is installed in, as indicated by your saying "adb is not recognized as an internal or external command, operable program or batch file".
In your terminal window, try using the cd command to switch to whatever folder the adb.exe file is in, and then try running the command. You don't even need the phone hooked up to test at first...just type adb devices or something to see if the app runs or not. On my Mac, if I just type adb at the command line, adb responds with a list of all available commands.
Do a dir command (Win) or ls (Mac/Linux) to confirm the file is in the same directory you are.
distortedloop said:
It sounds to me like your problem is that the adb executable is not in your path and you're not trying to run it from within the directory it is installed in, as indicated by your saying "adb is not recognized as an internal or external command, operable program or batch file".
In your terminal window, try using the cd command to switch to whatever folder the adb.exe file is in, and then try running the command. You don't even need the phone hooked up to test at first...just type adb devices or something to see if the app runs or not. On my Mac, if I just type adb at the command line, adb responds with a list of all available commands.
Do a dir command (Win) or ls (Mac/Linux) to confirm the file is in the same directory you are.
Click to expand...
Click to collapse
Yea, the error is the one you get when you use a windows command thats not in the path. So do this, or add it to your path environment variable
Thanks to all who answered. That is why this community is the best. The older version of adb just had tools folder, while the new version has platform tools that needs to be used. Again thanks.
sent from my commando style T-Bolt.
I'm on win 7 32 bit.
I have HTC sync installed, adb installed, added system variables and cannot get adb to recongize my device in command prompt.
http://www.youtube.com/watch?v=A1SOSXwkc_8
iam having trouble using ADB with windows XP. i have downloaded superoneclick program and opened the ADB folder inside. then i turned usb debugging on, then connected, then ran the ADB program, it starts with showing how to run commands, but only stays open for about 5 seconds, then closes, i cant read what the rest of it says because it closes to quickly. iam new to android and have never used adb before but i followed all the steps i think. what iam i doing wrong? thanks
RPK925 said:
iam having trouble using ADB with windows XP. i have downloaded superoneclick program and opened the ADB folder inside. then i turned usb debugging on, then connected, then ran the ADB program, it starts with showing how to run commands, but only stays open for about 5 seconds, then closes, i cant read what the rest of it says because it closes to quickly. iam new to android and have never used adb before but i followed all the steps i think. what iam i doing wrong? thanks
Click to expand...
Click to collapse
you have to open a command prompt in the folder where adb.exe is stored. you don't need to run the program itself, just run commands necessary to do whatever hack you're trying to do. if you just put the apk files in the same folder as adb.exe then use "adb push" commands and such (whatever is detailed in the instructions)
to open a command prompt in the folder, i think you can just right click and select "Open command prompt here" (i know that's in win7, not too sure about xp)
also - this is the wrong section to post this. it should be in the Q&A section, not development.
raybond25 said:
you have to open a command prompt in the folder where adb.exe is stored. you don't need to run the program itself, just run commands necessary to do whatever hack you're trying to do. if you just put the apk files in the same folder as adb.exe then use "adb push" commands and such (whatever is detailed in the instructions)
to open a command prompt in the folder, i think you can just right click and select "Open command prompt here" (i know that's in win7, not too sure about xp)
also - this is the wrong section to post this. it should be in the Q&A section, not development.
Click to expand...
Click to collapse
thanks for your help. when i extracted adb from S.O.C. i gave me 5 files
ADB.exe
ADBmac
ADBlinux
ADBWinUsbapi.dll
ADBWinApi.dll
I right clicked on all of them and couldnt find anything about opening command prompt?
RPK925 said:
thanks for your help. when i extracted adb from S.O.C. i gave me 5 files
ADB.exe
ADBmac
ADBlinux
ADBWinUsbapi.dll
ADBWinApi.dll
I right clicked on all of them and couldnt find anything about opening command prompt?
Click to expand...
Click to collapse
start, run and type cmd. this gives you a command prompt
Why are you using super one click on your atrix? Gingerbreak or gladroot is the preferred method for the atrix.
Sent from my Blue Steeled Atrix
Big-A-Rob said:
Why are you using super one click on your atrix? Gingerbreak or gladroot is the preferred method for the atrix.
Sent from my Blue Steeled Atrix
Click to expand...
Click to collapse
Yes I know iam just trying to get the ADB files from.SOC. iam rooted on gingerbreak.
Sent from my MB860 using XDA App
scorneil said:
start, run and type cmd. this gives you a command prompt
Click to expand...
Click to collapse
Start the. Exe? Because it wont allow me to type any commands it just runs for about 2 seconds then closes.
Sent from my MB860 using XDA App
I'm trying to update my phone and it won't boot into download mode :X so I'm trying to do it with adb my problem is I can't get adb commands to work because I don't know what the path should be in the variables :C my location for adb is "C:\Program Files (x86)\Android\android-sdk\platform-tools.adb.exe" thats so much in advace!!
Dunphy said:
I'm trying to update my phone and it won't boot into download mode :X so I'm trying to do it with adb my problem is I can't get adb commands to work because I don't know what the path should be in the variables :C my location for adb is "C:\Program Files (x86)\Android\android-sdk\platform-tools.adb.exe" thats so much in advace!!
Click to expand...
Click to collapse
In order for adb to work you need to set the path to where adb.exe is. The code is
chdir C:/Program Files (x86)/Android/android-sdk/platform-tools
adb shell
that will enable you to use adb
Sent from my Optimus Me using xda premium
for adb to work u just needed to be booted up normally with usb debugging selected.
locate to the folder where adb.exe resides. SHIFT + right click on that folder and choose "open command window here"
cmd terminal will open up wid C:/Program Files (x86)/Android/android-sdk/platform-tools
nw run "adb devices"
if ur device is detected with serial no then are good to use adb....
Sent from my Nexus One using Tapatalk
I've tried on windows 7 and Ubuntu 12.10 and no matter what I do,no matter how many times I update the SDK or uninstall and reinstall the SDK,ADB version is still 1.0.29...tried killing server,restarting adb, etc.
Trying to ./extract files from cm10.1 for compiling CM but ADB must be updated to connect to JB devices...
Someone please help!!! I've googled for hours and tried everything..still getting nowhere.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
:SOLVED FOR ME:
so what i did (and i dont know why all of a sudden its working) but,
i opened up the terminal and did the following
lsusb
This should kick out a list of plugged in devices. Most likely the last one is the phone. There were references to Samsung and Galaxy so it was pretty easy to figure out. On that same line, there is an ID number in this format...xxxx:xxxx. Write that number down for reference.
Now a few more commands:
cd
sudo gedit /etc/udev/rules.d/99-android.rules
When the rules open, copy/paste the following with the id "lsusb" gave you:
replace the ####:#### in the above string of text with the number you got from "lsusb"
Then save and exit.
sudo service udev restart
sudo adb devices
# XXXXXXXXXXXX offline
sudo ./extract-files.sh
GOT THE WINDOW POPUP ON MY PHONE
check always accept from this computer
then everything went smoothly....hope this somehow or another helps someone...if it does,please hit thanks.
in Ubuntu, once you update the SDK , copy the adb file in SDK/platform-tools to /usr/bin
reboot Ubuntu and try .
i don't use windows sorry
Sent from my GT-S5670 using xda premium
soham jambhekar said:
in Ubuntu, once you update the SDK , copy the adb file in SDK/platform-tools to /usr/bin
reboot Ubuntu and try .
i don't use windows sorry
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
just tried sudo cp ~/android-sdk-linux/platform-tools/adb /usr/bin
it seemed to have copied since the original adb there was like 577kb and the new one is 1.2mb but still same issue.. i dont care to get it working on windows anyways...just thought i was strange it wont work on either platform...any other suggestions??
just a mention if someone arrives due to google search and are having an issue updating adb version in windows..this thread only speaks of a fix in linux so here is what i found: somehow someway adb.exe along with a couple dll files found their way to my windows directory, even though i always had its installed path included in my systems environment variables!! first i simply renamed these 3 files and added the extension .old to them. immediately running adb version in a command prompt my version finally read properly as it should 1.0.31 and not 1.0.26. its self explanatory why. hope this helps someone!
sinner99 said:
just a mention if someone arrives due to google search and are having an issue updating adb version in windows..this thread only speaks of a fix in linux so here is what i found: somehow someway adb.exe along with a couple dll files found their way to my windows directory, even though i always had its installed path included in my systems environment variables!! first i simply renamed these 3 files and added the extension .old to them. immediately running adb version in a command prompt my version finally read properly as it should 1.0.31 and not 1.0.26. its self explanatory why. hope this helps someone!
Click to expand...
Click to collapse
I had to sign up for this forum just to tell you, THANK YOU!!!! For the life of me, it was ridiculous that I couldn't find just simple information on how to do stuff. This is my first time looking into this stuff, So I couldn't even figure out how to update individual tools like that, which is what I've been spending the last 2 hours or more trying to figure it out.
It really was those three files in the Windows directory this whole time. Now my device is online, and adb shows the right version. Amazing. It's absolutely pathetic that google has their program screw up the entire adb functionality by putting these broken versions of the tool in the Windows directory.
I had to add to the path variable the location folder of the appdata platoformtools abd.exe.