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

[Q] fastboot drivers

I'm a need of help here. I've been searching around the web and here to find the answer that for some reason I can't find. When I connect Kindle Fire 2 using a fastboot cable the device that comes up in Device Manager is otter2-prod-04. I've tried to install drivers manually using "Have a Disk" method but adb would not communicate with device (adb devices doesn't return a value). I don't know if the android_winusb.inf has to be edited (it only seems to be the case with first gen kindle) but I haven't found any guides that tell you to do it for Kindle Fire 2. Any help or proper direction is appreciated.

Resolver1 said:
I'm a need of help here. I've been searching around the web and here to find the answer that for some reason I can't find. When I connect Kindle Fire 2 using a fastboot cable the device that comes up in Device Manager is otter2-prod-04. I've tried to install drivers manually using "Have a Disk" method but adb would not communicate with device (adb devices doesn't return a value). I don't know if the android_winusb.inf has to be edited (it only seems to be the case with first gen kindle) but I haven't found any guides that tell you to do it for Kindle Fire 2. Any help or proper direction is appreciated.
Click to expand...
Click to collapse
Have you ran a fastboot cmd? ADB and fastboot are totally separate from one another. Try running: fastboot -i 0x1949 getvar product
That will give you the product id while in fastboot.

onemeila said:
Have you ran a fastboot cmd? ADB and fastboot are totally separate from one another. Try running: fastboot -i 0x1949 getvar product
That will give you the product id while in fastboot.
Click to expand...
Click to collapse
Hmm that did help. I should make a noob friendly guide because all of these guides are so vague when it comes to fastboot.

fast boot commands not functioning, adb works fine
onemeila said:
Have you ran a fastboot cmd? ADB and fastboot are totally separate from one another. Try running: fastboot -i 0x1949 getvar product
That will give you the product id while in fastboot.
Click to expand...
Click to collapse
when i issue this command all it does is sit with < waiting for device >
adb works fine, but not fastboot. fastboot devices returns nothing.
I have a factory cable that does boot it it fastboot screen.

lgweaver said:
when i issue this command all it does is sit with < waiting for device >
adb works fine, but not fastboot. fastboot devices returns nothing.
I have a factory cable that does boot it it fastboot screen.
Click to expand...
Click to collapse
Then you have a driver issue. Get the device into fastboot and with it plugged in go to your device manager and right click the device that shows up(it will probably have a yellow triangle next to it. Then select update driver, then choose "browse my computer for device software", lastly choose "let me pick from a list of device drivers on my computer". Since you have adb working then you should have one that says "adb composite interface" or something like that. Once you install the driver you should be ok.

onemeila said:
Then you have a driver issue. Get the device into fastboot and with it plugged in go to your device manager and right click the device that shows up(it will probably have a yellow triangle next to it. Then select update driver, then choose "browse my computer for device software", lastly choose "let me pick from a list of device drivers on my computer". Since you have adb working then you should have one that says "adb composite interface" or something like that. Once you install the driver you should be ok.
Click to expand...
Click to collapse
Found those steps. but that driver was already installed and said it was functioning. I risked it and attempted the root and install of jellybean without the fastboot command showing devices. apparently it works. my Kindle fire 2 is running cyanogen mod without issue now.
thanks for the response.

[Q] unlock bootloader prompt will not appear

When going through the adb commands and i type in fastboot oem unlock the command window says waiting for device but on the device nothing at all happens. Ive tried doing it in mtp and ptp modes but still nothing happens. device has never been rooted or unlocked before. On marshmallow and latest june security patch, please help

Wetbreadguy said:
tried doing it in mtp and ptp modes
Click to expand...
Click to collapse
It can only work in fastboot mode (when off press power+vol.dn).
The fastboot devices command must return your N7's serial number. If not, run it as root/admin and/or install a new driver and fastboot app or use NRT.

k23m said:
It can only work in fastboot mode (when off press power+vol.dn).
The fastboot devices command must return your N7's serial number. If not, run it as root/admin and/or install a new driver and fastboot app or use NRT.
Click to expand...
Click to collapse
I do have it in fastboot mode when i run the commands, i just originally set it in mtp or ptp modes.

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.

Bootloop issue with boot reason

hello there, I'm currently using one plus 7 T, I don't know why , but after updating the last software update my device stuck in Boot loop, i can't able to turn it on, The boot reason says that : Init_user0_Failed . Unable to parse kernel log.Could you please help me to get out from this issue. As i'm outstation from the city, so i can't able to reach the service center. I need my data so i'm trusting you that you guys will sort out the issue, Thank you so much for reading this.

"fastboot set_active other" to switch slot

I'm facing the same problem. Please find a workable solution asap. I'll thank endlessly.

HueyT said:
"fastboot set_active other" to switch slot
Click to expand...
Click to collapse
How and where do I do this?

kiranlalge said:
How and where do I do this?
Click to expand...
Click to collapse
In bootloader mode (check YouTube for how to boot into bootloader or fastboot mode for OnePlus 7t)

HueyT said:
In bootloader mode (check YouTube for how to boot into bootloader or fastboot mode for OnePlus 7t)
Click to expand...
Click to collapse
"fastboot set_active other" to switch slot
It looks like the above needs to be typed in somewhere. Because I do not see any typing option on any of the screens the device shows in this situation.
Please help further. I'm not sure if the developer of the given ROM is reading my posts. I'm very hopeful on him to resolve my issue. Fingers crossed.

kiranlalge said:
"fastboot set_active other" to switch slot
It looks like the above needs to be typed in somewhere. Because I do not see any typing option on any of the screens the device shows in this situation.
Please help further. I'm not sure if the developer of the given ROM is reading my posts. I'm very hopeful on him to resolve my issue. Fingers crossed.
Click to expand...
Click to collapse
Plug phone into windows laptop with adb installed on laptop:
[Download] ADB Installer v1.4.3 - Drivers, ADB and Fastboot Tools
Install drivers, ADB and fastboot tools with one single installer.Advertisement What’s ADB Installer v1.4.3 This package includes all required drivers for Android: ADB drivers (Android Debug Bridge), Fastboot and Google USB-drivers. Very easy to install. Features: Small size. Fast installation...
xiaomifirmware.com

I installed the ADB driver , now what ?? Will this erase my phone's data ?

Hi:
I'm with the same problem here, and i'm trying the "fastboot set_active other" command, but it returns me: "waiting for any device".
How can I proceed to make the phone recognized by the PC?

Zesotar said:
Hi:
I'm with the same problem here, and i'm trying the "fastboot set_active other" command, but it returns me: "waiting for any device".
How can I proceed to make the phone recognized by the PC?
Click to expand...
Click to collapse
15 min adb fastboot drivers, OnePlus USB drivers, Qualcomm USB 9008 drivers (msmtool)

ashuetrx said:
I installed the ADB driver , now what ?? Will this erase my phone's data ?
Click to expand...
Click to collapse
Enable "USB debugging" in Dev.Options, Boot into fastboot mode on phone, type "fastboot devices" and it should give you a code--then your phone is ready for fastboot flashing files

Tried in another computer with Windows 10. It returns: "Slot change is not allowed in Lock State"
I get the a code with the fastboot devices, so it seems the phone is ready.

Finally used MSM tool. I lost all my photoss but I recovered the phone.
Thanks for all the help!

Zesotar said:
Finally used MSM tool. I lost all my photoss but I recovered the phone.
Thanks for all the help!
Click to expand...
Click to collapse
how exactly did you do it with MSM tool?

cromedo7 said:
how exactly did you do it with MSM tool?
Click to expand...
Click to collapse
5 seconds with Google.
Fastboot method is much easier and without data loss.
Download
https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
Reboot to fastboot mode
Start minimal ADB and fastboot
Type: fastboot devices
If you see device and something like that:1S67gz everything's ok.
Now type: fastboot set_active other
Type reboot.
Done