Messed up /dev/mtdblock2, possible to restore from uBoot? EDIT: SOLVED!

[daveribs]

Hi, I have a HeimVision HM203 IP camera. It reports GK710XS. I was messing around with UART and this hack and I managed to mess up the filesystem. I tried making the persistent hack work with my device, which mostly uses /bak/ for all the files (start.sh, etc.) instead of /home/, but it doesn't boot properly anymore. It boots then constantly throws an error message for some time, then reboots. I currently do not have an SD card and would prefer trying to restore without one. I have backups for /dev/mtdblock2, /dev/mtdblock3, /dev/mtdblock4 and the zImage kernel, but I'm not sure how to restore mtdblock from uBoot. I can boot zImage from uBoot TFTP. Linux OS still kinda works for some time, but it's extremely hard to work with because error messages are constantly being spammed on the UART serial console until it reboots.

Is it possible to restore mtdblock from uBoot? I know I could load it in RAM from TFTP and restore it with some command, but I don't know the memory locations of the partitions. Does someone know how I could find this?

[daveribs]

Just want to report that I was finally able to make everything work on a cheap HeimVision HM203 (link here). I had to edit some stuff since this camera stores stuff in /bak instead of /home. Since /bin is RO, I had to use 'mount --bind' instead of cp.

• I remounted /bak as RW (mount -o rw,remount /bak)
• I dropped all hack files from the RO hack in /bak/hack
• I took the commands from debug_cmd.sh that use "mount --bind" instead of "cp" and put them in /bak/start.sh (with paths to /bak instead of /media since we're running from flash)
• Everything works like a charm and I was able to accomplish everything without an SD card. But I did need UART :P