Database Develop

[RECOVERY][OFFICIAL][Kenzo/Kate][TREBLE][V3.2.1-028-Beta] Red Wolf Recovery Project

{
"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"
}
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Red Wolf Recovery is custom recovery based on TWRP source code however some things are working here slightly different then you might expected. The main objective of this project is to provide stable recovery with features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. This recovery is also first recovery on the world with password protection.​
Based on TWRP version: 3.2.2
For devices: Kenzo & Kate
Authors build: ATG Droid
Developers: ATG Droid
Thanks: z31s1g (for the base of his theme), osm0sis (for his bootimage binaries), etc.
Features:
Code:
[B]Translated to EN & CZ [/B]
- Password protection
- Flashlight
- MIUI Incremental OTA Support
- Support automatic reboot after the restore process
- Advanced deactivation of the stock recovery
- Support for automatic deactivation of the dm-verity & forced encryption...
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- A lot of other things, just look at it ;)
*[B] Changes for security reasons [/B]*
- MTP isn't starting until user enter correct password
- Deactivated support of the custom themes
Some differences to the official version:
Code:
[B][COLOR="red"]- get out of here if you are pirating apps. this recovery is not for you[/COLOR][/B]
- always up-to-date with the latest TWRP changes
- compiled on omnirom-7.1 source
- kernel compiled inline with the recovery
- There isn't bug with reboot from recovery to recovery
- more languages
- other improvements from Features and Changelog lists
Changelog:
Code:
[B][U]RedWolf-V3.2.1_028-Kate_Kenzo-Beta.img[/U][/B]
* File-manager: Add support for rendering of multiple selected files & ability to do a specific action for these files at once
* Force rendering of the different GUI icon element object for zip files under the GUI Scroll list, since file-manager show special action for them
* Revert changes which caused issues with slow reboot in 027
* MIUI-Updater: Fix sometimes possible double declaration of the final install status
* DataManager: Fix the TWRP's missing LOGINFO mount point for Output_Version
* RWDumwolf: Add support for the different fstab path on some devices
* RWDumwolf: Better handle the process of modifications to the default properties and let user know about the number of modified ones
* RWDumwolf: Find and remove start of flash_recovery service from inits, if it exists
* Recovery: Don't rename scripts under the /system/bin /system/etc for stock recovery replace, instead of it set different permissions to cause issues with execution
* RWDumwolf: Cleanup
* Updater: Properly handle info about the OSE package signature
* Recovery: Directly call start of the ADB if at the start of main we aren't able stat password file
* Recovery: Correctly handle ADB with recovery password related changes
* Recovery: Update to Oreo tree
* Partition-List: Add new list types for OSE partitions and storages for backup/restore process
* Installation: Load zip entries directly to buffer instead of extracting them
* ORS: Reboot on the sucessfull installation is now optional based on user's selection from the GUI
* ORS: Call Deactivation Process even if reboot on finished ORS isn't allowed or isn't forced by the ORS result
* OPTM: Call set action with the empty value in case that value should be positive
* OPTM: Fallback to main without variable which would be needed to be parsed is now directly down with call of home
* GUI: Allow user to select any active storage for the OSE backup/restore process
* OPTM: Call clear action instead of set if argument is negative
* GUI: Allow user to select OSE partitions for the backup/restore process, instead of the previous direct definition
* Installation: Add support for the format of A/B packages on the OSE zip detection
* GUI: Remove redefinitions of objects from screen page, since they're already defined on one overlay
* PartitionManager: Add new fstab flag to exlude partition from the GUI mount section, cust isn't really needed to be here if we want to use double mount points for one block device
* GUI: Remove for us the useless theme loading parts from previous builds
* Installation: Set install status info to tmpfs first and then update the status in cache during the log file update, since the previous implementation was just slowing us
* Recovery: Set path for screenshots directly to main folder instead of previous resource one
* TWFunc: Cleanup
* GUI: Improve flashlight compatibility with different devices
* OSE: Improve backup/restore call
* Device-Tree: Add support for unofficial treble support on officialy supported devices
* GUI: Fix missing page on the rebootcheck call which caused complete lag during the reboot with formatted system partition
* Recovery: Call Deactivation Process on reboot if there wasn't at least single call during the main threads
* RWDumwolf: Force persist.sys.recovery_update to false during the cleanup process
* OSE: Fix the variable mismatch caused by global variable definitions without handling the previous possible defined value
* INIT: Add new triggers for the ADB startUP.
[B][U]RedWolf-V3.2.1_027-Kate_Kenzo.img[/U][/B]
- If screen is turned off then automatically detect AROMA Installer package and unblank screen before starting the update binary which is going to call AROMA GUI, so we won't be stuck at the black screen since AROMA engine require screen to be turned on.
- Added ability to change OTA Survival driver properties from the recovery GUI, allowing recovery to support "out of the box" almost all incremental OTA updates from different OEMs/custom ROMs out there (as long as they have correctly formatted metadata).
- Notify user about the current activity of the deactivation process - that's handled under the console
- Improved dumwolf driver
- Removed the vibration feedback from all GUI elements
- Automatically resize bootable partitions during nandroid backups
- Changed theme to black/white/red style based on @TBO material theme
- Data files aren't anymore saved on the storage partitions, which means that we're now able to survive even encrypted device.
- Some bug fixes and improvements...
[B][U]RedWolf-V3.2.1_026-Kate_Kenzo.img[/U][/B]
- This is just a quick bug fix release for MIUI users. So is highly recommend to update to this build if you are using MIUI.
[B][U]RedWolf-V3.2.1_025-Kate_Kenzo.img[/U][/B]
- Fixed crash of the recovery while running OTA_RES.. (So MIUI OTA is now working again)
- General bug fixes and improvements
- Fixed bug with MIUI Updater app showing error that installation failed after installation of full ROM
- Deactivation process is now called only when it's really needed
+ Some device specific changes...
Installation instructions:
- Download image and flash it the way you want.. You can use some apps, fastboot or your current custom recovery (if it's supported).
Known Bugs:
- There isn't any!
Downloads:
Latest build for Xiaomi Redmi Note 3 PRO/SE (Kenzo/Kate)
Links to builds:
RedWolf-028-kenzo-Beta.img
Links to MD5 files:
RedWolf-028-kenzo-Beta.img.md5
Warning:
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery. But your device can be still reinstalled using fastboot or Miflash.
XDA:DevDB Information
Red Wolf Recovery Project, Tool/Utility for the Xiaomi Redmi Note 3
Contributors
ATG Droid, Dadi11
Source Code: https://github.com/RedWolfRecovery
Version Information
Status: Testing
Created 2017-07-08
Last Updated 2018-07-22

Reserved
Kernel: https://github.com/TeamHorizon/android_kernel_xiaomi_kenzo/tree/o

Reserved
Screenshots!!

Woow new twrp

Thanks DEV. With every new and advanced developments like this, our DEVICE keeps on reviving. Thank you very much.
will test it and let you know if anything is quirky.
:good::good::good::good::good:

ATG Droid said:
Known Bugs:
Search engine for Snap Camera is right now broken. It's still searching for TWRP app so if you want to use it then you have to unfortunately uninstall official TWRP app.
Click to expand...
Click to collapse
So if i don't install twrp app, will snap camera search engine work?

Oh another recovery

Does the bug which causes this recovery non functional on Kenzo but functional on Kate fixed? And is it stable now?
Does it support f2fs?
Sent from my Redmi Note 3 using XDA Labs

AliGulzar-AF said:
Does the bug which causes this recovery non functional on Kenzo but functional on Kate fixed? And is it stable now?
Click to expand...
Click to collapse
+1, same question here. The password protection is the feature I've been waiting for so long.

rád tě zase vidím @ATG Droid

Still not working on kenzo grains/glitches on screen when i open in recovery.

sushank360 said:
Still not working on kenzo grains/glitches on screen when i open in recovery.
Click to expand...
Click to collapse
Thanks for confirming
Sent from my Redmi Note 3 using XDA Labs

I' using Kate so i can't test it.. So if there is someone who have Kenzo then please test if it is working.

sushank360 said:
Still not working on kenzo grains/glitches on screen when i open in recovery.
Click to expand...
Click to collapse
Thanks for reporting...

Using kenzo here..
Everything seems to be working normally
Haven't flashed any zip yet.
Will update later

exodius48 said:
So if i don't install twrp app, will snap camera search engine work?
Click to expand...
Click to collapse
If you have installed TWRP app on your device then recovery will not allow you to install Snap Camera.. Also if you don't have installed TWRP app then recovery will continually offer installation of the Snap Camera even if Snap Camera is installed.. But this bug shouldn't be a huge problem to fix in the next updates.

Password protection is the best

guess the password feature should br adopted to official twrp ...anyway nice work mate except for some wierd blurry screen on kenzo sometimes :fingers-crossed:

I forget that there is also option to get notified about finished installation.. Just try to click on install / find some zip file / and before you swipe to install it check here "Notify about finished installation".. :fingers-crossed:
Edit: Just uploaded new build for Kenzo.. So please test it and report back.

For me the latest version for kenzo is working perfectly i have also clean flashed a rom and it's working. I found only one bug: the shutdown from reboot menu isn't working.

[RECOVERY][OFFICIAL][SAGIT][V3.2.1-028-Beta] Red Wolf Recovery Project

{
"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"
}
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Red Wolf Recovery is custom recovery based on TWRP source code, however some things are working here slightly different then you might expected. The main objective of this project is to provide stable recovery with features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. This recovery is also first recovery on the world with password protection.​
Based on TWRP version: 3.2.1
For devices: Sagit, Mido, Land, Kenzo & Kate
Authors build: dadi11
Kernel: https://github.com/RedWolfRecovery/rw_device
Developers: ATG Droid, dadi11 & Devil7DK
Thanks: z31s1g (for the base of his theme), Ray Li (For his useful advice in the beginnings), osm0sis (for his image scripts), dadi11 (for his awesome kernel & mido builds) etc.
Features:
Code:
[B]Translated to EN, PL, zh_cn, & CZ [/B]
- Password protection
- Flashlight
- MIUI Incremental OTA Support
- Built-in latest Magisk, SuperSU & AromaFM
- Support two screenshot GUI actions - Power+VolDown to save screenshot in to the internal storage &
Power+VolUp to save screenshot in to the external storage (Will be automatically saved in to the internal in case
that external storage doesn't exist).
- Support automatic reboot after the restore process
- Recovery can automatically modify some props in the ROM directly during the installation
- Some built-in scripts from community
- Tap to wake support
- Advanced deactivation of the stock recovery
- Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- Support "set on boot" settings.
*[B] Changes for security reasons [/B]*
- ADB isn't starting automatically at the start of the recovery. You have to activate it in recovery
- MTP isn't starting until user enter correct password
- Deactivated support of the custom themes
Some differences to the official version:
Code:
[B][COLOR="red"]- get out of here if you are pirating apps. this recovery is not for you[/COLOR][/B]
- always up-to-date with the latest TWRP changes
- compiled on omnirom-7.1 source
- fixed backup/restore of Firmware
- more languages
- other improvements from Features and Changelog lists
Changelog:
Code:
[B][U]RedWolf-V3.2_027[/U][/B]
- If screen is turned off then automatically detect AROMA Installer package and unblank screen before starting the update binary which is going to call AROMA GUI, so we won't be stuck at the black screen since AROMA engine require screen to be turned on.
- Added ability to change OTA Survival driver properties from the recovery GUI, allowing recovery to support "out of the box" almost all incremental OTA updates from different OEMs/custom ROMs out there (as long as they have correctly formatted metadata).
- Notify user about the current activity of the deactivation process - that's handled under the console
- Improved dumwolf driver
- Removed the vibration feedback from all GUI elements
- Automatically resize bootable partitions during nandroid backups
- Changed theme to black/white/red style based on @TBO material theme
- Data files aren't anymore saved on the storage partitions, which means that we're now able to survive even encrypted device.
- Some bug fixes and improvements...
[B][U]RedWolf-V3.2_026[/U][/B]
- This is just a quick bug fix release for MIUI users. So is highly recommend to update to this build if you are using MIUI.
[B][U]RedWolf-V3.2_025[/U][/B]
- Fixed crash of the recovery while running OTA_RES.. (So MIUI OTA is now working again)
- General bug fixes and improvements
- Fixed bug with MIUI Updater app showing error that installation failed after installation of full ROM
- Deactivation process is now called only when it's really needed
- Updated kernel
[B][U]RedWolf-V3.2_024[/U][/B]
- Fixed GUI color glitch while starting Aroma Installer update-binary
- Optimized pigz runtime process
- Updated recovery base to the AOSP 8.1.0 & TWRP 3.2.1
- Highly improved signature verification for Incremental packages so now we can be really sure if the package is compatible with the ROM.
- Introduced a file based backup/restore engine. Expect it to be improved with the next builds...
- Improved security related to the password protection
- Fixed loading of the AromaFM config file
- System survival process for Incremental packages is now set by default
- Code optimizations
- Removed the dumwolf process
- Added signature check for incremental OTA survival so we won't be unnecessarily creating a new one if it's signed under the same access key
- Magisk updated to the version 15.1
- Added Indonesian language
- Fixed issues with Chinese characters...
- Governor which is changed by the action in the recovery GUI is now automatically set for all cores instead of only four.
[B][U]RedWolf-V3.2_023[/U][/B]
- Updated recovery base to the TWRP version 3.2.0
- Fixed issue with recovery sometimes showing "NO-OS" page even when OS is installed
- Merged: Fstab V2, minui updates, Keymaster 3.0 support, ADB updates, fixes related to the compiling errors...
- Added patch against the pirating applications
[B][U]RedWolf-V3.1_022[/U][/B]
- Small improvements in the installation process
- Recovery will now automatically warn the user in case that user selected to install the zip which contain a bootloader
- You can now wipe installed substratum overlays directly from the "advanced wipe" section
[B][U]RedWolf-V3.1_021[/U][/B]
- Automatically return install error if there is any issue with Incremental OTA Survival
- Added option to also backup system partition for Incremental OTA Survival (It's not always needed, but just in case it's better to backup it.)
- Added support for the compatibility verification of the Incremental Package
- Rebuilded & improved installation process
- Fixed starting process not being disabled correctly in case that we are running ORS
- Translation update
- Added support for devices with 2GB RAM or less... (Check installation process of this build for more info)
- Added checkbox for activation/deactivation of the boot check (Disable only if you really need to).
- Fixed booting problems on some custom ROMs which don't have gzip compressed ramdisk
- Removed bookmark feature
- Added ability to unzip files using the stock filemanager.
- Added search selection for the stock filemanager.
- Fixed 'No OS' on system image restore after wipe
- Merged some latest commits from TWRP gerrit
[B][U]RedWolf-V3.1_020[/U][/B]
- Fixed flashing of the images in the previous 018 build
- Added back support for unpacking of the LZ4 compressed ramdisk
- Fixed bookmark feature
[B][U]RedWolf-V3.1_019[/U][/B]
- Disable TWRP installation directly during the first boot
- Default time zone was set to CEST
- Use military time as default time.
- Support of the custom themes was completely removed from the installation process
- Few fixes & improvements in the strings.
- Default value of the RedWolf specific vibrations was slightly increased
- Improved saving/loading of the AromaFM config file.
- User can now select if recovery should disable stock recovery when system is mounted as read-only.
- Default color of the recovery was set to red.
- Fixed automatic reboot if the installation process was unsuccessful
- Center time in the statusbar as default
- Show CPU temp in statusbar as default
- Added "Red Wolf No-OS search engine". Enable this if you are sometimes getting No-OS installed error even when OS is installed.
- Added back support for extra languages
- Added support for Talian language
- Updated Chinese (simplified) translation of the AromaFM by LiuNian and Pzqqt
- Fixed displaying of the extra languages
- Improved mounting of the partitions during the applying of set on boot values
- Fixes with "stuck at unmounting"
- Highly improved speed of the recovery while setting up a new password, changing accent color or setting a new splash screen
- Magisk updated to the V14.3
- Recovery now won't allow the user to enter special characters while entering the password (Causing issues...)
- Few improvements with the Android Oreo installation
- Updated kernel
- Added ability to select if recovery should automatically disable forced encryption in the ROM
- Recovery will now automatically rename scripts in the system if the "Aggresive stock recovery deactivation" is enabled
- Added ability to select if recovery should automatically enable/disable USB Debugging in the ROM
- Removed some useless files to save the space
- Added support for saving the set on boot values also during the automatic reboot
- Redesigned flashlight icon
- Recovery now won't allow the user to enter the space in to the backup name
- Improved support of the last status checking of the MIUI ROM
- Recovery now won't show any button after the cancelled reboot action untill the sleep action won't be running anymore
- You can now select if recovery should also automaticaly reboot after the successfuly finished restore process
- Recovery will now hide the automatic backup feature if the system partition is mounted as read-only
- Updated recovery base to the AOSP 8.0.0
- Updated image drivers
- Added ability to select if recovery should automatically enable/disable "ro.adb.secure" property in the ROM
- Recovery will now automatically disable starting of the flash_recovery service if the "Aggresive stock recovery deactivation" is enabled (this process is also compatible with the backup of the init.rc by Magisk or SuperSU).
- Added new section called "Special Actions" in to the advanced menu
- Updated & optimized flashlight drivers
- Added ability to select if recovery should automatically enable/disable "ro.secure" property in the ROM
- Added ability to select if recovery should automatically enable/disable "ro.allow.mock.location" property in the ROM
- Highly improved support of the Incremental Package installation, detection etc.
- Updated Chinese (simplified) translation of the recovery by LiuNian and Pzqqt
- Added support for the complete deactivation of the secure boot in the MIUI based ROMs
- ADB is now automatically starting as root
- Added support for the RedWolf update package
- Default theme of the AromaFM was changed to holo black with the sense icons and automount turned on
- SuperSU Updated to the 2.82 SR5
- Updated ramdisk cleaner & added support for more kernels (thanks to @MOVZX's kernel installation scripts...)
- Small fixes with the /WOLF folder in the PartitionManager
- Highly improved speed of the reboot
- 'Deactivation process' is now automatically called during the installation instead of the reboot
- Imroved deactivation of the leds after the installation / backup / restore process.
- Fixed bug with recovery showing on the governor page that the active governor is "Interactive" even when user selected performance/powersave mode.
- Removed some GUI messages while we are installing built-in zips.
- And many other things which i don't remember anymore...
[B][U]RedWolf-V3.1_018[/U][/B]
- Fixed bugs with MIUI OTA Support to make sure that it will work even with newest beta builds of the MIUI
- Updated Polish translation by Daviteusz
- Fixed bugs in the Polish strings & edited the scale of the Russian strings
- Recovery will be now more aggressive if the process of the stock recovery doesn't want to be disconnected (Sometimes happen on some MIUI ROMs).
- Added detection of the installed ROM
[B][U]RedWolf-V3.1_017[/U][/B]
- Magisk updated to the V13.6
- SuperSU updated to the 2.82 SR3
- Added ability to automatically flash SuperSU config before the SuperSU - https://forum.xda-developers.com/apps/supersu/2017-08-13-supersu-config-t3655754
- Deactivated hw keys
- Added some missing back buttons
- Attempted to fix encryption
- Attempted to fix MIUI OTA installation - needs testing
- Removed extra languages (were not displayed properly)
- Small update which fixed deactivation of the dm-verity & forced encryption. Now you really don't have to flash the lazyflasher everytime when you are installing the MIUI ROM.
[B][U]RedWolf-V3.1_016[/U][/B]
- Fixed feature "Backup wifi, bluetooth & hosts" not to work if the user wiped the data partition using the "factory reset".
- TWRP source code was updated to the Aug 15, 2017
- Fixed recovery remembering the wipe list after setting a new gui page.
- Improvements with the mounting of the partitions during the boot
- Fixed led drivers on mido
- Fixed ability to set custom backup folder name & ADB ID
[B][U]RedWolf-V3.1_015[/U][/B]
- Updated with the latest TWRP changes
- Added flashlight switch on mido
[B][U]RedWolf-V3.1_014[/U][/B]
- Fixed recovery not deactivating the dm-verity, forced encryption, & stock recovery if the OS was detected as not installed. This issue was often happening on some MIUI ROMs.
- Improvements with the OTA update system of the MIUI.
- Fixed wrong reboot for some users.
- Added support for automatic deactivation of the dm-verity, forced encryption & stock recovery after finishing the OpenRecoveryScript process.
- Fixed recovery not deactivating the dm-verity & forced encryption during the automatic reboot after the finished installation.
- Better explain the current situation if the OS was detected as not installed.
- osm0sis's scripts "unpackbootimg" & "mkbootimg" can now be easily called from the script or terminal
- Improved the speed of the reboot
- Updated the community script "Fingerprint scanner fix" by Magua. It's now working again!
- Added NTFS & exFAT support
- Added more languages and updated Polish RedWolf translation by @Daviteusz
- Added FGO patch - https://goo.gl/GBkhMN
[B][U]RedWolf-V3.1_013[/U][/B]
- Slightly improved deactivation of the stock recovery during reboot after the zip installation
- Added ability to flash boot logo in the recovery
- Fixed firmware restoring issues
[B][U]RedWolf-V3.1_012[/U][/B]
- added F2FS support for mido
- added Night Mode (kcal) support for mido
[B][U]RedWolf-V3.1_011[/U][/B]
- Updated Polish translation by @Daviteusz
- Added few missing strings from the latest TWRP source
[Red Wolf] Install TWRP and root your device without breaking incremental OTA's!
Downloads:
Latest build for Xiaomi Mi 6 (sagit)
RedWolf-027-sagit.img
Screenshots:
Warning:
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery. But your device can be still reinstalled using fastboot or Miflash.
XDA:DevDB Information
Red Wolf Recovery Project for Xiaomi Mi 6, Tool/Utility for the Xiaomi Mi 6
Contributors
dadi11, ATG Droid, Devil7DK
Source Code: https://github.com/RedWolfRecovery
Version Information
Status: Testing
Created 2018-04-07
Last Updated 2018-04-07

Reserved
bugs: flashlight doesn't work, yet
https://t.me/joinchat/FZlpFECo9qt3MT5oRn-Bcg

Thanks Great Work

if you face issues with mounting Modem, redownload and flash the v27 image again

i was using your TWRP since kenzo, and mido. nice to see you here on sagit. does it support decryption on oreo? backup and restore works fine?

I flash the newest version, V3.2.1-027. After I enter system, I find the recovery is overwrite by system.
Steps:
1. flash recovery, Red Wolf V3.2.1-027.
2. Enter Recovery
3. Reboot to system
4. Reboot to recovery, the recovery is restored to original.
OS version: MIUI V9.2.3.0.OCAMIEK
P.S. I have renamed the file, /system/bin/install-recovery.sh, to /system/bin/install-recovery.sh.bak.
Does the under function work? or How to let it work? Thx.
"Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM"

@dadi11
sorry, but it seems it doesn't work on MIUI 8.4.5 Global Dev Oreo
same problem as previous, can't read the /sdcard /data.
any further support?

zilan said:
i was using your TWRP since kenzo, and mido. nice to see you here on sagit. does it support decryption on oreo? backup and restore works fine?
Click to expand...
Click to collapse
yes it works fine
planetera said:
Does it support Oreo decryption and vendor support?
Can we flash treble images with it?
Click to expand...
Click to collapse
no you can't
dewa5227 said:
@dadi11
sorry, but it seems it doesn't work on MIUI 8.4.5 Global Dev Oreo
same problem as previous, can't read the /sdcard /data.
any further support?
Click to expand...
Click to collapse
please be more descriptive next time.
sagit doesn't have /sdcard. if /data can't be mounted you have to format (not wipe) /data

finally,it get stable,what a good thing

It does not decrypt the files.

ibrahimyuksel said:
It does not decrypt the files.
Click to expand...
Click to collapse
why would it? that's what the encryption is for. format /data to disable encryption and have a full access..

dadi11 said:
please be more descriptive next time.
sagit doesn't have /sdcard. if /data can't be mounted you have to format (not wipe) /data
Click to expand...
Click to collapse
i'm sorry, it seems that it must be formatted to be able to use it.
but another problem is, the recovery doesn't seems to stick after reboot to system. it goes back to the original stock recovery.
i didn't change the option from the default Aggresively replacing stock recovery, it still being checked. yet it goes back to stock recovery after reboot to system.

slitaz said:
finally,it get stable,what a good thing
Click to expand...
Click to collapse
flashlight is still not running,and i can't change some settings

dewa5227 said:
i'm sorry, it seems that it must be formatted to be able to use it.
but another problem is, the recovery doesn't seems to stick after reboot to system. it goes back to the original stock recovery.
i didn't change the option from the default Aggresively replacing stock recovery, it still being checked. yet it goes back to stock recovery after reboot to system.
Click to expand...
Click to collapse
same problem always goes back to stock recovery and when I try flash it with no-verity-opt-encrypt-5.1 my phone softbrick at miui logo after reboot

dewa5227 said:
i'm sorry, it seems that it must be formatted to be able to use it.
but another problem is, the recovery doesn't seems to stick after reboot to system. it goes back to the original stock recovery.
i didn't change the option from the default Aggresively replacing stock recovery, it still being checked. yet it goes back to stock recovery after reboot to system.
Click to expand...
Click to collapse
I solved it, first u need flash twrp then flash magisk or supersu > reboot system > instal apk like root explorer/mixplorer > open root files > find system/bin/install-recovery.sh then rename > system/bin/install-recovery.sh.bak (i used mixplorer) turn off ur phone > press volume up + power button > say goodbye for mi recovery

I am on latest developer global for Mi6. Do I have to wipe everything (my files, settings and apps?) to install this recovery? Can someone give me link to proper installation procedure? I don't want to lose my stuff on phone.

spiderpl said:
I am on latest developer global for Mi6. Do I have to wipe everything (my files, settings and apps?) to install this recovery? Can someone give me link to proper installation procedure? I don't want to lose my stuff on phone.
Click to expand...
Click to collapse
it's not a rom. search for the guide and you will find it for sure

planetera said:
Can you please update this twrp to 3.2.1.1 base? Because it does not support Oreo encryption :/
Click to expand...
Click to collapse
it does. and if it's not then wait for next build

This is what I did:
1. Booted to fastboot
2. fastboot flash recovery recovery.img
3. fastboot boot recovery.img
The red wolf recovery logo appeared and nothing else happened. I had to turn off the phone and when I went back into recovery it was default xiaomi recovery

spiderpl said:
This is what I did:
1. Booted to fastboot
2. fastboot flash recovery recovery.img
3. fastboot boot recovery.img
The red wolf recovery logo appeared and nothing else happened. I had to turn off the phone and when I went back into recovery it was default xiaomi recovery
Click to expand...
Click to collapse
do not use fastboot boot command

{UPDATED}[RECOVERY][UNOFFICIAL]Red Wolf Recovery Project[09/07/2018][enchilada]

{
"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"
}
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Red Wolf Recovery is custom recovery based on TWRP source code however some things are working here slightly different then you might expected. The main objective of this project is to provide stable recovery with features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. This recovery is also first recovery on the world with password protection.
Based on TWRP version: 3.2.2
For device: Enchilada
Features
Translated to EN & CZ
- Password protection
- Flashlight(Currently Broken)
- Built-in latest Magisk, SuperSU & AromaFM
- Support two screenshot GUI actions - Power+VolDown to save screenshot in to the internal storage &
Power+VolUp to save screenshot in to the external storage (Will be automatically saved in to the internal in case
that external storage doesn't exist).
- Support automatic reboot after the restore process
- Recovery can automatically modify some props in the ROM directly during the installation
- Some built-in scripts from community
- Tap to wake support
- Advanced deactivation of the stock recovery
- Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- Support "set on boot" settings.
* Changes for security reasons *
- ADB isn't starting automatically at the start of the recovery. You have to activate it in recovery
- MTP isn't starting until user enter correct password
- Deactivated TWRP theme engine
Some differences
- get out of here if you are pirating apps. this recovery is not for you
- compiled on omnirom-8.1 source
- There isn't bug with reboot from recovery to recovery
Changelog
Code:
Initial Build
Bugs:
1)Flashlight doesnt work (only on recovery)
2)Aroma Installer doesn't work
3)If flashing MTP build, on boot if you enter wrong pattern it causes it to crash wherein you'd need to reboot by long pressing power button.
4) password protection doesn't work.
Fixed:
1) Vibration/Haptic Feedback has been fixed
2) encryption/Decryption now work
Glitches
1) Sometimes mtp doesn't work dircetly when booted into recovery. For MTP to work, once booted into recovery go to mount, and tap on disable mtp and then tap enable mtp.
2) When you select any option in reboot, it redirects to recovery. Do the same again and it will work
(For ex: you tap on reboot>system, it redirects to recovery. then again tap reboot>system it will work)
******************Installation Instructions******************
1)Flashing through a Custom Recovery
- Download the RedWolf-installer-enchilada-3.2.2-0.zip
- Copy the zip to your phone's internal storage
- Flash the zip and you're good to go
2)People who don't have any custom recovery(through fastboot)
- Download both RedWolf-installer-enchilada-3.2.2-0.zip & RedWolf-027-Unofficial-enchilada.img into your pc.
- Copy RedWolf-recovery-installer.zip to the internal storage of your phone.
- In PC go to the dir where you downloaded the RedWolf-027-Unofficial-enchilada.img
-Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and then select Open command window here (or) open powershell here
- Now switch off your phone, connect your phone to pc using the original cable provided.
- Press power button + vol up button to boot into bootloader.
- In thecmd on your pc type :
Code:
fastboot boot RedWolf-027-Unofficial-enchilada.img
- In a few moments your phone will boot into RedWolfRecovery.
- Once booted into recovery immediately press install and locate the redwolfinstaller zip that you copied into your phone and flash it.
- Wait for it to Flash.
- and you've successfully flashed RedWolf-Recovery
DOWNLOADS
RedWolf-Recovery(MTP) for enchilada(OnePlus6)
RedWolf-Recovery(NO-MTP) for enchilada(OnePlus6)
Warning:
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery.
Sources:
DeviceTree
RedWolf
Credits: @dees-Troy && @wuxianlin for their sources
OMNI rom for twrp
RedWolf Team for the RedWolf source
A big thanks to @joemossjr for fixing the issues with recovery not booting
@notsyncing on github for the fixes
@Titokhan for helping me with a and b
me for compiling and testing and fixing Haptic Feedback on RedWolf

