yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] albertdc:
Skola28

Your problem is not from the security issues you had. It is from the MK2 bootloader.

Look back at post #1011 for the solution. The original solution was posted way back, but it was quoted/summarized there. (I'm on my phone so excuse me for not replicating it). One small edit and you'll be good to go.
[Verizon Samsung Galaxy S 4] skola28:
Albert: Made the change to the build.prop from post #1011 - (added a # before the indicated line)

and FML all of the options are available! AND THEY STUCK! You are a genius. Really really really wish I had more patience than I do - would have found this solution last night and not reflashed a half dozen times. I'm going to fully reboot, reflash, redo everything to 'clean up' and I'll report back.
[Verizon Samsung Galaxy S 4] albertdc:
LOL. Thanks. But I am NOT a genius! I did not figure out that solution, I just had to do it and remembered reading about it. The credit goes to all the people in the thread that figured it all out to begin with.

Glad it's working.
[Verizon Samsung Galaxy S 4] V0latyle:
Nope...auto rotate still doesn't not work for me, and the S View function doesn't work properly.
[Verizon Samsung Galaxy S 4] skola28:
After the wipe/reflash, I setup my phone and allowed it to download everything it needed. Modified the build.prop once again (since the reflash reset it) and restarted. Added my work Google Apps account, enabled pin.

Unfortunately, now when I select to encrypt the phone, after I select "Encrypt" the device changes to a Green Android on a black background and then resets. It doesn't actually encrypt the phone.

http://forums.androidcentral.com/at...or-green-android-gears-20140108_081737-1-.jpg

That is the image that comes up briefly.

Do I need to uninstall or deactivate SafeStrap somehow? Do I need to re-enable that security setting in the build.prop?
[Verizon Samsung Galaxy S 4] dgutierrez04:
No issue for me. Try reinstalling the rom again and check the md5 before u flash make sure they match.
[Verizon Samsung Galaxy S 4] lookimback:
I had went from MK2>NC2>NC5 a few weeks ago and had the FCs and it seemed slower. This morning I tried using SS to flash the v2 stock-root-deodex.zip. I checked the md5 first. Do I need to Odin the other stuff again? If I do need to Odin, can I do so without wiping again? Thanks.
[Verizon Samsung Galaxy S 4] skola28:
So I installed Safestrap and deactivated the Safestrap recovery.

Rebooted, tried to enable encryption - same result - reboots phone but doesn't encrypt

I reverted my build.prop to remove the #, rebooted, and tried to enable encryption. Same result - Reboots but not encrypted.
[Verizon Samsung Galaxy S 4] dgutierrez04:
Well for u to kill those bugs it will be best if u start from scrach. U will less likely experience any bugs. Yea u can try a dirty flash but it might be possible it might not fix ur bugs. But like I said start a fresh built and if u already have the other stuff already it wouldnt be necessary since u already have it. But it wouldnt hurt to do it again.
[Verizon Samsung Galaxy S 4] clkinsler:
Lock screen options grayed out

"Change the following in build.prop found in system folder using a root explorer app. Es file doesnt seem to work so try another.

security.mdpp=none

To

#security.mdpp=none "

Reboot, worked in Deodex
[Verizon Samsung Galaxy S 4] skola28:
I did that, and it fixed my inability to select the various lock screen options. HOWEVER, now I am stuck unable to encrypt my phone.
[Verizon Samsung Galaxy S 4] lookimback:
OK, I'm going to try again from scratch later. I'll just have to back up everything first. Thanks!
[Verizon Samsung Galaxy S 4] zmedhaug:
Good suggestion. Will try when I mess it up again But I am thinking it is one of the knox apps. I'll report back
[Verizon Samsung Galaxy S 4] punkwhan:
Thanks.

I didn't do the advanced wipe.

It looks like that was it.
[Verizon Samsung Galaxy S 4] Beakhole:
Toggles

I went in, reordered the toggles to how I want and then saved the zip file and reflashed that Toggles zip but it didn't take effect. I'm on your deodexed ROM.

