-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unlock gone wrong #86
Comments
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." |
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. |
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.
The text was updated successfully, but these errors were encountered: