[Bacon] OnePlus One Info thread w/ Extras

[MMWolverine]

Greetings!

This is a general how-to thread (similar to my S3 mods, tips & tricks) and will offer help, guides, mods and even software.

I will do my best to answer any questions regarding OnePlus One, or Android in general. Feel free to contact me with your feedback (questions/praises/critics), either here or through pm.

 

[MMWolverine]

GUIDES

[HOW-TO] Boot KitKat, LolliPop and MarshMallow roms in MultiROM

For discussion on MultiROM, how to install and use it, please visit the original thread here.

As you already know, since their arrival Lollipop roms require you to flash the a new version of firmware. This is regulary updated with CM nightly releases and without it you get bootloops. However, if you use CM11 roms and flash the new firmware, your proximity sensor gets broken, resulting in a Screen of Death during calls. Other issues may appear as well. This can be fixed by flashing latest CM11 modem (contains only NON-HLOS.bin).

When you have your MultiROM up and running, you will need three things: updated CM12.x/CM13 firmware, CM11 modem and the proximity sensor fix. All files will be attached to this post and regulary updated. So download and transfer them to your device.

Make sure you are using TWRP MultiROM Recovery v2.8.6.0, otherwise modem/firmware will not install! Flash on primary ROM and reboot Recovery.

• CM12.x/CM13 firmware (05-15-2015) - - - AndroidFileHost /// Dev-Host
• CM11 modem (radio) only - - - AndroidFileHost /// Dev-Host
• Proximity sensor fix for CM12.x/CM13 Roms* - - - AndroidFileHost /// Dev-Host

Now, depending on which rom you are running as primary and which one(s) as secondary/-ies, do the following in one recovery session:

1. flash CM12.1/CM13 firmware from Install menu in TWRP Recovery
2. flash CM11s modem from Install menu in TWRP Recovery
3a. if you are running CM12.x/CM13 rom as primary, flash proximity sensor fix from Install menu in TWRP Recovery
3b. if you are running CM12.x/CM13 rom(s) as secondary/-ies, flash proximity sensor fix from MultiROM menu in TWRP Recovery
4. reboot

NOTICE 1: After flashing CM11 modem, baseband version in CM13 roms will be unknown, but calls and connectivity should work without problems.

NOTICE 2: To revert my proximity sensor fix (restore original sensors.msm8974.so), flash this on primary or secondary CM12.x/CM13 (depends on where you have it) - - - AndroidFileHost /// Dev-Host



If you cannot install modem as zip in recovery, feel free to use my cmd program attached below.
Extract this zip to your PC, then extract NON-HLOS.bin from CM11s modem zip and put it in the ModemFastbootFlash folder. Finally run INSTALL.bat and follow instructions.

Seperate commands are:

adb reboot bootloader
fastboot flash modem NON-HLOS.bin
fastboot reboot

*flashable zip contains old blob sensors.msm8974.so, from SlimSaber LP Jan.08.

Credits
@KINGbabasula and @Tasssadar for MultiROM Mod/Recovery and Manager
@Natakranta for pointing out the proximity sensor fix

 

[MMWolverine]

SOFTWARE

Cyanogen OS 12.1.1 (YOG7DAS2K1) Stock Kernel

If you flashed the wrong custom kernel (phone won't boot) or simply want to revert back to stock, flash this in Recovery.

Download
md5: 12f390ae56395aa4e611a5de736023bc

Fastboot-flashable Cyanogen OS 12.1.1 ROM (YOG7DAS2K1)

Extract the zip to your desktop and follow INSTRUCTIONS.txt and INSTALL.bat program.

Download
md5: 5acdcbc9792c3e7ea4dbf9d37430d73d

Recovery-flashable Cyanogen OS 12.1.1 ROM (YOG7DAS2K1) Rooted!

ROM is completely stock with added SuperSU root.

Download
md5: 247d06e4853866dbee7b75058c0e6ff4


=== Older versions ===

Cyanogen OS 12.1 (YOG4PAS3JL) Stock Kernel md5: 7b20c4b5759410117f2ee7ad8d289794
Fastboot-flashable Cyanogen OS 12.1 ROM (YOG4PAS3JL) md5: bc40efee3a12f0da6bd2866fb3127e76
Recovery-flashable Cyanogen OS 12.1 ROM (YOG4PAS3JL) Rooted! md5: 2c80f700e700ee557865c7acd6476fd4

Cyanogen OS 12.1 (YOG4PAS2QL) Stock Kernel md5: 7753b852a06d3bbd46359647513f753d
Fastboot-flashable Cyanogen OS 12.1 ROM (YOG4PAS2QL) md5: cb3f528099a6bd46c7450ff44c8939a4
Recovery-flashable Cyanogen OS 12.1 ROM (YOG4PAS2QL) Rooted! md5: 813121c52ce12e76fc5bdc6bdd0c1103

Cyanogen OS 12.1 Stock Kernel (YOG4PAS1N0) md5: 0c137df35edc41ea35d3111bd62a6210
Fastboot-flashable Cyanogen OS 12.1 ROM (YOG4PAS1N0) md5: 8037e519874afe9fd9db320c30d0b6d1
Recovery-flashable Cyanogen OS 12.1 ROM (YOG4PAS1N0) Rooted! md5: 1a7a971d643920f7106f14e9591b69ee

Cyanogen OS 12 Stock Kernel (YNG1TAS2I3) md5: 27a93d38906eac3efadf8568a0ba195d
Fastboot-flashable Cyanogen OS 12 ROM (YNG1TAS2I3) md5: 5c10792f845d7d42e69b900ffedfa1e2
Recovery-flashable Cyanogen OS 12 ROM (YNG1TAS2I3) Rooted! md5: f11392490e0d4e56d0a850147adbb8df

 

[MMWolverine]

MODS

Bypass Xposed for Lollipop bootloop

DEPRICATED: Please use official Xposed uninstaller http://forum.xda-developers.com/showthread.php?t=3034811

Incompatible Xposed modules and SELinux set to Enforcing will make your phone bootloop. I couldn't find a flashable zip, so I made one myself. It disables Xposed Installer and system boots normally. Once you've found the problematic module, simply wipe data for Xposed Installer and boot again.

Source guide

 

[emam damon]

As you already know, since their arrival Lollipop roms require you to flash the a new version of firmware. This is regulary updated with CM12 nightly releases and without it you get bootloops. However, if you use CM11(s) roms and flash the new firmware, your proximity sensor gets broken, resulting in a Screen of Death during calls. Other issues may appear as well. This can be fixed by flashing CM11s modem (contains only NON-HLOS.bin).

When you have your MultiROM up and running, you will need three things: updated CM12 firmware, CM11s modem and the CM12 proximity sensor fix. All files will be attached to this post and regulary updated. So download and transfer them to your device.

• CM12 firmware
• CM11s modem
• CM12 proximity sensor fix*

Now depending on which rom you are running as primary and which one(s) as secondary/-ies, do the following in one recovery session:

1. flash CM12 firmware from Install menu in TWRP Recovery
2. flash CM11s modem from Install menu in TWRP Recovery
3a. if you are running CM12 rom as primary, flash CM12 proximity sensor fix from Install menu in TWRP Recovery
3b. if you are running CM12 rom(s) as secondary/-ies, flash CM12 proximity sensor fix from MultiROM menu in TWRP Recovery
4. reboot

*flashable zip contains old blob sensors.msm8974.so, from SlimSaber LP Jan.08.

thank you sir.i was looking for this.

 

[xanthrax]

Good work wolverine, how about cm11 as primary, latest 05Q and cm12 second, cm 11 has proximity issues, cm12 works fine
I have the latest cm12 firmware flashed otherwise it will always reboot cm12

Sent from my Darkside of 1+1

 

[MMWolverine]

Good work wolverine, how about cm11 as primary, latest 05Q and cm12 second, cm 11 has proximity issues, cm12 works fine
I have the latest cm12 firmware flashed otherwise it will always reboot cm12

Sent from my Darkside of 1+1

Just 05Q modem on primary and the proximity fix on your cm12 secondary.

 

[antares-gr]

Thank you very much. Solved my proximity sensor problem. Running cm11s as primary with cm12 blisspop as secondary.

 

[Mandrake2010]

hi, but in cm12 firmware static_nvbk.bin is 0 byte so if flash this zip overwitre partition static_nvbk with 0???
static is about 10MB
no problem to flash this partition on primary rom?

 

[MMWolverine]

Thanks for noticing, but since there were no reports so far, I think it wouldn't cause major problems. static_nvbk.bin wasn't even part of firmware since 44S.

Correction, I've checked tobitege's and darkobas's firmaware zips, static_nvbk.bin is 0b in both. Latest cm12 nighlty the same. So all ok.

 

[taff2408]

Thanks Wolverine it works like a dream. Many thanks for putting this thread together.

 

[n.praveen13]

I have wiped the device clean using mutirom custom twrp recovery and installed CM12 Rom.

I'm using mutirom v30 with CM12 as primary and cm11s as secondary.

I have never installed the firmware update.
I do not get boot loops with cm12 nor cm11s, do I have to still install the firmware?

I face the issue with proximity issue while answering calls on cm12
I should flash firmware update on CM12 ROM and then install proximity fix that's all right?

I don't know if I should flash the cm11 modem fix on cm12 rom or cm11 rom.

Excuse me for being a noob :silly: , have been using android only from the past 90 days or so

 

[MMWolverine]

Well you can try only proximity sensor fix on cm12. But to avoid possible issues, I would advise you to flash cm12 firmware, cm11s modem and the proximity sensor fix, all three on primary partition t.i. cm12 rom.

Should you flash only the firmware update, the prox. sensor on cm11s wouldn't work. And the fix is for lollipop roms running with the older modem.

 

[n.praveen13]

I have installed proximity fix only, didn't work.

Installed cm12 firmware update and proximity fix, didn't work.

In fact those made it worse. I had screen locked only for incoming calls and unlocking would still allow me to answer. Now I have blacked out screen for incoming and outgoing calls too. Even the unlock button would unlock the screen. Will try installing all three else I'm restoring.

Edit: The steps you provided had worked

Thanks.

 

[Sonic132]

Looking for the 11S firmware

Hey. Looking to try out CM12 roms. But the first one I tried out (crDroid) failed to flash in recovery (TWRP).
So I want a stock firmware I can flash in case flashing something breaks something.
The link you posted. Is that the one I'd want?
Lastly, your post is awesome. I'd like to multi boot. But it's a little over my head. Any chance of making a simpler to read version?

 

[MMWolverine]

Hey,

the link you're looking for is at the end of 2nd post "To revert back CM11s firmware, flash from Install menu in TWRP Recovery."
File is named as "CM11s_XNPH05Q_modem_firmware.zip", from the latest stock OTA update.

Before flashing any LolliPop rom you need to install CM12 firmware. As per your request I'll simplify the MultiROM guide.

1. use MultiROM Manager app to install MultiROM v32, Recovery 2015-03-05 (0) and Kernel
Note: the CM12 AK Kernel from this app is outdated (v.010), it will boot, but please visit http://ak.hiddenbytes.org/ to upgrade

2. now boot into MR TWRP recovery and in the Advanced section under MultiROM add, manage or remove secondary roms
For example: to install gapps on a secondary rom, press "List ROMs", select it and press Flash ZIP.

3. if you plan on multi-booting CM11 and CM12 roms, you have to flash CM11s modem (2nd link in 2nd post) + the proximity sensor fix (see points 3a-3b)

I hope the rest is self-explanatory, should you have any further Q, feel free to ask.

 

[rajesh261092]

Hi @MMWolverine ! Great Guide !
I am dual booting CM11S and CM12 (primary) using the following step
I had a rooted stock CM11S with latest AK Kernel installed
I just added the CM12 as a secondary ROM and once it finished installing, I swapped it with CM11S
The only problem I face on the CM11S now is that once I turn off the screen, it simply refuses to turn back on
Note: CM12 works without any problems
Any help is appreciated. Thanks in advance.

EDIT: I was able to fix the problem in CM11S by unchecking the "check proximity sensor for accidental screen unlock" option under Display & Lights

 

[dio62000]

Ok, so let me double check this:

I have CM12 (Blisspop) as primary ROM. Works without problems.
I have CM11 (stock rooted) as secondary ROM. I have the proximity problems during calls, but by unchecking the 'accidental wakeup' option at least I can turn the screen on.

Shoud I now:

Flash CM12 proximity sensor fix and CM11 modem only (so only follow steps 2 and 3a) or should I flash CM12 modem firmware too?

1. flash CM12 firmware from Install menu in TWRP Recovery
2. flash CM11s modem from Install menu in TWRP Recovery
3a. if you are running CM12 rom as primary, flash CM12 proximity sensor fix from Install menu in TWRP Recovery
3b. if you are running CM12 rom(s) as secondary/-ies, flash CM12 proximity sensor fix from MultiROM menu in TWRP Recovery
4. reboot

 

[MMWolverine]

Hi @MMWolverine ! Great Guide !
I am dual booting CM11S and CM12 (primary) using the following step
I had a rooted stock CM11S with latest AK Kernel installed
I just added the CM12 as a secondary ROM and once it finished installing, I swapped it with CM11S
The only problem I face on the CM11S now is that once I turn off the screen, it simply refuses to turn back on
Note: CM12 works without any problems
Any help is appreciated. Thanks in advance.

EDIT: I was able to fix the problem in CM11S by unchecking the "check proximity sensor for accidental screen unlock" option under Display & Lights

Flash CM11S modem as primary (in twrp from "Install") and CM12 proximity sensor fix on CM12 rom as secondary (from MultiRom menu). I'm not a big fan of swapping roms, had some issues in the past. But the feature is there so you can use it of course.

 

[MMWolverine]

Ok, so let me double check this:

I have CM12 (Blisspop) as primary ROM. Works without problems.
I have CM11 (stock rooted) as secondary ROM. I have the proximity problems during calls, but by unchecking the 'accidental wakeup' option at least I can turn the screen on.

Shoud I now:

Flash CM12 proximity sensor fix and CM11 modem only (so only follow steps 2 and 3a) or should I flash CM12 modem firmware too?

You most likely already flashed CM12 firmware, otherwise you would already have problems on BlissPop. So only CM11s modem and proximity sensor fix.