yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] blambo:
Same. Scott's works perfectly as L secondary. No issues, no headaches, and no disappointments.

Install Stock-Root-LRX21P-5.0 as secondary, restore apps with Backup+, install ElementalX 3.02zip, OC @ 1944. Then off to the races. The entire thing takes less than 15 min. Too bad it doesn't look like XPOSED is ever going to make it along for the ride with us, otherwise Scott's would be doing primary duty pronto.
[Nexus 7 (2013) Original Android Development] iaTa:
Which kernel are you all using for the internal rom which has root and kexec?
[Nexus 7 (2013) Original Android Development] xanthrax:
it depends on your rom... dontcha think ?
[Nexus 7 (2013) Original Android Development] iaTa:
Does it? I didn't think they were mutually exclusive. I'm on stock L.
[Nexus 7 (2013) Original Android Development] lemene:
Just apply stock 5.0 from the multirom app or use other like elementalx 3.02. You ll still have root, etc
[Nexus 7 (2013) Original Android Development] iaTa:
I haven't been able to get root with the stock 5.0 from MR app and I'm not a fan of elementalx as I seem to get audio stutter no matter what config I try.

Are there any other options, or how do I get root with that stock 5.0 from MR app?
[Nexus 7 (2013) Original Android Development] thereal_bigjake:
You can try hells kernel I don't have a link handy. I use ElementalX and have never had audio stutter. I see there is a new Glitch kernel for Lollipop but I haven't tried it yet.
[Nexus 7 (2013) Original Android Development] iaTa:
I didn't know Hells makes a Flo kernel? Love their N5 L Kernel.

I can't get root working on the latest Glitch kernel either, explanation here:

http://xdaforums.com/showpost.php?p=56773536&postcount=2088

ElementalX is the only kernel I can root and use MR so far, hence my original post.
[Nexus 7 (2013) Original Android Development] thereal_bigjake:
I think it may have been a port but I can't seem to find what thread it was in. It was one of the L rom threads.
[Nexus 7 (2013) Original Android Development] hhairplane:
Can't wait for app/data sharing. Would SMS/MMS be part of this? This is the main/only thing that I have to redownload on all ROMs having it shared would be amazing.
[Nexus 7 (2013) Original Android Development] Scottchy014:
Thank you for the update to v30! I can now choose what ROM to boot into when I restart or turn on my Nexus 7 (flo) running lollipop. Here is my latest video on MultiROM: Nexus 7 (2013)**Android Lollipop 5.0**MultiROM!
[Nexus 7 (2013) Original Android Development] idCyber:
I would like to try MultiROM, but before I do I have a few questions:

1. Can I flash MultiROM recovery and keep my installed ROM and kernel and settings directly as a primary ROM or I have to wipe and reflash the ROM and kernel I am currently using and then flash a different ROM and kernel as secondary?

2. Can i restore a nandroid backup and make ot primary if I have a secondary ROM installed ?
[Nexus 7 (2013) Original Android Development] Sora1995:
You keep all the settings from the primary ROM. The only exception is you may have to flash a different kernel. And yes, you can use a nandroid if you'd like.
[Nexus 7 (2013) Original Android Development] borxnx:
After I wiped /system to flash a new primary rom I had to reflash the multirom mod, FYI. Everything was still there, but I just wasn't getting the selection screen at startup.
[Nexus 7 (2013) Original Android Development] Grondinm:
All you would have had to do is go into multirom menu in TWRP and say inject current boot sector.
[Nexus 7 (2013) Original Android Development] borxnx:
That's how to avoid having to reflash the mod? I was wondering what that did. Thanks!
[Nexus 7 (2013) Original Android Development] Grondinm:
yep. you would have to do that any time you flash a new kernel.
[Nexus 7 (2013) Original Android Development] robdroyd:
Ok, thanks!

Booted into TWRP, did System/Wipe (to remove former Primary ROM), installed "Clean ROM" from zip file, went into MultiROM options- injected current boot sector, renamed the new primary ROM correctly.

Rebooted system.. all is good... now "Clean ROM" is my primary ROM. Booted back into recovery, then into MultiRom options, deleted former secondary ROM and now my former tertiary ROM (Stock-Rooted) is now my secondary ROM.

Thanks for the advise all!
[Nexus 7 (2013) Original Android Development] Links2004:
looks really nice is it possible to get this working on the LTE version (deb)?
[Nexus 7 (2013) Original Android Development] StrangerWeather:
How do I flah superSU on my secondary rom? It's lost root...
[Nexus 7 (2013) Original Android Development] silvan g:
in twrp go to advanced>multi rom> list roms>select your rom>flash zip ;)
[Nexus 7 (2013) Original Android Development] StrangerWeather:
Thanks, I did this but it failed... I wonder why...:)
[Nexus 7 (2013) Original Android Development] Tasssadar:
I see that lot of you are struggling with this. I can make this automatic - check if MultiROM is installed in boot image before zip installation and if so, make sure it is installed after the installation finishes, too. I'm afraid that it could be taken as too intrusive, though....

BTW, sorry for not responding to any other posts right now, suddenly I find myself with several threads to follow and sooo many posts to read....
[Nexus 7 (2013) Original Android Development] Grondinm:
No need to apologize that is why this is a community. Also I think its OK to leave it an option just in case. Maybe it just needs to be made clearer in the OP.
[Nexus 7 (2013) Original Android Development] flash5000:
In my opinion this would be a good enhancement, as one could use CyanDelta or CM updater without loosing/reflashing MR daily...

Maybe make it an option in settings?

Gesendet von meinem Nexus 7 mit Tapatalk-4
[Nexus 7 (2013) Original Android Development] Tasssadar:
Yeah, it would be an optiom in settings, that's for sure. The question is - is it enabled by default? I think it would be better to enable it by default, because it makes things easier for less experienced user.
[Nexus 7 (2013) Original Android Development] Raverbunny:
already answered in this thread, search button is your friend :p

http://xdaforums.com/showpost.php?p=45908348&postcount=22
[Nexus 7 (2013) Original Android Development] robdroyd:
I also think it would help us newbies... "enabled by default"? Yes, why not- with the option to disable the feature clearly available.

Make a great utility even better!
[Nexus 7 (2013) Original Android Development] Tasssadar:
New recovery was released. It automatically injects boot sector with MultiROM after flashing a ZIP file or using adb sideload. That means you don't have to click "Inject boot sector" every time you install different kernel, it does it for you. It can be turned off on "Confirm flashing" and "adb sideload" pages in recovery.

http://d-h.st/Vjo

Not right now, but I will probably make flashable ZIPs with stock, unmodified 4.4 once it is out, same as I always make ZIPs with stock Androids for grouper.
[Nexus 7 (2013) Original Android Development] z31s1g:
Holofied MultiROM theme released

Holofied MultiROM (codename "rainbow") released

Changes made 16/10/2013 (auto inject MultiROM) included.

Huge thanks to [MENTION=3418703]Tasssadar[/MENTION] for helping me finishing this.

About:

Portrait only theme.

Landscape option is still present, but will default back to stock TWRP theme.

Tested working:

Everything Android related

Needs to be tested:

Installation of MultiROM Installer files.

Download:

Holofied Thread

Screens:
[Nexus 7 (2013) Original Android Development] AL2000EX:
Sorry I want to install this mod and I have a couple of nooby questions.

Will my primary rom's Data partition be wiped when adding a secondary ROM?

Will the secondary Roms be able to read data from primary rom's storage, so apps would be able to use their data ?

Thanks!
[Nexus 7 (2013) Original Android Development] borxnx:
Have you enabled adb+apps in development settings? And is your secondary ROM OmniROM?
[Nexus 7 (2013) Original Android Development] gunfromsako:
NM... Lol
[Nexus 7 (2013) Original Android Development] Nolfer:
Sorry to ask, but I don't seem to find the answer anywhere:

How do I flash a kernel for a secondary ROM? How do I flash it if it is a .img file? Do I have to use the "inject boot.img file" option? If yes, why does it not ask for what ROM it will be injected?
[Nexus 7 (2013) Original Android Development] xanthrax:
When from the list you select a Rom the next option to inject a .img is for that ROM

Sent from my Darkside of 1+1
[Nexus 7 (2013) Original Android Development] idCyber:
New TWRP is available . Cant wait for and update from MultiROM
[Nexus 7 (2013) Original Android Development] drewski_1:
i believe you will need a flashable zip and install in the Multirom section.
[Nexus 7 (2013) Original Android Development] bmakk2055:
[MENTION=3418703]Tasssadar[/MENTION] could you do a zip of the new update 5.0.1 (LRX22C)?
[Nexus 7 (2013) Original Android Development] KARNAG3:
Partition

Hello great community! 2-3 days ago I've installed Multirom (Latest release at that moment) via GooglePlay app on my nexus 7 32Go Rooted Running Lollipop. After that, my stock rom only showed that I had approximatly 16Go of total space on my device as if it was partitioned in 2. After, I tried to uninstalled Multirom by folowing the first post but then nothing changed, I still only had approximately 16Go on my device as if I bought the 16Go version 2 years ago. Following the first post I also wiped everything and flash the stock image 5.0.1 via the Nexus Root Toolkit v1.9.9 and I still only have 16Go (Freshly installed with no apps, 10.65Go available). What would you guys suggest I should do? Any suggestions? Thanks! :confused:
[Nexus 7 (2013) Original Android Development] mdamaged:
Factory reset is the common fix for that.
[Nexus 7 (2013) Original Android Development] KARNAG3:
Already did Flash Stock + Unroot in Nexus Root Toolkit.

Did "fastboot format userdata" from another post in another thread without result.

Currently trying Factory reset from within Lollipop, will report back.
[Nexus 7 (2013) Original Android Development] mdamaged:
Good luck.
[Nexus 7 (2013) Original Android Development] KARNAG3:
Thanks a lot! It worked!! I had doubts but it did the trick!
[Nexus 7 (2013) Original Android Development] mdamaged:
Glad to help. :)
[Nexus 7 (2013) Original Android Development] muschiu35bv:
Error install ROM

Hello guys!I wanted to install AiCP Lollipop ROM on Flo device using multirom by I get this error"error executing updater binary in zip tmp/Mr_update.My primary ROM is Stock Lollipop LRX22C and my second is Carbon ROM KitKat.How to be able to install ROM using multirom?Thank you!
[Nexus 7 (2013) Original Android Development] xanthrax:
It doesn't work, the updater script needs modifications

You can ask in the ROM thread

Sent from my Darkside of 1+1
[Nexus 7 (2013) Original Android Development] muschiu35bv:
When i was on Lollipop LRX21P i was able to install Aicp Lollipop without issue.This is not a issue with multirom.I hope the AiCP team they fix this problem.Thank You!
[Nexus 7 (2013) Original Android Development] xanthrax:
This is the way the updater script comes from cm with the latest update, this happens on all devices with multirom support

Sent from my Darkside of 1+1
[Nexus 7 (2013) Original Android Development] tungdil:
with MultiROM?

Hello muschiu35bv!

when you wrote; from LRX21P to Aicp Lollipop it worked.

This was outside of MultiROM, right? Could you explain how you did it?

As far as I understand you'll need a flashable ZIP for MultiROM which contains the system folder in a tared, gzipped file (system.tar.gz). The problem with Lollipop builds is that the release-process (when building the ROM) packages the images in a different way (even different from KitKat) which "only" contains images of partitions. The system partition is in system.new.dat. Unfortunately this image seems to have a "strange" format, at least for noobs such as I. Linux "recognizes" the partition as ext4 but cannot mount it. Diving into this you'll find a "bad geometry", something like EXT4-fs (loop0): bad geometry: block count 215040 exceeds size of device (97960 blocks). Maybe someone at XDA with more knowledge could comment on this?

Thanks and best regards,

tungdil
[Nexus 7 (2013) Original Android Development] muschiu35bv:
I hope de Aicp team to find something to fix this issue.Lollipop is very different from kitkat or other google os.Anyone knows a fix for this will be helpful.I really want to use Lollipop custom ROM with MultiRom.Thank You!
[Nexus 7 (2013) Original Android Development] thereal_bigjake:
Here is an example on how to edit the updater script so cm12 roms will install as secondary http://xdaforums.com/showthread.php?p=57211572

This is is for the Nexus 5 but same concept just edit the script in the rom you want to flash.
[Nexus 7 (2013) Original Android Development] klaust58:
Hello,

i'm currently not able, to get a working system from a backup! No problem installing new rom's from zip.

I tried now many times...backup a previously created, working rom. Then create new rom from backup, no failures but when booting, it stays at the google logo for a minute or two and then restarts to twrp. Nothing helps...fullwipe also did not help.

Is this a known problem or what can i do?

Thanks!

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] muschiu35bv:
Hello!Thank you for your help but i dont know how to edit the script because until now i havent did that.I hope MultiRom to release a new update with fixing this isue.
[Nexus 7 (2013) Original Android Development] thereal_bigjake:
Aosp or CM rom? I have backed up and restored aosp Lollipop roms many times without issues.
[Nexus 7 (2013) Original Android Development] klaust58:
All ROMs...SlimKat, SlimLp, Stock, AOSP, CM12....

I also restored many times without problems.....but this was some weeks ago.

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] muschiu35bv:
Just after i update to LRX22C i could not instal Lollipop custom ROM with multiRom but with LRX21P i was able to install Lollipop custom ROM.Only KitKat Roms work with multiRom
[Nexus 7 (2013) Original Android Development] klaust58:
I have to correct myself.... reloaded KitKat-ROMs function normally. Only reloaded Lollipop-ROMs don't boot.

Is this because of TWRP 2.8.1? Fixed in 2.8.2?

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] gicuenitro:
Install issues?

Hey everyone! Happy Holidays! Hope all is well...

I have installed and updated multirom. But when I reboot to the modified twrp, the multirom section does not show.

Everything works fine on my nexus 5 but on the nexus 7 (flo) no matter what I seem to do, the options are not showing up.

Any ideas on what I am doing wrong? Thanks for your help!
[Nexus 7 (2013) Original Android Development] drewski_1:
Are you using any theme?
[Nexus 7 (2013) Original Android Development] muschiu35bv:
Try This

If you use theme for TWRP you need to download the theme for multiRom not just simple TWRP.Those file you can find here http://xdaforums.com/showthread.php?t=2409432 . I hope this help
[Nexus 7 (2013) Original Android Development] gicuenitro:
Multirom theme or TWRP theme? I dont believe I have installed a theme on either of them for the 7 or 5. Both of them are the dark/holo looking theme just like the second screenshot found here(thanks to muschiu below) http://xdaforums.com/show....php?t=2409432. Again, I followed the same procedure as I did on the 5 and installed the latest version of TWRP as well. Could it be using a theme that I might have installed a long time ago even though I have installed a fresh or new version? Thank you very much for replying and helping me thru this. I really appreciate it!
[Nexus 7 (2013) Original Android Development] z31s1g:
The Holofied themes are no longer maintained, please consider using the new Materialised theme.

