Database Develop

[RMX206X][RECOVERY] Pitch Black 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:
/*
*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: Realme 6 Pro(RMX2061/2063)
Authors build: @ishu88
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/PitchBlackRecoveryProject/android_device_realme_RMX2061-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
Disable DM Verity
Use AromaFM as default file manager
Various tools are included
Universal flash-able file for all variant of a device
Many bug fixes ,optimization & much more
Click to expand...
Click to collapse
Installation Instructions
WARNING
If you are flashing this recovery for the first time /or/ If you are flashing this after installing the stock ROM,
You will get a "Current Image Destroyed Error".
To fix it, Just flash the original vbmeta.img extracted from the ozip file of current realmeui ROM and flash it in fastboot mode by disabling Verity.
Fastboot code to flash vbmeta below
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Flashing 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 fastboot flash recovery.img
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
Changelog
PBRP Side Changelog
Code:
v3.0.0
- Fully Redesigned UI
- Added new Keychecks While Flashing PBRP or recovery.img or Ramdisk
- Fully Redesigned Website https://pitchblackrecovery.com
- New Android like Power Menu (Activated via power key hold)
- Flashlight toggled by Vol up(+) on hold
- New Scrollable Advanced menu
- Totally Redesigned Icons
- Removed old unnecessary Theming Stuff
- Tested on almost all handy Resolutions
- Flashlight toggle on Lockscreen
- More checks for SAR/Non-SAR
- New Navbar
- Support on almost all Android version (5.0+)
- Update ozip decrypt
- Fix up ozip print logs & take all paths
- Update FUNDING.yml
- Fixed encrypted removal checks & buttons
- Add Flag for disabling treble compatibility by default
- Is_Data_Wiped: Simplify function signature
- Unified AB_OTA_UPDATER
- Change AB device log storage to /data/recovery
- Delay start if specified in board
- Optimize touchscreen driver initialization delay.
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Device Side Changelog
Code:
initial build
Bugs
- Stock ROM Ozip flashing error (use twrp for now)
- Flashlight not working
- MTP only works for SD card
Downloads
Flashable zip
https://drive.google.com/file/d/14BgBiKlfMXnKRwBp5YZh2g0N85gm6sJY/view?usp=drivesdk
XDA:DevDB Information
Pitch Black Recovery Project, Tool/Utility for the Realme 6 Pro
Contributors
Kevin Saiza, ishu88
Version Information
Status: Testing
Created 2020-08-19
Last Updated 2020-08-19

Screenshots
Take a look what pbrp offers

Reserved 2

wow thank you friend & hope to fix all problems asap
all support to your work

do you need a patcheed vbmeta to installl this fresh to a bootloader unlocked 6 pro? Im very new sorry if this is a obvious answer.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Okay so i just straight up flashed the recovery image and yep theres something else you need to make it work. Probably refer to the TWRP guide in this same device forum to figure it out.
Thanks for your work, now i have a phone to fix lol not complaining tho! i might be able to get my android skills up!

SKELEKINETIC said:
Okay so i just straight up flashed the recovery image and yep theres something else you need to make it work. Probably refer to the TWRP guide in this same device forum to figure it out.
Thanks for your work, now i have a phone to fix lol not complaining tho! i might be able to get my android skills up!
Click to expand...
Click to collapse
Just flash the original vbmeta extracted from the ozip file of current stock ROM and flash it in fastboot mode by disabling Verity
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

Kevin Saiza said:
Up-to-date kernel, built from sources
Click to expand...
Click to collapse
Can you share how you got the 6 pro kernel compiling, and most of all, running?

Kevin Saiza said:
Just flash the original vbmeta extracted from the ozip file of current stock ROM and flash it in fastboot mode by disabling Verity
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Why the above command gives me the error as below?
--------------------------------------------------------------
PS C:\Users\Administrator\Desktop\platform-tools> fastboot devices
eaaf29e6 fastboot
PS C:\Users\Administrator\Desktop\platform-tools> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
C:\adb\fastboot.exe: unknown option -- disable-verity
PS C:\Users\Administrator\Desktop\platform-tools>
--------------------------------------------------------------

neoxcool said:
Just flash the original vbmeta extracted from the ozip file of current stock ROM and flash it in fastboot mode by disabling Verity
Why the above command gives me the error as below?
--------------------------------------------------------------
PS C:\Users\Administrator\Desktop\platform-tools> fastboot devices
eaaf29e6 fastboot
PS C:\Users\Administrator\Desktop\platform-tools> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
C:\adb\fastboot.exe: unknown option -- disable-verity
PS C:\Users\Administrator\Desktop\platform-tools>
--------------------------------------------------------------
Click to expand...
Click to collapse
Try to use latest version of minimal adb and fastboot , and , platform tools

Do you have twrp 3.4 built for this device? Or does nullexceptiosn 3.3 work to flash stock ozips?

Kevin Saiza said:
Just flash the original vbmeta extracted from the ozip file of current stock ROM and flash it in fastboot mode by disabling Verity
Click to expand...
Click to collapse
Thank you. Where can I learn more about "dm-verity" and vbmeta? They are anti tamper protection right? W

I know xda really isnt for noob but a step by step with prerequisites would be amazing. currently i cant get FBE to work.

Pitchblacl no longer decrypts internal storage!

neoxcool said:
Just flash the original vbmeta extracted from the ozip file of current stock ROM and flash it in fastboot mode by disabling Verity
Why the above command gives me the error as below?
--------------------------------------------------------------
PS C:\Users\Administrator\Desktop\platform-tools> fastboot devices
eaaf29e6 fastboot
PS C:\Users\Administrator\Desktop\platform-tools> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
C:\adb\fastboot.exe: unknown option -- disable-verity
PS C:\Users\Administrator\Desktop\platform-tools>
--------------------------------------------------------------
Click to expand...
Click to collapse
I had the same issues with the commands, even after updating my Fastboot, and for some reason, they worked fine in Command Prompt, instead of Powershell, give it a try!!

Link doesnt work. google says the file is in the owners trash

SKELEKINETIC said:
Link doesnt work. google says the file is in the owners trash
Click to expand...
Click to collapse
It works

SKELEKINETIC said:
Do you have twrp 3.4 built for this device? Or does nullexceptiosn 3.3 work to flash stock ozips?
Click to expand...
Click to collapse
To flash stock ozip,use twrp only

I couldn't download this L.R. TWRP from russian site pda. Does anyone have this file (LR.TWRP-3.4.2b_RMX2061.img)?

It looks to be incompatible with the latest firmware, A.33. I'm going to downgrade and see if PBRP works with A.31. It did work before I upgraded to A.33.

I was able to make it work after I downgraded to A.17 but it broke the moment I flashed anything to do with the system partition.

[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

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

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

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

Reserved

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[RECOVERY][OFFICIAL]PitchBlack Recovery v3.1.0 [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"
}
Click to expand...
Click to collapse
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 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.
*/
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.5.2
- PitchBlack version: 3.1.0
- Maintainer: Nazim @naz664
- For device: M21/M215f
- PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject/manifest_pb
- Device tree: https://github.com/PitchBlackRecoveryProject/android_device_samsung_m21-pbrp
- Kernel tree:
https://github.com/naz664/android_kernel_samsung_m21
- PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
- Fully native android like UI
- Up-to-date kernel, built from sources
- Full dark theme with changeable accents
- Reorganized menus
- Disable DM Verity
- Use AromaFM as default file manager
- Various tools are included
- Many bug fixes & optimization & much more
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
- After installation reboot the recovery
- Enjoy
* If you are getting vbmeta error flash null vbmeta
From PC
- Download PitchBlack Recovery flashable zip from bellow
- Extract the PBRP zip
- Tar the recovery file and flash via odin in Ap block
- Enjoy
changelog
PBRP Side Changelog
Code:
v3.1.0
- Bump to 3.1.0
- Based on TWRP 3.5.1
- Redesigned homescreen
- Fixed minor glitches
- Added more languages support
Device Side Changelog
Code:
- Initial release
- Added support to directly flash images in logical partition
- Added dtbo,vbmeta partition backup and restore support
- Disabled dm verity by default
- Fixed MTP
- Fixed flashlight
Credits:
- @Yilliee for the base tree
- @Chaitanya_Yeranagula and PBRP team for all your help
- And all the testers for their reports
Downloads
Samsung Galaxy M21 | m21 - PitchBlack Recovery Project
PBRP Version: 3.1.0 Maintainer: Nazim
pitchblackrecovery.com

Nice job!!

Awesome work dev!

Clutchmaster_OP said:
Nice job!!
Click to expand...
Click to collapse
Thankz bro

Daniel~007 said:
Awesome work dev!
Click to expand...
Click to collapse
Thankz

Tried to flash (both trough TWRP & Tar file flash) but booting into Download Mode only. Its for M21/M215F, is that why its not working on M215G?
Its showing some red error msg like Custom Binary Invalid & vbmeta, something like that.

OldNoobOne said:
Tried to flash (both trough TWRP & Tar file flash) but booting into Download Mode only. Its for M21/M215F, is that why its not working on M215G?
Its showing some red error msg like Custom Binary Invalid & vbmeta, something like that.
Click to expand...
Click to collapse
Try flashing null vbmeta via Ap block of odin

naz664 said:
Try flashing null vbmeta via Ap block of odin
Click to expand...
Click to collapse
Same error repeats :
ODIN MODDE (AVB Fail)
recovery: Error verifying vbmeta image: invalid vbmeta header (6)
I even tried flashing another vbmeta zip file (906kb) which had worked before during flashing GSI but even after that I got same error.

OldNoobOne said:
Same error repeats :
ODIN MODDE (AVB Fail)
recovery: Error verifying vbmeta image: invalid vbmeta header (6)
I even tried flashing another vbmeta zip file (906kb) which had worked before during flashing GSI but even after that I got same error.
Click to expand...
Click to collapse
Flashing gsi doesn't need null vbmeta.
* Extract the zip
* Flash recovery.img into recovery partition using any other recovery
* And check if ure getting vb meta error or not
If yes try flashing the vbmeta file i attached before
* If the problem still persist contact me on telegram @naz664

naz664 said:
Flashing gsi doesn't need null vbmeta.
* Extract the zip
* Flash recovery.img into recovery partition using any other recovery
* And check if ure getting vb meta error or not
If yes try flashing the vbmeta file i attached before
* If the problem still persist contact me on telegram @naz664
Click to expand...
Click to collapse
1) Actually null vbmeta was the issue I was facing on SM-M215G (while flashing GSI) and as per Dev GuruPrasadAH, he gave me null vbmeta file which solved the problem and after that GSI booted.
2) I already had done that, when i had flashed recovery img to recovery partition, same error was showing.
3) Now the phone only boots to download mode, so I think I should flash stock ROM again.

OldNoobOne said:
1) Actually null vbmeta was the issue I was facing on SM-M215G (while flashing GSI) and as per Dev GuruPrasadAH, he gave me null vbmeta file which solved the problem and after that GSI booted.
2) I already had done that, when i had flashed recovery img to recovery partition, same error was showing.
3) Now the phone only boots to download mode, so I think I should flash stock ROM again.
Click to expand...
Click to collapse
Ok may be it will only work on M215f (2020 edition)
If you have any more queries contact me on telegram @naz664

Okay.... Here I am! I'm the kid who gave OldNoob the null vbmeta. So here, I dont think the problem is the vbmeta. Ive only seen this happen when either the devicetree/kernel is mucked up. SO, I have two suggestions:
1. @naz664 can you rebuild with universal9611 tree and kernel like used in this one: https://forum.xda-developers.com/t/...y-project-unified-r11-1-m21-m21s-f41.4252089/
2. Can someone share boot.img of m215g(not m215f). its really simple - just execute the following (from pc with adb installed) while in recovery mode:
Code:
adb shell dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
And attach it to ur reply. Ill fix and post (possibly) fixed recovery image.
Chill
GuruPrasadAH

GuruPrasadAH said:
Okay.... Here I am! I'm the kid who gave OldNoob the null vbmeta. So here, I dont think the problem is the vbmeta. Ive only seen this happen when either the devicetree/kernel is mucked up. SO, I have two suggestions:
1. @naz664 can you rebuild with universal9611 tree and kernel like used in this one: https://forum.xda-developers.com/t/...y-project-unified-r11-1-m21-m21s-f41.4252089/
2. Can someone share boot.img of m215g(not m215f). its really simple - just execute the following (from pc with adb installed) while in recovery mode:
Code:
adb shell dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
And attach it to ur reply. Ill fix and post (possibly) fixed recovery image.
Chill
Click to expand...
Click to collapse
GuruPrasadAH said:
Okay.... Here I am! I'm the kid who gave OldNoob the null vbmeta. So here, I dont think the problem is the vbmeta. Ive only seen this happen when either the devicetree/kernel is mucked up. SO, I have two suggestions:
1. @naz664 can you rebuild with universal9611 tree and kernel like used in this one: https://forum.xda-developers.com/t/...y-project-unified-r11-1-m21-m21s-f41.4252089/
2. Can someone share boot.img of m215g(not m215f). its really simple - just execute the following (from pc with adb installed) while in recovery mode:
Code:
adb shell dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
And attach it to ur reply. Ill fix and post (possibly) fixed recovery image.
Chill
GuruPrasadAH
Click to expand...
Click to collapse
Does that recovery working for you ?

naz664 said:
Does that recovery working for you ?
Click to expand...
Click to collapse
As stupid as this may sound, I dont have the phone anymore. Upgraded to redmi note 10 pro max. But, I do have some experience and can help out after honework and classwork.
I'm not a leech who spampings for eta lol

GuruPrasadAH said:
As stupid as this may sound, I dont have the phone anymore. Upgraded to redmi note 10 pro max. But, I do have some experience and can help out after honework and classwork.
I'm not a leech who spampings for eta lol
Click to expand...
Click to collapse
Ooh kk can anyone confirm that ?

naz664 said:
Ok may be it will only work on M215f (2020 edition)
If you have any more queries contact me on telegram @naz664
Click to expand...
Click to collapse
Thanks no problem naz664

GuruPrasadAH said:
Okay.... Here I am! I'm the kid who gave OldNoob the null vbmeta. So here, I dont think the problem is the vbmeta. Ive only seen this happen when either the devicetree/kernel is mucked up. SO, I have two suggestions:
1. @naz664 can you rebuild with universal9611 tree and kernel like used in this one: https://forum.xda-developers.com/t/...y-project-unified-r11-1-m21-m21s-f41.4252089/
2. Can someone share boot.img of m215g(not m215f). its really simple - just execute the following (from pc with adb installed) while in recovery mode:
Code:
adb shell dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
And attach it to ur reply. Ill fix and post (possibly) fixed recovery image.
Chill
GuruPrasadAH
Click to expand...
Click to collapse
Oh Dev GuruPrasadAH, nice to meet you again
My phone only booting to Download Mode , so after I restore from backup I will have ADB access again then i'll run the above command and paste it here.

OldNoobOne said:
Thanks no problem naz664
Click to expand...
Click to collapse
Unified orangefox recovery for exynoss9611 working for you ?

naz664 said:
Unified orangefox recovery for exynoss9611 working for you ?
Click to expand...
Click to collapse
OFox Beta didnt work, so I went back to Soulr344 TWRP; Honestly speaking TWRP isnt that bad

OldNoobOne said:
OFox Beta didnt work, so I went back to Soulr344 TWRP; Honestly speaking TWRP isnt that bad
Click to expand...
Click to collapse
Ok thankz for the report.
I used ofox tree as base if it didn't boot then no hope for this one too lol

Development [RECOVERY] [Realme8 Pro] [TWRP 3.7.0] [RMX3081] [12-0] [UNOFFICIAL] TeamWin Recovery - Initial release

