Custom Firmware Downgrader 5.3.0 Chinese to 5.2.5 English

Hasslehogg

n3wb
Joined
Oct 16, 2017
Messages
16
Reaction score
1
ok it was the installation that was the issue. was fine after cleared out everything and reinstalled.

ok hopefully almost there, i have took a temp copy of mtkblock6 and have changed the language to 01, i have my devtype (38920) which is 9808 in hex, i have looked at the 2322 modded pic and can see changes in sections 04 & 05 on the 1st row, and 04 on the 7th row with the instructions stating:-

"0x64 and 0x65 devType bytes set to the value from your prtHardInfo command, for example 0x9807 (ie 0798 for the correct byte order) for the DS-2CD2232-I5"
I assume i put my 07 in row 7 column 4 and column 5 is already 98

"0x04 and 0x05 Checksum-16 bytes Set to the Checksum-16 value as calculated by HxD for the 0xF4 bytes starting from location 0x09 remembering the correct byte order, 0x04 is the least significant byte."

This is a little confusing, do i need to put my Checksum-16 value (0E28) backwards as well putting in 28 in row 0 column 4 and column 5 having 0E. but it mentions location 09?

thanks again Alastair
Ah re you saying take the reading from 0x09? i get it. ok I think i am done, i will update to 5.3 to 5.4 to 5.4.5 fingers crossed and thanks a lot for the help, appreciate it
 

Hasslehogg

n3wb
Joined
Oct 16, 2017
Messages
16
Reaction score
1
Ah re you saying take the reading from 0x09? i get it. ok I think i am done, i will update to 5.3 to 5.4 to 5.4.5 fingers crossed and thanks a lot for the help, appreciate it
Sorry back again, my checksum has changed after i changed the above. The checksum i enter into 0x64 and 0x65, is this the checksum before i started this, or after all of the changes i just done please?
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,966
Reaction score
6,795
Location
Scotland
Your devType is 9808 not 9807.
And the checksum must match the current data.
So if you change the data, you need to change the checksum.

I think you've got it!
 

Hasslehogg

n3wb
Joined
Oct 16, 2017
Messages
16
Reaction score
1
Your devType is 9808 not 9807.
And the checksum must match the current data.
So if you change the data, you need to change the checksum.

