Closed godreborn closed 2 months ago
It usually happens because of hash mismatch. With mlc it can happen because of scfm caching. (Some of the current data may be in the cache and not written to the mlc yet). Maybe one day there will be an option to give the cache too so we can have an actual complete image, but currently its format is unknown.
So it's normal? I'm just a little concerned, because I don't know if the nand dumper dumped the nand correctly in case of needing to reflash. Thanks for responding.
Yes it is normal. Sadly it is a known limitation with dumping/flashing back mlc. flashing it back may not work because of the scfm. the best chance is to delete it before flashing back, but in this case for example the file will remain corrupted.
I'm getting this error:
I've always gotten errors extracting the mlc, and I have no idea why. it simply says that a file can't be read, and this has happened across two systems. however, the file error is different for each one, a different file can't be read. I don't know if it's the dumper or extractor, but I ftp'd the file over, and injected it. same error as you can see, afterwards.