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

Search This thread

exnokiafan

Senior Member
Aug 29, 2014
333
43
48
have u try "format data" ?
if not, u had to do that, but remember to backup storage before proceed

Of course mate. I've successfully completed the task multiple times on other devices. Last week on a Galaxy A5 on oreo and a couple of months ago on my S7. But yesterday I flashed the latest stock oreo and that's the result. I just wanted a stock rom with my personal debloat and that's where I'm at now :(
 

exnokiafan

Senior Member
Aug 29, 2014
333
43
48
have u try "format data" ?
if not, u had to do that, but remember to backup storage before proceed

A user suggested not to swipe for modifications, in order not to trigger the dm-veriti thing. Then flash both dm-verity and remove_encription, then magisk.

I don't know if this might work.
 
Last edited:

Tkkg1994

Recognized Contributor / Inactive Recognized Devel
Jun 10, 2014
10,138
29,146
0
Coding City
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)
 

Anthonomy

Member
Feb 5, 2012
35
4
0
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)

Could you do the same modification for the hero2ltekor variants? Thanks! :)
 

shah22

Senior Member
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)

So this is was the reason on oreo that after flashing magisk in twrp and rebooting, twrp won't see /data ?

Sent from my S7 Edge using XDA Labs
 

Andi46

Senior Member
Feb 7, 2016
238
131
0
Vechta
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)

THX a lot for sharing the files and info :good:
Now FULL BACKUPS are no problem anymore :D
 

Ubimo

Senior Member
Dec 22, 2011
1,416
642
133
Restoring a nougat rom is not booting with the new modified TWRP. How can I go back to a nougat rom? I tried an oreo rom but want to go back to nougat. Older TWRP does not mount data.
 

Pat750

Senior Member
Sep 12, 2016
588
256
73
Restoring a nougat rom is not booting with the new modified TWRP. How can I go back to a nougat rom? I tried an oreo rom but want to go back to nougat. Older TWRP does not mount data.
I'm not sure, but I would format data with new TWRP, then flash older TWRP and reboot recovery, then check if data can be mounted.
This is only a suggestion...
 
  • Like
Reactions: Andi46 and Ubimo

Ubimo

Senior Member
Dec 22, 2011
1,416
642
133
I'm not sure, but I would format data with new TWRP, then flash older TWRP and reboot recovery, then check if data can be mounted.
This is only a suggestion...
Thank you, thank you, thank you, that did the trick. :good::victory:
I did try several different combinations of BLs and other TWRPs but I would've never guessed that formatting data with modified TWRP and the flashing "old" TWRP would work. :confused:
 
  • Like
Reactions: Pat750

savvy1968

Senior Member
Jul 18, 2014
1,665
786
0
Halifax
Cheers bud

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)

Its been annoying when flashing getting data cant be mounted..Thanks:good:
 

mrsmtt

Senior Member
Mar 8, 2009
341
158
0
Hi everyone! Just to be sure, even with Tkkg1994's TWRP version recv error is still there right? Because I'm facing it right after flashing Superman v3
 

adel alsayed

Senior Member
Dec 7, 2014
457
89
0
Egypt
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)
Question
In TWRP V2.X.X in old device like s4 note 3 thar is option when i do full wipe thin restart recovery the twrp asking install root access .. But in v 3.x.x no more this option
Q. can you make v3.x. have that option it's ( include ) it in helpful to get root without searching for root zip file
 

Top Liked Posts

  • There are no posts matching your filters.
  • 202
    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.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone