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.

[Work in progress] Fixing a "Hard-Bricked" Moto X

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

[Q] Having driver issues in Download mode VS980

I have a rooted Verizon LG G2 that I somehow screwed up when going to Lollipop from KitKat. I have lost my 3G and LTE capabilities, thus no data unless connected to WiFi. From what I have read, it sounds like I need to try to revert to stock and start over. This is where I am having my major issues. I have tried the .kdz and the .tot methods of returning my phone to stock firmware. Upon placing my phone into Download mode on both a PC and a laptop (Windows 7 on both) my phone is at best recognized as a USB Modem Phone ADB Port, not the Port (COM LPT) that is required for either method to work. What can I do to get my phone to register as the Serial Port so that the LG Flash Tools will recognize it? (I have installed the most recent LG VZW Drivers and have uninstalled other drivers without any changes). Thanks

!bump having the same issue myself

Beeve said:
I have a rooted Verizon LG G2 that I somehow screwed up when going to Lollipop from KitKat. I have lost my 3G and LTE capabilities, thus no data unless connected to WiFi. From what I have read, it sounds like I need to try to revert to stock and start over. This is where I am having my major issues. I have tried the .kdz and the .tot methods of returning my phone to stock firmware. Upon placing my phone into Download mode on both a PC and a laptop (Windows 7 on both) my phone is at best recognized as a USB Modem Phone ADB Port, not the Port (COM LPT) that is required for either method to work. What can I do to get my phone to register as the Serial Port so that the LG Flash Tools will recognize it? (I have installed the most recent LG VZW Drivers and have uninstalled other drivers without any changes). Thanks
Click to expand...
Click to collapse
Screenshots, exact details, please. Maybe it's a simple driver fix or maybe it's a scary Qcomm diag mode issue (hopefully the good one). You've installed the latest drivers from LG, yes (3.12 or 3.13)? You often (usually) have to manually update the driver in Device Manager. Nothing listed under COM ports at all while the phone is in download mode?
Standard what-have-you:
Install latest LG Drivers (can be downloaded from LG support website).
Open Windows Device Manager and look under COM Ports for the LG device. Right-click on device, choose properties, and change the COM port to Port 41. Even if it says that port is already in use, do it anyways. This the port that LG Flash Tools uses to flash their stock images.
NOTE: Some tutorials will tell you to set your computers date back to make LG Flash Tools work: that is incorrect with version 1.8x and unnecessary, ignore them.
After the port is set to 41, unplug the USB cable from the phone, then open up LGFlashTools.exe. Select the correct VS980 .dll file and select the TOT file to flash. Press OK. Then press the yellow arrow in the upper left of the main LG Flash Tools window. It will think for a minute, then say Ready! or some such crap in the upper left port 41 box. Then you plug the USB cable back into the phone and it will start flashing. You do not have to wait until it reaches 100%, only until the phone fully boots up and presents you with the LG Setup Wizard (1st thing it asks for is your language preference). After you get there just close the LG Flash Tools program.
If it does not successfully flash:
-- Make sure you connect the USB cable directly to a motherboard port, do *not* use a hub.
-- Do not connect or remove others devices to your system until the flashing is done, as I've had that bork my flash before.

info
culot said:
Screenshots, exact details, please. Maybe it's a simple driver fix or maybe it's a scary Qcomm diag mode issue (hopefully the good one). You've installed the latest drivers from LG, yes (3.12 or 3.13)? You often (usually) have to manually update the driver in Device Manager. Nothing listed under COM ports at all while the phone is in download mode?
Standard what-have-you:
Install latest LG Drivers (can be downloaded from LG support website).
Open Windows Device Manager and look under COM Ports for the LG device. Right-click on device, choose properties, and change the COM port to Port 41. Even if it says that port is already in use, do it anyways. This the port that LG Flash Tools uses to flash their stock images.
NOTE: Some tutorials will tell you to set your computers date back to make LG Flash Tools work: that is incorrect with version 1.8x and unnecessary, ignore them.
After the port is set to 41, unplug the USB cable from the phone, then open up LGFlashTools.exe. Select the correct VS980 .dll file and select the TOT file to flash. Press OK. Then press the yellow arrow in the upper left of the main LG Flash Tools window. It will think for a minute, then say Ready! or some such crap in the upper left port 41 box. Then you plug the USB cable back into the phone and it will start flashing. You do not have to wait until it reaches 100%, only until the phone fully boots up and presents you with the LG Setup Wizard (1st thing it asks for is your language preference). After you get there just close the LG Flash Tools program.
If it does not successfully flash:
-- Make sure you connect the USB cable directly to a motherboard port, do *not* use a hub.
-- Do not connect or remove others devices to your system until the flashing is done, as I've had that bork my flash before.
Click to expand...
Click to collapse
LG site has latest VS980 drivers as 2.18
When I plug in my phone and download mode starts, Device Manager will intially show it under 'Other Devices' as 'Android'. Then it will load a generic Android ADB driver. If I hijack the driver install I can manually install an LG Port (COM and LPT) driver, but it will error upon install. It will still show with a yellow exclamation point. I can still change the Port here, but its the error that I think is holding everything up.
I've tried both the kdz and tot method to no avail.
I've tried on a PC, both front and rear USB ports, and a laptop (both USB ports) and no luck.
Any other info I can provide to you? Thanks for helping

Beeve said:
LG site has latest VS980 drivers as 2.18
When I plug in my phone and download mode starts, Device Manager will intially show it under 'Other Devices' as 'Android'. Then it will load a generic Android ADB driver. If I hijack the driver install I can manually install an LG Port (COM and LPT) driver, but it will error upon install. It will still show with a yellow exclamation point. I can still change the Port here, but its the error that I think is holding everything up.
I've tried both the kdz and tot method to no avail.
I've tried on a PC, both front and rear USB ports, and a laptop (both USB ports) and no luck.
Any other info I can provide to you? Thanks for helping
Click to expand...
Click to collapse
Stick to the rear USB ports on the PC, definitely. I've sometimes had it work via a hub, sometimes not (more often not).
So you've chosen the LGE AndroidNet driver, yes? And at this point you don't have the LG Flash Tools open yet, yes? It's best to keep that closed until after you've set the COM port to 41 (probably safe either way, but it does flag a conflict in com ports sometimes, which IME, doesn't matter, but still). While leaving the phone plugged into the USB, is that exclamation point still there after reboot? Screenshots? What error message does it provide under the devices status when you choose Right-click->Propertires(/Alt+Enter)?

Info
I've attached screenshots of the driver error as I install it and its properties. I've also attached shots of using the kdz method showing that nothing is detected when I press the phone information button, and also a shot of the error saying phone is disconnected when starting the flash process.

Beeve said:
I've attached screenshots of the driver error as I install it and its properties. I've also attached shots of using the kdz method showing that nothing is detected when I press the phone information button, and also a shot of the error saying phone is disconnected when starting the flash process.
Click to expand...
Click to collapse
Oh gosh, I'm sorry, I didn't see this reply! XDA sometimes notifies me of replies, sometimes it doesn't. Often it doesn't, grrrr! Are you still stuck here? lol. crap, so sorry.
EDIT:
Oh, when I was mentioning port 41 I think was thinking LG Flash Tools for TOT files, no the 2014 version (which I haven't used in a while).
But that's moot, thanks to the 'device cannot start' error. This should put it into perspective:
- Uninstall all the drivers for that, all LG drivers, all Android drivers, kill 'em all -- this includes uninstalling all LG smartphone software, too. (Note: using something like UninstallTool is always best (IObit has a bloatware-laden tool like that that's free), but surely the Windows Installer should uninstall fine.)
- Reboot.
- Reinstall LG Drivers with their installer.
- Boot device into Android then plug in USB.
Windows should do the usual finding drivers rigamarole, and if it's taking a long time (more than 30 seconds or so), unplug device, the Windows add drivers dialogs should disappear, then plug it back in.
- Check Device Manager to make sure the drivers automatically loaded up, check the details on each of the drivers to make sure it's the LG driver (since you should have no other LG or Android drivers installed at this point it should be).
- If exclamation point next to device, the do the update driver thing and choose the correct LG driver.
- Reboot Windows.
- Unplug device.
- Put device in 'Download Mode' and connect USB (use motherboard ports if on desktop, not hub or case ports; never had port problem on laptop).
- Check Device Manager to see if drivers auto-found it (usually not, for me).
- Update them to LG drivers.
Is the driver still throwing up errors at this point?
Oh, when in Device Manager, select the device, then choose from the menubar View->Device by Connection. It will show the other drivers loaded for that device, and more importantly, it will show just where the device is connected to. A screenshot of that would be mucho helpful if your problem still persists.
Again, sorry I didn't get back to you. D:

Ha ha, I wasn't notified of this either. I never did get it to work. Because what I was really looking for was to get my radios working again, I had another member suggest going to a ;stock-ish' rom and flashing it (xdabbeb) along with the 12b bootstack. Lo and behold this worked for me. I was able to get my phone to show up via ADB so that I could push the files over. I never could get the .tot or .kdz to work, but I don't have the need to continue on at this point.
Thanks for your help though!

hello BEEVE i have screwed my lg g2 in the same way so can you please tell me how did you fix it or give me a link or something anything is fine
thanks in advance

I ended up flashing to a Rom that was based on stock LG. Been awhile so I don't remember. It seemed to help after a while. I also used the LTE Discovery app whenever I wasn't using my phone. The thought was that it would trick it into working. I think what actually ended up working was time. It just eventually started working better. Maybe a combination of everything, I don't know. I no longer use the phone so it's a little sketchy.

Computer not recognising Lenovo K30-W

I have a bricked Lenovo K30-W I'm trying to fix (freezes on startup). My computer (Windows 10) won't recognise it when I connect it to the USB port. In device manager, the phone is displayed as unknown, with error "Device descriptor request failed". I tried connecting to different USB version ports, I tried installing multiple different drivers and software, but nothing helped. Adb doesn't recognise it as well, even if I boot the phone to fastboot with volume+power buttons. Any other ideas? Thanks.

Update: problem seems fixed. I used another USB cable and plugged it into an older version USB port. It is now recognised.

Moto e4 usb issue

I have a moto e4, so I have SO issues so I have been trying to use the save to repair but the pc does not recognize the phone, the problem phone does not recognize that it is connected to a pc, I tried several computers with different cables and nothing, the pc does not recognize it in fast boot mode nor does the android sdk