Discussion in 'Hikvision' started by whoslooking, May 3, 2015.
No you must do the mtd hack first, then upgrade with English 5.30
Ah wish I saw this yesterday, I had paid CBX for his hack last year which I thought was the MTD hack, I did the upgrade and now have the language mismatch error. Will have to try and go back through the forums to see how to unbrick it.
I'm almost there, just missing to find where to make the change to the hex file.
Hopefully I'll get my DS-2CD1103-I running V5.2.3 build 141024 into english so it can work along with my DS-7104N-SN/P that's already working fine with another DS-2CD2020F-I.
Thanks for sharing the solutions found.
We're together, I'm stuck trying to figure out where to make the change.
This technique is only for the DS-2CD2x32 cameras, the R0 series.
Your camera, I believe, is an R2 series, so the method does not apply.
In others words, there's nothing else I can do about that then.
The only way to keep using that camera will be by streaming the videos with the RTSP protocol. I didn't want to miss the feature of "controlling" the camera setup such as data right on the NVR.
The basic technic apply to all series even nvr but need to be older then Mid 2015 to accept latest firmwares without issue. Newer cameras have additional protection
I just want to thank "Whoslooking" for posting this method. I totally blew my leg off today by updating a Chinese camera with US firmware. This method totally saved my ass today so THANK YOU!!!
Hi, I'm really sorry, I'm new here.
I'm actually going to purchase CN version of DS-2CD45C5F cameras due to 3 times price difference.
Could someone kindly advise if I will be able to apply MTD hack to this model?
Thanks a lot in advance
Can anyone tell me where to get Chinese FW 5.1.6 with or without modification for language?
Couldn't find 5.1.6 anywhere but managed to use the 5.2.5 from the downgraded. Unfortunately the smart events which is the reason I want to upgrade still aren't there
Have I missed something here. Do I need to do the MTD hack and use EU FW to get the smart events on my 2132's?
editing the region and the mac or date was to keep the checksum correct, i believe the new checksum calculation is known any one care to share?? so i can edit the region with out altering the date or mac addr???
Tried messing around with normal motion detection and kept failing to save via IVMS4200 (Camera Settings page). Then tried via remote configuration through IVMS and got the following error when saving motion settings:
"Error code HCNetSDK.dll.(Data transmission failed, incorrect data to or from the device.)"
Plugin doesnt work on safari OS X so can't use web interface.
So I tried rolling back to 5.0 (provided by seller) and got failed to update error. Then thought i'd try to update to 5.2.5 again incase something went wrong the first time. Now no longer get English option like I did the first time I updated, but to do get smart events showing up on web interface (they don't show up on IVMS, but that is the same for my UK camera so presume its an IVMS issue).
Effectively 1 step forward 1 step back. Guess I need to do the MTD hack on this camera now. But still not sure why motion settings aren't saving.
Any pointers/help please
Well thought I'd try the MTD hack on this Cam. Decided to backup all the MTD blocks and came across first problem:
# cat /dev/mtdblock8 > temp8
cat: read error: Input/output error
All the other blocks, including 5 & 6 seemed to work so I moved on. Downloaded iHex (on MAC) and found temp5 = all FF's.
Corrupt block? Something to do with the vendors own hack?
Is there a way to recover it?
Forgot to mention block 6 is fine.
Bit the bullet and updated another camera to 5.2.5 (needed to update to enable Telnet access) and again MTD5 is all FF :/
Any help would be greatly appreciated as can't seem to find any other threads mention this issue.
Mtdblock8 is open by the system, it holds the recovery files, a basic kernel and the update programs.
Use mtd8ro instead.
There should be a few hundred bytes of data at the beginning of mtdblock5, the rest is all in the erased (0xFF) state.
Ahh thanks for the pointer on Mtdblock8, that worked.
Unfortunately mtdblock5 is definitely FF on both cameras. Checked and double checked and then once again out of shear desperation :/
I'm not sure if I caused this by using the 5.2.5 FW from the 5.3.0 -> 5.2.5 downgraded.
It's most likely something to do with when the camera was manufactured.
It doesn't really matter.
A firmware update doesn't change it.
This is on both cameras Iv'e updated to 5.2.5. The others I can't check as 5.0 doesnt have option to enable telnet and I can't seem to find any other version between the two.
Ok I guess I edit block 6 and proceed then? I'm currently stuck anyway so keep digging to get out of the hole
Separate names with a comma.