Database Develop

[RECOVERY][OFFICIAL]PitchBlack Recovery Project[ONCLITE]

{
"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.

[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][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

[UNOFFICIAL][RECOVERY][PitchBlackRecoveryProject] PBRP For Lenovo Tab 4 8 ( TB-8504X/F )

{
"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.
*
* I'm 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.
*/
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
For Device: Lenovo Tab 4 8 TB-8504X/F
Build by: @Electron.48
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device Trees: Device Trees
Fully native android like UI
Full dark theme with changeable accents
Reorganized menus
Use AromaFM as default file manager
Various tools are include
System debloater available
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Installation Instructions:
Fastboot Method:
Download PBRP-TB8504-3.1.0-20220528-1258-UNOFFICIAL.img
Open Terminal where u have downloaded the pbrp img file
Go into Bootloader
Apache config:
adb reboot bootloader
Flash the recovery image
Code:
fastboot flash recovery PBRP-TB8504-3.1.0-20220528-1258-UNOFFICIAL.img
Reboot to Recovery and congrats you have successfully installed PBRP.
Flashing ZIP:
You should have a custom recovery already for this method
Flash the PBRP-TB8504-3.1.0-20220528-1258-UNOFFICIAL.zip in your custom recovery
Press volume down button to reboot to PBRP.
Congrats. You have successfully installed PBRP
What works:
Everything ( May find bugs its in testing phase )
Bugs:
You tell me
Downloads:
PBRP-TB8504-3.1.0-20220528-1258-UNOFFICIAL.img
PBRP-TB8504-3.1.0-20220528-1258-UNOFFICIAL.zip
Credits:
TeamWin for TWRP
PitchBlack Team for PBRP
@highwaystar_ru for Device Trees
Status:
Testing
Release Date:
28-05-2022

reserved

Awesome recovery and thanks for tools feature
Only one bug : touch is not responding but turning display off than on fix it.
Question : is it possible to restore twrp backups using PBRP

ZONTAC said:
Awesome recovery and thanks for tools feature
Only one bug : touch is not responding but turning display off than on fix it.
Question : is it possible to restore twrp backups using PBRP
Click to expand...
Click to collapse
Ig it should be possible. Try to copy the backups in PBRP folder then restore. Tell if it works or not

ZONTAC said:
Awesome recovery and thanks for tools feature
Only one bug : touch is not responding but turning display off than on fix it.
Question : is it possible to restore twrp backups using PBRP
Click to expand...
Click to collapse
Btw can u share some screenshots...?

Electron.48 said:
Ig it should be possible. Try to copy the backups in PBRP folder then restore. Tell if it works or not
Click to expand...
Click to collapse
Working

it doesnt work it just goes to the normal android recovery after i try to use it after flashing

stinkysockboi said:
it doesnt work it just goes to the normal android recovery after i try to use it after flashing
Click to expand...
Click to collapse
Tell in detail or provide log so that dev can work on it

Electron.48 said:
Bugs:
You tell me
Click to expand...
Click to collapse
So TB-8504F has a touchscreen issue where you need to sleep and wakeup recovery after it boots for touch to work. Like what @ZONTAC mentioned earlier. I was able to fix it on TWRP 3.6.2 that I built for testing. I would imagine it would work for PBRP as well. It does not affect TB-8504X which is why its not commonly seen. The F variant is not as popular. I have not tested it on 8504X mind you but I don't think that flag will be needed by it.
TB-8504F: Remove blank on boot · deadman96385/[email protected]
This flag kills the Himax touch until you lock and unlock on TB-8504F but strangely does not affect TB-8504X
github.com

deadman96385 said:
So TB-8504F has a touchscreen issue where you need to sleep and wakeup recovery after it boots for touch to work. Like what @ZONTAC mentioned earlier. I was able to fix it on TWRP 3.6.2 that I built for testing. I would imagine it would work for PBRP as well. It does not affect TB-8504X which is why its not commonly seen. The F variant is not as popular. I have not tested it on 8504X mind you but I don't think that flag will be needed by it.
TB-8504F: Remove blank on boot · deadman96385/[email protected]
This flag kills the Himax touch until you lock and unlock on TB-8504F but strangely does not affect TB-8504X
github.com
Click to expand...
Click to collapse
But i have 8504X variant

ZONTAC said:
But i have 8504X variant
Click to expand...
Click to collapse
Your recovery advertises that it supports both variants. That patch will fix the issue on TB-8504F, it should not change anything on TB-8504X but I don't have that version to confirm.

deadman96385 said:
Your recovery advertises that it supports both variants. That patch will fix the issue on TB-8504F, it should not change anything on TB-8504X but I don't have that version to confirm.
Click to expand...
Click to collapse
If you have build so i can test it on my tab(8504x)

Do You have any idea?
Freshly flashed stock, there everything works, but I cannot flash any ROM - tried both crDroid, RR and Ubuntu. Always same error.
Strange is it mounts system at first... And after formatting it can be mounted again, but than I got error, cos no image is there to be patched, I believe?

ch3mn3y said:
Do You have any idea?
Freshly flashed stock, there everything works, but I cannot flash any ROM - tried both crDroid, RR and Ubuntu. Always same error.
Strange is it mounts system at first... And after formatting it can be mounted again, but than I got error, cos no image is there to be patched, I believe?
Click to expand...
Click to collapse
Follow proper processor
In your case :- if you are coming from stock , 1. mount system in stock recovery
2.flash pbrp/twrp
3. do factory wipe(or reset)
4. do advance wipe in which wipe system, cache, delvick ,data
5.after that flash system
6. Still having problem try d/f twrp or contact rom dev

Did a test boot without flashing. System starts but hangs on many tasks, even restarting to other modes hangs the system. My device reports as tb_8504x. I had problem with flashing through TWRP so I wanted to try PBRB.

Hello, I got PBRP to boot into recovery, I have OEM bootloader unlocked and USB debugging enabled. I'm trying to completely format the tablet to install LineageOS 18. When I wipe the process gets stuck on "Formatting system using mke2fs". It's been on it for about an hour now. Is that normal? The device is responsive. I can hold the power button down and get reboot options. I can force a reboot and get back into the recovery and try again but each time it gets halted at the format stage. What should I do?

Development [RECOVERY][UNOFFICIAL] TWRP for Galaxy Tab S8 Series (Snapdragon)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Supported Models:
Galaxy Tab S8 X906B, X906C, X906N, X900, X806B, X806C, X806N, X800
Download & Guide:
1. Unlock your bootloader.
2. Downloads for Tab S8: gts8u twrp, gts8p twrp , gts8 twrp and kernel
3. Reboot to download mode
4. Put the TWRP TAR for your device with Odin in the AP slot, vbmeta_disabled_R.tar in USERDATA slot and click start.
5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.​If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​- Type: multidisabler again. will see - Finished. when done.​- Go back to Wipe > Format Data > type yes.​- Reboot to recovery.​7. Flash custom kernel and magisk apk in twrp.
8. Reboot to system, Enjoy.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
@Dan_FFM (David Dean) for helping with convert readonly f2fs vendor to readwrite
Donators
Sources:
Kernel tree
Device tree: gts8u, gts8p

Changelog:
GitHub History Tab S8
GitHub History Tab S8+
GitHub History Tab S8 Ultra

Note1: You need a custom permissive kernel to boot with R/W vendor.
Note2: If you got bootloop on Samsung logo, reboot to TWRP and wipe metadata from Advanced Wipe section

You have no idea how excited I got when I saw this. I'm going to try this first thing tomorrow and post my results! One question though; When you said "You need a custom permissive kernel to boot with R/W vendor.", is that the one that you've linked in the initial post?

SavXL said:
You have no idea how excited I got when I saw this. I'm going to try this first thing tomorrow and post my results! One question though; When you said "You need a custom permissive kernel to boot with R/W vendor.", is that the one that you've linked in the initial post?
Click to expand...
Click to collapse
Yes its.
Also if anyone have the regular Tab S8 send me recovery.img here or on telegram

Sure, this is for X700XXU1AVCD/X700OXM1AVCD/X700XXU1AVCD (Tab S8 Wi-Fi Middle East).
I used this to root but it may be corrupt so you might wanna check.
Download

Hello ,
Is it possible with this twrp version to use the sd card also ? Thank you for your answer .

I see magisk v25 change log mentions
Fix vb meta extraction implementation.
So does that mean magisk v25 will disable vb meta automatically now?

Techguy777 said:
I see magisk v25 change log mentions
Fix vb meta extraction implementation.
So does that mean magisk v25 will disable vb meta automatically now?
Click to expand...
Click to collapse
I belive so. IIRC, if you've rooted your tablet by patching the AP file with Magisk and flashed it in Odin, then vbmeta should already be disabled. Magisk, and therefore root, will still persist even after a factory data reset because your device is running Magisk as a system app.

Finally awake. Gonna go ahead and flash TWRP on my Tab S8+ and share my results!

SavXL said:
I belive so. IIRC, if you've rooted your tablet by patching the AP file with Magisk and flashed it in Odin, then vbmeta should already be disabled. Magisk, and therefore root, will still persist even after a factory data reset because your device is running Magisk as a system app.
Click to expand...
Click to collapse
I don't know about magisk becoming a system app I own the tab s6 I'm on one UI 4.1 and have magisk v25 And it doesn't install the system app so I don't know about that. I don't own s8 tablet

Techguy777 said:
I don't know about magisk becoming a system app I own the tab s6 I'm on one UI 4.1 and have magisk v25 And it doesn't install the system app so I don't know about that. I don't own s8 tablet
Click to expand...
Click to collapse
Then don't spam every thread with tab s6 topics

I come baring results. I flashed TWRP and vbmeta in Odin as described in the initial post, and it booted into TWRP! However, the good news ends there. The touch screen doesn't seem to work when in TWRP, and interestingly, when I have the keyboard attachment on, the install button darkens as if I'm pressing it no matter what I do on the trackpad. I've tried rebooting the tablet by holding pow + vol- but all it does is reboot once and then put me back in TWRP. I can use ADB to go into download mode, but I can't boot back to Android. Looks like I'm gonna need to flash my patched firmware and try again when this gets fixed. For context, I flashed the gts8p TWRP tar because I have a Tab S8+, but the WIFI only variant (X800), which is in the supported versions list, so I'm not sure what went wrong.

SavXL said:
I come baring results. I flashed TWRP and vbmeta in Odin as described in the initial post, and it booted into TWRP! However, the good news ends there. The touch screen doesn't seem to work when in TWRP, and interestingly, when I have the keyboard attachment on, the install button darkens as if I'm pressing it no matter what I do on the trackpad. I've tried rebooting the tablet by holding pow + vol- but all it does is reboot once and then put me back in TWRP. I can use ADB to go into download mode, but I can't boot back to Android. Looks like I'm gonna need to flash my patched firmware and try again when this gets fixed. For context, I flashed the gts8p TWRP tar because I have a Tab S8+, but the WIFI only variant (X800), which is in the supported versions list, so I'm not sure what went wrong.
Click to expand...
Click to collapse
Thanks for the feedback, will look into it soon. If you can send me vendor/firmware folder will try to fix touch.

afaneh92 said:
Thanks for the feedback, will look into it soon. If you can send me vendor/firmware folder will try to fix touch.
Click to expand...
Click to collapse
How do I do that? Is it a command I can run in adb?

SavXL said:
How do I do that? Is it a command I can run in adb?
Click to expand...
Click to collapse
Use root explorer, zip the folder and upload it

afaneh92 said:
Use root explorer, zip the folder and upload it
Click to expand...
Click to collapse
Alright, will do once I get back into android.

afaneh92 said:
Use root explorer, zip the folder and upload it
Click to expand...
Click to collapse
Alright, here's the vendor folder! It's compressed from the original size (~2.15GB).
715 MB file on MEGA
mega.nz

SavXL said:
Alright, here's the vendor folder! It's compressed from the original size (~2.15GB).
715 MB file on MEGA
mega.nz
Click to expand...
Click to collapse
Wow, I asked for firmware folder from vendor not the whole vendor.

afaneh92 said:
Wow, I asked for firmware folder from vendor not the whole vendor.
Click to expand...
Click to collapse
Ohhhhhhhhhh, I'm sorry LOL. When you said vendor/firmware I assumed you said to upload the vendor folder OR the firmware folder. I'll remember that for next time. XD