Database Info

[DEV][WIP][RECOVERY][TWRP 2.7] TWRP Touch Recovery for Samsung Galaxy S Duos[ALPHA 1]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
DOWNLOAD:
Latest Release
INSTALLATION
Power off your Galaxy S Duos
Get into Download mode by pressing Volume (-) + Home + Power Keys followed by Volume (+) to Confirm.
Step:1 - Press "PDA" button and choose the filerecovery.tar.md5 !
Step:2 - Press "Start" button under Execution.
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.
Credits-
@coolamit for testing.
XDA:DevDB Information
TWRP - kylexx, Tool/Utility for the Android General
Contributors
v_superuser
Version Information
Status: Stable
Stable Release Date: 2014-04-21
Created 2014-04-21
Last Updated 2014-08-18

Note - There might be some things broken, you need to keep calm.
Also, you need to install with the update package from codename13. (Thanks to @coolamit )

Man this recovery almost screw up my phone. for no reason from a certain point the restored backups doesn't boot anymore, stuck at Samsung logo, tried making other backups, reflash twrp, first cwm then twrp but nothing.
The only one working was AN old backup of a week ago, restored that.
I can't use this if it isn't 100% reliable sorry

holymoz said:
Man this recovery almost screw up my phone. for no reason from a certain point the restored backups doesn't boot anymore, stuck at Samsung logo, tried making other backups, reflash twrp, first cwm then twrp but nothing.
The only one working was AN old backup of a week ago, restored that.
I can't use this if it isn't 100% reliable sorry
Click to expand...
Click to collapse
What else do you expect from an Alpha build? :/

v_superuser said:
What else do you expect from an Alpha build? :/
Click to expand...
Click to collapse
ok, I will wait for a more stable version, I like this recovery specially for the compression of backups that saves a lot of space

Awesomee and good work sir ...
can weget for ldpi devices like galaxy pocket,y etc phones ..?? in zip format

Does anyone know if it also works on ace 2x?
Sent from my GT-S7560M using XDA Premium 4 mobile app

Need help for s duos
do you have still s duos and could you please tell how to fix the animation problem in cm11 4.4.4 for s duos( in your cm11 there is no such problem)

I just installed sucefully, but when boot in recovery mode, just hang up.... therefore, the phone boot normally... well, I also lost the root

Not booting in TWRP. Getting restarted every time I am trying to boot with VolUP+Power+Home. If I hold the keys it keeps rebooting, and if I release it boots to system.
If I execute the command from terminal
Code:
adb reboot recovery
it boots into Samsung stock recovery.
Also showing a yellow symbol (!) while booting.
Should I flash it to stock recovery image?
Or is there any other way out to update the recovery to TWRP?

Solved
Thanks to KlinkOnE and m4jonez.
First I installed (ROOT) Rashr - Flash Tool from Play Store as suggested in the post.
Then downloaded Recovery - TWRP 2.8.0.1 and Recovery - TWRP 3.0.2 as mentioned here .
Placed both of the .zip files in the internal memory.
Now I open Rashr and flashed the recovery selecting the .zip file of TWRP 2.8.0.1 (My phone is rooted, so Rashr was able to flash it). Then rebooted to TWRP. But, failed. Removed the battery and insert it again. Now with Vol + Home + Power key, booted the phone in TWRP. From TWRP installed the TWRP 3.0.2. Rebooted to TWRP. It works fine now.

hcp006sl said:
Thanks to KlinkOnE and m4jonez.
First I installed (ROOT) Rashr - Flash Tool from Play Store as suggested in the post.
Then downloaded Recovery - TWRP 2.8.0.1 and Recovery - TWRP 3.0.2 as mentioned here .
Placed both of the .zip files in the internal memory.
Now I open Rashr and flashed the recovery selecting the .zip file of TWRP 2.8.0.1 (My phone is rooted, so Rashr was able to flash it). Then rebooted to TWRP. But, failed. Removed the battery and insert it again. Now with Vol + Home + Power key, booted the phone in TWRP. From TWRP installed the TWRP 3.0.2. Rebooted to TWRP. It works fine now.
Click to expand...
Click to collapse
pls help i'm new to the whole rom flashing thing. i tried what you wrote but the Rashr dosnt seem to find the TWRP both in my phone and external memory. i tried it on both core prime (SM-G360H) and (GT-I9060). i rooted both with kingroot via pc. thanks in advance for your assistance.

digitzonline said:
pls help i'm new to the whole rom flashing thing. i tried what you wrote but the Rashr dosnt seem to find the TWRP both in my phone and external memory. i tried it on both core prime (SM-G360H) and (GT-I9060). i rooted both with kingroot via pc. thanks in advance for your assistance.
Click to expand...
Click to collapse
I don't think this TWRP is for those two models - Core Prime and Grand Neo. Please download TWRP for your phone.
For GT-I9060 follow the thread [RECOVERY][GT-I9060] TWRP 2.8.0.1 touch recovery [UNOFFICIAL] and you can download the TWRP recovery for I9060 from here -Mod edit link removed ppc
For SM-360H follow the thread [Recovery] Official TWRP SM-G360H.
Please don't use king root for rooting. If you have used, replace it with SuperSU. Super-Sume Pro is the app that replaces KingRoot by SuperSu.

