yashsingh1/xdaforums huggingface dataset:
[Magisk] DarkLanternX:
It crashes my play services, and so the SN tab is stuck on an infinite loading. Can reflashing gapps fix this?
[Magisk] teddy0209:
Working perfectly fine here... ?

---------- Post added at 06:52 AM ---------- Previous post was at 06:50 AM ----------

Force closing play services and wiping its data/cache should help...

---------- Post added at 06:56 AM ---------- Previous post was at 06:52 AM ----------

I don't see anything wrong with the log...
[Magisk] rauleeros:
I guess I'll just roll back to the previous version then :/
[Magisk] DarkLanternX:
I cleared the data and cache still seems to crash..i am gonna do a clean install , srsly m pissed.:crying:
[Magisk] Artim_96:
If you are using v10.2 it won't handle superuser
[Magisk] chudy_85:
Work correctly on my mate7 android 6.0

Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka
[Magisk] designori:
working perfectly with magisk 11.1 & manager 4.1.

had saftynet faild issue(cts not matching) with 11.0 & 4.0.

nexus 6p + PN 21jan17 + franco r47

TY topjohnwu!
[Magisk] DarkLanternX:
I just did a clean install reflashed the whole thing

Flashed ROM

Flashed magisk v10.2(just to check)

Installed phh superuser

Updated magisk manager

Still the SN tab keeps loading. I don't understand. Someone please help me:confused:
[Magisk] soder:
But now, when updated to 11.1 the SafetyNet failed, even if I toggle the Magisk Hide function in settings.

OPO with LOS14.1

/Söder
[Magisk] HamsterHam:
[MENTION=4470081]topjohnwu[/MENTION] tasker log.
[Magisk] Wesley_NL:
my usb debug is always activated maby thats why i have to do all these steps before i can pass safetynet ?
[Magisk] Wesley_NL:
oh i still have to toggle magisk hide after reboot, even in 11.1,, 1st 2 images after reboot, last 2 images after toggle magisk hide off/on
[Magisk] Selenia:
Stab in the dark here...are you using Magisk Viper4Android? I am running latest PureNexus on my 6P with latest ElementalX kernel. I repeatedly ran into the same problem as you whether updated from the app, installed it from a clean flash, or updated using my recovery. When I forgot to include the mod in my flashes, I suddenly booted successfully with 11.1. However when adding it after the fact, I ended up in a bootloop again. So I conclude that this version is incompatible with the mod in some way. I ended up rolling back to 10.2 because that's a deal-breaker for me. The main reason I use Magisk is to use Viper with selinux enforcing. I use SuperSU for actual root permissions. So for now I'll use the old version because it still works as good as ever.
[Magisk] photolarry:
As I have tried to communicate but nobody is listening to me since I guess they do not care if Android Pay works for them , The Superuser solution that is built into version 11 is not working fully! It is buggy and I recommend not using it. I did as was suggested when I got the update for the app (via play store) and let it update to version 4 (of the app not magisk itself). The app pretty much forces you to upgrade to v11. So a long story short, until he fixes it, I recommend rolling back to 10.2 and 3.1 of the app. And to be sure you get and keep root, flash the phh root he modified a few months ago (r266_2) zip. Once I was able to restore everything and not update the APP to 4, I was working with Android Pay again and everything seems fine.
[Magisk] GryphonBR:
C'mon, larry, the app doesn't force you to do squat; it's designed to work with the latest solution (provided by v11), so it's not that big a surprise that it won't work with previous versions. But I'm pretty sure that lashing out at people that are working rather pro bono towards the community doesn't quite seem like the best bet to get support for your issue, you know?
[Magisk] chhapil:
in Magisk 11.1 Magisk Hide is not working, it was working on 11 with toggle hack.

