|
| 1 | +# UnlockECU |
| 2 | + |
| 3 | + |
| 4 | + |
| 5 | +Free, open-source ECU seed-key unlocking tool. |
| 6 | + |
| 7 | +## Getting started |
| 8 | + |
| 9 | +Download and unarchive the application from the [Releases](https://github.com/jglim/UnlockECU/releases/) page, then run the main application `VisualUnlockECU.exe`. |
| 10 | + |
| 11 | +Ensure that you have *.NET Desktop Runtime 5.0.0*. , available from [here](https://dotnet.microsoft.com/download/dotnet/5.0). |
| 12 | + |
| 13 | +## License |
| 14 | + |
| 15 | +MIT |
| 16 | + |
| 17 | +Icon from [http://www.famfamfam.com/lab/icons/silk/](http://www.famfamfam.com/lab/icons/silk/) |
| 18 | + |
| 19 | +Excluding the icon, this application **does not include or require copyrighted or proprietary files**. Security functions and definitions have been reverse-engineered and reimplemented. |
| 20 | + |
| 21 | +*When interacting with this repository (PR, issues, comments), please avoid including copyrighted/proprietary files, as they will be removed without notice.* |
| 22 | + |
| 23 | +## Features |
| 24 | + |
| 25 | +- There is no need for additional files such as security DLLs. The application supports a set of security providers out of the box, and definitions are stored in `db.json`. |
| 26 | +- Security functions are completely reverse engineered and re-implemented in C#. |
| 27 | +- The project is unencumbered by proprietary binary blobs, and can be shared freely without legal issues. |
| 28 | + |
| 29 | +## Demo |
| 30 | + |
| 31 | + |
| 32 | + |
| 33 | +## Adding definitions |
| 34 | + |
| 35 | +Definitions specify a seed-key function for a specific ECU and security level. The input seed's size, output key's length as well as the security provider must be specified. Some security providers require specific parameters to operate. |
| 36 | + |
| 37 | +Here is an example of a definition: |
| 38 | + |
| 39 | +``` |
| 40 | +{ |
| 41 | + "EcuName": "ME97", |
| 42 | + "AccessLevel": 5, |
| 43 | + "SeedLength": 2, |
| 44 | + "KeyLength": 2, |
| 45 | + "Provider": "PowertrainBoschContiSecurityAlgo2", |
| 46 | + "Origin": "ME97_ME97_13_10_01", |
| 47 | + "Parameters": [ |
| 48 | + { |
| 49 | + "Key": "Table", |
| 50 | + "Value": "37C1A8179AE3745B", |
| 51 | + "DataType": "ByteArray" |
| 52 | + }, |
| 53 | + { |
| 54 | + "Key": "uwMasc", |
| 55 | + "Value": "4108", |
| 56 | + "DataType": "ByteArray" |
| 57 | + } |
| 58 | + ] |
| 59 | + } |
| 60 | +``` |
| 61 | + |
| 62 | +Currently, these security providers are available: |
| 63 | + |
| 64 | +- DaimlerStandardSecurityAlgo |
| 65 | +- DaimlerStandardSecurityAlgoMod |
| 66 | +- DaimlerStandardSecurityAlgoRefG |
| 67 | +- DRVU_PROF |
| 68 | +- EDIFF290 |
| 69 | +- EsLibEd25519 |
| 70 | +- ESPSecurityAlgoLevel1 |
| 71 | +- MarquardtSecurityAlgo |
| 72 | +- OCM172 |
| 73 | +- PowertrainBoschContiSecurityAlgo1 |
| 74 | +- PowertrainBoschContiSecurityAlgo2 |
| 75 | +- PowertrainDelphiSecurityAlgo |
| 76 | +- PowertrainSecurityAlgo |
| 77 | +- PowertrainSecurityAlgo2 |
| 78 | +- PowertrainSecurityAlgoNFZ |
| 79 | +- RBTM |
| 80 | +- RDU222 |
| 81 | +- RVC222_MPC222_FCW246_LRR3 |
| 82 | +- SWSP177 |
| 83 | + |
| 84 | +The definitions file `db.json` should be found alongside the application's main binary. |
| 85 | + |
| 86 | +## Notes |
| 87 | + |
| 88 | +- If your diagnostics file has unlocking capabilities, usually your diagnostics client can already perform the unlocking without further aid. Check your client's available functions for phrases such as `Entriegeln` , `Zugriffberechtigung` , and `Unlock`. |
| 89 | +- Generally, this application operates like most DLL-based seed-key generators. If you already have a DLL-based tool, this application does not offer much more (only includes a few modern targets such as `HU7`). |
| 90 | +- Definitions are reverse-engineered from DLLs and SMR-D files. If the definition does not innately exist in those files, they will not be available here (e.g. high-level instrument cluster definitions). |
| 91 | +- There are ECUs that share the same seed-key function. For example, `CRD3` and `CRD3S2` appear to share the same function as `CRD3NFZ`. |
| 92 | +- The core of this project is a "portable" .NET 5 class library which can be reused on other platforms. |
| 93 | +- As the security providers are now written in a high-level language, they can be better studied. For example, `DaimlerStandardSecurityAlgo` performs a XOR with its private key as a final step, which allows the private key to be recovered from a known seed and key. |
| 94 | +- `DaimlerStandardSecurityAlgo` is usually used for firmware flashing, and might not unlock other capabilities such as variant-coding. |
| 95 | + |
| 96 | +## Contributing |
| 97 | + |
| 98 | +Contributions in adding security providers and definitions are welcome. |
0 commit comments