Can't flash or read the ROM from your ECU - Start Here! - Page 5 - EvolutionM - Mitsubishi Lancer and Lancer Evolution Community



Can't flash or read the ROM from your ECU - Start Here!

Reply
 
 
 
Thread Tools Search this Thread
Old Oct 28, 2014, 07:34 PM   #61
Evolved Member
iTrader: (30)
 
raasfaas's Avatar
 
Join Date: Oct 2006
Location: Fl/Jam
Posts: 780
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: 06-IX-MR-GG

I must be missing something here, I'm helping a friend out reading his ROM (96940011) but it looks like the addresses aren't right.
Funny thing is I have another friend with the same exact ROMID and his file opens up and looks fine.
Any ideas??
Attached Thumbnails
Can't flash or read the ROM from your ECU - Start Here!-96940011.png  
Offline
 
Reply With Quote
Old Oct 29, 2014, 01:42 PM   #62
Evolved Member
iTrader: (2)
 
wreckleford's Avatar
 
Join Date: Jun 2003
Location: Jamaica
Posts: 1,142
Thanks: 0
Thanked 7 Times in 6 Posts

Drives: Evo I with an 8 ECU

Quote:
Originally Posted by raasfaas View Post
I must be missing something here, I'm helping a friend out reading his ROM (96940011) but it looks like the addresses aren't right.
Funny thing is I have another friend with the same exact ROMID and his file opens up and looks fine.
Any ideas??
Someone probably changed the ROM ID.
Offline
 
Reply With Quote
Old Oct 29, 2014, 04:08 PM   #63
Evolved Member
iTrader: (30)
 
raasfaas's Avatar
 
Join Date: Oct 2006
Location: Fl/Jam
Posts: 780
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: 06-IX-MR-GG

Hmm true, I'll check it out and report back.
Thanks.
Offline
 
Reply With Quote
Old Jan 9, 2015, 12:11 PM   #64
Newbie
 
Join Date: Jan 2015
Location: turkey
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: evo 9

Exclamation Help me

My cars is 2006 lancer evo 9 . I am use open port 2 cable. Not Connect. Please help me. Acc mode on. Battery voltage is ok. What is a Problem ?



[21:04:29.974] EcuFlash Version 1.44.4361
[21:04:29.974] OS Version Windows 7
[21:04:29.974] Qt Version 5.2.0
[21:04:29.990] 67 memory models read.
[21:04:29.990] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[21:04:30.161] 746 ROM metadata models scanned.
[21:04:30.161] checksum module "subarudbw" loaded.
[21:04:30.161] checksum module "subarudiesel" loaded.
[21:04:30.161] checksum module "mitsucan" loaded.
[21:04:30.161] checksum module "mitsuh8" loaded.
[21:04:30.161] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[21:04:30.161] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[21:04:30.177] using metadata XML ID read_evo9 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/read templates/read_evo9.xml
[21:04:30.177] flashing tool "wrx02" loaded.
[21:04:30.177] flashing tool "wrx04" loaded.
[21:04:30.177] flashing tool "sti04" loaded.
[21:04:30.192] flashing tool "sti05" loaded.
[21:04:30.192] flashing tool "mitsucan" loaded.
[21:04:30.192] flashing tool "mitsukernel" loaded.
[21:04:30.192] flashing tool "mitsukernelocp" loaded.
[21:04:30.192] flashing tool "mitsubootloader" loaded.
[21:04:30.192] flashing tool "shbootmode" loaded.
[21:04:30.192] flashing tool "shaudmode" loaded.
[21:04:30.192] flashing tool "subarucan" loaded.
[21:04:30.192] flashing tool "subarucand" loaded.
[21:04:30.192] flashing tool "subarubrz" loaded.
[21:04:30.208] flashing tool "subaruhitachi" loaded.
[21:04:30.224] J2534 API Version: 04.04
[21:04:30.224] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00
[21:04:30.224] Device Firmware Version: 1.15.4340
[21:04:30.224] Device Serial Number: TAGdvwoL
[21:04:30.224] interface close
[21:04:30.239] J2534 API Version: 04.04
[21:04:30.239] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00
[21:04:30.239] Device Firmware Version: 1.15.4340
[21:04:30.239] Device Serial Number: TAGdvwoL
[21:04:30.239] interface close
[21:04:30.255] J2534 API Version: 04.04
[21:04:30.255] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00
[21:04:30.255] Device Firmware Version: 1.15.4340
[21:04:30.255] Device Serial Number: TAGdvwoL
[21:04:30.255] interface close
[21:04:30.270] J2534 API Version: 04.04
[21:04:30.270] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00
[21:04:30.270] Device Firmware Version: 1.15.4340
[21:04:30.270] Device Serial Number: TAGdvwoL
[21:04:30.270] interface close
[21:04:30.286] J2534 API Version: 04.04
[21:04:30.286] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00
[21:04:30.286] Device Firmware Version: 1.15.4340
[21:04:30.286] Device Serial Number: TAGdvwoL
[21:04:30.286] interface close
[21:04:30.302] J2534 API Version: 04.04
[21:04:30.302] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00
[21:04:30.302] Device Firmware Version: 1.15.4340
[21:04:30.302] Device Serial Number: TAGdvwoL
[21:04:30.302] interface close
[21:04:44.092] using metadata XML ID read_evo9 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/read templates/read_evo9.xml
[21:04:44.108] J2534 API Version: 04.04
[21:04:44.108] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00
[21:04:44.108] Device Firmware Version: 1.15.4340
[21:04:44.108] Device Serial Number: TAGdvwoL
[21:04:46.884] sending init sequence 1 (0001)
[21:04:50.145] sending init sequence 1 (0003)
[21:04:53.405] sending init sequence 1 (FFFF)
[21:04:57.167] sending init sequence 1 (F0F0)
[21:04:59.885] no response to any known code
Offline
 
