November 10, 2013 By: Will Verduzco
A little under a year ago, we talked about a rather unique multiboot solution available for the Google Nexus 7 (2012). The tool, which was developed by XDA Recognized Developer Tasssadar, differed from most other multiboot solutions available on other devices because it streamlined the process and requires no modification of your device’s bootloader or existing /system partition. It did, however, require modification to the /data partition, but things were still more civilized than most other multiboot solutions due to the integrated installer app.
Now, Tasssadar’s MultiROM solution has been extended to also support the Nexus 4 and Nexus 7 (2013). Just as before, the main staple of MultiROM is its ability to allow you to boot into any number of Android ROMs. In addition to adding support for the two new devices, however, MultiROM has undergone a whole host of improvements over the last year.
For starters, MultiROM now allows you to restore from an existing Nandroid backup for use as a secondary ROM. This is an extremely practical feature because it allows you to make a backup of your existing ROM and transfer it to the secondary installation so that you can objectively compare results when flashing modifications.
Tasssadar has also removed one of the key limitations from last year’s release. Before, all ROMs had to be installed on internal memory. This presented somewhat of a challenge to many since modern Nexus devices lack external SD card expansion slots. Now, MultiROM allows you to use a USB-OTG cable and connected USB storage to house the ROMs off of device storage.
To get started, visit the appropriate thread below:
[Thanks to Tasssadar and Nikwen for the heads up!]
The Samsung Galaxy S Plus GT-I9001 is the lesser known cousin of the original Galaxy S GT-I9000 smartphone.While virtually indistinguishable from the I9000 from the outside, the devices are vastly different on the inside: For starters, the I9001 swaps out the 1 GHz Hummingbird processor for a 1.4 GHz Snapdragon S2.
While the hardware received somewhat of an upgrade compared to the original Galaxy S, there is a bit less aftermarket development available for the S Plus. Now, however, a major gap has been crossed, thanks to XDA Recognized Developer educk and Senior Member h0rn3t. The developer was able to get dual boot functioning on the device.
Educk and horn3t’s solution comes in the form of an application and compatible kernel that is able to switch between your ROM installations once the ROMs are installed in the manner specified by the developer. There are, however, a few requirements and restrictions that must be met before getting up and running. For starters, the main ROM has to be an AOSP-derived ROM based on Android 2.3.6 or above. This is installed on internal storage. The secondary ROM is then installed on your SD-EXT partition, and it must be Android 4.1.2 or greater.
If you’ve wanted to experiment with a newer ROM but didn’t want to leave behind your old Gingerbread installation, now may be the time to do it. To get started, head over to the original thread.
[Many thanks to XDA Senior Member mrjraider for the tip!]
Dual booting on a device, be it a phone or tablet, brings forth some pretty substantial benefits. In addition to simultaneously and effortlessly switching between two ROMs, you also no longer have to wipe everything in order to try a new one. This, in and of itself, allows for more fun and experimentation to be had. After seeing dual boot on the Note 2, it was only a matter of time before something similar would pop up on the Galaxy S 4.
Thanks to the initiative of XDA Senior Member Grarak, a mod has been created that allows you to dual boot ROMs without having to wipe any data or make any backups. The primary ROM must be stock TouchWiz, while any AOSP-based ROM can fill in the second spot. By default, you should be running the Perseus Kernel, which the aforementioned Note 2 owners may be familiar with. However, this can be changed later. As explained by Grarak, the method is reliant on the mod switching between the two kernels that you will have installed.
It can’t be said that the initial setup of the dual boot method is a particularly easy process. However, it is relatively straightforward, and most folks wouldn’t experience much trouble when following the instructions posted. The mod is still in alpha stage, but Grarak is claiming that it is stable enough for everyday use.
If you’ve been looking to dual boot on your Galaxy S 4, head over to the development thread for more information and discussion.
Now that we’re in the latter half of 2013, it seems that the majority of the tech world has left older devices in the dust. With a plethora of new devices from various manufacturers, more devices are coming our way before the year’s close. Along with this, previous devices are being pushed further and further back into the archives. So it’s wonderful to see that this is certainly not the case for a few aged devices, as we have seen previously with the (almost) entire Xperia line of 2011.
Now we can add the HTC Pico to the list, as XDA Recognized Contributors -JohnCarter- and -NickHalden- have discovered a method to dual boot two ROMs on the 2011 device. The method largely consists of creating three SD-EXT partitions. This allows you to have two ROMS, a primary and a secondary, installed at the same time. Switching ROMs can be done with a simple custom app developed by Recognized Contributor galaxyfreak, and no data wipe or backup is required.
As of now, CyanogenMod Beta 6 is the only rom that can be installed as the primary ROM, while the secondary ROM can include any that does not use SD-EXT partitions, such as CM 9, CM 10, and stock firmware.
If you are interested in dual booting on your HTC Pico or are curious about the development, check out the original thread for more information.
Got yourself a Galaxy Tab 2 7″ P31xx and not satisfied with running just one build of Android on it? Want to dabble into custom ROMs like CyanogenMod 10, but don’t want to lose the stock ROM at the same time? XDA Member Macadamia Daze has found a way to dual-boot two Android builds on this tablet.
This dual boot method runs one Android build from the internal memory and the other from the SD card. Before you begin, you must have an 8GB or higher capacity SD card, though 16GB or more is recommended. Also note that the ROM you are running from the SD card has to be prepared to run that way. Fortunately, the developer has provided the latest CM10 nightly already prepped for the purpose, along with instructions on how to prep any ROM of your choice for booting from the SD card. For more details and the complete guide, head over to the forum thread and enjoy dual-booting two Android ROMs on your tablet!
Also, if you have yet to root their Galaxy Tab 2 7.0, we have already featured the rooting instructions for this device as well.
March 2, 2012 By: ElCondor
Perhaps you remember the days of the very first Android ports to Windows Mobile phones such as the HTC Touch Diamond and HTC HD2. Beside the fact that this groundbreaking development was one of the factors that ultimately led to the end of Windows Mobile development on XDA, it did bring some innovative features to the table. Dual boot for example. It was revolutionary to be able to choose between Android and Windows Mobile. After a few months, when people started to move to newer phones, and this innovation ultimately got buried under the huge
mess mass of development for Android phones.
It seems there is currently only limited active development for a dualboot system for native Android phones. There have been projects in the past, for example for the Samsung Galaxy S II, Droid Eris, Xperia Play and LG GT540, but it seems development is more focused on individual ROMs nowadays. Multi-device development – and yes, we use the word development a lot – is more and more subject to development on individual devices. In the past, developers collaborated to put together something great (Ervius Visual Kitchen, anyone?). The Android port to Windows Mobile, called XDANDROID, and the dual boot innovation are just few of the many examples of this.
Although it isn’t a bad thing that developers have a strong focus at individual ROM development, we probably all share the dreams of being able to boot into a clean, battery-saving and light-weight Ice Cream Sandwich ROM while also having the option to boot into another ROM, one that might be an experimental ROM or a ROM that is more focused on performance. Or any other combination. The open-source Android OS allows for many dramatic changes to be made to its structure, dualboot on Android has been proven to work on the Droid Eris, so why hasn’t development started yet? Why seems development of such innovative systems at a standstill? I say we fire up that innovation engine as soon as possible.
February 7, 2012 By: Ian Stacy
Every time we publish a story about the mods and developments on the Nook Color, it makes me seriously wonder if the Barnes and Noble people knew what was possible with the little ebook reader they were selling.
XDA Senior Member racks11479 has updated his multi-boot images for the Barnes and Noble Nook Color to include an SD image with both Gingerbread and Ice Cream Sandwich. Since the ICS build is semi-unstable and he still needed access to Gingerbread, racks11479 created this dual boot image for use on an SD card rather than the internal eMMC.
Following the SD versions release he put together a flashable version for the adventurous. Building the SD card requires the use of a partition manager and an image burner, but that’s a small price to pay to protect your devices precious eMMC.
If you decide to flash to your internal memory then, as usual, you take your devices future into your own hands. Check out the thread here to try it yourself and be sure to thank racks11479 for another great contribution to the Nook Color world!