There is no “total disk” clone/flash using recovery mode (there used to be back in the days of the TK1). Life is now complicated by signing of partitions, and so there are still tools for preserving partitions, but those tools require a running system. If the process is not correct, then the Jetson won’t boot and will need to be flashed from scratch.
If you wish to clone all of the regular partitions you can use “dd”. You wouldn’t want to use dd to clone the rootfs while it is being used, but none of the other partitions have any issue with this. If you were booted to an SD card (and thus not using the rootfs on eMMC), then this would copy the entire eMMC:
sudo dd if=/dev/mmcblk0 of=clone.bin bs=512
Even if you use the rootfs and boot normally you could clone the other non-APP (non-rootfs) partitions one at a time, e.g.:
sudo dd if=/dev/mmcblk0p2 of=p2.bin bs=512
Restoring is a different matter. You shouldn’t mix releases of rootfs and different other partitions, but if you have booted system you could for example restore a non-rootfs partition like this example:
sudo dd if=p2.bin of=/dev/mmcblk0p2 bs=512
Now in theory, if you had booted a Jetson to an SD card to avoid using the rootfs from eMMC, and had cloned with “sudo dd if=/dev/mmcblk0 of=clone.bin bs=512”, then you could restore:
sudo dd if=clone.bin of=/dev/mmcblk0 bs=512
Any failure means you have to flash fresh since the system must boot before dd can be used.