[OFFICIAL] TWRP 3.0.2-2 Recovery for Redmi Note 3 [SnapDragon]

Search This thread

emuzychenko

Senior Member
Mar 31, 2016
51
196
53
Novosibirsk
How that can be "normal"? All guides (since TeamWin has no their own) say that TWRP makes Nandroid backup, a full snapshot of the device. It means all data stored in device memory. TWRP offers to backup partitions, not directories. A backup of "data" partition means all internal memory data.

Of course, data amount can be huge. But how else to make a full, complete backup of the device?
 

d1eter

Senior Member
Feb 13, 2007
89
4
remote island
I need to ask (and understand) these...

my kenzo was in China Stable 7.3.8
I got it unlocked, officially and successfully,
flashed modified boot.img (created from China Stable 7.3.6 fastboot)
flashed twrp-3.0.2-2 and root.
everything works fine.

then I decided to try MIUI 8 China Dev,
so I MiFlashed China Dev 6.7.7 fastboot (flash all) , successfully.
and immediately received OTA 6.7.14, and update successfully.
then I realized I lost the TWRP boot recovery.

Question:
1. to bring back the TWRP, can I just flash the recovery image?
or do I need to create a new modified boot image from China Dev?

2. in the future, if there's new OTA release, can I just update without any problem?
(problem = losing TWRP, root, bootlop, etc.)

3. if I want to flash fastboot ROM, is there a way to prevent TWRP recovery being overwritten?

4. if I wish to change to another MIUI ROM, do I need to everytime create a modified boot image based on that ROM which I want to flash?

Thank you very much.

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.

...
 

zinconnu

Senior Member
Jun 12, 2008
398
24
How that can be "normal"? All guides (since TeamWin has no their own) say that TWRP makes Nandroid backup, a full snapshot of the device. It means all data stored in device memory. TWRP offers to backup partitions, not directories. A backup of "data" partition means all internal memory data.

Of course, data amount can be huge. But how else to make a full, complete backup of the device?

I understand, but i have three different phones that can do nandroid backups (with TWRP or 4ext) and none of them backup this partition. There must be a reason.
BTW, is there an app to mirror this partition to SD card?
 

emuzychenko

Senior Member
Mar 31, 2016
51
196
53
Novosibirsk
There must be a reason.
Which reason could be there?

Much more reason is to make it configurable. Since TWRP offers to backup a partition but really backups only a small part of it, it must at least warn the user to be informed.

BTW, is there an app to mirror this partition to SD card?
There are some ways to swap internal memory and SD card so /sdcard if mapped to an external SD.

But it seems to be strange to buy a phone with 32-128 GB of internal memory but use external SD to store data. And if you need to use two SIMs, you have no access to your app/data stored on external SD.
 

kRel

Senior Member
May 17, 2008
439
49
Stupid question: updating to 3.0.2-2 starting to TWRP 3.0.2.-1 must be done by selecting "Recovery" partition . . . It's correct ?

 

Alexey71

Senior Member
Oct 13, 2012
1,632
858
Russian
TWRP not work MIUI 8 android 6.0.1
Screenshot_1970-02-26-17-40-50.pngScreenshot_1970-02-26-17-40-54.pngScreenshot_1970-02-26-17-40-59.png
 

Attachments

  • recovery.log
    29.1 KB · Views: 18
Last edited:

spezzlk

New member
Aug 11, 2016
1
0
URL is expired. New one, PLEASE?

(Disregard the screenshot. I tried it in a different browser, and found the domain is expired.)

Hello there - I get the normal fastboot screen after flashing the img I think it is because I didnt flash the modifide img?
Can I verify that my bootloader is unlocked somehow? I did the unlock on the last miu global dev and did a update to the latest one.
Okay i verified my device is unlocked with fastboot oem info.

But I need the modified img PLZ the link is down

EDIT 2:
i modified my bootimage from and removed the ",verify" and flashed it with fastboot. After that i flashed twrp img and rebooted the phone.
I still have to standart fastboot recovery. I dont know how to fix this.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 68
    Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.



    CHANGELOG for 3.0.2-0:

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

    CHANGELOG for 3.0.1-0:

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

    CHANGELOG for 3.0.0-0:

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

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

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

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

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

    CHANGELOG for 2.8.7.0:

    -Initial ground work for software drawn keyboard (_that)
    -Fix handling of wiping internal storage on datamedia devices (xuefer)
    -Allow DataManager to set and read values from the system properties (xuefer)
    -Fix crash when taking screenshots on arm64 devices (xuefer)
    -Fix error message after an ORS script completes (Dees_Troy)
    -Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
    -Add system read only option – more details below (Dees_Troy)
    -Add resize2fs and GUI option to run resize2fs (Dees_Troy)
    -Fix crash loop caused by empty lines in AOSP recovery command file (_that)
    -Prevent duplicate page overlays such as multiple lock screens (mdmower)

    Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.

    System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.

    resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.

    This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.

    DOWNLOAD:
    Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
    1) Download the latest version from our website on your device
    2) Reboot to TWRP
    3) 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 Note 3

    TWRP Downloads

    NOTE: If you are flashing TWRP for the first time then you need to first flash modified boot.img from here and then TWRP

    XDA:DevDB Information
    Recovery for the Xiaomi Redmi Note 3

    Contributors
    vibhu0009
    Source Code: https://github.com/TeamWin
    Device Tree: https://github.com/TeamWin/android_device_xiaomi_kenzo


    Version Information
    Status: Stable

    Created 2016-04-06
    Last Updated 2016-04-06
    7
    Sorry for the delay guys. Am little held up with personal life.. will push the commits to twrp gerrit when i have time and you will get the new update :)
    7
    New update will be coming soon with F2FS support :)
    7
    Hey,
    I just tried this Recovery & as of now it is not able to flash MIUI zip files! Earlier Chinese recoveries were able to flash full zips at least! [OTA cant be flashed though]
    Edit- Threre is some weird error as - Failed to mount '/factory' (Invalid argument)


    Doesn't effect anything.. But new build is coming soon with this error fixed..
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone