This was a default backup dealing with a non multiboot situation, non power kernel. I had hoped and presumed, that if your decided to restore in case of emergency, you would use you own backup. That's why I asked to you start with making a backup of your own with backup menu. The link referred to by others, was to describe a theoretical situation to restore without USB. This must be the current situation (Fabry has mostly mentioned it): - In nand you probably have 2.6.28.10-power49 (from the former situation) - On rootfs you now have backup menu and the default kernel 2.6.28-omap1 libraries. No multiboot images in /boot, because that imagefile has no multiboot. Backup menu is the first thing started when keyboard open, so I can imagine it tries to load. It could be the former multiboot situation gives some trouble. Backup menu was not made with multiboot in mind (the creator of backupmenu did't like the concept of multiboot at all, but it could be easly adapted for multiboot). Pressing the "r" for restore during the backup/bootmenu will probably not react... I am sorry to see that the technical explanation in http://talk.maemo.org/showpost.php?p...5&postcount=21 did not end up in the right choice. When you later asked if the image from the link would overwrite the kernel (http://talk.maemo.org/showpost.php?p...8&postcount=23) I could honestly say no, because it doesn't. I did not expect you where actually gonna use this images for a restore (causing a mismatch), but only mentioned it to described a fictive situation to point out the kernel overwrite. Again, I feel very bad about the whole situation. I was under the impression the situation was clear and in any case, you would start with making a backup of your own device to be restored in case of emergency.