unbricking NVR DS-7608NI-I2/8P help

[Simon Huppatz]

Hi all, hoping someone may be able to help please.
I recently received an NVR with corrupted database (likely installing incorrect firmware), and want to put fresh firmware on it and try to bring it back to life.
It's a region RR , currently can boot up to GUI showing v4.0 of whatever firmware was on there.

Little unsure what firmware to use, but some google posts suggest the NI can be upgraded with EU firmware? I've tried a couple different ones, but run in to the same issue.
I've set up a TFTP server, and can get it to connect and start the download, but it just seems to repeat:
- TFTP server initialized
- device test tftpserver
- Connect client success
- start file ...digicap.dav transmitting
- Connect client success
- start file ...digicap.dav transmitting
- Connect client success
- start file ...digicap.dav transmitting ... etc (for 20 mins, up to 9 repeats and counting)
PC has the 192.0.0.128, and I only have the NVR connecting from 192.0.0.64 on the same LAN segment (nothing wireless). It doesn't seem to complete the transmission.
Is it just incorrect firmware?
What am I doing wrong?

 

[alastairstevenson]

currently can boot up to GUI showing v4.0 of whatever firmware was on there.

Are you saying it just gets to the splash screen and stays there?

Is it just incorrect firmware?

Very likely. You haven't specified the origin of the firmware you are trying.
But I have a vague recollection that there may be a file size limit on the Hikvision tftp updater that this firmware may breach.

There will be a downgrade block that inhibits applying earlier firmware that what has been attempted, so you may need to try several choices from here :
DOWNLOAD PORTAL
All will be revealed if you connect up to the serial console on the main board.

 

[Simon Huppatz]

