yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] MrCeez:
I've installed the ROMs on my SD card but upon booting I can not see them to select. Some guidance please
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Seems that needs better integration (it's a feature born these days), it's not mine and depends on original MultiROM, even if I can complete myself

New build out! v28c

Device source:

Add MicroSD Card to init devices

Fixed device autoboot in recovery after a reboot/shutdown!!

Now ROMs installed on MicroSD card are recognized in boot menu.

No need to wait some time after reboot/shutdown. Now you can power on again right away!! :victory:

Download in post #3
[Galaxy S 4 i9505 Original Android Development] FeyoMx:
Thanks for the new build. Now if I can see the ROM in the external card. but I can not start it. seems to start but goes to the boot animation of the internal ROM
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Some other instability may be possible, I'll continue to support and debug boot from MicroSD but I'm not interested to use it :)

The best option is always install and boot from internal memory, in this way the speed is 1:1 as the primary ROM since all the ROMs boot from the same eMMC.

External memory is much slower than internal one, meaning longer ROM install process and slower boot (snail mode? Lol) plus highly depends on MicroSD's class

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] FeyoMx:
I actually was not interest me so much just testing the feature. it would really be great is to share applications between ROMS, I read that you were working on it, how it goes? or is there any easy way to do it?

Thanks in advance
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Yes I'm working on it but goes slowly (less free time)

This option should be considered as can really work

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] jimbomodder:
I was never able to flash gapps for secondary ROMs, where did I go wrong?

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
What kind of GApps package are you trying to install? Are you installing secondary ROMs on the internal memory (/sdcard) or Micro SD?
[Galaxy S 4 i9505 Original Android Development] jimbomodder:
I'm trying to flash open gapps Pico, I flash the 1st from with gapps and boot up no issue, I then try flashing second either on internal or SD card but I can't select gapps. Im sure I'm doing something wrong

EDIT: sorted, my noob self didn't see the "add zip" button. Looking forward to multirom 3.0.2-0
[Galaxy S 4 i9505 Original Android Development] jimbomodder:
Well now ive sorted that I've got another issue, I've installed secondary onto ext SD card as far more space but I cannot install all my apps as I've run out of room!? How can I get round this please guys

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

Clearly shows more

Yet this shows different
[Galaxy S 4 i9505 Original Android Development] ValerieAnne84:
I guess I'm not meant to use mutlirom tools lol. I wanted to try a new rom without redoing everything again and when it's installing I get a failed error on the 'mr update' thing (sorry I don't know how to logcat from recovery). Telling me my update isn't update to date but according to the MUTLIROM application itself, I have everything installed/updated correctly. It even downgraded my TWRP from the newest to a different version (2.86 I believe, didn't check but it looks like the 2.86 one) Ooh well. Just thought I'd say it here incase others have a problem.

There's nothing wrong with my current rom was just gonna test a new one to see if I wanted to switch over. Not a huge deal/big deal at all.

Thanks for all the hard work put into it =D Oh and I'm using a sprint variant S4.
[Galaxy S 4 i9505 Original Android Development] benlm72:
Same pb for me, but when you then reboot system from the recovery you finally enter second rom. Strange, but it's a long time since it works like that for me.
[Galaxy S 4 i9505 Original Android Development] Xenotrumpet:
[MENTION=5464206]AntaresOne[/MENTION] If you don't want to support this project anymore, have you considered open-sourcing it? Or what would you do?
[Galaxy S 4 i9505 Original Android Development] Sale.s:
I installled this MultiROM menager and 2 roms on I9505.

How can i now completly remove everything (roms and multirom)?
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
It is already open-source in JDCTeam's GitHub, the current issue is still the MultiROM TWRP's too big for JF's recovery partition (basically something already happened in the past but the differences between TWRP < 3.0 and the newest are a lot, therefore there's more work to do on recovery's kernel to get smaller recovery image)

Flash MultiROM uninstaller zip, you can find it under Downloads in this thread. Or just delete "multirom" folder in the internal memory using TWRP recovery's file manager
[Galaxy S 4 i9505 Original Android Development] Dang !!!:
support for i9500

sir, please aad support to i9500 users
[Galaxy S 4 i9505 Original Android Development] grebulon:
Tried to install JDCTeam's Nougat AOSP build - doesn't work...
[Galaxy S 4 i9505 Original Android Development] Mitsch79:
Nor does it work for CM13 nightlies as secondary rom. My first rom is Imperium V15. All you get is an error regarding a mr-update.zip.
[Galaxy S 4 i9505 Original Android Development] vitalogy_rs:
Hello,

So I installed multirom, everything was OK (I thought so) and I had the stock rom from Samsung on internal and OptimizedCM13 as secondary rom. When I tried to use the camera on the stock rom I got "Camera failed".

I managed to understand where the problem was, both kernels for the touchwiz , version 5.0.1, crash the camera app.

Anyone else with this problem? Or with a solution?

Cheers
[Galaxy S 4 i9505 Original Android Development] m3rkd45:
AICP (Android Ice Cold Project) works without any problems as primary or secondary ROM in my GT-I9505...

h**p://dwnld.aicp-rom.com/?device=jfltexx
[Galaxy S 4 i9505 Original Android Development] V3rt!g(o):
Theres a way to bypass that but its kinda pain in the behind :)

So, you have a primary rom with multiboot and everything works fine

In recovery:

back up primary rom

install a a new primary rom that wont work as secondary and back it up

restore old rom as primary

restore new rom as secondary

rename it because it will have the old roms name (maybe)

I got it working and cross-testing JDC CM14 as primary and RR CM14 as secondary

The reboot to recovery bug is annoying but...how many times in your regular day do you switch roms? ;)

Bugs aside, Multirom is still a very powerfull piece of code thx to Antares :)
[Galaxy S 4 i9505 Original Android Development] ayesco:
Does it work on s4 value addition jflvete
[Galaxy S 4 i9505 Original Android Development] m3rkd45:
All check xda-member alaskalinuxuser https://xdaforums.com/member.php?u=7026648

https://thealaskalinuxuser.wordpress.com/homemade-kernels/samsung-galaxy-s4-kernels/

and

https://thealaskalinuxuser.wordpress.com/homemade-roms/samsung-galaxy-s4-roms/

His kernel-builds support kexec-hardboot!

(SlimRom MM)
[Galaxy S 4 i9505 Original Android Development] vinadoros:
assert in updater-script

First off, thanks for your work on this. I just got done installing it, will give it more testing as I go along, but I'm glad we have a good multiboot option for jflte!

Question: I noticed a few pages back that some users were having an issue with the assert line in updater-script:

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

I tried flasing 28c (multirom-20141001-v28c), and got the assert failure on my device (which is a jfltespr, an SPR-L720). I know you mentioned this had been fixed previously, but is it still fixed for the latest release? I removed the assert line in updater-script, and the file flashed just fine afterwards. Just thought I'd check ;)
[Galaxy S 4 i9505 Original Android Development] MrCeez:
What classes of SD will bring us near 1:1 speed as my ROMs on the SD are unusable due to lags. Thanks
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
The assert checks for jflte device, the jflte contains all variants like xx, usc, can, spr...

For the last build I leaved the assert as is, if you got error it's the case to continue to add other devices :)

Near 1:1 only a good class 10 card. I'm on Samsung Plus 32GB UHS-1

For new users: multiboot is supported from both internal and external memories!

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] xzaxox:
I use now Cm11 and try to flash multirom but I got installation aborted :/ Whats wrong? Search didnt work at xda right now so I dont know if this is already asked and answered.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Read post #101

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] xzaxox:
I dont find this line from the updater script :/

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

I only got "installation aborted" no mention to assert.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
It's this:

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

EDIT: Package uploaded again with fixed assert.

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] xzaxox:
I feel myself sooo stupid rightnow but I have to ask if this is even right place where I am searching for?:rolleyes:

multirom-master.zip\multirom-master\install_zip\prebuilt-installer\META-INF\com\google\android\updater-script

Edit: Ok I download new package. Thanks!

---------- Post added at 01:10 PM ---------- Previous post was at 12:51 PM ----------

Now I am so confused :( What I am doing wrong or is there something wrong with my phone/recovery.... I still get installation aborted. I also tried to flash that twrp recovery from your link and same error there :eek:

Then I tried to flash other recovey and there wasnt any problems :eek:
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Recovery doesn't have assert, so installation can only be good

What jflte variant do you have?

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] xzaxox:
Jfltexx
[Galaxy S 4 i9505 Original Android Development] Wyneg:
Hi!

I have a dumb question too: do you have planned make a version to galaxy s3? If you don't, do you know somebody doing that?

Thanks! :D
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
I have the same variant and no problems here with the last updates

I don't think so, I don't own a Galaxy S3 and to make something for a device that I don't have it's very hard, it's not like compile a ROM, MultiROM needs a lot of work and without a device to test isn't possible

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] BerndHhn:
i'm speechless... Multiboot still alive! Great Job!
[Galaxy S 4 i9505 Original Android Development] tabish84:
I had the same problem with 28c installation failed so I installed 28. I have i9505
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
The 28c works well, retry the updated download

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] tabish84:
I redownloaded and 28c works
[Galaxy S 4 i9505 Original Android Development] mitky82:
Sorry for noob question, but I try to install cm11 on ext card. I install them, but how to flash gapps? When I flash them, gapps is like other rom in boot menu

Ops, sorry I will follow update steps :)
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Just go in MultiROM settings>List ROMs and select a ROM, then "Flash ZIP" to flash a ZIP file into a ROM :)

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] SKyLiNe1980:
Only the alucard kernel works for me. The kt is being detected as non kexec hardboot when trying to boot secondary rom.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
So guys, I've added support to MultiROM Manager app :) later I'll write how it works

Now just wait that Tasssadar releases an updated version in Google Play Store with this inside

Thanks for the help [MENTION=5093942]KINGbabasula[/MENTION] :highfive:
[Galaxy S 4 i9505 Original Android Development] kevinco1:
If this could eventually work for AT&T users, you'd be a hero to all the people that who have had to use Safestrap. It's very limited compared to this project and the dev jumped ship a few months back.

Support for either carrier would bring in droves of people who would be more than interested in its potential. Keep up the hard work and thanks
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
It's very difficult that in future will work on AT&T and Verizon variants due to the locked bootloader (and so the bootimage modify restriction) that hardly breaks the way how MultiROM works.

Integration of Loki patch with MultiROM may be possible (strongly unsure) but requires the rewrite of all the code that modify and write again the bootimage... A hard and long work

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] kevinco1:
Loki could work, unfortunately it only works up to MDL. There's been at least five new firmware releases since then which most users have taken. That's why so many people are using Safestrap. No one has come up with a Loki type of exploit since then which probably won't ever happen again.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
[MENTION=4675887]arcane spade[/MENTION] tried a test that I have prepared some days ago on his vzw variant. Loki-modified bootimage it's kinda different and can't be unpacked with umkbootimg Linux executable like non-Loki one, so even MultiROM can't. I sent him Alucard kernel already patched with MultiROM stuff inside ramdisk (from my jfltexx) and repacked a flashable zip with Loki patch. Result? MultiROM stuff is messed up, in fact there's no menu at boot. Obviously, the command "Inject curr. boot sector" from modified TWRP can't work

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] flexxoo:
[MENTION=5464206]AntaresOne[/MENTION] can you port this to the tmobile note 3?
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Sorry but I don't think, I don't own a Note 3 and to make this project for a device that I don't have it's very hard since needs a lot of work and without a device to test in my hand isn't possible

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] rebel1699:
This is working perfectly on my T-Mo S4 running Dirty Unicorns and Nameless rom as secondary. I have used MR since it was first created and released on the Nexus 7 2012 model. I love being able to use it on my S4. Hopefully Tassadar will get the MultiRom manager on the store updated with compatibility for our device. Great work op!
[Galaxy S 4 i9505 Original Android Development] tabish84:
I uninstalled multirom with multirom uninstaller then flashed the twrp recovery but did not installed the regular kernel and now I can not boot into recovery although I installed recovery through odin. Can anyone give me a link to a kernel for tw rom with .tar extension
[Galaxy S 4 i9505 Original Android Development] xzaxox:
Two questions:

Can I do backups in recovery? Primary and secondary roms.

Why it is not recommended to install TW rom as secondary?
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Yes, you can backup.

It's not recommended because TW ROMs are huge and occupy a lot of space when installed as secondary ROMs
[Galaxy S 4 i9505 Original Android Development] cantenna:
Will this work with Faux kernel GPE as primary? Thanks!
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Nope due to unpatched kexec

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] R.Suave:
Just wanted to stop by and say thanks for the work you've put into this :good:
[Galaxy S 4 i9505 Original Android Development] imjustafq:
please somebody port this to 9500 :)
[Galaxy S 4 i9505 Original Android Development] cantenna:
Pitty, thanks for letting me know. Would the op of the thread be able to add? Or just Faux
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
:)

Look https://github.com/AntaresOne/multirom_device_samsung_i9500. I'm starting :)

I know how but I don't wanna lose time doing it where there's already other kexec-hardboot patched kernel, try to ask him if he can :)
[Galaxy S 4 i9505 Original Android Development] robertogl:
There is a way to separete the sdcard from the internal rom and another rom? I use a lot of apps that use the internal sdcard for their data, if i install the same apps in the second rom the data are in conflict... :p
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Only app's cache may be in conflict, since app data is in data/data even in MultiROM ROMs

Can I configure boot menu to be showed only when I want?

You can. Boot in TWRP recovery, go under Advanced>MultiROM>Settings>Configure autoboot and set Keypress-based, then select a ROM to autoboot. In this way, if you power on your device boot menu isn't showed and the ROM you choose to autoboot is booted, but if you power on and rightly when you see "Samsung Galaxy S4" bootlogo you press and keep pressed Vol+ or Vol- button, boot menu is showed.​
[Galaxy S 4 i9505 Original Android Development] dacmcbibs:
I noticed that the installer blocks installation of a verizon S4. I assume this is due to the locked boot loaders. Is there any reason those of us early adoptors with an unlocked boot loader couldn't modify this to work on our phones, or is there something else involved with a verizon phone that i should avoid playing with this?
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
I have disabled installation on AT&T and Verizon devices due to the locked bootloader that totally breaks the way how MultiROM works. I'm still searching for a solution :)

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] cantenna:
The reason I asked is because Faux kernel is the only GPE kernel that supports mounting of obb folder in folder mount.

