Database Develop

[Recovery][OFFICIAL][UBL] TWRP 3.5.0 Touch Recovery for Xperia T/TX/V

{
"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"
}
TWRP 3.5.0 - Based upon Android 6.0 :
* Whole new TWRP 3 interface
* Flashable to FOTA for permanent recovery
* Bootable recovery image if required
OFFICIAL DOWNLOADS FOR XPERIA BLUE :
https://twrp.me/sony/sonyxperiat.html
https://twrp.me/sony/sonyxperiatx.html
https://twrp.me/sony/sonyxperiav.html
twrp-3.x.x-x-x.img : Official TWRP image
How to install : All informations available on TWRP.me
DEVELOPMENT DOWNLOADS FOR MINT (Xperia T) :
https://mega.nz/#F!3t0yyCia!HjUIl4o_TnOSWZzq3uWV1g
twrp-3.x.x-x-fota-mint.zip : Flashable TWRP 3 to FOTA installer
twrp-3.x.x-x-boot-mint.img : Fastboot bootable TWRP 3 image
cleaner-fota-mint.zip : Flashable FOTA formatter (optional)
DEVELOPMENT DOWNLOADS FOR HAYABUSA (Xperia TX) :
https://mega.nz/#F!egUHyCKQ!W-DNbBzdz1_OEatVQuuk0A
twrp-3.x.x-x-fota-hayabusa.zip : Flashable TWRP 3 to FOTA installer
twrp-3.x.x-x-boot-hayabusa.img : Fastboot bootable TWRP 3 image
cleaner-fota-hayabusa.zip : Flashable FOTA formatter (optional)
DEVELOPMENT DOWNLOADS FOR TSUBASA (Xperia V) :
https://mega.nz/#F!71EGkRpY!B3PQP3GjL8H-AMeR-XfwFw
twrp-3.x.x-x-fota-tsubasa.zip : Flashable TWRP 3 to FOTA installer
twrp-3.x.x-x-boot-tsubasa.img : Fastboot bootable TWRP 3 image
cleaner-fota-tsubasa.zip : Flashable FOTA formatter (optional)
HOW TO INSTALL EASILY TO FOTA :
Installing to FOTA will make it "permanent" and kept with ROM flashes
* (Optional) : Download the TWRP bootimage and flash it to boot
fastboot flash boot twrpfilename.img
* Boot to recovery : Enter the Recovery as usual
* Flash to FOTA : Install the TWRP FOTA zip
* (Optional) : Flash the ROM you want
HOW TO INSTALL MANUALLY TO FOTA :
* Bootimage : Download the TWRP bootimage you want to flash
* File storage : Adapt the path and push the file to the device this way :
Code:
adb root
adb wait-for-device
adb push /path/to/recovery.img /tmp/twrp.img
* Flash : Extract the TWRP image to the FOTA partition
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
* Reboot to recovery : adb reboot recovery
ABOUT THE USERDATA UNIFICATION :
Due to the unification, you will see 3 partitions in Mount.
* Data is the "UserData" partition, used for apps and user settings
* Internal storage is a portion of the "UserData" partition, used for medias
* Legacy SDCard is the old "Internal Storage", to support and access old ROMs
INFORMATIONS ABOUT TWRP 3 :
* Installation : Only flash the zip with a working TWRP or CyanogenRecovery
* Known issues : No major issue remaining, but sources open to improvements
* Usage : Built for Marshmallow, works for Lollipop based ROMs too
* More here : http://www.xda-developers.com/twrp-3-0-0-has-arrived/
ADDITIONAL LINKS :
* Easy ADB and Fastboot for unexperienced users :
http://forum.xda-developers.com/showthread.php?p=48915118
Thanks to the TWRP Team​
Current local manifest of the TWRP build
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!-- https://github.com/AdrianDC/twrp_development_sony -->

wow nice with material style :good:

Adrian DC said:
TWRP 3.0.0 - Based upon Android 6.0.0 :
Click to expand...
Click to collapse
Hey Adrian,
When you get a chance could you bump the TWRP blue build up to 3.0.2? There were all sorts of buglets in all the first 3.0 release. But 3.0.2 now works great with your SP builds
Thanks for all your work on the Sony stuff,
KC

Done !

Adrian DC said:
Done !
Click to expand...
Click to collapse
Could I get some instructions on how to install this on a stock device?

Adrian DC said:
Done !
Click to expand...
Click to collapse
It's working on Xperia T just fine I think. I flashed few zip fixes and gapps and that went fine. I haven't tried to flash a ROM so I don't know if it's ok, or it will show up some error like that error 7

A new more official release specific to the devices will be coming soon but I need to confirm they work for the moment.

I've tried to install this for Xperia T (mint), running with the final cm12.1 build of WhiteNEO, but unfortunately neither flashing the twrp.img via fastboot flash recovery, nor flashing the zip via twrp succeeded.

All three devices are now considered working fine with TWRP 3.0.2
so I invite you to test it all on your own device.
Bootimage is fully bootable and usable.
FOTA fully working too, if your current ROM doesn't support it,
know CM13 new releases will soon.

New releases for all 3 devices, stable & considered fully ready.
TWRP (and MultiROM TWRP) upgraded, like CyanogenRecovery, for proper performance and heat control.

Hi guys. have downloaded the twrp3 Tsubasa for my xv device. Now I want to install them.my android version is 4.3 JB with 9.2.A.2.5 built number.
Can you plz explain the installation step by step, or a video tutorial.???
it's my first time I don't know what to do at all.
I really need help.
And by the way how can I reboot into twrp3 recovery after the installation finished? Tnx
By the way my device doesn't reboot into recovery cwm or twrp. I don't know the reason.
Reply sooner please

Some body answer please.
My android version is 4.3 JB can i install this twrp3 on my device????

Younes_vd said:
Some body answer please.
My android version is 4.3 JB can i install this twrp3 on my device????
Click to expand...
Click to collapse
Read man... Read!!! - http://forum.xda-developers.com/showthread.php?t=2090268 This topic on XDA are pinned so people can see them and read them before posting everywhere

krasimiretov said:
Read man... Read!!! - http://forum.xda-developers.com/showthread.php?t=2090268 This topic on XDA are pinned so people can see them and read them before posting everywhere
Click to expand...
Click to collapse
i have already unlocked my bootloader .so you read and see what i have asked for
---------- Post added at 06:35 AM ---------- Previous post was at 06:33 AM ----------
im askimg if it is possible to install twrp3 on xv with 4.3 jb android .

Younes_vd said:
i have already unlocked my bootloader .so you read and see what i have asked for
---------- Post added at 06:35 AM ---------- Previous post was at 06:33 AM ----------
im askimg if it is possible to install twrp3 on xv with 4.3 jb android .
Click to expand...
Click to collapse
Download the .img file from OP and flash it with Flashtool(fastboot). its meant to use on MM or LP if you consider using it.

krasimiretov said:
Download the .img file from OP and flash it with Flashtool(fastboot). its meant to use on MM or LP if you consider using it.
Click to expand...
Click to collapse
ok thank you
---------- Post added at 07:10 AM ---------- Previous post was at 06:42 AM ----------
krasimiretov said:
Download the .img file from OP and flash it with Flashtool(fastboot). its meant to use on MM or LP if you consider using it.
Click to expand...
Click to collapse
hey are you there i installeed a twrp recovery now when i turn on my phone it directly goes into twrp. how shoud i reboot into system ???
in twrp i press reboot into system but again it goes into recovery menu .whats wromg?
---------- Post added at 07:29 AM ---------- Previous post was at 07:10 AM ----------
i cant boot into system help me plz.
i have a custom rom 5.5.9 in my sdcard if i install that via twrp, will my phone load up into system insteead twrp or not .
im waiting

Latest build is working without any problems, I already flashed your last CM13 build +gapps with it

@Adrian DC: You've build this using Omni 6.0, not CM-13.0 - right?

I tried rebuilding the Recovery for the Xperia V on a Debian8 system using the minimal omni build tree from here and the local_manifest posted by Adrian DC in the OP.
When trying to make the bootimage target, I run into the following build error:
Code:
Install: /home/defier/twrp-test/twrp/out/target/product/tsubasa/root/init
Target ram disk: /home/defier/twrp-test/twrp/out/target/product/tsubasa/ramdisk.img
/bin/bash: / 2048 * (2048+64): syntax error: operand expected (error token is "/ 2048 * (2048+64)")
Target boot image: /home/defier/twrp-test/twrp/out/target/product/tsubasa/boot.img
/bin/bash: (((21626880 / 100) - 1) / img_blocksize + 1) * img_blocksize: division by 0 (error token is "img_blocksize + 1) * img_blocksize")
build/core/Makefile:580: recipe for target '/home/defier/twrp-test/twrp/out/target/product/tsubasa/boot.img' failed
make: *** [/home/defier/twrp-test/twrp/out/target/product/tsubasa/boot.img] Error 1
make: *** Deleting file '/home/defier/twrp-test/twrp/out/target/product/tsubasa/boot.img'
#### make failed to build some targets (02:32 (mm:ss)) ####
I tried removing squashfstools, replacing them with a newer version and other things, but the issue still persists. Can someone help me, please?

Hi
Can someone explain what the cleaner does what is its purpose and how to use safely in Twrp?

[EXPERIMENTAL][TESTING][29-3-17] MultiRom Latest For kenzo/kate

{
"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"
}
For kenzo/kate​Supports all Roms (SHOULD)​
NOTE:
Code:
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 features included in this Kernel
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.
What is MultiRom?
MultiRom is one-of-a-kind multi-boot mod. It can boot any Android Rom as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our device. Besides booting from device's internal memory, MultiRom can boot from USB drive connected to the device via OTG cable. The main part of MultiRom is a boot manager, which appears every time your device starts and lets you choose ROM to boot. Roms are installed and managed via the modified TWRP recovery. You can use standard ZIP files to install secondary Android Roms, daily prebuilt image files to install Ubuntu Touch and MultiRom even has its own installer system, which can be used to ship other Linux-based systems.
I am not the developer of MultiRom. All Credits for it goes to Tasssadar, the actual developer of it.
Features:
MultiBoot any number of Android Roms
Restore Nandroid Backup as secondary ROM
Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting
Boot from USB drive Attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash Stock Rom zips again. Make backups. Always.
TESTED ON ROMS:
Test and Report
SUPPORTED DEVICES:
kenzo
kate
Please Test it in other Similar SD Variants and Report it Below.
Bugs:
You tell me
SCREENSHOTS:
All Screenshots HERE
INSTALLATION INSTRUCTIONS:
Via The MultiRom Manager App:​This is the easiest way to install everything MultiRom needs... Just follow the Below Instructions:
Install the app (Links Below)
Select MultiRom and Recovery on the Install/Update card.
Press "Install" on the Install/Update card to start the installation.
DONE! MULTIROM IS READY TO ROCK!
You current rom will not be erased by the installation.
Download link is in the second post.
Adding ROMs:
Android
Boot into MultiRom Recovery -> select MultiRom -> Add Rom -> Select the Rom's zip file and click Confirm.​
Updating/changing ROMs:
1. Primary Rom (Internal)
Flash Rom's zip File as Usual, Do factory reset if needed (it won't erase secondary Roms)
Go to MultiRom in recovery and do Inject curr. boot sector.
2. Secondary Android Roms
If you want to change the Rom, delete it and add new one. To update the Rom, follow these steps:
Go to MultiRom -> List Roms and select the Rom you want to update.
Select "Flash zip" and Flash the Rom's zip File.
Explanation of recovery menus:
Main menu
- Add Rom - Add Rom to Boot
- List Roms - List Installed Roms and Manage Them
- Inject boot.img File - When you Download something, for example a Kernel, which is Distributed as a Whole boot.img (eg. Qassam Kernel), you have to use this option on it, otherwise you would lose MultiRom.
- Inject curr. boot sector - Use this option if MultiRom does not show up on boot, for example after Kernel Installation.
- Settings - Well, SETTINGS!
Manage Rom
- Rename, Delete - No Need to Explain this I Think!
- Flash Zip (Only Android Roms) - Flash zip to the Rom, for example GAPPS
- Add/Replace boot.img - Replaces boot.img used by this Rom, this is more like a Developer Option.
- Re-Patch init - This is available only for Ubuntu. Use it when Ubuntu cannot find the root partition, i.e. after apt-get upgrade which changed the init script.​
GitHub Source Codes:
MultiRom Organization for Xiaomi Devices​Kenzo/Kate MultiRom Device Trees​MultiRom Manager App Source Codes​
Current Status:
Test and Report...
CREDITS:
Rishabh Rao (ME) - For Porting MultiRom to kenzo/kate
Tasssadar - For his awesome MultiRom
nkk71 - For his No-KEXEC workaround
Version Information:
Status: Unofficial, IN TESTING, Version 33
ENJOY!:good:
XDA:DevDB Information
MultiRom For kenzo/kate, Tool/Utility for the Xiaomi Redmi Note 3
Contributors
Rishabh Rao
Source Code: https://github.com/multirom-xiaomi
Version Information
Status: Testing
Current Beta Version: v33
Beta Release Date: 2017-03-29
Created 2017-03-29
Last Updated 2017-03-30

