In this straightforward step by step guide, I am going to show you how to root Samsung Galaxy S7 for any carrier.
Prerequisites to root Samsung Galaxy S7
- Samsung Galaxy S7 (any carrier)
- Microsoft Windows PC
- Make a Backup of the data on your phone, including pictures and videos.
Steps to root Samsung Galaxy S7
Step 1: Install Samsung USB device drivers
STEP 2: Install ADB (system-wide)
- On your phone, go to Settings -> Lock screen and security.
- Make sure that “Secure startup” is off/disabled. This option prevents the su binary from giving root.
- Again on your phone, go to Settings -> About phone.
- Tap on the space that says ‘Build number‘ seven times until it tells you that developer mode/options have been enabled.
- Tap back and then tap on Developer options.
- Make sure that developer options are ON (general setting at the top of the Developer options screen) and then scroll down to USB debugging. Tap to enable USB debugging.
- Connect phone to PC via USB.
- At your PC, OPEN Windows command prompt (Win+R and type ‘cmd’ and press enter or find it under Start -> Accessories).
- In the command prompt, type adb wait-for-device.
- Your phone may prompt you to authorize the computer and it is important that you approve the authorization and check on to “Always allow from this computer”.
- If it doesn’t prompt you, that’s fine (you may have given it authorization some other time), but you should not skip this step or the root process may not work.
- After the adb command in command prompt returns to a blinking prompt, you may close the command prompt window (or just type exit inside the prompt).
Note: if typing the ‘adb’ command gives you the message “‘adb’ is not recognized as an internal or external command, operable program or batch file”, then please check the F.A.Q./Help section of this guide.
STEP 6 : Download and extract Odin3 v3.12 (try either version)
DOWNLOAD Odin3_v3.12.zip (MD5 hash F4BAE9E20925DA85854A9C49E8E06F1C)
Note: most people use the PrinceComsy version, but some AT&T users said the other version will prevent bootloop/stuck AT&T logo.
STEP 7: Download engineer-rooted boot image appropriate for your model of phone:
Note: that this download is a TAR file and while it looks like an archive, you should not extract its contents.
- Power off the phone.
- Turn it back on while holding Home, Volume Down, and Power buttons at the same time to enter download mode.
- Press Volume Up to confirm that you want to flash data to the phone.
- Open Odin.
- Click ‘AP‘ and select the appropriate AP TAR file: Samsung_G930x_QC_Rooted_BOOT.TAR (any Samsung Galaxy S7)
- Still, in Odin, click ‘Start‘ to flash the engineer-rooted boot image and reboot the phone.
- When the phone has finished rebooting and while it is still connected to your PC, enter settings and re-enable USB debugging if it has been disabled.
- Start the SuperSU flash package by double-clicking ‘root.bat’ from ‘SuperSU-v2.76-S7QC’.
- Once it finishes, the phone will automatically reboot again. If double-clicking ‘root.bat’ only briefly shows a command prompt that quickly disappears, then most likely your PC is not recognized/authorized for USB debugging, the USB cable isn’t connected, or ADB isn’t properly installed. Check the steps above and try again or check the F.A.Q./Help section of this guide for more.
- You’ll know that the ‘root.bat’ process has completed successfully when your phone reboots. Once it has finished rebooting, SuperUser may inform you that the ‘su’ binary is outdated and that you should update. Dismiss this notice for now as Chainfire has indicated that our build is unsupported and that we should not update. As of right now (July 15, 2016), v2.76 is the most recent version for our phone.
Proceed to the recommended next steps to fix some odd quirks and behaviors with the root boot image.
RECOMMENDED NEXT STEPS (after rooting)
Prerequisite: rooted Samsung Galaxy S7 (any carrier)
STEP 1: On your phone, open the SuperSU app (installed during the root process) and tap on Settings. Half-way down under Security, tap on “Enable su during boot”. This option will ensure that startup scripts that are installed during this process get to do their job
STEP 2: Install FlashFire on your phone: DOWNLOAD FLASH FIRE
STEP 3: Download the fix or fix+debloat script flashable ZIP package appropriate for your model of phone and COPY this file to your device:
DOWNLOAD S7_or_S7Edge_Fixes_V15.zip (MD5 hash F15CD9BDC35382A8F48FFBEDBB1BCDF0) (any Samsung Galaxy S7 or S7 Edge)
DOWNLOAD S7_or_S7Edge_Fixes_Debloater_V15.zip (MD5 hash 4DED5D7B09BB7672723AAA77F395BC87) (any Samsung Galaxy S7 or S7 Edge)
DOWNLOAD VZWS7_PE1_Fixes_V15.zip (MD5 hash 7FEE320A9749B7CDFBAEACCBDC8AC45C) (Verizon Samsung Galaxy S7 on *PE1 firmware)
DOWNLOAD VZWS7_PE1_Fixes_Debloater_V15.zip (MD5 hash 9146006E9A3C5AB5CAF9EB6123F7DB77) (Verizon Samsung Galaxy S7 on *PE1 firmware)
DOWNLOAD VZWS7Edge_PE1_Fixes_V15.zip (MD5 hash 5F7CC8C95D316332B581F982D4ECAAF9) (Verizon Samsung Galaxy S7 Edge on *PE1 firmware)
DOWNLOAD VZWS7Edge_PE1_Fixes_Debloater_V15.zip (MD5 hash 00850CA4D879660E74A54CFD3D47D0E5) (Verizon Samsung Galaxy S7 Edge on *PE1 firmware)
What’s special with the Verizon-only files? We flash a patched /system/framework/framework-res.apk that bypasses Verizon’s Wi-Fi hotspot tethering provisioning. This is only compatible with the PE1 firmware and only for Verizon.
- Launch FlashFire on the phone and click the (+) button in the lower right to add a step.
- Select a ‘Flash ZIP or OTA’ flash step. Locate the flashable ZIP package and select it.
- For options, check on ‘Mount /system read/write’ and leave the rest of the options unchecked.
- Scroll all the way down and click the ‘Flash’ lightning button in the lower left to commit this single step and wait a few moments. You should see the phone flash the package briefly before rebooting twice.
Will I lose my data during the root process?
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.
I can’t get Odin to flash the images.
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.
BusyBox won’t install.
Try another BusyBox installer, like JRummy’s BusyBox for Android which is known to work.
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.
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.