Related
Hello all,
I have been following the guide posted by Nephron http://forum.xda-developers.com/showthread.php?t=532719 but am having a few problems with my computer recognising my G1 as an ADB device...
My computer's OS is Vista. I have followed the guide to the letter, have downloaded the SDK and unzipped it to C:\ root. I have checked my phone and ensured that 'USB Debugging' is checked. My computer doesn't try to install the Android 1.0 driver (as the original drivers are already installed) and my device is ready to use as a storage device - HOWEVER it is not acknowledging it is an ADB device.
I have tried using USBDeview but it won't let me uninstall the 3 already installed Android drivers. I have even tried manually uninstalling them through the taskbar USB device manager. Even when I uninstall them and re-connect my phone, it automatically installs the standard drivers and doesn't give me an option to select the SDK drivers.
Hope that makes sense to someone. How can I install these damn SDK/ADB drivers on my G1?! Thanks.
Try this...
Remove every mass storage device except your phone (Any usb memory sticks, external HDD's, other phones, etc)
Open the start menu, right click on 'Computer', click 'Manage', and you may need to click continue here.
On the next page, click on 'Device Manager' on the left hand side. In the list on the right, open up the tree for 'Universal Serial Bus Controllers'
Find 'USB Mass Storage device' in the list. Right click it, click 'Uninstall'
Click 'Action' at the top, then 'Scan for hardware changes'.
If it all goes well, you should now be asked to locate a driver, point the the Android USB driver. Good luck.
PS, this is all from memory of the issues I had, so if you get stuck, post back .
Worked a charm, thanks!
(Mods...can this be merged to the NEWBIE Q&A thread for ADB/Fastboot etc...more useful place for it than here!)
Glad I could help .
OK...
New problem...
I am using command prompt on vista, entered the following:
cd C:\android-sdk-windows-1.5_r2\tools
adb devices (shows my device listed as HT845KV02724)
adb shell (shows a # on the following line)
However....when I enter adb it returns with /sbin/sh: adb: not found .....what have I done wrong? I have checked that the SDK is in C:\ and have downloaded the SDK again just to be sure. What do I need to change???
Once you type adb shell, you're in a terminal on your phone, you can type shell commands there, you need to type exit before typing adb again.
Basically, it's working as intended .
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.
Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
magma9495 said:
Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
Click to expand...
Click to collapse
I'm having the same issue myself i think.
Look under N1 Q&A and find the topic "N1 Bricked"
Glad to know im not the only one
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
I have a tutorial called ADB 4 Dummies that will walk you through installing the android sdk 2.2(froyo) and setting up your environments. Step by step for every system.
First thing, unplug your Phone from computer, uninstall ALL drivers and try from scratch.
Also, if you're using windows, when you're done and you plug in your phone, don't choose to "automatically find drivers" instead manually point it to the drivers folder in the SDK.
Don't worry, it's not bricked. lol.
mrandroid said:
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
Click to expand...
Click to collapse
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
magma9495 said:
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
Click to expand...
Click to collapse
Hmmmm....
There are 2 modes to the bootloader HBOOT and Fastboot.
Make sure you're phone is in fastboot mode... it should say FASTBOOT USB highlighted in red on top. If it doesn't, use the volume down key, select Fastboot and hit the power button once to switch the phone to fastboot.
Remember, "adb devices" works while your phone is turned on regular. If your phone is in Fastboot mode use "fastboot devices"
Ok, are you using windows? If you are;
Turn off your phone and boot it back up in Bootloader mode. (trackball+pwr, or volume down+pwr)
Once it's on bootloader, plug it in to the computer.
See if the computer asks for any drivers, etc. If it does point it to the Drivers folder in the SDK. If it doesn't... go into your Device Manager. (Right click on MY COMPUTER, click on MANAGE and when computer management opens up, go to Device manager from the list on the left). Look to see if there are any icons with an Exclamation mark and yellow background. If there is, right click on it, select update driver and point it to the drivers folder in the sdk.
Basically there should be a menu on top that says "Android Phone" and when you expand that selection you'll see "Android Bootloader Interface".
nope, no luck with that either, I tried it both on windows XP and windows 7. same error each time. Could it be a problem with my device? because Snow Leopard doesn't recognize the nexus as a storage device or anything
Damn. I think i'm out of options. Last thing to try:
- Turn on phone regular.
- Plug in through USB to computer (try a different USB cable, even if that one worked with the CLIQ, try a different USB port also.)
- On Phone: GO to settings, Application Settings, Development, USB Debugging, (if it's checked on, check it off then on again) make sure it's ON.
Go into your Android SDK folder, go into the TOOLS folder. Now click on DDMS. See if it lists your device...
Last thing would be to go back through the Device Manager, and click on SCAN HARDWARE while your phone is plugged in... It has to be on that list somewhere, whether it's a bad driver, etc, it should still appear in your device manager somehow.
alright that didnt work, but, i got it, i just kept unplugging and plugging back in my phone until adb recognized it. then i got fastboot to run and now i have superuser . But now im stuck at another point. I'm trying to do the recovery.img file. I tried in mobile terminal "flash_image recovery /sdcard/recovery.img" but it told me something like "flash_image not found" I saw that i could do this via fast boot but i dont know how to do that. how would i do fastboot on Mac?
http://www.myhangoutonline.com/tutorials/nexus-one/6-upgrade-nexus-one-recovery
when i try to do the fastboot command i get "-bash: fastboot: command not found" i dont think i have fastboot set up right
have you tried typing in "./" before the command? I found that that was one of my mistakes I did when I first rooted my phone
tried that, entered "./fastboot-mac flash recovery recovery.img" and i just get "waiting for device"
I believe you can also try "./fastboot-mac flash recovery ./recovery.img"
Alright I flashed a clockwork recovery through the app manager in the market. Is there any way I can apply the other recovery with an update.zip?
Also, thanks so much for all the help guys!!!!!!!!!!
you can do it through terminal emulator, if you go to amonra's recovery thread he tells you how.
this is the link http://forum.xda-developers.com/showthread.php?t=611829
fastboot somtimes doesn't come in the SDK... download the version for your system from here: http://www.myhangoutonline.com/tutorials/nexus-one/5-unlock-nexus-one-bootloader
place it in your androidsdk/tools folder
Been trying to root N1(FRG83) without unlocking bootloader. Downloaded android-sdk to c: drive and downloaded usb driver.
When I boot the N1 into fastboot mode and type fastboot from the cmd prompt on the computer it sees the phone and gives me the serial (HT****)
When I try the same thing from ADB (ADB devices) it doesn't recognize the phone. I just get a blank line and go back to the command prompt. I've tried this on 2 machines (1 Vista the other Windows 7) and get the same results.
The frustrating thing is that I actually had the phone recognized with the ADB devices command when I first set it up but got called away from the computer and never had a chance to run the rooting routine.
Anybody out there solved this problem?? All help appreciated.
Thanks.
download and install the sdks and nexus ine drivers manually.
thanks but no luck
Downloaded drivers as you suggested but no luck. Also tried reinstalling sdk. Debugging is on, Java is installed, I'm out of ideas for the moment.
astron46 said:
Downloaded drivers as you suggested but no luck. Also tried reinstalling sdk. Debugging is on, Java is installed, I'm out of ideas for the moment.
Click to expand...
Click to collapse
Del everything...restart your pc, and download the drivers and sdk..it'll take a few more mins.
When this happened to me, I restarted my PC and it worked.
astron46 said:
Been trying to root N1(FRG83) without unlocking bootloader. Downloaded android-sdk to c: drive and downloaded usb driver.
When I boot the N1 into fastboot mode and type fastboot from the cmd prompt on the computer it sees the phone and gives me the serial (HT****)
When I try the same thing from ADB (ADB devices) it doesn't recognize the phone. I just get a blank line and go back to the command prompt. I've tried this on 2 machines (1 Vista the other Windows 7) and get the same results.
The frustrating thing is that I actually had the phone recognized with the ADB devices command when I first set it up but got called away from the computer and never had a chance to run the rooting routine.
Anybody out there solved this problem?? All help appreciated.
Thanks.
Click to expand...
Click to collapse
If I recall correctly, adb won't work while the phone is in fastboot mode - and that fact that your fastboot commands work fine indicates that it shouldn't be a driver issue. Make sure you're running the adb commands when your phone is actually booted (at least to recovery).
If the phone is recognized by the computer via usb, but the adb does not see the phone connected, you just may need to simply delete and reinstall the latest USB driver that is offered.
There is actually an issue with Nexus One's where the adb composite interface doesn't work. It seems related to the issue with the broadcom driver and the mac address starting with 38.
See here - http://code.google.com/p/android/issues/detail?id=9437 - for more info.
I have now upgraded to frg83 and it works fine.
codesplice said:
If I recall correctly, adb won't work while the phone is in fastboot mode - and that fact that your fastboot commands work fine indicates that it shouldn't be a driver issue. Make sure you're running the adb commands when your phone is actually booted (at least to recovery).
Click to expand...
Click to collapse
This. If you're running ADB in fastboot, you'll get nowhere.
I've searched and searched for a solution to this, nothing is working. Really need help guys.
Phone is on stock ICS rom, PC is Win8 Pro x64. All three files are in the folder, SDK is installed (x64 version), Google USB driver installed, Java for windows installed, and HTC Sync installed but not running.
When in FASTBOOT and USB connected it shows FASTBOOT USB. Device manager shows Android Phone - Android ADB Interface. Is this correct or should it show something else in device manager?
No matter what I've tried when running fastboot oem get_identifier_token in command prompt I get waiting for device. Also running fastboot devices returns nothing.
Don't know what else to try... Seems it doesn't recognize the device but it's in device manager.
Edit: have also tried different usb ports and I know the cable works.
Edite 2: I fixed it. Took me hours to get this working but for any one struggling like I was here is what I did.
Got rid of all the drivers and started back at Android 1.0 in device manager. Manually installed the official SDK google usb driver and selected Android Bootloader Interface for Android 1.0. Also boot the phone and manually install again and select Android ADB Interface.
Here is what really caused me problems. The HTC tutorial I looked at said to take adb.exe, fastboot.exe, and adbWinApi.dll and put them in their own folder. This absolutely does not work for me even now. I used the directory straight from the SDK (sdk\platform-tools) and added fastboot.exe from a previous sdk revision into that folder. Now everything works!!! Finally!
Hi everyone!! I have the same issue as brother bassvoykevlar but the solution here expresed is not all clear to me. Can anyone please give me a hand on this, i am really mad with it . Thanks in advance.
The Best Solution
this problem has also happened with me and i found a solution to this,
this usually happens if your system lacks fastboot drivers.
ADB drivers can only Run ADB shell so that is why you need to have fastboot drivers as well to use fastboot commands.
i think you must have tried this code:
"fastboot oem unlock"
then cmd may have got stuck on "waiting for device"
don't worry install drivers for fastboot then it should work.
google it then get it.
there is 15seconds ADB,fasdtboot installer available try that.
then give it another try.