yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Active Original Android Development] Devo7v:
I'm having a very strange issue with MultiROM. I had CM12-20150304-NIGHTLY installed as my main ROM. This morning I downloaded and dirty flashed CM12-20150317-NIGHTLY but it flashed far too quickly, maybe 15 seconds. I tried to boot and nothing just a bootloop. I then went back into recovery and wiped cache/dalvik and reflashed CM12-20150304-NIGHTLY (this was the file I originally used to install the ROM for the first time). Again it flashed seemingly too quickly, and again bootloop. I'm not sure what is going on, I'm using MutliROM-20150207-v30-UNOFFICIAL and MultiROM_twrp_20150207_174341. See the TWRP log below, any help would be greatly appreciated.

Installing '/external_sd/ROMs/S4Active/CM12/cm-12-20150304-NIGHTLY-jactivelet.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
script succeeded: result was [0.200000]
Injecting boot.img with MultiROM...
Extracting boot image...
Decompressing ramdisk...
Ramdisk uses GZIP compression
Copying trampoline...
Compressing ramdisk...
Packing boot image
Updating partition details...
...done

EDIT:

I was finally able to flash 20150317. I had to wipe my main system so that no ROM was installed, flash 20150304, confirm that it boots, and then flash 20150317. I have no idea what I couldn't dirty flash from 20150304 to 20150317 originally, but I finally got where I want to be. Now all I need to do is restore my apps.
[Galaxy S 4 Active Original Android Development] sicHiRsch:
Hi there,

I have the latest multirom twrp and multirom (31) installed, but when i choose something but the main rom it just reboots into recovery, instead of into that rom. Does anyone know what is going on? I have CM 12 as my main rom, Stockyrom and SuperWizCyan as additional roms. Cheers
[Galaxy S 4 Active Original Android Development] spegelius:
Have you installed KT kernel for Stockyrom and WizCyan? Stock TW kernel doesn't have KEXEC-HARDBOOT...
[Galaxy S 4 Active Original Android Development] sicHiRsch:
Indeed I have not yet. Thanks
[Galaxy S 4 Active Original Android Development] WillyTP:
Hi,

could you be please so kind to provide an update to the latest version of TWRP for our active?

Thank you so much!
[Galaxy S 4 Active Original Android Development] O-T:
Last months [MENTION=3876105]spegelius[/MENTION] has been busy with real life. We are some versions behind 2860 left at 2840 from February.

http://xdaforums.com/showthread.php?p=46136281

Still it's more recently updated that the i9295 Philz recovery more than 7 months old.

Developer Philz has abandoned the source i9295 Philz is ported from while TWRP source is still alive.
[Galaxy S 4 Active Original Android Development] blausand:
Can't find the TWRP 31 download as tar?

As many will confirm, precise filenames are important to avoid getting confused with ROMs and images.

I found a zip named

multirom_twrp_20150215_000001

somewhere on google drive, and i had to unzip it and wrap it in .tar format.

But ODIN 3.07 hangs at the very beginning of the flash process ("Starting...") and i can't tell if i have the right file and format now.

Earlier TWRP versions didn't react on touch input and since it has no hardware button support, i couldn'T use it.

The twrp_mythi_8.tar on Google Drive shows version number 2.8.0.0 in it's header and wasn't working.

The only recovery i could use with the jactivelte was philz_mythi_4.tar

But it makes setup of StockyMOD a nightmare because you navigate blindly with volume buttons and power button without touch support.

Any ideas why touch doesn't work?

Please, link to that latest TWRP from may, matching the MultiROM V31 somewhere!

---------- Post added at 08:37 PM ---------- Previous post was at 08:18 PM ----------

I tried the multirom_twrp_20150215_000001 per PhilZ touch 6.57.9 (ClockworkMod v6.0.5.1)

and got the following Errors:

E: footer is wrong

E: signature verification failed

E: Installation aborted.

That was, obviously, because the signature was not correct.

Skipping the verification makes the install succeed.

Result was a booting Multi TWRP 2.8.5, but unfortunately again,

i can't communicate because the state lacks touch input

.
[Galaxy S 4 Active Original Android Development] spegelius:
The .tar.md5 version is there, been since i uploaded it (you do know that Odin expects .tar.md5 files?)

