Ok, I have had multiple Android devices and have never had a problem with any of them with adb however, my computer had done some weird thing and every time I opened SDK Manager, it would open, but then time out and freeze..
SO.
I uninstalled both java development kit, and sdk manager, but now the manager wont open at all.. It just flashes a command prompt and exits out... So I ran the android.bat batch file in a command window, and i got this error
'xcopy' is not recognized as an internal or external command,
operable program or batch file.
ERROR: SWT folder 'lib\x86_64' does not exist.
Please set ANDROID_SWT to point to the folder containing swt.jar for your platform.
If anyone can help me, I would be much appreciated, I just got two new devices this month. I was able to root my SGS2 before, and now I am trying to root my Kindle, and all this is happening... Any help would me much appreciated...
Oh, and I did check my system32 file, and I do have xcopy in my system files
UntamedDeviance said:
'xcopy' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
Do you know if "C:\Windows\System32" is in your Environmental Variables Path? My friend had this problem recently, and for some reason it wasn't in there. We added it to the path, and everything works fine now.
EDIT: Here is a link to a tutorial on how to fix this error: http://helpdeskgeek.com/how-to/fix-not-recognized-as-an-internal-or-external-command/
Might try executing the command from a CMD window set to the directory where the files are as a quick test. I agree with checking the Env. paths too.
Related
I am running adb on windows vista. and When i type in the command:
C:\Users\korey\Desktop\Korey's ****\android-sdk-windows\tools>adb devices
My phone comes up. But when i try to install apks from another folder like so:
C:\Users\korey\Desktop\Esquire\HTC Magic\CrackedApps> adb install NemoPlayer.apk
It gives an error saying: 'adb is not recognized as an internal or external command,
operable program or batch file.
can some one please help me with this i would really appreciate it
"crackedapps" eh?
This thread is hilarious
Esquire22 said:
I am running adb on windows vista. and When i type in the command:
C:\Users\korey\Desktop\Korey's ****\android-sdk-windows\tools>adb devices
My phone comes up. But when i try to install apks from another folder like so:
C:\Users\korey\Desktop\Esquire\HTC Magic\CrackedApps> adb install NemoPlayer.apk
It gives an error saying: 'adb is not recognized as an internal or external command,
operable program or batch file.
can some one please help me with this i would really appreciate it
Click to expand...
Click to collapse
You need to add "C:\Users\korey\Desktop\Korey's ****\android-sdk-windows\tools" to your PATH environment variable.
Please post in the correct forum next time
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.
I've installed the java sdk, the android sdk, set the environment paths, and updated the android tools and cannot get windows to recognize "adb" command.
I've cd'd to the tools folder and tried to use it, but it keeps saying "adb is not recognized as an internal or external command, operable program or batch file."
I'm not sure what to do at this point.
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
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