Yeah! The latest flagship killer from Samsung is here. And you might just want to cuddle with it a little, may be root it, or install a custom ROM. But, in order to do that, you must first have a custom recovery installed. So, today we are going to help you on how you can easily install TWRP, disable forced encryption and finally root Samsung Galaxy S7.

The era of the old ClockWorkMod has seen its history, but TWRP is yet the most renowned and stable custom recovery available for Android devices. It lets you perform a variety of useful functions on your Android, like flashing zip files, repairing filesystems, mounting and formatting partitions, backing up ROMs, and much more. These functions could come in handy, if you’re looking to go par enforced Samsung protocols.

Huge thanks to XDA member — jcadduono, who has brought the TWRP experience to the S7. He is also the official TWRP maintainer of Galaxy S7. So users can now instantly go on flashing and mopping, without any hesitation.

The process of TWRP installation follows the use of Odin tool to flash the recovery, which is quiet easy and doesn’t require an expertise. Just your S7, USB cable, PC with Windows OS, and an internet connection, will be sufficient to carry out the complete process.

Once TWRP is installed, you can easily disable forced encryption and root Samsung Galaxy S7.


INSTRUCTIONS


TWRP officially supports Galaxy S7. The currently supported Exynos based devices are:

  • G930
  • G930F
  • G930FD
  • G930X
  • G930W8
  • G930S
  • G930K
  • G930L

Do not install this on any other models (Qualcomm-based), than the ones listed above, the conclusion are unknown and may prove harmful.

Disclaimer

Flashing TWRP will most-likely trigger the KNOX counter. Understand the risk of rooting your Android and follow the procedure only then. DroidOrigin shall not be held responsible for any damage to your S7.

Before You Begin

  • Disabling forced encryption requires you to completely wipe the internal storage, so backup everything – Internal storage, messages, contacts, etc.
  • Download and install Samsung USB drivers.
  • Charge your S7 to at least 60% battery level. This will avoid any device shut downs during the process.
  • Enable OEM unlock, under Settings > Developer options.
  • Download Odin Flasher v3.10.7 and extract it: Link
  • Download latest TWRP recovery for your S7: Link
  • Chainfire’s SuperSU: Link
  • dm-verity and forced encryption disabler: Link

 

Install TWRP Recovery

  1. Open the folder where ‘Odin3_v3.10.7.zip‘ file was extracted. Double-click on ‘Odin3 v3.10.7.exe, to start the Odin program.
  2. Time to boot your S7 into Download mode — Power off the device completely. Now, press and hold the Volume down, Home, and Power button altogether until a blue coloured warning screen shows up. Press the Volume up key once, to finally enter Download mode.
  3. Once the device is in Download mode, connect it to the PC using the USB cable.
  4. Odin will now detect the phone and display the corresponding ID:COM port. In case it doesn’t, try restarting Odin, and make sure that the drivers have been properly installed.
  5. Under Options, in Odin window, make sure that everything is untouched.
  6. Click on the AP button. Now, browse and select the ‘twrp-3.0.2-4-herolte.img.tar’ file.
    Root Samsung Galaxy S7 (Odin Screenshot)
  7. When everything is set as stated, click on the Start button.
  8. Hold back for a few seconds, and once the process is about to complete, hold down Volume up and Home button. So now when your S7 reboots, it will enter TWRP recovery. You can release the buttons once you see the TWRP screen.

 

Disable Forced Encryption, and Root Samsung Galaxy S7

  1. In TWRP, go to Wipe > Format Data. Enter the keyword ‘yes‘, in the provided space and enter. This will wipe the automatically encrypted filesystem, and decrypt it.
  2. Once the wiping is done, reboot back into recovery. Go to Reboot > Recovery.
  3. When the recovery boots again, connect your S7 to the PC and Enable MTP under the Mount section.
  4. Transfer the downloaded no-verity-opt-encrypt-4.1.zip’ and ‘SR4-SuperSU-v2.78-SR4-20161115184928.zip’ to your S7’s internal storage.
  5. Disconnect the device now.
  6. Tap on Install. Now, navigate your phone’s storage and select ‘no-verity-opt-encrypt-4.1.zip’. Finally swipe the ‘Swipe to confirm Flash’ button on the bottom of the screen.
  7. The flashing process will merely take a few seconds. And when its done, follow the same method to flash the root package – ‘SR4-SuperSU-v2.78-SR4-20161115184928.zip’.
  8. Okay, its done. Go to Reboot and tap on System to finally reboot your S7.

