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.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.
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.
has anyone had the chance to try this out ?
twrp decrypt password?
what is decrypt password?
please help..
Hogyoku said:
has anyone had the chance to try this out ?
Click to expand...
Click to collapse
Yes, and it works well.
beaver21c said:
what is decrypt password?
please help..
Click to expand...
Click to collapse
It's because of the dm-verity protection included in the MIUI firmwares.
To disable it, you have to:
- Format all encrypted partitions on fastboot (fastboot format system; fastboot format userdata;...)
- Boot on TWRP and flash a MIUI recovery image
- Download this patched boot file
- On fastboot flash the patched boot.img (fastboot flash boot boot-patched.img)
To manually remove the protection from a kernel you have to:
- Extract boot.img from a rom/device
- Unpack it, with this tool for example -> mkbootimg_tools
- Search the fstab file (fstab.qcom for example) and remove the "verify" mention and replace all "forceencrypt" mentions by "encryptable"
- Repack it and flash it
Abdess76 said:
Yes, and it works well.
It's because of the dm-verity protection included in the MIUI firmwares.
To disable it, you have to:
- Format all encrypted partitions on fastboot (fastboot format system; fastboot format userdata;...)
- Boot on TWRP and flash a MIUI recovery image
- Download this patched boot file
- On fastboot flash the patched boot.img (fastboot flash boot boot-patched.img)
To manually remove the protection from a kernel you have to:
- Extract boot.img from a rom/device
- Unpack it, with this tool for example -> mkbootimg_tools
- Search the fstab file (fstab.qcom for example) and remove the "verify" mention and replace all "forceencrypt" mentions by "encryptable"
- Repack it and flash it
Click to expand...
Click to collapse
Wouldt the latest super su do this already since it repacks the original boot img and patches the dm-verity ?
Thanks for the recovery and boot.img btw !
Hogyoku said:
Wouldt the latest super su do this already since it repacks the original boot img and patches the dm-verity ?
Thanks for the recovery and boot.img btw !
Click to expand...
Click to collapse
Yes, SuperSu do this already and it works well!
You're welcome.
Just a question though, given that Mi Max has identical hardware to Redmi Note 3 pro, is it possible to use custom roms of the latter ? Or does it require some porting ?
landono5 said:
Just a question though, given that Mi Max has identical hardware to Redmi Note 3 pro, is it possible to use custom roms of the latter ? Or does it require some porting ?
Click to expand...
Click to collapse
The Mi Max has some similarities with the Redmi Note 3 Pro but it's, unfortunately, not identical. Kenzo roms can't work directly on Mi Max.
how to unlock the bootloader on mi max ?
sam razzy said:
how to unlock the bootloader on mi max ?
Click to expand...
Click to collapse
Like all Xiaomi phones, here: http://en.miui.com/unlock/
How-to: http://en.miui.com/thread-202290-1-1.html (No need to flash a developer rom before)
My Mi Max is already waiting for me to get home this weekend... Already got unlock permission from Xiaomi so I am all set for playing with my new toy. I will be unlocking bootloader, flash TWRP and root it.
So few questions... I don't have to worry about all encrypted fs? SuperSu will take care of them? Do I have to fastboot format userdata first? Is the internal /sdcard partition encrypted?
Not very familiar with all this fs encryption thing.
Let's hope we get some good custom ROM for this device soon... AOSP, CM, whatever...
nijel8 said:
My Mi Max is already waiting for me to get home this weekend... Already got unlock permission from Xiaomi so I am all set for playing with my new toy. I will be unlocking bootloader, flash TWRP and root it.
So few questions... I don't have to worry about all encrypted fs? SuperSu will take care of them? Do I have to fastboot format userdata first? Is the internal /sdcard partition encrypted?
Not very familiar with all this fs encryption thing.
Let's hope we get some good custom ROM for this device soon... AOSP, CM, whatever...
Click to expand...
Click to collapse
Congratulation, this is a very comfortable phone a good size to play big games like GTA.
If a FS is encrypted you'll have to format it, you'll surely need to use fastboot to format userdata, internal sdcard isn't encrypted by default.
Custom roms are on the road.
Done... Unlocked bootloader, rooted, decripted, xposed, Google apps... But still cannot consider it as my primary phone yet. Not till global ROM at least is installed. All this China related stuff is annoying.
BTW I noticed pointer (like a pc mouse) in the center of the screen... Any way to remove it?
Also only back hardware button works, home and menu doesn't.
nijel8 said:
All this China related stuff is annoying.
Click to expand...
Click to collapse
CM13 for Max is out in the Chinese MIUI forum.
hyibin said:
CM13 for Max is out in the Chinese MIUI forum.
Click to expand...
Click to collapse
Found it but can't download it from baidu, I guess I need account?! Chinese is like... aahh... Chinese to me... If you can could you please mirror it somewhere for us? Much appreciate it!
Here we go.
https://drive.google.com/file/d/0BwLamA2L7HU7OWxGYjdjcEJWTDA/view?usp=sharing
hyibin said:
Here we go.
https://drive.google.com/file/d/0BwLamA2L7HU7OWxGYjdjcEJWTDA/view?usp=sharing
Click to expand...
Click to collapse
You are the man... :good: Thank you!
So far it's working... Just one problem - if WiFi is set to DHCP phone can't obtain IP address... If set to Static no problems.
It works well in version 7.3.16?
Abdess76 said:
Like all Xiaomi phones, here: http://en.miui.com/unlock/
How-to: http://en.miui.com/thread-202290-1-1.html (No need to flash a developer rom before)
Click to expand...
Click to collapse
i hit thank you
After installing twrp using fastboot, my phone cant boot in the os.. just stuck at mi.com logo without android below it.. can someone help me? I already unlock the bootloader.
---------- Post added at 05:44 PM ---------- Previous post was at 05:38 PM ----------
Abdess76 said:
Yes, and it works well.
It's because of the dm-verity protection included in the MIUI firmwares.
To disable it, you have to:
- Format all encrypted partitions on fastboot (fastboot format system; fastboot format userdata;...)
- Boot on TWRP and flash a MIUI recovery image
- Download this patched boot file
- On fastboot flash the patched boot.img (fastboot flash boot boot-patched.img)
To manually remove the protection from a kernel you have to:
- Extract boot.img from a rom/device
- Unpack it, with this tool for example -> mkbootimg_tools
- Search the fstab file (fstab.qcom for example) and remove the "verify" mention and replace all "forceencrypt" mentions by "encryptable"
- Repack it and flash it
Click to expand...
Click to collapse
Where can I get MIUI Recovery Image?
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.
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
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.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.
Xiaomi Redmi Note 3
TWRP Downloads
NOTE: If you are flashing TWRP for the first time then you need to first flash modified boot.img from here and then TWRP
XDA:DevDB Information
Recovery for the Xiaomi Redmi Note 3
Contributors
vibhu0009
Source Code: https://github.com/TeamWin
Device Tree: https://github.com/TeamWin/android_device_xiaomi_kenzo
Version Information
Status: Stable
Created 2016-04-06
Last Updated 2016-04-06
Special thanks to @Santhosh M
Could you add chinese language please? Thank you
Can we get TWRP Manager app from Google Play store to reference this TWRP version (kenzo)? Will make it easier to flash and apply updates in future.
Does it need to flash cracked boot.img with this official version?
vlado05 said:
Does it need to flash cracked boot.img with this official version?
Click to expand...
Click to collapse
yes.. if u flashing it for the first time then u gotta flash the modified boot.img and then TWRP
_ossie_ said:
Can we get TWRP Manager app from Google Play store to reference this TWRP version (kenzo)? Will make it easier to flash and apply updates in future.
Click to expand...
Click to collapse
It will be up very soon in TWRP manager
vlado05 said:
Does it need to flash cracked boot.img with this official version?
Click to expand...
Click to collapse
Yes, you still need the modded boot.img for respective version of the rom.
---------- Post added at 01:08 PM ---------- Previous post was at 01:06 PM ----------
_ossie_ said:
Can we get TWRP Manager app from Google Play store to reference this TWRP version (kenzo)? Will make it easier to flash and apply updates in future.
Click to expand...
Click to collapse
Definitely it would be easier, with a unlocked BL though.
Thanks
feds64 said:
Yes, you still need the modded boot.img for respective version of the rom.
Click to expand...
Click to collapse
Sorry for the noob Qs and a bit off-topic but can you flash the modded boot.img with TWRP itself? The only way I have been flashing a modded boot.img is via Fastboot.
(I imagine you'd need to convert the boot.img to a flashable zip but I don't know how to do that.
Also, isn't the modded boot.img the very LAST thing to flash? Because every time I have done it differently I have ended up in bootloop/stuck at Mi logo.
The other way I've been restoring boot is via a TWRP backup (boot only) but this requires it to be previously flashed and backed up.
_ossie_ said:
Sorry for the noob Qs and a bit off-topic but can you flash the modded boot.img with TWRP itself? The only way I have been flashing a modded boot.img is via Fastboot.
(I imagine you'd need to convert the boot.img to a flashable zip but I don't know how to do that.
Also, isn't the modded boot.img the very LAST thing to flash? Because every time I have done it differently I have ended up in bootloop/stuck at Mi logo.
The other way I've been restoring boot is via a TWRP backup (boot only) but this requires it to be previously flashed and backed up.
Click to expand...
Click to collapse
In twrp select option of flash images, and then it will show the image file, select and flash it.
Hey,
I just tried this Recovery & as of now it is not able to flash MIUI zip files! Earlier Chinese recoveries were able to flash full zips at least! [OTA cant be flashed though]
Edit- Threre is some weird error as - Failed to mount '/factory' (Invalid argument)
TheDj408 said:
Hey,
I just tried this Recovery & as of now it is not able to flash MIUI zip files! Earlier Chinese recoveries were able to flash full zips at least! [OTA cant be flashed though]
Edit- Threre is some weird error as - Failed to mount '/factory' (Invalid argument)
Click to expand...
Click to collapse
Doesn't effect anything.. But new build is coming soon with this error fixed..
vibhu0009 said:
Doesn't effect anything.. But new build is coming soon with this error fixed..
Click to expand...
Click to collapse
thanks @vibhu0009 for all your hard work
really appreciate it
oficial twrp fr my rn3
omg
thnkz @vibhu0009
gona try it right awy
I Think you remove
/factory ext4 /dev/block/bootdevice/by-name/factory
_ossie_ said:
Sorry for the noob Qs and a bit off-topic but can you flash the modded boot.img with TWRP itself? The only way I have been flashing a modded boot.img is via Fastboot.
(I imagine you'd need to convert the boot.img to a flashable zip but I don't know how to do that.
Also, isn't the modded boot.img the very LAST thing to flash? Because every time I have done it differently I have ended up in bootloop/stuck at Mi logo.
The other way I've been restoring boot is via a TWRP backup (boot only) but this requires it to be previously flashed and backed up.
Click to expand...
Click to collapse
Alternatively you can, always keep these two files together in you device as you may need it for OTA or etc.
---------- Post added at 03:21 PM ---------- Previous post was at 03:19 PM ----------
Thanks for the quick fix...
When is the new build with /factory mount error fix?
DrWillz said:
When is the new build with /factory mount error fix?
Click to expand...
Click to collapse
i gues u did not see the change of name of thread
it was fixd and released 3-4 hours bak by @vibhu0009
take links from frst page
---------- Post added at 05:15 PM ---------- Previous post was at 05:14 PM ----------
feds64 said:
Alternatively you can, always keep these two files together in you device as you may need it for OTA or etc.
---------- Post added at 03:21 PM ---------- Previous post was at 03:19 PM ----------
Thanks for the quick fix...
Click to expand...
Click to collapse
+1
thanks for the quick fix...
First of all thank you very much for your hard work on twrp. It's really amazing. I suppose that release 3.0.2-1 is not yet finished! I cannot see any link for this version, just 3.0.2-0.
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.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:
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.
TWRP is fully open source, port / compile TWRP for your device today!.
Build in CM-13.0 environment w/TWRP source forked : @mdmower
Fork of TWRP
This fork differs from the original in the following ways:
Designed to be built with CyanogenMod 13.0 only
Require fstab v2 syntax (see examples and supported flags below)
Use external repositories for pigz, exfat, fuse
Power key toggles screen on/off
Remove the need to specify either DEVICE_RESOLUTION or TW_THEME so long as TARGET_SCREEN_HEIGHT and TARGET_SCREEN_WIDTH are set
Other minor customizations (see change history)
Versioning
To help distinguish builds of recovery made from this fork, the minor version digit is replaced with M#. Minor version increments will be handled as needed, independent of TWRP. The major and semi-major version digits follow upstream to roughly indicate feature parity (as close as possible with a fork, anyways).
Convention:
3.0.M0-0 incorporates all major features from TWRP 3.0.0-0
3.0.M1-0 is the minor version increment after 3.0.M0-0 and is independent of any TWRP minor version increment(s)
3.1.M0-0 is the semi-major version increment after 3.0.M4-2 and is tied to a TWRP semi-major version increment
3.0.M0-1 is a device-specific fix to 3.0.M0-0; this device digit resets when any other version increments
maintained rework by : @artefvck
DOWNLOADS:
Fastboot Mode
Flashable Zip
source
Convert ext4 partition to F2FS partition without loosing data
Preface
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel.
The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Prerequisites
PC with ADB installed for SD backups
F2FS compatible ROM
F2FS compatible Kernel
F2FS compatible TWRP Recovery (this recovery has F2FS support, too)
sdcard Fix Permissions script (scroll down a little bit)
Procedure
Flash the F2FS compatible TWRP Recovery with fastboot or other recovery for example
Boot into Recovery
Backup > Data
Save your internal SD card with one of the following options
Either reboot to system and copy files to your PC via USB (MTP)
Or pull files via adb (adb pull /data/media sd_backup)
Copy the kernel and the sdcard fix script to your created backup folder
Wipe > Advanced Wipe > Data > Repair or Change File System > Change File System > F2FS
Wipe > Advanced Wipe > Cache > Repair or Change File System > Change File System > F2FS
Copy the saved SD card content back to your device with: adb push sd_backup /data/media/0/
Afterwards the folder structure should look like this: /data/media/0/…Folders like DCIM, Music, Downloads, …
You can check with: adb shell ls -R /data/media
Restore > Choose backup > Data (the warning about ext4 backup doesn’t matter)
Advanced > Fix Permissions
Flash the sdcard Fix Permissions script with: Install > Choose sdcard fix zip
Wipe > Advanced Wipe > Cache & Dalvik Cache
Flash a F2FS compatible kernel with: Install > Choose kernel zip
Reboot to system
Now your Android device should fly again ��
Note:
In my mind it doesn’t make much sense to format/system to F2FS because you would need a modified ROM to use it. Everytime you update your ROM you would have to modify it to use /system as F2FS. On top of that there shouldn’t be a real performance gain with a F2FS /system partition because it’s read-only. And reading operations are fast with ext4, too. The difference is non-existent or very low. In my humble opinion the so called All-F2FS is pretty useless.
You can format your /data and /cache partition to F2FS. Normally you’ll loose all data in this process and have to reinstall everything. But this small howto will show you how to recover your data so you can continue where you left off. Just like a “dirty” ROM flash.
Good.
oh gee nice that you make update for TWRP 3.0 but is it fixes nandroid backup ?
Because I had this error that make me regret it it's called ( extractTarFork() process ended with ERROR: 255 ) and it's from your TWRP 3.0 M-1 ( if i'm not mistaken ) it's a nandroid backup of stock rom when I want to try the custom ROM
and Keep Up The Good Work yes ?
Regards
Awesome0ne ?
Sent from my ASUS_T00F using Tapatalk
RevanEphys said:
oh gee nice that you make update for TWRP 3.0 but is it fixes nandroid backup ?
Because I had this error that make me regret it it's called ( extractTarFork() process ended with ERROR: 255 ) and it's from your TWRP 3.0 M-1 ( if i'm not mistaken ) it's a nandroid backup of stock rom when I want to try the custom ROM
and Keep Up The Good Work yes ?
Regards
Click to expand...
Click to collapse
latest build fixed
try twrp 3.0.M-2.0
X AnwarMov said:
latest build fixed
try twrp 3.0.M-2.0
Click to expand...
Click to collapse
You Mean TWRP 3.0.2 ? I will try that later when all CM 13 or Android 6.0 ROM quite stable enough ( even though it will still has bugs )
Thanks
RevanEphys said:
You Mean TWRP 3.0.2 ? I will try that later when all CM 13 or Android 6.0 ROM quite stable enough ( even though it will still has bugs )
Thanks
Click to expand...
Click to collapse
please report to your Rom development .
this thread i think can't have problem
Hi,
Instalation is for flash or fastboot?
Good joob
marceloz5 said:
Hi,
Instalation is for flash or fastboot?
Good joob
Click to expand...
Click to collapse
oh yeah fastboot for now ,
latest build i can upload flashable.zip for more easly
thanks
i only get white screen after flashing wonder y
Nice ?
Sent from my ASUS_T00F using XDA-Developers mobile app
X AnwarMov said:
Build in CM-13.0 environment w/TWRP source forked : @mdmower
Fork of TWRP
This fork differs from the original in the following ways:
Designed to be built with CyanogenMod 13.0 only
Require fstab v2 syntax (see examples and supported flags below)
Use external repositories for pigz, exfat, fuse
Power key toggles screen on/off
Remove the need to specify either DEVICE_RESOLUTION or TW_THEME so long as TARGET_SCREEN_HEIGHT and TARGET_SCREEN_WIDTH are set
Other minor customizations (see change history)
Versioning
To help distinguish builds of recovery made from this fork, the minor version digit is replaced with M#. Minor version increments will be handled as needed, independent of TWRP. The major and semi-major version digits follow upstream to roughly indicate feature parity (as close as possible with a fork, anyways).
Convention:
3.0.M0-0 incorporates all major features from TWRP 3.0.0-0
3.0.M1-0 is the minor version increment after 3.0.M0-0 and is independent of any TWRP minor version increment(s)
3.1.M0-0 is the semi-major version increment after 3.0.M4-2 and is tied to a TWRP semi-major version increment
3.0.M0-1 is a device-specific fix to 3.0.M0-0; this device digit resets when any other version increments
maintained rework by : [MENTION=4258433]artefvck
- add new touchscreen synaptics driver / update
- built-in modules
- F2FS partitions
- kernel version v3.10.20
DOWNLOADS:
FOLDER UPLOAD
source :
Device tree
Kernel
Click to expand...
Click to collapse
Thanks for this...no lags whatsoever except when booting to twrp and when booting to system... keep up the good work
can install on cm 12.1?
emirfahimi said:
can install on cm 12.1?
Click to expand...
Click to collapse
Yeah.
tank0412 said:
Yeah.
Click to expand...
Click to collapse
but here you said cm 13 "only"
I've tried both 3.0.M-1.0 and 3.0M-2.0.
They are quite lag on my Zenfone 5 when compare with 2.8.7.0
For example, it takes 10-20 seconds to go into recovery and several second before it reboot.
When i tried backup rom twrp suddenly restart and back to first screen twrp again, i tried twice but the problem still persist
abw_bw said:
When i tried backup rom twrp suddenly restart and back to first screen twrp again, i tried twice but the problem still persist
Click to expand...
Click to collapse
When I try to backup System, Data, Config, and System Image, my phone turns off when the backup nearly completed. and ends up with Usb Logo. :silly:
baszu said:
I've tried both 3.0.M-1.0 and 3.0M-2.0.
They are quite lag on my Zenfone 5 when compare with 2.8.7.0
For example, it takes 10-20 seconds to go into recovery and several second before it reboot.
Click to expand...
Click to collapse
i faced this to.
Sent from my ASUS_T00F using XDA-Developers mobile app
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.2-2:
-Fix subpartition restore bug (ex: EFS)
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:
TWRP 3.0.2-2
Can be updated quickly and easily within TWRP if TWRP is already installed
1) Download the latest version from the above link
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
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.
SOURCE/THANKS:
Device tree: https://github.com/TeamRegular/android_device_zte_ailsa_ii
@DrakenFX for testing and requesting my help
@Unjustified Dev for being....ME of course
Prerequisites:
* Unlocked bootloader Guide Here
Installation:
Code:
adb reboot bootloader
fastboot flash recovery twrp-3.0.2-2-a2017u.img
fastboot reboot
To enter recovery:
* Power + volume up
Code:
adb reboot recovery
Installing Mods:
If you plan on modifying the system, please follow this post here or you'll result in a bootloop.
Reserved
Holy **** that is quick. You are a hero.
I picked up the chinese model though, still waiting for bootloader... They confirmed it but they are taking their time.
Hoping the devices are similar enough that this twrp will also work on mine.
aPexalpha said:
Holy **** that is quick. You are a hero.
I picked up the chinese model though, still waiting for bootloader... They confirmed it but they are taking their time.
Hoping the devices are similar enough that this twrp will also work on mine.
Click to expand...
Click to collapse
The base HW should be the same across the world. The only real difference is the Force Touch feature in the Chinese 6GB model, which might necessitate a different touch screen driver.
The Chinese ROM also calls the device the ailsa_ii, just with a different model number.
that's awsome, very nice work. Now the custom ROMs have open doors
In BoardConfig.mk, wouldn't we want "BOARD_HAS_NO_REAL_SDCARD := false" (just leave it out) and "TW_NO_USB_STORAGE := false" (or leave it out)? I'm pretty sure it has OTG support and it definitely has a real SD card.
Thanks for getting the repo up and running as well.
Very good news! Suprised how fast it all went down, cheers! On a side note, is there any chance this or any other method will ever work for EU models? I really like the phone, but waiting for the manufacturer to do something about the software is kind of hopeless.
MeggaMortY said:
Very good news! Suprised how fast it all went down, cheers! On a side note, is there any chance this or any other method will ever work for EU models? I really like the phone, but waiting for the manufacturer to do something about the software is kind of hopeless.
Click to expand...
Click to collapse
It all depends on ZTE Europe releasing a bootloader unlock for the European (Global) version of the phone.
Thank you! Sharing the device tree helps a ton with additional development. Let's see what we can build with this.
TeutonJon78 said:
In BoardConfig.mk, wouldn't we want "BOARD_HAS_NO_REAL_SDCARD := false" (just leave it out) and "TW_NO_USB_STORAGE := false" (or leave it out)? I'm pretty sure it has OTG support and it definitely has a real SD card.
Thanks for getting the repo up and running as well.
Click to expand...
Click to collapse
1st config as I remember is for internal storage. Something about not allowing you to partition it.
2nd config is to remove mass storage support. TWRP supports mtp.
Sent from my 6045I using Tapatalk
Thank you! One question, which I suppose isn't just limited to TWRP: Though we have TWRP (again, awesome!), we don't have a stock image or a way to get back to "locked, unrooted" status yet or the default ROM, right?
ScaryBugThing said:
Thank you! One question, which I suppose isn't just limited to TWRP: Though we have TWRP (again, awesome!), we don't have a stock image or a way to get back to "locked, unrooted" status yet or the default ROM, right?
Click to expand...
Click to collapse
Unfortunately I do not know. ZTE blocked the command fastboot boot so we couldn't backup the stock recovery.img we had no choice but to flash it. You can however backup system image in recovery and restore it later. This is the first thing that should be done before flashing root as well as a normal backup. If you restore your system image you can always OTA update through TWRP since it will be an untouched image. I do doubt that you can return to official OEM locked status unless they say it won't void warranty if you unlock it.
Sent from my 6045I using Tapatalk
ScaryBugThing said:
Thank you! One question, which I suppose isn't just limited to TWRP: Though we have TWRP (again, awesome!), we don't have a stock image or a way to get back to "locked, unrooted" status yet or the default ROM, right?
Click to expand...
Click to collapse
Nope, as far as I know. ZTE has to release the stock factory images. It's extremely difficult to create from a mere backup because it requires ZTE's signature verification.
Sent from my XT1095 using Tapatalk
---------- Post added at 12:16 PM ---------- Previous post was at 12:13 PM ----------
I'm really happy for the TWRP. Thank you man.
Sent from my XT1095 using Tapatalk
When I flash SuperSU 2.76 the phone just turns off, which is kind of strange. Has anyone else had any luck?
Got the same thing when I flash SuperSU
goalkeepr said:
When I flash SuperSU 2.76 the phone just turns off, which is kind of strange. Has anyone else had any luck?
Click to expand...
Click to collapse
allan1229 said:
Got the same thing when I flash SuperSU
Click to expand...
Click to collapse
After you try to install super su and the phone turns off boot back into recovery and
adb pull /cache/recovery/last_log
first time doing this. let me know if its right
http://www.mediafire.com/download/s988ykn9wws5a63/last_log
Unjustified Dev said:
1st config as I remember is for internal storage. Something about not allowing you to partition it.
2nd config is to remove mass storage support. TWRP supports mtp.
Sent from my 6045I using Tapatalk
Click to expand...
Click to collapse
Ah, that would make sense. I couldn't tell from the TWRP documentation if either one was general. The SD one is about partition, I just didn't know if applied to an external card (not that most people partition one since Windows doesn't allow it anyway). You definitely wouldn't want people partitioning their internal one.
It makes sense to get rid of UMS, as then TWRP couldn't read it while you're connected to the computer. It's unfortunate they names it USB rather than UMS then. Thanks.
Unjustified Dev said:
Prerequisites:
* Unlocked bootloader Guide Here
Installation:
Code:
fastboot flash recovery twrp-3.0.2-0-a2017u.img
fastboot reboot
To enter recovery:
* Power + volume up
Code:
adb reboot recovery
Click to expand...
Click to collapse
I'm confused I connect my phone and go into command prompt and do the first command fastboot flash recovery twrp-3.0.2-0-a2017u.img enter and all I get is waiting on device am I doing something wrong?
Team Win Recovery Project
This is a unified build for both the Redmi Note 3 (kenzo) and the Redmi Note 3 SE (kate)
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
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: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (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!
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
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.
FEATURES:
MTP support
USB OTG storage support
Hardware Qualcomm-based full-disk encryption support ( ext4 & f2fs )
f2fs file system support (read, write, format, backup & restore)
Covers more partitions for nandroid backup (fstab)
ADB root
Full SELinux support
Built with android 7.1 tree
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
CONTRIBUTIONS:
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
TWRP for Redmi Note 3, Tool/Utility for the Xiaomi Redmi Note 3
Contributors
TheStrix
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created 2017-03-04
Last Updated 2017-03-21
FAQ:
WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Personally, I'd have tried this after 15 minutes.
WHY DOES F2FS MAKE TWRP SO SLOW?
When TWRP boots up or wipes partitions and a few other scenarios, it checks each partition to see how much disk space is used. Ext4 handles disk usage calls quite efficiently and will finish this very fast. F2FS on the other hand is very slow when it comes to checking disk usage. We're unsure why this is. Every file on the F2FS formatted partition adds a little more time, and a device that is 30 GB full could take up to 10 minutes to boot TWRP!
HOW DO I GET LOGS SO WHEN I COMPLAIN I'M NOT COMPLETELY IGNORED OR SHAMED BY OTHER USERS?
To get logs while in TWRP, you should connect your device to your PC and use adb.
adb pull /tmp/recovery.log
adb exec-out dmesg > dmesg.log
This will create 2 files in the directory your shell is currently in, recovery.log and dmesg.log. You will need to upload these somewhere such as a pastebin or Google Drive. You can also attach it to your XDA post (recommended!)
If you are having an operating system boot issue, you should gather a ramoops log instead. Do this while in TWRP after the failed boot:
adb exec-out "tar c /sys/fs/pstore 2>/dev/null" > pstore.tar
Is this TWRP able to flash official ROM and incremental OTA also without any workaround, like TWRP zcx does?
i did a few benchmark on f2fs, but didnt notice a major difference on kenzo, is it really the case? or is F2Fs really worth it
fardeenah said:
i did a few benchmark on f2fs, but didnt notice a major difference on kenzo, is it really the case? or is F2Fs really worth it
Click to expand...
Click to collapse
With latest lineage os and Radeon kernel I get 89500 with Antutu. Changing to f2fs gets me 91500. 1 would say a 2000 Antutu increase is pretty impressive.
Antutu don't test disk-speed! So your 2000 extra points have another reason, maybe media-indexing at phone-start etc...ext4 is best filesystem for your phones because it is fast in ALL cases and rock solid!
D4xel said:
Is this TWRP able to flash official ROM and incremental OTA also without any workaround, like TWRP zcx does?
Click to expand...
Click to collapse
I'd like to know this as well, as i'm expecting a Kate device soon.
Thanks! It also prompt you to install the twrp app. Working well for now (Only flashed and wiped stuff)
Hey guys I converted data & cache from ext4 to f2fs (backup data>wipe dalvik+format cache f2fs+format data f2fs>restore data backup with rm-rf) and internal storage was wiped in the process. I don't remember wiping internal storage and can anyone help me check whether I was careless or it is a bug.
With the latest version, I'm not able to install kenzo custom roms to my kate phone.
Getting following error, tried different roms:
"This package is for device: kenzo; this device is kate.
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/Nitrogen-OS-kenzo-20170304.zip'
when i did clean wipe & give reboot to recovery phone start on system not going to recovery.
I have to press vol+ & power for 10 sec to go to recovery.
Please fix it.
Note: Its only happen while clean wipe.
So using f2fs is better than ext4?
gaurav1902 said:
So using f2fs is better than ext4?
Click to expand...
Click to collapse
Lot's of devs say no. I can't feel the difference overall but opening Settings>Apps in f2fs is a whole lot faster than in ext4 for me.
Btw ext4 is compatible with more stuff as you might face issues flashing zips to f2fs partition (which I haven't faced yet).
jianwen03 said:
Lot's of devs say no. I can't feel the difference overall but opening Settings>Apps in f2fs is a whole lot faster than in ext4 for me.
Click to expand...
Click to collapse
Same
Awesome thanks for sharing
Draygon said:
With the latest version, I'm not able to install kenzo custom roms to my kate phone.
Getting following error, tried different roms:
"This package is for device: kenzo; this device is kate.
'
Click to expand...
Click to collapse
The error probably arose due to this being a unified TWRP for Kenzo and Kate . Apparently, this TWRP is able to differentiate between Kenzo and Kate devices, and has assigned a specific flag to each identification. Thus , Kenzo is ID'd as a Kenzo , and Kate is ID'd as a Kate.
This is actually very bad news for Kate users. If you look around Note 3's ROM scene, every single custom ROM is named as a Kenzo release and is keyed for Kenzo. The only reason kate users were able to install these Roms was because they were using Kenzo TWRPs. Despite being Kate, the TWRP fooled the ROM into thinking it is Kenzo and then allowed the installation.
In every ROM and in some other zip installs, there's a file called updater.script. This file, actually the first lines of the file, is where the ROM performs its only device check.
So how does a Kate user bypass this ERROR 7? Well, there are many ways:
1. Change the two mentions of "Kenzo" on the first lines of the ROM 's updater.script to "Kate", then flash like before,
2. Or, urge the op to make a Kenzo-only TWRP, and flash.that,
3. Or beg the op to modify the TWRP to forgo this updater.sfript check.
Personally, I'd just stay away from Kate or Kenzo/Kate unified TWRPs. Changing update.script on every ROM you want to flash can become very tedious.
It's a lot easier being a fake Kenzo, then a real Kate.
gaurav1902 said:
So using f2fs is better than ext4?
Click to expand...
Click to collapse
I am using f2fs for 2 days now and it is definitely snappier when it comes to multitasking. On ext4, the recents button was a bit slow for me, pressing and showing up the recents sometimes took a good half second, was unsure if I even pressed it but then oh look it appeared. No such issue for f2fs, everything is happening as I'm pressing buttons.
Draygon said:
With the latest version, I'm not able to install kenzo custom roms to my kate phone.
Getting following error, tried different roms:
"This package is for device: kenzo; this device is kate.
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/Nitrogen-OS-kenzo-20170304.zip'
Click to expand...
Click to collapse
Did you install Kate's TWRP or Kenzo's one?
@TheStrix
System won't boot after changing from M4 recovery to this one..
but this time, I'm even unable to revert back to M4 -> system not booting, just mi logo > reboot
m4 recovery also wouldn't boot
so now I'm completely stuck (given my limited capabilities).
btw: I actually wasn't able to change to another recovery since I changed to f2fs on M4 (tried zcx, dad1, ... )
logs are here: https://drive.google.com/open?id=0B9NuN8yWvpeZQzFDVGF4UTREWnc
edit: found out that it might be a problem with latest AGNI kernel: I unbricked and reinstalled (CM13), and my problem seems to be reproducable with latest releases - radon works however..
schmanto said:
@TheStrix
System won't boot after changing from M4 recovery to this one..
but this time, I'm even unable to revert back to M4 -> system not booting, just mi logo > reboot
m4 recovery also wouldn't boot
so now I'm completely stuck (given my limited capabilities).
btw: I actually wasn't able to change to another recovery since I changed to f2fs on M4 (tried zcx, dad1, ... )
logs are here: https://drive.google.com/open?id=0B9NuN8yWvpeZQzFDVGF4UTREWnc
Click to expand...
Click to collapse
If you are able to boot into recovery, format partitions as ext4 and flash recovery of your choice.