[Recovery][Exynos] Official TWRP for Galaxy S7 (herolte)
- Thread starter Ivan_Meler
- Start date
is it possible to upgrade TWRP from Within TWRP or only by ODIN ?
I have installed TWRP 3.3.1.0 and want to upgrade to the newest 3.5.2_9_0
because i want to make a FW upgrade from TeamExyKings (Android8) to Lineage17.1 (Android10) and dont know, if i can do this with the old TWRP or if a should upgrade TWRP first.
I have installed TWRP 3.3.1.0 and want to upgrade to the newest 3.5.2_9_0
because i want to make a FW upgrade from TeamExyKings (Android8) to Lineage17.1 (Android10) and dont know, if i can do this with the old TWRP or if a should upgrade TWRP first.
Last edited:
Hi, whenever I boot into twrp it says storage is 0 and I have no drives. To install a rom I must always format data and then my storage returns. I can't flash magisk etc after installing a rom because as soon as I boot up it says storage is 0 and there's no system to install upon. Any ideas?
To install ROms I must use my SD card.
To install ROms I must use my SD card.
A past update of LOS 17.1 (unofficial) on my herolte appears to have taken away my TWRP -- and also removed rooting. And added problem is that it is not possible to connect to the phone through the PC (I think that this is an intermittent problem with herolte) so I am not sure how to install a new version of LOS or root the phone. What can I do to install recovery and to root the phone.
The following two articles helped me out:
How to Replace LineageOS Recovery with TWRP
TWRP is the most popular custom recovery, but the LineageOS bring its own custom recovery when installing the custom ROM. So here we are on how to
rootmygalaxy.net
How to Update LineageOS and Regain Root Access With Magisk - KrispiTech
In this article, we will look at how you can install the latest LineageOS OTA update and regain root access again, using LOS Recovery.
krispitech.com
I decided to forego TWRP for now, so the first article was unnecessary but explained to me where TWRP went, I guess.
Hello,
I have an SM-g930F in a boot loop and I need to save the data that I have on it.
I'm trying to install TWRP through Odin, but when I try to do it, the Blocked by FAP message appears. (On the S7 screen)
I don't have access to developer options, because the phone is in a boot loop, I can only enter in Download Mode (Odin Mode), Recovery doesn't work either.
I tried to flash the latest firmware with ODIN but it gave me FAIL with hidden.img
After that, the mobile only started in Emergency recovery and in Download Mode (Odin Mode). Also after this, the phone was discharged and the battery stopped charging. I can only use it if it is connected to the wall or via USB.
I don't know what to do, any help will be appreciated
Here more info:
https://forum.xda-developers.com/t/cant-install-twrp-blocked-by-fap-in-a-galaxy-s7.4483575/
Thank you very much
I have an SM-g930F in a boot loop and I need to save the data that I have on it.
I'm trying to install TWRP through Odin, but when I try to do it, the Blocked by FAP message appears. (On the S7 screen)
I don't have access to developer options, because the phone is in a boot loop, I can only enter in Download Mode (Odin Mode), Recovery doesn't work either.
I tried to flash the latest firmware with ODIN but it gave me FAIL with hidden.img
After that, the mobile only started in Emergency recovery and in Download Mode (Odin Mode). Also after this, the phone was discharged and the battery stopped charging. I can only use it if it is connected to the wall or via USB.
I don't know what to do, any help will be appreciated
Here more info:
https://forum.xda-developers.com/t/cant-install-twrp-blocked-by-fap-in-a-galaxy-s7.4483575/
Thank you very much
blazethelight
Senior Member
There is no known way without OEM-Unlock active, usb-debugging on etc.
Always first activate this options, than create a backup (Samsung Kies) and than play with your phone (like flashing).
No backup = no fun!
If you want revert to stock with a soft bricked device:
01. Download SamFirm (newest version) if you want go back to stock: https://samfirmtool.com/
02. Extract CSC Archiv for PIT File (repartition).
03. Start Odin and select all files of downloaded firmware.
04. If you have NAND problems, tick option NAND erase. If not only check option PIT file and repartition (other options keeps to standard).
04. Check the option for PIT file and select extracted PIT file.
04. Flash firmware and wait for finish.
Good luck and hopefully enjoy your phone again.
No warranty!
Last edited:
blazethelight
Senior Member
Start reading first posts to install twrp again.
It's firmware related bugs and not really twrp related.
Some AOSP roms doesn't support twrp and only supports AOSP Recovery.
Read the Rom threads first for instructions.
blazethelight
Senior Member
Yeah. This is also true for my S7 (first stock and than after flash twrp, I must install decypter zip and format data for install a new custom rom like Alexanders Dev Rom.).
I don't know, why this appear (twrp logs always before: can't mount data).
Maybe any dev of this twrp thread (@Ivan_Meler) knows more why this appear?
PS. Into Alexander Dev Base thread, he documented the message for a success encrypted device. Maybe it's here the same?
Last edited:
blazethelight
Senior Member
Read your rom thread if decryption is supported. And if yes, ask there the dev to activate it.
blazethelight
Senior Member
You know, that decryption a Samsung phone need Samsung (closed) sources?!
Some official AOSP Roms able to decrypt and encrypt storage with recovery, but it's also Rom related.
If you want this features, search a Rom for this or go back to stock.
Unofficial roms mostly can't de - or encrypt storage.
I am also not an developer or responsible for this thread or twrp, but iam wondering, why you ask this question into this twrp recovery thread...?
blazethelight
Senior Member
Really? That's all of informations you gave and now you ask indirect for help?
Sorry, that's really disappointing for an xda forum member!
If you need a real life example how to ask for help, look at post number @#1628 by @Logeate .
Last edited:
Hello, I too have a SM-G930F stuck at the "teamwin" loading screen, and also really wanted to keep my data. However, while I'm certain I enabled USB debugging, I am uncertain if I remembered to also turn on OEM-Unlock.
I was wondering if trying to reflash the same exact version of twrp would possibly leave me in a worse spot than I am right now considering OEM-Unlock might or might not be enabled. Would failing to flash cause problems or just... do nothing?
Additional information:
- I was able to access recovery multiple times in the past, I did not reflash it recently, just wanted to access recovery to do a routine backup.
- The device is rooted
- Currently using lineage-18.1-20220908-UNOFFICIAL-herolte by Ivan_Meler
- TWRP version is twrp-3.6.2_9-0-herolte
- I accessed recovery by tapping reboot (not shutdown) in the OS and then holding down the key combo (home + volume up)
- The device wont turn off. Forcing power off through key combo (vol down + power) just reboots it to recovery instead.
My current theory is that trying to access recovery by rebooting together with the phone being plugged into a PC somehow caused the problem.
Thank you a lot for any help
Last edited:
Hi. Just tried to upgrade from 3.6.2 to 3.7.0 but get:
Size of image is larger than target device
As far as I know the device has the default PIT, plus I notice the image is larger than previous images.
Has anyone else been able to upgrade?
Thanks.
Size of image is larger than target device
As far as I know the device has the default PIT, plus I notice the image is larger than previous images.
Has anyone else been able to upgrade?
Thanks.
+1 installation failed with "Size of image is larger than target device"
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.
New posts
-
Cannot find OEM Unlock for Samsung galaxy s21 + 5g- Latest: SubwayChamp
-
-
