Hikvision NVR new firmware 3.2.1

mtdblock2 is pure cramfs so you can just cat it back - unmount mtdblock2 then cat mtdblock2 > /dev/mtdblock2, mount it again, reboot.
The block driver handles the flash erase process. It will take a minute or two to complete the erase / write with 16MB file.
But you need a decently accessible and working device to be able to do that.
A neat thing to do is to create some new firmware using @wzhick hiktools program.
Check out the 'create' option here: http://www.ipcamtalk.com/showthread...anguage-extract-files-and-create-own-firmware
Then you can use that firmware just like the official releases. Web GUI, tftp.
I think it's good to have an 'as delivered' position you can return to.
 
Last edited by a moderator:
  • Like
Reactions: scn101
Alastair, are you saying that I can create a digicap.dav load from the mtdblock2 dump? That would be great but I don't see how to accomplish that using hiktools (which is an excellent tool). I've read a lot of posts but the only thing I can see that I can do is expand an existing digicap.dav file and replace files from another firmware expansion and the recombine into a new firmware but I can't see how to create a new FW from the mtdblock2 dump.
 
Actually, I think I might see it now. Using a hex editor you take the first bytes from a standard digicap.dav file (bytes 0x00-0x6B from 3.0.10 - NVR_(76,77,86-Ex)BL_EN_STD_V3.0.10_141126.zip) and prepend it to the mtdblock2 file that I captured from the NVR thus creating a new GUI loadable digicap.dav file. Is this correct? Will this preserve the English interface should a firmware load cause the NVR to revert to Chinese? I'm hesitant to try it as I don't want to brick the unit or have it revert to Chinese only.

If the above is correct, then I'm thinking any new firmware, 3.2.1, etc., should always allow you to GUI download the above FW restoring your NVR as purchased, English and all. What do you think? Or can the FW mod mtdblock0 and 1? That would change this.
 
*edit* no need to use a Hex editor. To your earlier question:

Yes, and I've used that method to put my 7816N-E2 back the way it was when I received it, after some experiments.
The steps essentially are:

Copy the mtdblock2 into a new folder, with no other files, rename it as 'cramfs.img'. The NVR firmware update objects if there is more than one file in the digicap.dav Lets call the folder 'FWsource'.
You need a real digicap.dav ideally of the same firmware version as the mtdblock2 to use as the header source.
For my 7816N-E2 which came with 3.0.8, I used an English-only release NVR_(78,79-Ex)QDBL_CN_STD_V3.0.8_140825 downloaded from the Hikvision China website. Lets call this digicap308.dav

Then, when the current directory is the parent of FWsource, with hiktools04r.exe in it, the new firmware can be assembled using:
hiktools04r create digicap308.dav FWsource
The result will be a firmware file called FWsource.dav
Rename this to 'digicap.dav', store safely and job done!

Depending on the language setting of the NVR relative to that of the header source there may be a need to adjust the language flag of the resultant firmware with the hiktools 'lang' command.
 
  • Like
Reactions: scn101
Fantastic, I will try that, thank you. If I then try 3.2.1, can I use the new digicap.dav file that was created, via the 3.2.1 GUI, to downgrade back to 3.0.10? If yes, that would be nice as I don't have the UART set up yet. I so don't want to cripple the NVR!
 
Yes, either through the GUI, or TFTP recovery. That's pretty well what I did, and it worked OK.
However - be aware that there may well be some risk, some unknowns, so do anything with your eyes open, knowing what could happen.
Don't forget to export the device and IPC configurations as well.

I've left my 'production' system as-is, and bought an additional NVR just to play with, so not a big problem if I lose it.
Having said that though, it's pretty handy having it set to record motion only, due to the lack of motion markings in the web playback under continuous recording with alarm recording on the 'production' system.
It would be good if Hikvision could add that feature, as QNAP have done in Surveillance System for example.
 
Any one tryed 3.3.1 ?

[FONT=微软雅黑]Package applies to the following models:[/FONT] [FONT=微软雅黑]DS-7804/08 / 16N-E1, DS-7804N-E1 / 4N, DS-7804N-E1 / 4P, DS-7808/16 / 32N-E2, DS-7808/16 / 32N-E2 / 8N, DS- 7808/16 / 32N-E2 / 8P, DS-7816 / 32N-E2 / 16N, DS-7816 / 32N-E2 / 16P, DS-7908/16/32-E4, DS-7908N-E4 / 8P, DS- 7916 / 32N-E4 / 16P[/FONT]

