Bricked my NVR by updating from very old firmware straight to latest one.

[nickkd]

Hi everyone,

Does anyone know how to fix a "semi-bricked" nvr caused by updating from very old firmware straight to latest one? I found out I should not update firmware like that the hard way.

My NVR is DS-7604NI-E1/4P which ran firmware v3.3.4 build 160118 when I received it. I updated it to the latest ones v3.4.106 Build191009 through web interface successfully and I was able to create password and pattern. However, after restart the pattern doesn't work, user name drop down list is blank and un-clickable.

I went through this forum and here is the list of what I did:

TFTP using hikvision tftp tool: unsuccessful with econt-vision-av2000 failed message.
TFTP using Scott Lamb python script on window laptop: unsuccessful with same econt-vision-av2000 failed message.
TFTP using Scott Lamb python script on linux laptop: no response or message from nvr. I used command line "sudo tcpdump -i eth0 -vv -e -nn ether proto 0x0806" and the result showed that my nvr only look for itself and my router ip address, not the tftp server address of 192.0.0.128: "Request who-has 192.0.064 tell 192.0.064, length 46, Request who-has 192.168.50.254 tell 192.0.0.64, length 46". I think since my nvr is only semi-bricked and can still boot, it does not switch to recovery mode and look for tftp server?!

If anyone can suggest me other methods to fix this I would really appreciate. In the mean time, I have ordered some PL2303 and PL2303TA cables to serial into my nvr if all other method fail. Hope I ordered the correct one since I have not done this before.

 

[alastairstevenson]

TFTP using hikvision tftp tool: unsuccessful with econt-vision-av2000 failed message.

That's the NVR probe looking for 'Arecontvision' devices that it puts out on normal bootup.
It uses a similar handshake to the Hikvision tftp updater - so the tftp updater comments on it.
It's not an error, but it does indicate that the tftp updater handshake has not taken place and the NVR has booted normally.

Getting the tftp updater response does imply that the Windows firewall is allowing inbound traffic from the NVR.
And the 192.0.0.64 address does imply I think that it's unlikely the target address for the tftp updater has been altered from the default 192.0.0.128
That's set in a bootloader environment variable.
So it's not clear why the PC isn't seeing the UDP probe from the NVR and resulting response from the tftp updater.
One possibility - do you have the PC and NVR directly connected via ethernet?
The resulting extra delays of speed / duplex negotiation can get in the way of the short timings the NVR allows waiting for a response to its probe.
Best to have the PC and NVR each wired to their own switch port.

 

[nickkd]

Thanks Alastair. I forgot to mention that both laptops' firewall had been turned off and all troubleshooting and trial had also been done through my RT-AX3000 router/switch. One of my suspicion is with all the extra security setting on my router, it might prevent the handshake?! I don't have any other spare switch but I have an old router/switch from my previous ISP that I can try later.
I want to include the links to the firmware that bricked my nvr and the serial cables I bought for you to check but the forum just give error message whenever I click post

Edit:
I just found out that if I post links to aliexpress, I would get error message so I will just include screenshots. Hope I'm not breaking any rules.
The firmware: v3.4.106 Build191009

Would these cable work with my nvr?

PL2303



PL2303TA

 

[alastairstevenson]

From what I recall (it's ages since I bought any of these) the TA version is required if the PC is running Windows 10. A driver issue.
You'll notice that compatibility isn't mentioned on the non-TA version.
Also - it's easy enough to insert the connector wires into the -TA version adaptor.

You'll also need a wired 4-pin 1.5mm JST ZH connector, usually sold in 10-packs.

And check out this post to help with the connections :

Hikvision NVR DS-7804N-E1/4P Bricked

Hello, i have NVR DS-7804N-E1/4P bricked when i flash wrong firmware DS-7604NI for it. So now it only boot to Logo then bip bip and auto restart. I tried flash TFTP very many time by set IP of my PC to 192.0.0.128 / subnet 255.255.255.0 and turn firewall is off. But no thing flashable although i...

ipcamtalk.com

 

[nickkd]

Yes I did order the 4-pin 1.5mm JST ZH connector, and yes I also did read that post as well, that's why I ordered the cables. The reason I'm asking is because from that post you mentioned the nvr will only accept 3v (I might mistaken there?) The TA version only has 5v where as the non-TA has both 5v and 3.3v. If I use the TA version, which only has 5v, would it fry my nvr?

 

[alastairstevenson]

That's an interesting question.
Looking at the Prolific specs, it doesn't mention the signal levels, looking around elsewhere suggests the TX is 3.3v which matches the NVR requirements.
There is a 5v VCC available on the device, but that's not needed and should not be connected.