Davide Cavestro

@jock Just an update about booting HK1 rbox r1 having a crappy emmc (cannot erase the bootloader using multitool nor dd) I initially spent some time trying to fill the gap between the multitool boot process and other images since I was able to boot multitool from sdcard but not armbian nor libreelec. Provided that I'm still far from a deep understanding of the whole boot process, I saw that - simply overwriting u-boot on the sdcard - then both armbian and libreelec can boot even if the emmc still have its bootloader in place, that is when I remove the sdcard I can see the original boot splash screen. All credits go to gausus at https://dietpi.com/forum/t/dietpi-on-rk3328-rk3318-tvbox/15587 Following his steps, I simply extract uboot from multitool image, then copy it in two chunks to the sdcard (I can provide full steps here in case someone is interested) This way I can boot Armbian_23.08.0-trunk_Rk3318-box_bookworm_edge_6.3.13_minimal.img without further changes, while for LibreELEC-RK3328.arm-11.0.3-a1.img I had to place rk3318-box.dtb on the sd and change the FDT entry on /extlinux/extlinux.conf

So I got a crappy rk3318 tvbox with internal emmc probably bad soldered. Since it stopped working, I booted it with the multitool, saw that erase mmc fails, but the terminal works. GIven that I'm here to learn having fun, I gave a look at multitool and saw it generates a rootfs with a selection of debian packages. So why not trying to reuse it pre-installing busybox, kodi, etc, then replace the menu with a proper init i.e. to start kodi standalone? So my question: why the choice to use an NTFS as main partition? Just as an easy way to make it readable to most systems?