Develop Bugs

[Guide] Install double boot CM7 + CM9

Here's a simple guide for CM7 users, to install CM9 as a test rom AND keep their CM7 ROM as a main ROM​
EDIT (01/04/2012):Guide updated according to new versions of multiboot. Also works for CM10!
DUE TO KERNEL INCOMPATIBILITIES, MY GUIDE IS FOR PEOPLE WHO INSTALL CM9 +CM7 WITH THE SAME KERNEL. (EX: CM7 FROYO KERN + QUARX CM9 FOR FROYO KERN)
This guide is tested and approved on froyo kernels.
First: I suggest you backup your rom before doing anything, but there's no danger don't worry
first download and simply place on your SD-Card these files:
m11kkaa's multiboot:
http://forum.xda-developers.com/showthread.php?t=1364659
This will allow us to lauch our main ROM normaly, and when we want to, launch our 2nd rom (which will be CM9 =D)​
Epsylon3's or Quark's latest version of CM9:
http://defy.wdscript.fr/
Or
http://quarx2k.ru/
Google Apps (optional):
http://goo-inside.me/gapps
Place all 2/3 zips on SD-card.
Download 3filesystem images that will be your virtual partitions for CM9 on Sdcard:
www.mediafire.com/?vvkmy2tx4yeg32m
extract them, and place all 3 of them under /multiboot/CM9 in SDcard
You can also use the app called multibootmanager to do this
Warning: these partitions have size limits (300mb each). Don't run out of space!
People who know how to can create their own partitions, any size they want, threads exist for that
Here are the instructions:
DO NEVER WIPE DATA DURING PROCESS, IT IS NOT NEEDED
1) Go into Bootmenu
2) Choose "recovery ->" to go to the recovery choice menu
3) MAKE SURE you have:
"Custom Recovery" OR "Latest Recovery"
"Stable Recovery"
"Stock Recovery"
4) Choose "Stable Recovery"
6) Install Zip from SD-Card: multiboot_vXXXX.zip
7) REBOOT SYSTEM NOW
8) When you get the blue led, press Vol. Down, you will be in the Bootmenu.
-Choose boot->Set Default->2nd-init
-Go back once
-choose [2nd-system] to boot into the 2nd system menu.
- Here is where you will be able to select 2nd roms to boot. If you put the files on the SDcard in the right place (see above), you should see them in the menu. Other choices are "boot from nand","recovery" or "reboot".
- Choose Recovery(CWM), and then select which rom you want to apply the modifications (CM9). You will now reboot into a recovery for your virtual system.
9) a) Install zip from sdcard: CM9!!! =D
9)b) (OPTIONNAL): install google apps
10) Wipe cache and dalvik cache and then reboot system.
11) Done! reboot. If you want to launch CM9 just press Vol. Down on blue led, boot into 2nd system like above and select CM8 to boot it.
Booting any virtual ROM will take a few minutes, sd cards are slower, and this will be first boot.​
Enjoy Epsilon's, Quark's, m11kkaa's and walter79's great work!​
Originally Posted by m11kkaa
Some info:
- After installation, The recoveries under the 2nd system multiboot menu is for your virtual system and "Stable Recovery" for your real system
- you can restore any backup or install any zip in "Lastest Recovery" and it will go into your virtual system
- boot the virtual system with the 2ndsystem-option in bootmenu
Click to expand...
Click to collapse
Tutorial video made by Yamandude:
http://youtu.be/aqdQSusw2zw
If one day you don't want CM9 again, simply remove the folder /fsimages/ from your SDcard.
I suggest you keep them in case, you may change your mind one day
You now have double boot, and CM7, and CM9 on your same phone!!!!

Troubleshooting:​
My main ROM works, but i get a bootloop with CM9
In latest recovery: wipe cache + Dalvik cache. If you still get a bootloop then wipe data too. ​

Are u shore u flash multiboot from custo/latest recov?
I always do it from stable recov!
Sent from my MB525 using xda premium

It IS from custom and NOT latest recovery (step 4). Your "guide" is incorrect and if you ask me, makes things even more complicated than they are...sorry.
In what way is this needed amyway?; there's already a multi-boot thread.
No warning about NOT wiping data in latest recovery...Nothing about the size and limits of the 3 image files...

[] AL [] said:
It IS from custom and NOT latest recovery (step 4). Your "guide" is incorrect and if you ask me, makes things even more complicated than they are...sorry.
In what way is this needed amyway?; there's already a multi-boot thread.
No warning about NOT wiping data in latest recovery...Nothing about the size and limits of the 3 image files...
Click to expand...
Click to collapse
"Custom recovery" as we know today used to be called "latest recovery" a few months ago. The name changed so i mentionned both names in case people get confused if i say only one and they see the other. What is important is checking if you have three recoveries, not the way you call them.
Seen as CM9 is for test purposes, i doubt that warning not to install to much apps on the Second ROM is very relevant. Even though i will take into account your comment
Sent from my 1Ghz CM7 Defy

nogoodusername said:
Are u shore u flash multiboot from custo/latest recov?
I always do it from stable recov!
Click to expand...
Click to collapse
If you flash multiboot.zip in the stable mod, you'll change mount settings for your 2nd init partition, and then it will be your main rom that will load from sdcard. I tried this and unfortunately my main com became CM9, and it is not what we want ^^.
Sent from my MB525 using xda premium
Sent from my 1Ghz CM7 Defy

In fact, my bad: I meant "stable" not custom. m11kkaa multiboot is to be installed in stable recovery and never in latest.
Never wipe data in latest recovery or android secure will be erased and your main boot apps will stop working.
There are incompatibilities between some roms: MSGinger will not work with ics..
...OP need some work to say the least...
Here:
[] AL [] said:
QUOTE=twa_priv;19863273]I think that's exactly what most people here are doing. Look at AL's post (http://forum.xda-developers.com/showpost.php?p=19814199&postcount=280) which is the one that got me started using multiboot.
Click to expand...
Click to collapse
Yes thanks. He might also be interested in reading this one and this one as well on this.
Edit:
And i don't know about wajkiui, but there's is a problem with MSGinger though; so be warned!
Just give it a shot anyway... but if there was ever a reason to make a nandroid backup of your current build before jumping into something, I think multiboot calls for it...
L.E.: and while I think about it: one drawback I've noticed from multiboot is that once you boot back into your main rom, the battery stats are screwed up (or to the state they were when you left for the 2nd-boot). So give your phone a nice long charge to fix this or don't complain about eventual steep battery drop...[/QUOTE]

crakeron said:
If you flash multiboot.zip in the stable mod, you'll change mount settings for your 2nd init partition, and then it will be your main rom that will load from sdcard. I tried this and unfortunately my main com became CM9, and it is not what we want ^^.
Sent from my MB525 using xda premium
Sent from my 1Ghz CM7 Defy
Click to expand...
Click to collapse
That is incorrect...that's how I did (and others and how m11kkaa's instructions were at first _ I believe) and CM7 IS my main boot and ics my 2nd boot. And multiboot zip most probably can be install with both when you think about it. It's ICS that you absolutely need to install in latest/custom recovery... that was my last comment here good luck with this thread.

[] AL [] said:
That is incorrect...that's how I did (and others and how m11kkaa's instructions were at first _ I believe) and CM7 IS my main boot and ics my 2nd boot. And multiboot zip most probably can be install with both when you think about it. It's ICS that you absolutely need to install in latest/custom recovery... that was my last comment here good luck with this thread.
Click to expand...
Click to collapse
Yeah i've just re-done it all by flashing the multiboot in stable recovery, both work you're right ^^
Sent from my 1Ghz CM7 Defy

Great guide. Thanks.
Sent from my MB525 using XDA App

and how to uninstall 2nd boot now?
Screwed my Cyanogen 7.1: cannot run any external keyboard, language is always English after reboot.

tvg said:
and how to uninstall 2nd boot now?
Screwed my Cyanogen 7.1: cannot run any external keyboard, language is always English after reboot.
Click to expand...
Click to collapse
I wouldn't bother with uninstalling the multiboot function. But if you don't want to use your 2nd rom anymore simply take the /fsimages/ folder of your sdcard.
If one day you change your mind, copy them back . Multiboot may go away if you change anything to do with bootmenu in your main ROM (CM7).
Remember: if you don't want the 2nd Boot anymore, simply take the partitions under /fsimages/ off your card
P.S. You should have a chat with epsylon and m11kkaa about the issues you mentionned
royale1223 said:
Great guide. Thanks.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Your welcome =)

