I've run into the problem when flashing disk images onto our own devices, that the written bytes counter on the progress bar represents the written byte indexes on the destination instead of the mapped indexes of the source image.
In practice:
We have a 360MB image and an 8GB device to flash to, the progress bar would indicate {written} bytes / 360MB, but {written} here is the index in the destination device, so would go all the way up to the 8GB marker. So the progress bar would be incorrect for the majority of the upload
I've run into the problem when flashing disk images onto our own devices, that the written bytes counter on the progress bar represents the written byte indexes on the destination instead of the mapped indexes of the source image.
In practice:
We have a 360MB image and an 8GB device to flash to, the progress bar would indicate {written} bytes / 360MB, but {written} here is the index in the destination device, so would go all the way up to the 8GB marker. So the progress bar would be incorrect for the majority of the upload