Recent content by Vyto-Khron

The latest official TWRP works now (thanks to our new maintainer). He also maintains PitchBlack recovery which is a good alternative to OrangeFox.

Hey there, reviving this thread to ask if anyone had issues with Magisk v22 installation/update?

How did you fix it?

Is clean flash mandatory? Can I dirty flash from february 12.5 to april 12.6?

When I press the "check for updates" button in Updater app, I get a toast message saying I am up-to-date although I am still on 21.2.4. Why?

Anyone tried the updated TWRP by brigudav?

Formatted data. Works now. Thanks. Thought it would not be necessary though.

The default file manager gives the following error message: "Cannot access items. Try using Android Storage Access Framework instead." Is this new to Android 11 or am I missing something? Running MIUI 12.5 (21.2.4)

I flashed the latest @geoanto555 twrp and then tried PitchBlackRecovery before returning to twrp via fastboot. When I tried to reboot to system, it returns me to recovery. I get the following error in twrp: enablefilecrypto_failed Running MIUI 12.3 weekly on ginkgo

System stuck in recovery mode after flashing your twrp but decryption works. Any fix?

Oh... my apologies. You are right. From @BanditGR 's post, I believed the recovery would only work on that particular build only. Guess I will have to stick to this unofficial version of TWRP then. Thanks for the quick replies.

Uhh... Not sure what "weeklies" you are referring to here because MIUI 12.5 (21.1.13) is the first update after the MIUI 12.3 (20.12.9) one - the one that originally caused decryption problems. Beta was suspended officially by Xiaomi during that one month gap but correct me if I'm wrong.

Has anyone tried the latest MIUI 12.5 update to see if the decryption issue has (hopefully) been resolved?

Find the original post here. We have a few questions that we would like the mods to answer: Is it affecting all RN8 devices or have we somehow messed up the installation? Is this an issue on your side or Xiaomi's side? Could it be intentional or you believe it will be fixed in future updates...