R0 / DS-2CD2x32 BrickfixV2 brick recovery and full upgrade tool - enhanced.
- Thread starter alastairstevenson
- Start date
alastairstevenson
Staff member
That's a pity - I thought that might be the key, as it was on others.
Presumably a 'ping -t 192.0.0.64' shows 2 or 3 responses after power on, then none. But does it repeat?
As a long shot - as no changes had previously been needed - temporarily disable the Windows firewall and see if the tftp updater connects.
Ausjacko
n3wb
I'm the same trying to change v5.5.61 I can see the device in SADP but when I try to ping the IP, or using a browser to get to it, nothing. Best I have achieved is 2 or 3 packets received via a ping. No firewall active. Telnet via putty to the device is also not possible. Oddly enough, I can hear the camera 'clicking' as I try to ping it. I can see a green activity LED flashing inside it but that is about it.
FYI, I read somewhere else that v5.5.X has the ONVIF disabled as a default setting.
FYI, I read somewhere else that v5.5.X has the ONVIF disabled as a default setting.
ruslanruslan
n3wb
alastairstevenson
Staff member
That is a bit of a puzzle.
It looks like the u-boot handshake process with the tftp updater is not working.
It sends the probe, but does not respond to the resulting response and complete the handshake.
And you have proved it's not due to the usual aspects that can sometimes get in the way.
Where are you based?
If you feel inclined to get to the bottom of this, by spending further time and effort on it, the serial console will show what's happening and provide an alternate method of updating.
For this you need a couple of items :
A serial TTL to USB convertor, a PL2303HX-based one works OK.
A 4-pin 1.5mm ZH JST wired connector, usually sold in 10-packs.
ruslanruslan
n3wb
I'm in Russia. pin-connecting is too hard for me..
anyway, today I update 3 other absolutely the same cams. It was easy and fast, without any problems. Guess, maybe, it is not recommended to use this type of updating for bricked cams, because the only difference was that my first cam was bricked by updating to 5.4.5 from web gui. so now i got fresh cams and milestone software imported them successfully, thank you for your work!
anyway, today I update 3 other absolutely the same cams. It was easy and fast, without any problems. Guess, maybe, it is not recommended to use this type of updating for bricked cams, because the only difference was that my first cam was bricked by updating to 5.4.5 from web gui. so now i got fresh cams and milestone software imported them successfully, thank you for your work!
alastairstevenson
Staff member
challengedaivvd
n3wb
- Joined
- May 16, 2015
- Messages
- 6
- Reaction score
- 0
where do i go from here?
followed this guide, but not closely enough i made a mistake with hex editor and put the wrong info in, then the camera wont start and says language mismatch
now i have updated the hex file correctly but his time but cannot get a putty session to connect, what am i missing?
thanks in advance
followed this guide, but not closely enough i made a mistake with hex editor and put the wrong info in, then the camera wont start and says language mismatch
now i have updated the hex file correctly but his time but cannot get a putty session to connect, what am i missing?
thanks in advance
alastairstevenson
Staff member
challengedaivvd
n3wb
- Joined
- May 16, 2015
- Messages
- 6
- Reaction score
- 0
Hi, i did just that, started from scratch and its now upgraded, just x2 more to do
thanks for this guide, very helpful even for us newbs
thanks for this guide, very helpful even for us newbs
alastairstevenson
Staff member
Excellent! Well done, nice result.
Thank you for all this info. I used the instructions on a DS-SCD2332-I that was sourced from China and to allow US firmware. While it wasn't a big problem I could not set the camera as HIKVISION when adding it to my NVR, but had to set it as ONVIF. Once using these instructions I was able to load US firmware into it.. problem was gone. I couldn't see any later than 5.4.0 firmware though for this model of camera.
alastairstevenson
Staff member
Well done for getting there!
5.4.5 here :
Value Series
DOWNLOAD PORTAL
5.4.0 is still vulnerable to the 'Hikvision backdoor'. You need 5.4.5 or 5.4.41
5.4.5 here :
Value Series
DOWNLOAD PORTAL
Worked like a champ! 12 Cameras upgraded from v5.2.0 to v5.4.5 build 170123 (9x DS-2CD2032-I / 3x DS-2CD2432-IW)
Thanks so much @alastairstevenson
Wow! didn't realize this was my first post and I have been lurking since 2014 :O
Thanks so much @alastairstevenson
Wow! didn't realize this was my first post and I have been lurking since 2014 :O
Attachments
Last edited:
alastairstevenson
Staff member
Hey, well done.
That's impressive!
i have the same problem. I only see 2-3 pings from 192.0.0.64
but I'm ready to go ahead and flash through TTL-USB converter))) How can I do that?
alastairstevenson
Staff member
If you have access to the serial console, and can interrupt the bootloader, you can use the 'update' command to trigger the tftp load and install of brickfixV2xx (named as digicap.dav).
fritzycat1
n3wb
Inadvertently attempted to flash English 5.4.5 on my Chinese language DS-2CD2032-I - causing it to be inaccessible from the web GUI. This process brought it back to life, and in English too!
While I was at it I updated my other Chinese camera to English - a DS-2CD2432F-IW (slab) camera. Also worked great - only issues were some communication challenges with TFTP and putty, but it eventually worked.
Thanks for all the hard work in creating this process!
While I was at it I updated my other Chinese camera to English - a DS-2CD2432F-IW (slab) camera. Also worked great - only issues were some communication challenges with TFTP and putty, but it eventually worked.
Thanks for all the hard work in creating this process!
That makes me wonder... does going through the console and forcing an update (pull a digicap.dav) via TFTP work successfully, if that digicap.dav is an english FW and the camera is china sourced and had previously chinese FW? All the ones I did (all successfully in the end ) were always the Hex edit method.