1.Can I flash any Other Kernel?
- YES! You CAN flash ANY Kernel!!!
2. Can I Flash Roms to USB-OTG? How?
- Yes, You CAN Flash Roms to USB-OTG.
Follow these steps to do so:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on Add Rom.
4. Select the correct Location and Flash it...
Note: Flashing on a USB-OTG takes some Time, so be patient & Don't Worry!
3.Where to Find Roms Installed in my USB-OTG Drive? How to Boot into Them?
- After Flashing the Rom you will be Booted into the MultiRom Boot Menu.
All your Roms Flashed on the Internal Memory will be in Internal Tab.
All Others will be in the External Tab.
4. How to Rename/Remove/Delete/Wipe Dalvik Cache or Flash any Other zips to an Existing Rom?
- Follow these steps:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on the Rom which you want to Remove/Add zips.
You will find all the options you need there!
5. "Unable to Flash, I am getting Errors" / "Executing Updater Script Failed" / "Rom is not Booting". ANY HELP???
- Please Provide Logs. It will be located in /sdcard/multirom/error.txt OR if that's not present here: /proc/last_kmsg
It would be Great if you can Provide Some Screenshots.
Press Volume Down + Power Buttons Together to take Screenshots.
6. How to Disable Auto Boot / Change Rom Name / Hide Roms / Change Brightness of MultiRom Boot Menu?
- Follow these steps:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on the 3 Dots on the Top Right of the Screen.
4. Select Settings.
You will find all the Customizations of the MultiRom Boot Menu you need there!
7. What is the No-Kexec Workaround?
- The No-Kexec Workaround by @nkk71 allows you to use MultiROM without having to flash a Kexec Enabled Kernel.
Please read More about No-Kexec Workaround from the author words only (to avoid duplicity and to get the latest information), thanks to @nkk71 once again!
http://forum.xda-developers.com/showpost.php?p=68738134&postcount=4

Download Links:
MultiRom Manager App 2.4-rishabhrao

Guys please test this in your Kenzo/Kate and Please tell me how it works

Will it work on 16 gb

pdpmoto said:
Will it work on 16 gb
Click to expand...
Click to collapse
All devices which support TWRP 3.1 official for kenzo or kate should definitely support this
Well try it out, definitely won't harm your device....
Also, uninstaller inckuded
Sent from my LeEco Le 2 using XDA Labs

Will test after exam
---------- Post added at 12:10 PM ---------- Previous post was at 12:00 PM ----------
Everything is ok as of now twrp flashed but will check more if i am in my town because If something go wrong then i will fix with my pc

Does it support the sailfish os?

Is f2fs supported?
Because I can't inject current boot sector

Anyone know if MIUI works?

Installing now on miui,reaaaally thx,because I was working on it without any result....
I will report if it worked
---------- Post added at 08:26 AM ---------- Previous post was at 08:17 AM ----------
It doesn't work on miui
It injects mltrm but,after a reboot boots normally.
Also its impossible to add roms,it says:
Failed to extract update script
Erasing incomplete Rom...
Plz fix it....

SMYM said:
Installing now on miui,reaaaally thx,because I was working on it without any result....
I will report if it worked
---------- Post added at 08:26 AM ---------- Previous post was at 08:17 AM ----------
It doesn't work on miui
It injects mltrm but,after a reboot boots normally.
Also its impossible to add roms,it says:
Failed to extract update script
Erasing incomplete Rom...
Plz fix it....
Click to expand...
Click to collapse
Hey Thanks a lot for trying and reporting...
Can you test something?
Just install mrom from app
Then goto recovery and add rom and see if you can add roms?
Also try once without injecting anything?
Coz that sometimes works too?
Sent from my LeEco Le 2 using XDA Labs

午夜听雪 said:
Does it support the sailfish os?
Click to expand...
Click to collapse
try it !

Rishabh Rao said:
Hey Thanks a lot for trying and reporting...
Can you test something?
Just install mrom from app
Then goto recovery and add rom and see if you can add roms?
Also try once without injecting anything?
Coz that sometimes works too?
Click to expand...
Click to collapse
I can't add any rom and the mltrm menu hasn't been shown up...

SMYM said:
I can't add any rom and the mltrm menu hasn't been shown up...
Click to expand...
Click to collapse
Let me check it out once...
EDIT: Can anyone try on some Rom other than miui?
So i can get a sure idea if it's a problem only with Miui or with all Roms...
Sent from my LeEco Le 2 using XDA Labs

I tried installing a few different ROMs and it always gave an error..
Hope this helps

Doesn't seem it is able to install roms to the sd card

4I-I said:
I tried installing a few different ROMs and it always gave an error..
Hope this helps
Click to expand...
Click to collapse
I have exactly the same error...

SMYM said:
I have exactly the same error...
Click to expand...
Click to collapse
Download links

[email protected] said:
Download links
Click to expand...
Click to collapse
Download via the app attached to first post

[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

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