The flash log shows success, and nothing was wrong with the process. Would you have a serial console boot log to show logging during startup? For information on serial console, see:
However, before you bother with the log, you’ll want to confirm that you are using the correct Connect Tech software. What follows is an explanation of how CTI software would differ from the default L4T flash (the content flashed, not the software performing the flash).
Flash software for performing a flash will not care which carrier board is used during the flash, but upon reboot incorrect firmware will cause partial or complete boot failure. Flashing is much simpler (from the flash software viewpoint) than is booting normally.
Realize that third party carrier boards require firmware specific to the carrier board. Much of a computer is not “plug-n-play”, e.g., there are clocks and power rails and optional routing of various components which may differ across different carrier boards, and these cannot self-report the way a PCIe card or USB end device can. The result is that a device tree is used to tell the operating system where (e.g., base address) to find components and which driver to assign. These differ such that any component which is not routed exactly the same way as the dev kit carrier board has to have modified firmware, and only Connect Tech would have that information.
When manufacturers such as CTI provide content to use for flash this is mostly the same as the default NVIDIA dev kit flash software, but would contain an altered device tree.