yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] KINGbabasula:
That's a check to see if you have the latest firmware installed, you can remove the line from the updater-script and it will flash correctly, it should work but I heard you will have problems with the proximity sensor, while if you flash the firmware you will have problems with the sensor in Kitkat.

You have to flash it on primary
[ONE Android Development] noeticdm:
[MENTION=5093942]KINGbabasula[/MENTION], Yes, exactly right. I have flashed two aforesaid zip. Now LP is being installed but proximity sensor in KitKat (primary rom) is not working due to new radio file; this is pretty annyoing during call. Plz guide how to fix it without compromising anything.
[ONE Android Development] KINGbabasula:
You should flash the older files from 4.4 firmware through fastboot, NON-HLOS.bin to modem and static_nvbk.bin to oppostanvbk
[ONE Android Development] noeticdm:
[MENTION=5093942]KINGbabasula[/MENTION] Links plz for those specific files. I didn't keep images of stock rom. After pushing those both will work as usual and proximity sensor issue will be solved?
[ONE Android Development] KINGbabasula:
I don't have the files, I don't care about Kitkat, aftwr flashing them the sensor will work correctly on Kitkat but not on Lollipop
[ONE Android Development] NoobInToto:
Now it does not seem consistent,I have a kmsg,bit with no problems. I will post the last_kmsg when I can reproduce the problem.

https://docs.google.com/file/d/0B4F7gn-xCXE3bko4TEVXSUZ0YmM/edit?usp=docslist_api
[ONE Android Development] KINGbabasula:
SELinux errors as always... You should set SELinux permissive in some way and it should boot correctly, I'll try to make a workaround
[ONE Android Development] noeticdm:
[MENTION=4524142]rajesh261092[/MENTION] Those who want to keep both KK and LP rom an easy guide for them:

Use the multirom app from playstore to install latest updated multirom.zip and modded TWRP with your rooted phone for easy setup. All the necessary changelogs and bugs (viz. encryption support) are fixed to be used with LP roms and can be found in the apps itself. Next,

Swapping between two KK or two LP rom is easy as each of them shares their own set of common files. With kexec patched kernel this can be done. If CM12_Update.zip and OPO_alpha_Modem_LP.zip, these two zips are not flashed latest LP rom bulids will show an error during flashing with a TZ assertion error. But these zips contain new Radio files which mismatches KK radio files. So while in call from KK rom the proximity sensor doesn't work. And the screen goes off so one lose all the control of phone during call, which turns out to be much annoying. So the most feasible and easiest solution is to flash this zip file on KK rom. This will result into non-working of proximity sensor in LP rom then. But it can be lived up with; unlike KK rom screen doesn't turn black during call, instead the screen remains on always. So finally the control over the phone is not lost, and for testing purpose it can be accepted IMHO. For fully wokring of proximity sensor in LP do flash the first two zips in this post again. Voila! you are done. Hope, this helps!
[ONE Android Development] NoobInToto:
It is permissive. Idk if it changes during boot. Anyways thanks if you can fix it. I like your work :D

Thanks for multirom :D
[ONE Android Development] KINGbabasula:
Important

Ok, the problem is this one and I'll add it to the FAQ as soon as possible:

once you have installed secondary ROMs, MultiROM MUST run on every boot, it means that if you forget to inject current boot sector, well, your SELinux on secondary ROMs will be screwed up and won't let ROMs boot. In TWRP there is the option that automatically injects the boot sector, I suggest enabling it so every time you flash something it will get injected
[ONE Android Development] AYEHAN:
With multirom is it possible that sms, contacts and call logs sync between the installed Roms

Sent from OnePlus One @ CyanHacker v3
[ONE Android Development] tobitege:
No, the roms have their own data area, but you can use e.g. Titanium Backup (whose backup folder is common to all) to backup apps+data in your "main" rom and just restore that in the other rom(s).
[ONE Android Development] KINGbabasula:
Here we go:

MultiROM v32c

* Vsync improved, no more tearing and the boot menu is much smoother, it looses less frames

* trampoline updated to v21

* Some small fixes

Recovery 9/3/2015

* Added UI for Pattern encryption unlock

