yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Active Original Android Development] spegelius:
Did you install the TWRP? I haven't tried with CWM. Error 7 sounds like old recovery or something... not sure (had those problems with AOSP updater and some versions of CWM at some point).

I don't use dualboot, best not to mix it with this. Actually i think dualboot break multirom (need to flash multirom again after dualboot rom flash) and vice versa.

Haven't tried nandroid restore with MultiROM but i think it should be possible? Also if i got this right, if you restore your nandroid as an multirom installation, you'll have two instances of same rom; the main rom and the one installed from nandroid.
[Galaxy S 4 Active Original Android Development] ZeroZorro:
Just installed TWRP with Odin and after that MultiROM and it works...cause SuperWizCyan works great i'll leave it as Primary ROM for now and will install CM12 and StockROM on my SDcard...to be continued!
[Galaxy S 4 Active Original Android Development] spegelius:
Hmm , i wonder if the latest CM12 installer works with MultiROM since it has custom partition format script which allows it to detect f2fs/ext4. Make sure you have backups before trying.
[Galaxy S 4 Active Original Android Development] ZeroZorro:
Okay, i even moved my Nandroid Backup to my PC before proceeding.....you can never be too careful!

Installing CM12 to my SD-card now.....

* I have to keep the screen 'alive' while installing CM12 with MultiROM, otherwise when the screen goes black...well i had to reset the phone....

* 2nd attempt it seems to work, no errors and after pushing the Reboot-button screen goes black again...> reset

* I can see the Boot-screen but touch-screen not working so trying to cancel Boot from Internal doesn't work so it auto-boots... >> found it ... Use Volume Buttons!

* But: i can see that CM12 is listed as 2nd ROM ;)

* So now i have to find a way to get into the menu to choose ROM to boot

And... how do i install the GAPPS for this 2nd ROM? >> found it...you can do it within TWRP>MultiROM #cool

Also installed MultiROM manager apk hoping it would give me boot options but (obvious) it doesn't work on 9295 for now.

For testing purposes i set the 2nd ROM to boot in MultiROM setting (trough TWRP)....it seems that the black screen is a problem of TWRP, not MultiROM

Oh well... booting CM12 doesn't work for now...will post multirom_log soon
[Galaxy S 4 Active Original Android Development] ZeroZorro:
See attached multirom_log,txt
[Galaxy S 4 Active Original Android Development] spegelius:
In the log there was mention about kexe-hardboot failing... Is WixCyan a TW rom? Is the kernel in it KEXEC-HARDBOOT patched? That patch is in CM11, CM12 and AOSP (and other CM11 derivates) since their kernels are the same base. For TW, you'd need some modified kernel.
[Galaxy S 4 Active Original Android Development] 6783:
So it works only for aosp and cm roms?
[Galaxy S 4 Active Original Android Development] spegelius:
No without patched kernel. It might work if the TW rom isn't the first rom, but instead a multirom.
[Galaxy S 4 Active Original Android Development] ZeroZorro:
Update: i'm there ;)

Now i have SuperWizCyan as Primary (internal) ROM and SammyStockTW as secondary on my SD-card

I made it harder then needed cause i forgot to make a Nandroid with TWRP instead of CWM so i had to re-install CWM to get my 1st ROM back.

(If you really wanna know what i did, please ask, for now i will spare you the details ;) )

For now, as you can see in the previous post, CM12 doesn't work for now....we'll wait and see and do some more testing!

But hey, it worked and so far so good.....1 thing i didn't read about is if there i going to be an option of app-sharing like DualPatcher does. App-sharing with data-sharing would be even better for my banking apps and Whatsapp to work on both ROM's.

Thanks again [MENTION=3876105]spegelius[/MENTION] !
[Galaxy S 4 Active Original Android Development] spegelius:
Great, apparently there's KEXEC_HARDBOOT patch somewhere there or it's not needed :).

For CM12, another installer zip is needed, which has the normal /system format and mount commands. I'll see if i get it done.

No app sharing, at least automatically. In the I9505 thread someone suggested moving the apps/data to sdcard or something...
[Galaxy S 4 Active Original Android Development] spegelius:
Oh and the problem with screen timout is known, didn't remember to mention it. Screen timeout can be disabled in Settings.
[Galaxy S 4 Active Original Android Development] O-T:
Interested in replace CWM 6.0.5.0 with TWRP. Not sure if ready to use the rest of MultiRom setup yet. Is TWRP stand-alone capable of replacing CWM in a single ROM setup?
[Galaxy S 4 Active Original Android Development] spegelius:
Yes, TWRP works without MultiROM. There are few checkboxes, like Inject MultiROM that need to be disabled when installing roms for example, but basic stuff works without multirom.
[Galaxy S 4 Active Original Android Development] O-T:
[MENTION=3876105]spegelius[/MENTION]

Ehhm, small correction for OP Installation - Modified Recovery:

It's a tar-file on your Gdrive, no zip-file for installation by recovery multirom_twrp_20141204_1838.tar.md5

Not tried Mobile Odin yet but I know PC Odin swallow tar-files.

About warning TWRP format of /data also include /sdcard. /sdcard is soft or hardlinked(?) to /data/media/0

Can the relationship between fstab of TWRP and mount points of S4A be a good place to start tracing, or is this all fuse managed?

Recovery.log of CWM 6.0.5.0 got me thinking:

W:Unable to get recovery.fstab info for /sdcard during fstab generation!

Can mount points be somewhat off? (at least for CWM) . The reason is that delete dalvik cache take less than a microsecond, as if it has not been executed. Delete cache and zip install has been good.

Will update to TWRP using Odin from PC and follow up.
[Galaxy S 4 Active Original Android Development] ZeroZorro:
Yes WizCyan is TW ROM and should work....?

see: http://xdaforums.com/galaxy-s4-active/development/rom-super-wizcyan-s5-style-t2874424

I'll ask [MENTION=5266778]JASONRR[/MENTION] if he can implement KEXEC-HARDBOOT in next version.

I have to do some clean install cause i can't restore my Nandroid Backups (all CWM-related). :crying:
[Galaxy S 4 Active Original Android Development] spegelius:
Yes it's tar.md5. Hmm, copied the installation stuff from AntaresOne's thread, didn't proofread it :rolleyes:... I'll propably add zip variant also someday.

About sdcard format: i noticed this when formatted /data as f2fs; my sdcard was empty and it was also formatted as f2fs. There's a TWRP build variable RECOVERY_SDCARD_ON_DATA, which is 'true', i'm thinking about checking that. Links of any kind shouldn't affect partition formatting (hopefully...). And fstab shouldn't affect what the format does, it should first scan the existing partitions and just format those.
[Galaxy S 4 Active Original Android Development] spegelius:
Well if the MultiROM is working, i.e. you can install and boot multiple roms, dunno if it's actually needed... kexec patch needs new kernel build. It can be done since KK kernel sources are available.
[Galaxy S 4 Active Original Android Development] mythi:
good work [MENTION=3876105]spegelius[/MENTION] with booting twrp again :) it was giving me a black screen what ever i did :D , you're awesome .
[Galaxy S 4 Active Original Android Development] spegelius:
Thanks, it's Tasssadar's work mostly, but good addition to Active. I have another build coming which should disable the screen timeout. I haven't studied the code to see if the black screen death is fixable.
[Galaxy S 4 Active Original Android Development] Devo7v:
I'm about to install this but just want to confirm I'm doing everything properly so I don't mess anything up. I'm currently using CM11-2014-12-09 with CMW v6.0.5.1, so I know I need to install the modified TWRP before I do anything else. I'm planning on using the steps below to get everything set up, so please let me know if I'm doing anything wrong.

Download multirom_twrp_20141204_1838.tar.md5 from the second post and flash the modified recovery to the phone using Odin in the PDA slot.

Next flash multirom-20141203-v30-UNOFFICIAL-jactivelte.zip through the recently installed TWRP

Once completed you will have the modified TWRP installed and MultiROM support enabled.

One thing I'm not sure about is whether or not the default CM11kernel has the necessary kexec patches enabled. If not can somebody point me to a kernel that does so I can use CM11 as my primary ROM?

I did install the MultiROM Manager app and it says that the i9295 is not supported, as expected, so there are no options available within the app. Will there be an effort in the future to add the i9295 to the list of supported devices so that installation will be easier?