I think you've got it!
unfortunately not, i made the changes i stated above, logged into the gui and it was in english :) but then i updated to 5.3 from the european site and its pinging and showing in sadp but it says min-system again and the actual browser screen is still showing rebooting but its been showing that for 10 minutes :(

i changed:-

row 00000010 column 00 from 02 to 01
row 00000060 column 04 i put 08
row 00000060 column 05 i put 98

i then recalculated the new checksum from row 00000000 column 09 to the end of 000000F0 which was different from the checksum before i made any changes. anyway it was 0D31

so i changed the following also:-

row 00000000 column 04 i put 31
row 00000000 column 05 i put 0D

i saved as temp6 and wrote it back with:-

cat temp6 > /dev/mtdblock6

then ran the reboot tool and logged in fine.

then i ran the firmware upgrade from the EU site of IPC_R0_EN_STD_5.3.0_151016

and back to no web gui in the browser, any idea what i have done wrong guys, thought i had it :(
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,966
Reaction score
6,795
Location
Scotland
What you've described above sounds OK to me.

There is another potential 'gotcha' that fits the symptoms, depending on when the camera was manufactured.
Cameras manufactured with firmware 5.2.8 don't have the 'status of last firmware update' pre-set in the flash, with the result that when the 5.3.0 is installed and checks for it, the firmware reboots into min-system recovery mode as it considers the last update had failed.
Here is how to check and fix (hopefully this will be your situation) :
Extract a copy of mtdblock1 and examine the contents of locations 0x0C and 0x8000C
If they hold a 0 change them to a 2 and rewrite mtdblock1 back to the camera.

the actual browser screen is still showing rebooting but its been showing that for 10 minutes
That's because the IP address in use has changed, the browser is still trying the previous address, also in min-system recovery mode there are no web services, so no browser access.
 

Hasslehogg

n3wb
Joined
Oct 16, 2017
Messages
16
Reaction score
1
What you've described above sounds OK to me.

There is another potential 'gotcha' that fits the symptoms, depending on when the camera was manufactured.
Cameras manufactured with firmware 5.2.8 don't have the 'status of last firmware update' pre-set in the flash, with the result that when the 5.3.0 is installed and checks for it, the firmware reboots into min-system recovery mode as it considers the last update had failed.
Here is how to check and fix (hopefully this will be your situation) :
Extract a copy of mtdblock1 and examine the contents of locations 0x0C and 0x8000C
If they hold a 0 change them to a 2 and rewrite mtdblock1 back to the camera.


That's because the IP address in use has changed, the browser is still trying the previous address, also in min-system recovery mode there are no web services, so no browser access.
thanks again Alastair, i will give it a try, i will start again from scratch

thanks
 

Hasslehogg

n3wb
Joined
Oct 16, 2017
Messages
16
Reaction score
1
You just need to get back to 5.2.5 with the '5.3.0 to 5.2.5 downgrader', no more than that.
Then check out the mtdblock1.
The rest will still be OK.
Alastair could you tell me in idiots speak what those 2 locations are please 0x0C and 0x8000C

I have HxD open but havent a clue which 2 parts to check

thanks
 

Hasslehogg

n3wb
Joined
Oct 16, 2017
Messages
16
Reaction score
1
Alastair could you tell me in idiots speak what those 2 locations are please 0x0C and 0x8000C

I have HxD open but havent a clue which 2 parts to check

thanks
53 57 4B 48 0F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 08 00 02 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FF 48 4B 57 53
Alastair could you tell me in idiots speak what those 2 locations are please 0x0C and 0x8000C

I have HxD open but havent a clue which 2 parts to check

thanks
managed to work it out and its working, thanks very much for all your help Alastair, really appreciate it.

I dont suppose if you know if the procedure is the same for a 2335 on firmware 5.4.20 do you please?

Any best practice tips you have as well would be appreciated for security or anything really as i dont know what i am doing with this apart from watching live feed, the emails done work, the record when someone passes doesnt seem to work, when i manually record it stops all the time.

anyway thanks again, you are a star
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,966
Reaction score
6,795
Location
Scotland
managed to work it out and its working,
Will done for getting there. It can be a bit of a learning curve when the topics are new and unfamiliar.
Your screenshot of mtdblock1 does show it was firmware version 5.2.8 with 0 in the locations that define the last update status.

The 2335 is a different camera series.
I don't ( as yet) have the equivalent process for those.
 
Joined
Oct 17, 2017
Messages
7
Reaction score
1
I can't seem to get it to work. Could you please confirm the following steps are correct? My camera is DS-2CD3410FD-IW come with default Chinese version of 5.3.0 Build 150327
- Assign the computer IP 192.0.0.128
- Run the TFTP server from the zip file
- Reboot the camera
- I can see it connected > Try to transmit > Resend required > Complete transfering > ... and then nothing
- I can go to the IP and the camera is still in Chinese.
Please help :)
Day whoslooking

I have already tried everything but he does not go beyond this! do you have any tips? The model number is DS-2CD2132F-IS

Kind regards
unnamed.jpgunnamed-2.jpg
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,966
Reaction score
6,795
Location
Scotland
Seeing ' re-send required' in the tftp updater is an indication of networking issues.
The PC should be wired, not WiFi, for example.
Maybe check the cables also.
 
Joined
Oct 17, 2017
Messages
7
Reaction score
1
Hi thanks for the quick answers! I've been lying over the cable and trying another utp, but he keeps saying!
 
Joined
Oct 17, 2017
Messages
7
Reaction score
1
I have already tried with 2 different computers! and I've also tried a lot of different webdav versions but I do not want to succeed! I have to do a hard reset on the camera first!
 
Joined
Oct 17, 2017
Messages
7
Reaction score
1
And do you know which software version I should have? For this Camera DS-2CD2132F-IS China
 
Joined
Oct 17, 2017
Messages
7
Reaction score
1
I am now thinking a little further! He says that he's been successful! but after 51 minutes, and when I open SADP then I do not see a camera ???

unnamed-3.jpg
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,966
Reaction score
6,795
Location
Scotland
A couple of things -
There are both EN and CN versions of the 'downgrader' - have you tried both?
Also, if firmware of 5.4.0 or higher has been applied, a downgrade block will be in place, requiring the brick-fix tool to be used. See my signature.
 
Joined
Oct 17, 2017
Messages
7
Reaction score
1
my english is not very good! but you meant to try another version? and if yes! could you give me a link where i can download it?

Sincerely Dirk
 
Joined
Oct 17, 2017
Messages
7
Reaction score
1
YES YES it has been successful !!!!! I've found the V5.3.5_150925 version somewhere on a site !! and who does! AMAZING

Thank you for your help
 
Top