[RECOVERY][OFFICIAL]PitchBlack Recovery v3.1.0 [m21]

[naz664]

/*
*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

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

- 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

 

[Clutchmaster_OP]

Nice job!!

 

[Daniel~007]

Awesome work dev!

 

[naz664]

Nice job!!

Thankz bro

 

[naz664]

Awesome work dev!

Thankz

 

[OldNoobOne]

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.

 

[naz664]

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.

Try flashing null vbmeta via Ap block of odin

 

[OldNoobOne]

Try flashing null vbmeta via Ap block of odin

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.

 

[naz664]

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.

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

 

[OldNoobOne]

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

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.

 

[naz664]

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.

Ok may be it will only work on M215f (2020 edition)
If you have any more queries contact me on telegram @naz664

 

[GuruPrasadAH]

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://xdaforums.com/t/recovery-of...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:

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

 

[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://xdaforums.com/t/recovery-of...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:

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

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://xdaforums.com/t/recovery-of...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:

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

Does that recovery working for you ?

 

[GuruPrasadAH]

Does that recovery working for you ?

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

 

[naz664]

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

Ooh kk can anyone confirm that ?

 

[OldNoobOne]

Ok may be it will only work on M215f (2020 edition)
If you have any more queries contact me on telegram @naz664

Thanks no problem naz664

 

[OldNoobOne]

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://xdaforums.com/t/recovery-of...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:

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

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.

 

[naz664]

Thanks no problem naz664

Unified orangefox recovery for exynoss9611 working for you ?

 

[OldNoobOne]

Unified orangefox recovery for exynoss9611 working for you ?

OFox Beta didnt work, so I went back to Soulr344 TWRP; Honestly speaking TWRP isnt that bad

 

[naz664]

OFox Beta didnt work, so I went back to Soulr344 TWRP; Honestly speaking TWRP isnt that bad

Ok thankz for the report.
I used ofox tree as base if it didn't boot then no hope for this one too lol