yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] osm0sis:
Haha yesss but.. flo/deb also? :D
[Nexus 6  Original Android Development] H4X0R46:
An update would be awesome! I LOVE multirom! :D
[Nexus 6  Original Android Development] nkk71:
i have no idea :o

adb pull /dev/graphics/fb0

:p
[Nexus 6  Original Android Development] aoaleman:
What does this mean!? lol :D
[Nexus 6  Original Android Development] Captain_Throwback:
It means that anyone should be able to clone the device files and produce a build. Whether that build will work is a different story, especially if the person building it doesn't have the device on which to test.
[Nexus 6  Original Android Development] H4X0R46:
Hopefully Tassadar himself will be back with an update soon. We can hope! :P Till then, nothing I've found is broken to the point of being unusable, but the multirom TWRP is getting dated.
[Nexus 6  Original Android Development] Captain_Throwback:
Just because I set up a build doesn't mean it works, especially since I have no way to test it.....:rolleyes:
[Nexus 6  Original Android Development] deeplyyoung:
Guys a Surprise for all the MR lovers...

A HUGE THANKS TO [MENTION=1162986]Captain_Throwback[/MENTION] to make it possible...

TRY AT YOUR OWN RISK

MULTIROM V 33
[Nexus 6  Original Android Development] nkk71:
scale the screenshots mate ;)
[Nexus 6  Original Android Development] H4X0R46:
Anyone test this and can confirm it doesn't create a physical paradox that makes the world implode on itself and set the year to -2016? LOL the unofficial version of course.

In plain English, does this work well?
[Nexus 6  Original Android Development] aoaleman:
It has worked so far. Backed up, restored, flashed new ROM, etc.
[Nexus 6  Original Android Development] H4X0R46:
Tried it for myself, currently posting this comment on the newest Chroma as secondary! Great work! :D I'm gonna have to get used to the new layout of the recovery, but it works perfectly and I haven't seen an issue yet! Thanks!
[Nexus 6  Original Android Development] garywojdan81:
Works great, thanks Cap!
[Nexus 6  Original Android Development] nkk71:
how can you confirm a paradox in the first place... isnt that the whole point of a paradox :confused: :rolleyes:

i'm sure this will come back with some kind of witty remark
[Nexus 6  Original Android Development] H4X0R46:
Very carefully. How's that for a witty remark? LOL but nah, I got nothing.
[Nexus 6  Original Android Development] H4X0R46:
Out of curiosity, do you guys ever leave your phone booted into secondaries all the time? Even when charging overnight and what not? I always boot back to internal before I charge my device overnight just cause, anyone else just always have their phone booted in a secondary?
[Nexus 6  Original Android Development] demlv:
Yes, secondary rom booted almost exclusively for months at a time.
[Nexus 6  Original Android Development] H4X0R46:
Wow, and no issues at all?
[Nexus 6  Original Android Development] arifqur:
Actually been using MR for ages since the Nexus 4 across many devices and if I am on a secondary, I remain on it for days and weeks on end and then maybe flash another Secondary and then jump to it. Never had any issues for day to day requirements and usage.
[Nexus 6  Original Android Development] H4X0R46:
Cool! I always boot back to primary at the end of the night as a precaution, but I would choose to use cyanogenmod more, I find that cyanogenmod with elite kernel, and CPU governor set to elementalx just makes for stellar battery life!
[Nexus 6  Original Android Development] H4X0R46:
There was also talk a while back about a workaround to kexec, was this ever implemented? I just use a kernel that has the patch, but someone mentioned a work around that worked without it. What happened with that?
[Nexus 6  Original Android Development] amritanshu001:
There is an option "Enable No-Kexec workaround" in Mulitirom ->Setting Menu. Maybe you can check it out and tell us the results :p
[Nexus 6  Original Android Development] deeplyyoung:
In future we will boot secondaries without Kexec but as of now it's not possible :D
[Nexus 6  Original Android Development] Captain_Throwback:
Does the option not work?
[Nexus 6  Original Android Development] H4X0R46:
I haven't tested it myself, but I don't think it works yet. Hopefully soon! It would be cool to not require a "supported" kernel!
[Nexus 6  Original Android Development] nkk71:
Errors?, Logs?, Details?, etc ;)

EDIT: description and details of the no-kexec-workaround can be found here http://xdaforums.com/showpost.php?p=64248526&postcount=4
[Nexus 6  Original Android Development] H4X0R46:
Throwing this out there, AICP flashes and boots with this unofficial multirom version! Also, as for the kexec workaround, I might get around to trying it sometime.
[Nexus 6  Original Android Development] Droidphilev:
Thanks for the update. Will try asap
[Nexus 6  Original Android Development] nkk71:
Glad it works and all,

but

it would just be nice to say why it didnt before (if it didnt?), what version, what script, etc.

the

"it doesn't work" posts

"it works" posts

"i think it doesn't work" posts

are not very helpful .... especially in a development thread

i'm neither saying "IT" works or "IT" does not (whatever "IT" is being referred to), but still .... not even a decent name of file / rom / link / version.... :rolleyes::rolleyes:
[Nexus 6  Original Android Development] H4X0R46:
Well we all know what we're talking about in this thread lol but in all seriousness, I don't know why AICP didn't work before. It would flash fine, but get stuck on the boot animation and never boot. As for why, I have no idea why it did that. Just tried it with the new multirom and was surprised it booted.
[Nexus 6  Original Android Development] nkk71:
ah my bad, didn't know that, thanks for making it clearer
[Nexus 6  Original Android Development] Droidphilev:
I'm sorry for giving you doubts. I'm still on the last official build and never had any problems. I only wanted to thank you for updating, nothing more. I understand that you implemented no-kexec, right? I will try to find a kernel that is not Multirom-ready but i'm afraid only a stock kernel is such a kernel. Testing this would re-encrypt my device.
[Nexus 6  Original Android Development] nkk71:
Whether to test it or not is entirely up to you... I am

in no way

encouraging people to use it or even test; since you have kernels with kexec-hardboot support (which is Tasssadar's preferred method) you can easily stay with those.

the workaround is "an option" which (depending on device) one can use, or not... if you're happy with the way it's working for you, then that's perfectly fine

btw, as mentioned here ... you don't even need a different kernel, options 3 and 4 would ask / force the workaround to be used.

As I mentioned, I don't know if it works on your device at all / not / how well, since I don't have it, so there's no way for me to test, nor am I asking anybody to test it.

It was originally developed for the HTC One M9 (due to lack of kexec-harboot kernel and tools), and since it was working nicely, I continued it for the M7 and M8.

Other devs have decided to try / use it as well.... but that is at their discretion.

As I mentioned, if you're happy the way your setup is, then i'm not asking or encouraging anyone to use it.... If on the other hand someone does test it, and wishes to report back that's entirely up to you guys

It is a workaround, and the post I linked earlier explains exactly what it does, so please bear that in mind at proceed at your own discretion.
[Nexus 6  Original Android Development] H4X0R46:
I was going to test it myself earlier, then I was thinking "man, what if that just corrupts my memory?" Worst case scenarios (possible or not) kept be from trying it. As of now, I really really like Elite kernel! Use it in all my roms, it also has kexec, so been using that.

---------- Post added at 03:13 AM ---------- Previous post was at 03:10 AM ----------

Also, could you link me to the post where you mentioned how the workaround works? Can't seem to find it for some reason. Thanks again! :D
[Nexus 6  Original Android Development] wrongway213:
You were attempting to use the 4/10 modified Franco kernel from Chroma, yes? That's where the issue is, not in the ROM itself - the kernel that came with Chroma 4/10 build did not have kexec hardboot implemented. I suppose you don't technically have to be running Chroma to use zephiK's modified Franco kernel - that is what you had been trying to use when errors arose though, correct? If not I have no idea why this line is in your log - my post and explanation was all based on assuming the following line from your log reflects the kernel you were running, which does not have kexec hardboot support:

<5>[ 0.000000] Linux version 3.10.40-unofficial-franco.Kernel-r26 (zephik@ubuntu) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Fri Apr 10 02:53:28 EDT 2015
[Nexus 6  Original Android Development] elevatorguy:
Never attempted anything from chroma. Don't know what kernel validus or crdroid use. I thought only the primary rom needed the patch but could be totally wrong. Also I never flashed any kernel just rom, gapps and su.
[Nexus 6  Original Android Development] wrongway213:
Bliss doesn't use Franco, Validus is not on 5.1 so it wouldn't be using that particular Franco.. I have NO idea - I think that maybe I am in fact as unable to read logs as I originally thought, lol. The line I posted does seem to be pretty clear, I have no idea why it'd be in your log if you are not using that kernel - but as I said, this is the first attempt I have ever made to decipher a log for someone.. given I saw a kernel that didn't have kexec in literally the firs five lines I just assumed that was it, lol. It also appears to list your primary ROM as AOSIP... I really don't know man, gonna have to let someone who knows how to read logs get into this one. As for primary kernel being the only one that needed kexec patch, that is my understanding as well.. hope someone can make some sense of the log I clearly failed miserably at trying to help you figure out lol
[Nexus 6  Original Android Development] elevatorguy:
No worries man lol. I don't know if it makes a difference but everything I'm running is 5.0.X no 5.1 till xposed gets all sorted out. I will try and install again tonight if it's a no go will post another log and exactly what I have installed and tried to install.
[Nexus 6  Original Android Development] demlv:
I could have installed a secondary rom directly onto an OTG drive, but I didn't. :(

So can I manually move a secondary rom from internal storage (data\media\0\multirom\roms\[rom_name_here]) to an OTG drive AND make it bootable? Anyone know of a how-to?
[Nexus 6  Original Android Development] Tasssadar:
You have franco.Kernel #26 in your primary, it doesn't have kexec-hardboot patch enabled (basically franco forgot to turn it on in the kernel config during build) - you can tell by "kexec_load failed: Function not implemented" in the log. MultiROM is unfortunately not able to detect that right now on Nexus 6, so you get that black screen with log instead of a nice "Kexec-hardboot patch required" warning. Flash different kernel with the patch for now, I'll notify franco and see what I can do about detecting the presence of the patch.
[Nexus 6  Original Android Development] elevatorguy:
I must have posted the wrong log( If I did I apologize ahead of time for the confusion) I'll post the one from when I tried this morning and see if something is different. Have vindicator kernel installed now and in app it says kexec-hardboot patch present. I have never run franco kernel always been on either sensei or vindicator. Will try and post it when I get near a computer for some reason can't attach a log using mobile app. Thanks for the help.

Edit attached new log

Again thanks for the help
[Nexus 6  Original Android Development] Tasssadar:
That's an old vindicator kernel with wrong version of the kexec-hardboot patch. The dev just couldn't wait for my release so he tried to do it by himself, with disastrous results. I don't know if it is fixed in newer versions, but bug him about it.
[Nexus 6  Original Android Development] elevatorguy:
That would explain it. Don't think he's updating his 5.0.X kernel he's on to 5.1 but I'll try shooting him a message to ask, can't hurt most he could say is no. Thanks for your time. Have a good one
[Nexus 6  Original Android Development] wrongway213:
Lol I was so confused.. Like I know I'm a total noob at reading logs but it seemed very clear to me that you were on Franco from Chroma... Glad Tasssadar got a look at it and now I don't feel like a total dummy
[Nexus 6  Original Android Development] elevatorguy:
Right log wrong log still don't know how chroma or franco came up in that log, I've never ran either. But weirder things have happened ?
[Nexus 6  Original Android Development] SilentO:
My device would freeze at the, "Google" screen.

1) I have 5.1.0 (LMY47I) installed as my primary and installed MultiROM via MultiROM Manager app.

2) MultiROM Manager indicates that I have kexec-hardboot patch installed, green font.

3) I installed my secondary ROMs using these steps, in recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.

I have tried the following as my secondary ROMs but all hung at the "Google" screen.

1. [ROM][3/21/15] - CleanROM 2.2 -★| 5.1 LMY47M | Aroma! | Clean! | Super Stable!

2. [ROM] Terminus [Android 5.1.0_r3 LMY47I][shamu][RRO - Layers]

3. [ROM][N6][5.1 r5][LMY47O] Chroma – 04/17/2015 | Native LED | Layers

4. [ROM][5.1 LMY47O[Shamu][Apr 14] Euphoria-OS 1.1

Please help!

Thank you
[Nexus 6  Original Android Development] wrongway213:
Are you actually adding these ROMs normally, or adding them as Nandroid backups? You have to run he restorecon command on any backup that you wish to install as a secondary ROM - the issue is nonexistent on primary ROMs. Based on the behavior you described, I am guessing you simply need to run the restorecon command on your secondary ROM backup you are trying to boot from and all should be well. If I am wrong and you are not restoring backups, but instead simply trying to add ROMs, I would have to ask what kernel are you using on your primary? Are you using an older Vindicator kernel or Chroma's modified Franco kernel from 4/10 build? Those kernels will say they have kexec hardboot support, but they don't. If none of this helps, you may want to get a logcat for Tasssadar to look at - hopefully something in this post will be enough to fix your issue.
[Nexus 6  Original Android Development] cmh714:
BlissPop for sure works... since thats my second ROM.
[Nexus 6  Original Android Development] demlv:
I installed the NexZen rom yesterday as a secondary rom -- installed as a .zip (not from a nandroid). It worked fine.

I had only one tiny surprise to deal with. The install/injection of the multirom zip in recovery did not happen automatically upon rebooting, like it does in most video reviews of multirom. Instead, I had to do it manually.
[Nexus 6  Original Android Development] SilentO:
Thank you for the responses cmh714 and wrongway213.

this is my first time trying to get multiROM to work.

I started with a clean installation of 5.1 version LMY47I. I then rooted it and installed MultiROM via MultiROM Manager app. Following the installation of MultiROM, the system rebooted into recovery and updated kernel and recovery then rebooted into android. When I opened the MultiROM app, it indicates that i have kernel, kexec-hardboot.

I then booted into recovery and installed my secondary ROM through selecting Advanced -> MultiROM -> Add ROM.

I powered off the device. When I powered on the device, it prompted me to confirm the OS to boot. I tap on the prompt to get to MultiROM screen to select my secondary ROM. I tapped on the secondary ROM twice and device attempted to reboot but freeze up at the Google screen.

Will try blisspop but any other suggestions would much appreciated
[Nexus 6  Original Android Development] wrongway213:
I would suggest pulling a logcat from ADB and submitting to Tasssadar - if you are unfamiliar with how to take a logcat via ADB, this thread should help guide you: http://xdaforums.com/showthread.php?t=1726238 I'm not 100% on what the command would be for this or I'd just tell you, I think it's "adb logcat *:E > crash.txt" but I am NOT 100% on that - I would advise reading through the thread and finding the proper command to get a log to output when your device will not boot.
[Nexus 6  Original Android Development] SilentO:
After days of fiddling around, I found the root of the problem. My OTG USB drive was extFAT which is not compatible. I reformatted the drive to FAT32 and was able to boot several different ROM.

Thank you
[Nexus 6  Original Android Development] pinoyflayv:
Clarification please...

Setup - Primary - Stock 5.1 with Franco Kernel r26

- Secondary - CM 12.1

If and when r27 comes out, do I need to update my Primary's kernel from the the Kernel Updater App or download the zip and flash it from the Recovery? Love my setup and do not want to brick or start all over again. Thanks in advance.
[Nexus 6  Original Android Development] fuzzybuffalo:
You can update it either way, but you need to go to recovery and inject current boot sector before booting up.

So the zip would probably be easier.

As per OP

Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.

You just need to do this for the primary ROM, every time you update primary ROM or kernel.
[Nexus 6  Original Android Development] nkk71:
There is always a chance of something going terribly wrong when modding your phone... be that from normal ROM flashing, MultiROM, no-kexec-workaround, xposed, and all the other mods out there.

(even SuperSU had a "flaw" of sorts in earlier version, where it would null out the entire boot partition prior to flashing it.... on a non-MultiROM ROM, that's just fine... but since MultiROM symlinks the boot partition to a regular file, the nulling out would continue until all your storage has been filled - not [probably] overwriting anything, but still; info here )

Which is why all and any modding, should only be done when someone is willing to accept that

fact

... there's nothing 100% safe about modding a phone.

As I said, if you're happy with your setup, dont change it.... if you feel adventurous that's entirely and individual decision; and I make no guarantees either way.

The only thing I do ask, is to be provided complete information. That is the only way, to be able to debug and improve something.

As for why the ROM you mentioned previously didn't work, but now does, is possibly due to the many post february 10 build changes, or even something in the ROM installer script.... but obviously I can't say which change that would be, since I dont know pre and post versions of the ROM in question.

---------- Post added at 12:33 ---------- Previous post was at 12:32 ----------

was in the post above yours :p

this one here explains what's going on: http://xdaforums.com/showpost.php?p=64248526&postcount=4
[Nexus 6  Original Android Development] H4X0R46:
Oh THAT post, alright! Must have saw that earlier today and forgot to go back and check it out lol So how exactly does the workaround change mounts? Like, the nerdy details of it I mean. I know the normal way using kexec can switch kernels without a reboot thus loading another ROM, that's how that works, but as for the workaround, what is it exactly that allows the switch?
[Nexus 6  Original Android Development] Droidphilev:
Testing is np for me. I know what can go wrong. I tested the earlier unofficial builds before they were released in this thread.

About the no-kexec patch you implemented. You wrote it's not needed to use another kernel to test but correct me if i'm wrong:

I know about the settings that this patch involves (i use a Multurom version on my tablet which has this patch). How would one be able to test if no-kexec works on the nexus if the used kernel has the kexec patch? I think you would like also to know if the patch itself works and not just the popup that is asking to use no-kexec. To test if the patch itself works we need a 'no-multirom' kernel flashed as primary kernel. If this isn't true i'm totally wrong (or we understand each other wrong. Sorry if that's the case. I'm not a native English speaker). Thats what i tried to explain: AFAIK all custom kernels for the nexus have the kexec patch so it could only be tested with a stock kernel. Since my device is not ecnrypted i'm not able to test that exact part. Maybe there's a volunteer that has an encrypted device and is willing to flash full stock as primary together with your build.

Correct me if i'm wrong! :)
[Nexus 6  Original Android Development] nkk71:
Options 3 and 4 in the advanced section "force the no-kexec-workaround", in other words... it doesnt care if your current kernel has kexec-hardboot support or not, it will disregard that (in option 3, it will ask you which method to use).

I've done this myself quite a few times on M7 and M8 (both of which have kexec-hardboot kernels).... I've booted the same secondary ROM(s) using both methods.

Just because the kernel does have kexec-hardboot, does not "override" the "forced" methods.

Okay, more details:

Usual kexec-hardboot MultiROM

Select secondary ROM

MultiROM detects a boot.img

MultiROM reads the secondary boot.img into memory

MultiROM initiates a kexec second boot

but

into the secondary boot.img from above

MultiROM continues

No-kexec-workaround MultiROM

Select secondary ROM

MultiROM detects a boot.img

MultiROM

flashes

the secondary boot.img into the primary boot partition

MultiROM initiates a full second boot

but

with the secondary boot.img in the real boot partition

MultiROM continues as usual

so the difference is in point 3... whereas normal kexec'ing loads the secondary boot.img into memory and goes from there, the workaround, actually flashes it to the real primary boot partition... and continues normally from there
[Nexus 6  Original Android Development] Droidphilev:
Off-topic: i guess this is why that to bootmanager boots twice before booting to chosen rom? (off-topic because i have this 'problem' on my other device)
[Nexus 6  Original Android Development] nkk71:
it reboots twice in either case
[Nexus 6  Original Android Development] H4X0R46:
Thanks for the explanation! Alright, so I'm thinking I'd rather use the normal kexec way, it just sounds a bit safer to me. If the workaround flashes the secondary rom's boot to the real boot partition, how does it replace the original boot when you boot into your internal? Does it just backup your original boot partition contents and restore that when it needs to?
[Nexus 6  Original Android Development] nkk71:
That's fine, I fully understand.

If you have questions about the workaround not already mentioned here

http://xdaforums.com/showpost.php?p=64248526&postcount=4

feel free to ask, otherwise i'm pretty sure i mentioned most / all of your questions in that post
[Nexus 6  Original Android Development] Polv89:
Someone tried to flash this as secondary?

http://xdaforums.com/showthread.php?t=3381845

Thanks

Inviato dal mio Nexus 6 utilizzando Tapatalk
[Nexus 6  Original Android Development] deeplyyoung:
Tried N preview 3 with EX but didn't boot..... Btw I'm using latest unofficial MR 3.0.2.. First time reverted to rom selection menu and then struck at bootlogo.... Might be someone else succeed...
[Nexus 6  Original Android Development] Captain_Throwback:
Did you try using (forcing) the no-kexec workaround?
[Nexus 6  Original Android Development] deeplyyoung:
del
[Nexus 6  Original Android Development] nkk71:
i was afreaid of the "it does not work post" :p ;)
[Nexus 6  Original Android Development] deeplyyoung:
waste
[Nexus 6  Original Android Development] greeneyez15o:
Restorecon
[Nexus 6  Original Android Development] H4X0R46:
What exactly does the restorecon option even do? I've never pushed it.