Thread: unbrik kindle3
View Single Post
Old 03-26-2012, 02:39 PM   #22
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by hawhill View Post
From looking at the info in the OP, it looks like the eMMC degraded and the sectors on the end are not working anymore. This is probably the internal controller in the eMMC, in fact the damaged flash sectors might be in another physical position.

It looks like a case of "send it to amazon and hope for exchange device".

Note that I don't think it's the USB connection. The errors on the Kindle itself indicate otherwise.

I have one question left: How did it break? Out of thin air or after doing something? It wasn't mentioned in the OP...
From what I have seen in the mmc read and write functions in the u-boot source code, they do not do effective write wear-leveling. It is possible that the mmc was worn out by too many repeated writes to a limited area. One way this can occur is by mounting a swap file on the MMC. It should be possible to map out the bad areas, but some blocks may still be near end-of-life. FAT partitions support bad block mapping, so you can map out defective areas that way.
geekmaster is offline   Reply With Quote