Related
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Good work, looks wonderful! I will wait for the 720p GNexus version.
Awesome will give it a try when the small bugs are sorted out!
Sent from my Galaxy Nexus using XDA
Pretty nice. It's usable.. Can't wait till all the bugs r gone. Especially the wait time it takes to boot to recovery.. But very nice work tho.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-6
Finally some development at the recovery site, i was spoiled with the 4ext recovery's at my HTC phones .
Thanks!
melvie said:
Finally some development at the recovery site .
Thanks!
Click to expand...
Click to collapse
yeah,agree with that!it seems soo user-friendly...i want to try it right now!thanks OP,waited a lot for that!!!
Thanks guys, the tablet version also looks very good.
Fresh air around these parts
This looks nice.. I will for sure try it out, but waiting until it's more stable
WOW it's amazingggg .
Definitely looks promising; but came across an issue and the link to the issues log seems to be down.
While trying to flash an update (CM9 Unofficial) the installation fails; however I can easily flash the update using Clockworkmod.
Here is the pastebin link for the log file of the issue: GSM Galaxy Nexus TRWP2 Log
omg that's the only thing i missed from the nexus s. finally on gnex too!
thanks very much for that.
mykegger said:
Definitely looks promising; but came across an issue and the link to the issues log seems to be down.
While trying to flash an update (CM9 Unofficial) the installation fails; however I can easily flash the update using Clockworkmod.
Here is the pastebin link for the log file of the issue: GSM Galaxy Nexus TRWP2 Log
Click to expand...
Click to collapse
Thank you for the log (so many people forget the log!). I see the issue and it should be a pretty easy fix. My Galaxy Nexus arrives today so I should have a fix for this and have an updated theme that fills the whole screen sometime tomorrow.
the usb mount function does nothing, is it because of galaxy nexus internal memory structure (mtp, etc)?
i assume it will be removed completely in further versions like it was with cwm?
i still hope in some workaround that lets me add/remove files from recovery without adb
Dees_Troy said:
Thank you for the log (so many people forget the log!). I see the issue and it should be a pretty easy fix. My Galaxy Nexus arrives today so I should have a fix for this and have an updated theme that fills the whole screen sometime tomorrow.
Click to expand...
Click to collapse
Thanks! Looking forward to the fixes.
Sent from my Galaxy Nexus using xda premium
Updated builds available.
mykegger said:
Thanks! Looking forward to the fixes.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The issue you reported should be fixed in the new build. Let me know if you have any problems. Thanks.
Dees_Troy said:
Updated builds available.
The issue you reported should be fixed in the new build. Let me know if you have any problems. Thanks.
Click to expand...
Click to collapse
Great job on this one; works perfect and haven't had any problems so far. Thanks
Man this is the sickest......thanks man!!!
Where can I find themes for this
Sent from my Galaxy Nexus using Tapatalk 2 Beta-6
I tried doing a backup and it says its completed right after u start but the back up is still going and I'm not sure if this is by design but while the backup is going u can still hit the back button. In my previous experiences u can't do anything until the backup is finished.
Edit: after a few reboots its working fine now.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-6
There were a few problems with installing zips on the builds I uploaded earlier. If you aren't sure, go ahead and re-update just in case. Sorry.
Dees_Troy said:
There were a few problems with installing zips on the builds I uploaded earlier. If you aren't sure, go ahead and re-update just in case. Sorry.
Click to expand...
Click to collapse
I thought it was something I was doing or incomplete download. Thanks.
Default [RECOVERY] [10/5/13] TWRP 2.6.3.2 - TeamWin Recovery Project
TeamWin is proud to present TWRP 2.6.3.2 for the Galaxy Note 3 (T-Mobile)!
Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo
Special credits:
Dees_Troy for quick porting.
agrabren for writing the initial TWRP GUI code.
AssassinsLament and Dees_Troy for initial TWRP code
CRudner and Reb0rn for testing
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project 2.6, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout – true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups – now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for 2.6 features
Older Releases
What's new in 2.4:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes
-Support for exFAT formatted sdcards
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Other minor bugfixes and improvements
-cm10.1 build support
What's new in 2.3:
-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.
What's new in 2.2:
On-screen keyboard! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
Name new backups before creation and rename existing backups
Rename files and folders in the file manager
Pseudo-terminal emulator
Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
Simplified XML layout support between resolutions
Added dual storage selection radio buttons to zip install, backup, and restore pages
Improved zip install compatibility
Updated update-binary source code
Numerous small bug fixes and improvements
What was new in 2.1:
Zip queuing as seen in TWRP 1.1.x is back
Slider control (swipe to confirm most actions aka swipe to wipe)
Lockscreen (with slider to unlock)
Basic file manager (copy, move, delete, and chmod any file)
Added support for devices with /data/media (most Honeycomb tablets, new ICS devices like Galaxy Nexus)
Displays sizes of each partition in the backup menu
Added listbox GUI element (currently used for listing time zones)
Updated stock XML layouts to be more consistent and easier to port to different resolutions
XML layout files are significantly smaller
Partitions available backup are more accurate for some devices
Removed unneeded error messages (/misc errors, unable to stat sd-ext, etc.)
Fixed a bug with blkid detection code
Fixed bug where a blank line was inserted between every line of text during zip installs
Fixed a bug during zip installs where an invalid zip would cause TWRP to get stuck in the zip install
Added setting for themers to toggle simulation mode to make theming easier
New devices added - Galaxy Nexus GSM & CDMA (preview only, manual install), Acer Iconia Tab A500, HTC Vivid, Motorola Defy
Added support for .jpg images in the theme engine
Changed images for stock tablet theme - makes tablet builds about 500KB smaller
Removed unneeded non-GUI images from GUI - makes all builds about 100KB smaller
In addition to the above new features, TWRP 2.2 features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
Known Issues:
CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it
Source Code:
GitHub - https://github.com/TeamWin/
Gerrit Instance - http://review.teamw.in
If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
n7100 Device Config: https://github.com/bigbiff/android_device_samsung_n7100
Kernel: https://github.com/bigbiff/kernel_samsung_sgh-i317
DOWNLOAD:
All official devices are listed at the top of the page on the Team Win website. Search for the device in the textbox.
http://teamw.in/project/twrp2
Support:
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers
XDA:DevDB Information
TWRP, a Tool/Utility for the Samsung Galaxy Note 3
Contributors
bigbiff, Dees_Troy
Version Information
Status: Testing
Created 2013-10-05
Last Updated 2013-10-05
Reserved
Reserved 2
good.
using your work on note 2 and now on note3. :good:
But can i use this (tmobile version) on my french mobile (LTE SM-N9005) without problem??
someone have a workong link for 2.6.3.2 version?
does this work on SM-N900?
kenzolo said:
someone have a workong link for 2.6.3.2 version?
Click to expand...
Click to collapse
here http://teamw.in/project/twrp2/198
micky387 said:
here http://teamw.in/project/twrp2/198
Click to expand...
Click to collapse
are you able to download 2.6.3.2 version?
Follow this link.
For odin method http://goo.im/devs/OpenRecovery/hltetmo
Envoyé depuis mon SM-N9005 avec Tapatalk 4
micky387 said:
Follow this link.
For odin method http://goo.im/devs/OpenRecovery/hltetmo
Envoyé depuis mon SM-N9005 avec Tapatalk 4
Click to expand...
Click to collapse
come on micky I understand...but I can't downlod 2.6.3.2 version (404 error page note found)
404 - Not Found
micky387 said:
Follow this link...
Click to expand...
Click to collapse
404 - Not Found
Are all hlte devices supported it is only htletmo listed on the official device list
Sent from my SM-N9005 using Tapatalk 4
Works fine on N9008, thank you very much, finally a decent recovery
Using 2.6.3.1, 2.6.3.2 download gives error 404 as someone else said.
I confirm that I cannot download 2.6.3.2 either.
There are two links in the list:
openrecovery-twrp-2.6.3.2-hltetmo.tar
penrecovery-twrp-2.6.3.2-hltetmo.tar (without the "o" in the filename)
.. but none works, its probably gone from the server or the name has been somehow changed without updating the links too.
However, questions for those who tried the Recovery - did you try the root the phone using the recovery? And can you delete/reset all traces of root or custom modification from the device in case you'll need to use the warranty ? Thank you for quick reply.
Yeah the devs derped the upload of 2.6.3.2 - neither of the two downloads (typo and no typo) work, both are 404. Been like that since yesterday afternoon. Running 2.6.3.1 for now.
---------- Post added at 10:16 AM ---------- Previous post was at 10:15 AM ----------
wencel said:
I confirm that I cannot download 2.6.3.2 either.
There are two links in the list:
openrecovery-twrp-2.6.3.2-hltetmo.tar
penrecovery-twrp-2.6.3.2-hltetmo.tar (without the "o" in the filename)
.. but none works, its probably gone from the server or the name has been somehow changed without updating the links too.
However, questions for those who tried the Recovery - did you try the root the phone using the recovery? And can you delete/reset all traces of root or custom modification from the device in case you'll need to use the warranty ? Thank you for quick reply.
Click to expand...
Click to collapse
Once you modify ANY of the phone's partitions, you trip the KNOX_WARRANTY_VOID flag in the bootloader.
With twrp 2.6.3.1...anyone who has sucessfuly created backup and restored without issues? Just asking becoz the cwm recovery still cannot restore properly.
[email protected] from Bad Ass Note III-SM-N9500
Thanks for your hard work! Still waiting on a SM-N9005 version. Not really sure what's required for that or if the above is compatible, but I'm happy to wait until goomanager has a compatible one =)
Is this only ccompatible with the T-Mobile variant and do backup and restore work without problems?
dark_dude said:
Is this only ccompatible with the T-Mobile variant and do backup and restore work without problems?
Click to expand...
Click to collapse
Just downloadet the TWRP 2.6.3.2 file from Goo.im
inffy said:
Just downloadet the TWRP 2.6.3.2 file from Goo.im
Click to expand...
Click to collapse
Is this link？
http://goo.im/devs/OpenRecovery/hltetmo/openrecovery-twrp-2.6.3.2-hltetmo.tar
[RECOVERY] [4/5/16] TWRP 3.2.3-0 - TeamWin Recovery Project
TeamWin is proud to present TWRP 3.2.3-0 for the Samsung Galaxy S6!
Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for new features
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit for TWRP Official Device Configs - http://gerrit.twrp.me
Gerrit Instance - http://gerrit.omnirom.org
If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
zeroflte Device Config: TBD
Kernel: TBD
DOWNLOAD:
All official devices are listed at the top of the page on the Team Win website. Search for the device in the textbox.
http://twrp.me
Support:
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers
Changelog
Please see https://twrp.me for changelogs.
3.0.2-2
- Fix booting on mm
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.
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
3.0.0.1
-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
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 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!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links.
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 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!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links.
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 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!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links.
2.8.7.2
Fix MTP copy/moves.
2.8.7.1
- Unify and fix kernel booting for 5.0.2 and 5.1.1
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)
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.
2.8.6.2
- fix OTG
2.8.6.1
- fix adb
2.8.6.0
- 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)
Fix Deep Sleep from Chainfire:
http://forum.xda-developers.com/showpost.php?p=60383471&postcount=49
This is for the S6 Edge as well?
Project X-Ray said:
This is for the S6 Edge as well?
Click to expand...
Click to collapse
It should work for all S6 devices since they are all using the same SOC.
However the asserts are not working for every device. I am deciding on whether I should use a unified init but I will need lots of help from users for testing etc.
flashed it by odin
mobile running good but not going into recovery
and now it is stuck boot when pressed vol+ and menu and power to go in recovery
G920F
Project X-Ray said:
This is for the S6 Edge as well?
Click to expand...
Click to collapse
Unfortunatly it doesn't work on my edge(SM-G925F), boots in to recovery but the screen is all messed up, just shades of green,
Thanks for porting this ! cant wait till it works on the edge.
a0007 said:
flashed it by odin
mobile running good but not going into recovery
and now it is stuck boot when pressed vol+ and menu and power to go in recovery
G920F
Click to expand...
Click to collapse
Can you get /proc/last_kmsg please?
bigbiff said:
Can you get /proc/last_kmsg please?
Click to expand...
Click to collapse
I install new rom by odin without wipe
Last_kmsg
https://app.box.com/s/lccif3dhyfn0gohjwyo3wk868muvub8u
Sent from my SM-G920F
a0007 said:
flashed it by odin
mobile running good but not going into recovery
and now it is stuck boot when pressed vol+ and menu and power to go in recovery
G920F
Click to expand...
Click to collapse
same problem here ,
& TWRP manager app doesn't have the S6 as a supported device ,
& the dd method stuck on boot logo
G920F
tiboric said:
Unfortunatly it doesn't work on my edge(SM-G925F), boots in to recovery but the screen is all messed up, just shades of green,
Thanks for porting this ! cant wait till it works on the edge.
Click to expand...
Click to collapse
@bigbiff - Same issue here.
Samsung just published kernel source code for S6 920 and S6 Edge 925 http://www.androidauthority.com/galaxy-s6-s6-edge-kernel-source-code-600528/
flashed it on g920p
now im stuck in recovery and the touchscreen doesnt work
SM-G925T Galaxy S6 Edge T-Mobile after installing reboot to recovery I get a black screen. I do have access to the SDCard but can't seem to find the recovery.log. OP let me know if I can help I bought this phone to use for development and I can just restore the recovery no problem. Thanks.
PS ADB device is offline.
So it seems the Edge has it's own configuration as well as the F series international.
So far this works only on the International S6 and Tmobile S6 as far as I am aware.
All others will have to be worked on in due time.
Biggest time sinks for me is downloading everything.
If you don't have something working,
1. Get recovery.img from sammobile and post it somewhere fast for me to download for your device
2. Download the kernel src and post it somewhere for me to download
So far I am working on the F series. It might take time to support all devices.
^^are you working on 925F ?
bigbiff said:
So it seems the Edge has it's own configuration as well as the F series international.
So far this works only on the International S6 and Tmobile S6 as far as I am aware.
All others will have to be worked on in due time.
Biggest time sinks for me is downloading everything.
If you don't have something working,
1. Get recovery.img from sammobile and post it somewhere fast for me to download for your device
2. Download the kernel src and post it somewhere for me to download
So far I am working on the F series. It might take time to support all devices.
Click to expand...
Click to collapse
Thanks I have the recovery.img but don't know what the 'src' is sorry, can you help?
zone23 said:
Thanks I have the recovery.img but don't know what the 'src' is sorry, can you help?
Click to expand...
Click to collapse
maybe source code?
Sent from my SM-G920T using Tapatalk
zone23 said:
Thanks I have the recovery.img but don't know what the 'src' is sorry, can you help?
Click to expand...
Click to collapse
The kernel source from samsung open source center.
bigbiff said:
The kernel source from samsung open source center.
Click to expand...
Click to collapse
OK thanks I have them uploading to my dropbox. Can I PM you when its uploaded would that be ok?
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
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