Unbricking Hikvision IP Cameras (Repair, Reflash and TFTP Guide)

download the file hikvisionpaswordresethelper.

Download the firmware for your camera, connect the camera to 12 volt adapter, connect a lancable from your computer to your camera, set your lanadaptor in your computer to 192.0.0.128
than make a directory tftp on you cdrive…
download hikvision tftp en put it in the tftp directory.
than put the firmware in the same directory.

start tftp and check that it shows 192.0.0.128
then disconnect the 12volt and directly connect it again.

if the firmware is correct it will load it and you have a working camera again…

questions? [email protected]


Hi, Thanks for explaining everything. I am having issues stuck on block 1 / 39556. Checked the firewalls and everything looks good.

Anyone have an idea what could be causing this?
Thank you

looks like hardware issue, reading or writing to blocks.
I assume this is the upload log, i would check all the wiring for corrosion and that water has not got into the camera

Thanks a lot for the guide

looks like its connected, but running super slow. after 10 mins all I have is this? (connected via eth. machine and camera on the same POE switch)

PC:~/Downloads/hikvision-tftpd-master$ sudo ./hikvision_tftpd.py
Setting block size to 512
Serving 23458645-byte digicap.dav (block size 512, 45818 blocks)
Mon Dec 30 22:18:08 2024: Replied to magic handshake request.
Mon Dec 30 22:23:27 2024: Replied to magic handshake request.

Sorry to reply to an old subject but thankyou wendell and others as this page helped me out recovering a DS-KH6320-WTE1 hikvision indoor station that had a failed firmware update and this might be useful to others:
I bought a PL2303HXA rs232 cable off Amazon, (had to replace the windows 11 auto installed driver with one from the Prolific website). Had the station plugged in with a normal ethernet cable direct to my laptop (on 192.0.0.128) and powered the station up using the 12vdc option rather than poe. I had no luck getting any connection with the hikvision tftp program, Scott Lamb’s python script (tried python 2 and 3), or tftp32. They all just sat there waiting for a connection that didnt happen - but I saw in Wireshark that the hikvision was trying to connect from the correct ip 192.0.0.64. I fiddled with tftp settings, firewall settings, turning av off but nothing. Out of frustration I tried solarwinds tftp server instead and suddenly my putty screen showed it was downloading the file! I didn’t have to change any of the default settings in the software, just put the digicap file in the server directory. After the download and reboot the station is now working properly, and on the latest firmware. fantastic! thanks!

1 Like
4 Likes

Hi, and sorry to revive the topic here. I’ve been trying to get DS-KV8113-WME(C) back to life after a botched Firmware update (apparently, I should have updated each small version, not directly to the new one).

This guide is the first one that allowed me to make progress. Using Hikvision’s own TFTP tool on Windows didn’t work because it was not getting a response from the device.

Using the Python script, I also don’t get a response. It is loading the firmware file, but not getting the call-back from the device, regardless if I use the 192.0.0.128 or the 192.168.1.128 IP address.

Finally, after using Wireshark to watch over connection requests, I saw “dead-silence” using the 192.0.0.128 IP, but got a response using the 192.168.1.128 IP. The problem is that it was rotating between a 192.168.1.120 and a 192.168.1.144 (I am unable to verify if the MAC address is from the device, but considering that it is the only thing connected to my Macbook, I can assume it is).

I have one major limitation: I can only “easily” power the device using PoE. The other alternative would be to go to the front door, connect the 12v cable, go back down to the basement, connect the ethernet cable. Please advise if this is a major limitation :frowning:

I’m really desperate because we rely on the doorbell to enter the house. Hikvision support has been useless, because the guy who built our house got it “on the cheap” in Bulgaria and they are refusing to offer warranty support in Germany.

PS: this is by FAR the best guide I found on this so far. You’re a real hero!

1 Like

cna you post more info about your wireshark dumps? perhaps the camera is connecting to tftp but not finding the file its looking for, or something like that. you may need to hard wire your macbook in as tftp via wifi is a recipe for headache in this type of scenaro usually

Thanks for the quick reply. I am adding two screenshots:

  • the first shows the folder in which the firmware file is and where the python script is being run from, next to the terminal window running the python script and the terminal window with Wireshark being called
  • the second one shows Wireshark running AFTER I stopped everything and tried to run SolarWinds’ TFTP App in Parallels using Windows 11 (the network connection is bridged).

Things to note:

  • Wi-Fi is switched off for the MacBook in both scenarios.
  • en8 / AX88179A is the USB-C dongle I use to connect the Ethernet cable to my laptop.
  • en8 is bridged to Parallels (I got a call-back from one of my functioning PoE HikVision screens when I connected it).


I really appreciate the help. Thanks!

1 Like

mdns doesnt matter for us, filter it out (ai helper can give you the syntax)
arp… probably doesnt matter (it might)

the output here suggests it is serving the file to the camera, but perhaps the camera is not applying it. have you tried other files/versions? newer/older?

I forget if the script tells you when the client asks for a file but its not there. I have a vague memory of watching for files the camera asks for, that aren’t there, and using that as a clue to give it what it wants.

the fact it does seem to be loading the file is a great sign, and suggest its either not flashing the file (because it doesn’t match some check)… could be from too new, or too old

2 Likes

You got me a little hopeful there, but I didn’t get to a solution yet.

I’ve tried multiple versions of the firmware, to no avail. Even back to the 2.7 version that was there before the botched update, then the 2.8 after it, etc.

I’m posting a new screenshot. If I don’t move anything and just disconnect and reconnect the camera, the Ethernet interface also doesn’t give any response.

I’m desperate to find out what I am doing wrong…

1 Like

Hi Fellow members,

I’m after some advice.

I have a DS 2CD2355-I (3 of them) and have loaded up SADP but it states that there are REMAINING RETRY TIMES: 0 These cameras are on V5.420build 160726. It also shows a different IP range 192.168.254.52 which was previously part of the NVR solution which failed (Hard disc died).

I also have the older version cameras which where on same NVR but i can connect to in SADP the DS 2CD2332 with default user and password. Those cameras were on Software version V5.20build 140721.

It seems the first problem is the retry times = 0.

Has anyone come accross this issue with the HiKVision Camera ?

I asked for support from HIKVision but they said
”Not in service region. Based on the information provided, your device is not supplied through authorized distributors of Hikvision Australia. Due to our policy and security requirements, we recommend contacting your original supplier for technical support. Our local support team is only able to provide assistance for products purchased through authorized local channels. We strongly recommend purchasing products through authorized distributors to ensure warranty coverage and product safety.”

I cant contact the installer anymore?

Is this a brick now?