[RECOVERY][otter] TWRP 3.1.0-0 touch recovery [2017-03-10]

[RECOVERY][otter] TWRP 3.1.0-0 touch recovery [2017-03-10] - Kindle Fire Android Development

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

id love to try this out, but from the comments on the site, it appears that the commands listed do not work... also i have a mac so its probably different.

Sweet! I'll have to try this out!

I just gave the new version a quick run around the block...
PROS: The distribution is no longer a boot image that forces a flash of the old FFF 1.0 along with TWRP. It's now an actual recovery image that can be flashed through fastboot like... "fastboot flash recovery twrp-fire-2.1.0.img"
CONS: Even though there are some more reboot options in this new version, they are all still broken. Just as in 2.0.0, none of the reboot options (system, recovery, bootloader... I'm assuming the last one is supposed to boot into fastboot mode) will reset the bootmode accordingly before the device is restarted. That makes these options pretty useless as the device will still continue to boot in the previous bootmode. So, the TWRP bootloops will continue to plague new users who have no idea how to get it to boot to the system.... bummer.

I love that we got this! Buuuuttttt I like 2.0 just fine. Its stable. It works. love to see progress though.
Sent from my Kindle Fire using XDA

its great to see progress, but as kinfaun said reboot is still broken.
Sent from my HTC Glacier using xda premium

smirkis said:
its great to see progress, but as kinfaun said reboot is still broken.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
thats a deal breaker for me... thanks for the update tho

I spoke with deestroy n were gonna try to get it resolved. yay lol
they don't have our device so its hard to know what doesn't work. looking forward to testing the update
Sent from my HTC Glacier using xda premium

smirkis said:
I spoke with deestroy n were gonna try to get it resolved. yay lol
they don't have our device so its hard to know what doesn't work. looking forward to testing the update
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Sweet id switch back if it was fixed i like how its skinable

i cant install any zip files i get unknown md5 error just rooted tonight

nckfrs said:
i cant install any zip files i get unknown md5 error just rooted tonight
Click to expand...
Click to collapse
I just tried playing around with the new version some more and I can confirm the above...
Here's what I get from TWRP's Install section for the few ROMs I tried to test flash.
Code:
-- Verify md5 for /sdcard/update-cm7-wipeall.zip
-- No md5 file found, ignoring
-- Installing /sdcard/update-cm7-wipeall.zip ...
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "blaze" || getprop("ro.build.product") == "blaze"
E:Error in /tmp/sideload/package.zip
(Status 7)
* Verifying filesystems...
* Verifying partition sizes...
Error flashing zip '/sdcard/update-cm7-wipeall.zip'
This version is really not ready for use. Hang on to your version 2.0.0 for at least a little while longer.

While I agree its not ready it did work for me to make a back up and then install Hashcode's test rom and restore a back up another user posted for us.

Reboot to system works perfectly fine for me, and has in previous versions as well.

Reboot to system works fine for me to. Always has.
Sent from my LG-P999 using Tapatalk 2

treUse said:
Reboot to system works perfectly fine for me, and has in previous versions as well.
Click to expand...
Click to collapse
dw9906 said:
Reboot to system works fine for me to. Always has.
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
Yeah it will, until you assign the bootmode outside of using the power button from firefirefire (in other words, use fastboot, adb or 'reboot recovery' from a rom to set the bootmode) the reboot wrappers won't set it back. It is actually a relatively simple solution and Smirkis' is familiar with what's required if he is talking to the OP I would expect a solution for this.

treUse said:
Reboot to system works perfectly fine for me, and has in previous versions as well.
Click to expand...
Click to collapse
dw9906 said:
Reboot to system works fine for me to. Always has.
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
If you used the power button to get into recovery while FFF was loading, reboot to system will work fine. That's not what's being discussed here.
If you got to recovery that way, the bootmode was never changed and stayed (presumably) on 4000. So, hitting the reboot from within TWRP will continue to boot in normal mode and it "seems" to work fine.
Try setting the bootmode to recovery (5001) and restart the device to get to TWRP. Then if you try rebooting into the system, it will go back into TWRP because TWRP does not change the bootmode back to normal (4000) before attempting to reboot into the system.
The same problem exists for all the reboot options in 2.1.0... whether normal, recovery, or bootloader, it will not change the bootmode to the appropriate value before restarting the device. As a result, the device will just reboot using whatever bootmode is already set.
EDIT: What Sblood86 said above... I'm just longer winded.

I knew what you meant, but that's not what you explained in your first post. Had you been this specific in your initial post then this conversation would have never happened.
On another note, this recovery might as well be forgotten about. Doesn't seem like they are ever going to fix it completely.
EDIT: Didn't mean for that to sound like i was being rude to kinfauns. That's not how i meant it to be.
Sent from my LG-P999 using Tapatalk 2

dw9906 said:
I knew what you meant, but that's not what you explained in your first post. Had you been this specific in your initial post then this conversation would have never happened.
On another note, this recovery might as well be forgotten about. Doesn't seem like they are ever going to fix it completely.
EDIT: Didn't mean for that to sound like i was being rude to kinfauns. That's not how i meant it to be.
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
I wasn't offended by your post, so you shouldn't take this post that way either... but I don't think you read the thread very carefully before you posted. I think I was fairly clear about what the problem entailed in my first post of this thread. I made it a point to mention that TWRP does not set the bootmode properly before rebooting. In addition, smirkis noted that he's gotten the developer's ear in getting some problems fixed, so things are looking up in terms of getting past these issues.
Furthermore, TWRP can't simply be "forgotten about" because the super majority of articles on the Internet detailing steps in modifying the Kindle Fire mention TWRP. New users will continue to use TWRP just for the fact that it's simply the more recognized recovery program of the two we have available.
FWIW, I'm more hopeful than ever TWRP will get fixed and continued to be developed.

I really do hope it gets fixed. I really like the themeing capabilities. It's a great recovery, just doesn't seem to have much support.
Sent from my LG-P999 using Tapatalk 2

clockwork recovery ftw.

Related

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

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.2-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

Cha-Ching, THANK YOU TEAM-WIN! Thanks a Bunch been waiting for an official - will test if SD card slot is working.
UPDATE: Works Great!

Confirmed reading from the sd card. Diddnt try to flash from sd card, but it reads it. And the interface is nice in comparison. All I did was fix permissions and it worked.
Sent from my SG3 using GSM (Team Sonic) + Trinity
http://supercentral.net

Awesome!!! Been using TWRP on my Nook for awhile now. Love it! Thanks for this.

How do u make it back up to ext sdcard? Also anyone know the commands for terminal emulator...thanx in advance
Edit....nvmd figured it very nice ty!

sarni84 said:
How do u make it back up to ext sdcard? Also anyone know the commands for terminal emulator...thanx in advance
Edit....nvmd figured it very nice ty!
Click to expand...
Click to collapse
Mind sharing the info. Thanks.
Sent from a Galaxy far far away

now that this is official can we flash cm9 without changing the script?

cwalker0906 said:
now that this is official can we flash cm9 without changing the script?
Click to expand...
Click to collapse
Yeah, is this able to flash cm9 correctly?

neotoky said:
Mind sharing the info. Thanks.
Sent from a Galaxy far far away
Click to expand...
Click to collapse
It's super easy ! When you click backup, there is two boxes at the bottom saying "Use external SD" and "Use Internal Storage". Use internal is by default.

I was under the impression that TWRP supported adb in recovery, though this version does not seem to work. Is that something that is being worked on, or just not gonna happen?

lumbu said:
I was under the impression that TWRP supported adb in recovery, though this version does not seem to work. Is that something that is being worked on, or just not gonna happen?
Click to expand...
Click to collapse
Worked just fine for me.
mounted /system and pushed a few files successfully.

neotoky said:
Mind sharing the info. Thanks.
Sent from a Galaxy far far away
Click to expand...
Click to collapse
Also to install its even easier. Download goomanager from market its free. Then go into it hit your menu button on phone then hit " install open recovery script" .....it will download and install the latest version (which is this one) for u and as far as using external sd goes for backups. When u hit backup just select external

overground said:
Worked just fine for me.
mounted /system and pushed a few files successfully.
Click to expand...
Click to collapse
Yep, my bad. Needed to install the naked adb drivers instead of the Samsung ones I first installed. Is that what you have installed?

lumbu said:
Yep, my bad. Needed to install the naked adb drivers instead of the Samsung ones I first installed. Is that what you have installed?
Click to expand...
Click to collapse
My adb driver installation for this device was such a nightmare (Win7 64).
This is what finally worked for me (follow the link trail).
http://forum.xda-developers.com/showpost.php?p=27921718&postcount=278

Took the plunge and just flashed CM9 nightly with no problems. Cheers!

Thank you guys, this is much better than the touch CWM!
The SD card option is terrific!

Does flashing this with GooManager trip the flash counter?

hypmatize said:
Does flashing this with GooManager trip the flash counter?
Click to expand...
Click to collapse
Does it matter anymore?
There is already a way to reset the flash counter.

ipaq_101 said:
Does it matter anymore?
There is already a way to reset the flash counter.
Click to expand...
Click to collapse
Yeah true... but why trip it when you don't have to

hypmatize said:
Does flashing this with GooManager trip the flash counter?
Click to expand...
Click to collapse
No, only flashing a non-stock file through Odin increases the flash counter. Nothing you do on your phone, including Mobile Odin, trips the counter.

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

Reserved

Reserved.

Works for me. Thanks!

Fixed adb and added USB OTG support. I'll be looking to upscale the theme and add decrypt support when I have more time.

Thanks for this, Dees. I'll see to it that one of my writers puts this on the front page.

Dees_Troy said:
Fixed adb and added USB OTG support. I'll be looking to upscale the theme and add decrypt support when I have more time.
Click to expand...
Click to collapse
Forgive my ignorance, but does this also root the device, or do I need to root first?
The ability to backup to OTG USB is excellent - thanks.

Lumsdoni said:
Forgive my ignorance, but does this also root the device, or do I need to root first?
The ability to backup to OTG USB is excellent - thanks.
Click to expand...
Click to collapse
Root after installing TWRP by flashing SuperSU in TWRP.

Awesome thanks just wondering, does this have the random reboot issue like cwm?
Sent from my Galaxy Nexus using Tapatalk 2

draco259 said:
Awesome thanks just wondering, does this have the random reboot issue like cwm?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
It doesn't. This recovery works perfectly, other than the theme issue. CWM has also been fixed by damien667.

Man i LOOVEEE TWRP... thanks for this, cant wait to try it tonight

willverduzco said:
It doesn't. This recovery works perfectly, other than the theme issue. CWM has also been fixed by damien667.
Click to expand...
Click to collapse
Awesome thanks for the info
Sent from my Galaxy Nexus using Tapatalk 2

willverduzco said:
Root after installing TWRP by flashing SuperSU in TWRP.
Click to expand...
Click to collapse
I am confused... how can you give goomanager root access if the tab isn't rooted already?

You can't. You will have to install it through fastboot.
Sent from my GT-N7100 using xda app-developers app

draco259 said:
Awesome thanks just wondering, does this have the random reboot issue like cwm?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I was able to figure out what was needed to prevent the reboot. I pushed my device configuration files to the team win github if you really want to take a look or compile your own. Good news is that I can compile from source without having to repack manually.

Randomwalker said:
You can't. You will have to install it through fastboot.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
ah... ok.. i must have gotten confused when one of the admins said to root it after installing twrp using goomanager..
EDIT: So these direction from post #1 are totally wrong? if randomwalker is correct?
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:

That's if you are already rooted, go with the or option.
Sent from my Galaxy Nexus using Tapatalk 2

I installed and got into TWRP fine the first time.Now I'm stuck in a boot loop. It has been sitting for 30 minutes with just the X flashing.
I can get into the bootloader and TWRP fine but the system will not boot just sits with the flashing X..

Mike02z said:
I installed and got into TWRP fine the first time.Now I'm stuck in a boot loop. It has been sitting for 30 minutes with just the X flashing.
I can get into the bootloader and TWRP fine but the system will not boot just sits with the flashing X..
Click to expand...
Click to collapse
Did you just unlock it? If so, reboot into TWRP and go to the wipe section. Format Data & Wipe Cache & you will be good to go.

Same as user above with bootloops. I tried wiping cache/delvik and also factory reset but it says failed everytime in red at the top of TWRP. Im lost. Does the same with stock CWM Touch also. I downloaded the pre rooted factory rom but cannot access sd through mounting to flash that rom either. An ideas as far as sending the file to sd using adb commands?

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

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

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