Database Users

Cannot get past "adb devices" command line

I have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.

I believe part of the instructions are to install the Platform Tools, which should include drivers. Try running the SDK Manager and updating or installing the drivers again. Also ensure you have USB Debugging ON in your Developer settings and OEM Unlocking enabled. Lastly, tap the notification in your shade about the USB connection (I think it defaults to Charging Only) and change it to various modes. Mine seems to only work on PTP mode. When you run the adb devices command you will need to authorize the connection on the phone end the first time by clicking OK so make sure the screen is on and unlocked so you can see it.
Hope this helps.

peckaldee said:
I have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.
Click to expand...
Click to collapse
u enable OEM Unlock under developer settings?
You enable USB debugging?
Me personally do not get any strings of data returned when im on fastboot
i open CMD, run ADB DEVICES, get message saying the port is opening, and then listing devices... which is empty
but i am able to flash anything i want using fastboot....
try this command and see if it works after that... fastboot reboot-bootloader
it should reboot bootloader for u.. thats a easy way to know its responding to u

Is the device showing properly in the Device Manager when it's connected to your system?

hEaTLoE said:
Is the device showing properly in the Device Manager when it's connected to your system?
Click to expand...
Click to collapse
It shows up in windows explorer as "Nexus 6p" when I plug in the USB cable.
I have USB debugging and unlock bootloader checked in settings.
My fastboot devices command returns nothing.

peckaldee said:
It shows up in windows explorer as "Nexus 6p" when I plug in the USB cable.
I have USB debugging and unlock bootloader checked in settings.
My fastboot devices command returns nothing.
Click to expand...
Click to collapse
Did you change the USB mode? Mine shows in Explorer as you described but won't work in ADB/Fastboot until I change it to PTP.

fury683 said:
Did you change the USB mode? Mine shows in Explorer as you described but won't work in ADB/Fastboot until I change it to PTP.
Click to expand...
Click to collapse
Yeah I tried every option. Nothing.
The instructions say the fastboot devices command should return my serial number and it does not.

When booted into the bootloader one it tells me on one line phone LOCKED and on another line says download mode DISABLED.
Don't know if this has anything to do with my problems but I still cannot get a return on the fastboot devices command in order to proceed with the unlock command of "fastboot flashing unlock"

remember that u need latest fastboot for this to work.
did u updated the SDK manager to the latest? i had to do that in order to work for 6P

chaco81 said:
remember that u need latest fastboot for this to work.
did u updated the SDK manager to the latest? i had to do that in order to work for 6P
Click to expand...
Click to collapse
I'm using sdk manager revision 24.4.1

peckaldee said:
I have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.
Click to expand...
Click to collapse
I had the same issue ,it was down to when I plugged the phone into the PC for the first time,it installed the Google.USB driver ,but it didn't install the driver for the adb interface,I had to download it from Google and install it manually

I also had the same issue, I had an old Clockworkmod generic driver that I was using for my Samsung Galaxy S5 installed.
Go to Device manager (either type it in the start menu, or: right click This PC, click manage, and click device manager), plug in your unlocked Nexus 6P phone and watch for a new item to pop up. If it says android something, uninstall it. I had to uninstall 3 times, then reinstall the drivers from the SDK before it would work.

I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.

mbonus said:
I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.
Click to expand...
Click to collapse
This worked. Now my commands in terminal are working correctly. thanks all for the help

Got A device to pop up under the command adb devices, but nothing under fastboot devices. Any tips? Had to follow the skipsoft instructions to install adb/fastboot devices. Yes USB Debugging is on and the OEM unlocking is set to allow..
Christ I'm retarded. Sorry boys, thought my phone was in the bootloader when I was trying this command LOL

Same problem
peckaldee said:
When booted into the bootloader one it tells me on one line phone LOCKED and on another line says download mode DISABLED.
Don't know if this has anything to do with my problems but I still cannot get a return on the fastboot devices command in order to proceed with the unlock command of "fastboot flashing unlock"
Click to expand...
Click to collapse
I'm having the same problem. Did you ever figure out what was wrong?

mbonus said:
I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.
Click to expand...
Click to collapse
Solved my problem as well. Thanks!

complete gridlock (g903f, linux pc)

i know that it's a bit silly to create an entire thread for one guy's problem, but i am stuck and probably going to give up hope when it comes to rooting my s5 neo (again, g903f), which is running android 5.1.1.
several days worth of research have yielded nothing. i can connect to my device using mtp, and i have usb 2 and 3 ports. lsusb and adb are working for me; i have set udev rules and "adb devices" returns my phone's serial number and its status. usb debugging is enabled as is the oem unlock (though whenever i try to disable developer tools and put them on again, the gui messes itself up and it won't let me turn them off, even if i refuse to put in my device's password). that's the only success i've had.
fastboot isn't working; "fastboot devices" shows nothing and it hangs at "< waiting for device>" with other commands, such as "fastboot oem unlock". adb won't work in download mode, either - though this is expected. rebooting into download mode via adb doesn't fix my problem, nor does using "sudo" or the root account.
odin3 won't work either despite the window opening with wine; the device never shows up in download mode. heimdall also doesn't seem to detect my device - although it might just be down to my ignorance.
the usual root tools, such as srsroot and kingo don't seem to do any good, though neither worked under wine, which helps to diagnose the problem. i have no access to windows, even through vmware.
i feel like everything i do only brings me one step closer to a brick wall, which i'm hitting all the time. it's like i've been chosen to experience this. if any of you guys can help me to get this phone rooted, i'd probably scream out of sheer ecstasy. and no, "try getting a girlfriend" who has windows isn't an answer.
[insert wojak here]

Hi!
It seems a driver issue
have you used already this tool in your pc successfully or is just a problem with your S5?

Reyse said:
Hi!
It seems a driver issue
have you used already this tool in your pc successfully or is just a problem with your S5?
Click to expand...
Click to collapse
i don't think that drivers are an issue; i have linux. do i need to use kies to install them under wine? it didn't work with wine 1.8 and kies3; i'm trying wine 1.9 right now.

thefailure said:
i don't think that drivers are an issue; i have linux. do i need to use kies to install them under wine? it didn't work with wine 1.8 and kies3; i'm trying wine 1.9 right now.
Click to expand...
Click to collapse
Did you debug (adb, fastboot) another phone already or is this your first one?

[A2017G] Bootloader unlock stuck at < waiting for any device >

I'm very sorry if this problem has been raised and solved before or if this is the wrong place to ask this. My phone is currently on the b08 build and I was able to flash twrp 3.0.2-2 using this guide http://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ([GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM) which has been very helpful but I just could not get past the 15th step when unlocking the bootloader. Whenever I type in "fastboot oem unlock", all I get is < waiting for any device > and nothing else. When i tried typing "fastboot devices" I get blank as well. I've tried using different usb ports, redoing all the steps for bootloader unlock part while my phone's in twrp, killing adb.exe while the < waiting for my device > line appeared but I couldn't get past the < waiting for any device > issue. This is actually the first time I've ever attempted a bootloader unlock on any device and I'm still a complete noob when it comes to this stuff so any help will be greatly appreciated!

ileikpi said:
I'm very sorry if this problem has been raised and solved before or if this is the wrong place to ask this. My phone is currently on the b08 build and I was able to flash twrp 3.0.2-2 using this guide http://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ([GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM) which has been very helpful but I just could not get past the 15th step when unlocking the bootloader. Whenever I type in "fastboot oem unlock", all I get is < waiting for any device > and nothing else. When i tried typing "fastboot devices" I get blank as well. I've tried using different usb ports, redoing all the steps for bootloader unlock part while my phone's in twrp, killing adb.exe while the < waiting for my device > line appeared but I couldn't get past the < waiting for any device > issue. This is actually the first time I've ever attempted a bootloader unlock on any device and I'm still a complete noob when it comes to this stuff so any help will be greatly appreciated!
Click to expand...
Click to collapse
either you are not in bootloader mode on the phone or you need to fix your drivers.

