Develop Bugs

[Recovery] [Unofficial] [MI 8] - PitchBlack-Recovery

UNOFFICIAL PITCHBLACK RECOVERY FOR MI 8
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Pitch Black Recovery was started in March 18 2018 with the movement to enhance TWRP with better customizatons, themes and features.
https://sourceforge.net/projects/pitchblack-twrp/
I'm not a developer, i've simple done a porting to MI 8 Dipper of this recovery
​
Initial build Based on TWRP version: 3.2.3
Upto date with latest TWRP source
Supports Treble and non-Treble ROMs
Full dark theme with changeable accents
MIUI OTA support
Force encryption disabler
Use AromaFM as default file manager
Universal flash-able file for all variant of a device
Various tools are include
Many bug fixes & optimization
CHANGELOG :
Code:
# PB v2.9.0 v2 (20181227-1829)
-fixed device id
# PB v2.9.0 v1 (20181227-0547)
-initial release
-rebuild from Poco F1 project (https://forum.xda-developers.com/poco-f1/development/recovery-pitch-black-pocof1-t3883268)
DOWNLOAD :
PitchBlack-dipper-2.9.0-20181227-1829-UNOFFICIAL
OLD
PitchBlack-dipper-2.9.0-20181227-0547-UNOFFICIAL
INSTALLATIONS :
Flash Zip file with other TWRP
and then it will reboot automatically to recovery
Enjoy
KNOWN BUGS:
AromaFM install hangs the device
Let me know if you find others bugs
SCREENSHOTS:
Source Code: https://github.com/PitchBlack-Recovery
Official Site: https://sourceforge.net/projects/pitchblack-twrp
Created 2018-12-27
Last Updated 2018-12-27
www.paypal.me/gulp79​

nice to see another development, let me test. Thanks
2 question :
- can you make statusbar under notch so we can see the time
- if I have TWRP Backups should I move to folder PBRP and then restore?

error installing pixelrom,verification zip failed

R0MaN0 said:
error installing pixelrom,verification zip failed
Click to expand...
Click to collapse
Ops, fixed and reuploaded:
https://drive.google.com/open?id=1X9B_rkqLteH7arULYUR8pFSKTBOA5TTN

kaizer hanz said:
nice to see another development, let me test. Thanks
2 question :
- can you make statusbar under notch so we can see the time
- if I have TWRP Backups should I move to folder PBRP and then restore?
Click to expand...
Click to collapse
Sorry for statusbar i'm not able to hide notch....
For backups, i've not tested a restore, but you should move yours to PBRP folder and then you can try to restore.

Finally, a MI 8 recovery with OTA survival.
Big ups!
(Bootloader locked so can't test it....gotta wait a month)

Last build twrp 3.2.3 is 1208.
What build in a pitchblack?

Great to see a custom recovery for Mi8.
Thanks man

Seems great! Can someone explain what "No need to worry about ARB" means ?

gulp79 said:
[*]No need to worry about ARB
Click to expand...
Click to collapse
Could you give a bit more of info about this?
It just checks ARB and doesn't let you install if it is below the current ARB number?

desvariando said:
Could you give a bit more of info about this?
It just checks ARB and doesn't let you install if it is below the current ARB number?
Click to expand...
Click to collapse
Sorry i'm not the developer of this recovery, i've just done a simple porting to MI 8 Dipper.
Btw, this is the developer's changelog:
Code:
Info
PitchBlack v2.9.0
Based on TWRP 3.2.3
Update Log :
- Initial NON-ARB (Support update and downgrade miui rom ARB 4 ARB 3, ARB 3 ARB 4. Without delete firmware, baseband and etc-update the follow firmware)
- AutoReboot Fixed
- Update DM Verity Logic
- Update fstab flags
- Update magisk
- Update unroot magisk
- Update noverity
- Etc
and this it the option to enable to avoid ARB:
Btw i've not tested this, because my MI 8 dosn't have ARB (i've always been on xiaomi.eu or Custom rom, never on official MIUI).

gulp79 said:
Btw i've not tested this, because my MI 8 dosn't have ARB (i've always been on xiaomi.eu or Custom rom, never on official MIUI).
Click to expand...
Click to collapse
Well..., I've installed official builds and it HAS ARB.
Currently I'm on 1.

shaman91 said:
Last build twrp 3.2.3 is 1208.
What build in a pitchblack?
Click to expand...
Click to collapse
Atm is based on infrag build:
Code:
TWRP 3.2.3.0:
Build 17/12/2018
Build on Android 9.0 TWRP sources

Rommco05 said:
MIUI OTA support means if I received incremental update will be installed over PichBlack without issues?
Click to expand...
Click to collapse
Another thing that i've not tested (i'm on xiaomi.eu weekly, so i install full rom every week, i've no OTA on xiaomi.eu)
but there are some infos under advanced settings

nighthawk696969 said:
Seems great! Can someone explain what "No need to worry about ARB" means ?
Click to expand...
Click to collapse
This feture is not tested on MI 8 and is not clear how to use or what it does, so atm i've removed the ARB related features from OP (could be dangerous to use this untested features to roll back from Pie to Oreo)

gulp79 said:
This feture is not tested on MI 8 and is not clear how to use or what it does, so atm i've removed the ARB related features from OP (could be dangerous to use this untested features to roll back from Pie to Oreo)
Click to expand...
Click to collapse
Thanks for clarifying. It would be great to have a tool that prevents us from flashing files with lower arb counter in the future, just to avoid all the bricks.

gulp79 said:
Another thing that i've not tested (i'm on xiaomi.eu weekly, so i install full rom every week, i've no OTA on xiaomi.eu)
but there are some infos under advanced settings
Click to expand...
Click to collapse
should I enable "Support MIUI Incremental OTA" ? because now I enable it and flash EU ROM 8.12.27 working fine.
or I just disable it like default setting?
Sent from my MI 8 using Tapatalk

error when backup "E:recv error on uevent"

powergo said:
error when backup "E:recv error on uevent"
Click to expand...
Click to collapse
I've just done a backup without errors.
Can you post your log?
What partitions have you tried to backup?
On what partition you get the error?

Force encryption disabler??
Sent from my Mi 8 using Tapatalk

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

[RECOVERY][TREBLE][UNOFFICIAL] TWRP 3.5.2 for NB1

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. It's a full 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.
TWRP built for the Nokia 8. It should work fine, but using it is a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery.
Installation
If you are installing TWRP for the first time, then you need to flash it from fastboot:
Code:
fastboot flash:raw boot <twrp.img>
Otherwise you can install the latest release by flashing the appropriate .zip file
Downloads
Treble: Releases · resident-nokia/android_device_nokia_A1N-TWRP (github.com)
Stock: Releases · resident-nokia/android_device_nokia_NB1-TWRP (github.com)
Contributors
THMSP, emufan4568
Sources:
Treble: https://github.com/GPUCode/twrp resident-nokia/android_device_nokia_A1N-TWRP: TWRP tree for Nokia 8 Sirocco / Treble (github.com)
Stock: resident-nokia/android_device_nokia_NB1-TWRP: TWRP tree for Nokia 8 Stock (github.com)
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2020-11-07
Last Updated 2021-04-10

New build is up!
* TWRP is based on the twrp-10.0 branch now
* Decyption blobs have been updated to android 10
* Decryption works with and without screen lock (pattern, pin. password)

New release is up! Download from here: https://github.com/GPUCode/android_device_nokia_nb1_TWRP/releases/tag/twrp-3.4.0-0-2-2
* Allow wiping of System partition
* Fixed OTA updates failing at Step 2 of flashing

emufan4568 said:
New release is up! Download from here: https://github.com/GPUCode/android_device_nokia_nb1_TWRP/releases/tag/twrp-3.4.0-0-2-2
* Allow wiping of System partition
* Fixed OTA updates failing at Step 2 of flashing
Click to expand...
Click to collapse
Treble, and ota updates? Enlighten me here.
Back to stock, that's a huge fix. But oh, we can't install it on stock. So... What's going on?!

Arashone said:
Treble, and ota updates? Enlighten me here.
Back to stock, that's a huge fix. But oh, we can't install it on stock. So... What's going on?!
Click to expand...
Click to collapse
By OTA updates I mean my crDroid releases. In the past, flashing the .zip from TWRP would fail at step 2. Now you do not have to wipe data and reflash T-Virus every time you need to update to any new crDroid release

emufan4568 said:
By OTA updates I mean my crDroid releases. In the past, flashing the .zip from TWRP would fail at step 2. Now you do not have to wipe data and reflash T-Virus every time you need to update to any new crDroid release
Click to expand...
Click to collapse
Great
Is it possible for stock version too?

Arashone said:
Great
Is it possible for stock version too?
Click to expand...
Click to collapse
Yes it is. I just need to replace the kernel with a non-treble one and remove the vendor partition references. But why would you need a stock version anyway? There are no custom ROMs for stock to flash

emufan4568 said:
Yes it is. I just need to replace the kernel with a non-treble one and remove the vendor partition references. But why would you need a stock version anyway? There are no custom ROMs for stock to flash
Click to expand...
Click to collapse
There are ota updates for stock official ROM. Many people have let's say 488b and want to stick to latest version of oreo. TWRP 3.3.1 can't do that, and fails at stage 2 of flashing offline ota.
Btw, this new xda is God fast... Kisses to the Prophets!

Arashone said:
There are ota updates for stock official ROM. Many people have let's say 488b and want to stick to latest version of oreo. TWRP 3.3.1 can't do that, and fails at stage 2 of flashing offline ota.
Btw, this new xda is God fast... Kisses to the Prophets!
Click to expand...
Click to collapse
Stock TWRP has this issue too. It is caused by listing non-existant partitions in gpt-utils https://github.com/resident-nokia/t...d3df561fb6/recovery/gpt-utils/gpt-utils.h#L82 When installing an OTA TWRP tries to switch slot but it fails because it is not possible to switch slot on a partition that does not exist. This issue was fixed by this commit https://github.com/GPUCode/android_...mmit/179c5de56987455ca10e424ab1eaa00dd882228d and now it lists all the correct partitions and TWRP no longer fails when installing updates. I agree, XDA feels more like modern website rather than a 2005 forum

emufan4568 said:
Stock TWRP has this issue too. It is caused by listing non-existant partitions in gpt-utils https://github.com/resident-nokia/t...d3df561fb6/recovery/gpt-utils/gpt-utils.h#L82 When installing an OTA TWRP tries to switch slot but it fails because it is not possible to switch slot on a partition that does not exist. This issue was fixed by this commit https://github.com/GPUCode/android_...mmit/179c5de56987455ca10e424ab1eaa00dd882228d and now it lists all the correct partitions and TWRP no longer fails when installing updates. I agree, XDA feels more like modern website rather than a 2005 forum
Click to expand...
Click to collapse
Is this issue fixed in TWRP 3.3.1 too (which is used for stock firmwares)? That was my question. 'cause the last (recent) time I used it, no such change was apparent. Also, restoring bku was impossible, although I'm not sure about it.
The change here, paves the way of using Q on our lady.

New build is up! Download from here: https://github.com/resident-nokia/android_device_nokia_A1N-TWRP/releases/tag/v3.5.2
Updated TWRP to version 3.5.2
Up-to-date umbrella kernel
Updated decryption blobs to Q
Use common FBE TWRP decryption strategy (should fix most issues with decryption)

emufan4568 said:
New release is up! Download from here: https://github.com/GPUCode/android_device_nokia_nb1_TWRP/releases/tag/twrp-3.4.0-0-2-2
* Allow wiping of System partition
* Fixed OTA updates failing at Step 2 of flashing
Click to expand...
Click to collapse
now phone stuck at teamwin logo

[RECOVERY][UNOFFICIAL][3.5.2_10-0][dipper] TWRP Recovery for Xiaomi Mi 8

Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
{
"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
Prerequisites:
Unlocked bootloader
What's working?
- ADB
- MTP
- DECRYPT
- And more
Download:
twrp3.5.2_10-0
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Source code:
GitHub - LowTension/android_device_xiaomi_dipper: Device tree for build TWRP for Xiaomi MI 8(dipper) only.
Device tree for build TWRP for Xiaomi MI 8(dipper) only. - GitHub - LowTension/android_device_xiaomi_dipper: Device tree for build TWRP for Xiaomi MI 8(dipper) only.
github.com
GitHub - TeamWin/android_bootable_recovery
Contribute to TeamWin/android_bootable_recovery development by creating an account on GitHub.
github.com
Credits:
althafvly​

reserved

Anything different than the official one?

Installed without problems.
Works well on A-11
Thank you

250652 said:
Installed without problems.
Works well on A-11
Thank you
Click to expand...
Click to collapse
Thank you for your feedback.

Thankyou ZonaRMR
Does it work with LineageOS? Previous Official did not

vulongmos said:
Does it work with LineageOS? Previous Official did not
Click to expand...
Click to collapse
Official TWRP 3.5.0_9 works fine with official LOS.
I didn't get the point on this release yet, TWRP says their _10 versions are for devices released with Android 10, so _9 is correct for the good old Mi 8...

vulongmos said:
Thankyou ZonaRMR
Does it work with LineageOS? Previous Official did not
Click to expand...
Click to collapse
Do you mean that?
Moldeb said:
Official TWRP 3.5.0_9 works fine with official LOS.
I didn't get the point on this release yet, TWRP says their _10 versions are for devices released with Android 10, so _9 is correct for the good old Mi 8...
Click to expand...
Click to collapse
it makes sense to me since the Xiaomi Mi 8 received android 10 officially.

Moldeb said:
TWRP says their _10 versions are for devices released with Android 10
Click to expand...
Click to collapse
ZonaRMR said:
Mi 8 received android 10
Click to expand...
Click to collapse
Spot the difference. I'm on Android 10 as well of course, soon on Android 11 and the official TWRP _09 branch supports this. Could you please explain the benefits of your unofficial version? I'd like to understand the facts before considering a test.

Tried to compile it on my own with your device Tree.
Got Error
FAILED: ninja: '/[...]/out/target/product/dipper/obj/SHARED_LIBRARIES/libcryptfs_hw_intermediates/export_includes', needed by '/[...]/out/target/product/dipper/obj/SHARED_LIBRARIES/libcryptfsfde_intermediates/import_includes', missing and no known rule to make it
21:58:28 ninja failed with: exit status 1
Did something change on TWRP?
Greets and thanks

Updated to 3.5.2_10-0 (Based on Android 10)
Download: https://www.mediafire.com/file/fe9ttmec4vjc5nb/twrp3.5.2_10.0.img/file

How do i decrypt my Mi8 Dipper? i just formatted data and clean flashed and now have encrypted phone.

Arthur P. Dent said:
Tried to compile it on my own with your device Tree.
Got Error
FAILED: ninja: '/[...]/out/target/product/dipper/obj/SHARED_LIBRARIES/libcryptfs_hw_intermediates/export_includes', needed by '/[...]/out/target/product/dipper/obj/SHARED_LIBRARIES/libcryptfsfde_intermediates/import_includes', missing and no known rule to make it
21:58:28 ninja failed with: exit status 1
Did something change on TWRP?
Greets and thanks
Click to expand...
Click to collapse
Did you ever figure this out? I'm getting the same error trying to build official TWRP for the mi 8 Pro.
EDIT: Turns out you can get around the error by removing the line: "TARGET_HW_DISK_ENCRYPTION := true" from your BoardConfig.mk but I'm not sure if it will be able to decrypt.

Hi, all day trying to flash TRWP. I want to switch from miui.eu to lineageos, so I wipe data and then try to flash LOS. Nothing work and I decided to upgrade TWRP from FASTBOOT. Nothing work, the phone got stuck on fastboot. Then with MIflash I was able to install miui global, but now I simple cant install TWRP over the MI-Recovery 3.0
I'm using diferent TWRP versions and the following commands
Code:
fastboot flash recovery recovery.img
fastboot boot recovery.img
After that black screen for a few seconds and the it boot normally to MIUI and MI Recovery 3.0 still there. Dont know what to do or combination to use
Please help!!

nortuzar said:
Hi, all day trying to flash TRWP. I want to switch from miui.eu to lineageos, so I wipe data and then try to flash LOS. Nothing work and I decided to upgrade TWRP from FASTBOOT. Nothing work, the phone got stuck on fastboot. Then with MIflash I was able to install miui global, but now I simple cant install TWRP over the MI-Recovery 3.0
I'm using diferent TWRP versions and the following commands
Code:
fastboot flash recovery recovery.img
fastboot boot recovery.img
After that black screen for a few seconds and the it boot normally to MIUI and MI Recovery 3.0 still there. Dont know what to do or combination to use
Please help!!
Click to expand...
Click to collapse
Make sure all is working(adb, fastboot, USB port...)
Code:
fastboot flash recovery recoveryname.img
fastboot reboot recovery

Please @LowTension Could start Creation Of TWRP 3.6 Working on Android 12

Development [RECOVERY][UNOFFICIAL] OrangeFox for Xiaomi Mi11X / Redmi K40 / POCO F3 [R11.1][alioth]

{
"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
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 Recovery
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.
Information
Status: Unofficial
Version: R11.1_0
Release Date: 2021-12-14
Source Code: https://gitlab.com/OrangeFox
Device Tree: https://github.com/Pranav-Talmale/android_device_xiaomi_alioth-ofox
Kernel Source: https://github.com/Pranav-Talmale/android_kernel_xiaomi_alioth
Download:
AFH Link
Installation:
Flashing guide:
Method 1: Already having a custom recovery
1.Just flash the OFox zip in your existing recovery
Method 2: using Fastboot
1. Extract the recovery.img inside the ofox zip
2. open adb and use the following command :
3. Fastboot boot recovery.img
4.After booting in the recovery, Flash the OFox zip again to make it permanent
Note:
1.You will need to reflash recovery every time you flash a ROM.
2. Magisk Root is lost so flash Magisk if you need root after flashing Recovery.
3. HentaiOS is currently unsupported and won't be supported in the future.
Bugs:
Android 12 decryption unsupported.
Credits
* TeamWin - for TWRP
* The OrangeFox Team - for your hard work
* All our testers - for your patience and help
FEATURES:
* Supports Treble and non-Treble ROMs
* Updated with latest TWRP commits
* Password
* Support for MIUI and Custom ROMs
* Better language support
* Optimized versions of community scripts
* Fox theme engine:
- choice of theme (black, dark, etc)
- choice of color scheme
- choice of splash screen
* Alternative lockscreen
* And many more!
Source changelog:
https://wiki.orangefox.tech/changelog
Telegram channels:
- Support Group

Noice finally orangefox is here ! Thanks dev

im waiting for this so long its my favorite recovery

Is compatibile with xiaomi.eu based on android 12?

domthewizard said:
Is compatibile with xiaomi.eu based on android 12?
Click to expand...
Click to collapse
No.

Is this based on any of the two existing TWRP modifications for Poco F3 or is it a new approach? Reasons for asking is that they both come with their own type of bugs.

TheBrutalLicker said:
Is this based on any of the two existing TWRP modifications for Poco F3 or is it a new approach? Reasons for asking is that they both come with their own type of bugs.
Click to expand...
Click to collapse
I have tried to take the good parts of all the existing TWRPs and add my own modifications to make the recovery more stable. There will be regular updates almost every week, so make sure to check the download link almost every other day. For changelogs of the latest build, You can check the pinned message of the support group

Woahh... Nice... my fave recovery since Redmi note 5 Whyred.
Hope next build also has feature to automatic reflash ofox after flashing a rom.
Thanks.... will try this after i get home.

Vuska said:
Woahh... Nice... my fave recovery since Redmi note 5 Whyred.
Hope next build also has feature to automatic reflash ofox after flashing a rom.
Thanks.... will try this after i get home.
Click to expand...
Click to collapse
The auto reflash ofox feature won't be implemented until the ofox source developers add it. Till that time, you can just select ofox zip in the "add to queue" option so that it will reflash after the ROM flashes

Works great so far, xiaomi.eu stable 12.5.19 (android 11)
In fact, it works better than twrp, to do a backup with twrp I had to run the rm data/extm - Rf before I could backup, but with orange fox, it works normally, no commands needed
Thankyou for your work on this sir

It really works. Xiaomi.eu stable 12.5.19. Backup also works, only restoration does not work ERROR: 255
Many Thanks

varadinum said:
It really works. Xiaomi.eu stable 12.5.19. Backup also works, only restoration does not work ERROR: 255
Many Thanks
Click to expand...
Click to collapse
Backups
wiki.orangefox.tech

Cant use fastbootd on my Redmi K40(Android 11)

But other function work well

eee625 said:
Cant use fastbootd on my Redmi K40(Android 11)View attachment 5528595
Click to expand...
Click to collapse
I have noted down the issue. It seems I had not added fastbootd functionality. I am working on a fix and will release a new build soon

Ok,thank you for fixing this

Pranav Talmale said:
I have noted down the issue. It seems I had not added fastbootd functionality. I am working on a fix and will release a new build soon
Click to expand...
Click to collapse
Any chance of A12 decryption like the twrp skkk where if you don't have a lock screen, it can decrypt?

regedit12345 said:
Any chance of A12 decryption like the twrp skkk where if you don't have a lock screen, it can decrypt?
Click to expand...
Click to collapse
I don't know what black magic that guy has done to achieve that, since his trees are private (they are not on github) and I've tried contacting him 2-3 times. All I got was no response. And I myself have tried to figure it out on my own more than 5-10 times, still no luck. So I don't think I'll be able to implement a12 decryption until TWRP officially supports it.

Pranav Talmale said:
I don't know what black magic that guy has done to achieve that, since his trees are private (they are not on github) and I've tried contacting him 2-3 times. All I got was no response. And I myself have tried to figure it out on my own more than 5-10 times, still no luck. So I don't think I'll be able to implement a12 decryption until TWRP officially supports it.
Click to expand...
Click to collapse
You're doing a good job either way. Keep it up.
The only reason I switched back to twrp from orangefox was it woudnt virabte on touch so I couldn't figure out if the recovery is fully functional and I can start using it or its still booting.

regedit12345 said:
You're doing a good job either way. Keep it up.
The only reason I switched back to twrp from orangefox was it woudnt virabte on touch so I couldn't figure out if the recovery is fully functional and I can start using it or its still booting.
Click to expand...
Click to collapse
Are you using the latest build ? Vibration has been fixed a long time ago. Please use the latest build. Latest build I pushed was on 1st February