Quote:
Originally Posted by Renate
1) How are you sure that "adb reboot edl" doesn't work? Does it just boot normally? What happens.
|
adb devices -l never shows anything connected, no devices for it to send the command to. adb reboot edl comes back with no devices/emulators found. the tablet just loops over and over with the output in the pastebin below.
Quote:
|
2) I still haven't seen a log from abltest when you started it before reset.
|
I'm not certain what/how to perform the reset you mention. If I hold the button down too long, it powers off. If I hold it less than too long the bootloop just continues, it doesn't seem to do anything.
With abltest running, I've started the device from power off state multiple times. I've also disconnected the battery and plugged it back in which I think would be a cold boot and not a warm boot. All whild abltest is running/listening.
Does abltest prefer a warm or cold boot?
Pastebin of two boot cycles at
http://pastebin.com/3Ege96wa
Quote:
|
3) The Windows driver for the FTDI is for the USB UART, not the Onyx.
|
I understand. The FTDI usb to serial driver is for the internal connection on the Note 2 where I've captured putty and abltest logs.
The USB connection from my PC to the USB-C port on the Note 2 doesn't register a connection to the device...the PC, adb never recognize the device being plugged in, never sees it.
I plug an old samsung tablet running android 9 into the PC and windows does it ding-dong with a pop-up. Never installed samsung specific drivers (or any android drivers for that matter, just the android developer kit so I could get adb) and windows saw it right away. For adb to see it I had to enable USB debugging in developer options. After that it sees it in adb devices -l , no problem. I have an old android phone I'm going to test once it charges up, but I have a feeling it might work just like the samsung.