NefMoto

First of all i tried just to validate memory and all of this happenened.  I found out that it had had a apr trial tune in the past.  its a 2004 audi a6 s-line 4Z7907551AA

VCDS-Lite Version: Release 1.1
Wednesday, 18 May 2011, 17:10:05.


Chassis Type: 4B - Audi A6 C5
Scan: 01,02,03,06,08,15,16,17,18,34,35,36,37,45,55,56,57,65,67,75,76,77
 
-------------------------------------------------------------------------------
Address 01: Engine       Labels: 078-907-551-AZA.LBL
   Controller: 4Z7 907 551 AA
   Component: 2.7L V6/5VT     G   0010
   Coding: 07752
   Shop #: WSC 77875
   VCID: 8277890B9D01
   WAUCD64B34N096051     AUZ7Z0D2618165
3 Faults Found:
18089 -  Control Module Programming Not Finished
            P1681 - 35-00 -   -
18011 - Shareware Version. To Decode all DTCs
            P1603 - 35-10 - Please Register/Activate - Intermittent
18010 - Shareware Version. To Decode all DTCs
            P1602 - 35-10 - Please Register/Activate - Intermittent
Readiness: 0110 1101

-------------------------------------------------------------------------------
Address 02: Auto Trans       Labels: 01V-927-156.LBL
   Controller: 4B0 927 156 EE
   Component: AG5 01V 2.7l5VT USA 2223
   Coding: 01002
   Shop #: WSC 02334
   VCID: 6EAF4DBB3999
1 Fault Found:
18258 -  Powertrain Data Bus: Missing Message from ECU
            P1850 - 35-10 -   - - Intermittent

-------------------------------------------------------------------------------
Address 03: ABS Brakes       Labels: 4B0-614-517.LBL
   Controller: 4B0 614 517 H
   Component: ABS/ESP allrad      3428
   Coding: 06397
   Shop #: WSC 02334
   VCID: 263F759BD1E9
2 Faults Found:
18258 -  Powertrain Data Bus: Missing Message from ECU
            P1850 - 35-10 -   - - Intermittent
18258 - Shareware Version. To Decode all DTCs
            P1850 - 35-10 - Please Register/Activate - Intermittent

 

Seems weird. You get no spark/fuel?

Are you able to read the flash using the NefMoto flasher?

If you are in a jam, I just found this:

http://www.audis4parts.com/product368.html

no i'm not able to read the flash.  it seems as though im locked out.

Can you post the log file from the NefMoto flasher?

Validating the memory layout only tries to read the ECU flash, it does modify the flash at all.

One thing you can try, is to connect to the ECU with NefMoto flasher, and then disconnect. That will hopefully cause the ECU to think that "programming" has finished.

tried to connect and reconnect  nothing happened.  The log file is attached

Your ECU has "programming not finished" flag raised.
If next attempts to write with OBD-software can't recover this situation than you must clear this flag manually.
This means to desolder 95040 eeprom chip from ECU board, read it, properly correct content of dump, write back and solder chip in your place.

Or use a professional flashing tool  :P

To the op: If you send it my way I can fix it without desoldering. I just had a 05 GLI do the same thing when I flashed it with Nefmoto. Car started fine but threw "Programming not finished" code. Reflashed with tool and hasn't come back since.

PS: I doubt this is something APR did, but the GLI was APR tuned as well.

No need to actually remove the eeprom if it does need reprogramming. It can be reprogrammed in circuit with an SOIC clip and a programmer such as the UPA-USB.

From this point of view may say more - no need UPA, clips and etc to reprogram eeprom on the board.
Just temporally convert ME7 ECU in "eeprom programmer".
Get freely "minimon" soft, load in boot mode your specially programm and start it - that's all you need.
But if you don't have a set of tools and experience desolder method is the simplest.

You log file shows that you only tried to validate the flash memory layout. Validating the flash memory layout failed though, because reading from the flash memory was disabled.

Entering programming mode in the ECU appears to have caused it to think that it has started programming and not completed. Normally the "programming not complete" flag is only set when you start writing to the ECU.

Can you try validating the flash memory layout again, then click the disconnect button, then turn off the ignition. Then see if you can start the car.

If that doesn't work, try validating flash memory layout again, then do a "check if flash matches" operation, then click the disconnect button, then turn off the ignition. Then see if you can start the car.

If those two methods don't work, I think I can give you a test release with a code fix that may work. Normally after validating the memory layout, I do a quick checksum calculation to make the ECU happy, but I don't do that if validating the memory layout fails. So I should be able to give you a test release that will do the checksum calculation regardless of if validating the memory layout succeeds or not.

I have a test release that will hopefully fix this issue, with the car not starting after the Validate Memory Layout fails when RequestUpload is blocked by aftermarket software.

I got the vendor to reflash the ecu for free so all is good now.  thanks for all of your help and suggestions

I will do some more testing myself on the 4Z7 907 551 AA ECU to make sure this doesn't happen again. It is possible that the APR trial software is doing something extra to make the car not start.

I was told by the vendor the apr told him that this occasionally happens when the trial wears off and the car is cycled off and on to quickly before the ecu has a chance to boot into the proper flash after the trial.   Who knows?  i knew the trial wore off while i was driving and after i stop before i started it again i tried to validate the memory so i could save the original flash.  i didnt know that the apr was still there just dormant.  Live and learn i guess.

Its always in there unless you explicitly ask them to flash you back to stock.
Software doesn't magically disappear you know... :P

happened again this is the log file

I have the same fault code,  but mine will start and run, Problem is I have a check engine light on, and it won't pass emissions test until it is corrected.
I also have APR software, (as long as the previous owner told me the truth)

Tried to validate memory layout, failed, then this  DTC showed up.

2004 Golf GTI AWP - ECU #  06A 906 032 NK
 
Thanks in advance

Same thing happened to me a few days ago... so it looks like nefmoto still does something its not supposed to w/ these ecus

Demand APR to fix it?

is this a confirmed issue w/ only APR flashed ECU's?

Is there a way for me to ID the tune I pulled from the ECU as APR? as I'm not certain it was APR flashed.

This issue is not just with APR tunes.

This happens on 06A 906 032 NK stock ecu, and on 06A 906 032 RN.  Both are 04's.  It flashes fine with MPPS, then it seems any kind of programming session and it trips this fault?

Doesn't seem to be specific to the hardware, but the software.  If I load 06A 906 032 LP file all is good, load either of the others with Nefmoto it trips the code.  It can be cleared and the car will start then but after an ignition cycle it comes back.

Did anyone have input on what needs to change in the eeprom to remove this flag?

this a known issue with this software threw obd2... Ive found that with blind read it avoids this all together...or change software versions to fix the issue

sorry to revive an old thread but it seems the best place for this question.

i have purchased a complete AWP engine from a wrecked jetta, and i was told the ECU "might have a tune".  based on what i've read here, i'm nervous about trying to read from this ECU lest i brick it.  so i have 2 questions:

-is there any low risk way to determine whether the ECU has software that is susceptible to this issue?

-if this ECU does have an APR tune, and i do brick it by attempting to validate the memory layout, can i repair it by uploading the eeprom (which i've already backed up) or would i also need to upload the flash memory (thereby overwriting any tuned maps on the ECU)?

thanks!!

Backup everything in boot mode. compare what you read to a stock file to determine if it's stock. Just avoid the risk doing it over OBD altogether. Mostly because of the tune, but in general it's the safest method.