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.
Reserved.
Dees_Troy said:
This has been available for a little while, but now I'm adding an official thread for it here on XDA.
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.3.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
Would it work with V28C ?
Thx.
Sent from my LG-P970 using xda premium
florin250 said:
Would it work with V28C ?
Thx.
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
i dont think so......
but....we better wait answer from the expert
@OP
wow.....i just dream about this last night and today you give this.....thank you so much....
the latest is 2.3.1.1
http://techerrata.com/file/twrp2/p970/openrecovery-twrp-2.3.1.1-p970.img
Ilko said:
the latest is 2.3.1.1
http://techerrata.com/file/twrp2/p970/openrecovery-twrp-2.3.1.1-p970.img
Click to expand...
Click to collapse
download stuck at 99,99%, why???
edit : downloading without download manager, now it's okay
In ClockworkMod, on Nandroid Backup...(there is no option to save the name as we wish), it defaultly gives a name with date for backup..
So, here in TWRP, is there possibility for giving name for Nandroid Backup ?
And what are the bugs remaining after 2.3.1.0 update ?
Had anyone brick phone or bootloop history with this ?
sekhar13515 said:
In ClockworkMod, on Nandroid Backup...(there is no option to save the name as we wish), it defaultly gives a name with date for backup..
So, here in TWRP, is there possibility for giving name for Nandroid Backup ?
And what are the bugs remaining after 2.3.1.0 update ?
Had anyone brick phone or bootloop history with this ?
Click to expand...
Click to collapse
The old TWRP recoveries never completely worked for OB.Sometimes it was the SD mounting, sometimes you couldn't restore the backup done with the same TWRP version and so on.I will try this because I like TWRP more than CWM but it's the last time if it won't work.
---------- Post added at 10:37 AM ---------- Previous post was at 10:36 AM ----------
Ilko said:
the latest is 2.3.1.1
http://techerrata.com/file/twrp2/p970/openrecovery-twrp-2.3.1.1-p970.img
Click to expand...
Click to collapse
No, it's not but it's 2.3.20(not yet for OB of course).
USB storage not mounting.
Back to the "bomb proof" cwm 5.8.1.3 touch.
great share!Very good job, thank you.
there is a new version 2.3.1.1
timvdhoorn said:
there is a new version 2.3.1.1
Click to expand...
Click to collapse
ilko already said it here http://forum.xda-developers.com/showpost.php?p=34469364&postcount=6 and there is a newer version but it haven't been built to our device yet.
Updated!
Dees_Troy said:
Updated!
Click to expand...
Click to collapse
SDcard mounting as mass storage still not working, please check.
I was writing the same report : )
well, too bad. I like it but it's useless to me since I transfer files very often through recovery. I can't compile a flasher with that
Indeed I prefer twrp rather than cwm.
Dees, what you need to solve the SD card?
Enviado desde mi LG-P970 usando Tapatalk
Every new version always the same problem.
re4lsk said:
Indeed I prefer twrp rather than cwm.
Dees, what you need to solve the SD card?
Enviado desde mi LG-P970 usando Tapatalk
Click to expand...
Click to collapse
I need to know the proper path for the lun file. By default it's in /sys/devices/platform/usb_mass_storage/lun0/file
You'll have to look for it in TWRP, not in Android though if you find it in Android then I can try switching kernels... I'd need a copy of your current kernel or boot image to switch.
A lot of newer devices don't support USB storage mode anymore at all, so bear that in mind when you're getting ready to upgrade to a new device. You'll have to get used to using ADB to push files or use ADB sideload mode.
Dees_Troy said:
I need to know the proper path for the lun file. By default it's in /sys/devices/platform/usb_mass_storage/lun0/file
You'll have to look for it in TWRP, not in Android though if you find it in Android then I can try switching kernels... I'd need a copy of your current kernel or boot image to switch.
A lot of newer devices don't support USB storage mode anymore at all, so bear that in mind when you're getting ready to upgrade to a new device. You'll have to get used to using ADB to push files or use ADB sideload mode.
Click to expand...
Click to collapse
well the black is an old device(2011) so usb storage still works, you need zImage or boot.img to get the kernel? i can point you to the CM kernel source, i'll see if my old linux VM still works to get you the zImage. but in the mean time i'll upload you the boot.img from cm10 from 20-12-2012 nightly.
CM kernel source
re4lsk said:
well the black is an old device(2011) so usb storage still works, you need zImage or boot.img to get the kernel? i can point you to the CM kernel source, i'll see if my old linux VM still works to get you the zImage. but in the mean time i'll upload you the boot.img from cm10 from 20-12-2012 nightly.
CM kernel source
Click to expand...
Click to collapse
It's not that I need a kernel as much as I need the proper path to the lun file for whatever kernel I happen to be using. Since I don't have an Optimus Black I can't boot it up and look for it myself.
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.
Great to have a second choice! I'm still using RomRacer though.
A great clockwork alternative!
Flashed it and it looks great! Haven't tested it out fully but i wish I could use the internal partition because my sdcard is pretty full and the battery percentage would show. Unless i find a reason to switch back to cwm, Ill keep this.
Any plans on adding support for CM7 based roms? Only /sdcard is being recognized, /emmc isn't available at all.
*Edit* Also wanted to include webtop (/osh) in the above question.
I also flashed it, but didn't spend much time in it (got work to do ).
Can the backup restore location be changed to point to backups that were made with other recoveries?
Download link is dead for me
rozzco said:
I also flashed it, but didn't spend much time in it (got work to do ).
Can the backup restore location be changed to point to backups that were made with other recoveries?
Click to expand...
Click to collapse
I don't think other recovery backups will be compatible. The test backup I did yesterday looks like this:
boot.emmc.win
data.ext4.win
system.ext4.win
And none of my CWM backups were showing up when navigating through my sdcard contents.
no more power button + volume down? wow. i need to slow down now
thanks for this.
anyone wana make a zip of this? im sure you will get 3x more users downloading ur recovery than before.
slojko said:
anyone wana make a zip of this? im sure you will get 3x more users downloading ur recovery than before.
Click to expand...
Click to collapse
I did yesterday. See this post from my thread in General.
ive actually been running this for a few days now and found it really awesome!
backup and restores are lightning fast and everyhting ive tried works perfectly
i found that in cm7 based ROMs only the external gets mounted. which is fine because thats what I use
Great work Team Win
Wow, this looks awesome. I just downloaded it and will load it up on my phone in a few minutes. Thanks for the awesome work TeamWin!
Great work, but i'm getting a few issues:
Everytime i try to install something,at the end of process it gives me:
E: cannot load volume /misc.
Also when i mount usb and unmount, later on i try to install something and recovery restarts itself showing homescreen, fixed by going back to usb mount screen and unchecking "unmount cache" although it's weird to see this checked, when actually i didn't check anything( i see only "unmount sd-card" checked when i leave the panel).
Hope this can be addressed soon,cause it's a very nice recovery UI
ATT Atrix 4G
Darkside 4.2
Kernel Faux 0.23 1.45Ghz @stock
Teamwin Recovery 2.0
its possible to use this on locked atrix ?
and..we have any recovery to use with an locked atrix ? i need to wipe my battery and dont know how without a custom recovery....
many tks
There are no recovery for a locked atrix(real ones at least)
Search the market for battery calibration
sent from my Atrix via XDA premium
flaviocc said:
its possible to use this on locked atrix ?
and..we have any recovery to use with an locked atrix ? i need to wipe my battery and dont know how without a custom recovery....
many tks
Click to expand...
Click to collapse
Just unlock it. Its definatley worth it. Then you can get cwm or this and wipe whatever and flash whatever.
And I have to say the recovery is very nice. Kinda weird not using volume buttons but very nice. I am also getting the can't load volume thing error.
Sent from my MB860 with ICS using xda premium
ghost_og said:
I did yesterday. See this post from my thread in General.
Click to expand...
Click to collapse
This works for me One question: can i install .zip file from internal memory,cant find internal sdcard anywhere?
dulexetina said:
This works for me One question: can i install .zip file from internal memory,cant find internal sdcard anywhere?
Click to expand...
Click to collapse
I'm guessing you're on a CM7 based ROM? Currently it only supports motoblur naming (sdcard, sd-ext). They plan on adding support for /emmc at some point. Keep a backup .zip of CWM on your sdcard just in case.
Can you guys take Rom Racer's recovery and just add the tweaks from this CWM to it? Pretty much make a touch version of Rom Racer's...
ghost_og said:
I'm guessing you're on a CM7 based ROM? Currently it only supports motoblur naming (sdcard, sd-ext). They plan on adding support for /emmc at some point. Keep a backup .zip of CWM on your sdcard just in case.
Click to expand...
Click to collapse
I am on blured rom,and even restore did not worked for me-tried many times (to restore full,just data,just system...but no succes) i am back on old recovery until this one gets fixed. This recovery is so simple to use and realy nice,just waiting for full working version now.
Sent from my MB860 using XDA App
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
[ THIS POST IS TEAMWIN'S STOCK TWRP POSTING. USE OF THE WORDS "US" AND "OURS" MEANS "DEES_TROY AND TEAMWIN" NOT HASHCODE ]
*** ALL CREDIT FOR TWRP BELONGS TO DEES_TROY AND TEAMWIN. ***
They do a BANG UP job on making a fantastic customizable touch-based recovery.
Donate to TeamWin:
http://www.teamw.in/project/twrp2
BEFORE YOU FLASH THIS, PLEASE MAKE SURE THAT YOU HAVE A 2ND-BOOTLOADER INSTALLED FROM HERE:
http://forum.xda-developers.com/showthread.php?t=2100963
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.
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.
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!
** THIS IS A FLASHABLE .ZIP FILE FOR INSTALLING IN YOUR CURRENT VERSION OF TWRP **
DOWNLOAD:
[ DO NOT DOWNLOAD ANY FILES FROM TEAMWIN'S WEBSITE. IN GENERAL, THEY ARE MEANT TO BE FLASHED TO UNLOCKED DEVICES AND WON'T WORK FOR THE KINDLE FIRE 2 ]
You can download from goo.im here and place on your SDCARD:
http://goo.im/devs/Hashcode/otter2/recovery-zip/zip-otter2-twrp-2.6.3.1-recovery.zip
md5sum: b9eb941b1673396c91f73ccda010daf1
INSTALL INSTRUCTIONS:
During the BLUE logo screen press the power button to cycle through options and select "Recovery" to enter TWRP.
Select "Install"
Navigate to where you placed the file on your device
Select the .zip filename
Swipe to confirm flash
Reboot
KNOWN ISSUES:
None at the moment.
BUGS:
First: I'd read through this thread and see if your issue isn't answered.
Second: Try googling for it
Third: If it seems like a Kindle Fire 2 issue, then post in the thread.
Lastly: If you have found a bug, please consider posting it to TeamWin's 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 #kindlefire-dev or #twrp on Freenode with your IRC client or just click this link.
can i just flash the new image from the old (previously available twrp) recovery?
755 said:
can i just flash the new image from the old (previously available twrp) recovery?
Click to expand...
Click to collapse
You flash it via fastboot
Sent from my Amazon Kindle Fire2 using xda app-developers app
The link is dead
Alin1997 said:
The link is dead
Click to expand...
Click to collapse
No, it isn't.
--
Sent from my mind to your screen.
Any chance this will get usb mounting fixed?
I can adb push, but usb mounting would make like much easier
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
any chance for flashable zip?
mindmajick said:
Any chance this will get usb mounting fixed?
I can adb push, but usb mounting would make like much easier
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I dont think TWRP supports USB sharing for /data/media emulated sdcard space.
Sent from my DROID4 using Tapatalk 2
Hashcode said:
I dont think TWRP supports USB sharing for /data/media emulated sdcard space.
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Is it possible to port a cwm recovery?
Sent from my A2109A using Tapatalk HD
While I'm waiting on my fastboot cable, I've been trying to get to fastboot mode on my own. No luck, of course, no matter what I try. I guess I don't need twrp-2.4 yet since 2.3 does the job, but not having the latest is bothersome.
Sent from my Amazon Kindle Fire2 using xda premium
TWRP 2.5.0.0 for KF2?
Thanks for this. Wondered if TWRP 2.5.0.0 was on the way for the KF2. Any news?
Squuiid said:
Thanks for this. Wondered if TWRP 2.5.0.0 was on the way for the KF2. Any news?
Click to expand...
Click to collapse
Contact @Hashcode. He can make a newer version.
Gesendet von meinem LG-P990 mit Tapatalk 2
TWRP 2.6.0.0 is being tested.
Once approved, I'll add it to the instructions
Sent from my XT926 using Tapatalk 2
OP Updated with TWRP 2.6.0.0 download and instructions.
NOTE: USB Vendor ID / Product ID's have been reset to match Amazon stock OS for better compatibility
Enjoy
and remember if you like this product you can donate to TWRP at the top of this page:
http://www.teamw.in/project/twrp2
(Maybe mention [KFire2] in the donation so that they know what device you have)
WARNING: IF YOU INSTALLED THIS BEFORE TONIGHT(7/8) THEN I WOULD ADVISE RE-INSTALLING. I MADE SOME LAST MINUTE FIXES.
Hashcode said:
OP Updated with TWRP 2.6.0.0 download and instructions.
NOTE: USB Vendor ID / Product ID's have been reset to match Amazon stock OS for better compatibility
Enjoy
and remember if you like this product you can donate to TWRP at the top of this page:
http://www.teamw.in/project/twrp2
(Maybe mention [KFire2] in the donation so that they know what device you have)
WARNING: IF YOU INSTALLED THIS BEFORE TONIGHT(7/8) THEN I WOULD ADVISE RE-INSTALLING. I MADE SOME LAST MINUTE FIXES.
Click to expand...
Click to collapse
Flashed and looking good.
The WIPE screen has changed. Can I get a general consensus that choosing Advanced Wipe, and then choosing "Internal Storage" will still end in a bricked device, before anyone does it?
Thanks for your work on this Hashcode.
EDIT:
I normally create a backup and then copy it to my PC (Ubuntu 13.04), but I can't copy:
system.ext4.win
data.ext4.win
It gives me an error saying it can't copy them. I've tried a couple of times without joy.
Is there anything you want me to try?
chronicfathead said:
Flashed and looking good.
The WIPE screen has changed. Can I get a general consensus that choosing Advanced Wipe, and then choosing "Internal Storage" will still end in a bricked device, before anyone does it?
Thanks for your work on this Hashcode.
EDIT:
I normally create a backup and then copy it to my PC (Ubuntu 13.04), but I can't copy:
system.ext4.win
data.ext4.win
It gives me an error saying it can't copy them. I've tried a couple of times without joy.
Is there anything you want me to try?
Click to expand...
Click to collapse
Could be leaving those files open for some reason. Can you reboot back into recovery and try copying them again?
Also, the "Internal Storage" option under "Advanced Wipe" is for formatting /data + /sdcard. This should *NOT* result in a brick, but I haven't tested it personally.
Instructions have been changed slightly:
Swapped out the .img file for a flashable .zip file for use by those who already have TWRP installed.
Just download, toss on the SD card and flash in TWRP like anything else.
People who do not have TWRP installed should be using the 2nd-bootloader thread anyway.
Hashcode said:
Could be leaving those files open for some reason. Can you reboot back into recovery and try copying them again?
Also, the "Internal Storage" option under "Advanced Wipe" is for formatting /data + /sdcard. This should *NOT* result in a brick, but I haven't tested it personally.
Click to expand...
Click to collapse
I have rebooted into recovery and mounted USB storage, but it doesn't mount on my Ubuntu PC. The message I get is:
Unable to open MTP device '[usb:002,019]'
If I flick into the terminal in TWRP I see the following message:
E: Unable to locate volume information for USB storage mode.
Off to work. If you want me to try anything, just let me know.
chronicfathead said:
I have rebooted into recovery and mounted USB storage, but it doesn't mount on my Ubuntu PC. The message I get is:
Unable to open MTP device '[usb:002,019]'
If I flick into the terminal in TWRP I see the following message:
E: Unable to locate volume information for USB storage mode.
Off to work. If you want me to try anything, just let me know.
Click to expand...
Click to collapse
Sorry, you are correct. USB mounting inside recovery is not supported for any /data/media sharing type device. This includes the Galaxy Nexus and Nexus 4. :/
Best way to push/pull files from the device is via the Windows Command Line using adb.
To push files to the device:
adb push <filename> <destination>
example: adb push cm-10.1-otter2.zip /sdcard/Download
or to pull files from the device while in recovery:
adb pull /sdcard/Download/cm-10.1-otter2.zip
(This would pull the file from the device to whatever directory you are currently in)
or
adb sideload
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.
Reserved
Note that the Z2, like most other Sony devices does not have a proper bootable recovery. As such you have to install a kernel that includes a recovery with it. For a time I will try to continue to supply updated stock kernels repacked with TWRP in them. If you are running one of my kernels or have a custom ROM like OmniROM installed, you can install TWRP in the FOTAKernel partition to stay on the latest version of TWRP.
Device page on our website
Mirror 1
Mirror 2
To install a stock kernel, boot the device into fastboot mode and then from your computer: fastboot flash boot path/to/filename.img
R/W on Root not possible
Hi,
After i flashed this version of the Kernel for .402 FW i got no permissions to write on the root / partition or subfolders (system,..)
Is it possible that this is restricted in the offical version as in Doomlords Unofficial TWRP Version its working fine.
Another User experienced the same:
http://forum.xda-developers.com/showthread.php?p=53330667
Thank you in advance
beloero said:
Hi,
After i flashed this version of the Kernel for .402 FW i got no permissions to write on the root / partition or subfolders (system,..)
Is it possible that this is restricted in the offical version as in Doomlords Unofficial TWRP Version its working fine.
Another User experienced the same:
http://forum.xda-developers.com/showthread.php?p=53330667
Thank you in advance
Click to expand...
Click to collapse
it might be the Sony RIC function, which ensures system partition untouchable.
you can disable it by changing /sys/kernel/security/sony_ric/enable to 0 everytime you boot your device.
Umm how do I flash this via fastboot?
I used the fastboot flash boot twrp.img command and it worked. I could boot into recovery but I cannot boot into Android OS now. Even if I don't press the Volume Up button, the device goes into recovery mode.
eRajesh said:
Umm how do I flash this via fastboot?
I used the fastboot flash boot twrp.img command and it worked. I could boot into recovery but I cannot boot into Android OS now. Even if I don't press the Volume Up button, the device goes into recovery mode.
Click to expand...
Click to collapse
What exactly did you flash ?
You should flash this file --> stock-17.1.1.A.0.402-sirius-repack.img -- with the 'fastboot flash boot ..... ' command.
Flashing ----> openrecovery-twrp-2.7.1.0-sirius.img --- with 'fastboot flash boot .....', wont work,
because the proper way of flashing a recovery is with 'fastboot flash recovery .....'
But according to post 2, you can't 'just' flash a recovery on to the Z2, you need a boot image with a recovery inside, which is the repack i believe.
So flashing the repack with the 'fastboot flash boot stock-17.1.1.A.0.402-sirius-repack.img' should get you back into the OS.
Is there a way of flashing TWRP with a boot image of our choice?
heatl0rd said:
Is there a way of flashing TWRP with a boot image of our choice?
Click to expand...
Click to collapse
Kinda, if the kernel developer add support for having recovery in FOTAKernel partition you can put the recovery.img in there and it'll be used, Cyanogenmod for example does this. Doomlord is reluctant to use it in his kernel for some reason.
Sent from my Nexus 7 using Tapatalk
Ok so just so im clear. This can be installed by flashing "stock-17.1.1.A.0.402-sirius-repack.img" via fastboot.
But can this be installed by simply flashing via an existing recovery?
heatl0rd said:
Ok so just so im clear. This can be installed by flashing "stock-17.1.1.A.0.402-sirius-repack.img" via fastboot.
But can this be installed by simply flashing via an existing recovery?
Click to expand...
Click to collapse
Yes and yes - if someone makes a flashable zip
Dees_Troy said:
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.
Phone look:
Tablet look:
CHANGELOG for 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
DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
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.
Click to expand...
Click to collapse
thank you, looks great but 1 question
will this work with sgp512 (z2 16gb wifi tablet)?
@Dees_Troy
Just installed and version is showing 2.7.0.0. Can i reconfirm the OP links are indeed 2.7.1.0?
I aint really sure what is happening but it seems to, when I fastboot flash stock kernel with this TWRP I can not delete services with Titanium backup...They always get back after a reboot?
I have never experienced this before
Dirtyzecret said:
I aint really sure what is happening but it seems to, when I fastboot flash stock kernel with this TWRP I can not delete services with Titanium backup...They always get back after a reboot?
I have never experienced this before
Click to expand...
Click to collapse
See posts #3 and #4
Basically no automatic write access to system without some tinkering.
arrrgh said:
See posts #3 and #4
Basically no automatic write access to system without some tinkering.
Click to expand...
Click to collapse
Sorry guys, for not reading trough thread.
Downloading recovery 0/100....
Anyone?
Why theres no windows flashing version?
SkyS1gn said:
Downloading recovery 0/100....
Anyone?
Why theres no windows flashing version?
Click to expand...
Click to collapse
Same here. Even after app was updated.
Sent from my D6503 using XDA Premium 4 mobile app
Bad problem with the new cm nightly 20140709 and the twrp manager.
Recovery could not load!
can i have the twrp recovery as a zip file pls?
A flashable zip would be nice! Cause the twrp manager does not work any more on cm.
Or have somebody an introduction for making flashable zips.
Regards Peterle