Quote:
Originally Posted by knc1
And many are not technically correct in their wording.
You have to be very careful about what non-technical people might write about a technical subject. It is mostly just magic.
The DEVICE jail break (our signature certificate) exists in the main system image and is only used during the installation of a package.
The 'reset' action does not affect the part of the main system image where the installation keys are saved.
And you will notice that those "many" people are reporting that something will not run, not that something will not install.
The 'jailbreak survival code' lives in /var/local, the hidden user area that is backed by partition #3 (the main system image lives in partition #1).
The portion of the overall file tree that is under /var/local IS affected by a reset.
In fact, that is what you are resetting, the file system contents that are stored on partition #3 and partition #4.
The 'hotfix' installs things in addition to the jail break survival code into /var/local.
Some of which is required to **run** (not to **install**) our add-ins.
Things including the application run-time keys. Those are also 'bridged' by the jailbreak survival code.
The 'reset' action includes running the de-registration process, which deletes our application keys.
When a system update is performed, it only replaces what is stored on partition #1.
(In the USA, it would be a criminal act for Amazon to delete anything in the user's data partition, /var/local/** ).
|
Well then a hotfix can put us back on track after a reset?
So, a reset doesnt need a re-jb? @knc1