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.

Win7 Auto Installs Wrong Drivers

Sorry, noob here. Please help!
My computer keeps on installing the wrong drivers everytime I plug in my Nexus 7. I don't know how to stop it.
When my tablet is in bootloader mode, Windows will try to install a bootloader interface driver that does nothing.
I have already:
- Went to Devices and Printers Installation settings and clicked on never install driver software
- Went to gpedit.msc and enabled: Prevent Installation of Devices not described by other policy settings,
So now my policy will block the auto install. But when I try to manually try to try Naked Drivers, it'll say it can't find any drivers.
When my tablet is in normal mode, the adb drivers comes back on.
I'm just trying to boot to recovery so I can install a new rom through the command prompt. Current rom is too unstable to do anything, new rom is already on the internal sdcard.
If any has any solutions, please let me know.
Thanks!

It sounds like you did things to prevent driver installation. But you need to install the correct drivers for things to work. Getting the correct drivers installed seems to be the biggest issue people have in being able to connect to a pc or use adb or fastboot. I know I installed the drivers from a root toolkit, installed rsd lite, android sdk, motohelper, etc. and still couldn't connect. Then I installed the pda.net app on the N7 and installed pda.net for android on my pc. Finally it worked and I can reliably connect to the pc, use adb and fastboot, and recognize the N7.
If all you are trying to do is get into recovery, why don't you just power off, hold the vol down and power until the screen comes on, use the up vol to change the menu to recovery, then hit the power button to enter recovery. Then you can wipe and flash. I hope I got those commands right. I'm using cwm recovery and I can get there like that. Usually, I just use Rom Manager to boot into recovery.

pdanet was what worked for me as well. none of the others did.
Sent from my Nexus 7

Thanks guys. that did the trick!
Sent from my Nexus 7 using xda app-developers app

[Q] MTP Mode Problem

After trying to Sideload the 4.4 Update onto my Wifi Nexus 7 (2012) I'm unable to connect to my Computer in MTP Mode & can only connect in PTP Mode which is far more limited than MTP Mode. I did a Factory Reset & updated to 4.4 OTA, but I'm now still unable to connect in MTP Mode, when I use MTP Mode I get a Google Nexus 7 ADB Interface in Device Manager with Manufacturer ID of ClockworkMod has anyone got any clues how to get MTP Mode working?
P.S. I'm unrooted and have no idea how the ClockworkMod ADB Driver got installed and haven't got a clue how to permanently remove it.
Roland

Rolandh said:
After trying to Sideload the 4.4 Update onto my Wifi Nexus 7 (2012) I'm unable to connect to my Computer in MTP Mode & can only connect in PTP Mode which is far more limited than MTP Mode. I did a Factory Reset & updated to 4.4 OTA, but I'm now still unable to connect in MTP Mode, when I use MTP Mode I get a Google Nexus 7 ADB Interface in Device Manager with Manufacturer ID of ClockworkMod has anyone got any clues how to get MTP Mode working?
P.S. I'm unrooted and have no idea how the ClockworkMod ADB Driver got installed and haven't got a clue how to permanently remove it.
Click to expand...
Click to collapse
Look in your PC's Control Panel - do you see Portable Devices (it's most likely missing or not showing up)
Folks over at Nexus 5 (I owned both devices) are running into similar problems - long story short, it's corrupted and/or missing usb devices drivers. Simplistic solution, use the computer (assuming you are running Windows 7 or Vista and not Linux) SYSTEM RESTORE feature & roll back to last few days, it should be a successful effort & then reboot. Reconnect your device, let it sit & recognize the device, install drivers, etc. - do this with USB debugging OFF first, and when it is done - enable USB debugging, let it finish.
Now, reboot PC again to be sure, and connect. usb cable again - give it 3 to 5 seconds, your Auto Play should be popping up with prompt to open folders/files, etc.
Check your CP again, you should now see Portable Devices part of the hardware, and Google Nexus 4 (yes, that's what is on mine)
Let me know if this solution works for you - the alternative is to uninstall all usb drivers, reboot, install, etc. etc. Please post your results if you choose to follow this dummy's approach, thanks.

XT320 setup wizard issue after flashing

Hi everyone,
I have a big issue after having flashed my XT320 : when it starts, I have a setup wizard failure (com.android.setupwizard) asking me to force closing it... and it does it again without ending (error message, close, error message, close..). The consequence is that I can't use my phone anymore (the weird thing is I see the incoming sms, but that's all).
The problem is that my phone is not detected by RSDlite anymore (and even by Motorola device manager). ADB isn't working when I try to connect when the phone is in USB mass storage mode (device not found), which could be normal as I can't enable USB debugging mode. The only thing I can do is power on the phone in recovery mode, then plug it to the PC, then use the terminal to make fastboot recovery (I used a custom recovery.img taken from xda). Thus, I might be able to reflash the phone with another ROM, but I am not sure... I figured I also could enable USB debugging mode with ADB, but I can't use ADB
Anyway, this is what I've done before I was stucked :
- enable fastboot (it wasn't)
- root my phone (ok)
- install CWM
- backup my data
- install CyanogenMod 7.2.zip and corresponding google apps on my SD card
- restart in recovery
- wipe data & cache
- choose install from sdcard option
- run cyanogenmod 7.2 and google apps
- reboot
If you have a genious idea, please tell me, I will be REALLY grateful !
Thanks
EDIT:
I have also installed Motorola Device Manager (and I am under windows 8). I was wondering if there was an issue with the drivers, but I tried to reinstall, reboot, with no changes... I also tried to force windows using the drivers in Motorola folder, but windows says the device won't work properly. I am quite sure there is a driver issue too (I've just tried to use Android root software, but the phone is not detected).

ADB phone access via Windows 10 (broken screen)

Unfortunately I broke the screen of my beloved 6P today and have spent the last 8 hours trying to figure out how to recover everything from it. It's still working as I can hear notifications and phone calls but the screen is blank.
After searching everywhere (xda, stackoverflow etc.), I'm a bit stuck and was wondering if anyone can help. Here's my plan/what I know:
1) I want to emulate the phone screen on my PC via USB using Android Control
2) I need USB debugging mode to access the phone via ADB
3) I need the correct (Google) USB drivers installed on my PC to access ADB
I have downloaded several tools/drivers and this is how far I got:
1) Windows sees/recognizes the phone under Devices and in Device Manager (as It does normally) - I am unable to access the phone because it's not in file transfer mode
2) When I run adb devices, the list is empty
3) I tried to update the driver to the latest Google USB driver but Windows 10 won't let me (windows has determined the best drivers etc. etc.)
I can't be sure what is blocking access via ADB. I'm sure I enabled USB debugging when I first got the phone but it was a long time ago. I read that I might need to disable Windows Driver Signing to install the latest Google driver but I haven't tried it yet.
My question is, how can I tell if it's USB debugging or the Driver? Any help would be greatly appreciated!

If you have your bootloader open, then this should be easy. You can install (if not already installed) TWRP recovery with "fastboot flash recovery file.img". When you then boot blindly into the recovery (its always the same amount of button presses in bootloader) then you can access the storage of your phone.
Other cheap solution: Get a phone with bootloop issue and use that screen from it. Then you have again a fully working phone.