I also cannot get into ADB. I type adb devices and it doesn't list my device. fastboot devices does list it.
No matter if my phone is in "Fastboot" or "HBOOT" its the same outcome.
In addition, USB debugigng and ADB network is enabled.
I have even reinstalled the HTC drivers and rebooted the phone several times and such.
I maybe wrong, adb will not work in fastboot or hboot mode. It works when you are in recovery or when you are at desktop.
Related
adb devices returns no listed devices,
One_X_All-In-One_Kit says device not found.
Tested with different drivers (HTC drivers from One_X_All-In-One_Kit,and Universal_Naked_Driver_0.72), phone is detected by Windows, in bootloader it says fastboot usb, but I can't do sh*t And it used to work just fine a month ago.
Tested on 2 different computers with different USB cables... (Win 7 and 8 run as admin).
One strange thing is that I remember updating TWRP to 2.6.0.0 and now it's 2.4.something. What happened, what can I do?
Just want to update boot.img so I can install CM10.2, currently on CM10.1.
No ideas?
I can connect adb over WiFi, but ofcourse it says offline.
USB debugging ticked?
A
Adb doesn't work in the bootloader. Only fastboot commands
Iceax123 said:
USB debugging ticked?
A
Click to expand...
Click to collapse
Yes, I did this a few times before, I know how to do it. But now, there is no way to flash boot.img from PC.
I reboot phone in to Bootloader, connect it to PC (phone says fastboot USB), I can see ADB device in device manager, if I 'adb device' in Command Prompt there are none (except when I connect it with WiFi adb).
kbal said:
Yes, I did this a few times before, I know how to do it. But now, there is no way to flash boot.img from PC.
I reboot phone in to Bootloader, connect it to PC (phone says fastboot USB), I can see ADB device in device manager, if I 'adb device' in Command Prompt there are none (except when I connect it with WiFi adb).
Click to expand...
Click to collapse
adb does not work in bootloader...
of that doesnt help, try another USB port... I know this sounds ridiculous but trust me, it helped me once before.
Well, i managed to get my phone be detected in adb and fastboot, by manually installing Nexus adb drivers (have a disk option).
Drivers that used to work- HTC drivers, won't do anymore. Don't know why.
My Verizon variant phone is in a bootloop and i cant use any adb/fastboot commands. On top of it, I cant mannually reboot to bootloader. Only thing I've seen that has hope is that with the phone powered off and with the usb cord connected to pc. If i run adb devices. I get the serial number and the status as recovery not device as it would be in full boot mode in adb. Ive never seen this before nor do I know what commands I can run or which ones I should. Anyone with any knowledge of what i can run with adb in recovery status under adb devices phone powered off , but charging thru pc by the usb.
Casetheace said:
My Verizon variant phone is in a bootloop and i cant use any adb/fastboot commands. On top of it, I cant mannually reboot to bootloader. Only thing I've seen that has hope is that with the phone powered off and with the usb cord connected to pc. If i run adb devices. I get the serial number and the status as recovery not device as it would be in full boot mode in adb. Ive never seen this before nor do I know what commands I can run or which ones I should. Anyone with any knowledge of what i can run with adb in recovery status under adb devices phone powered off , but charging thru pc by the usb.
Click to expand...
Click to collapse
adb reboot bootloader
then fastboot commands after that
It should work if adb devices returns your serial#
Hey,
trying to flash the preview. Enabled adb in dev. settings and when the watch is normally powered on i see my watch in adb devices. However, after typing adb reboot bootloader and being in fastboot mode, it doesnt find my device.
Short said: PC recognizes watch on adb, but not on fastboot in fastboot mode, have tried many adb versions etc. but didnt help.
It also says in device-manager "Android", with a yellow triangle when being in bootloader/fastboot mode.
Cables are ok!!
Thanks for any help!
You need drivers to be installed.
Mike
Michael1200 said:
Hey,
trying to flash the preview. Enabled adb in dev. settings and when the watch is normally powered on i see my watch in adb devices. However, after typing adb reboot bootloader and being in fastboot mode, it doesnt find my device.
Short said: PC recognizes watch on adb, but not on fastboot in fastboot mode, have tried many adb versions etc. but didnt help.
It also says in device-manager "Android", with a yellow triangle when being in bootloader/fastboot mode.
Cables are ok!!
Thanks for any help!
Click to expand...
Click to collapse
If you just type "flash-all.bat" (no quotes) and hit Enter it should still work. It does for me.
Hi.
Got a problem here I can't solve on my own.
QFIL-flashed a stock rom (tried to fix the blue screen on boot-thing) and was thinking it should be a breeze to unlock the bootloader and so on. But nope.
I have:
* Adb and fastboot installed
* The ZUK USB-drivers (yes, have turned off the option for windows to require signed drivers)
* Tried different USB-ports. Even another computer
* Other drivers, such as the "mi flash" drivers, universal ADB-drivers, naked ADB-drivers...
I have enabled USB-debugging, and when I write adb devices (when the phone is in android), the device is shown.
Then I use the "adb reboot bootloader" fo get into fastboot. The phone says fastboot_mode, but when I try to find the device via "fastboot devices", it's not shown.
In windows device manager the driver is OK, and shown as "ShenQI Composite ADB Interface".
Any clue what's wrong?
Well, I used the "tool all in one", and now it works....from that program. But still no devices in fastboot devices when I check manually....
I am trying to root my Redmi Note 8. When the phone is on, adb works perfectly and recognise the device. I can even reboot device when the phone is unlocked. But once I go into Fastboot/Recovery mode then ADB fails to find the device and no commands work(.To the best of my knowledge, I have all the necessary drivers. I have tried multiple USB slots, multiple computers (Windows 7 sp1 and Windows 10 latest update), and have searched all around the internet and various forums on XDA for an answer. I've tried manually updating the USB drivers through device manager, installed universal usb driver, but that did nothing. What I don't understand is that how ADB works when the device is on but don't work when it's in Recovery/Fastboot mode. I would have post images to clear things but the site is not letting me to post images
tldr: adb recognize phone when it's on but Adb don't work in fastboot/recovery mode
Thanks in advance for any help, I've tried everything I can think of.
Replace adb by fastboot in fastboot mode
ex instead of
adb reboot
type
fastboot reboot
You've to use the fastboot command instead of adb. Please note that fastboot doesn't have all adb features, e.g. install, shell, etc
[email protected] said:
I am trying to root my Redmi Note 8. When the phone is on, adb works perfectly and recognise the device. I can even reboot device when the phone is unlocked. But once I go into Fastboot/Recovery mode then ADB fails to find the device and no commands work(.To the best of my knowledge, I have all the necessary drivers. I have tried multiple USB slots, multiple computers (Windows 7 sp1 and Windows 10 latest update), and have searched all around the internet and various forums on XDA for an answer. I've tried manually updating the USB drivers through device manager, installed universal usb driver, but that did nothing. What I don't understand is that how ADB works when the device is on but don't work when it's in Recovery/Fastboot mode. I would have post images to clear things but the site is not letting me to post images
tldr: adb recognize phone when it's on but Adb don't work in fastboot/recovery mode
Thanks in advance for any help, I've tried everything I can think of.
Click to expand...
Click to collapse
adb commands only work when phone is turned on and connected to pc using ADB.. it wont work n fastboot mode. In fastboot mode the command is fastboot.
example:
in adb-> adb devices
in fastboot-> fastboot devices