2011 WRX Sti Bricked

[Gmguy]

Hi team,

Hopefully someone can help with advise to recover this ECU in. 2011 AUDM wrx sti.

Ecu had previosly been tuned with ECUtek, i attenpted to write a stock file and it started to right but failed almost immediately and now the ECU is bricked. Any pointers would be appreciated before i try ktag

[MiikaS]

Hi,

What version do you have and do you have any logs of the flashing? On windows it should found on <users home folder>/AppData/Local/FastECU/<version>/syslogs

But usually, if it failed at the beginning of full flash, it means that you neet to flash it again in SH boot mode (FDT Renesas or ktag etc.)

[Gmguy]

I have recovered the ECU using ktag and that went through no worries, but it would appear it has also bricked my tcm, not sure how i am going to recover that

[MiikaS]

If you used DenosCAN protocol and bricked TCU, then it's also Denso. You can use ktag also with it, same method as with ECU. I am thinking ways to not accidentally connecting to TCU with DensoCAN method when flashing in car as both ECU and TCU use same bootloader with it.

[Gmguy]

That is what i thought may have happened, i do not have a stock read for tcu though and no idea on calibration number for the tcu

Vehicle is a 2011 wrx sti with calibration AZ1J500J

That calibration is listed for a jdm car on rom raider, but this car is audm and the calibration number was confirmed before bricking the ecu

[MiikaS]

So it's not responding to anything?

You can look the number from the TCU box if it helps to find ROM for it.

[Gmguy]

No comms to tcu at all, shift lock not working etc. I will pull it own soon and check numbers on the box

[MiikaS]

But it's still shifting gears?

[Gmguy]

Have not driven it far, the box does engage in reverse and drive if you bypass the shift lock but bangs into gear as normal with a no comm tcm. Also logs a u0101 in the engine and abs for tcu signal not recieved

[Gmguy]

Numbers on the plastic case are as follows

31711 AN 65 0

30919 AB 600

112400 - 8280

Can confirm it is a denso sh7058s processor

[rimwall]

Depending on when in the process the flash failed, most of the TCU ROM may still be there. For example, it's possible only the first ROM block was written to. This will still cause the TCU to be uncommunicative but the rest of the TCU will still have the original ROM, and might be recoverable before you do the SH Boot.

Do you have the log of exactly what happened? Look for the file that @MiikaS mentioned.

If no log, can you remember exactly where in the process it crashed?

[Gmguy]

I have tried using bootmode to recover it on the bench and it fails when trying to load bootloader.

Only way forward is boot mode the processor

[Gmguy]

Depending on when in the process the flash failed, most of the TCU ROM may still be there. For example, it's possible only the first ROM block was written to. This will still cause the TCU to be uncommunicative but the rest of the TCU will still have the original ROM, and might be recoverable before you do the SH Boot.

Do you have the log of exactly what happened? Look for the file that @MiikaS mentioned.

If no log, can you remember exactly where in the process it crashed?

The log has nothing in it except selecting the specific modules, no flashing data.

It pulled about about 10 lines that had yes and no next them then gave an error.

Ive looked up on partsouq as you suggested and it does not give me any other info on the part other than saying not available

It does give me a destination code for the vin and that destination code is KA which google tells me is australia, funny enough the engine romid crosses to a jdm vehicle and that was id’d by pcmflash before the ecu became a brick

[rimwall]

I'm struggling to remember all the details of the SH boot approach, but fundamentally I think what happens is a bootloader is first loaded into RAM, and then that bootloader is used to write a ROM onto the chip. IIRC, the bootloader also has commands to dump data from the ROM. So, you could use the bootloader to read the TCU ROM contents. If you're lucky, only the top flash block of the ROM will have been flashed. This flash block is the same for all TCUs. So you could stitch the ROM back together using a dump from the bootloader combined with the top flash block from any TCU.

[Gmguy]

I have tried with the shboot protocal as well and had no luck, it sends messages but does not get any response, also tried the kline mode as well with no luck.

Im hoping the rom that was found on romraider for a 2011 sti with tg5 gearbox will get it working again. Then i will get in touch with a more knowledgeable dealer and see about the pak files