I tested CM9 and deleted /fsimages.
I reflashed many times using SBF, fixed SBF, omg, at least ten times.
And my CM7 (a new instance) does not save the language I choose after a reboot.
And any keyboard except the built-in one also hangs (The application has stopped etc).
Help, I need to fix it back =( I just cannot understand why I reflashed all the things thoroughly and still I can't get just the normal CM7 back =(
---------- Post added at 12:59 AM ---------- Previous post was at 12:58 AM ----------
crakeron said:
P.S. You should have a chat with epsylon and m11kkaa about the issues you mentionned
Click to expand...
Click to collapse
Thank you, I will try...

10x for detail Explanation; Can I translate this and post into Korean forum?

CM9现在还不成熟，系统也有bug吧

Motivateme said:
10x for detail Explanation; Can I translate this and post into Korean forum?
Click to expand...
Click to collapse
Sure feel free . Put a little link to this thread somewhere as a source and you can
Sent from my 1Ghz CM7 Defy

tvg said:
I tested CM9 and deleted /fsimages.
I reflashed many times using SBF, fixed SBF, omg, at least ten times.
And my CM7 (a new instance) does not save the language I choose after a reboot.
And any keyboard except the built-in one also hangs (The application has stopped etc).
Help, I need to fix it back =( I just cannot understand why I reflashed all the things thoroughly and still I can't get just the normal CM7 back =(
---------- Post added at 12:59 AM ---------- Previous post was at 12:58 AM ----------
Thank you, I will try...
Click to expand...
Click to collapse
Did you backup before starting any of the instructions as i suggested? It's a wierd issue you have there =/ ....are you sure it has nothing to do with settings you may have changed? What do the dev's say about it?
Sent from my 1Ghz CM7 Defy

jejeje thanks for your tutorial, now maybe if I can install it without problems

lenidas said:
jejeje thanks for your tutorial, now maybe if I can install it without problems
Click to expand...
Click to collapse
How did it go?

I tried to install it, but no luck. After reboot I am stuck on Cyanogoogle logo forever... Wonder what could be wrong?

[KERNEL]DualBoot - Devil4.2 (04-Feb-2013)

Attention! Before installing this kernel, read carefully (don't forget reading post 2!)!
1.) Make a Nandroid!
2.) If you are installing this kernel the first time, it wipes your data and system! (this is caused by creating the secondary system partition) - you can restore your nandroid afterwards
3.) Make sure to have 700 mb free space at your internal sdcard (this is needed for secondary data)
4.) You can't install a rom as secondary rom, without doing some work yourself! This is caused by the way, rom installing is mounting the system partition. I can't do anything against it (What you need to do is written in the guide of post 2)
5.) You only can install 4.2.1 roms, with the "default"/cm partition layout!
6.) You have to install the kernel again, after you have installed a new rom. If you forget to install it, you just boot up to primary rom.
Many thanks to:
- cm team, especially pawitp
- stratosk
- mialwe
- zachariasmaladroid
- kasper_h
- krarvind
- kufikugel
- gokhanmoral (great idea to build a dualboot kernel, always helpful)
- Bejda
- sUsH667 ( i have taken his design for aroma filemanager, it's looking great)
- amarullz ( who coded the filemanager)
- ...

About this kernel (and installing it):
installing a dualboot kernel the first time:
1.) the kernel needs to create a secondary system partiton. this is taking place at the current /data partition.
b) the new version (04-Feb.) is creating an addional "devil" partition of 20 mb. it currently isn't used, but i am preparing already for later (boot.img is limited to 7.5 mb in size because of the boot partition size), because the dualboot kernel needs to include more files as the stock one, and for 4.1.2 support, i even need to include more...
2.) by installing the kernel the first time, data and system get deleted due to the partition change.
3.) as a security feature, the install fails the first time, before your data gets formated. if your install fails, you still can make a nandroid, if you didn't before. then just install again. this time the install does not fail. the kernel reboots to recovery automatically now
4.) install the kernel a third time
5.) before installing a new rom, go to advancend, reboot recovery
6.) after installing a rom (primary or secondary), flash the kernel again, follow the steps below for this!
updating the dual boot kernel to a newer version/installing the kernel after a rom flash:
1.) flash the kernel
2.) reboot to recovery (just in case...)
how to revert the partition changes:
there also is a "revert" kernel now, which is available here:
http://rootaxbox.no-ip.org/derteufel/jellybean4.2.x/
if one isn't using the dualboot kernel, the "revert" kernel doesn't revert anything, but is a normal single boot kernel, with the same features as the dualboot one.
if one is flashing reset kernel after dualboot, you need to flash it three times. the first install just fails. the second one succeds and reboots to recovery. the third one finishes the restore.
The reset kernel wipes data and system, (only) if coming from dualboot kernel!
in the recovery:
1.) by default, there is no entry for system and data in the fstab. i have done this, to ensure you don't install apps/packages to the wrong rom. this means, if you just go to install zip, install fails, because there is no system partition which can be mounted.
2.) the dualboot menu. what do these options do?
a) the first two options are mounting primary/secondary filesystem right after clicking.
b) these two options are preparing for mounting primary/secondary filesystem after you reboot to recovery. without using this, you don't have the options in recovery, to mount/format data or system, etc
3.) reboot primary/secondary system should be clear
how to install a rom as primary/secondary rom:
1a ) remove spaces from filename!
1b )install zip from sdcard
2.) choose from where to install
3.) choose what and where to install
note: the kernel installs itself after the rom. no need to reflash. this does not work with elite rom (because of the zip design)
How to create/restore a nandroid:
1.) go to dual boot menu
2.) select "enable mounting of pri. fs" or select "enable mounting of sec. fs"
3.) reboot to recovery
4.) backup or restore your nandroid, depending on your previous choise, you'll backup/restore the primary or secondary system
5.) consider to rename your backup, to something like primary_date or secondary_date
here you get the kernel. nothing else needed:
http://rootaxbox.no-ip.org/derteufel/dualboot/

Going to try it out
Enviado desde mi GT-I9000 usando Tapatalk 2

Where is the link
Sent from my GT-I9000 using xda premium

WOW great work derteufel
thanks a lot

WOW... Just wow!

almost all files uploaded/added now
a dualboot version of hellybean is currently uploading

thanks dev :good:
will give it a try ! ...

will you compile a kernel without dualboot for JB4.2.1???
Gesendet von meinem GT-I9000 mit Tapatalk 2

Awesome. Cant wait to try this. I remember a long time ago i mentioned it in your kernel thread.
Still following your work actually, but got stuck on CM all this time. Now can be on both! Nice.
So how does one boot into 1st or 2nd rom? By button combo? Dont see it mentioned.
Considering second donation :thumbup:

WOW WOW WOW WOW !!! DUAL BOOT ON OUR GALAXY S!!! FANTASTIC!!!! someone tested it???
sorry for my bad english

