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

[knc1]

Originally Posted by CaelThunderwing

sadly k3flasher's only for linux, but a lil easier to use than atk.

k3flasher is built against libusb -
so it should build for Windows also (one of the reasons for using libusb).

When you get it built for Windows, please post a copy (binary and any source patches you had to apply).

[PabloEr]

Colleagues - on steps pls...
Concerning battery - I will charge the battery in other Kindle. It isn't charged in the USB Downloader mode. I lcharged in 2 days - voltage became 3.2 volts. Now I charging in other Kindle (simply I opened a cover and I inserted).

[knc1]

Originally Posted by PabloEr

It isn't charged in the USB Downloader mode. I lcharged in 2 days - voltage became 3.2 volts.

Known, and well documented here.

Now I charging in other Kindle (simply I opened a cover and I inserted).

[PabloEr]

Colleagues - step by step manual please... I`m real noob in Kindle development.


Merry XMAS, dear !!!!

[Mariodood]

What happened to this thread?
http://www.mobileread.com/forums/sho....php?p=2202022

The link is broken...

Also, why is debricking Kindles such a big deal? I'm new to Kindle homebrew, in what situation will your Kindle get bricked?

[geekmaster]

Originally Posted by Mariodood

What happened to this thread?
http://www.mobileread.com/forums/sho....php?p=2202022

The link is broken...

Also, why is debricking Kindles such a big deal? I'm new to Kindle homebrew, in what situation will your Kindle get bricked?

That URL is broken because is contains ellipses ("...") inside it. You need the original URL, which is probably a "showpost" URL like this:
http://www.mobileread.com/forums/showpost.php?p=2202022

You mignt not be able to view the full URL in the forum posts, in which case you need to press the QUOTE button and copy it from the edit box, or you need to click it and copy it from the web browser URL address.

EDIT: Personally, I prefer to link to "showthread" instead of "showpost", so that you can see it in the context of surrounding posts:
http://www.mobileread.com/forums/sho....php?p=2202022

[StuMcBill]

Couple of questions:

1. Will this help my Kindle 3 Keyboard (WiFi & 3G) that keeps freezing?

2. Will this restore to pure stock firmware (no jailbreaks / hacks)?

Cheers

Stewart

[knc1]

Originally Posted by StuMcBill

Couple of questions:

1. Will this help my Kindle 3 Keyboard (WiFi & 3G) that keeps freezing?

2. Will this restore to pure stock firmware (no jailbreaks / hacks)?

Cheers

Stewart

1) Tell us why your K3 keeps freezing and we could answer that one.

2) Sort-of. Some of the images have the jailbreak installed. But of course you can always uninstall whatever the image has pre-installed after you write it to the device.

[StuMcBill]

Originally Posted by knc1

1) Tell us why your K3 keeps freezing and we could answer that one.

2) Sort-of. Some of the images have the jailbreak installed. But of course you can always uninstall whatever the image has pre-installed after you write it to the device.

For some reason it keeps freezing after a couple of days of being Idle, and it doesn't respond to the Power Switch (the green light flashes, but nothing happens on screen till I charge the device).

Once I actually get the device to turn on, after a bit of charging (5 minutes or so) it does a full reboot, with the progress bar along the bottom.

When it does turn on, the battery is still almost fully charged, so it doesn't seem to be a battery problem?

I have posted about it here: http://www.mobileread.com/forums/sho...d.php?t=200523

Hmmm, upon looking into it, it maybe is a battery problem!

[knc1]

Yup - battery problem.

The firmware only tests the "terminal voltage" of the battery - NOT the battery's capacity to store a charge.

For Li-Ion - the "aging effect" is to lose storage capacity - it will always re-charge to the full rated terminal voltage.

[geekmaster]

Originally Posted by knc1

Yup - battery problem.

The firmware only tests the "terminal voltage" of the battery - NOT the battery's capacity to store a charge.

For Li-Ion - the "aging effect" is to lose storage capacity - it will always re-charge to the full rated terminal voltage.

The portion of lithium in the battery that no longer takes a charge is referred to as its "rock content". That increases over time, even if stored new in the box. It increases faster with abuse, such as by discharging it too far (leaving it in diags mode, for example). It also increases as you use up its limited number of charge/discharge cycles, so for maximum lifespan you should only charge it when it shows a low battery (i.e. not every night).

[WhiteDwarf72]

On Geekmaster's request I'm posting a fragment of our PM.

WhiteDwarf:

I've just tried to unbrick my K4 black from its demo mode, but every time I'm doing, press power button+home and after LED goes off release power. My kindle just restarts and returns to its demo mode. My Win7 discovers the HID device and when I run mfg tool in the A panel I have this message: Kindle Internal Storage USB Device. I think it is not as it suppose to be. My kindle is still in it's happy demo mode.

geekmaster:

The K4 magic key is the 5-way pad down button, not the home key.

It realy works on my K4 but I've stuck now with driver.

[geekmaster]

Originally Posted by WhiteDwarf72

It really works on my K4 but I've stuck now with driver.

You need to install libusb-win32, as discussed in the "select boot" thread/

If you are running a 64-bit windows, you need to boot into "allow unsigned drivers" mode.

Or, you can instead run imx_usb_loader from the command line, instead of MfgTool. It is cross-platform, but simpler to run it from linux, so you do not need to deal with windows device driver issues like you do with MfgTool...

[WhiteDwarf72]

I've done the "no integrity checks" yesterday, after you've mentioned it. So I hope the checks are inactive until I change otherwise. I've seen a post with similar problem somewhere on the forum. There were even a screen shots, but I can't find it right now:/

[WhiteDwarf72]

For progress loging purpose:
I've used inf.wizzard suplied in libusb. I've created specific driver for my machine and it worked.

Ok, I've moved a bit. I flashed the diags but failed to flash diags kernel as it says file too large.