Recent content by ntlkr

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...

I do know the theory of how KMI works, and as I said I had also tried different patches but it didn't work correctly. Still thanks for your reply.

First of all, thank you. Did your device firmware come with KMI 6.6.66 or did you just use that version of Wild+? Cause my main problem is that my Mi 15 (dada) 214 ROM comes with KMI 6.6.30, which is not released in the Wild+ GitHub repo (lowest there is 6.6.50).

Is anyone using WildPlus kernel on Xiaomi 15 HyperOS 2.0.214.0? I can't find the correct KSU next build for 6.6.30 in Wildkernels GKI repo, so I tried multiple other patches from KMI 6.6.x, as they should theoretically work aswell, but the ones I tried all had problems like broken pwm control...

Hi, i have recently wrecked my 14 pro and got myself a Xiaomi 15 global as a replacement. I still have to wait 2.5 days until I can unlock it, but: Over the last years, I have seen multiple individual fixes for different devices (modem fixes, camera firmware issues etc). Now as my Mi 15 ist...

@porcelain4 Settings > Additional settings > Gesture shortcuts > Power off