[OFFICIAL] TWRP 3.1.0-0 Recovery for Redmi 3 - Xiaomi Redmi 3 ROMs, Kernels, Recoveries, & Other

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CHANGELOG for 3.1.0-0:
-Vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-Adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
-Tweak MTP startup routines (mdmower)
-Support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-Support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-Better indicate to users that internal storage is not backed up (Dees_Troy)
-Improve automatic determination of TW_THEME (mdmower)
-Minimal getcap and setcap support (_that)
-Try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-Shut off backlight with power key (mdmower)
-Timeout during FDE decrypt (Dees_Troy and nkk71)
-Support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-Boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-Support for AB OTA zips (Dees_Troy)
-Support new Android 7.x log command (Dees_Troy)
-Update recovery sources to AOSP 7.1 (Dees_Troy)
-Numerous bugfixes and improvements by too many people to mention
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.
Xiaomi Redmi 3
TWRP Downloads
Contributors
Anik_khan

---

Reserved
How to use F2FS
Download TWRP from the link above
Grab a rom that supports F2FS
Back up any important data as this will wipe your entire internal storage
Boot into the bootloader and flash the recovery
Boot into TWRP and go into Wipe > Advanced Wipe
Select Data and then hit "Change or Repair File System"
Hit Change File System
Choose F2FS and slide to confirm
Repeat the previous three steps for cache partition
Reboot and move all of your files back over (if restoring through TWRP, make sure to check the option to use rm -rf instead of formatting)
If you have any issues with this, feel free to ask me.

---

NOTE:
Xiaomi added dm-verity check on Bootloader. You will be need to disable it for modifying system. You can do it simply via adb.
Connect phone with adb (you need to execute this command with root)
Code:
adb root
Code:
adb disable-verity
That's it
Enjoy

---

Nice, great work Anik!
Birthday gift for yourself

---

Its only for unlock bootloader ?thanls
Inviato dal mio Redmi Note 3 utilizzando Tapatalk

---

cranio84 said:
Its only for unlock bootloader ?thanls
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
Click to expand...
Click to collapse
It says on the first post in red letters that bootlocker needs to be unlocked.
Poslano sa mog Redmi 3 koristeći Tapatalk

---

Thank you! I will flash this once I have unlocked my BL.

---

@Anik_khan can i execute flash the root only via adb? Or any method how to root dev rom locked bootloader?

---

After flashing (which went pretty smooth)....the recovery page only shows a mobile screen with usb plugged in, no stock or twrp!!! am I doing something wrong here?

---

raad.sobhan said:
After flashing (which went pretty smooth)....the recovery page only shows a mobile screen with usb plugged in, no stock or twrp!!! am I doing something wrong here?
Click to expand...
Click to collapse
Is your bootloader unlock before flashing twrp recovery?

---

v0ne said:
Is your bootloader unlock before flashing twrp recovery?
Click to expand...
Click to collapse
ya, this was the first thing I did after unlocking.

---

raad.sobhan said:
ya, this was the first thing I did after unlocking.
Click to expand...
Click to collapse
I too have that problem. Could it be that I went back to the latest rom available (V7.2.4.0.LHP) ?
I unlocked the bootloader from dev rom.
Switched back to V7.2.4.0.LHP, but checked for bootloader : still unlocked.
Then i proceeded to fastboot flash the recovery, everything went fine with the regular fastboot message confirming transfert and write, but when I reboot into recovery mode, it shows the Xiaomi recovery picture like @raad.sobhan described.
I'll try in few minutes with dev rom to see if it changes anything.

---

Ok so, I tried with dev rom miui_HM3_6.3.17 and same result.
Here's a pic of the recovery once the following commands were issued:
Code:
X:\XX\XX>fastboot flash recovery TWRP_3.0.0-0-ido.img
target reported max download size of 268435456 bytes
sending 'recovery' (13496 KB)...
OKAY [ 0.438s]
writing 'recovery'...
OKAY [ 0.500s]
finished. total time: 0.938s
X:\XX\XX>fastboot reboot
rebooting...
finished. total time: 0.000s
@Anik_khan, if there's any logs I could grab to sort the problem out, let me know.

---

you need
fastboot.exe flash recovery TWRP_3.0.0-0-ido.img
and then
fastboot.exe boot TWRP_3.0.0-0-ido.img
the first boot from file actually make this recovery flash permanent

---

Oh thanks ! I feel dumb for not trying to boot directly the img file.

---

mouhii said:
Oh thanks ! I feel dumb for not trying to boot directly the img file.
Click to expand...
Click to collapse
Also, make sure to execute commands from the second post! They will terminate any possible recovery replacement!

---

usblaidas said:
Also, make sure to execute commands from the second post! They will terminate any possible recovery replacement!
Click to expand...
Click to collapse
Yeah, that's what I was planning to do but once under the recovery

---

mouhii said:
Yeah, that's what I was planning to do but once under the recovery
Click to expand...
Click to collapse
you have to execute them before even flashing recovery

---

usblaidas said:
you have to execute them before even flashing recovery
Click to expand...
Click to collapse
Oh I didn't realise that but it makes sense.
However when I use adb root under android, I have "adbd cannot run as root in production builds". Do I need a modified boot.img for that or am I missing something ?

---

mouhii said:
Oh I didn't realise that but it makes sense.
However when I use adb root under android, I have "adbd cannot run as root in production builds". Do I need a modified boot.img for that or am I missing something ?
Click to expand...
Click to collapse
Make sure to go to Security app, Permissions, and make sure to enable root