So guys the builds and testing are finally done.
As told i have uploaded two builds with mtp and without mtp
Based on twrp 3.2.2 source
Bugs:
1)Flashlight doesnt work (only on recovery)
2)Aroma Installer doesn't work
3)If flashing MTP build, on boot if you enter wrong pattern it causes it to crash wherein you'd need to reboot by long pressing power button.
Fixed:
1) Vibration/Haptic Feedback has been fixed
2) encryption/Decryption now work
Glitches
1) Sometimes mtp doesn't work dircetly when booted into recovery. For MTP to work, once booted into recovery go to mount, and tap on disable mtp and then tap enable mtp.
2) When you select any option in reboot, it redirects to recovery. Do the same again and it will work
(For ex: you tap on reboot>system, it redirects to recovery. then again tap reboot>system it will work)
CREDITS
A big thanks to @joemossjr for fixing the issues with recovery not booting
also thanks to wuxianlin and Dees_Troy for the sources @notsyncing on github for the fixes
The Download links and Instructions will be updated in OP
Dated : 09-07-2018

Is Aroma Installer working?
Regards

Lol I built this a few weeks ago
---------- Post added at 03:08 AM ---------- Previous post was at 02:52 AM ----------
encryption doent work

Only for the One Plus 6? Any plans on expanding to other devices?

Eliminater said:
Is Aroma Installer working?
Regards
Click to expand...
Click to collapse
It should, Not tried though

joemossjr said:
Lol I built this a few weeks ago
---------- Post added at 03:08 AM ---------- Previous post was at 02:52 AM ----------
encryption doent work
Click to expand...
Click to collapse
Damn I didn't notice that.... my bad
Updated for now in OP

jdmst77 said:
Only for the One Plus 6? Any plans on expanding to other devices?
Click to expand...
Click to collapse
That's not dependant on me mate

pranavasri said:
Damn I didn't notice that.... my bad
Updated for now in OP
Click to expand...
Click to collapse
Np it's probably due to the 7.1 branch your using btw why are you using the 7.1 branch again?

joemossjr said:
Np it's probably due to the 7.1 branch your using btw why are you using the 7.1 branch again?
Click to expand...
Click to collapse
their 8.1 sources gave issues while compiling(probably due to device sources, so i went with 7.1 source )

pranavasri said:
their 8.1 sources gave issues while compiling(probably due to device sources, so i went with 7.1 source )
Click to expand...
Click to collapse
Ah. Yeah that's where you messed up what was the errors? I've got about every single one lol plus the 8.1 branch has the proper decryption for us lol

joemossjr said:
Ah. Yeah that's where you messed up what was the errors? I've got about every single one lol plus the 8.1 branch has the proper decryption for us lol
Click to expand...
Click to collapse
Shall i PM

pranavasri said:
Shall i PM
Click to expand...
Click to collapse
I'll do you one better hit me up on Hangouts @ [email protected]

Eliminater said:
Is Aroma Installer working?
Regards
Click to expand...
Click to collapse
No, aroma is not working and even core functionality like decryption of the data partition don't work.

xXx said:
No, aroma is not working and even core functionality like decryption of the data partition don't work.
Click to expand...
Click to collapse
Chill man we will get it working

is DM verity and force encrypt disabled? how'd you achieve this? is it only for installing rom after recovery? (format data) or another way?
can you please explain @pranavasri

virtyx said:
is DM verity and force encrypt disabled? how'd you achieve this? is it only for installing rom after recovery? (format data) or another way?
can you please explain @pranavasri
Click to expand...
Click to collapse
I wouldn't say they are disabled but yes they might not work, (looks like it's because i've used nougat source) i didn't get thelast part of your question

pranavasri said:
I wouldn't say they are disabled but yes they might not work, (looks like it's because i've used nougat source) i didn't get thelast part of your question
Click to expand...
Click to collapse
firstly we need a TWRP with decrypt possible for us to disable encryption
and also the ability to edit the fstab in /vendor partition (/vendor/etc/ there are 2 fstab files we need to edit and remove force encrypt to encryptable)
i have tried this with official twrp and didnt work
i cant seem to mount /vendor as R/W in OS or TWRP my changes dont stick for some reason.

