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][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][Realme 6 Pro] TWRP Recovery [Stable]

{
"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 (or isn't ? who am I to judge ?)
*
* We are 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.
*
*/
Team Win Recovery Project 3.4.1 for Realme 6 Pro
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.
Ported From Realme X50 5G
• by ctapchuk from 4pda
Most Bugless Recovery Right Now
Installation
1. Disable verified boot first
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img which is extracted from current stock rom ozip file
2. Flash downloaded twrp
Code:
fastboot flash recovery twrp.img
3. Reboot to recovery
Code:
fastboot reboot recovery
List of features :
• Decryption of storage works on latest Stock firmware (September security patch)
• Successful installation of any ROM's
• External sdcard & USB-OTG support
• Additional features such as close AVB2.0 (disabled-verify on vbmeta), disable replace TWRP
• Working mounting of dynamic partitions (r/o only)
• Additional backup/restore partitions list (except system, vendor and etc)
Download :
https://drive.google.com/file/d/1NWS74xHgyIKwpTd5sZ6af9ukroXF7VAp/view?usp=sharing
Version Information
Status : Stable
Current Stable Version : 3.4.1b_0507
Stable Release Date : September 30, 2020

Reserved

Good work, i was trying to find a proper TWRP for my Realme 6 Pro from lasat week.
Until now i was able to flash updates or downgrades just via Realme Flash Tool.
Do we still need to flash vbmeta_v2 in order for TWRP to work properly?
Testing now.
Update:
It does need the OF_avb-patcher.zip tp be flashed in order to keep TWRP after restart and to decrypt MPT storage and phone corectly.
I did not flashed it and all the time got stuck in a boot loop and TWRP and all phone remained encrypted, was not able to do anything until i flashed Stock Rom via Realme Flash Tool.
Disclaimer: Flashing Stock Rom will make TWRP gone, to preserve it, follow the steps:
1. Flash Stock ROM .ozip
2. Flash patched-vbmeta-v2.img
3. Flash TWRP from above link
4. Flash OF_avb_patcher.zip
6. Flash Magisk via TWRP (If required)
7. Done

Richardo87 said:
The same issue i was getting with the previous TWRP versions, cannot access MTP storage. Also while phone on, cannot copy anything on storage.
Click to expand...
Click to collapse
Please provide screenshots of your problem. I assume that you are trying to copy files to an encrypted internal storage. Decrypt /data or copy files to SD card

Is this compatible with build number RMX2061_11_A.35? Thank you!
Sent from my RMX2061 using XDA Labs

ByinAlbirt said:
Is this compatible with build number RMX2061_11_A.35?
Click to expand...
Click to collapse
Yes

Richardo87 said:
Good work, i was trying to find a proper TWRP for my Realme 6 Pro from lasat week.
Until now i was able to flash updates or downgrades just via Realme Flash Tool.
Do we still need to flash vbmeta_v2 in order for TWRP to work properly?
Testing now.
Update:
It does need the OF_avb-patcher.zip tp be flashed in order to keep TWRP after restart and to decrypt MPT storage and phone corectly.
I did not flashed it and all the time got stuck in a boot loop and TWRP and all phone remained encrypted, was not able to do anything until i flashed Stock Rom via Realme Flash Tool.
Disclaimer: Flashing Stock Rom will make TWRP gone, to preserve it, follow the steps:
1. Flash Stock ROM .ozip
2. Flash patched-vbmeta-v2.img
3. Flash TWRP from above link
4. Flash OF_avb_patcher.zip
6. Flash Magisk via TWRP (If required)
7. Done
Click to expand...
Click to collapse
No need i guess. Try 'Disable Replace TWRP' and reboot ...

debdeep98 said:
Yes
Click to expand...
Click to collapse
Thank you so much! I have successfully installed TWRP Recovery in my realme 6 Pro build number RMX2061_11_A.35.
Sent from my RMX2061 using XDA Labs

Richardo87 said:
Good work, i was trying to find a proper TWRP for my Realme 6 Pro from lasat week.
Until now i was able to flash updates or downgrades just via Realme Flash Tool.
Do we still need to flash vbmeta_v2 in order for TWRP to work properly?
Testing now.
Update:
It does need the OF_avb-patcher.zip tp be flashed in order to keep TWRP after restart and to decrypt MPT storage and phone corectly.
I did not flashed it and all the time got stuck in a boot loop and TWRP and all phone remained encrypted, was not able to do anything until i flashed Stock Rom via Realme Flash Tool.
Disclaimer: Flashing Stock Rom will make TWRP gone, to preserve it, follow the steps:
1. Flash Stock ROM .ozip
2. Flash patched-vbmeta-v2.img
3. Flash TWRP from above link
4. Flash OF_avb_patcher.zip
6. Flash Magisk via TWRP (If required)
7. Done
Click to expand...
Click to collapse
All you need is vbmeta.img from your stock ROM.
I used above instructions and everything work just fine, including decryption of internal storage.
@Kevin Saiza thank you for your good work.
Everything's working as expected.
Right now I'm using:
Firmware A.35
LR.TWRP 3.4.1B_30.09
Magisk 21.0 (pass safety net check)

Newer version with all features including fastboot(d) working, ported from Xiaomi Black Shark 3 is on download in pda. Can someone attach download link here for :
LR.TWRP 3.4.2B_05.10 — RMX2061 (from Black Shark 3) .img
or
LR.TWRP 3.4.2B_05.10 — RMX2061 for Windows.zip
Thanks!

Junior MemberThanks: 0
Junior MemberThanks: 0
Is this compatible with build number RMX2065_11_A.35? Thank you!

neoxcool said:
Newer version with all features including fastboot(d) working, ported from Xiaomi Black Shark 3 is on download in pda. Can someone attach download link here for :
LR.TWRP 3.4.2B_05.10 — RMX2061 (from Black Shark 3) .img
or
LR.TWRP 3.4.2B_05.10 — RMX2061 for Windows.zip
Thanks!
Click to expand...
Click to collapse
Coming Soon

Andres88z said:
Junior MemberThanks: 0
Junior MemberThanks: 0
Is this compatible with build number RMX2065_11_A.35? Thank you!
Click to expand...
Click to collapse
Yes why not .

Kevin Saiza said:
Yes why not .
Click to expand...
Click to collapse
Some problem with RMX2063. You try whit RMX2061
Sorry Is 2063
thank's

LR.TWRP 3.4.2B_05.10 for RMX2061 Ported from Xiaomi Black Shark 3 by Ctapchuk & logotoy73
Change extention to .img
https://anonfiles.com/hfcehcd1p9/LR.TWRP_3.4.2B_05.10_for_RMX2061_img
Changelog:
• Port from Xiaomi Black Shark 3
• Upgrade to version 3.4.2
• Fixes in Russian language
• Changed the font for English language
• Fixed fastbootd
• A/B table selection Disabled
• Correct display of the status bar

If i only boot, i need flash vbmeta?

I need urgent help please the twrp does not recognize my otg it only recognizes the sd but the otg does not what should I do to make it recognize it please help

:good:

Can't delete file from phone with root explorer so i tried with TWRP as usualy and for the first time IT DOESNT WORK!! Never seen that before. Though system's not mounted as read only. What to do..?

Do nothing. vendor, product and system partitions are R/O, because they are part of new type partition named "super". It is dynamic partition that is not editable.
Take a look here for details
Implementing Dynamic Partitions | Android Open Source Project
source.android.com

[CLOSED][RECOVERY][dandelion][v3.0.0]Pitch Black Recovery[31/12/2020]

{
"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:
/*
*Disclaimer
*
* 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.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.4.0
PitchBlack version: 3.0.0
For device: dandelion
Maintainer/Authors build: PBRP Team
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/PitchBlackRecoveryProject/android_device_xiaomi_dandelion-pbrp
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
Full dark theme with changeable accents
Reorganized menus
MIUI OTA support
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Installation Instructions
From previous version or other recovery
Download the PitchBlack zip to your device
Reboot to your current custom recovery
Flash the PitchBlack zip
The device will automatically reboot into PitchBlack Recovery after installation
Enjoy
From PC
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by
Code:
fastboot flash recovery recovery.img
Flash vbmeta (get from fastboot rom)
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Boot into PBRP by
Code:
fastboot boot recovery.img
or
Code:
fastboot oem reboot-recovery
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
Bugs
- fastbootd
- sideload
Device Tree:- https://github.com/PitchBlackRecoveryProject/android_device_xiaomi_dandelion-pbrp
Downloads
Dropped Support
You Can Build Amd Fix Bugs As Device Tree I have shared

cant wait to try! thanks for your work mate!

touch screen not working plz help me...

dreadmachine said:
touch screen not working plz help me...
Click to expand...
Click to collapse
it is working for me
check if touch is working in this https://gofile.io/d/UWjWjR

Mrinalsaha said:
it is working for me
check if touch is working in this https://gofile.io/d/UWjWjR
Click to expand...
Click to collapse
sadly wont boot, i tried flashing it, but its not booting to it

dreadmachine said:
sadly wont boot, i tried flashing it, but its not booting to it
Click to expand...
Click to collapse
it boot but the screen stays black
press power button 2 times to see it when it is in black screen

i did and it worked, but.... when i install system.img of rom, it says no os on system.. sure you want to reboot?

everything functions correctly(mtp,brightness,touch,decryption) but couldn't root with magisk(both with recovery provided one and the official one) it flashes, but when i turn on device and open the magisk manager app, it shows no root. and tried flashing gsi (to super partition) messed up the partition table. didn't try backup. couldn't find a way to wipe system, there was no system entry. couldn't mount it either

Rediancool said:
everything functions correctly(mtp,brightness,touch,decryption) but couldn't root with magisk(both with recovery provided one and the official one) it flashes, but when i turn on device and open the magisk manager app, it shows no root. and tried flashing gsi (to super partition) messed up the partition table. didn't try backup. couldn't find a way to wipe system, there was no system entry. couldn't mount it either
Click to expand...
Click to collapse
flashing magisk to get root works but you'll have to use the latest 21.2 version
I have tried to flash all the magisk version but only 21.2 gave me root
download from here https://github.com/topjohnwu/Magisk/releases

Mrinalsaha said:
flashing magisk to get root works but you'll have to use the latest 21.2 version
I have tried to flash all the magisk version but only 21.2 gave me root
download from here https://github.com/topjohnwu/Magisk/releases
Click to expand...
Click to collapse
thanks man it worked. were you successful in flashing gsi?

Rediancool said:
thanks man it worked. were you successful in flashing gsi?
Click to expand...
Click to collapse
how are you suggesting that I would flash gsi ?

Mrinalsaha said:
how are you suggesting that I would flash gsi ?
Click to expand...
Click to collapse
i meant did you flash gsi with this

Is there any way to flash arm64 gsi in redmi 9a? because I want to run google camera which works in 64bit

Rediancool said:
i meant did you flash gsi with this
Click to expand...
Click to collapse
no it cannot be flashed

i can not edit system files from any root explorer
or move files in root with pbrp file manager. any suggestions?
several forum post suggested that editing system files is hard in android 10
any way to do that?
(and in magisk log it says that unlock failed with error 13 permission denied)

Rediancool said:
i can not edit system files from any root explorer
or move files in root with pbrp file manager. any suggestions?
several forum post suggested that editing system files is hard in android 10
any way to do that?
(and in magisk log it says that unlock failed with error 13 permission denied)
Click to expand...
Click to collapse
You can't modify system in recovery because of dynamic partition

[/QUOTE]
Rediancool said:
i can not edit system files from any root explorer
or move files in root with pbrp file manager. any suggestions?
several forum post suggested that editing system files is hard in android 10
any way to do that?
(and in magisk log it says that unlock failed with error 13 permission denied)
Click to expand...
Click to collapse
Try this way

Wooww!! It worked fine for me... But just to install recovery. I can't root with magisk. No with 21.2 or 21.4 versions, cause the phone goes into bootloop.
No way with supersu.
I'm in MIUI 12.0.10.0 QCDEUXM
Is there anybody who can help me, please?

t's sad, but it doesn't feel pressed . the touchscreen doesn't work(

wanlus said:
Wooww!! It worked fine for me... But just to install recovery. I can't root with magisk. No with 21.2 or 21.4 versions, cause the phone goes into bootloop.
No way with supersu.
I'm in MIUI 12.0.10.0 QCDEUXM
Is there anybody who can help me, please?
Click to expand...
Click to collapse
you have to flash vbmeta to avoid bootloop
fastboot flash vbmeta vbmeta.img
Gofile - Free Unlimited File Sharing and Storage
Gofile is a free, secure file sharing and storage platform. With unlimited bandwidth and storage, you can easily store and share files of any type without any limits. Our advanced features, such as CDN support and password protection, make Gofile the ideal choice for individuals and businesses...
gofile.io

[RECOVERY][UNOFFICIAL] TWRP for Galaxy Tab S7/S7+ Series (Snapdragon)

{
"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 Tab S7+ T978U, T978U1 and T978W.
Galaxy Tab S7 T878U, T878U1 and T878W.
US/Canada bootloader unlock thread:
here
Download & Guide:
1. Unlock your bootloader.
2. Download Tab S7+ 5G: gts7xl.
3. Reboot to download mode and flash vbmeta_disabled.tar in AP slot and reboot. Device will reboot to stock 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.
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.​7. Go back to Wipe > Format Data > type yes.
8. Reboot to recovery.
9. Flash magisk apk in twrp.
10. Reboot to system, Enjoy.
Note:
To disable encryption manually:
You need to replace fileencryption=ice with encryptable=ice only in userdata line (maybe rest lines) in vendor/etc/fstab.qcom
To avoid stock recovery restoration manually:
Rename system/recovery-from-boot.p to recovery-from-boot.p.bak
Click to expand...
Click to collapse
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
ianmacd for multidisabler and kernel commits
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
- Fix haptic feedback
28.07.2021 - Initial Release.

Amazing!! will try asap!

Any news bout T870/T875 development?

tabs s7 sm-t875 twrp please

I have posted a test build for the T870 here:
TWRP for the Samsung Galaxy Tab S7+ 5G (T976B)
I'm stuck in TWRP loop with the new T970XXU1ATK3 firmware won't boot to system after the update. Is there anyway to fix this issue?
forum.xda-developers.com
Please let me know if it works for you.

Good morning sir is good for tab s7+ sm-t975? tanks in adcance

Marx71 said:
Good morning sir is good for tab s7+ sm-t975? tanks in adcance
Click to expand...
Click to collapse
You can test, but make full backup and know how to recover soft brick by reflashing stock recovery/firmware.

tank you. But recover soft brick possible whit fastboot?

No, samsung disabled fastboot by default.

If I don't care about flashing in TWRP (yet) can I just flash recovery and see it running? (Basically is the wipe data optional)

parkerlreed said:
If I don't care about flashing in TWRP (yet) can I just flash recovery and see it running? (Basically is the wipe data optional)
Click to expand...
Click to collapse
Flashing vbmeta disable will wipe data

I have SM-T870, After point #4, its just in the loop. Cannot get to recovery.

To clarify, US tab s7+ (SM-T970N) snapdragon requires the paid token unlock before this can be flashed?

gpz1100 said:
To clarify, US tab s7+ (SM-T970N) snapdragon requires the paid token unlock before this can be flashed?
Click to expand...
Click to collapse
No, T970N is Korean not US!

tyracz said:
I have SM-T870, After point #4, its just in the loop. Cannot get to recovery.
Click to expand...
Click to collapse
If it doesn't boot on T870 then its not supported.

afaneh92 said:
No, T970N is Korean not US!
Click to expand...
Click to collapse
Hmm.. Costco has it wrong?
https://www.costco.com/samsung-galaxy-12.4%22-tab-s7%2b-128gb---mystic-black---includes-keyboard.product.100684979.html

afaneh92 said:
If it doesn't boot on T870 then its not supported.
Click to expand...
Click to collapse
I have rooted my SM-T870 by inserting Magisk into AP file and flashing it with odin. Only problem is that now i have in magisk A/B - NO. Which means my partitions are not flashed. I run into problems trying to execute some root programs where they crash since they dont have access to both partitions. Is there any way to root partition A/B?

tyracz said:
I have rooted my SM-T870 by inserting Magisk into AP file and flashing it with odin. Only problem is that now i have in magisk A/B - NO. Which means my partitions are not flashed. I run into problems trying to execute some root programs where they crash since they dont have access to both partitions. Is there any way to root partition A/B?
Click to expand...
Click to collapse
our device is not A/B its A only

afaneh92 said:
our device is not A/B its A only
Click to expand...
Click to collapse
Thank you for answer. If I root SM-T870 with Magisk via AP insert, is this considered full root ? or is this root like partial?