I can't wait to start using this and testing out other ROMs. Coming from the i537, this seems to be a much less restrictive version of SafeStrap. Keep up the good work, I can't wait to see where this goes.
[Galaxy S 4 Active Original Android Development] spegelius:
CM11 has KEXEC_HARDBOOT patch and its enabled. MultiROM manager: possibly. Haven't had a look into it yet.
[Galaxy S 4 Active Original Android Development] Devo7v:
Thanks, it looks like I got everything working properly. I did run into the timeout bug with TWRP and had to pull the battery to start over. One thing I noticed though is I was making a backup and the screen turned off, rather than pull the battery and start over I decided to let it sit for awhile so my backup could finish. After about 10 minutes the screen automatically turned back on and the backup was finished. I don't know if this helps troubleshoot the bug, but I thought I'd let you know.

Does CM12 work with this? I installed it as a secondary ROM, but it just sits at the boot screen.
[Galaxy S 4 Active Original Android Development] spegelius:
As discussed earlier, CM12 has custom updater scripts for fs format etc. and can;t be patched by MultiROM. I'm actually suprised that installing CM12 didn't format your primary rom... perhaps MultiROM disables formats or something...

I'm planning to release CM12 variant with normal updater scripts, once i get some things worked out.
[Galaxy S 4 Active Original Android Development] Devo7v:
Sorry about that, I must have missed that post. I guess I got lucky, and I'll gladly wait for your update and try CM12 later.

Thanks again for all your work on this, it's great.
[Galaxy S 4 Active Original Android Development] ZeroZorro:
wel....having some big problems inhere....

After some playing around my boot-screen/multirom-screen was tearing heavingly and looks burned-in now.

Another thing is that TWRP touch doesn't work anymore....tried to re-install CWM and even there touchscreen only works 1 time. After that i have to use harware keys (which isn't possible in TWRP)

Did a complete reset and even re-install official firmware trying to get back to point 0 and start over: no luck so far

Does any of the above sounds familiar to you guys or do i have a bricked phone in my hands :crying: ?

Touchscreen works well when booted into OS, burn-in still there.... think gonna leave the battery out for a while....
[Galaxy S 4 Active Original Android Development] Alxoom33:
Anyone know if SCH-I545 is supported?
[Galaxy S 4 Active Original Android Development] spegelius:
Hmm that doesn't sound good. By burn-in, do you mean that colors are wrong or something?

I've had no problems with touchscreen or colors. Did you clean /sdcarc/TWRP directory? There's .twrps file which apparently contains all TWRP settings.

Are you using the KT kernel i uplaoded yesterday?

Hope it revives after a while without battery
[Galaxy S 4 Active Original Android Development] ZeroZorro:
Left my phone overnight with Burn-in tool running, but somewhere my girlfriend pulled the plug (don't ask me why!)

I'll have to retry that tonight but it got already slighlty better, but far from good yet.

Deleted /scdard/TWRP and re-installed TWRP through Odin 3.07 with no luck.

But as it doesn't work in CWM and Aroma-installers also it's not TWRP related i guess. Cause touchscreen works when booted into (any) ROM i really dunno where to start.

I used your KT Kernel yes, i don't think that broke it either.

Another thing i noticed with TWRP. When choosing to reboot it just showed a battery with a circle and after that a battery with (in green) showing how much it is 'filled'. Underneath 4 'charging' dots. I have to press the key on the right side again to start the device. The second screen whith the battery is where i first noticed a lot of 'tearing' of the screen. Hope it will help somehow narrow down the problem....

Oh...and also flashed philz_touch_6.15.4-jfltexx but it ends up with black screen :( .....back to CWM 3.0.4.7 for now
[Galaxy S 4 Active Original Android Development] JASONRR:
Seems to be an issue with the ktoonez kernel. Installed it yesterday morning and had put it on flight mode in the night, the screen was unresponsive on waking up in the morning, had to hard boot with power button to get it working. Again a while ago the screen became unresponsive when left idle for very long. Power & volume buttons were working though
[Galaxy S 4 Active Original Android Development] spegelius:
Alright, thanks for the report. I'll have to do more testing on the kernel. It was running ok for day or so, but i have only wifi connection and not much use since it's i use another phone as main phone.

ZeroZorro: what kind of burn-in test? With KT kernel? Hmm, i wonder how well the thermal stuff works with the kernel... i did some benchmarking, but not a long run with full cpu stability tester so i can't say how the temps react on long run. I also have added some thermal paste on the cpu while i had the phone open during the screen replace so it runs bit cooler. I fear that the symptoms you are descibing tell that the phone has just heated too much... i hope i'm wrong.
[Galaxy S 4 Active Original Android Development] ZeroZorro:
I meant an app that might be able to get rid of the burn-in : https://play.google.com/store/apps/details?id=com.gilonm.burnfix

If the source of problems is the heat then it has taken place while flashing a new ROM: i was trying to install CM12 onto external scdard while giving a little more room to DATA and SYSTEM.

That took a whole lot of time to install and i did it overnight, so maybe there is what created the problem....i really dunno. On the other side: overheating could have something to do with the screen, but not with touchscreen not working in CWM/TWRP/Aroma and still working in normal use?
[Galaxy S 4 Active Original Android Development] spegelius:
Ah ok, i understood that you had left some cpu benchmark/stablity stuff running.... ok. In that case, it shouldn't be heat related. Installing rom doesn't heat my phone more than 51 Celsius or so... and even moving stuff around shouldn't be that cpu intensive.

Well for that burn in stuff, never come across such phenomena.
[Galaxy S 4 Active Original Android Development] spegelius:
New TWRP version, 20141218_215324:

both Odin flashable tar and CWM zip available

merged changes from Tassadar's repo, TWRP version 2.8.20

disabled screen timeout for now. Need to look at the code more to understand why wake up doesn't work
[Galaxy S 4 Active Original Android Development] ZeroZorro:
Have downloaded several times, but keeps saying MD5-hash is invalid?
[Galaxy S 4 Active Original Android Development] spegelius:
Reuploaded, file had been accidentally renamed after md5summing. Should work now.
[Galaxy S 4 Active Original Android Development] walter79:
Found a bug. Phone can t boot if phone is of and charger plugged. Only battery charging animation. I used Samsung 4.4.2 with patched kernel and CM12 as second rom. Booting Android works well without charger.
[Galaxy S 4 Active Original Android Development] Devo7v:
I think that's a bug with the bootloader because I've had that issue since I got my phone, way before I installed MultiROM.
[Galaxy S 4 Active Original Android Development] walter79:
fixable?
[Galaxy S 4 Active Original Android Development] O-T:
ADB or Terminal app command:

getprop ro.bootloader

I9295XXUCNE4

The NE4 bootloader also has issue.

CWM 6.0.5.1 + CM11

I don't have Lollipop.

What is your bootloader?
[Galaxy S 4 Active Original Android Development] 6783:
As I understood it's not the multirom bug. I have installed cm12 without multirom and have same bug. Can't turn on the phone while it charges. So it's lollipop issue.

---------- Post added at 06:31 PM ---------- Previous post was at 06:30 PM ----------

Can somebody help me? I want to have stock and cm12, can someone provide me step by step instruction what should be done for good result. Thank you in advance
[Galaxy S 4 Active Original Android Development] walter79:
1. install Stock 4.4.2

2. install patched stock kernel

3. install multirom twrp

4. install multirom 30 zip

5. install cm12
[Galaxy S 4 Active Original Android Development] O-T:
No boot when charging - what is your bootloader version?

getprop ro.bootloader

=?
[Galaxy S 4 Active Original Android Development] 6783:
Which version of stock rom i can use as base, darkmen's stock or ...
[Galaxy S 4 Active Original Android Development] spegelius:
By default, none. But with KT kernel, at least WizCyan works fine, i haven't tried others...
[Galaxy S 4 Active Original Android Development] spegelius:
New TWRP and MultiROM releases.

TWRP 20150112_202427

Changes:

All commits here: https://github.com/spegelius/Team-Win-Recovery-Project/commits/master?page=2 since Dec 18, 2014

MultiROM 20150112-v30-UNOFFICIAL-jactivelte

Changes:

All commit here: https://github.com/Tasssadar/multirom/commits/master since Dec 03, 2014
[Galaxy S 4 Active Original Android Development] d8389:
Hi.

I don't use multi-ROM, but this recovery perfect with stock based ROM except one minor bug.

Instead of reboot device it will switch it off. Reboot download, reboot recovery and adb reboot work perfectly.

Can you fix it ?

Thanks.
[Galaxy S 4 Active Original Android Development] spegelius:
This problem is in CWM recovery too. It's on my backlog, but on the end of it. No idea when i get to it...
[Galaxy S 4 Active Original Android Development] sartana:
i tried to use Rom from external Sd without success.

it takes a big time to flash, a really big time to boot, and after all roms don't work correctly.

I try whit CM12 and slim, system has stopped, ui has stopped and many other errors.

Primary Rom it's PacMan.

If i use some Rom on internal , no problem at all.

In recovery there are two point of mount for external sd:

/dev/block/mmcblk1p1 (vfat)

/dev/block/mmcblk1p (vfat)

I use first cause the second gives error immediatly.

It can be an sd card related problem? i format (fat 32 ) it whit pc.
[Galaxy S 4 Active Original Android Development] spegelius:
Yes, if it's a slow card, errors seem to happen. I got a relatively fast sd card and quite often when i boot a rom from it, first time opening the camera crashes. It opens ok afterwards, though. I suggest to stay away from flashing roms to external storage with slow cards.
[Galaxy S 4 Active Original Android Development] d8389:
"reboot" command in internal terminal works as expected.

Probably wrong script under reboot buttons. May be shutdown command with not supported by shell parameters.
[Galaxy S 4 Active Original Android Development] moviecut:
I am not using multirom, but i want to use twrp with my normal cm11 rom. But i am afraid about this: "MultiROM TWRP can work without MultiROM installed. Obviously most MultiROM related featiures won't so steer away from them.

When formatting partitions, especially /data, do keep backups handly, even from /sdcard. Current build seems to format /sdcard alongside /data."

I am afraid to format my internal sd. Is it fixed?

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] spegelius:
Well, don't really know how to fix it, because in S4 and S4 active, /data is on the same disk as sdcard. So if you format internal sdcard, you format /data. One option could be to not actually format the sdcard, but to run recursive file deletion... but that doesn't work when one wants to change internal sdcard's file system.

Formatting external sdcard doesn't affect /data.
[Galaxy S 4 Active Original Android Development] d8389:
I've investigatad "Reboot" problem some more and found temporary solution.

typing

cd /sbin
echo #!/sbin/sh > rebootsystem.sh
echo /sbin/reboot system >>rebootsystem.sh

chmod 755 rebootsystem.sh

in terminal window makes Reboot System button work as expected.

Now re-packing initrd and I'll post patched image here in case of success and if op will permit this.
[Galaxy S 4 Active Original Android Development] spegelius:
If it works, yes do post it.
[Galaxy S 4 Active Original Android Development] d8389:
Patched recovery with working "Reboot System" buttons.

Tested on TW based ROM.

I don't use MultiROM.

I'm not familiar with kernels, just used tool from this thread http://xdaforums.com/showthread.php?t=2073775. So, no warranty, but it works.

tar - https://my.pcloud.com/publink/show?code=XZOBWkZdg5LeQzIqbyO0ILGKTqCDb7zbtrk

zip - https://my.pcloud.com/publink/show?code=XZUBWkZRBExgE0dIjX5SmzA8dkiy5cPDK8k
[Galaxy S 4 Active Original Android Development] spegelius:
New MultiROM and TWRP released:

20150207-v30-UNOFFICIAL-jactivelte

Changes:

All commits here: https://github.com/Tasssadar/multirom/commits/master since Jan 12, 2015

TWRP 20150207_174341

Changes:

All commits here: https://github.com/spegelius/Team-Win-Recovery-Project/commits/master?page=2 since Jan 12, 2015

Fix reboot not working (credits for the fix: [MENTION=2354543]d8389[/MENTION])
[Galaxy S 4 Active Original Android Development] spegelius:
New MultiROM and TWRP released:

multirom-20150215-v31-UNOFFICIAL-jactivelte

Changes:

All commits here: https://github.com/Tasssadar/multirom/commits/master since Feb 7, 2015

Supports new CM12 fstab scheme, needed for newest CM12 builds to work

multirom_twrp_20150215_000001

Changes:

All commits here: https://github.com/spegelius/Team-Wi.../master?page=2 since Feb 7, 2015
[Galaxy S 4 Active Original Android Development] Pkt_Lnt:
Did you get this solved? I just had it happen to me. :(

After weeks, I got my bootloader updated, installed WizCyan. Two days later installed ktoonsez TW kernel to setup Multi-Boot. Less than 24 hours later I have images burned if of philz recovery and my homescreen combined. I was in recovery maybe 45 min total and home screen on 4 hours. Trying the Burn-In app to repair.

We can take this to PM or another thread since it is a bit OT.
[Galaxy S 4 Active Original Android Development] ZeroZorro:
I just PMed you Pkt_Lnt ...