yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] rmedure:
I'll be jumping into xposed soon, and just want to make sure I have a known good backup/restore method in my back pocket. Can anyone confirm the following? If I can boot up and run FF, but ROM is otherwise jacked up then I can restore a 'normal' backup in FF? And if no boot, then odin to NC5, root, run FF and restore 'full' backup?

Oh, and confirmed tether patch working on VZW i545, deodexed, with no ill side effects so far as I can tell, but I think y'all already knew that. :)

[MENTION=4708661]muniz_ri[/MENTION], thanks again for this ...

Cheers!
[Verizon Samsung Galaxy S 4] OrneryTX:
Downgrade from OC1 to NK1

I upgraded to Lollipop and kept root using the method in this thread without any problems and thanks for that. Unfortunately because one of my most important apps isn't playing well with Lollipop, it looks like I'm going to have to downgrade back to KitKat. I've scrolled through many pages of this thread and, if I'm reading things right, I should be able to follow these directions to get back to 4.4.2 (the same way I rooted to begin with): http://xdaforums.com/galaxy-s4-verizon/general/how-to-root-i545vrufnk1-4-4-2-12-1-2014-t2959613

Can someone confirm? That the simplest/best/safest method?

Thank you.
[Verizon Samsung Galaxy S 4] grimjeeper:
Any insight on flashing the deodexed version on top of the odexed version?
[Verizon Samsung Galaxy S 4] muniz_ri:
No different than flashing any compatible ROM after another. The ROM's perform a full wipe and leave you with a clean install so backup prior to flashing.
[Verizon Samsung Galaxy S 4] dcjamies:
Installed this a day ago after accidentally taking the NK4 update and losing root. Downgraded to NC1, rooted, and then upgraded to OC1 via this thread. All has been fine until this afternoon and the power button seems to have failed. Has anyone else experienced this on this update? I thinking I'm just dealing with a bad button that needs to be replaced, but I wanted to consult with the experts first. Thoughts? Suggestions?

I have installed "Button Savior" to make the phone more functional.
[Verizon Samsung Galaxy S 4] vegita319:
It's possible your power button is "physically" broken. Mine eventually gave out and had to be replaced. I used a multi-meter to check the power switch after opening it up. If you're gutsy, there's a youtube video online on how you can test and then replace the power button with a new one. Good luck! I take no responsibility if you decide to open it up as you are voiding the warranty :).
[Verizon Samsung Galaxy S 4] happy2472:
This THE only LL rom i can get working fully on my sch-i545 ... was wondering if i can flash a different kernel? Like Hybridmax V3.5
[Verizon Samsung Galaxy S 4] sinner822:
Only if you have a MDK bootloader.

If you updated with this rom no.
[Verizon Samsung Galaxy S 4] rbird2:
Just follow the instructions and flash with Flashfire. No need no revert back to NC5. Be sure to back up your data since installing will do a clean install. I just went from the stock odex version of this ROM to the deodex version today and it worked fine. Note that there is a much longer wait at the Verizon screen vs installing the stock version.
[Verizon Samsung Galaxy S 4] dcjamies:
I figured that's what is going on, too. No worries on the warranty. i bought the unit second hand anyway. Trying to ride out my days until upgrade in September. Thanks!
[Verizon Samsung Galaxy S 4] muniz_ri:
Yes, you can flash the NK1 ROM to get back to 4.4.2. Or, here is an NK4 ROM which is the most current 4.4.2 version which I assume resolved some bugs in NK1: I545_NK4_Stock_Rooted_ROM

I don't expect there is much demand for KitKat at this point in time so I don't plan on releasing NK4 in its own thread.
[Verizon Samsung Galaxy S 4] ATGkompressor:
Yeah, it's a good 10-15 minute wait compared to the odex. But it's worth it. Very very snappy ROM. I tried Echoe...buggy as hell.
[Verizon Samsung Galaxy S 4] grimjeeper:
So I just flashed the deodex over the stock version, stuck at custom screen, haven't seen the verizon screen. Is it a boot loop or should I stick it out?
[Verizon Samsung Galaxy S 4] muniz_ri:
You forgot to set your screen timeout to 10mins.
[Verizon Samsung Galaxy S 4] grimjeeper:
No I made sure of that, didn't even take 2 minutes to complete anyway. I'm odin back to NC5 now.

---------- Post added at 07:27 PM ---------- Previous post was at 06:30 PM ----------

Has there been an issue with the flashfire app not opening after the odin back to nc5?
[Verizon Samsung Galaxy S 4] grimjeeper:
Got the App to work, still stuck at "samsung galaxy s4" screen. Timeout set to 10 minutes, not sure where the problem lies.
[Verizon Samsung Galaxy S 4] OrneryTX:
Thank you for the NK4 update. I wonder if that would have helped with my downgrade. After spending all day yesterday (and deep into the night) fighting boot loops, wifi troubles, and various other problems, I finally got things back up and running on NK1 this morning. I think I"ll wait a few days before trying NK4. Same alternative Safestrap method work for that?
[Verizon Samsung Galaxy S 4] tommykmusic:
So if I updated to OC1 rooted and loose safe strap then what do I use as a custom recovery?
[Verizon Samsung Galaxy S 4] haza12d:
Flashfire
[Verizon Samsung Galaxy S 4] tommykmusic:
Cool, that sounds awesome! Now we just have to get that link working to become a beta. What custom roms work on OC1?
[Verizon Samsung Galaxy S 4] grimjeeper:
Same issue flashing Deodexed version with safestrap, stuck at galaxy s4 screen.
[Verizon Samsung Galaxy S 4] rbird2:
Use Flashfire. Follow the instructions on page 1 and flashing the Deodexed version works. I loaded the Deodexed ROM yesterday using Flashfire with no problems.
[Verizon Samsung Galaxy S 4] grimjeeper:
I had the stock one running since it was first released, worked like a charm. So yesterday I flashed the deodexed version with flash fire twice had to Odin to nc5. So then I figured I'd use safe strap since I was having an issue with flashfire, sol no dice. Must be an issue with my phone and the deodexed version, haven't tried to stock version since all the updates.
[Verizon Samsung Galaxy S 4] Tech 4 9:
I apologize for this maybe being off topic but ...flashfire no longer even installs ...doesn't even ask for su permission. ..out of clear blue. Re odined back to nc5 multiple times. Su and busy box all updated. Vzw i545. Very odd. Any help appreciated and thanks.
[Verizon Samsung Galaxy S 4] rmedure:
Flashfire app expired June 1. Until the dev fixes it, go into system settings and disable auto date/time and manually set the date to anything before 6/1.
[Verizon Samsung Galaxy S 4] rmedure:
Any issues?
[Verizon Samsung Galaxy S 4] aznjosh:
Those of you who get stuck should try flashing the oc1 reupgrade file from here using odin http://xdaforums.com/showthread.php?t=3100016. Your kernel probably didn't get upgraded to oc1.
[Verizon Samsung Galaxy S 4] notoriousB:
First of all thanks to muniz_ri for putting this together! I updated this weekend and everything's running great with one exception: I have to run an app called Good For Enterprise for my corporate email and any time I launch the current Good app it crashes. It's behaving like I have xposed framework installed (that's what the app does if it detects xposed - nice huh?) but I don't, I'm running the odex version of the OC1 update with root, no xposed. Anyone else have to run this app and having issues (or not)?

I did find a workaround for anyone else affected, download version 2.7.0.390 from http://get.good.com/ea/previous - apparently this is a version prior to their implementation of the xposed intentional crash. Maybe this will help someone else.
[Verizon Samsung Galaxy S 4] muniz_ri:
I doubt that is the case based on FF's performance among numerous devices. It's still buggy and likely stopped flashing prematurely. Watch the screen during the flash.....seeing "Rebooting...." at the end of the flash usually confirms a complete flash.

But if someone stuck on the S4 boot screen would like to try to Odin flash the kernel here it is: I545_OC1_Stock_Kernel
[Verizon Samsung Galaxy S 4] rp1226:
GFE doesn't like root. You might need this ROM without root to make it work. I used to use it a while back on my S4 but if it detected root, it would lock down and you would need a new pin for it. Keep an eye out on the the other forums for more details on this app.
[Verizon Samsung Galaxy S 4] notoriousB:
Thanks, fortunately for me this isn't a root detection issue that i can tell. I'm not getting locked out, the app just crashes. My company doesn't enforce the root check, I've been using GFE while rooted for years now. I can't even get to the PIN install on a new load of this ROM before GFE crashes. If i use an old version it installs fine, then if i update to new it crashes. Very strange. v2.7 seems to work fine for now.
[Verizon Samsung Galaxy S 4] grimjeeper:
Would going from odex to de odex cause the kernel to be lost.
[Verizon Samsung Galaxy S 4] ericmtnbkr:
I flashed to original OC1 root upgrade. Anyone know whether I should do a full wipe if I want to flash the latest deodexed version?

Thanks.
[Verizon Samsung Galaxy S 4] skepticmisfit:
the zip automatically wipes data and cache n stuff so yeah, plus it's always good to wipe data and cache before flashing a ROM of any kind. the modifications (that aren't the tethering add-on) will automatically wipe cache before flashing, also to avoid any system conflicts
[Verizon Samsung Galaxy S 4] CoMtnMan:
I also just boot-looped at the Samsung screen with the Deodexed ROM version. Tried flashing the OC1 kernel - No Go. Odin'd back to NC5, re-rooted, etc...

