Quote:
Originally Posted by patrick9
Hello there,
I have a Kobo Aura H20 which is running the latest Start Menu with nightly builds of KOreader.
I am normally usig Koreader for my daily reading, but I have just noticed that Nickel will not start up at all... KOreader and the Start Menu are still running fine.
When I select Nickel on Start Menu, it starts to boot up, seeing the five squares where it hangs for a few seconds and then resets itself. Sometime booting back to Start Menu, sometimes back again into attempting to start Nickel.
What does this mean? Is this what's called "bricked"? How would I be able to restore it without being able to boot into Nickel?
Thank you for any help, as it's a bit worrying...
Many thanks,
Patrick
|
You say that the device is sometimes booting to KSM, and sometimes to nickel. Are you aware that KSM by default starts nickel if you do not select any menu entry in the first 20 or so seconds after booting? Is it possible that this is what you are seeing? (By default the device boots every second time to KSM, and every other time to nickel. But I guess you changed this setting already. Right?)
A potential cause for problems is that KSM uses fmon to communicate with nickel. Did you follow this part of the install instructions?
Quote:
|
check that all images (exit_nickel.png, switchtokoreader.png, etc.) are listed in the library and their thumbnails are displayed there, and at least once as tiles on the home screen. Only then proceed to step two.
|
If you did not do this (or maybe not completely; or if the database was recreated since then), there could arise a situation that nickel cannot start. But usually this would not lead to rebooting the device, but only to falling back to KSM. You could anyway try to start nickel by a different way:
- select tools > nickel divers.msh > start nickel without fmon.sh
(this is possibly not the exact wording, but you will find the relevant entries; I do not have my device with me, so I cannot verify the wording.)
If this starts nickel, then open exit_nickel.png, switchtokoreader.png, etc. and then power off the device (you cannot return to KSM in this situation directly). Next time you should be able to start nickel the regular way.
If you cannot start nickel in the way just mentioned, than there is a different problem unrelated to the pngs. When nickel hangs for a certain amount of time for some reason, the device gets rebooted. For instance, a corrupted database can cause nickel to hang. You could check the integrity of the database with a database tool on your pc, or you can also do it by selecting
- tools > nickel divers.msh > check db integrity.sh (or similar)