* Added restorecon action for secondary ROMs (if a secondary ROM doesn't boot anymore, select it, it will fix SELinux contexts that may be set wrong by a boot without MultiROM running, for example if you forgot to inject the boot sector, for more info, check the FAQ)

Always thanks to Tasssadar because a lot of work is done by him, he is awesome
[ONE Android Development] magic.hand:
I tried to update to v32c but failed to install TWRP.
[ONE Android Development] juancarlos5:
what is the persist option in backup?
[ONE Android Development] toqpuk:
Trying to update today Multirom and recovery over APP, it is showing me "Failed to mount /cache!"

Multirom zip has installed over recovery manually, img file tried to install Flashify, but still app showing that recovery need to update. Please, how to fix "Failed to mount /cache!" ?
[ONE Android Development] isoladisegnata:
I always have the problems with CM11S (Calkulin's) secondary ROM. . Black screen during calls..:confused:
[ONE Android Development] juancarlos5:
i dont have problem in my test with this tuto - http://xdaforums.com/showpost.php?p=58776196&postcount=2

i run CM11 primary and Crash Rom in secundary, but try with CM12 proximity sensor fix
[ONE Android Development] isoladisegnata:
Tnx...a lot..then if I have CM12 Nightly on primary ROM and Calkulins ROM (CM11S-5Q) in secondary...... I flash (CM12 proximity sensor fix) from Install menu in TWRP Recovery and not from Multirom ..Yes?:o
[ONE Android Development] Natakranta:
I updated last night using MultiROM Manager app. All good, no problems encountered.

I just had to update Materialised theme from 2850 to 2860 testing because old theme was causing some misalignment of text in new recovery.

I changed the recovery curtain with the theme flashify script successfully on first attempt.

I'm happy to report USB OTG works back for me. I successfully mounted 64GB microSD through Meenova card adapter.

Very good update, great work, lots of thanks!

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] MMWolverine:
Yes [emoji3]
[ONE Android Development] juancarlos5:
Yes, flash in TWRP ( primary rom)
[ONE Android Development] isoladisegnata:
Tnx 1000 to WWolverine and Juancarlos5.. 5Q work 100%

---------- Post added at 01:39 PM ---------- Previous post was at 12:52 PM ----------

false alarm...:confused:

now black screen calls work on cm11s in secondary ROM and...don't work CM12 nigtly primary ROM..Why?
[ONE Android Development] MMWolverine:
Ok, I see what you mean. Maybe there's something new to CM12 nightlies regarding proximity sensor, let me check and report back
[ONE Android Development] isoladisegnata:
no..ok...I flash modem in primary TWRP..yes ?
[ONE Android Development] MMWolverine:
Yes, on primary and then reflash proximity sensor fix on primary where you have CM12. I just tested latest 20150310 nighty and screen turns of during calls, so it still works fine. False alarm. :D
[ONE Android Development] isoladisegnata:
Ok..

I have flashed CM12 Nightly (20150310) davilk / cache..

then I have flashed XNPH05Q_Extras davilk / cache..

and then flashed proximity sensor fix..

but it'is go in bootlop...grrr...:)

What's the problem..:eek:

---------- Post added at 02:23 PM ---------- Previous post was at 02:18 PM ----------

ok tnx..MMW:good:
[ONE Android Development] MMWolverine:
The problem is that you're flashing XNPH05Q_Extras and that's why CM12 is bootlooping. Just follow my tutorial on my forum and download the links I posted - files are named like this:

CM12_09.02.15_modem_firmware.zip (1st flash)

CM11s_XNPH05Q_modem.zip (2nd flash)
[ONE Android Development] isoladisegnata:
ok ...I flash this in TWRP Recovery normal and then proximity sensor fix...?
[ONE Android Development] MMWolverine:
Yes. :D
[ONE Android Development] :
It's possible install cm12 as secondary if i use the PA 4.6 Beta6?
[ONE Android Development] isoladisegnata:
now work perfectly..tnx:good::laugh:
[ONE Android Development] juancarlos5:
YES,

i run cm12 crash rom in secondary with the tuto of MMWolverine.

My primary rom is cm11s
[ONE Android Development] giveme13s:
A noob question...apologize if it has been answered before.

I always update multirom and twrp using multirom manager app on primary rom.

Is it ok to do so on secondary rom?
[ONE Android Development] AYEHAN:
i am using CyanHacker v3 Android 5.0.2, what kernel should i install when installing from MultiRom Manager?

CM12 or CM11/CM11S/AOSP
[ONE Android Development] isoladisegnata:
use ak kernel..
[ONE Android Development] AYEHAN:
its not giving an option for AK

Just CM12 or CM11/CM11S/AOSP
[ONE Android Development] AYEHAN:
Screenshot attached now tell me whicone i should use with having android 5.0.2Rom

Sent from OnePlus One @ CyanHacker v3
[ONE Android Development] AYEHAN:
[MENTION=4245169]isoladisegnata[/MENTION] thanks to you Sire

installed Ak in recovery flashed Multirom and then Patched Recovery all set and booted up

just the nandroid isnt booting zip flashed roms working fine
[ONE Android Development] isoladisegnata:
:good:
[ONE Android Development] ricardowec:
Where does USB OTG work... in your ROM or in Recovery?

I am on latest BlissPop and Boefla Kernel as primary and enven though I can access the USB I can see no files on it.

thanks
[ONE Android Development] Natakranta:
Both. One have nothing to do with the other.

If you mean when in ROM, that's ROM/karnel problem.

If you mean when in MultiROM TWRP, maybe it's for system on your external storage. My microSD card is exFAT formatted. It mounts in TWRP and I see what's on it.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] KINGbabasula:
MultiROM v32d:

