Tutorial KindleBreak - Software Jailbreak for (almost) any Kindle <= 5.13.3

[NiLuJe]

The JB is literally one single inert file, so, no, it has nothing to do with any of this.

[alexbmd]

Originally Posted by j.p.s

as I posted above

thank you will try

[mathieulh]

I applied kindlebreak on my Kindle OASIS 3 a while ago along with the hotfix, it is still on firmware 5.13.3 and I figured this firmware is too old to use the Kindle store, is it safe for me to update, would I be keeping the jailbreak while doing so?

[j.p.s]

Originally Posted by mathieulh

I applied kindlebreak on my Kindle OASIS 3 a while ago along with the hotfix, it is still on firmware 5.13.3 and I figured this firmware is too old to use the Kindle store, is it safe for me to update, would I be keeping the jailbreak while doing so?

I doubt that it is too old to use the kindle store.

Why do you think it would be?

[mathieulh]

Originally Posted by j.p.s

I doubt that it is too old to use the kindle store.

Why do you think it would be?

I get error messages when I try.

[dhdurgee]

Originally Posted by mathieulh

I get error messages when I try.

Please let us know what the error messages are so we can help diagnose the cause of them.

Dave

[p0wer0n]

Looking to see the jb source code if possible. Can someone post it here? Future devs might benefit from it.

[alexbmd]

Originally Posted by j.p.s

Let it run down until you get a low battery warning, then let it charge as high as it wil go. You might have to repeat once.

hi
so I didi 3 times.... discharge until turnoff itself... charge 2+ hours...
still is not showing me that battery is full even after 3 cycle of training battery

[j.p.s]

Originally Posted by alexbmd

hi
so I didi 3 times.... discharge until turnoff itself... charge 2+ hours...
still is not showing me that battery is full even after 3 cycle of training battery

Then your battery has lost capacity.

[alexbmd]

Originally Posted by j.p.s

Then your battery has lost capacity.

and this is happened right after JB , not after charhing ? no I dont guess so

[alexbmd]

and as I see on other big forum... exist few person with the same problem...

[j.p.s]

Originally Posted by alexbmd

and this is happened right after JB , not after charhing ? no I dont guess so

Coincidence is not causation.

Originally Posted by alexbmd

and as I see on other big forum... exist few person with the same problem...

Links?

[alexbmd]

Originally Posted by j.p.s

Coincidence is not causation.

yes, and only few person.. it's resulting small percentage with that problem from all peoples who did JB... but it's not nice that I got into this percentage
but it's not pleasant anymore that there is no solution to the problem
like for android phones

Spoiler:

forum on foreign language

[LostOnTheLine]

Originally Posted by alexbmd

I charge it all day and only 94%

So this might be your problem. Overcharging can kills cells in a battery.

Originally Posted by alexbmd

3 yo
wear - first half year - 1 book at month, then 1 book at year

This could also be it. If it was sitting at full charge for years that can also kill cells in a battery. This is more likely the warmer the area it was kept in was or if it ever got to freezing temps.

Here's why
All Lithium batteries come with a charge less than 80% & usually less than 50%. This is because sitting without discharging can kill the cells. the less power in the cells the less likely it is to happen. Though if you leave it sitting you don't want the battery to be below 20% because there will be some dissipation while it sits &, unlike other battery technologies like NiCad, Lithium batteries need a controller to charge, so if that controller doesn't have power it may not ever charge again without taking apart the battery & replacing the controller. (I don't know why the controller can't just be powered by the charger to initiate it, but I was told that isn't possible with most batteries).

So it's possible that because you left it sitting for a long time fully charged, you live in a hot area & you kept it somewhere not air conditioned, or when you charged it you left it sitting on the charger well after it was full each time your battery has lost some cells. When you have ruptured or bad cells a few different things can happen. 1.) your controller might not ever report that it is full. This is most likely your situation. 2.) Your controller may think you have more when you don't so the device might die when it says it has 10% battery left. 3.) Your controller might have a spot where the controller reads that you have 65% left, then the next second it reads that there's only 48% left. Most people will have encountered at least one of these in their lifetime, that's why.

TL/DR:

• Leaving your device on the charger long time = BAD
• Leaving device unused while fully charged = BAD

Now it's possible that you had this problem before & your device didn't report it because you hadn't calibrated your battery or you had worn the battery down & the sitting on the charger for a long time was the last straw to break the camel's back. Either way the Jailbreak didn't do it, at most it might have refreshed the controller to show something that was already a problem.

[Enduring]

What I haven't been able to find is, what version should we run if we have our pick?

I currently have a PW4 (G000T6) running the minimum 5.10.3.
I know this is compatible with the jailbreak, but should I update to another version?

Are there any benefits/features gained by updating to anything between 5.10.3-5.13.3?

watchthis r03 supports 5.13.4-5.14.2, are any of those updates worth anything?

I am proceeding with jailbreaking 5.10.3 as it seems updating is easy enough while downgrading might not be (but saw downgrading can be possible if already jailbroken...)

Please let me know if anyone has input on the most ideal version.