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

Search This thread

rroyy

Senior Member
Flashed this version yesterday and i couldn't see internal storage.

Please tell me how do I fix this error?

Updater process ended with ERROR:1
Error installing zip file '/external_sd/Flash Files/no-verity-opt-encrypt-3.1.zip'

Updating partition details...
...done

Hi,
Does this TWRP work on an SM-G935F under Oreo G935FXXS4ESC5?

Thank you in advance
Fred

Unofficial TWRP Upstream for hero2lte
 
  • Like
Reactions: darksx

darksx

Senior Member
Dec 19, 2014
237
87
  • Like
Reactions: Saleen NS and rroyy

Misterjunky

Senior Member
Jan 18, 2011
9,455
6,717
Bakersfield, California
Android Wear
re: TWRP 3.3.0.0 update

Flashed this version yesterday and i couldn't see internal storage.

I had the same problem, After flashing TWRP 3.3.0.0 I could not mount DATA and the only way to be able to mount data was to FORMAT DATA (not wipe) but that deletes the internal SD Card and unless you have a twrp nandroid backup you will need to re-flash the zip file rom OR go into download mode and Odin flash the official stock S7 Edge firmware.

This problem never happened to me with any of the previous twrp updates.

Good luck, have a great day!
 
Last edited:
  • Like
Reactions: cavinrocks

Ubimo

Senior Member
Dec 22, 2011
1,469
755
There has to be some difference since:
recovery_hero2lte-160419.img is 44.393kb
twrp-3.3.0-1-hero2lte.img is 44.377kb
 

rroyy

Senior Member
I had the same problem, After flashing TWRP 3.3.0.0 I could not mount DATA and the only way to be able to mount data was to FORMAT DATA (not wipe) but that deletes the internal SD Card and unless you have a twrp nandroid backup you will need to re-flash the zip file rom OR go into download mode and Odin flash the official stock S7 Edge firmware.

This problem never happened to me with any of the previous twrp updates.

Good luck, have a great day!

I see there are now two "new" TWRPs.
Which one is "better"? What's the difference?
Ivans TWRP or
turbolukex5s TWRP?

Apparently none since both are based on the same source

Sent from my S7 Edge using XDA Labs

There has to be some difference since:
recovery_hero2lte-160419.img is 44.393kb
twrp-3.3.0-1-hero2lte.img is 44.377kb

I'm not having mount problem with turbolukex5s TWRP
 
I had the same problem, After flashing TWRP 3.3.0.0 I could not mount DATA and the only way to be able to mount data was to FORMAT DATA (not wipe) but that deletes the internal SD Card and unless you have a twrp nandroid backup you will need to re-flash the zip file rom OR go into download mode and Odin flash the official stock S7 Edge firmware.

This problem never happened to me with any of the previous twrp updates.

Good luck, have a great day!

Same Problem, the turboluke Version fixed it.
 

b4ron4711

