Develop Bugs

[Q] EVO Unrecognized - WTF??

Guys, I need a little help here. I've rooted my share of phones, and even some tablets, but the Evo i bought a few days ago has been a nightmare.
For some reason, and I can't tell why, this thing will not be recognized by Windows.
It always shows up as "Unknown Device" under the USB catagory on Device Manager.
I've tried different OS versions (Windows 7 64Bit, Vista 64bit, Even Mac). I've also pulled down every form of driver I can think of (SDK Orginal version, HTC Sync, Hboot Versions, etc.)
I just cannot get this thing to be recognized. And if I manually try to update the driver and point it to one that I've downloaded, Windows tells me that the most current driver is already installed.
The bottom line is that I need to be able to connect to the phone from the comp in order to push stuff via ADB and throw commands at it. The same unknown device situation happens when the phone is in bootloader or actually booted into Stock Froyo (2.2)
Has anyone ever seen anything like this? I know i haven't, and it's buggin me out.

buster3845 said:
Guys, I need a little help here. I've rooted my share of phones, and even some tablets, but the Evo i bought a few days ago has been a nightmare.
For some reason, and I can't tell why, this thing will not be recognized by Windows.
It always shows up as "Unknown Device" under the USB catagory on Device Manager.
I've tried different OS versions (Windows 7 64Bit, Vista 64bit, Even Mac). I've also pulled down every form of driver I can think of (SDK Orginal version, HTC Sync, Hboot Versions, etc.)
I just cannot get this thing to be recognized. And if I manually try to update the driver and point it to one that I've downloaded, Windows tells me that the most current driver is already installed.
The bottom line is that I need to be able to connect to the phone from the comp in order to push stuff via ADB and throw commands at it. The same unknown device situation happens when the phone is in bootloader or actually booted into Stock Froyo (2.2)
Has anyone ever seen anything like this? I know i haven't, and it's buggin me out.
Click to expand...
Click to collapse
I've never seen that before. Wish I had something for ya. Is the Evo brand new or used? Are you sure the usb cable is good? I've seen a bad cable cause some headaches before. Wish I had more for ya, sorry man.
Sent from my PC36100 using XDA App

EVO is not new. I bough it from cragslist a few days ago. It seems to work fine otherwise. Not rooted for sure, and running Sprint original 2.2.
I did try a couple of different USB cables just to be sure, and had the same results.
The funny thing is that even though I was never able to get it "recognized" on any of my machines, I was able to get ADB so "see" it for a while. I started the rooting process by pushing files to it via ADB and even sent a reboot command to it.
Once it rebooted, that's when it all went bad. It was still showing as unrecognized (just like before), but now ADB can't see it at all. Keeps telling me no devices are connected.
Even my friend's Mac Air (which supposedly doesn't need any kind of drivers to see the phone) can't see it either.
It's just weird...

perform a hard reset, maybe a rogue app or setting got messed up,
fastboot screen>clear storage>yes

Tried that as well. Sorry i didn't mention it in the original post.
I think I've pretty much tried everything that's somewhat logical at this point.
Now I'm looking for the "illogical" ideas.

Make sure usb debugging option is turned on in settings>applications>development and the phone is in charge only mode. Then it should be recognized and you should be able to use adb.

Debugging was turned on already. I made sure of that.
As for the mode of connection I've tried them all with mixed results.
Here's what I've seen so far...
Charge only - unrecognized device in Device manager, and ADB can't see it.
HTC sync - unrecognized device in Device manager, and ADB can't see it.
Disk Drive - unrecognized device in Device manager, and ADB can't see it.
Internet Sharing - never tried it.
Here's the weird part. If i uncheck Debugging and set the phone to HTC Sync, I am sometimes able to get ADB to see it.
This is just confusing...

What happens if you uninstall HTC Sync and just leave the drivers installed? Could work I suppose. I know unrevoked says to make sure you uninstall HTC Sync and install the ADB drivers.

try this. connect your evo to a machine running xp. i had the same problems rooting one evo using windows 7. connected to a machine running xp ,zipped right through without a hitch.
HOPE THIS HELPS YOU IN YOUR QUEST

