Will I lose my data during the root process?

Does this method trip Knox?

Does Samsung Pay work?

Does Android Pay work?

What happens if I brick my phone?

I installed the ADB system-wide on my Windows computer/laptop, but I see "'adb' is not recognized as an internal or external command, operable program or batch file".

I can't get Odin to flash the images.

BusyBox won't install.

I am seeing odd blank menus in Settings that causes it to force-close when I click it. Also Quick Settings force-closes when editing.

You shouldn't if you're just rooting, however you shouldmake a backup. Helium from the Play Store is a good choice as is Samsung's built-in cloud backup. If you have to flash the stock image for any reason, it will erase your app data as well as the internal storage (internal sdcard) so be sure you copy any important files to a safe location first. It's always a good idea to have backups and it's generally assumed that users who are looking for root/admin access to their phones know and accept the risks involved.No, it doesn't. And flashing back to stock will allow Knox to work again, as long as you didn't flash files from other sources (there are some that will trip Knox, so be careful).No, sorry. They can detect the rooted boot environment through a driver, so you can't even hide root from the app using RootCloak.It does, but you have to make a change that disables root and then reboot your phone. You can toggle this back/forth without flashing, but you either get root or Android Pay at any one time.As long as there are stock images to flash back to, it's almost impossible to do this no matter how badly the process goes. Check that we have stock images; if we do, then we can always flash them over the device using the unroot method in this guide. That practically guarantees a return-to-stock experience for a phone as long as it doesn't have any serious physical damage preventing it from powering on.Your user profile path can't contain a space. That means if your Windows user is 'Somebody Nice' and thus your Windows user path is 'C:\Users\Somebody Nice', the install will fail. You can create another user on your computer (if prompted for a Microsoft login, choose to make only a local account) and enter a short, single-word name for your user. Sign into and use that user profile instead. Also, the path where you extract the SuperSU package can't contain a space, so try extracting them to somewhere simple like perhaps C:\S7Root.This typically means you haven't followed the instructions carefully. Read the prerequisites for each section, don't skip or skim anything, and make sure you've downloaded the files for your phone. This guide works for both the S7 and S7 Edge, so only download the correct files relative to your device. There are also two versions of Odin going around that work slightly different from each other. If one is causing issues, try the other.Try another BusyBox installer, like JRummy's BusyBox for Android which is known to work.We suspect that XTouchWiz is causing this and I recommend uninstalling that Xposed module. Then either flash the latest version of my fix+debloater package in the 'Recommended Next Steps' section or manually use a file explorer to delete /system/csc/feature.xml (leave everything else alone). Reboot and the menus and force-closes should be fixed.