Boot Manager Official Manual

New Video Tutorial!



If you are having trouble installing a ROM try opening settings and forcing large boot.img! More about this here

Boot Manager REQUIRES Root & S-OFF!

Background Knowledge

About the application

Boot Manager is Android's first multi-booter application. It allows you to boot up to 5 ROMs on your phone and switch between them with just a reboot. Each ROM is completely separate in that they all have their own filesystems and all data is preserved on each ROM so it's like having 5 different phones.

About the Devs

Team Init 2 Winit Apps includes GFlam from DroidForums.net and Conap from forum.xda-developers.com. We are both self taught Android developers who love to do the impossible, and create original never before done applications such as Boot Manager and Boot RANDimations.

Conap-started developing rom's for the Droid Eris with his line of CELB rom's and kernels at XDAForums as well as working on some previous dual booting projects for android and eventually moved on to coding apps for android. He is self taught through the power of Google search and by day works in Law Enforcement for the State of Delaware.

GFlam-started as a themer at Droid Forums but soon moved on to code by deving a ROM known as Sourcery along with Eagle1967 and later moving on to applications. He is currently a student at the University of Delaware and studying finance with future dreams of going to law school.

Contact informations

Devs Names: GFlam and Conap
Forum: http://forum.init2winitapps.com
Email: support@init2winitapps.com
Twitter: @init2winitapps
Website: http://init2winitapps.com

What boot manager actually does

Boot Manager does not touch anything on your phone, and never will, all of the real magic happens on your sdcard. When installing a ROM you must select the checkboxes within the application to wipe data, cache, and system, however, these wipes will not wipe your phone your phones data will not be touched. The application will wipe the imgs that are made on your sdcard leaving all of your data on your sdcard and phone untouched. The application allows you to boot from your sdcard or in other words when you boot an sd rom you are actually running from your Sdcard and not the phone. This can cause lag for some which is easily fixed by overclocking and letting things settle in, which a reboot usually greatly helps improves speeds. A higher class sdcard may also help and we recommend a class 6 or above but it's not required.

How the application works

The application works by creating imgs of your different partitions on your sdcard which allows us to boot ROMs from your sdcard without wiping your card or phone. The different imgs are basically the same thing as your phones partitions data, system, and cache it all works the same so your sdcard ROMs run the same as your phone ROM everything you can do on your phone ROM you should be able to do from SD ROMs.

Getting Started

Setting up your phone rom

Non 2nd Init Devices

Setting up your phone ROM is very important and you will be bugged about it until you do it. What this does is creates a boot.img of your phone ROM so that you can boot back to it from Sd ROMs. It also lets you boot back to it if your sd ROM install didn't go as planned. To boot it manually reboot ro recovery and browse to /sdcard/BootManager/phoneRom and apply the update.zip there and then reboot and you will be brought back to your phone ROM and all your data will be fine.

2nd Init Devices
Before you continue please see the device specific information for 2nd Init Devices below by clicking here
Basically the same thing as the non 2nd init devices as it is run the same the only difference is your boot.img is not backed up due to the locked boot loader. Instead a hijack-boot zip will be placed on your sdcard in place of the boot.img. This zip will act the same way however allowing you to get back to your phone rom as the boot.img does. If an install doesn't go as planned and you can still boot recovery you can also manually boot our slots by browsing to /sdcard/BootManager/phoneRom and applying the update.zip there.

When you change your phone ROM it is important to set your phone ROM up again!!!
To set up your phone ROM select the button Setup Phone ROM from the main activity. Once it is done you will get a dialog telling you about a succesful backup of your boot.img this should only take a few seconds to do no longer than 30 seconds.

Installing your first ROM to your sdcard

After setting up your phone ROM you are good to get your first ROM installed to your Sdcard. Open the application select the top button to install a zip and select the ROM of your choice from your Sdcard. You will then be brought to the install screen for installing a ROM you MUST select all three checkboxes to wipe. These check boxes will not wipe your phone, none of your data will be touched only the imgs the app makes will be wiped not your phone.
Once your install is finished you should install the google apps since the application requires the market in order to check your license. If you forgot to install your google apps or for some reason can't boot your Sdcard ROM, fear not just reboot to recovery and flash the update.zip at /sdcard/BootManager/phoneROM/update.zip and you will be able to reboot back to your phones ROM and all of your data etc will be there.

Installing addons (gapps, kernels, themes etc)

