[tshering]

Originally Posted by trekk

I tested this on a Glo. The menu installs fine, I can tap various menu entries, which will be highlighted then. Nothing else happens.

As the Pinhole procedure or other ways for a factory reset won't work, I'm kind of stuck now with a useless device. I've bravely taken the risk, but sadly no award for me

Edit: If the device is turned off, it still shows the menu. If you tap the screen, no menu entry will be highlighted. Make sure the device is turned off, hold the light button, while pushing and holding the power button. This will cause a factory reset. In my case the device only resets, while pressing the buttons during a startup. This was a fast debricking!

Would it not be nice if we could make the start menu run on Glo with FW 3.2.0?
I cannot figure out what is happening here. Therefore, I would appreciate any help. Maybe, I should shortly explain how the menu works. Generally speaking, there is an executable file, kobomenu, that takes a number of arguments. When started, kobomenu displays these arguments in a list. If the user pokes on a list item, kobomenu echos the text of the selected item, and quits.
In the rcS file, kobomenu is called with every loop in a while do-done block. Each time kobomenu quits, the echoed value is read into a variable and based on its content some command or other is executed.

  while [ "$selection" != "EXIT" ]; do
    selection=$(kobomenu $moptions) # read the text echoed by kobomenu into selection
    case $selection in
      # execute some commands depending on the content of selection
      ...

    esac
  done

On the Glo, however, nothing seems to get executed, even so kobomenu seems to register the touch input. At the moment, I can think of two possibilities what could be happening here.
1) kobomenu echos the correct values, but does not quit. Therefore, the script does not continue at this point and the value is never read into selection, ....
2) kobomenu does quit, but it does not echo an expected value. Therefore, no command is executed and the while loop continues for ever.

In order to find out something more about it, you, brave owner of a Glo, could run a test (Be aware that there is alway a risk in testing!). If you like,

1) install FW 3.2.0
2) install KBStartMenu_03check.zip (previous post)

• after installation the Glo will show the behaviour reported by trekk
• slide the power slider to the right and hold it there for 20 seconds in order to force a power off
• after powering on, nickel will be started (if things go as planned)
• connect via usb to PC and replace .kobo/kbmenu/kobomenu.sh with the file provided in this post (unzip it first from the archive). Maybe you should preserve a copy of the original kobomenu.sh for later use.
• power circle
• now the menu gets started; poke several times on different menu entries
• force a power off, then power on again; now nickel should be running
• find the file .kobo\kbmenu\txt\seltest01.txt and post it here

3) restore your Glo to a usable reader; there a two options
3.1) (option 1) change in .kobo\kbmenu\runsettings.txt the line

runmenu=alternateMenu

to

runmenu=never

(and restore the original kobomenu.sh, if you like)
With this option, you are prepared to easily run further test in near future.
3.2) (option 2) copy uninstall\KoboRoot_3.2.0\KoboRoot.tgz to kobo.

Note: In certain situations, you cannot see on the screen whether the device is powered off or not. Sometimes powering off needs even more than 20 seconds, be patient. If for some unexpected reason your device gets totally unresponsive, do a factory reset (before that, however, you must power off).