Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,738,971 Members 44,268 Now Online
XDA Developers Android and Mobile Development Forum

Nexus 7 2013 ADB sideload device not found solved for stock nexus 7 in simple fashion

Tip us?
 
Sunburn74
Old
#1  
Junior Member - OP
Thanks Meter 17
Posts: 14
Join Date: Jul 2012
Default Nexus 7 2013 ADB sideload device not found solved for stock nexus 7 in simple fashion

Hi. Was trying to update my nexus 7 2013 to kitkat early and get running into the ADB sideload device not found. I finally solved the issue and wish to post here as it really was very difficult and there was a lot of false information floating around on the internet. I realize there are posts on this website regarding this but again its very fragmented and fraught with false information. This is designed for the layman for rapid updating of his stock nexus 7 2013 without issue.

Essentially to get the 4.4. OTA installed on your nexus 7, you need

1) android SDK installed with google drivers and USB debugging turned on (to get usb debugging you have to press the model number like 7 times I believe in under tablet to bring up developer mode and from there you can select it)
2) the Kitkat OTA downloaded
3) google ADB sideload drivers installed. Without these, whenever you switch into recovery mode you will always get the adb device not found error when you try to run commands from windows

So here's what you need to do for us non technical people (total time of work about 6 mins)
To install android SDK, just download the large zip file from android SDK, extract the file, and run the file labeled SDK manager. It should auto install the SDK and the google USB driver.

Then download the kitkat ota and rename it kitkat (it should auto designate itself as kitkat.zip). Place it in the platform tools folder of your extracted SDK install collection wherever that is.

Connect your tablet in USB debugging mode to your PC (to unlock usb debugging mode, tap on the build number >7 times in about tablet and you should get the option for developer mode. The USB debugging option is there). Then, navigate in windows to your platform tools folder, and press shift+left click and select open a command prompt here. then type: adb reboot bootloader

If that works that means you device was recognized in windows which it should as you have the default google usb drivers installed. The device should reboot to the bootloader and highlight recovery with the tablets volume buttons and the power to actually select the choice.

Now, in recovery you should see an android man with a red exclamation mark. Also if you have your sound on windows should give you a sound indication of a device being disconnected and reconnected around this time. Press and hold the power button and quickly tap the up volume button and it should pull up a menu where you can select apply update from ADB.

Now open windows device manager and look for an unrecognized device nexus 7; I believe it should be under portable devices. Then select update driver and select browse my computer, let me pick a list of device, and then have disk. Go to the extras folder in the extracted SDK folder collection. Then selectgoogle -> usb drivers and select android win usb. Then of the three options you have pick the one that says android bootloader interface. Finish the driver install and you should now be able to put in the much wanted command.

adb sidload kitkat.zip

Note, this method is simple and doesn't require any driver editing which was part of all the false information floating about.

The website below goes through the steps for galaxy phone, but its similar overall.

http://www.teamandroid.com/2012/07/3...h-android-sdk/
The Following 16 Users Say Thank You to Sunburn74 For This Useful Post: [ Click to Expand ]
 
jgauthier
Old
#2  
Junior Member
Thanks Meter 0
Posts: 2
Join Date: Feb 2013
Default Genius.

You're a genius. This is the only solution that worked. Everything else wouldn't work. I couldn't get the device to be recognized once I selected Install update from adb. Thank you!
 
JahanUddin
Old
#3  
Junior Member
Thanks Meter 0
Posts: 1
Join Date: Nov 2013
Thank you so much, honestly.. the best post on XDA to explain the process..

Searched all over the internet non of there "fixes" worked. This did!!

 
J3FFTXD
Old
#4  
Junior Member
Thanks Meter 2
Posts: 8
Join Date: Aug 2012
Quote:
Originally Posted by Sunburn74 View Post
Go to the extras folder in the extracted SDK folder collection. Then selectgoogle -> usb drivers and select android win usb.
Ok, this is where you lost me. Under google/usb_drivers it only shows me the amd64 and i386 folders. Am I doing something wrong?

---------- Post added at 06:25 PM ---------- Previous post was at 06:19 PM ----------

Quote:
Originally Posted by J3FFTXD View Post
Ok, this is where you lost me. Under google/usb_drivers it only shows me the amd64 and i386 folders. Am I doing something wrong?
I just figured it out. I wasn't paying close enough attention to the part just before that. My bad.
 
arkson82
Old
#5  
Junior Member
Thanks Meter 0
Posts: 3
Join Date: Nov 2013
Location: Auckland
Thumbs up This worked!

Thanks mate, that worked wonders...delicious KitKat updated! Yippee!
 
digitalexplr
Old
#6  
Member
Thanks Meter 1
Posts: 36
Join Date: Aug 2011
This should be a sticky! 😂

Sent from my Nexus 7 using Tapatalk 4
 
joweedeame
Old
#7  
Junior Member
Thanks Meter 1
Posts: 8
Join Date: May 2009
I love you!
 
naveenvalaja
Old
#8  
Junior Member
Thanks Meter 0
Posts: 18
Join Date: Dec 2012
Default Help

Quote:
Originally Posted by Sunburn74 View Post

Now open windows device manager and look for an unrecognized device nexus 7; I believe it should be under portable devices. Then select update driver and select browse my computer, let me pick a list of device, and then have disk. Go to the extras folder in the extracted SDK folder collection. Then selectgoogle -> usb drivers and select android win usb. Then of the three options you have pick the one that says android bootloader interface. Finish the driver install and you should now be able to put in the much wanted command.



http://www.teamandroid.com/2012/07/3...h-android-sdk/
Under usb_driver folder I am able to see amd64 and i386 folders only...I am not able to select android win usb file. Its showing only folders list.
Please help.

---------- Post added at 01:04 AM ---------- Previous post was at 12:59 AM ----------

http://blog.dantup.com/2012/10/fixin...recovery-mode/

This one helped...

Thanks

---------- Post added at 01:08 AM ---------- Previous post was at 01:04 AM ----------

http://blog.dantup.com/2012/10/fixin...recovery-mode/

This one helped...

Thanks
 
Sunburn74
Old
#9  
Junior Member - OP
Thanks Meter 17
Posts: 14
Join Date: Jul 2012
Quote:
Originally Posted by naveenvalaja View Post
Under usb_driver folder I am able to see amd64 and i386 folders only...I am not able to select android win usb file. Its showing only folders list.
Please help.

---------- Post added at 01:04 AM ---------- Previous post was at 12:59 AM ----------

http://blog.dantup.com/2012/10/fixin...recovery-mode/

This one helped...

Thanks

---------- Post added at 01:08 AM ---------- Previous post was at 01:04 AM ----------

http://blog.dantup.com/2012/10/fixin...recovery-mode/

This one helped...

Thanks
You have to specifically pick browse my PC and let me choose a device. Then navigate to your android SDK folders and pick the driver .I spent hours reflexively doing what you were doing.
The Following User Says Thank You to Sunburn74 For This Useful Post: [ Click to Expand ]
 
groopk
Old
#10  
Junior Member
Thanks Meter 0
Posts: 4
Join Date: Jul 2012
Quote:
Originally Posted by Sunburn74 View Post
You have to specifically pick browse my PC and let me choose a device. Then navigate to your android SDK folders and pick the driver .I spent hours reflexively doing what you were doing.
Holy crap, I spent more time than I care to admit trying to figure out exactly what step I was missing that made me not have the usb_driver folder!! Thanks for spelling it out again, I definitely had the same reflexes lol.

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes