yashsingh1/xdaforums huggingface dataset:
[ONE General] myweca:
Hello there!

I have read many pages in this thread!

Some questions - just to be 100% sure - I already read gerciolisz's answer, two posts before!

I am using Euphoria as my Primary Rom and Euphoria CAF as my Secondary Rom.

I want to try MIUI as well, but not as a Primary Rom.

Can anyone post me a link of the best MIUI Rom for a daily driver? I mean the one that people in this thread are using!

I have found at least 3 roms for OnePlus One here on XDA.

And finally, how did you make it work? You just followed the Original Post? Or something different?

Thanks in advance!
[ONE General] mp187263:
Thanks a million for the proximity fix...the only one that made it work perfectly. Running RR 5.5.6.
[ONE General] AYEHAN:
a quick question before i apply this method

i am on 5.1.1 as Primary and want MIUI7 kitkat as secondary, MIUI is working fine but gets random reboots and off-course the proximity issue, will using the method solve both proximity and random reboots?
[ONE General] MMWolverine:
This method won't fix random reboots. You should first determine whether you have soft or hard reboots. The former are usually caused by apps & settings, the latter by kernel and its config. Best you contact MIUI development support and ask there.

Regarding the proximity issue, you can go ahead with my guide. So you need kitkat cm11s modem and proximity sensor fix both flashed on primary 5.1.1.

Note to all:

Sorry I'm lately not very active in this thread or Android forums in general (due to personal reasons). I'll try to answer questions when/if I can.
[ONE General] AYEHAN:
i have 5.1.1 as primary and all other secondary as 5.1.1 too except MIUI( going to install XNPH22R now )

what i did is install modem on primary and fix on secondary rom ... is that ok? tough it didnt solve the issue of proximity in MIUI but all other ROM was working fine.

Edit : installed CM11S 05Q works fine but on calls screen goes black, installed 05Q modem and Proximity fix on primary 12.x ROM still same issue ... did i made any mistake?
[ONE General] AYEHAN:
and i guess this is my issue on MIUI(Random Reboots, hard Reboots i guess), and broken proximity on CM11S

any solution for Baseband 00241? with 12.x Primary and 4.4.4 as Secondary
[ONE General] MMWolverine:
No, when you flash CM11S 05Q modem your baseband version should be this: MPSS.DI.2.0.1.c7-00020-M8974AAAAANPZM-1

Only then will proximity sensor fix work on 5.1.1 roms and MIUI without the fix will also work. If you don't see this version string then cm11s modem was not installed and you still have OxygenOS baseband. Check that you're using TWRP up to v2.8.6.0 or follow my fastboot guide in op to flash the modem.
[ONE General] venky61:
Hi,

I am running Exodus 5.02 as primary rom and CM11 44s as Secondary rom. Flashed cm 11 44s radio zip in secondary rom. Primary worked well, but the secondary had screen going black during a call. Tried numerous solutions but in vain. Then checked your thread. Flashed cm12 sensor fix and cm 11 44s radio on primary. Even then the problem in secondary did not go, moreover, the primary stopped booting. Please help to make both roms work without issues.

Thanks in advance.
[ONE General] MMWolverine:
Again, if proximity sensor doesn't work even after flashing my fix can only mean that the CM11s modem was not installed. Here is an updated guide and I will also add this to the OP.

1. flash TWRP MultiROM Recovery v2.8.6.0 (normally as a flashable zip on primary): https://www.androidfilehost.com/?fid=24052804347826975

2. go into Reboot and Reboot Recovery

3. flash CM11S modem on primary

4. flash proximity sensor fix on primary Exodus 5.02

ROM shouldn't bootloop after flashing proximity sensor fix (at least it never did for me), but make sure you always

have nandroid backups

.
[ONE General] venky61:
Can I ask Y specifically I need to flash v2.8.6.0 multi rom recovery when I already have the latest multirom? In the remaining steps instead of 05Q modem, I flashed 44s modem. I shall try now with 05Q ones.

Edit: Sorry for asking about the multirom version, I read the OP again. My bad I missed it.

---------- Post added at 07:07 PM ---------- Previous post was at 06:45 PM ----------

It worked half.... My kitkat rom is working fine now... no proximity issues... Thank you. But still the primary exodus is not able to boot. Should I try dirty flashing the rom once?
[ONE General] MMWolverine:
Because TWRP versions 2.8.6.1 and 2.8.7.0 have a bug and don't install modem or firmware. Flashing process is displayed as successful, but current lollipop modem is never replaced. You can try 05Q modem, however, for proximity sensor fix it doesn't really matter whether it's 44s or 05Q. Both are KitKat modems.

If you dirty flash the rom, my proximity sensor fix will still stay installed (the old sensor blob that is). I made it in such a way that users don't need to always reflash the fix when updating roms. So first flash my revert zip: https://www.androidfilehost.com/?fid=23991606952599217 This will restore original sensor blob, then if the rom still won't boot dirty flash. And then try proximity sensor fix again.
[ONE General] Ejvyas:
Bug ? I read it was a feature not to touch the modem/firmware partition
[ONE General] MMWolverine:
Well the multirom TWRP version has a safety precaution to prevent flashing modems from secondary roms. I get that. But to call it a feature because of encryption commits or what not, is imo a bit excessive. How many people had issues with seperate flashing of firmware? But since twrp team is aware of this and aren't changing it, you're right, best not call it a bug. :)
[ONE General] ronaldrenteria:
Greetings Wolverine, I use a CM12.1 Nightly, you can give me a hand, telling the order in which I do Flashing files ..

Thank you.
[ONE General] MMWolverine:
Hi,

you didn't say where you want cm12.1 nightly, as primary or secondary rom. I will explain this for the combination cm12.1 nightly primary and cm11 secondary.

1. flash TWRP MultiROM Recovery v2.8.6.0

2. flash MultiROM v32k and a MR supported kernel (use MR Manager app)

3. flash CM11 rom as secondary

4. flash CM11s modem (radio) as primary

5. flash proximity sensor fix as primary

If you plan on using only Lollipop roms with MultiROM you don't need this guide.
[ONE General] anirudhvk:
Just wondering, the new HydrogenOS firmware does give me better signal but breaks the proximity sensor. Will this proximity sensor fix, fix it?
[ONE General] MMWolverine:
No, I just tested on COS12.1 and it makes it even worse (SOD during calls). So don't use this fix with HydrogenOS firmware.

Sent from the One, it's bacon!
[ONE General] cloudx720:
HydrogenOS modem is just a placebo effect no difference what so ever.
[ONE General] DjDiabolik:
I thinks i can thanks you for a flashable stock kernel of cos12.1.........................
[ONE General] MMWolverine:
Don't know how many people are using latest YOG4PAS2QL update, supposedly it has some bugs with notifications and wifi, causing users to revert. I don't have any issues and will post newest stock kernel and rom over the weekend.
[ONE General] DjDiabolik:
Lol... Yeah same... Ah the wifi problem it's also present in previous first release of cos 12.1.

In all other parts i don't have any problems whit this new update :)
[ONE General] guillermorojaz:
Regards [MENTION=4842497]MMWolverine[/MENTION]

I've flashed your ROM, Recovery-flashable Cyanogen OS 12.1 ROM (YOG4PAS2QL) Rooted!

Making clean installation, Wipe : Dalvik Cache - Cache - System And Data.

All it is going great.

I have a question, Adjusting, phone information, build number, I get dev-keys.

What does that mean :confused:

Grateful for your time and effort :good:
[ONE General] MMWolverine:
Lol, I haven't even noticed that. :D It means developer build. I am still searching for a signed zip and will upload once it's availble.

For now the only way to get LMY48B build without the dev-keys is to reflash COS12.1 Y0G4PAS1N0 (if you did any system or kernel changes) and then flash COS12.1 YOG4PAS2QL OTA zip. I've read many people had problems doing that, which is why I never use OTA updates.
[ONE General] miksi:
Only debuggable image is available.

