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...

I have messed up, I don't know where to turn. HTC One M8 softbricked in Bootloop.

I have an HTC One m8 that is stuck on Bootloader. It is an unlocked bootloader with S-Off. I had CWM but I installed stock recovery back onto the phone before flashing a stock kernel (I was trying to make the phone look untampered with before I turned it over to my provider), the Kernel came with a sha1 and was from a trusted website and I am 100% sure it was the right compatible Kernel I'm pretty sure I just had a bad flash.
I have tired the following to get the phone past the bootloader:
1. Fastboot USB Mode --> Try to get ADB to recognize the device --> Debugging mode isn't on (obviously) --> ADB can't recognize the device.
2. Use AndroidSDKSlim/ Android SDK tools / Android Utility to remotely turn on Debugging mode (I got nowhere with this)
3. Attempted to use PdaNet to remotely turn on Debugging mode (got nowhere)
4. HTC Sense doesn't even know whats going on
I just need to get TWRP or CWM or litearlly Any recovery installed. That's all I need, I can do everything from there. I can't remotely install a recovery via adb because adb can't recognize my device because I can't turn Debugging mode on because my device is softbricked!!! Gahhhh. I haven't been able to come up with a way to remotely enable debugging mode or to get adb to recognize my device.
Any ideas/comments/suggestions would be heavily appreciated - I've resourced from every relevant thread I could find. Posting here was a last resort I try to fix things on my own but I'm too many days into this with no results please anybody.

ADB won't work while on fastboot mode. ADB only while in recovery or on OS running.
You don't need USB debugging on for fastboot
fastboot devices - see whether your device is listed with serial no.
if yes then run
fastboot flash recovery NameofRecovery.img

ckpv5 said:
ADB won't work while on fastboot mode. ADB only while in recovery or on OS running.
You don't need USB debugging on for fastboot
fastboot devices - see whether your device is listed with serial no.
if yes then run
fastboot flash recovery NameofRecovery.img
Click to expand...
Click to collapse
Thank you for reply!
I have not been able to get ADB to recognize the device, which is pretty much my whole issue right now. It does not appear under the devices list. If I can just get adb talking with my phone everything else should be easy, I just can't figure out why it's not recognizing it.

Gitnerd said:
I have an HTC One m8 that is stuck on Bootloader.
I have tired the following to get the phone past the bootloader:
1. Fastboot USB Mode --> Try to get ADB to recognize the device --> Debugging mode isn't on (obviously) --> ADB can't recognize the device.
Click to expand...
Click to collapse
Gitnerd said:
I have not been able to get ADB to recognize the device, which is pretty much my whole issue right now.
Click to expand...
Click to collapse
I repeat again my reply ...
ADB won't work while on fastboot mode. ADB only while in recovery or on OS running.
You don't need USB debugging on for fastboot
fastboot devices - see whether your device is listed with serial no.
When on bootloader/fastboot mode
run command
fastboot devices
not adb devices
Gitnerd said:
I just need to get TWRP or CWM or litearlly Any recovery installed. That's all I need, I can do everything from there. I can't remotely install a recovery via adb because adb can't recognize my device because I can't turn Debugging mode on because my device is softbricked!!!
Click to expand...
Click to collapse
then run these command to install recovery ... you can't install recovery via ADB, only fastboot
fastboot flash recovery NameofRecovery.img

ckpv5 said:
I repeat again my reply ...
ADB won't work while on fastboot mode. ADB only while in recovery or on OS running.
You don't need USB debugging on for fastboot
fastboot devices - see whether your device is listed with serial no.
When on bootloader/fastboot mode
run command
fastboot devices
not adb devices
then run these command to install recovery ... you can't install recovery via ADB, only fastboot
fastboot flash recovery NameofRecovery.img
Click to expand...
Click to collapse
Oh.. My..God..
You just saved my life, this whole time I thought fastboot utility in AndroidSDK was just a stripped version of ADB. I'm a moron!
I have TWRP up and running holy crap thank you so so so so much, you are seriously a life saver.

try this
Gitnerd said:
I have an HTC One m8 that is stuck on Bootloader. It is an unlocked bootloader with S-Off. I had CWM but I installed stock recovery back onto the phone before flashing a stock kernel (I was trying to make the phone look untampered with before I turned it over to my provider), the Kernel came with a sha1 and was from a trusted website and I am 100% sure it was the right compatible Kernel I'm pretty sure I just had a bad flash.
I have tired the following to get the phone past the bootloader:
1. Fastboot USB Mode --> Try to get ADB to recognize the device --> Debugging mode isn't on (obviously) --> ADB can't recognize the device.
2. Use AndroidSDKSlim/ Android SDK tools / Android Utility to remotely turn on Debugging mode (I got nowhere with this)
3. Attempted to use PdaNet to remotely turn on Debugging mode (got nowhere)
4. HTC Sense doesn't even know whats going on
I just need to get TWRP or CWM or litearlly Any recovery installed. That's all I need, I can do everything from there. I can't remotely install a recovery via adb because adb can't recognize my device because I can't turn Debugging mode on because my device is softbricked!!! Gahhhh. I haven't been able to come up with a way to remotely enable debugging mode or to get adb to recognize my device.
Any ideas/comments/suggestions would be heavily appreciated - I've resourced from every relevant thread I could find. Posting here was a last resort I try to fix things on my own but I'm too many days into this with no results please anybody.
Click to expand...
Click to collapse
1) Reboot the phone using Power+Vol Up
2) The moment the screen goes dark to reboot and before the white HTC logo screen appears again (Should be around 10 seconds), press the volume down key.... Do not let go of vol down until you see the bootloader screen
3) If the bootloader doesn't appear, you either started pressing Vol Down too late, or let go of it too early. Just do the steps again until you get it right.
4) Once you are in the bootlader, select select fastboot by pressing power key.
5)you can flash either permanent or temporary a TWRP recovery once you are in fastboot.
6)Once you are in recovery mode, you can transfer any custom rom to memory or sd card, then install it from the place you chose.
7) you can flash RUU file at fatboot mode as well.

fastboot never start after update to android 6

Hy
I had an unlocked bootloader phone. Yesterday I flashed the new Android 6, Europe version from the Huawei blog forum, no beta, on my Huawei GX8. I used the method, dload on SD card, Phone off an the press Volume down+volume up+Power button.The flashing was normaly.
Now the phone starts normaly but I can´t start fastboot. When the phone is off and i press Vol down + Power the phone start the android system and the Huawei logo is coming not the fastboot Modus. I can see my phone and the order under Windows but i can not control my phone with the fastboot command. (example: fastboot device. the answere ist searching devices, but it comes no resolution) I loaded the last version of Fastboot, but the problem is the same.
Please can you help me. What can i do? Many thanks for your help!

Should be connect the charger cable to the phone.
charger or computer
excuse me for bad english

No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.

bertl237 said:
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
Click to expand...
Click to collapse
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?

krispin said:
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
Click to expand...
Click to collapse
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.

bertl237 said:
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
Click to expand...
Click to collapse
So, you connect your phone, open minimal adb and fastboot too, run "adb devices", you see device id? If yes, run "adb reboot bootloader" . Phone shoult reboot to fastboot mode. Then run "fastboot devices" to see if it is connected properely.

i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?

bertl237 said:
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
Click to expand...
Click to collapse
No, you should be able to use adb and fastboot with stock recovery.
After first adb command you shoult approve authorization on your phone.

Here is screenshot from minimal adb...
Phone must be in MTP mode.

And here is phone in fastboot

Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.

bertl237 said:
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
Click to expand...
Click to collapse
Just reboot to fastboot and flash surdu-petru version of TWRP recovery 3.0.2 with command "fastboot flash recovery xxxxx.img". And than reboot to recovery and flash supersu zip.

(help please) htc one m8 not showing in adb command prompt while in fastboot.

so I'm trying to fastboot flash TWRP. That way I can root it after the custom recovery is set up.
My HTC is S-OFF, I installed android studio for the adb fastboot command prompt. Then installed all HTC drivers. I then plugged in my HTC into my pc which is running windows 10 via USB port which are 3.0
I opened up the folder where the fastboot was installed when I downloaded android studio. Then I pushed shift and right clicked and chose open command promp. I then typed: adb devices
The command prompt runs and it shows my HTC in the device list. Then I typed: adb reboot bootloader. It boots to the fastboot.
And so here is my problem........... once I boots to fastboot I thenjoy again type: adb devices. Cmd runs and the device list is blank. I checked my drivers and device in device manager and everything is fine. Even I'm fastboot it reads the drivers no problem.
I've tried everything. I've read to try reinstalling the drivers, try installing universal drivers, try different USB cables, try different USB ports that arent 3.0 port, I even tried a different adb fastboot software and still came up with the same outcome. I've read a bunch of different threads and just can't find anything. I am just stuck I don't know what to do. And am asking for help please. I would really appreciate the help and guidance. Because....... this s**t is driving me crazy haha. I've rooted galaxies and have my s5 on lollipop rooted. But
I'm still a noob and especially with HTC. So please some one lend me a helping head I am at a complete loss.

