What is the de-bricking process for HIKVision camera and NVR firmware updates?

Hmm the ds-2cd2345-i is not at all in the list?

Already tried those firmwares (the 5.4.0 and 5.4.5).

It is somehow blocking it I guess. Any other tricks? :-( :-(
 
This newegg page suggests the camera has a reset button - but I can't vouch for it's accuracy. Hikvison DS-2CD2345-I IP Network Camera 4MP H.265 Dome IP Camera Multi-language Version 2.8mm Lens - Newegg.com
And if it does - it will likely be internal.
If you do find one, the method is :
Power off the camera, hold the reset button, power on and hold the button for at least 20 secs after which the camera will be in an 'Inactive' state requiring that you create a strong password, and reconfigure from the defaults now in place.
 
I'd just like to add my recent experience. Had a customer's 7608NI-E1 NVR ready to upgrade firmware. (I noticed quite a few of those models were mentioned in this thread. It's the first HIKv NVR I've ever had do this during a firmware upgrade.

I was connected to it from my laptop via wifi. (not sure but that may have been the problem) anyway, ran the firmware upgrade, appeared to be going smooth and then nothing. NVR totally bricked, no video from HDMI/VGA, no presence on SADP, etc. I took it back to the shop and began studying this thread, and experimenting the hikvision tftp (which by the way is hard to find anymore. I found it on an archive.org site via a google search). Like others it took about 5-6 tries and a few mistakes. I'll try to list frtom best of my memory what was going on that finally worked.

Used a switch between NVR and PC
used the 192.168.0.128 and tftp program
I did NOT rename the digicap file to digcap like the readme instructions suggested. (I did at first and then renamed it back to digicap and it worked).
turned all windows firewalls off on PC
ran and ping to NVR 192.168.0.64 -t and was finally able to get a reply (like only 2)
then a few trial and error starts of the tftp program and the NVR.
What finally worked was double clicking the program and powering up the NVR at exactly the same time. Once it connnects it's immediate, like in the first 5 seconds. I had no luck on previous attempts waiting the 5-6 minutes like some others.
The transfer process was pretty quick (like under a minute) and then another 4 or so minutes to apply it. I looked up and saw 8 beautiful "No Video" squares on the monitor.
Just had to go back in and reset all of the customers setting/IP's, DDNS, etc and all worked like a champ. Even the previously stored video was still there.

Hi,

Everything went smooth as per your instructions. But there was an error saying.

** Open File [..\TFTP\router.img] failure.

NVR model - DS-7108NI-E1/V/W.
Firmware versions tried - V3.4.80_160817 & V3.4.1_151225

Any comments would be appreciated.

Thanks,
 
Armarzook, not sure, it's been a while for me. I'm guessing it might be an access or permission issue on that file open. Make sure it's in an accessible directory or the default one that the TFTP program thinks it should be in. Also make sure all firewalls, antiviruses, etc are turned off during this process.

Maybe one of the more experienced pros on this thread will have more thoughts.

Good luck.
 
you have to use a network switch, it's a stubborn nvr but does recover. I've got one and play with it all the time
I have the same problem with a bricked DS-7604NI-SE/P NVR. I also uploaded V3.0.15 firmware and now all mine does is to give 2 beeps and nothing else happens. I can't see it with SADP; the address was 192.168.1.4. I've tried just about everything. What did you mean with the switch and how do I do it. I'm addressing this question to WhosLooking. I haven't made any replies so I just want to make sure I get this to the right person. Thanks, Phil
 
Old thread, but hopefully someone can help.

I'm trying to reflash my DS-7608NI-I2/8P but I keep getting the following, it just repeats:

[2018-09-12 17:06:12] TFTP server [192.0.0.128] initialized
[2018-09-12 17:06:13] Connect client success [192.0.0.64]Success
[2018-09-12 17:06:13] Start file transmitting[C:\TFTP-Update\digicap.dav]
[2018-09-12 17:06:43] Connect client success [192.0.0.64]Success
[2018-09-12 17:06:43] Start file transmitting[C:\TFTP-Update\digicap.dav]
[2018-09-12 17:08:47] Connect client success [192.0.0.64]Success
[2018-09-12 17:08:47] Start file transmitting[C:\TFTP-Update\digicap.dav]

It's connecting, however it doesn't appear to be transmitting and installing the firmware. Any ideas?
 
[/QUOTE]
The firmware file for that model of NVR is too large for the Hikvision tftp updater tool.
There is an equivalent to the tool on GitHub that does not have that file size restriction. I don't have the link to hand via the phone but if you do a forum search for GitHub you should find it.

*edit*
scottlamb/hikvision-tftpd

Please can someone explain how to use this. My firmware is too big for hikvision ftp program. Many thanks.
 
Please can someone explain how to use this.
How far did you get in trying it?
Have you installed Python?
Are you using Windows or Linux?

Essentially the steps are :
With the PC and the NVR both wired to your LAN, set the PC to the required 192.0.0.128 IP address, just as for the Hikvision tftp updater.
Have the unzipped firmware in the same folder as the tftp program.
Start the tftp program.
Power on the NVR, watch the info on the PC screen.
 
hello,i am using windows. i tried hikvision ftp. wheen i connect direct nvr and pc there is no connection.( used both crossover and standard lan cable). When i connected nvr and pc to switch ftp server worked. Firmware start to transmiting but after few minutes again start to transmiting.. from the posts from this thread firmware is too big for this ftp. solution is this python for linux but dont now anything about linux. is there some tutorial how to use python? many thanks
 
Last edited:
is this python for linux
I've not used Python in Windows myself, but certainly its available, and there is a wealth of how-to info on a Google search.
I'm almost tempted to try it in a Windows VM.

Please can someone explain how to use this. My firmware is too big for hikvision ftp program. Many thanks.
Are you doing a recovery from bricked / password reset or just an update?
What model of NVR/DVR, and does it have a DB9 serial interface on the back?
 
If a firmware fails to update properly use TFTP to restore a working copy of the firmware.
http://www.hikvision.com/europe/support_more.asp?id=269

Link is dead

I will attach a zip file of the Hikvision TFTP file v1.0 2007 -- also available externally from here:

Tech Tips & Tricks: Hikvision TFTP Tool

I just did it with DS-7332HGHI Turbo 1.0 Hybrid DVR w/ official 3.3.4 digicap.dav en-US

Procedure (from text file in TFTP package with some small additions):

1. Rename the firmware to digcap.dav
2. Put the firmware under the same folder of this TFTP
3. Set the IP of computer as 192.0.0.128
4. Device's IP can be anything.
5. -- While DVR ON -- Run the tftpserv.exe -- should say TFTP server started [192.0.0.128] --
6. Power off and power on the DVR/DVS/IPC. The device will search the new firmware and upgrade it automatically.
7. Please wait until TFTP shows "Device [192.0.0.64] system update completed!" It takes about 5 minutes. (I don't remember seeing this - I could tell it was done when I could hit enter and get a # prompt, type 'help' and get list of commands, etc.)
8. Close the TFTP before the camera reboots. (I just unplugged the RJ-45 and plugged the DVR into my switch to configure with SADP)
9. DVR/DVS/IPC will restart automatically after upgrading. (I don't think this happened but it's possible)

My DVR had to be on for the TFTP software to assign to the address of ethernet card. It would assign to loopback (127.0.0.1) if the DVR was off. Just starting the TFTP program while DVR was on seemed to do the trick, then power cycle DVR afterward.

Note: It helps to monitor with an RS232-USB adapter, I used puTTY for term - 115200, 8n1 (get COM port from Device Manager after plugging in your USB-serial adapter as it will be automatically assigned)

There's more detailed instructions here, but I did not need them. This process was easy AF. You don't need to wireshark anything, the devices all have standard IP 192.0.0.64 - you can also find it running SADP tool or IVMS-4200 (even if it's bricked and/or not on your subnet). I'd try that first.

How to Fix a Bricked Hikvision IP Camera Firmware - HandymanHowto.com
 

Attachments

  • Like
Reactions: catseyenu
Hi guys,
I do have DS-7604N-E1/4P NVR (bought from China) and tried to upgrade old firmware to latest EU firmware and device bricked - i really don`t get why device is not able to verify firmware before bricking it.
As much i know i should use Chinese multilingual firmware to restore it, but i`m not able to find it nowhere- could someone help me with that?
I tried several times with direct cable connection from PC to NVR and now i read that NVR still should be connected through switch.