Did I do something wrong? Sorry to bother you again.
[Verizon Samsung Galaxy S 4] Hollywood67:
Can't find this file. Can someone give me a step by step?

I was using fx w/root expl.
[Verizon Samsung Galaxy S 4] clkinsler:
I used Rom Toolbox (pro) went to root browser/scroll down to system folder then build.pro file. You will need a text editor (I have RB Text Editor) Worked like a charm
[Verizon Samsung Galaxy S 4] dgutierrez04:
OTE=Hollywood67;52800794]Can't find this file. Can someone give me a step by step?

I was using fx w/root expl.

https://play.google.com/store/apps/details?id=com.estrongs.android.pop

I use this folder to edit it and go into the built.pro.
[Verizon Samsung Galaxy S 4] swears11:
Does anyone have a fix for the Auto-Rotate not working?

Thanks.
[Verizon Samsung Galaxy S 4] Hollywood67:
"Change the following in build.prop found in system folder using a root explorer app. Es file doesnt seem to work so try another.

security.mdpp=none

To

#security.mdpp=none "

I am still unable to save the file to see if this change works for me.

I have tried:

RB text editor

ES note editor

FX text editor

SQLite editor

This is such a minor issue, but any other ideas?
[Verizon Samsung Galaxy S 4] Surge1223:
Mount system rw first. Open terminal emulator and type

su

mount -o remount,rw /system

Then make the edit with a file editor and the save should stick.
[Verizon Samsung Galaxy S 4] Hollywood67:
Honored to have the OP chime in and reply...

how to "mount system rw".

how to "open terminal emulator'
[Verizon Samsung Galaxy S 4] lookimback:
[MENTION=4949937]Hollywood67[/MENTION]

I used FX w/root explorer and FX text editor without a problem. Navigate to the System folder as a root user then click the padlock icon to mount the System folder rw. Just remember to click the padlock again when you're done to remount System as read only.
[Verizon Samsung Galaxy S 4] Hollywood67:
Success!!
[Verizon Samsung Galaxy S 4] chris23445:
Hate to bother you Surge, but do you have any idea why auto-rotate is not working? I'm on the deodexed ROM.
[Verizon Samsung Galaxy S 4] Surge1223:
My auto-rotate works fine, does anyone else have this issue? It could be bootloader related since im on the NC2 bootloader and mine works.
[Verizon Samsung Galaxy S 4] gadget!:
Auto rotate works fine for me.

NC2 bootloader

Sent from a Galaxy S4... Far far away
[Verizon Samsung Galaxy S 4] lookimback:
My auto-rotate works fine on NC5. Not sure how to tell what bootloader I'm on.
[Verizon Samsung Galaxy S 4] tshelby73:
Auto rotate works for me mk2 bootloader

Sent from S4 using Tapatalk
[Verizon Samsung Galaxy S 4] mhaas75:
Mine is fine. MK2 Bootloader NC5 everything else.
[Verizon Samsung Galaxy S 4] chris23445:
Those are the two people that I see in the thread with the issue also. But it seems multiple people do not have the issue.
[Verizon Samsung Galaxy S 4] downhillvinnie:
Icon settings

So I set the pulldown notifications icons to my preferences, wifi, bluetooth, gps, sync, once I reboot they go back to stock one's. I tried SQL Editor to delete the ones I dont use, but they come back on a reboot....Any ideas
[Verizon Samsung Galaxy S 4] swrght13:
I have the issue with auto-rotate. I'm on NC5 bootloader
[Verizon Samsung Galaxy S 4] dtomlin:
No issues with auto rotate or tiles. NC5 bootloader and your nc5 deodex.
[Verizon Samsung Galaxy S 4] Surge1223:
Alright I have some free time today so lets try to grind out some of these nagging issues, is there anything in common those with auto rotate issues did? Like what mods did/didnt you flash? Are you using the s5 interface?
[Verizon Samsung Galaxy S 4] clkinsler:
Everything and I mean everything is working for me now. I am on MK2 Bootloader, when I initially did the install I did the Odex version and my screen got stuck on the Verizon splash screen. I ended up soft bricking and downgraded back to MK2 and started from scratch, I did the Deodex and everything went great, the only thing I had to fix was the security setting in build.pro. My Bluetooth (playing in my car and earpiece), WiFi, & sound are all working flawlessly.

Thanks Sure1223, you are a genius for putting all of this together and supporting the community.
[Verizon Samsung Galaxy S 4] pscshuler:
The only issue I have been having are my tiles reset themselves after I reboot. Tried flashing the zip & clearing the cache but still won't stick. (NC5 deoxed, NC2bl)

Did run into an issue a couple times where I could not get any sound on outgoing calls, connects but no sound either way. Reboot fixed it. (used fast reboot a few times, think that may be the issue)
[Verizon Samsung Galaxy S 4] Beakhole:
Need Help with toggles

Per your previous instructions, I went into the updater-script, reordered the toggles to how I want with a text editor and then saved the zip file and reflashed that Toggles zip but it didn't take effect. I'm on your deodexed ROM. Somehow it always goes back to the same toggles.

Am I doing something wrong?

EDIT: Attached is the screenshot of my issue. This is the order of my toggles after each reboot, even after reflashing the toggles.zip that I had edited to change their order.
[Verizon Samsung Galaxy S 4] apeman81:
I am currently running NC2 up from MK2 on my VZW G4. It runs wonderfully except for one issue. The Samsung messaging app will not employ a sound for notification. It vibrates as set and the reminder function works, just no sound.

Any suggestions?

Thanks
[Verizon Samsung Galaxy S 4] dtomlin:
I deleted the toggled.bak file from the init.d folder. Could that be causing some peoples toggles to revert? I forgot that I had done it. I could be wrong, hell I am a lot, but I believe that it will still read in init.d even if it's renamed with .bak.
[Verizon Samsung Galaxy S 4] Eddie Hicks:
I already installed Safestrap Recovery v3.71 from Hashcode. Can I use that or do I have to install the KK version in the OP? Thanks
[Verizon Samsung Galaxy S 4] lazer9:
Follow the instructions to a T in the OP. You will need to get the SS v3.72 clearly mentioned.
[Verizon Samsung Galaxy S 4] Eddie Hicks:
Thanks I'm new to this Safestrap program. Can I install the version in the OP over the version I have or do I have to remove it first?
[Verizon Samsung Galaxy S 4] -Lawless:
This is how I did it.
[Verizon Samsung Galaxy S 4] Eddie Hicks:
Thanks Lawless, I found the solution. I had to run the safestrap installation file and choose uninstall recovery. It was much more simpler than I expected.
[Verizon Samsung Galaxy S 4] tech_head:
No issue here with MK2 BL.
[Verizon Samsung Galaxy S 4] Beakhole:
Delete

Did you use the odexed or deodexed ROM? I'm on the deodexed. I did what you suggested and deleted the toggled.bak from that folder, then reflashed my toggles.zip file with my preferred order of toggles and it still didn't take.

Did you do anything else?

EDIT: Never mind!! It worked! After deleting the file, reflashing, and then manually rearranging the toggles, I rebooted and they stayed how I wanted!!!!!! THANK YOU!! :laugh:
[Verizon Samsung Galaxy S 4] V0latyle:
I dirty re flashed last night (deodexed) and auto rotate works now. S view function still is buggy; it works on home screen and when receiving a call but the in call screen doesn't work.

Also, my toggles reset after every boot...and I can't seem to keep the torch toggle.

Other than that things have been relatively smooth...
[Verizon Samsung Galaxy S 4] Surge1223:
To all - I wrote the instructions in the OP the way they are written for a reason. Please keep that in mind before asking questions. Also to address some common questions/concerns ill add zips to flash that will fix the lock screen security and toggle customization issues along with zips to switch to the stock reboot menu, 4in1 or the extended one i made the default (on the deodex NC5 anyways).

This is 99% the issue, I must've forgot to put the edited "toggles" script in to init.d, the old one renames the file to toggled.bak while the newer one (that I forgot to include) deletes it. Thanks for the find!

Edit: attaching patch here and in the OP. This patch will add toggles, remove the init.d toggle script so that you can save your own customized order of toggles and will fix the lock screen security types issue. This zip is also meant to replace the toggle zip since it also adds the toggles, amogst the other fixes mentioned above. This is for both the stock root deodex and odex roms.

NC5-patch1.zip

Just flash in Safestrap after the rom install or at your earliest convenience.
[Verizon Samsung Galaxy S 4] V0latyle:
Same here except I didn't modify the toggles.zip; I simply deleted toggled.bak. everything is as I want it.
[Verizon Samsung Galaxy S 4] punkwhan:
I'm on the rooted NC5after following the instruction.

My question is if there is any other kernel I can flash.

I just want to be able to modify the colors using Trickster Mod.

It looks like the baked kernel doesn't allow that.

Any suggestion?

Thanks.
[Verizon Samsung Galaxy S 4] budmannxx:
I wasn't having the rotation issue, but I was having the toggles issue. I can confirm this new zip fixes the problem.

Here's what I did:

1. Flash the zip

2. Reboot and organize the toggle tiles in the order I want

3. Reboot to confirm my tile order was preserved (it was)

FWIW, I'm on the deodexed v2, with (I'm pretty sure) the MJ7 bootloader (I went straight from MJ7 to NC5).
[Verizon Samsung Galaxy S 4] pscshuler:
Patch works perfectly Surge. Thanks! :D
[Verizon Samsung Galaxy S 4] tech_head:
Nope.

The kernel is signed.

If you can't do it with the stock kernel, you can't do it.
[Verizon Samsung Galaxy S 4] FireMedic1234:
Am I missing something?

I had root before the OTA came out, and broke it with Odin so I could upgrade. Now obviously I don't have root. Maybe I am missing something but I've installed safestrap and cannot reboot into recovery, what am I missing? Sorry I haven't played around with safestrap at all. i have always been content with a stock rooted version, and since that hasn't happened yet I figured i would give this a try.
[Verizon Samsung Galaxy S 4] V0latyle:
Well damn. I flashed the patch and now my auto rotate stopped working again.
[Verizon Samsung Galaxy S 4] scootier:
If you don't have root safestrap will not work.

first sort that out (depending on baseband version there are different methods. Sounds like your on 4.4.2 so will need to use Surge's downgrade/root/upgrade steps).

then install safestrap and go into app and install recovery.
[Verizon Samsung Galaxy S 4] FireMedic1234:
What am I not getting then. My baseband is NC5, and there is currently no available root for that.
[Verizon Samsung Galaxy S 4] gadget!:
It is complicated simply because there are so many steps involved but read and read again. If you follow the inductions in the OP you should be able to gain root.

Sent from a Galaxy S4... Far far away
[Verizon Samsung Galaxy S 4] engmaad:
I'll try

thanks

:laugh:
[Verizon Samsung Galaxy S 4] FireMedic1234:
Maybe this is what I am missing. Do I use Odin to install one of the BL's that can be rooted, then get into safestrap, and follow the OP method?
[Verizon Samsung Galaxy S 4] gigilie:
hello my name is....

Figured a few of you 4.4.2 Root havin Safestrap lovin users would be kind enough to maybe try one of my new 4.4.2 ROMs or ports they can be found in the Verizon Android Development I'd like some users to post their screenshots for thanks from me plz that'd be DoPE oh n same with feedback I'll take some of that :) Thx (3 new roms in the lobby. FoxHounds, Purified, gDux !!!)

Read step 0 when installing the ROM if you've used mine or surge's upgrade with root method already! NE questions for these ROMs can b answered in their respective threads or in my SAFEUP&Downgrade thread please don't bother Surge with them!

Thanks have a great day,

gogolie
[Verizon Samsung Galaxy S 4] VincentDHam:
After 2 tries this finally worked! Thank you!
[Verizon Samsung Galaxy S 4] Centinno:
I'm having the strangest behavior with SafeStrap. I was able to get all of this going fine, but now when I try to open SafeStrap, it always shows "Unfortunately, Safestrap has stopped." Oddest thing is, I have no other issues and can boot into recovery from the menu and all SafeStrap functions work.

Any suggestions? Thank you!
[Verizon Samsung Galaxy S 4] scootier:
Maybe reinstall the safestrap apk?
[Verizon Samsung Galaxy S 4] Centinno:
Unfortunately, I tried that multiple times and it didn't work. I'm trying something else by re-installing zip file and starting from scratch. Only time will tell...
[Verizon Samsung Galaxy S 4] scootier:
Have you tried wiping davlik cache and cache?
[Verizon Samsung Galaxy S 4] Sir_Eagle:
Have to ask this, so slap me around when I'm done.

If you are on NC5, downgrade, root, SS, upgrade with root, can you then delete SS and keep root?

OK slap away now. :eek:
[Verizon Samsung Galaxy S 4] tshelby73:
That's what I did but I'm on mk2 bootloader

Sent from S4 using Tapatalk
[Verizon Samsung Galaxy S 4] tech_head:
But the disadvantage to that is you can't make regular nandroid backups of your ROM/data.

I like SS because I can backup everything.
[Verizon Samsung Galaxy S 4] Surge1223:
The Safestrap .apk shouldn't have been on your system after you flashed the NC5 rom. You must've forgot to wipe /data when you installed, normally you have to manually install the apk after flashing the nc5 rom and when you open the apk after installing, it will report that recovery is installed. The reason you are having force close issues with SS is because of SELinux policies on the /data partition. You will have to use restorecon to fix this.

su
restorecon -Rv /data/*
restorecon -Rv /data/data/*
[Verizon Samsung Galaxy S 4] Sir_Eagle:
Might give it a go someday.

Ad removal and a couple minor tweaks is all I do anymore with root. Got tired of playing with ROMs. Been waiting but it's beginning to look like this or gigilie's method is going to be the only way to gain root. Probably wait a while longer and see if anyone finds a exploit in NC5.
[Verizon Samsung Galaxy S 4] k1mu:
You're using a version of Safestrap that's not supported on VZ device; what you're seeing is why it's not supported.

What happens is that Safestrap can't read one of it's configuration files at startup, causing it to crash. It's a SELinux thing, since the file (/system/etc/safestrap//flags/version) can't be read even if I set the permissions to allow everyone to read it.

I haven't tried the restorecon thing, but that may fix it.
[Verizon Samsung Galaxy S 4] Hollywood67:
Thanks for the explanation. I have been wondering about that, just didn't post about it.
[Verizon Samsung Galaxy S 4] srdryl:
I was wondering the exact same thing.....when u get a response please let me know.
[Verizon Samsung Galaxy S 4] Surge1223:
the 3.72 SS apk definitely works on vzw s4. The reboot menu in the apk doesnt work for us or att, this is a kk issue it doesnt work because the reboot binary is linked to toolbox. I manually fixed mine by replacing /system/bin/reboot with a stock one and setting its perms (chmod 755) so my 3.72 SS apk completely works on my phone (im on my my nc5 deodex)
[Verizon Samsung Galaxy S 4] obxftbll1:
Wifi Problem on NC5

So I updated to 4.4.2 via MJ7 -> NC2 -> NC5. Everything works fine, except I'm having a few problems with wifi. When I originally connect to wifi (imput username and password because it's my college's network) everything works fine. However, after a while, wifi stops working. Everything indicates that I'm still connected to a network, but I can't browse the internet, refresh Facebook, etc. until I turn wifi off and use mobile data. If I want to use wifi again, I have to turn it back on, re-sign in to my school's network, and go from there. I was wondering if anyone has encountered any similar problems and if there was a way to fix it. (Possibly flashing the jfltevzw-FN2-modules or reflashing the NC5 modem?) Thanks!
[Verizon Samsung Galaxy S 4] sinner822:
I have no problems with safestrap. However i do restore all my apps and restorecon in a flashed zip no matter what rom I run. I have been running hot and also had a card run read only... I believe this happens from titanium backup if you try to rename another folder for backup.. Not the first time it has happened to me... Happened to me on a SanDisk and a Samsung card.. I believe it is titanium... Recovered card by formating in Linux and reflashing rom with new ID... But all in all is all running smooth.
[Verizon Samsung Galaxy S 4] k1mu:
The problem I'm having is caused by the /system/etc/safestrap folder being locked down by SELinux. It tries to read /system/etc/safestrap/version at startup and is denied, causing Safestrap to crash when it tries to read the version number. Easy fix.

I suspect that what you end up using your technique gives you an older SELinux policy than what I have (I used the zip in Safestrap recovery to update my phone - muniz_ri's upgrade technique.)
[Verizon Samsung Galaxy S 4] decaturbob:
att ss 3.72 functions on verizon S4 but it definitely has issues with verizon S4 and why hashcode hasn't endorsed using it on verizon phones and why he hasn't issued verizon based ss yet.
[Verizon Samsung Galaxy S 4] lazer9:
And thanks to [MENTION=4939386]Surge1223[/MENTION], it does work well enough to run his wonderful base NC5 rom to even allow us WHO desire to be on KitKat & ROOTED. :good:

Also, at least for me, I can perform and restore Nandroids with no issue whatsoever. Only thing I'm aware of that SS 3.72 won't work doing is running ROMS in slots which is not a personal preference to me anyhow due to space limitations on internal SD.

To each his own I guess.
[Verizon Samsung Galaxy S 4] DjSkreem:
My phone was stuck at the Verizon screen the cache flashed but did not install when it reached the recovery it failed the second option also failed for me so I'm back on the unrooted 4.4.2 I'll stay on thus rom until it gets another root or the official come out
[Verizon Samsung Galaxy S 4] Silassi1:
Yes follow surge's instructions to the letter...I was getting the cache not installed error and followed what he said to resolve it ( downgrade to mk2, rebooted phone completely - I went through the entire setup wizard) then I rebooted phone into download mode and did exactly what he said about using heimdall to flash mk2 cache and recovery. Then I rerooted with saferoot, installed safestrap 3.71 then followed surge's directions on upgrade. The one thing I did differently here as to my previous tries was to go into safestrap advance wipe menu to wipe everything but sdcard. Before I was just using the first wipe option and the phone would not boot it would get stuck on the red Verizon splash screen and kept on vibrating.

Since i got it working I did the re downgrade then upgrade about three times now just for the heck of it and it worked every time!
[Verizon Samsung Galaxy S 4] touche112:
Figured out my problem.

You have to go into ADVANCED WIPE in SafeStrap, and check EVERYTHING except for SD Card. By default, SafeStrap does NOT wipe /system!

Also, the first boot takes a long time. :o
[Verizon Samsung Galaxy S 4] Surge1223:
Just letting everyone know:

1. Yes, I'm aware of the two harmless FC's closes on boot. Yes that's my fault. Sorry.

2. If you cant get WiFi to work because you dont know how to use bypasslkm you might get better help in Q&A, my priorities were not getting an easy way to get WiFi to work or creating a ROM that was flawless (works fine for me though..)

3. Please keep questions/comments related to the upgrade/downgrade methods.

Thanks
[Verizon Samsung Galaxy S 4] Scottchy014:
After adding the files to step 7, could you just uncheck the "auto reboot" and then hit start so that you don't have to worry about restarting into download mode again for step 8? Maybe I'm wrong but this may take care of some issues faced with step 8.

Edit: After using Odin on my wife's old Samsung Charge, I noticed that I had to close out Odin and restart to flash the next .tar. If I didn't, I would get a "fail" indication. Just an idea. It also saved my rear end when I rooted a Sprint Note 3 KitKat just the other day.