NefMoto

Hi guys, I have a 2003 Jetta with IMMO3. I kept getting a K1:Short to ground and could not track it down. I could not access anything via the DLC. I decided to try another cluster and was suddenly able to access everything available. I figured that the K1 short must be in the cluster itself and decided to try swapping it for the one I picked up. This car is bone stock, so I figured it would be an easy swap. Not!

I went through the entire RT swap procedure and it keeps hanging up, when I enter the PIN that I want to store in the replacement cluster. I'm hoping you guys can help shed some light on this for me, or that there might be something I missed. If this is the wrong forum, please forgive me. If there is any available software on this site that can help me out, please let me know. Here's a screen grab.. Note the fields "System" and "Not ok"

(http://i218.photobucket.com/albums/cc123/SD70M/2003%20Jetta%201-8T/VCDS/systemnotok.jpg)

I forgot to mention... It was ArgDub's software, that made it possible to get the PIN from the ECU.. Thanks ArgDub!

just swap e2p from ori cluster to new cluster.

Have a look on Ross-Techs site
Look into immo2 to immo3 cluster swap and also ECU swap.

This should provide you the answers you require.
When you swap clusters, you need to resync all car keys as well.

I got some help from rand0mher0, in regards to changing the cluster dump of the replacement cluster. Here is what I started with:

(http://i218.photobucket.com/albums/cc123/SD70M/2003%20Jetta%201-8T/VCDS/MIDGET-HEX-NOT-EDITED.jpg)

It has the old IMMO ID, SKC and VIN in it.

Here's how it looks, after editing it with the new IMMO ID, SKC and VIN in it:

(http://i218.photobucket.com/albums/cc123/SD70M/2003%20Jetta%201-8T/VCDS/MIDGET-HEX-EDITED2.jpg)

Think it will work?

Ok... So I successfully changed the IMMO ID, SKC and VIN for the cluster. Trying to adapt the keys, however, just isn't working. Here's what VCDS is telling me:

Saturday,30,August,2014,21:56:06:14659
VCDS -- Windows Based VAG/VAS Emulator
VCDS Version: 12.12.3.0 (x64)
Data version: 20140822


VIN: 3VWSE69MX3M103749 License Plate: GREENMIDGET0830



--------------------------------------------------------------------------------
--------------------------------------------------------------------------------


Address 17: Instruments Labels: 1J0-920-xx5-17.lbl
Control Module Part Number: 1J0 920 906 J
Component and/or Version: KOMBI+WEGFAHRSP VDO V64
Software Coding: 01232
Work Shop Code: WSC 00050
Additional Info: 3VWSE69MX3M103749 VWZ7Z0B6059414
VCID: 2F6738D0ED240F66327-5106
2 Faults Found:

01177 - Engine Control Unit
65-10 - Unauthorized - Intermittent
01179 - Incorrect Key Programming
35-00 - -

There is a 4 byte immobilizer ID somewhere in that file that much match the ecu.

Any idea where that is in the ECU?

EMD do you mind posting the ECU file?

Here ya go!

Just in case, here's the file I uploaded to the cluster...

In the ecu it is right after the login code. (4 bytes)

Ok, so in that ecu file the 4 bytes after the login is E7 F2 81 55 which decodes to 1434579687. Now I have no idea where that goes in the cluster file. I might need to go grab the eeprom off my ecu...

The 4 bytes after the SKC are: E7 F2 81 55

Where does that need to go, in the cluster file?

http://nefariousmotorsports.com/forum/index.php?topic=6575.msg60802#msg60802

Also, you're misunderstanding byte.  Byte = 8bits = 1 character.  So 4 bytes = 4 characters, not 8 like you posted.

I must be too new with hex editing, to understand what you meant in that post. I do have team viewer and the files loaded in my hex editor, if you would care to show me what you mean. Sorry for not understanding.

Basically the first 4 characters we posted. 1 byte = 1 character I guess. So, E7 F2.

Also.. I can't get the software to complete the eeprom dump of my ecu. I keep on getting some error, I'll have to post in his thread.

I did get that part... It was what he said in the post that he linked to, that I wasn't understanding...  http://nefariousmotorsports.com/forum/index.php?topic=6575.msg60802#msg60802

It doesn't seem to make sense. The addresses that he listed where the immo is and the login are in that thread... don't match up to where your immo/login is in your cluster file. And I'm wondering if this is because that thread is for a completely different cluster. This is way beyond me at this point, lol. Until I can get my ecu file I can't figure this out.

Thanks for all the help you have been already!

Time for me to hit the sheets!

If you know the immo id for the "new" cluster (in hex)... search for that in the bin and replace it with the immo id for the ECU (in hex)...

correct

I transferred the VIN, SKC and IMMO ID to the file I uploaded to the cluster. I just need to know which 4 bytes I need to change, to match the ECU.

Similar problem, similar cluster: http://nefariousmotorsports.com/forum/index.php?topic=6302

Of course it's harder to be sure since you don't have the original cluster dump, but look at the file diff in that thread...

That thread is a good read. I just can't tell where I need to put those 4 digits from my ECU into my cluster file though.

Try using the latest version of 95040tool, availible in the bottom post on this thread: http://nefariousmotorsports.com/forum/index.php?topic=6134.msg62009#msg62009

use it like this:
95040tool.exe --in new_cluster_dump.bin --pair your_ecu_eeprom.bin --out paired_cluster_dump.bin

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:

(http://i218.photobucket.com/albums/cc123/SD70M/2003%20Jetta%201-8T/VCDS/paired2.jpg)

I will also post all three .bin files, so someone might be able to see where I went wrong..

What happened when you tried to pair the keys?

The IMMO light will only blink. I can never get it to adapt, to even the key I got with the car.

Did you follow the RT instructions and check the other measuring blocks first?

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.

There is also a step about making sure a set of blocks is all zeros... did you check that?

Also, did you redo the coding on the cluster after flashing the modified bin?  That step is supposed to correct the dash checksum.

The lockout fields were all at 0.0

I will try re-entering the coding.

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

Thank you!

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.

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. ..

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!

Thats annoying about your two new keys, you can get RFIDs off ebay for about $5 each.

Glad you got it working :)

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.

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...

Can you please link the thread for this tool.exe file?
Would like to try this on a few bin files I have.

Thanks

Turboat posted it in post 26 of this thread:

Try using the latest version of 95040tool, availible in the bottom post on this thread: http://nefariousmotorsports.com/forum/index.php?topic=6134.msg62009#msg62009 (http://nefariousmotorsports.com/forum/index.php?topic=6134.msg62009#msg62009)

use it like this:
95040tool.exe --in new_cluster_dump.bin --pair your_ecu_eeprom.bin --out paired_cluster_dump.bin

cheers guys.

glidn - if you have any comments, bugs, etc, please post them in the 95040tool thread. It currently doesnt work with immo2 bins, which is in the pipeline, and seems to report 'bad checksum' for some virgin reads - I'll be working on this when I have some time spare.

it's taken me ages to find this little gem, I just realised it won't work on immo2 after spending ages trying to virginise my ecu and dash with new rfid chips.

Biggest problem for me is i dont have the immo tag from the original dash as i have upgaded to a later dash pod and set it to immo2 on adaption channel 60.

I am struggling to edit in hex as i'm dead old,LOL

Previous cluster saw the keys but the me7.5 ecu that i changed to over m5.92 had to de immo'd to allow it to start, i'd ideally like to get it all paired up and an immo working now i have later ecu and dash.

Any help anyone can give would be appreciated

Or shall i start my own thread?

Start a new thread for this one, I'm unbelievably hungover so struggling to think through the situation, but fairly sure you will be able to get it working. I have a immo 2 version of eepromtool in progress, but Ive not properly tested it yet.

Edit: just seen your thread.

I've same issue: could not swap immo3 to immo3 cluster.
Old one cluster was Motometer, new one is vdo...
Using standard adaptaion 50 channel - say wait and nothink happend. Cluster do not match to ecu...
May be someone knows where located in motometer dump these 7 bytes for matching cluster to ecu? Some other info like adopted keys as I understand located in vdo immo 3 dump (cluster 9208x6) at addresses 20-27 and 40-47.
Dumps of motometer and vdo are attached.

Why I am not read ECU? It is Marelli 4MV ECU in the car and I could not find tool to read it.

Thanks in advance for your help!

In continuation with my previous post above: problem solved!
I have found 7 Bytes in Motometer dump based on Bosh dump.  ;)
There are adresses from 10 to 16 in dumps of 1J0920806 clusters by MM/Bosh.
Pasted these 7 bytes to vdo dump  in 3 areas and after that key learning done successfully.
Hope it helps somebody.

Thats useful info, thanks for posting it up.