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

Run VMware/VirtualBox and Hyper-V on Same Machine


Sometimes, you have to use VMware or VirtualBox, but you have Hyper-V installed on your machine (usually to develop Windows Phone application). VMware or VirtualBox can’t run side-by-side with Hyper-V. They have different type of Hypervisor.

If you want to run VMware/VirtualBox and Hyper-V on same machine (but not side-by-side), you can set-up your hypervisor launch options in BCD. Simply, open Administrator’s Command Prompt (Run as administrator) and then:

Disable Hypervisor Launch Options: to run VMware or VirtualBox

C:\WINDOWS\system32>bcdedit /set hypervisorlaunchtype off
The operation completed successfully.

OR

Enable Hypervisor Launch Options: to run Hyper-V

C:\WINDOWS\system32>bcdedit /set hypervisorlaunchtype auto
The operation completed successfully.

Don’t forget to reboot your machine. And voilà: you can use Hypervisors that you want.