Jump to content

[RECOVERY] TWRP 2.4.2.0 touch recovery [2013-02-26]


Guest Dees_Troy

Recommended Posts

Guest Dees_Troy

Thanks to walaway for being persistent and helping test to get the graphics to actually display on the screen.

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:

RAsb.jpgAO13.jpg

Tablet look:

7zXg.jpgnkUM.jpg

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!

CHANGELOG for 2.3.3.0:

-Fix renaming backups with a space in the name

-Add decrypt button to mount page if you cancel decryption during startup

-Added ignore blkid flag

-Fixed handling of MTD partitions during mount

-Fixed some keyboard mapping issues on 800x1280 layout

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 rafael_mfr

Wow! Finally first step was done!

Now let's get custom rom shows begin!!!

Thanks a lot!

edit --------------------------------

twrp works smoothly

Edited by rafael_mfr
Link to comment
Share on other sites

anyone are tried mount the internal SDcard over recovery? I have drivers erros in Windows7

I think there isn't an option in this recovery for use internal data of PF2 as usb disk.

For to install driver, for use ADB, you have to modify the android_winusb.inf file in asus driver folder (you can download it from asus site) adding this lines under [ASUS.NTx86], if you have a x86 OS, or under [ASUS.NTamd64], if you have a x64 OS:

%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001

%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0228

If you have win 8, you have to disable signature driver.

As always sorry for my English :)

Link to comment
Share on other sites

  • 3 weeks later...
Guest Koplinjp

Guys, after reading some things about it, do not flash TWRP and keep stock rom! It seans that TWRP corrups the partitions and you'll brick the phone (this happened to me...)! For now, my humbble advice is keep stock recovery or install clockworkmod recovery...

Link to comment
Share on other sites

Guest phoenixg36

I have created a backup with TWRP 2.4.4.0 and everything worked.

But when I turn on compression, the backup stops after the system partition.

Can someone confirm?

Link to comment
Share on other sites

  • 4 weeks later...
Guest Dees_Troy

Just FYI, you should not be installing official updates from Asus using TWRP or if you've modified your device. Official updates are not designed to be installed on modified devices and may cause a brick. (This really should go without saying but it seems that a lot of PF2 owners are not aware of this caveat about modifying their devices.)

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.