NefMoto

Technical => Flashing and Chipping => Topic started by: erroob0977 on September 08, 2011, 06:10:39 PM



Title: ME7.1.1/7.5 Programming Not Finished - P0602, P1681 or 18089
Post by: erroob0977 on September 08, 2011, 06:10:39 PM
I flashed my 2004 A6 (4z7907551S) with a tuned (and checksum corrected file). Afterwards the car would not start, it kept cranking but wouldn't turn over. Before I tried to start it I was able to connect with VCDS, after trying to start it I couldn't connect with VCDS or Nefmoto.

I unhooked the battery for a minute, hooked it back up and was able to connect again after that. I then flashed the stock file back to the ECU. Before trying to start it I connected with VCDS and had an fault for Control Module Programming Not Finished (18089 / P1681) so I wasn't surprised when I tried to start it and got the same behavior as after the first flash. I tried a few other bin files for my ECU and had the same result every time. I had to disconnect and reconnect the battery between each attempt.

Wondering if anyone had any thoughts or know what may be going on?

[ed: fix/workaround thread here http://nefariousmotorsports.com/forum/index.php?topic=6719.0]

[ed: Another old 18089 thread here http://nefariousmotorsports.com/forum/index.php?topic=1845]

[ed: list of known broken ECUs]

06A906032RN
06A906032MS
4B0906018DQ
4Z7907551S
4Z7907551AA
8E0909518AK
8E0909518AQ
8E0909518AS
8N0906018CJ

Pretty much anything newer than 03 is going to have this problem.



Title: Re: 4Z7907551S Control Module Programming Not Finished - NO START
Post by: Tony@NefMoto on September 18, 2011, 06:43:53 PM
I assume you are flashing your ECU with the NefMoto software?

Do you know which version of NefMoto you are using and do you have a log file of the flashing process?


Title: Re: 4Z7907551S Control Module Programming Not Finished - NO START
Post by: Enclavet on September 23, 2011, 10:20:44 PM
I am using Nefmoto 1.8 and I get the same issue. I also get code P0602.

Attaching log.


Title: Re: 4Z7907551S Control Module Programming Not Finished - NO START
Post by: Enclavet on September 24, 2011, 12:07:14 PM
So I flashed a 4Z7907551R file that Tony posted on the forum and the car worked. Wierd that I have a tiptronic car and tried at least 4 4Z7907551S flashes on the board and none of them worked. Flashed the 4Z7907551R file and got it working again.

Regards,

Andrew


Title: Re: 4Z7907551S Control Module Programming Not Finished - NO START
Post by: Drludlow on April 06, 2012, 03:59:22 PM
Flash reported successful. no start and the below code. Quick research revealed others had corrupted 95040. pulled the 95040 and it has several differrences from the ori. Fixed via bootmode rewriting of 95040 via argdubs tool. If i hadn't pulled the 95040 image to get the SKC I would have been in a pickle. Whats with the nefmote tag at the end of the 95040 dump. My CH box has that in there as well but it is the only diff and the car doesn't care

18089 - Control Module Programming Not Finished
            P1681 - 35-00 -


blue cable
win7

3 flashes


Title: Re: 4Z7907551S Control Module Programming Not Finished - NO START
Post by: erroob0977 on April 12, 2012, 10:13:18 AM
EDIT: For anyone in the future wondering - If you flash 4z7907551S bin and get the P1681 error, all you need to do is reconnect with NM Flasher, do a full read of the ECU (reading back the bin you just flashed - I just save it as 'junk.bin' and delete it later). Then hit disconnect in NM Flasher, cycle the ignition and it'll start right up.


Title: Re: 4Z7907551S Control Module Programming Not Finished - NO START
Post by: AARDQ on August 05, 2012, 10:22:29 PM
Wish doing a full read afterwards had worked for me...  Same 4z7907551S box (at least, reports as S in VCDS; it is labeled R and the 95040 (really, 5P8C03) also reports as R).

So what happened was:  Read and saved the 95040 using Argdub's tool -- no problem.  Or maybe there was, I never tried to start the car aftwerwards so can't say for certainty that something didn't corrupt at that point.

Read the box (no flash, just a read) using the Nefmoto software.  Worked fine.  Except, no start afterwards, with the 18089 - Control Module Programming Not Finished flag set.  I'm sure I hit Disconnect before closing out, but there you go.  Tried reading it fully again, but no luck, no start, Control Module Programming Not Finished flag still set.  Definitely hit Disconnect before closing out.  (Tried this several more times.)

OK, still no prob, plenty of tricks up my sleeve.  Took the box to the bench and using the GQ-3X wrote the saved 95040 back to my spare AA box's EEPROM.  Wanted to do that someday soon anyway since the AA is a (mild) tuning upgrade over the stock box, just bummed that it's not on my terms.

Nope, now reporting Immo tripped (I thought that was all that was necessary to use a different ECU was to imprint the original EEPROM's contents onto the new box's EEPROM?)  What's strange is the bits others have reported as tripped when Immo is tripped, weren't tripped.  Apparently (dash?  ECU itself?) knew that there was a VIN mismatch between ECU and 95040.
In the end, ended up using a "generic IMMO Off" bin; getting too late to do anything else. 

Any of this sound familiar to anyone?  What could I have been missing?


Title: ME7.1.1 Programming Not Finished - P1681 or 18089
Post by: AARDQ on September 11, 2012, 01:12:17 PM
Working with 4Z7907551AA and 4Z7907551S, I continually run into the 18089 - Control Module Programming Not Finished
            P1681 - 35-00 brick wall.  Reads and writes work fine using the Nefmoto flasher (i.e. I've never been locked out from communicating) but always get the error, with no start as a result.  I had been succesful earlier in clearing the error by loading a generic 95040 to the EEPROM and getting the Flash and EEPROM on the same page, but I guess I just was lucky because that isn't working for me now.  It seems like the EEPROM and Flash are passing the Programming Not Finished msg back and forth -- enter programming mode and that info gets passed to the EEPROM; cycle the system after flashing and the EEPROM sends the msg back to the flash?  Or is that flag getting set elsewhere?

Any ideas or suggestions as to technique or methods appreciated (including boot-mode-- I've never been able to get one of these into boot mode, so if anyone has a generally fool-proof method for the 7.1.1, I'm all ears.)

Thanks in advance, I'm not intending to be a leach but I can't contribute at this point...


Title: Re: ME7.1.1 Programming Not Finished
Post by: NetMofo on September 11, 2012, 01:46:37 PM
Working with 4Z7907551AA and 4Z7907551S, I continually run into the 18089 - Control Module Programming Not Finished
            P1681 - 35-00 brick wall.  Reads and writes work fine using the Nefmoto flasher (i.e. I've never been locked out from communicating) but always get the error, with no start as a result.  I had been succesful earlier in clearing the error by loading a generic 95040 to the EEPROM and getting the Flash and EEPROM on the same page, but I guess I just was lucky because that isn't working for me now.  It seems like the EEPROM and Flash are passing the Programming Not Finished msg back and forth -- enter programming mode and that info gets passed to the EEPROM; cycle the system after flashing and the EEPROM sends the msg back to the flash?  Or is that flag getting set elsewhere?

Any ideas or suggestions as to technique or methods appreciated (including boot-mode-- I've never been able to get one of these into boot mode, so if anyone has a generally fool-proof method for the 7.1.1, I'm all ears.)

Thanks in advance, I'm not intending to be a leach but I can't contribute at this point...

This happens to me often with my '04 A6 (even this past weekend), flashed a 4Z7907551S and got the 'programming not finished' error.  All you need to do is use Nefmoto to read the the ecu flash and write it to a file (i.e. save a new bin file), then disconnect, turn off ignition, wait 60 seconds and start - You should be good after this.

http://nefariousmotorsports.com/forum/index.php?topic=1845.msg17936#msg17936

Good luck.


Title: Re: ME7.1.1 Programming Not Finished
Post by: AARDQ on September 11, 2012, 04:48:05 PM
Thanks, I was following that procedure but it sounds like I'm too impatient and am not waiting long enough w/ ignition off.  Too bad I'm traveling the next few days, or I'd head right out and give it a shot.

And thanks for the link -- weird that Search didn't turn that one up.




Title: Re: ME7.1.1 Programming Not Finished
Post by: AARDQ on September 13, 2012, 07:05:53 PM
I dunno...  Still have not been successful with an S or an AA, even waiting 1 min, 5 minutes or an hour.  I finally just flashed a 551R (thanks erroob0977 for that particularly helpful tip --from the other thread-- that this is software-related and not hardware) and problem solved, she started right up.  I'll just port my tune using that as the base and be done with it.



Title: Re: ME7.1.1 Programming Not Finished
Post by: NetMofo on September 14, 2012, 03:43:25 PM
It's more about performing a second operation than the amount of time you wait after disconnecting.  If you flash a file, try reading it back again to get out of programming mode (the same thing I told erroob0977 months ago).  As for waiting, I usually wait about 30-60 seconds after a read/write operation just to be safe and to let the ecu cycle.


Title: Re: ME7.1.1 Programming Not Finished
Post by: nyet on September 14, 2012, 05:27:02 PM
It's more about performing a second operation than the amount of time you wait after disconnecting.  If you flash a file, try reading it back again to get out of programming mode (the same thing I told erroob0977 months ago)

PLEASE let tony know... I'm SURE this can be fixed in nefmoto.


Title: Re: ME7.1.1 Programming Not Finished
Post by: AARDQ on September 14, 2012, 09:30:45 PM
It's more about performing a second operation than the amount of time you wait after disconnecting.  If you flash a file, try reading it back again to get out of programming mode (the same thing I told erroob0977 months ago).  As for waiting, I usually wait about 30-60 seconds after a read/write operation just to be safe and to let the ecu cycle.

Definitely tried that numerous times, and just about any other combination of clearing DTCs/not clearing DTCs, reading back/not reading back etc. I could think of.  I'm sure it's me or my set-up; clearly it must be if simply reading back works for others.  Using a 551R as the base for tuning is fine for my purposes (although I hate being forced into something).


Title: Re: ME7.1.1 Programming Not Finished
Post by: erroob0977 on September 17, 2012, 06:20:25 AM
Tony's aware of the problem with the 4z7*S box, but my car was out of commission last time I talked to him about it so I wasn't able to get any logs or anything to show the problem. Now that it's back on the road hopefully I can get him whatever he needs and get this fixed.


Title: Re: 4Z7907551S Control Module Programming Not Finished - NO START
Post by: ddillenger on March 26, 2014, 11:55:16 AM
If you attempt to read a 2.7t Allroad or A6 4Z7907551AA, or 4Z7907551S, you will then be stuck with a "programming not completed" DTC, as well as a no start situation!

To remedy this, reconnect with nefmoto (which will still work, thank god for small miracles) and flash one of the attached files. Neither of these have this issue and are compatible with all BEL Allroads/A6's.

Any tuning done on ME7.1.1 equipped 2.7t's should use the 551R (North American) or 551N (Euro) file as a base to avoid complications.



Title: Re: 4Z7907551S Control Module Programming Not Finished - NO START
Post by: coreyj03 on March 26, 2014, 12:00:22 PM
thanks for posting this


Title: Re: 4Z7907551S Control Module Programming Not Finished - NO START
Post by: ddillenger on March 26, 2014, 12:02:37 PM
No problem. You're the third person this week that's done this. With nefmoto gaining popularity, it warrants a warning. Good luck, and please report back.


Title: Re: 4Z7907551S Control Module Programming Not Finished - NO START
Post by: coreyj03 on March 26, 2014, 12:04:43 PM
i will say this has happened to me  with an early version of nefmoto on a b5 passat when i attemped to read it bricked the ecu. this was 2-3 years ago however. and i have not had an issue since except the allroad.


Title: Re: 4Z7907551S Control Module Programming Not Finished - NO START
Post by: ddillenger on March 26, 2014, 12:19:23 PM
Reading an APR or United file will do this as well. My advice, have a recovery solution available before attempting any reading/writing.


Title: Re: 4Z7907551S Control Module Programming Not Finished - NO START
Post by: jackson.amrol@gmail.com on March 26, 2014, 09:33:21 PM
Would not keying off prevent this?


Title: Re: 4Z7907551S Control Module Programming Not Finished - NO START
Post by: jackson.amrol@gmail.com on March 26, 2014, 09:40:54 PM
Would not keying off prevent this?

AS IN can you simply notice, and write the file back.
or
can you not write until it has been keyed off?


Title: Re: 4Z7907551S Control Module Programming Not Finished - NO START
Post by: ddillenger on March 26, 2014, 10:00:03 PM
It's not the file that's the issue, but the fact that nefmoto doesn't properly end the programming session. You can flash it back, then do a FULL READ, save the file, and MAYBE recover it, but it's unlikely. The 551R never fails.


Title: Re: 4Z7907551S Control Module Programming Not Finished - NO START
Post by: jackson.amrol@gmail.com on March 26, 2014, 10:42:03 PM
THANK YOU Double D


Title: Re: 4Z7907551S Control Module Programming Not Finished - NO START
Post by: ddillenger on March 26, 2014, 10:59:38 PM
Four people this week (no exaggeration) have emailed/messaged me after doing this. I hope this will prevent a few "what have I done!" moments.


Title: Re: 4Z7907551S Control Module Programming Not Finished - NO START
Post by: ddillenger on March 27, 2014, 07:51:45 AM
The 06A906032RN has a similar issue. Same DTC, same problem, but the code doesn't actually cause any harm.

Just something to think about :)


Title: Re: 4Z7907551S Control Module Programming Not Finished - NO START
Post by: Snow Trooper on April 05, 2014, 11:02:19 AM
Have had this happen and as stated the R file written over it fixes it.  The S file is very common, I have only had one not do this to me after reading it, not sure why.  I have also found that you can get by without changing to the R, you have to flash back in the stock file, disconnect, attempt to start, get the code, flash in again and then power down, disconnect the ecu from 12v, power back up and clear codes, then it will start.  But it is obviously easier to just switch and be done with that nonsense.


Title: Re: 4Z7907551S Control Module Programming Not Finished - NO START
Post by: vwaudiguy on May 17, 2014, 10:45:02 AM
Just to add had this same issue on an 04' beetle 2.0 ecu id 06A906032MS


Title: Re: 4Z7907551S Control Module Programming Not Finished - NO START
Post by: ddillenger on May 17, 2014, 10:52:46 AM
Just to add had this same issue on an 04' beetle 2.0 ecu id 06A906032MS

Pretty much anything newer than 03 is going to have this problem.


Title: Re: 4Z7907551S Control Module Programming Not Finished - NO START
Post by: vwaudiguy on May 19, 2014, 09:42:22 AM
Pretty much anything newer than 03 is going to have this problem.

Thanks for clearing that up, D. I assume mpps doesn't have these types of protocol issues? How new a car can mpps interface with reliably?


Title: Re: 4Z7907551S Control Module Programming Not Finished - NO START
Post by: ddillenger on June 01, 2014, 11:46:19 AM
Hard to comment on that. I'm using V18.whatever they are at now.

The clones are pretty good though, certainly more reliable than nefmoto.


Title: Re: 4Z7907551S Control Module Programming Not Finished - NO START
Post by: mounty on June 28, 2014, 04:51:55 AM
So with my v8 allroad being a 2004 I'm going to have this issue as well?


Title: Re: Looking for 4Z7907551S file. Allroad 2004 Tip
Post by: kosiik on August 10, 2014, 02:05:55 AM
Please immo EEprom 95040 files ?
thanks ;)

Ecu reports dtc unfinished programming :(


Title: Re: P1681 Control Module Programming Not Finished. UPDATE: FIXED. Link on page 2.
Post by: ddillenger on September 01, 2014, 01:47:55 PM
fix: http://nefariousmotorsports.com/forum/index.php?topic=6719.0


Title: Re: P1681 Control Module Programming Not Finished. UPDATE: FIXED. Link on page 2.
Post by: nyet on October 15, 2014, 08:33:27 PM
http://nefariousmotorsports.com/forum/index.php?topic=2200.msg65208#msg65208

4B0906018DQ


Title: Re: P1681 Control Module Programming Not Finished. UPDATE: FIXED. Link on page 2.
Post by: ddillenger on October 15, 2014, 08:34:37 PM
http://nefariousmotorsports.com/forum/index.php?topic=2200.msg65208#msg65208

4B0906018DQ

2003+ will experience this.



Title: Re: P1681 Control Module Programming Not Finished. UPDATE: FIXED. Link on page 2.
Post by: edgy on November 05, 2014, 05:26:44 PM
I ran into this today using MPPS with a 4B0906018DQ ECU...


Title: Re: P1681 Control Module Programming Not Finished. UPDATE: FIXED. Link on page 2.
Post by: Ionut on March 19, 2015, 03:11:36 PM
Same here with an 2005 Audi A4 1.8T 8E0909518AQ
Just read over OBD and ecu remained in programming session. P1681 arrived and never goes away. Car cranking but engine doesn`t start.
When connecting with VCDS it disconnects after a minute or two and then connects again, if this matters.
Would the change from 0x2D to 0x0D prevent that fault to came up and engine starts well after that? or the EEPROM is corrupt too?


Title: Re: P1681 Control Module Programming Not Finished. UPDATE: FIXED. Link on page 2.
Post by: ddillenger on March 19, 2015, 03:19:40 PM
Same here with an 2005 Audi A4 1.8T 8E0909518AQ
Just read over OBD and ecu remained in programming session. P1681 arrived and never goes away. Car cranking but engine doesn`t start.
When connecting with VCDS it disconnects after a minute or two and then connects again, if this matters.
Would the change from 0x2D to 0x0D prevent that fault to came up and engine starts well after that? or the EEPROM is corrupt too?

It'll run fine. Eeprom is fine.


Title: Re: P1681 Control Module Programming Not Finished. UPDATE: FIXED. Link on page 2.
Post by: Ionut on March 19, 2015, 03:26:40 PM
The file also had some other changes than stock (after compared to stock and looked into bottom of file the things are clear. SW is made by a local tuner that i know personally, but not for good work that he`s doing). I can send you ORI and file pulled out from car to tell me what is that modified part of file that doesn`t look to be part of a map and is not the checksum from end of file neither.


Title: Re: P1681 Control Module Programming Not Finished. UPDATE: FIXED. Link on page 2.
Post by: Ionut on March 20, 2015, 02:50:30 AM
Recovered ECU few moments ago. Deleted tuner signature, noread tag, changed that byte you found and flashed file via OBD with FGTech v54. Car started from first attempt.
Before that tried to read 2 times to unlock ecu with no luck.

EEPROM seems to be fine, but i`ve asked him to take off ECU and come to me to make a backup to EEPROM too.... you don`t know what can happen with the ECU in the future.


Title: Re: P1681 Control Module Programming Not Finished. UPDATE: FIXED. Link on page 2.
Post by: KBATTPO on July 23, 2015, 08:25:52 AM
Got the P1681 after simply reading my 4Z7907551S (2004 Allroad 2.7T manual). Did some searching on this site and came upon this thread. Flashed the 4Z7907551R.bin into my ECU. It did indeed get the car to start again but introduced a bunch of new codes:

Code:
-------------------------------------------------------------------------------
Address 08: Auto HVAC        Labels: 4B0-820-043-MY2.lbl
   Part No: 4B0 820 043 AQ
   Component: A6-Klimavollautomat 0208 
   Coding: 00010
   Shop #: WSC 06133 

1 Fault Found:
01314 - Engine Control Module
            49-10 - No Communications - Intermittent

-------------------------------------------------------------------------------
Address 17: Instruments        Labels: 4B0-920-xxx-17.lbl
   Part No: 4B0 920 983 FX
   Component: KOMBI+WEGFAHRS. VDO D17 
   Coding: 00264
   Shop #: WSC 06133 

1 Fault Found:
01314 - Engine Control Module
            49-10 - No Communications - Intermittent

-------------------------------------------------------------------------------
Address 34: Level Control        Labels: 4Z7-907-553.lbl
   Part No: 4Z7 907 553 F
   Component:  - 2C1A1          D060   
   Coding: 25500
   Shop #: WSC 02334 

1 Fault Found:
01577 - Turn-Off due to Over-Temp
            35-10 -  -  - Intermittent

Needless to say I was not happy at all and began to look for the ways to fix my original 4Z7907551S.bin. Came across this thread: http://nefariousmotorsports.com/forum/index.php?topic=6719.0 (http://nefariousmotorsports.com/forum/index.php?topic=6719.0), edited that one byte, reflashed the original 4Z7907551S.bin into my ECU and the car started from a quarter turn and been running great ever since.

BTW, not only did the 4Z7907551R.bin introduce new codes, it eliminated a few that were set off by my deleting of the SAI system, both EGT sensors and both post-cat OXS sensors.

With the original 4Z7907551S.bin:

Code:
-------------------------------------------------------------------------------
Address 01: Engine        Labels: 078-907-551-AZA.lbl
   Part No: 4Z7 907 551 S
   Component: 2.7L V6/5VT     G   0020 
   Coding: 07715
   Shop #: WSC 02335 

7 Faults Found:
17840 - Secondary Air Injection Solenoid Valve (N112)
            P1432 - 35-00 - Open Circuit
17530 - Oxygen (Lambda) Sensor Heating; B2 S2
            P1122 - 35-00 - Open Circuit
17526 - Oxygen (Lambda) Sensor Heating; B1 S2
            P1118 - 35-00 - Open Circuit
17861 - Exhaust Gas Temp Sensor 1 (G235)
            P1453 - 35-10 - Open or Short to Plus - Intermittent
17865 - Exhaust Gas Temp Sensor 2 (G236)
            P1457 - 35-10 - Open or Short to Plus - Intermittent
17522 - Oxygen (Lambda) Sensor; B1 S2
            P1114 - 35-00 - Internal Resistance too High
17548 - Oxygen (Lambda) Sensor; B2 S2
            P1140 - 35-00 - Internal Resistance too High
Readiness: 0010 1001

vs. with the 4Z7907551R.bin flashed into my ECU:

Code:
-------------------------------------------------------------------------------
Address 01: Engine        Labels: 078-907-551-AZA.lbl
   Part No: 4Z7 907 551 R
   Component: 2.7L V6/5VT     G   0003 
   Coding: 07715
   Shop #: WSC 02335 

3 Faults Found:
17840 - Secondary Air Injection Solenoid Valve (N112)
            P1432 - 35-00 - Open Circuit
17530 - Oxygen (Lambda) Sensor Heating; B2 S2
            P1122 - 35-00 - Open Circuit
17526 - Oxygen (Lambda) Sensor Heating; B1 S2
            P1118 - 35-00 - Open Circuit
Readiness: 0110 1101

In the hex editor the 4Z7907551S.bin and the 4Z7907551R.bin also appear to be rather different. I am glad I am able to use my original 4Z7907551S.bin again.


Title: Re: P1681 Control Module Programming Not Finished. UPDATE: FIXED. Link on page 2.
Post by: KBATTPO on July 28, 2015, 09:47:45 PM
Update.
Thanks to the tip from stuklr, I now have the 4Z7907551R.bin running my Allroad. It took two interrogations and two subsequent erases to get rid of the extra codes, but they are gone now.


Title: Re: ME7.1.1 Programming Not Finished - P1681 or 18089
Post by: nyet on July 29, 2016, 03:18:19 PM
Workaround (.bin ASM patch) here: http://nefariousmotorsports.com/forum/index.php?topic=6719.0


Title: Re: ME7.1.1 Programming Not Finished - P1681 or 18089
Post by: Crushing on March 11, 2018, 09:43:05 PM
What am I doing wrong? I am still very new at this but I tried full read with nefmoto on my 2004 a6 2.7t, the. It wouldn't start and was throwing codes po602, p1681 and p18089 programming not finished. After reading several posts on the issue I tried full read several times a long with full write/flash, delete codes, not deleting codes, cycling key, disconnecting battery, writing the 4z7907551r .bin instead of stock 4z7907551s .bin with no luck on either file. I don't want to brick my ecu as I haven't had luck with getting it in boot mode with galletto 1260 yet either. I started looking through the hex editor in tuner pro for this threads fix but after an hour of searching I felt like an idiot thinking there is probably a hex search option that would find it quicker. Please tell me what I'm doing wrong and point me in the right direction.

Sent from my SM-G930V using Tapatalk



Title: Re: ME7.1.1 Programming Not Finished - P1681 or 18089
Post by: AudiA4_20T on June 18, 2018, 09:35:02 AM
Don't mean to bump an old thread, but I have an '05 Passat 1.8T AWM. Ended up having this same issue, I was only doing a read on the ECU, Nefmoto doesn't seem to get the vehicle out of programming mode (DIS lights up PRND432) even if I disconnect. Writing the stock .bin back onto the ECU didn't help, neither did doing another read. I can only drive the car if I clear this code each time I start it.


Title: Re: ME7.1.1 Programming Not Finished - P1681 or 18089
Post by: fukenbroken on June 18, 2018, 02:47:24 PM
fix it and write back
whats the question?


Title: Re: ME7.1.1 Programming Not Finished - P1681 or 18089
Post by: AudiA4_20T on June 19, 2018, 09:18:57 AM
fix it and write back
whats the question?

The question is how do I fix it? I've tried the "do a read and cycle the ignition" and it doesn't work.


Title: Re: ME7.1.1 Programming Not Finished - P1681 or 18089
Post by: vwaudiguy on June 19, 2018, 09:23:59 AM
The question is how do I fix it? I've tried the "do a read and cycle the ignition" and it doesn't work.

Read your binary, search for the string, modify it, calculate checksums, write it back. Alternatively, you can write the original file back with a pro tool, and that will resolve the issue as well.


Title: Re: ME7.1.1/7.5 Programming Not Finished - P0602, P1681 or 18089
Post by: idzioch on May 08, 2019, 03:31:51 AM
8E0909518AQ - P0602 after NefMoto read.

Write ori flash with KESS resolved the problem...


Title: Re: ME7.1.1 Programming Not Finished - P1681 or 18089
Post by: nyet on May 08, 2019, 08:46:47 AM
The question is how do I fix it? I've tried the "do a read and cycle the ignition" and it doesn't work.

There is an entire thread dedicated to fixing this when the "do a read and cycle the ignition" doesn't work.