EMD_Driver
Jr. Member
Karma: +0/-0
Offline
Posts: 28
|
|
« Reply #30 on: September 01, 2014, 07:47:56 PM »
|
|
|
I sure did. With the replacement cluster in, I get 0 keys adapted and 1 meaning it is ready. It just won't take any.
|
|
|
Logged
|
|
|
|
digitalhippie
Full Member
Karma: +0/-5
Offline
Posts: 111
|
|
« Reply #31 on: September 01, 2014, 10:16:10 PM »
|
|
|
There is also a step about making sure a set of blocks is all zeros... did you check that? [Select] [17 - Instruments] [Meas. Blocks - 08] Group 024 [Go!] Any numbers displayed in fields 1-4 represent the time in minutes that must be counted down before the Immobilizer is unlocked. If the fields are all zero, skip to step 6. If the Immobilizer is locked: [Done, Go Back] [Close Controller, Go Back - 06] Do not switch off the ignition! Allow the car to sit for AT LEAST the number of minutes that were indicated by the display in Group 024
|
|
|
Logged
|
|
|
|
digitalhippie
Full Member
Karma: +0/-5
Offline
Posts: 111
|
|
« Reply #32 on: September 01, 2014, 10:22:03 PM »
|
|
|
Also, did you redo the coding on the cluster after flashing the modified bin? That step is supposed to correct the dash checksum.
|
|
|
Logged
|
|
|
|
EMD_Driver
Jr. Member
Karma: +0/-0
Offline
Posts: 28
|
|
« Reply #33 on: September 01, 2014, 11:31:24 PM »
|
|
|
The lockout fields were all at 0.0
|
|
|
Logged
|
|
|
|
EMD_Driver
Jr. Member
Karma: +0/-0
Offline
Posts: 28
|
|
« Reply #34 on: September 01, 2014, 11:31:54 PM »
|
|
|
I will try re-entering the coding.
|
|
|
Logged
|
|
|
|
automan001
Full Member
Karma: +47/-0
Offline
Posts: 153
|
|
« Reply #35 on: September 01, 2014, 11:51:50 PM »
|
|
|
There is a 4 byte immobilizer ID somewhere in that file that much match the ecu.
I know it's 7 bytes sequence but not 4. According to eeprom file of the ECU the immo key was E7 F2 81 55 07 4B E9 (positions 34h and 2-nd copy at position 44h). The same immo key (=cluster code) should be in the cluster dump (positions 1-st at 72h, 2-nd at 7Ah, 3-rd at 82h) ). But actually last byte of cluster code E7 F2 81 55 07 4B B0 differs by some reason (B0 instead of E9). I guess the 95040 tool didn't copy last 7th byte of the immo key (=cluster code) from the eeprom of the ECU into cluster dump and you have B0 left from old donor's dump. Try to manually update the dump and put correct cluster code E7 F2 81 55 07 4B E9 at these places I mentioned. This should help to solve the immo issue
|
|
« Last Edit: September 02, 2014, 12:25:43 AM by automan001 »
|
Logged
|
|
|
|
EMD_Driver
Jr. Member
Karma: +0/-0
Offline
Posts: 28
|
|
« Reply #36 on: September 02, 2014, 01:00:28 AM »
|
|
|
Thank you!
|
|
|
Logged
|
|
|
|
turboat
|
|
« Reply #37 on: September 02, 2014, 01:43:59 AM »
|
|
|
Good spot automan! That's defo a bug, guess both my new and old clusters had the same 7th byte, sorry for time wasted
I'll get the tool fixed today.
|
|
|
Logged
|
|
|
|
EMD_Driver
Jr. Member
Karma: +0/-0
Offline
Posts: 28
|
|
« Reply #38 on: September 02, 2014, 02:28:20 AM »
|
|
|
No time wasted on this end! I learned a lot, in the process.. I now know a lot more, about these issues. I have 4 Jettas and I am sure this info could come in very handy. If not for me, someone else may get the answer to a similar issue.. Just from our experiences. ..
|
|
|
Logged
|
|
|
|
EMD_Driver
Jr. Member
Karma: +0/-0
Offline
Posts: 28
|
|
« Reply #39 on: September 02, 2014, 06:42:05 AM »
|
|
|
I went back in the cluster-paired file and changed the three "B0" entries to "E9" and re-uploaded it to the cluster. I put it in the car, went through the necessary steps and was immediately able to adapt the factory key back to the vehicle. I'm guessing that trying to adapt the two new keys previously, ruined the RFID chips. Neither of them would adapt to the car, no matter what I tried.
I will attempt to find a couple of virgin RFID chips and try adapting them again.
Many thanks to everyone, for their help! I could not have done this, without you!
|
|
|
Logged
|
|
|
|
turboat
|
|
« Reply #40 on: September 02, 2014, 06:44:11 AM »
|
|
|
Thats annoying about your two new keys, you can get RFIDs off ebay for about $5 each. Glad you got it working
|
|
|
Logged
|
|
|
|
automan001
Full Member
Karma: +47/-0
Offline
Posts: 153
|
|
« Reply #41 on: September 02, 2014, 07:23:18 AM »
|
|
|
I went back in the cluster-paired file and changed the three "B0" entries to "E9" and re-uploaded it to the cluster. I put it in the car, went through the necessary steps and was immediately able to adapt the factory key back to the vehicle. I'm guessing that trying to adapt the two new keys previously, ruined the RFID chips. Neither of them would adapt to the car, no matter what I tried.
Key code which is generated and written to RFID depends of the cluster code. So, wrong cluster code lead to wrong key code which was saved in the transponder chip. Then the chip was closed ("locked") by immo3 (immo 2 doesn't lock the chip, immo3 does) New blank transponders will solve the issue.
|
|
|
Logged
|
|
|
|
turboat
|
|
« Reply #42 on: September 02, 2014, 07:37:10 AM »
|
|
|
If you wanted to get those keys working, could you set the cluster code in the cluster and ecu to the one in the keys?
|
|
|
Logged
|
|
|
|
EMD_Driver
Jr. Member
Karma: +0/-0
Offline
Posts: 28
|
|
« Reply #43 on: September 02, 2014, 07:55:35 AM »
|
|
|
If you wanted to get those keys working, could you set the cluster code in the cluster and ecu to the one in the keys?
I'm not sure... I just ordered a couple of cheapo keys with virgin chips off ebay, so I will try the chips out of them, in the keys I already have cut...
|
|
|
Logged
|
|
|
|
Allabout
Full Member
Karma: +0/-2
Offline
Posts: 54
|
|
« Reply #44 on: September 11, 2014, 08:20:30 PM »
|
|
|
I ran the tool and it went off, without a hitch. Checked the data and it appeared correct. The E7 F2 digits even transferred across. When I put the cluster in the car and turned the key on, the immo light was blinking. I was unable to adapt any of my 3 keys to it. Here's a screen grab of what I did with the tool: I will also post all three .bin files, so someone might be able to see where I went wrong.. Can you please link the thread for this tool.exe file? Would like to try this on a few bin files I have. Thanks
|
|
|
Logged
|
|
|
|
|