Quote:
Originally Posted by knc1
- What do you mean by "bricked" ?
At least give a good description of changes in the device's behavior you have noticed.
|
The Kindle boots up to about a third of the progress bar and then resets, booting from anew. It's stuck in a loop.
I can enter 'Recovery Mode' by holding 'Home' during startup, doing a factory reset:
Code:
Reset to Factory Defaults
You are about to reset your Kindle DX to factory defaults, which will
remove all downloaded or transferred content from this device. You
will still be able to download Archived items. If you wish to continue
enter "reset" on the keyboard.
(click to cancel)
This then gives me a screen displaying the following:
Code:
Your Device Is in Reovery Mode.
To exit this mode, press the (R 4) key.
If you need to update your Kindle
through Recovery Mode, please
call Customer Service for rurther
assisstance at 1-866-321-8851 or
1-206-266-0927. For UK customers,
please call +44(0)800 496-2499.
In this mode I can access the document partition (which is empty after a factory reset) via USB and transfer files.
Quote:
Originally Posted by knc1
- Which version of firmware is now on the device?
|
Still the original version
2.5.8.
Quote:
Originally Posted by knc1
- What have you done to the device?
|
First thing I did was jailbreaking it and installing a VNC viewer according to
http://www.techhive.com/article/2595...c_display.html (or something very similiar). This worked perfectly.
I then tried to install wget to be able to automatically download news etc. without needing a PC. I did this by transmitting the binary via the document partition and moving it to /usr/bin with SSH (I'm not sure about the exact paths, but it was a quite standard linux filesystem).
Unfortunately, wget needed some system libraries which weren't on the Kindle or which were too old. So I upgraded them without thinking. Unfortunately, I don't remember where I got them from (just took the first ARM version I found) and which ones I updated. There were at least a few important ones, possibly libc.
Quote:
Originally Posted by knc1
- What things have you tried already to correct the problem?
Include the result of each thing you tried.
|
In fear of doing other stupid things and lacking a complete firmware image, not much.
I put the firmware update from Amazon (
https://s3.amazonaws.com/G7G_Firmwar...2.5.8_B002.bin)
on to the document partition and restarted the Kindle, hoping it would apply the .bin file.
Result: Still stuck in a boot-loop.
Quote:
Originally Posted by knc1
- How did you determine it was "just a few system files"?
|
Because that's the only thing I changed.
Quote:
Originally Posted by knc1
- How did you determine the above without learning where they are kept and how to access them?
Note: the DX(G) devices store the system image spread across multiple physical devices.
|
They weren't system image files or anything so low-level, I replaced system
libraries, meaning .so files in /usr/lib or /usr/local/lib.
Quote:
Originally Posted by knc1
- This point is the confusing one -
How did you come about the specific knowledge of the "fix" required without knowing the general background knowledge.
|
Well, over SSH it's more or less a standard linux system, no specific knowledge required to mess that up. I have no idea about the internals lying below the operating system. Probably some kind of bootloader?
I think the confusion stems from thinking I messed with the system image itself, not just with the files from the OS.
Quote:
Originally Posted by knc1
- Names of the files you need.
|
Probably just the content of /usr/lib or /usr/local/lib or wherevere the Kindle keeps its libraries and way of getting them there. These are all open-source libraries and shouldn't be copyrighted by Amazon.
Quote:
Originally Posted by knc1
Translation:
To solve this problem, you will have to visit here more often than once every 3 or 4 months.
If only so you can clarify what your problem is.
There isn't a "black box - answer all problems" solution here, we need to know more about what we are expected to fix.  |
Yeah, I'm sorry about that.
I do have more time now, so I will reply as soon as I can. (I just noticed I had notification emails on 'weekly', fixed it)
I'm very glad for your help - You have all been very obliging!
