yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] JuveAddict96:
Thanks a lot.

---------- Post added at 05:13 PM ---------- Previous post was at 05:02 PM ----------

So, basically, the app was not updated, right? Latest twrp and mod I found there were from June I guess...
[Nexus 6  Original Android Development] Droidphilev:
Well... the fix is made by an offcial maintainer (Moto G) but it's not "official" so it's not in the app
[Nexus 6  Original Android Development] JuveAddict96:
OK, anyway I'll use this post to update it from now...the rom works now! ;)
[Nexus 6  Original Android Development] Droidphilev:
I don't know if other updates will come. You have the latest version now. The only problem left is slow booting to secondary (time between bootmanager and bootloader coming back to front is much to long). We are trying to get it fixed but found no solution yet.
[Nexus 6  Original Android Development] JuveAddict96:
Got it...hope you'll be able to fix it...
[Nexus 6  Original Android Development] :
I've seen an improvement of booting speed after flashing the stock decrypted kernel. Anyway, in Settings -> Security -> Encryption you have to see this as an option.
[Nexus 6  Original Android Development] BxingFetus:
A small issue I'm encountering when going from secondaries to primary, my Wi-Fi password on my primary seems to not stick, anyone else having this happen?
[Nexus 6  Original Android Development] cmh714:
Yes, but I cannot tell if its the password...just seems the radio is confused or something. But yes, having similar issues.
[Nexus 6  Original Android Development] Greedy242:
Question only when am flashing something on my internal ROM I would do the inject current boot sector but if am updating my secondary rom any of them after I flash (rom update/kernel/or mod) do I also inject current boot sector or jus restart like normal ...... Just asking cause I was uodating a secondary rom but it seem it didn't flash for that but my internal ROM instead had benzo as primary and aosip as my secondary then when I tried to reboot it said kexec hardboot patch not found but bear in mind my primary kernel already had the patch
[Nexus 6  Original Android Development] cmh714:
I dont need to inject into the secondary, I just flash the rom, gapps and anything else and then just boot up. I am using Stock as Primary and BlissPop for secondary
[Nexus 6  Original Android Development] wrongway213:
I have a question pertaining to the issue of Nandroids not restoring for secondary ROMs. I am new to MultiROM, the N6 is the first device I've owned that has it - please bear that in mind. I don't consider myself a "noob" otherwise, I just lack experience with MultiROM and don't want to mess my setup up. How are users getting around this issue with Nandroids restoring and still switching from primary to secondary ROM and vice versa without losing data? I assume that all your data is saved when you reboot as it normally would be without making a backup, then via kexec patch you can boot into a secondary ROM and use it for X amount of time, and then boot back into your primary and return to all of your data from before switching ROMs being right there without ever having taken any sort of backup at all. I am assuming this is the beauty of MultiROM, but I just want to be clear that this is the case as I have never used this - I do not want my first attempt to be at a time when an issue (Nandroids not restoring) causes me to be unable to properly use this release. If my understanding is correct, I would imagine it will not be an issue unless I mess something up and need to restore. If anyone is able to confirm my understanding of how this operates is correct or if I have missed something fundamental (I read the FAQ and OP but I believe it's assumed you've had some sort of exposure to MultiROM unless I missed this) it'd be much appreciated - I am more than ready to set my secondary ROM up.
[Nexus 6  Original Android Development] cmh714:
I am new to MutliROM as well and not a noob. But I believe that pretty much what you wrote is correct. Each ROM must be stored on Data since they are always there, but that also means they take up space, almost sort of SafeStrap like. So it still would be very nice to be able to backup and restore. Having said that, I have 3 ROMs: Stock, BlissPop, and AOSiP; and the first 2 each have 3 movies on them, and I still have 17GB free
[Nexus 6  Original Android Development] jelucas30:
Gapps

---------- Post added at 05:19 PM ---------- Previous post was at 05:11 PM ----------

Nevermind. Figured it out.
[Nexus 6  Original Android Development] z31s1g:
I've read your post thrice and still don't understand the question. Why do you assume that restoring a backup (of the main rom?) would cause issues?

You can use/backup/restore/wipe the main rom the way you're used to. And you can do just the same with the secondaries you install.

Restoring a backup of a main rom will not influence the secondaries.
[Nexus 6  Original Android Development] wrongway213:
If you read back through the page previous to this one, users have been reporting issues when attempting to restore Nandroid backups via MultiROM TWRP recovery. I have not ever used MultiROM before, I have familiarized myself with the FAQ and all of that, but as this is apparently an issue that has only been happening very recently, this is not something that is addressed. Basically I am just choosing to ask a question that a search is not yielding an answer to as opposed to delving into something I am not entirely informed about- just trying to be clear on how this issue will impact my ability to use MultiROM.
[Nexus 6  Original Android Development] z31s1g:
Time to make a backup and try a restore, haven't restored stuff in ages. BRB.

---------- Post added at 00:54 ---------- Previous post was at 00:42 ----------

Restoring backups made with mr twrp works. I don't have backups made with "normal" twrp, so I can't test that.

So if you make a backup after installing mr twrp, you should be save.
[Nexus 6  Original Android Development] demlv:
One advertised feature of multirom is the ability to restore a nandroid backup to a secondary ROM slot instead of clean flashing a new ROM. Based on what I'm reading, it is that function that is not working as expected.
[Nexus 6  Original Android Development] cmh714:
that would be correct, at least from my experience...doesnt matter if its from TWRP direct, or from within MultiROM.

---------- Post added at 05:03 PM ---------- Previous post was at 05:01 PM ----------

Well, I disagree since that hasnt worked for me, as I already posted
[Nexus 6  Original Android Development] Skripka:
I tried a MultiROM TWRP nandroid restore a few nights back. Bootloop city...and that was with only an Internal ROM at the time (no secondaries to muddle things up)
[Nexus 6  Original Android Development] wrongway213:
Well, now I just don't know what to think again. On 32a, 04-06 recovery or the previous versions? I've precisely waited until I got everything totally stable and working on 5.1 ROMs and kernels before trying to start using MultiROM so I would like to avoid bootloop city if possible.

Edit: seems the issue is whether restoring a Nandroid to a secondary is broken only, or if restoring secondary ROM data that has been set up clean flashed via MultiROM is broken entirely. This is what is unclear.
[Nexus 6  Original Android Development] Skripka:
IIRC it was 32a. I'm operating off memory. I was having bad issues of bootloop on Vindicator-kernel stock on Benzo...and tried 4 or 5 clean flashes...couldn't get it to run right. Tried restoring my nandroid to internal (from internal originally), and it wouldn't do more than bootloop. At which point I tried using a non-vindi kernel I had on hand and clean flashing and things have been hunky-dory ever since. Was chatting with one of my fellow TwistedSlim testers....on Hammerhead, he doesn't bother with nandroids on MultiROM as he never got them to work.
[Nexus 6  Original Android Development] crawlingcity:
logs !

Flashed a 2nd ROM and BOOM.

Log attached.
[Nexus 6  Original Android Development] fuzzybuffalo:
I got what looks like the same log file.

Are you using Chroma 4/10 as your primary/internal ROM, if so you can use Chroma as a secondary ROM or drop back to Chroma 4/7, either way works fine.

[MENTION=5964313]wrongway213[/MENTION] this might be of interest to you.

I just started using MultiROM today, but I have been playing with nandroid backups all day.

I was able to restore any nandroid to the primary/internal position. By any, I mean any nandroid made with Non MR TWRP 2.8.6.0, you need to inject current boot sector for this to work.

I was able to restore any nandroid made with MR TWRP to the primary/internal position. Even a nandroid of a secondary ROM.

I was not able to restore a nandroid to the secondary ROM position. I get the same as [MENTION=1875769]cmh714[/MENTION], Google screen, black screen, Google screen then TWRP.

But you can restore the secondary ROM nandroid to the primary position, then use Swap ROM button and copy it to a secondary ROM position and then restore your primary ROM.

It's the long way around, but it does get your nandroid restored to the secondary ROM position.
[Nexus 6  Original Android Development] umair shaikh:
Just one question...

After i install multirom can i flash other kernel (in my case franco ) coz i think it replaces kernel right ?
[Nexus 6  Original Android Development] crawlingcity:
Read post one again.
[Nexus 6  Original Android Development] crawlingcity:
Disregard my post. It's my fault.

I went on and read the logs, there was this line saying

<11>[ 15.025067] multirom: kexec call failed,

So It was kinda obvious the kernel didn't had the proper kexec patch , though I might be wrong.

I flashed Franco kernel, the original one and the problem is gone.

So for you and anyone else with this problem, chroma claims the kernel is the same with s2w etc, clearly, that is not the case.

[MENTION=452513]tassadar[/MENTION] ignore my logs, it was user's error
[Nexus 6  Original Android Development] Droidphilev:
I'm not encrypted and also tried a few different kernels. The problem is never there when booting to primary or booting to secondary from the multirom application. My friend is working on it for a few days now but no fix yet. I received 4 testversion and they had all the same problem. I also think it's not really kernel related (not sure!) because its only the fase between bootmanager and reboot to bootloader that takes longer as it should. From the moment bootloader spashscreen is shown the boot speed is normal again. Hopefully...
[Nexus 6  Original Android Development] jcrompton:
Please understand that the app is completely unnecessary for multi ROM to work. It just adds an in OS control panel if you will. The app has download links for the actual recovery goodies but the download links aren't updated to the fixed versions.
[Nexus 6  Original Android Development] demlv:
First, thanks for spearheading the effort to get MR for Shamu updated.

Next, I don't think I know what you mean in saying that the "time between bootmanager and bootloader coming back to front" is longer than expected. Mine certainly isn't instantaneous, but when booting to my secondary rom, it takes no more than 20-25 seconds to get from the bootmanager screen all the way to the initial boot animation. How long is this process taking for you? I'm more than willing to wait half a minute extra to have an extra rom or two available!!
[Nexus 6  Original Android Development] greeneyez15o:
Mine would take up to a minute to get to initial boot animation, depending on the kernel at use in the primary rom
[Nexus 6  Original Android Development] rotarydial:
Any insight appreciated.

I'm new to MultiROM. I am looking to play with Android Pay. I got everything installed and chose a bone stock ROM for my 2nd-slot ROM. I flashed the "base" from this post: http://xdaforums.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052

This file: (md5)shamu-MRA58K-base.zip

Everything got set up fine except that the phone/ROM isn't seeing my sdcard. Ergo I can't take pictures, etc.

Any idea how to get my storage found/seen?
[Nexus 6  Original Android Development] Droidphilev:
Hi,

Well... the problem is not the waiting time, the problem is that the waiting time is not normal :)

If i boot the device and bootmanager comes to front i press cancel to cancel autoboot to primary. After that i double tap a secondary rom. The time bewteen the bootmanager closing and the bootloader starting up is far too long (between 1 to 2 minutes) i only have a black screen.

---------- Post added at 06:22 AM ---------- Previous post was at 06:21 AM ----------

Encryption?

---------- Post added at 07:05 AM ---------- Previous post was at 06:22 AM ----------

Can i ask: which kernel(s) are you using?
[Nexus 6  Original Android Development] arifqur:
Try to flash a custom kernel like Elite on your secondary rom.

Seems like a read/write issue.
[Nexus 6  Original Android Development] Droidphilev:
Hi,

Can i ask: you use Elite on all roms? How much time gets spend between bootmanager and bootloader when you boot to secondary?
[Nexus 6  Original Android Development] arifqur:
No I use Elite, ElementaleX, and Despair.

If you mean when you select a secondary rom in the boot manager and a toast comes up saying "Booting cm13-blabla",

it takes like 2 seconds before it reboots to the Google splashscreen and starts to load the rom.

Literally like 2 seconds
[Nexus 6  Original Android Development] Droidphilev:
Appriciate your answer. I use Hells on all roms in flash. Will test Elite. I think we are talking about same fase, yes. Between choosing a secondary rom and bootloader.
[Nexus 6  Original Android Development] arifqur:
Seems like there is some other factor involved.

I don't think all of the modified multirom users have the problem that you have.

Maybe you should start fresh from a factory image and go from there.
[Nexus 6  Original Android Development] Droidphilev:
Probably, had to flash a lot testbuilds the last weeks. You are right, will start fresh
[Nexus 6  Original Android Development] arifqur:
Before you start fresh why don't you flash the Official TWRP and Multrom v32b and see if you still have the same problem
[Nexus 6  Original Android Development] Droidphilev:
Well, its fixed :)

