Develop Bugs

[Recovery] TWRP 3.0.3-0 for L5 (E610/E612/E617)

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CHANGELOG for 3.0.3-0:
-Add TWRP app install via TWRP recovery
- Update Ukraine language translation (via jemmini)
- Support to android-7.1
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:
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 down below
2) Reboot to your current recovery or flash the recovery.img with dd on your recovery partition
3) Flash the provided archive
TWRP L5

good work!

cool,thanx.
--SIGNATURE--

Does not work for me. Can't update via TWRP (gives error while executing binary), when flashing via Rashr it flashes succesfuly, but can't boot this recovery.

kamil79123 said:
Does not work for me. Can't update via TWRP (gives error while executing binary), when flashing via Rashr it flashes succesfuly, but can't boot this recovery.
Click to expand...
Click to collapse
Works very well for me

Jonas Cardoso said:
Works very well for me
Click to expand...
Click to collapse
Here's a log from TWRP 2.8.7.0:
Installing New Recovery
assert failed: package_extract_file("recovery.img", "/tmp/recovery.img")
E:Error executing updater binary in zip '/external_sd/twrp-3.0.0.1-e610-JonasCardoso.zip'
Error flashing zip '/external_sd/twrp-3.0.0.1-e610-JonasCardoso.zip'
Updating partition details. . .
. . . done
So, what's wrong?

kamil79123 said:
Here's a log from TWRP 2.8.7.0:
Installing New Recovery
assert failed: package_extract_file("recovery.img", "/tmp/recovery.img")
E:Error executing updater binary in zip '/external_sd/twrp-3.0.0.1-e610-JonasCardoso.zip'
Error flashing zip '/external_sd/twrp-3.0.0.1-e610-JonasCardoso.zip'
Updating partition details. . .
. . . done
So, what's wrong?
Click to expand...
Click to collapse
It is not extracting the recovery file, see if the zip is not corrupted, and the TWRP is enabled the writing mode

Jonas Cardoso said:
It is not extracting the recovery file, see if the zip is not corrupted, and the TWRP is enabled the writing mode
Click to expand...
Click to collapse
Re-Downloaded and now works, so it was my bad, sorry.
Nice work, but DPI seems a little too small, but great thanks!

kamil79123 said:
Re-Downloaded and now works, so it was my bad, sorry.
Nice work, but DPI seems a little too small, but great thanks!
Click to expand...
Click to collapse
It is not problem in dpi is the resolution of l5 is low even

Jonas Cardoso said:
It is not problem in dpi is the resolution of l5 is low even
Click to expand...
Click to collapse
DPI determines resolution. Is there a way to change resolution to proper value?

kamil79123 said:
DPI determines resolution. Is there a way to change resolution to proper value?
Click to expand...
Click to collapse
I do not know

Added OC version https://www.androidfilehost.com/?fid=24457741883933541

Jonas Cardoso said:
Added OC version https://www.androidfilehost.com/?fid=24457741883933541
Click to expand...
Click to collapse
What is exactly OC version?

kamil79123 said:
What is exactly OC version?
Click to expand...
Click to collapse
Overclock version

Jonas Cardoso said:
Overclock version
Click to expand...
Click to collapse
Overclock version of TWRP? I know OC version of kernel, but TWRP? What does can we overclock in TWRP?

kamil79123 said:
Overclock version of TWRP? I know OC version of kernel, but TWRP? What does can we overclock in TWRP?
Click to expand...
Click to collapse
The kernel comes with the standard overclocking the CPU, all recovery has a kernel that only this modified

Very good work bro

Can flash cm12.1 stable?

adrian1234a said:
Can flash cm12.1 stable?
Click to expand...
Click to collapse
There is no stable cm12.1

Jonas Cardoso said:
There is no stable cm12.1
Click to expand...
Click to collapse
the last build of aidasaidas75 no?

[RECOVERY][Robin] TWRP 3.0.2-0 touch recovery

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CHANGELOG for 3.0.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.

Install instructions and the latest download links:
https://twrp.me/devices/nextbitrobin.html
Troubleshooting:
If you never set a encryption password (It asks you during the startup wizard), then you just click enter and skip it.

And it starts. So excited

I'm surprised they could get it ported so quickly!

