US import XKR 4.2 no keys

Reply Subscribe

Thread Tools

Search this Thread

Yesterday | 10:17 AM

#21

dutchviking

Thread Starter

Junior Member

Joined: Mar 2021

Posts: 11

Likes: 0

Attached the contents before adding new keys of original and from a spare KTM

Attached Files

KTM_good.bin (128 Bytes, 2 views)

spare_KTM.bin (128 Bytes, 2 views)

Yesterday | 10:20 AM

#22

dutchviking

Thread Starter

Junior Member

Joined: Mar 2021

Posts: 11

Likes: 0

maybe @harencguri can decipher the VINS from attached files?

Yesterday | 10:41 AM

#23

harencguri

Junior Member

Joined: Apr 2026

Posts: 9

Likes: 2

BOTH eeproms has vin A47483 ...
in my case epprom was FFFFFF , i have edit to my car vin and after i have make new transpored with launch for 30seconds succesfull...

Yesterday | 10:44 AM

#24

harencguri

Junior Member

Joined: Apr 2026

Posts: 9

Likes: 2

this is my final eeprom changed that i have write and make succesfull keys with launch...

Attached Files

CGPro_93LC46_EEPROM_FINAL-OK.bin (128 Bytes, 3 views)

Yesterday | 12:24 PM

#25

dutchviking

Thread Starter

Junior Member

Joined: Mar 2021

Posts: 11

Likes: 0

Thank you, will compare with hex editor. Which setup did you use? SDD vxxx on VM? Mongoose? Wonder if V125 IDS might be better? And use an original Rotunda VCM in stead of the Mongoose cable?

Yesterday | 04:46 PM

#26

harencguri

Junior Member

Joined: Apr 2026

Posts: 9

Likes: 2

no i never used it... i have used launch and autel ...

Yesterday | 06:20 PM

#27

michaelh

Veteran Member

Joined: Apr 2014

Posts: 4,795

Likes: 3,008

From: Jersey, Channel Islands

Quote:

Originally Posted by dutchviking

Visited the Jaguar again today, but the Immobilizer routine failed, and module scan shows a red cross through the ECM and an orange question mark for the KTM. When I select CAN Network as Selected Symptom i get over 20 100% matches, all kind of modules lost contact with CAN, ECM module as well.

Is the CAN intact - 60Ω across pins 6 & 14 of the DLC?

I also see a question mark re the KTM on an SDD scan. Perhaps that's normal on a 'broken' car as it's apparently an optional module? Excerpt from PLATFORM_X103.exml in SDD:

"
<module>
<module_code_name acronym="KTM" ISOName="KTM">KTM_SYSTEM_A</module_code_name>
<address type="phys" session="diag">0x48</address>
<network>ISO</network>
<data_identifier_set type="NET">legacy</data_identifier_set>
<fitment>optional</fitment>
<tm id="@J_M_ACRO_KTM"/>
</module>
"

Quote:

Originally Posted by dutchviking

So next we used a separate twisted wire straight from the OBD connector to the ECM CAN wires, did not make any difference, also when we cut the CAN wires vehicle side. No change at all. I also tested with Mongoose pin 13 removed, no difference.

Pins 11, 12 & 13 for TCM & ECM flash on the earlier cars are shown as no connection for the 4.2L

Quote:

Originally Posted by dutchviking

Now I am starting to think that maybe the ECM is damaged. If someone before me has tried to (re)program it, is there a way to rescue it? Or source a used one and program as new?

Did you see the red X for the ECM on your original scan? If not, did you manage to get a VID block read?

There is a rectification process in SDD - see attached. Programming the ECM 'as new' might be an issue if the data is incorrect in any of the other modules the process interrogates.

Quote:

Originally Posted by dutchviking

And use an original Rotunda VCM in stead of the Mongoose cable?

I'd definitely choose the Rotunda over the clone for programming.

Attached Files

Jaguar 32-bit ECM recovery procedure.pdf (192.4 KB, 2 views)

Last edited by michaelh; Yesterday at 07:01 PM.

Yesterday | 06:59 PM

#28

michaelh

Veteran Member

Joined: Apr 2014

Posts: 4,795

Likes: 3,008

From: Jersey, Channel Islands

Quote:

Originally Posted by harencguri

BOTH eeproms has vin A47483 ...
in my case epprom was FFFFFF , i have edit to my car vin and after i have make new transpored with launch for 30seconds succesfull...

Interesting (although academic) that the last 6 of the VIN are stored as nibbles in the first 3 bytes. I also see the module part # - LNF2665AA - and, presumably, its 'part number suffix' 000 on the first row, stored as a mix of nibbles & bytes. Quite a lot more data in yours than dutchviking's dumps. Did you program more keys, perhaps?

The eeprom I pulled from the wet KTM read mostly FF other than 3 bytes. Whether that was from the water damage or someone's failed attempt to run immo setup, IDK.