I have been at this all day and have tried everything I have read to troubleshoot connecting to my 05. Here is what I am getting with ECUFlash V1.29a. It gives me an error and says to see log for details.

[03:56:56.261] Version 1.29.906
[03:56:56.271] 8 memory models read.
[03:56:57.563] 140 ROM metadata models read.
[03:56:57.563] checksum module "subarudbw" loaded.
[03:56:57.573] flashing tool "wrx02" loaded.
[03:56:57.573] flashing tool "wrx04" loaded.
[03:56:57.573] flashing tool "sti04" loaded.
[03:56:57.573] flashing tool "sti05" loaded.
[03:56:57.573] flashing tool "mitsukernel" loaded.
[03:56:57.573] flashing tool "mitsukernelocp" loaded.
[03:56:57.573] flashing tool "mitsubootloader" loaded.
[03:57:10.852] sending init sequence 1 (0001)
[03:57:24.692] sending init sequence 1 (0001)

My cable is recognized in the lower right corner as OpenPort 1.3 Mitsubishi TX14sjay. I also tried Malibujack's unlocker program with no luck.

When I try this with v1.30 I don't get the error...it just says it can't communicate with the ECU. I don't think there is a problem with the cable as it has been used before on my friend's car with no issues. I'm sure everyone gets sick of hearing this in so many threads...but it is obviously a problem. I did 5 hours of searching and trying different things so I feel it is now time to ask for pointers. Any ideas?

 

Got it!!! 5 min after I posted. I'm not even going to tell you the stupid mistake I made. Ugh.

 

No tell us! It will make us feel better about any stupid mistakes we have made, or those we will make in the future!

MB

 

Its probably a good idea to post your solution just so someone searching in the future might be making the same error.

 

Didnt have the cable plugged in all the way on the OBD port I bet :P

 

You guessed it. I plugged that sucker in like 5 times and never got it in all the way

As long as the operator has a brain they shouldn't make this error

 

It happens to the best of us.. That damn connector isn't always easy to seat fully.