Can't flash or read the ROM from your ECU - Start Here!
#1
Can't flash or read the ROM from your ECU - Start Here!
This thread will be a living list of common reasons why users can't read or write to the ECU. Feel free to add to this list by posting in this thread.
Before posting a thread!
If you have tried all the suggestions in this thread and they don't work feel free to post a thread explaining your problem.
If you have not tried all the suggestions in this thread do not post a thread, it will be closed. Remember, altering the parameters of the ECU can cause catastrophic damage to your motor. If you feel unsure about tuning yourself please seek the help of a professional.
Typical Error message in ECUflash log:
Battery voltage too low
This seems to happen more on the Evo 9s than 8s. If you battery is even somewhat lower then it should be the ECU will not allow a write or read. Has your car been sitting for a week or so or longer? Try charging the battery either with a charger or by starting the car and letting it run.
I have personally run into this problem numerous times. The car will start fine but after a few minutes of just idling the battery will be charged enough to pull or write the file.
ECU is locked
This is more common with old vendor habits of tuning cars and locking their intellectual property. Most vendors today don't lock the ROM. Use the ECU Unlocker (Found here: https://www.evolutionm.net/forums/ec...downloads.html) in combination with ECUflash to successfully read the ROM.
Key is set to ACC instead of On
Probably the least common problem but I would be lying if I hadn't done it. Ensure the car is not started but the key is in the 'On' position before attempting to read or write to the ECU.
Before posting a thread!
If you have tried all the suggestions in this thread and they don't work feel free to post a thread explaining your problem.
If you have not tried all the suggestions in this thread do not post a thread, it will be closed. Remember, altering the parameters of the ECU can cause catastrophic damage to your motor. If you feel unsure about tuning yourself please seek the help of a professional.
Typical Error message in ECUflash log:
[23:19:45.923] EcuFlash Version 1.42.2595
[23:19:45.923] OS Version Windows Vista
[23:19:45.923] Qt Version 4.5.0
[23:19:45.939] 56 memory models read.
[23:19:45.939] scanning for metadata models in C:/Users/DurstMan/Desktop/EcuFlash/rommetadata
[23:19:46.407] 343 ROM metadata models scanned.
[23:19:46.407] checksum module "subarudbw" loaded.
[23:19:46.407] checksum module "mitsucan" loaded.
[23:19:46.407] flashing tool "wrx02" loaded.
[23:19:46.407] flashing tool "wrx04" loaded.
[23:19:46.407] flashing tool "sti04" loaded.
[23:19:46.407] flashing tool "sti05" loaded.
[23:19:46.407] flashing tool "mitsukernel" loaded.
[23:19:46.407] flashing tool "mitsukernelocp" loaded.
[23:19:46.407] flashing tool "mitsubootloader" loaded.
[23:19:46.407] flashing tool "shbootmode" loaded.
[23:19:46.407] flashing tool "shaudmode" loaded.
[23:19:46.407] flashing tool "subarucan" loaded.
[23:19:46.407] flashing tool "mitsucan" loaded.
[23:20:01.196] J2534 API Version: 04.04
[23:20:01.196] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[23:20:01.196] Device Firmware Version: 1.10.2658
[23:20:13.853] sending init sequence 1 (0001)
[23:20:17.161] sending init sequence 1 (0003)
[23:20:20.468] sending init sequence 1 (FFFF)
[23:20:23.775] sending init sequence 1 (F0F0)
[23:20:26.521] no response to any known code
[23:20:26.521] interface close
[23:19:45.923] OS Version Windows Vista
[23:19:45.923] Qt Version 4.5.0
[23:19:45.939] 56 memory models read.
[23:19:45.939] scanning for metadata models in C:/Users/DurstMan/Desktop/EcuFlash/rommetadata
[23:19:46.407] 343 ROM metadata models scanned.
[23:19:46.407] checksum module "subarudbw" loaded.
[23:19:46.407] checksum module "mitsucan" loaded.
[23:19:46.407] flashing tool "wrx02" loaded.
[23:19:46.407] flashing tool "wrx04" loaded.
[23:19:46.407] flashing tool "sti04" loaded.
[23:19:46.407] flashing tool "sti05" loaded.
[23:19:46.407] flashing tool "mitsukernel" loaded.
[23:19:46.407] flashing tool "mitsukernelocp" loaded.
[23:19:46.407] flashing tool "mitsubootloader" loaded.
[23:19:46.407] flashing tool "shbootmode" loaded.
[23:19:46.407] flashing tool "shaudmode" loaded.
[23:19:46.407] flashing tool "subarucan" loaded.
[23:19:46.407] flashing tool "mitsucan" loaded.
[23:20:01.196] J2534 API Version: 04.04
[23:20:01.196] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[23:20:01.196] Device Firmware Version: 1.10.2658
[23:20:13.853] sending init sequence 1 (0001)
[23:20:17.161] sending init sequence 1 (0003)
[23:20:20.468] sending init sequence 1 (FFFF)
[23:20:23.775] sending init sequence 1 (F0F0)
[23:20:26.521] no response to any known code
[23:20:26.521] interface close
This seems to happen more on the Evo 9s than 8s. If you battery is even somewhat lower then it should be the ECU will not allow a write or read. Has your car been sitting for a week or so or longer? Try charging the battery either with a charger or by starting the car and letting it run.
I have personally run into this problem numerous times. The car will start fine but after a few minutes of just idling the battery will be charged enough to pull or write the file.
ECU is locked
This is more common with old vendor habits of tuning cars and locking their intellectual property. Most vendors today don't lock the ROM. Use the ECU Unlocker (Found here: https://www.evolutionm.net/forums/ec...downloads.html) in combination with ECUflash to successfully read the ROM.
Key is set to ACC instead of On
Probably the least common problem but I would be lying if I hadn't done it. Ensure the car is not started but the key is in the 'On' position before attempting to read or write to the ECU.
Last edited by MR Turco; May 14, 2010 at 05:22 PM.
#2
I use tactrix openport2.0 with LANCER EX 2009 GT 2.0 CVT
what happen I incorrect? Please help me.
[19:22:07.366] EcuFlash Version 1.42.2595
[19:22:07.366] OS Version Windows Vista
[19:22:07.366] Qt Version 4.5.0
[19:22:07.375] 56 memory models read.
[19:22:07.375] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[19:22:07.782] 447 ROM metadata models scanned.
[19:22:07.782] checksum module "subarudbw" loaded.
[19:22:07.782] checksum module "mitsucan" loaded.
[19:22:07.782] flashing tool "wrx02" loaded.
[19:22:07.783] flashing tool "wrx04" loaded.
[19:22:07.783] flashing tool "sti04" loaded.
[19:22:07.783] flashing tool "sti05" loaded.
[19:22:07.783] flashing tool "mitsukernel" loaded.
[19:22:07.783] flashing tool "mitsukernelocp" loaded.
[19:22:07.783] flashing tool "mitsubootloader" loaded.
[19:22:07.783] flashing tool "shbootmode" loaded.
[19:22:07.784] flashing tool "shaudmode" loaded.
[19:22:07.785] flashing tool "subarucan" loaded.
[19:22:07.785] flashing tool "mitsucan" loaded.
[19:22:44.923] J2534 API Version: 04.04
[19:22:44.923] J2534 DLL Version: 0.50.2598 (DEBUG) Jun 26 2009 15:02:29
[19:22:44.923] Device Firmware Version: 1.07.2597
[19:22:48.691] sending init sequence 1 (0001)
[19:22:51.968] sending init sequence 1 (0003)
[19:22:55.245] sending init sequence 1 (FFFF)
[19:22:57.962] no response to any known code
[19:22:57.963] interface close
what happen I incorrect? Please help me.
[19:22:07.366] EcuFlash Version 1.42.2595
[19:22:07.366] OS Version Windows Vista
[19:22:07.366] Qt Version 4.5.0
[19:22:07.375] 56 memory models read.
[19:22:07.375] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[19:22:07.782] 447 ROM metadata models scanned.
[19:22:07.782] checksum module "subarudbw" loaded.
[19:22:07.782] checksum module "mitsucan" loaded.
[19:22:07.782] flashing tool "wrx02" loaded.
[19:22:07.783] flashing tool "wrx04" loaded.
[19:22:07.783] flashing tool "sti04" loaded.
[19:22:07.783] flashing tool "sti05" loaded.
[19:22:07.783] flashing tool "mitsukernel" loaded.
[19:22:07.783] flashing tool "mitsukernelocp" loaded.
[19:22:07.783] flashing tool "mitsubootloader" loaded.
[19:22:07.783] flashing tool "shbootmode" loaded.
[19:22:07.784] flashing tool "shaudmode" loaded.
[19:22:07.785] flashing tool "subarucan" loaded.
[19:22:07.785] flashing tool "mitsucan" loaded.
[19:22:44.923] J2534 API Version: 04.04
[19:22:44.923] J2534 DLL Version: 0.50.2598 (DEBUG) Jun 26 2009 15:02:29
[19:22:44.923] Device Firmware Version: 1.07.2597
[19:22:48.691] sending init sequence 1 (0001)
[19:22:51.968] sending init sequence 1 (0003)
[19:22:55.245] sending init sequence 1 (FFFF)
[19:22:57.962] no response to any known code
[19:22:57.963] interface close
#4
Evolving Member
iTrader: (4)
Okay so I'm trying to download the ecu unlocker, but I need to be a registered member of ActiveMatrix.com. Fine. No problem, except I have tried to register three times on two different computers and after I fill out all the info it brings me to a blank white screen. That's it. No ability to login to get the program and I'm stuck. No confirmation e-mail, nada. Can anyone let me use their login to get this? I can't contact an admin about it because I'm not a member; because I can't login. It's a conundrum.
Heeeeeeeeeellllllllllllllllllllpppppppppppppp!!!!! !!!!
Heeeeeeeeeellllllllllllllllllllpppppppppppppp!!!!! !!!!
#5
Evolved Member
iTrader: (14)
Join Date: Aug 2005
Location: Socal :)
Posts: 2,636
Likes: 0
Received 0 Likes
on
0 Posts
I have a new laptop running Windows 7, Ecuflash 1.42, and using my Tactrix Openport 1.3 cable - although the computer appears to recognize the cable I cannot connect to the ECU (read or write). Any ideas why ?
I can use the same cable just fine on an older laptop running XP, Ecuflash 1.30, and the same cable. Thanks in advance!
I can use the same cable just fine on an older laptop running XP, Ecuflash 1.30, and the same cable. Thanks in advance!
#6
Evolving Member
iTrader: (9)
Join Date: Apr 2005
Location: Avondale, PA
Posts: 145
Likes: 0
Received 0 Likes
on
0 Posts
My 1.3u cable will not read/write with ecuflash but my 2.0 cable will. The 1.3u cable will work with evoscan though.... The 2.0 cable only logs about 1 packet per second where-as the 1.3 will get 5-7 packets. Gets annoying having to switch back and forth.
I'm running the most recent versions of both programs and the cables are only a couple months old.
I'm running the most recent versions of both programs and the cables are only a couple months old.
Trending Topics
#8
Hey i have 98640014 id and i downloaded the 98640014 dif file for it put it in the rometadata/mitsubishi/evo folder but when i read my ecu with ecuflash it doesnt load any of the parameters etc just has ROM. how do i get into accessing that part of ecuflash?
#14
Evolving Member
iTrader: (26)
Join Date: Apr 2008
Location: North Dakota
Posts: 334
Likes: 0
Received 0 Likes
on
0 Posts
ive been able to read write to my ecu and just this morning i tried uploading a new map, i get some error that says see log for details same thing with trying to write to it???? also if i try to log through evo scan it says unable to connect with the ecu?? also the car wont start? hope the ecu is wasted? anythign guys
#15
Cable OP1.3., EcuFlash 1.29a.
I read ROM out an insertion normally.
After editing.
In a test mode it is not filled in. Reaches 50 %
On three blocks gives out CRC NO and on the rests YES.
If I try at once a normal mode of record gives out
Red error.
At record attempt relay operation is audible.
And as 1 time at attempt FLASH has burned down a safety lock 10А in interior - responsible for ignition coils.
In what there can be a business??
I read ROM out an insertion normally.
After editing.
In a test mode it is not filled in. Reaches 50 %
On three blocks gives out CRC NO and on the rests YES.
If I try at once a normal mode of record gives out
Red error.
At record attempt relay operation is audible.
And as 1 time at attempt FLASH has burned down a safety lock 10А in interior - responsible for ignition coils.
In what there can be a business??