Quote:
Originally Posted by knc1
It would be very difficult to "get it right" and there is no point to doing it.
The March update (of several years ago) for the K3 was more than just new CA records.
When first released, it was a separate update but at sometime afterwards, Amazon rolled it into the 3.4.2, K3 update without changing the version number (or the URL link).
So now that you have put "foreign" files onto the system ...
*) remove them and restore the state of the file system to what it was before you made any changes or additions.
Why?
Because the files are manifested and checksummed for the "incremental" style of updates used by the 3.x series firmware.
The device will brick if updated when altered files exist on the system.
*) Follow the update directions for your model of device here:
https://www.amazon.com/gp/help/custo...deId=200529700
As I noted above, the image updates linked there already have the TLS changes and the CA certificate updates bundle into them.
Even though the firmware version was not changed from what is shown as install on your device!
or
just do it because I say so.
I.E: Just because your device says it is running 3.4.2 does not mean it is running what is NOW posted by Amazon as 3.4.2
*) Afterward, stop screwing with the system files, you don't have the required background on the Kindle system to be doing that (if you did, you would have never just stuffed the Ubuntu CA files onto it.) |
I did think that it might cause some problems, but I backed up the old files beforehand. Even if it did brick, I got this kindle for $22 off of eBay to mess around with chrooting into Debian on it and just play around with it. It's not a big deal to me, and even if it were to brick if updating, that's fine because I'm not going to update it. I stuffed the Ubuntu CA files onto it to see if it would work (and it did), I already got enough enjoyment out of messing with this device to make the $22 USD worth it to me. Thanks though.