Hey Guys,

I've been working on programming a used TCM for a 2011 Chevrolet Express with VIN Number 1GAZG1FG7C1110094. The TCM was initially working fine, and I downloaded the calibration files from SPS, creating an archive manually. However, trouble struck during the programming via DPS. It threw an error, and now the TCM seems to be dead. I've been attempting to reprogram it through SPS, but each attempt fails. Additionally, the scan tool isn't showing any communication with the TCM. Any guidance would be highly appreciated. Thanks!

attached are the logs and the utility file
 

GM.zip ProgramLog.Txt

Are you able to use the GM SPS service to program the TCM?

it shows unrecognized calibration and when i start programming it, it retries 3 times and fails and gives me an error message 

• E4491/E4423 – Programming Failed.
  
  the TCM was ok before car was running and everything was fine but i just wanted to program the correct files now its dead 😔

I don't believe the TCM is bricked as it appears to be still communicating, just missing the calibration files. Is it possible for you to attempt a diagnostic with a different interface? I have encountered similar issues before, where failed programming resulted in the module only being recoverable using a genuine GM MDI2 interface with GM SPS service.

Unfortunately, I don't have genuine MDI 2 only the scanmatik and vxdiag and I tried both and they are failing. even tried to remove battery and wait for some time but still it doesn't load the calibration files both the SPS and DPS 

now you need tool like IOTERMINAL for sw recovery.

 

6 hours ago, Talha Tariq said:

Hey Guys,

I've been working on programming a used TCM for a 2011 Chevrolet Express with VIN Number 1GAZG1FG7C1110094. The TCM was initially working fine, and I downloaded the calibration files from SPS, creating an archive manually. However, trouble struck during the programming via DPS. It threw an error, and now the TCM seems to be dead. I've been attempting to reprogram it through SPS, but each attempt fails. Additionally, the scan tool isn't showing any communication with the TCM. Any guidance would be highly appreciated. Thanks!

attached are the logs and the utility file
 

GM.zip 591.79 kB · 1 download ProgramLog.Txt 232.77 kB · 1 download

The TCM is still alive otherwise it wouldn't respond to the broadcast request or even allow you back through security access.  I'm not there to see it myself but it's attempting to load up the first calibration and immediately returning an error code that is stating it cannot process the request.  It's basically telling you it's busy....  but I'll admit, I'm not sure why.  I've never seen this behaviour.  It could also be due to the load being too large for the EEPROM (i.e. using a different VIN - the used TCM might be slightly different).  Do you have the original VIN?  Wouldn't mind to take a look.  I also would bet that if you used the original VIN, it would come back to life but with the wrong calibrations that you need lol.

another module "sof bricked" due not understanding DPS packages construction. Is issue with calibrations position. Position is stated in VIT2. Some modules required to be manually configured as DPS, don't have VIT2 info. To be recovered now need all data to be prepared and loaded. If SPS has to be used, will need VCI to skip SW check

13 minutes ago, Lyubomir Krastanov said:

another module "sof bricked" due not understanding DPS packages construction. Is issue with calibrations position. Position is stated in VIT2. Some modules required to be manually configured as DPS, don't have VIT2 info. To be recovered now need all data to be prepared and loaded. If SPS has to be used, will need VCI to skip SW check

lol we're on both posts.  The other post, SPS should have worked as it would have populated, this one is different.  I would for sure try it here.  I also didn't read this utility (it's late lol)

Hi yes i do have the original vin i took the photo luckily

So the DPS calibration files in the archive were not downloaded using the VIN that was already stored in the TCM? If not, try using the VIN that was in the TCM to download the files from SPS, then try to program the module using those. 

Alright thank you very much

2 hours ago, Troy said:

So the DPS calibration files in the archive were not downloaded using the VIN that was already stored in the TCM? If not, try using the VIN that was in the TCM to download the files from SPS, then try to program the module using those. 

Not likely SPS to see module as currently is in soft bricked state - no OS or any calibrations stored. So SPS cannot conduct checks and release current calibrations. It has to be force loaded into module

2 minutes ago, Lyubomir Krastanov said:

Not likely SPS to see module as currently is in soft bricked state - no OS or any calibrations stored. So SPS cannot conduct checks and release current calibrations. It has to be force loaded into module

 

In that case if not possible, if he has the other TCM he could use that with the VIN from this TCM in sps.

I had this same issue with an ECM and SPS was able to recover it using an MDI2, 

1GTHC43K79F108401 TCM.zip

thanks alot brother

Did @Kirill Kirill DPS file get the TCM working again?

i will program in a few hours and will update you guys. Thanks alot for helping 

13 minutes ago, Talha Tariq said:

i will program in a few hours and will update you guys. Thanks alot for helping 

If that doesn't work, do you have hp tuners interface? A friend of mine was able to recover a tcm just like your situation with hp tuners. We tried dps with original vin calibrations and also tried sps2, still didn't work. Hp tuners saved the day 

Unfortunately no i dont have and i tried to program the archive that was provided unfortunately the TCM is now bricked and cant even get controller info it says and error occurred and doesnt program at all. Sps is also giving an error retrieving the controller data

Is it not possible to read info from the ecu using dps?

I could do it before but now it says an error occurred 😭😂. I think its dead now completely might need some other tool like io terminal to write complete files

Vehicle was Express 2012, TCM from Sierra 2009,, same MYD 6L90,, is it done...

 

Unfortunately no. It has been bricked and currently i don’t have any tool to recover it