yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Im_Gumby:
Was attempting to take the plunge into f2fs, only wanted to use the modified TWRP to do so, after installing it, I get the bad kernel error listed in the OP. Decided f it... I'll go back to the original recovery. Odin flash for 2.7.1.0.tar fails see below. Then I try to use the md5 file associated with that, sends ODIN into thinking land forever, never finishes so I can install. Trying the same thing with 2.8.1.0 despite the disappearing backups... same deal.

<ID:0/003> Added!!

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> recovery.img

<ID:0/003> NAND Write Start!!

<ID:0/003> FAIL! (Auth)

<OSM> All threads completed. (succeed 0 / failed 1)

Is there an ODINable file out there for TWRP that will undo the modified version?

Is there an ODINable file out there to fix the Kernel issue so it'll boot into recovery again?

Despite the kernel error when booting into recovery, I was still able to boot normally. I was able to reinstall recovery via the TWRP app.
[Galaxy S 4 i9505 Original Android Development] darkassain:
Finally got a it running with TW as primary and Carbon as secondary (in a SD card no less)

The thing is dont use TW too often and i only have 16gb (of which i really only have 8ish available) so internal memory is a great issue to me, so i ask is there no way to have tw in a secondary on the sd card?

Not to mention the added pain of not being able to use the sd card if booting from it (understandable really)

Anybody have a TW rom that boots as a Secondary?

I have tried 3 TW's roms and havent had luck booting them (stock NH7 rooted deodex knoxless, and stock nb4 along with stock mdl i believe, either booting googy or alucard kernel)

Best case is booting from sdcard, although i will take booting from internal as a secondary (JB or KK doesnt matter as long as its TW Tmobile based) at this point (ill slim it down so i can somehow manage :p),

as downloading almost 5gb of roms that have all failed is disheartening to the say the least
[Galaxy S 4 i9505 Original Android Development] magikmichael:
Is it possible to flash latest lollipop rom from antaresone with multirom? Because i get errors when i want the rom to boot? Or do i have to wait for a new build?
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
The problem is that we do not have the option to wipe system in multi boot ATM. I think I found a workaround but haven't fully tested yet as I boot cm12 in primary.

Use zip installer to update multi boot ROMs once you are in them, you can then install ROM updates or whatever you like directly from the ROM, and the best part is you can choose to wipe system at the same time therefore bringing that option back.

Of course this won't help if your ROM is already borked in multi boot. Only thing I can suggest is to delete and install from fresh.

I was messing around with AICP L the other night and this workaround worked.

Like I said, I'm not sure about AntaresONE's cm12 so give it a go and let us know if it works.

Full clean install is recommended anyway moving from 5.0.0 to 5.0.1 ;)
[Galaxy S 4 i9505 Original Android Development] magikmichael:
I removed the old cm12 and flashed a fresh installation. But it still doesnt work. Will wait for antares to fix this.
[Galaxy S 4 i9505 Original Android Development] fartlec:
i had the same problem starting from nightly 2611. i solved flashing alucard kernel after flashing the rom

edit

updating the rom itself is another issue, though
[Galaxy S 4 i9505 Original Android Development] magikmichael:
Yep flashing alucard does solve this. But now i have the wakeup with back\menu keys... Will keep this for the moment. Tried ktoonz kernel but that one wont boot.
[Galaxy S 4 i9505 Original Android Development] peppe130:
Hi [MENTION=5464206]AntaresOne[/MENTION] :) Are you going to patch GoogyMax 1.2.2 kernel?
[Galaxy S 4 i9505 Original Android Development] stanguay:
TW GoogyMax 1.2.2 kernel is patched.

I have TW GoogyMax 1.2.2 kernel on on primary rom and Multirom work great.

Maybe I misunderstand your question ?
[Galaxy S 4 i9505 Original Android Development] peppe130:
I asked because I didn't see the Googy 1.2.2 in third post :)
[Galaxy S 4 i9505 Original Android Development] aymelis:
"Shutting down MultiROM to avoid data corruption" error

Hi guys,

When I try to boot my secondary ROM (cm12 20142103) I get the following error message :

"An error occured.

Sutting down MultiROM to avoid data corruption.

Report this error to the developper!

Debug info: /sdcard/multirom_log.txt

Press POWER button to reboot."

How did this happen :

1- I first installed multiROM and an older version of CM12. All was going fine, CM12 was fast and pretty, but no network and no sdcard.

2- I had deleted my original cm12 .zip file to free some space on my sdcard, and unfortunately I am not sure which build it was.

