MobileRead Forums - View Single Post - Original "Simple" debricking methods for K5-Touch, K4-Mini, & K3-Keyboard

kerotan · 06-06-2012, 01:25 PM

I'm back with a bricked kindle touch again!

I successfully unbricked my KT just a few hours ago, but now I tried updating it first to 5.1.0 firmware and it showed me an Error 007. It restarted so and booted up again in the main menu so everything was just fine by then. Until I tried updating it to 5.0.3 firmware (I have the .bin lying around here in my HD) and it showed me an Error 006. It rebooted and now it's stuck in the tree with the text: Please wait a moment while your Kindle starts up.

So here I am again. What could've gone wrong?

It won't even do a hard reset no matter how long you hold it (nor the sometimes required 2nd press after the long hold). And no, I haven't gone through the debricking method just yet. Should I not update it?

EDIT: After you've debricked your kindle touch, don't update to 5.0.3. It will debrick it again. I found the solution by updating to 5.0.4 firmware. It's up and running again. Thanks to all those who helped!

06-06-2012, 01:25 PM	#304
kerotan Member Posts: 13 Karma: 10 Join Date: Jan 2012 Device: Kindle Touch	I'm back with a bricked kindle touch again! I successfully unbricked my KT just a few hours ago, but now I tried updating it first to 5.1.0 firmware and it showed me an Error 007. It restarted so and booted up again in the main menu so everything was just fine by then. Until I tried updating it to 5.0.3 firmware (I have the .bin lying around here in my HD) and it showed me an Error 006. It rebooted and now it's stuck in the tree with the text: Please wait a moment while your Kindle starts up. So here I am again. What could've gone wrong? It won't even do a hard reset no matter how long you hold it (nor the sometimes required 2nd press after the long hold). And no, I haven't gone through the debricking method just yet. Should I not update it? EDIT: After you've debricked your kindle touch, don't update to 5.0.3. It will debrick it again. I found the solution by updating to 5.0.4 firmware. It's up and running again. Thanks to all those who helped! Last edited by kerotan; 06-06-2012 at 03:03 PM.