[RECOVERY] TWRP 2.8.5.0 Touch Recovery [2015-03-02]

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.
This Recovery is for Cm-12 build only , its based on Native sd-card it means you have to make 2 sd-ext partition of desired size to flash this recovery . It is compiled with F2FS support it means you can switch your partition file system from ext4 --> f2fs or vice versa. Secondaly its not Awsome layout based will add its support when needed
Phone look:
Tablet look:
CHANGELOG for 2.8.5.0:
-Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-Improve thread handling and move input handling into the main rendering thread to improve stability
-Make MTP work even if unplugged and plugged back in
-Unify scrollable list code and make kinetic scrolling feel more natural
-Fix handling of mapped zip files for OTA updates (CM12 updater)
-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
-Other small fixes and improvements
CHANGELOG for 2.8.4.0:
-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
-Fix some MTP related crashes and bugs
-Eliminate TWRP toggling USB IDs during boot if MTP is enabled
-Fix various adb sideload issues
-Improve threading of actions
-Eliminate separate thread for screen timeout
-Update libblkid to 2.25.0
-Use power button as back button on watch themes for easier navigation
-Add mutex locking to data manager
-Improve custom theme handling on encrypted devices
-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
CHANGELOG for 2.8.3.0:
-MTP will now tell the host PC that storage is removed instead of disabling MTP completely
-MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
-Update and improve fix permissions and make fixing contexts optional
-Update SuperSU in TWRP to 2.40 and update install process
-Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
-Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
-Fix kernel panic during MTP start on some devices
-Support unicode fonts on devices with True Type Font support
-Fix slider value not showing sometimes (vibration settings page)
-Toggle MTP off during adb sideload to set correct USB IDs
-Reduce library requirements for 5.0 L decrypt
-Other minor fixes and improvements
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.
CHANGELOG for 2.8.2.0:
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
CHANGELOG for 2.8.1.0:
-MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
-TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
-Temperature support - thanks to bigbiff
-Various other bugfixes and tweaks
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.
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!
DOWNLOAD:
Download the Latest Version From Here : http://download.htclegacy.tk/?dir=pico/Twrp
1) Make sure you have made 2 sd-ext partitions otherwise it will not detect /system and /data
2) Reboot into Bootloader/fastboot mode
3) Run command
Code:
fastboot flash recovery recovery.img
4) Reboot To Recovery
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
Twrp Recovery, Tool/Utility for the HTC Pico (Explorer)
Contributors
kirmaniarslan
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2015-01-29
Created 2015-01-29
Last Updated 2015-01-29
XDA:DevDB Information
Twrp Recovery, Tool/Utility for the HTC Pico (Explorer)
Contributors
kirmaniarslan
Version Information
Status: Stable
Current Stable Version: 2
Stable Release Date: 2015-03-02
Created 2015-01-29
Last Updated 2015-03-14

Recovery Update :- 3/2/2015
Download :- http://download.htclegacy.tk/?dir=pico/Twrp
Changelog :-
- TWRP 2.8.5.0
- added Nand partition but you will see it as sd-ext ( it is used dalvik-cache in CM12 )
- Added a3some mod thanks @thewisenerd

Latest recovery
@kirmaniarslan Just flashed latest recovery and it's not opening it just goes to twrp logo and fone reboots and fone bootloops what was the problem??
Reverted back to 2.7.0.0 and kitkat.
Feeling sad for not having lollipop on my Pico..

owaisnaim said:
@kirmaniarslan Just flashed latest recovery and it's not opening it just goes to twrp logo and fone reboots and fone bootloops what was the problem??
Reverted back to 2.7.0.0 and kitkat.
Feeling sad for not having lollipop on my Pico..
Click to expand...
Click to collapse
Don't flash the recovery with android terminal use pc for flashing it n if still u get error try fastboot erase recovery before flashing recovery

Please help me...How to install Twrp recovery???
I cannot do this by myself...Though i tried but failed...
Please give me some Easy instructions
Thanks

Recovery not working
Hey @kirmaniarslan i flashed the said recovery but it shows the twrp logo and then reboots. I tried the command fastboot erase recovery but its not working. plz help. I have my 2 partitions in ext4, is it because of this that I cannot goto recovery?

sbanrocks said:
Please help me...How to install Twrp recovery???
I cannot do this by myself...Though i tried but failed...
Please give me some Easy instructions
Thanks
Click to expand...
Click to collapse
follow this guide its simple: http://forum.xda-developers.com/htc-explorer/general/guide-how-to-flash-cyanogenmod-12-t3060293
Hit thanks if i helped u
---------- Post added at 12:42 PM ---------- Previous post was at 12:42 PM ----------
Rjrocks22 said:
Hey @kirmaniarslan i flashed the said recovery but it shows the twrp logo and then reboots. I tried the command fastboot erase recovery but its not working. plz help. I have my 2 partitions in ext4, is it because of this that I cannot goto recovery?
Click to expand...
Click to collapse
use this guide its simple: http://forum.xda-developers.com/htc-explorer/general/guide-how-to-flash-cyanogenmod-12-t3060293
Hit thanks if i helped u
---------- Post added at 12:44 PM ---------- Previous post was at 12:42 PM ----------
Rjrocks22 said:
Hey @kirmaniarslan i flashed the said recovery but it shows the twrp logo and then reboots. I tried the command fastboot erase recovery but its not working. plz help. I have my 2 partitions in ext4, is it because of this that I cannot goto recovery?
Click to expand...
Click to collapse
step by step guide http://forum.xda-developers.com/htc-explorer/general/guide-how-to-flash-cyanogenmod-12-t3060293
Hit thanks if i helped u

