@ncik:

Yup...I encountered that as well when I was learning how to install Ubiboot.

That's why in the "TIPS" under the "Install Nemo Mobile OS" section (#5) I mentioned NOT to turn on the device yet until you finish the rest of the steps...because the latter part of the Wiki talks about the "bzImage" of Nemo and how to go about it.

@death_jax

Hm..."bzImage" to be saved in the /boot folder of the Nemo partition...that I did not do, since there is already a file named "bzImage" in that location when I checked it; it is a symlink that points to a file named "vmlinuz-2.6.32.20130129.1-n950".

What I did is (as I have written in the Wiki):

1. I took a look at the properties of the "bzImage" file that is located in /boot of the Nemo partition and found out that it is a "symlink" (symbolic link) that points to a file named "vmlinuz-2.6.32.20130129.1-n950", which is also already there (in /boot of Nemo partition). I never got Nemo to boot up (turns off after turning on, or reboot loop).

2. So I took that "vmlinuz-2.6.32.20130129.1-n950" file and copy-pasted it to the /boot folder of the N9 root partition (not the /boot folder that we created inside the N9 "MyDocs" partition), and then renamed it as "bzImage".

3. That was the only time I got to resolve the "reboot loop" or "not booting/turning off" problem whenever I tried to use Nemo.

These steps are documented in the Wiki as "FINAL STEPS" under the section of "Flash the Device with Ubiboot-02".

The nice thing about Ubiboot is, you don't have to start from scratch. While the device is turned off, plug the USB cable to the computer. The device will turn on in "maintenance mode" and (if you are using a Linux-based OS), all the partitions will be mounted (i.e. your File Manager will fire up, showing the partitions). Once that happens, copy-paste the files as indicated in the Wiki.

The only exception is that if you failed to extract the "preinits.tar" file prior. I read all the IRC logs and in one of those conversations, extraction of the "preinits.tar" file needs to happen at the earlier part of the process. So that is what I have followed.

By the way, I documented the steps in such a way that it conforms to how the author (juiceme) already designed the "ubiboot.conf" file so as to lessen the number of things that a user would need to do (example: I wrote the steps such that "zImage" would be renamed to be spelled the same way as it was in the ubiboot.conf file, e.g. "zImage_e-yes_nitdroid+l2fix"...under "NITDroid Files"section).

Hopefully this allows more end-users to be able to install Ubiboot with the least amount of trouble, as long as they follow the steps in the order it was written in the Wiki. Of course, more experienced users can afford to alter the order of steps as they know what they are doing (editing ubiboot.conf, etc.). I targeted the Wiki/guide to end-users so as to gain patronage of Ubiboot.