This problem for me was that my phone was coming up as "android" instead of QUSB_BULK. So I used Zadig to show me all the drivers, right clicked on "Android", deleted that and the old QUSB_BULK driver, connected my phone again and then let Zadig install the missing driver again. This made my phone be seen as QUSB_BULK again and then unlocking bootloader worked for me.

I got stuck at that step as well, had to do a hard reboot, attempts at reinstalling the drivers only seemed to make it worse!

JP_93 said:
This problem for me was that my phone was coming up as "android" instead of QUSB_BULK. So I used Zadig to show me all the drivers, right clicked on "Android", deleted that and the old QUSB_BULK driver, connected my phone again and then let Zadig install the missing driver again. This made my phone be seen as QUSB_BULK again and then unlocking bootloader worked for me.
Click to expand...
Click to collapse
Thank you very much for replying to me on both threads. My phone also shows up as "Android" instead of QUSB_BULK in device manager when I reboot it into bootloader but I'm a bit confused about how you deleted "Android" and the old QUSB_BULK driver. Did you uninstall/disable "Android" in device manager or is there a way to do it in Zadig?
I tried uninstalling "Android" in device manager when in bootloader but I have no idea how to remove the old QUSB_BULK driver. I then unplugged my phone and plugged it back in but the driver Zadig installed still made it appear as "Android". Sorry, I'm still really new to all this!

ileikpi said:
Thank you very much for replying to me on both threads. My phone also shows up as "Android" instead of QUSB_BULK in device manager when I reboot it into bootloader but I'm a bit confused about how you deleted "Android" and the old QUSB_BULK driver. Did you uninstall/disable "Android" in device manager or is there a way to do it in Zadig?
I tried uninstalling "Android" in device manager when in bootloader but I have no idea how to remove the old QUSB_BULK driver. I then unplugged my phone and plugged it back in but the driver Zadig installed still made it appear as "Android". Sorry, I'm still really new to all this!
Click to expand...
Click to collapse
Sorry I don't have access to a pc atm but I'm sure I right clicked "Android" while using Zadig and it lets yoy uninstall the driver. Once that was done I unplugged my phone and plugged it back in and used Zadig to reinstall the driver for the axon. Then it showed up as QUSB_BULK again.

JP_93 said:
Sorry I don't have access to a pc atm but I'm sure I right clicked "Android" while using Zadig and it lets yoy uninstall the driver. Once that was done I unplugged my phone and plugged it back in and used Zadig to reinstall the driver for the axon. Then it showed up as QUSB_BULK again.
Click to expand...
Click to collapse
Zadig doesn't let me right click to uninstall drivers T-T. I tried reflashing twrp and redoing everything in the guide to make sure I didn't miss anything but I'm still stuck at < waiting for any device >. Unlocked bootloader seems so close yet so far... Thank you very much for your help thus far tho!

if you just connect the phone in MTP mode and you do "adb devices" is your phone showing?

Bucci83 said:
if you just connect the phone in MTP mode and you do "adb devices" is your phone showing?
Click to expand...
Click to collapse
Yep it does.

lafester said:
either you are not in bootloader mode on the phone or you need to fix your drivers.
Click to expand...
Click to collapse
I'm pretty sure I'm in bootloader. At this point I'm pretty sure my drivers are the issue but how do I fix them? When in bootloader mode, my phone just shows up as "Android" and Zadig did not help there. As I said, typing fastboot devices also show nothing. I'm probably the dumbest or the unluckiest person in here to be stuck at the same damn point for days...