Updated encryption support

A few small updates
[ONE Android Development] mapolidori:
On the most recent update of multirom, everything seemed to go well, even the flashing in twrp, but every time I boot back up and look at my current version, it says v31v, update v32d available. I can't get it to show the correct version. Has anyone had this issue? And will it cause any issues?

I am running the most recent euphoria with ak kernel.
[ONE Android Development] morissio:
Even to me

bye
[ONE Android Development] isoladisegnata:
Vai King..good..;)
[ONE Android Development] FullWipe:
I have a problem with the latest version 32d ..... I can not install it either from the app MultiROM Manager, either via recovery downloading it from here.

I tried to install it at least 5 times but on reboot marks me this ......

The strange thing is that before I had the 32c and now reports 31v which also does not exist ...... what happens? :eek:

EDIT: I forgot ..... I've aboard SlimSaber LP (last version) + AK v.128
[ONE Android Development] mapolidori:
I have the same issue. I'm on ak v128 and Eurphoria LP.
[ONE Android Development] KINGbabasula:
The update is installed, just it shows the wrong version number, I'll update it in a few minutes and reinstalling should show the correct version
[ONE Android Development] Natakranta:
That's what I thought. Thanks!

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] KINGbabasula:
Now the version number is correct
[ONE Android Development] Natakranta:
Flashed and confirmed. Thanks!

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] FullWipe:
+1

Now is perfect :good:

Thanks for quick fix! :)
[ONE Android Development] mapolidori:
Thanks for the great work!
[ONE Android Development] jesterpaul:
? I just flashed the version in the second post and still get it reporting that it's version 31v

Where is the link for the fixed version

Sent from my Blissed out OPO
[ONE Android Development] Natakranta:
Use MultiROM Manager app from Play Store to update to latest version.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] jesterpaul:
Doing just exactly that. Even uninstalled then reinstalled the application from Play Store. When I launch MultiROM manager it shows that 32d is available, but when it downloads. It shows that it's downloading version 31v all over again.

EDIT: I'm an idiot. Wasn't wearing my glasses and misread it (really!).

Works perfectly. Thanks to the dev for tireless work on this [emoji106][emoji106]

My bad.

Sent from my Blissed out OPO
[ONE Android Development] Natakranta:
LOL

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] DZYR:
Wifi breaks on primary ROM

Hi Guys,

I am rather new to using MultiROM and I seem to be having some issues and I hope it can be resolved with some help from the community here. My main ROM is Darkobas 3.5.8-20150309 with Kernel 3.4.67-cyanogenmod-g5e162d6.

Having installed MultiROM Manager from the PlayStore, I proceeded to install MultiROM v32d and update my recovery 2015-03-09. Then I proceeded to recovery to install a secondary ROM i.e. Validus ROM jupiler-V7.0-20150301. The secondary ROM boots up and works fine. However, when I boot back into my primary ROM, my wifi is broken. To fix this, I reboot into recovery and dirty flash my primary ROM. On rebooting wifi is back, but the issue is I lose the ability to multi-boot (don't get the screen to select ROM to boot). The MultiROM app also shows Kernel: doesn't have kexec-hardboot patch!.

I figured I needed to flash the CM12.zip (that was downloaded when I installed MultiROM). I did this and now I can multi-boot but this again breaks the wifi on my primary ROM.

Not sure how to fix this issue. I do hope someone can point my in the right direction.

Cheers!
[ONE Android Development] KINGbabasula:
Probably the kernel the app downloads is too old and incompatible with latest builds, I'll update it soon, just flash any kernel with kexec hardboot
[ONE Android Development] ravvio:
I see a Big One Plus One Logo along with powered by Android instead of the normal one at the start of my phone. Why ? Please help.
[ONE Android Development] prstorero:
For the life of me I can't get it working right haha. I've used multirom on both my nexus 5 and 7 before so I'm not new to installing it, but the multirom menu doesn't show in advanced. I've done some searching around and looked over the last however many pages but I can't find anything on it. It shows up when booting so I know it's installed. I tried a couple different versions of recovery and got the same results. I also tried doing an install through the app and also manually.

EDIT: turns out the twrp theme I was using removed it. I've never used a theme before for recovery so I had no idea it could have that effect.
[ONE Android Development] Natakranta:
Theme didn't remove MultiROM menu, it just didn't show it as it's designed for normal TWRP which doesn't have it.

You need to use MultiROM TWRP theme. Chose one from here with MultiROM in name. They work perfect for me. Copy the zip to TWRP/theme and rename to ui.zip

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] prstorero:
Thanks, I appreciate it :)
[ONE Android Development] pippoaacc:
Hi. Every time I update my primary CM12 Temasek with AK kernel new releases, my secondary cm11s stops to boot. Trampoline shows up but when selecting cn11s it is stuck on opo logo for a while then reboots into recovery. Usually reflashing multirom helps but this time it didn't, nor did running resyorecon and inject current boot image command. Any suggestions?
[ONE Android Development] laulau42400:
what firmware do you have? with cm12 you must have the

https://www.androidfilehost.com/?fid=95916177934526343
[ONE Android Development] pippoaacc:
I have that firmware. What doesn't boot is CM11S. Already booted into that a few days ago. Now no way
[ONE Android Development] laulau42400:
Why not stay on CM12?

Tapaltak and Lollipop ? One+
[ONE Android Development] pippoaacc:
Because some games I have to finish (eg Assassin Creed pirates) are not compatible under subsequent roms than 22r
[ONE Android Development] i04055:
i found the answer...
[ONE Android Development] KINGbabasula:
MultiROM v32e:

* Disabled back Vsyinc, now the UI is smoother

* Minor UI improvements like buttons shadows

Recovery update:

* Important security update: the new updater-script parser doesn't let secondary ROMs flash bootloaders or radios
[ONE Android Development] xanthrax:
Oops in multirom when attempting to flash the gapps, the rom flash went fine

Latest multirom update
[ONE Android Development] stab244:
I had something similar happen to me but I had a theme on so I thought it was the theme. Guess not.

Sent from my bacon
[ONE Android Development] chikimonke:
As others have said, I had an issue with trying to use TWRD Materialized theme and the sliders for confirming a flash don't work/aren't there. I looks like others have noticed it in non-themed recoveries as well. Seems the slider got shifted in some instances?
[ONE Android Development] xanthrax:
no themes applied, I've flashed the previous 9/3 multirom via flash img from recovery in order to continue my installation

most probably the button shadows borked it, the King will fix it, just revert to the previous multirom

sent from my Darkside of SHIELD Tablet
[ONE Android Development] KINGbabasula:
For people having problems with sliders: TWRP now has reduced themes number and switched to a new scaling algorithm to fit themes in different screens, themes now must be updated to be compatible. I haven't got any problem with sliders without themes
[ONE Android Development] xanthrax:
I'm not using any theme, I was only trying to flash the gapps on a freshly second flashed ROM and the screenshot shows how the slider looks
[ONE Android Development] KINGbabasula:
Does it happen always or just sometimes? If you rebbot does it go away?
[ONE Android Development] xanthrax:
Nope, I have rebooted twice the recovery and even Booted into the rom and back to recovery

I've tried to toggle the rotation of the recovery as well, no change

If power button is pressed, the unlock slider looks OK but not swipe to flash
[ONE Android Development] KINGbabasula:
I checked all the sliders, the only one that looks wrong is Advanced > MultiROM > List ROMs > rom > Flash zip, I'll fix it as soon as I can
[ONE Android Development] xanthrax:
Great, that's essential for us to use second roms [emoji4]
[ONE Android Development] KINGbabasula:
The latest build of TWRP has now fixed sliders
[ONE Android Development] transvin:
after installing multirom & flashin all other files, when my phone rebooted, the wifi & mobile data didn't turn on. I rebooted the phone again but the problem remains. Should I have installed kernel 5.0 at the first time? I'm using CM12 nightly bacon firmware latest on my phone.
[ONE Android Development] laulau42400:
Can not install a few things. Wide problem with the theme.

http://chinandroidphone.com/themes-twrp-twrp-multirom

Tapaltak and Lollipop ? One+
[ONE Android Development] xanthrax:
"all other files" you flashed is the problem not the multirom, check them
[ONE Android Development] transvin:
those files were automatically downloaded by multirom (that's what I meant by 'all other files')

the files were MultiROM v32e, Recovery 2015-03-17, Kernel: 4.4.x or 5.0.x

I tried flashing both kernels, but I faced different errors, and bootloops.

Maybe I should go back to official CM11, install multirom & all its files. Then flash a parallel CM12 nightly ROM.
[ONE Android Development] xanthrax:
nope , this didn`t happen here , I`ve just updated my second rom , cm 12 nightly and flashed the new gapps , reboot into it, all good

it`s something in your end

you maybe didn`t chose the correct kexec patched kernel according to the primary rom
[ONE Android Development] rahulrai:
I am on bliss pop 11th build. I downloaded the 13th build but when I tried to flash it, have error in updater script. Later when I tried to boot back thinking might be a corrupt file, it ended up in bootloop. I'm on multirom. All other ROMs boot up fine. I also tried flashing back to the 11th build which flashed earlier without any problem but this time all the blisspop ROMs are giving the same error. Error in updater script.

I'm on multirom 32E & AKs kernel v133. Before updating to latest multirom it was fine but now, can't understand what is going on.

I'm now on Calquilins stock ROM, but all my data is on Bliss Pop ROM as primary. Please help.

Any other info required?
[ONE Android Development] rahulrai:
This is the error I'm getting while I'm trying to install any build of bliss pop. Have also posted the same in BlissPop thread.
[ONE Android Development] rahulrai:
Thanks man for that piece of idea ?. Can't understand why did I have to flash the 9th Feb firmware update as I had flashed it earlier & was running smooth multirom. Back to normal now.
[ONE Android Development] DZYR:
Flashed Franco's kernel (Nightly 39) but that didn't work. Then flashed AK Skull and now it works. Thanks for your help. Appreciate it.

Sent from my One
[ONE Android Development] muzafa:
[MENTION=5093942]KINGbabasula[/MENTION] ubuntu is available https://forums.oneplus.net/threads/wip-ubuntu-touch-for-oneplus-one.266170/ support it please
[ONE Android Development] RenderBroken:
I checked the past few pages and searched as well but couldn't find this reported.

Reboot Into Recovery from MultiRom just went to black screen like it just shutdown. Not a huge issue since I could just turn it back on but thought I should report it none the less.

Thanks for all the hard work that has gone into this project!
[ONE Android Development] KINGbabasula:
I use reboot to recovery from boot menu many times to test things, can you reproduce it or it just happened once?
[ONE Android Development] Natakranta:
Last TWRP with Materialised theme updated specially for bacon MultiROM works fine. I was flashing today secondary ROM and primary ROM. All working. Thanks.

Only thing is the text describing flashing process is much smaller now, still legible but not comfortable, but that's probably for theme to fix.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] jsmonu:
Hi guys,

I've currently got Mahdi 4.4.4 build as primary, but when trying to flash Euphoria or Blisspop as secondary it throws an error. The same flashes fine as primary. Any clues what am I missing.

Multirom is updated..
[ONE Android Development] tobitege:
You probably need to update your bacon firmware to a newer version (see my signature in web view for link).
[ONE Android Development] jsmonu:
But if this is the firmware for CM12 (LP), won't it break my primary ROM (on KK 4.4.4)?
[ONE Android Development] ak0r:
Follow this thread:

I am using CM12 as primary and stock rom as secondary. No issues.

http://xdaforums.com/oneplus-one/general/guides-mmwolverines-opo-mods-tips-tricks-t3027926
[ONE Android Development] dansou901:
[MENTION=5093942]KINGbabasula[/MENTION], can you do a new build of MultiROM and recovery? Tassadar fixed support for Sailfish OS, a first build of Sailfish is now available in General section. We need a new version of MultiROM and recovery for testing. Thanks!
[ONE Android Development] KINGbabasula:
Yes, sure, I was going to build it, just came home from school :cyclops: