Database Develop

CM-su still being detected by Magisk, Magisk Hide not working

Hi,
I'm currently so confused as to why my Magisk isn't working. I'm currently running the last CM 13 snapshot for the Galaxy S5 (G900F, klte), and root and Xposed work fine via Magisk.
However, what isn't working is Magisk Hide, and I'm not sure why. However, I'm noticing that even though I fully unrooted cm-su (using SuperSU, in a way that means the only root I can select in Dev Options is ADB only), I'm still getting cm-su detected by Magisk.
I'm confused -- is there anyway I can remove it? I've tried looking through TWRP file manager, but whenever I do so, I can't even see /system/ files, and mounting only mounts to USB, but that's unrelated.
Thanks for any help!

intcompetent said:
Hi,
I'm confused -- is there anyway I can remove it? I've tried looking through TWRP file manager, but whenever I do so, I can't even see /system/ files, and mounting only mounts to USB, but that's unrelated.
Click to expand...
Click to collapse
I don't think SuperSU removes the in-built CM superuser. Use the UNSU zip by osmosis instead. https://forum.xda-developers.com/showthread.php?t=2239421
Also magisk hide will NOT hide Xposed. Yes not even systemless 87.1 Xposed.

SuperSU removed its own root only, CM root is unaffected.
Also, Magisk hide only works with Magisk's own phh root.
And, as far as I know, it can't successfully hide Xposed either. Doesn't matter if it is systemless or not.

