# Command Prompt : Adb Devices error

Last Updated:

1. ### NickBaragonaWell-Known Member

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!

2. ### D13Well-Known Member

is there a # in the beginning of the line?
3. ### HowieWell-Known Member

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
4. ### NickBaragonaWell-Known Member

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!
5. ### HowieWell-Known Member

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.
6. ### D13Well-Known Member

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"
7. ### NickBaragonaWell-Known Member

I put it in C:\DroidX

So would I type cd\computer\C:\DroidX\adb devices

? I know I'm doing something wrong, is it case sensitive?
8. ### D13Well-Known Member

ok so I
cd C:\Users\Jeff\Desktop\tools
mount -o remount,rw -t yaffs2 /dev/mtd/mtdblock4 /system

All I want to do is a push to the system
9. ### NickBaragonaWell-Known Member

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.
10. ### HowieWell-Known Member

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.)
11. ### D13Well-Known Member

So its not in the tools folder of the android sdk. I see adb.exe in it
12. ### HowieWell-Known Member

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.
13. ### NickBaragonaWell-Known Member

ok thanks, looks like I got one step further! I type in 'adb devices' and it showed this :

*daemon started successfully*

List of devices attached

And thats it. So its not detecting my Droid X, correct?
14. ### HowieWell-Known Member

did you turn on USB debugging on the device?
15. ### NickBaragonaWell-Known Member

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?
16. ### HowieWell-Known Member

I'd restart the computer, make sure Droid X is in "PC Mode" instead of storage, and verify drivers installed successfully after the reboot.
17. ### D13Well-Known Member

So here is how it is. Tools folder on the desktop

mount -o remount,rw -t yaffs2 /dev/mtd/mtblock4 /system (mount system R/W?
adb push droidxsystemapps (in the tools folder) /system/app
18. ### HowieWell-Known Member

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
D13 likes this.
19. ### D13Well-Known Member

Thank you so much
Wait second still not working
20. ### D13Well-Known Member

I cant run any adb commands it seems after I run adb shell
21. ### NickBaragonaWell-Known Member

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.
22. ### NickBaragonaWell-Known Member

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?
23. ### HowieWell-Known Member

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)
24. ### FenotypWell-Known Member

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
D13 likes this.
25. ### D13Well-Known Member

Thanks man I new it was something like that