Notices
ECU Flash

Flashed to 9417 v7 now car won't start

Thread Tools
 
Search this Thread
 
Old Feb 6, 2010, 06:37 PM
  #1  
Evolved Member
Thread Starter
iTrader: (18)
 
Jorge T's Avatar
 
Join Date: May 2004
Location: Houston, TX
Posts: 1,494
Likes: 0
Received 1 Like on 1 Post
Flashed to 9417 v7 now car won't start

Checked imo, flashed back to 94170008 gave me an error, tried several attemps and it flashed, but car would not start.

Flashed to my stock rom and still car wont start. what could of fried? Is there a trick to get it back? HELP!?

I've tried so far charging battery and leaving ecu off for 15 min. Then reflashed stock rom, No start.

Tried disabling Immobilizer with perifery. No start.

Even rolled back from ecuflash 1.42 to 1.41
image compare says their identical

I'm at a loss on what to do next.
Old Feb 6, 2010, 08:16 PM
  #2  
Evolved Member
Thread Starter
iTrader: (18)
 
Jorge T's Avatar
 
Join Date: May 2004
Location: Houston, TX
Posts: 1,494
Likes: 0
Received 1 Like on 1 Post
could the ecu be fried?
Old Feb 6, 2010, 08:29 PM
  #3  
EvoM Guru
iTrader: (6)
 
tephra's Avatar
 
Join Date: Feb 2007
Location: Melbourne, Australia
Posts: 9,486
Received 66 Likes on 42 Posts
valet mode???

stock ROM - check ure immob..
Old Feb 6, 2010, 08:48 PM
  #4  
Evolved Member
Thread Starter
iTrader: (18)
 
Jorge T's Avatar
 
Join Date: May 2004
Location: Houston, TX
Posts: 1,494
Likes: 0
Received 1 Like on 1 Post
I'm back to stock rom with my immo code and still wont start. I'm leaving ecu unpowered overnight and I will reflash in the Morning.

It's like there is no spark
Old Feb 6, 2010, 08:50 PM
  #5  
EvoM Guru
iTrader: (6)
 
tephra's Avatar
 
Join Date: Feb 2007
Location: Melbourne, Australia
Posts: 9,486
Received 66 Likes on 42 Posts
well I can't how a flash could break anything...

maybe try disabling the immobiliser code as well...
Old Feb 6, 2010, 09:46 PM
  #6  
Evolved Member
Thread Starter
iTrader: (18)
 
Jorge T's Avatar
 
Join Date: May 2004
Location: Houston, TX
Posts: 1,494
Likes: 0
Received 1 Like on 1 Post
I can't figure out why either. when I reflashed back the first time to 94170008 it stopped mid way stating that there was a problem and to try again. I had to boost up the battery to get it to complete the burn. After that it would not start again. The engine was warm, temp in the 50s and in a garage.

which is the correct way of disabling the immo?
Old Feb 6, 2010, 09:50 PM
  #7  
Evolved Member
iTrader: (2)
 
logic's Avatar
 
Join Date: Apr 2003
Location: Berkeley, CA
Posts: 1,022
Likes: 0
Received 5 Likes on 4 Posts
Edit: reading comprehension owns me, nevermind, you already tried that.
Old Feb 6, 2010, 09:53 PM
  #8  
Evolved Member
iTrader: (6)
 
mt057's Avatar
 
Join Date: Apr 2007
Location: DFW
Posts: 1,529
Received 12 Likes on 11 Posts
What does it say when you attempt to flash? Can it hook up? Is it telling you that the new flash was sucessful?
Old Feb 6, 2010, 10:02 PM
  #9  
Evolved Member
Thread Starter
iTrader: (18)
 
Jorge T's Avatar
 
Join Date: May 2004
Location: Houston, TX
Posts: 1,494
Likes: 0
Received 1 Like on 1 Post
what's baffling is that it says flash completed succesfull.

It won't start with 3 roms i've tried all with my immo code.

I have not tried reading the rom to see if it give any error.
Old Feb 7, 2010, 08:13 AM
  #10  
Evolved Member
Thread Starter
iTrader: (18)
 
Jorge T's Avatar
 
Join Date: May 2004
Location: Houston, TX
Posts: 1,494
Likes: 0
Received 1 Like on 1 Post
Tried again this morning. did 2 flashes first one with stock rom. (did not try to start) completed correct. Then proceded to flash my tune on a new base rom And it gave me an error before completing.

Crap is this a bad ecu?

10:02:53.046] written in 46 pulse(s)
[10:02:53.046] kernel blank flash page: addr: 00006000
[10:02:53.062] erased in 2 pulse(s)
[10:02:53.062] kernel write flash buffer addr: 00006000 len: 00000200
[10:02:53.156] kernel write flash buffer addr: 00006200 len: 00000200
[10:02:53.234] kernel write flash buffer addr: 00006400 len: 00000200
[10:02:53.328] kernel write flash buffer addr: 00006600 len: 00000200
[10:02:53.421] kernel write flash buffer addr: 00006800 len: 00000200
[10:02:53.515] kernel write flash buffer addr: 00006A00 len: 00000200
[10:02:53.609] kernel write flash buffer addr: 00006C00 len: 00000200
[10:02:53.703] kernel write flash buffer addr: 00006E00 len: 00000200
[10:02:53.796] kernel commit flash addr: 00006000 len: 00001000 crc32 8bc774b0
[10:02:54.156] written in 44 pulse(s)
[10:02:54.156] kernel blank flash page: addr: 00004000
[10:02:54.171] erased in 2 pulse(s)
[10:02:54.171] kernel write flash buffer addr: 00004000 len: 00000200
[10:02:54.250] kernel write flash buffer addr: 00004200 len: 00000200
[10:02:54.343] kernel write flash buffer addr: 00004400 len: 00000200
[10:02:54.437] kernel write flash buffer addr: 00004600 len: 00000200
[10:02:54.531] kernel write flash buffer addr: 00004800 len: 00000200
[10:02:54.625] kernel write flash buffer addr: 00004A00 len: 00000200
[10:02:54.718] kernel write flash buffer addr: 00004C00 len: 00000200
[10:02:54.812] kernel write flash buffer addr: 00004E00 len: 00000200
[10:02:54.906] kernel commit flash addr: 00004000 len: 00001000 crc32 6999640c
[10:02:55.250] written in 44 pulse(s)
[10:02:55.250] kernel blank flash page: addr: 00003000
[10:02:55.265] erased in 2 pulse(s)
[10:02:55.265] kernel write flash buffer addr: 00003000 len: 00000200
[10:02:55.359] readback mismatch
[10:02:55.359] reading kernel comm stats
[10:02:55.375] readback mismatch
[10:02:55.375] kernel write flash buffer addr: 00003000 len: 00000200
[10:02:55.468] readback mismatch
[10:02:55.468] reading kernel comm stats
[10:02:55.468] readback mismatch
[10:02:55.468] kernel write flash buffer addr: 00003000 len: 00000200
[10:02:55.546] readback mismatch
[10:02:55.546] reading kernel comm stats
[10:02:55.562] readback mismatch
[10:02:55.562] kernel write flash buffer addr: 00003000 len: 00000200
[10:02:55.640] readback mismatch
[10:02:55.640] reading kernel comm stats
[10:02:55.640] readback mismatch
[10:02:55.640] kernel write flash buffer addr: 00003000 len: 00000200
[10:02:55.734] readback mismatch
[10:02:55.734] reading kernel comm stats
[10:02:55.734] readback mismatch
[10:02:55.734] kernel write flash buffer addr: 00003000 len: 00000200
[10:02:55.828] readback mismatch
[10:02:55.828] reading kernel comm stats
[10:02:55.828] readback mismatch
[10:02:55.828] failure in flashing block
[10:02:55.828] kernel flash disable
[10:02:55.828] readback mismatch
[10:02:55.828] interface close
Old Feb 7, 2010, 08:35 AM
  #11  
Evolved Member
iTrader: (6)
 
mt057's Avatar
 
Join Date: Apr 2007
Location: DFW
Posts: 1,529
Received 12 Likes on 11 Posts
I would back up any roms or patches you want to save on to a usb mem drive and delete all old ecuflash files and start from scratch and see if that helps. This is a weird one. I have not been able to interface before because of loose wires at the plug... but you are interfacing.
Old Feb 7, 2010, 09:07 AM
  #12  
Evolved Member
Thread Starter
iTrader: (18)
 
Jorge T's Avatar
 
Join Date: May 2004
Location: Houston, TX
Posts: 1,494
Likes: 0
Received 1 Like on 1 Post
I just reflashed to a stock rom (just changed my injector settings) to see if I got a start but did not start.

What i did notice is that everytime i try to add my tune it gives the readback mismatch error at the same address location. It looks like its corrupted. when I go back to the stock it has no changes to do in that address but stays corrupted. Is this possible?

I'm dreading spending for a new ecu, but if its fried its fried, but I hate to buy one and thats not it.

Last edited by Jorge T; Feb 7, 2010 at 09:09 AM.
Old Feb 7, 2010, 09:50 AM
  #13  
Evolved Member
Thread Starter
iTrader: (18)
 
Jorge T's Avatar
 
Join Date: May 2004
Location: Houston, TX
Posts: 1,494
Likes: 0
Received 1 Like on 1 Post
To try my ecu in another evo I just change my immo to his correct?
Old Feb 7, 2010, 10:15 AM
  #14  
Evolved Member
iTrader: (3)
 
Jim in Tucson's Avatar
 
Join Date: Oct 2006
Location: Tucson, Arizona, USA
Posts: 1,480
Likes: 0
Received 1 Like on 1 Post
Have you tried an original unmolested pure stock ROM, changing only the immobilizer code - changing nothing else?

Your EVO should start and run just fine off-boost on a stock ROM. Going back to OEM at least eliminates extraneous matter.

Of course, your Otto cycle engine still requires fuel, air, compression, and spark. We assume none of those are compromised, correct?

Old Feb 7, 2010, 10:45 AM
  #15  
Evolved Member
Thread Starter
iTrader: (18)
 
Jorge T's Avatar
 
Join Date: May 2004
Location: Houston, TX
Posts: 1,494
Likes: 0
Received 1 Like on 1 Post
Car was running fine until the flash episode to 9417 v7 then the error (same as post #10) going back to 94170008. I had just returned from a drive and then instead of loading my flash I loaded the V7 I was building by mistake. After the flash finished I proceded to reflash to my tune 008 rom...then the nightmare began.

Tried an unmolested rom with my immo code only- No Start

what else could of gone wrong in that reflash? could it be something stupid like a fuse?
Could my sparktech Non CDI go bad.


Quick Reply: Flashed to 9417 v7 now car won't start



All times are GMT -7. The time now is 03:26 AM.