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.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CHANGELOG for 3.2.1-0:
[*]Allow restoring adb backups in the TWRP GUI (bigbiff)
[*]Fix gzip backup error in adb backups (bigbiff)
[*]Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
[*]Better support for installing Android 8.0 based zips due to legacy props (nkk71)
[*]Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
[*]Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
[*]Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
[*]v2 fstab support (Dees_Troy)
[*]Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
[*]Various other minor bugfixes 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:
twrp_3.2.1-0_mojo.img
Install via fastboot as usual:
Poweroff MOJO
Plug USB Male-Male into USB 2.0 port (closest to hdmi)
Poweron MOJO
Type fastboot flash recovery twrp_3.2.1-0_mojo.img
You can also boot it via fastboot boot twrp_3.2.1-0_mojo.img
Additional notes:
Code:
[B][U]Opengapps install "fix":[/U][/B] go to Mount and check "system" (do not check "mount system read-only") and then you can install them as usual.
If you are anoyed by long time wipe, go to Advanced and check "always use rm -rf".
adb and mtp enabled, for adb sideload you must disable mtp first in Mount->disable MTP.
Crypto enabled (for addoptable storage).
PS: Big thanks to carp_be for finding good kernel sources.
Amazing work! Thanks so much for your hard work and awesome updated software!
elijah.salim said:
This is what happens every time. Its frozen, mouse and all, light around the bar is frozen. Left it sitting there for 30 mins. What's causing this? Haven't been able to install gapps once. This is a brand new device just rooted and this is the first install. Is there any way around this?
Click to expand...
Click to collapse
I can confirm this issue. I have just completely wiped my MOJO via Advanced Wipe using this version of TWRP. I noticed the mouse was a bit laggy in general use and the wipe took longer than usual, but it completed the install of Lineage OS 13. However, upon attempting to install open_gapps-arm-6.0-nano-20171228.zip it completely froze as per the poster above. I hope this is useful info for you.
K-Project said:
I can confirm this issue. I have just completely wiped my MOJO via Advanced Wipe using this version of TWRP. I noticed the mouse was a bit laggy in general use and the wipe took longer than usual, but it completed the install of Lineage OS 13. However, upon attempting to install open_gapps-arm-6.0-nano-20171228.zip it completely froze as per the poster above. I hope this is useful info for you.
Click to expand...
Click to collapse
I will take a look, thanks for reporting.
Updated Opengapps install instructions in first post.
nono2lozere said:
Updated Opengapps install instructions in first post.
Click to expand...
Click to collapse
Thank you. This solution works and I have successfully installed Lineage 13, AddonSu and Gapps.
Fantastic!
Rm -rf is under settings>general tab "use rm -rf instead of formatting", correct? And then wipe as usual?
elijah.salim said:
Rm -rf is under settings>general tab "use rm -rf instead of formatting", correct? And then wipe as usual?
Click to expand...
Click to collapse
Correct.
Is it simple to turn this img file into a zip file so it can be flashed in recovery?
Flashing Magisk using this TWRP leads to a freeze of the whole System.
Using 2.8.7 it works fine.
Maybe you could look at this.
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.
Note, theme is slightly undersized for now.
Device page on our website with instructions for a manual install.
Download folders with all current and prior versions:
Mirror 1
Mirror 2
Are there any screenshots of how it looks like on a watch?
Archon810 said:
Are there any screenshots of how it looks like on a watch?
Click to expand...
Click to collapse
Here you go
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this works awesome, now bring on the custom rom's, lol.
spiderflash said:
Here you go
Click to expand...
Click to collapse
Cheers. Looks like it needs to have the UI adjusted, but if it works, it works.
Archon810 said:
Cheers. Looks like it needs to have the UI adjusted, but if it works, it works.
Click to expand...
Click to collapse
Well yes, as Dees_Troy said:
Dees_Troy said:
Note, theme is slightly undersized for now.
Click to expand...
Click to collapse
It has a resolution of 240x240 instead of 280x280.
Awesome work!! I didn't think TWRP would resize properly for the G Watch! I might as well pause work on CWM Touch then
Awesome Nice work. I am so Pumped right now to check this out.
Question??? Did backup then pulled file. Reset watch disconnected quickly then pushed backup back to watch. Worked but would not connect back to phone. Had to restore. Any thoughts???
Sent from my Nexus 5 using XDA Premium 4 mobile app
Watch your heat and battery while in TWRP. We had to reduce max speed and limit to 2 cores on the Gear Live to keep things in check. We may need to do the same on the G Watch. Let me know.
Would be awesome if we could install this via our phone through the twrp manager app
Sent from my HTC One_M8 using XDA Premium 4 mobile app
What kind of wrist band is that? Can you post a pic of the whole watch? Just got my G-watch and really want a new band:laugh:
RunNgun42 said:
What kind of wrist band is that? Can you post a pic of the whole watch? Just got my G-watch and really want a new band:laugh:
Click to expand...
Click to collapse
This one. Also go here for a full picture.
Smith7018 said:
Awesome work!! I didn't think TWRP would resize properly for the G Watch! I might as well pause work on CWM Touch then
Click to expand...
Click to collapse
Nooooooooo, I hope CWM lands for Dory, i don't know why but for how clever TWRP is i hate the thing its so friggin' ugly ( and yes I have to time to faff about skinning the recovery ) i just can't deal with TWRP
hutzdani said:
Nooooooooo, I hope CWM lands for Dory, i don't know why but for how clever TWRP is i hate the thing its so friggin' ugly ( and yes I have to time to faff about skinning the recovery ) i just can't deal with TWRP
Click to expand...
Click to collapse
cool story bro
No idea this its going to work when the Moto 360 releases with round screen.
hutzdani said:
Nooooooooo, I hope CWM lands for Dory, i don't know why but for how clever TWRP is i hate the thing its so friggin' ugly ( and yes I have to time to faff about skinning the recovery ) i just can't deal with TWRP
Click to expand...
Click to collapse
Unlike CWM, TWRP is fully them-able.
So since there is storage on the watch itself but I dont think its available to use just yet (or is it?), where do the backups save to? I would assume on the parent phone?
Tower1972 said:
So since there is storage on the watch itself but I dont think its available to use just yet (or is it?), where do the backups save to? I would assume on the parent phone?
Click to expand...
Click to collapse
Sure the storage is available. You can store your backups there if you want, but I always save my backups externally on my pc.
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.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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!
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.
Downloads for vee7:
twrp-3.0.2-0-vee7.img
Sources:
Device Tree: https://github.com/HostZero/android_device_lge_vee7/tree/cm-13.0
Kernel Source: https://github.com/HostZero/lge-kernel-lproj/tree/cm-13.0
TWRP Source: https://github.com/lj50036/platform_manifest_twrp_cm
I am Interested to make This TWRP if its working fine without any problem. please reply in comment section.
XDA:DevDB Information
[TWRP][vee7] TWRP 3 for LG L7 II, Tool/Utility for the LG Optimus L3 II, L5 II, L7 II, L9 II
Contributors
HostZero
Source Code: https://github.com/HostZero/android_device_lge_vee7/tree/cm-13.0
Version Information
Status: Testing
Created 2016-07-02
Last Updated 2016-07-02
Huh? Isn't it a repeat of this thread? http://forum.xda-developers.com/opt...ent/recovery-twrp-3-0-0-0-vee7-l7-ii-t3313792
nick37332001 said:
Huh? Isn't it a repeat of this thread? http://forum.xda-developers.com/opt...ent/recovery-twrp-3-0-0-0-vee7-l7-ii-t3313792
Click to expand...
Click to collapse
Not a repeat. Somewhat reason I like this Device. I want to make TWRP official for this device. Where as this is based on cm-13.0 tree. I hope you will test.
HostZero said:
Not a repeat. Somewhat reason I like this Device. I want to make TWRP official for this device. Where as this is based on cm-13.0 tree. I hope you will test.
Click to expand...
Click to collapse
Alright then. Because the other twrp is also cm-13.0 based therefore I was confused.
nick37332001 said:
Alright then. Because the other twrp is also cm-13.0 based therefore I was confused.
Click to expand...
Click to collapse
Nothing much to be confused ri8? better. you or your friend has a device and can do a full test i would be satisfied.
- HostZero
HostZero said:
Nothing much to be confused ri8? better. you or your friend has a device and can do a full test i would be satisfied.
- HostZero
Click to expand...
Click to collapse
I was confused because why would one make the same thing. By the way it does not boot into recovery
<MOD EDIT - DON'T QUOTE FULL OP. THANK YOU.>
Please build Slimrom (marshmallow based) for our device.
Or a custom kernel for JB 4.1.2 P710 or p715
XDA-00 said:
<MOD EDIT - DON'T QUOTE FULL OP. THANK YOU.>
Please build Slimrom (marshmallow based) for our device.
Or a custom kernel for JB 4.1.2 P710 or p715
Click to expand...
Click to collapse
Wrong Place for the request. Post in Device Q&A forum.
how do i flash the recovery
Please compile twrp 3.1.1-0 for vee7
Unofficial release -TWRP recovery for the Galaxy On8 - SM-J710FN, Exynos 7580
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 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 (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
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
INSTRUCTIONS FOR ADB BACKUP:
https://www.droidorigin.com/take-adb-backup-using-twrp-v3-1-0-0/
Update 1/5/2017
TWRP 3.1.0-1 MM build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
ADB backup
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory images from the official firmware can now be flashed with TWRP instead of ODIN. I have extended this feature to include BOOT, RECOVERY, SYSTEM, CACHE, HIDDEN and RADIO(MODEM) partitions.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
NOTE: To flash the modem, first it needs to be renamed to modem.bin.img
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
TWRP: twrp_3.1.0-1_sm-j710fn_29417
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, TeamWin, special thanks to my tester hhaawwkk
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
You did good job. If I helped you. hit a thank.
thank you
hhaawwkk said:
You did good job. If I helped you. hit a thank.
thank you
Click to expand...
Click to collapse
Added to credits.
It wud be great help if we could get a custom rom.
Sent from my Redmi Pro using Tapatalk
apna.suresh0305 said:
It wud be great help if we could get a custom rom.
Sent from my Redmi Pro using Tapatalk
Click to expand...
Click to collapse
try a j7 2015 rom and see if it boots
Oves786 said:
try a j7 2015 rom and see if it boots
Click to expand...
Click to collapse
Did anyone tried that..? I can't try without confirmation.
Sent from my Redmi Pro using Tapatalk
great mate.my props here
exynos 7580??typo mate ?
side said:
great mate.my props here
exynos 7580??typo mate ?
Click to expand...
Click to collapse
Typo? No why?
ashyx said:
Typo? No why?
Click to expand...
Click to collapse
isnt j710fn based on 7870 ? is it my fault ?
That's not for j710fn bro.. Maybe you mean j700f? J710fn is SG J7 2016
side said:
isnt j710fn based on 7870 ? is it my fault ?
Click to expand...
Click to collapse
No different device that is the J7. This is ON8.
Oves786 said:
try a j7 2015 rom and see if it boots
Click to expand...
Click to collapse
J700h is common with on8(exynos 7580) but it can't work without some changes. Main problem is meta inf folder (Update script).
We may take j700h custom rom for modify on8,s stock rom and port it into custom rom
hhaawwkk said:
J700h is common with on8(exynos 7580) but it can't work without some changes. Main problem is meta inf folder (Update script).
We may take j700h custom rom for modify on8,s stock rom and port it into custom rom
Click to expand...
Click to collapse
Try 1st if not installs then ill make meta folder for u
But 1st try and install
Guys can we keep it on topic and post rom talk below:
https://forum.xda-developers.com/galaxy-j7/help/samsung-galaxy-8-t3499001
@ashyx It will be great if you can also provide link to stock recovery, or any roll back steps to move to stock recovery.
Thanks in advance.
Link to Stock Recovery
Will the device status be official after rooting? I am worried about the updates.
bnayagrawal said:
Will the device status be official after rooting? I am worried about the updates.
Click to expand...
Click to collapse
Well not being funny but the clue is in the question.
TWRP = not official software.
Rooting = Unofficial modification
Knox = Tripped
Device status =?
ashyx said:
Well not being funny but the clue is in the question.
TWRP = not official software.
Rooting = Unofficial modification
Knox = Tripped
Device status =?
Click to expand...
Click to collapse
Well, that says it all. The only reason i wanted to root is substratum. But got to know that it wont work. And after getting nougat, root will not be required for substratum to work.
Do I need to unlock bootloader before flashing twrp or does odin do it itself? If I need to unlock it, how do I do it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 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 (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
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
this will VOID YOUR WARRANTY am not responsible for any damage!
Links
beta 5
https://drive.google.com/file/d/1xRiveHDEM5EcwU8tvU5mpHZDeKbPXIVO/view?usp=sharing
BUGS
otg not working
Current status: BETA
HIT THANK BUTTON IF I HELPED
changelog
Beta-1
* Initial release
Beta-2
*Roms installation failed fixed have some problems but still installing n roms
*some bug fixes
Beta3
*system image backup and flash supoort
*bug fixes
*roms installation fixed
*some new features
Beta 4
*recovery backup and flash issue fixed
*some bugs fixes
beta 5
* MTP fixed
* based on latest vegito kernel
* minor bug fixes
Bugs
*otg
Good job, can we get some screenshots?
FardeenTGO said:
Good job, can we get some screenshots?
Click to expand...
Click to collapse
Yes will upload for now am busy
Sent from my SM-G532F using Tapatalk
Screenshots added
new twrp version coming with system image flash and many new features
new twrp version added
HIT THANK BUTTON IF I HELPED
Does the partition sdcard option work?
FardeenTGO said:
Does the partition sdcard option work?
Click to expand...
Click to collapse
Sorry not tested wait while test for now am busy
Sent from my SM-G532F using Tapatalk
odin flash file added
note: this is not a update just a odin flash file
Waiting
For stable version
Radwan Selo said:
For stable version
Click to expand...
Click to collapse
ok any bug you founded
test recovery
usb otg fixed (if you mounted usb and disconnected to use usb again reboot to recovery again)
screenshots not working
some bug fixes
note : this is test recovery mean not stable not beta only for testing
What do u recommend for flashing los14.1 and root addons and gapps aroma "testing or beta" version?
Or back to 3.0.2-0 ?
Is ur recovery 3.1.0-0 or 3.1.1-0?
BTW thank you.?
Radwan Selo said:
What do u recommend for flashing los14.1 and root addons and gapps aroma "testing or beta" version?
Or back to 3.0.2-0
Is ur recovery 3.1.0-0 or 3.1.1-0?
BTW thank you.
Click to expand...
Click to collapse
first its beta version not stable
second typing mistake in file name and in thread name
its twrp 3.1.1-0
and if recovery dont flash roms so why twrp:laugh:
my twrp flashing every rom
only two bugs
mtp(use mount usb instead)
otg
Radwan Selo said:
What do u recommend for flashing los14.1 and root addons and gapps aroma "testing or beta" version?
Or back to 3.0.2-0
Is ur recovery 3.1.0-0 or 3.1.1-0?
BTW thank you.
Click to expand...
Click to collapse
well flash stable lineage 14.1 and pico gapps
Beta 4
Recovery flash and backup issue fixed
Some bugs fixes
Improvements
https://drive.google.com/file/d/0B2BVNSuLC6xFVFZoQjZzdWtRaHc/view?usp=drivesdk
Hit thanks button if I helped
beta 5 twrp
MTP fixed (need confirmation )
based on latest vegito kernel
minor bug fixes
PRESS THANKS IF I HELPED
Closed at OP request
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
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) Install IMG and reboot recovery
4) done
UNOFFICIAL DOWNLOAD FOR Idol 3: HERE
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 Alcatel Onetouch Idol 3
Contributors
Carlos Arriaga, FireLord
Version Information
Status: Stable
Created 2017-12-29
Last Updated 2017-12-28
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Couldn't boot this TWRP - booting with "fastboot -i 0x1bbb boot *filename*" fails with "FAILED (remote: dtb not found)". Flashing it in then trying to use VOL_UP key combo or "adb reboot recovery" from within the OS don't work either, the device simply goes to fastboot.
My device is a 6045B with stock Android 5.0.2. The only TWRP that works is the 2.8.7.0 one from quite a while ago.
EDIT: Didn't expect that I'd need MM bootloader to use this - working alright now.
Hello everyone,
I currently use an unofficial TWRP v3.1.0-0 (https://forum.xda-developers.com/idol-3/development/twrp-3-1-0-0-3-0-2-r5-idol-3-t3572607) which has a bug with the lockscreen function on my Alcatel Touch Idol 3 4.7 (6039Y).
May someone confirm me the TWRP 3.2.1 version in this thread is compatible with the Alcatel Touch Idol 3 4.7 (6039Y) ?
Thank you very much for your help !
Regards
TWRP 3.2.2 is out, if you have time to update it
Thanks a lot for your good work!
Tried to flash this and lost recovery mode
Carlos Arriaga said:
Click to expand...
Click to collapse
My old recovery is 2.8.7.0 version for idol3. I tried to update for this version. In recovery mode, I flashed this one and rebooted to recovery and stuck at Alcatel logo. I can turn off the phone and reboot to system. However, I cannot enter to recovery mode. Is there any way I can go back to my old recovery by flash twrp 2.8.7.0 ?