Here we go!!!
TWRP 2.8.6.0 for BigPart devices only! - Big thanks to @Schischu for making this possible
Download:
Flashable Zip (In Recovery): https://www.androidfilehost.com/?fid=23991606952607491
Flashable Img (In Fastboot): http://duckbox.info/android/recovery/recovery.twrp.2.8.6.0.bigPart_2.img.tar.bz2
TWRP 2.8.1.0 for BigPart devices only!
Download:
Flashable Zip (In Recovery): https://www.androidfilehost.com/?fid=95784891001606053
Depreciated 2.8.0.0
Flashable Zip (In Recovery): https://www.androidfilehost.com/?fid=23622183712473407
Flashable Img (In Fastboot): https://www.androidfilehost.com/?fid=23622183712473406
TWRP 2.8.0.0 for Non-BigPart devices only!
Download:
Flashable Zip (In Recovery): https://www.androidfilehost.com/?fid=95784891001604345
Changes:
2.8.6.0
-Fix daylight savings time rules for USA and Europe (_that)
-Allow mulitple overlays for popup boxes (Dees_Troy)
-Add pattern style password entry for decrypt (Tassadar)
-Keyboard improvements (_that)
-Update AOSP base to 5.1 (Dees_Troy)
-Reduce theme count to 5 and rely on scaling (Dees_Troy)
-Various scaling improvements (Dees_Troy)
-Improved handling of resources in the GUI (_that)
-Make scroll bar size proportional to list size (_that)
-Allow scoll lists to render without a header (_that)
-Make console scroll per pixel with kinetic scrolling (_that)
-Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
-Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
2.8.5.0
-Scale the GUI - TWRP can read the theme’s resolution and scale it up or down to fit the theme to your screen’s resolution
-Backups can now be cancelled while the backup is in progress (does not include restore because we don’t want to leave your device in
a bad state)
-Improve thread handling and move input handling into the main rendering thread to improve stability
-Make MTP work even if unplugged and plugged back in
-Unify scrollable list code and make kinetic scrolling feel more natural
-Fix handling of mapped zip files for OTA updates (CM12 updater)
-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
-Other small fixes and improvements
2.8.4.0
-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
-Fix some MTP related crashes and bugs
-Eliminate TWRP toggling USB IDs during boot if MTP is enabled
-Fix various adb sideload issues
-Improve threading of actions
-Eliminate separate thread for screen timeout
-Update libblkid to 2.25.0
-Use power button as back button on watch themes for easier navigation
-Add mutex locking to data manager
-Improve custom theme handling on encrypted devices
-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches
with round screens
2.8.3.0
-MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
-MTP will now tell the host PC that storage is removed instead of disabling MTP completely
-MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
-Update and improve fix permissions and make fixing contexts optional
-Update SuperSU in TWRP to 2.40 and update install process
-Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
-Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
-Fix kernel panic during MTP start on some devices
-Support unicode fonts on devices with True Type Font support
-Fix slider value not showing sometimes (vibration settings page)
-Toggle MTP off during adb sideload to set correct USB IDs
-Reduce library requirements for 5.0 L decrypt
-Other minor fixes and improvements
2.8.2.0
-MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
2.8.1.0:
-MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
-TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
-Temperature support - thanks to bigbiff
-Various other bugfixes and tweaks
2.8.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
Regards!
new sticky please
Do we still have any hardcore xoomers who haven't upgraded to BigPart and want TWRP 2.8? I've made one (untested since I'm on BigPart).
@webeougher was going to be my tester but I sent it to him 2 days ago and hasn't replied so if anyone wants to test ping me and I'll send a link. If it is functional I'll publish it here.
Sorry, Matt, been working 14+ hours a day the last three days and I just wanted to actually put it through its paces and make sure nothing was broken. I haven't really flashed any roms with it because I'm staying with stock, but it did install with no issues and I was able to use it to flash a root package.
Sent from my XT1060 using XDA Free mobile app
matt4321 said:
Do we still have any hardcore xoomers who haven't upgraded to BigPart and want TWRP 2.8? I've made one (untested since I'm on BigPart).
@webeougher was going to be my tester but I sent it to him 2 days ago and hasn't replied so if anyone wants to test ping me and I'll send a link. If it is functional I'll publish it here.
Click to expand...
Click to collapse
Matt4321, I installed TWRP 2.8 for a couple weeks ago and everything flash over him junctional. Feel free to report here (Bigpart)
Sent from Tapatalk MZ601 - TeamEOS 4.4.4 Kitkat nightlies
Update to TWRP 2.8.1.0:
This is only for BigPart users, I'll update Non-BigPart in the coming days when I have some time.
Changes:
-MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
-TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
-Temperature support - thanks to bigbiff
-Various other bugfixes and tweaks
Regarding adding Temperature support, this currently is not working on Xooms (well my Xoom at least), if users can report if it works on theres.
This is due to the lack of the /sys/class/thermal/ directory and content. After some research and looking at documentation I think the thermal aspect needs to be added/enabled in the kernel (ref) . The thermal aspect may just be in a different location on the Xoom and then we can change the location of where the recovery thinks it is. I may be wrong with some of this, so if someone wants to chip in and advise that'd be great.
So this is mainly bug fixes and a change of font.
DL link or am I just not seeing it¿
hochoch said:
DL link or am I just not seeing it¿
Click to expand...
Click to collapse
In the OP
matt4321 said:
In the OP
Click to expand...
Click to collapse
@matt4321 hit my profile and email me when you can. I'm working on something (take a wild guess ;0) and I need some backup.
hochoch said:
DL link or am I just not seeing it¿
Click to expand...
Click to collapse
First post in hidden content
bigrushdog said:
@matt4321 hit my profile and email me when you can. I'm working on something (take a wild guess ;0) and I need some backup.
Click to expand...
Click to collapse
Hey @bigrushdog , email sent, got it from your PayPal donation section. Hope that's cool. If you want to converse via the xda PM function let us know
Recovery 2.8.1.0-BigPart
Matt4321,
Can I flash this recovery on Everest?
Thanks for all your work.
Albert52 said:
Matt4321,
Can I flash this recovery on Everest?
Thanks for all your work.
Click to expand...
Click to collapse
Yeah it should be fine, as long as it's not any of the Hong Kong versions it should work on wingray, stingray and everest
matt4321 said:
Yeah it should be fine, as long as it's not any of the Hong Kong versions it should work on wingray, stingray and everest
Click to expand...
Click to collapse
Thanks again.
Just flashed it and all works fine.
I hesitated to flash because the download file did not mentioned Everest
Albert52 said:
Thanks again.
Just flashed it and all works fine.
I hesitated to flash because the download file did not mentioned Everest
Click to expand...
Click to collapse
That just because I have a wingray, probably should have named it xoom but oh well.
Wingray, stingray and everest are all the same internally other than RIL related stuff, so even roms can be cross flashed but you'd lose data connectivity in some circumstances
I dared to flash 2.8.1 stingray over 2.8.0 everest by trusted on you without asked for few day ago
Sent from Tapatalk MZ601 - TeamEOS 4.4.4 Kitkat nightlies
Can i use this version to make bigpart repartitioning?
mrbreit said:
Can i use this version to make bigpart repartitioning?
Click to expand...
Click to collapse
Just flashing a bigpart recovery will not repartition the device for you. You must follow the instructions in the resource centre which is in the development section
matt4321 said:
Just flashing a bigpart recovery will not repartition the device for you. You must follow the instructions in the resource centre which is in the development section
Click to expand...
Click to collapse
Matt, this 2.8.1.0 recovery is working great for me, but I do have a question in case this ever happens to me (although I'm not sure how this would happen). I noticed the following post in the CM11 string and wondered if he could just flash TWRP over CWM. Since he thought he still had big part would it be possible to change recoveries or would that really mess things up?
Quote:
Originally Posted by Kingsman1
Hey Schischu, day before yesterday,I was informed by my SU software that I needed to upgrade the SU. I went ahead and did it. During this upgrade I was told that there was a problem with my root and I was told it to repair it. After this was finished, at some point I went into recovery, only to discover that my TWRP recovery has been replaced with a CWM recovery. It doesn't appear to have modified my Big-Part partition Xoom in any way except that pressing the on/off button is very difficult to work with to accomplish any task during recovery. I'm not real comfortable with this particular recovery. How do I reinstall my TWRP without messing up my Big-Part Partitioning?
I know this reveals that there are areas where I don't have expertise, but I know that if anyone knows this system it would be you.
Thanks Schischu
Hi, I am using the recovery(big part), all is good except the back and home button is unresponsive. Any idea? Thanks.
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.
Ahh I'm in heaven now. I flashed it using goo manager. One click and it was installed in like 2 minutes. Thanks for this recovery. Best imo
1st! ... Q...
What if I have an existing CWM recovery, can I just flash this blob over on top of it with fastboot or will I need to flash back to stock recovery?
TheExpertNoob said:
1st! ... Q...
What if I have an existing CWM recovery, can I just flash this blob over on top of it with fastboot or will I need to flash back to stock recovery?
Click to expand...
Click to collapse
It'll overwrite CWM.
Awesome .
Q: Does the File System Size Check takes that long ?
Sent using Chanook 300
awww snap. thank you so much for this!
Thanks so much! I will definitely jump on when external SD is supported.
thx
Glad to see this ported to our tf300...and easy to install with goo manager!
Very nice Thanks a bunch.
We pushed out an update to v. 2.1.5 to fix a bug with zip installs, please update via the website or goo manager.
Woot awesome! Thanks for the update.
Sent from my ADR6300 using Tapatalk 2
Must admit that I wasn't keen on installing a different recovery image but as CWM isn't restoring my kernels between standard rom and CM9 I thought I'd give it a go.
So far so good.
Waiting for build 3 of CM9 to properly test it.
Is there any real advantage to using TWRP instead of CWM? Or is it just a personal preference?
camblue said:
Is there any real advantage to using TWRP instead of CWM? Or is it just a personal preference?
Click to expand...
Click to collapse
CMW isnt restoring kernels so its a right ball ache to revert the tablet to standard again.
And if you are testing CM9 nightly and then changing back its too much.
TWRP says it can fully restore my standard image after testing CM9.
Hmmm might have to give it a whirl and give up my long standing relationship with CWM.
Northern-Loop said:
CMW isnt restoring kernels so its a right ball ache to revert the tablet to standard again.
And if you are testing CM9 nightly and then changing back its too much.
TWRP says it can fully restore my standard image after testing CM9.
Click to expand...
Click to collapse
camblue said:
Hmmm might have to give it a whirl and give up my long standing relationship with CWM.
Click to expand...
Click to collapse
Yeah I was the same but seems alright - Big test will be the next CM9 build.
---------- Post added 26th May 2012 at 12:10 AM ---------- Previous post was 25th May 2012 at 11:26 PM ----------
Seems we can't delete backups inside recovery? Is it okay to delete them in a file manager?
Not sure what's up, maybe kernel version still not being restored properly, but Wi-Fi still doesn't work when restoring back to a stock ROM from CM9.
Berzerker7 said:
Not sure what's up, maybe kernel version still not being restored properly, but Wi-Fi still doesn't work when restoring back to a stock ROM from CM9.
Click to expand...
Click to collapse
Go into settings then about and see what it says about kernel, post details here.
Did you flash build 1 or 2? Should be fixed in build 2 of CM9
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Northern-Loop said:
Go into settings then about and see what it says about kernel, post details here.
Did you flash build 1 or 2? Should be fixed in build 2 of CM9
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Click to expand...
Click to collapse
I have the same issue and I used build 2.. When restoring back, even from trwp backup,
Kernel 2.6.39.4_cm9-ga1dbdc6
[email protected]#1
It's looks to be retaining th kernel..
Very slow as well.. Did I miss something in my backup process?
Sent from my iPad using Tapatalk HD
Server is taking too long to respond
I'll try again later...
EDIT: Finally got the Blob and flashed it through Terminal
Currently backing up the stock ROM before testing out CM9 Build 3!
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
This build should work for a5dug, a5ul, and a5u variants.
Device page on our website with instructions for a manual install.
Download page with current and previous versions.
Thanks to jmztaylor for porting TWRP and making it officially supported on the Desire 816!
thnx for thew awesome work keep supporting this awesome device :good:
Dees_Troy said:
This build should work for a5dug, a5ul, and a5u variants.
Device page on our website with instructions for a manual install.
Download page with current and previous versions.
Thanks to jmztaylor for porting TWRP and making it officially supported on the Desire 816!
Click to expand...
Click to collapse
Official support...!!!!! Awesome...
Thanks a lottttttttt....
But con you confirm for A5DWG?
jithumon said:
Official support...!!!!! Awesome...
Thanks a lottttttttt....
But con you confirm for A5DWG?
Click to expand...
Click to collapse
does the DWG have a different partition layout than the other? if not then it will work
jmz said:
does the DWG have a different partition layout than the other? if not then it will work
Click to expand...
Click to collapse
I think its same....Unofficial port was working well.
jithumon said:
I think its same....Unofficial port was working well.
Click to expand...
Click to collapse
I can't download from official page...can you upload to other web?
calors said:
I can't download from official page...can you upload to other web?
Click to expand...
Click to collapse
Dude.... Ask dev's not me...
I'm not the developer.
calors said:
I can't download from official page...can you upload to other web?
Click to expand...
Click to collapse
See link below.
https://docs.google.com/file/d/0ByTAJ7v5eoN7bFN2R21kbTAwTE0/edit?usp=docslist_api
support single sim ?
support single sim ?
There is no 'a5' in TWRP manager(phone list)
ajeshmanu said:
There is no 'a5' in TWRP manager(phone list)
Click to expand...
Click to collapse
Same prob here..
Thanks for the update to 2.8 ..
But, MTP is not working..
With the a5ul the touch does not work you can choose to install but then do not go back and if it freezes you can not unlock
Sent from my HTC Desire 816 Single sim using XDA Free mobile app
my bro got this HTC 816 dual sim what its name A5 ? is it supported ?
its important to me whats name of dual sim version of it to download and flash or not
swipe to unlock not function. I am stuck there. What should I do to solve this problem?
smartzac said:
swipe to unlock not function. I am stuck there. What should I do to solve this problem?
Click to expand...
Click to collapse
Are you on single sim? If so, there's a lot of problems like this on single sim. If not, just disable the screen lock feature in TWRP settings.
FoxyDrew said:
Are you on single sim? If so, there's a lot of problems like this on single sim. If not, just disable the screen lock feature in TWRP settings.
Click to expand...
Click to collapse
Yes I am on 816x single sim. The back button also not function.
smartzac said:
Yes I am on 816x single sim. The back button also not function.
Click to expand...
Click to collapse
Then this TWRP isn't for your phone. Re-flash CWM.
FoxyDrew said:
Then this TWRP isn't for your phone. Re-flash CWM.
Click to expand...
Click to collapse
Already flash back to CWM again.
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.
PSA: DO NOT restore EFS backups made with TWRP 3.0.2-1 as there is a bug in that version that affects how the backup is made. Backups of EFS made with TWRP 3.0.2-1 are invalid and should be discarded. Also, seriously people, do not restore EFS unless you absolutely know that you need to.
Device specific page including instructions for a manual install
Download links for current and past versions of TWRP
Sweet.
nice can't wait to get my nexus 6p tomorrow
Awesome to see you here!
If someone grabs me a boot.img I can get us working decrypted kernel in about 2 minutes
DespairFactor said:
If someone grabs me a boot.img I can get us working decrypted kernel in about 2 minutes
Click to expand...
Click to collapse
Still need a boot.img?
kingmikel said:
Still need a boot.img?
Click to expand...
Click to collapse
Yes sir
Sent from Nexus 5X in the Despair filled Dark Side
@DespairFactor Here you have them.
http://downloadmirror.co/android/K3/mda89d-boot.img
http://downloadmirror.co/android/K4/mdb08k-boot.img
Note for everybody else: these are stock boot images, not modified ones. For that, look out for DespairFactor's posts.
itskapil said:
@DespairFactor Here you have them.
http://downloadmirror.co/android/K3/mda89d-boot.img
http://downloadmirror.co/android/K4/mdb08k-boot.img
Note for everybody else: these are stock boot images, not modified ones. For that, look out for DespairFactor's posts.
Click to expand...
Click to collapse
Why are we using two? Are devices not getting OTA to the latest build?
Sent from Nexus 5X in the Despair filled Dark Side
DespairFactor said:
Why are we using two? Are devices not getting OTA to the latest build?
Sent from Nexus 5X in the Despair filled Dark Side
Click to expand...
Click to collapse
Um, mdb08k would do. I just thought you might need them, so.. anyway, mdb08k OTA is definitely rolling out, so this only should more than suffice.
DespairFactor said:
Yes sir
Sent from Nexus 5X in the Despair filled Dark Side
Click to expand...
Click to collapse
Here you go. The stock MDB08K boot.img
http://1drv.ms/1OXgbJR
DespairFactor said:
Why are we using two? Are devices not getting OTA to the latest build?
Sent from Nexus 5X in the Despair filled Dark Side
Click to expand...
Click to collapse
They're for the two different variants (MDA89D & MDB08K), so I'm guessing they'll both need to be modified.
kingmikel said:
Here you go.
http://1drv.ms/1OXgbJR
Click to expand...
Click to collapse
Removed verity checks and removed forced encryption, it will be uploaded in this link shortly http://renderserver.net/?dir=devs/DespairFactor/angler
Heisenberg said:
They're for the two different variants (MDA89D & MDB08K), so I'm guessing they'll both need to be modified.
Click to expand...
Click to collapse
The file size is too small for those two
Until we get a modified boot.img from @Chainfire, there's no way to root correct?
kingmikel said:
Until we get a modified boot.img from @Chainfire, there's no way to root correct?
Click to expand...
Click to collapse
I can get it working possibly, just let me get my device tomorrow. Keep in mind I am doing all of this stuff remotely.
kingmikel said:
Until we get a modified boot.img from @Chainfire, there's no way to root correct?
Click to expand...
Click to collapse
Read..... the few posts literally right before yours are discussing this...
Heisenberg said:
Read..... the few posts literally right before yours are discussing this...
Click to expand...
Click to collapse
it may not be that cut and dry, we may need to mod permissions, or disable selinux. I will see when I get my device if this doesn't work by itself.
kingmikel said:
Here you go.
http://1drv.ms/1OXgbJR
Click to expand...
Click to collapse
DespairFactor said:
Removed verity checks and removed forced encryption, it will be uploaded in this link shortly http://renderserver.net/?dir=devs/DespairFactor/angler
The file size is too small for those two
Click to expand...
Click to collapse
It's probably pretty important to note which variant this boot.img came from.
Heisenberg said:
Read..... the few posts literally right before yours are discussing this...
Click to expand...
Click to collapse
@DespairFactor mentioned removing encryption from it, but I think it needs the patched sepolicy for supersu to work.
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
---------- Post added at 11:13 PM ---------- Previous post was at 11:12 PM ----------
Heisenberg said:
It's probably pretty important to note which variant this boot.img came from.
Click to expand...
Click to collapse
Fixed! Thanks
These builds are UNOFFICIAL , But are built from Omni latest 5.1.1 source, stock boot.img and stock recovery.img for our device ( NOT A PORT )......Thus making these builds of TWRP the most stable recovery for our device. And HIGHLY prefer using these builds for all your flashing needs.!!!
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.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
CHANGELOG for 2.8.6.0:
-Fix daylight savings time rules for USA and Europe (_that)
-Allow mulitple overlays for popup boxes (Dees_Troy)
-Add pattern style password entry for decrypt (Tassadar)
-Keyboard improvements (_that)
-Update AOSP base to 5.1 (Dees_Troy)
-Reduce theme count to 5 and rely on scaling (Dees_Troy)
-Various scaling improvements (Dees_Troy)
-Improved handling of resources in the GUI (_that)
-Make scroll bar size proportional to list size (_that)
-Allow scoll lists to render without a header (_that)
-Make console scroll per pixel with kinetic scrolling (_that)
-Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
-Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
CHANGELOG for 2.8.5.0:
-Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-Improve thread handling and move input handling into the main rendering thread to improve stability
-Make MTP work even if unplugged and plugged back in
-Unify scrollable list code and make kinetic scrolling feel more natural
-Fix handling of mapped zip files for OTA updates (CM12 updater)
-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
-Other small fixes and improvements
CHANGELOG for 2.8.4.0:
-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
-Fix some MTP related crashes and bugs
-Eliminate TWRP toggling USB IDs during boot if MTP is enabled
-Fix various adb sideload issues
-Improve threading of actions
-Eliminate separate thread for screen timeout
-Update libblkid to 2.25.0
-Use power button as back button on watch themes for easier navigation
-Add mutex locking to data manager
-Improve custom theme handling on encrypted devices
-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
DOWNLOAD:
Download Page for TWRP Builds
Download Page For TWRP 3.0.0-1 and Above
BUGS:
- None So Far
SUPPORT:
SOURCES:
Will Post SOON.!!
CREDITS:
@Dees_Troy - For Guide Found HERE
@marduk - For Sources, found HERE
XDA:DevDB Information
twrp-eyeul, Tool/Utility for the HTC Desire Eye
Contributors
xXminiWHOOPERxX
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-05-01
Created 2015-12-29
Last Updated 2016-05-01
reserved
Not working on s-on ...
It will be great if you made it working on s-on phones too.
thank you for your works
What's the differente between this and the 2.8.7.1 posted new stock ui??
karo222 said:
Not working on s-on ...
It will be great if you made it working on s-on phones too.
Click to expand...
Click to collapse
Take the plunge to s-off. I do all my work s-off so.. figuring out what causes your phone to not boot it means I have to go back s-on.. which I won't.. sorry. Plus I'll be releasing a few new things that require s-off to do... sorry again.
fabrizio b92 said:
thank you for your works
What's the differente between this and the 2.8.7.1 posted new stock ui??
Click to expand...
Click to collapse
2.8.7.1 and the other recoveries in that thread are all ported from m8.... this one is purely built for our device.. I will be trying to get it to become official.
Sent from my HTC Desire EYE using Tapatalk
xXminiWHOOPERxX said:
Take the plunge to s-off. I do all my work s-off so.. figuring out what causes your phone to not boot it means I have to go back s-on.. which I won't.. sorry. Plus I'll be releasing a few new things that require s-off to do... sorry again.
Sent from my HTC Desire EYE using Tapatalk
Click to expand...
Click to collapse
There is no way to s-off desire eye like m8 or m7 phones and we can't s-off our phone here like other places.
Can we s-off eye with sunshine 3 ?? It cost 25$
I says that it supports htc desire eye
https://docs.google.com/spreadsheets/d/1fGIQKchHaWzVQpAAkPFaE4nEVVTn_btuKybcfZp_lXM/edit#gid=0
karo222 said:
There is no way to s-off desire eye like m8 or m7 phones and we can't s-off our phone here like other places.
Can we s-off eye with sunshine 3 ?? It cost 25$
I says that it supports htc desire eye
https://docs.google.com/spreadsheets/d/1fGIQKchHaWzVQpAAkPFaE4nEVVTn_btuKybcfZp_lXM/edit#gid=0
Click to expand...
Click to collapse
Go to their actual page and download it. Pay $25 and enjoy your modding needs lol
Sent from my HTC Desire EYE using Tapatalk
PHP:
xXminiWHOOPERxX said:
Go to their actual page and download it. Pay $25 and enjoy your modding needs lol
Sent from my HTC Desire EYE using Tapatalk
Click to expand...
Click to collapse
Best $25 i have ever spent for my HTC m8 lool.
This is a nice surprise! thanks!
61 downloads, 2 thanks, lol
S-on
karo222 said:
Not working on s-on ...
It will be great if you made it working on s-on phones too.
Click to expand...
Click to collapse
My Desire Eye is S-on and it works great.
William Of Astora said:
My Desire Eye is S-on and it works great.
Click to expand...
Click to collapse
How did you flash it??
Can you please tell me the procedure that you done.
Thanks
karo222 said:
How did you flash it??
Can you please tell me the procedure that you done.
Thanks
Click to expand...
Click to collapse
My Eye is s-on, too
I flash this recovery with WinDroid Universal Android Toolkit v2.6 , works fine, you can flash Kernels too
TWRP 3.0 has been released. Is it possible to have it on our desire eye?
Sent from my HTC Desire EYE using Tapatalk
Rouz. said:
TWRP 3.0 has been released. Is it possible to have it on our desire eye?
Sent from my HTC Desire EYE using Tapatalk
Click to expand...
Click to collapse
Working on it now!!! >
xXminiWHOOPERxX said:
Working on it now!!! >
Click to expand...
Click to collapse
Awesome, flashing right now to be updated to the very latest . I feel Sense 8 comming to our lives sometime soon with the M10.
Anyboday saw the leeak supposed pics/ It looks like an HTC A9....:S
Not Working
I have htc desire eye jw5.2 rom mm6.0.1, S-OFF and its not working for me same as the last version which still leave me to 2.8.5.0 and i am desperately trying to get to 3.0.0 please help me
karanm18 said:
I have htc desire eye jw5.2 rom mm6.0.1, S-OFF and its not working for me same as the last version which still leave me to 2.8.5.0 and i am desperately trying to get to 3.0.0 please help me
Click to expand...
Click to collapse
Which variant of Desire EYE?
xXminiWHOOPERxX said:
Which variant of Desire EYE?
Click to expand...
Click to collapse
EYE_TUHL ........... its an Asian Model and Unlocked
karanm18 said:
EYE_TUHL ........... its an Asian Model and Unlocked
Click to expand...
Click to collapse
Lollipop firmware? May need your stock boot.img
Sent from my HTC One_M8 using Tapatalk
xXminiWHOOPERxX said:
Lollipop firmware? May need your stock boot.img
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
No its on Marshmallow firmware and unfortunately i dont have stock boot.img is there any way i can get it
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Unofficial TWRP 3.0.2-8 for Elephone P9000
Mirror 1
INSTALLATION:
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 above
2) Reboot to TWRP
3) Hit Install and tap the "Install Image" 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
To install from SP Flash Tools:
1) Download scatter file attached to this post
2) Load scatter file into SPFT
3) Plug USB cable into device and computer
4) Press download in SPFT
5) Reboot device
BUGS:
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed.
XDA:DevDB Information
[RECOVERY] Unofficial TWRP for Elephone P9000, Tool/Utility for the Elephone P9000
Contributors
Jonny
Source Code: https://github.com/JonnyXDA/android_device_elephone_p9000/tree/Omni
Version Information
Status: Stable
Current Stable Version: 3.0.2-8
Stable Release Date: 2016-08-24
Created 2016-07-26
Last Updated 2016-09-11
FAQ:
Attention ROM Devs - You need to update your ROM's updater-script to use the correct by-name parts for this recovery, the old M2 ported one had this:
Code:
/dev/block/platform/mtk-msdc.0/by-name
The correct by-name parts for the Elephone P9000 are:
Code:
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name
DEVICE-SPECIFIC CHANGELOGS:
3.0.2-8:
-Updated Kernel to an early version of my DarkSense kernel
-Possible fix for F2FS support (if it doesn't work we have a few theories as to why)
3.0.2-7:
-Updated Kernel to Deepflex's flexy kernel for now (compatible with new preloader and lk images)
3.0.2-6:
-Updated prebuilt kernel to 20160715 firmware version
-Fixed MTP Mounting Issue
3.0.2-5:
-Updated prebuilt kernel to 20160628 firmware version
-Remove SuperSU from the recovery (doesn't fully support Android 6.0 ROM's)
-Cleanup and remove useless files
-Add Timezone data to TWRP, fixes some errors in recovery.log
-Increase default brightness slightly, was a bit too dim before
-Add ability to flash raw system.img files
3.0.2-4:
-Fix USB-OTG Mounting
3.0.2-3:
-Use Toybox mount and grep
3.0.2-2:
-Fully built from source for Elephone P9000 - unlike the other one which was ported (repacked recovery.img) from the Elephone M2
Current TWRP "bugs" for Elephone P9000:
NONE
Jonny said:
Current TWRP "bugs" for Elephone P9000:
NONE
Click to expand...
Click to collapse
:good:
---------- Post added at 10:19 PM ---------- Previous post was at 10:08 PM ----------
Pease upload in a different more android browser friendly host.
andy radical said:
:good:
---------- Post added at 10:19 PM ---------- Previous post was at 10:08 PM ----------
Pease upload in a different more android browser friendly host.
Click to expand...
Click to collapse
Done, the Mega link has been renamed to Mirror 1.
installed and everithing seem work good , language , vibr, brightns, need something to install now but im sure everything is fine .
The only missing feature is the battery meter , i don't know if you have it..
andy radical said:
installed and everithing seem work good , language , vibr, brightns, need something to install now but im sure everything is fine .
The only missing feature is the battery meter , i don't know if you have it..
Click to expand...
Click to collapse
Thanks, I'll look into it.
3.0.2-4:
-Fix USB-OTG Mounting
andy radical said:
installed and everithing seem work good , language , vibr, brightns, need something to install now but im sure everything is fine .
The only missing feature is the battery meter , i don't know if you have it..
Click to expand...
Click to collapse
Further info on the battery meter issue. I spoke to some of the guys over on the twrp freenode IRC channel and after a bit of experimentation it turns out that this is an issue with the way the kernel links to the battery level, some proprietary lib or bin is needed to help link them, at this moment in time I haven't a clue which one but I'll keep looking.
Does this work on P9000 Lite?
Jtig said:
Does this work on P9000 Lite?
Click to expand...
Click to collapse
No, once I'm happy with this I'll maybe look into making one for P9000 lite, but I'm vary wary of developing things for devices I do not own, as I can't test things.
3.0.2-5:
-Updated prebuilt kernel to 20160628 firmware version
-Remove SuperSU from the recovery (doesn't fully support Android 6.0 ROM's)
-Cleanup and remove useless files
-Add Timezone data to TWRP, fixes some errors in recovery.log
-Increase default brightness slightly, was a bit too dim before
-Add ability to flash raw system.img files
Jonny said:
No, once I'm happy with this I'll maybe look into making one for P9000 lite, but I'm vary wary of developing things for devices I do not own, as I can't test things.
Click to expand...
Click to collapse
What's so different about P9000L? You can even run P9000 ROMs on P9000L with fixed buildprop
Jtig said:
What's so different about P9000L? You can even run P9000 ROMs on P9000L with fixed buildprop
Click to expand...
Click to collapse
I just don't particularly like doing blind builds, never have done.
Hi....can I update from TWRP 3.0.0.0 by Marsapa?
I have installed this one......
Thanks
fatalhh said:
Hi....can I update from TWRP 3.0.0.0 by Marsapa?
I have installed this one......
Thanks
Click to expand...
Click to collapse
If you have installed this one then you have updated the recovery, unless you're asking something else?
Sent from my Elephone P9000 using XDA Labs
Jonny said:
If you have installed this one then you have updated the recovery, unless you're asking something else?
Sent from my Elephone P9000 using XDA Labs
Click to expand...
Click to collapse
No more question at all.....I asked because I didn't know about compatibility between both....when I connect my phone to the Pc ..this recognize the phone as M2.....will it change with this update?
Thanks
fatalhh said:
No more question at all.....I asked because I didn't know about compatibility between both....when I connect my phone to the Pc ..this recognize the phone as M2.....will it change with this update?
Thanks
Click to expand...
Click to collapse
Ok you seem to be getting confused, there is no incompatibility between the recoveries, the recovery is contained within the .img file so when you are flashing a new recovery, you are completely replacing the old one, it doesn't matter what the old one was.
Sent from my Elephone P9000 using XDA Labs
Jonny said:
Ok you seem to be getting confused, there is no incompatibility between the recoveries, the recovery is contained within the .img file so when you are flashing a new recovery, you are completely replacing the old one, it doesn't matter what the old one was.
Sent from my Elephone P9000 using XDA Labs
Click to expand...
Click to collapse
Really confusing my friend.....I am newbie in the side of rooting....flashing....etc.....and reading a lot to learn.....everytime I flash something my stomach get butterflys.....like when you are in love:laugh::silly:
Thanks mate
3.0.2-6:
-Updated prebuilt kernel to 20160715 firmware version
-Fixed MTP Mounting Issue
Jonny said:
3.0.2-6:
-Updated prebuilt kernel to 20160715 firmware version
-Fixed MTP Mounting Issue
Click to expand...
Click to collapse
Hi @Jonny, when I backup with twrp i must choose every voice or i must untick system image? Thank you
Inviato dal mio P9000 utilizzando Tapatalk