Team Win Recovery Project 3.0.2-1
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 S6 edge (6.0+) stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Flash a root such as SuperSU or phh-superuser. You can also flash no-verity-opt-encrypt.zip.
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/samsunggalaxys6edge.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 a link to Samsung's Mobile drivers page here:
https://idlekernel.com/flash-tools/
FULL STEPS FOR ROOTING YOUR DEVICE
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.10.7.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for your device variant.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] + [Power] 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 without touching any other options, then press [Start].
Hold [Volume Up] + [Home] + [Power] buttons near the end of the flash, and keep holding them until you are in recovery.
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 step 12 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.
Only if you want your internal storage or data partition to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
If you only want a bootable system partition or readable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
** If your internal storage is encrypted, you will need to use adb sideload instead.
Go to [Reboot] -> [System].
Wait up to 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-0 (twrp.me) - same as v3.0.2-1
v3.0.2-1 - New device tree and kernel, support added for Marshmallow, f2fs, and MTP.
v3.0.2-0 - See here for the changes.
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)
NTFS file system support (read, write)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3 (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_zerolte (android-6.0)
Kernel: https://github.com/jcadduono/nethunter_kernel_noblelte (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 S6 edge, Tool/Utility for the Samsung Galaxy S6 Edge
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/jcadduono/android_device_samsung_zerolte
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-05-27
Created 2016-04-08
Last Updated 2016-10-02
Builds are coming soon, just putting a thread up for a reference on the device page!
jcadduono said:
Builds are coming soon, just putting a thread up for a reference on the device page!
Click to expand...
Click to collapse
Sweet, stick a mention that G925W8 users flash T-Mobile variant plz. [emoji6] thanks for this! Now my friends can read.
Sent from my SM-G925W8 using XDA-Developers mobile app
christopherrrg said:
Sweet, stick a mention that G925W8 users flash T-Mobile variant plz. [emoji6] thanks for this! Now my friends can read.
Sent from my SM-G925W8 using XDA-Developers mobile app
Click to expand...
Click to collapse
there won't be a marshmallow G925W8 or G925T build until kernel sources are released. afaik neither of those devices have 6.0 officially yet.
they will still be using lollipop at 3.0.2-0 for now.
for others:
https://idlekernel.com/twrp/zerolte see 3.0.2-1, should be built soon on official, whenever someone confirms that everything is working ok
this includes:
adb shell
brightness slider
installing zips
formatting partitions (as ext4 and f2fs)
not crashing
backup & restore works for each partition
mtp
vibration
otg storage
whatever else you can think of checking
check on both L and M bootloaders, preferably quote my list with Y(working)/N(not working) in front of issues, and give recovery.log
I have successfully flashed the latest twrp. Though I had issues with the older one in backup restore area. Does the new do up backup and restore without error?
Nothing for SM-G925I ? zeroltedv
Ognjen123 said:
Nothing for SM-G925I ? zeroltedv
Click to expand...
Click to collapse
Brother I am using g925i only. Go to arter97 kernel page and download the recovery which he has modded for both and F and I variants.
jcadduono said:
there won't be a marshmallow G925W8 or G925T build until kernel sources are released. afaik neither of those devices have 6.0 officially yet.
they will still be using lollipop at 3.0.2-0 for now.
for others:
https://idlekernel.com/twrp/zerolte see 3.0.2-1, should be built soon on official, whenever someone confirms that everything is working ok
this includes:
adb shell
brightness slider
installing zips
formatting partitions (as ext4 and f2fs)
not crashing
backup & restore works for each partition
mtp
vibration
otg storage
whatever else you can think of checking
check on both L and M bootloaders, preferably quote my list with Y(working)/N(not working) in front of issues, and give recovery.log
Click to expand...
Click to collapse
G925W8 PC5 sources are up. Nothing for the 920W8 yet.
violin.siva said:
Brother I am using g925i only. Go to arter97 kernel page and download the recovery which he has modded for both and F and I variants.
Click to expand...
Click to collapse
Can you please pm the link ?
---------- Post added at 11:16 PM ---------- Previous post was at 11:06 PM ----------
Can the twrp-3.0.2-1-zerolte.tar.md5 be flashed on the g925i ?
Why aren't the link working?
G925f link?
Inviato dal mio SM-G925F utilizzando Tapatalk
Is the topic dead ? Anybody can tell me what recovery they are using on g925i 6.0.1 android ?
Ognjen123 said:
Is the topic dead ? Anybody can tell me what recovery they are using on g925i 6.0.1 android ?
Click to expand...
Click to collapse
Twrp 3.0.2 with arter97 kernel. Working flawlessly in my g925i.
This is making me crazy , is there any suport here ? Links not working , where from to dl the 3.0.2-1 ver for g925i ?
OEM Unlock ??
I can't find it in my Developper Menu. I have 6.0.1 !
Help please...
Anyone found a working link for the recovery file?
Questions about TWRP versions found over some threads
I would like to know some things. Firstly say there's still nothing when you open http://teamw.in/devices/samsunggalaxys6edge.html
so, i looked up the link you gave
https://idlekernel.com/twrp/zerolte
but if I don't remember wrong, zerolte is S6 flat.
Does that kernel work anyway?
If that's so, does that mean official http://teamw.in/devices/samsunggalaxys6.html or TWRP S6 Edge Europe Version would also work?
Why wouldn't they?
Also, what's the difference with the twrp from @arter97 found Here
with yours?
Thanks!!
I hope someone could shed some light over those questions.
Sorry for my bad english!
Nobody is answering from them here , 0 suport . Kernel from arter97 and twrp recovery from him work fine .
Ognjen123 said:
Nobody is answering from them here , 0 suport . Kernel from arter97 and twrp recovery from him work fine .
Click to expand...
Click to collapse
See my above post.
Alright, this is what I did for my S6 Edge 925F which works fine so I thought I would share it with you guys:
I flashed the latest TWRP using ODIN from this link:
http://www.arter97.com/browse/S6/ke...r97-recovery-g925fi-13.1-twrp_3.0.2-0.tar.md5
which is the same link given at the bottom of this post along with the instructions as well:
http://forum.xda-developers.com/showpost.php?p=60390986&postcount=5
After rebooting the phone (which looped a couple of times), I flashed the latest SuperSU 2.71 (Beta) from ChainFire in the newly flashed TWRP which is given here:
http://forum.xda-developers.com/showthread.php?t=1538053
And now I have TWRP with SuperSU. I need to mention that I rooted my phone with CF-Auto root previously so it was already rooted, but I just wanted to have custom recovery for flashing other .zip files.
I also tried the latest stable version of SuperSU first, but it had problems finding and installing binaries. But there are no problems with the latest Beta (2.71) so far.
Related
Unofficial release -TWRP recovery for the Galaxy Tab S2 - SM-T713/719/813/819, Qualcomm MSM8976
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
Update 1/4/2017
TWRP 3.1.0-1 MM/NN build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from source
System image backup
F2FS support >> To be added
Twrp app support
Bugs:
Reboot to recovery loop when using reboot utilities. Use hardkeys combo only to boot to recovery POWER + HOME + VOL UP
If you get stuck in a recovery loop reflash TWRP with auto-reboot enabled.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.10.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
TWRP 3.1.0-1 - Nougat
twrp_3.1.0-1_sm-t713_14417n
twrp_3.1.0-1_sm-t719_13417n
twrp_3.1.0-1_sm-t813_14417n
twrp_3.1.0-1_sm-t819_14417n
TWRP 3.1.0-1 - Lollipop/Marshmallow
twrp_3.1.0-1_sm-t713_1417
twrp_3.1.0-1_sm-t719_1417
twrp_3.1.0-1_sm-t813_1417
twrp_3.1.0-1_sm-t819_1417
TWRP 3.0.2-1
SM-T713/719
twrp_3.0.2-1_sm-t713
SM-T813
twrp_3.0.2-1_sm-t813
SM-T819
twrp_3.0.2-1_sm-t819_31816
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my testers, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Does rooting require a permissive kernel?
DeeXii said:
Does rooting require a permissive kernel?
Click to expand...
Click to collapse
Rooting doesn't, custom recovery might.
I don't know yet until someone reports.
I was able to both flash TWRP with Odin as well as root the device.
I was not able to mount /data in TWRP however.
I couldn't use adb shell while in recovery due to a libc.so not found error. ADB did work in the Samsung provided Android 6.0.1.
I've attached the recovery log as well as the kernel log.
dalingrin said:
I was not able to mount /data in TWRP however.
Click to expand...
Click to collapse
I'm not sure, but could this be caused by enabled encryption
As far as I know Android devices which are sold with 6.0.1 by default need to be encrypted
dalingrin said:
I was able to both flash TWRP with Odin as well as root the device.
I was not able to mount /data in TWRP however.
I couldn't use adb shell while in recovery due to a libc.so not found error. ADB did work in the Samsung provided Android 6.0.1.
I've attached the recovery log as well as the kernel log.
Click to expand...
Click to collapse
York2k16 said:
I'm not sure, but could this be caused by enabled encryption
As far as I know Android devices which are sold with 6.0.1 by default need to be encrypted
Click to expand...
Click to collapse
Thanks for testing and posting the logs. @York2k16 Correct the error mounting data is because of encryption. Twrp is unable to find the encryption key.
It's true Android 6 devices are encrypted by default, but don't need to be.
Work around for now would be not to use encryption until I find the solution.
The issue with adb is because of Samsungs stock kernel.
I need to recompile it with root protection removed.
Unfortunately no sources are available as yet.
Well at least we have a working recovery and a root solution.
Can you confirm a few things:
UI orientation, portrait or landscape?
UI colour?
All other options and features working correctly?
Thanks, well done for probably being the first in the world to have a rooted S2 VE 8.0
ashyx said:
Work around for now would be not to use encryption until I find the solution.
Click to expand...
Click to collapse
Few weeks ago I've tested the T813 and returned it back after a few days. I'm going to buy the LTE model soon or when the prices go down a bit.
Checking the security settings menu I've realized that there is no option for enabling/disabling device encryption, only SD encryption.
@dalingrin: Is this the same case on your device?
This "issue" would open up another question: How do I decrypt a device, which is encrypted by factory default, but doesn't offer any options to disable/enable encryption?
TWRP does not work properly on T813. I am unable to use it because can not click on buttons
York2k16 said:
Few weeks ago I've tested the T813 and returned it back after a few days. I'm going to buy the LTE model soon or when the prices go down a bit.
Checking the security settings menu I've realized that there is no option for enabling/disabling device encryption, only SD encryption.
@dalingrin: Is this the same case on your device?
This "issue" would open up another question: How do I decrypt a device, which is encrypted by factory default, but doesn't offer any options to disable/enable encryption?
Click to expand...
Click to collapse
you need to format the data partition in TWRP to remove encryption.
whynottoday said:
TWRP does not work properly on T813. I am unable to use it because can not click on buttons
Click to expand...
Click to collapse
How about a little more constructive detail like I asked for?
What orientation is the GUI, is it landscape or portrait. Are the touches simply misplaced?
@dalingrin
Does this at least ask for the encryption password?
https://www.androidfilehost.com/?fid=24572330218881914
Also whilst in the android OS could you post me the output of
ls -l /dev/block/bootdevice/by-name/
Thanks.
ashyx said:
How about a little more constructive detail like I asked for?
What orientation is the GUI, is it landscape or portrait. Are the touches simply misplaced?
Click to expand...
Click to collapse
Oh sorry
So it is landscape and yes it seems that touches are misplaced. Thanks
Sent from my SM-T810 using XDA-Developers mobile app
whynottoday said:
Oh sorry
So it is landscape and yes it seems that touches are misplaced. Thanks
Sent from my SM-T810 using XDA-Developers mobile app
Click to expand...
Click to collapse
Does this fix the touch issue?
https://www.androidfilehost.com/?fid=24572330218881937
.
ashyx said:
Does this fix the touch issue?
https://www.androidfilehost.com/?fid=24572330218881937
.
Click to expand...
Click to collapse
Yes thanks so much. Root done with my sdcard. Mount issue still here
Sent from my SM-T810 using XDA-Developers mobile app
whynottoday said:
Yes thanks so much. Root done with my sdcard. Mount issue still here
Sent from my SM-T810 using XDA-Developers mobile app
Click to expand...
Click to collapse
Mount issue, you mean data?
Can you post the recovery.log.
You will find it under Advanced in twrp.
ashyx said:
mount issue, you mean data?
Can you post the recovery.log.
You will find it under advanced in twrp.
Click to expand...
Click to collapse
here attached
whynottoday said:
here attached
Click to expand...
Click to collapse
try this, could you post the log too please.
https://www.androidfilehost.com/?fid=24572330218881937
I now have a T713 if you need anything tested.
---------- Post added at 11:52 AM ---------- Previous post was at 11:46 AM ----------
Anyone here have a link to the T713 stock PD9 firmware?
DeeXii said:
I now have a T713 if you need anything tested.
---------- Post added at 11:52 AM ---------- Previous post was at 11:46 AM ----------
Anyone here have a link to the T713 stock PD9 firmware?
Click to expand...
Click to collapse
Can you test the link in post #11.
Can you mount data?
ashyx said:
Can you test the link in post #17.
Can you mount data?
Click to expand...
Click to collapse
Give me a few...
I'm finishing up some work things and uploading stock to AFH.
---------- Post added at 12:51 PM ---------- Previous post was at 12:50 PM ----------
ashyx said:
Can you test the link in post #11.
Can you mount data?
Click to expand...
Click to collapse
Post #17 says its for T813; Does that matter?
Team Win Recovery Project 3.0.2-0
This is for the Chinese SM-G9350 Qualcomm model only! Do not flash on Exynos models!
If you have a SM-G9300 or SM-G9308, look here instead!
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 edge 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/samsunggalaxys7edgechina.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin 3.12.3+ 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
Follow these instructions until someone nice comes along and makes a video from them (without ads):
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
You will need to unlock your bootloader now. To do this, download the app "CROM Service By Samsung Electronics Co., Ltd." from the Galaxy Apps store and run it.
Follow the instructions in the CROM Service app to allow your device to accept custom images in download mode.
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 hero2qltechn.
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 7.
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 step 10 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.
If you want to be rooted with something else or just want a bootable system:
Download the latest no-verity-opt-encrypt zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
It will allow your system to boot after swiping to enable modifications or using backup/restore in TWRP.
It should also allow you to use [Format Data] and prevent encryption, allowing you to use your data partition and internal storage inside TWRP.
Go to [Reboot] -> [System].
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.0 - Official release on twrp.me
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 (USA): https://github.com/jcadduono/android_device_samsung_hero2qlte (android-6.0)
Device tree (China): https://github.com/TeamWin/android_device_samsung_hero2qltechn (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_msm8996 (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 China, Tool/Utility for the Samsung Galaxy S7 Edge
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/TeamWin/android_device_samsung_hero2qltechn
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-09-09
Created 2016-09-10
Last Updated 2016-11-22
As a joke, here you go USA!
https://idlekernel.com/twrp/hero2qlte/twrp-3.0.2-0-hero2qlte.tar.md5
It works for all USA variants of the S7 edge, but you can't flash it! Muahahahaha!
You going to compile with DM-Verification off? You can check my device tree it has the kernel built with it disabled.
travis82 said:
You going to compile with DM-Verification off? You can check my device tree it has the kernel built with it disabled.
Click to expand...
Click to collapse
It doesn't matter, dm-verity isn't enabled in the fstab, nor does the TWRP image contain any verity signatures to enforce.
finally...
thank god!finally!but the front cam issue have been solved?
Anyone know what roms work with this device? Also how to return to stock?
When compression is enabled on backups the device freezes.
What happened to CROM Service? It's not in the Galaxy Apps and .apk's from mirror websites crash when opened.
I flashed this twrp but recovery won't boot. Get blue screen with red writing up top that says custom binary blocked by secure boot (recovery.img). I have gs7 edge AT&T version. Now what?
ryan49er said:
I flashed this twrp but recovery won't boot. Get blue screen with red writing up top that says custom binary blocked by secure boot (recovery.img). I have gs7 edge AT&T version. Now what?
Click to expand...
Click to collapse
this recovery is for unlocked bootloaders only. IE chinese and hong kong models only.
Well that sucks
Report...
jcadduono said:
Team Win Recovery Project 3.0.2-0
This is for the Chinese SM-G9350 Qualcomm model only! Do not flash on Exynos models!
If you have a SM-G9300 or SM-G9308, look here instead!
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 edge 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/samsunggalaxys7edgechina.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin 3.12.3+ 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
Follow these instructions until someone nice comes along and makes a video from them (without ads):
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.
You will need to unlock your bootloader now. To do this, download the app "CROM Service By Samsung Electronics Co., Ltd." from the Galaxy Apps store and run it.
Follow the instructions in the CROM Service app to allow your device to accept custom images in download mode.
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 hero2qltechn.
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 7.
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 step 10 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.
If you want to be rooted with something else or just want a bootable system:
Download the latest no-verity-opt-encrypt zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
It will allow your system to boot after swiping to enable modifications or using backup/restore in TWRP.
It should also allow you to use [Format Data] and prevent encryption, allowing you to use your data partition and internal storage inside TWRP.
Go to [Reboot] -> [System].
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.0 - Official release on twrp.me
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 (USA): https://github.com/jcadduono/android_device_samsung_hero2qlte (android-6.0)
Device tree (China): https://github.com/TeamWin/android_device_samsung_hero2qltechn (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_msm8996 (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 China, Tool/Utility for the Samsung Galaxy S7 Edge
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/TeamWin/android_device_samsung_hero2qltechn
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-09-09
Created 2016-09-10
Last Updated 2016-11-22
Click to expand...
Click to collapse
I had G9350ZCU2APK2 ROM (China), so I installed the Hong Kong ROM G9350ZHU2APK2 (I needed the google services) and the phone work great except the part of receiving or sending SMS's, I have two sim cards cards (China Telecom and China Mobile), if I sent a message from the CT the message was sent also from CM, if I send from CM is not working, when I receive messages I received on both sim cards... , big problem for me, so, I installed the last G9350ZCU2APL3 ROM (China) and is working ok but no google services...
I've tried your method and is working... (kind of) once I installed the TWRP and the last SuperSU the phone had no Wifi and no network signal, so I put back the original firmware...
All I need are the google services because Signal is not working without, the email client is not receiving the email (automatically) without and so on... I've tried all the "possible" ways, no luck...google installer v2 and so on...
Any ideas on how to put the google services?
----- Edit - 28 January 2017 ----
I reinstalled the TWRP provided in the first post and the phone is working, has signal (China Telecom and China Mobile) and also the WIFI is working, I didn't install the SuperSU, kind of weird, with SuperSu installed the phone has no WIFI and no signal...
I've tried to install the gapps pico and the TWRP is saying that "could not mount/data and unable to find crypto folder", "Failed to mount '/data' (invalid argument)", "Unable to recreate /data/media folder", "failed to mount '/data' (Invalid argument)", "Unable to mount storage" , "Unable to mount / data/media/TWRP/. twrps.
The last error is: "Failed to mount'/data' (invalid argument)
After reading more posts on the forum I found the following:
"You CANNOT mount an encrypted partition in TWRP.
You do NOT wipe the partition.
Use the FORMAT DATA button. It's right there under the WIPE options next to the ADVANCED WIPE button."
Probably I will try this method when I am in the mood...
This works for SM-G935P? It says manufactured in china on the back.
Salanrm said:
This works for SM-G935P? It says manufactured in china on the back.
Click to expand...
Click to collapse
The post is for the Qualcomm, Galaxy S7 Edge SM-9350, China Open and Hong Kong, same hardware, different software (the Chinese one has no google services).
For your phone SM-G935P, search on google and you will find more instructions, I don't know if I am allowed to post here links from other websites.
jcadduono said:
As a joke, here you go USA!
twrp-3.0.2-0-hero2qlte.tar.md5
It works for all USA variants of the S7 edge, but you can't flash it! Muahahahaha!
Click to expand...
Click to collapse
good afternoon
Reference is unfortunately not working
Can somebody share twrp-3.0.2-0-hero2qlte.tar.md5
thank you in advance for your response
So, this will 100% NOT work for the g935A? (Att s7 edge)
Craz Basics said:
So, this will 100% NOT work for the g935A? (Att s7 edge)
Click to expand...
Click to collapse
No. Locked bootloader
Sent from my SM-G935T using Tapatalk
Ahhh. That's some crap. Think it will ever be able to be unlocked?
Craz Basics said:
Ahhh. That's some crap. Think it will ever be able to be unlocked?
Click to expand...
Click to collapse
It's a serious long shot but it is slowly being worked on.. check out this thread. It's for t mobile but the solution if found will apply to all us carriers as we all use the same method to root on marshmallow.
https://forum.xda-developers.com/showthread.php?t=3544220
Sent from my SM-G935T using Tapatalk
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Device specific page including instructions for a manual install
Download links for current and past versions of TWRP
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[kagura] TWRP 3.1.1-0 touch recovery, Tool/Utility for the Sony Xperia XZ
Contributors
AndroPlus
Source Code: https://github.com/TeamWin/android_device_sony_kagura
Version Information
Status: Stable
Created 2016-10-08
Last Updated 2017-08-28
Now it's official!
Make a material version?
Sent from my F8332 using Tapatalk
Can someone post a detailed instruction please? I followed the TWRP instructions but kept getting stuck on "waiting for devices" on fastboot. I tried several different drivers suggested in other threads but none worked for me
@AndroPlus Do we need an unlocked bootloader for this?
Yes we do.
@AndroPlus, please maybe you can give some hint. I unlocked the bootloader (worked), when I installed TWRP with fastboot and the installation seemed to be sucessful, but I cant boot into TWRP. During boot I'm pressing vol+, but nothing happens. Even the LED shows no light during boot. What I did wrong or what can I do to boot into TWRP?
edit: problem solved I installed your kernel with: sudo fastboot flash boot boot.img
and now I can boot into TWRP and LED during boot shows light. Seems to be a really great kernel.
paulle said:
@AndroPlus, please maybe you can give some hint. I unlocked the bootloader (worked), when I installed TWRP with fastboot and the installation seemed to be sucessful, but I cant boot into TWRP. During boot I'm pressing vol+, but nothing happens. Even the LED shows no light during boot. What I did wrong or what can I do to boot into TWRP?
Click to expand...
Click to collapse
1. Turn your device off.
2. At the same time, press the Power button and Volume down until your device vibrates.
3. Quickly release the Power button, but keep pressing Volume down (5 sec or more).
AndroPlus said:
1. Turn your device off.
2. At the same time, press the Power button and Volume down until your device vibrates.
3. Quickly release the Power button, but keep pressing Volume down (5 sec or more).
Click to expand...
Click to collapse
Thank you, this method worked too.
@AndroPlus will that work with the dual Sim version F8332 also?
hanaheeno said:
@AndroPlus will that work with the dual Sim version F8332 also?
Click to expand...
Click to collapse
yes
Thanks a lot for your great amazing efforts @AndroPlus, is there any need to unlock the bootloader prior to rooting or flashing TWRP? And if yes, is it simply booting into fastboot and running the command "fastboot oem unlock" or enabling it from the Developer Options?
hanaheeno said:
Thanks a lot for your great amazing efforts @AndroPlus, is there any need to unlock the bootloader prior to rooting or flashing TWRP? And if yes, is it simply booting into fastboot and running the command "fastboot oem unlock" or enabling it from the Developer Options?
Click to expand...
Click to collapse
You have to enable oem unlock in developer options and run "fastboot oem unlock", then flash my custom kernel.
Because of strict security, we have to edit kernel to disable sony_ric and dm-verity to root if you want to custom /system.
If you can use system-less SuperSU you don't need to flash custom kernel.
Restore bug?
I just restored my backup and IMEI was gone. So the backup as such works fine besides the IMEI. Consequently I couldn't connect to the mobile network. I had to flashtool the original rom and restart the whole process.
Anyone else experienced such a problem?
I've repacked the 250 stock kernel with everything (except twrp, indeed). I use your recovery, and it works fine so far. But from system, I can't boot into twrp directly (e. g. from Titanium Backup or NeoPowerMenu).
For any help thanks in advance!
Hi, I flashed the twrp.img, but when I tried wipe or install rom to xperia XZ, I got can't unmount system, 'device or resource busy' error. Any ideas how to fix it? Thanks
drakegao said:
Hi, I flashed the twrp.img, but when I tried wipe or install rom to xperia XZ, I got can't unmount system, 'device or resource busy' error. Any ideas how to fix it? Thanks
Click to expand...
Click to collapse
See post #13 (3 posts above yours) - doing this does the trick
Klaus N. said:
See post #13 (3 posts above yours) - doing this does the trick
Click to expand...
Click to collapse
Thanks give a try. Will this twrp work on UK-customized rom? I flashed that rom using flash tool
drakegao said:
Thanks give a try. Will this twrp work on UK-customized rom? I flashed that rom using flash tool
Click to expand...
Click to collapse
Yes, indeed.
No boot in recovery
Problem: Unlock done and OK, flashed TWRP and OK. But I cannot boot in TWRP. Not with buttons, not with adb. I see only the message, that my device is unlocked.... The LED ist dark.
Today I flashed the kernel v4 and Ok, flashed TWRP again and ok, same result. No boot in recovery. Only the f***in message that my device is unlocked, Firmware is..... . 260 and a German xz single Sim.
Any Idea? Sorry for my poor English.
Unofficial release -TWRP recovery for the Galaxy A7 - SM-A720F/DS, Exynos 7880
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
Update 12/4/2017
TWRP 3.1.0-1 MM build released.
Current status: BETA
NOTE: THIS IS CURRENTLY IN THE TESTING STAGE, THERE MAYBE BUGS, IT MAY NOT BOOT AT ALL. I DON'T OWN THIS DEVICE. I CAN'T FIX ISSUES IF PEOPLE DON'T POST RECOVERY LOGS OR PROPERLY DESCRIBE THE ISSUE. STOCK RECOVERY IS PROVIDED BELOW IF NEEDED.
Features:
MTP working > to be confirmed
ADB working > to be confirmed
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory images from the official firmware can now be flashed with TWRP instead of ODIN. I have extended this feature to include BOOT, RECOVERY, SYSTEM, CACHE, HIDDEN and RADIO(MODEM) partitions.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
NOTE: To flash the modem, first it needs to be renamed to modem.bin.img
Issues:
Current versions of SuperSU seem to be incompatible.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.10.7.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
TWRP: twrp_3.1.0-1_sm-a720f_12417
Stock recovery: A720FXXU1AQC5_stock_recovery
To Root:
PHH SUPERUSER
https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
or MAGISK
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption and mount internal storage (/DATA):
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install root (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin, my tester moistcity
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
. .
thanks
Hello, when I'm flashing SuperSU the phone reboots at extracting files.
Cannot flash supersu
Sorry, I'm a new member. Had inadvertently edited
@aindra.ap29
Why did you post that?! Please remove your unnecessary post.
moistcity said:
Hello, when I'm flashing SuperSU the phone reboots at extracting files.
Click to expand...
Click to collapse
Any chance you can you test the patched version of SuperSU below?
Please save the recovery log file afterwards.
SR3-SuperSU-v2.79-SR3-20170114223742-ashyx
.
thanks bro.. :highfive:
can i try with firmware A720FXXU1AQC6?
and how about knox?
ashyx said:
Any chance you can you test the patched version of SuperSU below?
Please save the recovery log file afterwards.
SR3-SuperSU-v2.79-SR3-20170114223742-ashyx
.
Click to expand...
Click to collapse
Fancy meeting you here
I've got magisk already but I'll try to flash this and report back with the recovery log.
Off topic question though,
Has there been any successful attempt at removing the knox counter on new samsung phones (S7, A2017, C2017 etc..)?
moistcity said:
Fancy meeting you here
I've got magisk already but I'll try to flash this and report back with the recovery log.
Off topic question though,
Has there been any successful attempt at removing the knox counter on new samsung phones (S7, A2017, C2017 etc..)?
Click to expand...
Click to collapse
No, it can't be done. This is one thing that Samsung make sure of. I've seen certain websites and procedures claiming they can, but I know of no recent Samsung device that can be reset.
@ashyx will you make a version for the A5?
@ashyx
Ok, I've been reading and watching videos on Magisk, which I have never heard of before, so now I have a more informed opinion of it. It's interesting, but there definitely are some red flags, particularly with version 12 (as per reviewers). I might give it a shot, even though I still think SuperSU is more reliable and stable.
As for the patched SuperSU, was it patched by Chainfire or by you?
stephymv said:
@ashyx
Ok, I've been reading and watching videos on Magisk, which I have never heard of before, so now I have a more informed opinion of it. It's interesting, but there definitely are some red flags, particularly with version 12 (as per reviewers). I might give it a shot, even though I still think SuperSU is more reliable and stable.
As for the patched SuperSU, was it patched by Chainfire or by you?
Click to expand...
Click to collapse
Blimey you don't trust anyone! It was patched by me, honestly I won't steal your bank account details.
ashyx said:
Blimey you don't trust anyone! It was patched by me, honestly I won't steal your bank account details.
Click to expand...
Click to collapse
Lol. It's not about that, I just like to be well informed. Among other things, now I know, for example, that when Chainfire updates its app (say, to 2.80), the ZIP might still be unflashable, due to the patched version being yours, not theirs, thus, rendering their official download page pretty much useless to A7 users.
I don't have a Windows device, so I'll update you when I can.
Thanks.
stephymv said:
Lol. It's not about that, I just like to be well informed. Among other things, now I know, for example, that when Chainfire updates its app (say, to 2.80), the ZIP might still be unflashable, due to the patched version being yours, not theirs, thus, rendering their official download page pretty much useless to A7 users.
I don't have a Windows device, so I'll update you when I can.
Thanks.
Click to expand...
Click to collapse
Why do you need Windows?
ashyx said:
Why do you need Windows?
Click to expand...
Click to collapse
To flash TWRP with Odin.
stephymv said:
To flash TWRP with Odin.
Click to expand...
Click to collapse
I'd assumed you'd already flashed it. No PC at all?
ashyx said:
I'd assumed you'd already flashed it. No PC at all?
Click to expand...
Click to collapse
Yeah, none at all. I always have to go to a lanhouse, or ask someone to use theirs.
Unfortunately, we still need Windows for a lot of things, even when we don't want/have it anymore. Hopefully someday you guys will create methods where neither root nor Odin are needed to flash custom recoveries.
Oh, and I reinstalled the stock ROM when SU failed, so that's why.
See you soon.
@ashyx
Hmm.. I tried flashing the patched SuperSU but the same thing happens. It automatically reboots at "extracting files". Guess I can't provide a useful recovery.log
I restored back to my old root and I just recently discovered that magisk has some downloadable modules. Some worked but the xposed sdk23 87.1 says its been installed but doesn't appear on the modules and rebooting doesn't do a thing. I guess, help?
@moistcity
Because you're already rooted, you can probably install the Xposed sdk (if you have a Samsung, get the patched sdk, by Wanam, to avoid bootloops) directly (via TWRP) and then the Xposed installer (manager) on Android.
As for making it work within Magisk, @ashyx might know, I can't help you there as I am yet to try and know Magisk firsthand. I don't know if Magisk (modules segment) and Xposed installer can coexist, but you never know ('til you know).
Try installing the Xposed installer and see if the module you installed from Magisk shows up on the former.
Assuming they can coexist (and flashing the sdk via TWRP on a device with Magisk won't trigger bootloops), you can just install Xposed the traditional way then, unless you absolutely want the Magisk module to work. Before doing the traditional method, look up for information on coexistence, before risking it.
Will it work for A7 - SMA700FD ??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unofficial TWRP 3.4.0.0 For Galaxy note 7 FE (N935X)
Disclaimer:
I do not own this device, however i work on the S7/S7E and there was enough requests for a FE support. so here we are.
This TWRP has been tested on 2 devices so far, it fixes mounting issues, and is based on new device trees. This should pave the way for other S7 developers to join in and add support to the FE since its not that difficult.
My custom kernel (Cronos) and Floyd Q Rom will make it to this thread once they are validated more.
Thanks to @butchieboy and Đỗ Gia Huy for testing
Also moving forward with this thread, you take full responsibility of any modifications done towards your device.
Features: :
Code:
- built from latest Pie source
- built from android-9.0 recovery sources
- fully compatible with Android 8.*/9.0/10.0
- Full F2FS Support for data and cache
- Full support for FLoydQ ROM
- Built with Busybox and resetprop
Downloads:
N935X (N935F/FD/S/L/K) : Download
Instructions:
Odin
Download latest Odin zip from Here
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Home + Volume down + Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in your hands, disconnect the usb cable and press simultaneously the Home + Volume down + power until the Download mode pop-up shows
Press volume DOWN (so the phone reboots) then quickly press Home + VolumeUp + Power until the TWRP screen shows up
If it didn`t worked, redo the steps from #1 being more careful. and faster
TWRP (If you have a previous twrp installed)
Download TWRP_*.img, push it into phone storage (or external sdcard if thats not avalible), choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods due to RMM Lock / KG State, make sure you check this thread
Rooting and Internal Storage:
Finally, if you want to be able to read/write to the internal storage, you must format it to clear encryption, take a backup of your stuff before hand.
Go to TWRP > Wipe > Format Data > Type YES.
your data is now usable. if you didnt flash noverity-opt-encrypt or MagiskRoot your data will be encrypted again.
If you want to root your device now, simply download the latest magisk and flash it in your new recovery.
Sources:
Device tee : Github
Kernel : Github
Credits:
TeamWin, corsicanu, morogoku, Shariq3422 and testers
XDA:DevDB Information
TWRP-3.4.0.0, Tool/Utility for the Samsung Galaxy Note FE
Contributors
ananjaser1211, morogoku, corsicanu, Shariq3422
Source Code: https://github.com/ananjaser1211/android_device_samsung_gracerlte
Version Information
Status: Testing
Current Stable Version: V1.0
Stable Release Date: 2020-06-23
Current Beta Version: V1.0
Beta Release Date: 2020-06-23
Created 2020-06-23
Last Updated 2020-06-25
Misc Links:
Telegram Support Group
[*]Telegram news Channel
Latest Magisk
FloydQ Oneui 2.0 Beta ROM + N7FE Kernel
F.A.Q
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Can,t find OEM Toggle, RMM Locked
A : Read this thread
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Make sure you have the latest samsung stock firmware installed (to be on latest bootloader and modem combo)
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
Q: How to Use F2FS ?
A : This requires you to be on Floyd ROM and the latest FE CronosKernel build. otherwise you wont be able to boot. Follow these steps
1) Wipe > advanced wipe > Data > CHANGE > F2FS (Your entire internal storage will be wiped out!)
2) Reboot and you will have DATA as F2FS, the same can be done to CACHE as well. Do not do it to SYSTEM
P.S : Again, make sure BOTH your ROM and KERNEL support F2FS.
Please let me know what issues you find in this TWRP, i am aware it boots, backsup and flashes zips. but do let me know if USB / MTP works as expected or if it needs further work.
I will be working on adding FE Support to all my exynos8890 projects moving forward. hopefulyl putting some life in this forum
Yo ma...man
Well done bro!
USB OTG works. Got this error when formatting data. Restored backup that was generated, everything went fine booted up as normal.
Sent from my SM-N975U using Tapatalk
TWRP-3.4.0.0-gracerlte-20200625
TWRP-3.4.0.0-gracerlte-20200625
* Fix error in SAR disable script (Fixes installing android 9 roms while 10 is installed)
* include resetprop (required for SAR script)
* Add custom TWRP Ver Name
Download : Github
This should fix the error reported above, and fix installing Pie roms while having 10 installed.
Wow, you are all over the place my friend. Thank you..lol[emoji481]
Sent from my SM-N975U using Tapatalk
Error no longer present
Sent from my SM-N975U using Tapatalk
Getting error again when trying to create backup or flash anything
Sent from my SM-N975U using Tapatalk
butchieboy said:
Getting error again when trying to create backup or flash anythingView attachment 5048397
Sent from my SM-N975U using Tapatalk
Click to expand...
Click to collapse
Could you try to flash a pie rom while having my Q rom installed ?
the script is there to change /system_root mount point back to /system . which is due to recent TWRP changes
i think the script is erroring due to line endings, but im not sure. let me know if the ROM flashed.
for System backup always use the system image format while dealing with android 10. ill update you if twrp pushes any more updates to this
The only Pie roms that we had for FE caused major issues. Not sure if anyone even uses them there was 1 I think. Developer threw a rom together that would throw malware on your device, lock it up and made device unusable then vanished without fixing anything. So not sure if anything is out there and really don't want to update my bootloader.
Sent from my SM-N975U using Tapatalk
ananjaser1211 said:
Please let me know what issues you find in this TWRP, i am aware it boots, backsup and flashes zips. but do let me know if USB / MTP works as expected or if it needs further work.
I will be working on adding FE Support to all my exynos8890 projects moving forward. hopefulyl putting some life in this forum
Click to expand...
Click to collapse
Installed TWRP 3.4.0.0 on the SM-N930, everything works ... Thanks Bro !!!
---------- Post added at 10:02 AM ---------- Previous post was at 09:18 AM ----------
ananjaser1211,may I ask you to build a core for SM-N930X???...I will be grateful.
I have released my cronos kernel for Pie
For a feature list , they are mentioned on this thread here
So now you can use the same kernel from Q on pie ROMs if you choose so.
Download : Github
Enjoy
Just flashed your Floyd Q 3.0 on Note FE...my friend you are really keeping these older devices alive. Thank you.
NOTE FE FLOYD Q 3.0
thank you thank you THANK YOU
---------- Post added at 04:45 PM ---------- Previous post was at 04:41 PM ----------
It's work
butchieboy said:
Just flashed your Floyd Q 3.0 on Note FE...my friend you are really keeping these older devices alive. Thank you.
NOTE FE FLOYD Q 3.0
Click to expand...
Click to collapse
Did you have issues booting into system after you rooted? I know it's old but I just can't do it after flashing and following the root guide here
Nope sure didnt
Sent from my SM-N975U using Tapatalk
twrp-3.5.2_9-0-gracerlte.img
twrp-3.5.2_9-0-gracerlte.tar
ripee said:
twrp-3.5.2_9-0-gracerlte.img
twrp-3.5.2_9-0-gracerlte.tar
Click to expand...
Click to collapse
link broken