Mac is not even detecting anything.
@FelixKa , can I ask you to generate a sha256 checksum for lenovo-cd-18781y-rootfs.img and lenovo-cd-18781y-rootfs.sha256 ? it could be 7-zip messing with me while extracting the tarball+.xz.
https://felix.kaechele.ca/projects/thinksmart/CHECKSUM doesnât hold sha256 for lenovo-cd-18781y-rootfs.img and lk2nd.img Iâm afraid :') (but for the archives and lk2nd-lenovo-cd-18781y-20240227.img âŚ
No worries, appreciate you are doing all this in your spare time so no rush 
Giving an update here - tried installing @mattmon rom on it first now, after that installing yours @FelixKa ⌠not it boots with HA-logo first and then jumps into a very dim screen with 19:00. Read that somebody else see the dim screen, so will play around more tomorrow. Thanks so far!
1 Like
Yeah, that suggests you might have another display variant. If you can get a dmesg output from the stock ROM thatâd be great.
I will be happy to, can you give me some hints on how to access a terminal on it ? ssh from windows somehow ?
adb root
adb shell dmesg
Thanks @mattmon, Iâm struggling with a CDC NCM USB driver to be able to use adb on Windows with this device. Will put dmesg dump once Iâm getting around this (feel free to let me know if you know how, Install OEM USB drivers | Android Studio | Android Developers doesnât seem to work with the device it finds).
I donât use windows, but pretty sure @Nerwyn can help you, check out his posts in my thinksmart thread.
I havenât managed to get it to work (yet) on Windows 10 - when the device is in EDL mode it perfectly fine identifies as a Qualcomm device and âQualcomm HS-USB QDLoader 9008â driver loads well. When not in EDL mode (booted up with the dim display showing 19:00 clock) it identifies as a âCDC NCMâ where I havenât managed to find a working driver. I can add a Google Legacy ADB driver (âAndroid ADB Interfaceâ), but that doesnât make a difference.
@mattmon, with your rom on my other device I am able to use adb without problems (getting identified as âQualcomm HS-USB Android DIAG 901Dâ according to Windows). Hope @FelixKa perhaps can give us some hints on differences in the usb requirements in edl/non-edl on his 20240227 buildâŚ
@FelixKaâs images should boot up with the usb port being exposed to the host as a CDC-ECM network adapter.
Adb is, for the most part, android specific
Edit for clarity:
Every thinksmart has QDL and fastboot modes, provided by the bootloader and allows the respective client software to connect and flash images to the emmc.
There is only a difference after the kernel loads.
For Linux, usb will appear as whatever itâs been configured as (for the pmos rom in this thread, itâs cdc-ecm.)
For android, itâs exposed as an Android Debug Bridge or âadbâ interface.
Have you tried minimal adb and fastboot? Itâs old, but still what Iâve used.
https://xdaforums.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
FIRST robotics? Good luck on your competition! I coach an FLL team comprised of 5th and 6th grade students from my elementary school. Theyâre going to regionals next week 
Indeed. FRC Team 7200 
Thanks for wishing us good luck. Weâre going to need at least a little of that too 
2 Likes
You guys are too cool, those kids probably see you as digital superheroes.
1 Like
Perhaps thatâs where all the confusion kicked in - you replied
but that would only work on Android rom, and not the PMos rom, correct ? 
Iâd say itâs not just those kids 
Then again, maybe Iâm still a kid at heart. At any rate Iâm looking in awe at all the progress Felix, Deadman, and everyone here is making. Itâs so impressive.
1 Like
Correct.
You can use those commands to determine your lcd type from android.
You can also do the same from linux, just omit the adb stuff.
Even better, pipe dmesg through grep to filter irrelevant lines:
dmesg | grep mdss
First, thanks for all the effort for putting this together! Itâs an exciting project.
Iâve got my View running PMOS and would like to get some more usable space on the disk. Any suggestions on what could be done to free up some?