Any help guys?

It looks completely fine like any other B01C rom.

Its a A01C rom tho ? Theres a tune that creates pops in the exhaust would i still edit it the same way? Im on my phone so i cant post the link

Sent from my SGH-T999N using Tapatalk

It's been said a hundred times, if you don't know what roms are used as the basis for the openflash roms, and don't know how the definitions work, then you shouldn't be fucking around with them. If you want to take roms provided by the openflash guys and use them on a cheaper system, it's up to you to understand what you're doing. We are not here to spoon feed the same answer to the same question asked by a different person every two days.

you can either delete those trigger lines or put semi colons at start so tghey are comment, but id just delete them. use a basic text editor fancy ones like work may insert formatting characters or hiden characters which stuff up the file.

no need to remove sd card whan flashing.

if no triggers it just starts logging on ignition on or plug in and stops on ignition off.

to be safe i plug in with ignition off then turn on do runs then igninition off then unplug.

Okay bud, you need to relax and take it down a notch. I set everything up my self with ecuflash the only reason I ask is to double check. Nothing more, nothing less. If you get so frustrated at people asking the same question all the time then you shouldnt be on a forum. Thanks for the help though.

Sent from my SGH-T999N using Tapatalk

He's frustrated because the answers to all of your questions are in this thread. Including as to why he references the B01C rom regardless of his car being an A01C.

All of the OFT Tunes are based on the B01C Rom.

Hmmm not correct in V2 tunes roms prior to B01C like 700C A01C were based on B01C, but not case for V1x tunes still floating arround after B01C theirs still some calid changes to D00C F00C F40C and corresponding D series roms, its pretty random and sometimes its a forward calid change somnetimes its backwards. It also happens on other rom series like G I and possibly others.

eg a OFT A02G rom is actually A01G and the E00I is actually a A01I, happens in usa roms as well.

Changes again on the oft openflash header specific tunes as well they have different calid hacks again.

And the turbo ans SC roms are different again and the flex roms are different again they are likely A01G australian roms looking like C series roms of various calid like A01C B01C

You cannot pick it unless you look at rom with hex editor and check the three calid locations in rom.

These hacks are done to make the oft roms work with oft system. They are not designed to catch you out but they will if you dont check the roms.

Failure to do this and not understanding the basics of definitions and flashing process basic tables checksums etc has resulted in several people bricking their ecu.

Romraider and ecuflash only check the first calid at 8000 hex.

oft hacks both the 8000 and 10000 hex calid, the third one at a bit over 11000 is the real rom calid.

These hacks fool romraider and ecuflash if your not using matched hacked definitions.

The best way is to use the native rom there all 3 calid are same

Ahh thanks for the clarification. I guess I wasn't thinking about Rom's abroad outside of the US. I thought most of them were and still based of the B01C.

I no longer use a tactrix cable myself. Was a nice cheap option, however looking back on it I wish I just spent the money for an OFT/ECUTek right off the bat.

Added ZA1JA02I stock rom for Australia Europe and south Africa 2014 Auto transmission cars

Can anyone give me link to get the original oem za1ja00g file? this is not on the first page:( Thank you guys

You much better to flash the updated A01G or A02G rom to a car that came with A00G as the old A00G rom did not have transient retard DI seal fix.

Dealer should have flashed all earlier 700G or A00G car to A01G or A02G




Attached is A00G rom but I recommend you use the A01G or A02G its a much better ROM

Having issues with logging on the Tactrix OP2. Reads and Writes ok but doesn't log at all.

First problem is it doesn't even recognize the cable as a storage device so I had to use an SD card reader to input the logcfg.txt file

Second problem is no matter what I do I can't get it to log what so ever. I deleted the start/stop conditions entirely, reformatted FAT32(not sure if cluster size matters but its set at 32KB), made sure the file was in the root directory and named logcfg.txt and attempted the methods of initiating the log described in this thread. Just flashes those rainbow colors do matter what I do.

Hmmm with SD card in device, you should be able to see the SD card as a usb drive when tactrix connected to computer.


assume you don't have usb connected when trying to log as it wont work, must be standalone to log ie just plugged into obd port.


It possible the devices sd card slot is faulty, maybe talk to the tactrix guys.