Related
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.2-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
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
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.
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
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?
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
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
Dees_Troy said:
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
Click to expand...
Click to collapse
Every time I download, file size is like 5 kb. I tried flashing without noticing that but didn't work. Flashed back other recovery in meantime. Think the newest version needs to be reuploaded.
Sent from my Find7 using XDA Free mobile app
I download it from my find 7 without any issue.
P/S: the recovery is not working, install and when reboot to recovery, it turns to black screen and nothing goes to the recovery,
Sent from my X9076 using xda premium
I can confirm that too. The recovery seems to be working, because the touchscreen aswell as the software-buttons are responsive, but there is only a black screen every time i boot into it.
yeah this did not work for me either. Also, after reflashing the recovery that I was using before (find 7a 6-12-14) the same thing happens. I have no access to my recovery now.
v2.7.1.1. is not working with me either, just a black screen and flashing on and off, gonna try reverting to gummy twrp
---------- Post added at 10:28 PM ---------- Previous post was at 10:22 PM ----------
opie546 said:
yeah this did not work for me either. Also, after reflashing the recovery that I was using before (find 7a 6-12-14) the same thing happens. I have no access to my recovery now.
Click to expand...
Click to collapse
why were u using a 7a recovery? also you can use fastboot to restore your old recovery i just did and it works fine
Black screen on my X9077 too.
bobbydigital222 said:
v2.7.1.1. is not working with me either, just a black screen and flashing on and off, gonna try reverting to gummy twrp
---------- Post added at 10:28 PM ---------- Previous post was at 10:22 PM ----------
why were u using a 7a recovery? also you can use fastboot to restore your old recovery i just did and it works fine
Click to expand...
Click to collapse
bobbydigital222 said:
why were u using a 7a recovery? also you can use fastboot to restore your old recovery i just did and it works fine
Click to expand...
Click to collapse
Sorry I probably misspoke. I was using the first port from the F7a for the F7. It was 1080p and everything. Never bothered updating it until now. Yeah, I know about fastboot and took care of it. Thanks!
I can't wait until the offical twrp is updated/fixed. the team gummy version is so annoying.
opie546 said:
Sorry I probably misspoke. I was using the first port from the F7a for the F7. It was 1080p and everything. Never bothered updating it until now. Yeah, I know about fastboot and took care of it. Thanks!
I can't wait until the offical twrp is updated/fixed. the team gummy version is so annoying.
Click to expand...
Click to collapse
Ya same here, I don't like the theme, and I'm hoping for ntfs support
Is there anyway to add ntfs support?
Link
Thanks
Link not found for TWRP 2.8.0.1
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.
CHANGELOG for 2.8.0.1:
-Fix a bug that causes weird graphics glitches and touch issues
CHANGELOG for 2.8.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
Click to expand...
Click to collapse
Hi,
As you know in find 7 QHD device, TWRP 2.8.0.0 is showing only Full HD, and it is not detecting the QHD Resolution properly.
So, I am looking for the next update TWRP 2.8.0.1
But the download of TWRP 2.8.0.1 is not available yet
Please have a look...
http://techerrata.com/browse/twrp2/find7
Thank you
Mnt-XDA said:
Hi,
As you know in find 7 QHD device, TWRP 2.8.0.0 is showing only Full HD, and it is not detecting the QHD Resolution properly.
So, I am looking for the next update TWRP 2.8.0.1
But the download of TWRP 2.8.0.1 is not available yet
Please have a look...
http://techerrata.com/browse/twrp2/find7
Thank you
Click to expand...
Click to collapse
2.8.0.0 is usable, but this was a side effect of the LVM rework being done in the device tree. I began moving the recovery init script out of msm8974-common and into the find7 device-specific tree - but while I deleted it from -common the patch which readds it to the find7 tree isn't merged yet. Fortunately the only function that script serves is to detect QHD and copy the appropriate theme - but the 1080p theme will at least be usable on QHD devices in the meantime. Sorry about that.
I just got back from vacation, I need to talk to Dees_Troy, but likely the build that contains the fix for QHD devices will also contail full LVM support.
Thanks for the update @Dees_Troy .. still having a graphics glitch in 2.8.0.1. It's got this invisible line running down the screen
Find 7(s)
Just wanted to ask, the thread name says 2.8.1.0 but I can not find this up to date build for the Find 7 anywhere, website and TWRP Manager app both show 2.8.0.1 as the newest version.
Am I looking in the wrong place or is the thread title incorrect??
Downgrade to jellybean stable color os then flash in fastboot TWRP 2.8.0.1 do not boot into color os hold pwr vol down boot into TWRP it shoulb be gone flash desired rom if you flas kitkat Color os it'll come back I think is something in the newer bootloader thats brakin it.
Sent from my Find7 using XDA Premium HD app
carlosjcar said:
Downgrade to jellybean stable color os then flash in fastboot TWRP 2.8.0.1 do not boot into color os hold pwr vol down boot into TWRP it shoulb be gone flash desired rom if you flas kitkat Color os it'll come back I think is something in the newer bootloader thats brakin it.
Sent from my Find7 using XDA Premium HD app
Click to expand...
Click to collapse
also i have wave glitch effect with twrp 2.8.0.1 on find 7 QHD and color OS 2.0! If i return to colos 1.2.x and after i reflash colos 2.0 (nandroid backup or new flash with factory reset) i resolve this problem or i reupdate the bootloader and the glitch reappears?
fosseperme said:
also i have wave glitch effect with twrp 2.8.0.1 on find 7 QHD and color OS 2.0! If i return to colos 1.2.x and after i reflash colos 2.0 (nandroid backup or new flash with factory reset) i resolve this problem or i reupdate the bootloader and the glitch reappears?
Click to expand...
Click to collapse
same issue here with colorOS 2.0.0i and I do not want to downgrade to get rid of this issue but yeah like a line that move downwards when in TWRP
Natherul said:
same issue here with colorOS 2.0.0i and I do not want to downgrade to get rid of this issue but yeah like a line that move downwards when in TWRP
Click to expand...
Click to collapse
same thing persists after flashing stock recovery from oppo forums.... Anyone know if its something wrong with the files I have or what else it could be?
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.1.1-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 (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
[/LIST]
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 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
TWRP, Tool/Utility for the OEM Cross Device Development
Contributors
arvinquilao
Version Information
Status: Stable
Current Stable Version: 3.1.1-0
Stable Release Date: 2017-05-18
Created 2016-04-13
Last Updated 2017-05-23
Reserved
arvinquilao said:
TWRP 3.0.1-0 is here!
Download from Google Drive
Just flash the zip file using your current custom recovery. Or extract the img file and flash via fastboot (TWRP can also flash img files).
For changelog, visit the TWRP Github repo.
Device tree.
Click to expand...
Click to collapse
Only Qualcomm variants I presume??
Does it support Android N squashfs?
MSF Jarvis said:
Only Qualcomm variants I presume??
Click to expand...
Click to collapse
Good catch.
Yes, for Qualcomm only. Post updated.
vel_tins said:
Does it support Android N squashfs?
Click to expand...
Click to collapse
I don't think it supports squashfs. I haven't touched anything in the recovery folder yet and I didn't see any squashfs related commits in the twrp repo.
arvinquilao said:
I don't think it supports squashfs. I haven't touched anything in the recovery folder yet and I didn't see any squashfs related commits in the twrp repo.
Click to expand...
Click to collapse
TWRP already supports squashfs I believe since I can make backups
At least 3.0.0 couldn't mount /system on Android N Developer Preview.
Marshmallow doesn't use squashfs, but ext4 which is no problem.
Question: How do you update your TWRP recovery? Can it be update by just using your phone?
Sent from my SM-T705 using XDA-Developers mobile app
axl226 said:
Question: How do you update your TWRP recovery? Can it be update by just using your phone?
Sent from my SM-T705 using XDA-Developers mobile app
Click to expand...
Click to collapse
Copy the recovery to sdcard, then boot into TWRP and select install > images and point to that img file
MSF Jarvis said:
Copy the recovery to sdcard, then boot into TWRP and select install > images and point to that img file
Click to expand...
Click to collapse
how about on the part of "Select Partition to Flash Image", do I just flash directly or select "Boot" then flash?
axl226 said:
how about on the part of "Select Partition to Flash Image", do I just flash directly or select "Boot" then flash?
Click to expand...
Click to collapse
Select recovery and then flash. Boot is your kernel, if you flash onto that, you will always get to the recovery, though they would be different versions.
There's no recovery at the list of choices, only boot.
Ok, did a quick test and it doesn't support squashfs.
So it can't be used with N Developer Preview.
If I have a little bit time next week, I will check if it's possible to add (like for TWRP for Android Wear).
Otherwise, we have to wait for official support.
axl226 said:
There's no recovery at the list of choices, only boot.
Click to expand...
Click to collapse
Which TWRP' version do you have? Can you post a screenshot?
vel_tins said:
Ok, did a quick test and it doesn't support squashfs.
So it can't be used with N Developer Preview.
If I have a little bit time next week, I will check if it's possible to add (like for TWRP for Android Wear).
Otherwise, we have to wait for official support.
Click to expand...
Click to collapse
Thanks for testing. By the way I re-uploaded a new zip file, download link is updated. I forgot to put the timezone related build flag in the initial build. Timestamp should be fixed now.
Thread updated. Version bumped to 3.0.2-0. See https://plus.google.com/+DeesTroy/posts/jk9dwNrhnQ8
Still no squashfs support in case you're wondering.
arvinquilao said:
Still no squashfs support in case you're wondering.
Click to expand...
Click to collapse
hoping this is updated to work with android N file system sooner than later. i found preview #2 of android N in april to be good enough as daily driver with my cm android one g1. will stick with it until final consumer release. :good:
Does this recovery support General Mobile 5 Plus? Should I flash it for rooting purposes?
I will try to boot it temporarily
c:\fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.723s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 0.815s
no luck