Develop Bugs

PitchBlack recovery for Zenfone 5 2018

{
"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.2.3
PitchBlack version: 2.9.0
For device: X00Q/ZE620KL
Maintainer/Authors build: https://forum.xda-developers.com/member.php?u=9533478
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/Imajkej/recovery_asus_X00Q
Kernel: https://github.com/Imajkej/kernel_asus_zenfone_X00QD
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 PC(Windows & Linux)
Download PBRP PC Installer zip from bellow
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP PC installer zip & copy the flashable zip to the installer folder
Goto fastboot mode in your device
Windows users open pbinstaller.bat file
Linux users execute pbinstaller.sh in a terminal
Follow the introductions on the installer from there
Enjoy
(LInux users will need unzip, adb & fastboot installed on their system)
Changelog
Code:
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Downloads
Flashable zip
https://androidfilehost.com/?fid=6006931924117926089
PC Installer
https://sourceforge.net/projects/pi...ller/PB_Installer_20181014_ALPHA.zip/download[/INDENT]
XDA:DevDB Information
PitchBlack Recovery, Tool/Utility for the Asus Zenfone 5Z
Contributors
imajkej
Version Information
Status: Beta
Created 2019-07-29
Last Updated 2019-07-28

I want to flash your TWRP.
But always error.(error 1).
If I flash by another TWRP it will cash.
Please fix it.
I just want to disable dm-verity.
Please help me.
I don't want to format my data partition.
Have anything can I try.
Device:ZE620KL
Android: Android 9.0(1907.105)

EdwardWu6688 said:
I want to flash your TWRP.
But always error.(error 1).
If I flash by another TWRP it will cash.
Please fix it.
I just want to disable dm-verity.
Please help me.
I don't want to format my data partition.
Have anything can I try.
Device:ZE620KL
Android: Android 9.0(1907.105)
Click to expand...
Click to collapse
Ok, if you downloaded the zip file, find recovery.img and unpack it. Than just use fastboot as you would flash recovery for the first time but before that to be sure that everything works use "fastboot erase recovery" and than "fastboot flash recovery recovery.img"
Hope it helps.

imajkej said:
Ok, if you downloaded the zip file, find recovery.img and unpack it. Than just use fastboot as you would flash recovery for the first time but before that to be sure that everything works use "fastboot erase recovery" and than "fastboot flash recovery recovery.img"
Hope it helps.
Click to expand...
Click to collapse
Ok.
I will do that tomorrow.
And if it work or not,I will report it to you.

Is there any customs rom for our ZE620KL?

vembazaxxx said:
Is there any customs rom for our ZE620KL?
Click to expand...
Click to collapse
No.Just GSI images and fix hotfix packages.

EdwardWu6688 said:
No.Just GSI images and fix hotfix packages.
Click to expand...
Click to collapse
I have a booting lineage os zip but I have to fix some missing packages in vendor partition which is taking a long time. When there will be the q source available I am definitely going to put work into porting it for this phone. My work is available on GitHub under the same nickname.

imajkej said:
I have a booting lineage os zip but I have to fix some missing packages in vendor partition which is taking a long time. When there will be the q source available I am definitely going to put work into porting it for this phone. My work is available on GitHub under the same nickname.
Click to expand...
Click to collapse
Thanks~
I wish I can see the project soon.
By the way.
Last time I try your TWRP.
Use your tips,it can't work on my device.
(Android Pie)
Do you have any debugging TWRP can give me try?
And Your TWRP have to contain Chinese(traditional) language package?
Thanks your help.

EdwardWu6688 said:
Thanks~
I wish I can see the project soon.
By the way.
Last time I try your TWRP.
Use your tips,it can't work on my device.
(Android Pie)
Do you have any debugging TWRP can give me try?
And Your TWRP have to contain Chinese(traditional) language package?
Thanks your help.
Click to expand...
Click to collapse
what is the problem you are encountering? could you guide me somehow what is the problem? is it not booting at all or somethingg different?

imajkej said:
what is the problem you are encountering? could you guide me somehow what is the problem? is it not booting at all or somethingg different?
Click to expand...
Click to collapse
It can booting in.
I just can see the first logo,and it will cash.
And reboot soon.

EdwardWu6688 said:
It can booting in.
I just can see the first logo,and it will cash.
And reboot soon.
Click to expand...
Click to collapse
I dont understand. Could You describe it more precisely? does twrp made by shakalaca work?

imajkej said:
I dont understand. Could You describe it more precisely? does twrp made by shakalaca work?
Click to expand...
Click to collapse
Yes. Shakalaca's TWRP is work.
I'm come from Taiwan too.
Shakalaca is my friend.
I had meet he before.
Now I using(It can work) twrp-3.3.1-0-X00Q-20190801-security-patch-2019-07-01-AndroidP.img
Made by him.
---------- Post added at 04:11 AM ---------- Previous post was at 04:10 AM ----------
Sorry. My English is not great.

EdwardWu6688 said:
Yes. Shakalaca's TWRP is work.
I'm come from Taiwan too.
Shakalaca is my friend.
I had meet he before.
Now I using(It can work) twrp-3.3.1-0-X00Q-20190801-security-patch-2019-07-01-AndroidP.img
Made by him.
---------- Post added at 04:11 AM ---------- Previous post was at 04:10 AM ----------
Sorry. My English is not great.
Click to expand...
Click to collapse
ok, I do not know how to help You if you won't describe it more precisely. On my phone it works fine, and I have reinstalled it quite a few times.

imajkej said:
ok, I do not know how to help You if you won't describe it more precisely. On my phone it works fine, and I have reinstalled it quite a few times.
Click to expand...
Click to collapse
What's your system version?

EdwardWu6688 said:
What's your system version?
Click to expand...
Click to collapse
pie, latest stock version, had been working on previous, had been working with custom gsi's, had been working with my own kernel and without.

imajkej said:
pie, latest stock version, had been working on previous, had been working with custom gsi's, had been working with my own kernel and without.
Click to expand...
Click to collapse
I use the pie(1907.105).
I will try again on weekends.

Will it work on Zenfone 5Q - ZC600KL?

Thanks for your amazing work, I'm watching with a lot of attention your device tree building. If you want me to help, I would be glad to be with you!

ashye said:
Will it work on Zenfone 5Q - ZC600KL?
Click to expand...
Click to collapse
Nope, there are not such things as cross compatible recoveries.

Since I flashed the recovery I'm in bootloop and I can't do anything anymore.
recovery and bootloader work but I can't install stock firmware
should I flash the original recovery, but where can I find it?
I have the firmware UL-ASUS_X00QD-ASUS-15.0619.1810.73-1.1.26-user
taken from the asus website can I take it here? if so how?
thanks.
Risolto!!!!!
I installed this rom from twrp and it has done !!!
Stock firmware with removed device check: https://androidfilehost.com/?fid=1395089523397941607
Now I have discovered that the wifi and the fingerprint do not work. Is there a method to install a stock with twrp?

[Recovery][v3.0.0][Curtana] Unofficial PBRP Recovery

{
"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.
This particular build is based on the amazing work done by the PBRP team and Joyeuse devs with some little changes to get it working on Curtana.
This build is really experimental so flash at your own risk.
However, the main use cases are fully covered as the most important functions of the recovery are working correctly.
Working
Data decryption
Flash
Wipe and format data
Backup and restore
Bugs
ADB sideload
Flashing Magisk results in bootloop: if you want to use Magisk you can patch a "boot.img" file from Magisk Manager and then flash that img to the Boot partition from recovery.
The recovery always asks for encryption password, even if the device is not encrypted: if your device is not encrypted just press cancel and it will work just fine.
Error 7 when flashing a ROM: check that System, Vendor and Product partitions are not mounted in the Mount section of the recovery before flashing a ROM.
Changelog
20200730
Updated to the new 3.0 UI
Language selection now works properly
Timezone selection now works properly
20200722
Initial Build
Downloads
20200730
20200722
Source Code
android_device_xiaomi_curtana-pbrp

Hey,
great work!
thanks!
I saw on github you changed that version from joyeuse to curtana.
Would you be able to compile a joyeuse version too for all the joyeuse owners?
Add it here too and change the title [curtana-joyeuse]?
I've unpacked your version and changed build.prop and repacked.
It's working beautifully on my joyeuse_eea device.
It is the only version that:
- does not lock touch after wake up
- can decrypt
- is not closed source as LR-twrp
- backup works
So great work!
PS: have no clue howto compile myself, otherwise I would have tried that path

kheno said:
Hey,
great work!
thanks!
I saw on github you changed that version from joyeuse to curtana.
Would you be able to compile a joyeuse version too for all the joyeuse owners?
Add it here too and change the title [curtana-joyeuse]?
I've unpacked your version and changed build.prop and repacked.
It's working beautifully on my joyeuse_eea device.
It is the only version that:
- does not lock touch after wake up
- can decrypt
- is not closed source as LR-twrp
- backup works
So great work!
PS: have no clue howto compile myself, otherwise I would have tried that path
Click to expand...
Click to collapse
Hi!
dungphp already did a version of PBRP for joyeuse that you can download here:
https://androidfilehost.com/?fid=8889791610682886707
On the other hand PBRP devs are working on a official device tree for joyeuse, but as far as I know there are still no official builds. You can check their progress here:
https://github.com/PitchBlackRecoveryProject/android_device_xiaomi_joyeuse-pbrp

Hey,
Thanks for the info.
For some reason the version of dungphp did not backup the existing install.
Can't remember the actual error.
Another version was 3.4.0 and did not decrypt.
So i stated looking into altering different curtana versions.
The LR twrp is closed source and locks up touch after waking up from sleep.
This version works flawlessly for me. 
I will track the progress of the official build.
Many thanks!

@end222 after flashing joyeuse version of recovery, recovery booted fine but internal storage folders have random names and no files in them, also backup dont work with error that folders dont exist or something like that, also phone didn't been able to boot system after installing recovery.I needed to reflash stock firmware to fix system.Any ideas?

You shouldn't have installed any recoveries because they are in alpha phase.
You can install some roms by using factory recovery and fastboot.

Thanks for the recovery.
patch a "boot.img" file from Magisk Manager and then flash that img to the Boot partition from recovery.
Click to expand...
Click to collapse
Which boot image should I patch and then flash?

mtolgae said:
Thanks for the recovery.
Which boot image should I patch and then flash?
Click to expand...
Click to collapse
You have to patch the image of the ROM you're using. To get it just extract the ROM's zip and you'll see it

end222 said:
You have to patch the image of the ROM you're using. To get it just extract the ROM's zip and you'll see it
Click to expand...
Click to collapse
Thanks

Updated to 20200730:
- New 3.0 UI
- Language selection works well now
- Timezone selection works fine as well

Flashing Magisk results in bootloop: if you want to use Magisk you can patch a "boot.img" file from Magisk Manager and then flash that img to the Boot partition from recovery.
Click to expand...
Click to collapse
If I flash the patched boot image, will it be fully rooted or will my device get bricked by file mangers like other's in the forum have mentioned?

Yoss Roness said:
If I flash the patched boot image, will it be fully rooted or will my device get bricked by file mangers like other's in the forum have mentioned?
Click to expand...
Click to collapse
It should work just fine. I've been using the recovery as a daily driver ever since I released the build and I've flashed Magisk using that method several times, all of them successfully.

end222 said:
It should work just fine. I've been using the recovery as a daily driver ever since I released the build and I've flashed Magisk using that method several times, all of them successfully.
Click to expand...
Click to collapse
Great, thank you!

Thank you
Sent from my Redmi Note 9 Pro using Tapatalk

is it safe to install this recovery over lr-twrp? i don't want to reinstall my whole phone btw. thanks for this project!!

keiner99 said:
is it safe to install this recovery over lr-twrp? i don't want to reinstall my whole phone btw. thanks for this project!!
Click to expand...
Click to collapse
Yes, at least I did...
Sent from my Redmi Note 9S using Tapatalk

how you guys install ROMs? i did everything described in Bugs Section... unmount system, vendor, product.
press cancel and ignore encryption password.
then i try to install mi-globe rom and get error 256 because system partition is unmounted

trinity_user said:
how you guys install ROMs? i did everything described in Bugs Section... unmount system, vendor, product.
press cancel and ignore encryption password.
then i try to install mi-globe rom and get error 256 because system partition is unmounted
Click to expand...
Click to collapse
I have the same issue with miglobe Rom it endet up in System unmounted and Read Only... After that only flash the original Rom with MiFlash fixed this.
With the EU ROM everythings OK.
I have the Issue with LRTWRP to.
I think the Script from MIGlobe ROM that run after flash the .zip - doest work with the unoficial TWRP Versions for now...

Timmiotool said:
I have the same issue with miglobe Rom it endet up in System unmounted and Read Only... After that only flash the original Rom with MiFlash fixed this.
With the EU ROM everythings OK.
I have the Issue with LRTWRP to.
I think the Script from MIGlobe ROM that run after flash the .zip - doest work with the unoficial TWRP Versions for now...
Click to expand...
Click to collapse
sounds logical to me. hm and its possible to fix this? @end222

Method installation
Thanks for the recovery, in the post initial no have installation explication, is "fastboot flash recovery filename.img" the best method? Or fastbootd? I just unlocked the bootloader. Thanks.

PBRP [Joyeuse][v2.9.1]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.4.0
PitchBlack version: 2.9.1
For device: Redmi Note 9 Pro
Maintainer/Authors build: https://forum.xda-developers.com/member.php?u=8529431
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Kernel Source: https://github.com/Joyeuse-Indonesia-Project/kernel_xiaomi_sm6250
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
Full dark theme with changeable accents
Reorganized menus
MIUI OTA support
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Installation Instructions
From previous version or other recovery
Download the PitchBlack zip to your device
Reboot to your current custom recovery
Flash the PitchBlack zip
The device will automatically reboot into PitchBlack Recovery after installation
Enjoy
From PC
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by fastboot flash recovery.img
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
Changelog
Code:
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Fix Dynamic Partition
- Improper mount of /data partition
- Some bug fixed
Downloads
Flashable zip
https://drive.google.com/uc?id=1HiPbEimxTiZlAXmjgVzf69bB_knn4H1E&export=dow nload

GREAT JOB!

Works on curtana? thanks

zenez said:
Works on curtana? thanks
Click to expand...
Click to collapse
onlye Joyeuse, in curtana you already have twrp and others.

All right, will try later. ?

Yuluga said:
onlye Joyeuse, in curtana you already have twrp and others.
Click to expand...
Click to collapse
Yes but this one is said dealing with dynamic partition. A must have.
Is it planned to have a release devoted to Curtana.
Thanks
EDIT:
I've just tested it on Curtana in order to test file copy/modify in system via file explorer.
Unsuccessful trial. System is still kept at read only state.
Anyway a real nice interface design. Thanks to devs.

any one test it? any bug?

hoang_phuong84 said:
any one test it? any bug?
Click to expand...
Click to collapse
It is working from what I can do on a Curtana. It cann't install because digest is not in accordance but should be working well on Joyeuse and at any point better than LR modded fix release available at T.me.
Just boot it on your phone and try it like that.

Recoveries struggle to get stable on this device/system it seems (what is the status of PBRP: alpha, beta, stable?). I saw something about a Android 10 Boot Partition causing the problems but would like to understand better if and how Recovery will work nicely with this device and Custom ROMs. Can someone point me to a explanation/thread why on RN9P, Android 10 it is so difficult to get a working Recovery for Custom ROM Install/Updates?

hello,
bravo for this excellent work, since the time we hoped functional custom recovery. Are all backup and restore functions functional, micro sd recognition, etc? ... Thank you

the right commend for Flash the recovery.img is "fastboot flash recovery recovery.img"
second, i get decrypt data after i reboot to recovery.

I have curtana twrp on joyeuse phone. Can ı flash via curtana twrp?
Edit 1: I tried install via curtana twrp. Error 1 fail...

Anybody try to flash latest Redmi Note 9 Pro EU ROM (v11.0.5.0) with this recovery? I tried dirty flash it from 11.0.4 and got error message. After flashing, It stay and boot on 11.0.4 but lost wifi mac address.

fathroen said:
Anybody try to flash latest Redmi Note 9 Pro EU ROM (v11.0.5.0) with this recovery? I tried dirty flash it from 11.0.4 and got error message. After flashing, It stay and boot on 11.0.4 but lost wifi mac address.
Click to expand...
Click to collapse
I've tried too but the same result.
"Fixed it" with fastboot first time installation of v11.0.4 and will wait for fastboot package v11.0.5.

After flashing recovery, and entering to PBRP is asking for password for decrypt data, i do not have password, my phone is not encrypted

fathroen said:
Anybody try to flash latest Redmi Note 9 Pro EU ROM (v11.0.5.0) with this recovery? I tried dirty flash it from 11.0.4 and got error message. After flashing, It stay and boot on 11.0.4 but lost wifi mac address.
Click to expand...
Click to collapse
Are you referring to the xiaomi.eu rom v11.0.5? If so, there's alot of people reporting problems booting after flashing that version. You're probably not referring to the stock rom, as I don't think there are any recovery flashable zips for that available.
In regard to fixing your wifi problem, in reading through the GSI rom thread, there are many reports of wifi being lost after flashing the boot.img from a different version of the stock rom than that which users were originally on without updating the other partitions. If the v11.0.5 boot.img was flashed to your phone, but some other partitions failed to flash, that may explain things. You could try downloading/extracting the v11.0.4 boot.img, either from the stock or xiaomi.eu rom package depending on which you are using, and flashing that again from fastboot using "fastboot flash boot boot.img".
Otherwise if that fails, reflashing v11.0.4 in its entirety should hopefully get your wifi working again.

mariob098 said:
After flashing recovery, and entering to PBRP is asking for password for decrypt data, i do not have password, my phone is not encrypted
Click to expand...
Click to collapse
Same issue here

You'll have to use the password/pass number you used to unlocked your device when waking it up.

blowy666 said:
You'll have to use the password/pass number you used to unlocked your device when waking it up.
Click to expand...
Click to collapse
But i do not have lock screen pin/password

thanks
Sent from my Redmi Note 9 Pro using Tapatalk

[RECOVERY][3.5.2_9-2][Mi A2 Lite] Unofficial TWRP recovery for Xiaomi Mi A2 Lite

{
"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:
Code:
#include <std_disclaimer.h>
/*
*
* 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.
*
*/
Features:
- Open Source
- Payload.bin support (ROM flashing works)
- Proper MTP support (for both 4.9 and 3.18 kernels)
- Working decryption for both FBE and FDE
- Adoptable Storage is working
- Android 11 support (No bootloops to recovery mode)
- NTFS, F2FS, exFAT, FAT32 support for SD Cards and USB drives
- Ability to flash splash images directly to the splash partition
- Adjusted theme to account for the notch (the clock doesn't overlap with the notch)
- No TWRP app installation prompts
- Older 3.4.0 button-style reboot menu instead of the newer listbox-style one
- Addon.d script to make TWRP survive ROM updates
Download:
TWRP image: https://drive.google.com/file/d/19ysSbW31NG4QF5OClbox-mArIb17KbpT/view?usp=sharing
TWRP Installer: https://drive.google.com/file/d/1-wk_0kOe_e-2XDDiv08BxJhn1ixWXjUw/view?usp=sharing
Installation Instructions:
- Make sure your bootloader is unlocked. If not, unlock it first.
- Reboot to Bootloader (aka Fastboot mode)
- Execute:
Code:
fastboot boot twrp-3.5.2_9-2-daisy-unofficial.img
- Flash the TWRP Installer zip to keep TWRP permanently
Notes:
- You can ignore any "Failed to unmount /vendor: Device or resource busy" errors since they do not cause any issues (this
happens when switching the active slot while the vendor partition is mounted).
- This TWRP does not have the newer 3.5.0 theme changes in the reboot menu because it is confusing for a significant amount
of users and does not match the rest of the button-style design.
- The TWRP app checks and prompts have been completely removed due to the app causing a lot of issues including bootloops
since it is not designed for A/B devices.
- The portrait_hdpi theme has been adjusted to have more padding in the status bar and to account for the presence of the
notch (the clock's position has been modified in order for the clock not to get overlapped by the notch)
- TWRP's addon.d will only work in the following scenarios:
a) When updating your ROM through the ROM's Updater application
b) When dirty-flashing a newer build of the same ROM you have installed from recovery
- TWRP's addon.d (TWRP survival) may not work in all ROMs as some ROMs choose not to have permissive update-engine domain. This essentially results in SELinux denials, preventing the addon.d script from executing when SELinux is enforcing. You can read more about the said issue here (https://github.com/topjohnwu/Magisk/commit/cba0d040000d6ff38c6646bb9d7daa12beae2878)
Source code:
Recovery Source: https://github.com/LinkBoi00/android_bootable_recovery
Device tree: https://github.com/LinkBoi00/twrp_device_xiaomi_daisy
Kernel source: https://github.com/LinkBoi00/twrp_kernel_xiaomi_daisy
XDA:DevDB Information
TWRP-3.5.2_9-2-Unofficial, Tool/Utility for the Xiaomi Mi A2 Lite
Contributors
LinkBoi
Source Code: https://github.com/LinkBoi00/twrp_device_xiaomi_daisy
Version Information
Status: Stable
Current Stable Version: 3.5.2_9-2
Stable Release Date: 2021-05-04
Created 2020-10-19
Last Updated 2021-05-04

Reserved

Reserved

i'll give a try. still using twrp-3.3.1-dees_troy-daisy cuz its the only one that doenst ask a decrypt key that i dont have

Antho02 said:
i'll give a try. still using twrp-3.3.1-dees_troy-daisy cuz its the only one that doenst ask a decrypt key that i dont have
Click to expand...
Click to collapse
decryption does not work in this build, im looking into a fix. Custom roms do not support decryption anyways so it's a minor issue for now

The handling of the "Adoptable Storage" still broken.
E:Failed to mount decrypted adoped storage device
Click to expand...
Click to collapse
DATA is not encrypted (I use a custom ROM with Force-Encryption-Disabler)

PC295 said:
The handling of the "Adoptable Storage" still broken.
DATA is not encrypted (I use a custom ROM with Force-Encryption-Disabler)
Click to expand...
Click to collapse
Can you send me logs of that issue (advanced > copy log > tick the "include kernel log" option and swipe in the "bar")? After doing this can you also try official twrp and tell me if that has the same issue?
Thanks for the feedback
PS: Can you join a telegram group (https://t.me/XMiA2Lite)? If /When you join there, mention me (@runrunrun00) and your issue, thanks in advance

The problem is with all TWRPs. (Official, Offain, this)
I have to use OTG to install Custom ROMs etc.
It is probably not a TWRP problem but one of the CustomROMs?
Unfortunately, I also find that there are adoptable storage issues in many custom ROMs.
It got noticeably worse with Android 10 ROMs.
For example the migration via key file (/data/misc/vold/....key) does not work everywhere.
Or the memory only works after setting up the microSD several times.
Log attached...

PC295 said:
The problem is with all TWRPs. (Official, Offain, this)
I have to use OTG to install Custom ROMs etc.
It is probably not a TWRP problem but one of the CustomROMs?
Unfortunately, I also find that there are adoptable storage issues in many custom ROMs.
It got noticeably worse with Android 10 ROMs.
For example the migration via key file (/data/misc/vold/....key) does not work everywhere.
Or the memory only works after setting up the microSD several times.
Log attached...
Click to expand...
Click to collapse
i might have found a way to fix this issue (in the bootable twrp, the installed one depends on your rom)

again, with twrp Bogdan, for my work fine, no problem with storage external

dochdoc said:
again, with twrp Bogdan, for my work fine, no problem with storage external
Click to expand...
Click to collapse
what problem do you have with external storage?

dochdoc said:
again, with twrp Bogdan, for my work fine, no problem with storage external
Click to expand...
Click to collapse
what's your issue exactly?

nothing, no problem with this custom recovery (TWRP 3.3.1 by @ScaryMen1325), work fine with me

dochdoc said:
nothing, no problem with this custom recovery (TWRP 3.3.1 by @ScaryMen1325), work fine with me
Click to expand...
Click to collapse
And what's the issue with this recovery regarding external storage (not scarymen's)?

LinkBoi said:
And what's the issue with this recovery regarding external storage (not scarymen's)?
Click to expand...
Click to collapse
If you only boot from TWRP, you can't access Adptable Storage.
There is an installed TWRP required.

PC295 said:
If you only boot from TWRP, you can't access Adptable Storage.
There is an installed TWRP required.
Click to expand...
Click to collapse
Is it possible to contact me on telegram again? I have one version in test that most likely fixes your issue

When I use Offain TWRP PC output is like this
Code:
downloading 'boot.img'...
OKAY [ 15.830s]
booting...
OKAY [ 0.748s]
finished. total time: 16.578s
and then phone reboot to stock Android
When I use TWRP from this thread PC output is same but phone boot Android Recovery and it says Can't load Android system. Your data be corrupt and there are 2 options Try Again and Factory Reset when I try again it boots to stock.

Yyres55 said:
When I use Offain TWRP PC output is like this
Code:
downloading 'boot.img'...
OKAY [ 15.830s]
booting...
OKAY [ 0.748s]
finished. total time: 16.578s
and then phone reboot to stock Android
When I use TWRP from this thread PC output is same but phone boot Android Recovery and it says Can't load Android system. Your data be corrupt and there are 2 options Try Again and Factory Reset when I try again it boots to stock.
Click to expand...
Click to collapse
If you want, you can contact me on telegram, I might have a fixed version there

LinkBoi said:
If you want, you can contact me on telegram, I might have a fixed version there
Click to expand...
Click to collapse
It worked. I tried another USB port and it's okay

hi, is there any plan to support encryption??

biladina.id said:
hi, is there any plan to support encryption??
Click to expand...
Click to collapse
Yup, of course. In the next release, 3.5.0, every bug I listed will be fixed, including Decryption, Android 11 support and more. If you want to test the release candidate (which is still 3.4.0 because twrp hasn't released 3.5.0 yet), you can join the telegram group below:
www.t.me/DaisyTestflight
New update will be released in XDA when TeamWin releases 3.5.0

[RECOVERY] [11] [12] [13] [UNOFFICIAL] TWRP for OnePlus 6 & 6T

{
"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.x 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.
* We are not responsible for bricked devices, dead SD cards
* you point the finger at us for messing up your device, we will laugh at you.
Code:
INSTALLATION:
1. Download TWRP-***.img
2. Reboot to bootloader
3. boot into TWRP using "fastboot boot TWRP-***.img"
OR
Flash TWRP-***.zip from existing recovery
Code:
TO PERMENANTLY INSTALL RECOVERY
SELECT Flash current TWRP from advance or flash ZIP
NOTE:
Unified Build for 6 & 6T for _11
_11 build is for OOS 11 & A11 custom roms
_12 build is for A12 & above custom roms
Separate Build to Avoid Encryption Issue
Advantage Over official recovery
- A12 rom encryption support with pin/pattern/password
- Up to date with source
DOWNLOADS:
For A11 & OOS
SourceForge
For A12,A12.1 & A13
SourceForge
SOURCES:
TWRP
Device tree
Hit Thanks If You Liked My Work

Update
7/10/22
3.7.0_12 is up
- Source side Update
- Slot Switching Fix
- Better A13 Decryption
12/08/22
- Source Side Update
- Render UI at 60 FPS
- Revert to old Flashing Zip
24/06/22
3.6.2_11
- Source side Update
- Minor Fix
ONLY for A12 & above custom rom
3.6.2_12
- A12 Manifest
- A12 Support (with pin/pattern/password)
27/02/22
- Bump to 3.6.1
- Sdcard mount fix
- Source side update

Thanks for your work

Boots properly. Thank you for providing a working TWRP for OP6T.

Siddk said:
View attachment 5497027
Team Win Recovery Project 3.x, or TWRP3.x 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.
* 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.
Code:
INSTALLATION:
1. Download Recovery.img
2. boot into fastboot
3. Type following commands
"fastboot boot recovery.img"
Code:
TO PERMENANTLY INSTALL RECOVERY
SELECT Install to Ramdisk from advance or flash ZIP
DOWNLOADS:
MEGA
SourceForge
SOURCES:
TWRP
Device tree
Hit Thanks If You Liked My Work
Click to expand...
Click to collapse
best ,

what's the difference between this and the latest official 3.6.0_9?

Has this recovery been updated work on the Debranded Tmobile variant? This version is included in Havoc OS and it does NOT boot on the Tmobile Variant. It just gets stuck on the twrp boot screen.

Gytole said:
Has this recovery been updated work on the Debranded Tmobile variant? This version is included in Havoc OS and it does NOT boot on the Tmobile Variant. It just gets stuck on the twrp boot screen.
Click to expand...
Click to collapse
Yeah I wish more people would talk about debranded T-Mobile varients. Spend hours trying to figure that out last night because apparently no one at the havoc team thought about it

zickler_malta said:
what's the difference between this and the latest official 3.6.0_9?
Click to expand...
Click to collapse
It is unified so op6 & 6t shares same file
in Official 3.6.0 you cant do fastboot boot recovery.img it went to crashdump mode
my twrp have support for 6t where official twrp only support 6 A11 version
Gytole said:
Has this recovery been updated work on the Debranded Tmobile variant? This version is included in Havoc OS and it does NOT boot on the Tmobile Variant. It just gets stuck on the twrp boot screen.
Click to expand...
Click to collapse
i didnt get full logs of this version in havoc group someone shared only recovery log if you want share log with me on telegram
CybeastEXE said:
Yeah I wish more people would talk about debranded T-Mobile varients. Spend hours trying to figure that out last night because apparently no one at the havoc team thought about it
Click to expand...
Click to collapse
share logs using
adb logcat -d > logcat.txt
adb shell dmesg > dmesg.txt
adb pull /tmp/recovery.log
@Gytole

Siddk said:
It is unified so op6 & 6t shares same file
in Official 3.6.0 you cant do fastboot boot recovery.img it went to crashdump mode
my twrp have support for 6t where official twrp only support 6 A11 version
i didnt get full logs of this version in havoc group someone shared only recovery log if you want share log with me on telegram
share logs using
adb logcat -d > logcat.txt
adb shell dmesg > dmesg.txt
adb pull /tmp/recovery.log
@Gytole
Click to expand...
Click to collapse
Siddk said:
It is unified so op6 & 6t shares same file
in Official 3.6.0 you cant do fastboot boot recovery.img it went to crashdump mode
my twrp have support for 6t where official twrp only support 6 A11 version
i didnt get full logs of this version in havoc group someone shared only recovery log if you want share log with me on telegram
share logs using
adb logcat -d > logcat.txt
adb shell dmesg > dmesg.txt
adb pull /tmp/recovery.log
@Gytole
Click to expand...
Click to collapse
to clarify can I get these logs if I fastboot boot recovery.img? or does it have to be installed?

CybeastEXE said:
to clarify can I get these logs if I fastboot boot recovery.img? or does it have to be installed?
Click to expand...
Click to collapse
Get log anytime no issue

Don't flash it on OnePlus 6 because it will destroy your data partition , that what happened when I flash it on OSS 11.1.2.2

NLhardcore said:
Don't flash it on OnePlus 6 because it will destroy your data partition , that what happened when I flash it on OSS 11.1.2.2
Click to expand...
Click to collapse
May be,that's why I can't flash syberia OS. It's not booting into system. But official has no problem.

NLhardcore said:
Don't flash it on OnePlus 6 because it will destroy your data partition , that what happened when I flash it on OSS 11.1.2.2
Click to expand...
Click to collapse
i have tested on stock rom everything fine
chackopg said:
May be,that's why I can't flash syberia OS. It's not booting into system. But official has no problem.
Click to expand...
Click to collapse
A12 not supported yet

Siddk said:
i have tested on stock rom everything fine
A12 not supported yet
Click to expand...
Click to collapse
That is not known. Thanks.

NLhardcore said:
Don't flash it on OnePlus 6 because it will destroy your data partition , that what happened when I flash it on OSS 11.1.2.2
Click to expand...
Click to collapse
Yes, same thing with my phone. Do you know how to restore it? When im rebooting into system TWRP is turning on :/

[This message has been deleted.]

piechu11 said:
Yes, same thing with my phone. Do you know how to restore it? When im rebooting into system TWRP is turning on :/
Click to expand...
Click to collapse
Ok, got it working using MSM Tool and OOS 10.3.8

Siddk said:
Get log anytime no issue
Click to expand...
Click to collapse
Got those logs for the no boot on the Debranded T-mobile variant. These should hopefully help with fixing sky hawk recovery as well. if you need me to test any fixes

CybeastEXE said:
Got those logs for the no boot on the Debranded T-mobile variant. These should hopefully help with fixing sky hawk recovery as well. if you need me to test any fixes
Click to expand...
Click to collapse
can you get logcat
recovery.log shows nothing
share directly on telegram @Siddk or zulip