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

alastairstevenson said:
I believe so.
The EU portal is usually the most up to date - this is all the newest firmware for R0 cameras : DOWNLOAD PORTAL
That's assuming 5.4.5 is newer than 5.4.41
Unless anyone knows differently.
Click to expand...

Did you find out what the latest version was? I've been using 5.4.5 assuming it was the latest version, but the build dates are the wrong way around if so.

I thought the build dates worked as - YYMMDD? If so the 5.4.41 is newer
 

Attachments

  • dates.JPG
    dates.JPG
    12.3 KB · Views: 9
alexf40 said:
Did you find out what the latest version was? I've been using 5.4.5 assuming it was the latest version, but the build dates are the wrong way around if so.
Click to expand...
So have I, but I've not taken a look at the internals yet, I've been away.
I'll have a poke around tonight and see what I can find.
 
alastairstevenson said:
I'll have a poke around tonight and see what I can find.
Click to expand...
OK, I had a look at the 5.4.41 and the 5.4.5 version of firmware, specifically the davinci program which is the main app.

Here is IPC_2XX2_EN_STD_5.4.41_170312
Code: 
Working Copy Root Path: /usr/local/jenkins/workspace/Frontend_BaseLine_Publish_Build_InterfaceII/4029
URL: https://192.0.0.140/Camera/Platform/Branches/branches_frontend_software_platform/comm_bug_fix/cgi_fix/ipc_repair/ipc_5.4.0_R0
Repository Root: https://192.0.0.140/Camera
Repository UUID: df2d70c3-7593-7941-af1e-571b313c0946
Revision: 262807
Node Kind: directory
Schedule: normal
Last Changed Author: huangjiangsheng
Last Changed Rev: 262804
Last Changed Date: 2017-03-11 23:51:22 +0800 (Sat, 11 Mar 2017)

And here is IPC_R0_EN_STD_5.4.5_170123
Code: 
Working Copy Root Path: /usr/local/jenkins/workspace/Frontend_BaseLine_Publish_Build_InterfaceII/2539
URL: https://192.0.0.140/Camera/Platform/Branches/branches_frontend_software_platform/IPC_develop_branch/ipc_5.4.0_R0
Repository Root: https://192.0.0.140/Camera
Repository UUID: df2d70c3-7593-7941-af1e-571b313c0946
Revision: 253120
Node Kind: directory
Schedule: normal
Last Changed Author: liudan9
Last Changed Rev: 253065
Last Changed Date: 2017-01-23 17:45:28 +0800 (Mon, 23 Jan 2017)


Which does match the build dates as implied by the firmware filenames.
I also checked both versions to determine if they are vulnerable to the Hikvision backdoor - neither appear to be. Both require authentication when asked to provide a configuration file.
Interestingly, the Hikvision USA Tech Support site only has 5.4.5 as the most recent for R0 - Value Series
The Hikvision EU site has both - DOWNLOAD PORTAL
 
alastairstevenson said:
No, G0 is completely different internal architecture from R0.

The tftp server is not responding. You will need to use the 32-bit version.

I've converted several 2335/3335 CN cameras to English - but it's a but fiddly as they had hacked firmware with update capability disabled.
There are several posts on the topic, example : Long-shot help request - Hikvision DS-2CD3335D - G0 series IPC.
Click to expand...
thanks for your attention.

I have some questions:
1- How can i unpack new frimware? ( Hiktools not work with new frimwares)
2- How can edit boot and image files?
3- What should to do with Davinci program?
 
I have another pair of hacked Chinese cameras, a DS-2CD2142FWD-I and a DS-2CD2145F-IS, both running 5.3.6.
I'm not clear on how and when to do prtHardInfo to get the devType.
Do I just walk through the unbricking process, update to brickfixV2CN, then to 5.4.0, and run the command in Putty before running /dav/fixup.sh?
Are there points in the process where devType is unavailable or invalid?
 
These are both R6 series cameras, so the brickfixV2 method does not apply to them.
The 'hardware signature block' is held in a security protected separate chip in an attempt to prevent the camera parameters from being able to be changed.
 
alastairstevenson said:
These are both R6 series cameras, so the brickfixV2 method does not apply to them.
The 'hardware signature block' is held in a security protected separate chip in an attempt to prevent the camera parameters from being able to be changed.
Click to expand...
Alas. Naught to be done, then?
Ah, well. Many thanks for the help on the others.
 
alastairstevenson said:
The DS-2CD2032-I is an R0 series camera, so you are good to go with the brickfixV2 update method.
Click to expand...

Thanks for the information. I have one more question. Is it possible to enable SSH somehow on DS 2CD2032-I?
I have tried to do this using EN-HCNetSDK(Windows32)V5.3.2.15_build20171122 but without a success. The clientDemo app is able to read some parameters but cannot write any.
 
regarding brickfixV2 update. There is "fix up mtdblock1" step but there is no explanation what exactly and how should be fixed. Could you please provide more info regarding this?
 
You must log in or register to reply here.
Top Bottom