PDA

View Full Version : Audi A3 2.0 TDI EDC17CP14 - Genuine Ktag Write - Non Starter - Please Help :(



KDScunny
29th November, 2022, 12:27 AM
Hi Guys,

I am at a bit of a loss here. Not sure if we've had a freak accident or what really but I will explained what has happened.

EDC17CP14 Audi A3 2009. ID and Read the file using genuine Ktag service mode, file was then modified with a simple power tune + EGR/DPF off using a switech solution which have used plenty times before.

Written back on and the car won't start, then initially error codes coming up either P1603 "ECU error" or P160A depending on which scanner used. Also intermittently have seen errors relating to injectors when trying to turnover for a while.

Where it gets really strange is if I write the original backup back on the car still won't start, as if something has been lost in the process... my initial thought was immo issue but even after trying an immodelete same issues.

Things we have tried so far:
-Immo delete file
-Reflashing original file on service mode ktag
-Reflashing original file on using Boot Mode (Protocol P151) ktag
-Flashing original file onto the ecu on Ktag and then using genuine Kess with a standard VR file from Alientech DB on OBD...
-Flash original on service mode, then backup with BDM, then reflash with BDM.
-Same as above but also with modified DPF/EGR file.

Nothing seems to be working, ECU communication is fine I can read codes, I can even read and write and ID via OBD when ecu fitted to car but for whatever reason I cannot get it to start. This was supposed to be a pretty straight forward job and has now turned into a multi day nightmare especially over weekend when alientech support was closed.

Yes we have alientech support, they have reviewed the logs and can't seem to find anything wrong with any of the files. BUT in my experience the experts on forums like this know what they are talking about more than Alientech... also they are not open evening or weekends which just makes it worse.

Any suggestions please??

I've attached a couple of the files:
Backup - Original file read with Ktag servicemode
Backupimmo - Modified file with immo delete
BDMBackup - Backup read taken from BDM after writing original back on in SM
VR Ori - VR file for OBD map data.

tutzu
29th November, 2022, 07:49 AM
TRY TO RESTORE WITH FRF FILE ODIS ETC... OR TRY ANOTHER ECU WITH IMMO OFF TO UNDRSTAND IF THE PROBLEM IS OLD ECU

KDScunny
29th November, 2022, 08:56 AM
Hi,

Sorry I'm not familiar with FRF/ODIS?

I don't have a spare ecu was trying to avoid buying one. No idea how I'm supposed to have damaged it when didn't even open ecu until after this issue but I will have a look.

Any other pointers please appreciated

qni666
30th November, 2022, 07:23 AM
write to alientech support