jelle2503 said:
Awesome. Cant wait to try this. I remember a long time ago i mentioned it in your kernel thread.
Still following your work actually, but got stuck on CM all this time. Now can be on both! Nice.
So how does one boot into 1st or 2nd rom? By button combo? Dont see it mentioned.
Considering second donation :thumbup:
Click to expand...
Click to collapse
Also, when do we need to flash the kernel again? When we install the main rom, or every time when we install a rom, even if its primary or secondary.

I am scared
Sent from my GT-I9000 using XDA Premium HD app

Perfect timing and choices DerTeufel,that guy:
DerTeufel1980 said:
- sUsH667 ( i have taken his design for aroma filemanager, it's looking great)
Click to expand...
Click to collapse
Keeps telling me i have to test Slim beta 2

Trak-X said:
Also, when do we need to flash the kernel again? When we install the main rom, or every time when we install a rom, even if its primary or secondary.
Click to expand...
Click to collapse
you have to flash the kernel everytime you install a rom, because every rom flashes a kernel. as this is implemented in the rom update script, i can't avoid it.

Terrible.... I am without voice!

There is no need to edit the primary ROM, is it?
Sent from my GT-I9000 using Tapatalk 2

So i flashed Dual Kernel (2 times as expected,error 7 first).
Advanced>reboot recovery> dual boot menu and all is here.
I mount secondary filesystem and flash the edited Slim beta2.
Reflash the dual kernel but it only boot in recovery.
If i don't flash dual kernel after Slim install it is stuck at semaphore boot image.
I have 1g free on sd,don't know what i'm missing,i think i'll download again edited slim beta2..don't know but its install seems too fast in cwm (i know it's Slim but hey,it's fast lol).

I love you DerTeufel.
Good Job.
Amazing<3
Gesendet von meinem GT-I9000 mit Tapatalk 2

Bejda said:
So i flashed Dual Kernel (2 times as expected,error 7 first).
Advanced>reboot recovery> dual boot menu and all is here.
I mount secondary filesystem and flash the edited Slim beta2.
Reflash the dual kernel but it only boot in recovery.
If i don't flash dual kernel after Slim install it is stuck at semaphore boot image.
I have 1g free on sd,don't know what i'm missing,i think i'll download again edited slim beta2..don't know but its install seems too fast in cwm (i know it's Slim but hey,it's fast lol).
Click to expand...
Click to collapse
This should not happen. Could you please flash the kernel a third time.
If the install fails like it does the first time, secondary system did not get created
Gesendet von meinem GT-I9000 mit Tapatalk 2

Note 2 - Dual BOOT Roms

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)

[Guide/Development/Info/Discussion][GEE] Multiboot for the Sprint Optimus G!

This was being discussed in the unofficial CM11 thread, So I thought I would give it a home.
Here is the thread for; Development, Discussion, Information, and Also A guide on how to Multiboot different ROMs on the LG optimus G.
Code:
I in no way made this MOD,
all the rights and credit go to the original creators.
I Just wanted to give an area and help other people learn how to do this.
I (Or the Creators of this mod) are NOT responsible for anything bad happening after flashing this MOD;
Bricks, Soft Bricks, Explosions, Implosions, Girlfriend leaving you after trying to boot too many roms.
YOU choose what YOU do to your 700$ Device. Now Lets get to the Guide. :)
Before you do ANYTHING, Be sure to read this over many, many times. If you do NOT know what you are doing, do NOT try this. Enjoy. :good:
This is how I multi boot, using a backup.
1st: To multiboot, please be rooted.
2nd: Please Flash the Custom TWRP Multiboot recovery. (Link Below)
2½ (Optional, but still preferred.): If you plan on multibooting a 4.2+ ROM, I would make an "0" (Zero) folder and moving all precious things there. (So that your backup will go there and you can also see your download folder.)
3rd: Make A backup of whatever ROM you are on in that recovery, and as you will see if you reboot, the backup in be in the "0" directory. (I prefer stock as my ROM to backup.)
4th: Flash the Multiboot.zip (Link Below)
5th: Now Wipe as normal like if you installing another ROM. and Set whatever ROM you want as your primary ROM.
6th: In Recovery, go to advanced> add ROM
7th: click next then choose backup as 2nd ROM.
8th: Let it do its thing, and guess what?
Enjoy Multi booting.
This is how to Multiboot with a .zip. (results may vary)
1st: To multiboot, please be rooted.
2nd: Please Flash the Custom TWRP Multiboot recovery. (Link Below)
2½ (Optional, but still preferred.): If you plan on multibooting a 4.2+ ROM, I would make an "0" (Zero) folder and moving all precious things there. (So that your backup will go there and you can also see your download folder.)
3rd: Make A backup of whatever ROM you are on in that recovery, and as you will see if you reboot, the backup in be in the "0" directory. (I prefer stock as my ROM to backup.)
4th: Flash the Multiboot.zip (Link Below)
5th: Make sure you have primary ROM. You don't need to edit this if you want to keep it
To change primary ROM before adding new ones, wipe as normal and setup/backup etc.
6th: In Recovery, go to advanced> add ROM
7th: click next then choose .zip file of ROM as 2nd ROM.
8th: Let it do its thing, and guess what?
Enjoy Multi booting.
Helpful Quotes:
dopy25 said:
If you are on the ls970 sprint Optimus make sure to use the geehrc4G and not the geespr versions in the google drive. I know it might not make much sense but they work and they were edited by gearslam to flash pretty much any rom for the ls970 or gee.
Go to twrp, advanced, multiboot, add rom, then follow the prompts. I prefer to use the do not share kernel option. After that you can choose to install a rom from zip. Then the next boot you can choose which one to boot into.
If you want to add stuff, IE; change kernel or flash another zip to that rom (GAPPS) just go to advanced, multirom, list roms, then select the rom you want and you can choose a normal option such as flash zip, wipe data, wipe dalvik, wipe cache. It's all there once you select list roms.
Click to expand...
Click to collapse
gearslam said:
You need to install the TWRP-2.7.0_MR_geehrc.zip Recovery and then flash the multirom-20140409-v22-UNOFFICIAL-geehrc.zip
In TWRP under Advanced There is a MultiROM option. You can use a TWRP Backup or a ROM ZIP.
I'm currently running both Stock and Unoffical CM11 without any problems on the Sprint LS970.
Click to expand...
Click to collapse
gearslam said:
I just wanted to point out for those that don't know. OTG is working good in this recovery. I've been using a 16Gig flash drive formated to exfat. All you need is an OTG-Y cable. You can easily backup/restore and flash ROM's from USB drive. Another alternative to sideloading if you accidently wipe everything out.
Click to expand...
Click to collapse
gearslam said:
I patched the recovery and multirom zips so geespr roms can be flashed and EFS backups can be made. I used Unoffical CM11 as my primary ROM and a TWRP backup of the stock based ROM as a boot option. You can flash different kernels on the primary ROM not sure about the secondary, etc. Anytime you flash a new Kernel, you have to go into advanced ->multirom and there is an option to inject multirom into boot.img
The secondary ROM's and there Data are stored in /data/media/0/multirom/...
The patched recovery and multirom are in my google drive: https://drive.google.com/folderview?id=0B3Vq3sppfNgnVjUzMy1YVXZxYmM&usp=sharing
Click to expand...
Click to collapse
Download Links to MultiBoot Recovery & .Zip: https://drive.google.com/folderview?id=0B3Vq3sppfNgnVjUzMy1YVXZxYmM&usp=sharing
*ALL* credit goes to Gearslam and anyone who helped.

Mine. Muhahahahaahahahaha :good::good::fingers-crossed::laugh:

Awesome.
I use this method and am rocking the dual boot with @gearslam 's mods. Thanks again for all the help.
EDIT: 4-29-2014
@gearslam Can you edit the script to allow installation of geespr roms? I tried to install an official rom and it said during installation that the process is for (insert multiple "GEE" type roms) and listed gee_spr but said the one I was trying to install was geespr. I think the underscore might make a difference. And since I have no idea how to update it to allow other roms, would you please?

Awesome! Thanks for this guide!
Sent from my Optimus G using XDA Free mobile app

Thanks for this, and thank you too gearslam! Rocking both cm11 and stocktimus ce. Love it, especially now that the stock Rom is using the 0 folder to load files so there aren't 2 separate areas to search through ( had to use twrps file manager to move some things up so I could view photos I took on stock lol)
Sent from my LG-LS970 using Tapatalk

So... Does multibooting mean I can switch between roms and its just how I left it each time I switch? For example if I download an app and switch its still in the rom I downloaded the app for? Like I don't need to create a backup every time ?
idk how I got here...

treezy26 said:
So... Does multibooting mean I can switch between roms and its just how I left it each time I switch? For example if I download an app and switch its still in the rom I downloaded the app for? Like I don't need to create a backup every time ?
idk how I got here...
Click to expand...
Click to collapse
From what I have personally tested yes. But you will need a backup of a run to use as 2nd. Like I said I use cm11 as primary and stock as backup. Very nice.

treezy26 said:
So... Does multibooting mean I can switch between roms and its just how I left it each time I switch? For example if I download an app and switch its still in the rom I downloaded the app for? Like I don't need to create a backup every time ?
idk how I got here...
Click to expand...
Click to collapse
Yes,
I use about 5 different ROMS and they all have different apps, and app data for that matter unless you have the app synced to something like facebook. Also, it depends on if you choose restore from my google account and back up this phone to my google account during setup.
Whiplashh said:
From what I have personally tested yes. But you will need a backup of a run to use as 2nd. Like I said I use cm11 as primary and stock as backup. Very nice.
Click to expand...
Click to collapse
Also, a backup to create a secondary rom is not necessary, you can choose to flash a zip to add a rom. I do it every time I want to try a new rom instead of flashing over my current. BUT YOU CAN CHOOSE TO RESTORE A BACKUP AS SECONDARY.
This by far is the most awesome feature I have ever came across. You can even have different kernels for each, just make sure during install that don't share kernel is checked.

dopy25 said:
Yes,
I use about 5 different ROMS and they all have different apps, and app data for that matter unless you have the app synced to something like facebook. Also, it depends on if you choose restore from my google account and back up this phone to my google account during setup.
Also, a backup to create a secondary rom is not necessary, you can choose to flash a zip to add a rom. I do it every time I want to try a new rom instead of flashing over my current. BUT YOU CAN CHOOSE TO RESTORE A BACKUP AS SECONDARY.
This by far is the most awesome feature I have ever came across. You can even have different kernels for each, just make sure during install that don't share kernel is checked.
Click to expand...
Click to collapse
You got it to work without a backup? Can you elaborate how? I couldn't get it to. Whenever I tried to flash normal zip ROM, it gave me errors.

