yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A21s Guides, News, & Discussion] Scia0:
If this works id pay you if i had money
[Samsung Galaxy A21s Guides, News, & Discussion] evan.gibson.66@gmail.com:
It works ive done this personally
[Samsung Galaxy A21s Guides, News, & Discussion] hamada2001:
Does it work on Android 12 and with u8 protection
[Samsung Galaxy A21s Guides, News, & Discussion] localdemoda:
Hello everyone.

I have read all the messages from the first to the last post from root to a21s.

Currently I just have to follow the steps in the first message without using modified magisk to be able to root?

Forgive my English I am Spanish and I use google translate.
[Samsung Galaxy A21s Guides, News, & Discussion] Scia0:
what android version are you on
[Samsung Galaxy A21s Guides, News, & Discussion] localdemoda:
I have android 12 but I can install android 11, which one is better for root?
[Samsung Galaxy A21s Guides, News, & Discussion] atlaspsp3:
ies thiss is best guide to root a21s im downgroaded to android11 (U8) .dont forget oem lock/bootloader unlock mode.
[Sony Xperia 1 III] sal82:
i just got the phone on monday. what's with the random reboots when i wake it up? when the battery is low, it doesn't reboot at all. only when it's in charge or when it's at a high battery percentage.
[Sony Xperia 1 III] tommyvca:
Exactly same issue with my phone. I have already got a new one but still reboot. Hope sony see this.
[Sony Xperia 1 III] Maazellat:
Write all problems to Sony. They will make an update about this maybe.
[Sony Xperia 1 III] sal82:
i posted on the sony website. hopefully, someone replies with some help.

it's an annoying issue. my phone hasn't rebooted at all today. i keep testing it out, and it's behaving.
[Sony Xperia 1 III] misquia:
I have the same issue. I recently returned mine and waiting for a new one, fingers crossed that I don't get the same problem with the new one.
[ZTE Axon 30 Ultra] briodroid:
Hi !

Have you tested the beta android 12 on our axon ?

Be carefull it's for chinese version only.

Download Android 12

ztedevices.com
[ZTE Axon 30 Ultra] Jhomhf:
Eu já ia baixar, o meu é versão global

Translation:
[ZTE Axon 30 Ultra] svano:
hello someone has installed android 12 although for china?
[ZTE Axon 30 Ultra] Jhomhf:
O rapaz informado para tomar cuidado porque é somente para a versão chinesa e no site informa que tem bugs por exemplos que não funciona a impressão digital.

Translation:
[ZTE Axon 30 Ultra] svano:
Thanks a lot, and a site where they explain how to install an update manually, someone knows
[ZTE Axon 30 Ultra] Jhomhf:
No próprio site da ZTE eles te ensinam e te fornecem o dowloader do andróid 12 e outros firmaware que é direcionado para seu dispositivo ZTE.

Translation:
[ZTE Axon 30 Ultra] svano:
View attachment 5525599
[ZTE Axon 30 Ultra] svano:
Esto es lo que explica el sitio de zte para instalar Android 12, no puedo hacer el paso 4 "sdcard" no entiendo
[ZTE Axon 30 Ultra] Jhomhf:
você consegue fazer isso com um cabo OTG e um pendrive.

Translation:
[ZTE Axon 30 Ultra] svano:
Ok thank you
[ZTE Axon 30 Ultra] Pascal536:
SD card upgrade package ZTE Axon 30 Ultra 5G SD Card Upgrade Package (430331B2276MyOS11.5.22_A2022P) Release Notes | Date: 27-05-2022 Size: 3.9 GB​

This is the chinese rom

Is it possible to convert Global Axon 30 Ultra to chinese one ? (A2022PG to A2022P)

Is there a way to use ADB Sideload via ZTE boot rom ?

Pascal
[ZTE Axon 30 Ultra] Pascal536:
Hi,

Some capture screen of Camera apk from Axon 30 Ultra Android 12
[ZTE Axon 30 Ultra] Pascal536:
Last CN MyOS12.0.36_A2022P update for Axon 30 ultra, after python extract contain this :

mcfg_sw/generic/APAC/DCM/Commercial/mcfg_sw.mbn

mcfg_sw/generic/APAC/KDDI/Commercial/mcfg_sw.mbn

mcfg_sw/generic/APAC/SBM/Commercial/mcfg_sw.mbn

mcfg_sw/generic/China/CMCC/Commercial/Volte_OpenMkt/mcfg_sw.mbn

mcfg_sw/generic/China/CMCC/Lab/AGNSS_LocTech/mcfg_sw.mbn

mcfg_sw/generic/China/CMCC/Lab/Conf_VoLTE/mcfg_sw.mbn

mcfg_sw/generic/China/CMCC/Lab/EPS_Only/mcfg_sw.mbn

mcfg_sw/generic/China/CMCC/Lab/LPP_LocTech/mcfg_sw.mbn

mcfg_sw/generic/China/CMCC/Lab/Nsiot_VoLTE/mcfg_sw.mbn

mcfg_sw/generic/China/CMCC/Lab/RRLP_LocTech/mcfg_sw.mbn

mcfg_sw/generic/China/CMCC/Lab/TGL_Comb_Attach/mcfg_sw.mbn

mcfg_sw/generic/China/CMCC/Lab/W_IRAT_Comb_Attach/mcfg_sw.mbn

mcfg_sw/generic/China/CT/Commercial/hVoLTE_OpenMkt/mcfg_sw.mbn

mcfg_sw/generic/China/CT/Lab/CTA/mcfg_sw.mbn

mcfg_sw/generic/China/CT/Lab/RUIM/mcfg_sw.mbn

mcfg_sw/generic/China/CT/Lab/TEST/mcfg_sw.mbn

mcfg_sw/generic/China/CT/Lab/TEST_EPS_ONLY/mcfg_sw.mbn

mcfg_sw/generic/China/CT/Lab/TEST_NO_APN/mcfg_sw.mbn

mcfg_sw/generic/China/CT/Lab/VoLTE_Conf/mcfg_sw.mbn

mcfg_sw/generic/China/CU/Commercial/VoLTE/mcfg_sw.mbn

mcfg_sw/generic/China/CU/Lab/Test/mcfg_sw.mbn

mcfg_sw/generic/EU/DT/Commercial/Austria/mcfg_sw.mbn

mcfg_sw/generic/EU/DT/VoLTE/Commercial/mcfg_sw.mbn

mcfg_sw/generic/EU/Elisa/Commercial/FI/mcfg_sw.mbn

mcfg_sw/generic/EU/H3G/Commercial/Austria/mcfg_sw.mbn

mcfg_sw/generic/EU/H3G/Commercial/SE/mcfg_sw.mbn

mcfg_sw/generic/EU/H3G/Commercial/UK/mcfg_sw.mbn

mcfg_sw/generic/EU/Orange/Commercial/Spain/mcfg_sw.mbn

mcfg_sw/generic/EU/Tele2/Commercial/Sweden/mcfg_sw.mbn

mcfg_sw/generic/EU/Telefonica/Commercial/DE/mcfg_sw.mbn

mcfg_sw/generic/EU/Telefonica/Commercial/Spain/mcfg_sw.mbn

mcfg_sw/generic/EU/Telenor/Commercial/Hungary/mcfg_sw.mbn

mcfg_sw/generic/EU/Telenor/Commercial/Norway/mcfg_sw.mbn

mcfg_sw/generic/EU/Telia/Commercial/Norway/mcfg_sw.mbn

mcfg_sw/generic/EU/Telia/Commercial/Sweden/mcfg_sw.mbn

mcfg_sw/generic/EU/Vodafone/VoLTE/Germany/mcfg_sw.mbn

mcfg_sw/generic/EU/Vodafone/VoLTE/UK/mcfg_sw.mbn

mcfg_sw/generic/LATAM/AMX/MX-Commercial/mcfg_sw.mbn

mcfg_sw/generic/LATAM/Movistar/Commercial/mcfg_sw.mbn

mcfg_sw/generic/NA/ATT/VoLTE/mcfg_sw.mbn

mcfg_sw/generic/NA/TMO/Commercial/mcfg_sw.mbn

mcfg_sw/generic/Russia/Beeline/Gen_3GPP/mcfg_sw.mbn

mcfg_sw/generic/Russia/MTS/RU-Commercial/mcfg_sw.mbn

mcfg_sw/generic/Russia/MegaFon/RU-Commercial/mcfg_sw.mbn

mcfg_sw/generic/common/Austria_A1/Commercial/mcfg_sw.mbn

mcfg_sw/generic/common/KPN/Commercial/mcfg_sw.mbn

mcfg_sw/generic/common/O2_Czech/Commercial/mcfg_sw.mbn

mcfg_sw/generic/common/Plus/Commercial/mcfg_sw.mbn

mcfg_sw/generic/common/RDS/Commercial/mcfg_sw.mbn

mcfg_sw/generic/common/ROW/Commercial/mcfg_sw.mbn

mcfg_sw/generic/common/Tele2/Commercial/mcfg_sw.mbn

mcfg_sw/generic/common/WindTre/Commercial/mcfg_sw.mbn

Axon 30 ultra Android 12 Global and EEA might be not far.
[ZTE Axon 30 Ultra] AJ732101:
After the official OTA Android 12 upgrade all four camera modules on the back work fine in GCam (before the two Samsung ISOCELL GW3 sensors did not work, the 0.5x and the 1.2x)
[ZTE Axon 30 Ultra] xphyle1971:
Which Gcam version are you using please? Could you please provide a link? Thanks!
[Touch Diamond, MDA Compact IV General] likinho:
I have a problem in showing all the "whole day events" on the smae day at the front page of TF3D, if there are two or more "whole day events" on the same day, say "A's birthday" and "Christmas Eve". is there any tweak or manila editing can help? thanks very much
[Touch Diamond, MDA Compact IV General] likinho:
can anyone help on this??

my question is that if on any one day, say 25th of december, you have two (or more) whole day events, like "Christmas day" and "Someone's Birthday", my experience is that my dimaond can show only one of them (say "Christmas day"), but not all, on the home page of TF3D, and then show the immediate coming meeting under this "Christmas day". is anyone here having the same experiece? do anyone know how to fix it to show all the whole day events on the home page?

Thanks a lot!
[Xiaomi Mi 10 Lite  ROMs, Kernels, Recoveries, & Ot] T3cheN:
​

​

LegionOS for Xiaomi Mi 10 Lite 5G [monet]​

​

* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.

What is this?​

LegionOS is an AOSP based ROM​

Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device​

Based on Android 11​

​

Whats working?​

Wi-Fi​

RIL​

Mobile data​

GPS​

Camera​

Flashlight​

Camcorder​

Bluetooth​

Fingerprint reader​

Lights​

Sound/vibration​

​

CLEAN FLASH :​

Download the latest build and GApps (optional)​

Reboot to recovery​

Wipe Cache, and Data (you might need to format data partition!).​

Flash the latest build and GApps(on non Gapps build if needed)​

Reboot​

​

DIRTY FLASH :​

Download the latest build (gapps or non Gapps)​

Reboot to recovery​

Flash the latest build​

Wipe Cache​

Reboot​

​

Known issues​

You tell me​

​

Stay tuned​

​

DOWNLOAD LINK

​

​

Device Support Group

​

​

Android OS version: 11 [R]​

Build author/Device Maintainer: TecheN​

Rom Source code: https://github.com/Project-LegionOS​

Kernel Source: https://github.com/xiaomi-sm7250/android_kernel_xiaomi_sm7250​

ROM Developer: RajKale​

​
[LG Velvet Guides, News, & Discussion] BladeRunner:
MY T-Mobile LG Velvet just got the August security update which allegedly includes 5G enhancements including SA 5G.
[Samsung Galaxy S21 Ultra] shobuddy:
Used to be I would get an option to remove location information from a photo before sharing. I recently reset the camera settings and no longer have this option for new photos I've taken since. The setting to tag photos with location is on so what am I missing?
[Samsung Galaxy S21 Ultra] shobuddy:
Camera was set to take pictures in HEIF format. I disabled that and can see the option to remove location when sharing.
[Samsung Galaxy S21 Ultra] vladmir:
Don't show that option for me in Android 12 beta 1. Can remember to saw that option on Google photos too but also disappear!
[Samsung Galaxy S21 Ultra] UNIK97122:
in the gallery type in details then modify and delete the location manually
[Samsung Galaxy S21 Ultra] SOGKush420:
Doesnt matter if you remove the tag or not.. its still captured in the pictures metadata so there is no point of doing it
[Magisk] DiracDeBroglie:
Hi,

I installed Magisk.zip v23 into the system through TWRP, and Magisk.apk v23, on my Samsung Galaxy J5 (2016) Nougat 7.1.1

The phone is clearly rooted as some of the tested apps request root, which I gave.

I noticed that something is not quite alright when I open the Magisk app (see attached image)

In the image, the second part is about the App and shows the latest verion 23.0, so that looks OK.

The first part shows the value of the settings A/B, SAR, Ramdisk and the Installed version (=N/A) .

The setting Installed should show the Magisk version 23.0 instead of N/A, and that is clearly wrong.

Also, clicking the settings cogwheel (top/right) should show a long list of settings, including MagiskHide.

However, that is not the case and the options are just a few.

There is clearly something wrong with the installation of Magish.apk, but what?

So, how can that be fixed?

How do I get back all the missing settings, including MagiskHide.

Help would be very much appreciated.

thanks

View attachment 5416439
[Magisk] toolhas4degrees:
Search for kdragon safety net fix
[Magisk] Revolver:
John Wu, the main contributor to Magisk, now works for Google in their Android Platform Security department. So now his job is to prevent MagiskHide to work, and now it seems he removed it from Magisk.
[Magisk] Didgeridoohan:
@DiracDeBroglie since your Magisk app doesn't recognise that you have Magisk installed, none of the options you're mentioning will be available.

First thing I would check is if the Magisk app is installed to the internal storage. If it isn't, things won't work correctly.

https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_not_installed
[Magisk] Didgeridoohan:
But that will have no effect on Magisk v23, that the OP is talking about. And, if you take a quick peek on GitHub and the commits over the past month (or follow the conversations in the general Magisk thread) you'll see that MagiskHide still exists, but in the new form of the deny list. Exactly how that'll work will have to wait until John releases the next Canary.
[Magisk] Didgeridoohan:
OP has a device from 2016. I very much doubt that it uses hardware backed key attestation... Besides, that has nothing to do with the described issue.
[Magisk] toolhas4degrees:
Actually it does be the new zip I told him to get ere3nables magisk hide and repo....
[Magisk] Didgeridoohan:
The latest release of USNF (currently v2.1.1) adds back a few of the props that MagiskHide currently changes, apart from disabling hardwarebacked key attestation. That is not relevant for the OP, since Magisk v23 still has all of that. The issue here is something else...

And it sounds like you're talking about the unofficial Alpha Magisk releases rather than the SafetyNet Fix, since the latter doesn't include anything that has to do with the soon to be removed modules repo.
[Magisk] DiracDeBroglie:
Thanks for the reply.

I unstalled Magisk with uninstall.zip. That worked fine, rootchecker said that root was gone and banking and ID apps were working again.

Then I installed Magisk.zip again through TWRP, and that went well too.

Following reboot there was some sort of little Magisk app in the app folder (see first image). I double clicked it and it installed the full version of Magisk app (13MB), also that went well.

But the problem persists as before with Magisk app, that is: Installed=N/A and the important Settings, like Magiskhide and the Modules part, are missing, which means btw that Universal SafetyNet Fix cannot be installed anyhow.

My device is from 2016 (design 2015), so I have very strong doubts my device supports any hardware-backed attestation.

The Magisk core elements work flawlessly, Root Checker shows root, root apps like VPN hotspot work fine, and the banking and ID apps .... well, they detected root and refuse to continue working. So root is clearly OK.

Somehow the Magisk app in the user/data partition does not/cannot communicate with the Magisk core elements (sitting in the boot ramdisk I presume).

So, is there any app, tool or software to analyze, study or have a closer look at the communication between the app and the core elements?

If this doesn't work out with v23, then I won't have much of a choice but to install lower versions, v22, v21, ... until I come across a version that works, but that is really my last resort as my preference is v23.

Any suggestions ....

View attachment 5417545View attachment 5417547
[Magisk] Didgeridoohan:
Did you check if the app has been installed to external/adoptable storage? That would cause this exact behaviour...

Also, did you previously have Magisk installed with the app repackaged with a random name? If so, that app might still be present and could be the source of your problem. If so, you can uninstall that app and try again (but you might also have to uninstall and reinstall the regular Magisk app as well).

