Quote:
Originally Posted by YwllowFox
Okay, I've done some stuff now:
first I took the Definitions from Github (RR_ZA1JA0G) and copied the tables MAF Correction after Start inGear/neutral to the definitions file from OFT (OFTv4_ZA1J700G.xml) and I looked at my OFT Stage 1 Tune and the Original ROM.
It looked alright and the tables appeared. I changed one single Value (the first one) and saved the bin like that.
After that I went and compared the new bin with the unchanged bin in a Hex comparer. And it looks like there is only one change at the address of the table and some others at the end of the file (i think this might be a kind of checksum or smth like that...?).
After that all I think the bin would be perfectly flash-able onto my ECU (or am I missing something here??) because the definitions are not used for flashing with OFT right?
So if I am not mistaking,I could use these modded Defs to change all those tables which i cant see on the OFT Defs (MAF Correction after start), and then go back to the other Defs (if I made any mistake) and change the other tables and flash my modded Stage 1_withColdStart Tune onto my car without any hesitation with the OFT.
I still don't get it why one shouldn't use the Github Defs for editing the oft tune roms. Or at least when the tables are at the same Addresses, why not? Is there something that the romraider does to the rom when using defs? which like changes the way the rom gets flashed or what?
Thank you so much.
PS: Steve are you working in this space or why is it that you got so much Experience in this? I've seen you in so many threads, always helping the technical questions.
|
Ok oft looks at the ecu calid strings at 8000 and 10000 hex to determine what it thinks is the ecu calid. With oft tunes they often alter the first two calid strings ar 8000 and 10000 hex . The real calid is the third calid string arround 11000 hex , you can see these with hex editor search for ZA1J which all calid steings start with
OFT wants to match the first two calid strings with whats in the stock rom it originally read from car
Unfortunately romraider only checks whats at 8000 hex and this get latered in oft tunes so romraider get confused
for exapmple your rom was indicating 700G but internally its rearly a A01G compatavle rom
Each time subaru\toyota complie a new rom the tavles are often in different positions so you can end up editing program code not tables and that can end up "bricking" your ecu
What you have done seems correct as you 700G oft tune is actually a A01G rom altered to look like 700G
OFT hack there defs to match tunes where romraider defs expact unhacked roms