[TOOL/UTILITY][TWRP][3.2][RECOVERY] TWRP 3.2.2-0 TeamWin Recovery Project - Galaxy Note 4 Original Android Development

[TOOL/UTILITY][TWRP][3.2][RECOVERY] TWRP 3.2.2-0 TeamWin Recovery Project - Galaxy Note 4 Original Android Development

[RECOVERY] TWRP 3.2.2-0 - TeamWin Recovery Project
TeamWin is proud to present TWRP 3.2.2-0 for the Samsung Galaxy Note 4 (Exynos/Qualcomm International)!
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.
treltexx Device Config: TBD
Kernel: https://github.com/bigbiff/android_...ub.com/bigbiff/android_kernel_samsung_trltexx
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
See http://twrp.me for official release notes.
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
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.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.1
treltexx
- fix color scheme again
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)
2.8.5.0
- Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
- Improve thread handling and move input handling into the main rendering thread to improve stability
- Make MTP work even if unplugged and plugged back in
- Unify scrollable list code and make kinetic scrolling feel more natural
- Fix handling of mapped zip files for OTA updates (CM12 updater)
- USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
- Add Cancel Backup capability
- Other small fixes and improvements
2.8.4.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
- Fix some MTP related crashes and bugs
- Eliminate TWRP toggling USB IDs during boot if MTP is enabled
- Fix various adb sideload issues
- Improve threading of actions
- Eliminate separate thread for screen timeout
- Update libblkid to 2.25.0
- Use power button as back button on watch themes for easier navigation
- Add mutex locking to data manager
- Improve custom theme handling on encrypted devices
- Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
2.8.3.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- MTP will now tell the host PC that storage is removed instead of disabling MTP completely
- MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
- Update and improve fix permissions and make fixing contexts optional
- Update SuperSU in TWRP to 2.40 and update install process
- Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
- Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
- Fix kernel panic during MTP start on some devices
- Support unicode fonts on devices with True Type Font support
- Fix slider value not showing sometimes (vibration settings page)
- Toggle MTP off during adb sideload to set correct USB IDs
- Reduce library requirements for 5.0 L decrypt
- Other minor fixes and improvements
2.8.1.2
- 2nd release with everything working except ADB

Reserved3

Also for n910f snapdragon
Sent from my SM-N910F using XDA Premium 4 mobile app

Not working for me. It flashed alright. Got the screen but its not making backup. perhaps I am missing something.
N-910C

bigbiff said:
2.8.1.2
- 2nd release with everything working except ADB
Click to expand...
Click to collapse
Installed on N910C I try to do an backup but
write E: unknown action "nandroid"
and nothing else
edit : I give a try to 2.8.1.1 and I can backup ?????

TKokab said:
Not working for me. It flashed alright. Got the screen but its not making backup. perhaps I am missing something.
N-910C
Click to expand...
Click to collapse
Yes, there something wrong at your side. Because a lot of people around the world have tested this version, and backup is working flawless.

TKokab said:
Not working for me. It flashed alright. Got the screen but its not making backup. perhaps I am missing something.
N-910C
Click to expand...
Click to collapse
+1 if you use the 2.8.1.2
i flash the 2.8.1.1 and it work, i have too an N910C

TWRP throwing errors on 2.8.1.2
kondronaute said:
+1 if you use the 2.8.1.2
i flash the 2.8.1.1 and it work, i have too an N910C
Click to expand...
Click to collapse
Hi there.
I'm on N910U exynos.
Flashed 2.8.1.2 sucessfully.
Tried to do backup and getting error in red "unknown action".
Actually, anything I try to do in TWRP I'm getting the above error.
I've tried flashing via odin with the .tar & via CWM recovery with .zip file with same results.
Anyone else having this problem?
---------- Post added at 11:17 PM ---------- Previous post was at 11:10 PM ----------
geewizz said:
Hi there.
I'm on N910U exynos.
Flashed 2.8.1.2 sucessfully.
Tried to do backup and getting error in red "unknown action".
Actually, anything I try to do in TWRP I'm getting the above error.
I've tried flashing via odin with the .tar & via CWM recovery with .zip file with same results.
Anyone else having this problem?
Click to expand...
Click to collapse
Whoops, looks like I read it wrong.
Will try 2.8.1.1 & see if that works...
---------- Post added at 11:38 PM ---------- Previous post was at 11:17 PM ----------
Ok, flashed 2.8.1.1.
Semmed to flash ok but when holding down volume up, home and power buttons it hangs at the "galaxy note 4' scrren and doesn't enter TWRP.
Have to pull battery to restart.
2.8.1.2 flashes ok but any command throws the unknown action error.
2.8.1.1 flashes ok but I can't enter recovery.
Any ideas anyone?

geewizz said:
Hi there.
I'm on N910U exynos.
Flashed 2.8.1.2 sucessfully.
Tried to do backup and getting error in red "unknown action".
Actually, anything I try to do in TWRP I'm getting the above error.
I've tried flashing via odin with the .tar & via CWM recovery with .zip file with same results.
Anyone else having this problem?
---------- Post added at 11:17 PM ---------- Previous post was at 11:10 PM ----------
Whoops, looks like I read it wrong.
Will try 2.8.1.1 & see if that works...
---------- Post added at 11:38 PM ---------- Previous post was at 11:17 PM ----------
Ok, flashed 2.8.1.1.
Semmed to flash ok but when holding down volume up, home and power buttons it hangs at the "galaxy note 4' scrren and doesn't enter TWRP.
Have to pull battery to restart.
2.8.1.2 flashes ok but any command throws the unknown action error.
2.8.1.1 flashes ok but I can't enter recovery.
Any ideas anyone?
Click to expand...
Click to collapse
same for me
With 2.8.1.1 If You wait a long time you finally enter recovery
It take ages also to reboot from system to recovery.
The 2.8.1.2 Is not working.
Hope a Fix soon

geewizz said:
Hi there.
I'm on N910U exynos.
Flashed 2.8.1.2 sucessfully.
Tried to do backup and getting error in red "unknown action".
Actually, anything I try to do in TWRP I'm getting the above error.
I've tried flashing via odin with the .tar & via CWM recovery with .zip file with same results.
Anyone else having this problem?
---------- Post added at 11:17 PM ---------- Previous post was at 11:10 PM ----------
Whoops, looks like I read it wrong.
Will try 2.8.1.1 & see if that works...
---------- Post added at 11:38 PM ---------- Previous post was at 11:17 PM ----------
Ok, flashed 2.8.1.1.
Semmed to flash ok but when holding down volume up, home and power buttons it hangs at the "galaxy note 4' scrren and doesn't enter TWRP.
Have to pull battery to restart.
2.8.1.2 flashes ok but any command throws the unknown action error.
2.8.1.1 flashes ok but I can't enter recovery.
Any ideas anyone?
Click to expand...
Click to collapse
2.8.1.1 and 2.8.1.2 been tested for flashing roms, flashing zips and other mods, backup and restore and all was good. No problems whatsoever. You guys must be having something wrong at your end.
Sent from my SM-N910C

Al Asmi said:
2.8.1.1 and 2.8.1.2 been tested for flashing roms, flashing zips and other mods, backup and restore and all was good. No problems whatsoever. You guys must be having something wrong at your end.
Sent from my SM-N910C
Click to expand...
Click to collapse
you are wrong we are 3 to have same pbm with 2.8.1.2 cannot backup to extcard say unknown pbm....
I installed it with odin
the 2.8.1.1 is working for me but take ages to enter recovery.
I am here from my S2 ......s3....s4.........................note4

kondronaute said:
you are wrong we are 3 to have same pbm with 2.8.1.2 cannot backup to extcard say unknown pbm....
I installed it with odin
the 2.8.1.1 is working for me but take ages to enter recovery.
I am here from my S2 ......s3....s4.........................note4
Click to expand...
Click to collapse
+1

kondronaute said:
you are wrong we are 3 to have same pbm with 2.8.1.2 cannot backup to extcard say unknown pbm....
I installed it with odin
the 2.8.1.1 is working for me but take ages to enter recovery.
I am here from my S2 ......s3....s4.........................note4
Click to expand...
Click to collapse
I'm not saying that you are wrong. What I'm trying to tell you is that you may be having problems with your extsd. Try to install a permission fix and try again. For me and for so many others it's working fine.
Sent from my SM-N910C

Al Asmi said:
I'm not saying that you are wrong. What I'm trying to tell you is that you may be having problems with your extsd. Try to install a permission fix and try again. For me and for so many others it's working fine.
Sent from my SM-N910C
Click to expand...
Click to collapse
result is E:unknown action 'fixpermissions'

kondronaute said:
result is E:unknown action 'fixpermissions'
Click to expand...
Click to collapse
Try this :
https://app.box.com/s/ajtshutm4mfexzvp004x
Unzip then flash with flashify. Tested on N910C and have no issues.
Sent from my SM-N910C

Al Asmi said:
Try this :
https://app.box.com/s/ajtshutm4mfexzvp004x
Unzip then flash with flashify. Tested on N910C and have no issues.
Sent from my SM-N910C
Click to expand...
Click to collapse
can u give me tar version please i use odin
---------- Post added at 11:08 AM ---------- Previous post was at 11:04 AM ----------
Al Asmi said:
Try this :
https://app.box.com/s/ajtshutm4mfexzvp004x
Unzip then flash with flashify. Tested on N910C and have no issues.
Sent from my SM-N910C
Click to expand...
Click to collapse
no need for tar i do what you say and it work fine
thank u

kondronaute said:
can u give me tar version please i use odin
---------- Post added at 11:08 AM ---------- Previous post was at 11:04 AM ----------
no need for tar i do what you say and it work fine
thank u
Click to expand...
Click to collapse
Glad that it worked for you.
@bigbiff, this is the last version with corrected color (blue) you've posted at the testing thread.
I hope it will work for the others who's having problems with the tar file.
https://app.box.com/s/ajtshutm4mfexzvp004x
Sent from my SM-N910C

Should i use the tmobile version on my SM-N910F?

Al Asmi said:
Glad that it worked for you.
@bigbiff, this is the last version with corrected color (blue) you've posted at the testing thread.
I hope it will work for the others who's having problems with the tar file.
https://app.box.com/s/ajtshutm4mfexzvp004x
Sent from my SM-N910C
Click to expand...
Click to collapse
Its working now.....thanks for the link

Related

[TOOL/UTILITY][TWRP][3.0][RECOVERY] TWRP 3.0.2-0 TeamWin Recovery Project 4/5

[RECOVERY] [4/5/16] TWRP 3.0.2-0 - TeamWin Recovery Project
TeamWin is proud to present TWRP 3.0.2-0 for the Samsung Galaxy Note 2 (Att)!
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.
t0lteatt Device Config: https://github.com/TeamWin/android_device_samsung_t0lteatt
Kernel: https://github.com/bigbiff/android_kernel_samsung_smdk4412
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
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.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-0
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.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.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)
2.8.5.0
- Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
- Improve thread handling and move input handling into the main rendering thread to improve stability
- Make MTP work even if unplugged and plugged back in
- Unify scrollable list code and make kinetic scrolling feel more natural
- Fix handling of mapped zip files for OTA updates (CM12 updater)
- USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
- Add Cancel Backup capability
- Other small fixes and improvements
2.8.4.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
- Fix some MTP related crashes and bugs
- Eliminate TWRP toggling USB IDs during boot if MTP is enabled
- Fix various adb sideload issues
- Improve threading of actions
- Eliminate separate thread for screen timeout
- Update libblkid to 2.25.0
- Use power button as back button on watch themes for easier navigation
- Add mutex locking to data manager
- Improve custom theme handling on encrypted devices
- Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
2.8.3.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- MTP will now tell the host PC that storage is removed instead of disabling MTP completely
- MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
- Update and improve fix permissions and make fixing contexts optional
- Update SuperSU in TWRP to 2.40 and update install process
- Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
- Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
- Fix kernel panic during MTP start on some devices
- Support unicode fonts on devices with True Type Font support
- Fix slider value not showing sometimes (vibration settings page)
- Toggle MTP off during adb sideload to set correct USB IDs
- Reduce library requirements for 5.0 L decrypt
- Other minor fixes and improvements
2.8.1.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
- Temperature support - thanks to bigbiff
- Various other bugfixes and tweaks
2.8.0.1
Fix exfat external sdcard backup
2.8.0.0
- Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
- Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
- Add support for color in the console and give error, warning, and highlight lines different colors
- Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
- Improve handling of /misc thanks to mdmower
- Improve setting of time on Qualcomm devices thanks to [NUT]
- Allow using images on slidervalue GUI objects thanks to Tassadar
- Allow using variables and addition and subtraction in variables for easier theming
- Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
- Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
- Other minor fixes and improvements
2.7.2.2
- fix backup to exfat
2.7.2.1
- fix exfat
2.7.2.0
All thanks to @Dees_Troy
- fix crash in setting contexts on datamedia
- fix restoring data partition as f2fs after formatting f2fs
- mount data after being formatted
2.7.1.0
- Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
- Various bugfixes to backup and restore
- Improvements to USB storage handling
- Added a class to search for files to make finding the correct brightness file automatic in most cases
- Various other bugfixes and tweaks
2.7.0.1
-Add F2FS
-Fix splitting of /system during certain conditions
2.7.0.0
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
2.6.3.1
Add SELINUX Kernel and SELINUX improvements for backing up and restoring
2.6.3.0
Proper backup and restore of SELinux contexts (thanks to Tassadar)
Pull in some ROM information for backup name generation
Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
Add 1200x1920 theme (thanks to Tassadar)
A few other fixes and tweaks
Change to GPL exfat kernel module to work around exfat-fuse bugs
2.6.1.0
Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
Initial support for f2fs file system formatting (Moto X)
Update SuperSU install for 4.3 ROMs
Fixed a permissions bug on files created during backup
Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
Ignore lost+found folder during backup and size calculations
Various other minor bug fixes and tweaks
2.6.0.3
Reverted back to stock kernel with optimizations instead of CM kernel to fix boot times
2.6.0.1
Fix Data being listed twice in advanced wipe
2.6.0.0
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
Can encrypt a backup to prevent theft of private data from your backup files
Updated graphics / icon courtesy of shift
Updated exFAT to latest commits
Fixed a problem with Samsung TouchWiz decryption
Update SuperSU binary
Fixed saving of backup partitions list
Fixed saving of last used zip install folder
Fixed backup of datadata on devices that use a separate partition for datadata
Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
Fixed some problems with partitioning a SD card
Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
2.5.0.1
Fix encryption
2.5.0.0
Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
Fixed a problem with directory permissions on split archive backups
Fixed a problem with md5 verification of backups
Added a search function to libtar (thanks to kokotas)
Improve handling of XML errors (fix permissions)
Fixed handling of subpartitions
Improvements to recovery.fstab flags
Fixed a problem with decryption not being able to locate the decryption key in some situations
2.4.4.0
Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
More fixes for the file selector
Switched from using busybox md5sum to a direct C function call
Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
Update exFAT to latest commits
Added a build flag to disable using the ioctl for screen blanking
2.4.3.0
Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
Added a scroll bar to file selectors and listboxes courtesy of Tassadar
Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
Added a screen dim effect 2 seconds before screen off on some devices
Finally fixed file selector crash (one of the joys of working with multi-threaded software)
Fixed loading of screen timeout setting during startup
Improvements and bugfixes to screen timeout code
Fix Military Time setting persisting
2.4.2.0
Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
Add a brightness setting (requires device specific setup and only some devices have been added)
Add a root checker and offer to install SuperSU if the device isn't already rooted
Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
Check and offer to fix root permissions if broken
Add an option for a 24 hour clock display instead of AM/PM (aka military time)
Move stock recovery reflash check to occur during the reboot cycle
Add support for some MTK6xxx devices
Change libtar to vfork to help prevent memory problems
Add a "clicked" effect to most buttons, file selector, and listbox
Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
Other minor bugfixes and improvements
2.4.1.0
Fixed detection of exfat and vfat
Fixed vfat formatting past 2 GB
2.4.0.0
Reverted back to kernel drivers for performance on EXFAT.

FAQ
Q. Are there any themes I can use?
pctv007 has ported some themes for the Note2: http://www.mediafire.com/?34sulxbjxzb34
Q. Are there any themes I can use?
pctv007 has ported some themes for the Note2: http://www.mediafire.com/?34sulxbjxzb34
Q. Can I use Goo Manager to install TWRP if I am not rooted?
A. No, you will not have permissions to access the recovery paritition without a rooted system installed. This gives you the ability to have su installed as SUID root and with Superuser or SuperSu, you can give Android applications root access to use su to access the system as the root user.
Q. Where is the "Delete battery stats opton?"
A. We removed this option in 2.1. Please see https://plus.google.com/u/0/105051985738280261832/posts/FV3LVtdVxPT as reference.
Q. What happens if I wipe /data?
Good description also here: http://teamw.in/DataMedia
The Galaxy Note 2 is using the fuse filesystem to pretend /data/media is its own filesystem to external computers when you plug the phone into the computer. /data is one partition formatted as ext4. There is a subdirectory for media under /data which is presented as its own block device using fuse. Then mtpd uses this directory to present the directory to a host computer when plugging in via USB.
Never allow your computer to format this directory in case there is a problem with mtpd. Also NEVER wipe data under the Wipe menu unless absolutely necessary. This will remove all your files in /data/media.
On the original note, internal SDCARD was a separate file system formatted with the fat32 filesystem but exported directly through MTP.

for some odd reason i really cant get this too install .. had it on my original note ... trouble with this one

I had a problem with using odin to install the tar file and odin'd cwm instead. I tried to install twrp using the zip file in CWM but it just won't take. It aborts installation. Any insight would be great.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

tdamocles said:
I had a problem with using odin to install the tar file and odin'd cwm instead. I tried to install twrp using the zip file in CWM but it just won't take. It aborts installation. Any insight would be great.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Which cwm worked on the note 2

tdamocles said:
I had a problem with using odin to install the tar file and odin'd cwm instead. I tried to install twrp using the zip file in CWM but it just won't take. It aborts installation. Any insight would be great.
Click to expand...
Click to collapse
same here .. kept crashing ODIN ... but i didnt even install CWM ... which one worked ??? the latest touch ??

i just installed using goomanager and it went off without a hitch. thanks biff

Also installed with goomanager and didn't have any problems at all.

timmyhawk1983 said:
same here .. kept crashing ODIN ... but i didnt even install CWM ... which one worked ??? the latest touch ??
Click to expand...
Click to collapse
I think I know why it's borked in Odin now. I am tweaking my build script now and will upload them soon. I will post in the thread when it's done and if someone can test I would be grateful.
I am maintaining around 7 device threads now, so bear with me. Poor Dees_Troy has like 40 though.

Wait goomanager installed the tar file or is there a zip?
Nvm I found it

OK, I reuploaded the tars. Let me know if you guys still have issues.

truth77 said:
Wait goomanager installed the tar file or is there a zip?
Nvm I found it
Click to expand...
Click to collapse
Just FYI, Goo Manager downloads the img file and install's TWRP for you. It will even alert you to new updates.

Successfully installed with Goo Manager and didn't run into any issues.
This is feeling more and more like it's mine now and not AT&T's

i can't get the bloody zip files to install. i used Odin to install CF-Auto-Root, then booted back up, verified root, downloaded openrecovery-twrp-2.3.1.1-t0lteatt.zip, rebooted into recovery and it says:
E:signature verification failed
Installation aborted.
rebooted, installed GooManager, found the openrecovery-twrp-2.3.1.1-t0lteatt.zip, let it download it, then it rebooted and says:
E:unknown volume for path [/storage/extSdCard/goomanager/openrecovery-twrp-2.3.1.1-t0lteatt.zip
E:Can't mount /storage/extSdCard/goomanager/openrecovery-twrp-2.3.1.1-t0lteatt.zip
(also tried using /storage/sdcard0/goomanager/openrecovery-twrp-2.3.1.1-t0lteatt.zip with the same results)
am i an idiot or what?
careful...

Anyone else notice that external sd cannot be used?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

Will this work on the Rogers version? Thx.

truth77 said:
Which cwm worked on the note 2
Click to expand...
Click to collapse
Link to cwm6-recovery-i317.tar.md5
It's in the first post as i317.

If you're using stock recovery you can't flash zips. In goo manager press menu then install OpenRecoveryScript to install twrp.
itsonlym3 said:
i can't get the bloody zip files to install. i used Odin to install CF-
Auto-Root, then booted back up, verified root, downloaded openrecovery-twrp-2.3.1.1-t0lteatt.zip, rebooted into recovery and it says:
E:signature verification failed
Installation aborted.
rebooted, installed GooManager, found the openrecovery-twrp-2.3.1.1-t0lteatt.zip, let it download it, then it rebooted and says:
E:unknown volume for path [/storage/extSdCard/goomanager/openrecovery-twrp-2.3.1.1-t0lteatt.zip
E:Can't mount /storage/extSdCard/goomanager/openrecovery-twrp-2.3.1.1-t0lteatt.zip
(also tried using /storage/sdcard0/goomanager/openrecovery-twrp-2.3.1.1-t0lteatt.zip with the same results)
am i an idiot or what?
careful...
Click to expand...
Click to collapse

tdamocles said:
Anyone else notice that external sd cannot be used?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
What kind of external sdcard do you have and how is it formatted?

[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][jfltexx] TWRP 3.1.1-0 touch recovery [2017-05-19]

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?

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

Reserved
Starting with version 2.7.1.1, we're now doing a unified build for both the 1080p 7a and the 1440p devices. This means the same recovery image works on both devices and will provide you with the proper stock theme for your display. Of course, you can still install a custom theme if you like.
Link to device specific page on our website
Direct link to downloads folder for current / past versions

first.
friggin sweet...

noice, im rooted and haz twrp

Thanks! Seems to install and run fine. :victory:

Waiting for my preorder

Dees_Troy said:
Currently only officially support the Find 7a with the 1080p screen.
Link to device specific page on our website
Direct link to downloads folder for current / past versions
Click to expand...
Click to collapse
I was gonna ask which find 7 this supports. Thanks!!
Sent from my SGH-T889 using XDA Premium 4 mobile app

CAN someone give me a backup of ROM
I buy my find 7a in china And no playstore ans french langage on it
Actually i manage to root via chineese forum And install playstore And turn 80 per 100 of thé phone ni french with morelocale2
But i want thé international ROM to get 100 per 100 french
If someone CAN help
Thanks

i can not use this to flash stock rom
来自我的 X9007 上的 Tapatalk

Dees_Troy said:
Team Win Recovery Project 2.x, or twrp2 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.
Phone look:
Tablet look:
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
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.
XDA:DevDB Information
[RECOVERY][Find7] TWRP 2.7.0.0 touch recovery [2014-04-14], a Tool/Utility for the Oppo Find 7
Contributors
Dees_Troy, bigbiff
Version Information
Status: Stable
Current Stable Version: 2.7.0.0
Stable Release Date: 2014-04-14
Created 2014-04-15
Last Updated 2014-04-14
Click to expand...
Click to collapse
Anybody have any idea how to change the language in app drawer menu settings to english. I have changed the default language in settings to english. But that doesn't help change the language in the settings menu of app drawer. Please help !

Nice!
Sent from my HTC One using Tapatalk

Sorry for the question
I know this might be a bad question, but can someone explain to me or send me a link on how i can install this recovery? I'd rather as stupid questions that brick my phone

troysyx said:
I know this might be a bad question, but can someone explain to me or send me a link on how i can install this recovery? I'd rather as stupid questions that brick my phone
Click to expand...
Click to collapse
Download the recovery file: http://techerrata.com/browse/twrp2/find7a
Install the Google ADB / Fastboot drivers (Windows http://goo.gl/ZWGG)
Hold in Power and Vol Up to put your Find 7 into Fastboot mode.
Plug your USB cable into your phone and computer.
Type fastboot devices.
You should see your phone listed. If you're do proceed.
To just boot the recovery: fastboot boot openrecovery-twrp-2.7.0.0-find7a.img
To install / flash the recovery: fastboot flash recovery openrecovery-twrp-2.7.0.0-find7a.img

rayfin said:
Download the recovery file: http://techerrata.com/browse/twrp2/find7a
Install the Google ADB / Fastboot drivers (Windows http://goo.gl/ZWGG)
Hold in Power and Vol Up to put your Find 7 into Fastboot mode.
Plug your USB cable into your phone and computer.
Type fastboot devices.
You should see your phone listed. If you're do proceed.
To just boot the recovery: fastboot boot openrecovery-twrp-2.7.0.0-find7a.img
To install / flash the recovery: fastboot flash recovery openrecovery-twrp-2.7.0.0-find7a.img
Click to expand...
Click to collapse
Awesome! Thank you so much

Dees_Troy said:
DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our website!
Click to expand...
Click to collapse
FYI, I tried to install it with TWRP Manager. It stopped at the "Downloading Image" status bar on my F7a. I tried to download it manually, and it worked. Probably some write permission issues.
I ended up flashing it with fastboot and it works like a charm.
Thank you Guy´s!

Any possibilities to flash on Mac OSX?

betold said:
FYI, I tried to install it with TWRP Manager. It stopped at the "Downloading Image" status bar on my F7a. I tried to download it manually, and it worked. Probably some write permission issues.
I ended up flashing it with fastboot and it works like a charm.
Thank you Guy´s!
Click to expand...
Click to collapse
same here for me.. can't download with TWRP Manager

TWRP Nightmare
Every time I install TWRP, it gives me problems. I was gonna flash cm11 using TWRP, so I flashed it via fastboot to my phone. Now, whenever I boot the phone, it boots straight into the recovery. Even if I boot into system from recovery, it still boots back into TWRP. I tried both versions 2.7, and 2.7.1, but the same result. This isn't even the weird part. Whenever I flash another recovery, like CWM or PhilZ, if I reboot my phone, it goes BACK to TWRP recovery! Wtf? When I flash OPPO's recovery, the phone gets stuck at the OPPO logo forever. What could be wrong? If I need to provide more info, let me know. I didn't think flashing roms and recoveries on this phone would be so frustrating. I never had this much trouble flashing recoveries and ROMs on my Galaxy S2. Any help is appreciated. Thanks!

Anyone else having problems with the time being displayed in TWRP? My backups are time stamped 1970 as well. I had this problem on Gummy's recovery as well so maybe it's the phone's internal clock that is off?
*edit*
googled and found partial answers.

azeem40 said:
Every time I install TWRP, it gives me problems....
Any help is appreciated. Thanks!
Click to expand...
Click to collapse
I'd say start fresh and work through it.
Do a fresh fastboot flash and provide that log/entry here.
Then after you boot TWRP again, wipe system/data/cache/davlik, flash your ROM and before you reboot provide the recovery.log (from Settings or Advanced I believe, will copy to your SD card).
If you still aren't able to boot into Android I'm guessing we can find the problem there there.

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

Reserved
Starting with version 2.7.1.1, we're now doing a unified build for both the 1080p 7a and the 1440p devices. This means the same recovery image works on both devices and will provide you with the proper stock theme for your display. Of course, you can still install a custom theme if you like.
Link to device specific page on our website
Direct link to downloads folder for current / past versions

Dees_Troy said:
Starting with version 2.7.1.1, we're now doing a unified build for both the 1080p 7a and the 1440p devices. This means the same recovery image works on both devices and will provide you with the proper stock theme for your display. Of course, you can still install a custom theme if you like.
Link to device specific page on our website
Direct link to downloads folder for current / past versions
Click to expand...
Click to collapse
Every time I download, file size is like 5 kb. I tried flashing without noticing that but didn't work. Flashed back other recovery in meantime. Think the newest version needs to be reuploaded.
Sent from my Find7 using XDA Free mobile app

I download it from my find 7 without any issue.
P/S: the recovery is not working, install and when reboot to recovery, it turns to black screen and nothing goes to the recovery,
Sent from my X9076 using xda premium

I can confirm that too. The recovery seems to be working, because the touchscreen aswell as the software-buttons are responsive, but there is only a black screen every time i boot into it.

yeah this did not work for me either. Also, after reflashing the recovery that I was using before (find 7a 6-12-14) the same thing happens. I have no access to my recovery now.

v2.7.1.1. is not working with me either, just a black screen and flashing on and off, gonna try reverting to gummy twrp
---------- Post added at 10:28 PM ---------- Previous post was at 10:22 PM ----------
opie546 said:
yeah this did not work for me either. Also, after reflashing the recovery that I was using before (find 7a 6-12-14) the same thing happens. I have no access to my recovery now.
Click to expand...
Click to collapse
why were u using a 7a recovery? also you can use fastboot to restore your old recovery i just did and it works fine

Black screen on my X9077 too.
bobbydigital222 said:
v2.7.1.1. is not working with me either, just a black screen and flashing on and off, gonna try reverting to gummy twrp
---------- Post added at 10:28 PM ---------- Previous post was at 10:22 PM ----------
why were u using a 7a recovery? also you can use fastboot to restore your old recovery i just did and it works fine
Click to expand...
Click to collapse

bobbydigital222 said:
why were u using a 7a recovery? also you can use fastboot to restore your old recovery i just did and it works fine
Click to expand...
Click to collapse
Sorry I probably misspoke. I was using the first port from the F7a for the F7. It was 1080p and everything. Never bothered updating it until now. Yeah, I know about fastboot and took care of it. Thanks!
I can't wait until the offical twrp is updated/fixed. the team gummy version is so annoying.

opie546 said:
Sorry I probably misspoke. I was using the first port from the F7a for the F7. It was 1080p and everything. Never bothered updating it until now. Yeah, I know about fastboot and took care of it. Thanks!
I can't wait until the offical twrp is updated/fixed. the team gummy version is so annoying.
Click to expand...
Click to collapse
Ya same here, I don't like the theme, and I'm hoping for ntfs support

Is there anyway to add ntfs support?

Link
Thanks

Link not found for TWRP 2.8.0.1
Dees_Troy said:
Team Win Recovery Project 2.x, or twrp2 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 2.8.0.1:
-Fix a bug that causes weird graphics glitches and touch issues
CHANGELOG for 2.8.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
Click to expand...
Click to collapse
Hi,
As you know in find 7 QHD device, TWRP 2.8.0.0 is showing only Full HD, and it is not detecting the QHD Resolution properly.
So, I am looking for the next update TWRP 2.8.0.1
But the download of TWRP 2.8.0.1 is not available yet
Please have a look...
http://techerrata.com/browse/twrp2/find7
Thank you

Mnt-XDA said:
Hi,
As you know in find 7 QHD device, TWRP 2.8.0.0 is showing only Full HD, and it is not detecting the QHD Resolution properly.
So, I am looking for the next update TWRP 2.8.0.1
But the download of TWRP 2.8.0.1 is not available yet
Please have a look...
http://techerrata.com/browse/twrp2/find7
Thank you
Click to expand...
Click to collapse
2.8.0.0 is usable, but this was a side effect of the LVM rework being done in the device tree. I began moving the recovery init script out of msm8974-common and into the find7 device-specific tree - but while I deleted it from -common the patch which readds it to the find7 tree isn't merged yet. Fortunately the only function that script serves is to detect QHD and copy the appropriate theme - but the 1080p theme will at least be usable on QHD devices in the meantime. Sorry about that.
I just got back from vacation, I need to talk to Dees_Troy, but likely the build that contains the fix for QHD devices will also contail full LVM support.

Thanks for the update @Dees_Troy .. still having a graphics glitch in 2.8.0.1. It's got this invisible line running down the screen
Find 7(s)

Just wanted to ask, the thread name says 2.8.1.0 but I can not find this up to date build for the Find 7 anywhere, website and TWRP Manager app both show 2.8.0.1 as the newest version.
Am I looking in the wrong place or is the thread title incorrect??

Downgrade to jellybean stable color os then flash in fastboot TWRP 2.8.0.1 do not boot into color os hold pwr vol down boot into TWRP it shoulb be gone flash desired rom if you flas kitkat Color os it'll come back I think is something in the newer bootloader thats brakin it.
Sent from my Find7 using XDA Premium HD app

carlosjcar said:
Downgrade to jellybean stable color os then flash in fastboot TWRP 2.8.0.1 do not boot into color os hold pwr vol down boot into TWRP it shoulb be gone flash desired rom if you flas kitkat Color os it'll come back I think is something in the newer bootloader thats brakin it.
Sent from my Find7 using XDA Premium HD app
Click to expand...
Click to collapse
also i have wave glitch effect with twrp 2.8.0.1 on find 7 QHD and color OS 2.0! If i return to colos 1.2.x and after i reflash colos 2.0 (nandroid backup or new flash with factory reset) i resolve this problem or i reupdate the bootloader and the glitch reappears?

fosseperme said:
also i have wave glitch effect with twrp 2.8.0.1 on find 7 QHD and color OS 2.0! If i return to colos 1.2.x and after i reflash colos 2.0 (nandroid backup or new flash with factory reset) i resolve this problem or i reupdate the bootloader and the glitch reappears?
Click to expand...
Click to collapse
same issue here with colorOS 2.0.0i and I do not want to downgrade to get rid of this issue but yeah like a line that move downwards when in TWRP

Natherul said:
same issue here with colorOS 2.0.0i and I do not want to downgrade to get rid of this issue but yeah like a line that move downwards when in TWRP
Click to expand...
Click to collapse
same thing persists after flashing stock recovery from oppo forums.... Anyone know if its something wrong with the files I have or what else it could be?

Develop Bugs

welcome