[RECOVERY][jflteatt] TWRP 3.1.1-0 touch recovery [2017-05-19] - AT&T Samsung Galaxy S 4 Android Development

[RECOVERY][jflteatt] TWRP 3.1.1-0 touch recovery [2017-05-19] - AT&T Samsung Galaxy S 4 Android 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.

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

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][toroplus] TWRP 3.0.0-0 touch recovery [2016-02-06]

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.

Nice. Had this on my nexus s 4g and loved it.
Sent from my Galaxy Nexus using xda premium

Will nandroids from other recovey work??
GNEX

Definitely will be keeping an eye on this. Great work.

I can stand bugs, but taking a full minute may be a but much, considering how often I am in recovery. I'm really happy to see it here, though, and can't wait for a more finished product.

fcisco13 said:
Will nandroids from other recovey work??
GNEX
Click to expand...
Click to collapse
From past experience, no. Different file format used in the backup from this recovery and clockwork.

gunna give this a shot. TWRP was awesome on my E3D
EDIT: Working good so far. Screen formatting is a little odd, but not a big deal. The 60 second boot up was a little odd too, but worth it.

Back up in 76 seconds!! File manager!! Win!!
GNEX

I'll definately be following this. I use Boot Manager so I'm only in CWM if a rom wont boot. Once the 60 second issue is fixed, this will be a daily recovery for me. Thanks!
Sent from my Galaxy Nexus using Tapatalk

Using this now and even with the bugs it kicks ass, thanks!
Sent from my Galaxy Nexus using XDA

same here once the 60 secs is gone this will be my new recovery!

For whatever reason, mine didnt take 60s to come up. I wasnt timing it but it was a reasonable amount of time.

Thanks Dees_Troy and the rest of the TeamWin team, I've been hoping to get a chance to try out TWRP, it sounds very promising! I'm looking forward to future releases that iron out the kinks. Thanks again!

What does it do that clockworkmod doesn't? Except take forever to load. No one's gonna wait 60 seconds to go in recovery. Booting all the way into Android doesn't even take that long. And clockworkmod touch has been around for a while so get that if you want the touch feature.

weirddan455 said:
What does it do that clockworkmod doesn't? Except take forever to load. No one's gonna wait 60 seconds to go in recovery. Booting all the way into Android doesn't even take that long. And clockworkmod touch has been around for a while so get that if you want the touch feature.
Click to expand...
Click to collapse
The interface is 100x better.... And are you in such a hurry that you can't wait a minute to boot into recovery? It's not that serious.
I've never liked CWM so this is a no brainer for me. Plus CWM Touch is just the standard CWM with added touch. Seems cheap to me. TWRP 2 is a completely touch orientated recovery, built from the ground up to do so.
Sent from my Galaxy Nexus using Tapatalk 2

weirddan455 said:
What does it do that clockworkmod doesn't? Except take forever to load. No one's gonna wait 60 seconds to go in recovery. Booting all the way into Android doesn't even take that long. And clockworkmod touch has been around for a while so get that if you want the touch feature.
Click to expand...
Click to collapse
Ummm..
Que files to flash.
Half the time (if not faster) to backup/restore.
That alone does it for me.
GNEX

Proper working builds (no more preview build) are now available!

Sweet thanks!
Sent from my Galaxy Nexus using Tapatalk 2

Every zip that I try to flash errors out and fails. Using a verizon gnex.
*update* I flashed the recovery through fastboot and it works fine now. Not sure if something is up with your recovery zip.

There were a few problems with installing zips on the builds I uploaded earlier. If you aren't sure, go ahead and re-update just in case. Sorry.

[RECOVERY][toro] TWRP 3.0.0-0 touch recovery [2016-02-06]

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.

I really love this recovery.

This recovery kicks burt
Sent from my Galaxy Nexus using xda premium

Thank you much. Love having touch again

did 2.1.2 add any thing that makes it worth flashing form 2.1.1?
i guess the major reason for it was the sprint phone?

gi812 said:
did 2.1.2 add any thing that makes it worth flashing form 2.1.1?
i guess the major reason for it was the sprint phone?
Click to expand...
Click to collapse
Bug fix. Apparently 2.1.1 would only back-up and not restore
Sent from my Galaxy Nexus using XDA

