+- PINE64 (https://forum.pine64.org)
+-- Forum: ROCKPRO64 (https://forum.pine64.org/forumdisplay.php?fid=98)
+--- Forum: Android on RockPro64 (https://forum.pine64.org/forumdisplay.php?fid=100)
+--- Thread: adb connection failed (/showthread.php?tid=6472)
adb connection failed - jylee650 - 08-28-2018
I can not connect adb using USB-C or TCP.
- Using USB type C to C
no device
- Using tcp(ping is succeed)
adb connect 192.168.1.134
unable to connect to 192.168.1.134:5555: Connection refused
If someone succeeds, please help me.
Thank you!
RE: adb connection failed - dukla2000 - 08-28-2018
It works fine for me, check the wiki here.
Note use of the top USB2 port has NOT been verified - looking at the schematic it seems it may in fact be the type 3 USB A port that is OTG. But for sure I have had no problems with the type C port
RE: adb connection failed - Firesped - 08-28-2018
I'm also trying to get this working. when I plugged into the USB 2.0 OTG port. nothing happened. I found a type-c to type-a cable and plugged it in. my computer recognized a new device.
I am using adb to sideload gapps from opengapps.org.
however the signature verification failed.
error: 21
it seems to be timing out at around 50% of file transfer.
RE: adb connection failed - blitzfr - 12-06-2018
I have the exact same problem.
adb devices return no device.
adb connect is falling despite that the ping is working.
I did try on android 7 and android 8. I also tried on all usb 2 ports. For usb c, I use a hub c to 3 and connect it to the MacBook pro. Also note that I tried on a MacPro with ubuntu.
lsusb on both machines, never show the rockpro64 :/ and adb is not working.
On the device itself I am developer mode and try all transfer mode possible (MTP, PTP...)
please help!
RE: adb connection failed - blitzfr - 12-08-2018
Actually, I bought a usb c to usb 3 and it works now.