David112x
commented
4 months ago The tool doesn't need support to flash more than one rawprogram.xml and patch.xml, because you can do it yourself and the reason why is because the files (0 to 5) are there is because of your device's LUNs in it's UFS, for example, rawprogram0.xml along with patch0.xml only change LUN 0, while rawprogram1.xml and patch1.xml only change LUN 1, this means that after using the command to flash the firmware with the XML files for LUN 0, you can use the same command but instead of using the same XML files for LUN 0, you use the ones for LUN 1 and so on, until you get to the ones for LUN 5, then your device should have everything.
As for the errors regarding the sparse images, your best bet is to unsparse them (probably super.img and userdata.img, because I faced this exact issue on my Poco X3 NFC while flashing it over EDL) and set "sparse" to false for super and userdata in the rawprogram0.xml, after that, you'll have to turn both of them into raw images, you can use simg2img to do this.
As janky as it might be to flash a raw super.img and raw userdata.img over EDL, I don't know if there's any other way to flash those two while being sparse images.
TL;DR Flash with those rawprogram and patch files as well, don't stop at 0 and make super.img and userdata.img raw images rather than sparse.
basc0hex
While attempting to flash a Xiaomi device (Redmi 9T) with the latest firmware, which contains multiple rawprogram files (0 to 5) along with the necessary patches, I encountered an unexpected limitation with the flashing tool. The tool does not support more than one rawprogram and patch simultaneously. Despite trying various command structures, I was unable to overcome this limitation.
To work around this issue, I attempted to flash each rawprogram file (X) along with its corresponding patch (X) without closing the device connection with the Sahara and proceeded to flash the subsequent rawprogram files sequentially. However, I encountered a failure during the flashing process of the first rawprogram file (0) due to the presence of sparse partitions in the XML file defining the rawprogram. The atthached file is the first rawprogram0.
rawprogram0.txt
Furthermore, the gpt_mainX.bin (X=0 to 5) files belong to the PrimaryGPT partition, and the gpt_backupX.bin (X=0 to 5) files belong to the BackupGPT partition, as defined in different rawprogram files.
Additional Information: Other sparsed partitions existing in different rawprogram files need to be addressed accordingly to ensure successful flashing.