Mod Edit
This thread is a work in progress and should be used carefully.
Read this entire thread before flashing anything.
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.
CHANGELOGS :
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.
TWRP 3.0.0.0 (Testing ...)
TWRP Folder
Sources
- android_device_samsuung_heroqlte
Bugs ?
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
Support
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[RECOVERY][QCOM][heroqlte] TWRP 3.0.0-0 touch recovery [2016-03-12], Tool/Utility for the Samsung Galaxy S7
Contributors
h2o64
Version Information
Status: Testing
Created 2016-03-12
Last Updated 2016-03-13
Reserved
Info :
The kyro MSM platform that MSM8996 (Snapdragon 820) isn't supported by anything but CAF. So AOSP and OmniROM doesn't supports it officially
Thanks for your work so far, h2o64!
I've heard other people say that the G930V and G930P are practically the same -- is this firmware targeting support for the G930V/heroqltevzw (Verizon Samsung Galaxy S7)in addition to the devices listed?
psouza4 said:
Thanks for your work so far, h2o64!
I've heard other people say that the G930V and G930P are practically the same -- is this firmware targeting support for the G930V/heroqltevzw (Verizon Samsung Galaxy S7)in addition to the devices listed?
Click to expand...
Click to collapse
This device is compatible. Any Qualcomm variant will run this recovery.
please do the same
http://forum.xda-developers.com/showpost.php?p=65789701&postcount=75
@h2o64 How to install? It's an .img, is there .tar variant available?
MiNoOo said:
please do the same
http://forum.xda-developers.com/showpost.php?p=65789701&postcount=75
Click to expand...
Click to collapse
Done
Sorry been out of the flashing game
a while, so bear with me. Can you detail how to install this? I have the US T-Mobile (930T) variant. You said it should work on all Qualcomm variants so hopefully it works for me! Thanks in advance buddy! Great work!
DJBhardwaj said:
@h2o64 How to install? It's an .img, is there .tar variant available?
Click to expand...
Click to collapse
+1
---------- Post added at 04:09 AM ---------- Previous post was at 04:07 AM ----------
psouza4 said:
Thanks for your work so far, h2o64!
I've heard other people say that the G930V and G930P are practically the same -- is this firmware targeting support for the G930V/heroqltevzw (Verizon Samsung Galaxy S7)in addition to the devices listed?
Click to expand...
Click to collapse
Doesn't Verizon lock the bootloader? So you will have a brick if you try?
sml2004 said:
+1
---------- Post added at 04:09 AM ---------- Previous post was at 04:07 AM ----------
Doesn't Verizon lock the bootloader? So you will have a brick if you try?
Click to expand...
Click to collapse
Verizon is supported
DJBhardwaj said:
@h2o64 How to install? It's an .img, is there .tar variant available?
Click to expand...
Click to collapse
It's my first Samsung experience, I'll invest the odin things.
h2o64 said:
It's my first Samsung experience, I'll invest the odin things.
Click to expand...
Click to collapse
Same here. But then how did you test the recovery on your phone?
DJBhardwaj said:
Same here. But then how did you test the recovery on your phone?
Click to expand...
Click to collapse
A friend that eagerly wanted to get root before leaving ask me a recovery, I made the image and he didn't said much ^^
h2o64 said:
A friend that eagerly wanted to get root before leaving ask me a recovery, I made the image and he didn't said much ^^
Click to expand...
Click to collapse
Cool, haha. Do let us know how we can flash this, it would be great to know. I am familiar with the .tar method using Odin. But not so much with .img on Samsung. :good:
DJBhardwaj said:
Cool, haha. Do let us know how we can flash this, it would be great to know. I am familiar with the .tar method using Odin. But not so much with .img on Samsung. :good:
Click to expand...
Click to collapse
FYI if this does work, it will work on G930T, G930P, G930FD and maybe G930V (if it is unlocked, seriously, is it?)
G930W8 (the Canadian variant) is Exynos and should work with the official G930F release.
Update: Apologies if you don't want me mirroring this, but I'm really interested in your results.
For Odin:
https://idlekernel.com/twrp/heroqlte/h2o64/AP_twrp-3.0.0-0_heroqlte_RECOVERY.tar.md5
DJBhardwaj said:
Cool, haha. Do let us know how we can flash this, it would be great to know. I am familiar with the .tar method using Odin. But not so much with .img on Samsung. :good:
Click to expand...
Click to collapse
with samsung you cant flash a .img file without root. you have to use odin to get past that. so we will need a .tar or .md5 file. i can create an md5 file but i get a secure fail error with my bootloader on my phone for recovery. so it doesnt flash. it gets to rqt_close in odin and fails.
jcadduono said:
FYI if this does work, it will work on G930T, G930P, G930FD and maybe G930V (if it is unlocked, seriously, is it?)
G930W8 (the Canadian variant) is Exynos and should work with the official G930F release.
Update: Apologies if you don't want me mirroring this, but I'm really interested in your results.
For Odin:
https://idlekernel.com/twrp/heroqlte/h2o64/AP_twrp-3.0.0-0_heroqlte_RECOVERY.tar.md5
Click to expand...
Click to collapse
I'm uploading 30 MO of recovery on my tiny connection ^^ we'll see in a few minutes
jcadduono said:
FYI if this does work, it will work on G930T, G930P, G930FD and maybe G930V (if it is unlocked, seriously, is it?)
G930W8 (the Canadian variant) is Exynos and should work with the official G930F release.
Update: Apologies if you don't want me mirroring this, but I'm really interested in your results.
For Odin:
https://idlekernel.com/twrp/heroqlte/h2o64/AP_twrp-3.0.0-0_heroqlte_RECOVERY.tar.md5
Click to expand...
Click to collapse
still doesnt work. this is in odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
on my phone the error message is secure check fail : recovery
i have oem unlock on in developer settings. my phone is g930T.
Yeah, when I get to NAND Write Start!! the progess bar on the phone starts but just seems to stall out. Looks like it isn't able to actually copy it over.
Corwinder said:
Yeah, when I get to NAND Write Start!! the progess bar on the phone starts but just seems to stall out. Looks like it isn't able to actually copy it over.
Click to expand...
Click to collapse
and this my friends, is what you call "increasing development on Exynos"
Looks like the Qualcomm variants are locked!
queue disappointment
Perhaps contact T-Mobile and ask them if it's possible to unlock your device's bootloader (secure verification flash) (not SIM)
You will need to ask to be put with someone in engineering probably, if you complain like crazy they might forward the request up the chain.
T-Mobile has not done locked Samsung devices before, so they are likely to receive a huge backlash on providing the device really early to shorten the return window.
They might forward request to Samsung to unlock it if people work together to threaten to switch carriers, lol.
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.
Changelog - See our website!
FAQ:
How to install with Fastboot:
1. Download the fastboot binary for your computer from HTC
2. Connect your phone and boot it into fastboot
3. Run fastboot with the command
Code:
Code:
fastboot flash recovery path/to/recovery-twrp-crespo4g-1.0.3.img
Error when flashing some zip files:
twrp only supports the latest and greatest edify script for zip flashing. Please bug the zip developer to update the zip script to edify.
Does this back up the WiMAX partition?
That is an option if you chose, but you'll find it under "efs" and not wimax. Both the NS4G and the GSM Nexus S have an efs partition. The efs partition on the NS4G includes WiMAX along with some other fairly crucial data. It's a good idea to back up your efs separately (e.g. just pick efs and don't choose any other partitions) and keep this backup in a safe place.
Live support:
Click this link or join us in #twrp on Freenode IRC.
Yes. Thanks for this. Works great
So how will flashing our backed up images thru fastboot work since they are backed up as .win?
Uncle Jimmy says hello
snandlal said:
Yes. Thanks for this. Works great
So how will flashing our backed up images thru fastboot work since they are backed up as .win?
Uncle Jimmy says hello
Click to expand...
Click to collapse
What partition?
Most are img files just with a different extension some are .tars. You can try it. If it doesn't work you can just restore.
If i go in TWRP on my storage and look at the backed up images like system.win, data.win, boot.win. how would i use that image in fastboot if for some reason i couldnt get to recovery? Rename it to .img?
Uncle Jimmy says hello
The .win files are either .tar or .tgz files (depending on whether you chose compression or not). The backups themselves are usually done with dd. So long as you're not messing with the recovery partition itself and leaving compression turned off, you should be good to go with fastboot flashing, though I don't have a NS4G myself to check.
snandlal said:
If i go in TWRP on my storage and look at the backed up images like system.win, data.win, boot.win. how would i use that image in fastboot if for some reason i couldnt get to recovery? Rename it to .img?
Uncle Jimmy says hello
Click to expand...
Click to collapse
No, you can not fastboot system/data/cache/sd-ext/.android_secure as those are essentially tgz. You can how ever fastboot or dd the others which are boot/recovery/efs by renaming it to .img
AssassinsLament said:
No, you can not fastboot system/data/cache/sd-ext/.android_secure as those are essentially tgz. You can how ever fastboot or dd the others which are boot/recovery/efs by renaming it to .img
Click to expand...
Click to collapse
What? Ok so all im asking is.....the system.win in TWRP, can i rename that system.img and flash thru fastboot?
Uncle Jimmy says hello
snandlal said:
What? Ok so all im asking is.....the system.win in TWRP, can i rename that system.img and flash thru fastboot?
Uncle Jimmy says hello
Click to expand...
Click to collapse
You can fastboot these backups:
boot/recovery/efs
You cannot fastboot these:
system/data/cache/sd-ext/.android_secure
Hope that clears it up.
Dees_Troy said:
You can fastboot these backups:
boot/recovery/efs
You cannot fastboot these:
system/data/cache/sd-ext/.android_secure
Hope that clears it up.
Click to expand...
Click to collapse
Ok thanks. That did clear it up.
Uncle Jimmy says hello
You guys gonna submit this to koushik so it can be flashed in rom manager under "flash alternate recoveries"?
I would love to use this recovery, but unable to push anything on my laptop right now (needs formation). Any flashable scripts?
Sent from my Nexus S 4G using XDA Premium App
info[]box1 said:
I would love to use this recovery, but unable to push anything on my laptop right now (needs formation). Any flashable scripts?
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
Use "flash_image gui" by Joeykrim. Apps & Themes section
http://forum.xda-developers.com/showthread.php?t=1122599
snandlal said:
Use "flash_image gui" by Joeykrim. Apps & Themes section
http://forum.xda-developers.com/showthread.php?t=1122599
Click to expand...
Click to collapse
Thanks for help I'll report back.
Edit: it worked thx
Sent from my Nexus S 4G using XDA Premium App
Loving this recovery. Great job teamwin!
Wish all capacitive buttons worked though.
snandlal said:
Use "flash_image gui" by Joeykrim. Apps & Themes section
http://forum.xda-developers.com/showthread.php?t=1122599
Click to expand...
Click to collapse
Please advise: If your using the app do you just select the recovery image option and hit flash file?
very very well done.
would there be a way to implement the option to perform backup/restore via adb like on RA recovery?
I tried it but i am not sure if i remember the command properly I did
Code:
adb shell
# cd /sbin
# nandroid-mobile.sh -b
TheBurgh said:
Please advise: If your using the app do you just select the recovery image option and hit flash file?
Click to expand...
Click to collapse
yeah the first attempt i selected recovery img and manually selected wipe cache. it prompted successful execute, but recovered cwm recovery (no recovery)lol. just rebooted and the second attempt i didnt check wipe cache. all is GOOD now lol.
[email protected] said:
very very well done.
would there be a way to implement the option to perform backup/restore via adb like on RA recovery?
I tried it but i am not sure if i remember the command properly I did
Code:
adb shell
# cd /sbin
# nandroid-mobile.sh -b
Click to expand...
Click to collapse
We don't use nandroid.sh at all. It's not included in our recovery. All of our backups are done in C, so this isn't possible. Sorry.
We didn't base our recovery on CWM or Amon_RA. While we may have used a few bits of code here and there, for the most part we tried to write our own recovery doing things the best way that we thought was possible.
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!
Patiently awaiting the day I can see TWRP on my screen!!
Recovery before a unlocked bootloader... awesome!!!
Sent from my SAMSUNG-SGH-I337 using xda premium
Awesome, I can't wait to be able to install. Now here comes the "I just loaded through goo manager and now I can't boot!" posts!
Can this work on the Canadian (i337M) version?
Links not uploaded??
The links go to download site however no recovery is shown..... are they uploaded yet? Thank you so much for this..
It installed perfectly on my Rogers SGH-I337M, although, it definitely has some bugs.
When setting the backup name, the keyboard is ultra-sensitive; you often get multiple entries even with the slightest touch.
The time it's completely off. Mine is about 1h45m fast and, yes, I have the settings set properly with Eastern Time Zone Selected, and the Daylight Saving Time option checked.
Also, the backup file is huge; almost 4GB, and while the backup was in progress, it stated that it had to break up the file into multiple archives.
Otherwise, great work so far.
PETER
Addendum: I installed TWRP through Goo Manager. Also, touching the screen did not work to get the device out of sleep mode while in TWRP. I had to use the Home button.
Sent from my SGH-I337M using xda premium
PeterGuru said:
It installed perfectly on my Rogers SGH-I337M, although, it definitely has some bugs.
When setting the backup name, the keyboard is ultra-sensitive; you often get multiple entries even with the slightest touch.
The time it's completely off. Mine is about 1h45m fast and, yes, I have the settings set properly with Eastern Time Zone Selected, and the Daylight Saving Time option checked.
Also, the backup file is huge; almost 4GB, and while the backup was in progress, it stated that it had to break up the file into multiple archives.
Otherwise, great work so far.
PETER
Sent from my SGH-I337M using xda premium
Click to expand...
Click to collapse
I've got to say Peter, you've got serious kahunas flashing this. Thanks man, appreciate it! The question I have: Is the I337M bootloader unlocked, or is your test indicative of what would happen on all 337 variants when flashing TWRP?
Please don't talk about my kahunas without first getting permission from my wife.
What I'm about to say is not gospel but, according to MobileSyrup, all Canadian variants have an unlocked bootloader. It appears to be true, that is, with the Rogers variant, as I have been able to boot into TWRP effortlessly, and maintain root, not to mention having done all that AFTER performing a system update.
Peter
Sent from my SGH-I337M using xda premium
On M-syrup, Dan Badder really knows his stuff, I doubt he would say it was unlocked without being damn sure. I just did a search and found his comment (good to know one of us has the attention span to read the full review). For others, here is his comment:
"It appears that Samsung has left the device’s bootloader alone on the Canadian builds which, unlike on the AT&T model, means there shouldn’t be an issue loading new software on it. The problem is that because the Canadian model shares the same underlying architecture as the aforementioned U.S. variant, initial availability of custom ROMs and kernels will be limited due to a shortage of developers with access to the phone’s bootloader. This is an unfortunate situation alleviated somewhat by the fact that the device runs Android 4.2.2, the latest version of the Android software."
I just got the device today, rooted before the ota to be safe, and now the update won't work because my device is "Modified". Did the update make any difference whatsoever? Would be good to know if it is worth installing via odin when the firmware becomes available.
I was having serious lag prior to the update, much of it now solved following the update, although, some lag still exists. There's simply too much bloat on the device. After all, the TWRP backup file was 4GB.
By the way, you can unroot your device and reverse everything back to stock it you want to install the update. There's another thread somewhere that explains how to do it, which is what I did.
Peter
Sent from my SGH-I337M using xda premium
PeterGuru said:
I was having serious lag prior to the update, much of it now solved following the update, although, some lag still exists. There's simply too much bloat on the device. After all, the TWRP backup file was 4GB.
By the way, you can unroot your device and reverse everything back to stock it you want to install the update. There's another thread somewhere that explains how to do it, which is what I did.
Peter
Sent from my SGH-I337M using xda premium
Click to expand...
Click to collapse
Thanks Peter! Found the thread, unrooted (didn't even factory reset) and the ota loaded like a charm. It is good to see a lot of the quality people from the GS3 gang here. This year really flew by!
PeterGuru said:
...it really wasn't too much of a risk. I've only had the device for two days, so I'm still within the 15-day return period, plus I've got a few tricks up my sleeve when returning rooted and modified devices. Had things gone terribly wrong, I simply would have brought it back and gotten a new one.
Click to expand...
Click to collapse
I find it interesting how many people here think nothing of announcing publicly that they are willing to commit fraud against the various carriers, or recommend that others do so. I realize that there are two camps on this issue. Many apparently would do this, but many of us feel it is just plain morally wrong. It is not unlikely that behavior such as this has been a factor in the decision to lock the phones down. For now, the Canadian carriers evidently haven't done so, but this kind of behavior won't encourage them to stay open.
Successfully installed on bell i337m.
creepyncrawly said:
I find it interesting how many people here think nothing of announcing publicly that they are willing to commit fraud against the various carriers, or recommend that others do so. I realize that there are two camps on this issue. Many apparently would do this, but many of us feel it is just plain morally wrong. It is not unlikely that behavior such as this has been a factor in the decision to lock the phones down. For now, the Canadian carriers evidently haven't done so, but this kind of behavior won't encourage them to stay open.
Click to expand...
Click to collapse
No thank you, I'll make up my own mind about what I think is moral or immoral.
creepyncrawly said:
I find it interesting how many people here think nothing of announcing publicly that they are willing to commit fraud against the various carriers, or recommend that others do so. I realize that there are two camps on this issue. Many apparently would do this, but many of us feel it is just plain morally wrong. It is not unlikely that behavior such as this has been a factor in the decision to lock the phones down. For now, the Canadian carriers evidently haven't done so, but this kind of behavior won't encourage them to stay open.
Click to expand...
Click to collapse
I'm finding it interesting that your signature includes information about flashing kernels without increasing your flash counter and how to prepare your phone to send to warranty for replacement. Kind of ironic I suppose.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
lessthanzach said:
I'm finding it interesting that your signature includes information about flashing kernels without increasing your flash counter and how to prepare your phone to send to warranty for replacement. Kind of ironic I suppose.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Getting your device unrooted and ready for standard hardware repair is much different then bricking the device out of personal negligence and committing fraud to get a new one.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Mike on XDA said:
Getting your device unrooted and ready for standard hardware repair is much different then bricking the device out of personal negligence and committing fraud to get a new one.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
And I quote "Prepare your phone to return to the store or for warranty replacement"
Maybe you should look at the person's signature I mentioned prior to attempting to correct me, thanks.
Also, for what other reason would you need to inhibit a flash counter besides warranty fraud? Please enlighten me.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Just tried on my Rogers i337m. Works like a charm. Thank you!
Sent from my SGH-I337M using xda app-developers app
[RECOVERY] TWRP 3.2.2-0 - TeamWin Recovery Project
TeamWin is proud to present TWRP 3.2.2-0 for the Samsung Galaxy Note 4 (Exynos/Qualcomm International)!
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.
treltexx Device Config: TBD
Kernel: https://github.com/bigbiff/android_...ub.com/bigbiff/android_kernel_samsung_trltexx
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
See http://twrp.me for official 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.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.1
treltexx
- fix color scheme again
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)
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
- 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
- Add Cancel Backup capability
- Other small fixes and improvements
2.8.4.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
- Fix some MTP related crashes and bugs
- Eliminate TWRP toggling USB IDs during boot if MTP is enabled
- Fix various adb sideload issues
- Improve threading of actions
- Eliminate separate thread for screen timeout
- Update libblkid to 2.25.0
- Use power button as back button on watch themes for easier navigation
- Add mutex locking to data manager
- Improve custom theme handling on encrypted devices
- Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
2.8.3.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- MTP will now tell the host PC that storage is removed instead of disabling MTP completely
- MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
- Update and improve fix permissions and make fixing contexts optional
- Update SuperSU in TWRP to 2.40 and update install process
- Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
- Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
- Fix kernel panic during MTP start on some devices
- Support unicode fonts on devices with True Type Font support
- Fix slider value not showing sometimes (vibration settings page)
- Toggle MTP off during adb sideload to set correct USB IDs
- Reduce library requirements for 5.0 L decrypt
- Other minor fixes and improvements
2.8.1.2
- 2nd release with everything working except ADB
Reserved3
Also for n910f snapdragon
Sent from my SM-N910F using XDA Premium 4 mobile app
Not working for me. It flashed alright. Got the screen but its not making backup. perhaps I am missing something.
N-910C
bigbiff said:
2.8.1.2
- 2nd release with everything working except ADB
Click to expand...
Click to collapse
Installed on N910C I try to do an backup but
write E: unknown action "nandroid"
and nothing else
edit : I give a try to 2.8.1.1 and I can backup ?????
TKokab said:
Not working for me. It flashed alright. Got the screen but its not making backup. perhaps I am missing something.
N-910C
Click to expand...
Click to collapse
Yes, there something wrong at your side. Because a lot of people around the world have tested this version, and backup is working flawless.
TKokab said:
Not working for me. It flashed alright. Got the screen but its not making backup. perhaps I am missing something.
N-910C
Click to expand...
Click to collapse
+1 if you use the 2.8.1.2
i flash the 2.8.1.1 and it work, i have too an N910C
TWRP throwing errors on 2.8.1.2
kondronaute said:
+1 if you use the 2.8.1.2
i flash the 2.8.1.1 and it work, i have too an N910C
Click to expand...
Click to collapse
Hi there.
I'm on N910U exynos.
Flashed 2.8.1.2 sucessfully.
Tried to do backup and getting error in red "unknown action".
Actually, anything I try to do in TWRP I'm getting the above error.
I've tried flashing via odin with the .tar & via CWM recovery with .zip file with same results.
Anyone else having this problem?
---------- Post added at 11:17 PM ---------- Previous post was at 11:10 PM ----------
geewizz said:
Hi there.
I'm on N910U exynos.
Flashed 2.8.1.2 sucessfully.
Tried to do backup and getting error in red "unknown action".
Actually, anything I try to do in TWRP I'm getting the above error.
I've tried flashing via odin with the .tar & via CWM recovery with .zip file with same results.
Anyone else having this problem?
Click to expand...
Click to collapse
Whoops, looks like I read it wrong.
Will try 2.8.1.1 & see if that works...
---------- Post added at 11:38 PM ---------- Previous post was at 11:17 PM ----------
Ok, flashed 2.8.1.1.
Semmed to flash ok but when holding down volume up, home and power buttons it hangs at the "galaxy note 4' scrren and doesn't enter TWRP.
Have to pull battery to restart.
2.8.1.2 flashes ok but any command throws the unknown action error.
2.8.1.1 flashes ok but I can't enter recovery.
Any ideas anyone?
geewizz said:
Hi there.
I'm on N910U exynos.
Flashed 2.8.1.2 sucessfully.
Tried to do backup and getting error in red "unknown action".
Actually, anything I try to do in TWRP I'm getting the above error.
I've tried flashing via odin with the .tar & via CWM recovery with .zip file with same results.
Anyone else having this problem?
---------- Post added at 11:17 PM ---------- Previous post was at 11:10 PM ----------
Whoops, looks like I read it wrong.
Will try 2.8.1.1 & see if that works...
---------- Post added at 11:38 PM ---------- Previous post was at 11:17 PM ----------
Ok, flashed 2.8.1.1.
Semmed to flash ok but when holding down volume up, home and power buttons it hangs at the "galaxy note 4' scrren and doesn't enter TWRP.
Have to pull battery to restart.
2.8.1.2 flashes ok but any command throws the unknown action error.
2.8.1.1 flashes ok but I can't enter recovery.
Any ideas anyone?
Click to expand...
Click to collapse
same for me
With 2.8.1.1 If You wait a long time you finally enter recovery
It take ages also to reboot from system to recovery.
The 2.8.1.2 Is not working.
Hope a Fix soon
geewizz said:
Hi there.
I'm on N910U exynos.
Flashed 2.8.1.2 sucessfully.
Tried to do backup and getting error in red "unknown action".
Actually, anything I try to do in TWRP I'm getting the above error.
I've tried flashing via odin with the .tar & via CWM recovery with .zip file with same results.
Anyone else having this problem?
---------- Post added at 11:17 PM ---------- Previous post was at 11:10 PM ----------
Whoops, looks like I read it wrong.
Will try 2.8.1.1 & see if that works...
---------- Post added at 11:38 PM ---------- Previous post was at 11:17 PM ----------
Ok, flashed 2.8.1.1.
Semmed to flash ok but when holding down volume up, home and power buttons it hangs at the "galaxy note 4' scrren and doesn't enter TWRP.
Have to pull battery to restart.
2.8.1.2 flashes ok but any command throws the unknown action error.
2.8.1.1 flashes ok but I can't enter recovery.
Any ideas anyone?
Click to expand...
Click to collapse
2.8.1.1 and 2.8.1.2 been tested for flashing roms, flashing zips and other mods, backup and restore and all was good. No problems whatsoever. You guys must be having something wrong at your end.
Sent from my SM-N910C
Al Asmi said:
2.8.1.1 and 2.8.1.2 been tested for flashing roms, flashing zips and other mods, backup and restore and all was good. No problems whatsoever. You guys must be having something wrong at your end.
Sent from my SM-N910C
Click to expand...
Click to collapse
you are wrong we are 3 to have same pbm with 2.8.1.2 cannot backup to extcard say unknown pbm....
I installed it with odin
the 2.8.1.1 is working for me but take ages to enter recovery.
I am here from my S2 ......s3....s4.........................note4
kondronaute said:
you are wrong we are 3 to have same pbm with 2.8.1.2 cannot backup to extcard say unknown pbm....
I installed it with odin
the 2.8.1.1 is working for me but take ages to enter recovery.
I am here from my S2 ......s3....s4.........................note4
Click to expand...
Click to collapse
+1
kondronaute said:
you are wrong we are 3 to have same pbm with 2.8.1.2 cannot backup to extcard say unknown pbm....
I installed it with odin
the 2.8.1.1 is working for me but take ages to enter recovery.
I am here from my S2 ......s3....s4.........................note4
Click to expand...
Click to collapse
I'm not saying that you are wrong. What I'm trying to tell you is that you may be having problems with your extsd. Try to install a permission fix and try again. For me and for so many others it's working fine.
Sent from my SM-N910C
Al Asmi said:
I'm not saying that you are wrong. What I'm trying to tell you is that you may be having problems with your extsd. Try to install a permission fix and try again. For me and for so many others it's working fine.
Sent from my SM-N910C
Click to expand...
Click to collapse
result is E:unknown action 'fixpermissions'
kondronaute said:
result is E:unknown action 'fixpermissions'
Click to expand...
Click to collapse
Try this :
https://app.box.com/s/ajtshutm4mfexzvp004x
Unzip then flash with flashify. Tested on N910C and have no issues.
Sent from my SM-N910C
Al Asmi said:
Try this :
https://app.box.com/s/ajtshutm4mfexzvp004x
Unzip then flash with flashify. Tested on N910C and have no issues.
Sent from my SM-N910C
Click to expand...
Click to collapse
can u give me tar version please i use odin
---------- Post added at 11:08 AM ---------- Previous post was at 11:04 AM ----------
Al Asmi said:
Try this :
https://app.box.com/s/ajtshutm4mfexzvp004x
Unzip then flash with flashify. Tested on N910C and have no issues.
Sent from my SM-N910C
Click to expand...
Click to collapse
no need for tar i do what you say and it work fine
thank u
kondronaute said:
can u give me tar version please i use odin
---------- Post added at 11:08 AM ---------- Previous post was at 11:04 AM ----------
no need for tar i do what you say and it work fine
thank u
Click to expand...
Click to collapse
Glad that it worked for you.
@bigbiff, this is the last version with corrected color (blue) you've posted at the testing thread.
I hope it will work for the others who's having problems with the tar file.
https://app.box.com/s/ajtshutm4mfexzvp004x
Sent from my SM-N910C
Should i use the tmobile version on my SM-N910F?
Al Asmi said:
Glad that it worked for you.
@bigbiff, this is the last version with corrected color (blue) you've posted at the testing thread.
I hope it will work for the others who's having problems with the tar file.
https://app.box.com/s/ajtshutm4mfexzvp004x
Sent from my SM-N910C
Click to expand...
Click to collapse
Its working now.....thanks for the link
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:
https://www.androidfilehost.com/?w=files&flid=41298
Can be updated quickly and easily within TWRP if TWRP is already installed
1) Download the latest version from the above link
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Prerequisites:
* Unlocked bootloader
Unlocking bootloader:
fastboot -i 0x1bbb oem unlock
NOTE: If you are running Linux, you will need root permission via "sudo"
Installation (temp/boot):
Code:
fastboot -i 0x1bbb boot twrp-3.0.0-1-idol3.img
Installation (permanent):
Code:
fastboot -i 0x1bbb flash recovery twrp-3.0.0-1-idol3.img
What's different from the previously released one in the other thread?
kevev said:
What's different from the previously released one in the other thread?
Click to expand...
Click to collapse
People had issues with petrov.0 build I personally haven't tested his. This version includes the time fix which is the only difference besides upstream updates.
Thanx for the Update. It did fix the time problem.
discard
Just flashed and work fine 6045Y, but still bug with the time.
Thank you
Updated to new recovery works fine, but I noticed that it takes a long time to make the two wipe Dalvik cache and cache. It happens to you?
masterdex said:
Updated to new recovery works fine, but I noticed that it takes a long time to make the two wipe Dalvik cache and cache. It happens to you?
Click to expand...
Click to collapse
Takes a while to boot as well it's slow in general the UI lags. I'm working on that now.
edit: I have succeeded I will upload it after further testing. It's flying now booted in like 3 seconds from fastboot.
Sent from my 6045I using Tapatalk
Ok meanwhile I restored to DallasCZ aspect you to edit the new version.
ok, since @Unjustified Dev has this thread i will ask the Mods to close my thread to avoid duplicity.
Just installed on my 6045I and I got this error 255. Did I miss something when I flashed the image?
Am I the only one to whom the recovery is painfully slow when performing a wipe of any partition?
On the "old" TWRP release,a wipe of any partition would be done in less than 5 seconds,but on this release,it takes more than 30 seconds.
The Marionette said:
Am I the only one to whom the recovery is painfully slow when performing a wipe of any partition?
On the "old" TWRP release,a wipe of any partition would be done in less than 5 seconds,but on this release,it takes more than 30 seconds.
Click to expand...
Click to collapse
For me it took over 35 minutes. I was about to force shutdown. 30 seconds is golden by comparison. I'm back on petrov.
Unjustified Dev said:
Takes a while to boot as well it's slow in general the UI lags. I'm working on that now.
edit: I have succeeded I will upload it after further testing. It's flying now booted in like 3 seconds from fastboot.
Sent from my 6045I using Tapatalk
Click to expand...
Click to collapse
Hello, no news about update? Thanks
wallah said:
Hello, no news about update? Thanks
Click to expand...
Click to collapse
Unable to test it correctly now. I'm stuck with sending commands by shell. I'll keep you all up to date on any progress I make.
Unjustified Dev said:
Unable to test it correctly now. I'm stuck with sending commands by shell. I'll keep you all up to date on any progress I make.
Click to expand...
Click to collapse
Have you considered running vnc server on the phone and remote admin'ing it from the pc?
https://play.google.com/store/apps/details?id=org.onaips.vnc&hl=en
theres a new version of TWRP out now 3.00 http://www.xda-developers.com/twrp-3-0-0-has-arrived/
would be nice for us to have it ported
gecko702 said:
theres a new version of TWRP out now 3.00 http://www.xda-developers.com/twrp-3-0-0-has-arrived/
would be nice for us to have it ported
Click to expand...
Click to collapse
I agree with that. I would also be willing to donate for continued support of this phone. Hopefully We'll have cm13 eventually as well
-Update- Started by using the Regular version posted by Unjustified Dev. Took forever to actually boot into TWRP. Backups seemed on par though. Test2 version boots great and in a timely fashion like it should. factory reset with that version just took about 15 minutes.
-Update2- It appears the option in TWRP to use rm -rf instead of formatting clears up the time it is taking to do wipes. My times are 100% better with that option ticked. 15 minute factory reset time to 5 seconds!! And if that wasn't good enough, it also fixes the hangups in restore and I was able to restore in about 3 minutes. Thanks much Unjustified Dev. Personally I'd say test2 is the one for me at this point.
TWRP 3.0 released on feb 5th, 2016
http://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html Article has more details.
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
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.
DOWNLOAD & HOW-TO INSTALL:
--------- On Device ---------
1) Download the latest recovery.img from Android File Host
2) Use Flashify to flash the recovery.img
(How to use flashify)
1) Grant Root Access
2) Click "Recovery image"
3) Click "Choose a file"
4) Select the img you just downloaded and when prompted to flash, press "Yep"
5) When it offers you to reboot, select "Yep"
------------------------------------------------------------------
--------- Odin (On Windows PC) ---------
1) Download the recovery.tar from Android File Host
2) Open Odin and click the "AP" button and select the .tar file you downloaded
3) Boot your phone into download mode (hold Volume Down + Home + Power)
4) When prompted, press the Volume Up button to continue
5) Connect your device to your PC and press Start
6) Once your device is finished booting, shut it off
7) Once your device is completely off, press and hold Volume up + Home + Power until you get a "recovery is not seenforcing" message in red at the upper left hand of your screen
-----------------------------------------------------------------------------
XDA:DevDB Information
TeamWin TWRP Recovery for the Sprint Samsung Galaxy S6 (SM-G920P)
Contributors
tvm2487 - TWRP Compiler
1619415 - Thread Maintainer
And TeamWin (duh)
Version Information: 3.0.2-0
Status: Stable
Last Updated May 10th, 2016
XDA:DevDB Information
[TOOL/UTILITY][TWRP][RECOVERY] TWRP 3.0.2-0 TeamWin Recovery Project 5/10, Tool/Utility for the Sprint Samsung Galaxy S6
Contributors
1619415, tvm2487
Version Information
Status: Stable
Created 2016-05-10
Last Updated 2016-05-10
We love you, man. No homo
Sent from my SM-G920P using Tapatalk
Thank you guys! Keep up the good work!
asafegous said:
We love you, man. No homo
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Lol
Excellent job TeamSpr. Much appreciated. Sadly, not working the Edge yet
iam assuming this will also work for boost mobile,?
nyfl2004 said:
Excellent job TeamSpr. Much appreciated. Sadly, not working the Edge yet
Click to expand...
Click to collapse
If the good folks that built the modified version would share the device tree, I can help unify it with the Edge ( I don't have an edge, but can help @nyfl2004 extract the necessary blobs, et al, to build the Edge in).
Did you start with this by chance? https://github.com/TeamWin/android_device_samsung_zerofltespr
It won't flash for me....it gets most of the way through and then it fails.
Euronymous88 said:
It won't flash for me....it gets most of the way through and then it fails.
Click to expand...
Click to collapse
What version of Odin are you using? I personally use the one linked above which worked fine. Make sure you have enabled OEM Unlocking under Dev options. Also, make sure that you don't bump the cable or anything while flashing I suggest that you just plug it in lay it on a flat surface and just let it run.
1619415 said:
What version of Odin are you using? I personally use the one linked above which worked fine. Make sure you have enabled OEM Unlocking under Dev options. Also, make sure that you don't bump the cable or anything while flashing I suggest that you just plug it in lay it on a flat surface and just let it run.
Click to expand...
Click to collapse
That's what I normally do. I've used Odin many times...I'm using the latest version of Odin. Just seeing if anyone else had the same problem.
tdhite said:
If the good folks that built the modified version would share the device tree, I can help unify it with the Edge ( I don't have an edge, but can help @nyfl2004 extract the necessary blobs, et al, to build the Edge in).
Did you start with this by chance? https://github.com/TeamWin/android_device_samsung_zerofltespr
Click to expand...
Click to collapse
I have already built it for the edge, please pm me on how you rooted!
Sent from my SM-G925P using Tapatalk
Euronymous88 said:
That's what I normally do. I've used Odin many times...I'm using the latest version of Odin. Just seeing if anyone else had the same problem.
Click to expand...
Click to collapse
You can just untar it and that will give you the image. For example, in linux:
Code:
tar xvf New_S6_Spr_TWRP_MM_Bootloader2.tar
That will give you a file called "recovery.img"
Then copy that file to your phone, adb shell in, type "su" at the shell prompt (which will ask you for permission, of course, so grant it); then 'dd' it to the recovery partition as described in the section "dd Install Method (Requires Root)" at https://twrp.me/devices/samsunggalaxys6sprint.html.
You don't need Odin to install TWRP in most cases.
Once you successfully flash TWRP...all you need to do for root is flash SuperSU 2.68.
So soon we will have the TeamSpr v2 rite ?
Sent from my SM-G920P using Tapatalk
TaNuXzx said:
So soon we will have the TeamSpr v2 rite ?
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
V3.0.0-1 we just added the "-1" that way you guys know that this is the updated and working version
1619415 said:
V3.0.0-1 we just added the "-1" that way you guys know that this is the updated and working version
Click to expand...
Click to collapse
i mean the rom . sorry ?
Sent from my SM-G920P using Tapatalk
I Installed thru Flashify,only Because the wife was on the computer gaming. It worked made a backup flashed xposed modules turned on now thanks.
Great work TeamSpr. Works great on my s6 phone. Thx
Sent from my SM-G920P using Tapatalk
Not taking, still on default recovery
Hi,
Just checking if others see this:
1) turn on oem unlocking (even off then on again to assure it's on);
2) load up Odin3 v3.10.7 (used this to flash twrp in LL, works fine, also used to return to stock and take OTA);
3) turn off R. Reset Time;
4) Flash New_S6_Spr_TWRP_MM_Bootloader2.tar
It just reboots to stock MM, then if I force to recover, it's still stock recovery.
?? Anyone have a clue on that one? I can get to stock recovery and reboot to system still, but sheesh -- no take of the Odin flash of TWRP? Not enough knowledge in my head around Odin for that one if anyone has some help.
tdhite said:
Hi,
Just checking if others see this:
1) turn on oem unlocking (even off then on again to assure it's on);
2) load up Odin3 v3.10.7 (used this to flash twrp in LL, works fine, also used to return to stock and take OTA);
3) turn off R. Reset Time;
4) Flash New_S6_Spr_TWRP_MM_Bootloader2.tar
It just reboots to stock MM, then if I force to recover, it's still stock recovery.
?? Anyone have a clue on that one? I can get to stock recovery and reboot to system still, but sheesh -- no take of the Odin flash of TWRP? Not enough knowledge in my head around Odin for that one if anyone has some help.
Click to expand...
Click to collapse
Turn on Reset time and try the Odin included in This zip