[RECOVERY][jfltexx] TWRP 3.1.1-0 touch recovery [2017-05-19] - Galaxy S 4 i9505 Original Android Development

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

Great!

Works fine now, no splash screen bug, restore/backup, all fine so I can come back to my favorite recovery
GT-I9505 ~ SlimBean

Installed and fully working. thanks!!!

Nice one @Dees_Troy
Sent from my GT-I9505 using XDA Premium 4 mobile app

Great job!
Just tested it on my S4 with device encryption. Unfortunately TWRP isn't prompting me for the decryption password like 2.6.1.0 did, so it can't mount anything.
Is this just a bug, or has device encryption support been removed?

Are the s4 variants going to see some love? :laugh:

caponi said:
Great job!
Just tested it on my S4 with device encryption. Unfortunately TWRP isn't prompting me for the decryption password like 2.6.1.0 did, so it can't mount anything.
Is this just a bug, or has device encryption support been removed?
Click to expand...
Click to collapse
When i was testing for @Dees_Troy i specifically told him that old backups don't always work with this new update, try backing up with encryption and restore it and see if your prompted to type the password
Sent from my GT-I9505 using XDA Premium 4 mobile app

I repacked this recovery for the ATT S4 (I337) and posted it on the ATT s4 thread.
The only issue I can find with this version of TWRP so far is the below:
1: randomly hanged at "Recovery booting..". A simple reboot fixed it and rebooted fine into recovery after battery pull.
I experienced no hangs at TWRP recovery screen as previously.

tried it on new sammy 4.3 mi8 stock... if want install with
goomanager message appears that my device not suppoted

gavin-phelan said:
When i was testing for @Dees_Troy i specifically told him that old backups don't always work with this new update, try backing up with encryption and restore it and see if your prompted to type the password
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My problem is not related to backup and restore. My S4 is encrypted with "Android Device Encryption". For example: CWM recovery does not support this, so it can't mount any of the encrypted partitions. In other words, CWM is useless when using Device Encryption.
However, TWRP 2.6.1.0 is prompting me for the decryption password when i boot into the recovery, so i could flash/backup/restore/etc as if the device is not encrypted. TWRP 2.6.3.1 doesn't prompt me for the decryption password anymore, so it has the same issue as CWM: it can not mount the encrypted partitons and i virtually can't do anything.

As it is related to this post, I will post it here.:
Can anyone please confirm if it is working for AOSP roms as well now? I want to try cyanogenmod 10.1.3.
Many thanks for all your hard work fellas
---------- Post added at 03:06 PM ---------- Previous post was at 03:05 PM ----------
diddsen said:
tried it on new sammy 4.3 mi8 stock... if want install with
goomanager message appears that my device not suppoted
Click to expand...
Click to collapse
I am getting the same message!

There is no .Tar file. Both are img and cant flash via odin.

echohack said:
There is no .Tar file. Both are img and cant flash via odin.
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2

Yeah treid that. Downloaded as zip, then unpack and its a img file.

For those who didnt look in the old thread, here the flashable zip again. But only usable when you are on a custom recovery.

echohack said:
Yeah treid that. Downloaded as zip, then unpack and its a img file.
Click to expand...
Click to collapse
Since your are from Sweden I guess you have a 9505.
You can dl an Odin flashable tar from here

echohack said:
There is no .Tar file. Both are img and cant flash via odin.
Click to expand...
Click to collapse
No, but you could use sgs4 flasher from playstore.
L

I hope that the dev can help me.
Recently i cant reboot again without power cable or usb cable...
When i choose reboot, or phone off and then boot, the phones boots...i get the sammy line, bootanimation is starting...Boom, phones off and keeps rebooting till battery is dead..
Tried everything, full wipe, switched to your recovery..... i worked 1 day, then same again..
Any idea what can bring me the answer/solution?

Related

[RECOVERY][d2tmo] 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.
Cha-Ching, THANK YOU TEAM-WIN! Thanks a Bunch been waiting for an official - will test if SD card slot is working.
UPDATE: Works Great!
Confirmed reading from the sd card. Diddnt try to flash from sd card, but it reads it. And the interface is nice in comparison. All I did was fix permissions and it worked.
Sent from my SG3 using GSM (Team Sonic) + Trinity
http://supercentral.net
Awesome!!! Been using TWRP on my Nook for awhile now. Love it! Thanks for this.
How do u make it back up to ext sdcard? Also anyone know the commands for terminal emulator...thanx in advance
Edit....nvmd figured it very nice ty!
sarni84 said:
How do u make it back up to ext sdcard? Also anyone know the commands for terminal emulator...thanx in advance
Edit....nvmd figured it very nice ty!
Click to expand...
Click to collapse
Mind sharing the info. Thanks.
Sent from a Galaxy far far away
now that this is official can we flash cm9 without changing the script?
cwalker0906 said:
now that this is official can we flash cm9 without changing the script?
Click to expand...
Click to collapse
Yeah, is this able to flash cm9 correctly?
neotoky said:
Mind sharing the info. Thanks.
Sent from a Galaxy far far away
Click to expand...
Click to collapse
It's super easy ! When you click backup, there is two boxes at the bottom saying "Use external SD" and "Use Internal Storage". Use internal is by default.
I was under the impression that TWRP supported adb in recovery, though this version does not seem to work. Is that something that is being worked on, or just not gonna happen?
lumbu said:
I was under the impression that TWRP supported adb in recovery, though this version does not seem to work. Is that something that is being worked on, or just not gonna happen?
Click to expand...
Click to collapse
Worked just fine for me.
mounted /system and pushed a few files successfully.
neotoky said:
Mind sharing the info. Thanks.
Sent from a Galaxy far far away
Click to expand...
Click to collapse
Also to install its even easier. Download goomanager from market its free. Then go into it hit your menu button on phone then hit " install open recovery script" .....it will download and install the latest version (which is this one) for u and as far as using external sd goes for backups. When u hit backup just select external
overground said:
Worked just fine for me.
mounted /system and pushed a few files successfully.
Click to expand...
Click to collapse
Yep, my bad. Needed to install the naked adb drivers instead of the Samsung ones I first installed. Is that what you have installed?
lumbu said:
Yep, my bad. Needed to install the naked adb drivers instead of the Samsung ones I first installed. Is that what you have installed?
Click to expand...
Click to collapse
My adb driver installation for this device was such a nightmare (Win7 64).
This is what finally worked for me (follow the link trail).
http://forum.xda-developers.com/showpost.php?p=27921718&postcount=278
Took the plunge and just flashed CM9 nightly with no problems. Cheers!
Thank you guys, this is much better than the touch CWM!
The SD card option is terrific!
Does flashing this with GooManager trip the flash counter?
hypmatize said:
Does flashing this with GooManager trip the flash counter?
Click to expand...
Click to collapse
Does it matter anymore?
There is already a way to reset the flash counter.
ipaq_101 said:
Does it matter anymore?
There is already a way to reset the flash counter.
Click to expand...
Click to collapse
Yeah true... but why trip it when you don't have to
hypmatize said:
Does flashing this with GooManager trip the flash counter?
Click to expand...
Click to collapse
No, only flashing a non-stock file through Odin increases the flash counter. Nothing you do on your phone, including Mobile Odin, trips the counter.

[RECOVERY][manta] 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
Reserved.
Works for me. Thanks!
Fixed adb and added USB OTG support. I'll be looking to upscale the theme and add decrypt support when I have more time.
Thanks for this, Dees. I'll see to it that one of my writers puts this on the front page.
Dees_Troy said:
Fixed adb and added USB OTG support. I'll be looking to upscale the theme and add decrypt support when I have more time.
Click to expand...
Click to collapse
Forgive my ignorance, but does this also root the device, or do I need to root first?
The ability to backup to OTG USB is excellent - thanks.
Lumsdoni said:
Forgive my ignorance, but does this also root the device, or do I need to root first?
The ability to backup to OTG USB is excellent - thanks.
Click to expand...
Click to collapse
Root after installing TWRP by flashing SuperSU in TWRP.
Awesome thanks just wondering, does this have the random reboot issue like cwm?
Sent from my Galaxy Nexus using Tapatalk 2
draco259 said:
Awesome thanks just wondering, does this have the random reboot issue like cwm?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
It doesn't. This recovery works perfectly, other than the theme issue. CWM has also been fixed by damien667.
Man i LOOVEEE TWRP... thanks for this, cant wait to try it tonight
willverduzco said:
It doesn't. This recovery works perfectly, other than the theme issue. CWM has also been fixed by damien667.
Click to expand...
Click to collapse
Awesome thanks for the info
Sent from my Galaxy Nexus using Tapatalk 2
willverduzco said:
Root after installing TWRP by flashing SuperSU in TWRP.
Click to expand...
Click to collapse
I am confused... how can you give goomanager root access if the tab isn't rooted already?
You can't. You will have to install it through fastboot.
Sent from my GT-N7100 using xda app-developers app
draco259 said:
Awesome thanks just wondering, does this have the random reboot issue like cwm?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I was able to figure out what was needed to prevent the reboot. I pushed my device configuration files to the team win github if you really want to take a look or compile your own. Good news is that I can compile from source without having to repack manually.
Randomwalker said:
You can't. You will have to install it through fastboot.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
ah... ok.. i must have gotten confused when one of the admins said to root it after installing twrp using goomanager..
EDIT: So these direction from post #1 are totally wrong? if randomwalker is correct?
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
That's if you are already rooted, go with the or option.
Sent from my Galaxy Nexus using Tapatalk 2
I installed and got into TWRP fine the first time.Now I'm stuck in a boot loop. It has been sitting for 30 minutes with just the X flashing.
I can get into the bootloader and TWRP fine but the system will not boot just sits with the flashing X..
Mike02z said:
I installed and got into TWRP fine the first time.Now I'm stuck in a boot loop. It has been sitting for 30 minutes with just the X flashing.
I can get into the bootloader and TWRP fine but the system will not boot just sits with the flashing X..
Click to expand...
Click to collapse
Did you just unlock it? If so, reboot into TWRP and go to the wipe section. Format Data & Wipe Cache & you will be good to go.
Same as user above with bootloops. I tried wiping cache/delvik and also factory reset but it says failed everytime in red at the top of TWRP. Im lost. Does the same with stock CWM Touch also. I downloaded the pre rooted factory rom but cannot access sd through mounting to flash that rom either. An ideas as far as sending the file to sd using adb commands?

[RECOVERY][jfltetmo] 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!
Thank you sir!
:laugh:
---------- Post added at 10:43 PM ---------- Previous post was at 10:39 PM ----------
I'm getting no recoveries found for device...
---------- Post added at 11:06 PM ---------- Previous post was at 10:43 PM ----------
Got the tar from goo thx
Working fine!
Sent from my SGH-T889 using Tapatalk 2
This is great.
awesome
It just keeps getting better and better Is it fine if I just install it from the Goo app even though i'm on stock recovery but rooted?
whytechapel_x said:
It just keeps getting better and better Is it fine if I just install it from the Goo app even though i'm on stock recovery but rooted?
Click to expand...
Click to collapse
That's what I did - worked just fine.
will also work if your on the cwm based recovery in the other development forum, before anyone asks.
this weekend we will probably see a crap load of roms released
That was quick. Awesome.
Great job. And confirmed working with 64-gb SD.
Thanks.
Sent from my SGH-M919 using xda premium
thx
Awesome - was waiting for this with baited breath.
Any reason why i cant flash this directly into place with odin, then dump superusersu 1.25 into place?
Their recommended method of app install on a rooted device requires an odin step, or a root exploit anyways - and I'd rather go direct - just too chicken $h1t to be first.
======Edit========
Found my huevos and did it
perfect install
stock -> odin twrp 2.5 -> reboot recovery -> superusersu1.25.zip -> twrp fix perms -> reboot -> golden
and now restoring crap via TiBkup, then debloating.
First & only Recovery that works on my Tmob GS4
I had to wait 3 WHOLE DAYS with my newest toy before I could make even one backup
because the stock 3e is a tiny worthless tool and that rainbow text thing was so tiny. Agat63
and I worked together for a few hours but even though he has one of his great recovery tools
working on the Sprint GS4, couldn't get it to even load via ODIN on my Tmob GS4.
Then like a gift from above, TWRP appeared on this forum.
Downloaded Goo from app store, followed the OP and in seconds ... MAGIC!
Bottom Line: This recovery is fantastic on my SGH-M919 and made
my first full backup without a hiccup.
Thank you TEAMWIN !
Glenn
weltwon said:
that rainbow text thing was so tiny
Click to expand...
Click to collapse
That's been fixed EDIT: pretty much always; OUDHSR is not only bigger and not "rainbow" unless you want it, but touch-enabled.
Dees, thanks for the official port! Options are great.
I can confirm flashing directly with Odin works. I am not rooted yet but plan on flashing SuperSU next after a backup.
What should I include when doing a backup? Recovery? EFS?
Wow, things are coming along quickly. Installed in minutes and crated a backup. Thanks!
Sent from my SGH-M919 using Tapatalk 2
k0nane said:
That's been fixed since 1:52pm CST today; OUDHSR is not only bigger and not "rainbow" (again, blame Shabby!) unless you want it, but touch-enabled.
Dees, thanks for the official port! Options are great.
Click to expand...
Click to collapse
actually it was fixed the night it was released, hence why you posted afterwards saying to redownload if you wanted bigger text...
shabbypenguin said:
actually it was fixed the night it was released, hence why you posted afterwards saying to redownload if you wanted bigger text...
Click to expand...
Click to collapse
Well, that, too.
I ran a backup as soon as I installed..Everything went smooth...I checked to see if the file was saved to either phone or extsd, was saved to phone at 2.4GB..
I moved the file to my extsd just for storage...Now if I want to do a restore im sure I have to move the file back to phone...or do I?
Secondly is there a way or will there be a way to save to extsd?
Thnx....
DISREGARD POST!!!!!!!!!!!!!
I went back into TWRP after I posted and found where I can save to extsd.... Oooppss..But im learning..lol
SBERG117 said:
I ran a backup as soon as I installed..Everything went smooth...I checked to see if the file was saved to either phone or extsd, was saved to phone at 2.4GB..
I moved the file to my extsd just for storage...Now if I want to do a restore im sure I have to move the file back to phone...or do I?
Secondly is there a way or will there be a way to save to extsd?
Thnx....
Click to expand...
Click to collapse
There is, when you go to backup there is a little bar that says internal storage. Click that and you can choose your ext sdcard, internal or one other thing. I forgot what...
Sent from my HTC One X using xda premium
So there's a build of cyanogenmod up on goomanager if any of you feel flash happy and risky
Sent from my SGH-M919 using xda app-developers app

