Database Develop

[RECOVERY][m8whl] TWRP 3.1.1-0 touch recovery [2017-05-19]

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.
CHANGELOG for 3.0.2-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
CHANGELOG for 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: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (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
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.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
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
OR:
You can find more information and download links on our website.
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.

Reserved
Based on the work and assistance of @simonsickle so thanks very much to him.
Device specific page on our website.
Download link to current and past versions

Thanks for this!

Thanks @Dees_Troy and @simonsickle!
~Jflteusc on OctOS
KToonsez Kernel
1.998 Max ¦ 189 Min ¦ 702 Screen Off
Ktoonsified v5 Setup

Okay. I'm brain dead. Post says 2.7.0.0.
Link has 2.7.0.2 as latest.
Sorry. Been up since 2am.

Thanks guys
Sent from my SM-N900P using XDA Premium HD app

Is it possible to post a recovery flashable zip...for this recovery?
Sent from my 831C using Tapatalk

asafegous said:
Is it possible to post a recovery flashable zip...for this recovery?
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
I used the terminal emulator install method. You can cut and paste the command line right from the twrp site. Very quick and easy.
Sent from my 831C using Tapatalk

Sweet! Now all I need to see is an RUU for emergency's and ARHD support for Sprint before I pick this phone up on Sprint's network :angel::good:

No answer? Is it a typo?

mcwups1 said:
No answer? Is it a typo?
Click to expand...
Click to collapse
02 would be the latest, 2.700 Is the stable version.
Sent from my gunmetal sexbox

Yay, finally the official post has arrived!

Still don't know which to install.
OP states 2.7.0.0 is stable, but the date is 4/14, which doesn't match any in the link. The only one close to that date is the 2.7.0.2 version, but still isn't the exact date.
The OP and the links don't match.

2.7.0.2 wasn't stable for me. Back on capt.'s 2.7.0.5.
Sent From My HTC One (M8)

mcwups1 said:
Okay. I'm brain dead. Post says 2.7.0.0.
Link has 2.7.0.2 as latest.
Sorry. Been up since 2am.
Click to expand...
Click to collapse
I think this thread just has not been updated with 2.7.0.2 I'm running 2.7.0.2 from the link posted.
---------- Post added at 12:29 AM ---------- Previous post was at 12:28 AM ----------
Rydah805 said:
2.7.0.2 wasn't stable for me. Back on capt.'s 2.7.0.5.
Sent From My HTC One (M8)
Click to expand...
Click to collapse
What wasn't stable? seems ok to me.

Yea Idk y it got labeled 0 when 2 was the latest "official", but nothing wrong with additions cap has added to make it .5. Have been running that through the Mills and have seen reason those additions shouldn't be push to official soure
~m8whl modded stock
2.265 Max ¦ 300 Min
ondemand
row

MassStash said:
Yea Idk y it got labeled 0 when 2 was the latest "official", but nothing wrong with additions cap has added to make it .5. Have been running that through the Mills and have seen reason those additions shouldn't be push to official soure
~m8whl modded stock
2.265 Max ¦ 300 Min
ondemand
row
Click to expand...
Click to collapse
Because those patches, while they may work fine on our device, may not work well (or at all) on others. Even worse, they could break functionality on other devices. Thus the need for complete and proper testing prior to such features being merged.

So, would your recovery (2.7.0.7) be the best to use for now?
I figure you wouldn't run it if it didn't include everything.

mcwups1 said:
So, would your recovery (2.7.0.7) be the best to use for now?
I figure you wouldn't run it if it didn't include everything.
Click to expand...
Click to collapse
If you're having issues with this one, then yes, mine is another option.

Is the Aroma touch issue fixed in this version?
Sent from my 831C using xda app-developers app

[RECOVERY][p880] TWRP 3.1.1-0 touch recovery [2017-05-19]

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.
CHANGELOG for 3.0.2-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
CHANGELOG for 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: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (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
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.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
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
OR:
You can find more information and download links on our website.
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.

Device page with manual instructions on our website.
Download folders with prior versions:
Mirror 1
Mirror 2
Thanks to Adam77Root for supporting the p880 in OmniROM and helping to make TWRP official for this device!

Hey Dees_Troy happy to see you here.
Thanks for the always awesome work.
Salut
Sent from my LG-V500 using Tapatalk

Great thx seems you are on Androidpolice congrats Dees_Troy and Adam77root

thanks to Dees_Troy and Adam77root for the official support of twrp for P880 ! :highfive:
great recovery.:good:

Why is there no f2fs support?

sprite048 said:
Why is there no f2fs support?
Click to expand...
Click to collapse
you be of good cheer. they just started working.
---edit---
How do you know that no service f2fs?
File openrecovery-twrp-2.7.1.0-p880.img is dated 2014-07-21 so it is current with changes in version 2.7.1.0
You carefully read the changelog for this version in the first post.

What?
srsly. "If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added."

Installed it and working good. Please add support for f2fs file sytem...:good:

ze7zez said:
you be of good cheer. they just started working.
---edit---
How do you know that no service f2fs?
File openrecovery-twrp-2.7.1.0-p880.img is dated 2014-07-21 so it is current with changes in version 2.7.1.0
You carefully read the changelog for this version in the first post.
Click to expand...
Click to collapse
Since it's based on an fstab and cannot accept some partitions as auto (like system, cache, data) it won't work with an f2fs installation. IOW, if it's not built with a specific fstab it won't work with f2fs.
It should be noted that unless you are running a massive sql server on your phone or writing copious amounts to data f2fs is about half as fast as ext4.
It's not an improvement in any way and just like with most of the additions that grouper devs add, this isn't an addition that you'll want either.
File systems take decades to mature, in 2024 i'm sure it will be considered either the best or the worst file system for a phone but at this point in time it's meh.
You see, sequential reads is a big deal on a hard drive but not as big as random reads so on an actual hard drive this would be a MASSIVE improvement, on a static memory all reads are sequential and f2fs has half the performance on sequential reads compared to ext4.
The only file system i'm aware of that would be faster is xfs.

IcanhasLG said:
(...) You see, sequential reads is a big deal on a hard drive but not as big as random reads so on an actual hard drive this would be a MASSIVE improvement, on a static memory all reads are sequential and f2fs has half the performance on sequential reads compared to ext4.
The only file system i'm aware of that would be faster is xfs.
Click to expand...
Click to collapse
I see you have the same opinion as the @iodak.
To the opinion referred @Demetris.
I personally think that every technology has its advantages and disadvantages.
Do not always use the best, but the most optimal.
.

@IcanhasLG
You're absolutely right.XFS is a high-end data processing.It can be referred to as the file systems in a file system.
Only so much about it.

there are some reports about a version 2.7.1.1
Is it existing ?
Where is the code and changelog to 2.7.1.0 ?

That's what found :
hat's new in 2.7.1.0:
Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.Various bugfixes to backup and restoreImprovements to USB storage handlingAdded a class to search for files to make finding the correct brightness file automatic in most casesVarious other bugfixes and tweaks
Best regards

TWRP 2.8 rocks. Thanks.?

TWRP 2.8
TWRP 2.8 working fine. Thanks a lot!
I just was not able to flash it through TWRP app and had to use the terminal command:
su
cat /mnt/sdcard/openrecovery-twrp-2.8.0.1-p880.img >/dev/block/mmcblk0p1
sync
The image is in: http://techerrata.com/browse/twrp2/p880

2.8.0.1 works fine. Thanks ! :victory:

I will wait for a MultiROM build from @Adam77Root. Or someone else brings this up...

Fladder72 said:
I will wait for a MultiROM build from @Adam77Root. Or someone else brings this up...
Click to expand...
Click to collapse
It's on the way, will release it soon.

openrecovery-twrp-2.8.1.0-p880.img
working very fine! :good:

[RECOVERY][a11 32bit] TWRP 3.1.1-0 touch recovery [2017-05-19]

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.
CHANGELOG for 3.0.2-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
CHANGELOG for 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: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (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
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.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
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
OR:
You can find more information and download links on our website.
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.

Device specific page on our website including instructions for a manual install
Download folder with current and past versions

WOOHOO!

Dees_Troy said:
Device specific page on our website including instructions for a manual install
Download folder with current and past versions
Click to expand...
Click to collapse
I don't seem to see the 2.8.3.0 build. Am I looking in the wrong place?

plaese 64 bit version too :/

rjmohit said:
I don't seem to see the 2.8.3.0 build. Am I looking in the wrong place?
Click to expand...
Click to collapse
The TWRP Manager app also only offers ver. 2.8.1.0. I guess we don't get 2.8.3.0 yet, but it's nice to see the 510 is officially supported by TWRP.

huggs said:
The TWRP Manager app also only offers ver. 2.8.1.0. I guess we don't get 2.8.3.0 yet, but it's nice to see the 510 is officially supported by TWRP.
Click to expand...
Click to collapse
^^ only the 32bit variant is supported which is a real shame for us in the uk and australia

Inside 4ndroid said:
^^ only the 32bit variant is supported which is a real shame for us in the uk and australia
Click to expand...
Click to collapse
OOps, that might be why I have no recovery now..... Anyone got a dump of the U.K. recovery partition they could send my way.........

Alsajosora said:
OOps, that might be why I have no recovery now..... Anyone got a dump of the U.K. recovery partition they could send my way.........
Click to expand...
Click to collapse
There is no uk stock recovery for 64bit that i know of hence we have no custom recovery... your out of luck until htc release ruu firmware

hi all
i have 510 sid roger , i download the twrp TWRP 3.0.2-0 and i put it in sdcard and reboot to recovery and i select install and image but i can't see recovery just boot ??
is it Wrong ver for my device ?

Samy6699 said:
hi all
i have 510 sid roger , i download the twrp TWRP 3.0.2-0 and i put it in sdcard and reboot to recovery and i select install and image but i can't see recovery just boot ??
is it Wrong ver for my device ?
Click to expand...
Click to collapse
You should be flashing the recovery from a computer like you had to do before with adb..

I downloaded then installed this on my cricket HTC desire 510 with fastboot. And it will not boot this recovery at all. It just goes into a recovery loading boot loop. I am S-on btw

I don't know how active this device is anymore cause I've been moved on for some years now. But I decided to mess around with my old phone.
But here's some feedback, Only Twrp 3.0.2 and below work!
Both 3.1.0 and 3.1.1 boot loop and don't work.
Thank you!

[RECOVERY][lenok] TWRP 3.1.1-0 touch recovery [2017-05-19]

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.
CHANGELOG for 3.0.2-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
CHANGELOG for 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: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (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
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.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
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
OR:
You can find more information and download links on our website.
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.

Device specific page on our website with manual install instructions.
Download links for all current and past versions.

There's no lg g watch r (lenox) available in twrp app. I have latest version of the app. What's wrong?
Sent from HTC One M8 running Viper One

Vi553r said:
There's no lg g watch r (lenox) available in twrp app. I have latest version of the app. What's wrong?
Sent from HTC One M8 running Viper One
Click to expand...
Click to collapse
You will not be able to use the app to flash this because of the way fast boot works. Unless they make a custom watch app to dd flash it.
Sent from my A0001 using XDA Free mobile app

first things first, kudos to tonu42 for posting the unofficial twrp back in december.
sadly, the 2.8.3.0 build somehow screwed up adb for me - but now with the official 2.8.4.0 and that "powerbutton to go back" functionality...just swell

eeermm....I just flashed the twrp recovery and now when I restart, it always goes into recovery. I can't seem to get to boot.
is this normal?

b0gd4n said:
eeermm....I just flashed the twrp recovery and now when I restart, it always goes into recovery. I can't seem to get to boot.
is this normal?
Click to expand...
Click to collapse
No it isn't normal. I flashed yesterday and haven't experienced this problem, you did flash recovery right? How are you trying to reboot btw?

TimmyUK said:
No it isn't normal. I flashed yesterday and haven't experienced this problem, you did flash recovery right? How are you trying to reboot btw?
Click to expand...
Click to collapse
yeah, so I booted in fastboot and did fastboot flash recovery open....zip
twrp works nice, but when I choose reboot system it starts recovery again.
I am also getting mounting errors (unable to mount data and storage).
EDIT: also, in twrp the Internal Storage is appearing as 0MB

b0gd4n said:
yeah, so I booted in fastboot and did fastboot flash recovery open....zip
twrp works nice, but when I choose reboot system it starts recovery again.
I am also getting mounting errors (unable to mount data and storage).
EDIT: also, in twrp the Internal Storage is appearing as 0MB
Click to expand...
Click to collapse
Symptoms don't sound good. You may have to re-flash the system/software from one of the other threads. Maybe worthwhile re-flashing the previous ver of TWRP?

TimmyUK said:
Symptoms don't sound good. You may have to re-flash the system/software from one of the other threads. Maybe worthwhile re-flashing the previous ver of TWRP?
Click to expand...
Click to collapse
yeah, I'm gonna try following this thread http://forum.xda-developers.com/g-watch-r/development/emergency-guide-how-to-blank-regenerate-t2984678
I'll try another twrp now.

TimmyUK said:
Symptoms don't sound good. You may have to re-flash the system/software from one of the other threads. Maybe worthwhile re-flashing the previous ver of TWRP?
Click to expand...
Click to collapse
ok...so flashing previous version of twrp did not work, same problem with unable to mount.
now, this is weird. I flashed stock recovery, and the watch started straight away...

b0gd4n said:
ok...so flashing previous version of twrp did not work, same problem with unable to mount.
now, this is weird. I flashed stock recovery, and the watch started straight away...
Click to expand...
Click to collapse
That is weird, you running 5.0.1?

TimmyUK said:
That is weird, you running 5.0.1?
Click to expand...
Click to collapse
yeah, 5.0.1.
ok, so after I flashed the stock recovery, and restarted the device normally, I adb sideloaded the 5.0.1 update mentioned in the thread posted earlier.
I then flashed the latest twrp again, and it now seems to be all nice and fine. I can boot to twrp, and the stuff gets mounted and I can reboot the system as well.
dunno what, but smth went wrong the first time I flashed.
all fine now.

Really strange, glad you got it sorted.

@b0gd4n
I've had the same problem at first TWRP Flash.
That's why i've posted this guide

Schmurtz1968 said:
@b0gd4n
I've had the same problem at first TWRP Flash.
That's why i've posted this guide
Click to expand...
Click to collapse
erm, which guide?

b0gd4n said:
erm, which guide?
Click to expand...
Click to collapse
The one you've pointed in this Thread

I did bootloader unlock for my watch using fastboot oem unlock
did fastboot flash recovery twrp.img
fastboot reboot.
I do have TWRP but when i press reboot->System it keeps booting to twrp.
I know to properly flash things on my devices but something here is wrong.

anyone got twrp working after flashing wear 5.02 ?

2.8.5.0 works for me on 5.0.2, Supersu FC's after rebooting and attempting installation. I think this is already a known problem. Just need to do a little more digging.
<edit> Updating to the latest (v2.46) has seemed to have resolved my issue

[OFFICIAL] TWRP 3.0.2-2 Recovery for Redmi Note 3 [SnapDragon]

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.
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.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
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:
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
OR:
You can find more information and download links on our website.
Xiaomi Redmi Note 3
TWRP Downloads
NOTE: If you are flashing TWRP for the first time then you need to first flash modified boot.img from here and then TWRP
XDA:DevDB Information
Recovery for the Xiaomi Redmi Note 3
Contributors
vibhu0009
Source Code: https://github.com/TeamWin
Device Tree: https://github.com/TeamWin/android_device_xiaomi_kenzo
Version Information
Status: Stable
Created 2016-04-06
Last Updated 2016-04-06

Special thanks to @Santhosh M

Could you add chinese language please? Thank you

Can we get TWRP Manager app from Google Play store to reference this TWRP version (kenzo)? Will make it easier to flash and apply updates in future.

Does it need to flash cracked boot.img with this official version?

vlado05 said:
Does it need to flash cracked boot.img with this official version?
Click to expand...
Click to collapse
yes.. if u flashing it for the first time then u gotta flash the modified boot.img and then TWRP

_ossie_ said:
Can we get TWRP Manager app from Google Play store to reference this TWRP version (kenzo)? Will make it easier to flash and apply updates in future.
Click to expand...
Click to collapse
It will be up very soon in TWRP manager

vlado05 said:
Does it need to flash cracked boot.img with this official version?
Click to expand...
Click to collapse
Yes, you still need the modded boot.img for respective version of the rom.
---------- Post added at 01:08 PM ---------- Previous post was at 01:06 PM ----------
_ossie_ said:
Can we get TWRP Manager app from Google Play store to reference this TWRP version (kenzo)? Will make it easier to flash and apply updates in future.
Click to expand...
Click to collapse
Definitely it would be easier, with a unlocked BL though.

Thanks

feds64 said:
Yes, you still need the modded boot.img for respective version of the rom.
Click to expand...
Click to collapse
Sorry for the noob Qs and a bit off-topic but can you flash the modded boot.img with TWRP itself? The only way I have been flashing a modded boot.img is via Fastboot.
(I imagine you'd need to convert the boot.img to a flashable zip but I don't know how to do that.
Also, isn't the modded boot.img the very LAST thing to flash? Because every time I have done it differently I have ended up in bootloop/stuck at Mi logo.
The other way I've been restoring boot is via a TWRP backup (boot only) but this requires it to be previously flashed and backed up.

_ossie_ said:
Sorry for the noob Qs and a bit off-topic but can you flash the modded boot.img with TWRP itself? The only way I have been flashing a modded boot.img is via Fastboot.
(I imagine you'd need to convert the boot.img to a flashable zip but I don't know how to do that.
Also, isn't the modded boot.img the very LAST thing to flash? Because every time I have done it differently I have ended up in bootloop/stuck at Mi logo.
The other way I've been restoring boot is via a TWRP backup (boot only) but this requires it to be previously flashed and backed up.
Click to expand...
Click to collapse
In twrp select option of flash images, and then it will show the image file, select and flash it.

Hey,
I just tried this Recovery & as of now it is not able to flash MIUI zip files! Earlier Chinese recoveries were able to flash full zips at least! [OTA cant be flashed though]
Edit- Threre is some weird error as - Failed to mount '/factory' (Invalid argument)

TheDj408 said:
Hey,
I just tried this Recovery & as of now it is not able to flash MIUI zip files! Earlier Chinese recoveries were able to flash full zips at least! [OTA cant be flashed though]
Edit- Threre is some weird error as - Failed to mount '/factory' (Invalid argument)
Click to expand...
Click to collapse
Doesn't effect anything.. But new build is coming soon with this error fixed..

vibhu0009 said:
Doesn't effect anything.. But new build is coming soon with this error fixed..
Click to expand...
Click to collapse
thanks @vibhu0009 for all your hard work
really appreciate it

oficial twrp fr my rn3
omg
thnkz @vibhu0009
gona try it right awy

I Think you remove
/factory ext4 /dev/block/bootdevice/by-name/factory

_ossie_ said:
Sorry for the noob Qs and a bit off-topic but can you flash the modded boot.img with TWRP itself? The only way I have been flashing a modded boot.img is via Fastboot.
(I imagine you'd need to convert the boot.img to a flashable zip but I don't know how to do that.
Also, isn't the modded boot.img the very LAST thing to flash? Because every time I have done it differently I have ended up in bootloop/stuck at Mi logo.
The other way I've been restoring boot is via a TWRP backup (boot only) but this requires it to be previously flashed and backed up.
Click to expand...
Click to collapse
Alternatively you can, always keep these two files together in you device as you may need it for OTA or etc.
---------- Post added at 03:21 PM ---------- Previous post was at 03:19 PM ----------
Thanks for the quick fix...

When is the new build with /factory mount error fix?

DrWillz said:
When is the new build with /factory mount error fix?
Click to expand...
Click to collapse
i gues u did not see the change of name of thread
it was fixd and released 3-4 hours bak by @vibhu0009
take links from frst page
---------- Post added at 05:15 PM ---------- Previous post was at 05:14 PM ----------
feds64 said:
Alternatively you can, always keep these two files together in you device as you may need it for OTA or etc.
---------- Post added at 03:21 PM ---------- Previous post was at 03:19 PM ----------
Thanks for the quick fix...
Click to expand...
Click to collapse
+1
thanks for the quick fix...

First of all thank you very much for your hard work on twrp. It's really amazing. I suppose that release 3.0.2-1 is not yet finished! I cannot see any link for this version, just 3.0.2-0.