NefMoto

I'm not really sure how to phrase this question, so I'll just throw it out there with as much detail as possible.  Sorry if it's not described in a technically correct manner.  I have a 2000 B5 S4.  The car was originally Canadian, but was 'Americanized' (fog lights added, instrument cluster replaced).  The ECU was physically altered/flashed by APR 10+ yrs ago, but now is evidently dead and cannot be repaired or reverted to stock.  The ECU currently in the car is 8D0907551H.  A friend of mine sent me a used ECU from an A6 (I believe) along with what he called an H-box file.  The ECU he sent is 4B0907551P.  He said the ECU he sent can be flashed to mimic/replace my dead one, and that immobilizer would need to be disabled, although he had never done either himself.  If the hardware in the ECUs is the same, I would assume this is possible, but would this be a straight forward flash in the car, or would it have to be done with the ECU out of the car and/or in 'boot mode'.  I have no idea what that mode is, I just saw it in a few discussions when I was looking for anything similar to what I'm trying to do.  Right now, I'm just trying to get the car started and then go from there.  Thanks.

Not too sure on S4's but generally speaking it is very easy to adapt the immobilizer on ME7 using VCDS

Otherwise you'll need bootmode yes, there are countless topics on it and is very easy.

8D0907551H and M are compatible. If you flash the 8d0907551M to your new ECU that will take care of your immo issue as that software version does not have immo. Best bet is to bootmode flash the ecu specially when cross flashing software versions. Lucky for you you will not need to mess with the eeprom as long as you use the m version. Best of luck.

So you're saying that the H-file (software) I have, has the immobilizer enabled/present, and would require an extra step(s) to disable/remove it by 'messing with the eeprom' (which I definitely know nothing about), but if I can get an M-file, I will be able to flash the 'new' ECU and avoid having to worry about the immobilizer?

neither H or M have immo, but prefer M since it has full definitions and well understood.

Thanks for the info.  By 'has full definitions', do you mean the descriptions for each 'setting', or the actual number/totality of the settings?  I poked around on this site and found an example of someone who was trying to modify an existing def file to make it more complete.  Are these xdf files akin to the .inf files that accompany windows drivers? 

Here's the link to the example:   http://nefariousmotorsports.com/forum/index.php?topic=17979.0

His collection contains an xml file (not sure of it's purpose), a definition file and the bin file.  If I have a bin file, I assume I also need the corresponding def and xml files?  I found 8D0907551M-0001.bin and 8D0907551M-0002.bin on s4wiki.com/stock.  How can I determine the differences between the two (which one to try)?  On the same site, in the defs directory, there are several files that appear to be used with an M bin file.  What is the purpose of the csv and kp files and do these files go with a specific bin file?

Locations for maps in the flash


Not even remotely applicable. There is pretty much nothing from windows that is even remotely related. Windows knowledge is totally useless.


You need a xdf or .kp (or full ols). No clue what that post is, it seems useless.


For mapping purposes, the are the same. If you are doing ASM changes, no.


.kps are mappacks for winols (analogous to .xdf for tuner pro)

.csvs are just there for people who want locations in a portable/universal format.

Thanks for the help.  I was finally able to get the ECU flashed.  The car now runs :)  All i have to do now is get a new tune.  Thanks again!