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.2-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
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.
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
Page on our website with instructions, etc.
Direct download link
If you have just used fastboot oem unlock, you should let the device boot up normally first before trying to install TWRP. If you boot TWRP first before booting normally, you will be prompted for a password. Hit cancel and got to Wipe -> Format Data. Type yes at the prompt and hit the "enter" key. Hit the home button at the bottom and Reboot -> Recovery. Unlocking the device will cause you to lose all userdata, apps, pictures, downloads, etc.
To root, when you select to reboot from the GUI in TWRP, you will be asked if you want to install SuperSU. Swiping to confirm will root your device.
Thanks! I assume since you posted it, it's totally fine to flash on the N5, but are you expecting there to be issues with 4.4? I know a lot of stuff changed, so are we going to run into problems early on?
Thanks again for all of your work. I've been using TWRP for well over a year now!
Party can start now TWRP is here!
Thanks for all your hard work Dees_Troy
Awesome! Thank you for your hard work OP!
@Dees_Troy
Boss is finally here!! Good work as always!
TWRP!
{
"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"
}
nuff said.
My favorite recovery is here!
This is stable ? I still waiting for my phone to get delivered zzzz
Sent from my GT-I9505 using Tapatalk
Hoping the N5 isnt as slow as the G2 when it comes to wiping partitions in recovery.
Anyone do this through goo manger yet on the N5?
Please post feedback.
Says no recovery available for me?
What is the difference between this one and the other official TWRP excapt the touch thing?
^^^ Good question.
Also (unless I missed it) can we get a link to the direct TWRP download so we can run it through fastboot.
Haeretik said:
What is the difference betweent this one and the other official TWRP excapt the touch thing?
Click to expand...
Click to collapse
This thread is from the original author of twrp.
Gesendet von meinem Nexus 5 mit Tapatalk
Haeretik said:
What is the difference betweent this one and the other official TWRP excapt the touch thing?
Click to expand...
Click to collapse
This one was posted by the Official Creator and Developer of Team Win Recovery Project.
The other one was more of "spreading the news" and was in the incorrect section.
This one is also one version ahead.
Sent from my Nexus 5 using Tapatalk
Hand76 said:
^^^ Good question.
Also (unless I missed it) can we get a link to the direct TWRP download so we can run it through fastboot.
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/hammerhead
Sent from my Nexus 5
Good to know, i unsubscribe the other thread Thanks for your answers
sorry for the noob question : what happens when an official OTA hits, if I unlock the bootloader and flash this recovery without rooting ?
Everytime I boot up the phone it takes me to the twrp screen. I can't seem to get to home screen? Is this normal?
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?
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
{
"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"
}
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. It allows you to back up and restore your data, flash custom ROMs and zips to your device, repair broken file systems, and root your device.
CHANGELOG for 3.1-0:
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
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
XDA:DevDB Information
TeamWin Recovery Project, Tool/Utility for the LeEco Le 1S
Contributors
DroidThug, lbule
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Current Stable Version: 3.1.0
Stable Release Date: 2017-03-06
Created 2016-12-28
Last Updated 2017-03-15
DOWNLOADS
https://dl.twrp.me/x3/
You can also download from the app
You can Find more information and download links on our website
INSTRUCTIONS
Find them here
https://twrp.me/devices/letvle1s.html
Known Bugs
Battery stats miscalibrated at 50% (capacity files are getting reset)
NOTE:
The block files are located at:
Code:
/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/$insertwhateverblockyouwant
Awesome Work!
New era beings
Thank you @DroidThug
A quick note that this will fail to install the 20161127 Resurrection Remix ROM (and possibly the CM ROM also by Bule), aborting with "error: 7"
This is due to the fact that the RR (and probably CM) ROM was badly constructed, it makes TWRP think that it is being installed on the wrong device.
To fix this follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=2522762
You need to delete the first line in the file "META-INF/com/google/android/updater-script", the one starting with "assert(" and ending with a semicolon (as each full line of code in the file does, using an editor that recognises non-windows end of line characters is advised for clarity).
This line is supposed to prevent bricking a device by preventing flashing a ROM for a different device that is not listed in the file, Bule (or whoever created the custom TWRP) seems to have produced a broken TWRP that ignores this important error to flash a broken ROM .zip, edit the updater-script file in the ROM and it flashes just fine with official TWRP.
I'm sorry if this question is stupid, but
Does this work with all variants of 1s? Like x500, x507,x509 and more that there are.
Because i have x509 and of like to know if there's a problem with that...
sscsps said:
I'm sorry if this question is stupid, but
Does this work with all variants of 1s? Like x500, x507,x509 and more that there are.
Because i have x509 and of like to know if there's a problem with that...
Click to expand...
Click to collapse
Yes it works.
Now we really need some good custom rom to flash on le1s ..
But how to root le 1s without pc
Bro Mine device is not rooted and M running eui5.8.019s
While installing TWRP through fastboot it doesn't require unlocked bootloader ?
tejus said:
Bro Mine device is not rooted and M running eui5.8.019s
While installing TWRP through fastboot it doesn't require unlocked bootloader ?
Click to expand...
Click to collapse
It will unlock it automatically
sscsps said:
It will unlock it automatically
Click to expand...
Click to collapse
I successfully unlocked bootloader by
Fastboot oem unlock
But problem is that now when i use fastboot flash command there's written unable to flash (will tell u exact error today )
tejus said:
I successfully unlocked bootloader by
Fastboot oem unlock
But problem is that now when i use fastboot flash command there's written unable to flash (will tell u exact error today )
Click to expand...
Click to collapse
Okay, I'll try to help.
For me, i followed the steps on the device page on twrp site and it worked fine.
When I executed flash command, it first unlocked tge bootloader abd then flashed the recovery and then when I executed reboot command, it locked the bootloader by itself.
sscsps said:
Okay, I'll try to help.
For me, i followed the steps on the device page on twrp site and it worked fine.
When I executed flash command, it first unlocked tge bootloader abd then flashed the recovery and then when I executed reboot command, it locked the bootloader by itself.
Click to expand...
Click to collapse
i dont know why it didnt worked on window 7 but worked on ubuntu
and also i installed every drivers still but now success on ubuntu
tejus said:
i dont know why it didnt worked on window 7 but worked on ubuntu
and also i installed every drivers still but now success on ubuntu
Click to expand...
Click to collapse
Okay, need anything else, just ask anyone
Deleted!!
Moving to another post.
thanks for the latest recovery
This TWRP has saved me SO many headaches with these phones.
If any one have le 1s related problem and solution or any one want to try new rom or kernal asap then all of u are welcome in our group on telegram so plz join with us
Requriemt
1. Download telegram from play store
2. Just click below link
https://telegram.me/LeSuperGroup
Thanks all of u
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.1.1-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/androidbootablerecovery/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:
Recovery Folder
SOURCES:
sources (WIP)
Credits: @jonas2790 , big thanks to you and AndroidPrimou team for device/kernel/vendor trees. :good:
TWRP team. :good:
Changelogs
2017/5/26(fixed):
Updated to TWRP 3.1.1-0
2017/3/11:
Updated to TWRP 3.1.0-0 with proper Android nougat supports.
2017/1/26:
release of 3.0.3-0 with LZMA compressed, reduces image size.
?
on one v cdm maybe?
kikon34 said:
on one v cdm maybe?
Click to expand...
Click to collapse
sorry, i don't have the CDMA variant of this device, i'm not sure if it can "force" flash on primoc, so take you own risk or wait for further info, thanks!
it's super, but it boot very loooong time. the biggest bug is, recovery can't read any sd card in the phone. but the adb sideload helped. thanks again for the new recovery.
spiramedia said:
it's super, but it boot very loooong time. the biggest bug is, recovery can't read any sd card in the phone. but the adb sideload helped. thanks again for the new recovery.
Click to expand...
Click to collapse
works fine for me, none of those bug happened on my phone, thanks.
tarkzim said:
works fine for me, none of those bug happened on my phone, thanks.
Click to expand...
Click to collapse
belive me, sideload does its work. so if you can just try to fix the sd bug. some time i need it
spiramedia said:
belive me, sideload does its work. so if you can just try to fix the sd bug. some time i need it
Click to expand...
Click to collapse
i'm sorry, but SDCard works for me so i can't debugging with, are you using One V GSM variant or CDMA variant?
tarkzim said:
i'm sorry, but SDCard works for me so i can't debugging with, are you using One V GSM variant or CDMA variant?
Click to expand...
Click to collapse
GSM variant. Strange. Then maybe i have done something wrong.
spiramedia said:
GSM variant. Strange. Then maybe i have done something wrong.
Click to expand...
Click to collapse
any log? send it
new build released
updated to TWRP 3.1.1-0 with some nougat changes.
please test it and give some feedback, thanks.
Would help if there was a Nougat ROM. I'm tempted to obtain a primou unit just to maintain CM/Lineage 13.
Paspie said:
Would help if there was a Nougat ROM. I'm tempted to obtain a primou unit just to maintain CM/Lineage 13.
Click to expand...
Click to collapse
i have built it once, but not booting and i don't have the way to see the logs or debugging with it due to i can't even get to bootanimation...
i'm sorry for the wrong image files...
i thought it was a working twrp builds since 3.1.0, but it was not...
so i just removed "WRONG" files, and now the correctly TWRP image has been uploaded.
======================================
OK, i just get RR Nougat (7.1) to boot on my One V, but a lot of crashes and things not working.
so i will try to fix those bugs and let you know, thanks.
here are some screens.
@jonas2790
You'll almost definitely want to max out the CPU to 1.5GHz, as the experience would be painful otherwise.
Paspie said:
You'll almost definitely want to max out the CPU to 1.5GHz, as the experience would be painful otherwise.
Click to expand...
Click to collapse
will try to do that, thanks.
but ROM is still not playing well, sometimes doesn't boot at all.
Most likely it's a RAM issue. The build will have to be as minimal as possible to work, I'm not sure a full RR build will cut it.
Hello, I installed your port twrp 3.1.1-0, before that there was version 2.6.3.0 from the official site twrp. I liked the interface and new features, thank you very much for the port. Now there is one problem: twrp takes a section of emmc, which is 95 MB in size, as an external memory card. Because of this, when backing up the android_secure partition, which is actually on an external memory card, twrp thinks that android_secure is in the emmc section and, correspondingly, tries to copy the image of android_secure located in emmc, and it's not there. When you select the partitions to create the images, the android_secure size is displayed as 0 MB, and the creation of the android_secure image is completed in 0 seconds. And when restoring the image of the android_secure partition (made in twrp 2.6.3.0), twrp restores it to the emmc partition, creating the android_secure folder in it and restoring it to it until the memory in this section is full, and at the end the error due to a lack of memory in Emmc.
And another question: why can not I copy the image of the recovery partition? It simply is not in the list of sections. In the official version 2.6.3.0 there is such an opportunity, though for some reason there is no possibility to restore it, do not know why?
Screenshots and logs by link: https://cloud.mail.ru/public/6our/8DmZauMtw
I apologize, if that, just could not find how to download them here
°Andrew° said:
Hello, I installed your port twrp 3.1.1-0, before that there was version 2.6.3.0 from the official site twrp. I liked the interface and new features, thank you very much for the port. Now there is one problem: twrp takes a section of emmc, which is 95 MB in size, as an external memory card. Because of this, when backing up the android_secure partition, which is actually on an external memory card, twrp thinks that android_secure is in the emmc section and, correspondingly, tries to copy the image of android_secure located in emmc, and it's not there. When you select the partitions to create the images, the android_secure size is displayed as 0 MB, and the creation of the android_secure image is completed in 0 seconds. And when restoring the image of the android_secure partition (made in twrp 2.6.3.0), twrp restores it to the emmc partition, creating the android_secure folder in it and restoring it to it until the memory in this section is full, and at the end the error due to a lack of memory in Emmc.
And another question: why can not I copy the image of the recovery partition? It simply is not in the list of sections. In the official version 2.6.3.0 there is such an opportunity, though for some reason there is no possibility to restore it, do not know why?
Screenshots and logs by link: https://cloud.mail.ru/public/6our/8DmZauMtw
I apologize, if that, just could not find how to download them here
Click to expand...
Click to collapse
thanks for your feedback, but i'm getting tired with this device,
just too old and too slow to make it running new Android stuff...
maybe i will look into it soon and get back to you, or i'm gonna abandon this thing.
tarkzim said:
just too old and too slow to make it running new Android stuff...
Click to expand...
Click to collapse
There most likely, all you need to do is swap memory partitions, and emmc display like emmc, not as SDCard. After all, this version of twrp is officially designed for a higher Android, and there the memory sections are located on the contrary than on the HTC One V. Did you check this version on your One V?