For other links acces is denied.
[ONE General] MMWolverine:
Yep, that's the kernel with debug enabled. I actually got the unsigned ROM zip on reddit 10 days ago, added root and removed the otasigcheck crap from updater-script. That way it can be dirty flashed, but only in custom recovery.
[ONE General] therahmaniac:
Cifs support on ak caf kernel

Hi.. Has anyone been able to make cifs mounts on device running ak caf kernel? I used some commands found online to check cifs support on my device and they respond negative.
[ONE General] MMWolverine:
YOG4PAS2QL kernel and rom re-uploaded from signed sources.
[ONE General] Natakranta:
Thanks for keeping repository updated!

It's great to know there is place to go for latest download if needed.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE General] zul kap@n:
thanks MMWolverine

multirom 2015-04-16(v2.8.6.0) / v32i

1. flash CM12.1 firmware (15-05-2015) from Install menu in TWRP Recovery

2. flash CM11s modem from Install menu in TWRP Recovery

3. flash CM12 proximity sensor fix from Install menu in TWRP Recovery

internal: exodus 5.1.1 ( baseband version : mpps.di.2.0.1.C7-00020-m8974aaaaanpzm-1)

kernel; 3.4.108-AK308.OPO.CM12.1

2: AICP 6.0.1 11.0-NIGHTLY-20160124 ( baseband version : unknown) but without having proximity issues:D

3: euphoria 5.1.1 (20150803)

4: kitkat 4.4.4_OPO_XNPH05 BOEFFLA KERNEL 2.10 20150608 CM11

5: miui.xs 4.4.4

6. TEMASIk 5.1.1

all works fine without having proximity issues
[ONE General] MMWolverine:
Lol, I'm glad it still works for you. However, be aware this is outdated and I cannot take responsibility for any issues. Use at your own risk.
[ONE General] nachomagic:
Hi [MENTION=4842497]MMWolverine[/MENTION]

I used your great guide to have LL and KK multirom and I wohder if you will release a official guide to have MM and LP multirom :)

Thanks in advance
[ONE General] MMWolverine:
[MENTION=2660283]nachomagic[/MENTION]

MM and LP run in MultiROM without proximity sensor issues, so a special guide for that isn't neccessary. Firmware and modem (c6-00241) are the same, even if you'd flash fw from 01/30 cm13 nightly, there wouldn't be any problems.
[ONE General] MMWolverine:
Hi all,

I took some time and tested the proximity sensor fix in CM13 roms (when you have CM11 rom in MultiROM). As zul kap@n wrote a few posts earlier, after flashing KitKat modem, the baseband version in MarshMallow roms is unknown, but calls and connectivity still work. In CM12.x.x roms radio version is shown correctly.

I edited my guide in 2nd post and also renamed and re-uploaded proximity sensor fix/restore zip files. If any issues arise, please let me know.

P.S.

Also disregard my comment in post before, when I said that firmware from 01/30 shoudn't cause problems. Actually that was realeased in CM13 nightly from December 12, 2015, but reverted since than to old 05-15 fw. So please only use the older one.
[ONE General] zul kap@n:
thank you very much [MENTION=4842497]MMWolverine[/MENTION]
[ONE General] iliyasbaba:
can u provide a flashable zip of stock 44s rom...i tried installing one it shows error executing binary
[ONE General] MMWolverine:
Ah sorry I misread you asked for XNPH44S. I don't have that one anymore.
[ONE General] f41lbl0g:
Do you know if the fix works in caf 6.0.1 roms as well? I will try it out, just wondering if you tried.

EDIT: CAF roms work, don't even need proximity fix.
[ONE General] nachomagic:
Hi again mate

I've been reading the updated second post but in a little bit confused about the fw version.

At this moment I'm with slimsaber 5.1.1 and I would like to test a MM rom.

What is the best configuration? MM as primary and LP as secondary?

Could I have LP as primary?

What fw should I install to have LP and MM working?

