No USB connection - phone not seen!
@plainenough - I have been using the phone without the back extensively for cooling while testing.
Replaced back and:
1) held vol^ + power until RED led, eMMC UBPorts - udevadm monitor = no change.
2) held vol^ + power until GREEN led, eMMC UBPorts screen shows 'Awaiting command' - udevadm monitor responded (extract below, see https://bpa.st/MGTA):
ID_VENDOR=Pine64
ID_VENDOR_ENC=Pine64
ID_VENDOR_ID=1209
ID_MODEL=PinePhone
ID_MODEL_ENC=PinePhone
ID_MODEL_ID=4201
ID_REVISION=0506
ID_SERIAL=Pine64_PinePhone_Jumpdrive
ID_SERIAL_SHORT=Jumpdrive
ID_BUS=usb
ID_USB_INTERFACES=:0202ff:0a0000:080650:
ID_VENDOR_FROM_DATABASE=Generic
MAJOR=189
MINOR=3
Pc file system now shows various mounted partitions:
1.0 MB - boot.scr.
2.6 GB - android, bin, boot, dev, etc, home (etc).
67 MB - lost+gounf, dtb, initrd.img, vmlinux.
67 MB - lost+found, modules, config-5.6.0-pine64, dtb, initrd.img, System.map-5.6.0-pine64, vmlinuz.
8.4 MB - lost-found.
cache - lost+found, recovery, system-image-upgrader.log.
userdata - android-data, system-data, user-data, .last_update, SWAP.img.
So it appears the usb/ethernet is probably electrically functional?
Normally booting the phone from eMMC/SD either inhibits usb starting or stops it. UBPorts direct flash mode provides apparently normal usb access leaving the phone in a state 'Awating command'. Does this imply that reflashing eMMC would solve the issue?
Replaced back and:
1) held vol^ + power until RED led, eMMC UBPorts - udevadm monitor = no change.
2) held vol^ + power until GREEN led, eMMC UBPorts screen shows 'Awaiting command' - udevadm monitor responded (extract below, see https://bpa.st/MGTA):
ID_VENDOR=Pine64
ID_VENDOR_ENC=Pine64
ID_VENDOR_ID=1209
ID_MODEL=PinePhone
ID_MODEL_ENC=PinePhone
ID_MODEL_ID=4201
ID_REVISION=0506
ID_SERIAL=Pine64_PinePhone_Jumpdrive
ID_SERIAL_SHORT=Jumpdrive
ID_BUS=usb
ID_USB_INTERFACES=:0202ff:0a0000:080650:
ID_VENDOR_FROM_DATABASE=Generic
MAJOR=189
MINOR=3
Pc file system now shows various mounted partitions:
1.0 MB - boot.scr.
2.6 GB - android, bin, boot, dev, etc, home (etc).
67 MB - lost+gounf, dtb, initrd.img, vmlinux.
67 MB - lost+found, modules, config-5.6.0-pine64, dtb, initrd.img, System.map-5.6.0-pine64, vmlinuz.
8.4 MB - lost-found.
cache - lost+found, recovery, system-image-upgrader.log.
userdata - android-data, system-data, user-data, .last_update, SWAP.img.
So it appears the usb/ethernet is probably electrically functional?
Normally booting the phone from eMMC/SD either inhibits usb starting or stops it. UBPorts direct flash mode provides apparently normal usb access leaving the phone in a state 'Awating command'. Does this imply that reflashing eMMC would solve the issue?
