Modifying firmware involves extracting a partition, editing its contents, and reassembling the monolithic binary using pack.py . Step 1: Modify the Partition
| Use Case | Description | |----------|-------------| | | Delete pre-installed apps from system partition | | Replace boot logo | Change the startup splash screen | | Extract kernel | Get the Linux kernel for analysis | | Root firmware | Inject su or Magisk into the root filesystem | | Recovery modification | Modify recovery partition contents | | Firmware translation | Replace language files in the rootfs |
The mstar-bin-tool suite includes four core utilities:
If Python is not recognized, you may need to add it to your system PATH or use python3 instead of python on Linux/macOS. mstar-bin-tool
python mstar_bin_tool.py -f encrypted.bin --decrypt --key 16bytekey.bin -o decrypted.bin
: Contains magic bytes and CRC32 checksums for both the header and the bin sections to ensure integrity. Basic Workflow for Firmware Modification
: The file was corrupted during download, or a manual partition modification altered the file size without updating the configuration config. Basic Workflow for Firmware Modification : The file
C:/firmware_work/
If rootfs.bin is SquashFS (most common):
The extracted key files will be saved in the ./keys directory. Advanced Usage: Secure Boot and Encryption :
After modifying the images (e.g., modifying system.img ), you can repack the files: python pack.py output_folder new_upgrade.bin Use code with caution. Advanced Usage: Secure Boot and Encryption
: