[RECOVERY][kenzo/kate] TWRP 3.1.0-0 for Xiaomi Redmi Note 3

TheStrix

Recognized Developer
May 10, 2014
680
6,371
0
Mumbai
TheStrix.github.io
Team Win Recovery Project



This is a unified build for both the Redmi Note 3 (kenzo) and the Redmi Note 3 SE (kate)

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.

Read more about TWRP here: https://twrp.me/about/

CHANGELOG for 3.1.0-0:

-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention

CHANGELOG for 3.0.2-0:

-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.

CHANGELOG for 3.0.1-0:

-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements

CHANGELOG for 3.0.0-0:

-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks

WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.

Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.

Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.

We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!

DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.

FEATURES:
  • MTP support
  • USB OTG storage support
  • Hardware Qualcomm-based full-disk encryption support ( ext4 & f2fs )
  • f2fs file system support (read, write, format, backup & restore)
  • Covers more partitions for nandroid backup (fstab)
  • ADB root
  • Full SELinux support
  • Built with android 7.1 tree

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

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

XDA:DevDB Information
TWRP for Redmi Note 3, Tool/Utility for the Xiaomi Redmi Note 3

Contributors
TheStrix
Source Code: https://github.com/TeamWin


Version Information
Status: Stable

Created 2017-03-04
Last Updated 2017-03-21
 
Last edited:

TheStrix

Recognized Developer
May 10, 2014
680
6,371
0
Mumbai
TheStrix.github.io
FAQ:

WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?

Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Personally, I'd have tried this after 15 minutes.

WHY DOES F2FS MAKE TWRP SO SLOW?

When TWRP boots up or wipes partitions and a few other scenarios, it checks each partition to see how much disk space is used. Ext4 handles disk usage calls quite efficiently and will finish this very fast. F2FS on the other hand is very slow when it comes to checking disk usage. We're unsure why this is. Every file on the F2FS formatted partition adds a little more time, and a device that is 30 GB full could take up to 10 minutes to boot TWRP!

HOW DO I GET LOGS SO WHEN I COMPLAIN I'M NOT COMPLETELY IGNORED OR SHAMED BY OTHER USERS?

To get logs while in TWRP, you should connect your device to your PC and use adb.
adb pull /tmp/recovery.log
adb exec-out dmesg > dmesg.log

This will create 2 files in the directory your shell is currently in, recovery.log and dmesg.log. You will need to upload these somewhere such as a pastebin or Google Drive. You can also attach it to your XDA post (recommended!)

If you are having an operating system boot issue, you should gather a ramoops log instead. Do this while in TWRP after the failed boot:
adb exec-out "tar c /sys/fs/pstore 2>/dev/null" > pstore.tar
 
Last edited:

fardeenah

Senior Member
Nov 7, 2016
276
43
28
i did a few benchmark on f2fs, but didnt notice a major difference on kenzo, is it really the case? or is F2Fs really worth it
 

redbullman

Senior Member
Dec 15, 2009
589
107
63
i did a few benchmark on f2fs, but didnt notice a major difference on kenzo, is it really the case? or is F2Fs really worth it
With latest lineage os and Radeon kernel I get 89500 with Antutu. Changing to f2fs gets me 91500. 1 would say a 2000 Antutu increase is pretty impressive.
 
G

GuestK00171

Guest
Antutu don't test disk-speed! So your 2000 extra points have another reason, maybe media-indexing at phone-start etc...ext4 is best filesystem for your phones because it is fast in ALL cases and rock solid!
 

jianwen03

Senior Member
Jan 23, 2017
244
96
0
Hey guys I converted data & cache from ext4 to f2fs (backup data>wipe dalvik+format cache f2fs+format data f2fs>restore data backup with rm-rf) and internal storage was wiped in the process. I don't remember wiping internal storage and can anyone help me check whether I was careless or it is a bug.
 

Draygon

Senior Member
Jul 11, 2011
464
91
48
With the latest version, I'm not able to install kenzo custom roms to my kate phone.

Getting following error, tried different roms:
"This package is for device: kenzo; this device is kate.
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/Nitrogen-OS-kenzo-20170304.zip'
 
  • Like
Reactions: Dims_Camper

jianwen03

Senior Member
Jan 23, 2017
244
96
0
So using f2fs is better than ext4?
Lot's of devs say no. I can't feel the difference overall but opening Settings>Apps in f2fs is a whole lot faster than in ext4 for me.
Btw ext4 is compatible with more stuff as you might face issues flashing zips to f2fs partition (which I haven't faced yet).
 
Last edited:
  • Like
Reactions: LeoYL

Efuma

Senior Member
Dec 1, 2012
82
51
0
Taipei
With the latest version, I'm not able to install kenzo custom roms to my kate phone.

Getting following error, tried different roms:
"This package is for device: kenzo; this device is kate.
'
The error probably arose due to this being a unified TWRP for Kenzo and Kate . Apparently, this TWRP is able to differentiate between Kenzo and Kate devices, and has assigned a specific flag to each identification. Thus , Kenzo is ID'd as a Kenzo , and Kate is ID'd as a Kate.

This is actually very bad news for Kate users. If you look around Note 3's ROM scene, every single custom ROM is named as a Kenzo release and is keyed for Kenzo. The only reason kate users were able to install these Roms was because they were using Kenzo TWRPs. Despite being Kate, the TWRP fooled the ROM into thinking it is Kenzo and then allowed the installation.

In every ROM and in some other zip installs, there's a file called updater.script. This file, actually the first lines of the file, is where the ROM performs its only device check.

So how does a Kate user bypass this ERROR 7? Well, there are many ways:

1. Change the two mentions of "Kenzo" on the first lines of the ROM 's updater.script to "Kate", then flash like before,

2. Or, urge the op to make a Kenzo-only TWRP, and flash.that,

3. Or beg the op to modify the TWRP to forgo this updater.sfript check.

Personally, I'd just stay away from Kate or Kenzo/Kate unified TWRPs. Changing update.script on every ROM you want to flash can become very tedious.

It's a lot easier being a fake Kenzo, then a real Kate.
 

Freddycom

Senior Member
Sep 18, 2012
88
19
0
So using f2fs is better than ext4?
I am using f2fs for 2 days now and it is definitely snappier when it comes to multitasking. On ext4, the recents button was a bit slow for me, pressing and showing up the recents sometimes took a good half second, was unsure if I even pressed it but then oh look it appeared. No such issue for f2fs, everything is happening as I'm pressing buttons.
 
  • Like
Reactions: LeoYL

D4xel

Senior Member
Jun 24, 2015
196
17
0
Florence
With the latest version, I'm not able to install kenzo custom roms to my kate phone.

Getting following error, tried different roms:
"This package is for device: kenzo; this device is kate.
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/Nitrogen-OS-kenzo-20170304.zip'
Did you install Kate's TWRP or Kenzo's one?
 

schmanto

Senior Member
May 28, 2015
53
21
0
@TheStrix
System won't boot after changing from M4 recovery to this one..
but this time, I'm even unable to revert back to M4 -> system not booting, just mi logo > reboot
m4 recovery also wouldn't boot
so now I'm completely stuck (given my limited capabilities).

btw: I actually wasn't able to change to another recovery since I changed to f2fs on M4 (tried zcx, dad1, ... )

logs are here: https://drive.google.com/open?id=0B9NuN8yWvpeZQzFDVGF4UTREWnc

edit: found out that it might be a problem with latest AGNI kernel: I unbricked and reinstalled (CM13), and my problem seems to be reproducable with latest releases - radon works however..
 
Last edited:

sumchamp

Senior Member
Dec 25, 2010
295
90
0
Mumbai
@TheStrix
System won't boot after changing from M4 recovery to this one..
but this time, I'm even unable to revert back to M4 -> system not booting, just mi logo > reboot
m4 recovery also wouldn't boot
so now I'm completely stuck (given my limited capabilities).

btw: I actually wasn't able to change to another recovery since I changed to f2fs on M4 (tried zcx, dad1, ... )

logs are here: https://drive.google.com/open?id=0B9NuN8yWvpeZQzFDVGF4UTREWnc
If you are able to boot into recovery, format partitions as ext4 and flash recovery of your choice.
 
  • Like
Reactions: fourzero0