Quote:
Originally Posted by tommytomtom
I do not quite know which part you are referring to, but if we can get a file with update*.bin in the root directory, we do not need "poison" in the filename, we can just put the real update_5.3.9.bin there and after a restart, we should have a regular kindle!
|
Good point.
A way to "move" /documents/update_5.3.9.txt to /update_5.3.9.bin in the user store. . . .
- - - -
OR -
At one point early in my relationship with this Italian Demo device - -
It checked with Amazon and located an update for its Demo system image (which it really wanted to download and install - I "told it no" - took its wifi away from it).
Perhaps a "smart http proxy" on the lan which could intercept that request and substitute the update_5.3.9.bin package?
Note: The Regular and the Demo packages might be signed by different keys - that may be why the Kindles ship with two Amazon key certs.
I.E: the Kindle might be able to detect this sort of foul play.
