DS-2CD2632F-IS not more working after update v5.4.0 R0

Hello,

I'm still looking for a solution, an help .... In France it's difficult to find a good reseller with honnest prices. Then this one came from a Chinese Reseller ...
I was hoping that peraphs someone can help me to solve it. But seems that is perahps more complicate ...
 
Have a look at my 2xx2 downgrader post.

It's for English cameras, but there's a good chance it could help.

TFTP it to your camera and then let it reboot. If it was accepted (not sure) it will complain of language mismatch because your camera is Chinese, but it will reset the flag Brad C discovered.

Then you can TFTP Chinese 5.3.0 firmware to it or whatever.

Of course if not work then let me know.
 
The 2632 is not mentioned in the Supported Product List in the PDF that comes with the v5.4.0.

EDIT:I doesn't see like any of the 3MP 2x32 cameras are supported
 
Last edited by a moderator:
Enabler said:
Have a look at my 2xx2 downgrader post.

It's for English cameras, but there's a good chance it could help.

TFTP it to your camera and then let it reboot. If it was accepted (not sure) it will complain of language mismatch because your camera is Chinese, but it will reset the flag Brad C discovered.

Then you can TFTP Chinese 5.3.0 firmware to it or whatever.

Of course if not work then let me know.
Click to expand...
Hi Enabler,

Unfortunally, camera don't want to come back ... Here the log of TFTP
[2016-07-12 08:54:23] TFTP server[192.0.0.128] initialized

[2016-07-12 08:54:46] Device[192.0.0.64] test tftpserver

[2016-07-12 08:54:55] Connect client[192.0.0.64] success

[2016-07-12 08:54:55] Start file[C:\IPC_R0_EN_STD_5.3.0_160325_downgrader\digicap.dav] transmitting

[2016-07-12 08:55:21] Completed file[C:\IPC_R0_EN_STD_5.3.0_160325_downgrader\digicap.dav] transmit

[2016-07-12 08:55:44] Device[192.0.0.64] system update completed!
Click to expand...
When done, I close TFTP, Unplugged, wait and plugged the camera. It start for few seconds (I can see activity on my switch). I can only see it with arp -a command line.
I try to ping it, don't work. With browser too, SADP see nothing.

I think my camera is totally lost in the starting block because seems always rebooting :(
 
I assume you've not messed with mtd files etc right?

If you ping -t 192.0.0.64 and plug in, how long until it restarts?

Now had my firmware on version flag should be reset. What happens if you now TFTP Chinese 5.3.0 to it?
 
Regarding mtd files , i dont understand what you mean. I changed nothing manually. I've done the update to 5.4.0 with web interface when caméra was still running

Regarding ping-t i've that :
e88d2963f3f59feefa06a83c062a50da.jpg

Regarding the CN firmware 5.3.0, the confirmation of system updated don't appear in TFTP. i can see it with arp -a. When in this status, i try a ping -t , message is "impossible to reach ...."
 
Last edited by a moderator:
I tried 5.3.0 EN , confirmation system updated...but dont work after reboot
Regarding rebooting , it reboot approximatively each 40sec
 
Last edited by a moderator:
IL-MAFIOSO said:
There is a excel document listing the camera . My camera is a R0 . On same link you can find the R0 category...
Click to expand...

Yes your camera is a R0 (as is my 2132) but the fact is that none of the 3MP cameras are listed as being supported by the v5.4.0 update. These cameras have been listed to be supported with every IPC R0 firmware update until now (including v5.3.8), go back and have a look if you don't believe me.

So I can only conclude that until somebody tries and confirms otherwise, these cameras are not supported.
 
I installed 5.4.0 on a 2CD2332-I and it worked perfectly. I believe that's an R0 camera.
I don't put any faith in Hikvision documentation being accurate (or spec sheets for that matter).
 
hi, at the end somebody found a way to recover a Chinese R0 cam flashed with 5.4.0 firmware? I'm stuck in the same situation...
 
You must log in or register to reply here.
Top Bottom