You....the sin that you were to pluck on a thing obvious, that is, that the only way out is recovery from the bdm, and the user who opened the post is not is made more vivid to say if and how he solved
Printable View
You....the sin that you were to pluck on a thing obvious, that is, that the only way out is recovery from the bdm, and the user who opened the post is not is made more vivid to say if and how he solved
[I]hello guys there are, however, I'm away for work I go back tonight and tomorrow I try to take a look at the fileinviati from new diesel 80, but the size seem to read in the obd anyway, thanks to all
Sorry for the stupid question...
On the edc 16 in the obd as well-known, it only reads the flasks.if after changing going to write in obd happens some kind of hitch is you nails...
In bdm you can write only the flash or the ec need to force full backup..
you can also write only the flash, the problem is that many not to say all, the reading is made in the serial flash are not complete, and then also writing it in the bdm does not solve anything, which is why it is recommended to always do before reading in the bdm.
Also you have to hope that when you write by obd, block, have not corrupted the eprom.
As eprom what you mean...the e2p or the flash.
Yes e2p I mean
Mmm to me it seems strange that can become corrupted the e2p...
When you write in obd are not only intervenes on the flash?
It happened to me again, not on a edc16c8 but on a med9.1.
Yes, when you write by obd, write the flash. But I repeat, it happened to me.
hello, and' a bit' that I updated my situation, but it's not changed! I tried to contact the administrators of the site,but the problem and' recover ilbackup bdm on my ecu