kindle firmware update weirdities and oddnesses

[geekmaster]

kindle firmware update weirdities and oddnesses

Just 12 days ago I downloaded all available kindle firmware updates for all eink kindle models.

I discovered that a couple of the update*.bin files were slightly different sizes than files I had previously downloaded awhile ago. I extracted and compared the contents of these update files. The ONLY difference was that a different method of updating the java certificates was used.

Previously, the (text file) certs were patched with a huge monolithic script that ran "bspatch" on a ton of binary patch files that patched both binary and text files.

In the latest download of the latest update files WITH THE EXACT SAME FILENAME as the older versions, the certs update patch files were removed, and the huge monolithic script has had the cert patching code snippet removed. Instead, there is a new (complete) cert file, and a new script to replace the old cert file.

Today, I downloaded a bunch of update*.bin files for multiple of my kindle models, and comparing them shows that the file sizes have also changed on those files, even though the download file names are exactly the same as the previous different downloads of these same file names.

Kindle does not mention anything about multiple different versions of firmware update files with identical file names, nor any need to update your kindle. I wonder how this will affect folks (such as myself) who have already installed the old versions of the latest firmware files on some of their kindles...

[knc1]

The complete replacements are probably to avoid bspatch failures.

Plus, the overall total size should be smaller.
bsbatch was specifically design to yield a small size when used on an ELF file structure.
It doesn't do a very good job of minimizing the patch size on text files.

And their not bothering to update the firmware version is not new either.
2.5.8 is up to either 2.5.8.2 or 2.5.8.3 now by any sane numbering system.

[geekmaster]

The firmwares where a patch was removed and replaced by a script and text (cert) file are indeed slightly smaller, in all cases I have examined thus far.

But still, I am curious why they bothered. I suppose if there was a (hidden) fix to the cert file (in cases where bspatch failed to update it), then those of us with the older update installed could have obsolete java certificates (or they plan to sneek in a hidden OTA patch when we turn off wireless on (or airplane mode off as the case may be).

On another note, while doing firmware updates to a K5 I am using (which previously had the firmware version installed by kubrick), I was surprised by the significant changes to the GUI framework screen layout, replacement fonts, replacement images (including the screen for USB drive mode), etc.

[knc1]

They stopped accepting SSLv3 on their network on March 22nd.

[geekmaster]

Originally Posted by knc1

They stopped accepting SSLv3 on their network on March 22nd.

So folks who already have the (old) latest firmware version on their kindles have to redownload and reinstall the "new" latest (same) version with the new cert file?

[knc1]

Originally Posted by geekmaster

So folks who already have the (old) latest firmware version on their kindles have to redownload and reinstall the "new" latest (same) version with the new cert file?

For some models, it is listed as a update_cacert.bin file.

But that is not used consistently for all models.
Some just say:
"Even if on latest firmware version, download and install the one now posted." (or words to that effect)

The 'new' page layout at Amazon for each device gives the details.