Help with Bricked ECU (ECUflash or Evoscan solutions)
Jul 2, 2018, 03:57 PM
#1
Help with Bricked ECU (ECUflash or Evoscan solutions)
Okay, here's the setup. Went to reflash my vehicle the other day with Evoscan. I always let the car run for a little to make sure there's enough battery power to flash. I also usually do a couple logs to make sure there's a good connection to the ECU. No problems so far. Then I go to load my ROM. Error about halfway through. Fine, try again, same thing. So I stop. I have a buddy come over so hookup some jumper cables, assuming my battery wasn't making it through the flash. Nope. Getting the "no response to any known code, interface close" error.
I am 99% positive I bricked the ECU. Could be my cable finally crapped out. A new one is on the way. Assuming that is not the issue though, my understanding, and please correct me if I am wrong, is there is no way to remedy this with Evoscan. So my option seems to be to reflash with ECUflash, while running an unlocker. Does that sound right? AND, if so, can someone walk me through the steps with links to appropriate files? For example, I tried to open my ROM with ECUflash, but I get an error. I think I am missing an XML. My tuner told me it should be the "94917 variant." I have no idea what that means, where I get it, or where I put it. My skills with tuning start and stop with logging/flashing. Can someone in the Bay Area help? Here's the other fun part, the car is in a basement parking garage, so I can't remote anyone into my computer while I work on this.
Please help!
I am 99% positive I bricked the ECU. Could be my cable finally crapped out. A new one is on the way. Assuming that is not the issue though, my understanding, and please correct me if I am wrong, is there is no way to remedy this with Evoscan. So my option seems to be to reflash with ECUflash, while running an unlocker. Does that sound right? AND, if so, can someone walk me through the steps with links to appropriate files? For example, I tried to open my ROM with ECUflash, but I get an error. I think I am missing an XML. My tuner told me it should be the "94917 variant." I have no idea what that means, where I get it, or where I put it. My skills with tuning start and stop with logging/flashing. Can someone in the Bay Area help? Here's the other fun part, the car is in a basement parking garage, so I can't remote anyone into my computer while I work on this.
Please help!
Jul 7, 2018, 03:03 PM
#4
Voltage wasn't the issue. Also turned out not the be bricked. Just a crappy 1.3 cable. My new Tactrix 2.0 worked just fine. Relieved it wasn't a bigger issue, but also annoyed these EvoScan cables don't even last two years and a couple dozen flashes/logs. Thanks to everyone that chimed in.
Jul 7, 2018, 05:00 PM
#5
Voltage wasn't the issue. Also turned out not the be bricked. Just a crappy 1.3 cable. My new Tactrix 2.0 worked just fine. Relieved it wasn't a bigger issue, but also annoyed these EvoScan cables don't even last two years and a couple dozen flashes/logs. Thanks to everyone that chimed in.
Thread
Thread Starter
Forum
Replies
Last Post
smanders
Evo X Engine Management / Tuning Forums
10
Oct 21, 2009 09:20 PM
RicerX1
Evo X Engine Management / Tuning Forums
47
Dec 19, 2008 11:50 PM