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
Related
Hi, when i connect an Huawei 3g usb dongle i see this in dmesg:
[ 2706.844241] usb 2-1: new high speed USB device using tegra-ehci and address 7
[ 2706.876571] usb 2-1: New USB device found, idVendor=12d1, idProduct=1c05
[ 2706.876627] usb 2-1: New USB device strings: Mfr=2, Product=1, SerialNumber=0
[ 2706.876671] usb 2-1: Product: HUAWEI Mobile
[ 2706.876705] usb 2-1: Manufacturer: HUAWEI
but i can't find the associated device under /dev (I guess it should be ttyHS[X])
Thanks for any help!
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.
Hello,
I have problem with device T-R42.
I cannot enable ethernet - every time I try enable connection it logs to logcat:
dmesg reports:
<6>[ 3.329844] usb 2-1.4: new full speed USB device number 3 using usb20_host
<3>[ 3.409848] usb 2-1.4: device descriptor read/64, error -32
<3>[ 3.599841] usb 2-1.4: device descriptor read/64, error -32
whilest properly operational device has
<6>[ 3.390032] usb 2-1.4: new high speed USB device number 3 using usb20_host
<6>[ 3.502644] usb 2-1.4: New USB device found, idVendor=0b95, idProduct=772b
<6>[ 3.502680] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 3.502716] usb 2-1.4: Product: AX88772C
<6>[ 3.502741] usb 2-1.4: Manufacturer: ASIX Elec. Corp.
<6>[ 3.502766] usb 2-1.4: SerialNumber: 0002B1
<6>[ 4.153134] ASIX USB Ethernet Adapter:v4.1.1 17:50:33 Aug 13 2013
Is there anybody who can help me, please?
Many thanks
Jan
Hi,
First i'm french si sorry for grammar
I 'm on cyanogenmod 12 / nethunter /root /busybox
I recently bought an wifi adaptater and plug it on my phone but I doesn't show up on ifconfig or airmon-ng.I have tried an other card who work with no problem. The strange thing is that the card show up in lsusb and dmesg
Output of lsusb:
Code:
[email protected]:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Output of dmesg:
Code:
[53625.557927] init: untracked pid 1031 exited with status 0[53636.095878] msm-dwc3 msm_dwc3: DWC3 exited from low power mode
[53636.098024] qpnp_chg_ext_charger_reset: qpnp_chg_ext_charger_reset reset:1
[53636.100268] qpnp_chg_ext_charger_reset: qpnp_chg_ext_charger_reset reset:0
[53636.104646] qpnp_chg_ext_charger_wdt_set: qpnp_chg_ext_charger_wdt_set seconds:0
[53636.105999] bq24196_charge_en enable:0
[53636.108919] bq24196_vddmax_set voltage:4350
[53636.115950] bq24196_charge_en enable:2
[53636.125106] xhci-hcd xhci-hcd: xHCI Host Controller
[53636.125408] xhci-hcd xhci-hcd: new USB bus registered, assigned bus number 1
[53636.137471] xhci-hcd xhci-hcd: irq 163, io mem 0xf9200000[53636.155514] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[53636.156186] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[53636.156286] usb usb1: Product: xHCI Host Controller
[53636.156439] usb usb1: Manufacturer: Linux 3.4.67-cyanogenmod-g399b32b xhci-hcd
[53636.156536] usb usb1: SerialNumber: xhci-hcd
[53636.160953] xHCI xhci_add_endpoint called for root hub
[53636.160962] xHCI xhci_check_bandwidth called for root hub[53636.161638] hub 1-0:1.0: USB hub found
[53636.161736] hub 1-0:1.0: 1 port detected
[53636.162783] xhci-hcd xhci-hcd: xHCI Host Controller
[53636.162936] xhci-hcd xhci-hcd: new USB bus registered, assigned bus number 2
[53636.163183] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[53636.163330] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[53636.163473] usb usb2: Product: xHCI Host Controller
[53636.163554] usb usb2: Manufacturer: Linux 3.4.67-cyanogenmod-g399b32b xhci-hcd
[53636.163701] usb usb2: SerialNumber: xhci-hcd
[53636.165570] xHCI xhci_add_endpoint called for root hub
[53636.165579] xHCI xhci_check_bandwidth called for root hub[53636.166218] hub 2-0:1.0: USB hub found
[53636.166310] hub 2-0:1.0: 1 port detected
[53636.653437] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[53636.686391] usb 1-1: New USB device found, idVendor=148f, idProduct=7601
[53636.686847] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[53636.687281] usb 1-1: Product: 802.11 n WLAN
[53636.687521] usb 1-1: Manufacturer: MediaTek
[53636.687759] usb 1-1: SerialNumber: 1.0
[email protected]:~#
If anyone know how to fix or patch it let me know how.
TurtleForGaming said:
Hi,
First i'm french si sorry for grammar
I 'm on cyanogenmod 12 / nethunter /root /busybox
I recently bought an wifi adaptater and plug it on my phone but I doesn't show up on ifconfig or airmon-ng.I have tried an other card who work with no problem. The strange thing is that the card show up in lsusb and dmesg
Output of lsusb:
Code:
[email protected]:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Output of dmesg:
Code:
[53625.557927] init: untracked pid 1031 exited with status 0[53636.095878] msm-dwc3 msm_dwc3: DWC3 exited from low power mode
[53636.098024] qpnp_chg_ext_charger_reset: qpnp_chg_ext_charger_reset reset:1
[53636.100268] qpnp_chg_ext_charger_reset: qpnp_chg_ext_charger_reset reset:0
[53636.104646] qpnp_chg_ext_charger_wdt_set: qpnp_chg_ext_charger_wdt_set seconds:0
[53636.105999] bq24196_charge_en enable:0
[53636.108919] bq24196_vddmax_set voltage:4350
[53636.115950] bq24196_charge_en enable:2
[53636.125106] xhci-hcd xhci-hcd: xHCI Host Controller
[53636.125408] xhci-hcd xhci-hcd: new USB bus registered, assigned bus number 1
[53636.137471] xhci-hcd xhci-hcd: irq 163, io mem 0xf9200000[53636.155514] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[53636.156186] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[53636.156286] usb usb1: Product: xHCI Host Controller
[53636.156439] usb usb1: Manufacturer: Linux 3.4.67-cyanogenmod-g399b32b xhci-hcd
[53636.156536] usb usb1: SerialNumber: xhci-hcd
[53636.160953] xHCI xhci_add_endpoint called for root hub
[53636.160962] xHCI xhci_check_bandwidth called for root hub[53636.161638] hub 1-0:1.0: USB hub found
[53636.161736] hub 1-0:1.0: 1 port detected
[53636.162783] xhci-hcd xhci-hcd: xHCI Host Controller
[53636.162936] xhci-hcd xhci-hcd: new USB bus registered, assigned bus number 2
[53636.163183] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[53636.163330] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[53636.163473] usb usb2: Product: xHCI Host Controller
[53636.163554] usb usb2: Manufacturer: Linux 3.4.67-cyanogenmod-g399b32b xhci-hcd
[53636.163701] usb usb2: SerialNumber: xhci-hcd
[53636.165570] xHCI xhci_add_endpoint called for root hub
[53636.165579] xHCI xhci_check_bandwidth called for root hub[53636.166218] hub 2-0:1.0: USB hub found
[53636.166310] hub 2-0:1.0: 1 port detected
[53636.653437] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[53636.686391] usb 1-1: New USB device found, idVendor=148f, idProduct=7601
[53636.686847] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[53636.687281] usb 1-1: Product: 802.11 n WLAN
[53636.687521] usb 1-1: Manufacturer: MediaTek
[53636.687759] usb 1-1: SerialNumber: 1.0
[email protected]:~#
If anyone know how to fix or patch it let me know how.
Click to expand...
Click to collapse
I guess this thread can help you:
https://forum.xda-developers.com/oneplus-one/general/unleash-true-potential-oneplus-t3394310
Nope. In my case I think it's driver related because other card work but I can't install the linux driver for the MT7601U due software dependencies / 404 error
UP
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.