Hi all,
A few weeks ago I installed several DS-2CD2347G3-LIS2UY/SL 2.8 cameras. (EU model)
I also installed the latest HiTools, which marked 2 cameras as update available. Unfortunately, after updating, 2 cameras ended up badly bricked:
I tried the reset button while monitoring with Wireshark for BOOTP / TFTP / similar recovery traffic, but without success.
I then made a UART serial connection using the Molex 1.25 mm connector and managed to get console access. From there I found that the bootloader is still accessible and functional, and I can interrupt boot with Ctrl+U to reach the HVB prompt.
The unit is not hard-dead: the kernel boots, BusyBox init starts, and /etc/init.d/rcS runs. The failure happens later, during early userland / partition / runtime initialisation. In the boot log I see failures such as:
From the HVB bootloader menu, I can restore basic Ethernet/IP settings and start a TFTP session. This allows me to download the normal digicap.dav image, but so far that has not solved the boot issue.
At this stage, I’m not convinced the normal digicap.dav update path is sufficient, because the logs suggest a broken or incomplete runtime image rather than a simple connectivity issue.
I also tested the upf command in the HVB bootloader. On my unit, this appears to be a factory-style Ethernet recovery path, and it explicitly tries to fetch a file named:
mImage_h13u
via TFTP.
That is where I’m currently stuck: I do not have the file named 'mImage_h13u', and I have not been able to find it on the Hikvision portal.
Has anyone run into this exact issue before and found a solution or workaround?
Many thanks.
A few weeks ago I installed several DS-2CD2347G3-LIS2UY/SL 2.8 cameras. (EU model)
I also installed the latest HiTools, which marked 2 cameras as update available. Unfortunately, after updating, 2 cameras ended up badly bricked:
- no usable IP connectivity anymore
- endless boot loop
I tried the reset button while monitoring with Wireshark for BOOTP / TFTP / similar recovery traffic, but without success.
I then made a UART serial connection using the Molex 1.25 mm connector and managed to get console access. From there I found that the bootloader is still accessible and functional, and I can interrupt boot with Ctrl+U to reach the HVB prompt.
The unit is not hard-dead: the kernel boots, BusyBox init starts, and /etc/init.d/rcS runs. The failure happens later, during early userland / partition / runtime initialisation. In the boot log I see failures such as:
- RESV partition attach/format failing because the corresponding MTD is reported as 0 bytes
- MODEL partition mount failure
- Error: not found h13u_modules
- /etc/app: line 399: emmc_info_app: not found
- Not find initrun.sh!
From the HVB bootloader menu, I can restore basic Ethernet/IP settings and start a TFTP session. This allows me to download the normal digicap.dav image, but so far that has not solved the boot issue.
At this stage, I’m not convinced the normal digicap.dav update path is sufficient, because the logs suggest a broken or incomplete runtime image rather than a simple connectivity issue.
I also tested the upf command in the HVB bootloader. On my unit, this appears to be a factory-style Ethernet recovery path, and it explicitly tries to fetch a file named:
mImage_h13u
via TFTP.
That is where I’m currently stuck: I do not have the file named 'mImage_h13u', and I have not been able to find it on the Hikvision portal.
Has anyone run into this exact issue before and found a solution or workaround?
Many thanks.
