Database Develop

[RECOVERY][UNOFFICIAL][09/20]Red Wolf Recovery Project

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Red Wolf Recovery is custom recovery based on TWRP source code, however some things are working here slightly different then you might expected. The main objective of this project is to provide stable recovery with features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. This recovery is also first recovery on the world with password protection.​
Based on TWRP version: 3.2.1
For devices: Z2 PRO, Z2121, Z2_ROW
TREE: https://github.com/mracar07/android_device_zuk_z2_row/tree/RWRecovery
Developers: ATG Droid & dadi11
Thanks: z31s1g (for the base of his theme), Ray Li (For his useful advice in the beginnings), osm0sis (for his image scripts), cosmedd for twrp tree
Features:
Code:
[B]Translated to EN, PL, zh_cn, & CZ [/B]
- Password protection
- Flashlight
- MIUI Incremental OTA Support
- Built-in latest Magisk, SuperSU & AromaFM
- Support two screenshot GUI actions - Power+VolDown to save screenshot in to the internal storage &
Power+VolUp to save screenshot in to the external storage (Will be automatically saved in to the internal in case
that external storage doesn't exist).
- Support automatic reboot after the restore process
- Recovery can automatically modify some props in the ROM directly during the installation
- Some built-in scripts from community
- Tap to wake support
- Advanced deactivation of the stock recovery
- Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- Support "set on boot" settings.
*[B] Changes for security reasons [/B]*
- ADB isn't starting automatically at the start of the recovery. You have to activate it in recovery
- MTP isn't starting until user enter correct password
- Deactivated support of the custom themes
Some differences to the official version:
Code:
[B][COLOR="red"]- get out of here if you are pirating apps. this recovery is not for you[/COLOR][/B]
- always up-to-date with the latest TWRP changes
- compiled on omnirom-7.1 source
- kernel compiled inline with the recovery
- fixed backup/restore of Firmware
- added F2FS support
- added NTFS support
- added exFAT support
- more languages
- other improvements from Features and Changelog lists
Changelog:
04/09:
Treble Support
In AEX Blue Led of Death fixed
thanks to @cosmedd
Redwolf source updated...
04/09 Second Release:
Slow backup-restoring fixed
04/18:
Renamed from factory to vendor
BUGs:
Only in recovery FLASHLIGHT
Downloads:
Latest build for ZUK Z2 PRO(z2_row):
https://androidfilehost.com/?fid=1322778262904009823
Screenshots:
Warning:
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery. But your device can be still reinstalled using fastboot or Miflash.
Donate DEV: paypal.me/mracar07​

Flashed, no problem...excellent development, thank you!

flashed, made backup and restore with it, worked without problems. Thanks!

looks interesting any incompatiblity with roms? is the su included? or just a script to install from path "xyz"? is the kernel change / govenor change permanently or temporary for one boot?
so many questions :fingers-crossed: thx for your work guys

Thanks for your work ,but I met some trouble .I use AEX 5.2 ,try to flash this recovery from twrp. but when I rebot to the RW , I can see RW's first screen ,then LED was blue(900E) .I back to TWRP now. I hope you can fix it.THX

江泽民1926 said:
Thanks for your work ,but I met some trouble .I use AEX 5.2 ,try to flash this recovery from twrp. but when I rebot to the RW , I can see RW's first screen ,then LED was blue(900E) .I back to TWRP now. I hope you can fix it.THX
Click to expand...
Click to collapse
Not have any issiue. Tested and working properly :good:

Does it chinese language supported?I can help you im chinese

江泽民1926 said:
Thanks for your work ,but I met some trouble .I use AEX 5.2 ,try to flash this recovery from twrp. but when I rebot to the RW , I can see RW's first screen ,then LED was blue(900E) .I back to TWRP now. I hope you can fix it.THX
Click to expand...
Click to collapse
me too!

Bave Lee said:
Does it chinese language supported?I can help you im chinese
Click to expand...
Click to collapse
-> "Translated to EN, PL, zh_cn, & CZ "

Great Project! We need a german translation. I can help you. Tell me what can i do. OK, i see we have a german translation. Great work.

江泽民1926 said:
Thanks for your work ,but I met some trouble .I use AEX 5.2 ,try to flash this recovery from twrp. but when I rebot to the RW , I can see RW's first screen ,then LED was blue(900E) .I back to TWRP now. I hope you can fix it.THX
Click to expand...
Click to collapse
Hi, Chairman 江☺I 've encountered the same issue with you, I am currently using MIUI 9 , not sure if I need to clean up the old TWRP files.
Did you flash latest LR.Team TWRP (by wzsx150)?

Updated. 04/09.
for test thanks to @weimerd

04/09 Second Release:
Slow backup-restoring fixed
for test thanks to @weimerd

Thanks man, nice work

Unfortunately not possible to run edl mode . Btw good work and recovery works quite good and fast . Thanks for your work .

mar.ur said:
Unfortunately not possible to run edl mode . Btw good work and recovery works quite good and fast . Thanks for your work .
Click to expand...
Click to collapse
There's no direct button for it within RW Recovery, but it has adb working, so once you're started up in Red Wolf Recovery, just plug into the computer and send it "adb reboot edl" from a terminal. I just tested it and it worked fine.
I'm assuming you have a functional installation of android sdk or platform tools and working USB drivers on a capable computer, otherwise what exactly did you plan on doing with EDL mode anyway?

Terminator.J said:
There's no direct button for it within RW Recovery, but it has adb working, so once you're started up in Red Wolf Recovery, just plug into the computer and send it "adb reboot edl" from a terminal. I just tested it and it worked fine.
I'm assuming you have a functional installation of android sdk or platform tools and working USB drivers on a capable computer, otherwise what exactly did you plan on doing with EDL mode anyway?
Click to expand...
Click to collapse
No possible to run edl mode from system by ADB command . Edl = download and is existing in twrp as I know .

mar.ur said:
No possible to run edl mode from system by ADB command . Edl = download and is existing in twrp as I know .
Click to expand...
Click to collapse
... I"m sorry, I don't know what else to say, other than either you're wrong or there must be something wrong with your computer/phone configuration. I literally just started up in the latest red wolf recovery, connected via USB cable to my computer (Windows 10 laptop), opened an administrative command prompt on the computer, cd to directory I unzipped platform tools to, typed "adb reboot edl", and the phone rebooted into emergency download mode, and ran QFIL, which sees a 9008 mode device ready for flash.
However I did also test from within the recovery itself... going to terminal inside RW recovery and typing "reboot download" did not work, it just restarted normally. That is true. But again, it's not an issue since you have the computer & USB cable there (or else you wouldn't need EDL mode) and can just send the adb command from the computer.

I only reported that is impossible to run edl mode from system by ADB and from twrp by download button .

04/18 UPDATED....
Renamed from factory to vendor

[Android 10][Recovery][A715F]TWRP 3.5.0 [ianmacd]

{
"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.
*
* I am 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 doing this to your device
* 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.
*/
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, root your device and more.
Disclaimer:
- I do not claim this work as my own, this thread was created to have an XDA thread for A71 TWRP. I will try my best to keep it up to date with Ian's work, but can't promise that will remain for ever. If you want the latest TWRP and to be notified as soon as its published, be sure to join the Telegram channel.
- I am not responsible about any damage of any kind that this custom binary may cause.
- Please read the whole main post & related ones before proceed and follow the guide as it is wrote. I will not offer support for any issues that have been already stated.
- Your Knox Warranty Bit will be blown once you flash this or others custom binaries, preventing you to use Knox Features. It can't be resetted in any way, so think twice before flashing this.
- Bugs can be reported here in XDA or via our Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs (device variant and logcat).
How to Install:
First, you need to unlock the bootloader. Here's how to do it:
- Backup all media before proceeding, this will erase everything in your internal storage including music and photos
- Go to developer settings and enable [OEM Unlock]
- Reboot to download mode
- When prompted, press and hold VOL + to enter bootloader unlock mode
- Press VOL + to confirm you want to unlock bootloader, this will wipe your data
- If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
- Go through the initial setup. Skip through all the steps since data will be wiped again later when we flash TWRP and magisk
- Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader. This step is MANDATORY
- Your bootloader now accepts unofficial images in download mode.
After finally unlocking the bootloader, proceed with installing TWRP (tar) with Odin:
- Boot to download mode and load TWRP tar file and VBMeta disabler tar file in AP and BL of Odin, doesn't matter which goes where
- Disable [Auto Reboot] in Odin
- Flash
- Force a reboot by pressing VOL+, VOL - and POWER buttons at the same time
- After the screen goes black, IMMEDIATELY let go of all buttons and IMMEDIATELY press and hold VOL+ and POWER button at the same time to boot to TWRP
- After booting to TWRP successfully, go to WIPE in TWRP
- At the bottom, you should see an option to FORMAT DATA. After you select it, you will be asked to type "yes" in your keyboard. If you do not see this, you probably selected the wrong option.
- After formatting data, flash the Multidisabler zip with TWRP. This is done to avoid future bootloops.
(Optional) Flash magisk.zip to root (google where to find it)
- Reboot to system
- Wait patiently for the device to boot for the first time
How to flash TWRP (img):
- Reboot to recovery
- Select Install
- Select Install Image and search for the TWRP img file
- Flash as recovery
- Reboot to recovery
- Done
Downloads:
twrp-a71-3.5.0_10-4.img by ianmacd
twrp-a71-3.5.0_10-4.tar by ianmacd
Multidisabler zip by Ianmacd
VBMeta disabler
Previous Versions:
TWRP 3.5.0 10-2
TWRP 3.5.0_10-2.tar by Ianmacd
TWRP 3.5.0_10-2.img by Ianmacd
Source Code: https://github.com/ianmacd/twrp_a71
Source Code: https://github.com/ianmacd/a71
Change log:
TWRP 3.5.0_10-4
This minor release accommodates the new (currently canary only) packaging of Magisk.
Future versions will no longer come as a separate .zip file, but will have the Magisk payload embedded inside the Magisk Manager .apk file.
To this end, TWRP will now also list any files named Magisk.apk, app-release.apk or app-debug.apk in the list of flashable .zip files.
Credits:
- Samsung for kernel source code
- TeamWin for their awesome recovery
- @ianmacd for compiling, updating, and maintaining for A71

Join Ian's TWRP Telegram group​
Code:
Check out the latest TWRP releases and notes on Ian's Telegram group
For anything already released, please ask here in XDA
Link: Telegram Group
Join our A71 Telegram group​
Code:
Check out the latest projects on our Telegram, where we share our advancement on new things and try to help as best as we can.
For anything already released, please ask here in XDA
Link: Telegram Group
Join our Spanish General Android Telegram group​
Code:
Grupo para los que hablamos español en donde discutimos Android en general /// Group made for Spanish speakers to discuss Android in general
Link: Telegram Group​

How to install GSI with TWRP:
The A71 (and almost all 2020 devices I believe) doesn't use the traditional partitioning system, they now include the super partition. This is called a dynamic partition. Basically, it contains system, vendor, odm and product images inside. TWRP can't install system.img directly to system partition for now, so you will have to follow a workaround.
You can follow the guide here: https://forum.xda-developers.com/t/...ung-galaxy-a51-super-partition-image.4216083/
This guide was made for the A51, but has been also confirmed working for the A71 since they both use this dynamic partition
Feel free to ask questions here or in that thread, we can try to help out.

so this will NOT work on an unlocked A71 A716U?

sixisixsix said:
so this will NOT work on an unlocked A71 A716U?
Click to expand...
Click to collapse
I don't think so, not sure. I don't have that device.

ShaDisNX255 said:
I don't think so, not sure. I don't have that device.
Click to expand...
Click to collapse
thank you for the response! So this model will work A71 SM-A715F/DS (amazon link)

Well it works on SM-A715F, I think the DS just stands for Dual SIM.

ShaDisNX255 said:
Well it works on SM-A715F, I think the DS just stands for Dual SIM.
Click to expand...
Click to collapse
ahh ok thank you. Samsung has an asinine amount of sku's/model which makes it extremely confusing especially in the US where you have to seek out global versions and cannot buy locally

sixisixsix said:
ahh ok thank you. Samsung has an asinine amount of sku's/model which makes it extremely confusing especially in the US where you have to seek out global versions and cannot buy locally
Click to expand...
Click to collapse
Thats the truth. I've been a Samsung user for years and I still get confused with all their variants

Hi, thank you for your work.
I am getting "Invalid Zip Format" and "directory) Error opening" errors with this method at TWRP. I followed the steps, put the image into gsi folder and renamed it to system.img. Any help?
ShaDisNX255 said:
How to install GSI with TWRP:
The A71 (and almost all 2020 devices I believe) doesn't use the traditional partitioning system, they now include the super partition. This is called a dynamic partition. Basically, it contains system, vendor, odm and product images inside. TWRP can't install system.img directly to system partition for now, so you will have to follow a workaround.
You can follow the guide here: https://forum.xda-developers.com/t/...ung-galaxy-a51-super-partition-image.4216083/
This guide was made for the A51, but has been also confirmed working for the A71 since they both use this dynamic partition
Feel free to ask questions here or in that thread, we can try to help out.
Click to expand...
Click to collapse

taha2626 said:
Hi, thank you for your work.
I am getting "Invalid Zip Format" and "directory) Error opening" errors with this method at TWRP. I followed the steps, put the image into gsi folder and renamed it to system.img. Any help?
Click to expand...
Click to collapse
Probably was zipped incorrectly. Not sure.

Yeah you're right. Should've known better to zip 3 folders together instead of the parent one. It's working now and I'm testing Havoc-OS. Great, thanks.
ShaDisNX255 said:
Probably was zipped incorrectly. Not sure.
Click to expand...
Click to collapse

New TWRP is up! 3.5.0_10-4
Check out the changelog and the new download links in the OP

ShaDisNX255 said:
How to install GSI with TWRP:
The A71 (and almost all 2020 devices I believe) doesn't use the traditional partitioning system, they now include the super partition. This is called a dynamic partition. Basically, it contains system, vendor, odm and product images inside. TWRP can't install system.img directly to system partition for now, so you will have to follow a workaround.
You can follow the guide here: https://forum.xda-developers.com/t/...ung-galaxy-a51-super-partition-image.4216083/
This guide was made for the A51, but has been also confirmed working for the A71 since they both use this dynamic partition
Feel free to ask questions here or in that thread, we can try to help out.
Click to expand...
Click to collapse
@ShaDisNX255 apologies for going a bit off topic.. But could you tell if any GSI rom is stable for our device?

karan5chaos said:
@ShaDisNX255 apologies for going a bit off topic.. But could you tell if any GSI rom is stable for our device?
Click to expand...
Click to collapse
I'm sorry but I don't use GSI. I'm quite contempt with Samsung software lol.

Will this work with A71 5G? I have SM-A716U

cyclesrxnder said:
Will this work with A71 5G? I have SM-A716U
Click to expand...
Click to collapse
No, it won't.

Thanks!

A7160可以用吗
Translation: Can A7160 be used

Is it possible to add password on TWRP?

Development [RECOVERY][UNOFFICIAL] TWRP for Galaxy S21 Ultra (Exynos)

{
"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 S21 Ultra G998B/N.
Download & Guide:
1. Unlock your bootloader.
2. Download S21 Ultra: p3s.
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 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
Sources:
Kernel tree
Device tree

Changelog:
29.11.2021 - Update to TWRP 3.6.0
- Updated to latest kernel source
- Update multidisabler
- fstab clean up
21.08.2021 - Add Symlinked dynamic partitions to fstab
09.08.2021 - Fix haptic feedback
- Updated to latest kernel source
- No vbmeta disable require
- fstab clean up
01.03.2021 - Initial Release.

Boss!

Boss

Thanks boss..

Boss!

Omg.... Boss and Heroes

Any custom rims for this device yet? Maybe a Pixel Experience ROM?

Any news on rom development by chance?, Just curious thanks.

It will take a big while before custom ROMs, don't expect them too soon

Hello everyone, I only have one question, besides the Twrp and the vbmeta_disabled_R.tar do you also need to flash a Multidisabler via Odin? Thank you.

siriow said:
Hello everyone, I only have one question, besides the Twrp and the vbmeta_disabled_R.tar do you also need to flash a Multidisabler via Odin? Thank you.
Click to expand...
Click to collapse
You just need to go to advanced then open terminal in TWRP, and type multidisabler, then wait, then type it again.

FreeRunner2017 said:
You just need to go to advanced then open terminal in TWRP, and type multidisabler, then wait, then type it again.
Click to expand...
Click to collapse
Ok, Thank you

siriow said:
Ok, Thank you
Click to expand...
Click to collapse
Your welcome, any issues feel free to PM me

I wish there was a very easy way to patch AP to keep TWRP after a dirty flash manual upgrade.

Burt Squirtz said:
I wish there was a very easy way to patch AP to keep TWRP after a dirty flash manual upgrade.
Click to expand...
Click to collapse
1.Easiest option - Go with custom ROM (If available)
2.Second easy, modify AP and patch it.
Extract all the contents of AP file - delete recoevry and vbmeta images - Repack as tar (You can use 7zip or similar) - Patch it with magisk
After flashing, straightway go to TWRP - and apply multidisabler before booting device.

dr.ketan said:
1.Easiest option - Go with custom ROM (If available)
2.Second easy, modify AP and patch it.
Extract all the contents of AP file - delete recoevry and vbmeta images - Repack as tar (You can use 7zip or similar) - Patch it with magisk
After flashing, straightway go to TWRP - and apply multidisabler before booting device.
Click to expand...
Click to collapse
This would clear the User data / Accounts also, yeah ?
@afaneh92 _ Bro, I think the existing TWRP doesnt mount Data on the Newest March Security Patch.
I had no issues with the February Firmware.
Could you have a look ?

JazonX said:
This would clear the User data / Accounts also, yeah ?
@afaneh92 _ Bro, I think the existing TWRP doesnt mount Data on the Newest March Security Patch.
I had no issues with the February Firmware.
Could you have a look ?
Click to expand...
Click to collapse
You asked for dirty flash trick right? If erasing data and acc then it's not dirty flash.
I don't have any issue on March secure patch

What could be causing this issue?
Did a full stock flash as well, and repeated the TWRP process.

JazonX said:
What could be causing this issue?
Did a full stock flash as well, and repeated the TWRP process.
Click to expand...
Click to collapse
Run multidisabler script in twrp terminal

[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