yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Yes, it's going to be fixed in the next release. It's an issue with the installation method, already fixed in AOSP of 19 June

Official TWRP doesn't have support to manage F2FS like convert or format a partition with this filesystem, that's why I build myself a version with F2FS. It has been updated to the v2.8.7.0, the MultiROM TWRP always has F2FS support, for this last updated to 2.8.7.0 we need some time, Tasssadar (creator of MultiROM) must update his special TWRP source :)

If you have /data (userdata) partition as F2FS the MultiROM will not work, hopefully I'll be able to build one specifically for this file system. Then two versions: one for ext4, one for F2FS (or one with both inside haha)

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] franzyroy:
If I summarize:

Official TWRP hasn't the support, even if that, I don't care. :) Not my question!;)

Your TWRP F2FS support the F2FS, of course, but not the MultiROM

MultiROM TWRP always support F2FS, but isn't updated because you're waiting Tassadar's sources.

Your latest MultiROM TWRP is built from the sources of June 15, so unofficially, it's a version 2.8.7.0 like at this date, the features of the 2.8.7.0 were already in the sources, don't you think? z31s1g also think that.

---------- Post added at 09:01 AM ---------- Previous post was at 08:59 AM ----------

In addition:

Official TWRP hasn't the support for F2FS but now can resize it, right?

---------- Post added at 09:03 AM ---------- Previous post was at 09:01 AM ----------

I say that, because there are 2 new buttons whose the "Resize FS" button.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Latest MultiROM TWRP is built on 15 June, but the last commit in that source has been done on the 2 June. Two days ago the 2.8.7.0 (not MultiROM one) has been released, so 19 days of commits are missing in MultiROM TWRP which must be updated by Tassadar.

See the normal TWRP and MultiROM TWRP as two different projects!

Useful links:

https://github.com/omnirom/android_bootable_recovery

https://github.com/Tasssadar/Team-Win-Recovery-Project

MultiROM TWRP 2.8.6.0 is 2.8.6.0, nothing more to say

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] franzyroy:
OK OK
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
After having found the way to build updated MultiROM TWRPs for this device, expect an update as soon as Tassadar updates sources :)
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Great!:good:

Only request for me, appoints it 2.8.7, as you made with yours 2.8.6, it's for my mod, it avoids to change my script!;)

