alastairstevenson
Staff member
The firmware writes it's version number into a 0x40 byte segment at the start of mtdblock1 - and periodically re-writes that (possibly from the version value held in the sqlite3 configuration tables, but I'm not sure) if you modify it to try to circumvent the downgrade block.
But I have found that, depending on the date / version of the bootloader/update program, a downgrade works OK via the tftp method.
So that is easy enough to try.
If you check your conversations - I'll send you a link to some V5.3.0 EN/ML firmware that might just work.
Also as an experiment (I've not played much with this), @montecrypto hikpack tool has an option to change the firmware header version and date.
[MCR] Hikvision packer/unpacker for 5.3.x and newer firmware
But I have found that, depending on the date / version of the bootloader/update program, a downgrade works OK via the tftp method.
So that is easy enough to try.
If you check your conversations - I'll send you a link to some V5.3.0 EN/ML firmware that might just work.
Also as an experiment (I've not played much with this), @montecrypto hikpack tool has an option to change the firmware header version and date.
[MCR] Hikvision packer/unpacker for 5.3.x and newer firmware