View Single Post
Old 10-27-2016, 06:35 PM   #4
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by encol View Post
I know there is for factory images, but i intended the firmware update files that Amazon releases.

Perhaps we can try (with the contribute of the members of this forum) to mantain such list, every time Amazon release an update
It does not work, geekmaster tried it.
The problem is Amazon re-issues the update packages without any hints to anyone.
So you can't tell if it is a re-issue or a transmission error.

But there is a life saver there - -

The initial factory images are not 'model locked' - which also means they do not have an over all checksum.
The individual components have checksums, but the updater can not 'back up' if it finds a bad component.

Which is why I provide an external, overall, checksum.

The Amazon customer images are 'model locked' - which means the package has an overall checksum.
And the Kindle update code checks that before it even tries to unpack the components.

Which is why Amazon does not provide an external, overall, checksum (its internal).
knc1 is offline   Reply With Quote