{
"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"
}
Disclaimer
Code:
/**
* What you do with your device is your choice.
* None of the developers of this software will be held accountable for any damages to your device or to third parties.
* You should know this by now.
**/
What's this?
This is TeamWin Recovery Project for our ZUK Z2 / Lenovo Z2 Plus (z2_plus, z2131, z2132).
This is an official recovery support thread.
Known Issues
None
Requirements
Unlocked bootloader
Common sense and a Z2
Downloads, changelogs, installation info
All of this info can be found at the official info page.
If you use fastboot to install TWRP, you may have to specify a vendor ID in the commandline, like so:
Code:
fastboot [B]-i 0x2b4c[/B] flash recovery twrp.img
fastboot [B]-i 0x2b4c[/B] reboot
Thanks
@varotone for the initial TWRP device tree (and also for the thread template )
@kubersharma for some commits in the device tree
Frequently Asked Questions
Is this recovery compatible with both treble and non-treble ROMs?
Yes, this recovery is compatible with both non-treble and treble ROMs mounting /factory as vendor (the most updated ones are doing so), while it isn't compatible with the ROMs renaming /factory as /vendor. If the ROM you're using is still using /vendor instead of mounting /factory as vendor, report this to the maintainer and tell them to update.
Reserved !!
Reserved!
Thanks for the wonderful job!
Why we are going back to the old days that mounting /factory as /vendor? Does it affect flashing GSI?
getting an error in twrp saying "Failed to mount '/vendor' (Invalid argument)
Edit : I had flashed stock ROM , locked bootloader and then unlocked it back and flashed the latest twrp , and it works like a charm. Thanks for the new twrp mate
akshay pro said:
getting an error in twrp saying "Failed to mount '/vendor' (Invalid argument)
Click to expand...
Click to collapse
Same here...
Gibranibang said:
Same here...
Click to expand...
Click to collapse
Bro , u gotta flash vendor to factory from the current twrp and flash the latest twrp , then the problem will be solved
akshay pro said:
Bro , u gotta flash vendor to factory from the current twrp and flash the latest twrp , then the problem will be solved
Click to expand...
Click to collapse
Still same unable to mount vendor
I flshed vendor to factory and reboot(twrpbuilder)
Then flashed official factory twrp and reboot.
Any solution ?
akshay pro said:
Bro , u gotta flash vendor to factory from the current twrp and flash the latest twrp , then the problem will be solved
Click to expand...
Click to collapse
I've followed the steps, but i kept getting error everytime i try to install the factory rom
Gibranibang said:
I've followed the steps, but i kept getting error everytime i try to install the factory rom
Click to expand...
Click to collapse
So go via my original way , flash stock rom , update it to the latest version and flash the twrp recovery now. Done
Support you
Hey guys, TWRP 3.3.0 is out
Go and download it in the first post
The branch has also been changed to android-9.0 for z2_plus meanwhile
DD3Boh said:
Hey guys, TWRP 3.3.0 is out
Go and download it in the first post
The branch has also been changed to android-9.0 for z2_plus meanwhile
Click to expand...
Click to collapse
There is no link for 3.3.0! Is not up yet?
mondechristo1 said:
There is no link for 3.3.0! Is not up yet?
Click to expand...
Click to collapse
Yeah it will be out soon
It's weird because for z2 row it has been built already.
TWRP 3.3.0 is up now!
https://eu.dl.twrp.me/z2_plus/twrp-3.3.0-0-z2_plus.img.html
mondechristo1 said:
TWRP 3.3.0 is up now!
https://eu.dl.twrp.me/z2_plus/twrp-3.3.0-0-z2_plus.img.html
Click to expand...
Click to collapse
Deleted
PLEASE MAKE TWRP 3.3.0 for Vendor based ROM Devs
DD3Boh said:
Disclaimer
Code:
/**
* What you do with your device is your choice.
* None of the developers of this software will be held accountable for any damages to your device or to third parties.
* You should know this by now.
**/
What's this?
This is TeamWin Recovery Project for our ZUK Z2 / Lenovo Z2 Plus (z2_plus, z2131, z2132).
This is an official recovery support thread.
Known Issues
None
Requirements
Unlocked bootloader
Common sense and a Z2
Downloads, changelogs, installation info
All of this info can be found at the official info page.
If you use fastboot to install TWRP, you may have to specify a vendor ID in the commandline, like so:
Code:
fastboot [B]-i 0x2b4c[/B] flash recovery twrp.img
fastboot [B]-i 0x2b4c[/B] reboot
Thanks
@varotone for the initial TWRP device tree (and also for the thread template )
@kubersharma for some commits in the device tree
Frequently Asked Questions
Is this recovery compatible with both treble and non-treble ROMs?
Yes, this recovery is compatible with both non-treble and treble ROMs mounting /factory as vendor (the most updated ones are doing so), while it isn't compatible with the ROMs renaming /factory as /vendor. If the ROM you're using is still using /vendor instead of mounting /factory as vendor, report this to the maintainer and tell them to update.
Click to expand...
Click to collapse
Sir please make TWRP 3.3.0 for Vendor ROM or Make one TWRP that supports both vendor as well as factory by just flashing v2f or f2v in one single TWRP it will be more easy thank you very much for this TWRP.
A new update has been released! TWRP-3.3.0-1 is present in the website
Changelog:
- Added edl reboot option (download mode)
- Don't wipe data if the command isn't sent by the user
- Sign the build with aosp keys
Go update your recovery
DD3Boh said:
A new update has been released! TWRP-3.3.0-1 is present in the website
Changelog:
- Added edl reboot option (download mode)
- Don't wipe data if the command isn't sent by the user
- Sign the build with aosp keys
Go update your recovery
Click to expand...
Click to collapse
Hey dev i just have a question ..... Is it possible to add a pattern lock in twrp ???? I know it's silly but at the same time it will secure or phones surely ..... I'm just curious about it
Related
TWRP
This project provides the TWRP recovery for for the Sony Xperia XZ1 Compact (lilac).
{
"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"
}
FEATURES
File-Based Encryption (FBE) support
EXT4 support
F2FS support
EXFAT support
Provides unzip
Additional languages
This recovery will use the security patch level from the system partition to decrypt data. It should not be tied to a security patch level anymore.
DOWNLOAD
Make sure you download the .img and corresponding .asc.txt file (see INTEGRITY)!
You can always find the latest version of the recovery HERE.
INTEGRETY
The recovery images also come with an GPG armor file (.asc). With that file you verify that the image I created hasn't been altered.
How do you do that?
Download my gpg keyring here: https://cryptomilk.org/gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg.
Download the recovery.img and recovery.img.asc.txt file
Rename the recovery.img.asc.txt file to recovery.img.asc
Verfiy the signature using the following command:
Code:
gpg --keyring ./gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg --verify recovery.img.asc
A good tutorial is: How to verify signatures for packages from the Tor Project.
SECURITY ADVICE
Don't flash ROMs or Magisk modules which set SELinux to permissive or you welcome malware on your device!
XDA:DevDB Information
recovery_twrp_sony_lilac, Tool/Utility for the Sony Xperia XZ1 Compact
Contributors
modpunk, Dees_Troy
Source Code: https://github.com/cryptomilk/android_device_sony_lilac
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-09-16
Created 2017-11-18
Last Updated 2019-09-16
Nice work!
What does the STOCK addition in the title mean?
Can't I flash for example LOS with it?
Nice work! So does that mean that we finally can root our xz1 compact?
And currently this TWRP is not working for security patch November, right? I mean build nr: 47.1.A.5.51
4rz0 said:
What does the STOCK addition in the title mean?
Can't I flash for example LOS with it?
Click to expand...
Click to collapse
RTFM!
aikon96 said:
Nice work! So does that mean that we finally can root our xz1 compact?
And currently this TWRP is not working for security patch November, right? I mean build nr: 47.1.A.5.51
Click to expand...
Click to collapse
No, I need to create one for November. Will do that soon.
modpunk said:
RTFM!
Click to expand...
Click to collapse
I did read the OT, if that's what you mean, but it doesn't answer my question.
If the LOS I want to flash comes with the same security patch level, would it work?
4rz0 said:
I did read the OT, if that's what you mean, but it doesn't answer my question.
If the LOS I want to flash comes with the same security patch level, would it work?
Click to expand...
Click to collapse
There is no limitation in flashing. However there is no LOS you can flash yet ...
works perferct! thank you :good:
I got an XZ1. Any chance to get TWRP for it (for testing)?
Could someone please test https://xor.cryptomilk.org/android/twrp-lilac/twrp-3.1.1-0-lilac-patchlevel-2017-11-05.img
TWRP
modpunk said:
Could someone please test
Click to expand...
Click to collapse
ok. I'll test it
modpunk said:
Could someone please test https://xor.cryptomilk.org/android/twrp-lilac/twrp-3.1.1-0-lilac-patchlevel-2017-11-05.img
Click to expand...
Click to collapse
I will indeed test too juhuuu...
it flashes okay via fastboot, and twrp is also working. except for format option under wipe, when typing 'continue' it seems like it doesn't show the inputs, only the last letter 'e'
anyway after i flashed the twrp, i booted it up, and mounted everything except for otg. and then of course i flashed magisk.zip (latest v14) and it also succeeded
but then when i reboot from twrp, it stucks at sony logo, meaning default bootanimation doesn't kick in, and i patiently waited for like 10-15 min
so i assume it's not working. i even tried with a userdebug and regular user build 47.1.A.5.51
now i will try just to boot the twrp without flashing it and then flash magisk.zip while it's booted up via fastboot to see if it boots up normally
a) Do you have your partition encrypted and could you mount it, so it asked for a password?
b) TWRP writes a log file you can download adb pull /tmp/recovery.log
c) adb logcat is also working
Note that there is currently no upstream TWRP developement for Oreo ongoing. I just wrote several hacks to get it working.
modpunk said:
a) Do you have your partition encrypted and could you mount it, so it asked for a password?
b) TWRP writes a log file you can download adb pull /tmp/recovery.log
c) adb logcat is also working
Note that there is currently no upstream TWRP developement for Oreo ongoing. I just wrote several hacks to get it working.
Click to expand...
Click to collapse
A: it does not ask for password upon bootup so i guess it's not encrypted in that way
B attached here
C is there any specific logcat you want, like error or fatal level etc.
Question just to be clear: do we have to update twrp for evry new securitypatch?
To decrypt the /data partion on a stock ROM, yes you do.
Hi modpunk,
Ur a true star...****
I just want to ask a couple of question's.
Does the bootloader have to be unlocked in order to flash this....?
I have had a Z3 Compact and got it rooted with bootloader locked and also a Z5 Compact using munjen setup.
Install TWRP on it Flashed SuperSU using TWRP was best thing i did.
Do you have a step by step guide how to flash this. I would love to test it for you.
When you flash is it using munjen flashtool...?
Thanks Sham
UPDATE
TRWP is working actually, just figured out that it's magisk that get the phone not to boot, bith 14 and 14.5
and latest supersu both the xperia one and the regular one v.2.82 fails, give error "unzip fail, no proper recovery etc."
Now for fun i will load it up with userdebug firmware and see if i can make it manually root with the "angela" method
{
"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"
}
OrangeFox Recovery
Installation:
0. Backup your ROM, your data, your internal storage, and your settings/apps, to an external device
1. Reboot to fastboot screen, connect USB and send fastboot commands "fastboot flash recovery <recovery image file name including extension>"
OR
1. Reboot to existing TWRP recovery and flash image file to recovery partition
2. Reboot to recovery
3. Enjoy!
Features:
* Updated with latest TWRP commits
* Built-in support for installing init.d functionality
* Built-in support for installing Magisk
* AromaFM
* Flashlight
* Password, torch, led
* Superb new UI and themes
* OrangeFox theme engine:
- choice of theme (black, dark, etc)
- choice of color scheme
- choice of splash screen
* Alternative lockscreen
* And many more!
Source Code:
https://gitlab.com/OrangeFox
https://github.com/neobuddy89/android_device_oneplus_cheeseburger-twrp
Screenshots:
https://files.orangefox.tech/Screenshots/R10/
IMG Download:
19 Feb 2020: https://sourceforge.net/projects/cr.../OrangeFox-20200219-cheeseburger.img/download
Frequently Asked Questions:
* See https://forum.xda-developers.com/showpost.php?p=76885728&postcount=3
Credits
* TeamWin - for TWRP
* The OrangeFox Team - for your hard work
XDA:DevDB Information
OrangeFox Recovery Project, ROM for the OnePlus 5
Contributors
neobuddy89
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2020-02-18
Last Updated 2020-02-18
Added to the OnePlus 5 Index Thread here.
Added to Telegram Channel here: http://t.me/op5_files/1559
The recovery is very beautiful !
could you add the support to F2FS ? it can't read my data partition，Thx.
Also, seems it is unable to restore backups within same ROM for Q. I can try unless you are aware of it.
Thanks Mr neo. Backs up great looks great. Haven't tried to restore yet
Can it be used to flash custom pie roms?
str8str said:
Thanks Mr neo. Backs up great looks great. Haven't tried to restore yet
Click to expand...
Click to collapse
Did you use it to flash a rom? If so, has the procedure been performed without any issues?
Sc4r3Crow said:
Did you use it to flash a rom? If so, has the procedure been performed without any issues?
Click to expand...
Click to collapse
So far just did backup. Can't see why it wouldn't work
Sc4r3Crow said:
Did you use it to flash a rom? If so, has the procedure been performed without any issues?
Click to expand...
Click to collapse
Yes works. I tried install, backup, restore, moving files, etc. I am Encrypted BTW.
Can anyone tell me if wiping vendor is necessary when changing roms or clean/dirty flashing
str8str said:
Can anyone tell me if wiping vendor is necessary when changing roms or clean/dirty flashing
Click to expand...
Click to collapse
yes,recommended.
tried to flash twrp recovery
It's so pretty.
Restoring from a backup is working.
When trying to flash twrp-3.3.1-0-cheeseburger.img using this recovery it gets stuck in the bootloader and wont start anything.
not sure if this is an issue with twrp recovery. or even a corrupted file.
using firmware_9.0.10
@spo0nless What ROM was the image made of and which parts are backing up/restoring?
Is it possible to make it OP 5T compatible ?
mnurolcay said:
Is it possible to make it OP 5T compatible ?
Click to expand...
Click to collapse
It works fine on the 5t, I've been using it for a few weeks and the only "issue" is that it says cheeseburger instead of dumpling.
I've had no issues restoring nandroid backups (both ones made with twrp and OrangeFox).
Isn't there a port specifially for the 5t?
Pokemetti2 said:
Isn't there a port specifially for the 5t?
Click to expand...
Click to collapse
There's one but a bit outdated. This one is more up to date esp about Android 10.
spo0nless said:
It's so pretty.
Restoring from a backup is working.
When trying to flash twrp-3.3.1-0-cheeseburger.img using this recovery it gets stuck in the bootloader and wont start anything.
not sure if this is an issue with twrp recovery. or even a corrupted file.
using firmware_9.0.10
Click to expand...
Click to collapse
It's surely a corrupt file. I've flashed other twrp versions using OrangeFox and it worked everytime. Just to be sure you could flash 9.0.11 in advance and have a try to flash another twrp after that...
If I select internal memory, along with the usual, to wipe, is that the equivalent of TWRP's format data?
edit: just noticed the note saying it got moved to manage partitions, so nvm
{
"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.
{
"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
{
"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