After the JB update, I can't seem to get Diagnostic Mode ##3424# to work. I've tried stock with goodies and OMJ build. Diag port doesn't show up in Windows 7. It does show up in Windows XP but driver doesn't install. Previous ICS worked on both XP and Win7. I've gone back to Stock with goodies ICS to confirm it still works. I'm just hoping ot have it available in JB.
Any help appreciated. Thanks.
Diag mode works for my stock rooted JB w/ s-off
Sent from my EVO using xda app-developers app
decayer177 said:
Diag mode works for my stock rooted JB w/ s-off
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
It's enabled but doesn't get installed properly in windows like ICS diag mode. You're still showing up in Windows correctly has diag modem?
supernoman said:
It's enabled but doesn't get installed properly in windows like ICS diag mode. You're still showing up in Windows correctly has diag modem?
Click to expand...
Click to collapse
Having the same problem. I can get into diagnostic mode on the phone but in Windows it won't show up as a modem in device manager or show what port (i was trying to manually change prl). Tried reinstalling HTC diagnostic drivers but it says it's not the right drivers for my device. Which is strange since they worked when I was on ics. I guess something changed on the drivers front with jelly bean.
Sent from my EVO using xda app-developers app
B1GQ1B said:
Having the same problem. I can get into diagnostic mode on the phone but in Windows it won't show up as a modem in device manager or show what port (i was trying to manually change prl). Tried reinstalling HTC diagnostic drivers but it says it's not the right drivers for my device. Which is strange since they worked when I was on ics. I guess something changed on the drivers front with jelly bean.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Check this post I just got mine installed running MeanBean
http://forum.xda-developers.com/showpost.php?p=28717758&postcount=8
bigdaddy619 said:
Check this post I just got mine installed running MeanBean
http://forum.xda-developers.com/showpost.php?p=28717758&postcount=8
Click to expand...
Click to collapse
I ended up going back to ice cream to flash a custom prl. Thanks for this tho, I'll definitely bookmark it for next time.
Sent from my EVO using xda app-developers app
B1GQ1B said:
I ended up going back to ice cream to flash a custom prl. Thanks for this tho, I'll definitely bookmark it for next time.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Yeah that post is like GOLD haha saved my butt a few times and welcome
Any solution for XP
Tried the above for XP but it does not work...
aankush said:
Any solution for XP
Tried the above for XP but it does not work...
Click to expand...
Click to collapse
Try this to get the drivers installed correctly
http://forum.xda-developers.com/showpost.php?p=28717758&postcount=8
bigdaddy619 said:
Try this to get the drivers installed correctly
http://forum.xda-developers.com/showpost.php?p=28717758&postcount=8
Click to expand...
Click to collapse
My bet is that only works for windows 7. I've that post with both windows xp 32 bit and windows 8 64 bit and on both it tells me the drivers are not designed for my hardware (or something to that effect).
For now those on either of those OS's might just have to nandroid, flash ICS do their PRL update and then restore their JB nandroid.
Unless anyone else has figured out the proper drivers?
supernoman said:
After the JB update, I can't seem to get Diagnostic Mode ##3424# to work. I've tried stock with goodies and OMJ build. Diag port doesn't show up in Windows 7. It does show up in Windows XP but driver doesn't install. Previous ICS worked on both XP and Win7. I've gone back to Stock with goodies ICS to confirm it still works. I'm just hoping ot have it available in JB.
Any help appreciated. Thanks.
Click to expand...
Click to collapse
you need to install the drivers first. look at this page for help http://forum.xda-developers.com/showthread.php?t=1769284&highlight=qpst+make+evo+louder . if you are on windows 7 64 bit like me and are having troubles with the guide that was first provided look here http://forum.xda-developers.com/showpost.php?p=28717758&postcount=8 ask me if you have any questions, i went through the same thing so i probally will know the answer. hope this helped.
P.S. the guide I provided was for use with qpst so if you aren't going to be using that only do steps 1,3,4, and 5. also this person probably meant step 3 not 4 when he says this "Browse to the folder containing the drivers your downloaded in step 4" in step 4
try changing to disk drive instead of HTC Sync Manager option in the phones drop down menu. that should install the diag drivers that you have already.
Related
Back in March I was rooted, running a cool sense 5 based custom ROM and happy. But the phone had other ideas. It stopped recognizing the SIM card and the replacement phone Verizon sent was on the latest firmware which we couldn't hack. I couldn't deal with the stock configuration after having the custom ROM so I binned the phone and went back to my old GS3 hoping to someday be able to go back to the DNA.
If I understand things correctly, that day has come and we can root the current firmware equipped phones.....Correct? I've read thru a number of posts and all it has done is left me confused and hesitant to give it a shot.
Can someone help me out with the correct steps, methods and procedures to root my stock, S-on DNA running the latest OTA firmware (2.06)? Any help is greatly appreciated!!
http://forum.xda-developers.com/showthread.php?t=2314771
scheirere said:
Back in March I was rooted, running a cool sense 5 based custom ROM and happy. But the phone had other ideas. It stopped recognizing the SIM card and the replacement phone Verizon sent was on the latest firmware which we couldn't hack. I couldn't deal with the stock configuration after having the custom ROM so I binned the phone and went back to my old GS3 hoping to someday be able to go back to the DNA.
If I understand things correctly, that day has come and we can root the current firmware equipped phones.....Correct? I've read thru a number of posts and all it has done is left me confused and hesitant to give it a shot.
Can someone help me out with the correct steps, methods and procedures to root my stock, S-on DNA running the latest OTA firmware (2.06)? Any help is greatly appreciated!!
Click to expand...
Click to collapse
So I just follow the steps listed in the link above and I'll be ready to flash a custom ROM? No HTC unlock code and such?
Correct.
Sent from my HTC6435LVW using Tapatalk 4 Beta
beaups said:
Correct.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Ok, gave it a shot with the windows version and didn't succeed. Followed the instructions and definitely made sure there was no trace of HTC Sync on the computer. When I run the Distiller.exe file, everything seems to run OK for test 1 (rebooting into bootloader) and test 2 (booting device) were the phone reboots like normal. Then the script says rebooting into bootloader (again) and sits there waiting for fastboot. It times out after 60 seconds and says connection failed. usb connection error.
Any ideas on were to go from here?
You need fastboot drivers.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Moonshine works great
Sent from my HTC6435LVW using xda app-developers app
Suggestions on were I can get those fastboot drivers?
Google HTC fastboot drivers. If you are on win8 with usb 3 ports only you can expect issues.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Googled HTC fastboot driver and it looks like I need HTCDriver3.0.0.007.exe . If I google HTC android drivers I can find another file HTCDriver_4.2.0.001.exe. Tried them both on my home windows 7 machine with a USB2 port. Nothing changed. Same results.
So I tried the window XP computer at my office that I originally used to root the old DNA. Got a little further this time. I get a message that temproot has failed. I also get a lot of stuff going on with "other devices" drivers when I watch my device manager. Is this normal during the process?
scheirere said:
Googled HTC fastboot driver and it looks like I need HTCDriver3.0.0.007.exe . If I google HTC android drivers I can find another file HTCDriver_4.2.0.001.exe. Tried them both on my home windows 7 machine with a USB2 port. Nothing changed. Same results.
So I tried the window XP computer at my office that I originally used to root the old DNA. Got a little further this time. I get a message that temproot has failed. I also get a lot of stuff going on with "other devices" drivers when I watch my device manager. Is this normal during the process?
Click to expand...
Click to collapse
Ok temproot failing means factory reset time. You should be good after that.
Sent from my HTC6435LVW using Tapatalk 4 Beta
That did the trick!! Factory reset and the older XP machine. God, how much I missed the custom roms for this phone. It totally transforms the device.
As for the Moonshine process, like I said, it worked for me but I did run into a few more speed bumps. Everytime the phone would reboot, I had to squash the HTCsync install. I guess it's something on the phone as I searched hi and low to find anything like it on the computer, with no luck. Anyhow, I would just cancel out everytime the message appeared on the screen. If I didn't cancel out, the moonshine script would time out and fail.
Just wanted to follow up on this in case someone else has similar issues.
Thanks again, guys!
So I can't move files off or on to my device by dragging and dropping any more.
I have searched and found stuff about MTP drivers and work arounds but have not found anything that works. Anyone have any ideas about a fix.
I am running OSE, the latest build.
OSE DNA
johnwaug said:
So I can't move files off or on to my device by dragging and dropping any more.
I have searched and found stuff about MTP drivers and work arounds but have not found anything that works. Anyone have any ideas about a fix.
I am running OSE, the latest build.
OSE DNA
Click to expand...
Click to collapse
Could this be an issue with that specific ROM? My works fine with Window 8.1 64bit on either CM11 or AOSPA v4 beta. Have you tried PTP mode?
I guess I might have to flash another rom to find out.
OSE DNA
Might want to dig deeper.. only thing you can't do with Windows 8/8.1 is use fastboot ... as far as I know.
Sent from my HTC6435LVW using Tapatalk
Flashed CM 11 and connected right away.
CM 11 DNA & Tab 10.1 4.4.2
jbarcus81 said:
Might want to dig deeper.. only thing you can't do with Windows 8/8.1 is use fastboot ... as far as I know.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
Fastboot works on windows 8.0.
The update to 8.1 broke the drivers. No fastboot.
Just spent last night removing that update from my computer. Pain in the a.. but now my fastboot drivers are back up and working fine.
sdamark said:
Fastboot works on windows 8.0.
The update to 8.1 broke the drivers. No fastboot.
Just spent last night removing that update from my computer. Pain in the a.. but now my fastboot drivers are back up and working fine.
Click to expand...
Click to collapse
How did u remove the 8.1 update?
mopartonyg said:
How did u remove the 8.1 update?
Click to expand...
Click to collapse
Mouse to lower right corner of screen >settings. >change pc settings. Then I think its the middle option >restart pc and save files.
Note... be sure to backup the files it says you will lose, and anything important.
This takes windows back to when your computer was new. Now I'm on a clean install of Windows 8.0 :good: and all my drivers work again
sdamark said:
Fastboot works on windows 8.0.
The update to 8.1 broke the drivers. No fastboot.
Just spent last night removing that update from my computer. Pain in the a.. but now my fastboot drivers are back up and working fine.
Click to expand...
Click to collapse
I'm back on Windows 7 for now.. trying to acquire a new DVD of my Windows 8 because of a scratch too deep to fix (as far as I can tell) ... I was on Windows 8.1 but corrupted data forced me to format (I broke it, haha!) and could only get my Windows 7 DVD to work.. Oh well.. been on the fence about linux so I may jump ship.
For me personally it was an mtp setting in the ROM I had forgot to check.
Sent from my HTC6435LVW using xda app-developers app
I have successfully rooted and installed a few roms. I have updated radios and even installed the new sense 5.5 rom. It locked my phone, so I have been trying to unlock it for a couple of days. I have used htc dev unlock and win droid versions. I've used three different windows versions. Still no PC recognizes my phone. Is there a common fix? I have read and found none here, nor online.
pah3000 said:
I have successfully rooted and installed a few roms. I have updated radios and even installed the new sense 5.5 rom. It locked my phone, so I have been trying to unlock it for a couple of days. I have used htc dev unlock and win droid versions. I've used three different windows versions. Still no PC recognizes my phone. Is there a common fix? I have read and found none here, nor online.
Click to expand...
Click to collapse
Try again with ubuntu. Make sure to sudo su.
Sent from my EVO using Tapatalk
Do you have htc sync driver installed?
numel007 said:
Try again with ubuntu. Make sure to sudo su.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
I have lubuntu installed on an xp netbook. I'll look it up and try, thanks.
Valsorim said:
Do you have htc sync driver installed?
Click to expand...
Click to collapse
Yes. It's recognized until I reboot to bootloader. Two evenings on this!
Are you selecting the Fastboot option when you get to the bootloader?
Sent from my EVO LTE
Not using Windows 8.1 w/USB 2.0, are you? Because if so, you'll have to use a hacky workaround.
Captain_Throwback said:
Not using Windows 8.1 w/USB 2.0, are you? Because if so, you'll have to use a hacky workaround.
Click to expand...
Click to collapse
Ha, yes I was! So I tried other ports. Then tried XP net book, to no avail. Everything works fine on the rom, and I saw your post about re-unlocking. I've never been stumped before. May try a windows7 laptop tonight. Not too familiar with Ubuntu. Thanks.
numel007 said:
Try again with ubuntu. Make sure to sudo su.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
Just finished. Same message: <waiting for device>
I assume you tried a different cable already, right?
Captain_Throwback said:
I assume you tried a different cable already, right?
Click to expand...
Click to collapse
Yessir. First used the replacement I bought, then the original. Only used the original trying Ubuntu. It must be something I'm missing. I really appreciate all the input.
Seems intriguing that some experience same problem with new released RUU.
So...last night Loki was trying to help me. My Omate wasn't allowing me to flash anything. After Loki's suggestions didn't work, I thought taking my Omate back to stock would hopefully fix the device and allow me to flash something. However, after following Loki's reset to stock guide, now not only will my Omate not turn on, but my computer will not recognize the device nor will Flash Tool.
So, what should I do? What could I have done wrong?
kp12584 said:
So...last night Loki was trying to help me. My Omate wasn't allowing me to flash anything. After Loki's suggestions didn't work, I thought taking my Omate back to stock would hopefully fix the device and allow me to flash something. However, after following Loki's reset to stock guide, now not only will my Omate not turn on, but my computer will not recognize the device nor will Flash Tool.
So, what should I do? What could I have done wrong?
Click to expand...
Click to collapse
Win7 or 8
Sent from my HTC One using Tapatalk
mghtymse007 said:
Win7 or 8
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Update: I removed the battery and now it turns on. However, I still am unable to flash stock (or any other ROM) still.
Win 7
My win7 system requires a reinstall of the flash drivers after a few flashes. Remove the current driver, restart and do a reinstall of the driver. Or do it manually.
Sent from my HTC One using Tapatalk
mghtymse007 said:
My win7 system requires a reinstall of the flash drivers after a few flashes. Remove the current driver, restart and do a reinstall of the driver. Or do it manually.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I've been knee deep in drivers all day - which drivers are you referring to? The MTK ones (for stock flashing)? Koush?
Sweet baby Cheesus, it just worked.
I don't know why...
kp12584 said:
Sweet baby Cheesus, it just worked.
I don't know why...
Click to expand...
Click to collapse
Good for you. I meant the MTK 65XX VCOM drivers.
Win7 and these drivers, along with the configuration can cause the flash tool and drivers to be touchy at times. Sometimes a restart and reinstall is all is takes.
Sent from my HTC One using Tapatalk
My phone has an older version of TWRP and I want to update it so that I can update to Viper Sense 6.0 and I can not do so. I believe I need to reinstall adb and fastboot drivers, how would I go about that (where can I find the correct drivers)? I am on Windows 8.1.
dkris2020 said:
My phone has an older version of TWRP and I want to update it so that I can update to Viper Sense 6.0 and I can not do so. I believe I need to reinstall adb and fastboot drivers, how would I go about that (where can I find the correct drivers)? I am on Windows 8.1.
Click to expand...
Click to collapse
try this thread, worked for me
http://forum.xda-developers.com/showthread.php?t=2757414
mopartonyg said:
try this thread, worked for me
http://forum.xda-developers.com/showthread.php?t=2757414
Click to expand...
Click to collapse
This works for me until I go into fastboot, still doesn't recognize my device. Will the Win. 8 drivers for the USB 3.0 thing work since I have 8.1?
dkris2020 said:
This works for me until I go into fastboot, still doesn't recognize my device. Will the Win. 8 drivers for the USB 3.0 thing work since I have 8.1?
Click to expand...
Click to collapse
I have 8.1 also with usb 2.0, did yiu try the section for usb 3.0 in the thread?
dkris2020 said:
My phone has an older version of TWRP and I want to update it so that I can update to Viper Sense 6.0 and I can not do so. I believe I need to reinstall adb and fastboot drivers, how would I go about that (where can I find the correct drivers)? I am on Windows 8.1.
Click to expand...
Click to collapse
Download the newest twrp image to your phone. Then go to the market and download flashify. It's a free app and it will flash the image for you from your phone. Worked perfect for me on my DNA. It's one way to just avoid using a computer to flash an image. Try that and report back.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
dkris2020 said:
This works for me until I go into fastboot, still doesn't recognize my device. Will the Win. 8 drivers for the USB 3.0 thing work since I have 8.1?
Click to expand...
Click to collapse
Try installing PDAnet, it's installed some blanket drivers that have helped me out of recognition issues in the past!