Quote:
Originally Posted by knc1
**Which** backdoor lock did you have installed or did you have both of them installed?
How much activity on your USB storage since this happened?
If not very much, there is a chance you could find the name of the deleted OTA update file for us.
Just use whatever FAT32 undelete tool you are comfortable with.
I ask this, because they must have changed their naming scheme to avoid our backdoor lock(s).
- - - - - -
Even better yet, if someone can catch the Kindle in the act of downloading the file (which isn't instantaneous over Wifi) -
then tell us what temporary name they are using ....
|
Well, unfortunately there was kind of a lot of activity- once I gave up on KOReader I deleted all the epubs on the kindle and put a bunch of mobis on.
But in any case, I used a program to show the deleted files. It's possible that the update in the first image is the OTA one (the night of December 3 was when I first noticed the greyed out button) but on the other hand I also updated from 5.4.3 to 5.4.5 that afternoon.
I'm guessing the deleted files in the system folder aren't useful at all, but I've included them anyway just in case.
[Images violate posting guidelines - MODERATOR]
MODERATOR NOTICE: Putting images that violate our posting guidelines in spoiler tags still violates our posting guidelines. TAKE THE TIME NOW TO READ THOSE POSTING GUIDELINES. A link is located at the bottom of every page.
Edit @NiLuJe:
Yes, I misunderstood how it worked. When I realized I was on 5.6.1 and nothing on the root would work, I put the stuff in the mrpackages folder and got it working.
Quote:
Originally Posted by shamanNS
To boot into diagnostics mode you should create "ENABLE_DIAGS" file on Kindle Drive (=userstore = /mnt/us, aka what you see when you connect you Kindle to your PC), and then reboot your Kindle. It should start in diagnostics mode. If it does you've verified that you still have functional diagnostics/ Recue pack.
Also what build of KOreader are you using? Because there were couple of reports here about bugs causing Kindle restarts on one of the nightly build of KOreader.
|
To the first question: things definitely seemed to be
happening when I rebooted- lots of screen flashes and things- but in the end it just settled back into regular USB mode, unfortunately. The same was true for when I unplugged it and restarted. : /
To the second one- koreader-kindle-arm-linux-gnueabi-v2014.04-1305-g0a94696, so the koreader-nightly-20141203 version.