Toyota GR86, 86, FR-S and Subaru BRZ Forum & Owners Community - FT86CLUB

Toyota GR86, 86, FR-S and Subaru BRZ Forum & Owners Community - FT86CLUB (https://www.ft86club.com/forums/index.php)
-   Software Tuning (https://www.ft86club.com/forums/forumdisplay.php?f=88)
-   -   Tactrix EcuFlash Info for BRZ 86 FRS Rom flash update and logging (https://www.ft86club.com/forums/showthread.php?t=62332)

MGPAX 05-06-2018 05:05 PM

Does anyone know where I can find a copy of a '14 BRZ auto ZA1JB00D original file. Mine is corrupted and I need to go to the dealer for 60K checkup.
Thanks for your help.

veta400 05-09-2018 07:11 AM

Hello, i have an 2013GT86 and because it has ZA1JA00G in it, i wanted to uprgade for ZA1JA01G rom. Why? Because i dont have full definition for 00G but found full definition for 01G.
What i did? Downloaded my ZA1JA00G and save to srf, and if i try to save bin it writes something about need to erase some zero data, and the bin file is shorter, so it cant be edited in RR.
When i write the ZA1JA01G file normally without issue, but the ignition was not able to turn off. I was scared, and reflashed it back to ZA1JA00G, and the Car is fine now.

I made some changes to DBW, IGN, AFR and made some progress, gained few HP and Torg. But i want to play more, also with Cams etc...

Did i done something wrong, or how can be the "upgrade" of firmaware done correctly ? For example EVO has Immo code it the rom, so it neads to be transfered in new rom..... but i didnt find anthing like in the GT86/BRZ rom.



Thank you for any usefull info.


steve99 05-09-2018 08:12 AM

Quote:

Originally Posted by veta400 (Post 3084185)
Hello, i have an 2013GT86 and because it has ZA1JA00G in it, i wanted to uprgade for ZA1JA01G rom. Why? Because i dont have full definition for 00G but found full definition for 01G.
What i did? Downloaded my ZA1JA00G and save to srf, and if i try to save bin it writes something about need to erase some zero data, and the bin file is shorter, so it cant be edited in RR.
When i write the ZA1JA01G file normally without issue, but the ignition was not able to turn off. I was scared, and reflashed it back to ZA1JA00G, and the Car is fine now.

I made some changes to DBW, IGN, AFR and made some progress, gained few HP and Torg. But i want to play more, also with Cams etc...

Did i done something wrong, or how can be the "upgrade" of firmaware done correctly ? For example EVO has Immo code it the rom, so it neads to be transfered in new rom..... but i didnt find anthing like in the GT86/BRZ rom.



Thank you for any usefull info.


A01G ro is directly compatable with A00G

Jist flash A01G to car, old ro will be completly erased no need to transfer anything

tomm.brz 05-14-2018 10:27 AM

is it possible to write a v4 ots rom (so patcher with launch control and ffs) edited with rom raider, with ecuflash?

ermax 05-14-2018 12:34 PM

Quote:

Originally Posted by tomm.brz (Post 3086432)
is it possible to write a v4 ots rom (so patcher with launch control and ffs) edited with rom raider, with ecuflash?



Yes

Conti93 05-26-2018 11:22 PM

2 Attachment(s)
Thank you very much Steve for your work.

For anyone wondering, the ZA1JF10I (late 2015 italian AT) uses the same def as the Subaru counterpart ZA1JF20Q, and can be replaced with ZA1JA01I for logging purposes as per Steve post.
I've attached to this post the original ROM in case anyone needs it.

By the way, tonight I flashed a MY17 GT86 with my Tactrix and the ZA1JK00G OFTv4.03 ROM, and I've encountered a strange problem.
After the first flash and two logs I decided to pull some timing and exhaust retard since it was knocking quite heavily. I proceeded with the second reflash, and after that the car refused to start, cranking repeatedly without firing up.
So I reflashed the stock ROM, and after that no cranking at all, only DCT B1571 "Immobilizer key check NG" :confused0068:
http://i.imgur.com/Hqvab37.jpg
After losing 10 years of life in an hour, since the car is of a friend of mine, I performed the "ECU communication ID registration" (also described in the ECU replacement thread) and all is well now.
Isn't that supposed to happen only when flashing an older rom to a MY17 or newer car?
The rom and definitions used are attached to this post. First one worked, second one triggered security lock. Is that possible?

The only thing I found is this, which states a "checksum fix" performed on that definition. Can a wrong checksum trigger the security lock?

steve99 05-27-2018 12:51 AM

Quote:

Originally Posted by Conti93 (Post 3091925)
Thank you very much Steve for your work.

For anyone wondering, the ZA1JF10I (late 2015 italian AT) uses the same def as the Subaru counterpart ZA1JF20Q, and can be replaced with ZA1JA01I for logging purposes as per Steve post.
I've attached to this post the original ROM in case anyone needs it.

By the way, tonight I flashed a MY17 GT86 with my Tactrix and the ZA1JK00G OFTv4.03 ROM, and I've encountered a strange problem.
After the first flash and two logs I decided to pull some timing and exhaust retard since it was knocking quite heavily. I proceeded with the second reflash, and after that the car refused to start, cranking repeatedly without firing up.
So I reflashed the stock ROM, and after that no cranking at all, only DCT B1571 "Immobilizer key check NG" :confused0068:
http://i.imgur.com/Hqvab37.jpg
After losing 10 years of life in an hour, since the car is of a friend of mine, I performed the "ECU communication ID registration" (also described in the ECU replacement thread) and all is well now.
Isn't that supposed to happen only when flashing an older rom to a MY17 or newer car?
The rom and definitions used are attached to this post. First one worked, second one triggered security lock. Is that possible?

The only thing I found is this, which states a "checksum fix" performed on that definition. Can a wrong checksum trigger the security lock?

What was original calid of car you flashed K00G rom to ?? K series roms not conpatable with 2012-2016 cars for 2017+ only

When flashing with tactrix always answer yes when it asks to crrect checksum

Conti93 05-27-2018 10:19 AM

Quote:

Originally Posted by steve99 (Post 3091942)
What was original calid of car you flashed K00G rom to ?? K series roms not conpatable with 2012-2016 cars for 2017+ only

When flashing with tactrix always answer yes when it asks to crrect checksum

The original CALID was ZA1JK00G, I'm not that stupid :lol:
So I probably misclicked "no" at "correct checksum"? 99.99% I clicked "yes" because I saved the ROM again, then reopened it and didn't ask for any checksum correction before flash..

tomm.brz 05-27-2018 12:24 PM

To understand better what you did and try to help:
You flashed an unmodified v4 k00g to it so ecuflash defs must be good
Did you then modify the rom with romraider or ecuflash? Is v4 RR def the one from Shiv? Where do v4 ecuflash def come from? Do they match 100%?
Problem came out when you did modify the map so must be something def related

steve99 05-27-2018 04:57 PM

Quote:

Originally Posted by MGPAX (Post 3082849)
Does anyone know where I can find a copy of a '14 BRZ auto ZA1JB00D original file. Mine is corrupted and I need to go to the dealer for 60K checkup.
Thanks for your help.

Use the B01D its a factory update to B00D

steve99 05-27-2018 04:59 PM

Quote:

Originally Posted by Conti93 (Post 3092000)
The original CALID was ZA1JK00G, I'm not that stupid :lol:
So I probably misclicked "no" at "correct checksum"? 99.99% I clicked "yes" because I saved the ROM again, then reopened it and didn't ask for any checksum correction before flash..

Ok :-)

If it was romraider modified or oft rom you would definitly need to correct checksum

Else ecuflash will write rom to ecu with incorrect checksum calculated. This will cause ecu to think rom is corrupt and will not run the rom in ecu, hence car will not start. As the ecu would likly have only run the boot area then stopped, it likely caused the imobilisier\authentication unit to lock out hence you required the ecu resync to get car going again. Good to see its all sorted now

Conti93 05-28-2018 01:21 AM

Quote:

Originally Posted by tomm.brz (Post 3092024)
To understand better what you did and try to help:
You flashed an unmodified v4 k00g to it so ecuflash defs must be good
Did you then modify the rom with romraider or ecuflash? Is v4 RR def the one from Shiv? Where do v4 ecuflash def come from? Do they match 100%?
Problem came out when you did modify the map so must be something def related

Exactly.
ROM has been always modified with ROMRaider using Shiv's def from the same .zip.
The ECUFlash def was converted with RR2EcuFlash.exe then adjusted manually (flash method subarubrz and SH72531).
If you want to see ROMS and defs used that night there's a zip containing both in my previous message.
Later I'll check if EcuFlash warnes me for the checksum or not..

P.s. are you from Forlė-Cesena??? :D

EDIT: Now I feel like a dumb ass for not recognizing your nickname.
We were side by side on Muraglione on Christmas Eve :lol: :offtopic:
http://i.imgur.com/2xm726l.jpg

EDIT 2: I am an idiot. Note to self: do not flash cars past 1 AM..
http://i.imgur.com/sQay32x.png
I was comparing my A01G with the new K00G on my desktop PC and ended up saving the A01G with the wrong name. Then I moved it to my laptop where I have both defs and flashed without paying attention to that little detail in EcuFlash log. That's why it locked up.
Sorry for the lost time, I assume that's a good reason to keep only one definition at a time in EcuFlash folder :bonk:

steve99 05-28-2018 10:54 PM

Yes ecuflash no check like ecutek or oft jist flasges whatever you tell it :-)

Lakitu 07-08-2018 03:09 PM

This post just saved my ass. Thanks so much dude!!


All times are GMT -4. The time now is 07:46 AM.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
User Alert System provided by Advanced User Tagging v3.3.0 (Lite) - vBulletin Mods & Addons Copyright © 2026 DragonByte Technologies Ltd.


Garage vBulletin Plugins by Drive Thru Online, Inc.