OK, before anyone goes off the deep end I have searched and searched and searched and I am still seeing a TON of mixed information on iwsti.com, openecu.org and on here regarding what methods to use to pull the flash off of a 2007 STi Limited.

Could someone be so kind as to step me through the following -

1. What tactrix cable I will need, I currently have one from the 2005 Lancer Evolution I had, will this work? My assumption is no.
2. What version of ECUFlash software I need.
3. Are there any connectors or wires under the dash I need to jump?

If someone could just do a step-by-step from start to finish I would be the happiest guy in the world, heck I would even paypal $5/10 for that persons time for the information PM'd to me as long as it works.

Please.

Tactrix cable from your evo right?
the 1.3m or something like that

Yes, it'll work

Use ECUFlash 1.29a (the latest)

and there is 2 green connectors underneath the fuse box

I notice you have an 07 sti limited, I dont think ecuflash works with the 07 sti's (yet)

Installed 1.29a all drivers are good and cable is connected and being seem (using 1.3M) version of cable which is compatible with 2005-2006 DBW WRX/STi that I have been told to use from some other people that got it to work (supposedly).

Put car into test mode by connecting to green connectors under driver's side dash.

Attempted to pull ROM but got FFFF0000 0008 error in the log, almost as if the software is not able to trigger the ECU to release the code, but not completely sure.

Everything works fine on 2005 Lancer Evo 8 without any problem so I have elminated everything but the software.

Do the radiator fans cycle when you plug in the diagnostic connectors?

yes, the fans cycle continuously and the check engine light on the dash also flashes.

everything is golden and acting as it should.

ev8siv3 pulled a rom from an 07 sti limited. You might want to ask him if he did anything different. That is the only 07 sti rom that I've seen.

I have also heard that the green connectors also need to be plugged in under the passenger side kick panel also.

I will check that also when I get home and see if plugging in all 4 connectors gets me past the error.

There are, but from what I've heard, you won't enter test mode if those are already disconnected (i.e. radiator fans cycling, etc.). But let us know if you figure it out. No one has flashed an 07 sti yet either with Ecuflash that I know of.

I think someone tried, but the persons car ended up with a new ECU (take one guess).

I think someone tried, but the persons car ended up with a new ECU (take one guess).
The only attempt that I know of was flashing an 06 sti rom on to the 07 sti. No one has read the 07 sti, made a change, a flashed it back.

I tried it with ecuflash and it did not work

I used Ecutek its superior IMHO anyway

Ap2 is ciomming out soon also

ev8siv3 pulled a rom from an 07 sti limited. You might want to ask him if he did anything different. That is the only 07 sti rom that I've seen.His user name on these forums is turboge (http://forums.nasioc.com/forums/member.php?u=35076). Why not PM him?

Also, it was determined that the current version of EcuFlash, 1.29a, is unable to read/write to the US 2007 WRX, but an older version of EcuFlash, 1.28, does work. You can read a discussion about this at http://forums.openecu.org/viewtopic.php?p=10103#10103 and you can download the 1.28 version of EcuFlash from http://openecu.org/downloads/ecuflash_setup128.rar.

Also I have an archive of the older stuff as it came out, if anyone wants a backdated version.

Well, I have come to the conclusion after installing ECUFLash 1.28 fresh on 2 laptops and connecting and following everyone's instructions that the 2007 STi ECU ROM cannot be read with ECUFlash.

I am almost convinced now that the people who are claiming they have read a 2007 STi (Ltd. or otherwise) are not being very truthful.

The ECU in the 2007 WRX and 2007 STi are different, so it might work for the plain vanilla WRX but it certainly DOES NOT work on the 2007 STi.

Thanks to everyone for their help. Guess I'll wait until COBB AP2 comes out.

The rom has been read from an 07 sti (limited) with Ecuflash. I assure you it is not a myth.

The rom has been read from an 07 sti (limited) with Ecuflash. I assure you it is not a myth.

+1 I was just looking at one in enginuity yesterday...

Lots and lots of tables:eek:

Ecuflash 1.29a uses different drivers for the Openport/Tactrix cable compared to any previous version. They're installed automatically when you install Ecuflash, but the installer doesn't uninstall the old versions. This has caused lots of problems.

Whenever you go from 1.29a to any old version, or vice versa, you should uninstall Ecuflash AND the Openport/Tactrix drivers via Control Panel, Add/Remove Programs. You should see one entry for Ecuflash, another TWO for the drivers. Uninstall ALL THREE, then reboot. Once you've done that, install the version of Ecuflash you want to try.

I would not draw any conclusions until you've done this. This is a pretty basic troubleshooting step.

Here are the ROMs that have already been posted on openecu.org:
2007 USDM STI Ltd. http://freon.shackspace.com/car/ecu%20and%20tuning/openecu/A2UG000J%20MY07%20STi.hex
2007 USDM WRX http://freon.shackspace.com/car/ecu%20and%20tuning/openecu/07_WRX_MT-A8DK100X.HEX