Whisperz6662 said:
so I'm trying to fastboot flash TWRP. That way I can root it after the custom recovery is set up.
My HTC is S-OFF, I installed android studio for the adb fastboot command prompt. Then installed all HTC drivers. I then plugged in my HTC into my pc which is running windows 10 via USB port which are 3.0
I opened up the folder where the fastboot was installed when I downloaded android studio. Then I pushed shift and right clicked and chose open command promp. I then typed: adb devices
The command prompt runs and it shows my HTC in the device list. Then I typed: adb reboot bootloader. It boots to the fastboot.
And so here is my problem........... once I boots to fastboot I thenjoy again type: adb devices. Cmd runs and the device list is blank. I checked my drivers and device in device manager and everything is fine. Even I'm fastboot it reads the drivers no problem.
I've tried everything. I've read to try reinstalling the drivers, try installing universal drivers, try different USB cables, try different USB ports that arent 3.0 port, I even tried a different adb fastboot software and still came up with the same outcome. I've read a bunch of different threads and just can't find anything. I am just stuck I don't know what to do. And am asking for help please. I would really appreciate the help and guidance. Because....... this s**t is driving me crazy haha. I've rooted galaxies and have my s5 on lollipop rooted. But
I'm still a noob and especially with HTC. So please some one lend me a helping head I am at a complete loss.
Click to expand...
Click to collapse
You're using the wrong command.
You can't use adb commands when booted to bootloader, only while booted to system, as you did the first time.
Once you do adb reboot bootloader use fastboot devices and your phone will show in cmd. You need to use fastboot commands while booted to bootloader.

xunholyx said:
You're using the wrong command.
You can't use adb commands when booted to bootloader, only while booted to system, as you did the first time.
Once you do adb reboot bootloader use fastboot devices and your phone will show in cmd. You need to use fastboot commands while booted to bootloader.
Click to expand...
Click to collapse
Wow that was so simple...... (face palm)
You are a saint haha. Thank you very much that was getting to me. It did show up was able to flash twrp.
No where did I see anything about typing fastboot in cmd instead of adb while phone was in fastboot. Well it might of and I might of just not of understood it when I read it. Again thank you I appreciate it

Fastboot commands not recognized

A little background info...
I bought a used Nexus 5x and received it running the stock rom with the bootloader unlocked. Not sure if the device was properly unrooted and returned to stock. It was running 7.1.2 out of the box. Also, I took the latest security update a few days ago, before attempting to root. I wanted to do some homework on the device before attempting root. It's been a while since I rooted a device. And wanted to refresh my memory.
When I began the process, I was having trouble getting my windows 7 PC (64) to recognize the device via adb. I did a little reading and found out my driver's needed to be updated. After I updated them the device could now be recognized in adb (yes, I did remember to enable USB debugging). Verified working by returning serial number after typing the adb devices command. So I was confident I could no proceed with flashing TWRP via fastboot.
The problem...
So now that I verified adb working and talking to my device I then typed adb reboot bootloader to access the bootloader (cause I honestly didn't want to disconnect the device and have to press buttons). The device successfully booted into the bootloader. My next step was to type fastboot devices in the command line but this is where the problem I'm having is. The device is not recognized. So I unplugged the device from the PC, opened a new command window in the platform-tools folder where fastboot resides, rebooted the device back into the bootloader, reconnected the device to the PC and attempted the fastboot devices command again and nothing, no device. I execute the command fastboot flash recovery TWRP.xx.xxxx.img and the command window says waiting for device or something like that. I am not sure what steps to take next. I've never had a problem getting a PC to recognize a device in bootloader mode before. I am pretty sure my environments are set up correctly. Is it something with the device? Is there a way to correct this? I'm really lost as to what to do here. I cannot root because I cannot flash custom recovery because I cannot get my PC to recognize the device in fastboot. Please, any help is appreciated. I'm stumped.
Update.
Resolved. Used a different pc with a fresh adb environment. Worked on the first try to flash twrp and super su.

ADB command not recognized
Hi there, i'm facing a similar problem. My 5x went into bootloop. It was on stock. After going through XDA posts, I was preparing to flash stock rom once again to see if that works. So I installed in my Windows 10 - SDK tools / platform. We I used command for ADB the command prompt say device listed, but does not come up with serial number. But when fastboot command is given, it returns with a serial number.
My question is what went wrong? My PC also dose not shows 5x in the explorer, despite installing drivers.
I would also like to know how to enable USB debugging when your phone is bricked?
Looking forward to any suggestions.....thanks upfront....