yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Tech 4 9:
You/are/thu/man (clapping impatiently like crazy person) ;)
[Verizon Samsung Galaxy S 4] klabit87:
Awesome! I made one of my own today also.

Just haven't tested it yet.

Thank for all your great work.
[Verizon Samsung Galaxy S 4] muniz_ri:
DeOdexed version added to OP.
[Verizon Samsung Galaxy S 4] ATGkompressor:
Thank God for deodex! Time to get XPOSED!
[Verizon Samsung Galaxy S 4] Tech 4 9:
Downloading now...
[Verizon Samsung Galaxy S 4] PartyDroid:
downloaded deodex

i got a verizon warning sign saying not correct software (the short version)
[Verizon Samsung Galaxy S 4] muniz_ri:
Use TiBU Pro to freeze SecurityLogAgent.apk.
[Verizon Samsung Galaxy S 4] ATGkompressor:
I'm lost...Did this occur after flashing the deodex version? During boot?

How would he freeze SecurityLogAgent.apk if this is happening in boot?
[Verizon Samsung Galaxy S 4] muniz_ri:
I am assuming he booted into the ROM and got the annoying security warning. If that is not he case then I would be interested in details of what exactly he flashed and how.
[Verizon Samsung Galaxy S 4] muniz_ri:
Are you saying that wifi is working?
[Verizon Samsung Galaxy S 4] JFam5:
Yes it's working just fine on a 5 Ghz channel. Haven't tried 2.4 Ghz but sure that will work too.
[Verizon Samsung Galaxy S 4] muniz_ri:
Great News! I thought Vz threw us a curve ball. I must have screwed up the first ROM. Thanks for testing!
[Verizon Samsung Galaxy S 4] EdrickMG:
In gonna go a head and try it wifi was the only I was waiting
[Verizon Samsung Galaxy S 4] JFam5:
I do have a problem with my WiFi locking up every once in a while and I think it's some of the new modem tweaks. I can drop WiFi and it will run on cell data. After a minute I turn on WiFi again and I'm running for a short while. It was doing that while on nk4 as well.
[Verizon Samsung Galaxy S 4] muniz_ri:
OK, thanks again. I will be interested in hearing if others have the same issue.
[Verizon Samsung Galaxy S 4] skepticmisfit:
would I be able to uninstall safestrap from lollipop? can I do it from my current custom ROM?
[Verizon Samsung Galaxy S 4] muniz_ri:
Yes, you can flash from any build/rom. Once updated to 5.0 you will need to install busybox and safestrap then use safestrap app's uninstall function.
[Verizon Samsung Galaxy S 4] jam0688:
Im still testing anyways ?lol
[Verizon Samsung Galaxy S 4] Jeezy831:
Confirming that flashing with Safestrap worked. I flashed modules immediately after installing rom, and can confirm WiFi is working without locking up.
[Verizon Samsung Galaxy S 4] muniz_ri:
Great, thanks for testing with Safestrap, it should also work with FF. I must have made a mistake when I created the initial ROM (the latest ROM has been moved to the OP).

And FYI......a new FF v0.17 was just released. Make certain that Everyone uses the latest version. Thanks All for your patience and to all of the testers. Enjoy!
[Verizon Samsung Galaxy S 4] ATGkompressor:
U flashed OP in safestrap? With what modules?
[Verizon Samsung Galaxy S 4] notonmdk:
Thanks for all your hard work. Are there any plans to test the possibility of downgrading from nk4 to mdk?
[Verizon Samsung Galaxy S 4] Qball21:
Will you lose root if you flash the latest version you posted?
[Verizon Samsung Galaxy S 4] Jeezy831:
Confirming that it worked with FF v0.17 and flashing modules with Odin after that. Wifi is also staying on. Thanks for the work man
[Verizon Samsung Galaxy S 4] muniz_ri:
Awesome, thanks!

Also, to avoid confusion I believe you mean the OC1 kernel not modules. I posted the OC1 kernel for Safestrap users only. FF will flash the OC1 kernel already included in the ROM.
[Verizon Samsung Galaxy S 4] jhud25:
Before I take the plunge, can anyone verify wifi tether/hotspot is working?
[Verizon Samsung Galaxy S 4] muniz_ri:
Funny, I was just uploading the I545_OC1_TetherAddOn. It should work but someone will need to test before I add to the OP. Use FF's "Flash zip or ota" option but do not wipe.

Worst case you bootloop and will have to Odin flash NC5 and start over.
[Verizon Samsung Galaxy S 4] EdrickMG:
Confirming the file worked awesome, muniz_ri I've been following your work since NC5 just want to thank you and all testers for flawless work..

For tethering I've always used xposed with no problems. But flashing would be cool also thanks!
[Verizon Samsung Galaxy S 4] Jeezy831:
Tether is confirmed, tested connection on my wife's ZTE Max.
[Verizon Samsung Galaxy S 4] Osama Chishty:
what is Deodexed version can u explain that..?
[Verizon Samsung Galaxy S 4] PartyDroid:
I followed your information to the T. I used ff v.17 i installed it then watched it run through all the words in the background then it said wiping and rebooting then after it rebooted thats when it said pretty much SORRY wrong Software installed. PS yes i also did the 10 min screen setting too.
[Verizon Samsung Galaxy S 4] EdrickMG:
Thanks Muniz for detox version... I don't know if rush into xposed what's the suggestion right now?? Thanks again
[Verizon Samsung Galaxy S 4] mike.s:
This is why this thread is 60 pages long. Off-topic questions with answers which can be easily searched for.
[Verizon Samsung Galaxy S 4] tadpole1969:
will this work if im on 4.3 i545VRUEMK2 ? or do i have to go a different route to get the i545_oc1-5.0.1 on my s4,

and if it will not work with mk2 can someone put me on the right path to do it
[Verizon Samsung Galaxy S 4] Stryke_the_Orc:
Thread cleaned.

Try to be more respectful of each other, and remember the rules - Search before posting is rule #1 of the rules you agreed to when you created your account.