3- I donwloaded the latest available to date : 20141203 and installed it over the previous install with no wipe (as a trial to avoid re-installing my apps) : cm12 would not boot...

4- I then tried the cleaner way : TWRP/Advanced/MultiROM/List ROMs/select cm12/wipe data + dalvik + cache (I noticed there is no way to wipe /system of the secondary ROMs in MultiROM's menu) and then Add ROM/Android/Don't share/Internal memory/Next/ZIP file/cm-12-20141203-UNOFFICIAL-jflte.zip : says it installs ok, but same MultiROM shut down error.

5- I booted on my primary ROM (4.4.2 Echoe ROM v20), went to MultiROM app/ROMs/cm12-20141203-UNOFFICIAL- and rebooted. Same MultiROM Shut Down error... but worse : I was not able to boot to my Primary ROM anymore !...

5- Rebooted to TWRP, Restored my Primary ROM backup.

6- Booted to my Echoe ROM : worked.

7- Rebooted to TWRP to try removing and re-insatlling MultiROM (installed multirom-uninstaller.zip) + reboot : uninstall successfull.

8- Re-installed MultiROM from TWRP again.

9- Re-installed CM12 : same thing...

I also tried to send the multirom_log.txt file to AndtaresOne (PM) but could not find how to attach the file... :D

Thanks for any help,
[Galaxy S 4 i9505 Original Android Development] stanguay:
I read thst he last version of cm 12 (20141203) is not compatible with multirom yet.

Envoyé de mon GT-I9505 en utilisant Tapatalk
[Galaxy S 4 i9505 Original Android Development] nds850:
By switching to primary I'm able to boot.
[Galaxy S 4 i9505 Original Android Development] fartlec:
i have it as secondary, just flashed alucard kernel after flashing rom
[Galaxy S 4 i9505 Original Android Development] wingg:
+1

//->>
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Guys, if you use Alucard kernel with latest CM12 builds works
[Galaxy S 4 i9505 Original Android Development] frorgaba:
Multirom on Galaxy S4

Hello,

I have install Multirom and all the files delivered with it.

I can boot in recovery Multirom TWRP 2014-11-26 (v2.8.1) to instaal a second ROM but I always get this message

E:error executing updater binary in zip "/tmp/mr-update.zip"

what is wrong?

thank you
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Hello,

Try to download again ROM's zip, seems corrupted

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] `SBR`:
+1...

Also I can install the zip file as primary and dual boot patcher.. without any issues.

Only multirom throws the above error in latest builds. .
[Galaxy S 4 i9505 Original Android Development] aymelis:
Hi fartlec, thanks. Unfortunately flashing the alucard kernet for TW did not help : same error...

Stanguay, Do you know what's the latest cm12 version compatible with multirom ? That might be the reason why my previous cm12 install did not have this issue. However I am surprised: I thought nothing in the ROM was special to be compatible with multiROM (even though I know some ROMs seem not to be compatible).

AntaresOne, thanks but unfortunately I retried with latest cm12 to date (20141205) with the same result ("Shutting down MultiROM to avoid data corruption.").

However, I could remember which version I originally installed successfully (20141117). I re-installed it, and this was successful, but still no PIN code asked (as if no SIM card inserted or airplane mode) and external sdcard that appears empty. Any more ideas ?

Thanks guys ;)
[Galaxy S 4 i9505 Original Android Development] fartlec:
alucard for lollipop. first download on alucard's page

you have to select cm12 from rom list, then flash zip. select alucard.

not alucard for tw either on top of tw or (worse) on top of cm12
[Galaxy S 4 i9505 Original Android Development] aymelis:
Hi fartlec, my primary ROM being a TW (Echoe v20 - 4.4) I thought alucard for TW was required. Indeed I tried what you suggested: went to alucard's xda page, downloaded kernel for 5.0 -> primary ROM does not boot anymore (there is not alucard for 5.0 TW yet). Flasing back to Kernel-Alucard-V2.3ga For 4.4 TW version.

Edit: OK, primary ROM back to Alucard v2.3ga for TW, and flashed Alucard for lollipop for secondary ROM. Primary booting, but some FCs... Secondatry (cm12 20141117) booting but still not asking pin code. Going to Parameters I can read "Baseband: Unknown"... Shall I flash a baseband separately ? Isn't it supposed to be installed with cm12 zip ? I think there is no means to flash a modem throught the recovery on i9505 (Odin only). Is there any means to flash a specific modem for multiROM secondary ROM and keep old modem for primary (internal) ?