Thats what I tried on the Vista box.removed HTC sync, and left the HTC drivers.when that failed I removed the drivers too and replaced them with several different ones I found online.none seemed to work.
The strangest part is that all guides seem to say that MAC OS should just see it without any drivers.
I borrowed friends MAC air and it didn't see it either.

I'm not sure which USB drivers you are using, but these work for me. Uninstall the drivers first, then install this. I hope it is legal to put these here and if not I am extremely sorry.
PS you could try a Linux Live CD and it will see it without drivers or go with Wubi which installs Ubuntu on your Windows hard drive and can be uninstalled just like any other program. It gives you the option to boot into Ubuntu or Windows on bootup. Neat little program and it is faster than using the live CD. Go to this link Wubi and click the Start Download button to download Wubi.

Those seem to be the same drivers I've tried (well those and a ton of others as well).
I'm gonna give that LiveCD idea a shot. Burning it now.
If not, I'm gonna try to find an XP machine somewhere.
I've got a couple of VM's on my machine running XP, but since the main Win7 Machine doesn't see it, it can't seem to pass the USB connection over to the XP VM.
Man, I have to say, this is just the most complicated rooting process I've ever seen. If this was my first root attempt, I'm pretty sure I'd leave Android forever

It usually is a painless operation to root the Evo. For some reason you are having a difficult time with driver installation. It seriously has to be something simple that has been missed, because I have rooted mine and several friends Evo's and it was very easy. I had a MyTouch 3g 3.5mm before this Evo and talk about a pain. Before the Universal Auto root app you had to make a gold card first and that in itself took over an hour. It was my first root and it was very difficult and time consuming, so to see how easy the Evo was no matter which way I do it made me very happy.

buster3845 said:
Thats what I tried on the Vista box.removed HTC sync, and left the HTC drivers.when that failed I removed the drivers too and replaced them with several different ones I found online.none seemed to work.
The strangest part is that all guides seem to say that MAC OS should just see it without any drivers.
I borrowed friends MAC air and it didn't see it either.
Click to expand...
Click to collapse
yes the mac doesn't require additonal drivers to run adb however u need to make sure the directory is properly set in terminal so adb knows where to pull commands from... on windows did u try uninstalling everything phone related? SDK, HTC Sync, the whole nine yards then try reinstalling only the sdk and the usb drivers? I know with the lastest SDK the usb driver is not included for some reason or at least it wasn't with mine... then one day my adb just randomly stopped working and a uninstall/reinstall cleared up everything... try this usb driver and see where it gets u. Don't know if it's any different that wat the guy above posted but worth a shot. Reinstall the appropriate SDK first then i would recommend plugging the evo into the pc with no usb drivers installed then when it cant automatically find the drivers direct it to the file u downloaded and it should pull the necessary drivers from there and see if that does the trick...
View attachment android-usb-driver.zip

No dice so far guys...but i have made progress in identifying the issue (sort of).
So here's the deal - the ONLY way the phone is recognized is if i toggle the "debugging" setting.
If i plug the phone in with the switch set on (meaning USB Debugging enabled) the phone is not recognized. Pointing the unknown device to the drivers (any drivers) does nothing.
However, if i plug the phone in with the switch set off, it finds a usb mass storage device. Then i turn the debugging switch on, and it finds the ADB Android phone with no issues. Then i can push commands via ADB without any problems.
The problem i have is that I cannot toggle that switch if i boot into HBOOT menu. So the comp never see's the phone.
I've tried this experiment on Win7-64bit, Vista-64bit, XP 32bit, and even MAC.
The same situation seems to apply everywhere, and with all of the drivers I've tried. None of them seem to allow the phone to be plugged in and automatically be found. The only way for the comp to see the phone is if i toggle the debugging switch off, then on.
At this point, I'm ready to put out a bounty on this. $20 via PayPal to anyone who can walk me through it. Bottom line is that I need to be able to see the phone without having to toggle the debugging switch. That will allow me to boot into HBOOT and still send commands to the phone via ADB.
Thanks for all the help guys. Hopefully, we can get this resolved.

**BUMP**
Anyone care to take a shot??

[Q] What can I do to get passed 'waiting on device'

