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.
Related
I recently soft-bricked my Vibrant so now it get stuck at the Vibrant screen and it is hardware locked. I can get my phone into download mode using adb but then it does not show up in ODIN. When I plug the phone in during the Vibrant screen, it shows up as COM 6 but then it is removed when it gets to Download mode.
I searched around for a while looking for a solution and tried a bunch of things but nothing worked.
Also, when I plug my phone in during download mode, it says "The USB device attached to the computer has malfunctioned and Windows does not recognize it."
I'm on Windows XP 32-bit
PC Not Recognizing Vibrant in Download Mode
My stock, rooted Vibrant was soft-bricked by the latest update. I've been following the instructions on this thread: forum.xda-developers.com/showthread.php?t=803492, but cannot get Odin to recognize the device in Download Mode.
One caveat of my current situation is that I'm running Windows XP (32bit) on VMWare on a Mac. Not sure if this is the cause of my pain, but I simply don't have a PC handy.
Currently, when the phone is connected via USB in Recovery Mode, it mounts and everything is cheery. Even on the Mac side, adb recognizes the device and lets me tunnel into it. But the instant I boot into Download Mode the computer no longer recognizes it.
I've reinstalled drivers, tried using 64-bit versions of drivers, tried Kies, but Odin simply does not see the device in Download Mode.
Has anyone experienced this and resolved the issue? Should I hunt down a PC and ditch VMware? That's pretty much my final option prior to heading down to T-Mobile.
theorginazation said:
I recently soft-bricked my Vibrant so now it get stuck at the Vibrant screen and it is hardware locked. I can get my phone into download mode using adb but then it does not show up in ODIN. When I plug the phone in during the Vibrant screen, it shows up as COM 6 but then it is removed when it gets to Download mode.
I searched around for a while looking for a solution and tried a bunch of things but nothing worked.
Also, when I plug my phone in during download mode, it says "The USB device attached to the computer has malfunctioned and Windows does not recognize it."
I'm on Windows XP 32-bit
Click to expand...
Click to collapse
What version of Odin were you using 1.0 or 1.3?
ckalima said:
My stock, rooted Vibrant was soft-bricked by the latest update. I've been following the instructions on this thread: forum.xda-developers.com/showthread.php?t=803492, but cannot get Odin to recognize the device in Download Mode.
One caveat of my current situation is that I'm running Windows XP (32bit) on VMWare on a Mac. Not sure if this is the cause of my pain, but I simply don't have a PC handy.
Currently, when the phone is connected via USB in Recovery Mode, it mounts and everything is cheery. Even on the Mac side, adb recognizes the device and lets me tunnel into it. But the instant I boot into Download Mode the computer no longer recognizes it.
I've reinstalled drivers, tried using 64-bit versions of drivers, tried Kies, but Odin simply does not see the device in Download Mode.
Has anyone experienced this and resolved the issue? Should I hunt down a PC and ditch VMware? That's pretty much my final option prior to heading down to T-Mobile.
Click to expand...
Click to collapse
It's the Mac....sounds like you've done everything correctly. do you have the option for Parallels?
Download mode uses a different usb driver. If you are running in a vm you need to set the vm app to pass that usb device thru to the guest os.. i use odin in virtualbox on linux just fine. I haven't tried it on osx though. There's also an app in development in the i9000 dev forum that runs natively on osx.
@shinybuddha unfortunately parallels is not an option, but I could likely hunt down a PC
@ttabbal thanks for the tip, I've been suspicious of the drivers. Currently I have version 5.2.0.5 installed, and when connecting the Vibrant in download mode, a "Generic Serial Device" appears, but fails to connect.
Unfortunately the device exhibits the same behavior on the Mac side, and isn't being recognized in Download Mode, at least not by "adb devices".
Is there a specific driver I should install in the virtual XP os? Or could you provide a link to the osx app?
I think I need to find a PC. After scouring the forums it appears there has been no successful Odin use on a Mac via VM.
forum.xda-developers.com/showpost.php?p=7854560&postcount=12
Also discovered this interesting bit from the Heimdall developer:
After some serious investigation and a bit low-level debugging it appears as though there is very little I can do to correct the GT-I9000's lack of USB specification compliance when in download mode. When in download mode the GT-I9000 is using an embedded Gadget Serial driver and not the one provided by the linux kernel (zImage). As such I have made Samsung aware of the issue although I don't know if they will resolve it or how long it will take.
Click to expand...
Click to collapse
forum.xda-developers.com/showthread.php?t=755265&highlight=heimdall&page=16
Found a Windows Vista 64-bit installation and followed the directions on the following thread:
forum.xda-developers.com/showthread.php?t=803492
My Vibrant is back! Done in 30 minutes, after spending 3 days trying to get it to work via VM on a Mac. Sometimes iCan't.
Just to help out anyone else with a similar problem using Windows directly... I also found that Odin would recognize my phone when on normally but not in download mode. To solve, what I did was put the phone in download mode, then open up device manager and there was a new unknown device... gave it the path to the downloaded drivers and let it install. Then another unknown device popped up (might have to close and reopen device manager, or refresh, or unplug and plug phone). Pointed it to drivers download again and it magically appeared in Odin.
Aerankas said:
Just to help out anyone else with a similar problem using Windows directly... I also found that Odin would recognize my phone when on normally but not in download mode. To solve, what I did was put the phone in download mode, then open up device manager and there was a new unknown device... gave it the path to the downloaded drivers and let it install. Then another unknown device popped up (might have to close and reopen device manager, or refresh, or unplug and plug phone). Pointed it to drivers download again and it magically appeared in Odin.
Click to expand...
Click to collapse
What drivers did you "point" too. Im having the same issue as you, except in my device manager is says "Gadget Serial." Either way, I need my PC to recognize my phone in download mode so please help!
I had the same proble. It showed Gadget serial in device manager. I uninstalled all other samsung and keis related drivers and installed 5.2.0.4 and it worked out fine. You can download them from here. Good luck.
http://forum.xda-developers.com/showthread.php?t=728929
omg thanks
ya, the other drivers were screwed somehow, switched to these and bam... odin sees the vibrant. Thanks in bunches, lifesaver move there
I am running the 12/09 version of jt's ICS. Trying to hook up my phone to use cdma workshop, but it can't find my phone. Odin will detect it in download mode, but from my understanding when you use cdma workshop the phone needs to be turned on? I have usb debugging enabled already so thats not it. I read somewhere about putting the phone in dialup mode, but in ICS I don't see an option for that?
Any ideas?
R u on XP? My comp. doesnt recognize my phone on XP but on Win7 it surely does.
I've on Windows 7.
Jordanqkoch said:
I've on Windows 7.
Click to expand...
Click to collapse
Follow droidstyle's guide for installing mtd roms, and install the nexus drivers so that your pc recognizes your phone. He has the link for the drivers
"the relentless pursuit of the perfect rom"
Not doin it for me. I need to know how to get ICS into diag mode. So it's recognized as a com port.
I just got a Droid X and I got it flashed to metroPCS. I am running GrapeGum Gummy Kang with Apex launcher. I have tried putting phone in Diag mode.
(Hold camera button from startup until home screen, then release)
I tried starting Windows without driver signing.
(Hold F8 until safe mode screen and choose start Windows without driver signing.)
USB debugging is on, Unknown sources is on. Phone charges off of PC. Phone is rooted.
I cannot for the life of me get the Data, MUX, TCMD, or Diag drivers to install no matter if I install "Motorola device manager 2.2.17" or "USB_drivers_32_Bit_4.6.0" I am also running Win7 Ultimate.
(To be clear, the packages DO install, but do absolutely nothing.)
Ultimately I am trying to get the phone recognized by the PC so I can enter CDMA and get Data and MMS going. Can someone please help me get this thing going?! I am better at doing EVO's but not too familiar with the whole Motorola way of doing this.
Any help or suggestions would be appreciated. Thanks guys.
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
This thread is a process of how to potentially get your phone prepared for these steps:
http://forum.xda-developers.com/moto-x/general/tut-resurrecting-bricked-moto-x-corrupt-t2629057
If your device says USB Input device and then disconnects after a few seconds, There is a potential theory as to how to bypass that.
After buying a "Factory cable" for the moto X for 10$ I plugged it into my computer and nothing, So i noticed that it would 'unplug' after it "installed" the driver. So i plugged it into the USB slot in my pc and found out that the green light not only showed up, but stayed on for a constant hour! This means that the phone must somehow still be alive and charging. The reason behind this is the fact that the TV didn't install the driver, but simply sent current to the cord. The problem is that if you've already installed the driver on your pc once, it will always fetch that same driver to install the device again. The bypass to that would be finding a Windows XP computer that asks if you'd like to install the drivers first. Or a Win 7/8 Pc that hasn't been connected to the Moto X yet. Go to devices and printers: right click my computer -> Driver installations -> Never install using Windows Update. This should allow you to install your own driver which is the one stated in the thread, I'm in the process of finding a Windows XP computer or borrowing a computer from one of my friends, anyone care to try this, or confirm other methods to bypass this?
omarachs said:
This thread is a process of how to potentially get your phone prepared for these steps:
http://forum.xda-developers.com/moto-x/general/tut-resurrecting-bricked-moto-x-corrupt-t2629057
If your device says USB Input device and then disconnects after a few seconds, There is a potential theory as to how to bypass that.
After buying a "Factory cable" for the moto X for 10$ I plugged it into my computer and nothing, So i noticed that it would 'unplug' after it "installed" the driver. So i plugged it into the USB slot in my pc and found out that the green light not only showed up, but stayed on for a constant hour! This means that the phone must somehow still be alive and charging. The reason behind this is the fact that the TV didn't install the driver, but simply sent current to the cord. The problem is that if you've already installed the driver on your pc once, it will always fetch that same driver to install the device again. The bypass to that would be finding a Windows XP computer that asks if you'd like to install the drivers first. Or a Win 7/8 Pc that hasn't been connected to the Moto X yet. Go to devices and printers: right click my computer -> Driver installations -> Never install using Windows Update. This should allow you to install your own driver which is the one stated in the thread, I'm in the process of finding a Windows XP computer or borrowing a computer from one of my friends, anyone care to try this, or confirm other methods to bypass this?
Click to expand...
Click to collapse
Did it work?
I have the same problem and i want to know if it has a solution. Also, is it necessary to have a factory cable?
viversba said:
is it necessary to have a factory cable?
Click to expand...
Click to collapse
Nope. Battery can be disconnected at all
Author, why start new topic? See existing.
+ driver pack for Moto + Qualcomm in attachment, for your needs )
But does this method work?
Could you bring yout Moto x back to life with this method?
viversba said:
Could you bring yout Moto x back to life with this method?
Click to expand...
Click to collapse
Yep. 95% rate, if not a hardware issue