Also, I am on the old bootloader...

Edit 2 : Just saw a new upload from Antares (cm12 20141206) : now boots, asks pin code and accesses my external SD card. All fixed !!! Antares Updater crashesthough, but excellent progress :)

Thanks
[Galaxy S 4 i9505 Original Android Development] fartlec:
just for information. tried zip installer to wipe system. no good, but good try
[Galaxy S 4 i9505 Original Android Development] VanGolfer:
Very annoying issue: 2nd rom reboot, regardless power off (then power on), normal reboot (suppose to go to the multi reboot interface), or recovery reboot, always go to recovery . Primary reboot works well as it should be. The good news is both rom boots successfully.

Primary rom: AOSP KK 4.4.4

2nd rom: CyanogenMod 12 unofficial by AntaresOne

both using latest alucard kernel accordingly

ext4 format [MENTION=5464206]AntaresOne[/MENTION]: could you please advise anything I can do to fix it?

Thanks!
[Galaxy S 4 i9505 Original Android Development] Technical:
You're not alone.
[Galaxy S 4 i9505 Original Android Development] planetf1:
I have gpe 444 as primary. I seem to be able to install cm12 builds as secondary along with alucard kernel and they boot, and work (1205)... But flashing (install zip) a new build (1206) and reflashing the kernel results in the secondary not booting (the multirom shutting down screen).

Any ideas. I wonder if it might be related to not reformatting /system but I can't see how to do this for the secondary rom

Does anyone have a cm12 update process that is working?

I had the same from 1203 to 1205
[Galaxy S 4 i9505 Original Android Development] fartlec:
no.i tried as someone suggested with zip installer- you can sipe system and flash from within the rom. but no luck. i suspect therre is a problem with modified twrp. only way with cm12 as secondary is fresh install. personally, i flash a new update as third rom and restore data/data. if there are no problems in a day or two, i cancel the previous rom and keep that. this is the beauty of multirom. no backups to restore if not satisfied
[Galaxy S 4 i9505 Original Android Development] planetf1:
Ok thanks for confirming. Can you elaborate on how you migrate the data from one rom to another -- do you mean the entire /data filesystem?

One thing I did notice is the first time I installed a CM12 rom I remember getting prompted for the virtual disk size to use... subsequently I've not seen this be prompted. I've also had to do some clearout on the internal rom, but even then I'm not sure I'll fit 2 additional ones -- any news on external sd support?

I'm mostly doing this until I feel more comfortable with the state of Android L - whether CM12, or a samsung shipped GPE. Right now the BT wakelock, and some black screens are preventing me going full out on CM12
[Galaxy S 4 i9505 Original Android Development] Tobirexy:
Edit: fixed

---------- Post added at 04:59 PM ---------- Previous post was at 04:44 PM ----------

Hello!

When i want to update the primary rom do i have to do "inject curr. boot" after flashing ?

Send from my GT-I9505. Sry for my bad english!
[Galaxy S 4 i9505 Original Android Development] Gerxp:
For CM12 to work with Multirom you need Alucard Lollipop, but also TWRP by AntaresOne.

Here is the link:

https://www.androidfilehost.com/?fid=95784891001609549
[Galaxy S 4 i9505 Original Android Development] fartlec:
i think it is simplier if you just copy the data/app folder with a file manager with root access. and then. copy this back in the new rom. this give you back the apps (even if i think google backup is much more practical).

in data/data there are the data saved by the apps. if you want, you can copy the desired ones and then paste in the new rom (these are settings, cache, etc). this is basically what titanium backup does. i use it for some apps, such as email
[Galaxy S 4 i9505 Original Android Development] Tobirexy:
Hello! I tried to install CM 11 on sd card but i got an error. Should I send you the log ? [MENTION=5464206]AntaresOne[/MENTION]

Send from my GT-I9505. Sry for my bad english!
[Galaxy S 4 i9505 Original Android Development] Tobirexy:
Hello! I tried to install CM 11 on sd card but i got an error. Should I send you the log ? [MENTION=5464206]AntaresOne[/MENTION]

Send from my GT-I9505. Sry for my bad english!

Send from my GT-I9505. Sry for my bad english!
[Galaxy S 4 i9505 Original Android Development] ComputerNmyPocket:
I'm also having the issue where after restarting or shutting down from secondary rom (cm11) it boots into twrp automatically. My first time installing multirom about a week ago I didn't have this problem. It worked fine, multiboot menu popped up on every boot. But I wasn't sure multirom was for me so I flashed the uninstaller and reverted to my old twrp via flashify and restored my touchwiz nandroid. Later wanted to give multirom another go so installed it again, but then got this annoying problem where it boots into twrp automatically after exiting the secondary rom.
[Galaxy S 4 i9505 Original Android Development] ComputerNmyPocket:
Could anyone tell me a Primary / Secondary Rom combination you're using that doesn't have the problem of automatically booting into recovery after shutting down from the secondary rom?

I'm using;

Primary: Insane Kit Kat 4.5

Treid both alucard and googymax kernals

Secondary: CM11 12/06 Nightly

I'm on SGH919 Tmobile device.
[Galaxy S 4 i9505 Original Android Development] nds850:
I don't mean to be repetetive but I'm not able to boot some ROMs at all. (This one for example: http://xdaforums.com/showthread.php?t=2544474)

In the MultiROM menu that pops up when I start the phone where I can see all ROMs I have installed. When choosing to boot one of these the phone reboots immediatelyand I can see the Samsung logo and the blue text in the corner that says booting to recovery. Now the thing is only some of the ROMs I have tried boots correctly after this and with others I enter recovery and I'm not able to boot them.

You mentioned that the RAM needs to cleared but how do I do that after choosing the ROM I want? Because the phone reboots directly after I choose the ROM. What am I missing? I must be doing something wrong?

Thank you
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
RAM needs full reset (+- 10 seconds) after power off before power on again to let the device don't boot in recovery itself. What kernel are you using in that ROM? Stock one that came together?
[Galaxy S 4 i9505 Original Android Development] nds850:
Yes I'm using the stock kernel that came with the ROM.

I'm also unable to boot these two:

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

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

I have never been able to boot any of those but MahdiROM and DirtyUnicorns work perfectly every time. :confused:
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Hmm... You install the ROMs, then you reboot and when you load them, your device reboots in recovery right? Try to install 3rd party kernel (don't flash the zip but add boot.img). Installing modules doesn't matter for now since you're just testing.

Custom kernels for secondary ROMs

As everyone knows, any custom Android ROM comes with a default boot.img inside (it's the kernel). When you install a secondary ROM in MultiROM, that boot.img is modified by some scripts and installed into /data/media/0/multirom/roms/NameOfROM instead of device's EMMC partition reserved for kernel. When you try to install a custom kernel into a secondary rom by Advanced>MultiROM>List ROMs>NameOfROM>Flash ZIP it's not modified and installed directly to kernel's EMMC partition instead of multirom folder. This gives error while trying to boot secondary ROMs after, so to install custom kernels in secondary ROMs follow that procedure explained above.​
[Galaxy S 4 i9505 Original Android Development] nds850:
Yes that's right.

Used the 3rd party kernel but it was unsuccessful. With the Google Edition ROM I got an error message and a log file. View attachment 2923463

Don't know if there is anything useful in it. :silly:
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
[MENTION=5305956]nds850[/MENTION]

For Google Edition ROMs remember to use GE kernel

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] gsmyth:
So do I need to power off, wait for 10 secs for ram to clear, then power on and boot into secondary rom? I've installed everything and can boot to the multirom menu but can select 'cancel', to switch roms.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
You can disable autoboot by booting into recovery then Advanced>MultiROM>Settings>and disable autoboot.

You need to wait 10 seconds before power on again only when you power off your device (i.e. never select "Reboot" on Android but only "Power off", otherwise it will reboot in recovery instead of MultiROM menu)

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] nds850:
Yes. Still not working for me unfortunately.
[Galaxy S 4 i9505 Original Android Development] gsmyth:
Got it thanks!

Works perfectly, this is the greatest functionality to have in my opinion as you can run all of your favourite roms and still keep your stable primary ROM untouched. Thanks again do your work.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Tomorrow I'll try that ROM myself

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] nds850:
Thank you so much for taking the the time to help me with this. I really appreciate it!
[Galaxy S 4 i9505 Original Android Development] Okaham:
OP, could you please also make a exec-hardboot compatible Android 4.2.2 AOSP Kernel? I'm trying out ColorOS, it's based on Android 4.2.2. Thanks!
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Just install ColorOS as secondary ROM! Kexec patched kernel is needed in primary ROM, optional in secondary. It's no longer as other MultiROM in other thread where you need kexec patched kernel in both ROMs. This mine it's updated, fixed and fully working

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Update available

Changelog:

Device source: Clean and update init devices

Device source: Add volume keys init (now you can select ROM/tabs also with volume keys)

Uninstaller package: fixed execution on other jflte devices

For who tries MultiROM for the first time, install the latest update.

For who already has MultiROM, this update is optional but suggested.

For downloads look in post #3

Custom kernels section for secondary ROMs update planned for tomorrow.
[Galaxy S 4 i9505 Original Android Development] Okaham:
Hi, I'm having an issue here booting my secondary ROM...

Recovery does not allow me to install it into the SDCard? Internal is the only option...and since ColorOS is HUGE, the recovery had to slim it down or something...but see now here's my problem. When I try to boot into ColorOS, the Galaxy S4 splash logo appears with a "Recovery booting" in blue on the top left (as if it were booting into recovery)...and then it boots into another mode saying that MultiROM encountered an error? TIA
[Galaxy S 4 i9505 Original Android Development] bdog2015:
Same happened for me with ColorOS. Not sure what the problem is.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Do you have enough space in internal memory?

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] bdog2015:
Yes I had plenty of space when I tried it.
[Galaxy S 4 i9505 Original Android Development] Okaham:
+1 with the post above, I also had plenty of space...but doesn't this mod have the option to install ROMs onto the SDCard as well..?
[Galaxy S 4 i9505 Original Android Development] Mystique:
i9095G Google Edition Device

Recovery install fails..
[Galaxy S 4 i9505 Original Android Development] XxSHaDoWxSLaYeRxX:
Any update on jflteatt and jfltevzw support?
[Galaxy S 4 i9505 Original Android Development] Alipk52:
Nevertheless your work is absolutely brilliant, I appreciate it from the deep of my heart, you've made flashing a real ease for us and we don't have to compromise our primary ROMs in order flash new AOSP builds! Thanks dev..you rock!
[Galaxy S 4 i9505 Original Android Development] zzzijo:
I installed latest modified recovery and it's amazing .. but I have one question .. I connect USB flash drive with USB-OTG cable but it won't mount when I'm in recovery mode ..

Every time I press USB-OTG it vibrates but it won't mount .. Can you tell me how can I mount flash drive ??

Thanks !!! :D
[Galaxy S 4 i9505 Original Android Development] todivefor:
I am also running Sprint variant (SPH-L720), but I am running CM11-M12. Can I just use one of the 2 list CM kernels (Alucard AOSPv2 v1.4ocm or

Googy-Max3 CM v1.1.9) or just leave as is with the stock kernel that came with M12 ROM?
[Galaxy S 4 i9505 Original Android Development] popliuc:
Error every single time and whit 5.0.0 GPE it enters recovery and whit yours 5.0.1 black screen whit some logs

https://mega.co.nz/#!JRN3kZTT!CPvuBGSejVuauNPIJTzJVbCpdYSIzB2purGzZchhkH8
[Galaxy S 4 i9505 Original Android Development] todivefor:
I decided to just try it. I am running CM11-M12 with kernel that came with CM11. Multirom did not have the "doesn't have kexec-hardboot patch!" in red letters, but has "has kexec-hardboot patch" in green, so I thought I was good to go. Installed modified TWRP. Everything boots, reboots, etc. and works fine. I tried installing a TW rom I have as secondary (I installed this from a nandroid backup). That all seemed to work. If I boot my secondary rom, I am taken to recovery. From within TWRP|multirom I select my secondary and on reboot, I get the message that to prevent damage multirom has stopped, report to developer. Any idea what could be wrong? Log attached: https://dl.dropboxusercontent.com/u/3407584/multirom_log.txt

edit: Tried shutting down for 10 seconds, then reboot, got "booting myrom", then went to recovery.
[Galaxy S 4 i9505 Original Android Development] eilex17:
please fix multirom for gpe 5.0 support....
[Galaxy S 4 i9505 Original Android Development] RDoughBoy:
I just opened the MultiROM app and it says there's an update for MultiROM (v30b). When I press install, it goes to recovery and installs but when I go back to the app, it says I didn't update.
[Galaxy S 4 i9505 Original Android Development] Okaham:
Is it just me or does MultiROM not work with any of the Android L ROMs?
[Galaxy S 4 i9505 Original Android Development] popliuc:
+1

Same here
[Galaxy S 4 i9505 Original Android Development] bertodex:
and same for me ...

maybe it has been already asked, but is it possible to boot last Lollipop GPE rom ?

thx ! :good: