You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The firmware + vendor package generated by the tool comes with an untouched dynamic_partitions_op_list, and with the reference to that file removed from the updater-script. Such a file is troublesome to flash, as depending on the currently present MIUI ROM on the device, it either requires two attempts to flash, or constantly fails to flash. Recovery log file from the flashing process: https://gist.github.com/kamild1996/a0db92ba4b1704d6bca95c68b1adbb7f
After some experimentation I found out that:
modifying the dynamic_partitions_op_list file to only include the "resize vendor" line
adding the assert(update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))); line back to the updater-script
allows the package to flash successfully regardless of the MIUI ROM currently present on the device.
The text was updated successfully, but these errors were encountered:
Thanks for your experimentation. Indeed the tool modifies dynamic_partitions_op_list, but seems I forgot to include it previously. Just fixed it in V2.2.2 with commit 022ce9c
The firmware + vendor package generated by the tool comes with an untouched dynamic_partitions_op_list, and with the reference to that file removed from the updater-script. Such a file is troublesome to flash, as depending on the currently present MIUI ROM on the device, it either requires two attempts to flash, or constantly fails to flash. Recovery log file from the flashing process: https://gist.github.com/kamild1996/a0db92ba4b1704d6bca95c68b1adbb7f
After some experimentation I found out that:
assert(update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")));
line back to the updater-scriptallows the package to flash successfully regardless of the MIUI ROM currently present on the device.
The text was updated successfully, but these errors were encountered: