Dealer reported codes are
P1153 02 Sensor Range Performance
P0390 Camshaft Position Sensor B Circuit Bank 2
P0365 Camshaft Position Sensor B Circuit Bank 1
P2094 OCV Circuit Open Bank 2
P2090 OCV Circuit Open Bank 1
P0019 & P0017 Crank/CAM timing for both exhaust sprockets

Not sure of P0171, might be a lean code.

VIN starts with JF1GR89689L

 

Pictures to help with identification

Main Bay

BB AB 2222

U20

128107 FC-TY856UW1MA

AVCS plugs, 3 and 2 wire

AVCS plugs, showing connection type

Passenger side, what looks like a fuel rail and some angle grinder action

Let me know if there are other angles needed to help figure out what motor this is and if replacing the heads would be a solution.

 

It looks like you don't have exhaust AVCS, I think the Cobb tech is correct.
Pic U20 - The smooth surface next to the ground strap is where your AVCS solenoid would be, if you had one.
Pic AVCS plugs, showing connection type - that hole on the head is where your cam position sensor would, if you had one.

I'm guessing engine blew and they swapped in a JDM engine, this is not uncommon.
I'm not sure how the missing AVCS is supposed to be addressed though.
Could be that you just get a tuner to zero out the exhaust AVCS tables and turn off the codes.
Or you'd have to hunt down a JDM ECU to go with the engine.
You can always swap in a used EJ257 also.

 

Thanks for the confirmation!

A used EJ257 is going for about half the cost of the car right now, so that is out.

My choices are to figure out what model number of dual AVCS heads to get to swap out on the 2L or to file a lawsuit against the dealer that sold it to me. The COBB shop said that the car is "untuable" in its current config. Dunno if that is because of rules, their ability or the access to parts.

I enjoy a challenge and fixing up cars, so I would rather make this usable as a 2L.

These posts are mainly to figure out if this is common, which you say happens and understand what roadblocks I am facing, like is there any tuning hardware that would help. If an Accessport or other thing would allow the setting of AF ratios after the swap.

The car is almost drivable currently. It just the jerky hesitation after 4K RPM and the 11MPG that make it an issue.

Any idea what 2L heads would work on a JDM block?

 

It’s untunable because Cobb can no longer turn the codes off.

 

Cheapest option would probably be open source tuning it and getting rid of the accessport.

 

Would an open source option bypass the AVCS codes?

Where is a good place to start researching this option?

 

Best place to start is to find a tuner that can tune with open source standalone ecus

 

And you also need to find out if a single AVCS map can be put onto a dual AVCS ecu.

 

Just ordered a Tactrix 2, watching training videos from @hpa101 on yt. Thanks for the insights, looking like a possible solution. If this fails looking at a LINK Ecu and if that fails, back to finding some compatible Dual AVCS heads.

Going to try the mention of zeroing the exhaust maps. Will post again when I get some data logs and start the tuning process.

 

Got the Tactrix 2.0
Plugged it in and got the following messages in ECUFlash when reading ROM

[17:21:40.583] using metadata XML ID read_subarush7058can from file C:/EcuFlash/rommetadata/read templates/read_subarush7058can.xml
[17:21:40.594] J2534 API Version: 04.04
[17:21:40.594] J2534 DLL Version: 1.02.4870 Feb  3 2017 23:36:31
[17:21:40.594] Device Firmware Version: 1.17.4955
[17:21:40.594] Device Serial Number: TAUvIhXA
[17:21:45.779] kernel get version
[17:21:45.984] VIN : JF1GR89689LXXXXXX
[17:21:46.111] CVN : 56839FD8
[17:21:46.111] Requesting Seed...
[17:21:46.111] Sending Key...
[17:21:46.126] interface close
[17:21:46.132] interface close

It does not seem to want to read.
Looking this up there is mention of green cables in the ECU area in the footwell, but not for a 2009, yet there are cables.

There are also some plugs that are not connected, does this look stock?

Asking here to see if someone has already done this and what next steps should be.
Thanks for any help

 

The green plug needs to be plugged in before you flash each time and then once flashed, you unplug it. Do you have romraider setup already also?

 

On my 08 STI the green plug does not need to be plugged in.
Did you download ecu definitions? https://www.romraider.com/forum/topic3808.html
You can try opening your stock ROM in EcuFlash and doing a compare: https://www.romraider.com/forum/viewtopic.php?f=35&t=7591

 

Ok, tried connecting the green cable and it did not seem to change anything, still no read.

Updated the Defs from SubaruDefs/ECUFlash/subaru standard/Impreza STi at Alpha · TD-D/SubaruDefs linked on that 3808 page.

The instructions on 3808 did not include any read definitions, so C:/EcuFlash/rommetadata/read templates/read_subarush7058can.xml has not been changed.

Tried to do another read and got same response as posted above.

Been searching around and people are mentioning that the previous owner may have not unmarried an EcuTek or AccessPort before transferring the vehicle.

Some say you can flash over the existing ROM but can not read it first.

This gets a bit sketchy as using a stock ROM would be for the 2.5L and it has the JDM 2L in it.

Not looking to brick it or jump to a standalone just yet, any ideas on how to proceed?

 

Download AZ1G201I or AZ1G202I from: https://www.romraider.com/forum/viewtopic.php?f=35&t=7591
Open the downloaded ROM in EcuFlash and after it loads try the compare or read function to see if it works.

 

Ok, downloaded it from that link.

Here is the procedure I used for this attempt:
Car is Off
Connect dongle to OBD2
Connect USB to laptop
Open EcuFlash
Load ROM file
Click Compare
Turn car to On, not to start
Click Test

Here is the result that came back.

[15:09:08.044] opening rom file C:/Soob/AZ1G202I.HEX
[15:09:08.055] Unable to find parent metadata 32BITBASE
[15:09:08.055] AZ1G202I (4 tables) inheriting AZ1G201I (360 tables)
[15:09:08.062] 1048576 byte image read.
[15:09:08.065] using metadata XML ID AZ1G202I from file C:/EcuFlash/rommetadata/subaru/Impreza STi/AZ1G202I.xml
which inherits XML ID AZ1G201I from file C:/EcuFlash/rommetadata/subaru/Impreza STi/AZ1G201I.xml
[15:09:13.632] J2534 API Version: 04.04
[15:09:13.632] J2534 DLL Version: 1.02.4870 Feb  3 2017 23:36:31
[15:09:13.632] Device Firmware Version: 1.17.4955
[15:09:13.632] Device Serial Number: TAUvIhXA
[15:09:28.204] kernel get version
[15:09:28.419] VIN : JF1GR89689LXXXXXX
[15:09:28.543] CVN : 56839FD8
[15:09:28.545] Requesting Seed...
[15:09:28.546] Sending Key...
[15:09:28.553] interface close
[15:09:28.553] interface close

As soon as I turn the car to On, the radiator fans start flicking on and off.
Some other posts mentioned that there should be a few seconds before they start switching in order to connect to the ECU.

Its looking like I either have a bad dongle or the ECU is encrypted or blocked somehow.

 

Since this ECU is not working out, was thinking of getting another stock ECU off eBay to mess with.

But the car has been parked for 2 months and the family stepped in to offer help.

Looks like I am going the standalone rout!

Just ordered a WRXLink V11 - WRX11X

Will post again after it arrives.

 

Not saying there's anything wrong with your procedure, but I usually turn the key on before clicking a button in EcuFlash to read/compare/flash.
Strange that you're not getting any errors. Maybe there's a locked COBB tune on it? I don't know what you would see in that situation.
Good luck with the standalone, hopefully it works well for you!

 

this video helped me a lot

follow up

 

I think it would be cool to try and remove what seems to be a locked COBB tune, while waiting for the standalone.

