[Recovery][Exynos] Official TWRP for Galaxy S7 (herolte)

Search This thread
By:
Advanced…
P

promeneur

Senior Member
Mar 31, 2014
131
5
@master373

Good news.
Finally, the battery reached 0 % then the phone switched off.
During the night, I charged the phone to 100 %.

This morning, I tried to start the phone. Success ! :) I found again the android stock 8.0 and all the data.

Before the phone switched off. I try this :
I linked my phone to the PC with a USB cable.
With the kde infocenter, I saw that the phone is well recognized as a USB device.
Perhaps there was something to try. But I don't know well the heimdal or adb command.

Can we make a soft reboot to download mode ?

Thanks
 
P

promeneur

Senior Member
Mar 31, 2014
131
5
@Ivan_Meler

in recovery mode i get android recovery mode not twrp.

Here is what i did.

In download mode, I flashed with your twrp page 83.

heimdall flash --RECOVERY recovery_herolte.img --no-reboot

heimdall reports

Uploading RECOVERY
100%
RECOVERY upload successful

at the phone screen, the progress bar was at 100 %

then

I pressed [Volume Down] + [Home] + [Power] to turn off the phone

then

I start the phone to check if android stock is there

then

I turn off the phone

then

I press [Volume Up] + [Home] + [Power] to switch to recovery mode

then

I get a message "no command"

then

I get the Android recovery mode

thanks
 
P

promeneur

Senior Member
Mar 31, 2014
131
5
I launch with success the phone in recovery mode.
But when I reboot with the option "system" then I get a boot loop !
 
P

promeneur

Senior Member
Mar 31, 2014
131
5
If I switch off the phone then I start the phone with the Power button, then by default it boots on recovery mode !

Something interesting :

If I wipe the cache I get red messages about data, storage, etc. partitions saying mounting partition fails.

Failed to mount /data (invalid argument)
Unable to recreate /data/media folder.
Updating partition details ...
Failed to mount /data (invalid argument)
...done
Unable to mount storage
Failed to mount /data (invalid argument)
Full SE linux support is present
Unable to mount /data/media/TWRP/.twrps
MTP enabled
Formating cache using mke2fs ...
Done
Updating partition details ...
Failed to mount /data (invalid argument)
...done
Unable to mount storage
 
M

master373

Senior Member
Feb 1, 2022
218
75
promeneur said:
And if I want only to replace the Android recovery ? it is not possible ?
Click to expand...
Click to collapse
Sure it is. Maybe you have to flash dm verity or something like this posted in OP. And than just format data and do factory reset with twrp. Otherwise simply flash stock based costum rom. Im not in stock rom since 4 years now so idont know how to stay completly stock with just twrp
 
Last edited:
N

Not_Rich

Senior Member
Aug 6, 2017
98
49
Samsung Galaxy S4 Mini
nVidia Shield Android TV (2017)
I installed stock because of a boot loop, I followed this guide to install twrp and no-verity without magisk, set the phone up installed a few apps, all good then made a backup in twrp.

I then installed Ivans Lineage 19 and 20 then backed up both. I can restore between 19 & 20 easily but when I restore stock I get an error extract tar fork error 255.

Using twrp 3.7.09

Any idea what's wrong.
 
Last edited:
N

Not_Rich

Senior Member
Aug 6, 2017
98
49
Samsung Galaxy S4 Mini
nVidia Shield Android TV (2017)
Not_Rich said:
I installed stock because of a boot loop, I followed this guide to install twrp and no-verity without magisk, set the phone up installed a few apps, all good then made a backup in twrp.

I then installed Ivans Lineage 19 and 20 then backed up both. I can restore between 19 & 20 easily but when I restore stock I get an error extract tar fork error 255.

Using twrp 3.7.09

Any idea what's wrong.
Click to expand...
Click to collapse
I installed the latest twrp and now the backup process gets stuck on a backup that previously worked, left it for 20 minutes and no change.

I didn't bother getting stock installed again, the solution for me is to flash Lineage and gapps then restore data from the backup that previously worked, once this is done reboot set everything up and make a new backup.
 
  • Like
Reactions: Durangic
walttheboss

walttheboss

Senior Member
Nov 1, 2010
671
244
52
Kunming
Hello All. In process of rebuilding two old g930f phones for my kids as audio players. I want LineageOS and root. I don't need any fancy features but do want wifi and bluetoorh. Can someone recommend the best LineageOS version. And is chainfireSU still the best root?
 
E

Ex novo

Senior Member
Apr 21, 2018
143
47
walttheboss said:
Hello All. In process of rebuilding two old g930f phones for my kids as audio players. I want LineageOS and root. I don't need any fancy features but do want wifi and bluetoorh. Can someone recommend the best LineageOS version. And is chainfireSU still the best root?
Click to expand...
Click to collapse

I'm on LineageOS 19 and it's fully stable with low battery consumption using NickGapps core and battery saver enabled in settings. Wifi and bluetooth are working. I'm not using LineageOS 20 because data encryption doesn't work in that version.
I recommend you install the 3 versions of LineageOS (18, 19 and 20) and test to see which one is best for you.
To root the device you must follow the instructions here:

Installation

The Magic Mask for Android
topjohnwu.github.io
On this device the simplest way to root is download the stable version of Magisk from here: https://github.com/topjohnwu/Magisk/releases/tag/v26.1
Rename "Magisk-v26.1.apk" to "Magisk-v26.1.zip" save on external sd card and flash with the recovery you installed on the device (TWRP or LineageOS recovery)
 
walttheboss

walttheboss

Senior Member
Nov 1, 2010
671
244
52
Kunming
Ex novo said:
I'm on LineageOS 19 and it's fully stable with low battery consumption using NickGapps core and battery saver enabled in settings. Wifi and bluetooth are working. I'm not using LineageOS 20 because data encryption doesn't work in that version.
I recommend you install the 3 versions of LineageOS (18, 19 and 20) and test to see which one is best for you.
To root the device you must follow the instructions here:

Installation

The Magic Mask for Android
topjohnwu.github.io
On this device the simplest way to root is download the stable version of Magisk from here: https://github.com/topjohnwu/Magisk/releases/tag/v26.1
Rename "Magisk-v26.1.apk" to "Magisk-v26.1.zip" save on external sd card and flash with the recovery you installed on the device (TWRP or LineageOS recovery)
Click to expand...
Click to collapse
Thank you very much. Exactly what I wanted. Have a great weekend.
 
You must log in or register to reply here.

Similar threads

yash92duster
  • Poll
[S7/S7 Edge][OneUI Pie][JetBlackUI][15-Jan-2020][v20] LightROM
Replies
2K
Views
2M
ali_m8j
ali_m8j
Ivan_Meler
LineageOS 15.1 (Android 8.1.0) for S7 herolte build 53 18.20.2020.
Replies
4K
Views
831K
E
Eklondh
F
[ROM][G930F/FD/W8/S/K/L][7.1.1] OFFICIAL LineageOS 14.1 for Galaxy S7
Replies
3K
Views
605K
Exodusnick
Exodusnick
Ivan_Meler
[STABLE] LineageOS 17.1 for Galaxy S7 build 44
Replies
2K
Views
569K
ScanX
ScanX
Ivan_Meler
LineageOS 16.0 for S7 build 30
Replies
2K
Views
677K
Exodusnick
Exodusnick

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 170
    Ivan_Meler
    Ivan_Meler
    Team 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:

    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 herolte.
      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 [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.
      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 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

    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-16
    View
    102
    Tkkg1994
    Tkkg1994
    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)
    View
    41
    Ivan_Meler
    Ivan_Meler
    If 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.
    View
    22
    ripee
    ripee
    3.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.
    View
    14
    jcadduono
    jcadduono
    I need someone to test 3.0.2-3 for me which should solve the BPH6 and APG8 bootloader issues, and maybe charging while off out of recovery, and possibly a few other bugs.

    Please join #twrp on irc.freenode.net.
    View

New posts