Kindle Paperwhite Jailbreak (5.2.0 - 5.3.1, 5.3.4, 5.3.5)

[GoSharks]

Originally Posted by henriquelbsouza

Yes it is possible, but you need to do a downgrade to 5.3.2 and then apply the jailbreak... after that you do the upgrade to 5.3.3 and re-install the

The Kindlet developer certificates.

and the

The Rescue Pack.

Has a better explanation on the first post at this topic.

Not that I should be the one to point out FW number mistakes (after my snafu in another thread!), but you need to downgrade your PW to FW 5.3.1 to apply the jailbreak. Definitely follow the directions at the first post...they are comprehensive.

[Gazella]

Yes I thought it was 5.3.1 and not 5.3.2. Anyways, I downgraded to 5.3.1 and have downloaded the jailbreak onto my Kindle so now it's currently going through the process of jailbreaking. I hope everything goes well.

[DonnieMega]

Nm I figured it out

[mallums]

So, what's the word on the Paperwhite 5.3.4 FW that came out a day ago?

Smells like another recovery image.

[diba]

Anyone already gone from 5.3.1 to 5.3.4 and having checked the survival of the JB?

[bluehanson]

Hey, ixtab, a friend of mine tried your method on a kindle paperwhite with firmware 5.3.4, it worked directly, no need to downgrade to 5.3.1 or any older.

[ixtab]

Originally Posted by bluehanson

Hey, ixtab, a friend of mine tried your method on a kindle paperwhite with firmware 5.3.4, it worked directly, no need to downgrade to 5.3.1 or any older.

Wow - thanks for the info... confirmed. Now that was totally unexpected.

[diba]

Thx, 1 hr before I went from 5.3.3 to 5.3.1 to 5.3.3 to 5.4.4 ...
But it worked, noe I just wait for the jbpatch ... and would be happy with hypernation and margins only yet.

[Yolina]

Originally Posted by ixtab

Wow - thanks for the info... confirmed. Now that was totally unexpected.

Is that lab126 *finally* showing you some love or did they just forget to mess with the JB

[mallums]

Just another confirmation: 1. On a previously jailbroken 5.3.3, updated to 5.3.4, the bridge appears to do its job, as the word "jailbreak" appears a couple of times during the *official* update. 2. For fun, I reapplied the 5.3.1 JB to 5.3.4, and the original method worked perfectly; the JB proceeded normally and appears to install successfully. 3. I reapplied the Kindlet dev certs update and the JBbridge update separately, and they installed fine, confirming that the 5.3.4 is jailbroken.

So there you have it!

/ US Paperwhite

[ixtab]

Originally Posted by mallums

Just another confirmation: 1. On a previously jailbroken 5.3.3, updated to 5.3.4, the bridge appears to do its job, as the word "jailbreak" appears a couple of times during the *official* update. 2. For fun, I reapplied the 5.3.1 JB to 5.3.4, and the original method worked perfectly; the JB proceeded normally and appears to install successfully. 3. I reapplied the Kindlet dev certs update and the JBbridge update separately, and they installed fine, confirming that the 5.3.4 is jailbroken.

So there you have it!

/ US Paperwhite

You forgot the most important one: the rescue pack - the bundled version was faulty at the time you installed the jailbreak, so you should have re-installed it, too.

BTW, I just uploaded a new version of the jailbreak installer, which includes the fixed rescue pack.

[kindleuzer]

How do you downgrade the firmware? The initial post didn't say.

[ixtab]

Exactly the same way as you upgrade the firmware: put the respective update*.bin on the Kindle and restart it.

[kindleuzer]

Oh, ok. I didn't know if it should go in the root directory or where.


>>edit: Can I install the dev-certs and the rescue pack all at once, or do I need to do them one at a time?

[kindleuzer]

Oh [edited - M.] - after loading the update_combined-dev-certs-20121002_install.bin and restarting, Kindle says:

-------------- ! -----------------------

The update was not successful.

If you need assistance visit www.kindle.com/support.

To resume using your Kindle, please press the power button.

UPDATE ERROR: 3

-------------------------------------

What do I do now? Just restart and try it again?


N/M - after installing the rescue pack I tried again, and this time it worked. Thanks!