Adb devices
DEVICE STATUS: UNAUTHORIZED
DEVICE INFORMATION: XXXXXXXXXXX unauthorized
My N1 can't boot.
How to "Revoke USB debugging authorization" in adb commands?
I want you to help me out of this situation . Thank you very muchh.
Related
When I connect my HTC Desire through USB cable to my laptop, my laptop wait a while then pop a windows which says USB Device Not Recognised. My device just got the orange light lit up but there is no response other than that i.e. no menu pops up to choose "charge only, disk drive" whatsoever.
It worked just two days ago before I reflash a new ROM (RCMixHD 3.6.1).
During the flash, the SD card was not recognised too so I tried to get it work by using "fastboot oem enableqxdm 0" as instructed by one post named "USB brick/rickrolled/b0rked -> FIXED!" on MoDaCo.
But I did not flash the update.zip as required cos my problem was fixed before this step.
Can anyone help me fix this problem? Waiting online
USB debugging still enabled?
What result from either adb or fastboot?
Code:
fastboot devices
adb devices
FASTBOOT shows "FASTBOOT USB", Bootloader also gives me "HBOOT USB PLUG", I think the USB cable is fine.
stringer7 said:
USB debugging still enabled?
What result from either adb or fastboot?
Code:
fastboot devices
adb devices
Click to expand...
Click to collapse
I tried the two commands in cmd, I copy down what it gives me
E:\SDK\Tools> adb devices
List of devices attached
E:\SDK\Tools> fastboot devices
HT05HPL12963 fastboot
E:\SDK\Tools>
Ok so the fastboot result means you can connect to PC.
What happens if you connect your device whilst it's booted up with USB debugging enabled? Enable this prior to connecting in settings>applications>development.
Hi thanks for the help, I managed to unbrick the USB brick. But now even though I'm able to connect to my laptop, the adb devices still doesn't give me any device. In device manager, I got an "ADB" with yellow exclamation mark under “Other Devices”, just cannot get the right driver for it. Could it be due to the USB brick?
Hi.
I have flashed stock ROM for my Xperia Play R800i to R800i_4.0.2.A.0.42_Generic.ftf
but after enabling USB Debugging and Unknown sources, no matter what I do flash tool will always say this:
Code:
25/038/2012 10:38:38 - INFO - Device connected with USB debugging off
25/038/2012 10:38:38 - INFO - For 2011 devices line, be sure you are not in MTP mode
With ADB, devices list is always empty.
theoneofgod said:
Hi.
I have flashed stock ROM for my Xperia Play R800i to R800i_4.0.2.A.0.42_Generic.ftf
but after enabling USB Debugging and Unknown sources, no matter what I do flash tool will always say this:
Code:
25/038/2012 10:38:38 - INFO - Device connected with USB debugging off
25/038/2012 10:38:38 - INFO - For 2011 devices line, be sure you are not in MTP mode
With ADB, devices list is always empty.
Click to expand...
Click to collapse
have u hold the back button when connect it to usb?? please wait a moment when the driver installing
Phone works fine but I cannot root anymore.
Sorry for bumping this, but still no luck.
It seems like USB Debugging does work because my PC detects the ADB device when I plug my phone in.
I have all drivers installed, as I did before, but I still can't get my device to display using "adb devices"
Any help would be great.
can some1 tell me the vendor id for the adb_usb.ini file? i cant find my incredible 2 when i ./adb devices. its just blank.
usb debugging enabled.
Hello all,
I have tried on different laptops, with different cables but my pixel c will not show the rsa dialog to allow access for adb/fastboot. I have tried NRT as well but the device cannot be found. The device is running the lastest software version as of 9/18/16
jasonc7649 said:
Hello all,
I have tried on different laptops, with different cables but my pixel c will not show the rsa dialog to allow access for adb/fastboot. I have tried NRT as well but the device cannot be found. The device is running the lastest software version as of 9/18/16
Click to expand...
Click to collapse
I think more detail is required. Device configured correctly? - Developer options - usb debugging enabled (also revoke debugging authorisations causes a request for RSA confirmation on a previously "connected perfectly" device). Guessing you're using Windows - what "adb" driver (if any) is shown in Device Manager
I've tried to revoke authorizations but nothing happens, and I can access the devices internal storage. However, when I plug the pixel c in, it immediately goes to charging mode and there isn't an mtp button in the storage settings in 7.0 so I can't toggle it on/off. I've also tried enabling/disabling debugging while connected and nothing happens.
I'll assume you have an "adb" driver of some form showing in Device Manager and adb.exe and fastboot.exe in a directory that I'll call "ADB".
Connect the Pixel C and unlock. By default it should have notifications for USB debugging enabled and "USB charging". Adb will work at this stage.
Open a command prompt and change to "ADB" Try the command "adb devices" and it should show your tablet.
Try "adb reboot bootloader" . I expect this command on your PC to fail because it holds no authorisation. But it should trigger:
a) get your tablet to request RSA authorisation
b) start the process of installing the "Android Composite ADB Interface" device driver (under "Android Device" in Device Manager.)
Repeat "adb reboot bootloader" and your tablet should reboot into a "waiting for fastboot command" screen
Try "fastboot devices" should show the tablet and then "fastboot reboot" will restart your tablet.
Pixel c not show up on adb devices list
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.