ADB Nexus 7 Issue

[SuperIVIan11]

I have spent many many many hours working on this and I am completely out of options. I can not get the ADB commands to work once the device is in Recovery Mode. I am currently working with a 2013 Nexus 7. I have turned USB debugging on, I have updated the Google USB driver. I've tried uninstalling and reinstalling the drivers as well. I've tried the generic USB driver from Clockworks. I've tried different USB cables and different USB ports. I checked the device manager while the device is in recovery and the computer sees the device, but abd commands don't work.

When the device boots normally it shows up with its serial number when I run the 'adb devices'. It responds to 'adb reboot bootloader', but the moment I try 'adb sideload (filename).zip' it stops working and I get a device not found error. I run 'adb devices' and nothing shows up dispite the computer recognizing it.

I've done this many times, it just refuses to work for me now, and I'm going crazy. any advice?

 

[Laura Knotek]

What version of Windows are you running?

Have you tried a different PC?

Sent from my Moto X Pure Edition using Tapatalk

 

[SuperIVIan11]

Windows 7

 

[SuperIVIan11]

Yes, I've tried 2 different PCs

 

[Laura Knotek]

Have you tried removing all adb drivers from device manager, rebooting the PC and then re-installing?

Do you have the Nexus 7 set to stay awake in developer options?

Sent from my Moto X Pure Edition using Tapatalk

 

[SuperIVIan11]

Yes and No, but I just switched it on and tried with no luck.

 

[hub1]

Are you trying to flash the image or the OTA file?
http://www.androidcentral.com/how-manually-upgrade-your-nexus
I used this link to update mine and my wife's N7s. I was able to use the OTA zip file.

 

[Saeed Okoroji]

It could be your cable. Or you have to put the tablet on USB debugging and authorize the connection between your tablet and computer.

Sent from my D6503 using Tapatalk

 

[SuperIVIan11]

Yes, I'm using the OTA file posted on the AC site.

 

[SuperIVIan11]

I tried a couple different cables, and ports. with not luck. I went into the settings and turned off and back on USB debugging. I also re added the PC as a trusted device. It works while the device is on. I can see it in the cmd but once I'm in recovery it doesn't show up and I get the error.

 

[Batavian]

Have you tried nrt at wugfresh?

 

[EJT]

Ok, this is going to sound dumb, but after you go to the sideload page with the tiny yellow text in the lower left corner, unplug the device from the computer, give it a second, and then plug it back in. You should be able to send the ADB sideload command then. I had that problem with my N6, and it drove me nuts until I figured it out.

Posted via the Android Central App

 

[italian_rowsdower]

If you search for Danny Tuppeny's blog you'll find a post from October 2012 titled 'Fixing adb "Device not found" with Nexus 7/Android devices in Recovery Mode' (I can't post links since I just subscribed). Basically changing the device ID in the android_winusb.inf file should solve the problem. It worked for me last year for the Lollipop update but it's not working this time (I can't remember the ID I used).

 

[doxidad]

I had the same problem and did some searching. What I found was that the device was unknown after you went in to the bootloader. All you need to do is go into the device manager and check and you probably will have a exclamation mark next to the device. right mouse click on the device and select load a device driver from your PC. Explicitly Select Google and then Google ADB USB and load it. ADB will then find your device ID and let you sideload the OTA zip. Evidently the USB driver gets confused once you are in the bootloader. Hope this helps you a bit

 

[cab2]

I would boot it from a Linux PC, Linux android tools package is more reliable. If that doesn't work you have a hardware problem. Also note that some USB cables are charge-only, i.e. no signal leads.

 

[SuperIVIan11]

Ok, this is going to sound dumb, but after you go to the sideload page with the tiny yellow text in the lower left corner, unplug the device from the computer, give it a second, and then plug it back in. You should be able to send the ADB sideload command then. I had that problem with my N6, and it drove me nuts until I figured it out.

Posted via the Android Central App

That's not dumb at all. I tried that and it did not work for me. I remember doing that last year with my N4 going to lollipop, but it hasn't work this year.

 

[SuperIVIan11]

If you search for Danny Tuppeny's blog you'll find a post from October 2012 titled 'Fixing adb "Device not found" with Nexus 7/Android devices in Recovery Mode' (I can't post links since I just subscribed). Basically changing the device ID in the android_winusb.inf file should solve the problem. It worked for me last year for the Lollipop update but it's not working this time (I can't remember the ID I used).

His blog was one I visited in my research to no avail.

 

[SuperIVIan11]

Have you tried nrt at wugfresh?

Yes, I love the Rootkit, when I used it for my GNexus. I just don't want to wipe the device since I'm doing it for another person.

 

[SuperIVIan11]

I had the same problem and did some searching. What I found was that the device was unknown after you went in to the bootloader. All you need to do is go into the device manager and check and you probably will have a exclamation mark next to the device. right mouse click on the device and select load a device driver from your PC. Explicitly Select Google and then Google ADB USB and load it. ADB will then find your device ID and let you sideload the OTA zip. Evidently the USB driver gets confused once you are in the bootloader. Hope this helps you a bit

The device shows up normal in the device manager while in recovery. Just to be sure though I uninstalled it and reinstalled the driver( with the tablet in recovery) and it still didn't work.

BTW I like you pic. The one in my profile pic is my mini grey piebald doxie.

 

[SuperIVIan11]

I would boot it from a Linux PC, Linux android tools package is more reliable. If that doesn't work you have a hardware problem. Also note that some USB cables are charge-only, i.e. no signal leads.

I will go through and see if I can find a stock cable. I thought I had had it, but I was told no. If that doesn't work, I'm going to throw this PC out a windows and I will build a new one with Linux.