Database Users

New Droid X can't install USB composite device

Hello folks,
Last Saturday, my Droid X was stolen. I just got the replacement today and being a semi-noob, I just realized that I hadn't copied all of my Titanium Backup from the SD card to the computer so now I'm basically stuck at the beginning.
I'm ready to root my device but I've hit a roadblock. For some reason, I cannot get through the installation for USB Composite Device. I've tried PC Mode, Mass Storage, Windows Media Sync, and Charge Only. Sometimes I can see the icon of the Droid in my computer but I can't get it to show only the removable storage device.
Cannot Install this Hardware - Error occurred during the installation of the device. The System cannot find the file specified.
I don't want to root and backup everything to the SD card if my computer won't read the SD card. I have the motorola drivers installed and this worked fine on the previous phone.
Can anyone help me figure out this problem? Thanks!

Make sure the Motorola drivers are installed correctly on your PC. You might need to locate the latest versions from motorola to do this.

IIRC, I had a similar problem on my work PC originally. For some reason, the automatic detection wasn't set to check the Internet for drivers, so it was only looking on my laptop. Try checking that.

Did you try changing the phone settings so "USB debugging" was on? Sorry- I can't remember where the heck it is now. The settings on this phone to me are just wonkie. It's in there though. Try it with that turned on.

Usb debugging is in settings>applications>development
Sent from my DROIDX using XDA App

Turn USB Debugging off. Set USB connections to Mass Storage.
If you have autplay turned on, then Windows will offer to run/install the moto connect software. This version is slightly different ( from what reason?) from the one available at Moto's website.
Run that full install, THEN switch over to USB Debugging and allow it to install the drivers (Again)

[Q] ADB Driver not being found - XP

Attempting to root my Droid X for the first time and have encountered a major complication. My PCs will not recognize my ADB interface.
So I started with NOOBs walk through and downloaded the 4.6 moto drivers. Installed the drivers. Followed the root directions for installing the SDK and updating it. Go to the point with typing "adb devices" at the command prompt and no devices are listed. I went into my DX --> Settings --> Applications --> turned on USB DEBUGGING. This now prompts me for additional drivers. Nothing works or is recognized as drivers for the ADB. I've tried the USB Driver_TI.zip, the USB_Driver_3.4.6_patch_ for HG.zip, and using the google drivers from the sdk/extras folder. No luck.
With debug turned on I have the device showing with an exclamation mark in my device manager. I've tried manually pointing the device to all of the drivers mentioned above with no luck. I've tried this on a 2nd XP machine with no luck. Same issue.
My droid X is about 2 weeks old. MB810 from Verizon.

May I ask.... why not just download Z4 Root and press "root"? If all you are wanting to do is root the phone.
Sent from my DROIDX using Tapatalk

I agree z4 is the easiest method for the x. To use adb you need the android sdk package,correct drivers,and you need to edit the system environment path to include the folders you adb files are in
Sent from my Droid

Again I would recommend using z4root. It's very easy to do and requires no drivers on your computer

I struggled with this on my XP box when first trying to root my Desire HD. I eventually accidentally found the solution:
Install HTC Sync before connecting the phone to the PC.

Gyalist said:
I struggled with this on my XP box when first trying to root my Desire HD. I eventually accidentally found the solution:
Install HTC Sync before connecting the phone to the PC.
Click to expand...
Click to collapse
you're in the wrong place. this is the droid x subforum

Oops! Must read thread title more carefully in the future.

[Q] Droid 2 driver problem

I am trying to root my Droid 2 2.3.3 on Verizon. I have Windows XP SP3. I have used the 1 click root and darkonion's version from last year.
When connecting my phone in PC Mode I get a New Hardware Wizard which will not find a driver after going through the motions.
I try installing the Motorola Mobility Drivers from the links provided here. (I have found two different links) to no avail.
When using DoRootWin_2.1.4 and doroot.bat it perpetually checks for devices.
When I adb devices from the command prompt I don't get anything.
I have the following checked;
PC Mode
USB Debugging
Unknown sources
I have tried to hard reset my phone. And have gone directly to rooting.
I have deleted the USB Drivers from the list an reinstalled them (used USBDeview)
I have downloaded the Android SDK and all associated files (JDK, Java, ecllipse, busybox, su, rage, & superuser)
I have added the path to my environment and rebooted.
Any help is appreciated. I am stuck. I don't know what I am missing.

[Q] adb Mode/usb developing mode does not work

