Quote:
Originally Posted by knc1
That all reads as if your PW1 has had a long and useful life.
It may be (past) time to put it down for good.
At least it does if you know of a way to euthanize a PW1.
|
Indeed it had a very long and useful life. A friend on lonely evenings and good way to spend my free time with way over 10k read pages. I'm about to buy another E-ink device but it was too good for the bin. That's why I wanted to debrick it and it will live a maybe short but good life in the family when my new reader arrives.
Quote:
Originally Posted by knc1
*) "installed Duokan";
The members of this forum actively dislike how the Duokan project abused Open Source software.
Not something you will find a lot of help for here.
|
I didn't knew about their Open Source abuse and now that I know about it I'll definitly read more about it. I'm writing scripts my self and publish them Open Source, too. I know how anoying it can be some times.
Quote:
Originally Posted by knc1
*) Missing diags;
The listing you provided above shows that you where trying to boot diags. You may not have intended that, but that is what the listing shows.
(argv[5]: "root=/dev/mmcblk0p2" )
|
I wrote an answer to my original post where I mentioned that it was a dumb mistake from me but I was way over the 5 minutes for editing the Post. I forced diags on boot and forgot to remove it. It was intended in the begining but at that point where I tried to boot the new Firmware it wasn't. Shame on me.^^
Quote:
Originally Posted by knc1
Two possibilities:*) Duokan did it;
Over the years it has been noticed that the Duokan project has attempted to prevent removal of the installation.
It has been known to leave the device crippled in some way(s).
*) The dying eMMC did it;
Not likely, but possible. |
I tested the eMMC over the whole day by writing and reading files, using the Kindle as intended and every thing else I could think about. I'm not 100% sure but I'd blame Duokan in combination with Android OTG.
Quote:
Originally Posted by knc1
Your PW1 should be old enough to use the old "Debricking Guide by geekmaster" once you find that in the "sticky" section, it will include links to off-site files.
Files that are complete "Main" kernel and system; also "Diags" kernel and system.
Even if you re-install all of them, you may need to erase your /dev/mmcblk0p3 (/usr/local IIRC).
Just "touch" it with some leading zeros and re-boot.
The start-up will test, find unusable, and reformat that system for you.
(Same-Same with mmcblk0p4 - your user visible USB directory system. It is much better to let the start-up system reformat any bad drives.)
|
At the moment my Kindle is working flawless. Or better the regular Firmware, Kernel and File System are working flawless. The biggest "Problem" I had was that I forgot to switch back to regular boot. I think I formated and reinstalled my Kindle 5 or 6 times until I gave up and went to bed. Today maybe 5 minutes after I sat down and started the serial console I noticed that I'm still forcing it to boot diags and it was fixed in like 5 seconds.
I'll have a look in the old "Debricking Guide by geekmaster" and i'll try to fix the last missing stuff. Thanks for your long answer.