[FONT=微软雅黑][/FONT]
[FONT=微软雅黑][/FONT]
[FONT=微软雅黑]Special Note:[/FONT]
[FONT=微软雅黑]Version: V3.3.1 build150422[/FONT]

[FONT=微软雅黑]Equipment upgrades at risk, please be sure to confirm whether to upgrade equipment.[/FONT]
[FONT=微软雅黑]Make sure that the upgrade package is available for your device.[/FONT]
[FONT=微软雅黑]Do not upgrade the device off.[/FONT]
[FONT=微软雅黑] [/FONT]
[FONT=微软雅黑]Note:[/FONT]
[FONT=微软雅黑]After the upgrade is no longer supported Kang domain (HiDDNS), please upgrade as appropriate![/FONT]
Click to expand...
 
Are you still able to downdrage or is it now blocked out on 3.3.1
 
downgrading from the web fails no ssh or telnet, not tried TFTP. when i get time i plan to modify 3.3.1 and change busybox and add telnet access be for trying to rewrite my 3.0.8 backup
 
I recently tried updating my 7716NI-SP to this firmware and everything came up but I am unable to login. Using mouse and monitor on the NVR itself displays no login accounts. I have tried the TFTP thing but all I ever get is Open file[D:\TFTP\econt_Vision-AV2000] failure].

Anyone have any idea's of how I could get this working?
 
Last edited by a moderator:
I scanned this thread some more and found where someone had the same issue as me. I have a serial cable and I use putty all the time. Can anyone explain to me the steps to push firmware to the NVR using this method?

gpower07 said:
I bought a USA verison ds9664 ni st nvr. and downloaded the 3.2.1. after successful update...rebooted. user name in the drop down menu is BLANK!!!!! and I tried to tftp back the older firmware. it WON'T let me do it. since I bought the usa version, so I called them. they told me that I can't downgrade unless use rs232 cable. so i bought the cable and call them back...they remote my pc and use putty and upload the firmware through the cable!!!!!!
Click to expand...
 
Some questions if I may to get a bit more detail, apologies if some are fairly obvious:

Is this the 3.2.1 firmware or the 3.3.1 firmware that you installed? Do you have the URL that you downloaded it from?
When you say "everything came up but I am unable to login" does it show the web login screen as on the very first post of this thread, on the originally-set IP address?
Are you trying to log on with the original default ID / password of admin / 12345 ?
What error are you getting when you try to log in?

Did you use the Hikvision-specific TFTP server - it shows in the window title bar as 'Hikvision TFTP Server', and place the digicap.dav file in the same folder as the TFTP executable ?
And did you follow the Hikvision TFTP recovery instructions, including PC IP address=192.0.0.128 / 255.255.255.0 and connect both the NVR and the PC to switch or router ports (not direct with a cable)?
 
3.2.1 from hikvisioneurope
http://www.hikvisioneurope.com/port...-SP -XT-RT/V3.2.1 build 150310 Multi-lingual/

I get the web interface but it does not accept any login or password.

Yeah I tried two different hikvision TFTP clients and tftp32.

Yes the digicap.dav that I downloaded from the place I bought the DVR originally was in the same folder as the TFTP executable.

Yes I configured the IP address that way and had my laptop directly connected to the NVR and via router ports.

I get the same message whether i was directly connected or over the router.
 
I'm not familiar with the 7716NI-SP, but I'm pretty familiar with the TFTP method on 78XX / 76XX and 2-series cameras, and have found it to work well.
I've no idea of the significance, and this is a bit off the wall - but I notice in the firmware you linked to, the file is named digicap.mav
Is this what you placed in the TFTP folder, as-is?
A couple of suggestions:
Make a copy of the digicap.mav in the TFTP folder, and rename it to digicap.dav
When ready to try TFTP again, use a command prompt on the PC to set a continuous ping, ie 'ping -t 192.0.0.64' and watch for responses on both the ping and the TFTP window when you power on the NVR. Watch if the ping responses just occur for a few seconds and don't repeat.
Yes the digicap.dav that I downloaded from the place I bought the DVR originally
Click to expand...
Is this the original firmware that was installed, prior to the 3.2.1 upgrade?
 
I may not have renamed from mav to dav. The firmware is newer than the original but I upgraded to 3.1.1 before this earlier in the year.
 
I could ping it for about 10-15 seconds but during that time I see nothing in the tftp. After it stops pinging it now says connect client failure,0
 
Well done, a good result.
So was it a matter of issuing commands to the serial console via the serial cable, or is there some method of transferring a file?
 
You must log in or register to reply here.
Top Bottom