Database Users

64-bit Droid X Diag Mode Drivers

Does anyone know if there are 64-bit diag mode drivers available for the Droid X?
I realize Motorola has a 64-bit version of the USB Drivers and I have installed these. However, when I hold the camera button down while plugging in the USB cable some unknown devices come up in Device Manager (Data, Diag, MUX, and TCMD interfaces).
Without the Diag Interface driver I cannot get QPST or CDMA Workshop to recognize the phone port.
Thanks for any assistance. (Trying to get this phone flashed to Cricket)
fritzel67

fritzel67 said:
Does anyone know if there are 64-bit diag mode drivers available for the Droid X?
I realize Motorola has a 64-bit version of the USB Drivers and I have installed these. However, when I hold the camera button down while plugging in the USB cable some unknown devices come up in Device Manager (Data, Diag, MUX, and TCMD interfaces).
Without the Diag Interface driver I cannot get QPST or CDMA Workshop to recognize the phone port.
Thanks for any assistance. (Trying to get this phone flashed to Cricket)
fritzel67
Click to expand...
Click to collapse
Ah yes - the awesomeness that is a Droid X flashed to Cricket! I wouldn't have it any other way! Anyway, all you need is the MotoConnect drivers.
When flashing your phone, USB Debugging needs to be on and the phone needs to be in PC mode, not in the bootloader. No need to hold down the camera button. Just have the phone on; it doesn't matter if it goes to black screen (sleep) even while you are programming it.
Download Motorola 4.9.0 Driver with MotoConnect and use the middle option on the left side. I use it all the time to keep my drivers up to date and it works flawlessly on any Windows based OS ( I say that because that is what I have used it on). I have used it on both 32 and 64 bit Windows 7 computers so, if that doesn't work for you, then your problem is elsewhere.
Oh, if you need PRL 49027 to get 3G, let me know

Thanks much. I just installed the MotoConnect drivers, but when I hold the camera button while booting to get into diag mode, device manager shows several interfaces under "Other Devices" with exclamations indicating the drivers aren't installed (including Diag Interface).
When I start QPST, it detects an unknown COM port, but afterwards it says "No Phone" on the port. I also tried simply booting phone and placing in PC mode w/ debugging on, but no go.
The only diag mode specific driver I have found is 32-bit, and it won't install on 64-bit Winbloze 7.

fritzel67 said:
Thanks much. I just installed the MotoConnect drivers, but when I hold the camera button while booting to get into diag mode, device manager shows several interfaces under "Other Devices" with exclamations indicating the drivers aren't installed (including Diag Interface).
When I start QPST, it detects an unknown COM port, but afterwards it says "No Phone" on the port. I also tried simply booting phone and placing in PC mode w/ debugging on, but no go.
The only diag mode specific driver I have found is 32-bit, and it won't install on 64-bit Winbloze 7.
Click to expand...
Click to collapse
Why do you need to be in diag mode? To use QPST you need to have the phone on, USB Debugging on and in PC Mode. Make sure you are using the latest build of QPST which is 2.7 version 3.0.1 If you are, you may just need to add the port you made with HW Virtual Port in QPST. It's a simple setting and it will show up in QPST.

Finally got it. MotoConnect drivers did the trick along with the correct HW VSP settings.
Thanks for the assist!
Sent from my HTC EVO on Cricket using XDA app.

fritzel67, how were you able to do it? i'm stuck with trying to connect my phone on windows7 64-bit version. really stuck and did extensive research with 0 luck. help would be appreciated, thanks! and yes, i'm using a droid x. wanting to hook it up to qpst or qxdm possibly.

Ohh please I need for 32bit drivers
I need programm my motoroi X, thx
diag mode drivers 32bit