I'm using the Asus Google Nexus ToolKit V3.8.2 (donated version).
With my first N7 I was able to unlock and root.
Now I exchanged it against the N7 3G (HSPA+). I was able to unlock the device and able to install the bootloader 3.34. But root does not work. I think it is because ADB does not recognize the tablet.
What happens:
1.) the start screen of the ToolKit does not show the serial in the adb device list (If I restart the tablet in fastmode it list the serial in fastmode device list)
2.) if I start the Root and the ToolKit wants to reboot in Fastboot Mode it says "Waiting for adb Mode".
3.) If I restart on my own in Fastboot Mode and start the Root procedure then it reboots the device and says "Procedure will continue in 20 seconds Waiting for USB debugging to be enabled". It does not help to re-activate the usb debugging mode and it doesn't help to re-connect the usb cable.
4.) I started cmd and changed to the "Google Nexus 7 ToolKit" folder to call "adb-toolkit devices". But it does not show any device. adb-toolkit kill-server and start-server doesn't help. usb reconnect doesn't help.
P.S. As I'm a new member I'm not able to post inside the official support thread, sorry.

It could be a driver issue on the pc..
try this
download a pc app called usbdview . Do a google search to find it..
Run the program on the pc without the nexus plugged in. Delete all adb/ usb devices that you do not have physically plugged into your computer.
Plug in the nexus 7 refresh the list . Delete what ever comes up for the nexus 7..
Reboot the computer WITH the nexus not connected..
Install the NEXUS DRIVERS.. plug in the nexus and the computer should find the device as if its the first time used.
Try you tool kit again...
Sometimes when adb is started and stopped if there are several versions Windows can be confused and not stop the right driver but start a older version instead VERY Common windows usb issue. This works with any USB Trouble shooting for devices not just Android...
Good LUCK ..

It's pretty obvious that you need to install the correct drivers for the Nexus 7 HSPA+.
I'm not the lowest of the low, but I am the slowest of the slow.

exglynco said:
It's pretty obvious that you need to install the correct drivers for the Nexus 7 HSPA+.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse
The nexus drives are a One driver for all Nexus Devices... This should only be a issue if there are multiple copies of usb adb in the windows registry . The usb drivers need to be removed then re installed or will just create more conflict. Usb Is NOT SO PLUG AND PLAY as it was intended.. Sometimes just plugging a usb device from one usb port to another in some computers can cause windows to install another copy of the driver. This is mostly on systems with a usb hub then a usb 2.o hub on a different port.. and so on.
I Use my notebook with several android devices . I often have issues with

erica_renee said:
It could be a driver issue on the pc..
Click to expand...
Click to collapse
This could it be. But I found a very simple solution:
stackoverflow.com/a/11991653/318765
When the Nexus 7 is plugged in there is a persistent notification that indicates "CONNECT AS / Media Device (MTP)". In this state adb devices will not show the Nexus, or undoubtedly any other device. Not exactly obvious, but if you select the second option "Camera (PTP)" the device is available for debugging (the lesson is ignore the camera, and focus on the protocol PTP).
This choice is persistent, and I'm guessing that with a band new device it will connect as MTP until told otherwise.
Click to expand...
Click to collapse

[Q] USB connection as MTP on WIn 8.1

Hi,
I have Oppo Find 7.
Installed Omnirom and all has gone well.
Except that when I try to connect the phone to PC via USB cable with USB Debugging enabled .. I get nada ..
Nothing appears in the Portable Devices ..
Had various roms before ( Nameless, Miui etc ) never had this problem before.
Any advise/work around/Solution ?
Thanks
11/10/14 - Today I restored my color O/S using TWRP. Guess what, I had no problems connecting my Find 7 to Win 8.1 , which installed the driver immediately. But try as I might connecting using OMINIROM , no drivers are installed. Phone is not even recognized in devices. Can ANYONE advance/suggest something.
Great rom especially as it works so well with the Bluetooth so would hate to try/move to another rom.
12/10/14 - Resolved. It looks as if every time I connected the phone thew wrong driver was being installed. Check these steps if you have same problem:
- Under Devices check under "Android Devices" for any driver that you do not recognize in my case it installed "acer composite adb interface"
- I UNINSTALLED this INCLUDING delete associate files ( check option under uninstall )
- Then connected phone again
- This time it installed Google Nexus drivers
- I UNINSTALLED this with delete files option
- Disconnected and reconnected my phone
SUCCESS - It now installed "Android Composite ADB Interface"
My Find 7 now connects as storage device and can access phone from Win 8.1
Hope this helps someone else in same dilemma.
J