Bricked DS-2CD2332-I - anyone can help?

[maxk]

I have a new Hikvision DS-2CD2332-I camera that came with 5.2.0 code which didn't like to play nice with my NAS. So, I decided to downgrade it to 5.1.6 code through TFTP. It took a few reboots but the unit finally downloaded the digicap.dav file and said "system update completed" in the TFTP log window. Well, the unit was supposed to reboot by itself and use the new code. It didn't based on the ping test I was running. I waited a few minutes, telneted into the camera and issued a reboot command. Now it doesn't come back at all and doesn't try to access TFTP. When plugging in the power it replies on 2-3 pings and that's it.
I did a sniffer trace and all I see coming from it are those two or three ICMP replies. Is there any way to revive it?
Does the inside have something like JTAG port which can be used for console access? I can see that it has JP1 connector but have no clue what it's for and what's the pinout. Any help would be appreciated!

 

[blake]

My latest turret domes have a push button on the pigtail. Do yours?

 

[fenderman]

My latest turret domes have a push button on the pigtail. Do yours?

Interesting, good to know. That is a much needed feature.

 

[blake]

Yeah it surprised me. RJ45 CONN, power conn, and a pushbutton.

 

[maxk]

nope, no buttons on this one.

 

[blake]

Hmmm. Gonna have to ask milk..

 

[maxk]

OK. I finally managed to fix this camera. All that was needed is to use a plain Windows machine. I was initially using a Mac or Windows running in a VM. None of these "exotic" configurations seemed to work for reliably but managed to screw the camera initially. So, advise to anybody doing a TFTP re-flash - don't use anything but plain Windows (this still could be a Mac running Windows in a Boot Camp).

 

[Ernie Biancarelli]

I recently FUBAR'd my 2332. Here is what I did to recover it:

0) download the firmware you want to load on the camera. Should have the name digicap.dav (or digicam.dav?)
1) configure a segment of my LAN for 192.0.0.0 subnet
2) get my PC on that segment and assign static IP of 192.0.0.128
3) reboot the camera
4) the camera comes up on 192.0.0.64 -- ping that address until it responds
5) telnet 192.0.0.64
6) log in with: root & 12345
6a) Now, you are at the shell prompt for the failsafe boot loader
7) From your PC, use an FTP program and connect to 192.0.0.64
8) from the FTP program, type 'put digicap.dav'
9) return to the telnet login and do an 'ls -l'. You should see the digicap.dav file in the root directory (/)
10) from the telnet login, type 'upgrade'
11) the Camera will upgrade the program in flash with the contents of the digicap.dav file
12) from the telnet login, type reboot
13) when the camera comes up, you can access the web configuration page @ http://192.0.0.64
14) enable DHCP on the configuration page
15) reboot the camera again
16) undo the LAN address configuration in steps 1-2.
17) find your camera on your LAN and reconfigure

 

[blake]

Man, this makes me feel like I need to go back to school!

 

[TinuSwiss]

Hi. I have the same Problem like you. My DS-2CD3222-I respond only 3 times to a ping request to 192.0.0.64. Im not able to connect to my TFTP-Programm on a Windows 7 System without Firewall.
You say the best Thing is a blank OS.
Can tell me what are doing to restore your cam ?? Witch OS ? Witch TFTP Programm ?
I use 192.0.0.128 for my PC with Windows 7 x64 and TFTPD32-Programm for Listening on Port 69.
But i cant see a Connection from the CAM to the TFTP-Server.

Thank u

 

[nathan7]

The solution Ernie posted made me try and realize my camera was not bricked.

 

[bcurran3]

I recently FUBAR'd my 2332. Here is what I did to recover it:

0) download the firmware you want to load on the camera. Should have the name digicap.dav (or digicam.dav?)
1) configure a segment of my LAN for 192.0.0.0 subnet
2) get my PC on that segment and assign static IP of 192.0.0.128
3) reboot the camera
4) the camera comes up on 192.0.0.64 -- ping that address until it responds
5) telnet 192.0.0.64
6) log in with: root & 12345
6a) Now, you are at the shell prompt for the failsafe boot loader
7) From your PC, use an FTP program and connect to 192.0.0.64
8) from the FTP program, type 'put digicap.dav'
9) return to the telnet login and do an 'ls -l'. You should see the digicap.dav file in the root directory (/)
10) from the telnet login, type 'upgrade'
11) the Camera will upgrade the program in flash with the contents of the digicap.dav file
12) from the telnet login, type reboot
13) when the camera comes up, you can access the web configuration page @ http://192.0.0.64
14) enable DHCP on the configuration page
15) reboot the camera again
16) undo the LAN address configuration in steps 1-2.
17) find your camera on your LAN and reconfigure

This seems very logical and I think would normally work. Unfortunately when I ping the camera it responds 3 times, goes unresponsive for awhile (probably in a boot loop), then responds and repeats. I've tried timing it to when it responds but can't get in via telnet, SSH, or HTTP. Thanks though. I think this would normally work.

 

[alastairstevenson]

when I ping the camera it responds 3 times, goes unresponsive for awhile (probably in a boot loop),

You are probably right.
It sounds like you are going to have to explore the tftp recovery method.
In the link on the first post here is a copy of the Hikvision-specific tftp server and instructions. https://www.ipcamtalk.com/showthread.php/4036-Custom-Firmware-Downgrader-5-3-0-Chinese-to-5-2-5-English
There is a fair chance the firmware there will also work OK, but depends on what camera you have, and when it was manufactured.

 

[bcurran3]

You are probably right.
It sounds like you are going to have to explore the tftp recovery method.
In the link on the first post here is a copy of the Hikvision-specific tftp server and instructions. https://www.ipcamtalk.com/showthread.php/4036-Custom-Firmware-Downgrader-5-3-0-Chinese-to-5-2-5-English
There is a fair chance the firmware there will also work OK, but depends on what camera you have, and when it was manufactured.

To put closure on my woes:

I gave up and started a support case with Hikvision. Their response was that it was a gray market Chinese model and they wouldn't support it. (No thanks Hikvision!)

So I ordered a new one from someone else who advertised it as being a US model. When it came in, I compared the two. THIS IS GOOD INFO TO KNOW FOR THOSE WHEN YOU BUY ONE OF THESE: The Chinese market camera has almost all Chinese writing on the back label. The US market one is in ALL English. Easy to figure out when you know that. And yes, it's a "Duh" moment, but think how much stuff you have that's made in China and still has SOME Chinese writing on it. Also the US market camera has a UL sticker on it as well.

My camera came with 5.2.5 firmware which was working, but made the camera fail when I upgraded it to 5.3.0. I noticed the back label showed it shipped with the latest firmware, but that's not what I got. So the importer that sold it to me flashed it with a modified older firmware - and thus no support for it.

New one is working fine, I can watch my young boys in their bedroom and make sure they aren't trying to kill each other. Haven't gotten audio working yet, but will when I have more time. A lot of hassle to try to originally save about $10.

 

[davedim]

Have 3- DS-2CD2332-i Hik cameras that are bricked. Ran brick recovery tool and SADP brings camera up as DS-2CD-Min-System V4.0.8build 130906.
Ran TFTPD64 / PuTTY and mtd6ro file doesn't require and changes.
(Also tried password recovery before TFTPD64 / PuTTY )
Tried many different firmware versions and camera just gets bricked and end of process again
Is there a specific digicap.dav file I need? V5.2.5 ? Can't find it anywhere..?
Please any suggestions?