Engine Control Unit (ECU) No Communication After VW Update

Hello!
I'm not sure if this is the right place for this, but I'll give it a try.
Today, I took my Golf 6 GTD (manufactured in 2010) to VW, and they found that there is a software update available for the engine control unit.
After I gave my consent, they wanted to proceed. The update started, and after a short time, the technician said the update failed. Since then, nothing works. The engine control unit no longer communicates, and there are still numerous other errors in the memory. Can anyone here tell me what happened? Did VW corrupt the software on my control unit during the update? VW is currently trying to figure out what to do with the factory, because they've run out of ideas!
Disconnecting the battery for 15 minutes didn't help either.

Well,

broken, new - ready - and I would say, completely free of charge for you.

Wie schreibst du in diesem Forum ? With a computer.
You've probably installed something before.
And if, for ANY reason, only half of it was played, it's worthless afterward.

Since the engine control unit (ECU) doesn't have a removable hard drive that can be taken out and formatted in another ECU, that was the issue. A new one needs to be installed.

That's my perspective.

m;

Okay, you don't need to explain to me how flashing an EEPROM works, etc. I'm an electrician by profession, so I'm quite familiar with the subject. I deal with firmware updates every day in my job, although in a different area than automotive. However, with our devices, there's something like a CRC check, so if an update is only halfway through and then interrupted, I can re-flash it and the device won't be immediately ruined!

Then they probably managed to do it anyway. Or maybe the bootloader was updated at the same time .

Hello,

What firmware was installed previously?

The update was from 6150 to 6650, although I don't remember the exact numbers anymore, it was something like that! At least, that's what the tester said!

Then the GTD is already a few months old?
Mine arrived in late April 2010 already with the 6655 version.

"Contact the dealer to resolve this issue. He's the one who messed it up in the first place. Have you been provided with a rental car?"

No, I didn't need a rental car. In theory, I probably would have been entitled to one, but I don't think so. Hmm, my car was first registered on March 20, 2010!

slg60 wrote:

No, I didn't need a rental car, although theoretically, I probably would have been entitled to one, or?! Hmm, my car was first registered on March 20, 2010!

If the dealer convinced you to get an update, and as a result, your vehicle is now malfunctioning, I would expect that. Otherwise, the situation might have been different if you had explicitly requested the update - but even then, the car should not be rendered unusable. However, there might have been more discussions .

I think that WOB will find a way for the dealer to completely re-flash the STG.

I see this as analogous to the broken windshield that my dealer damaged in 1997 while replacing the wipers on my G III GTI. They replaced the windshield at their own expense, and the loaner car was extended for an extra day free of charge.

I just checked again, and mine was updated to version 6175, which I think should be updated to 6655 or something like that. It seems they released an update shortly after mine was manufactured!

Well, he didn't do it on his own; I asked him to check if there were any software updates available for the control unit. He also asked me if I wanted it done. I agreed, but even then, it still had to run afterwards.

I haven't experienced this with an EDC17 before, but I have with an EDC16.

It failed three times in a row, but on the fourth attempt, it finally worked. However, I then flashed it using the built-in diagnostic tool.

I'm not sure if there's still a K-line available on the EDC17. If there is, try disconnecting the CAN Hi and Lo lines at the diagnostic connector and then try flashing it again.

If it's truly impossible to flash the device normally and they are reluctant to pay for it, then inquire with a tuner to see if they can flash it in "boot mode," provided it's not a VDO Continental control unit, as I understand that's not yet possible.

It's a Bosch engine control unit, and I don't think they'll refuse to pay. I just don't want them to have to take my entire car apart. They rarely put things back together the way they were originally!

chli1976 wrote:

I'm not entirely sure if there's still a K-line on EDC17, but if there is, then you should disconnect the CAN Hi and Lo lines at the diagnostic connector and try flashing it again.

I'm quite sure that VCDS reports K1/K2 and CAN as present when testing this model...

Okay, so tomorrow morning a new MSTG (Multi-Stage Turbine Generator) will be installed, let's see if it then starts working again. I could have clearly answered "yes" to the question of whether a new one was needed from the very first day!
No words needed!

Okay, it's working again now. I've also updated to version 6655. It drives noticeably differently now, but not necessarily in a negative way. It's a subjective impression! There was also a shift recommendation in the MFA+ system, although I'm not sure what it has to do with the MSTG (presumably a specific system or feature), but it must be the case, otherwise I wouldn't have it!