The first boot might take a few minutes, so don’t worry, have patience and let it do its job. Now that you have installed TWRP and rooted the Galaxy S7, you can choose to install custom ROMs, kernels, or mods.

If you want to confirm that the root method has worked, download Root Check app from the Play Store and run it.

Root Check
Developer: JRummy Apps Inc.
Price: Free

The appreciations goes to jcadduono for his work, that has led us to root Samsung Galaxy S7.

It was fun, installing TWRP and rooting your newly brought S7. Have you faced any issues during the process? Let us know through comments. Don’t forget to share this article with your friends who own the S7.

SOURCEXDA-Developers
SHARE
Previous articleAndroid N Features – What We Know So Far
Next articleHow to encrypt Android Smartphones and Tablets
Dhananjay (DJ) is an Android devotee and a Tech Blogger by profession. He is a keen undergraduate, seeking and working hard on his ambitions to achieve something distinctive in his life. He prefers interacting with his readers in the most reproaching manner possible and his desires here are not just to reach out the tech figures, but also attract those those non-interested minds to our Android universe. He proudly owns Nexus 6P, Nexus 5, OnePlus One and a Nexus 4.
  • plz help i canit find wher odin 3something zip was extracted?? when extract???

    • Extract the “Odin3_v3.10.7.zip” to the desktop, using WinRAR.

      • tisk tisk, show Igor Pavlov’s 7-zip some love. WinRAR is so 2006.
        (not sure if the name gives it away)

        • Right click on Odin3_v3.10.7.zip. 7-Zip > Extract here.
          A new folder (Odin3_v3.10.7) will appear in the same directory where you extracted the file, just now. Open it, and double-click on ‘Odin3 v3.10.7.exe’.

  • So I think it flashed TWRP properly, because I get a “PASS!” message in Odin, but I can’t seem to reboot into TWRP by pressing Volume Up and Home… Any tips? Thanks!

    • You have to press Volume Up and Home button, just at the time when your S7 is about to restart after the PASS! message. And keep them pressed until your device enters TWRP.

      Also, make sure that OEM unlock is enabled under Settings > Developer options, before doing all this.

      • I kept trying that, but it didn’t work. In the end, I also had to hold down the Power button, along with Volume Up and Home. Now I’m rooted, and everything works!

        • Glad to know that it worked. The idea behind this step was to save pressing of power button, since the device is reboot itself. But anyways, its all the same at the end. If you need something else for the S7, let us know.

  • Please give more explanations why should one disable or not disable
    Forced Encryption? I suppose at least boot = restart time goes down, but
    by how many seconds? Please measure.

    • Thank you Sam for the valuable advise. We will surely consider adding more information.
      Over to your questions. Enabling or disabling forced-encryption is solely a variable choice, where device performance is a major aspect.

      But then that is subjective too. Why? If you are using an high-end (Better hardware) device such as the S7, the performance of the device wouldn’t make much difference. While we had the S7, we used it encrypted for a week and rest of the time it stayed decrypted. We didn’t see any visible delays or lags. Yes, if you would take benchmarks and calculate the boot up time, they might show slight difference, but nothing significant that you may physically notice.

      And also, performance difference between encrypted and decrypted device is majorly seen is low-end devices. And the gaps shortens as the hardware gets better.

  • kzshantonu

    After flashing no-verity-opt-encrypt-2.1.zip, can I re-encrypt the device and flash original system, boot and recovery images later? Also, if I flash original system, boot and recovery images will the OS read the non-encrypted partitions correctly? Thanks

    • Yes, if you restore the complete stock firmware, your device’s storage will auto-encrypt on first boot. When decrypted, the OS should read the non-encrypted partition just as it does normally.

  • Good luck with that 🙂

  • Allan Kemp

    I have triggered the security warning by flashing twrp, is it still possible to get twrp by reflashing the dm-verity override.

    • Hello Allan. We didn’t quite understand, could you please elaborate more on what do you want to achieve? We will be more than happy to help.

      • Allan Kemp

        I just want the phone to boot, Top left reads: Custom Binary Blocked by Secure Boot (recovery.img) Screen Reads: Security Error: This Phone has been flashed with unauthorized software & is locked. Call your Mobile operator for additional support. I have no functional recovery and the phone boot loops into that security warning. I have odin mode still functional but cannot flash rom with odin.

        • Samsung G935X is S7 Edge. You may have flashed the TWRP for S7.
          The right guide for your is here: http://www.droidorigin.com/root-samsung-galaxy-s7-edge/

          • Allan Kemp

            twrp-3.0.2-0-hero2qltechn.img was the file i flashed. I dont think i will be able to reflash now though will i?

          • Allan Kemp

            when i try flash stock firmware odin says: SW REV CHECK FAIL: [aboot]Fused 3> Binary 2
            [1] eMMC write fail : aboot

          • Allan Kemp

            when i try flash TWRP Screen Reads: Secure Check Fail: recovery
            odin reads
            Added!!
            Odin engine v(ID:3.1203)..
            File analysis..
            SetupConnection..
            Initialzation..
            Get PIT for mapping..
            Firmware update start..
            SingleDownload.
            recovery.img
            Complete(Write) operation failed.
            All threads completed. (succeed 0 / failed 1)
            Removed!!
            Added!!
            Odin engine v(ID:3.1203)..
            File analysis..
            SetupConnection..
            Initialzation..
            Get PIT for mapping..
            Firmware update start..
            SingleDownload.
            recovery.img
            RQT_CLOSE !!

            Complete(Write) operation failed.
            All threads completed. (succeed 0 / failed 1)

          • Download this file and flash it via ODIN: https://dl.twrp.me/hero2lte/twrp-3.0.2-3-hero2lte.img.tar.html

            See if it works.

          • Allan Kemp

            Had already tried that one also, but tried again
            Added!!
            Odin engine v(ID:3.1100)..
            File analysis..
            SetupConnection..
            Initialzation..
            Get PIT for mapping..
            Firmware update start..
            SingleDownload.
            recovery.img
            NAND Write Start!!
            RQT_CLOSE !!

            Complete(Write) operation failed.
            All threads completed. (succeed 0 / failed 1)

            Have also tried different versions of odin, including the modded version “Odin_v3.12.3_Patched_SHA256”

          • I believe flashing the wrong recovery has messed up your device partition. Did you try and flash the complete stock firmware that has BL, AP, CP, and CSC files?

          • Allan Kemp

            I have tried that, with and without a matching pit file. I don’t know what else to try. Might be properly bricked. I also can’t take to Samsung because I’m in Australia and they won’t service anything other than a Australian model.

          • Flashing a file from another device could be disastrous. Just a shot in the dark, try flashing stock firmware without Bootloader (BL) file. Just use AP, CP, and CSC.

          • Allan Kemp

            Same again, and smart switch gets to 100% and then hangs the application does nothing on either end. So parts it is i guess (good thing its mint – bought on ebay as “for parts”)
            Added!!
            Odin engine v(ID:3.1203)..
            File analysis..
            SetupConnection..
            Initialzation..
            Set PIT file..
            DO NOT TURN OFF TARGET!!
            Get PIT for mapping..
            Firmware update start..
            SingleDownload.
            boot.img
            recovery.img
            system.img.ext4
            FAIL! (Auth)

            Complete(Write) operation failed.
            All threads completed. (succeed 0 / failed 1)

            PS: Thanks for all your help regardless of the end result i really appreciate it.

          • Allan Kemp

            Update: Did what you said the last time again, which triggered device to think it had a smart switch error. Then i was able to do emergency restore in smart switch. Device is fully operational. Although still T-Mobile locked and useless in Australia unless i can unlock which was what i was trying to do in the first place.

          • I am extremely happy that you got it working again. At least you have now gained some experience.
            I believe if you are trying to SIM unlock S7 Edge (T-Mobile), then you would like to have a look at this: https://support.t-mobile.com/docs/DOC-28005

          • Allan Kemp

            Yeah no good unlocking it the legitimate way T-Mobile wont help me and the device is currently ineligible for unlocking.
            Thanks though.

          • I wish we could be of more help here. Apologies Allan.

      • Allan Kemp

        Phone is currently on the “Samsung_G935x_Root_Boot_QC” version i had device functional with root, flashed TWRP via flashfire and soft bricked the phone.

  • wondim

    Nice tutorial! However, the link for “dm-verity and forced encryption disabler” is dead. This link worked for me https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-4.1.zip

    • Thank you wondim for notifying us of the broken link. I have fixed and updated the link as per your suggestion. Sorry, for the inconvenience caused.