Develop Bugs

[Q] ADB not working, Fastboot does.

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.

device not found

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.

[Q] adb shell returning device offline

I have all the JDK and Android SDK components installed on my Windows 7 box. I have enabled USB Debugging and when I try to run adb shell I get the following error:
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb shell
error: device offline
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb devices
List of devices attached
5099ba28 offline
Shows the device attached to my PC.
I have killed and restarted the adb server, rebooted my phone, no luck.
I have never had a problem before with adb. Do you need to use the USB 3.0 cord that was included with the Note 3 or will a regular mico USB work?

stevetrooper said:
I have all the JDK and Android SDK components installed on my Windows 7 box. I have enabled USB Debugging and when I try to run adb shell I get the following error:
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb shell
error: device offline
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb devices
List of devices attached
5099ba28 offline
Shows the device attached to my PC.
I have killed and restarted the adb server, rebooted my phone, no luck.
I have never had a problem before with adb. Do you need to use the USB 3.0 cord that was included with the Note 3 or will a regular mico USB work?
Click to expand...
Click to collapse
regular should work. That is just the data transfer speed.
Have you tried this? http://forum.xda-developers.com/showthread.php?t=2247471

Figured out the problem, I needed to upgrade my adb to the latest version (1.0.31). When I ran the adb shell, a pop-up window appeared on the Note 3 and I confirmed. Now I am able to access.

stevetrooper said:
Figured out the problem, I needed to upgrade my adb to the latest version (1.0.31). When I ran the adb shell, a pop-up window appeared on the Note 3 and I confirmed. Now I am able to access.
Click to expand...
Click to collapse
Yeah, the new adb(d) (6 months back, iirc) added some security where you have to confirm the rsa fingerprint of each machine you connect to. It's a little annoying, because you HAVE to connect adb via USB first, and only then can you use adb via wireless, which is all I ever use anymore.
(edit: adb security added in 4.2.2, which was released in february)

Flashing Shield 2017

Hi,
Have a Shield 2017 which I'd like to flash to a normal LInux userland rather than Android, however I seem to be failing at the first hurdle, namely ADB and Fastboot.
I have been able to ADB over Ethernet, however when I use ADB and Fastboot over USB I never seem to be able to discover the attached device. I've tried using both macOS and Linux, and have tried a number of USB A-A cables.
I've followed both the nVidia flashing instructions, plus a few from this forum, eg enabling the developer mode, USB debugging, etc. to no avail. These are the steps I've taken.
- Enable Development mode on SATV (click build a number of times)
- Enable ADB over USB on SATV (Settings/Development Options/Toggle USB Debugging)
- Download and install Android SDK tools from the Android SDK pages.
- Plugin USB A-A into the end USB port and my Macbook/Linux box
- Run `adb devices`
At this point I don't get any output.
Code:
[[email protected] ~]# adb devices
List of devices attached
If I connect via Ethernet...
Code:
[[email protected] ~]# adb connect 10.200.1.111
connected to 10.200.1.111:5555
[[email protected] ~]# adb devices
List of devices attached
10.200.1.111:5555 device
Although I can at this point reboot the Shield in fastboot/bootloader mode, with a quick `adb reboot bootloader`, I can't then fastboot, as again fastboot cannot see the device.
Code:
[[email protected] ~]# fastboot devices
On neither my mac nor Linux box, the USB device doesn't seem to be recognised (with lsusb or ioreg), although have tried a couple of new USB 3.0 A-A cables. Wondering if the USB debugging isn't enabling fully for some reason?
Any ideas??
Thanks
Dan

danhawker said:
Hi,
Have a Shield 2017 which I'd like to flash to a normal LInux userland rather than Android, however I seem to be failing at the first hurdle, namely ADB and Fastboot.
I have been able to ADB over Ethernet, however when I use ADB and Fastboot over USB I never seem to be able to discover the attached device. I've tried using both macOS and Linux, and have tried a number of USB A-A cables.
I've followed both the nVidia flashing instructions, plus a few from this forum, eg enabling the developer mode, USB debugging, etc. to no avail. These are the steps I've taken.
- Enable Development mode on SATV (click build a number of times)
- Enable ADB over USB on SATV (Settings/Development Options/Toggle USB Debugging)
- Download and install Android SDK tools from the Android SDK pages.
- Plugin USB A-A into the end USB port and my Macbook/Linux box
- Run `adb devices`
At this point I don't get any output.
Code:
[[email protected] ~]# adb devices
List of devices attached
If I connect via Ethernet...
Code:
[[email protected] ~]# adb connect 10.200.1.111
connected to 10.200.1.111:5555
[[email protected] ~]# adb devices
List of devices attached
10.200.1.111:5555 device
Although I can at this point reboot the Shield in fastboot/bootloader mode, with a quick `adb reboot bootloader`, I can't then fastboot, as again fastboot cannot see the device.
Code:
[[email protected] ~]# fastboot devices
On neither my mac nor Linux box, the USB device doesn't seem to be recognised (with lsusb or ioreg), although have tried a couple of new USB 3.0 A-A cables. Wondering if the USB debugging isn't enabling fully for some reason?
Any ideas??
Thanks
Dan
Click to expand...
Click to collapse
Have you solved your issue? I do not have PC but want to use other android device with Magisk and osm0sis ADB & Fastboot script and I have the same problem...

melendi said:
Have you solved your issue? I do not have PC but want to use other android device with Magisk and osm0sis ADB & Fastboot script and I have the same problem...
Click to expand...
Click to collapse
Do you have a nvidia gamepad?

gengt said:
Do you have a nvidia gamepad?
Click to expand...
Click to collapse
Yes and I had already been in fastboot but on another android device with osm0sis ADB & Fastboot script there are no fastboot devices listed.

ADB don't work in Fastboot mode.

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