To start with i dirty flashed my rom back and Elite afterwards. Normal booting time to secondary again. Thanks for the tip my friend!!!
[Nexus 6  Original Android Development] H4X0R46:
Anyone else having the issue with secondary ROMs not being able to mount the internal storage? File managers all say they couldn't mount. Also, play store crashes on all secondaries when trying to install an app. Probably because of the first issue in my post.
[Nexus 6  Original Android Development] Droidphilev:
Are you using the kernel that came with cm13? Thats probably the reason
[Nexus 6  Original Android Development] H4X0R46:
Yes I was. Although, I did try pac rom lollipop with elementalx kernel as well as cm 12.1 with elementalx. Same issue. All of them wouldn't show files in my data or let me install apps without force closing the play store.

Sent from my Nexus 6
[Nexus 6  Original Android Development] Droidphilev:
I guess because of using that cm13 kernel you are encrypted now. Have no other idea, sorry.
[Nexus 6  Original Android Development] arifqur:
Flash a permissive kernel, this is a read/write issue
[Nexus 6  Original Android Development] H4X0R46:
Damn, well alright thanks!

Sent from my Nexus 6
[Nexus 6  Original Android Development] H4X0R46:
Thanks so much! I'll try this! :D

Sent from my Nexus 6
[Nexus 6  Original Android Development] H4X0R46:
Also! Just wanted to add that I tried this and it worked perfectly! :D But why all of a sudden this new unofficial version of multirom needs this? The official version didn't have a problem with SE Linux. Thanks again dude! Glad it works at least!

EDIT: For 5.1 ROMs, do you know of a good custom kernel that lets you change SE Linux mode? Eementalx lets you for the Marshmallow version, but the Lollipop version of Elementalx does not give that option. My secondary ROMs that are lollipop are having the read/write issue and I'm not sure how to change SE Linux for lollipop.
[Nexus 6  Original Android Development] jcrompton:
The unofficial version was for some M ROMs having problems flashing as secondary. The unofficial were great help for those of us with problems
[Nexus 6  Original Android Development] H4X0R46:
It did work great for the M ROMs, but needed SE Linux changed, for me at least. It seems to have broken Lollipop ROMs because it too needs SE Linux changed, which for me, seems harder to figure out.
[Nexus 6  Original Android Development] arifqur:
Sorry don't have any Lollipop roms on my device. Have you tried using SELinux Mode changer app?
[Nexus 6  Original Android Development] H4X0R46:
I saw this mentioned in another thread and it sounded like a perfect solution! However, with this unofficial version of multirom, I can't even install apps onto a secondary ROM because the enforced SELinux doesn't even let me write to the userdata! I may just remove the lollipop ROMs and just wait for either multirom to be updated, or the custom ROMs to start using Marshmallow as a base! Thanks any way! Appreciate the reply! :D
[Nexus 6  Original Android Development] Droidphilev:
This has nothing to do with official or unofficial. AFAIK selinux is getting "better", that's all. And since it works fine for most there wont be updates for now. I use M as primary and L and M as secondary. No problems with writing.
[Nexus 6  Original Android Development] H4X0R46:
This is really weird! My secondary ROMs don't work right unless I have SELinux set to Permissive! Yours just works when set to Enforcing?

EDIT: The official version of multirom didn't give me this issue with lollipop roms, after switching to this unofficial build the issue arose.
[Nexus 6  Original Android Development] Droidphilev:
No idea. I never use enforcing kernels because of an XPosed module i use. Half of the M roms dont even work with an enforcing kernel anyway.
[Nexus 6  Original Android Development] H4X0R46:
I may just fastboot flash my phone back to 100% stock and try it all again to see if I get the same issue.
[Nexus 6  Original Android Development] Droidphilev:
Sure you will get this issue back.
[Nexus 6  Original Android Development] H4X0R46:
I'm leaning towards that too quite honestly, a last resort option really lol. I'm stumped here.
[Nexus 6  Original Android Development] H4X0R46:
Just confirming, did the restore to stock and then did it all over again, same result.
[Nexus 6  Original Android Development] Droidphilev:
Sure. BTW: whats the problem of using a permissive kernel?
[Nexus 6  Original Android Development] H4X0R46:
Well, since this update of multirom, all of my secondary roms can't read my data in file managers, can't access anything, which causes google play store to freeze and force close. I can only run the secondary rom without this issue if the secondary rom has a custom kernel with permissive. If you're asking why I can't just use a kernel with permissive for my secondaries, I literally cannot find a custom kernel that supports lollipop and is set to permissive by default. Because I cannot install apps on a secondary rom, it eliminates the solution of using the SELinux changer app. Sorry if I misunderstood your question, couldn't understand exactly what you were asking.
[Nexus 6  Original Android Development] Droidphilev:
You must be kidding! I answered your post in Q&A where you say you searched a whole day for a permissive LP kernel. I found one for you in half a minute.
[Nexus 6  Original Android Development] H4X0R46:
I JUST NOW saw your post there, never checked it again. Relax lol
[Nexus 6  Original Android Development] Droidphilev:
I'm probably nore relaxed that you are right now. mine works :)
[Nexus 6  Original Android Development] H4X0R46:
And? Good for you.
[Nexus 6  Original Android Development] Droidphilev:
And? Just always flash permissive kernels and it will work for you too.
[Nexus 6  Original Android Development] Gabbyii:
Installation question - so on the install when picking a kernel version - is this suppose to match the kernel version your primary is running (since there's no 6.x for marshmallow - I don't wanna brick and have to restore) - or is this kernel support for the secondaries?

Thanks
[Nexus 6  Original Android Development] carsenk:
Does anyone have the kexec-hardboot patch for the CM13 (Android 6.0) nightly kernal???
[Nexus 6  Original Android Development] daheazle:
If you are installing from the multirom app there is not an option for official MM, if your primary is indeed MM you will need to have custom kernel with kexec installed manually. The kernel installed as primary is the only one that matters as far as kexec goes and will not have any effect on your secondary roms.

CM would have to add that to their build, it is built into the kernel or someone take the CM kernel source and add it in before compiling, which doesnt seem to be worth the effort if that is all you are adding. The other option is a custom kernel that supports CM13
[Nexus 6  Original Android Development] daheazle:
Here is a solution.. Although you already found a kernel.

I made a flashable zip of the SELinux mode changer. Flash in TWRP and you are all set to switch to permissive.

SELinuxModeChanger.zip

I take no credit for the app, I simply made it flashable for this situation, all credit goes to [MENTION=4467676]MrBIMC[/MENTION] and if he objects I will remove it.
[Nexus 6  Original Android Development] H4X0R46:
Thanks so much! I'll hold onto this! Thanks again because this file is very helpful!
[Nexus 6  Original Android Development] daheazle:
No problem, but like I said all credit goes to MrBIMC. I simply made it flashable in TWRP.
[Nexus 6  Original Android Development] Droidphilev:
I think (so not sure) that this is too late. At least when it switches state everytime after boot. Is it the app with the green icon?

---------- Post added at 06:47 AM ---------- Previous post was at 06:38 AM ----------

There are plenty custom kernels here on xda. As long as the primary kernel you use is permissive and contains the patch there is no problem. Secondary kernels can be other (permissive) kernels. Make sure you don't flash the "official" multirom but the "unofficial" one i posted in this thread.
[Nexus 6  Original Android Development] daheazle:
Yes it does have a green icon. But I tested it on CM13 before posting it.

With CM13 on the stock kernel Root Explorer, or any other app can not see your sdcard do to the enforcing policy. The app does change the policy after boot, ideally a permissive kernel is the way to go since it is permissive during boot. For my purpose at least it was adequate. Now if you have an app that is looking to the sd before boot finishes you are still going to need a permissive kernel.
[Nexus 6  Original Android Development] Droidphilev:
Yes, that's what i mean. It's not the perfect solution. There are apps where this switch will be too late (some Xposed modules for example). Most of the M kernels are permissive anyway. I use Elite for both M and L roms.
[Nexus 6  Original Android Development] daheazle:
I agree 100% but there are circumstances where you'd like to keep the stock kernel to check functionality of things. Which is what inspired me to make the mode changer flashable.

Personally I don't care for enforcing mode at all, if you are installing custom roms, kernels or even rooting you should know enough to not install apps that are going to do harm. For the masses on a stock system I recognize its benefits, just don't feel like it has a place around here.
[Nexus 6  Original Android Development] Droidphilev:
True
[Nexus 6  Original Android Development] adl:
A quick question: I can't find any option to wipe system for the secondary ROM, only dalvic, cache and data. When I dirty flash a ROM I usually wipe system along with dalvic and cache, that's why I am asking. Wiping data I only use when I flash clean (which I don't do most of the time).
[Nexus 6  Original Android Development] deeplyyoung:
Swap the Rom with Primary, wipe system>dirty flash Rom> swap again.:o:good: