yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] robdroyd:
Ok, got it!

So it would be like this:

To get the new recovery utility installed....

From CMD prompt(in ADB-Tools directory):

"fastboot flash recovery TWRP_multirom_flo_20131016.img"

Then I can go ahead and flash the new MiultiROM zip from within the new recovery utility after reboot?
[Nexus 7 (2013) Original Android Development] flash5000:
Yes, exactly.

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 7 (2013) Original Android Development] robdroyd:
All went well, wanted to go back to stock kernel for a bit to see if that was the problem with the QI charging not working on my 32GB N7.

FWIW- the Franco kernel wasn't preventing the QI charging from working- there was a physical problem w/my N7 which I was able to repair.
[Nexus 7 (2013) Original Android Development] GialanG:
Fix SuperSU for secondary ROMs?

Today I recognized the phrase "Fix SuperSU for secondary ROMs" added to thread title, but I've never seen any problem with SuperSU for secondary ROMs in this thread. So what is it exactly?
[Nexus 7 (2013) Original Android Development] rtfpessoa:
Anyone here was able to install Firefox OS with the procedure described?
[Nexus 7 (2013) Original Android Development] L1lyksd@ddy:
No problem with Firefox here.
[Nexus 7 (2013) Original Android Development] teacherhh:
I am using a rooted stock rom as first rom. Will this be updated automatically when kitkat is rolling out by google? Or do I have to bring my device back to the unrooted / bootlocked state?

Gesendet von meinem Nexus 7 mit Tapatalk 4
[Nexus 7 (2013) Original Android Development] flash5000:
A rooted device will never be updated automatically, you will have to flash an update zip by yourself when 4.4 has arrived...

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 7 (2013) Original Android Development] teacherhh:
Thanks for the answer. Are those zip released the same time as the OTA Update?

Gesendet von meinem GT-I9300 mit Tapatalk
[Nexus 7 (2013) Original Android Development] manujis:
Yes they are!
[Nexus 7 (2013) Original Android Development] flash5000:
They are of course not released by Google itself, but it usually only takes a few hours until the community has some flashable ZIPs cooked up, often even prerooted.

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] StrangerWeather:
Nvm
[Nexus 7 (2013) Original Android Development] gravedigger76:
Anyone try to get PA 4.4 loaded in multirom? Does the current version support 4.4 or shouldn't matter?

Sent from my SGH-I337
[Nexus 7 (2013) Original Android Development] klaust58:
Open your eyes and read some of the previous postings above... ;)
[Nexus 7 (2013) Original Android Development] muschiu35bv:
I have read the postings before i putt the ask.I did not really understand what they say.Me also after ive install multirom and add a Lollipop custom rom after finishing and reboot the device has back to recovery again.I am on Marshmallow with ElementalX Kernel and supersu beta 2.50.Even without installing custom rom when device reboot is return to recovery.
[Nexus 7 (2013) Original Android Development] muschiu35bv:
Hello!I am sorry to bother you.I have multirom and first is stock Marshmallow with ElementalX kernel and supersu beta 2.50 and the secondary is aicp lollipop.After installing aicp as secondary everything was ok.I was able to boot Aicp rom.But after i reboot to stock the device has got back directly to recovery.And now even aicp does not boot.And same as stock is return to recovery without booting.Can you now a fix or if there is fix for that.Will be much apreciate.Thank You!
[Nexus 7 (2013) Original Android Development] thereal_bigjake:
MultiRom needs to be updated for M.

Turn off the inject boot image option when flashing M to primary and it will boot but then you won't have a MultiRom boot menu.
[Nexus 7 (2013) Original Android Development] muschiu35bv:
Thank You but how do i turn off the inject boot image option?
[Nexus 7 (2013) Original Android Development] thereal_bigjake:
When you flash a zip you will see the option ?
[Nexus 7 (2013) Original Android Development] tungdil:
I had the same problem, and even worse: there was no way for going back to a 5.1.1 primary ROM. The only "solution" I found was to do a "factory reset wipe" with TWRP, then clean flash a new primary and a new secondary ROM. I believe that there is some incompatibility between Marshmallow and Lollipop, not sure that this is really related to MultiROM. Therefore my recommendation for those of us wanting multiple ROMs, for the time being, is stay with 5.1.1
[Nexus 7 (2013) Original Android Development] diehard2013:
Hello,

