Alternate "Simple" debricking methods for K5-Touch, K4-Mini, & K3-Keyboard

[twobob]

Originally Posted by ixtab

Ok, but then I still think that what they're doing is just not fair. Why don't they (=lab126) just allow the developer community (=us) to just do our things, but instead spit into our faces with every new firmware release?

Ah whatever, it makes no sense to complain or argue. Corporate policy decided that they have to be assholes - and they agreed.

All I can say is we KNOW THEIR address... they do not know ours

I would "whoa down" on the spit if I was them

[geekmaster]

In cases where your Kindle battery just will not take a charge because it is TOO discharged, you might want to try this little trick to wake it up so it WILL take a charge:

This video shows a cellphone battery being revived, but the same trick may work on a Kindle battery. It is certainly worth trying before discarding an otherwise "dead" battery.

Do not apply the uncontrolled charge for long (more than about 10 seconds) to prevent danger from a Lithium fire. Better to do this outside, or at least on a fireproof surface.

[twobob]

cool idea... Terrible camera work

[tindom]

How to restore Paperwhite? ("Repair Needed")

1.FIRMWARE 5.3.3

2.Jailbreaked and usbnet 0.6

3.USB-disk is accessible less than 10 seconds , no ssh

4.copied data.stgz(thanks NiLuJe) and RUNME.sh to USB-disk

5.RUNME.sh

#!/bin/sh
mntroot rw
touch /mnt/us/a.bac
rm -f /etc/fonts/conf.d/99-font.conf
rm -f /usr/java/lib/font/*.ttf
cp /mnt/us/a.bac /mnt/us/a.ok
mntroot ro

6.after reset ,only RUNME.sh in USB-disk , no data.stgz ,no a.bac

Why RUNME.sh didn't worked.

Thx guys

Ps. Sorry for my bad English

[knc1]

Originally Posted by tindom

How to restore Paperwhite? ("Repair Needed")

1.FIRMWARE 5.3.3

- - - -

Why RUNME.sh didn't worked.

Thx guys

Ps. Sorry for my bad English

Because of item #1 on your list?
I think that is the case, otherwise we would use that method to jailbreak 5.3.3

Search in the de-bricking threads - I seem to re-call someone recovering a Kpw from this "repair needed" state.

[ixtab]

data.stgz does NOT work on FW 5.3.3.

If you have re-installed the rescue pack after the 5.3.3 upgrade, place ENABLE_DIAGS file on usb and reboot, enable USB network in diags, and debrick from there. (I.e., overwrite main kernel and partition, and blast /dev/mmcblk0p3). If you haven't... well, bad luck, serial port.

[tindom]

Originally Posted by knc1

Because of item #1 on your list?
I think that is the case, otherwise we would use that method to jailbreak 5.3.3

Search in the de-bricking threads - I seem to re-call someone recovering a Kpw from this "repair needed" state.

Yes,I have . Is it?

http://www.mobileread.com/forums/sho....php?p=2276382

so I know runme.sh

[tindom]

Originally Posted by ixtab

data.stgz does NOT work on FW 5.3.3.

If you have re-installed the rescue pack after the 5.3.3 upgrade, place ENABLE_DIAGS file on usb and reboot, enable USB network in diags, and debrick from there. (I.e., overwrite main kernel and partition, and blast /dev/mmcblk0p3). If you haven't... well, bad luck, serial port.

No,I haven't . Thx ixtab

[schorsch]

I debricked my black Kindle 4NT with the firmware version 4.1 but because there was no diags images for firmware 4.1 I flashed the mmcblk0p2-4.0.0 and restored my Kindle by using the mmcblk0p1-4.1.0 via SSH.
No my Kindle boots and sohow all available wifi networks, but if I try to connect the conection fails.
update:
It works after setting date via SSH and ignor the wifi error message.