Tools Snapshots of NiLuJe's hacks

[possumbly_human]

Originally Posted by IJustWantToRead

Just wanted to say I'm also in the same boat with not being able to open KUAL.

Initially got the expired certs error and now get "This item is not signed by an authorised developer. Please contact the developer."

Kindle Paperwhite 1 with fw 5.3.3 and Aeroplane Mode constantly on.

I'm hesitant to update the fw as @chaitanyal suggests because the newer it gets the more issues there appears to be.

Tried updating just the keys, didn't work. Tried a factory reset and full fresh jailbreak and KUAL install, didn't work.

Tried to change the date just to get past the cert expiration but I can only figure out how to change the time, not the date.

Luckily this has only happened to my Kindle because I was trying to put new textbooks on for uni so I've warned my partner never to exit KOReader on theirs. I would greatly appreciate some help as I struggle to read for long periods of time on my computer screen and would really rather read textbooks on the Kindle instead.

Thank you!

Absolutely nothing worked for me on my PW1 with 5.3.3., I HAD to follow @chaitanyal's method. I have not encountered any issues on 5.6.1 and my devide including KOReader actually runs MUCH smoother now. I also keep my device on airplane mode because I have no need for online features.

[roger64]

Originally Posted by shamanNS

The new certificate will expire in year 2099 So you don't need to worry about that since none of as posting here will be alive at that point

Perfect! Thanks.

[ifreedom168]

Originally Posted by chaitanyaI

Hi all,
for all who have issue that "The title is not signed by a registered developer"
I found a temporary solution until developers pitch in to correct the issue.
This is the only solution that worked for me on KPW1 after 3 days and multiple resets. Upgrade to 5.6.1.1 finally after everything worked for me.

I will say what I done, so modify it according to your needs

- Freshly reset the device
- Right now I am in 5.3.3
- Updated it to 5.4.4 (" why, I don't know. I thought it is safe for 5.4.x so why don't update to border ")
- Now jailbreak it as the official snapshot page says.
- Simply put, download "kindle-jailbreak-1.16.N-r19426.tar.xz" > extract kindle-5.4-jailbreak.zip > extract and put all files into root folder of kindle.
- Come to settings > update you will see ***JAIL BREAK***
- Now what I done is, copy the latest .bin for K5 from DevCerts-20250419-KeyStore.zip, placed in root folder
- again, settings > update
- now, install MRPI from this link as instructed. Once you are in 5.6.x.x you cant update any .bin by normal method only MRPI is the way for now.
- now copy latest Kual from official page and extract KUAL-KDK-2.0.azw2 and place in documents folder
- Still you can see when you open KUAL it says error.
- Now magic part, update kindle KPW1 to latest firmware, you know how -> place in root folder then settings > update
Check this screenshot of kindle root folder before updating
- while booting make sure you seen ***BRIDGE+***
- Volla now open KUAL , it worked for me.
- next install extensions like KOREADER or update .bin things using MRPI.

I am happy to write this post, as this should help someone who is struggling to use their old kindles.
This is chaitanya ...

my steps are the following and hope it can help others.
1. Freshly reset the device and mine is kindle paperwhite 2
2. Right now I am in 5.4.2, if not just degrade to this version
3. Now jailbreak,"kindle-jailbreak-1.16.N-r19426.tar.xz" >extract kindle-5.4-jailbreak.zip > extract and put all files into root folder of kindle.Come to settings > update you will see ***JAIL BREAK***
4. copy the latest .bin for K5 from DevCerts-20250419-KeyStore.zip, placed in root folder,again, settings > update
5. now, install MRPI using the file kual-mrinstaller-1.7.N-r19293.tar.
6. copy latest Kual from KUAL-v2.7.37-gfcb45b5-20250419.tar.xz and extract KUAL-KDK-2.0.azw2 and place in documents folder.
7.update kindle KPW1 to 5.4.5 using update_kindle_5.4.5.1.bin, you know how -> place in root folder then settings > update
8. install koreader and kpvbooklet.

[Malc]

I factory reset my 4th gen (4.1.4) - Successfully jail broke it, then followed the guide from the start once more and when I tried opening KUAL get the "this item is not signed by an authorised developer " message that has been detailed over the past 5 or 6 pages.

So I downloaded the DevCert bin file (K4-ALL) dumped that in the root of the kindle and updated the device - No change.

Part of the problem, for me at least, was it's easy to get lost when the guide links to other threads on the forum to download files. Whet would be nice would be a single zip file that contains just the files needed for that one model / firmware, with detailed install notes for dummies... It's so easy to miss a step, or copy the wrong file to the wrong folder and screw things up. Whilst some of you guys are very savvy with this sort of thing, with lots of youtube videos mentioning the way to brake free from Amazon, a lot of people with little or no experience of unlocking their kindles struggle.

