First off I am total idiot. Now that we got that out of the way, is there anyone out there that can help me.

I was flashing my Evo X MR with a modified map with JDM MIVEC maps. I Modified my stock with the JDM mappings.

I had a really bad stomach ache so instead of poo'ing in my pants so to say. I ran off to the bathroom. Now it seems that it would have been a better idea to soil my self.

When I got back to my car the screen was blank (probably went to sleep) and moving the mouse for a bit it came back and the status bar was stuck at 50% and then ECUFlash program crashed/closed. So I wasn't able to save a log of what happened.

I am freaking out since i couldn't get the car started again or reconnect to the ECU using the program.

When I tried to reconnect it would display in the log

Kernel Get Version and then disconnect or it would just hang.

I ended up towing the car to the dealer and they couldn't get a flash onto the ecu or connect.

They are telling me I need a new ECU. Did I brick my EVO X Ecu or does anyone have a way of saving it?

I was using ECUFlash 1.41.2294

 

Not to pour salt on the wounds but there is a reason why the Evo 10 Ecuflash hasn't been released yet and is still in beta testing. How did you get a working copy?

Have you tried "Exit programming state" and then tried to flash or pull the rom again?

 

It okay I deserve that. Don't really want to name names to get anyone in trouble. Besides this is my own dumbas mistake.

Yea I've tried Exit Programming state. Still getting the same when I try to pull or flash.

 

dam that sucks

 

I hope your paying for that ECU out of your packet. Take it as you want it.

P.S. If you think Mitsubishi does not read this forums, think again.

 

Yep if no one comes up with anything i'm paying 1350 to the dealer for a new ecu and labor. If anyone comes up with a good idea i'll pull my car from the dealer and try it. I'm trying to own up to my own mistake the best I could.

Or if any of the beta testers have had a similar experience and have fixed it. I would be greatful if you would share how you fixed it.

I've called Cobb regarding they're accessport to see if it can recover. From what I was told by Cobb was that it can recover a failed flash from the AP but not from opensource flashes.

 

yes the AP must be installed to be able to recover - what a shame

 

Sorry bro that blows. Live and learn. Better than it working and blowing the engine.

 

You could TRY and send me the ecu to see if Ecutek can recover ot or just check out an ecutek delear in your area

Al

 

No, this is why beta not to be released to the general public versions are use at your own risk or not at all until it's actually released.

I've never lost a ecu ever to ecuflash and I've flashed hundreds upon hundreds upon hundreds.

 

Dont leave your car when flashing! I always double check my connections, do a test write (sometimes twice) and watch the logs when flashing!

 

Yea dont blame this on ECUFlash. It is clearly user error in this case. I played with beta and screwed myself. I guess we finally found a reason why the EVO X version isn't offically released yet. It's also because I didn't do my research before hand.

I can give a list of everything I did wrong.
Didn't unplug the fans
Didn't use a extra battery or jumper pack on the car
Should have checked the sleep settings on my laptop
Plugged my laptop into the wall as i was working on it
Went to the bathroom before hand
Wait for an official release instead of using the beta
Not do it in the parking lot outside at work
Do a compare of the old and new maps
Do a test write
Pray j/k
-and there probably is a lot more.

This isn't thread wasn't started to put any blame on ECUFlash. Just me a desprate person calling out for help from my own stupidity.

 

to the op,

is there a X in a junk yard you can get another ecu from?

 

Yeah I dont think i can be stated enough, so Ill say it again. I can already see the people in the future saying "ecuflash is gonna brick yo ECU!".. *sigh*

REMEMBER...this was a BETA-Version of ECUFLash that the original user has already mentioned was HIS FAULT and NOT directly the programs fault.

 

Check AL from Dynoflash for help. I really think your stuck out there.