Well, let me try another of the obvious possibilities -
Check your firmware version -
Is it what you expect or did it update on you?
The reason:
USBnetworking is one of those that has to be re-installed after each Amazon update.
Oh, heck, don't bother, just re-install it being sure to remove the current one's configuration file first (it is normally left behind and you didn't show enough of the file system tree to know if that is part of the problem - such as a keyname flagfile).
I.E: One directory level above what you showed, see if you put a file named 'auto' in that directory (that could be what happened and the off-site directions you linked to mention it).
If you can't reach the user's USB storage, your fall back is to use the newest JB on the device.
Did you mention having kTerm?
You should be able to use 'wget' (or 'curl') to download the package directly to the Kindle (/mnt/us/mrpackages).
PS: As someone already suggested - you might be running 'diags' system rather than the 'main' system or running the 'demo' system.
Was this ever a "demo Kindle" ?
Last edited by knc1; 11-07-2016 at 09:52 AM.
|