Unbrick Dahua NVR5216-8P I/L

[cellman]

Hi,

i need some help with my NVR.

After a third Party Camera did not work correct i restarted my NVR (at this moment the 3 Dahua Cams worked fine).

After a few Minutes i tried to open the Webinterface but got no response.
When i checked the NVR Hardware and connect an Screen it Only shows NVR 4.0 and it beeps one time.

I tried to connect via serial and got this Log.

MMC:
EMMC/MMC/SD controller initialization.
Device is not exit !
MMC/SD Card:
    MID:         0x15
    Read Block:  512 Bytes
    Write Block: 512 Bytes
    Chip Size:   59632M Bytes (High Capacity)
    Name:        "CKTA4"
    Chip Type:   MMC
    Version:     4.0
    Speed:       25000000Hz
    Bus Width:   8bit
    Boot Addr:   0 Bytes

MMC read: dev # 0, block # 4096, count 2048 ... 2048 blocks read: OK

U-Boot 2010.06-svn5643 (Nov 24 2021 - 17:06:41)

MMC:   In:    serial
Out:   serial
Err:   serial
squashfs use gzip
SCU:   load slave image OK
spi env sysbackup=0
Read backup misc byte ...
erase_misc_byte ok!

backup tc exist !!!

backup rc exist !!!
ok!
PRODUCT:>1U
Hit any key to stop autoboot:  0

After a few minutes the system reboots automatically.

I already tried to interrupt the boot and flash the nvr via tftp but i did not get any response on the console (tried * and also Shift+8).

Any Idea?

Marcel

 

[almack]

Hi,
got the same error few days ago. To fix it I used null-modem cable (female/female) RS-232, USB-to-RS232(male) cable, TFTP server from HikVision, NCOM v1.02 app. To interrupt boot you need to press * 3 times in NCOM console, then cnahge TFTP server IP address in NVR if necessary local NVR ip also (use your router to assign 192.168.1.108 to your NVR), save it, next load do * 3 times again to stop autoboot and type prntenv. Upload firmware files to TFTP server root dir and call commands from printenv one by one:

dr=tftp romfs-x.squashfs.img; flwrite
du=tftp user-x.squashfs.img; flwrite
dw=tftp web-x.squashfs.img; flwrite
dl=tftp logo-x.squashfs.img; flwrite
ds=tftp slave-x.squashfs.img; flwrite
dc=tftp custom-x.squashfs.img; flwrite
up=tftp update.img; flwrite
tk=tftp uImage; bootm
pm=tftp 575s_PMX.bin.img; flwrite
dx=tftp u-boot_slave.bin.img; flwrite

run dr
run du
etc.

If something is missing in your firmware that's ok, just run what you have there. Use first v4 firmware before, then you can upgrade to lates version via usbflash drive as usually.

 

[almack]

Hit any key to stop autoboot: 0
press * 3 times before 0

 

[cellman]

Hit any key to stop autoboot: 0
press * 3 times before 0

Hi,

i can not stop autoboot, there is no reaction on pressing * 3 times.

Maybe i have an Hardware issue, because after i disconnect Power for a few days (5 or 7) and reconnect the NVR boots normal.

After the boot i reset the NVR and with the next reboot i got the same issue (beep / bootloop). After i disconnect the Power for a few days again it boots normal.

Now the NVR runs 3 Weeks without any Problem but i think if i restart it i got the same error.

 

[almack]

Hi,

i can not stop autoboot, there is no reaction on pressing * 3 times.

Maybe i have an Hardware issue, because after i disconnect Power for a few days (5 or 7) and reconnect the NVR boots normal.

After the boot i reset the NVR and with the next reboot i got the same issue (beep / bootloop). After i disconnect the Power for a few days again it boots normal.

Now the NVR runs 3 Weeks without any Problem but i think if i restart it i got the same error.

it seems hardware issue, i can't imagine how restart can damage embedded linux loader. but damaged capacitor can affect the loading of the entire system physically.