[RECOVERY][3.5.2_9-2][Mi A2 Lite] Unofficial TWRP recovery for Xiaomi Mi A2 Lite - Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth

[RECOVERY][3.5.2_9-2][Mi A2 Lite] Unofficial TWRP recovery for Xiaomi Mi A2 Lite - Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Open Source
- Payload.bin support (ROM flashing works)
- Proper MTP support (for both 4.9 and 3.18 kernels)
- Working decryption for both FBE and FDE
- Adoptable Storage is working
- Android 11 support (No bootloops to recovery mode)
- NTFS, F2FS, exFAT, FAT32 support for SD Cards and USB drives
- Ability to flash splash images directly to the splash partition
- Adjusted theme to account for the notch (the clock doesn't overlap with the notch)
- No TWRP app installation prompts
- Older 3.4.0 button-style reboot menu instead of the newer listbox-style one
- Addon.d script to make TWRP survive ROM updates
Download:
TWRP image: https://drive.google.com/file/d/19ysSbW31NG4QF5OClbox-mArIb17KbpT/view?usp=sharing
TWRP Installer: https://drive.google.com/file/d/1-wk_0kOe_e-2XDDiv08BxJhn1ixWXjUw/view?usp=sharing
Installation Instructions:
- Make sure your bootloader is unlocked. If not, unlock it first.
- Reboot to Bootloader (aka Fastboot mode)
- Execute:
Code:
fastboot boot twrp-3.5.2_9-2-daisy-unofficial.img
- Flash the TWRP Installer zip to keep TWRP permanently
Notes:
- You can ignore any "Failed to unmount /vendor: Device or resource busy" errors since they do not cause any issues (this
happens when switching the active slot while the vendor partition is mounted).
- This TWRP does not have the newer 3.5.0 theme changes in the reboot menu because it is confusing for a significant amount
of users and does not match the rest of the button-style design.
- The TWRP app checks and prompts have been completely removed due to the app causing a lot of issues including bootloops
since it is not designed for A/B devices.
- The portrait_hdpi theme has been adjusted to have more padding in the status bar and to account for the presence of the
notch (the clock's position has been modified in order for the clock not to get overlapped by the notch)
- TWRP's addon.d will only work in the following scenarios:
a) When updating your ROM through the ROM's Updater application
b) When dirty-flashing a newer build of the same ROM you have installed from recovery
- TWRP's addon.d (TWRP survival) may not work in all ROMs as some ROMs choose not to have permissive update-engine domain. This essentially results in SELinux denials, preventing the addon.d script from executing when SELinux is enforcing. You can read more about the said issue here (https://github.com/topjohnwu/Magisk/commit/cba0d040000d6ff38c6646bb9d7daa12beae2878)
Source code:
Recovery Source: https://github.com/LinkBoi00/android_bootable_recovery
Device tree: https://github.com/LinkBoi00/twrp_device_xiaomi_daisy
Kernel source: https://github.com/LinkBoi00/twrp_kernel_xiaomi_daisy
XDA:DevDB Information
TWRP-3.5.2_9-2-Unofficial, Tool/Utility for the Xiaomi Mi A2 Lite
Contributors
LinkBoi
Source Code: https://github.com/LinkBoi00/twrp_device_xiaomi_daisy
Version Information
Status: Stable
Current Stable Version: 3.5.2_9-2
Stable Release Date: 2021-05-04
Created 2020-10-19
Last Updated 2021-05-04

Reserved

Reserved

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

hi, is there any plan to support encryption??

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

Related

[RECOVERY][arm64]TWRP Recovery [3.2.2-r1] [10 July 18]

is it compatible with shreps twrp backup?

Ayan Uchiha Choudhury said:
is it compatible with shreps twrp backup?
Click to expand...
Click to collapse
Yes, should work :good:

thanksss dev for your work dev
i have noob qn
can i restore aosp oreo Rom data backup to lineage rom without problem

arun4777 said:
thanksss dev for your work dev
i have noob qn
can i restore aosp oreo Rom data backup to lineage rom without problem
Click to expand...
Click to collapse
That's not related to twrp. Restoring the whole data partition from one rom to another causes problems for sure. Better to use titanium backup and backup/restore user apps with it.

This should work with the G4 (Regular non Plus model) Right?

Vaizen said:
This should work with the G4 (Regular non Plus model) Right?
Click to expand...
Click to collapse
Yes [emoji106]
Sent from my Moto G4 Plus using Tapatalk

tywinlannister7 said:
Yes [emoji106]
Click to expand...
Click to collapse
Actually it didn't let me flash latest RR. Had to flash official version for it to flash correctly.

Update: 30 Dec 2017
Changelog
*Add support for flashing 64 bit ROMs
*Fix bugs from -r1 except encryption :3
Download:
https://sourceforge.net/projects/twrp-athene/files/twrp-3.2.1-r2-arm64-tywinlannister7.img/download

tywinlannister7 said:
Changelog
*Add support for flashing 64 bit ROMs
*Fix bugs from -r1 except encryption :3
Download:
https://sourceforge.net/projects/twrp-athene/files/twrp-3.2.1-r2-arm64-tywinlannister7.img/download
Click to expand...
Click to collapse
Will i able to flash 32 bit also and does backup restores?

Can I Flash 32 bit ROM and 64 with this recovery?

Luis Infante said:
Can I Flash 32 bit ROM and 64 with this recovery?
Click to expand...
Click to collapse
Yes u can

StevenFernandes said:
Yes u can
Click to expand...
Click to collapse
Thanks

i m facing a minor bug in my recovery it does not show exact time of device
and i had to set wrong time zone for see accurate time in recovery ......
is it a known bug?? or am i the only one facing it?
im on LOS 15.1 WITH stock kernal
thanks for fast update dev????

arun4777 said:
i m facing a minor bug in my recovery it does not show exact time of device
and i had to set wrong time zone for see accurate time in recovery ......
is it a known bug?? or am i the only one facing it?
im on LOS 15.1 WITH stock kernal
thanks for fast update dev
Click to expand...
Click to collapse
It's a bug found on many twrp builds. I don't know if it's device specific.

I notice they Ghost touch with they USB cable and PC connected for ADB Sideload (and this affect to the ROMs)
---------- Post added at 02:20 AM ---------- Previous post was at 02:17 AM ----------
I forgot to say that in this recovery for arm64 3.2.1.0 I don't have the arrow of the mouse appearing sometimes in the center of the screen (always on recovery, and sometimes on the system)

When i flash via fastboot the reovery, fastboot send me this error?
target reported max download size of 536870912 bytes
sending 'recovey' (14840 KB)...
OKAY [ 0.589s]
writing 'recovey'...
(bootloader) Invalid partition name recovey
FAILED (remote failure)
finished. total time: 0.597s
Click to expand...
Click to collapse

striplex said:
When i flash via fastboot the reovery, fastboot send me this error?
Click to expand...
Click to collapse
Yeah, see what you type: "recovey" but the partitions name is recovery

work roms 32 and 64 bits?

biel.paes said:
work roms 32 and 64 bits?
Click to expand...
Click to collapse
If you looked a few posts before you would clearly know that, yes, this build of twrp supports both 32 and 64 bit roms. Please use the search function before posting!

[Project Treble][UNOFFICIAL] for Wileyfox Swift 2/Plus/X

/*
* Your warranty is... still valid?
*
* 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.
*
*/
Click to expand...
Click to collapse
Project Treble
Important!
Recommended for installation only for advanced users***What is Project Treble? ***
Project Treble allows to install - Generic System Images on our device with a minimum number of bugs.
Vendor - this is partition where proprietary files and drivers are stored, which are separate from the system.
***Userful Information***
Project Treble XDA Thread
Generic System Image (GSI) list
***Development and bugs***
Development has been started about 3 months. backwards During this time, dozens of errors were corrected and millions of nerve cells were lost.
Vendor is based on the stock firmware UOS273C with a large number of edits.
The kernel is used from vm03 with driver edits for working on Project Treble.
Bugs in Generic System Images:
On Oreo and Pie GSIs don't working SafetyNET.
My Magisk Module: Wileyfox Swift 2 SafetyNet Pass
Bugs in Vendor:
SELinux Permissive
For the fingerprint scanner to work correctly before being added to Settings, it is necessary to “poke” 5-6 times into it, for the driver to load correctly.
***Preparing device for support Project Treble***
Download TWRP Treble
Repartition script 16GB or 32GB
Download Treble Vendor
Download Treble Boot
Mirror on Google Drive
Mirror on Cloud Mail.ru
If you want get back default partition table just flash:
Download Revert - 16GB
Download Revert - 32GB
You need to copy all the necessary information to an external memory card or PC, since the internal memory will be formatted and devided into special partitions for Project Treble can work.

Install TWRP Treble in a convenient way for you.
Install Repartition script in TWRP. Depending on your internal memory size.
After installing repartition script, device will automatically reboot into Recovery, where you must do:
Format Data (Wipe > Format Data)
Wipe Vendor (Wipe > Advanced Wipe > Vendor)
After that necessarily to reboot the Recovery (Reboot > Recovery)
Flashing Treble Vendor (Just install zip archive)
Flashing Treble Boot (Select the option in the lower right corner Install Image, select Boot_Treble_new.img and flash it as Boot Image)
Install your favorite firmware (about this below). (Select the option in the lower right cornerInstall Image, than flash it as System Image)
***Installing Android Oreo or Android Pie GSIs***
Flash any GSi from Generic System Image (GSI) list or XDA Thread
always choose arm64 A-ONLY!
* If camera don't working on Pie flash:
Camera Pie GSI patch
* If the NFC item in the settings hangs, or the NFC does not turn on (this is usually the case in the old October GSI), flash:
NFC all GSI Patch
* Patch for fix fingerprint scanner on some Pie GSIs
Folder with patches
For ArrowOS GSI, HavocOS 2.0, AEX 6.1 fix not needed.
***Google Apps***
Install GApps only before the first launch of the ROM!
Open GApps Project
***Thanks***
Testing and moral support:
Kirill_MegaFon (4PDA)
xyzmean (4PDA)
Zent16 (4PDA)
backspace696 (4PDA)
Help in bug fixes and kernel sources:
vm03 (XDA)
Mirrors for download files:
anatoliy-is (4PDA)
Fingerprint overlay:
creativchic (4PDA)
XDA:DevDB Information
[Project Treble][UNOFFICIAL] for Wileyfox Swift 2/Plus/X, ROM for the Wileyfox Swift 2
Kernel Sourses
DevelopedInside
Contributors
fx-mod
ROM OS Version: Android 8.1.x and Android 9.x
Version Information
Status: Beta
Created 2018-09-30
Last Updated 2018-09-30

Never heard of 'Project Treble' before, but it sounds very interesting to be able to use 'Generic System Images'.
Before playing around with it - can you please also provide a 'Repartition Script' to get back to the default Partitioning ?

fred0r said:
Never heard of 'Project Treble' before, but it sounds very interesting to be able to use 'Generic System Images'.
Before playing around with it - can you please also provide a 'Repartition Script' to get back to the default Partitioning ?
Click to expand...
Click to collapse
To return the phone to stock, just install Factory Firmware.

fred0r said:
Never heard of 'Project Treble' before, but it sounds very interesting to be able to use 'Generic System Images'.
Before playing around with it - can you please also provide a 'Repartition Script' to get back to the default Partitioning ?
Click to expand...
Click to collapse
Done!

i installed treble according to your instruction and flashed a AOSP 8.1 image (system-arm64-aonly-gapps-su.img.xz) which should include gapps and su.
unfortunately the su-part wasnt available, so i tried to boot into the recovery by selecting it during the start of the phone - but i instantly came back to the 'boot-screen' without starting twrp.
for now the only way to get back on the 'treble-twrp' i need to boot it via fastboot (fastboot boot TWRP_Treble_marmite.img)
i this a bug or am i doing something wrong ?
[edit]
installed another rom which had the option in developers to reboot directly into the recovery - that worked.
---------- Post added 5th October 2018 at 12:12 AM ---------- Previous post was 4th October 2018 at 11:43 PM ----------
Now i installed the latest Oreo Resurrection-Remix from https://downloads.resurrectionremix.com/arm64aonly/ and during startup:
{
"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"
}
Another thing is, that on all GSI-Images i installed so far the system-fonts are very tiny - like it's using a too high screen-resolution.

fred0r said:
......so i tried to boot into the recovery by selecting it during the start of the phone - but i instantly came back to the 'boot-screen' without starting twrp.
for now the only way to get back on the 'treble-twrp' i need to boot it via fastboot (fastboot boot TWRP_Treble_marmite.img)
i this a bug or am i doing something wrong ?
Click to expand...
Click to collapse
Nevermind - it works also to boot from the start. i needed first to select 'boot recovery' and then press on 'start' to boot into it.
Just installed the GSI from PixelExperience from pixelexperience.org and also get that 'vendor mismatch' message.

fred0r said:
Nevermind - it works also to boot from the start. i needed first to select 'boot recovery' and then press on 'start' to boot into it.
Just installed the GSI from PixelExperience from pixelexperience.org and also get that 'vendor mismatch' message.
Click to expand...
Click to collapse
I had this issue too and I believe flashing the vendor zip again did the job for me, not completely sure though.

xXxSAMIxXx said:
I had this issue too and I believe flashing the vendor zip again did the job for me, not completely sure though.
Click to expand...
Click to collapse
vendor miscmatch message is a warning. Not an error!

a great work ..soon i will get this device

I'd like to try out Android P. Has anyone tried this with a Swift 2 device and can recommend a GSI to use?
Edit: I couldn't get Pixel Experience (9.0) to boot succesfully but phhusson's AOSP 9.0 works. It's very barebones indeed. Someone made an overlay that makes adaptive brightness possible but I still can't adjust the LED for notifications. Not being able to turn off the charging/low-battery LED is a bummer. Otherwise it runs fine but I'll try a different GSI today.

Did you use the arm64 a-only image? I tried the arm a-only and that wouldn't boot but I'm (quite) happily buzzing along with the former.

fx-mod said:
* Patch for fix fingerprint scanner on some Pie GSIs
Phh AOSP 9 v106 [02/10/2018] only
ArrowOS 9 [23/09/2018] only
Pixel Experience P [20/09/2018] only
Click to expand...
Click to collapse
Is it possible to update the Pixel Experience P fingerprint scanner patch? The latest version of the ROM fixes the hotspot issues but the fingerprint scanner patch does not work.

erasmuswill said:
Is it possible to update the Pixel Experience P fingerprint scanner patch? The latest version of the ROM fixes the hotspot issues but the fingerprint scanner patch does not work.
Click to expand...
Click to collapse
it is done!

wileyfox swift 2X with 32GB storage.
32 gb repartition file ? or should i use 16 gb ?
just to be sure i'm not destroying my phone

waver1967 said:
wileyfox swift 2X with 32GB storage.
32 gb repartition file ? or should i use 16 gb ?
just to be sure i'm not destroying my phone
Click to expand...
Click to collapse
32 GB of course

failed to mount system
after doing all the steps twrp says no os installed

oeps my mistake..
forgot to unrar gsi file

Is it possible to patch at least one of Pie GSI's to work almost perfectly? Right now it is not possible to use any of GSI's for more than a week because every one have some annoying bugs

puszekkk said:
(
Click to expand...
Click to collapse
What does not suit you?

anatoliy-is said:
What does not suit you?
Click to expand...
Click to collapse
Broken hotspot, dumped fingerprints after reboot, broken wifi, broken audio routing :/

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

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

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

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

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

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

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

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

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

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

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

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

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

Thank you
Sent from my Redmi Note 9 Pro using Tapatalk

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

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

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

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

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

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

PBRP [Joyeuse][v2.9.1]

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

GREAT JOB!

Works on curtana? thanks

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

All right, will try later. ?

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

any one test it? any bug?

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

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

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

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

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

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

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

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

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

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

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

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

thanks
Sent from my Redmi Note 9 Pro using Tapatalk

[ROM] [12.1] [TREBLE] [UNOFFICIAL] [Gapps/Vanilla] CherishOS V3.9.5 for Nokia 8 [NB1] [DISCONTINUED FOR A13]

{
"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.
*/
CherishOS is an AOSP based rom focusing on a Unique UI with many customizations.
Known bugs
- Loudspeaker is loud and creates some echo in calls
- TWRP recovery does not decrypt internal storage with a pin set, this is TWRP's fault, but does not affect OTAs, cancel when prompted for pin it will say its incorrect. [fixed with latest twrp]
- Offline charging animation does not work [FIXED in 3.5.2]
- SIM2 mobile data does not work (for dual sim users) but the sim itself works fine [FIXED in 3.5.2]
- gyro sensor creates a drift in some games [FIXED in 3.6]
- requires flashing atomix zip for WPA2 hotspot to work (attached) < now included, needs test. [no longer required]
- you tell me
Please ensure T-virus-2.0 is installed before attempting to flash this rom! follow this guide here: https://forum.xda-developers.com/t/nokia-8-nb1-full-rom-installation-guide.4349525/
Selinux status: Enforcing
Download
ROM
Release CherishOS 3.9 [12.1] [Gapps/Vanilla] [Unofficial] · megafire91/NB1-CherishOS_Releases
CherishOS for NB1 treble only [T-virus 2.0 required] Changelog: https://t.me/CherishOS/1120 Device changelog: Changed to LOS camera to resolve not saving issues Audio visualiser now working Offlin...
github.com
Recovery
TWRP:
Release TWRP 3.6.2 A12.1 for NB1 · Niemandausduisburg/android_device_nokia_A1N-NB1-TWRP-new
TWRP 3.6.2 A12.1 for Nokia 8 (NB1) Flashable bootimage & flashable zip availible. Known Features xD: - MTP / ADB don't work sometimes. To fix disable & re-enable MTP in Mount-options. - ADB sidelo...
github.com
The Zip installer is used for easier access when flashing roms, the img is there in case you have forgotten to flash the zip and have lost recovery.
Flashing instructions
Clean Flash:
1. Take a full backup of both your data and internal storage as it may be wiped.
2. Download the ROM from above link and flash the recovery zip
3. Download the recovery zip of your choosing and flash it if not already on latest twrp.
4. boot into recovery and either remove rom pin or wipe internal to have it accessible to copy rom zip over (due to the decryption bug) or just use external sd card to flash.
5. flash the rom zip and recovery zip again right after the rom zip before rebooting , it will reboot you to recovery automatically in other slot. (optional) cherish recovery included.
6. Flash any mods you may want
7. run factory reset from recovery, or wipe /data and /dalvik if you don't want internal wiped.
8. reboot to system and enjoy!
(flashing Atomix zip is only needed if you flash the .img to fix hotspot, but not with the zip)
Installing an OTA (Dirty flash):
1. Download the ROM from above link
2. flash the rom zip and recovery zip and let it reboot into recovery.
3. wipe Dalvik cache only
4. flash any mods you had previously flashed.
5. reboot to system and enjoy!
(flashing Atomix zip is only needed if you flash the .img to fix hotspot, but not with the zip)
Device support:
https://t.me/HMD_Nokia_8
Credits
Me for building the rom
@emufan4568 for the NB1 device and vendor tree, atomix kernel and TWRP.
Rany42 for all his help and contribution and for using his device trees, he doesn't have an XDA account.
@oaid for contribution to vendor tree and atomix kernel and countless hours of bug fixing
@CherishOS team for the amazing ROM
@THMSP for T-virus
all users in our telegram groups that helped us contribute and find bugs as well as sent us logs.
if i missed anyone in credits please let me know and ill add you to this list.
coffee:
Pay Marcel Dos Santos using PayPal.Me
Go to paypal.me/marceldossantos91 and type in the amount. Since it’s PayPal, it's easy and secure. Don’t have a PayPal account? No worries.
paypal.me
if you do decide to donate, thank you, appreciate it more than you know.
Sources:
CherishOS: https://github.com/CherishOS
Device trees: https://github.com/GPUCode, https://github.com/c79

Reserved

in case anyone is wondering, the rom is considered stable and mostly everything works, but please when reporting bugs, attach a log, thanks!

Thanks!!!

build updated
Happy flashing!

In your instructions
I'm guessing step one should be make sure device bootloader Unlocked
And t virus is installed

johndaog said:
In your instructions
I'm guessing step one should be make sure device bootloader Unlocked
And t virus is installed
Click to expand...
Click to collapse
Yes you are correct. Ive updated the post accordingly, however it is always to be assumed any rom besides stock needs T-virus to work as it requires the treble base.

Thanks for making this! Out of curiosity, is this rom using the latest A11 DDV by @emufan4568 you mentioned in another thread?

r100 said:
Thanks for making this! Out of curiosity, is this rom using the latest A11 DDV by @emufan4568 you mentioned in another thread?
Click to expand...
Click to collapse
Yes, its using all the ddv blobs and hal's, and everything has been upgraded. All A12 roms for NB1 going forward will use them

Just flashed this ROM. Buttery smooth. Thanks a lot for your time and efforts.
Couple of possible bugs
1) Do not change the display cut out from default- it blanks the whole screen without any way to change back other than by factory resetting.
2) I can't connect to Internet when I turn on expressvpn. Might be just me though.
This just proves that the Nokia 8 is still a very capable device in 2022.
Can't really get a logcat for the first one but will look into the second one to see if there's a workaround for the VPN issue.

And just in case anyone is wondering, banking apps work just fine. Safetynet passes and Selinux is indeed enforcing

Latest Gcam seems to be a hit and miss for some modes. I'll share if there's a better one out there more suited to the Nokia 8
**Edit: https://www.celsoazevedo.com/files/android/google-camera/f/changelog1434/
This one seems good and stable for me

Xda2022 said:
Just flashed this ROM. Buttery smooth. Thanks a lot for your time and efforts.
Couple of possible bugs
1) Do not change the display cut out from default- it blanks the whole screen without any way to change back other than by factory resetting.
2) I can't connect to Internet when I turn on expressvpn. Might be just me though.
This just proves that the Nokia 8 is still a very capable device in 2022.
Can't really get a logcat for the first one but will look into the second one to see if there's a workaround for the VPN issue.
Click to expand...
Click to collapse
Hi all, found a fix for the VPN not connecting. I found that I had to be on a TCP protocol for it to work. I had issues with a UDP connection. Didn't have this issue on Pie so assume it's to do with this ROM, but nonetheless here's the solution if you've got the same problem.

Xda2022 said:
Hi all, found a fix for the VPN not connecting. I found that I had to be on a TCP protocol for it to work. I had issues with a UDP connection. Didn't have this issue on Pie so assume it's to do with this ROM, but nonetheless here's the solution if you've got the same problem.
Click to expand...
Click to collapse
I just tested UDP now with windscribe and i connected without any issues. Likely the issue is your vpn providers app not fully compatible with A12 yet.

marceldossantos91 said:
I just tested UDP now with windscribe and i connected without any issues. Likely the issue is your vpn providers app not fully compatible with A12 yet.
Click to expand...
Click to collapse
Interesting... I guess it's a fix for anyone on Express VPN.

new cherish build up, QC is finally fixed with this update. happy flashing

marceldossantos91 said:
new cherish build up, QC is finally fixed with this update. happy flashing
Click to expand...
Click to collapse
Probably me being a bit stupid, but how do you update? I don't see an update menu- does this need a microsd card to flash over twrp for every update?

Xda2022 said:
Probably me being a bit stupid, but how do you update? I don't see an update menu- does this need a microsd card to flash over twrp for every update?
Click to expand...
Click to collapse
You have to dirty flash through twrp. I am looking into how i can integrate an OTA updater but for now dirty flash procedure

build is updated, the only change is that the H/W lights for keys should now work.
Happy flashing!

Nice one Marcel!

Develop Bugs

welcome