MobileRead Forums - View Single Post - Kindle Touch: Bricked and readonly filesystem

pmugabi · 09-14-2012, 06:53 AM

Hi,

My Kindle Touch stopped working 2 days ago. I was reading a book and it became sluggish, so I did a reset by holding down the power button. Since then it has been rebooting endlessly at the boy under tree screen. I had never done any jailbreaking/hacking before this, only installed the automatic OTA updates from Amazon.

I have followed the guides here to de-brick it but nothing has succeeded. What I think seems to be the problem is that all the filesystems are readonly and I can't change them. I can go into fastboot mode and also into diag mode and export the USB drive. I have tried following the Simple debrick guide but the changes do no take effect.

For example if I put files on the USB drive, they are gone at the next reboot. Even deleted files re-appear at the next reboot. I have as a test also used fastboot to erase the diags partition and kernel but it starts up fine in diag mode even after this.

Any ideas on how I can make the device writable again so that I can fix it?

09-14-2012, 06:53 AM	#1
pmugabi Junior Member Posts: 3 Karma: 10 Join Date: Sep 2012 Device: Kindle Touch	Kindle Touch: Bricked and readonly filesystem Hi, My Kindle Touch stopped working 2 days ago. I was reading a book and it became sluggish, so I did a reset by holding down the power button. Since then it has been rebooting endlessly at the boy under tree screen. I had never done any jailbreaking/hacking before this, only installed the automatic OTA updates from Amazon. I have followed the guides here to de-brick it but nothing has succeeded. What I think seems to be the problem is that all the filesystems are readonly and I can't change them. I can go into fastboot mode and also into diag mode and export the USB drive. I have tried following the Simple debrick guide but the changes do no take effect. For example if I put files on the USB drive, they are gone at the next reboot. Even deleted files re-appear at the next reboot. I have as a test also used fastboot to erase the diags partition and kernel but it starts up fine in diag mode even after this. Any ideas on how I can make the device writable again so that I can fix it?