yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] Wongher:
Multirom 30c

[MENTION=5093942]KINGbabasula[/MENTION]

I flashed the 30b Multirom and nothing else, than my secondary ROMS boot without problem, with your 2.8.4 recovery.

if i flash the 30c Multirom with the same recovery no one secondary BOOT.

can i do something to help you and let you understand the problem?

many thanks
[ONE Android Development] mas_rock:
When I Boot into secondary rom Powered by Android That's appered and after that it boot into AK logo then it's reboot in to twrp recovery Not in the rom.
[ONE Android Development] tobitege:
Just to clarify: it must disappear after 3 seconds, if it stays longer than you have older firmware.
[ONE Android Development] mas_rock:
Now I am go back to the Multirom V30b and TWRP2.8.3 How can I go back to the older version?

I am using multirom App to update.
[ONE Android Development] laulau42400:
Adding new rom in MultiRom all.

Envoyé de mon A0001 en utilisant Tapatalk
[ONE Android Development] Wongher:
https://www.androidfilehost.com/?fid=95855108297851536

MultiRom 30b

Edit: [MENTION=5831162]mas_rock[/MENTION] flash it in primary screen recovery
[ONE Android Development] mas_rock:
SO, I have to flash THis Zip In my primary rom? Then clear cache/delvik ?

And No need to flash TWRP 2.8.3 recovery?
[ONE Android Development] Wongher:
ok , ok and no need downgrade recovery.

tell if it works

hope it helps and it works.
[ONE Android Development] mas_rock:
That dosen't bricked right?

And I already have 3 Rom as my secondary rom so After Flash this v30 b zip all rom will be saved?
[ONE Android Development] Wongher:
no, that doesn't brick device, and the rom will not be erased.

usually it's like that.
[ONE Android Development] mas_rock:
After flashed multiromv30b when I press reboot and select primary Rom then no 1 +logo come but after a minute it reboot into safe mode m scared and until then I don't reboot yet becuz of it s won't turn on again after that so m scared ...and I can not access now multirom app after flashed v30b ..so help
[ONE Android Development] kouss77550:
In safe mode you won't be able to use user app. If it booted in safe mode it will certainly boot normally. Just reboot and it should work

Press thanks button if I've helped you
[ONE Android Development] mas_rock:
Yes its work but I can seen 1 + logo and powered by android text in bottom without it will boot up so help me

To get back that logo and text plz
[ONE Android Development] ek69:
I've used multirom and sometimes it's just a black screen and no boot logo like you, but it does work and boot up primary ROM.

Try booting secondary and see what happens. It's random for me.

Sent From Lollipopified Bacon Goodness!
[ONE Android Development] Natakranta:
Primary SlimSaber LP. Firmware updated to CM12.

Updated from MultiROM 30b and TWRP 2830 Jan.05 to MultiROM 30c and TWRP 2840 Jan.24 - Secondary ROM (SlimLP 5.02) is boot looping on ROM booting animation. TWRP 2840 Jan.24 is not able to change spalash screen using Materialiezed Theme both ways: native TWRP 2840 or Theme osmosis script.

I falshed back MultiROM TWRP 2830 Jan.05 - Secondary ROM is boot looping on ROM boot animation.

I flashed back MultiROM 30b using zip linked few posts above - secndary ROM is booting fine.
[MENTION=5093942]KINGbabasula[/MENTION], what info can I provide you to help debuging it?
[ONE Android Development] kantjer:
Hadn't even seen there was a new app and recovery, thanks for the heads up. But based on your post I will wait upgrading them.
[ONE Android Development] kalevs:
exactly same case here - putting back MultiRom30b saved my day - managed to boot to secondary ROM again (SlimLP 5.02)
[ONE Android Development] Natakranta:
The same. Back on 30b and secondary SlimLP is booting fine, I'm routing from it now.

Other thing is splash screen change not working in multiROM materialised theme 284x.v2 on multiROM 2840 Jan.24. I tried both ways, through new native TWRP img flash and through the theme which is using osmosis script.

Edit

I managed to change splash screen on TWRP 2840 Jan.24 with materialised theme 284x.v2. I deleted recovery.img file from TWRP/flashify

Downgraded to multiROM 30b and no problem booting secondary ROM.

Edit 2:

MultiROM TWRP 2840 Jan.24 - my exFAT formatted 64GB microSD plugged through Meenova adapter is not being detected. It was not working in MultiROM TWRP 2830 Jan.05. Last time it was working was on MultiROM TWRP 2820 Dec.13 if I recall correctly.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] KINGbabasula:
Tomorrow I'm compiling MultiROM again, it should work like v30b
[ONE Android Development] Natakranta:
Than you very much. Please don't read me as complaining. I appreciate your continuous support to MultiROM on OPO a lot. Well, we wouldn't have you without you ;)

What with TWRP not seeing OTG mounted microSD? Could you try building MultiROM TWRP on base of bacon TWRP 2841?

Edit: [MENTION=5093942]KINGbabasula[/MENTION],

I've just tested. Official TWRP 2841 sees and reads my microSD plugged through Meenova adapter.

MultiROM TWRP 2820 Dec.13 does not see external storage, neither any of following MultiROM TWRP versions (2830-Jan.05, 2840-Jan.24)

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] chealyjazz:
What I had to do was update the multirom app in the primary ROM not the secondary I was using at the time .If you go on to the xda multirom forum its happened to a few people. I still had to do a clean install of my secondary ROMs afterwards though.
[ONE Android Development] skodaslx:
I'm able to boot slimsaber LP as secondary with the newest version of multirom. Don't know if there is a difference between SlimLP and SlimsaberLP and if this helps.

Gesendet von meinem A0001 mit Tapatalk 2
[ONE Android Development] tobitege:
The "saber" version uses "SaberMod" toolchain for compilation. Other than that it's the builders' choice of cherry-picking anything else into the rom when compared to other "editions", like different kernel commits etc.
[ONE Android Development] skodaslx:
Thanks for your answer. I think it was not clear what I wanted to say. What I wanted to say, is that I could boot slimsaber as secondary where others had problems with SlimLP. And I don't know if this could help to find the problem with booting SlimLP, because I don't know if there are differences between slimsaber and SlimLP when it comes to multi boot. Hope this makes clearer what I wanted to say.
[ONE Android Development] tobitege:
Ok, gotcha... can you p/m me the link to SlimLP rom that doesn't work. I'd try it out, too. Most likely just a few minor changes in the updater-script required related to how /system and/or data is mounted. With yesterday's update of MultiRom it might even work as BlissPop (as an example) is now suddenly installable out-of-the-box as a secondary rom whereas with the same script from previous build it errored in MultiRom.
[ONE Android Development] skodaslx:
I didn't tried SlimLP myself, just read a page back that some others had problems.
[ONE Android Development] KINGbabasula:
I've just updated MultiROM, I have also a recovery update which should fix OTG but it isn't booting because of some SELinux things, I'll have a look at it tomorrow
[ONE Android Development] kantjer:
Tried to update the MultiROM app twice now, but after reboot the app is still giving the message v30d is available for update.

Also for some reason my OnePlusOne is now listed as not officially supported in the app. Can't remember ever seeing that before.
[ONE Android Development] stab244:
Same. I think the issue is that in the multiROM boot menu, the version is listed as just 30, causing the app to think it's not up to date.

Sent from my bacon
[ONE Android Development] Natakranta:
The same for me. Tried 2 times and once manually in recovery, still MultiROM Manager app shows version 30 and available update to v.30d

[MENTION=5093942]KINGbabasula[/MENTION], when working on new TWRP, could you please check as well this:

adb is not working on TWRP 2840 Jan.24, MTP enabled or not.

I flashed back TWRP 2830 Jan.05 and adb is working after enabling MTP under Mounts menu. It works further even if I disable MTP upnuntil I disconnect USB cable from PC. Then to make adb work I had to enable MTP back.

Talking about MTP it works with PC, it detected it immediately and I could display contents of my phone's storage in TWRP 2830 Jan.05.

I'm guessing that broken adb in 2840 is connected to not working MTP.

Thanks!

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] :
Any news about the fix?
[ONE Android Development] KingBeike:
Why not 2.8.4.1? or just wrong displayed ?
[ONE Android Development] supermax:
For me is the same, no OTG
[ONE Android Development] tobitege:
Most recent update (24th) for recovery (almost) always reboots upon Mount|Enable MTP. Previously I had a workaround to unmount /data first, but that no longer works for me.

Will flash older release till next update.
[ONE Android Development] the_mentor:
I am new to MultiROM and I am trying to dual boot CM11 and CM12 nightlies is that possible or is there any known issues with that configuration?
[ONE Android Development] stab244:
CM 12 nightlies have their own radio and some other firmware files that don't work on CM 11. You can run both but then you'd have to flash the firmware for CM 11 before you rub CM 11 and flash the firmware for CM 12 when you want to run CM 12. A bit of a hassle.

Sent from my bacon
[ONE Android Development] tobitege:
[MENTION=2736461]the_mentor[/MENTION]: additional note regarding firmware: always flash it with primary recovery "Install" button, not from within MultiRom roms pages.
[ONE Android Development] the_mentor:
If I understand you guys correctly are you saying i will need to install CM12 as the primary ROM and CM11 as the multiROM?
[ONE Android Development] stab244:
I have CM 11 as primary. He's saying that you flash firmware onto primary ROM even if your primary ROM isn't what the firmware is for. So when you want to boot CM 12, you still flash the CM 12 firmware onto primary even if your primary isn't CM 12.

Sent from my bacon
[ONE Android Development] tobitege:
[MENTION=2222926]stab244[/MENTION]: +1

Firmware is outside of any rom partition and is global for any rom you boot, it persists across (custom) rom installs/updates/wipes. Exceptions are CM nightlies and of course stock factory images which contain a full set of firmware files (8 in total, incl. modem). HTH.
[ONE Android Development] duke_mac_l:
I have the same constellation.

I have cm11s in primary and some cm12 and lollipop ROMs in secondary.

I flashed the cm12 firmware and everything worked well.

No need to change the firmware files to boot up cm11s.

The only problem I find out is that I can not use the power bottom to wake up my screen when it's blank. I have to use the flipcover.

But for me these is ok.
[ONE Android Development] MMWolverine:
You can still have cm11/s as primary rom with the old modem/firmware and flash this proximity sensor fix on any CM12 as secondary. This was originaly posted by @Natakranta, so credits to him, I only made it a flashable zip. Mind you that Lollipop roms dual-booted in such a way will still have issues like random reboots, but it all comes down to your way of use. For example, I'm developing a toolbox app and need both platforms, however, not recommended as a daily driver.

Edit: one more thing, you'll also need to flash an older kernel on secondary cm12 rom (from the Multirom menu). Newer versions bootloop without the updated firmware, so use for example Boeffla 3.0-beta4 or AK.087.
[ONE Android Development] the_mentor:
Do you have a link or a guide on how to install the CM12 firmware ?

I'm trying to find a way to only install the the CM12 firmware.

Thanks.
[ONE Android Development] tobitege:
You can flash the one from my signature (switch to web view if using Tappatalk). Only need to flash it once from primary recovery screen (not from within MultiRom rom page!) and then forget about it. You won't need to flash it ever again unless there's a newer firmware coming out as it persists across regular rom install/update/wipes. Afaik only CM nightlies and official/stock images include firmware that would overwrite it again, hth.
[ONE Android Development] the_mentor:
That was exactly what i needed thanks !!

Hopefully this setup will be stable enough.

The main reason i wanted to dual boot CM11 and CM12 is to see if i can live without xposed....
[ONE Android Development] Natakranta:
Read my post in SlimSaber LP thread and few on next page there. You will find lots of details and different configuration examples and explanations.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] Wongher:
Multirom 30d

can someone post a link to download it?

thanks
[ONE Android Development] mas_rock:
For those who have problem with proximity sensor ( like i was before. >>I Have CM 11S as my primary rom and all CM12 as secondary rom ..)

So, please flash CM 12 firmware On primary rom.

And problem solved ...

Thanks to [MENTION=4877142]tobitege[/MENTION]
[ONE Android Development] MMWolverine:
Problem isn't solved that way, unless you only use lollipop roms. New fw messes up cm11s with sod's and such.
[ONE Android Development] mas_rock:
yes you right . but if you want to used Cm 12 as daily driver than flashed CM12 firmware and if you want to use CM 11 as daily driver than flashed CM11 firmware simple...
[ONE Android Development] tobitege:
Little "tutorial" especially for MultiRom users (novice and advanced):

Ever needed to get/put files from/to another secondary rom?

Why this could be of interest to you?

Booting between roms takes time which hurts people with little patience. :)

Just want to grab that one working mixer_paths.xml file from another rom after screwing it up with a mod?

Other rom doesn't boot anymore - for whatever reason - and you need to recover files from its data partition?

Forgot to set permissions of a changed build.prop or want to get a copy of it or restore it within other rom?

Some mod or app activated an "init.d" script and rom doesn't boot anymore any you want to remove it?

Or you'd like to copy over a working init.d script from another rom to your currently booted rom?

We'd first need a root-enabled file browser like FX, Total Commander, ES File Explorer or any other.

All MultiRom stuff including all your installed secondary roms resides here:

/data/media/multirom

and all the roms are then of course in

/data/media/multirom/roms

with each rom listed by its name as you see it in MultiRom app and boot menu.

Some file explorers allow to maintain a list of bookmarks, so it may be very convenient to set a bookmark here for later use.

As an example I'd like to grab the mixer_paths.xml file from my rom "testrom":

Within my file explorer I make sure to have root access/usage enabled first. Some apps have an explicit option to use/enable root permissions for file operations.

Then just navigate to /data/media/multirom/testrom and from here it is the same path as on your primary rom.

So go further down the "regular" path like "system/etc/" and find within that folder the "mixer_paths.xml" file.

The folders path to the file would then be /data/media/multirom/testrom/system/etc/

Now do whatever you want to do with that file, like copying it, correcting its permissions etc.

That's all! :)
[ONE Android Development] KINGbabasula:
Thanks for this post, I've added it to the FAQ
[ONE Android Development] neotoky:
sleep of death

First time installing multirom on my phone. I have color os as primary and a twrp backup of my stock 44s with franco kernel as my secondary. My issue is when the screen turns off on the secondary rom, it never turns back on again. I tried double tap and pressing power button to no avail. I have to obviously hild down the power button to reboot. I have been reading that the issue is common with the lollipop roms but I obviously have no lollipop roms installed.
[ONE Android Development] tobitege:
You might have to update your firmare, but I'm not on KK anymore. Here are some good links included.
[ONE Android Development] neotoky:
Any special way to flash this? Through TWRP? I ask because wouldn't that interfere with color os
[ONE Android Development] tobitege:
Flashing would be done through TWRP in any case, but always on primary rom, not from within MultiRom pages as firmware flashes don't work otherwise. I'm unfamiliar with ColorOS but thought it installed itself also with its own firmware. Newer firmware may or may not cause issues with it, but if you'd have a backup of the old one, you could always flash that again.

But once you flash a firmware, it is a "global" part on your phone, i.e. ALL roms within MultiRom will have to work with it.
[ONE Android Development] neotoky:
So it's not a good idea to flash a cm firmware over color os since it is my primary because it would potentially brick my phone or not? The color os I installed is supposedly the latest and it should have installed the newest firmware.

Can someone with color os installed shed some light on this. Thanks
[ONE Android Development] moosha:
What if your primary rom isn't working and you want to get some data off it using a secondary rom? Where can I find it?
[ONE Android Development] tobitege:
Your primary rom is also available under "/data/media/multirom/roms/Internal". :)
[ONE Android Development] neotoky:
I found the solution. Can't believe how simple it was. It was thanks to havok over at the oneplus one forums. On cm, under display and lights, I had to turn off prevent accidental wake up. No more sleep of death so for those who have the same issue as me, that's how you fix it.
[ONE Android Development] moosha:
Thanks :)
[ONE Android Development] neotoky:
Well of course, another issue that still deals with sleep of death but this time is when I make a call. When I make a call the screen goes black and it doesn't go back on. It dials out and when I get a call i can answer but it goes to black. When I double tap I only see the capacitive buttons light up. I'm stuck once again.
[ONE Android Development] scott62185:
Newb question, to update multirom I just flash the zip in TWRP?
[ONE Android Development] tobitege:
Easiest way is to use the MultiRom app itself as it will tell you - if needed - what it needs to update and just tap a button and reboot.

---------- Post added at 03:46 ---------- Previous post was at 03:42 ----------

This might be better placed in an Color OS thread I guess as MulitRom isn't the cause, so to speak. Personally, I'd recommend to drop ColorOS and jump onto current CM-12 based rom with current firmware as those issues should not happen (anymore). The prevent accidental wake-up was mostly the issue there, too.
[ONE Android Development] Oreol:
In the "accessibility option" turn on "power button ends call".. this way you can cancel current call thus your screen will back on. Of course during call the screen will blank. That's my solution otherwise you have to reboot the phone forcibly.. :)
[ONE Android Development] mcbyte_it:
cm12 as secondary

I used Multirom before to boot multiple kk and it works just fine, now i am trying to put cm12 in secondary, and it is not working as expected:

first install, daily 28/01/2015 during boot it restarts, found that I have to use new images for modem/sdi/sbl/etc, so i took the CM12 zip and fastboot flash all files except system to the main OnePlus, current rom still working smooth (Mahdi KK).

Now I can boot to CM12, but WiFi is not working in any way, says connecting then stops, then repeats, 3G data is working but not wifi. anybody knows what's the issue?

Thanks
[ONE Android Development] KingBeike:
Getting black screen and unresponsive device with 24.01.15 recovery...2.8.4...seems we need 2.8.4.1 ?
[ONE Android Development] amrmorsy:
That's because you need to install the new Alpha Modem by CM. I think...
[ONE Android Development] Shadowghoster:
Had the same Problem on Euphoria., but resolved it:

If your router is giving you a static IP, than add your IP in the advanced wifi-config (change from dhcp to static and insert your IP). After doing that I haven't had problems any more.

Regards Shadowghoster
[ONE Android Development] AhmedFaiz:
i am not able to flash the official PA alpha build on both internal and secondary rom! anyone having the same issue here? or the recovery need to be updated to flash properly!

badly need to try out this build. any workaround or help if anyone here knows how to fix this issue.
[ONE Android Development] tobitege:
Error screenshot would help. I had installed PA as secondary recently, but don't remember if I had to change anything.

And obviously newest firmware could as well be the solution.
[ONE Android Development] ayysir:
Multirom needs to be updated to 2.8.4.1 for PA to work on it
[ONE Android Development] AhmedFaiz:
[MENTION=5093942]KINGbabasula[/MENTION] can you update the multirom please.. I am not able to flash official PA yet. I am hearing reports for some users it's working but for me even after changing updater script I was not able to flash it. Hoping for an update soon.

Slimsaber slimlp/Ak
[ONE Android Development] ek69:
Make sure you're flashing complete updated firmware from cm12 builds as of Jan 20 or so or newer.

See above

See above and below, lol. Basically if it's a TZ comparison error then you need updated firmware not just alpha modem.

I remember your post when you said it worked fine as is without changing updater script. It was because multirom updated and from that point forward no changes were needed in updater-script file. This also applied to blisspop ROM as well I believe.

Here is a link to the updated firmware from blisspop ROM. The very first file is what's needed

http://downloads.blissroms.com/BlissPop/Official/bacon/

//edit

I just found out there's an official paranoid android lollipop version out now lol so maybe it actually doesn't work.... Will find out lol

//edit 2

Tried it out and failed, but there's nothing wrong with multirom or the recovery version I would bet

It's reporting device as bacon when updater-script file is looking for a0001 which is probably an easy fix but it's too late here for me to play with it lol

Cheers

Sent From Lollipopified Bacon Goodness!
[ONE Android Development] Goggle81:
I think you lost the bet ;)

An update of recovery is needed (or change update script in zip)
[ONE Android Development] AhmedFaiz:
Was talking about official PA build. I changed the updater script in the ROM still it's not flashing..if you have a guide how to fix it please share..

I am already on the latest firmware and modem.

I already used unofficial pa as my secondary before official was out, it worked fine..

Slimsaber slimlp/Ak
[ONE Android Development] MMWolverine:
PA alpha flashes just fine as secondary. I tried on twrp 2.8.4, although I'm using 2.8.3 because of the mtp issue.

In updater-script replace

with
[ONE Android Development] laulau42400:
Hello, cool, can you put the udapter file. Edit script to download? Thank you

Envoyé de mon A0001 en utilisant Tapatalk
[ONE Android Development] MMWolverine:
Replace meta-inf folder and you're good to go. ;)
[ONE Android Development] tilaksidduram:
who ever is facing issues in flashing the PA alpha1 zip on your OPO as seconday rom, you need to edit the "updater script" before you flash the zip.

steps to do that is just extract the updater_script from the zip file and delete the below mentioned line.

ifelse(is_mounted("/system"), unmount("/system"));

once it is deleted save the file and copy it back into the zip file into the same folder and then flash the zip on your phone via the recovery.

The same line can be deleted on other roms too that are being installed as secondry. its just that some roms have too many "if" & "else" statement in the updater script file. just delete those "if" & "else" line and you should be good to flash the rom.