Quote:
Originally Posted by knc1
Of course I am only guessing, but read this recent thread (still on the first page of the index):
https://www.mobileread.com/forums/sho...d.php?t=262862
The thing that I am going by is that storage device discovery has found the "faked" USB storage media, but that the file system discovery has not (yet) been run.
Considering how the automation is set up -
The Kindle is programmed to rebuild /mnt/us when/if errors are detected;
A reasonable explanation is that the storage media does not have an error free file system on it (or any file system at all).
Plus, this is an PW-1 (I.E: An older machine), lots more opportunities to develop bad blocks in the flash storage.
And if you where just hit by an OTA update to 5.6.1.1 (which involves some big files) -
now is when the storage hardware problems would be found. |
In this case, I'd just used
this trick to downgrade from 5.6.1.1 to 5.3.9 - the first thing I did after jailbreaking was install and activate Backdoor Lock, without ever turning on Wi-fi - I'd be surprised if it had even had a chance to download the update. I do wonder if that particular downgrade process not have introduced some problems, though- suppose being the guinea pig for this sort of thing can't hurt if that process broke something.
For clarification, as well - I was using MRPackageInstaller to install the Python package and Screensaver Hack package at the same time, queued up - I
assume that it was the Python package that caused it to hang, since the display stuck on that package's installation screen at the point where things screwed up.
But, yes. That thread looks
exactly like the problem I'm experiencing right now- very reassuring! I'll report back if it works, in case anyone runs across this thread in the future looking for a solution.
Thanks!