[RECOVERY][09-18-2014] TWRP2 Touch Recovery 2.8.0.3

[RECOVERY][09-18-2014] TWRP2 Touch Recovery 2.8.0.3 - Sprint HTC One (M7)

[RECOVERY] TWRP 2.8.0.3 Touch Recovery
The most up to date TWRP available for the M7SPR, with enhancements others are now migrating to their repos / phones (battery feedback, performance, etc.).
--------------------------
With permission graciously granted by the venerable @Dees_Troy I am opening this thread for further developing and maintaining the TeamWin Recovery Project (TWRP or TWRP2) for the Sprint HTC One (m7wls) device.
Want to Donate to me?
Cool! Not required, but I certainly appreciate all donations. I do risk my phone with every build I test, so some backup bucks for a dev phone (or even a dev phone if you have one to send) would be great. To donate, click my Donate button or just Go Here.
** General Description and Use **
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel. For more details, look to @Dees_Troy's original description.
Why the new thread? Because TWRP2 is now as up to date for Sprint HTC Ones (m7wls) as any other device. Indeed the issues so many have complained about regarding the first release of the recovery for our phone are all fixed. @Dees_Troy once wrote, quite accurately, that anyone could compile and fix the issues if they wanted because TWRP2 is fully open source. Well, that's the point -- it's done now, and I plan to keep updating, regularly, this recovery.
What Works (see also Change Logs and Issues List):
It appears everything, including OTG Support, off-line charging with notifications (LED and UI), screen-blank, and much more. Alas, bugs happen so if you find one, please post the relevant information about the bug here and create an issue on the github project for TWRP2 Sources given below. Devs, please use the updater-binary provided in this thread. Please read the "TWRP2 Things to Watch Out For" section in Change Logs and Issues List for details on why.
Reported Issues, Recent Updates and Things To Watch Out For: Read the Change Logs and Issues List.
To save you some headaches -- seriously -- read the Change Logs and Issues List -- particularly dealing with backups on newer versions like this and older versions, e.g., 2.6.3 or below.
FIRST AND FOREMOST NOTICE:
*** Use this custom recovery at your own risk. It is possible that use of this software may violate your carrier's Terms of Use/Terms of Service. Read the DISCLAIMER before committing to the use of this application.***
SECOND (AND JUST AS 'FOREMOST'), We all should recognize and give generous thanks to @Dees_Troy and the contributors to Team-Win-Recovery-Project ("TWRP"). Further, the same recognition and thanks should go to Steve Kondik And Koushik Dutta and team for creating CyanogenMod. Both of those projects are the basis of all TWRP builds you download here. Between these giants we get to reap huge benefits and just add that which we need. In short, any work I do here is merely standing on the shoulders of those mentioned above. To see the history of TWRP on our Sprint HTC Ones, look to this thread. Finally, give thanks to @kushdeck for his initial work on the device tree for m7wls devices.
** PREREQUISITES **
1) A rooted, Sprint HTC One (m7wls) Android phone;
2) The phone has an unlocked bootloader.
If you don't know what the above means, don't try to install this recovery by yourself -- that's why we have the Sprint HTC One Q&A, Help & Troubleshooting thread.
** INSTALLING **
Install through fastboot. If you don't know how to do that, you should not yet try to do so or even download this recovery. This is not a support thread for installing recoveries, it is a development thread for developing and enhancing the TWRP2 recovery for m7wls devices. To learn about installing recoveries, please post to the Sprint HTC One Q&A, Help & Troubleshooting thread.
Source Code:
The sources for the entire recovery are open source and you can build your own if you like. To do so, read How to compile TWRP touch recovery. For the specific sources necessary for the Sprint HTC One (m7wls) I keep sources up to date here:
TWRP2 Sources
HTC Common Device Tree
M7WLS Device Tree
Kernel
Offline Battery Charging
Feel free to fork those and send pull requests as you see fit.

Disclaimer
*** Legal Disclaimer -- READ ALL OF THE FOLLOWING ***
If you use the software, or convey it to someone else, you and all subsequent
conveyees are bound by the following:
# LEGAL DISCLAIMERS AND ASSUMPTION OF THE RISK BY THE USER OF THIS PROGRAM
# Assumption of the Risk of Use
# YOU ASSUME, AND AGREE TO ASSUME, ALL THE RISK OF HARM BY USING THIS
# PROGRAM. THIS PROGRAM MAY VOID YOUR WARRANTY WITH A THIRD PARTY,
# IT MAY IMPROPERLY OPERATE AND DAMAGE YOUR DEVICE, IT MAY CAUSE ANY
# MYRIAD OF HARMFUL OUTCOMES REGARDING YOUR DEVICE OR THE USE OF THE DEVICE
# ON WHICH IT GETS INSTALLED. YOU ACKNOWLEDGE THAT YOU ARE AWARE OF THOSE
# RISKS, UNDERSTAND THOSE RISKS, AND VOLUNTARILY AND INTELLIGENTLY ELECT
# TO ENGAGE THOSE RISKS BY USING THE PROGRAM.
#Disclaimer of Warranty.
# THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
# LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
# OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND,
# EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
# WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
# THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH
# YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME ALL LIABILITY AND
# AGREE THAT IN NO EVENT WILL YOU SEEK ANY FORM OF RECOMPENSE, WHETHER LEGAL OR
# EQUITABLE, INCLUDING BUT NOT LIMITED TO NECESSARY SERVICING, REPAIR,
# CORRECTION OR OTHERWISE.
#Limitation of Liability.
# IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL
# ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE
# PROGRAM, PERMITTED OR NOT, BE LIABLE TO YOU FOR LEGAL DAMAGES OR EQUITABLE
# RELIEF, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES
# ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT
# LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED
# BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
# PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
# POSSIBILITY OF SUCH DAMAGES.

Downloads
Current Releases:
TWRP2 Recovery 2.8.0.3
MD5: 4967f4139e6a89ec38fdcdf3363fa183
IMPORTANT!!!: If you are upgrading from a version less than 2.7.1.3, please run a nandroid backup of your ROM before loading the new TWRP. A latent command to wipe your data partition may be lurking in your /misc partition from a prior factory reset request if you ever requested that at the bootloader menu. This TWRP will honor that (as will all TWRP versions containing the new code).
Updater Binary (updater-binary for flashable zips) 2.7.1.2-06-18.2014
MD5 Hash: 32f38d458c380300e8606d7994c7d49e
Devs -- This updater-binary is for use in your flashable zips if your users are having problems with 'asserts on getprops.' This is fully TWRP2 compatible (in effect, Android 4.3 and Android 4.4 compatible). For documentation and supported updater-script functionality, see this post.
Prior Releases:
TWRP2 Recovery 2.8.0.2
MD5: aebcb0eb2fa171e77bdd7e005c45f8ba
IMPORTANT!!!: Before loading the new TWRP, please run a nandroid. A latent command to wipe your data partition may be lurking in your /misc partition from a prior factory reset request if you ever requested that at the bootloader menu. This TWRP will honor that (as will all TWRP versions containing the new code).
TWRP2 Recovery 2.7.1.3
MD5: 9b62f4fc94fa2fc2c9c834e8602773cd
IMPORTANT!!!: Before loading the new TWRP, please run a nandroid. A latent command to wipe your data partition may be lurking in your /misc partition from a prior factory reset request if you ever requested that at the bootloader menu. This TWRP will honor that (as will all TWRP versions containing the new code -- official or not).
TWRP2 Recovery 2.7.1.2
MD5: 0078cafec08e3dae169191a31ca94571
Updater Binary 2.6.3.4a (updater-binary for flashable zips)
MD5 Hash: ac14398cc826e8932d1e007a5b476c12
TWRP2 Recovery 2.7.1.1
MD5: 0078cafec08e3dae169191a31ca94571
TWRP2 Recovery 2.7.0.9
MD5: c8c24a041802492543d533d8b3d3f853
TWRP2 Recovery 2.7.0.4b
MD5: 84f2c210b0cf4dcc5e00d6e7becec636
TWRP2 Recovery 2.7.0.4
MD5: d49f435e1d6ad1880ad0d938bd6fb38b
TWRP2 Recovery 2.7.0.3
MD5: 2cbeb54429a96063898578160720b4c1
TWRP2 Recovery 2.7.0.2
MD5: 8dd6520d18668f92c8daa29128ad07a7
TWRP2 Recovery 2.6.3.4a
MD5: 6c10577b5b587e7f44b2b1d7f0659216
TWRP2 Recovery 2.6.3.4
MD5: 107d81dcabacc777f14f42656847ec5c[/INDENT]

Change Logs and Current Issues
Current Release:
Version 2.8.0.3 (09-18-2014)
Includes all prior features from 2.7.x.x, 2.8.0.1 and 2.8.0.2;
Increased SELINUX and POSIX compliance for a bit more future-proofing;
Supports for older (Jelly Bean) crypto;
Battery LED support for charging (as always from this TWRP);
Updated off-mode charging battery graphics (now from latest (standard) CM 11.0 sources, which are quite nice);
Performance mode for long operations (as always from this TWRP);
Synced with Android 4.4.4 / CM-11.0 sources as of date of build (and don't worry -- still supports prior versions);
Synced with OmniRom TWRP2 underlying sources as of date of build;
Updated exFAT support.
Updater-binary Version 2.7.1.2-06-18-2014 Change Logs:
Android 4.4 source tree compatible -- particularly alleviates assert(getprop ...) errors on which old updater-binaries fail;
Built with CM11 with up to date TWRP2 sources as of date of the build.
Prior Releases:
Version 2.8.0.2 (09-14-2014)
Includes all features of 2.8.0.1 -- Note MTP support is very cool;
Battery LED support for charging (as always from this TWRP);
Performance mode for long operations (as always from this TWRP);
Synced with Android 4.4.4 / CM-11.0 sources as of date of build (and don't worry -- still supports prior versions);
Synced with TWRP2 underlying sources as of date of build;
Ext4 file system synced with HTC version (instead of CM-11, as that has bugs);
Updated exFAT support.
Version 2.7.1.3 (07-19-2014)
Fixes /misc partition overwrites to incorrect area (a long standing bug in the official TWRP);
Now using by-name partitioning scheme for all mounts;
More feedback while doing operations;
Added /devlog as a mountable partition (great for devs and those wanting to erase the files and/or look into the logs;
Synced with CM-11 underlying sources as of date of build;
Synced with TWRP2 underlying sources as of date of build;
Updated off-line battery charger application with latest android code and blue text.
Version 2.7.1.2 (06-18-2014)
General maintenance release includes kernel bug fixes/updates;
Synced with CM-11 underlying sources as of date of build;
Sycned with TWRP2 underlying sources as of date of build;
Updated off-line battery charger application with latest android code and blue text.
Version 2.7.1.1 (06-05-2014)
General maintenance release includes kernel bug fixes/updates;
Synced with CM-11 underlying sources as of date of build;
Sycned with TWRP2 underlying sources as of date of build.
Updater-binary Version 2.6.3.4-02-22-2014 Change Logs:
Android 4.4 source tree compatible -- particularly alleviates assert(getprop ...) errors on which old updater-binaries fail;
Built with CM11 with up to date TWRP2 sources as of date of the build.
Version 2.7.0.9 (05-01-2014)
Upgraded kernel to support (arguably inappropriately forced) CM-11 ROM updater-script changes;
Support for CM-11 based builds using only ".md5sum" as opposed to ".md5" as the suffix to md5 hash files;
Synced with CM-11 underlying sources as of date of build.
Sycned with TWRP2 underlying sources as of date of build.
Version bump to cover the fact that CM-11 team put out some TWRP builds with (seemingly) randomly picked version numbers to try to cover on the (forced) updater-script changes.
Many other fixes.
Version 2.7.0.4b (04-06-2014)
Fixes 'set_metadata_recursive some files failed" message, which caused install failure of some Sense 6 ROMs.
Version 2.7.0.4 (03-31-2014)
Minor change to /etc/fstab to help some troublesome USB sticks;
FITRIM support for ext4 (fstrim works in recovery);
New offmode battery charging app -- new graphics and real-time battery charge percentage reporting;
Synced with CM-11 underlying sources to date of the 03-29-2014.
Version 2.7.0.3 (03-25-2014) Change Logs:
Slipstreamed in fix for slow formats on zip flashables -- if you have a prior build of this (look at the date on your flash .img file), redownload this and reflash;
Upgraded all underlying bits to current CyanogenMod build (cm-11.0 as opposed to older Nov. 2013 snapshot of stable/cm-11.0) -- source code synced with CM repo commits as of the date of the build;
All new kernel - using the standard (supported) msm8960 cm11.0 Sprint kernel as opposed to m7 basis -- decreases recovery size by roughly 500Kbytes;
All TeamWin committed bug fixes up to the date of the build (see https://github.com/omnirom/android_bootable_recovery);
Fairly aggressive thermal CPU throttling when in performance mode -- tweaks will be forthcoming based on user feedback for allowing higher temps before throttling.
Note: the TeamWin splash page comes up later than before so don't let that confuse.
TWRP2 Version 2.7.0.2 Change Logs:
All changelogs consistent with official TWRP2 2.7.0.1 release
Includes backward compatibility with old update-binaries (@Dees_Troy's patch after 2.7.0.1 release)
All other tdhite's enhancements from prior builds
Modified Performance mode to run with OnDemand kernel governor as opposed to Performance (runs CPUs a little cooler)
Still based on CM11 -- I am debating whether, given the patch release above, that CM10.2 is worth it in the end.
TWRP2 Version 2.6.3.4a Change Logs:
Added multi-core support for flash and nandroid long running operations -- message notifies you when performance mode is on or off;
Added screen dim settings;
Enhanced file searching for openrecovery scripts;
@elvisypi's off-line charging graphics, now committed until another cool set arrives.
TWRP2 Version 2.6.3.4 Change Logs:
All known issues fixed (OTG support, Screen Blank/Revive, off-line charging animation and screen blank, and much more);
Battery Charging LED support (mimics standard booted ROM LED indicators).
TWRP2 Things to Watch Out for:
Users have reported incompatibility of backups from the (long ago) release 2.6.3.0, though no problems with backup/restore done with the current release. To work around, restore ROM in prior release then flash new TWRP2 release and backup again.
IMPORTANT: A number of flashable zips include old (only Android 4.3 or below compatible) updater-binary executables. Those may cause "getprop" assertion errors (though generally should not as TWRP2 2.7.0.2 and above detect that and provide internal mappings for the old updater-binaries).
There are some themes in use that prevent folks from seeing the Vibration settings. IF YOU ARE USING A THEME -- PLEASE RUN IT WITHOUT THE THEME BEFORE REPORTING BUGS -- TWRP DOES NOT PROMISE THEMES ARE BACKWARD COMPATIBLE
Some folks execute a "fastboot erase cache" after flashing a recovery. Do not do that! Instead, either "fastboot format cache" or leave it alone. The fastboot erase cache command just blows the file system away and leaves you with an unmountable /cache partition until it's formatted (wipe will do that if you end up with errors about 'cannot mount /cache').

Nicely done sir
BTW first
@tdhite if you need a Dev-Host or AFH mirrors let me know I'll post here
AFH Mirror
Dev-Host Mirror

BD619 said:
Nicely done sir
BTW first
Click to expand...
Click to collapse
Let me know how it goes
Sent from my HTCONE using xda app-developers app

Cant wait to try this... :good::good:

BD619 said:
Nicely done sir
BTW first
@tdhite if you need a Dev-Host or AFH mirrors let me know I'll post here
Click to expand...
Click to collapse
Yea -- I do. My mirrors are fine too, but I'd really like this in the mirrors most folks have familiarity with. Thanks so much. If you upload somewhere like that, lemme know and I'll update the download links.

Thanks for your contribution man!
Sent from my HTCONE using Tapatalk

Sweet well done!!. Thank you much sir. One request, can we get the option to turn off vibration please

Superb job. Finally a recovery without bugs!
Sent from my HTC One using Tapatalk

benny3 said:
Sweet well done!!. Thank you much sir. One request, can we get the option to turn off vibration please
Click to expand...
Click to collapse
Yes please disable vibration if possible
Update tried Advance wipe/wipe
cache/dalvik cache/system/data
Failed
Tried using superwipe
Failed
Was getting unable to mount cache error.
Flashed back to 2.6.3.0
Should have gotten a recovery log darn it

Awesome!! Thank you for all your hard work this is amazing

benny3 said:
Sweet well done!!. Thank you much sir. One request, can we get the option to turn off vibration please
Click to expand...
Click to collapse
BD619 said:
Yes please disable vibration if possible
Update tried Advance wipe/wipe
cache/dalvik cache/system/data
Failed
Tried using superwipe
Failed
Was getting unable to mount cache error.
Flashed back to 2.6.3.0
Should have gotten a recovery log darn it
Click to expand...
Click to collapse
If u have a custom theme delete it reboot into stock recovery and the option for vibration shows.
sent from my-beanstalk-one

bearw815 said:
If u have a custom theme delete it reboot into stock recovery and the option for vibration shows.
sent from my-beanstalk-one
Click to expand...
Click to collapse
No theme here

BD619 said:
No theme here
Click to expand...
Click to collapse
Mine shows option to change vibration.
The error stated for the super wipe script is a get prop error failure.
Edit: getprop (ro.product.device)==
sent from my-beanstalk-one

bearw815 said:
Mine shows option to change vibration.
The error for the super wipe script is a get prop error failure.
sent from my-beanstalk-one
Click to expand...
Click to collapse
I have the vibration change as well
Sent from my One using Tapatalk 2

benny3 said:
Sweet well done!!. Thank you much sir. One request, can we get the option to turn off vibration please
Click to expand...
Click to collapse
Vibrations are all there -- just to go to "Settings" and "Vibration Duration" -- turn them all down to your liking. If anything is missing, look to your theme -- others had the same issue during early testing.

BD619 said:
Yes please disable vibration if possible
Should have gotten a recovery log darn it
Click to expand...
Click to collapse
But what will you use then?
Sent from my GT-N5110 using Tapatalk

FrozenRiff said:
But what will you use then?
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
Good point...

Related

[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

Reserved.

Dees_Troy said:
This has been available for a little while, but now I'm adding an official thread for it here on XDA.
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
Would it work with V28C ?
Thx.
Sent from my LG-P970 using xda premium

florin250 said:
Would it work with V28C ?
Thx.
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
i dont think so......
but....we better wait answer from the expert
@OP
wow.....i just dream about this last night and today you give this.....thank you so much....

the latest is 2.3.1.1
http://techerrata.com/file/twrp2/p970/openrecovery-twrp-2.3.1.1-p970.img

Ilko said:
the latest is 2.3.1.1
http://techerrata.com/file/twrp2/p970/openrecovery-twrp-2.3.1.1-p970.img
Click to expand...
Click to collapse
download stuck at 99,99%, why???
edit : downloading without download manager, now it's okay

In ClockworkMod, on Nandroid Backup...(there is no option to save the name as we wish), it defaultly gives a name with date for backup..
So, here in TWRP, is there possibility for giving name for Nandroid Backup ?
And what are the bugs remaining after 2.3.1.0 update ?
Had anyone brick phone or bootloop history with this ?

sekhar13515 said:
In ClockworkMod, on Nandroid Backup...(there is no option to save the name as we wish), it defaultly gives a name with date for backup..
So, here in TWRP, is there possibility for giving name for Nandroid Backup ?
And what are the bugs remaining after 2.3.1.0 update ?
Had anyone brick phone or bootloop history with this ?
Click to expand...
Click to collapse
The old TWRP recoveries never completely worked for OB.Sometimes it was the SD mounting, sometimes you couldn't restore the backup done with the same TWRP version and so on.I will try this because I like TWRP more than CWM but it's the last time if it won't work.
---------- Post added at 10:37 AM ---------- Previous post was at 10:36 AM ----------
Ilko said:
the latest is 2.3.1.1
http://techerrata.com/file/twrp2/p970/openrecovery-twrp-2.3.1.1-p970.img
Click to expand...
Click to collapse
No, it's not but it's 2.3.20(not yet for OB of course).

USB storage not mounting.
Back to the "bomb proof" cwm 5.8.1.3 touch.

great share!Very good job, thank you.

there is a new version 2.3.1.1

timvdhoorn said:
there is a new version 2.3.1.1
Click to expand...
Click to collapse
ilko already said it here http://forum.xda-developers.com/showpost.php?p=34469364&postcount=6 and there is a newer version but it haven't been built to our device yet.

Updated!

Dees_Troy said:
Updated!
Click to expand...
Click to collapse
SDcard mounting as mass storage still not working, please check.

I was writing the same report : )
well, too bad. I like it but it's useless to me since I transfer files very often through recovery. I can't compile a flasher with that

Indeed I prefer twrp rather than cwm.
Dees, what you need to solve the SD card?
Enviado desde mi LG-P970 usando Tapatalk

Every new version always the same problem.

re4lsk said:
Indeed I prefer twrp rather than cwm.
Dees, what you need to solve the SD card?
Enviado desde mi LG-P970 usando Tapatalk
Click to expand...
Click to collapse
I need to know the proper path for the lun file. By default it's in /sys/devices/platform/usb_mass_storage/lun0/file
You'll have to look for it in TWRP, not in Android though if you find it in Android then I can try switching kernels... I'd need a copy of your current kernel or boot image to switch.
A lot of newer devices don't support USB storage mode anymore at all, so bear that in mind when you're getting ready to upgrade to a new device. You'll have to get used to using ADB to push files or use ADB sideload mode.

Dees_Troy said:
I need to know the proper path for the lun file. By default it's in /sys/devices/platform/usb_mass_storage/lun0/file
You'll have to look for it in TWRP, not in Android though if you find it in Android then I can try switching kernels... I'd need a copy of your current kernel or boot image to switch.
A lot of newer devices don't support USB storage mode anymore at all, so bear that in mind when you're getting ready to upgrade to a new device. You'll have to get used to using ADB to push files or use ADB sideload mode.
Click to expand...
Click to collapse
well the black is an old device(2011) so usb storage still works, you need zImage or boot.img to get the kernel? i can point you to the CM kernel source, i'll see if my old linux VM still works to get you the zImage. but in the mean time i'll upload you the boot.img from cm10 from 20-12-2012 nightly.
CM kernel source

re4lsk said:
well the black is an old device(2011) so usb storage still works, you need zImage or boot.img to get the kernel? i can point you to the CM kernel source, i'll see if my old linux VM still works to get you the zImage. but in the mean time i'll upload you the boot.img from cm10 from 20-12-2012 nightly.
CM kernel source
Click to expand...
Click to collapse
It's not that I need a kernel as much as I need the proper path to the lun file for whatever kernel I happen to be using. Since I don't have an Optimus Black I can't boot it up and look for it myself.

[RECOVERY][G2] TWRP 3.0.0-0 touch recovery [2016-02-06]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

Note, all images have already been loki'd. Just flash away!
AT&T Downloads
Verizon Downloads Special thanks to rhcp for helping test the update for G2 VZW to fix 4.4 rom install.
T-Mobile USA Downloads
Korean F320K Downloads
Sprint Downloads
Bell Canada Downloads
Rogers Canada Downloads
Be sure to thank @djrbliss for his work on loki for the G2. Without loki, recovery and ROMs would not be possible.

SWEET! Thanks!
EDIT: Guess it's not available yet. Can't find it.
Sent from my LG-D801 using Tapatalk 4

You're the MAN! Thank you for all of the hard work Devs! it only gets better from here
it was there a minute ago....

cslingerland said:
You're the MAN! Thank you for all of the hard work Devs! it only gets better from here
it was there a minute ago....
Click to expand...
Click to collapse
You have it? I can't seem to find it.
Sent from my LG-D801 using Tapatalk 4

Once the links go live again, and we install TWRP, does this mean we can flash ROMS now, or do we need to wait for G2-specific development?

Han Solo 1 said:
Once the links go live again, and we install TWRP, does this mean we can flash ROMS now, or do we need to wait for G2-specific development?
Click to expand...
Click to collapse
Once ROMs are available specifically for the G2, you can flash them.
Right now there are none, and flashing something from a different phone WILL cause issues.

chrisexv6 said:
Once ROMs are available specifically for the G2, you can flash them.
Right now there are none, and flashing something from a different phone WILL cause issues.
Click to expand...
Click to collapse
Oh boy. I just want a stock ROM with wifi-hotspot enabled. That’s it.
---------- Post added at 03:23 PM ---------- Previous post was at 03:07 PM ----------
So is this not working yet? When I hit "install OpenRecoveryScript" in GooManager, it says "no recoveries were found for your device".

It hasn't been put on the servers per say.
Sent from my LG-D800 using Tapatalk 4

whats the status on using goomanager to get recovery other then what we already know

I tried updating thru goo manager but it doesn't work. It downloads the new .IMG file but even though it says recovery installed, when I boot to twrp its still version 2.5.*.* any ideas on why this happens? Or how to fix? BTW I'm on a att galaxy s4 (jflteatt)
Sent from my SGH-I337 using XDA Premium 4 mobile app

SeveNVapoR said:
I tried updating thru goo manager but it doesn't work. It downloads the new .IMG file but even though it says recovery installed, when I boot to twrp its still version 2.5.*.* any ideas on why this happens? Or how to fix? BTW I'm on a att galaxy s4 (jflteatt)
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
First, try posting in the correct forum for the correct device, this is the LG G2 section.
Second, change the download directory for GooManager from whatever it currently is to /sdcard/goomanager/ and that will fix it.

Your right...it worked
Sent from my SGH-I337 using XDA Premium 4 mobile app

Amazing work devs can't wait for more!
Sent from my LG-F320S using xda app-developers app

Fantastic work, thank you so much. Flashed, backed up, started removing system apps. Time to start working on a Custom Rom. Guess I ought to learn Aroma Installer, haven't made a rom since the the Bionic so I've never messed with it before.

Han Solo 1 said:
Oh boy. I just want a stock ROM with wifi-hotspot enabled. That’s it.
---------- Post added at 03:23 PM ---------- Previous post was at 03:07 PM ----------
So is this not working yet? When I hit "install OpenRecoveryScript" in GooManager, it says "no recoveries were found for your device".
Click to expand...
Click to collapse
I totaly feel you,
The phone itself feels solid except for all the crap bloatwear thats bugging down the ram and storage.
a clean rom with tethering is all this phone needs.

goomanager can't find any recovery for the F320K10m version,
is it possible?

can i hook my phone to PC and run adb and do fastboot flash recovery openrecovery-twrp-2.6.3.0-g2vzw.img ?

exciting stuff, this is great to see

drmp3z said:
can i hook my phone to PC and run adb and do fastboot flash recovery openrecovery-twrp-2.6.3.0-g2vzw.img ?
Click to expand...
Click to collapse
Considering this uses an exploit, almost 100% sure the answer is no.

[RECOVERY][sirius] TWRP 3.0.0-0 touch recovery [2016-02-06]

Reserved
Note that the Z2, like most other Sony devices does not have a proper bootable recovery. As such you have to install a kernel that includes a recovery with it. For a time I will try to continue to supply updated stock kernels repacked with TWRP in them. If you are running one of my kernels or have a custom ROM like OmniROM installed, you can install TWRP in the FOTAKernel partition to stay on the latest version of TWRP.
Device page on our website
Mirror 1
Mirror 2
To install a stock kernel, boot the device into fastboot mode and then from your computer: fastboot flash boot path/to/filename.img

R/W on Root not possible
Hi,
After i flashed this version of the Kernel for .402 FW i got no permissions to write on the root / partition or subfolders (system,..)
Is it possible that this is restricted in the offical version as in Doomlords Unofficial TWRP Version its working fine.
Another User experienced the same:
http://forum.xda-developers.com/showthread.php?p=53330667
Thank you in advance

beloero said:
Hi,
After i flashed this version of the Kernel for .402 FW i got no permissions to write on the root / partition or subfolders (system,..)
Is it possible that this is restricted in the offical version as in Doomlords Unofficial TWRP Version its working fine.
Another User experienced the same:
http://forum.xda-developers.com/showthread.php?p=53330667
Thank you in advance
Click to expand...
Click to collapse
it might be the Sony RIC function, which ensures system partition untouchable.
you can disable it by changing /sys/kernel/security/sony_ric/enable to 0 everytime you boot your device.

Umm how do I flash this via fastboot?
I used the fastboot flash boot twrp.img command and it worked. I could boot into recovery but I cannot boot into Android OS now. Even if I don't press the Volume Up button, the device goes into recovery mode.

eRajesh said:
Umm how do I flash this via fastboot?
I used the fastboot flash boot twrp.img command and it worked. I could boot into recovery but I cannot boot into Android OS now. Even if I don't press the Volume Up button, the device goes into recovery mode.
Click to expand...
Click to collapse
What exactly did you flash ?
You should flash this file --> stock-17.1.1.A.0.402-sirius-repack.img -- with the 'fastboot flash boot ..... ' command.
Flashing ----> openrecovery-twrp-2.7.1.0-sirius.img --- with 'fastboot flash boot .....', wont work,
because the proper way of flashing a recovery is with 'fastboot flash recovery .....'
But according to post 2, you can't 'just' flash a recovery on to the Z2, you need a boot image with a recovery inside, which is the repack i believe.
So flashing the repack with the 'fastboot flash boot stock-17.1.1.A.0.402-sirius-repack.img' should get you back into the OS.

Is there a way of flashing TWRP with a boot image of our choice?

heatl0rd said:
Is there a way of flashing TWRP with a boot image of our choice?
Click to expand...
Click to collapse
Kinda, if the kernel developer add support for having recovery in FOTAKernel partition you can put the recovery.img in there and it'll be used, Cyanogenmod for example does this. Doomlord is reluctant to use it in his kernel for some reason.
Sent from my Nexus 7 using Tapatalk

Ok so just so im clear. This can be installed by flashing "stock-17.1.1.A.0.402-sirius-repack.img" via fastboot.
But can this be installed by simply flashing via an existing recovery?

heatl0rd said:
Ok so just so im clear. This can be installed by flashing "stock-17.1.1.A.0.402-sirius-repack.img" via fastboot.
But can this be installed by simply flashing via an existing recovery?
Click to expand...
Click to collapse
Yes and yes - if someone makes a flashable zip

Dees_Troy said:
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.7.1.0:
-Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
-Various bugfixes to backup and restore
-Improvements to USB storage handling
-Added a class to search for files to make finding the correct brightness file automatic in most cases
-Various other bugfixes and tweaks
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
thank you, looks great but 1 question
will this work with sgp512 (z2 16gb wifi tablet)?

@Dees_Troy
Just installed and version is showing 2.7.0.0. Can i reconfirm the OP links are indeed 2.7.1.0?

I aint really sure what is happening but it seems to, when I fastboot flash stock kernel with this TWRP I can not delete services with Titanium backup...They always get back after a reboot?
I have never experienced this before

Dirtyzecret said:
I aint really sure what is happening but it seems to, when I fastboot flash stock kernel with this TWRP I can not delete services with Titanium backup...They always get back after a reboot?
I have never experienced this before
Click to expand...
Click to collapse
See posts #3 and #4
Basically no automatic write access to system without some tinkering.

arrrgh said:
See posts #3 and #4
Basically no automatic write access to system without some tinkering.
Click to expand...
Click to collapse
Sorry guys, for not reading trough thread.

Downloading recovery 0/100....
Anyone?
Why theres no windows flashing version?

SkyS1gn said:
Downloading recovery 0/100....
Anyone?
Why theres no windows flashing version?
Click to expand...
Click to collapse
Same here. Even after app was updated.
Sent from my D6503 using XDA Premium 4 mobile app

Bad problem with the new cm nightly 20140709 and the twrp manager.
Recovery could not load!

can i have the twrp recovery as a zip file pls?

A flashable zip would be nice! Cause the twrp manager does not work any more on cm.
Or have somebody an introduction for making flashable zips.
Regards Peterle

[RECOVERY] [unofficial] TWRP 3.0.2-0 Asus Zenfone 5 [A500CG] [A600CG]

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

Build in CM-13.0 environment w/TWRP source forked : @mdmower
Fork of TWRP
This fork differs from the original in the following ways:
Designed to be built with CyanogenMod 13.0 only
Require fstab v2 syntax (see examples and supported flags below)
Use external repositories for pigz, exfat, fuse
Power key toggles screen on/off
Remove the need to specify either DEVICE_RESOLUTION or TW_THEME so long as TARGET_SCREEN_HEIGHT and TARGET_SCREEN_WIDTH are set
Other minor customizations (see change history)
Versioning
To help distinguish builds of recovery made from this fork, the minor version digit is replaced with M#. Minor version increments will be handled as needed, independent of TWRP. The major and semi-major version digits follow upstream to roughly indicate feature parity (as close as possible with a fork, anyways).
Convention:
3.0.M0-0 incorporates all major features from TWRP 3.0.0-0
3.0.M1-0 is the minor version increment after 3.0.M0-0 and is independent of any TWRP minor version increment(s)
3.1.M0-0 is the semi-major version increment after 3.0.M4-2 and is tied to a TWRP semi-major version increment
3.0.M0-1 is a device-specific fix to 3.0.M0-0; this device digit resets when any other version increments
maintained rework by : @artefvck
DOWNLOADS:
Fastboot Mode
Flashable Zip
source
Convert ext4 partition to F2FS partition without loosing data
Preface
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel.
The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Prerequisites
PC with ADB installed for SD backups
F2FS compatible ROM
F2FS compatible Kernel
F2FS compatible TWRP Recovery (this recovery has F2FS support, too)
sdcard Fix Permissions script (scroll down a little bit)
Procedure
Flash the F2FS compatible TWRP Recovery with fastboot or other recovery for example
Boot into Recovery
Backup > Data
Save your internal SD card with one of the following options
Either reboot to system and copy files to your PC via USB (MTP)
Or pull files via adb (adb pull /data/media sd_backup)
Copy the kernel and the sdcard fix script to your created backup folder
Wipe > Advanced Wipe > Data > Repair or Change File System > Change File System > F2FS
Wipe > Advanced Wipe > Cache > Repair or Change File System > Change File System > F2FS
Copy the saved SD card content back to your device with: adb push sd_backup /data/media/0/
Afterwards the folder structure should look like this: /data/media/0/…Folders like DCIM, Music, Downloads, …
You can check with: adb shell ls -R /data/media
Restore > Choose backup > Data (the warning about ext4 backup doesn’t matter)
Advanced > Fix Permissions
Flash the sdcard Fix Permissions script with: Install > Choose sdcard fix zip
Wipe > Advanced Wipe > Cache & Dalvik Cache
Flash a F2FS compatible kernel with: Install > Choose kernel zip
Reboot to system
Now your Android device should fly again ��
Note:
In my mind it doesn’t make much sense to format/system to F2FS because you would need a modified ROM to use it. Everytime you update your ROM you would have to modify it to use /system as F2FS. On top of that there shouldn’t be a real performance gain with a F2FS /system partition because it’s read-only. And reading operations are fast with ext4, too. The difference is non-existent or very low. In my humble opinion the so called All-F2FS is pretty useless.
You can format your /data and /cache partition to F2FS. Normally you’ll loose all data in this process and have to reinstall everything. But this small howto will show you how to recover your data so you can continue where you left off. Just like a “dirty” ROM flash.

Good.

oh gee nice that you make update for TWRP 3.0 but is it fixes nandroid backup ?
Because I had this error that make me regret it it's called ( extractTarFork() process ended with ERROR: 255 ) and it's from your TWRP 3.0 M-1 ( if i'm not mistaken ) it's a nandroid backup of stock rom when I want to try the custom ROM
and Keep Up The Good Work yes ?
Regards

Awesome0ne ?
Sent from my ASUS_T00F using Tapatalk

RevanEphys said:
oh gee nice that you make update for TWRP 3.0 but is it fixes nandroid backup ?
Because I had this error that make me regret it it's called ( extractTarFork() process ended with ERROR: 255 ) and it's from your TWRP 3.0 M-1 ( if i'm not mistaken ) it's a nandroid backup of stock rom when I want to try the custom ROM
and Keep Up The Good Work yes ?
Regards
Click to expand...
Click to collapse
latest build fixed
try twrp 3.0.M-2.0

X AnwarMov said:
latest build fixed
try twrp 3.0.M-2.0
Click to expand...
Click to collapse
You Mean TWRP 3.0.2 ? I will try that later when all CM 13 or Android 6.0 ROM quite stable enough ( even though it will still has bugs )
Thanks

RevanEphys said:
You Mean TWRP 3.0.2 ? I will try that later when all CM 13 or Android 6.0 ROM quite stable enough ( even though it will still has bugs )
Thanks
Click to expand...
Click to collapse
please report to your Rom development .
this thread i think can't have problem

Hi,
Instalation is for flash or fastboot?
Good joob

marceloz5 said:
Hi,
Instalation is for flash or fastboot?
Good joob
Click to expand...
Click to collapse
oh yeah fastboot for now ,
latest build i can upload flashable.zip for more easly
thanks

i only get white screen after flashing wonder y

Nice ?
Sent from my ASUS_T00F using XDA-Developers mobile app

X AnwarMov said:
Build in CM-13.0 environment w/TWRP source forked : @mdmower
Fork of TWRP
This fork differs from the original in the following ways:
Designed to be built with CyanogenMod 13.0 only
Require fstab v2 syntax (see examples and supported flags below)
Use external repositories for pigz, exfat, fuse
Power key toggles screen on/off
Remove the need to specify either DEVICE_RESOLUTION or TW_THEME so long as TARGET_SCREEN_HEIGHT and TARGET_SCREEN_WIDTH are set
Other minor customizations (see change history)
Versioning
To help distinguish builds of recovery made from this fork, the minor version digit is replaced with M#. Minor version increments will be handled as needed, independent of TWRP. The major and semi-major version digits follow upstream to roughly indicate feature parity (as close as possible with a fork, anyways).
Convention:
3.0.M0-0 incorporates all major features from TWRP 3.0.0-0
3.0.M1-0 is the minor version increment after 3.0.M0-0 and is independent of any TWRP minor version increment(s)
3.1.M0-0 is the semi-major version increment after 3.0.M4-2 and is tied to a TWRP semi-major version increment
3.0.M0-1 is a device-specific fix to 3.0.M0-0; this device digit resets when any other version increments
maintained rework by : [MENTION=4258433]artefvck
- add new touchscreen synaptics driver / update
- built-in modules
- F2FS partitions
- kernel version v3.10.20
DOWNLOADS:
FOLDER UPLOAD
source :
Device tree
Kernel
Click to expand...
Click to collapse
Thanks for this...no lags whatsoever except when booting to twrp and when booting to system... keep up the good work

can install on cm 12.1?

emirfahimi said:
can install on cm 12.1?
Click to expand...
Click to collapse
Yeah.

tank0412 said:
Yeah.
Click to expand...
Click to collapse
but here you said cm 13 "only"

I've tried both 3.0.M-1.0 and 3.0M-2.0.
They are quite lag on my Zenfone 5 when compare with 2.8.7.0
For example, it takes 10-20 seconds to go into recovery and several second before it reboot.

When i tried backup rom twrp suddenly restart and back to first screen twrp again, i tried twice but the problem still persist

abw_bw said:
When i tried backup rom twrp suddenly restart and back to first screen twrp again, i tried twice but the problem still persist
Click to expand...
Click to collapse
When I try to backup System, Data, Config, and System Image, my phone turns off when the backup nearly completed. and ends up with Usb Logo. :silly:

baszu said:
I've tried both 3.0.M-1.0 and 3.0M-2.0.
They are quite lag on my Zenfone 5 when compare with 2.8.7.0
For example, it takes 10-20 seconds to go into recovery and several second before it reboot.
Click to expand...
Click to collapse
i faced this to.
Sent from my ASUS_T00F using XDA-Developers mobile app

[A2017U][RECOVERY][UNOFFICIAL] TWRP 3.0.2-2 touch recovery for ZTE Axon 7

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.2-2:
-Fix subpartition restore bug (ex: EFS)
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
TWRP 3.0.2-2
Can be updated quickly and easily within TWRP if TWRP is already installed
1) Download the latest version from the above link
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
SOURCE/THANKS:
Device tree: https://github.com/TeamRegular/android_device_zte_ailsa_ii
@DrakenFX for testing and requesting my help
@Unjustified Dev for being....ME of course

Prerequisites:
* Unlocked bootloader Guide Here
Installation:
Code:
adb reboot bootloader
fastboot flash recovery twrp-3.0.2-2-a2017u.img
fastboot reboot
To enter recovery:
* Power + volume up
Code:
adb reboot recovery
Installing Mods:
If you plan on modifying the system, please follow this post here or you'll result in a bootloop.

Reserved

Holy **** that is quick. You are a hero.
I picked up the chinese model though, still waiting for bootloader... They confirmed it but they are taking their time.
Hoping the devices are similar enough that this twrp will also work on mine.

aPexalpha said:
Holy **** that is quick. You are a hero.
I picked up the chinese model though, still waiting for bootloader... They confirmed it but they are taking their time.
Hoping the devices are similar enough that this twrp will also work on mine.
Click to expand...
Click to collapse
The base HW should be the same across the world. The only real difference is the Force Touch feature in the Chinese 6GB model, which might necessitate a different touch screen driver.
The Chinese ROM also calls the device the ailsa_ii, just with a different model number.

that's awsome, very nice work. Now the custom ROMs have open doors

In BoardConfig.mk, wouldn't we want "BOARD_HAS_NO_REAL_SDCARD := false" (just leave it out) and "TW_NO_USB_STORAGE := false" (or leave it out)? I'm pretty sure it has OTG support and it definitely has a real SD card.
Thanks for getting the repo up and running as well.

Very good news! Suprised how fast it all went down, cheers! On a side note, is there any chance this or any other method will ever work for EU models? I really like the phone, but waiting for the manufacturer to do something about the software is kind of hopeless.

MeggaMortY said:
Very good news! Suprised how fast it all went down, cheers! On a side note, is there any chance this or any other method will ever work for EU models? I really like the phone, but waiting for the manufacturer to do something about the software is kind of hopeless.
Click to expand...
Click to collapse
It all depends on ZTE Europe releasing a bootloader unlock for the European (Global) version of the phone.

Thank you! Sharing the device tree helps a ton with additional development. Let's see what we can build with this.

TeutonJon78 said:
In BoardConfig.mk, wouldn't we want "BOARD_HAS_NO_REAL_SDCARD := false" (just leave it out) and "TW_NO_USB_STORAGE := false" (or leave it out)? I'm pretty sure it has OTG support and it definitely has a real SD card.
Thanks for getting the repo up and running as well.
Click to expand...
Click to collapse
1st config as I remember is for internal storage. Something about not allowing you to partition it.
2nd config is to remove mass storage support. TWRP supports mtp.
Sent from my 6045I using Tapatalk

Thank you! One question, which I suppose isn't just limited to TWRP: Though we have TWRP (again, awesome!), we don't have a stock image or a way to get back to "locked, unrooted" status yet or the default ROM, right?

ScaryBugThing said:
Thank you! One question, which I suppose isn't just limited to TWRP: Though we have TWRP (again, awesome!), we don't have a stock image or a way to get back to "locked, unrooted" status yet or the default ROM, right?
Click to expand...
Click to collapse
Unfortunately I do not know. ZTE blocked the command fastboot boot so we couldn't backup the stock recovery.img we had no choice but to flash it. You can however backup system image in recovery and restore it later. This is the first thing that should be done before flashing root as well as a normal backup. If you restore your system image you can always OTA update through TWRP since it will be an untouched image. I do doubt that you can return to official OEM locked status unless they say it won't void warranty if you unlock it.
Sent from my 6045I using Tapatalk

ScaryBugThing said:
Thank you! One question, which I suppose isn't just limited to TWRP: Though we have TWRP (again, awesome!), we don't have a stock image or a way to get back to "locked, unrooted" status yet or the default ROM, right?
Click to expand...
Click to collapse
Nope, as far as I know. ZTE has to release the stock factory images. It's extremely difficult to create from a mere backup because it requires ZTE's signature verification.
Sent from my XT1095 using Tapatalk
---------- Post added at 12:16 PM ---------- Previous post was at 12:13 PM ----------
I'm really happy for the TWRP. Thank you man.
Sent from my XT1095 using Tapatalk

When I flash SuperSU 2.76 the phone just turns off, which is kind of strange. Has anyone else had any luck?

Got the same thing when I flash SuperSU

goalkeepr said:
When I flash SuperSU 2.76 the phone just turns off, which is kind of strange. Has anyone else had any luck?
Click to expand...
Click to collapse
allan1229 said:
Got the same thing when I flash SuperSU
Click to expand...
Click to collapse
After you try to install super su and the phone turns off boot back into recovery and
adb pull /cache/recovery/last_log

first time doing this. let me know if its right
http://www.mediafire.com/download/s988ykn9wws5a63/last_log

Unjustified Dev said:
1st config as I remember is for internal storage. Something about not allowing you to partition it.
2nd config is to remove mass storage support. TWRP supports mtp.
Sent from my 6045I using Tapatalk
Click to expand...
Click to collapse
Ah, that would make sense. I couldn't tell from the TWRP documentation if either one was general. The SD one is about partition, I just didn't know if applied to an external card (not that most people partition one since Windows doesn't allow it anyway). You definitely wouldn't want people partitioning their internal one.
It makes sense to get rid of UMS, as then TWRP couldn't read it while you're connected to the computer. It's unfortunate they names it USB rather than UMS then. Thanks.

Unjustified Dev said:
Prerequisites:
* Unlocked bootloader Guide Here
Installation:
Code:
fastboot flash recovery twrp-3.0.2-0-a2017u.img
fastboot reboot
To enter recovery:
* Power + volume up
Code:
adb reboot recovery
Click to expand...
Click to collapse
I'm confused I connect my phone and go into command prompt and do the first command fastboot flash recovery twrp-3.0.2-0-a2017u.img enter and all I get is waiting on device am I doing something wrong?

Database Develop

welcome