NefMoto

I want to understand how immo works in VAG cars with transverse TFSIs (MED9.1).

Specifically, why doesn't my car start if I take the ecu from another car and swap just the eeprom data? The engines are the same (CDL) as well as the ECU's (8P0907115B).

Search for cross flashing med9, you will find a thread with a full description on why

Most often the powerclass and brand are stored on the flash of the ecu. And these are part of the immo authentication algorithm.

If you are able to (cross) flash it to a version with correct brand and powerclass then swapping eeproms should be sufficient.


Rgs H2Deetoo

MED9.1 from these cars are with crypted immo in eeprom. There is a unique part in flash (should be 6C00 - 6CFF) which is important to copy too.

Okay, so I've tried this so far:
1. Transferring the crypto data in the flash address 06C00-06CFF
2. Additionally modify the flash so that immo software version matches the eeprom
3. Modifying eeprom software version to match that of the flash

Nothing worked, as dash kept displaying "immobilizer active" each time.

Is there anything else that could be done without turning off immo?

The car is mk6 R (CRZ engine) and the donor is MK2 TTS (CDL engine).

Take the old ECU, make a full read, and write the full read into the new ECU. And done.

Why are you screwing around with it?

I swapped over the OEM TT-S intake together with MAF. My engine bay has to look stock to pass the inspection

In that case just adjust OR pay someone to adjust software in your old ECU.
What you're doing now is retarded.

Well a local tuner just returned my car unable to adjust the software, so I'm not sure what to do now. Custom Maf housing + original Maf + rescale?

Why is the software swap "retarded"? It's the same engine sans MAF.

Find someone normal, who is not completely clueless.

It's literally ctrl+c ctrl+v 2 maps in the sw.

And it's retarded exactly for the reason of having to fuck with immo. Not to mention buying a whole damn ECU for something that takes a competent person 15 minutes!
This thread here is a perfect example of the XY problem (https://xyproblem.info/).
Thanks for wasting everyone's time.

I figured the two maps you meant are KFKHFM (correction factor for HFM) and MSHFMTPH (massflow as a function of period). So I transferred them from a TTS binary. And it worked: the car starts and idles just fine, the MAF reading reacts to throttle and I get no implausible signal DTCs.

However, what worries me and what is the entire reason I chose the "retarded" approach, is this little bit from the wiring diagram of TT-S:

(https://i.imgur.com/RU5vNA6.png)

TT-S MAF uses 4 wires, as opposed to 3 wires in 6R. The extra wire on the TT-S version goes to pin 42, which is likely "Sekundärluftrückmeldung (Min HFM)" (as per MED9 FR). I tried searching the FR for it, but the only hit is the pin out section. I'm guessing the extra wire isn't the temperature correction signal  ???

Also, it turns out the immo fix is really easy, just 4 bytes. However, the real problem seems to be CAN coding, because even though TTS software allows the car to start and run fine, I get U0146 DTC.

This is not needed on the Golf R software. You're done.
And the extra wire is most likely the temp sensor.

And of course the Audi software won't work, the CAN Matrix is different.
As I said, retarded. For many more reasons than I gave you.

its very simple you are use tts sw need mod can data and wfs other wise not working fine
not really big work
and working immo all other funkction

simple copy binary and immo  data not work different brand

Have you had success in modifying the CAN settings?