Key Features:
Ability to save custom recovery settings
Default partitions to back up
Default zip folder location
Default color theme (lots to choose from) (Thanks to ffolkes!)
Default Time Zone (for more accurate time stamps)
Zip Signature Verification
Zip md5 Verification (looks for file with zipname.zip.md5)
Ability to flash multiple zips in one go
Ability to select which individual partitions to backup, and restore.
Ability to choose compression or no compression backups.
Compression takes longer of course, but you save roughly half the space. EVO3D's stock system uncompressed is ~800mb, 380mb compressed. You choose.
Ability to auto restore GAPPS on zip flash (for CM based ROMS)
Ability to auto reboot after successful flashes (for the lazy)
Some devices utilize their capacitive buttons in recovery.
Home - Main Menu
Menu - Advanced Menu
Back - Up a Menu Level
Search - Select Current Selection
Battery Level and Timestamp (Better safe than sorry)
What's new in 2.6.0.0:
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
Special Note: If you are running a custom theme, some of the changes in 2.6.0.0 will likely not be visible with your custom theme.
What's new in 2.5.0.0:
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 DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
Fixed a problem with directory permissions on split archive backups
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
Special Note: If you are running a custom theme, the changes in 2.5.0.0 will likely not be compatible with your theme.
What's new in 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
HTC Dumlock Instructions:
Install the build of TWRP using your method of choice, but you must actually flash TWRP to recovery. No fastboot booting it. We need it in recovery so that this build of TWRP will be flashed to your boot. This new build of TWRP has features in it to easily restore your original boot.
Reboot into recovery.
Make a backup of your phone.
Tap Advanced.
Tap HTC Dumlock. (If you don't see HTC Dumlock then you need to remove any custom TWRP theme that you might be using.)
Tap Install HTC Dumlock. This will install the app and binaries needed to make everything work nicely.
Reboot your device.
Find and open the HTC Dumlock app.
If/when prompted, give the app root (SuperUser) permissions.
Tap the Execute HTC Dumlock button.
Wait patiently for a couple of minutes. It takes a little while.
If your device doesn't reboot automatically, reboot it manually. Reboot it normally. DO NOT reboot it to recovery.
You should now be in your recovery, but your recovery is flashed into boot.
Tap Advanced.
Tap HTC Dumlock.
Tap Restore Original Boot.
Use your recovery like normal. Flash a new kernel. Restore a backup with a different kernel. Do whatever you please!
Consider donating!
Note, you must repeat steps 8 through 17 EVERY TIME you need to flash boot.
Installation:
Unlock bootloader at http://www.htcdev.com/bootloader/
Turn phone completely off.
Boot into HBOOT then Fastboot
Erase cache from fastboot before flashing recovery. Use command "fastboot erase cache"
From fastboot. Use command "fastboot flash recovery recovery.img"
Downloads:
http://goo.im/devs/Flyhalf205/MYSTUL/Recovery//openrecovery-twrp-2.6.0.0-mystul.img
Root:
To gain root on stock rom. Flash recovery in fastboot then flash this inside of recovery. There are two root programs. Superuser and SuperSU. Both are listed.
Superuser - http://download.clockworkmod.com/superuser/superuser.zip
OR
SuperSU - download.chainfire.eu/supersu
PC USB Mass Storage:
You can't! http://teamw.in/DataMedia
This version of TWRP has OTG-USB support also. Enjoy
The download link is missing the .img extension. Also, once I flashed the recovery and booted into it, the screen started looking crazy, like the recovery was trying to output the wrong resolution or sync rates. Looked crazy: http://db.tt/RIaIsti9
nuclear_eclipse said:
The download link is missing the .img extension. Also, once I flashed the recovery and booted into it, the screen started looking crazy, like the recovery was trying to output the wrong resolution or sync rates. Looked crazy: http://db.tt/RIaIsti9
Click to expand...
Click to collapse
Easy fix. I'll put a new build out later.
New build is up if anyone can test and make sure graphic works?
Flyhalf205 said:
New build is up if anyone can test and make sure graphic works?
Click to expand...
Click to collapse
It's looking better, but the colors are off, and it's duplicated along the X axis. However, if I let the recovery sit long enough to turn off the screen, when it turns back on, it then looks correct (blue and not duplicated).
https://dl.dropboxusercontent.com/u/7859496/Android/2013-04-19 14.52.22.jpg
https://dl.dropboxusercontent.com/u/7859496/Android/2013-04-19 14.52.25.jpg
---------- Post added at 03:11 PM ---------- Previous post was at 03:08 PM ----------
Forgot to mention that this recovery is able to mount /sdcard and see the contents of it, so hopefully that helps you to improve the clockwork recovery to match.
nuclear_eclipse said:
It's looking better, but the colors are off, and it's duplicated along the X axis. However, if I let the recovery sit long enough to turn off the screen, when it turns back on, it then looks correct (blue and not duplicated).
https://dl.dropboxusercontent.com/u/7859496/Android/2013-04-19 14.52.22.jpg
https://dl.dropboxusercontent.com/u/7859496/Android/2013-04-19 14.52.25.jpg
---------- Post added at 03:11 PM ---------- Previous post was at 03:08 PM ----------
Forgot to mention that this recovery is able to mount /sdcard and see the contents of it, so hopefully that helps you to improve the clockwork recovery to match.
Click to expand...
Click to collapse
So this could flash zips without adb?
Sent from my HTC first
phositadc said:
So this could flash zips without adb?
Sent from my HTC first
Click to expand...
Click to collapse
It appears that way, though I have not tested that.
nuclear_eclipse said:
It's looking better, but the colors are off, and it's duplicated along the X axis. However, if I let the recovery sit long enough to turn off the screen, when it turns back on, it then looks correct (blue and not duplicated).
https://dl.dropboxusercontent.com/u/7859496/Android/2013-04-19 14.52.22.jpg
https://dl.dropboxusercontent.com/u/7859496/Android/2013-04-19 14.52.25.jpg
---------- Post added at 03:11 PM ---------- Previous post was at 03:08 PM ----------
Forgot to mention that this recovery is able to mount /sdcard and see the contents of it, so hopefully that helps you to improve the clockwork recovery to match.
Click to expand...
Click to collapse
Another easy fix It's building CWM right now with the fixed internal sdcard fix then I'll build the fixed TWRP.
New build of TWRP is up. Should be completely 100% to go now...
Man, I swear I love you lol. I was just checking the First/AT&T One section and bam. You pop up with the recoveries! My toolkits will be going this way, thanks to you!
hasoon2000 said:
Man, I swear I love you lol. I was just checking the First/AT&T One section and bam. You pop up with the recoveries! My toolkits will be going this way, thanks to you!
Click to expand...
Click to collapse
I try man. lol. Btw The ATT One works with the just the HTC One toolkit so you could just mirror post.
Sent from my ADR6425LVW using Tapatalk 2
Everything looks correct now.
Sent from my HTC first using xda premium
Hey man. Adb is broken on twrp and I assume cwm too. I'm going to send you a pull request with the fix
Sent from my M7 using xda premium
Pull request sent
Sent from my M7 using xda premium
jmztaylor said:
Pull request sent
Sent from my M7 using xda premium
Click to expand...
Click to collapse
Merged. I'll build them shortly. :good:
Flyhalf205 said:
Merged. I'll build them shortly. :good:
Click to expand...
Click to collapse
I only sent pull request for twrp. I don't use CWM so Im not completely sure that fix will work on CWM or not.
jmztaylor said:
I only sent pull request for twrp. I don't use CWM so Im not completely sure that fix will work on CWM or not.
Click to expand...
Click to collapse
Willing to test it? https://www.dropbox.com/s/nnmfxafdp756ptv/openrecovery-twrp-2.5.0.0-mystul.img
Flyhalf205 said:
Willing to test it? https://www.dropbox.com/s/nnmfxafdp756ptv/openrecovery-twrp-2.5.0.0-mystul.img
Click to expand...
Click to collapse
I'm already in bed. I will check it out tomorrow
Sent from my M7 using xda premium
Works good. I had a bunch of issues trying to boot any recovery earlier. But fastboot erase cache made it work. So its similar to the HTC One. Maybe put that in OP so you can avoid the questions.
Related
First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the HTC Wildfire. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for the modifications. Can be installed with unrEVOked. Installs and works well according to users in this thread. Off-mode charging works according to t0mas_.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-buzz.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-buzz.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Removed NULL ext3 in recovery.fstab to hopefully get ext4 working properly.
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.
Flash like a normal ROM ?
Use it with unrevoked then custom recovery in the menu and use the image file in the zip
If you're testing it, let me know if it works.
Sent from my Nexus S using Tapatalk
does this include off mode charging fix?
http://forum.xda-developers.com/showthread.php?t=1014498
Well my phone was installed and works well ...
t0mas_ said:
does this include off mode charging fix?
http://forum.xda-developers.com/showthread.php?t=1014498
Click to expand...
Click to collapse
No idea. It depends on the CM7 3.2.0.0 recovery source code. I didn't change anything, and I'm quite sure j_r0dd didn't touch this.
cse.10100 said:
Well my phone was installed and works well ...
Click to expand...
Click to collapse
Great! Updating the OP.
thanks, i'll try this out when i find time
one silly question. I use as recovery clockwork 2.xxxx version for a long time now since I first rooted my device with Unrevoked tool. If I flash this new recovery or any other recovery with unrevoked will it create another superuser option that will conflict with the one that was created from the first root?
aggourodolmas said:
one silly question. I use as recovery clockwork 2.xxxx version for a long time now since I first rooted my device with Unrevoked tool. If I flash this new recovery or any other recovery with unrevoked will it create another superuser option that will conflict with the one that was created from the first root?
Click to expand...
Click to collapse
Well, the recovery image itself doesn't touch superuser, but unrevoked will. I belive that you might be downgrading the superuser binary, but (at least for CM7) a reflash with the same zip without wiping anything should restore the superuser binary that was included in your ROM. It should work on other ROMs as well, as long as they're not wiping /data or /sd-ext while flashing for some reason. Make a nandroid backup before you consider flashing this recovery, that's my advice.
Can anyone confirm if this supports off mode charging?
s0ulbl5d3 said:
Can anyone confirm if this supports off mode charging?
Click to expand...
Click to collapse
Not sure where to look, but maybe one can search for this in some type of changelog for the official cwm repository.
s0ulbl5d3 said:
Can anyone confirm if this supports off mode charging?
Click to expand...
Click to collapse
works for me
How can i update this clockwork image,i cant see the image in clockworkmod,i just can see zip files.
rseke said:
How can i update this clockwork image,i cant see the image in clockworkmod,i just can see zip files.
Click to expand...
Click to collapse
You need to use unrevoked to flash the .img file.
ok but how,what i must to do ?
i cant find step by step manual fot clockworkmod update from img file.
rseke said:
ok but how,what i must to do ?
i cant find step by step manual fot clockworkmod update from img file.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=12548919&postcount=26
Unrevoked 3.14 can be found in the same thread on the first page.
Thanx for fast reply and for help.
I have one problem now,mu super user app not working how can i fix that,i cant enter to superuser app to update su binary,force close.
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.
Wow, works great! Thanks for this. I saw the Inc 2 users were getting something like this, made me jealous
It doesn't look to be working. HBOOT isn't finding the image, it seems like its failing to load it. However it did say No image or wrong image when loading PB31IMG.zip
---------- Post added at 12:31 PM ---------- Previous post was at 12:29 PM ----------
kschwarz88 said:
Wow, works great! Thanks for this. I saw the Inc 2 users were getting something like this, made me jealous
Click to expand...
Click to collapse
How did you get it to work?
Check to make sure your microSD is formatted FAT32, not FAT.
Download "PB31IMG-twrp-inc-2.0.0RC0.zip" and rename it to PB31IMG.zip. Put it in the root of the card.
Do backups from CWM work in this recovery?
Does multi touch for more than two fingers work with this recovery and incredikernel or one of lou's?
Flashed the image and it got stuck at the teamwin splash screen.
Can't wait to load this up later. I saw this released the other day and couldn't wait for Incredible support.
Sent from my ADR6300 using XDA App
I was just thinking about asking for this! Now we have it!
-My life is a shooting range, people never change-
I have been watching development on this since agrabren talked about it. I'm glad they gave the inc some love. Works great.
Sent from my HTC Droid Incredible using Tapatalk
curious if i was to move my cwm backups over to /twrp/backups will it change the MD5 and be unable to restore or should i be fine doing that?
i love the look and feel and battery/time in this defiantly my new recovery thank you so much TeamWin for this awesome work
Thank you for bringing this recovery to us. It us absolutely great.
Amazing! Works great so far!
Sent from my ADR6300 using xda premium
Thank you for support on the Incredible! This recovery is awesome!!!!!!!!!!
Does anyone know if cwm back ups will restore correctly with this?
Would it just abort if I tried to restore a backup from cmw?
Sent from my ADR6300 using xda premium
tribbey said:
Would it just abort if I tried to restore a backup from cmw?
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
I think you're going to have to try it yourself, as me and no one else is willing enough.
I'm trying this and it seems pretty cool so far. I haven't really messed with it much, but I like the change from the standard clockworkmod recovery
of course this comes the day before I get my nexus.
Sent from my ADR6300 using Tapatalk
Stay away from this recovery
If you love your Droid Incredible, please stay away from this recovery. Stick with the recovery you have already and which is proven to work under all circumstances. I installed this recovery this morning and sure enough I was impressed with UI, no more optical joystick or using volume buttons. I was happy, but my sorrows were yet to come. I made a backup of the ROM I was running (Stock GB), then flashed a downloaded ICS Alpha which was on my SD card. The ICS Alpha got stuck during boot and never made it to the home screen. I went back into this recovery and did a restore of my backup (Stock GB). My woes started. It finished restoring, rebooted, then on the home screen I saw a message about System UID not being the same and that I should try to wipe data. I did this and still the same message. I went back into the recovery, wiped data, cache,and did another restore... still the same error message. Worst of all is that nothing works now. Everything throws an fc. I am now downloading CWM 5.0.2.0 to try and reflash CWM then try to restore a previous backup I did with CWM before flashing this recovery. If you care to go through all these woes I mentioned here, stick with this recovery. If not, stay away from it. It is just eye candy at best.
I'm gonna play with it a little bit
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.
sweet i might have to try this out on one of mine
Works great
can you post instructions on how to get the recovery cuz i downloaded the app and i went to recovery and flashed the zip but nothing happened.
Does the battery indicator is still a issue?
Marshmellow92 said:
can you post instructions on how to get the recovery cuz i downloaded the app and i went to recovery and flashed the zip but nothing happened.
Click to expand...
Click to collapse
You have to flash the recovery .img as well. I used the GUI app renamed the. .img to recovery.img and flashed it. Then reflashed the zip for extra measure.
contactwajeeh said:
Does the battery indicator is still a issue?
Click to expand...
Click to collapse
Yes it is, but charging while powered off works now.
Very nice! Many thanks to the devs.
I cant access my external sd card from any of the directorys, emmc, internal sd, etc.. They all point to internal.
lmftmf said:
I cant access my external sd card from any of the directorys, emmc, internal sd, etc.. They all point to internal.
Click to expand...
Click to collapse
The bug has been confirmed and a fix is on the way.
Can I use this recovery when upgrading to ics using the new ics ruu? Right now on cwm, stock sense gb, rooted.
Sent from my HTC PH39100
cannothas said:
Can I use this recovery when upgrading to ics using the new ics ruu? Right now on cwm, stock sense gb, rooted.
Sent from my HTC PH39100
Click to expand...
Click to collapse
Yes you could, but here download this:
http://www.mediafire.com/?dzt7c3xz7ti73ic
The above recovery image has fix for external SD
The recovery that is installed by the app has the sdcard fix now too. The app build was updated by midnight last night eastern time.
Humm
Dees_Troy said:
The recovery that is installed by the app has the sdcard fix now too. The app build was updated by midnight last night eastern time.
Click to expand...
Click to collapse
Can you post a zip file I could Fastboot flash>? my phone wont boot because it wont charge when its off but I can still flash a recovery !
jul644 said:
Can you post a zip file I could Fastboot flash>? my phone wont boot because it wont charge when its off but I can still flash a recovery !
Click to expand...
Click to collapse
You can find that here:
http://www.teamw.in/project/twrp2/76
cruzin_cruzing said:
You can find that here:
http://www.teamw.in/project/twrp2/76
Click to expand...
Click to collapse
Does that link have the sdcard fix yet? Version 2.1.0?
htcvividnoob said:
Does that link have the sdcard fix yet? Version 2.1.0?
Click to expand...
Click to collapse
I don't know for sure, but I know this one does:
http://www.mediafire.com/?dzt7c3xz7ti73ic
cruzin_cruzing said:
I don't know for sure, but I know this one does:
http://www.mediafire.com/?dzt7c3xz7ti73ic
Click to expand...
Click to collapse
I downloaded this but its a .txt file
Sent from my HTC Raider X710e using xda premium
thuglifesk said:
I downloaded this but its a .txt file
Sent from my HTC Raider X710e using xda premium
Click to expand...
Click to collapse
Just rename it to an .img file and flash. This happens alot on mediafire with img files.
battery to dead
Thank you but unfourtunetly it didnt work
TWRP Recovery
For Galaxy Mini
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
BUGS:
If you have found a bug, please consider posting it here.
LIVE SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link
SPECIAL NOTE:
This is the first build of TWRP and may have some unknown bugs. I take no responsibility of your devices. This is "testing" phase (for some days only). Help in testing if you wish to otherwise stay away until a final release. Don't post back here that: "You destroyed my phone", "You are cheating", "You are playing with my device".
One more thing, we are using androidarmv6 sources and if you are asking for help on IRC channel mentioned above then please mention there that: "we are not using CM or OMNI sources, we are using androidarmv6 sources".
CREDITS:
TeamWin: For this awesome open-source recovery.
androidarmv6 team: To make all these possible.
chraso: For his precious help.
Me: For compiling it for Galaxy Mini.
CHANGELOG for 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 thanks to Samer Diab
-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.
DOWNLOAD:
http://www.upload.ee/files/3992673/recovery.img.html
INSTALLATION / UPDATING:
-From the above download link, you'll get a 'recovery.img' file.
-Put that file at the root of sdcard (means, not in any folder)
-Now, open Terminal Emulator and give this command:
Code:
su
You'll be asked to grant superuser permissions, grant them.
-Now, give this command:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!
What to test in latest build?:
-NOTHING. IT IS STABLE NOW.
Reserved
Will test it the moment I get home. Which is about 4 hours from now...
Tapatalk-kal küldve az én GT-S5570-el
doesnt boots.hangs on teamwin boot screen. luckily i had pc.currently flashing recovery by odin
+1
arpitkh96 said:
doesnt boots.hangs on teamwin boot screen. luckily i had pc.currently flashing recovery by odin
Click to expand...
Click to collapse
Thanks for feedback.
Now, can you help me find the problem?
How?
-Install recovery.
-Though it's stuck at Teamwin's screen, use adb in pc and give the following command:
Code:
adb pull /tmp/recovery.log
-Now, you will have a recovery.log file at the location where your adb files are there.
Attach that file in your post or use pastebin.com.
AND
Can you try that (terminal emulator) method once?
If you don't know what I'm talking about, see PhilZ recovery FAQs > Alternative way to flash this recovery.
Bhargav97 said:
Thanks for feedback.
Now, can you help me find the problem?
How?
-Install recovery.
-Though it's stuck at Teamwin's screen, use adb in pc and give the following command:
Code:
adb pull /tmp/recovery.log
-Now, you will have a recovery.log file at the location where your adb files are there.
Attach that file in your post or use pastebin.com.
AND
Can you try that (terminal emulator) method once?
If you don't know what I'm talking about, see PhilZ recovery FAQs > Alternative way to flash this recovery.
Click to expand...
Click to collapse
terminal method doesnt works either.here is the log
arpitkh96 said:
terminal method doesnt works either.here is the log
Click to expand...
Click to collapse
Thanks for logs. They helped me.
I forgot to add some things in recovery.
I didn't recompile but repacked with those things added.
If you get a black screen, don't give me logs. (It maybe a repack problem)
But, if you get teamwin logo, I need logs again.
New recovery.img for test:
http://www15.zippyshare.com/v/37395986/file.html
Use terminal emulator method.
Bhargav97 said:
Thanks for logs. They helped me.
I forgot to add some things in recovery.
I didn't recompile but repacked with those things added.
If you get a black screen, don't give me logs. (It maybe a repack problem)
But, if you get teamwin logo, I need logs again.
New recovery.img for test:
http://www15.zippyshare.com/v/37395986/file.html
Use terminal emulator method.
Click to expand...
Click to collapse
loops between black screen and Samsung logo. Cant give log ,adB doesnt recognises
Sent from my GT-S5570 using XDA Premium 4 mobile app
arpitkh96 said:
loops between black screen and Samsung logo. Cant give log ,adB doesnt recognises
Sent from my GT-S5570 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Will be back after a re-compile.(15-20 min)
Sorry to be late.
Here's new test:
http://www.upload.ee/files/3989901/recovery.img.html
Bhargav97 said:
Sorry to be late.
Here's new test:
http://www.upload.ee/files/3989901/recovery.img.html
Click to expand...
Click to collapse
Booted! Report time!
It can't flash sd-ext scripts.
Trying to mount or unmount partitions doesn't do anything and can get the vibration engine stuck on working.
hard bricked
cell bricked. time 4 ssc .hahaha.
only teamwin logo appearing.
sushil888 said:
cell bricked. time 4 ssc .hahaha.
only teamwin logo appearing.
Click to expand...
Click to collapse
Use test img files. Do all these only if you know how to recover. You'll have flash an older recovery using odin.
ast00 said:
Booted! Report time!
It can't flash sd-ext scripts.
Trying to mount or unmount partitions doesn't do anything and can get the vibration engine stuck on working.
Click to expand...
Click to collapse
Good...
Atleast it booted now...
You will have to help me.
-Boot into TWRP.
-Go to Mounts
-And select/un-select partitions and then install an sd-ext script and let it fail.
-Now, without doing anything else, give me the recovery log. (method in page #1)
And...you mean vibrator gets stuck in between?
Bhargav97 said:
Use test img files. Do all these only if you know how to recover. You'll have flash an older recovery using odin.
Good...
Atleast it booted now...
You will have to help me.
-Boot into TWRP.
-Go to Mounts
-And select/un-select partitions and then install an sd-ext script and let it fail.
-Now, without doing anything else, give me the recovery log. (method in page #1)
And...you mean vibrator gets stuck in between?
Click to expand...
Click to collapse
It's vibrating non stop and it only stops if I reboot.
http://pastebin.com/Bg5GJ8rF
This logs is weird... It looks like it does mount the stuff, it just doesn't update the ui.
ast00 said:
It's vibrating non stop and it only stops if I reboot.
Tapatalk-kal küldve az én GT-S5570-el
Click to expand...
Click to collapse
For me its not vibrating continuously but duration of vibration on a click or touch is really large.
One bug I noticed is that progress bars are not resized.
While backing up a ROM the indeterminate progress bar is fine but the blue one showing exact progress is not resized.
Its width is larger (it goes out of screen on rhs) and height is smaller than that of indeterminate progress bar so it doesn't actually appears as an overlay.I don't have camera now to show you a pic.I will show you pic after 2hrs
Sent from my GT-S5570 using XDA Premium 4 mobile app
ast00 said:
It's vibrating non stop and it only stops if I reboot.
http://pastebin.com/Bg5GJ8rF
This logs is weird... It looks like it does mount the stuff, it just doesn't update the ui.
Click to expand...
Click to collapse
Logs look fine.
@arpitkh96 says it's not vibrating non-stop but duration of vibration is long. I think, that can be managed somehow.
About the other report you gave of error when installing zip:
Your zip file's update-binary is old. You will need to update it. Replace /META-INF/com/google/android/update-binary file from cm11 or omni4.4 zip. You will need to do it in ANY zip that doesn't install. This is the way it works. KitKat has changed many a things, this is one of them.
Please try this and give result.
And, cm11 or omni or any other ROMs are installing or not?
Also, what do you mean by "mounting-unmounting partitions doesn't do anything." If the partitions are not mounted, your log would have errors but there are no errors.
@arpitkh96,
I know about that progress bar bug. Its theme related. I would fix it after fixing major recovery problems.
You can use any 240x320 twrp theme uptil then. It would work just fine.
For more info on Themes for TWRP, visit here:
http://forum.xda-developers.com/nexus-4/themes-apps/twrp-theme-collection-thread-t2035234
Hi,
I managed to build latest TWRP for N5100/N5110.
This a test build you can flash from your existing recovery.
Odin packages and flashable ZIPs are now available for n5100 and N5110.
Download:
http://www.androidfilehost.com/?w=files&flid=15631
What's new since 2.6.3.0?
What's new in 2.7.1.0:
Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
Various bugfixes to backup and restore
Improvements to USB storage handling
Added a class to search for files to make finding the correct brightness file automatic in most cases
Various other bugfixes and tweaks
NOTE: This is a test version and does NOT support f2fs, but you can switch to other filesystems
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 AOSP decrypt support
Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
Various SELinux fixes and bug fixes
Changelog:
Build 1:
-First release
Credits:
@sbrissen for original port and maintenance of CM11 for n5100/n5110/n5120.
@Dees_Troy & TEAMWIN for making TWRP
Reserved
i'm waiting for n5110
Is there any chance for a 5120 version, if you don't mind me asking.
Sent from my GT-N5120 using Tapatalk
Thx for your effort. Great to have a updated Recovery. Can this used for all kind of Roms? 4.1.2, 4.2.2 and 4.4.x?
Thank you for planning on including the 5110. I will patiently waiting for the addition of this device.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Build 2 is released.
Now n5100 and n5110 is supported. You can get tar files to flash via Odin or use zip files if you want to flash from your existing recovery (CWM, PhilZ or older versions of TWRP)
User_99 said:
Thx for your effort. Great to have a updated Recovery. Can this used for all kind of Roms? 4.1.2, 4.2.2 and 4.4.x?
Click to expand...
Click to collapse
I only tested with 4.4.x. But it should work with older ROMs too.
Fobz said:
Is there any chance for a 5120 version, if you don't mind me asking.
Sent from my GT-N5120 using Tapatalk
Click to expand...
Click to collapse
For now, I can't provide 5120 support.
whitemolecule said:
I only tested with 4.4.x. But it should work with older ROMs too.
For now, I can't provide 5120 support.
Click to expand...
Click to collapse
No problems!
Sent from my Nexus 4 using Tapatalk
Thanks much for flashable zips.
Works great. I've been waiting a long time for this release. Thank you. You rule.
Sent from my GT-N5110 using XDA Premium HD app
whitemolecule said:
Build 2 is released.
Now n5100 and n5110 is supported. You can get tar files to flash via Odin or use zip files if you want to flash from your existing recovery (CWM, PhilZ or older versions of TWRP)
Click to expand...
Click to collapse
Hello Sir thanks for your great work updating TWRP I been using Philz CWM recovery with no problems im thinking of trying yours which is better Philz CWM or TWRP hate to change since Philz is working let me know thanks
matthewtech770 said:
Hello Sir thanks for your great work updating TWRP I been using Philz CWM recovery with no problems im thinking of trying yours which is better Philz CWM or TWRP hate to change since Philz is working let me know thanks
Click to expand...
Click to collapse
The "better" is the one you choose.
Wow again. Quickly, I want to say, it's nice to get back to TWRP. Been using Philzs and it does a good job but not as smooth and easy as TWRP. The only rom I can't use this with is CivZ's new 4.4.2. It won't allow me to hit the "next" button when installing the rom. All other roms work perfect. This is donation good. Thank you again.
Sent from my GT-N5110 using XDA Premium HD app
Thanks for this. Seems It has problems with Aroma installers. The screen orientation specifically. The screen stays in landscape and only allows the top half of the screen to show the aroma installation, while the touch sensitivity is still in portrait. In other words you have to touch the screen as if it were in portrait and kind of guess where the buttons would be while the actual pictures on the screen are in landscape on only the top half of the screen and very stretched looking. Thanks again for your work.
kstephens98 said:
Thanks for this. Seems It has problems with Aroma installers. The screen orientation specifically. The screen stays in landscape and only allows the top half of the screen to show the aroma installation, while the touch sensitivity is still in portrait. In other words you have to touch the screen as if it were in portrait and kind of guess where the buttons would be while the actual pictures on the screen are in landscape on only the top half of the screen and very stretched looking. Thanks again for your work.
Click to expand...
Click to collapse
And that's why developers that use Aroma (like @civato) specify using Philz's Touch Recovery, which is a modified CWM, to flash their ROM's and kernels.
ramjet73
Nice observation. That is what I figured as well.. I usually have a flashable version of TWRP and Philz touch at the ready. I do a lot of testing with my tablet, with different roms and how apps work and can be modified with each.
Sent from my GT-N5110 using XDA Premium HD app
glockman4519 said:
Nice observation. That is what I figured as well.. I usually have a flashable version of TWRP and Philz touch at the ready. I do a lot of testing with my tablet, with different roms and how apps work and can be modified with each.
Click to expand...
Click to collapse
Yea, I do the same thing.
The easiest way I've found to switch recoveries is to keep "recovery.img" versions of each one on the SD card, then move the files you want to flash to the SD card, use Flashify to install the recovery needed if it's not already there, then reboot into recovery with the advanced power menu. It's still a good idea to keep the .zip version of each recovery on the SD card in case you're already in recovery before you discover that you have the wrong version installed. It would be nice to have USB OTG mount available in this version of TWRP recovery since I can't seem to get USB storage working as there appears to be some conflict with ADB.
I tend to do all my backups with TWRP though since it supports compression and restores have been more reliable for me than using CWM. The backup formats are different so it doesn't make sense to use both.
If the Samsung devices supported "fastboot boot recovery.img" like Nexus, HTC and most other brands it wouldn't be necessary to actually flash an alternate recovery since it could just be booted as needed when the tablet is connected to a computer.
Edit: I just discovered that the "fixed" 2.6.3.0 version of TWRP from this post works fine with Aroma. It doesn't have the USB storage option in mounts (explained in this post) but I can't get that to work with this 2.7.1.0 version anyway. I'd love to use this updated version of TWRP but it would be nice if the Aroma support could be included from the 2.6.3.0 version and an OTG mount option (as opposed to USB storage) could be added.
ramjet73
I was wondering if there would be a possibility of getting this recovery in portrait mode. I am wanting to use a Holofied theme that has more options that can utilize TWRP even better but it does not work with landscape layout. I have already tried to take the Grouper TWRP and used its res folder and added that to the n5110 twrp and repacked the recovery.img and flashed but recovery is still in landscape but is displaying a portrait layout which is unusable.
pimpmaneaton said:
I was wondering if there would be a possibility of getting this recovery in portrait mode. I am wanting to use a Holofied theme that has more options that can utilize TWRP even better but it does not work with landscape layout. I have already tried to take the Grouper TWRP and used its res folder and added that to the n5110 twrp and repacked the recovery.img and flashed but recovery is still in landscape but is displaying a portrait layout which is unusable.
Click to expand...
Click to collapse
Yes, I will try to build in portrait mode when I have time, I think this will also fix aroma installer issues too.