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

Update: The TFTP procedure worked flawlessly for the 5 cams. All I did was start the software then plug in the cam and the update took 2 minutes. I unplugged the cam and plugged back into the NVR POE port and it showed as a plug and play device with an image. Cam and PC only were plugged into switch for the procedure. The customer does not have internet for the recorder so I will leave well enough alone with the cams at 5.2.5. If he calls with internet I will upgrade each cam in sequence. Cams were originally from the US so I did not have to worry about the MTD hacks.
 
  • Like
Reactions: alastairstevenson
Well, that's a good result.
Curious though what happened to the cameras via the update button if there was no internet connection to download firmware.
Maybe it did a preparatory erase then could not download firmware, so left the cameras in that state.
The upf command in the bootloader used to work in that way.
 
alastairstevenson said:
Well, that's a good result.
Curious though what happened to the cameras via the update button if there was no internet connection to download firmware.
Maybe it did a preparatory erase then could not download firmware, so left the cameras in that state.
The upf command in the bootloader used to work in that way.
Click to expand...
I downloaded the latest firmware onto USB from home and applied it that way. I am curious to see if it would have worked if I applied them in sequential order. Not going to find out ;)
 
Thanks mate, fantastic description of the process, works flawless!
Just upgraded 2 DS-2CD2432F-IW's and 4 DS-2CD2032-I's from 5.2.X to 5.4.5. All but 1 have Chinese serials.
I bricked one of them but I must have made a mistake as the 2nd go worked fine.
 
I'm a bad learner...
On my model DS-2CD2132F-IS once had native firmware 5.2.5 141201. After crazy experiments, I turned it into a brick.
I used "Step By Step Guide" and stuck in step 8. SADP now defines my camera as DS-2CD-Min-System...CCRR...

"8. Using PuTTY, start a telnet session to 192.0.0.64 and make sure the telnet radio button is selected."
How? How to use Putty? It looks different for me than on the video instructions.
What do I need to run / activate / press / enter in order to become like a guru in the screenshot?

Will I be able to install the final firmware IPC_R0_EN_STD_5.4.5_170401?
Or do I not need Putty, and can I upload firmware 5.2.5 or 5.3 right now to work through the Web interface or connect the camera to the DVR?
 

Attachments

  • Snap_2020.02.01.jpg
    Snap_2020.02.01.jpg
    99.3 KB · Views: 21
  • Snap_2020.02.01_23.jpg
    Snap_2020.02.01_23.jpg
    90 KB · Views: 19
Last edited:
Did you try TFTP as mentioned in this thread? It is really easy as described in my Jan 20 post. If you read through the early parts of this thread you will see where to get the TFTP program.
 
south_sun said:
How? How to use Putty? It looks different for me than on the video instructions.
Click to expand...
No, it's the same.
As per the instructions, you need to select the Telnet radio button for the connection type for the PuTTY session, not SSH.
Look just above where you have put the red arrow in your PuTTY screenshot.
It will be OK when you've done that.
 
JMan said:
Did you try TFTP as mentioned in this thread? It is really easy as described in my Jan 20 post. If you read through the early parts of this thread you will see where to get the TFTP program.
Click to expand...
Using TFTP, I uploaded brickfixv2EN.dav to my camera. I don’t have a DVR yet. Next manipulations are required with Putty.

alastairstevenson, look at my actions. Why doesn’t it work like you?
 
Last edited:
Ok. I left it as it is. Nothing happens.
P.S. I guessed that I need to enter IP and click open. "The ice has broken, gentlemen of the jury"))
 

Attachments

  • Snap_2020.02.03_21h02m23.jpg
    Snap_2020.02.03_21h02m23.jpg
    66.6 KB · Views: 5
Last edited:
  • Like
Reactions: alastairstevenson
OMG! It works! I hardly understood what I was doing. It was like how to land on the moon when your actions dictate to you on the phone)) I jumped straight to 5.4.5 !!! New password, activation, and I say hello to the other side of the Earth!) Thank you, friend!
 

Attachments

  • Snap_2020.02.03_22.jpg
    Snap_2020.02.03_22.jpg
    59.9 KB · Views: 7
  • Snap_2020.02.03_223.jpg
    Snap_2020.02.03_223.jpg
    317.7 KB · Views: 7
  • Like
Reactions: alastairstevenson
Hi Guys,

I'm looking to fix my DS-2CD2132 since I seem to have bricked it this evening.

I got to the point where I used TFTP and restore the cam to working condition on a 5.2.5 firmware. Everything seems to work, until I reboot it.
Setting seem to be saved. Now it's still replying to ping on the IP address I gave it, but after about 40 replies, the ping gives about 8 timeouts and then starts responding again. (and it keeps doing that).

Webinterface is not working, Telnet/SSH is not working.

Can someone please tell me how to fix my cam?

Thanks!
 
So say someone successfully unbricks 9 cameras using this method, but in the process irretrievably loses the mtd files for one. Is there any hope for recovery? Asking for a friend. ;)

The good news is that the camera took the 5.2.5 firmware and is reliably stuck in min system mode, so I can telnet to it. I tried modifying the mtd6 from another camera (similar, but not identical.. the one which remains bricked is a DS-2CD2132F-IS, and the MTD I had was from a DS-2CD2132F-IWS. (In that MTD I edited a byte of the mac address to make it unique, and appropriately altered the checksum - I also simply tried to edit the ASCII portion of the name to remove the W and moved the S back to the previous byte)

I may have a DS-2CD2132F-IS installed and in service. If that is the case is there an easy way to pull the mtd's off that (If I have one, I can't be sure it's from the same batch or same vendor given how long ago I procured them? I'm also sure I have a USB to TTL serial cable somewhere if that provides alternate paths to recovery.
 
roydebets said:
Hi Guys,

I'm looking to fix my DS-2CD2132 since I seem to have bricked it this evening.

I got to the point where I used TFTP and restore the cam to working condition on a 5.2.5 firmware. Everything seems to work, until I reboot it.
Setting seem to be saved. Now it's still replying to ping on the IP address I gave it, but after about 40 replies, the ping gives about 8 timeouts and then starts responding again. (and it keeps doing that).

Webinterface is not working, Telnet/SSH is not working.

Can someone please tell me how to fix my cam?

Thanks!
Click to expand...

I have resolved the issue by flashing another downgrade firmware now.
After reboot it keeps working. So I'm fine with that.
 
  • Like
Reactions: alastairstevenson
I have 4 stubborn cams that got hard bricked during the process, on I can upload the brick fix tool, but when I try to mod the files the cam takes all the files yet will not show up on SADP it's a ds-2cd232f-is if anyone has this cam could they share with me the original MOD files that were extracted from this unit? I think durig the hex editor I messed the originals up and I don't have backups.

I tried creating a jtag to fix my remaining 4, will not update via tftp updater. I have connected them but not sure the next sets, I tried to putty through the serial connection but all i get is a blank putty window, it's only 3 wires I soldered has anyone here jtaged their cams?
 
You must log in or register to reply here.
Top Bottom