yashsingh1/xdaforums huggingface dataset:
[ONE General] 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
[ONE General] MMWolverine:
MODS

Bypass Xposed for Lollipop bootloop

DEPRICATED: Please use official Xposed uninstaller http://xdaforums.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
[ONE General] emam damon:
thank you sir.i was looking for this.
[ONE General] 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
[ONE General] MMWolverine:
Just 05Q modem on primary and the proximity fix on your cm12 secondary. ;)
[ONE General] antares-gr:
Thank you very much. Solved my proximity sensor problem. Running cm11s as primary with cm12 blisspop as secondary.
[ONE General] 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?
[ONE General] 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.
[ONE General] taff2408:
Thanks Wolverine it works like a dream. Many thanks for putting this thread together.
[ONE General] 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
[ONE General] 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.
[ONE General] 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.
[ONE General] 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?
[ONE General] 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.
[ONE General] rajesh261092:
Hi [MENTION=4842497]MMWolverine[/MENTION] ! 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
[ONE General] 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?
[ONE General] MMWolverine:
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.
[ONE General] MMWolverine:
You most likely already flashed CM12 firmware, otherwise you would already have problems on BlissPop. So only CM11s modem and proximity sensor fix.
[ONE General] Ofthecats:
[MENTION=4842497]MMWolverine[/MENTION]

My efs and persist partitions were corrupt.

Thankfully I had an efs backup on my PC from when I first unlocked my bacon. Restoring that, running a person command line command I found, and flashing latest cm12 nightly were my steps.

Up and running once again. Twrp just readded efs backup too lol ironic.

Thanks for the help.
[ONE General] @rvg:
Apologies, i am new to android and to this forum :)
[ONE General] lucariello83:
Hi, i had issues with proximity sensor and accelerometer.

I installed cm 12.1 06\06 nightly, cm 15_05 modem firmware and proximity fix (as described in first page).

I also tried to apply only the proximity fix, but the accelerometer doesn't work. Can you help me?

Thanks
[ONE General] @rvg:
[MENTION=4842497]MMWolverine[/MENTION] I am also facing the same problem. I am using COS12 as primary rom with franko kernel and latest firmware (from first post).

Tried by deleting the other roms, flash the fix zip from your first post, done the factory reset but still no luck.

Please help here.
[ONE General] MMWolverine:
Try my uninstaller zip from #2 post to remove the prox. sensor fix, check that there's no file "KeepSensorFix.sh" in /system/addon.d and that blob "sensors.msm8974.so" is installed in /system/vendor/lib/hw. Then you can reflash the rom for a clean system installation.

[MENTION=6747705]lucariello83[/MENTION]

Were you using my fix to compensate kitkat rom(s) in multirom or for any other errors? I'll test CM12.1 nightly asap.

[MENTION=1145819]RvG[/MENTION]

When you had Miui as secondary, did you install cm11s modem on primary? As zip or through fastboot?
[ONE General] @rvg:
[MENTION=4842497]MMWolverine[/MENTION] thanks, but my issue is resolved now, I factory format my COS12 in MRT and flash it again which resolved the issue. After that i restore my nandroid which made everything as previous.

And yes I had miui v6 as secondary rom after which this issues occured, i flashed the COS 12 firmware,cm11s modem and proximity sensor fix on all my lollipop roms (COS12,Exodus and Oxygen) throgh zip only but after that i found SOD during calls, so i tried to restore original sensors by flashing them, after which again I was getting broken proximity sensor including broken accelerometer (I've not checked the accelerometer before reverting the original sensors), but this time screen was continuously on during calls. However, it is fixed now...:D:D

Can you please identify what was the issue here and why i am not able to install miui 6 without broken proximity even after the flashing the fix and cm11s modems??? Eagerly waiting for your findings:):):)
[ONE General] lucariello83:
I haven't multirom. I simply installed the nightly and fixes ad discribed yesterday.

I don't know if i'm doing it right.

Inviato dal mio A0001 utilizzando Tapatalk

---------- Post added at 07:25 AM ---------- Previous post was at 07:06 AM ----------

Then how could i proceed to resolve my issue?! Thanks
[ONE General] @rvg:
I guess if u r not using kitkat based secondary rom or vice versa than there is no need apply those zips or fix. Jst factory format ur rom than flash ur cm12 rom over it wid updated firmware of cm12... If u r coming from kitkat based roms than its necessary to flash lollipop based firmware to install lollipop based roms... [MENTION=4842497]MMWolverine[/MENTION] ... Sir, please correct if the above steps are not correct
[ONE General] lucariello83:
Now i ve The cyanogen OS 12, i applied The prox fix and everithing works well. Then i think i need it.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE General] MMWolverine:
Hi guys, thanks for your reports!

[MENTION=1145819]RvG[/MENTION]

Your steps are ok; if you don't use KitKat roms alongside Lollipops in MultiROM than you don't need my proximity sensor fix. If you flash it by mistake, you can do a factory reset or use my uninstaller zip which restores original sensor file.

The problem with flashing cm11s modem as a zip is that it won't install in latest TWRP v2.8.6.1. Seems MR recovery is based on it and has the same problem. You'll have to flash the modem through fastboot, but I'll make a one-click batch file to make it simpler.

[MENTION=6747705]lucariello83[/MENTION]

You don't need my prox. sensor fix on COS12 unless you want to dual-boot KitKat roms.

Edit: I attached a small batch program to flash modem in fastboot, at least until twrp problem gets sorted out. 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.
[ONE General] NotesOfReality:
Proximity Issues on CM11S-05Q after downgrade

Hello [MENTION=4842497]MMWolverine[/MENTION] !! After I accidentally updated from CM11S-05Q as primary to COS12,then downgraded trough a clear TWRP backup,the proximity sensor is completely dead,I searched throug google on web the proximity sensor image for KitKat,please can you provide it to me or teach me how to extract it from a TWRP rom backup(It contains Data,System,Boot and EFS partitions),please it is so frustrating cause the proximity sensor tell me that there is always something above when however isn't true ,so when I call someone the screen and the touchscreen is always off.I hope it isn't a giant mistake and I hope I'm not asking too much from you,but please help me
[ONE General] MMWolverine:
Downgrading stock roms should always be done by fastboot flashing a factory image. When you upgraded to COS12 new firmware & lollipop modem were installed (breaking prox. sensor) and kept even after restoring twrp nandroid backup (which actually didn't save firmware partition).

So for starters you can flash CM11S-05Q firmware + modem: https://www.androidfilehost.com/?fid=95916177934527064
[ONE General] `SBR`:
to flash the a different radio for Miui 6 which file to be flashed? in the MultiRom add Radio option..

will that will solve Lollipop & kitkat rom without any proximity fix.

i have the Multirom 32g version with old 2.8.6 Recovery. currently running CM12.1 night as primary and Miui6 as secondary including Proximity fix with primary.

I need the latest modem for better reception. so would like to try the differed radio for Multirom.
[ONE General] MMWolverine:
CM11s radio or the one in Miui6, extract NON-HLOS.bin from zip, rename to .img and add to secondary. Though, I'm not sure it will work, never did for me with or without sensor fix. You'll have to uninstall proximity sensor fix on primary, then dirty flash the rom to get back latest CM12.1 radio.
[ONE General] `SBR`:
I did the procedure mentioned it's working without proximity fix and I can run latest modern as well.

Thanks
[ONE General] MMWolverine:
Great, thanks for reporting it works, will be useful to other users.

Poslano z mojega A0001 z uporabo Tapatalk
[ONE General] k_flynn:
[MENTION=4842497]MMWolverine[/MENTION] sorry if I'm asking the same old question, but I would like to double (maybe tiple :P) check to avoid any errors :)

I'm actually running cm12.1 nightly as a primary rom. I would like to test miui v6 (based on kitkat 4.4.4) as secondary.

Do I have to flash cm11 modem and cm12 sensor fix on my primary rom (cm12.1) or on my secondary (miui)? I never understood this :(

And eventually if I want to use cm12.1 as my daily rom do I have to flash something else or I can easily boot one of the two and everything will work?

Thanks in advance!
[ONE General] MMWolverine:
Better to ask many times and be sure. ;) You can flash cm11 modem and cm12 sensor fix on primary rom (cm12.1), although latest TWRP recovery has problems installing modem in a zip format. So you'll need to flash it via fastboot (see my guide here).

Or you can follow [MENTION=2477260]`SBR`[/MENTION]'s guide and use older Multirom 32g version with TWRP_multirom_bacon_20150416-00, extract NON-HLOS.bin from cm11 modem zip, rename it to radio.img (or any name), then "Add radio.img" to secondary Miui v6. That way you don't need cm11 modem + proximity sensor fix on primary.
[ONE General] k_flynn:
Thank You for the help! :) I would like to try 'SBR' guide so that I can have latest modem on primary cm12.1 and I understood that I need to flash radio.img on Miui v6 but, if I can ask, what do I have to do with TWRP_multirom_bacon_20150416-00? It's an img file, do I have to flash this first and then add radio.img to miui v6?

