It's probably something simple, but I would much rather ask a stupid question than be the enraged owner of an Incredibly expensive paperweight. I've been following the How 2 thread, and I've ran into a little issue.
I'm running the official Froyo 2.2 OTA on the Droid Incredible, but am looking to root my device with unrevoked 3.3. I've read through the procedures and searched through support topics, but with no success.
I downloaded the recovery tool, the Android SDK, and the usb drivers from revoked, unzipped them all and installed the recovery tool and the sdk.
I put the phone into HBOOT and installed the driver like the unrevoked guide said, removed the device and reconnected it to ensure that the driver was associated with the device and it is.
Here's the problem.
I reboot into the Android OS and reconnect the device to my pc. Now the driver is listed as 'ADB' in the device manager, which is not the same driver. The driver isn't installed correctly as there is a yellow exclamation point attached to the icon. I opened cmd, changed the directory to appropriate Android SDK directory, ran ADB and the command 'adb devices' to insure that my device was recognized. It is not.
So how do I repair/reinstall the ADB driver so that I don't brick my Incredible? Any and all help is tremendously appreciated
This helped me... http://www.droidforums.net/forum/dr...b-windows-7-64bit-should-also-work-32bit.html
I don't know if the motorola driver will work with htc, but i understand what you're saying. I'll find the standard google driver and try to install that the way the link mentioned. I just need to figure out how to do it in xp, as I am not a windows 7 user.
Thank you.
me144 said:
I don't know if the motorola driver will work with htc, but i understand what you're saying. I'll find the standard google driver and try to install that the way the link mentioned. I just need to figure out how to do it in xp, as I am not a windows 7 user.
Thank you.
Click to expand...
Click to collapse
I have an incredible and it worked for me...good luck.
me144 said:
It's probably something simple, but I would much rather ask a stupid question than be the enraged owner of an Incredibly expensive paperweight. I've been following the How 2 thread, and I've ran into a little issue.
I'm running the official Froyo 2.2 OTA on the Droid Incredible, but am looking to root my device with unrevoked 3.3. I've read through the procedures and searched through support topics, but with no success.
I downloaded the recovery tool, the Android SDK, and the usb drivers from revoked, unzipped them all and installed the recovery tool and the sdk.
I put the phone into HBOOT and installed the driver like the unrevoked guide said, removed the device and reconnected it to ensure that the driver was associated with the device and it is.
Here's the problem.
I reboot into the Android OS and reconnect the device to my pc. Now the driver is listed as 'ADB' in the device manager, which is not the same driver. The driver isn't installed correctly as there is a yellow exclamation point attached to the icon. I opened cmd, changed the directory to appropriate Android SDK directory, ran ADB and the command 'adb devices' to insure that my device was recognized. It is not.
So how do I repair/reinstall the ADB driver so that I don't brick my Incredible? Any and all help is tremendously appreciated
Click to expand...
Click to collapse
Go here and follow her steps exactly....
http://www.droidforums.net/forum/dr...ow-root-stock-2-2-using-unrevoked-3-32-a.html
Sent from my Incredible using XDA App
Related
I was reading some instruction from htcevohacks.com. Since i didn't decide to root or not yet, i just want to install those sdk and driver on my pc. sdk part is easy, and i installed it successfully. But adb driver part is tricky.
I followed instruction, turn on "USB debugging" in the settings, and reboot phone into recovery mode, plugged usb cable. However, the device manager of windows 7 didn't find any adb devices, then i tried refresh, still no lucky at all. what should I do to find adb device then update driver? or i have to root first b4 installing adb driver?
Install HTC Sync, then reboot your computer
JvIo55iBl3r said:
I was reading some instruction from htcevohacks.com. Since i didn't decide to root or not yet, i just want to install those sdk and driver on my pc. sdk part is easy, and i installed it successfully. But adb driver part is tricky.
I followed instruction, turn on "USB debugging" in the settings, and reboot phone into recovery mode, plugged usb cable. However, the device manager of windows 7 didn't find any adb devices, then i tried refresh, still no lucky at all. what should I do to find adb device then update driver? or i have to root first b4 installing adb driver?
Click to expand...
Click to collapse
I did, actually. As a matter of fact, i do have that sync icon in my task bar
I am not sure, but i was wondering if the adb driver is necessary to be installed?
Yeah the HTC Sync.exe will have the drivers. Check your hardware configuration to make sure it's installed right then in the folder with adb installed use the command prompt to go: adb devices -> You should see a device with numbers. then you correctly installed it
adseguy said:
Yeah the HTC Sync.exe will have the drivers. Check your hardware configuration to make sure it's installed right then in the folder with adb installed use the command prompt to go: adb devices -> You should see a device with numbers. then you correctly installed it
Click to expand...
Click to collapse
the problem right now is the device manager cannot even find any "other device" with question mark(when i plug the phone, which is under recovery mode, by usb cable)
JvIo55iBl3r said:
the problem right now is the device manager cannot even find any "other device" with question mark(when i plug the phone, which is under recovery mode, by usb cable)
Click to expand...
Click to collapse
this should definitely be in the Q&A board, not the developers board.
since you've already installed htc sync, the drivers should already be properly installed on your system.
ive only ran win xp and vista, not familiar with win 7, but if its designed the same, having no question marks, sounds like all connected devices have drivers properly installed ...
how do you know your adb drivers aren't installed? have you tried using adb? if so, what error does adb show?
Exit HTC sync first on your computer so it is not running or just uninstall it. It should find it after that.
joeykrim said:
this should definitely be in the Q&A board, not the developers board.
Click to expand...
Click to collapse
Sorry about that, will do next time
joeykrim said:
since you've already installed htc sync, the drivers should already be properly installed on your system.
ive only ran win xp and vista, not familiar with win 7, but if its designed the same, having no question marks, sounds like all connected devices have drivers properly installed ...
how do you know your adb drivers aren't installed? have you tried using adb? if so, what error does adb show?
Click to expand...
Click to collapse
i tried command "adb device", i got some serial number, does that mean adb driver has been successfully installed on my pc, and work properly?
JvIo55iBl3r said:
Sorry about that, will do next time
i tried command "adb device", i got some serial number, does that mean adb driver has been successfully installed on my pc, and work properly?
Click to expand...
Click to collapse
any help? anyone?
Ok, I have a T-Mobile locked and branded Desire and so trying to create a Goldcard but it just gives me Permission Denied when trying to get the CID, what am I doing wrong? I have followed the steps to the T
try the goldcard program?
YES!! Please seriously need help aswell with this. Have a sim free desire and I get to the line of code in the command prompt with
"ADB shell cat/sys/class/mmc_host/mmc1/mmc1:*/CID" and it just says device not found.
I am new to android so i'm pretty clueless with this. Any help would be greatly appreciated.
Kleptomaniac said:
... and it just says device not found.
I am new to android so i'm pretty clueless with this.
Click to expand...
Click to collapse
So about 'device not found'. I had this 'issue' when rooting mine a few weeks ago, so here's what I had to do.
When rooting, you're gonna be using the ADB tools to interface with your phone through USB. This would mean that the computer needs specific drivers for ADB to work properly, which for some reason, did not install well. I'm running Win7 x64 and had a hard time setting it up initially.
SO what you want to do is to first go to Device Manager on the PC and uninstall the drivers for anything related to the phone - it'd probably show up under 'Other devices' with a driver issue. Do that and unplug the phone.
Next, go to install PdaNet. Just run the exe and it will install the drivers you need for ADB to work! Once this is all done you can uninstall the PdaNet program if you don't use it - the drivers will still remain.
When you plug in your phone (it might prompt during the installation, I don't remember) and head to device manager now, you'll see a new entry at the top called Android Phone, with a device called Android ADB Interface. Once you see this, then you're good to go with the rest of the goldcard instructions you were following.
Just to be sure, reboot the PC and go to the Android SDK\Tools in a cmd prompt and type in adb devices. It should return with the serial number of your phone.
That's it, hope it helps!
Thanks alot man its nice to know people here are willing to help. I didn get the drivers but I used HTC sync instead to get them up and running, then after awhile of it still not working I found the goldcard program and it worked! Now all I have to do is wait for this root download to finish...
I'm having a problem that is affecting two different computers, both of them gives me a 'adb device not found' message and it won't list my G2 when I typed in 'adb devices', the only difference between them is that in my laptop it gives me a message that it couldn't successfully install 'ADB'(Windows 7 Home 64 Bit) while my older Windows XP SP3 desktop gives me no such message.
Before replying, please note that I have Checked USB debugging and have done everything in the ADB for dummies thread, which includes the adding the tools part to Path and I have reinstalled my drivers more than five times (with and without USBDeview), each time with a different method. I am not mounting my SD card. I have also tried the PDAnet method. I have modified the android_winusb.inf file and reinstalled it. Tried uninstalling my USB Root Hub's as suggested by another. I have updated my USB Driver in SDK to rev 4. There aren't any yellow checkmarks in my Device Manager, however I have noticed that I only have 'Android Phone' and the subcategory 'Android Composite ADB Interface', I've heard that I should see another category like 'ADB Device Driver'. I have tried to fix this problem for five hours to root my G2, any help would be appreciated very much.
Where did you get your drivers from ? In the guide at http://forum.xda-developers.com/showthread.php?t=865685 I suggest getting them from the HTC Sync software, not the SDK.
I walked a guy with Win 7 through this the other day, and it worked fine for him.
I know it sounds like a stupid question but is the adb.exe file in your tools folder? If not, try running an advance search and only in the titles search for "drivers". You should only get about 10 returns. The top one should have some files attached named tools. Download them and extract the files to your tools folder. Then try running the adb devices again, yesterday I had to do that cuz for some reason adb.exe wasn't there.
I second getting the drivers from HTC Sync and remember the desire z is the same a G2 so run the seach for desire z for htc sync.
Sent from my HTC Vision using XDA App
ddgarcia05 said:
Then try running the adb devices again, yesterday I had to do that cuz for some reason adb.exe wasn't there.
Click to expand...
Click to collapse
adb has been taken out of the latest version of the SDK "Starter" package (the 2.3 one). It used to be there in the 2.2 version. So now you have to run SDK Manager to install the platform-tools add-on, then you get adb. This is all in my updated adb guide
ddgarcia05 - I didn't have adb in my tools folder, however I don't believe that you need adb.exe in that folder, just in the 'platform-tools' folder or in the system-32 fodler. Thanks for trying.
steviewevie - Thank you so much! I found your adb for noobs thread and it seems that installing HTC Sync after uninstalling my previous drivers via USBDeview worked like a charm. I also didn't see that you had to add 'platform-tools' in the Path in the various other threads, so I did that too. +1 Thanks to your helpful thread!
Hi guys
I did own a Sapphire/Magic back in the days and came back to Android after some skipping done during the last year. Back then installing usb drivers and adb was easy: plug in the Sapphire, point Windows to the drivers folder, done.
With the Vision/Desire Z it was much more complicated. I did use the old drivers from back then and ran into problems. Device manager had an ADB device listed, ADB couldn't find it though. Once I got it working in Android, it wouldn't interface with the recovery adb though. Once I got that working, it wouldn't show/mount the SD card anymore. Short: a huge mess.
Right now I have everything more or less working (still using the old drivers I used with the Sapphire) but it's not really right, I tried an RUU the other day and it would fail because my ADB/RUU ADB/Driver combination wouldn't match.
Long story short: where did you guys get your drivers from to interface the Vision with ADB/Fastboot?
Update the SDK ...this time its in platform tools. run the sdk update and download the usb drivers. Refresh your SDK.
If you don't want to do that...then install pdanet just to grab the drivers
Or go to cyanogenmod the drivers may be avail in a post from ciwrl in vision.dz download section.
All right, I'm d/ling the Java JDK as prompted by the latest SDK installer
Thanks!
I did this too (SDK + Platform tools) to get ADB/shell. However, I never got fastboot to work (even tried fastboot-mac). Not sure what I was missing, but flashing via SD (including radio) has been working thus far for me. Any recommendations on where to get more info on "fastboot" process, specifically on a Mac?
Hmm... you did notice that the fastboot binary is - at least on Windows - in a different folder than ADB, right?
On Windows its two different paths pointing to either ADB or Fastboot.
[posted on the go]
Greetings XDA,
I'm trying to hurry and unlock my One before Verizon locks 'er down tight, but i'm having trouble getting the Fastboot driver installed.
I've installed the java run time environment, sdk, and even the HTC my sync settings (with drivers) and am seeing "My HTC" under Android ADB devices while booted normally, but as soon as I jump to fastboot, the "My HTC" receives an exclamation point and the device driver says not installed.
I'm running Windows 8 x64 and tried these instructions here: http://forum.xda-developers.com/showthread.php?t=2232799
Any help? Any one?
MetroGnome711 said:
Greetings XDA,
I'm trying to hurry and unlock my One before Verizon locks 'er down tight, but i'm having trouble getting the Fastboot driver installed.
I've installed the java run time environment, sdk, and even the HTC my sync settings (with drivers) and am seeing "My HTC" under Android ADB devices while booted normally, but as soon as I jump to fastboot, the "My HTC" receives an exclamation point and the device driver says not installed.
I'm running Windows 8 x64 and tried these instructions here: http://forum.xda-developers.com/showthread.php?t=2232799
Any help? Any one?
Click to expand...
Click to collapse
I had this problem too running windows 8 x64. I think my problem was that I installed the sdk first with google's USB driver and not HTC's driver. What I did to make it work is switch computers over to my wifes which at the time I hadn't installed anything on yet. I went to htcdev.com and went to the part of the site where it is step-by-step on how to unlock the bootloader. I installed the Java Runtime Environment on the link provided on the upper right side of the site, then I installed the HTC sync manager on the link provided as well. I had my phone connected to my computer usb 2.0 (not usb 3.0) the whole time and with USB debugging enabled (not in fastboot mode, but with phone normally on). After that I took the three files from the sdk that htc wants you to place in a separate folder and put them in c:\Android. I did not install anything from sdk this go around.. i just took the three files out and put them in a separate folder as instructed by htc. After that I opened cmd and directed it to the folder I placed the files in (cd c:\Android) and ran command "adb reboot bootlader" Once I did that and hit fastboot the "My HTC" in device manager no longer had an exclamation point. So in summary, I couldn't reverse the drivers from my computer that I installed first so I resorted to using my wife's computer that didn't have anything installed yet. I installed JRE, then HTC sync software, and just used the 3 files HTC wants from sdk and placed them into a separate folder. I didn't install anything from sdk. It all worked after that. I don't have instructions on how to reverse the usb drivers you have already installed because I couldn't figure it out... in fact, I formatted windows on my pc and am reinstalling. Hope this helps.
-eL
Sadly...
eL_777 said:
I had this problem too running windows 8 x64. I think my problem was that I installed the sdk first with google's USB driver and not HTC's driver. What I did to make it work is switch computers over to my wifes which at the time I hadn't installed anything on yet. I went to htcdev.com and went to the part of the site where it is step-by-step on how to unlock the bootloader. I installed the Java Runtime Environment on the link provided on the upper right side of the site, then I installed the HTC sync manager on the link provided as well. I had my phone connected to my computer usb 2.0 (not usb 3.0) the whole time and with USB debugging enabled (not in fastboot mode, but with phone normally on). After that I took the three files from the sdk that htc wants you to place in a separate folder and put them in c:\Android. I did not install anything from sdk this go around.. i just took the three files out and put them in a separate folder as instructed by htc. After that I opened cmd and directed it to the folder I placed the files in (cd c:\Android) and ran command "adb reboot bootlader" Once I did that and hit fastboot the "My HTC" in device manager no longer had an exclamation point. So in summary, I couldn't reverse the drivers from my computer that I installed first so I resorted to using my wife's computer that didn't have anything installed yet. I installed JRE, then HTC sync software, and just used the 3 files HTC wants from sdk and placed them into a separate folder. I didn't install anything from sdk. It all worked after that. I don't have instructions on how to reverse the usb drivers you have already installed because I couldn't figure it out... in fact, I formatted windows on my pc and am reinstalling. Hope this helps.
-eL
Click to expand...
Click to collapse
Sadly, i don't have such a machine lying around. The wife's comp has the sdk installed as well (she's a nexus user). Although, on her windows 7 machine, in fastboot i do see MyHTC driver as ok, but when i run the "fastboot oem get_token_modifier" command, i get "(bootloader) [ERR] Command error!!! OKAY finished"
so something still quite wrong!
I don't think the Fastboot drivers work on Windows 8.
Spent all day trying, and never got recognized in ADB. Used co-worker's computer with Windows 7, worked like a charm.
jadesocket said:
I don't think the Fastboot drivers work on Windows 8.
Spent all day trying, and never got recognized in ADB. Used co-worker's computer with Windows 7, worked like a charm.
Click to expand...
Click to collapse
.... This probably explains my problem as well. Will try on a Windows 7 computer in the morning and report back to see if that was the problem.
jadesocket said:
I don't think the Fastboot drivers work on Windows 8.
Spent all day trying, and never got recognized in ADB. Used co-worker's computer with Windows 7, worked like a charm.
Click to expand...
Click to collapse
ADB and Fastboot both work fine on Windows 8. I had to install the newest 4.3.0.001 drivers to get ADB to recognize my One on my Windows 7 partition, despite having had the most recent behind that. My Windows 8 partition worked like a charm because I had more recently installed the updated drivers on it. It's also possible you were connecting your phone to a USB 3.0 port. ADB/Fastboot is "wonky" over USB 3.0, and if you don't have the correct USB 3.0 drivers, you have no chance at all. Also, you need USB Debugging turned on, which can be done in this version of Android by going to Settings -> About -> Software Information -> More, then tapping on the build number 7 times, unlocking developer options, then going to Settings -> Developer options, and checking USB Debugging.
And all this may be moot for now, as it appears anyone who wasn't previously unlocked won't be able to for a while.
IceDragon59 said:
And all this may be moot for now, as it appears anyone who wasn't previously unlocked won't be able to for a while.
Click to expand...
Click to collapse
I can confirm. I successfully got fastboot to run on OS X, but when I try to send my token via HTCDev, I'm met with error 160: MID not Allowed..