|
Well, I mentioned above that I considered this device "bricked". However, knc1 is probably right - the underlying problem might not be fixable, but could in theory be bypassed (one of my favorite quotes from Gilliams "Brazil": "can you fix it?" - "no I can't. But I can bypass it").
In order to do that, one would have to modify the in-kernel mmc driver (given that it really does bad block management in there, which I still find hard to believe that the eMMC does nothing in that regard) to alter its bad block management. Plus, the kernel would need to be exchanged.
That would be some major work that probably noone will tackle who doesn't feel really pressed to solve a similar problem.
I'd really like to emphasize that I can't think of any other thing that would produce those errors on the Kindle itself. They clearly complain about the eMMC, not the USB connection. And from all the things that work via USB, I find it hard to believe that the culprit should be there.
|