adb devices could not detect my LG LS740

If none of the more specific forums is the right place to ask

adb devices could not detect my LG LS740

Postby debian » 2017-10-01 16:13

I have a rather old AMD Duron desktop computer with 640 MB RAM + 80 GB HDD that I would like to re-purpose it. So, I decided to install debian 9.1.0 (Stretch). Upon finishing the installation, I installed ADB using aptitude adb. Whenever I 1st launch adb devices, it crashes with error messages as shown below. However, the subsequent launches don't crash the adb, but adb fails to detect my LG LS740 Android smartphone plugged into one of the USB ports on the computer. Am I missing some packages, i.e. USB driver, etc.? Can anyone please help so I can re-use this old computer to connect to my LG LS740 Android smartphone?
Code: Select all
[debian@debian:/home/debian 3%] ~ adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
*** Error in `adb': free(): invalid pointer: 0x014615a0 ***
======= Backtrace: =========
/lib/i386-linux-gnu/libc.so.6(+0x6737a)[0xb739837a]
/lib/i386-linux-gnu/libc.so.6(+0x6dfb7)[0xb739efb7]
/lib/i386-linux-gnu/libc.so.6(+0x6e7f6)[0xb739f7f6]
/usr/lib/i386-linux-gnu/libcrypto.so.1.1(CRYPTO_free+0x39)[0xb71eab39]
/usr/lib/i386-linux-gnu/libcrypto.so.1.1(CRYPTO_secure_free+0x1e1)[0xb71ebe41]
/usr/lib/i386-linux-gnu/libcrypto.so.1.1(+0x8bd16)[0xb7155d16]
/usr/lib/i386-linux-gnu/libcrypto.so.1.1(BN_clear_free+0x87)[0xb7155da7]
/usr/lib/i386-linux-gnu/libcrypto.so.1.1(RSA_free+0x9f)[0xb721481f]
/usr/lib/i386-linux-gnu/android/libadb.so.0(+0x249bc)[0xb77149bc]
/usr/lib/i386-linux-gnu/android/libadb.so.0(+0x2551f)[0xb771551f]
/usr/lib/i386-linux-gnu/android/libadb.so.0(_Z13adb_auth_initv+0x56)[0xb7715ec6]
adb(+0x72f9)[0x4e12f9]
adb(+0xc603)[0x4e6603]
adb(main+0x39)[0x4dedb9]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6)[0xb7349276]
adb(+0x4e32)[0x4dee32]
======= Memory map: ========
004da000-004fd000 r-xp 00000000 08:03 85         /usr/lib/android-sdk/platform-tools/adb
004fd000-004fe000 r--p 00022000 08:03 85         /usr/lib/android-sdk/platform-tools/adb
004fe000-004ff000 rw-p 00023000 08:03 85         /usr/lib/android-sdk/platform-tools/adb
0145b000-01480000 rw-p 00000000 00:00 0          [heap]
b5d00000-b5d29000 rw-p 00000000 00:00 0
b5d29000-b5e00000 ---p 00000000 00:00 0
b5f00000-b5f21000 rw-p 00000000 00:00 0
b5f21000-b6000000 ---p 00000000 00:00 0
b60b9000-b60ba000 ---p 00000000 00:00 0
b60ba000-b68ba000 rw-p 00000000 00:00 0
b68ba000-b68bb000 ---p 00000000 00:00 0
b68bb000-b70bd000 rw-p 00000000 00:00 0
b70bd000-b70c0000 r-xp 00000000 08:03 262155     /lib/i386-linux-gnu/libdl-2.24.so
b70c0000-b70c1000 r--p 00002000 08:03 262155     /lib/i386-linux-gnu/libdl-2.24.so
b70c1000-b70c2000 rw-p 00003000 08:03 262155     /lib/i386-linux-gnu/libdl-2.24.so
b70c2000-b70c8000 r-xp 00000000 08:03 1184399    /usr/lib/i386-linux-gnu/android/liblog.so.0
b70c8000-b70c9000 r--p 00005000 08:03 1184399    /usr/lib/i386-linux-gnu/android/liblog.so.0
b70c9000-b70ca000 rw-p 00006000 08:03 1184399    /usr/lib/i386-linux-gnu/android/liblog.so.0
b70ca000-b7315000 r-xp 00000000 08:03 1184587    /usr/lib/i386-linux-gnu/libcrypto.so.1.1
b7315000-b7316000 ---p 0024b000 08:03 1184587    /usr/lib/i386-linux-gnu/libcrypto.so.1.1
b7316000-b7327000 r--p 0024b000 08:03 1184587    /usr/lib/i386-linux-gnu/libcrypto.so.1.1
b7327000-b732e000 rw-p 0025c000 08:03 1184587    /usr/lib/i386-linux-gnu/libcrypto.so.1.1
b732e000-b7331000 rw-p 00000000 00:00 0
b7331000-b74e2000 r-xp 00000000 08:03 262152     /lib/i386-linux-gnu/libc-2.24.so
b74e2000-b74e3000 ---p 001b1000 08:03 262152     /lib/i386-linux-gnu/libc-2.24.so
b74e3000-b74e5000 r--p 001b1000 08:03 262152     /lib/i386-linux-gnu/libc-2.24.so
b74e5000-b74e6000 rw-p 001b3000 08:03 262152     /lib/i386-linux-gnu/libc-2.24.so
b74e6000-b74e9000 rw-p 00000000 00:00 0
b74e9000-b7505000 r-xp 00000000 08:03 262148     /lib/i386-linux-gnu/libgcc_s.so.1
b7505000-b7506000 r--p 0001b000 08:03 262148     /lib/i386-linux-gnu/libgcc_s.so.1
b7506000-b7507000 rw-p 0001c000 08:03 262148     /lib/i386-linux-gnu/libgcc_s.so.1
b7507000-b755a000 r-xp 00000000 08:03 262156     /lib/i386-linux-gnu/libm-2.24.so
b755a000-b755b000 r--p 00052000 08:03 262156     /lib/i386-linux-gnu/libm-2.24.so
b755b000-b755c000 rw-p 00053000 08:03 262156     /lib/i386-linux-gnu/libm-2.24.so
b755c000-b755e000 rw-p 00000000 00:00 0
b755e000-b76ce000 r-xp 00000000 08:03 1184428    /usr/lib/i386-linux-gnu/libstdc++.so.6.0.22
b76ce000-b76d4000 r--p 0016f000 08:03 1184428    /usr/lib/i386-linux-gnu/libstdc++.so.6.0.22
b76d4000-b76d5000 rw-p 00175000 08:03 1184428    /usr/lib/i386-linux-gnu/libstdc++.so.6.0.22
b76d5000-b76d8000 rw-p 00000000 00:00 0
b76d8000-b76e3000 r-xp 00000000 08:03 1192900    /usr/lib/i386-linux-gnu/android/libcutils.so.0
b76e3000-b76e4000 r--p 0000a000 08:03 1192900    /usr/lib/i386-linux-gnu/android/libcutils.so.0
b76e4000-b76e5000 rw-p 0000b000 08:03 1192900    /usr/lib/i386-linux-gnu/android/libcutils.so.0
b76e5000-b76ee000 r-xp 00000000 08:03 1192898    /usr/lib/i386-linux-gnu/android/libbase.so.0
b76ee000-b76ef000 r--p 00008000 08:03 1192898    /usr/lib/i386-linux-gnu/android/libbase.so.0
b76ef000-b76f0000 rw-p 00009000 08:03 1192898    /usr/lib/i386-linux-gnu/android/libbase.so.0
b76f0000-b7723000 r-xp 00000000 08:03 1192902    /usr/lib/i386-linux-gnu/android/libadb.so.0
b7723000-b7724000 r--p 00032000 08:03 1192902    /usr/lib/i386-linux-gnu/android/libadb.so.0
b7724000-b7725000 rw-p 00033000 08:03 1192902    /usr/lib/i386-linux-gnu/android/libadb.so.0
b7725000-b773e000 r-xp 00000000 08:03 262166     /lib/i386-linux-gnu/libpthread-2.24.so
b773e000-b773f000 r--p 00018000 08:03 262166     /lib/i386-linux-gnu/libpthread-2.24.so
b773f000-b7740000 rw-p 00019000 08:03 262166     /lib/i386-linux-gnu/libpthread-2.24.so
b7740000-b7742000 rw-p 00000000 00:00 0
b775c000-b775f000 rw-p 00000000 00:00 0
b775f000-b7761000 r--p 00000000 00:00 0          [vvar]
b7761000-b7763000 r-xp 00000000 00:00 0          [vdso]
b7763000-b7786000 r-xp 00000000 08:03 262147     /lib/i386-linux-gnu/ld-2.24.so
b7786000-b7787000 r--p 00022000 08:03 262147     /lib/i386-linux-gnu/ld-2.24.so
b7787000-b7788000 rw-p 00023000 08:03 262147     /lib/i386-linux-gnu/ld-2.24.so
bfbc1000-bfbe2000 rw-p 00000000 00:00 0          [stack]
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
[debian@debian:/home/debian 4%] ~ adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

[debian@debian:/home/debian 5%] ~ adb kill-server
debian
 
Posts: 153
Joined: 2007-02-24 14:27

Re: adb devices could not detect my LG LS740

Postby pylkko » 2017-10-01 18:42

what do you see in the kernel log when you attach it? Are you using a data usb cable? There are many usb cables for charging that only have the power lines inside the cable. These of course wont work
User avatar
pylkko
 
Posts: 1174
Joined: 2014-11-06 19:02

Re: adb devices could not detect my LG LS740

Postby debian » 2017-10-02 15:31

pylkko wrote:what do you see in the kernel log when you attach it? Are you using a data usb cable?
No dmesg log activities when I plugged my LG LS740 into any of USB ports on my computer.


There are many usb cables for charging that only have the power lines inside the cable. These of course wont work
I had that thought also. The USB cable I used came with the LG LS740 and I can confirm it is a data cable because I had no problem to use this same USB cable to connect the very same LG LS740 on a friend's Windows XP computer and the software on the Windows XP computer was able to read/write to the LG LS740. This means my computer does not have the correct Linux USB driver, does it? What software package provides such a USB driver?
debian
 
Posts: 153
Joined: 2007-02-24 14:27

Re: adb devices could not detect my LG LS740

Postby pylkko » 2017-10-03 09:19

if you only want to move files see:

viewtopic.php?f=16&t=134786

Or try to look through the settings on the phone what protocol you are supposed to use to connect to the storage.

Or do you need adb for flashing/debugging? The modules required for usb to work come with the kernel itself.

can you plug the phone in and the provide the output of
Code: Select all
cat /var/log/syslog


you need to be root to be able to view that file.
User avatar
pylkko
 
Posts: 1174
Joined: 2014-11-06 19:02

Re: adb devices could not detect my LG LS740

Postby debian » 2017-10-03 14:34

pylkko wrote:if you only want to move files see:

viewtopic.php?f=16&t=134786
When I connected my LG LS740 to a USB port on a friend's Windows XP computer and was able to R/W files on my LG LS740 smartphone, I did not try to perform any flashing mainly because my friend did not want me to install some additional software on to the Windows XP computer.

Or try to look through the settings on the phone what protocol you are supposed to use to connect to the storage.
On my LG LS740 smartphone, I have the USB debugging setting enabled.

Or do you need adb for flashing/debugging? The modules required for usb to work come with the kernel itself.
Yes and I need to be able to do some firmware flashing and/or performing rooting any Android smartphone using adb. My understanding is, USB drivers for most Android smartphones are included in the kernel itself. But, my computer does not even detect my LG LS740 device when I plugged it into any of the USB ports.

[quote]can you plug the phone in and the provide the output of
Code: Select all
cat /var/log/syslog
I powered up my debian stretch computer and before I plugged my LG LS740 into any of the USB ports, I excerpted the last few lines of my computer's /var/log/syslog file as shown below. When I plugged my LG LS740 smartphone into one of the USB ports, the last few lines of my computer's /var/log/syslog file remain the same (no changes).
Code: Select all
Oct  3 15:12:10 debian kernel: [   32.993979] usb 2-2: New USB device found, idVendor=0d9f, idProduct=0001
Oct  3 15:12:10 debian kernel: [   32.993987] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct  3 15:12:16 debian systemd-timesyncd[224]: Synchronized to time server [2001:738:0:860:1::2]:123 (2.debian.pool.ntp.org).
Oct  3 15:12:45 debian kernel: [   68.833453] usbhid 2-2:1.0: can't add hid device: -110
Oct  3 15:12:45 debian kernel: [   68.833500] usbhid: probe of 2-2:1.0 failed with error -110
Oct  3 15:12:46 debian mtp-probe: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:10.0/usb2/2-2"
Oct  3 15:12:46 debian mtp-probe: bus: 2, device: 2 was not an MTP device
Oct  3 15:14:02 debian systemd[1]: Created slice User Slice of debian.
Oct  3 15:14:02 debian systemd[1]: Starting User Manager for UID 1000...
Oct  3 15:14:02 debian systemd[1]: Started Session 3 of user debian.
Oct  3 15:14:02 debian systemd[488]: Reached target Paths.
Oct  3 15:14:02 debian systemd[488]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Oct  3 15:14:02 debian systemd[488]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Oct  3 15:14:02 debian systemd[488]: Listening on GnuPG cryptographic agent (access for web browsers).
Oct  3 15:14:02 debian systemd[488]: Listening on GnuPG cryptographic agent and passphrase cache.
Oct  3 15:14:02 debian systemd[488]: Reached target Sockets.
Oct  3 15:14:02 debian systemd[488]: Reached target Timers.
Oct  3 15:14:02 debian systemd[488]: Reached target Basic System.
Oct  3 15:14:02 debian systemd[488]: Reached target Default.
Oct  3 15:14:02 debian systemd[488]: Startup finished in 40ms.
Oct  3 15:14:02 debian systemd[1]: Started User Manager for UID 1000.

FYI, I do have the /etc/udev/rules.d/51-android.rules file as shown below.
Code: Select all
[debian@debian:/home/debian 7%] ~ cat /etc/udev/rules.d/51-android.rules   
SUBSYSTEM=="usb", SYSFS{idVendor}=="0502", MODE="0666", GROUP="plugdev" #Acer
SUBSYSTEM=="usb", SYSFS{idVendor}=="0b05", MODE="0666", GROUP="plugdev" #ASUS
SUBSYSTEM=="usb", SYSFS{idVendor}=="413c", MODE="0666", GROUP="plugdev" #Dell
SUBSYSTEM=="usb", SYSFS{idVendor}=="0489", MODE="0666", GROUP="plugdev" #Foxconn
SUBSYSTEM=="usb", SYSFS{idVendor}=="04c5", MODE="0666", GROUP="plugdev" #Fujitsu
SUBSYSTEM=="usb", SYSFS{idVendor}=="04c5", MODE="0666", GROUP="plugdev" #Fujitsu Toshiba
SUBSYSTEM=="usb", SYSFS{idVendor}=="091e", MODE="0666", GROUP="plugdev" #Garmin-Asus
SUBSYSTEM=="usb", SYSFS{idVendor}=="0414", MODE="0666", GROUP="plugdev" #Gigabyte
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666", GROUP="plugdev" #Google
SUBSYSTEM=="usb", SYSFS{idVendor}=="201E", MODE="0666", GROUP="plugdev" #Haier
SUBSYSTEM=="usb", SYSFS{idVendor}=="109b", MODE="0666", GROUP="plugdev" #Hisense
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666", GROUP="plugdev" #HTC
SUBSYSTEM=="usb", SYSFS{idVendor}=="12d1", MODE="0666", GROUP="plugdev" #Huawei
SUBSYSTEM=="usb", SYSFS{idVendor}=="24e3", MODE="0666", GROUP="plugdev" #K-Touch
SUBSYSTEM=="usb", SYSFS{idVendor}=="2116", MODE="0666", GROUP="plugdev" #KT Tech
SUBSYSTEM=="usb", SYSFS{idVendor}=="0482", MODE="0666", GROUP="plugdev" #Kyocera
SUBSYSTEM=="usb", SYSFS{idVendor}=="17ef", MODE="0666", GROUP="plugdev" #Lenovo
SUBSYSTEM=="usb", SYSFS{idVendor}=="1004", MODE="0666", GROUP="plugdev" #LG
SUBSYSTEM=="usb", SYSFS{idVendor}=="22b8", MODE="0666", GROUP="plugdev" #Motorola
SUBSYSTEM=="usb", SYSFS{idVendor}=="0e8d", MODE="0666", GROUP="plugdev" #MTK
SUBSYSTEM=="usb", SYSFS{idVendor}=="0409", MODE="0666", GROUP="plugdev" #NEC
SUBSYSTEM=="usb", SYSFS{idVendor}=="2080", MODE="0666", GROUP="plugdev" #Nook
SUBSYSTEM=="usb", SYSFS{idVendor}=="0955", MODE="0666", GROUP="plugdev" #Nvidia
SUBSYSTEM=="usb", SYSFS{idVendor}=="2257", MODE="0666", GROUP="plugdev" #OTGV
SUBSYSTEM=="usb", SYSFS{idVendor}=="10a9", MODE="0666", GROUP="plugdev" #Pantech
SUBSYSTEM=="usb", SYSFS{idVendor}=="1d4d", MODE="0666", GROUP="plugdev" #Pegatron
SUBSYSTEM=="usb", SYSFS{idVendor}=="0471", MODE="0666", GROUP="plugdev" #Philips
SUBSYSTEM=="usb", SYSFS{idVendor}=="04da", MODE="0666", GROUP="plugdev" #PMC-Sierra
SUBSYSTEM=="usb", SYSFS{idVendor}=="05c6", MODE="0666", GROUP="plugdev" #Qualcomm
SUBSYSTEM=="usb", SYSFS{idVendor}=="1f53", MODE="0666", GROUP="plugdev" #SK Telesys
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666", GROUP="plugdev" #Samsung
SUBSYSTEM=="usb", SYSFS{idVendor}=="04dd", MODE="0666", GROUP="plugdev" #Sharp
SUBSYSTEM=="usb", SYSFS{idVendor}=="054c", MODE="0666", GROUP="plugdev" #Sony
SUBSYSTEM=="usb", SYSFS{idVendor}=="0fce", MODE="0666", GROUP="plugdev" #Sony Ericsson
SUBSYSTEM=="usb", SYSFS{idVendor}=="2340", MODE="0666", GROUP="plugdev" #Teleepoch
SUBSYSTEM=="usb", SYSFS{idVendor}=="0930", MODE="0666", GROUP="plugdev" #Toshiba
SUBSYSTEM=="usb", SYSFS{idVendor}=="19d2", MODE="0666", GROUP="plugdev" #ZTE
[debian@debian:/home/debian 8%] ~
debian
 
Posts: 153
Joined: 2007-02-24 14:27

Re: adb devices could not detect my LG LS740

Postby pylkko » 2017-10-03 16:25

Believe it or not, some phones don't allow adb if mtp (or ptp) is not allowed. Does your Debian machine have libmtp-common installed? Do you have android-tools-adbd installed?

Can you access the storage in a file manager?
Can you access storage on it if you boot into recovery or fastboot?

Do you see it in lsusb?

can you show
Code: Select all
/etc/udev/rules.d/51-android.rules


is your user in the plugdev group?
or are you running the daemon as root?

EDIT:

sorry man, I see that you already posted the udev rules. I see you have an LG entry in there, but does it correspond to the vendor id that your phone has?
User avatar
pylkko
 
Posts: 1174
Joined: 2014-11-06 19:02

Re: adb devices could not detect my LG LS740

Postby debian » 2017-10-03 23:35

pylkko wrote:Believe it or not, some phones don't allow adb if mtp (or ptp) is not allowed. Does your Debian machine have libmtp-common ]installed? Do you have android-tools-adbd installed?
Both the libmtp-common and android-tools-adb are already installed

Can you access the storage in a file manager?
Can you access storage on it if you boot into recovery or fastboot?

Do you see it in lsusb?
lsusb shows nothing about the LG LS740 when it is plugged into one of the USB ports (see be;low. At the moment, I can't access the GUI desktop. The display shows a blank screen. So, I won't know if I can access the storage in a file manager. If you know how to access the storage through a CLI, please let me know and I will be more than happy to give it a try. I have not tried to boot into recovery or fastboot (which I have no idea how to do this fastboot).
Code: Select all
[root@debian:/home/debian 17%] # lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 09be:0001 MySmart.Com MySmartPad
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0d9f:0001 Powercom Co., Ltd Uninterruptible Power Supply
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[root@debian:/home/debian 18%] #

is your user in the plugdev group?
Yes.

or are you running the daemon as root?
If you meant running adb devices as root, then the answer is yes.
debian
 
Posts: 153
Joined: 2007-02-24 14:27

Re: adb devices could not detect my LG LS740

Postby pylkko » 2017-10-04 06:30

Storage devices can be viewed with
Code: Select all
lsblk
, but if you cannot see it at all, chances are you wont see it there either.
Fastboot and recovery boot are the two other boot modes on android phones.
I don't know of what more to try. Except maybe fastboot, given that it is so simple, that is, there are significantly less confounding factors. either you see the device or not.

Or try chaging from mtp to ptp or vice versa.

Or maybe create a adb_usb.ini file manually.

your tail /var/log/syslog has these errors:

Code: Select all
Oct  3 15:12:45 debian kernel: [   68.833453] usbhid 2-2:1.0: can't add hid device: -110
Oct  3 15:12:45 debian kernel: [   68.833500] usbhid: probe of 2-2:1.0 failed with error -110
Oct  3 15:12:46 debian mtp-probe: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:10.0/usb2/2-2"
Oct  3 15:12:46 debian mtp-probe: bus: 2, device: 2 was not an MTP device


Something was trying to be recognized as a usbhid (keyboard etc) device. Also, there is a mtp-probe failure. Maybe doing an internet search on these might help. My understanding is that there is also a default fallback udev rule which is mtp-based.

maybe try to plug it in again and look at
Code: Select all
lsusb
and
Code: Select all
journalctl -fe
, try to get mor data somehow.
User avatar
pylkko
 
Posts: 1174
Joined: 2014-11-06 19:02

Re: adb devices could not detect my LG LS740

Postby debian » 2017-10-05 16:28

I re-installed debian stretch. During the installation, I had two Android smartphones, i.e. LG LS740 and HTC Desiree 510, plugged into the USB ports on my computer and only the HTC was detected during the installation. Now that the installation is done and the computer is booted, I see dmesg shows only the HTC smartphone (see below).
Code: Select all
[    3.604089] usb 1-6: new high-speed USB device number 4 using ehci-pci
[    3.753150] usb 1-6: New USB device found, idVendor=0bb4, idProduct=064e
[    3.753222] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.753280] usb 1-6: Product: Android Phone
[    3.753334] usb 1-6: Manufacturer: HTC
[    3.753390] usb 1-6: SerialNumber: xxxxxxxxxxxx
[    3.772937] usb-storage 1-6:1.2: USB Mass Storage device detected
[    3.773332] scsi host2: usb-storage 1-6:1.2
[    3.773751] usbcore: registered new interface driver usb-storage
[    3.775230] usbcore: registered new interface driver uas
[    3.960783] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[    4.805213] scsi 2:0:0:0: Direct-Access     HTC      Android Phone    0000 PQ: 0 ANSI: 2
[    4.806191] scsi 2:0:0:1: CD-ROM            HTC      Android Phone    0000 PQ: 0 ANSI: 2
[    4.814016] sr 2:0:0:1: [sr1] scsi-1 drive
[    4.814679] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[    4.815046] sr 2:0:0:1: Attached scsi CD-ROM sr1

Right now, the /etc/udev/rules directory is empty, i.e. no 51-android.rules file. Yet, when I executed adb devices for the 1st time, it spitted out some error messages as shown below. However, the subsequent 2nd run indicates adb found my HTC, but flagged as unauthorized. If I installed /etc/udev/rules/51-android.rules file, adb will not detect my LG phone and will show the same that my HTC is unauthorized.
Code: Select all
[root@debian:/home/debian 19%] # [b]adb devices[/b]
List of devices attached
* daemon not running. starting it now on port 5037 *
*** Error in `adb': free(): invalid pointer: 0x00b8e390 ***
======= Backtrace: =========
/lib/i386-linux-gnu/libc.so.6(+0x6737a)[0xb732837a]
/lib/i386-linux-gnu/libc.so.6(+0x6dfb7)[0xb732efb7]
/lib/i386-linux-gnu/libc.so.6(+0x6e7f6)[0xb732f7f6]
/usr/lib/i386-linux-gnu/libcrypto.so.1.1(CRYPTO_free+0x39)[0xb717ab39]
/usr/lib/i386-linux-gnu/libcrypto.so.1.1(CRYPTO_secure_free+0x1e1)[0xb717be41]
/usr/lib/i386-linux-gnu/libcrypto.so.1.1(+0x8bd16)[0xb70e5d16]
/usr/lib/i386-linux-gnu/libcrypto.so.1.1(BN_clear_free+0x87)[0xb70e5da7]
/usr/lib/i386-linux-gnu/libcrypto.so.1.1(RSA_free+0x9f)[0xb71a481f]
/usr/lib/i386-linux-gnu/android/libadb.so.0(+0x249bc)[0xb76a49bc]
/usr/lib/i386-linux-gnu/android/libadb.so.0(+0x2551f)[0xb76a551f]
/usr/lib/i386-linux-gnu/android/libadb.so.0(_Z13adb_auth_initv+0x56)[0xb76a5ec6]
adb(+0x72f9)[0x4be2f9]
adb(+0xc603)[0x4c3603]
adb(main+0x39)[0x4bbdb9]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6)[0xb72d9276]
adb(+0x4e32)[0x4bbe32]
======= Memory map: ========
004b7000-004da000 r-xp 00000000 08:03 140        /usr/lib/android-sdk/platform-tools/adb
004da000-004db000 r--p 00022000 08:03 140        /usr/lib/android-sdk/platform-tools/adb
004db000-004dc000 rw-p 00023000 08:03 140        /usr/lib/android-sdk/platform-tools/adb
00b88000-00bad000 rw-p 00000000 00:00 0          [heap]
b5d00000-b5d29000 rw-p 00000000 00:00 0
b5d29000-b5e00000 ---p 00000000 00:00 0
b5f00000-b5f21000 rw-p 00000000 00:00 0
b5f21000-b6000000 ---p 00000000 00:00 0
b6049000-b604a000 ---p 00000000 00:00 0
b604a000-b684a000 rw-p 00000000 00:00 0
b684a000-b684b000 ---p 00000000 00:00 0
b684b000-b704d000 rw-p 00000000 00:00 0
b704d000-b7050000 r-xp 00000000 08:03 1048587    /lib/i386-linux-gnu/libdl-2.24.so
b7050000-b7051000 r--p 00002000 08:03 1048587    /lib/i386-linux-gnu/libdl-2.24.so
b7051000-b7052000 rw-p 00003000 08:03 1048587    /lib/i386-linux-gnu/libdl-2.24.so
b7052000-b7058000 r-xp 00000000 08:03 112        /usr/lib/i386-linux-gnu/android/liblog.so.0
b7058000-b7059000 r--p 00005000 08:03 112        /usr/lib/i386-linux-gnu/android/liblog.so.0
b7059000-b705a000 rw-p 00006000 08:03 112        /usr/lib/i386-linux-gnu/android/liblog.so.0
b705a000-b72a5000 r-xp 00000000 08:03 267159     /usr/lib/i386-linux-gnu/libcrypto.so.1.1
b72a5000-b72a6000 ---p 0024b000 08:03 267159     /usr/lib/i386-linux-gnu/libcrypto.so.1.1
b72a6000-b72b7000 r--p 0024b000 08:03 267159     /usr/lib/i386-linux-gnu/libcrypto.so.1.1
b72b7000-b72be000 rw-p 0025c000 08:03 267159     /usr/lib/i386-linux-gnu/libcrypto.so.1.1
b72be000-b72c1000 rw-p 00000000 00:00 0
b72c1000-b7472000 r-xp 00000000 08:03 1048584    /lib/i386-linux-gnu/libc-2.24.so
b7472000-b7473000 ---p 001b1000 08:03 1048584    /lib/i386-linux-gnu/libc-2.24.so
b7473000-b7475000 r--p 001b1000 08:03 1048584    /lib/i386-linux-gnu/libc-2.24.so
b7475000-b7476000 rw-p 001b3000 08:03 1048584    /lib/i386-linux-gnu/libc-2.24.so
b7476000-b7479000 rw-p 00000000 00:00 0
b7479000-b7495000 r-xp 00000000 08:03 1048580    /lib/i386-linux-gnu/libgcc_s.so.1
b7495000-b7496000 r--p 0001b000 08:03 1048580    /lib/i386-linux-gnu/libgcc_s.so.1
b7496000-b7497000 rw-p 0001c000 08:03 1048580    /lib/i386-linux-gnu/libgcc_s.so.1
b7497000-b74ea000 r-xp 00000000 08:03 1048588    /lib/i386-linux-gnu/libm-2.24.so
b74ea000-b74eb000 r--p 00052000 08:03 1048588    /lib/i386-linux-gnu/libm-2.24.so
b74eb000-b74ec000 rw-p 00053000 08:03 1048588    /lib/i386-linux-gnu/libm-2.24.so
b74ec000-b74ee000 rw-p 00000000 00:00 0
b74ee000-b765e000 r-xp 00000000 08:03 267079     /usr/lib/i386-linux-gnu/libstdc++.so.6.0.22
b765e000-b7664000 r--p 0016f000 08:03 267079     /usr/lib/i386-linux-gnu/libstdc++.so.6.0.22
b7664000-b7665000 rw-p 00175000 08:03 267079     /usr/lib/i386-linux-gnu/libstdc++.so.6.0.22
b7665000-b7668000 rw-p 00000000 00:00 0
b7668000-b7673000 r-xp 00000000 08:03 126        /usr/lib/i386-linux-gnu/android/libcutils.so.0
b7673000-b7674000 r--p 0000a000 08:03 126        /usr/lib/i386-linux-gnu/android/libcutils.so.0
b7674000-b7675000 rw-p 0000b000 08:03 126        /usr/lib/i386-linux-gnu/android/libcutils.so.0
b7675000-b767e000 r-xp 00000000 08:03 119        /usr/lib/i386-linux-gnu/android/libbase.so.0
b767e000-b767f000 r--p 00008000 08:03 119        /usr/lib/i386-linux-gnu/android/libbase.so.0
b767f000-b7680000 rw-p 00009000 08:03 119        /usr/lib/i386-linux-gnu/android/libbase.so.0
b7680000-b76b3000 r-xp 00000000 08:03 133        /usr/lib/i386-linux-gnu/android/libadb.so.0
b76b3000-b76b4000 r--p 00032000 08:03 133        /usr/lib/i386-linux-gnu/android/libadb.so.0
b76b4000-b76b5000 rw-p 00033000 08:03 133        /usr/lib/i386-linux-gnu/android/libadb.so.0
b76b5000-b76ce000 r-xp 00000000 08:03 1048598    /lib/i386-linux-gnu/libpthread-2.24.so
b76ce000-b76cf000 r--p 00018000 08:03 1048598    /lib/i386-linux-gnu/libpthread-2.24.so
b76cf000-b76d0000 rw-p 00019000 08:03 1048598    /lib/i386-linux-gnu/libpthread-2.24.so
b76d0000-b76d2000 rw-p 00000000 00:00 0
b76f6000-b76f9000 rw-p 00000000 00:00 0
b76f9000-b76fb000 r--p 00000000 00:00 0          [vvar]
b76fb000-b76fd000 r-xp 00000000 00:00 0          [vdso]
b76fd000-b7720000 r-xp 00000000 08:03 1048579    /lib/i386-linux-gnu/ld-2.24.so
b7720000-b7721000 r--p 00022000 08:03 1048579    /lib/i386-linux-gnu/ld-2.24.so
b7721000-b7722000 rw-p 00023000 08:03 1048579    /lib/i386-linux-gnu/ld-2.24.so
bf92f000-bf950000 rw-p 00000000 00:00 0          [stack]
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
[root@debian:/home/debian 20%] # [b]adb devices -l[/b]
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
xxxxxxxxxxxx           unauthorized usb:1-6

[root@debian:/home/debian 21%] #

Below is the output from lsblk you requested.
Code: Select all
[root@debian:/home/debian 41%] # lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
fd0      2:0    1    4K  0 disk
sda      8:0    0 37.3G  0 disk
├─sda1   8:1    0  9.3G  0 part
├─sda2   8:2    0  3.7G  0 part [SWAP]
└─sda3   8:3    0 24.2G  0 part /
sr0     11:0    1 1024M  0 rom 
sr1     11:1    1 17.2M  0 rom 
[root@debian:/home/debian 42%] #

I will try to find out how to do the fastboot and/or recovery boot on my LG phone to see if they will make any difference. I will also look into how to change from mtp to ptp or vice versa.

Or maybe create a adb_usb.ini file manually.
I don't know how to do this. I certainly will appreciate more information on this.

your tail /var/log/syslog has these errors:

Code: Select all
Oct  3 15:12:45 debian kernel: [   68.833453] usbhid 2-2:1.0: can't add hid device: -110
Oct  3 15:12:45 debian kernel: [   68.833500] usbhid: probe of 2-2:1.0 failed with error -110
Oct  3 15:12:46 debian mtp-probe: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:10.0/usb2/2-2"
Oct  3 15:12:46 debian mtp-probe: bus: 2, device: 2 was not an MTP device


