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!
First other than op awesome Dees
will try!!!!
Does anyone know if we can flash this on stock through goomanager?
master acehole said:
First other than op awesome Dees
will try!!!!
Click to expand...
Click to collapse
Dees, thank u so much ma man. Yur the best.
Never mind I already did it. Awesome! Thanks dees troy. I just did a backup (which was over 2.5gb even with compression) and I backed up boot, system, data, and I think it was called efs. do I need to backup efs? I've only owned a nexus 7, so I'm not too familiar with sammy. also when I went to reboot, it said that I appeared to have lost root, and offered to fix it for me. Is that because I rooted using the motochopper method and not cf-root?
opz187 said:
Never mind I already did it. Awesome! Thanks dees troy. I just did a backup (which was over 2.5gb even with compression) and I backed up boot, system, data, and I think it was called efs. do I need to backup efs? I've only owned a nexus 7, so I'm not too familiar with sammy. also when I went to reboot, it said that I appeared to have lost root, and offered to fix it for me. Is that because I rooted using the motochopper method and not cf-root?
Click to expand...
Click to collapse
Same here and I did the moto way as well.
Everything else looks awesome!
Sent from my SPH-L720 using Tapatalk 2
mjs2011 said:
Same here and I did the moto way as well.
Everything else looks awesome!
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
I think we'll see development starting to pick up in the coming days
Great job. Touch sensitivity is off, for me anyway. For example, when choosing files to install it is almost impossible to use the slider tab. It is also hard to flick through the files. Keeps registering as a push, click, instead of a flick, Swype. Not at a computer so I can't test adb or mounting. Install, backup and restore is good. Backup location is good.
Sent from my SPH-L720 using xda premium
crawrj said:
Great job. Touch sensitivity is off, for me anyway. For example, when choosing files to install it is almost impossible to use the slider tab. It is also hard to flick through the files. Keeps registering as a push, click, instead of a flick, Swype. Not at a computer so I can't test adb or mounting. Install, backup and restore is good. Backup location is good.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
Hey man I gotta question. Which options should we select to back up?
opz187 said:
Hey man I gotta question. Which options should we select to back up?
Click to expand...
Click to collapse
I choose them all. Better safe than sorry is what I say.
Sent from my SPH-L720 using xda premium
Noob question, I see in a changelog it added root checker and ability to install SuperSU if not. Is it possible if unrooted to install GooManager, install this then root? Or just root then install this is easier.
Hey @Dees_Troy - Thank you!
Yes, yes, dev thread.. results forth coming..
xchampx13 said:
Noob question, I see in a changelog it added root checker and ability to install SuperSU if not. Is it possible if unrooted to install GooManager, install this then root? Or just root then install this is easier.
Click to expand...
Click to collapse
You can't install recovery with GooManager unless you are rooted. You can use the Odin flashable tar then boot TWRP to root if you like.
Dees_Troy said:
You can't install recovery with GooManager unless you are rooted. You can use the Odin flashable tar then boot TWRP to root if you like.
Sent from my C6602 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your help. I am on Mac so will probably just root with motochopper first then install through goomanager.
That was fast! Team Win is awesome!
crawrj said:
Great job. Touch sensitivity is off, for me anyway. For example, when choosing files to install it is almost impossible to use the slider tab. It is also hard to flick through the files. Keeps registering as a push, click, instead of a flick, Swype. Not at a computer so I can't test adb or mounting. Install, backup and restore is good. Backup location is good.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
got to agree touch sensitivity is a bit flakey but usable.
going to test a backup / restore etc in a few.
Thanks!
lafester said:
got to agree touch sensitivity is a bit flakey but usable.
going to test a backup / restore etc in a few.
Thanks!
Click to expand...
Click to collapse
Can you tell me which options you select to backup? I've been asking everywhere
---------- Post added at 10:10 PM ---------- Previous post was at 09:52 PM ----------
Yea I just tried to install something via Twrp, and it was impossible to navigate. Couldn't scroll, it just kept registering as a tap
opz187 said:
Can you tell me which options you select to backup? I've been asking everywhere
Click to expand...
Click to collapse
Data, system, boot are usually the default selections for a normal backup..I haven't booted I to recovery yet, but they should be selected by default. That's all u really need for a good backup.
Sent from my SPH-L720 using Tapatalk 2
This is great news!
Sent from my SPH-L720 using Tapatalk 2
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.
Kernel source for Bricked kernel being used in TWRP is here:
https://github.com/showp1984/bricked-mako/tree/twrp_recovery
Has built-in thermal management to help prevent CPU overheat.
Hell yes. I'll flash this and report back. Love some TWRP.
DARKSIDE
Wicked! Been waiting for this!
Just flashed and it won't boot to it. Just reboots the device :s
Tried flashing with goo manager and bit wouldn't stick.
Transmitted from my GALAXYSIII running Jelly Bean. XDA premium
benjamin.j.goodwin said:
Wicked! Been waiting for this!
Just flashed and it won't boot to it. Just reboots the device :s
Click to expand...
Click to collapse
Same here, tried both goomanager and fastboot method
Tried to install it from goomanager and now I can't boot into recovery. also, when I used rom toolbox to boot into recovery, i got force closes from gapps and a few others. Weird behavior. Any idea where I should start looking?
I've been using TWRP since the beginning of time and absolutely love it! I guess my last excuse for not rooting has finally been put to rest
Sent from my Nexus 4
enserio said:
Tried to install it from goomanager and now I can't boot into recovery. also, when I used rom toolbox to boot into recovery, i got force closes from gapps and a few others. Weird behavior. Any idea where I should start looking?
Click to expand...
Click to collapse
Download the image and flash it through fastboot. It's the safest way to do it.
Sent from my Nexus 4 using XDA Premium HD app
dots in IRC tested and confirmed that the latest build flashes and boots fine. Sorry for any inconvenience.
Dees_Troy said:
Can someone try this when they get a chance?
http://techerrata.com/dees_troy/mako.img
See if it will flash and stick with fastboot flash recovery mako.img
Let me know. Can also get on IRC and try to catch me there.
#twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
Confirmed the TWRP you posted mako.img boots up
cwm sticks but this will not. makes me very sad. i love twrp and not so much cwm recovery. also getting gapps (calendar storage etc. force closes when attempting to boot to recovery via goomanager. If anyone can get it to stick please post here how you accomplished please.
Dees_Troy said:
Can someone try this when they get a chance?
http://techerrata.com/dees_troy/mako.img
See if it will flash and stick with fastboot flash recovery mako.img
Let me know. Can also get on IRC and try to catch me there.
#twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
I can confirm that this worked for me. I wiped caches, rebooted, then manually went back into recovery just to make sure it stuck. Thank you mucho.
n82k said:
cwm sticks but this will not. makes me very sad. i love twrp and not so much cwm recovery. also getting gapps (calendar storage etc. force closes when attempting to boot to recovery via goomanager. If anyone can get it to stick please post here how you accomplished please.
Click to expand...
Click to collapse
I did as the man said and flashed through fastboot. Like you, I get the gapps fc when I try to boot in recovery via goomanager or rom toolbox. Kinda weird, and I'd like to get rid of it. Pretty sure it's not a part of flashing this recovery, though. Gotta be in how we rooted and flashed recovery the first time.
n82k said:
cwm sticks but this will not. makes me very sad. i love twrp and not so much cwm recovery. also getting gapps (calendar storage etc. force closes when attempting to boot to recovery via goomanager. If anyone can get it to stick please post here how you accomplished please.
Click to expand...
Click to collapse
Try the one he just posted 2 posts back. It boots up fine
The version in GooManager should now flash and boot just fine too.
Dees_Troy said:
The version in GooManager should now flash and boot just fine too.
Click to expand...
Click to collapse
confirmed!!
Sent from my Nexus 4 through Tapatalk
Dees_Troy said:
The version in GooManager should now flash and boot just fine too.
Click to expand...
Click to collapse
Worked fine for me too. I had cwm installed first through the toolkit for what its worth...
Sent from my Nexus 4
Flashed through goo manager app and it booted fine.
Sent from my Nexus 4 using Tapatalk 2
<3
Great job ! Installed smoothly via Goomanager and also sticks and works properly, haven't had this recovery before but looks promising !
For sure gonna give it a good try after CWM and 4EXT and feel the differences !
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.
Both Mega 5.8 and 6.3 are supported but they use separate images. Be sure that you grab the correct file for your device!
Mega 5.8
Direct download links for Mega 5.8:
http://techerrata.com/browse/twrp2/crater
http://goo.im/devs/OpenRecovery/crater
Mega 6.3
Direct download links for Mega 6.3:
http://techerrata.com/browse/twrp2/melius
http://goo.im/devs/OpenRecovery/melius
Atlast You Released it Thanks. Will install it now hoping that you removed the preload from the Test recovery. Thanks again For the long IRC chats.
Sent from my GT-I9152 using Tapatalk 4
I need root to install this?
Or installing this will provide root?
Sent from my GT-I9152 using Tapatalk 4
Indian Devil said:
I need root to install this?
Or installing this will provide root?
Sent from my GT-I9152 using Tapatalk 4
Click to expand...
Click to collapse
If you get the .tar file of the recovery you should be able to use odin to flash it to your device and the .tar file is available in the link in the post a few above this one i see and it should root the device after you have flashed it..good work on this so far for the mega 5.8, i have the mega 6.3 model i527m.
Indian Devil in the link given above you will get the .tar file too. Flash it like any other recovery via odin.
If your device is not rooted, TWRP gives you option to root your device after you boot into recovery.
Sent from my GT-I9152 using Tapatalk 4
Rittik said:
Indian Devil in the link given above you will get the .tar file too. Flash it like any other recovery via odin.
If your device is not rooted, TWRP gives you option to root your device after you boot into recovery.
Sent from my GT-I9152 using Tapatalk 4
Click to expand...
Click to collapse
Oh yeah i forgot TWRP gives that option to root after it is installed..sorry that i forgot to mention that. :silly:
Dees_Troy said:
Currently only available for the Mega 5.8. If someone with the 6.3 model wants to come by our IRC channel, we can try to add it as well.
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
This is great to see twrp support for the mega. I was actually looking through your work about porting it to the 6.3 i527m
Great job as always
Sent from my SGH-I527M using Tapatalk 4
markbencze said:
This is great to see twrp support for the mega. I was actually looking through your work about porting it to the 6.3 i527m
Great job as always
Sent from my SGH-I527M using Tapatalk 4
Click to expand...
Click to collapse
Porting it to the mega 6.3 (i527m) would be awesome i think. :good:
Guys Just find a device tree. I think Garak has one if I am nkt wrong. Go to TWRP irc and Dees_Troy will give u test builds, if they are working fine. He will make it official in like 10minutes. Thats exactly what I did for mega 5.8. Special credits to Shabbypenguin
Sent from my GT-I9152 using Tapatalk 4
Exellence. Finally we have TWRP for our devive.
Thanks for this TWRP for mega 5.8
Sent from my GT-I9152 using xda app-developers app
Do we need to untick Auto Reboot in Odin while flashing this?
Sent from my GT-I9152 using Tapatalk 4
Will be there TWRP for mega 6.3 anytime soon?
Sent from my GT-I9200 using XDA Premium HD app
I did ask on IRC but I am in the wrong timezone
Nothing so far anyway.
Thanks for answer, i hope we will have TWRP too someday soon.
Just in case want to get back to stock rom via odin do I need triangle away to reset counter first?
bongski55 said:
Just in case want to get back to stock rom via odin do I need triangle away to reset counter first?
Click to expand...
Click to collapse
No. Only for warranty purposes
sent from my Galaxy Mega
Done flashing TWRP. first time to use it after CWM and Philz. Also successfully tested triangle away. Used Titanium backup to freeze some apps.
Waiting for custom ROMs...
Just to confirm guys I'm testing twrp for the 6.3 mega. I'm using the i527m model. However the twrp version is build off the i9200 recovery which is great news.
About to flash my rom and get this phone going!
sent from my Galaxy Mega
TWRP 3.0.0-0 Released
DOWNLOADS
SUPPORTED DEVICES:
twrp-3.0.0.0-millet-160207-0142
* msm8226-sec-millet3g-chn-open
* msm8226-sec-millet3geur
* msm8226-sec-milletwifieur
* msm8926-sec-milletlte
* msm8926-sec-milletlte_tmo
* msm8926-sec-milletlteko
twrp-3.0.0.0-matisse-160207-0145
* msm8226-sec-matisse3g
* msm8226-sec-matissewifi
* msm8926-sec-matisselte
* msm8926-sec-matisselteusc
twrp-3.0.0.0-degas-160207-0212
degaslte twrp @ ctxz -> http://forum.xda-developers.com/tab-4/development/recovery-twrp-3-0-0-galaxy-tab-4-lte-t3323064
CHANGELOG 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 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)
Read more
CHANGELOG 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 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
XDA:DevDB Information
[RECOVERY] TWRP Samsung Galaxy Tab 4 [SM-T3XX|5XX], Tool/Utility for the Samsung Galaxy Tab 4
Contributors
sub77, ctxz
Source Code: https://git.sphere.ly/twrp
Version Information
Status: Stable
Stable Release Date: 2015-04-30
Created 2014-10-30
Last Updated 2016-02-27
Reserved
Thanks but what is an unsecured kernel? What is the difference to twrp that you have posted in tgals thread?
Joe4899 said:
Thanks but what is an unsecured kernel? What is the difference to twrp that you have posted in tgals thread?
Click to expand...
Click to collapse
# Rooting Prevention
#CONFIG_SEC_RESTRICT_ROOTING is not set
#CONFIG_SEC_RESTRICT_SETUID is not set
#CONFIG_SEC_RESTRICT_FORK is not set
#CONFIG_SEC_RESTRICT_ROOTING_LOG is not set
changed from y to is not set. you can now adb to recovery without mounting system.
Thanks!
Does this version also need screen time-out set to 'off'?
sub77 said:
TWRP 2.8.1.0
Kernel unsecured - Linked Libaries are working now
DOWNLOAD
XDA:DevDB Information
[RECOVERY] TWRP 2.8.1.0 for Samsung Galaxy Tab 4 10.1, Tool/Utility for the Samsung Galaxy Tab 4
Contributors
sub77
Version Information
Status: Testing
Created 2014-10-30
Last Updated 2014-10-29
Click to expand...
Click to collapse
T530 ot T535?
krogoth said:
T530 ot T535?
Click to expand...
Click to collapse
T530 tested only
TWRP 2.8.1.0 for flash via Odin
It's working really fine so far^^ Just noticed little bug: When you go to fix permission (did it because wanted to get "Nandroid Manager" working, because it detects the recovery well but didn't find the backups - because you don't have permission to read / write TWRP folder)^^ So I've tried to go to fix permission in recovery and after that I didn't had even permission to delete files in my "Download" directory^^ After firmware reset threw Samsungt Kies 3 and restore backup it work's fine again^^ I've saved the backups to internal storage if the information is helpful^^
Maybe small problem with backup permission general? :laugh:
HELL just noticed that you live in Koblenz^^ I also live there!^^
Joe4899 said:
It's working really fine so far^^ Just noticed little bug: When you go to fix permission (did it because wanted to get "Nandroid Manager" working, because it detects the recovery well but didn't find the backups - because you don't have permission to read / write TWRP folder)^^ So I've tried to go to fix permission in recovery and after that I didn't had even permission to delete files in my "Download" directory^^ After firmware reset threw Samsungt Kies 3 and restore backup it work's fine again^^ I've saved the backups to internal storage if the information is helpful^^
Maybe small problem with backup permission general? :laugh:
HELL just noticed that you live in Koblenz^^ I also live there!^^
Click to expand...
Click to collapse
You can fix this with:
su
restorecon -v -R /data/media
In terminal
Joe4899 said:
HELL just noticed that you live in Koblenz^^ I also live there!^^
Click to expand...
Click to collapse
das ist echt HELL!
i think the problem is that i didnt configed the right mountpoint in the recovery.fstab file, but it shouldnt be a problem, but iam a little bit too dru. äh tired too fix it now.
the last thing for today is triying to build 535 recovery if the kernel source download will be finished sometime.
Hi,
I keep in losing backups made on external SD. It seems it has nothing with mounting but the problem is that TWRP has a problem with exfat (i use a 64Gb card).
Droidphilev said:
Hi,
I keep in losing backups made on external SD. It seems it has nothing with mounting but the problem is that TWRP has a problem with exfat (i use a 64Gb card).
Click to expand...
Click to collapse
have you tried philz recovery? cant test just have a 2gb sd card
Droidphilev said:
Hi,
I keep in losing backups made on external SD. It seems it has nothing with mounting but the problem is that TWRP has a problem with exfat (i use a 64Gb card).
Click to expand...
Click to collapse
Doing that now, yes. I will use Philz if there's no other option. I'm used to TWRP, that's all
http://d-h.st/P8Q twrp 2.8.1.0
http://d-h.st/users/sub77
Philz takes about 30 mins to make a backup. Anyone else facing this?
Droidphilev said:
Philz takes about 30 mins to make a backup. Anyone else facing this?
Click to expand...
Click to collapse
without compression?
i dont have 2.7 sources of twrp, and didnt find.
Hi again,
Did some tests:
With an external sd formatted in exfat.
2.8.1.0 sees this external sd. Nothing looks abnormal. Backup is made and shown in TWRP fileman. When user boots and goes to TWRP folder on external sd in a fileman: no backup. it gets lost somewhere
2.7.1.0 made by Sub77 (haven't test the Tgalal build) backup to external sd works fine and doesn't get lost.
This is thesame behaviour that is mentioned on other device-specific threads. So...if, i say 'if' , Sub77 has the time and likes to make a build of 2.7.1.0 but with the fixes he implemented in 2.8.1.0 we would have a good working recovery until TeamWin comes with a fix for TWRP8.
As we all know not only Philz has abandoned his recovery but also CWM itself is dead.
---------- Post added at 03:45 PM ---------- Previous post was at 03:41 PM ----------
sub77 said:
without compression?
i dont have 2.7 sources of twrp, and didnt find.
Click to expand...
Click to collapse
Without compression yes.
Well... made a build once:
http://forum.xda-developers.com/showpost.php?p=55801060&postcount=21
but since that folder is gone i used your build from:
http://forum.xda-developers.com/showpost.php?p=55828226&postcount=26
---------- Post added at 04:40 PM ---------- Previous post was at 03:45 PM ----------
a backup with TWRP 2.7.1.0 Sub77 build takes 489 seconds. Small difference with the 30 mins in Philz
Hi .
Set CM-11, as written by a http://forum.xda-developers.com/showpost.php?p=55543219&postcount=1 via TWRP 2.8.1.0. Looked , tried. Returned to recovery. Did wipe system, data cache and dalvik cache. Then restore my backup from the external memory card. Everything was back, but the state sdcard is LEGACY!
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.
The theme is a bit undersized. We're using the 1200x1920 theme that's also used on the Nexus 7 2013. At this point we do not feel that it's worth the effort to maintain a stock TWRP theme for 1536x2048 unless more devices pop up using this resolution.
At least running the stock ROM from Google, the Nexus 9 is *ALWAYS* encrypted even if you did not set up encryption. It uses "default_password" as the default password. TWRP can decrypt this and will do so automatically if the default_password is in use.
If you have not unlocked your bootloader, you will need to do so. Hold volume up and down while turning the device on. You will be in the bootloader. Do a "fastboot oem unlock" followed by a "fastboot reboot" from your computer to unlock. This will wipe all of your data including internal storage so back up anything you might want first. If you do not fastboot reboot before installing TWRP, you will probably have to perform a "Format Data" from within TWRP. It is highly recommended that you let the device boot normally immediately after doing the fastboot oem unlock and wait to install TWRP after the first successful boot after the unlock.
Device specific page on our website.
Download link for current and past versions.
Yeeeessss!
Getting this going right now.
Nice work !!
Yay!!!! Thank you so much!!
The app crashes when i select the divice i want to use.
Got it up and running fine. Looks good. Didn't do much, just flashed a different system font but that worked.
The TWRP application from the Play Store didn't work at all, just crash after crash. So just installed the recovery.img with fastboot and everything is fine.
Great to see this!
Question, I read on g+ that decryption is causing issues with making backups other than a raw data image (much lager than a .tar or .win as you use) so this does work now? Also you noted that adb sideload and USB OTG were the only ways to flash a new ROM, is this still the case or will we be able to flash from internal data?
Maybe the best thing for me to do is just flash and find all this out....
Thanks for the great work once again!
Wohooooo . Awesome.
demkantor said:
Great to see this!
Question, I read on g+ that decryption is causing issues with making backups other than a raw data image (much lager than a .tar or .win as you use) so this does work now? Also you noted that adb sideload and USB OTG were the only ways to flash a new ROM, is this still the case or will we be able to flash from internal data?
Maybe the best thing for me to do is just flash and find all this out....
Thanks for the great work once again!
Click to expand...
Click to collapse
As noted in the second post, decrypt of the data partition is working properly on the Nexus 9. I waited to do this release until I got the data decrypt working so none of those issues apply anymore.
Excellent. Making a backup now.
Anyone else having the twrp manager app crashing on you when installing recovery?
jd1639 said:
Anyone else having the twrp manager app crashing on you when installing recovery?
Click to expand...
Click to collapse
I flashed the .img file via fastboot with no issues. Generally it is the safest way to go. Some one reported earlier the TWRP app was not working properly.
Well, let the easy flashing and backuping begin Thanks!
nrage23 said:
I flashed the .img file via fastboot with no issues. Generally it is the safest way to go. Some one reported earlier the TWRP app was not working properly.
Click to expand...
Click to collapse
I'd the image up on team win?
Sent from my Nexus 5 using XDA Free mobile app
nrage23 said:
I flashed the .img file via fastboot with no issues. Generally it is the safest way to go. Some one reported earlier the TWRP app was not working properly.
Click to expand...
Click to collapse
What about flashify ?
---------- Post added at 06:44 PM ---------- Previous post was at 06:44 PM ----------
pantmunu said:
What about flashify ?
Click to expand...
Click to collapse
I will actually give it a shot myself when i get home .
jd1639 said:
I'd the image up on team win?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes you can download the img file from their website.
nrage23 said:
Yes you can download the img file from their website.
Click to expand...
Click to collapse
Thanks, I found it
Sent from my Nexus 5 using XDA Free mobile app
Cheers!!
pantmunu said:
What about flashify ?
---------- Post added at 06:44 PM ---------- Previous post was at 06:44 PM ----------
I will actually give it a shot myself when i get home .
Click to expand...
Click to collapse
Flashing isn't working, it can't find the boot partition. I think it's probably because of the encryption
Sent from my Nexus 9 using XDA Free mobile app
[RECOVERY] [4/5/16] TWRP 3.2.1-0 - TeamWin Recovery Project
TeamWin is proud to present TWRP 3.2.1-0 for the Samsung Galaxy Note 5 (GSM)!
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
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.
noblelte Device Config: https://github.com/TeamWin/android_device_samsung_noblelte
Kernel: https://github.com/TeamWin/android_kernel_samsung_noblelte
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 release notes.
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
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.1
- fix OTG
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.
Known working:
SM-N920T - note 5 tmobile
SM-G928G - s6 edge +
bigbiff said:
Known working on Tmobile Note 5 so far.
Click to expand...
Click to collapse
AWESOME - will be flashing soon - thanks - as always for your work - it is greatly appreciated!
Flashed and booted successfully into recovery -but saw somethnig I have never seen before -
System partitian unmodivied twrp can leave your system partitian unmodified to make it easier for you to take official updates. Twrp will be unable to prevent stock rom from replacing twrp and will not offer to root your device.
Swipe to allow modification...
I assume this means if I select allow modification - it will flash as normal but then would not allow official updates - is that correct?
ALso - OTG is not currently working - hoping this will be taken care of sometime in the future?
I have never seen this before and wondered what the ramifications of this are?
I had problem installing this through ODIN using img.tar.md5, it would failed to download to device and the device would not boot system/receovery , I had to download the img file and flash it using flashify since CWM doesn't do img flashing. Will there be zip file available in near future? Other than that, so far so good everything is working as usual!
Crushader said:
I had problem installing this through ODIN using img.tar.md5, it would failed to download to device and the device would not boot system/receovery , I had to download the img file and flash it using flashify since CWM doesn't do img flashing. Will there be zip file available in near future? Other than that, so far so good everything is working as usual!
Click to expand...
Click to collapse
When I flashed the TWRP Tar in Odin - it flashed and then seemed to hangup at the end when it was clearly finished flashing - it just sat there for a while - maybe 20 seconds - but then it completed the flash and booted immediately into TWRP when I saw the initial warning/tip I mentioned in my previous post - but it did complete the flash from ODIN it just took longer than usual.
mocsab said:
When I flashed the TWRP Tar in Odin - it flashed and then seemed to hangup at the end when it was clearly finished flashing - it just sat there for a while - maybe 20 seconds - but then it completed the flash and booted immediately into TWRP when I saw the initial warning/tip I mentioned in my previous post - but it did complete the flash from ODIN it just took longer than usual.
Click to expand...
Click to collapse
Mine just flashed and then it failed right away and download mode stays on, tried to reboot to recovery to test but it have me an error something about update system failed, try to restore from smart switch on PC. Sop I had to go back to arter's custom CWM from ODIN and then the phone boots up again. Lucky that Flashify managed to flash TWRP img file and everything is working. My model is N920I.
GSM means international lte version ? like n920C ?
mocsab said:
AWESOME - will be flashing soon - thanks - as always for your work - it is greatly appreciated!
Flashed and booted successfully into recovery -but saw somethnig I have never seen before -
System partitian unmodivied twrp can leave your system partitian unmodified to make it easier for you to take official updates. Twrp will be unable to prevent stock rom from replacing twrp and will not offer to root your device.
Swipe to allow modification...
I assume this means if I select allow modification - it will flash as normal but then would not allow official updates - is that correct?
ALso - OTG is not currently working - hoping this will be taken care of sometime in the future?
I have never seen this before and wondered what the ramifications of this are?
Click to expand...
Click to collapse
I will look at enabling OTG soon. 5.1.1 on all phones introduced dm-verity on the system partition. If it gets modified, OEM updates are disabled, and the OEM kernel will fail to boot. If you want to keep completely stock, you need to keep the system r/o
Flashing custom roms/kernels with this turned off will make it so you can have it r/w. R/O will backup the entire system as an image using dd.
bigbiff said:
I will look at enabling OTG soon.
Click to expand...
Click to collapse
awesome - if you need help testing it (I helped you with that on the S6) just let me know
AlMaghraby said:
GSM means international lte version ? like n920C ?
Click to expand...
Click to collapse
All GSM versions should potentially work.
re: TWRP 2.8.7.3
bigbiff said:
Known working on Tmobile Note 5 so far.
Click to expand...
Click to collapse
Just thought to let you know that the "twrp-2.8.7.3-noblelte.img" also works
100% (except for OTG) on my G928T S6 Edge+ phone.
On twrp itself you forgot to change the version number from 2.8.7.0 to 2.8.7.3
When I go into twrp recovery the version still says 2.8.7.0 but it's only cosmetic.
Thanks for all your work!
Can someone test http://build.twrp.me/twrp/twrp-2.8.7.1-noblelte.img.tar for OTG please?
I left my darn OTG at home and cant test until after work - if no one else does, I will try i tthen and will report back. Thanks BigBiff - really appreciate your work!
works on n920c thanks however the odin flashable tar didn't work I made my own tar file without the cach ims don't know why
bigbiff said:
Can someone test http://build.twrp.me/twrp/twrp-2.8.7.1-noblelte.img.tar for OTG please?
Click to expand...
Click to collapse
Installed - but won't recognized OTG when I try to mount in TWRP - I seem to recall you needed the DSMEG after attempting to put the OTG in - but I don't remember how to get the DMSEG - any help is appreciated and I will post the log after I return - assuming I get instructions on where to get it
thanks
mocsab said:
Installed - but won't recognized OTG when I try to mount in TWRP - I seem to recall you needed the DSMEG after attempting to put the OTG in - but I don't remember how to get the DMSEG - any help is appreciated and I will post the log after I return - assuming I get instructions on where to get it
thanks
Click to expand...
Click to collapse
adb shell dmesg > /sdcard/dmesg.txt
AlMaghraby said:
works on n920c thanks however the odin flashable tar didn't work I made my own tar file without the cach ims don't know why
Click to expand...
Click to collapse
Hm, how did you make the tar, just removed the cache.img?
I flashed this using flashfire beta app... installed the .tar file using the firmware flash function in flashfire.
This worked well... only thing I noticed was it shows as v2.8.7.0 but the download link shows as v2.8.7.3
Not sure which it is supposed to be, but either way, it did install.
Thanks. I don't yet have an otg, or else I would be willing to test that feature for you.
bigbiff said:
adb shell dmesg > /sdcard/dmesg.txt
Click to expand...
Click to collapse
I had to install SDK Tools - and Java - once installed I confirmed device is connected - went to recovery and tried to connect OTG - immediately after I attempted the commands you gave in Terminal on my computer and I got a message saying could not find the path specfied - I know I am doing something wrong but can't figure out what?
I did try using the Terminal in TWRP - and did a command for dmesg and when I checked in my sd card after booting - I found there was a file there - it is called dmsesg but I don't know if it is what you are looking for - (Even a broken clock is corect twice day) hope this is what you needed...