You might want to add if this is a dev kit or if it uses a third party carrier board. In the case of a third party carrier board, then it might need a custom device tree, and any sort of update might use the wrong device tree if for some reason this is configured wrong. Even so, it is unlikely to cause flash failure.
You could include a serial console log during flash, along with a log of command line flash. Keep in mind that you can only use L4T R32.x (which is what gets flashed) via JetPack/SDKM 4.x (which is the front end performing the flash). On command line, flash for a dev kit would go something like this (including logging):
sudo ./flash.sh jetson-tx2 mmcblk0p1 2>&1 | tee log_flash.txt
You could in fact also connect a serial UART to the serial console pins, and start logging there as well via a serial console program. With both running you would get the most information (from both the Jetson and the software performing the flash).
For releases, see:
You might also mention if the host PC performing the flash is a VM or not, and which Ubuntu release is running on that host PC. Command line flash is more likely to work in many cases if this is not a specific Ubuntu host PC. TX2 should use Ubuntu 18 (preferred) or Ubuntu 16 (works well) when JetPack/SDKM is used, but a much wider range of Linux hosts work with command line.
You might also suggest if these devices are exposed to the Internet.