Installing addons such as gapps, kernels, themes etc is done basically the same way you install a ROM. Each update zip is installed the same except for kernels. If you want to install a kernel scroll down to the next paragraph
To install an addon (themes, updates, gapps) select Install Zip from the main screen and browse to the addon you wish to install and press it. You will then be brought to the installer screen this time DO NOT select any of the wipes, unless the dev told you to wipe something while installing it. Then select the slot you wish to install it to. So lets say I've installed cm7 to slot one and now wish to install the google apps to this I would not select any of the wipes and press slot 1. It will ask you if you want to overwrite the slot confirm this and install it over the slot. The installation will run as a ROM install does and once done congrats you've installed an addon to your SD ROM!

Installing Kernels-kernels have a separate installer which many people overlook. To install a kernel you do basically the same thing as an addon, however, after selecting your kernel select the fifth button on the install screen which reads "Install Kernel." A dialog will then display asking which slot to install it to. Using the previous example lets say I still have cm7 installed to slot 1 and want to install a new kernel to it, I would select slot 1 in the dialog and confirm the install. It will then run as a normal install and when finished the ROM will have a new kernel.

Restoring Nandroid's to Slot

An option that was introduced in V2.0 was the ability to restore nandroid's to your sd slots. To do this select the button Manage Installed ROMs from the main screen and then select Restore Nandroid to SD. You will then be brought to a list of all of the items on your sdcard. Browse to the location of the nandroid you wish to install and press it. You will then be shown a dialog asking if you want to restore the nandroid, select okay. Next you will be brought to a screen listing your four slots select the slot you wish to restore to and confirm. Then select the ext you wish to use and the process will begin to run as an install does. Once finished congrats you've just restored a nandroid to an sd slot.

Backup ROM Slots

You can not do nandroids through recovery for sdcard slots it will not work but within the app you can do the equivilent of an nandroid by selecting the button that reads "Manage Installed ROMs." Then select the first button Backup ROM Slots, select your slot to back up and let it do it's thing. This works just as a nandroid does for your sd slots. All data will be presevered and must be restored from the application as well (not recovery). Backups must be restored however to their original slot they can not be restored to other slots.

Advanced Options & Info

Ext2 vs Ext4 support

Ext 4 may allow for faster speeds but is not supported on all devices. If Ext4 doesn't work for you try Ext2 as it's supported on a lot more devices. Ext4 and ext2 are very similar, however, ext4 doesn't include journaling like ext2, thus you may experience faster speeds using this.

Forcing Large Boot.img

A new feature in Boot Manager as of V3.1 is a smaller boot.img by default. This smaller boot.img will help many devices boot a lot more ROMs, however, some devices such as the Droid Incredible 2 and Thunderbolt need to use the large boot.img and is as of V3.2. If you're device is not booting ROMs go to settings and select force large boot.img it should then work if it wasn't before. If you need more help feel free to contact us.

Sdcard ROM Lag & Fixes

Sdcard ROMs may lag this is easily fixed by overclocking and allowing things to settle in. A reboot usually helps a lot to settle things in so it's recommended if you're lagging a lot to reboot and your lag should disappear for good. Once things are settled in and you're over clocked your lag should go away completely and run as smooth as your phone ROM does. If you still are lagging you may want to consider buying an Sdcard of a higher class we recommend a card of a class of 6 or above but this is not required.

SD Booster Info

The SD Booster option was added in V2.1 and has been shown to significantly reduce lag.
SD Booster Originally from BrainMaster at xda

Alright so lets cut to the chase by answering a few questions
Q. What does the SD Booster do?
A. The SD Booster adjusts your cache read size which basically means it creates a pool for read cache so that files are retreived quicker.
Q. Can this hurt my SD card?
A. Definately not because like Stated in the first question the booster doesn't affect any of the data because it doesn't work with the SD's data it just creates a smaller or larger memory pool where files will be stored for quicker access.
Q. What's the best size for my SD?
A. There is no clear cut answer for that, it depends on your sdcard and device. Some ballpark guesses though include the following, a class 2 card (512kb, 1024kb, 2048kb), class 4 card (1024kb, 2048kb, 3072kb) class 6 card (2048kb, 3072kb, 4096kb) and a class 10 card (3072kb, 4096kb, 5120kb). These numbers may not work well for you though so we recommend you play with the numbers a little yourself. The best for me on my class 2 card is 512kb so sometimes bigger isn't always better since it could strain the card if you go to high and slow it down more.

Install time and how to speed it up

For phones with larger imgs such as the thunderbolt which has monsterous imgs at about 3gbs your first install may take a while due to the sheer size of the imgs your phone needs to create. What you can do though after your first install is copy the imgs to the other slots and then just overwrite them. This can cut your time down dramatically.

Understanding what the app does

Alright now that you've just installed a ROM to your sdcard lets take a little time to quickly explain what just happened. The app created a few files on your sdcard in the slot you installed to they include the data, system, boot, and cache imgs, an update.zip and a name file. The data.img system.img and cache.img are your different file systems which is where all your data for your sdcard ROMs is kept. The boot.img is like the brains of the sdrom it tells the phone what to use and when flashed tells the phone to use that specific slot as the rom, mounting the correct imgs etc. The name file is just the name of the ROM so the app knows what to call the slot, and the update.zip is your fail safe. If you for some reason are stuck on a ROM, maybe you forgot to install the google apps and can't open the app or maybe your ROM didn't boot etc you can reboot to recovery and select the update.zip in whatever slot you want including your phone ROM. This will flash the slots boot.img and get you back up and running.

Device Specific Tips & Troubleshooting

Motorola Droid 1 (sholes)

This device requires clockworkmod to switch between the ROMs without user interface. Unfortunately Motorola had the droid 1's boot loader more secure than HTC did and wouldn't let us flash boot.imgs live, so it requires a reboot to recovery to flash it. If you do not want to use clockworkmod you can just install the update.zip manually. It takes half a second to install the zip, just browse to the slot you want and apply the update.zip the path to the slots is /sdcard/BootManager

Wifi issues V1.0 and V1.2 please see this post at droid forums for sd rom wifi fix WiFi Fix for droid 1

HTC Incredible 1 (incs)

No real special instructions other than you have the option to install ROMs to your eMMc which might be quicker than your sdcard you can choose where it installs to from the settings.

HTC Thunderbolt (mecha)

Install Time-The install time for the thunderbolt is long unfortunately due to your large imgs which are around 3gbs total. This can take some time to do but once you have one install the time is dramatically cut. Your first install may take some time but what you can do after you install once is copy the data, system, and cache imgs over to the other slots and then just select to wipe system, data, and cache with the check boxes and overwrite the imgs. This will cut your time down dramatically.

Radios and connection-your ROMs use different radios between gingerbread and froyo this unfortunately is a phone limitation for you guys and we can't do anything about it. You will need different radios for gingerbread and froyo slots so you will have data only on one of them unless you flash the radio manually. Apparently MR2+ radios however work on both gingerbread and froyo but this has not yet been confirmed since neither of us own a thunderbolt.

2nd Init Devices

V2.2 added a few 2nd init devices those being the Droid X and the Droid 2 these devices function for the most part the same as any other device however there are a few little differences. First you MUST be running a 2nd Init ROM with the gingerbread kernel(Currently CM7 or MIUI or OMFGB)--Must be the gingerbread kernel versions of these ROM's.
You can't use Droid X or Droid 2 Bootstrap recovery. You must use the recovery that comes with CM or the 2nd init recovery through ROM Manager (For D2 you want the recovery used for 2nd init ROM's such as CM7 gingerbread).
Although the phone ROM must be a 2nd init ROM you can run your favorite non 2nd init ROMs on the sdcard. The sd ROM's will need to use the gingerbread kernel though in order to work since that's the kernel that will be installed on your phone.
There is also a failsafe written in, if you install a ROM and it does not boot then pull your battery and reboot your phone. Boot Manager will always boot to recovery from the sd ROMs so if the ROM goes far enough to initalize the init scripts then it will write the file to get you back to clockworkmod recovery. This will save you from a lot of sbf's. Booting from one rom to another will skip recovery but rebooting the phone normally will go to recovery if your on an sd rom. If you need to reboot the phone when it goes to recovery just choose reboot phone from there and it will boot back to the ROM.
If you do need to sbf for whatever reason it will not effect the sd ROMs you have already installed sbf will only affect your phone ROM.
For a list of booting and non-booting ROMs see this post on our forum
2nd Init Specific Information for Boot Manager

More Information

Helpful Tips

V2.1 introduced the ability to keep your screen on during installs (in the settings). If you have a profile to underclock your device when your screen is off we recommend you turn this option on in settings to keep your screen on during installs. This will speed the process up and having the screen off could potentially cause issues in some cases.

Finally if at first you don't succeed try try and try again some ROMs may not work due to their dev doing something funky or you may just have had a bad install for some crazy reason. If you continue to have issues view the contact info below and get in touch with us and we'll be happy to help you with any issues.

Thank you from the devs

Thank you for all the downloads and continued support, as well as the many nice comments and emails we've received. We really love doing this stuff and hearing from you guys makes it all the better. We thank you for the downloads and all the help we've received in the past.

Conclusion

That's all there is to Boot Manager, if you still have any questions feel free to send us an email and congratulations if you actually read through this all you are now an expert on Boot Manager and how it works :)