NefMoto

Good day all. I have been using 518 ak software in my 05 a4 MT Q. Went to flash recently, messed up my connection, and bricked the ECU. Through multiple failed attempts to get bootmode, I gave up and picked up another ECU. Can't seem to get that one in to boot mode either, to flash immo bin. So.. I'm hoping to use vcds method to satisfy immo on the al.
But, don't have a pin for either.

Any suggestions?
I'll attach original bin.

pin stored in the eeprom

ok... I'm unable to access either computer though obd...
The original computer, (one I recently locked up) when attempting to activate bootmode, doesn't respond. Also, ABS light luminates, when batt is connected,  along with the yield circle and the other normal one, beside it. Can't recall which one that is atm.

The new ecu, seems to get in to boot mode, or programmable mode, but immo won't allow data access, read or write...

Any suggestions on accessing the eeprom.. or any ideas that may move things forward...?
Thank you very much for your response btw!

Another detail, it seems the new ECU my be entering boot mode, but when I load the 515kb immo file to nefmoto read/write application.
The "choose flash file" window turns yellow... not sure why.
As a result, can't flash the immo bin to the ecu...
Any idea how to make application accept the 512k immo bin?

eeprom is 512b not 512k
and not flashable by nefmoto software

read forum before do something weird

Correct. Original ecu is 518bc. I installed 518ak software due to the availability of 518ak xdf's.
I have decided to try to aquire the fob matching the ecu..

He means the eeprom size is 512 BYTES not 512 KILOBYTES :)

To get into bootmode I find these 518xx ECUs like a bit more time grounding pin 24. Seven seconds works every time for me, whereas my Jetta ECU was anywhere from 3-5 seconds. Try giving it a couple seconds longer and see if that works.

Are you doing this in car? I have never had luck pulling the e2p through the OBD port (although that just could be my Audi). I had to do it on the bench to make it work...

I have been trying in car, I had read somewhere that ten seconds was sometimes needed. Hadn't tried seven.
I'm away from the car for a while now.
I'll try seven seconds as soon as I get back to the car.
Do you recall, was your abs light on while attempting to activate bootmode?
Thank you all for your input once again!

Sorry I never tried in car. I couldn't even read the eeprom in car. I pulled the ECU and hooked it up to my bench rig.

I needed to write the copied eeprom to my Ebay ECU so I had my bench rig ready to go anyhow. It was far simpler doing it that way. I wouldn't consider doing it in car TBH. I've got long arms but switching the ignition on while grounding the boot pin doesn't sound like fun at all.

Lol, I leave tglhe key in "on" position, then ground 2nd terminal on chip while connecting ground terminal at battery.
I had a look at the bench flashing harness. That does seem like a better way to go.
The K-line is the data transfer line I'm assuming..?
If so... which usb pin out would be the correct one to wire to k-line..?

K-line is pin 7 on the OBD connector. See this post by Matt Danger if you want a picture: http://nefariousmotorsports.com/forum/index.php?topic=417.msg2805#msg2805

You can make bootmode easy by using a seizer probe, momentary switch and alligator clip. Wire the seizer to the clip through the switch. Hook the seizer probe on pin 24 and clip the other end to the edge of the pcb. Hold momentary switch on, apply power via the bench rig, count off the seconds you want, then release switch and voila; bootmode. It how I roll at least. Never fails for me. First attempt every time...

Yeah, I probably should construct a little assembly like you have described... Honestly I've never had a problem getting boot mode either, until this most recent failed attempt. Other times (maybe 4x) have activated boot mode seamlessly...
From memory, does it seem normal that abs waning light in cluster is lit when car is powered up..?
I do recall rad fans kick in when power is applied, but ecu is bricked. Which my car is doing. But I feel like the abs light is not normally lit in this circumstance.
I'll try a few more boot attempts, going to check continuity across resistors on the ecu board, assemble a bench harness. If none of these methods will get me in to boot mode. Then I'll have to assume this ecu is shot...

Good day all.
Thank you each for your input. I have been doing further research and learning regarding eeprom changes and adaptions, starting to get a better understanding.
I made a mistake building my bench harness, and wrecked 2 ecu's as a result. The mistake was... I grounded pin 24 on the Harness pin-out. Not sure what pin number 24 on the harness controls, but ground it and your ecu will never be the same...lol.
Picked up another ecu, and nearly ready to turn off immo. ECU is same as my original, 8e0 909 518 bc.

Having wrecked 2 ecu's lately, I'm feeling pretty cautious.
My question is, once you have completed the bootmode/immo off process. (i plan to use turboat's tool) do you simply turn off the power supply, or command a disconnect first?

just turn it off after reading/writing operation complete

Good to know, and thanks for the reply!  :)

Another query..
I just noticed there is a 80e 909 518m
Would this ecu be considered an m-box, if so could I flash this bin to my 518bc (which is 518ak compatible)?
From what I understand, m-box ecu's do not utilize "immobilizer function".

Then flash the ecu with suitable bin for my car...
Any opinions on this strategy?

No that is not the 'm-box' referred to here which is the 551m ecu from a 2.7t. Totally different animal.

I think the 518m is from a 2002 A4 which is not cross-flashable to the 2003-05 ECUs. Different clock speed on the processor.

Different clock speed, and different boot up, according to another post.
Thanks for the reply on the matter!

Well, completely stock, untampered ecu, and I can't seem to access bootmode.
I think the ecu is going in to bootmode, but vcds cable seems unable to communicate with ecu in bootmode...
I have successfully flashed in bootmode in the past (in the car, through obd port) with this cable, but doesn't seem to work for boot mode anymore.
At least not with my bench harness.
Any suggestions or opinions?
Thanks

Could I....
Remove vcds drivers..?
Could this possibly force the vcds cable to go straight ftdi..?
Or am I grabbing at clouds here..?
:)

To anyone who may know... I sent awayfor, and in my lack of knowledge, received a  "KKL VAG-COM for 409.1" all blue cable.
Seems both vcds and nef do not want to utilize this cable. Windows 7 operating sys.
I bought a couple untampered ecu's, had attempted bootmode on one of them numerous times, with both genuine ross-tech cable, and the new blue kkl, using nefmoto, neither connected so I was unable to verify whether I was in boot or not.
Then restart ecu and make sure vcds can still read ecu, and it can.

If I did enter bootmode, but was unable to access the ecu, did I wreck the existing tune..?
I tried to start the car after an eeprom chip transplant. No "safe" warning, but no check engine light either. Car did not start.
One tab on the eeprom chip broke, the connection may be questionable.

Thanks guys for any input, or suggestions.

If you are in bootmode, neither VCDS or Nef will connect. They do not work in bootmode. Only Galletto and ME7eeprom work in bootmode in my experience.

Getting out of bootmode is as easy as cycling the power to the ECU with the pin ungrounded. Your flash contents should still be there regardless of what you did to the eeprom as its a different chip altogether.

If you broke a leg off the eeprom chip then it is likely not going to work, but I'm a pilot not an electronics engineer so I could be wrong.

It's weird, because in the past, Had put the ecu in bootmode, on 2 or 3 separate occasions, in car, connected with rosstech cable over obd, and used nef moto to reflash while in boot mode...
It all seemed pretty straight forward, and went as it should according to what I read on the forum.

Now, I'm having a crazy difficult time getting in to bootmode, or if I am in bootmode, I'm unable to verify it, nor able to communicate with the ecu...
I read that my new cable may have been a poor choice.. The solid blue "KKL-VAG for 409.1"
I'm now just looking to find a place to have immo defeat performed... Unless someone has some suggestions..?