Has anyone been able to upgrade to the deodexed version with Flashfire 0.20? Perhaps this is a problem with the newest version of FF since people seemed to flash the deodexed version just fine 3 days ago (version 0.18). Getting ready to try again. This time will closely watch the FF process for completion. Will report back.

Try #2

So... FF hung on System img then rebooted to Galaxy S4 start screen without saying "Complete" or "Rebooting" - likely this is bad flashing.

Tried to use Re-upgrade as mentioned above but still bootlooped at splash screen

Try #3 coming soon
[Verizon Samsung Galaxy S 4] CoMtnMan:
Trial #3 - and boom goes the dynamite...

I Odin'd back to NC5 (full wipe). Re-rooted with TR. I found an old version of FF (version 0.18) and installed that instead of the 0.20. Changed the date to before June 1st, 2015 in the settings. Then followed muniz_ri's instructions in the first post. Waited a very long 15 min but now on OC1 with NK4 BL.

So apparently from my N of 1 study FF 0.20 may not work but FF 0.18 does. Perhaps we could contact Chainfire and ask permission to post the older version in OP.
[Verizon Samsung Galaxy S 4] grimjeeper:
I got the same result flagging the deodex over nc5 with safestrap also. Seems to be something with the deodex and certain phones.
[Verizon Samsung Galaxy S 4] CoMtnMan:
The 0.18 version of Flashfire worked for me with the deodexed ROM. Give it a shot.
[Verizon Samsung Galaxy S 4] grimjeeper:
Not sure how to revert back with a beta
[Verizon Samsung Galaxy S 4] CoMtnMan:
I had an older copy backed up...after Odin'ing back to nc5 I merely installed the old version instead of the new. You also have to change the date in settings to something prior to June 1st, 2015 as there is a timer in the 0.18 version that expired.

I'm not sure how Chainfire would feel about his older beta work being posted here so I'm not going to link the version I have....I can PM him though and see what he says.
[Verizon Samsung Galaxy S 4] muniz_ri:
In your case this issue is unrelated to FF and likely due to your decision to use Safestrap to flash the ROM. Safestrap will not flash the kernel which will result in being stuck on the Samsung screen after flashing. Everyone should follow the directions as written in the OP.
[Verizon Samsung Galaxy S 4] grimjeeper:
I tried the method in the OP multiple times, figured what would it hurt to try safestrap. I almost certain I used v.18 of FF and still had galaxy screen bootloops. Before I tried the deodexed version I was running the stock version you uploaded that originally fixed the wifi. I haven't tried to flash the deodex with v.20 yet read another user didn't have sucess but did with v.18.
[Verizon Samsung Galaxy S 4] dcjamies:
Clock app stops every time. I cannot open to use the alarm clock, timer, etc. Is this a known issue? I searched this thread with no results. I know it's not that big of a deal, but would be nice to have a working native clock. I've cleared cache, etc.
[Verizon Samsung Galaxy S 4] ATGkompressor:
I flashed the deodex with v.20 from NC5 and xposed v3 sdk.
[Verizon Samsung Galaxy S 4] rbird2:
Battery life poor with DeOdexed ROM.

I had to revert back to the "I545_OC1_Stock_Rooted_ROM_wNK4_BL" since I found the battery life on my Samsung Galaxy S4 was very poor with " I545_OC1_Stock_DeOdexed_ROMwNK4_BL"

Battery life is now very good with the "I545_OC1_Stock_Rooted_ROM_wNK4_BL" .
[Verizon Samsung Galaxy S 4] rmedure:
Have you noticed any issues with xposed? I thought I've seen some folks having weird side effects ...
[Verizon Samsung Galaxy S 4] skepticmisfit:
I haven't had any issues, certain modules might cause weird conflicts though since not all modules are compatible with lollipop
[Verizon Samsung Galaxy S 4] rmedure:
That's good to know. I know some features of some modules may not work and may even be risky to try. But I could have sworn I heard some folks having weird side effects from just xposed without any modules ...
[Verizon Samsung Galaxy S 4] daventodd123:
Dropped my phone in water yesterday and the phone I was given as a replacement has 5.0.1 on it. Is there any way to root it on that update? I had my last phone safestrapped, so I understand that taking the OTA wasn't advised but the phone was already on that version when I got it.
[Verizon Samsung Galaxy S 4] skepticmisfit:
nope you're s.o.l.
[Verizon Samsung Galaxy S 4] ATGkompressor:
The issues that have been reported are likely user error. And not following OPs' instructions verbatim.

I've not had one single issue with just Xposed minus modules. And correct, some modules aren't fully functional.

Wanam, changing multiple options per 1 reboot causes a bootloop at red vzw bootanimation (and possibly just a single modification also). But if this happens, just pull the battery, wait a few seconds, re-insert, power up and should boot fine, but b patient.
[Verizon Samsung Galaxy S 4] millz2140:
Root vrugoc1

I'm wondering the same thing. . I took the update also and am now stuck without root Muniz please help us (will donate) $$ or gehot needs to make a upgrade version of towelroot for lollipop 5.0.1 users. . XDA DEVELOPERS PLEASE HELP US.. YALL RULE
[Verizon Samsung Galaxy S 4] skepticmisfit:
geohot didnt actually make towelroot. it was a really old linux kernel exploit discovered by another guy, geohot just made an app for it and then discovered it worked on vzw/at&t s5. and s4 active, which was a phone he probably owned.
[Verizon Samsung Galaxy S 4] fawzisaeed:
why this rom rooted dosnt appear with cdma dfs after mack cp log enable like s5
[Verizon Samsung Galaxy S 4] Murcus:
It Worked!

Just worked! 4.4 to 5.0.1. Running Titanium Backup to get all my settings back now.

Thank you so much muniz_ri, that update notifier was getting annoying.
[Verizon Samsung Galaxy S 4] Eddie Hicks:
Is it nornal to have less battery life with the deodexed version? Anyone else with the deodex ROM experiencing poor battery life?
[Verizon Samsung Galaxy S 4] teookie:
I followed OP's instructions exactly and I'm bootlooping on the "Samsumg Galaxy" logo. It doesn't even make it to the verizon logo. Help? Was running NC5 rooted prior to flashing.

Edit: well, I've ODIN'd back to NC5 and rooted. Will try again tomorrow.
[Verizon Samsung Galaxy S 4] GogoplataMMA:
I followed the instructions on my father's Samsung Galaxy S4 Mini i545 and it rebooted into the FlashFire screen and it tried installing the rooted upgrade.

