Quote:
Originally Posted by hawhill
I don't know whether k3flasher will bring real improvements here. You could try it - just to get a different, potentially more verbose error message. My guess is it is in a constant-reboot-loop, an indication we have seen before in some cases. Not entirely sure what this causes, but my guess is on hardware error. (There is the possibility that the battery might not present the right status reporting, but I consider this a rather wild guess that is probably unjustified.)
PS: oh, by the way: the "initial" is a stage where the file you flash doesn't even play a role yet. In that stage, a "loader program" (it is distributed with the ATK) is sent to the kindle and the kindle is made to execute it. Kind of a staged boot-loader, after the very generic "USB downloader" boot loader that is stored in the hardware.
|
Most likely cause, based on the few symptoms I have been able to observe in person - -
fsck errors - and seems to be on mmcblk0p3 (an ext3 file system).
But that would (I assume here) be done in the initramfs image attached to the kernel - - -
A real big bag of worms to to change.
If that filesystem is unreadable or not present at boot time - the initramfs image will recreate it.
But lab126 does not seem to have handled the case of "present with large number of errors".
I think (I am guessing here) that the way out of the "boot loop" is to intentionally destroy the filesystem on mmcblk0p3 (write 16, 512 byte "blocks" if zeroes to it, then re-boot so a new fs gets built).
The above comments 95% based on a sometimes defective crystal ball. YMMV