And I should have mentioned - you can't really skip sections of the method as it's either not available to be able to do the 'mtd hack' or there is a deliberate and quite nasty trap, depending on the specific version of firmware when trying it.
The cameras don't have to be bricked in order to use the brickfixV2 method to change the language.
Strictly - the 5.4.41 version is slightly later than the 5.4.5 version, but wasn't obviously so due to the way Hikvision number the firmware. Either would work ok.
Thanks, ended up processing the 2 cams I had (DS-2CD2132-I) and it went without any issues, both cameras are up and running using the Hikvision protocol and I have the full functionality now, and in english, thanks!
I noticed there is a firmware update showing as being available on the NVR for my 4 Hikvision cameras, should I use the NVR to update them? I think I read somewhere best not to use the NVR but to use the manual web interface for updating firmware on the Hikvision cameras?!?
I was also under the impression that I was already on the latest firmware available too, the NVR doesn’t say what version is available....It's also not showing in the web interface, only on the device.
DS-2CD2185FWD-IS - V5.6.5 build 200316 x 2
DS-2CD2132-I - V5.4.5 build 170401 x 2
Hi all, came across the thread after trying to find out why my DS -2CD2332 cameras wouldnt show up with my HKVision NVR.
I have tried to go through the process with the camera powered through the POE switch, but doesnt seem to progress. I suspect it is due to the power.
Trying to find out what external power to use. I have a 12V adapter that outputs 2A. Is that going to be fine, or do I need something with less output?
thanks in advance
Thanks to Alastair for the tutorial/step by step video. Helped me update 6 of my 7 DC-2CD2332-I cameras.
I was able to add them to my NVR, and get them working for the 1st time in over a year....
For some reason, my 7th camera decided to add itself to the NVR, without updating it - tho I cant get it off the wall if I tried...
Thanks again mate, would buy you a beer if you lived down under!!
Hello !
I am trying to reset the password on my DS-2CD2432WD-I camera. The Password reset code method does not work for me.
Would I be able to use this method to reset the camera to defaults ?
I don't recall if that model has an internal reset button - but you've probably already checked for that.
There are a couple of things you could do:
Using SADP, check the firmware version to find if it has the 'Hikvision backdoor' vulnerability that allows the password to be extracted.
If the firmware is 5.4.0 or earlier, try this URL to pull a copy of the configuration file.
http://<camera_IP_address>/System/configurationFile?auth=YWRtaW46MTE
If that works - zip it up and attach here, and it can be decrypted and decoded to expose the password.
You can also use the tftp updater to apply the same version of firmware as is already installed.
That will reset the camera to default settings.
I havent checked for an internal reset button. The camera does not have a microsd slot,, so no reset buttons there.
Would an internal reset button be inside the main housing ? How should I go looking for it ?
Using SADP, check the firmware version to find if it has the 'Hikvision backdoor' vulnerability that allows the password to be extracted.
If the firmware is 5.4.0 or earlier, try this URL to pull a copy of the configuration file.
http://<camera_IP_address>/System/configurationFile?auth=YWRtaW46MTE
If that works - zip it up and attach here, and it can be decrypted and decoded to expose the password.
I tried the tftp method. Unfortunately, the camera never gets the IP address of 192.0.0.64
I see the camera using the SADP tool, but with an IP address of 192.168.1.222. I am also unable to ping that address, even when my computer is in the same subnet. Could it be that the camera is in some kind of boot loop ? How would I check ?
That's only used for a few seconds during startup when the camera probes for the tftp updater.
What does the tftp updater window show when you power on the camera?
Did you get a Windows firewall popup on first start of the tftp updater?
The tftp updater works best when both camera and PC are wired to the switch - no WiFi and not directly connected together, and powered by 12v.
That's only used for a few seconds during startup when the camera probes for the tftp updater.
What does the tftp updater window show when you power on the camera?
Did you get a Windows firewall popup on first start of the tftp updater?
The tftp updater works best when both camera and PC are wired to the switch - no WiFi and not directly connected together, and powered by 12v.
The original 'brick-fix tool' and 'enhanced mtd hack' has proven pretty useful for those with R0 cameras that had been bricked by doing a firmware update.
It's been even more useful to deal with the fallout from the 'Hikvision backdoor' disclosure where so many people are finding their cameras are being messed with from the internet, mischievously or maliciously, and need to update to safer firmware.
However - the rather techy original method to make the changes, and probably my not-very-clear instructions have been a challenge for some people.
* And I only just noticed this - my original .txt attachments were in Linux format, not Windows format, making them hard to read without proper line breaks. And no-one let me know! Dohh! *
So here is 'Brick-fix tool V2' aimed at making the process less complex, a bit automated and easier to use, with the following changes:
After Brick-fix toolV2 has been installed using the Hikvision tftp updater, following the power cycle to activate and drop the payload, the camera will boot directly into 'min-system' mode with telnet and tftp access and a 'fixup' script ready and primed for use.
No web GUI access or Windows shares are needed to move files in and out of the camera.
The fixup script handles all the basics of extracting the original mtdblock6, importing and applying the user-modified mtdblock6 that has had the 'enhanced mtd hack', and initiating a firmware update.
The Brick-fix toolV2 automatically writes a valid template into mtdblock1 that stops cameras that originally had firmware 5.2.0 or 5.2.8 from otherwise going into a bricked state when newer firmware is applied.
Attached to this post are the resources required to convert your R0 / DS-2CD2x32 cameras into full English upgradeable devices.
The brick-fix tool V2 in both EN and CN header language versions (brick_fixv2.zip).
A required resource list and step-by-step guide to the fixup script.
A description of how to do the 'enhanced mtd hack' with screenshot with a list of devType codes for those cameras that have the masqueraded values.
A sample transcript of the fixup script going through all 3 stages - extract mtdblocks, import modded mtdblock6, apply firmware update.
edit 15Dec17 By popular request, a video worked example using a DS-2CD3332-I camera donated by a generous forum member. edit 28Jan18 devType codes updated - thanks @hikcamuser
Resource List
The Hikvision tftp updater tool and usage instructions, courtesy of @whoslooking - tftpserv
A standard tftp server - tftpd32.452.zip at bottom of this thread.
A telnet client. PuTTY is pretty good and widely used - Download: 64-Bit | 32-Bit
Hikvision's really useful SADP tool. This will find your Hikvision device on the LAN whatever it's IP address, allow 'activation', and change of IP address. - SADP Tool
Step By Step Guide:
Here are the steps to take when using the brick-fixV2 tool to recover a bricked camera, and running the fixup script to change the camera to English / upgradeable. The camera doesn't have to be bricked to run the brick-fix tool if all that's required is a helping hand doing the 'enhanced mtd hack'.
Create a folder on the local drive of your Windows PC to hold the Hikvision tftp updater, the chosen tftp server program (e.g. jouinin.net version), the unzipped 'brick-fixV2' files, and the Hikvision firmware to use for updating. The HxD hex editor should be installed on the PC.
With the PC and the camera each on a wired connection (not WiFi) set the PC IP address to 192.0.0.128, subnet mask to 255.255.255.0 The default gateway does not matter.
Make a copy of brickfixV2EN and name it as digicap.dav If the EN version does not work, e.g. "System update completed" is not displayed in step 5 or you don't get the login prompt when trying to telnet in step 8, try the CN version.
Start the Hikvision tftp updater tftpserve.exe and if a Windows firewall popup appears, click OK to accept what the program needs.
Power on the camera and observe the status messages in the tftp updater. Hopefully you will see 'System update completed' after 2 or 3 minutes.
Close the Hikvision tftp updater, delete the digicap.dev file from step 3 and make a copy of the Hikvision firmware to use for updating and name it digicap.dav.
Power down the camera. At this point the brickfixV2 tool has been installed but not yet activated. Power on the camera to activate the tool, it will then drop the payload, fix up mtdblock1 and reboot into min-system mode for telnet access.
Using PuTTY, start a telnet session to 192.0.0.64 and make sure the telnet radio button is selected. At the login prompt username=root password=12345. You should see a # prompt. The message "can't chdir to home directory '/root/'" isn't an error and can be ignored.
Start the normal tftp server (not the Hikvision tftp updater). If it's the jouinin.net version, the program is tftpd32.exe
At this point, Stage 1 of 3 is ready to be executed.
At the telnet command prompt, type:
/dav/fixup.sh
and watch the on-screen messages.
On success with Stage 1, check the PC folder that the tftp server is running in for the presence of the file 'mtd6ro_orig'. You may have to hit F5 to refresh. Make a copy of mtd6ro_orig rename to mtd6ro_mod. Do the 'enhanced mtd hack' on it, using the instructions in the spoiler below.
These are the steps that are used to do the 'enhanced mtd hack' to mtdblock6 in an R0 IP camera.
Extract a copy of mtdblock6 from the camera. The 'Brick-fixV2 tool / fixup script' will conveniently do this for you, or it could be done manually by other methods.
Make a copy of the mtdblock6 file and name it mtd6ro_mod
Check / change as needed the language byte at location 0x10 to ensure it is 01
Check the devType value in locations 0x64 and 0x65
[*]
If the value shown is FF98 - then the FF value needs to be replaced with the true numeric value. Ideally the true value is determined from the 'devType' line from the prtHardInfo shell command, but as that is going to be unavailable on a bricked camera use this (partial) cross-reference list, paying careful attention to the exact model number.
There is some slight uncertainty here - it would be good if any forum members could confirm / supplement the content.
Replace the FF in location 0x64 with the first 2 digits of the numeric devType value.
If location 0x64 already has a 2-digit numeric value, no change is needed.
Starting at location 0x09, drag to select and highlight a length of F4 bytes, as shown he the HxD bottom status bar.
[*]
Using the Analysis / Checksum menu, double-click Checksum-16 to calculate the new checksum. This will show as a 2 byte value in the Checksums tab at the bottom of the screen. These need to be applied using the correct 'endian-ness', which is the reverse of how the values are presented on the screen.
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
Use your own just-calculated values - not those from the screenshot.
Click File | Save and the mtd6ro_mod file has had the 'enhanced mtd hack' and is ready to be applied to the camera.
This is done during Stage 2 of the fixup script in the brick-fixV2 tool.
Good luck!
At this point, Stage 2 of 3 is ready to be executed.
At the telnet command prompt, type:
/dav/fixup.sh
and watch the on-screen messages.
This will bring in the modified mtd6ro_mod and apply it to the camera to convert it to English / upgradeable.
At this point, Stage 3 of 3 is ready to be executed.
At the telnet command prompt, type:
/dav/fixup.sh
and watch the on-screen messages.
This will attempt a firmware update using the Hikvision firmware file digicap.dav that you placed in the same folder as the tftp server.
Assuming a successful result, shut down the tftp server and power cycle the camera. Interestingly, on testing I did find that a straight jump to the 5.4.5 firmware version worked OK. YMMV. But worth trying.
Start SADP and check for the camera presence running the firmware version used for the update.
If you used the 5.4.5 firmware, the camera will require 'activation' with your choice of strong password.
If already active, if earlier firmware was used for the upgrade, log in with the admin password=12345
Change the IP address to what you want the camera to use.
How To Upgrade
Rename the firmware to digicap.dav
Put the firmware under the same folder of this TFTP
Set the IP of computer as 192.0.0.128
Camera's IP can be anyone.
Run the tftpserv.exe
Power off and power on the DVR/DVS/IPC. The device will search the new firmware and upgrade it automatically.
Please wait until TFTP shows "Device [192.0.0.64] system update completed!" It takes about 5 minutes.
Close the TFTP before the camera reboots.
DVR/DVS/IPC will restart automatically after upgrading.
