FORUMS

I/O Summary: How Android M Handles Power And Charging

In the spirit of improving the core Android experience, Google is changing Android … more

I/O Summary: Google Photos App

At I/O 2015, Google tackled the information problem in mobile once more, this time through … more

I/O Summary: Development, Play Store, The Next Billion

VP of Engineering Jen Fitzpatrick began talking about what Google is doing to … more

I/O Summary: Google Now on Tap

Google is all about organizing the world’s information to make it universally useful, and these … more

[RECOVERY][deb/flo] TWRP 2.8.6.0 touch recovery [2015-03-26]

Thanks Meter: 10,585
 
Post Reply Subscribe to Thread Email Thread
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.6.0:

-Fix daylight savings time rules for USA and Europe (_that)
-Allow mulitple overlays for popup boxes (Dees_Troy)
-Add pattern style password entry for decrypt (Tassadar)
-Keyboard improvements (_that)
-Update AOSP base to 5.1 (Dees_Troy)
-Reduce theme count to 5 and rely on scaling (Dees_Troy)
-Various scaling improvements (Dees_Troy)
-Improved handling of resources in the GUI (_that)
-Make scroll bar size proportional to list size (_that)
-Allow scoll lists to render without a header (_that)
-Make console scroll per pixel with kinetic scrolling (_that)
-Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
-Various other fixes and improvements (mdmower, bigbiff, codelover, etc)

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.

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 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; 26th March 2015 at 06:19 AM.
The Following 110 Users Say Thank You to Dees_Troy For This Useful Post: [ View ]
 
 
27th July 2013, 01:00 AM |#2  
Dees_Troy's Avatar
OP Senior Recognized Developer
Flag KC MO
Thanks Meter: 10,585
 
Donate to Me
More
Reserved
The Following 6 Users Say Thank You to Dees_Troy For This Useful Post: [ View ]
27th July 2013, 01:01 AM |#3  
Dees_Troy's Avatar
OP Senior Recognized Developer
Flag KC MO
Thanks Meter: 10,585
 
Donate to Me
More
You may need the new SuperSU beta for 4.3 to get root working, not sure.

Thanks to viperboy for testing.
The Following 9 Users Say Thank You to Dees_Troy For This Useful Post: [ View ]
27th July 2013, 01:02 AM |#4  
aooga's Avatar
Senior Member
Flag California
Thanks Meter: 953
 
More
Already??? Wow, thanks!

---------- Post added at 05:02 PM ---------- Previous post was at 05:01 PM ----------

Quote:
Originally Posted by Dees_Troy

You may need the new SuperSU beta for 4.3 to get root working, not sure.

Thanks to viperboy for testing.

Thats right. The old one doesn't work on my Nexus 4, so I dont think it will work here either.
The Following User Says Thank You to aooga For This Useful Post: [ View ]
27th July 2013, 01:09 AM |#5  
Mr. Steve's Avatar
Senior Member
Flag Newark, Delaware
Thanks Meter: 64
 
More
Quote:
Originally Posted by aooga

Already??? Wow, thanks!

---------- Post added at 05:02 PM ---------- Previous post was at 05:01 PM ----------



Thats right. The old one doesn't work on my Nexus 4, so I dont think it will work here either.

I believe SuperSU got an update yesterday so that you don't need to use the beta app on 4.3
27th July 2013, 01:10 AM |#6  
tw1tch175's Avatar
Senior Member
Thanks Meter: 99
 
More
Flashing now, will update when Im rooted with custom recovery

Running perfectly, flashed chainfires root and installer supersu and now my nexus 7 is rooted and I am happy!
Last edited by tw1tch175; 27th July 2013 at 01:19 AM.
27th July 2013, 01:17 AM |#7  
Mr. Steve's Avatar
Senior Member
Flag Newark, Delaware
Thanks Meter: 64
 
More
Quote:
Originally Posted by tw1tch175

Flashing now, will update when Im rooted with custom recovery

The suspense is killing me.
27th July 2013, 01:18 AM |#8  
ATGAdmin's Avatar
Senior Member
Flag Western NY State
Thanks Meter: 1,050
 
More
Why is the recovery for our device called "TWRP for Nexus 7 2013 [flo]" and not "[razor]"?
27th July 2013, 01:22 AM |#9  
Mr. Steve's Avatar
Senior Member
Flag Newark, Delaware
Thanks Meter: 64
 
More
Quote:
Originally Posted by ATGAdmin

Why is the recovery for our device called "TWRP for Nexus 7 2013 [flo]" and not "[razor]"?

The device codename is razor while the board id is flo. On the old Nexus 7 for example, the device codename was nakasi while the board id was grouper.
The Following User Says Thank You to Mr. Steve For This Useful Post: [ View ]
27th July 2013, 01:24 AM |#10  
Senior Member
Thanks Meter: 62
 
More
YAYYYYYYYYYY, finally I got ROOT on new Nexus 7
The Following User Says Thank You to phuduong For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes