whoslooking
IPCT Contributor
Help reverting or fixing a 5.3.0 firmware update
- Thread starter tastle
- Start date
fer.dexter.fer
n3wb
- Joined
- Jun 23, 2015
- Messages
- 1
- Reaction score
- 0
Hi everyone,
I have similar problem with my DS-2CD2432F.(Chinese version from aliexpress)
Everything was fine until I try to update with EU firmware V 5.3.0 through web GUI. After that it is bricked.
Right now I am crazy from trying different solutions to recover cam.
I tried different version of TFTP but neither one seems to be working.
All I can get is "TFTP server 192.0.0.128 initialized"
I set static IP 192.0.0.128.
Turned off firewall
Turned off firewall + removed inbound firewall rules
Turned off firewall + modified inbound firewall rules
For connection I used
crossover cable + regular 12V power
Ethernet cable + PoE
When I start ping -t 192.0.0.64
Reply from 192.0.0.128: Destination host unreachable.
Reply from 192.0.0.128: Destination host unreachable.
Reply from 192.0.0.64: bytes=32 time<1ms TTL=255
Reply from 192.0.0.64: bytes=32 time<1ms TTL=255
Reply from 192.0.0.64: bytes=32 time<1ms TTL=255
General failure. (sometimes Request timed out.)
General failure.
General failure.
Reply from 192.0.0.128: Destination host unreachable.
Reply from 192.0.0.128: Destination host unreachable.
Reply from 192.0.0.128: Destination host unreachable.
I tried digicap.dav firmware files from (http://www.hikvisioneurope.com/portal)
EU V5.3.0 and
EU V5.2.3
Should I try some other versions or some Chinese versions ?
Where I can find other versions ?
What am I doing wrong?
Any sugestions ?
Tnx in advance.
I have similar problem with my DS-2CD2432F.(Chinese version from aliexpress)
Everything was fine until I try to update with EU firmware V 5.3.0 through web GUI. After that it is bricked.
Right now I am crazy from trying different solutions to recover cam.
I tried different version of TFTP but neither one seems to be working.
All I can get is "TFTP server 192.0.0.128 initialized"
I set static IP 192.0.0.128.
Turned off firewall
Turned off firewall + removed inbound firewall rules
Turned off firewall + modified inbound firewall rules
For connection I used
crossover cable + regular 12V power
Ethernet cable + PoE
When I start ping -t 192.0.0.64
Reply from 192.0.0.128: Destination host unreachable.
Reply from 192.0.0.128: Destination host unreachable.
Reply from 192.0.0.64: bytes=32 time<1ms TTL=255
Reply from 192.0.0.64: bytes=32 time<1ms TTL=255
Reply from 192.0.0.64: bytes=32 time<1ms TTL=255
General failure. (sometimes Request timed out.)
General failure.
General failure.
Reply from 192.0.0.128: Destination host unreachable.
Reply from 192.0.0.128: Destination host unreachable.
Reply from 192.0.0.128: Destination host unreachable.
I tried digicap.dav firmware files from (http://www.hikvisioneurope.com/portal)
EU V5.3.0 and
EU V5.2.3
Should I try some other versions or some Chinese versions ?
Where I can find other versions ?
What am I doing wrong?
Any sugestions ?
Tnx in advance.
Apologies for the threadjack, but I'm puzzled. I have a DS-2CD2532F-I with a Chinese serial number. It was purchased from wrightwoodsurveillance.com a few months ago, and shipped with 5.2.0 firmware. Knowing the risk I was taking, I recently updated it to the European v.5.3.0. I experienced no problems (and everything is still in English). So, what distinguishes the units which are having the problem described in this thread? Apparently, not all the Chinese 2-series cams are affected.
Last edited by a moderator:
So I spent some one-on-one time with Wireshark again. I filtered based on the mac address. I noticed that the camera was looking for something on 192.168.1.1. That's the IP of my router. So I bumped it's IP and set my laptop to be 192.168.1.1. So I waited (takes forever before I see this pop up).
So my computer is responding, but nothing is happening in the TFPT client.
Code:
"No.","Time","Source","Destination","Protocol","Length","Info"
"27868","571.492124000","Hangzhou_2b:6c:02","Broadcast","ARP","60","Who has 192.168.1.1? Tell 192.168.1.64"
"27869","571.492199000","Dell_6d:54:22","Hangzhou_2b:6c:02","ARP","42","192.168.1.1 is at 5c:26:0a:6d:54:22"
"32978","871.749881000","Hangzhou_2b:6c:02","Broadcast","ARP","60","Who has 192.168.1.1? Tell 192.168.1.64"
"32979","871.749961000","Dell_6d:54:22","Hangzhou_2b:6c:02","ARP","42","192.168.1.1 is at 5c:26:0a:6d:54:22"
alastairstevenson
Staff member
That does show that the camera is on the changed default address, and is doing an ARP request for the device that's presumably still configured as the default gateway, ie 192.168.1.1. So it's not totally dead.
But you didn't spot any UDP packets to 192.0.0.128 or ARP requests for that? You would have to have the computer on that IP segment to see them.
But you didn't spot any UDP packets to 192.0.0.128 or ARP requests for that? You would have to have the computer on that IP segment to see them.
That's correct. I filtered by the camera's mac (src / dst) for any traffic. After waiting a long time, it just repeated. The capture shows exactly what I seen. Prior, when stuck in the boot loop, I was seeing more activity.
whoslooking
IPCT Contributor
Follow the downgrading post about 5.3.0
I re-read this and realized I didn't test exactly what you inquired.
So I put my Ethernet back to 192.0.0.128 and turned on wireshark and powered up the camera. I don't see a single thing in the over 10 minutes I've left it running that looks like the camera is issuing anything to or from 192.0.0.128.
Code:
"No.","Time","Source","Destination","Protocol","Length","Info"
"34","18.351039000","192.0.0.128","192.0.0.255","NBNS","92","Name query NB N0503<20>"
"36","18.351432000","192.0.0.128","224.0.0.252","LLMNR","65","Standard query 0xd024 A n0503"
"38","18.351760000","192.0.0.128","224.0.0.252","LLMNR","65","Standard query 0x035e AAAA n0503"
"39","18.655416000","192.0.0.128","192.0.0.255","NBNS","110","Release NB WORKGROUP<1d>"
"40","18.655600000","192.0.0.128","192.0.0.255","NBNS","110","Release NB <01><02>__MSBROWSE__<02><01>"
"41","18.655790000","192.0.0.128","192.0.0.255","NBNS","110","Release NB WORKGROUP<1e>"
"42","18.657714000","192.0.0.128","192.0.0.255","NBNS","92","Name query NB WORKGROUP<1e>"
"45","18.761769000","192.0.0.128","224.0.0.252","LLMNR","65","Standard query 0x035e AAAA n0503"
"46","18.761994000","192.0.0.128","224.0.0.252","LLMNR","65","Standard query 0xd024 A n0503"
"47","19.100502000","192.0.0.128","192.0.0.255","NBNS","92","Name query NB N0503<20>"
"48","19.405570000","192.0.0.128","192.0.0.255","NBNS","110","Release NB WORKGROUP<1e>"
"49","19.407517000","192.0.0.128","192.0.0.255","NBNS","92","Name query NB WORKGROUP<1e>"
"50","19.850749000","192.0.0.128","192.0.0.255","NBNS","92","Name query NB N0503<20>"
"52","20.155760000","192.0.0.128","192.0.0.255","NBNS","110","Release NB WORKGROUP<1e>"
"53","20.157726000","192.0.0.128","192.0.0.255","NBNS","92","Name query NB WORKGROUP<1e>"
"55","20.910556000","192.0.0.128","192.0.0.255","NBNS","92","Name query NB WORKGROUP<1e>"
"56","21.660331000","192.0.0.128","192.0.0.255","NBNS","92","Name query NB WORKGROUP<1e>"
"58","22.410753000","192.0.0.128","192.0.0.255","NBNS","92","Name query NB WORKGROUP<1e>"
"95","52.169768000","192.0.0.128","192.0.0.255","NBNS","92","Name query NB WPAD<00>"
"97","52.170849000","192.0.0.128","224.0.0.252","LLMNR","64","Standard query 0xcd61 A wpad"
"99","52.171743000","192.0.0.128","224.0.0.252","LLMNR","64","Standard query 0x6c39 AAAA wpad"
"102","52.581635000","192.0.0.128","224.0.0.252","LLMNR","64","Standard query 0x6c39 AAAA wpad"
"103","52.581647000","192.0.0.128","224.0.0.252","LLMNR","64","Standard query 0xcd61 A wpad"
"104","52.919452000","192.0.0.128","192.0.0.255","NBNS","92","Name query NB WPAD<00>"
"105","53.669650000","192.0.0.128","192.0.0.255","NBNS","92","Name query NB WPAD<00>"
"783","654.426915000","192.0.0.128","192.0.0.255","NBNS","92","Name query NB WPAD<00>"
"785","654.427887000","192.0.0.128","224.0.0.252","LLMNR","64","Standard query 0x4041 A wpad"
"787","654.428869000","192.0.0.128","224.0.0.252","LLMNR","64","Standard query 0x977f AAAA wpad"
"790","654.839558000","192.0.0.128","224.0.0.252","LLMNR","64","Standard query 0x977f AAAA wpad"
"791","654.839799000","192.0.0.128","224.0.0.252","LLMNR","64","Standard query 0x4041 A wpad"
"792","655.176542000","192.0.0.128","192.0.0.255","NBNS","92","Name query NB WPAD<00>"
"794","655.926806000","192.0.0.128","192.0.0.255","NBNS","92","Name query NB WPAD<00>"
Code:
"No.","Time","Source","Destination","Protocol","Length","Info"
"448","336.746999000","Hangzhou_2b:6c:02","Broadcast","ARP","60","Who has 192.168.1.1? Tell 192.168.1.64"
"770","636.934341000","Hangzhou_2b:6c:02","Broadcast","ARP","60","Who has 192.168.1.1? Tell 192.168.1.64"I've just upgraded a second brown-box DS-2CD2532F-IS with a Chinese serial number from 5.2.0 to 5.3.0 with no trouble at all. Sure would be nice to know why some work and some don't.
whoslooking
IPCT Contributor
But why upgrade, what benefits do you gain.
but all models with a firmware below 5.2.5 can upgrade as well as downgrade, it's just models with factory firmwares 5.2.5 / 5.2.8 that half issues upgrading to 5.3.0
but all models with a firmware below 5.2.5 can upgrade as well as downgrade, it's just models with factory firmwares 5.2.5 / 5.2.8 that half issues upgrading to 5.3.0
I can only speak from what happened from my point of view, but I did it because I typically update my firmware regularly (security, fixes, etc.) If the thought had crossed my mind that I would have had a problem, I wouldn't have done it. It was completely my mistake, not knowing what I was getting into. I'm just very thankful that I only did one at a time. I almost did both at the same time.
FYI - The camera I bought has v5.3.0 on it, but by looking at the other camera, the seller had downgraded me to 5.2.5 to patch it for English. (I could get the exact build number from the other camera if needed.)
With my problem, I think I'm stuck. I've changed my laptop's ethernet to go on 192.168.1.1 and it'll respond to the camera, but I don't see firmware being transferred.
Are we at the point where the camera is a lost cause?
Again, thank you for everyone's help and I so sorry I've wasted this much time from all of you for my stupid mistake. It's just kinda hard to throw a few hundred bucks in the garbage if there was a was to get it working.
whoslooking
IPCT Contributor
Part of owner responsibility is maintaining the software with the most recent security fixes. This is a matter of best practice, in part to reduce the risk of compromised and abused devices. A networked device that can't be updated with security fixes is not acceptable to me. This particular upgrade included a number of security architecture improvements, as well as feature updates. Here are the release notes (which, by the way, do call out the change to the default IP address and gateway): http://www.hikvisioneurope.com/portal/index.php?dir=Product Firmware/Cameras/DS-2CD2xx2/V5.3.0 build 150513(new)/&file=IP Camera V5.3.0 Release Note .pdf It was only by accident that I purchased Chinese-market cameras. It will not happen again; they'll go back to the seller next time.
Ah, I see. Thank you for that info; good to know.
My apologies, I might have forgotten to explicitly follow up on that. I had read through the thread, and your firmware is the one that I really want to get on my camera. Like REALLY, REALLY bad.
http://www.ipcamtalk.com/showthread.php/4036-Custom-Firmware-Downgrader-5-3-0-Chinese-to-5-2-5-English
I read through the entire thread, and I'll re-read it tonight. But my camera isn't on 192.0.0.64. It's on 192.168.1.64. And it's looking for 192.168.1.1. So I set my PC to that, and as posted earlier, my PC responds. But then nothing happens for minutes. Then the camera asks again 192.168.1.1 to tell 192.168.1.64 it where it is. Again, nothing happens.
I'll give it another go tonight. I'll quadruple check everything, especially firewalls.
Cheers!
whoslooking
IPCT Contributor
- Wireshark is showing that the camera is looking for 192.168.1.1. (Prior, when I was in a boot loop before I got the junky firmware on the camera, it was looking for 198.0.0.128)
- You say TFTP only works on 192.0.0.128.
Does the above mean that I have to use NAT to map one IP to the other? I'll give that a go tonight. Definitely something I didn't try.
I've been lurking/learning for the past week since I made the mistake of upgrading my new DS-2CD2532F-IWS to 5.3 firmware. My cam is stuck on IP of 192.168.1.64 (as shown in SADP). I can't access the web interface. I sure hope somebody is able to figure this out.
whoslooking
IPCT Contributor
FYI - I followed that post and it doesn't help. It ignores the situation where the camera is looking for 192.168.1.1, and that the TFTP software (according to what was said earlier) must run on 192.0.0.128.
I have a friend that might have access to a layer 3 switch that would allow me to do NAT. But in the meantime, I ordered a replacement camera (I can still buy two from China for less than the same prices as one in Canada) to unblock my home installation, while I can muck around with my setup to get this camera to work.
I'll post back when I get access to that layer 3 switch. If I find anything that works, I'll be the first to let everyone know.