How to unbrick Dahua DVR5208A

Hello,

last week i was upgrading my DVR but something went wrong and as a result i bricked the device...

Now i'm tryng to unbrick the DVR, using "General_DVR5X08_Eng_PN_V3.200.0001.26.R.20150119" firmware. This firmware contains several files, including "update.img"

I'm using DIME MANAGER and PUTTY software.

At the end of procedure,Putty shows me this error:

U-Boot 2010.06-svn704 (Apr 27 2013 - 19:19:16)

DRAM: 256 MiB

Check spi flash controller v300. found

Spi(cs1) ID: 0x01 0x20 0x18 0x03 0x01 0x00

Spi(cs1): Block:64KB Chip:16MB Name:"S25FL128P-1"

the size of spi flash is 0x1000000

In: serial

Out: serial

Err: serial

judge ddr init

user init finish.B

can't find corresponding entry

### CRAMFS LOAD ERROR<0> for /bmp_logo.bmp!

load log failed

Hit any key to stop autoboot: 0

netup time out: 3

Timeout

### JFFS2 loading '/boot/uImage' to 0x82000000

raise: Signal # 8 caught

Scanning JFFS2 FS: done.

find_inode failed for name=boot

load: Failed to find inode

### JFFS2 LOAD ERROR<0> for /boot/uImage!

Wrong Image Format for bootm command

ERROR: can't get kernel image!

hisilicon #

This is the result of printenv command:

hisilicon # printenv

bootargs=mem=116M, console=ttyAMA0,115200 rootfstype=cramfs root=/dev/mtdblock1

bootcmd=netup; fsload; bootm

bootdelay=3

DEVID=00000000000000000000000000000000

dh_keyboard=1

load_modules=1

appauto=1

da=tftp u-boot.bin.img; flwrite

dr=tftp romfs-x.cramfs.img; flwrite

du=tftp user-x.cramfs.img; flwrite

dw=tftp web-x.cramfs.img; flwrite

dl=tftp logo-x.cramfs.img; flwrite

dc=tftp custom-x.cramfs.img; flwrite

up=tftp update.img; flwrite

tk=tftp uImage; bootm

baudrate=115200

netup_timeout=3

bootfile="uImage"

ethaddr=90:02:a9:a3:2d:d6

eth1addr=ff:ff:ff:ff:ff:ff

ID=PA3DU07100994

HWID=00000000000000255.255.255.255

netmask=255.255.0.0

gatewayip=10.42.0.1

restore=0

serverip=10.42.0.100

ipaddr=10.42.0.102

stdin=serial

stdout=serial

stderr=serial

verify=n

ver=U-Boot 2010.06-svn704 (Apr 27 2013 - 19:19:16)

Environment size: 804/131068 bytes

I think the problem is due to lack of "upgrade_info_7db780a713a4.txt", which seems to be required to complete the process: is it true?

Can you please help me to solve the issue?

Marco