Hi, I've recently installed several Hikvision 2032 cameras at my home, and everything was working great. WAS. I had the great idea to update one of them from 5.2.5 to 5.3 , and yep, bricked. So I've read pages and pages of threads, I did find one similar to what I am seeing. The camera shows up in SADR as 192.168.1.64 on firmware 4.0.8 ?? It will respond to a ping, but you cannot manage it, telnet or ssh to it. I have tried updating with multiple firmwares using tftp , some have completed, some have not, but the result is the same. One other weird thing - the camera sticker says 5.3.0 , but it came from China running 5.2.5 , the other 4 like it are running 5.2.5 also. Sorry for the long paragraph, this is not letting me enter a carriage return.
2032I and 5.3 firmware update failure
- Thread starter slickdawg
- Start date
Read carefully and follow this: http://www.ipcamtalk.com/showthread...are-Downgrader-5-3-0-Chinese-to-5-2-5-English
Then give a big thanks to @whoslooking
Then give a big thanks to @whoslooking
Last edited by a moderator:
Thanks for the quick reply. I tried that before with no luck, but since, I've read where turning windows firewall off may help, so I'm trying that right now. Any idea why I cannot enter a carriage return to start a new paragraph? I've used vbulletin for years, never seen this problem.
First - huge thanks to @whoislooking - many of the threads I have read, he has been a major contributor. Appreciate someone taking the time to help like he does, I know it is time consuming. I just completed that, and it appears to have gone successfully. Log file: [2015-08-12 17:31:31] TFTP server[192.168.1.114] initialized
[2015-08-12 17:31:43] Device[192.0.0.64] test tftpserver
[2015-08-12 17:31:53] Connect client[192.0.0.64] success
[2015-08-12 17:31:53] Start file[C:\5.30 Downgrader\digicap.dav] transmitting
[2015-08-12 17:32:26] Completed file[C:\5.30 Downgrader\digicap.dav] transmit
[2015-08-12 17:32:49] Device[192.0.0.64] system update completed!
[2015-08-12 17:31:43] Device[192.0.0.64] test tftpserver
[2015-08-12 17:31:53] Connect client[192.0.0.64] success
[2015-08-12 17:31:53] Start file[C:\5.30 Downgrader\digicap.dav] transmitting
[2015-08-12 17:32:26] Completed file[C:\5.30 Downgrader\digicap.dav] transmit
[2015-08-12 17:32:49] Device[192.0.0.64] system update completed!
The camera responds to a ping, but I get connection refused for telnet, ssh and ftp. Unable to manage in browser, no response. This no carriage return thing is annoying. Anyway, I have tried 5.3 and had no luck. Let me try again not that I have the firewall turned off. Since my camera came from China (aliexpress) , is this the right 5.3 to use? http://www.hikvision.com/en/us/download_more.asp?id=1499
We have a pulse!! The camera rebooted and showed up in SADP as 192.0.0.64 , I was able to get to the GUI this time. I changed the IP to what it was, let it reboot, it came online, then unplugged it, plugged it back in, and it came back as expected. I know I tried this 2-3 times without success, however that was before turning off windows firewall. It worked after turning off windows firewall. Thank you @Del Boy for your help! Now I need to go re-mount the camera, I took it down for ease of access.
Last edited by a moderator:
alastairstevenson
Staff member
Well done, you got there!
Yup - the camera probes for the Hikvision tftp server with a UDP packet holding the magic number. If the firewall blocks that the camera feels quite alone.
The firewall rules are set based on your responses when you run tftpserve.exe for the first time.
You could adjust the inbound allow rule manually to save having to turn the firewall off again the next time you need to use tftp recovery ...
Yup - the camera probes for the Hikvision tftp server with a UDP packet holding the magic number. If the firewall blocks that the camera feels quite alone.
The firewall rules are set based on your responses when you run tftpserve.exe for the first time.
You could adjust the inbound allow rule manually to save having to turn the firewall off again the next time you need to use tftp recovery ...
I changed the IP of the camera, rebooted it, and now it is not taking my password, the default password, or anything. ugh. At least I'm well experienced in firmware loads now. 