DS-2CD3132F-IWS bricked, tftp re-flashing not working

[neetmans]

Hello,

today I flashed my DS-2CD3132F-IWS camera with the IPC_R0_EN_STD_5.3.0_150814 firmware from the Hikvision website.
I purchased the camera on aliexpress, and at the time of flashing I wasn't aware of the difference between the EN/multi-language and CH versions.

(in the meantime I became aware of this.... ).

Now I've tried multiple re-flashes with TFTP, with the firmware of @whoslooking
The 5.3 downgrader tot 5.2.5.
Also tried the 5.1.6 firmware.

All flashes look like this :
[2015-12-29 17:53:01] TFTP server[192.0.0.128] initialized
[2015-12-29 17:53:24] Device[192.0.0.64] test tftpserver
[2015-12-29 17:53:32] Connect client[192.0.0.64] success
[2015-12-29 17:53:32] Start file[C:\tftp\digicap.dav] transmitting
[2015-12-29 17:54:07] Completed file[C:\tftp\digicap.dav] transmit


Never having the 'system update completed' message.

When powering off and on the camera it appears in the SADP tool after a long time (15+ minutes I think).
It has IP-address 192.168.1.64, can ping, but unable to access it any way. Also HTTP-port is empty, so unable to browse to the camera.

Is there anything else I can try to fix this camera?
Is anyone here willing to help me out with this?

Many thanks guys!

 

[acvb]

Never update Chinese hikvision camera's without reading here 1st. Rule #1.... never update Chinese hikvision camera firmware. Rule #2 ... Return camera fast if you updated the firmware. Rule #3... look for "whoslooking" and ask if he can help. Rule #4... put camera in junk drawer with the old foscams and lessons learned.

 

[alastairstevenson]

When powering off and on the camera it appears in the SADP tool after a long time

What is the firmware version on the camera as displayed by SADP, and how does that compare with the version that you last flashed?
If the camera is booting into a 'recovery mode' due to incompatible firmware, or a hardware problem, it usually shows as a 4.0.8 version, maybe with 'min-system' showing in the serial number.

 

[neetmans]

indeed it is showing version 4.0.8 or something similar in SADP. Mini-system is not in the serial number field.
A lower version as it was shipped with.

I flashed it to version : IPC_R0_EN_STD_5.3.0_150814
(which went wrong).
Afterwards I tried several other versions, but no luck.

SADP initially said firmware 5.2.5 build 141201 was on it.
(probably a chinese version).
The box the camera was in says v5.3.0_150513

 

[alastairstevenson]

From what you've described, the camera is a Chinese region camera that was running 'hacked to English' firmware.
Worth trying anyway is to ask the reseller for a copy of the firmware that they loaded on to it.

The camera is booting into a 'recovery mode', that's what the 4.0.8 in SADP shows.
There is a fair chance that @whoslooking downgrader will fix your camera - but make sure you give it maybe 10 mins for the firmware to be written after the file transfer:
https://www.ipcamtalk.com/showthread.php/4036-Custom-Firmware-Downgrader-5-3-0-Chinese-to-5-2-5-English
Maybe try the first link initially - the one without the 4-line mod.

 

[Enabler]

Don't put it in a drawer if all else fails, put Chinese 5.3.0 on it and configure with Chrome (auto translate) or an ONVIF application.

Main problem would be if you have a Hikvision NVR which will want the camera to be English.

 

[whoslooking]

I can confirm that the downgrader does work on this model.
What you would need to do is re-flash the Chinese 5.30 via tftp to recover your camera. then using Chrome so you can translate to English update via the Web interface using the downgrader (yes it will work).

Then after the upgrade reboot.
Job done, now leave the camera alone.

 

[neetmans]

Thanks guys for the tips.
I have downloaded IPC_R0_CN_STD_5.3.0_150513.zip for the Chinese firmware.
Unfortunately the cam keeps hanging at :

[2016-01-02 19:47:33] TFTP server[192.0.0.128] initialized
[2016-01-02 19:48:30] Device[192.0.0.64] test tftpserver
[2016-01-02 19:48:40] Connect client[192.0.0.64] success
[2016-01-02 19:48:40] Start file[C:\tftp\digicap.dav] transmitting
[2016-01-02 19:49:06] Completed file[C:\tftp\digicap.dav] transmit

Not getting the 'system update completed' message.
Maybe because the wrong firmware flashed was 5.3.0_150814 (English), and now trying to flash 5.3.0_150513 Chinese?

Or isn't it nessescary to have same versions?

Thanks!

 

[normel]

I also landed in same position( while trying to fix a camera of a friend ,, he stranded also in same situation.. he tried to update a Chinese cam.. bumbb
trying to flash 5.3.0_150513, not getting SYSTEM UPDATE COMPLETED message.. it just hangs forever at Completed file[C:\tftp\digicap.dav] transmit

 

[marku2]

Maybe we need to do a picture by picture sequence on how too.do this it does work I've tried on a little cube that was in recovery mode it has Chinese
Language now just waiting for some cables so I can mount the board and flash the full English into it

 

[alastairstevenson]

he tried to update a Chinese cam..

If the firmware tried was 5.4.0 or higher - it may be that the anti-rollback has trapped the camera.
If it's a DS-2CD2x32-I, check out this fix-up roundup : Hikvision DS-2CD2x32-I (R0) brick-fix tool / full upgrade method / fixup roundup.

now just waiting for some cables so I can mount the board and flash the full English into it

Although the serial console is pretty much a life saver, with the 5.2.5 CN firmware you can easily do the 'enhanced mtd hack' via the telnet or SSH access that 5.2.5 still has and do the full update that way.

 

[normel]

@alastairstevenson
It indeed was 5.4.0 or higher. Thanks again. It surprises me each time how helpfull you can be, ( others also, but especially you ) Big thanks.