edit: Well DUH. It says... u-boot_g1.bin . If I could only figure out what type of camera it is...
I should go to bed I'm so friggin slow. Got a cheap g1 uboot for a bum?
.
u-boot_g1.bin is what is asked for on the hik G1 cams. I do not have a u-boot_g1.bin handy and if I did it would not have any more commands than you already have. it would not help.
if I were you, do not trash u-boot or play with it. The minisys and uboot commands are more or less useless for direct access to the cam
if you trash the u-boot you will need to flash the nand(manually)
if you trash the minisys you still are able to load a new minisys as u-boot is intact.
if you trash the PRI partions you will still be able to use the uboot and minisys.
Really depends on your knowledge and how much risk you want to take. for some pulling the nand is easy peasy lol dump the firmware and reassemble job done.
The minisystem will be the weak point in the cam. there will be minimal checks. if you get or make a minisys it may not boot the cam that's assuming you can get it to take it.
The correct way to root your cam is to backup what you have , so you have a point of return. But that's not always possible based on a persons knowledge.
I never found a use for the usb commands in the minisys. the go or gos interested me but I never had an sdk to make a standalone app. GPIO was also interesting but never found a use for it
Most of these commands alter FLASH. go and gos load apps into user space.
I am working on the images on G1 now but getting a minisys to load and run in user space will be the final thing I attempt. At the moment I am having trouble just re-assembling the main boot image lol
There are size,crc and model checks amongst other things in the minisys header. if its not on correct format the cam will not take it.