Ben's said:
Ah yes - the awesomeness that is a Droid X flashed to Cricket! I wouldn't have it any other way! Anyway, all you need is the MotoConnect drivers.
When flashing your phone, USB Debugging needs to be on and the phone needs to be in PC mode, not in the bootloader. No need to hold down the camera button. Just have the phone on; it doesn't matter if it goes to black screen (sleep) even while you are programming it.
Download Motorola 4.9.0 Driver with MotoConnect and use the middle option on the left side. I use it all the time to keep my drivers up to date and it works flawlessly on any Windows based OS ( I say that because that is what I have used it on). I have used it on both 32 and 64 bit Windows 7 computers so, if that doesn't work for you, then your problem is elsewhere.
Oh, if you need PRL 49027 to get 3G, let me know
Click to expand...
Click to collapse
Now I tried this and installed the Motorola 4.9.0 Driver with MotoConnect and got nothing. Once installed it just sits there. No drivers updated. Device manager refreshes like something happened but NOPE. Red X's all day.
I'm on 32Bit though. any other information you can spread. I gotta get phone into CDMA so I get data & MMS going on MetroPCS.

I also need a driver for the Droid X Diag Interface on Windows 7 x64. Searching it in the Internet I found nothing. Then I decided to remake the driver from the modem Novatel and I managed it. So, I presenting it to you:
Drivers for Motorola Droid X Diag Interface
Operating System: Windows 7 x64 and x32 and the other.

m.ksy said:
I also need a driver for the Droid X Diag Interface on Windows 7 x64. Searching it in the Internet I found nothing. Then I decided to remake the driver from the modem Novatel and I managed it. So, I presenting it to you:
Drivers for Motorola Droid X Diag Interface
Operating System: Windows 7 x64 and x32 and the other.
Click to expand...
Click to collapse
You can download official Motorola 32 bit and 64 bit driver packages from the MotoDev site....\
http://developer.motorola.com/tools/usb_drivers/

facepalm.jpg
Completely turn off your phone, then press camera button+power. When phone already turned on, connect it to PC and try to install the drivers from motorola site.

computer can't find phone in fastboot mode

Hi people
I've been trying to unlock the bootloader to root my nexus s 2.3.3 for 2 days now and have tried everything i can find in all the related threads but my computer wont see the phone when in fastboot mode.
Im getting really fed up as i do not know what to try next.
Anyone had this problem before?
Any help would be much appreciated.
Jon

Have you tried the PDA.net way to install the drivers for fastboot? Google: PDA net

Andrew421 said:
Have you tried the PDA.net way to install the drivers for fastboot? Google: PDA net
Click to expand...
Click to collapse
Yeah I've tried that too but computer does'nt see the phone in fastboot mode so i cannot update the drivers at all.

What do you mean by it cannot see it. Also, what OS are you running? Often times the phone is detected via fastboot when ADB fails (this happens to me all the time).

kenvan19 said:
What do you mean by it cannot see it. Also, what OS are you running? Often times the phone is detected via fastboot when ADB fails (this happens to me all the time).
Click to expand...
Click to collapse
Hi, when i put the phone in fastboot mode the computer doesnt see the phone in device manager but it does see it when not in fastboot mode. Im running windows 7 64.

Hey man, I had the same issues. It took me a total of 12 hours to root my phone and I tried everything . I was stuck trying to unlock the bootloader for hours. The problem for me was that the driver couldnt be found. I tried the pda net and it kept saying that the drivers were installed. Assuming your using windows, go to devices with the phone plugged in and you should see the device named something different with a yellow exclamation mark..... right click and hit update driver software. Then find the file pdanet and point it to update with that file. If this doesnt work, theres a file in there I believe its called android_usb or android_winusb and you push "have disk" and force install from that file . then it should see your phone. this was the only way i could get it to work was by pushing have disk and pointing it at the actual android 1.0 driver becuase the google usb package didnt have it (at least at the time). Im new to the forum, so bare with me if my directions aren't too great, just thought I'de try to help you out bc it was so frustrating!. Also, here is a good link in the xda forums for you to check out http://forum.xda-developers.com/showthread.php?t=875580
also,,,are you getting the "waiting for device" message when you type fastboot oem unlock? these instructions are for if you are experiencing that... Its basically not found becuase there is an android 1.0 driver that you have to force to update. good luck!

Thanks for the replies am now downloading the sdk onto the wifes laptop as hers is win 7 32 so hope there is less issues. fingers crossed.

