Hi,
I am new to this rooting thing, but got the incredible for just that purpose. I have followed many threads and still not had any luck. I have a couple questions that may not only help me, but others.
First, what parts of sdk need to be installed? I'm assuming the usb drivers, but do any of the other components, short of tools, of course need to be installed. When my phone is connected by usb, there is an android entry in my device manager, but the phone itseld says "my htc". I see 2 hard drives in my computer, neither of which are accessable. Is the wrong driver for the phone installed and could this be causing the problem of not being able to get adb to recovery.
Also, when I hit recovery, I hear the usb connect sound and then the 3 quick rings when there is a usb error and then the phone goes to the black screen and sits.
Again, any help would be greatly appreciated!!!
Thanks
Rod
I did not have HTC sync installed (I know, you didn't ask about this, figured I'd throw it in anyways), and from the SDK, I installed the tools, the packages that related only to 2.1 (API7) and the usb driver package. I don't really know if this is what enabled me to root, but I had tried countless times with everything from the SDK installed.
Related
Hey! I'm not completely new at this, I have a little knowledge as regards to rooting and and tweaking different things. But I'm having an issue that I just don't understand how to fix, and I can't find any help on google. So I came here.
BTW, I have Windows XP 32bit.
I'm trying to install the ADB files so the computer can recognize the phone. Before Ive done anything(nothing installed or changed), I can plug my phone into the computer and the phone gives me the option to charge, sync, use as disc drive, or internet sharing. So, I don't know if maybe thats all I need.
I downloaded the adb files for windows from here http:/ /htcevohacks . com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/. I hope its not a vista/win 7 file...
I installed the correct "SDK platform Android 2.1 AP17" and "usb driver revision 3" as the instructions read. I shut the phone off and boot into recovery mode, and then plug the USB in. Nothing happens. Nothing on the computer or the phone change. I don't find any "ADB" in the device manager, and no window pops up asking about updating drivers. I do exactly as the instructions on that site say, but nothing happens.
If the phone is on normally and in "Debugging Mode", I can plug the phone in and the Device Manager shows the "ADB". Also, the window pops up to ask about updating drivers. So I've tried going through both; I specify a location, which for me is c:\android-sdk-windows\usb_driver. It searches for a few seconds, and then says it cant find the right driver for my device.
I really want to start doing some things with this phone, but im stuck! Any help would be greatly appreciated.
read this whole thread
that should help. hopefully
and I think I've just recently read that its not really necessary to install the adb files?
timothydonohue said:
read this whole thread
that should help. hopefully
Click to expand...
Click to collapse
thanks, I'll take a look at it now!
For some odd reason, I lost adb functionality (i.e. any adb command issued receives "error: device not found"). I looked in Device Manager and noticed that MyHTC was gone! I looked at my phone and USB debugging was enabled and in charge only. I could put it in USB Drive mode and the PC would recognize it as a USB Mass Storage Device so that I could exchange and view files but no adb.
I searched and searched on this issue for hours and installed over a half a dozen "androidusb.inf" driver files several times over. Every install generated the Code 10 error where Device Manager was lacking some information from the driver file and could not start the device. I reinstalled HTC Sync and gave that a try...nothing. Downloaded USBDeview and uninstalled all HTC drivers including the HTC Android USB Device and tried again to no avail. WTF?! What else am I supposed to do?
Well, in a "what the hell, let's give it a try" kind of moment, I decided to toggle the USB debugging off and then back on (and yes, it was checked and on the whole time). WORKS!!! WHAT THE CRAP?!! MyHTC is back in Device Manager and everything is back to normal. I'm glad but irritated!
I share this story in hopes that if someone else stumbles on this problem, they will not have to go through the same headache as I did. Just thought this was odd considering how many times I have plugged and unplugged and never had any problems with adb.
Toggle USB Debugging....so simple. *rolleyes*
Same Issue
I've got the same issue on my EVO 4G. Just installed the latest CM7 and now it tell me device not recognized. If I manually install the drivers it gives me the same code 10. I can't bring up the phone as a storage device and toggling the debugging is not working. Any ideas?
SillyJay said:
I've got the same issue on my EVO 4G. Just installed the latest CM7 and now it tell me device not recognized. If I manually install the drivers it gives me the same code 10. I can't bring up the phone as a storage device and toggling the debugging is not working. Any ideas?
Click to expand...
Click to collapse
You installed the hboot drivers correctly?
Boot into recovery, with usb debugging enabled, connect to pc, it should install the drivers.
Still the same
Even when I reboot into recovery it still gives me "USB Device not recognized." I previously had MikFroyo on my phone with no problems. I'm at a loss.
SillyJay said:
Even when I reboot into recovery it still gives me "USB Device not recognized." I previously had MikFroyo on my phone with no problems. I'm at a loss.
Click to expand...
Click to collapse
You most likely have a bad cable, do you have another one you can try?
Possibility
Not at the moment but that may explain it. Still seems weird for it to just go out right as I change to CM7, but still a possibility. I am going to run and grab my other cable. Thanks for the advice.
No Luck
The new USB cable didn't fix the problem. Also, in device manager, even with the driver installed its labeled as "unknown device."
If I boot into hboot the computer recognizes it.
**update: After rebooting from the hboot, my phone is recognized by the computer however, a disk drive is not coming up in "my computer." I have USB storage turned on but Im not getting anything.**
Any help would be much appreciated!
Sad Day
Apparently the Micro USB port on the bottom of my phone is going bad... I talked with some other people who've had the same problem. HTC knows that the ports aren't very sturdy as well. Well... sad day for me.
Also if you're getting the notice from windows saying that you your device will run faster in a 2.0 usb port and you know the port is 2.0 ... chances are your port is going bad as well.
*****UPDATE*****
Flashed to MikFroyo and none of the above stated problems. I would venture that it was CM7 but apparently everyone else is able to use it so who knows.
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??
Hi,
So before going on, I've now spent couple hours trying to fix this issue, looking for tips and threads without luck.
I'm using a rooted DHD, with an Affinity rom. It works perfectly fine.
Yesterday, a friend asked me to install a custom rom on his tablet, which I did.
I had to clean all my Android drivers because the tablet wouldn't be recognized properly by my computer (no ADB driver).
In the end it didn't help and I had to use a fastboot method, which ended well.
Now, my phone doesn't prompt me what I want to do when I plug it to my computer.
I, once again, clean the usb drivers, installed HTC Sync and all its dependencies but the software doesn't recognize my phone (I couldn't care less, but I suppose it's part of my "no prompt" problem).
Of course I tried with and without AV, firewall... No luck (and I think I rooted my phone with both them ON anyway). I tried other USB ports as well
If I plug the phone without HTC Sync and its drivers installed, Windows 7 installs 3 out of 4 drivers, the last being in this suite I suppose.
I tried using the drivers provided with the sdk, they're not for that missing driver.
With the suite installed, I end up with 2 new devices on my devices manager : one "Android USB Device" labeled "My HTC" and one "mobile device" labeled as "J:" (drive name) which means no ADB drivers.
Of course, USB debug and ask when connect are both ON. I tried turning them ON and OFF, but still no luck (except a new driver installation).
ADB drivers start to install as soon as uninstall the "HTC Drive Installer" component, which is weird.
So I don't really know what to do now except that it's driving me nuts as I cannot do anything else than charging the phone now.
Is this a case of "USB brick" ? The threads I read about it all talk about "stock roms".
Try Multi Mount SD Card from the Market.
https://market.android.com/details?...vaWQubXVsdGltb3VudHNkY2FyZC53aWRnZXQuZnJlZSJd
Thanks for the alternative, it works fine
I'd still like to know how to fix this though, if anyone has any clue about it.
It's a sense rom?
Sense roms have an option to permanently put the usb state to charging or storage, etc, without prompting you again. It's an option you tick, in the settings (usb connections, or usb sync maybe? sorry, I don't use sense).
Yes it's a sense rom, with the "always ask me" option activated
Exactly. Yes.
That's strange.
Got my USB-C to USB-A cable today, so I'd like to unlock the bootloader on my Pixel C. The problem is, when I hook it up to my PC, it does recognize it in Windows as the Pixel C - I can see it and browse through the drive and folders - but when I try to run an ADB Devices command, it does not see anything.
I think I have all the latest drivers - I grabbed the Marshmallow and USB drivers from the links on this page:
http://www.androidbeat.com/2015/10/how-to-unlock-nexus-6p-bootloader/
But I'm still not getting anything. I've tried using different USB ports on my computer, both USB 2 and USB 3 ports (although I've always had success with the USB 2 ports in the past), but still no dice. I did notice when I go to Device Manager, that there is an ADB Interface Device that is unrecognized, but I've tried updating the drivers (no luck), as well as uninstalling and then rescanning for hardware changes (just get the same unrecognized ADB device as I started with).
For reference sake, I'm using a Windows 10 Pro 64bit PC.
I'm at a loss as to what to do, so any help I can get here would be greatly appreciated.
Nevermind, I was able to get it straightened out. Used the download/instructions found on this XDA thread to get everything squared away:
http://forum.xda-developers.com/showthread.php?t=2588979
Device is now unlocked and I can go ahead and set it up properly while waiting for root access to become available.
What did you do to resolve this? I am running Windows 10 64bit, with the same issue. I followed the thread for the adb installer, with no luck.
regime2008 said:
What did you do to resolve this? I am running Windows 10 64bit, with the same issue. I followed the thread for the adb installer, with no luck.
Click to expand...
Click to collapse
I think the main issue was with getting the device recognized correctly by Windows. I believe what ultimately solved the problem was going into Device Manager and clicking on the appropriate item and then updating the driver to the correct one. I don't remember what is was exactly off-hand, but if you download the file in the link I provided, there is a help image (a number of pictures, really) which spells out exactly what steps to take to get the issue resolved in Device Manger.
Note that I had to do this twice, once when the device was first connected, and then a second time as well (I believe it was after enabling fastboot, although I could be mistaken on the second part).
The whole thing is actually a pretty simple fix once I knew the correct steps to take. Was working on it for hours though until I stumbled across the answer.
Geese1 said:
I think the main issue was with getting the device recognized correctly by Windows. I believe what ultimately solved the problem was going into Device Manager and clicking on the appropriate item and then updating the driver to the correct one. I don't remember what is was exactly off-hand, but if you download the file in the link I provided, there is a help image (a number of pictures, really) which spells out exactly what steps to take to get the issue resolved in Device Manger.
Note that I had to do this twice, once when the device was first connected, and then a second time as well (I believe it was after enabling fastboot, although I could be mistaken on the second part).
The whole thing is actually a pretty simple fix once I knew the correct steps to take. Was working on it for hours though until I stumbled across the answer.
Click to expand...
Click to collapse
Funny thing is, I have tried all of those steps, and still no luck. I have deleted all of the drivers completely. Reinstalled them, and still get code 10. It seems several people are getting this issue in the thread you linked in your second post.
My Pixel C got an invalid pin error so tried to do a factory reset through android recovery but that ended to a bootloop and the tablet is simply useless. Thought I'd try to install OS again see if that would bring it back but I can't even get it recognised in the pc. I've put it in fastboot mode and it won't even acknowledge I've connected anything. Nothing shows up on Device Manager. Am I doing something wrong here? I'm out of ideas