Reply With Quote
Old Jan 9, 2015, 02:32 PM   #65
Evolved Member
iTrader: (1)
 
letsgetthisdone's Avatar
 
Join Date: Oct 2013
Location: Las Vegas
Posts: 9,770
Thanked 395 Times in 376 Posts

Drives: 2005 Evo 8. 2011 F150 FX4

Quote:
Originally Posted by okankoc16 View Post
My cars is 2006 lancer evo 9 . I am use open port 2 cable. Not Connect. Please help me. Acc mode on. Battery voltage is ok. What is a Problem ?



[21:04:29.974] EcuFlash Version 1.44.4361
[21:04:29.974] OS Version Windows 7
[21:04:29.974] Qt Version 5.2.0
[21:04:29.990] 67 memory models read.
[21:04:29.990] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[21:04:30.161] 746 ROM metadata models scanned.
[21:04:30.161] checksum module "subarudbw" loaded.
[21:04:30.161] checksum module "subarudiesel" loaded.
[21:04:30.161] checksum module "mitsucan" loaded.
[21:04:30.161] checksum module "mitsuh8" loaded.
[21:04:30.161] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[21:04:30.161] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[21:04:30.177] using metadata XML ID read_evo9 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/read templates/read_evo9.xml
[21:04:30.177] flashing tool "wrx02" loaded.
[21:04:30.177] flashing tool "wrx04" loaded.
[21:04:30.177] flashing tool "sti04" loaded.
[21:04:30.192] flashing tool "sti05" loaded.
[21:04:30.192] flashing tool "mitsucan" loaded.
[21:04:30.192] flashing tool "mitsukernel" loaded.
[21:04:30.192] flashing tool "mitsukernelocp" loaded.
[21:04:30.192] flashing tool "mitsubootloader" loaded.
[21:04:30.192] flashing tool "shbootmode" loaded.
[21:04:30.192] flashing tool "shaudmode" loaded.
[21:04:30.192] flashing tool "subarucan" loaded.
[21:04:30.192] flashing tool "subarucand" loaded.
[21:04:30.192] flashing tool "subarubrz" loaded.
[21:04:30.208] flashing tool "subaruhitachi" loaded.
[21:04:30.224] J2534 API Version: 04.04
[21:04:30.224] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00
[21:04:30.224] Device Firmware Version: 1.15.4340
[21:04:30.224] Device Serial Number: TAGdvwoL
[21:04:30.224] interface close
[21:04:30.239] J2534 API Version: 04.04
[21:04:30.239] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00
[21:04:30.239] Device Firmware Version: 1.15.4340
[21:04:30.239] Device Serial Number: TAGdvwoL
[21:04:30.239] interface close
[21:04:30.255] J2534 API Version: 04.04
[21:04:30.255] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00
[21:04:30.255] Device Firmware Version: 1.15.4340
[21:04:30.255] Device Serial Number: TAGdvwoL
[21:04:30.255] interface close
[21:04:30.270] J2534 API Version: 04.04
[21:04:30.270] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00
[21:04:30.270] Device Firmware Version: 1.15.4340
[21:04:30.270] Device Serial Number: TAGdvwoL
[21:04:30.270] interface close
[21:04:30.286] J2534 API Version: 04.04
[21:04:30.286] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00
[21:04:30.286] Device Firmware Version: 1.15.4340
[21:04:30.286] Device Serial Number: TAGdvwoL
[21:04:30.286] interface close
[21:04:30.302] J2534 API Version: 04.04
[21:04:30.302] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00
[21:04:30.302] Device Firmware Version: 1.15.4340
[21:04:30.302] Device Serial Number: TAGdvwoL
[21:04:30.302] interface close
[21:04:44.092] using metadata XML ID read_evo9 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/read templates/read_evo9.xml
[21:04:44.108] J2534 API Version: 04.04
[21:04:44.108] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00
[21:04:44.108] Device Firmware Version: 1.15.4340
[21:04:44.108] Device Serial Number: TAGdvwoL
[21:04:46.884] sending init sequence 1 (0001)
[21:04:50.145] sending init sequence 1 (0003)
[21:04:53.405] sending init sequence 1 (FFFF)
[21:04:57.167] sending init sequence 1 (F0F0)
[21:04:59.885] no response to any known code

