View Single Post
Old 09-27-2016, 09:42 AM   #13
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:
Making it immutable is ugly, but, I don't think the system ever changes the file.
Only every time Amazon or yourself installs a firmware update file.
These devices (since 5.1.something) use complete system images as the update.

Also the system still has a file manifest in the form of a list of file, md5sum values for what Amazon/Lab126 considers: "Critical" files.

The rescue pack (rp) installed along with its add-in (cowards rescue pack (crp) ) is (by design) tested very early in the start-up (and certainly before the manifest check although I don't recall if before X is started).

It would be a real good idea for anyone to consider how they are going to rescue or de-brick their Kindle (and maybe practice a bit) before changing system image files.

Last edited by knc1; 09-27-2016 at 09:51 AM.
knc1 is offline   Reply With Quote