This recovery is working flawlessly
Sent from my Galaxy Nexus using Tapatalk 2

cowsquad said:
This recovery is working flawlessly
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Except for it refuses to flash pure aosp build 5
Sent from my Galaxy Nexus using xda premium

I had to switch back to CWM bc I ran into too many ROMs refusing to flash. Hope this issue can be remedied soon.

zedorda said:
I had to switch back to CWM bc I ran into too many ROMs refusing to flash. Hope this issue can be remedied soon.
Click to expand...
Click to collapse
Sent from my Galaxy Nexus

zedorda said:
I had to switch back to CWM bc I ran into too many ROMs refusing to flash. Hope this issue can be remedied soon.
Click to expand...
Click to collapse
Same here. Would really like to be able to use this recovery. Hopefully it will be good to go soon.

PacerguyDon said:
Same here. Would really like to be able to use this recovery. Hopefully it will be good to go soon.
Click to expand...
Click to collapse
I've been using this recovery without issues.
Sent from my Galaxy Nexus using Tapatalk 2

I hope the dev didn't drop working on this one for the sprint version. I really hate the CWM recovery and would love to be able to count on this one but it still fails to flash most of the ROMs I have tried.

Yes.... I have had this problem as well and have switched back to CWM.
Sent from my Galaxy Nexus using Tapatalk 2

zedorda said:
I hope the dev didn't drop working on this one for the sprint version. I really hate the CWM recovery and would love to be able to count on this one but it still fails to flash most of the ROMs I have tried.
Click to expand...
Click to collapse
Sprint sucks anyways lol jk mine works very well on VERIZON NEXUS
Sent from my Galaxy Nexus using Tapatalk 2

Loving this recovery, the zip queue is awesome!

tacosrdelicioso said:
This recovery kicks burt
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Who's burt
Sent from my Galaxy Nexus using xda premium

BlackHoleSlam said:
Who's burt
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Duh!!! "Smokey and the bandit" "Cannonball run"
GNEX

crimson12 said:
Loving this recovery, the zip queue is awesome!
Click to expand...
Click to collapse
What is zip queue btw? What does it do?
Sent from my Galaxy Nexus using Tapatalk 2

fcisco13 said:
Duh!!! "Smokey and the bandit" "Cannonball run"
GNEX
Click to expand...
Click to collapse
oh my bad where are the themes for twrp
Sent from my Galaxy Nexus using xda premium

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

sweet, i had the t-mobile one installed but nice to know its official for ATT.

Cool

Installed on my d2can via GooManager; Works well, but the "Mount as USB Storage" option doesn't work on either internal or external storage.

Thank you for the recovery for this device I was painfully using cwm until this got released I am very glad it is out now,I see only external works but its alright because I put most files on there to save internal memory space...Hope to see this device progress even more

sk8trix said:
Thank you for the recovery for this device I was painfully using cwm until this got released I am very glad it is out now,I see only external works but its alright because I put most files on there to save internal memory space...Hope to see this device progress even more
Click to expand...
Click to collapse
Actually internal works.. Just that it's path is a bit odd.. Look in /data/media and there is your internal storage. I haven't tried to back up to internal yet but I did just do a backup to my extSD.
I haven't tried mount usb storage at all yet but I will when I go home. Nor have I tried a restore yet. But will soon.
Thanks Dees Troy maybe this will make fix people with IMEI troubles (well not ones who have already lost it but if CWM was the culprit then perhaps TWRP is all we need to avoid it)
Edit: Dees Troy have you any thoughts on including an EFS backup similar to what bigbiff has in TWRP 2.2.1.1 for the i717? That might also be helpful just a thought thought since we are not 100% certain of the EFS partition containing IMEI info anyway. However it may be something to consider. Thanks again Dees you da man :thumbup: :beer:
Sent from my SAMSUNG-SGH-I747 using xda premium

has this been tested for any imei loss? i only as bc im scared to change my current CWM version for fear of imei loss

Woot. My favorite recovery is now officially supported by team win! Installed from goo manager. Imei still intact.

kurtiskobain said:
has this been tested for any imei loss? i only as bc im scared to change my current CWM version for fear of imei loss
Click to expand...
Click to collapse
We won't know until people here flash some roms around... Best way to lose imei seems to be flashing cm9 or 10 then going back to a nandroid backup or stock.. At least that's the common element in the spread sheet

Narcistic said:
We won't know until people here flash some roms around... Best way to lose imei seems to be flashing cm9 or 10 then going back to a nandroid backup or stock.. At least that's the common element in the spread sheet
Click to expand...
Click to collapse
Just made a backup with twrp installed cm10 and booted it. Then restored the backup. Imei still intact.

I have this issue when trying to install the recovery from the Goo Manager market app.
"no recovery were found for your device" (AT&T S3)

gunnyman said:
Just made a backup with twrp installed cm10 and booted it. Then restored the backup. Imei still intact.
Click to expand...
Click to collapse
It's not guaranteed loss of imei just seems to be the trend

Just did the same thing and still got my imei. Thank goodness! It's possible that twrp might be the way to go.
Thanks guys for supporting our phone!
stock rooted and rocking kt747 kernel...still got my imei

Narcistic said:
It's not guaranteed loss of imei just seems to be the trend
Click to expand...
Click to collapse
nothing's guaranteed of course just reporting so far so good.

Couldn't resist testing for IMEI loss....
I installed TWRP recovery via Goo app, backed up CM10 (installed via CWM) with TWRP, used TWRP to flash CWM recovery, restored a CWM stock deodexed nandroid, reinstalled TWRP to make a nandroid of the stock ROM, restored the stock via TWRP to ensure it worked and then restored CM10, which is what I've been running since 7/20. I tested for IMEI loss along the way and (so far) it's still there.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

timeToy said:
I have this issue when trying to install the recovery from the Goo Manager market app.
"no recovery were found for your device" (AT&T S3)
Click to expand...
Click to collapse
Same issue here. On the TeamWin site the only S3 option is for verizon.

I don't see any installed roms in my internal sd card when in recorvery
Sent from my SAMSUNG-SGH-I747 using xda premium

Narcistic said:
We won't know until people here flash some roms around... Best way to lose imei seems to be flashing cm9 or 10 then going back to a nandroid backup or stock.. At least that's the common element in the spread sheet
Click to expand...
Click to collapse
That means that I must've been lucky then. I had cm10 then decided to go back to my nandroid of stock. I still have my imei after flashing from that stock nandroid to aokp then back to a deodexed stock rom. I used cwm every time.
via my Samsung Galaxy S III

I really dont think CM10/9/AOKP are the culprits for lost IMEI, in fact CWM alone may not even be to blame, I think its a combination of factors that can cause IMEI loss, one thing I think is how CWM is flashed to the phone, I've personally only used ADB to flash CWM to the phone, and havent (thank god) experienced the IMEI loss issue, however there have been reports that flashing CWM via odin and then flashing CM9/10/AOKP from stock causes IMEI loss...I'm pretty sure its quite a random occurrence though.

djkinetic said:
I really dont think CM10/9/AOKP are the culprits for lost IMEI, in fact CWM alone may not even be to blame, I think its a combination of factors that can cause IMEI loss, one thing I think is how CWM is flashed to the phone, I've personally only used ADB to flash CWM to the phone, and havent (thank god) experienced the IMEI loss issue, however there have been reports that flashing CWM via odin and then flashing CM9/10/AOKP from stock causes IMEI loss...I'm pretty sure its quite a random occurrence though.
Click to expand...
Click to collapse
Losing imei is very very very rare or you would see rom threads full of crying... Cm and aokp are probably not the culprits but it's so far the only thing other than cwm that seems to be reoccurring in the occurrences that imei does disappear. Usually it seems by people using nandroid backup somewhere before or after flashing cm9/10

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

Reserved!

Thank you sir!
:laugh:
---------- Post added at 10:43 PM ---------- Previous post was at 10:39 PM ----------
I'm getting no recoveries found for device...
---------- Post added at 11:06 PM ---------- Previous post was at 10:43 PM ----------
Got the tar from goo thx
Working fine!
Sent from my SGH-T889 using Tapatalk 2

This is great.

awesome

It just keeps getting better and better Is it fine if I just install it from the Goo app even though i'm on stock recovery but rooted?

whytechapel_x said:
It just keeps getting better and better Is it fine if I just install it from the Goo app even though i'm on stock recovery but rooted?
Click to expand...
Click to collapse
That's what I did - worked just fine.

will also work if your on the cwm based recovery in the other development forum, before anyone asks.
this weekend we will probably see a crap load of roms released

That was quick. Awesome.

Great job. And confirmed working with 64-gb SD.
Thanks.
Sent from my SGH-M919 using xda premium

thx
Awesome - was waiting for this with baited breath.
Any reason why i cant flash this directly into place with odin, then dump superusersu 1.25 into place?
Their recommended method of app install on a rooted device requires an odin step, or a root exploit anyways - and I'd rather go direct - just too chicken $h1t to be first.
======Edit========
Found my huevos and did it
perfect install
stock -> odin twrp 2.5 -> reboot recovery -> superusersu1.25.zip -> twrp fix perms -> reboot -> golden
and now restoring crap via TiBkup, then debloating.

First & only Recovery that works on my Tmob GS4
I had to wait 3 WHOLE DAYS with my newest toy before I could make even one backup
because the stock 3e is a tiny worthless tool and that rainbow text thing was so tiny. Agat63
and I worked together for a few hours but even though he has one of his great recovery tools
working on the Sprint GS4, couldn't get it to even load via ODIN on my Tmob GS4.
Then like a gift from above, TWRP appeared on this forum.
Downloaded Goo from app store, followed the OP and in seconds ... MAGIC!
Bottom Line: This recovery is fantastic on my SGH-M919 and made
my first full backup without a hiccup.
Thank you TEAMWIN !
Glenn

weltwon said:
that rainbow text thing was so tiny
Click to expand...
Click to collapse
That's been fixed EDIT: pretty much always; OUDHSR is not only bigger and not "rainbow" unless you want it, but touch-enabled.
Dees, thanks for the official port! Options are great.

I can confirm flashing directly with Odin works. I am not rooted yet but plan on flashing SuperSU next after a backup.
What should I include when doing a backup? Recovery? EFS?

Wow, things are coming along quickly. Installed in minutes and crated a backup. Thanks!
Sent from my SGH-M919 using Tapatalk 2

k0nane said:
That's been fixed since 1:52pm CST today; OUDHSR is not only bigger and not "rainbow" (again, blame Shabby!) unless you want it, but touch-enabled.
Dees, thanks for the official port! Options are great.
Click to expand...
Click to collapse
actually it was fixed the night it was released, hence why you posted afterwards saying to redownload if you wanted bigger text...

shabbypenguin said:
actually it was fixed the night it was released, hence why you posted afterwards saying to redownload if you wanted bigger text...
Click to expand...
Click to collapse
Well, that, too.

I ran a backup as soon as I installed..Everything went smooth...I checked to see if the file was saved to either phone or extsd, was saved to phone at 2.4GB..
I moved the file to my extsd just for storage...Now if I want to do a restore im sure I have to move the file back to phone...or do I?
Secondly is there a way or will there be a way to save to extsd?
Thnx....
DISREGARD POST!!!!!!!!!!!!!
I went back into TWRP after I posted and found where I can save to extsd.... Oooppss..But im learning..lol

SBERG117 said:
I ran a backup as soon as I installed..Everything went smooth...I checked to see if the file was saved to either phone or extsd, was saved to phone at 2.4GB..
I moved the file to my extsd just for storage...Now if I want to do a restore im sure I have to move the file back to phone...or do I?
Secondly is there a way or will there be a way to save to extsd?
Thnx....
Click to expand...
Click to collapse
There is, when you go to backup there is a little bar that says internal storage. Click that and you can choose your ext sdcard, internal or one other thing. I forgot what...
Sent from my HTC One X using xda premium

So there's a build of cyanogenmod up on goomanager if any of you feel flash happy and risky
Sent from my SGH-M919 using xda app-developers app

Develop Bugs

welcome