Recent content by ntlkr

If you mean "downgrade" as in "dirty flashing", then no, you shouldn't do that. If you mean "downgrade" as in "reflashing", then yes, thats absolutely no problem. No extra steps required, just be sure to use fastboot and run the "_install_and_format_data" script for your OS.

@Alex274 To unlock the bootloader of a CN device, you need an account that is Lvl 5 on Chinese community (the kind of account that was posted on this thread will not work bcs it's global), and need to take a test in Chinese language about various stuff regarding low-level android development...

Hi, the first question is about comparison which I dont have, so I cant answer that. Also it's a design choice by Xiaomi so no one will be able to do anything about it. Regarding the keyboard padding, I can confirm that on xiaomi.eu, there is absolutely no padding there as long as fullscreen...

Sure. But first, I want you to know that it doesn't make any difference if you've got KSU or Magisk in terms of play integrity. The important questions are if there's a valid keybox floating around and if your device is compatible with the PIF config that has been selected. The only difference...

Read FAQ. There are no detailed changelogs from xiaomi.eu for stable ROMs. You can go to www.miuiver.com and look at Xiaomi's changelogs for the base ROM versions.

Yes. But as gogocar62 already pointed out, you must not lock the bootloader in that state. So be careful to NOT run the flash_all_lock.bat, as it will cause a hardbrick and make your device permanently unusable. Instead use the flash_all.bat. If you're using MiFlash, make sure to select the...

Of course. Recovery is just a boot partition that is not related to the installed ROM. Just get the recovery.img from the "images" folder in the ROM package you have installed, then flash it the same way you flashed twrp. Though, if you're going to install global stock ROM, this is obviously...

I don't think so. This is something the dev of your twrp image has to fix. Why don't you just leave the stock recovery? If the new user is advanced enough to need twrp, they'll probably be able to flash it by themself.

Try selecting "Advanced wipe" and choosing metadata, data, cache and dalvik cache. If that doesn't work, you'll have to use the format_data_only script in order to reset.

You've got LSPosed already, you can install pengeek and disable the settings restrictions for system apps, then just disable the notification.

Don't do that. Security app handles a huge part of the UI and basic device features, it should never be disabled.

Sounds like the UI of some social media platform burned into your screen. This also has nothing to do with the ROM upgrade, it just happens over time. This is probably permanent, nothing to fix.

Using twrp sideload feature usually works without problems. If you want to make sure it goes smoothly though, just use the fastboot script.

Maybe I actually am doing something wrong, no clue... I usually just take the anykernel3.zip and flash it as a sideload package in twrp. This has worked on multiple kernel versions on multiple devices - until now.

Update: issue fixed. I talked to the Wildkernels devs and apparently they had problems building SUSFS with kernels earlier than 6.6.50 and that's why there was no release. Anyways, they found a fix for it literally just now and there is a new release including 6.6.46 and 6.6.30. Big thanks for...