Quote:
Originally Posted by Td-d
In defense of Ecuflash, the few situations where people have had issues are when OFT roms are being flashed without understanding what the OFT has implemented to prevent users from flashing anything other than the correct rom onto their ecu.
In a nutshell - any OFT rom is in most cases not the actual calibration ID that is stated on it. In other words, if the rom says AZ1J700C, for example, on the latest V2 roms - it is not actually AZ1J700C. The actual rom being used is AZ1JD00C, where the calibration ID has been manually changed to AZ1J700C - that's the process that the OFT uses to prevent OFT users from loading the wrong rom onto their ecu.
Now that works very well for the OFT users - since the definitions provided are actually all based off one rom - in this case AZ1JD00C for example - despite the roms being named the full range of released rom. The problem comes in when you cross the pond to open source - when a definition is provided that says AZ1J700C, it is for AZ1J700C. So when you read an OFT rom, say version 2 - you are using the wrong definition. This is where the problem can comes in, with incorrect checksums being calculated, critical areas of the rom being edited that should not, etc. It is not an inherent flaw of Ecuflash - but a direct consequence of how the OFT works.
That being said - what Steve says above is the point - you need to understand what you are doing when using the OP2 - the onus is on you. There is always someone to ask on here if you are unsure - rather ask, than risk the headache of having to recover / SHBoot your ecu.
|
I have no problem with Tactrix/Ecuflash Romraider or opensource and have a great respect and admiration for the opensource guys who put in countless hours of their timeand considerableskils and expertise for basily free.
My intention was to save opensource/ecuflash from being blamed for bricking ecu,s, it a good and powefull system just needs that bit more understanding to use.
Yes both who got into trouble, basicly unboxed Tactrix loaded ecuflash then proceeded to read/write roms with basicly no understaning of definition files calid bitbase ect or even their existance , it only worked as they happened to want to flash a USA rom and thats the defs that come with ecuflash, unfortunatly they fell victim to the calid trap.
However they just appear to have loaded a rom that ecuflash would flash without knowing their original calid, lucky they were not in another region even some roms from same region dont work eg D00G into A01G does not work well but doesnt brick ecu .
Thanks again Tdd