ADB flatly refuses to recognise my Xoom MZ601.
I run ADB on my Debian Linux computer and it recognises my LG Optimus 2x (P990) which appears in the list provided by 'adb devices' the same command with my Xoom produces 'List of devices attached' with nothing underneath. The USB Debug setting on the Xoom is ticked and the computer recognises the device. The computer's log shows:
Jun 24 12:10:37 dataman1 kernel: [3605717.696244] usb 1-7.2: new high-speed USB device number 67 using ehci_hcd
Jun 24 12:10:37 dataman1 kernel: [3605717.800363] usb 1-7.2: unable to read config index 0 descriptor/start: -71
Jun 24 12:10:37 dataman1 kernel: [3605717.800368] usb 1-7.2: chopping to 0 config(s)
Jun 24 12:10:37 dataman1 kernel: [3605717.807734] usb 1-7.2: New USB device found, idVendor=22b8, idProduct=70a8
Jun 24 12:10:37 dataman1 kernel: [3605717.807739] usb 1-7.2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Jun 24 12:10:37 dataman1 kernel: [3605717.807742] usb 1-7.2: Product: MZ600
Jun 24 12:10:37 dataman1 kernel: [3605717.807745] usb 1-7.2: Manufacturer: Motorola
Jun 24 12:10:37 dataman1 kernel: [3605717.807748] usb 1-7.2: SerialNumber: xxxxxxxxxxxxxxxxx
Jun 24 12:10:37 dataman1 kernel: [3605717.807878] usb 1-7.2: no configuration chosen from 0 choices
{The serial number has been changed to protect the innocent }
The udev 51-android.rules shows:
# LG Optimus 2x
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTR{idVendor}=="1004", ATTRS{idProduct}=="618e", SYMLINK+="libmtp-%k", MODE="0666"
# Xoom
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTRS{idProduct}=="70a9", SYMLINK+="libmtp-%k", MODE="0666"
# Bootloader
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"
I have run out of ideas. I am hoping to root the Xoom soon so any suggestions would be greatly appreciated.
BarrySamuels said:
ADB flatly refuses to recognise my Xoom MZ601.
I run ADB on my Debian Linux computer and it recognises my LG Optimus 2x (P990) which appears in the list provided by 'adb devices' the same command with my Xoom produces 'List of devices attached' with nothing underneath. The USB Debug setting on the Xoom is ticked and the computer recognises the device. The computer's log shows:
Jun 24 12:10:37 dataman1 kernel: [3605717.696244] usb 1-7.2: new high-speed USB device number 67 using ehci_hcd
Jun 24 12:10:37 dataman1 kernel: [3605717.800363] usb 1-7.2: unable to read config index 0 descriptor/start: -71
Jun 24 12:10:37 dataman1 kernel: [3605717.800368] usb 1-7.2: chopping to 0 config(s)
Jun 24 12:10:37 dataman1 kernel: [3605717.807734] usb 1-7.2: New USB device found, idVendor=22b8, idProduct=70a8
Jun 24 12:10:37 dataman1 kernel: [3605717.807739] usb 1-7.2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Jun 24 12:10:37 dataman1 kernel: [3605717.807742] usb 1-7.2: Product: MZ600
Jun 24 12:10:37 dataman1 kernel: [3605717.807745] usb 1-7.2: Manufacturer: Motorola
Jun 24 12:10:37 dataman1 kernel: [3605717.807748] usb 1-7.2: SerialNumber: xxxxxxxxxxxxxxxxx
Jun 24 12:10:37 dataman1 kernel: [3605717.807878] usb 1-7.2: no configuration chosen from 0 choices
{The serial number has been changed to protect the innocent }
The udev 51-android.rules shows:
# LG Optimus 2x
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTR{idVendor}=="1004", ATTRS{idProduct}=="618e", SYMLINK+="libmtp-%k", MODE="0666"
# Xoom
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTRS{idProduct}=="70a9", SYMLINK+="libmtp-%k", MODE="0666"
# Bootloader
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"
I have run out of ideas. I am hoping to root the Xoom soon so any suggestions would be greatly appreciated.
Click to expand...
Click to collapse
download http://adbdriver.com/upload/AdbDriverInstaller.exe
and install adb drivers installer on pc,open it
and connect your phone to pc and install the
adb drivers.
Syed.Zeshan said:
download http://adbdriver.com/upload/AdbDriverInstaller.exe
and install adb drivers installer on pc,open it
and connect your phone to pc and install the
adb drivers.
Click to expand...
Click to collapse
It is nice of you to try and help but a Windows executable is not going to run on a Linux machine. There are drivers already on the Linux machine because, as I said in my post, I can use ADB to connect to my LG Optimus 2x.
Wasn't there some udev rule that needs adding?
Sent from my HTC One using xda app-developers app
Maybe use WiFi adb? That's another solution that will probably work. I'm sure you can find an app easily enough. Or does stock android has it by default? Don't really remember...
Chaosgod27 said:
Maybe use WiFi adb? That's another solution that will probably work. I'm sure you can find an app easily enough. Or does stock android has it by default? Don't really remember...
Click to expand...
Click to collapse
I'll give that a try and report back.
spychodelics: I have added udev rules as shown in my first post.
Thanks to you both for trying to help.
Update: I have now solved the problem. With some Linux kernels, mine included, if the ehci_hcd module (needed for USB 2.0) is loaded it prevents the Xoom from being recognised so a modprobe -r ehci_hcd will unload that module and, Voila!, my Xoom is now recognised by ADB. I imagine a fix for that bug will be issued sometime.
Related
After building a system image to root the ASUS MemoPad FHD 10, I am fed up with having to wait almost 15 minutes for Windoze to boot up and shut down so I can run fastboot to flash the image file. So, I've been on a quest to get adb and fastboot working with Ubuntu so I don't have to deal with stupid Windoze.
Using lnusb, tablet has different vendor:device ids when regular booted and usb debug on (adb mode) and when bootloader/recovery booted with fastboot waiting for command.
Tablet mounts using 'go-mtpfs' so I can work with internal/external SDcards.
Tablet displays with 'adb devices' (normal boot) as Medfield9A65CCEC (also shows this with Windoze fastboot devices)
Tablet doesn't display with 'fastboot devices' (bootloader/recovery boot)
51-android.rules file to recognize both vendor ids:
Code:
# ASUS MemoPad FHD 10 32Mb
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", MODE="0666", GROUP="plugdev", OWNER="Me" # MTP mode with USB debug on
SUBSYSTEM=="usb", ATTR(idVendor}=="8087", MODE="0666", GROUP="plugdev", OWNER="Me" # fastboot mode
Tried downloading a different fastboot binary, same results.
At this point I am stumped why adb works but fastboot does not. fastboot works fine in Windoze.
More Info
After some more research, I found this:
http://packages.ubuntu.com/raring/i386/android-tools-fastboot/filelist
which shows a rules file in /lib/udev/rules.d/70-android-tools-fastboot.rules
so I looked in /lib/udev/rules.d and found the rules file: 51-android-rules.rules with loads of entries
and not /etc/udev/rules.d/51-android-rules.rules as most discussions refer to
so I modified the ASUS section to this:
Code:
# Asus MemoPad FHD 10 (Intel)
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", ATTR{idProduct}=="521f", SYMLINK+="android_adb"
SUBSYSTEM=="usb", ATTR{idVendor}=="8087", ATTR{idProduct}=="09ef", SYMLINK+="android_fastboot"
#SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", MODE="0660", GROUP="adbusers"
#SUBSYSTEM=="usb", ATTR{idVendor}=="8087", MODE="0660", GROUP="adbusers"
If I comment out the first two lines and use #3&4 syslog shows an error - udevd[3982]: specified group 'adbusers' unknown
If I use the first two lines and comment out #3&4 (as shown above) syslog shows:
Code:
Dec 20 14:45:48 kernel: [25297.608132] usb 2-1: new high-speed USB device number 11 using ehci-pci
Dec 20 14:45:48 kernel: [25297.745240] usb 2-1: New USB device found, idVendor=8087, idProduct=09ef
Dec 20 14:45:48 kernel: [25297.745252] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Dec 20 14:45:48 kernel: [25297.745260] usb 2-1: Product: Android-Phone
Dec 20 14:45:48 kernel: [25297.745268] usb 2-1: Manufacturer: Android
Dec 20 14:45:48 kernel: [25297.745275] usb 2-1: SerialNumber: Medfield9A65CCEC
Dec 20 14:45:48 mtp-probe: checking bus 2, device 11: "/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1"
Dec 20 14:45:48 mtp-probe: bus: 2, device: 11 was not an MTP device
There are no errors, so the rules file in /lib/udev/rules.d and not /etc/udev/rules.d is being used
Also interesting is that lsusb shows:
Bus 002 Device 011: ID 8087:09ef Intel Corp.
...which is a different Vendor ID
However, even with the correct rules file set and no syslog errors on USB connect, fastboot still refuses to recognize the device when connected in fastboot mode.
I have also tried fastboot i 0x8087 reboot and fastboot -sMedfield9A65CCEC reboot and it just waits for device.
It may be possible that fastboot doesn't like the Intel and is looking for ARM, not sure - although Windoze version of fastboot works fine.
On Archlinux I have the same problem
sudo adb devices works, fastboot fails with <Waiting for device>
but in fastboot mode nothing works at all
Same problem in Ubuntu 14.04 for Kindle Fire
I know this thread has been dormant for a while, but it's pretty much the only hit that comes up when searching on how to setup the /lib/udev/rules.d/70-android-tools-fastboot.rules to get device to mount in fastboot properly.
I had followed some other guides like the OP that said to put rules in the /etc/udev/rules.d/51-android-devices.rules which didn't work at all. I do not have a file /lib/udev/rules.d/51-android-devices..rules
I am having issues similar to the OP with a Kindle Fire Gen2. Device shows up when in Adb mode, but not in fastboot (using factory "fastboot" cable).
Was there ever a resolution to this issue?
Anybody have a source of documentation on how these config files need to be set up when in fastboot mode to gain access and/or get a trusted connection in MTP?
I've been scratching head all evening trying to solve this, with no luck.
I've added the following lines to the /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", MODE="0600", OWNER="paul"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee0", MODE="0600", OWNER="paul"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee1", MODE="0600", OWNER="paul"When I run adb devices, it looks OK
List of devices attached
07c082820f1e64c0 deviceAnd lsusb | grep Google finds the device (although it is identified as a Nexus 4 for some reason)
Bus 001 Device 105: ID 18d1:4ee2 Google Inc. Nexus 4 (debug)Finally, ls -Rl /dev/bus/usb/001/105 indicates
crw-rw----+ 1 paul audio 189, 104 Nov 11 00:13 /dev/bus/usb/001/105
But, when I set the phone to bootloader mode by running adb reboot bootloader, and run fastboot devices, I get an empty line.
When I run fastboot flashall -w, I get
< waiting for device >When I run lsusb, the Google line is no longer displayed.
Also, I see in the /var/log/syslog that the Google device is added when I boot the phone, and is removed when I change to fastboot mode.
On reboot:
Nov 11 00:13:03 LENOVO-W541 kernel: [ 2807.950990] usb 1-2: Product: AOSP on HammerHead
Nov 11 00:13:03 LENOVO-W541 kernel: [ 2807.950992] usb 1-2: Manufacturer: LGE
Nov 11 00:13:03 LENOVO-W541 kernel: [ 2807.950993] usb 1-2: SerialNumber: 07c082820f1e64c0
Nov 11 00:13:03 LENOVO-W541 colord: Device added: sysfs-LGE-AOSP_on_HammerHeadIn fastboot:
Nov 11 00:21:08 LENOVO-W541 kernel: [ 3293.100855] usb 1-2: USB disconnect, device number 105
Nov 11 00:21:08 LENOVO-W541 colord: device removed: sysfs-(null)
Nov 11 00:21:08 LENOVO-W541 colord: device removed: sysfs-(null)
Nov 11 00:21:08 LENOVO-W541 colord: device removed: sysfs-LGE-AOSP_on_HammerHead
Can anyone help? I can't even do something as basic as flashing a new image to the phone.
Paul
Try
Code:
sudo fastboot devices
Found the problem (I think). Seems to be a stupid USB cable problem.
At work, with phone in fastboot/bootloader mode:
$ lsusb | grep Google
Bus 001 Device 098: ID 18d1:4ee0 Google Inc.There seems to be a bug, because in normal mode, the same command gives:
Bus 001 Device 100: ID 18d1:4ee2 Google Inc. Nexus 4 (debug)At home, in fastboot mode this command gives nothing, just an empty line.
Similarly, at work, in fastboot mode:
$ fastboot devices
07c082820f1e64c0 fastbootThe same command at home gives:
<waiting for device>
All with the same phone and laptop, just different cables.
After creating rules, did you reload them? either by rebooting or using udevadm?
What distro are you on?
beekay201 said:
After creating rules, did you reload them? either by rebooting or using udevadm?
What distro are you on?
Click to expand...
Click to collapse
beekay,
Yes, I had reloaded the rules, using sudo /etc/init.d/udev restart
Ubuntu 14.04. problem solved, as I indicated above.
Hi,
For some reason, "fastboot devices" shows no devices when I connect my LG G Stylo MS631 in the download mode (a.k.a. the firmware update mode) to the PC. Not sure why that is and what could be done about it.
Any ideas? Thanks
More info: when the phone in the dowload mode connected to the PC, in the log I see the following:
Feb 06 10.06:22 tst kernel: [969014.956096] usb 1-2: new high-speed USB device number 37 using ehci_hcd
Feb 06 10.06:22 tst kernel: [969015.172125] hub 1-0:1.0: unable to enumerate USB device on port 2
Feb 06 10.06:29 tst kernel: [969021.740096] usb 1-2: new high-speed USB device number 38 using ehci_hcd
Feb 06 10.06:29 tst kernel: [969021.874612] usb 1-2: New USB device found, idVendor=1004, idProduct=633e
Feb 06 10.06:29 tst kernel: [969021.874624] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 06 10.06:29 tst kernel: [969021.874633] usb 1-2: Product: LGE Android Phone
Feb 06 10.06:29 tst kernel: [969021.874640] usb 1-2: Manufacturer: LG Electronics Inc.
Feb 06 10.06:29 tst kernel: [969021.874647] usb 1-2: SerialNumber: LGxxxxxxxxxxxxx
"fastboot devices" still shows no devices though. Any ideas? Thanks
Hello,
connecting my OnePlus One to my Linux machine without running adb works just fine. But as soon as I launch adb, the phone keeps connecting and disconnecting. adb does not find any devices.
Code:
Okt 21 20:15:52 asaru kernel: usb 2-3: new high-speed USB device number 8 using xhci_hcd
Okt 21 20:15:52 asaru kernel: usb 2-3: USB disconnect, device number 8
and so it goes on every second.
Code:
# adb --version
Android Debug Bridge version 1.0.39
Revision 8.0.0_r17
Linux is 4.13.7-1-ARCH. The mobile device is at the OEM firmware, most recent version *lol*.
I tried it on different USB ports and two different machines, the behavior is identical.
Any idea?
Thanks a lot!
Solved for me at least (ADB in arch is out of date)
EDIT:: TLDR: It's adb for sure. Download the latest version from google via HERE (direct link here
So I know this doesn't really add to the issue but I think this may be an adb or kernel issue. I have the same kernel and same ADB version as you (Actually running arch as well ^_^)
The odd thing is the udev rules work just fine in creating the initial links and the flakiness in the usb attachment doesn't start until after I spawn the adb server (I'm not sure if yours is the same way). The only difference between our behavior that I can see is that I'm using a Samsung S8+ :/ (sorry for the wrong thread and if this is hijacking please let me know and I'll delete it.). I am just trying to lend evidence to his/her issue.
udev version
Code:
root at locallaptop.local in ~
$ udevadm --version
235
kernel version
Code:
root at locallaptop.local in ~
$ uname -r
4.13.7-1-ARCH
adb version:
Code:
root at locallaptop.local in ~
$ adb --version
Android Debug Bridge version 1.0.39
Revision 8.0.0_r17
unplugging and then Plugging in my phone prior
Prior to starting the adb server:
Code:
$ udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[6495.318173] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0 (usb)
KERNEL[6495.318456] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/tty/ttyACM0 (tty)
KERNEL[6495.318563] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1 (usb)
KERNEL[6495.318717] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.2 (usb)
KERNEL[6495.318851] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.3 (usb)
UDEV [6495.320466] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0 (usb)
KERNEL[6495.320719] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1 (usb)
UDEV [6495.321900] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.2 (usb)
UDEV [6495.322998] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/tty/ttyACM0 (tty)
UDEV [6495.323727] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.3 (usb)
UDEV [6495.324702] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1 (usb)
UDEV [6495.344709] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1 (usb)
KERNEL[6510.098862] add /devices/pci0000:00/0000:00:14.0/usb1/1-1 (usb)
KERNEL[6510.101484] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0 (usb)
KERNEL[6510.102087] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1 (usb)
KERNEL[6510.102905] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/tty/ttyACM0 (tty)
KERNEL[6510.103484] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.2 (usb)
KERNEL[6510.104179] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.3 (usb)
UDEV [6510.677580] add /devices/pci0000:00/0000:00:14.0/usb1/1-1 (usb)
UDEV [6510.680327] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0 (usb)
UDEV [6510.682239] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1 (usb)
UDEV [6510.683855] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.2 (usb)
UDEV [6510.684237] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.3 (usb)
UDEV [6510.686602] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/tty/ttyACM0 (tty)
Now when I start ADB the device is repeatedly disconnected:
Code:
KERNEL[6600.187212] add /devices/pci0000:00/0000:00:14.0/usb1/1-1 (usb)
KERNEL[6600.190544] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0 (usb)
KERNEL[6600.190930] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1 (usb)
KERNEL[6600.192065] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/tty/ttyACM0 (tty)
KERNEL[6600.192586] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.2 (usb)
KERNEL[6600.194047] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.3 (usb)
UDEV [6600.750663] add /devices/pci0000:00/0000:00:14.0/usb1/1-1 (usb)
UDEV [6600.756551] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1 (usb)
UDEV [6600.756820] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0 (usb)
UDEV [6600.758959] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.2 (usb)
UDEV [6600.762960] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.3 (usb)
UDEV [6600.763358] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/tty/ttyACM0 (tty)
KERNEL[6601.181364] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/tty/ttyACM0 (tty)
UDEV [6601.186369] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/tty/ttyACM0 (tty)
KERNEL[6601.500084] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/tty/ttyACM0 (tty)
KERNEL[6601.500886] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0 (usb)
KERNEL[6601.501316] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/tty/ttyACM0 (tty)
KERNEL[6601.501415] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1 (usb)
KERNEL[6601.501566] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.2 (usb)
KERNEL[6601.501811] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.3 (usb)
KERNEL[6601.502434] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1 (usb)
UDEV [6601.504065] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0 (usb)
UDEV [6601.504908] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/tty/ttyACM0 (tty)
UDEV [6601.505005] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.3 (usb)
UDEV [6601.505985] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.2 (usb)
UDEV [6601.506638] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/tty/ttyACM0 (tty)
UDEV [6601.507346] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1 (usb)
UDEV [6601.524724] remove /devices/pci0000:00/0000:00:14.0/usb1/1-1 (usb)
KERNEL[6601.994357] add /devices/pci0000:00/0000:00:14.0/usb1/1-1 (usb)
KERNEL[6601.996190] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0 (usb)
KERNEL[6601.996697] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1 (usb)
KERNEL[6601.997695] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/tty/ttyACM0 (tty)
KERNEL[6601.998163] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.2 (usb)
KERNEL[6601.998534] add /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.3 (usb)
Corresponding kernel log:
Code:
Oct 27 16:43:45 locallaptop.local kernel: usb 1-1: new high-speed USB device number 47 using xhci_hcd
Oct 27 16:43:46 locallaptop.local kernel: cdc_acm 1-1:1.1: ttyACM0: USB ACM device
Oct 27 16:43:47 locallaptop.local kernel: usb 1-1: USB disconnect, device number 47
Oct 27 16:43:47 locallaptop.local kernel: cdc_acm 1-1:1.1: ttyACM0: USB ACM device
Oct 27 16:43:47 locallaptop.local kernel: usb 1-1: new high-speed USB device number 48 using xhci_hcd
Oct 27 16:43:47 locallaptop.local kernel: cdc_acm 1-1:1.1: ttyACM0: USB ACM device
Oct 27 16:43:49 locallaptop.local kernel: usb 1-1: USB disconnect, device number 48
Oct 27 16:43:49 locallaptop.local kernel: cdc_acm 1-1:1.1: ttyACM0: USB ACM device
Oct 27 16:43:49 locallaptop.local kernel: usb 1-1: new high-speed USB device number 49 using xhci_hcd
Oct 27 16:43:49 locallaptop.local kernel: cdc_acm 1-1:1.1: ttyACM0: USB ACM device
Oct 27 16:43:51 locallaptop.local kernel: cdc_acm 1-1:1.1: ttyACM0: USB ACM device
Oct 27 16:43:51 locallaptop.local kernel: usb 1-1: USB disconnect, device number 49
Oct 27 16:43:51 locallaptop.local kernel: usb 1-1: new high-speed USB device number 50 using xhci_hcd
Oct 27 16:43:51 locallaptop.local kernel: cdc_acm 1-1:1.1: ttyACM0: USB ACM device
Finally, trying to connect via libmtp works without issue for me:
Code:
$ mtp-detect
libmtp version: 1.1.14
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Found 1 device(s):
Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 79
I tried clearing my "External Storage" and "Media Storage" which seems to fix the issue if you get:
Code:
LIBMTP_Get_Storage(): Resource temporarily unavailable
When trying to pull/push files via mtp but I'm not having that issue and can list/use mtp without issue:
Code:
$ timeout 1 mtp-filetree
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Attempting to connect device(s)
Device: MyAndroidPhone
Storage: Phone
2000000 Samsung
2 Music
891 Over_the_Horizon.mp3
2000001 Android
4 data
2000022 .nomedia
2000023 com.samsung.android.coreapps
2000173 cache
2000174 volley
2000024 com.android.providers.media
2000175 albumthumbs
2000025 com.google.android.youtube
2000177 cache
2000179 exo
Is this the same with your phone as well?
EDIT:: After downloading the latest ADB client/server it works without issue::
Code:
$ ./adb devices -l
List of devices attached
98891a303554423541 device usb:3-1.1 product:dream2qltesq model:SM_G955U device:dream2qltesq
Hi *,
I hava a xiaomi mi a3 with broken screen, i already rooted and enable debugging previous of the broken.
Now i would use scrcpy but adb listing my device as unhautorized.
I see in other post that i need to copy the key on /android/data/..., but i unable because adb shell does not work, so i read that entering in fastboot mode i able to copy the files without key.
So i powered off the phone and restart with volume up+power and i see this on my syslog
Oct 22 15:32:22 debian-z230 kernel: [ 5541.994136] usb 2-7: new high-speed USB device number 19 using xhci_hcd
Oct 22 15:32:23 debian-z230 kernel: [ 5542.144023] usb 2-7: New USB device found, idVendor=18d1, idProduct=d001, bcdDevice= 4.14
Oct 22 15:32:23 debian-z230 kernel: [ 5542.144038] usb 2-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 22 15:32:23 debian-z230 kernel: [ 5542.144044] usb 2-7: Product: Mi A3
Oct 22 15:32:23 debian-z230 kernel: [ 5542.144048] usb 2-7: Manufacturer: Xiaomi
Oct 22 15:32:23 debian-z230 kernel: [ 5542.144051] usb 2-7: SerialNumber: 7044fce4312c
Oct 22 15:32:23 debian-z230 gvfsd[14218]: LIBMTP PANIC: Unable to find interface & endpoints of device
Oct 22 15:32:23 debian-z230 gnome-shell[2659]: Unable to mount volume Mi A3: Gio.IOErrorEnum: Unable to open MTP device “002,019”
Oct 22 15:32:24 debian-z230 gvfsd[14218]: Device 0 (VID=18d1 and PID=d001) is a Meizu Pro 5 Ubuntu Phone.
I tryed to run adb but it seems always recognized it as unhautorized, fastboot devices command instead does not report any output:
[email protected]:~$ fastboot devices
[email protected]:~$ fastboot reboot
< waiting for any device >
[email protected]:~$ adb devices
List of devices attached
7044fce4312c unauthorized
if the phone starts in normal mode instead on the syslog i see this
Oct 22 15:44:24 debian-z230 kernel: [ 6263.802797] usb 2-7: new high-speed USB device number 24 using xhci_hcd
Oct 22 15:44:24 debian-z230 kernel: [ 6263.953115] usb 2-7: New USB device found, idVendor=2717, idProduct=ff08, bcdDevice= 4.14
Oct 22 15:44:24 debian-z230 kernel: [ 6263.953121] usb 2-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 22 15:44:24 debian-z230 kernel: [ 6263.953123] usb 2-7: Product: Mi A3
Oct 22 15:44:24 debian-z230 kernel: [ 6263.953125] usb 2-7: Manufacturer: Xiaomi
Oct 22 15:44:24 debian-z230 kernel: [ 6263.953126] usb 2-7: SerialNumber: 7044fce4312c
Oct 22 15:44:24 debian-z230 mtp-probe: checking bus 2, device 24: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-7"
Oct 22 15:44:24 debian-z230 mtp-probe: bus: 2, device: 24 was not an MTP device
Oct 22 15:44:25 debian-z230 mtp-probe: checking bus 2, device 24: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-7"
Oct 22 15:44:25 debian-z230 mtp-probe: bus: 2, device: 24 was not an MTP device
Oct 22 15:44:55 debian-z230 /usr/libexec/gdm-x-session[2473]: (EE) event2 - Primax HP USB Keyboard: client bug: event processing lagging behind by 13ms, your system is too slow
Oct 22 15:45:01 debian-z230 CRON[14796]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
so seems that product, vendor and device id is different.
Could someone confirm that the first id, of product vendor and device is fastboot device?
There is a method to solve this impasse?
Thanks a lot to all
so the vendor product and device is different
Fastboot gets enabled by default when an Android device boots up, unless manufacturer ( e.g. Samsung ) decided not to support Fastboot. But Xiamomi devices support Fastboot, AFAIK.
FYI: Fastboot isn't a device you can find in /dev/block, it's a software that allows to operate on Android device's bootloader.
jwoegerbauer said:
Fastboot gets enabled by default when an Android device boots up, unless manufacturer ( e.g. Samsung ) decided not to support Fastboot. But Xiamomi devices support Fastboot, AFAIK.
FYI: Fastboot isn't a device you can find in /dev/block, it's a software that allows to operate on Android device's bootloader.
Click to expand...
Click to collapse
Hi and thanks for the answers, but I think that Linux discover fastboot device with different product vendor and device id respect normal boot. I would know why fastboot command does not discover my device, I suspect, because my screen on device is broken, that device not start in fastboot mode and I ask to group what kind of product device and vendor I'd you seen for your xiaomi mi a3 device under syslog or lsusb in fastboot mode.
Yes
Code:
sudo ./fastboot devices
returns
Code:
<SERIAL_ID> fastboot
but that's NOT AN ANDROID DEVICE, IT'S THE DEVICE'S BOOTLOADER connected to, and nothing else.
If the output is shown as above listed, then Fastboot-mode is enabled/activated and working.