Hikvision Emergency Firmware Recovery TFTP (2024)

[Ray Sharp Boi]

Is this still a thing in 2024

I just opened a sealed camera box for a G1 Acusense . Howerever it just does NOT want to work,
its definitely out of warranty. When I plug it in, all the lights correspond to how they should but the SADP tool does not find it.
I have hooked it up via a POE injector to power it on and connected it straight the LAN port of my laptop and it still does not see it.

The TFTP instructions are simple, I have followed them

"""
Firmware:

Firmware

us.hikvision.com

1. Rename the firmware to digcap.dav
2. Put the firmware in the same folder as the TFTP files
3. Set the IP of computer as 192.0.0.128
4. Camera's IP can be anything
5. Run the tftpserv.exe by double clicking
6. Power on your IP camera and plug it into your router using a cable.
7. Please wait until TFTP shows "Device [192.0.0.64] system update completed!" It takes about
5 minutes.
8. Close the TFTP before the camera reboots.
9. IP Camera will restart automatically after upgrading.

Go to the cameras IP address usually 192.0.0.64
and set a new password it must be secure. usually capital letters and small and numbers.

Then set your cam to whatever you wish I ticked DHCP so it is set by my NVR.

set your PC IP address back to normal

""

but this is as far as it goes...

 

[alastairstevenson]

Rename the firmware to digcap.dav

That's not correct - the unzipped firmware file does not need renaming, and will be digicap.dav

Set the IP of computer as 192.0.0.128

Some later, but still old, models of camera probe for the updater on 192.168.1.128

Run the tftpserv.exe by double clicking

At which point, for the first time it's run, there should be a Windows security pop-up asking if access to the PC for that program should be allowed.
Click OK.
If not - temporarily disable the Windows firewall to allow the program to respond to the inbound probes.

I have hooked it up via a POE injector to power it on and connected it straight the LAN port of my laptop and it still does not see it.

Due to some short timing allowances, the Hikvision tftp updater works best when the camera and PC are each connected to their own router or switch port, and the camera is powered by 12v as opposed to via PoE.

The Hikvision tftp updater has a 32MB filesize limit, and will get stuck in a download loop if the firmware file is larger than that.
If so the Scott Lamb Python2 clone does not have that size limitation.

GitHub - scottlamb/hikvision-tftpd: Unbrick a Hikvision device (NVR or camera) via TFTP

Unbrick a Hikvision device (NVR or camera) via TFTP - scottlamb/hikvision-tftpd

github.com

 

[mcaramb]

Just put this guide together for myself as we are transitioning some proprietary cams to a ubiquity system now that they support 3rd party cams.

The guide points out some annoying little caveats you need to pay attention to or the process can fail. One of the big problems we ran into was using the tftpd server supplied by Hikvision. It only allows up to 32mb uploads, and locks up with the newer firmwares, so you have to use scott's Python script instead. Also had problems connecting the cam directly to the computer. If you do this with the Hikvision tftp server, it won't work because it'll detect the port as disconnected and not post it's 192.0.0.100 ip. You have to connect the computer to a switch.

(This is written for an flashing an ADC-VC836 (Hikvision DS-2CD2325FWD-I) for use with a Ubiquity NVR and ecosystem and using a Mac Laptop with OSX to install)

Use parts of it and find the firmware you need as it pertain to your system. Hope this helps!

1. Get Software
HikVision SADP: HiTools
digicap.dav Firmware:

https://www.hikvision.com/en/produc...yIP-/ds-2cd2325fwd-i/?subName=DS-2CD2325FWD-I

hikvision_tftpd.py: hikvision-tftpd/hikvision_tftpd.py at python3 · scottlamb/hikvision-tftpd (python 3 version)

2. Configure Computer
- Connect computer ethernet port to a standalone non-POE switch
- Set computer ethernet ip to 192.0.0.128, subnet 255.255.255.0, gateway 192.0.0.1
- Put hikvision_tftpd.py and digicap.dav in the same folder

3. Open SADP

4. Run hikvision_tftpd.py
- Open Terminal
- Go to folder with hikvision_tftpd.py and digicap.dav and type:
sudo -s
sudo ifconfig en0 alias 192.0.0.128 255.255.255.0
chmod 777 hikvision_tftpd.py
./hikvision_tftpd.py

5. Connect CAM to a standalone non-POE switch and upload Firmware
- Connect CAM to standalone non-POE switch.
- Power CAM via external 12v power supply at CAM or a stand-alone 48v POE Injector (using POE from a POE switch won't allow a handshake for some reason)
- hikvision_tftpd.py should show magic handshake and upload file progress bars almost immediately
- When says Done!, Immediately hit CNTRL-C to exit the tftpd server
- Wait about 1 min, then disconnect power from CAM
- Wait about 30 secs then reconnect power to CAM

6. Configure CAM in SADP
- In about a minute, Cam should make a click noise and show up in SADP
- Checkbox the CAM. Enter a new password to activate. Default userid will be admin
- Enter security questions. Click Confirm then Cancel
- Change to DHCP

7. Move camera and computer off standalone switch and connect to Ubiquity Network Switch/Router
- Change Computer IP settings to DHCP
- Login to Switch.
- Open Ubiquity Network app
- Find CAM's DHCP assigned IP on Port the CAM is plugged into.

8. Configure CAM settings (DO NOT SKIP SETTING TIME SETTINGS!)
- Login to CAM at it's IP. No special port, just usecured http port 80
- This version of the firmware will show video without plugins!!! (although it and some other screens can be slow to load)
- System Settings->Time Settings (set Time Zone, Set Time sync with computer time). Click Save
- DST (check on). Click Save
- Network->Advanced Settings->Integration Protocol and ENABLE ONVIF.
- Add userid:admin and a password in User List (checkbox administrator)
- Click Save
- System->Upgrade & Maintenance->Reboot

9. Open Ubiquity Protect app on NVR.
- Cam will not automatically show as a 3rd Party Device even if you have "Discover 3rd Party Devices" turned on.
- Add as a custom device in Unifi under (?)