yashsingh1/xdaforums huggingface dataset:
[ONE General] MMWolverine:
Hm, ok, let me check my modem-flashing batch file real quick, then I'm off to bed. Maybe there's sth wrong with the script, but I checked it was working fine before posting here.

I think this is the last TWRP that flashed modem/firmware without issues. https://www.androidfilehost.com/?fid=95916177934555897

Edit: my modem installation script is working fine (see screenshot below). Although I'm on COS12 the baseband version is CM11s, so modem partition flashes correctly. Maybe the full firmware was not flashed properly, but when a boot is stuck on 1+ logo it usually means sth wrong with the kernel. Or were you refering to the secondary cm12 YNG1TAS2I3 not booting? Not sure.

Best you try flashing zips in older twrp I gave you and we'll talk later.
[ONE General] jordany_91:
ok thanks i'm trying with older versions now multirom23h twrp201404016 and furnace kernel

no luck even with older version

the primary cm11s isn't booting. i am not even getting to the multirom boot part

---------- Post added at 01:34 AM ---------- Previous post was at 12:59 AM ----------

i have tried it all.... yet no result.

can you please try what i wanna do with the versions i want to achieve it and tell me your method. or anyone who tried it and worked for him, just a step by step for a desperate user

i'm just tired of flashing the rom over and over again in fastboot, and then restoring my backup....

thanks in advance for anyone who offers to help.

and big thanks to [MENTION=4842497]MMWolverine[/MENTION]

oh and if it helps, my running system is cm-11.0-XNPH05Q with the little (around 8mb) update that prepares the os to get updated into cm12
[ONE General] jordany_91:
Or if anyone got the two systems thing done with cm11s as primary. Please provide the method he followed with the all of the files versions (or links to them if possible) including multirom version, kernel and version, cm11 version, cm 12 firmware version, cm12s or 12.1 rom's version and modified twrp 's version
[ONE General] MMWolverine:
Instead of Ak kernel (the 4.4.4 in MR app) I suggest you use Boeffla kernel, which has official support for CM11s and COS12. Multirom works with it, only the boot animation time is a bit slower than with AK. http://boeffla.df-kunde.de/bacon/bo....0s_download/Stable/Series 2.x (for XNPH38R)/

Try the following steps:

1. have a clean fastboot installation of cm-11.0-XNPH05Q

2. in twrp 2.8.6 flash CM12.1 firmware (15-05) and CM11s modem

3. flash Boeffla kernel

4. flash multirom

5. check if it's booting

6. flash secondary roms and proximity sensor fix on Lollipops

7. check if they're booting

I used to have cm11s + cm12 firmware as primary and many secondary lollipop roms, so I know for a fact it works.
[ONE General] jordany_91:
ok trying now with all the versions you told me, and the old version of multirom multirom-20150425-v32h-UNOFFICIAL-bacon.zip

once the fastboot flashing is done, i'll report back. (and i won't be updating the system with small update that i mentioned above(which prepares the system for cm12 updating)

---------- Post added at 04:44 PM ---------- Previous post was at 04:28 PM ----------

still the same thing bootloops on the 1+ powered by android screen.

here's what i did in details

1.flash clean install of cm-11.0-XNPH05Q-bacon-signed-fastboot.zip > reboot (with fastboot reboot)

2.enabled developer options>unchecked update cm recovery>enable usb adb>recognized device (with adb devices) > adb reboot bootloader.

3,flashed twrp-2.8.6.0-bacon.img with fastboot. > reboot (fastboot reboot)

until here everything is fine, rom booted normally.

4.copied the files to my internal memory, multirom-20150425-v32h-UNOFFICIAL-bacon.zip, boeffla-kernel-2.10-CM11s-bacon.recovery.zip, CM11s_XNPH05Q_modem.zip, CM12.1_05.05.15_modem_firmware.zip, cm12_fix_proximity_sensor.zip.

5. rebooted into recovery, and from there added the queue of zips in this order CM12.1_05.05.15_modem_firmware.zip>>CM11s_XNPH05Q_modem.zip>> boeffla-kernel-2.10-CM11s-bacon.recovery.zip >> multirom-20150425-v32h-UNOFFICIAL-bacon.zip.

6.rebooted system (without deleting any cache or so, just hitting reboot system)

IT GOT ME TO THE SAME RESULT :( :(

---------- Post added at 05:35 PM ---------- Previous post was at 04:44 PM ----------

i even tried flashing super user right after the first boot (after fresh install) and booting >> everything ok

flashed twrp 2.8.6.0 and reboot >> everything ok

flashed kernel first (boeffla) and reboot >>> everything ok (wiping cache before reboot)

flashed cm12.1 firmware and cm11 modem >> BOOTLOOP AGAIN :( :( :[
[ONE General] jordany_91:
to new users

please can anybody with a FRESH new oneplus one, or a newly FULL WIPED oneplus one who tried this method and gt it done, tell me how did he do it step by step?? :)
[ONE General] MMWolverine:
A user in MultiRom thread is reporting the same problem. http://xdaforums.com/showthread.php?p=61756617

Maybe the developer or anyone else can explain why this is happening.

Sent from the One, it's Bacon!
[ONE General] jordany_91:
I tried posting on the developer's fthread, and even asking for previous versions, but i don't have privileges to post there. So my post went into Q/A thread and seems like no one lives there [emoji14]
[ONE General] lieuliau:
I followed your guide and now I have CM12.1 and CM11s running great. Thanks a lot!
[ONE General] jordany_91:
Can you please give more details?
[ONE General] drikkk:
I've rolled back from cm12.1 nightlies to cm11s and my screen goes black when calling.

I've flashed every radio/modem I could find from xnph33r to xnph05q. I've also tried the proximity sensor fixes from the start of this thread.

Nothing works. Screen goes black when making/answering a call.

If my headset is connected the screen lights up but the buttons does not work. Same when connected to car stereo on bluetooth....

Any suggestions what to try next?

Thank you in advance

Skickat från min A0001 via Tapatalk
[ONE General] MMWolverine:
Hi,

are you by any chance flashing radio in (multirom) TWRP recovery 2.8.7.0? Because that would be the only explanation, as radio won't install. You can revert back to 2.8.6.0 or flash the modem in my cmd batch program (instructions in 2nd post).

Check that older modem was installed - Baseband version for xnph05q is MPSS.DI.2.0.1.c7-00020-M8974AAAAANPZM-1.

Also you don't need proximity sensor fix on cm11s, so you can use my uninstaller zip to revert.

Hope that helps.
[ONE General] drikkk:
Hail to the KING!

It was the TWRP 2.8.6.1 version messing it up. The modems never got installed. I flashed TWRP 2.8.6.0 and then the modem and now it works like a charm!

Is there a problem with having the fixes installed on cm11s cos I couldnt find the revert zip in your first posts?

Thanks again
[ONE General] MMWolverine:
I'm glad you got it working. There shouldn't be problems having sensors.msm8974.so from proximity sensor fix installed, but just to be on the safe side here's the revert zip: https://www.androidfilehost.com/?w=...5b0235de8a8c31fc1ec745cdaef2e64356b7bce0f49db

Or you could delete /system/addon.d/KeepSensorFix.sh and dirty flash the rom, that'll restore original sensor blob as well. ;)
[ONE General] drikkk:
Done!

Great, thank you.

I know this may be OT but do you know if there still is a big difference in cm12.1 vs cm11s in battery time?

Sorry for the off topic and thanks again :)

Skickat från min A0001 via Tapatalk
[ONE General] MMWolverine:
I haven't used cm11s for a while now, but from my observations and user reports battery is worse on lollipop. Depends on the usage of course. I'm a heavy user with 300+ apps and get 4-5h sot on COS12, maybe an hour more on custom cm12.1. But rarely look at my stats, flashing often and multi-booting, charging inbetween. So it's hard to say, as long as it gets me through the day I'm satisfied.

Poslano z mojega LIFETAB_P9514 z uporabo Tapatalk
[ONE General] LuckyBtc:
Will CyanogenOS 12 firmware (YNG1TAS0YL) work on YNG1TAS213? I'm tired of bricking my one. I've been trying to install Nethunter all i get is an error after booting into Kali and once i boot Kali it bootloops.
[ONE General] LuckyBtc:
Ok thanks! gonna try it out again hope i'll not see a black screen with error again lol

---------- Post added at 05:00 PM ---------- Previous post was at 04:41 PM ----------

Bah! It doesn't works.
[ONE General] nicesoni_ash:
[MENTION=4842497]MMWolverine[/MENTION]

Hi mate,

I have an off topic question, how can I know whether I have a CM12 or CM11 logo in my oneplus? I have flashed CM11 as a primary rom and flashed CM12 as a secondary rom. I do remember that I flashed a CM12 zip to be able to flash CM12 as a secondary rom but that's a faint memory and I am not sure about that. I want to be sure before flashing a logo because last time I did that, I lost everything in my Oneplus and had to start from the beginning first by reviving it from its dead state.

I did ask the same question in another thread and was told that since cm11 is my primary rom, I have cm11 logo but I just want to have one more confirmation before I flash any modified logo on my oneplus.

Thanks.

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

Fueled by 7000mAh ZeroLemon Battery
[ONE General] MMWolverine:
This will be hard for me to answer, because I haven't changed logos and probably never will. Thinking logically, since logo.bin comes as part of the firmware, by flashing cm11 rom you most likely have cm11 logo (provided you were flashing in twrp up to 2.8.6.0 or via fastboot). But because cm12 as secondary needs new firmware, you'd need a working tool for cm12 logo and I'm not sure there are any out there.

Maybe someone else can confirm, again I can only guess and cannot be 100%.
[ONE General] nicesoni_ash:
There is one now recently released and working good by [MENTION=5448769]makers_mark[/MENTION]. I will however see about the logo issue. Thanks. ☺

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

Fueled by 7000mAh ZeroLemon Battery
[ONE General] MMWolverine:
Ah ok, I didn't know about that.

On a side note, in a few days I'm off to my vacation and won't be answering promptly. Thanks for understanding.

Sent from the One, it's Bacon!
[ONE General] nicesoni_ash:
Just to update if someone else is searching for, I needed to flash cm12 logo in my setup of dual rom as cm11 primary and cm12 as secondary.

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

Fueled by 7000mAh ZeroLemon Battery
[ONE General] gsmyth:
I had a multirom set up with COS12 on primary with CM11 roms on secondary, I then deleted the secondary roms and flashed the COS12 modem, everything seems to be working fine on COS12 except black screen when making receiving calls. I tried flashing the CM12 proximity fix but it didnt help, anyone any ideas?

[MENTION=4842497]MMWolverine[/MENTION] I tried your cm12 restore proximity sensor zip also but still getting the same issue.
[ONE General] MMWolverine:
Flash my zip to remove proximity sensor fix and restore original sensors blob: https://www.androidfilehost.com/?fid=23991606952599217

Then flash COS12 modem in TWRP 2.8.6.0 or through fastboot.
[ONE General] rahulrai:
I have BlissPop as primary rom & Miui as secondary. But I am getting black screen during calls. I can't disconnect the calls until the other party disconnect as the screen won't turn on. Any help will be highly appreciated
[ONE General] MMWolverine:
Try my 2nd post guide, a quick walk-through would be:

1. flash cm11s modem on primary BlissPop

2. flash proximity sensor fix on primary BlissPop

Use TWRP v2.8.6.0 to avoid issues with modem not installing.
[ONE General] gsmyth:
Thank you! that sorted it, I think I had previously flashed an earlier lollipop modem, whether that was the issue.
[ONE General] miksi:
Hello,

I have cm11s as primary and cm12s as secondary. I tried to flash latest cm12s ota incremental on secondary but it reports that I have the keys for first cm12s YNG1TAS0YL but he expects YNG1TAS2I3 which I have flashed already. Should I delete my CM12s and full flash the latest as secondary or there is a method to somehow use the OTA on existent secondary. And why it's reporting older keys? I followed instalation steps from this thread.
[ONE General] MMWolverine:
Hi,

this is because we're using TWRP recovery and not the stock CM, which also needs to be the latest version. I had same issue yesterday on primary CM12s and simply flashed the entire ROM package after a full wipe.

I'll post rooted recovery-flashable and fastboot-flashable COS12.1 in a few moments (to 3rd post). So you can flash the rom which I recommend, or stock recovery + the incremental OTA.
[ONE General] miksi:
So can I dirty flash the latest rooted recovery-flashable cm12.1s zip over my previously cm12s secondary rom to be able to keep apps and the rest or should just destroy existent secondary and flash another. Also is there any difference between earlier cm12.1 modem-firmware zip and this new content from posted zip. I should off course flash cm11s modem because my primary is cm11s.
[ONE General] MMWolverine:
I wouldn't recommend dirty flash, because it's an upgrade to 5.1.1. You could simply flash COS12.1 as secondary alongside CM12S and transfer your user apps/data with Titanium Backup from one to the other, then once you're satisfied delete CM12S.

Firmware in COS12.1 is the same as CM12.1 from May 15, the modem is the same as in OxygenOS Rom. Baseband version DI.3.0.c6-00241-M8974AAAAANAZM-1. So if you have CM12.1 firmware (15-05-2015) + CM11s modem already installed you're good to go. Flashing COS12.1 as secondary won't change firmware or modem, you just need to flash my proximity sensor fix.
[ONE General] gneville:
My Proximity / Light Sensors have stopped working - and not sure what else to try. I have tried the following:

Flashed CM11S

Flashed CM12OS & CM12.1OS

Flashed Modems individually (for relavent rom) - and tried Oxygen

If I try the app 'Light Sensor' on the Play Store- it tells me there's no sensor available on my phone.

Looking for any other suggestions really. How likely is it that the sensors have just failed?

I've also emailed Oneplus support - but don't hold out much hope for a prompt or useful reply (looking at other peoples experiences!)
[ONE General] MMWolverine:
First check if you have this file on this location: /system/vendor/lib/hw/sensors.msm8974.so

If you flashed my proximity sensor fix there should also be sensors.msm8974.so.bak

Also in which recovery did you flash modem? Anything past TWRP v2.8.6.0 won't install it. CWM or PhilZ should work fine.
[ONE General] gneville:
Thanks for the reply.

I'm back on CMOS12.1 now - I haven't flashed the proximity fix this time, but I will do.

Also - I made sure to use TWRP v2.8.6.0 for all the flashing I mentioned.

---------- Post added at 06:13 PM ---------- Previous post was at 06:08 PM ----------

Ok I flashed the proximity fix zip, and I have the file sensors.msm8974.so.bak.

However nothing has changed :(
[ONE General] MMWolverine:
Try flashing cm11s modem, but if that Light Sensor app still won't find sensors, there may be sth else faulty. Again, my fix only makes proximity sensors work when multi-booting kitkat and lollipop roms and won't solve any other related issues.
[ONE General] gneville:
Tried flashing that - doesn't make a difference.

Oh well, I guess it's just failed..!
[ONE General] ec0li:
Hi,

First, thanks for the proximity fix - Since lollipop my opo won't get LTE on any lollipop modem. I still don't know why, APN is correct, etc.

So each time I flash a lollipop rom, I have to flash a CM11s modem + the proximity fix.

Now I'm on COS12.1 and the proximity fix doesn't work anymore :(

I can flash an old modem, I get LTE, but the proximity sensor won't work with or without the fix.

Any idea?

Thanks
[ONE General] MMWolverine:
I tried to replicate, but proximity sensor fix works fine on COS12.1 with CM11s modem. See screens, original blob backed up, no black screen on call, turns off close to the ear. ;)

Please check that you have the correct baseband version (compare to my screenshot).
[ONE General] ec0li:
Thanks a lot for the help!

I have redownloaded the modem and the fix and tried again, it works now :D

I tried twice before without success, don't know where I did it wrong but anyway it's all good now.
[ONE General] CounterC:
If I follow flash instructions from the OP my modem version doesn't change. I tried 2 times already and it stays the same (modem 241).

I didn't flash firmware because I'm already on the latest. I'm on slimsaber caf latest build with ak kernel caf v13.

Any idea?

Edit: I have the sensor bak file so the flashing did something...
[ONE General] MMWolverine:
Are you flashing in TWRP v2.8.7.0 or v2.8.6.1? Because it won't install in either of those recoveries. Use TWRP 2.8.6.0 or if you have access to a computer flash in fastboot with seperate commands or with my ModemFastbootFlash.zip.
[ONE General] CounterC:
I was on TWRP 2.8.7.0 and then I downloaded and flashed 2.8.6.0 (TWRP 2.8.7.0 allows to flash .img files in recovery)

Now my TWRP is 2.8.6.0 and I still have the same result. Tried to flash the files in OP multiple times but in settings => about phone the version is always 241

EDIT: This is getting weird. I even tried with your fastboot zip to boot in fastboot and then flashed the modem like that. It succeeded but in settings => about phone I STILL see version 241.......
[ONE General] MMWolverine:
Try wiping cache and dalvik, used to fix it when no bandwidth was showing.
[ONE General] CounterC:
Can you please describe the exact steps that I should take?

- in recovery 2.6.8.0 wipe cache and dalvik

- flash 44s modem

- flash prox fix

- reboot

Is that it?

EDIT: I give up...
[ONE General] MMWolverine:
Since you already fastboot flashed cm11s modem you only need to wipe cache and dalvik in recovery 2.6.8.0. Also prox fix is already installed if you have sensor bak, so skip that.

Edit: strange this, I'll download SlimSaber-CAF and do a test myselft. Stay tuned.

Edit 2: Confirmed, baseband won't change on CAF, I tried Chromer19 and Sultan version as secondaries. Not sure why so I'll ask around.
[ONE General] CounterC:
Thanks man. Here is the thread http://xdaforums.com/showthread.php?t=3175742

Also the prox fix is not working for me. On calls the screen just turns black...
[ONE General] MMWolverine:
Well maybe that's a good thing. Since baseband changes fine on cm12.1 based roms (will surely even on cm11 and cm12), you can just flash proximity sensor fix on them and on SlimSaber CAF restore the sensor with this https://www.androidfilehost.com/?fid=23991606952599217.

I'm not sure which primary-sencondary ROM config you have, but with DI.3.0.c6-00241-M8974AAAAANAZM-1 baseband you don't need the fix. If you have cm12 or cm12.1 flash the fix.
[ONE General] f41lbl0g:
I just flashed the proximity sensor restore file, and all my sensors are broken now, good thing is that I can pick up calls now.
[ONE General] CounterC:
Dirty flash your rom and it should be fine

---------- Post added at 05:46 PM ---------- Previous post was at 05:41 PM ----------

Check my posts here : http://xdaforums.com/showthread.php?p=62694868

How do I know whether the cm11s modem is flashed?
[ONE General] MMWolverine:
In Settings About phone it's displayed as MPSS.DI.2.0.1.c7-00020-M8974AAAAANPZM-1. Same thing if you write this in android terminal

su
getprop | grep baseband

In Lollipop if cm11s is installed your screen would be always on during calls. Without the proximity sensor fix.
[ONE General] CounterC:
This is really going nowhere...

Might be that the modem files are embedded in the firmware files like mentioned in the CAF thread?
[ONE General] MMWolverine:
Yeah that's the only logical explanation and Natakranta wrote a nice response in that thread as well. Maybe sth can (or will be) tweaked in twrp & multirom, but I'm far from an expert in that development field to be 100% sure.
[ONE General] Natakranta:
We need [MENTION=3306843]kantjer[/MENTION] to confirm how it was adopted in SlimSaber, is the radio image included in the ROM built in firmware or not. I don't recall details.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE General] maxed4901:
Thank you for the welcome gesture.. I am confused. So will try to give as much details as possible.

I am on Multiboot Latest.

Stock (BASE) rom is COS12.1.1 (YOG4PAS1NO)

Secondary ROM1: SOKP5.1.1

Secondary ROM2: MIUI V7 (ported) Rom.

SOKP and base rom works fine.. sensors and calls and connectivity is also perfect. However, After installing MIUI rom which is based on 4.4.4 (KITKAT), i get black screen on receiving and making calls. except for this, all is ok. I can give code commands to network operator and connection with internet (3G/2G) also works.

How can i get myself to fix this? I have the modem for 4.4.4 flashable zip. Should i just flash it in multirom>list rom>choose rom and flash file? will this effect the modems used in other 5.1.1 roms? Would appreciate your advice. Thanks

Vlad
[ONE General] MMWolverine:
Hi Vlad,

you cannot flash any modem as zip in twrp multirom menu, because it won't install it.

You can do this: extract NON-HLOS.bin from zip and rename it to radio.img, then in multirom>list rom>choose rom (MIUI)>add radio choose that radio.img file. That will set kitkat modem to secondary MIUI, at least it should.

Or you can do this: flash modem 4.4.4 flashable zip on primary ROM (normal from install menu in TWRP) and then my proximity sensor fix to primary COS12.1 and secondary SOKP 5.1.1. That way you'll have kitkat modem on all roms, but with prox fix you'll be able to make calls normally on 5.1.1 roms. Note that for this you need TWRP v2.8.6.0!

Hope that's understandable and works for you.
[ONE General] gerciolisz:
Hi [MENTION=4842497]MMWolverine[/MENTION] i was trying to make exact same thing but i have euphoria CAF AS secondary .

And flashed cm11s modem on cyanogenmod12 on primary ----> miui worked like it should but euphoria dont want to fix proximity sensor after flashing your fix. It can be caused it is CAF based?

All best!

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE General] MMWolverine:
Your proximity sensor was broken even befor you flashed my fix? Euphoria is 5.1. and because modem doesn't change on CAF (lollipop modem is hardcoded in the kernel), you wouldn't need my proximity sensor fix. At least that was the case with SlimSaber CAF, maybe CraZY_BoY^'s rom is different.

I'll check in next few days if my theory is correct.
[ONE General] `SBR`:
I think only sultanxda cm12. 1 and kantjer slimsaber CAF rom has the firmware built in.. Other CAF roms are normal (not sure though) and we can flash the firmware over it.
[ONE General] gerciolisz:
Hmm i think it was broken before flashing fix but i m not sureXD i think i've read About a modem in CAF roms that is build in this euphoria too but again maybe i am mistake.. It was late and few beers too lateXD

I'll try today evening to flash everything clean and start again.

Also seems that after changing non-hlos.bin to radio.img filename and seting AS radio in miui gives me no SIM card error... I was trying 44 and 5q modems

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE General] avong:
thanks for the guide
[ONE General] cloudx720:
Why hasn't the cyanogenos team issued a fix for the compass/gyroscope/proximity? Baffled.....
[ONE General] gerciolisz:
Ok so i am back here.

AS i said before i am now on some cm ROM on primary (dunno which dont using it[emoji14]) secpndary euphoria CAF(with included modem) and miui.

So i flashed 44 modem on primary and proximity sensor is working good on euphoria:) and OFC on miui :)

Hope it will help someone:)

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE General] DrNinjaa:
I may sound Stupid...But I'm searching for any possible method to have oxygen OS modem to work on CM11 ,as I had a great reception in my place with oxygen OS modem but I really can't compromise stability,battery use of cm11 and the various bugs I have been facing during my use of lollipop roms.

Can Anyone answer my curiosity....Thanks