My HTC one x running cyanogen mod kitkat 4.4
whenever i connect my phone my computer is unable to recognise the device
I've tried everything uninstalled the drivers but nothing works
the device is not recognised in fastboot mode also.
pls help me resolve this issue.
try using a different usb cable. reinstall drivers, a genuine htc usb cable should work. try this as well (worked for me): http://adbdriver.com/downloads/
also in your device manager, check if there is "android phone" with yellow triangle. right click it and update driver manually
If reinstalling drivers fails, and you need to get to stuff stored on it, you could try and mount the storage in your recovery (CWM or TWRP) and get stuff off.
Related
I wanted to root my phone and flash a costum rom... unfortunately my DHD (2.2.1) is T-Mobile branded, so i had to create a goldcard in order to downgrade from 1.75.111.2 to 1.32. When it came to temproot it manually with cmd i had to plug my DHD into my PC in load only mode, usb debugging activated.
I knew already that my DHD wont recognize my PC or the other way round (i somehow broke it when i deleted the htcsync drivers.exe from my sd card), but i thought maybe it would somehow work in usb debugging mode.
Well, it didnt(phone not found).
i then focused on repairing my usb connection, so i tried it on 2 other pcs (mine is w7, the other ones are xp and win7) but it all failed
(xp asked for drivers, which i installed directly from htc.com today(on all pcs(plus i removed and reinstalled them all properly))/win7 did nothing/mine said that it fails to connect and that i should use a usb 2.0 port(well all ports are usb 2.0, i also tried usb3.0))
evertime i plugged my DHD in i was asked which connection i want to use, none worked, i also restarted my phone several times (usb connected and without) when i type in #7284# (or *#7284# i tried both) it says: connection failure or invalid mmi code
Finally i resetted my phone and did it all again! But it wont work!
please help me!
Hi...It looks like a driver issue...
If your drivers are installed correctly, in your win-7 Device manager it will show DHD.
I would suggest to Re-install HTC Sync from HTC website - Run it again and give it a try
doesnt work either.... win7 says the device does not run properly, my phone does nothin unusual...
i wonder if htc could fix the issue... this would be my last option
however i believe in you guys at xda!
how did you reset your phone?
Did you install the android SDK? Does adb recognize your phone? (run "adb devices", if your device is listed, everything should be fine)
On my win7-machine, the HTC-Software gives me an error message (along the lines of "phone doesn't respond" or something like that) but adb works nonetheless.
thank you for your answer but im afraid it didnt work... i installed the usb driver pack on sdk but i couldnt find it under sdk/usb driver..., however i found some files -> android/android-sdk/extras/google/usbdriver/amd64 -> usbdrivercoinstall2.dll... i tried to install this driver in hardware manager, and i tried to install an adb.exe which i found in my downgrade folder as a driver. but win7 said no driver installation is necessary the "best" drivers are already installed (win7 aint gonna install anything)
also my dhd is found under unkown device, -this device is deactivated because it made errors- "Dieses Gerät wurde angehalten, weil es Fehler gemeldet hat. (Code 43)"
well i deinstalled it and searched for new hardware, he now says the drivers are installed properly please restart however i neither see my sd card nor my devices name (instead unkown device with this little yellow triangle)
btw. for reset i used my android reset (settings -> sdcard -> reset)
It is normal, the HTC Sync turns on the USB debug?
Have the same issue. My DHD can be connected to the PC no other way than charge mode, no matter is usb debugging turned on or off. Tried 2 PCs with W7 and 1 PC with Ubuntu 10.04. This trouble appeared several days ago. Wipe didn't help. Thinking of re-installing firmware, but it seems like hardware problem. An engineer in our service center said it might be motherboard malfunction.
Some ways of solving this problem are described here: http://goo.gl/2eMcP But none of those solutions helped me. If anyone can help, please advise.
UPD: re-installing the firmware had no success - connection with PC failed. 95% hardware problem, will take it to service center.
Guys I know it's a stupid advice, but I had same problems (suddenly my connection with pc didn't work anymore): did you try to change usb cable?
giegi_dc said:
did you try to change usb cable?
Click to expand...
Click to collapse
tried 3 cables and 3 PCs
i just found a solution for me : i tried a forth pc (win7) freshly installed htcsync + android sdk + !downloaded! (not properly installed) adb drivers (which i surprisingly did not need) well i plugged my DHD in and he installed all drivers, but never asked for an adb driver. instead he had problems installing 7 different bluetooth drivers for my DHD (???)^^
it just worked for me this way (also worked for debugging mode + load only mode (for radio s-off/hboot s-off))
:|)
well it's not exactly a permanent solution just a temporal way to root my phone, but in worst case i think its nessesary to reinstall win7 on your pc....
Hi,
I have rooted my phone with rootbox rom and i cannot seem to connect to pc using usb cable,I have tried everything (replacing cable,installed another rom liquidsmooth,updating drivers,troubleshooting with kies) nothing seems to work no matter what i do the windows still shows mtp driver installation failed.I would be very thankful if someone could help me out here,..Oh yeah and i am able to connect it to pc from recovery by mounting usb storage but not in normal mode
I had this issue with 3 different phones of my own. I ultimately had to remove the Samsung drivers and reinstall them. Do a google search for captivate drivers, you should find an xda post on this somewhere.
I just purchased an HTC M8 running software number 1.55.631.4 and I am using Windows 7.
- I first tried plugging in the phone via usb, and Windows notified that the driver install failed.
- Then I tried installing the drivers manually using the All in one toolkit, tried plugging in the phone, and nothing happened.
- Then I uninstalled the driver, and tried installing the HTC Sync Manager (driver included), plugged in the phone, and still nothing happened.
- This problem occurred on an HP EliteBook, so I tried on another HP laptop I have at work, and the driver install failed when I plugged it in as well.
- Now I am here.
Does anyone have any possible ideas/solutions? Any feedback is appreciated.
bump
Install HTC Sync Manager, then uninstall it but leave the drivers. Should then work fine
http://www.htc.com/uk/support/software/htc-sync-manager.aspx
I'm running into the same problem. Have just unlocked bootloader and rooted the phone. I now want to achieve S-OFF. However when I get to the ADB push command nothing happens. I notice the error "HTC MTP Device - Failed" when it tries to update drivers after passing command adb reboot. Tried installing HTC Sync and uninstalling a few times but stuck in the same place. Any way around this?
Thanks
Running Windows 7 64bit. Software version 1.54.161.10
EddyOS said:
Install HTC Sync Manager, then uninstall it but leave the drivers. Should then work fine
http://www.htc.com/uk/support/software/htc-sync-manager.aspx
Click to expand...
Click to collapse
I just tried this, and it didn't work. When I plug in the phone via USB, my computer doesn't even make the notification sound that something has been detected. The red light on the phone shows its charging, but my computer doesn't even show that anything was plugged in or detected. Could this be a problem with my computer?
If another computer works, then yes
andrewjrr said:
I just tried this, and it didn't work. When I plug in the phone via USB, my computer doesn't even make the notification sound that something has been detected. The red light on the phone shows its charging, but my computer doesn't even show that anything was plugged in or detected. Could this be a problem with my computer?
Click to expand...
Click to collapse
what about device menager ?
Maybe you have some other drivers installed for android devices, try uninstalling them first.
wodzini said:
what about device menager ?
Maybe you have some other drivers installed for android devices, try uninstalling them first.
Click to expand...
Click to collapse
Nothing in device manager either.
I do have my Nexus drivers installed. Do you think that could be the problem? Should I uninstall everything previous?
I tried installing HTC sync manager on my work laptop (which has no other phone drivers installed), and it's still the same problem. One thing I've observed though is when I leave the phone plugged in to the computer USB and do a reboot on the phone, the computer detects it at the startup "htc one" screen, but the device disappears seconds later as the phone continues to boot. It's like it detects it initially, then some software with the phone is causing it to fail. Any ideas?
bump.. went through HTC customer service and they pretty much got me to try reinstalling drivers, sync manager, etc.. didn't work. Said they would push me to the next level tech support which would be as long as 7-10 business days and that was last Monday and still haven't heard anything
I've been eager to try Scott Crosler's new CM11 but didn't have time until tonight. To ensure cleanliness, at the bootloader I erased cache, system and userdata. I've flashed ROMs dozens of times, and as usual, there were no problems with fastboot recognizing the device.
I then entered CWM, and it was the darndest thing: three fast USB connection beeps and this error:
"Windows could not install driver software for your device."
But I've had the generic USB drivers installed for two years! At first I thought it was interference from the Samsung drivers when reflashing my wife's tablet, but I tried our two laptops, same result. No matter that I right-clicked "Nexus 7" in Device Manager and pointed it to freshly downloaded drivers, even that I tried installing drivers using the SDK Manager,
"Windows could not install driver software for your device."
I've read that turning off USB debugging helps, but um, with an erased /system, I had nothing to boot into!
Normally I prefer flashing via ADB sideload. To get up and running again, I flashed TWRP and used its feature of mounting USB-OTG and flashing from an external drive. Once I got into CM11, I turned on and off USB debugging, but I still can't install the USB drivers, and ADB can't recognize any devices. At least there's flashing via external flash drives.
Has anyone had the like?
didn't see win 8.1 mentioned but thought this may help? http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908. I have had problems with drivers in past. adb composite are the ones that work for me. I simply removed drivers under android devices in device manager then plugged in device. GL.
Windows 7 here, but thanks for the suggestion anyway.
This morning I can connect it as a media device, and it's in Device Manager just fine as "Nexus 7." But turning that off, it becomes "flo" in Device Manager and can't find the updated drivers. And either way, I still can't get it recognized while in recovery mode. Ah well, as I said, at least TWRP has the option to mount USB OTB and flash files from an external drive.
Let me add that I already tried another cable (for our Samsung tablet), and tonight I see that I can connect it in MTP mode. In MTP mode, it shows up just fine in Device Manager (under Portable Devices), but turning off MTP throws it under Other Devices with the dreaded ! (and I just can't get it to install the driver no matter where I point it to). And no matter what combination I try, I still can't get ADB to recognize it at all.
Although this is for Windows 8.1 it may apply to your situation: http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908
As I e-mailed you, sfetaz's suggestion of USBDeview is part of the solution! I still can't get it recognized in booted Android as anything but a media device, but now it's fine during recovery. Darndest thing I ever saw in 19 years of dealing with Windows drivers.
http://www.nirsoft.net/utils/usb_devices_view.html
Then in an old bookmark, I tried Koush's universal ADB drivers.
http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Even if USBDeview hadn't helped, it was still good to clear out all the old devices I no longer use. Definitely a handy utility to keep around and recommend.
I have an HTC One M8 by T-Mobile, running the latest firmware, unlocked, rooted and on Android 5.0 Lollipop with the stock recovery. (I put the stock recovery back on because I had no need for the custom at the time and charging would bring me through the recovery and be real annoying).
I had no problem doing all of this but now (a few weeks later) I need to get the custom recovery back on in order to flash a new ROM.
Problem is, I'm connecting my phone to my computer and I can't get ADB to connect, HTC Sync Manager shows there's no device connected and windows explorer only shows a new CD Drive connected and mounted on (F that doesn't work and does not act as a storage platform for my phone.
What I have tried:
Disabling USB Debugging
Restarting Phone
Re-enabling USB Debugging
Un-installing HTC Sync Manager
Force installing "androidusb.INF"
uninstalling HTC Sync Manager, unplugging phone, disabling usb debugging, turning off phone and then going back through again, installing, plugging in turning on and enabling.
Really puzzled here, need to connect to ADB to flash custom recovery to go back to my stock ROM.
Try using the generic Android MTP drivers in Device manager. Of course you could also check all the basics as well.
Try a different port or a different cable. Try to kill the adb server and restart it. Can also try revoking the USB permissions and accepting again when prompted on the device.
Though you don't really need adb to flash the recovery, it needs to work in Fastboot mode. ADB will only work in a running OS or in a recovery, fastboot of course from fastboot mode, which is what you'll need in order to flash the recovery. You won't need USB debugging enabled for it either.
Try some of the stuff above, especially if maybe it's a cable or port issue.
I realize you may find a solution before even considering the option below ⬇
http://forum.xda-developers.com/showthread.php?t=2965030
If you have an extra rooted device and get the cable coming you will never have to worry about troubleshooting drivers again considering after an ruu or a conversion you will go through the possible issues of drivers more than once
I've changed my CID,MID,flashed recovery with this method.
Being S-OFF I've not needed to try an ruu through ruu mode but would guarantee it will do the job