Okay here is how you enable DIAG Mode on the Nexus 4:
su -c 'setprop usb.sys.config diag,adb'
And to restore MTP Mode:
su -c 'setprop usb.sys.config mtp,adb'
Note: You must be rooted in order to issue the above commands.
Now for the hard part. Although enabling DIAG Mode is easy, finding the Qualcomm diagnostic drivers for this device on the other hand is not and without these we cannot do much more.
If anyone can get these drivers or has the knowledge to patch Samsung's drivers to enable the Diagnostic Serial Port then please get in touch.
Sent from my Nexus 4 using Tapatalk 2
My first guess for obtaining the drivers would be LG.
I hopped on their site, looked for the OG resources and downloaded them; they do include generic diag drivers.
I thought I'd just try and see if they worked for a N4 in diag mode, but your command did nothing as far as I could see on a non-stock ROM.
The Nexus still shows up with MTP access, and enumerates with the same VID and PID, with and without USB debugging enabled that is.
Next step would probably be having a look at the Optimus G's driver entries and changing them to the N4's, if we could see what the N4 enumerates with.
If that makes sense to any of you.
Good old Motorola days, weeks spent sifting through their OMAP bootrom drivers.
Well here is a link to the USB initialisation rc script source code:
https://android.googlesource.com/de...974430a67da4878c61de0970b56f/init.mako.usb.rc
Here we can see exactly what gets changed when setting property sys.usb.config to diag,adb.
As you can also see we also have the ID and vendor info to modify another devices driver with.
Let the games begin!
Sent from my Nexus 4 using Tapatalk 2
lyriquidperfection said:
Well here is a link to the USB initialisation rc script source code:
https://android.googlesource.com/de...974430a67da4878c61de0970b56f/init.mako.usb.rc
Here we can see exactly what gets changed when setting property sys.usb.config to diag,adb.
As you can also see we also have the ID and vendor info to modify another devices driver with.
Let the games begin!
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Without changing anything in LG's drivers it already recognized LGE AndroidNet For Diagnostics Port (COM3) and AndroidNet USB Serial Port (COM4), but it got stuck on a CDC serial driver.
And right when I'm typing this and downloading QPST the phone reboots.
But you should have a go at LG's drivers, they already seem to work partly.. I'm going to put it in diag mode again and see how QPST responds.
Yup, both ports are basically recognized, though I'm lacking knowledge of QPST.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm guessing the first one is the modem?
The read out on it works flawlessly (after figuring out that an unlocked phone probably has no MSL/SCP) with a QPST version you uploaded last year (what a coincidence!), but I can't connect to the QC apq8064 and I don't know whether I'm even supposed to. But a newer QPST version would be worth a shot.
But like I said, I'm seriously in over my head.
Thanks a lot for doing this. This certainly gives me something to work on!
Sent from my Nexus 4 using Tapatalk 2
Would this allow us to unbrick a nexus 4? Or perhaps unlock radio bandwidths for use on LTE networks ? I am not familiar with qpst I think I used it once to flash a droid to cricket.
Kaffeekranz said:
Without changing anything in LG's drivers it already recognized LGE AndroidNet For Diagnostics Port (COM3) and AndroidNet USB Serial Port (COM4), but it got stuck on a CDC serial driver.
And right when I'm typing this and downloading QPST the phone reboots.
But you should have a go at LG's drivers, they already seem to work partly.. I'm going to put it in diag mode again and see how QPST responds.
Yup, both ports are basically recognized, though I'm lacking knowledge of QPST.
I'm guessing the first one is the modem?
The read out on it works flawlessly (after figuring out that an unlocked phone probably has no MSL/SCP) with a QPST version you uploaded last year (what a coincidence!), but I can't connect to the QC apq8064 and I don't know whether I'm even supposed to. But a newer QPST version would be worth a shot.
But like I said, I'm seriously in over my head.
Click to expand...
Click to collapse
OK I installed the LG Drivers but still a no go for me. Can you have a look in your device manager and tell me what driver name goes with each PID & VID.
Thanks in advance.
Sent from my Nexus 4 using Tapatalk 2
Isn't qpst for cdma phones? I've never used it on a GSM phone, only sprint and cricket phones.
scottx . said:
Isn't qpst for cdma phones? I've never used it on a GSM phone, only sprint and cricket phones.
Click to expand...
Click to collapse
Not necessarily. Advanced functions maybe but I used QPST on my Samsung SGS3 LTE I9305 which was GSM but as it used a Qualcomm Modem I was able to backup and restore nv items in diag mode.
This is what I am trying to achieve with the Nexus 4.
I also think having access to the nv area will allow us to tinker with other things.
Sent from my Nexus 4 using Tapatalk 2
lyriquidperfection said:
OK I installed the LG Drivers but still a no go for me. Can you have a look in your device manager and tell me what driver name goes with each PID & VID.
Thanks in advance.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Does it even pick up on the additional devices?
It was pretty straight forward for me, besides getting into diag.
I first enabled USB debugging, then terminal
su
setprop sys.usb.config diag,adb
Afterwards I connected the phone and my Win7 x64 PC already started installing the LG diag drivers.
But I'll have a looksie what drivers and VID/PID it uses specifically when I'm back home tonight.
(And I deleted the standard N4 ADB drivers first, but I doubt that made a difference)
Didn't install anything for me. I just have 4 devices. 3 say Nexus 4 and one says CDC Serial.
Sent from my Nexus 4 using Tapatalk 2
What's the goal with the diag mode here? lg uses lgnpst for their phones, and we have a thread on here somewhere that has stock roms in that format, if anyone wants to try it out. You can get your nexus in download mode(vol buttons combo) and potentially revive a bricked device.
Edit: here's the thread. http://forum.xda-developers.com/showthread.php?t=1976057
RussianBear said:
What's the goal with the diag mode here? lg uses lgnpst for their phones, and we have a thread on here somewhere that has stock roms in that format, if anyone wants to try it out. You can get your nexus in download mode(vol buttons combo) and potentially revive a bricked device.
Edit: here's the thread. http://forum.xda-developers.com/showthread.php?t=1976057
Click to expand...
Click to collapse
Thanks for the info. I have already been looking into this however as QPST is specifically for Qualcomm chipsets you can potentially do alot more with it. LG's Tool is quite restricted in many respects.
Sent from my Nexus 4 using Tapatalk 2
lyriquidperfection said:
Thanks for the info. I have already been looking into this however as QPST is specifically for Qualcomm chipsets you can potentially do alot more with it. LG's Tool is quite restricted in many respects.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
What are you trying to accomplish? I could point you towards a few very good threads on here. Different chipsets, but goes deep into some Qualcomm stuff.
RussianBear said:
What are you trying to accomplish? I could point you towards a few very good threads on here. Different chipsets, but goes deep into some Qualcomm stuff.
Click to expand...
Click to collapse
Mainly backing up and restoring of all nv items etc. I have a program I made that can communicate with Qualcomm chipsets which allows IMEI repair etc so im really looking to make Nexus 4 work correctly with it then I will release to the masses for testing etc.
Sent from my Nexus 4 using Tapatalk 2
I can't seem to get my computer to recognize DIAG mode after entering the command in terminal emulator. I tried uninstalling the ADB drivers and tried it without touching them. Any tips?
Check this post for drivers: http://forum.xda-developers.com/showthread.php?p=40195799
Asus padfone2 has the same apq8064 chipset.
Can't test, as I'm at work.
lyriquidperfection said:
Thanks for the info. I have already been looking into this however as QPST is specifically for Qualcomm chipsets you can potentially do alot more with it. LG's Tool is quite restricted in many respects.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
did you ever get this working?
sucsss said:
did you ever get this working?
Click to expand...
Click to collapse
Yes I have it working and can backup nv in QPST but restore always fails at 9 percent.
To get device recognised in diag mode you must install the latest LG United USB drivers then place phone in diag mode as per the first post.
Sent from my Nexus 4 using Tapatalk 2
lyriquidperfection said:
Yes I have it working and can backup nv in QPST but restore always fails at 9 percent.
To get device recognised in diag mode you must install the latest LG United USB drivers then place phone in diag mode as per the first post.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I have found that restoring certain nv values causes errors on some phones. I think it is a protection system. If you an figure out where exactly it is failing, you might have success skipping over the trouble nv values.
Related
So I have the OTA ICS update now. I want root again (didn't have it previously on this phone), so I decided I would try one of the "1-click" scripts. My problem now lies in my PC (win 7 64bit) and drivers I think. Downloaded the motorola utility to get all my correct drivers. When I plug up my phone, my pc downloads all the drivers, but it never downloads the Mot ADB interface one. I'm stumped. I've tried it on all 3 machines. I can transfer files and the phone mounts ok OTHER THAN the adb interface.
When I run adb shell it says "error: device not found"
Here's what I have done.
1. Uninstalled all my drivers
2. Re-installed all the drivers
3. Tried every USB port on the computer
4. Made sure USB Debugging was checked
5. Made sure my phone was in Media mode
6. Wiped cache and data
7. Tried it on other machines
8. Re-installed windows on 1 machine.
When I put the phone in AP Fastboot, then and ONLY then will the PC see the phone as an adb interface.
Any thoughts?
I think you need to switch it to a pc mode other people have said.
Sent from my GT-I9300 using xda premium
You use USB 2.0 ports?
Zanith said:
I think you need to switch it to a pc mode other people have said.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
on the new ICS update there isn't a PC mode.
HSD-Pilot said:
You use USB 2.0 ports?
Click to expand...
Click to collapse
yes.
Here's what my device manager looks like. As you can see, it has NO option of ADB anywhere! Thinking it might be this phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jdenman03 said:
Here's what my device manager looks like. As you can see, it has NO option of ADB anywhere! Thinking it might be this phone.
Click to expand...
Click to collapse
This is what you should see:
pedrotorresfilho said:
This is what you should see:
Click to expand...
Click to collapse
You are correct. But its not prompting me even to install the adb interface. Thus the reason why I feel as though it is the phone and not the PC's. I run adb on my other phones just well.
Try typing
start adbd
In terminal emulator in your phone?
Sent from my GT-I9300 using xda premium
I'm going to assume you tried this link to get the drivers:
http://forum.xda-developers.com/showthread.php?t=1539192
If not, uninstall all the drivers you have currently and reboot and then go to the link above and get the Moto drivers and RSD Lite.
Another link is here which really gets in-depth on getting ADB to function:
http://www.droidrzr.com/index.php/t...find-out-how-to-manipulate-your-system-files/
Zanith said:
Try typing
start adbd
In terminal emulator in your phone?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
this doesn't do anything.
iBolski said:
I'm going to assume you tried this link to get the drivers:
http://forum.xda-developers.com/showthread.php?t=1539192
If not, uninstall all the drivers you have currently and reboot and then go to the link above and get the Moto drivers and RSD Lite.
Another link is here which really gets in-depth on getting ADB to function:
http://www.droidrzr.com/index.php/t...find-out-how-to-manipulate-your-system-files/
Click to expand...
Click to collapse
tried this and still failed. I've done it now on 5 machines. All have the same issue. None of them ever prompt me to install drivers for adb interface. terminal emulater doesn't do anything on my phone either. Bout to take my phone to verizon.
OK I am running emulator on my phone, and when I enter command "adb shell" adb starts and still says "error: device not found"
gonna throw this phone to the wall. Thanks for all the suggestions and help thus far. If I can't get it fixed by tonight, i'll take it to verizon tomorrow and have them send me a replacement.
EDIT: Plugged in my wife's razr with usb debugging and everything worked correctly. DEFINITELY the phone! Can't believe I have wasted this past 2 days on this!
I am having the SAME EXACT problem running the same version of Windows. I'm guessing you haven't found a work around as of yet, eh? I still have been unable to get Windows to recognize the ADB interface. Whenever I connect my Bionic, it finds/installs it just fine, but not so much with the Razr Maxx.
Have you attempted a factory reset at all? The issue began with me because I rooted the device, used OTA rootkeeper, installed the OTA, but then Rootkeeper was unable to restore root, so I also tried to use the 1-click scripts.
jdenman03 said:
OK I am running emulator on my phone, and when I enter command "adb shell" adb starts and still says "error: device not found"
gonna throw this phone to the wall. Thanks for all the suggestions and help thus far. If I can't get it fixed by tonight, i'll take it to verizon tomorrow and have them send me a replacement.
EDIT: Plugged in my wife's razr with usb debugging and everything worked correctly. DEFINITELY the phone! Can't believe I have wasted this past 2 days on this!
Click to expand...
Click to collapse
I had the same issue.. You need to download Matts utility 1.7 and then extract the zip into an (empty) folder. Then click the first file in your folder and click on the 64 bit. Let it install then run the utility.. Make sure your device is in USB debugging mode and that you have your storage device set to mtb.. Then click the root android 4.0.4 option and let the program to the rest! I hope this helps it sure helped me.
Sent from my DROID RAZR using xda app-developers app
I had a very similar issue that was stopping me from re-rooting after I pulled the official OTA. At the end of it, my problem seemed to also center on not having the Mot Composite ADB Interface driver install when I connected the device by USB. I was running Moto Drivers ver. 5.7.0 (current) and successfully connected on other RAZRs, just not my current one. Same 'device not found' errors.
Connecting my device as a camera (PTP) fixed the problem (settings -> storage -> press the menu key and choose Camera (PTP). After doing that, windows installed the additional devices: USB Composite Device, DROID RAZR, and Mot Composite ADB Interface and I was back on track. Regardless of what I tried otherwise (including a wipe data) the ADB interface just wouldn't install until I connected as a camera.
My post is here:
http://forum.xda-developers.com/showthread.php?t=1743367&highlight=root+ota&page=2
EDIT: Just re-read the OP. Not just close. Sounds like you're having the SAME problem. Hope this helps.
At first I could not get this script to work. Apparently I had no ADB interface installed. What did the trick for me, was switching off the USB debugging, plugging in my Droid 4 a few times in camera, MTP and mass storage mode. That made my computer install all the necessary drivers.
Having done this, it all worked perfectly. Thank you very much! I am completely new to Android and XDA, and this almost foolproof script is excellent. :good:
So simple..
Had same problems with my new phone as everyone else, PC not recognizing ADB .... tried downloading a couple of different things from other advice as I don't know much about computers this just got confusing. All I had to do was turn off the USB debugging, plug in under the different USB computer connections and ta da!
No Storage Drives Show
Hi everyone.
First time I post on the forum, although I've been using it for quite some time.
This time I'm experiencing an annoying situation with which I spent many hours of my last two days.
Turns out my Windows (7 64-bit) won't display the mass storage drives from my Droid Razr (XT910 Model, Brazilian Carrier OTA).
The funny thing is that all Motorola Drivers are shown on Device Manager and when in AP Fastboot Mode, RSD will recognize the phone as connected and flash normally.
I am really out of ideas here. Did religiously everything written on this forum and many others:
Tried different cables and pcs
ReInstalled ICS OTA
Wiped cache/data
Factory Reset from Android
Tried to connect as Camera, Media and Mass Storage
Tried with USB Debugging both on and off
One thing that may have caused the problem, from what I recall, is I am running without the cid file, as I deleted it to install JellyBean through the steps suggested by "TheRazRGuy" here on xda.
Thing is, as I don't have the cid, I must boot through BPTools on bootmanager everytime the system is turned on. After I downgraded the JellyBean to ICS OTA again, I went on to root the device but forgot about the boot requirement I described.
After the easyroot first reboot, the screen went black as always when normal reboot without cid. Even though easyroot still rebooted 2 more times and displayed the "your phone is rooted" message, I thing something may have gone wrong on this process.
It is worth saying that with JB the mass storage was being shown and before the easyroot process too..
I am really out of clues here, hope someone can help!
Found a solution on another thread:
http://forum.xda-developers.com/showthread.php?p=36543010#post36543010
Just had to modify an option on BootMenu Manager
I have an HTC Droid DNA that I hope to get switched over to MetroPCS. I have done this several times so I thought it would be no problem, but then I ran into a problem. No program I have tried (QPST, CDMA Workshop, DFS) can connect through the com port. The drivers are installed correctly and I tried updating them to no avail. Tried different usb ports and cables. Tried uninstalling and reinstalling drivers. Uninstalling and reinstalling htc sync. When i go into qpst configuration to add the port it sees it but doesnt have any info and when i open the service programming it doesnt detect a phone at all. In CDMA workshop it connects to the port but when I try to read the info it just comes back with garbage data and it gives an error when I try to send the SPC. Also the "HTC 9K DEV" isnt installed but I've heard it has something to do with LTE so that shouldnt matter right? are there drivers for this? I've been searching but haven't found anything that helps :/ Any help appreciated...
ZERO16LIVES said:
I have an HTC Droid DNA that I hope to get switched over to MetroPCS. I have done this several times so I thought it would be no problem, but then I ran into a problem. No program I have tried (QPST, CDMA Workshop, DFS) can connect through the com port. The drivers are installed correctly and I tried updating them to no avail. Tried different usb ports and cables. Tried uninstalling and reinstalling drivers. Uninstalling and reinstalling htc sync. When i go into qpst configuration to add the port it sees it but doesnt have any info and when i open the service programming it doesnt detect a phone at all. In CDMA workshop it connects to the port but when I try to read the info it just comes back with garbage data and it gives an error when I try to send the SPC. Also the "HTC 9K DEV" isnt installed but I've heard it has something to do with LTE so that shouldnt matter right? are there drivers for this? I've been searching but haven't found anything that helps :/ Any help appreciated...
Click to expand...
Click to collapse
Are you running the stock ROM, what OS are you on, does this require adb? Just a few basic things. The DNA sometimes seems to have problems communicating so need to know some things.
Chyrux said:
Are you running the stock ROM, what OS are you on, does this require adb? Just a few basic things. The DNA sometimes seems to have problems communicating so need to know some things.
Click to expand...
Click to collapse
Sorry, I knew I forgot to put something haha. I was on the stock Rom, tried unrooted then rooted just in case. I'm on FactoryROM now with the same result. My os is win 7 ultimate and I don't believe it requires adb but it does work with adb. Man I hope I can get this working, I already love this phone...
Thanks
So I tried it on a fresh win7 installation and still nothing so im going to try a different version. I'm currently using version 2.7 build 362 what do you guys use? do you possibly have a link?
EDIT: Tried build 366 and its the same. I tried build 378 and it says APQ8064 under phone 0 for esn and phone number and banner are blank and when i try to connect it says "online connection error: unspecified error" but at least it sees the phone now... Is there like a special way you're supposed to connect this phone or something? I have been doing it the same way i did my HTC Droid Eris, HTC Evo Shift 4G, and HTC Evo 3D...
EDIT2: Just found out that APQ8064 is the model number for the Snapdragon processor in the Droid DNA so at least it is seeing the phone and recognizing it...
HTC Sync supposedly (I haven't tested this) causes interference with the communication you need for the rooting exploit. Maybe it's also causing interference with the programs you're trying to use.
Just a thought.
M0rtiferrimus said:
HTC Sync supposedly (I haven't tested this) causes interference with the communication you need for the rooting exploit. Maybe it's also causing interference with the programs you're trying to use.
Just a thought.
Click to expand...
Click to collapse
thanks, worth a shot.
I'm an idiot, all i had to do was install the driver for htc 9k diag and use that port instead... Wow, i feel dumb.
Merry Christmas and thanks for the help
EDIT: Nope nevermind still doesnt work...
Do you have USB debugging enabled?
yeah it is.. ugh I'm out of ideas...
Try turning USB debugging off. If that doesn't work, you could try resetting your phone.
If that still doesn't work, your computer may have downloaded faulty drivers. PM me and I can send you the ones from my phone, if you want.
M0rtiferrimus said:
Try turning USB debugging off. If that doesn't work, you could try resetting your phone.
If that still doesn't work, your computer may have downloaded faulty drivers. PM me and I can send you the ones from my phone, if you want.
Click to expand...
Click to collapse
I'll give it a shot. I don't think its the drivers though, I tried different ones just in case but these work with my other phones...
ZERO16LIVES said:
I'll give it a shot. I don't think its the drivers though, I tried different ones just in case but these work with my other phones...
Click to expand...
Click to collapse
I'm having the same issue. Did you ever figure it out? CDMA WS, DFS, and QPST aren't letting me write to the device.
I have a brand new bone stock dinc 4g lte.
I have activated sim and all features of phone work except when trying to connect via DIAG (##3424#).
Phone enters diag mode just fine.
USB debugging is enabled; Charge only is the PC connection.
My laptop is windows xp 32-bit.
I have installed the HTC Drivers: HTCDriver3.0.0.007
However, whenever I plug the phone in it recognizes new hardware: "Android Phone" and "HTC DIAG"
But after clicking "Install software automatically" it searches and then fails (even though I know the drivers are there).
When not in diag mode I can see my memory card and transfer files back and forth so I know part of the drivers are working.
What am I doing wrong?
*I found my own solution so I thought I'd post it just in case anyone else had my same problem.
1) I followed all the steps in the procedures listed in this thread, but needed to "disconnect my phone" before clicking "have disk".
This allowed me to successfully install drivers and connect to QPST. However.........
2) When I was connected QPST showed a question mark in front of my ESN. So I read and found that for this phone we need v2.7 build 3.74.
This did the trick!
3) I can verify that the "open sesame door" procedure works on this phone! Now can anyone confirm that it works for the Verizon HTC One also?
Read here
Thanks for replying so quickly! I'm glad to see you still use this phone.
I actually looked at that very thread before I started this one. QPST does not see the phone, so there aren't any phones listed when I try to add the port. So I can't click the "read phone" step in your directions because it's grayed out..
I've tried a different cable and different xp computer, and still can't load drivers!
Any other suggestions?
You should notice the diag drivers are not the same as the 3.0.0.007 drivers. Check that post I linked again.
Sent from my Incredible 4G LTE using Tapatalk 2
Are you talking about this link?
>When you have QPST installed Proceed to get your HTC Diagnostic Drivers, you can get them HERE
If so, that is what I've tried and hasn't worked.
Are there other driver download links in that thread I am missing?
I also tried all of the drivers you had stickied, but none worked.
This is very frustrating. Any other ideas?
supermaxkato said:
Are you talking about this link?
>When you have QPST installed Proceed to get your HTC Diagnostic Drivers, you can get them HERE
If so, that is what I've tried and hasn't worked.
Are there other driver download links in that thread I am missing?
Click to expand...
Click to collapse
Strange, I remembered the drivers posted to that thread being correct. In any case, a simple google search for "htc diag drivers" brings this up as the first result: http://forum.xda-developers.com/showthread.php?t=697487
If there is a thread with diag drivers then I've looked at it. So yes I looked at that post already. But maybe there is another way to connect to qpst without diag drivers? Or is it possble that I don't have something enabled correctly on this brand new phone?
Is there another way to create a virtual com port besides using dm router?
instead of automatic install have you tried doing it manually.
choose drivers, navigate to file, update driver?
synisterwolf said:
instead of automatic install have you tried doing it manually.
choose drivers, navigate to file, update driver?
Click to expand...
Click to collapse
Yes; I've followed this exact same process many times.
I just did it again (re-downloaded the files from the link you posted).
HIs instructions show windows 7 and I have xp, but it shouldn't matter.
When I choose his x86 drivers it always gives me this error:
HTC DIAG
When it finds new hardware "HTC DIAG" pops up in all caps.
Are drivers case sensitive?
Because all of the drivers I am manually choosing are lower case.
Could it be that is why they don't "contain information about my hardware?"
BTW, I have installed HTC diag drivers on this laptop (and my desktop) for my incredible 2 and have no problems connecting. So I'm struggling to understand why this one is so difficult!
Mine was for the evo LTE not the incredible LTE
Going home in a few, I'll see if I can get it to work and I'll report back.
Sent from my iPhone 5 using Tapatalk 4 beta
Thanks so much for your help!
Do you have a windows XP you can test it on?
I've tried 2 XP machines (both with SP3) and 2 different cables, but no luck.
I'm so glad people actually try to help on this forum (unlike some other forums).
It's been a few days; anyone able to help this phone work with windows xp? My incredible 2 was a breeze compared to this one.
Thanks to anyone who might be able to help!
So I tried searching google and the forums and found nothing.
So on multiple PC's it will charge my DNA but it will not detect it in device manager, like it's not plugged in at all. Almost like it's not seeing any RX/TX Just VCC and Ground. I've tried 3 different Pc's and probably 10 different USB cables. Multiple roms and it will not even see it in bootloader. Not sure if anyone else has experienced this issue, it's been going on for months, I can do pretty much everything without USB access to my phone but if I want to RUU I'm going to be SOL.
Any thoughts?
yutsoku said:
So I tried searching google and the forums and found nothing.
So on multiple PC's it will charge my DNA but it will not detect it in device manager, like it's not plugged in at all. Almost like it's not seeing any RX/TX Just VCC and Ground. I've tried 3 different Pc's and probably 10 different USB cables. Multiple roms and it will not even see it in bootloader. Not sure if anyone else has experienced this issue, it's been going on for months, I can do pretty much everything without USB access to my phone but if I want to RUU I'm going to be SOL.
Any thoughts?
Click to expand...
Click to collapse
What operating system are u using? I started a thread about windows 8 not seeing the dna in bootloader. it happens because htc has not updated the drivers for windows 8
heres the link http://forum.xda-developers.com/showthread.php?t=2521504
Win7 and linux... Think its a phone issue. Well I'm 99% sure
Sent from my HTC6435LVW using Tapatalk
Do you have drivers installed and can you boot into recovery and mount ur device? You may need adb installed. Do you have SDK drivers installed.
Another good way to get ur computer to see ur phone is to download pdanet and it will install the needed drivers to see ur phone.
thayl0 said:
Do you have drivers installed and can you boot into recovery and mount ur device? You may need adb installed. Do you have SDK drivers installed.
Another good way to get ur computer to see ur phone is to download pdanet and it will install the needed drivers to see ur phone.
Click to expand...
Click to collapse
i have done all that. i can adb into bootloader but once in bootloader the computer does not recognize the phone anymore.
thayl0 said:
Do you have drivers installed and can you boot into recovery and mount ur device? You may need adb installed. Do you have SDK drivers installed.
Another good way to get ur computer to see ur phone is to download pdanet and it will install the needed drivers to see ur phone.
Click to expand...
Click to collapse
Not quite understanding, it's not a driver issue... The PC it's self will not see the device. Not even in device manager as an unknown device, the phone it's self will not say, "Hello PC I am here, do you have my drivers?" I plug it in, get nothing as if I am using a charging cable with only VCC and ground, without RX/TX. I'm pretty positive that it's a phone issue, not a PC/Driver issue. Even if it was a driver issue I'd be getting the MTP device showing up.
yutsoku said:
Not quite understanding, it's not a driver issue... The PC it's self will not see the device. Not even in device manager as an unknown device, the phone it's self will not say, "Hello PC I am here, do you have my drivers?" I plug it in, get nothing as if I am using a charging cable with only VCC and ground, without RX/TX. I'm pretty positive that it's a phone issue, not a PC/Driver issue. Even if it was a driver issue I'd be getting the MTP device showing up.
Click to expand...
Click to collapse
Actually it could be a driver issue. There has to be a driver installed for something to notice something.
Go to device manager and look at the very top when you connect your phone does it show this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Or the driver could be corrupted and you tried to uninstall and reinstall
thayl0 said:
Actually it could be a driver issue. There has to be a driver installed for something to notice something.
Go to device manager and look at the very top when you connect your phone does it show this?
View attachment 2408658
Or the driver could be corrupted and you tried to uninstall and reinstall
Click to expand...
Click to collapse
Driver isn't installed on my work PC still nothing. Tried driver on work PC...still nothing :/
Sent from my HTC6435LVW using Tapatalk
yutsoku said:
Driver isn't installed on my work PC still nothing. Tried driver on work PC...still nothing :/
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
Heres what I just had to do because my phone wasn't being seen by my pc.
http://www.youtube.com/watch?v=oaNM-lt_aHw
Do that and after boot into recovery and mout the system is should reinstall the correct driver.
Confirmed it's not drivers my phone can't see USB otg either. Probably my phone is defective
Sent from my HTC6435LVW using Tapatalk
yutsoku said:
Confirmed it's not drivers my phone can't see USB otg either. Probably my phone is defective
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
I find that to be very rare but okay best the luck to you.
Hello, I'm having a few different issues when I go to install the latest 4.4.3 (or any for that matter) RUU. I've connected my phone to my laptop and downloaded HTC sync and have automatically updated the drivers. However when I go to actually install the ruu, the usb disconnects and I'm forced to hard reset the phone to get it unstuck. I've tried this with two different USB cords and two separate computers. Any advice? Stuck without service and I'd really like to see UPSM and boomsound improvements. This is completely stock. Thank you
What OS. USB 3.0 ports or 2.0…?
Win 8.1 with USB 3.0 ports can be finicky to get it to work just right.
- Sent from a payphone ...
tommy_riley said:
What OS. USB 3.0 ports or 2.0…?
Win 8.1 with USB 3.0 ports can be finicky to get it to work just right.
- Sent from a payphone ...
Click to expand...
Click to collapse
Both are running Windows 7. I'm not sure on the USB ports, I believe they're 2.0
What hboot numbers is the phone currently on?
It is the AT&T branded version M8, correct? I only ask, because folks sometimes come on here trying to flash an AT&T RUU on another version device.
Any error messages when the RUU fails?
redpoint73 said:
What hboot numbers is the phone currently on?
It is the AT&T branded version M8, correct? I only ask, because folks sometimes come on here trying to flash an AT&T RUU on another version device.
Any error messages when the RUU fails?
Click to expand...
Click to collapse
The # is 3.16.0.000. The errors I receive are 170 & 171, something about the usb disconnectingand to check it and try again.
Sounds like a driver issue. Uninstall HTC related drivers and install the drivers from adb or the google drivers.
- Sent from a payphone ...
tommy_riley said:
Sounds like a driver issue. Uninstall HTC related drivers and install the drivers from adb or the google drivers.
- Sent from a payphone ...
Click to expand...
Click to collapse
Just tried this as suggested abd still getting the same error. I get far enough that I can accept the version update on the ruu, the phone displays "HTC" against a black screen, and the usb disconnects. I uninstalled all the drivers and after I plugged in the cord, the sync manager said it was updating the drivers. Should o uninstall sync manager and try again?
Yeah get rid of sync manager. After its gone try the alternative drivers and make sure the phone comes up correctly in device manager then try RUU again. It might be a matter of trying a few different driver vs RUU combinations.
If the system only has USB 3.0 ports and its an Intel chip set then you might also try and go install the latest Intel USB port drivers directly from their website. If the USB port drivers are outdated or if Microsoft has their drivers in for USB instead of Intel's (on 3.0 ports only most of the time) what will happen is everything will look fine with connection to phone via USB from computer but once you are in recovery or fastboot mode the connection will be lost.
I can give more specifics if you want to go down this route much later in the evening with screen shots and driver locations if needed, I'm just on my phone ATM on my way to work. So it would be much later tonight. Let me know...
- Sent from a payphone ...
tommy_riley said:
Yeah get rid of sync manager. After its gone try the alternative drivers and make sure the phone comes up correctly in device manager then try RUU again. It might be a matter of trying a few different driver vs RUU combinations.
If the system only has USB 3.0 ports and its an Intel chip set then you might also try and go install the latest Intel USB port drivers directly from their website. If the USB port drivers are outdated or if Microsoft has their drivers in for USB instead of Intel's (on 3.0 ports only most of the time) what will happen is everything will look fine with connection to phone via USB from computer but once you are in recovery or fastboot mode the connection will be lost.
I can give more specifics if you want to go down this route much later in the evening with screen shots and driver locations if needed, I'm just on my phone ATM on my way to work. So it would be much later tonight. Let me know...
- Sent from a payphone ...
Click to expand...
Click to collapse
I uninstalled sync manager and the phone proceeded to Download the drivers again (in addition to an older sync manager driver for some reason) but still no avail. The laptop is definitely an Intel powered one, I'd greatly appreciate if you could post those screenshots when you get the chance
is fastboot enabled? If stock it is not enabled by default...enable it and try again. If you do not know how to enable it follow this:
Settings>About>Software information>More
Tap on build number 7 times repeatedly developer options will be enabled
Go back to settings open Developer options, make sure USB Debugging is enabled
WNC - Good point.
- Sent from a payphone ...
tommy_riley said:
WNC - Good point.
- Sent from a payphone ...
Click to expand...
Click to collapse
I tried installing it in fastboot usb but It didn't even detect the phone. Is there another type of fastboot or is that the only way?
Only one fastboot. Sounds more and more like a driver issue,be it a usb system driver update or htc driver update...something is amiss on that end.
Apologies for not getting back to this thread. Started a new work assignment this week causing my commute to significantly increase (along with a nasty storm yesterday resulting in power outage). I'll get back here this weekend when I have some time to login from home computer...
- Sent from a payphone ...
So, there are a few ways to check if you have USB3.0 drivers
One, is to look at the USB ports on your laptop/computer - unless it's a custom gaming rig, the USB2.0 ports plastic tabs will be black, while the USB3.0 ports will be blue - if all of your little plastic tabs inside the actual USB ports are blue, then sounds like you have USB3.0 ports only.
The other way is to go into your device manager and look at see what it lists under USB - refer to the below image. Should look like something similar to as follows:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now, provided that you have an INTEL chipset AND these 3.0 extensible drivers are currently using Microsoft drivers, then what you may want to do is replace the Microsoft Intel USB 3.0 drivers with the INTEL drivers themselves.
What you would look for is your chipset version of the intel chipset (e.g. C220, C217, C270 etc) you should see other areas in your device manager that will refer to your Intel chipset type) then do a search on Intel's website for "USB 3.0 driver C216" (or C220, C270 etc) and download the drivers for your version of Windows (Windows 7 64bit? probably)
The download center for Intel is here: https://downloadcenter.intel.com/
The original article where I ran into this same situation was located here - for some reason I still have it book marked. I was trying to update/root an HTC EVO LTE about two years ago and ran into this issue on Windows 8 - I imagine a similar issue exists on Windows 7 USB3.0 only systems. This allowed me to keep my connection to my EVO while in fastboot mode (no USB disconnected) on Windows 8 and do what I needed to do to root my phone. It was my first root and folks were saying it was impossible to use Win8 with USB3.0 only ports to accomplish this task, but using the method at the link I was able to : http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
Here's to hoping you are running into something similar. If not, the next area I would try is just going to Intel's website and download there own driver check utility which should search your computer for all of their own drivers and download install the updated ones. You can try that out too.
Let me know how it goes.