I wanted to sideload Android 5.1.1 (currently running 5.1) to my Nexus 5.
I've sideloaded before and it's really easy, but now I've ran into a weird problem I can't seem to fix. The Nexus 5 is completely stock.
I connected my phone with the USB cable it came with onto my desktop computer (Windows 8.1) with the USB driver (08/28/2014,11.0.0000.00000) installed and USB debugging is turned on.
adb devices showed me a device,
adb reboot recovery worked, but then Windows didn't want to find any USB device attached.
No sound, no nothing. It did not appear in the Device Manager (also not under the "Other devices" section)
Tried my laptop (running also Windows 8.1 with the same driver), but didn't want to recognise the device either. So, exact same problem.
After hours of searching the internet, I came across several potential solutions which I've tried but not succeeded with.
Koush's universal USB driver installer & Universal Naked Driver both did not work for me.
Then I tried following the steps in this article, which tells you to change the
INF file of the driver.
I've added various lines of code and installed it after disabling the driver signature check in Windows, but did not succeed.
The article tells you to add this line:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
But that did not work for me. After reading this in the article:
The ID I saw in device manager against the Nexus was USB\VID_18D1&PID_D001, which didn't turn a lot up in Google!
I found my ID in the Device Manager when the device was booted into Android, changed the last part of the line, but that did not work in the end either.
I've tried using another cable as well, though I don't think that's the issue. It's plugged in quite firm and the device is being recognised in Android and the bootloader immediately.
Who can help me out?
Edit: I just got the update through OTA, but I still would like to know why my computers act like the N5 isn't plugged at all when in Recovery mode.
Mountsand enabling/disabling MTP (enable if its disabled and disable if its enabled). Then try connecting again? This has worked a fair number of times for me.
.inffile: you can cross-check VID (vendor ID) and PID (product ID) using
lsusbwhen the device is connected to your Linux machine. Be aware the very same device might present different PIDs depending on boot mode (recovery/bootloader/normal).
lsusbon a linux machine. Thanks so far.
lsusband it showed the id and pid like it should in normal and bootloader mode, but once I go into the recovery, the machine acts like there is no USB input at all