[Recovery][Exynos] Official TWRP for Galaxy S7 edge (hero2lte)

Search This thread

shah22

Senior Member

I would recommend to start anew if you don't want any trouble , reflash stock in odin , then flash latest twrp and reboot into it directly (don't tick auto restart on odin) then its upto you if you want to go systemless root like magisk (if not do swipe for modifications) , when in twrp go to wipe and format data , reboot again to twrp , flash magisk/super su, then reboot and let phone initialize

If you go systemless route you won't need any verity zips , if you choose modifications then you need to flash no verity force encrypt zip after flashing magisk/super su(without reboot)

If you wanna take risk (you would have to format data in twrp either way so backup your stuff first) , just flash twrp in odin, untick auto restart , boot directly into it and do wipe>format data and then reboot again in twrp , install magisk/supersu + no verity force encrypt zip (no need for no verity if you didnt do modifications), then reboot to phone (i am not sure what effect will previous cf auto root installation have if rooting again with magisk/super su).

Here one thing is of consideration , twrp had some quota problem on android oreo rom (don't know if its fixed in latest version) , it would not detect data after rebooting into it and hence we needed to format data every time , some users said it only happened when rooting with magisk, while some said they were fine, it is either due to forced encryption or quota thing. If twrp behaves like this flash tkkg1994's modified twrp.

Also before doing anything make sure to check that oem unlock is on and you have efs folder backed up..

Sent from my S7 Edge using XDA Labs
 
Last edited:
  • Like
Reactions: force70

AndroidS70

New member
Aug 29, 2019
4
0
Hello i guess ill try my shot here as well, since its all about s7, etc. Back in older days you could pull whole userdata partition, convert to vhd, mount, then use recovery programs to read your "formatted" aka deleted but not overwritten data and recover all of your lost files, blocks, etc which are still in good condition, but now i ran into some problems = recovery programs find nothing meaningful in my partition or whole memory blocks, is it because oreo as android encrypts userdata on its own?

IS there ANY possibility to recover my lost data (formatting accident when rooting) from my phone? Or simply these things are impossible with newer androids, at least the approach i am trying and which worked fine back in the day, but now its old news?
 

jackching

Senior Member
May 21, 2013
164
18
After reading through this multiple times, im still not 100% sure on what to do in my situation. All i want is a custom rom rooted on the canadian variant. The phone has the most recent factory firmware on it now. Im interested in Viperos and want it rooted. I think it might be the #10 step throwing me off.
 

Superheat

New member
Nov 9, 2019
3
1
Hi,

I have the latest official oreo stock rom G935FXXS6ESH1. Non rooted device(since 2017). Is it safe to flash the latest twrp via odin. I just want to make a full nandroid backup so I can root and install custom roms.

Thanks in advance.
 

syednawaz

Senior Member
Sep 30, 2015
757
248
Samsung Galaxy S8
Hi,

I have the latest official oreo stock rom G935FXXS6ESH1. Non rooted device(since 2017). Is it safe to flash the latest twrp via odin. I just want to make a full nandroid backup so I can root and install custom roms.

Thanks in advance.

You can root your device, but backup your internal memory like photo or videos and contact and texts to sd card or to your pc. Bec when you install twrp the first thing it will ask is format data, where you will lose everything, search for s7 edge twrp and you will get alot of youtube video on how to install it. Also you will lose samsung pay and some other functions when you root, i am still half not satisfied with rooting my phone, so think alot what you will get from rooting.

Too long to read, you must back your data before you do anything else.
 
  • Like
Reactions: Superheat

Superheat

New member
Nov 9, 2019
3
1
My friend, I have a question, even though my baseband/bootloader binary version is now 6, its ok to flash latest twrp? As long as oem/debugging is on. Wiping the data after installing twrp will not give me 'not registered on network' right? Is it possible to make full nandroid backup via twrp first before root? Thank you my friend.
 

syednawaz

Senior Member
Sep 30, 2015
757
248
Samsung Galaxy S8
My friend, I have a question, even though my baseband/bootloader binary version is now 6, its ok to flash latest twrp? As long as oem/debugging is on. Wiping the data after installing twrp will not give me 'not registered on network' right? Is it possible to make full nandroid backup via twrp first before root? Thank you my friend.

Yeah you can flash twrp on new version as well just follow the step.
After installing twrp, it will format your device which will be like factory reset, you will not lose modem or bootloader, but you will need a sdcard so you can copy system, modem or others, but no data( which are other applications which you have installed) as its already deleted because of format.

The imei issue happens when you are running a 2018 baseband and you install custom rom update your bootloader to 2019 but not modem or vise versa, so then imei is lost, for g935 or g930 its easy as you just flash latest modem and bootloader again and you will get them back. And you can find them here in some post.

Always check your model before you flash anything. And again, make a backup of your important stuff.

Just in case
If you find your internal storage 0. Just go to wipe, click on format data and then swipe.

Lastly, Good luck bro
 
  • Like
Reactions: Superheat

mastabog

Senior Member
Oct 1, 2008
192
28
Galaxy S7, Android 8.0.0, BTU August update. I installed TWRP 3.3.1 via Odin then swiped right, then I got a boot loop. Then I read the instructions in the 1st post here which say in step 10

If you only want a bootable system partition:
Download the latest dm-verity and force encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.

I did that and Android got past the Samsung screen and didn't reboot (yay) but then immediately said

Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data.

WTF? Any ideas? Would flashing a stock rom via Odin work? I don't want to lose the current data and don't want to root.

EDIT: Ok, I just tried to flash a stock firmware with Odin like I did so many times before. But after placing the BL+AP+CP+CSC files, Odin goes straight to reboot and reboots the phone, it doesn't flash anything!

EDIT 2: Managed in the end. The windows drivers for Odin were getting muddled by a running adb server in the background. Rebooted the PC and tried again, then Odin worked.
 
Last edited:

syednawaz

Senior Member
Sep 30, 2015
757
248
Samsung Galaxy S8
Galaxy S7, Android 8.0.0, BTU August update. I installed TWRP 3.3.1 via Odin then swiped right, then I got a boot loop. Then I read the instructions in the 1st post here which say in step 10



I did that and Android got past the Samsung screen and didn't reboot (yay) but then immediately said



WTF? Any ideas? Would flashing a stock rom via Odin work? I don't want to lose the current data and don't want to root.

EDIT: Ok, I just tried to flash a stock firmware with Odin like I did so many times before. But after placing the BL+AP+CP+CSC files, Odin goes straight to reboot and reboots the phone, it doesn't flash anything!

EDIT 2: Managed in the end. The windows drivers for Odin were getting muddled by a running adb server in the background. Rebooted the PC and tried again, then Odin worked.
Hmmmm ? you have any issue now?

And look at the post above you, in that i said that after installing twrp you have to format data, which is like doing a factory reset. And you will lose all your data.
 

expansion valve

New member
Dec 28, 2019
1
0
dm-verity appeared again.

Hmmmm you have any issue now?

And look at the post above you, in that i said that after installing twrp you have to format data, which is like doing a factory reset. And you will lose all your data.

Hello,
I flashed twrp 3.3.1 via odin, formatted data and flashed Magisk-v20.1, after I finished setting-up the phone and verified that I am now rooted, I reboot into TWRP to make nandroid back-up before installing custom roms, but the dm-verity appeared again. My problem is, do I need to flash also the no-verity-opt-encrypt.zip?? format data and flash magisk again? I have official stock oreo firmware (G935FXXS6ESH1). Thanks in advance.
 

syednawaz

Senior Member
Sep 30, 2015
757
248
Samsung Galaxy S8
Hello,
I flashed twrp 3.3.1 via odin, formatted data and flashed Magisk-v20.1, after I finished setting-up the phone and verified that I am now rooted, I reboot into TWRP to make nandroid back-up before installing custom roms, but the dm-verity appeared again. My problem is, do I need to flash also the no-verity-opt-encrypt.zip?? format data and flash magisk again? I have official stock oreo firmware (G935FXXS6ESH1). Thanks in advance.

yes on page first check step 10 and download and install dm verity disabler. before that you must have enabled oem unlock and usb debuggging in developer menu. after that you an easily root the rom with magisk.
 
  • Like
Reactions: engr.clifford

busterybub

New member
Mar 28, 2020
1
0
Can’t move forward

So I got everything but what is happening now is that on Odin when I flash the twrp for s7 edge, at the point that I am supposed to press the down volume, home, and power buttons the phone is removed from Odin. And I only get a com4 not com6. Any help would be awesome cause I have no idea why it won’t open the TWRP after pressing 3 buttons and the releasing the power button.

Also, I have noticed that when downloading TWRP file from two youtube rooting guides the icon for the .tar looks like a .rar icon whereas my icon is like a piece of paper. I wonder in there is something I am missing and downloading the wrong recovery file.
 
Last edited:

gfachinello

New member
Mar 29, 2020
3
0
Red screen

Hey guys
I am trying to install twrp 3.14.1 on my s7 g935f.
After doing the procedures to install via odin, I restarted the phone and it did not start in recovery mode, and now when starting the device it is only on a red screen.
I tried to reinstall the stock rom, but without success, how do I proceed?
Thanks
 

Top Liked Posts

  • There are no posts matching your filters.
  • 203
    Team Win Recovery Project 3.0.2-4



    This is for the International SM-G935F/FD/X, Korean SM-G935K/L/S, and Canadian SM-G935W8 Exynos models only! Do not flash on flat S7 or Qualcomm models!

    WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
    You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.

    WARNING #2: The Galaxy S7 stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
    SOLUTION: Follow the full rooting steps below, in order, to allow system modifications without the risk of a boot loop!


    WHAT IS TWRP?

    Oh come on, you know what it is - don't try to fool me!
    In case you're serious, though...

    Team Win Recovery Project is a custom recovery for Android devices.
    It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.

    DOWNLOAD

    You can find the device page here:
    http://teamw.in/devices/samsunggalaxys7edge.html

    There is a download link there, as well as instructions on how to flash it.

    I highly recommend using Odin to flash when possible.
    You can find a zip containing Odin as well as Samsung's Mobile drivers here:
    https://build.nethunter.com/samsung-tools/

    FULL STEPS FOR OBTAINING ROOT

    You can follow this video by Max Lee if you'd like: How to Root Galaxy S7 & S7 Edge! [Exynos ONLY]
    Otherwise, follow these instructions:

    1. In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
      Transparent.gif
    2. Now go to Settings -> Developer options. (above About device)
      You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
      Transparent.gif
    3. Extract Odin_3.12.3.zip to your computer.
      Transparent.gif
    4. Install Samsung Mobile Phone Drivers for Odin to find your device.
      Transparent.gif
    5. Download a .tar image of TWRP for hero2lte.
      Transparent.gif
    6. Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
      Once you reach the Download mode warning screen, press [Volume Up] to continue.
      Transparent.gif
    7. Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
      Transparent.gif
    8. Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
      If you don't see then TWRP boot splash try again from step 6.
      Transparent.gif
    9. At this point, you will reach the screen asking you if you want to allow system modifications.
      By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
      If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
      Transparent.gif
    10. If you want to be rooted with SuperSU:
      Download the latest SuperSU by Chainfire.
      Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
      You will need an external SDcard for this method, if you don't have one you will have to use adb sideload to install SuperSU.

      If you only want a bootable system partition:
      Download the latest dm-verity and force encryption disabler zip.
      Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
      Note: This does not disable the forced encryption on Bxxx firmware, only Axxx firmware due to a change in vold by Samsung.
      Transparent.gif
    11. Go to [Reboot] -> [System].
      Transparent.gif
    12. Wait 2-5 minutes for your device to finish setting itself up.
    * MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.


    CHANGES
    • v3.0.2-4 - Fix restoring of non-ext4 partitions, update f2fs drivers, update to BPID source & Linux 3.18.43
    • v3.0.2-3 - Fix booting on BPH6/APGH bootloaders, rebase on Note 7 sources, enable NTFS-3G formatting
    • v3.0.2-2 - Fix MTP issue in kernel
    • v3.0.2-1 - Separation of Korean variants, retrieve actual model from bootloader, drop modem from fstab, remove legacy flags, add bootdevice symlink, last_kmsg support
    • v3.0.2-0 - See here for the changes.
    • v3.0.1-0 - Fixed USB OTG storage
    • v3.0.0-0 (twrp.me) - Disabled backup/restore of modem partition (must be signed and flashed in Odin)
    • v3.0.0-0 - Initialize new device tree based on Samsung OSRC G935FXXU1APAW kernel.

    FEATURES
    • MTP support
    • USB Mass Storage support
    • Micro SDcard and USB OTG storage support
    • f2fs file system support (read, write, format, backup & restore)
    • exFAT file system support (read, write, format, backup & restore)
    • NTFS file system support (read, write, format)
    • ADB root
    • Full SELinux support
    • Built in android 6.0 tree

    KNOWN ISSUES

    CONTACT & SUPPORT

    You can find us on IRC at #twrp on chat.freenode.net.
    You can also post in this thread and I will attempt to answer any questions you may have.

    SOURCE CODE

    TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
    Device tree: https://github.com/TeamWin/android_device_samsung_hero2lte (android-6.0)
    Device tree (Korea): https://github.com/TeamWin/android_device_samsung_hero2ltekor (android-6.0)
    Kernel: https://github.com/jcadduono/android_kernel_samsung_universal8890 (twrp-6.0)

    CONTRIBUTIONS

    Gerrit for TWRP: http://gerrit.omnirom.org/
    Gerrit for officially supported devices: http://gerrit.twrp.me/

    XDA:DevDB Information
    Team Win Recovery Project - Samsung Galaxy S7 edge, Tool/Utility for the Samsung Galaxy S7 Edge

    Contributors
    jcadduono, Team Win & friends
    Source Code: https://github.com/TeamWin/android_device_samsung_herolte


    Version Information
    Status: Stable
    Current Stable Version: 3.0.2-4
    Stable Release Date: 2016-10-15

    Created 2016-03-11
    Last Updated 2016-11-08
    67
    Hey guys :) :highfive:

    Some may know me, some probably not. It's not important who I am BUT I found that our device tree for TWRP builds is damn outdated (based on MM).

    I don't know if you faced this issue already, but some people couldn't mount /data partition in TWRP even though they removed encryption. Why this happens?

    Explanation:
    Samsung added quota support in their oreo update for the /data partition. Means a TWRP update with proper quota support is needed to get this new feature to work. Till now, many developer simply disabled this feature again on their kernels (so they can mount /data without issues on the old TWRP).

    What I did:
    I updated the tree with the latest files, kernels and so on. Including the above mentioned quota support.

    This TWRP version works on stock and supported oreo kernels. Older kernels (which removed quota to fix mounting problems) won't work here. Please advice your kernel developer to update his kernel with the changes :good:

    Download:
    Img file (flash via TWRP)
    tar.md5 file (flash via odin)
    39
    Reserved

    If you have a G935P, G935V, G935R, or G935A (aka the US Snapdragon models) your bootloader is locked. I will not be making TWRP for your device - it simply cannot happen. Sorry.
    Update: G935T users can expect TWRP for their devices as soon as T-Mobile convinces Samsung to unlock the bootloader - I already have a fully complete working build ready.

    You know who you can blame?

    THE DONALD!~~~~~~~~~~~~
    or Obama, I dunno, blaming Obama is getting kind of old guys, sorry.
    19
    Just a quick step by step - including the steps I couldn't figure out because I'm a samsung newbie.

    Downloads needed:

    Samsung Drivers: http://developer.samsung.com/board/download.do?bdId=T000000117&attachId=0000000003
    Odin: https://idlekernel.com/flash-tools/Odin_3.10.7.zip
    TWRP: https://idlekernel.com/twrp/hero2lte/ ##.md5 file##
    No verity: https://idlekernel.com/fun-stuff-trust-me/no-verity-opt-encrypt.zip
    SuperSU: https://download.chainfire.eu/924/SuperSU/BETA-SuperSU-v2.68-20160228150503.zip?retrieve_file=1

    Steps:
    1. Install Sammy drivers
    2. Extract Odin, place TWRP file into the same folder
    3. Transfer No-verity-opt-encryption.zip + BETA-SuperSU-v1.68.zip to phone.
    4. Power phone off
    5. Press all 3, Volume DOWN + Home + power till screen turns on.
    6. Press confirmation key
    7. Open Odin
    8. Click "AP" key and select TWRP file
    9. "Start" in Odin
    10. power off phone upon completion
    11. Press all 3, Volume UP + Home + Power till screen turns on.
    12. Swipe to allow
    12. wipe - "FORMAT DATA" ##NOT ADVANCED WIPE##
    13. Install - No-verity-opt-encryption.zip
    14. Reboot - Recovery
    15. Flash SuperSU
    16. Reboot System
    17. Enjoy.
    11
    I will need someone to verify if features are working as this was just a copy paste of the herolte (non-Edge) device tree.
    Mainly expecting brightness slider to not work, so please if things don't work, join #twrp on freenode and talk to me.