[OFFICIAL] TWRP 3.1.0-0 Recovery for Redmi 3
- Thread starter Anik_khan
- Start date
-
- Tags
- ido recovery redmi 3 twrp xiaomi
The command is right, check where you put the recovery image, type full address always a good idea e.g "c:/xxx/xxx/..."
krasCGQ
Inactive Recognized Contributor
Internal storage is a part of your data partition. ¯\_(ツ)_/¯
I need some help here. After reformatting data&system to f2fs, I'm unable to boot to restored OS.
By reflashing ROM & OpenGApps I ended up on error message Incompatible Device Detected, your device: arm (wrong)
TWRP gives this warning on restore:
WARNING: This /data backup was made by filesystem ext4! Backup won't boot if it won't change back to ext4.
The question is: will I be any way able to restore my data partition after filesystem change?
Last edited:
krasCGQ
Inactive Recognized Contributor
1) You shouldn't wipe system to f2fs. Only do it for data and cache.
2) Tick "Use rm -rf instead of formatting" in TWRP settings before restoring ext4 backup.
It succeeded, but was painful (lost all data on internal storage) and minor problem with reflashing OpenGapps (first flash after conversion needs to be done on clean system).
After all the results aren't so good as I expected, A1 Bench for internal memory gives rates 58/93 MB/s which is worse than ext4. Is there a kernel, scheduler that performs better?
One question more, why TWRP won't allow to f2fs system partition? I always end up with ext4. Is there a trick to force having even system f2fs?
After all the results aren't so good as I expected, A1 Bench for internal memory gives rates 58/93 MB/s which is worse than ext4. Is there a kernel, scheduler that performs better?
One question more, why TWRP won't allow to f2fs system partition? I always end up with ext4. Is there a trick to force having even system f2fs?
krasCGQ
Inactive Recognized Contributor
Even when it does, ROM flash just reformats it back to ext4.
Sent from my Redmi 3 using XDA Labs
#brokenEnglish :v
How to install the latest vers, i updated from v.3.0.0(cofface) it says the instalation is success but when i boot to recovery it boot to system not to twrp, so my twrp was gone, my question is whats wrong about my step? It happended too when i used rashr.
How to install the latest vers, i updated from v.3.0.0(cofface) it says the instalation is success but when i boot to recovery it boot to system not to twrp, so my twrp was gone, my question is whats wrong about my step? It happended too when i used rashr.
New version 3.2.1-0:
What's new in 3.2.1-0:
* 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)
Download:
https://eu.dl.twrp.me/ido/
What's new in 3.2.1-0:
* 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)
Download:
https://eu.dl.twrp.me/ido/
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 rootThat's itCode:adb disable-verity
Enjoy
hi, i never use miui 9 since this rom released. now i'm trying it. im flashing it on redmi 3. flash twrp and try to root using supersu. i've been trying all methods sadly end up boot loop every time. i did every single step on miui thread. those that include modified boot.img and else but still bootloop. is it have something to do with this dm-verity???
Yes,
There is also on the MIUI forum a thread called 'A script to disable dm-verity and forced encryption".
After flashing twrp you can also flash this zip file before first boot to disable it.
Or try the instructions from the post you quoted.
Dm-verity
I read those lazyscript flash to disable dm-verity, I'll try it later for last option.
Never had this on custom ROM
But ?
adb cannot run as root in production builds
disable-verity only works for userdebug builds.
Ok thanks for your answer
I read those lazyscript flash to disable dm-verity, I'll try it later for last option.
Never had this on custom ROM
But ?
adb cannot run as root in production builds
disable-verity only works for userdebug builds.
Ok thanks for your answer
Hi,
1. I'm on MIUI 7 China Stable straight from the factory currently, can I unlock bootloader with this ROM?
2. After I got bootloader unlocked and flashed twrp using fastboot, when do I run "adb disable-varity"? In fastboot? In TWRP? Boot into MIUI again?
3. It says for running "adb disable-varity" requires root, but I can't get root if I don't enable system modification, and enabling system modification will bootloop the system, any way around this?
4. Do I need to run "adb disable-varity" after every ROM flash? I intend to use Lineage14.1.
1. I'm on MIUI 7 China Stable straight from the factory currently, can I unlock bootloader with this ROM?
2. After I got bootloader unlocked and flashed twrp using fastboot, when do I run "adb disable-varity"? In fastboot? In TWRP? Boot into MIUI again?
3. It says for running "adb disable-varity" requires root, but I can't get root if I don't enable system modification, and enabling system modification will bootloop the system, any way around this?
4. Do I need to run "adb disable-varity" after every ROM flash? I intend to use Lineage14.1.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
55Team 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.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_khan5Gonna leave my standing mark here.
Anyway, I've unpacked the F2FS compatible TWRP and replace the built-in kernel with my own kernel based on the official CAF sources + upstreamed mainline kernel + F2FS drivers updates and LineageOS updates. I've tested the recovery by creating and deleting folder via terminal on my F2FS formatted 32GB MicroSD card and everything goes like it should and never crash or panic and reboot again.
The problems we had with F2FS and the F2FS compatible TWRP is very simple, the kernel panics with every single command done on F2FS formatted partitions (except wiping).
Just shut up you funky man.
Okay. Here's the link and the kernel source used.
Why not create a new thread for this?
This is only a slight modification (kernel replacement) to the F2FS compatible TWRP done by me, so it's a nonsense to create another thread just with this change.
Credits
- @Anik_khan
- @osm0sis - Android Image Kitchen
- @arter97
- Someone else...
Sent from my Redmi 3 using XDA Labs