Thanks Again! :)
[ONE General] MMWolverine:
You can flash twrp image in current recovery, under Install in bottom right corner click the button "Images...", select img and on top "Recovery", flash and reboot recovery. Or you can use an app like Flashify and install it from the system. Whichever you prefer. ;)

Then add radio.img and reboot to Miui, sensors should work ok. You can also compare Baseband versions between primary and secondary.
[ONE General] k_flynn:
Thank You very much sir! :D
[ONE General] ak0r:
Can anyone confirm the latest baseband version of 15-05 firmware? Just to know if flash via recovery works :D
[ONE General] @rvg:
After updating multirom i am not able to boot my secondary roms which are oxygen n exodus...oxygen is stuck at oneplus logo screen and exodus at boot animation...

I am using cos12 as primary rom with franko kernel...

Plz help guys...
[ONE General] rucioTozzy:
Yap, I'm no luck in 32k, either. The only version I can boot second Oxygen or hydrogen rom is 32h, but it can't boot miui and change radio with multirom function(32i can boot miui successful and change radio, not test 32j and 32k yet.)
[ONE General] MMWolverine:
I flashed Miui on 32j and installed fine, not sure about Oxygen. For that rom it's best to use 32h. Regarding bootloops on bootanimation, a reflash or delete-flash should make it boot.
[ONE General] Go48Roms:
Im sorry if this question is stupid. But what is the meaning of up and running?

Does that mean

- I installed multi-Rom

--> I flashed CM12 (thats my plan) normally as primary

--> then flash CM11 as secondary

-----> At this point I should be able to boot everything up? But I will have stuff like proximity sensors broken. And now I need to flash the files?

Thanks in advance, this is my first use of multi rom. So I'm still a bit scared :p
[ONE General] MMWolverine:
Hi,

with "MultiROM up and running" I ment setting-up MR: installing MultiROM zip, modded TWRP and flashing a secondary rom. I can see you already did that, so you should be able to boot in both CM12 and CM11.

To fix the proximity sensor you can flash CM11 modem on CM12 rom through fastboot, because latest multirom twrp recovery still won't install firmware as zip (I'll put my cmd program in OP). And flash my prox. sensor fix zip in recovery.

Or you can use older Multirom/TWRP versions do add kiktat modem as radio.img in secondary CM11. Links & instructions should be in one of previous posts.

Best way to check proper modem version installed is to compare baseband in About phone section.

KitKat CM11 modem (radio): MPSS.DI.2.0.1.c7-00020-M8974AAAAANPZM-1

Lollipop CM12 modem (radio): DI.3.0.c6-00241-M8974AAAAANAZM-1
[ONE General] ramola:
I flashed CM12.1 firmware then flashed CM11s firmware modem (radio) and then cm12 proximity sensor fix ... all from twrp install menu.

I am on CM 12.1 as primary and Mahdi KitKat as secondary... before flashing i was getting problem for proximity sensor in Mahdi. But now after flashing getting problem over both.

I want to revert back. Should i flash Only cm 12_restore_proximity sensore file ...? Or will need to do something more...?
[ONE General] MMWolverine:
Yes, that zip will restore sensor blob, but check if cm11s modem was actually installed. Compare version numbers I posted above.
[ONE General] Acill:
I had a hard time with my sensors too and flashing with TWRP never seemed to work. At the advice of someone else that I dont remember I tried flashing using fastboot. This did the trick. The command is fastboot flash modem xxx.bin and its should work out much better.
[ONE General] MMWolverine:
Thanks, short tutorial with a cmd batch file is already in op. Users need only extract .bin file into the folder and run install.bat, phone will boot in and out of fastboot. Or input the command manually.
[ONE General] ddsoft:
Just got my OPO yesterday and I have been jammed up with the proximity issue from lollipop 5.1.1 after flashing several custom roms. This post really saves me from just depressing with the old cm11, which isn't bad at all, but I've been waiting too long to test lollipop and I finally can enjoy it ! Thank you so much:good:
[ONE General] jordany_91:
Can"t get it done at all!!

seems like i can't get it done at all!!!

so, what i have is cm11s (Unofficial-cm-11.0-XNPH05Q-bacon-signed) which is the flashable zip.

i want it (CM11s) to stay as primary, and be able to get cm12 (cm-12.0-YNG1TAS2I3-bacon-signed) and blisspop 5.1 cm12.1 kernel based(BlissPop-v3.5-bacon-OFFICIAL-20150623-0855) and some other cm11 and cm11s roms.

but i'm not able at all to get multisystems working, i tried all the suggestions in this thread. but i always get stuck in boot loops and so..

i'll post the basic method that i followed,(with which i was able to get some cm11 and cm11s roms up and running with multirom)

i am using multirom manager app, in which i tick multiromv32k, recovery 2015-07-02(0) and kernel 4.4.x

once downloaded i choose reboot and let do its work (flashing twrp modified for multirom, kernel and multirom mod itself)

after that advanced>multirom>add rom>select zip>select zip and flash a cm11 or cm11s (or based on) rom/s then run >run restorecon

and everything is fine.

but when flashing any cm12 or cm12s (or based on) roms and following the guide i get bootloops and softbricked, and i then reflashing through fastboot the original rom (cm11.0 xnph05q) then restoring the backup.

can some one pleaaase give me a step by step tutorial based upon the info i provided??

most important i want cm11 (05q) as primary

cm12 YNG1TAS2I3 as secondary

and blisspop as secondary.

the mobile is new, so there's no problem in wiping it to stock :D
[ONE General] MMWolverine:
Based on your info I can presume you are lacking cm12 firmware on primary, that's why your secondary lollipop roms won't boot. So now that you have cm-11.0-XNPH05Q installed, flash CM12.1 firmware (05-05 or 15-05) and right after CM11s modem (both on primary) and then reflash secondary roms.

Hope that helps, we'll resolve proximity sensor error once you successfully boot.
[ONE General] jordany_91:
i should flash CyanogenOS 12 firmware (YNG1TAS0YL) or CM12.1 firmware (05-05-2015) on the primary (cm-11.0-XNPH05Q) ?

should i first try to just flash the firmware and the cm11s modem over the primary and try to boot into it before flashing a secondary?? in order to be sure that it boots normally
[ONE General] MMWolverine:
Yeah, you can even flash CyanogenOS 12 firmware, CM11s should boot fine. But some secondary lollipops may need latest firmware, so if you get flashing errors later on, you'll want to upgrade to fw 15-05. For now just test that primary boots and proximity sensor works with cm11s modem.

Oh one more thing. Because newest TWRP recovery refuses to install modem as a flashable zip, check my guide how to install it via fastboot (in 2nd post along with ModemFastbootFlash.zip).
[ONE General] jordany_91:
well, i had cm-11.0-XNPH05Q running as primary, and carbon 4.4.4 as secondary.

both booting and runnning well.

i flashed CM12.1 firmware (05-05-2015) on primary (on primary from main menu of twrp)

CM11s modem (on primary from main menu of twrp)

flashed cm12 YNG1TAS2I3

then you replied me and told me to flash through fastboot, so i got the NON-HLOS.bin from cm-11.0-XNPH05Q-bacon-signed-fastboot.zip and ran you install.bat and followed yourr instruction (booted into fastboot from recovery, flashed the non-hlos.bin, then rebooted)

and now i'm stuck in a loop of the (1+ powered by android) screen.

i am now flashing a clean cm-11.0-XNPH05Q-bacon-signed-fastboot.zip theough fastboot.

can you please give a tutorial STEP BY STEP pleaasee :D

i''ve been over this for two days now.

oh and if you know a working modified-twrp to flash the modem from there it'd be better :) thanks