Not going to be very helpful, sorry but...

1) This is the best formatted post I've seen on here. Damn.

2) Make sure you create a post in the Magisk Support thread so that information is out there. I'd format it exactly like this. /u/topjohnwu would appreciate it I'm sure.

As that article mentions you will need to install and use a CA cert on your phone with that wifi connection. I found this guide on how to do it but you'll have to work with your tech support in order to figure it out and they'll have to provide the appropriate cert. There's also a magisk module called "Move Certificates" that you may need to use to move user certs to system certs.

If you mean microG, that's just open source implementation of minimal Google services. It's generally considered safe to log-in to the microG, but I can't say you did anything wrong.

Consider visiting https://microG.org

It's possible that Magisk is being removed randomly.

This is a common issue i've seen around various forums.

Installing Magisk 16.6 fixed it for me. https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589

The latest beta is 16.7, so i assume that would work as well.

The .zip from the Magisk repo has always been glitchy. Download your appropriate .zip from here : https://forum.xda-developers.com/apps/magisk/magisk-iytbp-youtube-vanced-t3712097

Then flash it via Recovery. Don't forget to disable your built in Youtube app.

Some people in the beta thread appear to be having luck with v13 betas. If you're desperate and the steps in the guide don't work, I suggest you try the beta.

FIXED IT! The problem was I had a second magisk app. I hided it and disabled it using this to hide root from banking apps as I already mentioned. That's why I couldn't see it. Lucky I had LS Posed and xprivacy module installed. I used them to uninstall the hidden app from there and everything worked!

Do you pass safety net? Did you hide the app with Magisk Hide?

https://play.google.com/store/apps/details?id=com.scottyab.rootbeer.sample

https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettest

Try testing SN with this app and see what it says. If it fails, then try this fix

No problem man. Currently my DNS setting is Auto since my hard reset a few days ago. I usually use cloudflare though, but haven't experienced any issues with vanced syncing correctly.

I use Private Internet Access for a VPN and when it's active, it uses its own DNS settings. So I think I may just leave my phone's set to auto unless I run into issues.

That's no advantage because there are other ways to prevent that without systemizing the apps in my case I use https://play.google.com/store/apps/details?id=com.baloota.dumpster&hl=pt_PT it automatically backups any deleted or updated app or file.

Try to test the integrity of your device with this : https://play.google.com/store/apps/details?id=gr.nikolasspyr.integritycheck

Note : MEETS_STRONG_INTEGRITY will never succeed with an unlocked bootloarder

All I needed was the displax Safetynet fix mod, that setup has been passing Play Integrity here for months.

Try:

• Uninstall shamiko + any props hiding/changes
• Enable zygisk
• Enable "enforce denylist"
• Hide the magisk settings app
• Install the unsf displax mod
• Clear data for:
• * Google play services
• * Play Store
• Then reboot

You should be passing at this point. I usually use this app to test play integrity status: https://play.google.com/store/apps/details?id=gr.nikolasspyr.integritycheck

I've never needed to add gpay to the denylist, only banking apps and others that detect root themselves rather than relying on play integrity.

Try switching to the modified version of the Safetynet fix by displax (it's on XDA in the unsf module thread and on the author's github,) then clear data for play services, the play store and the Marriott app. You might need to reboot after clearing play services data, I don't remember.

Once you've done that you should be passing the new Play Integrity checks that apps are doing now, and with the Marriott app added to the denylist it should work. I didn't really spend any time in the app, just long enough to flip through the sections along the bottom, but it launched and worked for me.

FWIW Safetynet is deprecated now, you want to check to see if you're passing Play Integrity verification using something like https://play.google.com/store/apps/details?id=gr.nikolasspyr.integritycheck

my vol buttons are dead. i found an app in the store that allows you to have an iOS style control center. not the best but it works.

link to app: https://play.google.com/store/apps/details?id=com.luutinhit.controlcenter

Download Play Integrity API Checker and see does your device meets both basic and device integrity.

If it doesn't meet them then you can fix it. If it does meet both of them then your bank app checks for strong integrity which currently cannot be bypassed.

I'm not sure if you're using the modded version of USNF, but I think I'll do a copy and paste of a comment which I did here, a few months ago...

Google deprecated SafetyNet, in favour of the Play Integrity API, basically rendering the original USNF module useless. However, you can try this modified version of the same module on XDA, by Displax.

As for checking that you can pass the Play Integrity API to at least MEETS_BASIC_INTEGRITY, get this, from Google Play. Also, I'd recommend not using the MagiskHide Props Config module with this, as the modded USNF module drops the device fingerprint to Android 6.0, but MHPC basically reverts that.

As for Momo, you're better off asking anyone other than me

Is it your phone/Google Play Services thats detecting root, or the RootBeer app?