Fit me the best should have LP as primary and not update the FW to avoid problems and just add the new MM rom as secondary but may be this is a dream :)

Thanks in advance
[ONE General] MMWolverine:
There shouldn't be any issues running LP as primary, I always have it that way (stock COS 5.1.1 primary and MM secondaries). Simply add MM in MultiROM and see if everything works (boots-up, no random reboots etc.). Slim doesn't flash fw, so if you flashed stock rom anytime since May/June last year, you should still have the latest firmware. If MM secondary gives problems, just flash 05-15-15 fw on primary and it will be ok.
[ONE General] nachomagic:
Thanks

I've already have 05-15-15 but the MM roms in the first step installation talks about a MM specified Fw 01-02-16

http://download.jgcaap.xyz/files/oneplusone/firmware/

On the other hand I should flash the proximity fix in bith, Lp and MM, should I?
[ONE General] MMWolverine:
Yeah OnePlusFirmware-01022016.zip is actually fw from 30th December 2015. It will work on MM, as will the older version from 15th May 2015.

You don't need my proximity sensor fix, that is only when you run KitKat roms in MultiROM.
[ONE General] JT1510365:
Thanks a ton for this awesome thread:)
[ONE General] buttasush:
I am running CM 11s. I have installed multirom manager through play store. I tried installing Sultan CM13 marshmallow rom but gives me error on booting incompatible ioctl. Please help.
[ONE General] MMWolverine:
[MENTION=6294963]buttasush[/MENTION]

Have you tried flashing Sultan CM13 as primary? Maybe outdated kexec-patched kernel is the problem...
[ONE General] buttasush:
Not yet. But is there any other workaround.
[ONE General] Hijmen:
Did you update to the cm13 firmware first?
[ONE General] nachomagic:
Hi mates

First of all thanks to [MENTION=4842497]MMWolverine[/MENTION] for helping us

I wonder how to detect s proximity sensor issues in order to flash the fix.

Does anybody know what is the proximity sensor issue?

Is there any test or way to detect the issue?

Thanks

Enviado desde mi A0001 mediante Tapatalk

---------- Post added at 07:49 AM ---------- Previous post was at 07:42 AM ----------

Hi again

So if I had LP as primary and MM as secondary I don't have to flash the proximity sensor fix in any rom?

This is only if you have a KK rom?

Enviado desde mi A0001 mediante Tapatalk
[ONE General] MMWolverine:
Proximity sensor not working properly is when during calls the screen goes black and it won't turn back on. So when you move your phone away from your ear, the screen stays black and you have to reboot. This happens when you use a newer modem (radio) in KK roms.

For example in Multirom you flash LP/MM primary (which also installs new firmware and modem), consequently you'd have a broken prox. sensor in KK secondary. So you have to flash old CM11 modem on primary, but that breaks breaks prox. sensor in LP/MM. The only difference is that here screen always stays on during calls. To bypass this, flash my proximity sensor fix on LP/MM.

To sum up, fix is only if you have KK rom(s) in MultiRom.
[ONE General] nachomagic:
Everything is working great with LP as primary and MM as secondary using the latest 01022016 firmware.

No proximity sensor issues

Thanks!!!!!
[ONE General] MMWolverine:
I also have c7-00011 fw now (recommended by RR dev), seems to be better than c6-00241 (05152015). I'll post here when I can.
[ONE General] nachomagic:
Great [MENTION=4842497]MMWolverine[/MENTION]

Will you release the CM13 version?

I really need it :)

I'm stuck in a bootloop in a secondary rom and I don't know how to get \data\data path for a secondary one using twrp file manager

Thanks
[ONE General] MMWolverine:
I don't plan on releasing COS13, at least not until an official img is available. Here's a flashable zip, which works fine ... http://xdaforums.com/showthread.php?t=3355423

Secondary rom is accessible at /data/media/0/multirom/roms, but if you have bootloop because of xposed, simply flash the uninstaller.
[ONE General] Flaxius92:
Hello, I'm having issues with the proximity sensor with my CM13 after flashing the 01-02-16 firmware despite the fix patch.