I'm trying to root but I can't get passed 'waiting on device'. I read through the forums and guides but all they say is make sure HTC sync is uninstalled, but I never installed it. Here's what i've done. Installed the new drivers, have my phone on debugging, have my phone on charge only. What else can I do?

Well you need to install HTC sync, then uninstall it. I know it seems pointless, but it installs drivers that you need. So try then, then try to run unrevoked again.

teh roxxorz said:
Well you need to install HTC sync, then uninstall it. I know it seems pointless, but it installs drivers that you need. So try then, then try to run unrevoked again.
Click to expand...
Click to collapse
Still didn't work, wish I knew what I was doing wrong.

have your phone in usb debugging, connect it to the pc, boot into the bootloader > recovery. You'll get the red triangle and !, check to see if your pc install the drivers for it. You'll have to battery pull to restart.

go to settings and applications and uncheck fastboot and also disable any anti virus programs...i was stuck there till i disable the anti virus..

Got it, thank you!

Glad you got it working.

no problem

[Q] Problem downgrading

I have tried this several times and it always gets stuck in the same spot. I have used adb before to root several of my Eris's. This one just doesn't seem to be working right.
It gets stuck at the
<waiting for device>
Do you have any suggestions?

scouter68 said:
I have tried this several times and it always gets stuck in the same spot. I have used adb before to root several of my Eris's. This one just doesn't seem to be working right.
It gets stuck at the
<waiting for device>
Do you have any suggestions?
Click to expand...
Click to collapse
Wish I could help.. do you have the drivers installed?
also try turning off your virus protections firewall when trying. never know.

I turned everything off, I installed the drivers in the package and I have the PDAnet drivers installed.

