bluelancer20028

i can pull my rom with no problem but i can not put anything on ecu from ecuflash . ecuflash keeps giving like a error and i can hear the ecu click . so if anyone has any advice im open for suggestions.

bluelancer20028

[19:16:27.000] sending init sequence 1 (0003)
[19:16:28.031] got 0x05 response
[19:16:28.031] sending init sequence 2
[19:16:28.046] got 0x1B response
[19:16:28.046] sending init sequence 3
[19:16:28.421] entering bootloader
[19:16:28.437] sending kernel size (4420)
[19:16:28.453] sending kernel load address (0xFFFF7000)
[19:16:28.453] uploading kernel
[19:16:29.171] verifying kernel checksum response
[19:16:29.171] kernel valid
[19:16:29.390] kernel get version
[19:16:29.406] rkrv: preamble 1 error
[19:16:29.421] reading kernel comm buffer size
[19:16:29.625] reading kernel flash buffer size
[19:16:29.843] interface close


That is the log from ecuflash

senate6268

iTrader: (20)

What version of EcuFlash are you using? What is your ROM ID? If you can read your ROM then you should be able to flash your ROM as well.

03lances

iTrader: (14)

Not trying to insult you or anything but you have the cable with the bootstrap correct? I think there is one cable with just the obd plug for logging and the other with the white connector as well needed to flash.

bluelancer20028

i had the version before 1.42 and i have went to 1.42 as of this morning and i have the 1.3 cable with both connectors.

bluelancer20028

still having the same problem rom id is 86640007

03lances

iTrader: (14)

Does your rom you pull look fine in terms of numbers where they should be? or do they look jumbled?

ClixT

iTrader: (2)

EDIT: problem fixed

bluelancer20028

still having the same problem senate fixed it but still having reflash problem

ClixT

iTrader: (2)

maybe you have the same problem as i do.
make sure you have OEM ecu..

bluelancer20028

how would i find out??? what did you do?

ClixT

iTrader: (2)

well mines pretty straightforward.. i bought this flashed ecu and installed it..
then i realized that i have the flashed ecu, installed the oe one, then it worked.


edit: try this
maybe your ecu is locked..

senate6268

iTrader: (20)

Definitely worth a try. I'm pretty sure this is meant for ECUs that are locked due to licensing (EcuTek and other flashers do this).

Thinking back I just realized that I was getting this same error when trying to flash my Evo ECU for the first time. I downgraded to EcuFlash v1.29a and all was well. Might want to give that a try, as well.

bluelancer20028

anyway i can get v 1,29a?

ClixT

iTrader: (2)

from senate: https://www.evolutionm.net/forums/la...ster-list.html