Install this to check if SafetyNet Attestation is passing. If it does you are ok to use banking apps and Wallet

Magisk is systemless (system partition remains untouched).

To edit the Build.Prop file, I use a Root Browser. Only a few of them allow you to mount System as R/W.

I have wallet working with the same setup as yours. Maybe check RootBeer Sample if anything is getting detected? Make sure to hide it via Magisk

If you and him are running on custom ROMs, did they pass SafetyNet to begin with? Pixel Experience does. I always make sure to fully set up Magisk and its modules and verify that I pass SafetyNet with YASNAC before running apps such as Google Pay / Wallet. If your device gets flagged for failing SafetyNet at any point, it's messier to recover from that.

There are few apps detect zygisk. The example is here https://play.google.com/store/apps/details?id=id.bmri.livin&hl=en&gl=US&referrer=utm_source%3Dgoogle%26utm_medium%3Dorganic%26utm_term%3Dlivin+by+mandiri&pcampaignid=APPU_1_KpnNYp6YAYvg4-EPmcKMoAs

You can use Thanox to blur the tasks in recent menu. It also has an app lock feature, which I guess is in pro version only. I'm using pro version, its worth it.

Github link - Thanox

Play store - Thanox pro

Yeah I'm using this for the moment https://play.google.com/store/apps/details?id=live.wallpaper.livewall

but the app gets kill even though I disable battery optimization and it has double lockscreen which is not that good either.

I wasn't able to do it in Tasker on my phone (A11), but i think Tasker has (or plans to have) this functionality on Android 13.

I could however do it with Custom Quick Tiles, using root commands.

But this is also REALLY not simple. (Although it should be)

First, you need a command that works on your phone. On my OnePlus i can use settings put global oneplus_screen_refresh_rate and set it to 1 or 0 to choose 60 or 90 Hz. But this won't work on a Xiaomi.

Second, and WORST, not only do you need a paid version of the app (like a dollar) to use root commands, it is SUPER FUCKING BUGGY. As in, it will usually not give a shit about what you tell it and will just not save the changes you make.

But since I did spend over half an hour setting this SIMPLE thing up, here is a demonstration and how to set it up (which miraculously worked first try this time). Of course you have to replace the command with something for your phone.

Some tips to maybe avoid bugs when setting it up:

• Set the command actions first
• Set the tile names second
• Set the icons last
• At no point, during the previous steps, should you leave the config screen
• When it's setup, test the tile a couple of times before leaving the config screen. This seems to help save the changes.

you will probably find it useful to check the results of a SafetyNet and CTS Profile check, such as https://play.google.com/store/apps/details?id=rikka.safetynetchecker

also, go into Google Play, Settings, About and check if your device is being recognized as certified. If it's not, you may need to set a Build Fingerprint using resetprop.

Aside from that, make sure Zygisk is enabled, turn on the deny list and make sure the banking apps are on it.

wow thanks. here's the playstore url: https://play.google.com/store/apps/details?id=sg.gov.nea&hl=zh&gl=US

​

P.S. Current fix for now:
Magisk alpha 13450819-alpha(24306) (27)
Modules:
riru v26
riru unshare 2.0
shamiko 0.4.4(106)
Universal SafetyNet Fix 2.1.3 riru