Thanks!
[Galaxy S 4 i9505 Original Android Development] todivefor:
[MENTION=6762848]FNetV1[/MENTION] any luck getting sph-l720 to work? Last time I tried, I also had your problem, no cell service. I now run dualboot with TW-OD2 (http://xdaforums.com/galaxy-s4-sprint/general/rom-sph-l720-lollipop-od2-deodexed-t3108732) stock as primary, AtaresOne-opt as secodary (daily driver), and CM-jfltespr as a third for testing. When I have a chance, I want to try my OD2 with hulk kernel primary with MR.
[Galaxy S 4 i9505 Original Android Development] tasstass99:
[MENTION=5464206]AntaresOne[/MENTION]

1: Why cant i use/see sd card (external) on me secondary rom which is installed on the sd card (external) formatted as exFAT

2: Google Play Store FC when installed on internal memory will provide a logcat

Logcat: https://mega.nz/#!uJpWkJya!6geYqeI5WKF5U3UFlHxfDnTO2CmPseX7MIhrmjiA7RQ
[Galaxy S 4 i9505 Original Android Development] Rambooka:
I am new to MultiROM... I have been using DualBoot... MultiROM seems easier to use, so I thought I would give it a try... I have imperrium TW Rom as the primary ROM. I followed the guides for installing a secondary rom onto my 64GIG SDCard... install went ok for Ressurection Remix V5.4.6 I rebooted the phone the Samsung boot logo came up and then screen goes blank... phone vibrates and the phone reboots into recovery...

I manually installed the MultiROM's TWRP & zip file... due to the Play Store app not being able to download any files...

The boot menu seems to work well after i worked out the the touch screen is not used and all selections are done with the phone volume buttons... Maybe some one can update the OP with the fact that you use the hardware button to navigate the boot menu... I thought the menu had crashed !!!
[Galaxy S 4 i9505 Original Android Development] AmyClaraRose:
Touchscreen works fine I've used it with no problem
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Did you all install?

TWRP MultiROM (I saw that YES)

MultiROM zip file (I saw that YES - it seems)

Kernel with kexec-hardboot patch

For the N°3,: Is what your Rom have the Kernel with kexec-hardboot patch?
[Galaxy S 4 i9505 Original Android Development] benlm72:
It seems we are some users facing the same pb with touchscreen. For me I've TW5.0.1 natvie install (samsung rom), multirom boot injected via twrp, tried with AEL, Imperium and Hulk TW5.0.1 kernels : always the same, no touch screen. I wait for the new Multirom release, hoping it will fix this pb.
[Galaxy S 4 i9505 Original Android Development] AmyClaraRose:
Maybe it's touchwiz as primary from any custom non touchwiz from I used touchscreen works fine
[Galaxy S 4 i9505 Original Android Development] Rambooka:
I am running imperium rom. The kexec hard boot patch is supported by the kernel. The multirom app from play store says the kernel is patched
[Galaxy S 4 i9505 Original Android Development] franzyroy:
OK, so it's other thing.
[Galaxy S 4 i9505 Original Android Development] Rambooka:
My sdcard is 64gig and formatted as exFAT.... could this be the problem?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Nothing is written about of that!:p

Edit

:

Except your post, you've:

This

That

Edit2

:

I only mention this sentence on the 2 posts:
[Galaxy S 4 i9505 Original Android Development] benlm72:
Hi AntaresOne,

Do you have infos about the next release date ?

Thank's !
[Galaxy S 4 i9505 Original Android Development] smeroni68:
ETA??

The last update is of two weeks ago and you are asking when a new release will come out???

This is not a ROM!!!

Until it works with current ROMS, there is no need of an update...
[Galaxy S 4 i9505 Original Android Development] benlm72:
But we are a few having pbs with Multirom and 12.1 cm opt rom that prevents this rom to install without impact or even to install it, AntaresOne himself said he has identified the pb and that an update was soon coming. That was just my question.
[Galaxy S 4 i9505 Original Android Development] jwacher:
Great Work!

I have Optimized CM 12.1 installed and I love it. I stalled multirom because it looks awesome. However I am formatted to f2fs and the boot manager doesn't start up like someone said in a previous post. Is there anyway for me to convert my filesystem without formatting ( aka losing my stuff). Keep up the great work! I look forward to seeing the F2fs update. Thanks for all your work!
[Galaxy S 4 i9505 Original Android Development] Madalinsuny:
[MENTION=5464206]AntaresOne[/MENTION]

Same Here!

I'm using cm-12.1-20150702-NIGHTLY-jfltexx as secondary rom

Any Fix?
[Galaxy S 4 i9505 Original Android Development] 0kti:
+1 for cm 12.1 and pacrom. SD card works with resurrection rmx rom as secondary. Tested on my phone

Sended from my phone
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Did you already try to install the ROM in the internal memory instead of external?

Google apps FCs: flash another package

Optimized CM12.1: MultiROM compatibility must be really fixed this time in the build published right a little time ago, check its thread

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] Madalinsuny:
[MENTION=5464206]AntaresOne[/MENTION] Thanks for the replay

I'm downloading your latest build (optimized) and I will report back/
[Galaxy S 4 i9505 Original Android Development] Madalinsuny:
[MENTION=5464206]AntaresOne[/MENTION] Bad news..

After flash your rom as socond on internal sd, the primary rom (Albe95 S6 PORT 3.0) won't boot anymore.

I must give up of multirom :( I realy hoped to make a dual boot with you rom)
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Hm... Okay, let's see what bothers that. Sorry, please give me some time, I'll surely sort out this issue.

For now please do not flash Optimized CM as secondary ROM
[Galaxy S 4 i9505 Original Android Development] Pth Creations:
Primary ROM Wont Boot Up....

Hi Antares One,

I am Having MultiROM on my GT-I9505 Running Stock Touchwiz 5.0.1 Primary And CM12.1 Optmized Build 20150616 Secondary..

Was Running Fine....

Just a Few Minutes Ago I Downloaded The New Build 20150701 And Flashed It ..

Now When I Turn On My Phone And Boot In To Primary ROM he Screen Goes Black...

So I Rebooted and Booted In To CM12.1 Optmized Build 20150701,Workz Fine...

So Wat To Do Now??Need to Remove MulitROM and again flash Primary And Secondary CM12.1 Build 20150616??
[Galaxy S 4 i9505 Original Android Development] Madalinsuny:
Thanks. The same probleme i have with the previous optimized build. Realy hope you can fix it.

With the official CM it works,but no more internal/external SD.

Can this problem can by with the CM source?!
[Galaxy S 4 i9505 Original Android Development] benlm72:
Hi AntaresOne,

Same pb for me, the new cm12.1opt release doesn't solve the pb of primary tw no more booting after installing cm12.1. Hoping tou could fix this pb, fo now I goes on testing cm12.1opt as secondary rom.

Thank's for what you can do for us !
[Galaxy S 4 i9505 Original Android Development] eclpsues:
im getting corrupt file on the modified TWRP.

Already downloaded a few times. Stil the same result.

Any mirrors?
[Galaxy S 4 i9505 Original Android Development] 0zura:
Same fail here

Can't install and can't unpack latest modified TWRP
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Was an upload problem, fixed now

https://www.androidfilehost.com/?fid=23622183712473047

:)
[Galaxy S 4 i9505 Original Android Development] eclpsues:
Testing...

Thanks! Its working.
[Galaxy S 4 i9505 Original Android Development] 0zura:
What is swap rom?

I "google" it for hours but can't find anything. have anyone an explenation?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Under Linux, we talk very often Swap partition Swap, see what Swap. This physical memory is often installed under Linux as a separate partition, part of the hard drive is reserved for the virtual memory system that will alleviate the overload. Less useful nowadays with newer motherboards, it is nevertheless inevitable.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
[MENTION=5199431]0zura[/MENTION]

On MultiROM, "swap ROM" feature switch the primary ROM with any user-choice secondary ROM
[Galaxy S 4 i9505 Original Android Development] arcane spade:
Verizon?

anybody know if this works on the vzw variant of the S4? Jflte Rom's are unified but I have no idea if the recovery is different or not.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
I haven't yet added support for vzw and att, but you can first flash the loki patch then flash recovery zip, to install MultiROM the same, first loki then mrom zip

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] 0zura:
Another "nooby" question

Can we share installed apps over second and third rom or we have to install each app twice?
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
By default, original MultiROM can't. I'm working in my free time to implement this feature :)

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] arcane spade:
I flashed loki then tried to flash multirom but it failed. I didn't try flashing twrp mod. Any ideas why multirom wouldn't work or should I just wait until you add support for vzw?
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Hmm.. I think that MultiROM can't unpack and repack boot.img on device with locked bootloader. Will try to do something, but I need someone that can test for me

EDIT: What the error says?

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] cantenna:
You could just install link2sd from market and create a 10gig partition ext4 on external sd move all apps to ext4 and relink in options of link2sd within each newly installed ROM. I'd also use foldermount and backup and restore setting amongst ROMs.

I just installed multirom on xperia tab z, awesome app! Thought I'd check it out oh GS4,but I'm using Danvdh ROM as base and want to keep using his kernel. Any chance you can patch?

Thanks man for porting, awesome app!
[Galaxy S 4 i9505 Original Android Development] arcane spade:
Sorry, didn't see your reply until now. I repeated and got same error, see below.

Installing '/sdcard/Download/multirom-20140906-v28-UNOFFICIAL-jflte.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/Download/multirom-20140906-v28-UNOFFICIAL-jflte.zip.md5
Skipping MD5 check: no MD5 file found.
Warning: No file_contextsscript aborted: This package is for 'jflte,jfltexx,i9505,GT-I9505,jgedlte,i9505g,GT-I9505G,jfltespr,jflterefreshspr,jfltetmo,jfltecri,jfltecsp,jfltecan,jflteusc,jfltezm' devices; this is a 'jfltevzw'.
This package is for 'jflte,jfltexx,i9505,GT-I9505,jgedlte,i9505g,GT-I9505G,jfltespr,jflterefreshspr,jfltetmo,jfltecri,jfltecsp,jfltecan,jflteusc,jfltezm' devices; this is a 'jfltevzw'.
E:Error executing updater binary in zip '/sdcard/Download/multirom-20140906-v28-UNOFFICIAL-jflte.zip'
Error flashing zip '/sdcard/Download/multirom-20140906-v28-UNOFFICIAL-jflte.zip'
Updating partition details...
I:Data backup size is 3158MB, size: 9948MB, used: 6699MB, free: 2925MB, in data/media: 3540MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /data/media/0/recovery.log
Copied recovery log to /data/media/0.
I:Set page: 'action_complete'
I:Set page: 'clear_vars'
I:Set page: 'advanced'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'reboot'
I:Set page: 'rebootcheck'
I:Switching packages (TWRP)
I:Set page: 'fixsu'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
[MENTION=4675887]arcane spade[/MENTION]

As you can check in META-INF/com/google/android/updater-script, the assert.getprop is disabled for jflteatt/jfltevzw since they have locked bootloader

I thought that flashing loki patch can give write access to MultiROM, but due the way how MultiROM works it's hard to give support to bootloader locked device.

We can try something btw, download Alucard kernel according to your primary ROM, flash it so the loki patch (integrated with Alucard's flashable ZIP) can modify boot.img, then boot in Android and run this in Terminal Emulator:

su (to give superuser access)
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/bootvzw.img (this command on a single line)

Zip that new file, upload on any file sharing site and send me link.

I need it to see what differences are inside normal bootimage and one loki-patched to build a MultiROM-compatible bootimage for verizon and at&t variants

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] arcane spade:
Thanks. I've actually been running Alucard's kernel. I PM'd you the boot image.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
I still don't have any PM...:rolleyes:
[Galaxy S 4 i9505 Original Android Development] arcane spade:
not showing in my sent either, I tried again and ... idk

https://www.dropbox.com/s/m0d9l9wff68ma07/bootvzw.zip?dl=0
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Now I got the PM too :silly: I'll take a look inside boot right now
[Galaxy S 4 i9505 Original Android Development] XakFak:
So i want to try CM bulds. Primary rom is Albe S6 Port 3.0 Which bulds i can install as secondary?
[Galaxy S 4 i9505 Original Android Development] Madalinsuny:
Do you have internal/external sd on secondary rom?

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

I try official CM and no internal/external sd...with optimized cm i cant boot on albe95 rom....with go edition i stuck on installing go rim but albe95 continued to work.....conclucion: i did'd find any rom to flash as secondary and work perfectly with Albe95 s6 v3 rom..
[Galaxy S 4 i9505 Original Android Development] BillSwaginGates:
Working almost perfectly on my phone, although with 2 small issues. First, if I have TW installed as primary and a cm12.1-based rom as secondary, when I boot into the rom selection screen touch seems to be disabled and i am forced to use volume keys and power button to navigate. Possible fix for this??? Second, when I take out the battery or the battery dies, when booting back up it automatically boots into recovery instead of into multirom, which isn't much of a problem, just a little annoying. Other than that, working perfect on my i9505 (Albe95 S6 Port 2.0 as primary, Fusion 6.0 as secondary) :D
[Galaxy S 4 i9505 Original Android Development] benlm72:
Yes, I have internal/external sd on the secondary rom, that I have installed on external sd in an ext4 partition. No more pb with the ext4 sd (I had previoulsy post about my partition seeming to be too small, that is no more the case).

EDIT : but I have noticed that my external sd card is no more named extSdCard but sdcard1.
[Galaxy S 4 i9505 Original Android Development] bongster:
Hi, I have cm optimized as primary ROM, data and cache formatted with f2fs. Can I use multirom with that combination on a vfat sdcard?

Thanks
[Galaxy S 4 i9505 Original Android Development] Madalinsuny:
I have hadthe second rom instead on internal sd and when I used the second rom, I have no internal/external sd
[Galaxy S 4 i9505 Original Android Development] Rambooka:
Hi... I reinstalled everything from scratch using imperrium rom. .. but still rims on external sd card reboot into recovery... here is the multiform log.... hopefully someone can see a problem and help me fix problem https://mega.nz/#!UZtwBQLR!AotQLUluHwxzmEn9gT3TUKaoJSJf06LUn6lWdfSKWoA
[Galaxy S 4 i9505 Original Android Development] Xenotrumpet:
The problem is that flashing CM12.1OPT as secondary wipes primary /system.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Or remove this in the updater-script file

run_program("/tmp/install/bin/format.sh");
[Galaxy S 4 i9505 Original Android Development] Marco_nx:
Does this problem also occur with Slim Optimized?
[Galaxy S 4 i9505 Original Android Development] Madalinsuny:
Thanks!

