I loaded up the OBDII readiness code patch, and the new EGR disable routine yesterday, and everything seemed to load fine .xml wise as I could see the tables and I could change the hex... I closed out Ecuflash to go upload the new rom to the car. I get out to the car to upload the rom, and when I open up ecuflash and click on the new rom I created I get a parse error/check sum for like row 395 row 50 (something like that) for some reason... okay I guess I somehow loaded the xml wrong... I go back through and double check everything and all is well...

I get a new stock xml and reapply the patches and reload everything into ecuflash... still no go still same error message.

I uninstall ecuflash and load up the newest version 1.42 and then get the no parse error message yet again WTF.

I uninstall ecuflash yet again, and reinstall 1.35 and download the rom off my car with previous flashes, and it loads up fine. I add all the xml patches i previously had and now everything is fine. I just thought it was a weird glitch and see if anyone else has ran into this. I am just glad that I remembered excatly what patches I had on the car, and exactly where to go to find them!

Thanks goes out to Chaotichoax for generally organizing the sticky with all the ecu topics, and to all the ecu gurus that have made all this possible.

 

I haven't seen that error yet but then again I just flashed my first OBD II readiness code car. Everything went smoothly. Backed the car out of my stall and went to the st. insp. bay. The car passed with no problems.

 

A parse error means there is an error in the XML file syntax. Your ROM is unaffected. If you get it again, note the line number, go to that line number in the xml file, and look for the error.

 

^ thanks for the info...

 

+1. In general before making xml changes always just back up the files somewhere else and if this happens you can always quickly roll back.

 

i really need to learn how to do all this lol.

 

Another cheap trick you can usually use is try to load the xml in IE. If its not properly formed it won't load in IE.