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
This build should work for a5dug, a5ul, and a5u variants.
Device page on our website with instructions for a manual install.
Download page with current and previous versions.
Thanks to jmztaylor for porting TWRP and making it officially supported on the Desire 816!
thnx for thew awesome work keep supporting this awesome device :good:
Dees_Troy said:
This build should work for a5dug, a5ul, and a5u variants.
Device page on our website with instructions for a manual install.
Download page with current and previous versions.
Thanks to jmztaylor for porting TWRP and making it officially supported on the Desire 816!
Click to expand...
Click to collapse
Official support...!!!!! Awesome...
Thanks a lottttttttt....
But con you confirm for A5DWG?
jithumon said:
Official support...!!!!! Awesome...
Thanks a lottttttttt....
But con you confirm for A5DWG?
Click to expand...
Click to collapse
does the DWG have a different partition layout than the other? if not then it will work
jmz said:
does the DWG have a different partition layout than the other? if not then it will work
Click to expand...
Click to collapse
I think its same....Unofficial port was working well.
jithumon said:
I think its same....Unofficial port was working well.
Click to expand...
Click to collapse
I can't download from official page...can you upload to other web?
calors said:
I can't download from official page...can you upload to other web?
Click to expand...
Click to collapse
Dude.... Ask dev's not me...
I'm not the developer.
calors said:
I can't download from official page...can you upload to other web?
Click to expand...
Click to collapse
See link below.
https://docs.google.com/file/d/0ByTAJ7v5eoN7bFN2R21kbTAwTE0/edit?usp=docslist_api
support single sim ?
support single sim ?
There is no 'a5' in TWRP manager(phone list)
ajeshmanu said:
There is no 'a5' in TWRP manager(phone list)
Click to expand...
Click to collapse
Same prob here..
Thanks for the update to 2.8 ..
But, MTP is not working..
With the a5ul the touch does not work you can choose to install but then do not go back and if it freezes you can not unlock
Sent from my HTC Desire 816 Single sim using XDA Free mobile app
my bro got this HTC 816 dual sim what its name A5 ? is it supported ?
its important to me whats name of dual sim version of it to download and flash or not
swipe to unlock not function. I am stuck there. What should I do to solve this problem?
smartzac said:
swipe to unlock not function. I am stuck there. What should I do to solve this problem?
Click to expand...
Click to collapse
Are you on single sim? If so, there's a lot of problems like this on single sim. If not, just disable the screen lock feature in TWRP settings.
FoxyDrew said:
Are you on single sim? If so, there's a lot of problems like this on single sim. If not, just disable the screen lock feature in TWRP settings.
Click to expand...
Click to collapse
Yes I am on 816x single sim. The back button also not function.
smartzac said:
Yes I am on 816x single sim. The back button also not function.
Click to expand...
Click to collapse
Then this TWRP isn't for your phone. Re-flash CWM.
FoxyDrew said:
Then this TWRP isn't for your phone. Re-flash CWM.
Click to expand...
Click to collapse
Already flash back to CWM again.
Related
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.
Ahh I'm in heaven now. I flashed it using goo manager. One click and it was installed in like 2 minutes. Thanks for this recovery. Best imo
1st! ... Q...
What if I have an existing CWM recovery, can I just flash this blob over on top of it with fastboot or will I need to flash back to stock recovery?
TheExpertNoob said:
1st! ... Q...
What if I have an existing CWM recovery, can I just flash this blob over on top of it with fastboot or will I need to flash back to stock recovery?
Click to expand...
Click to collapse
It'll overwrite CWM.
Awesome .
Q: Does the File System Size Check takes that long ?
Sent using Chanook 300
awww snap. thank you so much for this!
Thanks so much! I will definitely jump on when external SD is supported.
thx
Glad to see this ported to our tf300...and easy to install with goo manager!
Very nice Thanks a bunch.
We pushed out an update to v. 2.1.5 to fix a bug with zip installs, please update via the website or goo manager.
Woot awesome! Thanks for the update.
Sent from my ADR6300 using Tapatalk 2
Must admit that I wasn't keen on installing a different recovery image but as CWM isn't restoring my kernels between standard rom and CM9 I thought I'd give it a go.
So far so good.
Waiting for build 3 of CM9 to properly test it.
Is there any real advantage to using TWRP instead of CWM? Or is it just a personal preference?
camblue said:
Is there any real advantage to using TWRP instead of CWM? Or is it just a personal preference?
Click to expand...
Click to collapse
CMW isnt restoring kernels so its a right ball ache to revert the tablet to standard again.
And if you are testing CM9 nightly and then changing back its too much.
TWRP says it can fully restore my standard image after testing CM9.
Hmmm might have to give it a whirl and give up my long standing relationship with CWM.
Northern-Loop said:
CMW isnt restoring kernels so its a right ball ache to revert the tablet to standard again.
And if you are testing CM9 nightly and then changing back its too much.
TWRP says it can fully restore my standard image after testing CM9.
Click to expand...
Click to collapse
camblue said:
Hmmm might have to give it a whirl and give up my long standing relationship with CWM.
Click to expand...
Click to collapse
Yeah I was the same but seems alright - Big test will be the next CM9 build.
---------- Post added 26th May 2012 at 12:10 AM ---------- Previous post was 25th May 2012 at 11:26 PM ----------
Seems we can't delete backups inside recovery? Is it okay to delete them in a file manager?
Not sure what's up, maybe kernel version still not being restored properly, but Wi-Fi still doesn't work when restoring back to a stock ROM from CM9.
Berzerker7 said:
Not sure what's up, maybe kernel version still not being restored properly, but Wi-Fi still doesn't work when restoring back to a stock ROM from CM9.
Click to expand...
Click to collapse
Go into settings then about and see what it says about kernel, post details here.
Did you flash build 1 or 2? Should be fixed in build 2 of CM9
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Northern-Loop said:
Go into settings then about and see what it says about kernel, post details here.
Did you flash build 1 or 2? Should be fixed in build 2 of CM9
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Click to expand...
Click to collapse
I have the same issue and I used build 2.. When restoring back, even from trwp backup,
Kernel 2.6.39.4_cm9-ga1dbdc6
[email protected]#1
It's looks to be retaining th kernel..
Very slow as well.. Did I miss something in my backup process?
Sent from my iPad using Tapatalk HD
Server is taking too long to respond
I'll try again later...
EDIT: Finally got the Blob and flashed it through Terminal
Currently backing up the stock ROM before testing out CM9 Build 3!
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
Device page on our website with instructions for a manual install.
Link to download.
Mirror
Fantastic work, as always, @Dees_Troy. It's always nice to see (official) TWRP on new (and dev-friendly) devices. I've posted this to the XDA Portal.
This is fantastic! It couldn't have come at a better time. So many things to flash... :highfive:
Anyone happen to have the stock recovery? TWRP works great for flashing all the things, except the stock CM ROM. I know, I know, I didn't make a backup. I'm a baddie.
rayfin said:
Anyone happen to have the stock recovery? TWRP works great for flashing all the things, except the stock CM ROM. I know, I know, I didn't make a backup. I'm a baddie.
Click to expand...
Click to collapse
Try the attached test build
It's almost identical but was built from a 4.3 tree instead of 4.4, which resolves the issues with 4.4 recoveries flashing older update-binaries
(For complete source, look at the android-4.3 branches of the oppo n1 on omnirom along with a few patches to the 4.3 n1 branch on omni gerrit - note that the 4.3 device tree is ONLY intended to support recovery building and nothing else.)
Entropy512 said:
Try the attached test build
It's almost identical but was built from a 4.3 tree instead of 4.4, which resolves the issues with 4.4 recoveries flashing older update-binaries
(For complete source, look at the android-4.3 branches of the oppo n1 on omnirom along with a few patches to the 4.3 n1 branch on omni gerrit - note that the 4.3 device tree is ONLY intended to support recovery building and nothing else.)
Click to expand...
Click to collapse
Hehe This is who you worked with last night. Thanks again for all of your work last night
rayfin said:
Hehe This is who you worked with last night. Thanks again for all of your work last night
Click to expand...
Click to collapse
LOL. Didn't mouseover your G+ link...
Entropy512 said:
LOL. Didn't mouseover your G+ link...
Click to expand...
Click to collapse
Can i just flash 2700 in recovery , i am on 2630.. Thank you
Entropy512 said:
LOL. Didn't mouseover your G+ link...
Click to expand...
Click to collapse
Can i just flash 2700 in recovery , i am on 2630.. Thank you
giuliano rigon said:
Can i just flash 2700 in recovery
Click to expand...
Click to collapse
You can't flash a recovery while you're in recovery.
You can use Goo Manager, Flashify, or other apps of that nature to flash it while System is booted. Or you can boot into bootloader and flash recovery that way. I downloaded the recovery image and flashed it with Flashify.
hey guys
my friend bought me a n1 from china..
i don't like color os then i decide install pac-man rom
today i flash last version of twpr recovery with out any error
C:\adb>fastboot flash recovery openrecovery-twrp-2.7.0.0-N1.img
sending 'recovery' (7580 KB)...
OKAY [ 0.267s]
writing 'recovery'...
OKAY [ 0.387s]
finished. total time: 0.657s
but when i enter to recovery ''vol down + power''
i faced to stock recovery !!
my installation wasn't success?
it's possible to flash any custom rom with stock recovery ?
If you have rooted color os try using flashify to flash a recovery
Sent from my N1 using XDA Premium 4 mobile app
trialsrider1 said:
If you have rooted color os try using flashify to flash a recovery
Sent from my N1 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thanks for replay
yes i did same as your way
flash root and su from stock recovery and install recovery tools
:fingers-crossed:
TWRP Manager crash when I try to use "Install Recovery" on GT-I9100
Hi!
Just to let you know that the latest recovery manager available on Google play store crash when I try to use "Install Recovery" on a Samsung Galaxy S2 GT-I9100.
Regards!
N1 still gets TWRP 3.0.0. cool!
Where is the link for 3.1.1.0? I can only find v.2.8.6.0
Ronii10 said:
Where is the link for 3.1.1.0? I can only find v.2.8.6.0
Click to expand...
Click to collapse
try to check it on their website.
https://twrp.me
cheeze.keyk said:
try to check it on their website.
https://twrp.me
Click to expand...
Click to collapse
I did there's nothing there same with their app
Ronii10 said:
I did there's nothing there same with their app
Click to expand...
Click to collapse
Can yuo help..... cant get rid of from SuperSu my recovery twrp 2.8.6.0 Please .......
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
Device page on our website
Download folders with current and previous versions:
Mirror 1
Mirror 2
someone try to flash supersu ? work ?
Hurray!
Sent from my Nexus 4 using Tapatalk
Nice, now for a million backups.
Sweet! Flashing soon on my friends 1+1
good to see your project keep it up your work
Can anyone please tell me how to buy the one plus one
xXPr0XNinjaXx said:
Can anyone please tell me how to buy the one plus one
Click to expand...
Click to collapse
they do not sell it, they do not need money.
only for fun club available by invitation.
xXPr0XNinjaXx said:
Can anyone please tell me how to buy the one plus one
Click to expand...
Click to collapse
not to be a bad guy but you could just google it and go to their site and all the information is right there... Google is rather helpful :good: :laugh:
Only on the OPO do we get recovery before root. Well done
YoshiFan501 said:
Only on the OPO do we get recovery before root. Well done
Click to expand...
Click to collapse
Because we got root from the start... You'll just have to enable it in settings... Meaning we had root before recovery. We also had unlocked bootloader before recovery.
playya said:
not to be a bad guy but you could just google it and go to their site and all the information is right there... Google is rather helpful :good: :laugh:[/QUOTE
instead of being smart just help .. i was on their site but i wanted to know if there are other ways to buy it without someone to invite me.
instead of posting this dont even post !!!!!!!!!!!!!!1
Click to expand...
Click to collapse
xXPr0XNinjaXx said:
playya said:
not to be a bad guy but you could just google it and go to their site and all the information is right there... Google is rather helpful :good: :laugh:[/QUOTE
instead of being smart just help .. i was on their site but i wanted to know if there are other ways to buy it without someone to invite me.
instead of posting this dont even post !!!!!!!!!!!!!!1
Click to expand...
Click to collapse
Haha I did help by telling you too read my friend. There site is quite helpful and they tell you what you need to know. Help comes in many different ways my friend don't be mad.... Lol
Click to expand...
Click to collapse
playya said:
xXPr0XNinjaXx said:
Haha I did help by telling you too read my friend. There site is quite helpful and they tell you what you need to know. Help comes in many different ways my friend don't be mad.... Lol
Click to expand...
Click to collapse
oki
Click to expand...
Click to collapse
Hmmmm
BACON
Go to oppomart.com
That's where I'm getting mine
Sent from my Nexus 5 using XDA Free mobile app
simo.scorpion said:
someone try to flash supersu ? work ?
Click to expand...
Click to collapse
Yes I am root
Envoyé de mon One en utilisant Tapatalk
Is it right that my 1+1 Sandstone black 64gb first must be unlocked? When i try to flash via fastboot it says phone is locked and cant be flashed.
Gesendet von meinem One mit Tapatalk
m3dd0g said:
Is it right that my 1+1 Sandstone black 64gb first must be unlocked? When i try to flash via fastboot it says phone is locked and cant be flashed.
Gesendet von meinem One mit Tapatalk
Click to expand...
Click to collapse
Yes, you should run "fastboot oem unlock" first.
[RECOVERY] [4/5/16] TWRP 3.2.3-0 - TeamWin Recovery Project
TeamWin is proud to present TWRP 3.2.3-0 for the Samsung Galaxy S6!
Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for new features
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit for TWRP Official Device Configs - http://gerrit.twrp.me
Gerrit Instance - http://gerrit.omnirom.org
If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
zeroflte Device Config: TBD
Kernel: TBD
DOWNLOAD:
All official devices are listed at the top of the page on the Team Win website. Search for the device in the textbox.
http://twrp.me
Support:
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers
Changelog
Please see https://twrp.me for changelogs.
3.0.2-2
- Fix booting on mm
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.
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
3.0.0.1
-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
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 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!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links.
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 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!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links.
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 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!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links.
2.8.7.2
Fix MTP copy/moves.
2.8.7.1
- Unify and fix kernel booting for 5.0.2 and 5.1.1
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)
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.
2.8.6.2
- fix OTG
2.8.6.1
- fix adb
2.8.6.0
- Allow mulitple overlays for popup boxes (Dees_Troy)
- Add pattern style password entry for decrypt (Tassadar)
- Keyboard improvements (_that)
- Update AOSP base to 5.1 (Dees_Troy)
- Reduce theme count to 5 and rely on scaling (Dees_Troy)
- Various scaling improvements (Dees_Troy)
- Improved handling of resources in the GUI (_that)
- Make scroll bar size proportional to list size (_that)
- Allow scoll lists to render without a header (_that)
- Make console scroll per pixel with kinetic scrolling (_that)
- Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
- Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
Fix Deep Sleep from Chainfire:
http://forum.xda-developers.com/showpost.php?p=60383471&postcount=49
This is for the S6 Edge as well?
Project X-Ray said:
This is for the S6 Edge as well?
Click to expand...
Click to collapse
It should work for all S6 devices since they are all using the same SOC.
However the asserts are not working for every device. I am deciding on whether I should use a unified init but I will need lots of help from users for testing etc.
flashed it by odin
mobile running good but not going into recovery
and now it is stuck boot when pressed vol+ and menu and power to go in recovery
G920F
Project X-Ray said:
This is for the S6 Edge as well?
Click to expand...
Click to collapse
Unfortunatly it doesn't work on my edge(SM-G925F), boots in to recovery but the screen is all messed up, just shades of green,
Thanks for porting this ! cant wait till it works on the edge.
a0007 said:
flashed it by odin
mobile running good but not going into recovery
and now it is stuck boot when pressed vol+ and menu and power to go in recovery
G920F
Click to expand...
Click to collapse
Can you get /proc/last_kmsg please?
bigbiff said:
Can you get /proc/last_kmsg please?
Click to expand...
Click to collapse
I install new rom by odin without wipe
Last_kmsg
https://app.box.com/s/lccif3dhyfn0gohjwyo3wk868muvub8u
Sent from my SM-G920F
a0007 said:
flashed it by odin
mobile running good but not going into recovery
and now it is stuck boot when pressed vol+ and menu and power to go in recovery
G920F
Click to expand...
Click to collapse
same problem here ,
& TWRP manager app doesn't have the S6 as a supported device ,
& the dd method stuck on boot logo
G920F
tiboric said:
Unfortunatly it doesn't work on my edge(SM-G925F), boots in to recovery but the screen is all messed up, just shades of green,
Thanks for porting this ! cant wait till it works on the edge.
Click to expand...
Click to collapse
@bigbiff - Same issue here.
Samsung just published kernel source code for S6 920 and S6 Edge 925 http://www.androidauthority.com/galaxy-s6-s6-edge-kernel-source-code-600528/
flashed it on g920p
now im stuck in recovery and the touchscreen doesnt work
SM-G925T Galaxy S6 Edge T-Mobile after installing reboot to recovery I get a black screen. I do have access to the SDCard but can't seem to find the recovery.log. OP let me know if I can help I bought this phone to use for development and I can just restore the recovery no problem. Thanks.
PS ADB device is offline.
So it seems the Edge has it's own configuration as well as the F series international.
So far this works only on the International S6 and Tmobile S6 as far as I am aware.
All others will have to be worked on in due time.
Biggest time sinks for me is downloading everything.
If you don't have something working,
1. Get recovery.img from sammobile and post it somewhere fast for me to download for your device
2. Download the kernel src and post it somewhere for me to download
So far I am working on the F series. It might take time to support all devices.
^^are you working on 925F ?
bigbiff said:
So it seems the Edge has it's own configuration as well as the F series international.
So far this works only on the International S6 and Tmobile S6 as far as I am aware.
All others will have to be worked on in due time.
Biggest time sinks for me is downloading everything.
If you don't have something working,
1. Get recovery.img from sammobile and post it somewhere fast for me to download for your device
2. Download the kernel src and post it somewhere for me to download
So far I am working on the F series. It might take time to support all devices.
Click to expand...
Click to collapse
Thanks I have the recovery.img but don't know what the 'src' is sorry, can you help?
zone23 said:
Thanks I have the recovery.img but don't know what the 'src' is sorry, can you help?
Click to expand...
Click to collapse
maybe source code?
Sent from my SM-G920T using Tapatalk
zone23 said:
Thanks I have the recovery.img but don't know what the 'src' is sorry, can you help?
Click to expand...
Click to collapse
The kernel source from samsung open source center.
bigbiff said:
The kernel source from samsung open source center.
Click to expand...
Click to collapse
OK thanks I have them uploading to my dropbox. Can I PM you when its uploaded would that be ok?
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.
PSA: DO NOT restore EFS backups made with TWRP 3.0.2-1 as there is a bug in that version that affects how the backup is made. Backups of EFS made with TWRP 3.0.2-1 are invalid and should be discarded. Also, seriously people, do not restore EFS unless you absolutely know that you need to.
Device specific page including instructions for a manual install
Download links for current and past versions of TWRP
Sweet.
nice can't wait to get my nexus 6p tomorrow
Awesome to see you here!
If someone grabs me a boot.img I can get us working decrypted kernel in about 2 minutes
DespairFactor said:
If someone grabs me a boot.img I can get us working decrypted kernel in about 2 minutes
Click to expand...
Click to collapse
Still need a boot.img?
kingmikel said:
Still need a boot.img?
Click to expand...
Click to collapse
Yes sir
Sent from Nexus 5X in the Despair filled Dark Side
@DespairFactor Here you have them.
http://downloadmirror.co/android/K3/mda89d-boot.img
http://downloadmirror.co/android/K4/mdb08k-boot.img
Note for everybody else: these are stock boot images, not modified ones. For that, look out for DespairFactor's posts.
itskapil said:
@DespairFactor Here you have them.
http://downloadmirror.co/android/K3/mda89d-boot.img
http://downloadmirror.co/android/K4/mdb08k-boot.img
Note for everybody else: these are stock boot images, not modified ones. For that, look out for DespairFactor's posts.
Click to expand...
Click to collapse
Why are we using two? Are devices not getting OTA to the latest build?
Sent from Nexus 5X in the Despair filled Dark Side
DespairFactor said:
Why are we using two? Are devices not getting OTA to the latest build?
Sent from Nexus 5X in the Despair filled Dark Side
Click to expand...
Click to collapse
Um, mdb08k would do. I just thought you might need them, so.. anyway, mdb08k OTA is definitely rolling out, so this only should more than suffice.
DespairFactor said:
Yes sir
Sent from Nexus 5X in the Despair filled Dark Side
Click to expand...
Click to collapse
Here you go. The stock MDB08K boot.img
http://1drv.ms/1OXgbJR
DespairFactor said:
Why are we using two? Are devices not getting OTA to the latest build?
Sent from Nexus 5X in the Despair filled Dark Side
Click to expand...
Click to collapse
They're for the two different variants (MDA89D & MDB08K), so I'm guessing they'll both need to be modified.
kingmikel said:
Here you go.
http://1drv.ms/1OXgbJR
Click to expand...
Click to collapse
Removed verity checks and removed forced encryption, it will be uploaded in this link shortly http://renderserver.net/?dir=devs/DespairFactor/angler
Heisenberg said:
They're for the two different variants (MDA89D & MDB08K), so I'm guessing they'll both need to be modified.
Click to expand...
Click to collapse
The file size is too small for those two
Until we get a modified boot.img from @Chainfire, there's no way to root correct?
kingmikel said:
Until we get a modified boot.img from @Chainfire, there's no way to root correct?
Click to expand...
Click to collapse
I can get it working possibly, just let me get my device tomorrow. Keep in mind I am doing all of this stuff remotely.
kingmikel said:
Until we get a modified boot.img from @Chainfire, there's no way to root correct?
Click to expand...
Click to collapse
Read..... the few posts literally right before yours are discussing this...
Heisenberg said:
Read..... the few posts literally right before yours are discussing this...
Click to expand...
Click to collapse
it may not be that cut and dry, we may need to mod permissions, or disable selinux. I will see when I get my device if this doesn't work by itself.
kingmikel said:
Here you go.
http://1drv.ms/1OXgbJR
Click to expand...
Click to collapse
DespairFactor said:
Removed verity checks and removed forced encryption, it will be uploaded in this link shortly http://renderserver.net/?dir=devs/DespairFactor/angler
The file size is too small for those two
Click to expand...
Click to collapse
It's probably pretty important to note which variant this boot.img came from.
Heisenberg said:
Read..... the few posts literally right before yours are discussing this...
Click to expand...
Click to collapse
@DespairFactor mentioned removing encryption from it, but I think it needs the patched sepolicy for supersu to work.
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
---------- Post added at 11:13 PM ---------- Previous post was at 11:12 PM ----------
Heisenberg said:
It's probably pretty important to note which variant this boot.img came from.
Click to expand...
Click to collapse
Fixed! Thanks