Why am I getting and error message ADB Device Not Found when attempting to Sideload my Android 5?

[Jim Panse]

It works! Finally i found this post! Thanks alot GuavamanX

 

[bljy]

this worked for me too in sideloading the marshmallow update onto my nexus 9. thanks a million!

 

[Xaiux]

This post helped me with my Nexus 7 2013 today with the Marshmallow update. Thanks so much!

 

[abhikush]

This post helped me with my Nexus 7 2013 today with the Marshmallow update. Thanks so much!

This post helped me with my Nexus 7 2013 today with the Marshmallow update. Thanks so much!

Are you using Windows 10? If so can you explain what you did? "adb devices" command does not show anything for me. I have reinstalled drivers multiple times. I have USB debugging turned on. I can also see the Nexus 7 folders in Windows.

 

[Laura Knotek]

Are you using Windows 10? If so can you explain what you did? "adb devices" command does not show anything for me. I have reinstalled drivers multiple times. I have USB debugging turned on. I can also see the Nexus 7 folders in Windows.

Did you change directory (using the cd command) in the Windows terminal? You'll need to open terminal as administrator (command prompt admin) and then use cd command.

 

[Piper5150]

I ran into this last night - I had to use an old 2014 version of the driver - for some reason it worked. I kept trying the various Android drivers that were already installed on my laptop (recently updated to Win10). I think it was the driver I installed previously when I sideloaded Loliflop - I'll try to take a look when I get home and report back exactly which driver it was that worked.

 

[aperture22]

I just got my N7 to update to Marshmallow on a Windows 10 machine with USB3.0 ports. I connected the device to the laptop using the cable; booted into recovery and selected "sideload via ADB". Then went to the device manager on my PC and found the new device with the yellow triangle. Selected to install the driver manually by choosing from the list. Selected "ADB device"; then chose "Google" from the manufacturer list and on the right pane chose ADB ver 8.0. Tried the ADB sideload command again and it worked! Running Android 6.0 on my N7 now

 

[augustokemp]

Re: ADB Device Not Found When Attempting to Sideload Android 5

Man, this really worked out for me! Thanks a lot!!

 

[mantangg]

After a lot of reading and driver updates, I have found the real reason for the problem.

It has nothing to do with the drivers, assuming that the drivers have been updated.

The problem is "ro-debuggable = 0" as seen in "adb shell getprop". Because of that, the device is not
visible once it is in reboot-recovery mode and therefore adb sideload does not work.

I didn't think Google is so dumb, because none of this is mentioned anywhere on developers.google.com/android/ota

In my case, all this trouble because the OTA Nougat update that Google has been pushing does not update. Tried
several times first, during install, phone is supposed to restart, well it does not and when I power it up manually, it is
still on 5.1.1 Marshmallow.

 

[GSDer]

The problem is "ro-debuggable = 0" as seen in "adb shell getprop". Because of that, the device is not
visible once it is in reboot-recovery mode and therefore adb sideload does not work.

Do you have USB debugging enabled in Settings -> Developer options?

In my case, all this trouble because the OTA Nougat update that Google has been pushing does not update. Tried several times first, during install, phone is supposed to restart, well it does not and when I power it up manually, it is still on 5.1.1 Marshmallow.

Apparently you do not have a Nexus 7 (2013)? That's the device forum you're posting in. Perhaps you could repost this in your device specific forum - you might get better assistance there.

 

[T-Dubs1217]

Hey, I just saw this post, and figured I'd chime in with my two cents
So, if you haven't already done so, please be sure to enable "Allow USB Debugging" under developer options. If it's greyed out, just unplug the USB cable from your PC, and then it'll become selectable again. This occurs if you have reboot/reset your phone using fastboot, and you have re-enabled developer options while still plugged into your PC. Hope this helps!

 

[HawkEye1969]

Updating the driver for the phone on my PC seemed to do the trick.

Thanks!