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

[answer] [how to] [CDMA/LTE] How To Re-Flash Factory-Image/Recover from Soft-Brick

How To Re-Flash Stock Image
Assuming you have ADB and everything setup already....
1. I just did this for practice. I did not need to do it –but I wanted to do it successfully before I “needed” to do it. I thought I would expand a little on the process and make it a little more noob friendly.
2. Getting started.
a. Read through the entire set of instructions first.
b. I am not responsible if you BORK your phone. I BORKED mine using someone else’s instructions and tried to write a very detailed step-by-step to help others out– but it is completely possible I have also made some small error in the instructions.
3. This will completely wipe your phone – including the SD partition – so transfer any files you need before you do this.
4. This will not re-lock your bootloader. It will remain unlocked.
5. Syntax (spelling, spaces, periods, dashes, CAPITOL, or lower case) matters. There were some spelling errors and file extensions left off the commands – and that will not work.
6.I used the file…
mysid-icl53f-factory-65895fa8.tgz
…which is 4.0.2 for the cdma/lte galaxy nexus [code name = toro/mysid]. The file is located here...
http://www.google.co...NiI9yTxKdUyW1tA
7. Unzip the file (I used 7.zip to do this).
Then you will have a .tar file…
mysid-icl53f-factory-65895fa8.tar
8. Unzip that file and you should end up with a folder…
mysid-icl53f
Inside that folder you will have five files…
i. bootloader-toro-primekk15.img
ii. flash-all.sh
iii. radio-cdma-toro-i515.ek05.img
iv. radio-toro-i515.ek02.img
v. image-mysid-icl53f.zip
Do not unzip “image-mysid-icl53f.zip”
9. Go ahead and copy and paste all these files to your directory…
/android/platform-tools
(or whatever directory you work from. You do not need the “flash-all.sh” so you do not have to copy it).
10. Open the Command Prompt in the directory where you have placed the necessary files by navigating to the directory, pressing shift, and then right mouse click (normally “C: /android/tools” or C: /android/platform-tools). This will bring up the dialogue box and you can select “open a command window here”.
11. Then enter the command…
adb devices
[…this should return your serial number…]
12. enter the command…
adb reboot-bootloader
[wait for bootloader – you should here 2 alert sounds – not just 1]
13. enter the command…
fastboot flash bootloader bootloader-toro-primekk15.img
14. enter the command…
fastboot reboot-bootloader
[wait]
15. enter the command…
fastboot flash radio radio-toro-i515.ek02.img
16. enter the command…
fastboot reboot-bootloader
[wait]
17. enter the command…
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
18. enter the command…
fastboot reboot-bootloader
19. enter the command…
fastboot -w update image-mysid-icl53f.zip
20. So you know, steps 17 (flashing the cdma radio) and step 19 (flashing the update image) took longer than the rest so don't freak out - just be patient. If you did the steps in the proper order after entering the last command your phone should reboot on its own and be completely “fresh”. If you made mistakes (like I did the first time) and flashed the radios out of order (like I did) or did not wait long enough for an “Okay” dialogue (like I did) then when you reboot you will have no signal and no phone number and you will have to go through the process again and do it right (like I did).
Hope this helps someone.
Credit goes to JW at that other site for the fastboot commands. I just added detail for the write up.

Great guide, but what if the serial number doesn't show up?
Thank you for the excellent walkthrough. I am following it, but when I enter "adb devices" at the command prompt I receive "list of devices attached" but no serial number. Also, my Nexus displays: "Fastboot Command Read Error -2147483647". I did a battery pull after getting stuck in a bootloop, and am trying to recover. I can unlock and relock the bootloader, but that is the only command that is working.

Ominous39061 said:
Thank you for the excellent walkthrough. I am following it, but when I enter "adb devices" at the command prompt I receive "list of devices attached" but no serial number. Also, my Nexus displays: "Fastboot Command Read Error -2147483647". I did a battery pull after getting stuck in a bootloop, and am trying to recover. I can unlock and relock the bootloader, but that is the only command that is working.
Click to expand...
Click to collapse
if it does not return a serial number than the phone is not being recognized. I believe that there are 2 different sets of drivers that are needed. Let me look for the link and info.
the fact that it returns "list of devices attached" but no number means that it is not finding your device which means it is probably a driver issue. let me see what I can come up with. But I am no expert at any of this.

Ok - so I just did some testing of my own. I ran into the same problem as you. And I know that I have the drivers installed. So what I did was try and "shut down" any thing that could interfere with with ADB/Fastboot.
Any tethering apps that you may have - PDA NET, Easy Tether, etc, could possibly do this. Also - when you plug your phone in - and the Auto Play options pop up for FTP (File Transfer Protocol) - X out of that.
I initially plugged in my phone. Opened the command prompt in my platform-tools folder. typed in...
adb devices
...and I got the same message as you. I then "turned off" everything that could be causing problems with the process. I unplugged the phone and replugged it in (and closed the dialog box again) and then re-opened the command prompt and entered...
adb devices
...and then I got the proper return message.

thepolishguy said:
Ok - so I just did some testing of my own. I ran into the same problem as you. And I know that I have the drivers installed. So what I did was try and "shut down" any thing that could interfere with with ADB/Fastboot.
Any tethering apps that you may have - PDA NET, Easy Tether, etc, could possibly do this. Also - when you plug your phone in - and the Auto Play options pop up for FTP (File Transfer Protocol) - X out of that.
I initially plugged in my phone. Opened the command prompt in my platform-tools folder. typed in...
adb devices
...and I got the same message as you. I then "turned off" everything that could be causing problems with the process. I unplugged the phone and replugged it in (and closed the dialog box again) and then re-opened the command prompt and entered...
adb devices
...and then I got the proper return message.
Click to expand...
Click to collapse
I got the same problem with mine i dont have anything like pda net installed but nothing i have tried is able to get adb to list my phone

Getting the same issue myself...help!

Thank you so much I'm a total noob with this stuff but your guide was very helpful!

Noev said:
I got the same problem with mine i dont have anything like pda net installed but nothing i have tried is able to get adb to list my phone
Click to expand...
Click to collapse
ChuckTu said:
Getting the same issue myself...help!
Click to expand...
Click to collapse
Ok - so another member posted this...
ADB/Naked Drivers
...and I have heard some people say that it was very helpful. So hopefully this will help you guys to get your devices recognized.
Then there is also this thread and the OP said this...
Code:
On your windows PC. Use the root guide by bman
( [url]http://rootzwiki.com...nlock-and-root/[/url] )
and download the third option for drivers. Extract all
of these tho wherever you have your fast boot
( for me it was c:/users/thatmayh3mguy/) then run
fastboot in the cmd. The adbapi.DLL file will be there
and will make the fast boot work. I didn't have the sdk
installed ( fresh install of win 7 ultimate last week and
don't have it all set up yet) and it worked
thread...
adb help/getting your drivers installed correctly
OK - here is also another method that I found. I have PDA Net installed and I did not have any issues with fastboot. Here are some instructions that say the drivers that PDA Net use are the same drivers that you need for fastboot. So here is a link to the thread and hopefully one of these methods is going to work for you.
Installing PDA Net to solve your fastboot problems

ah ha - just read something else that I should have thought of...
If your phone is already in bootloader - the command...
adb devices
...will not work. so if you are in bootloader you should try the command...
fastboot devices
...instead and see if that returns anything for you.

just wanted to jump back in hear and say i was able to get mine working again. adb was allowing me to lock/unlock the bootloader i toggled that on and off then when i went to boot my phone it took a long time to boot but finally did. Thanks for all the help was in a real jam there for a minute. I used the naked adb drivers posted above not sure if that did anything but it worked for me. Thanks again!

Noev said:
just wanted to jump back in hear and say i was able to get mine working again. adb was allowing me to lock/unlock the bootloader i toggled that on and off then when i went to boot my phone it took a long time to boot but finally did. Thanks for all the help was in a real jam there for a minute. I used the naked adb drivers posted above not sure if that did anything but it worked for me. Thanks again!
Click to expand...
Click to collapse
cool. glad to hear it.

trying this with a Linux OS
So I have a Samsung Galaxy Nexus on Verizon and I put 4.0.4 (IMM30B) using the Galaxy Nexus ToolKit on Windows. Since then I've had a few issues with performance so I want to go back to stock (ICF53F) then maybe goto latest IMM76K (I think). I've retrieved the zip file from steps above and untar'd the file, but when I try to flash the boot file it just sits there waiting for device. I'm not sure what it's waiting for. I'm in fastboot mode and then plugged in the phone to the usb cord but nothing happens.
Any ideas?
UPDATE:
I figured out the issue. On a linux machine using fastboot requires super user privileges. Maybe an update to the instructions may be in order?

CMD keeps telling me waiting for device.
How long will it takes first time?
this after entering: fastboot flash bootloader bootloader-toro-primekk15.img

ladyminnie said:
CMD keeps telling me waiting for device.
How long will it takes first time?
this after entering: fastboot flash bootloader bootloader-toro-primekk15.img
Click to expand...
Click to collapse
Does "fastboot devices" return your device?
If not, you may have a driver issue.
Sent from my Galaxy Nexus using Tapatalk 2

A mistake I made a while ago, if you are sure that you have already installed ADB drivers, and your device still isn't being recognized by ADB..
Be sure USB Debugging is checked on.
Sent from my Galaxy Nexus using Tapatalk 2

adb devices returns my number from the phone
adb reboot-bootloader does bring my phone into bootloader
than it stops with the next command. I waited for 45 minutes/
---------- Post added at 07:03 PM ---------- Previous post was at 06:57 PM ----------
usb debugging was/is still on
The white small led is lightning up every 10 seconds orso

problem solved with:
http://forum.xda-developers.com/showthread.php?t=1766475

[Q] Fastboot cannot find device (Ubuntu/Win7)

Ok, I *have* searched the forums and googled this, but none of the standard solutions seem to work.
I have the Verizon HTC One and successfully ran the rumrunner S-OFF (root, unlocked, etc). Now I want to flash a recovery using fastboot, but no matter what I do, I cannot get "fastboot devices" to show anything (or I get <waiting for device> if I try anything else with fastboot). ADB works fine.
On Ubuntu 11.10:
I downloaded the back-ported android-tools (apt-get install android-tools-fastboot/adb from the ppa:nilarimogard/webupd8 repository).
I tried fastboot as root, and I also tried with a udev rule (SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", MODE="0666").
adb works fine (I used it to reboot in fastboot-usb mode)
I tried different USB ports.
On Windows 7:
I tried both fastboot from the Android SDK and from the "Minimal Tools".
ADB works fine.
I un-installed and re-installed drivers as I plugged in and unplugged my phone into the USB ports.
Note that Windows 7 does complain about the drivers and says that the device is unplugged when it isn't. It seems to timeout when trying to install drivers from the internet
I tried installing and uninstalling HTC Sync, PDANet.
I would prefer if there is a way to make it work in Ubuntu so that I can eliminate the Windows drivers from the equation. Anything obvious that I missed? Does the version of fastboot matter?
Thanks in advance for any suggestions.

neutrino37 said:
Ok, I *have* searched the forums and googled this, but none of the standard solutions seem to work.
I have the Verizon HTC One and successfully ran the rumrunner S-OFF (root, unlocked, etc). Now I want to flash a recovery using fastboot, but no matter what I do, I cannot get "fastboot devices" to show anything (or I get <waiting for device> if I try anything else with fastboot). ADB works fine.
On Ubuntu 11.10:
I downloaded the back-ported android-tools (apt-get install android-tools-fastboot/adb from the ppa:nilarimogard/webupd8 repository).
I tried fastboot as root, and I also tried with a udev rule (SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", MODE="0666").
adb works fine (I used it to reboot in fastboot-usb mode)
I tried different USB ports.
On Windows 7:
I tried both fastboot from the Android SDK and from the "Minimal Tools".
ADB works fine.
I un-installed and re-installed drivers as I plugged in and unplugged my phone into the USB ports.
Note that Windows 7 does complain about the drivers and says that the device is unplugged when it isn't. It seems to timeout when trying to install drivers from the internet
I tried installing and uninstalling HTC Sync, PDANet.
I would prefer if there is a way to make it work in Ubuntu so that I can eliminate the Windows drivers from the equation. Anything obvious that I missed? Does the version of fastboot matter?
Thanks in advance for any suggestions.
Click to expand...
Click to collapse
You can run a fastboot command from terminal emulator. If you can't find the commands, I will send them when I get to a computer tomorrow.
Sent from my One.

Do you have Fastboot turned off in system settings?
Unless I'm mistaken, you need to be sure that's switched off to utilize fastboot mode.
If it's already switched off and you are still having the issue, then ignore this post.

santod040 said:
Do you have Fastboot turned off in system settings?
Unless I'm mistaken, you need to be sure that's switched off to utilize fastboot mode.
If it's already switched off and you are still having the issue, then ignore this post.
Click to expand...
Click to collapse
I have fastboot checked in settings and fastboot commands work... When I'm in fastboot mode.
OP, I have made the simple mistake of not putting it in fastboot mode before. Were you booted into fastboot mode? I.E. reboot into bootloader, with fastboot selected hit the power button and ensure that it says deadbolt at the top? Something really simple that had tripped me up before!
Sent from my HTC6500LVW using XDA Premium 4 mobile app

This is worth a shot, as I've read in previous post. Only plug your HTC One into a usb 2.0 instead of 3.0. What does this mean? If you look inside the usb on your computer and the color you see is blue? Don't use that one. For whatever reason, when using the commands, usb 3.0 doesn't work with the HTC One. If you only have the 3.0 ports... I have nothing.

BygSii said:
This is worth a shot, as I've read in previous post. Only plug your HTC One into a usb 2.0 instead of 3.0. What does this mean? If you look inside the usb on your computer and the color you see is blue? Don't use that one. For whatever reason, when using the commands, usb 3.0 doesn't work with the HTC One. If you only have the 3.0 ports... I have nothing.
Click to expand...
Click to collapse
ADB works fine over USB 3.0 for any Android device if you have the proper drivers installed. If you have a mixture of 2.0 and 3.0 ports, as I do, use the 2.0, as it is more reliable, though slower. I'm using ADB on my device via USB 3.0 as I type this, using Windows 7 x64.
If your motherboard has an Intel chipset, you can try this method to get Fastboot working over USB 3.0, just disregard the download links about making it work on Windows 8, as the drivers were designed for Windows 7. My motherboard has an Asmedia USB 3.0 controller, and I am unable to use the Intel drivers, and thus unable to use Fastboot over USB 3.0, which isn't really a problem for me, as I also have the USB 2.0 ports.

brymaster5000 said:
You can run a fastboot command from terminal emulator. If you can't find the commands, I will send them when I get to a computer tomorrow.
Sent from my One.
Click to expand...
Click to collapse
Oh, you mean directly on the phone? Presumably one could do it from "adb shell" as well? I would be interested to know what the commands are, since typing fastboot in the terminal emulator is not recognized.
[edit]
I found this in the forums:
Code:
su
flash_image recovery path_to_recovery_image.img
I assume that is what you meant.

kdj67f said:
I have fastboot checked in settings and fastboot commands work... When I'm in fastboot mode.
OP, I have made the simple mistake of not putting it in fastboot mode before. Were you booted into fastboot mode? I.E. reboot into bootloader, with fastboot selected hit the power button and ensure that it says deadbolt at the top? Something really simple that had tripped me up before!
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So just to be patently clear. To boot into fastboot, I reboot into the bootloader with USB attached, select "fastboot", then it says "fastboot USB" and I select "Reboot", correct? I have never noticed the word "deadbolt". Is there a way to check on the phone that I've booted into fastboot?
I have been using USB 2 ports (tried different ones).
I have fast boot unchecked in my settings.

neutrino37 said:
So just to be patently clear. To boot into fastboot, I reboot into the bootloader with USB attached, select "fastboot", then it says "fastboot USB" and I select "Reboot", correct? I have never noticed the word "deadbolt". Is there a way to check on the phone that I've booted into fastboot?
I have been using USB 2 ports (tried different ones).
I have fast boot unchecked in my settings.
Click to expand...
Click to collapse
Don't click reboot once your phone says "Fastboot USB". That's where you're going wrong.
You say that ADB works on occasion. Trying downloading the newest drivers from this thread. Plug your phone in and type "adb devices". If it displays your phone's serial number and says "device" next to it, you're doing fine. Then type "adb reboot bootloader". It will bring you to where you are able to type fastboot commands. Type "fastboot devices". If it shows your device's serial number and says "fastboot" next to it, then your Fastboot commands will work properly.

neutrino37 said:
Oh, you mean directly on the phone? Presumably one could do it from "adb shell" as well? I would be interested to know what the commands are, since typing fastboot in the terminal emulator is not recognized.
[edit]
I found this in the forums:
Code:
su
flash_image recovery path_to_recovery_image.img
I assume that is what you meant.
Click to expand...
Click to collapse
Open a terminal emulator on your phone then get root access:
su
After that, cd to the location of the .img file: (i.e. if it was on the root of the sd card then...)
cd /sdcard/
Finally, flash the image to the recovery partition:
dd if=recovery.img of=/dev/block/mmcblk0p21 (not sure if this location will be different on this phone..someone else may want to chime in)
Then exit the terminal emulator and reboot.

IceDragon59 said:
Don't click reboot once your phone says "Fastboot USB". That's where you're going wrong.
You say that ADB works on occasion. Trying downloading the newest drivers from this thread. Plug your phone in and type "adb devices". If it displays your phone's serial number and says "device" next to it, you're doing fine. Then type "adb reboot bootloader". It will bring you to where you are able to type fastboot commands. Type "fastboot devices". If it shows your device's serial number and says "fastboot" next to it, then your Fastboot commands will work properly.
Click to expand...
Click to collapse
Thanks, not clicking the reboot made it work with fastboot (even in Win7!). I was confused by the statements about rebooting "into fastboot" and assuming that once it displayed "fastboot USB" I should reboot. Took me 2 seconds to install TWRP once this PEBKAC was resolved .
I would've tried the dd option from the terminal, but I'm glad I didn't have to (have used that wrong once on a Linux system and it was not pleasant!).

Glad you figured it out, even with my typo!
Sent from my HTC6500LVW using XDA Premium 4 mobile app

Commands
brymaster5000 said:
You can run a fastboot command from terminal emulator. If you can't find the commands, I will send them when I get to a computer tomorrow.
Sent from my One.
Click to expand...
Click to collapse
Hi, I have been trying to debrick my tp and I've posted in forums asking basically this question.. seems it goes fine till failed to install/find Fastboot.. would you send me the command? thanks..

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