yashsingh1/xdaforums huggingface dataset:
[Magisk] Blauhasenpopo:
So there i will hang with this Prob., too :(

I need Xposed cause of special needs, is there a way to have xposed and the rest of the Stuff above?
[Magisk] djibril13:
Is there any way to make secure settings work with magisk v8 ?
[Magisk] AbiDez:
When you use phh superuser, I think you can't install SuperSu, SuperSu will patch the boot... But you have patched boot with Magisk. Why you need suhide? Either you use Suhide + Root Switch (many says that is probably not work) or use magisk without XPosed that will work. I'm xposed user, too. But the most things I found a solution like display always on on pogo...

CarHDRom V.24.7 by Carotix S6e
[Magisk] htb2050:
Do the modules like adblock busybox and emojis one work fine on touch wiz
[Magisk] edyny1:
I'm trying to figure it out, the way is looking is that to make it work with xposed, suhide needs to be flashed and phhs superuser r259 not compatible with suhide (suhide hides xposed framework)

Look at this screenshot when i try to install suhide
[Magisk] nkk71:
Here you go, I haven't tested the module myself, but the binary (v0.2) should work on Android N and previous versions.

EDIT: A huge thanks to [MENTION=1162986]Captain_Throwback[/MENTION], who took the trouble of setting up an android-7.0 build environment and allowing me to use it, without his (as always) valuable help, I could have not done it so quickly.

Many thanks Cap!!
[Magisk] zapahacks:
I have the same problem as you guys, I currently managed to get root working with Magisk + Phh's Super User, but I can't run xposed. I can install it, but if it is enabled Safetynet won´t pass.

I flashed suhide 0.55 but I doesn't make any difference. I even tried to flash the official xposed and try to hide it with an option in the root switch app (it disables oficial xposed, it doesn´t 'hide' it, so the modules don´t work).

If you guys find any way to solve this please share with me/all :)

I'll do the same :)

---------- Post added at 10:27 AM ---------- Previous post was at 10:24 AM ----------

May I ask what is this fix for? :good:

EDIT: nevermind, I can see is something related to bootloader
[Magisk] loserskater:
Works on a 6P running 7.1.1. Thank you!

Now I just need to figure out why I'm still not passing safety net.

EDIT: had to set ro.boot.flash.locked to 1. Now passing!

EDIT2: the command to use is

xsetprop ro.boot.flash.locked 1

And can be added to /magisk/xsetprop/post-fs-data.sh

Maybe [MENTION=2605798]nkk71[/MENTION] or [MENTION=1162986]Captain_Throwback[/MENTION] can update the module with that..
[Magisk] edyny1:
We just gotta flash it and thats all? Or we also gotta activate ot within magiskmanager?
[Magisk] KyeWalker:
Right guys, instead of all this hassle of getting Xposed to work, can't we port modules from Xposed to Magisk?? If so or any ideas, show me the way :cool:
[Magisk] loserskater:
I think you're misunderstanding what Xposed does and what Magisk does. Xposed allows you to hook into apps during runtime to run your own code. Magisk allows you to alter the system files without actually touching the system. The only way you could port an Xposed module to Magisk is if you actually modified the apk with the code you want to run (more difficult than it sounds) and then use that apk to replace the one in system.
[Magisk] jcrompton:
Thank you guys ..... I wish I could absorb all this stuff and be of more help.

I'm not sure if I did the set to.boot.flash.locked correctly,, but I still fail safetynet
[Magisk] loserskater:
In terminal use xsetprop instead of set.
[Magisk] waylo:
I had this problem but was able to get it to work by using flashfire instead of twrp. I thought it had to do with my encrypted data partition but wasn't sure entirely.
[Magisk] jcrompton:
Hey thanks again!

That worked with the command, but still fail safetynet ....

Maybe it's the kernel I'm using .... It's still reporting permissive. I thought I had restored the stock boot when I did a full unroot with the SuperSu app
[Magisk] zapahacks:
I am trying to follow your steps but I don't understand something

In 1., I did the first and the second command, but when doing the third (adb sideload SuperSU.zip) it will through an error. Do I need a SuperSU file? Is this step the first one of all or it need to be done after SuperSu is installed?

In 5., after flashing Magisk, do I need to overwrite "autogenerated custom_ramdisk_patch.sh"? I don´t understand what you meant with the text inside ( )

Thanks!
[Magisk] Renate:
Thank you for your support.

I had to jump through hoops to get it by the bot.

https://github.com/topjohnwu/Magisk/issues/5098
[Magisk] MartK87:
Thanks for getting back. I did use Lineage and I like Lineage in the way its quite degoogled. The only issue I had with it though was the fact I wasn't able to find the mixer paths xml file to increase mic gain. Otherwise I owuld have used it. I noticed a guideo n here for all LOS up until 17 but not 18 for increasing mic gain. Do you or anyone else here know how I would increase mic gain using LOS 18 on Galaxy S5? If yes then I will just do it that way rather than messing around with Stock ROM. Thanks :)
[Magisk] MartK87:
I want to do the same as what you did but at the same time, be able to apply the patch for mic gain. I am aware of patches here for this but it only goes up to LOS17 unfortunately :(
[Magisk] pndwal:
I see you made comment in GitHub issue... 👍

Why don't you try the test build???

Mic gain for LOS 18.1:

https://xdaforums.com/t/rom-officia...-samsung-galaxy-s5-klte.4267517/post-84960197

Other solutions (4th post):

https://xdaforums.com/t/rom-officia...-samsung-galaxy-s5-klte.4267517/post-84903071 PW
[Magisk] MartK87:
Thanks mate.

Sorry yes you're right I will try the test build. Half an hour ago I flashed 22.1 ZIP file on TWRP.

The manager I installed is 8.07.

How do i totally uninstall all of Magisk so I can run the test build? Is it as easy as just uinstalling the app through application manager?

I don't know where I would be without this forum and to the people on it with the knowledge they have.. its just amazing.

Thanks for your help :D

Mart.
[Magisk] zgfg:
In the Magisk app you have BIG Uninstall Magisk button - you couldn't miss (?)

There is also a link to Github with documentation, instructions, Wiki

I don't understand why people don't read (but ask questions clearly described there) - e.g., Magisk can be also uninstalled by flashing uninstall.zip from TWRP (where TWRP is available)

Magisk app is just a manager or front end. Installing or uninstalling Magisk app will only install/uninstall that app, but not the Magisk itself
[Magisk] MartK87:
Well, in fairness to me... my magisk doesn't have the option of uininstall and I have read topics which say to press that option but I don't get it. Don't be so quick to jump on your high horse and be sarcastic before finding out details.
[Magisk] zgfg:
Oops, ok - you have that problem with improper installation

Sorry, I don't recall details with your phone and I'm not familiar with Samsung (if so).

If TWRP is available, download the Magisk apk (from Github or the same you used when installing, if it was Canary, Alpha), rename to uninstall.zip and flash through TWRP

Otherwise, you could flash your original boot.img, or if not available for your Samsung then dirty flash the ROM (it's not the same as uninstalling Magisk but you didn't have modules, etc)

Since your app declares that Magisk is not installed, maybe it would be enough to just uninstall the app but I would rather go through the steps as above (to make sure there are no remnants of even unsuccessful Magisk installation in your boot img or so)
[Magisk] MartK87:
@zgfg Apologies for what I said back up there. Not having the best of days today.

I will give all those suggestions a go appreciate yours and everyones help :)
[Magisk] MartK87:
Just another thing to also add... with regard to boot.img... when I try to flash the boot.img through magisk I get an error. I can flash the Stock ROM .tar file successfully in magisk but not just the boot.img. Is this normal? Is flashing the .tar file an ok thing to do? It rsults in a file 3.42GB in size. Thanks :) Mart.
[Magisk] pndwal:
For that test build, I don't think you need to remove Magisk mask at all, so can ignore in-app uninstall even if you do see it.

It may only be an app issue / regression it seems (sepolicy causing issue on armeabi-v7a devices) as has been mentioned!... You should only need to uninstall any Magisk / App you have, then install test app, may need reboot but you should see Magisk installed version instead of N/A IF IT WORKS!... Then you could take direct update to upgrade again...

Either way you should be able to save / send logs requested... I've answered question re logs in issue thread...

If you do need to uninstall all residual Magisk folders / settings / ramdisk changes, you can rename magisk.app (incl. test app?) to uninstall.zip and flash from TWRP... Doubt you need this though... Last resort... PW
[Magisk] zgfg:
Boot images cannot be flashed through Magisk APP (but only through TWRP or Fastboot)

Only Samsung has that specifics with tar hence I don't know about, and whether you could flash the tar through Magisk app. Besides, flashing through Magisk app should be only possible once already rooted, while you say you are not

Or you ment fashing through TWRP (not thrugh the Magisk app)?!
[Magisk] pndwal:
Not sure what you mean "flash in Magisk"... The official instructions include special instructions for Android 9+ Sammy, and these need flashing patched image as complete ROM package in Odin... If standard Fastboot flash doesn't work for Android 6 Sammy and you need Odin flash, you may need to follow those instructions... Read them anyway, they'll likely give you the clues you need...

Sounds like you should probably refresh your mind on whole Installation Instruction page... 😜 PW
[Magisk] MartK87:
Hey, Thanks for getting back. Ok no worries I will get this test app in then and get some logs uploaded very shortly. I will report back on how I go with it.
[Magisk] MartK87:
Hey thanks for getting back. Yes sorry I must clarify. I was able to put my .tar file into magisk on version 23, 22 and version 18. It had an option of 'install' which i pressed and then 'Patch from file' i selected that .TAR file (Which I had earlier copied to storage) then it successfully patched the TAR file making a magisk version of the TAR file. I then transferred that Magisk .TAR file back to the PC (3.42GB in size) then flashed it with ODIN in AP field. In doing that, Magisk Application still showed me same thing with 'Installed N/A' however using 'Root Check' it said I was rooted. Its almost like it half roots the phone maybe?

I am going to give that Magisk Test app a go and report back the logs it generates. Hopefully that will give the developer a clearer picture of the problem.

Thanks guys for the input :)
[Magisk] zgfg:
Patching only prepares the patched boot (tar in your case) that meeds to be flashed through Fastboot (TWRP) or Odin for Samsung

At the end you have the same half or unsuccessful Magisk patch/installation (despite that it said that patching was 'succesfull') as previously (same problem - bug to be tested/fixed)

Follow the @pndwal's instructions for your Samsung
[Magisk] MartK87:
Hey!

Ok I won't bother with the patching part then. The frustration is I had this working for 3 years on the S5 without any of these problems. I am pretty sure I just did a normal Flash of a Magisk ZIP in TWRP and installed a normak Magisk Manager and for 3 years it was fine. Since reflashing the same stock ROM (Telstra Nov 2017) there has been an issue with any version of Magisk I use.

I just wish I had noted down the working one I had before (For 3 years) doh!

Hopefully the dev will resolve this and i'll do everything I can to help with logs etc its just right now I get a message on my logs screen saying "Magisk logs are empty, that's weird" (This is using Magisk Manager 8.07)

Any other Magisk App (Manager) (v21, 22 and 23) gives me limited options on all screens.

Cheers :)
[Magisk] pndwal:
Its here Realme users!

Latest Universal SafetyNet Fixes:

v2.2.1 (Zygisk)​

Changes​

Fixed under-display fingerprint sensor on Realme devices (thanks @osm0sis, @byxiaorun, @Jowat97)

Clarified definition of "basic attestation" in readme

Add check to prevent installation on unsupported Android versions (7.x and older)

v2.1.3 (Riru)​

Changes​

Fixed under-display fingerprint sensor on Realme devices (thanks @osm0sis, @byxiaorun, @Jowat97)

Clarified definition of "basic attestation" in readme

Add check to prevent installation on unsupported Android versions (7.x and older)

👍 PW
[Magisk] pndwal:
@MartK87

Even if you go to LOS 18.1 later (I would), your GitHub issue help now may be invaluable for producing a fix for Magisk for many devices (Samsung and apparently Xiaomi) running stock Android 6 / 7.

Some of these may have no custom alternative... 👍 PW
[Magisk] MartK87:
I am glad to be of help. I want to be able to resolve this for not only me but many others who encounter this issue. Ill do everything I can :D
[Magisk] dcarvil:
See this post. https://xdaforums.com/t/rom-officia...-samsung-galaxy-s5-klte.4267517/post-85649543
[Magisk] MartK87:
Thanks for the link. I have put LOS18 on and root was successful. No matter which file manager i use.. X-Plore, Root Explorer, ES File Explorer I cannot save changes to the edited .XML file after changing the values in to 118. The values won't change. I am also unable to copy the Mixers XML file into the system/etc/vendors folder. Any ideas? I can confirm i am fully rooted and root access was granted to all apps mentioned above.
[Magisk] zgfg:
Check to /vendor/etc/fstab.* (extension is usually aligned with the chipset vendor name or so), open as textual file (I use MiXPlorer as the best [root] explorer) whether your /system or / (SAR = System As Root) is ro=read-only or rw=read/write

If read-only, this is why Magisk provides Systemless mechanism (mounting changes at the boot time).

E.g. AdAway writes to /data/adb/modules/hosts/system/etc/hosts

and Magisk mounts that to /system/etc/hosts on every reboot

That's what Magisk modules usually do (among other things)
[Magisk] dcarvil:
That is normal, as the file system is read-only. The link I gave above points to another post with complete instructions. Follow those instructions.
[Magisk] Lughnasadh:
FYI...

https://twitter.com/i/web/status/1474101935611408389
[Magisk] pndwal:
I gave same solution / link yesterday too! -

🤪 PW
[Magisk] MartK87:
Mixplorer worked nicely thanks for getting back mate :)
[Magisk] MartK87:
All sorted thanks. Ill keep lineage on here for now then when those devs want my help ill happily switch back to Stock ROM to help them out
[Magisk] pndwal:
Switch-back time already! ... Looks like he's added more debugging! 😜 PW
[Magisk] pulpf:
hi i have reinstalled magisk with the keep root method on my oneplus7t.

it is well installed but i am no longer safety net.

what should i do?
[Magisk] replica9000:
Newer versions of Magisk will need a separate module, such as Universal SafetyNet Fix
[Magisk] Smankusors:
Hello everyone, I have an Oppo F5 Youth (CPH1725), that's already have the bootloader unlocked. I followed a guide from bkerler/mtkclient to root my device. But after flashed the patched boot.img, my device bootlooped, it's stuck at Oppo logo, and then resetting itself again. 😭

I have tried the APK linked on that guide, latest stable magisk version, and latest canary version (92546e8a). Flashing the stock boot.img returns it to normal though. Is there anything left I can do?

Here I uploaded a attachment of Magisk install log when patching, in case you need it

Thanks,
[Magisk] pndwal:
I suggest you download latest Canary Magisk and try using official Installation Instruction as guide; use patch image / fastboot flash method to eliminate TWRP issues. Nb. latest Canary contains some recent fixes for MTK.

If this doesn't work (or. if method matches what you tried already), consider opening a proper Magisk issue ticket for you device; I can't find any reported for Oppo F5 or F5 Youth despite many web posts complaining about lack of Magisk support... People need to help Devs if they want support for their devices... PW
[Magisk] Smankusors:
the canary version I mentioned is the latest, for now. I also followed the guide on the official one, didn't work either. (Yeah, it's identical guide)

I was going to create a new issue, but I need the last_kmsg. I thought this will not work because I need to remove the battery every time I need to flash. But I actually got it to work without the removing the battery. So yeah I created the #5124.

Thanks for the help btw
[Magisk] rdmitry0911:
Hi, I have exactly the same problem on my redmi note 8, MIUI Global 12.0.2. Did you find a solution?
[Magisk] zgfg:
No, did not find solution for partitions mounted abnormally. It seems to appear for MIUI ROMs
[Magisk] F308:
But if explanation was given what it is about and it is about unlocked bootloader I would not worry much if all other of behavior is normal.

Likely I have red text on booting Samsung saying that ROM is not original.

Yes. It is not, so what?

I myself made it this way.
[Magisk] zgfg:
If you are referring to Momo:

Partitions mounted abnormally and Unlocked Bootloader are two different findings

Unlocked BL is not the cause for Partitions mounted abnormally

If you followed discussions on Telegram on various channels, there were users who had first without the second, and vice versa.

And many not having either of them, although everybody who flashes Magisk for certain does have their Bootloaders unlocked

Anyway, I'm no more obsessed with Momo, I have actually dosbled the Momo hence I don't care for mow about it 'suspicious' findings and reports
[Magisk] rdmitry0911:
The thing is, that my bank application detects magisk and refuses to work. I'm trying to make magisk invisible to this app using momo as a magisk presence detector, but without success as for now. May be you can provide a reference where you did find a way how to get rid of this abnormal mounting problem?
[Magisk] F308:
Well. This is not my model then I don't follow it. And if phone behavior is not correct it is different story.
[Magisk] zgfg:
You never know if your banking app uses the same detection methods as Momo.

Particularly, does it use some most advanced detection method as provided in Momo

Did you go through all 'regular' prevention checking methods as described in Wiki?

Particularly, did you put your banking app to Magisk Hide (DenyList - whichever you use) - reboot is required then, did you hide/repackage Magisk app, etc

Also, wipe Data for your banking app before the new try - sometimes they remember that 'root' was detected last time

PS: I never got rid of Abnormal partitions mounted detection, hence cannot provide you a reference how to do that
[Magisk] GabbyWC:
I flashed a recent unofficial build of Pixel Experience 12 on to my Xiaomi Redmi Note 9 Pro global version (joyeuse) phone today. I also installed the Magisk Alpha app and will use that to patch this custom ROM's boot.img file to gain root access but should I select the "patch vbmeta in boot image" option or not? This ROM (which is based on Android 12) uses encryption that current builds of OrangeFox and TWRP don't yet support. I have the Pixel Experience recovery installed but I don't think that can be used to flash Magisk. I will flash the patched boot.img file in fastboot mode after I have the answer to my question about the vbmeta option.
[Magisk] rdmitry0911:
Of cause I did everything including wiping app's data to hide root from the app. Nothing works. I have no idea what detection methods they are using, but as far as momo can detect abnormal mounting, other programs can do the same thing. So, I think it is better to start from making momo happy, and if that's not enough, (I believe it would be enough), do something else.
[Magisk] pndwal:
I'd certainly try without changing patch vbmeta as preset first; you can always try after flashing back stock image if that doesn't work / results in bootloop.

Nb. The vbmeta fixes for MIUI, MTek etc are fairly new, eg

https://github.com/topjohnwu/Magisk/commit/228570640eb42333d42b79d17e6301fc0513adb6

- checking the issues that this commit closed may help you determine if you need to change the additional setting.

Due to outstanding issues (need for manual intervention) this toggle has been requested but still hasn't been merged in n TJW builds; it is in vvb2060 Alpha for testing:

https://github.com/topjohnwu/Magisk/pull/5028

Nb.2. There were issues with Universal SafetyNet Fix compatibility on PE ROMs due to their manipulation of certain props; I know that this is fixed in some recent PE ROMs however. PW
[Magisk] pndwal:
If you just name the bank app someone may be able to help you! PW
[Magisk] huskydg:
Magisk works on emulator
[Magisk] rdmitry0911:
It is ubs access app.
[Magisk] pndwal:
I just tried with a similar setup to you (Zygisk, Shamiko etc) using Hide My Applist for root apps, and did not succeed.

Seems app is detecting isolated process leaks etc.

A user here reports canyie's Riru-MomoHider works for UBS Access hiding however:

https://xdaforums.com/t/banks-app-d...hide-and-hidden-manager.3877412/post-85700373

You'll need to revert to Magisk 23.0 to use this with working USNF-Riru (2.1.3) and MagiskHide, or use custom Alpha Magisk (allows MagiskHide w/ Riru) or other custom Magisk, and configure MomoHider for all 4 hide options... PW
[Magisk] Eng.Raman:
When you make Momo happy then ( I believe ) you will be able to run any app just by adding it to the DenyList. No need to configure further steps such as HMA, momohider, ...etc.

I have happy Momo and passed UBS Access app just by adding its first process to the DenyList.
[Magisk] pndwal:
Potential useful point, and I did notice previously that this is possible on Realme... I don't believe anyone has Happy Momo on MIUI... We just need to get real... PW
[Magisk] iankelly2001:
I am using the latest Magisk Canary version 23016 with the latest Universal SafetyNet Fix (Zygisk) v.2.2.1 installed and MagiskHide Props Config installed with a certified device fingerprint installed. But I am still failing CTS profile match when running SafetyNet attestation.

I know that I need to include two items under the Google Play services heading in the DenyList (com.google.android.gms and com.google.android.gms.unstable) but when I reboot my phone, these items won't "stick" and are missing from the DenyList. There is no problem in getting other apps to "stick" in DenyList after reboots.

Any ideas what the problem is and if anything can be done to make the items under Google Play services stick after a reboot? Or is the failure of the Google Play services to stick in the DenyList a bug in this version of Magisk?
[Magisk] rdmitry0911:
I know about that message. I tried it before I changed config to 23016 + Shamiko. It does not work in my case. And more over, momo with momohider installed still detects root. 23016+Shamiko makes momo generate only 1 item in a checklist - abnormal mounting, in 23+momohider there were 3 items in momo checklist
[Magisk] pndwal:
USNF for Zygisk does this by design, not an issue. See documentation on GitHub.

CTS Profile match issue may be ROM or module related... What custom ROM do you use? What device? PW
[Magisk] pndwal:
I notice that user seems to be using MIUI however. Xiaomi Mi 11. PW
[Magisk] iankelly2001:
Problem solved - I changed the device fingerprint in Props Config and it suddenly passed! And the entries for Google Play Services "stuck" in the DenyList afterwards as well after reboots.
[Magisk] pndwal:
I take it you do have a custom ROM? Or Chinese region?

That's strange... Unless you turned off Zygisk, or changed to USNF version lower than 2.2.x.

This is supposed to ensure gms services don't stick in denylist w/ Zygisk:

https://github.com/kdrag0n/safetynet-fix/commit/cd84bf361f1514601a99bcd2fb027528fc16f612 🤔 PW