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

[Dees_Troy]

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.

 

[Dees_Troy]

Reserved!

 

[stevehkim]

Patiently awaiting the day I can see TWRP on my screen!!

 

[goobieracing]

Recovery before a unlocked bootloader... awesome!!!

Sent from my SAMSUNG-SGH-I337 using xda premium

 

[scoot05redss]

Awesome, I can't wait to be able to install. Now here comes the "I just loaded through goo manager and now I can't boot!" posts!

 

[theo1998]

Can this work on the Canadian (i337M) version?

 

[sd_N]

Links not uploaded??

The links go to download site however no recovery is shown..... are they uploaded yet? Thank you so much for this..

 

[PeterGuru]

It installed perfectly on my Rogers SGH-I337M, although, it definitely has some bugs.

When setting the backup name, the keyboard is ultra-sensitive; you often get multiple entries even with the slightest touch.

The time it's completely off. Mine is about 1h45m fast and, yes, I have the settings set properly with Eastern Time Zone Selected, and the Daylight Saving Time option checked.

Also, the backup file is huge; almost 4GB, and while the backup was in progress, it stated that it had to break up the file into multiple archives.

Otherwise, great work so far.

PETER

Addendum: I installed TWRP through Goo Manager. Also, touching the screen did not work to get the device out of sleep mode while in TWRP. I had to use the Home button.

Sent from my SGH-I337M using xda premium

 

[David Dee]

It installed perfectly on my Rogers SGH-I337M, although, it definitely has some bugs.

When setting the backup name, the keyboard is ultra-sensitive; you often get multiple entries even with the slightest touch.

The time it's completely off. Mine is about 1h45m fast and, yes, I have the settings set properly with Eastern Time Zone Selected, and the Daylight Saving Time option checked.

Also, the backup file is huge; almost 4GB, and while the backup was in progress, it stated that it had to break up the file into multiple archives.

Otherwise, great work so far.

PETER

Sent from my SGH-I337M using xda premium

I've got to say Peter, you've got serious kahunas flashing this. Thanks man, appreciate it! The question I have: Is the I337M bootloader unlocked, or is your test indicative of what would happen on all 337 variants when flashing TWRP?

 

[PeterGuru]

Please don't talk about my kahunas without first getting permission from my wife.

What I'm about to say is not gospel but, according to MobileSyrup, all Canadian variants have an unlocked bootloader. It appears to be true, that is, with the Rogers variant, as I have been able to boot into TWRP effortlessly, and maintain root, not to mention having done all that AFTER performing a system update.

Peter

Sent from my SGH-I337M using xda premium

 

[David Dee]

On M-syrup, Dan Badder really knows his stuff, I doubt he would say it was unlocked without being damn sure. I just did a search and found his comment (good to know one of us has the attention span to read the full review). For others, here is his comment:

"It appears that Samsung has left the device’s bootloader alone on the Canadian builds which, unlike on the AT&T model, means there shouldn’t be an issue loading new software on it. The problem is that because the Canadian model shares the same underlying architecture as the aforementioned U.S. variant, initial availability of custom ROMs and kernels will be limited due to a shortage of developers with access to the phone’s bootloader. This is an unfortunate situation alleviated somewhat by the fact that the device runs Android 4.2.2, the latest version of the Android software."

I just got the device today, rooted before the ota to be safe, and now the update won't work because my device is "Modified". Did the update make any difference whatsoever? Would be good to know if it is worth installing via odin when the firmware becomes available.

 

[PeterGuru]

I was having serious lag prior to the update, much of it now solved following the update, although, some lag still exists. There's simply too much bloat on the device. After all, the TWRP backup file was 4GB.

By the way, you can unroot your device and reverse everything back to stock it you want to install the update. There's another thread somewhere that explains how to do it, which is what I did.

Peter

Sent from my SGH-I337M using xda premium

 

[David Dee]

I was having serious lag prior to the update, much of it now solved following the update, although, some lag still exists. There's simply too much bloat on the device. After all, the TWRP backup file was 4GB.

By the way, you can unroot your device and reverse everything back to stock it you want to install the update. There's another thread somewhere that explains how to do it, which is what I did.

Peter

Sent from my SGH-I337M using xda premium

Thanks Peter! Found the thread, unrooted (didn't even factory reset) and the ota loaded like a charm. It is good to see a lot of the quality people from the GS3 gang here. This year really flew by!

 

[creepyncrawly]

...it really wasn't too much of a risk. I've only had the device for two days, so I'm still within the 15-day return period, plus I've got a few tricks up my sleeve when returning rooted and modified devices. Had things gone terribly wrong, I simply would have brought it back and gotten a new one.

I find it interesting how many people here think nothing of announcing publicly that they are willing to commit fraud against the various carriers, or recommend that others do so. I realize that there are two camps on this issue. Many apparently would do this, but many of us feel it is just plain morally wrong. It is not unlikely that behavior such as this has been a factor in the decision to lock the phones down. For now, the Canadian carriers evidently haven't done so, but this kind of behavior won't encourage them to stay open.

 

[thuglifesk]

Successfully installed on bell i337m.

 

[scott14719]

I find it interesting how many people here think nothing of announcing publicly that they are willing to commit fraud against the various carriers, or recommend that others do so. I realize that there are two camps on this issue. Many apparently would do this, but many of us feel it is just plain morally wrong. It is not unlikely that behavior such as this has been a factor in the decision to lock the phones down. For now, the Canadian carriers evidently haven't done so, but this kind of behavior won't encourage them to stay open.

No thank you, I'll make up my own mind about what I think is moral or immoral.

 

[lessthanzach]

I find it interesting how many people here think nothing of announcing publicly that they are willing to commit fraud against the various carriers, or recommend that others do so. I realize that there are two camps on this issue. Many apparently would do this, but many of us feel it is just plain morally wrong. It is not unlikely that behavior such as this has been a factor in the decision to lock the phones down. For now, the Canadian carriers evidently haven't done so, but this kind of behavior won't encourage them to stay open.

I'm finding it interesting that your signature includes information about flashing kernels without increasing your flash counter and how to prepare your phone to send to warranty for replacement. Kind of ironic I suppose.

Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

 

[Mike]

I'm finding it interesting that your signature includes information about flashing kernels without increasing your flash counter and how to prepare your phone to send to warranty for replacement. Kind of ironic I suppose.

Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Getting your device unrooted and ready for standard hardware repair is much different then bricking the device out of personal negligence and committing fraud to get a new one.

Sent from my SAMSUNG-SGH-I337 using xda app-developers app

 

[lessthanzach]

Getting your device unrooted and ready for standard hardware repair is much different then bricking the device out of personal negligence and committing fraud to get a new one.

Sent from my SAMSUNG-SGH-I337 using xda app-developers app

And I quote "Prepare your phone to return to the store or for warranty replacement"
Maybe you should look at the person's signature I mentioned prior to attempting to correct me, thanks.
Also, for what other reason would you need to inhibit a flash counter besides warranty fraud? Please enlighten me.

Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

 

[evilive27]

Just tried on my Rogers i337m. Works like a charm. Thank you!

Sent from my SGH-I337M using xda app-developers app