Quote:
Originally Posted by coplate
Once you have installed 5.8.8+ on a kindle with an official update, it creates a file on the kindle names like "/update_version.txt"
That file has in it 'FB03'
Once that file is in place, you can no longer install 'FB02' packages, which is what the downgrade packages are all.
The actual installation process is in the linux kernel, with private extensions that amazon does not give the source to.
If you are already on 5.8.10, then no version of FB02 packages will install. you can now only install official amazon packages, or look into the 'serial' method.
|
Well, if the "update_version.txt" says "FB03", then why can't I downgrade to something like 5.8.9.2, which also is a "FB03" package?
================
OK, actually I saw the file "version.txt" in the etc folder of the rootfs but I don't think that the Kindle checks it during update. I think that the Kindle only checks for "target OTA" number of the update file. I changed that number of the older 5.8.9.2 and the Kindle actually liked it. It started upgrading, even with a progress bar on the screen but after a few moments, I get Error 04. And that is because of the signature.
I don't really understand why NiLuJe's KindleTool even has the option to sign with pubprodkey02.pem when obviously it doesn't work, and isn't it possible to change the Target OTA revision and the Magic 1, Magic 2 and Minor numbers without resigning the package. Aren't those just some sort of meta data applied to the file, outside of the signature envelope?