Quote:
Originally Posted by adonis
Well, let me describe the current situation:
My kindle seems to be bricked. It shows the following message on the kindle-screen:
https://goo.gl/photos/v1Hc9uWpX3evmtVf6
When i plug it via USB, it's not getting recognized by my computer.
So I've connected the kindle via serial (CP2102) to my Mac.
When i restart my kindle i get this log-output through serial connection:
http://pastebin.com/jJ4pRqwX
- - - - |
Reading that, it looks to me as if your still running the initramfs (I.E: the boot hasn't progressed far enough to load the rootfs stored on /dev/mmcblk0p0 "main" or p1 "diags").
The chance that there is something wrong with the kernel or any of the code in the initramfs file system is slim to none.
It passes its checksum tests when loaded.
None of the code in 'main' or 'diags' could be at fault - you never get far enough along to execute either of them.
- - - -
Possible paths towards narrowing down the problem:
You have two (2) kernels with their statically linked in initramfs.
You could try booting the 'other' one.
I.E: If that boot log was from 'main' try booting 'diag' system's kernel.
You can get into the boot sequence at the u-boot prompt.
You have two different builds of u-boot available.
The first one (which you escape into from the serial port) is a small (limited feature) build of u-boot.
When you execute the bist command - that actually loads the larger (more fully featured) build of u-boot.
Do that, then list the available commands of the "full" featured build of u-boot.
Your looking for something that will read or write or re-initialize the battery ID field.
(I.E: Something you did (but haven't mentioned yet) may have trashed that information in the flash data area.)
I still don't see why you think that fastboot isn't running.
Just because your getting battery status reports on the serial port does not mean that fastboot is not running.
So continue on with the instructions, try communicating with the Kindle's fastboot utility from your PC.
Use the fastboot set/get bootmode commands (or anything else that might give you an indication if the Kindle is responding).
I suggest trying the bootmode setting commands, because you can then try setting the bootmode to 'diags' and re-booting (both using fastboot on the pc) - just skip on down to the instructions for doing that in the other how-to you linked to.
This will give you the chance to try the other kernel (and its code in its own initramfs).
But I don't expect it will be any different about not liking the battery (unless it auto-reinitializes the battery id fields during its diag start-up).
Try some of the above, keep notes, post what you tried and what the results where.
- - - - -
If really hard up and you want to chase down what is triggering the battery message;
Check my recent thread on the insides of the pw1-5.6.1.1 update package.
The process is the same for any of the "full image" (since 5.2.something) update packages that Amazon has posted.
The link to the older thread near the start of the new one gives the gory details (and some of the common Amazon variations on the same theme) of earlier than 5.6.x packaged kernels (back to 2.5.8 IIRC).
In fact, I did a "cut, paste and edit" of the command examples for the K4 kernel to take apart the 5.6.1.1 kernel.
So yes, its an old thread, but still has useful information in it.