https://www.didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_apps
[Magisk] Didgeridoohan:
@toolhas4degrees I'm not sure what you mean by that screenshot, but it just shows exactly the same thing I was talking about in the post you quoted.
[Magisk] DiracDeBroglie:
No, at the last install there was not any external SD card present.

No, never installed Magisk under any another name, neither did I try to hide it or so.

However, ... I did install the app Magisk.apk first a few days ago at first contact with Magisk, and then later I installed Magisk.zip through TWRP while there was an external SD present. So, .... maybe there is some remnant code laying around in the system.

I could uninstall.zip Magisk again and then look for remnants in the system and delete those. If there are any remnant left, those should probably have "magisk" in their name. Do you have any idea where to look for Magisk remnants after uninstallation?

Remember the device is a Samsung Galaxy J5 (2016) and I am not all too sure if Odin is really the most handy tool to look for code remnants. I got ADB and Fastboot installed that I used before for testing my Asus tablets. Also Terminal in TWRP I can use. If I only knew what exactly and where to look for the stuff ....
[Magisk] DiracDeBroglie:
Here is an update.

As my device is still rooted by Magisk I checked out the filesystem starting from root with Solid Explorer File Manager (SE).

I found folders and files from Magisk in /root/data/adb/magisk (folder), /root/data/adb/modules (empty folder) and the file /root/data/adb/magisk.db

I uninstalled Magisk by installing uninstall.zip (from Magisk.zip) through TWRP.

And as SE needs root, I installed SuperSU-v2.82-SR5.zip through TWRP, which then worked fine.

With SE I removed magisk.db and any magisk folder at /root/data/adb/

Next thing I did was to remove, uninstall and unroot SuperSU through its own settings.

But after having clean-installed Magisk.zip again from TWRP, having installed the Magisk app using the Magisk preinstaller app in the apps folder and rebooting the device a few times, the problem hasn't gone!

And so the Magisk app pane still shows Installed = N/A, and MagiskHide, Modules and the other options are also still missing from Settings.

Any suggestions for a next move would be welcome.

thanks
[Magisk] Didgeridoohan:
What does this mean? What's a preinstaller?
[Magisk] DiracDeBroglie:
If one performs a clean installation of Magisk.zip -- so there is no Magisk on the phone anywhere -- through TWRP, not only the core elements are installed, but also in the /data part some little Magisk app is installed that shows up in the apps folder, which I call a (pre)installer. See first image #9. Double clicking that will install the full Magisk app in the user or /data part.

So all looks ok during the installation, and rooting definitely works, but that annoying problem just persists.

I would be glad to hear any suggestions...
[Magisk] Didgeridoohan:
Ah... Now I get it. It sounded like you were using some custom unofficial stuff, and that would definitely have been a possible source of issues.

I have no suggestions, but you haven't posted any Magisk log, have you? Might be a good idea, to see if anything shows up in there. First it would be good if you could install the Canary release though, since it has more verbose logging.
[Magisk] DiracDeBroglie:
I just had a look for those log files but couldn't find any. Any idea where to look for? In /root/data/adb/ there are no log files.
[Magisk] Didgeridoohan:
The Magisk log is in /cache.
[Magisk] DiracDeBroglie:
So this is what I have in the log.

01-05 19:43:01.276 262 262 I : Magisk 23.0(23000) daemon started

01-05 19:43:01.281 262 262 I : * Device API level: 25

01-05 19:43:01.296 262 264 I : ** post-fs-data mode running

01-05 19:43:01.297 262 264 I : * Mounting mirrors

01-05 19:43:01.298 262 264 I : mount: /sbin/.magisk/mirror/system

01-05 19:43:01.298 262 264 I : mount: /sbin/.magisk/mirror/data

01-05 19:43:01.299 262 264 I : link: /sbin/.magisk/mirror/cache

01-05 19:43:01.299 262 264 I : link: /sbin/.magisk/mirror/persist

01-05 19:43:01.299 262 264 I : link: /sbin/.magisk/mirror/vendor

01-05 19:43:01.299 262 264 I : * Initializing Magisk environment

01-05 19:43:02.901 262 264 I : * Running post-fs-data.d scripts

01-05 19:43:02.906 262 264 I : * Running module post-fs-data scripts

01-05 19:43:02.906 262 264 I : * Loading modules

01-05 19:43:07.207 262 538 I : ** late_start service mode running

01-05 20:43:07.209 262 538 I : * Running service.d scripts

01-05 20:43:07.227 262 538 I : * Running module service scripts

09-25 19:09:50.969 262 2470 I : ** boot_complete triggered

09-25 19:31:29.395 262 12576 W : su: request rejected (10166)

09-25 19:31:41.551 262 12618 W : su: request rejected (10166)

09-25 19:31:53.716 262 12667 W : su: request rejected (10166)

09-25 19:32:05.877 262 12707 W : su: request rejected (10166)
[Magisk] nightwolf410:
Have you tried patching boot.img and flashing it? If not, can you try? If you are not using custom rom or you don't have rom zip file, check how to extract boot.img then achieve it first.

And can you try canary build as well, change from settings/update channel. If can't see canary, set to custom and use this:

https://github.com/topjohnwu/magisk-files/blob/master/canary.json

After changing it try to install again or just flash the zip it downloads, 23001 and lets see what happens.
[Magisk] DiracDeBroglie:
After introducing the link in the custom update channel, nothing happens. Magisk app did not update at all, even after rebooting a few times.

So I then finally installed the app-debug.apk from topjohnwul his github site myself and that updated the Magisk app. While before it was Latest: 23 (23000) & Installed: 23 (23000) (see image post #1), it now shows Latest: N/A & Installed: f822ca5b(23001). Note that the install button on the right side in the App pane is now gone.

But the original problem remains unchanged. In the Magisk pane (see image post #1), there is still Installed N/A.

Could it be that I made a mistake in installing app-debug.apk somehow?

Any suggestions for next move?
[Magisk] nightwolf410:
Then last I can suggest is patching boot.img. Check how to extract it and patch with magisk then flast boot.img in twrp
[Magisk] bencollinz:
THANK YOU!! I spent a week trying to figure this garbage out. Updated my phone to A11, update magisk/manager to v23 and just could not get the hide option/menu to appear. Rolled back to v7 and voila. What a nightmare.
[Magisk] CitizenSmith:
I've got the same problem. I too had sucessfully rooted phone checked the root access via root checker pro it confirmed when it wasn't and then when it was when enabling and disabling Magisk hide so I know I had rooted then tested with apps and worked that is until I updated Magisk to v23.0 no I have no access to half the settings like you it only visable up to Download Path rest of setting are gone.
[Magisk] CitizenSmith:
Just to confirm I too have same issue I'm using android 8 on ALEXNDR custom rom all was working fine untill I install Magisk 23.0 now I have no settings beyond "Download Path". I still have safetynet success though and i had previously enable Magisk Hide but don't know it's condition at present as unable to view it's status.

I just updated TWRP and no-verity-opt-encrypt-6.1 it was on 3.1 via twrp but that has made no differance.

Update:

Reinstalled magisk 22.1 now have all setting back but failing safetynet but strangely Santander banking app working!.

really want to stop using magisk now. I found this (ih8sn) says it is best used instead of magisk but no help with installation and no instructions on how to setup what a shame. realy don't like or trust google and now this developer working for them I really don't want magisk on my phone as it now makes my phone feel unclean! :/ again what a shame so many choosing the dark side!.
[Magisk] msssm:
I thought, Magisk 24 was the first version dropping MagiskHide.

Anyway, what is the next solution to get Magisk hidden for some apps? Even the Magisk developer said, that it's better done by module developers than by himself, after it was always a lot of work to maintain and also (maybe) because of his new job at Google.

Then the module repository is also dropped, so where is some central place to get Magisk modules now? Is there already a module doing the hide?

From what I at read https://www.androidpolice.com/a-new-method-for-hiding-root-in-magisk-may-soon-emerge/ there will be some new solution called "Shamiko", but not ready yet.

Is there some central thread here at xda for the Magisk Hide topic? So far I'm watching this here.

I know the opinions that actually the app developers should be pushed to remove and root detection and stuff which is senseless as long as there is a hide technique. BUT, most of them are banking applications and they won't remove it for the <1% of users with rooted devices. So we still need some MagiskHide.
[Magisk] mingkee:
Your Magisk is NOT installed in boot.

Try patching method