Database Users

Getting Nexus One ADB/USB Mount working (Driver)

Download This file and extract.
hit Windows Key + r
Type in devmgmt.msc
right click on nexus one
click update
update from location on computer.
select that folder.

404 not found...

Updated sorry about that.

and what is ADB?

android device bridge (i think)
its a program on your PC that gives you control over your android phone. you can flash partitions, push/pull files, go to shell, etc.

It also gives you the ability to mount your sd card and use droid explorer.

I love you. Seriously...

Carloswithac said:
I love you. Seriously...
Click to expand...
Click to collapse
Bear my children? haha.

Sticky Please
th3fallen said:
Download This file and extract.
hit Windows Key + r
Type in devmgmt.msc
right click on nexus one
click update
update from location on computer.
select that folder.
Click to expand...
Click to collapse

Excellent! Thank you!
(downloads in preparation for tomorrow)

Should this work with Windows 7 x64?
th3fallen said:
Download This file and extract.
hit Windows Key + r
Type in devmgmt.msc
right click on nexus one
click update
update from location on computer.
select that folder.
Click to expand...
Click to collapse

DRO4LIFE said:
Should this work with Windows 7 x64?
Click to expand...
Click to collapse
It did for me.

Didnt accept that file for me in Windows XP

In order to use this in vista 64-bit or win7 64-bit put your computer in test mode like this:
-Start>Run>type CMD>Enter
-type "bcdedit /set testsigning on" without the quotes>Enter
-Reboot
-Computer should say "Test Mode" in one of the corners
Mine says it in the bottom right.

For the life of me i can't get this to work. Whenever I plug up the phone to the computer, windows automatically installs a driver. When I try to update, it says the best driver is already in use. ADB not working. Tried uninstalling and same cycle happens over and over. It must be something small and stupid that i'm missing, can anyone help out?
windows vista by the way 32 bit

Hmm any thought for linux users?

Never mind. I'm an idiot. (Don't forget to enable USB debugging!)

Got the nexus plugged in through USB in debugging mode, installed this driver. When I do adb remount I get error message: "error: device not found"
What am I doing wrong? Does this driver not work for Windows XP?

Getting Nexus One ADB/USB Mount working
I have downloaded & unzip the file. But what's the "hit Windows Key + r" you mean I need to run? And the rest of the comment below. Please kindly provide more details.
Type in devmgmt.msc
right click on nexus one
click update
update from location on computer.
select that folder.
P.S. I'm using Windows XP. Eclipse simple can't detect my Nexus One phone even I have the USB debugging turn on. Please kindly help.

evan742 said:
Got the nexus plugged in through USB in debugging mode, installed this driver. When I do adb remount I get error message: "error: device not found"
What am I doing wrong? Does this driver not work for Windows XP?
Click to expand...
Click to collapse
I'm getting the same problem, except I keep uninstalling the drivers and trying to use the ones I downloaded from here. I believe it is using the drivers I downloaded but cannot connect to the phone.
I have under device manager: a usb composite device that I cannot change, USB mas storage device, which I cannot change, and the Nexus one ADB driver which installed no problem. Still getting the same error, even with USB debugging clicked.
I keep trying to update the USB mass storage device and the usb composite device associated with the phone, but it keeps saying the best drivers are in use. The nexus one driver worked but still no adb.

Can't connect to adb shell after Damagecontrol 2.1 ROM update

I have my 2.1 DamageControl ROM running fine (thx damage!). I'm just trying to connect to adb. I'm on win7, 64bit.
I used to connect fine when I was on fresh 1.1.
I thought it was b/c I had an outdated sdk, which I did. I upgraded from v3 to v5, and made sure I downloaded all the latest, including the latest usb driver.
I also checked to make sure I have HTC sync 2.08.
but I just keep getting this.
C:\android-sdk-windows\tools>adb remount
error: device not found
Click to expand...
Click to collapse
anyone else getting this issue, or know the solution?

Try this. It worked for me with Windows 7.
http://theunlockr.com/2009/10/06/how...droid-devices/
I started at Step II. Reinstall Drivers since I already had the SDK.

crunchybutternut said:
Try this. It worked for me with Windows 7.
http://theunlockr.com/2009/10/06/how...droid-devices/
I started at Step II. Reinstall Drivers since I already had the SDK.
Click to expand...
Click to collapse
Link no worky.
I had this same problem. Go into your device manager and reinstall your ADB driver. If you're in the same situation I was in, it'll have a "!" on the ADB item in your list. Right click ADB, update driver, pick from a list of available drivers... or something like that. In the list it gives you, you should see something along the lines of "Android ADB Interface." Pick that... it may give you some kind of warning but install it anyway and you're done.

Try this,
adb kill-server
abd start-server

illogic6 said:
Link no worky.
I had this same problem. Go into your device manager and reinstall your ADB driver. If you're in the same situation I was in, it'll have a "!" on the ADB item in your list. Right click ADB, update driver, pick from a list of available drivers... or something like that. In the list it gives you, you should see something along the lines of "Android ADB Interface." Pick that... it may give you some kind of warning but install it anyway and you're done.
Click to expand...
Click to collapse
Ah hah.. thanks for the heads up. Here's the correct link. I also fixed my original post.

thanks for all the advice! I'll give them all a try.

This is what makes this website awesome. I'm glad everyone has come back together after all of that madness.

Tipharet said:
Try this,
adb kill-server
abd start-server
Click to expand...
Click to collapse
FYI, this one didn't work.

@crunchy - hm, I don't see any adb driver reference

I also went to device mgr in win7, and yeah, it has the !, but when I tried to update, it still failed. I even tried pointing to the usb driver folder in my android sdk, but it didn't like it. maybe something specific to win7 64bit?
Maybe I need to install the drivers manually? But what driver should I look for, for this Damagecontrol 2.1 ROM Sprint Hero now?

Did you make sure to enable debugging?

I don't have a link handy, but just go to the HTC support site for the Eris and download the latest HTC sync. It will fix your drivers, no fuss and straight forward.

smw6180 said:
Did you make sure to enable debugging?
Click to expand...
Click to collapse
Yes, tried with it off, and on. I also tried reinstalling HTC sync 2.08.

I didn't tell you to reinstall sync 2.0.8
Go here http://member.america.htc.com/download/Driver/DROID_ERIS_Verizon/HTCSync2.0.25.zip
And install THAT version of sync it has the proper drivers.
Think I told you to go to the Eris page by accident? Think again. Do it, fix your problem and let's all move on.
Sorry for being so blunt, just frustrated you that you wrote off my original suggestion, responding that you already tried reinstalling the same version of sync that wasn't working in the first place. If you paid attention to my first tip this would have already been solved.

obelisk79 said:
I didn't tell you to reinstall sync 2.0.8
Go here http://member.america.htc.com/download/Driver/DROID_ERIS_Verizon/HTCSync2.0.25.zip
And install THAT version of sync it has the proper drivers.
Think I told you to go to the Eris page by accident? Think again. Do it, fix your problem and let's all move on.
Sorry for being so blunt, just frustrated you that you wrote off my original suggestion, responding that you already tried reinstalling the same version of sync that wasn't working in the first place. If you paid attention to my first tip this would have already been solved.
Click to expand...
Click to collapse
actually, I didn't read your post yet when I posted my statement that I installed 2.08. I was responding to someone else. I'll try out your tip. thx.

obelisk79 said:
I didn't tell you to reinstall sync 2.0.8
Go here http://member.america.htc.com/download/Driver/DROID_ERIS_Verizon/HTCSync2.0.25.zip
And install THAT version of sync it has the proper drivers.
Think I told you to go to the Eris page by accident? Think again. Do it, fix your problem and let's all move on.
Sorry for being so blunt, just frustrated you that you wrote off my original suggestion, responding that you already tried reinstalling the same version of sync that wasn't working in the first place. If you paid attention to my first tip this would have already been solved.
Click to expand...
Click to collapse
Try your own link. It doesn't have a link to the Eris page.
EDIT: the joys of technology. When I used google chrome, the download link didn't work - when I used firefox, it did.
FYI, HTC sync 2.0.25 for the Eris didn't work.

ro_bro said:
Try your own link. It doesn't have a link to the Eris page.
googled and found it myself:
http://www.htc.com/us/support/droid-eris-verizon/downloads/
edit: ugh, the download link leads to a general support page again.
Click to expand...
Click to collapse
Must be a problem with the htc site, the link I provided was a direct link. I'll see if I can find another
Edit: now you do have some kind of weirdness going on. If that didn't work.
First make sure you have done the following... reboot pc and phone. Usb debugging enabled. Then connect phone attempt and shell and copy error here.
Also a question, did you install sync 2.0.8 prior to installing the 2.0.25version ?
A few other possible steps you could try.
Go to your start menu and type cmd one you see the cmd icon pop up in the menu rightclick and run as administrator. Then,
adb kill-server
adb start-server
adb shell
If you still get device not found try: adb devices and paste the output here.

obelisk79 said:
Must be a problem with the htc site, the link I provided was a direct link. I'll see if I can find another
Edit: now you do have some kind of weirdness going on. If that didn't work.
First make sure you have done the following... reboot pc and phone. Usb debugging enabled. Then connect phone attempt and shell and copy error here.
Also a question, did you install sync 2.0.8 prior to installing the 2.0.25version ?
A few other possible steps you could try.
Go to your start menu and type cmd one you see the cmd icon pop up in the menu rightclick and run as administrator. Then,
adb kill-server
adb start-server
adb shell
If you still get device not found try: adb devices and paste the output here.
Click to expand...
Click to collapse
Yes, I had 2.0.8 installed, but i uninstalled first before installing the 2.0.25. but I haven't tried the pc reboot, nor the kill server yet, I'll give those a try. thx!

obelisk79 said:
Must be a problem with the htc site, the link I provided was a direct link. I'll see if I can find another
Edit: now you do have some kind of weirdness going on. If that didn't work.
First make sure you have done the following... reboot pc and phone. Usb debugging enabled. Then connect phone attempt and shell and copy error here.
Also a question, did you install sync 2.0.8 prior to installing the 2.0.25version ?
A few other possible steps you could try.
Go to your start menu and type cmd one you see the cmd icon pop up in the menu rightclick and run as administrator. Then,
adb kill-server
adb start-server
adb shell
If you still get device not found try: adb devices and paste the output here.
Click to expand...
Click to collapse
This advice got me further... but here's what I get:
C:\>cd android-sdk-windows
C:\android-sdk-windows>cd tools
C:\android-sdk-windows\tools>adb remount
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\android-sdk-windows\tools>adb kill-server
C:\android-sdk-windows\tools>adb start-server
* daemon not running. starting it now *
* daemon started successfully *
C:\android-sdk-windows\tools>adb shell
error: device not found
C:\android-sdk-windows\tools>adb devices
List of devices attached
C:\android-sdk-windows\tools>
Click to expand...
Click to collapse
FYI, I still see a '!' beside my 'Android Phone' icon in my device manager.

Try to download and Install
HTC Sync Version 2.0.18 from HTC Support and it must work for you
Thanks

[Problem] Adb won't show up devices whatever I do...

I Tried guides that try to solve this from everywhere, Including here,
I used latest version of the android usb-drivers that comes with the latest Android SDK (downloaded directly from google with the SDK download GUI thinggy).
Tried to uninstall all usb roots,
Tried force removal of driver using external app and re-installations
Tried different drivers from multiple locations,
And still, whatever I try - there is notihng on the "adb devices" list
"List of devices attached"
<CR>
<CR>
C:\.......>
Everything shows up okay, on first run of the adb the 'whatever' service starts and everything is fine
Device DOES appear properly on device manager "Android Composite ADB Interface".
Windows DOES the pnp beep whenever I check or uncheck the "Debugging mode"
This hapnned both on STOCK ROM (first or second software version of the phone released) and on latest Cyanogen 5.0.6
One thing I did noticed, "Android ADB Device" Either appear under "Android" type (usb debugging on) or under USB Controllers (When usb debugging is off).
Ho, I did not mentioned the phone, I'm talking about Nexus One.
Thanks for any help.

Amm, any ideas?

Try using a program named USBDEVIEW, remove the android driver and plug the phone to your PC again and wait to reinstal the drivers.

I take it your on Windows, so I might not be much help as I use Linux strictly but try to run the command prompt as Administrator (right click > run as I think) and then
adb kill-server
adb start-server
Not sure if that will help but I know in Linux you must start the ADB server as root in order to see the attached devices, so I assume in Windows you must start it as Administrator.

I ran into a similar issue with my sapphire. Turns out it was as simple as me having my tethering app on. Once I turned it off (pda net), it worked like a charm. Hope this helps

Beackman said:
Try using a program named USBDEVIEW, remove the android driver and plug the phone to your PC again and wait to reinstal the drivers.
Click to expand...
Click to collapse
I Ment just that when I said "Tried force removal of driver using external app and re-installations"
drew630 said:
adb kill-server
adb start-server
Click to expand...
Click to collapse
Tried that just now, on windows I'm in the Administrators group, that should work... It doesn't :/
bmxrideher said:
I ran into a similar issue with my sapphire. Turns out it was as simple as me having my tethering app on. Once I turned it off (pda net), it worked like a charm. Hope this helps
Click to expand...
Click to collapse
Good idea, but still no salvation :/

Try uninstalling the mass storage driver for the phone, this worked for me

Oh Ehm Gee!!!!
That was perfect! I did that and I got what I needed. Now I'm off to root that som'bish.
+1 to you sir, +1 indeed

Synestr said:
Oh Ehm Gee!!!!
That was perfect! I did that and I got what I needed. Now I'm off to root that som'bish.
+1 to you sir, +1 indeed
Click to expand...
Click to collapse
No problem, lol, almost a month later. Glad I could help.

Naemion said:
No problem, lol, almost a month later. Glad I could help.
Click to expand...
Click to collapse
Hells to the yea, I now has root and rom and I am a happy boy!
Thanks again

hmm >.< nothing is working for me this laptop is not detecting my (Nexus S) device in ADB
windows sees it fine, drivers are installed (for normal mode and ADB mode), mass storage works,
but ADB Devices list shows up empty
2 other phone works just fine (SGS & XT720)
Update: went to another computer and it shows up properly.... (you just gotta "luv" windows )

Try installing htc sense from htc website even if running vanilla. It will install the driver properly. Then un-install sense and keep drivers. It's the only thing that worked for me.
Sent from my HTC Vision using XDA App

windows 8 consumer preview and ADB

This seems to have messed up my ADB.. i can no longer access my phone..
it says android adb device in device manager, but when i try and fastboot into it it say
"the system cannot find message text for message number 0x2331 in the message fille for Application"
also it now says Device offline...
anyone else have this issue?
iv tried reinstalling drivers but it says drivers already installed
SCRATCH THIS....
i fixed it.. strange problem with windows 8.. nevermind

What exactly did you do to get it to work at all? I can't see to get it to even see my device.

Jasgfx said:
What exactly did you do to get it to work at all? I can't see to get it to even see my device.
Click to expand...
Click to collapse
Make sure you got the .net framework in place and java.
Sent from my Nexus S 4G using Tapatalk

Make sure you have USB debugging on ..
it just installed adb drivers for me ... .
It ended up being a problem with my rom, I had adb over network on and it messed it up ...
Also try
Adb stop server
Adb start server
Sent from my Nexus S using Tapatalk

also adb works fine , but fastboot doesnt.... so that's an issue

Anyone get ADB working?

Anyone get ADB working? I'm getting a no permissions (udev rules) on my linux machine. I'm guessing we need to add the device into udev
EDIT: Solution for Ubuntu/Linux here: https://forum.xda-developers.com/showpost.php?p=73619079&postcount=20
hmm it works on my Mac though..

did you use Sudo?

stewa2jm said:
did you use Sudo?
Click to expand...
Click to collapse
Yeah, it's not working.. I tried adding the dev in my android.rules file and still nothing. I'm going to play with it more now
Sent from my PH-1 using Tapatalk

Do you need to update your ADB version on your Linux box? I had this issue at one point. With a different phone a couple years ago. Wouldn't recognize the device.

stewa2jm said:
Do you need to update your ADB version on your Linux box? I had this issue at one point. With a different phone a couple years ago. Wouldn't recognize the device.
Click to expand...
Click to collapse
I'm always on the latest version since I do a lot of Android development. I don't get why it's not working.. I've had to add devices in udev so many times, never did it give me an issue before. I'll see if I can figure it out though
Sent from my PH-1 using Tapatalk

ADB Debugging is on in Dev Options right? lol
I know its super basic, but got to check anyway.

whatever you figure out, please let us know! Good luck, and congrats on getting your device!

IM0001 said:
ADB Debugging is on in Dev Options right? lol
I know its super basic, but got to check anyway.
Click to expand...
Click to collapse
Really? Lol I did mention it works on my Mac, so yeah.. It's turned on.. I've even tried turning it off and then on again. [emoji1] [emoji1] [emoji1] [emoji1]
stewa2jm said:
whatever you figure out, please let us know! Good luck, and congrats on getting your device!
Click to expand...
Click to collapse
Will do!
Sent from my PH-1 using Tapatalk

any idea whats causing adb to not work?

drocny87 said:
I found a work-a-round to transfer your files from one phone to the Essential.
create a folder on your desktop and copy and paste all files you want transferred to the PH1. Once you have completed that just copy and paste those files from that folder to the phone.
Click to expand...
Click to collapse
wow, an extremely obvious solution to a problem no one asked about and has nothing to do with this thread!!

I've got ADB to connect somewhat. Instead of cd\sdk\platform-tools just run cd\sdk. ADB devices shows my phone, but once I ADB reboot bootloader, it will boot into the bootloader, but that's it.

I can't get it to work at all windows 10
Sent from my PH-1 using Tapatalk

I'm on Windows 10 as well. ADB works as long as the phone is booted into the OS. Once I enter the bootloader ADB nor fastboot can see the device

skw5115 said:
I'm on Windows 10 as well. ADB works as long as the phone is booted into the OS. Once I enter the bootloader ADB nor fastboot can see the device
Click to expand...
Click to collapse
What is your usb setting? Charging, file transfer?

bricky23 said:
What is your usb setting? Charging, file transfer?
Click to expand...
Click to collapse
I tried on both already
Sent from my PH-1 using Tapatalk

I got ADB working on linux. You need to add this to your 51-android.rules
#Essential
SUBSYSTEM=="usb",ATTR{idVendor}=="2e17", ATTR{idProduct}=="c032", MODE="0666", GROUP="plugdev"
I still can't get fastboot to work yet though. To get it to work I need to run: sudo $(which fastboot) devices
I'm going to play around with it more to see if I can get it to work just using fastboot devices

ADB is working on Windows 10, but as mentioned above, fastboot isn't recognized. Can't unlock the effing bootloader without that dammit.
---------- Post added at 08:20 PM ---------- Previous post was at 08:14 PM ----------
bricky23 said:
What is your usb setting? Charging, file transfer?
Click to expand...
Click to collapse
File transfer

Okay so to get it my PC to recognize the device in fastboot, I had to open Computer Management < Device Manager and find the device listed as Mata while booted into the bootloader. Windows didn't know what driver to use so I manually selected the Android Bootloader driver. You have to list all installed drivers on your machine and it should show up for windows 10 users. Device is now unlocked

skw5115 said:
Okay so to get it my PC to recognize the device in fastboot, I had to open Computer Management < Device Manager and find the device listed as Mata while booted into the bootloader. Windows didn't know what driver to use so I manually selected the Android Bootloader driver. You have to list all installed drivers on your machine and it should show up for windows 10 users. Device is now unlocked
Click to expand...
Click to collapse
Same here, just manually installed Google USB Driver and installed it as "Fastboot Interface" and it worked.

Ok I got adb and fastboot both working on Ubuntu/Linux now. Instead of adding the line I posted in my previous post just run this:
sudo sh -c "echo 'SUBSYSTEM=="usb", ATTR{idVendor}=="2e17", MODE="0666", GROUP="plugdev"' >> /etc/udev/rules.d/51-android.rules"
Then
sudo service udev restart
Then ubplug your device if it's plugged in via USB and then plug it back in. adb works as well as fastboot