NefMoto

I tried to flash using nefmoto via obd in my 2001 allroad. I had already put an M box file on the ecu and been driving with this ecu. The tune was a little too aggressive for my clutch so I wanted to return it to stock until my funds could supprt a clutch swap. Nefmoto got 27% through then stopped. Typical Allroad ecu fun right? No reconnection could be made via vagcom or nefmoto. The check engine light did not even illuminate. Great, ecu bricked....

Well I pulled the ecu and tried to connect Via galletto and reflash via boto mode. Could get the ecu into boot mode and when trying to look at ecu data, It says "erro ecu data" Makes sense since it failed during programming. I try to write a different file to the ecu via boot mode. It goes through the steps, says erasing goes ok and begins writing. The progress bar at the bottom never shows a change from 0%. It waits 30-45seconds and states " Writing failed". Anyone have some insight? I have to write the same file again in boot mode? Or can it be any other file? Maybe thats my issue? Thanks for the help. 

Tried a second computer and galletto cable. Still no write. Each time, the program says it erases, but cannot write. I have checked my hardware variables. Power supply from a good battery at 12.6V. The exact same bench setup was able to flash the L box A6 ecu I picked up as a spare. Went right through via nefmoto. Not sure where to go from here...

Is it possible the chip now needs replacing? Too far gone to start over? Does anyone with a good hot air setup want the task of swapping the chip for me? Willing to pay. I want to use this as my primary ecu. Thanks all.

Send it over, I'll rejuvinate it as long as you didn't short the bootpin with any others and cause real damage. I have a hotair, and a chip burner.

Just cover the shipping to and from, no charge :)

PM me for an address.

I had similar issue some months ago, the only thing that works was desolder and write the flash, and solder it back...

How nice is that, bravo!

Thank you sir. PM sent.

It'll go back out to you tomorrow.

Didn't know what you wanted on it, and it was bricked so I couldn't check the softcoding, so I just put an M-box on it. Flash over it when it arrives.

Thanks very much. Big help.

In my experience galletto is VERY VERY picky. I had luck (believe it or not) programming after keeping boot pin shortened for several seconds into programming started, according to galletto. If programming craps out, unplug from power for full two minutes, try again. I usually ignore instructions that say to keep somethign off-power for x amount of seconds but with our ECUs it is actually required!

I noticed that so long the galletto flashes first 8% successfully, you can then hook it up to normal nefomoto cable and ECU will be alive.

With my A8 ECU ME7.1.1 I had the same issues with a write fail.

I tried and tried and tired with galleto using boot mode.

I finally gave up and unplugged everything overnight.

Tried again the next morning and it went flawlessly.

I've done this twice now with the same experience and two different ECU's

It's almost like a security feature and that it has to sit for so long..??

I also noticed that as soon as I power on the ECU for me grounding pin 24 for about 10 seconds and immediately initiating a galleto write works the best.

For some reason these ecu's seem really picky

I didn't have very good luck flashing over the OBD route my first time. I followed julexs' advice and left the ECU powered down for a full 2 minutes and removed the K-line fuse. I eventually got it to complete 100% after a couple attempts.

I also requested my Nefmoto licence today - having the premium services enabled with shave your 2 min flash times down to under 30 seconds giving it less time or opportunities to error.

Since then, I've only flashed on the bench. With the help of another forum member gathering parts - I built a proper bench flash harness on Friday. So much easier and less worry with getting it out of the car and on the bench. I have never had a flash fail on the bench.

I have to add that my Allroad (Euro 6mt) is the same.  After 1 or 2 attempts at flashing it appears to be bricked.  I disconnect battery for 10 minutes and leave car for an hour after.  Then it normally responds ok.

I shat my pants first time it happened as my ECU looks different to all the pictures (pic below) I have found relating to boot mode so was dreading the thought of trying to find the pins and earth points.

I have read somewhere that the ODB k-line can have issues on these early cars and my vagcom does drop connection every now and again which I am guessing might be linked to the flashing issues?  I am going to run a separate k-line direct from the ecu to another OBD plug just for flashing.

I am slowly getting there.  Just managed to replace a turbo with the engine still in, but never again!  Luckily the next time will be engine out with some K04's  :-)

I just need to find someone who I can pay to create a definition file for my early ECU ( 4Z7907551B) as I am having too many issues using M-box and would rather tinker with the proper file if possible.

Happy motoring!