It means adding your Android ID to this webpage which is intended for users who want to use custom ROMs (aka that can't get certification).

Check your Android ID by using SQLite on the Google Services Framework's database (/data/data/com.google.android.gsf/databases/gservices.db) at the row main.android_id or use the Device ID app (check out the Google Services Framework section).

That should add your ID to Google's database and certify you upon the next check, which in my case I triggered by deleting all data from GSF, Google Play Services and Google Play Store.

Techcombank - This app CAN DETECT Magisk app even it has random package and doesn't check Magisk traces in isolated process so uninstall/freeze magisk app or put Techcombank in IsLand and it will work

Moreover, this is also an app has strong detection that DenyList is not enough to hide root

Check this app: https://play.google.com/store/apps/details?id=ua.gov.diia.app

Idk about a magisk module.. but there's a Xposed/LSPosed/EdXposed module available on Google Play and it works.

https://play.google.com/store/apps/details?id=net.accelf.devoptshide

Just install.. LSPosed module be it Zygisk version if you are using Zygisk or Riru version if wanna use that.

Activate the module, add your app to its list and you are good to go.

If you have lucky patcher installed you can do it from the app. If not just go here (https://apkpure.com/google-play-store/com.android.vending) and hit Download APK and then install it. I have the same phone as you and I hap trouble passing safetynet as well. Eventually, I figured it out. Let me know if this works.

googling "outlook bypass module" led me here:

• https://forum.xda-developers.com/xposed/modules/mod-bypass-exchange-policies-outlook-t3408049
• http://repo.xposed.info/module/info.xposed.bypassexchangepolicies

I dont remember if that's what i used, but it's worth a shot.

If there's magisk modules too then i dont think it would hurt to try :)

I used this app to freeze the Magisk Manager app and it worked. But I only tried it with the german Sparkasse Tan App, not sure if it works for you

I assume you've unlocked the bootloader and survived the data wipe (and dealt with frickin RMM state, VaultKeeper, etc.).

1. Download a custom Recovery for a device. TWRP has never failed me.

2. Start ODIN, and flash the tar file. Make sure you do NOT check Auto Reboot in the Options tab. This installs a Recovery on the device.

3. Yank out the battery or force shutdown. Turn on the device using a Recovery mode key combo. This is important; stock ROMs usually wipe a custom Recovery binary when it is detected. TWRP patches the stock ROM to prevent that, but it requires you to immediately boot into recovery.

4. TWRP boots. Check if you can go to Advanced » File Manager and Internal Storage has all of your files in a correct way (i.e. not garbled).

5. If the files and folders have garbage names, it means your device has File-Based Encryption. If you don't see anything at all, it means your device has Full-Disk Encryption. In any case, you need to wipe data and internal storage from within TWRP. Go to Wipe and swipe the slider to wipe internal storage and apps.

6. Reboot to system. Set-up the device via the First Time Boot Setup aka Android Setup.

7. Install the Magisk app.

8. Rename the Magisk APK to Magisk.zip and reboot to Recovery.

9. Flash the Magisk.zip by Install » Browse through for the ZIP.

10. Reboot and see if things work out.

Check post #4 on this thread on XDA-Developers. I have a Pixel 3a XL and the TWRP recovery for the 3a XL doesn't work with Android 10, so I cannot flash the Magisk zip. The steps in post #4 is what I used to install Magisk.

https://forum.xda-developers.com/apps/magisk/lineage-os-17-unable-to-root-magisk-t4073269

According to ththe XDA core-mode Magisk thread (https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366), my only options when flashing this over are:

• Flash It Thru TWRP Recovery
• Or Magisk Manager --> Modules --> Add (+)
• Or Flash It Thru ADB Sideload

None of those options are available to me as I am limited to fastboot commands. Unless there's a way to use fastboot to "sideload?" I did see where the Pixel 3 group has a fastboot img available for flashing, but I've not found one for the LG G6.

Magisk officially supports Android back to 7.0 for "full protection" and back to 6.0 for hide.

https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

It's more likely OP did something wrong or something is fucky with their unofficial lineageOS build.

The images that you typically flash with Odin are actually a bunch of smaller images in a compressed format so you can't patch them easily. If you rename the file from name.tar.md5 to name.tar you can extract the individual partitions using something like winrar and use Heimdall to flash only the boot partition. It's a bit more complicated than using Odin so if you want me to make a little tutorial just tell me what os you're using

Microg has an unofficial lineage fork that has magisk+microg pre-installed. You can check it out at the link below. That's where I was going anyways so i decided to use this fork instead, which made everything way easier.

https://lineage.microg.org/

It took a while, but I found a MAGISK UNINSTALL FOR ALL VERSIONS!

​

https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

​

I worked like a charm!

​

What I did:

1) Booted into TWRP

2) Enabled TWRP Sideload

3) On Computer: sideloaded the Magisk uninstall zip

4) Waited a few seconds

5) On phone: selected to reboot the phone

6) Waited about a minute for phone to reboot properly into a working phone!!!!

Good luck. I've literally just finished reading
this:

Which actually had a new release today stating that they've fixed the disappearing root issues. Haven't tried it yet to find out.

Get the uninstaller from this thread:

https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Specifically this:

https://github.com/topjohnwu/Magisk/releases/download/v16.4/Magisk-uninstaller-20180429.zip

I had the same issue for months. I tried so many things, reflashing rom without magisk, different roms, kernels, to no avail. What worked was simply flashing "Universal SafetyNet Fix v2 Beta 5" https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431

Instantly fixed both magisk safety net and android pay :)

Magisk 15.1 was released, here's what's changed.

Official XDA thread

Announcement post

 

Changes...

• Fixed some bugs that were causing bootloops for some users. > Topjohnwu: The previous stable release has been put into extensive testing from my testers, and also very thoroughly tested on my side (4 different device setups, 4 Android versions), but still some issues are kept under the radar and went through all the testing...... > > Please accept my sincere apology! There were some faulty code in magiskboot, which in some cases will cause fstab to be corrupted, leading to bootloops. The issue is now identified, reproduced, fixed, and tested. In addition, with reports and feedback from users, Magisk Manager is also updated with bug fixes and more robust sudb management.
• Support sorting online repos by "Last Update"
• ‎Fixed issue where advanced installation settings wouldn't stick
• ‎Prevent sudb from crashing Magisk Manager

If you're on mobile you have to open the link in a new tab when you're on the XDA page. Here's a direct link from the official GitHub: Link

Here's the official XDA post.

I'm not sure what you're talking about. If you have problems with magisk make sure you have installed the latest zip and magisk manager from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 . Magisk manager has been removed from the google play store but the apk is available in the xda thread.

> I'm trying v13.3 Pixel b2 now. We'll see how it goes. It mounts correctly so far at least

I'm trying v13.3 Pixel b2 now. We'll see how it goes. It mounts correctly so far at least.

you can find it here https://forum.xda-developers.com/apps/magisk/unofficial-google-pixel-family-support-t3639262

The first link has the newest manager, uninstaller, and magisk img.

Works fine for me, 6P with core only mode as well. Maybe try disabling core only mode then.

You already tried rebooting I assume? Otherwise, try uninstalling and reinstalling using the tools on XDA.

https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Stickied in an attempt to keep all discussion centralized.

OP, if you have a problem with this and would rather me make a post and use that as a sticky instead, let me know and I'll happily do so.

Edit: Potential temp fix on XDA (thanks /u/IzeBerg!)

Yes there is a viper module that is a fork that actually works let me go find it real quick and I will link it (assumed you already had it sorry)

Edit:link

https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589

I'm quite sure the only requirement is a linux kernel above v3.5 and at least android 5.0

no offence but looks like you have no idea how flashing works on android devices :D first of all your bootloader must be unlocked, after that you have to install a custom recovery like twrp. Boot into the recovery, make a full backup of every partition, after that flash the zip either with sideload or from your local storage. Regarding the unlocking and installing the custom recovery I highly suggest you visit the xda thread of your device, I'm sure there are guides on how to do everything. (can't tell you any specifics cause it's different on every device)

Good luck and don't forget to backup!

There is a known issue with Xiaomi devices and Magisk For this to work, you need to add a module to magisk.

Refer to THIS thread to get it working.

Don't use the magisk module, use the vanced manager: YouTube Vanced (vancedapp.com)

And remember to disable auto update both for youtube and for youtube music (if installed)

Sure: * Open the magisk app * on the top right, there is a settings symbol. Click on it * scroll a bit down until you find the "systemless hosts file". Toggle that switch on. * reboot * Download and install Adaway: https://adaway.org/ * open the app, grant it root access, click on the red button at the bottom (if you see a pause button, it's already enabled) * check if ads still show up, if they still do, reboot again * if have trouble with YouTube ads, I'd recommend an alternative YouTube client: NewPipe https://newpipe.net/

So i found this trick, i hope it works with you ("it worked with me")

Download : Disable Application [ROOT]

Here is the link : https://play.google.com/store/apps/details?id=com.iamaner.oneclickfreeze

Go to your renamed Magisk and disable it after you finished with app undisable Magisk!

scrolling app 1

scrolling app 2

Not sure if this is what you're looking for

Yeah, it detects it immediatly upon opening the app and sends you to a webpage explaining they disallow rooted phones.

It's this app: https://play.google.com/store/apps/details?id=dk.bec.android.mb1.b00369.prod

And thanks for your help :)

I've installed the new update 4.1.5 of the Ing Home Bank from google play (https://play.google.com/store/apps/details?id=ro.ing.mobile.banking.android.activity), and I receive the same error with the custom rom, or rooted phone. I'm rooted and use magisk, but up until now the method of hiding magisk from ING app (the romanian version), and changing the magisk installer app name was helpful in running ing app. Have you manage to find a way to solve it?

Do you have any root-related apps such as Titanium Backup and Xprivacy? Because sometimes, it's one of the things apps do to detect root. To isolate the app, try cloning it with the Shelter app, then try again if it detects root when launched from the work profile.

I'm not aware of any modules that can hide ADB. But you might want to take a look at Teamviewer Host as an alternative to ADB based "remote" control apps. Hopefully this works for you!

I checked for the su binaries, but didn't find any. I also found a remote-supuersu script on xda, looked at the source code for the script, and made sure none of the files or directories that were being removed were on my phone, so I'm thinking a previous install of SuperSU isn't my issue.

I also tried removing some other apps that I figured ADT might be detecting (Fdroid, Adaway, TWRP official app), disabled Dev options, and disabled installing apps from 3rd parties, but still no luck. (Each time I test ADT, I force-stop it, and clear it's data and cache, just to make sure it doesn't cache it's previous discovery.)

I'm really having my doubts that ADT can check anything else with their security, and am starting to wonder if they simply have a bug with how they check if someone has a rooted/modded phone (e.g., maybe they have some stupid check like, if android version < 7.0).

You've already spent enough time trying to help me debug this, but if you or anyone else are feeling curious, maybe give ADT Pulse an install to see if you get the same error (it occurs before any login/etc screen shows).