Firmware Updating Hikvision DS-7616NI-E2

fishcakes

Young grasshopper
Nov 2, 2016
33
1
I've been trying to update the firmware on a Hikvision DS-7616NI-E2.

This version was purchased directly from a distributor in HK.
- so yes it's an "import"
- but it's an English Version
- and I can find no Chinese anywhere (so don't know if this is what people call "grey market"..)

Current Firmware: V3.3.4 build 150616
Latest Firmware: V3.4.92 build 170228
Downloaded from:
Hangzhou Hikvision Digital Technology Co. Ltd.
(Baseline Firmware_NVR (76/77NI-E)_ML_STD_V3.4.92_170228)

I've tried to update it from iVMS-4200 client software on Windows 10.
- goes "Upgrading Succeeded" and reboots

But then when I check SADP the version still says the old one (V3.3.4 build 150616)

Same results via Firefox v51 with Webcomponents active.

How I can upgrade?
- Is there somewhere else I should be downloading firmware updates from?
- Have I got the wrong digicap.dav file?

*Note: I'm trying to upgrade because I'm getting issues with recording on Motion detection.
- running 2 excellent WD Purple Western Digital 4TB SATA III 64Mb WD40PURX CCTV Hard Drives
 
Last edited:
And just for checking that this isn't non English grey market NVR I've attached a pic of the back serial.

20170606_165842.jpg

The English software on the NVR works perfectly from over a year of use. No bugs, just the video stuttering on Motion Recording.

Edit: On exporting the IP Camera parameters xls file I get:
Device Type DS-7616NI-E2/8P Language Type(Chinese:2,Other:1) 1
 
Last edited:
Edit: On exporting the IP Camera parameters xls file I get:
Device Type DS-7616NI-E2/8P Language Type(Chinese:2,Other:1) 1
What you've described should work - and the firmware you downloaded looks like a match.
And your export and the model suffix does suggest it's not a CN language NVR.
But worth also trying the EU EN/ML versions here : DOWNLOAD PORTAL

A different update method worth trying would be the 'Batch Configuration Tool' : Hangzhou Hikvision Digital Technology Co. Ltd.
And maybe with those odd results it would be best to avoid the Hikvision tftp updater method.
 
Thanks for your suggestions. Tried both EN and ML versions from multiple English speaking locations. Unfortunately I'm still stuck with the same V3.3.4 result.

Using the batch configuration tool seems to be basically the same interface as iVMS-4200 Client for Windows 10 (with SADP look)
- unfortunately same results

nvr page.jpg batch config page.jpg

The region code of my serial number reads "RR".

Which according to this link means other unspecified...
Here's how to read Hikvision serial numbers

Will try updating via USB stick with a monitor directly at the NVR and see if that does anything different.

If it was a grey market model how would I update the firmware?
 
Also is getting 2 different IP addresses for the 1 NVR on SADP normal?
- why does this happen?
 
Also is getting 2 different IP addresses for the 1 NVR on SADP normal?
- why does this happen?
Curious.
There are acttually 2 IP addresses - the LAN interface, and the PoE interface, usually 192.168.254.1 as per your screenshot.
But normally you'd not see them both (and all the cameras) at the same time as they are not on the same wiring, they are separate networks.

SADP works across different IP addresses but only on the same wiring because it relies on broadcasts.
So I'd speculate that maybe you have an extra cable connected from the router/switch to a spare NVR PoE port.
Strictly, that is an invalid network topology, due to the internal forwarding in the NVR, but I know it can be useful for direct camera access.

A long shot - but if you do have this extra cable, maybe try disconnecting it before doing the update.
 
Yes, I do have an extra cable - only because I wanted to view via SADP.
- the IP addresses of my cameras keep resetting every time I try updating the NVR
- SADP is the best way for me to modify the IP Addresses of the cameras

Router -> NVR's LAN Port
Router -> NVR's POE Port

I'll try to disconnect that cable.
 
Ok, disconnecting that cable didn't work.

I've tried upgrading to V3.4.90_161008 (the closest version to V3.3.4) which also didn't upgrade.
Says upgrade successful every time but just resets random settings.. Nuts.

Will have to get another monitor to try upgrading via USB as my current monitor can't seem to view over hdmi right now.
- will try upgrading via USB with a new monitor tomorrow

maybe with those odd results it would be best to avoid the Hikvision tftp updater method.

Why do you say that? - (looking at trying that next)
- is it because I may brick the NVR and not be able to get it back to the V3.3.4 firmware again?
 
Ok, so I tried updating using the tftp method.

Used the software and instructions from this post:
Hikvision TFTP update software

Still not working.

What's really really weird is that the device keeps resetting to MY original password and IP address that I set a year ago.

Wired the NVR directly via cat5e cable to my computer and got the following response:

[2017-06-07 02:21:48] TFTP server[192.0.0.128] initialized *NOTE: Turned on the NVR first to get this 192.0.0.128 IP address. Otherwise tftp.exe would start as 127.0.01 "TFTP server[127.0.0.1] initialized"
[2017-06-07 02:21:49] Connect client failure,0
[2017-06-07 02:23:21] Connect client failure,0 *NOTE: Keep resetting IP Address in SADP to 192.0.0.64
[2017-06-07 02:24:16] Connect client failure,0
[2017-06-07 02:25:10] Device[192.0.0.64] test tftpserver
[2017-06-07 02:25:10] Connect client[192.0.0.64] success
[2017-06-07 02:25:10] Start file[C:\TFTP\digicap.dav] transmitting
[2017-06-07 02:25:21] Completed file[C:\TFTP\digicap.dav] transmit
[2017-06-07 02:25:26] Connect client[192.0.0.64] success *NOTE: Keeps repeating which I don't see on other notes & youtube videos
[2017-06-07 02:25:26] Start file[C:\TFTP\digicap.dav] transmitting
[2017-06-07 02:25:36] Completed file[C:\TFTP\digicap.dav] transmit
[2017-06-07 02:25:41] Connect client[192.0.0.64] success
[2017-06-07 02:25:41] Start file[C:\TFTP\digicap.dav] transmitting
[2017-06-07 02:25:42] Resend required
[2017-06-07 02:25:43] Resend required
[2017-06-07 02:25:44] Resend required *NOTE: Keeps looping on the resends forever since IP Address has now changed....

At a loss here... Its resetting back to MY original IP address settings. I have HiDDNS set up previously.

Keep having to change the NVR via SADP back to
Manual IP Address: 192.0.0.64
Manual Subnet Mask: 255.255.255.0
Manual Gateway: 0.0.0.0
 
Last edited:
Ok, tried some more and really can't get it to do anything.

Its as if MY random year old settings have been hardcoded into the device.

Tried turning off HiDDNS, tried going System > Maintainance > Default > Restore + Default
Tried downgrading to V3.3.2

NOTHING works.

The NVR is clearly in an endless loop going back to my original settings!!
- trying to brick it but can't!!!

What's going on here??

Is there a stronger way to reset the NVR and upgrade?
- maybe putty or something else?
- not that I know much about putty
 
Last edited:
Ok, got an old monitor with a VGA port (since the HDMI connection didn't work).
- the monitor said "input not supported"
- even after downgrading resolution and refresh rate to the lowest setting.
- so still can't try upgrading via USB (not that I think it'd make any difference)

Also got an email from hikvision with a 2017 version of the TFTP updater.
- exactly the same as the other file from the forum link above

Tried that and failed again with the system continuously resetting.

Is there any way to do a HARD factory reset - overriding my 192.168.1.79 IP Address?
 
Although via the app should work, have you tried this via the Web GUI on the NVR itself?
 
Yea just tried again, this time via HDMI (using a 4k monitor).

Gets to the loading screen saying "Embedded NVR".
- Then goes blank "signal not detected"

The NVR also resets the resolution to 1080p everytime I try changing it.

So can't update via USB at the moment.
 
The NVR is clearly in an endless loop going back to my original settings!!
- trying to brick it but can't!!!

What's going on here??
Bizarre!
If you want to spend even more time on this mystery - the next step would be to hook up to the serial console and see what it's saying while you do the update and it reboots.
If you haven't already seen what you need for that - it's :
A TTL serial to USB convertor, such as a PL2303HX-based one, often advertised as for Arduino.
A (set of, often in 10s) 4-pin 1.5mm ZH JST wired connector.
 
Haven't tried removing the battery yet but sounds like an idea. Will probably try that another time along with the PL2303HX connector as system strangely is still running at this point. Just with some playback/recording issues here and there.
 
mate NEVER UPDATE THE NVR BY THE WEB GUI I had the same problem I just updated via the NVR HDMI -USB that way I know it's doing it's job


AND BEFORE UPDATING TO V3.4.92 build170228
YOU MUST GO V3.4.0 build150929

I JUST SEEN your running V3.3.4 build150616

you need to go like this
V3.4.0 build150929
V3.4.1 build151225
V3.4.2 build160226
V3.4.6 build160405
V3.4.62 build160503
V3.4.80 build160718 English+Multi-lingual
V3.4.90 build161008 English+Multi-lingual
V3.4.91 build161220
V3.4.92 build170228

YOU ARE JUMPING FROM
Current Firmware: V3.3.4 build 150616
to a MASSIVE JUMP to
Latest Firmware: V3.4.92 build 170228


download from Here
DOWNLOAD PORTAL

Never update without updating to V3.4.0 due to the OS update's and moving some system files etc

the newer the software there can't update older files due to some file system changes
 
Last edited:
Oops. Maybe that's why the system is stuck in a loop now.

Should have tried it sequentially.

If I can get it back to v3.4.0 without setting changes I'll try updating it that way.
 
Remove all poe camears and see if the nvr stays online

Sent from my SM-G955F using Tapatalk


Can you please also tell me what the SN number has there is four words in your SN number not at the end but in the middle this tells us if its a RR OR WR ( upgradeable) OR CH ( China none upgradable)




the reaseon i came around to that i updated my nvr rightly as i seen this on this site
NVR
and there said this Warning: Firmware upgrades must be done in ascending order and cannot skip versions.
so thinked that is what your problem is