Related
Where can I find the latest usb drivers for this phone?
My phone isn't listed when I do the adb devices cmd. I assume it's because I'm missing the drivers. I got the usb_driver.zip from the xda wiki for this phone, but there is no installation, just a bunch of random files...and inf and a bunch of dlls.
So if you know, please tell me and don't tell me to use the search function as I've already tried that and Google.
if you have the usb_driver.zip, just unzip it
plug it your device, and open device manager
try to look for device with a ! next to it
the name should be something "ADB" or something similar
right click and choose update driver
you should have the option to select the folder that you unzipped at the begining
fsrkewd said:
if you have the usb_driver.zip, just unzip it
plug it your device, and open device manager
try to look for device with a ! next to it
the name should be something "ADB" or something similar
right click and choose update driver
you should have the option to select the folder that you unzipped at the begining
Click to expand...
Click to collapse
Thanks!! Got it
The best place to get the drivers IMHO is via installing the free HTC Sync software from HTC's website. See the "adb for noobs" guide in the dev forum.
Sent from my HTC Desire Z
Install Linux. :3
blackknightavalon said:
Install Linux. :3
Click to expand...
Click to collapse
I tried setting up ADB on my Ubuntu 10.04 box at work, and still have not been able to get it working for some reason. Is here a good guide that goes into detail about it? I believe I saw one here at XDA, and even after performing all the detailed steps I still couldn't get it to work.
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
So after going through this headache of not being able to fastboot either of my Nexus devices (GNex and N7) I have found the solution to my problems and I am sharing it with you guys.
Windows 8 forces drivers to be digitally signed and checks that signature with it's known driver signatures at home. This is a problem if you are trying to install and use something like fastboot/adb which Redmond may not have drivers for.
I was personally trying to install this as I did before on Windows 7: http://forum.xda-developers.com/showthread.php?t=1379875 and in order to install this we need to "Disable driver signature enforcement"
Steps to be taken:
1.) Bring up Charms by mousing over to the right of the screen
2.) Go to Settings
3.) Change PC Settings
4.) General
5.) Scroll down to Advanced Startup > Restart Now
6.) Trouble shoot
7.) Advanced options
8.) Windows startup options
9.) Restart
10.) Choose F7 (I believe) or click on "Disable driver signature enforcement"
11.) Reboot
Install the relevant driver (In my case Universal driver) under Device Management
This allowed me to install the Universal driver for both my Nexus devices. Anyway, hope it helps ya'll.
(Mods if posted before feel free to delete/merge/whatever.)
Or avoid all that by installing drivers from here:
http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW#
Then you can install the N7 ones as well.
http://support.asus.com/Download.aspx?SLanguage=en&m=Nexus+7&p=28&s=2
That way you don't have to deal with a Test Mode watermark and have the latest drivers.
Already posted in the "101" sticky over a week ago.
efrant said:
Already posted in the "101" sticky over a week ago.
Click to expand...
Click to collapse
efrant, if you use the official drivers and not ones that someone patched together, there is no need for that step.
adrynalyne said:
efrant, if you use the official drivers and not ones that someone patched together, there is no need for that step.
Click to expand...
Click to collapse
Yup, if you use the Verizon_Wireless_I515_Galaxy_Nexus_USB_Driver_v1.4.6.0.exe from Samsung's website, I believe it is signed, so it probably would work.
The issue was that some users (myself included), had problems installing the driver using Samsung's .exe package. 1wayjonny's repack worked flawlessly, and doesn't install anything else...
I am able to isntall just fine BUT i cannot get the drivers to work and its ****ing iritating. I just get something like This unit cannot start (error 10), A request for the USB device descriptor failed.
Nburnes said:
So after going through this headache of not being able to fastboot either of my Nexus devices (GNex and N7) I have found the solution to my problems and I am sharing it with you guys.
Windows 8 forces drivers to be digitally signed and checks that signature with it's known driver signatures at home. This is a problem if you are trying to install and use something like fastboot/adb which Redmond may not have drivers for.
I was personally trying to install this as I did before on Windows 7: http://forum.xda-developers.com/showthread.php?t=1379875 and in order to install this we need to "Disable driver signature enforcement"
Steps to be taken:
1.) Bring up Charms by mousing over to the right of the screen
2.) Go to Settings
3.) Change PC Settings
4.) General
5.) Scroll down to Advanced Startup > Restart Now
6.) Trouble shoot
7.) Advanced options
8.) Windows startup options
9.) Restart
10.) Choose F7 (I believe) or click on "Disable driver signature enforcement"
11.) Reboot
Install the relevant driver (In my case Universal driver) under Device Management
This allowed me to install the Universal driver for both my Nexus devices. Anyway, hope it helps ya'll.
(Mods if posted before feel free to delete/merge/whatever.)
Click to expand...
Click to collapse
Thanks,, Solved the problem...
thanks!!!
I tried this method and another method. I still can't get the drivers to work correctly. I installed the drivers and now when i connect my phone it is now coming up on device manager as "Andriod bootloader interface" I have a sony xperia S and after about 5 seconds it reboots. Any thoughts?
when i upgraded to windows 8, all i did was plug my phone in, go into device manager and find my phone and uninstall drivers since it wouldn't let me use fastboot even though it recognized my phone. i then installed pdanet and let it install the drivers and rebooted and it worked great.
t1.8matt said:
when i upgraded to windows 8, all i did was plug my phone in, go into device manager and find my phone and uninstall drivers since it wouldn't let me use fastboot even though it recognized my phone. i then installed pdanet and let it install the drivers and rebooted and it worked great.
Click to expand...
Click to collapse
I looked up pdanet and its a program to tether my phone. Why would that help with fastboot?
it installs the correct drivers needed to use fastboot for your phone. you can just uninstall the app when it's done, i kept it because sometimes i use the cable to tether my phone to my laptop.
---------- Post added at 02:47 PM ---------- Previous post was at 02:47 PM ----------
i'm just telling how i did it, it's up to you how you do it.
t1.8matt said:
when i upgraded to windows 8, all i did was plug my phone in, go into device manager and find my phone and uninstall drivers since it wouldn't let me use fastboot even though it recognized my phone. i then installed pdanet and let it install the drivers and rebooted and it worked great.
Click to expand...
Click to collapse
I did what you said it installed the drivers but when i connect my phone in fastboot its still doing the same thing, rebooting after 5 seconds. On device manager the phone comes up as "boot S1 download" I will try installing the fastboot drivers again and report back
did you uninstall any drivers for your phone first?
I'm having an absolute mare with Windows 8, fastboot drivers won't install (with the Samsung package or the naked drivers - just says 'no drivers found') and now the SDK won't install as it doesn't think I've got the Java SDK on my computer (which I have). This is a ballache!
Windows 7 was so much easier...
EDIT: SDK seems to be done following this:
http://forum.xda-developers.com/showthread.php?t=1758817
I did do it but think I set the path wrong so need to check it later on!
Nburnes said:
So after going through this headache of not being able to fastboot either of my Nexus devices (GNex and N7) I have found the solution to my problems and I am sharing it with you guys.
Windows 8 forces drivers to be digitally signed and checks that signature with it's known driver signatures at home. This is a problem if you are trying to install and use something like fastboot/adb which Redmond may not have drivers for.
I was personally trying to install this as I did before on Windows 7: http://forum.xda-developers.com/showthread.php?t=1379875 and in order to install this we need to "Disable driver signature enforcement"
Steps to be taken:
1.) Bring up Charms by mousing over to the right of the screen
2.) Go to Settings
3.) Change PC Settings
4.) General
5.) Scroll down to Advanced Startup > Restart Now
6.) Trouble shoot
7.) Advanced options
8.) Windows startup options
9.) Restart
10.) Choose F7 (I believe) or click on "Disable driver signature enforcement"
11.) Reboot
Install the relevant driver (In my case Universal driver) under Device Management
This allowed me to install the Universal driver for both my Nexus devices. Anyway, hope it helps ya'll.
(Mods if posted before feel free to delete/merge/whatever.)
Click to expand...
Click to collapse
You seriously saved the day. Awesome! Gave thanks!
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.
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 !!!