Ecutek Corrupt ECU, Bad Flash, Can i reset?

[Deadspool]

Originally Posted by Lonewolf

Too bad he as well as other tuners who might have been able to help have been booted again...

Thats odd.

[xjohnx]

My money is on a bad pin in the harness. Seems to be a somewhat common occurrence. Wish someone would write a DIY on fixing it.

[Danklvr]

Originally Posted by jamesm

weird on the backorder thing... a local bricked his and just picked up a new ecu at the dealer for like $600 iirc.. had it in stock

i guess some dealers have em and some dont. my dealership doesnt do a lot of scion business or stock scion parts. personally i think the backorder story is dealer speak for "its gonna be about a month before we can have your ecu tested to find out what you did to it so we dont have to cover under warranty"...

[Danklvr]

@ Skullworks - is that ecu software proprietary or freeware?

[Shiv@Openflash]

Originally Posted by SkullWorks

I recovered my Bricked ECU with ECUflash software,

It wouldn't recognize with anything at the time of the bricking either.

Do you have a tactrix OP2.0 cable or access to one?

If your ecu was bricked, by definition, it wouldn't be recoverable. What you probably had was a cal ID mismatch that prevented the initial communication. I'm the case of actual bricked ecus, you wouldn't even be able to achieve comms. This could be due to corrupt boot loader. In that case, the only solution would be to reprogram the micro on the board directly (not through obd).

Back on topic, the OP should definitely exhaust all possibilities (bent pin, bad cable, etc). One thing to try is to see if any other diagnostic tool can communicate with the ecu. A cheap $50 generic obd2 reader (from Pep Boys) would suffice. If that is able to read codes, things look good. If that won't communicate, and the pins on the obd2 plug look good, then things don't look so good

[Hawaiian]

I had. Bricked ecu from bad code a while back. Ecutek had me send them my ecu, and they fixed it. It was about a 10 day turnaround, but way cheaper than a new ecu. I also wrote a DIY in the DIY thread.

[steve99]

Originally Posted by Danklvr

@ Skullworks - is that ecu software proprietary or freeware?

The Ecuflash software is free to download although you will need to get the BRZ Beta version, however you will need a Tactrix dongle to be able to communicate with the ECU

http://www.tactrix.com/

see post for BETA version download
http://www.ft86club.com/forums/showp...&postcount=307

http://www.tactrix.com/downloads/ecu...ta_1444040.exe


Might also want to look here

http://www.romraider.com/forum/viewt...=brz&start=330

appears newer beta version released, its a work in progress

[gdrider77]

Originally Posted by shiv@vishnu

If your ecu was bricked, by definition, it wouldn't be recoverable. What you probably had was a cal ID mismatch that prevented the initial communication. I'm the case of actual bricked ecus, you wouldn't even be able to achieve comms. This could be due to corrupt boot loader. In that case, the only solution would be to reprogram the micro on the board directly (not through obd).

Back on topic, the OP should definitely exhaust all possibilities (bent pin, bad cable, etc). One thing to try is to see if any other diagnostic tool can communicate with the ecu. A cheap $50 generic obd2 reader (from Pep Boys) would suffice. If that is able to read codes, things look good. If that won't communicate, and the pins on the obd2 plug look good, then things don't look so good

Well. As I said the elm Bluetooth that I used with torque won't communicate at all, same issue won't connect to ecu. I am going to get under the dash and check very closely all the pins and make sure they all look good. Will look at that tomorrow.

I have been told by a couple tuners that ecutek has the capabilities to recover a bricked ecu, so hoping they will get back to me in the next few days with instructions on that.

Also, why was Visconti banned again? He has been super helpful for me?

[xjohnx]

Originally Posted by gdrider77

Well. As I said the elm Bluetooth that I used with torque won't communicate at all, same issue won't connect to ecu. I am going to get under the dash and check very closely all the pins and make sure they all look good. Will look at that tomorrow.

I have been told by a couple tuners that ecutek has the capabilities to recover a bricked ecu, so hoping they will get back to me in the next few days with instructions on that.

Also, why was Visconti banned again? He has been super helpful for me?

This happened to me once, try this to confirm or rule out a loose pin in the obd2 port

Plug in your EcuTek cable to the OBD2 port and with one or two fingers behind your Ecutek cable, apply light pressure pulling it towards you, hold it in that position while you try to "Detect vehicle" from the ecutek software. If that doesn't work, put light pressure on the EcuTek cable in the opposite direction (push vs pull) and try to detect vehicle again.

I've also found that with the cable disconnected, if you pushing the metal tab on the ecutek cable inboard so that it bends slightly inboard, the cable will lock more firmly into the OBD2 port.

[kster1]

@gdrider77


Just curious, did this get resolved? Any updates? Thanks.

[gdrider77]

Originally Posted by kster1

@gdrider77


Just curious, did this get resolved? Any updates? Thanks.

Nope, nothing yet. Dead ECU , dead car.

Last attempt was a reboot that Paul from @AVOturboworld sent me. Suggestion from @EcuTek, but no luck.

I am hoping that Paul has followed up with @EcuTek on it, and we are waiting. Not really sure on the status, but trying to be patient, as @EcuTek is overseas, so turnaround time might be slow, plus not sure if they are on vacation and what not. I was hoping they would have at least said something in this post, but appears they dont check the forums too regularly.

Will definitely keep everyone updated on it. Even if i have to pull the ecu and send to @EcuTek, that fine with me, just want some direction at this point.

[FA20Club.com]

sent you an email.

[stugray]

I saw a thread on here recently where someone unbricked their ECU themselves but you need some electrical skills.

It required a power supply, a circuit board (or arbitrary function generator) to stroke the watchdog, and some wires soldered onto the ECU to a serial cable.

Or you could send in the ECU and they would fix it for a fee ( I think it was a thread on Romraider)

[gdrider77]

For those that are wondering. I was able to get my ECU fixed via remote recovery from @EcuTek. They got in there and were able to get it fixed.

I am awaiting their response on why it happened. Just a FYI. I will update this more once i hear back from them.