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

Dees_Troy · Apr 10, 2012

[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.

That Baker Guy · Apr 10, 2012

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.

AustinFire · Apr 10, 2012

Sweet! I'll have to try this out!

kinfauns · Apr 10, 2012

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.

AFAinHD · Apr 10, 2012

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

smirkis · Apr 11, 2012

its great to see progress, but as kinfaun said reboot is still broken.

Sent from my HTC Glacier using xda premium

DJLamontagneIII · Apr 11, 2012

smirkis said:
its great to see progress, but as kinfaun said reboot is still broken.

Sent from my HTC Glacier using xda premium

thats a deal breaker for me... thanks for the update tho

smirkis · Apr 11, 2012

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

DJLamontagneIII · Apr 11, 2012

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

Sweet id switch back if it was fixed i like how its skinable

nckfrs · Apr 11, 2012

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

kinfauns · Apr 11, 2012

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

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.

raiderep · Apr 11, 2012

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.

treUse · Apr 11, 2012

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

dw9906 · Apr 11, 2012

Reboot to system works fine for me to. Always has.

Sent from my LG-P999 using Tapatalk 2

Sblood86 · Apr 11, 2012

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

dw9906 said:
Reboot to system works fine for me to. Always has.

Sent from my LG-P999 using Tapatalk 2

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.

kinfauns · Apr 11, 2012

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

dw9906 said:
Reboot to system works fine for me to. Always has.

Sent from my LG-P999 using Tapatalk 2

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.

dw9906 · Apr 11, 2012

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

kinfauns · Apr 11, 2012

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

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.

dw9906 · Apr 11, 2012

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

d33dvb · Apr 12, 2012

clockwork recovery ftw.

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

Senior Recognized Developer

Senior Member

Senior Member

Retired Senior Moderator and Retired DC Lead

Senior Member

Senior Member

Senior Moderator

Senior Member

Senior Moderator

Senior Member

Retired Senior Moderator and Retired DC Lead

Senior Member

Senior Member

Senior Member

Inactive Recognized Developer

Retired Senior Moderator and Retired DC Lead

Senior Member

Retired Senior Moderator and Retired DC Lead

Senior Member

Senior Member

Similar threads

Top Liked Posts