As said above i took a look on the "Rescue Tool", when started it look like this:

"connect and send", which is so far ok, but when one check the about dialog there is "Time and Language set". That look like the "tool" is or was doing more than only connect and send soemthing. And actually there is more, but all in chinese language and disabled. So i did translated it into english and re-aranged/enabled again all hidden things. Now the tool likes like this:

No one can set 3 types of things:
- HDVersion (more about this below)
- Language licensing (no idea if this is really used by the firmware, i'm always using default/english/EN)
- time (which didn't work as Hantek removed the code to send time and added code to send profile reset)
One can use that tool now to set these things, but as said abive, langaue is fine when set to what it is. Sure, there might exists OEM models like Voltcraft DSO-3062C where the langauge is set (in EEPROM) to German, but generaly one don't need that functionality. Time/Date settings as said above are not functional, but i leaved them visible. The profile purge, which is "the rescue", is nothing special, the tool is sending shell cmd (one can use the tool fro Peter Dreisiebner for that even better) to purge the file /param/sav/run1kb*. What remains is the
BIG BONUS , the HDVersion settings function, used to store options and hardware licensing into the EEPROM.
I did posted some time ago about the options/hardware licensing stored in the EEPROM (starting from hw1005, on hw0 there was only SN/general info and language set, nothing else)
There are two blocks of information in the EEPROM:
• general information
• licensing information
The general informations are:
• [--LOGx--] - log number, the EEPROM can have multiple entrys (LOG0, LOG1 and so on)
• [serial number] - just your S/N
• [operation time] - the date/time of the DSO final test/factory calibration
• [operator] - the operator/technician name
The licensing informations are:
• [pcb] - PCB version, see below and version.txt for numbers to be entered
• [lcd] - LCD orientation, 0=default, 1=180° rotated
• [front] - your guess is as good as mine, 0 or 1 (but see below more)
• [usb] - i guess this is front usb port activation, 0=default(no second USB), 1=second USB enabled
• [touch] - touch panel function - not yet implemented, default=0
• [net] - LAN license - 0=no lan, 1=LAN enabled
• [iso] - isolation, 0=default (no isolation), 1=isolation enabled (like on DSO1000S handhelds)
• [buf] - memory depth license, 0=4k, 1=20k, 2=1M, 3=2Mpoint enabled
• [sd] - SD function license, 0=no SD, 1=SD enabled
• [vei] - Video function license, 0=no video, 1=video enabled
• [dds] - 0=default. I guess a 1 should enable the AWD/DDS (when integrated)
• [key] - Keyboard layout, 0=default (Hantek)
- The [pcb] is 1005 for hw1005, 1007 for hw1007, etc. For detailed list see attached version.txt
- The [lcd] as said above is used for screen orientation.
- The [front] is unknown to me, i thought some time ago that 1 is for Handheld and 0 for Benchtop,
but i do have some Handheld dumps with [front]=0 and as well MSO5000D dumps with [front]=1.
- The [usb] i think it might be for enabling the 2nd USB port on front, can't test that.
- The [touch] is touch version, no use right now.
- The [net] is 0 on models with no LN and 1 on models with LAN.
- The [iso] thing was unknown for me, finally i know that it means "isolation". Afaik only DSO1000S
handhelds should make use of that key.
- The [buf] key is as said abov for max. enabled memory. Of course it need to be physically available as well,
simply enabling 2M on 40k model will not change anything. Currently on 2Mpoint benchtop models there is
different CPLD design used, so one need not only to solder bigger memory, but as well to program different
design into CPLD (it is on my OneDrive). On Handhelds it seems that there is by default the 2Mpoint
CPLD design programmed, so it is enought to solder bigger SRAM and to change that option in EEPROM.
- The [vei] is enbling video support, one need as well at least kernel 2.6.30 installed.
- The [sd] us enabling the SD card support, on need as well at least kernel 2.6.30 installed.
- The [dds] i thought it will be used by models with DDS, but i did checked MSO50x4FG and there is no
use of that key, it is still set to 0. Wondering why (dod Hantek forgot that option, or do they use it only
on DSO7xxx and Handhleds with DDS?, no idea yet).
- The [key] might be set to 0 (hich is default), 1 and 2. The 1 and 2 are used by some Redsea Handhelds,
with different layout, so it is good idea to leave it by 0 (default).
How these information are stored to EEPROM (see attached picture):
• byte 0002h, 0003h are used for langauge licensing
• general info stored from 1C00h to 1CFFh
• hdversion setting stored from 1D00h

How the S/N can be written:
well, one need to create an empty file and store it on DSO as
/i2c.format. Additionally file containing the S/N
need to be created and stored on DSO as
/i2c.org . The content of this file looks like:
[--LOG0--]
[serial number]DSO050012345
[operation time]2014-05-01 12:00:01
[operator]smart-hackerNOTE: each line in this file need to be terminated with 0Ah and not 0Dh 0Ah.
When these file exists while DSO is booting, the firmware will erase the EEPROM and program the content with informations from the i2c.org file. When there are as well /HDVersion.set and /language.set available in the root of DSO, then they will be programmed as well into the EEPROM. I think there is little need to change S/N, but who knows. If someone wish to change the language or HDVersion licensing informations, then it is sufficient to have onle the /HDVersion.set and/or /language.set copied to DSO root, there is no need to format the EEPROM (so no need for i2c.format file) nor program the S/N (no need for i2c.org file).
And here is this debunked "rescue tool" very useful, one don't need to care about HDVersion.set file format, 0Dh at end of line nor what so ever - simply connect DSO to PC, run that tool, chose HDVersion options and click on write button. That's all. After next reboot the information will get written into the EEPROM (you will see short message window).The debunked tool can be found on my OneDrive
http://1drv.ms/1hf4SgONOTE: you should make backup of your EEPROM content first, to do this simply copy /i2c.log file to secure location. In that file all your options and as well S/N are stored (it is in principle copy of the EEPROM content and it will be re-created each time you change something! so make an backup).