Database Info

Living with Root and Knox (SELinux = enforcing) - Tipps n Tricks collection

So you want to keep (knox) warranty and still use root?
Well there is RDLV and the "forbidden" Tool for that, BUT you will still have SELinux on enforcing mode, which means you don't have full control even with root. While technically most things still do work, they might work a lil different or need a different approach.
Lets collect our findings here...
---
First of all, remounting system with apps like solid explorer does not seem to work.
A workaround for this is to run the following command in terminal or through quick terminal etc:
Code:
/system/bin/mount -o rw,remount /dev/block/mmcblk0p2 /system
This command gets through where other methods fail. Once you have mounted the system writable like this, you can go back to your root explorer app to delete things etc on system partition. Solid explorer gives me error messages still when I delete apps from /system/app/, but they still disappear / get deleted.
---
This also brings me to my next workaround:
To delete system apps and not just freeze them with Titanium, you need to remount system like above and then delete the apks from the /system/app/ directory. A reboot should then remove everything else related to that app afaik. (like the /data/data/ of the app etc.)
Titanium on the other hand gives me an error when I try to delete a system app, even after remounting system to rw.
---
If you want to edit things from your system partition, like build.prop etc. Copy them to your sd first and edit them there. Then mount system rw, and create a backup of the file you are editing. (make a copy and just append "_bak" or smth to the file name) And finally copy the sd file over the corresponding file in system. Make sure you check permissions before and after you copied everything and edit them if they do not match up.
---
My final Tip for now:
I noticed that most root methods on SELinux (this includes RDLV and the forbidden one) use install-recovery.sh to start su as a system daemon which handles all the su requests. (as far as I understood it at least).
Well we can also use this file (or create an install-recovery-2.sh in /etc/ which gets called by the first one by default when you got the root) to run init.d scripts or other stuff.
I don't have tested it yet but I will put the code below once it works...
Code:
tbd
..
hopefully we find a way to turn off this selinux enforcing mode while keeping knox warranty at some point.. - xposed framework might be the answer but not sure - in theory its able to overwrite all methods used by apps. (but I guess selinux above xposed still in system rights and therefore cannot be affected by it?)

And another one:
Don't like this big n clunky user interface? The DPI for the Note 3 is set to 480, thats for old people! If you have want things a bit more refined and more "space" on the screen, edit your build.prop (like I mentioned above) and set the "ro.sf.lcd_density" value down.
I used 360 instead of 480 and that seems perfect to me. It looks like 240 DPI used to look on the Note 1. - You could try 320 or 400 as well.
If you want to set the dpi of individual apps, install xposed and the app settings module. (I would still set browser to 360 or even 320 dpi, 400 is just too much - the adress bar is so damn huge still)

Glad to see you still at it homie. Kingoapp is great. "Google kingoapp" anyone needing help. Just don't post any links please.
Sent from Heaven.

dallastx said:
Glad to see you still at it homie. Kingoapp is great. "Google kingoapp" anyone needing help. Just don't post any links please.
Sent from Heaven.
Click to expand...
Click to collapse
Definitely try out at least the dpi change to 360 or 400, that one is golden =). (nothing special but still..)
--
so far I haven't found anything that does not work at least with a workaround. Some apps do not work as supposed, but thats because they havent adapted yet to the new environment as far as I can tell. And yea, you cannot edit the selinux stuff or turn it off (at least not easy) but thats it. What I did not yet try, which is for risk-friendly people only anyway, is to mess with the efs folder. (you can change your devices mac there, good for privacy concerns hehe). Could be that selinux blocks that one as well, but other than that most things work alright. Just no custom recovery yet, but this could maybe be made possible through the install-recovery.sh file, telling it to start up a custom recovery but not actually flashing it hard onto the device.

Reboot apps I can't get to work. You know the apps that restart phone, bootloader etc... Even through the side 4 button mod. I can only reboot through factory restart. Pressing the power button and using the default restart button.
Sent from Heaven.
---------- Post added at 06:50 PM ---------- Previous post was at 06:49 PM ----------
Yea I always do DPI changes for Gmail , browser, settings, and few other apps
Sent from Heaven.

aww yea youre right - I havent got any app to reboot the phone yet, only the normal reboot through the stock power menu works for me. Didnt try terminal yet.
Maybe not "reboot" but "shutdown -r now"

