yashsingh1/xdaforums huggingface dataset:
[Magisk] plittlefield:
OK, I have managed to get the phone up-and-running by ...

1. Hold buttons (Power + VOL DOWN) to get in to the bootloader.

2. USB cable > fastboot devices

3. USB cable > fastboot boot twrp-3.2.3-1-sailfish.img

4. TWRP > Reboot > Slot A

...and the phone seems fine.

I can reboot it as normal.

However, I cannot reboot to Recovery... seem to have lost TWRP, which I can reinstall again.

However, I am going to wait until I get a reply first.

:)

Paully
[Magisk] TENN3R:
I know that Magisk has OTA support.

As a sailfish owner too, I remember when Pixels were not supported by Magisk OTA system, I just get used to flash it manually in a 5 minutes procedure.

All I always do is flash the new factory image (removing the "-w" at the bottom line of the flash-all script, so it will upgrade without wiping) and then simply fastboot boot twrp and reflash magisk.

Never had a single problem doing this. I don't know what guide you followed, but the procedure you did looks like correct.

If you prefer this automatic way, try follow the official guide that topjohnwu made.

Hope it helps
[Magisk] Didgeridoohan:
As far as I know (I don't own a device where this is applicable), it's still recommended to

not

install TWRP at the same time as Magisk on A/B devices. Since they both alter the boot image, you might end up with issues like bootloops. Only boot TWRP...

It's not certain that this was the source of your issue, but it's one possibility. Other possibilities might include modules that are incompatible with the update, etc.

Other than that, the official docs linked above should work fine.
[Magisk] plittlefield:
Thank for the tip about editing the ./flash-all script to remove the -w ... neat.

More research is required, as am new to Magisk, but the second poster to reply to this has mentioned that TWRP and Magisk do not sit well together, and it never occurred to me that I don't really need TWRP actually installed, if I can always get to a laptop and USB cable!

:)

Thanks for your reply... I dunno, the things we do to keep stuff "easier".

Paully
[Magisk] plittlefield:
Thanks for your reply.

Now I think about it, as long as I can get to my laptop and a USB cable, I don't need to _install_ TWRP if I need to do stuff.

So, the Pixel with 9.0 is currently in this state...

* SLOT A with Security Patch level: 5 December 2018

* Magisk patched boot image not installed

* TWRP not installed?

* Magisk Manager app installed

I think SLOT B is broken?

How do I do this properly? Are there STEP BY STEP instructions somewhere?

Do I uninstall TWRP, or is it already hosed when Magisk 'restored images' and then 'patched'???!

Yours, a bit worried...

Paully
[Magisk] TENN3R:
That's right, since december (I think?) looks like Magisk and TWRP have some incompatibilities, before I always flashed them together with no problems at all.

A useful "trick" about flashing without a pc would be using Franco Kernel manager, as he added support for a flasher even without having twrp installed. Just select the zip and tap on flash. That's kinda magical.

Of course for this you need to buy his app, but as of today it's a pretty universal kernel manager, not only restricted for his kernel. I find it very useful.
[Magisk] plittlefield:
OK, so what do I do now to remove Magisk, TWRP and then start again?
[Magisk] plittlefield:
Seriously, a web page on this very problem!

:)

https://magiskroot.net/uninstall-magisk-module-twrp/
[Magisk] Didgeridoohan:
That particular link is for removing modules through TWRP, so not anything to do with your problem (or have I misunderstood you completely)...

But, I mainly wanted to give a warning: be very wary of any site that has to do with Magisk and isn't directly mentioned by [MENTION=4470081]topjohnwu[/MENTION] in the release thread. There are some really scammy sites and take apps out there trying to benefit from Magisk's popularity.
[Magisk] plittlefield:
Thanks. I'll not use that site then.

I could do with some help on how to remove both TWRP and Magisk then start again but not installing TWRP.

Cheers anyone!
[Magisk] Didgeridoohan:
From my understanding (again, remember I have no experience with A/B devices), all you need to do is to flash the stock boot image. Possibly to both slots, but someone that has experience with A/B devices would be a better source of information, or better yet: check your devices forum for info.

Once you have the stock image installed all you need to do is to boot TWRP and flash the Magisk zip.
[Magisk] plittlefield:
Understood, that sounds reasonable.

Cheers everyone.
[Magisk] TENN3R:
Yep, going back to stock boot image on Pixel are just 2 commands. Extract the boot.img from the stock factory image, then in fastboot:

- fastboot flash boot_a boot.img

- fastboot flash boot_b boot.img

Then reboot
[Magisk] plittlefield:
OK, so I am currently running PQ1A.181205.002.A1, Dec 2018 in Slot A (it won't boot from Slot B)

Do I download the OTA image or the FULL image? I guess they contain the same bootloader image...?

bootloader-sailfish-8996-012001-1811131534.img

Thanks in advance.

:)

Paully
[Magisk] TENN3R:
Images are only in the full factory image, not ota.

If you wanna stay on december update, download the december factory image otherwise grab the latest february, edit the script to keep data and flash so it will upgrade everything with no wipes.

If you wanna flash only the december boot image, you can find it in the zip, which is inside another zip in the factory image.

Pay attention, the boot is exactly called "boot.img", I tell you because inside that zip there is another file called "boot-a" or something similar, this is NOT the one you wanna flash
[Magisk] plittlefield:
OK, so that worked.

I flashed the February factory image without wipe...

Sending 'bootloader_a' (32424 KB) OKAY [ 1.401s]
Writing 'bootloader_a' (bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 13.421s]
Finished. Total time: 14.934s
rebooting into bootloader OKAY [ 0.042s]
Finished. Total time: 0.193s
Sending 'radio_a' (57140 KB) OKAY [ 2.403s]
Writing 'radio_a' OKAY [ 1.102s]
Finished. Total time: 3.625s
rebooting into bootloader OKAY [ 0.042s]
Finished. Total time: 0.343s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: 8996-012001-1811131534
Baseband Version.....: 8996-130181-1811270246
Serial Number........: FA69M0304045
--------------------------------------------
Checking product OKAY [ 0.050s]
Checking version-bootloader OKAY [ 0.050s]
Checking version-baseband OKAY [ 0.050s]
extracting boot.img (29 MB) to disk... took 0.178s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
archive does not contain 'product-services.img'
archive does not contain 'recovery.img'
archive does not contain 'super.img'
extracting system.img (1944 MB) to disk... took 14.619s
archive does not contain 'system.sig'
extracting system_other.img (312 MB) to disk... took 3.222s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (259 MB) to disk... took 1.987s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
Sending 'boot_a' (29761 KB) OKAY [ 1.301s]
Writing 'boot_a' OKAY [ 0.655s]
Sending sparse 'system_a' 1/4 (524284 KB) OKAY [ 23.023s]
Writing sparse 'system_a' 1/4 OKAY [ 4.642s]
Sending sparse 'system_a' 2/4 (524284 KB) OKAY [ 22.421s]
Writing sparse 'system_a' 2/4 OKAY [ 4.345s]
Sending sparse 'system_a' 3/4 (524284 KB) OKAY [ 22.368s]
Writing sparse 'system_a' 3/4 OKAY [ 4.341s]
Sending sparse 'system_a' 4/4 (418060 KB) OKAY [ 17.867s]
Writing sparse 'system_a' 4/4 OKAY [ 3.545s]
Sending 'system_b' (319668 KB) OKAY [ 13.160s]
Writing 'system_b' OKAY [ 3.048s]
Sending 'vendor_a' (265748 KB) OKAY [ 10.768s]
Writing 'vendor_a' OKAY [ 2.838s]
Setting current slot to 'a' OKAY [ 0.404s]
Rebooting
Finished. Total time: 156.038s

Should I be able boot from Slot B because it doesn't do anything if I try?

Paully
[Magisk] plittlefield:
Do I need to worry about using Slot B?
[Magisk] TENN3R:
I never changed slots after a flash, neither selected to which slot flash zips, I think it's all manager by the installer scripts, same for magisk, twrp, kernel, ...

Once you flash and reboot you're ok
[Magisk] plittlefield:
OK, thanks :)
[Magisk] plittlefield:
OK, so all's well that ends well.

After flashing the full February stock image without wipe, it booted fine.

I then adb fastboot booted the TWRP image, flashed the Magisk.zip file, booted in to the system and installed the magisk app which runs fine and now Titanium backup work too.

I have disabled the Android 'automatic system updates' in Developer Mode' of Settings and will now follow the following procedure whenever there is a Android update:-

