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

Dees_Troy

Senior Recognized Developer
Mar 31, 2008
1,705
13,536
0
KC MO
www.teamw.in
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.
 
Last edited:

Dees_Troy

Senior Recognized Developer
Mar 31, 2008
1,705
13,536
0
KC MO
www.teamw.in
Thanks to @AdamOutler for testing!

It took a lot of effort to make this happen. Adam was able to get UART working. When the kernel source dropped I compiled a kernel. We used information from the UART output to determine correct addresses for kernel, ramdisk, and tags to make our first image. We could tell that it was init'ing and booting via the UART output, but no adb. We were eventually able to get adb by kanging the init.rc from the LG G Watch which allowed us to finally get a rooted shell via adb to dump the factory images. From there we determined that TWRP needed to use Qualcomm's overlay graphics to get display working. With that and some more init.rc work we got TWRP booting up and adb working. With 4 cores running, the Gear Live gets very hot and the battery drains quickly. With more changes to the init.rc we're now running with only 2 cores with a max frequency of 600MHz to keep thermals and battery drain in check.

The theme is undersized. Hopefully next week I can work on upscaling the the 240x240 theme up to 320x320 to fit the full screen. Still, for now I present the first fully working recovery for the Gear Live.

Manual install instructions.

Download folders with current and prior versions:
Mirror 1
Mirror 2
 
Last edited:

rant

Senior Member
Nov 7, 2004
76
18
0
Recovery installed fine, but now my only option appears to boot into recovery, regardless of what I select from twrp or bootloader, cannot boot into the OS.
 
  • Like
Reactions: AdamOutler

zav22

Member
May 19, 2009
5
4
0
Same issue here. Recovery seemed to install fine, but every time I try to boot to system it loops back to recovery. Trying to figure out Adams factory image too. Doesn't seem like there's a download mode on the watch so I assume odin is out?
 

skitty

Senior Member
Jul 17, 2005
207
49
0
I installed twrp fine using fastboot flash recovery recovery.IMG. have to use a PC to boot into it tho

Sent from my D6503 using XDA Premium 4 mobile app
 

Dees_Troy

Senior Recognized Developer
Mar 31, 2008
1,705
13,536
0
KC MO
www.teamw.in
Those of you who flashed TWRP to the boot partition can download the boot.img from Adam's dump of the stock software and flash it using fastboot mode with this command:
fastboot flash boot boot.img
 
  • Like
Reactions: hav0c

zav22

Member
May 19, 2009
5
4
0
Still no luck. Flashed stock boot.img. Trying to boot to system returns to TWRP. Trying to install SuperSU, factory wipe, or ADB sideload all generate errors "unable to mount '/data'", '/data/media', storage, etc. Applying KVM78X update will get me as far as the spinning colored dots..
 

jeffrey1790

Senior Member
Oct 8, 2011
65
32
0
Niagara Falls
Those of you who flashed TWRP to the boot partition can download the boot.img from Adam's dump of the stock software and flash it using fastboot mode with this command:
fastboot flash boot boot.img


did a fastboot oem unlock;fastboot flash recovery recovery.img;fastboot flash boot rootADB.img and it still boots into twrp when i turn my watch on
 

lichti1901

Senior Member
Sep 28, 2010
4,140
9,308
0
Riding my Bike
Flashed twrp yesterday and run into the same issues as some others here.

1. Unlocked bootloader (fastboot oem unlock)
2. falashed twrp afterwards (fastboot flash recovery nameofrecovery.img)
3. boot into recovery and played with it a little
4. tried to reboot system, but it boots straight into recovery again
5. Flashed boot.img from Adam´s system dump (fastboot flash boot boot.img) .... still the same-boot straight to recovery again
6. flashed system.img from system dump (fastboot flash system system.img) .... the same
7. flashed recovery from system dump (fastboot flash recovery recovery.img) ... system tries to boot, but bootloops.
8. Now the funny thing, i cant get into bootloader mode, only in the menu where you can enter download mode, upload mode, recovery and power off, tried to adb sideload the rom but that doesnt work because adb and fastboot dont work, notebook doesnt recognize the watch.

Seems like i bricked it.

If anyone have ideas what else i can do or know something i i dont know, please help me out. :angel:

Regards, lichti
 

jeffrey1790

Senior Member
Oct 8, 2011
65
32
0
Niagara Falls
Flashed twrp yesterday and run into the same issues as some others here.

1. Unlocked bootloader (fastboot oem unlock)
2. falashed twrp afterwards (fastboot flash recovery nameofrecovery.img)
3. boot into recovery and played with it a little
4. tried to reboot system, but it boots straight into recovery again
5. Flashed boot.img from Adam´s system dump (fastboot flash boot boot.img) .... still the same-boot straight to recovery again
6. flashed system.img from system dump (fastboot flash system system.img) .... the same
7. flashed recovery from system dump (fastboot flash recovery recovery.img) ... system tries to boot, but bootloops.
8. Now the funny thing, i cant get into bootloader mode, only in the menu where you can enter download mode, upload mode, recovery and power off, tried to adb sideload the rom but that doesnt work because adb and fastboot dont work, notebook doesnt recognize the watch.

Seems like i bricked it.

If anyone have ideas what else i can do or know something i i dont know, please help me out. :angel:

Regards, lichti
Ended up doing that exact thing. And it seemed to work for me. Hmm.
 

Dees_Troy

Senior Recognized Developer
Mar 31, 2008
1,705
13,536
0
KC MO
www.teamw.in
I pushed out a 2.7.1.1 update with a full screen 320x320 theme included.

The proper process for unlocking the bootloader is to fastboot oem unlock then fastboot reboot. Let the device boot up normal after unlocking so that it completes the wipe of the data partition. For those that are stuck in a bootloop because you flashed and/or booted TWRP first, try going to Wipe -> Format Data and type yes to complete the wipe then let the Gear Live boot normally.
 

Dees_Troy

Senior Recognized Developer
Mar 31, 2008
1,705
13,536
0
KC MO
www.teamw.in
Where are backups stored? Phone, right?
No, there's no Bluetooth in recovery and even if there was, the transfer rates would be slow and probably consume a lot of battery. Both the Gear Live and G Watch have 4GB emmc chips in them with about 3GB of user accessible storage. The backups are stored directly on the watch.
 

JoeFCaputo113

Senior Member
Feb 2, 2013
6,614
2,850
0
New York
No, there's no Bluetooth in recovery and even if there was, the transfer rates would be slow and probably consume a lot of battery. Both the Gear Live and G Watch have 4GB emmc chips in them with about 3GB of user accessible storage. The backups are stored directly on the watch.
How big is the AVG backup? And cool I did not know that!

Also, in your opinion, what are the benefits as it stands right now to rooting, installing a custom recovery on the Live?