Hi, try to pusch * key during the boot, you must have prompt.
After you can follow my instruction.
After you can follow my instruction.
DHI-NVR5432-16P-4KS2 won't boot up after upgrade
- Thread starter kamils
- Start date
Hi, I've problem with my nvr after update. My step:
connected in serial port 115200/8/N/1 - it's OK
Stop autoboot with * key - it's OK
Started tftp server on my Pc with ip 192.168.1.1 255.255.255.0 pointed to unziped files downloaded from dahua - It's OK
Passed run dc (download customs....) - problem:
hisilicon # run dc
stmmac_init,692,0x70431,3
T T T T T
Retry count exceeded; starting again
do_tftp_secure failed
hisilicon #
hisilicon # ping 192.168.1.1
stmmac_init,692,0x70431,3
ARP Retry count exceeded; starting again
ping failed; host 192.168.1.1 is not alive
Defender,firewall, turn off. I don't know which problem's
My nvr has addres 192.168.1.108 dynamic
connected in serial port 115200/8/N/1 - it's OK
Stop autoboot with * key - it's OK
Started tftp server on my Pc with ip 192.168.1.1 255.255.255.0 pointed to unziped files downloaded from dahua - It's OK
Passed run dc (download customs....) - problem:
hisilicon # run dc
stmmac_init,692,0x70431,3
T T T T T
Retry count exceeded; starting again
do_tftp_secure failed
hisilicon #
hisilicon # ping 192.168.1.1
stmmac_init,692,0x70431,3
ARP Retry count exceeded; starting again
ping failed; host 192.168.1.1 is not alive
Defender,firewall, turn off. I don't know which problem's
My nvr has addres 192.168.1.108 dynamic
Last edited:
Ubaid Masood
Getting the hang of it
It is highly suggested to not upgrade multi HDD NVR5-4KS2 from 3.0 (older version than 2019) to 4.0 newest directly.
first need to upgrade to first released version of 4.0 upgrade and then you can upgrade to latest version
first need to upgrade to first released version of 4.0 upgrade and then you can upgrade to latest version
Ubaid Masood
Getting the hang of it
are you trying upgrade the NVR via serial
try
lip 192.168.1. 108
sip (ur tftp server ip)
Savenv
make sure the firmware directory is selected from TFTP server
run da
run up
Hello everyone.
Have a similar problem with DHI-NVR5264-4KS2
Tryed actions from this thread with different firmware v4 versions - no success. Firmware v3 versions - nvr said that its not supported firmware.
I have an error (can see when it connected to com) - stmmac_init,692,0x70431,3
Can anyone help please?
Also Google say that its problem with bootloader and i need to use dump to rescue. Mb anyone have work dump for DHI-NVR5264-4KS2 ?
I'll be glad to any advices. Thanx!
Have a similar problem with DHI-NVR5264-4KS2
Tryed actions from this thread with different firmware v4 versions - no success. Firmware v3 versions - nvr said that its not supported firmware.
I have an error (can see when it connected to com) - stmmac_init,692,0x70431,3
Can anyone help please?
Also Google say that its problem with bootloader and i need to use dump to rescue. Mb anyone have work dump for DHI-NVR5264-4KS2 ?
I'll be glad to any advices. Thanx!
We did it!)
Used this update.img via tftp64:
In console (connected via com):
run up
After reboot NVR started correctly. After this we correctly upgraded it to latest version (via web gui using ie) -
Used this update.img via tftp64:
In console (connected via com):
run up
After reboot NVR started correctly. After this we correctly upgraded it to latest version (via web gui using ie) -
If you do not have a computer with a COM port you can use a USB to serial cable.
It worked with my laptop via USB and NVR
It has to be the exact type which I attached in this message
Can always help
Not sure if I need a null modem or straight thru RS232 cable to connect my laptop to the RS232 port on the back of the NVR?
In the picture you show, is it a null modem or straight thru RS232 USB to serial cable?
Problem witch commend's "Unknown command 'lip' - try 'help' "
hisilicon # ping 192.168.1.55
stmmac_init,692,0x70431,3
miiphy_speed,366,1040
miiphy_speed,366,1040
host 192.168.1.55 is alive
when used commends :
hisilicon # run dc
stmmac_init,692,0x70431,3
miiphy_speed,366,1040
miiphy_speed,366,1040
ARP Retry count exceeded; starting again
do_tftp_secure failed
I don't now where is problem's ;/
I get solution's:
A、Type “mac” , you will see “Unknow command ‘mac’ – try ‘help’ “on the screen, that means , this DVR with an old version software Type “setenv serverip address of the PC” to set the TFTP server ip Type “setenv ipaddr ip address of the DVR” to set the DVR ip Type “save” to save
I must use command: setenv serverip 192.168.1.55 {my addres}
next step's ; setenv ipaddr 192.168.1.108 {my nvr dahua}
next : save
more informations my case 6-7 side
Only one possibility will make the upgrade v4.0 not bootable.
Your NVR is the Chinese version, and the English version is flashed.
Early firmware V3.2 will not verify the hardware regional version.
V4.0 will verify the hardware region.
Unable to boot if the firmware area is wrong.
Your NVR is the Chinese version, and the English version is flashed.
Early firmware V3.2 will not verify the hardware regional version.
V4.0 will verify the hardware region.
Unable to boot if the firmware area is wrong.
Hi all,
You can find the files i used here:
I use
run dr
run du
run up
Regards
HI Alexis
i have the saem issue but am new to the putty and tftp usage could you helpme please? how do i find the machine using the serail cable i have a usb to serial cable would this work?
Many Thanks
Raks
my NVR5xx geave me a message of bad magic number on terminal via telnet
can someone help me please to fix my NVR
I fixed my NVR boot problem using a crossover cable directly from pc to NVR. I used a USB to DB7 serial cable to interrupt the boot process using *. Be sure to set the Gateway on your network settings to the NVR's ip address. Set up your ftp server to use your pc's ip address and the firmware file location. After interrupting the boot process, enter the commands to set serverip and ipaddr as posted by people above. I then entered run up, and away it went.
My problem started when I was away from home. System is on an ups, but power was lost and system went down later during an electrical storm. After restoring the NVR, only 1 of my 4 cameras operated. All 4 cameras are the same model and firmware. I worked with one and never gained access. Using a net monitor it's network card is up and down, maybe between two ip addresses. I was able to ping one 192.168.1.108, showing it is dropping in and out. If anyone else has solved this problem, please post.
My problem started when I was away from home. System is on an ups, but power was lost and system went down later during an electrical storm. After restoring the NVR, only 1 of my 4 cameras operated. All 4 cameras are the same model and firmware. I worked with one and never gained access. Using a net monitor it's network card is up and down, maybe between two ip addresses. I was able to ping one 192.168.1.108, showing it is dropping in and out. If anyone else has solved this problem, please post.
I had another power failure, this time while I was home. I shut down the NVR. When the power came back I turned it on and the UPS it is on went up and down a couple times taking out the NVR firmware again. So what actually took out my NVR and cams was the UPS and not a lightening strike. Reloading NVR firmware at it's regular location failed. I suspect a wall wort there was too noisy. Pulled NVR to another room and firmware went first time through. EmpireTecAndy just got a order from me for a IPC-B5442E-ZE to replace one of my failed IPC-HFW5231EP-Z5E.