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

Yes - that's because the Region is still set to China.
To change that, you could change byte 0x55 from 0x01 to 0x03 in mtd6 to change the Region to World.

Just to confirm. Changing byte 0x55 from 1 to 3 and rewriting back to the camera has indeed now given me a serial number of "DS-2CD2332-I20150415CCWR5...." rather than CCCH and the US English 5.4.5 firmware is happy on it.

Thanks
 
Hi guys, thanks for putting this up. Awesome work by Alastair. I have succesfully converted chinese 2332 camera to 5.4.5 firmware using this guide and now i got two chinese 2432 camera to convert. But i am stuck with first step of updating it to brickfixv2 firmware. I have tried both CH and EN version, both does nothing after hikvision tfth server initialised. I have waited well over 10 min for both but still no luck. What am I missing. Brickfixv2 firmwares different between 2432 and 2332 or wireless nature of 2432 playing mess here. The camera was previously connected using wi-fi, but when does updating i used ethernet connection with poe injector.

Thanks guys
 
The Hikvision tftp updater is unreliable when the camera is powered over PoE. Best to use a 12v power supply.
It can also be troublesome when directly connected to the PC. It works best when both camera and PC are wired to a switch or router.
 
For reference - my old Chinese DS-2CD3332-I which arrived with hacked english on it was also happy with the devtype

0898 - DS-2CD2332-I

Mark
 
Hello
first of all a big thank you to
alastairstevenson for the time he spends helping on this forum.

I try to unlock an intercom from hik DS-KV8102A from the Chinese market.
until the last firmware I arrived with hiktools05R1 to load the new DIGICAP.DAV.
since the last, it hangs, without briquing, with the message: language incompatible with the client.

so I will try the method "Brick-fix tool V2"
however, I stall on: "Ideally the true value is determined from the 'devType' line from the prtHardInfo shell command,"

question: how do we activate this command "prtHardInfo shell". Do you need a tool other than those described in the procedure?

thank you for responding to my request. I can attach the DIGICAP.DAV files from the device, but we can easily find them on the FTP hik europe.
 

Attachments

  • 1587931956992.png
    1587931956992.png
    312 bytes · Views: 8
I try to unlock an intercom from hik DS-KV8102A from the Chinese market.
so I will try the method "Brick-fix tool V2"
No - the brickfixV2 method is for R0 series cameras only - it is not for doorbells or door stations or for any other series.

I can attach the DIGICAP.DAV files from the device, but we can easily find them on the FTP hik europe.
These are EN/ML files that will not work on a Chinese door station device. As you have discovered.
 
No - the brickfixV2 method is for R0 series cameras only - it is not for doorbells or door stations or for any other series.


These are EN/ML files that will not work on a Chinese door station device. As you have discovered.


thank you for these clarifications.

however I successfully use the an / ml versions with the "hiktools05R1.exe" tool
Who is it for R0 cameras?
 
I just want to try this method and for that I do not have the answer to the question I ask on the forum.
imagine that it works, i would be happy to share it with you.
 
question: how do we activate this command "prtHardInfo shell".
If the camera supports it - you need to be able to get to a command shell to issue the command.
Some of the newer firmware allows ssh access :
Code:
alastair@PC-I5 ~ $ ssh admin@192.168.1.102
admin@192.168.1.102's password:
BusyBox v2.0.0-548754 Protect Shell (psh)
Enter 'help' for a list of davinci system commands.

# prtHardInfo
Start at 2020-03-09 13:41:18
Serial NO :IPC-T2347G-LU20191006AAWRD68543108
V5.6.4 build 191224
NetProcess Version: 8.11.3 [09:37:40-Oct 31 2019]
Path: /Camera/Platform/Branches/branches_FSP_network_protocol/shizhi/FSP_network_protocol_chanpin_G1_V5.6.4
Last Changed Rev: 635684
Last Changed Date: 2019-10-30 15:51:14 +0800 (Wed, 30 Oct 2019)

Sec Version: 1.0.1 [16:47:42-Mar 20 2019]
Path: /Camera/Platform/Trunk/FSP_network_security
Last Changed Rev: 460994
Last Changed Date: 2018-11-09 14:26:28 +0800 (Fri, 09 Nov 2018)

Db Encrypt Version: 131072
hardwareVersion    = 0x0
hardWareExtVersion    = 0x0
encodeChans        = 1
decodeChans        = 1
alarmInNums        = 0
alarmOutNums        = 0
ataCtrlNums        = 0
flashChipNums        = 0
rms                = 0x200
networksNums        = 1
language            = 1
devType            = 0x26006
net reboot count    = 0
vi_type            = 62
hardwareType        = 1
firmwareCode        = 0000000200000100000000010c91bc6f000000010000000100000002ffffffff0506000400130c1800026006
Path: /Camera/Platform/Branches/branches_frontend_software_platform/IPC_develop_branch/ipc_baseline/baseline_V5.6.0_IPC
Last Changed Rev: 671597
Last Changed Date: 2019-12-23 16:58:14 +0800 (Mon, 23 Dec 2019)


#
 
  • Like
Reactions: iTuneDVR
thank you
I saw on a forum that one could use this command while passing by "PUTTY"

do you confirm ?

I will try the manipulation tomorrow and will keep you posted
 
I want to ask the only question, why follow this long quest, if the old IP camera with the Chinese version of the firmware is in working condition, then it will be more convenient to make a service firmware that will make the necessary changes yourself.
 
First off - thank you Asastair for the whole brickfix! Its pretty amazing what you were able to do! I have used it on 7 cameras sucessfully, but on one, it got stuck just like Bidon (TFTP stuck on test) on a 2CD2432F-IW that came with a hacked english 5.1.2. ran the I read through all the info on the last set of pages - but I don't currently have serial access. I have tried TFTP probably 50 times under different circumstances - 12v power on a switch, direct to computer, PoE... nothing.

Here is the wireshark capture in case anyone can make sense of that.

So, my question - is it worth trying to get a serial adapter up? I don't have the linux skills of Bidon, but can follow directions fairly well!

is there any other way to unbrick?

5.4.5 upgrade works now!!!
Time to sleep!...
 

Attachments

I have used it on 7 cameras sucessfully
Very good!

Here is the wireshark capture in case anyone can make sense of that.
There is a single valid instance of the probe / response handshake in packets 533/534 - 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.

is there any other way to unbrick?
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.
 
Hello
I come back to you to declaw.
reminder: door phone DS KV 8102A.
brickfixV2EN loading without result;
brickfixV2CH loading: "Completed file [D: \ tftpserv \ tftpserv \ digicap.dav] transmit"
as when I load a firmware;
I never have the indication: "System update complete"
Unable to communicate with PuTTY.
at this point, on SADP the intercom address is 192.0.0.65 and not 64 with a gateway at 192.0.0.1

here is
I can no longer upgrade my device

thanks again for these great tips
are you doing well
bye
 
brickfixV2CH loading: "Completed file [D: \ tftpserv \ tftpserv \ digicap.dav] transmit"
as when I load a firmware;
I never have the indication: "System update complete"
The firmware is being downloaded then rejected as being invalid for the device.
No - the brickfixV2 method is for R0 series cameras only - it is not for doorbells or door stations or for any other series.