yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Terr20114:
AWWW Man! I wish i hd noticed that there was a new page. I just tried and got the multi rom black screen error too. I.m currently restoring my TW Backup. can you please try the boot.img thing you mentioned. oh n by the way it didnt flash the preload. I'm guessing that might be why it failed.
[Galaxy S 4 i9505 Original Android Development] ckvisme:
Going through the process right now... I'll let you know how it goes... Cross ur fingers

...ok, going to take a bit longer... I forgot I deleted the Rom zip already

(I've got 209mb on internal storage available)

I'm re-downloading to another device then I'll grab the boot.img I need ?
[Galaxy S 4 i9505 Original Android Development] Terr20114:
lol, and thanks man, I really hope it works. wishing u the best of luck
[Galaxy S 4 i9505 Original Android Development] ckvisme:
No good?...MultiRom just shuts down.

Also tried running restorecon with terminal emulator

Su

restorecon -FR /data/media/0

Su

restorecon -RFv /system

Su

restorecon -FRv /cache

But as stated in the thread I linked previously, I think there may be some issues with the recovery binaries that cause restorecon to fail
[Galaxy S 4 i9505 Original Android Development] Terr20114:
Thanks alot once again man, I really hope this gets fixed soon since I doubt samsung will be giving the s4 the marshmallow update. So I'll need this touchwiz rom but i still wanna use android M. I'd like to have 6.0 as my secondary rom. All the bet wishes man.
[Galaxy S 4 i9505 Original Android Development] nicolapit:
I have samsung S4 I9505 with lollirom deodex 6 that works fine - I want also lollirom odex 6.

I'm installing multirom...

I have installed multirom zip file from recovery and the new twrp form recovery and I have rebooted the phone in recovery mode, now in advanced mode in list roms I haven't roms so I have selected add rom and it says choose rom type

I have 3 questions...

1 - it says: android OR multirom installer (*.mrom files)? - what must I do?

2 - it says install to: internal memory OR /dev/block/mmcblk1 (vfat)? - what must I do?

3 - what do you suggest for primary rom odex or deodex?

thank you
[Galaxy S 4 i9505 Original Android Development] jimbomodder:
Unable to change splash screen.

Device-jfltexx

Recovery- multi rom v2.8.6.0
[Galaxy S 4 i9505 Original Android Development] Technical:
Why?

In my case, I couldn't find (

yet

) the img file to follow the default procedure described here: http://xdaforums.com/showpost.php?p=56224204&postcount=2
[Galaxy S 4 i9505 Original Android Development] jimbomodder:
I can change it on non-multirom recovery with out issue.

Edit:: sorted,
[Galaxy S 4 i9505 Original Android Development] jimbomodder:
Only real issue is if i install a new rom it wont let me / cant find a way to flash gapps, currently got aicp as main and tipsy backup as secondary

Sent from my SM-T210
[Galaxy S 4 i9505 Original Android Development] cookiiee94:
I'm running imerium ll 10.1 as primary, and I installed jdc team aosp as secondary, but it fails to boot
[Galaxy S 4 i9505 Original Android Development] Xenotrumpet:
JDC AOSP Alucard kernel does not have the kexec-hardboot patch. Flash their stock CM kernel.
[Galaxy S 4 i9505 Original Android Development] cookiiee94:
So I flash stock cm 12.1 kernel to my secondary (JDC AOSP) rom? Where can I find this kernel?

Thanks in advance [emoji4]
[Galaxy S 4 i9505 Original Android Development] coolasice1999:
go under advanced, multirom, list roms, select your rom, and you can then flash zip to that rom.
[Galaxy S 4 i9505 Original Android Development] meangreenie:
got a weird one.. if i set radio.img i get no sim detected on the secondary rom; removing the radio.img it then works fine again

i got 4.4.4 on primary and new m6.0 on secondary

the radio thing always worked for me no problem before, anyone have an idea?
[Galaxy S 4 i9505 Original Android Development] jimbomodder:
Which device u got?

Sent from my SM-A500FU
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Not a S4, these devices seems to be:

Google NEXUS 5

LG G FLEX 2

LENOVO K3 note

I'll say: Google NEXUS 5 for Marshmallow.
[Galaxy S 4 i9505 Original Android Development] Technical:
Thanks! Will test right now...

Any reason for the MultiROM TWRP to be in 2.8.7.0 version and your TWRP F2FS on 2.8.7.1 ?

Can't MultiROM TWRP go further and be updated?
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
That's just a minor patch (reserved as device-specific) :)

We didn't have yet a 2.8.7.0 for MultiROM but already got it for the TWRP-F2FS, so to add the IMEI backup/restore I bumped to .1
[Galaxy S 4 i9505 Original Android Development] benlm72:
Multirom error at first boot

Hi,

I've updated my S4 with the last manager app version, and installed recovery and multirom from the app, the operation were successfull. I had already installed Imperium kernel v2.9.

Then I've tried to install last Optimized CM12.1 from JCDTeam in multirom, in internal memory. Install is successfull but at first boot a get at multirom erro message, telling me multirom will shut down to avoid data corruption.

Atatched is the log of my last try : Optimized CM12.1 on internal memory (last because I've already tried AOSP and Opt CM12.1 on microSD/Ext4 and internal, with the previous multirom version, I had the same pbs. The only build I manage to install is an old Opt CM12.1 from july).

Does anyone faced this pb and have a workaround ?

Many thanks for any help !
[Galaxy S 4 i9505 Original Android Development] jimbomodder:
I got that when I installed the recovery included in the app. DONT DO IT, use recovery provided in op.

Sent from my SM-A500FU
[Galaxy S 4 i9505 Original Android Development] benlm72:
Thanks for the help. I've tried that, but unfortunately it has changed nothing !
[Galaxy S 4 i9505 Original Android Development] jimbomodder:
No it won't. Unfortunately the only fix I did find and get to work was stock ROM via Odin, seems to be only fix unless someone else knows something.

Sent from my SM-A500FU
[Galaxy S 4 i9505 Original Android Development] benlm72:
Yes, that's what I would avoid... as you say, if someone else knows something !
[Galaxy S 4 i9505 Original Android Development] mehdoux:
Hi,

I'm exactly facing the same issue. This problem was also present with the previous version of MultiROM. (v32a)

My first ROM : EdYoBlue ROM (TW Based) with Imperium 2.9 Kernel

Secondary ROM I would like to install : JDCTeam AOSP or OptimizedCM12.1

Well, always the same message after rebooting and selecting the secondary ROM : "to avoid data corruption blablabla..."

Anyone has a solution ?

Thanks.
[Galaxy S 4 i9505 Original Android Development] BillSwaginGates:
Will this new version fix the bug with TW rom as primary where touch in multirom menu doesn't work? Excited to try it out! :D
[Galaxy S 4 i9505 Original Android Development] benlm72:
Not for me ! But installing OPT CM12.1 as primary enables touch in multirom.
[Galaxy S 4 i9505 Original Android Development] saranhai:
Been trying to get one of the latest TouchWiz ROMs to boot as a Secondary, but none of them seem to be booting correctly, they all auto reboot straight into TWRP, anyone else experiencing this? Is there something that I missed?

Thanks!
[Galaxy S 4 i9505 Original Android Development] BillSwaginGates:
Touchwiz Roms do not boot as secondary they can only be installed as primary roms
[Galaxy S 4 i9505 Original Android Development] benlm72:
I've installed OPT CM12.1 as primary. then I've tried to install my TW backup+AEL kernel as secondary : I've always the same pb. So help would always be welcomed !
[Galaxy S 4 i9505 Original Android Development] Duck4Cover:
Is there anyway to get the latest TW roms to be the primary? As they all seem tobe ported when you try to it States that it will not work on these roms as they are not shown as GT-I9505. When you mod the plist it causes all sorts of issues.
[Galaxy S 4 i9505 Original Android Development] PePeMoke:
Hi.

I wonder if there is version of twrp 2.8.7.2 (newest modified by Antares with options to backup IMEI, golden copy etc.) supporting multirom as I do not want to give up this options..
[Galaxy S 4 i9505 Original Android Development] BillSwaginGates:
I think you're talking about the updater script not allowing the rom to flash because it is not "the correct version" even though all international variants are the same (i9505, jflte, jftlexx, etc) I have no problem flashing TW roms as primary, for me it's usually the custom CM roms that have the updater script issue, which is a quick fix and doesn't cause any bugs that I'm aware of. However, the reason I'm not using multirom right now is because of the touch functionality bug when I do have TW roms as primary where touch in multirom menu doesn"t work.
[Galaxy S 4 i9505 Original Android Development] Okaham:
Are there any Kexec-Hardboot kernels for TW 5.1.1 ROMs? Thanks!
[Galaxy S 4 i9505 Original Android Development] PePeMoke:
Boots into recovery (Ram cleared)

Hi guys,

I've got the issues too that secondary ROM won't start even when I wait more that 10 secs to let RAM clear..

On a GT-I9505 I use this one as primary:

http://xdaforums.com/galaxy-s4/i9505-orig-develop/exclusive-antaresone-alucard24-s-t3066696

I try to use this one as secondary:

http://xdaforums.com/showpost.php?p=63729768&postcount=312

Is it caused by using a wrong kernel for the secondary cm13 based one?

Can you help me out please?
[Galaxy S 4 i9505 Original Android Development] BillSwaginGates:
My guess is that 6.0 isn't supported due to there not being any official development thread for 6.0 on our S4's. Marshmallow is pretty new and probably won't reach the S4 for a few months (as did TW lollipop) Have you tried installing the CM13 as primary, or even without multirom altogether?
[Galaxy S 4 i9505 Original Android Development] dancekid:
Selektion of secondary rom always boots into TWRP

Good Morning,

i can confirm this issue:

installed CM12.1 Antares optimized as Primary and different Roms as secondary: crdroid, CM11, SlimSaber, Antares CM12.1 Test.

Everytime i choose any secondary Rom, it boots to TWRP instead of booting into Rom.

Selection Reboot in TWRP boots into selected secondary.

Greetings Michael
[Galaxy S 4 i9505 Original Android Development] PePeMoke:
Tried with resurrection Rom and got the same issue.

Then after it booted into recovery I selected "reboot system" as Michael mentioned said and it worked.

Will give it a try with CM13 today and report back.

EDIT: Does not work. FC on boot.

CM13 seems not to work as secondary. Might work as primary but I did not try.
[Galaxy S 4 i9505 Original Android Development] BillSwaginGates:
Thinking back I do remember experiencing this bug back when I had multirom installed, not sure whether it was after booting into primary or secondary though. Might be a bug with the multirom TWRP or with the booting process from the multirom menu. I'd try different combinations of roms and see if the problem persists.
[Galaxy S 4 i9505 Original Android Development] ceanth:
Hi all,

I have tried MultiROM on my i9505 and it installs fine however I cannot boot into a second rom which is on my SD Card.

I install the ROM (tried both Ubuntu Touch and MIUI7) and when I select to boot those ROMS I am taken back to TWRP. If I then reboot the device from TWRP it looks like the device tries to boot the second ROM however it fails and I am left with a blank screen with lots of text on it.

I have tried two different ROMs but the exact same thing happens. Can anybody advise as to what I am doing wrong?
[Galaxy S 4 i9505 Original Android Development] ceanth:
To add to this, I receive an error:

An error occurded.

Shutting down MultiROM to avoid data corruption

Report this error to the developer!

Debug info: /sdcard/multirom_log.text

Press POWER button to reboot

I have attached the log file.
[Galaxy S 4 i9505 Original Android Development] Gerxp:
I have exactly the same issue with booting into secondary rom. But this is with TWRP from 10/29.

Before this I used TWRP 2.8.6.0 from 6/15 and there was no issue.
[Galaxy S 4 i9505 Original Android Development] znayver:
Can i flash this rom at i9506
[Galaxy S 4 i9505 Original Android Development] ceanth:
How can I use TWRP 2.8.6.0? My understanding is that the Multirom setup installs a custom recovery with a new option for multi boot.

Can I simply flash this modified TWRP?
[Galaxy S 4 i9505 Original Android Development] Technical:
Yes you can flash the modified TWRP. But it is already on 2.8.7.0.
[Galaxy S 4 i9505 Original Android Development] Johan1976:
Im having the same problem as the rest. Secondary rom ends up in recovery. Reboot to system ends up booting original rom (trying to boot from otg-usb)

Anyone looking into this?

Skickat från min GT-I9505 via Tapatalk
[Galaxy S 4 i9505 Original Android Development] Technical:
Same here.
[Galaxy S 4 i9505 Original Android Development] Osama Chishty:
Installed Optimized CM12.1 Antares as Primary and Antares 6.0 dec as secondary rom.. but keep booting in recovery, if i try to reboot from recover it stuck on black screen with led lights... anyone help me about this thanks in advance
[Galaxy S 4 i9505 Original Android Development] benlm72:
I had the same pb with AOSP from JDCTeam. The only way I found thanks to smeroni68 was to backup cm12.1, install the new rom aosp 6.0 as primary, and restore cm12.1 as secondary. Probably you can restore cm12.1 as primary and restore antares 6.0 as secondary to match your aim.
[Galaxy S 4 i9505 Original Android Development] PePeMoke:
You can do it like that. works fine.

http://xdaforums.com/showpost.php?p=63889707&postcount=43

---------- Post added at 10:35 AM ---------- Previous post was at 10:31 AM ----------

I've got a problem.

I've installed cm12.1 optimized as primary and AOSP 6.0 as secondary.

Works fine so far but everytime when I switch ROMs whatsapp wants me to verify my number because I used it on "another phone".

Anyone an idea how I can get rid of it?
[Galaxy S 4 i9505 Original Android Development] Mr.Yawnie:
Backup Whatsapp using titanium backup on either rom. Switch roms and restore Whatsapp backup. You will be signed in on both roms. One issue to keep in mind though; messages sent/received in 6.0 won't show in 5.1.1 and vice versa as they share different memory slots.
[Galaxy S 4 i9505 Original Android Development] PePeMoke:
Will try.
[Galaxy S 4 i9505 Original Android Development] Galukon:
Hey all,

I was thinking of flashing MultiRom. In the installation is my primary ROM touched? I will make a backup ofcourse. Can i run ROM's from my SD card? I have a 16 Gb S4 so running another rom on Internal Storage isn't that great for my storage. Thank for answers
[Galaxy S 4 i9505 Original Android Development] Technical:
We're not able to flash MM Roms in MultiROM as we get "update-script" error. I've tested with 4-5 different ROMs.

Is it only me? Are devs alerted of this error/problem?
[Galaxy S 4 i9505 Original Android Development] benlm72:
cm13 kernel with kexec patch

Hi all,

Does anybody know if a kernel for cm13 with kexec exists ?
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
I use "dual boot app" with no issues with cm13 or AOSP 6.0.1 MM
[Galaxy S 4 i9505 Original Android Development] Technical:
Me too. They use different methods of running dual/multi boot.
[Galaxy S 4 i9505 Original Android Development] Technical:
I've tried to install a ROM from a nandroid and got the following error:

Then the "incomplete" ROM is deleted and I can't install in the 2nd partition (ext4) of my sdcard.

Can anybody help?
[Galaxy S 4 i9505 Original Android Development] Xenotrumpet:
Sorry bud, MultiROM has been outdated for quite some time now. Don't know what happened but it needs some fixing for use with Android 5.1.1+ ROMs.
[Galaxy S 4 i9505 Original Android Development] iPAQ 6515a User:
To the OP. Is there any chance to revive the project? An update to 3.0.0.0 would be very welcome
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
This project never died up to now, i was just waiting for news in the upstream. MultiROM v33 with TWRP 3.0.0 are coming soon, the biggest update will be full support for Marshmallow ROMs. :)
[Galaxy S 4 i9505 Original Android Development] iPAQ 6515a User:
Yooopppeeeee
[Galaxy S 4 i9505 Original Android Development] irshad12497:
Any MULTIROM MOD WHICH IS WORKING FOR SAMSUNG NOTE 2 N7100.
[Galaxy S 4 i9505 Original Android Development] AmyClaraRose:
No its not a universal app it only supports very few devices
[Galaxy S 4 i9505 Original Android Development] mephisto20:
hi guys,

is it possible to say when v33 will be available for galaxy s4 ?

I have seen unofficials for various devices.

Please don´t feel rushed ... I would just like to know if it is a matter of days or weeks or months as I have to decide wether to use dual boot or wait for multirom.

i definitiely prefer multirom.

thanks
[Galaxy S 4 i9505 Original Android Development] Gerxp:
I am waiting patiently. :p
[Galaxy S 4 i9505 Original Android Development] jimbomodder:
Never been able to get a working gapps on a secondary ROM, any ideas?
[Galaxy S 4 i9505 Original Android Development] Officer_Dale:
Has MultiROM 33 been released yet?
[Galaxy S 4 i9505 Original Android Development] jimbomodder:
Not yet

Sent from my SM-G903F
[Galaxy S 4 i9505 Original Android Development] vbajs:
Will MultiROM work with MM ROMs or only LP ROMs?
[Galaxy S 4 i9505 Original Android Development] jimbomodder:
Current version is Lp only, they are working on V33 which will work with MM roms too

Sent from my SM-G903F
[Galaxy S 4 i9505 Original Android Development] benlm72:
Hi,

For me Multirom works with MM roms. I've installed JDCTeam CM 13 as primary and CM12 and AOSP 6.0.1 as secondary roms. The pb I meet is that I can't install the roms directly as secondaries : I have to :

- backup my "true primary" rom

- install my "future secondary" rom as primary

- backup this temporary primary rom

- restore my "true primary" rom

- restore my "future secondary" rom as secondary with TWRP multirom moded

A little bit complicated, but it works for me !
[Galaxy S 4 i9505 Original Android Development] Elfik123:
Antares One tell me when to wait for the update to version V33
[Galaxy S 4 i9505 Original Android Development] fanfzero:
How can I uninstall the "multirom" file?
[Galaxy S 4 i9505 Original Android Development] Alexander Glogger:
Got a question. Would it might be possible to port this for the Gt-i9515 (S4 Value Edition) without that much work since this devices seems very similar to the normal S4.

I would welcome your response, Alex.
[Galaxy S 4 i9505 Original Android Development] yfriday14:
Is Android Marshmallow 6.0.1 compatible patched kernel available for i9505?
[Galaxy S 4 i9505 Original Android Development] ckvisme:
#multirom4thewin

I've had multirom on my m8 for over a year now, and have used it on this jfltespr.

Anyway I've also helped test MultiRom b4 and if you need/want help testing please let me know.

BTW the upsteam updates are brilliant it's my favorite MOD I've ever used :highfive:
[Galaxy S 4 i9505 Original Android Development] mephisto20:
I am afraid that this project is dead. That´s a pitty.

Maybe anybody can give me a hint how to realize dual boot on S4 with Android 6 (Marshmallow)-Roms ?

Thanks guys !
[Galaxy S 4 i9505 Original Android Development] benlm72:
I manage to make it work for my MM rom, see my post #975 if it can help !
[Galaxy S 4 i9505 Original Android Development] naeem_0310:
my primary rom is: lollirom 8.0

my second rom is :jdc 5.1.1

when i want to boot second rom it's goto recovery?!?!

what's wrong?

sry for my bad english.
[Galaxy S 4 i9505 Original Android Development] JoshDaWhite:
[MENTION=5464206]AntaresOne[/MENTION] ,have you thought about another update since twrp 3.0.0 is out?No matter what I tried,K couldn't get multirom working.Will you make another "after 6 months update" ?
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Of course, got some time to spend on this for tomorrow. :)
[Galaxy S 4 i9505 Original Android Development] eddloschi:
Can't boot any secondary room

Hi

I installed MultiROM and managed to properly install and boot PA 4.6 Beta 2. But then when I tried to install SlimSaberKat I got an error. Now every ROM that I install gives me the same error when I try to boot it, even the previously successful PA.

I already tried to remove the multirom directory, reflash multiromzip, reflash the kernel (Alucard 2.7.2a) and inject curr. boot sector. None of these helped.

So right now I can only boot to the primary ROM.

I attached the error screen presented as well the latest log from a failed boot attempt
[Galaxy S 4 i9505 Original Android Development] davidwilson83:
Did you select Inject boot.img for the secondary ROM? That needs a patched kernel as well as the primary ROM.

Dual booted Dirty Unicorns I9505
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
[MENTION=5963463]eddloschi[/MENTION]

Reinstall MultiROM zip to be sure

Flash again Alucard kernel

Under Advanced>MultiROM select "Inject curr. boot sector

Add a ROM and be sure that Share kernel with primary it's on Don't share

Reboot and voilà

:)

[MENTION=4603975]daveyannihilation[/MENTION]

Dave, don't forget that this MultiROM isn't the old one like Oblikas

So, you need kexec-hardboot patched kernel only in primary ROM, as wrote in red in 3rd post :p

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] davidwilson83:
Whoops. :) So I don't need to select Inject boot.img after installing secondary ROM? all I have to do is flash ROM and that's it? Well I feel silly :silly:
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Exactly, you need only to flash secondary ROM :)

Nothing else, and just select "Inject curr. boot sector" if MultiROM menu isn't showed at boot

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] eddloschi:
So I did it and was able to install ParanoidAndroid again. But unfortunately SlimSaberKat caused the same issue again, even if installed first after these steps. I'll experiment more next days... maybe it's because my data partition is f2fs. But it's strange how this SlimSaberKat issue could affect every subsequent ROM installation.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Hmm... May be data partition formatted in F2FS can be a problem if MultiROM can't recognize well that partition (by original things) but I wouldn't bet too much. Mine is ext4 and I don't have any problem at all booting SlimKat, SlimSaberKat is just the same ROM compiled with the SaberMod toolchain

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] eddloschi:
I had no problems with SlimKat too, so besides being the same room just compiled differently SlimSaberKat seems to be causing the issues.

Anyway, thanks for the help! When I format data back to ext4 I'll post here the results
[Galaxy S 4 i9505 Original Android Development] robygt:
Ciao, Cyano stock kernel supports k exec module, I didn't know that, good!
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Kexec is not a module :silly:

The hardboot patch is supported also by stock CM kernel, I saw days ago but forgot to write in 3nd post :)

Inviato dal mio GT-I9505

EDIT: Now it's wrote on 3rd post
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
New update!

MultiROM:

ROM boot from external SD (MicroSD card) is now supported

TWRP Recovery:

General update (branch master)

Removed "Share kernel" option

ROM Installation to external SD (MicroSD card) is now supported

Uninstaller ZIP added back and now working

Now you can load ROMs from MicroSD too!

MicroSD card in ROM installation is dev/block/mmcblk1p1

To remove MultiROM now, just flash multirom_uninstaller.zip

Downloads in post #3

MultiROM Manager support soon available!

:cowboy:
[Galaxy S 4 i9505 Original Android Development] robygt:
Sei un grande! Thanks so much, you are great!
[Galaxy S 4 i9505 Original Android Development] FeyoMx:
Sorry. Link fixed. Great work.
[Galaxy S 4 i9505 Original Android Development] robygt:
Twrp recovery and multirom boot menu work perfectly!