|
|
#16 | |
|
Member
![]() Posts: 10
Karma: 30
Join Date: Jul 2022
Device: kindle paperwhite 2
|
Quote:
Thank you anyway. |
|
|
|
|
|
|
#17 |
|
Member
![]() Posts: 10
Karma: 30
Join Date: Jul 2022
Device: kindle paperwhite 2
|
Maybe.... I may try updating (or downgrading....) to other firmware version (less than 5.18) by hand. But I think I need to disable OTA update hotfix first. I have basic linux skills, maybe modifying some config file or something like that.... and then putting the update....bin file in the root folder.... so it will be detected and then I will can restart the jailbreak with the classic method, wich worked fine.
|
|
|
|
|
|
#18 |
|
Junior Member
![]() Posts: 4
Karma: 10
Join Date: Mar 2026
Device: K2i
|
K2i with KUAL giving same "title isn't signed error" D:
I'm a literal complete beginner to jailbreaking, and I've been trying for a few days to be able to open KUAL on my old K2i, but every time it gives me the "title isn't signed by a registered developer".
I've successfully jailbroken the Kindle with Niluje's jailbreak and used downloaded launchpad and the custom screensavers, so I think the jailbreak has worked. I've also tried to download the updated MKK from here, using MRPI and in the Root directory: https://www.mobileread.com/forums/sh...postcount=1295 The way I downloaded KUAL doesn't appear (?) to give me an easy way to update the developer key manually, and I've tried all of the tricks on this forum and others that I can find, Any help from someone who knows what they're doing better than me would be amazing! |
|
|
|
|
|
#19 | |
|
Junior Member
![]() Posts: 4
Karma: 10
Join Date: Mar 2026
Device: K2i
|
Quote:
|
|
|
|
|
|
|
#20 |
|
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,168
Karma: 12345678
Join Date: Feb 2010
Location: Serbia
Device: Kindle PW5, Kobo Libra 2, Kindle PW1
|
MRPI isn't used and isn't needed on a K2 (or K3 and K4 either). Custom bin installer on that device are all installed by simply copying bin file into "root" of Kindle removable drive and then after ejecting from computer and using "Update Your Kindle" option.
You don't need KUAL to install new, updated DevCert/MKK. Just copy "Update-mkk-20250419-k2i-B003_keystore-install.bin" and install it using "Update Your Kindle" UI option. If KUAL doesn't even show in your list of book then you used wrong file or copied in into wrong folder. (you new to use "KDK 1.0" azw2 KUAL file and place in into "documents"). Last edited by shamanNS; Yesterday at 05:43 PM. |
|
|
|
|
|
#21 | |
|
Junior Member
![]() Posts: 4
Karma: 10
Join Date: Mar 2026
Device: K2i
|
Quote:
|
|
|
|
|
|
|
#22 |
|
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,168
Karma: 12345678
Join Date: Feb 2010
Location: Serbia
Device: Kindle PW5, Kobo Libra 2, Kindle PW1
|
Well if you can't get KUAL to work I guess you're gonna need to adapt and run those scripts KUAL extension would run using alternative methods. Like defining a shortcut hardware keys combo in launchpad (or if Kindle 2 firmware had search bar commands maybe defining a custom command to run your script).
What do you use KUAL for? Starting KOReader? |
|
|
|
|
|
#23 |
|
Junior Member
![]() Posts: 4
Karma: 10
Join Date: Mar 2026
Device: K2i
|
I'm planning on installing KOReader with KUAL, yeah
Is there a forum that explains how to utilize Launchpad for that? |
|
|
|
![]() |
| Tags |
| kual |
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Troubleshooting Kindle 4 can't launch KUAL after getting out of KOReader. | Brandacafe | Amazon Kindle | 11 | 04-25-2025 02:21 PM |
| K3 (some) KUAL applications do not launch after importing. | lctapps | Kindle Developer's Corner | 5 | 11-10-2023 01:28 PM |
| KUAL won't launch on my Oasis after update | motorvision | KOReader | 3 | 10-03-2023 02:39 PM |
| Launch KUAL extension from within KOreader | Barbas | Kindle Developer's Corner | 10 | 01-18-2023 12:37 PM |
| Porting apps to launch with KUAL (question) | scullyware | Kindle Developer's Corner | 17 | 08-27-2013 02:56 PM |