Let me start by saying I'm not a dev so don't expect a whole lot from me. I do know some things though and will answer any questions I can.
So here goes. First off I plugged my phone in regularly without debugging on and let it install all the drivers by clicking on each mode on the phone. Then I turned it debugging on and let the rest install. Now for whats important.
Plug usb into computer.
Power down the phone.
Hold volume down and power to get into the bootloader menu.
Press volume down until you see BP Tools.
Press volume up.
New drivers should install.
One of them says something about diagnostics and will give a port#. Mine was com 18.
The phone should then boot up.
Open QPST and you should see the port it showed during drive installation.
If it does but says no phone just boot back into BP Tools and the phone will show. Proceed as you normally would with QPST.
You will need your MSL to do anything with QPST. The best way to get it is to call Sprint and ask. I'm working on other methods but that's the only way with this phone for now.
For info about QPST and downloads Google is your friend. There are plenty of tutorials and the software is free.
Also Google 000001 prl. It's worked wonders on all my Sprint phones. This should also allow CDMA workshop to work but you'll need your MSL for that also as myself and a few others have been unsuccessful getting it with CDMA workshop.
Update:
Forgot to add make sure you have QPST build 366 or above or it won't work right.
Here is the link for QPST build 366
http://conflipper.com/Software/QPST_2.7_366.rar
Update:
Here is instructions to flash a prl with qpst. This tutorial is for the 3D but steps 11 on apply to our phones also.
I take no credit for this part, just sharing the info.
http://forum.xda-developers.com/showthread.php?t=1145111
I also think I found a simpler way to get into diag mode but I can't confirm until my computer find it's way back home.
Sent from my MoPho using Tapatalk
Cool! So for the QPST did you use the software found online, for example this link http://www.x-drivers.com/catalog/flash/mobile_phones/companies/qualcomm/models/qpst/12051.html ?
money226 said:
Let me start by saying I'm not a dev so don't expect a whole lot from me. I do know some things though and will answer any questions I can.
So here goes. First off I plugged my phone in regularly without debugging on and let it install all the drivers by clicking on each mode on the phone. Then I turned it debugging on and let the rest install. Now for whats important.
Plug usb into computer.
Power down the phone.
Hold volume down and power to get into the bootloader menu.
Press volume down until you see BP Tools.
Press volume up.
New drivers should install.
One of them says something about diagnostics and will give a port#. Mine was com 18.
The phone should then boot up.
Open QPST and you should see the port it showed during drive installation.
If it does but says no phone just boot back into BP Tools and the phone will show. Proceed as you normally would with QPST.
You will need your MSL to do anything with QPST. The best way to get it is to call Sprint and ask. I'm working on other methods but that's the only way with this phone for now.
For info about QPST and downloads Google is your friend. There are plenty of tutorials and the software is free.
Also Google 000001 prl. It's worked wonders on all my Sprint phones. This should also allow CDMA workshop to work but you'll need your MSL for that also as myself and a few others have been unsuccessful getting it with CDMA workshop.
Sent from my MoPho using Tapatalk
Click to expand...
Click to collapse
Looks good man, couple o' questions though, you said you booted up every option and installed all the drivers, where did you find MDM6600 and/or is it even important? I tried re installing RSD lite but no go.
EDIT: Never mind, just 1 question...lol
EDIT 2: Finally got it to show me phone in QPST config and also in programming, but as soon as I try to open programming by clicking ok to see the phone page it gives me "Online connection failure: Unspecified error". At a loss now..I dunno, going to bed.
-DJ
You need build 366 or above. Sorry I forgot. I added it to the op.
Sent from my MB855 using Tapatalk
Well got into QPST and tried changing several settings, but even the banner doesn't change. Seems nothing sticks. Am I missing something? As far as the prl goes, dialing ##775# does nothing. Is there some other way you did it?
-Dj
If you're rooted you can get the "MSL reader" app from the market, it's worked well for me in the past.
Has anyone else been able to get this to work? I have the newest QPST, and Windows 7 SP1. I am able to get the phone into BP Tools mode, and I can see the diagnostic port in QPST. However, when I try to add the port to QPST, it errors out and refuses to add the port. I have tried this with and without developer mode on. Make no difference. I have also tried creating a virtual serial port in the same way people interact with the Droid X. This also fails; I am not able to get the virtual port software to connect to 192.168.16.2:11008 when creating the port. At an rate, I would be much obliged if someone could let me know if I am doing something wrong? I have used the Verizon roaming PRL at work for a few years now, and it makes my user experience 100% better at the office. Although I am finally able to get a usable Sprint signal with the Photon (this is the only phone that has ever gotten a signal at my office), I think I could still benefit from the new PRL. Thanks in advance.
Don't add a port. It will do it automatically when you install the drivers. As long as you have the right version of QPST it should work. Just select your device from the list and go to service programming.
Sent from my MB855 using Tapatalk
So what version of Windows is everyone using? I have Windows 7, and I can get the Diagnostics port to show up, but when I try to add the port with QPST Configuration, it always errors out? any ideas? You say you don't have to add the port, but if you don't add it, what are you connecting to in Service Programming? Thanks...
Your phone should show. The port should be there. Do you have build 366? Post some seen shots and I can help you out better. I used Windows 7 64 bit
Sent from my MB855 using Tapatalk
money226 said:
Let me start by saying I'm not a dev so don't expect a whole lot from me. I do know some things though and will answer any questions I can.
So here goes. First off I plugged my phone in regularly without debugging on and let it install all the drivers by clicking on each mode on the phone. Then I turned it debugging on and let the rest install. Now for whats important.
Plug usb into computer.
Power down the phone.
Hold volume down and power to get into the bootloader menu.
Press volume down until you see BP Tools.
Press volume up.
New drivers should install.
One of them says something about diagnostics and will give a port#. Mine was com 18.
The phone should then boot up.
Open QPST and you should see the port it showed during drive installation.
If it does but says no phone just boot back into BP Tools and the phone will show. Proceed as you normally would with QPST.
You will need your MSL to do anything with QPST. The best way to get it is to call Sprint and ask. I'm working on other methods but that's the only way with this phone for now.
For info about QPST and downloads Google is your friend. There are plenty of tutorials and the software is free.
Also Google 000001 prl. It's worked wonders on all my Sprint phones. This should also allow CDMA workshop to work but you'll need your MSL for that also as myself and a few others have been unsuccessful getting it with CDMA workshop.
Update:
Forgot to add make sure you have QPST build 366 or above or it won't work right.
Here is the link for QPST build 366
http://conflipper.com/Software/QPST_2.7_366.rar
Update:
Here is instructions to flash a prl with qpst. This tutorial is for the 3D but steps 11 on apply to our phones also.
I take no credit for this part, just sharing the info.
http://forum.xda-developers.com/showthread.php?t=1145111
I also think I found a simpler way to get into diag mode but I can't confirm until my computer find it's way back home.
Sent from my MoPho using Tapatalk
Click to expand...
Click to collapse
i flashed my prl successfully to 11114 i had full bars, no data.....can you reccommend a prl or site where to find optimized ones for your area?
Got it working on my netbook after wiping it back to stock. Windows 7 32 bit on there and now with only Moto drivers and QPST it's working great! Thanks!
Can`t work. In win7 X64, The QPST say "There was an error enabling COM**.the port may not be working properly or may be busy. (-2147467259[0x80004005])".
seawinds said:
Can`t work. In win7 X64, The QPST say "There was an error enabling COM**.the port may not be working properly or may be busy. (-2147467259[0x80004005])".
Click to expand...
Click to collapse
I had the *EXACT* same issue and it was due to an old Windows 7 install. I made a new partition and did a quick clean install, installed new drivers and QPST, and it worked on the first go! Good luck!
New Win7 ! I see. Thanks!
I don't understand this.. I tried Ur method once and it works couple of time, but suddenly it stop working. HW VSP method, Ur method..none working. qpst/cdma ws won't detect the photon and with always show busy, I tried on new installed PC it gives the same error.. I tried with my DX it works normally with qpst or cdma ws, I already try activate the diag mode via ##3282# but the diag port still busy.
can anyone give me some advise?
for anyone has diag port busy, try these method:
req. Motorola 5.2.1 driver
- Clean install the 5.2.1 driver (remove previous driver installed)
- Install all the USB mode driver
- Before switch to BP Tools, set the USB Mode to PC Mode then switch BP Tools
- Let BP Tools install it's driver and open QPST, add the diag port showed
- Done, and QPST can read the phone as FFA-QSC6695 phone
Note: I'm using Win 7 32bit OS, hope my guide can help people out there having trouble with MoPho diag port
Done, I installed PRL 11115 and I have 3g and I can force roam and use 3g in verizon!!
Took me 3 chats with sprint to get the MSL.
I did the same with the ET4G and the nexus s 4g but with them I did not need the msl.
Where exactly do you get the PRL file to load onto the phone? I have the prl 51082 right now, and am looking to switch to the "business" prl which would allow 3g roaming. Any download links for such a prl? Thanks
w0lf215 said:
Where exactly do you get the PRL file to load onto the phone? I have the prl 51082 right now, and am looking to switch to the "business" prl which would allow 3g roaming. Any download links for such a prl? Thanks
Click to expand...
Click to collapse
Here!!!! this is the prl, unzip the file.
Related
Hi.
I'm pretty sure it's around here, but I just don't seem to find it after hours of searching.
How can I use QPST (2.7 build 301) with my HTC PRO from sprint?
I've already downloaded HTC WM drivers and installed them on my vista laptop; I've tried in ##DIAG# (##3424#) with and w/o WM Device Manager.
But QPST does not recognize the phone in any of the 5 ports set up... while it recognices right away a BB Storm 9530.
What Am I doing wrong?
Where's a guide of how to get this going?
Also I've downloaded Qualcomm's QXDM but I don't understand it (and AVG considers it a trojan). And also CDMA Workshop.
This is a bit frustrating, please help
guess my question would be... what are you needing it for? QPST is a very powerful tool that if used wrong can surely render your device useless
either way make sure you have the HTC wm drivers installed... once that is done plug your device in and put in in diagnostic mode... then you will need to setup the port in QPST's configuration dialog.... one the program is up and connected click read from phone to see all your values..... also stay away from the AMPS tab... if you click it you will have to close the program and reopen before you can do anything else
After I OTA'd the phone, I wanted to do something in QPST, so I hooked up the phone in diag mode (Debugging active and Dial Up Networking). The phone connected in diagnostic mode, but connected to a different port than before I had OTA'd it, and QPST wouldn't connect or recognize it anymore. Oddly, CDMA Workshop would connect, but still wouldn't read it.
Seeing as how the port it connected to was com port 8, I changed it to a lower port number (port number 2), because I had heard CDMA Workshop sometimes has issues with anything above port 6. Still no luck.
The weird thing is that the port I was using it on before I OTA'd (port 3) claimed it was still in use. In a last ditch attempt to get it working, I connected to port 3 anyway, and still had no luck.
Anyone have any ideas?
Please I need a solution.
Was the phone in dialup mode? Did you usbui to modem?
Sent from my DROIDX using Tapatalk
hondakorn said:
Was the phone in dialup mode? Did you usbui to modem?
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Yep and yep.cdma workshop keeps saying failed.. Cannot read phone. Or some thing like that
Yep same here. I did a *22899 to try to remedy something else & now qpst won't see the phone. I uninstalled & reinstalled both qpst & the phone drivers & so far it's a no-go. Any ideas?
Sent from my SCH-I500 using XDA App
Whats the dif? between *228 and 22899? Im still not finding the answer to the problem, Ive even tried changing the cable.
dandog96 said:
Whats the dif? between *228 and 22899? Im still not finding the answer to the problem, Ive even tried changing the cable.
Click to expand...
Click to collapse
I was once told that *22899 was the same as *228, option 1 which reprograms the phone radio settings but when I did it yesterday it said it was in activation mode & the lock p/w was set. I rebooted & reran 228, option 1 cause I thought I had hosed it up & thats where my qpst trouble began.
Sent from my SCH-I500 using XDA App
garywojdan81 said:
I was once told that *22899 was the same as *228, option 1 which reprograms the phone radio settings but when I did it yesterday it said it was in activation mode & the lock p/w was set. I rebooted & reran 228, option 1 cause I thought I had hosed it up & thats where my qpst trouble began.
Click to expand...
Click to collapse
My prob. is when I plug it in to qpst it finds the com port but on the com port its says no phone.
Now I realized that its not limited to qpst, when I try to One-Click root it says Error Device Not Connected, Even when im on debug mode. So it seems to be a general usb prob. : /. This needs to be fixed.
This could have something with the ota causing mass storage to show up as a cdrom. Borked usb drivers in the ota it seems.
The only thing is I didn't update from the ota, I used Adrynalyne's modem, rom & kernel which he deodexed, debloated & rooted. Because of his work, I never had the cdrom problem & still don't; I can mount it as usb mass storage just like on di01. It's just that qpst won't see it, but everything else does.
update: Problem solved. Blade765 in the dev forum suggested booting the phone up while connected by usb with qpst open & it worked. As soon as it booted fully, qpst saw it & I was in. Oddly enough, the only value that was reset to the [email protected] and disabled was the #1 setting. The #0 setting was still enabled and still set to @vzw (no dun). Hope this helps...
Sent from my SCH-I500 using XDA App & 3g hotspot
garywojdan81 said:
The only thing is I didn't update from the ota, I used Adrynalyne's modem, rom & kernel which he deodexed, debloated & rooted. Because of his work, I never had the cdrom problem & still don't; I can mount it as usb mass storage just like on di01. It's just that qpst won't see it, but everything else does.
update: Problem solved. Blade765 in the dev forum suggested booting the phone up while connected by usb with qpst open & it worked. As soon as it booted fully, qpst saw it & I was in. Oddly enough, the only value that was reset to the [email protected] and disabled was the #1 setting. The #0 setting was still enabled and still set to @vzw (no dun). Hope this helps...
Sent from my SCH-I500 using XDA App & 3g hotspot
Click to expand...
Click to collapse
Great to know your fixed. Ill try this after work. Can you please explain to me what is a dun file, as I am a newbie.
.dun is stands for dial up networking and it is the value that directs your connection to the billing pipeline. So the goal is to change the first two entries in the service programming mode from "[email protected]" to "[email protected]" in order to keep your connection in the unlimited smartphone data pipeline which you're already paying for.
Sent from my SCH-I500 using XDA App
Well. Unfortunately it seems we have dif. problems because that solution does not work : (.
Can you try a different cable? Many othe micro usb cables are compatible.
Sent from my SCH-I500 using XDA App
Yea, Qpst worked before. Its just at one point it just stopped connecting. Ive tried three cables, same problem. Ive tried running qpst, and restarting the phone with the usb in, still doesnt help. I just dont understand. Same with the one-click root software. It worked before, but now it wont let me root, as it says my device is not connected.
Solution for this issue. Running out of options.
I have a Verizon fascinate,
hardware version i500.04,
firmware 2.1 update1,
build sch-i500.di01 ( i tried this with dl09 as well ).
When I check the box to see unknown qpst will see the ports but it will not see a phone on it. I have also searched a variety of different forums and have found other people with this issue but no resolutions other then to start with usb connected. Diagnostic mode is enabled and so is usb debugging. I have tried a variety of different combinations of settings with no luck.
Is there another solution for this issue other then booting with qpst and usb cable. Currently I have tried qpst with the following.
1: installing Samsung_Mobile_USB_Driver_V1.3.550.0_SCH-i500_Fascinate and rebooting.
2: installing SAMSUNG_USB_Driver_for_Mobile_Phones_x86.msi and rebooting
3: removing com ports and modem and reinstalling in every way i know how to.
4: used odin to flash back to dl01
5: Taken this to a fresh computer and installed only the fascinate drivers and qpst with no luck.
Any help would be greatly appreciated.
doctorslack said:
I have a Verizon fascinate,
hardware version i500.04,
firmware 2.1 update1,
build sch-i500.di01 ( i tried this with dl09 as well ).
When I check the box to see unknown qpst will see the ports but it will not see a phone on it. I have also searched a variety of different forums and have found other people with this issue but no resolutions other then to start with usb connected. Diagnostic mode is enabled and so is usb debugging. I have tried a variety of different combinations of settings with no luck.
Is there another solution for this issue other then booting with qpst and usb cable. Currently I have tried qpst with the following.
1: installing Samsung_Mobile_USB_Driver_V1.3.550.0_SCH-i500_Fascinate and rebooting.
2: installing SAMSUNG_USB_Driver_for_Mobile_Phones_x86.msi and rebooting
3: removing com ports and modem and reinstalling in every way i know how to.
4: used odin to flash back to dl01
5: Taken this to a fresh computer and installed only the fascinate drivers and qpst with no luck.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Does rebooting the phone with QPST on help? It doesn't for me. Im on the verge of giving up.
I know this may sound stupid but do you have debugging on and dial up networking checked? Sorry if this is painfully obvious but I've found that most most of my troubles have come from details that I might've missed. Also, the reboot with the usb connected & qpst on is what did the trick for me.
Sent from my SCH-I500 using XDA App
garywojdan81 said:
I know this may sound stupid but do you have debugging on and dial up networking checked? Sorry if this is painfully obvious but I've found that most most of my troubles have come from details that I might've missed. Also, the reboot with the usb connected & qpst on is what did the trick for me.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Are you saying to disable those or make sure their enabled. I'm looking into performing the steps to get the work around for free mobile hotspots myself. Still doing a lot of reading as I'm new to Modding my phone but have learned a lot in the few days I've been teaching myself and was amazed at how easy a lot of this is especially with great guides on these forums and others.
Sent from my SCH-I500 using XDA App
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!
Hello wise XDAers....
Ok so my goal is to get my new vs985 12b to CM12 or something cooler. So first step I need to downgrade the phone in order to root. I've been trying to follow the instructions here http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html?m=1 but I seem to be stuck at step 4 - getting the phone to be recognized by Windows in firmware update mode. I have tried 3 Windows 7 machines and a VM W7 machine. Granted the 3 machines are similar HP laptops. I think they are all 64 bit. I don't have a COM/LPT in the Device Managers, not after showing hidden devices and there does not seem to be a BIOS setting which affects.
In firmware update mode I've got yellow flags on CDC serial, lge android phone and vs985 4g. Are these even the right and complete list of device manager items I am to install? I'm hoping one of these I can edit to get the COM port setup? Some have said to enable debug mode or ethernet USB mode - but these options are only available in normal boot mode in the phone; I did try and turn on debug nonetheless (though it was greyed out, it did seem to check the box??) and I could not find ethernet mode. I do see some posts on the internet that others seem to lack this option, perhaps in 12b it was removed. Further it does seem that many new machines lack a COM/LPT port, so I don't know if there is a way to emulate this or if the drivers for the LG set this up? I am using the LG's dedicated usb cord and have tried multiple usb ports.
I am trying the Windows drivers available on the LG support page for the phone but there also seems to be Verizon LG drivers. Not sure if I am supposed to use one or both or if once installing it one or the other it screws things up and how you are to remove? The VZ drivers seem to be removable under "uninstall programs" but not the LG drivers. I also have been trying to get Windows update to auto install the drivers, but does not seem to work. Here are the two I have been trying:
LGUnitedMobileDriver_S51MAN313AP22_ML_WHQL_Ver_3.13.2.exe
LG_VZW_United_WHQL_v2.14.1.exe
Am I doing this all wrong? Is there an easier way? Help!
Hi, just a quick reply that's not all inclusive as I'm at work and I'm going to hurry. You don't have to bother uninstalling the regular drivers. Installing the Verizon drivers is what you need to do, and it'll be fine if you installed the other drivers first. I'll try to get back about the rest of your post later.
roirraW "edor" ehT said:
Hi, just a quick reply that's not all inclusive as I'm at work and I'm going to hurry. You don't have to bother uninstalling the regular drivers. Installing the Verizon drivers is what you need to do, and it'll be fine if you installed the other drivers first. I'll try to get back about the rest of your post later.
Click to expand...
Click to collapse
Thanks roirraW "edor" ehT! I've got the LG_VZW_United_WHQL_v2.14.1.exe installed now, so I guess the issue is in firmware update mode I've got yellow flags on CDC serial, lge android phone and vs985 4g. On my virtual machine w7 I do have a lpt/com in device manager, but none of those 3 items are in that parent item. I guess if I figure out how to install them properly, they might "go under" the lpt/com parent entry? I've tried all the USB ports and tried rebooting the phone and computer several times. Tried letting Windows update search for drivers to update (if you rmb/properties on these items with yellow flags it says the driver is not installed despite the installed Verizon drivers). Not sure what else to do.
OK! Think I figured it out! Got the right device installed with the latest Vzw driver from LGs site - seems to be version 20.
abexman said:
OK! Think I figured it out! Got the right device installed with the latest Vzw driver from LGs site - seems to be version 20.
Click to expand...
Click to collapse
Excellent! Glad to hear it. I couldn't resist coming back to try to give you more ideas (I was going to suggest rebooting with the phone unplugged, and then plug it back in). I work with VMs a lot so that aspect interested me.
Cheers!
roirraW "edor" ehT said:
Excellent! Glad to hear it. I couldn't resist coming back to try to give you more ideas (I was going to suggest rebooting with the phone unplugged, and then plug it back in). I work with VMs a lot so that aspect interested me.
Cheers!
Click to expand...
Click to collapse
Thanks mate! I am not out of the woods yet - now having an issue in the flash tool, posted here: http://forum.xda-developers.com/verizon-lg-g3/help/q-t3035198