bri3d / VW_Flash

Flashing tools for VW AG control units over UDS. Compression, encryption, RSA bypass, and checksums are supported for Simos18.1/6/10, DQ250-MQB, DQ381-MQB, and Haldex4Motion-Gen5-MQB.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Unlock gone wrong

opened this issue · comments

flash.log
flash_details.log
udsoncan.log

we are following the steps https://github.com/bri3d/VW_Flash/blob/master/docs/windows.md

we find ourselves stuck at not seeing"H13" to "X13"

We can no longer start the car or revert back to stock.

It looks like you did a normal full flash of the 8V0906259H file, NOT an "unlock" flash. As a result, the ecu is now immo bricked and will need to be opened and recovered via bench.

is there no way to recovery via VW_Flash?

Unfortunately not, I did the same thing to my own ECU once.

in the log i see the following line "2023-01-23 20:24:47 [INFO] FlashUtils: Patching CBOOT into Sample Mode."
and the result is 8V0906259H this is correct.
but did you do this task in the "file" menu with "unlock ecu"?

Sorry this happened to you.

You must unlock using File->Unlock ECU, or you risk an immobilizer brick.

You must be very careful to never flash a calibration with an ImoDat which does not match your car's PClass. IMO this is a bug in VW's immobilizer system but it cannot be bypassed besides by using boot flashing - once the PClass array in the calibration does not match the one stored in your immobilizer data, the car will not enter a programming session.