FORUMS
Remove All Ads from XDA

[RECOVERY][ariel] TWRP 2.8.6.0 touch recovery [2015-06-07]

3,628 posts
Thanks Meter: 4,496
 
By jmz, Inactive Recognized Developer on 7th June 2015, 04:37 PM
Post Reply 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. It’s 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:
  1. Fix daylight savings time rules for USA and Europe (_that)
  2. Allow mulitple overlays for popup boxes (Dees_Troy)
  3. Add pattern style password entry for decrypt (Tassadar)
  4. Keyboard improvements (_that)
  5. Update AOSP base to 5.1 (Dees_Troy)
  6. Reduce theme count to 5 and rely on scaling (Dees_Troy)
  7. Various scaling improvements (Dees_Troy)
  8. Improved handling of resources in the GUI (_that)
  9. Make scroll bar size proportional to list size (_that)
  10. Allow scoll lists to render without a header (_that)
  11. Make console scroll per pixel with kinetic scrolling (_that)
  12. Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
  13. Various other fixes and improvements (mdmower, bigbiff, codelover, etc)

CHANGELOG for 2.8.5.0:
  1. 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
  2. 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)
  3. Improve thread handling and move input handling into the main rendering thread to improve stability
  4. Make MTP work even if unplugged and plugged back in
  5. Unify scrollable list code and make kinetic scrolling feel more natural
  6. Fix handling of mapped zip files for OTA updates (CM12 updater)
  7. USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
  8. Other small fixes and improvements

CHANGELOG for 2.8.4.0:
  1. Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
  2. Fix some MTP related crashes and bugs
  3. Eliminate TWRP toggling USB IDs during boot if MTP is enabled
  4. Fix various adb sideload issues
  5. Improve threading of actions
  6. Eliminate separate thread for screen timeout
  7. Update libblkid to 2.25.0
  8. Use power button as back button on watch themes for easier navigation
  9. Add mutex locking to data manager
  10. Improve custom theme handling on encrypted devices
  11. 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:
  1. MTP will now tell the host PC that storage is removed instead of disabling MTP completely
  2. 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)
  3. Update and improve fix permissions and make fixing contexts optional
  4. Update SuperSU in TWRP to 2.40 and update install process
  5. Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
  6. Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
  7. Fix kernel panic during MTP start on some devices
  8. Support unicode fonts on devices with True Type Font support
  9. Fix slider value not showing sometimes (vibration settings page)
  10. Toggle MTP off during adb sideload to set correct USB IDs
  11. Reduce library requirements for 5.0 L decrypt
  12. 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.
The Following 9 Users Say Thank You to jmz For This Useful Post: [ View ] Gift jmz Ad-Free
 
 
7th June 2015, 04:37 PM |#2  
jmz's Avatar
OP Inactive Recognized Developer
Flag Lawton, OK
Thanks Meter: 4,496
 
More
Everything seems to be working. No known issues. USB-OTG works also

Download

or use our TWRP Manager software to install it automatically for you



Install either by DD or maybe flashify will work for you.

Code:
dd if=recovery.img of=/dev/block/mmcblk0p7
Thanks goes to @Dees_Troy as this was my first MediaTek based device to build recovery for

This will also be taken official this week.
The Following 5 Users Say Thank You to jmz For This Useful Post: [ View ] Gift jmz Ad-Free
7th June 2015, 05:39 PM |#3  
jmz's Avatar
OP Inactive Recognized Developer
Flag Lawton, OK
Thanks Meter: 4,496
 
More
Pulled download temporarily
The Following User Says Thank You to jmz For This Useful Post: [ View ] Gift jmz Ad-Free
7th June 2015, 06:21 PM |#4  
Senior Member
Thanks Meter: 4
 
More
Thanks for your work dude but we do not have recovery image for our Fire 6 HD sadly ...
7th June 2015, 06:22 PM |#5  
jmz's Avatar
OP Inactive Recognized Developer
Flag Lawton, OK
Thanks Meter: 4,496
 
More
Quote:
Originally Posted by alucard_xs

Thanks for your work dude but we do not have recovery image for ou Fire 6 HD sadly ...

The HD 7 and HD 6 are EXACTLY the same device. The OTAs for both are EXACTLY the same. The only difference is the screen size. There essentially is no difference betweent the 2 devices
7th June 2015, 06:25 PM |#6  
Senior Member
Thanks Meter: 4
 
More
Sure but what about factory / recovery image, is there anyone floating around ?
7th June 2015, 06:25 PM |#7  
jmz's Avatar
OP Inactive Recognized Developer
Flag Lawton, OK
Thanks Meter: 4,496
 
More
Quote:
Originally Posted by alucard_xs

Sure but what about factory / recovery image, is there anyone floating around ?

just dump your current recovery.img.

dd if=/dev/block/mmcblk0p7 of=/sdcard/stockrecovery.img

Then as soon as you boot into recovery make a backup.
7th June 2015, 07:10 PM |#8  
Senior Member
Thanks Meter: 37
 
More
Root
Will flashing the SuperSU package in recovery root, or cause a bootloop?
7th June 2015, 07:11 PM |#9  
jmz's Avatar
OP Inactive Recognized Developer
Flag Lawton, OK
Thanks Meter: 4,496
 
More
Quote:
Originally Posted by ryanyz10

Will flashing the SuperSU package in recovery root, or cause a bootloop?

Dont need to flash anything with TWRP. If you boot twrp then choose reboot to system option it will ask if you want to install SuperSU.
The Following User Says Thank You to jmz For This Useful Post: [ View ] Gift jmz Ad-Free
7th June 2015, 11:34 PM |#10  
jmz's Avatar
OP Inactive Recognized Developer
Flag Lawton, OK
Thanks Meter: 4,496
 
More
Reuploaded fixed version. Found a couple bugs that i didn't notice before. All good now
7th June 2015, 11:59 PM |#11  
Senior Member
Thanks Meter: 942
 
More
So for us the slow ones, can you explain this in detail?
You've replaced the stock recovery with TWRP, so we can flash images from USB drives ? But you need root to do the first flash to recovery, correct?
Will Amazon update re-write the recovery partition so you are back to stock ?
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