{
"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!!!
*
* If sh!t happens, i am not responsible for your bricked device.
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications,
* Do at your own risk!!!
*/
Team Win Recovery Project 3.7.0 for Realme 8 Pro​Introduction:​ Team Win Recovery Project, 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.
Version and device Information:​
Status - Stable, (Initial build)
Based on TWRP version: 3.7.0
Device: RMX3081 aka Realme 8 Pro
Android version: RealmeUI 3 (Android 12+)
Release Date: December 14, 2022
Last Updated: January 03, 2023
Maintainer: Shibu Shaji, (perilouspike)
Source:​Minimal manifest: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp​Device tree:
GitHub - perilouspike/android_device_realme_RMX3081_twrp: TWRP device tree for Realme 8 pro
TWRP device tree for Realme 8 pro. Contribute to perilouspike/android_device_realme_RMX3081_twrp development by creating an account on GitHub.
github.com
Installation:
1.Disable verified boot first (optional)
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
'Which is extracted from current stock rom ozip file.'
2. Flash twrp build
Code:
fastboot flash recovery [image name].img
3. Reboot to recovery
Code:
fastboot reboot recovery
List of features working:
• Support DECRYPTION for Android 12 (tested and works with stock firmware and some available GSI roms)
• External SD-card & USB-OTG support.
• Successful installation of flashable zips. "magisk" (Custom rom not tested as it is not available now)
• Additional features such as close AVB2.0. (disabled-verify on vbmeta)
• Working mounting of dynamic partitions. (r/o only)
• Fully functional backup/restore of all partitions.
• Adb sideoad
• Fully functional adb and fastboot in twrp.
Features not working:
-Tell meh
Note:
• If you got 'unable to mount /data' error or Bootloop after flashing a ROM or having done a Format Data do the below
Boot to bootloader and:
Code:
fastboot devices
fastboot -w
fastboot reboot
Changelog:
• Changed StatusBar icon positions
• Fixed some partition issues in Fstab
• Updated sources
Click to expand...
Click to collapse
Download:
TWRP-12.1_Realme-8-pro_RMX3081-Unofficial.img
CREDITS:
• TeamWin - for TWRP
• @carlodeeCrypton - Special thanks for his effort to make data decryption to work.
#Flash and enjoy
Spoiler: screenshots
[/]

Great work!

It works on the rodo version ?

siksu said:
It works on the rodo version ?
Click to expand...
Click to collapse
GDPR ? I think, currently only the EXPORT version can unlock the bootloader. it can be installed if you have unlocked it

Shibu Shaji said:
RODO ? Myślę, że obecnie tylko wersja EXPORT może odblokować program ładujący. można go zainstalować, jeśli go odblokowałeś
Click to expand...
Click to collapse
Czy można jakoś zainstalować wersję eksportową? Takie duże ograniczenie tylko ze względu na wersję oprogramowania

great

Shibu Shaji said:
View attachment 5784327​
Code:
/*
* Your warranty is now void!!!
*
* If sh!t happens, i am not responsible for your bricked device.
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications,
* Do at your own risk!!!
*/
Team Win Recovery Project 3.7.0 for Realme 8 Pro​Introduction:​ Team Win Recovery Project, 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.
Version and device Information:​
Status - Stable, (Initial build)
Based on TWRP version: 3.7.0
Device: RMX3081 aka Realme 8 Pro
Android version: RealmeUI 3 (Android 12+)
Release Date: December 14, 2022
Last Updated: January 03, 2023
Maintainer: Shibu Shaji, (perilouspike)
Source:​Minimal manifest: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp​Device tree:
GitHub - perilouspike/android_device_realme_RMX3081_twrp: TWRP device tree for Realme 8 pro
TWRP device tree for Realme 8 pro. Contribute to perilouspike/android_device_realme_RMX3081_twrp development by creating an account on GitHub.
github.com
Installation:
1.Disable verified boot first (optional)
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
'Which is extracted from current stock rom ozip file.'
2. Flash twrp build
Code:
fastboot flash recovery [image name].img
3. Reboot to recovery
Code:
fastboot reboot recovery
List of features working:
• Support DECRYPTION for Android 12 (tested and works with stock firmware and some available GSI roms)
• External SD-card & USB-OTG support.
• Successful installation of flashable zips. "magisk" (Custom rom not tested as it is not available now)
• Additional features such as close AVB2.0. (disabled-verify on vbmeta)
• Working mounting of dynamic partitions. (r/o only)
• Fully functional backup/restore of all partitions.
• Adb sideoad
• Fully functional adb and fastboot in twrp.
Features not working:
-Tell meh
Note:
• If you got 'unable to mount /data' error or Bootloop after flashing a ROM or having done a Format Data do the below
Boot to bootloader and:
Code:
fastboot devices
fastboot -w
fastboot reboot
Changelog:
Download:
TWRP-12.1_Realme-8-pro_RMX3081-Unofficial.img
CREDITS:
• TeamWin - for TWRP
• @carlodeeCrypton - Special thanks for his effort to make data decryption to work.
#Flash and enjoy
Spoiler: screenshots
[/View attachment 5784423View attachment 5784335View attachment 5784337View attachment 5784339View attachment 5784341View attachment 5784343View attachment 5784345View attachment 5784347View attachment 5784349View attachment 5784353View attachment 5784355]
Click to expand...
Click to collapse
Hello Brother,
Are there any plans to start custom ROM development?
Or make a tree?

I installed this recovery on realme 8 Pro running android 13 with UI 4. It installed without any errors and decrypted file system on first run from fastboot. But after booting the phone in to OS and rebooting, it went into realme system recovery (Power+Vol down) everytime. I followed the process of installing TWRP as mentioned above. What can be done to prevent stock recovery from overwriting TWRP?

kgpabhi said:
I installed this recovery on realme 8 Pro running android 13 with UI 4. It installed without any errors and decrypted file system on first run from fastboot. But after booting the phone in to OS and rebooting, it went into realme system recovery (Power+Vol down) everytime. I followed the process of installing TWRP as mentioned above. What can be done to prevent stock recovery from overwriting TWRP?
Click to expand...
Click to collapse
Immediately after installing the recovery, you need to install something, so the recovery will not be reset

kakalkin said:
Immediately after installing the recovery, you need to install something, so the recovery will not be reset
Click to expand...
Click to collapse
I checked that in a post for realme 3 TWRP installation.
https://forum.xda-developers.com/t/twrp-for-realme-3-working-updated-21-aug-2019.3944022/
Edit (solution): After flashing a custom recovery, always flash a custom kernel or root.

Hey are you able to install any gsi using this recovery?

No, can't install gsi via twrp, need to use Fastboot.