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....
Ok so I want to root my epic, there's just one problem... ADB doesn't see my phone. It is listed in my device manager and is showing as working. but when i try and list adb devices it shows nothing. My phone is in USB Debugging mode. I have the Samsung drivers installed. I just cannot figure out why this is not working for me. I have looked everywhere and have been unable to find anything that has helped my problem at all. Tried to upload a pic showing my device manager but i guess i cant yet because i haven't made enough posts yet. Device manager show my device in three different sections one under USB Controllers as SAMSUNG USB Composite Device, One under Ports (COM & LPT) as SAMSUNG Mobile Modem Diagnostic Serial Port (WDM) (COM4) , and one under Modems as SAMSUNG Mobile Modem.Thanks for any ideas.
jarmour05 said:
Ok so I want to root my epic, there's just one problem... ADB doesn't see my phone. It is listed in my device manager and is showing as working. but when i try and list adb devices it shows nothing. My phone is in USB Debugging mode. I have the Samsung drivers installed. I just cannot figure out why this is not working for me. I have looked everywhere and have been unable to find anything that has helped my problem at all. Tried to upload a pic showing my device manager but i guess i cant yet because i haven't made enough posts yet. Device manager show my device in three different sections one under USB Controllers as SAMSUNG USB Composite Device, One under Ports (COM & LPT) as SAMSUNG Mobile Modem Diagnostic Serial Port (WDM) (COM4) , and one under Modems as SAMSUNG Mobile Modem.Thanks for any ideas.
Click to expand...
Click to collapse
Try different USB port, switch data cable and also uninstall - reboot- reinstall driver - reboot - reboot phone - try again.
If you are using a laptop sometimes it's flaky. Reboot often and remember that you may have to kill that exe process... Think it was adb.exe a few times and just screw with it until you trick it to work. Trial and error
Sent from my SPH-D700 using XDA App
Ok so I wated a video on rooting samsung epic and one thing that I noticed was that when he hooked up his epic it showed up in the device manager under ADB Devices and mine shows up in 3 other locations. Is this where my problem is... am I just having issues with my drivers?
Sent from my SPH-D700 using XDA App
Turn off any security and uninstall the samsung drivers. reinstall drivers and watch and make sure your phone is detected by your pc. Now run your rooting app.
Sent from my SPH-D700 using XDA App
Hello. I am having the same problem as described above. The Epic is installing as a modem (on my Win7 PC) instead of an Android Composite ADB Interface. I cannot connect at all to the Epic (cannot connect via adb with debugging turned on and it I try and mount the Epic no folders show up on the PC). I have reinstalled the drivers and checked all of my serial ports. Also, I have a Samsung Captivate that works fine using the same system. Incidentally my wife took the Phone into Sprint to get the latest android version and they gave her a hard time cause it was rooted. I think they may have done something to the phone cause I pulled pictures off her phone to the PC last week. Help please!!
OK, so I got the Eipc to work. I still do not know the root cause but here are the steps I took to "fix it":
1) Unplugged USB cable and disabled usb debugging
2) Plugged in phone to USB and selected Mass storage. The drivers were installed correctly
3) Unplugged phone and turned on USB debugging)
4) Plugged in phone and the proper devices were detected but windows hung on installation of a "strange" unkown ADB device
5) Unplugged phone and plugged back into the USB port and all was working!
Hope this helps.
Hello,
I've been able to use ADB to install and test apps that I'm writing under the stock ROM for my Epic, as well as under CM9 (and I think an early CM10, not sure about that though). After installing the 20130101 build of CM10.1 (keeping the included kernel), I am having issues trying to deploy and debug apps from my any of my computer to the phone (all of which previously worked). I've verified that Android Debugging is still enabled on my phone.
In the device manager on my computer, "SAMSUNG Android USB Modem" and "Unknown Device" are both showing the "problem" icon. I've tried uninstalling and reinstalling various versions of the Samsung USB drivers, I've tried a few versions of Kies, and even a few third-party tweaked USB drivers. It doesn't seem like anything wants to recognize my phone now that is running CM10.1 (or CM10.1 in addition to something peculiar with my installation).
Additionally, if I have USB debugging enabled on my phone, even if I enable USB mounting, the computer won't recognize the mount until I disable debugging mode on the phone. Once I do that, then the volume will appear on my computer. Previously, when ADB debugging in general worked, I wouldn't have to disable debugging to get the USB mass storage mounting to work.
These problems happened at once on all three of my computers that I've been using for Android development, so I'm fairly convinced these issues are directly related to the ROM I'm running. I've attempted to search the forum and Google for others that may have had this issue and what the resolution/work-around might be, but so far I've not found anything. Surely other people are using CM10.1 and developing apps, which makes be believe it could be something unusual with my installations, but I've tried full wipe without a data restore and it didn't seem to have any impact. I've also tried searching to see if there were special drivers needed for CM10.1, and didn't find anything with that either. I know reverting back to an earlier ROM is an option to get ADB working, but I'm really hoping to get ADB working with CM10.1.
Does anyone have any suggestions on what I can check/do to get USB debugging working on CM10.1 (epicmtd)?
Thank you very much for your time
--James
Re: [Q] Unable to use ADB to connect CM10.1/driver issue
I had the same problem, tried absolutely everything I could to get it to work and couldn't... had to roll back to a tw rom to get it to work (not a fan of the HUGE battery drain on cm9)
Edit- I know this doesn't help you, just wanted to point out you're not the only one with this problem....
Re: [Q] Unable to use ADB to connect CM10.1/driver issue
Locate the drivers for your phone on your computer and uninstall them. Then plug your phone in and let the computer reinstall the drivers. I had the same problem (although I wasn't making apps) and my suggestion above worked for me, so hopefully it'll work for you.
Sent from my SPH-D700 using Tapatalk 2
Re: [Q] Unable to use ADB to connect CM10.1/driver issue
jeffreyjicha said:
Locate the drivers for your phone on your computer and uninstall them. Then plug your phone in and let the computer reinstall the drivers. I had the same problem (although I wasn't making apps) and my suggestion above worked for me, so hopefully it'll work for you.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Tried this multiple times... it may have actually been a problem with my pc... get it back on Friday, so time will tell...
flastnoles11 said:
Tried this multiple times... it may have actually been a problem with my pc... get it back on Friday, so time will tell...
Click to expand...
Click to collapse
I've tried this with my previous uninstall/reinstall driver attempts, but tried it again anyway.
Unfortunately, it didn't' seem to have a positive impact. It looks like it reinstalled the mass USB storage driver, but it did not reinstall any other drivers (like the modem driver) so I'm still not able to do anything with ADB.
Re: [Q] Unable to use ADB to connect CM10.1/driver issue
Have you tried manually installing the drivers?
Here is the .exe that I used to install the drivers for my phone.
Sent from my SPH-D700 using Tapatalk 2
jeffreyjicha said:
Have you tried manually installing the drivers?
Click to expand...
Click to collapse
Hello again. Yes. I've tried installing various versions of USB drivers floating around the net as well as Kies (after uninstalling and deleting current drivers to try to avoid conflicts). Other versions of Epic ROMs (Stock, CM9, etc.) worked with ADB using my installed drivers until I installed CM10.1 (maybe starting with CM10) on my Epic.
As an aside, using ADB requires some additional (special) drivers beyond the drivers required for mass storage support.
I'm hoping one of the CM10.1 developers will chime in with what they did and/or installed to have ADB working with CM10.1 on Windows 7.
Thanks!
--James
I'm going to update to the most recent build of CM10.1 and see if ADB works for me. If it doesn't work, i'll try reinstalling drivers.
jeffreyjicha said:
I'm going to update to the most recent build of CM10.1 and see if ADB works for me. If it doesn't work, i'll try reinstalling drivers.
Click to expand...
Click to collapse
I don't know what I did differently in my search (I've been trying to find solutions for awhile now). I found this thread:
http://forum.xda-developers.com/showthread.php?t=1817954
I upgraded my Kies to 2.0, which includes the latest drivers from here:
http://www.samsung.com/us/kies/
I still had "Unknown Device" listed in my device manager. Based on that forum thread, I right-clicked on the "Unknown Device", selected "Update Driver", "Let me choose from software installed on computer" and then picked "ADB Interface". A list of a few Samsung ADB entries in it appeared, and I picked one (I had two with the same name, so not sure what the differences are between them) and after a few seconds I had no more alerts in the device manager and when I run "adb devices" I now see a device in the list. I fired up Eclipse to give it a real-world test and it worked: I'm now able to deploy and debug apps on my connected device.
Woot!
I'll be taking these actions on my other computers tonight.
Thank you very much for your assistance.
samej71 said:
I don't know what I did differently in my search (I've been trying to find solutions for awhile now). I found this thread:
http://forum.xda-developers.com/showthread.php?t=1817954
I upgraded my Kies to 2.0, which includes the latest drivers from here:
http://www.samsung.com/us/kies/
I still had "Unknown Device" listed in my device manager. Based on that forum thread, I right-clicked on the "Unknown Device", selected "Update Driver", "Let me choose from software installed on computer" and then picked "ADB Interface". A list of a few Samsung ADB entries in it appeared, and I picked one (I had two with the same name, so not sure what the differences are between them) and after a few seconds I had no more alerts in the device manager and when I run "adb devices" I now see a device in the list. I fired up Eclipse to give it a real-world test and it worked: I'm now able to deploy and debug apps on my connected device.
Woot!
I'll be taking these actions on my other computers tonight.
Thank you very much for your assistance.
Click to expand...
Click to collapse
No problem.
samej71 said:
I don't know what I did differently in my search (I've been trying to find solutions for awhile now). I found this thread:
http://forum.xda-developers.com/showthread.php?t=1817954
I upgraded my Kies to 2.0, which includes the latest drivers from here:
http://www.samsung.com/us/kies/
I still had "Unknown Device" listed in my device manager. Based on that forum thread, I right-clicked on the "Unknown Device", selected "Update Driver", "Let me choose from software installed on computer" and then picked "ADB Interface". A list of a few Samsung ADB entries in it appeared, and I picked one (I had two with the same name, so not sure what the differences are between them) and after a few seconds I had no more alerts in the device manager and when I run "adb devices" I now see a device in the list. I fired up Eclipse to give it a real-world test and it worked: I'm now able to deploy and debug apps on my connected device.
Woot!
I'll be taking these actions on my other computers tonight.
Thank you very much for your assistance.
Click to expand...
Click to collapse
Activating through developer options doesnt help? just go to about phone --> tap build number 7 times
I just went to device manager, uninstalled the failed USB device, and then plugged the phone back to the computer via USB.
Boom, just like that, all was well.
i tried everything and could not connect to my htc rezound (w/ CM10.1) thru adb. then i tried the following:
1. download the android adk from google (i can't post links)
2. connect phone thru usb
3. on your computer's adk download folder, navigate to sdk\platform-tools\
4. press shift + right click on the window, open command window here
5. type "adb devices" in the command window w/o the quotes
6. there should be a window pop up on ur phone asking for USB debugging permission. say OK.
7. type "adb devices" again and you should see ur phone connected thru adb.
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 no idea what I do wrong, but this is what I tried:
I enabled adb mode on my Chinese watch
The watch is in fastboot mode
I installed all drivers, pdanet didn't work (no usb connected)
Once I put my cable in my laptop and it said: USB error, try again later or something like that?
no adb response in the commands. just blank... in the devices list, there is no sign of my watch...
It charges normally. I could really use your help
Somehow I found the chinese wear OS so I can use it. at least that is something. Is there any way to get in in English or Dutch without adb?
My other laptop seems to see a 'unknown usb device'. no adb device found...
I have no idea... maybe it's due to the unofficial cable?
I bought an expensive cable, the original, but no laptop can see the watch (windows 10 and windows 7)
The old cable is some sort of ok with the windows 7. I get an error 43 in devicemanagement.
Please help... I have no idea what I can do now...
https://forum.xda-developers.com/showpost.php?p=73472794&postcount=15
I've posted this many times in the various Huawei forums and it has worked for everyone so far.
First, remove all other drivers using USBDeview.
http://www.nirsoft.net/utils/usb_devices_view.html
Then use this tutorial to manually install the Google USB driver.
http://visualgdb.com/KB/usbdebug-manual/
Good luck!
edit - here is a fool proof method.
https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=71653349&postcount=12
I've posted this many times in the various Huawei forums and it has worked for everyone so far.
First, remove all other drivers using USBDeview.
http://www.nirsoft.net/utils/usb_devices_view.html
Then use this tutorial to manually install the Google USB driver.
http://visualgdb.com/KB/usbdebug-manual/
Click to expand...
Click to collapse
i am also bugged with this.
the win7-pc says unknown usb device detected. i turned dev mode and adb on.
then i tried to manually install the driver from the android sdk. when i try to select the driver windows says there were no driver found (but the driver is there) and i should make sure that the driver is written for x64-systems. WTF?
and even the watch does not charge wenn via usb 2.0 or 3.0 connected - but its connected cause of the message from the pc.
in the device manager the watch is listed as unknown device.
that's exactly my problem...
I have done everything. I'll try to connect it to my linux pc, I got an old laptop with ubuntu or something like that (haven't used it in ages)
maybe that will do the trick. I installed everything manually. my win10 can see an unknown device as well... but that's about it...
maybe dev mode is not working on some watches even when its enabled. or it has something to do with the 2.0 Version auf AW and it affects not every watch.
Its funny. I've been trying to get my HW1 watch to connect to my PC for a year now. Have tried numerous different cables and the original that came with my watch didn't work. Different PCs haven't worked either. Unless I'm that unlucky with all these OEM cables or the ADB debugging toggle really doesn't work for USB connections. It works just fine for bluetooth and wifi, neither of which allow you to unlock the bootloader. Guess I've got to wait for the next update manually and try again.