yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] nds850:
I'm not sure I understand how you mean. I completely shut the phone off and wait for the RAM to reset. I then start the phone and in the MultiROM menu choose the ROM I want to use. The phone restarts and load to recovery. Does the RAM need to be cleared after choosing the ROM? If that is the case how do I do that? :)
[Galaxy S 4 i9505 Original Android Development] BakaB:
sorry for the dumb question but didn't see answer anywhere.

does multirom work for i337m / jfltecan?

:confused:
[Galaxy S 4 i9505 Original Android Development] bdog2015:
I would assume so. It should work on all jflte's. It works fine on my jflteusc.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
[MENTION=1358557]BakaB[/MENTION] [MENTION=5740438]bdog2015[/MENTION]

Yes, it works on all jflte devices.

I337, I545, L720, M919, R970, I9505, I9507, I9508

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] davidwilson83:
I have been trying to flash the MultiROM zip through TWRP Recovery and I keep getting the following errors:

assert failed: getprop("ro.product.device") == " jflte" | | getprop("ro.build.product") == " jflte "

But what's weird is that both the lines that script is looking for (ro.product.device & ro.build.product) both say jflte in my build.prop so I'm very confused. I'm running Alliance ROM v2.0 I9505XXUGNG2 with stock permissive kernel and TWRP 2.7.1.0

Any help/advice would be appreciated.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
[MENTION=4603975]daveyannihilation[/MENTION]

What model number has your device?

Thanks for reporting, new build tomorrow with fixed assert for all jflte devices.

For now, open MultiROM zip through WinRAR, go under META-INF/com/google/android and open updater-script, delete:

assert(getprop("ro.product.device") == "jflte" || getprop("ro.build.product") == "jflte");

Then save the file and confirm modified file in WinRAR, now flash that zip

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] davidwilson83:
Ok MultiROM is installed. After installing MultiROM I flash TWRP_multirom_jflte_20140901.zip through TWRP and then reboot recovery. When TWRP reboots, I don't have any options under Advanced for MultiROM. Recovery is now showing 2.7.1 in the top left whereas before it was showing as 2.7.1.0 so I know that the recovery has changed.

Have I done something wrong? When I reboot the phone I get the MultiROM boot screen coming up asking me to either let it boot into the internal ROM or touch to change, but when I boot into recovery I have no options for MultiROM. I am happy to upload any logs that might help to decipher the issue I am having.

Thanks for your help mate.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
[MENTION=4603975]daveyannihilation[/MENTION]

Here no problem, do you read "MultiROM TWRP v2.7.1" on the left?

EDIT: New build available

Changes: Fixed installation on other jflte devices

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] davidwilson83:
Dude... I'm just an idiot. I had twrp holofied which wasn't showing the menus and buttons. This mod is AMAZING!!! Dude I have been looking for this forever, you are a king. I'm definitely gonna be using this from now on, thank you so very very much! [emoji4]

Alliance I9505
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
[MENTION=4603975]daveyannihilation[/MENTION]

Hahaha don't worry :)

Now just remember this

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] bdog2015:
Is the new build recommended or am I fine if everything is working for me?
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
The only change in new build is the fixed installation on other jflte devices. If you installed the previous build without errors, no need to update [emoji1]

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] Newbie F:
I downloaded the files and i also installed multirom. Thank you for your instructions. Something i would like to ask is

I have CM11 as secondary rom and i would like to install gaps in it. How can i do it. Like the update rom?

*Also can i remove the auto boot feature cause some times doesnt correspond well and it boots internal automatically
[Galaxy S 4 i9505 Original Android Development] fartlec:
install gapps.

reboot from twrp, advanced, multirom, list roms, choose cm11, flash zip

remove autoboot

from twrp, advanced, multirom, settings

either as OP suggest in useful tips

or, as you wish, disable autoboot
[Galaxy S 4 i9505 Original Android Development] Newbie F:
Thank you very much. Also i saw at the picture of the post thread that every memory has a unique name and avatar. How do you put those. Do you know? I just saw on the menu only rename internal memory.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Hello,

Since you are on 4.2 bootloader you need to install an AOSP 4.4/CM11 & CM11 based ROM along with correct kernel for your ROM:

Alucard AOSP for AOSP 4.4 & CM11-based ROMs

Alucard AOSPv2 for 'new' CM11 after 4 August's M9 build & CM-based ROMs that use updated jflte kernel source

Alucard GE for AOSP Google Play Edition ROM

You can't use a stock-based 4.4 ROM while on 4.2 bootloader.

If you want to reinstall your TW 4.2 ROM as secondary you can backup and restore as secondary through modified TWRP recovery

You can go under Advanced>MultiROM>List ROMs and choose what ROM you want to rename, then rename it through dedicated button. I saw now your PM, sorry but I was busy

[MENTION=4603975]daveyannihilation[/MENTION] thanks for helping people :) :highfive:

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] GiRaFa-SAMA:
I mentioned this in another forum, but I'll ask here ..

It is possible to later add a function in which the installed applications to be shared between the roms installed?
[Galaxy S 4 i9505 Original Android Development] Newbie F:
I would like also to learn the answer of the above. Or else i installed foldermount to put my games/app on my sd but i think that the problem cannot because system is modified. So i wonder is there a program that i could put my games/apps on sd without problems on system?
[Galaxy S 4 i9505 Original Android Development] fartlec:
a few pages back there is an answer. create ext4 partition on sd, install link2sd
[Galaxy S 4 i9505 Original Android Development] Newbie F:
So i read every singe page on this thread but nowhere i can fing answer. Something about loki what!! And i am newbie abviously so is there any link or something that could be helpful for ppl like me that are not so familiar with all these. How to create ext4 part that you mention above. :|||||||||||||||||||
[Galaxy S 4 i9505 Original Android Development] fartlec:
there are a lot of guides out there

here some

http://awanstuff.wordpress.com/2013...ink2sd-in-any-android-phone-with-screenshots/

http://xdaforums.com/showthread.php?t=1614700
[Galaxy S 4 i9505 Original Android Development] Newbie F:
Ok i thanked you for your help. And ofc i return with questions again

1. First of all i see the xda thread is from 2012 so i wonder is that program still workable? (lol that word i know)

2. When i put my apps or games on the external card how can i install them for the secondary rom. I ask that because i have many paid app from play store. So because internal memory is not big as the card i wonder if there is a guide on how then to use these apps that you link.
[Galaxy S 4 i9505 Original Android Development] stanguay:
TWRP screen Timeout problem

Hello,

Everything work great for me except for one thing with TWRP, everytime the screen timeout appear, the phone freeze and I can’t open TWRP, I need to push the Power button and reboot the phone. For the work around I disable the screen timeout but I would like to know if I am the only one with this problem and any fix?

Note: I don’t have this problem with the original TWRP

Thanks for your help

Phone : I337M

Bootloader: I337MVLUFNE1

Kernel: GoogyMax3 TW v1.1.8
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Hello,

Yes it's a common problem, never fixed until now just because isn't important :) but I'll fix it in the next build, if you can't live together...:p

Updates are coming, Tasssadar merged my commit on GitHub, so the companion app called MultiROM Manager has full support for this device as soon as the new update is released in Play Store by the developer!!

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] visanciprian:
Hey!

I have 2 problems:

1) I flashed a TW as internal ROM, and an CM11-based ROM as secondary ROM. Everything working perfect in the start, but if I try to flash Alucard Kernel on second ROM it fails booting and 2) there's no multirom_log.txt on /sdcard (maybe problems with mounting sdcard?)
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
This MOD is meant to use stock kernel that come in secondary ROMs

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] schizovivek:
couple of issues

hey.. first of all.. love this idea ! dual booting makes lives of flashaholics like me easier.. I have been able to make it work but I have a few issues.. Noting them down below.

1. In the modified TWRP any flash I do gives

E: EV_REL 6 <number>

&

E: EV_REL 7 <number>

errors while flashing. Its continuous and the only thing that changes is <number>. The flash does complete and I have been able to load the new ROM added but this wasn't occurring earlier. I s this something I should be concerned about? Even if not why is this occurring and how can I get rid of it?

2. I have a TW ROM as my primary. When I flashed to my external sd card (which is shown as /dev/block/mmcblk1p1) the new ROM (PA) I get an option to set cache/data and system partition sizes. Is there an optimum level I need to set them to, to get the best out of the secondary ROM?

3. I also installed the same ROM on my Internal. Installation was pretty smooth. But when the ROM loaded I just had this niggling feeling its pretty slow. Is this expected? The external SD ROM also seems slow but I changed the system partition to have 2GB. The one on the Internal seems slower in comparison. I'm judging performance from the point of view of having a clean AOSP ROM on my phone as the only ROM. Any tips on the best setup for performance would be appreciated

4. I do not get the option of "Share Kernel" in the first screen of MultiROM-> Add ROM. I just get "Android" and "MultiROM Installer" options. Expected?
[Galaxy S 4 i9505 Original Android Development] visanciprian:
so there's no support for alucard's kernel? can't make it work neither if i force inject kernel's boot.img & files into ROM's zip file.

so what are the supported kernels/ROMs then? thought it supports all ROMs
[Galaxy S 4 i9505 Original Android Development] Michael2907:
hi,

it is very interessting for me, but i had some question.

Must i change the kernel, or can i always use the stock one?
[Galaxy S 4 i9505 Original Android Development] WerWolv:
I found some icons in the .zip file. For example the Cyanogenmod, Paranoid Android and AOKP icons. I think, they should get displayed in the bootmenu. Is that correct? Because I've installed Paranoid Android as secondary ROM and it still displays the default 3-Lines-Icon. :3
[Galaxy S 4 i9505 Original Android Development] bernarbernuli:
Just update app "MultiROM Manager" and now supports Samsung Galaxy S4 (i9505).

https://play.google.com/store/apps/details?hl=en&id=com.tassadar.multirommgr
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Those are TWRP debug infos, nothing to worry about. About image size of AOSP/CM-based secondary ROMs in MicroSD card I suggest minimum 1024MB for system, 250~300MB for cache and what you want for data. For MIUI minimum 1536MB system and 400MB for cache. It's weird that it's slower, the secondary ROMs in internal memory (eMMC like primary ROM) have the same speed of the primary one, try to delete and install again that ROM. Best setup performance is to use internal memory for secondary ROMs due to less speed of MicroSD card. Share kernel option was available in older builds, no longer now.

Support for custom kernels is in primary ROM (a kernel with kexec-hardboot patch is always needed in primary ROM to make MultiROM working), theoretically all ROMs are supported. For custom kernel in secondary ROMs try to use KT or Googy-Max, Alucard one breaks boot of these ROMs.

You need to flash a kernel with kexec-hardnoot patch only in primary ROM (e.g. the one in eMMC partitions) to make MultiROM working. Look in post #3.

Yes, those icons are meant to be showed in boot manager. But still I can't find why aren't showed (maybe only on official supported devices?)

So, MultiROM Manager it's updated with full support for this device now :)

I'll continue to provide updates also in post #3, but starting from now you can install/update MultiROM, MultiROM's TWRP recovery and kexec-hardboot patched kernels from the Manager available on Play Store, even if you never installed this mod!!

Probably if you install and run that app now you'll have "update available" showed near MultiROM version. It's a ghost update because it's the latest one (1st Oct) available also in 3rd post, due to missing Manager support of MultiROM ZIP needed to parse currently installed build with the one for the update. Will be fixed as soon as I reach home. :)

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] schizovivek:
brilliant ! gave around 500 to cache and 2 gb to system.. Installed 3 AOSP ROMs (Mahdi, PA and SlimKat). SlimKat seems to work the smoothest. Installed all on my SD Card. Removed the Internal one. Gonna play around with this some more. THANK YOU FOR THIS !

btw... the boot pop-up of boot now/Cancel doesnt respond to touch. I need to press the Volume key to get to the menu. Expected?

Just installed MultiROM Manager app.. Getting the following screen:

MultiROM: v28 (Update available) -> I had installed v28c from the OP

Recovery: N/A (update available) -> Even this I picked up from the OP

Finally in Red it says "MultiROM recovery is not installed"

Guess this is a bug in the app for 9505 devices?
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
You mean rightly after you boot the device, in the boot manager? If so, touch works but needs 4-5 seconds to initialize touchscreen drivers.

Nope it's not a bug, flashable recovery in OP is the last one without MultiROM Manager support
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Updates

Here we go with v29!

25/10/2014

MultiROM:

Minor updates

