Database Develop

[Recovery] [V3.0-006] 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"
}
/* Your warranty is now void! I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the flashlight 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 me for messing up your device, I will laugh at you. */
Click to expand...
Click to collapse
Introduction
Red Wolf Recovery is alternatovní recovery based on the source code TWRP.
The main objective of the Red Wolf Recovery is to provide the features that were for some reasonrefusedto add to the official source code Winu Team (besides the maximum utilization of hardware options that device ...).
Hence Recovery supports password protection, since Team Win rejected this method of security because users generally do not read any kind of warning, then it was just a mistake on the part of Team Winu that somebody got into the facility despite a recovery password protected.
For this reason, therefore, I warn that the red wolf is secured in such a way that nobody could get into recovery without the user's password, but no recovery willnot safeguardagainst reinstall the device via Flash or Mi fastboot. So please take a note!
Acknowledgments:
Ray Li: For his help in modifying the source code TWRP.
osm0sis: In the video below scripts which also runs most of the functions recovery.
z31s1g: For the base material. theme.
And all the other developers of the various scripts and installation files as Chanfire,topjohnwu,cofface,etc
Features recovery:
- Brightness can be reduced to a minimum fair value. (TWRP only supports a minimum of 10% Brightness).
- Support for more than 50 sections (including "subsections").
- Possibility of installation of paintings in section Modem and Boot Logos.
- Adjusted ADB - for security reasons already does not start automatically at boot recovery, but now it turns in the recovery
- Recovery allows you to set and remove a password
- Torch phone is now going to turn right in Recovery
- Automatically Block stock recovery
- Recovery contains settings regarding Governor where recovery is currently running. If, therefore, not in a hurry, so just switch to performance and processes such as backup, restore or installation will be up almost 20% faster.
- When you confirm the installation file on the screen appears and warnings checkbox for the finished installation. This recovery will automatically notify the completed installation using the notification LED.
- For safety reasons deactivated TWRP theme engine.
- Official TWRP application was replaced for Snap Camera HDR.
- Access to the folder with zálohama and setting recovery is blocked. Access to these files is only possible from the recovery. (This is only an internal storage)
- The first recovery that is built on OMNI ROM code purely for Kate.
- Folder screenshotama of recovery has been moved to /sdcard/WOLF.res to already screenshots of recovery are not confused with the other screenshotama ..
- Updated Czech translation - Slovak translation can be translated from the strings provided below.
- new terminal supports three commands: unpackbootimg, mkbootimg and zipper (so they may also be retrieved from the script, of course).
- Recovery supports Tap To Wake Engine (dt2w is not supported yet ...)
- Support for "night mode".
- Built AromaFM supports Czech language.
- User can set custom name for the folder backup & ID at the ADB.
- Create backup can also be erased at once (not therefore been deleted one by one as it is in ofiko TWRP).
- Recovery is assembled on AOSP 7.1.2 / TWRP 3.1.1-0 / Omni 7.1.2.
Built-in installation files:
Supers
Magisk
Nitrogen UNROOT
substrates Rescue
Deactivation dm-verity
substrates Rescue Legacy
- Built-in scripts community:
Fix-fp-scanner (script to fix the fingerprint reader if the ROM reports "hardware can not be found")
ramdisk- cleaner (the script automatically cleans content boot from custom kernels and thus need not be renewed when switching to a different kernel stock kernel. However, the script still only supports ElementalX kernel, Radon kernel and Franco kernel.Warning: After cleaning the content boot must just to flash a new kernel - certainly attempt to restart the device to the system !!)
rm-pass(script to remove security currently installed ROM.)
NOS-before-flash-other-kernel(script recently found on 4PDA - deactivates the post-script Nitrogen boot ROM and thus allows better compatibility custom kernel).
Community scripts can thus be understandable added community. If you have your script / tip on a script about it here let me know.

Known Bugs
- The search engine of the camera HDR Snap is momentary assembly inoperable. TWRP still finds the application and if the application is installed TWRP and even prevents installation Snap CAMERA HDR.
The problem is mainly that I do not have complete access to that search engine - probably even if I somehow repaired and recovery will still prefer ofiko TWRP search application. So it probably could not be correct function ofiko TWRP applications not installed. However, definitely I do something in the next builds I make.

Link to download
latest build released: official
https://www.androidfilehost.com/?fid=889764386195913594
Update Changes
Update!
RedWolf-V3.0_006-Kate_Kenzo
Major changes;
- After clicking on the main menu icon coffee displays a new button "folder backups." Here you can now rename your current folder & zálohama or even set a new ID instead of the serial number at the ADB.
- Clicking on the Main Menu button to restore the icon appears at the top "bones". Using this button you can now delete all backups currently displayed. Therefore no longer need to delete one by one separately.
Current info
Version recovery: V3.0
Current build: 006
Number of community scripts: 4
Number of installation files: 6
Date of latest released build: 05-7-2017

Strings of recovery can be download here:
Strings for any translation AromaFM:
Extra Links
https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9
https://github.com/TeamWin
All Credit to ATG Droid
Source

Ss pls

not in a hurry but will have to remind you that source is not updated.... please add
~peace

AxeCORE said:
Ss pls
Click to expand...
Click to collapse
here!

adithyan25 said:
not in a hurry but will have to remind you that source is not updated.... please add
~peace
Click to expand...
Click to collapse
Visit our Forum - https://androidforum.cz
měj hezký den

Can i flash any rom on this type of recovery ?

xN00Bx said:
here!
Click to expand...
Click to collapse
Flashed just now device is not rebooting to recovery mode at all instead of going to recovery mode device is booting to normal plz check it
Previously i am using zcx twrp from that i have flashed this recovery flashing done successfully no issues about thag
Waiting for solution

cherri said:
Flashed just now device is not rebooting to recovery mode at all instead of going to recovery mode device is booting to normal plz check it
Previously i am using zcx twrp from that i have flashed this recovery flashing done successfully no issues about thag
Waiting for solution
Click to expand...
Click to collapse
+1

filipino guy said:
Can i flash any rom on this type of recovery ?
Click to expand...
Click to collapse
Yes you can flash it on any roms
cherri said:
Flashed just now device is not rebooting to recovery mode at all instead of going to recovery mode device is booting to normal plz check it
Previously i am using zcx twrp from that i have flashed this recovery flashing done successfully no issues about thag
Waiting for solution
Click to expand...
Click to collapse
after flash press reboot to recovery ( if your device booting normally) then press vol plus + power button immediately after the screen goes down while pressing reboot to recovery,
try again master, no problem here!

xN00Bx said:
Yes you can flash it on any roms
after flash press reboot to recovery ( if your device booting normally) then press vol plus + power button immediately after the screen goes down while pressing reboot to recovery,
try again master, no problem here!
Click to expand...
Click to collapse
Yaa now working don't know why it didn't worked at first he he he thank you bro

I am having some weired grains on the screen when reboot to recovery..after a few seconds the grains disappears andt
reboots to system

anandumohan said:
I am having some weired grains on the screen when reboot to recovery..after a few seconds the grains disappears andt
reboots to system
Click to expand...
Click to collapse
Same thing

Recovery was withdrawn because its not yet ready to run on the variant Kenzo fully,
only kate is completely functional!
we will back to you when it's gets fixed
~thanks

Mod Edit
Thread closed at the request of the [OP]
malybru
Senior Moderator

[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][UNOFFICIAL][09/20]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: Z2 PRO, Z2121, Z2_ROW
TREE: https://github.com/mracar07/android_device_zuk_z2_row/tree/RWRecovery
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), cosmedd for twrp tree
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
- kernel compiled inline with the recovery
- fixed backup/restore of Firmware
- added F2FS support
- added NTFS support
- added exFAT support
- more languages
- other improvements from Features and Changelog lists
Changelog:
04/09:
Treble Support
In AEX Blue Led of Death fixed
thanks to @cosmedd
Redwolf source updated...
04/09 Second Release:
Slow backup-restoring fixed
04/18:
Renamed from factory to vendor
BUGs:
Only in recovery FLASHLIGHT
Downloads:
Latest build for ZUK Z2 PRO(z2_row):
https://androidfilehost.com/?fid=1322778262904009823
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.
Donate DEV: paypal.me/mracar07​

Flashed, no problem...excellent development, thank you!

flashed, made backup and restore with it, worked without problems. Thanks!

looks interesting any incompatiblity with roms? is the su included? or just a script to install from path "xyz"? is the kernel change / govenor change permanently or temporary for one boot?
so many questions :fingers-crossed: thx for your work guys

Thanks for your work ,but I met some trouble .I use AEX 5.2 ,try to flash this recovery from twrp. but when I rebot to the RW , I can see RW's first screen ,then LED was blue(900E) .I back to TWRP now. I hope you can fix it.THX

江泽民1926 said:
Thanks for your work ,but I met some trouble .I use AEX 5.2 ,try to flash this recovery from twrp. but when I rebot to the RW , I can see RW's first screen ,then LED was blue(900E) .I back to TWRP now. I hope you can fix it.THX
Click to expand...
Click to collapse
Not have any issiue. Tested and working properly :good:

Does it chinese language supported?I can help you im chinese

江泽民1926 said:
Thanks for your work ,but I met some trouble .I use AEX 5.2 ,try to flash this recovery from twrp. but when I rebot to the RW , I can see RW's first screen ,then LED was blue(900E) .I back to TWRP now. I hope you can fix it.THX
Click to expand...
Click to collapse
me too!

Bave Lee said:
Does it chinese language supported?I can help you im chinese
Click to expand...
Click to collapse
-> "Translated to EN, PL, zh_cn, & CZ "

Great Project! We need a german translation. I can help you. Tell me what can i do. OK, i see we have a german translation. Great work.

江泽民1926 said:
Thanks for your work ,but I met some trouble .I use AEX 5.2 ,try to flash this recovery from twrp. but when I rebot to the RW , I can see RW's first screen ,then LED was blue(900E) .I back to TWRP now. I hope you can fix it.THX
Click to expand...
Click to collapse
Hi, Chairman 江☺I 've encountered the same issue with you, I am currently using MIUI 9 , not sure if I need to clean up the old TWRP files.
Did you flash latest LR.Team TWRP (by wzsx150)?

Updated. 04/09.
for test thanks to @weimerd

04/09 Second Release:
Slow backup-restoring fixed
for test thanks to @weimerd

Thanks man, nice work

Unfortunately not possible to run edl mode . Btw good work and recovery works quite good and fast . Thanks for your work .

mar.ur said:
Unfortunately not possible to run edl mode . Btw good work and recovery works quite good and fast . Thanks for your work .
Click to expand...
Click to collapse
There's no direct button for it within RW Recovery, but it has adb working, so once you're started up in Red Wolf Recovery, just plug into the computer and send it "adb reboot edl" from a terminal. I just tested it and it worked fine.
I'm assuming you have a functional installation of android sdk or platform tools and working USB drivers on a capable computer, otherwise what exactly did you plan on doing with EDL mode anyway?

Terminator.J said:
There's no direct button for it within RW Recovery, but it has adb working, so once you're started up in Red Wolf Recovery, just plug into the computer and send it "adb reboot edl" from a terminal. I just tested it and it worked fine.
I'm assuming you have a functional installation of android sdk or platform tools and working USB drivers on a capable computer, otherwise what exactly did you plan on doing with EDL mode anyway?
Click to expand...
Click to collapse
No possible to run edl mode from system by ADB command . Edl = download and is existing in twrp as I know .

mar.ur said:
No possible to run edl mode from system by ADB command . Edl = download and is existing in twrp as I know .
Click to expand...
Click to collapse
... I"m sorry, I don't know what else to say, other than either you're wrong or there must be something wrong with your computer/phone configuration. I literally just started up in the latest red wolf recovery, connected via USB cable to my computer (Windows 10 laptop), opened an administrative command prompt on the computer, cd to directory I unzipped platform tools to, typed "adb reboot edl", and the phone rebooted into emergency download mode, and ran QFIL, which sees a 9008 mode device ready for flash.
However I did also test from within the recovery itself... going to terminal inside RW recovery and typing "reboot download" did not work, it just restarted normally. That is true. But again, it's not an issue since you have the computer & USB cable there (or else you wouldn't need EDL mode) and can just send the adb command from the computer.

I only reported that is impossible to run edl mode from system by ADB and from twrp by download button .

04/18 UPDATED....
Renamed from factory to vendor

[RECOVERY][UNOFFICIAL][3.5.2] TWRP for Galaxy M21

{
"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"
}
Disclaimer:
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 recovery 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.
Kernel Features:
latest kernel source release
disabled security stuff/knox/proca/logging/audit/useless features
Recovery Features:
TWRP 3.5.0, Android 10
Built in 64-bit mode
Super partition support
Added custom super binary to help with managing super partitions ( more on that in post #3 )
Native rw mount dynamic partitions
Native GSI flashing
Native dynamic partitions resize/wipe/backup/restore
Working MTP and ADB only!
How to install?
Spoiler: ODIN(Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Press the volume down + volume up button whilst the phone is connected to a pc to boot in download mode;;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol down + bixby key + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, factory reset data and redo from step 5!
Download TWRP.tar from download link below;
Open odin and place the TWRP.tar file in AP slot and press start. Once you press start, keep holding power and volume up button and the device will reboot to recovery mode.
* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this Internal storage won't work in TWRP
Flash the encryption_disabler.zip from the link below to disable internal storage encryption and patch stock recovery restoration.
Additionally, flash TWRP_Bootlogo_patcher to patch warning screens when booting the device.
If you want to root, flash Magisk.
Spoiler: TWRP
If you're coming from other TWRP versions, download TWRP.img, reboot to recovery, tap Install > Install Image > Navigate to downloads folder > select TWRP.img > Select Recovery and swipe to confirm flash. Go to reboot and reboot to recovery and the changes will have taken place.
Downloads:
TWRP-3.5.2-m21-v3.1 ( Android 11 ONLY )
TWRP-3.5.1-v3.0_m21nsxx ( Android 11 ONLY )
TWRP-3.5.0-v2.0_m21nsxx ( Android 11 ONLY )
TWRP-3.5.0-v1.1_m21nsxx ( Android 10 ONLY )
Encryption Disabler
TWRP_Bootlogo_patcher
Sources:
Device Tree: https://github.com/soulr344/android_device_samsung_m21
Kernel Source: https://github.com/soulr344/android_kernel_samsung_m21nsxx/tree/prebuilt
TWRP Source: https://github.com/soulr344/android_bootable_recovery/commits/android-10.0
Credits:
TeamWin, corsicanu, ananjaser1211, jesec, epicX67, testers and anyone else who made this possible.

Changelog:
v2.0
Initilal Android 11 support
isn't backwards compatible with android 10
rewrote fstab
added EFS/SecEFS Image Backup
added prism/optics mount
v1.1
fixed adb only
permissive
updated super binary
fixed long boot time
v1.0
Initial Release
MISC LINKS
Telegram Channel
Telegram Group
TeamWin Official Website

FAQ
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you flashed encryption disabler zip / formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing a more recent firmware. If you still don't succeed, post here some details about your device and previous firmware and we might be able to help.
Q: Why do i need to format data partition?
A: Because old firmware encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
Q: I can't flash anything with TWRP. Internal Storage has some random folders with weird name.
A: Format Data and flash encryption disabler.

Info about custom super partition helper binary. (Irrelevant because of native logical partitions but yeah, its present)
It's meant to help with managing partitions inside the super partition itself. It has some functions built in like mount, unmount, flash and format. Here is a brief rundown on what each of them do.
Partitions that are supported are:
system, system_root, vendor, odm, product
Click to expand...
Click to collapse
Please note that system_root is an alias of system and umount is an alias of unmount.
All of these commands are runnable through TWRP Terminal ONLY!
Code:
super mount partition
This will mount partition in rw mode in mountpoint in fstab.
Code:
super unmount[or umount] partition
This command will unmount given partition and make it read only.
Code:
super format partition
This command will format given partition as ext4 inside super partition.
Code:
super flash partition /path/to/image.img
Flashes image.img to partition.
You can also flash GSI (Generic System Image) using this command. Simply run:
Code:
super flash system /path/to/gsi.img
For Custom ROM Developers:
You can use this as an alternative to mount/format/unmount partitions that are inside super partition normally.
Code:
run_program("/sbin/super", "format", "system"); # formats system
run_program("/sbin/super", "mount", "system"); # mounts system as rw
run_program("/sbin/super", "unmount", "system"); # unmounts system and makes it ro

Don't own an M21 but good job

Good work bro

Well nice, indeed

Don't hab M21 but Excellent Work

Can I flash it on M21s (F415)?

well done soul

Excellent. Will try it out very soon.

bro , Encryption disabler.zip link doesn't work

soulr344 said:
Disclaimer:
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 recovery 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.
Kernel Features:
latest kernel source release
disabled security stuff/knox/proca/logging/audit/useless features
Recovery Features:
TWRP 3.5.0, Android 10
Built in 64-bit mode
Super partition support
Added custom super binary to help with managing super partitions ( more on that in post #3 )
Working MTP and ADB only!
How to install?
Spoiler: ODIN(Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Press the volume down + volume up button whilst the phone is connected to a pc to boot in download mode;;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol down + bixby key + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, factory reset data and redo from step 5!
Download TWRP.tar from download link below;
Open odin and place the TWRP.tar file in AP slot and press start. Once you press start, keep holding power and volume up button and the device will reboot to recovery mode.
* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this Internal storage won't work in TWRP
Flash the encryption_disabler.zip from the link below to disable internal storage encryption and patch stock recovery restoration.
Additionally, flash TWRP_Bootlogo_patcher to patch warning screens when booting the device.
If you want to root, flash Magisk.
Spoiler: TWRP
If you're coming from other TWRP versions, download TWRP.img, reboot to recovery, tap Install > Install Image > Navigate to downloads folder > select TWRP.img > Select Recovery and swipe to confirm flash. Go to reboot and reboot to recovery and the changes will have taken place.
Downloads:
TWRP-3.5.0-v2.0_m21nsxx
TWRP-3.5.0-v1.1_m21nsxx
Encryption Disabler
TWRP_Bootlogo_patcher
Sources:
Device Tree: https://github.com/soulr344/android_device_samsung_m21nsxx
Kernel Source: https://github.com/soulr344/android_kernel_samsung_m21nsxx/tree/prebuilt
TWRP Source: https://github.com/TeamWin/android_bootable_recovery/commits/android-10.0
Credits:
TeamWin, corsicanu, ananjaser1211, jesec, testers and anyone else who made this possible.
Click to expand...
Click to collapse
soulr344 said:
Changelog:
v2.0
Initilal Android 11 support
isn't backwards compatible with android 10
rewrote fstab
added EFS/SecEFS Image Backup
added prism/oE]
Hi mate,
tried several times to get the encryption disabler.
No access and no reply when asking for access.
What can I do?
Thanks,
Jürgen
Click to expand...
Click to collapse
kayfee said:
bro , Encryption disabler.zip link doesn't work
Click to expand...
Click to collapse
Hi mate,
Could you please give me access to the encrypt disabler link?
Thanks,
Jürgen

encryption disabler
st

kebson4021 said:
encryption disabler View attachment 5254867st
Click to expand...
Click to collapse
You can flash multi disabler instead. Its available in the telegram group for the device.

encryption disabler...
just put new link please...
I flashed with this Kernel and phone start working...

@soulr344 Does TWRP_Bootlogo_patcher work on Android 11?

mudshark1309 said:
Hi mate,
Could you please give me access to the encrypt disabler link?
Thanks,
Jürgen
Click to expand...
Click to collapse
yep, given access to everyone. check again

userprince said:
@soulr344 Does TWRP_Bootlogo_patcher work on Android 11?
Click to expand...
Click to collapse
yep

Thanks for keeping this updated

[RECOVERY][UNOFFICIAL] TWRP for Galaxy M31s (Exynos)

{
"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.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
Supported Models:
Galaxy M31s M317F.
Download & Guide:
1. Unlock your bootloader.
2. Download M31s : m31s.
3. Reboot to download mode and flash vbmeta_disabled.tar in USERDATA slot and click start, Device will reboot to recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
4. Put the TWRP TAR for your device with Odin in the AP slot and click start.
5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.​If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​- Type: multidisabler again. will see - Finished. when done.​- Go back to Wipe > Format Data > type yes.​- Reboot to recovery.​7. Flash magisk apk in twrp.
8. Reboot to system, Enjoy.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram:
Link
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree

Changelog:
29.11.2021 - Update to TWRP 3.6.0
- Add Symlinked dynamic partitions to fstab
- Update multidisabler
- fstab clean up
04.06.2021 - Initial Release.

vbmeta_disabler_R stuck on ODIN.
UPD: It's flashed, but after TWRP.tar flashing, I'll have an VBMeta error in Download Mode.

withwaves86 said:
vbmeta_disabler_R stuck on ODIN.
UPD: It's flashed, but after TWRP.tar flashing, I'll have an VBMeta error in Download Mode.
Click to expand...
Click to collapse
file updated

afaneh92 said:
file updated
Click to expand...
Click to collapse
It works, thank you. I'll be test this

Is it working on One Ui 3.1 on M31?

Atharkhan101 said:
Is it working on One Ui 3.1 on M31?
Click to expand...
Click to collapse
You can test

afaneh92 said:
You can test
Click to expand...
Click to collapse
In not here to test. I don't want to screw my phone.

Atharkhan101 said:
In not here to test. I don't want to screw my phone.
Click to expand...
Click to collapse
Then dont

TWRP works in ONEUI 3.1. I flashed it but after it boots to the system and I reboot it or shut it down I get only official binary are allowed to be flashed, and I have to go back to stock. Latest U3 Android 11 M31S. Do you have any kernel for this model?

Working on M31s One UI 4.1

afaneh92 said:
3. Reboot to download mode and flash vbmeta_disabled.tar in USERDATA slot and click start, Device will reboot to recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
Click to expand...
Click to collapse
does this mean I will have to wipe my phone's entire data?

CosmicSavage said:
does this mean I will have to wipe my phone's entire data?
Click to expand...
Click to collapse
yes

The device is not going into recovery mode instead getting stuck at samsung logo after flashing vbmeta using odin

afaneh92 said:
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.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
Supported Models:
Galaxy M31s M317F.
Download & Guide:
1. Unlock your bootloader.
2. Download M31s : m31s.
3. Reboot to download mode and flash vbmeta_disabled.tar in USERDATA slot and click start, Device will reboot to recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
4. Put the TWRP TAR for your device with Odin in the AP slot and click start.
5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.​If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​- Type: multidisabler again. will see - Finished. when done.​- Go back to Wipe > Format Data > type yes.​- Reboot to recovery.​7. Flash magisk apk in twrp.
8. Reboot to system, Enjoy.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram:
https://t.me/a11twrp
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree
Click to expand...
Click to collapse
Hello Bruh..it worked.. i had issue earlier with the
KG State and/or RMM state prenormal then i reflashed using the official m31S ROM then i unlocked the OEM and flashed the above two files at the same time using odin

afaneh92 said:
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.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
Supported Models:
Galaxy M31s M317F.
Download & Guide:
1. Unlock your bootloader.
2. Download M31s : m31s.
3. Reboot to download mode and flash vbmeta_disabled.tar in USERDATA slot and click start, Device will reboot to recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
4. Put the TWRP TAR for your device with Odin in the AP slot and click start.
5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.​If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​- Type: multidisabler again. will see - Finished. when done.​- Go back to Wipe > Format Data > type yes.​- Reboot to recovery.​7. Flash magisk apk in twrp.
8. Reboot to system, Enjoy.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram:
https://t.me/a11twrp
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree
Click to expand...
Click to collapse
Hi ,
Thanks a lot for the TWRP support.
Although I'm able to successfully complete all the above steps , once i boot into system KG state is triggered and i end up getting the error "Only official released binaries are allowed to be flashed".
and the device goes into KG state = prenormal and its locked for 7 days.
i also tried flashing RMM_Bypass_v3_corsicanu , but no luck as it is throwing ERROR : " cant mount /system_root .... aborting"
(currently M31s is running on Android 11)
Kindly Help.
Thanks

Hangrylion said:
Hi ,
Thanks a lot for the TWRP support.
Although I'm able to successfully complete all the above steps , once i boot into system KG state is triggered and i end up getting the error "Only official released binaries are allowed to be flashed".
and the device goes into KG state = prenormal and its locked for 7 days.
i also tried flashing RMM_Bypass_v3_corsicanu , but no luck as it is throwing ERROR : " cant mount /system_root .... aborting"
(currently M31s is running on Android 11)
Kindly Help.
Thanks
Click to expand...
Click to collapse
You don't need all this hassle just connect to internet and open browser then check kg status, must be checking.

are the links updated?

Any update on M31s android 12 OneUI Core 4.1 ???
I didn't seem to be working many guys said here they were forced to go back to the official rom...
Can someone confirm what's going on?

osama_blythe said:
Any update on M31s android 12 OneUI Core 4.1 ???
I didn't seem to be working many guys said here they were forced to go back to the official rom...
Can someone confirm what's going on?
Click to expand...
Click to collapse
M31s, android 12, OneUI core 4.1,
working perfectly with no any issue with TWRP and magisk.