Can you confirm that after install optimized or unopt build on internat as secondary we have internal and external sd?!
[Galaxy S 4 i9505 Original Android Development] franzyroy:
No, I can't, I didn't install it like secondary, I only give a suggestion to avoid the crushing of your primary rom.
[Galaxy S 4 i9505 Original Android Development] benlm72:
I can't test for now, so do you think restoring /system with TWRP previous backup will restore the primary rom without delete secondary rom ?
[Galaxy S 4 i9505 Original Android Development] stanguay:
yes
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
That's to correctly install the ROM without wiping /system, a temporary fix for MultiROM users.

The real and permanent fix must be done in the format.sh in Optimized ROM itself

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] franzyroy:
In waiting, maybe they can make a wipe system via the MultiROM recovery, I don't know, I propose it because I haven't still installed several roms with your awesome TWRP.
[Galaxy S 4 i9505 Original Android Development] bongster:
Hi again,

fyi. I was not able to use multirom with data and cache formatted with f2fs. After migrating back to ext4 it works now!

Thanks for your incredible work!
[Galaxy S 4 i9505 Original Android Development] Rambooka:
Did you install roms onto internal or external memory
[Galaxy S 4 i9505 Original Android Development] bongster:
I tried both but after my last post I found also this post:

http://xdaforums.com/showthread.php?p=61496740

So I guess for now it really works only with a ext4 data partition.
[Galaxy S 4 i9505 Original Android Development] junkyarddog:
Ciao AntaresOne,

Like some other users, I have same problem: touch doesn't work @ boot, I have to use vol/power button to select the ROM.

Manual install worked without a problem following your guide.

Model: GT-i9505 (jftlexx)

Status before install:

ROM: Stock Lollipop 5.0.1 rooted (with a little "deodexing")

Recovery: TWRP 2.8.2.0

Follows what I've done:

- Copied 3 files needed Modded TWRP & Kernel patched (downloaded from liks provided in 3rd post) and CM12.1 Nightly build on SDCard (Samsung EVO 32Gb exFAT formatted)

- Booted in recovery

- Installed "Imperium" kernel

- Wiped cache & Dalvik

- Rebooted (about 10 mins of optimization)

- Tested about 1h (to be sure that all was working fine)

- Rebooted again in recovery

- Installed MultiROM TWRP

- Rebooted again in "new" recovery

- Installed CM12.1 as 2nd ROM in external SDCard after setting appropriate cache, data and system's size

- crossed fingers

- Rebooted again.

- After few seconds, the Selection ROM Menu correctly popped up, but without touch support :(

Status after installation:

"internal" ROM (default): Stock Lollipop 5.0.1 rooted (with a little "deodexing") and, of course, new "Imperium" kernel

"external" ROM (on SDCard): CM12.1 Nightly Build (17/04/2015)

The autoboot countdown is stopped only pressing vol button. No touch support inside the multirom menus.

Both ROMs work fine

Jyd
[Galaxy S 4 i9505 Original Android Development] benlm72:
Tested indeed, it's OK.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Ciao Jyd,

There's only one reason:

MultiROM parts need to grep touch screen driver from kernel when building. Since TouchWiz and AOSP/CM ROMs have very different kernel source (there are also many changes in drivers) if you use a TouchWiz ROM as primary the touch screen will not work in MultiROM boot screen because I build this with CM kernel.

But now that many users reported this issue I'll probably start to release two versions of the main zip (one built on CM kernel, the other on TouchWiz), all packed in an user-friendly Aroma package:

Start zip installation

Choose type of current primary ROM

End installation

For everyone: yes, as stated by me please use MultiROM only if you are on ext4 because it doesn't currently support F2FS

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] Rambooka:
If I am still on an old kitkat bootloader... Will multi boot work or do I need a lollipop boot loader ?
[Galaxy S 4 i9505 Original Android Development] Xenotrumpet:
Kitkat bootloader works just fine.

---------- Post added at 12:49 AM ---------- Previous post was at 12:47 AM ----------

Did you get a maelstrom of FCs upon booting up to primary after restoring /system?
[Galaxy S 4 i9505 Original Android Development] benlm72:
No, it works fine. I've not tested a long time because I went back to the secondary rom, but no FC at boot.
[Galaxy S 4 i9505 Original Android Development] BillSwaginGates:
Any estimate as to when the new installer zip with TouchWiz kernel will be out? Having the same problem as Junkyarddog with no touch and the keypress autoboot works kinda funny for me. Thanks!