Thank you.
[Verizon Samsung Galaxy S 4] muniz_ri:
Thx, I have not heard anyone else report this issue so I would consider it an anomaly I guess.
[Verizon Samsung Galaxy S 4] muniz_ri:
No, FF does not work properly from MK2. You must first update to kitkat nc5.
[Verizon Samsung Galaxy S 4] muniz_ri:
I do not know the status of xposed, i don't use it, but received requests for deodexed version. I guess we will now soon find out...
[Verizon Samsung Galaxy S 4] ATGkompressor:
To wait until a more stable method is found. As soon as I get the deodex version flashed I'm gonna jump into xposed. Some users are reporting that a flashable version of xposed is working but with certain limitations as to what modules will operate.
[Verizon Samsung Galaxy S 4] EdrickMG:
Thanks I'll wait for more stability on xposed, history showed us being impatient in this kind of things bring more problems if this is your daily phone
[Verizon Samsung Galaxy S 4] Tech 4 9:
I did fresh odin of NC5, rerooted, installed su+busybox, flashed deod-rom after all wipe but sd. ROM seemed fine until I flashed sdk after installation of xposed. I flashed sdk+cache wipe+delvik wipe. Got android apps updating then reboot. Result: Caller ID fc, Amazon App suite fc, Amazon music "crashes", Google services fc (and seemed as if it wasn't installed at all as I was able to install from backup getting install screen as opposed to update screen), Google play will not open/fc. Tried multiple installs, wipes and restarts. I did get the amazon stuff to chill out by disabling in app manager. Current status is rom seems to fine, no fc after last reboot....only current issue from those mentioned is no google play or services. But xposed did load.
[Verizon Samsung Galaxy S 4] killnut:
What the difference between -*I545_OC1_Stock_Rooted_ROM_wNK4_BL and -*I545_OC1_Stock_DeOdexed_ROMwNK4_BL?
[Verizon Samsung Galaxy S 4] muniz_ri:
See here: http://xdaforums.com/showthread.php?p=60954071
[Verizon Samsung Galaxy S 4] aznjosh:
Hey did you try http://xdaforums.com/showpost.php?p=60957657&postcount=528
[Verizon Samsung Galaxy S 4] grimjeeper:
Has anyone had issues with restarting after a dead battery that has been charged, then having a system not responding message once it finally boots?

I think it may be some left over files from my last room. Would a full wipe back to nc5 then start over be a good idea or can I fully wipe this room as is and start over?
[Verizon Samsung Galaxy S 4] jam0688:
Hey has anyone had any issues flashing with FlashFire since the newest update? I had issues trying to flash a deodexed stock rooted version a buddy of mine [MENTION=4168602]klabit87[/MENTION] and all it does is reboot after installing and it just boots up to stock as if i never flashed it. Ive done several other deodexed tests for him and it does the same thing. I thought maybe something in my system archive may have been messed up so i odined back to nc5 rooted and flashed Oc1 rooted with nk4 bootloader and it still does the same thing. And before it has never done that until the latest update. Im downloading the op version that Muniz_Ri posted and im gonna try it and see if it does the same thing.
[Verizon Samsung Galaxy S 4] richh57:
I carefully followed the latest instructions to install OC1 and now I only get a boot into the "Samsung Custom" boot screen. I 'did' have 4.4.2 root access and I 'did' set the screen timeout to 10 minutes. I used the DeOdex'd ROM and it all seemed to be working fine until it rebooted. I saw the messages about reloading modem, etc. and I saw a message about loading system that seemed to take a while, but I can't say that I saw anything after that. The phone vibrated twice and then rebooted.

The only thing that I ran into that may be odd is that FlashFire complained that the SuperSU version was too old and needed version 2.40 or higher. So, I downloaded 2.46 from the store and installled it. Then when I ran flashfire, a message popped up that asked whether I wanted to grant root to FlashFire and I clicked on 'grant'.

I can only boot into "Samsung custom" and then I need to pull the battery. What is the best way to recover from this point? I tried just using Odin to reload the NK1 and the NC5 kernel into the AP slot, but that did not fix ti problem. Any ideas?
[Verizon Samsung Galaxy S 4] jam0688:
I just flashed the oc1 tether add on and it flashed fine. We're thinking it's maybe something wrong with his scripts. They aren't taking well with FlashFire. Im still gonna test yours [MENTION=4708661]muniz_ri[/MENTION] and see how it goes.
[Verizon Samsung Galaxy S 4] muniz_ri:
Check FF's last log after flashing. It should spell out any errors.
[Verizon Samsung Galaxy S 4] Kakamarsson:
Well, im on a good Internet right now.

Im still on MK2 and wanna go to NC5 and then use FF as the OP said. Can anyone show me a good method to do that. The only one I found in the forum uses Safestrap. If possible, I want to do this without SS.

Thank you!
[Verizon Samsung Galaxy S 4] klabit87:
I will get a closer look once I am able to test myself.

We are going through some bad weather in our area and I don't want to attempt to Odin in a storm.

Is there a specific FlashFire version you recommend? I've heard of problems with v18 that weren't present in v17.

I can explain in more detail via pm if/when you get a spare moment.

I just don't see what I'm missing.

You could backup everything and use the full-wipe NC5 Odin package.

then Towelroot, and upgrade to OC1 via the OP.
[Verizon Samsung Galaxy S 4] ATGkompressor:
The deodex version in the OP contains CERT.RSA, CERT.SF, & MANIFEST.MF in the META-INF folder. The odex version doesn't contain this. Maybe why the deodex version isn't flashing right?
[Verizon Samsung Galaxy S 4] klabit87:
Possibly.

I just sat down to look at it.

Edit:

Those files are generated when you sign the zip.

I try to sign all of my zips.

Edit 2:

If it helps bring anything to light, the log from my last failed zip seemed to think it was an aroma script?!

I have nothing resembling aroma in any of the zip so I don't know what that could mean.

All I did with the script was modify it so that i was only flashing my modified system.img.ext4.

Any ideas [MENTION=4708661]muniz_ri[/MENTION] ?

Thanks for your time in advance.
[Verizon Samsung Galaxy S 4] ATGkompressor:
If they are removed, will it affect the outcome of the flash? And, if that signature is being checked by FlashFire, could it be possible that it is somehow inadvertently causing or triggering a check at boot, giving users the unauthorized software warning?

I've noticed that taking a backup in FlashFire and checking the last.log, that Triangle Away is mentioned in that log. I'm trying to figure out why this is happening while keeping in mind FlashFire is still in BETA.
[Verizon Samsung Galaxy S 4] klabit87:
I haven't seen anything in the FlashFire thread that indicates it checks zip signatures.

Besides the behavior is the same whether i sign the zip or not.

I have made a backup but haven't tried restoring my backup.
[Verizon Samsung Galaxy S 4] muniz_ri:
I am not clear on the problem you are trying to solve for.

Are you saying that you are getting the "unauthorized software" after flashing my rom? Or some other .zip or rom?
[Verizon Samsung Galaxy S 4] klabit87:
Delete
[Verizon Samsung Galaxy S 4] Tmosco:
hi

please i want to know if this method will work on towelroot.That the app i used to root my kitkat
[Verizon Samsung Galaxy S 4] muniz_ri:
Sorry, but that is completely off topic. Please take elsewhere, thx.
[Verizon Samsung Galaxy S 4] ATGkompressor:
No
[Verizon Samsung Galaxy S 4] klabit87:
I understand. I will move this issue elsewhere.
[Verizon Samsung Galaxy S 4] rmedure:
Issues with selinux enforce

Is it normal to be stuck with selinux enforce after this?

Came from Hyperdrive 20 ROM, rooted. Unfortunately I followed another guide (apparently copied from here) before I found this thread. That guide linked to your I545_OC1_Stock_Firmware.tar.rar with md5 = 312d9a7b2ad31b07d92d9e26a732f4d5 and to your I545_OC1_Modem+NK4_Bootloader.zip with md5 = 71d49337586dd010fcc390fbb4d6260e. And the guide replicated the "alternative firmware method" in the OP but with everroot selected of course. I might have missed the step to uncheck everything under 'process cache'.

Everything seems to work fine, and I surely have root access. But I'm at my wits end trying to figure out how to get selinux permissive to work. In the meantime I have no write access to the system folder. I've tried using the tried/true SELinuxModeChanger app ... even located a newer version 3.2. And I've tried a variety of terminal/command line methods.

Do I need to reflash the latest I545-OC1_Stock_Rooted_Firmware.tar? I would imagine not since it looks like this is a bone stock ROM with su pre-installed.

Any help on getting write access to the system would be greatly appreciated.

Cheers!
[Verizon Samsung Galaxy S 4] ATGkompressor:
Yes it's normal. Pretty sure SELMC doesn't work on this. setenforce=0 just reverts after boot without ever actually working. The constricting grip that is Samsung Security is ever more tightening with each passing OTA.
[Verizon Samsung Galaxy S 4] Kakamarsson:
Well, tried to make your instructions with the new rooted file, but happened the same.

Seems that FF wont work with mk2.

So i odine nc5, rooted, and ran you new 1 method (with no firmware file).

Im running Lollipop perfectly. TY very much!
[Verizon Samsung Galaxy S 4] rmedure:
SELinux Permissive

I can't get it to go permissive AT ALL. I'd be reasonably happy if with it resetting on reboot. The way it is now I cannot delete a single app in the system folder. Or install any system apps.
[Verizon Samsung Galaxy S 4] wonger007:
Other than the SE Linux not being able to be permissive....

I have an exchange email program (boxer) that requires administrative rights to my phone. What happens is that after a reboot my lockscreen security setting changes from PIN (required by boxer... well my companies exchange server) to a regular swipe. To get it back to PIN i have to jump through some hoops.... If boxer didnt have administrative rights to my phone then it works normally.

edit... well screw boxer... using cloudmagic now... everything is good...
[Verizon Samsung Galaxy S 4] PartyDroid:
I've noticed you update quite often which is really nice. But i also have not seen an update log so that I can see what it is that you"ve updated. could you please give an update log? Please and Thank you alot 4 ur hard work you give us here at XDA.
[Verizon Samsung Galaxy S 4] wonger007:
I dont think the ROM itself was updated... and thank you for serving our country, hope you had a killer memorial day.
[Verizon Samsung Galaxy S 4] PartyDroid:
Ok. &'d I worked all weekend and yesterday too rebuilding 5 computers dumping them and reinstalling new software & programs & redoing my Cell phone for the 9th time this weekend too.
[Verizon Samsung Galaxy S 4] wonger007:
You werent the only one working on memorial day =) Cause I was too, lucky there was nothing really going on.
[Verizon Samsung Galaxy S 4] PartyDroid:
So true:laugh:
[Verizon Samsung Galaxy S 4] muniz_ri:
The latest changes have more to do with my OCD than any thing that would affect user experience, the system.img remains the same. So there are no plans for an update log.

Plus I put out an experiment or two once in awhile for my own learning (nothing free in this world).

Anyway, at this point I don't plan on anymore updates for this build.
[Verizon Samsung Galaxy S 4] muniz_ri:
Yes, it was confirmed a couple of days ago that FF does not function correctly on MK2. I added a note to the top of the OP.
[Verizon Samsung Galaxy S 4] rmedure:
Write access issues ...

Hmm, I don't have write access to anything on the internalSD. JR Root Explorer can't write to it (and other root file explorers for that matter), JR App Mgr can't uninstall sys apps... but TiBU can uninstall system apps. Oh, and Avast Anti-Theft was able to install itself as a system app.

Anyone have any ideas?

Solved:

Decided to start over, Odin NC5, then flashed the deodexed ROM. :) I figure I'll want xposed at some point soon. Anyway, now the JR Root Explorer can write everywhere; but the JR App Mgr still cannot uninstall sys apps ... I'm going to assume it's a bug since TiBU seems to have no problem. Cheers!
[Verizon Samsung Galaxy S 4] PartyDroid:
OK Thanks
[Verizon Samsung Galaxy S 4] tadpole1969:
ok so i need to flash nc5 with odin correct ? in doing so i will lose the root sence its rooted correct?
[Verizon Samsung Galaxy S 4] rmedure:
Pin Lock Issue

I have the same pin-lock issue. I tried disabling all phone admin accounts and the behavior remains the same. On reboot, pin-lock reverts to swipe-only and I have to go back in and re-enter my pin (by the way, it still requires the old pin to reset the pin).

I looked at build.prop according to one of the previous posts on this issue ... I have security.mdpp.reult instead of security.mdpp; so not sure if I should change that.

BTW, I flashed the deodexed rom. :)
[Verizon Samsung Galaxy S 4] wonger007:
Yea i flashed deodexed too.. butyea removing boxer that used admin fixed it. Gotta find an alternative and there was a better one i felt which was cloudmagic
[Verizon Samsung Galaxy S 4] aznjosh:
Newest v3 of arter97's xposed working on deodexed version of this rom! Thanks!
[Verizon Samsung Galaxy S 4] rmedure:
Well all admin accounts on mine are disabled ... and still no joy. :crying::crying: This is a serious security problem.

---------- Post added at 04:08 PM ---------- Previous post was at 04:07 PM ----------

I think the answer is yes ... but NC5 is super easily rooted with towelroot right? That's what I did.
[Verizon Samsung Galaxy S 4] muniz_ri:
Is anyone else having trouble using lockscreen pin code setting? Or is this an isolated instance due to user modification?
[Verizon Samsung Galaxy S 4] MorpheusER:
I received a refurbished GS4 from Verizon today because my recently lollipop rooted GS4 was having network connection issues had to be returned. Well this refurbished phone came with Android Version 5.0.1, Baseband version: I545VRUGOC1. Is rooting not available yet?
[Verizon Samsung Galaxy S 4] skepticmisfit:
if it came with that, no. can't root
[Verizon Samsung Galaxy S 4] MrGeekGuy:
I'm having the same issue, I flashed the I545_OC1_Stock_Rooted_ROM_wNK4_BL ROM. I've also made sure build.prop has #security.mdpp=none

Also, I'm having an issue with the wifi, ever since I flashed I545_OC1_Stock_Rooted_Firmware.tar with I545_OC1_Modem+NK4_Bootloader, it's very weak. Even when I odin back to NK4 it stays weak. Strange thing was I flashed I545_OC1_Stock_Rooted_ROM_wNK4_BL and wifi was still weak, I flashed the I545_OC1_TetherAddOn, it was strong for an hour, but went back to weak.
[Verizon Samsung Galaxy S 4] muniz_ri:
I see what I did....I used the same system.img file as for the MDK bootloader users which required the security.mdpp=None line to be commented out due to the presence of the MDK bootloader. Just uncomment out the line by removing the # sign and you should be good to go. I will upload a patch to the OP and eventually a new ROM.

Wifi is likely an issue with your router or modem. Can't help you there.
[Verizon Samsung Galaxy S 4] rmedure:
Thank you!! :good::good: Worked for me (edit build.prop, reboot, change back to swipe, change back to pinlock, reboot again).
[Verizon Samsung Galaxy S 4] MrGeekGuy:
Hi muniz,

I did as you suggested, removed the #, and it still went back to the swipe only.

As far as Wifi, it worked perfectly before on NG6, when I flashed to OC1, it went really weak (I have to be within 3 feet of my router to get full bars, all my other devices on my network are fine) I'll try to odin back to NK4 later and see if I can't get it going again.

Also, thank you for all your work, you're awesome.
[Verizon Samsung Galaxy S 4] muniz_ri:
No worries, also see the post above. Looks like it requires a couple of reboots for the new build prop to stick.
[Verizon Samsung Galaxy S 4] jhb04jhb04:
Thanks so much for sharing! I thought it was only me! I am experiencing the same issue as well. I thought it might have a Lollipop issue so I Odin'd back to Nk1 but my wifi has never been the same. Also, I know it's not just my home network because the performance has also suffered at the office where I am literally in the same room as the router.
[Verizon Samsung Galaxy S 4] MrGeekGuy:
Yup, I read that just after I posted, and did as suggested, and it worked! Thank you!

---------- Post added at 10:29 PM ---------- Previous post was at 09:50 PM ----------

Well, thats two of us, hopefully there will be more, so we can compare notes, and see if there is a solution.
[Verizon Samsung Galaxy S 4] kdo23:
I am wondering if anyone has had any success deodexing the odexed version of this rom. I flashed early after the keep root method was released but do not wish to wipe just for deodex. Or if a no wipe deodex exist to flash with flashfire?
[Verizon Samsung Galaxy S 4] ATGkompressor:
If I am on the odex version of this ROM and want to flash the deodex version, do I need to downgrade back to nc5 and start over? Or can I just wipe and follow FlashFire protocol?
[Verizon Samsung Galaxy S 4] AndroidCraig:
Flashed this update and now phone keeps dropping to 3G

All,

I flashed this update from a replacement phone I got for one that had a busted screen. Flash of the deodexed rom went fine, and it restored almost all my apps, so I'm rooted on Lollipop for which I'm happy.

However since flashing this the phone won't stay in 4g for more than a couple of minutes before dropping to 3G. This happens everywhere, work, home, on the way to work, I live in So. Call so I know it's not the area. None of my other phones have ever had this problem. as I didn't use the new phone before rooting and updating it last night I don't know if it's the device or the 5.01 update. As dropping to 3g kills my battery I really want to get my 4G back.

Has anyone else had this problem ? If so what did you do to fix it? If not what can I do to fix it?

Thanks for any help.
[Verizon Samsung Galaxy S 4] MinutemanZ:
Neither solution stuck at first. At first I tried changing the screen lock security settings as soon as the phone booted. After a while, the PIN I entered no longer worked to unlock the phone. If I rebooted then it worked the first time. The solution was to wait until I was certain the phone was fully booted before I changed its screen lock settings.