[MOD][FEB 10] MultiROM v33

[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.

Sent from my Nexus 7 using Tapatalk

 

[matt4321]

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.

Sent from my Nexus 7 using Tapatalk

flash the arm xposed, not arm64 or x86

 

[osm0sis]

is MultiRom compatible with Android 6.0.1 ?

This will help ...

Actually the original updated zip (by the guy who built it) got fixed, so better to link to that:
http://forum.xda-developers.com/showthread.php?p=63756363#post63756363

He deserves our thanks.

 

[bahha87]

This will help http://forum.xda-developers.com/showthread.php?p=63822404

Sent from my Nexus 5 using Tapatalk

Thanks , it works
I wonder why it's not implemented in the official app !

 

[WyldOne91]

flash the arm xposed, not arm64 or x86

I'm an idiot. Thank you!

Sent from my Nexus 7 using Tapatalk

 

[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?

 

[osm0sis]

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?

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!

 

[badhon_raj]

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!

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://forum.xda-developers.com/showthread.php?p=63756363#post63756363

 

[osm0sis]

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

The original file uploaded by ajbiz11 was deleted so I had to use the file from pilotv.

No, koron393 is the correct file, and it works for both (as it should). :good:

 

[[email protected]]

Free space got lost after flashing secondary ROM

Hello All,

I have several ROMs installed via MultiROM (Ubuntu Touch, Firefox OS, CM12.1). But weird thing happened to my Nexus 7 (flo, 16Gb) on the weekend.
I wanted to add a new one Bliss Rom 6.0 by Team Bliss as a secondary ROM. At the first time installation failed, and I expected that free space be the same as before but I noticed it has decreased by ~500Mb. So I've tried one more time, failed and again I've lost 500Mb. I tried to google something on that but no success. So yesterday I spent a lot of time trying to find something that may take this place on my device but nothing unusual was found (checked /data/media/0/multirom and explored almost all internal memory). I decided to make one more try to add this ROM. This time installation was successful but as it was Marshmallow ROM it hasn't booted so I've removed it. Nevertheless I looked at the amount of free space that has left after all this manipulations and again - minus 500Mb

So totally I've lost 1.5Gb of internal memory. I haven't tried to re-flash factory images yet. I'd like to figure out what is going on. So I have a couple of questions here :

• Did anybody tried to flash this ROM as secondary via MultiROM ?
• Did anybody faced the similar behavior ever ?
• What can be done to find missing space and get it back ?

Appreciate any response.

 

[hachiroku]

No, koron393 is the correct file, and it works for both (as it should). :good:

wow i was struggling with frustration for about an hour. this works perfectly on my flo version. confusing as there were no instructions, but i simply flashed within recovery.

 

[dragancla]

Guys, I need some help.
So, I installed ElementalX-N7-5.07 kernel.
Then I opened the MultiROM app on my rooted stock 6.0.1 Nexus 7 2013 FLO and installed MultiROM.
When it booted into the MultiROM boot menu I picked Reboot Recovery.
Went to Advanced->MultiROM->Add ROM.
Chose the DirtyUnicorn 5.1.1 ROM and installed the pico gapps.
Booted DirtyUnicorn, all was fine.
Tried to boot back into the Marshmallow internal ROM, it just sent me back to Recovery.
Tried to reinstall supersu and then the kernel again, restarted tablet, chose Internal ROM, booted again back to recovery.
Tried restoring the nandroid backup I did just before I installed the kernel. It says:
Restoring System...
and 10 seconds afterwards:
E:extractTarFork() process ended with ERROR=255
But installing the ROM in MultiROM from backup works fine but it still doesn't boot, still sends me to Recovery.
Also, recovery keeps asking me to install SuperSU because it "does not appear to be rooted" but I keep saying "Do Not Install" every time. Not sure if relevant or not.

Anyone have any idea what I should do to boot into my internal ROM?

 

[drewski_1]

Guys, I need some help.
So, I installed ElementalX-N7-5.07 kernel.
Then I opened the MultiROM app on my rooted stock 6.0.1 Nexus 7 2013 FLO and installed MultiROM.
When it booted into the MultiROM boot menu I picked Reboot Recovery.
Went to Advanced->MultiROM->Add ROM.
Chose the DirtyUnicorn 5.1.1 ROM and installed the pico gapps.
Booted DirtyUnicorn, all was fine.
Tried to boot back into the Marshmallow internal ROM, it just sent me back to Recovery.
Tried to reinstall supersu and then the kernel again, restarted tablet, chose Internal ROM, booted again back to recovery.
Tried restoring the nandroid backup I did just before I installed the kernel. It says:
Restoring System...
and 10 seconds afterwards:
E:extractTarFork() process ended with ERROR=255
But installing the ROM in MultiROM from backup works fine but it still doesn't boot, still sends me to Recovery.
Also, recovery keeps asking me to install SuperSU because it "does not appear to be rooted" but I keep saying "Do Not Install" every time. Not sure if relevant or not.

Anyone have any idea what I should do to boot into my internal ROM?

May be the Multirom from the app, which I don't think he's been updated for MM.

Try the one in the link from the post right above yours.

Sent from my 6.0 OG Shield Tablet

 

[dragancla]

May be the Multirom from the app, which I don't think he's been updated for MM.

Try the one in the link from the post right above yours.

Sent from my 6.0 OG Shield Tablet

Fixed it by flashing https://www.androidfilehost.com/?fid=24269982086994463, as you said. Thanks!

 

[nicche]

Hi guys, I need some help too... I'm feeling close to the solution but I can't understand where I make mistake. (sorry for my bad english)

I've had already installed: Elemental XN7-5.08 kernel, the BETA-SuperSU-v2.67 and multirom recovery on my Nexus 7 2013 FLO.
At first I installed the multirom app by appstore but when I chose the internal rom ( my first rom is MM 6.0.1 sotck, rooted ) it sent me to recovery... I tried many times but the results were the same.
Then I flashed the .zip suggested by drewski_1 and it works, I mean if I choose te internal rom it starts without problems but when i try to flash miui_Nexus7_4.3.14_a387a94c89_4.4 and then i choose this rom by the multirom boot it sent me in to recovey again why?? Miui rom is too old??

 

[drewski_1]

Hi guys, I need some help too... I'm feeling close to the solution but I can't understand where I make mistake. (sorry for my bad english)

I've had already installed: Elemental XN7-5.08 kernel, the BETA-SuperSU-v2.67 and multirom recovery on my Nexus 7 2013 FLO.
At first I installed the multirom app by appstore but when I chose the internal rom ( my first rom is MM 6.0.1 sotck, rooted ) it sent me to recovery... I tried many times but the results were the same.
Then I flashed the .zip suggested by drewski_1 and it works, I mean if I choose te internal rom it starts without problems but when i try to flash miui_Nexus7_4.3.14_a387a94c89_4.4 and then i choose this rom by the multirom boot it sent me in to recovey again why?? Miui rom is too old??

i'd guess it's too old being a KK / 4.4 based ROM.

 

[Tasssadar]

MultiROM v33 and updated recovery was just released. @nkk71 and @z31s1g pretty much made this update possible by their contributions, thanks!

It has some compatibility fixes and updates TWRP to 3.0.0. CM13 now works, as well as system-less su (use BETA 2.67-20160203160253 ( http://bit.ly/m_su ) or newer).

ZIPs made from factory images of 5.1.1 and 6.0.1 can be found on androidfilehost and basketbuild (unmodified stock images, no root, no anything. Forceencrypt and verify is disabled in these).

 

[nkk71]

MultiROM v33 and updated recovery was just released. @nkk71 and @z31s1g pretty much made this update possible by their contributions, thanks!

It has some compatibility fixes and updates TWRP to 3.0.0. CM13 now works, as well as system-less su (use BETA 2.67-20160203160253 ( http://bit.ly/m_su ) or newer).

ZIPs made from factory images of 5.1.1 and 6.0.1 can be found on androidfilehost and basketbuild (unmodified stock images, no root, no anything. Forceencrypt and verify is disabled in these).

Congrats, nice to see you back.

I personally also want to thank @Captain_Throwback for his continued drive (and driving me mad ), amongst many other things... if I were to list them they would be too long)
and @z31s1g for jumping to our help so quickly (not to mention all the great things he's done for official twrp as well)

Many thanks to both of you, for all help and support.

nkk71

 

[followmsi]

Congrats, nice to see you back.

I personally also want to thank @Captain_Throwback for his continued drive (and driving me mad ), amongst many other things... if I were to list them they would be too long)
and @z31s1g for jumping to our help so quickly (not to mention all the great things he's done for official twrp as well)

Many thanks to both of you, for all help and support.

nkk71

Works like a charm .. Thanks a lot !

 

[nkk71]

Works like a charm .. Thanks a lot !

Glad it is :good::good:

took quite some work, testing, and such
hope we didnt miss anything, but the new changes will allow for easier merges rebasing, in the future