[Node]

they broke because of kdcan flashing... kdcan chinese fw is the cause

Chinese k-dcan can't transfer big blocks of data(255 bytes), they do it sometimes with trash, and winkfp doesn't double check what was written, so when it checks signature at the end of flash it fails. For example xhp works with chinese kdcans, because it will rewrite data until it will match.But this has nothing to do with this thread, because you cant kill ECU with Chinese d-can it will still communicates. So please, stop flooding about thing that you don't know.

First, WinKFP was never designed to work with crap HW. Why would it be???

Second, IMHO there is no way for WinKFP to know what was actually written into the unit. At least on some of units. Else it would be ёд5у to read flash over OBD which is NOT always the case. xhp works with a limited set of units, so it's NOT a good comparison AT ALL.

Third, YES, you can easily kill units with wrong flash data. Especially simple units like ZBE which do have have luxury of having enough spare flash/RAM to store data received in some unused buffer to first verify it, then reflash itself from that buffer. Those units are rewriting their flash as soon as data was received. Yes, bootlоаdёя should start in emergency mode and allow reflash blah blah blah. That is IF it itself was updated properly. We are talking about E series here where flash was not that low cost before it dropped and became mainstream.

So do NOT blame others for telling TRUTH you don't seem to know yourself.

[pRoxxxDD]

they broke because of kdcan flashing... kdcan chinese fw is the cause

Chinese k-dcan can't transfer big blocks of data(255 bytes), they do it sometimes with trash, and winkfp doesn't double check what was written, so when it checks signature at the end of flash it fails. For example xhp works with chinese kdcans, because it will rewrite data until it will match.But this has nothing to do with this thread, because you cant kill ECU with Chinese d-can it will still communicates. So please, stop flooding about thing that you don't know.

First, WinKFP was never designed to work with crap HW. Why would it be???

Second, IMHO there is no way for WinKFP to know what was actually written into the unit. At least on some of units. Else it would be ёд5у to read flash over OBD which is NOT always the case. xhp works with a limited set of units, so it's NOT a good comparison AT ALL.

Third, YES, you can easily kill units with wrong flash data. Especially simple units like ZBE which do have have luxury of having enough spare flash/RAM to store data received in some unused buffer to first verify it, then reflash itself from that buffer. Those units are rewriting their flash as soon as data was received. Yes, bootlоаdёя should start in emergency mode and allow reflash blah blah blah. That is IF it itself was updated properly. We are talking about E series here where flash was not that low cost before it dropped and became mainstream.

So do NOT blame others for telling TRUTH you don't seem to know yourself.

Yes, you are right not all units allow you to read flash, but in the third рдят you are totally wrong. There is no temporary storage, you always write to the FLASH, and Ecu is designed only to write in ranges, it will not allow you to write to factory bolo or somewhere else, yes there could be errors in design and you can вурдs this restriction, but it's not just ёд5у. So if you write some trashed bytes with china k-dcan there was still factory bolo/bolo/app(depends what are you flashing) for communication.

If i don't know things, why i have suggested to use їсош? How can i know that kdcan can't flash zbe and some others ecu? If you have only kdcan you will deal with a broken zbe for software issue. Stop assuming that you're better than other people. I was responding to a wrong suggestion wich is "use kdcan". If u use bїшшёяgeeks works, or ёdїдbд5lib works, chinese not. And if you have only kdcan you have a piece of crap instead of a zbe. Zbes about this thread are not responding like the op says, so only mcu solutions are possible.

Because it seems you didn't read the first post of the thread, the Author wrote that the unit doesn't communicate, it doesn't matter DCAN or їсош, if DCAN is not broken ofc, it will not start to communicate. їсош doesn't do anything special it still will kwp2000 protocol, through DCAN.

[ttkkas01]

Interesting, I also have an E series ZBE/Idrive controller with corrupt software and doesn't communicate, a dump would be nice

[Akadem]

What programmer can be used to remove the protection from this processor?WinKfp ёxpёят to try.There is also a  battery discharge