Also, the multirom recovery requires a specific theme (with all the additional menus you're currently missing).

So if you're going to switch to the Materialised theme, make sure to use a version that is marked compatible (eg 1200_dark_multirom).

If you don't want to use a recovery theme any longer, use a root explorer to remove the ui.zip from "/sdcard/TWRP/theme" folder.
[Nexus 7 (2013) Original Android Development] muschiu35bv:
Lollipop CustomROM Install Isue

Hello Guys!IDo you plain to update MultiROM because is not working with Lollipop LRX22C.KitKat Roms works without problems but Lollipop Custom Rom is not working.Some guys from the Lollipo Custom Rom say that the problem is with MultiROM.I am sorry for my question.Thank You!
[Nexus 7 (2013) Original Android Development] HearMeWhisper:
Any chance for the newest update zip? 5.01
[Nexus 7 (2013) Original Android Development] mdamaged:
If you can't wait, and you already have 5.0.0 as a secondary(or you can flash the 5.0.0 now), swap it to primary, (if it isn't already), grab boot and system from the 5.0.1 factory images, then boot into fastboot and do:

fastboot flash system system.img

fastboot flash boot boot.img (if the kernel you have is 5.0.1 ready then you can skip this)

fastboot format cache

fastboot reboot

You just have to reroot, and redo whatever mods you like to do to system, kernel...etc. I did the boot.img too, so I also had to reflash twrp and install my fave custom kernel, and multirom.
[Nexus 7 (2013) Original Android Development] tungdil:
If you are not yet on 5.0 the following might work....

Note: I'm just summarizing information which I found at various places here @ XDA-developers and elsewhere. What is described below works for me, no warranty that it will work for you as well. I'm not responsible for anything that happens when you try following the description below. It's @ your own risk. You have been warned!

You'll need: Tassadars build lrx21p_flo.zip and the factory image razor-lrx22c-factory-a9c6e55f.tgz, a computer running Linux (I'm on Ubuntu 14.10) with some Gigabyte free space and, finally, the tool "simg2img". In Ubuntu the latter can be installed using sduo apt-get install android-tools-fsutils

At first unpack "system.img" and "boot.img" from the factory-build into a new directory. I started in the directory where I put the two builds and used "lrx22c":

mkdir lrx22c
cd lrx22c
tar -xzf ../razor-lrx22c-factory-a9c6e55f.tgz razor-lrx22c/image-razor-lrx22c.zip
unzip razor-lrx22c/image-razor-lrx22c.zip system.img boot.img

Then convert and mount the system image (using options for mount, you'd need to be root, i.e. use sudo) and create "system .tar.gz" in a subirectory called "rom"

simg2img system.img system.img.raw
mkdir mnt-img
mkdir rom
sudo mount -t ext4 -o loop system.img.raw mnt-img/
sudo tar -czvf rom/system.tar.gz -C mnt-img/ .

The final step is to exchange "system.img" and "boot.img" in "lrx21p_flo.zip" and create "lrx22c-test_flo.zip".

cp ../lrx21p_flo.zip lrx22c-test_flo.zip
zip -u lrx22c-test_flo.zip rom/system.tar.gz
zip lrx22c-test_flo.zip boot.img

This will leave you with a zip file ("lrx22c-test_flo.zip") that can be flashed as secondary ROM in MultiROM. I trust you know how how to unmount the raw-image and to "get rid" of all the files and directories that were created.

Good luck!
[Nexus 7 (2013) Original Android Development] muschiu35bv:
Updater Script

Hello!Can you tell me please how to modify the updater script?I dont know how to do that.I want to instal Aicp Llllipop rom on my Nexus 7 2013 but i get that error.Thank You!
[Nexus 7 (2013) Original Android Development] PlayingPoise:
Most lollipop ROMs will work if you back up your kitkat ROM, flash the lollipop ROM as primary, then restore the kitkat ROM as secondary and swap them. It should work perfectly after that.
[Nexus 7 (2013) Original Android Development] tungdil:
Just checked it with today's build aicp_flo_lollipop-1.0RC0-NIGHTLY-20141213.zip and it works with the same method as described here.

Note: I tried it with other builds before. Installation as secondary was possible but after the boot animation the screen turned black and boot wouldn't continue.

Good luck!
[Nexus 7 (2013) Original Android Development] muschiu35bv:
Updater Script

Thank You very much!I did has you say and works without issue.Thank You again !You make my day!:o
[Nexus 7 (2013) Original Android Development] TheIronMaiden:
I'm getting the "error in binary updater" so I can't install any secondary roms. Searched and couldn't find an answer. I've tried to reinstall the recovery through the multirom app. Even tried several different recoveries. Same outcome. Different roms even. Never came across this before. It's strange
[Nexus 7 (2013) Original Android Development] tungdil:
If it is the E: error executing updater binary in zip '/temp/mr_update.zip' problem then modifying the updater-script might help. See two posts above...
[Nexus 7 (2013) Original Android Development] klaust58:
Same with SlimLP for N4/mako and N7/flo. Modifying the updater-script solves the problem.

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] SA3DX:
Awkward thing is with me that certain ROMs worked with me before I flashed primary ROM with a custom. Now that particular ROM flashed as secondary gives a boot loop.
[Nexus 7 (2013) Original Android Development] asp2010:
Hi,

I've looked around but can't seem to find any definitive information, so I thought I'd ask. I want to swap my primary ROM with one of my secondary ones. Is it enough to take backups of both and restore them to their new places, or is there something more I should do?

Thanks.

Sent using the XDA mobile app
[Nexus 7 (2013) Original Android Development] tungdil:
Backing up is always a good idea... and then just use Recovery->Advanced->MultiROM->Swap Roms (this post shows a screen print of TWRP 2.8.0)

---------- Post added at 11:48 AM ---------- Previous post was at 11:21 AM ----------

I guess without any information about the ROMs you are using it will be difficult for a developer to help you. Just being a user the only thing that comes to my mind is that the kernel of your primary ROM might just not support kexec-hardboot. I'd recommend using the MultiROM Manager App and check the status it will say something like Kernel: doesn't have kexec-hardboot patch! (see 1st post in this thread "Installation")
[Nexus 7 (2013) Original Android Development] SA3DX:
Finally someone replied. I'm sorry but this would give you a more thorough approach . I posted two times, one in the help thread. And no body replied or gave a damn. Anyway, I made a thread in Q&A section and no body gave a damn either. So here you go.

http://xdaforums.com/google-nexus-5/help/multirom-secondary-rom-boot-loop-t2984172
[Nexus 7 (2013) Original Android Development] mindmajick:
Edit: biting tongue after the fact
[Nexus 7 (2013) Original Android Development] asp2010:
Thanks, I've done this and can now boot into my new primary ROM :good:

It's probably unrelated, but I can't boot the old primary ROM that is now a secondary one. If I choose it in multirom, it just boots into my primary one, without showing the splash screen again. I've updated a few things (kernel, multirom version) and can't really tell if one of those impacted it or it never worked since I moved it. Has this happened to anyone else?

Thanks again.
[Nexus 7 (2013) Original Android Development] mdamaged:
Do both roms have a kexec-patched kernel?
[Nexus 7 (2013) Original Android Development] asp2010:
Yes. Although, just for my curiosity, do they both need it? I thought it was said in the OP that only the primary ROM needs kexec-hardboot.

This is the setup I'm running:

Primary - AOSP Lollipop ROM w/ Glitch Kernel (was secondary before, works fine)

Secondary - AICP KitKat ROM (was primary before, can't boot now)

Secondary - AICP Lollipop ROM (can boot this one)
[Nexus 7 (2013) Original Android Development] mdamaged:
No, like you said only primary needs it, just covering both/all roms in one question.

Did you try reflashing the secondary's (the one that won't boot) kernel?