+1 I was just looking at one in enginuity yesterday...

Lots and lots of tables:eek:
Those are just preliminary definitions for that particular 07 sti rom. I haven't bothered messing with it as I have yet to hear of anyone flashing the 07 usdm sti with Ecuflash with success. However, the 07 wrx is not a problem and has been added to the latest definitions (usdm and adm). Also, the adm 07 sti does not have the same funkyness, so I'm guessing we are just the lucky ones.

Ecuflash 1.29a uses different drivers for the Openport/Tactrix cable compared to any previous version. They're installed automatically when you install Ecuflash, but the installer doesn't uninstall the old versions. This has caused lots of problems.

Whenever you go from 1.29a to any old version, or vice versa, you should uninstall Ecuflash AND the Openport/Tactrix drivers via Control Panel, Add/Remove Programs. You should see one entry for Ecuflash, another TWO for the drivers. Uninstall ALL THREE, then reboot. Once you've done that, install the version of Ecuflash you want to try.

I would not draw any conclusions until you've done this. This is a pretty basic troubleshooting step.

Here are the ROMs that have already been posted on openecu.org:
2007 USDM STI Ltd. http://freon.shackspace.com/car/ecu%20and%20tuning/openecu/A2UG000J%20MY07%20STi.hex
2007 USDM WRX http://freon.shackspace.com/car/ecu%20and%20tuning/openecu/07_WRX_MT-A8DK100X.HEX

Let me be clear -

1. I am being TRUTHFUL when I say to all of you that I have read and re-read all the instructions (in spite of my background) and properly removed and installed the software a dozen times with the same results on my first laptop that I used.

2. I am not trying to shove my weight around, let me give you just a bit of my backgroud. I've got close to 15+ years as a Novell & Microsoft Engineer, so technically I understand the basics, (i.e. Add/Remove programs, uninstalling drivers, etc.). I won't even get into stripping down the registry...

3. As I stated clearly earlier, I installed ECUFlash 1.28 on my personal laptop at home and on my work laptop after the other laptop I used was giving me those 0008 codes in the log. NEITHER of these two laptops ever had ECUFlash 1.29a installed on them, so my installation of 1.28 was FRESH, CLEAN, PRESTINE and NOTHING had to be rolled back. Both laptops now exhibit the same behavior as the first laptop I tried. RESULT: all 3 laptops do the same thing.

4. Again, I have already read/flashed other vehicles including my 2005 Lancer Evolution WITH SUCCESS. No problems. I have ruled out any hardware issues at this point, and as far as software issues go ECUFlash is communicating properly with the Tactrix cable.

Has anyone else that has offered suggestions on this thread actually truthfully TRIED to pull the ROM from a 2007 STi? The impression I get is everyone thinks it has been done, but how many on here have done it successfully with ECUFlash?

The only other things I can think of that may be an issue -

Different revision of ECU in my car
Maybe a different ECUFlash ECU trigger code needs to be in the software, like the EVOs.

The impression I get is everyone thinks it has been done, but how many on here have done it successfully with ECUFlash?
One person has at least read the rom. Have you tried PMing turboge (or ev8siv3 on the Enginuity boards)? It has been done, as we have a copy of it. No one knows if flashing will work, however.

I have not PM'd either of these guys yet. I know we have a copy but who knows what has been done to it. I would prefer to get my ROM off of my ECU since I know it works and would like it for archival purposes in case these new Subaru flashes don't entirely work out or end up detuning the car slightly that way I can flash back to what I had.

The point was that a rom has been read from an 07 sti limited since you seem to think that it is some myth or something.

Fine, the ROM has been read on a 2007 STi. Unfortunately, I don't belive it has been pulled with ECUFlash. Apart from me PM'ing the 1 or 2 individuals the concensus is that nobody responding within this thread or on this forum has READ it with ECUFlash 1.28/1.29/1.29a.

Nothing personal, but I trust the ROM I can pull rather than what someone else says is from an 07' STi.

Again, I appreciate the information everyone.

Fine, the ROM has been read on a 2007 STi. Unfortunately, I don't belive it has been pulled with ECUFlash.
The guy who pulled it is on the Enginuity team. So am I. He has read/flashed quite a number of Subarus. I've disassembled the 07 sti rom question, created the preliminary defs for it and I guarantee it is genuine.

While I believe the ROM has been pulled from an 07 STI, I tried to do it from my just reflashed 07 STI and got the same errors. I'm going to try uninstalling everything and using 1.28 to get it maybe later tonight or tomorrow. I was able to log data fine with Enginuity so the connection works. I also got all the blinking lights and cycling fans so the machine was in diagnostics mode.

I'll report back when I try again with 1.28. I'm also using a 1.3 version of the cable based on how it was detected in EcuFlash. I just bought the cable this week and got it today.

The guy who pulled it is on the Enginuity team. So am I. He has read/flashed quite a number of Subarus. I've disassembled the 07 sti rom question, created the preliminary defs for it and I guarantee it is genuine.

Thanks for the reply. It would be nice to know what you did to pull the ROM using ECUFlash, it would add more credibility to the discussion on how to pull it using ECUFlash.

You didn't state how you pulled it BTW, so I guess my final comment is again what did you use and how did you do it?

While I believe the ROM has been pulled from an 07 STI, I tried to do it from my just reflashed 07 STI and got the same errors. I'm going to try uninstalling everything and using 1.28 to get it maybe later tonight or tomorrow. I was able to log data fine with Enginuity so the connection works. I also got all the blinking lights and cycling fans so the machine was in diagnostics mode.

I'll report back when I try again with 1.28. I'm also using a 1.3 version of the cable based on how it was detected in EcuFlash. I just bought the cable this week and got it today.

PhatBoyG,

Everything you described was the same for me before the REFLASH and after the REFLASH with (411 revision). My cable and software are working fine because I can flash my old 2005 Lancer Evolution GSR, and Enginuity will log data for me.

Until someone explains how they pull it using ECUFlash step-by-step I am still skeptical that it was done using ECUFlash.

Results of latest test (using Version 1.28.716) :(

[09:46:26.156] ssm2_init
[09:46:26.390] ssm2_init
[09:46:26.390] ssm2_init
[09:46:26.406] ssm2_init
[09:46:26.421] ssm2_init
[09:46:26.437] ssm2_init
[09:46:26.453] ssm2_init
[09:46:26.468] ssm2_init
[09:46:26.484] ssm2_init
[09:46:26.500] ssm2_init
[09:46:26.703] kernel get version
[09:46:27.234] validating denso kernel ram area addr: FFFF0000 len: 0008

Thanks for the reply. It would be nice to know what you did to pull the ROM using ECUFlash, it would add more credibility to the discussion on how to pull it using ECUFlash.

You didn't state how you pulled it BTW, so I guess my final comment is again what did you use and how did you do it?
I didn't do it. Tuboge (ev8siv3) did. Which is why I said to PM him.

I just ordered the 1.2 DBW cable for Subaru's. This is the only thing I can think of that is the problem. I am currently using the 1.3m cable...which, if you look on the tactrix cable compatability chart it is supposedly compatible and should not have a problem.

Oh well, live and learn if this was the case!

Someone who just flashed an 07 sti (itp) said he used Ecuflash 1.28, but had to change to different com port. I see that you responded to his thread, did he tell you that you have to use the 1.2 cable as well?

Yeah, ITP and I have been PM'ing back and forth. The only difference between all the issues that were brought up were the cable model differences, I was using 1.3m ITP was using 1.2 DBW.

I hope this fixes it...

I hope that resolves it. If that is the case, I'll be returning my brand new 1.3 and asking for the one I ordered (the 1.2 for WRX DBW).

I hope that resolves it. If that is the case, I'll be returning my brand new 1.3 and asking for the one I ordered (the 1.2 for WRX DBW).I don't think Tactrix still sells the 1.2 anymore. If you order the Subaru-only cable, I think you'll get the 1.3S version.

What is the exact hardware difference between 1.2 and 1.3 Openport as it relates to Subarus?

Markeddy,
Most people do not know that there was a driver revision that virtually requires these steps, let alone know to do this to fix the related problems. This is why I posted and didn't quote or direct it at anyone. There is no need to draw any conclusions if you're not excluding a different known problem. If you already did, more power, but it hasn't been posted yet here and most people do not automatically know. I think you can appreciate that this thread isn't about you alone, OP or not.

So, I still recommend the steps I posted earlier to anyone trying to get it to work.

I have a 1.2 cable but none of the local Subaru club members has bought an '07 yet. I'll post on our local BB to see if there are any new '07 owner members willing to let me try.

It's perfectly possible there is already a new ECU revision that breaks it, meaning some 07's work and some don't. I think Colby is still looking for someone to lend him an ECU. That would probably be the fastest way to get this to work for certain.

I have a 1.2 cable but none of the local Subaru club members has bought an '07 yet. I'll post on our local BB to see if there are any new '07 owner members willing to let me try.It's very possible that even the 2007 Legacy GT, which now supports OBD-II only via CAN, can be read/rewritten using the 1.2 cable and EcuFlash 1.28.

ECUFlash 1.30 was the ticket for me, I've pulled my ROM and loaded into Enginuity with the preview (beta) definition file. Once the official definitions are available and some others have reflashed their cars, I'll likely give it a shot and take it to a well known tuner for some adjustments.

I won't be first, but at least I can read the ROM from the car now, worked first try with 1.30 whereas it failed every time with 1.28 and 1.29.

Enjoy.