Related
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.
---------------Notes-------------
Be sure to enable debugging on your phone via Settings>Applications>Devlopment>USB debugging.
Confirmed working on:
Win 7 Ultimate x64/x86
Win 7 Home Edition x86?
Win Vista
XP Home x86
XP Pro x64/x86
O.S
What O.S you had this working on?
@th3fallen
143!!
I got it working on win7 Ultimate version
This works for Windows 7 Home Premium Edition as well.
In order to get ADB working on Linux (Ubuntu 9.04) I had to edit /etc/udev/rules.d/51-android.rules (I may have created this file for the G1) and add:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
What I was seeing was the device would sort of show up when I ran adb devices, but it would list ????????? as the ID and no permissions.
~Kenny
I was able to access it by using dream, magic and adb testing device didnt need any specific driver.
I did this to get it working on win 7 ultimate x64
NexVision said:
I was able to access it by using dream, magic and adb testing device didnt need any specific driver.
Click to expand...
Click to collapse
You need the latest refresh of the drivers (and tools for updated fastboot, etc.) from the SDK. If you go to a Windows command prompt and run Android, assuming the tools directory is in your path, you can select the update for both. It will fail in updating tools, since you are using an app in it, but don't close the app, just reapply at that point and it will work on the second go. Then when you install the N1, you will have the drivers you need to install as before.
Not meaning to argue with you but what I was saying is I have had no issues doing anything via adb with it as a magic I have done fastboot as well hey maybe its just working for me.
kfk2 said:
In order to get ADB working on Linux (Ubuntu 9.04) I had to edit /etc/udev/rules.d/51-android-rules (I may have created this file for the G1) and add:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
What I was seeing was the device would sort of show up when I ran adb devices, but it would list ????????? as the ID and no permissions.
~Kenny
Click to expand...
Click to collapse
Hmm...I have that already in my /etc/udev/rules.d/51-android.rules (mine has .rules, not -rules...I'm assuming that's a typo in your post?) and I'm still coming up with ?????????? as the device and no permissions, all attempts to do anything with adb result in it telling me I don't have permission to do these things.
Swervo said:
Hmm...I have that already in my /etc/udev/rules.d/51-android.rules (mine has .rules, not -rules...I'm assuming that's a typo in your post?) and I'm still coming up with ?????????? as the device and no permissions, all attempts to do anything with adb result in it telling me I don't have permission to do these things.
Click to expand...
Click to collapse
Yah that was a typo.. The no permissions error appears to me that adb doesn't have access to the /dev/ devices used. I'm not at home so I cannot lookup what device is created and used in /dev/ for you to check the permissions. I know I killed the adb server and restarted it a few times while trying to get mine to work, along with updating to the latest sdk. So you may want to try those things, you could also try running adb as root and seeing if that fixes it (if so, then it's a simple permission error with udev not creating it with correct permissions).
Alrighty, I think I got it. I'm no udev expert (in fact, I'm rather useless at it), but this worked for me.
1) Make sure USB debugging is turned on on the phone.
2) Plug the phone into the USB port on the machine.
3) Make sure /etc/udev/51-android.rules has
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Click to expand...
Click to collapse
in it.
4) run
adb kill-server
Click to expand...
Click to collapse
5) As root, run
service udev restart
Click to expand...
Click to collapse
6) run
adb start-server
Click to expand...
Click to collapse
Worked for me to get the device recognized.
Hey guys, I have the Android 1.5 SDK/ADB installed on my computer.. so I don't know what will happen when I mount my N1 (haven't tried yet). I want to be able to mount my N1 normally without ADB or anything, 'cause I'm not going to root it for a while. Thanks!
Confirmed on Vista
I can confirm that the instructions in the OP work on Vista. Thanks a lot, th3fallen.
Alleviate said:
Hey guys, I have the Android 1.5 SDK/ADB installed on my computer.. so I don't know what will happen when I mount my N1 (haven't tried yet). I want to be able to mount my N1 normally without ADB or anything, 'cause I'm not going to root it for a while. Thanks!
Click to expand...
Click to collapse
Nothing will happen, ADB doesn't start interacting with your phone without you explicitly telling it to. Also, if you don't have debugging turned on on your phone, then it won't even if you do explicitly tell it to. Feel free to mount the drive on it.
ADB and Root
Maybe I'm doing something wrong, but I can't get ADB to recognize my phone. ADB is all set up correctly, I have it updated (I believe) to the most recent version. I installed the updated USB driver and I see the "Android Phone" in my device manager. I have USB Debugging checked off in my phone settings. ADB worked fine for my G1, but it doesn't recognize my Nexus One.
I shouldn't have to root the phone to have ADB working should I? Can anybody think of something I overlooked? I am running Windows XP Professional SP3
Okay, so I navigated to the "1.1-nexusone-superboot" folder in the command prompt and tried
Code:
adb-windows devices
and my device showed up. Now I want to move those files to where I originally had my adb files in C:\android-sdk-windows\tools so that all I have to type is
Code:
adb devices
to have my phone listed. I tried replacing the files in my \tools folder and renaming them to what they were named before, but that didn't work. Could somebody please help me get this set up properly?
ccunningham83 said:
Okay, so I navigated to the "1.1-nexusone-superboot" folder in the command prompt and tried
Code:
adb-windows remount
and my device showed up. Now I want to move those files to where I originally had my adb files in C:\android-sdk-windows\tools so that all I have to type is
Code:
adb devices
to have my phone listed. I tried replacing the files in my \tools folder and renaming them to what they were named before, but that didn't work. Could somebody please help me get this set up properly?
Click to expand...
Click to collapse
in your command prompt you have to be in the c:\android-sdk-windows\tools\ directory for it to work
ccunningham83 said:
Maybe I'm doing something wrong, but I can't get ADB to recognize my phone. ADB is all set up correctly, I have it updated (I believe) to the most recent version. I installed the updated USB driver and I see the "Android Phone" in my device manager. I have USB Debugging checked off in my phone settings. ADB worked fine for my G1, but it doesn't recognize my Nexus One.
I shouldn't have to root the phone to have ADB working should I? Can anybody think of something I overlooked? I am running Windows XP Professional SP3
Click to expand...
Click to collapse
I was having the same problem yesterday. But i'm on Vista. Nothing seemed to work, but ADB was working fine on my Mytouch. At any rate, I ended up going to download the most recent SDK and trying adb again from a command prompt @ the tools location of the newest SDK, and then everything worked. I don't know if that was something I should have done in the first place and I just didn't know it (duh), but that's what worked for me.
Hey guys,
I have been trying to get my phone connected to my pc for a few days now.
I am having major issues with getting adb to work. I have googled pretty much every solution, tried the drivers posted on here, everything.
It seems that turning on USB debugging on my phone does nothing. I get no new notifications in windows (7), no new hardware, no ADB Composite Interface showing up.
I really don't know what to do next - anyone else have this problem?
Are you able to try plugging it into another computer to check the usb interface isn't faulty?
I have tried it on both my work pc (vista) and my home pc, with the same result.
When I type the command adb devices I just get a empty list.
I put it into fastboot mode and was able to get fastboot devices to list the serial, which is why I think theres something wrong with USB debugging mode on the phone.
Would a factory reset fix a problem like this?
Well I have fully reformatted my pc, and restored the phone and still have the same issue.
You have to install the ADB drivers.
I attached the drivers you need.
If you need more help, let me know.
Still not working - I tried the drivers you attached, as well as previously the drivers from the android adk.
I can get a Android ADB Interface to show up in Device Manager, but the adb devices command just gives me a blank list.
Why is it that I only get Android ADB Interface, and everywhere else on the web I see Android ADB Composite Interface?
W7 x64 and using the SDK drivers mine shows up as Android ADB Composite Interface (at the top, in it's own Android Phone category) with USB debugging enabled.
If I boot the phone into recovery mode, i get Android ADB Composite Interface, adb devices lists my phone, and Android ADB Interface is disconnected.
But when the phone is running, the composite interface is disconnected, and the Android ADB Interface is connected, but adb devices lists nothing.
I have just put on cyanogen mod 6 tonight, and its still the same. Is there any other part of the phone that might cause this?
Tonight I tried on my mates pc, it didn't work, but his desire showed up right away.
It's really frustrating buying a 'developer' phone which I can't develop on.
Well look's like this is a froyo problem with certain devices -
http://code.google.com/p/android/issues/detail?id=9437
So from reading the previous link it seems it's an issue with non 00 mac address's, like the wifi issue. My mac address on my nexus starts with 38.
But the updated broadcom driver in cyanogen mod 6 fixes wifi issuse I have, but not the adb issue.
What is the best way to try get something done about this?
motorola adb interface driver isnt installing on my windows rig? where can i find the driver? i have the sdk installed so i have adb but when i adb devices i get nothing on the list check my drivers and i have a motorola adb interface driver missing
thanks
i am able to wireless adb but still no physical usb adb because of the driver
Install Motorola Device Manager. It has the Motorola ADB driver.
You have USB debugging enabled right?
Sent from my Galaxy Nexus using Tapatalk 4
Here's a link to the Motorola Device Manager hosted by one of the guys on the IRC channel...
http://goo.gl/DiRvpE
Downloaded and installed moto Dev manager and everything it working fine now. Also I did have USB debug enabled.
sent from my rooted at&t moto x
I'm looking to port app restores - mostly game saves - from my old phone to the Droid Turbo. I've used Helium in the past but I can't get the Turbo to connect to Windows 7 yet. I've been trying to use the drivers linked from the Helium URL and here, but without success.
Anyone have luck tracking down USB drivers?
Any suggestions other than Helium?
Update:
Looks like the Motorola drivers started working as soon as I posted this (of course...).
This one was driving me nuts the last two days. On Win8.1 x64, the driver wouldn't auto-load when the device was plugged in. Until I saw your edit reason, I didn't even think to go through the manual device list and select the driver manually. "ADB Interface/Mot Composite ADB Interface" worked for me, as well.
Also, if you change your USB Storage mode on the phone, it may also change how the ADB Interface is detected. I had to manually add the ADB Interface driver a second time when I turned on MTP mode for the USB Storage connection. I had had it previously disabled while trying to figure out the ADB issues, once I had ADB working, I re-enabled MTP and subsequently Windows "forgot" the ADB device driver again.
For others: I had to go through the device manager, pick the unknown adb device and update drivers, pick drivers, select the clockworkmod section on the left and instead of mot composite I had to use the first option, android composite adb interface. Now my mtp connection works. Haven't tried reconnecting yet so it may well forget the drivers again, but at least I know what to do now!
Need the drivers from google sdk kit. Just google search installing adb drivers. I used helium fine.
Looking for some help. ADB isn't working on my MacBook. I have ADB and fastboot in a folder. When I type the devices command to link my device. It reads as offline, Everytime. I've done every troubleshooting tip available. And nothing. Anyone know of a fix?
megarain555 said:
Looking for some help. ADB isn't working on my MacBook. I have ADB and fastboot in a folder. When I type the devices command to link my device. It reads as offline, Everytime. I've done every troubleshooting tip available. And nothing. Anyone know of a fix?
Click to expand...
Click to collapse
Edit: I should note that ADB actually runs fine. It recognizes my OnePlus 3t (shattered screen) and my old note tablet. Just not my moto x4
Did you install the drivers for Moto X4?
Here is the link to the Moto drivers for Mac:
http://www.motorola.com/getmdmmac