New member
May 28, 2019
1
0
Hi. I need help. I have a big problem, i dont know what can i do now. I did Step 1 till Step 9 and then i canceled :( :( and now it dont boot

I hate me for this, pls help
 

Marsu42

Senior Member
Jul 13, 2008
140
50
[*]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

[*]If you want to be rooted withth 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.

After browsing through a lot (but not all) of the thousands of posts poor /me is still completely confused by step 10 :-o

This is kind of frustrating, since I used to do all this stuff on a Galaxy SII :-\

- I'd like to get twrp working, and then flash Lineage. Does this mean I "only want a bootable system partition"? Or should I simply flash Lineage right after twrp works, no matter this mysterious verity?

- If I want a rooted Samsung firmware with SuperSU, do I need to do the 2nd step "no-verity-opt-encrypt.zip", too?

- And what is this about firmware A/Bxxx - is this what "G935FXXS5ESF1" is on my new phone? Does this mean that no-verity-opt-encrypt.zip won't work anyway for me?

Thanks for any help, I'm puzzled how people manage to understand this step :-\
 

syednawaz

Senior Member
Sep 30, 2015
757
248
Samsung Galaxy S8
After browsing through a lot (but not all) of the thousands of posts poor /me is still completely confused by step 10 :-o

This is kind of frustrating, since I used to do all this stuff on a Galaxy SII :-\

- I'd like to get twrp working, and then flash Lineage. Does this mean I "only want a bootable system partition"? Or should I simply flash Lineage right after twrp works, no matter this mysterious verity?

- If I want a rooted Samsung firmware with SuperSU, do I need to do the 2nd step "no-verity-opt-encrypt.zip", too?

- And what is this about firmware A/Bxxx - is this what "G935FXXS5ESF1" is on my new phone? Does this mean that no-verity-opt-encrypt.zip won't work anyway for me?

Thanks for any help, I'm puzzled how people manage to understand this step :-\

B4 anything. Backup your data. Bec i also lost my internal storage.
Goto developer settings and enable frp unlock or just delete all accounts from your phone specifically google ones.

Then goto download mode and connect to pc.
On pc use odin i think it was 3.13. Select latest twrp and flash it.
When you boot twrp, then goto wipe and click format data bec your internal memory is 0. So it will fix that. And then goto install and flash any los or custom rom.

But rooting stock rom, i gave it a try but was failed. And there was no point for going back to bloated stock when you have lite custom roms.

And samsung pass wont work if you tripped the knox. I liked that feature.
Also YouTube is full of flashing twrp or roms video. You can look at them too. But yes its scary to flash.
 
  • Like
Reactions: Marsu42

Marsu42

Senior Member
Jul 13, 2008
140
50
Then goto download mode and connect to pc.
On pc use odin i think it was 3.13. Select latest twrp and flash it.
When you boot twrp, then goto wipe and click format data bec your internal memory is 0. So it will fix that. And then goto install and flash any los or custom rom.

Thanks!

And samsung pass wont work if you tripped the knox. I liked that feature.
Also YouTube is full of flashing twrp or roms video. You can look at them too. But yes its scary to flash.

There's your problem: It's so full of videos it's hard to separate them non-S7 stuff from what I'd need. Back in the good ol' days, there was one video for my SII, and one for my Amazon Fire :-o

Edit: Everything worked fine, however it took me several attempts to get into twrp because the device is so darn fast - if you don't press the keys immediately after Odin reboots, you'll end up in Samsung again.
 
Last edited:

shah22

Senior Member
Thanks!



There's your problem: It's so full of videos it's hard to separate them non-S7 stuff from what I'd need. Back in the good ol' days, there was one video for my SII, and one for my Amazon Fire :-o

What you want to do exactly ?

Sent from my S7 Edge using XDA Labs

---------- Post added at 01:32 PM ---------- Previous post was at 12:37 PM ----------

After browsing through a lot (but not all) of the thousands of posts poor /me is still completely confused by step 10 :-o

This is kind of frustrating, since I used to do all this stuff on a Galaxy SII :-\

- I'd like to get twrp working, and then flash Lineage. Does this mean I "only want a bootable system partition"? Or should I simply flash Lineage right after twrp works, no matter this mysterious verity?

- If I want a rooted Samsung firmware with SuperSU, do I need to do the 2nd step "no-verity-opt-encrypt.zip", too?

- And what is this about firmware A/Bxxx - is this what "G935FXXS5ESF1" is on my new phone? Does this mean that no-verity-opt-encrypt.zip won't work anyway for me?

Thanks for any help, I'm puzzled how people manage to understand this step :-\

As said the first thing vital is to enable oem unlock and usb debugging in developer options. Plus back up all your data. Download latest stock rom for your country and keep it handy if anything goes wrong and you need to start over. Only after doing these proceed forwards. A tip is to remove all accounts present in the device before proceeding. But enabling oem unlock disables frp lock. So you will be still good to go.

The first thing you need to worry about is choosing the absolute right rom/recovery/zips for your phone model. Then the first thing after getting root access is to Copy all your rom, specifically EFS folder or make a backup of it in a safe location..

Download latest odin, then flash latest twrp recovery, by selecting it in AP.

Now coming to verity thing, that sucks really, happens on roms (bootloaders) which are enabled for checking rom integrity, it is used for checking stock samsung rom for unauthorized access (root) if it detects it won't let the rom boot.

I honestly don't think anyone needs non verity on lineage roms, but yeah you may as do need them well, because your bootloader is still samsung, and it won't hurt to flash the no verity zip alongside lineage...? but you WILL need to flash no verity if you plan on rooting your stock rom (unless you go systemless route), as i heard most custom roms (lineage+samsung based) have verity disabled in their kernels? So you need to see your required rom thread for more info.

Coming to the verity zips, there are two types; no verity opt encrypt and no verity forced encrypt, the former is used for disabling dm verity only but later is used to disable forced encryption + dm verity in roms.

Now coming to root, there are various root methods, from creating your own cf auto root package, super SU to magisk and systemless roots.

On android 8.0 , it was difficult to achieve root/stay rooted, due to forced encryption in the rom twrp would not display data after rebooting, also magisk had some problems (don't know if they are sorted out). Also there is a modified twrp version by tkkg1994 and it was reported to work correctly, you can search it on forums. (I don't know if latest twrp version solves these issues). I guess latest twrp version coupled with no verity force encrypt should work ..

You can also try to flash both types of no verity zips with latest twrp to see if it is detecting everything correctly after rebooting. If not try the modified twrp by tkkg1994. All official links on the forums.

Also that a/b thing you talked about, that a/b partition doesn't applies to older devices like s7 series par my knowledge.

Systemless root is known to not trigger dm verity and you may not need dm verity zips if you go this route. For info on this search on forums, in short select twrp in read only mode (don't do swipe for modifications) and install magisk as systemless root. Systemless SuperSU root can also be used and there is a systemless root option as well when creating cf auto root package.

In the end a tip when rooting on stock rom, when booting in twrp for first time select wipe>format data>swipe/yes, do not select advanced wipe options or select anything more then data at that moment, you may end up loosing your rom ! (plus efs/imei if you are unlucky)

For flashing custon roms/zips/kernels, process is different and you may need to go in advanced options.. follow your required custom software thread for more info on this.. Good luck !

Links :

Odin

OfficialTwrp

No verity zips :

NoVerityOptEncrypt
NoVerityForcedEncrypt

Modified twrp by tkkg1994 : Link

SystemlessRoot

MagiskOfficial

SuperSU

CFautoroot note : version 5 bootloader firmware is not uploaded atm..

All credits to their respective contributors.


Sent from my S7 Edge using XDA Labs
 
Last edited:

Irtiza123

Member
Jul 19, 2019
6
0
Important

Hello! I have a rooted device and i want to install twrp if i i swipe to enable system modifications will i not be able to boot up or would i cuz i have a rooted device?
 

Irtiza123

Member
Jul 19, 2019
6
0
I just wanna know that since i have a rooted device will swiping to allow system modifications be harmful to me or not? I rooted with supersu and want to switch to magisk. Please give me an answer quickly
 

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.