MK_9

K my frustration level is definitely climbing.

I've checked and don't see anything related to this specific issue.

I'm following the step by step instructions on RootYourDroid. Have tried both the custom recovery image (adb shell is what's getting me that message) and the busybox instructions. Each time, in the adb window when I try either option I get an "error: device not found" After doing some research, I found info saying it likely had something to do with the debugging drivers. So I uninstalled them, reinstalled them and went through that whole process again. Tried both the busybox and custom recovery image steps. Still getting the error message.

Anyone have any experience with this issue that might be willing to sling some help my way?

Last edited by MK_9; March 2nd, 2010 at 10:26 PM.

Fabolous

Do you have USB debugging enabled under your settings, application, development?

__________________
Overclocked Rooted Droid X with ApeX

MK_9

I do.

DiegoMejia

this may sound like a dumb question but do you have the motorola drivers?

32bit version:
http://direct.motorola.com/hellomoto/Common/Drivers%20and%20Plug%20ins/USB_Drivers_32_bit_4.2.0.zip

64bit version:
http://direct.motorola.com/hellomoto/Common/Drivers%20and%20Plug%20ins/USB_Drivers_64_bit_4.2.0.zip

MK_9

Yes, have those as well.

vincentp

I'm stumped. I had the same problem when I first installed ADB, but installing the Motorola drivers fixed it.

"adb devices" doesn't list anything? Did you check to make sure the drivers are properly installed? They should show up in Device Manager under ADB interface or something like that.

__________________
The following statement is true
The previous statement is false

esocid

This happpened with me, but when using rds lite. It wouldn't recognize it, so I uninstalled drivers, rebooted, reinstalled and tried a different usb port and it started working again. So try another port.

MK_9

K tried this. No longer getting that message and adb is showing in the device manager.

Unfortunately now, I'm getting a permission denied message when I try to copy the flash_image file.

Last edited by MK_9; March 3rd, 2010 at 09:24 PM.

esocid

Copying it to where? Certain directories will require root access. So type su first. If it just sits there you may have to look at your phone and press allow in the little permission box that pops up.

natediddy1120

To the OP, are you using Windows? Or Linux or something...

SagayIam

Below is the content of the text file named "adb_has_moved.txt
You will find it in the following path:

C:\Program Files\Android\android-sdk\tools
or
C:\Program Files (x86)\Android\android-sdk\tools
=============================================

---The adb tool has moved to platform-tools/

If you don't see this directory in your SDK,
launch the SDK and AVD Manager (execute the android tool)
and install "Android SDK Platform-tools"

Please also update your PATH environment variable to
include the platform-tools/ directory, so you can
execute adb from any location.---

==============================================

adb shell Solution:

I am assuming you have downloaded and installed Java JDK (not JRE) and Android SDK.

Open your environment variables. How?
Right-click My Computer, properties, advanced system settings, environment variables.

Now update your adb path as follows:

In the System Variables group, double-click path
1. scroll to the end of the environment string
2. Type ;
3. type C:\Program Files\Android\android-sdk\platform-tools
** Please note that the path is case sensitive

If you have a 64 bit system
3. type C:\Program Files (x86)\Android\android-sdk\platform-tools

4. click ok, ok

Now your adb shell will work flawlessly.

If it worked for you (I know it will), a little thank you will be proper.

Last edited by SagayIam; January 15th, 2012 at 04:37 PM. Reason: To add my device

chbhargava

I had similar problem.. my device *some times* does not get detected.
But, it works fine after restarting the computer - which was real pain!

Following steps worked for me, with which we can avoid restarting of computer:
1. Start -> run: type "services.msc" and enter
2. Search for "FsUsbExService" -> right click restart.
3. Restart adb server
Open command prompt (Start -> run "cmd" and enter)
<Go to "platform-tools" dir OR add this to system's PATH variable>
adb kill-server
adb start-server

Hope it works!

Last edited by chbhargava; February 12th, 2012 at 01:40 PM.