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

after bootm, nothing happens and I can't ping camera
bootm won't do anything unless a kernel has been loaded into memory.
The upk command is used to write the flash with a kernel image.
It's the tftp hImage command that (if it's available) will load a kernel into memory.
The partitions mentioned in your upk transcript above hold the kernel:
mtd9: 00800000 00020000 "krn_pri"
mtd10: 00800000 00020000 "krn_sec"

By the way - be very cautious about trying random update commands - it's easily possible to erase the entire flash.
 
bootm won't do anything unless a kernel has been loaded into memory.
The upk command is used to write the flash with a kernel image.
It's the tftp hImage command that (if it's available) will load a kernel into memory.
The partitions mentioned in your upk transcript above hold the kernel:
mtd9: 00800000 00020000 "krn_pri"
mtd10: 00800000 00020000 "krn_sec"

By the way - be very cautious about trying random update commands - it's easily possible to erase the entire flash.
Ok !
I don't have tftp command in console mode. Just tftpboot command downloading digicap.dav when using it.
 
I don't have tftp command in console mode. Just tftpboot command downloading digicap.dav when using it.
OK - so I swapped out one of my live DS-2CD3332-I Hikvisions for a Dahua HDW4431C-A-V2 that I'd bought as spares&repairs on eBay and fixed up.
I'd been planning on swapping it out anyway - once I'd received and changed the 2.8mm lens for a 6mm one, which I did today.
So I've now got a Hikvision camera to test out some recovery scenarios on.

As you do seem quite adventurous - maybe you'd like to try this:
Unzip the mImage file attached and drop it in the same folder as the tftp updater (or tftp server if you are using that).
With the PC IP address set to 192.0.0.128, power on the camera and interrupt the bootloader with Control-U
Press Return a couple of times and use the command
upm

Hopefully it will download and write a new copy of the 'min-system' recovery partition.
Then if you are running the Hikvision tftp updater, shut it down.
Use the command
reset
and with some luck it should boot into the 'min-system' mode, from where the /dav/fixup.sh script can be run.

Good luck! I have my fingers crossed.
 

Attachments

A big thank you for sharing your knowledge.
I will be able to continue using my Hikvision DS2CD2432F IW.
I followed your instructions and updated firmware 5.2.5 to 5.4.5.
I did not know when I bought it that there was a difference between Hikvision CH and EN, but now the problem is solved.
Thanks again !!!!
(Translated by Google
 
  • Like
Reactions: alastairstevenson
I'll try tonight. If it doesn't work I'll buy a new cam ^^
I have another 2132, the bricked one will be usefull for pieces...

I don't asked but perhaps can I get something from my working camera ? How can I do that ?
 
I'm fairly hopeful that will work.
It works !!! You're the best !
Thank you very much :). :highfive::highfive::highfive:
I now have a fully operationnal 5.4.5 camera !!

I think I bricked my camera because of using brickfixEN instead of brickfixCN.

Will I try my other camera :lol: => done in less than 10 minutes, I choose the right brickfix this time :).
 
Last edited:
  • Like
Reactions: alastairstevenson
Excellent! I'm glad that worked.

But I'm sure the problem was not due to the other brickfixV2, it's only got a different language in the header.
Somehow in the install, the data written to the flash partition was corrupted.
 
Hi,
I make a mistake :(
i run /dav/fixup.sh my firewall block the file so re run fixup.sh and it go on stage 2 with error filenot found.... i go on dav folder and i remove 2 files possible to put back and how restart the process from stage1

thanks for your help

Code:
Checking that tftp works OK ...
[stage start] fixup_log.txt successfully transferrred to the PC via tftp
End of script - ready for the next run.
.
Checking that tftp works OK ...
[stage start] fixup_log.txt successfully transferrred to the PC via tftp
End of script - ready for the next run.
.
[Brick-fix tool] Initiating reboot into min-system
[Brick-fix tool] Initiating reboot into min-system
Checking that tftp works OK ...
[stage start] fixup_log.txt successfully transferrred to the PC via tftp
End of script - ready for the next run.
.
 

Attachments

  • Sans titre.png
    Sans titre.png
    28.9 KB · Views: 10
how restart the process from stage1
To start again from stage 1 needs the existence of a file called /dav/fixup_stage1.txt
The content does not matter.
So you can create it like this :

Code:
echo "Fixup stage1 completed - rollback payload dropped" > /dav/fixup_stage1.txt

Good luck!

*edit* But I'm assuming that you deleted the /dav/fixup_stage2.txt file.
Check what' may be still there with
ls -al /dav/fix*
Delete any still existing with
rm /dav/fixup_stage2.txt
or
rm /dav/fixup_stage3.txt

Then create the /dav/fixup_stage1.txt with the echo command above.
 
Last edited:
Hello,

I have followed all the steps successfully up to stage 1. But now, I don't know how to update mtd6ro_mod, I don't have devType for my cam (DS-2CD2032F-IW)

I don't know how to use 'prtHardInfo' command. I’ve tried with telnet, but it doesn't seem to work ("prtHardinfo: not found")

Any help would be much appreciated.
 
I don't have devType for my cam (DS-2CD2032F-IW)
What values are showing in the hex locations 64 and 65 of mtd6_orig ?
If not FF98 then you are OK and can proceed with the language byte change and checksum change.

If FF98 then you will need to know the correct devtype.
I don't have an example of the prtHardInfo from that model - maybe another forum member can advise.

Alternatively - you could use the Hikvision tftp updater to install the '5.3.0 to 5.2.5 downgrader' from the second dropbox link here : Custom Firmware Downgrader 5.3.0 Chinese to 5.2.5 English
Then, assuming the web GUI works OK, enable telnet, start a telnet session and use the 'prtHardInfo' command to see the devtype value.
 
  • Like
Reactions: DreamLand
Thanx to topicstarter!
flashed my cameras with 5.4.5, but one of 2132 flashed with mtd06 block from the neighbour
can anybody attach mtd06 from DS-2CD2132-I (or analogue)?
 
Thanks a lot alastair !

Downgrade has been done. GUI works OK, I was able to login with "admin"
I've had a hard time to find 'telnet enable' in chinese configuration menu. I've attached an image if someone else is looking for it

So here is the code for DS-2CD2032F-IW
devType = 38950

Now , i will try to finalise update to 5.4.5 firmware with english language ......
 

Attachments

  • ScreenShot020.png
    ScreenShot020.png
    22.9 KB · Views: 21
Last edited:
flashed my cameras with 5.4.5, but one of 2132 flashed with mtd06 block from the neighbour
What!! You didn't make a copy and store it somewhere safe?

can anybody attach mtd06 from DS-2CD2132-I
Attached is a worked example for a DS-2CD2132-I
Note - you will need to start the brickfix process again - writing mtdblock6 on firmware versions 5.3.0 or higher will trigger a nasty trap.
 

Attachments

  • Like
Reactions: m2a
What!! You didn't make a copy and store it somewhere safe?
Attached is a worked example for a DS-2CD2132-I
Note - you will need to start the brickfix process again - writing mtdblock6 on firmware versions 5.3.0 or higher will trigger a nasty trap.
thank you very much!!!
about backup - hurried to flash latest cam... :)
 
Thanks for the procedure, after disabling all firewalls I was able to modify/flash two Cube camera's (2CD-2432's).

Is there a similar procedure available for a R1 camera (pinhole - 2CD6412)?
 
Last edited: