vserena82
Newbie
Karma: +0/-0
 Offline
Posts: 18
|
 |
« on: June 16, 2021, 02:46:08 PM »
|
|
|
Hello,
I have often troubles with immobilizer on my Golf MK4, and I want to remove it.
I opened dashboard (code 0263604023) and found 2 eeproms inside: one 24C02 and one 93LC56
I'm electronic technician and I have hardware to read and write eeproms but I have no knowledge about automotive electronics and I don't know what to do to remove Immobilizer, so I need your help.
I read 24C02, bin file is attached.
If needed I will read 93LC56.
Someone can help me or tell me where I can find instructions to go on?
Thank you a lot!
|
|
|
|
« Last Edit: June 22, 2021, 01:42:07 PM by vserena82 »
|
Logged
|
|
|
|
tadope
Full Member
Karma: +2/-25
Offline
Posts: 221
|
|
« Reply #1 on: June 16, 2021, 08:30:14 PM »
|
|
|
There is software on the nefarious forum stickies that can do it. Easy and free. It's command line based. But very ez and simple
|
|
|
|
|
Logged
|
|
|
|
|
BlackT
|
|
« Reply #2 on: June 16, 2021, 11:51:08 PM »
|
|
|
here you go
|
|
|
|
|
Logged
|
|
|
|
stuydub
Full Member
Karma: +27/-12
Offline
Posts: 231
|
|
« Reply #3 on: June 17, 2021, 01:36:44 AM »
|
|
|
|
|
|
|
|
Logged
|
|
|
|
vserena82
Newbie
Karma: +0/-0
Offline
Posts: 18
|
|
« Reply #4 on: June 17, 2021, 03:55:22 PM »
|
|
|
Thank you a lot for your support!
Looking at image posted by BlackT, data on my memory doesn't match... or this is not for my eeprom or my eeprom is corrupted, could you check please my eeprom data? (atteched on previous post)
Is my ecu M3.8.x or M5.9.x? Where I can find this information?
I want to remove immobilizer because few days ago the car can't start and immoibilizer light was blinking. I tryed with 2nd key but problem was not solved. So I ask to my mechanic to check.
My mechanic tried to reprogram code on car.
It works only for first time, after that the same immobilizer problem...
My dashboard has code 0263604023 V11 1J0919 880B MMO.
This is the picture of the board:
|
|
|
|
« Last Edit: June 17, 2021, 04:12:27 PM by vserena82 »
|
Logged
|
|
|
|
stuydub
Full Member
Karma: +27/-12
Offline
Posts: 231
|
|
« Reply #5 on: June 18, 2021, 07:48:29 AM »
|
|
|
IMMO OFFhas nothing to do with cluster
|
|
|
|
|
Logged
|
|
|
|
stuydub
Full Member
Karma: +27/-12
Offline
Posts: 231
|
|
« Reply #6 on: June 18, 2021, 07:50:22 AM »
|
|
|
Also your immo 2 so try re adapting ECU with VCDS or try and recode keys using VCDS
|
|
|
|
|
Logged
|
|
|
|
|
BlackT
|
|
« Reply #7 on: June 18, 2021, 08:38:26 AM »
|
|
|
Your read is not good, try again
|
|
|
|
|
Logged
|
|
|
|
d3irb
Full Member
Karma: +134/-1
Offline
Posts: 195
|
|
« Reply #8 on: June 18, 2021, 09:41:53 AM »
|
|
|
Your read is not good, try again
The read is fine, it's just from the wrong module! Turning immo off is done in the ECU, not the cluster. Open the ECU and read the E2P from inside of the ECU, not the one from inside the cluster. Then the tools linked above will work. |
|
|
|
|
Logged
|
|
|
|
vserena82
Newbie
Karma: +0/-0
Offline
Posts: 18
|
|
« Reply #9 on: June 18, 2021, 01:15:58 PM »
|
|
|
So I read wrong eeprom... I read this one because mechanic tells me that problem is in cluster... and he suggest me to replace cluster to solve.
In the cluster there is informations about immobilizer key code or not? was mechanic wrong?
Do you think that changing cluster I will solve my problem? (problem is described above)
I will read ECU eeprom and after I will post here news
thank you
|
|
|
|
|
Logged
|
|
|
|
d3irb
Full Member
Karma: +134/-1
Offline
Posts: 195
|
|
« Reply #10 on: June 18, 2021, 02:12:25 PM »
|
|
|
Both parts are responsible: the cluster stores the pairing with the keys, but the ECU is what eventually refuses to start the engine. Basically the cluster tells the ECU "there is a valid key, you are allowed to start up now."
By turning off IMMO in the ECU itself, whatever is in the cluster no longer matters. The ECU will always start the engine even without a valid IMMO authentication.
Your mechanic is not wrong, the actual problem could be somewhere in your cluster - which is why others in this thread already recommended to reprogram your keys into the cluster module using VCDS. Unfortunately, there are fewer tools and less research into Immo 2 clusters than for ECUs (you can find a tool in this forum for Immo 3 clusters, but I don't _think_ that really helps you), so nobody can easily look at your cluster dump to see if the data makes sense.
In short: both the ECU and the cluster play a part in IMMO. It could very well be that something is wrong with your cluster. But, to just disable the IMMO, like you were asking about - that is done in the ECU alone.
|
|
|
|
« Last Edit: June 18, 2021, 02:32:55 PM by d3irb »
|
Logged
|
|
|
|
vserena82
Newbie
Karma: +0/-0
Offline
Posts: 18
|
|
« Reply #11 on: June 18, 2021, 02:24:47 PM »
|
|
|
Both parts are responsible: the cluster stores the pairing with the keys, but the ECU is what eventually refuses to start the engine. Basically the cluster tells the ECU "there is a valid key, you are allowed to start up now."
By turning off IMMO in the ECU itself, whatever is in the cluster no longer matters. The ECU will always start the engine even without a valid IMMO authentication.
Your mechanic is not wrong, the actual problem could be somewhere in your cluster - which is why others in this thread already recommended to reprogram your keys into the cluster module using VCDS. Unfortunately, there are fewer tools and less research into clusters than for ECUs, so nobody can easily look at your cluster dump to see if the data makes sense.
In short: both the ECU and the cluster play a part in IMMO. It could very well be that something is wrong with your cluster. But, to just disable the IMMO, like you were asking about - that is done in the ECU alone.
you explaned me well how it is working, now I understood better. I havent VCDS, but my mechanic tryed to reprogram keys to cluster. It was working only first attempt, and after immo error appears again. All alectronics components on cluster board seems to be well soldered, so I'm thinking to buy an used cluster and ask to mechanic to reprogram keys. If I will have problems again I will disable immo on ECU eeprom. There is possibility to modify mileage on new (used) cluster modifing eeprom data? |
|
|
|
|
Logged
|
|
|
|
elektronik13
Full Member
Karma: +11/-37
Offline
Posts: 207
|
|
« Reply #12 on: June 18, 2021, 02:35:34 PM »
|
|
|
you explaned me well how it is working, now I understood better.
I havent VCDS, but my mechanic tryed to reprogram keys to cluster. It was working only first attempt, and after immo error appears again.
All alectronics components on cluster board seems to be well soldered, so I'm thinking to buy an used cluster and ask to mechanic to reprogram keys. If I will have problems again I will disable immo on ECU eeprom.
There is possibility to modify mileage on new (used) cluster modifing eeprom data?
the mileage is in the address 0050 rewrite the entire line 294874 km ( pin 00054 ver. immo 2 ) only then, if you have the same dash or, you can set what mileage you want repairing this immo in this Golf takes up to 15 minutes if you have a working key |
|
|
|
« Last Edit: June 18, 2021, 02:42:59 PM by elektronik13 »
|
Logged
|
|
|
|
vserena82
Newbie
Karma: +0/-0
Offline
Posts: 18
|
|
« Reply #13 on: June 18, 2021, 02:55:49 PM »
|
|
|
the mileage is in the address 0050 rewrite the entire line 294874 km ( pin 00054 ver. immo 2 )
on line 50 I have FD 47 FD 47 FD 47 FD 47 FD 47 FD 47 FC 47 FC 47 how do you found 294874km? could you tell me the rule? repairing this immo in this Golf takes up to 15 minutes if you have a working key
do you mean that my cluster can be repaired? I have a working key but I havent tools, I can only read and write eeprom... |
|
|
|
|
Logged
|
|
|
|
elektronik13
Full Member
Karma: +11/-37
Offline
Posts: 207
|
|
« Reply #14 on: June 18, 2021, 03:07:57 PM »
|
|
|
on line 50 I have
FD 47 FD 47 FD 47 FD 47 FD 47 FD 47 FC 47 FC 47
how do you found 294874km? could you tell me the rule?
do you mean that my cluster can be repaired? I have a working key but I havent tools, I can only read and write eeprom...
47FD hex = 18492 dec x 16 = 294864 writing in the Whole line will be very little inaccuracy but I don't think it will be a problem for you 47FC hex = 18428 dec x 16 = 294848 294874 km = 18429 dec = 47FD 1. you need to have a device that will act as vcds, without it can not be programmed |
|
|
|
« Last Edit: June 18, 2021, 03:19:52 PM by elektronik13 »
|
Logged
|
|
|
|
|
