/dev/char/10:130 is a character device with major device number 10 and minor number 130. In non-embedded Linux systems it is more commonly named
When you open a watchdog device, a timer (often a hardware-level timer) starts ticking down. The program that opened the watchdog device is expected to periodically write something (anything, really) to the opened device, to indicate that the system is still alive and well. This will reset the hardware timer, which will then start ticking down towards zero again.
If this does not happen, e.g. because the system is hung or overloaded, the hardware timer will reach zero, and then the watchdog mechanism will activate a hardware-level reset signal to perform a hard reboot. It's the equivalent of a dead-man switch for the OS and/or other software running on the system.
If the software minding the watchdog needs to stop, some watchdog drivers require sending a specific character to the watchdog device just before closing the file. Then the watchdog driver in the kernel is supposed to disarm the watchdog timer. Your
sudo cat /dev/char/10:130 did not do this.
The problem is, some hardware watchdog timers apparently cannot be stopped without a reboot once activated. And if the kernel has been compiled with the CONFIG_WATCHDOG_NOWAYOUT option, the driver will expect that once the watchdog is activated, there should always be a watchdog-minder process present, and so the watchdog deactivation request will be refused.