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) Hit Install and tap the "Images…" button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.

BUGS:
If you have found a bug, please consider posting it to our github issues log. It’s pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that’s struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!

SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

XDA:DevDB Information
TWRP 3.0.x-y for Second Gen Android One MTK devices, Tool/Utility for the OEM Cross Device Development

Contributors
MSF Jarvis, varun.chitre15

Version Information
Status: Stable

Created 2016-04-06
Last Updated 2016-04-06

Sent from my SM-J200H using XDA-Developers mobile app

I just rooted my phone using odin and flashing the file CF Root SM J500FN. I installed twrp above it and it is all okay, I also installed xposed. But once I reboot my phone in TWRP normally then it doesn’t boot anymore. It goes in bootloop on the twrp screen. I fixed the problem flashing the original firmware but I’d like to mod my phone. Is there a way to mod it without getting bootlops? :S

I recently bought the Mate 8 and tried to root it today. I tried many different ways , but the idea was always the same :

1) flash TWRP with fastboot ( i tried different versions , from 2.87 to 3.02 )
2 ) go to TWRP , format data
3) send the firmware via adb to the phone ( I tried different firmwares )
4) flash it with TWRP
5) flash SuperSU

I have thte L29 i guess, so the european version. The error I get is :
E: Unknown command ( erron )

thats it , I can still boot in the system and it works fine, but I dont know if its a good idea to use the phone with that initial error.
any ideas ?

Any one having Twrp 3.0 for my honor bee please provide the same

Thanks in advance

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

Installation
download recovery place (copy) into sd card.
download mobile uncle tool
click on recovery update select recovery.img
done

or use flashify,rashr

Download
Download from here

What’s new in 3.0.1-0:

Downloads:

TWRP V3.0.1-0 KITKAT

TWRPV3.0.1-0 Recovery Flashable KITKAT

Credits:

Dees_Troy (Developer Of TWRP)
EndLess (For Building Recovery And Fixing Invert Touch )
Charansai (For Helping In Porting Of recovery)
Ayush Rathore (For Testing & Porting Recovery)
Pranto (For Material TWRP)
All Testers For Testing

HIT THANKS THIS WILL NOT COST YOU :cowboy:

i missed a backup before rooting my Honor 5x KIW-F21 and deleted the stock rom by reseting the data

Now i only can find Cyanogenmod, which works, but no stock rom, which i can put on via TWRP. I can only finde the APP stock rom file from Huawei. Is there any chance to get back to stock rom without an backup from Cyanogenmod?

Hope you can help!

Best regards!

WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don’t have to worry, as it’s incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.

WARNING #2: The Galaxy S6 edge (6.0+) stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Flash a root such as SuperSU or phh-superuser. You can also flash no-verity-opt-encrypt.zip.

WHAT IS TWRP?

Oh come on, you know what it is – don’t try to fool me!
In case you’re serious, though…

Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.

DOWNLOAD

You can find the device page here:
http://teamw.in/devices/samsunggalaxys6edge.html

There is a download link there, as well as instructions on how to flash it.

I highly recommend using Odin to flash when possible.
You can find a zip containing Odin as well as a link to Samsung’s Mobile drivers page here:
https://idlekernel.com/flash-tools/

FULL STEPS FOR ROOTING YOUR DEVICE

1. In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
   
2. Now go to Settings -> Developer options. (above About device)
   You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
   
3. Extract Odin_3.10.7.zip to your computer.
   
4. Install Samsung Mobile Phone Drivers for Odin to find your device.
   
5. Download a .tar image of TWRP for your device variant.
   
6. Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
   Once you reach the Download mode warning screen, press [Volume Up] to continue.
   
7. Open Odin and place that TWRP tar file in the [AP] slot without touching any other options, then press [Start].
   
8. Hold [Volume Up] + [Home] buttons near the end of the flash, and keep holding them until you are in recovery.
   
9. At this point, you will reach the screen asking you if you want to allow system modifications.
   By swiping right, you will trigger dm-verity, and if you don’t follow step 12 you will be unable to boot!
   If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
   
10. Only if you want your internal storage or data partition to work in TWRP:
    Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
    WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
    
11. Go to [Reboot] -> [Recovery].
    
12. If you only want a bootable system partition or readable data in TWRP:
    Download dm-verity and force encryption disabler.
    Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
    ** If your internal storage is encrypted, you will need to use adb sideload instead.
    
13. Go to [Reboot] -> [System].
    
14. Wait up to 5 minutes for your device to finish setting itself up.

* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.

CHANGES

• v3.0.2-1 – New device tree and kernel, support added for Marshmallow, f2fs, and MTP.
• v3.0.2-0 – See here for the changes.

FEATURES

• MTP support
• USB Mass Storage support
• Micro SDcard and USB OTG storage support
• f2fs file system support (read, write, format, backup & restore)
• exFAT file system support (read, write, format)
• NTFS file system support (read, write)
• ADB root
• Full SELinux support
• Built in android 6.0 tree

KNOWN ISSUES

