DS-2CD4332FWD-I(Z)(S)(H) no access after wrong firmware upgrade

anandrao

n3wb
Feb 6, 2016
3
1
I have a Hikvision IR Outdoor Dome DS-2CD4332FWD-I(Z)(S)(H) Net camera with the following data:

2.8 - 12 mm, 24V- 12.5 W MAX / PoE(802.3af)
3MP, WDR, Motorized VF lens optional, Heater optional

The paper label on the cam says:
Serial Number 516910624, 04/2015
Firmware Version 5.30_150326
DSP Version: V7.0 build 151124
Produkt standard: Q/BFW 004-2011
Hangzhou Hikvision Digital Technology Co., Ltd
MAC: xx:xx:xx:20:3a:9d (first 3 pairs masked by me)

  1. The actual Software build in SADP says that it has the software build V5.3build 151218 and not Version 5.30_150326 that is printed on the label. SADP does not allow me to change any of the settings.
  2. I tried many versions of Firmware updates via TFTP (v. 1.0): update is not reported as completed but remains in the updating loop. I read that this might be normal and the disconnect of the TFTP server should be the solution but the documentation says that I can expect an "upgrade complete" message. Still, with that being done, none of the firmware versions ever gave me access. I even tried a digicap.dav file from the chinese website, but no success.
  3. With Wireshark I found the address192.168.1.64 so I tried to open the website with a browser (Edge, Firefox) and get the following: Access Error: 404 -- Not Found firmware language mismatch: /home/webLib
  4. Telnet or ssh access via IP address 192.168.1.64 or 192.0.0.64 is not possible (no response).
  5. Connection via the Debug TTL connector with a USB-to-TTL adapter and display in Putty or Tera Term give no response at all. The USB port keeps sending data (TXD) to the device, but I see no response neither in Putty nor looking at the LED blinking at the adapter(RXD).
  6. Here a list of firmware versions I have tried:
IPC_R1_EN_STD_5.3.0_150326
IPC_R1_EN_STD_V5.4.41_Build170310
IPC_R3_EN_STD_5.3.0_150326
IPC_R4_EN_STD_5.3.0_150326
IPC_H0_ML_STD_V5.4.5_Build170302
20:DS-2CD4xxx、5xxx系列升级包
brick_fixv2

Is there anything else I can try to get the baby back to me?
Cheers and thanks in advance for advice
Martin
 
Thanks for commenting:) Yes I was guessing it´s an R1. I finally got the Debug TTL connector working but may have given it a command so that the firmware upgrade does not work anymore. Looks as if the whole system is mangled and it also looks very complicated to me as a user. Looks as if this is now at a state where I will need to dump that piece because there is too little ressource for help with it. I guess someone in possession of the right software could get it to work, but I can´t. Frustrating that a stupid firmware upgrade had brought that nice cam to garbage...
 
  • Like
Reactions: alastairstevenson