No ideas about the touch screen support, been working fine ever since the first build. Only problem with screen was the screen timeout bug where the screen went back and could not be woke up, fixed release or two back.
[Galaxy S 4 Active Original Android Development] moviecut:
i am still on cwm 6.0.5.1 as i am afraid of this: "When formatting partitions, especially /data, do keep backups handly, even from /sdcard. As /data and /sdcard are on same partition, formatting /data formats /sdcard. "

i dont use multirom, i only want to have a fully functional twrp for flashing my primary rom. But i am afraid to wipe my sdcard (i think it is the internal sdcard, right?). are there workarounds like a cleanwipe.zip, that i can flash before every rom, so that i dont have to use the dangerous twrp wipe?
[Galaxy S 4 Active Original Android Development] spegelius:
Formatting != wiping. When wiping, only /data is wiped (not formatted) and /sdcard i stays intact. When formatting, it needs to be done for the whole partition, hence /sdcard will be formatted too. And it might be that formatting happens only when changing filesystem type, like from ext4 to f2fs...
[Galaxy S 4 Active Original Android Development] moviecut:
Wouhouuu, i just flashed twrp v31 with my cwm and i am happy with all those new features. Multiple zip flashing, file manager, backup process with size and % details and lots more!

Edit: hey, reboot system from recovery is working! Cool!

The only thing i cant set, is the timezone...is that a known bug?

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] spegelius:
Don't know about timezone, just tried it for the first time. Seems there are no options to select...
[Galaxy S 4 Active Original Android Development] spegelius:
It seems releasing new version of TWRP is impossible for now, current TWRP code creates too big recovery image which cannot be flashed to phone. I've tried reducing kernel size by disabling some kernel options, but i'm still almost 200kb over the limit... don't know i it's possible to create working version.
[Galaxy S 4 Active Original Android Development] O-T:
Open issue.

deb: 2.8.6.1 Image is too big for recovery partition #415

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/415

Listed among some hundreds of other more or less significant issues

https://github.com/TeamWin/Team-Win-Recovery-Project/issues?page=1&q=is:issue+is:open

2860 might be a good enough choice for the moment. Some feedback is in the i9505 xda-forum of that one.

http://xdaforums.com/showthread.php?p=59777345

Good to hear from you [MENTION=3876105]spegelius[/MENTION] still keeping an eye on the S4 Active.
[Galaxy S 4 Active Original Android Development] spegelius:
Ok, might try 2.8.6.0. There seems to be some encryption bug on 2.8.6.0, though...
[Galaxy S 4 Active Original Android Development] spegelius:
I managed to build TWRP 2.8.6.0 and seems to be working ok. Not very extensive testing, though so i'm uploading it for testing with that in mind.

multirom_twrp_20150622_163952

Also uploaded multirom v32.

EDIT: removed twrp as it seems buggy by reports. Multirom still available, but consider it as test version as i don't know how well it works with older twrp.
[Galaxy S 4 Active Original Android Development] d8389:
spegelius

Hi,

people report bootlop after flashing http://xdaforums.com/galaxy-s4-active/development/mod-modfix-pack-5-0-1-i9295xxudob4-t3062934 , E8 version by new recovery multirom_twrp_20150622, but successfull boot when using multirom_twrp_20150215_000001.

I'll check later, that is the problem & update.

Update1

Bootloop after flashing https://drive.google.com/file/d/0B-CE1vlk7OYkSFFjcU45aU9iRnc/view?usp=sharing.

Still can't find what's the problem, because all seems good.

Don't know what's happening, but dex2oat crashing after using new TWRP, but works with no issues, when r-flashed by old one.
[Galaxy S 4 Active Original Android Development] Lahiru xda:
After updated to 2206 twrp recovery when I update new cm12.1 official build Google Apps crashing nonstop. After I go back to install twrp 1502 build no Google Apps crashing after updating cm12.1. Maybe this issue due to new twrp recovery build.
[Galaxy S 4 Active Original Android Development] spegelius:
If there's bugs, i'll remove the download. Not sure if newer versions are coming.
[Galaxy S 4 Active Original Android Development] Lahiru xda:
1502 twrp working for me just fine :good:. after installing latest build after updating cm 12.1 official gapps are crashing this the issue i faced :(
[Galaxy S 4 Active Original Android Development] NIKHILALWAYZ:
after adding a new rom ,no problem with booting but getting system ui fc loops
[Galaxy S 4 Active Original Android Development] FORC3:
I accidentally flashed MultiROM.zip instead of twrp.zip. how can i revert/uninstall it?
[Galaxy S 4 Active Original Android Development] moviecut:
Will there be a TWRP update to the latest version for our i9295?

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 Active Original Android Development] tasken:
an update on twrp would be grate! any way on helping?
[Galaxy S 4 Active Original Android Development] davidbejar:
Is it posible to change file system to f2fs? I did it with my M8 using advanced formatting option, I would like to use it with a CM12.1 ROM.
[Galaxy S 4 Active Original Android Development] spegelius:
To remove multirom, look for multirom directory on your sdcard and delete it. You can use file browser in android.

