R0 / DS-2CD2x32 BrickfixV2 brick recovery and full upgrade tool - enhanced.
- Thread starter alastairstevenson
- Start date
Hello, any instruction to change CN to EN for DS-2CD3366WDA4-L, V5.7.5 build 241103.
Many thanks
Many thanks
Last edited:
I just followed these steps to update a bricked DS-2CD2432F-IW to V5.4.5build 170401!
So is there a way I can update my other cameras that are still running V5.2.5build 141201 and not have them be bricked in the process so that I can avoid the brickfixv2 brick recovery process?
So is there a way I can update my other cameras that are still running V5.2.5build 141201 and not have them be bricked in the process so that I can avoid the brickfixv2 brick recovery process?
Well done!
If they are not China region cameras with hacked firmware - then the normal upgrades should work OK.
A clue may be in the serial numbers - CCCH usually indicates Chinese.
So I just checked, and they have CCCH in the serial number. So I need to do this entire process for all of them? Or since are there some short cuts that I can take since they are all the same model number?
Perhaps I can use the same mtd6ro_mod file for all of them?
Since the others are not bricked maybe the steps to do this are not exactly the same as a bricked camera? maybe there is a faster way to update all of them?
@EMPIRETECANDY Maybe I should just replace them. What would be the recommended replacement for the DS-2CD2432F-IW cameras? They provide enough resolution and features for my needs. The only issue I have with them is that some of them the IR no longer works... Other than that they work fine.
Last edited:
Hello, I have Ds-7616-e2/8p with V3.4.106 build 191009. I have ds-2cd2032i camera. I have downloaded the 5.30 from EU site and probable brick it. I have updated with brickfixV2CN . the problem is i can't access with telnet with 192.0.0.64. Did they disable with telnet with latest firmware?
Is the camera still connected to the NVR PoE port? And the PC on the LAN?
If so, the camera isn't directly accessible.
If the camera is still connected to the NVR, either connect the PC to an unused NVR PoE port, or connect the camera to the same LAN as the PC and power the camera with 12v.
And give the PC an IP address in the same range as the camera - which looks like 192.168.254.2
Is the camera still connected to the NVR PoE port? yes And the PC on the LAN? pc on NVR Poe port Yes
If so, the camera isn't directly accessible. not, only after flashed brickcn/en you can see the mini-system on sadp tool.
If the camera is still connected to the NVR, either connect the PC to an unused NVR PoE port (this is the method I'm being using), or connect the camera to the same LAN as the PC and power the camera with 12v.
And give the PC an IP address in the same range as the camera - which looks like 192.168.254.2
TFTP all came out complete and successful.
If so, the camera isn't directly accessible. not, only after flashed brickcn/en you can see the mini-system on sadp tool.
If the camera is still connected to the NVR, either connect the PC to an unused NVR PoE port (this is the method I'm being using), or connect the camera to the same LAN as the PC and power the camera with 12v.
And give the PC an IP address in the same range as the camera - which looks like 192.168.254.2
TFTP all came out complete and successful.
Min-System mode should allow telnet access, so the fixup script can be activated.
But it would normally use the 192.0.0.64 IP address, not the 192.168.254.2 address that your SADP list is showing.
I'm not sure why that is.
If you change the PC IP address to, say, 192.168.254.100 does a telnet access connect?
I finally got into telnet connection, I have to switch the pc into different poe port. Now the hex checksum the number is different from the video. Once I get home I will unload the screenshot here thx can you confirm the hex number is right that i replace it? thanks
The left hand byte (0x0C in the screenshot) is the most significant byte and should be used in location 0x05
The right hand byte (0x5F in the screenshot) is the least significant byte and should be used in location 0x04 DO i need to replace with 0C? also checksum needs to replace too?
The left hand byte (0x0C in the screenshot) is the most significant byte and should be used in location 0x05
The right hand byte (0x5F in the screenshot) is the least significant byte and should be used in location 0x04 DO i need to replace with 0C? also checksum needs to replace too?
Last edited:
Good news, I replaced checksum numbers too. now the firmware is 5.45 and is bought back from death. Thanks @alastairstevenson