T43 reflash fail

[dzidaV8]

Hi!
I'm trying to do SPS reflash of 2008 corvette T43 TCM after a friend has interrupted a reflash with intune diablo (the intune recovery also fails).
SPS goes to about 80% and restarts the reflash. It ends in a seemingly endless loop of reflashing. I waited for 5 loops and broke the connection. The OS that it's flashing is 24243170 and the TCM is original to the car so there should be no HW or eeprom mismatch. I doubt the Intune would install a modified OS or mess with eeprom, but maybe?
I'm trying to locate SPS logs but I can't find anything (I'm using offline TIS2000). I'll try to sniff CAN messages next time.
Thanks for any help!

[ironduke]

What was the original OS?
Was the intune putting in a different OS? or just some changes?

I do agree I do not think the intune would be writing to the eeprom section of the flash, as long as the OS is staying the same it should be fairly unbrickable, yet it is somehow.

I checked, I don't have anything with that OS, possibly check https://tis2web.service.opel.com/tis2web/ with the vin and see if there's a newer OS that might have been in there already and with tis2000 your trying to write an older OS?

It would be good to see where it's failing in the logs.. 80% of the way there sounds like it's finishing up the OS write and failing before it tries the calibration writes..

btw.. Is this in car or on the bench? If in vehicle is there anything aftermarket on the high speed CAN like a remote start?

[dzidaV8]

VIN is 1G1YY26W585114327, there is only one OS with no updates shown in TIS.
I'm assuming that the original OS matched the VIN as the car is original and AFAIK there was no tuning done before that Intune disaster. He said that during Intune reflash battery went low and it did not complete. But I wasn't there and it happened a few years ago and since the car is just sitting. Intune recovery option fails at seemingly random %. The owner kinda got frustrated and lost interest in it.
I'm flashing in car with RDO fuse pulled. I don't think there is anything aftermarket on CAN but haven't checked.

Do you know where the old offline TIS2000 stores logs, if any? I can't find anything in it's files.

[ironduke]

If your using an mdi you might be able to do this.
type in J2534 in the run box and the J2534 configuration application should load.
click on more on the lower right, find the device tab matching your device, then select enable monitoring.
Now click the apply button.. I think you can minimize it but I always just drag it off to the size.. Now go try programming and when it fails take a look at the file location shown for the output file on the device tab that you used.

[dzidaV8]

Unfortunately I don't have MDI, using VXdiag nano.

The owner confirmed that there were no mods to software before his Intune attempt.

[kur4o]

Maybe you can try to read the tcm and see what`s inside, might give it a clue where it fails and why it fails.

Diablo might have fried the memory chip, or corrupted eeprom, they also like to update OS, so device have maps for it. I have nothing but bad experience with any of this handheld piece of crap.

Last effort will be to remove tcm from gearbox, and bench flash it. Voltage might drop somewhere. getting the error of the last message also can show some info. Do you have access to gm secret flashing program. it may be way more stable than tis2000. I have seen some bugs with tis2000 flashing already.

[kur4o]

some archive in case you can use it.

[dzidaV8]

Thanks for the binaries!

[dzidaV8]

OK, I went back to the car, DPS reflash went successfully, but after that TCM still shows EPROM checksum error. TCM is in limp home mode, not shifting gears. I also tried reading TCM with intune (after succesful reflash) and it says there is no TCM calibration.

All 4 calibration part IDs show correctly.
Take a look at the attached reflash log. I tried reflashing twice with same effect.
Reflash was in vehicle with RADIO fuse removed.

[ironduke]

Can you post up the log of the get ecu info? odd how it's not showing programming status or the serial number.. my first guess is somehow the eeprom segment of the flash got corrupted with the intune flash. Only thing I have to overwrite that is IO-prog. Nothing software wise to work with a J2534 device..

btw, just to make it easier.. Don't need to worry about the radio, that's on low speed. Only thing aftermarket to worry about is something jumped into the high speed CAN like an aftermarket remote start...