[Recovery][Exynos] Official TWRP for Galaxy S7 (herolte)
- Thread starter Ivan_Meler
- Start date
Hi evrybody, Hi @Ivan_Meler
whats about that mess with TWRP?
Today I wanted to do the upgrade to LOS 20.1, but now I wonder not to do and better stay with LOS 19.1...
Does TWRP work now to do the upgrade to LOS 20.1 without problems?
If so, please tell me, wich TWRP version should I use actually.
I have downloaded that ZIP you had u.m. postet, @Ivan_Meler - is that working?
Allways, day and night, thank you for your efforts and work, Ivan - and also thanks a lot to all others for your help and work here!
Greetings,
netra3441
whats about that mess with TWRP?
Today I wanted to do the upgrade to LOS 20.1, but now I wonder not to do and better stay with LOS 19.1...
Does TWRP work now to do the upgrade to LOS 20.1 without problems?
If so, please tell me, wich TWRP version should I use actually.
I have downloaded that ZIP you had u.m. postet, @Ivan_Meler - is that working?
Allways, day and night, thank you for your efforts and work, Ivan - and also thanks a lot to all others for your help and work here!
Greetings,
netra3441
Extract the zıp and flash the .img file through TWRP or the .tar file through Odin, heimdall etcHi evrybody, Hi @Ivan_Meler
whats about that mess with TWRP?
Today I wanted to do the upgrade to LOS 20.1, but now I wonder not to do and better stay with LOS 19.1...
Does TWRP work now to do the upgrade to LOS 20.1 without problems?
If so, please tell me, wich TWRP version should I use actually.
I have downloaded that ZIP you had u.m. postet, @Ivan_Meler - is that working?
Allways, day and night, thank you for your efforts and work, Ivan - and also thanks a lot to all others for your help and work here!
Greetings,
netra3441
Sorry, but this was not my question. Please read the question, before your answer. Thank you.
TWRP works perfectly Fine if you are using always the latest Version. BUT The official website currently has issues which ivan told before. Thats why he posted here the zıp file. The files inside the zıp works perfect. Maybe you should read a few pages back before posting at all.
Hi I have flashed the stock rom because of a boot loop.
I want to install twrp and then install your android 12
I want to wipe stock rom and I dont need a backup.
Do I still need that dm-verity can I just swipe right to allow system modifications and wipe data system etc and then install new rom ?
in that case you dont need dm-verity, you will however have to format data (not just wipe, there is a difference in two) before installing a new rom for the first time
The attachment is in .zip format...what do I need to do to/with it so that Odin can flash it to the phone?
tnx for fix 3.7.0 master meler..i thought at first my device was broken but it was a twrp team fault.
@Ivan_Meler thanks a lot ! I was struggling for a bit while with the official release and couldn't get it installed
So I flashed TWRP in 2020 and it worked fine. I downgraded recently and was trying to flash it earlier when I got this log:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 46 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I flashed "twrp-3.7.0_9-0-herolte.img.tar" in the AP tab of Odin3 v3.14 and had auto reboot disabled, so I'm not quite sure what the problem was? unless I'm being dumb here does anyone know why it didn't work this time?
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 46 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I flashed "twrp-3.7.0_9-0-herolte.img.tar" in the AP tab of Odin3 v3.14 and had auto reboot disabled, so I'm not quite sure what the problem was? unless I'm being dumb here does anyone know why it didn't work this time?
For me the search is messed up so i can't point you to the right post. But there is a problem with the file size for the S7 with latest twrp. Flash a older one or search the one posted by Ivan_Meler here or in the LOS thread.
cool, Thanks. How do I flash it though? It doesn't get detected on the "AP" tab in Odin3 as a recovery.img
Just to summarize (with Samsung Galaxy S7 SM-930F) :
the current version of twrp was 3.6.0_9-0.
With the file twrp_3.7.zip provided by Ivan_Meler on page 83.
flash twrp-3.6.2_9-0-herolte.img.tar through ODIN
reboot recovery
flash recovery_herolte.img through TWRP
Done.
The first time, it didn't work with the file recovery_hero2lte.img.
The device rebooted well in recovery but the screen is weirdly yellow, TWRP is inactive, no buttons work anymore.
I had to come back in download mode (adb reboot download), reflash 3.6.2_9-0 version, and start again with the recovery_herolte.img file.
twrp 3.7.0_9-0 is installed and functional.
Thx
edit: clarity
the current version of twrp was 3.6.0_9-0.
With the file twrp_3.7.zip provided by Ivan_Meler on page 83.
flash twrp-3.6.2_9-0-herolte.img.tar through ODIN
reboot recovery
flash recovery_herolte.img through TWRP
Done.
The first time, it didn't work with the file recovery_hero2lte.img.
The device rebooted well in recovery but the screen is weirdly yellow, TWRP is inactive, no buttons work anymore.
I had to come back in download mode (adb reboot download), reflash 3.6.2_9-0 version, and start again with the recovery_herolte.img file.
twrp 3.7.0_9-0 is installed and functional.
Thx
edit: clarity
Last edited:
Are any of you using At&t in the united states? What firmware do you use for service?
G930FXXS7ESL6_G930FOJV7ESL8_XSG is the firmware I flashed last because the screen was going black and I just grabbed one to try. Well now on android 12 and 13 my sim card wont work it just gives busy signal and hangs up on everything. Thats the only thing I can think of. If you could even suggest one that might work that would be fine to. Its a junk phone for the most part. I like tweaking though and I would like the sim card to work again like it used to.
G930FXXS7ESL6_G930FOJV7ESL8_XSG is the firmware I flashed last because the screen was going black and I just grabbed one to try. Well now on android 12 and 13 my sim card wont work it just gives busy signal and hangs up on everything. Thats the only thing I can think of. If you could even suggest one that might work that would be fine to. Its a junk phone for the most part. I like tweaking though and I would like the sim card to work again like it used to.
The US has different bands compared to Europe. Thats because probally why the s7 with exynos not working on US networks. Normally US version are using Snapdragom processors
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
111I also missed the whole 3.7 discussion, or at least the part that the TWRP version of the img file didn't work as well.
I tried to install the img file from the TWRP app, now I get "could not do normal boot. Invalid kernel length" when trying to boot (normal and recovery) and no device is detected anymore when booting in download mode...
Reinstalling drivers has no effect.
Guess it's over and done? I wil try to drain the phones battery and try to boot to download mode once more.
Any suggestions?
edit:
Drained battery, connected phone to usb while holding vol dn + home +power. Phone went to download mode but died after 1 second. Phone doesn't charge anymore...
another edit:
It seems that my phone blew a softfuse on my laptops usb port. Any other device I tried to plug in wasn't detected. Disconnected my laptops battery for a few seconds, rebooted and I'm happy to say that where back in business! -
170Team 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.