Smaller version of recovery
Do you have a smaller version of this recovery or may be you can make one? I need it because, I think small part of my recovery partition is locked for writing (s-on bug or what, I just never succseed in flashing recoveries >4 Mb).
---------- Post added at 08:33 PM ---------- Previous post was at 07:45 PM ----------
Tried to flash it like that:
Code:
[email protected]:/home/user/android# fastboot oem rebootRUU
...
OKAY [ 0.155s]
finished. total time: 0.155s
[email protected]:/home/user/android# fastboot flash zip PJ03DIAG.zip
< waiting for device >
sending 'zip' (5062 KB)...
OKAY [ 0.910s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,54
(bootloader) [RUU]UZ,recovery,99
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,20
(bootloader) [RUU]WP,recovery,40
(bootloader) [RUU]WP,recovery,60
(bootloader) [RUU]WP,recovery,80
FAILED (remote: 51 partition update fail)
finished. total time: 7.500s
And it doesn't boots into bootloader anymore (PUU with fastboot only) :crying: Any way to restore it?
Help!

found the way to boot recovery and system manually ("fastboot oem gencheckpt" boots recovery and "fastboot oem boot" boots system), but this is the only way to boot smth and bootloader menu is still dead
I think, I need a original RUU to fix this, but I cant find it for my cid (HTC__07 - Russian one)

Smaller version of your recovery is still actual, btw

hi , sorry for my english, I would like to install TWRP 2.8.5.0 for htc pico, but I can not find the download because this link isn't working.

Indeed. The link leads to an empty directory. Temporary down?

migges said:
Indeed. The link leads to an empty directory. Temporary down?
Click to expand...
Click to collapse
There you go
http://forum.xda-developers.com/showpost.php?p=61602202&postcount=338

Cannot Download [Fix The Downloading Site]
Cannot Downloading Htc legacy Site...
Please Fix It
I Was use The TWRp Manager But :crying: My Device Not Listed
Device : Htc Pico

Can't download the recovery
kirmaniarslan said:
Recovery Update :- 3/2/2015
Changelog :-
- TWRP 2.8.5.0
- added Nand partition but you will see it as sd-ext ( it is used dalvik-cache in CM12 )
- Added a3some mod thanks @thewisenerd
Click to expand...
Click to collapse
I can't download the recovery from that link. It just shows an Index page with no entries !! Plase Help

I cannot flash it in anyway. It always throws this same error.
{
"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 is my problem too....
MSF Jarvis said:
I cannot flash it in anyway. It always throws this same error.
Click to expand...
Click to collapse
any on can help us?

mhvclash said:
any on can help us?
Click to expand...
Click to collapse
I'm trying something. Will let you know if it works
Sent from my HTC Desire 616 dual sim using Tapatalk

MSF Jarvis said:
I'm trying something. Will let you know if it works
Sent from my HTC Desire 616 dual sim using Tapatalk
Click to expand...
Click to collapse
[emoji31] [emoji31] [emoji31] Didn't work.....
Sent from my HTC Desire 616 dual sim using Tapatalk

Since that the links are broken and I still had a copy of this recovery on my computer, here it is. hope it helps

[NO LONGER MAINTAINED][RECOVERY][E8] TWRP touch recovery

UPDATE: I am no longer maintaining TWRP for devices that I do not possess. I am also no longer posting on XDA.​
Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
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.
Click to expand...
Click to collapse
Images
Installation instructions
TWRP Image Install method:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed.
Download the latest version of TWRP appropriate for your device/firmware
Reboot to TWRP
Hit Install and tap the "Install Image" button in the lower right
Browse to the location of the TWRP image on your device and select it
Select recovery from the partition list and swipe to flash
Alternate Installation Method:
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on their computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
Code:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
Code:
fastboot flash recovery twrp.img
Code:
fastboot reboot
Click to expand...
Click to collapse
Device Changelog
Current version: 3.2.1-0:
Code:
[LIST]Initial official release[/LIST]
Older Device-specific versions:
Code:
[LIST]N/A[/LIST]
Click to expand...
Click to collapse
TWRP Official Changelog
Current version: 3.2.1:
Code:
[LIST]minui fixes (cryptomilk)
[*]Better android-8.0 compatibility in ROM trees (Dees_Troy)
[*]Fix missing library in android-8.0 (nkk71)
[*]Fix inconsistent SDCard naming (DevUt)
[*]Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)[/LIST]
Older versions:
Code:
[SIZE="4"][COLOR="Green"]3.2.0:[/COLOR][/SIZE]
[LIST]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[/LIST]
[SIZE="4"][COLOR="Green"]3.1.1:[/COLOR][/SIZE]
[LIST]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)[/LIST]
[SIZE="4"][COLOR="Green"]3.1.0:[/COLOR][/SIZE]
[LIST]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 [URL="https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9"]here[/URL] (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]
[SIZE="4"][COLOR="Green"]3.0.3:[/COLOR][/SIZE]
[LIST]Partial release to help support the release of the [URL="https://www.xda-developers.com/team-win-releases-their-first-official-twrp-app-in-the-play-store/"]Official TWRP app[/URL][/LIST]
[SIZE="4"][COLOR="Green"]3.0.2:[/COLOR][/SIZE]
[LIST]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.[/LIST]
[SIZE="4"][COLOR="Green"]3.0.1:[/COLOR][/SIZE]
[LIST]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[/LIST]
[SIZE="4"][COLOR="Green"]3.0.0:[/COLOR][/SIZE]
[LIST]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[/LIST]
[U]Additional Notes[/U]
[LIST]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 updated 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![/LIST]
[SIZE="4"][COLOR="Green"]2.8.7.0:[/COLOR][/SIZE]
[LIST]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)[/LIST]
[U]Additional Notes[/U]
[LIST]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 [url]https://jenkins.twrp.me[/url] and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at [url]https://gerrit.twrp.me[/url] to help us keep devices up to date and working.[/LIST]
Click to expand...
Click to collapse
Downloads
Download
Latest Official versions
Sources
Device tree
Kernel source
Click to expand...
Click to collapse
Known Issues
None
Click to expand...
Click to collapse
Bug Reporting
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
{
"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"
}
If your issue is determined to be 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 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!
Click to expand...
Click to collapse
Additional Help/Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
XDA:DevDB Information
TeamWin Recovery Project (TWRP), Tool/Utility for the HTC One E8
Contributors
Captain_Throwback, Dees_Troy, bigbiff, _that
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Current Stable Version: 3.2.1-0
Stable Release Date: 2017-12-09
Created 2015-03-20
Last Updated 2018-08-14

Device-Specific Information
Reserved for FAQ (if needed)

Thumbs up, Cap!

Thanks for the official release.
If you have some spare time, could you consider material design ?
Sent from my HTC One_E8 dual sim using Tapatalk

DutchDanny said:
Thanks for the official release.
If you have some spare time, could you consider material design ?
Sent from my HTC One_E8 dual sim using Tapatalk
Click to expand...
Click to collapse
Use the Materialised theme.
When the stock theme is overhauled (expected with TWRP v3.0), I believe it will include some Material design elements.

@Captain_Throwback
I just flashed twrp 2.8.5.0 it's working great thanks.
I always had one problem which is when I press any button in the reboot menu there is a 5 second delay before it reboots.
All the previous versions had the same problem.
Is this permanent or can you fix it in future releases.
And the playstore twrp app doesn't have E8 on its menu, not even a single variant.
Can you please look into that too.
Thanks in advance.

