DS-2CD2332-I .. semi bricked after firmware update

M

m4gery

n3wb
Jul 18, 2016
6
0
Not knowing any better, i updated the firmware on my DS-2CD2332-I to 5.3 via he web gui, even thought looking at the sticker afterwards that is what it shipped with. I thought it was totally bricked, but found a python script that acted as a TFTP server. Now it's "semi" bricked; it shows up in SADP. I'm able to change the IP and ping it. However, now it says the version is v4.0.8, which i don't understand at all.

Any ideas on how to get it working again?
 
4.0.8 means MiniSystem which means camera is in fail mode. Now you need to find a correct firmware to upgrade via TFTP.
 
However, now it says the version is v4.0.8, which i don't understand at all.
Click to expand...
That's what's called 'Min-system mode', it's a recovery mode with minimal services (eg no web services) that the camera enters when flashed with incompatible firmware.
You might see 'Min-system' in SADP at the serial number.
Try the 5.3.0 to 5.2.5 downgrader from here - the 1-line version. The download link also holds the Hikvision-specific tftp tool and instructions.
https://www.ipcamtalk.com/showthrea...are-Downgrader-5-3-0-Chinese-to-5-2-5-English
 
I have another of the exact same camera brand new in the box, is it possible to extract the firmware from it?
 
Well, in theory, if the firmware is old enough to support telnet or SSH, you could connect to a root shell, mount, say, an NFS share (though you can to that in the web GUI, NetHDD) and copy out the /dev/mtdblocks
But you'd need first to get telnet access to the semi-bricked camera. Some do / some don't when in recovery mode.
The 'downgrader' is much the best option.
 
alastairstevenson said:
That's what's called 'Min-system mode', it's a recovery mode with minimal services (eg no web services) that the camera enters when flashed with incompatible firmware.
You might see 'Min-system' in SADP at the serial number.
Try the 5.3.0 to 5.2.5 downgrader from here - the 1-line version. The download link also holds the Hikvision-specific tftp tool and instructions.
https://www.ipcamtalk.com/showthrea...are-Downgrader-5-3-0-Chinese-to-5-2-5-English
Click to expand...
This +1. It's one of the top stickies here.

Don't use the 4-line version.
 
Tried the downgrader thing, the camera never talks to the TFTP server. Yes, my IP is set to 192.0.0.128 with a 24 bit mask. :)
 
I was hoping the downgrader would work. Honestly, in the two hours i've tried to get it to work, i've made enough money to buy another camera vs. screwing with Chinese crap that breaks.

I do appreciate you guy's help though.

Off to buy an Amcrest.
 
m4gery said:
I was hoping the downgrader would work. Honestly, in the two hours i've tried to get it to work, i've made enough money to buy another camera vs. screwing with Chinese crap that breaks.

I do appreciate you guy's help though.

Off to buy an Amcrest.
Click to expand...

An Amcrest? Don't be silly. That's a bad idea but hey ho, you're so rich that it doesn't matter.

You need to try to flash a different version of v5.3.0 on. Then use the downgrader. Sometimes you need the Chinese v5.3.0 version.

Btw, you broke it, it didn't break itself.
 
Its not chinese crap that breaks. Its users who buy china region to save a few bucks off the US region cameras, without researching first.
Amcrest is likely rebranded dahua. You can buy dahua for less. FYI, amcrest is a company out of texas that formally distributed foscam (foscam.us) ..they have reportedly left foscam customers out to dry.
 
Lol.. I like how it's my fault the thing doesn't work now.

I bought the camera off of a recommendation. Then i tried to apply an update from the manufacturer's web site. Forgive me for not researching the intricacies of managing a $100 camera.
 
m4gery said:
Lol.. I like how it's my fault the thing doesn't work now.

I bought the camera off of a recommendation. Then i tried to apply an update from the manufacturer's web site. Forgive me for not researching the intricacies of managing a $100 camera.
Click to expand...
It is your fault as you purchased from a scammer who failed to disclose that the camera was a China region hacked camera...had you done even a bit of basic research you would have known what to look for...and not to attempt a firmware updatethe camera is not the problem..the seller is
..
Most improtant you should be thankful for the information about Amcrest. Not defensive.
 
Ok, so I had some issues with a genuine 2332-I also.
Here are my notes.
I had a 2332-I with 5.2.0 on it from the factory. I upgraded it to 5.2.5 as found floating around on the forum in the downgrader package by tftp. Once I did that I was unable to load any other firmware on the camera. When I next tried to tftp a firmware to the camera, it wiped the flash and refused to accept the update. It was just stuck in min system mode.
I got into the camera with the serial console and managed to clone the mtd across from one of the others that is working and was back up and running.
Long story short. Upgrading to 5.2.5 using the web interface appears to be fine, but upgrading it using tftp leaves the camera broken (in that you can no longer change the firmware version).
I didn't do any more investigation into why that is/was, but I have a big note in my 5.2.5 directory not to tftp it to a camera for that reason.
I have 4 2332-I and a 2532F-I all running 5.2.5 that were upgraded using the same binary via the web interface, and I can up/downgrade those at will. The other 2332-I is now running the same version upgraded from 5.2.0 using the web interface and that's all good to, but if I were to tftp it to the camera I'd be stuck in the same situation.
I don't know what mods are made to that version in the downgrader, but the console kept spitting out language mismatches when I tried to tftp a firmware to the camera. Bear in mind all my cameras are genuine CCWR units.

What the heck, I learned about the serial console, how the mtd was structured and recovered the camera, so it wasn't a total loss.
 
  • Like
Reactions: alastairstevenson
Yes, but that is a special circumstance. You wont have that issues with firmware from the hikvision site updated via the web interface if its a US region camera.
 
Oh, no. Absolutely it was my own fault for using some random firmware I dredged up off a forum. I just could not find a "legit" download of 5.2.5 and wondered if there was any practical benefit over 5.2.3 (answer - no).
I was noting it more because it might trigger a lightbulb somewhere and some random in the future might say "hey, that's what my camera is doing and this random bloke on the net fixed his by doing *this*". Of course I could be just throwing more mud in the water too :)

I found it interesting the old Hik 3MP 2 line stuff uses mostly the same Ambarella chipset as Avigilon do in their wicked little 4 channel h264 encoders. Actually, the hardware in the 2332 is surprisingly well built for the price. It's a shame about the firmware though :)
 
  • Like
Reactions: fenderman
You must log in or register to reply here.
Top Bottom