Database Info

fastboot binary for windows!

I've compiled a fastboot binary for windows from the git source, using cygwin.
I had actually compiled it a couple of weeks ago, but I never could get it to work. I was looking into it again tonight and discovered that windows had installed the USB Mass Storage driver for the phone in SPL mode, instead of the android driver. So after updating it to the android driver, it worked! woot
Instructions:
(note: you have to check the USB device in Computer Manager when the phone is in fastboot mode. The computer sees the phone in fastboot mode as a different device than the phone in normal mode)
Download the file and extract it in the same folder as adb. (if you don't have adb yet, it's included in the android SDK for windows. go download it!)
Take out the usb cable and boot up your phone into the SPL (back + power). You have to have the dev bootloader for this to work (white background with 3 skateboarding androids).
Plug in the usb cable, and make sure the display on the phone changes from "Serial0" to "FASTBOOT". If it doesn't, try pressing the back button.
If it asks you to install drivers, then go ahead and use the same usb drivers that you used to get adb working. You can skip the rest of the instructions. Fastboot should be working for you now.
If it doesn't ask you to install a driver, you need to figure out if the correct driver is loaded already.
Right click on My Computer, and click Manage, then go to the device manager
If you see an "ADB Interface" category at/near the top, with "HTC Dream" under it, then you're good to go. Fastboot should be working for you.
If you don't see an "ADB Interface" category, then it's likely that windows loaded the USB Mass Storage driver for it automatically. In the device manager, go down to "Universal Serial Bus Controllers", and see if you have at least one "USB Mass Storage device". If you have multiple ones, you'll need to go through each to find the correct one.
To find the correct one, right click on the USB Mass Storage device and click Properties. Go to the Details tab. In the combo box at the top that says "Device Instance Id", bring up the pull down and choose "Compatible Ids". If that is the correct device, then you will see 3 entries:
USB\Class_ff&SubClass_42&Prot_03
USB\Class_ff&SubClass_42
USB\Class_ff
Once you find the correct device, go to the driver tab, and click "Update Driver". Choose "No, not this time", then "Install from a list or specific location", then "Don't search, I will choose the driver to install", and then choose the same usb driver that you used to get adb to work.
After that's done, you should be good to go. Open a command prompt and type fastboot devices and it should list the phone.

This is a great Christmas Present lol !!!!! Thanks again JesusFreke !!!!!

JesusFreke said:
I've compiled a fastboot binary for windows from the git source, using cygwin.
Click to expand...
Click to collapse
Just four minutes shy of delivering on Christmas day too I kid, I kid. Great work. This will be quite nice for those of us still working primarily in Windows. b

Really Good!!!!!!!

Thanks JF, not for the files, I already had them compiled but because I found out why they weren't working...
USB MassStorage driver was as well on! LOL Its the simple things sometimes.

That's fantastic thanks JF. Now since we got fastboot in windows how does that change the process for having our custom boot image. I could not for the life of me get fastboot to recognize my device in ubuntu no matter what I did.

pablizzo said:
That's fantastic thanks JF. Now since we got fastboot in windows how does that change the process for having our custom boot image. I could not for the life of me get fastboot to recognize my device in ubuntu no matter what I did.
Click to expand...
Click to collapse
Let me take a shot in the dark and say that it would allow you to do the "fastboot flash splash1 image.rgb565" part from windows instead of ubuntu?
Don't forget about koush's .NET application to convert an image to the correct format: http://forum.xda-developers.com/showthread.php?t=462489

Thank you JesusFreke!
Way faster than booting Ubuntu under Sun's VirtualBox

Pardon my ignorance, but all that I can see with search about fastboot is it allows us to flash cupcake and new splash screens.
Can someone enlighten me as to what exactly this is? Does it simply bypass key signatures or error checks? Being that I don't turn my phone on and off a lot, a custom splash is really not necessary and being that cupcake is severely limited, don't want to even toy with that until it has more work in it.
Thanks in advance!!!

anyone try this on vista 64 yet?

Damn, someone needs to hire you or something. You've got talent!

Ha, thanks. But it's not like I wrote it or anything. The windows code is all there. I just figured out how to get it to compile in cygwin. (and figured out the driver thing, of course)

Valicore said:
Damn, someone needs to hire you or something. You've got talent!
Click to expand...
Click to collapse
JesusFreke and Stericson need to partner up and start a company for Android apps.

I think your givin me too much credit....JF could handle the app shop all by himself, he's just that good
Stericson

THANKs alot i didnt feel i installing ubuntu on my laptop. once again thankss

hi，can i use this tool flash the cupcake to my G1？the driver is good，fastboot is good work，but when i use the command that FLASHALL，its told the products specified and android-products-out must be setted。i dont know whats that means~

"Waiting for device" with Fastboot
Edit: Got it working, thanks.

I've had issues with fastboot depending on which USB cable I used (I have different kinds with different shielding)... I assume my "cheap" cables didn't have enough shielding and corruption happened when trying to communicate... also noticed that this happened as well while using a USB hub... I now have a good cable connected to the BACK port of my PC... I used the back port because front ports have extensions running from the motherboard through the inside of the case that were making interference as well... hope this helps!

what the heck is fastboot?
Sorry, JF. What exactly is this?

texasaggie1 said:
Sorry, JF. What exactly is this?
Click to expand...
Click to collapse
http://www.gotontheinter.net/content/fastboot-cheat-sheet

Found Answer To Windows XP 32 Bit Driver install Error

Hi Guys!!!
Recently I had A problem Installing Windows 32 bit Driver For Android So i searched On the web for this error & Found that there were many people with this error...
Here Is the info about that Error In My Last Post: http://forum.xda-developers.com/showthread.php?t=493604
WINDOWS XP x86 / 32-Bit Only
The error was so:
When we download the android_usb_windows.zip then extract it and then try to install it via device manager all goes right it detects the driver but at the last step where it asks for androidusb.sys file and when given the path it waits some time and says Fatal Error...
SO I tried To Go deep in the system32 folder There Go into Drivers Folder Now Here You begin some stuff:
1. Go in "C:\WINDOWS\system32\drivers" Folder there Find These files and cut them and paste in some folder where its safe:
androidusb.sys
usbccgp.sys
usbstor.sys
wdf01000.sys !!!! (Be Careful Deleting this File, I Say First try Without Deleting this file !)
2. Now Go to device manager "Right-click My Computer -> Manager -> Device Manager"
3. Click On ADB Interference Or something like that U ll Get a sub-category Right-click on it Click Uninstall -> OK
Do The Same For the Following :
USB Composite Device
USB Mass Storage Device
4. Get The Drivers From Here If U already Don't Have: http://dl.google.com/android/android-sdk-windows-1.0_r2.zip
OR
Get The Haykuro's Updated USB Drivers from here : http://sapphire-port-dream.googlecode.com/files/usb_driver_updated.zip
5. Now Try To Install The Driver Again By Going to "Right-click My Computer -> Manager -> Device Manager -> Action -> Scan for Hardware Changes" Then You will Get a pop-up saying Found New Hardware...
6. Install the drivers As Usual..... It Will install The Drivers Succesfully....
You Are Done.....

All I can say is THANK YOU.
THANK YOU THANK YOU THANK YOU.
This post deserves a sticky..
you are great

LOL
-- well after this I couldn't use FASTBOOT anymore hahahahaha
well, I worked around that, had to reinstall drivers for Haykuro's SPL too. So now both ADB and FASTBOOT work.

Thanks helped with my Win NT at work. lol

lol i have no idea if this was the cause... after this, I was no longer able to use my laptops keyboard, mice, video card drivers were corrupted along with network drivers, processor bus communications driver and a whole lot more. I had to perform a full system recovery so... yay.. lost everything, but im working on it.
---EDIT, I performed this on my fully recovered system again, and had the same results after it rebooted. I was able to conlude that it was caused by the system file with the wdf in it. Luckily, I hadn't deleted it and simply moved it into the recylcing bin and was able to recover from it. This may just be specific to my system, but I'm not sure. Just a warning to back everything up.

SolemnWishing said:
lol i have no idea if this was the cause... after this, I was no longer able to use my laptops keyboard, mice, video card drivers were corrupted along with network drivers, processor bus communications driver and a whole lot more. I had to perform a full system recovery so... yay.. lost everything, but im working on it.
---EDIT, I performed this on my fully recovered system again, and had the same results after it rebooted. I was able to conlude that it was caused by the system file with the wdf in it. Luckily, I hadn't deleted it and simply moved it into the recylcing bin and was able to recover from it. This may just be specific to my system, but I'm not sure. Just a warning to back everything up.
Click to expand...
Click to collapse
So Is that you are sayin is we do not need to remove the wdf file, did the drivers work without removing & again installing that wdf file?
or u did not put the new file again before rebooting ?

I am not really sure. It can possibly just be my computer. Once removing all the drivers you listed, the ADB then successfully worked, and continued to work as long as the computer was not rebooted. Once rebooted, I drivers for many pieces of hardware became corrupt and unreadable. By simply replacing the wdf driver and rebooting, it fixed the issue. So, I really am not sure. My computer... is strange. I believe it likely could just be my computer thats all.

next time if u get such problem just try solving without removing the wdf file & post what happens...
& plz post the consequences....thanks

The key points are:
To choose ADB interface\HTC Dream Composite ADB Interface to install
--DIYism

sangeet.003 said:
next time if u get such problem just try solving without removing the wdf file & post what happens...
& plz post the consequences....thanks
Click to expand...
Click to collapse
I will be performing another system recovery install soon, so I will post the results. My computer got screwed up again, so backing everything up now...

I still have a problem...
thanks for your tutorial.
I followed as you say, but I can't find my phone in cmd mode in my computer.
I succeed to install driver also it's shown in device manager as like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but something wrong in cmd mode as like this.
I'v tried whatever I can do..reinstall driver, adb, swipe my phone..
what shall I do now?

adb problem
Hi,
Same problem here, tried everything but CMD just is not showing any device...

I found the solution: make sure that debugging mode is checked in your G1 settings because if not ADB will not work.

pluplus said:
I found the solution: make sure that debugging mode is checked in your G1 settings because if not ADB will not work.
Click to expand...
Click to collapse
I followed this completely, I have the phone installed correctly now, not a mass storage device, device manager reads:
ADB Interface > HTC Dream Composite ADB Interface
However, I have usb debugging enabled, and still get the same *error: device not found*
Took a decent amount of time to get done right too, thanks to "trustedinstaller" being the only "user" that can delete drivers on my laptop..yay for changing ownerships! You'd think administrator would suffice, but nay.
Anywho..wtf am I missing here?
edit: win 7 x64, however the same rules for this how-to should still apply, as all the drivers and install options/processes are identical

ive found that trying to use the adb driver the driver gave me error code 10 (within the device manager)
ive got rc win7 64 bit
what i used to get rid of this problem is the program called USBdeview ( google for it)
and uninstalled everything related to htc/android
after connecting the phone the correct driver installed and i could use the adb device

I didn't want to make another topic on this, but I have a problem. Whenever I uninstall the drivers from device manager, then search for new devices, it installs the drivers automatically. I have mass storage and adb dream interface, but no devices are found when I execute the adb command. I cleaned out what I could from the system32 and /drivers folder. Any clues? Just to add, it did work about a week ago, didn't need to use it, now it doesn't work.
Edit: Oops, I forgot the check the uninstall driver box. I have the drivers, they install correctly, but I still can't use adb.
PS: vista x64, installing from the amd64 subfolder.

sangeet.003 said:
Hi Guys!!!
Recently I had A problem Installing Windows 32 bit Driver For Android So i searched On the web for this error & Found that there were many people with this error...
Here Is the info about that Error In My Last Post: http://forum.xda-developers.com/showthread.php?t=493604
The error was so:
When we download the android_usb_windows.zip then extract it and then try to install it via device manager all goes right it detects the driver but at the last step where it asks for androidusb.sys file and when given the path it waits some time and says Fatal Error...
SO I tried To Go deep in the system32 folder There Go into Drivers Folder Now Here You begin some stuff:
1. Go in "C:\WINDOWS\system32\drivers" Folder there Find These files and cut them and paste in some folder where its safe:
androidusb.sys
usbccgp.sys
usbstor.sys
wdf01000.sys
2. Now Go to device manager "Right-click My Computer -> Manager -> Device Manager"
3. Click On ADB Interference Or something like that U ll Get a sub-category Right-click on it Click Uninstall -> OK
Do The Same For the Following :
USB Composite Device
USB Mass Storage Device
4. Get The Drivers From Here If U already Don't Have: http://dl.google.com/android/android-sdk-windows-1.0_r2.zip
OR
Get The Haykuro's Updated USB Drivers from here : http://sapphire-port-dream.googlecode.com/files/usb_driver_updated.zip
5. Now Try To Install The Driver Again By Going to "Right-click My Computer -> Manager -> Device Manager -> Action -> Scan for Hardware Changes" Then You will Get a pop-up saying Found New Hardware...
6. Install the drivers As Usual..... It Will install The Drivers Succesfully....
You Are Done.....
Click to expand...
Click to collapse
nothing happeneds...
after doing that after reboot my laptop,i'm loosing harware keyboard and have some other problems too..
i just change the drivers again and reboot and all ok but there isn't any way to my laptop(toshiba xqosmio x300 with vista 32bit)read my hero in fastboot usb condition...
i tried it and in 2 pc's with xp (service pack 2) but the same again and there....
adb shell and adb devices aren't reade the phone in fastboot usb ....
in my cmd i'm taking allways the same error message when i try to load the cm-hero-recovery.img ""canot load cm-hero-recovery.img""
anybody who can help??

i have the windows usb drivers. and when i go into device manager on my 32bit vista machine, it shows "Android Phone" under portable devices. i click update drivers and select the usb drivers. problem is, it tries to install them, then i get a message saying like 'unable to install "da da what ever driver its called" then it just closes.
why wont this work help is appreciated

THANKS, i was keen to install linux

Thank you, Thank you, Thank you, Thank you, Thank you, Thank you, Thank you, Thank you, Thank you, Thank you.
You save my life. I've been having this problem for MONTHS!!! and no way im gonna restore my windows xp again. Thanks so much.

Diagnosing USB Driver and ADB issues in Windows

Are you getting errors like "device not found" or "device offline" while trying to run ADB commands? Here's a quick way to troubleshoot your problem on Windows.
Steps
1. Ensure USB Debugging is enabled in Developer Options.
2. Verify current Google USB Driver is installed and that Device Manager is using that driver.
3. Update to latest version of ADB.
1. Ensure USB Debugging is enabled in Developer Options.
Enable Developer Options by going to Settings -> About Phone and tapping on "Build Number" multiple repeated times. You will be greeted with "You are a developer."
Now, under Settings -> Developer Options, ensure you check the box for "USB debugging."
2. Verify current Google USB Driver is installed and Device Manager is using that driver.
You may skip this step if Device Manager lists your phone as "Android Phone -> Android Composite ADB Interface." If it does not, this is likely your root cause.
Go to the Google USB Driver page and download the latest driver directly from Google. Extract the zip file to a folder you know and will remember in the future.
Open up Device Manger in Windows with your Nexus 5 connected. Whatever your Nexus 5 is currently detected as, right click on it and select Properties. Then, in the Driver tab, hit "Uninstall." If available, select "Delete the driver software for this device." and hit "OK." It will remove the old drivers.
Restart your computer.
After restarting, reconnect your Nexus 5. It should be recognized as an unknown device in the Device Manager. (If it isn't, try the previous driver deletion steps again.)
Right click on the unknown Nexus 5 device, choose Properties, and in the Driver tab again select "Update driver." Browse your computer manually by putting in the path to the new Google USB Drivers you unzipped to a folder of your choice in the beginning of this step. Choose next and your drivers should install! You'll know everything completed successfully when you see the phone listed under "Android Phone -> Android Composite ADB Interface" in Device Manager.
This is the most finicky process, so don't be afraid to reboot your computer a time or two and repeat these steps if they don't work on the first try.
3. Update to latest version of ADB.
This is a crucial step. The new version of ADB is required to work with the "USB debugging authorizations" setting.
Perhaps you know how to update ADB, in which case, just do it. However, here's a detailed manual approach to download JUST the adb suite from the SDK:
Go to the Google Android SDK website and choose "Use An Existing IDE" and click the "Download the SDK Tools for Windows." This will allow you to download only an 80 MB file rather than the whole 400 MB suite.
Install the SDK tools exe to a folder of your choosing.
Run SDK Manager and uncheck everything except for "Android SDK Platform-tools." This is the ADB and Fastboot bundle. Install that.
Navigate to your SDK Path as indicated at the top of your Android SDK Manager window. You will now see a freshly downloaded platform-tools folder containing ADB.exe, Fastboot.exe, and a host of other files. That folder is now your updated, portable ADB tools folder. You can move it anywhere you like as long as you run ADB from a command prompt window set to that directory.
After you've followed these procedures, running "ADB Devices" should trigger a prompt on your device to accept the RSA fingerprint of your computer. Accept it, and now all should be working as intended!
Questions? Ask below!

Crowd-sourced solutions.
Windows 8 Diagnosis
Yorus said:
The following worked for me, since all of the suggestions mentioned here didn't work for me:
If you use a Windows 8.1 enterprise N or KN edition, install the Microsoft Media Feature Pack :
http://support.microsoft.com/kb/2929699/en
Sounds too simple to be true but work instantly for me.
Hope it works you some of the people here looking for a solution
Click to expand...
Click to collapse
Setting up ADB and Fastboot commands to work from ANY path (credit to original author in quote).
Chromium_ said:
Setup, Preparation and Prerequisites
ADB and Fastboot Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components here (Thanks @El Daddy)
Extract the zip and place the android-sdk-windows folder on the root of your hard drive. (the path should be like this: C:\android-sdk-windows)
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If not, repeat the step above.
Open a command prompt window and run "sysdm.cpl" (without the quotes) and a new window should popup. Go to the Advanced tab > Environmental Variables
Now focus your attention to the System variables box (the lower box). Scroll down and look for the Path variable > highlight it > click Edit > go all the way to the end of the Variable value text box, and paste the following entry:
Code:
;C:\android-sdk-windows\platform-tools
(OR WHATEVER PLATFORM-TOOLS DIRECTORY YOU PICKED)
Click OK then close all of the System Properties windows
You should now be able to use adb/fastboot commands no matter what location your command prompt is in. To confirm that it is indeed working, open a command prompt window and enter "adb version" (without the quotes). If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case.
Click to expand...
Click to collapse
The importance of being careful with your command choices.
MkVsTheWorld said:
"Be sure to use the CORRECT adb/fastboot commands, double-check the path on all commands, and double-check the existence of each file you are working with."
I hate to admit this, but I couldn't figure out why nothing was appearing in the device list when I did "adb devices", while the phone was in Fastboot. I did everything from A-Z and tore my hair out for 30 minutes until it hit me, my phone's in Fastboot. I've been messing with Android for 3+ years and made a newbie mistake lol.
Click to expand...
Click to collapse
Fixing MTP device not showing up after installing ADB drivers.
dbareis said:
I'm not sure what happened but on my WINDOWS 7 (64 bit) OS I had to modify "%WINDIR%\inf\wpdmtp.inf" as shown here: "http://forum.xda-developers.com/showpost.php?p=37930602&postcount=937". I then uninstall the device and drivers and performed a hardware scan to get it to work. I also added a "...PID_4EE2&MI_01" line but I am not positive that was required.
Hope that helps someone.
Click to expand...
Click to collapse
Whyzor said:
You should also mention what worked for me in post #16 (& confirmed by a few others in other threads). That is to toggle Settings - Storage - USB Connection type from Camera to Mass storage & also the debugging mode on & off.
Click to expand...
Click to collapse
Ashcunak said:
Op might wanna tack this onto the bottom of the main post as a last resort for folks to "start over" and be sure they have no old drivers installed.
http://www.nirsoft.net/utils/usb_devices_view.html
i had to use this program (right click run as admin if permissions are set) to remove EVERY single android related driver in order to get mine working.. turns out i had so many old ones in my system and some i couldn't remove from the device manager, the buttons wouldn't become click able..
Click to expand...
Click to collapse
CrazyIvan said:
I've tried everything and cannot get the authorization prompt to pop up on my Nexus5 so when I run adb devices the phone shows up as "unauthorized". Any suggestions? This is with updated sdk and USB drivers. Device manager shows phone as "Android Phone->Android Composite ADB Interface" and "Portable Device->Nexus 5". Tried toggling between MTP/PTP, USB Debugging on/off, stopping and starting the adb server (latest version 1.0.31).
Thanks in advance!
EDIT: Finally got the ba$tard! Run this for some adb debug logging:
adb kill-server
set ADB_TRACE=all
adb nodaemon server
Go and look back at the output from the start for any errors. In my case it couldn't mkdir in c:\users\administrator, which for me doesn't exist. I changed the Windows environment variable "ANDROID_SDK_HOME" to point to "C:\users\<my account dir>", closed the DOS window, re-ran the commands and I got prompted for the permission on my phone. Yee ha! Now I can fire up hello world with the SDK on my phone. Praise be to Google search for turning up this thread that told me about the debug logging.
Click to expand...
Click to collapse
SonicAngel said:
I just rooted my N5 (using the guide on this forum so I had no other drivers other than Google's SDK) and after unlocking my bootloader windows did not recognize my phone so I couldn't go further. Upon checking device manager I saw something called "AOSP on Hammerhead", a quick online search found a lot of very complicated answers (uninstall all drivers, restart, install adb drivers was one example).
Instead of all that I just right clicked "AOSP on Hammerhead", chose Update Driver, manually choose driver, went to "Android bootloader", chose the default driver from "Google inc" manually and that for some reason worked.
I figured this might help someone since the other solutions I found really were very long.
Click to expand...
Click to collapse
Questions? Ask below!

MaxRabbit said:
Reserved.
Questions? Ask below!
Click to expand...
Click to collapse
Hey man, thanks for the tutorial, I seem to still have trouble with this. Followed all the steps, even reset the device, to no avail. Anyone else having issues?

KTT16 said:
Hey man, thanks for the tutorial, I seem to still have trouble with this. Followed all the steps, even reset the device, to no avail. Anyone else having issues?
Click to expand...
Click to collapse
You're welcome! What shows up in your Device Manager now?

MaxRabbit said:
You're welcome! What shows up in your Device Manager now?
Click to expand...
Click to collapse
Hey thanks for the quick reply! I got it to work finally via: http://forum.xda-developers.com/showthread.php?t=2507905
Great tips and tutorial though..so stoked to have this phone!

KTT16 said:
Hey thanks for the quick reply! I got it to work finally via: http://forum.xda-developers.com/showthread.php?t=2507905
Great tips and tutorial though..so stoked to have this phone!
Click to expand...
Click to collapse
What step exactly did you take that fixed it?

MaxRabbit said:
What step exactly did you take that fixed it?
Click to expand...
Click to collapse
Open a command prompt window and run "sysdm.cpl" (without the quotes) and a new window should popup. Go to the Advanced tab > Environmental Variables
Now focus your attention to the System variables box (the lower box). Scroll down and look for the Path variable > highlight it > click Edit > go all the way to the end of the Variable value text box, and paste the following entry:
Code:
;C:\android-sdk-windows\platform-tools
Click OK then close all of the System Properties windows
You should now be able to use adb/fastboot commands no matter what location your command prompt is in. To confirm that it is indeed working, open a command prompt window and enter "adb version" (without the quotes). If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case.

KTT16 said:
Open a command prompt window and run "sysdm.cpl" (without the quotes) and a new window should popup. Go to the Advanced tab > Environmental Variables
Now focus your attention to the System variables box (the lower box). Scroll down and look for the Path variable > highlight it > click Edit > go all the way to the end of the Variable value text box, and paste the following entry:
Code:
;C:\android-sdk-windows\platform-tools
Click OK then close all of the System Properties windows
You should now be able to use adb/fastboot commands no matter what location your command prompt is in. To confirm that it is indeed working, open a command prompt window and enter "adb version" (without the quotes). If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case.
Click to expand...
Click to collapse
Ahh, your problem with my instructions then were that you weren't running ADB from inside the platform-tools folder

Definitely! I seriously got frustrated for a second and forgot how to read!
Sent from my Nexus 5 using XDA Premium 4 mobile app

Not showing up as removable storage
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!

JonnyRock said:
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
Click to expand...
Click to collapse
same issue on my side...I canot use MTP only PTP...I also tryed new drivers from SDK but has not solved the problem
Alex

JonnyRock said:
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
Click to expand...
Click to collapse
This is a really strange problem :-/ what does it show up as when you are in device manager on your work computer?

MaxRabbit said:
This is a really strange problem :-/ what does it show up as when you are in device manager on your work computer?
Click to expand...
Click to collapse
It shows up as a 'Portable Device' -> 'Portable Media Player' (I was thinking it was a 'Device with Removable Storage').
I have full access to the internal file folders here at work.

Here's a suggestion for something to add to the OP.
"Be sure to use the CORRECT adb/fastboot commands, double-check the path on all commands, and double-check the existence of each file you are working with."
I hate to admit this, but I couldn't figure out why nothing was appearing in the device list when I did "adb devices", while the phone was in Fastboot. I did everything from A-Z and tore my hair out for 30 minutes until it hit me, my phone's in Fastboot. I've been messing with Android for 3+ years and made a newbie mistake lol.
Sent from my Nexus 5 using Tapatalk

JonnyRock said:
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
Click to expand...
Click to collapse
I have the same problem and done the same exact things u did. any help?

I'm having no luck with unlocking bootloader of my Nexus 5 today. I've unlocked previous Android devices fine, but this one for some reason it's not detecting it in USB drivers. It shows as Other devices -> Nexus 5 in device manager, but when I select update driver & navigate to the dir where Android SDK/extras/google/usb_driver
Windows was unable to install your Nexus 5
Windows could not find driver software for your device.
I updated the OTA that came right away earlier, maybe this caused the Windows USB drivers to not work match the updated OTA build? Is there a way to ensure that old windows driver is uninstalled? I can only select 'uninstall', but not the 'remove old driver files' some docs mention. Also when I connect my Nexus 4 it's fine, and enabling debugging mode prompts for to allow the security fingerprint of the PC. But this prompt doesn't appear on Nexus 5, not sure if it's supposed to happen AFTER the PC is able to communicate with the N5 or not, which is the step that I'm stuck on. Tried it on another Windows 7 system and same problem.
UPDATE: Well my Nexus 4 worked fine along with adb until a few minutes ago, after toggling the Debugging Mode on the phone, it's not recognized on Windows now either. So definitely think it's a Windows 7 or Google USB Driver issue. Any pointers on how to start over (without reinstalling Windows) would be appreciated.
UPDATE 2: For future reference, I got around my Windows driver issue by going into Nexus - Settings - Storage - USB computer connection, toggle to Camera (PTP) and Media device (MTP), that reinitialized windows to recognize it in Device Manager again. Stupid Windows.

aluxzen said:
same issue on my side...I canot use MTP only PTP...I also tryed new drivers from SDK but has not solved the problem
Alex
Click to expand...
Click to collapse
I'm not sure what happened but on my WINDOWS 7 (64 bit) OS I had to modify "%WINDIR%\inf\wpdmtp.inf" as shown here: "http://forum.xda-developers.com/showpost.php?p=37930602&postcount=937". I then uninstall the device and drivers and performed a hardware scan to get it to work. I also added a "...PID_4EE2&MI_01" line but I am not positive that was required.
Hope that helps someone.

Whyzor said:
UPDATE 2: For future reference, I got around my Windows driver issue by going into Nexus - Settings - Storage - USB computer connection, toggle to Camera (PTP) and Media device (MTP), that reinitialized windows to recognize it in Device Manager again. Stupid Windows.
Click to expand...
Click to collapse
That... Thankyou for that info.
I was able to get ADB to work but was not able to get the device to popup as a storage device. That fixed it. Thanks!

I'm not sure what happened but on my WINDOWS 7 (64 bit) OS I had to modify "%WINDIR%\inf\wpdmtp.inf" as shown here: "http://forum.xda-developers.com/show...&postcount=937".
Click to expand...
Click to collapse
Thanks, that link was really helpful! I struggled with the correct detection before (seems I had some old drivers for my last phone on that windows installation...)

Whyzor said:
I'm having no luck with unlocking bootloader of my Nexus 5 today. I've unlocked previous Android devices fine, but this one for some reason it's not detecting it in USB drivers. It shows as Other devices -> Nexus 5 in device manager, but when I select update driver & navigate to the dir where Android SDK/extras/google/usb_driver
Windows was unable to install your Nexus 5
Windows could not find driver software for your device.
I updated the OTA that came right away earlier, maybe this caused the Windows USB drivers to not work match the updated OTA build? Is there a way to ensure that old windows driver is uninstalled? I can only select 'uninstall', but not the 'remove old driver files' some docs mention. Also when I connect my Nexus 4 it's fine, and enabling debugging mode prompts for to allow the security fingerprint of the PC. But this prompt doesn't appear on Nexus 5, not sure if it's supposed to happen AFTER the PC is able to communicate with the N5 or not, which is the step that I'm stuck on. Tried it on another Windows 7 system and same problem.
UPDATE: Well my Nexus 4 worked fine along with adb until a few minutes ago, after toggling the Debugging Mode on the phone, it's not recognized on Windows now either. So definitely think it's a Windows 7 or Google USB Driver issue. Any pointers on how to start over (without reinstalling Windows) would be appreciated.
UPDATE 2: For future reference, I got around my Windows driver issue by going into Nexus - Settings - Storage - USB computer connection, toggle to Camera (PTP) and Media device (MTP), that reinitialized windows to recognize it in Device Manager again. Stupid Windows.
Click to expand...
Click to collapse
Thank you for sharing your solution.

[GUIDE] Nexus Player - How to Unlock Bootloader and Root using USB cable

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Setup, Preparation and Prerequisites
Open command prompt - Press Window Key + R, type in "cmd" (without the quotes), and hit enter.
USB Debugging - On your nexus player go to Settings > About > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enter bootloader mode - Hold the button on the bottom of the device when you plug in the power cable, or enable developer options and "adb reboot bootloader"
Once you are in fastboot mode, the light below nexus player will be blinking constantly. You can verify by using "fastboot devices"
ADB Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components here
Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are done.
Show File Extensions - Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Backup (Optional) - Unlocking the bootloader will completely wipe all data from the device. This includes apps, settings and even the contents of the internal storage (pictures, music, etc.). Copy all important files off the nexus player onto a PC or upload them to a cloud.
Driver Installation
Go to Device Manager, find the Android device, and select Update Driver Software.
Select Browse my computer for driver software
Select Let me pick from a list of device drivers on my computer
Selecting show all devices
Clicking have disk
Finally selecting Desktop\android-sdk-windows\extras\google\usb_driver\android_winusb.inf as the driver
Alternative you can also download and install the Universal ADB Driver.
Downloads
Root:
Android 7.X:
- Coming Soon-
Android 6.X:
http://cord-cutters.wonderhowto.com/how-to/root-nexus-player-0160218/
http://androidflagship.com/16765-root-nexus-player-android-6-0-marshmallow
Android 5.X:
Download the SuperSU zip below. Extract the zip file and you will have (root.img) to platform-tools folder located on your desktop within the android-sdk-windows folder.
SuperSU (Forum Thread) or SuperSU (Direct link)
Information
Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 2 main steps: Unlocking the Bootloader and Rooting. Each new step relies on the previous step to have been completed, and a basic summary of each part is:
Unlocking Bootloader: Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the device in future.
Rooting: You can gain root booting up root.img
1. Unlocking Bootloader
Turn the nexus player off. Then go into bootloader mode by holding the button on the bottom of the device when you plug in the power cable, or enable developer options and "adb reboot bootloader"
Plug nexus player into your PC, then open a command prompt window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot devices
This command will list the connected devices. If your nexus player serial number shows up you are good to go and may continue. If the nexus player is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the nexus player has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
OEM unlock twice
Code:
fastboot oem unlock
Code:
fastboot oem unlock
After you have done, please proceed onto the next section of the guide.
2. Installing a Custom Recovery
http://forum.xda-developers.com/nex...recovery-twrp-2-8-6-0-touch-recovery-t3114717
https://twrp.me/devices/asusnexusplayer.html
3. Rooting
Now that your nexus player has an unlocked bootloader, now this step is to gain root
Android 7.X
- coming soon -
Android 6.X
Require: TWRP, Custom boot.img and flashable supersu
(Refer to above link)
Android 5.0
Warning: This rooting guide is for Android 5.X only!
Boot (not flash) the root image which will give you root with the stock ROM
Confirm that you have downloaded the SuperSU zip from the downloads section above and you have extracted it and it is located in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Make sure the nexus player is in bootloader mode
Open a command prompt window and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot boot root.img
This will install SuperSU on your device, once the command has completed continue.
Open SuperSU and update the binaries.
Keep in mind that the first boot may take longer than usual.
Congrats! Your nexus player now has an unlocked bootloader, and is rooted.
==================================================
How to flash factory image for Nexus Player?
1) Download image file for your nexus player - https://developers.google.com/android/nexus/images
2) Boot your Nexus device into fastboot mode.
3) On your computer, use 7zip to extract the .tgz file you downloaded from the Android Developer website. Use 7zip a second time to extract the .tar file you extracted from the .tgz. When you’re done, you should have a folder with several files in it.
4) Copy all of these files and paste them in the platform-tools folder in the Android SDK on your computer. If you followed the above tutorial, this should be under the C drive, then under Program Files (x86) on Windows. Linux users, you know where you put it.
5) If you have not already done so, connect your Nexus device to your computer. ADB and Fastboot commands should already work at this point if you’ve been following along.
There are two flash-all files. If you’re in Windows, you’ll want to double click the one that has the gear logo and says “Windows Batch File” on the right. If you’re on Linux, you’ll want to double click the flash-all.sh.
At this point a box should pop up and you should see the installation taking place. While this is going on, do not unplug your device for any reason. Let it do its thing.
6) Once the installation process as finished, your device will automatically reboot and you can now safely disconnect your device from your computer.
==================================================
Credits:
- Chainfire (SuperSU and Rooting guide)
- Chromium (Easy to understand and detailed guide format)
- DevinWatson (USB driver guide)
- androidauthority (Flash firmware image guide)

Nice guide.
What about installing BusyBox?

I have a USB OTG cable but the adapter is female on the available USB side...I am not sure how to go about connecting my laptop/PC to the NP in order to perform ADB commands. Do I need a special cable or is there another way?

arecad said:
I have a USB OTG cable but the adapter is female on the available USB side...I am not sure how to go about connecting my laptop/PC to the NP in order to perform ADB commands. Do I need a special cable or is there another way?
Click to expand...
Click to collapse
Don't use the USB OTG cable, use a micro USB cable (same kind of cable that comes with android phones)

I cannot believe I missed that, how embarrassing. Thanks for the response, now I can follow this guide. I was thinking too hard about the OTG cable being a necessary piece of the puzzle.

I am able to get to the bootloader with no problems, I've got ADB and Fastboot installed on my PC, as well as the drivers. However ADB doesn't pick up my NexusPlayer even though fastboot does. Thoughts?
See Attachments
EDIT: Nevermind, I was expecting different responses from adb/fastboot. When in the bootloader adb will not confirm a connection, only fastboot. Sorry for being a noob...

xDragonZ said:
1. Unlocking Bootloader
[*] Turn the nexus player off. Then go into bootloader mode by holding the button on the bottom of the device when you plug in the power cable, or enable developer options and "adb reboot bootloader"
[*] Plug nexus player into your PC, then open a command prompt window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
[COLOR="red"]adb devices[/COLOR]
This command will list the connected devices. If your nexus player serial number shows up you are good to go and may continue. If the nexus player is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under adb devices.
Click to expand...
Click to collapse
I could be mistaken, but when you're in the bootloader you're going to use FASTBOOT and not ADB commands. So therefore the command should be "fastboot devices" instead of "adb devices"?

midnightzak said:
I could be mistaken, but when you're in the bootloader you're going to use FASTBOOT and not ADB commands. So therefore the command should be "fastboot devices" instead of "adb devices"?
Click to expand...
Click to collapse
AFAIK ADB is for Android, and Fastboot is for bootloader.
But i have the oposite problem. Mine NP is getting recognized useing ADB when normaly booted, but when i am in fastboot mode, fastboot isent working. I get no output when run 'fastboot devivces'. I have both tried to set the NP in fastboot mode by using the hiod button and plug in power, and with adb rebbot bootloader.
Any one have a clue why adb works, but not fastboot?

Double check to see if you have the latest version of fastboot. I have read that if you don't have the most up to date version the NP is not recognized.

Sleeepy2 said:
Double check to see if you have the latest version of fastboot. I have read that if you don't have the most up to date version the NP is not recognized.
Click to expand...
Click to collapse
+1 this.

goxboxlive said:
AFAIK ADB is for Android, and Fastboot is for bootloader.
But i have the oposite problem. Mine NP is getting recognized useing ADB when normaly booted, but when i am in fastboot mode, fastboot isent working. I get no output when run 'fastboot devivces'. I have both tried to set the NP in fastboot mode by using the hiod button and plug in power, and with adb rebbot bootloader.
Any one have a clue why adb works, but not fastboot?
Click to expand...
Click to collapse
Have you re-installed the Google driver when you are booted in the bootloader? The driver needs to install twice: once when booted into Android, and once when booted into the bootloader

