Nexus 5 doesn't recognize computer while in fastboot - Nexus 5 Q&A, Help & Troubleshooting

I'm trying to flash TWRP on a nexus 5. Bootloader is already unlocked. USB debugging is enabled. The command "adb reboot-bootloader" works when the device is on. While in fastboot it does not say USB is connected and doesn't show up on adb devices. (My laptop is currently running Elementary OS)

As soon as you're in bootloader mode you have to use 'fastboot flash recovery recovery.img' adb is used when the device is powered on and in debugging mode - but it's not the right command for flashing [emoji14]

experience7 said:
As soon as you're in bootloader mode you have to use 'fastboot flash recovery recovery.img' adb is used when the device is powered on and in debugging mode - but it's not the right command for flashing [emoji14]
Click to expand...
Click to collapse
Yeah I know HOW to flash a recovery I already tried that exact command. Thanks for the suggestion though. The problem is that it just doesn't know its there.
Sent from my HTC One using XDA Free mobile app

While in bootloader mode (not recovery!) connect your phone and try "fastboot devices". What does it show? Post a screenshot of your command prompt.

Sorry its my friend's phone so I don't have it with me. I will have to get back to you on that

1. USB Debugging ONLY applies to ADB while booted into Android, NOT the bootloader or recovery
2. ADB is only used within Android (with USB Debugging enabled) and recovery, NOT the bootloader
3. Fastboot is whats used while in the bootloader, not ADB (use fastboot devices, not adb devices)
4. Some people find you may need to use 'sudo' for fastboot commands

Related

Fastboot Commands Don't Work

I am trying to unroot and re-lock my xoom and everytime I try to use a fastboot command all I get at the command promt is "waiting for device". I have installed the moto drivers and adb is working fine, just no fastboot. Please help... Thanks in advance!
did you reboot your xoom into bootloader mode? (adb reboot bootloader)
does it show any devices when you type
adb devices
Yes,
adb devices returns the attached device with the serial number.
adb reboot bootloader reboots the device and it say starting fastboot protocol at the top. then when I try to use fastboot flash boot boot.img or any other fastboot command all it does is say waiting for device and that's it..
usb debugging is on? should be if you see the device with adb devices
try to flash another cwm - like rogue version
if you do that - same error?
./adb reboot bootloader
./fastboot flash recovery recoveryroguecwm.img (change real filename )
well, usb-debugging has no effect whatsoever on fastboot.
personally, I suspect a problem outside of the xoom. Have you installed the current motorola drivers using driverhelper? If not, please do so. Please make sure any firewall or anti-virus-software on your computer is disabled or uninstalled.
If you have the possibility, you should try fastboot with another computer.
btw: I'd try if fastboot works with the command fastboot devices. This should return a list of connected and detected devices.
Thanks! For some odd reason my driver needed to be re=installed. After I did that a restarted my computer everything works as it hasin the past!

[Q] PC won't recognise phone, but Moto Tool will

I need to restore to stock firmware to get Lollipop, but adb won't recognise my phone in cmd, thus I can't follow this guide: http://forum.xda-developers.com/showthread.php?t=2542219 . I installed the Motorola Drivers from here: http://forum.xda-developers.com/showthread.php?t=2550635 , and I have the Motorola Device Manager installed. MotoTool picks up my device and is able to boot it into fastboot and install CWM or TWRP, but when I try to flash stock recovery using MotoTool it either gives me a 'no command' screen or doesn't work at all. Anyone having the same problem/know how to fix this? I'm on the Moto G 2013 XT1032 British retail.
EDIT: I fixed it! I replaced Moto Tool's stock recovery with the one that was included in here: http://forum.xda-developers.com/show...3#post54872143 then used Moto Tool to flash it, as that recognised my phone. I could then download the OTA as normal and installed it like a regular update. Enjoying Lollipop!
If the phone is in fastboot mode, try using fastboot commands on your computer. At the command prompt, type fastboot devices to see of your phone's serial # appears.
Do you have USB debugging enabled in settings?
Are you opening cmd in the directory where fastboot and adb were installed?
Are you sure you installed adb and fastboot correctly?
audit13 said:
If the phone is in fastboot mode, try using fastboot commands on your computer. At the command prompt, type fastboot devices to see of your phone's serial # appears.
Click to expand...
Click to collapse
SammyP6 said:
Do you have USB debugging enabled in settings?
Are you opening cmd in the directory where fastboot and adb were installed?
Are you sure you installed adb and fastboot correctly?
Click to expand...
Click to collapse
Yes to both of these, I was in fastboot and 'adb devices' came back with nothing even though I was in the directory where adb and fastboot were installed and the phone had USB debugging enabled. I fixed it a different way though, I replaced Moto Tool's stock recovery with the one that was included in here: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143 then used Moto Tool to flash it as that recognised my phone. I could then download the OTA as normal and installed it like a regular update.
Adb commands won't work when the phone is in fastboot mode from what I have seen.
audit13 said:
Adb commands won't work when the phone is in fastboot mode from what I have seen.
Click to expand...
Click to collapse
They didn't work at all, no matter what mode I was in. All sorted now though.
Fithboy said:
They didn't work at all, no matter what mode I was in. All sorted now though.
Click to expand...
Click to collapse
It's great you that got the issue sorted out.
Post your solution in case it may help other users down the road. Thanks.

[Q] ADB not showing device while in bootloader

Hello guys. I have HTC Sensation, Bootloader unlocked, S-ON, HBOOT-1.27.0000
Yesterday I tried to flash TWRP using fastboot. I have downloaded ADB drivers and also HTC drivers. Connected device and everything was working good. ADB showed my device serial number (or what it is, I don't remember) when I type "adb devices" in command. Then I typed "cd Downloads" to point to download directory (this is where I have twrp.img) and at least "adb reboot bootloader" . Device rebooted into bootloader, but, suddenly, popup appeared on my laptop, it was saying "USB device not recognized". I have closed it and go into command, I typed "adb devices" again, but it didn't show anything at this time. Then I run command "fastboot flash recovery twrp.img" and it returned "Waiting for device...".
After no luck., I have tried to install twrp.img though Flashify. It successfully flashed. I go into recovery, make a backup, perform clean wipe and tried to flash CM12. But it didn't flash. Then I go to restore tab but I can't see my backup. So, TWRP is not flashing anything, I have even tried stock ROM, also it's not backing up things. So now, I'm in bootloop, no OS is installed on my sensation and every time I boot up device, it automatically going into recovery.
I have laptop running Windows 10. I want to make ADB working in bootloader mode or make TWRP working to flash something.
Thanks in advance.
DroidTwe4kz said:
Hello guys. I have HTC Sensation, Bootloader unlocked, S-ON, HBOOT-1.27.0000
Yesterday I tried to flash TWRP using fastboot. I have downloaded ADB drivers and also HTC drivers. Connected device and everything was working good. ADB showed my device serial number (or what it is, I don't remember) when I type "adb devices" in command. Then I typed "cd Downloads" to point to download directory (this is where I have twrp.img) and at least "adb reboot bootloader" . Device rebooted into bootloader, but, suddenly, popup appeared on my laptop, it was saying "USB device not recognized". I have closed it and go into command, I typed "adb devices" again, but it didn't show anything at this time. Then I run command "fastboot flash recovery twrp.img" and it returned "Waiting for device...".
After no luck., I have tried to install twrp.img though Flashify. It successfully flashed. I go into recovery, make a backup, perform clean wipe and tried to flash CM12. But it didn't flash. Then I go to restore tab but I can't see my backup. So, TWRP is not flashing anything, I have even tried stock ROM, also it's not backing up things. So now, I'm in bootloop, no OS is installed on my sensation and every time I boot up device, it automatically going into recovery.
I have laptop running Windows 10. I want to make ADB working in bootloader mode or make TWRP working to flash something.
Thanks in advance.
Click to expand...
Click to collapse
adb doesn't work in bootloader, only fastboot
when you enter in bootlaoder choose fastboot
in the hboot screen you will see fastboot usb
then you can use any fastboot command
i suggest to change the recovery to 4ext
http://d-h.st/rG7
extract the recovery.img and flash it via fastboot command
then before flashing the new rom from 4ext enable smartflash from it(because you are on S-ON)
rzr86 said:
adb doesn't work in bootloader, only fastboot
when you enter in bootlaoder choose fastboot
in the hboot screen you will see fastboot usb
then you can use any fastboot command
i suggest to change the recovery to 4ext
http://d-h.st/rG7
extract the recovery.img and flash it via fastboot command
then before flashing the new rom from 4ext enable smartflash from it(because you are on S-ON)
Click to expand...
Click to collapse
It doesn't even works in fastboot too :/ So I can't use any fastboot command
DroidTwe4kz said:
It doesn't even works in fastboot too :/ So I can't use any fastboot command
Click to expand...
Click to collapse
Probably win 10 is the issue
rzr86 said:
Probably win 10 is the issue
Click to expand...
Click to collapse
Drivers and SDK is compatible with Windwos 10. I don't think it's the problem, but thanks anyways.
DroidTwe4kz said:
Drivers and SDK is compatible with Windwos 10. I don't think it's the problem, but thanks anyways.
Click to expand...
Click to collapse
use usb 2.0 ports not 3.0
if nothing works then a ruu.exe to return back to stock
http://forum.xda-developers.com/showthread.php?t=1672425
by the way did you enable usb debugging mode from settings?
rzr86 said:
use usb 2.0 ports not 3.0
if nothing works then a ruu.exe to return back to stock
http://forum.xda-developers.com/showthread.php?t=1672425
by the way did you enable usb debugging mode from settings?
Click to expand...
Click to collapse
OK thanks, I'll try them.
Well, I'm not that much noob USB Debugging is enabled.

TWRP recovery menu not showing

hi, im new in this android arena and this is my first time using smartphone so please forgive my noobness.
i want to root my phone Xiaomi Redmi 5A and i follow some tutorial on youtube where he told to use Minimal ADB & fastboot, TWRP, lazyflasher noverity and lastly Magisk.
im flashing my phone using this command on ADB:
fastboot devices
fastboot flash recovery twrp.img
fastboot reboot
i guess this is it so im rebooting my phone to get into twrp recovery mode by pressing volume up+power but it showed xiaomi stock recovery instead not twrp recovery.
so what i do wrong that i cannot get into twrp recovery menu?
please help me
Don't type fastboot reboot command after flashing, reboot to recovery manually
StillrunsKK said:
Don't type fastboot reboot command after flashing, reboot to recovery manually
Click to expand...
Click to collapse
i type that command after the first try not working (without fastboot reboot command)
it still gave me the same problem even not typing fastboot reboot command
Is the TWRP flash successful?
Ensure that your mobile drivers are installed properly on your pc and that you've enabled USB debugging.
Now after connecting your device to the computer :
1)open adb
2)type adb devices, if it shows a serial number then proceed
3)adb reboot bootloader
4)fastboot flash recovery xxxx.img
After this, remove the USB and reboot to recovery by Holding the appropriate combination of keys.
If you reboot your device first, and then power off and reboot to recovery, you will still get stock recovery.
StillrunsKK said:
Is the TWRP flash successful?
Ensure that your mobile drivers are installed properly on your pc and that you've enabled USB debugging.
Now after connecting your device to the computer :
1)open adb
2)type adb devices, if it shows a serial number then proceed
3)adb reboot bootloader
4)fastboot flash recovery xxxx.img
After this, remove the USB and reboot to recovery by Holding the appropriate combination of keys.
If you reboot your device first, and then power off and reboot to recovery, you will still get stock recovery.
Click to expand...
Click to collapse
Ensure that your mobile drivers are installed properly
Click to expand...
Click to collapse
i dont know where to find this drivers
i've enable the usb debugging
and while flashing it didn't gave any error
im using adb from this thread https://forum.xda-developers.com/showthread.php?t=2317790
where it didn't show any devices when typing adb devices but it showed my devices when typing fastboot devices

Can't unlock oem bootloader on Oneplus 6 (Fixed)

Hey guys, as stated in the title i am unable to unlock my bootloader. The adb devices works up to the point where i boot into fastboot or recovery then it stops working. If i use the command it just says "waiting for any device" I want to install TWRP and change to LineageOS but the bootloader is bottlenecking me hard... any tips would be much appreciated!
Run
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
If this doesn't fix your issue then on Windows PC install the "Android USB Driver" suitable for the phone provided by OEM / Carrier.
jwoegerbauer said:
Run
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
If this doesn't fix your issue then on Windows PC install the "Android USB Driver" suitable for the phone provided by OEM / Carrier.
Click to expand...
Click to collapse
Thank you for your response, found the problem. It was the Qualcom drivers not being signed so after i put test mode on on PC it worked. Thanks for the advice!

Categories

Resources