<flokli>
it's just pads from something on the backside?
<grw>
hm unsure
<grw>
do you have 4g version? looks like unpopulated antenna connect at top
<flokli>
yes, that's a 4g version, and I do have 4g connectivity
<flokli>
so no clue what this connector is used for
<flokli>
the motherboard seems to be glued to the back as well, like the battery…
<flokli>
doesnt look like anything on the back, from a quick peek
<flokli>
I suggest we try your USB cable first :-P
<grw>
ya seems likely
<grw>
the linux cmdline has console=ttyMT0,921600n1 so evidently someone has been usig it
<flokli>
which is good, so we probably don't need to fiddle around with the bootloader like in the article, but probably already have a serial from android :-)
<flokli>
btw, did I simply overlook adb console, or is this option missing from developer settings? :-/
<grw>
i didnt look for adb
<grw>
i see there is another "rooted" fw image, maybe that has it
<flokli>
kk
<grw>
well, i get a lot of noise on both usb port
<grw>
but nothing intelligible
<sphalerite>
if you want a root shell on android, a rooted image + adb is probably the easiest way
<flokli>
sphalerite: it's more about serial in general... Poking with the bootloader, getting another kernel to work etc
<sphalerite>
ah right
<flokli>
grw: did you simply use one of those dumb usb-c to micro USB adapters?
<flokli>
Plus the tutorial you posted?
<grw>
i used a USB-A OTG adapter and a dissected usb cable