Third-party firmware typically disables signature verification, but this comes at the cost of losing DRM-protected streaming (e.g., 1080p Netflix). Moreover, careless flashing can the device—a risk mitigated by the Hi3798MV100’s built-in USB recovery mode (burning via USB OTG) that can reflash the bootloader even after a bad flash.
The firmware for the Hi3798MV100 follows a multi-stage boot architecture typical of embedded ARM devices. The boot sequence begins with the (masked inside the SoC), which loads the First Stage Bootloader (FSBL) from NAND flash, eMMC, or SPI NOR. The FSBL—often a proprietary HiSilicon binary called fastboot.bin or reg_info.bin —initializes DDR memory, clocks, and basic peripherals. It then loads the Second Stage Bootloader , usually a modified version of U-Boot , which presents a command-line interface or automatically loads the kernel. hi3798mv100 firmware
U-Boot for the Hi3798MV100 is heavily customized with HiSilicon-specific commands for burning images ( update ), partitioning, and boot parameter management. It reads the boot environment from a reserved flash area and decompresses the (typically version 3.18 or 4.4) with HiSilicon proprietary drivers for video decoding, GPU (Mali-450), and demuxers. The kernel mounts a root filesystem (squashfs, ext4, or UBIFS) that contains the Android or Linux userland. The boot sequence begins with the (masked inside