@pranavasri
Thank you for sharing.
I'm gonna give it a try!

pranavasri said:
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Red Wolf Recovery is custom recovery based on TWRP source code however some things are working here slightly different then you might expected. The main objective of this project is to provide stable recovery with features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. This recovery is also first recovery on the world with password protection.
Based on TWRP version: 3.2.1
For device: Enchilada
Features
Translated to EN & CZ
- Password protection
- Flashlight(Currently Broken)
- Built-in latest Magisk, SuperSU & AromaFM
- Support two screenshot GUI actions - Power+VolDown to save screenshot in to the internal storage &
Power+VolUp to save screenshot in to the external storage (Will be automatically saved in to the internal in case
that external storage doesn't exist).
- Support automatic reboot after the restore process
- Recovery can automatically modify some props in the ROM directly during the installation
- Some built-in scripts from community
- Tap to wake support
- Advanced deactivation of the stock recovery
- Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- Support "set on boot" settings.
* Changes for security reasons *
- ADB isn't starting automatically at the start of the recovery. You have to activate it in recovery
- MTP isn't starting until user enter correct password
- Deactivated TWRP theme engine
Some differences
- get out of here if you are pirating apps. this recovery is not for you
- compiled on omnirom-7.1 source
- There isn't bug with reboot from recovery to recovery
Changelog
Code:
Initial Build
Bugs
-Mtp removed (same reason as for the official build)(only in recovery)
-flashlight doesn't work
-encryption doesn't work. thnx to @joemossjr for letting me know
******************Installation Instructions******************
1)Flashing through a Custom Recovery
- Download the RedWolf-recovery-installer.zip
- Copy the zip to your phone's internal storage
- Flash the zip and you're good to go
2)People who don't have any custom recovery(through fastboot)
- Download both RedWolf-recovery-installer.zip & RedWolf-027-Unofficial-enchilada.img into your pc.
- Copy RedWolf-recovery-installer.zip to the internal storage of your phone.
- In PC go to the dir where you downloaded the RedWolf-027-Unofficial-enchilada.img
-Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and then select Open command window here (or) open powershell here
- Now switch off your phone, connect your phone to pc using the original cable provided.
- Press power button + vol up button to boot into bootloader.
- In thecmd on your pc type :
Code:
fastboot boot RedWolf-027-Unofficial-enchilada.img
- In a few moments your phone will boot into RedWolfRecovery.
- Once booted into recovery immediately press install and locate the redwolfinstaller zip that you copied into your phone and flash it.
- Wait for it to Flash.
- and you've successfully flashed RedWolf-Recovery
DOWNLOADS
RedWolf-Recovery for enchilada(OnePlus6)
Warning:
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery.
Sources:
DeviceTree
RedWolf
Credits: @dees-Troy && @wuxianlin for their sources
OMNI rom for twrp
RedWolf Team for the RedWolf source
@Titokhan for helping me with a and b
me for compiling and testing
Click to expand...
Click to collapse
If I don't like or want to revert back to TWRP can I flash TWRP from within red wolf?
---------- Post added at 10:36 PM ---------- Previous post was at 10:31 PM ----------
virtyx said:
firstly we need a TWRP with decrypt possible for us to disable encryption
and also the ability to edit the fstab in /vendor partition (/vendor/etc/ there are 2 fstab files we need to edit and remove force encrypt to encryptable)
i have tried this with official twrp and didnt work
i cant seem to mount /vendor as R/W in OS or TWRP my changes dont stick for some reason.
Click to expand...
Click to collapse
As far as decrypting in TWRP check my post here. https://forum.xda-developers.com/showpost.php?p=76845815&postcount=14
I was able to do it. Here's the whole thread. https://forum.xda-developers.com/oneplus-6/help/soft-brick-restoring-backup-twrp-t3805112

[RECOVERY][FBE]TWRP 3.4.0-0[Onclite][UNOFFICIAL]

{
"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"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Introduction:
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices.It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system which are functions often unsupported by stock recovery images.It is, therefore, often installed when flashing, installing, or rooting Android devices,although it isn't dependent on a device being rooted prior to installation. [Wiki]
Click to expand...
Click to collapse
Changelogs:
What's new in 3.3.1-0:
Code:
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
Build - 02/04/2020
Code:
* Initial Build
What's new in 3.4.0-0:
Code:
* System As Root (SAR)
- Fix backup and restore using SAR - dianlujitao
- System mount point - Chaosmaster
- ORS - Chaosmaster
- Zip install - Chaosmaster
- system_root bind mount to /system - Chaosmaster
- Autodetection of SAR - Chaosmaster
* Digest
- fix creation of digests for sub-partitions (was bugfix applied to many devices since last year) - Bigbiff
* Encryption
- ext4Crypt Wrapped Key Update - Peter Cai
- Fix upgrading encryption key if export fails - Peter Cai
- Fix wrapped key support for devices without metadata partition - mauronofrio
- Don't skip decryption when using block map file in order to write to /data in ORS - CaptainThrowback
- FDE - Decrypt master key first - AndroidableDroid
- vold_decrypt - set Android version and patch level automatically - CaptainThrowback
- Set wrapped decrypt support by twrp flag - Peter Cai
- Don't try wrapped support unless needed - mauronofrio
- restore ext4 policy on /data/cache - Bigbiff
- multiuser decryption - Noah Jacobson
- FDE retry - AndroidableDroid
* TWRP App
- unmount system after checking for app - Bigbiff
* Prebuilt updates -
- android.hardware.confi[email protected] - cryptomilk
* Compilation Fixes:
- TW_EXFAT_FUSE compilation fixes - Bigbiff
- libuuid - cryptomilk
- 'system/etc/ld.config.txt' not found error - Martin Dünkelmann
* Language Updates:
- Portugal - Vasco Machado
- Dutch - Ian Macdonald
- Turkish - Fatih Fırıncı
- Localisation of Backup_Tar: Ian Macdonald
* ld.config.txt
- updates for 8.x trees - CaptainThrowback
- fix search path for /sbin - CaptainThrowback
- /sbin should come first in search path - Ian Macdonald
* General Bugs
- Fix persistent log storage - SyberHexen
- Compress Persistent Logs - Bigbiff
- FB2PNG compilation errors - Bigbiff
- exclude per_boot from backups - Darth9
- Unmount all directories that point to same block device - AndroidableDroid
- Blank screen fixes - Sean hoyt
- Toolbox is default on android-9+ - mauronofrio
* Cleanup -
- Typo fix in comment - VDavid003
- newlines in ext4crypt - CaptainThrowback
- TW_OEM_BUILD compilation issue - Patrick Zacharias
- Fix Dependency requirements - Dees_Troy
- Fix Symbolic links for BB and Toolbox - Dees_Troy
* Bootloader Message
- cleanup - Alessandro Astone
- add configurable offsets
* Error Cleanup
- uevent errors and decryption error - mauronofrio
- using copy_file to copy files from /etc - CaptainThrowback
- ueventd access to /acct - early directory creation in init - cryptomilk
* Haptics
- TSP Driver - LameMonster82
- QTI Input - AndroidableDroid
* update_engine
- read all asserts - Hernán Castañón
* Resetprop
- Add Resetprop from Magisk - CaptainThrowback & mauronofrio
- compile from source - Chaosmaster
- fix for android-7 and earlier - Chaosmaster
- cleanup for spaces in properties - AndroidableDroid
* Properties
- Add Property override - Chaosmaster
* Backuptool
- mount system and vendor for A/B installs for backuptool - Chaosmaster
* twrpTar
- fix backup freezes when pigz and openaes are used - Fabrice Bellet
* Zip Installs
- Info for A/B zip installing to inactive slot - Chaosmaster
- Reboot to system button now allows to be rebooted to different partitions after zip install
- progressbar rework - Chaosmaster
* Magisk updates
- update binaries from source - AndroidableDroid
* A/B Updater Zip Template
- rewrite A/B installer zip from scratch using a new generic template and latest magiskboot - osm0sis
- installer zip support for recovery_a/recovery_b partition ramdisks on newer 2SI SAR A/B devices - osm0sis
- generate installer zips for all prod A/B devices - bigbiff
- improve installer zip dump/write speed and add more error catching - arter97 & osm0sis
* OZIP Encryption Support
- add OZIP encryption - mauronofrio
* File Selector
- Support for more extensions in File Selector - mauronofrio
Build - 20/08/2020
Code:
* TWRP-3.4.0-0 release
* Fixed CPU temperature
Click to expand...
Click to collapse
Important Notes:
* This recovery supports only File-based Encryption.
* Use this recovery only for Custom Roms with File-Based Encryption support.Ask your ROM maintainer for more info
* As our MIUI stock rom uses Full-Disk Encryption,this recovery don't support that
Click to expand...
Click to collapse
Bugs:
* You tell me if you find anything
Click to expand...
Click to collapse
Download Link:
TWRP-3.3.1-0 : Gdrive[zip]
TWRP-3.4.0-0 : Gdrive[zip]
Installation:
* Download and extract the zip file provided above
* Rename the extracted img file to recovery.img
* Method 1: Flash through fastboot mode
Code:
fastboot flash recovery recovery.img
* Method 2: Use any other custom recovery to flash the recovery img
Click to expand...
Click to collapse
Sources:
* TWRP source
* Device Source
Click to expand...
Click to collapse
Support:
* If you like my work, don't forget to hit thanks button.:good:
*Buy me a packet of biscuit, PayPal
Click to expand...
Click to collapse
XDA:DevDB Information
TWRP with FBE for Redmi 7, Tool/Utility for the Xiaomi Redmi 7
Contributors
Dhina_17
Version Information
Status: Stable
Stable Release Date: 2020-04-02
Created 2020-04-02
Last Updated 2020-08-19

Reserved

pro

Wahoo! Keep up the great work, bro!

Fantastic! Thanks..
Question: It will be added supported rom list later? Thank you very much
Odesláno z mého Redmi 7 pomocí Tapatalk

Its great to see this development but the older unofficial version works batter. After installing latest aosp fbe rom with this latest recovery when i tap reboot to system it reboots to recovery. Installed fbe rom that said install with this version of recovery but after trying again and again it boots back to recovery. Used latest orangfox recovery based on this build but it got stucked in recovery logo. Flashed this recovery again from fastboot and now this recovery to stucked at logo. Tried to install older unofficial twrp from fastboot and it workes. Installed fbe rom that said install with latest but installed with older twrp and its working. Everytime Whenever i download an updated recovery from this official post it works worst then the unofficial build. The unofficial build is more stable no problem at all. Now using the TWRP-3.3.2B-0317-REDMI7-CN-wzsx150.img.

Mes shahadat said:
Its great to see this development but the older unofficial version works batter. After installing latest aosp fbe rom with this latest recovery when i tap reboot to system it reboots to recovery. Installed fbe rom that said install with this version of recovery but after trying again and again it boots back to recovery. Used latest orangfox recovery based on this build but it got stucked in recovery logo. Flashed this recovery again from fastboot and now this recovery to stucked at logo. Tried to install older unofficial twrp from fastboot and it workes. Installed fbe rom that said install with latest but installed with older twrp and its working. Everytime Whenever i download an updated recovery from this official post it works worst then the unofficial build. The unofficial build is more stable no problem at all. Now using the TWRP-3.3.2B-0317-REDMI7-CN-wzsx150.img.
Click to expand...
Click to collapse
I think you are in wrong thread.. its not official twrp thread.. go to that. Thanks

TWRP-3.4.0-0 is up

Works better than official build of TWRP.

@Dhina_17
Just reporting a minor bug:
The status bar position is too low (there is a noticeable gap/padding between the notch and the top border of the status bar).

I have a problem, please help me. After installed the 3.4.0.0. image, the phone always forget my pin/pattern/password. If I reboot in recovery mode and delete all of the *.key and lockprint.* files the phone works without any pin/pattern/password until I set a new one. But when I set a new pin/pattern/password and turn off the screen, after I try unlock my screen, it always said the pin/pattern/password is wrong, and can't unlock my screen. Only if I reboot it again in recovery mode and delet the files. But in this case I don't have any screen lock security. The other problem is the fingerprint sensor is not working after installed twrp 3.4.0.0. What can I do?

sbalika0ó1983 said:
I have a problem, please help me. After installed the 3.4.0.0. image, the phone always forget my pin/pattern/password. If I reboot in recovery mode and delete all of the *.key and lockprint.* files the phone works without any pin/pattern/password until I set a new one. But when I set a new pin/pattern/password and turn off the screen, after I try unlock my screen, it always said the pin/pattern/password is wrong, and can't unlock my screen. Only if I reboot it again in recovery mode and delet the files. But in this case I don't have any screen lock security. The other problem is the fingerprint sensor is not working after installed twrp 3.4.0.0. What can I do?
Click to expand...
Click to collapse
I've only experienced that in the official version of TWRP that's why I stopped using that.

@Dhina_17 Works great! Any plans to add /data decryption support?

[RECOVERY][RMX2061][Unofficial]TeamWin Recovery Project [3.5.X]

TeamWin Recovery Project
{
"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"
}
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.​
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
TWRP is FREE SOFTWARE​Two versions: for RUI1 (Android 10) and for RUI2 (Android 11)
Features:
• Fastbootd is working;
• Decryption is working
• Using custom themes and fonts (special thanks to [email protected])
• Added custom patches in the Advanced settings (special thanks to [email protected]):
- SafetyNet fix patch
- Google Pay fix patch
- Patch for mount System and Vendor as r/w
• AVB2.0 (vbmeta) disabling special (thanks to [email protected] for his patch)
• Fix stock .ozip installation
• Patch to conversion of dynamic partitions to r/w (special thanks to @lebigmac for his script. Original thead)
• Patch to fix Magisk on RUI2
Download:
From Google Drive https://drive.google.com/drive/folders/1xerR8NmCNEoR1afh4dfbyrLz0ZOuWZPp?usp=sharing
Spoiler: Screenshots
Spoiler: Guides
Spoiler: Convert any ROM to r/w
How to convert ROM to R/W
The process below describes how to transfer the entire firmware to R/W (the ability to change/delete/add files in the system partitions: system, vendor and others ..).
All actions are carried out in TWRP itself i.e. on "live".
Your data is not affected.
Required for a successful conversion:
* free space on the internal memory of at least 25GB.
* charged battery (preferably at least 40%)
The process itself is not complicated:
1. Make
backup a Super partition (optional)
2. Go to the "Advanced" section and select "Convert ROM to RW".
3. In the next window, confirm with a swipe.
4. That's it, we are waiting ... about 5 minutes ...
5. After all the actions, the device will reboot itself into the system ...
6. Go to the explorer with root rights and delete the /data/local/tmp/makesysrw_[version] (/data/media/makesysrw_[version] for Android 11) folder, or do it in the TWRP explorer
To access the system partitions, respectively, you need root rights and a file manager with the ability to mount partitions in r/w.
The test was conducted on RealmeUI 1 A.45 and RealmeUI 2 C.15. But there is no difference, it is possible to convert any Android 10-11 ROM to r/w.
Changelog - current version (Android 11):
• Fixed decryption /data on realmeUI 2.0 (all versions)
• Enabled some patches in the Advanced section
• Updated Magisk and some patches
• Edits in the TWRP interface by @brigudav
• Removed the code that could break the formatting /data
• Updated sources
• And other changes that I forgot...
INSTALLATION
via TWRP-based recovery:
Download the TWRP IMG file to your device
Reboot to your custom TWRP-based recovery
Install the TWRP img file as image in recovery partition
Reboot into recovery after installation
Enjoy!
via fastboot:
Download the TWRP IMG file to your PC
Reboot your device to fastboot mode
Install the TWRP image with command:
Code:
fastboot flash recovery [image name].img
Reboot to recovery with the command:
Code:
fastboot reboot recovery
Enjoy
Notes:
• Installation of OTA packages not working
• ADB doesn't work in fastbootd mode only
CREDITS
• TeamWin - for TWRP
• brigudav - for his TWRP customization
• @lebigmac - for his makeSystemRW script
Version Information
Status: Stable
Current version: 3.5.2_10-1 (Android 10) / 3.5.2_1011-3 (Android 11)
Created 2021-03-18
Last Updated - 2021-09-03

CHANGELOGS
Spoiler: Android 11
Spoiler: 2021-09-03 (3.5.2_1011-3)
• Fixed decryption /data on realmeUI 2.0 (all versions)
• Enabled some patches in the Advanced section
• Updated Magisk and some patches
• Edits in the TWRP interface by @brigudav
• Removed the code that could break the formatting /data
• Updated sources
• And other changes that I forgot...
Spoiler: 2021-05-03 (3.5.2_1011-2)
• Fixed the installation of some ROMs
• Fixed fastboot (it was broken in the last build)
Spoiler: 2021-05-01 (3.5.2_1011-1)
• Disabled non-working patches in the Advanced section
• Enabled the install/remove Magisk feature in the Advanced section
• Added a boot repackaging patch with an oplus.fstab fix for Magisk (now after applying this patch, Magisk booted correctly on RUI 2)
• A small fix under the hood
Spoiler: 2021-04-29 (3.5.2_1011-0)
• Initial build
Spoiler: Android 10
Spoiler: 2021-04-23 (3.5.2_10-1)
• Universal patch disabling vbmeta by [email protected] (thanks to him for the patch)
• Now the internal storage after formatting /data is available without rebooting
• Minor changes in device tree (some libs are now taken from sources, small changes in the fstab, unnecessary system.props and flags are removed, edits in translation)
• Updated and fixed the script for converting firmware to R/W (now temporary files are deleted automatically when the conversion is successful)
• Added logcat copying
• Updated magisk to Canary 22104 (21) in which the SafetyNet check works correctly.
• Languages: Added Indonesian language [android_bootable_recovery]
• Change the missing logical partitions from LOGERR to LOGINFO [android_bootable_recovery]
Spoiler: 2021-04-05 (3.5.2_10-0)
• The list of Firmware-Update partitions for backup is finally changed (It is recommended to delete old "Firmware" backups and make new ones #2)
• Fix a regression error for digest checking [android_bootable_recovery]
Spoiler: 2021-03-30 (3.5.1_10-1)
• Added conversion of dynamic partitions to r/w (see Guides). Special thanks to @lebigmac for his script. Original script thead
• In the Mounting settings you can now mount System and Vendor r/o and r/w (if the partitions are in r/w). Taken fromTWRP by brigudav for Poco X3
• Returned the reboot menu from TWRP 3.3.x. Taken from TWRP by brigudav for Poco X3
• Changed the list of partitions for Modem backup. It is recommended to delete old backups and make new ones
• Changes in languages
• Other changes under the hood
Spoiler: 2021-03-18 (3.5.1_10-0)
• Initial version

Reserved

Can i use this recovery for Flash Android 11 custom roms?

Ayushmak said:
Can i use this recovery for Flash Android 11 custom roms?
Click to expand...
Click to collapse
Yes, if you already have installed the RUI1 or ROM's based on RUI1.
You cannot boot the TWRP if you on RUI2 or ROM based on RUI2

Somebody knows on which RUI is based RR from this thread? There is only "Based on: AOSP". So can I install this twrp or not?
[ROM][10.0] Resurrection Remix v8.6.3 [RMX206X, UNOFFICIAL]
Please Give Update A11 based RROS...
forum.xda-developers.com

Yes you can install it... 'cause i would try.. on RR rom

Zgadnijcie said:
Somebody knows on which RUI is based RR from this thread? There is only "Based on: AOSP". So can I install this twrp or not?
[ROM][10.0] Resurrection Remix v8.6.3 [RMX206X, UNOFFICIAL]
Please Give Update A11 based RROS...
forum.xda-developers.com
Click to expand...
Click to collapse
All Android 10 Custom ROMs based on RUI1. Yes, you can install TWRP

Good job Ctarchik!
If anyone is looking for more information about my make system RW script here is the official project thread

lebigmac said:
Good job Ctarchik!
If anyone is looking for more information about my make system RW script here is the
Click to expand...
Click to collapse
Hi, I took this patch from TWRP by brigudav. I didn't find any mention of the creators anywhere other than brigudav, just "Make System to RW for Poco X3". I am always for the preservation of copyright and always indicate the developers of the program. I apologize to you for not finding your original official project thread. I would like to use your script for my recovery, of course, with the condition of saving the author and specifying a link to the original post...

Ctarchik please feel free to use latest version of my script in your project. The more people have system r/w access the better for the open source community.
@brigudav rather than hacking my update-binary and replacing my program's title (!!!) with your own meaningless words and torturing my script's comments section by modifying and removing the original script name, original author name, original version, link to original project homepage, disclaimer, credits, manual and automatic installation instructions, usage examples, (and much more...) I would suggest to try to improve the underlying algorithm of the script itself. And NO that does NOT mean simply renaming my variables and my functions and changing their order as well as injecting your bogus useless function that does absolutely nothing (...)
Please don't be such a lazy ruthless hacker without any morals or respect! Thank you! You have been caught red handed as a cyber thief and now the only right thing to do is to admit your guilt, beg for pardon and STOP IT! Please stop stealing my work and releasing as your own okay? That's just very very wrong on so many levels!
I clearly stated in my disclaimer that by using my script you agree to not abuse my work for criminal illegal purposes. And what you're doing is a perfect example of copyright infringement as well as intellectual property theft which is illegal even in Russia. Don't forget that!

Can you mod this twrp so I can use external sdcard to backup?
Thank you!
Super Partition backup fails when using FAT32 stick (exFAT works) · Issue #143 · TeamWin/android_bootable_recovery
I am running an official build of TWRP, downloaded from https://twrp.me/Devices/ I am running the latest version of TWRP I have read the FAQ (https://twrp.me/FAQ/) I have searched for my issue and ...
github.com

Ctarchik said:
Yes, if you already have installed the RUI1 or ROM's based on RUI1.
You cannot boot the TWRP if you on RUI2 or ROM based on RUI2
Click to expand...
Click to collapse
I had to google to know what RUI1 and RUI2 meant - RUI1 is Realme UI 1.0 which is based on Android 10 - RUI2 is Realme UI 2.0 based on Android 11

beaker2 said:
I had to google to know what RUI1 and RUI2 meant - RUI1 is Realme UI 1.0 which is based on Android 10 - RUI2 is Realme UI 2.0 based on Android 11
Click to expand...
Click to collapse
Yes, it is. I just shortened RealmeUI to RUI

The problem I have been having is when I previously installed TWRP on my phone using ADB to install- patched_vbmeta-2 and then TWRP. I could reboot from ADB into recovery to TWRP, but then when I tried to reboot into system I was in a boot loop and phone would only go back to the stock recovery . Then I had to re flash the stock rom to get out of the boot loop and be able to boot into system again.
So can I do the same install from ADB as before but when I reboot , from ADB, into TWRP then I can install this TWRP then I can have the ability to boot into the stock ROM system . Then I could go to recovery and TWRP will still be there so that I could install a custom ROM ?
Thanks in advance, I'm a noob with this phone and its partitioning

Well, I tried the installation described above, installed TWRP from ADB then when booted and rebooted into TWRP and flashed this version of TWRP, seemed fine no errors BUT... the phone just returned to the stock recovery .
Then I tried exactly as described in this thread no error message and all seemed to go smoothly BUT... The phones internal memory was unreachable from any file manager or computer and the stock recovery returned not TWRP. Had to re-flash the phone several times, 1. stock recovery 2.from update 3.from flash tool, to finally get the internal phone memory visible again.
My phones build number is RMX2061_11_A49. Has anyone successfully installed TWRP on this build ?
How?

1. Prevent replacing TWRP:
Flash this file in Advanced Menu in the first time you go in TWRP.
2. Decrypt userdata: do them in order
- Flash this file:
Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip | by Droidwin for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
- Wipe / Format Data / yes
- Reboot to TWRP again
- Advanced / Fix AVB
- Reboot to System
Done!
P.S.: You will lost all data after this.

No, that didn't work. Kept getting -twrp error 1- when flashing the Disable dm verity forceencrypt file.
Tried several times.
Tried reinstalling the stock boot.img then installing same error 1
Tried reinstalling the stock rom installing twrp then flashing disable varity same error 1
Tried ignoring the error and going to fix AVB still no luck
Everything I tried it still just returned to the stock recovery

beaker2 said:
No, that didn't work. Kept getting -twrp error 1- when flashing the Disable dm verity forceencrypt file.
Tried several times.
Tried reinstalling the stock boot.img then installing same error 1
Tried reinstalling the stock rom installing twrp then flashing disable varity same error 1
Tried ignoring the error and going to fix AVB still no luck
Everything I tried it still just returned to the stock recovery
Click to expand...
Click to collapse
Try flash magisk before reboot system

nttuan said:
Try flash magisk before reboot system
Click to expand...
Click to collapse
I gave up and installed Magisk 23 and rooted. I just decided to live with the stock rom (debloated) and the stock recovery