[Android Head-Units] maxou2:
Just made a deep study and tests on this unit, here my results, thoughts, mods and other considerations hoping this will help.

Being scared to brick the unit I used a conservative approach by making step by step mods rather than flash the firmware at the first post.

Here's my changment pattern:

Firmware : Before rooting I updated to the last version of the firmware the vendor gave me ( the latest OEM firmware ).

It's an OTA update ( use the "five fingers screen touch & move" method ) after putting the the files .bin and .upd in a USB key connected to a USB port when you powerup the unit.

I enclose a link to download it.

OTA update

I've made a DUMP of the partitions ( by using the SP tool Readback feature, you can find a lot of tutos on the internet how to use it ) and with the WwR tools i managed to have a full flashable original FW backup.

Another interesting method is to retrieve the partition content on a "live" system by use a shell and the dd unix command :

Enable the developer option on the system and connect the 4 wire USB port to a PC ( by using a 4 wire male to male USB cable ).

If you have an ADB command environment installed on your PC you can just fire a "adb shell" command,

followed by an "su @#zxcvbnmasdfghjklqwertyuiop1234567890,." to have a shell with superuser rights.

Now you can navigate trought your file system as root.

Anyway here's the partions table :

/dev/block/platform/soc/11230000.mmc/by-name # ls -l

lrwxrwxrwx 1 root root 21 Dec 3 14:26 ANDROID -> /dev/block/mmcblk0p24

lrwxrwxrwx 1 root root 20 Dec 3 14:26 ARM2 -> /dev/block/mmcblk0p9

lrwxrwxrwx 1 root root 21 Dec 3 14:26 BOOTIMG -> /dev/block/mmcblk0p10

lrwxrwxrwx 1 root root 21 Dec 3 14:26 CACHE -> /dev/block/mmcblk0p25

lrwxrwxrwx 1 root root 21 Dec 3 14:26 DKB -> /dev/block/mmcblk0p22

lrwxrwxrwx 1 root root 21 Dec 3 14:26 EXPDB -> /dev/block/mmcblk0p20

lrwxrwxrwx 1 root root 21 Dec 3 14:26 FRP -> /dev/block/mmcblk0p23

lrwxrwxrwx 1 root root 21 Dec 3 14:26 KB -> /dev/block/mmcblk0p21

lrwxrwxrwx 1 root root 20 Dec 3 14:26 LK -> /dev/block/mmcblk0p6

lrwxrwxrwx 1 root root 21 Dec 3 14:26 LOGO -> /dev/block/mmcblk0p14

lrwxrwxrwx 1 root root 21 Dec 3 14:26 METAZONE -> /dev/block/mmcblk0p17

lrwxrwxrwx 1 root root 21 Dec 3 14:26 MISC -> /dev/block/mmcblk0p13

lrwxrwxrwx 1 root root 20 Dec 3 14:26 NVRAM -> /dev/block/mmcblk0p2

lrwxrwxrwx 1 root root 21 Dec 3 14:26 ODMDTBO -> /dev/block/mmcblk0p18

lrwxrwxrwx 1 root root 20 Dec 3 14:26 PROTECT_F -> /dev/block/mmcblk0p3

lrwxrwxrwx 1 root root 20 Dec 3 14:26 PROTECT_S -> /dev/block/mmcblk0p4

lrwxrwxrwx 1 root root 20 Dec 3 14:26 PRO_INFO -> /dev/block/mmcblk0p1

lrwxrwxrwx 1 root root 21 Dec 3 14:26 RECOVERY -> /dev/block/mmcblk0p11

lrwxrwxrwx 1 root root 20 Dec 3 14:26 SECCFG -> /dev/block/mmcblk0p5

lrwxrwxrwx 1 root root 21 Dec 3 14:26 SEC_RO -> /dev/block/mmcblk0p12

lrwxrwxrwx 1 root root 20 Dec 3 14:26 TEE1 -> /dev/block/mmcblk0p7

lrwxrwxrwx 1 root root 20 Dec 3 14:26 TEE2 -> /dev/block/mmcblk0p8

lrwxrwxrwx 1 root root 21 Dec 3 14:26 VENDOR -> /dev/block/mmcblk0p19

lrwxrwxrwx 1 root root 21 Dec 3 14:26 forfanzone -> /dev/block/mmcblk0p15

lrwxrwxrwx 1 root root 21 Dec 3 14:26 tszone -> /dev/block/mmcblk0p16

lrwxrwxrwx 1 root root 21 Dec 3 14:26 userdata -> /dev/block/mmcblk0p26

Just use the dd unix command to dump every partitions content to a /sdcard directory where you can easily copy to an external USB stick or PC via adb pull.

E.g: dd if=/dev/block/mmcblk0p10 of=/sdcard/TWRP/boot_from_dd.img

Luckily I didn't have to use these datas to unbrick my system...

TWRP : I used another version ,it's a v3.3.1, works well. Flashed with SP Flash tool and the scatter contained in the .zip firmware at first post. I enclosed it so someone can tell what's the best option amongst these.

ROOT : Flashing magisk zip from TWRP worked flawlessy, but in my case i experienced an additional delay at boot ( let's say between 20-30 sec ), now a cold boot takes about 1 minute whereas with no root it was about 35 secs. I suspect this is due to the magisk modification to the boot process .

HW mods, temp controls and other infos will follow.

Any questions, just ask.