Search results

Yes, using the search function on this forum. This has been reported dozens of times and affects nothing unless you're flashing more zips after installing the rom. Before that you'll see in the log that it installed fine.

No.

Boot image then. Same as doing it manually. https://topjohnwu.github.io/Magisk/install.html

Use Magisk to patch boot...

No -- hopefully Xiaomi fixed it in the next weekly, but all we can do is wait to find out.

You can find a newer build here: https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/apollo/ And flashing instructions here. Make sure you follow the instructions for apollo: https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/apollo/ Then you should have no...

Not specific enough. For example SKKK builds include the functionality to patch the bootloader with Magisk without even flashing the .zip file.

Try a different USB port if you're dead set on doing it the fastboot way. Otherwise install the SKKK v7.2 A13 build by referencing the how to in the Q&A section (if you don't already have a compatible TWRP recovery installed) and flash it that way.

1 and 3 are both working on Poco F3 on the dev builds. 2 is Xiaomi dependant. Some roms get them, some don't. It's an inconsistency on their part and something the .EU devs don't really have control over. The can't install Magisk is somewhat surprising. What recovery are you using?

That used to be the fix for Samsung Pay on my Galaxy Watch too when I was on MIUI 13 last year (Poco F3). I haven't tried any NFC payments in a while on MIUI14 but I suspect the same will apply there.

It should be fine since that's an update. If you were coming from the MIUI14 weeklies, then no.

When I had my Redmi Note 5 Pro I found it was picky about the cables used. Try a different cable, try a different usb port. Check device manager and force uninstall any other drivers that may have been installed. Windows seems to like installing weird ADB drivers through Windows Update...

Since payment apps turn it on for you and don't turn it back off, you have to go into the notification center to turn it back off anyway, I fail to see your point. Also directly attacking one of the lead developers like that will get you nothing except your account being banned lol.

Are you booting into fastboot before you connect the device? NOT RECOVERY.

Just put it in your notification center and you can see if its on or off... Edit: I see you have it in there already. Is showing it in one easy to check place not enough? lol

Yep give the A12 one a try. That should decrypt your data partition correctly. If not, reboot to android and set a pin, then remove it and try again.

Which version of the TWRP recovery are you using? It sounds like you're not using the correct one for MIUI13 (Android 12). You likely download the one with A13 in the file name.

Mine just asks to use that now when it detects location accuracy is low -- instead of how it used to ask you to do figure 8s with the phone to calibrate the mems sensor. Likely depends on Play Services and Google Maps app versions. In Maps it just pops up at the bottom and asks you to click...

Just flash the newest directly.

The augmented reality calibration? I haven't had any luck with that on my F3, possibly because I live in the suburbs and Google's street view data isn't that great in the area. (Also we're covered in snow right now and all the street view data is from summertime. Haha.)