[Recovery][Exynos] Official TWRP for Galaxy S7 (herolte)
- Thread starter jcadduono
- Start date
ripee
Recognized Developer / Recognized Contributor
He hasn't been maintaining the official twrp for a long time. Build 3.4 is from ivan_meler's updated source.
Oh, okay @ripee, thank you for this information!
So, @origold, I don't know if anybody can answer your question. Eventually you can't unlock OEM cause it is still unlocked from your first try 6 months ago, although you installed stockROM again in the meantime?!
Maybe you should contact @Ivan_Meler before flashing again?!
So, @origold, I don't know if anybody can answer your question. Eventually you can't unlock OEM cause it is still unlocked from your first try 6 months ago, although you installed stockROM again in the meantime?!
Maybe you should contact @Ivan_Meler before flashing again?!
Last edited:
Six months ago I unlocked oem with no problem and rooted my phone. When I tried to install custom rom I bricked my phone and didn't touched it since. And now when i flashed the original firmware I can't unlock the oem its so weird because I still cant use Samsung health and other apps.
Hello, cannot find an answer in the threads so give it a try here:
I want to install TWRP on S7 flat and keep stock rom latest version 8.0.0, no encryption enabled. Aim is to make nandroid backup of current data aftwerwards (I know this will trigger Knox).
1. Can I install TWRP without wipe data? (so I can do a nandroid backup of current data aftwerwards?).
2. do I have to install 'no-verity-opt-encrypt-6.1.zip' if I do not have encryption?
I want to install TWRP on S7 flat and keep stock rom latest version 8.0.0, no encryption enabled. Aim is to make nandroid backup of current data aftwerwards (I know this will trigger Knox).
1. Can I install TWRP without wipe data? (so I can do a nandroid backup of current data aftwerwards?).
2. do I have to install 'no-verity-opt-encrypt-6.1.zip' if I do not have encryption?
Last edited:
Stock ROM latest version is Android 8, not 9.
1. AFAIK, as soon as you flash a custom (unsigned) boot or recovery image, the phone will wipe the user data, and to be able to mount (access) /data in TWRP, you need to format it anyway.
2. Yes, or you need to flash Magisk or a custom ROM.
The best solution would be to flash ALEXNDR ROM, it's based on stock with a few tweaks (notably everything that is related to Knox is properly deleted).
I'm running Android 10 Lineage at the moment, but is there a problem downgrading to an earlier version of android? Anytime I try to flash another ROM (e.g. Android 7 based) I get an 'error 7' message in TWRP. Is this a fault with TWRP? I have the latest version installed.
Anyone else had this problem and found a way around it?
Anyone else had this problem and found a way around it?
Attachments
Last edited:
Try moving the .zip file to internal storage it may fix this.I'm running Android 10 Lineage at the moment, but is there a problem downgrading to an earlier version of android? Anytime I try to flash another ROM (e.g. Android 7 based) I get an 'error 7' message in TWRP. Is this a fault with TWRP? I have the latest version installed.
Anyone else had this problem and found a way around it?
I believe your issue may be the Samsung prohibition against installing a lower version of the bootloader over a higher (more recent) versionI'm running Android 10 Lineage at the moment, but is there a problem downgrading to an earlier version of android? Anytime I try to flash another ROM (e.g. Android 7 based) I get an 'error 7' message in TWRP. Is this a fault with TWRP? I have the latest version installed.
Anyone else had this problem and found a way around it?
I thought it must be something like that!
So.. presumably I can use Odin to downgrade using Android 7 stock firmware? If yes then flashing an Android 7 ROM should be no problem, am I right? ??
No, because the prohibition/enforcement is built into Odin.
I have read that you might be able to use TWRP to install a custom ROM with a lower/older bootloader, and then again use Odin to install a stock ROM. However, I have never done that, nor have I fully researched it.
So, seeing as I'm using an Android 10 ROM, does that mean it's likely I'm stuck using Android 10 with no way to use any ROMS based on earlier versions of Android?
What is the bootloader version in your phone, and what is the CSC?So, seeing as I'm using an Android 10 ROM, does that mean it's likely I'm stuck using Android 10 with no way to use any ROMS based on earlier versions of Android?
Forgive my ignorance, but I don't know what the CSC is! ? How do I check the CSC and the bootloader version? Will let you know as soon as I know! ??
Your bootloader version is "8" (the 9th digit), which is the most recent. Therefore you can install any build of Android Oreo that uses an "8" bootloader.
If you want the official Samsung version, download/install "Sanfirm" and then download the most recent version for EVR; verify the bootloader version after download; installation is via Odin.
If you want to use a debloated (unofficial, but close to stock) version, go to https://forum.xda-developers.com/galaxy-s7/development/rom-dqd2-devbase-v4-1-multi-csc-safe-t3592914. Installation of the Alexndr ROM is via TWRP.
Does anybody else here have problems like this when using encryption with the latest [STABLE] LineageOS 17.1 for Galaxy S7 build 16? Eventually it derives from a switch in LOS' SELinux from "permissive" to "enforcing"...!? Flashing "no-verity-opt-encrypt-6.1.zip" unfortunately won't help permanently.
@jcadduono
No, SELinux is not causing the issue! It's LOS' encryption as of October-version. Something must have been changed since a device does not show this problem as long as it is NOT encrypted. Hopefully there will be a solution in the near future.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
168Team Win Recovery Project 3.0.2-4
This is for the International SM-G930F/FD/X, Korean SM-G930K/L/S, and Canadian SM-G930W8 Exynos models only! Do not flash on S7 edge 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:
https://twrp.me/samsung/samsunggalaxys7.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:
- In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
- 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.
- Extract Odin_3.12.3.zip to your computer.
- Install Samsung Mobile Phone Drivers for Odin to find your device.
- Download a .tar image of TWRP for herolte.
- 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.
- Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
- Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap [Volume Down] to [Volume Up] (continuing to hold [Home] + [Power]) when the screen blanks.
If you don't see then TWRP boot splash try again from step 6.
- 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.
- 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.
- Go to [Reboot] -> [System].
- Wait 2-5 minutes for your device to finish setting itself up.
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 G930FXXU1APAW 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
- Samsung encryption is not supported yet in TWRP 3.0 (see: https://gerrit.omnirom.org/#/c/17308/)
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_herolte (android-6.0)
Device tree (Korea): https://github.com/TeamWin/android_device_samsung_heroltekor (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, Tool/Utility for the Samsung Galaxy S7
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 2019-01-16102Hey 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)41If you have a G930P, G930V, G930R, or G930A (aka the US Snapdragon models) your bootloader is locked. I will not be making TWRP for your device - it simply cannot happen. Sorry.
Update: G930T 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.223.3.0-1 from ivan's 8.1 sources
Changelog from 3.3.0-0:
Remove force quota and fix encryption on aosp
twrp-3.3.0-1-herolte.img
twrp-3.3.0-1-herolte.tar
twrp-3.3.0-1-hero2lte.img
twrp-3.3.0-1-hero2lte.tar
The official sources are getting old by now, so ivan rebuilt the herolte and hero2lte device trees. - In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
