Yep, i recovered from the same issue but using Windows, No Python needed. See below.I did the firmware upgrade on the NVR using 4.1.50 and got to the join the dot part. It would not accept the dots, I powered off then on, now I can't get past the log on. The "admin" line is blanked and when I change the password and set a new one and attempt to use it, it still won't proceed on. Hope this makes sense. I have attempted to log on from a browser using the 192.0.0.**, but that doesn't proceed. I have attempted SADP and can't get past the log in.
Glad it worked for you !!!Okay, Mike, finally success due to your post. I couldn't use Solar Winds but used Tftp32 and with this and your post fixed the bricked NVR just over 12 months after bricking it. I thank everyone here who had any input. It was all valuable. I now have a unbricked NVR woo woo.
Hey Guys,After a long time fearing this process, I've decided to pull the trigger. Below is my journey, which I think may help someone. Reminder: I have the official legitimate australian version of the DS-7608NI-I2 / 8P NVR and cams DS-2CD2385FWD-I.
First thing I did was download the latest NVR firmware from the "europe" website. However I've actually downloaded it from the Netherlands website in english, accidentally. I then upgraded my NVR using that firmware via a USB stick, and that "semi-bricked" it. Once powered on, the user list was big and only had values with strange characters in it. The NVR became useless, I couldn't get past the login screen.
After the initial WTF did I just do moment and some cold sweated desperation, I proceeded to download the latest firmwares for the NVR (V4.1.64 build 190119 at the time) and the CAMs (V5.5.82 at the time) from the UK websiteHIKVISION UK PORTAL, and
command for that is "ping 188.8.131.52". if it times out, its not working.
- Downloaded the tftpd software from scottlamb/hikvision-tftpd
- Put the NVR new firmware digicap.dav file in the same folder as tftpd
- Connected both the NVR and my laptop to my LAN
- Connected the NVR to my LCD display and a mouse
- Set my laptop ip to 184.108.40.206 / 255.255.255.0
- Tested that my laptop, with that ip address, could ping the NVR at its default IP (after brick) of 220.127.116.11
path=C:\Python27 (this is the path where I installed python at)
- Downloaded and installed python for windows Python Releases for Windows. For this, either version 2.x or 3.x will do. I used 2.7.
- Went to the path where I extracted the tftpd software and ran the commands
- The above last command displayed a message saying digicap.dav was being served. It will sit there not doing anything until you proceed with the step below
- I then powered off and powered the NVR back on (this is very important. the NVR basically tries to download the new firmware during its startup, via a fixed IP address... it tries to reach, by default, the IP 18.104.22.168. Which is the one you set for your the machine running tftp )
- After I powered my NVR, the tftp software running on my laptop started showing messages saying the file was being sent to the NVR
- All you have to do is wait for that process to finish by itself. The NVR will then reboot a couple times and it should come back with a wizard for you to configure it
After that was done, I've re-configured my NVR and updated the CAMs firmware via the NVR web interface without any issues.
In the end, I thought the firmware upgrades were totally worth it (so far at least... If I encounter an issue I will report it here). Main gains for me were:
- using the cameras via NVR and hik-connect is a LOT faster now (the image will display in 1-2 seconds, versus 6-7 s from before)
- using the playback function works a lot better
- I can now download video files via web interface and hik-connect, both of which are things I could not do before
I would not update unless you have a 32MP camera. I think 4.1.64 does its job well enough and has good enough performance. I would only upgrade if there were significant improvements to the interface, the way videos are downloaded and/or how recording take place (sensitivity, different options to configure, etc)So still stuck doing this method via the Hikvision UK portal?
Yep, agreed. It's not worth the hassle.I would not update unless you have a 32MP camera. I think 4.1.64 does its job well enough and has good enough performance. I would only upgrade if there were significant improvements to the interface, the way videos are downloaded and/or how recording take place (sensitivity, different options to configure, etc)
My Australian authorised reseller told me to download the latest version from the USA Hikvision site. I flashed this no problem, but the previous version, NOT the V4.22.005Yep, agreed. It's not worth the hassle.
Cheers for that Stumpy. O.K , so your saying if I'm at V4.1.64, the next version I should upgrade to V4.22.000 first, before V4.22.005? Also noticed on that USA website, there are other later versions V4.21.005/008, preceeding V4.22.000?My Australian authorised reseller told me to download the latest version from the USA Hikvision site. I flashed this no problem, but the previous version, NOT the V4.22.005
Link above for USA version if you ever did want to upgrade.
I had a very similar convo with them, which I detailed in earlier posts. It is what it is, I think people wanting to upgrade their AU NVRs will be left unsupported for upgrades for many years to come.I am looking at updating mine as well and have come across a very very interesting situation.
We had been told by the Australian distribution partner CSD that upgrading the DS-76xxNI-I2-xP NVR from firmware V3 to V4 was not possible as it bricked the NVR so it was a complete no go. We have heard of many people that have done this but it seems only AU units are having the issue
I found the support number for Hikvision support AU so rather than going through the distribution channels CSD and being stonewalled, I asked Hikvision Australia if I can get my DS-7608NI-I2-P8 updated from V3 to V4 firmware his comment was" You will have to ask your distribution channel for this firmware" "We have an agreement with them on what firmware is available for that region? i said"So you are telling my CSD has the call on what firmware we get and what we don't?" answer was "Yes you will have to talk to CSD and get it from them"