Pages: [1] 2
Author Topic: Allroad won't start after full flash read  (Read 13983 times)
Gingerw00ki3
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 11


« on: October 26, 2015, 02:18:12 PM »

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
Logged
adam-
Hero Member
*****

Karma: +123/-33
Offline Offline

Posts: 2179


« Reply #1 on: October 26, 2015, 03:12:59 PM »

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.
Logged
adam-
Hero Member
*****

Karma: +123/-33
Offline Offline

Posts: 2179


« Reply #2 on: October 26, 2015, 03:15:13 PM »

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.
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #3 on: October 26, 2015, 04:08:40 PM »

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.
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
Gingerw00ki3
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 11


« Reply #4 on: October 27, 2015, 04:55:41 PM »

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 Sad

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.
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #5 on: October 27, 2015, 05:02:19 PM »

Disconnect your battery for 10 minutes.
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
Gingerw00ki3
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 11


« Reply #6 on: October 28, 2015, 06:14:10 AM »

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 Cheesy )

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)

Logged
adam-
Hero Member
*****

Karma: +123/-33
Offline Offline

Posts: 2179


« Reply #7 on: October 28, 2015, 06:30:18 AM »

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)
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #8 on: October 28, 2015, 07:35:08 AM »

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

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
Gingerw00ki3
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 11


« Reply #9 on: October 28, 2015, 03:02:35 PM »

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)

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

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)
Logged
_nameless
Hero Member
*****

Karma: +342/-466
Offline Offline

Posts: 2800



« Reply #10 on: October 28, 2015, 04:12:02 PM »

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

Giving your mom a tuneup
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Offline Offline

Posts: 12268


WWW
« Reply #11 on: October 28, 2015, 06:58:59 PM »

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

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
adam-
Hero Member
*****

Karma: +123/-33
Offline Offline

Posts: 2179


« Reply #12 on: October 29, 2015, 12:54:36 AM »

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

Applauded once again! <3
Logged
_nameless
Hero Member
*****

Karma: +342/-466
Offline Offline

Posts: 2800



« Reply #13 on: October 29, 2015, 06:15:51 AM »

I even made a how to: nefmoto
Logged

Giving your mom a tuneup
Gingerw00ki3
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 11


« Reply #14 on: October 29, 2015, 12:10:40 PM »

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.
Logged
Pages: [1] 2
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.023 seconds with 17 queries. (Pretty URLs adds 0.001s, 0q)