[Recovery][Exynos] Official TWRP for Galaxy S7 edge (hero2lte)
- Thread starter jcadduono
- Start date
Hello
I was on TWRP 3.2.3-0, modified by TKKG1994.
I just flashed TWRP 3.3.1-0 and tried to make a backup of all partitions. There is an error saying "unable to locate '/preload' partition for backup calculation"
Is this a problem?
How can I solve this?
I was on TWRP 3.2.3-0, modified by TKKG1994.
I just flashed TWRP 3.3.1-0 and tried to make a backup of all partitions. There is an error saying "unable to locate '/preload' partition for backup calculation"
Is this a problem?
How can I solve this?
Did you end up fixing it or is it bricked? I'm contemplating trying this, but the last handful of messages on this thread and the lack of responses tells me to steer clear.
Edit: Went ahead with it and had zero issues. YMMV.
Last edited:
I've tried unsuccessfully to flash TWRP to my factory open SM-G935F in preparation for flashing the lineage Android 10 rom.
I did post a question here https://forum.xda-developers.com/s7-edge/help/boot-problem-successful-twrp-flash-t4175699 but haven't had any replies.
Currently I can 'successfully' flash TWRP and boot into it. I have tried flashing SuperSU and the no-verity-opt but I get a 'Failed to mount '/data' (Invalid argument}' message plus a load of red lines before the flash starts & on reboot I get taken to a 'Verification failed' screen saying 'Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data'.
Download mode before reflashing stock rom reads:
Odin Mode
Download Speed: Fast
Product Name: SM-G935F
Current Binary: Custom
System Status: Official
FRP Lock: Off
Secure Download: Enabled
Warranty Void: 1 (0x030c)
SWREV: B:8 K:6 S:7
Fortunately, I've been able to reflash the stock rom via Odin each time (now done 3 times) and restored the phone to working with all data.
Is there a way of sorting the verification without a reset as I want to make a NAND backup 1st and if not will resetting sort out the verification issue?
Thanks.
I did post a question here https://forum.xda-developers.com/s7-edge/help/boot-problem-successful-twrp-flash-t4175699 but haven't had any replies.
Currently I can 'successfully' flash TWRP and boot into it. I have tried flashing SuperSU and the no-verity-opt but I get a 'Failed to mount '/data' (Invalid argument}' message plus a load of red lines before the flash starts & on reboot I get taken to a 'Verification failed' screen saying 'Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data'.
Download mode before reflashing stock rom reads:
Odin Mode
Download Speed: Fast
Product Name: SM-G935F
Current Binary: Custom
System Status: Official
FRP Lock: Off
Secure Download: Enabled
Warranty Void: 1 (0x030c)
SWREV: B:8 K:6 S:7
Fortunately, I've been able to reflash the stock rom via Odin each time (now done 3 times) and restored the phone to working with all data.
Is there a way of sorting the verification without a reset as I want to make a NAND backup 1st and if not will resetting sort out the verification issue?
Thanks.
Last edited:
Pls follow the respective rom thread for exact steps. Make sure you're following all steps correctly. Also make sure that OEM unlock is enabled in first place.
In short :
Install twrp in odin and boot directly into it from download mode without booting into phone>don't allow for system modification when asked in twrp and tick dont ask again > format data in wipe options and type yes > without rebooting flash magisk and then reboot (thats a standard systemless root procedure)
When flashing a custom rom you generally flash the respective rom zip instead of magisk and follow any additional/special mentioned steps in your respective rom thread. Again, pls read carefully everything before messing with your phone. Good Luck
Sent from my hero2lte using XDA Labs
Hello, I flashed the newest TWRP 3.4.0, and seems like whenever I boot into a freshly installed rom I can't mount anything in recovery mode anymore after that and it would require me to reformat again in order to mount any storage. May I know if there is something I can do to fix this?
Yes. Because for those of us who are trying to do our bit for the environment and try not to be materialistic and so keep our phones for as long as possible, these "how-to"s are vital reminders of how to do things should we need to revert, maybe after a rebuild or something goes very wrong.
Found some old S7 edge in a drawer. Going to root it.
Link for recovery doesn't work.
Latest recovery for S7 edge exynos can be found here : https://twrp.me/samsung/samsunggalaxys7edge.html
Also link for samsung usb drivers redirects to galaxy watch stuff ^^
So, it didn't work with twrp 3.5 somehow but worked with 3.4.
Link for recovery doesn't work.
Latest recovery for S7 edge exynos can be found here : https://twrp.me/samsung/samsunggalaxys7edge.html
Also link for samsung usb drivers redirects to galaxy watch stuff ^^
So, it didn't work with twrp 3.5 somehow but worked with 3.4.
Last edited:
I got that too but it was after flashing supersu/customrom/gapps.
But if I want to wipe data, it tells that it's failing at mounting data too.
edit : So, in the recovery, try to format data. It worked for me I don't have the error message about data anymore
Last edited:
Help!
My twrp has all of these new files and I cant flash anything unless it's right after formatting. It all comes back right after boot back into recovery and says I dont have any space to flash anything else.
I'm back in stock rom now no root.
twrp 3.5, odin 3.14, g935w8
Any way to fix this?
My twrp has all of these new files and I cant flash anything unless it's right after formatting. It all comes back right after boot back into recovery and says I dont have any space to flash anything else.
I'm back in stock rom now no root.
twrp 3.5, odin 3.14, g935w8
Any way to fix this?
Hi I am having the same problem. I am using TWRP 3.5.1_9.0 and have installed lineage 17.1. Everything is fine but when I encrypt the phone and boot into recovery TWRP is not able to mount the encrypted data partition. This was not an issue for me with older TWRP versions. Did you by chance find a solution to this problem?
I looked on twrp and I think there is problem with encryption because in fstab there is "encryptable=footer" but in lineageos there is "encryptable=/dev/block/platform/155a0000.ufs/by-name/TOMBSTONES". So lineageos is getting crypto footer from different location.
Hey guys, is this still the most up-to-date resource for OS 8.0 and S7 Edge SM-G935L (hero2lgelgt) ??
Or somewhere else better?
And is there a way around wiping device to unlock bootloader? I've picked up 3 of these devices.
Thanks
Or somewhere else better?
And is there a way around wiping device to unlock bootloader? I've picked up 3 of these devices.
Thanks
I use the one from https://eu.dl.twrp.me/hero2lte/. That seems to be official and up-to-date, and works with encryption.Hey guys, is this still the most up-to-date resource for OS 8.0 and S7 Edge SM-G935L (hero2lgelgt) ??
Or somewhere else better?
And is there a way around wiping device to unlock bootloader? I've picked up 3 of these devices.
Thanks
I have to correct myself. Encrypted partitions cannot bei accessed. Everything else works.
3.7.0 issues have been fixed but they are pending rebuild on twrp servers, in the meantime you can find 3.7.0 builds in attachment
Official builds have patches merged and are working again
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
203Team 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:
- 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 hero2lte.
- 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 to [Volume Up] 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 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
- 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_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-0867Hey 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)39Reserved
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.19Just 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. - In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
