Zygote (10255) asking for root access!! - Android Q&A, Help & Troubleshooting

I've recently flashed a custom rom (DN7 Port) from E-Team on my Galaxy Note4 (SM-910C). Since there's a long time trying on xposed modules and so, I'm now trying on some modules and unchecking modules with no specific relevance and identified most of the draining my battery to a great extent.
Only in recent times I've been asked by the 'zygote' to root access, I've accidentally granted once and immediately denied thereby from the SuperSU. Sudden prompt of gaining root access by the Zygote (10255) has lead me to suspicion.

do you by any chance have whatsapp extensions module in your xposed? I noticed you have given root to whatsapp which should not be needed as far as i know.. Also, since last update of that module a day or two ago, i started getting promped for whatsapp and zygote root access which is quite strange imho

Or maybe it's relative to Lucky Patcher ?

equiliym said:
do you by any chance have whatsapp extensions module in your xposed? I noticed you have given root to whatsapp which should not be needed as far as i know.. Also, since last update of that module a day or two ago, i started getting promped for whatsapp and zygote root access which is quite strange imho
Click to expand...
Click to collapse
Exactly! The author of that extension has already addressed the issue. It shall be granted for the moment and the both the root access will be removed in the coming update.
Thought zygote service root access could be a security void for a while !

CODENEX said:
Exactly! The author of that extension has already addressed the issue. It shall be granted for the moment and the both the root access will be removed in the coming update.
Thought zygote service root access could be a security void for a while !
Click to expand...
Click to collapse
Likewise, never hears od zygote asking for permissions before, thought i got some malware or something.. The author told me it asks for root because of custom notifications or whatsoever so i just downgraded to version 4.1 of that module, didnt like the popups/notifications of supersu for zygote/whatsapp every 15 mins

i have no Watsap or Lucky patcher, or xposed, on my phone.
Today market report 3 updates. Aliexpress official app, Facebook and Messenger.
During update in background some thing asked "zigote" root permissions, I denied.
What is it?

Related

[Q] Micromax A57 unrooting itself without notice - why ?

Good morning world,
I rooted my A57 phone few weeks back by following the procedure that is described everywhere on the internet. Since that moment, the phone is pretty stable.
But something interesting happened twice to my phone. Without any particular reason, my phone goes back to a non-rooted state. I notice it because I stop being able to load any application that requires root permissions, like Titanium Backup for example.
TB tries to boot, Superuser grants it the root user permissions but then TB stays stuck on "Asking for root...". Almost same thing happens to ES File Explorer, which cannot mount /system/ as root anymore. Basically, I cannot do anything that requires root access anymore.
I tried many things but the only solution that currently works is to root it again.
Does anyone know why my phone is acting this way ? Is my phone updating and unrooting itself without me knowing ? Can I block this ? Is this a bug of Superuser ? Any idea ?
Thank you very much for your kind help.
razeryokes said:
Good morning world,
I rooted my A57 phone few weeks back by following the procedure that is described everywhere on the internet. Since that moment, the phone is pretty stable.
But something interesting happened twice to my phone. Without any particular reason, my phone goes back to a non-rooted state. I notice it because I stop being able to load any application that requires root permissions, like Titanium Backup for example.
TB tries to boot, Superuser grants it the root user permissions but then TB stays stuck on "Asking for root...". Almost same thing happens to ES File Explorer, which cannot mount /system/ as root anymore. Basically, I cannot do anything that requires root access anymore.
I tried many things but the only solution that currently works is to root it again.
Does anyone know why my phone is acting this way ? Is my phone updating and unrooting itself without me knowing ? Can I block this ? Is this a bug of Superuser ? Any idea ?
Thank you very much for your kind help.
Click to expand...
Click to collapse
last night i gt this Phone and today Morning Rooted it with UnlockRoot and its working fine
may b there is bug in ur superuser (MAY BE) Root again and try to update
Are you facing Slow internet and Low Sound during Call ??? well many user on internet saying these problem
but everything is okay in my case (heated in heavy use same As my Nokia 5230)still m getting Positive Response from my phone

SuperSU/SuperUser slowness... Make it faster?