Whiplashh said:
You got it to work without a backup? Can you elaborate how? I couldn't get it to. Whenever I tried to flash normal zip ROM, it gave me errors.
Click to expand...
Click to collapse
All I do is go to TWRP, Advanced, MultiRom, Add Rom, Make sure it says Android rom and not .mrom, check do not share (I don't know if it's necessary but I prefer not to share the kernel because I am greedy, also I have gproj and GEE roms) zip file then select your zip from storage.
Also, gearslam updated the files again, that might have something to do with it. I noticed a few errors while installing so I sent him a PM. The new files are on the google drive that's linked in the op.
His response was
I uploaded another one using the "geehrc4g" id which seems to be what the latest version of the LS970-TWRP is using these days...
Click to expand...
Click to collapse
Try using the ones he said. I was able to flash them in the order they are supposed to be OVER the old ones without losing anything, there is an option to inject multi rom after install, I selected that and everything works great. I can flash pretty much any rom as a secondary. I haven't messed around with much swapping because there hasn't really been a need.
I have Pac gee, Pac LS970 nightly, Beanstalk, Mokee, Lego, and stock. They were all flashed by adding a rom as a zip. No problems with any that I can see so far. I have a problem with Mokee and the keyboard but that might be unrelated.

dopy25 said:
All I do is go to TWRP, Advanced, MultiRom, Add Rom, Make sure it says Android rom and not .mrom, check do not share (I don't know if it's necessary but I prefer not to share the kernel because I am greedy, also I have gproj and GEE roms) zip file then select your zip from storage.
Also, gearslam updated the files again, that might have something to do with it. I noticed a few errors while installing so I sent him a PM. The new files are on the google drive that's linked in the op.
His response was
Try using the ones he said. I was able to flash them in the order they are supposed to be OVER the old ones without losing anything, there is an option to inject multi rom after install, I selected that and everything works great. I can flash pretty much any rom as a secondary. I haven't messed around with much swapping because there hasn't really been a need.
I have Pac gee, Pac LS970 nightly, Beanstalk, Mokee, Lego, and stock. They were all flashed by adding a rom as a zip. No problems with any that I can see so far. I have a problem with Mokee and the keyboard but that might be unrelated.
Click to expand...
Click to collapse
Okay. Thank you man

Whiplashh said:
Okay. Thank you man
Click to expand...
Click to collapse
Any time. Let me know how it goes if you do flash those other files.
If you try it out and it works for you maybe you could add it to the OP, that the ones to flash are the geehrc4g because anyone looking at them might not know that right off hand.

Quick question... When flashing a new rom to try, how does one go about doing that?
idk how I got here...

treezy26 said:
Quick question... When flashing a new rom to try, how does one go about doing that?
idk how I got here...
Click to expand...
Click to collapse
If you are on the ls970 sprint Optimus make sure to use the geehrc4G and not the geespr versions in the google drive. I know it might not make much sense but they work and they were edited by gearslam to flash pretty much any rom for the ls970 or gee.
Go to twrp, advanced, multiboot, add rom, then follow the prompts. I prefer to use the do not share kernel option. After that you can choose to install a rom from zip. Then the next boot you can choose which one to boot into.
If you want to add stuff, IE; change kernel or flash another zip to that rom (GAPPS) just go to advanced, multirom, list roms, then select the rom you want and you can choose a normal option such as flash zip, wipe data, wipe dalvik, wipe cache. It's all there once you select list roms.

Trying to get this working but running into a few problems when adding a rom tells me can't find my data partition... It does complete and shows it to be added but once I reboot and select it... It has error box pops up says kernel doesn't have kexec I've tried many different ways having stock as primary on internal have PAC on primary internal tried adding as a zip tried adding as back up all ends the same with me only being about to boot into the primary internal ROM...
Sent from my LG-LS970 using XDA Premium 4 mobile app

spleef said:
Trying to get this working but running into a few problems when adding a rom tells me can't find my data partition... It does complete and shows it to be added but once I reboot and select it... It has error box pops up says kernel doesn't have kexec I've tried many different ways having stock as primary on internal have PAC on primary internal tried adding as a zip tried adding as back up all ends the same with me only being about to boot into the primary internal ROM...
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I had the same problem with the error saying no Kexec. Have you tried making a new backup and then adding as 2nd rom? That is now mine worked.

spleef said:
Trying to get this working but running into a few problems when adding a rom tells me can't find my data partition... It does complete and shows it to be added but once I reboot and select it... It has error box pops up says kernel doesn't have kexec I've tried many different ways having stock as primary on internal have PAC on primary internal tried adding as a zip tried adding as back up all ends the same with me only being about to boot into the primary internal ROM...
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Any luck!? I have PAC gee as primary but I forget the kernel at the moment. I'm almost sure it's matr1x. Also make sure to use the geehrc4g version. It works perfect for me. And mine always says it can't find data partition. I think it's because it uses a folder named multirom in the sd0 partition. Also when your in a file manager you can't open that folder. I haven't tried with root permission but I don't want to mess anything up.

dopy25 said:
Any luck!? I have PAC gee as primary but I forget the kernel at the moment. I'm almost sure it's matr1x. Also make sure to use the geehrc4g version. It works perfect for me. And mine always says it can't find data partition. I think it's because it uses a folder named multirom in the sd0 partition. Also when your in a file manager you can't open that folder. I haven't tried with root permission but I don't want to mess anything up.
Click to expand...
Click to collapse
Not yet just tried again by making a back up of PAC and flashing a stock ROM but the stock ROM wouldn't boot kept kernel crashing immediately after the lg pop up so I'm going to download another stock ROM which one are you guys using? Says the same thing with trying with liquid though so I'm not sure what's going on tried to dual boot liquid and PAC had same exact results even tried making those two share the kernel as well as not buy of course didn't try that with the stock rom I kept it as is
Sent from my LG-LS970 using XDA Premium 4 mobile app

EDIT: I added some pics. 2 show the about this device. One is the boot menu the other is the list ROMs function under recovery.
The screenshots are the about info for my primary ROM.
Edit 2: Wow that was a weird double post. I use the stock zvc (from zip on the forum) but only as a secondary. PAC gee version from 4-4 is my primary.
@spleef ! I just thought of something, when I tried to use solid kernel on liquid smooth ls970 when it was a secondary ROM, my phone would also only boot the primary! I had to use f93 cpq to boot it and any other ROM other than primary. Maybe some kernels are not compatible if they override the primary. Try like I have with gee version of pac as primary and the kernel I'm using (might even be built in kernel) I'm hoping you know more than I do about it based on the about device info.

Nope still couldn't get it going...no matter how i try it get the kexec error doesn't matter which i use a primary stock or custom and same goes for secondary doesn't matter which one kexec error when trying to choose...I'm using geehrc4g version is very confusing
Sent from my LG-LS970 using XDA Premium 4 mobile app

[MOD][12 GEN 2015] [D851] Multirom

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Lg G3. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.​
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​
Installation
Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM (multirom-YYYYMMDD-vXX-d851.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_d851_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.​
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.​
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.​
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
Check on my github...
Credits: @tassadar for the awesome work; @invisiblek and @savoca @patrik.KT for them help
@Tectas cause i used his ( awesome) source code for building the kernel
And sure... tnx to @arifqur and @SonjaMichelle for testing this
...and all the people that now i forget

PLEASE READ THE MULTIROM WIKI TO UNDERSTAND BETTER WHAT YOU ARE DOING
IMPORTANT: Need to be with a Kitkat stock Rom ( if you use my kernel ) or with a rom that have a kernel with the kexec hardboot patch.
HOW TO INSTALL:
1- reboot in recovery and flash the new TWRP with Multirom support; --> HERE
2- reboot the recovery;
3- flash the kernel with the kexec hardboot patch HERE
4- flash the multirom zip; ---> HERE
5- install every Rom you want ( advanced--> multirom --> add rom )
6- reboot and choose the rom you want to boot.
You can also use a Cyanogenmod or similar with the wonderful Rin Kernel by @Tectas --> DOWNLOAD FOLDER
If you want show me your love for this you can consider a small DONATION
Issues:
1- On boot the touch need some seconds to work in multirom menu, you can use the volume keys to move and the power button to select.

another one

Was the first one to get it working on my D851,
Thanks to the OP.
Man you are definitely a very gifted developer as you did not even have the device and got everything to work on the first try.
Brilliant stuff my man.
You deserve the best.

I was the second one to test and run MultiROM this morning. skin1980 does excellent work! I could barely keep up. :good:
So far I've installed the stock factory ROM, SkyDragon 1.1.0 and Fusion5.0 (1/11/15). I have been able to swap the primary ROM with the secondary ROM and back again, install from backup and install from zip. Installing PA-gapps was a cinch when installing Fusion.
So far so good.

First and foremost, THANK YOU @Skin1980!!!!!!!!!!!!!!
Two quick questions though after reading Multiroms wiki page and the information provided in the OP.
1. Do you have the compatible uninstaller zip file compiled for the d851? (On the wiki it states that in order to fully remove multirom you have to flash an uninstaller) - Not that I plan on removing multirom, TRULY AWESOME & THANK YOU!!!, but better safe than sorry....should something go wrong... (yes, I am currently backing up my phone & will be placing it on my computer prior to diving into this fun)
2. After reading Multirom's WIKI, I know it states you can load ANY rom once you have everything setup, but does that include having both 4.4.x & 5.0 roms at the same time -- stated more plainly, Can I flip between Kitkat and Lolli with this??? (I was always taught, "If something seems too good to be true......")
But if it is true, aww man, you just answered my prayers!!! (Stock based KK @ home for wifi-calling (TMO has no signal @ my house) and L @ work cause I'm impatient and can't wait for TMO any longer to rollout 5.0)
I know it's been my burden to bear, but flashing twice a day just to enjoy L for part of my day has become tiresome....lol
Sorry about the long post, but thanks again for porting this over to d851 for us!!!!

mjfrank said:
First and foremost, THANK YOU @Skin1980!!!!!!!!!!!!!!
Two quick questions though after reading Multiroms wiki page and the information provided in the OP.
1. Do you have the compatible uninstaller zip file compiled for the d851? (On the wiki it states that in order to fully remove multirom you have to flash an uninstaller) - Not that I plan on removing multirom, TRULY AWESOME & THANK YOU!!!, but better safe than sorry....should something go wrong... (yes, I am currently backing up my phone & will be placing it on my computer prior to diving into this fun)
2. After reading Multirom's WIKI, I know it states you can load ANY rom once you have everything setup, but does that include having both 4.4.x & 5.0 roms at the same time -- stated more plainly, Can I flip between Kitkat and Lolli with this??? (I was always taught, "If something seems too good to be true......")
But if it is true, aww man, you just answered my prayers!!! (Stock based KK @ home for wifi-calling (TMO has no signal @ my house) and L @ work cause I'm impatient and can't wait for TMO any longer to rollout 5.0)
I know it's been my burden to bear, but flashing twice a day just to enjoy L for part of my day has become tiresome....lol
Sorry about the long post, but thanks again for porting this over to d851 for us!!!!
Click to expand...
Click to collapse
1- will compile but to remove completely just reflash the kernel and delete the multirom folder in sdcard
2- yes... you can have kk and LL togheter without issue... in my D855 i have 5 rom installed right now

Very nice.
Only one question if it's okay. Where it says one needs to be with a KK stock ROM does it have to be factory stock or will stock-based do (such as SkyDragon, et al)?
Thanks.
Sent from my LG-D851 using Tapatalk

marcdw said:
Very nice.
Only one question if it's okay. Where it says one needs to be with a KK stock ROM does it have to be factory stock or will stock-based do (such as SkyDragon, et al)?
Thanks.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
I'm running the SkyDragon ROM with skin1980's kernel. This was NOT by design. I did this by accident when I was flashing in TWRP. FOLLOW AT YOUR OWN RISK!
Here is what I did from memory as best as I can recall.
Boot into Recovery
Made a Nandroid Backup
Wiped System/Data/Cache/Dalvik
Restored my Factory Stock Backup that I made when I first rooted my phone.
Installed skin1980's Recovery
Installed skin1980's Kernel
Installed skin1980's MultiROM Zip
Installed a Second ROM
Rebooted Made sure Everything Worked.
Back into Recovery
Restored my Nandroid Backup
Installed skin1980's Kernel
Installed skin1980's MultiROM Zip
Reboot.
SkyDragon 1.1.0 is running with skin1980's kernel. Like I said, this was all by accident. FOLLOW AT YOUR OWN RISK!

marcdw said:
Very nice.
Only one question if it's okay. Where it says one needs to be with a KK stock ROM does it have to be factory stock or will stock-based do (such as SkyDragon, et al)?
Thanks.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Stock based is OK too
Sent from my SM-N910F using XDA Free mobile app

Thank you so much been waiting 7 months for this.
Sent from my LG-D851 using XDA Free mobile app

Screen Brightness
Any way to adjust the screen brightness on boot? Its really dull and hard to read when it comes to the option screen. Thanks!

Erock2k4 said:
Any way to adjust the screen brightness on boot? Its really dull and hard to read when it comes to the option screen. Thanks!
Click to expand...
Click to collapse
TWRP advanced multirom settings... choose your brightness level
Sent from my SM-N910F using XDA Free mobile app

Two things that I would love to have adjusted:
1) Vibrator intensity in the Modified TWRP recovery is very very low.
2) Screen size in Multirom Menu
Any ways this is just nit picking basically we are very lucky to have this in the first place.
Great job man.

Are you gonna be able to make this compatable with the multirom manager app from the play store? It says currently device is unsupported when app is opened.
Sent from my LG-D851 using XDA Free mobile app

anoymonos said:
Are you gonna be able to make this compatable with the multirom manager app from the play store? It says currently device is unsupported when app is opened.
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
I would assume that's only for officially supported phones....as ours is not.....

Im definitely sticking away from this one! I like my phone not being bricked!!! Haha
Thanks for brining it to XDA though

yanowman said:
Im definitely sticking away from this one! I like my phone not being bricked!!! Haha
Thanks for brining it to XDA though
Click to expand...
Click to collapse
You should give it a try... By definition, a brick is a device that is 100% useless. Bricking devices is almost completely extinct. The worst that could possibly happen is you end up having to restore bone stock and start all over. The last device that I actually "bricked" and rendered useless was my HTC G1...The first Android device...
@OP, thanks so much for this I will definitely be doing some flashing when I get home.
Quick question tho... Which Kernel was used as a base for the kexec hardboot patch? I assume it was just stock/patched. Is this correct? (I only ask, because I like to know what I will actually be changing when I flash things.)

I did something wrong. My phone goes into fastboot mode instead of recovery now

YES!
I have seriously missed the days of Boot Manager on my HTC Rezound. This is a GODSEND! I can have my stock rom at home and use the wifi calling in my low signal environment AND play with the 5.0 roms at work! WOOT! I did manage to install Multirom and throw a 5.0 rom on my internal storage. I made sure I could boot into my stock rom first and now I am setting up the 5.0 rom. This rocks!
Now which one shall I pair with my 360?