Fixing adb “Device not found” with Nexus 5 devices in Recovery Mode


Yesterday (June 20th, 2014), Google announced Android 4.4.4 update for some Nexus devices, including Nexus 5. But, when I tried to manual install the OTA update by entering the device to recovery mode and install from adb sideload, there was a problem. My Nexus 5 device did not detect while in adb sideload mode.

adb: device not found

I followed this instruction Fixing adb “Device not found” with Nexus 7/Android devices in Recovery Mode on my Windows 8.1 machine and gave me this error:

Driver Install Error

Install Error: The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.

If you have same problem with me, you can fix this error by following this step.

  1. Install original Google USB Driver.
  2. Open your Device Manager (Right click Windows Start logo > Device Manager).
  3. You will see Nexus 5 devices under Other devices group.
  4. Right click on Nexus 5, and then click Update Driver Software.
  5. Select Browse my computer for driver software.
  6. Click Let me pick from a list of device drivers on my computer.
  7. Choose Android Device and then Next.
  8. Choose Manufacture: Google and then model: Android Composite ADB Interface.
    SNAG-0219

  9. Windows will warn you about incompatibility driver. You can just click Yes to continue the process.
    SNAG-0220

Now, your Nexus 5 driver will be detected in recovery mode, so you can continue your Nexus 5 OTA update.

SNAG-0221

Advertisements

32 thoughts on “Fixing adb “Device not found” with Nexus 5 devices in Recovery Mode

      1. I got the same problem. I was able to download the USB driver ZIP file and then extract the contents but installing them must be done through some kind of sorcery…
        Are you supposed to install the drivers ONTO the phone and then install them again a different way?

        Like

  1. Will I receive future ota updates from Google on my nexus 5 if I manually install the lollipop ota.zip file now? Or should I manually update my phone every time from now on?

    Like

  2. Hello,
    Followed the guide no joy it seems as though when in recovery mode the driver stops working, when i look at the drivers in device manager when in recovery mode i have android bootloader interface and android composite adb interface both are greyed out, so when i do adb devices nothing is seen as connected when in normal normal mode i can issue adb commands. Any ideas?

    Cheers

    Like

  3. Update while in recovery mode i reinstalled the driver then killed adb server then restarted then it picked it up i have just transferred the update and it installed and I have not bricked my phone WOOT!!!! Thanks for the guide

    Like

  4. doesnt work for me. Im using N5 Lollipo rooted, TWRP.
    Once I reach fastboot mode. even though Android Device is listed in WINDOWS DEVICE MANAGER, in CMD it always says error: no device found. Or if I type adb devices. it shows nothing.

    Like

  5. Thank you very much, it works for me on my Nexus 5 but with some differences:
    I have installed Google USB drivers, and everything went right. But when I put my device in recovery mode my Nexus 5 was not recognized anymore (?!!) so I installed Google USB drivers again, following steps from 2 to 9 and finally I was able to use adb sideload.

    Like

  6. am having the same problem of “device not found error while installing the 5.0.2 lollipop version to my moto e(kitkat4.4.4). please help me to resolve the problem. I am totally exhausted by trying multiple times.

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s