Appreciate the response.
I've ordered a serial cable (no rear DB9 to connect to, so I assume one of the 4pin white plugs on the mainboard required?)
I can see the GUI on the monitor, but the usernames to select from are all strange characters, with 4.0 in top left (was told database corrupted)
I can also hit the GUI via 192.0.0.64 but don't have login credentials (need to reset it), and not sure of default.
Using the monitor I can't find the hidden button in the lower left (V3.3+ stopped that?).
Think the only official option is hikvision tech support for GUID code/key/file, but not sure if they'll play ball with a second hand unit? (could ask I guess, but don't want them to blacklist it)
Have tried a few of those files before, but again now V3.4.82, V3.4.98, V4.1.10 and V4.1.60
All had the same result - retry after ~2m7s (and I've left that run for 26mins/9 retries on one TFTP attempt)

[2018-08-12 20:25:47] TFTP server[192.0.0.128] initialized
[2018-08-12 20:25:57] Device[192.0.0.64] test tftpserver
[2018-08-12 20:25:57] Connect client[192.0.0.64] success
[2018-08-12 20:25:57] Start file[C:\utils\Hikvision\TFTP\digicap.dav] transmitting
[2018-08-12 20:28:04] Connect client[192.0.0.64] success
[2018-08-12 20:28:04] Start file[C:\utils\Hikvision\TFTP\digicap.dav] transmitting

[2018-08-12 20:29:00] TFTP server[192.0.0.128] initialized
[2018-08-12 20:29:09] Device[192.0.0.64] test tftpserver
[2018-08-12 20:29:09] Connect client[192.0.0.64] success
[2018-08-12 20:29:09] Start file[C:\utils\Hikvision\TFTP\digicap.dav] transmitting
[2018-08-12 20:31:16] Connect client[192.0.0.64] success
[2018-08-12 20:31:16] Start file[C:\utils\Hikvision\TFTP\digicap.dav] transmitting

[2018-08-12 20:31:57] TFTP server[192.0.0.128] initialized
[2018-08-12 20:32:11] Device[192.0.0.64] test tftpserver
[2018-08-12 20:32:12] Connect client[192.0.0.64] success
[2018-08-12 20:32:12] Start file[C:\utils\Hikvision\TFTP\digicap.dav] transmitting
[2018-08-12 20:34:19] Connect client[192.0.0.64] success
[2018-08-12 20:34:19] Start file[C:\utils\Hikvision\TFTP\digicap.dav] transmitting

[2018-08-12 20:35:26] TFTP server[192.0.0.128] initialized
[2018-08-12 20:35:36] Device[192.0.0.64] test tftpserver
[2018-08-12 20:35:36] Connect client[192.0.0.64] success
[2018-08-12 20:35:36] Start file[C:\utils\Hikvision\TFTP\digicap.dav] transmitting
[2018-08-12 20:37:44] Connect client[192.0.0.64] success
[2018-08-12 20:37:44] Start file[C:\utils\Hikvision\TFTP\digicap.dav] transmitting

File size limit sounds viable, have read others suggest that, but surely that would impact everyone trying to do it?? (all firmware look the same size except for .54 had a 19MB file, but seems corrupt?)
Are there settings I can try with another TFTP server? Any recommended? Assume it won't boot off USB for upgrade?
Any specific ones worth trying for a longer period?
Thanks again!

 

[alastairstevenson]

I've ordered a serial cable (no rear DB9 to connect to, so I assume one of the 4pin white plugs on the mainboard required?)

It's going to be TTL serial signal levels, not RS232 signal levels.
So you'll need a serial TTL to USB convertor as well as the 4-pin 1.5mm JST ZH wired connector.
The PL2303HX-based ones, usually advertised 'for Arduino' work OK.

File size limit sounds viable, have read others suggest that, but surely that would impact everyone trying to do it??

Yes, but it's been some years since Hikvision removed the tftp updater from their public websites. So no guarantees it will still work with new products.
And it's only the new model NVRs that have such big firmware.

Are there settings I can try with another TFTP server?

As far as I know - only via the menus of the serial console. The built-in 'probe for the Hikvision tftp updater' uses a proprietary handshake to validate what it finds on the LAN.
But - there was a Github python emulation of the tftp updater. I wonder if it would work OK? Not sure of the link, sorry.

 

[Simon Huppatz]

Thanks for the response.

But - there was a Github python emulation of the tftp updater. I wonder if it would work OK?

This looks interesting! Did some google and found a hikvision tftp in github, so will try that this week while I wait for some cables to be delivered. Should answer the question on file size at least.
Cheers.

 

[Simon Huppatz]

But I have a vague recollection that there may be a file size limit on the Hikvision tftp updater that this firmware may breach.

Great call! Thanks for the tip - did use that tftp program from github and got the oldest firmware I could find installed - 3.4.82 lol
scottlamb/hikvision-tftpd
Went nice and quick, no issues. Easy as.

So have set up the NVR with a new password, and I now have access!!
But it can't find any more recent firmware to auto-update to via the GUI, and it won't let me browse via the web gui (installed plugin but made no difference), so looks like I'm either finding another to tftp again, or trying usb.
Is there a known stable firmware best for this model?
I don't need any fancy features, just want something reliable. Any suggestion?
Thanks again!

 

[alastairstevenson]

So have set up the NVR with a new password, and I now have access!!

Hey, that's a good result! So it looks like there is a file size limit with the classic Hikvision tftp updater that trips up the newer larger firmware.

But it can't find any more recent firmware to auto-update to via the GUI

OK, so you have web GUI access. I'm not sure if the auto-update is actually functional.
A range of firmware available to download from here : DOWNLOAD PORTAL
Be very wary of the V4.x versions. A big re-write, and can be problematic when updating. There are some posts on the topic.

it won't let me browse via the web gui (installed plugin but made no difference)

I'm willing to bet you are not using IE11, maybe Edge on Win10, Chrome or Firefox even? That would fit those symptoms.
A useful tool for detailed admin and updates is the Batch Configuration Tool : Download | Tools - Hikvision

 

[Simon Huppatz]

I'm willing to bet you are not using IE11

Lol, you got me Tried edge & chrome, but old internet explorer ftw it seems.
I just did a usb upgrade to the V3.4.98 firmware and all seemed to go fine, and using IE in the web GUI there's now a button to firmware upgrade, and I can browse for files also.
I'll do some research before upgrading to V4 train, but at least I know how to unbrick it.
Thanks again, now off to learn how to use it!