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:
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 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
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
What's new in 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
What's new in 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
Downloadhttp://techerrata.com/browse/twrp2/m8
Huge shoutouts go specifically to
@Flemmard @bigbiff @Dees_Troy
I learned how to properly deal with DTB from these guys....
Known Issues:
No known issues anymore
No exFAT support. Need kernel source to investigate. This is only temporary. FAT32 works perfectly fine.
Random segfaults when starting actions. i.e. flashing restoring, backing up. Just makes you redo what you were trying to do. Dees_troy deems this nearly impossible to trace.
hmm wondering if this will work for the ATT variant since the DTB is variant specific usually, at least thats how it was on the G2.
Just wondering about off mode charging. Is it ok? I know there were issues with 2.7 on the m7. I was just wondering are the same issues present in the m8?
Whenever I finish flashing a ROM the screen goes off immediately, doesn't give me the chance to reboot. Doesn't seem right?
nice one thanks i can backup to ext sd now
djkinetic said:
hmm wondering if this will work for the ATT variant since the DTB is variant specific usually, at least thats how it was on the G2.
Click to expand...
Click to collapse
im using it on ATT version just fine
Ghost said:
Just wondering about off mode charging. Is it ok? I know there were issues with 2.7 on the m7. I was just wondering are the same issues present in the m8?
Click to expand...
Click to collapse
off mode charging works just fine.
guywithdesire1992 said:
Whenever I finish flashing a ROM the screen goes off immediately, doesn't give me the chance to reboot. Doesn't seem right?
Click to expand...
Click to collapse
In the second post, it talks about this.
jmz said:
im using it on ATT version just fine
off mode charging works just fine.
In the second post, it talks about this.
Click to expand...
Click to collapse
Excellent just wanted to make sure as DTB can be kind of a pain, when it comes to different variants.
djkinetic said:
Excellent just wanted to make sure as DTB can be kind of a pain, when it comes to different variants.
Click to expand...
Click to collapse
From the experimenting that has been done all the GSM DTBs are compatible with each other. And all the CDMA DTBs are compatible with each other. But not between GSM and CDMA.
Well i just tried on my m8 att variant and i get stuck at the teamwin curtain screen go figure lol
djkinetic said:
Well i just tried on my m8 att variant and i get stuck at the teamwin curtain screen go figure lol
Click to expand...
Click to collapse
Thats very odd. I have the ATT variant and using this
Try 2 things for me. Reflash but do fastboot erase cache before doing it. Then if it still doesn't work see if you have ADB when at the splash
jmz said:
Thats very odd. I have the ATT variant and using this
Try 2 things for me. Reflash but do fastboot erase cache before doing it. Then if it still doesn't work see if you have ADB when at the splash
Click to expand...
Click to collapse
i did that and it didnt work, i do have working adb which is how i was able to get back in hboot/fastboot.
Ok i was able to fix the hang, deleted my twrp theme folder and twrp settings from the other 2.6.3.3 version of twrp.
djkinetic said:
i did that and it didnt work, i do have working adb which is how i was able to get back in hboot/fastboot.
Ok i was able to fix the hang, deleted my twrp theme folder and twrp settings from the other 2.6.3.3 version of twrp.
Click to expand...
Click to collapse
ah yeah. that will do it.
should this be supporting ext sd card for rom installations? when i browse to External SD, my rom.zip isn't seen, folder looks empty.
nugzo said:
should this be supporting ext sd card for rom installations? when i browse to External SD, my rom.zip isn't seen, folder looks empty.
Click to expand...
Click to collapse
Did you check internal sd it might of saved it there
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Jarheadflip said:
Did you check internal sd it might of saved it there
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes i know it on my internal, i had to put it there to install it. but i would like to have my rom install files on my external and save my internal space for apps etc.
nugzo said:
yes i know it on my internal, i had to put it there to install it. but i would like to have my rom install files on my external and save my internal space for apps etc.
Click to expand...
Click to collapse
Is your sdcard in exFAT format? If so check second post
Sent from my HTC One_M8 using Tapatalk
Finally some good recovery
jmz said:
Is your sdcard in exFAT format? If so check second post
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I'll check. I formatted it with my phone, shouldn't that format it correctly?
Will this work with the Sprint version?
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.
Dees_Troy said:
[RECOVERY] TeamWin Recovery Project (twrp) 2.0.0RC0 [2011-12-17]
Team Win Recovery Project 2.0, or twrp2 for short, is a custom recovery built with ease of use and customization in mind.
Special thanks to xboarder56 for helping test the port and a couple of other testers that I forget the names of at the moment.
Click to expand...
Click to collapse
NICE, thanks to the both of you! Goin' on tonight fo sho.
Very nice job guys! I just might have to update my signature now.
Is there any future in external sdcard support?
Looks good I guess I'll have to update from the old version, thanks.
Awesome work guys.... this kicks total butt!
Nice! It's come a long way since I used it on my 3D. Alot faster compressed backup, thanks
Sent from my HTC Amaze 4G using xda premium
Has anyone had luck installing this on amaze????
Sent from my HTC Amaze 4G using xda premium
milo356 said:
Has anyone had luck installing this on amaze????
Sent from my HTC Amaze 4G using xda premium
Click to expand...
Click to collapse
I have. I can do it in different ways. flash_image recovery recoveryname.img command from the phone itself if you have the flash_image binary installed or by fastboot flash recovery recoveryname.img with the phone in bootloader mode.
Not complicated at all.
Works great, so much better than using the volume up/down keys and power keys. Two weird things that I want to see if anyone else is having issues with (want to know if it is worth reporting on the github)
1. After accessing recovery I get the "Tell HTC" This phone has just recovered from a abnormal reset message. Didn't get that with clockwork, not sure if it is a bug or not.
2. Cant mount ext SD card. Saw that the EVO 3D had the same issue but they had fixed it. I assume this is a problem with the Amaze since it is the same with clockwork mod?
Sikety said:
Works great, so much better than using the volume up/down keys and power keys. Two weird things that I want to see if anyone else is having issues with (want to know if it is worth reporting on the github)
1. After accessing recovery I get the "Tell HTC" This phone has just recovered from a abnormal reset message. Didn't get that with clockwork, not sure if it is a bug or not.
2. Cant mount ext SD card. Saw that the EVO 3D had the same issue but they had fixed it. I assume this is a problem with the Amaze since it is the same with clockwork mod?
Click to expand...
Click to collapse
Use this one if you want to backup and restore to and from external sdcard.
pardon the question, I've looked all over TeamWin's web site... Is there a way to boot the Amaze into twerp directly?
gregma said:
pardon the question, I've looked all over TeamWin's web site... Is there a way to boot the Amaze into twerp directly?
Click to expand...
Click to collapse
I don't understand your question.
You want to reboot into recovery?
adb reboot recovery
or use the 22 different other ways to reboot into recovery.
Binary100100 said:
I don't understand your question.
You want to reboot into recovery?
adb reboot recovery
or use the 22 different other ways to reboot into recovery.
Click to expand...
Click to collapse
I'm talking about rebooting into recovery when I'm not anywhere near a computer. Such as on my HD2, I would hold the power button down until in MAGLDR, then choose to boot into Recovery. Is there something similar on the Amaze?
Greg
gregma said:
I'm talking about rebooting into recovery when I'm not anywhere near a computer. Such as on my HD2, I would hold the power button down until in MAGLDR, then choose to boot into Recovery. Is there something similar on the Amaze?
Greg
Click to expand...
Click to collapse
Which rom are you using?
There are a couple of roms that have the Advanced Power Menu that has a reboot option. When selected it gives you other options such as recovery and bootloader.
There are also a few apps (do a search for Reboot Recovery) on the Market.
I have always used the option from ROM Manager.
You can also use terminal emulator and use the command "reboot recovery" and that should do it too.
You can also power off the device, hold volume down while pressing power to get to hboot mode then select recovery.
Binary100100 said:
Which rom are you using?
There are a couple of roms that have the Advanced Power Menu that has a reboot option. When selected it gives you other options such as recovery and bootloader.
There are also a few apps (do a search for Reboot Recovery) on the Market.
I have always used the option from ROM Manager.
You can also use terminal emulator and use the command "reboot recovery" and that should do it too.
You can also power off the device, hold volume down while pressing power to get to hboot mode then select recovery.
Click to expand...
Click to collapse
Stock ROM right now, I'm getting things set to start flashing new ROM's. Aha! I did see the "recovery" in hboot. Now once I figure out how I lost the ability to get into hboot by holding the volume down button I'll be good to go!
Greg
---------- Post added at 01:55 PM ---------- Previous post was at 01:22 PM ----------
gregma said:
Stock ROM right now, I'm getting things set to start flashing new ROM's. Aha! I did see the "recovery" in hboot. Now once I figure out how I lost the ability to get into hboot by holding the volume down button I'll be good to go!
Greg
Click to expand...
Click to collapse
I LOVE answering my own darned post.... Didn't realize you had to battery power cycle the device to get it back into hboot. I'm good to go now!
Greg
ok i got it loaded up fine on my phone but i cannot figure out how to flash. i click the install button and it takes me to my directories but i dont see any files in the directories... there is no files listed in the root of either sd card as well. what am i doing wrong?
2sh0rt said:
ok i got it loaded up fine on my phone but i cannot figure out how to flash. i click the install button and it takes me to my directories but i dont see any files in the directories... there is no files listed in the root of either sd card as well. what am i doing wrong?
Click to expand...
Click to collapse
Move the zip file to the other sdcard. Remember that you have two.
Here's a free tip!
Make two empty zip files.
Name one internal.zip
Name the other external.zip
Place the internal.zip in the internal sdcard and the external.zip in the external sdcard.
Reboot into recovery and if you see internal.zip file. Guess what sdcard you're looking at? Same goes for external.
Binary100100 said:
Move the zip file to the other sdcard. Remember that you have two.
Here's a free tip!
Make two empty zip files.
Name one internal.zip
Name the other external.zip
Place the internal.zip in the internal sdcard and the external.zip in the external sdcard.
Reboot into recovery and if you see internal.zip file. Guess what sdcard you're looking at? Same goes for external.
Click to expand...
Click to collapse
Dude, i know this... i came from the vibrant. Im saying that NEITHER card shows ANY files... only directories... no zips on the root of /sdcard or /sdcard/ext-sd... nada, zip, zilch
2sh0rt said:
Dude, i know this... i came from the vibrant. Im saying that NEITHER card shows ANY files... only directories... no zips on the root of /sdcard or /sdcard/ext-sd... nada, zip, zilch
Click to expand...
Click to collapse
I came from the vibrant as well however I wasn't so active there.
I don't understand why you don't see any zip files then. Strange.
Me either... think i'll just try and reload it and see what happens. Thought maybe i was clicking the wrong thing or not clicking something.
---------- Post added at 07:47 PM ---------- Previous post was at 07:43 PM ----------
and its not just that i dont see any zip files. i dont see ANY files at all! every directory i click is empty! even on the system partition! not a single file shows up. only directories and when i click them there is nothing except /.. and /.
TWRP 2.x-JB is now available for use on devices that have the Asus JB bootloader ONLY, please see our website for download information. Do NOT install if you are on the ICS bootloader.
We HIGHLY recommend users enable and backup your devices before flashing custom roms/recoveries or updating to the JB OTA with nvflash courtesy of AndroidRoot.mobi (this also makes your device essentially "brick-proof" so there's no reason not to do it)***
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.5.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.5.0.0 as your custom theme will likely not be compatible with the new changes!
-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
-Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
-Fixed a problem with md5 verification of backups
-Added a search function to libtar (thanks to kokotas)
-Improve handling of XML errors (fix permissions)
-Fixed handling of subpartitions
-Improvements to recovery.fstab flags
-Fixed a problem with decryption not being able to locate the decryption key in some situations
CHANGELOG for 2.4.4.0:
-Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
-More fixes for the file selector
-Switched from using busybox md5sum to a direct C function call
-Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
-Update exFAT to latest commits
-Added a build flag to disable using the ioctl for screen blanking
CHANGELOG for 2.4.3.0:
-Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
-Added a scroll bar to file selectors and listboxes courtesy of Tassadar
-Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
-Added a screen dim effect 2 seconds before screen off on some devices
-Finally fixed file selector crash (one of the joys of working with multi-threaded software)
-Fixed loading of screen timeout setting during startup
-Improvements and bugfixes to screen timeout code
-Fixed persistence of the 24 hour / military time setting
CHANGELOG for 2.4.2.0:
-Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
-Add a brightness setting (requires device specific setup and only some devices have been added)
-Add a root checker and offer to install SuperSU if the device isn't already rooted
-Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
-Check and offer to fix root permissions if broken
-Add an option for a 24 hour clock display instead of AM/PM (aka military time)
-Move stock recovery reflash check to occur during the reboot cycle
-Add support for some MTK6xxx devices
-Change libtar to vfork to help prevent memory problems
-Add a "clicked" effect to most buttons, file selector, and listbox
-Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
-Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
-Other minor bugfixes and improvements
CHANGELOG for 2.4.1.0:
-Fixed a problem with mkdosfs that formatted sdcards to 2GB
-Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
-Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
-Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
CHANGELOG for 2.4.0.0:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
-Support for exFAT formatted sdcards (also thanks to bigbiff)
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Improvements for building TWRP in CM10.1
-Other minor bugfixes and improvements
NOTE: 2.4.0.0 is, as always, still compatible with your older backups!
CHANGELOG for 2.3.3.0:
-Fix renaming backups with a space in the name
-Add decrypt button to mount page if you cancel decryption during startup
-Added ignore blkid flag
-Fixed handling of MTD partitions during mount
-Fixed some keyboard mapping issues on 800x1280 layout
CHANGELOG for 2.3.2.0:
-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
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
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: (THIS METHOD IS CURRENTLY DISABLED FOR THIS DEVICE SEE THE WEBSITE FOR MORE INFORMATION ON HOW TO FLASH)
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 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.
Using this on my i9250, nice to see it here as well.
WTF. I just said today I wish TWRP was on the TFP. Wow. I love it on my Sensation now and I know I'll love it on my TFP. Thanks Team Win!!!
Sent from my EPAD using xda premium
Do we need to unlock the bootloader to flash this recovery?? I would prefer option "ADB / Terminal method"
Amazing, my cable is at work, or else I'd be flashing this right now! I love to see the prime get supported, thanks Team Win!
[email protected] said:
Do we need to unlock the bootloader to flash this recovery?? I would prefer option "ADB / Terminal method"
Click to expand...
Click to collapse
Of course you need to be unlocked
Anyone install yet how do you like it?
one question: is this like CWM? can it replace that?
Awesome!! Only Recovery I'll use on my Evo 3D, it is simply amazing!!! Thank you Team Win for all of your hard work!!
---------- Post added at 01:40 AM ---------- Previous post was at 01:33 AM ----------
godlyitem said:
one question: is this like CWM? can it replace that?
Click to expand...
Click to collapse
Yes, this is a custom recovery and you can only use one. CWM is the most common as it has support on a lot of devices. That said, I've never been a fan of CWM and used other recoveries on my last couple of phones. TWRP(Team Win Recovery Project) is an awesome touch recovery that has never once failed me and works flawlessly every time on my Evo 3D. CWM didn't wipe certain partitions on the Evo 3D for the longest, not sure if it even does now. TWRP has always wiped just fine and is very user friendly!!!
this is awesome..a few things though
if you have backups already that you made in clockwork they do not come up in the restore section. not sure if there is a way for them to appear or not but this could be a problem
also, like clockwork it appears to have the dating bug where if you make a backup for some reason it is naming it as the 5th month right now. 2012-05-24-1-0-5 something like that the same bug has been in clockwork as well.
This is awesome man! Now I can have twrp on my Evo 3D and my Prime. Looks like I'll have something to do work tomorrow.
Sent from my Anthrax infected 3D!
If I've helped you in any way... hit the "Thanks" button.
Hi!
It's awesome!
I have successfully installed it from cwm 5.2.8.0 with the zip file.
After installation, i made a backup and wiped all data, cache and system.
I try to install aopk, wsg, virtuous prime and primalicious without any problem!
And the same thing with motleys and snb kernel 's.
ShreckBull said:
Hi!
It's awesome! ...I try to install aopk, wsg, virtuous prime and primalicious without any problem! And the same thing with motleys and snb kernel 's.
Click to expand...
Click to collapse
Thanks for the feedback! Really appreciate you taking the dive and running all those "tests"
By the way, which AOKP did you try this out on? v1.3 with Reboot to Recovery or just normal? I'm curious to see if the former works OK on this recovery as it'll only work on repacked CWM...
i use aopk 1.3 now for test it.
each time i use power+ vol down... no reboot to recovery.
OK, I see known issue about "no reboot to recovery"... in the OP.
Has anyone else experienced booting to recovery from powered off state?
I'm on Eos #7 and this morning after I flashed it, I decided to power off. When I turned it back on, it went straight to recovery. No worries though as hitting reboot -> system took me right back out of recovery.
Just giving feedback. Hope it helps.
knives of ice said:
this is awesome..a few things though
if you have backups already that you made in clockwork they do not come up in the restore section. not sure if there is a way for them to appear or not but this could be a problem.
Click to expand...
Click to collapse
Same question here. I'm really interested in this. Will I still be able to restore from backups made from CWM? I also have Rom Manager installed. I take it that after I install this recovery, there is no need to keep Rom Manager? I only use it to see if CWM has issued any updates anyway. -Thanks
Subsonic44 said:
Same question here. I'm really interested in this. Will I still be able to restore from backups made from CWM? I also have Rom Manager installed. I take it that after I install this recovery, there is no need to keep Rom Manager? I only use it to see if CWM has issued any updates anyway. -Thanks
Click to expand...
Click to collapse
Unfortunately CWM backups are not compatible. So I'd suggest making a fresh backup as soon as you flash TWRP. I'll add this to the OP.
So we can just flash this from cwm?
Sent from my ADR6300 using xda premium
eyeballer said:
Unfortunately CWM backups are not compatible. So I'd suggest making a fresh backup as soon as you flash TWRP. I'll add this to the OP.
Click to expand...
Click to collapse
Flash went fine. I'm backing up now. I guess if I ever really need a cwm backup, I could always reflash cwm and restore so I think I'll keep those backups anyway. Can you verify that there is no need for Rom Manager now? Thanks for the great work!
Subsonic44 said:
Flash went fine. I'm backing up now. I guess if I ever really need a cwm backup, I could always reflash cwm and restore so I think I'll keep those backups anyway. Can you verify that there is no need for Rom Manager now? Thanks for the great work!
Click to expand...
Click to collapse
Correct, no need for ROM manager. We're working with the Goo.im team and have support in the works for the tf201 with goo manager: https://play.google.com/store/apps/details?id=com.s0up.goomanager
If any of your favorite ROMs are hosted there you can use that app to get notifications of new builds, AOKP and EOS are supported. You can also download the recovery flashable .zip through the app too.
Team Win Recovery Project 3.x, or twrp3 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.
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!
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.
Dees_Troy said:
Thanks to Dr_Drache for testing for me!
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.0:
-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
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
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!
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.
Click to expand...
Click to collapse
Sweet thanks.
Sent from my CM9 HTC Thunderbolt from Tapatalk 2.4
Note, I forgot to have Dr_Drache test off-mode charging. Can someone install this, turn the device completely off, then plug it into a charger. The charge light should come on, maybe blink once or twice, but after about 2 minutes, the charge light should stay on without blinking anymore. Please let me know!
jonah1234 said:
Sweet thanks.
Sent from my CM9 HTC Thunderbolt from Tapatalk 2.4
Click to expand...
Click to collapse
THANK YOU
Dees_Troy said:
Note, I forgot to have Dr_Drache test off-mode charging. Can someone install this, turn the device completely off, then plug it into a charger. The charge light should come on, maybe blink once or twice, but after about 2 minutes, the charge light should stay on without blinking anymore. Please let me know!
Click to expand...
Click to collapse
Off mode charging is fine
Sent from my ADR6425LVW using Tapatalk 2
vinylfreak89 said:
Off mode charging is fine
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Good deal, thanks for checking it and confirming.
I've ran into some trouble with mine. I have created three backups, each with slight differences to system, trying some things out on the ROM. The lase edit was the build.prop. It wouldn't boot so I went to Recovery to restore one of my backups. When it is a good 10 seconds into restoring system, the progress bar stops turning and it reboots. Each time I try this it seems to stop at a slightly different point into the system restore. Most of the time it wont go far enough to allow boot, just the splash screen and then it automatically boots into TWRP.
All of that is ok, and I could get around it, but now my phone is dead! Any suggestions?
*Edit* Got it guys. I was able to use the USB charger from my TPrime and it charged in TWRP. After it charged a bit I was able to fastboot flash TWRP again and restore one of the backups. I'm not sure how it became corrupted, but its all good now!
When will the size be fixed?
Sent from my HTC Droid DNA
jonah1234 said:
When will the size be fixed?
Sent from my HTC Droid DNA
Click to expand...
Click to collapse
I don't have a DNA or any other 1080 * 1920 device that uses a portrait layout (no rotation in recovery). I am unable to do the upscale myself. There's a theme guide on our website if someone wants to to do it.
Dees_Troy said:
I don't have a DNA or any other 1080 * 1920 device that uses a portrait layout (no rotation in recovery). I am unable to do the upscale myself. There's a theme guide on our website if someone wants to to do it.
Click to expand...
Click to collapse
Alright I will give that a try later today.
Sent from my HTC Droid DNA
For some reason I can't make backups anymore. It gets about a quarter way, then reboots. I tried cwm..and same issue. Anyone have any ideas?
it has rebooted on me during a backup as well. i tried again and was successful, but there definitely seems to be a bug somewhere
Hello,
Definitely a bug, seems that after the first successful backup unit will no longer get past the system file.
UPDATE, your backups will complete if you do not change the name. Leave it as the date or default name If this does not work for you the only other thing I have done since it was rebooting was to install/update busybox. This may also work for those who are restoring backups and getting the reboot...did you change the file name? Whatever I am sure it is just a temp bug that will be fixed soon as well as the layout.
Cheers
Has anyone got a fix for the screen size yet?
starscream86 said:
Has anyone got a fix for the screen size yet?
Click to expand...
Click to collapse
I was looking into it ealier today. I haven't gotten it just yet tho.
Sent from my HTC Droid DNA
jschill31 said:
Hello,
Definitely a bug, seems that after the first successful backup unit will no longer get past the system file.
UPDATE, your backups will complete if you do not change the name. Leave it as the date or default name If this does not work for you the only other thing I have done since it was rebooting was to install/update busybox. This may also work for those who are restoring backups and getting the reboot...did you change the file name? Whatever I am sure it is just a temp bug that will be fixed soon as well as the layout.
Cheers
Click to expand...
Click to collapse
I have backups failing when not changing the name as well. Bug happens either way.
After several attempts I am eventually able to get a good backup, but it fails more often than it completes.
Deuces said:
I have backups failing when not changing the name as well. Bug happens either way.
After several attempts I am eventually able to get a good backup, but it fails more often than it completes.
Click to expand...
Click to collapse
Interesting, obviously this needs a bit of work. I have not tried to make another one, I have been spending time modding the factory shipped rom. There are so many features hidden by Verizon. Also there is something running in the background that eats our batteries. Hard to start cranking on a rom without a reliable recovery. I sent a note over on the TWRP website, hopefully someone will have some ideas. On the size issue has anyone tried using a TWRP skin from one of the 1080p tablets?
Cheers
Have you looked into using one of the 1080p tablet themes? I plan on doing that tonight.
Sent from my HTC6435LVW using Tapatalk 2
jschill31 said:
Have you looked into using one of the 1080p tablet themes? I plan on doing that tonight.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
Any luck with that?
starscream86 said:
Any luck with that?
Click to expand...
Click to collapse
Hello,
Actually a big NO on that...this recovery isn't even recognizing the THEME folder? It seems this has a few bugs to iron out. I looked at pulling the resource the other day and building a new one but I can't seem to find a reliable git for the DNA? If anyone knows of one please let me know and I will pull the files late tonight. I am not a DEV by all means but have been building for multiple devices for over two years and have a smoking build machine. I am not comfortable working on any roms until we have a solid recovery. Don't get me wrong, this does backup after a few tries but what I am worried about is a fail when trying to restore. I have read where Clockwork it the same way, seems to have something to do with the partitions?
Cheers
This is for all variants of the Desire 601
From their site:
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.
CHANGELOG 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
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
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
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
NOTES:
This is the official version of TWRP for our device only modified with the updated partition mount points as changed by the KitKat OTA.
I have also modified it to display the version "v2.7.1.1 (KK)" to visibly distinguish it from the 2.7.1.0 official version.
This is only for Desire 601 users who have updated to KitKat or, at the very least, attempted the update and had their partitions remapped. If you have not updated to KitKat using the OTA you need to use the original version which can be found on their website here.
This is for all variants - zara_cl and zara_ul
DOWNLOAD:
Two links are available for you to download from:
1) My Google Drive
2) Dev-Host
BUGS:
-The only bug I have found so far is when you select Advanced Wipe from the Wipe screen you will see Data listed twice. The second data is actually Internal Storage, so use caution when wiping your device.
This Recovery is only for KitKat right?
So If I'm still on JB I mustn't flash this right? but how if one day the Insertcoin KitKat released and I want to use it, should I flash the Recovery first or the ROM first?
Akishima said:
This Recovery is only for KitKat right?
So If I'm still on JB I mustn't flash this right? but how if one day the Insertcoin KitKat released and I want to use it, should I flash the Recovery first or the ROM first?
Click to expand...
Click to collapse
This is only for people who have updated to KitKat because it remaps the relevant partitions during the update process.
If you haven't done the update, your partitions haven't been remapped and therefore the official version will work just fine for you.
-Duir- said:
This is only for people who have updated to KitKat because it remaps the relevant partitions during the update process.
If you haven't done the update, your partitions haven't been remapped and therefore the official version will work just fine for you.
Click to expand...
Click to collapse
On KitKat from other means(backup restore) this is for me then right?
Kolma said:
On KitKat from other means(backup restore) this is for me then right?
Click to expand...
Click to collapse
I know you tried the OTA, so If your partitions got remapped then yes, if not then no.
i want to install this recovery i have untouched(locked) ZARA_UL(unlocked to all carrier) phone but S-OFF'd when i bought it...so can i simply install this recovery???????? without unlocking bootloader ....and plz guide me how to do it..........
rajat836 said:
i want to install this recovery i have untouched(locked) ZARA_UL(unlocked to all carrier) phone but S-OFF'd when i bought it...so can i simply install this recovery???????? without unlocking bootloader ....and plz guide me how to do it..........
Click to expand...
Click to collapse
U cant install recovery with a locked bootloader
rajat836 said:
i want to install this recovery i have untouched(locked) ZARA_UL(unlocked to all carrier) phone but S-OFF'd when i bought it...so can i simply install this recovery???????? without unlocking bootloader ....and plz guide me how to do it..........
Click to expand...
Click to collapse
Child's Play said:
U cant install recovery with a locked bootloader
Click to expand...
Click to collapse
The recovery image in it's current state requires an unlocked bootloader. However, being S-OFF you can make a special zip file that allows the bootloader to flash it directly with out being unlocked.
-Duir- said:
The recovery image in it's current state requires an unlocked bootloader. However, being S-OFF you can make a special zip file that allows the bootloader to flash it directly with out being unlocked.
Click to expand...
Click to collapse
sir plz help me to s-on my device then i will unlock bootloader by myself through htcdev(((((((i dont want s-off its risky i think and.... i can install custom rom,recovery,kernel with just unlocked bootloader???)))) .......
Hint
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.1-zaracl.img
@-Duir- is there any update for TWRP recovery (kitkat)?
they already release the 2.8 version for Zara but I don't know whether it's for kitkat or JB
Akishima said:
@-Duir- is there any update for TWRP recovery (kitkat)?
they already release the 2.8 version for Zara but I don't know whether it's for kitkat or JB
Click to expand...
Click to collapse
Official is still for JB. I have a modified KK version ready to go, I just need to check two things to see if they're issues with the official version or somehow created by modifying it.
I will also likely make a new thread when I upload it so that it will show up via devdb.
EDIT: New version posted in a new devdb thread. Though accidently in the wrong sub-section.
I'm hoping it can be moved, if so it will be moved to this section, also I will be requesting this thread removed.
Moderator Information
Thread has been closed at OP's request
Many thanks,
Ghost
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.8.6.0:
Fix daylight savings time rules for USA and Europe (_that)
Allow mulitple overlays for popup boxes (Dees_Troy)
Add pattern style password entry for decrypt (Tassadar)
Keyboard improvements (_that)
Update AOSP base to 5.1 (Dees_Troy)
Reduce theme count to 5 and rely on scaling (Dees_Troy)
Various scaling improvements (Dees_Troy)
Improved handling of resources in the GUI (_that)
Make scroll bar size proportional to list size (_that)
Allow scoll lists to render without a header (_that)
Make console scroll per pixel with kinetic scrolling (_that)
Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
CHANGELOG for 2.8.5.0:
Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
Improve thread handling and move input handling into the main rendering thread to improve stability
Make MTP work even if unplugged and plugged back in
Unify scrollable list code and make kinetic scrolling feel more natural
Fix handling of mapped zip files for OTA updates (CM12 updater)
USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
Other small fixes and improvements
CHANGELOG for 2.8.4.0:
Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
Fix some MTP related crashes and bugs
Eliminate TWRP toggling USB IDs during boot if MTP is enabled
Fix various adb sideload issues
Improve threading of actions
Eliminate separate thread for screen timeout
Update libblkid to 2.25.0
Use power button as back button on watch themes for easier navigation
Add mutex locking to data manager
Improve custom theme handling on encrypted devices
Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
CHANGELOG for 2.8.3.0:
MTP will now tell the host PC that storage is removed instead of disabling MTP completely
MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
Update and improve fix permissions and make fixing contexts optional
Update SuperSU in TWRP to 2.40 and update install process
Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
Fix kernel panic during MTP start on some devices
Support unicode fonts on devices with True Type Font support
Fix slider value not showing sometimes (vibration settings page)
Toggle MTP off during adb sideload to set correct USB IDs
Reduce library requirements for 5.0 L decrypt
Other minor fixes and improvements
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.
Everything seems to be working. No known issues. USB-OTG works also
Downloadhttps://www.androidfilehost.com/?fid=24052804347756852
or use our TWRP Manager software to install it automatically for you
Install either by DD or maybe flashify will work for you.
Code:
dd if=recovery.img of=/dev/block/mmcblk0p7
Thanks goes to @Dees_Troy as this was my first MediaTek based device to build recovery for
This will also be taken official this week.
Pulled download temporarily
Thanks for your work dude but we do not have recovery image for our Fire 6 HD sadly ...
alucard_xs said:
Thanks for your work dude but we do not have recovery image for ou Fire 6 HD sadly ...
Click to expand...
Click to collapse
The HD 7 and HD 6 are EXACTLY the same device. The OTAs for both are EXACTLY the same. The only difference is the screen size. There essentially is no difference betweent the 2 devices
Sure but what about factory / recovery image, is there anyone floating around ?
alucard_xs said:
Sure but what about factory / recovery image, is there anyone floating around ?
Click to expand...
Click to collapse
just dump your current recovery.img.
dd if=/dev/block/mmcblk0p7 of=/sdcard/stockrecovery.img
Then as soon as you boot into recovery make a backup.
Root
Will flashing the SuperSU package in recovery root, or cause a bootloop?
ryanyz10 said:
Will flashing the SuperSU package in recovery root, or cause a bootloop?
Click to expand...
Click to collapse
Dont need to flash anything with TWRP. If you boot twrp then choose reboot to system option it will ask if you want to install SuperSU.
Reuploaded fixed version. Found a couple bugs that i didn't notice before. All good now
So for us the slow ones, can you explain this in detail?
You've replaced the stock recovery with TWRP, so we can flash images from USB drives ? But you need root to do the first flash to recovery, correct?
Will Amazon update re-write the recovery partition so you are back to stock ?
bibikalka said:
So for us the slow ones, can you explain this in detail?
You've replaced the stock recovery with TWRP, so we can flash images from USB drives ? But you need root to do the first flash to recovery, correct?
Will Amazon update re-write the recovery partition so you are back to stock ?
Click to expand...
Click to collapse
yes. and future custom roms if they come. You should be disabling OTAs anyways. OTAs im pretty sure will fail anyways with a custom recovery
jmz said:
yes. and future custom roms if they come. You should be disabling OTAs anyways. OTAs im pretty sure will fail anyways with a custom recovery
Click to expand...
Click to collapse
Man, that's pretty awesome! It sounds like one just needs one good TWRP flash, and then it's not that hard to recover after a screw up via OTG.
And it seems like with this TWRP we should be able to flash Amazon updates onto the device (such as 4.5.4), and install root on top after that ? Root 4ever ? How hard is it to make TWRP flash stock Amazon updates ? I want 4.5.4 , with root !!!
You could also change the size of /cache, and add it to /data, or move dalvik cache from /data to /cache, see these allocations (there is 1 Gb of space in /cache !!!):
http://forum.xda-developers.com/fire-hd/help/internal-memory-structure-hidden-t3122246
So even without a custom ROM there are tons of easy tweaks that one could do.
I actually got to like the Fire OS, it is super stable for me. With custom recoveries things are often quite rocky for a while. I'd like to get some sort of Android Setup app, in order to change things above and beyond what Amazon allows (such as that Cyrillic AOSP keyboard!).
Once you figure out how to put stock Amazon update files onto the device plus root, you can pretty much play with Xposed and get into risky stuff (not being afraid of bootloop.) Just make sure to keep the trusty TWRP handy!!!
bibikalka said:
Man, that's pretty awesome! It sounds like one just needs one good TWRP flash, and then it's not that hard to recover after a screw up via OTG.
And it seems like with this TWRP we should be able to flash Amazon updates onto the device (such as 4.5.4), and install root on top after that ? Root 4ever ? How hard is it to make TWRP flash stock Amazon updates ? I want 4.5.4 , with root !!!
You could also change the size of /cache, and add it to /data, or move dalvik cache from /data to /cache, see these allocations (there is 1 Gb of space in /cache !!!):
http://forum.xda-developers.com/fire-hd/help/internal-memory-structure-hidden-t3122246
So even without a custom ROM there are tons of easy tweaks that one could do.
I actually got to like the Fire OS, it is super stable for me. With custom recoveries things are often quite rocky for a while. I'd like to get some sort of Android Setup app, in order to change things above and beyond what Amazon allows (such as that Cyrillic AOSP keyboard!).
Once you figure out how to put stock Amazon update files onto the device plus root, you can pretty much play with Xposed and get into risky stuff (not being afraid of bootloop.) Just make sure to keep the trusty TWRP handy!!!
Click to expand...
Click to collapse
Yeah, I am going to be working on the update this week. Starting a new job tomorrow.
Also, I added a link to our software TWRP Manager so it is even easier to install TWRP.
jmz said:
Yeah, I am going to be working on the update this week. Starting a new job tomorrow.
Also, I added a link to our software TWRP Manager so it is even easier to install TWRP.
Click to expand...
Click to collapse
I just saw your boot unlocker thread, you should better manage your cross-references Congrats for getting us this far!
But I wonder if one could just flash 4.5.4 first, and then unlock the bootloader, and install TWRP, then root. Which bootloader versions can be unlocked? All so far? So people who were force updated to 4.5.4 are not SOL ?
Of course, it's easier to just have TWRP flash Amazon updates, then root is always available. That would be an enabling step, with the ability to flash Amazon stock ROMs, one can mess things up totally, and still recover back.
Exciting times, man !!!!
bibikalka said:
I just saw your boot unlocker thread, you should better manage your cross-references Congrats for getting us this far!
But I wonder if one could just flash 4.5.4 first, and then unlock the bootloader, and install TWRP, then root. Which bootloader versions can be unlocked? All so far? So people who were force updated to 4.5.4 are not SOL ?
Of course, it's easier to just have TWRP flash Amazon updates, then root is always available. That would be an enabling step, with the ability to flash Amazon stock ROMs, one can mess things up totally, and still recover back.
Exciting times, man !!!!
Click to expand...
Click to collapse
Messing with things more and more I don't think that is a fully working bootloader unlock. For example, I can't boot an unsigned boot.img after flashing. But I can boot it if I flash to recovery partition then issue adb reboot recovery.
Or that may just be a MTK/Amazon/LK thing. Not too sure at this point. But it seems right now, custom kernels are out of the question.
jmz said:
Messing with things more and more I don't think that is a fully working bootloader unlock. For example, I can't boot an unsigned boot.img after flashing. But I can boot it if I flash to recovery partition then issue adb reboot recovery.
Or that may just be a MTK/Amazon/LK thing. Not too sure at this point. But it seems right now, custom kernels are out of the question.
Click to expand...
Click to collapse
I see what you mean ... Even a partial unlock is huge step forward in terms of customization options, and the biggest deal is that now it's not too scary to screw up! Btw, in Amazon update files there is recovery-from-boot.p, is that the image we need for recovery? Or should we make a proper one via dd?
In Amazon update they seem to update recovery, but I wonder who checks for signed boot.img ? Is this part of the chipset ?
(from /recovery/etc ):
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:5888256:6d9d1bbc4172c107db3228ed8d9f97111219c617; then
log -t recovery "Installing new recovery image"
applypatch -b /system/etc/recovery-resource.dat EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:5370112:c2c686ada1b194050a3c8f05e2102345df48e9ce EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery 6d9d1bbc4172c107db3228ed8d9f97111219c617 5888256 c2c686ada1b194050a3c8f05e2102345df48e9ce:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
bibikalka said:
I see what you mean ... Even a partial unlock is huge step forward in terms of customization options, and the biggest deal is that now it's not too scary to screw up! Btw, in Amazon update files there is recovery-from-boot.p, is that the image we need for recovery? Or should we make a proper one via dd?
In Amazon update they seem to update recovery, but I wonder who checks for signed boot.img ? Is this part of the chipset ?
(from /recovery/etc ):
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:5888256:6d9d1bbc4172c107db3228ed8d9f97111219c617; then
log -t recovery "Installing new recovery image"
applypatch -b /system/etc/recovery-resource.dat EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:5370112:c2c686ada1b194050a3c8f05e2102345df48e9ce EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery 6d9d1bbc4172c107db3228ed8d9f97111219c617 5888256 c2c686ada1b194050a3c8f05e2102345df48e9ce:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Click to expand...
Click to collapse
all devices have that in some form or another.
I would make a dd backup of the stock one before flashing.
jmz said:
just dump your current recovery.img.
dd if=/dev/block/mmcblk0p7 of=/sdcard/stockrecovery.img
Then as soon as you boot into recovery make a backup.
Click to expand...
Click to collapse
Is there an option in TWRP Manager to save stock recovery without any reboots? This sounds like an easy feature to add. Or is this part of "live backup" ?
bibikalka said:
Is there an option in TWRP Manager to save stock recovery without any reboots? This sounds like an easy feature to add. Or is this part of "live backup" ?
Click to expand...
Click to collapse
No there isn't.
Well, I guess I am out of the game for awhile. Just bricked my Fire.