Related
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.
Creating a troubleshooting thread to see if might be able to get some help on a big problem I'm having with my LG G2...
I'm trying to restore my VZ LG G2 to stock so that it can be returned (audio input is malfunctioning). I am currently running TWRP + CM 11 Nightlies on it.
When I enter download mode, I see the screen "Firmware Update" and it says "B99" and "Rooted" at the bottom.
When I use the R&D Test Tool + LGMobile Support Tool to try to restore to VS98011A_01.kdz, the software update runs on my computer as if it is pushing the update to the phone, but the phone itself shows no actual status change. It just sits there with 0% on the status bar.
When it finishes on my computer it says (on my computer) that the software update was successful. Unfortunately my phone boots into CM just like it normally does with all my apps and data there.
Based on some suggestions I have seen, I have tried manually changing to COM 41 and disabling the device as a modem in device manager -- does not make a difference.
I have no idea why no actual change is happening on the phone. Any suggestions?
Man, this is brutal. I thought that maybe the issue was that I was using the 3.10 LG United drivers instead of the 3.8 drivers, so I uninstalled 3.10 and installed 3.8.
Unfortunately now the LG G2 is recognized when it is in normal mode (running CM 11.0) but Windows shows "No drivers found" when I put it in download mode:
USB Composite Device: Ready to Use
CDC Serial: No drive found
CDC ECM: No driver found
LGE Android Phone: No driver found
Network Controller: No driver found
The last four all show up under "Other devices" in device manager with an exclamation.
Previously I was at least able to see the LG Android VZW etc. etc. under COM/Ports with 3.10 drivers installed.
I am burning so much time trying to figure this out. Mayday, mayday!
For anyone that may come across this thread in the future, I want to share what ultimately worked.
I followed the TOT method instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2448960
It was just as easy as the KDZ method, but actually worked! Here are the two things that seemed to make a difference:
1. I installed the _Verizon_ LG drivers referenced in that thread
2. I manually changed to COM41
Following all instructions in that thread everything worked like a charm.
Hi all,
I've broken my LG G2. I made an edit to build.prop and the phone stopped working. It will display the LG logo but then the screen goes black and the LED slowly flashes green/blue. I was running stock Rogers firmware, rooted, with a stock recovery.
I've performed a factory reset. Didn't fix anything.
I have tried to connect via ADB and fastboot but the phone isn't listed as a device.
I've tried using the LG Update program. The phone connects and is recognized but fails when reaching 4%.
I've used the LG Flash Tool 2014 but that fails at 2%.
When the phone is plugged into my computers, device manager shows it as: LGE AndroidNET USB Port (Com3) and LGE AndroidNET USB Modem. There is nothing else listed. I've tried installing all the recommended drivers; there is no change.
I have no idea what to do next. I'm hoping someone here can help.
deep6 said:
I have tried to connect via ADB and fastboot but the phone isn't listed as a device.... I've tried installing all the recommended drivers; there is no change.
Click to expand...
Click to collapse
Have you tried this driver? http://www.koushikdutta.com/post/universal-adb-driver As the page states, even when the manufacture offer their own drivers, ADB still won't recognize your phone as a device, sometimes. I had a similar experience and after installing this particular driver from Koush it recognized it. Hope it helps.
Dear all, I'm new here and just got my yotaphone 2 today, bought it locally from UAE, i beleive that the build ME refers to Middle East, got an android version of 4.4.3 YD201 model.
I thought that YD201 models are OTA updatable versions but seems not
Please can you guide me in a simple way how to update to lollipop? Noting that I've never flashed or done this before
Thank you so much..
https://forum.xda-developers.com/yo...grade-yotaphone-2yd206-running-4-4-4-t3506293
You can follow this guide fully but you don't need to flash HK first, so you just flash RU 5.0.0 firmware directly.
Caferatte89 said:
https://forum.xda-developers.com/yo...grade-yotaphone-2yd206-running-4-4-4-t3506293
You can follow this guide fully but you don't need to flash HK first, so you just flash RU 5.0.0 firmware directly.
Click to expand...
Click to collapse
Thank you so much.. Totally appreciate that.. But I don't know if it really matters as the tools relates to YD206 while I have YD201.. Should I proceed ?
By the tools do you mean YotaphoneFlasher? It works on both 201 and 206 since it's from official.
Thank you again.. OK I'm all set everything is ready but the only thing that's keeping me is drivers installation... Somehow the Google drive coming with the flasher is not being installed. I tried all ways possible, I.e. right click on the INF file and install but I get error message, and also tried to install it from device manager but couldn't. Can you please help with this? Thanks again
Btw I'm using Windows 7
Would you mind to post the srceenshot so I know your problem?
https://www.youtube.com/watch?v=R3wROHMJBDU This is the video of how you install driver
Caferatte89 said:
Would you mind to post the srceenshot so I know your problem?
https://www.youtube.com/watch?v=R3wROHMJBDU This is the video of how you install driver
Click to expand...
Click to collapse
my dear friend, i managed to update the driver, thanks to you, but it seems that when i power off the phone and enter the "downloading " mode on the phone screen then connect it to the computer it seems the phone is not being connected.. i used the flasher chosed option 1 "flash the cellphone" then i get the message "waiting for device" on the flasher..
i had a screenshot just to show that i have done everything i should (i guess) .. i.e. copied the firmware.. etc,,,
mindyou, i think the problem is that when i conncet the phone to usb it goes under other devices/Android which is not being recognized..
you are the best and thank you for your help again and again!
Weird. Do you've already install both drivers and restart your computer?
If yes, how about try to plug another usb port?
I got both ADB and Qualm drivers installed.. but nothing happening! I tried the 3 usb ports already..
I don't know how to solve this.. I think I need to try it on another computer .. maybe it'll work out!
Your driver not properly install. Try reboot pc, enable usb debugging at phone, plug in usb. See if there is any changes at device manager.
There is yellow triangle. So it mean.. Oh.. Oo..
If stilk not ok. Plug out usb from pc. At device manager, unsinstall both yellow triangle. Plug in back usb. So it will detect device and windows trying to install it.
If you have Windows 10 you have to disable signature driver verification, entering in the advanced boot menu of windows. After that the .inf driver will install.
I got the update at last and it's working beautifully smooth I downloaded universal driver from adbdriver.com and it worked perfectly. Thank you all guys for your help and efforts
Problem: The OnePlus 6T cannot boot into fastboot mode or ADB mode. When regularly booting, I get a "device is corrupt, can't be trusted" message. I achieved this by rooting my phone through suggested methods, then uninstalling Magisk, and locking my bootloader through the all in one tool. The all in one tool can no longer detect the device under any circumstance.
Attempted Solutions: I downloaded the MSM download tool and it says "Connected." The device shows as "Quallcomm HS-USB QDLoader 9005 (Com 5)" I also got it working for Com 6. The driver and connection appears to be fully functioning. USB debugging was enabled before I bricked my phone. When I start the download, I get stuck in the param preload phase, with the error message "DEVICE DOES NOT MATCH IMAGE." The "Verify" button works perfectly and says it's working.
I have downloaded every version of the MSMDownloadTool I could possibly find. I assume I have the most recent update of the OS -- It updated quite recently. I tried every single version I could find, including the most recent one (fajita_41_J.50_210121) and got this error every time. I know it's running Android 10, unless Android 11 for 6T is a thing.
I ran the program as an administrator.
I tried multiple USB ports, all with the driver properly installed.
I reinstalled drivers (signature patching is disabled and I don't assume drivers are the issue)
I restarted both the phone and computer multiple times.
I disconnected and reconnected the USB over and over, holding both volume buttons.
Why would I be getting a "device does not match image" and how can I bypass it to force the upload anyway?
I am using an INTERNATIONAL unlocked version. NOT a T-Mobile version. Since I can't access fastboot mode, I was not able to adjust certain settings. USB debugging was enabled, though, could this be the issue?
Hi,
Wrong Section please post in the correct thread to receive optimal answers.
arjunbalan1994 said:
Hi,
Wrong Section please post in the correct thread to receive optimal answers.
Click to expand...
Click to collapse
So what thread should this be posted in? Because I have the same problem/question and can't seem to find an answer. . .