View Single Post
Old 03-22-2021, 06:37 AM   #58
tryol
Warm Lighting Enthusiast
tryol ought to be getting tired of karma fortunes by now.tryol ought to be getting tired of karma fortunes by now.tryol ought to be getting tired of karma fortunes by now.tryol ought to be getting tired of karma fortunes by now.tryol ought to be getting tired of karma fortunes by now.tryol ought to be getting tired of karma fortunes by now.tryol ought to be getting tired of karma fortunes by now.tryol ought to be getting tired of karma fortunes by now.tryol ought to be getting tired of karma fortunes by now.tryol ought to be getting tired of karma fortunes by now.tryol ought to be getting tired of karma fortunes by now.
 
tryol's Avatar
 
Posts: 91
Karma: 754136
Join Date: Dec 2020
Device: Kindle Oasis 3 (jailbroken)
Quote:
Originally Posted by tva2000hn View Post
That's great to hear !! I think you only need to build the images for 5.10.3 to 5.13.3 , as everyone can still manually download the supported OS versions and sideload - upgrade it without turning wifi on ( every kindle is fully jailbroken up to PW1; and PW2 and above support OS versions 5.10.3 to 5.13.3)
Since only I got my first kindle a few months ago, I didn't get to experience the older firmwares. I assumed that some newer versions have issues or remove/change features that make people not want to upgrade to them. That's why I planned to support versions below 5.12.2.1.1, plus I also wanted to support KT and PW which are way below that. Seems like 5.10.3 - 5.13.3 is enough then, at least for the initial thread.

Quote:
Originally Posted by hius07 View Post
The main difference between firmwares 5.11.* and 5.12 (and above) is an ability to block firmware ota updates: simple blocking directory vs renaming sys files.
I've started using your KUAL script that renames the system files but I'm still scared to turn airplane mode off. Has it been tested extensively enough? (I'm on 5.12.4.)

Quote:
Originally Posted by hius07 View Post
So it might be enough to have just two magic images: for 5.11.2 (the last 5.11.*) and for 5.13.3 (the last jailbreakable) for all models starting from PW3 and newer (except PW4).
No need for PW4 images at all (well, not urgent).

The latest update for PW2 and KT2 is 5.12.2.1.1, highly likely with closed vulneability, need to be tested. 5.12.2 is good for sure.
The image for group 5.10.3-5.13.3 SHOULD work for any device in that range, there is no such thing as a 5.11.2, 5.13.3 or PW4 image. I'm planning to test that "SHOULD" though before I make the image public.

Quote:
Originally Posted by cabcool View Post
I'm only a dumb end-user, but I've been following these forums for a while in hopes of a jailbreak for my PW3 running 5.12.2.

If I'm not misunderstanding, that's what this exploit might be able to do?

Then I would like to help out if it's useful.
Quote:
Originally Posted by Akirainblack View Post
@tryol Is it worth releasing what you have working for the latest firmwares, just so that there are some of us who've done this and can then help those that struggle?
I've a Voyage on 5.13.1 which I'd love to get jailbroken and am more than happy to help others once I know the process.

I'll PM you both soon, 5.12.2 and 5.13.1 are versions I haven't explicitly tested yet, and I want to before I make the new thread.
If anybody else wants to help with testing, PM me with your device and firmware version! Untested firmwares preferred, especially the 2 extremities; 5.10.3 and 5.13.3.


The working firmware/device combinations for firmware versions (5.10.3 - 5.13.3) that got tested so far (constantly updated):
Spoiler:

5.13.3: KOA2
5.13.2: PW3
5.13.1: KV
5.12.5: KOA3
5.12.4: KT4, KOA3
5.12.3: KOA2
5.12.2.1.1 PW2 (PW2/KT2 exclusive firmware)
5.12.2.1: PW2 (PW2/KT2 exclusive firmware)
5.12.2: KT2, KT4, PW3
5.12.1.1: KOA3 (KOA3 exclusive firmware)
5.12.1: KOA2
5.11.2: KOA2
5.11.1.1: KOA2
5.11.1: PW4 (PW4 exclusive firmware)
5.10.3: KV


Once I get enough data I'll make it public for everybody.

Last edited by tryol; 03-23-2021 at 06:49 PM. Reason: Added 5.10.3 since it was found out that it belongs to the same group
tryol is offline   Reply With Quote