[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16]

Search This thread

raisage

Senior Member
Oct 27, 2010
163
68
Toronto
min.us
I flashed it yesterday. Definitely smoother in some sense. Like scrolling actually scrolls and doesn't just move by tab. It's pretty cool! There are also a few new things, like in wipe you can wipe USB_OTG. I have no idea what that is, but they added it!

USB On-The-Go is if you have a male microUSB-to-female USB adapter, you can connect USB peripherals (in this case, a thumbdrive or other storage device) to your phone.
 

bzhmobile

Senior Member
Feb 11, 2010
1,191
388
Paris
Version 2.7 is available :)
What's new in 2.7.0.0:

Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
Allow sideloading from /tmp on encrypted devices
Check for a crypto footer before asking for a password to prevent user confusion
Additional checks for validity to auto generated backup names
Text wrap in the console output
Proper caps lock support in the keyboard
Mouse support via USB OTG for devices with a broken digitizer
Improve scanning of storage locations for OpenRecoveryScript
Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions
Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
Update SuperSU to 1.93 and improve installation process
Added selinux contexts restoration to fix permissions
Load RTC offset on Qualcomm devices to fix the date/time in recovery
USB Mass Storage fixes Add SELinux support checking
Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
Add 4.4 decrypt support
Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
Various SELinux fixes and bug fixes

openrecovery-twrp-2.7.0.0-evita.img

Size: 8.9 MB
MD5: 0eb7f3d14d75a019b19757836a1ec805
 

FiyreWyrkz

Member
May 8, 2011
27
1
Victoria, British Columbia
Seems to me that the new version (2.7.0.0) has some issues with mounting as USB. Not sure if anyone else can confirm? I have tried re-flashing the recovery multiple times. Until this is fixed I guess it's the still the unofficial TWRP for those looking //needing// to flash 4.4+ ROMS.
 

liamstears

Senior Member
Nov 8, 2007
2,287
1,739
Kent
Seems to me that the new version (2.7.0.0) has some issues with mounting as USB. Not sure if anyone else can confirm? I have tried re-flashing the recovery multiple times. Until this is fixed I guess it's the still the unofficial TWRP for those looking //needing// to flash 4.4+ ROMS.

Works fine here for me...

Also made my own theme for the recovery, attached it if anyone wants to try it (Theme is only compatible with 2.7.0.0)
 

Attachments

  • ui.zip
    585.5 KB · Views: 21
  • Like
Reactions: bzhmobile

Top Liked Posts

  • There are no posts matching your filters.
  • 131
    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.6.3.0:
    -Proper backup and restore of SELinux contexts (thanks to Tassadar)
    -Pull in some ROM information for backup name generation
    -Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
    -Add 1200x1920 theme (thanks to Tassadar)
    -A few other fixes and tweaks

    CHANGELOG for 2.6.1.0:
    -Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
    -Initial support for f2fs file system formatting (Moto X)
    -Update SuperSU install for 4.3 ROMs
    -Fixed a permissions bug on files created during backup
    -Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
    -Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
    -Ignore lost+found folder during backup and size calculations
    -Various other minor bug fixes and tweaks

    CHANGELOG for 2.6.0.0:
    Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
    -Can encrypt a backup to prevent theft of private data from your backup files
    -Updated graphics / icon courtesy of shift
    -Updated exFAT to latest commits
    -Fixed a problem with Samsung TouchWiz decryption
    -Update SuperSU binary
    -Fixed saving of backup partitions list
    -Fixed saving of last used zip install folder
    -Fixed backup of datadata on devices that use a separate partition for datadata
    -Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
    -Fixed some problems with partitioning a SD card
    -Various other bug fixes and tweaks

    Notes about encrypted backups:
    Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.

    Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.

    DOWNLOAD:
    The fastest and easiest way to install TWRP is to use the GooManager app:
    Play Store Link
    Direct Download
    1) Install GooManager from the Play Store
    2) Open GooManager and provide root permissions
    3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
    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.

    XDA:DevDB Information
    [RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16], a Tool/Utility for the AT&T HTC One X

    Contributors
    eyeballer, dees_troy, bigbiff

    Version Information
    Status: Stable
    Current Stable Version: 2.6.3.0
    Stable Release Date: 2013-09-16

    Created 2013-09-16
    Last Updated 2013-09-16
    13
    Updated to 2.4.4.0
    9
    Updated OP with 2.4.2.0
    9
    Updated OP with 2.4.0.0
    8
    Updated to 2.2.1.4 which fixes adb and brings the device up to the latest codebase (small bug fixes). It's live on our website and in Goo manager.

    Thanks again to Turge for testing.