Anyway... any pointers on how to get passed this message and get KUAL working would be appreciated

[DCSH82]

Originally Posted by chaitanyaI

- I think you can update from 5.3.3 to 5.6.1 directly no need to update to 5.4.4.2
- Do all the steps ( Dev cert + MRPI + KUAL ) when you are in 5.3.3 then in final step update to 5.6

I can confirm that going right from 5.3.3 to 5.6.1 works for PW1, using the steps according to your description.

Thank you very much for your experiments and posting your solution here, that was very helpful!

I was almost going mad, as all other devides had no problems, but I couldn't get PW1 to launch KUAL again.

[mobichuck]

Okay, so here are some questions; my personal impetus for wanting Py3 on my Oasis was to be able to once again use KUAL's option to build collections from Calibre collections.

I installed the key update.

I seem to have gotten the Py3 hardfloat package installed, but KUAL still doesn't actually create any collections.

- How can I verify that Py3 actually got installed?
- Is Py3 actually the secret sauce that will allow collections to once again be built from Calibre/LibrarianSync?

[Malc]

Well I've tried all variations of KUAL listed on the threads below

https://www.mobileread.com/forums/sh...44&postcount=1
https://www.mobileread.com/forums/sh...d.php?t=225030

I tried the recent signature files after each installation when the original displayed the developer signature message. The only different message I got was when installing a file for around a decade ago which returned a message that the signature had expired or words to that affect and the software needs updating.

If anyone has managed to get this working on a gen 4 (looks like the attached). If so can the filed be zipped up and attached to a new post.

[aha]

Hi,

I can't get the fix working on a K3 Keyboard running 3.4.3.

I've tried a lot of different ways but I keep running into this error when opening the new KUAL, which I haven't seen mentioned yet:

"The title you attempted to open requires a new version of Kindle software. Please update your Kindle to the new software version from the Menu in Settings or the Manage Your Kindle web page. For additional help, please call Kindle Customer Service ..."

The FW is the latest possible version.


Things I've tried include:

- Starting from a factory reset and installing the jailbreak (copy to root folder+update), the new devcerts (copy to root folder+update), and the new KUAL-KDK-2.0.azw2 (copy to documents folder).

- Starting from a factory reset, installing the jailbreak, old devcerts, and old KUAL (getting back to the point of a "permissions expired" error when trying to open KUAL) and then installing the new devcerts and new KUAL as described here.

- all kinds of combinations of the above, installing the new KUAL and only then updating to the new devcerts, etc.


Any advice?

[SpartanHeavy]

Originally Posted by aha

and the new KUAL-KDK-2.0.azw2 (copy to documents folder).

That's the problem. You used the wrong file.

For K3, you need to use KUAL-KDK-1.0.azw2.

[aha]

Okay, I feel like an idiot now.

That works. Thank you!!

[dried]

After a few days of struggling, I was finally able to run KUAL & KOReader on my Kindle Touch, but only by keeping the device in airplane mode during the whole jailbreak process (per this discussion of a different device, might be unrelated) and installing the new DevCerts after the JailBreak (maybe they should be included in it?). Thank you NiLuJe for making and maintaining these hacks, and everyone else who provides advice & support!

[Malc]

Interesting.... might try another factory restore and set the thing up in airplane mode in the same way the above poster mentioned.

[stanislav2000]

Hello. On my Kindle 3 Keyboard does not work. I installed "Update-mkk-20250419-k3w-B008_keystore-install.bin" and then replaced "KUAL-KDK-1.0.azw2" with the current 2.7.37 version. I get the message "The title is not signed by a registered developer". I also had Coolreader installed, which worked without KUAL, but now it does not work either. Please help, because the reader works perfectлъ and I recently changed its battery.

[Malc]

Not sure if its progress, but this time round when launching KUAL I got the following message

"An error occurred: Main Class instantiation threw a RuntimeException. Please contact the developer"

Guys any help would be welcome... I'm losing the will to live at this rate !!

[SpartanHeavy]

Originally Posted by stanislav2000

Hello. On my Kindle 3 Keyboard does not work. I installed "Update-mkk-20250419-k3w-B008_keystore-install.bin" and then replaced "KUAL-KDK-1.0.azw2" with the current 2.7.37 version. I get the message "The title is not signed by a registered developer". I also had Coolreader installed, which worked without KUAL, but now it does not work either. Please help, because the reader works perfectлъ and I recently changed its battery.

Is your firmware up to date? The latest version for Kindle Keyboard is 3.4.3.

I believe the latest firmware needs to be installed for the new keystore update to work.