yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] niv3d:
How did you get it to work?
[Nexus 5 Original Android Development] stani2103:
Install Miui like primary and after swap it or do backup and rstore it like secondary

http://en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=25194&pid=490945
[Nexus 5 Original Android Development] niv3d:
OK great in may give that a shot. How often do you actually run miui though? Is it worth it to try it out? Lol
[Nexus 5 Original Android Development] gordo1701e:
Great Work!!

I just wanted to leave a note for the op. this is phenominal!! I'm just set it up with android 4.4.4 and ubuntu last night and this couldn't be any easier if the dev tried! thanks again and keep it up!!
[Nexus 5 Original Android Development] stani2103:
Runs smoothly and....well ,its MIUI ,elegant ,custom,..........I use it 3-4 days a week and update every Friday -dirty flash without problems:laugh:
[Nexus 5 Original Android Development] stone_ship:
I have never been able to swap ROMs, I get this error:

Copying /system...
E:failed to lsetxattr selinux on /data/media/0/multirom/roms/KTU84P//system/ .pin: 2 (No such file or directory)
Failed, removing incomplete ROM...

KTU84P is what I'm calling my internal ROM. Trying to swap with Mahdi in secondary.

As a workaround, I can make a full nandroid and restore as a new ROM.

XPosed uninstalled, busybox OK...not sure what else I can try.
[Nexus 5 Original Android Development] Andypandiiee:
Is there a way to backup a secondary ROM? and how do you restore it?
[Nexus 5 Original Android Development] z31s1g:
To backup:

Advanced > multirom > list roms > *select rom* > backup (works only if the kernel isn't shared with primary rom)

To restore:

Advanced > multirom > add rom > from backup >...
[Nexus 5 Original Android Development] dndwanted:
So I am getting this error trying to swap primary with secondary

Please help :)
[Nexus 5 Original Android Development] Wombatino:
That seems that the zip file is corrupt or is not good.
[Nexus 5 Original Android Development] dndwanted:
What does that mean? I have primary rom Stock 4.4.4 and secondary rom latest version of Paranoid Android.

What zip file?
[Nexus 5 Original Android Development] worhello:
Try swapping them manually.

What I mean is:

0) Make Nandroid backups of both ROMs

1) Restore the backup of the secondary ROM as the primary ROM

2) Restore the backup of the primary ROM as the secondary ROM

3) Make sure that whatever kernel you use with the Primary ROM has the kexec patch
[Nexus 5 Original Android Development] NaRiNe:
MultiRom on ParanoidA

i'm not getting to multirom to work on PA 4.5 Alpha :/ it was working on 4.41
[Nexus 5 Original Android Development] :
weird thing...

@Tasssadar

Hi

I m MultiRom User on CM11-Nightly 0719

also it is My Default ROM is CM11 with auto-boot to this.

But my phone Rebooted to Internal Rom (rooted stock android) without any permission and ...!

when i reboot again to CM11 the widgets on home pages were blank!

the last thing i have installed was This App

What can be cause of this? (Phone with MultiRom reboot to another Rom)

Thanks

:good:
[Nexus 5 Original Android Development] limzm:
For those who are stuck at Google logo while booting AndroidL, can you please try flashing the attached zip file?

This SELinux stuff is really really troublesome.

I believe for most people after flashing this, you will get be able to boot your Android L. However, you will be getting Force Closes all over.

And I also believe I found a tedious way to fix this problem.

All these problems are coming from recovery's SELinux which restores to only KitKat. So, restoring the Android L from backup uses the KitKat's SELinux rather than Android L, thus

causing permission errors all over.
[Nexus 5 Original Android Development] Alfonso87:
Hello, i'm in trouble.

It's from yesterday that my secondary rom (Android L) don't let me save anything. I can't access the "fake" (emulated) storage at all. This started when i wiped my primary rom. I tried to delete the secondary and re-flash it, but nothing changed...any idea? O.o
[Nexus 5 Original Android Development] :
Just flash a new primary ROM....with a compatible kernel for multirom. Go into it, install multirom app and you should be good again. ?
[Nexus 5 Original Android Development] Alfonso87:
Umh i have a stock 4.4.4 rom as primary...would be the same if i just swap it with the secondary rom, or would be better to wipe it and flash a different rom?
[Nexus 5 Original Android Development] :
I can't speak on L....used it for 30 minutes and then wiped it. Lol

Can you get into your current primary? Is multirom app installed and saying you're good?

I'd so, primary is fine and the issue is with L. Not sure what to say about that, other than wipe it and try again. :)
[Nexus 5 Original Android Development] Alfonso87:
Yep for sure issue is with L. Primary rom is fine, and i have just flashed CM as secondary (after have deleted L) and it works fine. Umh i think i will give it an other try. It's just boring have to wait that long every firstboot lol
[Nexus 5 Original Android Development] Tzfardaya:
I use 4.4.4 stock as the primary with L as a secondary, no issues on my device with that set up (I use franciscofranco's kernel on 4.4.4)
[Nexus 5 Original Android Development] limzm:
[MENTION=3418703]Tasssadar[/MENTION]
[MENTION=4544860]osm0sis[/MENTION]

I realised that the SELinux context used in /data/media/0/multirom is different for the ROM's /system and /data when it comes to Android L.

I did a clean flash on my primary ROM which is SlimKat and then the sdcard permission issue got to me on Android L. Then suddenly on the second start it refused to boot, getting stuck on the Google logo.

So I extracted the script from the flashable Android L ROM which contains the set_metadata commands and I flashed it, allowing me to get past the Google logo and into the system. However, I am getting FCs from every core apps which includes android.process.acore, gapps, Google Play Services and Google Dialer.

Then I did a restorecon -R /data/media/0/multirom/roms/AndroidL/data in TWRP and it gets stuck on the boot animation.

Thing is, what is the exact problem that is causing the FCs? Is it the permission or the SELinux context?

I figured the /system partition requires KitKat SELinux to boot while the /data partition requires Android L SELinux, but I just couldn't figure out the FCs.

I could wipe /data to restart my Android L setup all over but I really want to solve this without doing so.
[Nexus 5 Original Android Development] jsgraphicart:
It seems like everyone is using Android L as their secondary ROM. Is it possible to use Android L as the primary and a 4.4.4 ROM as a secondary? If so, is anyone doing it that way and are there issues?
[Nexus 5 Original Android Development] :
Only if there's a compatible kernel for it for multirom. Not sure if there is.
[Nexus 5 Original Android Development] jsgraphicart:
Good point. I think I'll just hold off. lol
[Nexus 5 Original Android Development] limzm:
Code Blue kernel has kexec support or you can use the stock kernel which was patched by Tasssadar in the second post if you want to use Android L as primary.

UPDATE on my findings: ok, I guess those FCs are due to PERMISSION problem in /data itself. Restoring SELinux allows it to boot up but permission causes the system to be unusable..

Classic problem I guess, and I have no idea how to set the permission on /data using Android L's parameters.
[Nexus 5 Original Android Development] Gustave17:
Faux kernel for Android L has the patch. He also post a notice for the FC's and SELinux.

Look in his thread...

Not sure if it could help...

Envoyé depuis mon Nexus 5

AOKPK & Faux123
[Nexus 5 Original Android Development] Alfonso87:
deleted
[Nexus 5 Original Android Development] edrickmph:
I got an error while installing android L as secondary with slimkat as primary.

"Failure to extract from archive"

"Failed to update from zip".

Anyone who could help? I search already but none came out.

Thanks in advance.
[Nexus 5 Original Android Development] Tzfardaya:
Redownload the zip and try again..
[Nexus 5 Original Android Development] edrickmph:
The L zip or the multirom zip?
[Nexus 5 Original Android Development] Tzfardaya:
The L zip.. That's the one that wouldn't install....
[Nexus 5 Original Android Development] edrickmph:
Ok. Ill try and keep you posted again.

Thank you.
[Nexus 5 Original Android Development] Tasssadar:
Since the release of Android L preview and creation of Miri the hydra, I was working on a redesign of MultiROM's boot manager to something that looks a bit more...from this century. It is almost finished, I just need to test it as much as possible. I'm still open to suggestions about the design though, so if you have some idea, speak up!

If you can, please flash it, test it and report back bugs, crashes and stuff like that. Thanks!

How to test it:

1. Using the MultiROM Manager app

Open the app, go to settings and tap the version seven times.

The developer options should show up.

Click the "Manifest URL" option

Change it to http://tasemnice.eu/multirom-test/manifest.json (just add -test, yes).

Go back to main screen and refresh. You should now see an update to MultiROM v26o - current testing version with the new GUI.

This way, the app will notify you of future testing version. Once the testing is over, you'll have to change the manifest URL back though.

2. Manualy flashing the ZIP

Download the appropriate ZIP file from this folder: http://tasemnice.eu/multirom-test/

Flash it in recovery
[Nexus 5 Original Android Development] Goggle81:
Looking good!
[Nexus 5 Original Android Development] Citizen_Snips:
Does pong still work? :p

Downloading now! :)
[Nexus 5 Original Android Development] mekayzer:
No problem yet
[Nexus 5 Original Android Development] eng.stk:
Very nice mate looking boot mate!

About MultiROM: did yous guys manage to fix the restore breaking L-preview?

If I restore L-preview backup on secondary it doesn't boot
[Nexus 5 Original Android Development] Gustave17:
Just flashed and it's OK for me...

Solve a bug with last Faux kernel:

Before, I had to disable Multirom on boot otherwise the phone didn't boot.

I can't choose Rom on boot just with the app!

Now it's all a good!

Thanks for the good work

Envoyé depuis mon Nexus 5

AOKPK & Faux123

---------- Post added at 09:17 AM ---------- Previous post was at 08:41 AM ----------

I had never seen the game in boot menu before today... :eek:

Don't know if it is new... But it is funny!! :thumbup:

Envoyé depuis mon Nexus 5

AOKPK & Faux123
[Nexus 5 Original Android Development] Tylog:
Great update and great job, thanks again for your great work [emoji106]

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] limzm:
You can try flashing my zip file onto Android L itself a few posts before.

I was able to get past the Google logo with it, but I reported FCs when booted into the system.

No one seems to have tested it yet so please do :).
[Nexus 5 Original Android Development] eng.stk:
Yes I used it and got same FC's you mention. So not really a solution, but thanks for the effort :good:
[Nexus 5 Original Android Development] limzm:
That's the problem right there. Because the /data partition has been affected with the older SELinux file context and permissions, it ceases to work on Android L.

I am not even sure how to restore it file by file so I guess I ran out of ideas to fix.

I believe TWRP or any recovery would need an update to fully support the new SELinux.
[Nexus 5 Original Android Development] SynnyG:
It's a dream or it's the reality ? It look so good ! I'm very very impressed ! Thanks for the work you do Tasssadar, as always you're awesome !

I've just two remarks:

- The animations of the boot "popup" is laggy just for the 2-3 first boot, after that, all is very smooth

- Same for the reboot option, It take me maybe 30secs to reboot after I've pressed the "reboot" option the 2 first times.

I don't know if it can be improved but I just wanted to tell you my experience ;)

Also, the "tap another time to boot system" is a really good idea, it prevent the wrong rom to be booted :)

I really love the flat style and card UI, I'm in heaven now :D I think from now i will reboot maybe 100 times a day to see the new boot screen :D
[Nexus 5 Original Android Development] samajid:
Hey...

How do i flash the code blue kernel ..ive got L running as my secondary rom...tried flashing it as a zip thru the modified recoverys multirom menu but it got stuck at google during boot.
[Nexus 5 Original Android Development] nadiros:
Multirom - List Roms - (pick the ROM) - Flash zip.

If you just flash the kernel without going through the " List ROMs" menu then you are just adding another boot without a ROM to boot into. This is the non technical explanation, and someone CMIIW please [emoji6]

Also be sure you have the Code Blue L version which at the moment is 1066 I believe. Cheers
[Nexus 5 Original Android Development] samajid:
I did go through the list roms menu ... Still got stuck.. Might b a faulty download. Will try again n post.. Btw latest code blue is 224
[Nexus 5 Original Android Development] nadiros:
Well that's your problem. If you want Code Blue for L then you require his L kernel. 224 is KK only. Am I missunderstanding what you are trying to do?
[Nexus 5 Original Android Development] samajid:
[/QUOTE]

Massive noob moment there! Thanks ...successfully flashed the right one. ?
[Nexus 5 Original Android Development] yoyoz808:
I'm having some trouble here. I am trying to boot into my secondary rom and just flashed francos latest r58 kernel. Now i can't boot into the rom. He mentioned some ramdisk changes and wondering if that would have anything to do with my problem?
[Nexus 5 Original Android Development] Tzfardaya:
Flashed Franco to the internal? . Isn't there a caveat on multi that if you flash anything to the boot partition it kills multi? Open your multi app and see I'd all. Needed parts are still avail, if not, reinstall them....
[Nexus 5 Original Android Development] AGiLiT:
Had the same problem on two different ROMS (Slim and PA); reported it in Franco's thread.

What I (and I presume yoyoz808) are saying is that when you flash the r58 zip onto a secondary ROM, it bootloops when you try to restart the system. I flashed r58.img onto my (stock) internal ROM with no problem. I think what you are referring to is when you flash an image to internal, you have to inject the boot sector to get the boot screen that allows you to choose which ROM to load. I think we're both getting past that; when the ROM starts, it just spins its wheels and doesn't boot.

EDIT: As I said in Franco's thread, I could flash r58 to internal and could go back to r57 on secondaries and everything works fine.
[Nexus 5 Original Android Development] Tzfardaya:
Fair enough, I've been dealing with too many people lately who have a hard time grasping the concept of an "on/off switch" and I think it might be spilling into my perceptions on xda issues... :( sorry...
[Nexus 5 Original Android Development] AGiLiT:
No prob; know you were trying (in your own inimitable style :D ) to be helpful.
[Nexus 5 Original Android Development] yoyoz808:
Yes exactly what i am taking about. I flash the kernel on a secondary rom it internal. Glad to see I'm not the only one with this issue. I'm sure it'll get worked out.
[Nexus 5 Original Android Development] Xami:
Anyone multibooting L and Nexsense ?
[Nexus 5 Original Android Development] AGiLiT:
I hope so. So far, we're being ignored in Franco's thread. :(
[Nexus 5 Original Android Development] davy917:
I have Android L running well as secondary, but the sdcard folders are all empty? Is this supposed to be that way?

Also anytime I try to download a file it fails, and I can't transfer files from my comp either. Is there something I'm missing?
[Nexus 5 Original Android Development] yogosun:
I had the same problem. What you have to do is the following:

1. Install terminal from play store in Android L ROM.

2. In terminal: "su" *enter*

3. In terminal: "restorecon -FR /data/media/0" *enter*

4. Wait.

5. Reboot.

*If it doesn't boot anymore, delete Android L as ROM, and flash it again trough multirom.

**No data will be lost, but make a backup just in case

This worked for me, good luck!
[Nexus 5 Original Android Development] yoyoz808:
Not getting any luck on either thread huh? lol
[Nexus 5 Original Android Development] davy917:
Thanks I'll give this a go
[Nexus 5 Original Android Development] AGiLiT:
Sorry to be showing up at the dance so late; it's been a busy week.

Looks very good! I like the option to change colors. The only thing I could find is that it seems to be a little dark (or dim); don't know what it's choosing as the light level, but I think it could be bumped up a bit.
[Nexus 5 Original Android Development] payas0:
trying to flash Ubuntu Touch. which channel is better ? or should i ask, what is difference between devel and devel-proposed ? tried searching, just can't find an answer ..

EDIT:

found the answer on the MultiROM App. haha. thanks!
[Nexus 5 Original Android Development] goodburner:
Can I use two different kernels for the ROMS? Like I'm using PA on one and CM 11S on the other. Elemental-X for PA and Elemental-X CM Version for the CM Rom?
[Nexus 5 Original Android Development] Spectrum75:
Yes ! ( check for primary kernel, must have kexec patch )
[Nexus 5 Original Android Development] Alexandroid99:
What does this command do?

I got these errors every time I used either L as a secondary or KK as secondary.

And why do I encounter this problem? I'm curious about how I can prevent it in the first place. :laugh:
[Nexus 5 Original Android Development] yashade2001:
Hi [MENTION=3418703]Tasssadar[/MENTION] i saw "redesign" branch in github. is that material-designed multirom? which you shared in g+? can i compile that branch for nexus 5? only design is changed, codes are still same, right?

thank you
[Nexus 5 Original Android Development] dexuus:
Try this :) :
[Nexus 5 Original Android Development] z31s1g:
[MENTION=3418703]Tasssadar[/MENTION]

multirom v26p & 2014-08-03 recovery

While looking into the changes you made to the recovery ui, I found that changing any setting (e.g. animation duration) also resets the color of the multirom boot menu to default. Bug or feature?

EDIT

Also, do you plan to implement the "track backup progress" and the "color in console" commits?
[Nexus 5 Original Android Development] Tasssadar:
New testing version 26p was released (if you don't know what is this about, read http://xdaforums.com/showpost.php?p=54416517&postcount=1523).

Changes since 26o:

slight changes to fonts in dialogs, namely ROM name in autoboot dialog

change dialog's drop shadow from opaque color to 70% transparent black color, looks better

add hover effect to dialog buttons

animation duration is now changeable from recovery

New recovery was also released on testing channel, 2014-08-04:

show secondary ROM's name in the header while executing its updater script (like, when using OTA in omnirom and such).

some backports from Ubuntu Touch recovery

fix failure to swap ROMs if they contain filename starting with a dot

fix installation of Android L preview as secondary ROM from a backup

add MultiROM options from 26o and 26p testing versions

EDIT: Changes in testing version v26q:

Fix some race conditions (-> crashes)

If you encounter any crashes (it suddenly boots internal ROM even if you wanted other ROM and/or didn't want to boot anything at all), please report them, even if you can't reproduce it.

Bug, it is fixed now. I usually only merge with upstream when new TWRP version is released. So yes, I will implement those when 2.7.2/2.7.3 (they may skip 2.7.2) comes out, unless you have some reason to merge them sooner.
[Nexus 5 Original Android Development] z31s1g:
No mate, no reasons. I just found out that including the required changes into the theme already doesn't break anything, so I'm good.

Thanks for the heads up (and the updated versions obviously...).
[Nexus 5 Original Android Development] eng.stk:
Golden ;)
[Nexus 5 Original Android Development] AGiLiT:
It didn't generate much discussion in Franco's thread, so to follow up on something a couple of us reported in this thread as well:

It appears you can't use Franco's kernel starting at r58 with a secondary ROM in MultiROM; it won't boot. R.57 and other recents work fine. This was reported to be true with Stock, PA, Slim and Omni. One user reported success with Carbon. You can search in Franco's thread if you're interested in the details.

If you can't live without Franco.Kernel, I've figured out a work-around. Since there is no problem installing r58 into the internal ROM, you can install a secondary ROM and have it share the kernel with the internal ROM. For any ROMS already installed, you can just use the option to remove boot.img.

The only drawback that I can think of to this so far is you won't be able to make nandroid backups of the secondary ROMS from MultiROM.
[Nexus 5 Original Android Development] Tasssadar:
Should be fixed in testing version v26r. You can get it using MultiROM Manager as described here or just download the ZIP from this folder and flash it: http://tasemnice.eu/multirom-test/

I may have broken the whole swap feature in test recovery 20140804. I've just uploaded version 20140804-01 which _really_ fixes it.
[Nexus 5 Original Android Development] gpvecchi:
Nooooooooooo!!!!!!!!!! I deleted my L backup on saturday!
[Nexus 5 Original Android Development] gravedigger76:
Please ignore me. Just blind here v
[Nexus 5 Original Android Development] Goggle81:
Didn't ignore you ;)
[Nexus 5 Original Android Development] Tzfardaya:
Ignore who?
[Nexus 5 Original Android Development] AGiLiT:
Excellent! I tested and it's working. Thank you! :)
[Nexus 5 Original Android Development] ast00:
Problem: Flashing any ROM as secondary results in it not booting. After selecting it, I get the Google logo, black screen and it reboots in 10 seconds.

I have over 2 gigs of space left, this all worked fine for a month before. And it happens with any zip I flash.

But any ROMs I flashed before yesterday work fine. So... WUT?

Bonus: Tapatalk crashes of I want to upload log, so I only have a Mega link. Sorry.

https://mega.co.nz/#!6c0yTQLD!pN-iaXO7oYcKEtGcq2fDDUJEg7-GpBA-qA-EC1q8tO0

EDIT: And now I got recovery not installed, failed to download info about updates. And I do have internet.

Tapatalk-kal küldve az én Nexus 5-el
[Nexus 5 Original Android Development] eng.stk:
I flashed L-preview Vomer's zip on secondary and ROM works fine, but no sdcard access (tried a couple of times always clean flashing).

Did you changed anything regarding partition mount on L ROMs with v26r?

Edit: On regular v26 it was working.
[Nexus 5 Original Android Development] yoyoz808:
+1 on sdcard issue. I had to use across terminal and type "restorecon -FR /data/media/0"

It worked sometimes but the last test caused the app fc's when i did that...

Edit: don't recommend using command as mentioned by [MENTION=3418703]Tasssadar[/MENTION].
[Nexus 5 Original Android Development] Tasssadar:
Don't do any of that restorecon mess and get me dmesg from that ROMs boot - reboot into it (even if you are already booted in it), check that you still can't access the /sdcard, and then do this in adb shell:

su
cat /init.hammerhead.rc > /data/local/tmp/mrom_log.txt
dmesg >> /data/local/tmp/mrom_log.txt
ls -lZ /data/ >> /data/local/tmp/mrom_log.txt
ls -lZ /data/media/ >> /data/local/tmp/mrom_log.txt
ls -lZ /data/media/0/ >> /data/local/tmp/mrom_log.txt
chmod 777 /data/local/tmp/mrom_log.txt

Then, exit the adb shell and pull the log file:

adb pull /data/local/tmp/mrom_log.txt

Upload that log file somewhere for me to see please.

That's all great and stuff, except it breaks MultiROM. Restorecon must not descend into /data/media/0/multirom, because when it does, it sets wrong contexts for all secondary ROMs.
[Nexus 5 Original Android Development] eng.stk:
Sure mate, here: https://dl.dropboxusercontent.com/u/12479179/log.txt