Develop Bugs

[RECOVERY][crespo4g] TWRP 3.0.0-0 touch recovery [2016-02-06]

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.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!
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.

Changelog - See our website!

FAQ:
How to install with Fastboot:
1. Download the fastboot binary for your computer from HTC
2. Connect your phone and boot it into fastboot
3. Run fastboot with the command
Code:
Code:
fastboot flash recovery path/to/recovery-twrp-crespo4g-1.0.3.img
Error when flashing some zip files:
twrp only supports the latest and greatest edify script for zip flashing. Please bug the zip developer to update the zip script to edify.
Does this back up the WiMAX partition?
That is an option if you chose, but you'll find it under "efs" and not wimax. Both the NS4G and the GSM Nexus S have an efs partition. The efs partition on the NS4G includes WiMAX along with some other fairly crucial data. It's a good idea to back up your efs separately (e.g. just pick efs and don't choose any other partitions) and keep this backup in a safe place.
Live support:
Click this link or join us in #twrp on Freenode IRC.

Yes. Thanks for this. Works great
So how will flashing our backed up images thru fastboot work since they are backed up as .win?
Uncle Jimmy says hello

snandlal said:
Yes. Thanks for this. Works great
So how will flashing our backed up images thru fastboot work since they are backed up as .win?
Uncle Jimmy says hello
Click to expand...
Click to collapse
What partition?
Most are img files just with a different extension some are .tars. You can try it. If it doesn't work you can just restore.

If i go in TWRP on my storage and look at the backed up images like system.win, data.win, boot.win. how would i use that image in fastboot if for some reason i couldnt get to recovery? Rename it to .img?
Uncle Jimmy says hello

The .win files are either .tar or .tgz files (depending on whether you chose compression or not). The backups themselves are usually done with dd. So long as you're not messing with the recovery partition itself and leaving compression turned off, you should be good to go with fastboot flashing, though I don't have a NS4G myself to check.

snandlal said:
If i go in TWRP on my storage and look at the backed up images like system.win, data.win, boot.win. how would i use that image in fastboot if for some reason i couldnt get to recovery? Rename it to .img?
Uncle Jimmy says hello
Click to expand...
Click to collapse
No, you can not fastboot system/data/cache/sd-ext/.android_secure as those are essentially tgz. You can how ever fastboot or dd the others which are boot/recovery/efs by renaming it to .img

AssassinsLament said:
No, you can not fastboot system/data/cache/sd-ext/.android_secure as those are essentially tgz. You can how ever fastboot or dd the others which are boot/recovery/efs by renaming it to .img
Click to expand...
Click to collapse
What? Ok so all im asking is.....the system.win in TWRP, can i rename that system.img and flash thru fastboot?
Uncle Jimmy says hello

snandlal said:
What? Ok so all im asking is.....the system.win in TWRP, can i rename that system.img and flash thru fastboot?
Uncle Jimmy says hello
Click to expand...
Click to collapse
You can fastboot these backups:
boot/recovery/efs
You cannot fastboot these:
system/data/cache/sd-ext/.android_secure
Hope that clears it up.

Dees_Troy said:
You can fastboot these backups:
boot/recovery/efs
You cannot fastboot these:
system/data/cache/sd-ext/.android_secure
Hope that clears it up.
Click to expand...
Click to collapse
Ok thanks. That did clear it up.
Uncle Jimmy says hello

You guys gonna submit this to koushik so it can be flashed in rom manager under "flash alternate recoveries"?

I would love to use this recovery, but unable to push anything on my laptop right now (needs formation). Any flashable scripts?
Sent from my Nexus S 4G using XDA Premium App

info[]box1 said:
I would love to use this recovery, but unable to push anything on my laptop right now (needs formation). Any flashable scripts?
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
Use "flash_image gui" by Joeykrim. Apps & Themes section
http://forum.xda-developers.com/showthread.php?t=1122599

snandlal said:
Use "flash_image gui" by Joeykrim. Apps & Themes section
http://forum.xda-developers.com/showthread.php?t=1122599
Click to expand...
Click to collapse
Thanks for help I'll report back.
Edit: it worked thx
Sent from my Nexus S 4G using XDA Premium App

Loving this recovery. Great job teamwin!
Wish all capacitive buttons worked though.

snandlal said:
Use "flash_image gui" by Joeykrim. Apps & Themes section
http://forum.xda-developers.com/showthread.php?t=1122599
Click to expand...
Click to collapse
Please advise: If your using the app do you just select the recovery image option and hit flash file?

very very well done.
would there be a way to implement the option to perform backup/restore via adb like on RA recovery?
I tried it but i am not sure if i remember the command properly I did
Code:
adb shell
# cd /sbin
# nandroid-mobile.sh -b

TheBurgh said:
Please advise: If your using the app do you just select the recovery image option and hit flash file?
Click to expand...
Click to collapse
yeah the first attempt i selected recovery img and manually selected wipe cache. it prompted successful execute, but recovered cwm recovery (no recovery)lol. just rebooted and the second attempt i didnt check wipe cache. all is GOOD now lol.

[email protected] said:
very very well done.
would there be a way to implement the option to perform backup/restore via adb like on RA recovery?
I tried it but i am not sure if i remember the command properly I did
Code:
adb shell
# cd /sbin
# nandroid-mobile.sh -b
Click to expand...
Click to collapse
We don't use nandroid.sh at all. It's not included in our recovery. All of our backups are done in C, so this isn't possible. Sorry.
We didn't base our recovery on CWM or Amon_RA. While we may have used a few bits of code here and there, for the most part we tried to write our own recovery doing things the best way that we thought was possible.

[RECOVERY][p4noterf] 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.

Will this work with N0813?
Also should i install it via goo?
Also THANKS!!!
Edit worked awesome!!!
Thanks again, no more buggy cwm!!!!

Yes, Working on GT-N8013
davidrules7778 said:
Will this work with N0813?
Also should i install it via goo?
Also THANKS!!!
Edit worked awesome!!!
Thanks again, no more buggy cwm!!!!
Click to expand...
Click to collapse
Works and Yes install through GOO is fine. Only issue experienced from the install so far is when in recovery trying to type or select sometimes creates double entries or backs out of the function completely. But aside from that it is working as expected.

hkeyman said:
Works and Yes install through GOO is fine. Only issue experienced from the install so far is when in recovery trying to type or select sometimes creates double entries or backs out of the function completely. But aside from that it is working as expected.
Click to expand...
Click to collapse
so awesome to have this on the note.
just wondering, does installing this through goo fix the problem we had with CWM root method where if you boot into recovery it would auto write a script to reinstall the standard recovery? right now i am rooted but because of this bug with the new firmware my CWM is gone and i haven't used the adb instructions to fix it.
once you use TWRP you'll never go back to CWM imo

knives of ice said:
so awesome to have this on the note.
just wondering, does installing this through goo fix the problem we had with CWM root method where if you boot into recovery it would auto write a script to reinstall the standard recovery?
once you use TWRP you'll never go back to CWM imo
Click to expand...
Click to collapse
Not sure, but i got out of that issue with the original clockwork.
Pretty sure it will though

Still rooted...
davidrules7778 said:
Not sure, but i got out of that issue with the original clockwork.
Pretty sure it will though
Click to expand...
Click to collapse
After installing TWRP and using recovery a few times and then rebooting back into system I am not seeing any root/unroot issues. All is working normally here. Which version of the Tablet are you running? I am on the GT-N8013.

hkeyman said:
After installing TWRP and using recovery a few times and then rebooting back into system I am not seeing any root/unroot issues. All is working normally here. Which version of the Tablet are you running? I am on the GT-N8013.
Click to expand...
Click to collapse
I am not having issues at all
Ask the other guy
Sent from a Baked Black Jelly Belly

What I am referring to is with the latest rooting method 2 and if you are on the latest firmware when you reboot the firmware automatically rewrites the cwm image. The only way to stop this is via adb check the instructions below that are to be used in the current method
0) Copy the SU/superSU zip file to your tablet.1) Boot into ODIN mode by holding volume down and power. Volume down is the one closest to power.2) Open ODIN on your computer, select the CWM tar.md5 file in the PDA slot, uncheck auto reboot.3) Hit start. It should flash recovery successfully4) Now you want to boot directly into CWM, or you'll lose it. So while holding down volume UP (the one farther from power), hold down the power button. When you see the Samsung Galaxy Note 10.1 logo, let go of power, or else you'll keep rebooting, but keep holding volume UP. Or at least that's what I had to do, which was kind of surprising coming from other Samsung devices.5) Once in CWM, flash the superSU zip file. Congratulations, you have root, but if you reboot now the firmware will nuke CWM. We don't want to have to flash it again, so let's remove the shell script that nukes CWM.6) Under mounts and storage in CWM, mount system.7) Back on your computer, run adb shell. If you forget to mount system it'll complain because it can't find sh, silly adb. For a second I thought Samsung didn't include sh out of the box and then I realized that makes no sense.8) Type su to become root9) rm /system/etc/install-recovery.sh
So anyways I personally don't know jack squat about adb so I am rooted but don't have cwm installed because it overwrite.
Flashing twrp with goo it flashes for me successfully it claims but when I reboot to recovery I still have stock recovery. I suspect because I didn't do the adb.instructions above that this is the problem
I was hoping flashing this would automatically remove that script you need to remove in adb

knives of ice said:
What I am referring to is with the latest rooting method 2 and if you are on the latest firmware when you reboot the firmware automatically rewrites the cwm image. The only way to stop this is via adb check the instructions below that are to be used in the current method
0) Copy the SU/superSU zip file to your tablet.1) Boot into ODIN mode by holding volume down and power. Volume down is the one closest to power.2) Open ODIN on your computer, select the CWM tar.md5 file in the PDA slot, uncheck auto reboot.3) Hit start. It should flash recovery successfully4) Now you want to boot directly into CWM, or you'll lose it. So while holding down volume UP (the one farther from power), hold down the power button. When you see the Samsung Galaxy Note 10.1 logo, let go of power, or else you'll keep rebooting, but keep holding volume UP. Or at least that's what I had to do, which was kind of surprising coming from other Samsung devices.5) Once in CWM, flash the superSU zip file. Congratulations, you have root, but if you reboot now the firmware will nuke CWM. We don't want to have to flash it again, so let's remove the shell script that nukes CWM.6) Under mounts and storage in CWM, mount system.7) Back on your computer, run adb shell. If you forget to mount system it'll complain because it can't find sh, silly adb. For a second I thought Samsung didn't include sh out of the box and then I realized that makes no sense.8) Type su to become root9) rm /system/etc/install-recovery.sh
So anyways I personally don't know jack squat about adb so I am rooted but don't have cwm installed because it overwrite.
Flashing twrp with goo it flashes for me successfully it claims but when I reboot to recovery I still have stock recovery. I suspect because I didn't do the adb.instructions above that this is the problem
I was hoping flashing this would automatically remove that script you need to remove in adb
Click to expand...
Click to collapse
Actually, you don't need to use ADB, but that was just the fastest way to do it for me. The script doesn't remove root so you can let it boot up and delete the sript using a root file explorer (these days I'm partial to Solid Explorer Beta). But you'll just have to flash CWM a second time if you let it boot up once.

No recovery found using GooManager
I tried installing TWRP through GooManager, but after several minutes of 'Looking for recoveries...' I guess it gave up
Device: GT-N8000 (EU WiFi+3G).

iofthestorm said:
Actually, you don't need to use ADB, but that was just the fastest way to do it for me. The script doesn't remove root so you can let it boot up and delete the sript using a root file explorer (these days I'm partial to Solid Explorer Beta). But you'll just have to flash CWM a second time if you let it boot up once.
Click to expand...
Click to collapse
Thanks.
Seems like goo is down again so as soon as its up we will see if this works

LayZeeDK said:
I tried installing TWRP through GooManager, but after several minutes of 'Looking for recoveries...' I guess it gave up
Device: GT-N8000 (EU WiFi+3G).
Click to expand...
Click to collapse
Did u go into goos menu and select install open recovery?

davidrules7778 said:
Did u go into goos menu and select install open recovery?
Click to expand...
Click to collapse
Of course. I pressed 'Install OpenRecoveryScript', pressed 'Yes', and a dialog box said 'Looking for recoveries...' for several minutes after which it disappeared. But knives of ice says that something is wrong with GooManager.

LayZeeDK said:
Yes, I pressed 'Install OpenRecoveryScript', pressed 'Yes', and a dialog box said 'Looking for recoveries...' for several minutes after which it disappeared. But knives of ice says that something is wrong with GooManager.
Click to expand...
Click to collapse
Yeah the goo servers seem to be down has happened many times in the past. I can't even login to my goo supporter account

There are download links for a mirror and instructions for a manual install on our website.

Dees_Troy said:
There are download links for a mirror and instructions for a manual install on our website.
Click to expand...
Click to collapse
Awesome I got it working now you definitely must delete the file referenced above if you have recently rooted on the latest firmware.
You can also manually flash with mobile Odin if you don't want to use adb like myself while goo is down. Just rename the file to recovery.img

Wanted to say thanks, Dees_Troy! Just picked up a WiFi GT-8013 and this is the first thing I put on it. If you need any help testing or whatnot, feel free to give me a shout and I will test you stuff

Finally got something to flash on this. Anyways it seems like something is messed up with the touchscreen in twrp recovery. Its either much too sensetive or won't scroll at all. Its near impossible to pick a file to flash right now for me anyways if its in a specific folder like downloads
Anyone else?

Yes, i´ve got the same problem, needed 10 minutes yesterday to pick up all the files for cm10 flash...

Same thing here, although I eventually got it to flash. CitizenX, if you flashed CM10, could you report whether your S Pen still works in the CM10 discussion thread? Mine just stopped working with the same errors I was getting last time the S Pen stopped working for me.

[RECOVERY][R819] TWRP 2.8.3.0 touch recovery [2014-12-22]

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.8.3.0:
-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
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.
CHANGELOG for 2.8.2.0:
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
CHANGELOG for 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
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.
CHANGELOG for 2.7.1.0:
-Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
-Various bugfixes to backup and 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
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.

Reserved
Device Page on our website:
http://www.teamw.in/project/twrp2/203
Downloads:
http://techerrata.com/browse/twrp2/R819

In my OPPO R819 Goomanager says "No recoveries were found for your device"

This is great news. Finally a custom recovery for R819!

Download img file here
http://techerrata.com/browse/twrp2/R819
Flash with MobileUncle MTK tools found from Play Store
https://play.google.com/store/apps/details?id=com.mobileuncle.toolbox
Do this with your OWN responsibility! I am not responsible if you screw around and brick your phone!
1. Put downloaded IMG file in root of SDcard
2. Open Mobileuncle Tools
3. Choose 'Recovery Update'
4. On the top of the list should show the IMG file on you SD card that you downloaded.
5. Tap it and confirm with OK to flash.

Can I flash Stock Recovery Back
I have installed TWRP 2.6.3.0, and I have used it to make Backups of the whole ROM.
However, I tried to install the ColorOS Beta 1.0.0 and found out it would not install, reason unknown.
So I used TWRP to clean the partitions /Data, /System, /Cache etc. and then installed successfully the complete ROM for Oppo R819 - R819AS-11.A.07-OTA-INT-007-all-SVN4875-wipe.zip since this is the only available until now. Perfect installation.
The system says that there is a downloadable OTA Update Stock Oppo OS 4.2.1 (Build R819AS_11_A.09_131010). I downloaded it, clicked the greenish-blue button "Install", but the phone is not able to install it, obviously, because the Stock Recovery is different, and the instructions are for it alone. Is there a way to return back to Stock Recovery, despite it looks so bare and ugly, just to update the system?! Or is there another way to do it? Maybe if I knew where is stored the downloaded OTA update, I could flash it via TWRP...

Hmm, strange, I installed Color OS with TWRP. To change to stock recovery all you need is to flash a stock rom, it overwrites the recovery during the install process.

TWRP 2.6.3.0
Sorry, there is no logic in that. I did install Stock ROM, the complete ROM for Oppo R819 - R819AS-11.A.07-OTA-INT-007-all-SVN4875-wipe.zip since this is the only available until now. Perfect installation. Via TWRP, of course. Nothing can change the recovery, it stays the same, it is on its own partition, most notably, so that nothing could mess with it. Simple principle - if you are in Recovery, you cannot destroy Recovery itself.
Thanks to a person, who has a phone Oppo Find 5, but told me the problem is with the root privileges, I managed to get past the problem. I preserved the same TWRP 2.6.3.0 Recovery, since I have no other, and I can't change it. I opened the SuperSU program, and checked inside it to "Disable", temporarily. I did not use the "Permanent Uninstall Root" option, which also exists in it. I rebooted to Recovery, and in TWRP wiped the Cache & Dalvik partitions. After that I chose "Install" and the ColorOS 1.0.0 ROM installed perfectly well. It is beautifull and shiny! :good:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Where can I find the stock recovery to flash it back in case I want to revert? Or can anyone give me instructions on how to backup the stock recovery before flashing TWRP?

mundano said:
Where can I find the stock recovery to flash it back in case I want to revert? Or can anyone give me instructions on how to backup the stock recovery before flashing TWRP?
Click to expand...
Click to collapse
Yeah I'd like to know too. Or perhaps anyone has stock recovery.img for R819 ?
Sent from my R819 using Tapatalk

distan7 said:
Yeah I'd like to know too. Or perhaps anyone has stock recovery.img for R819 ?
Sent from my R819 using Tapatalk
Click to expand...
Click to collapse
I have the Stock Recovery from 131010, the file is recovery.img 5,865,472 bytes but it can only be flashed with SP Flash Tool, which is not a thing to recommend to beginners, the Tool needs to have the "MT6589_Android_scatter_emmc.txt". That is why I am afraid to post it plainly, open to anyone, just because they might start experimenting without knowledge and break their Oppo R819. Trust me, if you have installed TWRP Recovery from above, using the MobileUncle Tool, you are safe and well, it is a much better Recovery than the plain Stock one.

I understand your point, but I'm not comfortable in flashing non reversible stuff in my phone...
So I will stick with the stock recovery until there is a safe way to revert back to stock.

Victor perhaps you might share how you extract your recovery.img ? Using dd ?
Sent from my R819 using Tapatalk

Distan7 managed to find a way to revert from TWRP back to Stock Recovery :good:
He has explained it here, has done it twice just to be sure it works every time:
http://www.oppoforums.com/posts/125077/
This is his detailed explanation. Nothing irreversible!
[Oppo R819] Flashing Stock Recovery After Using TWRP
More information on a couple of ways how to recover Oppo R819 are written here:
http://www.oppoforums.com/posts/133578

TWRP was updated today to version 2.7.0.0. I flashed it without problems on my R819.
Sent from my Nexus 7 using Tapatalk

TWRP 2.7.1.0 Updated
TWRP 2.7.1.0 is uploaded to the same place http://techerrata.com/browse/twrp2/R819

vickfred said:
TWRP 2.7.1.0 is uploaded to the same
Looks like development is dead
---------- Post added at 10:45 PM ---------- Previous post was at 10:40 PM ----------
distan7 said:
Victor perhaps you might share how you extract your recovery.img ? Using dd ?
Sent from my R819 using Tapatalk
Click to expand...
Click to collapse
There are many tools available u can get any
---------- Post added at 10:47 PM ---------- Previous post was at 10:45 PM ----------
distan7 said:
Victor perhaps you might share how you extract your recovery.img ? Using dd ?
Sent from my R819 using Tapatalk
Click to expand...
Click to collapse
There are many tools available u can get any
---------- Post added at 11:15 PM ---------- Previous post was at 10:47 PM ----------
ccav2000 said:
TWRP was updated today to version 2.7.0.0. I flashed it without problems on my R819.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thats nice
Click to expand...
Click to collapse

[RECOVERY][jactivelte] Un-Official TWRP 2.8.0.0 touch recovery [2014-9-26]

HEY GUYS IT'S M AGAIN THIS TIME I AM HERE WITH SOMETHING SPECIAL FOR YOU ALL !
AFTER HOURS OF CONTINUOUS WORK AND BRICKING MY PHONE WITH SOME HACKING , I'VE FU*K'N TWRP TO WORK FOR OUR PHONE LOL !!
Click to expand...
Click to collapse
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.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.
CHANGELOG for 2.7.1.0:
-Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
-Various bugfixes to backup and 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
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.
DOWNLOAD:
https://drive.google.com/file/d/0ByEZDplbxwxJT01GUXBsTkxnVW8/edit?usp=sharing
How to flash
Download tar file from download link
Download odin (3.07 recommended ) just search for it on xda
Open odin
do whats here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
connect device to download mode and hit start

Good work man! :thumbsup:

allram said:
Good work man! :thumbsup:
Click to expand...
Click to collapse
Wouldn't have been possible without you and spegelius

Thanks a lot!
: of course also to the other major developers ☺
I would like to test it. Is it possible to make a zip which can be flashed via CWM?
Best wishes, Christian

baaldfg said:
Thanks a lot!
: of course also to the other major developers ☺
I would like to test it. Is it possible to make a zip which can be flashed via CWM?
Best wishes, Christian
Click to expand...
Click to collapse
Yes i could make a zip but i am not free currently

Otherwise working fine, but doesn't seem to recognise my external memory card. Is there option to enable it or any idea what is causing it?

ElakNovAlamak said:
Otherwise working fine, but doesn't seem to recognise my external memory card. Is there option to enable it or any idea what is causing it?
Click to expand...
Click to collapse
Is it in Exfat format?

allram said:
Is it in Exfat format?
Click to expand...
Click to collapse
Fat32. This is first time having this kind of trouble. So far every rom and recovery has detected it ok.

ElakNovAlamak said:
Otherwise working fine, but doesn't seem to recognise my external memory card. Is there option to enable it or any idea what is causing it?
Click to expand...
Click to collapse
allram said:
Is it in Exfat format?
Click to expand...
Click to collapse
I have searched and tested and have two theories
1- The stock fstab that i used with is in jf-common/rootdir/qcom.fstab has messed up because of the heavy edits i had to make there .
2- It needs some patch that i am not finding .
extra ,
maybe needs a kernel commit or something
i would flash twrp again and test the external sd i have
edit : it doesn't show and the fstab seams fine to me ( i did double check)

Good start. All the red touch screen errors scare me on a recovery that is so critical to what I do. It needs to read / write external SD card. Hope it gets finished and not dropped halfway there.

Pkt_Lnt said:
Good start. All the red touch screen errors scare me on a recovery that is so critical to what I do. It needs to read / write external SD card. Hope it gets finished and not dropped halfway there.
Click to expand...
Click to collapse
I am trying my best with twrp , getting it to run on our phone is a success on its own , but i also encourge people to try the philz touch as i really like the extra features it offers .

mythi said:
I am trying my best with twrp , getting it to run on our phone is a success on its own , but i also encourge people to try the philz touch as i really like the extra features it offers .
Click to expand...
Click to collapse
You realize, via the link to Philz in your first post, that it is an abandoned product, right? Of the three recoveries, TWRP offers the only hope for improvements and bug fixes. CWM is antiquated and brain dead. Philz abandoned, that leaves TWRP half way, (sigh)

Pkt_Lnt said:
You realize, via the link to Philz in your first post, that it is an abandoned product, right? Of the three recoveries, TWRP offers the only hope for improvements and bug fixes. CWM is antiquated and brain dead. Philz abandoned, that leaves TWRP half way, (sigh)
Click to expand...
Click to collapse
TWRP will newer support exFAT, so Phill - the best.

d8389 said:
TWRP will newer support exFAT, so Phill - the best.
Click to expand...
Click to collapse
Did you meant TWRP will never support exFAT?

Pkt_Lnt said:
Did you meant TWRP will never support exFAT?
Click to expand...
Click to collapse
TWRP might support f2fs but i don't know about exfat , any way about the progress of mounting the sdcard i got the option to display on mount settings but nothing happenes upon click that so gonna dig more :crying:

Does "no exFAT support" also means no FAT32 support? Because with this TWRP my ext-sdcard is not selectable, only internal storage

defim said:
Does "no exFAT support" also means no FAT32 support? Because with this TWRP my ext-sdcard is not selectable, only internal storage
Click to expand...
Click to collapse
no actually the recovery has broken sdcard support

Dear Mithy,
could you please release an updated TWRP for our i9295? Latest version is now 2.8.3.0
Thank you very much, and happy new year!

so you are saying that the sgh-i537 has been boot unlocked?

Major-Hardon said:
so you are saying that the sgh-i537 has been boot unlocked?
Click to expand...
Click to collapse
Lol thanks for getting my hopes up but I'm 99% sure this recovery is for the international model (sgh-i9295). I'm not a gambling man but it sounds like the bootloader getting unlocked for our i537 is just never gonna happen. And if it did you'd hear about it, it'd be all over this phone's forum

[NO LONGER MAINTAINED][RECOVERY][supersonic]TWRP touch recovery

UPDATE: I am no longer posting on XDA.​
Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
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.
Click to expand...
Click to collapse
Images
Installation instructions
TWRP Image Install method:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed.
Download the latest version of TWRP appropriate for your device/firmware
Reboot to TWRP
Hit Install and tap the "Install Image" button in the lower right
Browse to the location of the TWRP image on your device and select it
Select recovery from the partition list and swipe to flash
Alternate Installation Method:
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on their computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
Code:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
Code:
fastboot flash recovery twrp.img
Code:
fastboot reboot
Click to expand...
Click to collapse
Device Changelog
Current version: 3.1.1-0:
Code:
[LIST]Initial official release[/LIST]
Older Device-specific versions:
Code:
[LIST]N/A[/LIST]
Click to expand...
Click to collapse
TWRP Official Changelog
Current version: 3.1.1:
Code:
[LIST]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)[/LIST]
Older versions:
Code:
[SIZE="4"][COLOR="Green"]3.1.0:[/COLOR][/SIZE]
[LIST]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 [URL="https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9"]here[/URL] (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[/LIST]
[SIZE="4"][COLOR="Green"]3.0.3:[/COLOR][/SIZE]
[LIST]Partial release to help support the release of the [URL="https://www.xda-developers.com/team-win-releases-their-first-official-twrp-app-in-the-play-store/"]Official TWRP app[/URL][/LIST]
[SIZE="4"][COLOR="Green"]3.0.2:[/COLOR][/SIZE]
[LIST]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.[/LIST]
[SIZE="4"][COLOR="Green"]3.0.1:[/COLOR][/SIZE]
[LIST]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[/LIST]
[SIZE="4"][COLOR="Green"]3.0.0:[/COLOR][/SIZE]
[LIST]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[/LIST]
[U]Additional Notes[/U]
[LIST]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 updated 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![/LIST]
[SIZE="4"][COLOR="Green"]2.8.7.0:[/COLOR][/SIZE]
[LIST]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)[/LIST]
[U]Additional Notes[/U]
[LIST]Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
[*]System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
[*]resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
[*]This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at [url]https://jenkins.twrp.me[/url] and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at [url]https://gerrit.twrp.me[/url] to help us keep devices up to date and working.[/LIST]
Click to expand...
Click to collapse
Downloads
Download
Latest Official versions
Sources
Device tree
Kernel source
Click to expand...
Click to collapse
Known Issues
None
Click to expand...
Click to collapse
Bug Reporting
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If your issue is determined to be 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 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!
Click to expand...
Click to collapse
Additional Help/Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
XDA:DevDB Information
Team Win Recovery Project (TWRP), Tool/Utility for the HTC EVO 4G
Contributors
Captain_Throwback, Dees_Troy, bigbiff, _that
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Current Stable Version: 3.1.1-0
Stable Release Date: 2017-05-18
Created 2015-03-20
Last Updated 2018-03-07

Device-specific Information
Reserved for FAQ (if needed)

Ty captain,
I like the new additions can't wait to check it out.
+1
Sent from my SM-G900P

2.8.6.0 has been uploaded.

2.8.7.0 has been uploaded.

Anybody tried the new TWRP yet?

Captain_Throwback said:
Anybody tried the new TWRP yet?
Click to expand...
Click to collapse
Working on maKing a Wi-Fi only phone for my cousins birthday out of my old evo I tried to find "supersonic" in the twrp app but it didn't come up. Would you be able to fix that or should I just install it manually?

paridoth said:
Working on maKing a Wi-Fi only phone for my cousins birthday out of my old evo I tried to find "supersonic" in the twrp app but it didn't come up. Would you be able to fix that or should I just install it manually?
Click to expand...
Click to collapse
What TWRP app? There's no official TWRP app. The install method is listed on the Download page for the device and in the OP here.

On the download page it links to the twrp manager app. I am installing over clockwork mod so can't install with recovery and I don't have access to a computer.

paridoth said:
On the download page it links to the twrp manager app. I am installing over clockwork mod so can't install with recovery and I don't have access to a computer.
Click to expand...
Click to collapse
Yeah, that's not an official TWRP app. You can disregard that. You can try Flash Image GUI or Flashify to flash recovery to your device, if you have to use an app, but I never recommend using an app if fastboot is available .

Yea I tried flashify but it locked up. Could I put it in a pc36img.zip and flash it from bootloader?

paridoth said:
Yea I tried flashify but it locked up. Could I put it in a pc36img.zip and flash it from bootloader?
Click to expand...
Click to collapse
What about Flash Image GUI? There's a free version available on XDA (last time I checked).
The bootloader method should also work, it just requires having an appropriate android-info.txt.

I'll try flash image gui and report back thanks!
---------- Post added at 10:28 AM ---------- Previous post was at 10:17 AM ----------
Is this the right one? https://play.google.com/store/apps/details?id=com.joeykrim.flashimagegui

paridoth said:
I'll try flash image gui and report back thanks!
---------- Post added at 10:28 AM ---------- Previous post was at 10:17 AM ----------
Is this the right one? https://play.google.com/store/apps/details?id=com.joeykrim.flashimagegui
Click to expand...
Click to collapse
Did you find more than one?

Just wasn't sure that was the right one. I found it on xda. Flashed twrp 3.0 rebooted to recovery but it took me to the boot loader. Tried again same thing. I'll try flashing an older version

paridoth said:
Just wasn't sure that was the right one. I found it on xda. Flashed twrp 3.0 rebooted to recovery but it took me to the boot loader. Tried again same thing. I'll try flashing an older version
Click to expand...
Click to collapse
You might just have to wait until you get to a PC and do it via fastboot. That way should work without issue.

Unfortunately I'm in hospital so no computer access. I flashed an older version and that worked when I get out I'll try flashing 3.0 with adb thanks!

paridoth said:
Unfortunately I'm in hospital so no computer access. I flashed an older version and that worked when I get out I'll try flashing 3.0 with adb thanks!
Click to expand...
Click to collapse
If you got a previous version installed, you should be able to flash the new version from within TWRP (as indicated in the OP).

Unfortunately it was 2.7 I installed I tried 2.8 but had the same issue

paridoth said:
Unfortunately it was 2.7 I installed I tried 2.8 but had the same issue
Click to expand...
Click to collapse
Is your EVO on the last available software update? I believe it was 5.07.651.6 or something like that?