R0 / DS-2CD2x32 BrickfixV2 brick recovery and full upgrade tool - enhanced.

but no follow-on seen.
Which is a bit odd.
Presumably the brickfixV2 digicap.dav is still in the tftpserve.exe folder.

A bit of a long shot, for no real reason - your PC is extremely chatty on IPv6 - maybe temporarily disable IPv6 and see if that changes anything.


Also - if the camera isn't currently bricked, you should be able to use the web GUI as normal to do a firmware update using the brickfixV2 firmware (probably the EN header version), via the maintenance menu with the PC IP address as normal.
Then after the update is complete, change the PC IP address to 192.0.0.128 and proceed to Stage 2.

I can't get to it via web, batch updater or any hiktools - even when I had no web interface on the old bricked cameras I could get rstp, but not this one.
turned off ipv6 - similar result - just the "test tftpservier"

yes, the brickfixv2 digicap is still in the tftp server - seems to be failing its tftpserver test...
 
turned off ipv6 - similar result - just the "test tftpservier"
That is odd.
The initial handshake is normal - the tftp updater responds, but then no follow-on from the camera.
There is the tftp updater clone, by Scott Lamb, but this has only been useful when the digicap.dav file exceeds 32MB, which is not the case here.

I suspect if you want to spend the time to explore this further, it will have to be via the serial console.
 
That is odd.
The initial handshake is normal - the tftp updater responds, but then no follow-on from the camera.
There is the tftp updater clone, by Scott Lamb, but this has only been useful when the digicap.dav file exceeds 32MB, which is not the case here.

I suspect if you want to spend the time to explore this further, it will have to be via the serial console.
Thanks - that is what I was worried about...

same result with python version - "replied to magic handshake request." then nothing!

Let me crack this thing open!

thank you for the help!
 
It will be interesting to see what you find.
Do you have the needed serial TTL to USB convertor? PL2303TA works ok.
And the 4-pin 1.5mm ZH JST wired connector?
 
I've downloaded this stuff, and I'm going to read through the pages here and give this a shot tonight.

I have 3 2342WD Turret cams that WERE working fine, and I'd previously updated from 5.3.8? to 5.4.5. Last night I tried to load the latest firmware and FireFox locked up. I've tried the Hikvision tftpd tool and the cameras each respond to the handshake and the firmware is downloaded, but I'm assuming they're rejecting the firmware as there's no "Update Complete" message and the cameras are still unresponsive. I can usually see them on the Hikvision Installation tools, and they're showing a v4.x.x firmware and now have a default admin password of 12345, but there's no WebGUI access.

Wish me luck I guess... These are practically new after sitting on my shelf in the box for 2 years, and I'd hate to have them as paperweights now.
 
These are R6 series cameras, so the brickfixV2 method is not applicable to them, it's for R0 only.

If the firmware version showing is 4.0.8 the camera is running in the min-system recovery mode due to installation of incompatible firmware.
This is a basic system with no web services.

Where did you download the firmware from? Can you provide a link?
You might just need to install valid firmware to recover them.
 
Thanks for the reply, I didn't realize these weren't R0 cameras!

With these being (supposed to be) US market cameras, I downloaded all the firmware updates from the US Hikvision website. I can link to the specific firmware if it would help.

I do have a copy of the last stable firmware update, but I don't know how to upload it without tftpd, which I've tried and it never succeeds.
 
I do have a copy of the last stable firmware update,
With the downgrade block and other aspects - it would be helpful to know what firmware version was on the camera before the attempted update if you can recall, and also what exact version(s) was attempted that caused the problem.
The downgrade block takes effect whether the update was successful or not.

There is a good selection of versions here :
 
Thanks for the info about the downgrade block, flashed the newest firmware and got the cameras up!

Now I just have to figure out this issue with IE not properly displaying the configuration page... None of the menu items on the left are click-able.
Hik_Config.jpg
 
  • Like
Reactions: alastairstevenson
That's likely to be due to the browser cache no longer matching the newer web structure of the newer firmware.
Either refresh the page or clear the browser cache, that should fix it.
 
Any 12v 1.5A centre-positive power supply, widely available on eBay or even Amazon.

It's likely to be a timing problem.
You might get lucky if you just keep retrying the power cycling, than can happen.

Finally got it done.

First of all, obviously used 12v adapter. Secondly I changed the camera's IP to 192.0.0.64 and 255.255.255.0. Still no luck. (Even tried 192.168.1.64 camera and 192.168.1.128 pc with no luck). In the end I disabled windows firewall and reverted IPs back to 192.0.0.64 and 192.0.0.128, boom it went success, but stuck at "download completed" section. Then used CH version file to get "update completed" stage.

So anyone having trouble like mine try disabling windows firewall, looks like it was mother of all problems.
 
Finally got it done.
Hey, well done!
And thanks for posting an update.

A couple of minor comments, for others info :
Secondly I changed the camera's IP to 192.0.0.64 and 255.255.255.0. Still no luck.
The configured IP address in the normally running state is not connected to the value the camera uses when probing for the Hikvision tftp updater.
The probe is done using an IP address that is set in the environment variables of the bootloader.

In the end I disabled windows firewall
Interesting.
Normally when the Hikvision tftp updater is first started, there is a Windows firewall popup to request allowed inbound access to the tftpserve.exe program.
Clicking 'OK' implicitly creates the inbound firewall rule.
Do you remember if you got this popup?
 
Hey, well done!
And thanks for posting an update.

A couple of minor comments, for others info :

The configured IP address in the normally running state is not connected to the value the camera uses when probing for the Hikvision tftp updater.
The probe is done using an IP address that is set in the environment variables of the bootloader.


Interesting.
Normally when the Hikvision tftp updater is first started, there is a Windows firewall popup to request allowed inbound access to the tftpserve.exe program.
Clicking 'OK' implicitly creates the inbound firewall rule.

Do you remember if you got this popup?

Yes that was done when i did my 2332 succesfully.
 
Awesome thread sir, thank you...

Perhaps know what firmware to use for DS-2DE2202I-DE3/W20160220CCCH575946125

I went through the above fix and installed a multi language firmware 5.3.9 and getting language mismatch error again :)
 
Disregard last post from myself :)

I had ran the EN brickfix mistakenly instead of CN.... Really appreciate all the help here on the forum, thank you everyone!!
 
  • Like
Reactions: alastairstevenson
Hi Guys, it is a bit off topic, but little related. Does anyone notice 2432 is running a little grainy in low light/night after updating firmware to 5.4.5? What sort of video/image settings running to overcome this?