Up until the last bytes sent it looks normal. The NvError 0x8 is this:
0x00000008, "module is in invalid state to perform the requested operation"
What should have happened is this:
system.img sent successfully
In particular, system.img is the root file system. I assume the JetPack version acts like a normal manual flash in that it updates the sample rootfs boot directory, creates a loopback mountable image as system.img, moves this to system.img.raw,and then creates a sparse image as system.img. Hardware could cause a failure of invalid state, but a simpler explanation would be that the system.img is invalid by reason of exceeding eMMC capacity.
There will be a subdirectory “bootloader” somewhere (I’m not sure how JetPack arranges directories) in the installation on the host. Within that, what is the exact size of any file starting with name “system.img”? E.g., “ls -l system.img*”?
Also, if a system.img is a raw image, it is loopback mountable…if it is a sparse image, then loopback mount will fail. Does this command (via sudo) run from the system.img file directory location succeed?
mount -o loop -t ext4 system.img /mnt/tmp
…if that command works, you can umount via:
If there is a system.img.raw, try the same thing using “system.img.raw” instead of “system.img”.