Hi. Was trying to update my nexus 7 2013 to kitkat early and kept 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 or piecemeal 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 three things to happen:
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) step by step
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 select google -> 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/30/how-to-set-up-adb-fastboot-with-android-sdk/
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!
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!!
:good::good:
Sunburn74 said:
Go to the extras folder in the extracted SDK folder collection. Then selectgoogle -> usb drivers and select android win usb.
Click to expand...
Click to collapse
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 ----------
J3FFTXD said:
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?
Click to expand...
Click to collapse
I just figured it out. I wasn't paying close enough attention to the part just before that. My bad.
This worked!
Thanks mate, that worked wonders...delicious KitKat updated! Yippee!
This should be a sticky! ?
Sent from my Nexus 7 using Tapatalk 4
I love you!
Help
Sunburn74 said:
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/30/how-to-set-up-adb-fastboot-with-android-sdk/
Click to expand...
Click to collapse
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/fixing-adb-device-not-found-with-nexus-7-in-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/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/
This one helped...
Thanks
naveenvalaja said:
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/fixing-adb-device-not-found-with-nexus-7-in-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/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/
This one helped...
Thanks
Click to expand...
Click to collapse
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.
Sunburn74 said:
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.
Click to expand...
Click to collapse
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.
Thanks Bro.. U helped a ton !!!
Cheers
Excellent
Sunburn74 said:
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, 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.
Click to expand...
Click to collapse
I wish this was reddit so i could give you gold. I spent the best part of two hours trying to side load the OTA lollipop update on my girlfriends Nexus 7 (2013). nothing worked. the I found your post and it worked immediately. THANK YOU!!
Sunburn74 said:
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/30/how-to-set-up-adb-fastboot-with-android-sdk/
Click to expand...
Click to collapse
I'm trying to sideload Lollipop and onto my N7 2012, and have run into this problem. The only problem I have is when I installed the -huge- sdk files per your instructions above, there is no google/usb drivers folder. Maybe it didn't install the driver?
My folder structure after installation is Extras\android\support\ etc etc.
Any ideas?
EDIT: I scrolled down in the SDK Manager and found that it hadn't installed the driver. All is good!
Works for Nexus 5
Thanks!! I looked all over for this solution and this also works for my Nexus 5 when updating to Android 5.0 Lollipop
Years later and this is still helping people...
Thanks again man haha.
dude thank you
the nexus 7 hates us, but thank you so much, android studios is how i did it and its all i could do to not pull my hair out after hours of google. i get 6.0 and its thanks to you good sir/mam.
Related
I am unable to get USB connection working with my phone for development purposes. I have turned on the USB debugging and connected the device with USB cable and it does detect file transfer capabilities, but I am unable to get the ADB connection working.
I am running Windows XP SP3
It says it has found a device 'Galaxy' but is unable to install drivers for it.
What I have tried:
sdk/extras/google/usb_driver directory
I tried installing PdaNetA302.exe
I tried installing Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe
I selected 'install from specific location' -> choose a driver -> 'Android Phone' but it had none listed and the aforementioned driver directories did not work either when I selected them as 'Have Disk' options.
I also tried uninstalling all related devices and do the whole connecting thing again, but without success.
Help please?
SOLUTION
Apparently HTC drivers got in the way. After I removed all HTC drivers from my Windows XP, restarted and connected the device, the Samsung drivers kicked in and made it work.
To remove unused drivers from Windows XP you can follow this guide.
Thanks for posting your experience.
Another problem I found, was that there's a different SamsungDriver.exe floating around, 8341kb. DOES NOT complete the ADB drivers necessary.
After installing the v1.4.6 drivers mentioned above, golden!
---------- Post added at 11:47 AM ---------- Previous post was at 11:41 AM ----------
Spoke too soon.
ADB recognizes it when it's booted in ICS, but while in the bootloader, it's not picked up. Thus fastboot commands won't work!
Windows 7 gives me a Android 1.0 driver not installed error.
Anyone?
PdaNet
waylo said:
Thanks for posting your experience.
Another problem I found, was that there's a different SamsungDriver.exe floating around, 8341kb. DOES NOT complete the ADB drivers necessary.
After installing the v1.4.6 drivers mentioned above, golden!
---------- Post added at 11:47 AM ---------- Previous post was at 11:41 AM ----------
Spoke too soon.
ADB recognizes it when it's booted in ICS, but while in the bootloader, it's not picked up. Thus fastboot commands won't work!
Windows 7 gives me a Android 1.0 driver not installed error.
Anyone?
Click to expand...
Click to collapse
I had no end of problems getting adb and fastboot working for GN due to the usb driver problems.
After much Google-ing...
I installed PdaNet on my laptop and this installed all required drivers in the process of installing, you can then un-install PdaNet and the required drivers are still on your system.
I now have adb and fastboot working for both my Nexus One and Galaxy Nexus phones on my Windows 7 x64 laptop.
Hope this helps!
Thanks to XDA member el3ctrik for this tip!
Thanks, figured it out just after you posted. The PDANet drivers were the trick, in #3 below (don't need to actually run the installation in this case).
You'd think after 1.5 years of playing/hacking/unhacking/fixing and refixing the N1 I'd know how this is supposed to work.
A couple of comments, since some tutorials are based on older installations.
1. Installing android sdk. I went through a crapload of unnecessary trouble in trying to reinstall these, thinking that the usb drivers, adb, and fastboot needed to be updated. NO.
1a. In fact, in trying to reinstall the android sdk, you have to install the Java SDK. THEN, with the latest revision, R15, FASTBOOT IS MISSING! Need to pull that from a r13 zip.
2. You need the CORRECT samsung drivers. The ones mentioned above are the correct ones. I installed some limited half-ass versions which did not do the job.
3. You need FASTBOOT drivers. These were found from this post http://forum.xda-developers.com/showpost.php?p=9919944&postcount=1
which states:
http://www.fileserve.com/file/5bgRBX5 (PDAnet x86 and x64 which are the fastboot drivers plus android sdk drivers)
The #2 drivers let ADB see it when ICS is running, #3 (and probably #2 too) are needed while in fastboot. To get #3 installed, I had to go to device manager in Win7, hit update driver (next to the error exclamation mark device), and direct to these files.
That is all <whew!>
Glad you got it sorted out buddy, I was in exact same boat, years of Nexus One fastboot and adb use, but still had problems!
I am really struggling to install ADB drivers (for using within ICS). The GNex is in developer debug mode. When I plug in, Device Manager shows the Portable Device, but no other devices are shown. So in this case, i have nothing to right-click to manually install the drivers. There is nothing under Android, or adb, or anything like that. Hope someone can advise...
I got it to appear by changing to PTP mode in the USB Computer COnnection on the phone!! Success.
Windows 7N USB driver issues
First post on this forum, so please bear with me.
I struggled for a few weeks trying to connect my new Samsung Galaxy Nexus (Rogers) to a 32-bit Windows 7 Ultimate N machine. The system wouldn't accept the drivers from Samsung - failed to recognize, driver software not successfully installed, etc. Tried all variety of proposed fixes, manually selecting the driver (have disk), downloading SDKs and ADB drivers.
Finally fixed it based on a very old suggestion from several years ago from an HTC user. The USB driver wasn't recognized in the absence of Windows Media Player being installed on the machine (a quirk of Ultimate N). Found the Patch from MS for WMP for 7 Ultimate N and the system immediately recognized and installed the Samsung driver and thus the Nexus is now connected.
Download my toolkit (ROM-Less), it will assist you in that manner!
It has easy instructions, and it will do most of the work itselff!
---------- Post added at 10:53 PM ---------- Previous post was at 10:49 PM ----------
AMoosa said:
I am really struggling to install ADB drivers (for using within ICS). The GNex is in developer debug mode. When I plug in, Device Manager shows the Portable Device, but no other devices are shown. So in this case, i have nothing to right-click to manually install the drivers. There is nothing under Android, or adb, or anything like that. Hope someone can advise...
I got it to appear by changing to PTP mode in the USB Computer COnnection on the phone!! Success.
Click to expand...
Click to collapse
Check this, it has all neccesary info/drivers for your device, including fastboot drivers!
Beatsleigher root helper (My toolkit) check it out
Hello!!
Well, hey guys. I thought I tell you the story, on why I posted this thread.
It started as I was installing Windows 8, on my laptop, and had the same problem, as some others. I just could not install the drivers, for my Droid, so I had a looksee and found that Windows 8 didn't yet have the capability, to download unsigned drivers, unlike Windows 7. So, I found a way of "tricking" Windows, into thinking, that these drivers are legit and it isn't forbidden to use, which is exactly what this tutorial tells Windows, in a way.
So, get going and use the full potential of your Android device!
Tutorial:
I have found a solution, to the following problem;
After installing Windows 8, you cannot install fastboot drivers, but it recognizes the ADB drivers...
Solution:
Open the dev-manager, by typing following, in a command prompt window, or the run dialog. Whichever you prefer... : devmgmt.msc
Now, the dive manager, should pop up.
Install ADB drivers, (If you do not have them present, download them here/
To prevent confusion: When I say install, it can mean unpack, or instal... Quick tip: An installer does nothing, apart from unpacking files, to allocated space, on your computer
Download USB drivers, from here. (Link fixed)
Should you NOT have drivers installed:
Install the USB drivers, and download ADB/fastboot drivers.
Installation of ADB/fastboot drivers:
Open the device manager, and look for "Samsung Mobile Device", or "Unidentified Device". You can make your search easier, by unplugging the phone, whilst in device manager, then plug it back in, and see what's changed...
Once you have found your phone, Perform a right-click, on the device. Select : "Update device drivers", once the dialog has poped up, choose "Browse my computer" and goto your dsktop, where you have installed the files to.
Open just the "drivers" folder, nothing else...
Select OK, then wait for installation to finish.
Once that has been done, you need to reboot your device, into bootloader mode; do this by typing
Code:
path=%userprofile%\Desktop\ADB\adb reboot-bootloader
adb reboot-bootloader
into the command prompt (download & install this, if you want to do it the cmd-way...)
Or, turn off your phone, and reboot i it manually into bootloader-mode, by pressing
Code:
VOL UP +DWM & PWR
together, untill phone vibrates...
Once the phone is in bootloader, go back to the device manager, and look for a device named "android 1.0". Perform a right-click on this and select "Update device drivers". Again, selct "Browse my computer", but, instead of clicking on "Browse" and selecting the folder, again, select "Let me pick, from a list of drivers." Once the menu has popped up, select "Samsung Android ADB interface". Click OK, and wait for the drivers to install . Then, you're done. You have then successfully installed the ADB + fastboot drivers correctly, to test this, open a cmd window, and type following:
Code:
path=%userprofile%\Desktop\ADB\
fastboot devices.
If your device shows up, then you have done it!!
Now type:
Code:
fastboot reboot
adb wait-for-device
adb kill-server
Note: while the phone is booting (If you typed "adb wait-for-device") A cursor will blink, wait for that, to stop blinking, then type the next command
I hope you learned, from this tutorial!! Check my root helper out, if you have enough time
Should you have problems, in recovery, open your dev. manager, and look for following device:
Code:
Full
Select, right-click. Update driver (blah, blah, witter, droan)
Browse my computer -> Let me pick -> Samsung ADB -> Done. You have enabled the ADB drivers, on your SAMUNG GALAXY NEXUS!"!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Addition: You can only reboot into bootloader, if you are using a motorola, Google or HTC branded Android device! This will NOT work with Samsung models (i.e. Galaxy S II/III) due to the fact, that they use Odin mode. Should the drivers need updating, for some devices, please let me know!
Motorola Razr
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Edit: In the ADB drivers link you posted, there's nothing to install. Just .sys files, .dlls, two .cat files, and some .infs. How exactly does one do anything with these files? Also, your second link for USB drivers was removed by mediafire.
thejakenixon said:
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Click to expand...
Click to collapse
Download MotoHelper. Right click the file and run in compatibility mode. It should install the drivers. I used this to run fastboot with my xoom.
It still hangs while running as admin under compatability mode for 7, I'll try as XP momentarily.
Edit: XP compatability didn't work either.
thejakenixon said:
It still hangs while running as admin under compatability mode for 7, I'll try as XP momentarily.
Edit: XP compatability didn't work either.
Click to expand...
Click to collapse
Bummer, I just remembered there was a setting to skip os version check in compatibility mode. Did you try that? If that won't work unfortunately I don't know what else to try. Sorry.
Sent from my Xoom using XDA Premium HD app
thejakenixon said:
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Edit: In the ADB drivers link you posted, there's nothing to install. Just .sys files, .dlls, two .cat files, and some .infs. How exactly does one do anything with these files? Also, your second link for USB drivers was removed by mediafire.
Click to expand...
Click to collapse
First of all, thanks, for letting me know about the link It's uploading again ^^
Yes, you can do the same for your Motorola. But only with the ADB drivers. Just do the same as with the Samsung. Select your device, form the devman. and right click. Update device drivers -> Browse -> Let me choose from a list... -> Samsnung ADB interface.
They are all provided by Google, inc. so, they are compatible, with every Android device. I've even used my Samsung ADB drivers, for a Sony Ericsson Xperia X8. So I can actually say, for myself, that they work. You then can work, using fastboot... ^^
Have fun fastbooting!
LG familyguy59/Beatsleigher
Well, I'm definitly glad, to see I'm actually helping some people, and they're appreciating it!!
I don't remember mentioning it, but if you Need help, PM me. I'll help you via Team Viewer ^^
will this work on Windows 8 Release Preview also ? are those compatible with x64 version of W8?
iconicpaul said:
will this work on Windows 8 Release Preview also ? are those compatible with x64 version of W8?
Click to expand...
Click to collapse
Yes, it works on both x86 and x64 bit architectures of Windows 8, works withRC and with pre-release...
Sent from my GT-I9300 using xda app-developers app
confirmed, it works, thank you...very fast and easy
thejakenixon said:
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Edit: In the ADB drivers link you posted, there's nothing to install. Just .sys files, .dlls, two .cat files, and some .infs. How exactly does one do anything with these files? Also, your second link for USB drivers was removed by mediafire.
Click to expand...
Click to collapse
To your edit. You have extracted the files. This is also called "installing" because you have extracted NEEDED files. Even when you extract a .zip/.rar/.tar/.tar.gz and so on, because you need files out of them, you are installing, but not to the system, but to yourself
Sorry for bringing up an old post, but this method is not working for me on Windows 8 Consumer Preview. When I'm trying to install the ADB drivers, it says the drivers cannot be installed because it's not digitally signed.
UPDATE: I got it to work by disabling the Digital Signature Enforcement on Windows 8. Steps: Restart Windows > Boot loader Menu > Other Options > Advance Options > *Computer Automatically Restarts* > Press F7 to Disable Digital Signature Enforcement
I cant get odin to work on win8 with my epic touch could this be my solution? Ive tried everything
Sent from my SPH-D710 using xda app-developers app
2phonejones said:
I cant get odin to work on win8 with my epic touch could this be my solution? Ive tried everything
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Yes, it should work with all Android-modification applications. I have never really had problems, with Odin, with any version of Windows, mainly because this is the first thing I do, on any of my Windows machines, but it is always worth a try Tell us, what you have found out!
If necessary, I'll try to find a solution myself
Sent from some GS III in some country, to a server somewhere in the US...
iconicpaul said:
confirmed, it works, thank you...very fast and easy
Click to expand...
Click to collapse
No worries, dude That's what I posted this thread for.
familyguy59 said:
Yes, it should work with all Android-modification applications. I have never really had problems, with Odin, with any version of Windows, mainly because this is the first thing I do, on any of my Windows machines, but it is always worth a try Tell us, what you have found out!
If necessary, I'll try to find a solution myself
Sent from some GS III in some country, to a server somewhere in the US...
Click to expand...
Click to collapse
thanks bro i didnt think anyone would repsond lol. Trying now, report back with results i want to flash so bad.:good:
Could someone pls. create a video tutorial, nad post this on Youtube, for me?
My laptop broke a couple of days ago, and my PC is only capable of running 98 - Vista, so, running on XP with 1GB of RAM.
I would appreciate this very much!
If you could do so and send me the link, via PM, I would be glad to pay 5€, via PayPal!
2phonejones said:
thanks bro i didnt think anyone would repsond lol. Trying now, report back with results i want to flash so bad.:good:
Click to expand...
Click to collapse
Ok, dude! Have fun!
Didn't work for me.
jorgefcbastos said:
Didn't work for me.
Click to expand...
Click to collapse
Did you follow the tutorial COMPLETELY, or did you leave stuff out? If you left something out, it's obviously not going to work
You may have to disable device driver signing, I've had quite a few people notify me about this.
But I'll sign the drivers, ASAP, so you won't have this problem
LG familyguy59/Beatsleigher
Edit: I forgot to mention, you need to tell me what exactly didn't work, otherwise I can't really help you
I wrote this guide for the Htc Evo3d-Cdma ver and started a thread there but I also wanted to start one here in case it might be helpful to anyone.
I take no responsibility if you screw up your phone. "IF YOU DON'T KNOW WHAT THIS GUIDE IS FOR OR HOW TO USE IT PLEASE DON'T".
How to install adb windows 8 Developers Preview
From what I've read a few members were having troubles installing adb on Windows 8 dev Preview-64bit
I have it installed and running and thought I'd share how I did it.
Ive linked a zip file containg the adb drivers,the java.exe,the android-sdk and the easytether.exe
I take no credit whatsoever for the htc/android driver I downloaded them from here
http://forum.xda-developers.com/showthread.php?t=1514942
Thanks to xda member "1wayjonny" please hit the thread up and give thanks to him for all his hard work.
There are alot of other methods to get adb installed on windows8 this is just how I did it.
Laie1472 link
http://db.tt/z5avjkJS
Here we go
Download the zip attatched to the link.
#1-Extract the "laie1472.zip" to your desktop or folder of choice.
#2-Extract the "universal zip" into the same folder.
Now install the jdk-6u22-windows-i586.exe if your running an intel i5 if not then download the correct java version from here-
http://www.oracle.com/technetwork/java/javase/downloads/index.html
and let it run that's all for the java.
Second extract the android-sdk_r07-windows.zip to your c:\ drive.
Meaning right click on the android sdk and choose extract.
A window will appear. In the address bar of that window is were the files will currently be extracted to. Please delete everything in the address bar except the c:\ Then click "ok" and close the window.
Then go to your start menu and click on it. From there go to computer and click on it. Then you will see an icon that says (c That's your hard drive were you extracted the android sdk. Click/Double click on this icon. From there you should see a folder named Android-sdk something something, Right click on this folder and rename it to "AndroidSDK" without the quotes.
Please rename the folder exactly as I wrote it capitol letters and all.
Next make sure that you have usb debuggin enabled on your phone. If you can't find this, "PLEASE STOP UNTIL YOU DO"
Now run the easytether.exe "free app included in the zip" file and when it opens up it will give you an option of Easy tether core or Android USB drivers. Please choose the Android USB drivers. But "STOP" and click the little arrow next to ANDROID USB DRIVERS. A menu will appear. When it does please choose ENTIRE FEATURE WILL BE INSTALLED ON C:\ DRIVE. Check that option as well. Click install and let it finish.
Now please REBOOT your Laptop/Desktop.
When your pc/laptop is up and running, plug your phone into your pc while powered on and choose "charge Mode only".
Then select the windows key on the keyboard
Then select "control Panel"
Then select "more settings"
Then select "device Manger"
Once your there look for the ""ADB DRIVER" or while in device manger unplug your phone from your pc and then plug it back in and choose "charge only" and watch for the device driver that shows up.
Then "right click" and choose "update driver"
Then select
"browse MY Computer for driver software"
Then select
"let me pick from a list of device drivers on my computer"
Then a window will appear.
Then select
"Next" from the top of the window.
Then select
"Have DISK"
Now when that window opens select "browse"
Then another window will appear.
Now at the top of the window you will see an "address bar" with a "down arrow next to it".
Select the "down arrow" and then a drop down list will appear.
From here browse to your desktop or where ever you extracted the laie1472.zip to and find the universal folder.
Then select the driver
"android_winusb.inf" and select "open".
Another window will appear and then select "OK"
Windows will prompt you to install the driver, also it will warn you that the driver is not signed but press install anyway.
When that is done close out all windows and unplug your phone.
Now restart your laptop/pc. You can do this by holding the window key and press the letter "R"
Now type "cmd" and press enter.
Now a command window will appear, in that window type this or copy and paste it
shutdown /s
Then press enter. Another window will appear saying that windows will shutdown in 60 seconds press ok.
Then type
exit
Then press enter and wait.
When your pc/laptop is back up and running plug your phone into your laptop/pc and choose charge only.
Then hold the window key and press the letter "R"
Now type "cmd" amd press enter.
When that command window appears. Type this command or copy and paste it.
cd\
then hit enter
Now type cd\AndroidSDK\tools\
Then hit enter
Now type
adb devices
You "should" see a bunch of numbers
Those numbers. Represent your phone.
Now type
adb shell
Then hit enter on your keyboard.
You should see the # sign. That means you have adb installed. To test it just type reboot recovery and it should reboot your phone into your current recovery. From there you got it.
I hope this helps anyone who was having a hard time getting adb to work on windows 8 Developers Preview64-bit. I have not tested this on the latest windows release or the 32bit verison but your welcome to and leave feedback if your successful to help the community.
This is For the HTC EVO 3d-CDMA, it may or may not work for the GSM version or the evo4g CDMA,GSM.
PLease take into mind that this guide may or may not work for you. Some will have no problems with this guide while others may or may not experince difficulties.
This Guide is in no way 100% guaranteed to work for all. Please refarin from posting negative feedback if it does'nt, how ever I would encourage postive feedback.
I will attempt to maintain this thread and help out any members who decide to use this guide.
Edit if you need help installing adb on ubuntu see my thread here
http://forum.xda-developers.com/showthread.php?t=794624
If you need help installing adb on windows 7-32,64bit,Vista-32,64bit or Xp-32,64bit see my thread here
http://forum.xda-developers.com/showthread.php?t=858118
Also the sdk I included is the older version, I haven't tried with the latest one. If you do please post if your successful to benefit the community. Also the path to the tools folder will change with the latest sdk, the command should be
c:\AndroidSDK\platform-tools\
This is not for development only for adb. You have to download the development platforms via adb tools.exe to do development.
Hope this helps.
Root-Hack_Mod*Always\
TL;DR: Install Universal Naked Driver instead of Google USB Driver from SDK or HTC Sync driver.
---------- Post added at 04:17 AM ---------- Previous post was at 03:39 AM ----------
Well this is just plain stupid. Just installed Android Composite ADB Driver on w8 and it works perfectly fine.
Huh ?? Man I have no idea what it is your referring to. Glad the guide worked for you.
#Root-Hack_Mod*Always\
when try to install the easy tether it says prematurely failed
Are you running the 32 bit ??? If so this is for the 64bit
#Root-Hack_Mod*Always\
Adiost said:
TL;DR: Install Universal Naked Driver instead of Google USB Driver from SDK or HTC Sync driver.
---------- Post added at 04:17 AM ---------- Previous post was at 03:39 AM ----------
Well this is just plain stupid. Just installed Android Composite ADB Driver on w8 and it works perfectly fine.
Click to expand...
Click to collapse
Don't understand what your getting at.
#Root-Hack_Mod*Always\
Trying something
Sent from my PC36100 using xda app-developers app
---------- Post added at 11:54 AM ---------- Previous post was at 11:41 AM ----------
[/COLOR]
Adiost said:
TL;DR: Install Universal Naked Driver instead of Google USB Driver from SDK or HTC Sync driver.
---------- Post added at 04:17 AM ---------- Previous post was at 03:39 AM ----------
Well this is just plain stupid. Just installed Android Composite ADB Driver on w8 and it works perfectly fine.
Click to expand...
Click to collapse
Could you share the steps of the installation and the download link of the Android Composite ADB Driver.
Thanks in advance :good:
Thanks for this guide!
Sent from an Apple killing JellyBean
DropBox link is dead. Can you please reupload those files? THX!
Yes will definitely reupload
Sent from my SCH-R530U using xda app-developers app
moparfreak426 said:
Thanks for this guide!
Sent from an Apple killing JellyBean
Click to expand...
Click to collapse
No problem glad it worked for you.
\Root-Hack_Mod*Always=LTE
Link fixed.
\Root-Hack_Mod*Always=LTE
laie1472 said:
Are you running the 32 bit ??? If so this is for the 64bit
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
I'm 64bit for sure and I got that same error, any suggestions?
When you try to run the easy tether??
#Root-Hack_Mod*Always\=LTE
I have my new Nexus 5X with Android 6 on it. I am trying to unlock and root.
I have enabled USB debugging and OEM unlock.
I have downloaded and installed the SDK package with Platform-Tools and drivers in the 'Extras' folder.
When first plugging in the phone I install the drivers with the 'Have Disk' and browse method.
Every time, installing the driver returns an Error 'Code 10 - device cannot start. 'Android ADB interface' shows up in device manager when I plug in the phone but with an exclamation point.
I have uninstalled, downloaded fresh drivers from other sources, reinstalled, tried plugging the phone in while in 'recovery' mode (starting by pressing all 3 hardware buttons).
I uninstall every time and reboot both the computer and the phone. The drivers simply won't work.
What is going on here? Is the phone/Android 6 still too new to unlock and root?
P.S. I should also say that I go into Developer options and change the Select USB Configuration between PTP and MTP (between which, I have not seen mention of the correct choice. Does it not matter?) - I cannot chose the others RNDIS, Audio Source, or MIDI; it seems to want to default to 'Charging' when I try to change to these choices.
Having the same issues on Windows 8.1. Can't get my 5x to connect to transfer files or to show up in adb.
Just need the right drivers. Download the driver files from here: https://www.dropbox.com/sh/e43knzpxvr9hzqi/AAC7Yiz8EShMpFiMkClPpkC5a?dl=0
1. Then with the phone plugged in and in PTP mode go into the device manager on your PC.
2. You'll probably have an Android device listed with an exclamation point showing. Right click on it.
3. Pick update driver.
4. Pick browse my computer for driver software.
5. Then pick "let me pick from a list of device drivers.
6. Then pick have disk.
7. Navigate to the folder you downloaded and select android_winusb
8. Let it install and you should be ok
bsinc1962 said:
Just need the right drivers. Download the driver files from here: https://www.dropbox.com/sh/e43knzpxvr9hzqi/AAC7Yiz8EShMpFiMkClPpkC5a?dl=0
1. Then with the phone plugged in and in PTP mode go into the device manager on your PC.
2. You'll probably have an Android device listed with an exclamation point showing. Right click on it.
3. Pick update driver.
4. Pick browse my computer for driver software.
5. Then pick "let me pick from a list of device drivers.
6. Then pick have disk.
7. Navigate to the folder you downloaded and select android_winusb
8. Let it install and you should be ok
Click to expand...
Click to collapse
I've got the same problems & the driver did not fix it. My computer won't use the android_winusb file gives me an error that it is not a 64 bit system fle. Same with te official google file.
ahunter said:
I've got the same problems & the driver did not fix it. My computer won't use the android_winusb file gives me an error that it is not a 64 bit system fle. Same with te official google file.
Click to expand...
Click to collapse
I was running into the same issue. The problem is you need to install them first as an ADB Interface Device (not composite) with the phone on and plugged in. From Device Manager choose the Google | Android ADB Interface (not the composite one. I saw another reference to making sure it's in PTP mode which may force it to this one as well but I didn't test). Then when you get into FastBoot mode on your phone and plug it in you can go through the same Update Driver steps and choose the "Android ADB Interface" for it as well when it shows the Nexus 5 with the yellow triangle. Then you should be good to go.
rgerrans said:
I was running into the same issue. The problem is you need to install them first as an ADB Interface Device (not composite) with the phone on and plugged in. From Device Manager choose the Google | Android ADB Interface (not the composite one. I saw another reference to making sure it's in PTP mode which may force it to this one as well but I didn't test). Then when you get into FastBoot mode on your phone and plug it in you can go through the same Update Driver steps and choose the "Android ADB Interface" for it as well when it shows the Nexus 5 with the yellow triangle. Then you should be good to go.
Click to expand...
Click to collapse
My phone shows up as a portable device/Nexus 5x . Are you saying it should be in Device Manager choose the Google | Android ADB Interface?
ahunter said:
My phone shows up as a portable device/Nexus 5x . Are you saying it should be in Device Manager choose the Google | Android ADB Interface?
Click to expand...
Click to collapse
Sorry. I should have been more specific. Part of it is I did so many different approaches they've bled together in my head and I was on my way out the door yesterday when I fired off the reply.
To try to break it down from memory (going to throw in a couple of different options since I can’t seem to fully uninstall / reinstall so please provide any corrections once you get it to work or let me know if anything doesn’t match what you find and I’ll try to remember from there):
Phase I (phone on and connected to computer):
Open Device Manager. My phone shows as Android Device | Android Composite ADB Interface or Android ADB Interface.
If it is the Composite version, I believe I had to update it to the straight “Android ADB Interface to get Phase II to work)
If you don’t see that, look to see if you have any uninstalled devices by scanning for new. If so, then right click on that device, and choose “Update Driver”
Choose “Browse my computer for driver software”
Choose the “Have disk” option and browse to your USB Driver folder
From there, choose “Google | Android ADB Interface”
Phase II (phone in recovery connected to computer)
On phone, choose “Update device from ADB”
Open Device Manager and you should see the Nexus 5 under Other Devices with the yellow triangle.
Right click on it and “Update Drivers”
Choose “Browse my computer for driver software”
Choose “Let me pick from a list….”
Choose “Android Device”
Choose “Android ADB Interface”
Now you should be able to push the update over
Simple method: What I did was plug it in and wait for it to show up in device manager. Then I deleted the device (the one that shows adb) from device manager. Then I unplugged the device and plugged it back in... Then waited for drivers to install on it's own. Everything was good after that.
I have no trouble other than on Windows 10. Windows 10 doesn't even show the drivers from a list to install.
Sent from my Nexus 5X using Tapatalk
I followed this to get my Nexus 5X detected on my Windows 10: http://stackoverflow.com/questions/...ould-we-use-for-the-nexus-5/19839812#19839812
I have no trouble with Fastboot or adb. It only happens when I try and sideload. I end up have to use my Macbook Pro to sideload.
Sent from my Nexus 5X using Tapatalk
bsinc1962 said:
Just need the right drivers. Download the driver files from here:
1. Then with the phone plugged in and in PTP mode go into the device manager on your PC.
2. You'll probably have an Android device listed with an exclamation point showing. Right click on it.
3. Pick update driver.
4. Pick browse my computer for driver software.
5. Then pick "let me pick from a list of device drivers.
6. Then pick have disk.
7. Navigate to the folder you downloaded and select android_winusb
8. Let it install and you should be ok
Click to expand...
Click to collapse
I wish it were that easy. But, no, this does not work. Nor do I believe my issue is the same as you others here, as I have Windows 7 and not the 8.1 and 10 issues that you are having.
No, no matter what driver I use, including any from your kind link, bsinc1962, they return an error, code 10 when trying just to install the drivers. I cannot go further.
What is this Code 10 error preventing drivers from installing?
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
I fought with this for ages today. To start with, I have the Wugfresh Nexus Root Toolkit installed. Now, when in bootloader, go to the device manager on your computer. Find the Pixel ("Unknown Device") and right click > Properties > Driver tab > Update Drivers > Browse Computer > Choose From List > WugFresh Development\Nexus Root Toolkit\data\Drivers > and pick the one that says something about the bootloader. Sorry, going off memory here. Now you should be able to get that one installed, and Fastboot will start showing up when in the bootloader.
Hakizi said:
I fought with this for ages today. To start with, I have the Wugfresh Nexus Root Toolkit installed. Now, when in bootloader, go to the device manager on your computer. Find the Pixel ("Unknown Device") and right click > Properties > Driver tab > Update Drivers > Browse Computer > Choose From List > WugFresh Development\Nexus Root Toolkit\data\Drivers > and pick the one that says something about the bootloader. Sorry, going off memory here. Now you should be able to get that one installed, and Fastboot will start showing up when in the bootloader.
Click to expand...
Click to collapse
I did the same : Choose from List >fastboot (I didn't install Wug)
jamgam said:
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
Click to expand...
Click to collapse
This is what worked for me....
http://forum.xda-developers.com/showpost.php?p=64777133&postcount=96
jamgam said:
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
Click to expand...
Click to collapse
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
@Istvan_86,
We should move the discussion for your problem here.
cam30era said:
@Istvan_86,
We should move the discussion for your problem here.
Click to expand...
Click to collapse
Hello,
I don't see any link and sorry if I made too many posts.
Istvan_86 said:
Hello,
I don't see any link and sorry if I made too many posts.
Click to expand...
Click to collapse
That's OK. No problem. Did you try the steps in post #5 above?
Which operating system are you on? What worked for me on Windows 10 was to give up after several days and use a Windows 7 computer. I read everything and tried everything and I could not get Fastboot working on this device with Windows 10. I used every toolkit, every driver version, toolkits that install multiple driver versions, Minimal ADB + Fastboot, and who knows what else. If a well-documented end-to-end solution to this ever appears I'll be really grateful.
FWIW, it was my frustrations with this Windows driver nonsense, that eventually drove me to abandon Windows entirely. Been on Ubuntu for several years. No regrets.
cam30era said:
That's OK. No problem. Did you try the steps in post #5 above?
Click to expand...
Click to collapse
Thanks for point me here, yo offer me too much help.
Now I´m on Nougat working flawlessly.
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
Really, really, really thanks. I have the exact same issue and this solved it for me also.
Cheers!
Istvan_86 said:
Thanks for point me here, yo offer me too much help.
Now I´m on Nougat working flawlessly.
Really, really, really thanks. I have the exact same issue and this solved it for me also.
Cheers!
Click to expand...
Click to collapse
Welcome.
cam30era said:
FWIW, it was my frustrations with this Windows driver nonsense, that eventually drove me to abandon Windows entirely. Been on Ubuntu for several years. No regrets.
Click to expand...
Click to collapse
It's very annoying, there seems to be a few reasons it fails. Cable, 3.0 usb ports, windows 10 drivers. I get different results with different cables in different types of usb ports. Also switching to PTP seems to work using a usb 2.0 port with a standard usb 2.0 A to micro with a micro to c adapter. Charging and MTP fail, but at least ADB and Fastboot respond.
I am going to try to edit the win10 driver using this post as reference.
http://stackoverflow.com/questions/34775508/where-is-the-windows-adb-driver-for-the-pixel-c
---------- Post added at 11:05 PM ---------- Previous post was at 11:04 PM ----------
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
I came to the same conclusion, but after a reboot it was unrecognized again.
Only way I can it to stick is installing the 2nd option drivers via skipsoft toolkit. Connect pixel c via 2.0 port and cable to PC. Switch to ptp. Then manually force install driver choosing have disk using bootloader option. From then on it works using ptp.
What I am able to see using USB Device Tree Viewer, is that when I plug in my Pixel C to my ASUS Z97-A blue usb ports with USB debugging enabled, it can not identify it. Those ports use Microsoft Windows 10 drivers for the Intel USB 3.0 eXensible Host Controller - 1.0. Which is what is causing the failure, not the Pixel C drivers. When I updated my other green USB ports driver, windows used the same ones on my ASMedia USB 3.1 eXtensible Host Controller and also couldn't recognize the Pixel C any longer. I rolled back to ASMedia drivers, it worked fine. Updated using newer ASMedia drivers 4/11/2016 ver 1.16.35.1 and those work fine. Now to find working drivers for the Inter Host. Win7 drivers refuse to load.
UPDATE: If your bios allows, disable xHCI. Your USB ports will work as USB 2.0 but will detect your PIXEL C without issues.
Solution works 100%
If you've installed the SDK drivers and win10 can detect your Pixel C in every mode with usb debugging off. Use these win10 USB xHCi drivers,
http://www.win-raid.com/t834f25-USB-Drivers-original-and-modded.html
@clockcycle,
This solution works 100% too. https://www.ubuntu.com/
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
Been smashing my face off the wall since LAST NIGHT trying to figure this out. windows 7 machine/ windows 8/ ubuntu ! trying 100 different methods and this one FINALLY SOLVED THE ISSUE. gawd dayum thank you so much from the future !!!