Help med17.5.2 boot - bricked ecu

[OVERSPEED]

Hi, today read jetta med17.5.2 with boot kess, made file and start writing... When it came at 99% gives error comunication not present and cant resume at all (tried about 20 times)... I tried writing again but kess cant recognize ECU, made a backup (with corrupted file i tried to write and fail) and notice it is smaller than it should be
It has 27bits less than a normal backup.

Tried to write backup but it cant recognize as med17/5.2 and when i try to write backup it says edc17cp46 and can write the wrong smaller file, but when i try to write a file with correct size it says file is damaged.

Fgtech v53 cant read passou

Ktag cant load pluggin to read or write it

[CustomCars]

I think i will be able to help pls post readed file here.
you write as separate or full ? with full via KTag i will not help.

[TricoreMan]

Never read an write edc/med17 via OBd!

[OVERSPEED]

I wrote only flash, you want backup readed after it bricked?

[CustomCars]

Yes post it, should be helped bring it to liFe.

[filecloud]

I wrote only flash, you want backup readed after it bricked?

MED17.5.2 has no Flash! Only processor.

[OVERSPEED]

MED17.5.2 has no Flash! Only processor.

You know what I mean, these ECU has no external memory, even eeprom (imobilizer, vin,etc) internal in processor too.

FLASH = calibration maps
EEPROM = individual settings, VIN, imobilizer, etc

[J_amb_o]

IROM and EEPROM

[silvergl]

Hi,
fix your problem whit odis engignering.

[filecloud]

Ok. Please send the original readout you did. The file must cover the complete processor including otp area to achieve something.

[OVERSPEED]

Here is "FLASH" (IRON) original readed by Kess

[filecloud]

Good.
Go find someone next to you with an original Byteshooter v4.0 or a EVC BSL with ADP. Then i will calculate your boot password and you can fix the ecu.

[VRPerformance]

1 QUESTION - is your tools original?

[OVERSPEED]

Every guy I know around here use Kess, Ktag or Fgtech... I guess only one has byteshooter.

When I try to read password with FGV53 it shows

............
.....
06J906027A..
.......5E.......
.................
BPG-81002.01.12P3H07
02.01.12
13240163

And says "for this news ECU we have no password at moment"

Can someone point me is there is some way to recover it with Kess or FGtech ? There some way to discover the password from file readed in backup by kess ? (by the way what is this format readed in backup with kess ?)

[OVERSPEED]

Don?t know if can be of one help, but when I try to write/read (even without the password)
it shows:
CPU ID 0000900001820
int flash ID 0053C001