But now with 11.1 its not working at all. :(

Airwatch was happy on 11 but now it detects root on 11.1 and breaks

I'm on Mi5 with Nougat
[Magisk] Jsilver73:
Magisk 11.1 Android pay success :laugh:
[Magisk] dinoc:
I updated to Magiksk 11.1 and I keep receiving this notification, "#su binary needs update" or so.

But there is no option to update the su binaries. This is the superuser which comes with Magiksk I believe. Anyone know what is the deal with this update notification?
[Magisk] soder:
It's the SuperUser app that's no longer needed, since Magisk got a new root method. Just remove the old app.

/Söder
[Magisk] teddy0209:
Recommending users to use an older version won't help in the development... Most of the time, the problem is on the users side... If it's not then submit a proper bug report (a detailed one)...
[Magisk] de.er:
uninstall phh's superuser app
[Magisk] photolarry:
I was not asking for support any longer. I have the solution. Do not upgrade. However the new APP does require you to update to 4.0 and obviously it is designed to work with version 11. That is not the point here. The point is simply that inside the app store, play store, whichever you call it, there is a prompt to update as well as inside the APP of 4.0 to update to Magisk version 11. I am stating facts not lashing out at anyone. I was frustrated trying to get things working when they all of a sudden broke with an update that I expected would work. It does not work. Sorry his superuser solution has bugs and is not tested enough to suggest that every user update. I simply and trying to communicate to others having the issue as I had. And yes it is a big surprise that a new version that was just released has bugs and fails safety net/android pay. Again I lashed out at nobody. It is how your read it. Good night.

PS: I do not wish to submit a bug report as that is not my responsibility. I am not the developer of this project and really think things should be tested better before a mass release. My opinion.

---------- Post added at 03:39 AM ---------- Previous post was at 03:32 AM ----------

Sorry but it is not my responsibility to submit a bug report. I am posting it here. I am not a project programmer using GIT. Sorry but no thanks. He can test properly before releasing updates. And I sure can recommend using a functioning older version. Why should other users wishing Android Pay be frustrated too? And suggesting it is on "user side" when I am an advanced user, is rude and insulting. Obviously it is a bug and I am informing others. Period. You are more than welcome to submit a bug report but do not tell me to do so.
[Magisk] revanmj:
Since Play Store is used to distribute the app now, I think it would be a good idea to release new versions as a beta first. This way only people who are willing to test it and aware of the problems that may occur would test it before releasing new version to all, including those who just want Safety Net to pass and don't really care about underlying changes.
[Magisk] photolarry:
I think you should make it clearer that installing this new version will break Android Pay. I fully understand not wanting to take programming time to do this. But do not just release something and force users to upgrade (both within the app and within the play store) so that they are free to continue using version 10.2 with app 3.1 which still works for Android Pay without your root solution. If you want to put root into your project, please test it out first before releasing it to everyone and then like me they learn it breaks Android Pay and SafetyNet. Sorry but this the only solution out there currently that works. So please do not take away a functional version just because you wanna put all the root capabilities into your app. Fine to do that, but test it with Android Pay and SafetyNet before releasing it.

Agree with above that it should be a beta first before making it a full release. Simple solution.
[Magisk] teddy0209:
Well, sorry to say it man, but I don't have any problem on my end, therefore I have no bug to report... May I just remind you that this is xda... ?
[Magisk] photolarry:
Thrilling. Yea I know. I have been using Android since version 2 thanksverymuch. And I do not care if you are not having any problems. I took time to attempt to make the new version work with AP and could not. So I reported it and asked if anyone had this issue. That is done. please quit adding to this. I am going to bed.
[Magisk] DarkLanternX:
Seems like my ROM was the problem, I rolled back to RR 5.7.3 android mm. And installed magisk v10.2 and the safetynet gives the CTC error but can play Pokémon go
[Magisk] DarkLanternX:
Gonna update to v11 let's see if it works
[Magisk] teddy0209:
Someone just reported AP is working... ?
[Magisk] spetrie:
Upgraded to V11.1 and manager V4.1, AP working, SafetyNet working, all good again. ?

Sent from my ONEPLUS A3003
[Magisk] Ricardo89:
After update to magisk 11.1 i keep getting message after reboot that my su binaries are outdated. But I cant find how to update?
[Magisk] leolawliet:
My device has logging disabled at the moment my bad :p
[Magisk] crusader727:
if you search for "outdated" in this thread you will get the solution
[Magisk] Ricardo89:
Yes I did. But i have to delete the superuser app. But it came with viperone 5.3 on my HTC and is installed as a systemapp. How do di delete it?
[Magisk] znbaboy:
TD app mobile payment not working? (Canada)

Can someone please get MagiskHide working for the TD canada trust mobile payment app? It somehow still detects root and doesn't allow me to use tap to pay. Unfortunately its the only way for me to use tap and pay as android pay doesnt support my bank atm.
[Magisk] sugigu:
Leandroid not working

Hi, can you check Leandroid's setting? It's say get rooted but not have selinux permissive, how can I solve it?
[Magisk] crusader727:
if you are using the Magisk version wait for an update, you could disable the app meanwhile.

else delete the app using a filemanager/ recovery
[Magisk] andacro:
After I got V11 to work after installing Boeffla EOL kernel on my S5, V11.1 installed perfectly, with root, but the Saftey Check gives me the CTS error, as with earlier versions too. But! I'm a happy camper even though. :)

+ Forgot to add that I'm running stock with initd and deodex ([ROM][G900F][ALEXNDR] CQAV, BPE3 * DevBase v3.8).
[Magisk] flandy7:
After enabling "Busybox" in settings (Magisk 11.1 , Manager 4.1) and after reboot my phone is not starting. Dark screen and it's all!
[Magisk] crusader727:
report to Leandroid that Magisk is using pseudo-enforcing now.

try if you can enter leandroids settings when turning Magisk Hide off

You can try setting it to permissive using post-fs-data.d -> setenforce 0

https://xdaforums.com/apps/magisk/magisk-details-dummies-to-developers-t3473486

---------- Post added at 10:46 ---------- Previous post was at 10:45 ----------

/cache/magisk.log
[Magisk] Istvan_86:
Hello,

I have 2 devices OP 3T and Pixel C.

I updated Magisk to 11.1 and Magisk manager to 4.1 and all is working fine, including SafetyNet in my OP 3T. I post feedback for Pixel C when I have time to update it.

Really thanks for the amazing job here.

Cheers.
[Magisk] westeight:
Android Pay working.

Amex Pay working.

All UK banking apps working.

:good:
[Magisk] DarkLanternX:
No need to update anything, uninstall phh superuser its useless now, magisk handles the su from now on
[Magisk] tag68:
I'd like to help making it possible that Magisk runs on Moto Z Play stock unmodified. How can I help?

The problem:

The f2fs is broken. You know, that post in SuperSU thread with about 600 thank you, where 50 percent of the devices are concerned, because it was never recognized and everyone uses the broken version.

The f2fs is being used for /data in Moto Z Play.

For /Magisk (in case of Magisk) and for /su (in case of SuperSU) there is the loopback device being used on /data. Exactly this is broken and not working.

Only systemless root which runs fine is phh superuser. Neither SuperSU nor phh superuser topjohnwu are running. SuperSU in system mode does work fine.

I have no idea when Lenovo/Motorola is going to integrate the fix for f2fs.

Is there anything possible? Is it possible to use another partition like /cache for installation which is ext4 in case of Moto Z Play? Does a workaround exist without using the loopback device on /data?

I did not test Magisk in current version. Some other user did test 11.0 on Moto Z Play and wrote it had bootloop. Testing seems not to make sense currently.

Is it possible for a developer to format his data partition on another device (where the fix is not implemented, but that should be nearly all devices currently) using f2fs to reproduce the problem?
[Magisk] reis1996:
Pokemon go can't be found in the magisk hide menu. Can anyone help or is this an update by pokemon

If so please try to fix this in the next build
[Magisk] andacro:
I installed Busybox with the normal install in Busybox by Stephen (Stericson), and it boots fine.
[Magisk] Istvan_86:
Whith all updated and no phh SuperUser apk uninstalled, IDK if this is needed or not but Magisk handles SU petitions now, I find inside Magisk Hide the Pokemon Go marked to hide by default. Check screenshot.

Hope this helps you.
[Magisk] disthomuc:
On my Samsung Galaxy S3, safty net check is failing and also magisk hide. Any ideas?
[Magisk] DarkLanternX:
Updated to magisk v11, works perfectly

Pokemon go running on mm

Just have to find a way to make it work on android n

Thanks to topjohnwu
[Magisk] DarkLanternX:
Need more info , how did u install it? Tell me step by step, u might have done something wrong
[Magisk] danecr7:
Hi guys,

Maybe someone here can help me, I'm getting an error while flashing version 11.1 it says Unable to restore RAMDISK.
[Magisk] Jsilver73:
Uninstall phh superuser manager from your app drawer
[Magisk] Didgeridoohan:
If you check the thread you'll see that Android Pay has been reported as working with Magisk v11.1 and Manager 4.1 by several users. Your problem is either device or user related...

If you are an advanced user as you say, at least provide something constructive and not just negativity and hostility, because that's how you're coming across with these posts right now. If you're an advanced user you could easily provide some logs, logcats and details about the issue you are experiencing. It takes a few minutes and can help the developer immensely if there's an actual problem. But, instead you choose this...
[Magisk] Jenanga:
Pokémon thread or what? :laugh:
[Magisk] Didgeridoohan:
Sorry mate, I'm not sure. Your Magisk log looks fine and I'm gonna guess a recovery log from installation wouldn't show much either, but maybe you could upload one anyway, just in case. Could just be a general incompatibility with your device and/or kernel and later versions of Magisk (v9 worked for you, right?). Topjohnwu said the next step would be trying to get compatibility with as many devices as possible, so there's at least that...

Edit: Have you tried changing kernel?
[Magisk] FlintStoned-:
Hi guys,

Since I'm on Magisk 11 and 11.1 I get reboots when I plug in my phone into a magnetic charging dock and when I take it back out.

I'm on: Sony Xperia Z3 compact, AOXP ROM 1.5.7 with EliteKernel and Magisk v11.1

Any thoughts on this?
[Magisk] Didgeridoohan:
Have you guys tried/checked these:

-Make sure there are no remnants of previous root

-Disable USB debugging

-Xposed cannot be installed/active

-Try a custom kernel (stock Samsung kernel is not compatible with Magisk Hide)

A recovery log from the installation would be very useful when troubleshooting.
[Magisk] yoesazel:
Is the latest version magisk already included super user? So i dont need installing phh super user? Any one help me... Please... Thanks
[Magisk] yoesazel:
Ok... Thanks for your respone... I used magisk with RR rom Nougat. Is work fine for me... And i use subtratum for theme too...
[Magisk] Didgeridoohan:
Working fine on Nougat (7.1.1) based ROM here. Check a couple of posts up for a few tips on what to check for if SN doesn't pass.
[Magisk] disthomuc:
I have lineageos latest build installed and flashed magisk 11.1 thru twrp. I installed the latest Manager from playstore and configured it thru the app.

On my oneplus with identical setup it is working perfectly fine
[Magisk] reis1996:
Thanks for your reply but pokemon doesn't appear in my list

I'm using magisk v11.1

App version 4.0
[Magisk] Istvan_86:
You should update Magisk Manager app through play store.

Try it and tell us.
[Magisk] Enismirdal:
MagiskSU seems to be incompatible with Toggle Network Type 5.0 by cygery, and acts oddly with Apps2SD by vickybonick.

With Apps2SD, on boot it displays both superuser granted and denied toasts, despite being set to grant su to Apps2SD, and displays the same behavior if MagiskSU is set to grant all requests. So far, with my limited testing, Apps2SD still seems to function, but this is undesirable, or at least rather unclear, behavior.

Cross-posting the Toggle Network Type bug report:

Issue/incompatibility report:

2015 Moto X Pure (clark) XT1575

Android 6.0.1 (Dirty Unicorns 10.6)

Toggle Network Type 5.0 1.1.6.0

Magisk/MagiskSU 11.1

SELinux enforcing

MagiskSU toast confirms SU granted on boot and on periodic widget update.

Toggle Network Type displays error toast:

"Can't change preferred network type. Is your device rooted?

Error -2: Command "service" not found"

Widget displays "Error"

Toggle Network Type requires the su binary to support -cn.
[Magisk] reis1996:
Thanks for that

Yes pokemon has appeared but after installing magisk 11 (I updated to 11.1 now) all my hw buttons don't respond

I'm on lineage using a galaxy note 2
[Magisk] bmg1001:
I was having an issue where Magisk 4.1 was showing that I had everything working, but after awhile it said I wasn't rooted, yet the apps that have already been granted root (and a few that haven't) were able to request it just fine.

