PX-IPD213

blade3609

n3wb
Joined
Jun 23, 2016
Messages
17
Reaction score
6
Ive looked in the mtdblock6 and i found 06 98 in locations 0x64 and 0x65 , and in the document i see 0698 DS-2CD2132-I , so if i follow this guide will i be able to upgrade this to the latest hikvision english firmware?
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,930
Reaction score
6,778
Location
Scotland
It sounds like there is a fair chance it would work ok.
What was in the language byte at hex location 10 ?
If it's 01 then already English, so a normal web GUI update should work.
Unless there is an issue with an OEM code.
 

blade3609

n3wb
Joined
Jun 23, 2016
Messages
17
Reaction score
6
Yes the language byte is already 01, i think there could be an issue with the OEM code, i updated it once from 5.0 to 5.1 and i used a special firmware they provided, it does say in the hex PX-IPD213, so i think its an modified version of the hikvision firmware. I dont want to brick the camera, so whats my best bet to try?
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,930
Reaction score
6,778
Location
Scotland
If you have the genuine device-specific firmware you have a potential escape route, via the tftp updater.
The web GUI update has quite a few validation facilities, so it should reject anything unsuitable.
 

blade3609

n3wb
Joined
Jun 23, 2016
Messages
17
Reaction score
6
Yup, just tried to put IPC_R0_EN_STD_5.4.5_170123 via GUI and got a notification update failed, so my only chance to update this is to use the brickfixv2
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,930
Reaction score
6,778
Location
Scotland
You need to upgrade through the versions, not just all the way.
Also worth doing is to verify if the checksum matches the data. If not, the update will not work.
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,930
Reaction score
6,778
Location
Scotland
how do i verify if the checksum matches the data ?
The simplest way is as shown in the YouTube video example and screenshot -
Using the HxD hex editor with mtdblock6, drag to highlight the bytes starting from hex location 09 (strictly should be 0B, but not going to contradict the guide) until there are F4 bytes total selected, as shown in the 'length' value in the status bar at the bottom.
Then, use the Analysis menu, Checksums, checksum-16 to show the checksum value.
This should match what's stored in hex locations 04 and 05
 

blade3609

n3wb
Joined
Jun 23, 2016
Messages
17
Reaction score
6
Yes i did that and the mtdblock6 matches correctly. I tried updating the camera through web again with this version but didn't work: Baseline Firmware_IPC_R0 series_En_V5.1.2 140116(Released)
The error i get is that "it doesn't know the progress" and just stays at 0%, and it didn't update anything
Do you think i should try the brick method? is there another file which blocks out the hikvision OEM firmware instead of the Winic ?
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,930
Reaction score
6,778
Location
Scotland
Do you think i should try the brick method? is there another file which blocks out the hikvision OEM firmware instead of the Winic ?
Brickfixv2 isn't going to change anything - it's all about the language byte, the devType and the checksum. And you've covered those.
I suspect that your device may have an OEM code that the Hikvision firmware is objecting to.
 

blade3609

n3wb
Joined
Jun 23, 2016
Messages
17
Reaction score
6
I've added the mtd6 file as an image here, maybe you see something i dont.the error i get now using 5.1.2 / 5.1.6 is "Failed to get the upgrade status"
 

Attachments

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,930
Reaction score
6,778
Location
Scotland
I've added the mtd6 file as an image here
That looks OK to me.
the error i get now using 5.1.2 / 5.1.6 is "Failed to get the upgrade status"
That can mean the firmware is incompatible with the camera - perhaps the OEM aspect, though I'm not sure.
But as it's quite an old camera, worth checking the contents of mtdblock1 - it might be fully erased (filled with FF). I'm not sure if that older firmware handles that without objecting. The newer firmware just writes a new, blank template when it finds nothing.

If you want to take a slight risk - you could transplant the attached (fixed-up) donor mtdblock6 from a Hikvision DS-2CD2132-I.
This would of course change the MAC address, serial number etc but should convert to Hikvision.
It was from one of mine that I sold on eBay.
I've not converted an OEM to Hikvision before - so do be aware there is an element of uncertainty here.
 

Attachments

blade3609

n3wb
Joined
Jun 23, 2016
Messages
17
Reaction score
6
Thank you very much, im curious though,but i'll probably test it when i have a replacement in case this one bricks beyond repair.
 

awsswa59

n3wb
Joined
Mar 23, 2023
Messages
24
Reaction score
7
Location
USA
The camera is easily updated with firmware from the R0 generation.
Just updated the camera from 5.0.2 to 5.4.800
 
Top