Database Develop

[SOLVED] Flashing issues. Error 170 & 171 Win7 and Vista users

After I started using my Win 7 system, I had to do the whole process of updating and flashing my device. After like 3 hours going back and fourth to find the solution, I found it is a pretty strange way. In a place where I would never have thought before:
The problem is about Drivers.
I've found there are two type of drivers:
1. ADB/Bootloader interfaces (usb_drivers we download from Android SDK). This are useful in the first part of the HOWTO since we need to run some ADB commands. This might be also useful during the rooting process
2. MyHTC drivers (both boot and standard). This are the basic HTC drivers for using with several software like HTC Sync AND for flashing phone. This are installed during the HTC Sync installation process.
How to know which driver is using at each time?
Under Control Panel -> System -> Device Manager -> We might find a driver called Android Phone.
1. With the phone in the Start menu into it we might see either:
a) ADB Interface
b) My HTC
2. If we go into the bootloader (rebooting device, volume down + power button) we might see
a) Bootloader
b) My HTC
If we need to FLASH, the we need in both parts My HTC
If we see anything else, we need to update the driver. Just by going into properties of the driver, Controller, Updating Controller -> Find Controller into the PC -> Select from the list of controllers of this PC -> Use Disk and we must look for the HTC Driver that is installed during the HTC Sync Installation process (Normally this is into Program Files-> HTC -> HTC Driver).
Finally we can update the driver by selecting the My HTC one from the list.
This worked perfectly for me, and make me discover this issue that may help some people. I write this as a complement for my guide for flashing to make it wider and more complete: http://forum.xda-developers.com/showthread.php?t=603286

Sorry to bump an old thread, but I'm having this issue with a friends HTC Legend.
MiSSigNNo said:
by going into properties of the driver, Controller, Updating Controller -> Find Controller into the PC -> Select from the list of controllers of this PC -> Use Disk and we must look for the HTC Driver that is installed during the HTC Sync Installation process (Normally this is into Program Files-> HTC -> HTC Driver).
Finally we can update the driver by selecting the My HTC one from the list.
Click to expand...
Click to collapse
What do you mean exactly by going into the properties of the driver? (Win 7 64bit)
Thanks.

MiSSigNNo said:
After I started using my Win 7 system, I had to do the whole process of updating and flashing my device. After like 3 hours going back and fourth to find the solution, I found it is a pretty strange way. In a place where I would never have thought before:
The problem is about Drivers.
I've found there are two type of drivers:
1. ADB/Bootloader interfaces (usb_drivers we download from Android SDK). This are useful in the first part of the HOWTO since we need to run some ADB commands. This might be also useful during the rooting process
2. MyHTC drivers (both boot and standard). This are the basic HTC drivers for using with several software like HTC Sync AND for flashing phone. This are installed during the HTC Sync installation process.
How to know which driver is using at each time?
Under Control Panel -> System -> Device Manager -> We might find a driver called Android Phone.
1. With the phone in the Start menu into it we might see either:
a) ADB Interface
b) My HTC
2. If we go into the bootloader (rebooting device, volume down + power button) we might see
a) Bootloader
b) My HTC
If we need to FLASH, the we need in both parts My HTC
If we see anything else, we need to update the driver. Just by going into properties of the driver, Controller, Updating Controller -> Find Controller into the PC -> Select from the list of controllers of this PC -> Use Disk and we must look for the HTC Driver that is installed during the HTC Sync Installation process (Normally this is into Program Files-> HTC -> HTC Driver).
Finally we can update the driver by selecting the My HTC one from the list.
This worked perfectly for me, and make me discover this issue that may help some people. I write this as a complement for my guide for flashing to make it wider and more complete: http://forum.xda-developers.com/showthread.php?t=603286
Click to expand...
Click to collapse
in english please? I can't understand HOW you are doing this... I am trying to flash a HTC Desire S with Android ICS (latest from htcdev WWE) and it connects fine, but when I get to "Waiting for Bootloader........" it does that for a minute, then says "Error [171] USB Connection Error" The phone shows the HTC logo with black screen. My laptop says "USB Device Not Recognized" too and it fails. What can I do to fix this? I have installed the ADB and SDK also the HTC drivers and HTC Sync, tried everything please help

mattygaga2012 said:
in english please? I can't understand HOW you are doing this... I am trying to flash a HTC Desire S with Android ICS (latest from htcdev WWE) and it connects fine, but when I get to "Waiting for Bootloader........" it does that for a minute, then says "Error [171] USB Connection Error" The phone shows the HTC logo with black screen. My laptop says "USB Device Not Recognized" too and it fails. What can I do to fix this? I have installed the ADB and SDK also the HTC drivers and HTC Sync, tried everything please help
Click to expand...
Click to collapse
I'm not sure if this applies to HTC Desire S... this was meant to be used for HTC Tattoo (HTC Click)

MiSSigNNo said:
I'm not sure if this applies to HTC Desire S... this was meant to be used for HTC Tattoo (HTC Click)
Click to expand...
Click to collapse
Ah I see. Any idea how I could probably fix this? I'm using Windows 8 and I have scoured XDA and the internet for 29 hours straight for answers and turned up empty. I have no MicroSD card to perform the update using the PB99xx.zip method and all other methods are useless. I just want a straight-forward RUU update for my phone but can't seem to do it without that silly Error 170/171 and USB Device Not Recognized errors

[Q] ABD Drivers + Windows 7 issues (plus a couple more questions)

Hello XDA Community.
I'm attempting to install the new RC of CyanogenMod-6 for the Hero CDMA. I'm currently running the stock 2.1 version of Android. I've been following the guides that were referred to in the thread (I tried posting the urls but new users can't do so to prevent spam).
I've successfully rooted my phone and now I'm trying to do a Nandroid backup. I'm running Windows 7 32-bit and have hit a road block with ADB not recognizing my device. I followed the guide put together by Nephron to install the Android SDK. I've spent several hours going through threads and doing google searches looking for the solution. I have debugging turned on and I don't mount my SD drive when I plug the USB cord in. I've used USBDeview as some have suggested to delete current HTC drivers and then reinstall - no luck.
Here is a screen shot of what happens when I plug in my Hero:
See attached - "failedinstall.jpg"
Then I'll go to device manager to manually install the driver (it never allows me to manually select upon connection for some reason):
See attached "devicemgr.png"
And then this is the message I get when I point it to the "right" folder with the drivers:
See attached - "unabletoinstall.png"
So, on the Android SDK site I noticed this message:
"The USB driver for Windows provides support for the following Android-powered devices:
T-Mobile G1* / ADP1
T-Mobile myTouch 3G* / Google Ion
Verizon Droid*
Nexus One
* Or similar hardware on other carriers
Any additional devices will require Windows drivers provided by the hardware manufacturer.
^So is all of this HTC's fault? I've downloaded a couple of different .zip folders from different threads claiming that these drivers would work. But none of them have yet to do the trick for me.
I'm new at this so I have a few other questions as well:
Most guides I've read about how to do a Nandroid backup always recommend flashing a ROM b/f doing a backup. But I want to backup my current stock rom and settings before I flash. Wouldn't I want to create a recovery image before installing any other ROMs? Perhaps I'm misunderstanding some requirements?
Referring again to the thread on the CyanogenMod RC, can someone help me understand step #3? How do I know if it is necessary to update my radio? What implications does this have? I tried looking for info about this on the wiki and I couldn't find anything comprehensive enough to answer my question.
I'd appreciate any guidance!

Before you modify anything you will want to boot into recovery, assuming you flashed one, by holding down Home and turning the phone phone back on(power button). But since you don't have adb working then you probably haven't. You can still do this using terminal on your phone.
Download terminal emulator from market and then download a revoery image (AmonRa 1.6.2 or Darch's 1.7xx) and then mount your sdcard to the computer and transfer the recovery to the root of the sdcard. Open up terminal emulator and type in
Code:
su
cd /sdcard
flash_image recovery recovery-RA-heroc-v1.6.2.img(type the exact file name of the recovery you are using)
reboot recovery
If you had factory 2.1 on your phone then you have the latest radio. The radio can be flashed just like any ROM, but make sure that the radio is not for GSM phones as this will destroy your phone.
Instructions from Android Developers and ADB, Fastboot, and Nandroid for Noob
Download the latest Android SDK.
Unzip to C:\AndroidSDK
Right-click on (My) Computer, and select Properties
Go to Advanced settings
XP: Click the Advanced tab
Vista/7: Click Advanced system settings on the left
Click the Environment Variables button
double-click on Path (under System Variables)
Add the full path to the tools/ directory:
C:\AndroidSDK\tools\
(make sure a semicolon ( separates this new path from all the others)
Latest windows sdk version appears to need: "C:\AndroidSDK\android-sdk-windows\tools", install location may change with further updates..
Run C:\AndroidSDK\SDK Setup.exe
If you get an error about not having Java SDK installed but you do, add the path to 'bin' within your Java installation location to the Path environmental variable as described above before the sdk entry you just made. (eg add "C:\Program Files\Java\jdk1.6.0_20\bin;") This is likely to only be necessary where the 64 bit Java SDK is installed (obviously) on a 64 bit machine.
If it gives you an error about http go to settings and click on "Force http//....."
Unselect all options except for the USB driver
If you can't get the setup to work, download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
On your phone, click Settings > Applications > Development and make sure USB Debugging is on.
Plug your phone into your computer via USB cable (it needs to be on). It should say installing drivers if using Windows.
After it installs the drivers, goto the Start menu and type cmd into the search bar (Vista or higher) or click Run then type in cmd (XP) to open the command prompt.
Type the following into the command prompt window:
adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set. If you do NOT see a serial number, then we need to reinstall the drivers.
Download USBDeview
While the phone is still plugged in, open USBDeview and sort by manufacturer. Find all the HTC/Android drivers and uninstall them all. (Windows Vista requires program to be run as an administrator, otherwise files won't uninstall.)
Once all have been uninstalled, unplug the phone from the USB cable and plug it back in.
The correct drivers should reinstall automatically (check the drivers as they are installing, one should say ADB Device driver).
To check, go to Devices in your Start menu then click on the “Android Phone”. Click on the Hardware tab, and check the list of drivers for ADB Interface under Type.
Done! Now you can use ADB to alter your phone from your computer.
If all else fails try installing HTC Sync software-- http://member.america.htc.com/download/Driver/HTC Hero (Sprint)/HTC_Sync_2.0.40.exe and then removing the drivers for it and then trying to install the android sdk drivers
Or you can dual boot with Linux and all you will need to do is download and unzip android sdk and edit 2 files and everything will work.

WOW>>>>>no that is way to confusing. the best thing to do is install vmware workstation. Then do a virtual WINDOWS XP MODE. from there you will be able to install the drivers and such in order to get the phone to be seen.

the version of htc sync i used for all my computers including win 7 was 2.0.33
if you want it then just pm me and I will get it to you
they don't offer it for a download anymore
this version corrected all my driver issues

[Q] Bootloader unlock stuck on waiting for device

I've searched and searched for a solution to this, nothing is working. Really need help guys.
Phone is on stock ICS rom, PC is Win8 Pro x64. All three files are in the folder, SDK is installed (x64 version), Google USB driver installed, Java for windows installed, and HTC Sync installed but not running.
When in FASTBOOT and USB connected it shows FASTBOOT USB. Device manager shows Android Phone - Android ADB Interface. Is this correct or should it show something else in device manager?
No matter what I've tried when running fastboot oem get_identifier_token in command prompt I get waiting for device. Also running fastboot devices returns nothing.
Don't know what else to try... Seems it doesn't recognize the device but it's in device manager.
Edit: have also tried different usb ports and I know the cable works.
Edite 2: I fixed it. Took me hours to get this working but for any one struggling like I was here is what I did.
Got rid of all the drivers and started back at Android 1.0 in device manager. Manually installed the official SDK google usb driver and selected Android Bootloader Interface for Android 1.0. Also boot the phone and manually install again and select Android ADB Interface.
Here is what really caused me problems. The HTC tutorial I looked at said to take adb.exe, fastboot.exe, and adbWinApi.dll and put them in their own folder. This absolutely does not work for me even now. I used the directory straight from the SDK (sdk\platform-tools) and added fastboot.exe from a previous sdk revision into that folder. Now everything works!!! Finally!

Hi everyone!! I have the same issue as brother bassvoykevlar but the solution here expresed is not all clear to me. Can anyone please give me a hand on this, i am really mad with it . Thanks in advance.

The Best Solution
this problem has also happened with me and i found a solution to this,
this usually happens if your system lacks fastboot drivers.
ADB drivers can only Run ADB shell so that is why you need to have fastboot drivers as well to use fastboot commands.
i think you must have tried this code:
"fastboot oem unlock"
then cmd may have got stuck on "waiting for device"
don't worry install drivers for fastboot then it should work.
google it then get it.
there is 15seconds ADB,fasdtboot installer available try that.
then give it another try.

HTC One M7 shown as offline in ADB

Hi,
For some reasons, I flashed my M7 phone with Lollipop 5.0 GPE. Everything is done w/o error & I ended up booting into Lollipop. But unfortunately, the USB debugging no longer work as there is no RSA key fingerprint dialog prompted for permission. I was trying the following approaches but none is working:
1. Update usb device to latest version
2. Update adb to latest version: 1.0.32
3. Update android sdk to latest version
4. Revoke/Disable/Enable USB debugging; reboot device; kill/start adb server; Change cable
5. Delete adb_key/adbkey.pub files
6. Manually copy adbkey file to /data/misc/adb/adb_key
7. Change pc: Windows 10; Debian 8 linux & Macbook Pro.
adb devices command shows my device as offline. Sometime, it shows my device multiple times & of cos, offline. Anyone knows how to make RSA key dialog to be prompted again, please help.

Hi, i am having exactly the same issue with android 5.1.
I've tried all the things you have listed and tried multiple adb drivers including naked and universal adb driver.
Have you come to a solution in the mean time or does anyone else know how to solve this issue?

[SOLVED] Please Help! Can't get fastboot to recognize device, but adb does

Former-Prime R1 HD 16GB
Windows v8.1
TL;DR:
I am unable to get my phone to be recognized in fastboot by the fastboot utility, yet it is recognized by adb. I've tried a couple of different sources for drivers, both signed and unsigned. Each time I've installed drivers I've gone into Device Manager and removed previous disconnected device instances along with the drivers (checked remove driver box). Besides the fact that adb sees the phone fine with the cable I'm using, it's the same cable I have successfully used with my Samsung and Nexus devices. I'm at my wit's end. :crying: I could really use some help.
Full version:
I've followed the instructions from this thread to flash my phone into an OEM non-Prime device:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
It's now running V12. I want to verify the state of the bootloader and jump through the hoops to safely put V17 on it (without whacking the preloader, etc.). My problem is that when I try fastboot devices no devices are listed. However, adb devices shows the phone.
I installed ADB and fastboot v1.4.3 using the package from this thread:
https://forum.xda-developers.com/showthread.php?t=2588979
I've tried a couple of different sources for drivers, both signed and unsigned. Each time I've installed drivers I've gone into Device Manager and removed previous disconnected device instances along with the drivers (checked remove driver box). I've got tzul's signed drivers installed which were obtained from this post using the enclosed instructions (both those in the "Android" and "CDC" folders):
https://forum.xda-developers.com/showpost.php?p=67927242&postcount=23
I also have the Android SDK's Platform Tools and Google USB driver installed and tried the adb and fastboot from there with the same results.
When booted to the Android OS, the phone shows up as Android Composite ADB Interface in Device Manager. When I use adb to try and reboot the phone into fastboot via adb reboot fastboot it merely reboots into the OS. To get into fastboot mode I have to do it via the bootloader (power+vol. up). When attatched in fastboot mode the phone shows up in device manager under "Other devices" as "Android" with The Yellow Triangle of Doom, and says drivers for the device aren't installed (Code 28). From what I've read, the drivers it's looking for are the in the "Android" folder of the drivers .zip I downloaded, which I have installed per the instructions.
Can someone please help me figure out what I've done incorrectly?

Fixed
As I had surmised, it was a driver issue. One of the driver bundles I had downloaded from androidmtk.com or another site foobar'd me. But before I had this straightened out, I gave up and used a Linux Mint virtual machine to verify my bootloader status, etc.
The way my drivers got straightened out was that I coincidentally ran Windows Update as I had updates available for which enough time had passed without reports of problems. Update offered me the following updates:
Important
Windows 8.1 Drivers
Microsoft - Other hardware - MTP Device
TP-LINK - Other hardware - Android Bootloader Interface
Windows 8.1 and later drivers
Samsung - Other hardware - Samsung Mobile MTP Device
Optional
Windows 8.1 Drivers
MediaTek - Other hardware - Android Composite ADB Interface
After installing these I again tried to use fastboot from my Windows box and it worked fine. So, one of the driver packs I installed screwed up my MTP drivers evidently (both the updates offered were from early last year). The TP-LINK driver was the VCOM I needed for fastboot to work.
So, all's well that ends swell.

Amazon Prime running on V.6.1
Windows 7 x64
I am having similar issues but I don't fully understand how the OP solved this problem. I believe I am connecting properly with ADB but no response from fastboot. Here is what I have done so far:
1) Installed the "15 Sec ADB Tool". Drivers seem to be working but could not located the ADB folder the tool was supposed to create. I suspect drivers were installed correctly because under Device Manager I have "Android Phone > Android Composite ADB Interface"
2) Directly downloaded latest SDK Platform Tools, which includes adb.exe & fastboot.exe, among other files. Tried testing the tools with the following results:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
5DFYRKKFQWBEQ4LJ unauthorized
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>fastboot devices
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>
Phone is turned on while doing the commands above. Could someone shed some light? Is the ADB response adequate? And should I get a fastboot response as well? If so, what could be the problem?
Lastly, phone has UBS Debug mode enabled.
Thanks in advance!

OldSkewler said:
Amazon Prime running on V.6.1
Windows 7 x64
I am having similar issues but I don't fully understand how the OP solved this problem. I believe I am connecting properly with ADB but no response from fastboot. Here is what I have done so far:
1) Installed the "15 Sec ADB Tool". Drivers seem to be working but could not located the ADB folder the tool was supposed to create. I suspect drivers were installed correctly because under Device Manager I have "Android Phone > Android Composite ADB Interface"
2) Directly downloaded latest SDK Platform Tools, which includes adb.exe & fastboot.exe, among other files. Tried testing the tools with the following results:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
5DFYRKKFQWBEQ4LJ unauthorized
Click to expand...
Click to collapse
This shows adb is on , on your phone but you did not allow the connection. =. When you first connect pc to phone with usb cable and adb enabled , you should get a pop up window on the phone. You may need to wake the screen and unlock to see it. The window asks you to authorize the connection
OldSkewler said:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>fastboot devices
Click to expand...
Click to collapse
You also missed a step here. You needed to reboot phone to bootloader /fastboot mode before asking to list fastboot devices.
So before that line you should have done "adb reboot bootloader"
OldSkewler said:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>
Phone is turned on while doing the commands above. Could someone shed some light? Is the ADB response adequate? And should I get a fastboot response as well? If so, what could be the problem?
Lastly, phone has UBS Debug mode enabled.
Thanks in advance!
Click to expand...
Click to collapse

mrmazak, you are absolutely right on both items. I wish I had come across something explaining this earlier... spent a lot of time sorting this out!
Hopefully this will help someone in the future!