I tried many things from reinstalling to uninstalling using the zip and reinstalling with no modules and I kept getting the same issue. I just reflashed the ROM, keeping data, and it looks like it might work now, but I wouldn't be surprised if I opened Magisk while typing this and it stopped working....Eh still working. SafetyNet always worked though.

I'm on a Nexus 6P with Dark ROM (based off Lineage) and Flash Kernel with F2FS on data and cache. I would post a log but considering that the issue I'm having causes Magisk to not be able to load the log, I don't know what to do, but for now it seems to be fixed. If it messes up again, I'll probably do a clean flash of everything or maybe do a "semi-wipe" to EXT4.
[Magisk] Didgeridoohan:
Ha! Someone got in between and I didn't realise it was you I had already answered...
[Magisk] Fild5x:
Eventually installed magisk 11.1. However, am still trying to see why exposed won't work normally. See attachment.
[Magisk] reis1996:
Toggle it by pressing the button in the top right corner of that attachment
[Magisk] DarkLanternX:
Bugs in ROM maybe, I had similar problem too, a clean install will do the job, take a nandroid backup ofc, or uninstall magisk , and flash the v10.2 first, update the magisk manager and then update the zip through it. Don't flash with twrp. Hope that works :fingers-crossed:
[Magisk] gr8st:
I hope it's not a damaged mag port but it's known to happen with our device. Is it jutting out at all when you touch it?