[RECOVERY][minnow] 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 current and past versions.
Its worth noting this uses the 240240 theme moved to fit, it works great and only issues are the nav bar button presses, the power button is now the back button so you can use that if its annoying to hit back/home.
Thanks, @Dees_Troy, but on 2.8.5.0, the theme is way too small. I have a feeling that it's not using the right theme or something.
Need to find an easy way to get to recovery without using the usb jig kit. Grabbed one apk that was supposed to reboot to all methods, but buttons do nothing.
SchmilK said:
Need to find an easy way to get to recovery without using the usb jig kit. Grabbed one apk that was supposed to reboot to all methods, but buttons do nothing.
Click to expand...
Click to collapse
Adb reboot recovery
SchmilK said:
Need to find an easy way to get to recovery without using the usb jig kit. Grabbed one apk that was supposed to reboot to all methods, but buttons do nothing.
Click to expand...
Click to collapse
I made an app to reboot to recovery (needs your watch to be rooted, though).
r3pwn said:
I made an app to reboot to recovery (needs your watch to be rooted, though).
Click to expand...
Click to collapse
I ended up finding one on playstore and it worked. Wish there were some packages to flash for updates other than just supersu.zip...Yesterday I had to revert to stock because my screen was covered with 'update available'. It wasn't until after I restored that I had the idea to modify build.prop to say 5.0.2, which ended up working for some.
SchmilK said:
I ended up finding one on playstore and it worked. Wish there were some packages to flash for updates other than just supersu.zip...Yesterday I had to revert to stock because my screen was covered with 'update available'. It wasn't until after I restored that I had the idea to modify build.prop to say 5.0.2, which ended up working for some.
Click to expand...
Click to collapse
I have the CM12 bootanimation installed on my Moto360 and am debating making it a zip flashable in TWRP. Would you like it?
Reboot to Recovery
r3pwn said:
I made an app to reboot to recovery (needs your watch to be rooted, though).
Click to expand...
Click to collapse
Would you be able to share the apk for reboot to recovery? Thanks in advance!
5.1.1 Stock recovery reflashing
It looks like our device would try to reflash stock recovery image after booting to OS on 5.1.1(at least it did so on 2.8.6.0). Is there any solution?
Does the twrp void the warranty?

[RECOVERY][clark] TWRP 3.2.3-1 Touch Recovery [2018-12-22]

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.2.3-0:
-Fix automatic installing of OTA zips on encrypted devices
-Remove SuperSU from TWRP
-Support both md5 and md5sum file extensions when doing MD5 checking for zip files
CHANGELOG for 3.2.2-0:
-adb backup fixes
-OTA style update zips will now install automatically without prompting for decrypt
-minor tweaks to handling date/time on Qualcomm devices
-updates to some language translations
CHANGELOG for 3.2.1-0:
-minui fixes (cryptomilk)
-Better android-8.0 compatibility in ROM trees (Dees_Troy)
-Fix missing library in android-8.0 (nkk71)
-Fix inconsistent SDCard naming (DevUt)
-Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
CHANGELOG for 3.1.1-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!
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:
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.[/QUOTE]
XDA:DevDB Information
TWRP, Tool/Utility for the Moto X Style (Pure)
Contributors
Hashbang173, jackpotclavin, Shawn5162
Source Code: https://github.com/TeamWin/Team-Win-Recovery-Project/
Version Information
Status: Testing
Created 2015-09-13
Last Updated 2018-12-22
Device Specific Changelog
Code:
- 12/22/18 Update to Nougat base
- 1/29/16 Add encryption support
- 12/2/15 Fix boot on M bootloader and fix reboot hang
- 9/16/15 Official support
- 9/14/15 [URL="http://forum.xda-developers.com/showpost.php?p=62822999&postcount=72"]RTC fix and fstab updated[/URL]
- 9/13/15 Initial unofficial release
Reserved
This is a beautiful thing! Well done and thanks to all involved!!
MOTO X PURE EDITION!
1st THX for this as I am waiting for my device to arrive this week.
I plan to make the clark twrp device tree compatible with omnirom build sometime tomorrow.
After that, I'll see about getting official support!
Flashed with no problems. Thanks!
recovery not sticking
i ran the test command and it booted into TWRP just fine then ran the install command and got "writing recovery ... OK"
Is there a formal way of entering recovery mode? From the bootloader, I got the red triangle then hit power and up vol, got into the factory recovery menu
thanks for your quick work!
ddash97 said:
i ran the test command and it booted into TWRP just fine then ran the install command and got "writing recovery ... OK"
Is there a formal way of entering recovery mode? From the bootloader, I got the red triangle then hit power and up vol, got into the factory recovery menu
thanks for your quick work!
Click to expand...
Click to collapse
Flash SuperSU to gain root, then download any app that reboots into recovery: example app is I think quick reboot it has options to boot into recovery w/ root permission.
Hope that helps!
thanks for the quick response
All rooted, no more ads ... many thanks!
Also just did a backup to SD with no problem, and SD appears available under Install although I installed SU from internal.
So now that there's root, will xposed work?
Sent from my HTC One_M8 using XDA Free mobile app
Thank you. Worked great. I am now rooted, as well.
silverxbv2 said:
So now that there's root, will xposed work?
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
You could try flashing the android 5.1 arm64 version, just make sure to backup as always before flashing. Worst case scenario is probably that your device bootloops and you have to restore your backup.
Confirming that backup to, and restore from SD, work just fine.
I guess I forgot how to do all this. I flashed TWRP, went into recovery, went to restart menu and rebooted phone. I thought it was supposed to prompt me to install SuperSU at that point. It didn't so I downloaded it from the Play Store and it says it can't install.
What am I doing wrong?
RyanTX said:
I guess I forgot how to do all this. I flashed TWRP, went into recovery, went to restart menu and rebooted phone. I thought it was supposed to prompt me to install SuperSU at that point. It didn't so I downloaded it from the Play Store and it says it can't install.
What am I doing wrong?
Click to expand...
Click to collapse
You have to flash it, in recovery. I always use the beta, http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
spotmark said:
You have to flash it, in recovery. I always use the beta, http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Thanks, did that as soon as I made my post. All is good now.
spotmark said:
Confirming that backup to, and restore from SD, work just fine.
Click to expand...
Click to collapse
Likewise. Happy days are here again!
I have Xposed installed, and the phone booted. I'm still waiting for Optimizing apps to finish.

Categories

Resources