i did mine with win 7 64 i tried 32 as well but my 64 worked better for me.... i looked at the driver details with my phone plugged in to see what drivers are on there .. you need the wdfcoinstaller , the winusb coinstaller, and the winusb.sys. if you find the device when plugged in to your computer and goto details and then hit update driver and then point it specifically at the android_usb.sys file in the pda net for android folder then it should work. the google drivers thru sdk don't contain this one file and its the one that makes the whole process work. Let me know if this works for you

mattdub1 said:
i did mine with win 7 64 i tried 32 as well but my 64 worked better for me.... i looked at the driver details with my phone plugged in to see what drivers are on there .. you need the wdfcoinstaller , the winusb coinstaller, and the winusb.sys. if you find the device when plugged in to your computer and goto details and then hit update driver and then point it specifically at the android_usb.sys file in the pda net for android folder then it should work. the google drivers thru sdk don't contain this one file and its the one that makes the whole process work. Let me know if this works for you
Click to expand...
Click to collapse
Have the same drivers installed but computer still doesn't see the phone when in fastboot mode. It worked perfectly on win7 32 on other laptop and I managed to root. still trying to get it to work on win7 64 as this is my main OS.

glad to hear,...just out of curiosity, how did you get it to work on the 32 bit version?? Id like to know for future reference,,, and also are you getting the waiting for device error in fastboot mode?

also, you did make sure to dowload the google usb package and get the right sdk version correct? I cant see any other reason that the phone wouldn't be recognized. I also believe you need usb debugging on

http://forum.xda-developers.com/showthread.php?t=878786 check out this post... VERY good guide and this is what helped me on the 64 bit 7. it sounds like your missing the fastboot driver which allows the computer to see the device in fastboot mode

mattdub1 said:
glad to hear,...just out of curiosity, how did you get it to work on the 32 bit version?? Id like to know for future reference,,, and also are you getting the waiting for device error in fastboot mode?
Click to expand...
Click to collapse
On win7 32 it was really easy once all the necessary programs and files were downloaded I first connected the phone switched on in normal mode with USB debug on and installed the drivers. Once in fastboot mode the path for the drivers was already there from the previous driver install I just selected the bootloader driver and the rest is history
Sent from my Nexus S using XDA Premium App

which one was the bootloader driver? did you get it from the google usb drivers or the pda net ones?

mattdub1 said:
which one was the bootloader driver? did you get it from the google usb drivers or the pda net ones?
Click to expand...
Click to collapse
it was the google usb drivers when i went update drivers on my system the path is
C:\android\android-sdk\extras\google\usb_driver.
Then go to option 'let me pick from a list of drivers on my computer' Which brings up three options:
Android ADB Interface
Android Bootloader Interface
Android Composite ADB Interface
Choose the Android Bootloader Interface hit next and yes to install.

Ok so on my win7 64 system i think that somewhere along the line i installed the wrong driver and broke the link although i can find the device in fastboot mode in devices and printers\unspecified but there it no option to upgrade drivers

noj78 said:
Ok so on my win7 64 system i think that somewhere along the line i installed the wrong driver and broke the link although i can find the device in fastboot mode in devices and printers\unspecified but there it no option to upgrade drivers
Click to expand...
Click to collapse
If you can see the phone in fastboot what else do you need?

deleted!!!!!!!!!!

I can see it in fastboot mode but not in device manager where it should be.
I can only see it in devices and printers where there are no driver options.

Okay, so put it in fastboot mode and try to run a fastboot devices real quick.

okay i bricked my phone and xp wont recognise?

Guys i need all the drivers for my vibrant for windows xp on my computer to recgnize it cuz it just gives me a unrecognized hardware thing and its anoying.. my win7 computers charger doesnt work so im stuck wit this xp crap :/

u may find the drivers for vibrant for xp here:http://www.userdrivers.com/PDA-Mobi...59-Phone-USB-Driver-1-0-for-Windows-XP-Vista/

anujpuri said:
u may find the drivers for vibrant for xp here:http://www.userdrivers.com/PDA-Mobi...59-Phone-USB-Driver-1-0-for-Windows-XP-Vista/
Click to expand...
Click to collapse
with those it should work right?

It still doesnt recognize it in download mode

You did open Odin right?

yeah ofcourse!!

I might be mistaken, but if you install the latest Kies Mini it also includes all the latest drivers you need.

SamsungVibrant said:
I might be mistaken, but if you install the latest Kies Mini it also includes all the latest drivers you need.
Click to expand...
Click to collapse
yes.
Get Kies Mini.
It installs ALL your drivers, and we're you on a 2.3 ROM before bricking? in that cause you may need NEXUS S drivers.

if you were on cm7 you may need the nexus s drivers. i get the drivers for cm7 from the android sdk manager->available packages->third pary add-ons->Google Inc.->Google USB Driver package.

Heres what happens, if i let my phone boot normally, it recognizes it normally as a sgh t959 device as samsung, but if my phone is in download mode it wont recognise it besides a unknown device????? i flashed simply honey 3.6 comming from 2.2.1 biwinning lol, so it bricked..

Definitely driver related. Re-install them, reboot the PC and try multiple USB ports and multiple PC's if possible. USB port could be a potential issue but wouldn't make sense being you can be recognized fine when the phone is booted.

I already tried that, and it still doesnt work??? God i hate that when it happens...
My win7 also just simply worked but xp is just killing me

[Q] Windows doesn't recognize my A500 through usb

Ok so I think I've searched well enough to conclude no one has my particular problem. When I plug in my A500 into my computer that has windows 7 windows recognizes that something was plugged in but not what it is. It says USB device not recognized, unknown device, and so on. I've tried installing the drivers from the acer website, I've tried installing the drivers from the link in the ics rooting thread, I've tried using the google android drivers and none have worked. I've even tried reinstalling windows but that had nothing to do with this it was a different thing that made me do it. Nothing has worked and I've become a bit frustrated with the tablet. Any suggestions on what to do?
Thanks

SolomonAiel said:
Ok so I think I've searched well enough to conclude no one has my particular problem. When I plug in my A500 into my computer that has windows 7 windows recognizes that something was plugged in but not what it is. It says USB device not recognized, unknown device, and so on. I've tried installing the drivers from the acer website, I've tried installing the drivers from the link in the ics rooting thread, I've tried using the google android drivers and none have worked. I've even tried reinstalling windows but that had nothing to do with this it was a different thing that made me do it. Nothing has worked and I've become a bit frustrated with the tablet. Any suggestions on what to do?
Thanks
Click to expand...
Click to collapse
What state are you connecting it in (recovery, fastboot, normal boot)?

Moborobo test program

Sorry forgot to say, it's stock rom not rooted and is being connected in normal boot.

SolomonAiel said:
Sorry forgot to say, it's stock rom not rooted and is being connected in normal boot.
Click to expand...
Click to collapse
tick the usb debugging

and that is on. Forgot to mention that as well. I forget about details quite often when i'm explaining something.

SolomonAiel said:
and that is on. Forgot to mention that as well. I forget about details quite often when i'm explaining something.
Click to expand...
Click to collapse
Moborobo, download the program and try it. Ami has worked with me many android devices
---------- Post added at 06:30 PM ---------- Previous post was at 06:26 PM ----------
Moborobo, download the program and try it. to me has run many android devices. sorry for my English

Your computer isn't detecting it at all, or is there an error while trying to identify it? Make sure you have the proper drivers for your device on your computer.

It's an error identifying it. I do have the correct drivers the a500 drivers from either the rooting guide or the Acer website neither has worked.

Moborobo does not work with the a500. I tried it and it still says to connect my device. which it is but it's just unrecognized.

If you have installed the driver correctly, AND you had administrator rights when you installed, should be no reason why you can't get the PC to recognize the device.
First, I would advise using a good USB cable. It's been known in the past, that some folks try to use a printer cable, and sometimes it doesn't work. If changing cables doesn't work, then do the following
1. In Device Manager, try loading the drivers manually. You should be able to have it search the windows system for the drivers. If it doesn't find it, then windows is being stupid. Try installing it manually (ignore the warning it may not be compatible,.....)
2. If that doesn't work, then you can use the Google USB drivers
http://www.redmondpie.com/android-u...r-samsung-htc-asus-sony-lg-and-other-devices/
Generally, we install the Android SDK first;
http://developer.android.com/sdk/index.html
And again, have Device manager look to that directory and manually select.
Either way, this should get you up and running.
And one more thing, turn on USB Debugging in your tablet's system properties.
MD

I've tried that. Didn't seem to work as windows would still not recognize the a500. And the usb debugging has been on since the beginning.

Okay i've gotten windows to the point of being able to install the drivers from the device manager but there is no clear option to choose. Here are the choices:
acer android communications port
acer android modem
acer hs-usb android diag
acer hs-usb diagnostics
acer composite adb interface
acer fastboot interface
acer picasso usb boot-recovery driver (google driver)
android bootloader interface (google driver)
So any suggestions cause I've tried installing the adb interface, fastboot interface and the android bootloader interface and haven't gotten any good results.
Thanks

Did you try a second PC? Sometimes a machine can get wonky if you've been using for years. Using a second machine or reinstalling Windows freshly would greatly increase the chances of detection.

Yep tried about 3 machines.

SolomonAiel said:
Yep tried about 3 machines.
Click to expand...
Click to collapse
I'm having the same issue with a bricked A500 I bought on ebay
Windows just recognizes it as an MTP USB device and fails to install the drivers
I have another A500 that comes up fine as an A500 on the same PC.

Try disabling the USB debugging in developer options I have the same issue with my Win 7 x64 system

Samsung drivers

Hi .
does anyone know other drivers i can use for the i9505 device?
The drivers installed from keis do not work under Recovery mode from TWRP .
When i connect my device to my windows 8 machine, on device manager it complains that it cannot find the drivers for the phone yet when the device is booted into a working rom of any kind, it detects it?
Thanks in advance

Google, Samsung usb drivers.

usb drivers
jonneymendoza said:
Hi .
does anyone know other drivers i can use for the i9505 device?
The drivers installed from keis do not work under Recovery mode from TWRP .
When i connect my device to my windows 8 machine, on device manager it complains that it cannot find the drivers for the phone yet when the device is booted into a working rom of any kind, it detects it?
Thanks in advance
Click to expand...
Click to collapse
Ok here you go, the official Samsung usb drivers for your phone: http://www50.zippyshare.com/d/74240052/114177/Samsung_USB-Driver_for_Mobile_Phones-1.5.27.0.exe (direct download link)
Install it and reboot the computer, then plug usb cable in and wait til windows recognizes .your phone.
Good luck!

Misterjunky said:
Ok here you go, the official Samsung usb drivers for your phone: http://www50.zippyshare.com/d/74240052/114177/Samsung_USB-Driver_for_Mobile_Phones-1.5.27.0.exe (direct download link)
Install it and reboot the computer, then plug usb cable in and wait til windows recognizes .your phone.
Good luck!
Click to expand...
Click to collapse
tried the above steps and did not work
windows still cant detect my phone.
edit: even on my windows 7 laptop it wont detect it

Did you kill or uninstall Kies? If so, try a different cable.

Might be Windows 8 ( wouldn't be surprised ) try running kies in Win7 or XP mode etc? Have you allowed USB debugging?

i've tried a different cable and even a different computer all together where i installed win7 on that laptop only a week ago so still fresh. im about to try it on my imac .
If this doesnt work then surely the drivers in question are not correct!
will find the mac drivers

i've tried a different cable and even a different computer all together where i installed win7 on that laptop only a week ago so still fresh. im about to try it on my imac .
If this doesnt work then surely the drivers in question are not correct!
will find the mac drivers.
edit: how can u enable debug mode from recovery?

jonneymendoza said:
i've tried a different cable and even a different computer all together where i installed win7 on that laptop only a week ago so still fresh. im about to try it on my imac .
If this doesnt work then surely the drivers in question are not correct!
will find the mac drivers.
edit: how can u enable debug mode from recovery?
Click to expand...
Click to collapse
Sorry I've read it wrong, didn't realize what TWRP was till I did a bit of research... I suggest emailing TeamWin Projects about it, theirs a few people on their with the same problem, hope you get it sorted.
http://www.teamw.in/project/twrp2/182