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.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
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 website.
TWRP for Yu Yutopia
XDA:DevDB Information
[OFFICIAL][TWRP][sambar] TWRP for YU Yutopia, Tool/Utility for the Android General
Contributors
HostZero
Source Code: https://gihtub.com/TeamWin/android_device_yu_sambar/tree/cm-13.0
Version Information
Status: Testing
Created 2016-08-03
Last Updated 2016-08-04
Reserved
Flash Recovery Guide
Code:
[B]adb reboot bootloader
fastboot -i 0x2A96 oem unlock
fastboot -i 0x2A96 erase recovery
fastboot -i 0x2A96 flash recovery twrp-3.x-sambar.img
fastboot -i 0x2A96 reboot[/B]
Reserved
Related
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.
Phone look:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
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.
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)
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.
DOWNLOAD:
1) Download TWRP from here
2) Flash via CWM or TWRP recovery
3) Enjoy
BUGS:
- You tell me
If you have found a bug, please consider posting it here. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, If you see someone that's struggling, feel free to point it out to me.Thanks!
SOURCES:
https://github.com/CyanogenMod-ARMv6/android_kernel_samsung_bcm21553-common
https://github.com/CyanogenMod-ARMv6/android_device_samsung_totoro
https://github.com/CyanogenMod-ARMv6/android_device_samsung_bcm21553-common
TWRP-240x320-ldpi-theme 2.8.7.0
TWRP-240x320-ldpi-theme 3.0.2-0
THANKS:
Dees_Troy.
TWRP team.
@psyke83 and BroadcomCM team for device tree and kernel source.
CHANGE LOG:
TWRP 3.0.2-1 [2016-10-16]
-TWRP now less than 5MB you can flash over stock PIT.
-Some UI improvement.
-Updated to latest changes.
TWRP 3.0.2-0 [2016-04-05] Removed
-Updated to latest changes.
TWRP 3.0.1-0 [2016-04-04] Removed
-Updated to latest changes.
TWRP 3.0.0-0 [2016-02-16] Removed
-Updated to latest changes.
-New theme reworked for ldpi (240×320).
TWRP 2.8.7.0 [2015-06-23]
-Fixed backup.
TWRP 2.8.6.0 BETA04[2015-04-10]
-Fixed all ui overlays.
-MTP enabled.
-Some changes I forgot.
TWRP 2.8.6.0 BETA03[2015-04-08]
-New UI hard coded from scratch.
TWRP 2.8.6.0 BETA02[2015-04-03]
-Fix inverted color
TWRP 2.8.6.0 BETA01[2015-04-01]
-Initial release
TWRP 3.0.2-1 now less than 5MB you can flash over stock PIT. If you want flash old TWRP3 look below
COLOR="Red"]For TWRP 3.0.0-0 to 3.0.2-0 we need boot partition size more than 5 MB[/COLOR]
Increase boot partition to 9 MB
1) Download totoro_moded.pit from here
2) Open odin and choose PIT then tick Re-Partition
3) Click on Start.
4) Reboot to recovery and flash TWRP 3.0.x-0
To restore stock PIT
1) Flash any kernel/recovery less than 5 MB, (eg twrp 3.0.2-1)
2) Download totoro_0623.pit from here
3) Open odin and choose PIT then tick Re-Partition
4) Click on Start.
Thank to Mohamed.Anwar for his work on modified PIT see thread
For me
Thanks
Sent from my C2305 using Tapatalk
BETA02 is up
-Fix inverted color
finnaly twrp for our device
I think this is the most advanced project for this device now, i liked it. Better than CWM [emoji57]
New portrait ui instead of watch ui takes some hours of work (porting and resize)
Realocate many buttons and lines to fix overlays.
guess new build soon Edit: BETA03 is up
Hello,
How can I flash it if I don't have CWM or TWRP installed? Thanks.
fdelente said:
Hello,
How can I flash it if I don't have CWM or TWRP installed? Thanks.
Click to expand...
Click to collapse
This is only to be used with cm11 as it's built into the cm11 kernel
come back here once you are using cm11 as then you will have CWM as it's built into the kernel
Is this not works with cm7? If yes please give me link to twrp which I need pls
Sent from my GT-S5360 using Tapatalk 2
doctor-who said:
Is this not works with cm7? If yes please give me link to twrp which I need pls
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
this is for cm11 only.
maybe in future will compile one for cm7
1% battery bug
Islam2001 said:
1% battery bug
Click to expand...
Click to collapse
Device tree uses fake bettery status (I dont know why)
BTW BETA04 is up and battery status is OK
-Fixed all ui overlays.
-MTP now enabled (not tested)
-Some changes I fogot
mohammad.afaneh said:
Device tree uses fake bettery status (I dont know why)
BTW BETA04 is up and battery status is OK
-Fixed all ui overlays.
-MTP now enabled (not tested)
-Some changes I fogot
Click to expand...
Click to collapse
Please , can you make it with OC?
Workaround method to get backup wroking
- Download and extract the attatchment file "twrps.zip" you will got ".twrps" without quotes.
- Copy .twrps to /TWRP folder on sdcard replace or remove the old one.
- Dont restore default in twrp settings menu (you will repeat steps again)
TWRP 2.8.7.0 touch recovery is up test and enjoy.
TWRP 3.0.0-0 coming soon
just some ldpi fixes to the UI and I will upload new build.
PS: screen shot say its 2.8.7.0 dont worry I tested the theme on the pre 3.0.0-0 version commit.
mohammad.afaneh said:
TWRP 3.0.0-0 coming soon
just some ldpi fixes to the UI and I will upload new build.
PS: screen shot say its 2.8.7.0 dont worry I tested the theme on the pre 3.0.0-0 version commit.
Click to expand...
Click to collapse
Wooohooooo greaat bro, go on, eagerly waiting btw , I just accessed a twrp recovery which is totally material themed , on cm12.1 , is it possible to port? (expecting too much xD )
raisul2010.5396 said:
Wooohooooo greaat bro, go on, eagerly waiting btw , I just accessed a twrp recovery which is totally material themed , on cm12.1 , is it possible to port? (expecting too much xD )
Click to expand...
Click to collapse
Why to port if we can compile it from source. And there is no ldpi theme at all, I redone every thing from zero.
And we dont have cm12.1!
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.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.
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 consistency (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.
CHANGELOG for 2.8.2.0:
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
NOTE: ONLY AOSP/GPE decryption is supported!! TWRP CANNOT (currently) decrypt HTC Sense ROMs!!
DOWNLOAD:
You can find more information and download links on our website!
Also, see attachments below for latest recovery image and device tree.
BUGS:
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log to SD, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed.
If your issue is determined to be 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 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.
Version Information
Status: Stable
K2CL OS: 4.2.2
Current Stable Version: 2.8.7.0
Stable Release Date: 2015-07-05
Current Beta Version: 2.8.7.0-K2CLB
Beta Release Date: 2015-07-17
Beta Patch Link: [WIP] gui: stock theme rework
Created: 2015-07-05
Last Updated: 2015-07-17
Source: Omnirom 5.1.1
Thanks for your work
Are there a stable version 2.8.7.0 twrp for k2u?
degerli43 said:
Thanks for your work
Are there a stable version 2.8.7.0 twrp for k2u?
Click to expand...
Click to collapse
If you are on 4.2.2 then send me your stock recovery and I can make it happen.
How to install it, pls?
itskapil said:
How to install it, pls?
Click to expand...
Click to collapse
If you are rooted and S-Off or using a custom kernel with write protection removed then download and install terminal emulator from the play store.
Download and unzip recovery image on internal sdcard. Rename it to twrprecovery.img for simplicity sake.
Open up terminal then enter the following:
Code:
su
Code:
dd if=/sdcard/twrprecovery.img of=/dev/block/mmcblk0p21
Otherwise, boot up to bootloader by powering off then pressing and holding the volume down key and power key.
When you see your HBoot select fastboot then plug your device to your computer.
Using fastboot type and enter:
Code:
fastboot flash recovery twrprecovery.img
SHM said:
Otherwise, boot up to bootloader by powering off then pressing and holding the volume down key and power key.
When you see your HBoot select fastboot then plug your device to your computer.
Using fastboot type and enter:
Code:
fastboot flash recovery twrprecovery.img
Click to expand...
Click to collapse
Thanks!
That's what I thought.
Was confused by the other file, device_htc_k2cl_twrp.zip, what's the use of this one?
itskapil said:
Thanks!
That's what I thought.
Was confused by the other file, device_htc_k2cl_twrp.zip, what's the use of this one?
Click to expand...
Click to collapse
Lol, no worries. The other attachment is the Device Tree used in conjunction with the Omnirom Open Source to build TWRP for the k2cl variant. If you do not know how to build TWRP or are unfamiliar with Open Sources then it won't pertain to you and you can just delete it. It's mainly there for any other Developers who wish to have it.
Currently using Omnirom 5.1.1 to make my builds.
@SHM Got it. Thanks a lot for help!
@degerli43, click here for k2u/ul TWRP Recovery.
OP updated with a Beta TWRP build using a reworked stock theme by @z31s1g. Version is 2.8.7.0-K2CLB. Below images will give you an idea of what it looks like. I am currently using this build for myself as I personally enjoy the new look and feel.
Device Tree has been reuploaded after being updated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my C525c using Tapatalk
In the past TWRP for this device never included the option to backup your /efs. Typically this is where your imei and other such info is stored. By backing this up using my builds and should you lose such information some how down the road, you can simply restore /efs within twrp and all should be well again with your device.
Sent from my C525c using Tapatalk
Removed by me - wrong thread
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.
Phone look:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
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.
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)
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.
DOWNLOAD:
1) Download TWRP from here
2) Flash via CWM or TWRP recovery
3) Enjoy
BUGS:
- SELinux contexts not supported in kernel
- Reboot to Recovery/Bootloader and Power Off
If you have found a bug, please consider posting it here. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, If you see someone that's struggling, feel free to point it out to me.Thanks!
SOURCES:
Kernel based on GT-S5360-opensource-Update-4
TWRP-240x320-ldpi-theme 3.0.2-0
THANKS:
Dees_Troy.
TWRP team.
CHANGE LOG:
TWRP 3.0.3-0 [2017-02-04]
-Initial release
Works good
Found the bugs you listed
Rebooted to system but stucked on bootlogo
Yes it is bootloop
Can you bring me a stockrecovery.zip?
I am not so familiar with this device and i dont want to reflash and delete whole data
Thanks in advance
basem_ym said:
Works good
Found the bugs you listed
Rebooted to system but srucked on bootlogo
Yes it is bootloop
Can you bring me a stockrecovery.zip?
I am not so familiar with this device and i dont want to reflash and delete whole data
Thanks in advance
Click to expand...
Click to collapse
Flash any custom stock kernel, you can find them dev thread.
mohammad.afaneh said:
Flash any custom stock kernel, you can find them dev thread.
Click to expand...
Click to collapse
still working on cm9 project?
erriezzans said:
still working on cm9 project?
Click to expand...
Click to collapse
I think its a waste of time.
Maybe when I got a lot of free time.
I think I did something wrong
I installed your TWRP by stock recovery
I forgot about flashing temp cwm
I reflashed stock and reinstalled this recovery in the right way
Very good work thank you :good:
Just a small tip for who stucked in bootlogo:
Just grap a. Pit file and reflash stock firmware with [re-partition] checked in odin and then install this recovery by cwm
I found that installing this twrp by stock recovery will mess the data partition causing it to not mount in any way for some reason
Wish to see all the bugs fixed :victory:
twrp is nice
your twrp for the ldpi look nice, I love using twrp to install custom rom.
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.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.2.1-0 is out now for Coolpad Note 3 Lite, Grab it right now.
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Changelogs for older versions
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
TWRP 3.1.1-0 Released
TWRP 3.1.1-0 is out now for all currently supported devices.
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
OLDER VERSION CHANGELOGS:
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
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.
DOWNLOAD:
Grab the latest build!
TWRP FOLDER
Note : Use 3.1.0 to flash Roms with old mount points ( mostly ported) and use 3.1.1 to flash Roms like MadOs, RR etc (Compiled ones)
New Improvements:
! Faster and Smoother than before
! Build from source
! supports Android 7.1.1
! MTP enabled
! Usb OTG supported(Fixed Now)
Credits:
-TWRP Team
@Dees_Troy
@kuberrocks96
-TeamZero
-mohancm
BUGS:
Not yet found
If you liked My developments Hit the LIKE/THANKS button :good:
Is it flashable for users using AOSP 7.1 ROM??
KritikXDA said:
Is it flashable for users using AOSP 7.1 ROM??
Click to expand...
Click to collapse
Yes it would work on all 3.18.xx kernel based roms
Its gone
I flashed TWRP in my phone yesterday using SP flash tool. It worked fine but today when rebooted again it booted into my stock recovery. What to do?
ojas.sinha said:
I flashed TWRP in my phone yesterday using SP flash tool. It worked fine but today when rebooted again it booted into my stock recovery. What to do?
Click to expand...
Click to collapse
Some faced this issue with old TWRP also , flash it via Flashify or TWRP itself again.
kuberrocks96 said:
Some faced this issue with old TWRP also , flash it via Flashify or TWRP itself again.
Click to expand...
Click to collapse
Now I don't have TWRP nor my phone is rooted.
Finally, a TWRP v3.1 for 3.18.19 kernel.
I ported this for my own device yesterday. Working good.
Thanks.
Great!
fr3akyphantom said:
Finally, a TWRP v3.1 for 3.18.19 kernel.
I ported this for my own device yesterday. Working good.
Thanks.
Click to expand...
Click to collapse
Good to hear that! Which Device you have?
Ported for my Primo RX5
kuberrocks96 said:
Good to hear that! Which Device you have?
Click to expand...
Click to collapse
I have ported this recovery to my device "Walton Primo RX5", not well-known, I know.
It is rebranded from "Gionee F103 Pro".
Thanks for the release. :good:
fr3akyphantom said:
I have ported this recovery to my device "Walton Primo RX5", not well-known, I know.
It is rebranded from "Gionee F103 Pro".
Thanks for the release. :good:
Click to expand...
Click to collapse
No worries.
Updated to 3.1.1
Decryption support (?)
kuberrocks96 said:
Updated to 3.1.1
Click to expand...
Click to collapse
Does it have Decryption support for previously encrypted Data partition (like v3.1.0 have)?
fr3akyphantom said:
Does it have Decryption support for previously encrypted Data partition (like v3.1.0 have)?
Click to expand...
Click to collapse
Yes it does have that, i am using different Mount Points here so that for our newer roms can be flashed easily with it, ported roms or older roms still require 3.1.0
support 8298-A01?
BlueNight1982BN said:
support 8298-A01?
Click to expand...
Click to collapse
No
MOD ACTION
THREAD CLOSED AT THE REQUEST OF OP.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About F2FS Support:
What is the F2FS Support?
File system can connect faster performance. It's a compression system.
How do I migrate my device to the F2FS file system?
1- Partially pour in place.
2- Enter the Advanced Wipe section.
3. Mark the Data and Cache section.
4- Repair or Replace the File System. Marking F2FS
And shape it ..
İnstall İnstructions:
1- Enable allow oem unlock from developer options in settings.
2- Power off your phone.
3-*Press the power key while holding down the volume down key.
4- You should see a menu.
5- Connect your phone to PC , open cmd, and write*fastboot oem unlock-go .
6- Your phone will open.
7-*Power off your phone again and press the power key while holding down the volume down key.
8- You'll see a menu again.
9- Extract your downloaded archive.
10- You should see recovery.img.
11-*In the folder where recovery.img file is located, right-click while holding down the shift key.
12- Write*fastboot flash recovery recovery.img*to cmd screen.
13- Select recovery with volume keys and press power button.
14- Your flashed twrp will open.[/align]
My Changes
* Add EFS Support.
* Add OTG_usb support
* Update TWRP 3.1.0.1
TWRP Changes
CHANGELOG for 3.1.1.0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
CHANGELOG for 3.1.0.0
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention.
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
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.
Bugs:
* Not that a bugs Really stable
Download's Lİnk
GM 5+ [OFFICIAL] TWRP 3.1.0.0.zip [15.6*MB]
Special Thanks:
@bigbiff for official bring up
@ataberkozen for tests
XDA:DevDB Information
[OFFICIAL] [F2FS / EXT4] TWRP 3.1.0.1 for GM 5 Plus, ROM for the General Mobile GM 5 Plus
Contributors
kaankulahli
Source Code: https://github.com/TeamWin/android_device_google_shamrock/tree/cm-14.1
ROM OS Version: 7.x Nougat
Version Information
Status: Stable
Created 2017-06-02
Last Updated 2017-06-02
I thought I need to format system in f2fs, but I see in first post that data need to format to f2fs.?
ludilo said:
I thought I need to format system in f2fs, but I see in first post that data need to format to f2fs.?
Click to expand...
Click to collapse
correct.
Gm8 de işe yararmı