The way I do it is to check a password stored in the EEPROM against a password stored and hidden in the flash using a custom routine. Most of the cars I tune (Volvo) erase the password in the EEPROM if it does not match what is stored in the paired module on the car. That way, even with an immo delete performed and the previous EEPROM copied into a new car, the passcodes do not match since one is correct and one is blank and the custom routine prevents start. For a car that doesn't perform the password erase, I would try looking at the immo check routine and code a routine to check the code against the immo directly, instead of checking what is stored in EEPROM. Either way, the bottom line is, even with all of this, the routines can still be disabled the same way they were added. The point of this is to stop people from mindlessly copying tune files from one vehicle to another. If someone is good enough to hack and disable these security routines, odds are they wouldn't need to be mindlessly copying files, IMO.

True, that is why I obscure my code with randomly generated bytes and also move the important maps into a mess of stuff. Again, any good tuner can probably get through it, but then again, any good tuner probably isn't copying.

Look what i found.. pro work