Results 1 to 13 of 13

Thread: 2011 Sti write fail

  1. #1
    Tuner
    Join Date
    Sep 2010
    Location
    Houston
    Posts
    120

    2011 Sti write fail

    I use the patch and did a write entire , but fail to write due to a invalid checksum issue , I flash back the factory calibration and wrote just fine ,
    OS - AE5IB40V

    Send ticket to support but nothing

  2. #2
    Potential Tuner
    Join Date
    May 2022
    Posts
    7
    I recently had a similar issue, was your error "Writer Transfer Exit: Invalid checksum"? The most similar article I could find said that to flash back to stock. My vehicle has been previously modified and I am in the process of using a tactrix cable to flash a stock rom on it. I can let you know how this works if you would like.

  3. #3
    Potential Tuner
    Join Date
    May 2022
    Posts
    7
    Downloading a stock rom and flashing via tactrix since I could not find a stock rom via HPT did in fact fix the issue.

  4. #4
    Tuner
    Join Date
    Sep 2010
    Location
    Houston
    Posts
    120
    The car had Cobb and was returned to stock, the calibration write fail only when I patched the file, original file flashed just fine, I think it has to do with the way the patch is structured

  5. #5
    Did it cycle all the way through the write process before displaying the checksum failure to write? Meaning did it go through its 2 1/2ish minute process? If so, that?s a common issue, and the file did indeed write. At which point, just key cycle per normal, and you?re good.

  6. #6
    Tuner in Training
    Join Date
    Nov 2019
    Posts
    17
    I've seen this quite a few times after removing an AP. Needs to be flashed to stock with Tactrix then HPT works.
    Last edited by joshua@arcflashllc; 2 Weeks Ago at 07:57 PM.

  7. #7
    Potential Tuner
    Join Date
    May 2022
    Posts
    7
    Quote Originally Posted by OperationDriftL43 View Post
    Did it cycle all the way through the write process before displaying the checksum failure to write? Meaning did it go through its 2 1/2ish minute process? If so, that?s a common issue, and the file did indeed write. At which point, just key cycle per normal, and you?re good.
    Ive noticed the changes apply when I get this error, besides this being a common question how do you know about this issue?

  8. #8
    Tuner in Training
    Join Date
    May 2022
    Posts
    14
    Quote Originally Posted by joshua@arcflashllc View Post
    I've seen this quite a few times after removing an AP. Needs to be flashed to stock with Tactrix then HPT works.
    What does Open Source/Tactrix do to solve this that returning a COBB tuned car to stock doesn't do?

    Quote Originally Posted by OperationDriftL43 View Post
    Did it cycle all the way through the write process before displaying the checksum failure to write? Meaning did it go through its 2 1/2ish minute process? If so, that?s a common issue, and the file did indeed write. At which point, just key cycle per normal, and you?re good.
    I had this same thing happen to me about two times in a row, trying VCM Editor, VCM Editor Beta etc. Are you saying that it actually worked? Did it work with the patch applied?

  9. #9
    Tuner in Training
    Join Date
    Oct 2021
    Posts
    13
    would use ecuflash for subaru platform. Easy to use when you know where things are in the rom file and what to change. If you need help with your tuning using ecuflash send me a pm. Have done training in the 16bit ecu flash which you can use adapt to the 32bit ecu in the rom

  10. #10
    Tuner in Training
    Join Date
    Nov 2019
    Posts
    17
    Quote Originally Posted by Kevin92 View Post
    What does Open Source/Tactrix do to solve this that returning a COBB tuned car to stock doesn't do?
    That's a good question. I don't know the answer for sure but my guess is the AP isn't actually restoring the original image to the ECU. It's close but perhaps not the same. I suppose I could pull the AP "OE" image and compare it to a RR image. Every time I've had this happen, flashing a stock image from Romraider with a Tactrix solves it.

  11. #11
    Potential Tuner
    Join Date
    May 2022
    Posts
    7
    Quote Originally Posted by joshua@arcflashllc View Post
    That's a good question. I don't know the answer for sure but my guess is the AP isn't actually restoring the original image to the ECU. It's close but perhaps not the same. I suppose I could pull the AP "OE" image and compare it to a RR image. Every time I've had this happen, flashing a stock image from Romraider with a Tactrix solves it.
    Got an email back from support earlier today it seems some of these errors are bugs. From my experimentation it seems editing the SI drive tables can cause this checksum issue. So if the vehicle was flashed back to stock successfully previously this error could have another cause.

  12. #12
    Quote Originally Posted by CountMomo View Post
    Ive noticed the changes apply when I get this error, besides this being a common question how do you know about this issue?
    From both my personal experiences and the training courses I?ve taken through Evans Performance Academy.

  13. #13
    Quote Originally Posted by Kevin92 View Post
    What does Open Source/Tactrix do to solve this that returning a COBB tuned car to stock doesn't do?



    I had this same thing happen to me about two times in a row, trying VCM Editor, VCM Editor Beta etc. Are you saying that it actually worked? Did it work with the patch applied?
    Yes, if it completes the 2.5ish minute write process before displaying the checksum error, it did indeed make the changes. Key cycle like you normally would, and you?re all set. If you?re referring to the custom features patch, yes, same scenario. Also, you need to use the Beta version for Subaru support. At least until they finish up the ?mass update?.