iamsuperuser said:
@Captain_Throwback
I just flashed twrp 2.8.5.0 it's working great thanks.
I always had one problem which is when I press any button in the reboot menu there is a 5 second delay before it reboots.
All the previous versions had the same problem.
Is this permanent or can you fix it in future releases.
And the playstore twrp app doesn't have E8 on its menu, not even a single variant.
Can you please look into that too.
Thanks in advance.
Click to expand...
Click to collapse
The reboot "delay" is normal.
And there is no official TWRP app on the Play Store.

2.8.6.0 has been uploaded.

Captain_Throwback said:
2.8.6.0 has been uploaded.
Click to expand...
Click to collapse
after updating TWRP to 2.8.6.0, swipe to install function is not working.
anybody else experiencing the same?
EDIT: was using an old theme, after removing the theme, it's working fine now

ghost_razr said:
after updating TWRP to 2.8.6.0, swipe to install function is not working.
anybody else experiencing the same?
Click to expand...
Click to collapse
Update your theme, or remove it.

hi
any chance you can compile twrp for E9 plus?

-=knop=- said:
hi
any chance you can compile twrp for E9 plus?
Click to expand...
Click to collapse
I don't have it, so no.

does this work for m8sw variant? (dual sim - china unicom) ?
UPDATE: I tried it... works great! Thanks

2.8.7.0 is uploaded.
NOTE: If you have already updated to Lollipop, then it's possible the latest version will not work on your device. If you determine that this is the case, let me know - I can upload a beta M8 version that should work on the E8.

Captain_Throwback said:
2.8.7.0 is uploaded.
NOTE: If you have already updated to Lollipop, then it's possible the latest version will not work on your device. If you determine that this is the case, let me know - I can upload a beta M8 version that should work on the E8.
Click to expand...
Click to collapse
TWRP 2.8.7.0 has my sd write-protected
tried it with 2 SD cards is effective immediately back on ... and this write protection can be removed by anything neither format or the like can you please fix

snoopyhaeckers said:
TWRP 2.8.7.0 has my sd write-protected
tried it with 2 SD cards is effective immediately back on ... and this write protection can be removed by anything neither format or the like can you please fix
Click to expand...
Click to collapse
I think you may be confused by the system read-only prompt. Did you read the change log in the OP? Recovery can't write-protect your device. No kernel changes were made for this device, so it can't be anything the recovery did.

did it with two different SD cards once I tasted from the sd a zip as supersu 2:46 install this after read-only , 2.8.6.0 no problem working again wonderful, and the system is stock only Xposed framework and super su installed 'm back aud 2.8 . 6.0 thus, the problem for me is first solved .

snoopyhaeckers said:
did it with two different SD cards once I tasted from the sd a zip as supersu 2:46 install this after read-only , 2.8.6.0 no problem working again wonderful, and the system is stock only Xposed framework and super su installed 'm back aud 2.8 . 6.0 thus, the problem for me is first solved .
Click to expand...
Click to collapse
Just disable the read-only option. I don't really understand your issue (language barrier?). If the previous version works fine for you, feel free to continue using it.

Hi, could u make a recovery with f2fs supported for E8? Thank u very much....

schqiushui said:
Hi, could u make a recovery with f2fs supported for E8? Thank u very much....
Click to expand...
Click to collapse
Are there any ROMs that support it? Otherwise it serves no useful purpose.

[RECOVERY][TWRP-2.8.7.0][ Lenovo Yoga Tablet 2 - 1050 ]

Team Win Recovery Project !​​​​
{
"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"
}
Permanent TWRP Recovery 2.8.7.0
Lenovo Yoga Tablet 2 - 1050
Changelog :
Code:
What’s new in 2.8.7.0:
[LIST]
[*] 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
[*] 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)
[/LIST]
What’s new in 2.8.6.0:
[LIST]
[*] Fix daylight savings time rules for USA and Europe (_that)
[*] Allow mulitple overlays for popup boxes (Dees_Troy)
[*] Add pattern style password entry for decrypt (Tassadar)
[*] Keyboard improvements (_that)
[*] Update AOSP base to 5.1 (Dees_Troy)
[*] Reduce theme count to 5 and rely on scaling (Dees_Troy)
[*] Various scaling improvements (Dees_Troy)
[*] Improved handling of resources in the GUI (_that)
[*] Make scroll bar size proportional to list size (_that)
[*] Allow scoll lists to render without a header (_that)
[*] Make console scroll per pixel with kinetic scrolling (_that)
[*] Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
[*] Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
[/LIST]
What's new in 2.8.1.0 :
[LIST]
[*] MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
[*] TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
[*] Temperature support - thanks to bigbiff
[*] Various other bugfixes and tweaks
[/LIST]
What's new in 2.8.0.0 :
[LIST]
[*] 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
[/LIST]
What's new in 2.7.1.0 :
[LIST]
[*] Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
[*] Various bugfixes to backup and restore
[*] Improvements to USB storage handling
[*] Added a class to search for files to make finding the correct brightness file automatic in most cases
[*] Various other bugfixes and tweaks
[/LIST]
What's new in 2.7.0.0 :
[LIST]
[*] Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
[*] Allow sideloading from /tmp on encrypted devices
[*] Check for a crypto footer before asking for a password to prevent user confusion
[*] Additional checks for validity to auto generated backup names
[*] Text wrap in the console output
[*] Proper caps lock support in the keyboard
[*] Mouse support via USB OTG for devices with a broken digitizer
[*] Improve scanning of storage locations for OpenRecoveryScript
[*] Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions
[*] Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
[*] Update SuperSU to 1.93 and improve installation process
[*] Added selinux contexts restoration to fix permissions
[*] Load RTC offset on Qualcomm devices to fix the date/time in recovery
[*] USB Mass Storage fixes Add SELinux support checking
[*] Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
[*] Add 4.4 AOSP decrypt support
[*] Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
[*] Various SELinux fixes and bug fixes
[/LIST][CENTER][/CENTER]
Downloads :
Code:
[CENTER]
* [URL="https://www.androidfilehost.com/?fid=24421527759888155"]openrecovery-twrp-2.8.7.0.img[/URL] md5 : 175eecd081720a9cb8a247e3ecc211ce
[/CENTER]
Installation :
Code:
[CENTER]
* [FONT="Arial Black"]Your Device Must Have A Unlock Bootloader ![/FONT]
*[FONT="Arial Black"] Image File ( openrecovery-twrp-2.8.7.0.img ) :[/FONT]
[LIST]
[*] boot your device in bootloader mode by :> adb reboot bootloader
[*] flash custom recovery :> fastboot flash recovery openrecovery-twrp-2.8.7.0.img
[*] reboot your device :> fastboot reboot
[/LIST]
[/CENTER]
Boot into TWRP :
Code:
[CENTER]
* > adb reboot recovery
* keep pressing at the same time : power off button and volume up - as soon as your device vibrate , please relase power off button and keep pressing volume up -> your device will enter very soon into TWRP recovery !
[/CENTER]
Source :
Code:
[CENTER]* [URL="https://github.com/TeamWin/Team-Win-Recovery-Project/tree/twrp2.7"]TeamWin GitHub[/URL] !
* YT2-TWRP : [URL="https://github.com/Huawei-Dev/twrp-yt2/tree/5.1"]GitHub[/URL] ;
* Kernel : [URL="https://github.com/Huawei-Dev/android_kernel_lenovo_yt2/tree/5.1.1"]GitHub[/URL] ;
[/CENTER]
Credit :
Code:
[CENTER]* [URL="http://teamw.in/project/twrp2"][B]Team[COLOR="RoyalBlue"]Win[/B][/COLOR][/URL]
* [URL="http://forum.xda-developers.com/showthread.php?t=1943625"]Dees_Troy[/URL]
* [URL="http://forum.xda-developers.com/member.php?u=4878287"]_that[/URL]
[/CENTER]
FAQ :
Code:
[CENTER]
* please perform a Backup with this version of TWRP - after that, you'll be able to restore successfully !
* do not perform a Restore from a Backup performed with other version of TWRP - your device will end with boot loop into TWRP !
[/CENTER]
SHARE :
Code:
[CENTER]
* [B][I]please, if you want to share or your work is basend on my source code - first, you should ask my permission via PM ![/I][/B]
* [B][I]also on your OP, you must provide adequate credit, for my works ![/I][/B]
* [B][I]you are always free to use & improve my works ![/I][/B]
* [B][I]thanks for understanding ![/I][/B]
[/CENTER]
regards,
Surdu Petru

* Unlock bootloader for YT2 - 1050F : Unlock-Bootloader-YT2-1050F.zip
Warning !
* Your device should be already updated to Android L ! Do not try to unlock bootloader on Android Kitkat !
* reboot your device in DNX Mode : On your display you should see : "Fastboot starting ... " ! ( press & keep at the same time all three hardware buttons, as soon as device vibrate please release power button ... you can release volume up/down buttons, as soon as you can see "Fastboot starting ..." : this is DNX Mode !
* extract bootx64.efi, droidboot.img & ESP.img from Unlock-Bootloader-YT2-1050F archive .
* (sudo)* fastboot flash osloader bootx64.efi
* (sudo)* fastboot flash ESP ESP.img
* (sudo)* fastboot flash osloader bootx64.efi
* (sudo)* fastboot boot droidboot.img
* (sudo)* fastboot reboot
Right now you are able to install/flash TWRP 2.8.7.0 !
(sudo) * - only for Ubuntu !
Best regards !

*** reserved ***

surdu_petru said:
* Unlock bootloader for YT2 - 1050F : Unlock-Bootloader-YT2-1050F.zip
Warning !
* Your device should be already updated to Android L ! Do not try to unlock bootloader on Android Kitkat !
* reboot your device in DNX Mode : On your display you should see : "Fastboot starting ... " ! ( press & keep at the same time all three hardware buttons, as soon as device vibrate please release power button ... you can release volume up/down buttons, as soon as you can see "Fastboot starting ..." : this is DNX Mode !
* extract bootx64.efi, droidboot.img & ESP.img from Unlock-Bootloader-YT2-1050F archive .
* (sudo)* fastboot flash osloader bootx64.efi
* (sudo)* fastboot flash ESP ESP.img
* (sudo)* fastboot flash osloader bootx64.efi
* (sudo)* fastboot boot droidboot.img
* (sudo)* fastboot reboot
Right now you are able to install/flash TWRP 2.8.7.0 !
(sudo) * - only for Ubuntu !
Best regards !
Click to expand...
Click to collapse
Can I get your sources for duplicating the unlock. I need it for another device on XDA....

workdowg said:
Can I get your sources for duplicating the unlock. I need it for another device on XDA....
Click to expand...
Click to collapse
Hello !
To unlock bootloader for other device you should ask to Manufacturer's device a method or a code for unlock bootloader ... Method described by me working ONLY on Lenovo Yoga Tablet 2 1050F !
Maybe you didn't know, but Lenovo has already provided for some users a method to unlock bootloader ... so, if you need source , you should ask direct to Lenovo.
Best regards !

tried this.. though i get a blue box come up with Certificate Verification Failure on top of the DNX.. Says Press any key to return.. which of course i cant..
Fastboot hangs on
sending 'osloader' (276 KB)...
OKAY [ 0.019s]
writing 'osloader'...
just sits there forever.

Sage said:
tried this.. though i get a blue box come up with Certificate Verification Failure on top of the DNX.. Says Press any key to return.. which of course i cant..
Fastboot hangs on
sending 'osloader' (276 KB)...
OKAY [ 0.019s]
writing 'osloader'...
just sits there forever.
Click to expand...
Click to collapse
You must be doing something wrong Sage,it worked perfect for me and several others I know of.

Does it work for 1050L
Sent from my YOGA Tablet 2-1050L using Tapatalk

Thank you for your work, I just got an Lenovo Tablet 2 10.1 as a gift.
When I'm trying to unlock the bootloader (1050F) I get this error :
C:\adb>fastboot flash osloader bootx64.efi
sending 'osloader' (276 KB)... OKAY [ 0.089s]
writing 'osloader'... FAILED (remote: flash_cmds error!
strangely I was able to install recovery, even with this error
also I was able to install osloader via fastboot (instead of droidboot [i thought this would be the same thing]), but I can't falsh ESP in this mode ?!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash ESP ESP.img
sending 'ESP' (33792 KB)...
OKAY [ 1.499s]
writing 'ESP'...
FAILED (remote: unknown command)
finished. total time: 1.516s
Click to expand...
Click to collapse
Offtopic:
Now we have a unlocked bootloader, shouldn't it work to install Linux/Windows now, with a different bios ?

Do you have a proper git history for the "android_bootable_recovery-twrp" folder? I would like to see the exact patches you made to TWRP instead of just the listing of all files.

@surdu_petru
how are you pal
im getting the below error when i try to build you twrp tree. have got your kernel source as well. can you help.
The file is there i have cheched.
/home/rob/cm/Tab/kernel/lenovo/yt2/drivers/gpu/drm/i915/intel_pm.c:36:27: fatal error: psb_powermgmt.h: No such file or directory
#include <psb_powermgmt.h>

I can get as far as needing to boot into twrp but can't get it, all i get is a screen with these options.
reboot system now
apply update from sdcard
wipe data/factory reset....
Im on the latest firmware, had it installed in the previous firmware, the had a bit of mess up took me a while to get tablet back working but thankfully did just need to get over this step then im good to go.
Any ideas?

foggs said:
I can get as far as needing to boot into twrp but can't get it, all i get is a screen with these options.
reboot system now
apply update from sdcard
wipe data/factory reset....
Im on the latest firmware, had it installed in the previous firmware, the had a bit of mess up took me a while to get tablet back working but thankfully did just need to get over this step then im good to go.
Any ideas?
Click to expand...
Click to collapse
Are you sure you have unlocked the bootloader?
Sounds like the problem to me

pug1 said:
Are you sure you have unlocked the bootloader?
Sounds like the problem to me
Click to expand...
Click to collapse
All the unlocking bootloader steps went okay same with flashing the recovery just the adb reboot recovery hold power volume up release power button at vibration wouldn't go to twrp.
Sorted now, used the tether method to flash supersu then installed flashify from playstore then flashed the recovery img.

Thank you surdu_petru!
This file worked for Lenovo Yoga Tab 2 830 F - thank you for making this happen!

Is there a way to boot temporarily into TWRP ? I just need to go in and modify some files and would like to use the TWRP explorer, thanks !

Hi,
how can I unlock bootloader of 1380F model? (13" version) Latest firmware is installed.
Tnx,
Enkidu

Booting windows on the android version of the yoga tab 2
Hi, since the bootloader has already been unlocked for this device, is it now possible to install windows onto the android version of the yoga tab 2?

Innocentius said:
Hi, since the bootloader has already been unlocked for this device, is it now possible to install windows onto the android version of the yoga tab 2?
Click to expand...
Click to collapse
No because they have different hardware. It would be nice but I dont think anyone has done this. I looked in to it a couple of years ago

pug1 said:
No because they have different hardware. It would be nice but I dont think anyone has done this. I looked in to it a couple of years ago
Click to expand...
Click to collapse
it has a x86 cpu?

[RECOVERY][KARATE][V3.2.1-025] Red Wolf Recovery Project

{
"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"
}
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Red Wolf Recovery is custom recovery based on TWRP source code, however some things are working here slightly different then you might expected. The main objective of this project is to provide stable recovery with features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. This recovery is also first recovery on the world with password protection.
Based on TWRP version: 3.2.1
For devices: Mido, Kenzo & Kate and now available for Karate
Developers: ATG Droid & dadi11
Features :
Code:
Translated to EN, PL, zh_cn, & CZ
- Password protection
- Flashlight
- MIUI Incremental OTA Support
- Built-in latest Magisk, SuperSU & AromaFM
- Support two screenshot GUI actions - Power+VolDown to save screenshot in to the internal storage &
Power+VolUp to save screenshot in to the external storage (Will be automatically saved in to the internal in case
that external storage doesn't exist).
- Support automatic reboot after the restore process
- Recovery can automatically modify some props in the ROM directly during the installation
- Some built-in scripts from community
- Tap to wake support
- Advanced deactivation of the stock recovery
- Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- Support "set on boot" settings.
* Changes for security reasons *
- ADB isn't starting automatically at the start of the recovery. You have to activate it in recovery
- MTP isn't starting until user enter correct password
- Deactivated support of the custom themes
Some differences to the official version:
Code:
- get out of here if you are pirating apps. this recovery is not for you
- always up-to-date with the latest TWRP changes
- compiled on omnirom-7.1 source
- kernel compiled inline with the recovery
- fixed backup/restore of Firmware
- added F2FS support
- added NTFS support
- added exFAT support
- more languages
- other improvements from Features and Changelog lists
Changelog:
Code:
RedWolf-V3.2_025
- Fixed crash of the recovery while running OTA_RES.. (So MIUI OTA is now working again)
- General bug fixes and improvements
- Fixed bug with MIUI Updater app showing error that installation failed after installation of full ROM
- Deactivation process is now called only when it's really needed
- Updated kernel
RedWolf-V3.2_024
- Fixed GUI color glitch while starting Aroma Installer update-binary
- Optimized pigz runtime process
- Updated recovery base to the AOSP 8.1.0 & TWRP 3.2.1
- Highly improved signature verification for Incremental packages so now we can be really sure if the package is compatible with the ROM.
- Introduced a file based backup/restore engine. Expect it to be improved with the next builds...
- Improved security related to the password protection
- Fixed loading of the AromaFM config file
- System survival process for Incremental packages is now set by default
- Code optimizations
- Removed the dumwolf process
- Added signature check for incremental OTA survival so we won't be unnecessarily creating a new one if it's signed under the same access key
- Magisk updated to the version 15.1
- Added Indonesian language
- Fixed issues with Chinese characters...
- Governor which is changed by the action in the recovery GUI is now automatically set for all cores instead of only four.
RedWolf-V3.2_023
- Updated recovery base to the TWRP version 3.2.0
- Fixed issue with recovery sometimes showing "NO-OS" page even when OS is installed
- Merged: Fstab V2, minui updates, Keymaster 3.0 support, ADB updates, fixes related to the compiling errors...
- Added patch against the pirating applications
RedWolf-V3.1_022
- Small improvements in the installation process
- Recovery will now automatically warn the user in case that user selected to install the zip which contain a bootloader
- You can now wipe installed substratum overlays directly from the "advanced wipe" section
RedWolf-V3.1_021
- Automatically return install error if there is any issue with Incremental OTA Survival
- Added option to also backup system partition for Incremental OTA Survival (It's not always needed, but just in case it's better to backup it.)
- Added support for the compatibility verification of the Incremental Package
- Rebuilded & improved installation process
- Fixed starting process not being disabled correctly in case that we are running ORS
- Translation update
- Added support for devices with 2GB RAM or less... (Check installation process of this build for more info)
- Added checkbox for activation/deactivation of the boot check (Disable only if you really need to).
- Fixed booting problems on some custom ROMs which don't have gzip compressed ramdisk
- Removed bookmark feature
- Added ability to unzip files using the stock filemanager.
- Added search selection for the stock filemanager.
- Fixed 'No OS' on system image restore after wipe
- Merged some latest commits from TWRP gerrit
RedWolf-V3.1_020
- Fixed flashing of the images in the previous 018 build
- Added back support for unpacking of the LZ4 compressed ramdisk
- Fixed bookmark feature
RedWolf-V3.1_019
- Disable TWRP installation directly during the first boot
- Default time zone was set to CEST
- Use military time as default time.
- Support of the custom themes was completely removed from the installation process
- Few fixes & improvements in the strings.
- Default value of the RedWolf specific vibrations was slightly increased
- Improved saving/loading of the AromaFM config file.
- User can now select if recovery should disable stock recovery when system is mounted as read-only.
- Default color of the recovery was set to red.
- Fixed automatic reboot if the installation process was unsuccessful
- Center time in the statusbar as default
- Show CPU temp in statusbar as default
- Added "Red Wolf No-OS search engine". Enable this if you are sometimes getting No-OS installed error even when OS is installed.
- Added back support for extra languages
- Added support for Talian language
- Updated Chinese (simplified) translation of the AromaFM by LiuNian and Pzqqt
- Fixed displaying of the extra languages
- Improved mounting of the partitions during the applying of set on boot values
- Fixes with "stuck at unmounting"
- Highly improved speed of the recovery while setting up a new password, changing accent color or setting a new splash screen
- Magisk updated to the V14.3
- Recovery now won't allow the user to enter special characters while entering the password (Causing issues...)
- Few improvements with the Android Oreo installation
- Updated kernel
- Added ability to select if recovery should automatically disable forced encryption in the ROM
- Recovery will now automatically rename scripts in the system if the "Aggresive stock recovery deactivation" is enabled
- Added ability to select if recovery should automatically enable/disable USB Debugging in the ROM
- Removed some useless files to save the space
- Added support for saving the set on boot values also during the automatic reboot
- Redesigned flashlight icon
- Recovery now won't allow the user to enter the space in to the backup name
- Improved support of the last status checking of the MIUI ROM
- Recovery now won't show any button after the cancelled reboot action untill the sleep action won't be running anymore
- You can now select if recovery should also automaticaly reboot after the successfuly finished restore process
- Recovery will now hide the automatic backup feature if the system partition is mounted as read-only
- Updated recovery base to the AOSP 8.0.0
- Updated image drivers
- Added ability to select if recovery should automatically enable/disable "ro.adb.secure" property in the ROM
- Recovery will now automatically disable starting of the flash_recovery service if the "Aggresive stock recovery deactivation" is enabled (this process is also compatible with the backup of the init.rc by Magisk or SuperSU).
- Added new section called "Special Actions" in to the advanced menu
- Updated & optimized flashlight drivers
- Added ability to select if recovery should automatically enable/disable "ro.secure" property in the ROM
- Added ability to select if recovery should automatically enable/disable "ro.allow.mock.location" property in the ROM
- Highly improved support of the Incremental Package installation, detection etc.
- Updated Chinese (simplified) translation of the recovery by LiuNian and Pzqqt
- Added support for the complete deactivation of the secure boot in the MIUI based ROMs
- ADB is now automatically starting as root
- Added support for the RedWolf update package
- Default theme of the AromaFM was changed to holo black with the sense icons and automount turned on
- SuperSU Updated to the 2.82 SR5
- Updated ramdisk cleaner & added support for more kernels (thanks to @MOVZX's kernel installation scripts...)
- Small fixes with the /WOLF folder in the PartitionManager
- Highly improved speed of the reboot
- 'Deactivation process' is now automatically called during the installation instead of the reboot
- Imroved deactivation of the leds after the installation / backup / restore process.
- Fixed bug with recovery showing on the governor page that the active governor is "Interactive" even when user selected performance/powersave mode.
- Removed some GUI messages while we are installing built-in zips.
- And many other things which i don't remember anymore...
RedWolf-V3.1_018
- Fixed bugs with MIUI OTA Support to make sure that it will work even with newest beta builds of the MIUI
- Updated Polish translation by Daviteusz
- Fixed bugs in the Polish strings & edited the scale of the Russian strings
- Recovery will be now more aggressive if the process of the stock recovery doesn't want to be disconnected (Sometimes happen on some MIUI ROMs).
- Added detection of the installed ROM
RedWolf-V3.1_017
- Magisk updated to the V13.6
- SuperSU updated to the 2.82 SR3
- Added ability to automatically flash SuperSU config before the SuperSU - https://forum.xda-developers.com/apps/supersu/2017-08-13-supersu-config-t3655754
- Deactivated hw keys
- Added some missing back buttons
- Attempted to fix encryption
- Attempted to fix MIUI OTA installation - needs testing
- Removed extra languages (were not displayed properly)
- Small update which fixed deactivation of the dm-verity & forced encryption. Now you really don't have to flash the lazyflasher everytime when you are installing the MIUI ROM.
RedWolf-V3.1_016
- Fixed feature "Backup wifi, bluetooth & hosts" not to work if the user wiped the data partition using the "factory reset".
- TWRP source code was updated to the Aug 15, 2017
- Fixed recovery remembering the wipe list after setting a new gui page.
- Improvements with the mounting of the partitions during the boot
- Fixed led drivers on mido
- Fixed ability to set custom backup folder name & ADB ID
RedWolf-V3.1_015
- Updated with the latest TWRP changes
- Added flashlight switch on mido
RedWolf-V3.1_014
- Fixed recovery not deactivating the dm-verity, forced encryption, & stock recovery if the OS was detected as not installed. This issue was often happening on some MIUI ROMs.
- Improvements with the OTA update system of the MIUI.
- Fixed wrong reboot for some users.
- Added support for automatic deactivation of the dm-verity, forced encryption & stock recovery after finishing the OpenRecoveryScript process.
- Fixed recovery not deactivating the dm-verity & forced encryption during the automatic reboot after the finished installation.
- Better explain the current situation if the OS was detected as not installed.
- osm0sis's scripts "unpackbootimg" & "mkbootimg" can now be easily called from the script or terminal
- Improved the speed of the reboot
- Updated the community script "Fingerprint scanner fix" by Magua. It's now working again!
- Added NTFS & exFAT support
- Added more languages and updated Polish RedWolf translation by @Daviteusz
- Added FGO patch - https://goo.gl/GBkhMN
RedWolf-V3.1_013
- Slightly improved deactivation of the stock recovery during reboot after the zip installation
- Added ability to flash boot logo in the recovery
- Fixed firmware restoring issues
RedWolf-V3.1_012
- added F2FS support for mido
- added Night Mode (kcal) support for mido
RedWolf-V3.1_011
- Updated Polish translation by @Daviteusz
- Added few missing strings from the latest TWRP source
Downloads:
Latest build for Lenovo K6 power (karate)
https://drive.google.com/open?id=1mjWfRdrFH4BU2Z8aaPHDuSMdGvKVetsT
ScreenShots : See in Screeshots section To see more about this recovery flash it
Warning:
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery. But your device can be still reinstalled using fastboot or Miflash.
XDA:DevDB Information
Redwolf Twrp, ROM for the Lenovo K6 / K6 Power / K6 Note
Contributors
Gautham Asir, karthick mostwanted, Gautham Asir, ATG Droid dadi11
Source Code: https://github.com/RedWolfRecovery
ROM OS Version: 8.x Oreo
Based On: TWRP Recovery
Version Information
Status: Stable
Current Stable Version: 3.2.1-025
Stable Release Date: 2018-02-06
Created 2018-02-06
Last Updated 2018-02-06

Will you make it for K6 Note K53a48?
Sent from my Lenovo K53a48 using XDA Forums PRO

Sniperboy1 said:
Will you make it for K6 Note K53a48?
Sent from my Lenovo K53a48 using XDA Forums PRO
Click to expand...
Click to collapse
I dont own that device bro sorry !

Sniperboy1 said:
Will you make it for K6 Note K53a48?
Sent from my Lenovo K53a48 using XDA Forums PRO
Click to expand...
Click to collapse
we already the have latest official version by karthik.
Also this recovery works with k53a58(karatep) except sdcard

Awesome work bro

Need to be able to use the SD card for backup.
Is this possible for K6 Note K53a48?
Other than that I have no problem
Thanks.
Sent from my Lenovo K53a48 using XDA Forums PRO

Made SD card internal storage so that solved the problem.
Outstanding TWRP.
Much better than the other original TWRP.
Thanks again.
Sent from my Lenovo K53a48 using XDA Forums PRO

adilrenzu said:
we already the have latest official version by karthik.
Also this recovery works with k53a58(karatep) except sdcard
Click to expand...
Click to collapse
Lol. The twrp for the k6 note is now updated and the sd card bug is already fixed. Please see on the official website.

Please give the official website link for the update karatep K53a48
Sent from my Lenovo K53a48 using XDA Forums PRO

firemax13 said:
Lol. The twrp for the k6 note is now updated and the sd card bug is already fixed. Please see on the official website.
Click to expand...
Click to collapse
LOL...I think u have problem contemplating english. I meant the sd card bug in this recovery not the one by karthik.
P.S : i was the one who tested the official twrp for k6 note for sd card bug,as Karthik doesn't own a k6 note.
P.S.S : It was fixed in twrp 3.1.x which i tested but Karthik never released that one for public, instead released 3.2.x directly

I know. I tested the k6 power old twrp but the sd card is working. But I stop testing the new 3.2 twrp for k6 power. I think 3.2 twrp karate sd card is not working for k6 note.

With the new update of lineage 15.1 by Karthick I had to use the official TWRP since wiping Vendor partition is required.
Hopefully RedWolf will be updated to the official specifications of the latest version of TWRP soon.
Sent from my Lenovo K53a48 using XDA Forums PRO

Well my question might be out of the league.
I flashed my K6 Power (karate) with RR, AOSP, Lineage. After finishing boot up, a screen appears encryption unsuccessful. I tried formatting through twrp but same error occurs again. Should I flash this file? Any help would be appreciated.

sanjoykumardas26 said:
Well my question might be out of the league.
I flashed my K6 Power (karate) with RR, AOSP, Lineage. After finishing boot up, a screen appears encryption unsuccessful. I tried formatting through twrp but same error occurs again. Should I flash this file? Any help would be appreciated.
Click to expand...
Click to collapse
Because you are using old twrp.

sanjoykumardas26 said:
Well my question might be out of the league.
I flashed my K6 Power (karate) with RR, AOSP, Lineage. After finishing boot up, a screen appears encryption unsuccessful. I tried formatting through twrp but same error occurs again. Should I flash this file? Any help would be appreciated.
Click to expand...
Click to collapse
You have to format the internal storage of the device to fix "encryption" related issues. Copy the important stuff to PC before formatting.

firemax13 said:
Because you are using old twrp.
Click to expand...
Click to collapse
No I am using updated one.

sanjoykumardas26 said:
No I am using updated one.
Click to expand...
Click to collapse
Then we need to format the data. If you don't format then error will come.

Done that too. Through twrp. But same error

Any chance you can update this to V3. 2.1??
It is so much easier to use than official TWRP.
Sent from my Lenovo K53a48 using XDA Forums PRO

Amazing recovery application.
Anyway to get external SD card to be enabled for backup?
Sent from my Lenovo K53a48 using XDA Forums PRO