Something was trying to be recognized as a usbhid (keyboard etc) device. Also, there is a mtp-probe failure. Maybe doing an internet search on these might help. My understanding is that there is also a default fallback udev rule which is mtp-based.
The syslog file I posted earlier was caputered before I even had my LG phone plugged into any of the USB port. I suspect it is from a Powercom Co., Ltd Uninterruptible Power Supply connected to one of the USB ports.
debian
 
Posts: 153
Joined: 2007-02-24 14:27

Re: adb devices could not detect my LG LS740

Postby pylkko » 2017-10-05 16:52

About the syslog, it's not going to help if you don't plug the phone in. Plug in and tail syslog or use journalctl imediately after. Does your machine have an optical disk drive or what are those rom block devices? The second one /dev/sr1 appears to be the other phone displaying itself as a cd-rom (phones can also do that). But what is /dev/sr0 then?

Also, found this bug report where the same crashing of the daemon on the same libcrypto is mentioned:
https://bugs.archlinux.org/task/55693

EDIT:
appears to have been reported in Debian even earlier:
https://bugs.debian.org/cgi-bin/bugrepo ... bug=858764

also:
https://bugs.launchpad.net/ubuntu/+sour ... ug/1711769

Also found this thread where people are complaining that they cannot get the LS740 to show up as a device on windows...
https://forum.xda-developers.com/showth ... 703&page=3
User avatar
pylkko
 
Posts: 1174
Joined: 2014-11-06 19:02


Return to General Questions

Who is online

Users browsing this forum: No registered users and 7 guests

fashionable