Database Info

[ROOT][TOOL][2012-07-24] GS3DebugFSRoot: Root the Verizon GSIII without flashing

THIS WILL NOT WORK WITH JELLY BEAN.
---
Here's a easy-to-use tool based on the method in this thread.
If you like this tool, please click the Thanks button!
Even better, see my signature.
DISCLAIMER: As with any rooting tool, there is some chance that something will go wrong. Use of this tool is at your own risk, and I will not be responsible if you brick your phone in the process. Although there have been zero reports of this tool breaking anyone's phone, don't run it if you aren't comfortable with the possibility of having something go wrong and having to re-Odin back to stock or worse.
Instructions:
Install the USB drivers if you don't have them already: Verizon_Wireless_I535_GSIII_Samsung_USB_Driver_v1_4_6_0.exe
Download the package and extract it somewhere (you'll need 7-Zip or some other modern compression tool) Make sure you extract all the files to a folder somewhere! Running it straight from your compression program probably won't work.
On your phone, enable installation of third-party apps (Settings --> Security --> Unknown sources, near the bottom in the "Device administration" section)
On your phone, enable USB debugging (Settings --> Developer options --> USB debugging)
On your PC, make sure you don't have any other Android devices connected, any Android emulators running, or any Android tools like PdaNet running.
Plug your phone into a USB port on your computer. For best results, use a port directly on the machine, and not a USB hub.
Double-click RootDebugfs.bat and follow the directions on the screen. Your phone will reboot 3 or 4 times during the process; just leave it plugged in. To be safe, don't switch to any other applications while the root process is running.
DOWNLOAD GS3DebugFSRoot R2 FOR US GALAXY S III VARIANTS ONLY!!!
(Released July 24, 2012)
If anything goes wrong, post here and I'll see what I can do.
Credits:
* miloj, for the debugfs root method for the Asus TF300T
* sparkym3, for his script for rooting the Asus Transformer Prime - this is a modified version of that script
* ChainsDD, for Superuser

Version History:
The most recent version is always at the top.
r2 2012-07-24
+ Changed font color to white for readability
+ Cleaned up output
+ Fixed typo in title (GSII instead of GSIII)
+ Fixed Unknown Sources/USB Debugging directions
+ Included latest version of adb from platform-tools 13, might make things more reliable
* Includes ChainsDD Superuser 3.1.3 and su binary 3.1.1
* Known to work with LF2 and LG1.
r1 2012-07-23
* Initial beta
* Includes ChainsDD Superuser 3.1.3 and su binary 3.1.1
* Works with LF2. Probably works with LG1.
Possible future features:
* APK version of the tool! I'm still not sure if this is possible - currently researching.
Sadly, I don't think this is going to happen.
* Unroot tool.
* Choice of Superuser or SuperSU.

FAQs:
Q: What versions of the stock ROM does this work with?
A: It's known to work with anything from LF2 up to LHE. It seems likely that DebugFSRoot will be able to work with any ICS ROMs. We'll have to wait and see if it works on JB or not.
Q: I'm getting an error like "adb is not recognized as an internal or external command", or "cannot stat 'su': No such file or directory". What do I do?
A: Don't run the tool straight from your compression program. Make sure to extract all the files somewhere first.
Q: Will this wipe my data?
A: Nope.
Q: How can I unroot? Will flashing a stock ROM unroot?
A: Flashing a stock ROM will unroot and also remove any modifications you made to /system.
Q: Everything seems to have worked fine, and the Superuser app shows the binary as present and working. However, none of my root apps work. What do I do?
A: This seems to happen to a very small number of people, and the cause is unknown. If this happens to you, try installing Chainfire SuperSU.
Q: Is this any better than flashing the root66 ROM?
A: The end result should be pretty much the same, but this tool is much smaller to download than the root66 ROM.
A: If you are on a phone with the stock LG1 ROM update, root66 will downgrade you to LF2, while this tool will leave your ROM alone.
Q: Is this any better than using the VRALEC boot chain method?
A: The boot chain is a little more complicated. It requires flashing two bootloaders, flashing recovery, and using Triangle Away to reset the Custom Binary Download counter. If you intend to install a custom recovery/custom ROMs anyway, it's fine and probably quicker. However, if all you want is root to run Titanium Backup or other root apps, GS3DebugFSRoot is easier.
Q: Will this increment the flash counter?
A: Not on its own. If you flash anything else after rooting, however, you might, so read up on what you're doing.
Q: Will this cause the "custom unlock" boot screen to appear?
A: In general, no. However, the spyware Samsung/Verizon included (SysScope/libcordon) is paranoid, and a lot of tweaks you can do after rooting will trigger it. If you don't want to risk getting the custom unlock screen, don't freeze any apps using Titanium Backup and generally limit your tweaking to things you could do without root.
Q: Can Samsung/Verizon block this method in the future?
Yes. It's very possible that a future OTA will patch the exploit that this tool uses. If you want to root, it's always best to do it now!

I just tried this and it appears to work. Installed Titanium Backup and SuperUser permissions were given. Thanks!
P.S.
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.

DFieldFL said:
I just tried this and it appears to work. Installed Titanium Backup and SuperUser permissions were given. Thanks!
P.S.
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.
Click to expand...
Click to collapse
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?

Noxious Ninja said:
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?
Click to expand...
Click to collapse
Also title says Galaxy S II not III.

Noxious Ninja said:
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?
Click to expand...
Click to collapse
The boot screen looks the same to me.

Worked for me, thanks

Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"

phantomevo77 said:
Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"
Click to expand...
Click to collapse
Same thing happening to me.
EDIT: Just switched usb ports and unplugged and replugged my phone in and it worked!

If my gs3 came updated with the newest version, will this still work?

Next release will be out tonight after I test it.
DFieldFL said:
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.
Click to expand...
Click to collapse
Fixed in the next version. Also, I added those steps to the main post.
open1your1eyes0 said:
Also title says Galaxy S II not III.
Click to expand...
Click to collapse
Typo on my part. Will be fixed in the next release.
phantomevo77 said:
Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"
Click to expand...
Click to collapse
I'm not sure about this one. However, I had packaged a slightly older version of adb, which could cause a difference. The next release will have the latest adb.
eakrish said:
If my gs3 came updated with the newest version, will this still work?
Click to expand...
Click to collapse
I think so, but I don't know if it's been tested. Worst case should be that it would fail when trying to copy su into /system/xbin/, and you might have to manually clean up a few things:
Code:
adb shell
[COLOR="Red"]$[/COLOR] rm /data/local/tmp
[COLOR="Red"]$[/COLOR] mv /data/local/tmp.bak /data/local/tmp
[COLOR="Red"]$[/COLOR] rm /data/local/su
[COLOR="Red"]$[/COLOR] rm /data/local/debugfs
[COLOR="Red"]$[/COLOR] rm /data/local/debugfsinput
[COLOR="Red"]$[/COLOR] exit
Really worst case is that your /system is screwed up and you have to re-flash a stock ROM with Odin, but that is highly, highly unlikely with this method.

Thanks for this awesome tool!!! Will there be a reversal to what this script does, aka, non-root to reverse changes if necessary or will that require odin flash?

It's probably possible to unroot via script. I think it might even be possible to move this into an APK and do away with adb altogether. I'll play around with it.

Is there an unroot method that's just as easy? I'd prefer not to reflash the phone to get rid of root. I guess I'm one of the oddballs here as I can care less about custom roms, I only root to be able to backup and remove bloatware.
edit: sorry I typed and posted this as others were doing the same... I couldn't delete or edit the post for a few minutes because of my newby status.

edthesped said:
Is there an unroot method that's just as easy? I'd prefer not to reflash the phone to get rid of root. I guess I'm one of the oddballs here as I can care less about custom roms, I only root to be able to backup and remove bloatware.
Click to expand...
Click to collapse
You should be able to do it via adb shell.
Code:
adb remount rw
adb shell
$ su
# rm /system/xbin/su
# exit
And then uninstall the Superuser app.
I'll try and add it to the script.

Thank You ! so much ... The tool works perfectly on my stock VZ ... Finally can get rid of all the crap that VZ puts in.

Noxious Ninja said:
It's probably possible to unroot via script. I think it might even be possible to move this into an APK and do away with adb altogether. I'll play around with it.
Click to expand...
Click to collapse
That would be awesome. It would be cool if you could make it unroot as well. Keep up the good work!
Tap'd via SGSIII(!)

CooL Very Very CooL
Thanks Noxious Ninja

eakrish said:
If my gs3 came updated with the newest version, will this still work?
Click to expand...
Click to collapse
Mine came with the update and I was able to root successfully with this tool. Very nice.

Kyocera DuraForce Super Thread

Welcome to the Kyocera DuraForce super thread
There isn't much information floating around for the DuraForce and I've created this thread to aggregate information as it's found so we have a single place for useful information, hacks, etc.
I'll keep the thread as up to date as possible and organize any information from future posts into the originals so people can find information easier.
There is a Lollipop update available for the device as of early February, 2016. I have found a way for users to update if the OTA fails (see below). I've also updated the below posts with information regarding the Lollipop update and moved the KitKat notes to another location (link for old notes is below)

Ota - lmy47v1218_2217
For those who are having trouble applying a FOTA on the DuraForce, check /cache/fota/xyz_fotalog_123.dat It's a text file that contains a lot of really good info on what is going on during a FOTA. Including errors. Keep a look out for signature mismatch errors.
I had errors with the following files. Took me a few tries to get the OTA applied as each attempt resulted in one error.
Uninstall Xposed (moar hacks)
/system/usr/keylayout/gpio-keys.kl (disable PTT/Speaker buttons)
/system/etc/permissions/platform.xml (sd card "fix")
If trying to address the issues manually does not work, follow the procedure below.
Download "vanilla" system image from HERE (link)
Extract zip file
Ensure at least 2Gb of storage is available for internal data
adb push mmcblk0p21_KVT49L_0617_0132 /storage/sdcard0/
adb shell
su
dd if=/storage/sdcard0/mmcblk0p21_KVT49L_0617_0132 of=/dev/block/mmcblk0p21
Reboot phone once it completes. It will take awhile and not report anything during the process.
After phone boots, run "adb reboot recovery"
Wipe data / factory reset
Wipe cache
Reboot
Run software update

General Notes - Lolipop
Force Reboot: Pwr + Vol Up + Vol Dn + Back + Home + App Switcher buttons for ~10-30 seconds
Root: Use KingRoot from http://king-root.net/ -- I used the android APK successfully
SD cards bigger than 32Gb still do not work correctly on stock firmware

Known Working Customizations
To be determined

KitKat Notes
All previous notes for KitKat have been moved to a document in box. The notes can be found HERE (link)

Sources / Mirror(s)
The OSS drop is available on Kyocera's developer site: http://www.kyoceramobile.com/support/developers/
Misc file mirror: https://nuskunetworks.box.com/s/p5hwq3hboctl0saze0wkcv3jzfefuw45

Do you trust Kingo?
I'm THRILLED to hear you were able to root and freeze all the AT&T crapware. I can't wait to do the same. But how do you feel about Kingo? I'm almost leaning more to keeping the bloat, kind of the devil you know, you know?
kemonine96 said:
Welcome to the Kyocera DuraForce super thread
There isn't much information floating around for the DuraForce and I've created this thread to aggregate information as it's found so we have a single place for useful information, hacks, etc.
I'll keep the thread as up to date as possible and organize any information from future posts into the originals so people can find information easier.
If you're looking for root, look no further than Kingo. I can confirm the Windows version of Kingo is working on the AT&T varient of the DuraForce.
Click to expand...
Click to collapse

tomzweifel said:
How do you feel about Kingo?
Click to expand...
Click to collapse
I've used it a few times over the last year and can only complain it does a sloppier job compared to SuperSU. Every pre-canned root wants to crap all over /system and none is better than the other so long as you get the su binary in a working state IMHO. I know Kingo is harder to clean up after than SuperSU / others but it's a hell of a lot easier to just use Kingo to root and cleanup after. Stacking root exploits and similar like Kingo is doing is a huge PITA and best left to those specializing in such things.
tomzweifel said:
I'm almost leaning more to keeping the bloat, kind of the devil you know, you know?
Click to expand...
Click to collapse
Fair enough, I was able to replace Kingo with SuperSU pretty easily:
Install SuperSU from Play Store
Run SuperSU and update su binary via "Normal" mode
Authorize SuperSU when Kingo prompts
Allow SuperSU to replace su binary
Freeze/Remove Kingo
Reboot and enjoy SuperSU
Optional: cleanup other Kingo remnants

Components to clean up?
Any chance you can steer me towards the "remnants" that need to be cleaned up and where to find them, just to make sure I get it all? I'm probably going to go though this exact process tonight or tomorrow.
Thanks for the information!
kemonine96 said:
I've used it a few times over the last year and can only complain it does a sloppier job compared to SuperSU. Every pre-canned root wants to crap all over /system and none is better than the other so long as you get the su binary in a working state IMHO. I know Kingo is harder to clean up after than SuperSU / others but it's a hell of a lot easier to just use Kingo to root and cleanup after. Stacking root exploits and similar like Kingo is doing is a huge PITA and best left to those specializing in such things.
Fair enough, I was able to replace Kingo with SuperSU pretty easily:
Install SuperSU from Play Store
Run SuperSU and update su binary via "Normal" mode
Authorize SuperSU when Kingo prompts
Allow SuperSU to replace su binary
Freeze/Remove Kingo
Reboot and enjoy SuperSU
Optional: cleanup other Kingo remnants
Click to expand...
Click to collapse

tomzweifel said:
Any chance you can steer me towards the "remnants" that need to be cleaned up and where to find them, just to make sure I get it all? I'm probably going to go though this exact process tonight or tomorrow.
Thanks for the information!
Click to expand...
Click to collapse
Unfortunately I don't have notes on what Kingo leaves around on /system... Some searching online or poking about /system should yield results.

New OTA Update
I just got notified of an available OTA update but I can't find a changelog or any info on it yet. I'll be sure to post it if I find it.

tomzweifel said:
I just got notified of an available OTA update but I can't find a changelog or any info on it yet. I'll be sure to post it if I find it.
Click to expand...
Click to collapse
Please do. I haven't gotten any notifications yet and I'm kinda curious what the OTA will contain.

http://www.att.com/esupport/article.jsp?sid=KB426870&cv=820
Software update includes
Kyocera Remote Lock
Miscellaneous improvements, fixes, and security updates

Dkesler76 said:
http://www.att.com/esupport/article.jsp?sid=KB426870&cv=820
Software update includes
Kyocera Remote Lock
Miscellaneous improvements, fixes, and security updates
Click to expand...
Click to collapse
Thanks for the heads up. Too bad it's not L.

kemonine96 said:
Thanks for the heads up. Too bad it's not L.
Click to expand...
Click to collapse
np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan

Dkesler76 said:
np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan
Click to expand...
Click to collapse
I managed to free up some time this weekend and I'm going to be pulling the OTA and seeing what I can do for re-packing it for those of us who are rooted and/or de-bloated.
Will post back with more info after I've had some time to poke at the OTA some.
Edit 1: Looks like this has patches for system and boot. /cache/delata looks like the directory where everything was downloaded. Hopefully binwalk and some other tools will yield useful information on what's contained within.
Edit 2: Looks like I was able to install the OTA despite being rooted. I'm waiting for 1st boot to verify root persisted and I'm also working on mirroring a number of partitions that can be used to "go back" to stock as well as images for updated partitions post-OTA.

Dkesler76 said:
np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan
Click to expand...
Click to collapse
I managed to get a stock boot and system partition uploaded today that you should be able to use to restore the de-bloated apps. The image is here
You can use a Linux machine (or other methods) to extract the APKs and put them back or use busybox + dd to restore the contents of the partition (you may need to re-root if writing the partition using dd). There are some good guys on XDA and elsewhere on how to restore a partition image on an Android device.
Edit: The posted file is for an ATT device

Good news everybody! The ATT OTA doesn't remove root and can be installed as-is provided you've not de-bloated the ROM or installed Xposed. If you've de-bloated (see below) you'll need to restore the missing bloatware and if you've installed Xposed, you'll need to uninstall it prior to applying the OTA.
In one of the early OP's there's a link to the "misc file mirror" that contains partition images for boot and system partitions. These are from an ATT device and can be used to restore back to a state that'll allow the OTA to apply.
Happy hacking and OTAing everyone.

kemonine96 said:
I managed to get a stock boot and system partition uploaded today that you should be able to use to restore the de-bloated apps. The image is here
You can use a Linux machine (or other methods) to extract the APKs and put them back or use busybox + dd to restore the contents of the partition (you may need to re-root if writing the partition using dd). There are some good guys on XDA and elsewhere on how to restore a partition image on an Android device.
Edit: The posted file is for an ATT device
Click to expand...
Click to collapse
weird i tried dd and busy box and no go not showing up on device

Dkesler76 said:
weird i tried dd and busy box and no go not showing up on device
Click to expand...
Click to collapse
What isn't showing up?

Verizon Root Guide (Knox still good)

I take no credit other than compiling info and making a guide. All credit goes to http://forum.xda-developers.com/member.php?u=4911585 (br3w3r, Chainfire and Princecomsy)
http://forum.xda-developers.com/att-...-root-t3410403
Also credits to Mastajeff for originally making the guide for T-Mobile.
First off download these files: http://d-h.st/PK3q
Extract them to whatever folder you want, there will be 5 files in there.
Folder named: "su" contains the SuperSU and thing needed to root the phone
ADB Setup EXE called: "adb-setup-1.4.3.exe" Needed to install ADB and the Drivers
Special patched Odin that skips the SHA 225 called: Odin PrinceComsy.exe (Mainly for AT&T)
.ini file named: "Odin3.ini"
Last, file, named: "Samsung_G935x_QC_Rooted_BOOT.TAR", this is the engBoot for the phone.
NOTE: Some users have experienced endless boot loop; this seems to be caused by using a package disabler that disabled certain services.
If you used one and end up getting an endless boot loop try wiping the cache and factory reset the phone.
I suggest you backup your phone before doing this, just in case something happens.
Install ADB by running adb-setup-1.4.3.exe
Make sure to put your phone into downloading mode (Power off--- Hold Down arrow + Home + Power button)
Open up Odin and click AP and mount Samsung_G935x_QC_Rooted_BOOT.TAR
Once restarted put the phone into USB debugging mode (Need Developer options for this)
To get developer mode, go to "About" then tap "build number" about 6 or 7 times
Go back to settings and you should now see developer options, turn on USB debugging
Now back on your PC, Move the folder named "su" into your ADB folder (Default Path: C:\adb)
Run CMD by either Win + R and typing cmd or from the control panel.
Once CMD is open type this
Code:
cd C:\adb\su
or whatever your path to your "su" folder.
After that type root.bat
Wait for the CMD to finish and then your phone should restart
Once your phone has finally restarted you will notice that SuperSU was installed and root should be working, download root checker to find out for yourself.
If your CMD just says starting Daemon and doesn't proceed any further than that, then you forgot to make sure USB debugging was turned on.
If everything went well you will see the CMD was able to push SuperSU.
You can now install Xposed via Flashfire. Unfortunately, TWRP does not work on this method, so, DO NOT TRY, there is a chance that you can Brick your phone from doing that.
NOTE: DO NOT UPDATE THE SU BINARY!
Fix for wifi bug on restart: http://forum.xda-developers.com/tmo...ticky-root-t3327399/post67592828#post67592828
Thanks 2swizzle for mentioning this.
If you want to fix the lag/slowness download any CPU or Kernel Editor or changer.
This one works fine: https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor&hl=en
To fix the lag
Open up the APP
Go into the CPU settings
Set CPU Governor to ondemand
Apply on boot
Thanks to orgulloso4202 I have found a way to fix the battery drain and help with Youtube and the CPU.
L Speed seems work fine and my battery no longer drains when using the recommended Profile.

Interesting. First Sammy I've seen that Knox is intact but Samsung Pay won't work.

Have been searching a bit after rooting mine, don't suppose anyone has word on how to or if you can install TWRP or Xposed?

AlphaD1 said:
Have been searching a bit after rooting mine, don't suppose anyone has word on how to or if you can install TWRP or Xposed?
Click to expand...
Click to collapse
Got Xposed with flashfire but sadly it left me in a boot loop on the verizon logo, think I need to start over.

If we can get the bootloader unlocked it will be fun times indeed!
Going to try this soon.
Don't care if my phone blows up, it's the 4th here in the U-S-A!
Besides my trusty Nexus 6 and even Note 5 are ready for duty!
Xposed would be nice, I do miss those features.
Layer support even just to change up the statusbar.
Themes have done a nice job to blackout the device.
Root, center clock and some battery icon customizations and I'm all set for sure.
Perhaps the horrid standby time will be fixed.
Because as of late this phone has lead to high frustration to the point where I want to see how good it skips across the lake! But when I think of how much I paid for it, well I keep it in my pocket!

TWRP doesnt work, but you can install Xposed from flashfire.

Argyrus said:
TWRP doesnt work, but you can install Xposed from flashfire.
Click to expand...
Click to collapse
So with Xposed working, that means battery saving apps like Greenify and Amplify work now for our devices?

GigaSPX said:
So with Xposed working, that means battery saving apps like Greenify and Amplify work now for our devices?
Click to expand...
Click to collapse
Not 100% sure.
I haven't really installed it on my phone. I only know Xposed work due to the countless others that tried it; however, I don't see why those should not work.

Xposed is working fine and you guys need to install a kennel app and change the engboot settings to ondemand, that's why it lags and slow

2swizzle said:
Xposed is working fine and you guys need to install a kennel app and change the engboot settings to ondemand, that's why it lags and slow
Click to expand...
Click to collapse
Root gives performance issues??

GigaSPX said:
Root gives performance issues??
Click to expand...
Click to collapse
Negative. The eng kernel has shown some lag and performance slowdowns for some people but can be remedied by changing the governor.
Sent from my SM-G935V using Tapatalk

MisterSprinkles said:
Negative. The eng kernel has shown some lag and performance slowdowns for some people but can be remedied by changing the governor.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Which governer do you recommend we use for optimal performance?

zachchen1996 said:
Which governer do you recommend we use for optimal performance?
Click to expand...
Click to collapse
Would seem the consensus is on-demand.
Sent from my SM-G935V using Tapatalk

Am I missing the download files for Verizon or are they not posted here

Can anyone report that they are suffering overheating issues after rooting even after a FDR? Thanks!

shawnten said:
Am I missing the download files for Verizon or are they not posted here
Click to expand...
Click to collapse
They are posted here: http://forum.xda-developers.com/tmobile-s7-edge/how-to/how-to-root-s7-edge-t3410470
I guess maybe I should make a thread here with all the download links and some other links that fix things.

Thread updated!
Added links and more stuff.

farfromovin said:
Interesting. First Sammy I've seen that Knox is intact but Samsung Pay won't work.
Click to expand...
Click to collapse
If you try opening the app you will get a message saying: "Access denied. Unauthorized modifications have been made to your device."
I am guessing that the app has some other type of security that checks if phone has been modded.

Anyone tried to unroot? Does Samsung Pay work if you revert NB to stock?
Sent from my SM-T320 using Tapatalk

How do we install xposed with flashfire?

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

Root PK1 with working LTE and voice/mms/hotspot

OK so after reading a bunch on rooting the different firmwares I went ahead and gave the root a shot on our 935P running PK1. It was successfully rooted and runs with no lag whatsoever, no reboots, and LTE is working as well as voice and MMS. I did not make any of the needed files I just found them on XDA and put them to use. Please make sure you thank the devs for this would not be possible without them. Here are the steps I took:
1. Download the following items on your Windows PC:
A. ADB
B. Odin found at http://www.filedropper.com/princecomsyodin
C. Stock PK1 TAR
D. The engineer boot.img from the thread labeled root 10/25 found at http://www.filedropper.com/samsungg935xqcrootedboot
E. The SU install package from same thread found at https://download.chainfire.eu/970/SuperSU/SuperSU-v2.76-S7QC.zip
2. With phone in DL mode use Odin to flash all 5 items of stock PK1 TAR. Let phone boot up and activate on the network.
3. Download Package Disabler from Play store and use it to disable the following items:
A. Bootagent
B. Carrier Setup Wizzard
C. Chameleon
D. Com.android.carrierconfig
E. MobileInstaller
F. SAE
G. Samsung DM Phone Interface
H. Samsung DM service
I. Setup Wizzard
J. securityLogAgent
4. Power off phone and start in DL mode
5. After installing ADB open up Odin and click AP and select the engineer boot.img file
6. With phone in DL mode connect to PC and flash boot.img through Odin (once complete phone will boot up)
7. Once phone boots up run the Root.bat script. After a successful run the phone will reboot and SuperSU will be installed.
8. Download build.prod editor from Playstore
9. Use build.prop editor to change the following 3 items:
A. ro.cdma.default_alpha from chameleon to sprint
B. ro.cdma.default_numeric from 310000 to 310120
C. ro.build.characteristics from Chameleon to Sprint
10. GoTo settings, security, other security settings and turn off automatic updates.
11. Reboot
12. Install Wireless Tether Router from Playstore
13. After install open and set desired broadcast name and password DO NOT change anything else.
14. Turn your phone's Wifi on
15. Hit Enable Wifi Router and grant SU permission when asked.
Your 935P on PK1 is now rooted with working LTE, voice, MMS, and hotspot.

thank you very much for your help. i confirm that this solution works on PL6 stock and everything like you said is working. This is what i did.
i followed everything you listed except 3 things.
1) i needed stockfile for PL6 and when unzipped i used 4 files . for the csc file i used home, so it preserves data.
2) for part I i didn't know which wizard setup, lol so i disabled both.
3) i also added securityLogAgent. to the disabled list, because i kept getting that notification that if u click it. it reboots and gets rid of root.
thank you once again, and once again this is working on PL6, just make sure u download PL6 stock

going totry this on pl6 today. wish me luck. any more tips for trying this on pl6? what "home" file did you use?

stebomurkn420 said:
going totry this on pl6 today. wish me luck. any more tips for trying this on pl6? what "home" file did you use?
Click to expand...
Click to collapse
Did you try this?

This worked flawlessly for me thanks
Sent from my SM-G935P using Tapatalk

hotrodssnova said:
Did you try this?
Click to expand...
Click to collapse
i sure did... it does work... there are a few minor snags i ran into but nothing i couldnt figure out. This method is definitely not for noobs. lol. not saying you are just proceed with caution.

With the update so close, im on the fence.

hotrodssnova said:
With the update so close, im on the fence.
Click to expand...
Click to collapse
What update are you referring to? I'm assuming 7.0? Any idea when it's coming out?

I got the update yesterday.

Could you link which package disabler you used? Some of them have been removing some of the packages that you can disable (im guessing from pressure from samsung).
Also, what did you do to get no lag?
Thanks!

stebomurkn420 said:
going totry this on pl6 today. wish me luck. any more tips for trying this on pl6? what "home" file did you use?
Click to expand...
Click to collapse
How'd it go? Looking to do this on PL6.

Hey guys. Im having some problems with this method because of ADB.
I flash the boot.img but once I run root.bat it goes though everything fine until I get to the line "adb install -r SuperSU-v2.76.apk" an error appears from adb saying "Error could not access the package manager. Is the system running?"
Ive tried making it the specific path. ex: "adb install -r /sdcard/Download/SuperSU-v2.76.apk" and stuff like it. (Im also not sure if its installing the apk from the file on the phone or the folder on my PC.
Any help would be appreciated. Running PK1 S7 Edge Sprint.
on top of this my phone just vibrates and lands at the Sprint LTE screen while it doesnt do anything. This is probably the problem. But I have the same version as #1 so whats the problem?

Goongydin said:
OK so after reading a bunch on rooting the different firmwares I went ahead and gave the root a shot on our 935P running PK1. It was successfully rooted and runs with no lag whatsoever, no reboots, and LTE is working as well as voice and MMS. I did not make any of the needed files I just found them on XDA and put them to use. Please make sure you thank the devs for this would not be possible without them. Here are the steps I took:
1. Download the following items on your Windows PC:
A. ADB
B. Odin found at http://www.filedropper.com/princecomsyodin
C. Stock PK1 TAR
D. The engineer boot.img from the thread labeled root 10/25 found at http://www.filedropper.com/samsungg935xqcrootedboot
E. The SU install package from same thread found at https://download.chainfire.eu/970/SuperSU/SuperSU-v2.76-S7QC.zip
2. With phone in DL mode use Odin to flash all 5 items of stock PK1 TAR. Let phone boot up and activate on the network.
3. Download Package Disabler from Play store and use it to disable the following items:
A. Bootagent
B. Carrier Setup Wizzard
C. Chameleon
D. Com.android.carrierconfig
E. MobileInstaller
F. SAE
G. Samsung DM Phone Interface
H. Samsung DM service
I. Setup Wizzard
J. securityLogAgent
4. Power off phone and start in DL mode
5. After installing ADB open up Odin and click AP and select the engineer boot.img file
6. With phone in DL mode connect to PC and flash boot.img through Odin (once complete phone will boot up)
7. Once phone boots up run the Root.bat script. After a successful run the phone will reboot and SuperSU will be installed.
8. Download build.prod editor from Playstore
9. Use build.prop editor to change the following 3 items:
A. ro.cdma.default_alpha from chameleon to sprint
B. ro.cdma.default_numeric from 310000 to 310120
C. ro.build.characteristics from Chameleon to Sprint
10. GoTo settings, security, other security settings and turn off automatic updates.
11. Reboot
12. Install Wireless Tether Router from Playstore
13. After install open and set desired broadcast name and password DO NOT change anything else.
14. Turn your phone's Wifi on
15. Hit Enable Wifi Router and grant SU permission when asked.
Your 935P on PK1 is now rooted with working LTE, voice, MMS, and hotspot.
Click to expand...
Click to collapse
Hello, i am currently running PJ2 on my samsung edge, do you think i should use the root method for pj2 or take the update to pk1 and then root?thanks in advanced

razzrmaxx said:
Hello, i am currently running PJ2 on my samsung edge, do you think i should use the root method for pj2 or take the update to pk1 and then root?thanks in advanced
Click to expand...
Click to collapse
I can confirm pk1 method works. Not sure about root on pj2.

After obtaining root from the OP I downloaded the current stable SuperSU 2.79 flashable zip. I flashed it from FlashFire. I received a security warning. Custom binary blocked by SECURE BOOT (boot.img). I then flashed the OP engineer boot.img in ODIN. this fixed the update binary issue, woot, and rebooted again fine.

I also got this to work on the third try on pj2. The first two were one hundred percent my mistake as both times I missed something very plainly stated in the OP. I would say to anyone experiencing difficulties to read over the threads where the OP files originate. That's what allowed my bone head to see what I was doing wrong. I can't believe I finally have root and hotspot! Thank you for all the hard work folks!

Oh man. Do you even know how much you helped me out. I have succesfully rooted 7.0 on my s7 edge. Will post tutorial soon, much credit to you sir you are awesome.
Edit:https://forum.xda-developers.com/sprint-s7-edge/how-to/sm-g935p-spr-root-nougat-7-0-data-t3568780

I can confirm this works 100% on PK1. Thank you so much

Any of you have any tips on fixing the lag? I love root but might go back due to lag and battery drain