DS-7608NI-I2/8P TFTP flashing problems (the uImage not support update_v3./bootm 0x42000000 fail.)

NACA_FAS

NACA_FAS

n3wb
Apr 19, 2021
6
0
Bideford
Hi,

I am trying to fix my bricked Hikvision NVR. I have the NVR successfully downloading the firmware (NVR_K51_BL_ML_STD_V4.40.015_200616) from a TFTP server. When I run setenv ';update', it gives me the following errors:
Code: 
HKVS $ setenv ';update'
using update v3...
Mounting yaffs2 mount point/partnum: nand/0
version.bin not found on nand[flash_sys0]
Copy /nand/uImage to 0x42000000... File not found
Mounting yaffs2 mount point/partnum: nand1/1
version.bin not found on nandflash_sys0
Copy /nand1/uImage to 0x42000000...     [DONE]
the uImage not support update_v3.
boot uImage from flash for update error[-8].
boot uImage from digicap...
timeout for link [5000]!
MAC:   **-**-**-**-**-**
MAC:   **-**-**-**-**-**
TFTP from server 192.0.0.128; our IP address is 192.0.0.64
Download Filename 'digicap.dav'.
Download to address: 0x4dd00000
Downloading: find the image, index: 1, startOffset: 0x5cc, fileLen: 0x948e50
#########
done
Bytes transferred = 9740288 (94a000 hex)
MAC:   **-**-**-**-**-**
headEx checkSum ok !
uImage checkSum ok !
the uImage support update_v3.
   Verifying RSA ... OK
## Booting kernel from Legacy Image at 42000000 ...
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] need to Authorization
[    2.427956] init(1) called reboot syscall, cmd: 0x0.
[    7.382324] libphy: 1:07 - Link is Up - 1000/Full
[    7.874861] Restarting system. (task: insmod, PID:642)


U-Boot 2010.06-svn64409 (Jul 01 2021 - 08:52:03)

Hit ctrl+u to stop autoboot:  0
Mounting yaffs2 mount point/partnum: nand/0
Configures yaffs mount nand success!
version.bin not found on nand[flash_sys0]
Copy /nand/uImage to 0x42000000... File not found
Mounting yaffs2 mount point/partnum: nand1/1
version.bin not found on nandflash_sys0
Configures yaffs mount nand1 success!
Copy /nand1/uImage to 0x42000000...     [DONE]
   Verifying RSA ... failed
Mounting yaffs2 mount point/partnum: nand1/1
version.bin not found on nandflash_sys0
Copy /nand1/uImage to 0x42000000...     [DONE]
   Verifying RSA ... failed
run command: bootm 0x42000000 fail.
HKVS $ HKVS $ bootm 0x42000000 fail.

I am unsure how to fix this. Any ideas? If it helps, I am 99% sure this DVR is a UK model (I may be wrong).

Many thanks
 
NACA_FAS said:
I am unsure how to fix this. Any ideas? If it helps, I am 99% sure this DVR is a UK model (I may be wrong).
Click to expand...
From your transcript, it seems the uImage originally on the primary boot partition was an older version that doesn't use the fairly new 'update_v3' firmware update method.
This method replaces the bootloader update code with code in a running system that performs more detailed validation of the offered firmware.

What version of firmware was originally installed?
What caused the device to be in a bricked state?
What has guided your choice to use the NVR_K51_BL_ML_STD_V4.40.015_200616 version to try to update from?
 
alastairstevenson said:
From your transcript, it seems the uImage originally on the primary boot partition was an older version that doesn't use the fairly new 'update_v3' firmware update method.
This method replaces the bootloader update code with code in a running system that performs more detailed validation of the offered firmware.

What version of firmware was originally installed?
What caused the device to be in a bricked state?
What has guided your choice to use the NVR_K51_BL_ML_STD_V4.40.015_200616 version to try to update from?
Click to expand...
Hi mate,

Honestly can't remember the firmware it originally used!

Basically when I got it I updated it using the model number from the listing (uploaded file to NVR), and it started bootlooping, later realising the model on the listing didn't match the NVR. After this me and a friend tried other firmwares & methods until we got to where we are now.

The choice from this firmware is just as it was the only one we could find thats fairly new and that would actually download to the NVR without it hanging
 
NACA_FAS said:
Basically when I got it I updated it using the model number from the listing (uploaded file to NVR)
Click to expand...
So I'm guessing - the device you bought was listed as a DS-7608NI-K2/8P and was actually a DS-7608NI-I2/8P to which various firmware versions have now been loaded.
It does look like it's got into an inconsistent state it can't automatically recover from.

I've used the newest I2-series firmware on K2-series NVRs to see how well they make use of the new features, but found the results to be quite variable and quirky.
The new web 4.5.x interface still needs some work.

Presumably you've come across this range of I-series firmware versions :
 
alastairstevenson said:
So I'm guessing - the device you bought was listed as a DS-7608NI-K2/8P and was actually a DS-7608NI-I2/8P to which various firmware versions have now been loaded.
It does look like it's got into an inconsistent state it can't automatically recover from.

I've used the newest I2-series firmware on K2-series NVRs to see how well they make use of the new features, but found the results to be quite variable and quirky.
The new web 4.5.x interface still needs some work.

Presumably you've come across this range of I-series firmware versions :
Click to expand...

Yeah it was listed as a K2, but is actually an I2

Pretty sure I have come across that firmware, do I need to take any other steps before flashing it on?
 
So I think I jinxed it..

Now at random points its crashing (using a display on hdmi, setting the output to 1080p, viewing it on ivms etc)... Any clue on possible causes / fixes?
 
NACA_FAS said:
Now at random points its crashing (using a display on hdmi, setting the output to 1080p, viewing it on ivms etc)
Click to expand...
Bummer!

NACA_FAS said:
Any clue on possible causes / fixes?
Click to expand...
You could hook up the serial console again to see what complaints there may be if it's a reboot that's happening.
But if I remember correctly, by default it runs quietly on the newer firmware.

Try typing the command
ttyAuth
about 10 seconds after bootup.
Then type 'admin' press Return and the admin password and press Return.
Don't worry if it doesn't immediately echo.
That should get it back to a chatty state.
 
You must log in or register to reply here.
Top Bottom