07 STi locked by Cobb

[patkelley]

I have an 07 USDM Sti (A2UJ000J) that has a Cobb pro tune flashed on it via a V2 accessport. The accessport is non-functional. Is it possible to read this rom via Fast ECU? I would like to obtain the flash in the event that I buy a new accessport (V3) and continue to use this tune. Thanks!!

[MiikaS]

You can try it with DensoCAN protocol, with or without test mode connectors.

[patkelley]

I tried the following DensoCAN protocols:

sub_ecu_denso_sh7058

PXL_20251108_023709315a.jpg (240.04 KiB) Viewed 261030 times

sub_ecu_denso_sh7058_can

PXL_20251108_023835058a.jpg (243.15 KiB) Viewed 261030 times

I received the following error messages (see pictures)

Not sure if I'm using the app correctly - I have flashed another 07 STI with ecu flash many times along with many Mitsubishis so I am experienced with Tatrix cables, ecu flash, romraider, and EvoScan

I also tried these with the test mode connector plugged or unplugged with the same results.

[MiikaS]

Right protocols are sub_ecu_denso_sh7058_densocan and sub_ecu_denso_sh7058s_densocan

BUT, as your log shows, ECU doesn't respond ECU init request via CAN, so they maybe won't work when ECU is in car...

[patkelley]

I tried both of those protocols with no success - the only one that appears to have any communication is the 'sub_ecu_denso_sh7058' where it finds the ecu ID.

If you have a source or link to build a bench flash setup, please provide it. I have a wiring harness from an Evo that has the diagnostic plug and plenty of wiring and pins to make a bench connector.

Thanks for all your help!!!!

[patkelley]

I wanted to follow up on this thread even though it's been a while since I first posted. I ended up using a V3 AP to restore the 07 STi to the OEM flash and re-tuning the car via RomRaider, FastECU and ECUFlash.

In the meantime I purchased a 2011 STi that is also Cobb protuned and I tried FastECU again with one significant change - I realized while tuning the 07 that I was using an Amazon Tactrix 2.0 rather than my genuine Tactrix which was sitting in the backseat of my EVO. I was able to read the Cobb rom with the 'genuine' Tactrix while the Amazon version gave the same errors that I posted above on the 2007. Not sure what's different between the 2 devices but I can also report that the Amazon version will not do anything on an EVO (this is what made me swap cables). The Amazon cable works fine with ECUFlash and RomRaider for read/write/datalog.

I have attached the 'Cobb' Rom from the 2011 - now I need to build a definition file for it Anyone tried to define a Cobb rom??