Cheers for the replies.
I wasn't aware that Magisk Hide didn't hide Xposed, that's my bad.
As for the presence of CM-SU, SuperSU did do something, as the Developer Options root option is now ADB only while previously it offered the option to Apps too. I'll try unsu.
Here's what I'm meaning btw: imgur.com /a /yTOTw (sorry for the link bypass, there's no other way for me to simply demonstrate the issue) (as you can see in the first screenshot, Magisk detects "cm-su" along with phh. When phh was disabled before I removed cm-su, it only detected cm-su, hence leading me to believe cm-su remains).
e: tried unsu, still cm-su remains. At this point, I'll leave it -- I presume that it's permanently ingrained into the ROM. I've gotten around the restriction I was facing anyway, and I'll adjust. Thanks anyway!

intcompetent said:
Cheers for the replies.
I wasn't aware that Magisk Hide didn't hide Xposed, that's my bad.
As for the presence of CM-SU, SuperSU did do something, as the Developer Options root option is now ADB only while previously it offered the option to Apps too. I'll try unsu.
Here's what I'm meaning btw: imgur.com /a /yTOTw (sorry for the link bypass, there's no other way for me to simply demonstrate the issue) (as you can see in the first screenshot, Magisk detects "cm-su" along with phh. When phh was disabled before I removed cm-su, it only detected cm-su, hence leading me to believe cm-su remains).
e: tried unsu, still cm-su remains. At this point, I'll leave it -- I presume that it's permanently ingrained into the ROM. I've gotten around the restriction I was facing anyway, and I'll adjust. Thanks anyway!
Click to expand...
Click to collapse
If there are SU files in /system/bin and /system/xbin, then CM root was not removed. Not completely.
To actually remove it you have to delete those files.

Pwnycorn said:
If there are SU files in /system/bin and /system/xbin, then CM root was not removed. Not completely.
To actually remove it you have to delete those files.
Click to expand...
Click to collapse
@intcompetent Osmosis's unsu zip removes those files. If those files are still there after flashing the unsu zip, I'd ask in his thread.

knpk13 said:
@intcompetent Osmosis's unsu zip removes those files. If those files are still there after flashing the unsu zip, I'd ask in his thread.
Click to expand...
Click to collapse
Or just remove them manually, jeez. It's just two files.
I've been doing it manually for months and everything works as intended.

As an a closer, there's nothing there. I presume that Magisk is picking up something freaky from somewhere, or something's up, but I'm good guys. I won't need anymore help.
Cheers!

I found this zip around somewhere. I believe it works to remove all root (systemless as well) and I've always flashed it before rooting normally. It should also remove CM root afaik.
As a test, after flashing, check and see if you pass safetynet before installing magisk

intcompetent said:
As an a closer, there's nothing there. I presume that Magisk is picking up something freaky from somewhere, or something's up, but I'm good guys. I won't need anymore help.
Cheers!
Click to expand...
Click to collapse
I
L

PADRadar2.7.1 now detecting magisk.

Updated the game PADRadar to 2.7.1, the game can not run now.Every method is tried,the only way is uninstalling the magisk.Who can help me?

Jacky Zhou said:
Updated the game PADRadar to 2.7.1, the game can not run now.Every method is tried,the only way is uninstalling the magisk.Who can help me?
Click to expand...
Click to collapse
First of all, ensure that Magisk Hide is set up properly and you have selected PADRadar within Magisk Hide list. Second, delete the Magisk Manager folder that can be found on your internal storage. Third, use the option to re-pack Magisk Manager with a random package name (can be done from within Magisk options). Last, force-stop the game and clear its cache and maybe data (be aware that you might lose your game process if you delete the game data, so be careful). Reboot your device and check again.

seems like a lot of apps are now detecting magisk
maybe they are looking for more than just magisk folder, su, busybox etc..
like samsung pay for the gear

TheUndertaker21 said:
seems like a lot of apps are now detecting magisk
maybe they are looking for more than just magisk folder, su, busybox etc..
like samsung pay for the gear
Click to expand...
Click to collapse
that would be impossible to detect magisk's folder since it's like an img file which needs to be mounted first before accessing it. However there is always a way, i suppose

Is Magisk Faux root?

I have been rooting my Androids since the original G1 and obviously have always used a traditional root method. I have been trying to do some research on what to do with my next device, traditional root or systemless. The obvious advantage of systemless is passing safety net and probably not have to worry about using root cloak, although root cloak still serves me well to this day. The disadvantages I have found is that because Magisk doesnt actually modify system files it just puts a modified file over the existing one on boot you cannot actually simply go into say root explorer, take any file on the system partition and modify it. Which to me seems like a major disadvantage to anyone who likes to modify files in the system partition. I mean something as simple as swapping out a font file is not longer just a copy paste and change permissions. Am i completely off base on this thinking? Please correct me if I am wrong. The only part that seems to be a huge disadvantage to true root is no one is actually developing SuperSU anymore now that ChainFire sold it from what I understand but there is still the old school superuser app that i believe was open source and could be developed on, as I understood the Superuser apps only denied or granted superuser authority did not actually root the device in the first place anyway.

First of all, SuperSU was systemless root long before Magisk...
I believe you're confusing MagiskSU with Magisk modules and Magic mounting. It's perfectly possible to alter /system while Magisk is installed, as long as you don't have a module that is magic mounting files over that particular part of /system. If that's the case, you'll just be trying to alter the Magisk mask instead of the actual files. If you're not using modules, or if you keep Core Only Mode enabled this won't be an issue.
But, even with magic mounting active you've got full access to the original /system files in /sbin/.magisk/mirror.

Didgeridoohan said:
First of all, SuperSU was systemless root long before Magisk...
I believe you're confusing MagiskSU with Magisk modules and Magic mounting. It's perfectly possible to alter /system while Magisk is installed, as long as you don't have a module that is magic mounting files over that particular part of /system. If that's the case, you'll just be trying to alter the Magisk mask instead of the actual files. If you're not using modules, or if you keep Core Only Mode enabled this won't be an issue.
But, even with magic mounting active you've got full access to the original /system files in /sbin/.magisk/mirror.
Click to expand...
Click to collapse
ah yes i do recall hearing about systemless SuperSU but it seemed that it just installed SuperSU on the user partition and not as a system app and still allowed modifying the system partition. Sorry for my ignorance about this just tough to google how magisk actually works compared to normal root. So if I have magisk it is systemless root but I can still modify the system partition? Thats good to know. What about when it comes to Xposed, can you use normal Xposed with systemless root or do you have to use systemless xposed? Im currently running lolipop with full root and xposed framework but have a new device with Oreo that Ill probably give Magisk a shot with I just want to know the differences I should expect with what you can and cannot do.

Joe333x said:
ah yes i do recall hearing about systemless SuperSU but it seemed that it just installed SuperSU on the user partition and not as a system app and still allowed modifying the system partition. Sorry for my ignorance about this just tough to google how magisk actually works compared to normal root. So if I have magisk it is systemless root but I can still modify the system partition? Thats good to know. What about when it comes to Xposed, can you use normal Xposed with systemless root or do you have to use systemless xposed? Im currently running lolipop with full root and xposed framework but have a new device with Oreo that Ill probably give Magisk a shot with I just want to know the differences I should expect with what you can and cannot do.
Click to expand...
Click to collapse
Yes you can use normal xposed on systemless root, systemless root basically roots by patching the kernel's ramdisk with the SU binary them magisk just install it's remaining binaries in the data partition and them proceeds to hide them through some Linux mounting tricks (it's just a simplified explanation) it's still normal root but the system partition gets intact,magisk and it's modules (in it's repository) use systemless installations as to hide from integrity checks like safetynet and allows you to more easily retain mods during rom updates,other than that magisk is just root with module and hiding functionality
---------- Post added at 12:53 AM ---------- Previous post was at 12:46 AM ----------
Joe333x said:
ah yes i do recall hearing about systemless SuperSU but it seemed that it just installed SuperSU on the user partition and not as a system app and still allowed modifying the system partition. Sorry for my ignorance about this just tough to google how magisk actually works compared to normal root. So if I have magisk it is systemless root but I can still modify the system partition? Thats good to know. What about when it comes to Xposed, can you use normal Xposed with systemless root or do you have to use systemless xposed? Im currently running lolipop with full root and xposed framework but have a new device with Oreo that Ill probably give Magisk a shot with I just want to know the differences I should expect with what you can and cannot do.
Click to expand...
Click to collapse
And if you are wondering how systemless mods (magisk modules) work they are basically 'mirrored' to the system partition during start up but the module itself is in the data partition

DanGLES3 said:
Yes you can use normal xposed on systemless root, systemless root basically roots by patching the kernel's ramdisk with the SU binary them magisk just install it's remaining binaries in the data partition and them proceeds to hide them through some Linux mounting tricks (it's just a simplified explanation) it's still normal root but the system partition gets intact,magisk and it's modules (in it's repository) use systemless installations as to hide from integrity checks like safetynet and allows you to more easily retain mods during rom updates,other than that magisk is just root with module and hiding functionality
---------- Post added at 12:53 AM ---------- Previous post was at 12:46 AM ----------
And if you are wondering how systemless mods (magisk modules) work they are basically 'mirrored' to the system partition during start up but the module itself is in the data partition
Click to expand...
Click to collapse
Thanks for the explanation I appreciate it, so now i guess my only question left is after I use magisk to root and then modify a file on the system partition will I now not pass safety net? I typically dont care about passing since I havent in years but just figured its a question worth asking.

Joe333x said:
Thanks for the explanation I appreciate it, so now i guess my only question left is after I use magisk to root and then modify a file on the system partition will I now not pass safety net? I typically dont care about passing since I havent in years but just figured its a question worth asking.
Click to expand...
Click to collapse
If you are on an old device it's possible you still will pass,but sometimes altering an file on the conventional way will trip safetynet,that's why systemless modules are a thing

Just altering regular files shouldn't affect things though. It usually takes ROM level alterations...

[DEBLOAT] OOS 9.5.x De-bloat (Systemless+Automated+Easily Reversible) [Aug 28]

This script was made to 9.5.8 OP7 OxygenOS, some things can be different in future, so report if something is broken. Use at your own risk and feel free to experiment as this is a systemless mod.
First, the prerequisites:
1- Unlocked bootloader with Magisk and TWRP (you can use temporary TWRP if you please). If you don't know what is that, take a look at the XDA threads about it, it's easy. Please don't ask about "how to unlock bootloader" or "how to install Magisk".
2- Debloater (Terminal Emulator) Magisk module. Download it from Magisk Manager.
3- Any Terminal Emulator app.
4- import-debloat.txt config file. Download it here
5. Backup (yeah, this module doesn't change anything in /system and can be reverted at any time, but backups are always welcome)
6. Magisk Mount script. Download it from here
Magisk mount is needed to "reinstall" system apps by deleting the dummy folders from Magisk partition if something breaks.
If you have everything handy it should be a matter of few seconds to debloat.
Let's deal with useless system apps, temeletry, some ****ty apps. According from the @Tomatot- thread:
Tomatot- said:
-You'll get more privacy: I've removed Qualcomm telemetry, OnePlus telemetry as well as some Google Telemetry (but you can't expect too much as long as you use gapps)
-You'll get better battery life: less apps running in the background, less wakelocks, less services communicating with servers to send telemetry.
-You'll get better performance: for the same reasons. Don't expect a huge difference as our phone is very smooth already.
-The feeling of having a clean device. And this has no price.
Click to expand...
Click to collapse
Debloated apps list (It's the same Tomatot-'s Light app list):
Code:
AntHalService^=/system/app/AntHalService
AutoRegistration^=/system/app/AutoRegistration
BasicDreams^=/system/app/BasicDreams
BookmarkProvider^=/system/app/BookmarkProvider
BTtestmode^=/system/app/BTtestmode
PrintService^=/system/app/BuiltInPrintService
card^=/system/app/card
EasterEgg^=/system/app/EasterEgg
EgineeringMode^=/system/app/EngineeringMode
EngSpecialTest^=/system/app/EngSpecialTest
GooglePrint^=/system/app/GooglePrintRecommendationService
GoogleTTS^=/system/app/GoogleTTS
LogKitSdService^=/system/app/LogKitSdService
NetflixActivation^=/system/app/Netflix_Activation
NetflixStub^=/system/app/Netflix_Stub
NFCTestMode^=/system/app/NFCTestMode
OEMTCMA^=/system/app/oem_tcma
OEMAutoTestServer^=/system/app/OemAutoTestServer
OEMLogKit^=/system/app/OEMLogKit
OnePlusBugReport^=/system/app/OPBugReportLite
OnePlusCommonLogTool^=/system/app/OPCommonLogTool
OPSesAuthentication^=/system/app/OPSesAuthentication
PartnerBoorkmarksProvider^=/system/app/PartnerBookmarksProvider
PhotosOnline^=/system/app/PhotosOnline
PlayAutoInstallConfig^=/system/app/PlayAutoInstallConfig
QdcmFF^=/system/app/QdcmFF
RFTuner^=/system/app/RFTuner
SensorTestTool^=/system/app/SensorTestTool
SoterService^=/system/app/SoterService
Stk^=/system/app/Stk
Talkback^=/system/app/talkback
Traceur^=/system/app/Traceur
UIMRemoteClient^=/system/app/uimremoteclient
Video^=/system/app/Videos
WallpaperBackup^=/system/app/WallpaperBackup
WAPICertManage^=/system/app/WapiCertManage
WIFIRFTestApk^=/system/app/WifiRfTestApk
GoogleFeedback^=/system/priv-app/GoogleFeedback
OnePlusCellBroadcastReceiver^=/system/priv-app/OPCellBroadcastReceiver
Tag^=/system/priv-app/Tag
USBDrivers^=/system/etc/usb_drivers.iso
Reserve^=/system/reserve
RFToolkit^=/vendor/app/Rftoolkit
AmazonShittyApps^=/vendor/etc/apps
Account^=/system/app/Account
OPBackup^=/system/app/Backup
BackupRestoreRemoteService^=/system/app/BackupRestoreRemoteService
CarrierDefaultApp^=/system/app/CarrierDefaultApp
CTSShimPrebuilt^=/system/app/CtsShimPrebuilt
GoogleDrive^=/system/app/Drive
GoogleDuo^=/system/app/Duo
GooglePay^=/system/app/GooglePay
HTMLViewer^=/system/app/HTMLViewer
GooglePlayMusic^=/system/app/Music2
NVBackupUI^=/system/app/NVBackupUI
OnePlusPush^=/system/app/OPPush
YouTube^=/system/app/YouTube
BackupRestoreConfirmation^=/system/priv-app/BackupRestoreConfirmation
CallLogBackup^=/system/priv-app/CallLogBackup
CTSShimPrivPrebuilt^=/system/priv-app/CtsShimPrivPrebuilt
GoogleRestore^=/system/priv-app/GoogleRestore
GoogleBackupTransport^=/system/priv-app/GoogleBackupTransport
GoogleOneTimeInitializer^=/system/priv-app/GoogleOneTimeInitializer
ManagedPrivisioning^=/system/priv-app/ManagedProvisioning
OnePlusWizard^=/system/priv-app/OnePlusWizard
OPAppLocker^=/system/priv-app/OPAppLocker
OnePlusDeviceManager^=/system/priv-app/OPDeviceManager
OnePlusDeviceManagerProvider^=/system/priv-app/OPDeviceManagerProvider
SharedStorageBackup^=/system/priv-app/SharedStorageBackup
Let's start this!
1. Copy the import-debloat.txt config file to the folder /data/cache in the root. (you can copy it by a root explorer or reboot into recovery and copy it by TWRP file explorer)
2. Install the Debloater (Terminal Emulator) Magisk module using the Magisk Manager.
3. Open the terminal emulator app
> Type 'su' and press enter
> Grant root permissions
> Type debloat and press enter.
4. You will see the options to debloat in various categories which are self explanatory. As we have the config file which has a predefined app list to de-bloat stored in /data/cache folder in root already. Type 'i' which says import config and press enter 2 times.
5. Reboot 2 times and you're done most probably if nothing breaks.
Ta-dah! Fully debloated OOS. To keep the debloat after update the ROM, just reflash Magisk and you're fine. You don't need to do the procedure every update.
Read from here if something breaks (from @Sreekant)
If it breaks the system or causes boot-loop which shouldn't be the case as I'm using the OP7 9.5.8 and everything is fine, but well, **** happens. Don't worry! It's pretty easy to reinstall all of them in one click by TWRP.
Did you download the Magisk Mount script which I asked to earlier? If yes, just flash it with TWRP and the magisk will be mounted and accessible in TWRP file explorer. If you didn't download the script earlier, Just adb sideload it in recovery.
After mounting the Magisk in TWRP > Click on Advanced and go to file explorer.
Then delete the app folder of the system app you've uninstalled in /Magisk/terminal_debloater/system/app (/sbin/.core/img/terminal_debloater/system/app) or /Magisk/terminal_debloater/system/priv-app (/sbin/.core/img/terminal_debloater/system/priv-app) then that should undo it.
Click to expand...
Click to collapse
----------------------
Feel free to give any feedback about the script.
Special thanks to:
@Tomatot- (the apps list and some explanations are from his thread)
@Sreekantt (the thread base and original idea from debloat for Poco F1)
@topjohnwu (Magisk developer)
The Debloater (terminal) team

Hi, welcome and thanks for your work..as I understand , that is magisk module to use for debloat ? If you used script from Tomato, is it light debloat or which one. More info about that will be nice..thanks again

marko94 said:
Hi, welcome and thanks for your work..as I understand , that is magisk module to use for debloat ? If you used script from Tomato, is it light debloat or which one. More info about that will be nice..thanks again
Click to expand...
Click to collapse
I took the Light debloat from Tomatot and converted to Debloat (Terminal Emulator) module syntax. I will let it more clear in the thread.
I can convert the other two ones (Extreme and Invisible), specially Invisible would be fine to less experienced users.

Dan_Jacques said:
I took the Light debloat from Tomatot and converted to Debloat (Terminal Emulator) module syntax. I will let it more clear in the thread.
I can convert the other two ones (Extreme and Invisible), specially Invisible would be fine to less experienced users.
Click to expand...
Click to collapse
Yes, that will be cool.. also if we want edit some of script, for example we don't want debloat one app ,is it possible ? Thanks

marko94 said:
Yes, that will be cool.. also if we want edit some of script, for example we don't want debloat one app ,is it possible ? Thanks
Click to expand...
Click to collapse
Yes, just follow the syntax do add another system app to debloat:
Appname^=/system/path/to/appfolder
If you don't want to debloat some app, just erase the entry with the app that you don't want to remove.
You can find the system apps folder browsing /system/app and /system/priv-app. After every change to import-debloat.txt you have to run debloat and import again (to create the dummy empty folders.)
Edit it in Notepad++ to avoid format issues (at PC) or Quickedit (at cell phone).

Light it's the best choice.
Invisible it's to low and Extreme could be too hard on cleaning up. But it's up to you, of course.:good:

Dev any update for OB Q oos ? Thanks

Updated to Android 10 and doesnt appear to be working. Any debloat solutions for android 10 around?

Question A Draconian legitimized redmi Spyware - com.miui.securitycenter & how to throw it out without boot looping

com.miui.securitycenter
This thing along with 3-4 other security components , pretends to securize
But it does just the opposite. It's a legitimized spyware from Xiaomi in every MI UI ROM .
So I opened up the APK components - services broadcast receivers etc.
Here is what I am find ( see more in screenshot )
-
Code:
AdsProcessPriorityService
com.facebook.ads.internal.ipc.AdsProcess
PriorityService
AdsMessengerService
com.facebook.ads.internal.ipc.AdsMessen
gerService
On disabling these specific components - it will not let me change them my modifications are reset to their default
- Being rooted -I do a magisk hide on all non essential components. Here too certain components of Xiaomi including this one are forcibly unhidden from magisk
-try and disable this using pm disable and that will not work
-tried to use a third party tool To fine grain it's permissions and remove them.
Here I get a warning
Code:
"This is a system application, change
A
settings may cause serious problems.
The Shared user ID for this application is
android.uid.system, and applications with
the same Shared user ID share most of the
permissions.
"
I am opening up this thread so we can collaborate and think of how to MOD this app possibly or any other solutions where all these so called security components of Xiaomi can be thrown out without boot looping.
One approach would be model security component is loaded after booting and original one is thrown out through a magisk module.
Can someone please give Me an approach how to go about doing this

Thanks for sharing this information.
This is annoying and I would never have noticed since I regularly use the cleaning tool (it is my first time using a Xiaomi phone). I just checked the Security Center's data usage and it's been consuming a little bit of my mobile data and WiFi. It's only now I know where's that supposedly going to

What about removing authorization for the app?

What ROM is it on? I'm on the EU and there is nothing called this in the apps, even system apps. Closest app below as attached.

MIUI 11.0.3 Android version 9

xNAPx said:
What about removing authorization for the app?
Click to expand...
Click to collapse
Yeah there's an option to revoke Authorization but that is just window dressing. It is switched off and whether you switch it on or off it will behave exactly the same way it has absolutely no impact I I try to disable individual service components and those to remain as they are

did you try magisk debloater module? Bootloop? I am interested

xNAPx said:
did you try magisk debloater module? Bootloop? I am interested
Click to expand...
Click to collapse
xNAPx said:
did you try magisk debloater module? Bootloop? I am interested
Click to expand...
Click to collapse
you mean this right here nah thx I will give it a shot. My biggest concern is if there is some kind of APK checking going on for the system to boot then it will get stuck in bootloop and I had to restore /system once again -though the terminal apps says that it creates a dummy file

let me know because I have it on my phone and looking for newer ways to debloat my phone, I might give it a shot tomorrow as I plan to reflash my firmware from scratch with the latest fastboot global stable, the thing is we need to understand what dependencies has this app and what triggers them

By the way I already a jar debloater file that brought an applet which will let you enable disable install uninstall. Even after I disable a lot of bloatware or uninstall it - un-installing in redmi isn't permanent , that crap is still out there - dunno where its stored. And you can always reinstall after you have uninstalled. So that uninstall is just a lollipop. Hopefully magisk mod will trick it.

did you try the magisk module?

Nandroided /system and ran the debloat --> boot looped.
restored /system and I am still in boot loop
I had 2 Nandrois of system still got stuck . Finally got it to boot after restoring /vendor from an old backup.
Dunno why /vendor was affected at all.

sieger007 said:
Nandroided /system and ran the debloat --> boot looped.
restored /system and I am still in boot loop
I had 2 Nandrois of system still got stuck . Finally got it to boot after restoring /vendor from an old backup.
Dunno why /vendor was affected at all.
Click to expand...
Click to collapse
BTW boot loop was AFTER that Redmi logo @ Powered by android . I moved a week ago from Havoc to MIUI due to some limitations in the former. Even then a simple full Nandroid restore would''nt work & it got stuck the same spot (@ Powered by android .)

what d'e do now?

We should understand what dependencies this app has, because for sure once we delete it something is looking for it. What did you debloat safely so far?

Hey fellas ...'y dope on this?

Did you find the dependencies? I don't think there are alternatives otherwise. If it is a spy software xiaomi made this by purpose

xNAPx said:
Did you find the dependencies? I don't think there are alternatives otherwise. If it is a spy software xiaomi made this by purpose
Click to expand...
Click to collapse
ty . looking for dependencies ... yes obvious analysis. got any code or something hand that I can test out or work with to develop something ?.

Do you mean the package com.miui.analytics?
Did you try to debloat both? As well as MIUI daemon?
I don't have any code I'm afraid and I would know anyway I'm not a developer

xNAPx said:
Do you mean the package com.miui.analytics?
Did you try to debloat both? As well as MIUI daemon?
I don't have any code I'm afraid and I would know anyway I'm not a developer
Click to expand...
Click to collapse
Dad is no issue with De bloating analytics. Problem is security center