I must be missing some step.

Nexus 7 2013

Android 6 Marshmallow ROOT

ElementalX-N7-5.04 kernel

I downlaod the MutliROM app and follow instructions.

The TWRP Multirom is installed.

I am able to add custom ROMS, but none boot up.

Not even the original ROM anymore.

No matter what options I chose (inject, no inject, IM, IV, :) ) I always end back in TWRP MultiROM...

Wiping and reflashing everything back to stock is the only way to get it back to boot.

Thanks.
[Nexus 7 (2013) Original Android Development] mdamaged:
Wait for an update from Tasssadar, or go back to 5.x.x.
[Nexus 7 (2013) Original Android Development] diehard2013:
thanks.

I'm confused because his website and app in google play store mention support for Android 6 (marshmallow).

Probably the store app, not the image code (injected boot.img)....

i'm sticking with marshmalllow, there's no turnning back.... :)
[Nexus 7 (2013) Original Android Development] mdamaged:
Yeah, if you notice in the app. it still lacks a 6.x kernel with kexec from Tasssadar. As osm0sis pointed out, it does not seem to like the trampoline injection.
[Nexus 7 (2013) Original Android Development] diehard2013:
No other ROA?

:D
[Nexus 7 (2013) Original Android Development] drewski_1:
Translation (roa) for the less knowledgeable? ?
[Nexus 7 (2013) Original Android Development] mdamaged:
Route of administration.
[Nexus 7 (2013) Original Android Development] vivi19:
Boot problem :/

Hi

I got problem in my nexus 7 2013 mm 6.0 after installing multirom app flashing system when I try to boot to internal rom boot to recovery any ideas ?
[Nexus 7 (2013) Original Android Development] drewski_1:
Read the last couple of pages. MR is not yet MM compatible.

Sent from my Moto X
[Nexus 7 (2013) Original Android Development] vivi19:
Ok thanks :)
[Nexus 7 (2013) Original Android Development] koron393:
mm-6.0 bootable multirom zip for deb (experimental)

Hi.

I built mm-6.0 bootable multirom zip for deb.

I tested my private-build RR(lollipop-5.1.1) in primary and also private-build cm-13.0(marshmallow-6.0) in secondery.

And RR primary, BadBoyz stock rooted ROM secondary.

Works fine.

(But not testing mm-6.0 primary)

Source is here. Thanks [MENTION=2605798]nkk71[/MENTION]!

This is VERY EXPERIMENTAL. At your own risk.

Sorry NO FLO, because I don't have flo. But probably multirom zip will work on flo.

Now, multirom zip works on flo.

Download is here

modified multirom.zip for deb (Updated. Fix for flo)

cm-13.0 (caf) for boot test
[Nexus 7 (2013) Original Android Development] nkk71:
sure, anytime, but not sure exactly how I helped :cyclops:
[Nexus 7 (2013) Original Android Development] javacookies:
I tried this on flo and my main ROM (Stock 6.0) is now bootable! :)

However, Ubuntu Touch still stays in Google logo :(

That's more important to me than my Android ROM :D
[Nexus 7 (2013) Original Android Development] ajbiz11:
I'm just going to point out that that repo is identical to Tassadar's repo. The issue is that he hasn't compiled v20c for everyone.

The only difference between deb and flo last I checked was the radio hardware, so modifying the updater script shoooooooould work.

---------- Post added at 06:09 AM ---------- Previous post was at 06:07 AM ----------

Hammerhead is having issues with Ubuntu Touch as well. I would stick with a very minimal 5.1 install as primary to get it working. I think that was their solution. I'm very tired, so nothing I say can be trusted.
[Nexus 7 (2013) Original Android Development] javacookies:
My Problem is I can't downgrade to 5.1.1 because I'm always stuck with Android is Starting/Upgrading.

But if Multirom won't be fixed for 6.0 anytime soon then I'll probably just do a full wipe.
[Nexus 7 (2013) Original Android Development] muschiu35bv:
Multirom on flo

Hello! ajbiz11 after editing the updater script i was able to install the multirom on flo and my first rom is Marshmallow stock and the second is Aicp lollipop.Everything is working without issue.Thank You for your work!!!
[Nexus 7 (2013) Original Android Development] magarto:
What did you edit on the updater script to have MM as main rom? I want to have it too
[Nexus 7 (2013) Original Android Development] Ænimal:
Just replace any 'deb' with 'flo’ (if you have a wifi-only n7) .Nothing to do with internal rom
[Nexus 7 (2013) Original Android Development] muschiu35bv:
I've just replace the deb with flo and that was all.
[Nexus 7 (2013) Original Android Development] koron393:
Thanks for reply.

Fixed this assertion and update the zip file :)
[Nexus 7 (2013) Original Android Development] ajbiz11:
I'm pretty sure you have to do a full wipe to downgrade. YMMV.

MultiROM is technically in a "working" state with v20c+

The post a couple of pages back has the zip for deb, and it's a simple edit for flo (or the other way around, but I'm too lazy to check and it doesn't really matter.)

I'm going to compile a copy of v20c+ for mako this weekend. We shall see if I can get Ubuntu Touch running on it.
[Nexus 7 (2013) Original Android Development] lemene:
Right.

Great. It worked for flo!

(Just modifiy 'deb' for 'flo' in updater-script @ folder meta-inf, com, google, android, zip again and flash)

Have mm as primay but I'm changing to lollipop as primary and mm as secondary and see if ubuntu boots.

Thanks.
[Nexus 7 (2013) Original Android Development] aristofeles:
Perfect for my Deb, primary Bad Boys w/ ElementalX and CM 13 as secondary

Thanks!!!
[Nexus 7 (2013) Original Android Development] pilotv:
Can anyone post the edited zip for Flo? Thanks

Enviado do meu Nexus 7 através de Tapatalk
[Nexus 7 (2013) Original Android Development] muschiu35bv:
Update Script for Flo

I just upload the script
[Nexus 7 (2013) Original Android Development] pilotv:
Here the upload of zip file updated with your script for Flo.

Finally my Multirom is working again with Marshmallow 6.0 MRA58V.

Tested in my N7.

Enviado do meu Nexus 7 através de Tapatalk
[Nexus 7 (2013) Original Android Development] koron393:
See my original post.

http://xdaforums.com/showpost.php?p=63756363&postcount=1198
[Nexus 7 (2013) Original Android Development] Wannabedeveloper:
Hope this will work on marshmallow

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] drewski_1:
that's exactly what the last few pages have been about . . . :p

i have stock rooted MM w/ Elemental-X on Primary and CM13 as Secondary working AOK
[Nexus 7 (2013) Original Android Development] Wannabedeveloper:
Really? Can you guide me?

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] Ænimal:
*sigh*

Do some reading first

Make sure you have latest bootloader (4.05) installed (flashable zip can be found in one of [MENTION=426561]scrosler[/MENTION] s threads).

Flash modified recovery from second post.

Flash experimental multirom zip from a couple pages back.

Flash a 5.+ rom and make sure it has a kexec patched kernel. If not, find custom one (make sure it is compatible: stock/aosp or cm etc).

In twrp recovery go to multirom menu and add secondary roms. For marshmallow roms make sure to flash supersu 2.52.

Hopefully enjoy multirom!

Edit: Haven't flashed a marshmallow rom as primary myself yet, mainly because I want my device to be at least usb-otg ready. Should be the same procedure as described above (for aosp it's a bit more tricky), but there are just a few custom kernels suitable for multirom (elementalx, glitch e.g.)
[Nexus 7 (2013) Original Android Development] thereal_bigjake:
I'm running M as primary and secondary ?
[Nexus 7 (2013) Original Android Development] nemeblist:
Working with ubuntu touch ??
[Nexus 7 (2013) Original Android Development] .MoHaMaD:
working

i have MoHaMaDRoM w/ Elemental-X on Primary and pure_nexus as Secondary

Thanks :o
[Nexus 7 (2013) Original Android Development] Wannabedeveloper:
Anybody here try to install cm13 as secondary?

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] aristofeles:
I did. CM13 not working as secondary for me, wont install. Tried the latest, 11.30.2015, and still the same.

Using DEB.
[Nexus 7 (2013) Original Android Development] drewski_1:
I have cm13 as secondary. I'll see what build when i'm at home

Sent from my Moto X
[Nexus 7 (2013) Original Android Development] GuyInTheCorner:
Okay, just so I get this straight:

I already have 32a installed w/ the custom recovery. All I need to do to get MM working with MultiROM is flash multirom-20151113-v32-UNOFFICIAL-deb.zip?

Cheers in advance guys, I'm slightly confused after reading the last few pages
[Nexus 7 (2013) Original Android Development] drewski_1:
old school . . . chilling on 11/3 CM 13 build as secondary.

Deb, stock, rooted MM w/ El-X kernel as primary.
[Nexus 7 (2013) Original Android Development] QuietusPlus:
Not sure if mentioned before, but there is currently an issue with the CM13 updater-script. The installer returns "system partition has unexpected contents after OTA update" when attempting to flash. The script can be modified to work by doing the following:

Open cm-13.0-201512##-NIGHTLY-flo.zip

Navigate to "\META-INF\com\google\android"

Extract updater-script and modify it using the example below.

Replace the original updater-script within the .zip.

Flash modified CM13 .zip.

Original

if range_sha1("/dev/block/platform/msm_sdcc.1/by-name/system", "28,0,32767,32768,32770,32825,32827,33307,65535,65536,65538,98304,98306,98361,98363,98843,130863,131072,131074,163840,163842,163897,163899,164379,169016,196608,196610,197090,215039") == "48415cce2a9134753f377a68cdd8765415275103" then
if range_sha1("/dev/block/platform/msm_sdcc.1/by-name/system", "34,32767,32768,32770,32825,32827,33307,65535,65536,65538,66050,97792,98304,98306,98361,98363,98843,130863,131072,131074,131586,163328,163840,163842,163897,163899,164379,169016,169528,196096,196608,196610,197090,215039,215040") == "2e33035f18150942c354c3015b441f0d079ae37b" then
ui_print("Verified the updated system image.");
else
abort("system partition has unexpected non-zero contents after OTA update");
endif;
else
abort("system partition has unexpected contents after OTA update");
endif;

Modified

if range_sha1("/dev/block/platform/msm_sdcc.1/by-name/system", "28,0,32767,32768,32770,32825,32827,33307,65535,65536,65538,98304,98306,98361,98363,98843,130863,131072,131074,163840,163842,163897,163899,164379,169016,196608,196610,197090,215039") == "48415cce2a9134753f377a68cdd8765415275103" then
ui_print("Verified the updated system image.");
else
if range_sha1("/dev/block/platform/msm_sdcc.1/by-name/system", "34,32767,32768,32770,32825,32827,33307,65535,65536,65538,66050,97792,98304,98306,98361,98363,98843,130863,131072,131074,131586,163328,163840,163842,163897,163899,164379,169016,169528,196096,196608,196610,197090,215039,215040") == "2e33035f18150942c354c3015b441f0d079ae37b" then
ui_print("Verified the updated system image.");
else
abort("system partition has unexpected non-zero contents after OTA update");
endif;
endif;
[Nexus 7 (2013) Original Android Development] tungdil:
[MENTION=4926181]QuietusPlus[/MENTION] Thank you very much!

There is an easier solution though, IMHO (that will work for other CM-based ROMs as well). Just comment out the lines, i.e. add a hash (#) at the beginning of each line, like so (these lines are from crDroid ROM):

[COLOR="Red"]#[/COLOR]ui_print("Verifying the updated system image...");
[COLOR="Red"]#[/COLOR]if range_sha1("/dev/block/platform/msm_sdcc.1/by-name/system", "28,0,32767,32768,32770,32825,32827,33307,65535,65536,65538,98304,98306,98361,98363,98843,131071,131072,131074,163840,163842,163897,163899,164379,166302,196608,196610,197090,215039") == "947e1e12c28b4b0f3dcbc867bc410f4786c1bc11" then
[COLOR="Red"]#[/COLOR]if range_sha1("/dev/block/platform/msm_sdcc.1/by-name/system", "34,32767,32768,32770,32825,32827,33307,65535,65536,65538,66050,97792,98304,98306,98361,98363,98843,131071,131072,131074,131586,163328,163840,163842,163897,163899,164379,166302,166814,196096,196608,196610,197090,215039,215040") == "3c55b4dff8589604d8415155d43f0c20ee30e799" then
[COLOR="Red"]#[/COLOR]ui_print("Verified the updated system image.");
[COLOR="Red"]#[/COLOR]else
[COLOR="Red"]#[/COLOR] abort("system partition has unexpected non-zero contents after OTA update");
[COLOR="Red"]#[/COLOR]endif;
[COLOR="Red"]#[/COLOR]else
[COLOR="Red"]#[/COLOR] abort("system partition has unexpected contents after OTA update");
[COLOR="Red"]#[/COLOR]endif;
[Nexus 7 (2013) Original Android Development] nkk71:
I don't know your device, but you may need to look at variants shell script too, if that exists on your device / ROM
[Nexus 7 (2013) Original Android Development] QuietusPlus:
Correct me if I'm wrong, but commenting out the entire section also disables any verification. Say something went wrong during the flash, the script wouldn't know... Might be better to modify like I've posted, just to be safe?
[Nexus 7 (2013) Original Android Development] tungdil:
Well... I guess this probably is a philosophical question.

As far as I know a lot of custom ROMs do not perform any verification form the updater scripts. I personally believe the risk that something goes wrong during flashing a CM based ROM is not higher than for other ROMs and, I am not sure that doing 1/2 verification is really better than nothing. Finally we're flashing a secondary ROM (which btw is dangerous as such and not supported by a lot of custom ROM developers anyway) and if something goes wrong we're not left with an "unuseable device".

But, ... this is just my opinion and maybe this discussion is anyway too much OT...
[Nexus 7 (2013) Original Android Development] madbat99:
A lot of roms actually do perform some checks in the updater script.
[Nexus 7 (2013) Original Android Development] tungdil:
No problem to change the wording to "some". Even though, at least in the updater scripts of the following MM-ROMS for flo I couldn't find the SHA1 verification: PureNexus, MoRoM, BadBoyz, OctOS, and CleanRom. On the other hand side I guess most CM-based MM-ROMs have the verification code in their updater script (unofficial MM AIPC doesn't).

Furthermore I didn't come across the "checksum-problem" in MultiROM prior to CM13. And at least the updater script in cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-flo.zip (I guess this is also true for other Lollipop ROMs) doesn't do the SHA1 verification.
[Nexus 7 (2013) Original Android Development] Pawel01:
The problem seems to be making it all bootable.

I've made a dirty flash of the new CM 13 nightly (before I had there CM 12.1 as my primary Rom and stock 5.1.1 as secondary - running the modified Version of multirom to flash MM, beeing posted a few days ago in the multirom-thread). After flashing CM 13 as primary Rom I have installed the open gapps. So far, everything was fine. But then I could not boot the secondary Rom. So I have flashed a kexec-hardboot-kernel (CM 12.1). My secondary stock 5.1.1 botted then, but my primary CM 13 didn't.

Then I've tried flashing another kernel with kexec-hardboot-patch (elemental x). I took the 6.0.1 stock kernel and both ROMs booted, but the colors in the primary ROM were a desaster.

Do you have any idea, which kernel I could take to make both Roms bootable?

Thanks in advance for any help! ☺
[Nexus 7 (2013) Original Android Development] anon-anon:
I had a similar problem to you but I solved it as follows,

1. installed stock MM 6.0.1 from Ubuntu (edit install script to remove -w if you don't want your data wiped during installation) and adb. Wiped Dalvik and cache. Reboot.

2. installed TWRP_multirom_flo.img fastboot from Ubuntu

3. flashed hacked multirom-20151113-v32-UNOFFICIAL-flo.zip from Nexus 7

4. flashed ElementalX-N7-5.06 from Nexus 7 for stock MM 6.0.1 as primary. Wiped Dalvik and cache. Reboot.

5. flashed BetaSuperSU 2.6.2-3. Reboot.

6. edited update-script in ROM by commenting out offending code as described earlier in thread. Flashed CM13-NIGHTLY as the secondary ROM.

Works great! I didn't bother with adding a custom kernel to the CM13 ROM as its based on MM 6.0.1 (MMB29K) and ElementalX-N7-5.05-cm is still only up to Android 6.0. Also I haven't tried flashing SuperSU on it, I just turned on the native superuser function in developer tools. Updated SuperSU on primary to 2.6.4 by flashing - no problem. To update CM13- NIGHTLY update-script in ROM needs to be edited every time (til its fixed) so automatic update in the ROM doesn't work.
[Nexus 7 (2013) Original Android Development] tungdil:
In case you haven't solved this yet...

You'll have to use a CAF (not AOSP) MM kernel for CM13. That's why the CM 12.1 kernel (Lollipop) and Elemental 6.0.1 (AOSP) didn't work. You could try for example ElementalX-N7-5.05-cm or Glitch-flo-r412-CMfull.zip.
[Nexus 7 (2013) Original Android Development] Pawel01:
Thanks a lot! I've tried out now with ElementalX-N7-5.05-cm and both ROMs are now bootable ??

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] bahha:
is MultiRom compatible with Android 6.0.1 . when I flash a rom I get boot loop to recovery . when removed everything works , as soon as I inject boot, it gets to boot loop again .

how do I fix this Rom is Pure nexus project 6.0.1

ElementalX latest .
[Nexus 7 (2013) Original Android Development] thereal_bigjake:
This will help http://xdaforums.com/showthread.php?p=63822404
[Nexus 7 (2013) Original Android Development] WyldOne91:
So I was trying to flash xposed to my current ROM and got this error which was just after flashing the update so I could use MultiROM with Marshmallow (which works perfectly, thank you). Is this error that I am seeing due to that update? Is there an easy way for me to fix this? Thanks for any pointers I'm advance.
[Nexus 7 (2013) Original Android Development] matt4321:
flash the arm xposed, not arm64 or x86
[Nexus 7 (2013) Original Android Development] osm0sis:
Actually the original updated zip (by the guy who built it) got fixed, so better to link to that:

http://xdaforums.com/showthread.php?p=63756363#post63756363

He deserves our thanks. :)
[Nexus 7 (2013) Original Android Development] bahha:
Thanks , it works

I wonder why it's not implemented in the official app !
[Nexus 7 (2013) Original Android Development] WyldOne91:
I'm an idiot. Thank you!
[Nexus 7 (2013) Original Android Development] badhon_raj:
anyone tested it with Marshmallow?

My nexus7 doesn't boot after installing multirom.

the screen becomes blank after google logo and reboots to recovery if select to boot from internal.

I haven't added secondary ROM yet though.

Device: deb

Base ROM: Bliss 6.0 (CM 13)

Kernel: ElementalX

Recovery: moded twarp

Can anyone please help?
[Nexus 7 (2013) Original Android Development] osm0sis:
I linked the original creator of the fixed zip above. It's working fine on my flo with Stock ROM + franco.Kernel r24, Firefox OS and UbuntuTouch. Remember to thank his post since he put in the effort to compile it for us all!
[Nexus 7 (2013) Original Android Development] badhon_raj:
Thanks.

I was getting assert error. then replaced back flo with deb in the updater script and it worked.

Thanks. :)

Update: It works great. http://xdaforums.com/showthread.php?p=63756363#post63756363
[Nexus 7 (2013) Original Android Development] osm0sis:
No, koron393 is the correct file, and it works for both (as it should). :good: