Related
Hey there, I have a question which seems to have been addressed at http://forum.xda-developers.com/showthread.php?t=1256708 , but would like to confirm: can I create an app partition on my SD card without having anything other than a stock ROM on my Desire? They seem to have done it simply with a rooted device...mine is not rooted, would I have to root it? If so, would that be it?
Thanks in advance for any advice!
You need root to use sd-ext partition. Not really sure, but I think you can't use any way of a2sd (meaning apps 2 sd-ext, not the "official" a2sd, that moves apps to fat32 sd) with stock ROM.
You need to flash a custom ROM, and if you want something as "stock rom but with a2sd" install SuperNova, or any other ROM from droidzone.
You also have lots of different options, with a higher ustomization, very different from HTC Desire stock ROMs, with Sense 2.1, 3.0. 3.5, or AOSP (without Sense) etc.
I see...thanks a lot for the info, Supernova seems to be my best bet, I want a ROM that is essentially unchanged so that I won't have bugs, etc.
Blackhawk is right, to be able to use a2sd (to sd-ext) you require root and a folder called init.d in the system partition which is not present in stock roms.
Sent from my HTC Original Desire with Beats Audio using Tapatalk
what if??
what if i were rooted, and created that folder in the system folder, would it then be possible to do this on stock 2.3.3??
i practically fell in love with not ever seeing that damn low phone memory notification, and now i switched back to a stock rom because of the 2.3.3 update for my lg
edit: so your saying there is no system partition in stock "ROMs"? only in custom roms? im quiet confused when it comes to factory ROMs because ive never really messed with them, i normally only used it a a fallback if i mess anything up beyond control
---------- Post added at 07:59 PM ---------- Previous post was at 07:09 PM ----------
i went to the previously mentioned thread and and basically re-asked the question, i am trying to get one solitary answer from both parties before i go messing with anything lol
once again thanks
ShawnnKushh said:
what if i were rooted, and created that folder in the system folder, would it then be possible to do this on stock 2.3.3??
i practically fell in love with not ever seeing that damn low phone memory notification, and now i switched back to a stock rom because of the 2.3.3 update for my lg
edit: so your saying there is no system partition in stock "ROMs"? only in custom roms? im quiet confused when it comes to factory ROMs because ive never really messed with them, i normally only used it a a fallback if i mess anything up
Click to expand...
Click to collapse
No. Even if you created it in the system partition, you will also need to have a modified boot.img than enables the usage of the init.d folder which is provided by all roms that uses that folder. Or you can search if anyone has hacked the boot.img to support it.
The system partition is just a protected sector of the NAND memory that stores all of the system files. It is present even in stock roms.
Sent from my HTC Original Desire with Beats Audio using Tapatalk
How to Dual Boot Multiple ROMs on Your Android Phone
Whether you want to test out a new ROM for daily use or just keep an eye on one that's being developed, you can run multiple ROMs on your rooted Android phone with BootManager, and pick which one to use when you start it up.
Having multiple ROMs to choose from is great, but flashing and re-flashing new ROMs just to try them out is annoying. If you want to try one out but don't want to fully flash it over your current ROM, BootManager will let you flash it (and up to three others) to your SD card, so you can try multiple ROMs at once. The ROMs you run from your SD card won't be quite as fast, and not every ROM out there will work, but it should give you a chance to try out most other ROMs without fully flashing them.
Right now the app is officially supported on the original Motorola Droid, Droid Incredible, HTC Thunderbolt, HTC Vision, HTC EVO 4G, HTC Inspire 4G, HTC Desire, and the HTC Desire HD. It may work on other phones, though, they just aren't officially supported yet.
Note: This tutorial contains some pretty advanced stuff, and i don't recommend it if you're unfamiliar with rooting and flashing ROMs. If you're just starting out, check out how to root your Android phone and how to flash Android ROMs before moving onto something like this.
Step One: Flash a Second ROM
Before you do anything, make a nandroid backup of your current ROM with ROM Manager or through your recovery module. If anything goes wrong, you can always restore from this backup to get things back to the way they were.
To set up BootManager, just download and install it from the Market, and start it up. You'll also want to grab a ROM of your choice and save the zip file on your SD card.
When you first start up BootManager, it'll prompt you to back up your boot.img, which you should do before installing any ROMs. Once you've done that, head to "Install ROMs". Pick the zip file from your SD card containing the ROM you want to flash, and check all three boxes: Wipe System, Wipe Data, and Wipe Cache. Let it do its thing (which will take awhile). When you're done, it will give you the option of booting into your new ROM. Hit Done; we aren't ready to boot into it just yet.
Step Two: Install Google Apps and Other ROM Add-Ons
Most ROMs don't come with Google's copyrighted apps, like Gmail, the Market, and others. This is a problem, since when you boot into your new ROM you need BootManager to function if you ever want to boot out of it, and it won't work unless you're signed into the Android Market. Luckily, there's an easy fix (note: if you know your ROM comes with Google Apps installed, you can skip this step).
Download the Google Apps zip file for the ROM you just installed and go back to BootManager. Hit Install ROMs. This time, pick Google Apps' zip file, and use the same slot that you used in step one. Leave all three "wipe" boxes unchecked this time. When it's done, booting into that slot will take you to the original ROM, but with the Google apps installed.
If you want to install a theme or other zip-based mod in the future, you can do that using this method too. Just remember: if you're flashing a new ROM, check all three "wipe" boxes, but if you're just installing an add-on to a ROM, don't check any of them.
Step Three: Switch Between ROMs
To boot into one of your other ROMs, just head into BootManager and choose "Boot Installed ROM". It'll show you a list of ROMs you have installed on your device, and after choosing one of them it will reboot into that ROM. BootManager will come installed on each of your other ROMs as well, and as long as you're signed into the Android Market on that ROM, you can boot into it from there as well and switch back to your main ROM.
That's it! You can flash up to five ROMs at a time, so you'll never be bored by one measly operating system. Hit the link to download BootManager.
BootManager is a $2.99 download for Android 2.1 and up. See the Market page below for officially supported devices.
https://play.google.com/store/apps/details?id=com.drx2.bootmanager&feature=search_result#?t=W251bGwsMSwxLDEsImNvbS5kcngyLmJvb3RtYW5hZ2VyIl0. (Theres a lite and pro version )
Found this app in the sensation forums and found it was officially supported on DZ
great job!! studying...
Great post. THNX
Sent from my SK17i using xda app-developers app
sweet deal, think i'll try this out. any major bugs, in your experience?
That's neat, any chance of conflicts when it comes to data on swap/sd-ext/sdcard ?
Isn't this post supposed to be located in "G2 and Desire Z Themes and Apps"?
You are actually just recommending an app and providing information that is already available on http://www.init2winitapps.com/
Sent from my HTC Vision using xda app-developers app
Cool stuff! Thanks for sharing! Wonder if this is the step to go for booting other Mobile Linux Distros like MeeGo!
When will be available this app with support for sony phones?
Sent from my SK17i using xda app-developers app
I've already test on my desire z and this don't work, when i want to reboot on my seconde rom my phone freeze on the boot image (just before the boot animation) I don't know if i'm not wait enough time but I wait 8 minutes !! and i've juste the boot splash !! I had to go by the bootloaderand after by the recovery for restored my phone
But Thanks a lot It's a very good idee to make a tuto
Does anyone have any ICS roms working with this?
i highly doubt most ROMs would work with this, especially ICS roms... it's just too good to be true, and the app needs a lot of refinement.
Yeah I downloaded the light version and the only ROM I could get working was the JoyOS port. I tried Andromadus Mimicry, MIUIv4, G2Slim, and some others I don't remember and they didn't work.
Sent from my HTC Vision using xda app-developers app
raydar670 said:
Yeah I downloaded the light version and the only ROM I could get working was the JoyOS port. I tried Andromadus Mimicry, MIUIv4, G2Slim, and some others I don't remember and they didn't work.
Click to expand...
Click to collapse
I've used this app off-and-on for months. Couple things to note. It won't work on G2/DZ unless you set the large boot setting. Also, some ROMs just don't seem to like it. Most ROMs can be made to work by installing normally, doing a nandroid then installing the nandroid to the boot manager pseudo-partition. Even that way, I've had some ROMs that wouldn't boot.
I definitely used it for ICS (Andromadus and CM9/unnoffical, I think) before I committed to DD with ICS.
GinoAMelone said:
I've used this app off-and-on for months. Couple things to note. It won't work on G2/DZ unless you set the large boot setting. Also, some ROMs just don't seem to like it. Most ROMs can be made to work by installing normally, doing a nandroid then installing the nandroid to the boot manager pseudo-partition. Even that way, I've had some ROMs that wouldn't boot.
I definitely used it for ICS (Andromadus and CM9/unnoffical, I think) before I committed to DD with ICS.
Click to expand...
Click to collapse
I have tried the large boot setting for all those ROMs but not the nandroid yet, maybe I'll try that later.
Anybody got this working? saw on the google play store there are a lot of apps that don't support samsung unfortunately because of the way things are partitioned.
What apps don't support Samsung?
Sent from my GT-N7105 using xda app-developers app
If by dual boot you mean booting two roms its not working on the note II yet AFAIK. Here is the progress thread http://forum.xda-developers.com/showthread.php?t=2153211&highlight=dual
mrevankyle said:
If by dual boot you mean booting two roms its not working on the note II yet AFAIK. Here is the progress thread http://forum.xda-developers.com/showthread.php?t=2153211&highlight=dual
Click to expand...
Click to collapse
That is correct, having 2 roms in memory and being able to switch between the two, with ease.
I saw that someone already had it working via Aroma on the Original Galaxy note.
BigBison420 said:
That is correct, having 2 roms in memory and being able to switch between the two, with ease.
I saw that someone already had it working via Aroma on the Original Galaxy note.
Click to expand...
Click to collapse
Ya k that's what i thought. You cant do that yet on the Note II but it is being worked on
mrevankyle said:
Ya k that's what i thought. You cant do that yet on the Note II but it is being worked on
Click to expand...
Click to collapse
Just figured I would give a "bump" to this Q&A since this dual-booting Samsung & AOSP is working well at this point. There are a few caveats and I am compiling a FAQ on just this topic. DerTeufel's thread is here and the OP references my FAQ > http://forum.xda-developers.com/showthread.php?t=2239453
Nand secondary?
RichMD said:
Just figured I would give a "bump" to this Q&A since this dual-booting Samsung & AOSP is working well at this point. There are a few caveats and I am compiling a FAQ on just this topic. DerTeufel's thread is here and the OP references my FAQ > http://forum.xda-developers.com/showthread.php?t=2239453
Click to expand...
Click to collapse
That would be nice, because I can't figure out how this DB recovery works. I have 2 ROMs on my phone right now. I appear to be able to do anything I want to my primary ROM, but I cannot figure out how to back-up my secondary.
The DB recovery is a useful idea. I have a custom 4.2.2 as primary and a sammy 4.1.2 as secondary. Both ROMs work was expected. Primary does not have to have devil kernel, but I believe secondary needs it in order to survive.
I am still new at this DB recovery thing. Has anyone figured out how to nand the secondary ROM? I have noticed that I can flash TWRP and I don't lose either ROM, as long as I DO NOT factory reset. I just have to flash DB Recovery again to access the other ROM. I have also noticed that some data is shared between the two ROMs. Robo TD shares the same back-up file on sdcard0, which is delightful
Today I am going to try a dirtly ROM flash on primary. Wish me luck.
floykoe said:
That would be nice, because I can't figure out how this DB recovery works. I have 2 ROMs on my phone right now. I appear to be able to do anything I want to my primary ROM, but I cannot figure out how to back-up my secondary.
The DB recovery is a useful idea. I have a custom 4.2.2 as primary and a sammy 4.1.2 as secondary. Both ROMs work was expected. Primary does not have to have devil kernel, but I believe secondary needs it in order to survive.
I am still new at this DB recovery thing. Has anyone figured out how to nand the secondary ROM? I have noticed that I can flash TWRP and I don't lose either ROM, as long as I DO NOT factory reset. I just have to flash DB Recovery again to access the other ROM. I have also noticed that some data is shared between the two ROMs. Robo TD shares the same back-up file on sdcard0, which is delightful
Today I am going to try a dirtly ROM flash on primary. Wish me luck.
Click to expand...
Click to collapse
The kernel is "shared" between them. If you flash another ROM to primary, it replaces the dual boot kernel. You are correct that the other ROM is not affected but other kernels can not boot the secondary ROM which is stored in a custom location. Creating a nandroid of (or restoring to) the secondary partition only requires you to go into the dual-boot selection and choose "enable secondary". Then all commands such as factory reset, bacup, restore, wipe cache, etc pertain to the secondary ROM until you reboot or reload recovery. You could choose backup and when it completes you coul go into dual-boot again and select "enable primary". Then all the commands would pertain to the primary ROM - again until you reboot or reload recovery.
Sent from my BNTV600 using Tapatalk 2
RichMD said:
The kernel is "shared" between them. If you flash another ROM to primary, it replaces the dual boot kernel. You are correct that the other ROM is not affected but other kernels can not boot the secondary ROM which is stored in a custom location. Creating a nandroid of (or restoring to) the secondary partition only requires you to go into the dual-boot selection and choose "enable secondary". Then all commands such as factory reset, bacup, restore, wipe cache, etc pertain to the secondary ROM until you reboot or reload recovery. You could choose backup and when it completes you coul go into dual-boot again and select "enable primary". Then all the commands would pertain to the primary ROM - again until you reboot or reload recovery.
Sent from my BNTV600 using Tapatalk 2
Click to expand...
Click to collapse
This is all very interesting and essential information to those of us trying to figure out this DB Recovery system. I suspect this is yet the tip of the iceberg.
So, with a DB set-up, both ROMs need to be installed with the Devil Kernel. For instance, Primary is installed first with Devil in place, then the same for secondary (or vice-verse), because you can't install a ROM with no kernel; but it turns into one kernel in the end. Is this correct? Only one kernel can exist with DB system. If secondary has devil and primary has trinity, secondary is (&cked. In other words, you still only have a single boot system with a secondary ROM installed that has no recovery capabilities.
OK, assuming that all that is correct (or at least parts of it), you get a big fat thank you.
Now earn another. Do both ROMs (sharing the same kernel) have to also share the same governor, I/O, clock, and voltage settings? Custom can handle more than sammy and different ROMs like different settings.
floykoe said:
This is all very interesting and essential information to those of us trying to figure out this DB Recovery system. I suspect this is yet the tip of the iceberg.
So, with a DB set-up, both ROMs need to be installed with the Devil Kernel. For instance, Primary is installed first with Devil in place, then the same for secondary (or vice-verse), because you can't install a ROM with no kernel; but it turns into one kernel in the end. Is this correct? Only one kernel can exist with DB system. If secondary has devil and primary has trinity, secondary is (&cked. In other words, you still only have a single boot system with a secondary ROM installed that has no recovery capabilities.
OK, assuming that all that is correct (or at least parts of it), you get a big fat thank you.
Now earn another. Do both ROMs (sharing the same kernel) have to also share the same governor, I/O, clock, and voltage settings? Custom can handle more than sammy and different ROMs like different settings.
Click to expand...
Click to collapse
I can post a more detailed answer later on today. However, the phone will always only have one kernel. When your phone boots up the kernel is loaded first. At that point, if you have the dual boot kernel, it has the capability to boot one or the other ROM. The secondary ROM is stored in a separate location on the internal SD card. If you flash a new ROM to either the primary or secondary partition, it will replace the kernel. At that point, both ROMs are still okay, but whatever the new kernel is, it can only boot the primary rom. Additionally, if you flashed directly to the secondary rom and the new kernel is not compatible ( AOSP vs. TW) with the pre-existing primary rom, you must flash the dual boot kernel again or the primary rom will not boot up properly. If you flashed to the primary rom, you don't technically need to reflash the dual boot kernel until you want to be able to boot up the secondary ROM again.
Sent from my GT-N7105 using Tapatalk 4 Beta
What if you were to delete the second rom off the internal or is there a way that it can be corrupted causing the phone not to boot after the primary kernel? can an ODIN restore to stock fix this (since it will repartition for only one boot)
As far as I know, not near enough Galaxy s3 owners are taking advantage of this amazing utility. It allows you to install multiple ROMs on your device without having to wipe the one you already have. I currently have 5 ROMs on my phone ranging from touchwiz to Cyanogenmod, Lollipop to Jelly Bean. It's very versatile and guess what!
It was recently updated to work with Lollipop ROMs! You can install any ROM you want as a secondary ROM and test to see if it works as a daily driver! No more getting scared about a brick or bootloop because a simple REBOOT switches you to your primary ROM!!
I constantly switch between CM ROMs for fluidity, Lollipop ROMs for cutting edge features, and TouchWiz ROMs to unleash the full potential of the camera, as well as get all those TouchWiz features like WiFi calling! You can flash any ROM, test experimental builds and flash any kind of ROM you want all without wiping the ones you already have! Unlimited ROMs!(space permitting)
Now, it may not be as simple as ROM manager for Nexus devices but it's pretty darn easy. here's the steps:
Flash MultiBoot Recovery(based on twrp 2.8.3.0)
Go to Advanced>
MultiBoot>
Create ROM>
Set ROM(to what you created)>
"Flash the ROM and gapps just like any other">
Set ROM>
Boot ROM(Click on one you just created)>
A menu will pop up saying Boot ROM!
There. You are done. I can boot into recovery and boot a ROM in a matter of seconds. Slimkat, SlimLP, CM11, CM12, TouchWiz 4.1.2, 4.3, 4.4.2, PAC ROM, any of them!
I just want more people to take advantage of this wonderful feat of developer genius!!! I feel like only have of the phones potential is had without this amazing recovery. Now that it is updated to allow Lollipop ROMs, it is too hard to keep it in.
Head over to development, it should be on the first page and try it! Alternately search for "Multiboot" and look for the thread.
All credits go to @Phil_Suz for being an amazing god.
but my question to you is, do you have to wipe out the current rom? and then do the process? or can you keep the current ROM? if so that would be awesome.
ALso another question.. if I am on 4.4.2 TW, can i still install lollipop as a multiboot rom with out having to wipe out my current rom (TW 4.4.2 Likewise S5)?
YPG70 said:
but my question to you is, do you have to wipe out the current rom? and then do the process? or can you keep the current ROM? if so that would be awesome.
ALso another question.. if I am on 4.4.2 TW, can i still install lollipop as a multiboot rom with out having to wipe out my current rom (TW 4.4.2 Likewise S5)?
Click to expand...
Click to collapse
You don't have to wipe your main ROM at all! It is just a recovery, and each secondary ROM is like a whole different device on your sdcard, you just have to switch to it it's amazing let me tell you. Your primary ROM, kernel, modem etc will not be affected at all until you decide to change it, which you just do like any other ROM (just be careful formatting because that will delete the multiboot folder on root of phone). If you flash another ROM and it doesn't boot, just reboot the phone to your main ROM and or go to recovery and try again you can create and delete ROM's as much as you please and even set up how much space you want to make the different parts of the ROM take on your sdcard (data, system, cache). Flash the multi boot recovery, read how to use it and you're golden there's also a video someone made of how to use it. If you don't like multiboot just flash another recovery and reboot the recovery. You won't lose anything unless you created an additional ROM or ROMs.
Can you give me instructions on how to do this properly? The video is a bit confusing. I understand how to create a new rom. I am just a bit lost, on how to switch to my current ROM, or set it up.
This is true its useful... for those who could figure out what to do at right times.
not only that but other carriers have it baked into the kernels for simply a reboot option.
we have more complicated version yet out phones are not bootlocked. if more people got tmobile phones I am sure they would have worked these issues out by now.
I certainly have taken advantage of this. Alternate between your favorite roms with ease.
reminds me of safestrap, which i used on my droid4, and appears to be available for some flavors of the SGS4 and some galaxy Notes. it also uses twrp. think of it as creating partitions on your PC - you make a partition for each Rom - they were called ROM Slots in safestrap - make a given slot active, then flash the rom and whatever else you want as you normaly would right there in twrp. if something breaks or you find a showstopper bug or just need to switch roms, simply reboot into recovery, change which rom is "active" and then exit - it loads the rom you just selected. it was great on my droid4 since gps and camera were both kinda buggy in almost any custom rom, and i was nervous not having it on my galaxy relay, but it worked out. it'll be nice to have on the sgs3, especially since I want to try out some L roms.
here's the thread for the multiboot recovery, so nobody else has to search for it:
http://forum.xda-developers.com/showthread.php?t=2646528
Running Verizon Pixel XL with Resurrection Remix at the moment but I don't care which rom I run.
I have some apps I want to run that I need to be unrooted to use, hiding root from them doesn't work even passing safety net. I want to be able to switch to slot b to be able to boot into the rom with a stock kernel that can pass safety net. If I am reading correctly, the 2nd slot needs its own separate rom flashed to work, even if its the same rom as slot a, but I like many others am confused if that is correct.
Do I need to flash an entire rom to slot B to have an unrooted 2nd option?
I think that for all the post I have read, this SLOT stuff do not work as a dual boot partition, when you installed custom ROM, you wipe system and data..??,because data shares both slots..Also when you flash a stock ROM on slot B to have an unrooted partiton, you are going to loose ROOT and TWRP on the other one, ..
Glsoto said:
I think that for all the post I have read, this SLOT stuff do not work as a dual boot partition, when you installed custom ROM, you wipe system and data..??,because data shares both slots..Also when you flash a stock ROM on slot B to have an unrooted partiton, you are going to loose ROOT and TWRP on the other one, ..
Click to expand...
Click to collapse
I have ran stock rooted in slot a and stock unrooted on b and had twrp on both slots just fine. I never tried a custom ROM and stock together.
sfetaz said:
Running Verizon Pixel XL with Resurrection Remix at the moment but I don't care which rom I run.
I have some apps I want to run that I need to be unrooted to use, hiding root from them doesn't work even passing safety net. I want to be able to switch to slot b to be able to boot into the rom with a stock kernel that can pass safety net. If I am reading correctly, the 2nd slot needs its own separate rom flashed to work, even if its the same rom as slot a, but I like many others am confused if that is correct.
Do I need to flash an entire rom to slot B to have an unrooted 2nd option?
Click to expand...
Click to collapse
Basically you have to flash the same rom on both partitions, and then root one while leaving the other unrooted, but if you try 2 different roms you'll have issues, at least I did. Also would suggest a custom kernel as that has the bootloader patches for things like Android pay.