• Samsung encryption is not supported yet in TWRP 3 (see: https://gerrit.omnirom.org/#/c/17308/)

CONTACT & SUPPORT

You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.

SOURCE CODE

TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree: https://github.com/TeamWin/android_d…amsung_zerolte (android-6.0)
Kernel: https://github.com/jcadduono/nethunter_kernel_noblelte (twrp-6.0)

CONTRIBUTIONS

Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/

XDA:DevDB Information
Team Win Recovery Project – Samsung Galaxy S6 edge, Tool/Utility for the Samsung Galaxy S6 Edge

Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/jcadduono/android…amsung_herolte

Version Information
Status: Stable
Current Stable Version: 3.0.2-1
Stable Release Date: 2016-04-08

Created 2016-04-08
Last Updated 2016-04-08

I try backup, restore, wipe, adb sideload, install, etc and works 100% for me.

Thanks to TeamWin TWRP for the Oneplus2 TWRP .

link:

http://www.mediafire.com/download/jx…3.0.2_x800.img

Then i wanted to flash the TWRP following this thread: http://en.miui.com/thread-245756-1-1.html (In the very last post there is an update for fix the touch problem)
I downloaded Mi Pc Suite, adb driver and fastboot driver (In fact both adb and fastboot recognize my device)
And then i flashed the TWRP as mentioned
But if i disconnect my phone, it wont reboot autmatically, i need to press power button for like 8 seconds
If i press power button for 8s it will reboot normally into android
If i connect the phone and through adb i write adb reboot recovery it will reboot into a black screen with a phone and a cable (that i think mean that the recovery isnt installed first, and second it’s like bootloader mode)

How to guys? I need TWRP to flash the new weekly
Thanks a lot to all

Federico

First of all it is beta test version….
As tested by a it has only battery percentage bug.
Test it and report if u find any new bug.

Attachment 3712176 Attachment 3712177 Attachment 3712178Attachment 3712179

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.

Download link
Unauthorized mirroring of any download file is strictly forbidden. No direct linking to the file below. Redirect all users to download TWRP from this page only.
I released TWRP 3.0.0-0 on other forums and what happened. They just decompiled my image, made changes to prop file and changed TWRP title to their names so as to claim as if it’s built by them. Please respect the developer (I ain’t one, just a starter) and if you want to build one, build one from the source.

How to flash

Flashify Method:
1.Use this method if you have already rooted your device.
2.Now install flashify through google play .
3.Open it and accept & grant root access.
4.On flashify’s home screen,tap on “Recovery image”.
5.Select Choose a file.
6.Then file explorer.
6.Storage.
7.Select inteternal sd(sdcard0),External SD(sdcard1) where you have downloaded the recovery.img.
8.Select recovery.img.
9.Select YUP!.
10.REBOOT NOW.

Spflashtool method:

1. Both drivers should be installed successfully on PC

2. Open spflashtool folder and paste "recovery.img"(for Coolpad Note 3)/ "recovery.img"(for Coolpad Note 3 rename it to recovery.img after download) and "MT6753_Android_scatter.txt"(for Coolpad Note 3)// "MT6735_Android_scatter.txt"(for Coolpad Note 3 files into spflashtool folder.

3. Now right click on "flash_tool.exe" and run as administrater,after flashtool start,click on "scatter loading" and select "MT6753_Android_scatter.txt"(for coolpad note 3)/".

4. Click on "download"(on left top side with green colour icon in spflash tool).

5. Now switch off phone and connect to Pc via USB cable.Press twice the volume up button. A slider will run on bottom of spflashtool. If everything fine then you will see a pop up with green tick.

6. Disconnect phone from PC. Press Volume up and Power button till recovery comes on the screen

7. Now you have successfully installed touch supported TWRP recovery.

CREDITS:– @Dees_troy (for his twrp & his guide)
Twrp
Amit kumar
Stoypia king
Anis mulla
Dhana mari
& Off course me lol

if someone i forgot pls tell me

This is non-destructive but, as usual, I take no responsibility for you wandering from the path and breaking something. You will need an unlocked bootloader, instructions here, and your warranty will most definitely be invalidated after this. The original instructions were in Turkish, so many thanks to the original poster, and to Google Translate for at least making it understandable.

So I take it we’re all sure what we’re doing with adb, fastboot etc? This is serious stuff so if you don’t think you’re up to it, don’t try it until you are. I’m just posting the method for rooting, the other stuff can be easily found. Plus it helps you understand the system of searching.

So when you’re ready, connect your phone to your pc by USB cable, ensure USB Debugging is enabled, and off we go:

Step 1 – Visit https://dl.twrp.me/h815/ and download twrp-3.0.2-0-h815.img to your sdk/platform-tools folder. Rename it to "twrp.img"

Step 2 – download SU zip from here https://download.chainfire.eu/921/Su…1226141550.zip and rename it to "su.zip". Copy it to either the root of your phone’s internal memory or sd card

Step 3 – switch to your sdk/platform-tools folder, shift and right-click on a white space and select "Open command window here"

Step 4 – type "adb reboot bootloader" [ENTER] then type "fastboot boot twrp.img" [ENTER]

TWRP will now run in memory

Step 5 – As TWRP isn’t actually installed, you’ll need to swipe the switch at the bottom to allow it to modify your phone

Step 6 – Tap Install and select su.zip. Select "Zip signature verification" and "Reboot after installation is complete".

Step 7 – Swipe the switch at the bottom to flash the zip.

And that’s your phone rooted. Allow it to restart (it may take a while longer than normal and may reboot , mine did once). Then install Root Checker from the Play Store and run it to confirm your phone has been rooted.

I found every where but did’t find any stable CUSTOM RECOVERY for my SM-J500F

Now @Nick Verse made a stable Recovery TWRP 3.0.0 for J5 (it works on all modle)

check it out from here http://forum.xda-developers.com/show….php?t=3338869

Sent from my SM-J500F using XDA-Developers mobile app

Before

After

Open OTA .zip on PC, open meta-inf/com/google/adndroid/update-script
Replace everything with my script from "after"

Now you can:
1. Do a factory reset
2. Flash cm-12.1-YOG7DAS2K1
3. Flash cm-bacon-cee4e8702d-to-e36dd78050
4. Dont mind about recovery or smth else

Android version 6.0.1

How to root with twrp ? :rolleyes: