{
"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
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Red Wolf Recovery is custom recovery based on TWRP source code however some things are working here slightly different then you might expected. The main objective of this project is to provide stable recovery with features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. This recovery is also first recovery on the world with password protection.
Based on TWRP version: 3.2.1
For device: X00TD
Authors build: ATG Droid
Features
Code:
Translated to EN & CZ
- Password protection
- Flashlight
- MIUI Incremental OTA Support
- Built-in latest Magisk, SuperSU & AromaFM
- Support two screenshot GUI actions - Power+VolDown to save screenshot in to the internal storage &
Power+VolUp to save screenshot in to the external storage (Will be automatically saved in to the internal in case
that external storage doesn't exist).
- Support automatic reboot after the restore process
- Recovery can automatically modify some props in the ROM directly during the installation
- Some built-in scripts from community
- Tap to wake support
- Advanced deactivation of the stock recovery
- Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- Support "set on boot" settings.
* Changes for security reasons *
- ADB isn't starting automatically at the start of the recovery. You have to activate it in recovery
- MTP isn't starting until user enter correct password
- Deactivated TWRP theme engine
Some differences to the official version:
Code:
[COLOR="red"]- get out of here if you are pirating apps. this recovery is not for you[/COLOR]
- always up-to-date with the latest TWRP changes
- compiled on omnirom-7.1 source
- kernel compiled inline with the recovery
- There isn't bug with reboot from recovery to recovery
- more languages
- other improvements from Features and Changelog lists
Changelog
Code:
20180510: Initial Build
Code:
20180522: Fixed brightness, all partition support
Installation instructions:
Flash using fastboot method or in recovery as IMG..
Known Bugs:
- None
Downloads:
RedWolf-027-Unofficial-X00TD.img
AFH
Fastboot Flashing Code
Code:
[CENTER]fastboot flash recovery RedWolf-027-Unofficial-X00TD-20180522.img[/CENTER]
Screenshots
Device Tree
Kernel Source
Warning:
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery.
XDA:DevDB Information
[RECOVERY]Red Wolf Recovery Project [X00TD], Recovery for the Asus ZenFone Max Pro M1
Contributors
Shivam Kumar Jha
Source Code: https://github.com/RedWolfRecovery
Version Information
Status: Testing
Created 2018-05-08
Last Updated 2018-05-22
Reserved for FAQ
Great !
Thanks sir, i never use this recovery, TWRP is my favorite.
is this same with TWRP ?
gusbalaa said:
Great !
Thanks sir, i never use this recovery, TWRP is my favorite.
is this same with TWRP ?
Click to expand...
Click to collapse
It's better than that... do a try
- MIUI Incremental OTA Support
Click to expand...
Click to collapse
So I assume that RWRP support official OTA?
dimedevil said:
So I assume that RWRP support official OTA?
Click to expand...
Click to collapse
Yes
support ota update???
F4217 said:
support ota update???
Click to expand...
Click to collapse
Yes
anisgvr said:
Yes
Click to expand...
Click to collapse
Have you tried doing an OTA with this recovery? Didn't work for me on Zenfone Max Pro
nrp31 said:
Have you tried doing an OTA with this recovery? Didn't work for me on Zenfone Max Pro
Click to expand...
Click to collapse
Worked for me .. that's advantage of red wolf :good:
Awesome work dev.
Ota update
Shivam Kumar Jha said:
Reserved for FAQ
Click to expand...
Click to collapse
Will we still get OTA update after flashing custom recovery and rooting via magisk??
Ak-64 said:
Will we still get OTA update after flashing custom recovery and rooting via magisk??
Click to expand...
Click to collapse
No
gusbalaa said:
No
Click to expand...
Click to collapse
Sir, is there a way by which we can manually download the update files and flash it?? If we can will it unroot the device?
Ak-64 said:
Sir, is there a way by which we can manually download the update files and flash it?? If we can will it unroot the device?
Click to expand...
Click to collapse
I was looking for flash the stock firmware, with fastboot/something that can restore my device to full to factory (example : restore to stock if got bootlooop). But i can't find it now, that's the reason why I'm not rooting my device yet.
Ak-64 said:
Will we still get OTA update after flashing custom recovery and rooting via magisk??
Click to expand...
Click to collapse
gusbalaa said:
No
Click to expand...
Click to collapse
so we need to unroot , remove all system mods
then we can ota right? but still keeping the rwrp??
anantos said:
so we need to unroot , remove all system mods
then we can ota right? but still keeping the rwrp??
Click to expand...
Click to collapse
i think we need stock boot and recovery,
also locked bootloader to still get ota.
As long i can remember OTA can't installed on unlocked bootloader.
Correct me if wrong.
gusbalaa said:
i think we need stock boot and recovery,
also locked bootloader to still get ota.
As long i can remember OTA can't installed on unlocked bootloader.
Correct me if wrong.
Click to expand...
Click to collapse
OTA can be installed with TWRP but it needs some special steps like,
Modify updater-script in update.zip and flash it in TWRP after unroot and removing Xposed
OR
Download full ROM package and install it via TWRP and re-root the rom.
OR
Apply OTA directly after unroot if TWRP supports it.Which one is applicable here is still not known.
Also it is recommended to keep bootloader unlocked if you do not have stock recovery, so all above steps are with unlocked bootloader.
Better keep the device integrity intact before we have tested UNBRICK with fastboot mode .. then we can take calculated risks.
.A.V.i.n.a.S.h. said:
OTA can be installed with TWRP but it needs some special steps like,
Modify updater-script in update.zip and flash it in TWRP after unroot and removing Xposed
OR
Download full ROM package and install it via TWRP and re-root the rom.
OR
Apply OTA directly after unroot if TWRP supports it.
Which one is applicable here is still not known.
Also it is recommended to keep bootloader unlocked if you do not have stock recovery, so all above steps are with unlocked bootloader.
Better keep the device integrity intact before we have tested UNBRICK with fastboot mode .. then we can take calculated risks.
Click to expand...
Click to collapse
Thanks for the correction.
I just keep my devices fully stock without any mods or something, agree with you no news about unbrick with fastboot mode. So I'm gonna wait for it.
img file is corrupted
OrangeFox Recovery Project
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* 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.
*
*/
OrangeFox is FREE SOFTWARE
Supports Treble, Miui, Custom Roms
Downloads:
1. OrangeFox download site: https://files.orangefox.tech/OrangeFox-Stable/dipper/
2. SourceForge: https://sourceforge.net/projects/orangefox/files/dipper/
Release Notes:
1. See README.md here: https://sourceforge.net/projects/orangefox/files/dipper/
2. Read very carefully the contents of post #2 below.
Documentation and Frequently Asked Questions: https://wiki.orangefox.tech/en/guides
INSTALLATION:
0. Backup your ROM, your data, your internal storage, and your settings/apps, to an external device
1. Download the OrangeFox zip file to your device
2. Reboot to your current OrangeFox or custom TWRP-based Recovery
3. Install the OrangeFox zip file as a normal zip
4. The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)
5. Enjoy!
Frequently Asked Questions; Installation from stock recovery; MIUI OTA; Troubleshooting; Sundry Information:
* See https://wiki.orangefox.tech/en/guides
Credits
* TeamWin - for TWRP
* The OrangeFox Team - for your hard work
* All our testers - for your patience and help
FEATURES:
* Updated with latest TWRP commits
* Built-in support for installing init.d functionality
* Built-in support for installing Magisk
* Flashlight
* Password, torch, led
* Support for Miui and Custom ROMs
* 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!
Screenshots
see https://files.orangefox.tech/Screenshots/R10/
Other useful information - see below
XDA:DevDB Information
OrangeFox Recovery Project, Tool/Utility for the Xiaomi Mi 8
Contributors
DarthJabba9, MrYacha
Source Code: https://gitlab.com/OrangeFox
Version Information
Status: Stable
Current Stable Version: R10.1
Stable Release Date: 2020-04-08
Created 2020-01-23
Last Updated 2020-04-08
R10.0_1_001 Beta released
I have released OrangeFox R10.1 Beta 001.
Downloads:
OrangeFox download site: https://files.orangefox.tech/OrangeFox-Beta/dipper/
Sourceforge: https://sourceforge.net/projects/orangefox/files/dipper/
Changelog (General for R10.1): https://wiki.orangefox.tech/en/changelog#orangefox-r101
Device-specific changes:
- Fixed language translations
- Updated the initd addon to use Anykernel3 (better support for system-as-root devices)
FAQ and Guides: https://wiki.orangefox.tech/en/guides
Backup and restore
Read this post for detailed advice. Do not try to backup/restore anything without first reading it.
Incremental MIUI OTA:
Due to recent changes in stock MIUI, you must not disable DM-Verity when flashing a stock MIUI ROM that is based on either Android Pie, or Android 10 (the relevant option in OrangeFox is now unticked by default). If you disable DM-Verity, incremental MIUI OTA updates will definitely not work.
Reserved
Thank you. Does it allow you to bakcup and restore the persist partition?
Boiisxu said:
Thank you. Does it allow you to bakcup and restore the persist partition?
Click to expand...
Click to collapse
Yes.
DarthJabba9 said:
Yes.
Click to expand...
Click to collapse
I'll try it, thank you.
Nice work mate. But can it flash persist.img directly from the menu? Thanks!
JonathanFreeze said:
Nice work mate. But can it flash persist.img directly from the menu? Thanks!
Click to expand...
Click to collapse
Should be fine.
I have Orangefox R10.0-3, and I cannot install R10.0-4 or the new beta R10.1. I tried both flashing from bootloader with fastboot commands (recovery.img) and installing the R10.1 beta zip from Orangefox R10.0-3. Phone won't boot to recovery and will just reboot to android. I have install.log but have less than 10 posts and have no idea how to attach files. I'll PM you with the log.
Xiaomi063 said:
I have Orangefox R10.0-3, and I cannot install R10.0-4 or the new beta R10.1. I tried both flashing from bootloader with fastboot commands (recovery.img) and installing the R10.1 beta zip from Orangefox R10.0-3. Phone won't boot to recovery and will just reboot to android. I have install.log but have less than 10 posts and have no idea how to attach files. I'll PM you with the log.
Click to expand...
Click to collapse
How did you flash from fastboot? You extracted the image file from the zip?
Xiaomi063 said:
I have Orangefox R10.0-3, and I cannot install R10.0-4 or the new beta R10.1. I tried both flashing from bootloader with fastboot commands (recovery.img) and installing the R10.1 beta zip from Orangefox R10.0-3. Phone won't boot to recovery and will just reboot to android. I have install.log but have less than 10 posts and have no idea how to attach files. I'll PM you with the log.
Click to expand...
Click to collapse
The log that you sent to me by PM looks perfectly fine, and everything should work.
Judging from what you said in the other thread where you first explained your problems, I think that something is seriously broken in your device. It may be that your bootloader has been modified by something you flashed before. In the previous thread, you describe the current situation. But what you have not told us is exactly how you got here in the first place. Without that information, one can only speculate. And my speculation is that the recoveries (whether flashed in fastboot or recovery mode) install correctly. However, something in the modified bootloader is ignoring them (or perhaps your partition sizes are borked). If this speculation is correct, then I think you might have to flash a full fastboot MIUI ROM (of whatever ROM came with the phone in the first place) and let it wipe everything (just don't accidentally lock your bootloader again). This should reset the partitions and also replace the recovery partition with stock MIUI recovery. Then you can start all over again by flashing an OrangeFox img with fastboot.
But unless you can retrace all your steps to identify what you originally flashed that started all these problems (and avoid it in the future) you might well end up in the same situation again.
DarthJabba9 said:
The log that you sent to me by PM looks perfectly fine, and everything should work.
Judging from what you said in the other thread where you first explained your problems, I think that something is seriously broken in your device. It may be that your bootloader has been modified by something you flashed before. In the previous thread, you describe the current situation. But what you have not told us is exactly how you got here in the first place. Without that information, one can only speculate. And my speculation is that the recoveries (whether flashed in fastboot or recovery mode) install correctly. However, something in the modified bootloader is ignoring them (or perhaps your partition sizes are borked). If this speculation is correct, then I think you might have to flash a full fastboot MIUI ROM (of whatever ROM came with the phone in the first place) and let it wipe everything (just don't accidentally lock your bootloader again). This should reset the partitions and also replace the recovery partition with stock MIUI recovery. Then you can start all over again by flashing an OrangeFox img with fastboot.
But unless you can retrace all your steps to identify what you originally flashed that started all these problems (and avoid it in the future) you might well end up in the same situation again.
Click to expand...
Click to collapse
I bought this phone second hand, it already had bootloader unlocked and came with TWRP wzsx150 installed. It had MIUI 11 global, not sure the exact version (11.0.1, 11.0.2...) but it was android 9, and the same day I got it I installed the latest xiaomi.eu beta rom on it, before trying to install other custom roms or installing another recovery.
I already tried flashing full fastboot MIUI Global rom using fastboot with MiFlash software, tried two versions: 11.0.6.0 and 10.1.2.0. When doing that the same happens, MIUI works correctly and I can install xiaomi.eu roms but not any other custom rom and only a reduced number of recovery versions.
Is there anything more I should check? like partition format or partition size? should I format all partitions?
I used MiFlash 20180528, not the latest version, don't know if this could affect the flashing process...
Xiaomi063 said:
I bought this phone second hand, it already had bootloader unlocked and came with TWRP wzsx150 installed. It had MIUI 11 global, not sure the exact version (11.0.1, 11.0.2...) but it was android 9, and the same day I got it I installed the latest xiaomi.eu beta rom on it, before trying to install other custom roms or installing another recovery....
Click to expand...
Click to collapse
Flashing a full fastboot ROM with the Mi Flash tool should have sorted out any problems. That is normally a last resort, and it should work. If it didn't work, then I am out of ideas. This might well be some sort of ARB issue - but I have no experience at all with ARB, so I can't tell. Perhaps it was already broken before it was sold to you. Who knows?
I know of no reason why the device should be happy with some recoveries, and not with others. There is no logic to it, that I can see.
Unfortunately, this discussion is now off-topic, as this is not a recovery issue (I thought it might have been - but it is obvious that it isn't). I guess you might have to cut your losses and stick with whatever recoveries and ROMs work with your device - and perhaps return to wzsx150 and the most recent MIUI Global (which would avoid ARD issues). Good luck!
I flashed the last stable version and it works flawlessly. I love that it flashes dfe automatically.
However, I don't know If I can use my old backups made by the twrp i was using, can I?
Thanks you!
Boiisxu said:
.... However, I don't know If I can use my old backups made by the twrp i was using, can I?
Click to expand...
Click to collapse
You can always try - but I wouldn't hold out much hope. It all depends on whether the partition tables are compatible. Also, OrangeFox expects its backups to be in /Fox/BACKUPS/ whereas twrp looks somewhere else - so there has to be some renamings of directories if OrangeFox is to be able to locate the backups.
Does the latest beta support encryption?
I am using xiaomi.eu ROM
Irish_Dude said:
Does the latest beta support encryption?...
Click to expand...
Click to collapse
Yes.
Many thanks for keeping OF for Mi8 dude
This is the best recovery so far imho
Adriano-A3 said:
Many thanks for keeping OF for Mi8 dude
This is the best recovery so far imho
Click to expand...
Click to collapse
Yeah it takes so much headache out of flashing that is unparalleled
arifqur said:
Yeah it takes so much headache out of flashing that is unparalleled
Click to expand...
Click to collapse
Thanks (also to @Adriano-A3).
The question now is whether the last beta is robust enough to turn it into a "Stable" release ...
{
"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"
}
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