[RECOVERY][p4noterf] TWRP 3.1.1-0 touch recovery [2017-05-19]

[RECOVERY][p4noterf] TWRP 3.1.1-0 touch recovery [2017-05-19] - Galaxy Note 10.1 Original Development

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.

Will this work with N0813?
Also should i install it via goo?
Also THANKS!!!
Edit worked awesome!!!
Thanks again, no more buggy cwm!!!!

Yes, Working on GT-N8013
davidrules7778 said:
Will this work with N0813?
Also should i install it via goo?
Also THANKS!!!
Edit worked awesome!!!
Thanks again, no more buggy cwm!!!!
Click to expand...
Click to collapse
Works and Yes install through GOO is fine. Only issue experienced from the install so far is when in recovery trying to type or select sometimes creates double entries or backs out of the function completely. But aside from that it is working as expected.

hkeyman said:
Works and Yes install through GOO is fine. Only issue experienced from the install so far is when in recovery trying to type or select sometimes creates double entries or backs out of the function completely. But aside from that it is working as expected.
Click to expand...
Click to collapse
so awesome to have this on the note.
just wondering, does installing this through goo fix the problem we had with CWM root method where if you boot into recovery it would auto write a script to reinstall the standard recovery? right now i am rooted but because of this bug with the new firmware my CWM is gone and i haven't used the adb instructions to fix it.
once you use TWRP you'll never go back to CWM imo

knives of ice said:
so awesome to have this on the note.
just wondering, does installing this through goo fix the problem we had with CWM root method where if you boot into recovery it would auto write a script to reinstall the standard recovery?
once you use TWRP you'll never go back to CWM imo
Click to expand...
Click to collapse
Not sure, but i got out of that issue with the original clockwork.
Pretty sure it will though

Still rooted...
davidrules7778 said:
Not sure, but i got out of that issue with the original clockwork.
Pretty sure it will though
Click to expand...
Click to collapse
After installing TWRP and using recovery a few times and then rebooting back into system I am not seeing any root/unroot issues. All is working normally here. Which version of the Tablet are you running? I am on the GT-N8013.

hkeyman said:
After installing TWRP and using recovery a few times and then rebooting back into system I am not seeing any root/unroot issues. All is working normally here. Which version of the Tablet are you running? I am on the GT-N8013.
Click to expand...
Click to collapse
I am not having issues at all
Ask the other guy
Sent from a Baked Black Jelly Belly

What I am referring to is with the latest rooting method 2 and if you are on the latest firmware when you reboot the firmware automatically rewrites the cwm image. The only way to stop this is via adb check the instructions below that are to be used in the current method
0) Copy the SU/superSU zip file to your tablet.1) Boot into ODIN mode by holding volume down and power. Volume down is the one closest to power.2) Open ODIN on your computer, select the CWM tar.md5 file in the PDA slot, uncheck auto reboot.3) Hit start. It should flash recovery successfully4) Now you want to boot directly into CWM, or you'll lose it. So while holding down volume UP (the one farther from power), hold down the power button. When you see the Samsung Galaxy Note 10.1 logo, let go of power, or else you'll keep rebooting, but keep holding volume UP. Or at least that's what I had to do, which was kind of surprising coming from other Samsung devices.5) Once in CWM, flash the superSU zip file. Congratulations, you have root, but if you reboot now the firmware will nuke CWM. We don't want to have to flash it again, so let's remove the shell script that nukes CWM.6) Under mounts and storage in CWM, mount system.7) Back on your computer, run adb shell. If you forget to mount system it'll complain because it can't find sh, silly adb. For a second I thought Samsung didn't include sh out of the box and then I realized that makes no sense.8) Type su to become root9) rm /system/etc/install-recovery.sh
So anyways I personally don't know jack squat about adb so I am rooted but don't have cwm installed because it overwrite.
Flashing twrp with goo it flashes for me successfully it claims but when I reboot to recovery I still have stock recovery. I suspect because I didn't do the adb.instructions above that this is the problem
I was hoping flashing this would automatically remove that script you need to remove in adb

knives of ice said:
What I am referring to is with the latest rooting method 2 and if you are on the latest firmware when you reboot the firmware automatically rewrites the cwm image. The only way to stop this is via adb check the instructions below that are to be used in the current method
0) Copy the SU/superSU zip file to your tablet.1) Boot into ODIN mode by holding volume down and power. Volume down is the one closest to power.2) Open ODIN on your computer, select the CWM tar.md5 file in the PDA slot, uncheck auto reboot.3) Hit start. It should flash recovery successfully4) Now you want to boot directly into CWM, or you'll lose it. So while holding down volume UP (the one farther from power), hold down the power button. When you see the Samsung Galaxy Note 10.1 logo, let go of power, or else you'll keep rebooting, but keep holding volume UP. Or at least that's what I had to do, which was kind of surprising coming from other Samsung devices.5) Once in CWM, flash the superSU zip file. Congratulations, you have root, but if you reboot now the firmware will nuke CWM. We don't want to have to flash it again, so let's remove the shell script that nukes CWM.6) Under mounts and storage in CWM, mount system.7) Back on your computer, run adb shell. If you forget to mount system it'll complain because it can't find sh, silly adb. For a second I thought Samsung didn't include sh out of the box and then I realized that makes no sense.8) Type su to become root9) rm /system/etc/install-recovery.sh
So anyways I personally don't know jack squat about adb so I am rooted but don't have cwm installed because it overwrite.
Flashing twrp with goo it flashes for me successfully it claims but when I reboot to recovery I still have stock recovery. I suspect because I didn't do the adb.instructions above that this is the problem
I was hoping flashing this would automatically remove that script you need to remove in adb
Click to expand...
Click to collapse
Actually, you don't need to use ADB, but that was just the fastest way to do it for me. The script doesn't remove root so you can let it boot up and delete the sript using a root file explorer (these days I'm partial to Solid Explorer Beta). But you'll just have to flash CWM a second time if you let it boot up once.

No recovery found using GooManager
I tried installing TWRP through GooManager, but after several minutes of 'Looking for recoveries...' I guess it gave up
Device: GT-N8000 (EU WiFi+3G).

iofthestorm said:
Actually, you don't need to use ADB, but that was just the fastest way to do it for me. The script doesn't remove root so you can let it boot up and delete the sript using a root file explorer (these days I'm partial to Solid Explorer Beta). But you'll just have to flash CWM a second time if you let it boot up once.
Click to expand...
Click to collapse
Thanks.
Seems like goo is down again so as soon as its up we will see if this works

LayZeeDK said:
I tried installing TWRP through GooManager, but after several minutes of 'Looking for recoveries...' I guess it gave up
Device: GT-N8000 (EU WiFi+3G).
Click to expand...
Click to collapse
Did u go into goos menu and select install open recovery?

davidrules7778 said:
Did u go into goos menu and select install open recovery?
Click to expand...
Click to collapse
Of course. I pressed 'Install OpenRecoveryScript', pressed 'Yes', and a dialog box said 'Looking for recoveries...' for several minutes after which it disappeared. But knives of ice says that something is wrong with GooManager.

LayZeeDK said:
Yes, I pressed 'Install OpenRecoveryScript', pressed 'Yes', and a dialog box said 'Looking for recoveries...' for several minutes after which it disappeared. But knives of ice says that something is wrong with GooManager.
Click to expand...
Click to collapse
Yeah the goo servers seem to be down has happened many times in the past. I can't even login to my goo supporter account

There are download links for a mirror and instructions for a manual install on our website.

Dees_Troy said:
There are download links for a mirror and instructions for a manual install on our website.
Click to expand...
Click to collapse
Awesome I got it working now you definitely must delete the file referenced above if you have recently rooted on the latest firmware.
You can also manually flash with mobile Odin if you don't want to use adb like myself while goo is down. Just rename the file to recovery.img

Wanted to say thanks, Dees_Troy! Just picked up a WiFi GT-8013 and this is the first thing I put on it. If you need any help testing or whatnot, feel free to give me a shout and I will test you stuff

Finally got something to flash on this. Anyways it seems like something is messed up with the touchscreen in twrp recovery. Its either much too sensetive or won't scroll at all. Its near impossible to pick a file to flash right now for me anyways if its in a specific folder like downloads
Anyone else?

Yes, i´ve got the same problem, needed 10 minutes yesterday to pick up all the files for cm10 flash...

Same thing here, although I eventually got it to flash. CitizenX, if you flashed CM10, could you report whether your S Pen still works in the CM10 discussion thread? Mine just stopped working with the same errors I was getting last time the S Pen stopped working for me.

Related

[RECOVERY][otter] TWRP 3.1.0-0 touch recovery [2017-03-10]

[RECOVERY][otter] TWRP 3.1.1-0 touch recovery [2017-05-19]
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.

id love to try this out, but from the comments on the site, it appears that the commands listed do not work... also i have a mac so its probably different.

Sweet! I'll have to try this out!

I just gave the new version a quick run around the block...
PROS: The distribution is no longer a boot image that forces a flash of the old FFF 1.0 along with TWRP. It's now an actual recovery image that can be flashed through fastboot like... "fastboot flash recovery twrp-fire-2.1.0.img"
CONS: Even though there are some more reboot options in this new version, they are all still broken. Just as in 2.0.0, none of the reboot options (system, recovery, bootloader... I'm assuming the last one is supposed to boot into fastboot mode) will reset the bootmode accordingly before the device is restarted. That makes these options pretty useless as the device will still continue to boot in the previous bootmode. So, the TWRP bootloops will continue to plague new users who have no idea how to get it to boot to the system.... bummer.

I love that we got this! Buuuuttttt I like 2.0 just fine. Its stable. It works. love to see progress though.
Sent from my Kindle Fire using XDA

its great to see progress, but as kinfaun said reboot is still broken.
Sent from my HTC Glacier using xda premium

smirkis said:
its great to see progress, but as kinfaun said reboot is still broken.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
thats a deal breaker for me... thanks for the update tho

I spoke with deestroy n were gonna try to get it resolved. yay lol
they don't have our device so its hard to know what doesn't work. looking forward to testing the update
Sent from my HTC Glacier using xda premium

smirkis said:
I spoke with deestroy n were gonna try to get it resolved. yay lol
they don't have our device so its hard to know what doesn't work. looking forward to testing the update
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Sweet id switch back if it was fixed i like how its skinable

i cant install any zip files i get unknown md5 error just rooted tonight

nckfrs said:
i cant install any zip files i get unknown md5 error just rooted tonight
Click to expand...
Click to collapse
I just tried playing around with the new version some more and I can confirm the above...
Here's what I get from TWRP's Install section for the few ROMs I tried to test flash.
Code:
-- Verify md5 for /sdcard/update-cm7-wipeall.zip
-- No md5 file found, ignoring
-- Installing /sdcard/update-cm7-wipeall.zip ...
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "blaze" || getprop("ro.build.product") == "blaze"
E:Error in /tmp/sideload/package.zip
(Status 7)
* Verifying filesystems...
* Verifying partition sizes...
Error flashing zip '/sdcard/update-cm7-wipeall.zip'
This version is really not ready for use. Hang on to your version 2.0.0 for at least a little while longer.

While I agree its not ready it did work for me to make a back up and then install Hashcode's test rom and restore a back up another user posted for us.

Reboot to system works perfectly fine for me, and has in previous versions as well.

Reboot to system works fine for me to. Always has.
Sent from my LG-P999 using Tapatalk 2

treUse said:
Reboot to system works perfectly fine for me, and has in previous versions as well.
Click to expand...
Click to collapse
dw9906 said:
Reboot to system works fine for me to. Always has.
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
Yeah it will, until you assign the bootmode outside of using the power button from firefirefire (in other words, use fastboot, adb or 'reboot recovery' from a rom to set the bootmode) the reboot wrappers won't set it back. It is actually a relatively simple solution and Smirkis' is familiar with what's required if he is talking to the OP I would expect a solution for this.

treUse said:
Reboot to system works perfectly fine for me, and has in previous versions as well.
Click to expand...
Click to collapse
dw9906 said:
Reboot to system works fine for me to. Always has.
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
If you used the power button to get into recovery while FFF was loading, reboot to system will work fine. That's not what's being discussed here.
If you got to recovery that way, the bootmode was never changed and stayed (presumably) on 4000. So, hitting the reboot from within TWRP will continue to boot in normal mode and it "seems" to work fine.
Try setting the bootmode to recovery (5001) and restart the device to get to TWRP. Then if you try rebooting into the system, it will go back into TWRP because TWRP does not change the bootmode back to normal (4000) before attempting to reboot into the system.
The same problem exists for all the reboot options in 2.1.0... whether normal, recovery, or bootloader, it will not change the bootmode to the appropriate value before restarting the device. As a result, the device will just reboot using whatever bootmode is already set.
EDIT: What Sblood86 said above... I'm just longer winded.

I knew what you meant, but that's not what you explained in your first post. Had you been this specific in your initial post then this conversation would have never happened.
On another note, this recovery might as well be forgotten about. Doesn't seem like they are ever going to fix it completely.
EDIT: Didn't mean for that to sound like i was being rude to kinfauns. That's not how i meant it to be.
Sent from my LG-P999 using Tapatalk 2

dw9906 said:
I knew what you meant, but that's not what you explained in your first post. Had you been this specific in your initial post then this conversation would have never happened.
On another note, this recovery might as well be forgotten about. Doesn't seem like they are ever going to fix it completely.
EDIT: Didn't mean for that to sound like i was being rude to kinfauns. That's not how i meant it to be.
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
I wasn't offended by your post, so you shouldn't take this post that way either... but I don't think you read the thread very carefully before you posted. I think I was fairly clear about what the problem entailed in my first post of this thread. I made it a point to mention that TWRP does not set the bootmode properly before rebooting. In addition, smirkis noted that he's gotten the developer's ear in getting some problems fixed, so things are looking up in terms of getting past these issues.
Furthermore, TWRP can't simply be "forgotten about" because the super majority of articles on the Internet detailing steps in modifying the Kindle Fire mention TWRP. New users will continue to use TWRP just for the fact that it's simply the more recognized recovery program of the two we have available.
FWIW, I'm more hopeful than ever TWRP will get fixed and continued to be developed.

I really do hope it gets fixed. I really like the themeing capabilities. It's a great recovery, just doesn't seem to have much support.
Sent from my LG-P999 using Tapatalk 2

clockwork recovery ftw.

[RECOVERY][d2tmo] TWRP 3.1.1-0 touch recovery [2017-05-19]

Cha-Ching, THANK YOU TEAM-WIN! Thanks a Bunch been waiting for an official - will test if SD card slot is working.
UPDATE: Works Great!

Confirmed reading from the sd card. Diddnt try to flash from sd card, but it reads it. And the interface is nice in comparison. All I did was fix permissions and it worked.
Sent from my SG3 using GSM (Team Sonic) + Trinity
http://supercentral.net

Awesome!!! Been using TWRP on my Nook for awhile now. Love it! Thanks for this.

How do u make it back up to ext sdcard? Also anyone know the commands for terminal emulator...thanx in advance
Edit....nvmd figured it very nice ty!

sarni84 said:
How do u make it back up to ext sdcard? Also anyone know the commands for terminal emulator...thanx in advance
Edit....nvmd figured it very nice ty!
Click to expand...
Click to collapse
Mind sharing the info. Thanks.
Sent from a Galaxy far far away

now that this is official can we flash cm9 without changing the script?

cwalker0906 said:
now that this is official can we flash cm9 without changing the script?
Click to expand...
Click to collapse
Yeah, is this able to flash cm9 correctly?

neotoky said:
Mind sharing the info. Thanks.
Sent from a Galaxy far far away
Click to expand...
Click to collapse
It's super easy ! When you click backup, there is two boxes at the bottom saying "Use external SD" and "Use Internal Storage". Use internal is by default.

I was under the impression that TWRP supported adb in recovery, though this version does not seem to work. Is that something that is being worked on, or just not gonna happen?

lumbu said:
I was under the impression that TWRP supported adb in recovery, though this version does not seem to work. Is that something that is being worked on, or just not gonna happen?
Click to expand...
Click to collapse
Worked just fine for me.
mounted /system and pushed a few files successfully.

neotoky said:
Mind sharing the info. Thanks.
Sent from a Galaxy far far away
Click to expand...
Click to collapse
Also to install its even easier. Download goomanager from market its free. Then go into it hit your menu button on phone then hit " install open recovery script" .....it will download and install the latest version (which is this one) for u and as far as using external sd goes for backups. When u hit backup just select external

overground said:
Worked just fine for me.
mounted /system and pushed a few files successfully.
Click to expand...
Click to collapse
Yep, my bad. Needed to install the naked adb drivers instead of the Samsung ones I first installed. Is that what you have installed?

lumbu said:
Yep, my bad. Needed to install the naked adb drivers instead of the Samsung ones I first installed. Is that what you have installed?
Click to expand...
Click to collapse
My adb driver installation for this device was such a nightmare (Win7 64).
This is what finally worked for me (follow the link trail).
http://forum.xda-developers.com/showpost.php?p=27921718&postcount=278

Took the plunge and just flashed CM9 nightly with no problems. Cheers!

Thank you guys, this is much better than the touch CWM!
The SD card option is terrific!

Does flashing this with GooManager trip the flash counter?

hypmatize said:
Does flashing this with GooManager trip the flash counter?
Click to expand...
Click to collapse
Does it matter anymore?
There is already a way to reset the flash counter.

ipaq_101 said:
Does it matter anymore?
There is already a way to reset the flash counter.
Click to expand...
Click to collapse
Yeah true... but why trip it when you don't have to

hypmatize said:
Does flashing this with GooManager trip the flash counter?
Click to expand...
Click to collapse
No, only flashing a non-stock file through Odin increases the flash counter. Nothing you do on your phone, including Mobile Odin, trips the counter.

[RECOVERY][manta] TWRP 3.1.1-0 touch recovery [2017-05-19]

Reserved

Reserved.

Works for me. Thanks!

Fixed adb and added USB OTG support. I'll be looking to upscale the theme and add decrypt support when I have more time.

Thanks for this, Dees. I'll see to it that one of my writers puts this on the front page.

Dees_Troy said:
Fixed adb and added USB OTG support. I'll be looking to upscale the theme and add decrypt support when I have more time.
Click to expand...
Click to collapse
Forgive my ignorance, but does this also root the device, or do I need to root first?
The ability to backup to OTG USB is excellent - thanks.

Lumsdoni said:
Forgive my ignorance, but does this also root the device, or do I need to root first?
The ability to backup to OTG USB is excellent - thanks.
Click to expand...
Click to collapse
Root after installing TWRP by flashing SuperSU in TWRP.

Awesome thanks just wondering, does this have the random reboot issue like cwm?
Sent from my Galaxy Nexus using Tapatalk 2

draco259 said:
Awesome thanks just wondering, does this have the random reboot issue like cwm?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
It doesn't. This recovery works perfectly, other than the theme issue. CWM has also been fixed by damien667.

Man i LOOVEEE TWRP... thanks for this, cant wait to try it tonight

willverduzco said:
It doesn't. This recovery works perfectly, other than the theme issue. CWM has also been fixed by damien667.
Click to expand...
Click to collapse
Awesome thanks for the info
Sent from my Galaxy Nexus using Tapatalk 2

willverduzco said:
Root after installing TWRP by flashing SuperSU in TWRP.
Click to expand...
Click to collapse
I am confused... how can you give goomanager root access if the tab isn't rooted already?

You can't. You will have to install it through fastboot.
Sent from my GT-N7100 using xda app-developers app

draco259 said:
Awesome thanks just wondering, does this have the random reboot issue like cwm?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I was able to figure out what was needed to prevent the reboot. I pushed my device configuration files to the team win github if you really want to take a look or compile your own. Good news is that I can compile from source without having to repack manually.

Randomwalker said:
You can't. You will have to install it through fastboot.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
ah... ok.. i must have gotten confused when one of the admins said to root it after installing twrp using goomanager..
EDIT: So these direction from post #1 are totally wrong? if randomwalker is correct?
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:

That's if you are already rooted, go with the or option.
Sent from my Galaxy Nexus using Tapatalk 2

I installed and got into TWRP fine the first time.Now I'm stuck in a boot loop. It has been sitting for 30 minutes with just the X flashing.
I can get into the bootloader and TWRP fine but the system will not boot just sits with the flashing X..

Mike02z said:
I installed and got into TWRP fine the first time.Now I'm stuck in a boot loop. It has been sitting for 30 minutes with just the X flashing.
I can get into the bootloader and TWRP fine but the system will not boot just sits with the flashing X..
Click to expand...
Click to collapse
Did you just unlock it? If so, reboot into TWRP and go to the wipe section. Format Data & Wipe Cache & you will be good to go.

Same as user above with bootloops. I tried wiping cache/delvik and also factory reset but it says failed everytime in red at the top of TWRP. Im lost. Does the same with stock CWM Touch also. I downloaded the pre rooted factory rom but cannot access sd through mounting to flash that rom either. An ideas as far as sending the file to sd using adb commands?

[RECOVERY][find7] TWRP 3.1.1-0 touch recovery [2017-05-19]

Reserved
Starting with version 2.7.1.1, we're now doing a unified build for both the 1080p 7a and the 1440p devices. This means the same recovery image works on both devices and will provide you with the proper stock theme for your display. Of course, you can still install a custom theme if you like.
Link to device specific page on our website
Direct link to downloads folder for current / past versions

first.
friggin sweet...

noice, im rooted and haz twrp

Thanks! Seems to install and run fine. :victory:

Waiting for my preorder

Dees_Troy said:
Currently only officially support the Find 7a with the 1080p screen.
Link to device specific page on our website
Direct link to downloads folder for current / past versions
Click to expand...
Click to collapse
I was gonna ask which find 7 this supports. Thanks!!
Sent from my SGH-T889 using XDA Premium 4 mobile app

CAN someone give me a backup of ROM
I buy my find 7a in china And no playstore ans french langage on it
Actually i manage to root via chineese forum And install playstore And turn 80 per 100 of thé phone ni french with morelocale2
But i want thé international ROM to get 100 per 100 french
If someone CAN help
Thanks

i can not use this to flash stock rom
来自我的 X9007 上的 Tapatalk

Dees_Troy said:
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[RECOVERY][Find7] TWRP 2.7.0.0 touch recovery [2014-04-14], a Tool/Utility for the Oppo Find 7
Contributors
Dees_Troy, bigbiff
Version Information
Status: Stable
Current Stable Version: 2.7.0.0
Stable Release Date: 2014-04-14
Created 2014-04-15
Last Updated 2014-04-14
Click to expand...
Click to collapse
Anybody have any idea how to change the language in app drawer menu settings to english. I have changed the default language in settings to english. But that doesn't help change the language in the settings menu of app drawer. Please help !

Nice!
Sent from my HTC One using Tapatalk

Sorry for the question
I know this might be a bad question, but can someone explain to me or send me a link on how i can install this recovery? I'd rather as stupid questions that brick my phone

troysyx said:
I know this might be a bad question, but can someone explain to me or send me a link on how i can install this recovery? I'd rather as stupid questions that brick my phone
Click to expand...
Click to collapse
Download the recovery file: http://techerrata.com/browse/twrp2/find7a
Install the Google ADB / Fastboot drivers (Windows http://goo.gl/ZWGG)
Hold in Power and Vol Up to put your Find 7 into Fastboot mode.
Plug your USB cable into your phone and computer.
Type fastboot devices.
You should see your phone listed. If you're do proceed.
To just boot the recovery: fastboot boot openrecovery-twrp-2.7.0.0-find7a.img
To install / flash the recovery: fastboot flash recovery openrecovery-twrp-2.7.0.0-find7a.img

rayfin said:
Download the recovery file: http://techerrata.com/browse/twrp2/find7a
Install the Google ADB / Fastboot drivers (Windows http://goo.gl/ZWGG)
Hold in Power and Vol Up to put your Find 7 into Fastboot mode.
Plug your USB cable into your phone and computer.
Type fastboot devices.
You should see your phone listed. If you're do proceed.
To just boot the recovery: fastboot boot openrecovery-twrp-2.7.0.0-find7a.img
To install / flash the recovery: fastboot flash recovery openrecovery-twrp-2.7.0.0-find7a.img
Click to expand...
Click to collapse
Awesome! Thank you so much

Dees_Troy said:
DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our website!
Click to expand...
Click to collapse
FYI, I tried to install it with TWRP Manager. It stopped at the "Downloading Image" status bar on my F7a. I tried to download it manually, and it worked. Probably some write permission issues.
I ended up flashing it with fastboot and it works like a charm.
Thank you Guy´s!

Any possibilities to flash on Mac OSX?

betold said:
FYI, I tried to install it with TWRP Manager. It stopped at the "Downloading Image" status bar on my F7a. I tried to download it manually, and it worked. Probably some write permission issues.
I ended up flashing it with fastboot and it works like a charm.
Thank you Guy´s!
Click to expand...
Click to collapse
same here for me.. can't download with TWRP Manager

TWRP Nightmare
Every time I install TWRP, it gives me problems. I was gonna flash cm11 using TWRP, so I flashed it via fastboot to my phone. Now, whenever I boot the phone, it boots straight into the recovery. Even if I boot into system from recovery, it still boots back into TWRP. I tried both versions 2.7, and 2.7.1, but the same result. This isn't even the weird part. Whenever I flash another recovery, like CWM or PhilZ, if I reboot my phone, it goes BACK to TWRP recovery! Wtf? When I flash OPPO's recovery, the phone gets stuck at the OPPO logo forever. What could be wrong? If I need to provide more info, let me know. I didn't think flashing roms and recoveries on this phone would be so frustrating. I never had this much trouble flashing recoveries and ROMs on my Galaxy S2. Any help is appreciated. Thanks!

Anyone else having problems with the time being displayed in TWRP? My backups are time stamped 1970 as well. I had this problem on Gummy's recovery as well so maybe it's the phone's internal clock that is off?
*edit*
googled and found partial answers.

azeem40 said:
Every time I install TWRP, it gives me problems....
Any help is appreciated. Thanks!
Click to expand...
Click to collapse
I'd say start fresh and work through it.
Do a fresh fastboot flash and provide that log/entry here.
Then after you boot TWRP again, wipe system/data/cache/davlik, flash your ROM and before you reboot provide the recovery.log (from Settings or Advanced I believe, will copy to your SD card).
If you still aren't able to boot into Android I'm guessing we can find the problem there there.

[TOOL/UTILITY][TWRP][RECOVERY] TWRP 3.0.2-0 TeamWin Recovery Project 5/11

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

Develop Bugs

welcome