Unofficial release -TWRP recovery for the Galaxy A8 - SM-A810F/DS, Exynos 7420
{
"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 17/4/2017
TWRP 3.1.0-1 MM build released.
Current status: BETA
Features:
MTP working
ADB working
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
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.
How we got here: https://forum.xda-developers.com/sa...w-time-to-getting-support-a8-2016-sm-t3511148
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-a810f_17417
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, Teamwin, my testers(majinawaz, RootAgain)
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
.
Awesome work dear if i able to buy a beer for you i must buy it
First, thanks boss @ashyx for great work. If you remember, I was first who asked yoi for twrp for this good phone. In meantime I bought it, and you make twrp. I tried it immediately and got this results :
Maybe it is important that I first done ota to newest offered AQA1 update.
Than odin flash twrp. All ok. Reboot to it and format data from wipe menu.
Hot error cant mount pcifs (maybe different name, I forgot, I can see again sorry).
Then flash supersu and patch and got same error, pcifs?
Root is working perfect but mount not. I back in twrp and see mount, it sees data. But tried some twrp install zip and got same error. And no app.
So obviously it is not mounted good...
Is there solution?
Thanks biggest
ivanox1972 said:
First, thanks boss @ashyx for great work. If you remember, I was first who asked yoi for twrp for this good phone. In meantime I bought it, and you make twrp. I tried it immediately and got this results :
Maybe it is important that I first done ota to newest offered AQA1 update.
Than odin flash twrp. All ok. Reboot to it and format data from wipe menu.
Hot error cant mount pcifs (maybe different name, I forgot, I can see again sorry).
Then flash supersu and patch and got same error, pcifs?
Root is working perfect but mount not. I back in twrp and see mount, it sees data. But tried some twrp install zip and got same error. And no app.
So obviously it is not mounted good...
Is there solution?
Thanks biggest
Click to expand...
Click to collapse
Post the recovery log file, so I can take a look.
How boss and which to do and to send result of it?
ivanox1972 said:
how boss and which to do and to send result of it?
Click to expand...
Click to collapse
twrp > advanced > save log
@ashyx boss strange thing, it seems it works with this error message? Look picture. I boot to twrp, data mounted, give classic backup job.
It did system and data and boot and on end message
Failed to mount cpefs.
Maybe actually it works, with this dummy message?
ivanox1972 said:
@ashyx boss strange thing, it seems it works with this error message? Look picture. I boot to twrp, data mounted, give classic backup job.
It did system and data and boot and on end message
Failed to mount cpefs.
Maybe actually it works, with this dummy message?
Click to expand...
Click to collapse
It's a protected partition so it can't mount. I should just remove it from the fstab.
You can just ignore it.
Thanks boss, so this is 100,% functional terp I can totally believe in backups and everything else?
ivanox1972 said:
Thanks boss, so this is 100,% functional terp I can totally believe in backups and everything else?
Click to expand...
Click to collapse
I don't see why not, the main partitions are able to be backed up.
After phone user Super burn recovery and their code is the code?
I could not do it. Do you have a video? Mount data failed
Awesome work
@ashyx Hi buddy, adb doesnt seems to work in twrp
AL_IRAQI said:
@ashyx Hi buddy, adb doesnt seems to work in twrp
Click to expand...
Click to collapse
Disable MTP in TWRP.
ashyx said:
Disable MTP in TWRP.
Click to expand...
Click to collapse
i already did that, it says device offline
BTW
did you think about pushing tree to official ?
AL_IRAQI said:
i already did that, it says device offline
BTW
did you think about pushing tree to official ?
Click to expand...
Click to collapse
I'd suggest installing the ADB drivers whilst in recovery mode.
Check device manager has detected it as an ADB device.
Hello ashyx adb is not working and shows adb device offline any solution please
[email protected] said:
Hello ashyx adb is not working and shows adb device offline any solution please
Click to expand...
Click to collapse
Disable MTP in TWRP first.
Thanks for your reply i will try it and reply you soon bro
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.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.
INSTRUCTIONS FOR ADB BACKUP:
https://www.droidorigin.com/take-adb-backup-using-twrp-v3-1-0-0/
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
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:
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, 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
.
Hands off.
As usual nobody can find the time to report back.
Thanks!
Successfully flashed TWRP but cannot flash SuperSU. TWRP reboots when superSU installer is doing "Extracting files"
moistcity said:
Thanks!
Successfully flashed TWRP but cannot flash SuperSU. TWRP reboots when superSU installer is doing "Extracting files"
Click to expand...
Click to collapse
Can you save and post the recovery.log file.
ashyx said:
Can you save and post the recovery.log file.
Click to expand...
Click to collapse
Hmm... I don't know how to attach files and xda doesnt let me post outside links
I have it on a google drive, I could email it.
moistcity said:
Hmm... I don't know how to attach files and xda doesnt let me post outside links
I have it on a google drive, I could email it.
Click to expand...
Click to collapse
Just put it on pastebin.com and just post the link without the https://pastebin.com
OK just looked at the log and I don't see any issues or reason why SuperSU would fail.
Maybe try a different version of SuperSU?
ashyx said:
OK just looked at the log and I don't see any issues or reason why SuperSU would fail.
Maybe try a different version of SuperSU?
Click to expand...
Click to collapse
Tried 2.79 sr2 but still nothing.
Trying 2.78 to see if it works or not
---------- Post added at 06:44 AM ---------- Previous post was at 06:26 AM ----------
Tested 2.78 and 2.77 beta.
2.78 reboots back to twrp.
2.77 reboots back to system.
I think it can't log what happened cause it just reboots on the process of flashing superSU.
moistcity said:
Tried 2.79 sr2 but still nothing.
Trying 2.78 to see if it works or not
---------- Post added at 06:44 AM ---------- Previous post was at 06:26 AM ----------
Tested 2.78 and 2.77 beta.
2.78 reboots back to twrp.
2.77 reboots back to system.
I think it can't log what happened cause it just reboots on the process of flashing superSU.
Click to expand...
Click to collapse
Everything else works fine? Backup, restore etc?
Can you see if /tmp exists in TWRP file manager.
Can you install the no-verity-no-encrypt_ashyx OK?
ashyx said:
Everything else works fine? Backup, restore etc?
Can you see if /tmp exists in TWRP file manager.
Can you install the no-verity-no-encrypt_ashyx OK?
Click to expand...
Click to collapse
Backup and restore works.
didn't check on that one but pretty sure /tmp is there.
I have installed no-verity-no-encrypt_ashyx just as the instructions said.
Resetting phone firmware with Smart Switch and trying it again.
Recovery.log before installing no-verity-no-encrypt_ashyx and SuperSU
pastebin.com/5VexMze8
Recovery.log after attempting to install SuperSU (Same problem happened again, fresh firmware)
pastebin.com/diY9xGP0
Recovery.log after successfully installing no-verity-no-encrypt_ashyx and attempting to install SuperSU
pastebin.com/SL4xyYRY
moistcity said:
Backup and restore works.
didn't check on that one but pretty sure /tmp is there.
I have installed no-verity-no-encrypt_ashyx just as the instructions said.
Resetting phone firmware with Smart Switch and trying it again.
Recovery.log before installing no-verity-no-encrypt_ashyx and SuperSU
pastebin.com/5VexMze8
Recovery.log after attempting to install SuperSU (Same problem happened again, fresh firmware)
pastebin.com/diY9xGP0
Recovery.log after successfully installing no-verity-no-encrypt_ashyx and attempting to install SuperSU
pastebin.com/SL4xyYRY
Click to expand...
Click to collapse
So it seems the issue is with SuperSU and may be one for Chainfire to look at.
Considering the boot image patcher installs fine, proves that zips are working.
I'm going to have a look at the supersu install script before I raise it as a bug.
ashyx said:
So it seems the issue is with SuperSU and may be one for Chainfire to look at.
Considering the boot image patcher installs fine, proves that zips are working.
I'm going to have a look at the supersu install script before I raise it as a bug.
Click to expand...
Click to collapse
Please do. I'd want to root my A720F and remove these annoying bloat.
moistcity said:
Please do. I'd want to root my A720F and remove these annoying bloat.
Click to expand...
Click to collapse
You can try installing system mode supersu. It may install, but I will need to manually patch the boot image .
Make a backup of your boot and system partition then install the version of SuperSU below.
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
Flash the patched boot image with ODIN or TWRP. If your device had encrption disabled you will need to flash no-verity-no-encrypt_ashyx again afterwards to disable encryption.
A720FXXU1AQC5_patched_root_boot
.
ashyx said:
You can try installing system mode supersu. It may install, but I will need to manually patch the boot image .
Make a backup of your boot and system partition then install the version of SuperSU below.
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
Flash the patched boot image with ODIN or TWRP. If your device had encrption disabled you will need to flash no-verity-no-encrypt_ashyx again afterwards to disable encryption.
A720FXXU1AQC5_patched_root_boot
.
Click to expand...
Click to collapse
System mode SuperSU tries to install a lot shorter now, stops and reboots at "Installing" or something, too fast I can't read it.
I have also flashed the patched boot image and for some reason flashed no-verity-no-encrypt_ashyx again.
This is the recovery.log
pastebin.com/5JHqasFP
moistcity said:
System mode SuperSU tries to install a lot shorter now, stops and reboots at "Installing" or something, too fast I can't read it.
I have also flashed the patched boot image and for some reason flashed no-verity-no-encrypt_ashyx again.
This is the recovery.log
pastebin.com/5JHqasFP
Click to expand...
Click to collapse
That log contains nothing regarding supersu. You should go to ADVANCED> SAVE LOG after running supersu or does twrp automatically reboot?
Can you also open TWRP terminal and see if you get the ~# prompt then type getenforce and report the output.
ashyx said:
That log contains nothing regarding supersu. You should go to ADVANCED> SAVE LOG after running supersu or does twrp automatically reboot?
Can you also open TWRP terminal and see if you get the ~# prompt then type getenforce and report the output.
Click to expand...
Click to collapse
After typing getenforce, the terminal outputted "Permissive".
Does the recovery log overwrite itself when turning on the phone? If I can pull the recovery log right before it automatically reboots, is it possible to see the problem?
moistcity said:
After typing getenforce, the terminal outputted "Permissive".
Does the recovery log overwrite itself when turning on the phone? If I can pull the recovery log right before it automatically reboots, is it possible to see the problem?
Click to expand...
Click to collapse
The recovery log changes each time recovery is booted into.
If it's auto rebooting it would be difficult to catch it as it may not catch the error.
You can use the command below with ADB to try and grab it before it reboots.
Disable MTP then do:
adb devices
adb pull /tmp/recovery.log
There are also alternatives to get root.
You can try 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
Managed to pull the recovery log before the phone reboots itself.
Code:
*****************
SuperSU installer
*****************
- Mounting /system, /data and rootfs
mount: mounting /dev/block/mmcblk0p25 on /data failed: Device or resource busy
2+0 records in
2+0 records out
2 bytes (2B) copied, 0.002642 seconds, 757B/s
3+0 records in
3+0 records out
3 bytes (3B) copied, 0.000393 seconds, 7.5KB/s
10+0 records in
10+0 records out
10 bytes (10B) copied, 0.000563 seconds, 17.3KB/s
0+0 records in
0+0 records out
0 bytes (0B) copied, 0.001912 seconds, 0B/s
/tmp/updater: line 971: /system/toolbox: not found
- Extracting files
Then it reboots back to twrp
---------- Post added at 07:10 AM ---------- Previous post was at 06:43 AM ----------
ashyx said:
There are also alternatives to get root.
You can try 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
Click to expand...
Click to collapse
Rooted my phone at last using Magisk. Finally!
Magisk Manager confirms that the device is properly rooted and I have backed it up by using Root Checker Basic and by
Code:
adb shell
[email protected]:/ $ su
[email protected]:/ #
Thank you very much.
I am wondering however what are the differences between PHH and Magisk, it seems that Magisk is more popular so I strongly went for that first. Being someone who only knows SuperSU, how do these installers differ?
At this point do I still need to install the patched-root-boot and no-verity-no-encryption? I have installed no-verity-no-encryption before doing the root.
moistcity said:
Managed to pull the recovery log before the phone reboots itself.
Then it reboots back to twrp
---------- Post added at 07:10 AM ---------- Previous post was at 06:43 AM ----------
Rooted my phone at last using Magisk. Finally!
Magisk Manager confirms that the device is properly rooted and I have backed it up by using Root Checker Basic and by
Thank you very much.
I am wondering however what are the differences between PHH and Magisk, it seems that Magisk is more popular so I strongly went for that first. Being someone who only knows SuperSU, how do these installers differ?
At this point do I still need to install the patched-root-boot and no-verity-no-encryption? I have installed no-verity-no-encryption before doing the root.
Click to expand...
Click to collapse
Magisk and phh are both open source.
You don't need the root patch. If you want to keep your data unencrypted then you will need to flash the no-verity-no-encrypt_ashyx patch.
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 ??
TWRP 3.1.1-0 Released
May 19, 2017
TWRP 3.1.1-0 is out now for all currently supported devices.
{
"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"
}
What's new in 3.1.1-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.
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)
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
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 vesrion .or above
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:
[MOD EDIT] Link removed
If you already have custom twrrp recovery to a lower version put img file from link below on your external sdcard and flash with flashify ap from play store or directly from Twrp with Install Image and tap recovery
[MOD EDIT] Link removed
To Root:
Chainfire SUPERSU v2.82
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
or MAGISK 13.3 and magisk manager 5.1.1.
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
XDA:DevDB Information
TWRP recovery for the Galaxy A5 2017 Exynos7880, Tool/Utility for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
vocoderism, ashyx
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2017-07-28
Created 2017-07-28
Last Updated 2017-07-28
Thanks !! ??
Works?
Inviato dal mio SM-A520F utilizzando Tapatalk
Thank you.
are u building any device trees for exynos7880 of lineage os
im oves786
j7 2016 tw developer
Oves786 said:
are u building any device trees for exynos7880 of lineage os
im oves786
j7 2016 tw developer
Click to expand...
Click to collapse
Not yet but device tree that I will use is for aosp like a5x6
Inviato dal mio SM-A520F utilizzando Tapatalk
vocoderism said:
Not yet but device tree that I will use is for aosp like a5x6
Inviato dal mio SM-A520F utilizzando Tapatalk
Click to expand...
Click to collapse
i hav j7 2016 im a tw developer
j7 2016 has exynos7870 and urs has exynos7880 and both processors are same just clock at 1.9 and different radio band rest all are of exynos7870
You have device tree?to port?You mean exynos7850?
Inviato dal mio SM-A520F utilizzando Tapatalk
Hi
installed your twrp by .img file coz I had already a previous version
seems all. ok
I'll try to flash a beta Custom ROM just. now through your TWPR
thanks
Thx.It can work on A520K
I installed TWRP but can't install viper4Android. Anyone else? Having issues?
Hi @vocoderism
Have you switched phone from A510 to A520 now?
Sent from my SM-A310F using Tapatalk
Sure development for a520 a510 broken
Sent from my Nexus 7 using Tapatalk
Is it possible to just boot and not flash the recovery?
Many thanks, works a treat. I finally have a TWRP backup.
Great job! everything is working like a miracle!
At first MTP & ADB didn't worked for me (Windblows 10 Creators update build ver. 10.0.15064), but after a lot of trials and errors I've finally managed to get It working.
Rockchip drivers Here
Thanks again.
vocoderism said:
TWRP 3.1.1-0 Released
May 19, 2017
TWRP 3.1.1-0 is out now for all currently supported devices.
What's new in 3.1.1-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.
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)
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
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 vesrion .or above
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.1-0_sm-a520_odin
If you already have custom twrrp recovery to a lower version put img file from link below on your external sdcard and flash with flashify ap from play store or directly from Twrp with Install Image and tap recovery
twrp_3.1.1-0_sm-a520_img
To Root:
Chainfire SUPERSU v2.82
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
or MAGISK 13.3 and magisk manager 5.1.1.
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
XDA:DevDB Information
TWRP recovery for the Galaxy A5 2017 Exynos7880, Tool/Utility for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
vocoderism, ashyx
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2017-07-28
Created 2017-07-28
Last Updated 2017-07-28
Click to expand...
Click to collapse
succsfully installed in my a520f/ds..but when creating a back up it says in the end "failed to mount /data (Invalid argument)"..how can i fix this...?i want to create back up before doing anything else...i also got 0md reading for my internal storage...
this what i dis on creating back up
* reboot to recovery mode
*it boots to twrp..and there is a question if i want to allow modification then swipe but i didnt i only checked read only
*then i go to backup then i start creating backup
after a while it almost done and then it says "failed to mount /data (Invalid argument)"...thats what it says...i dont created a back up..please help me
ryzel said:
succsfully installed in my a520f/ds..but when creating a back up it says in the end "failed to mount /data (Invalid argument)"..how can i fix this...?i want to create back up before doing anything else...i also got 0md reading for my internal storage...
this what i dis on creating back up
* reboot to recovery mode
*it boots to twrp..and there is a question if i want to allow modification then swipe but i didnt i only checked read only
*then i go to backup then i start creating backup
after a while it almost done and then it says "failed to mount /data (Invalid argument)"...thats what it says...i dont created a back up..please help me
Click to expand...
Click to collapse
You have to decrypt your device first. follow the procedure in this thread:
https://forum.xda-developers.com/sa.../samsung-sm-a520f-2017-kernel-source-t3557622
tsarig said:
You have to decrypt your device first. follow the procedure in this thread:
https://forum.xda-developers.com/sa.../samsung-sm-a520f-2017-kernel-source-t3557622
Click to expand...
Click to collapse
I'm having a similar issue. got up to:
Turn the phone off
Hold power + home button and volume up to enter the recovery .
Dont swipe to allow modifcations!! use read only!
Flash Supersu and after that reboot to android.
Also download the No-verity-no-encrypt Patch made by Ashyx and put it on your sdcard ( not internal )!!!
https://www.androidfilehost.com/?fid=24591000424951049
I'm guessing installing no-verify-no-encrypt patch is the decrypt? How do I install it (read only, allow modifications?). My phone is now rooted due to previous steps, but I still get the failed to mount message.
y2klol said:
I'm having a similar issue. got up to:
Turn the phone off
Hold power + home button and volume up to enter the recovery .
Dont swipe to allow modifcations!! use read only!
Flash Supersu and after that reboot to android.
Also download the No-verity-no-encrypt Patch made by Ashyx and put it on your sdcard ( not internal )!!!
https://www.androidfilehost.com/?fid=24591000424951049
I'm guessing installing no-verify-no-encrypt patch is the decrypt? How do I install it (read only, allow modifications?). My phone is now rooted due to previous steps, but I still get the failed to mount message.
Click to expand...
Click to collapse
WARNING: You must backup your data first. this procedure will wipe your data. (As instructed in the link I've attached, just read it and follow carefully).
Flash the dm-verity patch as any other zip.
After you flash the dm-verity patch you'll have to format your phone, otherwise, your phone will never get decrypted. to do so, in TWRP you must choose wipe>format data. then it asks you to type 'yes' for safety measures, just type yes and that's It.