-> HOME

Some common rules and explanations:

• When working with Mercedes it is not a good idea to talk about dumps at all. Everything is based on hash list.
• There can be a lot of different key versions, a lot of EIS with different hardware, but basic rules remain the same. For example data blocks from EIS are read out equally, it doesn’t matter what EIS it is (908, 912 or NEC based) if it is based on FBS3 ideology and rules. For keys situation is the same - it doesn’t matter which firmware version it is, must work equal in most cases. In later versions only some additional functions added. That’s why sometimes there are compatibility issues.
• All MBtool softwares are based on rules what follow from initial data, so called HASH LIST. That’s only information that makes each FBS3 component unique for each car.
• In our implementation HASH LIST data is stored in file with extension *.grnkey . It is actually a binary file what contains 8xKEY final hash, sonder hash, schliessung number (auth password), key set password,  SSID. It is possible to edit this file with any HEX editor you prefer. No any checksums inside, only plain data.
• It is not necessary to close opened software if you wish to open another one, just click on globe to release adapter.  
•  Some basics about component status flags:

• Initialized - all components we can use are already initialized at the final stage of production. Otherwise they are not usable.
• TP (transport protection)  - must release TP to continue
• Personalized - FBS3 data are written into component
• Activated - component is installed into car and works.

It isn’t valid that component is ACTIVATED, but flag PERSONALIZED isn’t set. In addition there are SPARE PART and NEUTRALIZED flags too:

• SPARE PART - component is initialized for spare part, some additional data written inside (AUTH PW) to allow to personalize it only by authorized people. Otherwise component is SERIES.
• NEUTRALIZED - component was unlocked at least once.