There are some details which are easy to miss during flash. Flash instructions leave a lot of it out…several threads on this forum about flashing. Some boards may actually require RMA, but there is a higher chance that one of those flash details is at fault. Instead of listing everything, let’s find out some of the more common issues.
FYI, the ${BOARD} is jetson-tk1. Also, any edit of the jetson config file for enabling USB 3 at boot should be avoided until things actually work, as USB 3 is not so simple because of firmware. And for video, if you used an adapter going to older 15 pin VGA, likely it will fail…monitor needs to actually be HDMI or DVI. VGA lacks the DDC channel used to tell the system about monitor specs.
Can we assume your host for the flash is running on a file system which works with linux file permissions? E.G., if you run on ext3 or ext4, this works…an NTFS partition cannot work.
Can we assume you unpacked any files for L4T as root, or sudo to become root? Lacking this corrupts things. Can we assume that any tar command included the option to preserve file permissions (I think it is -p, I’m not on linux at the moment, I’m doing it all from memory)? If you did not preserve permissions, strange things will happen.
Can we assume you ran the apply_binaries.sh as root or sudo?
What flavor linux host were you using, e.g., ubuntu, fedora? What is the output of “ls /dev/loop*”? Do you have /dev/loop0? If you run “losetup --find”, does it show loop0?
For your L4T directory, where flash.sh exists, look at your bootloader sub-directory. Does it now contain “system.img”? It should be betwee 8 GB in size and 15 GB.
What was your exact command line during flash? Did you hold down the reset button before and during application of power to the Jetson?