alastairstevenson
Staff member
That's very helpful, thanks, and the right model.
I don't suppose you can confirm what the devType is, the 2 bytes at hex location 64?
@gravykid - do you need to pick up on this offer?
R0 / DS-2CD2x32 BrickfixV2 brick recovery and full upgrade tool - enhanced.
- Thread starter alastairstevenson
- Start date
I don't suppose you can confirm what the devType is, the 2 bytes at hex location 64?
@gravykid - do you need to pick up on this offer?
Here is the hex view of it:
mtd6ro_orig HEX View
The devtype 1498 did work as well without losing the wifi.
( I confirmed that part in this post from the original prthardinfo: Hikvision DS-2CD2x32-I (R0) brick-fix tool / full upgrade method / fixup roundup. )
Last edited:
alastairstevenson
Staff member
OK, so in the original it has the 'masqueraded' devtype of FF98 and requires a change.
Do you have the value you changed it to in the modded version?
Yes....
mtd6ro_mod HEX View
I didn't circle the checksum numbers because it will be different for his (so as to not cause an issue
)Here is the mtd6ro_orig file from when I pulled it from mine. I zipped it in a directory:
http://redhat.systems/hik/DS-2CD2532F-IWS.zip
Alastairstevenson can confirm but I didn't think the mtd6ro file changes serial number?
gravykid, is your camera sourced from China (ie: with CCCH in the serial number)? I wonder if it did change the serial, if it would even matter.
Update! Sorry, I just noticed the serial of that camera I have is "518701055" so that does show up in that mtd6ro file. Lets see what Alastairstevenson says?
The serial ni the mtd6ro file appears to be made from the manufacturer date plus serial number?
Serial No in Hex Editor - mtd6ro_orig
Serial & manufacturer date on label
Last edited:
Yes, it's from China. When I had the other camera (that I accidentally copied the MTD from) plugged in to my network, I could not Putty into my camera. If it's the only thing on the network, it behaves. I'm wondering if there is network information like MAC address info in it as well?
I searched the mtd6ro-orig file in HxD for the MAC and portions of (c4:2f:90:29:0a:9c) and couldn't find it. If it is there, it could be in hex as well.
Given these devices are used on internal networks, If using that file forced it to adopt the MAC, it shouldn't hurt anything.
btw, don't give up on your camera... if you are not able to restore it via network, you could use the serial port on it. I ended up having to do that after having some problems (caused by me I think). Thanks to alastairstevenson for all his help on that one.
Last edited:
alastairstevenson
Staff member
If you mean the erratic ability to connect - it's the duplicate MAC addresses on the LAN. It's how a layer 2 environment addresses the packets, they need to be unique for it to work.
The MAC address is held on the mtd6r0 flash partition, so with the 2032 one copied top the 2532 they will both be the same in each camera.
If you power off the 2032 temporarily, the 2532 will be accessible, then you can swap in the donor mtd6ro, re-run the brickfixv2 process.
Having duplicate serial numbers should not be a problem.
Hello,
I bricked my ds-2cd2032-i with the same symptoms:
[2018-10-17 00:15:26] TFTP server[192.0.0.128] initialized
[2018-10-17 00:18:09] Device[192.0.0.64] test tftpserver
As I understand I had to connect to it with rs-232 port? Would you be so kind to write what exactly do I need. What hardware I must have to connect to rs-232?
Would attached mImage file fit to my camera?
Thank you in advance.
kindacute...
I can share how I did it on my Hikvision camera:
What helped me determine the connections:
Hikvision - Clearing Passwords and/or Loading Firmware via TTL Serial
The FTDI I used (serial to usb):
FTDI Friend + extras
(You can buy the cable versions too)
Also I soldered the wires to the GND/RX/TX pins.. but I used a very thin soldering tip (otherwise I would not attempt this method).
http://redhat.systems/hik/hik-serial1.jpg
I looked up a tear down of your DS-2CD2032-I :
Hikvision DS-2CD2032-I teardown - CCTV Forum
(most likely the 4 pin connector).
I used a meter to determine which pin was ground and then assumed RX/TX was next to it. (according to below).
(only three connections need to be made GND/RX/TX)
I used secureCRT and created a serial session to the applicable com port (you can use other tools too).
Once you are in via the serial, you can force it to do tftpd updates with a number of commands.
I can share how I did it on my Hikvision camera:
What helped me determine the connections:
Hikvision - Clearing Passwords and/or Loading Firmware via TTL Serial
The FTDI I used (serial to usb):
FTDI Friend + extras
(You can buy the cable versions too)
Also I soldered the wires to the GND/RX/TX pins.. but I used a very thin soldering tip (otherwise I would not attempt this method).
http://redhat.systems/hik/hik-serial1.jpg
I looked up a tear down of your DS-2CD2032-I :
Hikvision DS-2CD2032-I teardown - CCTV Forum
(most likely the 4 pin connector).
I used a meter to determine which pin was ground and then assumed RX/TX was next to it. (according to below).
(only three connections need to be made GND/RX/TX)
I used secureCRT and created a serial session to the applicable com port (you can use other tools too).
Once you are in via the serial, you can force it to do tftpd updates with a number of commands.
Alastairstevenson would be the "Yoda" to direct that question to
alastairstevenson
Staff member
Yes, it would work OK, it's for all R0 series cameras.
But before you spend time trying that, there are a couple of things that can get in the way of the tftp updater engaging with the camera, just in case these are valid for your setup -
Don't connect the camera and PC directly over ethernet or over WiFi - connect each to the router or switch.
Don't power the camera using PoE - use an external 12v power supply.
Something else worth trying - power the camera up, and then press the reset button at the back to see if it connects up to the tftp updater.
alastairstevenson
Staff member
Interesting - and well done!
I see that you got the min-system booted up.
But I don't see the steps you took to get there.
Did you just do the /dav/fixup.sh from there?
Once I got console connected I did as you said:
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
after that camera downloaded mlImage file and then either it is rebooted or I did reboot myself.
After that I was able to start fixup.sh ( I did it over console not over telnet)
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
after that camera downloaded mlImage file and then either it is rebooted or I did reboot myself.
After that I was able to start fixup.sh ( I did it over console not over telnet)
alastairstevenson
Staff member
Thanks for that - it makes sense - it may be useful for others too.