Quote:
Originally Posted by Tor
Thanks freerunner, we cross posted.
I will make a read/save first thing.
Everyone from my neck of the woods seems to have A01G, so I suppose I do as well. That's one less thing to worry about then.
I already updated the 32bitbase, with the one from Github. I just wanted confirmation that it was correct.
Which RR file from Kodename47 should I pick? Is his "standard" definitions also containing the extra tables?
|
don't get me wrong im not being an ass.
Over the past three years ive attemped to help several people who have bricked their ecu due not understanding the process and whats going on with flashing/defs/roms ect.
Bricking your ecu was quite expensive until we discovered the process to exchange ecu yourself , before that it was buy new ecu from dealer and get them to install and code in, about $1300 our money.
It took me quite some time to understand this process and their was basicly nothing written on how to do it back then.
This process is robust if you know what your doing and understand the process.
Its also very unforgiving if you get it wrong, once ecu is bricked its bricked, its not like a memory stick you can just erase and try again.
Things change constantly, and at freerunner said your usually ok with A01G roms/defs but oft guys change stuff all the time so you need to check. Also A01G is not suitable for all cars only up to about mid 2014 manuals.
Read out your stock rom first
Save a copy as .srf and .bin
Establish which calid it is
Play around with ecuflash and romraider and tunes before you try to flash
Conform the rom calid of the rom your going to flash
check tables in ecuflash and romraider if your editing and before flashing
always allow ecuflash to correct checksum if it askes (failure to do this will likely brick ecu)