yashsingh1/xdaforums huggingface dataset:
[Magisk] madkiran:
on latest Magisk 18 Google pay and some other banking apps are not working (saying device is rooted).

Magisk hide is not working (still detecting root)

Disabling "phone" permission for Google Play services is the only option to make them work. but If I do that some features of google are not working..

Magisk 17 is working fine ...

is there are workaround for this ? (I don't want to disable phone permission)

hope [MENTION=4470081]topjohnwu[/MENTION] will look into it and fix this.
[Magisk] FuSan:
Ok it seems to be fixed for now. I did remove the battery restrictions before. Since than I did restart sometime in the day, but who knows why didn't it work that time. Anyway fixed at the moment. Will notify if the problem comes back.

---------- Post added at 09:03 AM ---------- Previous post was at 08:59 AM ----------

Did you try the "Hide Magisk Manager" option in settings? Mine seems to work without it though. I have payooner, skrill, a local banking app. All of these 3 detected root without magiskhide but is fixed after I added them to it.
[Magisk] jcmm11:
Try turning battery optimization off for Magisk manager and see if that helps.
[Magisk] dj75:
safetnet not ok

sorry but safety check partially failed.

the file for fix it does't install from twrp.

the error is that magisk is not installed! imposdible!

i put a screenshot

asus zenfone 3 deluxe non pro version with the lstest oreo firmware installed
[Magisk] Cristiano Lira:
Tinder doesn't work with Magisk Manager app installed - it stays on setup phone page. It works when I install Magisk through TWP but don't complete Magisk Manager app installation.
[Magisk] Didgeridoohan:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] dope77:
Magisk uninstaller literally does nothing. Tried uninstalling from the manager itself, phone rebooted and magisk maanger got installed by itself, also 18.0 was still installed.

Tried the latest zip and flashed through twrp, still same problem, while flashing in twrp, i saw that it says boot.img backup not found. How do i remove magisk without flashing stock
[Magisk] xunholyx:
Really? Tinder is looking for root? lol
[Magisk] jcmm11:
You need to flash stock boot image. Backup not found is why uninstaller failed.
[Magisk] dope77:
Nah, but here's how i removed magisk.

I already have magisk 18.0 installed, so i reFlashed 18.0 from twrp, rebooted. Then rebooted to twrp and flashed the uninstaller. It worked.
[Magisk] ChrisG12:
What finally worked for me:

1) Flash latest full factory image (using flash-all script with -w to wipe phone)

2) Let phone boot, did initial setup (wifi, google, etc.)

2) Booted TWRP image using fastboot boot

3) From that TWRP instance I installed both TWRP zip and Magisk zip

4) Phone booted and everything worked.

Not sure that is a magic formula - as others have said - sometimes just trying things in different orders or multiple times seems to work too...
[Magisk] Spaceminer:
Moto G6 Play (xt1922-7) Magisk 18.0

Adding the Viper4android module to Magisk breaks the magisk.img. Root still works but it causes my boot animation to play half way, cutoff, then play a second time before finally booting. (Every boot.) It also causes graphical glitches on screen. I see random white bars that last only a split second. It's intermittent and unpredictable. Should I drop a bug report here, or in the Viper4android magisk module thread? Both??? Should I also upload the bugged out magisk.img? Should I try again on canary then post logs? Looking for some guidance here.

Edit: It still happens using the latest Canary. Switching to "Magisk Core Mode Only" fixes it on both Magisk v18 and Canary, but it also prevents Viper from working entirely, which makes root essentially useless to me... Any help would be greatly appreciated.
[Magisk] TheDevelopper:
>Hi there! Please, can we use some Magisk modules on our Galaxy devices? Because some users said that this cause some random reboots?>/
[Magisk] tech_head:
Yeah, I no longer pass safety net on my OnePlus 6T.

If I just install ElementalX, no issues but Magisk 18/18.1 no dice.
[Magisk] aadeshiscool:
How to use AdBlocker in magisk 18?
[Magisk] aadeshiscool:
I am not able to use adaway with Magisk 18, can some one help me out? Systemless hosts is enabled.
[Magisk] martyfender:
The systemless hosts is now a module. You click on it in Magisk Manager settings. You will see a toast: "added systemless hosts module".

Just like any other module installed, you must then reboot for it to be enabled.

---------- Post added at 02:41 PM ---------- Previous post was at 02:35 PM ----------

If the adblocker depends on the hosts file, You must first go into Magisk Manager settings, click on the systemless hosts option. You will then see a toast: "added sytemless hosts module". And just like any other module installed, you must reboot for it to be enabled.
[Magisk] M1810:
anyone knows of a module that enabled blur on quicksettings on pie?
[Magisk] DanGLES3:
Magisk can't do that,as stated a thousand times already (MAGISK IS NOT XPOSED)
[Magisk] ipdev:
[MENTION=6776154]aadeshiscool[/MENTION]

A little more info would help.

Device, ROM, Setup, ...

Two quick questions.

Did you use a patched boot.img or flash magisk using TWRP?

Did this happen after a ROM update?
[Magisk] 124112:
I tried to update Magisk from 16.x via the app, and selected Direct Installation. Now my phone is stuck at a screen that says Welcome to Fastboot Mode.

This is my first time updating Magisk. I don't know if it just wiped my phone, but I hope not. Please advise on what to do from here.
[Magisk] martyfender:
That is why I always flash Magisk with TWRP, because I have had that happen several times on my 5 devices. Here is what solved it for me:

Do you have twrp?

First, reflash you stock boot.img. before rebooting flash the Magisk.zip, all while booted in TWRP.

If you have used the patch boot.img method in the past, because you don't have TWRP for your device, reflash that patched boot.img in fastboot, again, If you saved the copy.

I assume that was done with an older version of Magisk. If that boots fine, Update Magisk Manager, to the latest, (but I assume you already have the latest) patch a stock boot.img with the newer version then flash it in fastboot.

Apparently, on some devices, such as mine and yours, the direct install method can corrupt the boot.img or the the flash does not complete, I'm not sure.

I have not had this occur once since I always now flash with TWRP.

Updating MM through MM is ok.

When you choose to install Magisk, choose install, download zip only, then reboot to TWRP select the downloaded Magisk.zip to flash it. For example, here is an unoffical one I just updated today: Magisk-v18.1.r7-2018122418.zip. Just choose the name of the most recent one you downloaded in the Android download folder.
[Magisk] 124112:
I will try this, thank you. It has been a while since I first rooted this device (LG V20 T-Mobile), and I did use TWRP (if it wasn't wiped?)

Going to do daily NAND backups after this.
[Magisk] martyfender:
I updated my post above. If you accidentally wiped TWRP, you can reflash it first, in fastboot, before proceeding with the above instructions.

The below files need to be on your PC, I always put them in the adb folder and open the command window in it by left clicking on an empty area of the folder, then right click,choose: open a command prompt here. You can also create a shortcut for the command prompt in that folder to make it easier then you can right click and choose run as administrator. (Some times necessary on Windows 10?)

Boot to bootloader/fastboot mode.

To confirm your device is connected to the pc:

fastboot devices

Hit enter, the device fastboot serial number is shown if connected.

To flash twrp in fastboot:

fastboot flash recovery twrp.img

(substitute the actual name of the twrp image, above) hit enter to flash and wait for successful completion.

To flash the stock boot.img:

fastboot flash boot boot.img

(substitute the actual name of the boot image, above) hit enter to flash and wait for successful completion.

If you have a boot.img on your device, you can also flash it in twrp. I keep a stock one in my Android download folder.

Do not reboot to Android first, instead:

Reboot to TWRP and select install, navigate to the Magisk.zip and swipe to flash. Read the message to confirm that there were no errors.

Reboot.

The above is assuming you are using Windows. If you are on Linux, like I am most of the time, you must use sudo before each fastboot command to run temporarily as root. Don't use sudo with Windows, though.

If you have trouble connecting to your pc in fastboot or adb mode, then you have a Windows driver issue, more than likely.
[Magisk] simplepinoi177:
Just an important note and warning; if you have any kind of Google Pixel phone, do

NOT

follow the non-spoiler part of this quote!!! At least for all Pixels (XL versions and non-XL versions), there is

NO

recovery partition -- the recovery resides in the boot partition/image! This often misunderstood fact has caused endless issues on the taimen forum....
[Magisk] hubab:
Anyone can help plz?
[Magisk] Didgeridoohan:
There are a few errors in your logs, but nothing showing why the YouTube apk wouldn't mount properly. Does other modules install as they should?

And it would be much better if you use the Canary debug build when posting logs... The regular Magisk log doesn't really show much as far as troubleshooting goes.
[Magisk] khalisz:
Issue with Titanium Backup Pro

Hello,

Titanium Backup Pro doesn't works with Magisk v18.

But still with Magisk v17.1

I sent an email to Titanium Backup Pro support team :
[Magisk] Paenik:
Hello, can you please solve the problem with the Galaxy S9 (+) G965FXXU2CRLI official Android 9 Pie. In the first system setup with WLAN, Google Account and the other things to set up. From the set up of iris scanners, face scanner and inteligent scanner as soon as the camera starts to come a screen where only black and is at the top in red letters that is allowed with official firmware, then the phone does not start and you only get into the download mode , please fix the problem (it can also be due to TWRP)

greetings Jeff
[Magisk] ktmom:
TiBu works fine on my PH-1 using Magisk 18

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
[Magisk] miststudent2011:
[MENTION=4470081]topjohnwu[/MENTION] bringing to your notice.

Emui 8.1 is detecting root on Honor 10 even after root hide in magisk while logging into Huawei account. Screenshot attached.

https://imgur.com/a/4kW8q8d

Edit: Paytm app too.
[Magisk] khalisz:
Yesterday I've done a full wipe of my phone.

I have installed as usual TWRP + Magisk v18.

Then after that I've installed Titanium Backup Pro for restoring my data.

When I've launched Titanium Backup Pro, it doesn't recognized Magisk and then no root access requested from it.

When I've unsintalled Magisk v18 and installed Magisk v17.1

Titanium Backup Pro has recognized Magisk and requested the root access.

It means for me, that there is an issue with Magisk v18 or Titanium Backup Pro.

I did the update to v18.

Yes Titanium Backup Pro still working properly.
[Magisk] ktmom:
You're missing the point. TiBu is requesting root without trouble on my device on Magisk v18. So your problems are not universal. Ergo, you will have to do more than just complain.

Run the Canary build, grab logs and also a logcat while opening TiBu to capture the time the su request occurs.

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
[Magisk] martyfender:
Thanks for pointing that out. I am aware of the the fact that they have boot/recovery, but since I have never had one, I am not very familiar with the procedure on Pixel devices. Are there any other devices that do it this way? The Oneplus 6/6T? Also, on Samsung devices one must use Odin in download mode.
[Magisk] guest4711:
You should either send your device to the developer so he could analyze the problem(s) or submit proper logs so someone could try to understand what is happening...

In the meanwhile you could also try [MENTION=4667597]Didgeridoohan[/MENTION]'s "Magisk Hide Props Config" module and read his fine "Magisk Trouble Shooting Guide" with many good ideas.

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] jcmm11:
AFAIK it's for any a/b device. For more info see https://xdaforums.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
[Magisk] dope77:
Yes there's a problem with magisk 18. It's magisk hide, turning on magisk hide will hide ROOT ACCESS FROM ALL APPS, EVEN IF THEY'RE NOT SELECTED.

The solution is simple, turn off magisk hide from magisk settings and you're good to go
[Magisk] khalisz:
Magisk hide was off.
[Magisk] ktmom:
Suggesting that this problem exists across devices is incorrect. Using Magisk hide does not cause problems on my device. And specifically TiBu still works fine, unless of course, I add it to to the hide list [emoji16]

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
[Magisk] dope77:
5 different devices with magisk 18 had this problem, turning off magisk hide solved the problem when apps like greenify, arcai netcut, root explorer... Failed to detect root when magisk hide was turned on, even if they weren't selected.
[Magisk] ktmom:
Well, we overlap with root explorer which has no problem on my device. If it's that reproducible for you, then logs probably would help. I would also wonder if you have a module(s) installed that are interfering.

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
[Magisk] dope77:
On my current device, only xposed sdk 27 and systemless hosts. On my friends devices, none. As i mentioned earlier, turning magisk hide off solve the problem. Turning it on will hide root from all apps even if no apps are selected. Never faced this on 17.3
[Magisk] martyfender:
Thank you so much for linking that article. It was extremely informative. I had recently searched and did not find anything like this that helped me understand A/B devices.

Reading that article and others linked in it made me realize that in some reports here of problems with Magisk 18 could be because things were flashed in improper order. For example, bootloops after flashing Magisk 18 etc and certain mods etc being overwritten. Many of those reports, I believe, were on A/B devices.
[Magisk] Didgeridoohan:
The key question is: have you provided any logs to help fix the issue?
[Magisk] aadeshiscool:
The pictures were taken after rebooting.
[Magisk] martyfender:
Are you using Adaway v4.10? If so, do you also have the systemless hosts option set in it's settings. If you are on v3.3, it will be greyed out, but still works.

If that still does not work, maybe try uninstalling Adaway and installing it again. Are you getting a root prompt when you try to apply a new host file?

If it still does not work I would suggest first searching the Adaway xda thread then asking if you can't find an answer in your search.
[Magisk] Nimueh:
2 different devices here and they have no such issue.

Greenify, TiBu, MiXplorer, Matlog, SD Maid ... I could go on but they ALL work on v. 18 with Magisk Hide enabled and none of them selected to hide Magisk from.

So no, you can't say it's a general issue :rolleyes:
[Magisk] gideonlfc:
Snapchat refuses to login for me this morning.

I've hidden from Magisk. Restored backup and data from titanium backup but I keep getting kicked out.

Anyone else experiencing this?
[Magisk] intruder16:
Just because something is broken in the app you use, you say that app is garbage?

I'm not gonna waste my energy here. Already felt a little bad for Kernel Adiutor app dev and now this.
[Magisk] jsaxon2:
I have no problem with it. Just long press on the app and allow.
[Magisk] gohamstergo:
hey [MENTION=4470081]topjohnwu[/MENTION], think you could add a 1x1 widget to your app to allow quick toggling of the root mount option? great work btw!
[Magisk] knpk13:
Maybe you can use Zooper widget pro to create a root mount toggle? (Like the widgets created to emulate the new Nexus launcher)
[Magisk] adrman:
Just had another payment attempt fail. This time I was as vanilla as possible. N6P, stock, rooted via phh, no Adaway, Xposed, custom kernel, etc... installed. I do pass Safetynet though. Although this is an excellent mod, I don't think AP is going to work with it in current form.
[Magisk] :
Agreed, Google is crafty this time and while yes AP runs and you can add cards payments are not working. I tried same thing clean wipe everything start from scratch and install only magisk and phh stuff, added card, pass safety net, fail payments

Just a stock Nexus 6p nothing fancy
[Magisk] adrman:
It wouldn't surprise me if there were a few folks in Mountain View getting a nice chuckle reading this thread.
[Magisk] gaganit:
Just checking: has anyone successfully completed an AP transaction?
[Magisk] LLStarks:
If you delete the requesting app from the Superuser GUI, you can't re-add it apparently as all further elevation requests will be automatically denied.
[Magisk] noidman123:
Tried at the vending machines in my break room on an LG G4. Could set up and add a card but payment won't go through
[Magisk] adrman:
Can you just clear data on the Superuser app? Yeah, I know you'd have to reauthorize all your other apps.
[Magisk] mykenyc:
Also to chime in i think http://xdaforums.com/android/software/viperaudio-viperatmos-3-8-sq-driver-t3289075 is better personally so I'd love to see that port. The version i use the most is ViPERAtmos 5.5 Sony Beats Edition and judging by the download count i would say others prefer it too.
[Magisk] bobby janow:
Probably some truth to that. But he who laughs last, laughs best. You know it's only a matter of time until someone figures this out if they haven't already. But will that knowledge be forthcoming since each time it's done it gets patched. With all the Android brainiacs out there someone knows what Google is seeing on a rooted system and then tripping the CTS check and Pay pass through. So whoever knows please PM me and I promise not to tell. :angel:
[Magisk] axiomofdarkness:
I also have this issue on a Droid Turbo. I am running the 6.0.1 Brazilian OTA, specifically this ROM. It seems to be a Motorola-specific issue.
[Magisk] FPSUsername:
Sorry to say, but I see this app as bloatware on my phone to use xposed systemless. I know what your purpose is with this app, but couldn't you work together with dvdandroid and implement this in the material xposed installer app? This way, we only need 1 app to control all the xposed stuff. And for disabling root, I get it, it shouldn't be in the xposed installer app, but as long as chainfire didn't develop a good "switch", its in my opinion the best solution
[Magisk] :
Totally bloatware dude. Runs in the background, hogs your CPU, eats your RAM. I never knew an app could slow my phone down so much! Magisk Manager literally sucks my battery down. Not kidding, I saw it crawl out of the screen and start chewing on my battery!

Jokes aside, if all your gonna do is complain you can gtfo. He already said the app was proof on concept, maybe if you read the OP you'd know that. Hate to be so harsh but when I see users telling devs what 'should' be done it pisses me off.

Have a good day.
[Magisk] FPSUsername:
Its just an app that I don't use. Thanks anyway
[Magisk] :
Then delete it?
[Magisk] FPSUsername:
Won't that interfere with the xposed systemless stuff?

Edit: okay, seems to work fine. Why aren't the files that get installed with this app not in the systemless xposed zip? Seems like that could be done and have only the app as an option to install
[Magisk] jsaxon2:
I do not have this problem at all. I just tested. I deny app, then delete app from superuser app. I then open my app and it requests root and I am prompted. Just like it should. Maybe you tried older version, but it is working fine for me.
[Magisk] Starvirus:
Well i'm still struggling with Magisk on my Axon 7 (A2017G, Firmware: B03 with unlocked bootloader)

I installed Magisk without error

logcat doesn't show anything from magisk

magisk manager shows magisk v6, but doesn't let you toggle anything

install phh su anyway

magisk manager shows magisk v6, but still doesn't let you toggle anything

/cache doesn't show any logs from magisk

any idea what's going wrong?
[Magisk] Dalamar666:
Some people said that works with suhide

http://xdaforums.com/xposed/unofficial-systemless-xposed-t3388268/page208

---------- Post added at 10:43 PM ---------- Previous post was at 10:40 PM ----------

Did you full unroot before? mm

Did you installed phh superuser manager? https://play.google.com/store/apps/details?id=me.phh.superuser&hl=es

try installing phh superuser, it's provides root...to toggle root ;) it's like supersu

also, wipe cache/dalvik
[Magisk] Starvirus:
yes did a unroot with the unsu.zip

phh's superuser manager is installed as well (but shouldn't be necessary to see magisk in the logcat somewhere)

dalvik and cache was wiped as well

but still the same
[Magisk] synxx:
I had the same problem as you. After abit of digging it seems superuser doesn't remove everything when doing the unroot in the app. I found a unsu.zip and flashed that, then followed the steps again and all worked fine.

For some reason I can't upload the zip file, I will try find the thread again for you.

http://xdaforums.com/showpost.php?p=63615067&postcount=2459

There you go :)
[Magisk] Starvirus:
that's the one i used
[Magisk] RandomPooka:
I know I'm late to the party. Just confirming that disabling Xposed will allow SafetyNet to pass again. Not much of a problem with that here, as I only use a very few Xposed modules, and none of them are critical to me.
[Magisk] chris9000:
I have no doubt that method works. But I must wonder...is this the start of a root arms race with Google? Does it stop here? Will Google constantly be finding ways to make life harder for rooters?

:(
[Magisk] theredbaron1834:
Yeap, just confirmed too, its xposed. Though for me xposed has a few "critical" modules. If I need android pay, or pogo, I guess I can always disable and reboot. Still sucks, though it does work.
[Magisk] Jorgesanux:
hello, well, after I installed this root, restart my phone for some modules Xposed be activated when the cell start, I realized I had left the root, so I took a chance and went back to flash the zip Magisk v6 and start again when the cell, and had root. I say all this for what it's like bug report or if someone else happens. Forgive misspelled or badly written nap, I am translating with google Traslate

Enviado desde mi MotoG3-TE mediante Tapatalk
[Magisk] JudgeDread11:
Have you tried restoring your original boot image.

Magisk shouldn't change the state of SE Linux.
[Magisk] mybikeisblack:
Hmm, I get stuck in bootloop if I try and disable xposed through the app. Had to flash the uninstaller and then reinstall. Thing Ill just stick to the old update for now unless I can figure this out.
[Magisk] Artim_96:
At least Magisk, but at first you have to remove the build in root
[Magisk] krelvinaz:
Just used this on my Nexus 5X which didn't have Xposed but was rooted with SuperSU. Unrooting was very straight forward, loading Magisk and PPF Root was easy. Quite happy to have Root, and still be able to use Android Pay even though I don't use it often.
[Magisk] synxx:
Sorry I didn't see your reply to the other person.
[Magisk] aIeck:
Okay, that's what I figured. Good to know!
[Magisk] yoorilovesyou:
Magisk with Xposed

I tried to run xPosed using settings provided on the UI xPosed installer. I'm using my Nexus 5 running on Cataclysm 6.0.1 after installi g and flashing systemless xPosed on twrp it says system UI has stopped. Uninstalled the xPosed and phone isnworking fine. Is there any workaround from this?