Quote:
Originally Posted by badgoodDeb
Might this be a case of "wrong update software"? Are you sure you manually installed the version that was MEANT for your version of Voyage? You can break them by accidentally getting the wrong version (I just wait for an over-the-air download).
|
Not possible, they are model locked.*
It is only the factory production line testing update packages used with the current jailbreak that are not model locked.
- - - -
There is one way that the update process can fail and brick a Kindle that I know of (although not seen reported here in a long time).
It is a full image update, the package is checked, the current charge level of the battery is checked but due to space limitations, if something goes wrong along the way, the updater has no way to "back up" (no "un-do" feature in the updater).
So if the O.P. would hook up the serial port and we looked into the problem, I bet we would find the system is trying to run a mixture of firmware versions (the new one only partly installed).
And that can be fixed (from the serial port) -
Put it into the 'diags' system, put a known good copy of the KV, 5.8.9.2 update on the drive, then trigger the install.
('Main' will not re-install the current version (or older) but diags will.)
* Just like our update_*.bin packages here are model locked.
Same package type and same package updater (we use the system one Amazon provides for their own use).
An interesting O.T. chuckle -
Over the recent couple of years I have found references to Lab126 packages being built by our (NiLuJe's) Kindletool.
Must have been times when our packager was more "up to date" than the company's internal application.
(It is also very likely much faster than their's.)