Tutorial WatchThis - Software Jailbreak for any Kindle <= 5.14.2

[izeman]

Originally Posted by NiLuJe

@izeman: Automod queue on new accounts (this is explicitly mentioned to you on post submission).

Thanks. I was aware of that, and it popped up once (during my second post). My first post was shown as white empty post, while the second one didn't show up at all. I was confused But it seems I just need to me patient. Thank you!

[Alex305]

Originally Posted by shamanNS

Download latest (released / repackaged yesteday) jailbreak hotfix from @NiLuJe's snapshots thread, copy it to Kindle, install it.

Using your PC download from Amazon's servers update bin for 5.14.2 or 5.14.3 (whickever you want to have at the end) > transfer it to your Kindle > install the update > reboot 2? times > AGAIN install the jailbreak hotfix package > reboot 2-3 times > reinstall KUAL using ";log mrpi" > rename ota binaries using "renameota" KUAL extension> done?

I downloaded the last hotfix fw5 I suppose works for my Paperwhite 11th..put into the Kindle root tried to update but can't do that... doesn't work....also I think if I put in the Kindle root the newer firmware already downloaded from Amazon will lock and/or remove my jailbreak

[shamanNS]

Paperwhite 11th gen = PW5 (here on MobileRead, and everywhere else where people count the actual number of models called "Paperwhite".)

[jbaumann]

Ok, now I found a reference to 5.14.1.1 and 5.14.2 as a file on s3 (on TousLesDrivers.com). How can I verify that it is an original firmware?

Cheers, Joe

Originally Posted by jbaumann

I could do everything up to step 7 of the jailbreak, and then got an application error. Rebooted the reader and then did step 8 as described. Everything is fine so far.

[But now I can't find the "Help & User Guides".] Found it after entering ";dsts"...

But after choosing "Get Started" I get an Application Error. Rebooting doesn't help, which leads me to the thought that I might have to update the firmware to 5.14.2 first.

Is that correct, and where can I find it?

And thanks a lot for the Jailbreak.

Cheers, Joe

[shamanNS]

Download desired firmware build from Amazon's servers:

https://s3.amazonaws.com/firmwaredownloads/update_kindle_all_new_paperwhite_11th_5.14.1.1.bin

https://s3.amazonaws.com/firmwaredownloads/update_kindle_all_new_paperwhite_11th_5.14.2.bin

https://s3.amazonaws.com/firmwaredownloads/update_kindle_all_new_paperwhite_11th_5.14.3.bin

My suggestion is to first manually update your PW5 to 5.14.1.1 and have a change to see how the new UI looks like. Since 5.14.1.1 still includes older UI code and in case you dislike it you at least have a choice to revert to that older UI (that you probably have on 5.14.0.1.) after jailbreaking.

If you like the new UI changes then you can then update your device to 5.14.3 (after successfully jailbreaking it while on 5.14.1.1 or 5.14.2).
I'm in the dislike camp and don't plan to update my PW5 from 5.14.1.1. If it wasn't necessary for successful jailbreaking I wouldn't even update it from 5.14.0.1

[Alex305]

Originally Posted by shamanNS

Download desired firmware build from Amazon's servers:

https://s3.amazonaws.com/firmwaredownloads/update_kindle_all_new_paperwhite_11th_5.14.1.1.bin

https://s3.amazonaws.com/firmwaredownloads/update_kindle_all_new_paperwhite_11th_5.14.2.bin

https://s3.amazonaws.com/firmwaredownloads/update_kindle_all_new_paperwhite_11th_5.14.3.bin

My suggestion is to first manually update your PW5 to 5.14.1.1 and have a change to see how the new UI looks like. Since 5.14.1.1 still includes older UI code and in case you dislike it you at least have a choice to revert to that older UI (that you probably have on 5.14.0.1.) after jailbreaking.

If you like the new UI changes then you can then update your device to 5.14.3 (after successfully jailbreaking it while on 5.14.1.1 or 5.14.2).
I'm in the dislike camp and don't plan to update my PW5 from 5.14.1.1. If it wasn't necessary for successful jailbreaking I wouldn't even update it from 5.14.0.1

so you are saying assuming that I already jailbroken my PW5 5.14.2 I can put into kindle root the new 5.14.3 downloaded from Amazon install it without lost jailbreak...I still little confuse because I followed all steps on first page of this topic , I used renameota to avoid software upgrade....and now I read I can update it....also I understood if I'd liked to remove jailbreak I just need to put into the kindle root the stock FW...so guys at this time, I think after lots pages lots guys like me have some confusion...make could be good idea to write down the new guide to follow step by stpep to jailbreak, hot fix and any others utility ...this I is the favor I ask.

Thanks

ps when I did ;enter_demo I enter and afer reboot in my case I tried to use trick double fingers and swipe but didn't work so typed ;demo and enter into menu and i found Sideload Content to be clicked ...strange still I don't understand why didn't need to use the "secret gesture" (double finger tap on bottom right of screen then swipe left)

[Funtast]

Hi!

Is it possible for this jaibreak to work on PW2 with firmware 5.12.2.2.2?
I had it jailbroken before but because it's an old model didn't bother to stop updates. As it happened - Amazon pushed firmware update just to patch the previous jaibreak and nothing more...

https://www.mobileread.com/forums/sh...&postcount=228

[shamanNS]

Originally Posted by Alex305

so you are saying assuming that I already jailbroken my PW5 5.14.2 I can put into kindle root the new 5.14.3 downloaded from Amazon install it without lost jailbreak...I still little confuse because I followed all steps on first page of this topic , I used renameota to avoid software upgrade..

You're confused probably because you're doing stuff without understanding what each of those things actually does.

"rename ota" does just that: renames and thus disables a service whose job is to download update bin on Kindle itself. After doing that Kindle itself should be unable to download firmware update file.
If doesn't stop you from doing that on your PC, transferring the update file to your Kindle and then restarting the device to trigger installation of firmware update, does it?

In any case nothing is stopping you from clicking on "restore" option in Remove OTA Kual extension, doing the firmware update and after restoring KUAL to functional state then again rename the OTA binaries.

Several times already I and other people tried to explain to you that jailbreak survives firmware updates.

If you really wanted to kill jailbreak you can do combination of factory reset followed by a firmware update, than should kill it and make it unrecoverable.

[Alex305]

Originally Posted by shamanNS

You're confused probably because you're doing stuff without understanding what each of those things actually does.

"rename ota" does just that: renames and thus disables a service whose job is to download update bin on Kindle itself. After doing that Kindle itself should be unable to download firmware update file.
If doesn't stop you from doing that on your PC, transferring the update file to your Kindle and then restarting the device to trigger installation of firmware update, does it?

In any case nothing is stopping you from clicking on "restore" option in Remove OTA Kual extension, doing the firmware update and after restoring KUAL to functional state then again rename the OTA binaries.

Several times already I and other people tried to explain to you that jailbreak survives firmware updates.

If you really wanted to kill jailbreak you can do combination of factory reset followed by a firmware update, than should kill it and make it unrecoverable.

Thanks for your patience I'm in this "world" since yesterday and already did , I suppose steps forward, I have installed MRInstaller , restarted device but when I'm in the Kual can't see any place to click to install Python putted as you said in the other topic ("mrpackeges" and putted this "Update_python3_0.15.N_install_pw2_and_up")

same thing when I put "Update_jailbreak_hotfix_1.16.N_install" into main kindle root and try to click update on kindle...I have not possibility to click the button is light grey "un-cliccable"

I'm almost regretting to do everything because instead enjoy my reading in those days I'm doing this

[shamanNS]

Those things happen when someone doesn't read through all the necessary information
You can't install any of MobileRead hacks (ok, the hotfix is the only exception to that rule) using build-in "Update you Kindle" option. That fact is the primary reason MRPI exists

The stuff you put into the "mrpackages" you run either using KUAL > helper > Install MRPI packages OR by typing ";log mrpi" (without quotes) into search bar of your Kindle.

If I recall things correctly to have "helper" submenu you need to download helper extension from Snapshots thread and unpack it into "extensions" folder on your Kindle.

[Funtast]

Originally Posted by Funtast

Hi!

Is it possible for this jaibreak to work on PW2 with firmware 5.12.2.2.2?
I had it jailbroken before but because it's an old model didn't bother to stop updates. As it happened - Amazon pushed firmware update just to patch the previous jaibreak and nothing more...

https://www.mobileread.com/forums/sh...&postcount=228

Sorry my mistake - the jaibreak works. I was stuck on Application error and didn't see the step where I reboot my device

[Alex305]

Originally Posted by shamanNS

Those things happen when someone doesn't read through all the necessary information
You can't install any of MobileRead hacks (ok, the hotfix is the only exception to that rule) using build-in "Update you Kindle" option. That fact is the primary reason MRPI exists

The stuff you put into the "mrpackages" you run either using KUAL > helper > Install MRPI packages OR by typing ";log mrpi" (without quotes) into search bar of your Kindle.

If I recall things correctly to have "helper" submenu you need to download helper extension from Snapshots thread and unpack it into "extensions" folder on your Kindle.

so just to recap:
I installed downloaded 5.14.3 , later finally hotfix...later reinstalled KUal and KOReader...seems all works...the strange thing...I straggled to lost jailbreak instead I didn't lost anything so I enable the OTA using restoreOTA because also with new FW jailbreak permaing ...the only thing still can't figure out is python...I tried any way...


ps during the first reboot onn the bottom of kindle the was a write like (( so I assumed jailbreak was gone...meanwhile I re installed any apps...so my questions is: is some way to check if there is jailbreak...because on the root I have the log...but was yesterday log after jailbreak...

[n1ghtshade]

The jailbreak script ran, but ;uzb does not seem to be doing anything, as once I type it in, and then plug in my kindle into my pc, it still shows these folders: . Am I supposed to manually create /mnt/us or did I do something else wrong, any help?

[Alex305]

@shamanNS thanks so much, finally I did...I putted python stuff you put into the "mrpackages" typed ";log mrpi and worked tooop

in any part of kindle I can see phyton app , I just installed to use mailpush 1.2
I saw into the root folder python ...in case I wish to un install that up is there any command line to remove?

Thanks

ps can I use python for something else?

[shamanNS]

You can use python in whatever script, KUAL extension... whatever you need/want. Things like ScreenSaver hack also use python. So you either use python code in python scripts and run those as KUAL extension or you would need something like "kterm" to be able to open a terminal session and go typing away python code. KOReader also has built in "terminal emulator" as an alternative to using kterm (which is a "standalone" terminal emulator app).

Originally Posted by Alex305

is some way to check if there is jailbreak

If you can install anything your jailbreak is alive. Without it you can't install anything other then official firmware update bin files. And of course you wouldn't be able to open KUAL or start KOReader.

The other question would be "is jailbreak bridge FULLY restored for the next time you do firmware update?" (aka did you install the hotfix successfully after updating to 5.14.3)