[TouchPad General] cvcduty:
Hi.

First, a disclaimer... I will not be responsible for you messing this up and bricking your device. I am only outlining a guide which I figured out and used to get my TP setup the way I wanted. DO NOT come to me for support, as I am not a dev and really have no time to save anyone from their doom...

I used RootExplorer (Paid App -

https://market.android.com/details?...sImNvbS5zcGVlZHNvZnR3YXJlLnJvb3RleHBsb3JlciJd) to do the steps outlined below. You may use any file manager of your choice, granted that it gives you root access with read/write access to /boot folder. Please make sure you backup anything you plan on changing by making copies and moving them to a safe location... Don't way I did not warn you... ^_^

With that said... I hope this helps some one... ^_^

I have just figured this thing out and soon after noticed that there is a thread with a video showing the methods to remove the extra UImage from the moboot boot menu.

The video shown here http://xdaforums.com/showthread.php?t=1511050 is a great way to remove the redundant UImages from the list except I figured out a easier method and also a way to choose the default OS (WebOS or CM or CN) to load when TP boots, which the video does not get into.

Once I updated to the latest CM9 V2, I rebooted and my TP wanted to boot into the Bricked_Kernel which I did not want. I would, in this case as many of you, scroll (within 3 seconds) to the right entry to boot or else, I would be needing to reboot again.

So here is what I did.

Boot into your Rom (CM9 in my case)

Install RootExplorer from the market.

Launch RootExplorer. You will be asked to grant SU. Press Yes.

Navigate into /boot folder.

Click on the Mount R/W. This will change to Mount R/O. Now you have read and write (important) access to the contents of this folder.

Find the entry UImage.Bricked_Kernel (It might be UImage.ClassicNerd or something else).

Long press the UImage you want to delete (or modify).

Delete (rename, if you want to keep it for some reason) the UImage of the old kernel

Click on the Mount R/O to set the folder for read only access before you exit.

Now when you reboot, you will notice that the MoBoot menu is missing the entry for the extra kernel that was there before. The problem now is that the default boot selection has been set to WebOS. This is because the device is looking for the missing default entry in the boot menu. So it's just going to the top of the list. If this is what you want, you can stop here but if this is not the OS you want to load by default, follow the next few steps.

Launch RootExplorer

Navigate into /boot

Click on the Mount R/W to set write access.

Find the entry moboot.default

Long press moboot.default and choose Open in Test Editor.

The entry in this text file will show the OS that MoBoot will choose to load by default. Mine had an entry "Bricked_Kernel"

Delete the entry in this file and retype the OS of your choice. Mine was "CyanogenMod" (without the "").

Exit. You will be told that RootExplorer made a moboot.default.bak was created for safety. If you are using other file explorers you might not get the automatic backup. So please make a back up of this file before you change the entry.

Click Mount R/O to set the permissions to read only before exiting.

Reboot.

Now you will see that the MoBoot has the right OS as the default OS.

For those of you that desire to make the WebOS as the default OS you can type WebOS in the moboot.default. Well, good luck.

PLEASE DO NOT CHANGE FILES IN THE /BOOT IF YOU ARE NOT SURE WHAT YOU ARE DOING!!! Only follow this guide if you are comfortable doing so!!!