Do you have ethernet connected? It is quite possible video is what is cycling and it isn’t actually rebooting. The inability to go to recovery mode though is a concern…are you using the micro-B USB cable and the host does not show via “lsusb -d 0955:7c18”? I know you said you checked to make sure you were doing it right, but if the cable is type-A instead of type-B it won’t work.
Interrupting boot requires a serial console.
Note: If you have ethernet you can ssh in and correct any overwritten libglx.so file…this would be very likely to have happened if it is only video which is cycling and not an actual reboot. Should you be able to connect over ethernet check this:
After successfully flashing my Rosie Embedded System (a nvidia jetson TX2) with JetPack 3.3 from an Ubuntu 16.04 Host, I rebooted the system and got an error about graphic configuration, selecting to run on default config, it got stuck on an infinite loop at the user start session screen.
I ssh from the host and checked: “sha1sum -c /etc/nv_tegra_release” but libglx.so is OK.
How can I solve this problem?