Got trouble with ECU for Evo X JDM
I will try it after NY holidays.
As I understood:
1. load up stock ROM in "alt. flash recovery mode"
2. turn ign OFF
3. turn off "alt. flash recovery mode"
4. wait 15 sec
5. turn ign ON
6. QUICKLY do the "Exit programming mode"
7. try start engine
right?
replace #1 with #3
in between #6 and #7 - wait for ECU flash to finish, and hopefully the fans will turn off - then you can IGN off for another couple of seconds before trying to start
in between #6 and #7 - wait for ECU flash to finish, and hopefully the fans will turn off - then you can IGN off for another couple of seconds before trying to start

Is it possible to flash in "recovery mode"?
Does It need turn ignition OFF before to be flashed? I always tryed flash/read with ignition ON.
Last edited by Maxim_S; Dec 30, 2009 at 03:02 AM.
I flashed with 52360016 rom (I dont have another ROM), and nothing new happend, still same problem.
ok try this:
1. turn off "alt. flash recovery mode"
2. turn ign OFF
3. wait 15 sec
4. turn ign ON
5. QUICKLY do the "Exit programming mode"
6. turn ign OFF
7. wait 15 sec
8. try start engine
1. turn off "alt. flash recovery mode"
2. turn ign OFF
3. wait 15 sec
4. turn ign ON
5. QUICKLY do the "Exit programming mode"
6. turn ign OFF
7. wait 15 sec
8. try start engine
Unfortunatly, when I press "Exit programming state" then error was occured. Here is log:
[19:45:23.387] J2534 API Version: 04.04
[19:45:23.387] J2534 DLL Version: 0.50.2598 (DEBUG) Jun 26 2009 15:02:29
[19:45:23.387] Device Firmware Version: 1.10.2658
[19:45:24.465] -- connecting to kernel --
[19:45:24.465] kernel get version
[19:45:25.276] interface close
[19:45:25.290] interface close
So ECU can be flashed in "alt. recovery mode". Log:
[19:42:50.566] J2534 API Version: 04.04
[19:42:50.566] J2534 DLL Version: 0.50.2598 (DEBUG) Jun 26 2009 15:02:29
[19:42:50.566] Device Firmware Version: 1.10.2658
[19:42:52.470] sending init sequence 1 (0001)
[19:42:53.483] got 0x05 response
[19:42:53.483] sending init sequence 2
[19:42:53.490] got 0x1A response instead of 0x1B
[19:42:53.490] sending init sequence 3
[19:42:53.846] entering bootloader
[19:42:53.854] kernel read area: addr: 03FFFA len: 0006
[19:42:53.895] kernel rsp page: 030000
[19:42:53.895] kernel read addr: 03FFFA len: 06
[19:42:53.895] kernel rsp end
[19:42:55.959] sending init sequence 1 (0001)
[19:42:56.974] got 0x05 response
[19:42:56.974] sending init sequence 2
[19:42:56.982] got 0x1A response instead of 0x1B
[19:42:56.982] sending init sequence 3
[19:42:57.338] entering bootloader
[19:42:57.346] Flashing ECU memory...
[19:42:57.346] Erasing ECU memory...
[19:42:57.346] kernel erase
[19:43:06.858] kernel init
[19:43:06.864] kernel write area: addr: 000000 len: 0080
[19:43:06.864] kernel set page: addr: 000000
[19:43:06.894] kernel write area: addr: 000080 len: 0080
.......
.......
[19:45:10.133] kernel write area: addr: 0BFF80 len: 0080
[19:45:10.228] checksum is: C0 1E
[19:45:10.229] interface close
But same problem, engine couldn't be start.
[19:45:23.387] J2534 API Version: 04.04
[19:45:23.387] J2534 DLL Version: 0.50.2598 (DEBUG) Jun 26 2009 15:02:29
[19:45:23.387] Device Firmware Version: 1.10.2658
[19:45:24.465] -- connecting to kernel --
[19:45:24.465] kernel get version
[19:45:25.276] interface close
[19:45:25.290] interface close
So ECU can be flashed in "alt. recovery mode". Log:
[19:42:50.566] J2534 API Version: 04.04
[19:42:50.566] J2534 DLL Version: 0.50.2598 (DEBUG) Jun 26 2009 15:02:29
[19:42:50.566] Device Firmware Version: 1.10.2658
[19:42:52.470] sending init sequence 1 (0001)
[19:42:53.483] got 0x05 response
[19:42:53.483] sending init sequence 2
[19:42:53.490] got 0x1A response instead of 0x1B
[19:42:53.490] sending init sequence 3
[19:42:53.846] entering bootloader
[19:42:53.854] kernel read area: addr: 03FFFA len: 0006
[19:42:53.895] kernel rsp page: 030000
[19:42:53.895] kernel read addr: 03FFFA len: 06
[19:42:53.895] kernel rsp end
[19:42:55.959] sending init sequence 1 (0001)
[19:42:56.974] got 0x05 response
[19:42:56.974] sending init sequence 2
[19:42:56.982] got 0x1A response instead of 0x1B
[19:42:56.982] sending init sequence 3
[19:42:57.338] entering bootloader
[19:42:57.346] Flashing ECU memory...
[19:42:57.346] Erasing ECU memory...
[19:42:57.346] kernel erase
[19:43:06.858] kernel init
[19:43:06.864] kernel write area: addr: 000000 len: 0080
[19:43:06.864] kernel set page: addr: 000000
[19:43:06.894] kernel write area: addr: 000080 len: 0080
.......
.......
[19:45:10.133] kernel write area: addr: 0BFF80 len: 0080
[19:45:10.228] checksum is: C0 1E
[19:45:10.229] interface close
But same problem, engine couldn't be start.
ok.
so your flashing the ROM which you think is correct?
NOW - can you pull any codes from the ECU?
I think you have to program the VIN because of the manual/alternate flash process probably overwrites it...
so your flashing the ROM which you think is correct?
NOW - can you pull any codes from the ECU?
I think you have to program the VIN because of the manual/alternate flash process probably overwrites it...

I flashed with 52360016 rom that I found at this forum. I dont have another rom.
How can I pull codes from the ECU? When I try to read ECU or "exit program state" same error occured:
kernel get version
interface close
How to program the VIN?
PCMScan will read CEL's
I suggest trying that first.
You can email me @gmail.com if you like
Reprogramming the VIN is a dealer thing - BUT I can possibly help you with that...
I suggest trying that first.
You can email me @gmail.com if you like
Reprogramming the VIN is a dealer thing - BUT I can possibly help you with that...
I've been following this thread. I want to get into flashing my own ROM (even though I have english racing around to do it for me). I just want to say thanks for the continued support tephra. When I get some money and start doing it myself I'll be sending a donation.






