For those of you who have been waiting for the triumphant return of TWRP 2. Well wait no longer! TWRP 2 is back for the supersonic with 100% less bricking!*
*Anything is possible... we take no responsibility for actual outcome on your device
Team Win Recovery Project 2.2, 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:
v2.2.1 - various bugfixes and HTC Dumlock support now built in for latest hboots that don't support flashing to /boot.
CHANGELOG (for 2.2.0):
- On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
- Name new backups and rename existing backups
- Rename files and folders in the file manager
- Pseudo-terminal emulator
- Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
- Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
- Simplified XML layout support between resolutions
- Added dual storage selection radio buttons to zip install, backup, and restore pages
- Improved zip install compatibility
- Updated update-binary source code
- Numerous small bug fixes and improvements
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app
For downloads and instructions please visit our TWRP website and choose your device in the dropdown menu
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 30 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.
DL does not work
jminor4326 said:
DL does not work
Click to expand...
Click to collapse
Some regions have been experiencing routing issues with our domain today. Kind of crappy. Links do work since others have been able to download, but they don't work for me personally either. :/
ViViDboarder said:
Some regions have been experiencing routing issues with our domain today. Kind of crappy. Links do work since others have been able to download, but they don't work for me personally either. :/
Click to expand...
Click to collapse
I too am having this problem is there any chance of a mirrorfor those of us going thru TWRP withdrawals
Sent from my PC36100 using XDA Premium App
I'll have to give this a try.
Thanks for your hard work.
Got it from the twrp website today from the other thread . So far I'm loving it.
Sent from my PC36100 using xda premium
Flashing Now Thank You.
This is nice. I'm using it now, backing up, but having some strange issues with tapping the icons on the middle of the bottom of the screen.
Working on grabbing the directly dl links.
Zip:
http://techerrata.com/file/twrp2/PC36IMG-twrp-supersonic-2.0.0RC0.zip
Img:
http://techerrata.com/file/twrp2/twrp-supersonic-2.0.0RC0.img
attached is the recovery.log for the failure to wipe data (factory reset). Let me know if anything further is required.
http://dl.dropbox.com/u/8128460/recovery.log
I flashed version 2, when I rebooted, I didn't rename the PCIMG36.ZIP but even after I did rename it by manually taking the card out and doing it in a USB drive, I am ONLY booting to the white screen on my Evo. Help, I am in an endless loop that it only boots into the white screen on my evo. I can't get the system to boot up past the white screen with the three androids on skateboards. I can get back to recovery, flashed back to 1.1.1 TWRP, but what did I do wrong?
Any and all help would be most appreciated.
Help.
Btw. Rename it to sometying with recovery in the name and you can use flash image GUI with the the .img file
Sent from my PC36100 using xda premium
SD-EXT
I don't have any useful information unfortunately but same problem as in twrp 1.1.1 it doesn't find my sd-ext ext3 partition created with AmonRA2.3 so I either have the choice of redoing the phone to use this or stick with Amon. I'll probably redo the phone because this recovery is nice!
Thank you noticed that quickly after typing this. I'll redo my phone next day or so and I'm sure that will remedy the problem. Very nice work though!
Last note: wiped everything tried to partition using 2.0 and it says successful but still won't mount ext.
bhint15 said:
I don't have any useful information unfortunately but same problem as in twrp 1.1.1 it doesn't find my sd-ext ext3 partition created with AmonRA2.3 so I either have the choice of redoing the phone to use this or stick with Amon. I'll probably redo the phone because this recovery is nice!
Click to expand...
Click to collapse
Yea, that issue is being tracked on Github. So we are looking into it.
Do u have a version coming for the Droid incredible
Sent from my Touchpad using xda premium
Takes. While to load on evo any special button to hit to go in.
Sent from my Touchpad using xda premium
This looks pretty amazing! A full GUI in recovery is like UEFI on pc's!
was able to flash rom fine ....... tried checking md5 sum said no md5 sum
Kchitown1977 said:
was able to flash rom fine ....... tried checking md5 sum said no md5 sum
Click to expand...
Click to collapse
Yea, for the md5 it looks for filename.zip.md5 with the checksum.
Sent from my Touchpad using xda premium
I am getting a loop of the boot animation when I try to flash some roms, like JaredTheGreat's ICS Port
Related
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.
Changelog: See our website!
FAQ:
How to install the zip:
1. Download and copy PG58IMG.zip to root of sdcard
2. Rename the zip to exactly PG58IMG.zip using a file explorer like Astro
3. Reboot into BOOTLOADER
4. Let it detect the zip
5. Select Vol UP when it says Do you want to start update?
6. Wait for it to flash
7. Press Power to reboot
8. Let the phone reboot into the regular Android OS
9. Use a file manager like Astro to rename, move, or delete the PG58IMG.zip file so that hboot doesn't try to flash it again
10. Reboot into recovery and enjoy
Error when flashing some zip files:
twrp only supports the latest and greatest edify script for zip flashing. Please bug the zip developer to update the zip script to edify.
Does twrp support off-mode charging?
Yes, but it won't charge while you're in recovery!
Which partitions do I need to back up for a proper backup?
Usually you just need boot, data, and system for a normal backup. If you don't know what you are doing, then these are usually the only ones that you need to back up and restore.
Live support:
Click this link or join us in #twrp on Freenode IRC.
Awesome! Many thanks for this! Will try asap.
Edit:
Installed Flawlessly and is looking great! Good Job! Backup compression is an awesome feature, but really takes some time...nandroid is running for 20 minutes and just reached /data
anyway, this recovery is definitely pure win!
Sent from my HTC Sensation Z710e using Tapatalk
Cool. Thanks fellas. I'll test out in a minute. And i think all zips are edify now adays.. I hope.
Sent from my HTC Sensation Z710e using XDA Premium App
Looks nice, any Pictures ?
EDIT:
Found ^^
Shaquiel Harris said:
Cool. Thanks fellas. I'll test out in a minute. And i think all zips are edify now adays.. I hope.
Click to expand...
Click to collapse
You'd be surprised... or maybe you wouldn't.
Nice! I always wanted to see this on the sensation, great job!
Sent from my HTC Sensation Z710e using Tapatalk
When the battery hits 0, does it glitch like cwm? it becomes a pain to turn back on
Awesome, i'm glad TeamWin is on board building this for the Sensation. I was hoping for it when i saw it being built for the Evo 3D.
Thanks!
Awesome work!
Knucklessg1 said:
When the battery hits 0, does it glitch like cwm? it becomes a pain to turn back on
Click to expand...
Click to collapse
At this point, yes, it probably will. It's a side-affect of the way HTC implemented charging on these new devices. That's part of the reason that we've been trying to implement a charge percentage indicator.
Dees_Troy said:
At this point, yes, it probably will. It's a side-affect of the way HTC implemented charging on these new devices. That's part of the reason that we've been trying to implement a charge percentage indicator.
Click to expand...
Click to collapse
Ah so it doesn't charge while off. Back to cwmr thanks though.
Sent from my HTC Sensation Z710e using XDA Premium App
Any "serious" advantages to this recovery??
Or is it a whatever feels better for you kinda deal??
Sent from my HTC Sensation 4G using XDA App
Ok i made this recovery into a flashable zip from bootloader
1. Download and copy PG58IMG.zip to root of sdcard
2. Reboot into BOOTLOADER
3. Let it detect the zip
4. Select Vol UP when it says Do you want to start update?
5. Wait for it to flash
6. Press Power to reboot and enjoy your new recovery
Download link on our site updated with flashable PG58IMG.zip. FAQ updated with install instructions. Credit to xboarder56 for the zip's creation. Thanks!
Couldn't charge while off be implemented in a similar fashion?
http://forum.xda-developers.com/showpost.php?p=16251759&postcount=876
Great stuff team win! Be glad when battery charge is fixed ...
Nice. No more CWM for me.
I currently prefer the safety net that CWM provides ito charging while off. Looks good though.
You didn't think of calling it the TeamWin Easy Recovery Project (twerp) LOL
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.
Changelog: See our website!
FAQ:
Install as a Flashable Zip? [RECOMMENDED]
Download flashable zip from the OP and rename it "PG06IMG.zip" (without the quotes)
Place in the root of the sdcard
Power off phone (make sure you turn off hot boot or pull the battery when it's off)
Power on the phone holding power and volume down
Follow the prompts to flash it
Delete .zip (PG06IMG.zip) after booting
Enjoy
How to install with Fastboot:
Download the fastboot binary for your computer from HTC
Connect your phone and boot it into fastboot
Run fastboot with the command
Code:
fastboot flash recovery path/to/recovery-twrp-speedy-1.1.0.img
Does this back up Wimax partition?
That is an option if you chose. Recommended to make at least one backup of just wimax and store that somewhere safe.
The screen went black after doing [insert random function]. What is the issue?
When testing the recovery early on we noticed fastboot wasnt a stable way to flash the recovery. Random issues would arise after using the method. As a result and a solution, flashing the recovery via the PG06IMG.zip is recommended to avoid such issues. Please try this as a solution.
I found a bug! What do I do?
Well you're probably going to want to post here and see if other people are having the same issue. We're also going to start tracking bugs on Github along with our project. This will let you see what issues we are aware of. You can submit a bug here: https://github.com/TeamWin/Team-Win-Recovery-Project/issues Be sure to include how you came about the issue as well as list your device and how you installed twrp.
Have a great new feature idea for TWRP?
Submit it on our Github page! It'll help us track it and notify you of the progress. https://github.com/TeamWin/Team-Win-Recovery-Project/issues
Why should I use this over ClockworkMod?
While all three recoveries offer roughly the same abilities (backup, restore, flash) we feel like ours adds a bit more in addition to the basics as well as blend some of the more useful features. A few differences to hightlight:
USB Mass Storage mode (Not in CWM)
Re-organized menus with most commonly used features on top
Saveable settings for all preferences selected
Date and battery display (configurable timezones)
Ability to auto-reboot after flashing
Color themes
Capacitive button support
Go a head and give it a try! You've got nothing to lose. If you don't like it you can always roll back to whatever recovery you want. Of course, shift might go all Emo Pony on us, but he'll get over it.
Sweet! First post! Time to get rid of rom manager!
Teleported from my Shifty Speedy using Tapatalk
Nice! Congrats on the release on the evo shift!
Thank you for this amazing recovery teamwin! Way way better then anyone ever expected! CWM will prolly never be used again lol
Supremely Shifted
ZOMFG!!
yeah, i'm pretty sure this is wood i'm sporting
Yeah, been using this since last night, it is awesome. And clockwork did have USB storage mode, its in the advanced settings, not that it matters anymore.
Found bug....
Rom: CM7 nightly 214(latest)
Kernel: PershootV9
Twrp install method: bootloader
Bug: whenever I go to fix permissions, the green progress bar will go all the way to them end and then freeze... I did it twice to make sure, but i needed to pull the battery both times
Teleported from my Shifty Speedy using Tapatalk
thronnos said:
Found bug....
Rom: CM7 nightly 214(latest)
Kernel: PershootV9
Twrp install method: bootloader
Bug: whenever I go to fix permissions, the green progress bar will go all the way to them end and then freeze... I did it twice to make sure, but i needed to pull the battery both times
Teleported from my Shifty Speedy using Tapatalk
Click to expand...
Click to collapse
Same thing here.. Had to do a battery pull.
Sent from my PG06100 using Tapatalk
Haha... You can still use RM to reboot to TWRP recovery and when I tried to backup my ROM (through RM) (just to see what would happen) it just sends me to TWRP recovery as well...
from the "CRACKED" Speedy EVO Engine...
thronnos said:
Found bug....
Rom: CM7 nightly 214(latest)
Kernel: PershootV9
Twrp install method: bootloader
Bug: whenever I go to fix permissions, the green progress bar will go all the way to them end and then freeze... I did it twice to make sure, but i needed to pull the battery both times
Teleported from my Shifty Speedy using Tapatalk
Click to expand...
Click to collapse
Are you sure you just didn't give it enough time? I've noticed that the progress bars actually bear no relation to the actual progress. I'm fixing permission in terminal now and I can tell you, it takes foreffingever. Haven't tried in recovery yet but I know not to believe the progress bar.
EDIT: In terminal it took 8min 24secs.
good job man. . .thank you
jesusice said:
Are you sure you just didn't give it enough time? I've noticed that the progress bars actually bear no relation to the actual progress. I'm fixing permission in terminal now and I can tell you, it takes foreffingever. Haven't tried in recovery yet but I know not to believe the progress bar.
EDIT: In terminal it took 8min 24secs.
Click to expand...
Click to collapse
Not doubting you! But with CWM it took barely a minute.
Teleported from my Shifty Speedy using Tapatalk
jesusice said:
Are you sure you just didn't give it enough time? I've noticed that the progress bars actually bear no relation to the actual progress. I'm fixing permission in terminal now and I can tell you, it takes foreffingever. Haven't tried in recovery yet but I know not to believe the progress bar.
EDIT: In terminal it took 8min 24secs.
Click to expand...
Click to collapse
I waited a good 5 minutes after the "end" of the progress bar and finally did a battery pull. I was able to fix permissions through terminal, just didn't work through recovery.
Sent from my PG06100 using Tapatalk
noob question but will this also restore backups made from cwm?
hoesnaps said:
noob question but will this also restore backups made from cwm?
Click to expand...
Click to collapse
No. You'll need to make fresh backups
Sent from my PG06100 using Tapatalk
Sweet new recovery. Does it support partitioning of sdcard yet? I think I'll wait for TWRP 2.x
Sent from my PG06100 using xda premium
sparksco said:
Sweet new recovery. Does it support partitioning of sdcard yet? I think I'll wait for TWRP 2.x
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
It has the option to partition but I haven't tried it yet... anyone?
Sent from my PG06100 using Tapatalk
Because of the way the recovery is packed into boot, this will not work with all kernels / ROMs. It is known to work with CM7.2 and CM9.1.0. It will probably work with most other MTD-based ROMs and kernels but will not work with any BML ROM or kernel. Use at your own risk! Installing a new ROM or kernel may end up replacing your install of TWRP. Also note that TWRP is *not* compatible with CWM backups. We are not based on CWM, we wrote our own recovery based on AOSP. With that said, I hope that you will get a chance to at least see how fast and easy-to-use TWRP is.
In addition to the on-screen keyboard, TWRP now supports using the hardware keyboard on the Epic 4G. Unfortunately the screen doesn't rotate, but hey, the hardware keyboard does work.
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:
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.
First. Thanks.
×Marcusant
Sick!!!"
Sent from my SPH-D700 using xda premium
Wow, this looks great, can't wait to try it out. Thanks TeamWin
Sent from my SPH-D700 using XDA
This will probably work on all mtd roms afaik.
×Marcusant
Niiiice
Part of the trick with this build of TWRP is the inclusion of a new utility that I've started working on called injecttwrp. It's a work in progress. I'll be building upon this to inject our recovery ramdisk into existing Samsung boot images so that you can choose to keep TWRP installed as you install new ROMs or kernels regardless of what recovery is included with the kernel or ROM that you are installing.
https://github.com/TeamWin/Team-Win-Recovery-Project/blob/master/injecttwrp/injecttwrp.c
Note that this utility is not restricted to just working with TWRP. It could be used to inject any recovery that you wanted.
Awesome, I use this for my Kindle Fire and love it. It also is the only current recovery that works with the new 3.0 kernel, but I think that is mainly a fire issue. I will try it when I get some time!
anyone confirm it works on ics (aokp particularly)?
This looks awesome
Just a thought.. marcusant.. could you build this recovery into nyan for sayyy cm7?
Sent from my SPH-D700 using XDA
Found the install for epicmtd... and as soon as it finished it booted me into recovery and attempted to flash and gave me a status 7... which is usually a signing failure.
Sent from my SPH-D700 using xda premium
Of course on the day I'm busiest is when this is released lmao. Thanks for the hard work guys, I'll be playing with this tomorrow for sure!
Sent from my SPH-D700 using xda premium
ÜBER™ said:
Found the install for epicmtd... and as soon as it finished it booted me into recovery and attempted to flash and gave me a status 7... which is usually a signing failure.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
The failure was an oddity with the formatting of our flash_image on ics as far as I can tell
×Marcusant
I might just have to yank the zip until I can figure it out, the manual install should work and I have it working in CM9 too.
Dees_Troy said:
I might just have to yank the zip until I can figure it out, the manual install should work and I have it working in CM9 too.
Click to expand...
Click to collapse
I mean it goes through everything but then stops towards the end... write_flash_image has an error and it shows E: /sdcard/goomanager/twrp.zip ... and aborts.. so what marcus said about the flash image.
Sent from my SPH-D700 using xda premium
hmm.. a nice shiny new touch recovery to play with (since we heard rumors about CWM Touch for the Epic but it never materialized.)
Might have to give this a shot.
Thanks!
pvtjoker42 said:
hmm.. a nice shiny new touch recovery to play with (since we heard rumors about CWM Touch for the Epic but it never materialized.)
Might have to give this a shot.
Thanks!
Click to expand...
Click to collapse
........interface similar to Epic CM Team's test touch recovery; will await sign from Dees_Troy + flash again.
.........sent from today's android = 4.0.4
I believe that the zip install should now be working!
Can't get it to download... won't show in my goomanager folder I made the mistake of enabling check signiture toggle and now it won't disable it when it tries to install it fails... and is not in the folder so I can toggle the sig verification and reflash via cwm....
Then I tried to share the link, copy it and then download via the browser its in the download folder now... I tried to flash that it says installation aborted (bad). Wtf?
Sent from my SPH-D700 using xda premium
ÜBER™ said:
Can't get it to download... won't show in my goomanager folder I made the mistake of enabling check signiture toggle and now it won't disable it when it tries to install it fails... and is not in the folder so I can toggle the sig verification and reflash via cwm....
Then I tried to share the link, copy it and then download via the browser its in the download folder now... I tried to flash that it says installation aborted (bad). Wtf?
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
I couldn't get it to install on cm7 says error installing blah blah (bad).. tried to download it twice.. both times errors
Sent from my SPH-D700 using XDA
Team Win Recovery Project 2.3, 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.3.2.3:
-Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)
-Fixed a bug with deleting a backup with a space in the name
-Added highlights on keyboard key presses
-TF101: Ignore blkid when mounting /data
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
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!
NOTE: If you're coming from another build of TWRP, you may need to go into settings and tap reset defaults to reset the storage paths so that you can see your zip files.
BUGS:
If you have found a bug, please acquire a recovery.log - you can do this in two ways - the fastest is "adb pull /tmp/recovery.log" right after you have the issue. Alternatively in the advanced menu there's an option to copy the log to the sdcard. Also consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 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 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.
We also now back up and restore boot! Yay!
Want to compile yourself?
I'm using this config: https://github.com/ViViDboarder/android_device_asus_tf101
And this kernel: https://github.com/ViViDboarder/android_kernel_TF101
And compiling against CM9 source tree
Further device specific announcements will go here
A few thanks for this specific build:
Roach2010 for helping be me test and find the mystery kernel
RaymanFX for finding a config that worked. Still not sure where he found it yet exactly
And... Dees_Troy and eyeballer for their relentless nagging
first ...
well second lol
So, third ......thanks guys, that's awesome !
thanks, been waiting for this.
great work, i've been waiting forever and finally have this on all my devices and those that I support.
I've been using the other one RaymanFX had built and both are awesome. Only 1 change other than the known issues, would be remove the "Bootloader" button under restart. But just my opinion. Thanks Again.
gdeeble said:
I've been using the other one RaymanFX had built and both are awesome. Only 1 change other than the known issues, would be remove the "Bootloader" button under restart. But just my opinion. Thanks Again.
Click to expand...
Click to collapse
Good note. That's a theme issue then. I can build a new theme zip or something later. Working on releasing the much delayed Nexus One build.
EDIT: I've been informed by Dees_Troy that we have build flags to do just this. So I'm adding them to my configs so the next build should have them removified.
It's worth pointing out that this build of TWRP has a recompiled kernel with boot and recovery exposed. You can finally back up boot and restore it.
GooManager keeps hanging at Looking for recoveries after trying to install OpenRecoveryScript. Unable to retrieve files...
Finally recovery on a touch screen device the way it should be! Thanks guys!
Sent from my SGH-I747 using Tapatalk 2
I thought I would give this a try and went to the TWRP page link as instructed. Followed the instructions to download the open recovery through goo manager, which it did and it rebooted my tablet and all looked good. I then tried to reboot to recovery from Team EOS3 Power menu. The usual TWRP blue curtain was there and when it raised, I saw the text at the bottom that my /data partition was being formatted without formatting /data/media and the tablet rebooted, without ever getting to the TWRP recovery menu and I'm now back at the initial Google setup screen. Guess I should have made a fresh Titanium backup first. A warning would have been nice, or is this a bug?
Strange. But I copped the blob from twrp site as "not recommended" suposedly. Ran the command in terminal cuz I don't Fux with goo manager... Everything worked fine. No issues
~Poisoned Viper4g LTEvOne by TeamVenom, Lionheart Cranked to 1.72Jigawats Deadline: Ca1ned.
MassStash said:
Strange. But I copped the blob from twrp site as "not recommended" suposedly. Ran the command in terminal cuz I don't Fux with goo manager... Everything worked fine. No issues
~Poisoned Viper4g LTEvOne by TeamVenom, Lionheart Cranked to 1.72Jigawats Deadline: Ca1ned.
Click to expand...
Click to collapse
Since it's installed now and it wiped my data without asking, I'm going to clear things out and reflash everything. I will test if it tries to wipe my data again after I reinstall a few apps.
sidneyk said:
Since it's installed now and it wiped my data without asking, I'm going to clear things out and reflash everything. I will test if it tries to wipe my data again after I reinstall a few apps.
Click to expand...
Click to collapse
Weird. It didn't wipe my data. Just installed nicely as per instructions.
running great with no issues I used goo manager app but i flashed it through the flash roms selection on the main menu not the 3-dot menu install open recovery script selection.
sidneyk said:
I thought I would give this a try and went to the TWRP page link as instructed. Followed the instructions to download the open recovery through goo manager, which it did and it rebooted my tablet and all looked good. I then tried to reboot to recovery from Team EOS3 Power menu. The usual TWRP blue curtain was there and when it raised, I saw the text at the bottom that my /data partition was being formatted without formatting /data/media and the tablet rebooted, without ever getting to the TWRP recovery menu and I'm now back at the initial Google setup screen. Guess I should have made a fresh Titanium backup first. A warning would have been nice, or is this a bug?
Click to expand...
Click to collapse
Did you ever try to use goo manager with the old unofficial version?
Sent from my HTC One S using xda premium
ViViDboarder said:
Did you ever try to use goo manager with the old unofficial version?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
No, I was using RaymanFX's TWRP build prior to this and before that Team Rogue Touch and before that Roach's CWM build, all flashed from within recovery. I only did the GooManager thing because that was the recommended method. Subsequent boots to recovery did not reproduce the data wipe and after reflashing my ROM and restoring my apps, I went into recovery without a hitch. It was only after installing this one through GooManager per the instructions. It downloaded, rebooted and flashed and rebooted back to Android (Team EOS3 JB #57). After a few minutes I rebooted to recovery from the Power menu in EOS3 and as soon as the blue curtain raised it was wiping my data partition - /data/media. Of course, I didn't expect that and didn't get any chance to stop it. I know I read somewhere before that open recovery wasn't working on the TF101, but since this was new and it was recommended to use open recovery, I just assumed that meant it was now working. Oh well, all is well now.
never mind i figured it out, open recovery only works with internal for now.(it may be because TWRP-2.2.1.4 is mounting the micro SD as /sdc instead of /storage/sdcard0) I moved the goomanager folder to /data/media updated the download folder location in the goomanager app settings to /data/media/goomanager re-ran flash roms from the goomanager apps made my selections and order to flash and selected wipe Cache and Dalvik and it ran just fine, it rebooted to recovery, flashed all the zips(including my mods) in the proper order and booted back up with no issues.
Running EOS3-N58 at this time.
Dam sweet once i figured it out!
Great job!
Thanks
cbrox said:
never mind i figured it out, open recovery only works with internal for now.(it may be because TWRP-2.2.1.4 is mounting the micro SD as /sdc instead of /storage/sdcard0) I moved the goomanager folder to /data/media updated the download folder location in the goomanager app settings to /data/media/goomanager re-ran flash roms from the goomanager apps made my selections and order to flash and selected wipe Cache and Dalvik and it ran just fine, it rebooted to recovery, flashed all the zips(including my mods) in the proper order and booted back up with no issues.
Running EOS3-N58 at this time.
Dam sweet once i figured it out!
Great job!
Thanks
Click to expand...
Click to collapse
I had already flashed EOS3-N58, but had changed some files experimenting with getting Polaris Office to work and gave up. So, I followed your suggestion and moved a few other files that I normally flash along with the ROM and it worked like a charm. Pretty nifty. I setup the order to flash for EOS3-N58, gapps, Guevor kernel, nVidia codecs, iobusy, and DSP Manager along with the preliminary cache and Dalvik cache wipes and it just worked like you say. Thanks. I hadn't tried that feature yet, mostly because until now I thought it might break something since I had read that open scripting wasn't working yet for TF101 somewhere. I can say now, with this recovery and your change to the download folder, that it is working and working well. You just have to have whatever files you want to flash in that folder (or maybe just somewhere in /data/media) and you're good to go.
Team Win Recovery Project 2.2, 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.2.2.0 compared to 2.2.0.0):
Mostly bugfixes:
Significantly improved sd-ext handling (ext partitions on sdcards)
Changes to kinetic scrolling in file selectors
Fixed a problem with using periods in backup names
Fixed problems in XML layouts with mounting system and USB storage
Fixed a problem with unmounting a partition before formatting during restore
Add Jelly Bean decrypt support
Updated 320x480 theme to match others (thanks to Llewelyn)
Improve "symlinking" of /data/media to either /sdcard or /emmc
Added sanitizing of device IDs for invalid characters (thanks to bigbiff)
Fixed free space calculation when switching backup devices on /data/media devices
Fixed a problem with using OpenRecoveryScript to create a backup without providing a backup name
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!
NOTE: If you're coming from another build of TWRP, you may need to go into settings and tap reset defaults to reset the storage paths so that you can see your zip files.
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 30 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.
thank you for this, ill test asap
if anyone wants a flashable zip, lemme know. i already have it done
edit: works good. only thing is i was flashing a rom (attempting to anyway) and somehow my zip got corrupted and unreadable. never had that happen before. any thoughts? (it was fine when i put it on my sd card, was flashing a 2nd time, so zip had worked previously and all other files on my sd are fine)
Going to flash this now and give it a try. Hopefully it works out good.
whoshotjr2006 said:
if anyone wants a flashable zip, lemme know. i already have it done
Click to expand...
Click to collapse
Throw it up brother!
thanks, always wanted a touch recovery and this one is great, if i could make a recovery touch it would be like this one again thanks
I flashed this a week or two ago and been working awesome! I love it.
i have been using cw recovery all time and always wanted to have a touch screen recovery and this one is sick, my only thing i have found is when i go to restore a backup it cannot find it,(one from cwm recovert). is it that it just cant restore those or did i miss something? no big deal to me ,just wanted to put it out there.
again thanks for this
they are in different folders on the SDCARD, im not even sure they are compatible.
ok cool im trying to do differant things and ill update you either way
would you know off hand where twrp folder would be? im looking if i get it before a reply ill post it
i got it twrp folder
alsp cani get the twrp 2220 in a zip format?
will this recovery work with firerats? on heroc?
dankdank11 said:
will this recovery work with firerats? on heroc?
Click to expand...
Click to collapse
Yes, Firerats has nothing to do with the recovery. Firerats just resizes your data/system/cache portion of the system really so you can install more apps.
I am using it and love it and works awesome on my Hero. :good:
thanks im trying it now, love the use of touch
I am going to leave the automated GooManager install for the Hero on version 2.2.2.0 due to the age of the device and the problems with recovery API 3 and older zips. TWRP 2.3.0.0 does work fine on the HeroC but I'm willing to bet that most zips are using old update binaries that will not install on the new version. If anyone wants to try, you're welcome to download and flash the newer versions manually:
http://techerrata.com/browse/twrp2/heroc
I was going to give 2.3.0.0 a try but like you stated, and someone in IRC said, that most of the zips online for the old Hero are prob all older so going to stick with 2.2.0.0 I think. Thanks for the update though.
Does TWRP require any particular hboot version, or will it function with any of them? I know you need to be on Android 2.3 in order to install TWRP, but I'm wondering... does it also mean that if you flash back to a stock ROM that TWRP won't work properly?
EDIT: My question was obviously stated with some knowledge missing. Recovery is obviously not dependent upon the ROM, as the ROM is loaded after the recovery program is done! But... I'm curious to know, if I made a nandroid backup with TWRP 2.2.2.0, will TWRP2 be able to restore it?
* DELETE *
There has been a small oversight with the GooManager route of distribution and the original post for this particular phone. You must have a PC or have a phone that can flash .zips or has a 2.3 or up ROM installed so it can run GooManager, even though this phones last OTA was Android 2.1, so it probably should have a .zip posted instead.
For example, I have a stock but rooted HTC Hero from Sprint as my backup with the latest OTA. So I can't use this method of install for this recovery without flashing a different recovery first, and then either flashing it as a .zip or upgrading my ROM to a 2.2 or 2.3 based ROM. In reality, I think most will just stick with whatever recovery must be flashed first in this situation as I will, even though I wanted TWRP. That said I think most of the users that use this will just want a .zip.
But there is no .zip posted for the guys that can flash it. This also makes it an overly cumbersome option if the handset is in stock state. As I said, I probably won't bother re-flashing, I kind of like sticking to one recovery on a phone and prefer to do minimal NAND writes.
DizturbedOne said:
There has been a small oversight with the GooManager route of distribution and the original post for this particular phone. You must have a PC or have a phone that can flash .zips or has a 2.3 or up ROM installed so it can run GooManager, even though this phones last OTA was Android 2.1, so it probably should have a .zip posted instead.
That said I think most of the users that use this will just want a .zip.
But there is no .zip posted for the guys that can flash it. This also makes it an overly cumbersome option if the handset is in stock state. As I said, I probably won't bother re-flashing, I kind of like sticking to one recovery on a phone and prefer to do minimal NAND writes.
Click to expand...
Click to collapse
As stated a couple of posts before you:
Dees_Troy said:
I am going to leave the automated GooManager install for the Hero on version 2.2.2.0 due to the age of the device and the problems with recovery API 3 and older zips. TWRP 2.3.0.0 does work fine on the HeroC but I'm willing to bet that most zips are using old update binaries that will not install on the new version. If anyone wants to try, you're welcome to download and flash the newer versions manually:
http://techerrata.com/browse/twrp2/heroc
Click to expand...
Click to collapse
Sent from my SCH-I535 using xda app-developers app
Hippie459MN said:
Yes, Firerats has nothing to do with the recovery. Firerats just resizes your data/system/cache portion of the system really so you can install more apps.
I am using it and love it and works awesome on my Hero. :good:
Click to expand...
Click to collapse
That's good to know. I think I'll give it a shot.