[RECOVERY][OFFICIAL][Kenzo/Kate][TREBLE][V3.2.1-028-Beta] Red Wolf Recovery Project - Xiaomi Redmi Note 3 [Snapdragon] ROMs, Kernels, Re

{
"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.

Related

[DEV][WIP] TWRP 2.4.4.0 - recovery

TeamWinRecoveryProject​
Changelogs from last Release from Shaaan to mine​
Code:
[B]2.4.4.0[/B]
* Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
* More fixes for the file selector
* Switched from using busybox md5sum to a direct C function call
* Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
* Update exFAT to latest commits
* Added a build flag to disable using the ioctl for screen blanking
[B]2.4.3.0[/B]
* Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
* Added a scroll bar to file selectors and listboxes courtesy of Tassadar
* Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
* Added a screen dim effect 2 seconds before screen off on some devices
* Finally fixed file selector crash (one of the joys of working with multi-threaded software)
* Fixed loading of screen timeout setting during startup
* Improvements and bugfixes to screen timeout code
* Fixed persistence of the 24 hour / military time setting
[B]2.4.2.0[/B]
* Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
* Add a brightness setting (requires device specific setup and only some devices have been added)
* Add a root checker and offer to install SuperSU if the device isn't already rooted
* Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
* Check and offer to fix root permissions if broken
* Add an option for a 24 hour clock display instead of AM/PM (aka military time)
* Move stock recovery reflash check to occur during the reboot cycle
* Add support for some MTK6xxx devices
* Change libtar to vfork to help prevent memory problems
* Add a "clicked" effect to most buttons, file selector, and listbox
* Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
* Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
* Other minor bugfixes and improvements
[B]2.4.1.0:[/B]
* Fixed a problem with mkdosfs that formatted sdcards to 2GB
* Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
* Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
* Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
[B]2.4.0.0:[/B]
* Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
* Support for exFAT formatted sdcards (also thanks to bigbiff)
* Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
* Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
* Added wipe cache and dalvik after ADB Sideload
* Replaced many system calls with their native C counterparts
* Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
* Fixed AOSP recovery commands to run after decryption on encrypted devices
* Improvements for building TWRP in CM10.1
* Other minor bugfixes and improvements
[B]2.3.3.0:[/B]
* Fix renaming backups with a space in the name
* Add decrypt button to mount page if you cancel decryption during startup
* Added ignore blkid flag
* Fixed handling of MTD partitions during mount
* Fixed some keyboard mapping issues on 800x1280 layout
[B]2.3.2.0:[/B]
* Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)
* Fixed a bug with deleting a backup with a space in the name
* Added highlights on keyboard key presses
[B]2.3.1.0:[/B]
* Unmount system after boot to prevent some status 7 symlink failed errors on zip install
* USB Mass Storage code improvements
* Better handling of mounting storage during boot for some devices
* Fixed a problem with sizes of images (boot & recovery) after resetting defaults
* Fixed size errors during backup for some devices on recovery, etc.
* Fixed a problem with restoring backups when multiple archives were present
[B]2.3.0.0:[/B]
* Rebased onto AOSP Jelly Bean source code
* Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
* ADB sideload functionality from AOSP is included in 2.3, see this link for more info
* Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
* Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
* Faster boot times
* Added charging indicator while in recovery (only updates once every 60 seconds)
Issues​
Code:
* Maybe your USB in recovery will be broken (so no mount storage to pc)
!!!It can happen that you brick your Device any other time, but this time NOT, when you flash this!!!
Downloads (My version)​
Code:
[URL="http://tinyw.in/clY8"]twrp_2.4.4.0-cooper.zip[/URL]
[B]MD5-Sum:[/B] b812c764b80b2db2d6ae53dc4eb0f9de
Your will look like that if i done all right:
{
"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:
[B]CREDITS:[/B]
* Dees_Troy and other devs for helping me
* original recovery from TWRP team (thx all)
* shaaan for recovery kernel
Wow man You rocks.... Hope we can get stable soon.... BTW any plan to make another version of CMX as it is full of bug
Why version 2.2.0 on screenshots?
Nice, finally Galaxy Ace has 2 custom recovery
Flashed it. Stuck on teamwin splash screen.
AW: [dev][recovery] twrp 2.4.1.0
yash295 said:
Flashed it. Stuck on teamwin splash screen.
Click to expand...
Click to collapse
good to know thanks man, i`ll look later into it, im away from home now
Sent from my GT-P1000 using xda app-developers app
Its fine man.. you are doing so much hard work for ace, least we can do is test things for you. keep it up.
OldDroid said:
good to know thanks man, i`ll look later into it, im away from home now
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
same heree
Re: [dev][recovery] twrp 2.4.1.0
So you fixed the mount errors?
Sent from my GT-I9070 using xda premium
AW: [dev][recovery] twrp 2.4.1.0
no shaaan it goes more deep into the complete recovery as i thought, now im debugging it with bigbiff from twrp team
Sent from my GT-P1000 using xda app-developers app
Re: [dev][recovery] twrp 2.4.1.0
Been looking forward to twrp for a while. Thanks for tackling it.
Sent from my GT-S5830i using xda app-developers app
Re: [dev][recovery] twrp 2.4.1.0
OldDroid said:
no shaaan it goes more deep into the complete recovery as i thought, now im debugging it with bigbiff from twrp team
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Yeah. Also Dees is making some rapid changes to the source to introduce new features.
I worked with him to add basic bml support. Now the recovery atleast recognizes the partitions!
Sent from my GT-I9070 using xda premium
Re: [dev][recovery] twrp 2.4.1.0
OldDroid said:
Code:
* Based on CM10 Code (Next Release or Build will be on CM10.1 Code)
* Maybe you land into a Bluescreen
(you can still boot into Download-Mode so you still can flash another Recovery ;)
Its not a [for me its still easy to fix, but you Wont brick your Device!)
Click to expand...
Click to collapse
Man wtf was the point of posting this. It don't work. I get blue screen. Seriously dude u need to let people know it don't work. Not "maybe you land on blue screen". U should change your wording to "will turn phone into blue flashlight"
I'm still working join fixing this.... Using Odin but it don't seem to be working. I have all the correct files for cwm install via Odin. Soi far its been running for 10 min.
Sent from my Nexus 7 using XDA Premium HD app​
ronedogg said:
Man wtf was the point of posting this. It don't work. I get blue screen. Seriously dude u need to let people know it don't work. Not "maybe you land on blue screen". U should change your wording to "will turn phone into blue flashlight"
I'm still working join fixing this.... Using Odin but it don't seem to be working. I have all the correct files for cwm install via Odin. Soi far its been running for 10 min.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
blue screen or twrp screen, no one reported before that you land on a blue screen, twrp screen is still possible because of wrong loaded bml partitions :silly:
ronedogg said:
Man wtf was the point of posting this. It don't work. I get blue screen. Seriously dude u need to let people know it don't work. Not "maybe you land on blue screen". U should change your wording to "will turn phone into blue flashlight"
I'm still working join fixing this.... Using Odin but it don't seem to be working. I have all the correct files for cwm install via Odin. Soi far its been running for 10 min.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Dont came here acting like this !!
U know that tere's risks is this wip projects ... and this dev is working on a top recovery for an almost ancient ace so bare some respects!
i can see that you're ace had problems but keep calm re-download odin files and just put phone in download mode and flashem well
the only hard brick known to ace i rom manager wich screws the partition's of it! If u can enter download mode you're ace is not bricked! keep trying if u need any help just pm me and i'll be glad to help
take care
Re: [dev][recovery] twrp 2.4.1.0
OldDroid said:
blue screen or twrp screen, no one reported before that you land on a blue screen, twrp screen is still possible because of wrong loaded bml partitions :silly:
Click to expand...
Click to collapse
LoL i wasn't being rude if i came across that way. I got cwm back now.
So what was my issue then. How can i use twrp. What else do i have to do. Just flash the zip with cwm, then what?
Sent from my Nexus 7 using XDA Premium HD app
AW: [dev][recovery] twrp 2.4.1.0
Any progress or isnt it possible to run twrp 2.4.x on our Aces?
Sent from my GT-S5830 using xda app-developers app
Re: [dev][recovery] twrp 2.4.1.0
OldDroid said:
TeamWinRecoveryProject​
Changelogs from last Release from Shaaan to mine​
Code:
[B]2.4.1.0:[/B]
* Fixed a problem with mkdosfs that formatted sdcards to 2GB
* Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
* Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
* Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
[B]2.4.0.0:[/B]
* Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
* Support for exFAT formatted sdcards (also thanks to bigbiff)
* Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
* Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
* Added wipe cache and dalvik after ADB Sideload
* Replaced many system calls with their native C counterparts
* Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
* Fixed AOSP recovery commands to run after decryption on encrypted devices
* Improvements for building TWRP in CM10.1
* Other minor bugfixes and improvements
[B]2.3.3.0:[/B]
* Fix renaming backups with a space in the name
* Add decrypt button to mount page if you cancel decryption during startup
* Added ignore blkid flag
* Fixed handling of MTD partitions during mount
* Fixed some keyboard mapping issues on 800x1280 layout
[B]2.3.2.0:[/B]
* Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)
* Fixed a bug with deleting a backup with a space in the name
* Added highlights on keyboard key presses
[B]2.3.1.0:[/B]
* Unmount system after boot to prevent some status 7 symlink failed errors on zip install
* USB Mass Storage code improvements
* Better handling of mounting storage during boot for some devices
* Fixed a problem with sizes of images (boot & recovery) after resetting defaults
* Fixed size errors during backup for some devices on recovery, etc.
* Fixed a problem with restoring backups when multiple archives were present
[B]2.3.0.0:[/B]
* Rebased onto AOSP Jelly Bean source code
* Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
* ADB sideload functionality from AOSP is included in 2.3, see this link for more info
* Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
* Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
* Faster boot times
* Added charging indicator while in recovery (only updates once every 60 seconds)
Current State​
Code:
* Based on CM10 Code (Next Release or Build will be on CM10.1 Code)
* Maybe you land into a Bluescreen
(you can still boot into Download-Mode so you still can flash another Recovery ;)
Its not a [for me its still easy to fix, but you Wont brick your Device!)
!!!It can happen that you brick your Device any other time, but this time NOT, when you flash this!!!
TWRP-2.4.1.0-cooper.zip
MD5-Sum: None
Your will look like that if i done all right:
Click to expand...
Click to collapse
Your source?
I do not respond to tech support via PM
AW: [dev][recovery] twrp 2.4.1.0
Shaaan said:
Your source?
I do not respond to tech support via PM
Click to expand...
Click to collapse
locally, added the reboot hack + bml partition layout to preserve a bricl
Sent from my GT-S5660 using xda app-developers app
Re: [dev][recovery] twrp 2.4.1.0
OldDroid said:
locally, added the reboot hack + bml partition layout to preserve a bricl
Sent from my GT-S5660 using xda app-developers app
Click to expand...
Click to collapse
So basically you haven't fixed anything?
I do not respond to tech support via PM

[ABANDONED][CAPRICORN] 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: Capricorn
Authors build: yshalsager
Developers: @ATG Droid & @Dadi11
Thanks: z31s1g (for the base of his theme), Ray Li (For his useful advice in the beginnings), osm0sis (for his image scripts), etc.
Features:
Code:
[B]Translated to EN & 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 TWRP theme engine
[/URL]
Some differences to the official version:
Code:
[COLOR="red"]- get out of here if you are pirating apps. this recovery is not for you[/COLOR]
- 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:
RedWolf-V3.2_026
- 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.
RedWolf-V3.2_025
- 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
RedWolf-V3.2_024
- 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.
RedWolf-V3.2_023
- 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
RedWolf-V3.1_022
- 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
RedWolf-V3.1_021
- 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
RedWolf-V3.1_020
- Fixed flashing of the images in the previous 018 build
- Added back support for unpacking of the LZ4 compressed ramdisk
- Fixed bookmark feature
RedWolf-V3.1_019
- 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...
RedWolf-V3.1_018
- 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
RedWolf-V3.1_017
- 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.
RedWolf-V3.1_016
- 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
RedWolf-V3.1_015
- Updated with the latest TWRP changes
- Added flashlight switch on mido
RedWolf-V3.1_014
- 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
RedWolf-V3.1_013
- 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
RedWolf-V3.1_012
- added F2FS support for mido
- added Night Mode (kcal) support for mido
RedWolf-V3.1_011
- 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!
Known Bugs:
- Flashlight is not working.
Downloads:
Latest build for Xiaomi Mi 5s (Capricorn)
RedWolf-026-capricorn.img
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
[ABANDONED][CAPRICORN] Red Wolf Recovery Project, Tool/Utility for the Xiaomi Mi 5s
Contributors
yshalsager, ATG Droid, Dadi11
Source Code: https://github.com/RedWolfRecovery
Version Information
Status: Testing
Created 2018-02-21
Last Updated 2018-02-24
Sources
Recovery: https://github.com/RedWolfRecovery/rw_recovery
Device tree: https://github.com/RedWolfRecovery-Xiaomi-Devices/android_device_xiaomi_capricorn
Screenshots: Here
Not Booting...
When I try to boot in recovery, my phone is restarting or remain on black screen....
JustAimz said:
When I try to boot in recovery, my phone is restarting or remain on black screen....
Click to expand...
Click to collapse
Same here
is it based on twrp 3.2.1-1?
It wont booting up same as others
Sounds promising
Black screen when booting to recovery....feels like screen is on but absolutley black....
jpg3927 said:
is it based on twrp 3.2.1-1?
Click to expand...
Click to collapse
Yes, Official trees
James Blode said:
Black screen when booting to recovery....feels like screen is on but absolutley black....
Click to expand...
Click to collapse
New build:
Please test
https://www.androidfilehost.com/?fid=962187416754462280
yshalsager said:
New build:
Please test
https://www.androidfilehost.com/?fid=962187416754462280
Click to expand...
Click to collapse
Tested it just minute ago....and....phone is rebooting to system....without any logo or black screen....just rebooting.....idk....maybe doing something not right....but flashing it in twrp official 3.2.1.1 like recovery....like always ....mi5s 3/64....with MIUIPRO....stock kernel....and magisk....now am going to flash some aosp rom with official twrp...and test with it....
James Blode said:
Tested it just minute ago....and....phone is rebooting to system....without any logo or black screen....just rebooting.....idk....maybe doing something not right....but flashing it in twrp official 3.2.1.1 like recovery....like always ....mi5s 3/64....with MIUIPRO....stock kernel....and magisk....now am going to flash some aosp rom with official twrp...and test with it....
Click to expand...
Click to collapse
Thanks for test.
No need to re-test, It can't be related to rom
@James Blode
The last build
Based on cofface tree
https://www.androidfilehost.com/?fid=746010030569955683
yshalsager said:
@James Blode
The last build
Based on cofface tree
https://www.androidfilehost.com/?fid=746010030569955683
Click to expand...
Click to collapse
In miui that too not working....but anyway....now im trying it on the oreo RR 6.0.0 Unofficial....maybe there it works?....thank you by the way for hard work....this is really cool twrp modification project...
yshalsager said:
@James Blode
The last build
Based on cofface tree
https://www.androidfilehost.com/?fid=746010030569955683
Click to expand...
Click to collapse
I confirm the reboot into the system, your recovery does not work.
@James Blode
Final Build
https://www.androidfilehost.com/?fid=962187416754462557
Thanks for all your effort, dear dev. The final build does not seem to work for me, though. After the redwolf splash screen the screen goes dark and I'm thrown back to the system booting. My device is a capricorn 3/64.
Okay, even I don't have a device to test, I got many requests to make this recovery and I did, but unfortunately, It can't boot well!
Basically, It MUST work as I used TWRP official trees. But It seems like there's something wrong.
So, this project is ABANDONED now.
Sources are in [URL="https://forum.xda-developers.com/showpost.php?p=75649176&postcount=2]this post[/URL] if anyone decided to continue
Thread Closed!

{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?

[UNOFFICIAL][RECOVERY][Rolex/Riva] OrangeFox Recovery Project [12/06/22] [R11.1_1][FDE+FBE]

{
"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"
}
OrangeFox 11.1(1) UNOFFICIAL
———————————————————————
Based on: TWRP 3.6.2 (Android 11) | Author: iusmac | Kernel: 4.9.309​
Summary:
Code:
Decrypt any Android and any encryption method (FDE or FBE) + Original features
*** DISCLAIMER ***
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.
Installation:
Spoiler
Using recovery:
Spoiler
1. Download the OrangeFox .zip file to your device
2. Boot into to an existing recovery
3. Install OrangeFox .zip file
4. The recovery should reboot automatically into OrangeFox
5. Enjoy!
Using Fastboot:
Spoiler
1. Download the OrangeFox .zip archive to your device and .img image to your PC
2. Connect your device to PC and enter into Fastboot Mode
3. Flash .img using the following commands:
Code:
fastboot erase recovery
fastboot flash {put-here-orangefox-recovery-file-name}.img
fastboot boot {put-here-orangefox-recovery-file-name}.img
4. After the last command your device should boot into OrangeFox
5. Install OrangeFox .zip archive
6. The recovery should reboot automatically
7. Enjoy!
Stock Features:
Spoiler
* Supports Treble and non-Treble ROMs
* Updated with latest TWRP commits
* Built-in support for installing init.d functionality
* Built-in support for installing Magisk
* Password protection
* Torch and LED
* Support for custom ROMs
* Better language support
* Optimized versions of community scripts
* Fox theme engine allows to set: custom scheme/theme (black, dark, etc)
* Gesture navigation
* Backup OrangeFox settings to internal storage or SD card
* And many more!
New Features (added by author):
Spoiler
Spoiler: 1. FBE Encryption Toggler (FBE = File-Based Encryption)
Spoiler: How to Enable/Disable FBE Encryption
* Make sure that the "Enable FBE" button has changed to "Disable FBE" (or vice versa if disabling)
How it works:
Formatting is needed to erase all traces of full disk encryption (FDE) + we need a completely new file system (recovery will take care of this). Immediately after that, the recovery switches encryption type to FBE in the ROM's vendor.
Spoiler: What is this? What is it for?
Some definition:
Android 7.0 and higher supports file-based encryption (FBE). File-based encryption allows different files to be encrypted with different keys that can be unlocked independently.
https://source.android…/encryption/file-based
Click to expand...
Click to collapse
What does FBE encryption look like?
Spoiler
1. The contents and names of files/folders are encrypted using random characters:
2. Upon system startup, the device is absolutely usable and does not require to enter a password. FBE decryption is bound to Lock Screen and occurs at the time of unlocking using PIN/Password/Pattern.
At the time of writing this post, 100% of our devices use Full Disk Encryption (FDE). Traditionally, FDE encryption is enabled inside ROM's settings, and personally, I did not encounter problems with this type of encryption before Android 10. Unfortunately, on new Androids FDE is very unstable. Moreover, in Android 13 (T) it will be possible to encrypt only using FBE method because FDE method is officially deprecated and will be completely removed.
Android T (AOSP experimental) removes support for full-disk encryption entirely.
https://source.android…y/encryption/full-disk
Click to expand...
Click to collapse
Some FDE issues on Android 10+:
1. The device hangs on boot logo (requires formatting of /data to fix).
2. The device may boot up successfully and be detected as encrypted, but most of the installed applications and settings disappear forever.
3. The device boots correctly but is not detected as encrypted.
Having tried a bunch of ROMs, I have never encountered the problems above and have always been able to successfully encrypt the device with FBE method. Therefore, if you are interested in encryption, accustom yourself to encrypt immediately after ROM flashing, since everything is quite handy
Warning: decryption on Android 12+ and workaround | FIXED in OrangeFox R11.1(4)
Spoiler
FIXED in OrangeFox R11.1(4)
Unfortunately, all ROM's on Android 12+ for our device can successfully be encrypted/decrypted using FBE method, but decryption in recovery is problematic. This is an Android bug, which doesn't expose the decryption keys used by the recovery. Indeed, this is a recovery problem; Android 12 stores decryption keys elsewhere, so recovery can't find them. OrangeFox / TWRP devs are already in the process of adapting to the changes of Android 12. As soon as new recovery is ready I'll build a new release and everything will work. Fortunately, I found out that passwordless decryption works.
Temporary workaround:
1. Reboot to ROM
2. Remove the Lock Screen protection (PIN/Password/Pattern)
3. Reboot to recovery, the data will be automatically decrypted
4. When you're done, reboot to system and enable Lock Screen protection again
Note: you'll need to do this until the ROMs fix the decryption keys related issue.
If you don't remove the Lock Screen protection, then instead of the data you will get:
Spoiler: 2. GUI implementation for USB Storage Exporter by 0xCAFEBABE
This is a GUI implementation of usb-stor-export.sh script for geeks.
For the folks, I implemented a way to export entire eMMC memory. How to use this:
1. Disconnect from PC if connected
2. Go to Mount and swipe the slider
3. Connect the device to the PC
4. Your PC should detect a 16/32GB device, as if you connected an external hard drive
Now, all partitions are at your disposal. You can resize them to add to /data , or make an image of the entire eMMC memory (highly recommend) or backup a specific system partition and restore even on another device. Backup using recovery will not do this to you.
(!) DO EVERYTHING AT YOUR OWN RISK! I AM NOT RESPONSIBLE FOR YOUR ACTIONS ON SYSTEM PARTITIONS!
(!) EVEN IF YOU HAVEN'T TOUCHED ANYTHING, ALWAYS UNMOUNT THE DISK FROM THE OS AND ONLY THEN TAP "Unexport".
Spoiler: 3. eMMC Lifetime Used indicator
It displays life time estimation for your eMMC memory. The percentage means how many reserved blocks have been consumed.
The status can be:
- Undefined = The kernel driver cannot detect eMMC memory state
- Normal = Your eMMC memory is fine
- Warning = Your eMMC memory consumed about 80% of reserved blocks
- Urgent = Your eMMC memory consumed almost 100% of reserved blocks
- Reserved = Your eMMC memory consumed all 100% of reserved blocks and will put itself in read-only mode very soon
For geeks: tap on it to print all HEX values to the console.
Spoiler: 4. Enter to Fastboot Mode inside recovery
This is a hidden feature of OrangeFox itself that I've simply exposed. Unfortunately, important commands like fastboot boot exit with an error, because we are still in recovery and things are kind of busy ... But for something not used/static, like flashing partitions, it's working.
Spoiler: 5. fastboot binary
Now, using OrangeFox's embedded Terminal you can do everything you normally did using a PC.
* If you made a male-to-male USB using an USB-OTG cable, then plug the USB-OTG into the device that will send commands.
Illustration: Xiaomi helps Asus
Spoiler: 6. Dark/Light Theme Toggler accessible from anywhere
This is to make sure your eyes feel comfortable
7. Ability to reboot into Fastboot Mode
8. Binaries: nano, tar, sed and xz utils
9. Support mounting of NTFS drives via OTG
10. Handy aliases (l, ll, la, lo) for `ls` command
11. Colorful support for prompt string (PS1) and for `ls/grep/egrep/fgrep` commands when using ADB/AromaFM
12. VIM - Vi IMproved Editor
13. UI rendering at 60 FPS
14. Support Python
15. Semi-transparent Lock Screen background as in stock TWRP
16. Saving screenshots in /tmp/screenshots if /sdcard is not mounted
Miscellaneous:
Spoiler
Spoiler: Error 7. Failed to unmount: /system. No such volume.
Sometimes got this error when flashing old ROM's of Android 9 and lower. To fix it:
1. Open .zip archive and search for file:
Code:
META-INF/com/google/android/updater-script
2. Open it and remove parts where /system is mounted:
Code:
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup", "/system");
unmount("/system");
also this one
Code:
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore", "/system");
unmount("/system");
3. Save it and repack .zip archive
Spoiler: Red/Blue lines after flashing
Can be fixed by installing a more recent Firmware.
For rolex | For riva
* Firmware for riva is also available on Android 8, so experiment. The Firmware V10.1.1.0.NCKMIFI (Android 7.1) works 100%.
Changelog:
Spoiler
-- OrangeFox 11.1(5) --
* Synced with latest OrangeFox R11.1 sources (September 2022)
* Correct FBEToggler button position in some circumstances
* Handle FBE encryption toggling on Android 13+
* Added fastboot support when rebooting to fastboot from OS
* Moved nano editor to ZIP to save space in ramdisk
* Revert back to /sdcard1 path for Micro SDCard mounting
* Disabled APEX
* Removed logcat binaries to free space in ramdisk
* Updated ueventd from Android 11
* Fixed mke2fs issues when wiping
Thanks to @wisanggeni aka Ervan Kurnia for collaborating
* Updated kernel to 4.9.326-2.2-iusmac
* Updated Magisk to v25.2
-- OrangeFox 11.1(4) --
* Synced with latest R11.1 sources based on TWRP 3.6.2 (Android 12.1)
* Fixed ABX format conversion on Android 12 ROMs
* Moved not vital dependencies to /persist partition after flashing recovery using .zip archive
* Added a 'missing dependencies' pop-up at start-up with an invite to flash recovery using .zip archive
* Added full FBE decryption support for Android 12 ROMs
* Removed extra languages (Chinese, Spanish, Hungarian) to free space in ramdisk
* Added to the console an invite to downgrade the recovery for those who use FBE encryption and Android 11 or lower
-- OrangeFox 11.1(3) --
* Upgraded built-in Magisk to v25.1
* Fixed some bugs
* Added to the console an invite to update the recovery for those who use FBE encryption and Android 12 or higher
-- OrangeFox 11.1(2) --
* Replaced 'Percent' with % for eMMC Lifetime Used value
* Added 'Back' button to FBE Encryption Toggler page
* Added synchronization of the fstab encryption flag with the /data encryption type
* Added battery temperature next to CPU temperature
* Enabled OTA by default
-- OrangeFox 11.1(1) --
* Synced with latest R11.1 sources based on TWRP 3.6.2 (Android 11)
* Upgraded Linux kernel to 4.9.309 (from Android 12)
* Upgraded built-in Magisk to v25
* Added nano, tar, sed, xz utils binaries
* Fixed Full Disk Decryption (FDE) on Android 12+
* Added File Based Encryption (FBE) support
* Added NTFS support for OTG devices
* Added handy aliases (l, ll, la, lo) for `ls` command
* Added colorful support for prompt string (PS1) and for `ls/grep/egrep/fgrep` commands when using ADB/AromaFM
* Fixed nano non starting on OrangeFox's embedded Terminal due to missing terminal info
* Added prebuilt VIM - Vi IMproved Editor v8.2.1643
* Added FBE Encryption Toggler to Partition Manager page
* Enabled reboot to 'Fastboot' item unconditionally
* Labeled /dsp partition as 'DSP'
* Moved MicroSD card mount point from /sdcard1 to /external_sd
* Added GUI implementation for USB Storage Exporter by 0xCAFEBABE to Mount page
* Added eMMC Lifetime Used indicator to Partition Manager page
* Add entering to Fastboot mode page to Main menu
* Added fastboot v29.0.6
* Increased UI rendering to 60 FPS
* Added Python v3.10.4
* Added Dark/Light Mode Toggler
* Made the lockscreen background semi-transparent as in stock TWRP
* Added support for saving screenshots in `/tmp/screenshots` if `/sdcard` is not mounted
* Removed Splash changing (it requires ramdisk repacking in recovery.img which exceeds bootloader limit)
Spoiler: (Important) Which OrangeFox version you should choose
CaseR11.1(3) or olderR11.1(4) or newerLatest versionMy ROM is not encryptedXI have an encrypted MIUIXMy ROM was encrypted using ROM's settingsXMy ROM is Android 11 (or lower) and it's encrypted with FBE methodXMy ROM is Android 12 (or higher) and it's encrypted with FBE methodX
Download latest OrangeFox release | Find all OrangeFox releases​
OrangeFox 11.1(2) Update​
Code:
* Replaced 'Percent' with % for eMMC Lifetime Used value
* Added 'Back' button to FBE Encryption Toggler page
* Added synchronization of the fstab encryption flag with the /data encryption type
* Added battery temperature next to CPU temperature
* Enabled OTA by default
Download latest OrangeFox release | Find all OrangeFox releases​
OrangeFox 11.1(3) + OrangeFox 11.1(4) Update
Spoiler: (Important) Which OrangeFox version you should choose
CaseR11.1(3) or olderR11.1(4) or newerLatest versionMy ROM is not encryptedXI have an encrypted MIUIXMy ROM was encrypted using ROM's settingsXMy ROM is Android 11 (or lower) and it's encrypted with FBE methodXMy ROM is Android 12 (or higher) and it's encrypted with FBE methodX
Code:
-- OrangeFox 11.1(4) --
* Synced with latest R11.1 sources based on TWRP 3.6.2 (Android 12.1)
* Fixed ABX format conversion on Android 12 ROMs
* Moved not vital dependencies to /persist partition after flashing recovery using .zip archive
* Added a 'missing dependencies' pop-up at start-up with an invite to flash recovery using .zip archive
* Added full FBE decryption support for Android 12 ROMs
* Removed extra languages (Chinese, Spanish, Hungarian) to free space in ramdisk
* Added to the console an invite to downgrade the recovery for those who use FBE encryption and Android 11 or lower
-- OrangeFox 11.1(3) --
* Upgraded built-in Magisk to v25.1
* Fixed some bugs
* Added to the console an invite to update the recovery for those who use FBE encryption and Android 12 or higher
Download latest OrangeFox release | Find all OrangeFox releases​
MTP mode not working in rolex
ashish1989 said:
MTP mode not working in rolex
Click to expand...
Click to collapse
working fine on Linux (Ubuntu 21.10)
iusmac said:
working fine on Linux (Ubuntu 21.10)
Click to expand...
Click to collapse
I am using Windows 11 Pro in which it isn't whereas in official TWRP the MTP mode is working fine
ashish1989 said:
I am using Windows 11 Pro in which it isn't whereas in official TWRP the MTP mode is working fine
Click to expand...
Click to collapse
can't help. Working fine on both Linux and Window 10.
iusmac said:
can't help. Working fine on both Linux and Window 10.
Click to expand...
Click to collapse
Let me check once again
OrangeFox 11.1(5) Update​
Code:
* Synced with latest OrangeFox R11.1 sources (September 2022)
* Correct FBEToggler button position in some circumstances
* Handle FBE encryption toggling on Android 13+
* Added fastboot support when rebooting to fastboot from OS
* Moved nano editor to ZIP to save space in ramdisk
* Revert back to /sdcard1 path for Micro SDCard mounting
* Disabled APEX
* Removed logcat binaries to free space in ramdisk
* Updated ueventd from Android 11
* Fixed mke2fs issues when wiping
Thanks to @wisanggeni aka Ervan Kurnia for collaborating
* Updated kernel to 4.9.326-2.2-iusmac
* Updated Magisk to v25.2
Download latest OrangeFox release | Find all OrangeFox releases​
for everyone who face issue "unknown partition" . try fastboot flash recovery {put-here-orangefox-recovery-file-name}.img

Categories

Resources