Hikvision DS-7608NI-I2/8P bricked after updating to the latest version

Jun 17, 2023
4
0
Australia
Hi, I have problem after updating my Hikvision DS-7608NI-I2/8P to the latest firmware from hikvision site. Now its not booting up. I can see only the welcome screen and then again booting. Any idea how to fix this issue.
I tried to TFTP but its not completing. its connecting to 192.0.0.64 and transmitting the Digicap.dav file but after few minutes its trying again transmitting the file. its like a loop not ending. Any idea?
Thanks,
JK
 

Attachments

  • TFTP Runtime.PNG
    TFTP Runtime.PNG
    67.5 KB · Views: 13
  • TFTP.PNG
    TFTP.PNG
    34.1 KB · Views: 14
Last edited:
I tried to TFTP but its not completing. its connecting to 192.0.0.64 and transmitting the Digicap.dav file but after few minutes its trying again transmitting the file. its like a loop not ending.
The I-series firmware is larger than the 32MB filesize limit of the Hikvision tftp updater.
You can get round this limitation by using the Scott Lamb Python 2 clone of the tftp updater, here :

But - just as important - what firmware are you trying to update the NVR with?
There are various issues, such as jumping too many versions and getting a corrupted config that blocks login, the downgrade block, picking the wrong model firmware etc.
Link to the firmware you've tried?
 
The I-series firmware is larger than the 32MB filesize limit of the Hikvision tftp updater.
You can get round this limitation by using the Scott Lamb Python 2 clone of the tftp updater, here :

But - just as important - what firmware are you trying to update the NVR with?
There are various issues, such as jumping too many versions and getting a corrupted config that blocks login, the downgrade block, picking the wrong model firmware etc.
Link to the firmware you've tried?
Hi alastairstevenson,

Thanks for your help. The initial upgrade i did through online (hikvision admin site) and it was successfully completed but when i tried to reboot its not booting up. It may be b'cse of i jumped too many versions.

This is the version i tried.

 
It may be b'cse of i jumped too many versions.
There has been a known issue when updating from too early a V3.x version to the V4.x versions of firmware where the configuration gets scrambled, which prevents logging in, but does not stop the NVR booting.
Do you recall what version you updated from?
 
There has been a known issue when updating from too early a V3.x version to the V4.x versions of firmware where the configuration gets scrambled, which prevents logging in, but does not stop the NVR booting.
Do you recall what version you updated from?
Its V3.x but not know the exact number. I update the firmware b'cse of its not let me add into the mobile app. It was working fine before but when i delete the app from mobile then unable to add it again.
 
What was the reason for updating?

Unable to add into the mobile app. It was working fine all these years (from 2018) and one day i deleted the app from mobile and try to add it again then its not let me to do so. Then i called hikvision they advise me to update the firmware with the installer but i went myself to update.
 
Suggestion :
Re-try applying the firmware using the tftp updater method, but with the Scott Lamb tftp updater clone providing the update service.

The Hikvision tftp updater will definitely not work with that size of firmware, but the usual consequence is just a looping transfer process as opposed to bricking the NVR.
 
If anyone is trying to use the script from Scott Lamb in 2024 and beyond I've forked it and added some features like a handy start.sh script that sets the correct IP Address on your ethernet adaptor, runs the python script then on exit reverses the changes back to stock settings. Ive also updated the script to work perfectly with Python 3! just clone my git repository GitHub - sbeehre/hikvision-tftpd_python3: Unbrick/Factory Reset a Hikvision NVR via TFTP

Ive also found that you can update the firmware from ANY version to the latest firmware and you don't seem to run into the bricking issues that you see when you upgrade it via the onboard GUI.
 
Ive also found that you can update the firmware from ANY version to the latest firmware and you don't seem to run into the bricking issues that you see when you upgrade it via the onboard GUI.
Beware of suggesting this to any users - instances of bricking, both NVRs and IP cameras, can occur via any method of updating if the jump in firmware version crosses a boundary where the structure holding the configuration has been updated, and the newer firmware doesn't have support for an older structure. Support for older structures only persists across a few firmware versions, hence the need for a more granular upgrade path.
 
Beware of suggesting this to any users - instances of bricking, both NVRs and IP cameras, can occur via any method of updating if the jump in firmware version crosses a boundary where the structure holding the configuration has been updated, and the newer firmware doesn't have support for an older structure. Support for older structures only persists across a few firmware versions, hence the need for a more granular upgrade path.
I've tested it on multiple NVRs all running the 3.4.xx firmware and this method has worked flawlessly every time... so yes that is a point worth considering if you upgrade the normal way though the GUI but doing it this way seems to work 100% on the 10 or so I've tried so far.