[Xiaomi Mi A3 ROMs, Kernels, Recoveries, & Other De] Typhus_:
Hello!

Thanks for your work, truly appreciate it.

Could you update the OP with the install method that I'm going to describe next? It's just to avoid future complications (lost of Wi-Fi, sound, etc...) for Noob users.

Download the OrangeFox zip file and copy it to your device (internal or external storage)

Extract the recovery.img from the zip and store it, on the folder where you have adb and fastboot files, on your PC

Open a cmd line and execute these commands (being on that folder, of course):

adb devices (to make sure your device is detected)

adb reboot bootloader (to reboot into fastboot mode)

fastboot getvar current-slot (to check what's your current active slot)

fastboot set_active b (if your active slot was a, if it was b then change it to a)

fastboot erase boot

fastboot flash boot recovery.img

fastboot reboot (

NOTE

: Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)​

When OrangeFox recovery boots, if you have the stock boot.img that matches the build on this "currently active" slot, flash it into boot partition. If you don't have, then just ignore this step...(it's not mandatory)

Install the OrangeFox zip (always install the latest build available)

Change slot to the one that was active on the beginning of these steps and reboot to Recovery (just to make sure that the slot, in fact, was changed)

Reboot to System

Enjoy :)

Why do I suggest this? Well, please read the hidden content:

By doing this method (which seems more complicated but I've tried my best to explain it as if I were explaining it to a 4 years old kid...) we will flash the recovery.img into the "inactive" slot, thus, not breaking anything on the "currently active" slot. When OrangeFox boots, it will patch both slots boot ramdisks. But the thing is, on the "currently active" slot (the one inactive on the beginning) it will patch the recovery.img but, on the "currently inactive" slot (the one that was active on the beginning), it will patch the stock boot.img, thus, no bug will happen that usually appears when a user accidentally flashes the wrong boot.img into boot partition. On the other hand, if we have the stock boot.img, that matches the build on the "inactive" slot, we could flash it into boot partition before installing the zip that patches ramdisk. By doing this we will patch both stock boot.img present on both slots (instead of patching recovery.img and boot.img).

Cheers!

---------- Post added at 12:04 ---------- Previous post was at 11:16 ----------

Hello....again...

I've just tested the install method that I've explained but, unfortunately, it's not working.

OrangeFox recovery only boots if the installer zip is run through TWRP...don't really know why since I've tested a lot of times doing this exact same method with TWRP recovery, and it's working. It should be working here as well.

Anyway the OF recovery boots but I think that it does not decrypt data. It doesn't gets frozen on the welcome screen (like before) but it doesn't decrypt (I see all the files with the "weird" names). This, of course, is only bad for those who want to remain on stock ROM. For anyone who wants to move on to custom ROMs, just format user data and your set to go.

Cheers!