: HOW TO: Recover your EvoX ecu after a failed reflash.


evoscan
07-08-2010, 02:45 PM
Does your EvoX not start after a failed reflash?
Did you flash a corrupt ROM file to your ECU?

Does your FANS still run after a reflash when you turn the key on?
and the ecu now won't reflash?

Some people call this a "bricked" ECU.
YES, you can "recover" your ecu to a working state again.

Do you get this message when trying to do a reflash?
[23:15:42.343] J2534 API Version: 04.04
[23:15:42.343] J2534 DLL Version: 1.00.3017 Apr 8 2010 14:16:53
[23:15:42.343] Device Firmware Version: 1.10.3038
[23:15:44.000] sending init sequence 1 (0001)
[23:15:47.218] sending init sequence 1 (0003)
[23:15:50.437] sending init sequence 1 (FFFF)
[23:15:53.140] no response to any known code
[23:15:53.140] interface close

This is sometimes a symptom of a faulty cable also. But not very often. (about 1% chance of a faulty cable)
Try your cable on another Mitsubishi just to be sure the cable is good.
Mitsubishi Dealer tools require minimum 9.7 - 9.8 volts for reflashing, I would highly recommend a minimum of 10.5-11.0 volts. Normal voltage on most EvoX during reflash is between 11.9 and 12.2 volts.

STEP 1: You need to pop your hood of the car, and remove your ecu, and wire the ecu direct to your op2 cable.

Connect OpenPort 2.0 USB Cable and Power Supply to EVOX ECU Pins:

http://www.evoscan.com/images/stories/EvoX_ECUPins760.gif
Figure 1. EvoX ECU pinouts, looking straight-on at the pins on the ECU when its out of the car.

http://www.evoscan.com/images/stories/EvoScan_OpenPort_Cable_Plug.jpg
Figure 2. OpenPort 2.0 USB Cable pinouts, looking straight-on at the pins on the Cable when its out of the car.

Connect the ECU to OpenPort 2.0 and Power Supply using the following wires:
EvoX ECU Pin OpenPort 2.0 Cable 12v-15v Power Supply
pin 71 pin 4 or pin 5 Negative/Ground (-) Black
pin 73 pin 16 12v Power Supply (+) Red
pin 82 pin 16 12v Power Supply (+) Red
pin 104 pin 16 12v Power Supply (+) Red
pin 103 pin 12
pin 80 pin 7
STEP 2:
a) Open ECUFlash
b) Load your last known good ROM file. (try not to use the ROM file you used during the failed flash, because it maybe corrupt.)
c) Select the from the ECUFlash menu: Files->Options
http://www.evoscan.com/images/stories/EvoX_RecoverA1.gif

d) Select "Flash Recovery Mode" and tick the box "Use alternative flash recovery mode"
http://www.evoscan.com/images/stories/EvoX_RecoverA2.gif

e) Ensure your OpenPort 2.0 cable is connected and the EcuFlash status bar shows "RECOVERY MODE"
http://www.evoscan.com/images/stories/OpenPort_20_Recovery_Mode.gif

f) Press "Write to ECU" as you normally would... If successful, recovery mode will start writing to ECU like this.
If it doesn't, go back and check all your wiring again.
http://www.evoscan.com/images/stories/EvoX_RecoverB.gif

Recovery Reflash completed...
http://www.evoscan.com/images/stories/EvoX_RecoverC.gif

g) Unplug all your bench wires from the ecu and go and put it back in the car. Plug in your OpenPort 2.0 cable to the car and laptop.

h) Turn EvoX Key to ON position (yes you will probably hear the Fans strangely running still.)

i) go back to the EcuFlash software menu: File->Options->Flash Recovery Mode and untick "Use alternate Flash recovery mode"
http://www.evoscan.com/images/stories/EvoX_RecoveryModeOff.gif

j) Reflash your last known good ROM to the ecu.

k) once the reflash is successful, turn the key OFF, then back ON and start your car!!!! SUCCESS.

If you find a better way to get the VMFI (ecu pin82) +12 volts enabled from the ETACS ecu. I think when the ecu is bricked the immobilizer code isn't reported from the main ecu, so the VMFI relay isn't activated, hence the need to remove the ecu from the car, and reflash it on the bench.
Let me know if you find a way to force 12v on pin82 without splicing any wires, then we could do it in the car without removing the ecu.

Yxd68
07-08-2010, 02:51 PM
Good info!

Thanks!

VGergo
12-06-2010, 09:57 PM
Hello

I will mad from that evo x. The story was begining with start up issue with DW1000cc.. tried everything, cranking ipw table, latency at low voltage no succes. sometimes the car coundt start up and it get worse.. when under idleing or cruesing the car stopped :D Fuel trims were in line always. So we put back the stock injectors flash back everything to oem. The car startup well, but on idleing is was stopped again !?!? and can not startup ?! cranking cranking but nothing ! wait some minutes and start up again. Any idea ? fuel pump or realy problem maybe ? the fuel pump relay was changed to the upgraded oem.

Ok, the main problem after all.. the owner was trying to play with the relays and fuses but unfortunatelly the ignition was turned on and the OP2.0 cable connected to the OBD port, we didnt touch anything on the notebook, just changeing the relays checking the fuses under the hood, when we heard the sound like you see under flashing ?!:freak: Like the flashing method was started with the relay changing ?
than the fan startup, lot of cel codes, can not cranking and ofcourse no response to anycode... like the ecu bricked :O
So I removed the Ecu wired the cable as Evoscan posted here between the Ecu and OP2.0 cable.
The power was a scooter battery, constant 12.05 volt. The power and ground wire was connect on the battery too. Is it should be ok right ?

With ecuflash 1.42.2595 I coudnt achieve the EcuFlash status bar shows "RECOVERY MODE" ?! why ? the 1.42.2595 recovery mode is not working ?

Than I downloaded the ecuflash_1433150_win_beta, with that recovery mode status was ok. I can write in the ecu the stock oem rom but until 74 % !! there it was stopped ! the ecuflash said the flashing was ok everything is succes but same issue no response to any code fans are on. I can not connect with ecu in the car . ( without alternaitve reflash mode)

Ok, than I realized the problem, recovery mode stopping at 74%. So i checked in the picture here Evoscan working with 1.43.3000 beta ecuflash. I got one but same problem the recovery flash stopping at 74% . Why ? what coud be the problem ? Any idea how to solve it, what was happened with that ecu ?

for me the complete stroy is unbeliviable.. without flashing how can we brick the ecu.. why recovery write stopping and like this.


here is the log : http://www.gigasize.com/get.php?d=pvp7b7j481b

zikizira
12-07-2010, 10:52 PM
Is there a better way to connect the pins to the ecu and openport plug? It seems not too easy to keep wires connected to the OP2 pins, specially 4-5 and 15-16 which are quite close to each other.

Maybe if I get a OBDII extension from Tactrix and cut the female connector in order to use its wire directely into the ecu pins?

Someone could build a kit with the proper connectors, including those for the ECU.

VGergo
12-08-2010, 02:02 PM
any idea why the recovery write stop at 75% ?

boostin20
12-13-2010, 01:26 PM
Sub'd for later

jojobanks
12-25-2010, 03:53 AM
I'm no genius with this stuff... but if it's just a relay not activating that's causing all of this, why can't you just jump the relay? Then you wouldn't have to take the ecu out of the car. Or am I missing something?

evoscan
01-05-2011, 12:46 PM
you are correct mr jojo, jumping the relay is the obvious idea. to be honest, I had completed the recovery flash, and therefore had no need to continue try jumping relays :) we just wanted to go boosting in the EvoX instead of playing under the hood, lol. if you try it and it works, let us know. If i need to recovery reflash ever again, I'll be sure to try that out first.

Irishman130
02-02-2012, 07:29 AM
Okay, so I'm going two months now on this problem, I received a tune on the dyno and during a run the bolts on my turbo backed out breaking a gasket. Besides that when the car came of the dyno everything went crazy, the car would not crank, the fans turned on when the key was in the on position, and the car threw every check engine light there is. To shorten up the story, I'll go to the end result right now. The ecu was benched, and the computer connects and flashes, but once the ecu is put back into the car, you cannot connect to the ecu to load a flash, what's wrong! Please help it's been way to long

Irishman130
02-02-2012, 07:30 AM
Oh yea the turbos completely fine now, but I don't think that really matters

gamaliel612
02-02-2012, 09:45 AM
subd in case needed

GSRony
03-10-2012, 01:12 PM
Does this method also work if your fans aren't spinning? I'm not bricked but I definitely locked my self out as I can't read or write anymore. Car run's fine but after writing my stock rom back I'm locked out. Would benching my ECU place it in programming mode so I can flash again? I've tried a different laptop already, reinstalling, etc. Thanks!

- rony

Golden
03-10-2012, 01:26 PM
It should. I have the same issue with a car that I'll probably have to bench today.

It runs. But I can't read or write the ECU. Sometimes it gets stuck in the "fans on" state and other times it goes back to normal mode and the car runs.

qwertykerr
03-10-2012, 01:29 PM
Does this method also work if your fans aren't spinning? I'm not bricked but I definitely locked my self out as I can't read or write anymore. Car run's fine but after writing my stock rom back I'm locked out. Would benching my ECU place it in programming mode so I can flash again? I've tried a different laptop already, reinstalling, etc. Thanks!

- rony

I would think it should fix it.... I had to bench my ECU because when I bought my car used the ECU was locked so I couldn't read\write from it. Once I benched it the ECU reset and then i was able to read\write whatever I wanted to it. I benched it with the stock ROM.... not that it may matter?

GSRony
03-10-2012, 02:05 PM
Thanks for the quick reply's guys, I'm off to radio shack to make this harness. Going to use a powersupply + psu/multimeter tester to make sure I'm getting the right voltages. Will report back later :thumbup:

bravozero
03-10-2012, 03:45 PM
Sub'ed in case this is needed in the future.