1) download latest stock full image

2) edit flash-all.sh to remove -w option

3) flash image

4) reboot

5) download latest magisk.zip and magisk.apk to phone

6) adb reboot-bootloader

7) fastboot boot twrp.img

8) install magisk.zip to patch boot image

9) reboot

10) install Magisk app and test

Happy days.

Thanks to everyone for your suggestions.

Regards,

Paully
[Android Q&A, Help & Troubleshooting] Funny_man88:
Hi Guys, could you please help me?

I download and install new android on my ulefone power 3s yesterday, everything passed ok, without errors, but now red logo on right corner appears which is visible almoust everywhere (probably developer sign) how can I remove it? do you have any ideas?

I`ll be very thankfull for every advice
[Android Q&A, Help & Troubleshooting] swamptastic:
Sadly this is a consequence of not backing up certain partitions prior to flashing the phone. I have got the same issue on an Oukitel K10. Best explanation I have found so far is here: https://xdaforums.com/android/help/allcall-s1-x-official-firmware-v1-t3870503

Mine came about after following the official upgrade process from the manufacturer!
[Android Q&A, Help & Troubleshooting] krobin:
Assume that your device is rooted with rw access to both vendor n system dir....

Try look into this line entry in build.prop in /vendor dir.

ro.mtk_trustkernel_tee_support=1

change the value to 0 fixed the watermark appearance on my oukitel u223 oreo stock rom.
[P3300, MDA Compact III General] maccied:
Hi

i've got the o2 xda orbit.

how would i bulk copy my sms's onto my pc via usb? or any other method that might work?

thanks in advance for your help
[P3300, MDA Compact III General] maccied:
Surely this question must have been asked before...

is it possible?

even a link would be great.

thanks
[Samsung Galaxy S10+ Guides, News, & Discussion] AllAboutTech:
[EU]Exynos 9820 - Samsung Galaxy S10+ News /Rumours and Other Stuff
[Xiaomi Mi A2 Lite Questions & Answers] ondraczsk:
I want have Pie base and Pie RR, but fingerprint isnt working and i dont want to flash OREO base, because RR with OREO is buggy. I tried flashing vendor.. etc. not work. :/ Is there some way to do this?
[Xiaomi Mi A2 Lite Questions & Answers] Voodoojonny:
RR7 works quite snappy with the combination of:

- Base = 10.0.3.0

- Vendor = 9.6.9.0

- Modem = 9.6.9.0 (flash modem-fix by [MENTION=8281637]eremitein[/MENTION] to fix modem settings)

- Aboot (if you want to use twrp) = 9.6.11.0

That´s how I had my configuration - everything worked fine, except of BT-calling, that´s why I went back to stock.

Bt-calling not working in any combination - I tried with with 9.6.4.0, 9.6.9.0, 9.6.11.0 and 10.0.3.0 and the combination shown above.

The problem also persists with Havoc 2.2., Arrow, Decendent, PE and Omni - all the other gsi have to test someone else... Wasted enough of time :eek:

Ah, and I replaced drivers and files of bt and ril - no success!
[Xiaomi Mi A2 Lite Questions & Answers] eremitein:
are you remember is bt-call work in Havoc 2.0?
[Xiaomi Mi A2 Lite Questions & Answers] cd492:
Which did App did u use for bt calling or did u just connect your daisy to your headphone via Bluetooth and then made a call? I've never tried Bluetooth calling so I would test it on the Viper Rom.
[Xiaomi Mi A2 Lite Questions & Answers] Voodoojonny:
I used havoc 2.0 for a while and I didn't experienced that bug... I switched back from havoc 2.0,becouse it became laggy and gcam freezed anytime I needed it... But I'm not 100% sure that bt call works there...

---------- Post added at 05:43 PM ---------- Previous post was at 05:39 PM ----------

Only stock dialer... That would be great! Have you already installed viper? If no, could you try, if dialer freezes without gapps installed? Becouse that was the reason I trow away viper:rolleyes: Yes I spent too much time on that ****...
[Xiaomi Mi A2 Lite Questions & Answers] cd492:
I already installed gapps. I'm using the Viper Rom for two weeks now [MENTION=7357714]10.[/MENTION]0.3.0 and I'm very satisfied, for the first time. Everything works only a Error Message shows up every Restart and yes BT Calling doesn't work. It switches to Smartphone Speaker when I start a BT Call.
[Samsung Galaxy S8 Questions and Answers] Blue31222:
Hi, so long story short my S8 got destroyed when it was left on top of our car and fell off and got run over. Since the frame and glass were both completely destroy I was wondering if It still worked, and it turns out it does the notification light still blinks and the CPU still gets warm so the board is OK. I was wondering could I transfer the components from the old S8 to a S8+ shell, or would it not fit? I have G950U if that helps.
[Samsung Galaxy S8 Questions and Answers] Outbreak444:
More than likely it will not work in the S8+ chassis. Screw holes will likely not line up. Not to mention the screen size, specific software and hardware differences on the board itself.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] REIGNZ3:
#include <std_disclaimer.h>
/*
* 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 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.
*/

SHRP is inspired by Material design 2 to bring the newest design to the native TWRP. SHRP provides much more along side of it's rich UI experience. New dashboard makes it very easy to interact with TWRP. SHRP got some cool features like Whole new theming section ,Flash Magisk (root or unroot), Camera2api enabler Directly from dashboard, Password protection etc. It's all started , lot more to come.

- Themes

- List view mode along with grid dashboard

- Status bar customization

- New rounded icons added on dashboard

- Notch mode with toggle to disable

- Dark mode or pure white, it's on you

- Navigation bar customization

- Settings + Advanced Settings

- Flash Magisk

- Clear fingerprints.

- Flash ViperFX

- Recovery Locking , Pin or Pattern lock

- CPU core lock/unlock

- Language changing

- Hal3 / CameraAPI2 enabling/disabling

- Oreo+ Reboot menu style

- Redesigned lock screen interface

- Flashlight

- Magisk manager - Enable, disable or delete magisk modules right from SHRP

- and many more, flash right now to find out

1. Make sure you have a custom recovery installed

2. Download the latest SHRP recovery for your device

3. Boot into recovery

4. Flash shrp recovery zip

5. Reboot to recovery.

6. Done

You tell... :P

DOWNLOAD NOW

Github

Website

ScreenShots

Telegram Group

EpicX

DNI9

Giovix92

TeamWin

osmOsis

VR25

Topjohnwu

Mauronofrio

DarthJabba9

Special Thanks

Pritish

Kirill

Burak D.

ZJRDroid

LayeardDevMod

Please inform if we forgot to mention your name here , thanks !

​

Maintainer: blitzfire3

Based On: TWRP

TWRP Version: v3.3.1-0
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] REIGNZ3:
Bugs

- Encryption & Decryption

- Report if you find any
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] REIGNZ3:
Changelogs

=======================

03-03-2020

=======================

- Bump to SHRP 2.2

- Build with latest LineageOS Tree

- Fix Freeze Issue

- Fix Battery % Bug

- Update To Latest Q Blobs

- Report bug and issue if u find any

- Fixed /system & /system_root remount

- Added more accents + icons/set-ups to theming room

- Changed initialization's behaviour for themes

- Fixed translations

- Added Dev mode

- Redesigned "About" section

- Added Zip/Unzip functions

- Improved file manager look + behavior

- Added a clear button in text boxes

- Fixed random reboots while selecting files

- Added flag to skip compatibility.zip check (#2)

- Upstreamed to Magiskboot 20.3 + Magisk 20.0 (#3)

- Added Magisk survival (#3 for Magisk ZIP)

- Upstreamed from TWRP (#4)

- Fixed Splashscreen view for non 16:9 devices (#5)

- Upstreamed Magisk Manager (#6)
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Aadeep:
Aroma installer packages working with this recovery?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Mcha01:
Great interface, is there an option to remove the pssword??
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Rahul kumat:
Does data decryption works?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] BenParz:
What is the main objective of this recovery? What makes it much more compelling to use than TWRP? And also, can you provide pictures of the recovery as well?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] rnrgy:
theme first change successs

second change not changed

and recovery boot password 100% required
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] ahmd gom3aa:
+1

what features other than visual changes ?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Woivod:
I apologize for my English, when installing the Russian language, the font is displayed in squares. Please change the font in the "font" folder.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Gaurav143S:
Great. New refreshed UI recovery for POCO F1. Lets try it.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] MadMelman:
Somehow its unable to decypt data.

I even tried disabling the lock.

Any workarounds?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] nirurules:
Same thing for me , I m also getting the same error

" recovery is password protected "

---------- Post added at 11:00 PM ---------- Previous post was at 10:57 PM ----------

I Had Tried With All The default passwords

Password

Default_password

Passcode

But it's not unlocking .. pls provide us the default password for shrp recovery.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] phonetech101:
In op step 6 says type "shrp" if it asks for password.

Tried it works fine.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] noitsbeckky:
Custom rom works fine, it only cant decrypt miui it seems, tried it and decrypt with twrp but after reflashing shrp it didnt detect the decrpytion and asks for password
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] shahzaan_don:
aroma work with all custom recovery
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Nikhil:
No it doesn't work with all custom recovery.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] KniggeMS:
Decyption doesent work with it. So sad.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] valen1321:
shrp is the password [emoji6]
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] nirurules:
Thank you so much I was blind enough to see the op , it's working thanks again.

---------- Post added at 01:32 PM ---------- Previous post was at 01:32 PM ----------

Thanks a lot buddy
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Sheikh Nadeem:
Can anyone confirm if aroma installer works?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] dalyer:
Why don't you just try it?!? :confused:
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] valen1321:
It should work... Just try with a simple zip
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Sheikh Nadeem:
I tried gapps aroma... Not working.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] solkarsalman:
Am using it on MiRoom 9.2.21 and it does not show my internal data, it is not even decrypting with the given password shrp. What to do.?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] dalyer:
Read the thread - already discussed!
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] REIGNZ3:
All the bug will be fix in the next release stay tuned!!
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] thiefxhunter:
Im in love with this recovery <3 Awesome Job ! , Thanks a lot

[MENTION=6549853]blitzfire3[/MENTION] Do you have plans to add multirom support ? it will be superb !
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] ps_minky16:
Aroma also?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] REIGNZ3:
Cannot say
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] ps_minky16:
I'll be happy to test for aroma.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] jackiass:
Can't decrypt data
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] testrm:
Decryption doesn't work, it doesn't take my device passwords. Will that be fixed too?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Gourav007:
+1
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] KennyG123:
Thread reopened at OP's request....something new????
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] REIGNZ3:
New Update will come soon :p :fingers-crossed:
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] :
when?!
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] 2WildFirE:
Soon! As op told.

And pls dont ask for eta!

Thanks
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] BentMetal:
SD Card support?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] REIGNZ3:
SHRP 2.0 IS UP

CHANGELOG :- CLICK HERE TO OPEN

DOWNLOAD :- PLEASE CLICK ME XD

=======================

Device Specific Changelog

=======================

- Fixed Encryption and Decryption Issue

- Fixed the issue that was present in V1.2
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] :
:highfive:
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Sheikh Nadeem:
Aroma still not working
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] REIGNZ3:
Poco Doesnt Support Aroma in twrp ;-;
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Pher-:
Please allow vendor wiping in next build is possible, I am using this recovery and it is elegantly looking. Thanks for bringing the new build!
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Indha Lezzio:
Finally an alternative to standard twrp with no freezes and decryption working

Thanks so much

Enviado desde mi POCO F1 mediante Tapatalk
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Diagrax:
Great that decryption is working!

But can you fix the flashlight?

I got an error at the Main Console:

"echo 200 > /sys/class/leds/led:torch_0/brightness echo 200 > /sys/class/leds/led:torch_1/brightness process ended with ERROR: 1"
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Glassgg:
amazingg recovery looks so good and smooth very nice work sir
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] troyinjapan:
Can you explain what "decryption working" means? I usually flash DisableForceEncryption.zip that removes encryption and gives me magisk root. Do you mean that I don't have to flash DisableForceEncryption.zip and just flash the current Magisk-v19.3.zip ?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] adhammagdy:
Wow new update.. will flash immediately..

Also if I extract the img file from the zip I can flash it with fastboot?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] dalyer:
Dfe was always optional but too many people flash it blindly because they think or are told that it's needed.

It's NOT.

I never use it, run encrypted and have never had any problems.

But I do stick with official twrp 3.3.0-0 also.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] :
no need to flash dfe on this recovery.only flash magisk if u want to root.