NefMoto

I have an 03 allroad 2.7T 6mt (WIN!) that is stock (other than a K+N and a muffler delete). I wanted to get in and start getting used to the software before messing with any settings and get a copy of the stock .bin for my car. I have experience with subaru/tactrix and haven't had this issue out of them. When I first tried a full flash read in nefmoto, the baud rate set it self to the highest setting after slow init with the ecu. The full read flash failed after %6 and nefmoto told me that it had an issue. I read that the ECU doesn't like communicating above 52800 and so I set that and got a successful full flash read. I am now un-able to start my car (and I'm in the wife's spot in the garage). I've tried to flash the bin back to the car (nefmoto says it's successful after about 5min), and I've also run the .bin file through the ME7Sum/check (awesomesauce right there) and they clear it for launch. The write is successful (according to nefmoto) but I still can't get the car to turn over (it cranks). Didn't have any major problems (tracking down a boost leak problem before I start tuning this thing)

Help... I didn't realize that a READ would innop my car!@#?! (Oh, I assumed ECU is stock as the bolts in the ECU clamshell hadn't been touched) I'm sure it's me doing something wrong

http://nefariousmotorsports.com/forum/index.php?action=printpage;topic=4847.0

DD says write the file back, disconnect, turn the key off for ten seconds, turn the key on for 30 seconds without starting, then try.

Otherwise, the EEPROM will need flashed I think.

http://nefariousmotorsports.com/forum/index.php?action=printpage;topic=1542.0

That, too.  Sometimes shorting the terminals of the battery together (disconnected from the battery, obviously), for a while and then attempting to reconnect will help.

http://nefariousmotorsports.com/forum/index.php?topic=981.0title=

Will fix you right up. In summary, write the 551R binary to fix it, or just do a quick patch to yours, fix the checksums, and flash it back. It will clear the error code on it's own after that.

Failing that, you can clear the eeprom.

HA! so now NM flasher won't even connect with my ecu (worked fine yesterday) I've also noticed that it won't even show same baud rates as yesterday. I gotta at least get my AR back on the road :(

Tripple checked that FTDI drivers are loaded (deleted them, used the program they have on the site to re-install it) re-installed NM flasher.. still fails to slow init on any of the three baud rates.

Disconnect your battery for 10 minutes.

Wish I had someone local to fort collins, I could have avoided this whole mess if I would have asked more questions. It seems that I have bricked my ecu all together trying to load other "Stock" .bin files into it. All of the talk I kept seeing about being able to use other 2.7T .bin files in different ECU platforms... anyway... as soon as I can get this thing recovered and back on the road (Horrible timing of this... I have a job interview tomorrow) I will create a comprehensive youtube video from fresh no drivers computer to completed a good flash (so long as that 551R .bin you guys gave me gets this thing running again... I have faith :D )

I think I could do a fairly decent job of walking noobs through the setup/read/write process. I had an idea for you guys... that community stage 1 you guys were building for the 2.7T (and others) Build one, and sell it as a package deal. With the STI, you could get a tactrix cable for $120, and a safe stage 1 for $100... If there could be some fail safe's built into NM flasher for stuff like this (determine the car and the quirks about it) Hell... I'd pay $200 to be able to load a stage 1 into my own car and adjust for stuff... Just a thought. (XPT has a really crappy website... but his tune is on point... lots of people use that over COBB stuff)

I think the problem here is that you've panicked and started flashing files randomly, and now you've bricked it.  Disconnect the battery for 10 minutes and attempt to connect with VCDS, Nef, whatever.  Does it connect?  Can you see the ECU with Vag-com?  Obviously the ignition has to be on.

If you can't connect to it, it should be assumed it needs to be bootmoded.  It's not hard, and if you follow the steps slowly, you'll get it done.  Don't rush.

Borrow the wife's car tomorrow, and forget about this whole business until your interview is finished.  Don't rush, cars can be fixed at any time.  And as something as trivial as this, one of the helpful users in the States would likely help bootmode it for you if you ship them the ECU for a few beer tokens.  Don't go PM'ing them all until they offer, they get enough requests.

Get your interview sorted first man, then deal with this.  Good luck with the job! (y)

I will fix it for you if you can't sort it. No charge. PM me if you choose to do so.

Yeah... Pretty much. I pulled a .bin for a different ECU (551N I believe?), did a sumcheck and you're right... bricked it :D

I have a non-immo stage 1 on order through a guy that I used to get EFI tuning instruction from. Going to have him clear this one, tune it for stage 1, and send me another OEM flash (so I can break/toy with the stage 1 until I have become comfortable with the galletto 1260) I do thank everyone for their help. Maybe a couple of weeks before I get a NOOB video up on dropbox and have the masterminds go over it. It will not contain tuning, but just the steps needed to cover how to use the software, what steps should taken to prevent something like this in the future.

Thanks again (And hell yes I'll donate beer to the community... always looking for local people to hang out with)

I have videos posted how to's if you need help with boot mode

I never have patience for howto videos. You can't browse them, or fast forward, or slow down.

Applauded once again! <3

I even made a how to: nefmoto

That did help quite a bit actually. But I feel that there was a lot missing from the video. How to doublecheck that the FTDI drivers were actually being used for the cable. Changing the baud rate (my allroad likes to automatically jump to the highest one available when you first connect, and then I have to make sure it gets dropped to the next lowest level in order for it to remain connected during read or write operations. I also think that the memory mapping should be put in there so people know which memory map pertains to their vehicle. Just simple stuff that can be considered common knowledge by expert users like your self. The more comprehensive the video is,  the less likely new users are going to continue asking stupid questions like me.

Unfortunately this is an app bug that affects all ECUs, that I can tell :(

I truly wish the source were available.

Mad props to ddillenger. He hooked me up big time. I have to figure out all the crazy codes my allroad is throwing now, but it's mobile (makes the wife happy I'm not taking up the entire garage). Guess it's a good thing I kept my airbag reset box :D

Once I figure out the overboost issue (Betting that it's the wastegates) I'll hit him up for a stage 2, and a spare stock ecu setup :D


Thanks to everyone who replied. Still waiting to hear back on that job interview :D

You guys should just tell people if they have an allroad... don't bother with this software... another no start condition (I'll I've been trying to do from the get go is log the damn thing to determine why it's acting stupid underboost). Wouldn't log using the .bin files I've tried to use... tried another read as a last result... car won't start... I've gotten MORE info out of Torque Pro than nefmoto. I will sell this as soon as I can source another ecu.

That S file is relatively rare:

http://files.s4wiki.com/stock/part-numbers.txt

Flash over it with a non bugged version and you're fine.


You shouldn't be doing ANY tuning without a galletto and bench harness or a spare ECU in case you brick.


Nefmoto is, foremost, a flashing tool, not a logging tool.

You should be using ME7L for logging.

You can write the 4Z7907551R file to the ecu, start or not, and have a running car.

And see... I didn't know that till I just tried :D Thanks much ddillenger... again... sorry for getting salty. (Febuary I'll be looking to get a stage 2 tune from you as well as get my LCD repaired)

No problemo. Check the coding on that ecu I sent. It could be setup for an A6, I don't know. I just immo off'd it and shipped it as I didn't recall what car you had!

So that explains why it was wigging the hell out when I got past 4 psi of boost :D Positive manifold pressure.