Hi, so this being my first post here apart from the introduction, don't go too hard on me please
Anyways let me get to the situation at hand:
Several days ago my audi a8 d2 3.7 litre + lpg was doing just fine... I parked it on the mall parking lot, turned it off, got out, came back, put the key in the igniton, turned it to ignition, the dreaded key light started flashing. Took the key out, turned it 180 degrees, tried again, still flashing. Tried to start it, standard immo procedure - ran for half a minute and turned off. Tried several more start attempts, no-go.
So I went to search for remedy, found this forum, (by the way the amount of stuff here is awe-inspiring, don't know how I missed it before?) and started reading and searching.
Needless to say, i found a ton of usefull stuff, but its all still bunch of info that im still only putting into right context. So, i have an ELM 327 OBDII cable, and decided to give it a go.
First after reading all that I found about the immo and eeprom on several posts, i went to my car, plugged in the obd, turned the key in the ignition to on, and opened the cmd, folowed the instructions on how to read the eeprom using the me7-eeprom-1.40 (not really knowing what to do, try-fail-try again something different method), and got the 'initiating communication... FAIL (error=0x21007)', after it opened com port ok. So, i know the cable can read some data on several cars, but I didnt do this part :
'- If you are using a KKL lead, download D2xx drivers from here:
http://www.ftdichip.com/Drivers/D2XX.htm'
(from the guide)
After several attempts of changing the baud rate and retrys, i decided to try the bootmode command line but with -r (read) parameter instead of -w (write).
To my 'amazement' it produced almost the same 'check cable' error after it prompted the 'starting boot mode - FAIL - no echo, check cable . (error=0x20B07)'.
So then not knowing what to do, i took the key out of ignition, put it back in, turned it and voilá! - immo is ok??? how? why? I mean, i really didnt establish any communication with eeprombecause of (i think) the cable?
Anyways, the engine starts, runs, but wery badly all off a sudden, shakes like hell, dies if i try to depress the gas pedal or put it in drive....
So im at a loss here, dont know if and what i messed up now, dont really know how to check error codes if it finds any through the ELM327 OBD2 cable, dont know how to check if i fried the ECU somehow...
Also, I wanted to ask - is bootmode on this type of ECU (gotta check the number?) only achievable by shorting the pin 24 (afraid to not really comprehend the instructions and doing more damage) or is it possible to do it over the OBD cable? I dont really understand this part. I think I understood it only works over some OBD cables and only on some of the ECU-s?
And another thing, while im at it, are there any .bin files and would a 'stock' flash (if there is a 'virgin' ecu file here) be recommended in this situation? Because i dont know if i messed the values somehow on the eeprom...
Please anyone any suggestions?
