I have used this on many ecu's with no issues. Make sure to use the 7.1.1 file if you don't have an me7.1/7.5 ecu.

I flashed this immo off .bin and got rid of the "immo not authenticated" error msg in Nef but I still get that the ECU has rejected security access and it won't let me go through with the reading or writing. What am I missing here?

This is for an HSbox that looks as if it had an LP file flashed to it from the dealer. I heard they do this now because the HS software has been superseded. I don't see how this should matter though.

Just to confirm.

Would i flash this bin as normal (bootmode + galletto)

If i then flash a file onto the car will it not put the immo back on if that bin file hasnt had immo off???

The convention on this site is:
- Flash - where the maps go (512kb or 1024kb)
- eeprom - where the immo data goes (512 or 1024bytes - i.e. 1024x smaller than the flash).

The immo bin on this page is for the eeprom, which is different from the flash where the maps are stored. You are correct, that you should use argdub's me7_95040 tool to write the eeprom.

However, I would always read the eeprom contents from the ecu, modify it for immo-off, and then write it back, rather than writing a generic immo-off.

7.1 and 7.5 seem to be the same, 7.1.1 is slightly different.

I usually use my tool to do immo off, because I can never remember how to set the checksum properly, but its super easy with a hex editor too. http://nefariousmotorsports.com/forum/index.php?topic=6134.15

As I did to a spare ecu this morning:

1. Read from ECU. (me7_95040 --OBD -r -p 1 eeprom.bin)

2. view info (eepromtool --in eeprom.bin)

3. turn off immo (eepromtool --in eeprom.bin --out eeprom_off.bin --immo off)

4. write back to ecu in boot mode (me7_95040 --bootmode -w -p 1 eeprom_off.bin)

took about 10 minutes. If you get a complaint about a checksum error on a virgin eeprom that you've just read from a virgin/working ecu, please post up on the thread for the tool.