2013 FRS flash
 

New too the tuning world and of course my flash error out.




ECU: ZA1JA00C and I tried to use stage 1.bin from OFT bins with ecuflash with Tactrix openport 2.0 it stop at 50% of the flash. Now the car will not crank over. I tried to reflash with factory ROM but did not complete either. Can some help!!!


Thanks

Sorry, here is log file
 

Forgot to attach the log file.

Did you get the brz beta version of the ecuflash software from romraider and the updated 32bitbase file and the correct definition files for your rom type ??

If you have got all that you may need to talk to tactrix or the romraider guys

http://www.ft86club.com/forums/showt...=47322&page=19


have a read of a obove page, not sure if you should be using defs off github or the openflash ones whos ROM are you trying to write ??

Try reflash again.
 

Steve,


I did install the beta version of ecuflash, ROM is stage 1.bin from OFT but 32bitbase not sure but I believe I did. Just now, I tried to reflash stage 1 it complete but still error. The car starts but in limp mode with check engine light on. I will attach the log file.

Steve,


ROM was from OFT OTS v1.55.

I am pretty sure you need to manually copy in the 32bitbase file

https://github.com/TD-D/SubaruDefs/t...standard/Bases


Also read here

http://www.ft86club.com/forums/showp...&postcount=408

re waiting after beeps

When using EcuFLash, connect the cable, click on "read rom" (or "write"), the prompt will ask you to turn on the ignition - do turn on the ignition, wait until the bipping stops (i think 5 bips), then wait another about 6 seconds, only then click on that pop up box confirming that the iginition is "on".

Steve,


I did verify that 32bitbase file is there under bases folder. My concern is that ecu not communicating so its going through OEM bootloader, is this normal?

When I open the stg1 A00C.bin in ecuflash, it ask if I want to correct the checksum, should I click yes or no?

The OFT Bins do not have checksum corrected its done by the OFT Tablet so you will need to correct the checksum with ROMRaider i am not sure ecuflash does it correctly. but you could try doing it in ecuflash.

Make sure your battery volts are good, bad flash can be caused by low battery volts maybe attach charger.

Steve,


Battery is good but not sure on how to correct the checksum in RR. I read the post and its telling to look through the tables. Not sure on what I'm looking for and what to correct. Can you point me in right direction?

If you just open the rom in rom raider then save it it should correct the checksum.

On the left hand side their is a table list about half way down their is one called "checksum fix"

RR will fix the checksum on a save regardless of the setting in the "checksum fix" tables so just open it then save the ROM again

This is what I did:


1. I took stg1 A00C.bin, opened it in RR then I saved it as stg1A00C.bin


2. I open ecuflash and open this bin stg1A00c.bin, again it ask too correct checksum, I said no. When I tried to flash it, it bombed fairly quickly.


3. After it bombed, I closed ecuflash while the ignition is on position. And reopen ecuflash again, decided to use stock.srf instead. The flash completed successfully, there is a god. Waited and crank it over, somehow the car was flashed with stock. I send amen and call it the night. I'm chalking this as hell of experiment.

According to utekineir, you are a dimwit because you did not figure this out in 5 minutes.

But dont go looking for that quote because he deleted it....

I didn't delete anything mods probably did and I stand by my statement that there is enough information in the linked threads to make it work.

I thought you were a 50+ year old mature grown ass man that contracts for nasa not a grudge holding child that saves and references quotes from a month back.

I was merely stating a fact. YOU are apparently the one with "issues" or the mods probably would not be censoring you. And I never said that I was 50+...

And I ws NOT "saves and references quotes from a month back".
It was on the very page of the link 3 posts above. :slap:

AND If I WAS 50+ I would probably threaten to "bend you over my knee"....

Still butt hurt from a month ago, tagging and quoting. I hadn't thought about the giggles you provided a month ago since then, obviously you haven't moved on like a clingy ex.


Way to go, you're awesome at the internet.

^ why don't you both stfu. byeeeeeeeeee

Talk to the 8 year old that brought me in with his tag and quote.

hahaha

Question: What was your stock ROM?

I thought that if you pulled a ROM that you did not have a definition for, then you couldnt write it back on?

Maybe the fact that it saves the file as a *.srf means that it can be restored without a definition...

very good question if i had a tactrix box id give it a go, would be a very usefull feature if you had a rom with no definition ie new one flashed by dealer.

maybe some of the guys with a tactrix could do some more work on the "how to flash with tactrix guide " started by @stugray and edited by @vgi

Stugray,

Here are my stock ROM from my vehicle both *.srf and *.bin.

I have engage Mike from Tactrix on this issue with the logs files. Like I said, all the *.xml are in right path.

If you think or know I did something wrong let me know. I followed every steps that I have read from other posts.

FRS-AZ - Thanks

Your stock ROM is ZA1JA00C

There IS an ECUFlash definition file: https://github.com/TD-D/SubaruDefs/b...Z/ZA1JA00C.xml

Did you have that on the machine when you reflashed the *.srf file?

Yes and here is the copy of the xml file from path:

openecu\ecuflash\rommetadata\subaru\BRZ\2012\


Hopefully its the correct one!!

The difference between the *.bin / *.hex file format and *.srf is that srf can deal with non-contiguous ROM areas, whereas *.bin / *.hex cannot. RR unfortunately cannot read srf files at this stage.

I would use Ecuflash to correct the checksum - there was a discussion on the BRZ thread over on the RR forums how the checksum is calculated (it's significantly bigger than the older roms, and required some code changes).

Have you tried again yet?

I am curious if you have figured out what went wrong.

No word from Mike or Tactrix yet.