Sign up ×
Android Enthusiasts Stack Exchange is a question and answer site for enthusiasts and power users of the Android operating system. It's 100% free, no registration required.

I've read a lot of articles about this problem but I can't resolve it. I decided to install my developer application on phone using wifi. To do this I need to do some things with my phone. The first step is to unlock bootloader. I stack on step 8, fastboot oem get_identifier_token shows info < waiting to device >. adb sees my device but fastboot can't. An idea?

My phone is HTC Wildfire S and these are steps which I am following:

  1. I restarted phone and entered into FASTBOOT USB mode
  2. I tried to run fastboot oem get_identifier_token command but without success.

I use Windows 7 Professional and my phone is recognized as HT1CSTR05155.

share|improve this question
What is the phone model, and what instructions are you following? Did you reboot the phone in fastboot mode (e.g., by using adb reboot bootloader)? What OS you are using on the computer, and how does it recognize the phone at that time? – Sergey Vlasov May 26 '13 at 18:40
Sergey, see my edit. – pepuch May 26 '13 at 18:57
Did you update the bootloader? You should see ***LOCKED*** on the phone screen after you boot into the bootloader, otherwise you do not have the proper bootloader version for unlocking. Also check that the phone appears in the Device Manager without any question marks when you invoke fastboot oem get_identifier_token — seeing the question mark there means that the fastboot driver is not installed properly. – Sergey Vlasov May 26 '13 at 19:37

6 Answers 6


Run fastboot as root or with sudo.

Other OS: credits

share|improve this answer

Are you rebooting the device into the bootloader and entering fastboot USB on the bootloader menu?


adb reboot bootloader

Then, look for on-screen instructions to enter fastboot mode.

share|improve this answer
up vote 3 down vote accepted

Problem solved. At the end I saw that drivers for android were not installed. I installed drivers from this site and device is visible by fastboot. One thing I don't understand is why adb saw device and fastboot not.

share|improve this answer
This is because the phone presents different device identifiers to the computer in these modes, and different drivers are needed, so it is possible to have proper drivers installed for one mode, but not the other. The fastboot program is simple and will just show the < waiting for device > message forever if drivers are missing. However, the same message may appear if the drivers are installed correctly, but the phone is not in the proper state with fastboot device IDs. – Sergey Vlasov May 26 '13 at 19:59

ADB and fastboot require different USB drivers.

Whilst you may see your device under adb when your phone is on it will not be detected by fastboot until you install the driver for it and hence will show "waiting for device".

You can follow the steps below to do so:

  1. Open your device manager and reboot your device into fast boot by pressing volume up, down and power button simultaneously
  2. You will notice that device manager refreshes and now your phone has a yellow icon
  3. Download the Google USB driver, it is a zip file so go ahead and unzip it in your local directory
  4. Right click on the yellow triangle for your device and update driver, select the option update from local storage and select the folder "usb_driver" under extracted files in previous step
  5. You are good to go now, fastboot oem unlock will detect the device now
share|improve this answer

try reinstalling fastboot driver

while in fastboot

  1. open device manager
  2. expand android
  3. there should be one device
  4. right click
  5. uninstall
  6. uncheck "delete driver software"
  7. click on pc with magnifying glass (in toolbar)
  8. if not fixed, repeat, but check delete driver (you may need to download it)
share|improve this answer

I didn't realize it right away, but there are different ADB drivers and Fastboot drivers. I had installed the google usb drivers with the SDK extras and ADB worked great but I got the "waiting for device" trying to flash in fastboot mode.

I went to device manager from the control panel and saw the "Android 1.0" device with the yellow icon showing it wasn't working right. I had to update the driver and pick from the list of existing drivers which had a fastboot entry.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.