Hikvision IPC Firmware 5.5.0 - released 24 Sept 2017

I checked the power adapter with a multimeter and it registered about 2.1 volts instead of 12v, i don't know if the adapter burned the camera or the camera burned the adapter.
 
OddMorning said:
I just found a way how to downgrade 5.5.0 to 5.4.x (it worked on DS-2CD2142FWD-I at least).
In short, use hikpack to change 5.4.x's version to 5.5.0 and then upload it via tftp.

Something like VirtualBox is needed in any case because hikpack works under Linux while TFTP works under Windows. Or probably use wine/win10 :blankstare:

Download the needed firmware file from the HikVision portal (there's also a file called List of IPC ... .xlsx with a "camera <=> firmware" matching table, it was 5.4.5 for R6 in my case).
Then use hikpack to change firmware version. Put downloaded digicap.dav next to hikpack file and enter these lines in terminal (r6 means platform):
Code: 
./hikpack -t r6 -x digicap.dav -o 5.4.5_unpacked
./hikpack -t r6 -p digicap_fake_5.5.0.dav -V 0x05050000 -o 5.4.5_unpacked
And after that use TFTP to upload the "fake" firmware to the camera (because the Web UI still doesn't accept it). That link already contains instructions how to use tftp but there are better instructions by HikVision (for windows) that I found useful.

I know there are mostly pros on this forum but I still hope it can be useful for someone (e.g. for me myself :lol:). These instructions are not really detailed because I'm not sure if that's an universal way or I'm just lucky and that works just for my camera.

Although the file version is changed to 5.5.0, the Web UI says it's V5.4.x and allows to upload any 5.4.x through it. To test it, I uploaded montecrypto's 5.4.3 repack via web and it worked well.

UPD: it seems this method works not just for me so I added the “fake” firmware to this message (R6 5.4.5 with changed version to 5.5.0) for those who doesn't know how to mess with linux (or just doesn't want to).
Click to expand...


OddMorning,

Good sh*t bro !!! This worked WELL with DS-2CD2342WD-I. For those still having issues, do the following and it will definitely unbrick your 2342 for sure:

1) Run Hikvision TFTP
2) TFTP the file OddMorning has posted.
3) Camera will reboot, but may not run the firmware correctly. Manually reboot the camera.
4) SADP tool will not discover your camera.
5) I went ahead and used the 5.4.5 version of firmware again and TFTP'd to the camera.
6) Reboot the camera and viola!

Awesome post.. I have been looking for a fix for some time now. Wish I seen this earlier!!

Thanks again OddMorning.. I truly appreciate it!!
 
@OddMorning,

very much appreciate your R6 fake 5.5.0 patch. It worked for my LaView LV-PB932F4 (aka HIK DS2CD2220/22) w/FM 5.4.0. LaView has joined the no revert bandwagon and locked their FM @ 5.4.0, similar to HIK, and took it further by not allowing any update newer as well, scabby at the very least. Your digicap reverted the ipc back to the HIK 5.3.0 FM I previously had, the first time through, An unexpected result but welcome nonetheless. Still scratching my head on how it did it! cudos
 
I sent my 2142 back to Hikvision after an upgrade to 5.5.0 would not allow it to connect to my router that had an ip reserved by MAC address. I was hoping they would roll me back to 5.4.5. They didn’t. They upgraded it to 5.5.5, which still cant pull and maintained a reserved IP address. I settled with a static ip and the cameras work well except it won’t connect to my NTP server. I have two other cams on 5.4.5 that work perfectly so I know it isn’t “the user” as some of you have claimed. Thinking of upgrading to 5.5.53. Anyone done that yet?
 
HikGr said:
I checked the power adapter with a multimeter and it registered about 2.1 volts instead of 12v, i don't know if the adapter burned the camera or the camera burned the adapter.
Click to expand...

AC or DC adapter?

I have plenty of 12V AC adapters but only one 12V DC adapter, I have now labeled it as such. For camera testing only.
 
So I managed to brick my DS-2CD2155FWD-IS trying to revert back to the stock R6 5.4.5. The camera pulls the file from TFTP, but never proceeds with the upgrade. I realize this is due to protection from 5.5.x to 5.4.x.

I then tried the R6 fake firmware posted in this thread, but still the same result. It pulls the R6 fake firmware down via TFTP, but never proceeds with the ugprade. I am able to SSH into the camera after TFTP via 192.168.1.64 with the login "root/hiklinux", so I am able to get to a shell. From here I try "/bin/upgrade", and receive the error message below.

[ERROR] [MIN]BURN digicap package error, can not upgrade!!!!

I am at a loss here. Thankfully I can get to a shell, so it's not a total brick. Any suggestions on what it could be?
 
I'm having a nightmare with a new DS-2CD2143G0-I. It was behaving strangely (weird live view issues, etc), so tried to upgrade the firmware (was on 5.5.53. It failed to complete the upgrade to 5.5.61. I attempted several different TFTP recoveries, all failed. Some I would get "Receive data ACK error". I also attempted to use the wonderful python Hikvision-tftp from Scott Lamb and would get:
Setting block size to 512

Serving 34510047-byte digicap.dav (block size 512, 67403 blocks)

Wed Oct 3 13:43:48 2018: Replied to magic handshake request.

read request options: {'tsize': '0', 'blksize': '8192'}

Setting block size to 8192

Serving 34510047-byte digicap.dav (block size 8192, 4213 blocks)

Wed Oct 3 13:43:54 2018: sending options ack

read request options: {'tsize': '0', 'blksize': '8192'}

Setting block size to 8192

Serving 34510047-byte digicap.dav (block size 8192, 4213 blocks)

Wed Oct 3 13:43:54 2018: sending options ack

read request options: {'tsize': '0', 'blksize': '8192'}

Setting block size to 8192

Serving 34510047-byte digicap.dav (block size 8192, 4213 blocks)

Wed Oct 3 13:43:54 2018: sending options ack

read request options: {'tsize': '0', 'blksize': '8192'}

Setting block size to 8192

Serving 34510047-byte digicap.dav (block size 8192, 4213 blocks)

Wed Oct 3 13:43:54 2018: sending options ack

read request options: {'tsize': '0', 'blksize': '8192'}

Setting block size to 8192

Serving 34510047-byte digicap.dav (block size 8192, 4213 blocks)

Wed Oct 3 13:43:54 2018: sending options ack

Wed Oct 3 13:43:54 2018: 1 / 4213 [ ]

<I'm truncating this from here>

Wed Oct 3 13:44:00 2018: 4213 / 4213 [#####################################################]

Wed Oct 3 13:44:00 2018: done!

Setting block size to 512

Serving 34510047-byte digicap.dav (block size 512, 67403 blocks)

Wed Oct 3 13:44:31 2018: received unexpected handshake bytes '53574b4807000000000000000000000000000000' from 192.0.0.64:59993


Still no life from this guy. Any thoughts? I was thinking maybe there's something new in the handshake for the G1 series cameras maybe?

Any thoughts?
 
OddMorning said:
I just found a way how to downgrade 5.5.0 to 5.4.x (it worked on DS-2CD2142FWD-I at least).
In short, use hikpack to change 5.4.x's version to 5.5.0 and then upload it via tftp.

Something like VirtualBox is needed in any case because hikpack works under Linux while TFTP works under Windows. Or probably use wine/win10 :blankstare:

Download the needed firmware file from the HikVision portal (there's also a file called List of IPC ... .xlsx with a "camera <=> firmware" matching table, it was 5.4.5 for R6 in my case).
Then use hikpack to change firmware version. Put downloaded digicap.dav next to hikpack file and enter these lines in terminal (r6 means platform):
Code: 
./hikpack -t r6 -x digicap.dav -o 5.4.5_unpacked
./hikpack -t r6 -p digicap_fake_5.5.0.dav -V 0x05050000 -o 5.4.5_unpacked
And after that use TFTP to upload the "fake" firmware to the camera (because the Web UI still doesn't accept it). That link already contains instructions how to use tftp but there are better instructions by HikVision (for windows) that I found useful.

I know there are mostly pros on this forum but I still hope it can be useful for someone (e.g. for me myself :lol:). These instructions are not really detailed because I'm not sure if that's an universal way or I'm just lucky and that works just for my camera.

Although the file version is changed to 5.5.0, the Web UI says it's V5.4.x and allows to upload any 5.4.x through it. To test it, I uploaded montecrypto's 5.4.3 repack via web and it worked well.

UPD: it seems this method works not just for me so I added the “fake” firmware to this message (R6 5.4.5 with changed version to 5.5.0) for those who doesn't know how to mess with linux (or just doesn't want to).
Click to expand...

Thank you mate, can confirm this worked also on a DS-2CD2142FWD-I with FW 5.5.53! :wave:
 
OddMorning said:
I just found a way how to downgrade 5.5.0 to 5.4.x (it worked on DS-2CD2142FWD-I at least).
In short, use hikpack to change 5.4.x's version to 5.5.0 and then upload it via tftp.

Something like VirtualBox is needed in any case because hikpack works under Linux while TFTP works under Windows. Or probably use wine/win10 :blankstare:

Download the needed firmware file from the HikVision portal (there's also a file called List of IPC ... .xlsx with a "camera <=> firmware" matching table, it was 5.4.5 for R6 in my case).
Then use hikpack to change firmware version. Put downloaded digicap.dav next to hikpack file and enter these lines in terminal (r6 means platform):
Code: 
./hikpack -t r6 -x digicap.dav -o 5.4.5_unpacked
./hikpack -t r6 -p digicap_fake_5.5.0.dav -V 0x05050000 -o 5.4.5_unpacked
And after that use TFTP to upload the "fake" firmware to the camera (because the Web UI still doesn't accept it). That link already contains instructions how to use tftp but there are better instructions by HikVision (for windows) that I found useful.

I know there are mostly pros on this forum but I still hope it can be useful for someone (e.g. for me myself :lol:). These instructions are not really detailed because I'm not sure if that's an universal way or I'm just lucky and that works just for my camera.

Although the file version is changed to 5.5.0, the Web UI says it's V5.4.x and allows to upload any 5.4.x through it. To test it, I uploaded montecrypto's 5.4.3 repack via web and it worked well.

UPD: it seems this method works not just for me so I added the “fake” firmware to this message (R6 5.4.5 with changed version to 5.5.0) for those who doesn't know how to mess with linux (or just doesn't want to).
Click to expand...
Hi MASTER!
Can You prepare also 5.4.0 false firmware for R6? I must downgrade from 5.4.0 to less than 5.4.0.
 
I got a couple of 2CD2442FWD. Did anybody get the PIR alarm working together with BlueIris on 5.5.0 or 5.5.53? Neither worked for me.

I've opened a ticket with BI to see if something can be done on that side. If not I guess it's only the TFTP option left to downgrade, right?
 
Hello,

This thread is quite old and the 5.5.x firmware must've matured by now. Is still there a reason not to use the 5.5.x firmware or a reason to stay on or downgrade to the 5.4.x firmware?
 
I just got 5.6.0 for my R7 camera and I WISH I could downgrade back to 5.5.3. It was so much better.
 
@tinimark Did you factory default the camera after the upgrade? If not, try that and then set up smart tracking again.
 
You must log in or register to reply here.
Top Bottom