Tools Snapshots of NiLuJe's hacks

[possumbly_human]

Originally Posted by shamanNS

Remove the azw2 version of KUAL and install the bin file ( = copy the bin into "mrpackages" folder and trigger MRPI install by using ;log mrpi in search bar) to get the booklet version of KUAL.
Other people that had the same error with new azw2 KUAL already confirmed (on Discord server) that booklet version of KUAL works fine.

Since you're using PW1 you can and should use the booklet version of KUAL anyways.

p. s. I have absolutely no idea why the new azw2 version doesn't work.

Tried to follow this.
PW1 on 5.3.3 and 100% fresh jailbreak after factory reset
Ran the DevCerts for K5 as a regular Update through the menu, Kindle did update and file got consumed

1. Made sure no KUAL-azw2 files exist on my Kindle
2. Followed MRPI instructions as per this post
3. Copied Update_KUALBooklet_v2.7.37_install.bin file into the mrpackages
4. Restarted device
5. Ran

;log mrpi

5. Nothing visibly happened; no new KUAL entry on device. Checked on Mass Storage Mode and .bin was not consumed
6. Tried adding Update_KUALBooklet_hotfix_v2.7.37_install.bin to mrpackages folder for good measure
7. Ran

;log mrpi

8. Same result, files in mrpackages not consumed

..Clearly I'm missing a step somewhere. Please keep I'm mind I'm a little dumb. Do I need to use MRPI? Can I even use it with no preexisting KUAL as it's a KUAL tool (or am I misunderstanding and is it a standalone tool with KUAL integration)?

[starlight992]

Originally Posted by NiLuJe

Rebuilt both KUAL builds in the first post against an updated keystore (available here).

(It lives in /var/local/java/keystore/developer.keystore)

Had to get creative, so, hopefully this doesn't break on old devices.

----

Here's a completely untested DevCerts build that *should* update your on-device keystore (and *only* that)...

Hello! I have a Kindle PW3. Should I put DevCerts-20250419-KeyStore.zip straight in the root folder of the Kindle, or decompress it and put it in a certain folder, or something else?

Thanks in advance!

[SpartanHeavy]

Originally Posted by NiLuJe

hopefully this doesn't break on old devices.

It seems to be broken on my K2.

I ran the DevCerts update and replaced KUAL-KDK-1.0.azw2 with the new version. When trying to open KUAL, I just get the error "The title is not signed by a registered developer."

I did the same thing on my K4, and it's working fine.

[Mattinger]

Hey!
Seems like we have the same issue! Spend 4 hours yesterday trying to get it to work, but sadly always (even after factory reset, fresh successful jailbreak and mkk installation) get the message "This title is not signed by a registered developer". Maybe someone more tech savvy then me has an idea?

[Mattinger]

Using the new devcerts I finally got kual to open on my K3w!! Thank you so much for keeping the software working on old devices!

[dpn703]

Been trying on this for hours now, can't figure it out at all. I get to the step with installing KUAL, and once I try to open it, I just keep getting the same "The title is not signed by a registered developer" error, which looks like a lot of others are facing the same issues.

Maybe its because I'm using a DX and it's just outdated since the recent change, just got this gifted from my grandmother so I just started looking into this today, so it would suck if this just didn't work at all LOL.

[roger64]

I have successfully jaibroken my PW3 with Winterbreak. I am using Kindle version 14.2. Koreader is working. Kual is working.

For added safety, I'd wish to install Niluje's latest DevCert that he published some days ago on my working installation.

However, I'm confused on how to proceed.

Could someone be kind enough to give a step by step tutorial? Which folder? When to reboot, etc.

[bittrulz]

Originally Posted by possumbly_human

Tried to follow this.
PW1 on 5.3.3 and 100% fresh jailbreak after factory reset
Ran the DevCerts for K5 as a regular Update through the menu, Kindle did update and file got consumed

I'm having the same problems on Kindle Paperwhite 1 using DevCerts for K5.

I get this error after update and tapping on KUAL:
"This item is not signed by an authorized developer. Please contact the developer."

[shamanNS]

@roger64

1) download & unpack (on your computer storage) the DevCert archive
2) copy just the "K5 ALL" installer into the "mrpackages" folder on your Kindle
3) also download the latest version of KUAL "coplate" from first post of this forum thread. Unpack it.
4) copy the KUAL installer bin also into the "mrpackages" folder on you Kindle
5) eject Kindle from your computer
6) in search bar of Kindle UI type in ;log mrpi and execute the search. MRPI installer should run and install the 2 bin packages you added from your computer and after that is done Kindle should reboot / restart itself automatically.

[MiniBookWorm]

For my Kindle 3 (3G + Wifi) Keyboard I just did the following:

Downloaded the Cert package and put Update-mkk-20250419-k3g-B006_keystore-install.bin in the root.

Replaced my prior KUAL-KDK-1.0.azw2 with the new one.

Ran the Kindle update, and everything works properly.

Is there going to be a complete package like Update_mkk-20141129-k3g-B006_install.bin that does this all? Or do you have to do a two-step process like I did above?

[chaitanyaI]

HI all...
"I ran the DevCerts update and replaced KUAL-KDK-2.0.azw2 with the new version.
When trying to open KUAL, I just get the error "The title is not signed by a registered developer." "

- Same error with me as all mentioning. Using PW1 model on 5.3.3.
- Done fresh jailbreak at least 5 times with 5 times complete reset.
- I went a bit further and upgraded my fw to 5.4.4 and done JB but still same KUAL error
- I tried ;log mrpi method, no use.

I think I tried almost everything everyone said, but with no success yet.

Please let me know something else I can test?

I tried another way also with no success, copied ".key" from new cert.zip and pasted in jailbreak method in one iteration of jailbreak. It did replaced the key file but no success.
Some one should pitch in for PW1.

[roger64]

Originally Posted by shamanNS

@roger64

1) download & unpack (on your computer storage) the DevCert archive
2) copy just the "K5 ALL" installer into the "mrpackages" folder on your Kindle
3) also download the latest version of KUAL "coplate" from first post of this forum thread. Unpack it.
4) copy the KUAL installer bin also into the "mrpackages" folder on you Kindle
5) eject Kindle from your computer
6) in search bar of Kindle UI type in ;log mrpi and execute the search. MRPI installer should run and install the 2 bin packages you added from your computer and after that is done Kindle should reboot / restart itself automatically.

Thank you very much for your much needed and detailed explanation. Updates went smoothly.
I guess that the new developer key has an extended life. By sheer curiosity, do you know its end date? This way, I'll be prepared and not surprised for the next emergency

[chaitanyaI]

Originally Posted by chaitanyaI

HI all...
"I ran the DevCerts update and replaced KUAL-KDK-2.0.azw2 with the new version.
When trying to open KUAL, I just get the error "The title is not signed by a registered developer." "

- Same error with me as all mentioning. Using PW1 model on 5.3.3.
- Done fresh jailbreak at least 5 times with 5 times complete reset.
- I went a bit further and upgraded my fw to 5.4.4 and done JB but still same KUAL error
- I tried ;log mrpi method, no use.

I think I tried almost everything everyone said, but with no success yet.

Please let me know something else I can test?

I tried another way also with no success, copied ".key" from new cert.zip and pasted in jailbreak method in one iteration of jailbreak. It did replaced the key file but no success.
Some one should pitch in for PW1.

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 ...

[bittrulz]

@chaitanyaI: yeah, it works for Kindle Paperwhite 1 (generation 5) Thank you so much! Now I can read with KoReader again

The only step missing to make it work after updating KUAL and the certificate is to also update the Kindle software to latest available version for this model.

I had 5.4.4 (not sure, something with 5.4) and I got the 5.6.1.1 update from Amazon:
https://www.amazon.com/gp/help/custo...MQC26VQQMM8XSW

[shamanNS]

Originally Posted by roger64

By sheer curiosity, do you know its end date? This way, I'll be prepared and not surprised for the next emergency

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