Quote:
Originally Posted by DoctorM
True, but there are people reporting re-occurring issues with the dictionary and such that other people have never seen. So that means either there is some bad data that a factory reset doesn't fix or a hardware problems. If it was a firmware issue, EVERYONE would have that problem.
|
It's entirely possible that everyone might
have a software problem, but the majority never experience it - if, for example, the dictionary-crash bug only occurred if a user has their location set to a particular country, and their default font size to a specific size, then some users would experience it consistently, whilst others would never experience it all. It's a delightful feature of software complexity.
Quote:
Originally Posted by DoctorM
In the past I've recovered a bricked reader, that among other things required using Porkupan's rescue package. (It then requires some hex editing to fix firmware version numbers and reflashing to the current one.)
By extension, there are restore-sets, design for de-rooting, but IIRC completely wipe the internal storage. So while it may take some hex editing as mentioned above, at that point, there should be nothing left of any remnant crap from a bad firmware flash.
|
I had read somewhere that some bugs could be fixed by re-formatting the partitions on the reader, but that apparently required that you had a second reader to then copy the partitions from afterwards. I didn't know about Porkupan's rescue package; this is interesting information. Can I use it to restore my reader if I've updated to a newer version of the firmware?