you need to down load the ECU unlocker. Post 15 in this thread..


https://www.evolutionm.net/forums/ec...cker-tool.html

To permanently unlock you ROM change the INIT code to 0001. Its hex, so you have to enter it as 0x0001..
Offline
 
Reply With Quote
Old Feb 13, 2015, 04:08 AM   #66
Evolving Member
 
TJung's Avatar
 
Join Date: Oct 2008
Location: Poland, Katowice
Posts: 286
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: Evo 9 2007'

Hello. My friend asked me for help with his idle map, but I cannot open his rom. When I;m opening it, it seems like someone changed xml or something. What should I do? Car is USDM E9
Attached Thumbnails
Can't flash or read the ROM from your ECU - Start Here!-xmlfailed.jpg  

Last edited by TJung; Feb 13, 2015 at 04:13 AM.
Offline
 
Reply With Quote
Old Apr 6, 2015, 04:15 AM   #67
Newbie
 
3VOLUTIONIST's Avatar
 
Join Date: Mar 2015
Location: Perth, Western Australia
Posts: 73
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: GSR Lancer

I've just finished wiring an Evo 6 ECU into my GSR Lancer (1995). The car starts and idles fine, havent driven it (yet).
Plugged in my tactrix cable and selected evo VI (MH7202F), hit read ECU, and I get:
[18:12:39.011] using metadata XML ID read_evo5 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo5.xml
[18:12:39.027] J2534 API Version: 04.04
[18:12:39.027] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00
[18:12:39.027] Device Firmware Version: 1.15.4363
[18:12:39.027] Device Serial Number: TAefRcRg
[18:12:41.946] sending init sequence 2
[18:12:43.956] interface close

Ideas?
Offline
 
Reply With Quote
Old Apr 6, 2015, 06:35 AM   #68
Evolved Member
iTrader: (27)
 
evo8426's Avatar
 
Join Date: Jan 2006
Location: Charlotte, North Carolina
Posts: 4,248
Thanked 4 Times in 4 Posts

Drives: WW Evolution IX MR and Overland Grand Cherokee

Quote:
Originally Posted by letsgetthisdone View Post
you need to down load the ECU unlocker. Post 15 in this thread..


https://www.evolutionm.net/forums/ec...cker-tool.html

To permanently unlock you ROM change the INIT code to 0001. Its hex, so you have to enter it as 0x0001..
The code he got is the same one that people get when there is not enough voltage to read/write.
Offline
 
Reply With Quote
Old Apr 6, 2015, 06:38 AM   #69
Newbie
 
3VOLUTIONIST's Avatar
 
Join Date: Mar 2015
Location: Perth, Western Australia
Posts: 73
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: GSR Lancer

Quote:
Originally Posted by evo8426 View Post
The code he got is the same one that people get when there is not enough voltage to read/write.
So youre saying I need to hook up my spare battery and try again?
Offline
 
Reply With Quote
Old Apr 6, 2015, 07:09 AM   #70
Newbie
 
3VOLUTIONIST's Avatar
 
Join Date: Mar 2015
Location: Perth, Western Australia
Posts: 73
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: GSR Lancer

Hooked up the spare battery, Downloaded ECU Unlocker, launched that, launched ECUFlash, turned key to ON, hit the read ECU button:

[21:05:27.738] using metadata XML ID read_evo5 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo5.xml
[21:05:27.759] J2534 API Version: 04.04
[21:05:27.759] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00
[21:05:27.759] Device Firmware Version: 1.15.4363
[21:05:27.759] Device Serial Number: TAefRcRg
[21:05:28.871] sending init sequence 2
[21:05:30.877] interface close

Doesnt appear to be any change.

It doesnt actually tell me what the error is. Im starting to wonder if this program is fked. Cant get it to work on my 03 WRX or my 01 Forester GT either.
Downloaded it from the Tactrix website.

EDIT: couldn't actually get anymore than 11.6 volts out of my spare or the one in the WRX when hooked up with jumper cables :/

Will go for a drive tomorrow to try and charge it a bit.

Starts amazingly fast with the Evo VI ecu, like, instantaneously...


I also get the same error when the tactrix cable isnt even plugged into the car... So i'm leaning pretty heavily toward the OBDII pins not being connected to the ECU properly, will have to check each one individually when I get back from holiday (going away tomorrow)

Last edited by 3VOLUTIONIST; Apr 6, 2015 at 07:22 AM.
Offline
 
Reply With Quote
Old May 12, 2015, 11:07 AM   #71
Newbie
 
absolut525's Avatar
 
Join Date: Oct 2014
Location: Valdez, AK
Posts: 36
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: 06 Evo SE

Quote:
Originally Posted by 3VOLUTIONIST View Post
Hooked up the spare battery, Downloaded ECU Unlocker, launched that, launched ECUFlash, turned key to ON, hit the read ECU button:

[21:05:27.738] using metadata XML ID read_evo5 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo5.xml
[21:05:27.759] J2534 API Version: 04.04
[21:05:27.759] J2534 DLL Version: 1.01.4358 Oct 10 2014 03:49:00
[21:05:27.759] Device Firmware Version: 1.15.4363
[21:05:27.759] Device Serial Number: TAefRcRg
[21:05:28.871] sending init sequence 2
[21:05:30.877] interface close

Doesnt appear to be any change.

It doesnt actually tell me what the error is. Im starting to wonder if this program is fked. Cant get it to work on my 03 WRX or my 01 Forester GT either.
Downloaded it from the Tactrix website.

EDIT: couldn't actually get anymore than 11.6 volts out of my spare or the one in the WRX when hooked up with jumper cables :/

Will go for a drive tomorrow to try and charge it a bit.

Starts amazingly fast with the Evo VI ecu, like, instantaneously...


I also get the same error when the tactrix cable isnt even plugged into the car... So i'm leaning pretty heavily toward the OBDII pins not being connected to the ECU properly, will have to check each one individually when I get back from holiday (going away tomorrow)
Did you ever figure out the issue?
Offline
 
Reply With Quote
Old May 12, 2015, 11:24 AM   #72
Newbie
 
3VOLUTIONIST's Avatar
 
Join Date: Mar 2015
Location: Perth, Western Australia
Posts: 73
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: GSR Lancer

Quote:
Originally Posted by absolut525 View Post
Did you ever figure out the issue?
I solved that issue and ran into others.

Turns out my reflashing plug (car side) had the pin in the opposite corner. The plug that Tactrix sent me had contacts in all the holes so I assumed they were all connected and ran out the back as the single wir . Nope, only one is actually connected to the stereo jack on the end of the plugg. I noticed when flicking through Merlin's ecuflash guide that my plug had the pin in a different spot. Awake it, and worked perfectly.

The MH7202F Evo 6 ECU I had in the car then went and decided to brick itself after I changed one fuel cell, and rn a successful test write, upon flashing it gave me a memory error and that was it. Tried bench flashing it, nothing. The guys at Tactrix want my ecu to look at because they can't figure it out either (unheard of for a 7202 to die).