Hello,
Is there a way to make SuperSU/SuperUser less slow? I mean, on a virgin rom it's already not so fast, but after you install your apps, it can takes minutes before the pop-up asking for root rights comes, if it comes..!! So is there a way to "fix" that? It's a pain, having to reboot sometimes cause of that!
Thanks.
goja said:
Hello,
Is there a way to make SuperSU/SuperUser less slow? I mean, on a virgin rom it's already not so fast, but after you install your apps, it can takes minutes before the pop-up asking for root rights comes, if it comes..!! So is there a way to "fix" that? It's a pain, having to reboot sometimes cause of that!
Thanks.
Click to expand...
Click to collapse
Set it to automatically grant permissions and turn notifications off, but remember that this is very insecure way so don't install any untrusted apps.
I've thought of that, but i'm not sure it would help : If it waits, let's say 2minutes, for showing pop-up asking for rights, then it would also wait 2minutes before automatically allowing apps...
2 minutes?? It should show immediately, so there is something wrong in your rom. Try to wipe cache and dalvik cache and fix permissions.
Man, this is not in MY ROM, this is in ANY roms... Seems that the more apps installed (=the more process running) the slower it'll be!
I agree. I have the same problem. I'm running CM13 (Marshmallow) on my old S3 i9300, and I flashed SuperSu (beta) for it. It work well, but its slow to grant permissions even when its meant to do so automatically. I've set it to start at boot, but this hasnt done much. Any fixes??
Same problem also here with every rom that I used it. Root in cm roms is almost instant.
same here on a custom cm12.1 rom
What the heck are you guys talking about? 2 minutes?! That is just plain wrong. I won't say impossible, cause you obviously have problems, but I have never seen that behavior you're talking about, and that is absolutely not caused by SuperSU or Superuser. Even my 7 years old HTC HD2 asks for, or grants root in 2 seconds max. Tell your developers to fix their ROMs.
Sent from my HTC One M9 using Tapatalk
Can it be that "Clean Master" or some other memory management software is pushing SuperSU back. Try uninstalling any memory management software.
never had issue having to wait for 2min either and ive rooted almost 50 diffrent phone from ics to lollipop to my current headache oppo mirror 5 still superSU still doing its job
I can confirm this is a real problem, but can also confirm it goes away with tweaking.
On aosp, it's important to disable the native su in dev options.
In anything else, for instance touch wiz, I have learned that system less root is evil, and mount separate name spaces is the devil.
Now, when installing prerooted rom, kernels etc, it's imperative to get your supersu set up prior to installing your root apps...or it will hit the fan....well..that's dramatic. It'll act oddly and you'll never realize what's causing things to be weird.
First and foremost, uncheck mount separate blah blah and reboot. Then, attempt to install supersu to system. If it fails after reboot, twice, then you must return the check mark to mount name spaces and reboot.
Once rebooted, try the "cleanup for reinstallation" and if that succeeds in allowing you to update/reinstall from play store, try to uncheck the mount name spaces again...then attempt the system install again...should work this time...
EDIT the point of all this is to test the app and the connection with the binary. If the app can't control the binary stuff, you'll probably be seeing lag. By doing all the options and checks that tweak the binary, you will have a good supersu environment, and the lag will disappear.
When you finally get supersu to do the things with its binary without crashing, you'll notice no more lag.
Further more, disabling notifications is an ABSOLUTE MUST. From @Chainfire himself, he suggests turning off notifications to get rid of overhead, and he states that logging does not effect it much, and after HUNDREDS of man hours tweaking and fiddling with supersu in every arena, from system less, to autoroot, I could not agree more.
Throw the man some love, respect, and donations, because he's at the front of the pack, hacking the infinite combinations of phones, to couriers, to software, to user intelligence.
His app is rock solid. The billions of other x factors are to blame
2nd edit mount name spaces will cause all sorts of odd things, so I disable that always, as well as notifications.
It's important to note, you'll always have delay for root requests in the first few minutes after boot, as certain things like scripts and even supersu itself might be denying for the first few minutes.
Enabling supersu at boot might help, actually it will help, but I've never needed it after configuring my root environment properly.
When everything fails, I Uninstaller root completely, and either reflash supersu, or my prerooted kernel of choice
3rd edit. Sigh, sorry. I notice my environment is in need of tweaking nearly 100% of the time when I flash a prerooted kernel, then a prerooted rom. Even flashing the kernel again, as is sometimes required for a rom not tailored for my device, will cause things to get out of wack which I notice instantly, when I got supersu lag
check if any other app stopping it.
I always update su binary, set the access to grant and delete su app.
Its d fastest way.
Read rules before posting questions on development forum¡*
Ur thread will b moved immediately.
BatDroid said:
check if any other app stopping it.
I always update su binary, set the access to grant and delete su app.
Its d fastest way.
Read rules before posting questions on development forum�?�¡*
Ur thread will b moved immediately.
Click to expand...
Click to collapse
â?¦
I don't even know how to process this ?¦ try my way first¦
I'd bet anything the speed will be just as fast¦ and i forgot to mention, i always enable full logging? so full logging, no lag?vs no nothing, no app, security etc
loogielv said:
I can confirm this is a real problem, but can also confirm it goes away with tweaking.
On aosp, it's important to disable the native su in dev options.
In anything else, for instance touch wiz, I have learned that system less root is evil, and mount separate name spaces is the devil.
Now, when installing prerooted rom, kernels etc, it's imperative to get your supersu set up prior to installing your root apps...or it will hit the fan....well..that's dramatic. It'll act oddly and you'll never realize what's causing things to be weird.
First and foremost, uncheck mount separate blah blah and reboot. Then, attempt to install supersu to system. If it fails after reboot, twice, then you must return the check mark to mount name spaces and reboot.
Once rebooted, try the "cleanup for reinstallation" and if that succeeds in allowing you to update/reinstall from play store, try to uncheck the mount name spaces again...then attempt the system install again...should work this time...
EDIT the point of all this is to test the app and the connection with the binary. If the app can't control the binary stuff, you'll probably be seeing lag. By doing all the options and checks that tweak the binary, you will have a good supersu environment, and the lag will disappear.
When you finally get supersu to do the things with its binary without crashing, you'll notice no more lag.
Further more, disabling notifications is an ABSOLUTE MUST. From @Chainfire himself, he suggests turning off notifications to get rid of overhead, and he states that logging does not effect it much, and after HUNDREDS of man hours tweaking and fiddling with supersu in every arena, from system less, to autoroot, I could not agree more.
Throw the man some love, respect, and donations, because he's at the front of the pack, hacking the infinite combinations of phones, to couriers, to software, to user intelligence.
His app is rock solid. The billions of other x factors are to blame
2nd edit mount name spaces will cause all sorts of odd things, so I disable that always, as well as notifications.
It's important to note, you'll always have delay for root requests in the first few minutes after boot, as certain things like scripts and even supersu itself might be denying for the first few minutes.
Enabling supersu at boot might help, actually it will help, but I've never needed it after configuring my root environment properly.
When everything fails, I Uninstaller root completely, and either reflash supersu, or my prerooted kernel of choice
3rd edit. Sigh, sorry. I notice my environment is in need of tweaking nearly 100% of the time when I flash a prerooted kernel, then a prerooted rom. Even flashing the kernel again, as is sometimes required for a rom not tailored for my device, will cause things to get out of wack which I notice instantly, when I got supersu lag
Click to expand...
Click to collapse
As he said i have dissabled notifications and worked, Thanks Man
I've had this problem on a Samsung Galaxy J7 (2016). It was because I disabled the encryption of /data. For details on how to solve it see here. I think there are probably other factors that can cause this, so this solution is probably not for everyone. But I would recommend checking your adb logcat to figure out if something is going on in the background that should not.
Since I installed SuperSu 2.79 on my klte on RR (los, android 7.1.1) the device started lagging, not a lot but enough to be annoying.

Zygote and Whatsapp requesting root??

Hello, I have a Redmi Note 3 Pro running sMiUI (based on the Xiaomi.eu ROM) but this seems to be irrelevant.
while this strange behaviour doesn't seem to be limited to this device, being noted here and here, it does seem that the symptoms are the same.
In the SuperSU logs i found that firstly Whatsapp tried to gain root and was denied, followed by zygote requesting 3 times over the following few hours. The log for each is blank.
I have just rebooted my device and after unlocking whatsapp immediately requested root. Yet to see zygote request root again but I'll update you should it appear.
UPDATE: Whatsapp has again requested root.
UPDATE2: WhatsApp continues to request, however zygote has not. It appears to be happening every half-hour (ish)
U3: uninstalled WhatsApp, will see what happens at the half-hour mark.
Anyone know what's going on?
Also some probably irrelevant weirdness but I'll write it anyway given this only started appearing after this happened:
My phone did something weird earlier, I restarted, and normally on my ROM it just has a spinning little loading thingy in the middle of an otherwise blank screen, then goes off and reboots, showing the Mi logo, this time however it randomly showed a kinda-pulsating android logo shortly after the usually " spinning loading icon" and then continued to the usual Mi logo. Given I'm running sMiUI I've never seen it display a large android logo before like this. I just rebooted again and this behaviour was not repeated.
Try xiaomi.eu rom, or stock rom. Or might be you're just installed modified WhatsApp and zygote apk from untrusted source. I don't use sMIUI
immns said:
Try xiaomi.eu rom, or stock rom. Or might be you're just installed modified WhatsApp and zygote apk from untrusted source. I don't use sMIUI
Click to expand...
Click to collapse
The struggle I went through to get off of the vendor ROM, I'm not going back to stock. sMiUI was based on the Xiaomi.eu ROM, so the zygote is probably straight out of that.
I have installed WhatsApp from Google Play so I assume it doesn't get more secure than that. I've made no attempt to replace zygote, I don't really know what it does, something about starting apps.
The ROM I'm using doesn't seem to be remotely relevant to this, given it's happened on 3 different devices from different brands as I can see from the links I provided.
It doesn't make any sense. WhatsApp is used to not request any root permission unless it's infected by mallware. You can try to use xiaomi.eu rom alongside with 3rd party mods instead of use pre-moded rom from sMIUI.
immns said:
It doesn't make any sense. WhatsApp is used to not request any root permission unless it's infected by mallware. You can try to use xiaomi.eu rom alongside with 3rd party mods instead of use pre-moded rom from sMIUI.
Click to expand...
Click to collapse
Indeed, last WhatsApp update was 13th December, so I would have seen this happening before today if it was in normal WhatsApp. This is nothing to do with sMiUI, I've had this ROM installed for many months now with no issues.
And as previously stated it is based on Xiaomi.eu ROM.
But yes my suspicion is malware, however it's not specific to MIUI or any varients as this was also occurring on a Galaxy S5 and another device.
Everyone: Please read the entire thread before replying so I don't have to keep restating facts
Hey, i have same problem too, im using redmi note 2, today i get notif, whatsapp need access root, after several minute, zygote need access root too, now i deny that access at super su
first time root/customrom/kernel etc.
Ive had the same thing happen..First time I thought it was strange though and denied permision was with the zygote thing asking permission...ive granted whatsapp and whatsapp extensions permisson for example cause i thought that was just the way it worked. ive granted LMT permission and a couple more apps
thought it was more of a windows type "" do you trust this program to do things" type thing.
things is my, installation is pretty fresh. and I dont get where I should've gotten malware from
htcm8/Viperrom/elementalx kernel
bunch of file explorers (sdmaid /totalcommander) and terminals all from the playstore. Xposed installer and a couple modules that all seemed reputable with ongoing xda threads and downloaded from the original source. amplify/bootmanager(something with that maybe?)/chromepie/secure settings for a tasker profile/minminguard.
you see something we have in common on the phone?
phone is running fine..nothing strange. The zygote i got for the first time today and I denied and hopped on google...whatsapp is in my rootlog constantly. i see the greybox popping up every once in a while that root was granted. never thought anything of it.
today I installed termux ternimal from the playstore...maybe thats where the zygote su request comes from?
---------- Post added at 10:05 PM ---------- Previous post was at 09:39 PM ----------
from what I see elsewhere the whatsapp extension module in xposed, which is a root app might have something to do with the whatsapp requests. I dont exactly know how these things work but the altering might explain app doing thing they normally dont do.
dont know about zygote...got it one time and it has not been back
Same here.
I'm on a fresh install and this zygote su request wasn't appearing until I reinstalled all my apps.
Another forum states that zygote is run at such a raw level that it simply would never request root.
I am for now denying su requests with little to no adverse effects.
Can anyone confirm for certain that zygote should never need to request root? Is there anyway to dig out the rogue source/apk when av apps are showing nill?
As I have nothing Whatsapp on my phone, thinking it may be an xposed mod. Might be a good idea for us to list are xposed mods so we can cross reference. Not sure?
samsung i9505 | resurrection remix | android 6

Removing Stock Apps -> no updates?

Hi all!
Last time I modded a phone was cyanogen mod on my samsung galaxy s (yes no number), and from back then I remember that simply uninstalling stock apps caused problems when updating.
Since that's what I want to do again now (too much bloat on that phone...), I wanted to ask if I still will be running into such issues with it.
I dont want to change the ROM, just remove a lot of the apps I dont want/use, will I still be able to get updates from xiaomi w/o problems?
Thanks for reading, much appreciated!
Yep, no problems with updates. Right after receiving the phone I removed (from the system and via adb) a lot of preinstalled bloatware, including some Xiaomi apps and the phone was updated to MIUI 9.6.22 without any problems.
katoda_ltd said:
Yep, no problems with updates. Right after receiving the phone I removed (from the system and via adb) a lot of preinstalled bloatware, including some Xiaomi apps and the phone was updated to MIUI 9.6.22 without any problems.
Click to expand...
Click to collapse
i already uninstalled what the system allowed me to w/o root, did you remove anything requiring root (i dont know what adb is...)?
My device is not rooted, for most bloatware concerned root is not necessary while using adb.
See https://forum.xda-developers.com/poco-f1/how-to/debloating-xiaomi-poco-f1-safe-to-t3836119 and https://forum.xda-developers.com/poco-f1/how-to/bloat-poco-f1-tested-t3836457 but read them thoroughly, as there are some comments that some of the safe-to-remove services/app are indeed required to properly operate the device.
What is adb and how to get it: https://forum.xda-developers.com/showthread.php?t=2317790
katoda_ltd said:
My device is not rooted, for most bloatware concerned root is not necessary while using adb.
See https://forum.xda-developers.com/poco-f1/how-to/debloating-xiaomi-poco-f1-safe-to-t3836119 and https://forum.xda-developers.com/poco-f1/how-to/bloat-poco-f1-tested-t3836457 but read them thoroughly, as there are some comments that some of the safe-to-remove services/app are indeed required to properly operate the device.
What is adb and how to get it: https://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
thank you very much, i even found out why i couldnt get updates any longer back in the day (with root):
These two commands respectively specify that the system app will only be uninstalled for the current user (and not all users, which is something that requires root access) and that the cache/data of the system application will be preserved (which can’t be removed without root access). Therefore, even if you “uninstall” a system application using this method, you can still receive official OTA updates from your carrier or OEM.
Click to expand...
Click to collapse

Can miui security center be removed?

hello,
been having this weird bug/problem with com.miui.security center with every miui 9 release for poco(miui 10/pie security app runs fine but i didnt like miui10!)
the strange thing is that xiaomi is sending updates to all its apps on miui 9 exept security center!!(am talking about the app update not about the antivirus defs update etc).
the question is : can i remove the security app?and how?( am on miui 9.6.14 global stable ....rooted).
Install Titanuim Backup and uninstall from there.
P.S you can run into problems and force close issues along with other unbearable ****. so backup Security App on Titanium Backup and then uninstall it
Don't even think of uninstalling the Security app. I tried it twice and ended up in bootloop. I spoke to a miui dev and he said Security app is an essential part of miui rom and messing with it means messing with the ROM.
Right
Same here
com.miui.securitycenter
Need a mod for this can someone help.
How do i mod this so that all undesirable tracking & spyware components can be removed. It is obvious that this of a tracker agent making it unsafe for the user only makes it safer for XIamoi & its partners.
So I opened up the the app components-
Broadcast receivers activities services etc. And here is what I found .....
In something that supposedly claims to be a for security component for the phone
- Dunno if they will let me stick in a screenshot here . There are adware and spyware components down to the core.
Code:
AdsProcessPriorityService
com.facebook.ads.internal.ipc.AdsProcess
PriorityService
AdsMessengerService
com.facebook.ads.internal.ipc.AdsMessen
gerService
That is to name a few
- any attempt to disable this component is futile because even if you run pm disable the component is force enabled
- the other singers if I am rooted and I am ' magiskcally ' I hide magisk from all these redmi components. ..... even Here it forces need to unhide magisk could you see the extent of spyware organisation down to the core
I would like to continue this thread with an invitation to vah word wants to give me an approach and work with me so that a magisk module that will grab his component from the current phone and mod it -let the original spyware component load during boot time and post boot do a swap with the mod
Is it possible to do this kind of modification & unspy MIUI
Yes it can be. Use lucky patcher and "delete system app". It worked for me without bootloop. I think there wasn't many things changed after that except for no 10s warnings and no sidebar functions
Vipxpert said:
Yes it can be. Use lucky patcher and "delete system app". It worked for me without bootloop. I think there wasn't many things changed after that except for no 10s warnings and no sidebar functions
Click to expand...
Click to collapse
i can confirm this , i on miui 13.0.11 , redmi note 10(mojito) . uninstalled com.miui.securitycenter , rebooted . no bootloop. i will let other know if i encounter some bug later
Edit1: cant open battery setting, manage apps show nothing
Vipxpert said:
Yes it can be. Use lucky patcher and "delete system app". It worked for me without bootloop. I think there wasn't many things changed after that except for no 10s warnings and no sidebar functions
Click to expand...
Click to collapse
can i delete miui cleaner ?
Apih95 said:
can i delete miui cleaner ?
Click to expand...
Click to collapse
Well.... Isnt that intergrated into Security Center app as well lol
ron_hyatt said:
hello,
been having this weird bug/problem with com.miui.security center with every miui 9 release for poco(miui 10/pie security app runs fine but i didnt like miui10!)
the strange thing is that xiaomi is sending updates to all its apps on miui 9 exept security center!!(am talking about the app update not about the antivirus defs update etc).
the question is : can i remove the security app?and how?( am on miui 9.6.14 global stable ....rooted).
Click to expand...
Click to collapse
Lucky patcher (slightly sketchy) and De-Bloater appear to work to remove apps on rooted devices
Obviously
Code:
adb shell pm uninstall --user 0 com.miui.securitycenter
will not remove it but if all you need is it to be disabled you can try that
Hello, this probably won't be seen, but to the very few travelers who discover this message on google or something:
As of January 19th 2023, the "Security Center" application on MIUI 13 is extremely sketchy.
I'm planning on trying to decompile it if possible.
Currently (According to the AOSP part of the settings) The app has permissions that are very worrying. Downloading files without permission, proprietary MIUI perms, full network access, etc.
Not only that, the built-in package manager utility (PM), refuses to disable com.miui.securitycenter due to being unable to "disable core miui packages..." and spitting out an exception dump.
This is clearly a protected app, that has too many permissions, for no apparent reasson.
Setting SELinux to permissive dosen't help either.
There are 2 options that people have currently - Either leaving a piece of a PUP (Potentially unwanted program) on their phone, or risking bricking it by uninstalling it.
According to the posts on this thread some people have had success, some got a soft-brick.
Doing so shouldn't result in a hard brick, so if you have backups, a userdata format should solve the issue.
TheMagnificent_Y said:
Hello, this probably won't be seen, but to the very few travelers who discover this message on google or something:
As of January 19th 2023, the "Security Center" application on MIUI 13 is extremely sketchy.
I'm planning on trying to decompile it if possible.
Currently (According to the AOSP part of the settings) The app has permissions that are very worrying. Downloading files without permission, proprietary MIUI perms, full network access, etc.
Not only that, the built-in package manager utility (PM), refuses to disable com.miui.securitycenter due to being unable to "disable core miui packages..." and spitting out an exception dump.
This is clearly a protected app, that has too many permissions, for no apparent reasson.
Setting SELinux to permissive dosen't help either.
There are 2 options that people have currently - Either leaving a piece of a PUP (Potentially unwanted program) on their phone, or risking bricking it by uninstalling it.
According to the posts on this thread some people have had success, some got a soft-brick.
Doing so shouldn't result in a hard brick, so if you have backups, a userdata format should solve the issue.
Click to expand...
Click to collapse
i recommend lineageos rom instead of miui but make backups
Hi I'm struggling with the same problem trying to stop de SecCenter. Maybe there is a way to stop the app to run. I tried on my Note 10 Pro with MIUI12.0.6 Global (Android 11) and it works.
You need root on the phone. You should change the owner of the folder "/data/user/0/com.miui.securitycenter" to a user the is not System. In my case a run the command "chown -R root:root /data/user/0/com.miui.securitycenter". After that you need to kill the process of the "com.miui.securitycenter". So at the end the process doesn't start anymore. In the next boot you need do the process again because the boot change the permission of the folder to the system again.
I'm trying to create a Magisk Module to do that but i don't know how until now.

Categories

Resources