MED17 VW Immo data edit

[g5n14]

Hello guys!

Have one car here, old ecu is completely gone, no com to any tool. (car after a lightning strike)

I have read out the flash+eeprom from MED17.5.25, but my VVDI2 MED17 dump editor doesnt support editing immo data in this ECU (flash 2560 sized).
I also read out dashboard immo data with VVDI2, could someone please transfer the immo data from dashboard to MED17? Attached is ECU dumps + immo data from dash (both as bin VVDI2 and trasfered to txt).

Huge thanks in advance!

[brend]

Ecu configuration is immo 6.
Only online away.

[g5n14]

Ecu configuration is immo 6.
Only geko or diller.

Kinda confused. So what does that mean? What should I do?

[g5n14]

Ecu configuration is immo 6.
Only online away.

New ECU is number to number with ori.

[ghitab]

Read sync data from key and post.

[avital]

Ecu configuration is immo 6.
Only online away.
Not is true ...

For topic starter - upload here 32 bytes sync_key.

[g5n14]

Thanks a lot for the replies!

Where can I read sync_key from?

[avital]

From working key

[g5n14]

From working key
Thanks! Can't find anything other than 7th byte from working key in my VVDI2 software

[g5n14]

By some manipulatiouns succeeded to read sync data, here it is

[avital]

first try add immodata from MQB immo block to Your ECU, pass on PM - additional question You have CANBUS analyzer ?
For now You must write new eeprom and moded flash (not forget about fix crc when upload to ECU)

[g5n14]

first try add immodata from MQB immo block to Your ECU, pass on PM - additional question You have CANBUS analyzer ?
For now You must write new eeprom and moded flash (not forget about fix crc when upload to ECU)

Yes i have linux machine with CAN bus libraries and CAN analyzer interface.
Thanks a lot will test ASAP!

[g5n14]

first try add immodata from MQB immo block to Your ECU, pass on PM - additional question You have CANBUS analyzer ?
For now You must write new eeprom and moded flash (not forget about fix crc when upload to ECU)

Well, looks like its gonna start. No SAFE on dash, it cranks. But a lot of errors. Sensor reference voltage B error, fuel pump module short to ground. And 7 more not so important (car is after lightining hit so i am not surprised at all. MANY MANY modules fried totally)

One question left. Now it thinks its DSG car, when i try to code it with VCDS it says request out of range, do i need the PIN or what? It rejected the dash pin. Do you know the right one?

HUGE THANKS MAN! Looks like immo is intact now.

[avital]

Yes as i only fiddled with immobilizer data but your ECU is from a different fairy tale :) ... even the ECU had a different power class ... but I fixed this little problem :)

For posterity :) -> information I did it all with the software: VAG IMMO CALCULATOR which is completely OFF-LINE.

Let me show you in a few steps how I did it (matching the ECU to the MQB dashboard)



1 - imported 189 bytes immo data and 32 bytes sync_key from MQB DASHBOARD to MQB editor immo data, and I maked special immo block for ECU,( is possible also for TCU or ELV from WFS5/WFS5+/WFS6/MQB immo systems )

754698

2 - imported and analyze files from ECU ME17.5.25 WFS6/MQB to MEDC17 editor ... and wow i see power class in dash and inside ECU is different...

754699

3 - imported flash file from ECU to MEDC17 Power class editor for change power class (Yes it is possible by good tool ;) ) and save moded FLASH file.

754705

4 - imported special immo block from MQB editor module to ME17 and saved new eeprom file, is the end operation, not is needed any ONLINE immobilizer coding.

[brend]

Not is true ...

For topic starter - upload here 32 bytes sync_key.


Are you sure?

[g5n14]

Yes as i only fiddled with immobilizer data but your ECU is from a different fairy tale :) ... even the ECU had a different power class ... but I fixed this little problem :)

For posterity :) -> information I did it all with the software: VAG IMMO CALCULATOR which is completely OFF-LINE.

Let me show you in a few steps how I did it (matching the ECU to the MQB dashboard)



1 - imported 189 bytes immo data and 32 bytes sync_key from MQB DASHBOARD to MQB editor immo data, and I maked special immo block for ECU,( is possible also for TCU or ELV from WFS5/WFS5+/WFS6/MQB immo systems )

754698

2 - imported and analyze files from ECU ME17.5.25 WFS6/MQB to MEDC17 editor ... and wow i see power class in dash and inside ECU is different...

754699

3 - imported flash file from ECU to MEDC17 Power class editor for change power class (Yes it is possible by good tool ;) ) and save moded FLASH file.

754705

4 - imported special immo block from MQB editor module to ME17 and saved new eeprom file, is the end operation, not is needed any ONLINE immobilizer coding.

Very informative, thanks a lot. Great work, appreciate it! Is it software developed by you?
Do you have any idea why ECU now is not accepting the coding?
Really need to make it manual again, but i dont know PIN.

[g5n14]

Yes as i only fiddled with immobilizer data but your ECU is from a different fairy tale :) ... even the ECU had a different power class ... but I fixed this little problem :)

For posterity :) -> information I did it all with the software: VAG IMMO CALCULATOR which is completely OFF-LINE.

Let me show you in a few steps how I did it (matching the ECU to the MQB dashboard)



1 - imported 189 bytes immo data and 32 bytes sync_key from MQB DASHBOARD to MQB editor immo data, and I maked special immo block for ECU,( is possible also for TCU or ELV from WFS5/WFS5+/WFS6/MQB immo systems )

754698

2 - imported and analyze files from ECU ME17.5.25 WFS6/MQB to MEDC17 editor ... and wow i see power class in dash and inside ECU is different...

754699

3 - imported flash file from ECU to MEDC17 Power class editor for change power class (Yes it is possible by good tool ;) ) and save moded FLASH file.

754705

4 - imported special immo block from MQB editor module to ME17 and saved new eeprom file, is the end operation, not is needed any ONLINE immobilizer coding.


Thanks a lot man! Great work, appreciate it! Is this software developed by you?
I have now problems coding it, no idea why it just rejects the coding attempts.
Maybe i need the pin for coding? Or what is the security pass for this MQB vehicles to enable VCDS coding?
If you need some help with CAN analyzing smth i can do it just DM me.

[ghitab]

If your car is dsg must flash correct sw to your engine. 04E906027LH is from fabia/rapid/ibiza/toledo(some flash not have auto part so codding is rejected) . Try reflash to 04E906027CJ from golf(CYVB). Post full scan of car for better analyze.

[g5n14]

If your car is dsg must flash correct sw to your engine. 04E906027LH is from fabia/rapid/ibiza/toledo(some flash not have auto part so codding is rejected) . Try reflash to 04E906027CJ from golf(CYVB). Post full scan of car for better analyze.

Thanks for your reply!
Both ECUs old and new one are 100% number to number, only serial and man date differs. I can post photos. But yeah, seems that you are right since it doesn’t accept coding, maybe donor ECU was already used in another car and reflashed at some point or smth.

[g5n14]

If your car is dsg must flash correct sw to your engine. 04E906027LH is from fabia/rapid/ibiza/toledo(some flash not have auto part so codding is rejected) . Try reflash to 04E906027CJ from golf(CYVB). Post full scan of car for better analyze.

I am home already, will post auto scan tomorrow

[g5n14]

Full Auto Scan is uploaded to this message.

ORI ECU numbers:
04E 907 309 AF HW:21
0 261 S09 531

DONOR ECU numbers:
04E 907 309 AF HW: 23
0 261 S09 531


So only the HW is the difference.

[g5n14]

If your car is dsg must flash correct sw to your engine. 04E906027LH is from fabia/rapid/ibiza/toledo(some flash not have auto part so codding is rejected) . Try reflash to 04E906027CJ from golf(CYVB). Post full scan of car for better analyze.

Here is autoscan

[g5n14]

If your car is dsg must flash correct sw to your engine. 04E906027LH is from fabia/rapid/ibiza/toledo(some flash not have auto part so codding is rejected) . Try reflash to 04E906027CJ from golf(CYVB). Post full scan of car for better analyze.

And my car is MANUAL, but ECU is DSG.

[ghitab]

Check what engine code you have? I think CYVB, if this type then try update by .frf to this version 04E906027GR and aftre code for manual.
On ecu label you see only hw number, but sw can be many version. In engine log I see you have short on reference B, try unplug some sensors until you find the faulty one.
As for other non reply modules need to check if dead or some supply voltage missing, you will have some work with this car...

[avital]

You should listen to him :), if - He (user Ghitab) did not help me , MQB module "synchronization" for software VAG IMMO CALCULATOR - it would be created a few months later with much more effort :)

[g5n14]

Thanks a lot for your help. It is CYVB.
I will try to find this frf To flash it tomorrow.

Almost all modules in this car were not replying when it’s brought. Car didn’t even give ignition until New BCM was fitted. Car was hit with lightning in the right side mirror. ECU dead no com, BCM dead no com. Same a lot of modules. Only CAN gateaway and dashboard got away from lightning.

BUT! That is not a question. That’s all a quick fix, I’ll just replace them once it starts.

Yeah. It’s CYVB. It doesn’t start because of many reasons. Sensors circuit B(most probably 60-70% of sensors are damaged), also fuel pump module burned by lighting. But also not a question, will handle that later, once i would be able to code It back to manual and make sure that’s set.

[g5n14]

Tried flashing FRF over OBD with VVDI2, it says "immo active, insert valid key". I think its just an error because VVDI doesnt support this kind of ECU, already had problems with it previously. Waiting for activation of PCMflash module 48 and then will write the FRF which ghitab mentioned.

Thanks once again.

[g5n14]

Activated module 48. But now when i make VR ofcourse i see only files for the same SW i have. Does someone have 2560KB file for 04E906027GR SW?

[ghitab]

Try flashing by odis or VCP. As Avital said before do you have can logger to check message dash-ecu?

[g5n14]

Try flashing by odis or VCP. As Avital said before do you have can logger to check message dash-ecu?
Hi! Yeah, i have can logger with linux machine, but i hope we can manage without it.
Before avital helped me to transfer data i had SAFE on dash, now its not here so i think we dont have any problems with that.

PCMflash support provided me the OBD VR file, but controller refused to be written by OBD. After that support just made a bench file for me with the SW you mentioned (I was really surprised with that level of support), i am writing it to ECU right now when typing all that.

Will report after i install the ECU back and try to code it for manual gearbox.

[g5n14]

Solved. File provided by PCMflash support did the trick. Succesfull written, connected to the car, recoded to manual transmission first try.

HUGE THANKS TO EVERYONE HELPING IN THIS TOPIC, YOU HELPED A LOT! ESPECIALLY TO USERS AVITAL AND GHITAB!

Will keep the topic updated about this car. Will try to figure out now which sensors are damaged and so so on.
But considering ECU pairing, i am pretty sure the job is done and i will not get back to it.

[RomanNng]

please tell me how did you read the sync file from the working key in vvdi2? ) I have the same problem, Russian terrorists stole ECU from the car.