dallastx said:
Reboot apps I can't get to work. You know the apps that restart phone, bootloader etc... Even through the side 4 button mod. I can only reboot through factory restart. Pressing the power button and using the default restart button.
Click to expand...
Click to collapse
The 4 way reboot menu from Wanam's xposed module works fine for me if you wanted to check that out.

I got one. Enter download mode by powering off. Then hold volume_down+home+power then press volume_up when promtped. Ok now this is what blows my mind. Everyone says pull battery to exit. I did this and the center off my screen looked messed up for about 8 seconds and I thought there must be a better way. Guess what to exit just hold power by itself for about 10 secs and you reboot out of download mode. Great easy way to check counter and no longer have to remove case, battery, etc.
Sent from my SM-N900W8 using XDA Premium 4 mobile app

TheAvatar said:
The 4 way reboot menu from Wanam's xposed module works fine for me if you wanted to check that out.
Click to expand...
Click to collapse
Yea i tried it but didnt work... It may of been conflicting with other apps. But what root method are you using?
---------- Post added at 07:16 PM ---------- Previous post was at 07:11 PM ----------
JohnnyRebel said:
I got one. Enter download mode by powering off. Then hold volume_down+home+power then press volume_up when promtped. Ok now this is what blows my mind. Everyone says pull battery to exit. I did this and the center off my screen looked messed up for about 8 seconds and I thought there must be a better way. Guess what to exit just hold power by itself for about 10 secs and you reboot out of download mode. Great easy way to check counter and no longer have to remove case, battery, etc.
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yea i have always got out of download mode on Note 3 by just holding power button.
---------- Post added at 07:20 PM ---------- Previous post was at 07:16 PM ----------
zroice said:
And another one:
Don't like this big n clunky user interface? The DPI for the Note 3 is set to 480, thats for old people! If you have want things a bit more refined and more "space" on the screen, edit your build.prop (like I mentioned above) and set the "ro.sf.lcd_density" value down.
I used 360 instead of 480 and that seems perfect to me. It looks like 240 DPI used to look on the Note 1. - You could try 320 or 400 as well.
If you want to set the dpi of individual apps, install xposed and the app settings module. (I would still set browser to 360 or even 320 dpi, 400 is just too much - the adress bar is so damn huge still)
Click to expand...
Click to collapse
Only reason i wouldn't change the DPI for everything because some apps will look crazy. Then you will have apps also like the play store that may not work correctly.

JohnnyRebel said:
I got one. Enter download mode by powering off. Then hold volume_down+home+power then press volume_up when promtped. Ok now this is what blows my mind. Everyone says pull battery to exit. I did this and the center off my screen looked messed up for about 8 seconds and I thought there must be a better way. Guess what to exit just hold power by itself for about 10 secs and you reboot out of download mode. Great easy way to check counter and no longer have to remove case, battery, etc.
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
good finding! (lol i couldve came up with this myself lol - holding power long enough always does a forced reboot).
I noticed too that when you pull the battery that sometimes you get lines on the screen - really scary, thought I messed up my device but after like 10 seconds or so they disappeared. But definitely something you want to avoid!
Holding down power to exit the download mode instead of pulling battery from now on.

I use Rootr Browser Pro... I can delete things out of the system partition and write into the system partition (after setting it for root privelege in settings and supersu) however I can''t just overwrite files.... The file I wish to overwrite must 1st be deleted or renamed,usually with .bak. Haven't had to use terminal.
Another handy tip, in the CSC folder, rename the customer.xls to customer.xls.bak and then a new option will be available in the settings/device/lock screen menu to add app shortcuts to the lock screen
if you add this code to the others.xml file AFTER <FeatureSet> and BEFORE </FeatureSet>
<CscFeature_Sip_UseSymbolInCMKey>true</CscFeature_Sip_UseSymbolInCMKey>
<CscFeature_Sip_EnableSymbolInSecondary>en_GB;en_U S;de;fr;es;it</CscFeature_Sip_EnableSymbolInSecondary>
You will then enable sub symbols on the default keyboard.
Works a dream...

TheAvatar said:
The 4 way reboot menu from Wanam's xposed module works fine for me if you wanted to check that out.
Click to expand...
Click to collapse
wait a minute - the 4 way reboot does work for you? Are you on Knox 0x0 still? And SELinux status enforcing? For me no "reboot" apps seem to work. They all just try to reboot (and SELinux denies it then most likely)
---
one other problem occured: when using xprivacy and deinstalling an app the system locks up. Can someone confirm this?

Why do people insist on DELETING apps from system? Just use pm disable, sheesh.

khaytsus said:
Why do people insist on DELETING apps from system? Just use pm disable, sheesh.
Click to expand...
Click to collapse
The xprivacy lockup also happens with user apps deinstallation. Just want to make sure its not me or my setup but xprivacy thats causing this. I turned it off and it works, turn it on, device hangs on deinstallations.

zroice said:
And another one:
Don't like this big n clunky user interface? The DPI for the Note 3 is set to 480, thats for old people! If you have want things a bit more refined and more "space" on the screen, edit your build.prop (like I mentioned above) and set the "ro.sf.lcd_density" value down.
I used 360 instead of 480 and that seems perfect to me. It looks like 240 DPI used to look on the Note 1. - You could try 320 or 400 as well.
If you want to set the dpi of individual apps, install xposed and the app settings module. (I would still set browser to 360 or even 320 dpi, 400 is just too much - the adress bar is so damn huge still)
Click to expand...
Click to collapse
Yeah, thanks for the tip. I used xpose app setting to set my nova launcher to be about 400. I will try modify the build.prop then.

Ok so what i did to quickly update to mj4 since it is now live. "you will lose root and everything on internal storage so back it up"
Be sure make COPY of backup of your titanium folder if use NOVA be sure to do a backup of your current layout. Copy these folders to your EXTsd. Remove card afterwards.
I was rooted so i kept getting "Cant up dated Modded system". Even unrooting i cant getting Modded system. I use almost the same root method as OP uses called kingoapp "cant provide links so google is your friend"
Anyhow.. i wanted to make sure i didnt trip KNOX and grew impatient for an update.zip. I didnt want to flash anything through ODIN, so i figured would use Kies.
Kies will see your phone as already updated. At the top of the app if you click tools then "firmware and initialization" Kies will override whatever is on your phone and update to mI5. This will take about 30 min but much quicker then trying to download the entire stock firmware from hotfile.
Once your phone is up go ahead and go to to settings on you phone and system update. Update will run and restart your phone. You are now on the latest firmware mj4.
Reroot and reinstall SD card. You are now rooted on latest update.
Notes - I tried everything to try to trick system to thinking its not modded including unrooting. Nothing worked reasoning i resorted to flashing through Kies.

dallastx said:
Ok so what i did to quickly update to mj4 since it is now live. "you will lose root and everything on internal storage so back it up"
....
Click to expand...
Click to collapse
Ohh theres an update? Well I bought a 2nd note today - couldnt resist it was 500€ only (they usually go for about 550 here). And mine had some display issues... gonna sell the first one and keep second - screen is better. Anyway, I got to redo everything now and restore the "old one" to stock.
To restore stock safely I would always suggest using Kies and doing a forced firmware update like dallas described. I read that flashing the same firmware twice with odin can already trip knox. (at least if you were tempering with the system)
But note that this will most likely update the bootloader of your phone as well.
---
Now I got the old bootloader on my new and still branded n3 - can someone explain what the difference actually is to the new bootloader? I mean both don't allow SELinux permissive, and both can be rooted (at least with the "tool")?
On S4 etc I understand that new firmware version introduced knox, and that there was firmware out without knox, but if you upgraded once you couldnt go back. But there are no knox free firmwares for the n3 are there? (I mean stock ones)

zroice said:
Ohh theres an update? Well I bought a 2nd note today - couldnt resist it was 500€ only (they usually go for about 550 here). And mine had some display issues... gonna sell the first one and keep second - screen is better. Anyway, I got to redo everything now and restore the "old one" to stock.
To restore stock safely I would always suggest using Kies and doing a forced firmware update like dallas described. I read that flashing the same firmware twice with odin can already trip knox. (at least if you were tempering with the system)
But note that this will most likely update the bootloader of your phone as well.
---
Now I got the old bootloader on my new and still branded n3 - can someone explain what the difference actually is to the new bootloader? I mean both don't allow SELinux permissive, and both can be rooted (at least with the "tool")?
On S4 etc I understand that new firmware version introduced knox, and that there was firmware out without knox, but if you upgraded once you couldnt go back. But there are no knox free firmwares for the n3 are there? (I mean stock ones)
Click to expand...
Click to collapse
Yea go ahead and do all your updates then root. I think the update may me just for Sprint N900p.

so there is still no way to get rid of "enforcing selinux" without tripping knox counter?
need this only to get my OTG cable to USB OBD working, seems SELinux is blocking serial usb communication :/

zroice said:
wait a minute - the 4 way reboot does work for you? Are you on Knox 0x0 still? And SELinux status enforcing? For me no "reboot" apps seem to work. They all just try to reboot (and SELinux denies it then most likely)
Click to expand...
Click to collapse
Sorry for the late reply. I was Knox 0x0, used Root De La Vega, installed xposed framework then grabbed wanam from the play store. Just had to enable it and it was all good.

[Help] Scripting with Tasker

Hi,
I've set up an emulator using genymotion and am playing a game on it. What I need to do right now is:
Loop begin
2. Simulate a touch/tap at a particular location on the game.
3. sleep for 10 seconds
Loop end
I used to simulate the touch using xdotool in lunux. However, I think tasker should be able to handle this better. I'm a noob when it comes to tasker. I chanced upon a tutorial where in this guy explains how a touch can be simulated buy I'm stuck. It doesn't work. Here is what I've done so far:
1.Tasker > New task > "Test"
2.Run shell
Command:
while [ 1 ]; do
input tap 545 240
sleep 15
done
3. Run tasker.
4. Open the game.
Aaaaand.....nothing happen.
Please assist.
TIA.

Have you ran the task? You say run Tasker, but you still have to run the task or specify an event/condition when to run it.

polobunny said:
Have you ran the task? You say run Tasker, but you still have to run the task or specify an event/condition when to run it.
Click to expand...
Click to collapse
Um.. I pressed the play button, then switched to the game to see if it works every 10 seconds. But didn't work

blueren said:
Um.. I pressed the play button, then switched to the game to see if it works every 10 seconds. But didn't work
Click to expand...
Click to collapse
You ticked Use Root in Run shell?

polobunny said:
You ticked Use Root in Run shell?
Click to expand...
Click to collapse
Edit - Oh no.. I had forgotten to set a profile. Now that it's done, I'm able to get the basic tap command working. But when i put it in the while loop, it fails.
Yes- root enabled. Basic command works, loop doesnt.

blueren said:
Edit - Oh no.. I had forgotten to set a profile. Now that it's done, I'm able to get the basic tap command working. But when i put it in the while loop, it fails.
Yes- root enabled. Basic command works, loop doesnt.
Click to expand...
Click to collapse
That will help you ;D
http://tasker.dinglisch.net/userguide/en/flowcontrol.html

polobunny said:
That will help you ;D
http://tasker.dinglisch.net/userguide/en/flowcontrol.html
Click to expand...
Click to collapse
I had done a silly mistake -__- how stupid of me. Things work now! Thanks for you help.
<<Thread can be closed>>

Thread closed - OP request.

[Q] Lollipop Wifi unlock options?

Hi All,
So the biggest feature I'm missing is trusted wifi unlock. All the app makers who had apps for pre 5.0 say Android has changed something and it's no longer possible. I sincerely hope this is not so they can sell more Smartwear devices.....but thats a debate for somewhere else.
My question is, are there any available solutions yet? I see that so far their are hurdles in front of xposed etc. for Lollipop.
Am I going to have to suffer it or shell out for a Watch?

I was going to ask the same question. Someone posted this solution. I tried it but I was getting error message from Secure Settings.
I am interested if this works for others (so I can figure if it is just problem on my end), or if there are other solutions that exist.

theganguly said:
I was going to ask the same question. Someone posted this solution. I tried it but I was getting error message from Secure Settings.
I am interested if this works for others (so I can figure if it is just problem on my end), or if there are other solutions that exist.
Click to expand...
Click to collapse
Ok, i got this to work with the help of your link. I also get an error too but make sure you do the following:-
Make sure your running secure settings 1.3.5
Go System+ and enable in secure settings
In secure settings click the spanner (top right) -> Pattern unlock method -> Lock settings (This was the one that fixed it for me)
Enable device adminstrator for secure settings in System Settings -> Security
Then in a tasker task I choose Secure settings -> Root actions -> Pattern Lock -> Disable / Enable
Hope it works for you.

Hmm. I'll have to try step 3 then as secure settings hasn't been working for me.

rootSU said:
Hmm. I'll have to try step 3 then as secure settings hasn't been working for me.
Click to expand...
Click to collapse
So far working great for me. Hope it works for you.

harveyd said:
Ok, i got this to work with the help of your link. I also get an error too but make sure you do the following:-
Make sure your running secure settings 1.3.5
Go System+ and enable in secure settings
In secure settings click the spanner (top right) -> Pattern unlock method -> Lock settings (This was the one that fixed it for me)
Enable device adminstrator for secure settings in System Settings -> Security
Then in a tasker task I choose Secure settings -> Root actions -> Pattern Lock -> Disable / Enable
Hope it works for you.
Click to expand...
Click to collapse
Thanks. I tried it a couple of times and it works now. I am glad that we were able to help each other out.
---------- Post added at 01:18 PM ---------- Previous post was at 01:09 PM ----------
rootSU said:
Hmm. I'll have to try step 3 then as secure settings hasn't been working for me.
Click to expand...
Click to collapse
I don't know if you viewed the link I posted but the guy there did ask people to join the beta for Android L compatibility. Maybe because you had Secure Settings pre-installed. Have you already tried uninstalling SS, join community on g+ and join beta, and reinstalled app again?
All the relevant links are included in the one I posted in post#2.

rootSU said:
Hmm. I'll have to try step 3 then as secure settings hasn't been working for me.
Click to expand...
Click to collapse
I don't know if you viewed the link I posted but the guy there did ask people to join the beta for Android L compatibility. Maybe because you had Secure Settings pre-installed. Have you already tried uninstalling SS, join community on g+ and join beta, and reinstalled app again?
All the relevant links are included in the one I posted in post#2.

[Q] No disable soft keys backlight settings?

How can I disable soft keys backlight without power saving? Is no longer in the settings of the Galaxy s6.

I don't believe theres a setting for it, I've looked and looked, I like to set it to 6 seconds but its nowhere to be found.

Yeah I think you need to root and install a custom Rom or xposed (if that's possible yet)

Please refer to my earlier post at http://forum.xda-developers.com/showpost.php?p=60009456&postcount=12 and/or use the search function.

The ATT version has this setting under Display. It's weird that the other versions don't have that setting.

How can I run adb for this fix? Can some one help me to run adb..

The post above has instructions on how to to that

I just ran terminal emulator from my phone and entered "settings put system button_key_light 0" and they are disable for good.

Capacitive Lights Off
Two ways ,
1. The observe the power saving mode turns it off by default.
2. This message is from the user/developer @Averix in one of the S6 thread,
"That thread covers the ADB method. I wrote an app that doesn't require root to set the values to whatever you want from .5 - 10 seconds on, off/on all the time."
Galaxy Button Lights
Hope this helps

nappent said:
I just ran terminal emulator from my phone and entered "settings put system button_key_light 0" and they are disable for good.
Click to expand...
Click to collapse
Are you rooted? Doesn't work for me.

knitler said:
Are you rooted? Doesn't work for me.
Click to expand...
Click to collapse
Does the app not work on your device?

knitler said:
Are you rooted? Doesn't work for me.
Click to expand...
Click to collapse
Use the app in the post above yours, I'm not rooted and it worked fine for me
Sent from my Verizon S6,
formerly abdel12345

Complete Root for G935P

THIS IS FOR QUALCOMM SM-G935P
I saw that the original root thread was missing a few information on the first and second post, so I decided to still offer the same information, while making the entire root process easy to follow along. All work goes to those at the Samsung G935P Root Forum and @colormedroid .
The Files Needed Are:
Odin by Princecosmy: ODIN
G935A: Galaxy S7 Edge
SuperSU: SuperSU Root
Minimal ADB and Fastboot: XDA Forums
You will also need Package Disabler Pro for Samsung: Package Disabler Pro (Samsung) $0.99
I know it costs money, but it is worth it, especially on future devices that support Samsung Admin while waiting for root.
Make sure all files above are downloaded and ready to be accessed.
These steps are best done on a factory reset (can be found in FAQ #3) on PF2 update.
Step By Step Instructions
1. After downloading Package Disabler Pro and getting it set up, you'll need to disable three packages: samsung dm phone interface, samsung dm service, and securityLogAgent.
2. Turn off your phone and boot into Download/Bootloader mode by pressing and holding the Vol Down+Home+Power after your phone is off.
3. Plug Phone into Flash the G935A.TAR in ODIN under AP and your device should restart by itself.
4. Your phone should boot straight into Android. Most likely you will have no LTE. Do not worry, that is normal. Continue onto step 5.
5. Copy the files from SuperSU to the location of your Minimal ADB and Fastboot folder on the computer (Default is "C:\Program Files (x86)\Minimal ADB and Fastboot")then after you enable USB debugging in the Developer Options menu on your phone (If you don't have Developer Options in Settings, go to About Phone, and tap on Build Number 7 Times), Run the Root.Bat file from your Minimal ADB and Fastboot Folder.
6. Open Build.Prop with BuildProp Editor and change the following settings
ro.cdma.default_numeric=310000
Change the value to 310120
ro.cdma.default_alpha=Chameleon
Change "Chameleon" to Sprint
Edit*ro.build.characteristics=Chameleon
Change "Chameleon" to Sprint
After a reboot, you should be good to go and have LTE.
Any other questions, feel free to post to the thread and myself and other helpful members of the community can help!
FAQ
1. Download and install BusyBox on Rails and get it set up. After that's set up, open up SuperSU, go to settings, and under Security check Enable SU during boot. Next, download Kernel Toolkit and under CPU set the Big Cores Maximum Frequency to 2150 Mhz. Don't forget to apply to boot from the side menu.
2. I'm stuck on the LTE splash screen. What do I do?
A: Press and hold the Volume Down + Power button down until your phone restarts. You may have to Factory Reset your device if it stays stuck on the splash screen. Get the files from FAQ #3 to successfully reset. If you wish to Re-Root, activate device beforehand by doing the Device Setup or by going into Settings - Activate Device. After Activated, follow the step by step guide.
3. I'd like to unroot and return to factory stock. How would I go about this?
A: Download the factory firmware from HERE and extract the file. Once Extracted, open ODIN and load each file in their appropriate space (BL file to BL, AP file to AP, CP file to CP, and CSC file to CSC). Make sure your phone is in download/bootloader mode by holding the Vol Down+Home+Power after the phone is off. Click Start once in download/bootloader mode and you should be back to stock once your phone reboots.
4. My WiFi credentials keep on getting erased after a reboot. What gives?
A: This seems to be an issue across all the QC S7 variants. Here's what I did to fix it. Use BuildProp Editor and change: ro.securestorage.support=true to ro.securestorage.support=false
Once the edit is saved correctly, restart your phone.
Credit goes out to: @guaneet for this fix
More answers to FAQ's to come.

Thanks, this guide is a bit clearer for beginners like me
EDIT: I can't seem to find the Minimal ADB and Fastboot Folder, where is it? (solved)
EDIT2: Where do I find the root.bat file in my phone? (solved, I had to run it from the computer not the phone)

This doesn't trip Knox right? So if I root and decide to go back stock, Samsung pay should work right?

JG96EVO said:
This doesn't trip Knox right? So if I root and decide to go back stock, Samsung pay should work right?
Click to expand...
Click to collapse
Correct. It requires to be on unchanged software. When going on complete factory reset using ODIN, it reverts any and all software changes made.

That changing the thing to sprint an the numbers to 310120 does not work for me when i do that i get no data wel 3g an it comes in an out then goes to roaming..an i cant change apns an there r no sprint apns as well...not sure if anyone els is having that

donbudafuko said:
That changing the thing to sprint an the numbers to 310120 does not work for me when i do that i get no data wel 3g an it comes in an out then goes to roaming..an i cant change apns an there r no sprint apns as well...not sure if anyone els is having that
Click to expand...
Click to collapse
Did you let the phone set up once before rooting? Did you also go into mobile networks and change roaming settings to home only?
Edit: The setup to bring your phone to Sprint did work because Sprint does not allow (unless with MSL) editing of APNs. I also made an edit that changes ro.build.characteristics=Chameleon in Build.Prop to ro.build.characteristics=Sprint. Hopefully that helps as well.

So let me throw out some errors that happened with me with the solvencies so no one has to feel like an idiot like me...
1. If Odin throws an error on your pit it will look like its good to go. It is not. Let your phone setup and then reodin
2. After initializing the 3 you disabled, go to settings, activate device. Let it activate but do NOT press done or ok or restart or a winky face emoticon or anything... But the home button and disable that same three again. Reboot. If your device keeps trying to be crazy, pick yourself up and try again.
3. For the bad file... Enable USB debugging, install the and drivers and the such then... Plug your phone into your computer and agree to the popup on your phone. After you agree (You have to be down with MTP, you know me) run the bad file on your computer. It'll say stuff and take a couple of minutes. Let it run. After reboot, reboot again. Root achieved.
Thanks so much for your clarification OP, I would've loved to use this post when I did mine lol
NOTE: Your mileage may vary... I did the buildprop change from Chameleon and the 31000 change and it negated my service. I went and changed it back, restarted, re-enabled the 3, activated the device, homed out, re-disabled the 3 and restarted. My LTE is back up and running

4. My WiFi credentials keep on getting erased after a reboot. What gives?
A: This seems to be an issue across all the QC S7 variants. Here's what I did to fix it. Use BuildProp Editor and change: ro.securestorage.support=true to ro.securestorage.support=false
Even after making these changes and verifying, my WiFi credentials and still being erased.

Hardcorp said:
4. My WiFi credentials keep on getting erased after a reboot. What gives?
A: This seems to be an issue across all the QC S7 variants. Here's what I did to fix it. Use BuildProp Editor and change: ro.securestorage.support=true to ro.securestorage.support=false
Even after making these changes and verifying, my WiFi credentials and still being erased.
Click to expand...
Click to collapse
Verify your edit stuck. Make sure there is not any extra "space" in line or end of that line. Reboot.

xyameax said:
Did you let the phone set up once before rooting? Did you also go into mobile networks and change roaming settings to home only?
Edit: The setup to bring your phone to Sprint did work because Sprint does not allow (unless with MSL) editing of APNs. I also made an edit that changes ro.build.characteristics=Chameleon in Build.Prop to ro.build.characteristics=Sprint. Hopefully that helps as well.
Click to expand...
Click to collapse
Tryed that still the samething..really doesnt mayter thimo i have data an call service as is so um goid just wanting to let everyine els know it might not work

LeftyGR said:
Verify your edit stuck. Make sure there is not any extra "space" in line or end of that line. Reboot.
Click to expand...
Click to collapse
After the next reboot they started to stick.

why can i not update su? without updating i cannot use buildprop editor... i even tried downgrading from pf2 to pe1.... no luck. phone also says custom on boot.

Are there still issues with lag and battery drain after root?

wojo797 said:
why can i not update su? without updating i cannot use buildprop editor... i even tried downgrading from pf2 to pe1.... no luck. phone also says custom on boot.
Click to expand...
Click to collapse
Updating supersu has had mixed results. Some have no problem, but it has been suggested by chainfire himself to not update it.

ch0de said:
Are there still issues with lag and battery drain after root?
Click to expand...
Click to collapse
If you follow the Kernal Auditor step, it helps with the lag and battery drain. It is because the phone is in performance mode first upon root, and so the phone throttles on heat. Setting it to Interactive brings down heat and ultimately lag and brings back battery life.

wojo797 said:
why can i not update su? without updating i cannot use buildprop editor... i even tried downgrading from pf2 to pe1.... no luck. phone also says custom on boot.
Click to expand...
Click to collapse
Are you on the Qualcomm or Exynos device? Are you sure you're G935P? I ask to try again one more time and make sure SU is installed on your phone. It may take a while for the prompt to open as well, but give it time.

xyameax said:
If you follow the Kernal Auditor step, it helps with the lag and battery drain. It is because the phone is in performance mode first upon root, and so the phone throttles on heat. Setting it to Interactive brings down heat and ultimately lag and brings back battery life.
Click to expand...
Click to collapse
Just to clarify, and I apologize for my ignorance..
When you say "helps" with battery drain and lag, does that mean it fixes the issue and it preforms at "stock", or does that mean its better then doing nothing but still more lag and battery/heat the unrooted stock ?

As per XDA forum rules, duplicating threads is not allowed. There is nothing wrong with making your contribution to the existing thread. Please continue there:
SM-G935P Root
THREAD CLOSED