yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] magnamentis:
this man gave you a correct answer but considering your questions over pages now and the fact that you don't understand that simple

answer i recommend you to first learn how to flash, backup etc. from recovery, before attempting using multirom. i mean all your

posts from the last few pages were about basic knowledge and without that knowledge you should consider to learn first, but not here,

there are dedicated Q&A and recovery threads to learn about that.

please don't get me wrong, i'm not complaining that you do not have the know how yet, we all started once, the above advice is really well intent.

i just see danger for your precious device and endless discussions ahead otherwise. you at least need proper nandroid backups to start this path and for this you need a custom recovery anyways. so if you are not familiar with custom recoveries you most probably (certainly) don't have a nandroid backup and that's a no go IMHO to start with multirom.

i really hope you don't feel attacked it's not the meaning, but these are essentials
[ONE Android Development] xanthrax:
nice shoot magna, good!
[ONE Android Development] davidjumani:
I know the basics of flashing, taking backups and all that stuff. I've even ported and built several roms for my device but all I want to know is if multirom needs a custom recovery to flash the files it downloads or will it just flash and replace the stock recovery. I received two different answers, one saying that it needs a custom recovery and the other saying that it will work with the stock recovery and replace it with the moded twrp so I'm just trying to clarify.
[ONE Android Development] magnamentis:
the files to download has basically nothing to do with the recovery, it's an app you can download from the playstore which will tell you what it needs to make multirom work and you check the box and go ahead. one of the items you need is twrp with multirom functinality which will be downloaded and installed in the process. more than that i still don't understand you, if you have a rooted phone which you need for the app to function and flash roms you will usually use a custom recovery to do so. yes there are exceptions but i don't see the point to make it complicated if using a custom recovery makes everything so simple. i admit that i most problably don't get your point, why don't you just try it out, takes a few minutes at most ?

so make multirom work you need to have access to the various roms, you have to inject boot sectors, you have to make nandroids from the secondary and/or further roms, you have to be able to add roms and delete them, and i've seen nothing yet that would allow you to do all that without extremely good skills in terminal perhaps, if at all, to do all that without the proper custom recovery and the proper means, the one which comes with multirom which is altered to the extent that it includes the above mentioned and a few not mentioned features.

after all i say that something does not fit here and assume it's semantics :)
[ONE Android Development] xanthrax:
doesn`t matter which recovery you have , stock/custom , the multirom will download the required recovery and multirom ( whichever you chose from it) and it will flash /install them

but , if you`re on stock cm rom , from dev options deactivate "update cm recovery" otherwise it won`t flash the custom one

i hope it`s clear now
[ONE Android Development] davidjumani:
Thanks guys. That's all I needed to know. Sorry for troubling you :)
[ONE Android Development] MMWolverine:
I said it before and I'll say it again. Stop writing such long posts. You don't use capital letters and reading these everlasting sentences is a pain in the neck. You clog up every thread you're in, accusing users they're noobs. You are only confusing them further and having a handful of devices doesn't make one an expert.
[ONE Android Development] magnamentis:
to make it clear, i write what i want and as long i want as long as more people find it helpful than not. i'm fully aware what kind of problem people like you have with my mostly helpful posts and a) i stopped caring long ago, b) you're a minority, c) you gonna join my ignore list and last but not least d) you should put me on your ignore list if it's so painful for you, still better than starting attacks like that out of the blue and with no good reasons IMO of course. since i don't want to give someone a reason for real complaints i save myself what else i'm just thinking. basically i got good feedback for the very same post you're complaining about, it's obviously a matter of taste. end of BS
[ONE Android Development] venky61:
Hey,

Sorry... My bad for the first answer. I forgot that the recovery can be installed via multirom app too.

And always go with the OP's answer. They are the most reliable answers. Between following my advice wouldn't have brought you any trouble other than an extra effort of installing custom recovery by yourself first and modifying it with multirom app. I had TWRP before installing multirom. No issues.

Cheers. Hope you already installed it and having fun with the multiple Roms :D
[ONE Android Development] magnamentis:
as you're using multirom i have a question for once :)

did you already run a kitkat rom, cm11 for example, after having flashed the new OPO firmware ?

if yes, can you share the outcome ? if no i'll do it now and keep you posted

thanks

EDIT: i'm aware from your posts in bliss thread that you tend to a now, so my question is just whether you tried or if it's just a reasonable assumption ?
[ONE Android Development] Superm@π:
Delete
[ONE Android Development] xanthrax:
my cm11 doesn`t work on secondary after flashing the new modem , haven`t tried yet with the new firmware as i don`t have a custom kexec patched kernel yet on the latest Bliss rom

the rom is booting but as soon as i switch off the screen it stays like that

most probably it won`t work with the new firmware , modem , aboot.img and other stuffs won`t match the cm 11 , i don`t know atm why

ill give a try soon but i`m kinda bussy atm
[ONE Android Development] magnamentis:
sure thanks, that's why i will take the path in 5 minutes after bliss update is up and running and backed up :)

BTW i have a 44s modem zip so when i go back to CM11 ( still my daily for functionality ) i just flash that back and vice versa :), i'll let you know or the other way around, depending who's recovered from the brick first haha....
[ONE Android Development] tobitege:
[MENTION=5372360]magnamentis[/MENTION]: just as fyi: I have latest CyanHacker KK as primary and 5 LP roms as secondary. Flashed the CM-11 firmware (as mentioned in Bliss thread), booted into CyanHacker to confirm mobile/wifi; then back to recovery to flash the CM-12 extras zip and booted up secondary Temasek rom and all is good.

Looking forward to your experience with it. :)
[ONE Android Development] xanthrax:
so , all modems flashed as normal not on secondary , right ? well , i understand , cm11 firmware on primary for KK but you said cm 12 flash , on secondary ?

also , after flashing cm 12 update/extras doesn kk / primary boot ? and yes , how does it behave ?
[ONE Android Development] tobitege:
Yeah, forgot to mention: flashed both modem/firmware with primary "Install" button. Will check KK primary rom now (while CM-12 modem is installed).

Hah, surprise! CM-12 modem/wifi works (almost) perfectly on KK!!! Using 3G in Settings for mobile (but shows "H+"), LTE not sure.

Have baseband ".3.0.c6.5..." showing in both KK and LP roms.
[ONE Android Development] magnamentis:
long post with BOLD letters ahead, don't read if you don't like that

ok, here are my findings:

a) new firmware installed + new modem + today's bliss build + gapps + boeffla v3 beta4 = WORKS flawlessly

b) new firmware still installed ( not replaced by cm11 firmware ) + 44s modem + cm11 20150103 nightly + [MENTION=947981]Lord Boeffla[/MENTION] v2 stable + xposed = WORKS !!!!!! flawlessly

so my original question was whether kitkat cm11 works with OPO latest firmware from CM for LP CM12 and the answer is "YESSSSS!!!!!"

thus no need to revert back to old firmware to run kitkat roms

additional info: multirom, blissrom as mentioned above under paragraph (a) as primary ROM _ cm11s nightly from january 03rd as mentioned above under paragraph (b) as secondary ROM

i think that's good news, saves quite some work and risk to flash different firmwares back and forth
[ONE Android Development] tobitege:
[MENTION=5372360]magnamentis[/MENTION]: glad to hear it works for you, too! :)

Just to confirm: when you write in e.g. a) "new firmware installed + new modem"... do you flash separate files or the zip with complete set of files (like the CM12_Update.zip)? I assume the latter is the case, right?

I haven't spent much time in KK with the previous testing, so I cannot say how stable the connection or BT is.
[ONE Android Development] Natakranta:
Having CM12 radio and KK ROM on primary, when booted to it, try switch screen off and back on. I wander if you will be able.

With OPO alpha LP radio (the first which came out, but CM12 radio.img is exactly the same) my primary KK ROM - SlimKat 9 - was not able to switch the screen back on after I switched it off. DT2W, power button, nothing could switch the screen on. I had to hard reboot long pressing power button.

I flashed CM 44S radio back and all good on KK side, but new LP ROMs with changes for CM12 radio and stuff have problem with proximity sensor. I'm overcoming it by manually pushing old blob sensors.msm8974.so to /system/vendor/lib/hw/ set permissions and reboot. This way I can keep CM 44S radio to maintain fully working KK ROM on primary and have new LP ROMs on secondary. SlimLP and SlimSaber LP in my case. The blob I linked is from last old radio compatible SlimSaber LP Jan.08

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] tobitege:
[MENTION=5180758]Natakranta[/MENTION]: as usual, spot on, mate. I hadn't tested prox. sensor yet, indeed. Bummer. ;)
[ONE Android Development] magnamentis:
yes i flash the full cm12-update.zip but revert back the modem before booting into cm11. albeit the modem is included in that zip, the modem is independent. so i keep the firmware but flash back and forth the modem because the modem is not backwards compatible. the issue it causes for me is that with alpha modem the display goes black in cm11 on calls, while with the 44s modem the display does not switch off while in call as it should. so if i only update the LP rom (bliss) i let the 44s modem because i do not make many calls with that phone, while if i make longer tests or try out settings i flash the alpha modem to be fully functional. hope that explains it well, while it's of course a very personal situation, while others have fully switched to LP roms.
[ONE Android Development] tobitege:
[MENTION=5372360]magnamentis[/MENTION]: ok, understood. As long as there's a working workaround, why not use it. :)
[ONE Android Development] MMWolverine:
Now that's a proper constructive solution, instead of reading bed time stories how to flash back and forth. :good::D
[ONE Android Development] beany>:
My solution to all this KK/LP modem discussion you guys having : ditched KK ages ago. Bliss has been my daily driver for a while. Not keen on repeated re-flashing of the firmware.
[ONE Android Development] millomonk:
On Tasssadar's original multirom implementation for the nexus 4 there is an option to set a modem file for secondary roms.

Is there any chance to see this feature for the one, too? Well, maybe a stupid question. I don't know the technical background at all...
[ONE Android Development] tobitege:
It's probably not a good idea to have this feature on the One because with all the firmware dependencies it's not just a single file or partition to be updated.

Though I have seen that option on a MR port on my LG G3 actually, but never used it, yet.
[ONE Android Development] beany>:
Please excuse this tangent off topic people...

Is the OPO significantly different to other phones, like the G3/N4 mentioned?
[ONE Android Development] tobitege:
Probably not that much but with the recent QCOM firmware/modem updates from CM-12, their update involved 8(!) files for flashing.

On my G3 only installed a single file for modem update recently, but full firmware through full stock(-based) roms only so far ("hidden" for regular users so to speak).
[ONE Android Development] KINGbabasula:
I'll see what I can do with that USB OTG option missing and with that modem option
[ONE Android Development] gb_Texas:
Still not primetime... LP / 5.0 roms still have issues on OPO ... bluetooth music ... even with latest modem / blisspop 1.7, music from Play or Spotify is slow / stutters on my bluetooth headsets (multiple headsets) ... wired headsets ok, on phone speaker ok, but BT is not there yet... an issue not only on Blisspop, but all CM and even AOSP build (like liquid smooth) ... so my humble opinion is that it is the BT Radio firmware .... (on KKat, CM11s, with 44s radios, everything is fine)...

so waiting on the BT Radio fix...
[ONE Android Development] gerciolisz:
LOL i clicked FORMAT DATA and immediately typed yes instead of FACTORY RESET which i've done next and formated system etcXDXDXD shame on me.. To more fun my adb windows drivers wasnt working.. i had great fun waking my phone back to life after this mess (again) XD
[ONE Android Development] ImbaWind:
I flashed cm-12-20150118-NIGHTLY-bacon.zip as secondary ROM on top of CM11s as primary,it booted up without any problem but as soon as I unplug my OPO from my computer, it hangs and I'm not able to boot cm12 from multirom again, have to delete it and install it over again.

Anyone also got this problem ? Any workaround ? I head that CM12 only work if it's installed as primary
[ONE Android Development] kennonma:
Install the cm12 20150118 directly to secnrom without replace script update file?
[ONE Android Development] acuicultor:
Had two weird bugs this week with multirom, first bug was the impossibility to boot secondary roms even if my primary rom had the kexec hard boot, solved reflashing multirom zip in recovery and the second bug was when i flashed secondary rom, the kernel of primary rom was replaced with the one of the secondary rom flashed, this happened twice with different roms ( euphoria & temasek cm12 ). I have cm12 nightlies on primary, dont know why this happened and ever happened before when i was on kk roms. Hope someone can clarify why this happens. Thanks in advance.
[ONE Android Development] ek69:
U have to choose between cm11s or cm12 now due to cm12 needing firmware updates for kernel and modem changes. I read this problem in one of the commit comments section but I can't remember which one.

If you update to alpha modem it breaks proximity sensor on cm11s and also there's kernel changes that need newer cm12 firmware. Without that new firmware there's boot loops etc.

Sent From Lollipopified Bacon Goodness!
[ONE Android Development] moosha:
I tried to wipe data and cache the normal wipe through multirom recovery and it wiped my phone clean.... No os, no user data or anything O.o I lost more than 30 Gb of data :(

Has this happened to anyone else?
[ONE Android Development] pgr1979:
Hi KingBABASULA,

is it possible to update multirom recovery to twrp 2.8.4.1 ?

is it needed to flash some new CM nightly based roms, as you can see here :

http://xdaforums.com/oneplus-one/development/rom-bliss-stalk-team-bliss-bacon-10-28-t2921057/page571

thanks in advance for your effort!
[ONE Android Development] Natakranta:
No. I was doing clean flash on primary last week. I went to wipe - advanced: tick 4:

Cache

System

Data

Dalvik.

All good as intended. System, caches and user apps cleaned. Internal storage (SD or precisely /data/media - is where your pictures and music is being stored) preserved.

What do you mean by "wiping data and cache normal wipe". Please precise what you did exactly.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] xanthrax:
I believe he's working on an update

The latest twrp apparently is needed to stick with the latest cm12 firmwares though my thoughts are purely speculative not based on a proper deep investigation, this is what I've done myself after some attempts using older version if twrp and confirmed after update by other users

Well, one can flash the latest twrp update firmware and re-flash the multirom, simple

[MENTION=5432138]moosha[/MENTION]

It's only your fault, you've selected, by mistake I assume the option to wipe internal storage, that's all, be careful next time

Sent from my Darkside of 1+1
[ONE Android Development] moosha:
I mean the non advanced wipe... Which wipes everything other than sd card.... And it wiped that too :/ If I sound like a noob iam not lol.... I have been doing this from years.
[ONE Android Development] redline2097:
Can you please post link to CM 44S radio update zip?
[ONE Android Development] tobitege:
cm-11-firmware-20141224.zip (KVT49L/XNPH25R)
[ONE Android Development] redline2097:
Is this the latest? I get weirdly low wifi speed with this (2mbps and my connection is 20mbps).
[ONE Android Development] tobitege:
It was from the latest nightly from CM servers that did not fail to download. Can't say anything about speeds as I'm on LP already.
[ONE Android Development] KINGbabasula:
I've updated MultiROM and TWRP to the latest versions :)
[ONE Android Development] toge64:
which kernel can I use on CM11S to use multirom?
[ONE Android Development] skydayzer:
Ok Fixed it.. anyone using TWRP theme should remove it.. If you want to get the advance option!!!:D:D:victory::victory:
[ONE Android Development] clock51:
hello guys, how to install the gapps the second rom
[ONE Android Development] skydayzer:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.

Select "Flash ZIP" and flash ROM's ZIP file.
[ONE Android Development] Goggle81:
Check OP:

"Update ROMs"
[ONE Android Development] Robson187:
nvm.
[ONE Android Development] clock51:
same for gapps? flashed zip after the second rom, flash gapps also second rom zip
[ONE Android Development] skydayzer:
Thats how I flashed mine
[ONE Android Development] bud77:
To flash a zip on a secondary rom, read this http://xdaforums.com/showpost.php?p=54880471&postcount=155
[ONE Android Development] hamzahrmalik:
Anyone got AOSP working yet? As either secondary or primary don't mind as long as I can have Mahdi on the other
[ONE Android Development] bud77:
I'm running mahdi & pac rom.

And pac as main rom since few hours ;)
[ONE Android Development] hamzahrmalik:
No way. Me too!

Well actually mahdi is my main

But I want aosp :(

I'm an xposed dev and it helps a lot
[ONE Android Development] KINGbabasula:
It won't be long, I think I've almost fixed it
[ONE Android Development] hamzahrmalik:
And for the third time:

THANK YOU SO MUCH!!! :)
[ONE Android Development] bud77:
Guys, don't forget to rate the thread, 5 stars of course :D
[ONE Android Development] skydayzer:
Am running Mahdi + PA and CM11 nightlies.... Awesome Mod..

.................Grazie Per il tuo Lavoro, Ti Stimo........................
[ONE Android Development] Zed3:
[MENTION=5093942]KINGbabasula[/MENTION] This method works fine, you might want to add this to the FAQ section...
[ONE Android Development] bud77:
There is no 100% AOSP yet (maybe omni someday). All the rom have CM code inside (since they provide device trees etc etc)

The closest build to full AOSP is slimkat at the moment
[ONE Android Development] lukemo:
First of all really thanks to KingBaBasula for your job and support.

I confirm removing boot image works with cm11/ aosp roms (I have mahdi as primary and pa as secondary) and ak30b2 kernel.

No way as stated to multiboot with cm11s even using ak cm11s kernel...I hope that the "don't share kernel" options will be fixed soon to go on with cm11s testing vs other roms; for the moment the only partial workaround is to swap primary and secondary ROMS with cm11s.

EDIT: there is only one problem for me with TWRP multirom: it freezes if you don't keep awake the screen while operating in multiboot menu
[ONE Android Development] Zed3:
Freezes here as well, 64gb version
[ONE Android Development] tobitege:
[MENTION=5093942]KINGbabasula[/MENTION]: thank you donation: 4P800802AU831702D

Mile grazie! (is that correct?)
[ONE Android Development] KINGbabasula:
Thank you very very much :)
[ONE Android Development] laulau42400:
hi

Installation V30c ok then restarts but bootloop even after having re installed Temasek rom ??

And you?:crying:
[ONE Android Development] tobitege:
Update worked fine and reboots normally.
[ONE Android Development] Wongher:
Me too

After the installation Every secondary stops before the bootanimation and reboot into recovery.

My secondaries are all LP.
[ONE Android Development] KINGbabasula:
Maybe it's because you haven't updated the bootloader and other things to latest Oneplus firmware
[ONE Android Development] laulau42400:
Firmware 20.01 ok, that you put it the other day?
[ONE Android Development] mas_rock:
Help

Same Problem occur to me .

Today morning I upadated Multirom v30b to v30c and Then after that all my secondary rom swon't boot up .and When i tried to boot up any secondary rom it's show 1+ logo then automatically boot up into TWRP recovery.

In my primary rom I have Stock 44 s (4.4.4 Kitakt rom ) With AK.077 kernel .

And In my secondary rom I used beanstalk ROM (5.0.2 ) with AK.085 kernel .

So, In multirom V30b it's work But After updated Multirom It 's wont boot up .

SO, please help ....
[ONE Android Development] Wongher:
I have updated to the last made by tugapower,

And i have a secondary rom that's a cm12 nightly of 08/01 and that ROM doesn't need the last updated firmware.

Could be the kernel? Or because i flashed the cm11 dowgrade to boot my primary cm11s and than reflashed the cm12 upgrade?
[ONE Android Development] tobitege:
[MENTION=5831162]mas_rock[/MENTION]: install ak .090 (or newer) kernel in beanstalk and try again
[ONE Android Development] Wongher:
i have ak 94 on temasek and on crdroid but they didn't boot.

maybe we have to flash it on the primary, ( even if i konw that the last compatible with kk is ak87)
[ONE Android Development] tobitege:
I also have a KK rom as primary (CyanHacker; not in use anymore) and my secondary LP roms like Temasek and BlissPop just booted fine with Boeffla kernel beta6, haven't touched any other kernel in the past 2 weeks.
[ONE Android Development] ek69:
I just did this update myself and no problems. Cm11s as primary with ak cm11s kernel for the kexec patch no clue what version it is, haven't booted it since early Dec 2014.

Temasek is in secondary and booted up fine after update. I have never flashed a cm12 nightly just flashed the firmware updates that have been posted all over... Not sure why u guys are having issues

Sent From Lollipopified Bacon Goodness!
[ONE Android Development] mas_rock:
After you flash AK94 on primary ROm it's works bro?
[ONE Android Development] Wongher:
I don't think is a kernel problem because the guy over said that they can boot with a "old" ak cm11s kernel.

I'll try reflash multirom trough recovery instead of the app.

have you use the app?
[ONE Android Development] laulau42400:
Problem solved after a clean flash.

Envoyé de mon A0001 en utilisant Tapatalk
[ONE Android Development] mas_rock:
I Flash AK.099 kernel On beanstak rom but still not working ?

Help please ...
[ONE Android Development] duke_mac_l:
Can you please explain what you did.
[ONE Android Development] tobitege:
Anyone with boot issues after today's udpate:

when booting up the phone, observe the "Powered by Android" text at bottom of screen. IF that does NOT disappear after 3 seconds, you have not yet flashed the current firmware for custom LP roms. Please see link at bottom of my sig for a flashable zip of most recent firmware, which only needs to be flashed ONCE as it is not touched by any regular rom installation/update/wipe (no cache wipe needed, neither).

After flashing the firmware in recovery just reboot and try to boot into secondary rom again and see if it works.