[Xiaomi Poco F2 Pro (Redmi K30 Pro) ROMs, Kernels, ] fr_jason:
A few things to note here, the ROM developer is not the same as the Recovery developer.

Meaning Recovery development takes place independent of ROM in this case.

Since the beginning of the transition from A12 to A13 ROMs on this device, the community has been wrought with comments such as these that do not factor in the fact that, not only is Recovery development takes place independently from ROM development but this has to do with Xiaomi more than the development community.

An A13 MIUI does not exist for lmi, therefore, the development community would have very little to nothing to go on to create an functional A13 recovery.

This has been so since A13 ROMs first came to lmi.

Only these last couple weeks things have begun to change.

The same Recovery developer, skkk, has apparently released a working A13 recovery, check comment by XDA member @aj197 further up the thread.

That should be more than enough information on that matter, seeing as google.com, xda's search feature, and Telegram search in the CrDroid | Poco F2 Pro group all appear to be nonfunctional on the devices you have access to.

I have that impression simply because if after all this time there is someone still complaining about an A12 recovery, with A12 literally in the filename not being able to decrypt an A13 ROM, it means they have not read properly nor sufficiently.

And this is dangerous, for several reasons, aside from possibly bricking your own device at some point, ignorantly mouthing off as evidenced in the quoted comment runs the risk of tarnishing the reputation of an android developer; and this developer in particular pushes out these ROMs with a comparatively (to other ROMs) incredible degree of stability and fluidity/performance. They also, listen to the feedback of their users, helps them troubleshoot bugs, pushes out hotfixes and patches as necessary until all can be included in the next update.

All of that for free, with THE OPTION available to donate to him.

So what you need to do is calm down, this is not a customer is always right type of situation because you didn't buy anything, even if you donated, it would be a donation and not any type of contractual obligation, in either direction.

When you calm down and muster sufficient self respect to keep a cool head when engaging the developer (or anyone else), you'll find that your approach is likely to have a more fruitful outcome.

For example, you have an issue, with 3-button navigation. So ask if there is a way to modify just that for the sake of your personal aesthetic preferences, like if there is a build.prop modification you can make or a suggested magisk module to effect the change.

And there you have a key to engagement for a more beneficial outcome.

The other issues that you have with the launcher I am unable to reproduce. My long press to close shortcuts on the 3-button navigation work fine.

My stock dialer and Google dialer have no ****ing missing buttons issue either.

Did you clean flash properly though?

I am not saying you're wrong to voice your concerns, I am saying your approach is wrong.

You're right about one thing though, a waste of time. Logging in to XDA, typing away your tears, all that copy/pasting and backspacing was time that could have been spent searching or asking in a more amiable manner.

Hell, you might have an aneurysm by the time you get to this part of my post.

TL;DR:

Pearls before swine.

Use skkk's recent TWRP recovery for lmi on A13