{
"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.5.1
PitchBlack version: 3.1.0
For device: a7y18lte
Authors build: itmr
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/itamar567/android_device_samsung_a7y18lte
Kernel: https://github.com/devkingsteam/android_kernel_samsung_universal7885/tree/android-8.1
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
ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto download mode in your device
Flash the recovery.img by heimdall flash --RECOVERY recovery.img
Boot into PBRP
Copy the zip to internal storage/sdcard
Flash it
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
Bugs
- Decryption doesn't work
- Flashlight
- Some people are experiencing black lines, expect a fix soon
- You tell me!
Downloads
Flashable zip
https://www.androidfilehost.com/?fid=14943124697586335986
itmr said:
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.5.1
PitchBlack version: 3.1.0
For device: a7y18lte
Authors build: itmr
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/itamar567/android_device_samsung_a7y18lte
Kernel: https://github.com/devkingsteam/android_kernel_samsung_universal7885/tree/android-8.1
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
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
ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto download mode in your device
Flash the recovery.img by heimdall flash --RECOVERY recovery.img
Boot into PBRP
Copy the zip to internal storage/sdcard
Flash it
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
Bugs
- Decryption doesn't work
- You tell me!
Downloads
Flashable zip
https://www.androidfilehost.com/?fid=14943124697586335986
Click to expand...
Click to collapse
This PBRP works fine on my TREBLE supported A7 2018 (sm-a750f/ds).
I tested this out. Only thing that doesn't seem to work is the flashlight but that's not a big deal
otherwise this recovery works flawlessly
For anyone wanting to flash this recovery!
You might want to downgrade to the stock November 2020 Security Patch while it's still allowed. As the newest Patch presents you with bootloops and black lines when flashing
edit:
device used A750FN
Dark8812 said:
I tested this out. Only thing that doesn't seem to work is the flashlight but that's not a big deal
otherwise this recovery works flawlessly
For anyone wanting to flash this recovery!
You might want to downgrade to the stock November 2020 Security Patch while it's still allowed. As the newest Patch presents you with bootloops and black lines when flashing
edit:
device used A750FN
Click to expand...
Click to collapse
Didn't know you can activate flashlight in PBRP, so I didn't notice the issue. I'll try to fix it
About the black lines, I had black lines with ashyx's TWRP and that's why I made this release.
I don't have black lines, but I think that I know how to solve this issue.
Expect an update today/tomorrow
Since this release is based on android 8, I thought that moving to android 10 would fix the black lines.
But I had problems with compiling PBRP on android 10. I will try it again later, but until then I made a release using latest kernel and android 8.
Can you tell me if this image boots for you on latest security patch?
kernel source: A750FNPUS5CTI1 kernel from Samsung opensource
download zip
NOTE: I noticed that adb shell doesn't work, but all other adb commands work (don't worry, normal terminal works). I will try to fix this and the flashlight in the next release.
itmr said:
Since this release is based on android 8, I thought that moving to android 10 would fix the black lines.
But I had problems with compiling PBRP on android 10. I will try it again later, but until then I made a release using latest kernel and android 8.
Can you tell me if this image boots for you on latest security patch?
kernel source: A750FNPUS5CTI1 kernel from Samsung opensource
download zip
NOTE: I noticed that adb shell doesn't work, but all other adb commands work (don't worry, normal terminal works). I will try to fix this and the flashlight in the next release.
Click to expand...
Click to collapse
I initially installed it on the latest DBT patch
A750FNXXS5CUC2 it booted fine however when flashing it rebooted into the recovery and it showed black lines in the meantime
Edit: I will try the updated version now I misread your request the first time
Dark8812 said:
Edit: I will try the updated version now I misread your request the first time
Click to expand...
Click to collapse
I can't seem to flash it using the newest firmware
If you are on Windows:
Flash this using Odin3.
If you are on Linux/Mac:
install heimdall
unzip the installer, open the terminal in the extracted folder and run:
Code:
heimdall flash --RECOVERY TWRP/recovery.img
itmr said:
If you are on Windows:
Flash this using Odin3.
If you are on Linux/Mac:
install heimdall
unzip the installer, open the terminal in the extracted folder and run:
Code:
heimdall flash --RECOVERY TWRP/recovery.img
Click to expand...
Click to collapse
It seems like there is a misunderstanding. I am able to flash the recovery and I had it for a few days now. However I need to first downgrade to bootloader version 5 of this phone (Security Patch 1st November 2020). For the recovery to work correctly. As the newest version shows black lines and restarts the phone when flashing a file in the recovery. Another thing is I can't flash the file you gave me for odin.
It gives this error:
Code:
ID0008 engine v(ID3.1401)
ID0008 File analysis..
ID0008 FAIL! LZ4 is invalid
OSM All threads completed. (succeed 0 failed 1)
Further if you flash it with an already existing recovery you get this error:
Code:
Could not do normal boot. Invalid KERNEL LENGHT!
I instead found a workaround and used the one found in the heimdall archive, I extracted the recovery.img file and added it to a new archive named recovery.tar. This is flashable trough odin and successfully installs the recovery
Dark8812 said:
Another thing is I can't flash the file you gave me for odin.
It gives this error:
Code:
ID0008 engine v(ID3.1401)
ID0008 File analysis..
ID0008 FAIL! LZ4 is invalid
OSM All threads completed. (succeed 0 failed 1)
Further if you flash it with an already existing recovery you get this error:
Code:
Could not do normal boot. Invalid KERNEL LENGHT!
Click to expand...
Click to collapse
Sorry about that, I didn't pack the recovery correctly for odin.
Dark8812 said:
I instead found a workaround and used the one found in the heimdall archive, I extracted the recovery.img file and added it to a new archive named recovery.tar. This is flashable trough odin and successfully installs the recovery
Click to expand...
Click to collapse
Glad you got it to work! Again, sorry!
If you upgrade the firmware to the latest security patch, can you boot this version of PBRP successfully without black lines?
itmr said:
Sorry about that, I didn't pack the recovery correctly for odin.
Glad you got it to work! Again, sorry!
If you upgrade the firmware to the latest security patch, can you boot this version of PBRP successfully without black lines?
Click to expand...
Click to collapse
On the latest security patch the recovery doesn't work that great. As I said before it restarts the phone into the recovery when flashing and also with certain compatible files it shows black lines when flashing them.
I can't flash it using TWRP. just stuck. Is it okay to flash it using TWRP image install? I'll just extract the zip and get the recovery.img
Hello, sorry I didn't answer for some time.
Dark8812 said:
On the latest security patch the recovery doesn't work that great. As I said before it restarts the phone into the recovery when flashing and also with certain compatible files it shows black lines when flashing them.
Click to expand...
Click to collapse
I made a new build with an extracted kernel from latest security patch (A750FNXXU5CUD3). Can you tell if it works?
kernel source should be in samsung opensource
download
xxfDeadStar88x said:
I can't flash it using TWRP. just stuck. Is it okay to flash it using TWRP image install? I'll just extract the zip and get the recovery.img
Click to expand...
Click to collapse
It seems that also other devices have the same issue. Yes, flashing using TWRP image install will work. I also suggest you to copy the zip files from PBRP/tools to /sdcard/PBRP/tools.
itmr said:
Hello, sorry I didn't answer for some time.
I made a new build with an extracted kernel from latest security patch (A750FNXXU5CUD3). Can you tell if it works?
kernel source should be in samsung opensource
download
It seems that also other devices have the same issue. Yes, flashing using TWRP image install will work. I also suggest you to copy the zip files from PBRP/tools to /sdcard/PBRP/tools.
Click to expand...
Click to collapse
Thanks bro! It works absolutely fine on my SM-A750GN/DS device. Thanks for this wonderful recovery!
Hello guys, i am a new XDA member and i have troubles rooting my samsung galaxy a7 2018 with april 2021 security patch, i find this new recovery but i didn't understand this point
Flash the recovery.img by heimdall flash --RECOVERY recovery.img
what i have to do after extract my PBRB ZIP?
Chris7897 said:
Hello guys, i am a new XDA member and i have troubles rooting my samsung galaxy a7 2018 with april 2021 security patch, i find this new recovery but i didn't understand this point
Flash the recovery.img by heimdall flash --RECOVERY recovery.img
what i have to do after extract my PBRB ZIP?
Click to expand...
Click to collapse
If you use GNU+Linux/Mac, install heimdall (https://glassechidna.com.au/heimdall/) and run heimdall flash --RECOVERY recovery.img
If you use Windows, compress recovery.img to a tar archive and flash the tar archive in odin AP slot
itmr said:
If you use GNU+Linux/Mac, install heimdall (https://glassechidna.com.au/heimdall/) and run heimdall flash --RECOVERY recovery.img
If you use Windows, compress recovery.img to a tar archive and flash the tar archive in odin AP slot
Click to expand...
Click to collapse
With 7zip? I tried as you said but when i boot into Pbrp, screen goes black and my phone was blocked
For those who flash through Odin3, I'll leave a link to the .tar file with recovery. It would be nice if the author added a link to this file and a manual to odin3.
Download recovery.tar
(Sorry if my English is bad, unfortunately I don't know him well)
itmr said:
Hello, sorry I didn't answer for some time.
I made a new build with an extracted kernel from latest security patch (A750FNXXU5CUD3). Can you tell if it works?
kernel source should be in samsung opensource
download
Click to expand...
Click to collapse
Blank screen (like switched off phone) on my SM-A750F/DS after flashing, running on A750FXXU5CUD3.
Found hard time to access download mode to recover.
Even Orangefox SAR behaved same with this ROM update.
But, previous PBRP worked at least. However, setting lockscreen with password or fingerprint kept rebooting in a loop until flashed rmpass.zip.
drbsin said:
Blank screen (like switched off phone) on my SM-A750F/DS after flashing, running on A750FXXU5CUD3.
Found hard time to access download mode to recover.
Even Orangefox SAR behaved same with this ROM update.
But, previous PBRP worked at least. However, setting lockscreen with password or fingerprint kept rebooting in a loop until flashed rmpass.zip.
Click to expand...
Click to collapse
have you tried format data? data partition will be corrupted after you flash the custom recovery. format data first before doing anything else.
Related
{
"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.3.1
PitchBlack version: 2.9.0
For device: onclite
Maintainer/Authors build: Ashu Sharma
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/PitchBlackRecoveryProject/android-device-xiaomi-onclite-pbrp
PitchBlack Team: @rezaadi0105, @firewolfxda, @manjot.gni, @androiabledroid, Arbaz Khan
Features
Supports Treble and non-Treble ROMs
Up-to-date Oreo kernel, built from sources (Pie is on the way)
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 Fastboot
Extract the Downoaded zip file
Grab the recovery.img from extracted folder
Reboot device in fastboot
Run "fastboot flash recovery recovery.img" from fastboot
Boot into recovery
Changelog
Code:
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Downloads
Flashable zip
PitchBlack-onclite-2.9.0-20190624-0606-OFFICIAL
Post Installation Instructions
BACKUP YOUR Boot.img BEFORE DOING THIS
To decrypt data:
1. Backup Boot.img
2. Wipe data and flash patched boot.img by magisk or Magisk zip file (You Can Patch boot.img through magisk app)
3. Reboot
Hit Thanks Button If I Helped You:good:
:laugh::laugh::laugh:
Nice thread, kindly explain the process of patching the the boot.IMG
And will I be able to use OTA from notification using this recovery even after I've flashed magisk?
Thanks for your anticipated response
Stephinnoye said:
Nice thread, kindly explain the process of patching the the boot.IMG
And will I be able to use OTA from notification using this recovery even after I've flashed magisk?
Thanks for your anticipated response
Click to expand...
Click to collapse
To patch boot.img
1. Open magisk
2. Click in install and select patch image
3. Find your boot.img
4. Done
5. Boot into recovery, wipe data and flash patched image
To apply OTA:
https://c.mi.com/thread-1782169-1-1.html
ashu7073 said:
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.3.1
PitchBlack version: 2.9.0
For device: onclite
Maintainer/Authors build:Ashu Sharma
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
......
..... . .
... . . .
Post Installation Instructions
BACKUP YOUR Boot.img BEFORE DOING THIS
To decrypt data:
1. Backup Boot.img
2. Wipe data and flash patched boot.img by magisk or Magisk zip file (You Can Patch boot.img through magisk app)
3. Reboot
Click to expand...
Click to collapse
After installing RECOVERY via fastboot, Is it necessary to backup boot image ?
There is no decrypt. Zip to flash after recovery coz i don't want to use magisk to decrypt data ?
[email protected] said:
After installing RECOVERY via fastboot, Is it necessary to backup boot image ?
There is no decrypt. Zip to flash after recovery coz i don't want to use magisk to decrypt data ?
Click to expand...
Click to collapse
Decrypt.zip is included in PitchBlack zip file. You've to flash again zip from any recovery or From Pitchblack to Get decrypt zip and other files which included in PitchBlack recovery zip file
Or you can use this : https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
It is Not Necessary to Backup boot.img after Flashing recovery But it is Recommended to Backup boot.img Before Flashing ForceDecrypt zip, patched boot image or Magisk.
In Case your Device got Stuck in Bootloop after flashing decrypt zip, You can Restore Boot.img.
ashu7073 said:
To patch boot.img
1. Open magisk
2. Click in install and select patch image
3. Find your boot.img
4. Done
5. Boot into recovery, wipe data and flash patched image
To apply OTA:
https://c.mi.com/thread-1782169-1-1.html
Click to expand...
Click to collapse
Thanks bro
But must u patch the boot.IMG? Wats the need for doing that?
All I want is root (using magisk) and a custom recovery
Thanks
---------- Post added at 15:38 ---------- Previous post was at 15:36 ----------
ashu7073 said:
Decrypt.zip is included in PitchBlack zip file. You've to flash again zip from any recovery or From Pitchblack to Get decrypt zip and other files which included in PitchBlack recovery zip file
Or you can use this : https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
It is Not Necessary to Backup boot.img after Flashing recovery But it is Recommended to Backup boot.img Before Flashing ForceDecrypt zip, patched boot image or Magisk.
In Case your Device got Stuck in Bootloop after flashing decrypt zip, You can Restore Boot.img.
Click to expand...
Click to collapse
What is d essence of this decrypt zip of a thing?
Stephinnoye said:
Thanks bro
But must u patch the boot.IMG? Wats the need for doing that?
All I want is root (using magisk) and a custom recovery
Thanks
Click to expand...
Click to collapse
It's optional and alternative to direct magisk zip
It's upto you. Flash magisk or patched image
ashu7073 said:
It's optional and alternative to direct magisk zip
It's upto you. Flash magisk or patched image
Click to expand...
Click to collapse
So once uve this pitch recovery, and I flashed magisk, I'm gud to go?
Thanks
Please help bro
I've pitchblack recovery now,but whenever I boot to recovery,it keep asking me to decrypt data .
I've tried to backup my boot.img but to no avail
Also, whenever I flashed anything,I get this response "unable to mount storage" and recovery can't read my internal storage
Kindly help pls
Thanks in anticipation
Stephinnoye said:
Please help bro
I've pitchblack recovery now,but whenever I boot to recovery,it keep asking me to decrypt data .
I've tried to backup my boot.img but to no avail
Also, whenever I flashed anything,I get this response "unable to mount storage" and recovery can't read my internal storage
Kindly help pls
Thanks in anticipation
Click to expand...
Click to collapse
This is problem in PitchBlack recovery. It can't decrypt data. I'm working on a fix. Untill then you can wipe data in pitchblack once to decrypt it.
Or go back to another recovery
ashu7073 said:
This is problem in PitchBlack recovery. It can't decrypt data. I'm working on a fix. Untill then you can wipe data in pitchblack once to decrypt it.
Or go back to another recovery
Click to expand...
Click to collapse
I've wiped data, but whenever I go-to recovery,it will still ask me to decrypt
And what abt the inability of the recovery to read my internal storage?
I opted in for pitchblack so that I can use OTA (tho I still don't get the procedures to enable me use OTA,but I'm sure u will still put me tru personally,that site seems complicated)
Stephinnoye said:
I've wiped data, but whenever I go-to recovery,it will still ask me to decrypt
And what abt the inability of the recovery to read my internal storage?
Click to expand...
Click to collapse
You've to flash magisk to disable force encryption
Or just flash your stock boot.img, pitchblack automatically disables force encryption
ashu7073 said:
You've to flash magisk to disable force encryption
Or just flash your stock boot.img, pitchblack automatically disables force encryption
Click to expand...
Click to collapse
I've flashed magisk, lemme see if the recovery can read my internal storage now
Modified: still can't read my internal storage
Stephinnoye said:
I've flashed magisk, lemme see if the recovery can read my internal storage now
Modified: still can't read my internal storage
Click to expand...
Click to collapse
Flashing magisk is not going to help with decrypting data. Either your recovery can decrypt, or it can't. If it can't, and you want to remain encrypted, then you will need another recovery which can decrypt. If you don't mind not being encrypted, then you can format your data ("format", not "wipe"). That will obliterate all the contents of your internal storage - so you had better backup all your photos, videos, etc, before formatting data.
For me works the recovery...but pc doesn't recognize device then...
Work in redmi 7 Global EEA
So whats up with this recovery is it usable or not? Can encryption be removed with formatting data? And also does miui ota survival work? I would like to use this recovery with xiaomi eu rom
Immortal0907 said:
So whats up with this recovery is it usable or not? Can encryption be removed with formatting data? And also does miui ota survival work? I would like to use this recovery with xiaomi eu rom
Click to expand...
Click to collapse
Yes, you can
Wipe data and flash any encryption disabler zip
Or patch boot.img with magisk and flash with PB recovery
Pb disables dm-verity so it may cause boot loop on miui. you've disable dm-verity disabler
ashu7073
How Disable Dm-verify method here, automatically or from where?!.
Don`t use this recovery if you are flashing xiaomi.eu rom fingerprint / Pin won`t work no matter what you do use LR Team TWRP.
{
"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.
{
"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
{
"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
{
"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