Suddenly, the phone turned off. Now, it doesn't power on... at all. Wtf? I've successfully done this twice on two other i545 S4 phones, so what's the deal? What do I do now? It doesn't go on!

Need help ASAP!
[Verizon Samsung Galaxy S 4] wavedashdoc:
Samsung Galaxy S4 Mini i545.

Galaxy S4 mini

S4 MINI

MINI

different phone then regular i545......

wrong device thread...

Rom not compatible with that model...

probably perm bricked...

please read.
[Verizon Samsung Galaxy S 4] mike.s:
Never heard of that one. Do you mean the Samsung Galaxy S4 Mini SCH-I435? Different phone, different firmware. Lollipop not available yet, if ever.
[Verizon Samsung Galaxy S 4] mitafoaj:
Results?

Were you able to reach out to Chainfire for v.0.18 [MENTION=1864368]CoMtnMan[/MENTION]. It's kind of frustrating to see that someone has found a solution, but cannot give us the antidote lol (I know you have to ask for permission to post the older version first). I keep seeing posts about people having issues (w/deodexed oc1 rom) boot looping using FF v.20 and poor battery life, but no one is providing a solution on how it can be fixed. People have the same question I have and are just told that it is the wrong forum. For example: [MENTION=5802175]killnut[/MENTION] asked "What the difference between -*I545_OC1_Stock_Rooted_ROM_wNK4_BL and -*I545_OC1_Stock_DeOdexed_ROMwNK4_BL?" He was given a link that pointed to the rules about searching the forum before posting questions. I'm like come on man! Pardon my noobism. I 'd like some answers or links to where this has been answered already. Anyone? I thank [MENTION=4708661]muniz_ri[/MENTION] for all the hard work as I would not know where to start without developers such as himself and I apologize for showing so much frustration in this post.

Thanks in advance for any help you all may provide.
[Verizon Samsung Galaxy S 4] rbird2:
Yes it appears so based on the information below:

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

"when developing Tornado for JVR both odexed and deodexed versions were Beta tested: the odex version was significantly better in stability, speed and battery life, so much so that the decision was made to develop Tornado solely as an odexed rom. "

http://terserahelubacanya.blogspot.com/2014/03/odex-deodex-all-rom-gampang-method-d.html

"With these explanation you can understand that:

Odexed Rom = +fast -difficult_customization +more_battery_life +better_stability +less_ram_utilization

Deodexed Rom = -slow +customization -less_battery_life -less_stability -worse_ram_manager
[Verizon Samsung Galaxy S 4] Eddie Hicks:
Thanks for the reply and link. I just switched from Muniz's odex to deodex assuming it was a better ROM since others were switching. I haven't used my phone much since I switched to deodex. I'm retired and use only use my land line when I'm home which is most of the time. I'll have to play around with it a see if I can find a difference in performance.
[Verizon Samsung Galaxy S 4] klabit87:
Most people that switched to deodex version switched because of the unofficial xposed framework.
[Verizon Samsung Galaxy S 4] rp1226:
I agree. That's why I switch. But really there isn't much need for that now adays. For the most part, LP runs awesome. I just wish there was a way to fix the memory leak problem since this is 5.0.1 without exposed.

I recommend going Odexed if you don't care for Xposed.
[Verizon Samsung Galaxy S 4] skepticmisfit:
another comment on deodexed ROM:

i personally love the xposed framework and mods for it but i felt like titanium backup restoring didn't go as smoothly as it did with the odexed OC1. one of my games, monument valley, didn't restore at all. maybe its a huge game but idk.
[Verizon Samsung Galaxy S 4] rp1226:
I've noticed the file structure on LP is different than KK. That could have something to do with it too. But good point!
[Verizon Samsung Galaxy S 4] MrGeekGuy:
Just to let you know, I did fix the issue, it was a hardware issue. Just had to take off the back cover and clean the wifi connector. It was just a coincidence it happened when I flashed OC1 . I guess two years in my pocket takes a toll. Now it works great.

http://forums.androidcentral.com/verizon-samsung-galaxy-s4/425226-wifi-low-signal-issue.html
[Verizon Samsung Galaxy S 4] brandoncampbell:
I'm guessing the same thing. the deodex rom seems to drain faster. Anyone have any ideas as to why?
[Verizon Samsung Galaxy S 4] CoMtnMan:
I messaged Chainfire but have not received a response. I also read that someone was able to ugrade successfully with FF 0.20, so perhaps it is not FlashFire at all. My experience was that it soft bricked twice in a row for 0.20 but successfully flashed for 0.18 on the first time. I can't explain why. Idk if muniz_ri has any different experience or input into the bootloops.
[Verizon Samsung Galaxy S 4] Osama Chishty:
i follw the instruction with deodex version flash fire did not flash anything and now i am just stuck on samsung custom logo... can u re post the old method please thanks in advance
[Verizon Samsung Galaxy S 4] AFront85:
After some days of hesitation, I upgraded this morning. Having read the available material, I found the process straightforward and rather simple. Once I restored my TB data and then froze the new bloat, everything was wonderful.

Titanium backup was invaluable, as was having extra back ups of my launcher and some widgets. This should go without saying for anything that requires factory reset.

Well done. Much appreciated.
[Verizon Samsung Galaxy S 4] Osama Chishty:
flash the stick rom successfully

i successfully install the I545_OC1_Stock_Rooted_ROMwNK4_BL.zip and its working very well . i think there is something wrong with deOdexed rom i tried 3 time same result and when i try stock one it booted and working very good... hope u fix it soon thanyou so much for your work
[Verizon Samsung Galaxy S 4] jeff b:
I flashed the stock, then decided I wanted the deodexed. Now stuck on the samsung custom screen.

How do I get back to loading the stock version? Use the full wipe odin tar? Just wondering since it says do not use the full wipe odin if you accepted the OC1 OTA and when I flashed the stock version it includes the OC1
[Verizon Samsung Galaxy S 4] Mowgli87:
Flashed the stock version this morning. Still in the process of restoring my stuff and removing bloat with Titanium Backup.

So far everything is working great. Thanks for your work!

Edit: I spoke too soon. Titanium backup will not backup to my SD card. Any idea why?
[Verizon Samsung Galaxy S 4] steepdgaf:
Are you on odexed or deodexed. On the deodexed I was able to flash xposed and then wanam has an option to write to SD. If on odexed try an app from play store for SD fix, one I tried was for KitKat but worked.
[Verizon Samsung Galaxy S 4] Mowgli87:
I flashed the odexed version. I had completely forgotten about the SD Fix app. That solved the problem.
[Verizon Samsung Galaxy S 4] FacinateMe:
Ok So I have a issue with root access. I thought this process was to keep root? well I tried to uninstall some bloat ware and it is telling me I don't have root access .. So following directions as stated

I don't seem to be having the same wifi issue but I want to get rid of the bloat ware .. Please help .
[Verizon Samsung Galaxy S 4] rbird2:
Had the same concern. I used "SDFix: KitKat Writable MicroSD" on Lolipop and now the SDCard works..

SDFix: KitKat Writable MicroSD

https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en

Run SDFix and reboot. Worked for me.
[Verizon Samsung Galaxy S 4] jeff b:
FYI restoring with the full wipe odin worked. Then followed instructions to get back root and installed the odexed version and now am good (other than really wanting wanam xposed)
[Verizon Samsung Galaxy S 4] aznjosh:
Deodexed works perfectly so it's something on your end. Either use gigilies method and use safestrap to flash the rom or try using an older version of flash fire.
[Verizon Samsung Galaxy S 4] dwhit24:
Clock App issue

Is anyone else having this problem? I am and cannot find an answer. Please let me know if you have any helpful information. Thanks!
[Verizon Samsung Galaxy S 4] {davros}:
where are you getting the xposed that works? I get a not yet compatible error