Quote:
Originally Posted by r00t65
Hi, sorry for taking your time.
I am completely stuck with fixing my bricked PW.
Code:
. . . . . . .
kinit: init not found!
Kernel panic - not syncing: Attempted to kill init!
I can't boot regular and I can't enter DIAGS Mode so I think I did something very stupid I didn't notice or something went not as expected.
Thanks in advance
Patrick
P.S. sorry for my bad english. It's not my main language. |
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.
*) File errors;
A sign that your eMMC chip (the "flash") is nearly dead.
Once it finishes using up its spare "erase blocks" it will be time for a new chip.
*) "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.
*) 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" )
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.
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.)