La venta termina hoyObtenga un 30% de descuento en cualquier curso (excepto paquetes)
Termina en --- --- ---
Publicaciones del foro
Cursos
Blog
Artículos técnicos
Si no se trata de afinación ni cableado, entonces pertenece aquí.
= Hilos resueltos
I have an ECU that I read via KESS3 (~3MB file, full bin) - this ECU was bricked by someone since that read - bootloader is corrupt.
I am able to read the contents via boot mode via K-TAG and then write those contents back successfully (~1MB size).
I tried to cut out the correct bootloader code and splice it into the file that is able to be written but it wont write - I am a bit stuck for resources and direction on this but feel I am very close to getting the bootloader back and running.
Specific question is - why won't K-TAG load up certain files (checksum?) and how to bypass?
General question is - for these types of situations, where to go, what to do?
Cheers!
hello,
sounds like a tough issue, you're right to chase the bootloader.
Bricked ECU's usually a corrupt or failed flash where its stuck in the BL.
I don't have direct knowledge of the K-Tag SW only OEM tooling but are you able to separate the boot from the application or calibration data and control the destination address? i have found in the past that flashing the boot independently helps recover a bricked ECU. Also have you tried converting the .bin into a .vbf and flashing that?
I'll take a look at K-Tag (out of personal interest) and see how they handle the checksums/security etc.
Apologies I can't be of more help
