Quote:
Originally Posted by DeGodefroi
How badly bricked?
And how did you solve it then? Is it irreversible? Or can you fix it anyway?
|
Just got it up again. ( ..a lot of hardware design/work... ) And now I have a lot of questions, as I don't know how I solved it !? (..errors in nodes, cluster size, etc. Have to investigate partial dumps, etc. ) Anyway, somehow I got the latest version to update Duokan, and this caused Amazon to do an update/refresh of the filesystem. ( some of my errors had to do with updates in /etc )
I will add one of my many questions - ( see attached picture ) - can anyone explain what happens if you do a reset ? ( is there any recovery partition ? ) ( got the screen shown here by reset+home, on another kindle )
Added this later:
1st: got something kicked in Duokan.....
2nd: kicked some "tinyroot" crawling the filesystem, after something like this:
https://www.mobileread.com/forums/sho...d.php?t=113362
Uncompressing Linux.....
...and 7 lines down
Press [ENTER] for recovery menu...
( enter opens the I,O,E,U,Q - menu )[ got myself out of there..Q]
Someplace there was a menu for Uboot, with lots of options..
( sorry for the incoherency.....)
Added info:
I have come across this bug-report:
http://bugs.gentoo.org/show_bug.cgi?id=82106
Same results and believe the missing characters is tied to this. Test something more..