Full MultiROM Manager support (this fixes the ghost update)

Modified TWRP:

Full MultiROM Manager support

Uninstaller ZIP:

Add support for other jf variants

Download links in post #3, or install/update through MultiROM Manager app!!
[Galaxy S 4 i9505 Original Android Development] Gransh:
Pretty nice

Thanks man for sharing
[Galaxy S 4 i9505 Original Android Development] bryantjopplin:
Is this similar with safestrap on how it loads different slots (roms)? Also anyway to easily make this work on the i545?
[Galaxy S 4 i9505 Original Android Development] 0kti:
I've tried v29. First rom PAC-man. Second MIUI. Both roms working great. Thx.

Send from Galaxy S4
[Galaxy S 4 i9505 Original Android Development] fjacquemot:
Hi,

i've installed v29 but when I change rom it still reboot in recovery mode.

There is no way to power off when selecting a rom to boot, either in boot menu or in app (restart option only).

I've seen lot of post about this problem and as I've read in this thread this should be ok since v28.

What am I doing wrong ?
[Galaxy S 4 i9505 Original Android Development] tiggerbcn:
+1 IDEM

Add the .log file
[Galaxy S 4 i9505 Original Android Development] davidmueller13:
The Device will switch of,when it' more then 5 min in Recovery.Then I have to press the Powerbutton for more than 10 sek. to switch on again or pull out the battery.
[Galaxy S 4 i9505 Original Android Development] stanguay:
Disable the Screen timeout in the setting of TWRP.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Safestrap and this are two completely different mods

Have you installed kexec-hardboot patched kernel?

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] bryantjopplin:
I understand is different. Was wondering if it's like boot manager the app which is similar to safestrap in that you can boot similar roms.
[Galaxy S 4 i9505 Original Android Development] alias4ever:
Forgive what may be a noob question. [emoji16] I am running out of space on my 16gb internal storage with the ROM I am currently using as a daily driver. I admit I let my 4 year old daughter play my phone and she loves a large variety of games. [emoji16] Anyway if I reformat my phone could I put the daily driver ROM on my microsd 32gb card for much more space? Is that possible? Then put the other ROMs I like just to test and use on the internal storage of my phone? Is that at all possible or recommended?

Thanks for this as of now it works great and I have 3 other ROMs so far installed other than my daily driver using this. I haven't had any issues at all with this. Works GREAT! Keep up the awesome work! [emoji106][emoji12]
[Galaxy S 4 i9505 Original Android Development] WerWolv:
[MENTION=4264654]alias4ever[/MENTION]

You should better put your Daily Driver on the Internal storrage and the others on external.

The external storage is way slower than the internal, so every ROM you put on an external storrage like your sdcard or a USB device will quite lag. For testing it's enough but for a Daily Driver I would strongly recommend you to put it on your Internal ;)
[Galaxy S 4 i9505 Original Android Development] gask7:
reply

i've installed v29 but when I change rom it still reboot in recovery mode.

the internal rom work perfect and secondary CM work perfect but secondary TW when reboot and selected this, reboot in recovery mode
[Galaxy S 4 i9505 Original Android Development] Technical:
I'm not being able to boot a copy of the primary ROM.

The log is attached.

Is there a way to copy primary to secondary on the external sdcard, or, in other words, can we move from one storage to another?
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Try to install TW ROM as primary and CM-based as secondary

There's a way to switch ROMs between internal-external storages, Advanced>MultiROM>Swap ROMs

Update

30/10/2014

Modified TWRP:

Update to v2.8.1.0

Check post #3 for Downloads or install through MultiROM Manager app
[Galaxy S 4 i9505 Original Android Development] Technical:
I've tried but I could not find a way to set the final destination of the ROM.

I know I can flash a ROM on sdcard, but could not find a way to set sdcard as the destination of a copied ROM.
[Galaxy S 4 i9505 Original Android Development] gask7:
thanks for replying.

No you misunderstood me.

Now I have CM in secundary and TW in the first. but i want to install another TW secondary and not start.
[Galaxy S 4 i9505 Original Android Development] stanguay:
New TW Kernel

[MENTION=5464206]AntaresOne[/MENTION]

The new Googy-Max3 Kernel 1.1.8 TW has the kexec hardboot (multirom) support and work great for me.

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

Maybe you can add it to the op.

Thanks again for your work. :good:
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Googy-Max3 kernel added to kexec-hardboot patched kernels for primary ROM in Downloads post. 30 minutes and I'll add it to MultiROM Manager :)
[Galaxy S 4 i9505 Original Android Development] Technical:
I'm not being able to boot any secondary ROM.

I've did two tests:

1. Installing from a nandroid of SlimKat (primary) as secondary ROM. All system, cache and data are on f2fs.

2. Installing a new CyanogenMod as secondary ROM.

The last error log is attached.

Besides, my sdcard (exFAT) was reduced from 32Gb to 9Gb and I've excluded both ROMs. Ah, I also flash MultiROM uninstaller.

It happened yesterday and I have to move and return back all the files, formating the card to get its 32Gb again... :mad:
[Galaxy S 4 i9505 Original Android Development] Vcolumn:
Just to clarify, this does not, and probably never will, work on carrier locked bootloader version of and S4? Like AT&T and Verizon. Love MultiRom on my flo. Thanks for expanding it to S4 :highfive:
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Do this:

TouchWiz or CM-based ROM as primary + correct kexec-hardboot patched kernel, Advanced>MultiROM>Add ROM>install a secondary ROM from ZIP file in Internal memory (not SD Card)

In this way, memory used is dynamic (internal memory, so /sdcard (a symlink of /data/media/0) and not FAT32/EXFAT that needs to create fixed-size images), you can remove ROMs without formatting any memory. For any problem, you can contact me through PM

Wait, maybe I have found a solution for vzw and att variants...:)

Recovery updated

4/11/2014

Modified TWRP:

Add back "Share kernel" option (same behavior can be obtained by pressing "Remove boot.img" under MultiROM>List ROMs>*rom name*)

As always, download flashable zip in post #3 or install directly through MultiROM Manager app :)

I have also added Googy-Max3 kernel to MultiROM Manager.
[Galaxy S 4 i9505 Original Android Development] mitky82:
I have reboots to recovery too, when i pres to boot from second rom :(

I use one kernel for two rom and other settings with different for ech other and cant boot second rom :(
[Galaxy S 4 i9505 Original Android Development] ilfrick:
Recovery

The app itself is flawless and eeverything else worked fine as for flashing and booting everything I threw at it. One big problem though: recovery freezes and the phone must be force rebooted to revive it. This is scary, what if it happened while flashing the main rom? It's still there with the latest update and I don't think it's due to TWRP (it doesn't happen with regular 2.8.1.0 or any version since 2.7.0.1).
[Galaxy S 4 i9505 Original Android Development] stanguay:
Read post #210

Envoyé de mon GT-I9505 en utilisant Tapatalk
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Don't use any custom kernel in secondary ROMs, leave the one shipped with zip file

Latest recovery works normally and doesn't have any freeze here.

To answer to your question: if happens while flashing primary ROM no fear, just boot recovery and flash again.

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Oh, I thought he was saying that recovery stops to work... Thanks! :highfive:
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Update available

Disabled annoying TWRP event logging

No more red debug strings :)

For download check post #3 or install/update through MultiROM Manager app
[Galaxy S 4 i9505 Original Android Development] 65vdub:
I'm curious as to what the solution is (or might be)
[Galaxy S 4 i9505 Original Android Development] Technical:
Many thanks. Indeed, they worth nothing and add no info at all :silly:

---------- Post added at 09:07 PM ---------- Previous post was at 09:04 PM ----------

But will this issue be addressed, I mean, solved?
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Wait and see [emoji14] gimme some time, I'm very busy

Soon, in the next recovery release. :)

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] 65vdub:
I will wait patiently then :)

Thank you for your hard work!
[Galaxy S 4 i9505 Original Android Development] Technical:
I've tried to flash MIUI and CM as secondary (internal sdcard) and both failed to boot.

When I choose them into the menu, phone boots into Recovery again and tells an error ocurred.

I'll try to upload the log later.
[Galaxy S 4 i9505 Original Android Development] Technical:
Tried again. CM with its default kernel: boots. Installing the latest pb version of Alucard: multiboot error (can't boot).
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
I said more than once in the past to use only default kernels in secondary ROMs...:)

Inviato dal mio GT-I9505