Yes, testing version 2.8.7 now. I needed to reduce kernel size quite a lot to fit all under 10MB, i did it by disabling some options in kernel (like net ipsec tunnels, unused ipv6 options, es325 codec firmware etc.).

Yes, i'm using f2fs myself, formatted with TWRP. Word of caution if you are going to be changing fs type for /data: /data and /sdcard are actually on same partition, so make sure you have backed up your internal sdcard before changing fs type. Changing fs type formats whole partition, i.e. /data and /sdcard.
[Galaxy S 4 Active Original Android Development] spegelius:
New MultiROM and TWRP testversions available:

multirom-20151225-v32-UNOFFICIAL-jactivelte and multirom-20151225-v32-UNOFFICIAL-jactivelte_f2fs

Changes:

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

Use f2fs version if your /data is formatted with f2fs. /system with f2fs not supported

multirom_twrp_20151225_225225

Changes:

All commits here: https://github.com/spegelius/Team-Wi.../master?page=2 since Feb 15, 2015

Kernel options have been turned off heavily so there might be bugs or something not working right: https://github.com/spegelius/android_kernel_samsung_jf/commits/cm-11.0-multirom

As always. i've only tested these by myself so if bugs are found, report them here. Multirom doesn't support initial CM13 build as 2nd rom, but i have newer CM13 build ready which can be flashed as 2nd rom.
[Galaxy S 4 Active Original Android Development] spegelius:
It seems that there's some problems with f2fs and current TWRP, which is built on CM11. F2fs drivers need an update, but that needs newer kernel and CM12.1 base, so i'll need to see if i can get TWRP built on CM12.1. This is really stopping my CM13 development for now...
[Galaxy S 4 Active Original Android Development] spegelius:
Apparently the f2fs problems were due to the updated baseband (OI5), somehow selinux got to be even more restrictive. So i moved twrp and multirom to CM12.1 base and configured selinux permissions for recovery as permissive. With CM12.1 base, kernel and tools have been updated, which should improve overall functionality. Also i made separate f2fs builds, for both twrp and multirom. Not entirely sure separate versions are needed, but if there's problems with f2fs, do try the f2fs versions.

New testbuilds uploading:

multirom_twrp_20151228_165546 and multirom_twrp_f2fs_20151228_171930:

built on top of CM12.1 instead CM11

separate f2fs build, in theory should support f2fs encryption, but not tested

multirom-20151228-v32-UNOFFICIAL-jactivelte and multirom-20151228-v32-UNOFFICIAL-jactivelte_f2fs:

built on top of CM12.1 instead CM11

separate f2fs build, might be needed when /data is formatted as f2fs
[Galaxy S 4 Active Original Android Development] Devo7v:
I updated to the 20151228 versions of twrp and multirom. I believe on the previous versions from February, if you only had 1 Rom installed it would bypass the multirom prompt when booting the phone. However if you had 2 or more ROMs it would display the multirom prompt when booting. For some reason I can't seem to figure how to activate this in the newest versions. Any ideas?
[Galaxy S 4 Active Original Android Development] spegelius:
Hmm, i don't remember any configuration option about that and don't know the code enough to say how it is configured... i'll have a look when i have some time
[Galaxy S 4 Active Original Android Development] Nixda99:
CM12.1 OTA updates with new version?

Thanks for your time and work.:good:

My friend had installed multirom_twrp_20150215 and problems with OTA updates for CM12.1 Official Nightlies. He stopped in recovery,

an error with corrupt update files. Tried more than 1 version, same error. Manual installation of the downloaded rom.zip works, but

its too complicated for him.

Should be the OTA updates works with the new version, multirom_twrp_20151228_165546.zip.

