RomRaider

Hi everyone, hoping someone may have a stock file for the following tcm
Numbers on the plastic case are as follows

31711AN650

30919AB600

112400 - 8280

Can confirm it is a denso sh7058s processor

I was trying to overwrite a locked ecu in car and the ecu bricked, i fixed the ecu with ktag but it appears to of got the tcu as well. Unfortunately i do not have the calibration number for the original file.

Ecu calibration number is AZ1J500J. 2011 wrx sti at, ecu number suggests jdm but vehicle is sold new here so is more likely audm

So I have worked out that 30919AB600 aligns with trends in the subaru flashwrite pak file names but I am unable to even find that online

I had the same issue on my Forester S Edition 5EAT.

I was trying to recover the ECU with FastECU, and wrote the ECU File to the TCU instead.

Luckly, it wasn't "bricked" as I still could read and write to it, but I never read the original ROM from the TCU (didn't even know it was possible to read, neither write to the TCU until that point)

I had a friend with a similar car disconnect their ECU, and read it using FastECU with Denso Recovery Protocol.

We got the stock TCU rom, which I could flash back to my car.

So the option you have there is, find someone else with the same car as yours, disconnect the ECU from the harness completely, read it using FastECU or other tools that can read the SH7058 over Kline or CANbus. (EcuFlash doesn't work for that)

That will give you the stock TCU file.

Flash it back to your car, make sure to disconnect the ECU from the harness when flashing aswell.

Best regards

I found a rom on this site an was lucky enough to confirm that the trans id etc was the same with the person who posted the rom.

Unit was dead via obd though so I had to boot mode it, was quite a process including tracing contact points on the board, a set frequency to initate boot mode the same as when recovering an ecu.

Got it going again though, i posted a wiring schematic over on the fastecu forums on how to do it if anyone ever needs

This is something I should work on, atleast add warnings to DensoCAN protocols that it might connect to TCU instead of ECU... and add some kind of test if possible before ROM read/write operations to make sure it connects to right module.

I believe the easiest way would just be a warning to unplug tcm if vehicle is auto. As mentioned with mine it killed both tcm and ecu in one go, so both units must of tried to accept programming