Wednesday, February 27, 2013

Nexus S 4G Fastboot Waiting for Device

I have an older Nexus S 4G (D720) and needed to flash it to Gingerbread to use for some application testing. This should have been simple to do, but I ran into some issues. I worked out my issues and I thought I’d document them here so others could benefit.

When I followed the instructions from posts like:
whenever I attempted any of the “fastboot” commands, fastboot would respond with

<waiting for device>

and fastboot would hang. I found many posts and articles describing similar behavior, but all the workarounds seemed to include installing unsigned drivers from suspicious download sites or other steps that didn't seem to address the core problem.

Here is what I learned in my situation. For background

1. Install the Android SDK and Eclipse.
Eclipse probably isn’t necessary but it is nice to have.

2. Launch the Android SDK Manager.
From Eclipse go to Window->Android SDK Manager

From the command line execute “sdk manager” from the android SDK folder (if it isn’t already in your path).

3. In the Android SDK manager verify that the Google USB Driver is installed and up to date.
Install or update the driver using the SDK Manager if needed.

4. Connect the target phone to the PC using USB. Make sure USB Debugging is enabled on the phone.
On the Nexus S 4G running Gingerbread 2.3.7 this is under Settings->Applications->Development

5. From the command line, display all adb devices
Use the command:

adb devices

This command is in the Android SDK platform-tools folder. I have this added to my Path. ADB should list out all attached Android devices
If no devices are listed, make sure you have the Google Android USB driver installed.

Windows Device Manager should show a device of “Android Composite ADB Interface”. If this device is shown with an error, right click and select Update driver software. The instructions at should be helpful.

6. Use ADB to reboot the phone into Fastboot mode
Use the command:

adb reboot bootloader

This command is in the Android SDK platform-tools folder. I have this added to my Path. The phone should reboot into Fastboot mode.

7. Verify that fastboot can access the phone
Use the command:

fastboot devices

This should list out all attached Android devices in Fastboot mode. Notice that the device is no longer visible to ADB. “adb devices” no longer lists the device. However, “fastboot devices” should.

A device in Fastboot mode requires a different driver on your Windows machine. Without this driver the Fastboot command cannot communicate with the phone. If no devices are listed, make sure you have the Android Bootloader Interface driver installed.

8. Install the Android Bootloader Interface driver if needed
If Fastboot Devices lists the phone, this step is not necessary. If Fastboot does not list the phone or shows 

<waiting for device>

You may need to install the Android Bootloader Interface driver.
a. Run Windows Device Manager from Control Panel
b. Right click on the Android phone device that shows a warning and select Update Driver Software
c. Select “Browse my computer for driver software”
d. Select “Let me pick from a list of device drivers on my computer”
e. Select the correct Manufacturer and Model. For my phone this was Google and Android Bootloader Interface.
f. complete the driver update
g. If a reboot is needed, reboot your PC.

Now repeat the previous step to verify that fastboot can access the phone

9. Download and expand the device images to use.
For this phone, Google publishes the standard images at

Download the selected image from the link and expand the archive. I used WinRAR from

The expanded archive includes a number of image files and some command scripts to flash the device

10. Execute the commands from to flash the device.
Change to the folder with the expanded images and execute the fastboot commands from the file:

fastboot flash bootloader bootloader-crespo4g-d720sprke1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo4g-d720sprkh1.img
fastboot reboot-bootloader
fastboot -w update

Friday, January 2, 2009

From old to new

Well, the cut-over was fairly painless. Especially from the Blogger side. My pain was self inflicted because I had some custom URL redirect logic in the old site and when I tested it with its new domain it kept redirecting me back to the old URL. Once I remembered, I shut off that feature and all seems fine.

So, if anyone is looking for the old site, in its full DNN glory, it can be found at

Cutting over to blogger

In the summer of 2005, I started a bit of a personal adventure. I quit my job and with two friends started our own Internet business. Around that time, I started a blog with every intention of tracking the technical ups-and-downs of our efforts. Like 90% of blogging efforts, it soon petered out.

One of the challenges I created for myself was that I was managing my own blog site. I had been exploring the DotNetNuke (DNN) web framework, so I set up my own DNN site with a Blog module to explore DNN and to blog. That experimental site wasn't our core business site, so it became a bit of an administrative burden to maintain it.

Now I figure I'll let Google worry about the administrative burden while I try to attempt active blogging one more time.

Happy 2009