Question
Is it possible root Software Concept 6.0 for Xperia Z3 with this recovery?
Thank you

Lousyguyy said:
I'm surprised they could get it ported so quickly!
Click to expand...
Click to collapse
Nexbit is very developer-friendly. They reached out to developers a while ago to get TWRP working as well as CM. Right now, it's mostly just a matter of waiting until developers get their Robins before ROMs get posted.

PherChe said:
Question
Is it possible root Software Concept 6.0 for Xperia Z3 with this recovery?
Thank you
Click to expand...
Click to collapse
This is for the Nextbit Robin not the Xperia Z3

Question.... does anybody care to share a nandroid backup? I may have made a mistake...

ilcapo09 said:
Question.... does anybody care to share a nandroid backup? I may have made a mistake...
Click to expand...
Click to collapse
Here is a rooted twrp backup:
http://forum.xda-developers.com/nex.../rom-rooted-twrp-backup-t3336828#post65843511

Thanks a lot deadman!

NICE
GOOD

Awesome! Works great. Next step --- custom ROM

TWRP 3.0.1-0 Released
Just a heads-up peeps:
TWRP has been updated to v3.0.1 !
Download: https://dl.twrp.me/ether/twrp-3.0.1-0-ether.img.html
What’s new in 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

Thread cleaned of off topic discussion.
Stay on topic please.

So with 3.0.1-0 being released, does this fix the decryption issue on phone? Also I can just fastboot flash recovery twrp.img and overwrite the old one, yes?
Edit: Doesn't seem like it, tried entering my password and still nada!
Also, 3.0.2-0 has been released as well!

Thank you for the update @deadman96385!

Every time I backup or restore I got this message
failed to unmount /system device or resource busy
Any idea? Suggestions?

Nextbit_Khang said:
Thank you for the update @deadman96385!
Click to expand...
Click to collapse
My screen unlock PIN - the one I have to enter after rebooting or flunking the fingerprint test - doesn't work to decrypt the data partition. I don't recall ever being prompted for a password at first boot.
Is the encryption secured with some default password? If we're all on one password that seems less secure than it could be.

(6 months later) has anyone gotten twrp to work with encryption? I am on cm13 and twrp cannot mount despite my entering the password. I've tried pin, pattern and password. Thanks.

F2FS missing?
Is it just me or is f2fs missing from twrp on this device?

[OFFICIAL][TWRP][taido] TWRP for Motorola Moto E (2016)

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOADS
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:
TWRP for Motorola Moto E 2016
Credits
@Dees_troy
@jcadduono
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.
XDA:DevDB Information
TWRP for Moto E3 Power, Tool/Utility for the Moto E3
Contributors
HostZero
Source Code: https://github.com/TeamWin/android_device_motorola_taido/tree/android-6.0
Version Information
Status: Beta
Created 2016-10-25
Last Updated 2016-11-19

Reserved

motorola is going release kernel code in few days for 6.0 Motorola Moto E3 Power
Status:
https://github.com/MotorolaMobilityLLC/motorola-kernel/issues/5

HostZero said:
Hey guys,
Here by I am planning for Official TWRP before that can i know is this twrp stable enough
https://www.androidfilehost.com/?fid=529152257862670134
Only for Moto E3 "Power"
Once you guys confirm everything is stable i will make it official
Source Code:
https://github.com/HostZero/android_device_motorola_taido/tree/android-6.0
XDA:DevDB Information
TWRP for Moto E3 Power, Tool/Utility for the Moto E3
Contributors
HostZero
Source Code: https://github.com/HostZero/android_device_motorola_taido/tree/android-6.0
Version Information
Status: Beta
Created 2016-10-25
Last Updated 2016-10-25
Click to expand...
Click to collapse
'/custom' error is appear every operation

onkar.35 said:
'/custom' error is appear every operation
Click to expand...
Click to collapse
Thankyou for information.
As per me. I have recently done a commit for fixing ext4 support and I am planning to remove /custom

HostZero said:
Thankyou for information.
As per me. I have recently done a commit for fixing ext4 support and I am planning to remove /custom
Click to expand...
Click to collapse
Ok buddy

OFFICIAL Builds are OUT @teamw.in

Thanks @HostZero

