jhkoka
Newbie
Karma: +0/-0
 Offline
Posts: 2
|
 |
« on: April 10, 2016, 11:17:59 PM »
|
|
|
I accidentally flashed B6 soft to my B5 1.8t Audi. So that done, obviously the car won't start and I have to reflash it with my original software.
I have read absolutely all topics in the entire internet about reflashing and bootmode and beching etc. etc. But nothing works.
Could it be, that wrong software completely burned the ECU and thats garbage now?
1) I have a brand new Galletto 1260 cable (60 eur), installed it with correct driver (showd up as USB device, not COM port, so no VCP corruptions). Installed it on a freshly installed brand new Windows XP.
2) Done the correct boot mode procedure - power off, 29F800BB pin 24 shorted to ground and then power on and released the ground. I've tried it on bench, with nice 13V power and on a car, with 1 week old brand new charged battery. Thried with 1k resistor, 2K resistor and without any resistor.
3) ECU is from 2000 year Audi 1.8t AEB 110kw. ECU nr: 4B0906018CG. CPU is labelled Infineo and as well SIEMENS.
And the problem is that it's impossible to establish any connection with the ECU. VCDS can't see ECU. Nefmoto software with KKL "Dumb" blue cable can't connect in normal mode nor in boot mode. Galletto 1260 can't connect in boot mode "BOOTMODE INACTIVE".
Just in case for information: this particular ECU and my cluster came with immo3 originally, but I had disabled it back then with eeprom flashing (95040 nefmoto software). Done this in bootmode and then it worked like a charm.
I feel like I tried everything I can. Is it really, that wrong flash kills the ECU completely and can't be recovered even with the best of devices?
|
|
|
|
|
Logged
|
|
|
|
|
adam-
|
|
« Reply #1 on: April 11, 2016, 12:11:11 AM »
|
|
|
Powered Pin 121?
|
|
|
|
|
Logged
|
|
|
|
jhkoka
Newbie
Karma: +0/-0
Offline
Posts: 2
|
|
« Reply #2 on: April 11, 2016, 12:36:00 AM »
|
|
|
You mean pin 121 on ECU? No I haven't powered it, because of schemes I found. Like this:  I will give it a try. Atleast something new, that I haven't tried yet. Thank you for the advice! |
|
|
|
|
Logged
|
|
|
|
|
nubcake
|
|
« Reply #3 on: April 11, 2016, 01:41:14 AM »
|
|
|
I was never able to get Galletto to communicate with ECU in boot mode. Ended up using MPPS for that.
Just my 2 cents.
|
|
|
|
|
Logged
|
|
|
|
|
Snow Trooper
|
|
« Reply #4 on: April 11, 2016, 08:24:16 PM »
|
|
|
When the wrong version is put on to these it is new chip time. Btdt
|
|
|
|
|
Logged
|
cartoons?
6A 61 72 65 64 40 76 6C 6D 73 70 65 63
|
|
|
|
dream3R
|
|
« Reply #5 on: April 11, 2016, 11:48:21 PM »
|
|
|
try 220ohm resistor
|
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #6 on: April 12, 2016, 02:12:50 AM »
|
|
|
When the wrong version is put on to these it is new chip time. Btdt
You can always boot mode it. You can boot mode it without a chip even soldered to the board, it is irrelevant what is on the chip. |
|
|
|
|
Logged
|
|
|
|
|
Snow Trooper
|
|
« Reply #7 on: April 12, 2016, 12:31:28 PM »
|
|
|
Odd, I have had a b6 file flashed to a b5 ecu, also a me7.1 2.7t file flashed to a bel 2.7t me7.1.1 ecu and an old b6 file flashed onto a newer style b6 and they all were not recoverable. I definitely know how to use boot mode. Seem pretty bricked at that point. I say that because when these issues were encountered, I enlisted the help of the various people who support me and my business on the back end tech wise when it's something that has me stumped and they couldn't fix it either.
This poster has an ecu that won't respond to boot mode. What does PRJ think he is doing wrong and what does PRJ suggest he do to fix it? What causes these non smoked boards to no longer go into boot mode? Or where you just here to post that I was wrong? Thanks for your info.
|
|
|
|
|
Logged
|
cartoons?
6A 61 72 65 64 40 76 6C 6D 73 70 65 63
|
|
|
fknbrkn
Hero Member
Karma: +186/-24
Offline
Posts: 1455
mk4 1.8T AUM
|
|
« Reply #8 on: April 12, 2016, 04:44:58 PM »
|
|
|
i have 1.8t me7.5 ecu restored after someone flashed it with mp3 song
im also recovered ecus after flashing it with newer bootrom files
bad checksums, lolcode etc
i was tryed galletto clone for this, but no luck here.
chiploader + kkl-usb good for boot-mode but after that ecu should be flashed via kwp2000
|
|
|
|
|
Logged
|
|
|
|
|
vwaudiguy
|
|
« Reply #9 on: April 12, 2016, 04:57:21 PM »
|
|
|
someone flashed it with mp3 song
I'm totally trying this tonight. I'm going to try and fit it in somewhere in the unused space. |
|
|
|
|
Logged
|
"If you have a chinese turbo, that you are worried is going to blow up when you floor it, then LOL."
|
|
|
|
Snow Trooper
|
|
« Reply #10 on: April 12, 2016, 10:18:17 PM »
|
|
|
Lol, start filling dead space with cryptic audio messages
|
|
|
|
|
Logged
|
cartoons?
6A 61 72 65 64 40 76 6C 6D 73 70 65 63
|
|
|
|
prj
|
|
« Reply #11 on: April 13, 2016, 03:23:59 AM »
|
|
|
You are probably not using correct tools or are not connecting stuff correctly.
I've recovered ECU's with TDI software flashed onto them and other totally ridiculous stuff.
Regardless, if you actually took your time to read through the C167 user manual, you would see, that when entering boot mode it does not matter at all what is in the processor's ROM or the processor's FLASH.
Simply put this code is never executed. When the correct logic is present at the correct pins, the processor simply enters a hardware mode and listens for serial communications through which you can upload your own code to be executed.
This is also why you can not protect a such ECU from a boot read.
TL;DR
You are doing it wrong. Proof is the C167 document.
|
|
|
|
|
Logged
|
|
|
|
|
vwaudiguy
|
|
« Reply #12 on: April 13, 2016, 10:01:57 AM »
|
|
|
Has anyone seen a case where flashing the wrong file did physical damage to the hardware on the pcb (flash chip or otherwise)?
|
|
|
|
|
Logged
|
"If you have a chinese turbo, that you are worried is going to blow up when you floor it, then LOL."
|
|
|
|
prj
|
|
« Reply #13 on: April 13, 2016, 01:04:47 PM »
|
|
|
Has anyone seen a case where flashing the wrong file did physical damage to the hardware on the pcb (flash chip or otherwise)?
It's all logic paths, it is impossible to damage unless you initiate an infinite loop of erase/write cycles. You could theorize that it is maybe possible to overload a driver, but unlikely. Basically, you can't do any physical damage by flashing random shit onto the ECU, the stuff flashed onto it must have malicious intent to damage the flash chip. |
|
|
|
|
Logged
|
|
|
|
|
vwaudiguy
|
|
« Reply #14 on: April 13, 2016, 01:43:21 PM »
|
|
|
Thanks for the explanation, prj.
|
|
|
|
|
Logged
|
"If you have a chinese turbo, that you are worried is going to blow up when you floor it, then LOL."
|
|
|
|
