Jump to content

[RECOVERY] TWRP 2.5.0.0 touch recovery for PadFone 1 [2013-04-22]


Guest Dees_Troy

Recommended Posts

Guest Dees_Troy

Thanks to oroo708 for helping test.

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:

AgsV.pngWujW.png

Tablet look:

eIDZ.pngfYob.png

CHANGELOG for 2.5.0.0:

Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.5.0.0 as your custom theme will likely not be compatible with the new changes!

-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection

-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)

-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache

-Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)

-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)

-Fixed a problem with md5 verification of backups

-Added a search function to libtar (thanks to kokotas)

-Improve handling of XML errors (fix permissions)

-Fixed handling of subpartitions

-Improvements to recovery.fstab flags

-Fixed a problem with decryption not being able to locate the decryption key in some situations

CHANGELOG for 2.4.4.0:

-Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)

-More fixes for the file selector

-Switched from using busybox md5sum to a direct C function call

-Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again

-Update exFAT to latest commits

-Added a build flag to disable using the ioctl for screen blanking

CHANGELOG for 2.4.3.0:

-Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)

NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.

-Added a scroll bar to file selectors and listboxes courtesy of Tassadar

-Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff

-Added a screen dim effect 2 seconds before screen off on some devices

-Finally fixed file selector crash (one of the joys of working with multi-threaded software)

-Fixed loading of screen timeout setting during startup

-Improvements and bugfixes to screen timeout code

-Fixed persistence of the 24 hour / military time setting

CHANGELOG for 2.4.2.0:

-Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices

-Add a brightness setting (requires device specific setup and only some devices have been added)

-Add a root checker and offer to install SuperSU if the device isn't already rooted

-Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems

-Check and offer to fix root permissions if broken

-Add an option for a 24 hour clock display instead of AM/PM (aka military time)

-Move stock recovery reflash check to occur during the reboot cycle

-Add support for some MTK6xxx devices

-Change libtar to vfork to help prevent memory problems

-Add a "clicked" effect to most buttons, file selector, and listbox

-Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)

-Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)

-Other minor bugfixes and improvements

CHANGELOG for 2.4.1.0:

-Fixed a problem with mkdosfs that formatted sdcards to 2GB

-Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)

-Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting

-Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)

CHANGELOG for 2.4.0.0:

-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)

-Support for exFAT formatted sdcards (also thanks to bigbiff)

-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)

-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running

-Added wipe cache and dalvik after ADB Sideload

-Replaced many system calls with their native C counterparts

-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder

-Fixed AOSP recovery commands to run after decryption on encrypted devices

-Improvements for building TWRP in CM10.1

-Other minor bugfixes and improvements

NOTE: 2.4.0.0 is, as always, still compatible with your older backups!

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.

Link to comment
Share on other sites

Guest Dees_Troy

Note, if you plan to take an official update from Asus, you need to revert back to stock including stock recovery. Do not install official updates on modified devices or using a custom recovery.

Link to comment
Share on other sites

  • 7 months later...
Guest Mr.Clark

I realise I'm well behind the curve, but I've just discovered that ASUS released a bootlock remover tool, so I'm trying to give the old Padfone a new lease of life.

Thanks for bringing the custom recovery to Google's attention!

 

If anyone else gets here from a web search, note that TWRP have updated to 2.6.3.0 which can be found on their website - http://techerrata.com/browse/twrp2/A68

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.