Kia Sorento 2010 95910-1U000 XM clear crash please

[mikedemirjian]

hey guys, can someone please clear the crash fault for me on this sorento module?

Kia Sorento 2010
Autoliv 95910-1U000
MAC7242

I read the file by cg100, and tried a solution here from the forum, but it gives me Internal Fault.

Thank you in advance!

[chiorbeq]

CG100 is a shit!

[mikedemirjian]

Actually its not! It never failed on me, been using it for a year already. Anyway i solved the problem, luckily i got an exact similar car, read its airbag module's flash and wrote it on mine, and crash fault is gone.

[chiorbeq]

I see many problems in read or write,if you are satisfied for this tool it's ok!

[BigPapaGotti]

Actually its not! It never failed on me, been using it for a year already. Anyway i solved the problem, luckily i got an exact similar car, read its airbag module's flash and wrote it on mine, and crash fault is gone.

I'm in a very similar situation with a 2011 Kia Sorento with SRS 95910-1U000. The original module that is in the vehicle, I am unable to read. I only have AlexFlasher and Tactrix OpenPort 2.0. When I try and read the original module I receive an error:

9/19/2021 1:31:58 PM APPLICATION IS RUNNING
9/19/2021 1:31:58 PM SELECTED DEVICE: OpenPort 2.0 J2534 ISO/CAN/VPW/PWM
9/19/2021 1:32:12 PM SELECTED DEVICE: OpenPort 2.0 J2534 ISO/CAN/VPW/PWM
9/19/2021 1:32:12 PM API VERSION: 04.04
9/19/2021 1:32:12 PM DLL VERSION: 1.02.4820 Jul 6 2016 17:20:04
9/19/2021 1:32:12 PM FIRMWARE VERSION: 1.17.4877
9/19/2021 1:32:12 PM SELECTED ECU: SRS/Kia/AIRBAG/AUTOLIV/FREESCALE MAC7242 64kb CAN BUS
9/19/2021 1:32:20 PM READ EEPROM FILE NAME = C:\Users\Owner\Documents\Original.bin
9/19/2021 1:32:20 PM API VERSION: 04.04
9/19/2021 1:32:20 PM DLL VERSION: 1.02.4820 Jul 6 2016 17:20:04
9/19/2021 1:32:20 PM FIRMWARE VERSION: 1.17.4877
9/19/2021 1:32:20 PM SERVICE MODE START
9/19/2021 1:32:20 PM PROGRAMMING SESSION START
9/19/2021 1:32:20 PM AUTHENTICATION
9/19/2021 1:32:21 PM SERVICE MODE START
9/19/2021 1:32:21 PM AUTHENTICATION
9/19/2021 1:32:23 PM PassThruReadMsgs ERR_BUFFER_EMPTY
9/19/2021 1:32:23 PM EEPROM READ ERROR

I purchased a used module off of eBay that has the same part number. I was successfully able to read this module using Alexflasher/OpenPort 2.0. This module throws me a B1684 "Not Configured" DTC when I connect it to my vehicle. I'm assuming this is because the VIN and ACU codes are different.

My question to you is, do you think it would be safe to write the 64KB EEPROM file to my original module that I can't read from? My fear is that I wipe out the VIN/ACU code on my original module and I'm stuck with the B1684 code on both modules. In other words do you know where the VIN and ACU codes get written to? I checked my dump, but I don't see the VIN listed so I think its written elsewhere?

Appreciate any help you can provide!!

[BigPapaGotti]

I went ahead and wrote the EEPROM data from my used module which had a different ACU code (XM51) to my original module (XM52) and my issues were resolved. All crash data was cleared and my B1620 error went away! After doing the write, I successfully read back the EEPROM from my original module using AlexFlasher and Tactrix OpenPort 2.0

I hope this helps someone in the future who is in a similar situation.