RomRaider

Hey everyone, thanks in advance for you time and knowledge. Long story short, I'm an absolute idiot

I have a 2006 WRX MT that has been STI swapped. The tune that was on the car when I got it was extreme to say the least.
I was looking at the WRX roms alongside the STI roms and somehow managed to name one of the STI roms to the name I wanted to flash onto my car. I ended up flashing a ROM meant for an A2ZJE11J ECU onto my A8DH201X ECU.

Now ECUFlash cannot read the ECU and gets stuck at Sending Key [1] the closes the interface.
I'm assuming this is because of the incorrect ROM and ECUflash trying to use the incorrect key.
I have verified it gets into Test mode.
Romraider logger will connect and read the codes fine

Any ideas on how to fix this?

Relevant ECUflash output:
[14:23:12.391] J2534 API Version: 04.04
[14:23:12.391] J2534 DLL Version: 1.02.4870 Feb 3 2017 23:36:31
[14:23:12.391] Device Firmware Version: 1.17.4955
[14:23:12.391] Device Serial Number: TAlvqK*T
[14:23:15.866] kernel get version
[14:23:16.073] interface close
[14:23:16.089] J2534 API Version: 04.04
[14:23:16.089] J2534 DLL Version: 1.02.4870 Feb 3 2017 23:36:31
[14:23:16.089] Device Firmware Version: 1.17.4955
[14:23:16.089] Device Serial Number: TAlvqK*T
[14:23:16.575] VIN:
[14:23:16.781] CVN: F8570952
[14:23:16.890] interface close
[14:23:16.922] J2534 API Version: 04.04
[14:23:16.922] J2534 DLL Version: 1.02.4870 Feb 3 2017 23:36:31
[14:23:16.922] Device Firmware Version: 1.17.4955
[14:23:16.922] Device Serial Number: TAlvqK*T
[14:23:17.098] SSM2 init
[14:23:17.246] SSM2 ECU ID is 4312594006
[14:23:17.323] Requesting Seed...
[14:23:17.370] Sending Key [1]...
[14:23:18.028] interface close
[14:23:18.028] interface close

assuming you've tried battery disconnect/reconnect and trying to flash again then it may be time to build a SHboot cable:
https://www.tactrix.com/index.php?option=com_content&view=article&id=66:reflashing-subaru-sh705x-ecus-using-the-renesas-boot-mode&catid=42:ecu-repair&Itemid=41

or

https://romraider.com/forum/viewtopic.php?f=33&t=7384

So both are same year USDM ROMs using same flash method (comparing stock ROMs says yes)? Then there should not be any difference on seed key values unless the other is EcuTek/COBB ROM. There is still method to write it even if it is but do you know are those both "stock" ROMs?

Also, if other one is K-Line and other is CAN, it should also be possible to flash it. If you want, you can send me ROMs so I can compare and wihout calibration part, just remove everything above 0xC0000.

Thanks guys
I've started down the path of sh bootmode.
Neither rom were ecutek/Cobb so I think something just massively messed up. I'll let you know how it goes!

Thank you for your guidance

I flashed the stock ROM last night via the serial connection and EcuFlash. It went well and all is good now!

Thank you again for your help