6P ADB : no connection

circ · 24 Dec 2020, 04:18

I've installed UBports on a factory new 6P successfully with (mostly) these steps.

I'm having a time getting adb to connect.
Am I missing or forgetting something I need to do?

When I recover to TWRP adb shell works fine.
When in UBports, developer mode on, adb doesn't see the 6P:

» adb shell                                                                                                                                        
error: no devices/emulators found

In recovery, fasboot is also ok:

» fastboot devices                                                                                                                                 
ABCXXXXXXX123	fastboot

I have tried adding a device code:

» cat ~/.android/adb_usb.ini                                                                                                                      
0x18d1

then , unplugging, resarting adb, plugging back in.

adb is running great and I'm able to connect to other UBports devices through the same cable.
host syslog has no message when the 6P gets plugged in.

A Former User · 24 Dec 2020, 14:00

@circ
adb isn't working.
you can try ssh instead.

circ · 24 Dec 2020, 21:46

Thanks.
For reference here is SSH access info.

Enabled via Terminal app :
sudo service start ssh

Not sure how to get a key on there without ADB, but looking.

A Former User · 24 Dec 2020, 21:58

@circ
if you want to move the key to your device you can use MTP

http://docs.ubports.com/en/latest/userguide/advanceduse/ssh.html

wgarcia · 25 Dec 2020, 10:21

Another way is to put the key in a server where you have an account, and tranfer it to the device from the server using sftp.

circ · 30 Dec 2020, 18:30

Thanks.

I managed to get a key onto the 6P by dropping it into a web page on a local server, opening on 6P, and copy/pasting to ./.ssh/authorized_keys following instructions here.

I have access while UT is running, but not in recovery (TWRP) or bootloader.

flohack · 31 Dec 2020, 18:23

ADB is currently not supported on any of the new Halium devices, sorry for that...

Not an easy solution, ssh was thought to be a replacement, but of course it needs network...

BR