If not, have you seen this guide? Might be corrupted install and worth going over to ensure no left over files.

Bit of a side note, but have you tested safety net and android pay yet? I plan to have the same setup soon so I was curious if it worked. You have to:

Open magisk manager

Enable magisk hide

Test safetynet

Reboot, test safetynet again

I have older setup with elite kernel, phh suhide, and system less xposed but still couldn't get it working so I'm hoping things changed.
[Magisk] Istvan_86:
Yeah, you should use Magisk 11.1 + Magisk Manager 4.1 no phh superuser apk needed. Glad that I can help you with Magisk and PoGo but sadly I can´t offer help for your HW buttons.....
[Magisk] Kyleh46:
When I update to 11 or 11.1 on my Note5, it returns and says that no Magisk is installed and asks me to redownload it. I'm guessing this is due to the magisk hide not playing nice with Samsung devices but some clarification would be appreciated. Thanks.
[Magisk] DarkLanternX:
That's the only need for me to bypass safety net, cuz m not so stupid to root and screw my official phone and cry for android pay. Peace out✌
[Magisk] kinfam:
Yes this is true, however because I use other mods such as H202 and custom kernels, I find taking the extra minute to clean flash Rom > root solution > mods > kernel to get a "fresh start" helps me narrow down possible issues if I come across them. Habit of an old SQA I suppose :)
[Magisk] afuller42:
Try

http://xdaforums.com/htc-10/themes/mod-viper4android-fx-viper10-t3541684/post70916704

Fixed it for me

[MENTION=3144884]Selenia[/MENTION] also
[Magisk] Fild5x:
Same situation
[Magisk] DarkLanternX:
Do a fresh install , don't flash v11 directly through recovery. Some mentioned that before and had this same issue.

Flash v10.2 zip and get the v3 manager, google for it

Download phh superuser

Enable magiskhide

Check SN

Update the manager through play store

Update when prompted or go to the install section

Magiskify
[Magisk] Captain_Throwback:
[MENTION=2296129]photolarry[/MENTION]

I'm sorry that you're having issues using the latest version of Magisk on your device. However you saying that it's "not your responsibility" to provide a log is incorrect. [MENTION=4470081]topjohnwu[/MENTION] only has a finite number of devices (and not that many - it's not as if he's getting paid to work on this), so he can't predict every device and setup that's out there and make sure it works perfectly for everyone. He has to depend on user feedback (especially logs) in order to figure out what's wrong in people's specific situations, and determine if there's something inherently wrong in the code and fix it. He performs thorough testing, as do I, on multiple devices, but that doesn't mean everyone will have success. Remember, this is a developer's forum, so we all need to collaborate together to help develop software that works universally. How do you expect him to fix an issue he doesn't have without a log? Just because it works on a previous version and doesn't work now doesn't automatically tell him what the issue is. We need more information, and that's where the logs come in to play.

If you're unwilling to help make the latest version of app compatible with your setup, that's fine. But don't come in here posting that you don't need to post a log; the developer asks you to post a log if you have issues. So either keep your problems to yourself or help be part of the solution.

Remember, some devices aren't supported at all (like the Pixels) so at least your device is at least partially supported. So please contribute to the ongoing compatibility of Magisk by participating in its development. Or don't, but don't tell others not to. Or even better - donate a device to the dev so he can experience your issue first hand and fix it directly ;).
[Magisk] teddy0209:
Yup, that is a good practice... Gladly all the mods I use are all systemless now...
[Magisk] biggdevon:
Had no issues updating from 10.2, 3.1 to 11,4 and then 11.1, 4.1. Running stock 6.0.1 with arter97's kernel. SafetyNet passing but not Android Pay. PoGo works fine

SM-N920T
[Magisk] Captain_Throwback:
First try the latest version (11.1) with the latest Manager and confirm that it's still not working. Also try disabling USB Debugging, as that seems to be an issue on some devices. If that doesn't work after enabling Magisk Hide in the new app and rebooting, then yes, maybe a logcat would be helpful, along with a magisk log with the advanced logging options enabled.
[Magisk] biggdevon:
I've got a successful install/upgrade on stock rom with custom kernel and all green in Magisk manager but no luck with AP. Can someone comb through my log on the off chance there's something obvious I'm missing? If it all checks out I'm going back to stock for a fresh start from scratch, maybe try a different kernel.