@HostZero kernel source is out.
https://github.com/MotorolaMobilityLLC/kernel-mtk/releases/tag/MMI-XT1706-S131-160905

Ya, kernel sources are out.. The kernel source they have released without commit history.. I have captured commits from tags.
If kernel source with commit history:
https://github.com/HostZero/android_kernel_motorola_taido

https://drive.google.com/file/d/0B176CbvuapswamJpSWdkT2dlUDg/view?usp=drivesdk

Is this for the Moto E3 (XT1700) or E3 Power (XT1706)?
Thanks

Can anyone confirm this actually works on a Moto E3 XT1700 (Not the E3 Power XT1706). I have tried to install this a dozen times using the fastboot method, but TWRP will not boot. I cannot even boot it using the "fastboot boot twrp.img" command, the devices just reboots into the stock OS.
@HostZero can you provide any advice?

Its for XT1706 and not XT1700 guys. Codename: Taido

I was under the impression that Taido was the code name for the xt1700, not the xt1706? My device says the baseband version is TAIDO.ROW.V18 2016/08/26 18:17.
Regardless of whether that's true or not, I can see from HostZero's github page that his version is for the E3 Power. That being the case, can the topic of this thread be changed to say Moto E3 Power, and not Moto E (2016), to remove the ambiguity? The current topic is confusing given this forum is for the E3 and not the E3 Power.
Also, HostZero how hard would it be to create an official build for the XT1700? I'm happy to be a test case if necessary.

Guys I found this article over the internet. Please see this http://www.android-nougat.host/2016/12/motorola-moto-e3-power-8337.html

Guys after root I have lost system tuner settings in menu. What could have happened.

XGr7078 said:
Guys I found this article over the internet. Please see this http://www.android-nougat.host/2016/12/motorola-moto-e3-power-8337.html
Click to expand...
Click to collapse
Guess it's not true !! If it would have been , it would have been moved in the section of xda n so on

Anyone compiling the kernel for nougat from source. I think it has been released.
Update: I visited the site but it said "closed"
And fyi after rooting and unlocked bootloader I have lost one feature. System tuner UI. Has anyone else faced this same issue or it's just me.

@HostZero - Any chance you could build a version of this for XT1700? I looked into it myself briefly but I don't know the first thing about building for android. The devices have the same chipset, I think perhaps just the partition sizes might need to be updated. I can supply any info on the device you need if you don't have one handy.
Thanks

[RECOVERY][UNOFFICIAL] TWRP 3.5.x for Redmi K30 5G [picasso]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
*Disclaimer
*
* Your warranty may be void.
*
* We're not responsible for bricked devices, dead OTGs or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Introduction:
Team Win Recovery Project 3.x , or twrp 3 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.
Features:
Wiping, backing up, restoring, and mounting various device partitions, such as the system, boot, userdata, cache, and internal storage partitions are also supported. TWRP also features file transfer via MTP, as well as a basic file manager, and a terminal emulator. It is fully themeable.
Click to expand...
Click to collapse
Bugs:
You tell me!
Check current issues at the GitHub Issues tracker before reporting one (it may already exist): https://github.com/Redmi-K30-5G/device_xiaomi_picasso_recovery/issues
Prerequisites:
1. Unlocked bootloader.
Instructions:
1. Download the TWRP image file to your PC.
2. Put your device into fastboot.
3. Type the following command to flash the recovery:-
Code:
Code:
fastboot flash recovery "name_of_recovery.img"
4. On installation of TWRP , to boot the recovery do:-
Code:
Code:
fastboot boot "name_of_recovery.img"
The device will automatically reboot into TWRP, and you will have TWRP as your permanent recovery!
5. Enjoy!
Contributors:
hadenix
Version Information:
TWRP version: 3.5.x
Device: picasso (all models should work)
Picasso TG general group: https://t.me/XiaomiRedmiK30
Maintainer/Authors build: @Hadenix
Downloads:
TWRP
Support:
Telegram Channel

Changelog
Code:
13-10-2021
Updated sources TWRP
Added support for encrypting firmware with OSS Vendor
Safetynet module update for MIUI
Added cleaning of Super partitions;
Added a backup and the ability to install images of the Super partition;
Fixed translations
20-06-2021
Fixed CPU temperature sensor
Synchronization with source code
Added support for MIUI firmware encryption on Android 11
Fastbootd is activated
And other minor edits and fixes
31-05-2021
Updated source codes to the current ones
Updated graphics
Removal of the LogCat log
a patch to prevent the replacement of twrp stock recovery (for of.MIUI)
install Magisk v23.0 and uninstall it
AVB protection removal patch (for OFIUI on 11 android).
script for full conversion of Super to RW partition (by brigudav)
script for mounting dynamic partitions in RW (by brigudav)
script for disabling forced encryption (by brigudav)
script for disabling partition logging (by brigudav)
installation of a module for Magisk to pass the SafetyNet test
16-02-2021
Fix adb sideload
Updated sources TWRP
Changing the interface of the top bar
31-01-2021
updated twrp sources
updated fstab
fix recent errors
removed some flags
made the sorting
17-12-2020
updated fstab
fix recent errors
now the date is being decoded by pin code
13-12-2020
removed unnecessary libs/files
removed some flags
made the sorting
fixed the status bar
updated twrp sources
updated fstab
26-10-2020
Fix Magisk Installation
Minor fixes that prevented the installation of MIUI firmware
25-10-2020
Update prebuilts to 12.0.7.0 stable
First release

@Hadenix
I'm using the EU rom, stable, i flashed your TWRP and now my K30 5G is stuck, wont boot into recovery or system, i followed your steps 1 by 1, and yes after flashing TWRP i booted to TWRP via Fastboot.
What to do ?
Thank you so much

Inpain said:
@Hadenix
I'm using the EU rom, stable, i flashed your TWRP and now my K30 5G is stuck, wont boot into recovery or system, i followed your steps 1 by 1, and yes after flashing TWRP i booted to TWRP via Fastboot.
What to do ?
Thank you so much
Click to expand...
Click to collapse
I did the installation from scratch and everything works for me

I am at eu rom but after flash magisk, it is bootloop, how to bypasss this issue. Thank

I am at eu rom but after flash magisk, it is bootloop, how to bypasss this issue. Thank

I am at eu rom but after flash magisk, it is bootloop, how to bypasss this issue. Thank

I am at eu rom but after flash magisk, it is bootloop, how to bypasss this issue. Thank

twrp-3.4.0_10-2-picasso-hadenix
17-12-2020:
updated fstab
fix recent errors
now the date is being decoded by pin code

vudungcom said:
I am at eu rom but after flash magisk, it is bootloop, how to bypasss this issue. Thank
Click to expand...
Click to collapse
try the latest version

vudungcom said:
I am at eu rom but after flash magisk, it is bootloop, how to bypasss this issue. Thank
Click to expand...
Click to collapse
if you put it clean, then you need to format the date, all data is deleted

Hadenix said:
if you put it clean, then you need to format the date, all data is deleted
Click to expand...
Click to collapse
Thank for suggestion but now i am using stable eu version n dont have time to do, when i want to change new rom, will use your TWRP

how can I decrypt twrp? i can't update my rom without decrypting. and i can't find any solutions for that. every time i want to update I need to formate everything. please help

sazzadbk05 said:
how can I decrypt twrp? i can't update my rom without decrypting. and i can't find any solutions for that. every time i want to update I need to formate everything. please help
Click to expand...
Click to collapse
You can type your screen passcode android

Hi I have a problem for your latest twrp twrp-3.4.0_10-2a-picasso-hadenix when I entered the pin code it
stuck on decoding FBE what shoud I do ?

31-01-2021
updated twrp sources
updated fstab
fix recent errors
removed some flags
made the sorting

The Twrp download link doesn't work

Avladis said:
The Twrp download link doesn't work
Click to expand...
Click to collapse
Redmi K30 5G / picasso - Browse /TWRP at SourceForge.net
Code name: picasso
sourceforge.net

Hello Sir and friends,
Thank you the updates.
TWRP 3.5 can flash GSI ROM now. I can mount /system partition in dynamic partition. I assume that we can flash GSI ROM with this updated TWRP with no need to use fastboot command line.

16-02-2021
Fix adb sideload
Updated sources TWRP
Changing the interface of the top bar

[UNOFFICIAL][RECOVERY] TWRP 3.5.1 for Galaxy J7 16

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP is an open source, community project. A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like LineageOS or OmniROM.
Disclaimer
I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Rooting your phone may void warranty so don't root your device unless you know what you are doing.
Downloads
MEGA : TWRP_3.5.1
Flashing
Recovery : Download Recovery.img file from link and flash it through your current recovery in recovery Partiton
ODIN : else pack recovery img in .tar and flash it through ODIN in AP.
Changelog
Fixes
Build compilation in 7.1 tree - CaptainThrowback
SAR: Don't follow symbolic links for block devices - bigbiff
SAR Update script name for clarity - CaptainThrowback
Wrappedkey support running only on FBE devices - CaptainThrowback
TWRP App log information reduced - epicX67
Refresh details after system wipe and adb sideload - AdrianDC
Chinese translation updates - betaxb
Support keymaster 2 - PeterCxy
add tzdata to TWRP for timezones - CaptainThrowback
ParitionManager: support delayed adopted storage mount - PeterCxy
Support to start terminal from file manager directory - AndroiableDroid
Nano support - nebrassy
Add nano support to open files from file manager - CaptainThrowback
Include new magisk apk support to be installed by TWRP - ianmacd
Add support to change directory name where TWRP stores backups - epicX67
Add bash support - not the default shell - DarthJabba9
ORS support to format data - AdrianDC
Add support to flash both slots when flashing an image - epicX67
NL translation updates - ianmacd
Cleanup
Installation cleanup - remove dupe PackageExtractFn - klabit87
Remove logd-reinit service - CaptainThrowback
Fixes
Restore system root context - bigbiff
Only include keymaster 2 if tree supports it - CaptainThrowback
Strip lines containing '--' in language_helper.py - ianmacd
Unlocalized string fix - ianmacd
Credits
all goes to @Astrako for his hard work with all exynos7870 device trees without him this would not be possible
Device trees : https://github.com/samsungexynos7870
7870 Group : https://t.me/samsungexynos7870
PrishSupport : https://t.me/prishsupport
PrishChannel : https://t.me/prishupdates
TWRP : https://twrp.me/site/update/2021/03/17/twrp-3.5.1-released.html
Note : Test it and if you found any issue do let me know by PMing me on telegram @neel0210 .

Hi, I don't have telegram. Can't mount /vendor, internal storage, /data and CPEFS. On official TWRP version 3.2 I also couldn't backup EFS, but with your release I had no such problem.
Don't know if relevant but it says can't find /vendor in fstab when trying from terminal in TWRP.
Also TWRP settings don't get saved.
I appreciate our work. this is almost the newest TWRP release, which is what I like. Do you have some ideas about the bugs?
I think I had the same issues with official TWRP too, but not sure.

StackExploit said:
Hi, I don't have telegram. Can't mount /vendor, internal storage, /data and CPEFS. On official TWRP version 3.2 I also couldn't backup EFS, but with your release I had no such problem.
Don't know if relevant but it says can't find /vendor in fstab when trying from terminal in TWRP.
Also TWRP settings don't get saved.
I appreciate our work. this is almost the newest TWRP release, which is what I like. Do you have some ideas about the bugs?
I think I had the same issues with official TWRP too, but not sure.
Click to expand...
Click to collapse
you can PM me on XDA for your questions

I couldn't wipe /data from this TWRP, but when I did it with adb shell commands (still running the same TWRP) it had no problem. Then I could mount it normally in the same TWRP.

StackExploit said:
I couldn't wipe /data from this TWRP, but when I did it with adb shell commands (still running the same TWRP) it had no problem. Then I could mount it normally in the same TWRP.
Click to expand...
Click to collapse
weird, have you tried any other recovery??

yes, I have tried. The results are mostly similar, but so far I found that orangefox recovery seems to have the least problems. I may test some other ones later.

Can you resend link to download it? This one was deleted or sth.

Please, can someone share the recovery file with me?

@neel0210 link is crashed

Need this recovery because orange fox doesnt work with A12

Namhoangnguyen said:
@neel0210 link is crashed
Click to expand...
Click to collapse
Releases · samsungexynos7870/android_device_samsung_j7xelte
Contribute to samsungexynos7870/android_device_samsung_j7xelte development by creating an account on GitHub.
github.com