But know worries, I'll try touchwiz as base instead.

Thanks for releasing this!

Cheers!
[Galaxy S 4 i9505 Original Android Development] cantenna:
"Don't share kernel' can't fine where this option is?

edit: sorry for double posting.

I have TW 4.4.2 Installed as primary and have installed GPE 4.4.4. As secondary on external fat32 micro sd.

Whenever I try to boot secondary it reboots into recovery

edit2; awesome!

Running Sky fall 4.4.2 TW with All Share by iB4std as primary and Danvdh CM 4.4.4 as secondary (daily driver)

Also created a 10gig second partition on extsd for running my secondary ROM.

Awesome! Thank you OP for porting this over. I have been running multirom on my xperia tablet z as well, made me want to get this to work.

Will this work on a Knox tripped 0x1 boot loader?

Cheers!
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Please don't make a double post if aren't yet passed 24 hours from your last post...

Share kernel option is no longer available, so as default kernel isn't shared.
[Galaxy S 4 i9505 Original Android Development] tiraceite:
I've installed miui rom 4.4.4 from this thread... in SD card I can see folder with rom but in recovery I can't swap between roms. I can't see secondary rom.
[Galaxy S 4 i9505 Original Android Development] design12:
I seem to be having an issue. I installed the multirom zip then the modified recovery. But when I go add a secondary rom this appears when flashing especially the first 2 errors. I'm currently on carbonrom 4.4.4 and alucard 1.4h kernel and jfltetmo.

View attachment 2962387
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
The secondary ROMs are in boot menu, in "Internal" if are installed in data/media/0 or in "External" if are installed in /external_sd

I can't see any error there, red strings are just TWRP debug infos.

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] design12:
So those are normal then? I was trying to install a TW rom but every time I choose it, it boots up back to recovery.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Are you installing as secondary or primary?

Are you installing any custom kernel on TW ROM if secondary?

If primary can't have error.

Don't trust the "Recovery booting" when you choose a secondary ROM, wait that the ROM boots

Don't forget to use kexec-hardboot patched on primary ROM only

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] design12:
I'm installing it as secondary to just try it. I'm using the custom kernel it already has built into the zip for the TW rom. And for my primary I'm using alucard kernel 1.4h. Do I still have to patch it?
[Galaxy S 4 i9505 Original Android Development] dacmcbibs:
Ok, so those of us lucky folks with an unlocked bootloader should be ok.

When I get a free moment I'll perform a full backup and give it a shot.

thanks!
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Yes, any variant with unlocked bootloader is okay

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] cantenna:
So I have Danvdh CM 11 M9 4.4.4 kitkat as secondary and Skyfall 4.2.2 TW installed as primary working perfectly but I'd prefer to use ASOP as my daily driver over TW. I can't for the life of me setup TW as a secondary ROM and I have tried just about every TW ROM available to me, crashes every time?

Any ideas? I like the idea of keeping tw around in case I need it but my daily driver takes 10 mins to boot from micro SD.

Anyone have any ideas?

Is it possible micro SD speed will be improved as future updates roll out?

Edit: I found out how to significantly reduce boot time on secondary ROM when installed to extsd, keep the primary ROM as lean as possible! I.e. don't install a lot of apps. Works for me because im really only using touch wiz for camera, telephone commands and all share support anyways. Wonder why though boot time increases for secondary ROM on extsd the more apps I have installed on primary?
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Install on Internal Memory, not in SD!!

Guys I remember to everybody that this Mod supports Internal memory & MicroSD! The Internal memory is the main part of MultiROM!

Installing on Internal memory: boot time 1:1 as primary ROM

Installing on SD: boot time unknown

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] noooooo:
Is there a way to share app data between rom? any xposed module or something? it would be fantastic
[Galaxy S 4 i9505 Original Android Development] davidwilson83:
MultiROM dual booted Dirty Unicorns I9505
[Galaxy S 4 i9505 Original Android Development] noooooo:
Using link would help me to move the apps, but I'd like to share app data also, this would have the same solution?

---------- Post added at 03:11 PM ---------- Previous post was at 03:10 PM ----------

PS, with app data I mean the settings (like video game saves)
[Galaxy S 4 i9505 Original Android Development] fartlec:
have you tried with gl to sd ? gonna try it now, would be totally hassle-free

edit. not good.. it just moves data, not the app itself. at least, i have to install the apps in both the roms