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

Search This thread

johnannis

Senior Member
Oct 16, 2012
344
96
Thessaloniki
I THINK there is a problem with that recovery.
When i go to backup it sais who many MBs will the data,boot,cache,etc take.
But when i restore the backup it says how many MBs were restored (you know what i mean :p)
And there had been restored about 100MB less :confused:
While i also noticed that the XDA app was missing after restore (maybe more apps i dindnt notice)
 

Malaquai

Senior Member
Aug 21, 2011
286
38
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

Can't change file sort order in file managers, for example when try to install a ROM.

Enviado desde mi M3 usando Tapatalk 2
 

diegons49

Senior Member
Mar 3, 2013
142
30
Salvador
Samsung Galaxy M51
First of all, thank you for this great recovery.

By accessing the menu "Advanced Wipe" I have seven options:

[ ] Dalvik Cache
[ ] Cache
[ ] Date
[ ] Micro
[ ] SDcard
[ ] Internal SDcard <=
[ ] Internal SDcard <=
[ ] System

As we can see, there are two options exactly alike, it would be a bug?
 

francois64

Senior Member
May 8, 2009
380
53
59
Pau ( France )
Hello
I have 2.6 version from Goomanager but i don't know why i can't see "recovery" option in restart menu ?
Can you please explain how to set this option ?
Thanks.
 

johnannis

Senior Member
Oct 16, 2012
344
96
Thessaloniki
The Power menu has to do with your rom, not the recovery.
So you need to do it manually with vol down or download a rebooter app

Sent from my MB860 using xda app-developers app
 
  • Like
Reactions: francois64

chelsea_fc

Senior Member
Sep 15, 2007
519
20
Jakarta
Any flashable zip for the latest twrp 2.6.3.0? Cant seem find one, goo.im server currently down

Sent from my XT907 using Tapatalk
 

eSu.Matix

Senior Member
Apr 21, 2011
561
140
Berlin
have you tried downloading the img file and flashing it via fastboot? or unpacking a previous zip, removing the old twrp, adding the new twrp, and rezipping?

What?
For what I've know I downloaded TWRP from Google Play so I don't have it in flashable format. And he's asking for the "NEW" recovery, cause Goo.im servers are down and you can't download it from GooManager. There is no sense in what you're saying.
 
Last edited:

palmbeach05

Senior Member
Oct 12, 2012
4,333
1,853
Motorola Atrix HD
AT&T Samsung Galaxy S III
  • Like
Reactions: mutil and eSu.Matix

eSu.Matix

Senior Member
Apr 21, 2011
561
140
Berlin
download any zip from here http://techerrata.com/browse/twrp2/olympus
unzip
open twrp
delete recovery.img
go back to http://techerrata.com/browse/twrp2/olympus and download 2.6.3.0 recovery.img
rename openrecovery-twrp-2.6.3.0-olympus.img to just recovery.img
place 2.6.3.0 recovery.img file in twrp folder from above.
re-zip file
move file to device
reboot recovery
install zip from sd card
reboot recovery
enjoy

Well your method didn't work. It gave me an error, but I flashed it with fastboot. Thanks for the provided links for the .img file.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 72
    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.
    11
    I just made a update.zip for 2.2: http://4by.in/3
    9
    [RECOVERY] TWRP 2.5.0.0 touch recovery [2013-04-09]
    8
    [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]
    6
    Updated to 2.2.2.0!