Search results

Wrong place for this buddy. This forum is NOT an official Xiaomi support forum. It's only for xiaomi.eu custom ROM, you will have to contact the official Xiaomi support to get help with that.

Might be a stupid question, but... Have you ever rebooted after installing the module? In case you have, and its still not working: Uninstall the module and AdAway app, reboot Then re-install the module and the app, reboot. Then try again if it works. Also: why do you have magiskhide installed...

I don't have magisk installed so I can't test the exact situation rn. Check if systemless hosts is really installed as a module (and enabled). If yes, uninstall the module, reboot, reinstall it from magisk settings and reboot again. Then retry AdAway.

If you enter the headphone's settings in bluetooth menu, there should be a toggle for LDAC codec. The option in dev settings is actually just a developer setting. It is not intended to be used with consumer headphones and therefore doesnt work.

The denylist specifies the processes/activities that should be "denied" from seeing the magisk/busybox binary files and processes which indicate root access. So, play services as well as all apps/processes/activities that may check for device security should have their toggle to the...

What do you mean by "disabled"? The toggles next to them should be enabled in order to keep them from detecting root. The difference between the apps that detect root and some that don't lies within their programming, starting over won't do anything about that. I also saw that there is a new...

If xiaomi.eu team rejects the bug report, it's likely a deeper seated problem with the base ROM, which they have very little influence on. The standard solution in this case with an old phone like that would be just buying a new phone. If you don't want that but want a new ROM, you could have a...

How did you configure denylist? It should at least contain com.google.android.gms.unstable, the whole Google play app pack as well as all activities associated to your banking apps. And don't forget to clear caches of services framework, play store and all banking apps and reboot after you put...

Have look at "Strict mode enabled" and "Show notification channel warnings" in dev options. If any of them are enabled, disable them. Otherwise we gotta hear what ROM devs say.

Sounds good Your phone will always be encrypted, u can't disable that and it's good that way. What's important is that in TWRP, after entering your screen lock, it shows "user 0 decrypted successfully" in log. The bank apps could be a bit bigger of a problem. I'm not too sure what the...

Ah, I forgot that was a thing lol. Usually when clean flashing, we use Fastboot for that in order to avoid exactly those kinds of problems you've been facing. Anyways, because you said HyperOS 2.0 is working now (probably cached or something, not sure myself), is gapps working aswell or are...

Once again I'm not sure if I'm understanding you correctly. What did you try to wipe in twrp and why? I thought you wanted to clean flash? For root, the easiest option is still the same as described before. Pull the magisk.apk file to PC, then enter sideload mode in TWRP, then use adb sideload...

Exactly. That's also what I'm using right now without issues.

That's why this thread has been inactive for 3 months.

Any updates on this? Did u already reflash?

In case youre referring to userspace encryption: That has been a thing for years now on pretty much any android phone. The problem was that the "skkk" beta twrp builds for 14 Series (and some other phones shipped with A14) were not able to decrypt it. This has been fixed with the new release by...

I still don't get what kind of encryption you are talking about. What exact problem are you facing at what exact point? I have never used (or even heard of) swiftbackup, I guess this is a huge knowledge gap for this discussion... (PS.: if you want to adb push/pull from/to any path outside of...

For the problem with magisk. You can start sideload mode in twrp, connect the phone to PC and run "adb sideload magisk.apk" or the magisk.zip (the ending doesn't matter, apks are literally just zip files with different name) Why do you need magisk tho, if you want to reflash anyways?

So, im not sure what you're trying to say with the rest of the message. But the reason why the adb push fails is because you put the paths in wrong order. It should be the origin path on you PC as first argument and the destination on phone as second.

Have you tried just running the upgrade script via Fastboot? Even if there is no actual upgrade, it should rewrite (fix) the vital partitions while leaving your data untouched. Remember to reflash TWRP (A15 variant by kyuofox), as it will be overwritten with stock recovery during update.