When I type adb devices, it comes up with this error : ' adb ' is not recognized as an internal or external command, operable program, or batch file.
I already installed the adb drivers, and Windows told me the drivers updated successfully. Any idea why I am getting this error? Thanks in advance, I hope to be rooted by the end of the night!
you aren't in the correct folder that has the "adb" application
you have to change directories to where ever you unzipped the Android SDK, then go into the Tools folder
Oh, I thought I just had to open up the command prompt and type that in. So how do I change directories in the command prompt? Sorry for being such a noob, I'm just excited at possibly rooting!
the command is cd (folder name)
so it would be, for example, cd \Windows..
That's not the location, just an example. I don't know the location you put that folder to give you the exact command line.
you aren't in the correct folder that has the "adb" application
you have to change directories to where ever you unzipped the Android SDK, then go into the Tools folder
I am having a problem in order for me to run mount -o.....etc( to mount system as R/W) I have to do adb shell and then I get the #. When I try to run a adb push it says " adb: not found"
ok so I
cd C:\Users\Jeff\Desktop\tools
adb shell
mount -o remount,rw -t yaffs2 /dev/mtd/mtdblock4 /system
adb push xxxxxxxxx /system/app
adb: not found
All I want to do is a push to the system
I downloaded the ADB drivers, but the file, did not come with any ADB application. What am I missing here? Thats why I had no idea what you guys were talking about when you referred to the 'Tools' folder.
you are both having the same problem. Did yous download the Android SDK from android.com?
If you did you aren't getting into the proper directory. Use "Computer" in windows to navigate around and location it. Take note of all the directory names you come across before you find adb.
After that go to the command line and type in "cd \(foldername)\(foldername) etc until you are in the proper location. (I don't remember the exact name of the folder that it unzips as but the word android was in it for me.)
you are both having the same problem. Did yous download the Android SDK from android.com?
If you did you aren't getting into the proper directory. Use "Computer" in windows to navigate around and location it. Take note of all the directory names you come across before you find adb.
After that go to the command line and type in "cd \(foldername)\(foldername) etc until you are in the proper location. (I don't remember the exact name of the folder that it unzips as but the word android was in it for me.)
So its not in the tools folder of the android sdk. I see adb.exe in it
So its not in the tools folder of the android sdk. I see adb.exe in it
So you do see adb.exe ? That file is the one you are trying to run in the command line... you need to type in that exact path to get there using 'cd'. Tell me the location of that file and I'll try my best to help you with the command line structure.
yeah, I don't know why its not even recognizing my Droid anymore under Devices with removable storage. When I plug my droid into the USB port of my laptop, it comes up with a 'Found New Hardware' box. It says 'Windows Needs to Install Drivers for your MB810'. Should I restart my computer?
So you do see adb.exe ? That file is the one you are trying to run in the command line... you need to type in that exact path to get there using 'cd'. Tell me the location of that file and I'll try my best to help you with the command line structure.
So here is how it is. Tools folder on the desktop
cd C:\Users\Jeff\Desktop\tools (point at adb.exe)
adb shell
mount -o remount,rw -t yaffs2 /dev/mtd/mtblock4 /system (mount system R/W?
adb push droidxsystemapps (in the tools folder) /system/app
adb: not found
cd C:\Users\Jeff\Desktop\tools (point at adb.exe)
adb shell
mount -o remount,rw -t yaffs2 /dev/mtd/mtblock4 /system (mount system R/W?
adb push droidxsystemapps (in the tools folder) /system/app
adb: not found
what is droidxsystemapps? Is that a directory/folder of files?
The "not found" means it doesn't know what's being asked of it. It thinks the "droidxsystemapps" is a file, but looks to be a folder. You'd have to tell it adb push droidxsystemapp\file1.apk (assuming it's apks)...etc
hope that helps. And remember adb is a linux command so it is caSe SenSitive
The Following User Says Thank You to Howie For This Useful Post:
what is droidxsystemapps? Is that a directory/folder of files?
The "not found" means it doesn't know what's being asked of it. It thinks the "droidxsystemapps" is a file, but looks to be a folder. You'd have to tell it adb push droidxsystemapp\file1.apk (assuming it's apks)...etc
hope that helps. And remember adb is a linux command so it is caSe SenSitive
what is droidxsystemapps? Is that a directory/folder of files?
The "not found" means it doesn't know what's being asked of it. It thinks the "droidxsystemapps" is a file, but looks to be a folder. You'd have to tell it adb push droidxsystemapp\file1.apk (assuming it's apks)...etc
hope that helps. And remember adb is a linux command so it is caSe SenSitive
I cant run any adb commands it seems after I run adb shell
Ok I restarted my computer. When I plug my Droid into USB, it still comes up with the 'Found New Hardware'. It never did this before I started this whole root process, so I think I know what the problem is. When I initially installed the ADB drivers, I believe I did the process wrong. I must have overwritten the drivers needed for the Droid to connect with my PC. Any idea what to do now? It does not detect my droid at all.
I reinstalled the Motorola drivers, and now my PC recognizes my droid again. Adb devices, and it listed my droid. However, the next step c:\droidx\adb push Superuser.apk /sdcard/Superuser.apk results in this error :
'adb' is not recognized as an internal or external command, operable program, or batch file.
Was I suppose to Merge the DroidXRoot folder along with the ADB folder? In the instructions, it tells you to download these files, but I did not know if it mattered where I put them on my PC. I have both of the zips I was supposed to download in seperate folders. Both the ADB and DroidXRoot folders are seperate. Is this my mistake?
I reinstalled the Motorola drivers, and now my PC recognizes my droid again. Adb devices, and it listed my droid. However, the next step c:\droidx\adb push Superuser.apk /sdcard/Superuser.apk results in this error :
'adb' is not recognized as an internal or external command, operable program, or batch file.
Was I suppose to Merge the DroidXRoot folder along with the ADB folder? In the instructions, it tells you to download these files, but I did not know if it mattered where I put them on my PC. I have both of the zips I was supposed to download in seperate folders. Both the ADB and DroidXRoot folders are seperate. Is this my mistake?
is the adb program in the droidx folder? Also, are you running that command from a directory that the Superuser.apk is in?
For example: cd in to the adb location. then run adb push \location\of\your\app\to\be\pushed.apk /sdcard (you don't have to do /sdcard/Superuser.apk because it will just assume to keep the same file name)
I cant run any adb commands it seems after I run adb shell
the "adb" commands are "C:\" prompt commands only. Once you run "adb shell" you're into the linux command line on your phone. It won't recognize adb commands.
What you want to do is "adb push" whatever files you want on your phone to the sd card (or you can just use the windows exlporer to copy and paste the files to your phone's sd card.)
Once you have all the files on the sd card, THEN "adb shell". You'll have a "$" prompt. Type in "su" and you'll get a "#" prompt (if you're already rooted). Keep an eye on your phone's screen because it may ask you to allow root access.
From the "#" prompt you can copy "cp", move "mv", remove "rm" files, and mount as read/write "rw" or read-only "ro"
If you don't see a "C:\" (or whatever letter your sdk tools are on) on the command line, you definitely can't use "adb <whatever>".
If you see a "$" or a "#" your command line is actually looking at the phone's file system, which is linux-based, and "adb <whatever>" won't work there. (This all assumes you're using windows.)
HTH, Dave
The Following User Says Thank You to Fenotyp For This Useful Post:
hiee guys
i own micromax a60
i have installed adb drivers of it
when i use
adb deices
i get a error
-------------------
list of devices attached
? devices
--------------------
why is it soooo
This is the Droid X forum, so we won't be a lot of help to you.
What I can tell you is that you need two things to get ADB to recognize your device:
- The manufacturer-provided drivers for your device
- And turn on USB debugging on your device (go to Settings > Applications > Development, check off USB Debugging)
All the above advice have been terrific; however, I've run into the problem of my command prompt in Windows 7 x64 not being able to recognize "adb" but ok with "adb.exe". Any insight? Thanks in advance for your help.
All the above advice have been terrific; however, I've run into the problem of my command prompt in Windows 7 x64 not being able to recognize "adb" but ok with "adb.exe". Any insight? Thanks in advance for your help.
Drew
Drew, welcome to the AndroidForums.
Sounds like either Windows has strangely lost its association of programs with a .exe extension or perhaps you have another file in your directory named "adb" that was mistakenly created (which would explain why an explicity reference to adb.exe works).
If you type a "dir adb*" command, do you see more than one item displayed?
Also, are you trying to run the adb command from the same directory in which it lives or do have its path added to the PATH environment variable?
Thanks for the response. My problem appears to be not only with adb, but any .exe file. Example - "java" is not recognized, but "java.exe" is. I'm trying to root my phone and hence I'm concerned that there is something more fundamental wrong and didn't want to proceed with the possibility of bricking my phone.
The Path is ok; I can call up "adb.exe" from any directory. The "dir adb*" doesn't seem to work; it appears to only search for adb files in the directory I'm immediately in.
Again, thanks for your help!
Drew
Thanks for the response. My problem appears to be not only with adb, but any .exe file. Example - "java" is not recognized, but "java.exe" is. I'm trying to root my phone and hence I'm concerned that there is something more fundamental wrong and didn't want to proceed with the possibility of bricking my phone.
The Path is ok; I can call up "adb.exe" from any directory. The "dir adb*" doesn't seem to work; it appears to only search for adb files in the directory I'm immediately in.
Again, thanks for your help!
Drew
Drew, hey no problem...I wish I could have been more help...
I did a quick Google search of "windows lost exe file association" and found more stuff (and scary stuff) than you probably want to see. Try this search and see all the results you get...you'll have to sift through the stuff that seems to match your circumstances (I would hate to hazard a guess here...remote debugging is such a pain, LOL).
Good luck with your rooting efforts!
By the way, you know this is the Droid X forum, right? I'm guessing you have a different device (which is cool, but we should probably try to throw in a DX reference to keep the Guides (LOL=me ) or Mods () happy:
"Hey, the Droid X is a pretty sweet device, eh" -- mission accomplished
When you install the sdk file, the adb is no longer in the "adroid-sdk/tools" folder. There is a text document in the android-sdk folder saying it moved to "android-sdk/platform-tools". My "android-sdk" folder is in my "program files" in a folder I named "android."
so, for example: cd c:\program files\android\android-sdk\platform-tools\
I had the same issue today, then i found that note in the android-sdk folder about the adb stuff moving. So, you must use "platform-tools" folder.
If you do not have Android-SDK", search for it on google. It will show up. I hope this helps.
When you install the sdk file, the adb is no longer in the "adroid-sdk/tools" folder. There is a text document in the android-sdk folder saying it moved to "android-sdk/platform-tools". My "android-sdk" folder is in my "program files" in a folder I named "android."
so, for example: cd c:\program files\android\android-sdk\platform-tools\
I had the same issue today, then i found that note in the android-sdk folder about the adb stuff moving. So, you must use "platform-tools" folder.
If you do not have Android-SDK", search for it on google. It will show up. I hope this helps.
Welcome to the AndroidForums, GiMortal5.
Yeah, subsequent to the above post, I whipped-up some notes about how to get the adb utility installed:
This might be easier for folks (also, the middle section has a downloadable .zip file that has the adb and fastboot utilities for Windows, Mac, and Linux platforms).
Command Prompt : Adb Devices error
I'm guessing you have a different device (which is cool, but we should probably try to throw in a DX reference to keep the Guides (LOL=me 
) happy:
Adb devices
