FORUMS

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

1,674 posts
Thanks Meter: 11,291
 
Post Reply Subscribe to Thread Email Thread
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.



CHANGELOG for 3.0.0-0:

-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It wonít be perfect and especially some languages that require large font files like Chinese & Japanese wonít be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROMís Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks

WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You donít want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.

Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.

Version number notes: For a while weíve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.

We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!

CHANGELOG for 2.8.7.0:

-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option Ė more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)

Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.

System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP wonít prompt to install SuperSU and TWRP wonít try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.

resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images donít take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.

This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.

DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!

BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!

SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Last edited by Dees_Troy; Yesterday at 08:48 PM.
The Following 12 Users Say Thank You to Dees_Troy For This Useful Post: [ View ]
 
 
26th July 2014, 03:57 AM |#2  
Dees_Troy's Avatar
OP Senior Recognized Developer
Flag KC MO
Thanks Meter: 11,291
 
Donate to Me
More
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 by Dees_Troy; 26th July 2014 at 05:06 AM.
The Following 11 Users Say Thank You to Dees_Troy For This Useful Post: [ View ]
26th July 2014, 10:06 AM |#3  
Senior Member
Thanks Meter: 49
 
More
TWRP installed and backup made. Let the custom ROMs begin

Sent from my D6503 using XDA Premium 4 mobile app
26th July 2014, 04:07 PM |#4  
Member
Thanks Meter: 14
 
More
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.
The Following User Says Thank You to rant For This Useful Post: [ View ]
26th July 2014, 09:32 PM |#5  
Quote:
Originally Posted by rant

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.

Sounds like you did Fastboot flash boot recovery.img.
The Following User Says Thank You to AdamOutler For This Useful Post: [ View ]
26th July 2014, 11:04 PM |#6  
Member
Thanks Meter: 14
 
More
Quote:
Originally Posted by AdamOutler

Sounds like you did Fastboot flash boot recovery.img.

Crap, you may be right. Any suggestions on how to resolve? I did download your factory image but not sure where to start
26th July 2014, 11:13 PM |#7  
Junior Member
Thanks Meter: 4
 
More
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?
26th July 2014, 11:24 PM |#8  
Senior Member
Thanks Meter: 49
 
More
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
27th July 2014, 12:09 AM |#9  
Dees_Troy's Avatar
OP Senior Recognized Developer
Flag KC MO
Thanks Meter: 11,291
 
Donate to Me
More
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
The Following User Says Thank You to Dees_Troy For This Useful Post: [ View ]
27th July 2014, 01:07 AM |#10  
Junior Member
Thanks Meter: 4
 
More
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..
27th July 2014, 01:10 AM |#11  
Member
Flag Niagara Falls
Thanks Meter: 32
 
More
Quote:
Originally Posted by Dees_Troy

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

Read More
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes