Quote:
Originally Posted by knc1
Ah, it is the "doing it to" part you have misunderstood.
What is being done is to the contents of the update package, if/when it is found on the area used for visible USB storage.
No header available on the file, file is not recoverable.
Load KindleTool and run an '--info' command against one of the .bin packages.*
That will show you what is missing when Lab126 "burns" the package header contents, contents of the package file, not of what is already installed.
* Use just the command name (kindletool) by itself to output the command description.
|
Quote:
|
What is being done is to the contents of the update package, if/when it is found on the area used for visible USB storage.
|
So upon finding a certain updater package on a certain device, the firmware would burn (as in "destroy") the first 8 KB, which is the header? Pretty neat. A sort of blacklist.
To counter that, and provided that U-Boot isn't checking signatures or anything fancy, a single Kindle has to be manually flashed (aka write to eMMC) with manually jailbroken firmware to see what are system daemons, etc doing. Now, who's going to donate their Kindle?