Develop Bugs

ADB doesn't work for my Galaxy Nexus

Hi,
I realize a lot of people might have the same problem as I have, but haven't found the answer after searching for many hours. So here's my problem:
windows vista x64
installed android SDK and all related drivers
GN is recognized with correct driver in both fastboot mode and regular "on" mode.
GN is recognized as a device in regular on-mode with 'adb devices'
GN is recognized as a device in fastboot mode with 'fastboot-windows devices'
HOWEVER, when GN is put into fastboot mode, NO devices are found with 'adb devices' even though the icon for 'safely removing hardware' pops up with 'Android ADB Interface', which means the driver is correctly installed.
Someone please help explain why the device is not recognized by 'adb devices' command under fastboot mode even though it's recognized by the computer!
Summary:
GN is found with 'adb devices' for normal boot, but GN is not found under 'adb devices' for fastboot mode. I have reinstalled the android ADB driver, but still the same problem.
I am stressed out! Please help me

I have noticed exactly what you are talking about however what I have found is that it doesn't seem to need to be able to respond to the adb devices command. I was still able to unlock,root and flash multiple different boot.img and radio.img files through fastboot without the computer returning the device while in fastboot. Hope this helps.
Justin
P.S. while you are in fastboot mode it seems you may be looking for something different than standard adb commands. Fastboot is primarily used in this situation so a command for you will typically look something like this"
fastboot-windows flash boot boot.img
or
fastboot-windows flash radio radio.img (the radio.img and boot.img files used in these examples you would want located in the same folder as fastboot-windows)
if you want to try the software out without flashing it "permanently" try:
fastboot-windows radio radio.img (just forget the flash portion)
for unlocking the bootloader the command will look something like this:
fastboot-windows oem unlock

ADB isn't used in fastboot mode, fastboot.exe is.
ADB is for when the phone is running Android or recovery only.

Phone doesn't recognize ADB in fastboot
Phone doesn't recognize ADB in fastboot - have used every conceivable method - downloaded Samsung drivers. Downloaded PDANet. Uninstalled Samsung and tried Naked Samsung. I got the phone unlocked. But I CANNOT get the PC 64 to recognize ADB when I am in fastboot. HELPPPPPPP. I've been working on this for TWO DAYS, and it is RUINING my Christmas holiday.

Have you tried the driver installation/troubleshooting section of this post?

Unfortunately, yes. I tried the Samsung drivers. Then I tried the PDANet. I also tried the Samsung naked drivers. I was sure that MSKIPS toolkit was going to work, but when I typed in "2" for rooting, NOTHING happened. I'm at my wits end.

HeathCliffR said:
Phone doesn't recognize ADB in fastboot - have used every conceivable method - downloaded Samsung drivers. Downloaded PDANet. Uninstalled Samsung and tried Naked Samsung. I got the phone unlocked. But I CANNOT get the PC 64 to recognize ADB when I am in fastboot. HELPPPPPPP. I've been working on this for TWO DAYS, and it is RUINING my Christmas holiday.
Click to expand...
Click to collapse
Of course it doesn't.
AS STATED MULTIPLE TIMES IN THIS THREAD, YOU MUST USE FASTBOOT.EXE.
Please, read thread then reply.

When phone is turned ON - use adb
When in FASTBOOT mode - use (surprise surprise) fastboot

When phone is turned on or in recovery - use adb (check it with "adb devices" ,without " in cmd)
When in FASTBOOT mode - use fastboot (check it with "fastboot devices" ,without " in cmd)
In order to work fastboot you must have the fastboot.exe preferably in the same folder with adb

Try this
I tried installing PDAnet but no Joy.. but went to device manager and selected adb drivers and samsung from the list and that did the trick...

Need some help getting adb and fastboot workiing under Ubuntu

Hey guys, I'm trying to get adb and fastboot working under Linux. I added udev rules for adb, fastboot and flashmode(idk if this one was really necessary). Adb and fastboot are already working with my other devices, but does not seem to recognize my Xperia Play, adb devices in terminal lists nothing, same thing with fastboot devices. I tried using flashtool, it says my device is connected using fastboot and when i try to flash lupus kernel flashtool shoots an error saying my device needs to be connected with fastboot.
My Xperia is running Ics/Paranoid 4.0.4 and debugging mode is turned on
What can possibly be wrong here? Any Ideas?

Check the drivers. It could be giving you those errors because of the drivers you're using. Try to update them.

adb reboot bootloader - device not found

I've installed ADB/Fastboot/USB Drivers from http://forum.xda-developers.com/showthread.php?t=2588979 (tried both 1.3 and 1.4.2 versions.
Booted my SW3 into Fastboot (whitescreen, with fastboot written on it) - attached to the PC, Device shows up as SAMSUNG Android Phone > Android ADB Interface
Ran CMD as an Administrator.
Typed, adb reboot bootloader.... Error: device '<null>' not found.
Typed adb devices... not listed.
Okay, so using a driver stripper (and windows program uninstaller), removed all Samsung phone USB drivers, KIES and existing ADB drivers. Re-ran the top tool to re-install everything. Repeated process, still showing up as SAMSUNG Android Phone > Android ADB Interface. Still not detected.
No idea at all what's going on here. I've tried cleaning the drivers multiple times. Other USB ports (2.0 & 3.0). Tried manually updating the driver to Google Inc. driver variants (9.0-11.0)
Really appreciate any help here.

if you're into bootloader you have to type fastboot devices , adb only works outside fastboot in system mode

woschirmer said:
if you're into bootloader you have to type fastboot devices , adb only works outside fastboot in system mode
Click to expand...
Click to collapse
Mind if I pick your brain on that point. I'm used to ADB on a smartphone, I really expected this to be similar but there's clearly some catches.
I don't think I'm into bootloader yet because the command 'adb reboot bootloader, or adb reboot-bootloader' doesn't do anything other than throw the error mentioned above.
However, typing fastboot devices gives me.
14442D38F870562 fastboot
But this doesn't allow me to process to run through the other ADB commands I need to complete. 'adb devices' still lists nothing.
In short, I'm trying to downgrade my SW3 to LCA32, as required to turn on the NFC functionality https://github.com/pimpimmi/LibreAlarm/wiki/How-to-install-NFC-on-Sony-Smartwatch-3
It's to assist in enhancing a medical device that uses NFC.

Sideburnt said:
Mind if I pick your brain on that point. I'm used to ADB on a smartphone, I really expected this to be similar but there's clearly some catches.
I don't think I'm into bootloader yet because the command 'adb reboot bootloader, or adb reboot-bootloader' doesn't do anything other than throw the error mentioned above.
However, typing fastboot devices gives me.
14442D38F870562 fastboot
But this doesn't allow me to process to run through the other ADB commands I need to complete. 'adb devices' still lists nothing.
In short, I'm trying to downgrade my SW3 to LCA32, as required to turn on the NFC functionality https://github.com/pimpimmi/LibreAlarm/wiki/How-to-install-NFC-on-Sony-Smartwatch-3
It's to assist in enhancing a medical device that uses NFC.
Click to expand...
Click to collapse
Okay progress, I see what you mean now adb reboot bootloader doesn't work. But fastboot reboot bootloader does. This is allowing me to move through the necessary TWRP and img steps. Thanks.

fastboot not detecting phone

hello all,
I am trying to install android 2.0 preview. I installed android studio and I am able to get device listed using "adb devices" command.
I am able to enter boot loader using "adb reboot-bootloader" as well.
but in boot loader when I try to run fastboot oem then it says "waiting for an device".
also "fastboot devices" does not return anything.
E:\Android\sdk\platform-tools>fastboot oem unlock
< waiting for any device >
I can see "Kedacom USB device" is installed while in bootloader mode. can anyone help me? thanks
I am using windows 10

Same here, not detected by '
Code:
adb devices
' or '
Code:
fastboot devices
'. Windroid toolkit stuck at "rebooting device" while it is in Fastboot mode, and if you reboot it manually, it gets stuck at "unlocking device". Drivers are installed, maybe not properly?not properly?

adb devices works for my case after downloading latest sdk. but fastboot is no go.

windows xp ???

Sorry forgot to add that details - windows 10

Have you found a way to resolve this?

Bricked HTC one m9. Any way to unbrick?

I have an HTC One m9 that bootloops and has a broken recovery that cannot be booted into. It has an unlocked bootloader. I tried to go into download mode and recover the phone with adb commands, but the device does not show up in the command line as a connected adb device. I suspect that is because usb debugging is not enabled. is there any way to enable usb debugging without having a working recovery or main os, or am I out of luck. Also is there any other way to unbrick the phone without using adb or usb debugging?

Re-flash Stock ROM.
Code:
fastboot devices
fastboot flash <STOCK-ROM.zip>

When I plug in the phone to the computer via usb, it does not find it as a device when I do fastboot devices. if I try to flash anyway, it just says something along the lines of waiting for device.
Also does it matter if I use powershell or cmd?

its better to use cmd, and have you installed fastboot drivers?