Page 1 of 2
2002 JDM FORESTER XT AUTO

Posted:
Mon Oct 29, 2007 6:25 am
by c0r0na
I have connected the green connectors under the OBD-II connecter,
and followed the instructions selecting a Subaru DBW models STi/FXT/LGT/Baja.
Heres what I get in Ecuflash:
[14:27:49.750] Version 1.33.1426
[14:27:49.750] 11 memory models read.
[14:27:49.750] scanning for metadata models in D:/EcuFlash133/rommetadata
[14:27:50.265] 219 ROM metadata models scanned.
[14:27:50.265] checksum module "subarudbw" loaded.
[14:27:50.265] flashing tool "wrx02" loaded.
[14:27:50.265] flashing tool "wrx04" loaded.
[14:27:50.265] flashing tool "sti04" loaded.
[14:27:50.265] flashing tool "sti05" loaded.
[14:27:50.265] flashing tool "mitsukernel" loaded.
[14:27:50.265] flashing tool "mitsukernelocp" loaded.
[14:27:50.265] flashing tool "shbootmode" loaded.
[14:30:38.906] Using interface OpenPort 1.3 Universal TX275xNK10caf4d51934395d3bf7fd34e405a4f6e032007a
[14:30:45.375] SSM2 init
[14:30:45.812] SSM2 init
[14:30:45.984] SSM2 ECU ID is 2A 04 44 63 05
[14:30:45.984] SSM2 read ram byte addr: 000061
[14:30:46.046] ECU is in test mode
[14:30:46.156] SSM2 init
[14:30:46.312] SSM2 ECU ID is 2A 04 44 63 05
[14:30:48.468] interface close
[14:30:48.500] interface close
The error reads: 'an erros has occured. see log for details'
I tried all other options and some Version but all error.
I connected the white connectors but the same error.
Some Japanese having forester have the same problem.
Anyone have an idea?

Posted:
Mon Oct 29, 2007 10:38 am
by merchgod
An 02 JDM Forester model is not DBW. You should be using the '2001–2005 Subaru non-USDM Impreza WRX/STi' read method.

Posted:
Mon Oct 29, 2007 5:45 pm
by c0r0na
I tried the '2001–2005 Subaru non-USDM Impreza WRX/STi' read method and other Subaru models,but all error.
Here is the '2001–2005 Subaru non-USDM Impreza WRX/STi' read method and connected the white connectors :
[10:09:26.765] Using interface OpenPort 1.3 Universal TX275xNK10caf4d51934395d3bf7fd34e405a4f6e032007a
[10:09:31.421] denso02_bootloader_cmd_start
[10:09:31.656] writing kernel area addr: 020000 len: 0664
[10:09:33.593] kernel get version
[10:09:33.812] reading kernel comm buffer size
[10:09:34.046] reading kernel flash buffer size
[10:09:34.265] interface close
[10:09:34.265] interface close
not connected the white connectors :
[10:02:47.953] Using interface OpenPort 1.3 Universal TX275xNK10caf4d51934395d3bf7fd34e405a4f6e032007a
[10:02:51.562] denso02_bootloader_cmd_start
[10:02:52.781] denso02_bootloader_cmd_start
[10:02:54.000] denso02_bootloader_cmd_start
[10:02:55.234] denso02_bootloader_cmd_start
[10:02:56.468] denso02_bootloader_cmd_start
[10:02:56.890] kernel get version
[10:02:57.218] interface close
[10:02:57.234] interface close
I think that the white connectors is necessary.
When it can be connected, D CHECK MODE does not run.
Not connected,run.
Please anyone help...

Posted:
Mon Oct 29, 2007 7:21 pm
by merchgod

Posted:
Mon Oct 29, 2007 10:38 pm
by c0r0na
Hi merchgod.
I tried the following...
I drove several miles and charged the battery.
I uninstalled EcuFlash/EcuExplorer/Enginuity and deleted the driver.
I installed only EcuFlash.
I tried various timings of turn on ignition and hit 'OK'.
I don't use ECUTEK.
...
I tried all appearing in FAQ.
The result was the same error.
Is not my car supported?
Did you succeed?
Thanks.

Posted:
Tue Oct 30, 2007 4:43 am
by merchgod
Is this a turbo model? Non-DBW NA models are not supported.

Posted:
Tue Oct 30, 2007 7:12 am
by c0r0na
Yes,it's a turbo model.
Have you heard the success of this model?

Posted:
Tue Oct 30, 2007 10:10 am
by merchgod
Yes, it should work. Not sure what the issue is with yours. Are you sure you followed every step in the FAQ I listed?
Can you log at all? - I would try Enginuity or Ecuexplorer's logger. If you can't log, then it is probably a driver or cable issue.

Posted:
Tue Oct 30, 2007 9:39 pm
by c0r0na
I try the FAQ once agein.
I can log at Enginuity & Ecuexplorer, but Ecuexplorer's Read Ecu Flash Memory didn't work.

Posted:
Wed Oct 31, 2007 5:47 am
by merchgod
Are you entering test mode (radiator fans cycle after a period of time)?

Posted:
Wed Oct 31, 2007 7:40 am
by c0r0na
When I connected the white connectors and the green connectors and selected the '2001–2005 Subaru non-USDM Impreza WRX/STi', I didn't enter into the test mode.
In the case of others, I entered into the test mode. When I entered into the test mode, It does not stop even if I hit 'OK'.
I don't yet try the FAQ.
Do you have any idea?

Posted:
Wed Oct 31, 2007 9:08 am
by merchgod
When you hit OK and it begins to read, the radiator fans will NOT cycle once it starts to read (assuming the read method is correct). If you wait until the radiator fans cycle to hit OK, then the read will fail. The '2001-2005 Subaru non-USDM Impreza WRX/STi' method IS correct for you car. There is no use trying any of the other read methods.
I don't know what else to tell you. Are you the original owner of the car - if you bought it recently then perhaps it has an Ecutek flash on it?
What is the ecu id that Enginuity shows in the lower right hand corner when you are logging?

Posted:
Wed Oct 31, 2007 6:33 pm
by c0r0na
Because I am an original owner, the Ecutek doesn't flash on my car.
Enginuity shows the ecu id is '2A04446305'. It is the same as ecuflash.
EcuExplorer shows the ecu info is 'MY03 Forester 2.0 Turbo (JDM) [AG572-1355]' .

Posted:
Thu Nov 01, 2007 3:58 am
by merchgod
Well, that rom hasn't been uploaded before by anyone, although there are other jdm forester turbo models that have been and have a similar ecu id. At this point, I would try to find someone local to you that has already read their ECU with Ecuflash successfully and then try your laptop and cable and see if you can read it. If you can, then the issue lies with your car. If you can't, then you have a driver, software, or cable issue.

Posted:
Thu Nov 01, 2007 7:43 am
by c0r0na
Thank you very much.
Will it be JDM Forester 2.0 Turbo Auto that you tried?