2018 Challenger TA 392 T2 Trans files corrupt?

I was having a problem getting TCM files at all. Now that seems to be resolved, but when I restore the vehicle back to stock and then try to tune the vehicle, its saying TCM FILES ARE CORRUPT. Any help on this would be great. Thank you!

JB

[mikel]

Please post the info.xml file from the T2 drive.

Info file attached per request.

Thanks.

[mikel]

copy this to the i3 drive andlet it import the file then load to the tcm then you should be good to tune.

I dragged and dropped the file you sent directly to the drive. Took it to the vehicle, hooked it up and it started the calibration file by itself, it then read back up of PCM and TCM. Then I went to tune, it read both backups again and said the same message. TCM APPEARS TO BE CORRUPT.

I am confused, did I do something wrong or is it something else?

my apologies, it says trans last read is corrupt, not just trans.

[mikel]

Id suggest choosing the skip tcm for now while we look into this.

Any idea how this is coming or how long I might be looking at to investigate this problem? I have been collectively working on this problem for over a month now.

[mikel]

jaybisciaio wrote:

Any idea how this is coming or how long I might be looking at to investigate this problem? I have been collectively working on this problem for over a month now.

Return to stock then download this file then copy it to the i3 drive. Then you can tune the tcm.
Sorry for the delay.
https://drive.google.com/open?id=1MjBY3 ... si1ZdLidPd

Mike,

That did the trick!

Thank you very much!

Jay

[mikel]

jaybisciaio wrote:

Mike,

That did the trick!

Thank you very much!

Jay

Glad to hear it, sorry for the delay.


Thanks

Mike,

I'm having the same issue the the TCM file is corrupt. I have a 2018 Charger Scat Pack with a Trinity T2 tuner. The last time I spoke with support back in October they said they didn't have TCM support for the 2018's yet. I'm assuming that you do now based on this thread.
Any help would be much appreciated.

Thanks,

Bill

[mikel]

please return to stock, update the tool then try again, should be resolved.