Kukunin
Newbie
Karma: +1/-2
Offline
Posts: 20
|
|
« on: July 15, 2018, 04:42:10 AM »
|
|
|
Good day. I decided to spend more time for my car, and get into the tuning process =)
History of my ECU is unclear, the previous owner said he has chipped the car, I chipped the car at unnamed car service (it was just a chip, no tests before/after etc). So I decided to start from a clean state.
My car is New Beetle 2003, 1.8t, Mexico. I have Immo III. My ECU was 06A906032KQ (this is what ECU returned, I haven't look on the ECU in real). I couldn't find an original firmware exactly for my ECU, but using the analogs thread, I found an original firmware for similar ECU: 06A906032FD.
Yesterday, I flashed it with MPPS via OBD, and the car stopped to start. Although it starts but stops in a second later. I get a single DTC error:
17978 engine start blocked by Immobilizer
I wonder why it stopped working since my EEPROM ImmoID and SKC remain the same. The immo light is blinking on the dash.
I started to move forward: I got to recover the SKC key. I dumped my EEPROM with me7_95040 and found my SKC. I'm able to login to the Immo with that code (17-Instrumental), but not to ECU (01-Engine): it disconnects no matter how many times I tried (yes, I did 2-3 minutes intervals).
Currently, I can't flash any other firmware with MPPS via OBD, it returns an error. My guess is because of the immo.
Here are screenshots from VCDS, the strange things that ECU knows nothing about the immo. Weird things: there is nothing at 081 group of ECU, it looks like it doesn't recognize the immo. The other weird thing is that the immo block has Starting permitted 0, so the immo doesn't like something as well. And the main question: why ECU doesn't accept my SKC from its EEPROM?
I know, I can disable immo in EEPROM and flash it in boot mode, but that's more educational post: why does it happen? Isn't ECU happy with the previous EEPROM?
|