ADB fastboot for Mac Quick Question??
Hey guys does anyone have any idea on how this can be done on a Mac....I know I know. When I initially plug in my Nexus player with the micro usb, nothing happens on my mac or the Nexus so i am guessing that the drivers are not installed. How would i go about getting these for the Mac? I have already downloaded the slim version of the ADB and Fastboot files with the platform tools into a folder on my desktop named Andriod, so i have these already. And i know that if you hold the button down on the nexus and plug the power in it brings up the bootloader screen. I just need help with the commands in terminal and where to access the drivers from. Also, on the Nexus the Developer options have already been enabled and USB debugging has been turned on. If anyone can help, It would be much appricated! Just started to use terminal commands so yes i am a noob in this department . Thanks agin in advance.
-Jason

MrBoostinduced said:
Hey guys does anyone have any idea on how this can be done on a Mac....I know I know. When I initially plug in my Nexus player with the micro usb, nothing happens on my mac or the Nexus so i am guessing that the drivers are not installed. How would i go about getting these for the Mac? I have already downloaded the slim version of the ADB and Fastboot files with the platform tools into a folder on my desktop named Andriod, so i have these already. And i know that if you hold the button down on the nexus and plug the power in it brings up the bootloader screen. I just need help with the commands in terminal and where to access the drivers from. Also, on the Nexus the Developer options have already been enabled and USB debugging has been turned on. If anyone can help, It would be much appricated! Just started to use terminal commands so yes i am a noob in this department . Thanks agin in advance.
-Jason
Click to expand...
Click to collapse
http://developer.android.com/sdk/win-usb.html
"Note: If you're developing on Mac OS X or Linux, then you do not need to install a USB driver. To start developing with your device, read Using Hardware Devices."
http://developer.android.com/tools/device.html

Sleeepy2 said:
http://developer.android.com/sdk/win-usb.html
"Note: If you're developing on Mac OS X or Linux, then you do not need to install a USB driver. To start developing with your device, read Using Hardware Devices."
http://developer.android.com/tools/device.html
Click to expand...
Click to collapse
Hey Sleepy2, I just did a brief read through and it states this:
Set up your system to detect your device.
If you're developing on Windows, you need to install a USB driver for adb. For an installation guide and links to OEM drivers, see the OEM USB Drivers document.
If you're developing on Mac OS X, it just works. Skip this step.
If that is the case, what would you suggest doing next? Thanks again for helping!

MrBoostinduced said:
Hey Sleepy2, I just did a brief read through and it states this:
Set up your system to detect your device.
If you're developing on Windows, you need to install a USB driver for adb. For an installation guide and links to OEM drivers, see the OEM USB Drivers document.
If you're developing on Mac OS X, it just works. Skip this step.
If that is the case, what would you suggest doing next? Thanks again for helping!
Click to expand...
Click to collapse
Open a terminal, navigate to the directory where you downloaded fastboot and go ahead with the commands shown in the first post. You will probably have to add a "./" in front of the commands given that you are on a mac, e.g.,
Code:
fastboot devices
becomes
Code:
./fastboot devices

I seem to be having the same problem as goxboxlive. I have tried installing the drivers about 100x tried on several computers and rebooted many a time. The only thing I can think of from the posts in here was to update fastboot but I dled the android studio and I would assume that has the latest version in there? Otherwise I couldn't find somewhere to download just fastboot from. Any help or recommendations or where I can dl the latest fastboot?
---------- Post added at 02:28 PM ---------- Previous post was at 01:57 PM ----------
Follow up. Got it to work. In the guide it says after booting into fastboot to type "adb devices" in the console. You should instead type "fastboot devices" to see if you have the correct drivers and then go on from there. This worked for me, hopefully it will help someone else too.

knobbs said:
I seem to be having the same problem as goxboxlive. I have tried installing the drivers about 100x tried on several computers and rebooted many a time. The only thing I can think of from the posts in here was to update fastboot but I dled the android studio and I would assume that has the latest version in there? Otherwise I couldn't find somewhere to download just fastboot from. Any help or recommendations or where I can dl the latest fastboot?
---------- Post added at 02:28 PM ---------- Previous post was at 01:57 PM ----------
Follow up. Got it to work. In the guide it says after booting into fastboot to type "adb devices" in the console. You should instead type "fastboot devices" to see if you have the correct drivers and then go on from there. This worked for me, hopefully it will help someone else too.
Click to expand...
Click to collapse
Yep, i posted this earlier in the thread, kinda surprised OP hasn't updated it.
http://forum.xda-developers.com/showpost.php?p=58172001&postcount=7

midnightzak said:
I could be mistaken, but when you're in the bootloader you're going to use FASTBOOT and not ADB commands. So therefore the command should be "fastboot devices" instead of "adb devices"?
Click to expand...
Click to collapse
knobbs said:
In the guide it says after booting into fastboot to type "adb devices" in the console. You should instead type "fastboot devices" to see if you have the correct drivers and then go on from there. This worked for me, hopefully it will help someone else too.
Click to expand...
Click to collapse
midnightzak said:
Yep, i posted this earlier in the thread, kinda surprised OP hasn't updated it.
http://forum.xda-developers.com/showpost.php?p=58172001&postcount=7
Click to expand...
Click to collapse
To avoid further confusion, I've updated the post since the OP hadn't yet.

midnightzak said:
Yep, i posted this earlier in the thread, kinda surprised OP hasn't updated it.
http://forum.xda-developers.com/showpost.php?p=58172001&postcount=7
Click to expand...
Click to collapse
efrant said:
To avoid further confusion, I've updated the post since the OP hadn't yet.
Click to expand...
Click to collapse
Thank you, saw your post that time and wanted to change it but keep forgetting.
Currently working on some basic developer app for Nexus Player.

xDragonZ said:
Thank you, saw your post that time and wanted to change it but keep forgetting.
Currently working on some basic developer app for Nexus Player.
Click to expand...
Click to collapse
It's all good, wasn't terrible let to figure out, and if you're developing even more for the Nexus Player, the more power to ya! Keep it up!

OPO not recognized in ADB Devices

Hey guys, I've long had this issue with my OnePlus One and I for the life of me cannot figure it out after searching and reading mad threads/forums.
Computer OS: Windows 7 x64
Problem: OnePlus One NOT RECOGNIZED under command > adb devices.
So I'm following all the instructions possible step by step. I have my OPO in Recovery (TWRP 2.8.6.0) and it won't show up as an ADB Devices...
Yet, noting key parameters here:
- All my drivers are up to date
- My Android SDK is up to date
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Java SE is up to date
FastBoot - Phone is recognized (picture below).
ADB Sideload Mode in TWRP Recovery - ADB Sideload recognizes OPO, but doesn't work still.
But standard ADB is not listed when Recovery is on main page. But I get this prompt whenever the phone boots into recovery or I plug it in via USB when Recovery is active.
This is my command prompt to prove FastBoot recognizes my device, but ADB does not.
What am I doing wrong? Can someone help me? I've noticed this issue as long as I can remember, and have resorted to always having to copy my ROM files through the OS, doing a factory reset, then installing. I have never been able to use ADB Push.
Can someone provide me some pointers?
Thanks!!!

do you have debugging enabled on the phone, and if you do, have you authorized that computer on the phone? (I guess you have already, but just throwing out some ideas you might have forgotten)

CSquared4290 said:
Hey guys, I've long had this issue with my OnePlus One and I for the life of me cannot figure it out after searching and reading mad threads/forums.
Computer OS: Windows 7 x64
Problem: OnePlus One NOT RECOGNIZED under command > adb devices.
So I'm following all the instructions possible step by step. I have my OPO in Recovery (TWRP 2.8.6.0) and it won't show up as an ADB Devices...
Yet, noting key parameters here:
- All my drivers are up to date
- My Android SDK is up to date
- Java SE is up to date
FastBoot - Phone is recognized (picture below).
ADB Sideload Mode in TWRP Recovery - ADB Sideload recognizes OPO, but doesn't work still.
But standard ADB is not listed when Recovery is on main page. But I get this prompt whenever the phone boots into recovery or I plug it in via USB when Recovery is active.
This is my command prompt to prove FastBoot recognizes my device, but ADB does not.
What am I doing wrong? Can someone help me? I've noticed this issue as long as I can remember, and have resorted to always having to copy my ROM files through the OS, doing a factory reset, then installing. I have never been able to use ADB Push.
Can someone provide me some pointers?
Thanks!!!
Click to expand...
Click to collapse
Firstly, uninstall all the drivers for your OPO from device manager and restart the system
Now, follow this link to install drivers >> http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
After this, install adb and fastboot files >> http://forum.xda-developers.com/showthread.php?t=2317790
Even I have Android SDK installed on my system for developing apps, however, I used above steps to ensure that my system recognises my OPO

Mr hOaX said:
Firstly, uninstall all the drivers for your OPO from device manager and restart the system
Now, follow this link to install drivers >> http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
After this, install adb and fastboot files >> http://forum.xda-developers.com/showthread.php?t=2317790
Even I have Android SDK installed on my system for developing apps, however, I used above steps to ensure that my system recognises my OPO
Click to expand...
Click to collapse
Thanks Mr. Hoax! I will give that a try and report back.
Interestingly in an attempt to use ADB Sideload to install the latest ROM update from scratch, I took a gamble and did a full format/wipe and was able to install the OS using ADB SideLoad. But afterwards, it still didn't come up under ADB Devices...But will try your recommendations and see what happens.
Elkhantar said:
do you have debugging enabled on the phone, and if you do, have you authorized that computer on the phone? (I guess you have already, but just throwing out some ideas you might have forgotten)
Click to expand...
Click to collapse
Yessir, Debugging was enabled through the OS (I don't know of any other way to enable debugging?)

Mr hOaX said:
Firstly, uninstall all the drivers for your OPO from device manager and restart the system
Now, follow this link to install drivers >> http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
After this, install adb and fastboot files >> http://forum.xda-developers.com/showthread.php?t=2317790
Even I have Android SDK installed on my system for developing apps, however, I used above steps to ensure that my system recognises my OPO
Click to expand...
Click to collapse
Hey Mr. Hoax. I tried those steps, uninstalled every driver I could associate with any of my Android devices (have an HTC One as a backup) and sadly, ADB is still not recognizing my OPO when I enter "ADB Devices".
However, I still get the Windows prompt. Any clue?

Wug's tookit for bacon hv step by step procedure to install adb n fastboot drivers...gv it a try...i did it myself n it works nice
1+1

CSquared4290 said:
Hey Mr. Hoax. I tried those steps, uninstalled every driver I could associate with any of my Android devices (have an HTC One as a backup) and sadly, ADB is still not recognizing my OPO when I enter "ADB Devices".
However, I still get the Windows prompt. Any clue?
Click to expand...
Click to collapse
After drivers installation is done, you need to reboot your OPO in bootloader(fastboot) mode and type
fastboot devices
And check out if the prompt shows your device serial number.

I see you're using the nexus driver. Perhaps try a Samsung ADB driver. It works with my phone without problems.

I get the same problem with my work PC, while everything works fine at home.
What CSquared4290 says, applies here:
Computer OS: Windows 7 x64
Problem: OnePlus One NOT RECOGNIZED under command > adb devices.
- All my drivers are up to date
- My Android SDK is up to date
The phone is recognised normally under command > fastboot devices.
Symantec Endpoint Protection is running at my work PC. Could this be a reason?

CSquared4290 said:
Hey Mr. Hoax. I tried those steps, uninstalled every driver I could associate with any of my Android devices (have an HTC One as a backup) and sadly, ADB is still not recognizing my OPO when I enter "ADB Devices".
However, I still get the Windows prompt. Any clue?
Click to expand...
Click to collapse
100% agree with the other posters, really delete all of your old USB ADB drivers, including the Google USB driver. Here's a tool I use for that: http://www.nirsoft.net/utils/usb_devices_view.html
Install Samsung ADB drivers, then when you plug your OPO in you should be able to see it in Device Manager as "Android Device" don't let Windows pick the driver. Right click and pick the browse my computer for drivers, then find the Samsung Android ADB Interface, install that. Unplug your phone, then plug it back in...profit? Good luck!

From my OnePlus X rooting guide. It looks like you need to install the universal adb driver linked in #2 and follow the steps in #3.
If you cannot get the connection to work:
1. Check your USB connection, then verify that Android debugging is enabled in settings and that your computer’s RSA fingerprint has been authorized.
2. Still not working? Open Device Manager in Windows and make sure that you don’t have a yellow exclamation point next to something like “Android Device” or “One.” This would indicate a driver problem that must be resolved. Try re-installing the Universal Android ADB Driver for Windows, and make sure to restart your computer. Once you’ve rebooted, if you still have a yellow triangle, right-click on the device and select “Update Driver Software,” then “Search automatically for updated driver software.”
3. If you still have a yellow exclamation point, then try forcing the driver to install:
In Device Manager, right-click on the device and select “Update Driver Software.”
Select “Browse my computer for driver software”
Select “Let me pick from a list of device drivers on my computer”
Select “ADB Interface” from the list
Select manufacturer “Google”
Select “Android Testing Interface Version xxx”
Click “Next.” If you get a warning, select “Yes” to continue and wait for the driver to install properly.
Click to expand...
Click to collapse