View Single Post
Old 11-02-2017, 03:11 PM   #2808
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 dhdurgee View Post
Nope. I was relating this to coplate's use of the VoiceView files to test for the ability to downgrade to factory firmware as they use the same format. Given the VoiceView files are an Amazon supported feature the inability to install them is a problem that should be reported to their support people as a regression in the firmware that should be fixed. After all it is quite possible that a VoiceView file might become damaged and require replacement.

Dave
I see, you missed what is being tested.

We only want to see if the Kindle will accept a package with the same first four characters. That is the "Package Type" or "Magic Number".
The contents do not matter for this particular test.

The reason is, when Amazon blocked our current jail break, they only disallowed the "Package Type" or "Magic Number" of the "Initial Factory (production use only)" files.
The Amazon VV files use the same four character magic number.

I.E: They DID block their own VV file packages, we know it, they know it, it was not accidental, it was done that way to avoid re-packaging the VV file packages then in distribution.

Because of problems supporting VV on devices where the customer has used "(Factory) Reset" the "block" is not included in all device/firmware combinations.
Evidently, when the complaint pile reaches a certain height, they push out a firmware version without the block, let every complainer reload the files and then push out another firmware version with the block.
It is only a single line of code that gets commented out in the firmware package.

Use "kindletool convert --info package_name" on both a factory initial package and a vv package and you can see what I mean.

Last edited by knc1; 11-02-2017 at 03:22 PM.
knc1 is offline   Reply With Quote