I only have one rom on my OPO - resurrection remix.

Would anyone have any suggestions for me?

Thanks
[ONE General] MMWolverine:
Hi,

I didn't recommend TWRP v2.8.7.0, because flashing modem/firmware with that won't work. Version 2.8.6.0 is correct, or any of newer ones 3.0.x.x. https://dl.twrp.me/bacon/

I have RR as secondary for some time now, and no problems at all. Even other firmwares caused no proximity sensor issues, appart from cm11 modem, which I haven't used for a long time.
[ONE General] Flaxius92:
I flashed TWRP 2.8.6.0 and managed to sort the issue, thanks a lot :)

However, if I wanted to try again and install the 01-02-16 firmware, given that it doesn't seem to work for me, do you reckon it's not doing a good job overwriting the previous modem or something?
[ONE General] MMWolverine:
Well I can only imagine that if you flashed my proximity sensor fix and dirty flashed RR, the fix is still there and unless you have cm11 modem, you don't need any fixes. It will only cause problems with newer modems. Flashing firmware will overwrite installed version, providing you're using the correct TWRP. So my advice is to flash my proximity sensor fix uninstaller https://www.androidfilehost.com/?fid=24415232478678284, that should restore original sensor blob. Or you can clean flash RR by formating /system. Then flash 01-02-16 firmware and see if it works for you.
[ONE General] Flaxius92:
With the right TWRP it worked like a charm! Thanks again so much!!! :laugh:
[ONE General] nachomagic:
Hi again [MENTION=4842497]MMWolverine[/MENTION] how are you?

At this moment I'm using DI.3.0.c6-00241-M8974AAAAANAZM-1 (commonly known as 241) firmware and I'm having issues with the GPS.

What firmware are you using at this moment?

Thanks in advance
[ONE General] MMWolverine:
I tried c7-00011 for a day or two and haven't seen any improvements compared to 241. I thought it would fix the "Compass needs calibrating" problem in Here maps, but didn't. Gps locks fine btw, in COS13.1 and latest RR.
[ONE General] nachomagic:
Thanks [MENTION=4842497]MMWolverine[/MENTION]

I'm not very familiar with the firmware files

Could you please give me a link to the firmware file?

Thanks in advance
[ONE General] MMWolverine:
Sure np, here are all the firmwares working with Marshmallow http://xdaforums.com/oneplus-one/general/firmware-modem-oneplus-one-lollipop-t3300907
[ONE General] nachomagic:
Thanks!!

So, you are using this file, aren't you?

bacon_firmware_update_2015_05-15_DI.3.0.c6-00241.zip
[ONE General] MMWolverine:
Yes, that's the same version that I have in my #2 post "CM12.x/CM13 firmware (05-15-2015)". I very rarely change modem.
[ONE General] sakoula:
question about kernels

Hi,

I have a very basic question. I have just installed multirom on my CM13.1.2-ZNH2KAS3P0-bacon using the multirom 6.0.x kernel (that has the keec-hardboot patch)

My goal is to install Kali Nethunter which according to their site it is based on CM 12.1. So I need to install the CM 12.1 as a secondary.

What I do not understand:

1. Assuming that I install CM 12.1 as a secondary, do CM13 and CM12 share the same kernel? Or CM12 will use a different one?

2. Are roms installed on a different partition? How can I check all the installed versions from the command line?

Thanks!
[ONE General] JT1510365:
I hope you can help me:)

I am running Sultans latest CM13 ROM as primary in multirom so how do i go about installing any kitkat rom as secondary so it boots up because i could never get the kitkat roms to boot only lp and mm roms booted

ThX for all your help in advance i am still trying to learn:)
[ONE General] MMWolverine:
As you might have noticed, I've been absent from this thread quite a while now, and in fact, from the entire Android scene. Real life eventually caught up with me. :rolleyes: I still follow a few things like A.R.I.S.E., Boeffla kernel etc., but without my frequent contribution with advice, like in the past.

Regarding MultiRom, the project is as good as dead to me. I asked the original developer some time back if he plans to release an official update for Nougats, he never did and a couple of guys made their own tweaks. But I've been having numerous problems with those, for example, constant mediascanner fc on RR secondary, not being able to access Developer options and so on. So I've finally tried EFIDroid and that's working fine, it's easy to install, maybe it'll even work with KitKat roms. Don't know for sure, coz I never use old builds, apart from latest COS.
[ONE General] Matt07211:
Your opinion on EFIDroid ? I don't quite get it, it states UEFI, what are the phone requirements?
[ONE General] MMWolverine:
Yeah, it's based on UEFI, phone requirements are root and unlocked bootloader. Here's a nice explanation http://www.androguider.com/2016/10/efidroid-takes-booting-to-completely.html

I like the simplicity of the EFIDroid app, though the icon could be a bit more innovative. :D There are some downsides compared to MultiROM, for example, you can't swap roms, the booting menu isn't touchscreen, no automated boot. Settings of secondary twrp didn't stick for me, also couldn't wipe cache/dalvik. Maybe that's working for some ppl, I'd have to ask on EFIDroid's thread.

The main reason I've tried this is to use TugaPower TWRP, which is the only one for OPO (afaik) where Aroma installer works. Wanted to try A.R.I.S.E. aroma installer. :D

Couldn't boot OOS 3.1.4, probably needs to be internal rom, which for me is still COS. I plan on changing that asap and if these EFIDroid's downsides will bother me too much, maybe I'll go back to MR.
[ONE General] Matt07211:
Hmmmm, thanks for the info. :)
[ONE General] davidnewton:
Thanks a lot for this excellent instruction. Following this instruction, now I can use Mahdi Rom as primary rom and Euphoria as second rom. They seem to work very well after several hours.
[ONE General] i04055:
Sorry I don't really understand the explaination.

In my case, I have lollipop as my primary ROM, and now i want to add PA 4.6 as my secondary ROM, what should i do?
[ONE General] MMWolverine:
Hello,

you cannot flash PA 4.6 in MultiROM because of this updater-script line, which checks the current and previously installed PA versions.

That's is most likely a safety precaution, so that users cannot flash 4.4.4 over 5.0.2, but it forces an error when doing a clean install as secondary rom. I disabled the line for you and attached META-INF folder to this post. Now please do:

1. replace META-INF folder in pa_bacon-4.6-BETA6-20141103.zip with the one from my zip (simply copy paste).

2. flash the changed pa_bacon-4.6-BETA6-20141103.zip

3. flash CM11S modem and proximity sensor fix both as primary (links in 2nd post)

4. you might also re-flash and re-inject AK kernel (or multirom 32d), because when I tested I had no MultiROM menu at boot-up.

Let me know if this works for you or post any additional questions.
[ONE General] i04055:
Thanks for the response, i'll try it tomorrow n will post the result...
[ONE General] i04055:
It's work for me, and don't have issue in point 4. My primary ROM boot normally, and so do the PA 4.6.

But i have another ROM which is PA 5, and it won't boot anymore, it keep boot to recovery every time I choose PA 5.

Should I reflash it?
[ONE General] MMWolverine:
Yes, please do that, it should fix it. Otherwise try repeating steps 1 & 2 from my 2nd post guide. Also don't forget to re-flash proximity sensor fix on PA 5 (just like the rom itself from multirom twrp menu).
[ONE General] nicesoni_ash:
Hi

I have a question related to multirom. If I am installing cm11 as primary and lollipop as secondary, what kernel should I flash to support multirom? Cm11 or cm12.

_____________

Sent from my "GT-I9300/1+1" powered by Carbon Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[ONE General] MMWolverine:
You can safely flash AK v.135, that's what I'm using. Or maybe boeffla-kernel-2.4-CM11, that one will also work. Just be sure you have CM12 firmware + CM11 modem, otherwise you will see a bootloop.