I dont need multi rom, only the TWRP recovery, is this file right???
[Galaxy S 4 Active Original Android Development] spegelius:
CM OTA updates are meant to be used with CWM. I remember trying OTA update few times, but hitting the probably same problem. So if OTA is needed, use CWM.
[Galaxy S 4 Active Original Android Development] Nixda99:
Thanks. Had seen OTA on an S4 mini with TWRP, that's why I thought it is always the case.
[Galaxy S 4 Active Original Android Development] dickta:
TWRP

Hi spegelius!

Can you please make an ordinary it stock version of your TWRP 2.8.7.0 for this device? The other TWRP is not working correctly 2.8.0.0. Your Multi rom TWRP is awesome but I think most of us is using your recovery because it works not for the multi rom capability.

So please make a stock TWRP 2.8.7.0 recovery for us!

Thank You for your attention!
[Galaxy S 4 Active Original Android Development] Devo7v:
You can use this as stock TWRP, just don't flash the multiROM zip. It will function exactly like stock TWRP, only it will have a nonfunctional menu item under the advanced button.
[Galaxy S 4 Active Original Android Development] dickta:
TWRP 3.0.0.0

Hi!

Will you make the new version of TWRP(3.0.0.0) in a stock or multirom variant to our beloved S4 Active?

Thanks for your answer in advance!
[Galaxy S 4 Active Original Android Development] jcadduono:
Wild JCADDUONO appeared!

JCADDUONO used PORT TWRP!

It was super effective!

http://xdaforums.com/galaxy-s4-active/orig-development/recovery-official-twrp-jactivelte-t3331202
[Galaxy S 4 Active Original Android Development] quubee:
How small is my? Is it enought for MultiROM?
[Galaxy S 4 Active Original Android Development] jcadduono:
It's 10 MB and my image is 8.9 MB so there's 1.1 MB to spare. If he wants to multirom upgrade mine then he should have plenty of space.
[Galaxy S 4 Active Original Android Development] Jhon998:
multirom uninstaller?
[Galaxy S 4 Active Original Android Development] ederekun:
Just delete the multirom folder from your internal storage
[Galaxy S 4 Active Original Android Development] GoZiLlA98:
Anyone still have a mirror of multirom? The links are dead. Thanks!
[Verizon LG G3] dbow32:
Ok, I was stock rooted to allow for wifi hotspot. Once I started getting the latest OTA from VZW I decided to try to go back to stock to accept the OTA. I went through all the YouTube video's and loaded the LG software but my phone would never sync to the LG suite software. I ended up giving up and just kept pushing the OTA off. It got so bad that I decided last night to install a recovery and then flash an unofficial CWM rom. So this morning it was working fine and then all of the sudden, I lost VZW data. Couldn't get any signal. So I decided to try to flash the Official Cyanogenmod 11. That blew up during the setup and gave me an error that it could not find any cellular service. I wiped the phone and tried to restore the backup I made of my stock rom with the recovery on it. I made the backup the second the recovery was finished. It's giving me an MD5 error?? I've tried this multiple times with the same result. So, I then decide to flash one of the two roms (unofficial & official) back to see if I can get the phone working again. No such luck.... It keeps trying to set up my "cellular service" and just runs. Nothing ever finishes. I'm really worried at this point. I would be perfectly fine to flash a Verizon image and go back to stock. But I can't seem to find out how to do this or where to find the file. Please help me.. I'm getting desperate.

Edit: I tired to flash the Unofficial Rom again and this time it seems to be working. I would still rather just go back to stock though. If anyone can point me to the correct place I'd be very appreciative.

Thanks

Dave
[Verizon LG G3] random571:
Here is a link to flash back to stock: http://xdaforums.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140

I know you wanted to take the OTA, but why not download one of the stock based 11c ROM's, like Jasmine 3.0? That way you'll still get the latest version(11c) but you won't lose root and recovery. The OTA patches root, so no recovery either. Here's a link for Jasmine 3.0 stock based 11c if you want to try it: http://xdaforums.com/verizon-lg-g3/development/rom-jasminerom-v1-0-t2904641

Also, there has been issues with data on the CM builds. It seems pretty common right now. Check the CM threads for more info on that. I believe there is a command people have been entering(killall rild in terminal emulator) to get data back, but it seems 50/50 that it'll work.
[Verizon LG G3] dbow32:
Hey thanks a lot for your reply. I understand what you're saying with going back to stock. My issues with flashing custom Roms is that I have to have my phone work 100%. I've been flashing since the original Droid Incredible. And I've NEVER found a Rom that didn't have minor glitches and issues. Usually those issues affect my daily routine. I'll give Jasmine3.0 a shot and if it works I might just keep it. If not i'll just suffer through VZW's BS! Anyway, really appreciate your input.

Dave
[Verizon LG G3] random571:
Glad to help. I'm with you on the 100% functionality too, so that is why I'm on Jasmine 3.0. Don't get me wrong, I love custom ROMs and all the work the devs do, but until all the kinks are worked out I'd rather be stock.

Also, I'm not trying to advertise anything, but flashing the skydragon kernel into Jasmine has helped the speed/lag and battery life as well. Its worth a try - but it only works on stock/non-AOSP based ROMs. If you try it though, also download the stock 11c kernel that the OP put in the thread just in case you have issues. I don't have the link handy, but the kernel is located in the "original android development" thread. Peace :)
[Verizon LG G3] BladeRunner:
Which drivers were you using? I had trouble with the Unified Drivers linked in some posts and had to use the Verizon specific drivers. I also had to usually reinstall the drivers each time I tried to use the flash tool to get it to recognize my phone.
[Verizon LG G3] dbow32:
To be honest, I'm not sure what drivers I was using. I did a Google search for LG suite and found the closest version I could find. They didn't have the VS985, Only P985. So that might have had something to do with it.
[Verizon LG G3] dbow32:
I have a question, what is the "Modem" for? BTW, this Rom is VERY nice. Thanks
[Verizon LG G3] random571:
Modem is the radio. Some people reported better signal strength on the 11c modem versus the 10b modem, but I didn't notice too much of a difference myself.

And glad you like the ROM, but all thanks go to hsbadr who came up with it :)
[Verizon LG G3] dbow32:
You know, it's really odd but the last few weeks my phone's signal has dropped. I listen to Sirius through my phone during the day at work. And I've always received 1 to 2 bars of 4g. But the last few weeks, It's dropped to about 2 to 3 bars of 3G. I thought maybe VZW was secretly throttling me. But maybe it's the updated Radio?
[Verizon LG G3] random571:
It's possible the modem could've been causing problems. Is 11c better or worse for you? And its also possible big red was throttling you too. That seems like something they'd do.

If you use/like xposed framework G3 tweaksbox is a good app to get for customizing your phone a little bit. And greenify and amplify are good xposed apps that help your battery life a whole lot. They are worth checking out in the play store.
[Android Apps and Games] DJRepresent:
Flashed the phone with Cyanogen and when I booted and ran FFIV, it only gave me the option for a new game. Weak! Is there any way to get my save data back? I figure I could try a recovery but not sure how to proceed with that.

Help's appreciated!
[Android Apps and Games] big gulps huh?:
did you wipe data before installing the rom? If so, its gone. Next time back up with Titanium backup or something like it and you wont have that issue.
[ONE Q&A, Help & Troubleshooting] QA Bot:
Q&A for [ROM]BenczeOS v 1.0 Umad - 11s based - feature loaded - December 1, 2014

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [ROM]BenczeOS v 1.0 Umad - 11s based - feature loaded - December 1, 2014. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[ONE Q&A, Help & Troubleshooting] cepone:
Hi, i tried this rom and liked it but the top of my screen has like a red border, at the start it was small and then it covered the whole status bar, i wiped everything before installing and installed using TWRP, any idea what it might be?

Thanks
[ONE Q&A, Help & Troubleshooting] Negan:
Can you post a screen shot? First I've seen or heard of this
[ONE Q&A, Help & Troubleshooting] cepone:
Will install again and let you know if i get the issue again :)

Cheers
[ONE Q&A, Help & Troubleshooting] gshadow325:
I tried this ROM and my Google play will not allow me to install simple app called credit karma, says not compatible with my device. Then looked into other apps and it did the same thing.
[ONE Q&A, Help & Troubleshooting] Negan:
This rom has nothing to do with Google play. You can't possibly believe that. It amazes me, that the first thought that pops into your head is "it must be the rom". In future please refrain from random nonfactual information out of no where. If you have a legit problem please refer to what I have asked you to do in the op and I will be happy to assist you .
[ONE Q&A, Help & Troubleshooting] gshadow325:
ok. if you say so. i will try again and see what i did wrong.

for me its a new device and i do love what you have done with it. i was fussing with it for a good 4 hours before i went back to stock.