ileikpi said:
I'm pretty sure I'm in bootloader. At this point I'm pretty sure my drivers are the issue but how do I fix them? When in bootloader mode, my phone just shows up as "Android" and Zadig did not help there. As I said, typing fastboot devices also show nothing. I'm probably the dumbest or the unluckiest person in here to be stuck at the same damn point for days...
Click to expand...
Click to collapse
have you tried re-installing the ZTE USB drivers?
I had some issues with the Zadig because it installed the Qualcomm drivers, but they weren't working correctly, I ended up downloading some other Qualcomm drivers and that did the trick...

Bucci83 said:
have you tried re-installing the ZTE USB drivers?
I had some issues with the Zadig because it installed the Qualcomm drivers, but they weren't working correctly, I ended up downloading some other Qualcomm drivers and that did the trick...
Click to expand...
Click to collapse
Ok I'll try that when I get home.
Sorry but may I ask if you remember what your phone was called in device manager when you rebooted it into bootloader? Was it "Android", some Qualcomm code (ie. QUSB_BULK), or ADB something? In @JP_93 and my cases, our phones were simply labelled as "Android" in device manager.

Unlocked using a different PC
Ok guys, I managed to unlock my phone using a friend's computer with no problems. The drivers in my own pc were definitely messed up and uninstalling and reinstalling them didn't work.
Thank you very much to everyone for your help and sorry if I blew this out of proportion!

Glad you got it to work!

Moto G4 seen by Windows but not by adb in fastboot mode

I'm trying to unlock the bootloader on my XT1622.
I can transfer files etc and backup when connected to PC and in Windows
I have installed the drivers and fastboot and adb and opened a cmd window in Admin mode in the directory where fastboot.exe and adb.exe are installed.
I have restarted the phone in fastboot mode (power up plus Vol Down) and connected by USB cable to my PC but when I type adb devices I get no information coming back.
Does anyone have any idea, please, where I may be going wrong?

Anyone able to help, please?
My post above is getting a number of views but sadly no replies.
Since posting I have tried different cables, different USB ports and even installed the drivers on my wife's laptop, but to the same effect - the device is seen in File Explorer but after booting into bootloader both fastboot devices and adb devices return blanks.
I think I'll just give up on the idea, which is a shame as accomplished it easily on my old Nexus tablet and on previous Moto G iterations.

actomox said:
My post above is getting a number of views but sadly no replies.
Since posting I have tried different cables, different USB ports and even installed the drivers on my wife's laptop, but to the same effect - the device is seen in File Explorer but after booting into bootloader both fastboot devices and adb devices return blanks.
I think I'll just give up on the idea, which is a shame as accomplished it easily on my old Nexus tablet and on previous Moto G iterations.
Click to expand...
Click to collapse
adb mode doesn't work when you are in the bootloader. But fastboot should. Boot into your phone and go to settings/Developer options and make sure you have OEM unlocking and Android debugging both enabled. Then on your PC connect your cable and open a command window. type the command "adb devices" and see if your phone shows up now. If so you can then boot into the bootloader via the command "adb reboot bootloader" While in the bootloader type the command "fastboot devices" and see if your phone shows up. If so you are good to go.
Oh, and I am assuming you have a non-Amazon model?

Still no show
Thanks Palmyra. I have followed those instructions to the letter.
In Developer options both OEM unlocking and USB debugging are switched on.
When I connect to the PC and run adb devices in a CMD window it first responds that daemon has been successfully started then that the list of devices is attached but it then returns me to the command prompt.
I did then try 'adb reboot bootloader' but it returned 'error: device not found' - not unexpected given the first command result.
In File Explorer however under this PC it does list Moto G(4) and I am able to explore the phone contents there.
It is not an Amazon model.
I really am at a loss to understand why this is happening.
pastorbob62 said:
adb mode doesn't work when you are in the bootloader. But fastboot should. Boot into your phone and go to settings/Developer options and make sure you have OEM unlocking and Android debugging both enabled. Then on your PC connect your cable and open a command window. type the command "adb devices" and see if your phone shows up now. If so you can then boot into the bootloader via the command "adb reboot bootloader" While in the bootloader type the command "fastboot devices" and see if your phone shows up. If so you are good to go.
Oh, and I am assuming you have a non-Amazon model?
Click to expand...
Click to collapse

actomox said:
Thanks Palmyra. I have followed those instructions to the letter.
In Developer options both OEM unlocking and USB debugging are switched on.
When I connect to the PC and run adb devices in a CMD window it first responds that daemon has been successfully started then that the list of devices is attached but it then returns me to the command prompt.
I did then try 'adb reboot bootloader' but it returned 'error: device not found' - not unexpected given the first command result.
In File Explorer however under this PC it does list Moto G(4) and I am able to explore the phone contents there.
It is not an Amazon model.
I really am at a loss to understand why this is happening.
Click to expand...
Click to collapse
Have you installed Motorola Device Manager? I had your same issue until I had installed the Motorola drivers.

Still no joy
negusp said:
Have you installed Motorola Device Manager? I had your same issue until I had installed the Motorola drivers.
Click to expand...
Click to collapse
Thanks. Yes, I have installed Motorola Device Manager. In Windows Device Manager the MotoG4 shows under Portable Devices only when USB set to Charging or File Transfer and as an Android device with Motorola Device Manager when connected as PTP. The situation has persisted since updating to Nougat and 'adb devices' draws a blank no matter which USB connection mode I use.

actomox said:
Thanks. Yes, I have installed Motorola Device Manager. In Windows Device Manager the MotoG4 shows under Portable Devices only when USB set to Charging or File Transfer and as an Android device with Motorola Device Manager when connected as PTP. The situation has persisted since updating to Nougat and 'adb devices' draws a blank no matter which USB connection mode I use.
Click to expand...
Click to collapse
Did an RSA key dialogue ever pop up when you plugged it into your PC?
If fastboot shows no devices when your phone is in fastboot mode (voldown+power hold), then something is seriously off. Have you tried multiple USB cables?
On your wife's PC did you make sure to install adb/fastboot and drivers: https://forum.xda-developers.com/showthread.php?t=2588979
And make sure to run the cmd shell as administrator/root? (right click cmd, click run as admin)

Will double check everything
Will double check all of those pointers over the weekend and report back. Thanks

Success at last
Went onto my wife's computer and deleted all that I could find relating to SDK and Motorola. Re-installed adb tools and the Motorola drivers and now adb devices return the details of the connected phone. Onto the next stage of unlocking the bootloader and then rooting. Thanks for the help.

Fastboot not finding device

Hey, I just bought an S7 Edge SM-G950U, the att&t version, SM-G950A. I heard some say that it's not possible to unlock its bootloader, but the OEM unlock option turned out to be available in developer options. However, I'm having a hard time properly installing its drivers, whichever adb driver I use, the driver still shows a yellow warning and the error is that the device can't be started. The device shows up with adb devices when the device is on, but it doesn't neither with fastboot devices nor adb devices when it's in download mode. I'm trying to install TWRP, the hero 2 version. Any help would be appreciated. Thanks in advance

If you in Windows Device Manager find any device with yellow mark right on the device, then the driver installed for it isn't suitable: uninstall it, get Samsung USB Driver and install it.
Samsung devices don't know of a Fastboot mode: there it's called Download mode. You can't run any Fastboot command in this mode.
ADB operates on Android OS, not on device's bootloader, hence it's not working when running the device in Download mode.

Thanks for the prompt reply. I used a different laptop and managed to install the drivers properly, no warnings. However, the result is the same. You mention how I can't run fastboot commands in Download mode, where can I run them? Only Odin is working in that mode now, but I gotta try to unlock the bootloader. A lot of people are saying that this model can't be unlocked, even though the OEM unlock checkbook in the Developer settings is there. Any advice is appreciated

Up

Gearninja said:
Up
Click to expand...
Click to collapse
Down