WTF!?? EcuFlash suddenly doesn't work....
 

CAR:
2006 Lancer Evolution IX

CABLE&SOFTWARE:
Tactrix Inc. OpenPort 2.0 Rev E
TAyXcd6M
EcuFlash Version 1.42.2595

PROBLEM 1:
Although the cable does record logs via "EvoScan v2.7", yesterday it started getting the following error.

[19:21:50.072] EcuFlash Version 1.42.2595

[19:21:50.072] OS Version Windows Vista

[19:21:50.072] Qt Version 4.5.0

[19:21:50.090] 56 memory models read.

[19:21:50.091] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata

[19:21:50.430] 343 ROM metadata models scanned.

[19:21:50.430] checksum module "subarudbw" loaded.

[19:21:50.430] checksum module "mitsucan" loaded.

[19:21:50.430] flashing tool "wrx02" loaded.

[19:21:50.431] flashing tool "wrx04" loaded.

[19:21:50.431] flashing tool "sti04" loaded.

[19:21:50.431] flashing tool "sti05" loaded.

[19:21:50.431] flashing tool "mitsukernel" loaded.

[19:21:50.431] flashing tool "mitsukernelocp" loaded.

[19:21:50.431] flashing tool "mitsubootloader" loaded.

[19:21:50.432] flashing tool "shbootmode" loaded.

[19:21:50.433] flashing tool "shaudmode" loaded.

[19:21:50.434] flashing tool "subarucan" loaded.

[19:21:50.434] flashing tool "mitsucan" loaded.

[19:22:20.214] J2534 API Version: 04.04

[19:22:20.215] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29

[19:22:20.215] Device Firmware Version: 1.10.3020

[19:22:24.806] sending init sequence 1 (0001)

[19:22:28.037] sending init sequence 1 (0003)

[19:22:31.265] sending init sequence 1 (FFFF)

[19:22:34.494] sending init sequence 1 (F0F0)

[19:22:37.209] no response to any known code

[19:22:37.210] interface close


I uninstalled and reinstalled EcuFlash with no luck. The car will not read or write from the Ecu. I even attempted writing to the car while it was running, and still no luck.

PROBLEM 1 SOLVED:

The connection between the second, white plug and the wire that feeds it back to the OBD-ii box unit, had failed.

The wire furthest to the right in this picture:

http://carview-img02.bmcdn.jp/minkar...2640355/p1.jpg






PROBLEM 2:

NOW, if i try opening any Tephra V7 based rom, i get this:

"Ecu Flash could not recognize this ROM image using any of the current definitions. You can choose one of the following options:" ....

Problem 2: SOLVED: The roms had to be moved into the a different folder before being opened. I suspect it had something to do with the reinstallation of EcuFlash and or the location of XML files (although i did reinstall all the Tephra files and it still didn't work until i moved the rom files as well. Still having issue with problem 1.

Tuning your car is hard enough. It's total BS when the hardware/software fight you. gerrrrrrr.


Can anyone help, :crap:

did you add the tephramod file to openecu > ecuflash > rommetadata > mitsubishi > evo?

no idea about problem #1 though. try reinstalling

The Tephra moded Roms had been working properly until yesterday. Any chance you have a link to this file so i can reinstall it?

Thanks for the reply either way :thumbup: :mitsu:

try https://www.evolutionm.net/forums/ec...-problems.html if you haven't

Thanks for the recommendation, but i drove the car for about 10+ minutes and then pulled over to get gas. As soon as I stopped, i attempted the reflash, and still didn't go :crap:

ah yeah man im having same problems

EDIT, fixed Problem 2 (again..)

I heard before that you can only flash the stock ECU so many times and then it's locked. Is that true?

Just an update:

I tested the battery, it's read 12.6V, even after sitting in the cold for over 3 hours.

I put a battery charger on it, and checked evo scan, it said it was reading 14.66v volts with the charger on it. In both cases, the cable still wouldn't read or write to the rom... It must be a physical problem inside the cable??

Did you get your ECU mapped from a tuner? Some ECU tuners change the initiation code and prevent it from being accessed.

If so, try ECU unlocker program.

It is true that ECU flash memory has limited number of "write" cycles.

NAND flash memory (such as USB memory stick or SD memory card) usually has about million times write cycle (if it is SLC-type, MLC-type usually has 1/10 that of SLC), but ECU flash memory is "NOR" flash memory, so it has much fewer write cycles.

But as I said, there is limited # of "write" cycles, not read. So you should be able to read the rom, even if you may have problem writing it.

PROBLEM 1 SOLVED:

The connection between the second, white plug (the second dash plug in for tuning) and the wire that feeds it back to the OBD-ii box unit, had failed.

The wire furthest to the right in this picture:

http://carview-img02.bmcdn.jp/minkar...2640355/p1.jpg

so did you have to get a new cable for it to work?

I had the same problem (problem 1) when I first tried to read my ECU.
That damn TRS mini jack on the white plug doesn't connect very well to the OBD2 connector.
I had to "fanagle" the connector just so to get a good connection. Would like to see a better connector in a future release of Openport.

i feel like i'm getting the opposite problem, the white cable snaps in real snug but the black obd connection is a little flimsy