smanders

iTrader: (4)

Hello,

I'm not sure if this should have gone here, or the EcuFlash section in the Evo 1-9 forum.

https://www.evolutionm.net/forums/ec...ml#post7600455

UT_EvoX

Real simple fix, don't worry. Open your ROM as usual, go to ECU --> Exit Programming State. Should get the ECU back into a normal state. Write the ROM to the ECU as usual after that, should be fine.

tephra

iTrader: (6)

^^ Try that first

If it don't work then:

1) When a flash craps out half way through:
a) DO NOT TURN THE CAR OFF
b) YOU CAN RESTART THE LAPTOP
c) TRY REFLASHING

2) If you did a) above then (until Colby fixes the inbuilt recovery mode) you need to bench your ECU - Basically:

Use http://www.roadraceengineering.com/e...-ecuwiring.htm as a reference

Looks like you need to hook up:

Power/Grounds:
73 = +12v?
81 = ground
82 = +12v?
93 = ground
104 = +12v?
Just ensure the "power pins" have +12v and the continutity between the ground pins and chassis is 0ohms:

To OBD connector:
90 = CANH
91 = CANL
80 = Kline
103 = pin 8 or 12 ???

If in doubt I would start by measuring the voltage output on the pins you will be "emulating". And also measuring the continuity between the OBD and ECU harness for the OBD connections.

A friend has done this and was able to recover their ECU

smanders

iTrader: (4)

Wow...Great Information!!!!

However, luckily I was able to get the ECU working again.

Here's a recap now looking back:
Last night after the USB unplug/plug sound happened during the flash, EcuFlash progress bar stopped. At that point I was not able to just stop the flash. EcuFlash threw a warning that it cannot stop the flash because it may leave the car in a state where it will not start. Looking through the menus I found the "Exit Programming State". That was the only way I could get EcuFlash to return to normal. But it did not return the car back to normal. The car was still in the flash "write" mode. And I could not get EcuFlash back into the "write" state since it could not initialize the interface. I then restarted EcuFlash. I still could not read or write. I turned the IGN off and back on and tried it all again. I doubled checked all the USB connections to make sure they were snug and they all were. I even move the USB plug to a different port so it would enumerate and reregister and still no luck. So I thought for sure it was bricked. I hoofed it 2 miles back to my home at 1:00am last night in a light rain. I could have called a cab but I needed time to think and blow off some steam. The wife was out of town and the kids were at grandma's so it was a good night for tuning.

After reading the recovery method mentioned in the 1st post, I drove my other car back to my Evo in the morning and gave it a try. Still nothing. I then went and played some golf....that helped.

After reading through everyone's posts today, I remembered that when I did have the IGN in the "on" position the dash seemed to still behave as if it was being flashed. The fans run and just about every light in the dash lights up. So I thought I need to some how get the ECU back to its normal operating state. My plan was to first just try multiple times of reading and writing. If that did not work, I was going to pull the negative terminal of the battery and totally reset the ECU. Luckily, I was somehow able to get a read to work successfully. EcuFlash complained that the image had invalid checksums. Signs were looking good though. I then loaded the last successful image back into the car and wah-lah. The write was successful and the car was finally out of the "write" state. The car cranked right up.

Thanks for everyone's help and the information gathered through this will make me more confident in the future in case I hit any other bumps down the road.

UT_EvoX

Wow...

I just recall having encountered a BSOD in the middle of a flash (Vista 64 + EcuFlash/EvoScan = fail) and the ECU got stuck in a write state. Fixed by using the Exit Programming State option. I had no idea about other potential "brick" scenarios.

Good thing you fixed yours, though

boostin20

Congrats on figuring it out yourself.

tobz

iTrader: (15)

Any more info would be great. I have tried to reconnect the #8 line to the #12 and reflash in alternative mode but i keep coming up with this response.

[15:47:01.318] J2534 API Version: 04.04
[15:47:01.318] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[15:47:01.318] Device Firmware Version: 1.07.2597
[15:47:04.099] sending init sequence 1 (0001)
[15:47:07.384] sending init sequence 1 (0003)
[15:47:10.662] sending init sequence 1 (FFFF)
[15:47:13.946] sending init sequence 1 (F0F0)
[15:47:16.665] no response to any known code
[15:47:16.667] interface close

please help. Thanks

tobz

iTrader: (15)

Ttt

Magnumpsi

iTrader: (2)

Tobz,

I have a couple spare Evo X ECU's laying around. Not sure about the immob. but if you can get around it you may get it to work.

Let me know dude,

Mitch

tobz

iTrader: (15)

Thx Broski!

I'll give u a call if needed.

onboost

Pin 8 or 12 on the obd plug IS NOT connected to pin 103 on the ecu which is the reflash pin. i had this problem on my ecu so i had to send it to Colby (all the way from New Zealand). follow the above instructions from tephra, that should fix your problem.