Comments on Red DI2 having issues with downgrade & root - updated w. log
Yeah, I hear you - DW's DI2 in red was in my hands last evening, took several hours while watching TV to get it done, finally - it should've been an easy one, but it wasn't.
Downgrade to HB.97 was easier, after uninstalling/rebooting & installing HTC drivers, etc. per excellent instructions. There're hidden usb/phone/device drivers that're conflicting & trying to run (use the OEM cable, it's better vs. a generic or Moto's.) Had to reboot both pc & phone a few times to try to get it to work together.
Getting the revolutionary to see the phone, run & zerging root was the challenge - finally managed to do it with relative success on an older laptop that I primary used as a backup when I'm on field assignment (XP-SP3 with antivirus/firewall disabled). Next, it would flash CWM's image file, after several attempts, went back to regular PC and used adb command to push it, worked & then reboot into recovery, did a full CWM Backup first, then flash the zip file to gain SU. It's now back on 2.3.3 & Sense 2.1 (instead of 2.3.4 and 3.0 as shipped)
I did it once before with the black DI2 so I figure it should be easy, it took more time with the locked bootloader on this red DI2. Seemed like the hidden VZ VCast Media Manager might be responsible, it's hiding somewhere and/or loading (install to a new PC) as soon as the device is connected, even in Charge Only mode - I'm too tired at this point to track it down & try a # of tools to uninstall it. Check the your lower right corner of the screen for the red V logo/symbol once you connect the DI2 to the PC before running the tools ....
Be patience & repeat, the only thing that I forget to try was to do a battery pull to power cycle it (something that I've done as recommended on SE phones).
[I]P.S. I saved last night's command prompt log of the downgrade - and for awhile, it was at a standstill with ZergRush, waiting for device & unable to find and identify the DI2. (see the attached log) - rechecked md5 sum, etc. - but, it came thru. [/I]

I've tried to uninstall that media sync also to no avail just right click and close you see it disappear if it shows back up close again
Sent from my ADR6350 using xda premium

Letitride said:
Yeah, I hear you - DW's DI2 in red was in my hands last evening, took several hours while watching TV to get it done, finally - it should've been an easy one, but it wasn't.
Downgrade to HB.97 was easier, after uninstalling/rebooting & installing HTC drivers, etc. per excellent instructions. There're hidden usb/phone/device drivers that're conflicting & trying to run (use the OEM cable, it's better vs. a generic or Moto's.) Had to reboot both pc & phone a few times to try to get it to work together.
Getting the revolutionary to see the phone, run & zerging root was the challenge - finally managed to do it with relative success on an older laptop that I primary used as a backup when I'm on field assignment (XP-SP3 with antivirus/firewall disabled). Next, it wouldn't flash CWM's image file, after several attempts, went back to regular PC and used adb command to push it, worked & then reboot into recovery, did a full CWM Backup first, then flash the zip file to gain SU. It's now back on 2.3.3 & Sense 2.1 (instead of 2.3.4 and 3.0 as shipped)
I did it once before with the black DI2 so I figure it should be easy, it took more time with the locked bootloader on this red DI2. Seemed like the hidden VZ VCast Media Manager might be responsible, it's hiding somewhere and/or loading (install to a new PC) as soon as the device is connected, even in Charge Only mode - I'm too tired at this point to track it down & try a # of tools to uninstall it. Check the your lower right corner of the screen for the red V logo/symbol once you connect the DI2 to the PC before running the tools ....
Be patience & repeat, the only thing that I forget to try was to do a battery pull to power cycle it (something that I've done as recommended on SE phones).
Click to expand...
Click to collapse
I had to do this on one of VZW's Red DI2's as well; My main PC is a Linux Mint machine and ADB had been broken for a while... I had to update the Android SDK and re-install Java to get it working again. Try updating the SDK and re-installing java. After that, type in "./adb devices" and see if it can find it. If you still get the "????????????", you may need to change your rules file to identify the phone...

I am not enjoying this... it still gets stuck at the same point. It is waiting on the device, the phone boots into the boot loader and just waits... forever.
I have re-installed the drivers and updated the SDK to make sure I have the latest USB drivers. I will restart the computer and the phone again and try later.

I'm also having some annoying issues with this.
View attachment 942722
Here's the command log that I've typically been getting, tried to downgrade my phone like 10 times, and it normally reboots running 2.3.4 after each try. (HBoot 0.98 fyi)
No idea what's going on, if someone on here is more adept at reading commands, could you tell me what's up?
Thanks in advance.

I had a lot of trouble getting the downgrade to work too. I had to type each command in manually in adb versus letting the tool do it. For some reason the tool was getting hung up during the process. Another thing I did was disabled the screen off on the phone while it is in charging mode and disabled my comps screen saver.
Sent from my Sabotaged Droid Incredible 2.

scouter68 said:
I am not enjoying this... it still gets stuck at the same point. It is waiting on the device, the phone boots into the boot loader and just waits... forever.
I have re-installed the drivers and updated the SDK to make sure I have the latest USB drivers. I will restart the computer and the phone again and try later.
Click to expand...
Click to collapse
This is because you don't have the fastboot drivers working correctly. You'll need to uninstall the PDAnet drivers and all other drivers on your machine for that matter and restart your computer to clean out those uninstalls. Then install the newer HTC drivers.
You can test if you have your adb folder setup correctly by doing "fastboot devices" instead of "adb devices" while in the bootloader

[Q] Unrecognized Device only in hboot/fastboot

Let me say beforehand that I am a lifetime lurker. I would not be posting here if I hadn't already spent at least two days scouring the web for an answer.
My HTC Desire HD cannot connect to HTC Sync, but it can connect as a storage device, and can be seen by adb. Whenever it connects while in hboot/fastboot, it will flicker "USB" a few times before Windows tell me it's not recognized (Device failed enumeration code 43). This includes using the RUU wizard from HTC. That will just make it stick on "RUU" in the bootloader.
I have tried every driver download suggested on this site. I have switched USB cables three times (all htc cables). I have used two seperate computers (Windows 8 and Windows 8.1).
I'll admit I'm a nooby specifically to Androids. All I want to do is flash new ROMs/root my device. As far as I know this is step one, and I can't go any further until I've unlocked my bootloader.
EDIT: SOLVED
HTC Desire HD drivers really hates Windows 8 and 8.1. Installed Windows 7 32-bit and it worked just fine.

That error can be a pain in the ass. I have it as well. I believe disabling griver signature enforcement in win8 (it's your OS, isn't it?) should allow installing adb drivers, but I was too lazy to check it. As a workaround I instead flash the boot.img in bootloader by putting it to PD98IMG.zip
I can upload you a template, leave the txt in it and replace the boot.img with your desired one, choose store (none) compression level, then put the zip directly (don't use folders) in sd card
EDIT: I didn't fully read your post before. If you don't have S-OFF most probably you can't get away without adb drivers..

Turned off device signing. No effect.

Have you tried now manually installing drivers in device manager while the phone is in unrecognized state? Does it still say the drivers are incompatible?
If your OS is 64bit, you need these http://d-h.st/23V

I have those drivers. I installed them manually. I tried the updating the drivers through device manager and pointing them directly to the drivers folder I need, and Windows is insistent that not having ANY drivers installed is the best driver to have installed for my device.
I am getting a pop up saying that the device is failing to to start. It's not like other usb devices I might have plugged in and they just sit there in at least their correct category in device manager.
The part that ticks me off most, is that this exact problem on this exact model has been solved on three different forums, and each time the OP just said "nvm I fixed it" and never even bothered to explain how for the rest of us.
It's really hard not to curse right now.

in device manager update dialog goto
browse my computer --> let me pick --> have disk --> choose the .inf from the drivers path.

Ya, I had tried that too. None of them will work. It says the file I chose doesn't have compatible software for my device.
Once again, this only happens in the hboot/fastboot/RUU. Once the phone has loaded the OS it works totally completely fine, save for HTC Sync not seeing the phone and vice versa. I don't understand why some drivers would only work sometimes unless something is wrong with my bootloader, and if so, how do i fix it?

have you tried un-installing HTC SYNC?

SuperMechaCow said:
Once again, this only happens in the hboot/fastboot/RUU. Once the phone has loaded the OS it works totally completely fine, save for HTC Sync not seeing the phone and vice versa. I don't understand why some drivers would only work sometimes unless something is wrong with my bootloader, and if so, how do i fix it?
Click to expand...
Click to collapse
Nothing is wrong with your phone, same thing happens to me, I just thought disabling driver signing should fix it, like I said I was too lazy to check it since I found workaround for my needs.

TheJokah said:
have you tried un-installing HTC SYNC?
Click to expand...
Click to collapse
It is currently uninstalled.
@smoger:
I would try your workaround, but I' m not sure where to obtain the boot image I need. Also, I thought you could only change the S-Off if your bootloader was unlocked anyways?

Power down DHD and connect it to PC. I realized, my win7 was installing drivers, while phone was off.
Sent from my HTC Desire HD using xda app-developers app

ammo12 said:
Power down DHD and connect it to PC. I realized, my win7 was installing drivers, while phone was off.
Click to expand...
Click to collapse
It appears to be the same device/drivers when powered off or when in the Android environment. While in the bootloader, it shows as an unknown device.
I also noticed that only when I am trying to update via RUU, it says instead "Device Descriptor Request Failed"

SuperMechaCow said:
@smoger:
I would try your workaround, but I' m not sure where to obtain the boot image I need.
Click to expand...
Click to collapse
The boot.img is in the ROM-zip-file packed. But I think, if its a RUU it is called PD98...img

Try this, I know its from Samsung, but this installs fastboot drivers and drivers used for ADB access
https://www.dropbox.com/s/vqfuv8fifmrkkxt/SAMSUNG_USB_Driver_for_Mobile_Phones.zip
For the set of Google Drivers, go here too http://d-h.st/23V

My drivers list does not show the Google or HTC drivers like yours does after installing all the things in your links. In fact, that's the fourth time I've downloaded those Google/HTC Win7 64x drivers from people around the web. They are not in my drivers list after installing them via the INF files. I must be doing something wrong.

SuperMechaCow said:
My drivers list does not show the Google or HTC drivers like yours does after installing all the things in your links. In fact, that's the fourth time I've downloaded those Google/HTC Win7 64x drivers from people around the web. They are not in my drivers list after installing them via the INF files. I must be doing something wrong.
Click to expand...
Click to collapse
Did you browse to the folder where the manual driver files reside?
Sent from my Desire HD using Tapatalk 4

SuperMechaCow said:
Ya, I had tried that too. None of them will work. It says the file I chose doesn't have compatible software for my device.
Click to expand...
Click to collapse
SuperMechaCow said:
I have those drivers. I installed them manually. I tried the updating the drivers through device manager and pointing them directly to the drivers folder I need, and Windows is insistent that not having ANY drivers installed is the best driver to have installed for my device.
Click to expand...
Click to collapse
To be exact I have:
Tried HTC Sync
Tried HTC Drivers Installer
Tried to Automatically search for drivers
Tried to install drivers by using the inf Install option
Tried to manually select drivers by pointing to the folder the Win7 64x drivers were placed
Tried to manually install by picking out the exact inf files
Tried to install from device drivers list, were they were not listed
Tried these steps with driver signing turned off
Tried all of these steps with another PC
I still think the issue is related to the fact that it only has problems in the bootloader menu

Ok, like u know I had this issue. Now I randomly managed to fix it when I needed adb drivers for my new toy (Sanei tablet for 40$ lol)
The mistake I was making is that I was trying to install the drivers while device was in fastboot, but apparently you can get away with casual "My HTC" drivers which can be installed when DHD is booted into Android. It looks likethe phone is not being detected from bootloader (it doesn't like any of the drivers I had tried), but I can fully use ADB while it's in recovery or starting/trying to boot OS, so it should be enough for rooting/unlocking bootloader.
I remember with HTC Wildfire I had drivers package with seperate drivers for Android and fastboot, so I had to install different driver after rebooting to fastboot, but with these new drivers and win8 it doesn't work out this way.

Solved. Used Windows 7 32-bit. Windows 8.1 was the culprit.

Similar issue
SuperMechaCow said:
Solved. Used Windows 7 32-bit. Windows 8.1 was the culprit.
Click to expand...
Click to collapse
I am facing the same problem and I too have tried different methods like you did. Am using Windows 8.
Gotta try on Windows 7. Shall update if that solves my problem too.

Having trouble connecting to computer to use ADB

OMG... finally got it working. I installed HTC Sync Manager again and decided to run it and see what happened. While it was scanning for music on my computer windows installed the drivers. More than once it seems.
Now I need to know if I can uninstall Sync Manager but keep the drivers. It keeps opening up and I don't know if it's safe to flash recovery if that's going to happen.
Flashed TWRP successfully and made my back up.
--------------------------
OLD NEWS BELOW:
Here's the deal... I just flashed the 3.x RUU so I'm stock but I'm unlocked and s-off. I'm trying to flash TWRP via fastboot so I can get a custom ROM on here. I turned on USB debugging on the phone.
First of all, that stupid HTC Sync manager keeps trying to install and I don't know how to stop it. Googling has not helped with this.
Second, I can't get the device to be seen in adb, or at least not online. I seem to be going backwards with all the steps I have taken to try to get this to happen.
I'm using dotatt's adb package. When I attach the phone while it is off windows looks for drivers and usually fails. One time it seemed to work and adb saw the device but then when it boots up that Sync Manager wants to install so I decline. Then my phone was seen but listed as offline.
So I tried uninstalling all HTC things on my computer and reattach phone. Didn't help anything. I tried installing the HTC Sync then uninstalling it thinking I would get the drivers, no go.
I grabbed these Universal ADB drivers http://www.koushikdutta.com/post/universal-adb-driver linked to from a twrp page here https://twrp.me/devices/htconem9.html
Nothing lists as a device in ADB at all now.
My windows Device Manager shows "Unkown Device" under "Other Devices" with no driver listed.
Tried this:
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
http://forum.xda-developers.com/showthread.php?t=2588979
Still not working.
ACK! Can anyone help me out?
Is there still an issue with using usb 3.0 ports? I feel like I heard something about that way back when.

That's pretty much how it's always been. Best way to get the appropriate drivers is to install HTC sync, let it do its thing, reboot the PC, then uninstall HTC sync without removing the drivers. To the best of my knowledge, been that way since at least the days of the Incredible, if not before. At least it's how I've always gotten the drivers to use adb.

Yeah I remember that from the Rezound, which is why I did that, but it seems that the drivers didn't actually get installed this time until I let HTC Sync Manager start running and scanning my computer. That's when I saw the message that it was looking for drivers and twice it told me it installed them.
I would think it would have them installed during the 'actual' installation process. So I guess I just uninstalled prematurely. Seems weird. But it's working now so all good.