Anyone know how to unCOBB or unbrick the ECU?
I am fine with soldering if that needs to be done.

The instructions on the Tactrix site are not usable.

 

Look at this thread: https://forums.nasioc.com/forums/showthread.php?t=2200443
But you'll be restoring a stock ROM, which you weren't sure about.
Keep in mind I'm only guessing about it being locked down, just don't know what else it could be.

 

The unbricking path was too difficult, as it looks like creating a PCB from scratch. Curious why a premade does not exist.

But the Link arrived and got it all wired up and installed.
Just need to figure out how to install an IAT and Wideband before first start.

 

I have been posting on the Link forum for direct tech support.
This path is proving to be very difficult as well.
Have been learning AFR/VE/Timing table tuning just to get this thing to run.

Here are the topics so far.

Subaru STI ECU Fault Code 49: Analog Temp 3 above Error High Value

Looking to repair fault code 49 on an 09 STI. The fault code manual says it could be a sensor that stays high when the car is off. I am unsure which part needs testing/replacing. Any help would be appreciated.

forums.linkecu.com

09 STI Connection error: 1019 LINK_NOT_RESPONDING_CORRECTLY

Getting some strange readings on first ECU connect. Connection error 1019 ECU Fault Code 64: IAT Signal Error ECU Fault Code 49: Analog Temp 3 above Error High Value Flash ECU is suggesting to flash to v1.4 from v6.27 After hitting cancel from the Flash window, the 1019 error goes away, but comes...

forums.linkecu.com

USDM Subaru STI x JDM EJ20 - Trigger Calibration Timing Light First Start

TLDR: How important is it to check timing with a timing light for a first start coming from a running stock STI ECU? There does not seem to be a timing mark on the inner, mid or outer ring of the accessory belt pulley to match up with the calibration badge next to the pulley. I purchased an analo...

forums.linkecu.com

Subaru EJ20 Single AVCS VVT and Trigger Settings

Going for first start and wanted to make sure these settings were correct. I only see an option for Quad AVCS, will that work with a single AVCS?

forums.linkecu.com

Subaru STI - APS and TPS Calibration for First Start

In the manual under section 1.8 First Time Startup #3 says to hit F12 and select the Analog tab. #3a then says TPS should span from 0 to 100% but there are no percents listed anywhere. When I do a TPS calibration, noise comes from the dash and it says calibration complete. Doing an APS calibratio...

forums.linkecu.com

Subaru STI - Wideband O2 Options/Debate

Before getting a Link, I was researching aftermarket o2 sensors and came across a lot of conflicting information. Some places said the Link supported any o2 sensor, others said it did not come with a Bosch Wideband controller onboard. The place I purchased the Link from said most should work, but...

forums.linkecu.com

Getting a bit discouraged as the learning curve here is pretty harsh.

 

After watching a bunch of youtube videos, its looking like this engine is a JDM STI EJ207, not the EJ20X, which is a nice surprise.

The Link is proving to be quite difficult to start off with as it needs a few aftermarket sensors to be installed before it will run, which is a catch 22 on being able to get the car to the shop to install those sensors.

I decided to return to the unbricking path and have some great news!
Got a friend that worked on Starlink to help reverse engineer the Tactrix unbrick diagrams and that user wireup from 10 years back.

We successfully got a stock ROM to upload over wired serial to USB! No more "married" ECU roadblocks!
The car runs now too! Going to be making sure no knock is present and keeping it at lambda 1 so it can get to the shop.

Will be creating a new unbrick guide once the parts arrive, should work for quite a few ECUs too!

 

HERE IT IS!!!

https://raw.githubusercontent.com/OhNineSTI/subaru-unbrick/refs/heads/main/Unbrick.pdf

Feel free to share and post it anywhere or make a youtube video with it.
If you come up with other ECU header pinouts or find a typo, let me know and ill add it to the repo.