CumeBox cm2-b (v2023.01)

u-boot-cm2-b.bin is the u-boot binary which could be used as BL33 or a bare metal program payload

• booting order is: usb0 -> mmc0(sd) -> mmc1 (emmc) -> pxe -> dhcp

cm2-b-u-boot.bin.sd.bin is the bootloader image containing the slightly modified u-boot as BL33

• addtionally it would read env from mmcblk2 offset 0xfa000 size 0x6000

cm2-b-bare-minimum.img is the USB burning image but with all of Android partitions removed, all it could do is to restore the box to a state where you can boot external systems.

sha256sums:

04f3b1eabe8092ad5708e1ede867ef687275ace39433ce575d98bb8d2029b9af  cm2-b-bare-minimum.img
733827e948611c83b891fd0e01b1415d43cc2715a228ed8ef01cf9cedf160b94  cm2-b-u-boot.bin.sd.bin
029262d0895016735ed2577b8cd249a9a0a53f077eab8da8f8f74746a35abb73  u-boot-cm2-b.bin

Xiaomi MiBox 3/3C [MDZ-16-AA] (v2023.01)

u-boot-mibox3.bin is the u-boot binary which could be used as BL33 or a bare metal program payload

• booting order is: usb0 -> mmc1 (emmc)

mibox3-u-boot.bin.sd.bin is the bootloader image containing the slightly modified u-boot as BL33

• addtionally it would read env from mmcblk2 offset 0xf0000 size 0x10000

mibox3-bare-minimum.img is the USB burning image but with all of Android partitions removed, all it could do is to restore the box to a state where you can boot external systems.

mibox3-bare-but-mainline-uboot.img is similar to the above one, but it contains the above bootloader image (mibox3-u-boot.bin.sd.bin) containing mainline u-boot, instead of the stock Xiaomi one

sha256sums:

b7201a3d198aaeb891086fea9a59d3af9ef32c93bc23b92721b9719560b75cee  mibox3-bare-but-mainline-uboot.img
35c6b6f743b5893f8372e897ffe24935fb88913042031035cc27f1fb20f4a0bb  mibox3-bare-minimum.img
3b72906f0eecc95eda1d4b56888e48ee5b95fcf64bd14f89182ea2c23cb2e5ab  mibox3-u-boot.bin.sd.bin
dbf588904b5936b2943c0d35cebe8d9b95a988a97ea39675508f7bccde41bf76  u-boot-mibox3.bin

UNIONMAN UNT403A (v2023.01)

u-boot-unt403a.bin is the u-boot binary which could be used as BL33 or a bare metal program payload

• booting order is: usb0 -> mmc1 (emmc) -> pxe -> dhcp

unt403a-u-boot.bin.sd.bin is the bootloader image containing the slightly modified u-boot as BL33

• addtionally it would read env from mmcblk2 offset 0xf0000 size 0x10000, if you want to store the env it's recommended to write it to mmcblk2boot0 or mmcblk2boot1 since its size is larger than 0xf0000

unt403a-bare-minimum.img is the USB burning image but with all of Android partitions removed, all it could do is to restore the box to a state where you can boot external systems.

sha256sums:

3b64d3ff5ad13668945763f52bba0cca04ec072a7bd79011b3cfa2adc7a36e3e  u-boot-unt403a.bin
2649cd646b0970e2bfdcecd9cdc7499c24b40d6b322afb2680e5391dbad5b569  unt403a-bare-minimum.img
1fbb39f7814d933e9a90b756cf6c3a14aa6444ff8bba655b8a5fc77c291fe996  unt403a-u-boot.bin.sd.bin

BesTV R3300L (v2023.01)

• The u-boot-r3300l.bin is the raw binary that should be executed as BL33 or a bare metal program payload on the box (e.g. with fatload then go)

  • The booting order is set to usb0 -> mmc0 (sd) -> mmc1 (emmc) -> pxe -> dhcp

• The r3300l-u-boot.bin.sd.bin is the image that should be written to the head of the eMMC (it contains addtional 512 byte, so it needs dd quirks as always, dd 442 then 512 with skip and seek)

  • Additionally, u-boot env is saved at mmc1 offset 0xf0000 size 0x10000, ending at 1MiB offset, so you can freely create MBR partitions on eMMC, and can edit u-boot env from within a system with the following fw_env.config

    /dev/mmcblk2 0xf0000 0x10000
    

• The r3300l-milton-bare.img is Milton's Android burning image but with most of its partition removed, it can be used to rescue the box to a bootable state (into Amlogic u-boot, then probably your external system, but not to Android, as it's incomplete) without having to burn the whole Andorid system, it does not contain the u-boot here actually so you need to burn it afterwards.