So, I bought a JDM Evo 7 ECU. Swapped a few wires, copied the MAF data from the evo 6 ROM into the evo 7 ROM, because I'm still running the 787maf. Car runs nicely. Just finished changing my turbo this evening, upgraded to a td05-14b. Now I need to sort out wideband logging.

My advice, don't waste your time with the 5&6 ecu unless you get it super cheap.

PS excuse any grammatical errors, I'm on my phone
Offline
 
Reply With Quote
Old Aug 21, 2015, 08:14 AM   #73
Newbie
iTrader: (1)
 
booosted's Avatar
 
Join Date: Mar 2013
Location: florida
Posts: 25
Thanked 0 Times in 0 Posts

Drives: Evo 8

Still having connection problems

Running latest driver, cable shows connection but i still get this message.

[07:50:41.587] unable to open OpenPort device [ TX39B14]. [07:50:41.587] unable to connect to vehicle interface.


Anyone else have other suggestions?

I've read through the post but nothing worked.
-Battery full charged
-cable connected and shows connection,
-Ignition on "on" position with engine off.
-Tried with car on
-Tried connecting to car then powering EcuFlash, vice versa
Offline
 
Reply With Quote
Old Sep 21, 2015, 07:40 AM   #74
Newbie
 
Outlaw666's Avatar
 
Join Date: Sep 2013
Location: Bolivia
Posts: 12
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: Evo 9

Hi guys. I'm new to this ECUflash/Tactrix cable. As I read it all seemed very straight forward but as I finally got my 1.3u cable I started having some problems. I have windows 8.1 with lastest ECUflash 1.44.4503 and Evoscan 2.9. And my car is a USDM Evo IX GSR

At first I couldnt read my ECU and used to get the sequence:


[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:55.245] sending init sequence 1 (F0F0)
[19:22:57.962] no response to any known code
[19:22:57.963] interface close

Then when I runned the program as administrator the problem was solved.

Last week I installed my AEM UEGO wideband and again started getting the same problem. I've tried running it as admin, charguing the battery by warming up the car a little bit. Checking if all my fuses where ok and even trying with my cousins laptop which has windows 7 and also used to work too... but no luck

Then last night I tried my laptop with a friends evo8 and it read his ecu with evoscan but ecuflash has started closing after a while of having it opened

Please can someone suggest me any other things I should also check? I guess the problem is now with my car as I've managed to read the evo8s ecu with my laptop and same cable...

Help please! I live in a country which no one has ever done this before so I can get any help at all.

Thank you very much!!



Last edited by Outlaw666; Sep 21, 2015 at 01:33 PM.
Offline
 
Reply With Quote
Old Oct 15, 2015, 06:12 AM   #75
Newbie
 
Jhova5's Avatar
 
Join Date: May 2013
Location: NJ
Posts: 11
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: Chevy Ltz & Evo8

Sorry guys I'm new to this ecu flash, I have got it to work but when I read the ecu I get this unknown rom image I used the ( wizard to create options ) I pick the best to my 05 evo8 rom and still can't read it have a rom ID 84185028 help
Attached Thumbnails
Can't flash or read the ROM from your ECU - Start Here!-image.jpeg  
Offline
 
Reply With Quote
 
 
Reply

Related Topics
Thread Thread Starter Forum Replies Last Post
HOW TO: Recover your EvoX ecu after a failed reflash. evoscan Evo X Engine Management / Tuning Forums 52 Jun 20, 2017 02:46 AM
EcuFlash Not Showing Rom Tables After Editing XML city EcuFlash 5 Jun 2, 2017 09:34 PM
Last ecuuflash Module MH8115F issues Hiram6g74 EcuFlash 1 Jan 5, 2017 07:24 AM
Ecuflash wont read rom. Searched already. FFEMT EcuFlash 5 Aug 1, 2016 05:45 AM
Need help reflash failed car wont start now GrabbinGears General Engine Management / Tuning Forum 2 Jul 7, 2016 03:19 PM


Tags
0001, ecu, ecuflash, error, flash, init, j25341, low, problem, read, rom, sending, sequence, tomcat, usar, voltage

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off



All times are GMT -7. The time now is 11:25 AM.


We are a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for us to earn fees by linking to Amazon.com and affiliated sites.
 
  • Ask a Question
    Get answers from community experts
Question Title:
Description:
Your question will be posted in: