[xf_phil]

Hi @Kukkolasse
If you fixed this ????? issue and still have the target identifier issue, have a look at the IAU. I would just try to a get used one and try it. Cheap and easy. Just plug n play.
https://www.jaginfo.org/posts/3001342/
XF_Phil helped me a lot with pointing me into this direction.

Cheers
Dirk

I'd suggest only to suspect the IAU if it fails with 16-17 seconds on the timer for the first automated ignition cycle during immobilization, after you've already checked/fixed the BCM emulated eeprom is ok.

 

[Kukkolasse]

Update on My Situation

I managed to find a used DX23-14B476-BG BCM; however, it has the wrong VIN (from a 3.0-liter model).

I'm currently trying to perform an EEPROM read/write, but I'm unable to get the software running on my XProg box. Here's the setup I'm using:

Windows 7 Professional 64-bit

XProg-M package purchased from AliExpress (versions 6.50/6.26/6.12, including Xprog 5.84/5.55)


I’ve been attempting to install the 5.86 drivers by selecting the correct file, but Windows keeps displaying an error saying, "Windows could not find driver software for your device."

Additionally, I noticed that both the packaging and the program indicate version 5.86. Could this mean I have the wrong XProg version for my setup?

If anyone has experience with this or suggestions on how to resolve the driver or version issue, I'd greatly appreciate your advice!

 

[Kukkolasse]

Hello, could someone kindly assist me?
I finally managed to install the Xprog 5.86 software on my computer and followed the dekiellon guide to install the virgin file (BCM DX23-14B476-BG) found here: https://www.jaginfo.org/posts/2948062/. I used the same selections for type, subtype, and device as indicated in the guide.

I found the attached virgin file on a forum and replaced the VIN with my own. Up until this point, everything seemed to work perfectly.

I installed the BCM back into the car (Jaguar XF Sportbrake 2.2D 2013) and tried to program it as new, but the SDD wouldn't allow me to program it and returned the error code "Cannot find target identifier." (The rear BCM was successfully updated using SDD). Additionally, the security/immobilizer is not functioning.

I removed the BCM again and reconnected it to the Xprog.
Could someone kindly check if I did everything correctly and assist me in virginizing the BCM again?

Thank you in advance!

 

[xf_phil]

Hello, could someone kindly assist me?
I finally managed to install the Xprog 5.86 software on my computer and followed the dekiellon guide to install the virgin file (BCM DX23-14B476-BG) found here: https://www.jaginfo.org/posts/2948062/. I used the same selections for type, subtype, and device as indicated in the guide.

I found the attached virgin file on a forum and replaced the VIN with my own. Up until this point, everything seemed to work perfectly.

I installed the BCM back into the car (Jaguar XF Sportbrake 2.2D 2013) and tried to program it as new, but the SDD wouldn't allow me to program it and returned the error code "Cannot find target identifier." (The rear BCM was successfully updated using SDD). Additionally, the security/immobilizer is not functioning.

I removed the BCM again and reconnected it to the Xprog.
Could someone kindly check if I did everything correctly and assist me in virginizing the BCM again?

Thank you in advance!

It's good to see you've resolved the driver issue, how did you resolve it?

Your editor has replaced all the nulls in the file with spaces! I suggest you try again, make sure to use an editor for binary files, and if you're already doing that find and disable the option that is replacing null characters with space characters.

Also dump a copy of the pflash from your new bcm ( keep a backup copy of that just in case ), and edit the VIN in the dumped image then erase the pflash, and flash the pflash with the version with the VIN modified.

 

[Kukkolasse]

Update


I found my father's 20-year-old Fujitsu Siemens laptop with Windows XP, and with it, there were no issues using X-Prog.

I ran the attached files for the BCM. I couldn't locate where to edit the VIN code in the P-Flash file using HxD editor, so it remains original.

After programming, I managed to program the keys to the car, and everything else seems to work except for the KVM, immobilizer, and BCM rewriting. For these, I received the code "Failed to find target identifier."

Could something have gone wrong again during the BCM rewriting, specifically with writing the P-Flash? Additionally, the temperature gauge seems to be missing, and the left headlight flickers and occasionally turns off.

Below is also an image of the fault codes:

• B1B01-55 (BCM): Key transponder
• U0422-00 (PBM): Invalid data received from the body control module
• U0155-00 (PCM): Lost communication with the vehicle immobilizer control module
• U0426-00 (PCM): Invalid data received from the vehicle immobilizer control module
  
  

 

[xf_phil]

Update


I found my father's 20-year-old Fujitsu Siemens laptop with Windows XP, and with it, there were no issues using X-Prog.

I ran the attached files for the BCM. I couldn't locate where to edit the VIN code in the P-Flash file using HxD editor, so it remains original.

After programming, I managed to program the keys to the car, and everything else seems to work except for the KVM, immobilizer, and BCM rewriting. For these, I received the code "Failed to find target identifier."

Could something have gone wrong again during the BCM rewriting, specifically with writing the P-Flash? Additionally, the temperature gauge seems to be missing, and the left headlight flickers and occasionally turns off.

Below is also an image of the fault codes:

• B1B01-55 (BCM): Key transponder
• U0422-00 (PBM): Invalid data received from the body control module
• U0155-00 (PCM): Lost communication with the vehicle immobilizer control module
• U0426-00 (PCM): Invalid data received from the vehicle immobilizer control module
  
  View attachment 203430

Your eeprom image looks good, if you post or PM me the pflash dump I'll have a search though it for the VIN too, as it is in the other dumps I've seen.
How far into the process are you when it gives you the failed to write target id message?
( if it's in the first automated ignition cycle, and the timer is showing 16-17 seconds then it could be an IAU failure, but it seems likely you're missing the VIN in the pflash dump somehow, so best address that first )

 

[Zbyrsimsek]

Hello SANDMAENNLE.

I have read this post you have replied to and you are guiding for a process to start the car again. I have the same problem after battery death. Can you help me?
My whatsapp is +46.73.939.19.60

Thank you very much.