Well done!
On both counts.
Anything worth sharing?
The tftp updater can be affected by using PoE for power, and direct LAN connection to the PC, both likely to be timing related.
R0 / DS-2CD2x32 BrickfixV2 brick recovery and full upgrade tool - enhanced.
- Thread starter alastairstevenson
- Start date
On both counts.
The tftp updater can be affected by using PoE for power, and direct LAN connection to the PC, both likely to be timing related.
No, if the camera is Chinese it will still give a 'language mismatch error' when flashing EN/ML firmware using the serial console.
The 'enhanced MTD hack' converts enough of the configuration to EN to make peace with EN/ML firmware, doesn't touch the serial number though, which would still show CCCH.
AH ok.. thanks.. so the "enhanced MTD hack" modifies the boot portion of the camera (that loads and checks the FW before loading). I love learning this stuff.. thank u!
Not quite - it modifies part of the data in the 'hardware signature block', the data that is specific to an individual camera, written during manufacturing, such as the MAC address, the serial number, the model number, the options such as audio, SD card, WiFi and so on, but importantly also the region (EN or CN).
The firmware uses that data to determine how to operate.
Hikvision have chosen to make CN region cameras and NVRs stop working when updated with EN/ML firmware.
I meant to post that all of my cameras are POE connected with a Cisco switch but TFTP wouldn’t connect. I had to use the 12v adapter with the cubes and a POE injector for the bullets.
Thanks for that - could well be useful to others.
It does seem that the Hikvision tftp updater / handhake implementation is a bit tight on timing.
It may be a bit like what happened on the original pi-3 network boot.
The specific switch that the code was developed and tested on had a particularly fast link-detect response, compared with the average switch.
So the hard-coded bootcode was troublesome and needed some messy workarounds to tweak it into life for many users, myself included.
It does seem that the Hikvision tftp updater / handhake implementation is a bit tight on timing.
It may be a bit like what happened on the original pi-3 network boot.
The specific switch that the code was developed and tested on had a particularly fast link-detect response, compared with the average switch.
So the hard-coded bootcode was troublesome and needed some messy workarounds to tweak it into life for many users, myself included.
Here is one that should help. UART connection to recover Hik cameras
Match up the RX, TX and GND to TX, RX, GND respectively on the serial TTL to USB adaptor.
If you're talking for the serial connector in the cameras? The ones I've done were a four pin JST connector. I wasn't sure of the direction (it was hard to tell) but one of the outer most pins is a ground, and the two directly next to the ground are TX and RX. I used a multimeter to determine which one was the ground, and just used the next two pins as RX/TX. The RX/TX if reversed just won't work, so you can reverse them if that is the case. The pin most opposite the ground is i think +5v.. which is not and should not be used for this.
fritzycat1
n3wb
Here are some details from my experience. The issues I had are probably covered somewhere in this thread, but I didn't read the entire thread before jumping right in (I only really read the first page of posts..)
Since this is a little long, so I'll put the lessons learned up front:
- Run everything as 'Administrator' (TFTP Server, HxD etc).
- Turn off windows firewall.
- Use short network cables.
My set up was a Windows 10 laptop, connected to a Trendnet TPE-S44 switch (8 ports, 4 with PoE), and the cameras connected to a PoE port on that switch. Using 6 foot Cat6 cables.
First upgrade was the DS-2CD2432F-IW. This camera was still working, but was running an old Chinese firmware. Here were the issues I encountered:
1. Initially, the camera would not connect to the Hikvision TFTP server. At first I thought it might be because I was using PoE for power, so I changed to an external power supply. That made no difference. Eventually I found I needed to disable the Windows Firewall on my laptop to get the connection to work (NetSh Advfirewall set allprofiles state off). After disabling the firewall, the camera connected just fine.
2. When running the first /dav/fixup.sh I would receive an error when it tried to upload the file to the FTP server. The message was 'error(2) permission denied' or something like that. I eventually determined that I needed to run the TFTP server (tftpd32) as 'Administrator' - that fixed the permission issue.
3. When editing the mtd6ro_mod file in HxD, I found I could not save the file to the 'C:\Program Files (x86)\Tftpd32' folder unless HxD was running as 'Administrator'.
4. I would periodically lose my putty telnet session connection, so just needed to start a new session. Not sure what the cause of that, but it happened with both of my cameras.
Next upgrade was the Chinese DS-2CD2032-I - this is the camera that was hobbled after the failed English V5.4.5 upgrade attempt. Only one issue with the process here:
This camera is installed outdoors, so I attempted to upgrade it over the existing network cable. About 100' of Cat5e. That didn't go so well. Several attempts to upload the brickfixV2EN digicap.dav file using the Hikvision FTP server failed. The camera failed to connect to the TFTP server initially, then when it did connect I received 'Receive Data ACK error' messages and the process hung after the 'completed file transfer' message (never received 'system update completed!' message). I had a few other failure messages after several other attempts too.
I moved my switch and laptop to the camera's location and connected the camera to a PoE port with a 6' Cat6 cable. That did the trick - the rest of the process went smoothly from there.
Thanks again for the time and effort put into this process. I have no idea how you figured out how to do this, but I'm sure glad you did!
I'd wonder about the 100 foot cable if changing the cable made the difference. It shouldn't.
You are welcome - glad to help.
Some of the triggers - apart from the curiosity and interest in analysis and problem-solving - were a dislike of Hikvision's sometimes quite nasty contempt for their end-user customers in the things they have incorporated in the firmware code to deliberately break the products.
fritzycat1
n3wb
Yea, I know it shouldn't but I've always had issues with this camera randomly losing connection and often the video is slow to load or temporarily drops out so I have my suspicions about the cabling. I was just removing the cabling as a variable by connecting it to the switch more directly. I need to take a closer look into it...
I agree - wish they would put that effort into product improvements instead.
super-thanks !! finally made useful my 2332
its been sitting bricked after trying to update its chinese base into EN...
...and now it finally gets to work
following instructions worked, tho please mention in the the step "- Start the tftp server" (NOT tftp updater server) , use tftp jouinin.net is needed
its been sitting bricked after trying to update its chinese base into EN...
...and now it finally gets to work
following instructions worked, tho please mention in the the step "- Start the tftp server" (NOT tftp updater server) , use tftp jouinin.net is needed
fritzycat1
n3wb
Just want to thank everyone for this. I just upgraded mine, and while it took a while I got it.
The biggest issue was when I was trying to get it to update from "hikvision tftpd" it wasn't working. I almost gave up then thought maybe I need to have it plugged into a switch rather than directly into the computer. That solved the issue for me. I noticed every time i turned the camera on when plugged into the computer it detected network then stopped, then detected then stopped, then detected and stayed on.
The biggest issue was when I was trying to get it to update from "hikvision tftpd" it wasn't working. I almost gave up then thought maybe I need to have it plugged into a switch rather than directly into the computer. That solved the issue for me. I noticed every time i turned the camera on when plugged into the computer it detected network then stopped, then detected then stopped, then detected and stayed on.
Yes, that can be a troublesome way to connect up the devices, not recommended.
There can be similar difficulties getting the handshake to complete reliably when the camera is connected via PoE.
That's the way the bootloader probes for the Hikvision tftp updater - it does an 'interface up', send a UDP packet, waits a short while, interface down, interface up, sends a packet, waits, interface down, then interface up as part of the normal boot if no response occurs.
When directly connected, after the interface up, the PC also has to respond with a link detect, so there is an additional delay which can cause the UDP packet to be missed by the PC.
Hey Guys,
Having some issues getting my DS-CD2532F-IWS to play nicely. Does anyone know what the proper devtype bytes are for this model? I accidentally updated it with the an MTD from my 2032 and trying to get it back to normal.
All the rest are playing nice....so far. I've attached my modded MTD...
EDIT: I may have figured it out as I think it may have had to do with having the same serial number from the 2032 camera. I updated the numbers with the correct serial number and we'll see how it goes...
Having some issues getting my DS-CD2532F-IWS to play nicely. Does anyone know what the proper devtype bytes are for this model? I accidentally updated it with the an MTD from my 2032 and trying to get it back to normal.
All the rest are playing nice....so far. I've attached my modded MTD...
EDIT: I may have figured it out as I think it may have had to do with having the same serial number from the 2032 camera. I updated the numbers with the correct serial number and we'll see how it goes...
Attachments
Last edited:
It's more likely that the duplicate MAC address is the problem. If these are both on the LAN at the same time, their networking will not work properly.
Is that screenshot your original mtd6ro since modified?
If so, the devType is already OK at 1498, which is the value for a DS-2CD2532F-IS. Did you manage to do the prtHardInfo command to see it?
Or have you lost the original mtd6ro?
If so, attached is a modded one from a DS-2CD2532F-IS, which will work OK, possibly apart from the WiFi function.
I don't have a sample from a DS-2CD2532F-IWS
I think I have a copy of the original mtd6ro_orig from my DS-2CD2532F-IWS if it helps.
I wasn't sure if the mtd6ro_orig it was at first, but if you open it with notepad, it does have some readable text on the top "DS-2CD2532-IWS" at the top.
View from notepad of mtd6ro_orig
Last edited: