[MOD][FEB 10] MultiROM v33

ELB27

Senior Member
Jun 8, 2012
76
54
0
Already lost the MultiRom bootscreen two times and had to reflash the zip. Strange.

Using Stock and CyanogenMod.
It is caused (a far as I know) by updating your primary ROM/kernel. After such update, you should go to advanced - > multirom and do "inject curr. Boot sector"

EDIT: Here is a quote from the OP on how to update primary ROM (or kernel) :
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.
Sent from my Nexus 4 using Tapatalk 4
 
Last edited:
  • Like
Reactions: cyberon and S0NB

Reamer09

Senior Member
Sep 28, 2008
628
153
0
+1 Always i have tried Ubuntu Touch it didnt boot for me... After selecting it in the boot menu my device restarts and stays in the "google" logo forever :(
I used the latest nightly (as of last night) and Ubuntu Touch booted for me. Just followed the OP step by step, I don't know this stuff well enough to get fancy with it. It sits at the Google logo for awhile and then turns black for awhile (a few minutes on both) but it eventually boots. Sometimes it just stays black and never boots, but a reboot fixed that. I tried Ubuntu Touch by itself a couple weeks ago and Wi-Fi and 3g worked, but it isn't now. I highly doubt this has anything to do with MultiRom, but I can't prove otherwise. Currently triple booting Android, Firefox OS, and Ubuntu Touch!
 

MikeCriggs

Recognized Developer / Inactive Recognized Contrib
Dec 24, 2010
2,748
5,832
0
Catskills, NY
twitter.com
I used the latest nightly (as of last night) and Ubuntu Touch booted for me. Just followed the OP step by step, I don't know this stuff well enough to get fancy with it. It sits at the Google logo for awhile and then turns black for awhile (a few minutes on both) but it eventually boots. Sometimes it just stays black and never boots, but a reboot fixed that. I tried Ubuntu Touch by itself a couple weeks ago and Wi-Fi and 3g worked, but it isn't now. I highly doubt this has anything to do with MultiRom, but I can't prove otherwise. Currently triple booting Android, Firefox OS, and Ubuntu Touch!
There's an issue between Ubuntu Touch and Multi-ROM that is causing networking issues ever since they started using MIR. Using Ubuntu Touch as your primary ROM remedies the issue, though I haven't tried it with Android as secondary.

Sent from my Nexus 7 using Tapatalk 4
 

Reamer09

Senior Member
Sep 28, 2008
628
153
0
There's an issue between Ubuntu Touch and Multi-ROM that is causing networking issues ever since they started using MIR. Using Ubuntu Touch as your primary ROM remedies the issue, though I haven't tried it with Android as secondary.

Sent from my Nexus 7 using Tapatalk 4
Ah, ok. Thanks for the explanation. Wonder if this will cause issues again if they decide to release 14.04 with XMIR. Twildev made a comment on his YouTube channel that they may steer clear of that situation since 14.04 would be an LTS release though.

Sent from my Nexus 4
 

DaGr81

Senior Member
Aug 9, 2010
97
23
0
Kathmandu
How to multiboot Firefox OS:
- Download both system and UI .zip files from the Firefox thread
- Put them on your phone
- Reboot to your recovery
- Go to Advanced, multiROM, add ROM
- click android at the top, and click don't share (it worked fine for me that way), then click next
- select zip file, and pick the system.zip
- when done, go to Advanced, multiROM, list ROMs, and select the rom you just flashed.
- click flash zip and flash the UI.zip
- when done just reboot, and select the firefox os from the boot menu
i'm on cm 10.1.3 but supplied kernel in main post is for 10.2. any way to solve it?
 

cewrld

Senior Member
Aug 4, 2013
183
81
0
Thank you. I am using Stock+Slim ROM and there is no problem. It will help all of us to try and configure new ROMS without completly lose our other system configurations.
 

Tasssadar

Inactive Recognized Developer
Dec 31, 2010
818
6,126
0
Brno
tasssadar.github.com
Okay, let's talk about Ubuntu Touch.
The method we're using to install Touch now (the ZIP files) is deprecated, and _might_ be the cause of some problems. It is now supposed to be installed via phablet-flash tool, as described on Ubuntu Touch wiki. It basically downloads files from http://system-image.ubuntu.com, pushes them to the device along with "installation script" file and lets their modified recovery do the installation itself.
Installation isn't a problem, right now I can do the same thing as Touch's recovery and run their installation script on secondary ROM. Problem is downloading those installation files - they are not sorted by anything a human could use, they are supposed to be downloaded by an application which parses metadata and selects the right files accordingly. I could modify phablet-flash tool to download files for MultiROM and to not rewrite my TWRP with their recovery, but that would still be a bit problematic (you need Ubuntu on your PC to run phablet-flash). So, I'm thinking an Android app - some kind of "MultiROM manager", which could install/update MultiROM and recovery and also download the right Ubuntu Touch files, which would then be installed via recovery. The catch here is that the Android app would need to download ~250-300 MB of data, which might not be something you want to be doing on WiFi.
What do you think?

It is a bit hard for me to make things work properly for mako, too, as I don't have the device. By the way, mobile data won't work unless you remove PIN from your SIM card - the interface to unlock simcard isn't there yet.

BTW, I also managed to make Ubuntu Touch OTA updates work with MultiROM.
 

bobo1337

Senior Member
Nov 8, 2012
444
124
0
Okay, let's talk about Ubuntu Touch.
The method we're using to install Touch now (the ZIP files) is deprecated, and _might_ be the cause of some problems. It is now supposed to be installed via phablet-flash tool, as described on Ubuntu Touch wiki. It basically downloads files from http://system-image.ubuntu.com, pushes them to the device along with "installation script" file and lets their modified recovery do the installation itself.
Installation isn't a problem, right now I can do the same thing as Touch's recovery and run their installation script on secondary ROM. Problem is downloading those installation files - they are not sorted by anything a human could use, they are supposed to be downloaded by an application which parses metadata and selects the right files accordingly. I could modify phablet-flash tool to download files for MultiROM and to not rewrite my TWRP with their recovery, but that would still be a bit problematic (you need Ubuntu on your PC to run phablet-flash). So, I'm thinking an Android app - some kind of "MultiROM manager", which could install/update MultiROM and recovery and also download the right Ubuntu Touch files, which would then be installed via recovery. The catch here is that the Android app would need to download ~250-300 MB of data, which might not be something you want to be doing on WiFi.
What do you think?

It is a bit hard for me to make things work properly for mako, too, as I don't have the device. By the way, mobile data won't work unless you remove PIN from your SIM card - the interface to unlock simcard isn't there yet.

BTW, I also managed to make Ubuntu Touch OTA updates work with MultiROM.
It would be great if you make app! :)

Sent from my Nexus 4 using Tapatalk now Free
 

aqsede

Senior Member
Mar 16, 2013
98
16
0
MACHANG
Downloads

1. Main downloads

MultiROM: multirom-20131005-v16-mako.zip
Modified recovery (TWRP 2.6.3.0): TWRP_multirom_mako_20131012.img

Kernel w/ kexec-hardboot patch (stock 4.3 - version JWRxxx): kernel_kexec_mako_430_jwr.zip
Kernel w/ kexec-hardboot patch (stock 4.3 - version JSSxxx): kernel_kexec_mako_430_jss.zip
Kernel w/ kexec-hardboot patch (CM 10.2 - older one) kernel_kexec_mako_cm102_old.zip
Kernel w/ kexec-hardboot patch (CM 10.2): kernel_kexec_mako_cm102-2.zip
(If you have CM-based ROM, try both kernels - if one gives you graphical glitches, the other one should work fine).

Mirror: http://goo.im/devs/Tassadar/multirom/mako/ (also accessible via GooManager, search for multirom)​
i noticed you have no 4.2.2 kexec-hardboot patch. im using Rootbox as internal, and its currently running 4.2.2. will you make 4.2.2 kexec support? as in nexus 7
 
  • Like
Reactions: terry6v and Rev4