Post Reply

[RECOVERY][sprat] TWRP 2.8.5.0 touch recovery [2015-02-12]

OP Dees_Troy

26th July 2014, 03:56 AM   |  #1  
Dees_Troy's Avatar
OP Senior Recognized Developer
Flag KC MO
Thanks Meter: 10,300
 
1,639 posts
Join Date:Joined: Mar 2008
Donate to Me
More
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.

Phone look:


Tablet look:


CHANGELOG for 2.8.5.0:

-Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-Improve thread handling and move input handling into the main rendering thread to improve stability
-Make MTP work even if unplugged and plugged back in
-Unify scrollable list code and make kinetic scrolling feel more natural
-Fix handling of mapped zip files for OTA updates (CM12 updater)
-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
-Other small fixes and improvements

CHANGELOG for 2.8.4.0:

-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
-Fix some MTP related crashes and bugs
-Eliminate TWRP toggling USB IDs during boot if MTP is enabled
-Fix various adb sideload issues
-Improve threading of actions
-Eliminate separate thread for screen timeout
-Update libblkid to 2.25.0
-Use power button as back button on watch themes for easier navigation
-Add mutex locking to data manager
-Improve custom theme handling on encrypted devices
-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens

CHANGELOG for 2.8.3.0:

-MTP will now tell the host PC that storage is removed instead of disabling MTP completely
-MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
-Update and improve fix permissions and make fixing contexts optional
-Update SuperSU in TWRP to 2.40 and update install process
-Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
-Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
-Fix kernel panic during MTP start on some devices
-Support unicode fonts on devices with True Type Font support
-Fix slider value not showing sometimes (vibration settings page)
-Toggle MTP off during adb sideload to set correct USB IDs
-Reduce library requirements for 5.0 L decrypt
-Other minor fixes and improvements

Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.

CHANGELOG for 2.8.2.0:
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates

Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9

So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.

DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
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 by Dees_Troy; 13th February 2015 at 04:20 PM.
The Following 11 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: 10,300
 
1,639 posts
Join Date:Joined: Mar 2008
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: 48
 
189 posts
Join Date:Joined: Jul 2005
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: 10
 
53 posts
Join Date:Joined: Nov 2004
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: 10
 
53 posts
Join Date:Joined: Nov 2004
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
 
4 posts
Join Date:Joined: May 2009
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: 48
 
189 posts
Join Date:Joined: Jul 2005
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: 10,300
 
1,639 posts
Join Date:Joined: Mar 2008
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
 
4 posts
Join Date:Joined: May 2009
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..

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes