I run dd-wrt and its disabled by default.
Think I have everything I need,.. will start this shortly.
Last edited:
R0 / DS-2CD2x32 BrickfixV2 brick recovery and full upgrade tool - enhanced.
- Thread starter alastairstevenson
- Start date
Think I have everything I need,.. will start this shortly.
alastairstevenson
Staff member
You'll be fine.
Odd though about it not coming back after a web GUI restart.
By the way - it's normal that the 5.3.0 to 5.2.5 downgrader comes up in Chinese.
It's just a recovery firmware for those CN cameras which no longer respond to the web GUI due to a 'firmware language mismatch' after using EN/ML firmware.
It provides a start point for the classic 'mtd hack' that part converts to EN.
Odd though about it not coming back after a web GUI restart.
By the way - it's normal that the 5.3.0 to 5.2.5 downgrader comes up in Chinese.
It's just a recovery firmware for those CN cameras which no longer respond to the web GUI due to a 'firmware language mismatch' after using EN/ML firmware.
It provides a start point for the classic 'mtd hack' that part converts to EN.
Tried this and its failed on Stage 3 of 3 of the Enhanced MTD hack.
The fixup_log.txt file shows:
Tailend of what I was seeing in the telnet session:
EDIT: apologies, dunno what happened with the image attachments; accidentally did it 3 times and somehow its blank anyhow 
The cam is showing as:
device type = DS-2CD-Min-System
software version = V4.0.8build 130906
The fixup_log.txt file shows:
Code:
[Brick-fix tool] Initialising fixup_log.txt
Payload dropped, rollback re-enabled
Initialising fixup current status to stage1
[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
Extracting the original mtdblocks ...
Extracted the original mtdblock6 as mtd6ro_orig
Extracted the original mtdblock1 as mtd1ro_orig
Transferring out mtd6ro_orig via tftp ...
Successfully transferred out mtd6ro_orig via tftp
Transferring out mtd1ro_orig via tftp ...
Successfully transferred out mtd1ro_orig via tftp
Fixup Stage1 is completed - Extracted the original mtdblocks
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
Successfully transferred in mtd6ro_mod via tftp
Written mtd6ro_mod to mtdblock6 ...
Initialising fixup next status to stage3 ...
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
Successfully transferred in digicap.dav via tftp
Attempting a firmware update ...
*** error doing the firmware update. ****
End of script - ready for the next run.
.
Code:
Successfully transferred in digicap.dav via tftp
.
Attempting a firmware update ...
.
*** error doing the firmware update. ****
.
.
Each stage of the process is carried out by a run of the /dav/fixup.sh script .. .
The next stage is :
-rw-r--r-- 1 58 Mar 17 20:50 /dav/fixup_stage3.txt
.
.
[ INFO][MIN]TFTP:
*** An error has occurred. Check the on-screen messages and the contents of the logfile ***
*** fixup_log.txt that was transferred to your PC and after correcting the cause of the ***
*** error re-run the script /dav/fixup.sh to resume. ***The cam is showing as:
device type = DS-2CD-Min-System
software version = V4.0.8build 130906
Last edited:
alastairstevenson
Staff member
Maybe the mtd6ro_mod isn't right - do you want to zip it up and attach here and I'll check it for you?
**edit** and maybe also the mtd6ro_orig
**edit** and maybe also the mtd6ro_orig
alastairstevenson
Staff member
The mtd6ro_mod file is OK -
The language change to 01 from 02 is correct, the devtype code 0898 is correct, and the changed checksum-16 is correct.
That eliminates the mtd6 mods as being the cause of the firmware rejection.
My suggestion is to re-try the firmware update using a lower version of firmware, such as the 5.3.0 from the forum downloads area.
When you re-run /dav/fixup.sh it will automatically restart at Stage3 for the firmware update - no need to re-do the earlier stages.
If/when that works OK, then you will be able to use the web GUI to progress up the version of firmware to the most recent.
Although in most cases a straight jump to 5.4.5 has worked OK, there have been some instances where it has not, for unknown reasons.
Couldn't find a 5.3.0,... would 5.2.0 be ok? from here DS-2CD2332-I
EDIT:
Tried it anyhow,... looks like same failure.
Tail end of /dav/fixup.sh
And the log file:
EDIT:
Tried it anyhow,... looks like same failure.
Tail end of /dav/fixup.sh
Code:
[ INFO][MIN]TFTP: ################################################################################
[ INFO][MIN]TFTP: ################################################################################
[ INFO][MIN]TFTP: ################################################################################
[ INFO][MIN]TFTP: #################################################
Successfully transferred in digicap.dav via tftp
.
Attempting a firmware update ...
.
*** error doing the firmware update. ****
.
.
Each stage of the process is carried out by a run of the /dav/fixup.sh script ...
The next stage is :
-rw-r--r-- 1 58 Mar 17 20:50 /dav/fixup_stage3.txt
.
.
[ INFO][MIN]TFTP:
*** An error has occurred. Check the on-screen messages and the contents of the logfile ***
*** fixup_log.txt that was transferred to your PC and after correcting the cause of the ***
*** error re-run the script /dav/fixup.sh to resume. ***
Code:
[Brick-fix tool] Initialising fixup_log.txt
Payload dropped, rollback re-enabled
Initialising fixup current status to stage1
[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
Extracting the original mtdblocks ...
Extracted the original mtdblock6 as mtd6ro_orig
Extracted the original mtdblock1 as mtd1ro_orig
Transferring out mtd6ro_orig via tftp ...
Successfully transferred out mtd6ro_orig via tftp
Transferring out mtd1ro_orig via tftp ...
Successfully transferred out mtd1ro_orig via tftp
Fixup Stage1 is completed - Extracted the original mtdblocks
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
Successfully transferred in mtd6ro_mod via tftp
Written mtd6ro_mod to mtdblock6 ...
Initialising fixup next status to stage3 ...
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
Successfully transferred in digicap.dav via tftp
Attempting a firmware update ...
*** error doing the firmware update. ****
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
Successfully transferred in digicap.dav via tftp
Attempting a firmware update ...
*** error doing the firmware update. ****
End of script - ready for the next run.
.
Last edited:
alastairstevenson
Staff member
The download section of the forum has a full set of firmware versions.
The 5.3.0 should be a safe starting point.
Don't use the brickfixv2 for the update now - it's a recovery environment, not a full firmware.
What should work is to download and unzip the 5.3.0 from the forum R0 downloads, telnet in as you have been doing, and instead of using /dav/fixup.sh use the update command.
The 5.3.0 should be a safe starting point.
Don't use the brickfixv2 for the update now - it's a recovery environment, not a full firmware.
What should work is to download and unzip the 5.3.0 from the forum R0 downloads, telnet in as you have been doing, and instead of using /dav/fixup.sh use the update command.
Ah found the rest of the downloads,... wasn't aware of the updates bit that exposed all the previous versions.
What's the update command? (Just going back through the thread)
EDIT:
Am only seeing the following .sh scripts
What's the update command? (Just going back through the thread)
EDIT:
Am only seeing the following .sh scripts
Code:
--w---x--T 1 6426 Mar 17 20:23 /dav/initrun.sh
--w---x--T 1 598 Mar 17 20:23 /dav/guard.sh
--w---x--T 1 8269 Mar 17 20:23 /dav/fixup.sh
Last edited:
alastairstevenson
Staff member
Try the command
upgrade
Or
update
I don't recall which one works at that level.
Or you could just use
/dav/fixup.sh
again.
upgrade
Or
update
I don't recall which one works at that level.
Or you could just use
/dav/fixup.sh
again.
These both failed,.... BUT /dav/fixup.sh worked!
Can I now just update via the 'config > maintenance > remote upgrade' area ?
Does it need to go staged, or can I go straight to '5.4.41_1703' ?
Its currently showing as 'V5.3.0 build 150814'.
alastairstevenson
Staff member
I think your camera has a random element built in. A bit odd. Like the not restarting properly.
On the updates - go through the major versions is recommended.
On the updates - go through the major versions is recommended.
Cool will do when I get home tonight,... via the web interface 'config > maintenance > remote upgrade' area ?
This cam does reek of some issue as after a powercycle/reboot it still doesn't come up unless I leave it off for a while. Quite weird.
Hopefully newer firmware may change this, otherwise it may go to the bin or put in a place that's easily accessible and not to be relied on.
This cam does reek of some issue as after a powercycle/reboot it still doesn't come up unless I leave it off for a while. Quite weird.
Hopefully newer firmware may change this, otherwise it may go to the bin or put in a place that's easily accessible and not to be relied on.
alastairstevenson
Staff member
Yes, that's correct.
Usually 5.3.0 -> 5.4.0 -> 5.4.41
alastairstevenson
Staff member
It does look like there is some sort of erratic problem with this camera.
If it starts the update, it's validated the file already, and the update should simply complete.
During the update, it's just writing the files to the flash memory, one by one.
If it starts the update, it's validated the file already, and the update should simply complete.
During the update, it's just writing the files to the flash memory, one by one.
Camera Model: DS-2CD2032F-I
Date on the Camera: 2015-10
Hi there, I tried the step by step guide after my camera stopped working after updating the firmware with the one from the Hikvision website.
However, I made some mistakes. I accidentally flashed the wrong digicap.dav using the tftpserv application, it showed that the firmware was successfully installed. Then I proceeded from the beginning of the guide and installed the brickfixv2EN.dav file by renaming it etc. This went all fine (it was send over to the camera and showed installed), however after power cycling the camera I was not able to telnet into it. So I proceeded to try to install the brickfixv2CN.dav version, however this time the camera will show up in the tftpserv under 192.0.0.64 but after that nothing happens. I cannot ping the camera, I cannot telnet in either, and it won't install any firmware anymore using tftpserv.
Is there anything I can do at this point?
Date on the Camera: 2015-10
Hi there, I tried the step by step guide after my camera stopped working after updating the firmware with the one from the Hikvision website.
However, I made some mistakes. I accidentally flashed the wrong digicap.dav using the tftpserv application, it showed that the firmware was successfully installed. Then I proceeded from the beginning of the guide and installed the brickfixv2EN.dav file by renaming it etc. This went all fine (it was send over to the camera and showed installed), however after power cycling the camera I was not able to telnet into it. So I proceeded to try to install the brickfixv2CN.dav version, however this time the camera will show up in the tftpserv under 192.0.0.64 but after that nothing happens. I cannot ping the camera, I cannot telnet in either, and it won't install any firmware anymore using tftpserv.
Is there anything I can do at this point?