Pages: [1]
Author Topic: Golf V 2.0 TDI BKD EDC16 ODIS-E Flash Fail  (Read 1708 times)
cgentil
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 3


« on: June 17, 2024, 05:45:27 AM »

Hello All,


I hope someone can help me.


Today I tried to flash with an update SW Golf V 2.0 TDI BKD EDC16 with ODIS-E.


The current SW is 03G 906 016 AP - 5876


The update SW is 03G 997 012 E - 4163


The flash itself gave an error, and PRNDS start flashing, fans running an car doesn't start.


It is exactly the same thing as below:


https://mhhauto.com/Thread-original-BDM-dump-03g997012E


https://mhhauto.com/Thread-original-BDM-dump-03g997012E?pid=890833#pid890833 - a user was able to recover it with VASPC.


Now the thing is. What went wrong?


I have original .bin file with Kess (I did a backup before flash), however it always returns Wakeup error when trying to put original file.


My question is, someone with online ODIS-S connection to VW Servers, will be able to restore all to normal and update all needed ECU's (engine and DSG also?)


This is the error I got.



I have K-LINE and CAN connection aswell.


Thank you in advance.
Logged
prj
Hero Member
*****

Karma: +1072/-481
Offline Offline

Posts: 6035


« Reply #1 on: June 17, 2024, 02:43:57 PM »

Chances are ECU was tuned and someone changed encryption key or signature via BDM.
ABT ecu's came like that and some others.

Result was that any OBD flash would brick the ECU.

In this case only chance is to do the whole thing via BDM (or if you have non-clone tools then bench mode), overlay all the new blocks at the correct addresses.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
dynamikmotors
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 1


« Reply #2 on: August 04, 2024, 05:38:21 AM »

Hello All,


I hope someone can help me.


Today I tried to flash with an update SW Golf V 2.0 TDI BKD EDC16 with ODIS-E.

Hi, ODIS-E only flashes sgo and frf file formats. If you want to flash bin files in an audi you will have to use something like KTAG ( diagnostic tool).
The current SW is 03G 906 016 AP - 5876


The update SW is 03G 997 012 E - 4163


The flash itself gave an error, and PRNDS start flashing, fans running an car doesn't start.


It is exactly the same thing as below:


https://mhhauto.com/Thread-original-BDM-dump-03g997012E


https://mhhauto.com/Thread-original-BDM-dump-03g997012E?pid=890833#pid890833 - a user was able to recover it with VASPC.


Now the thing is. What went wrong?


I have original .bin file with Kess (I did a backup before flash), however it always returns Wakeup error when trying to put original file.


My question is, someone with online ODIS-S connection to VW Servers, will be able to restore all to normal and update all needed ECU's (engine and DSG also?)


This is the error I got.



I have K-LINE and CAN connection aswell.


Thank you in advance.
Logged
_nameless
Hero Member
*****

Karma: +342/-466
Offline Offline

Posts: 2802



« Reply #3 on: August 04, 2024, 08:01:16 AM »

Chances are ECU was tuned and someone changed encryption key or signature via BDM.
ABT ecu's came like that and some others.

Result was that any OBD flash would brick the ECU.

In this case only chance is to do the whole thing via BDM (or if you have non-clone tools then bench mode), overlay all the new blocks at the correct addresses.
They have a few clone tools that do service mode now too
Logged

Giving your mom a tuneup
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.017 seconds with 15 queries. (Pretty URLs adds 0s, 0q)