View Single Post
Old 12-17-2023, 10:08 PM   #35
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
Nope, it's just a packaging change for *hotfix* packages. Which answers your other questions: hotfix packages have restrictions imposed on their packaging metadata in order to pass through the native "Update Your Kindle" checks.

MRPI packages can be more loosely packaged.

The rest of the packages (with the exception of USBNet, which I forgot for your specific case) haven't been respun, because they're not actually useful on newer devices.

Assuming you're using a KindleTool version built from master, you can repackage an existing (non hotfix) package with a combination of kindletool convert + kindletool create on the resulting tarball.

e.g.,
Code:
kindletool convert Update_usbnet_0.22.N_install_pw2_and_up.bin
kindletool create ota2 -X -d kindle5 Update_usbnet_0.22.N_install_pw2_and_up_converted.tar.gz Update_usbnet_respun.bin

Last edited by NiLuJe; 12-17-2023 at 10:10 PM.
NiLuJe is offline   Reply With Quote