1. you can not boot the ecu using nefmoto, you need galletto, chiploader or mpps or ktag
http://nefariousmotorsports.com/forum/index.php?topic=3088.0
http://nefariousmotorsports.com/forum/index.php?;topic=19922.0
2. you can try to crossflash but you should aim for a ecu which has two lambdas where the precat lambda is wideband
i am not familiar with us market me7.5 engine codes but in europe you would use aum, auq, bam, amk and maybe some a4 ecus to crossflash between them

good start by the way, nice first post

Thanks for the links. I think/hope I won't been to bootmode flash yet but I did grab galletto and set it up when I was initially researching. Mostly just lazy and don't want to make to hack together a power supply and bench cable for this first test. Looks like I'll want to work on that though for getting a spare ECU functional.


Thanks for the tips. Immo off doesn't look too hard and I only have one key right now so not a bad thing to work on anyways... buying the rfid things to get more immo-approved keys is a pita. Will need to work on building a bench rig but other than that, simple enough to get a spare ecu. Nobody's capable of driving stick here in the US anyways so theft potential is low, immo or not!

I guess I still don't fully understand what the definition files actually do. To me it seems like without a definition file then you just don't know what address/offset in the BIN corresponds to anything, so editing would be completely blind. But with a definition file you've mapped the BIN where an offset you now have claimed corresponds to something (say, a table like MSLUB, which is at offset 00010C20) to make editing much easier. I guess if the map was wrong for the BIN then certain address spaces would be opened based on what the map says and that data would not be in the correct offset location, so you'd inadvertently modify something you didn't mean to? Do I understand that correctly?

I ran a diff on my original CJ bin versus an original BB bin that was provided in the thread with the definition map I'm using. There's a few differences in the raw hex (primarily confined to one continuous address space, where the data is the same but my bin starts with three additional bytes, so it's all slightly shifted, and then shifts more later) but mostly looks the same. Also ran a diff on my stock bin versus the one I modified (before checksum fixes) and the only differences are bytes I have record of modifying from my screenshots... so even though it's probably not a great map for major changes, at least the changes I have are safe. Will flash it back today or tomorrow, fingers crossed all goes well. If not, well, at least it's not my daily.

Looking into it more it seems like BB was for BEA (225hp) TT's from 2003 and CJ is for BEA (225hp) TT's from 2004, but there's no record of any model year differences I can find for those years, all BEA is wideband etc etc... 2004 they started offering a DSG automatic with a VR6 but obviously that has no effect on 1.8T models... wonder if I could just get away with flashing the BB stock bin and running the car off that as a base flash. The map I have is really nicely defined... oh well, something to play around with once I can get a spare ECU, I guess!

This sums it up exactly.  It's like an encyclopedia with a contents page that suits only that encyclopedia.  Try and look up fuel in another authors one on the same page won't take you to fuel...

WinOLS is good for comparisons and lining up files to compare against.  Remember that everyone is a noob at some stage - so just because a thread here says "I used this def on this file and it's fine" doesn't mean they know what they're doing...

If I can offer any advice, get a bench harness and a spare ECU - clone your existing ECU (read immo with Argdubs tool in OBD mode) and then write it to your spare, in bootmode, on the bench.  Get used to it.  You WILL need it at some stage, and it's good to have the skill now, rather than trying to develop it in the rain at 2am 100 miles from home.

We can't discuss cloned versions but I knew a mate that ran 2.24 on Windows 10.