yashsingh1/xdaforums huggingface dataset:
[Magisk] Tangib1e:
Hm .... is it just me, or is the most recent Magisk completely broken? First of all, I tried:

1) Downloading (on a separate phone; let's call it my firewall phone, one that's never used for anything but downloading stuff) and patching the boot image; Magisk writes a 0-byte "patched_boot.img" file. I appreciate how smaller files are quicker to flash, but you may have taken it a step too far.

2) Letting Magisk Manager update itself (on the actual phone I use every day) and then having it download the 18.0 version of Magisk; allowing it to patch the running image. After choosing reboot, the phone is no longer rooted. The Magisk "update" has somehow uninstalled itself.

So that's twice on two different phones I'm seeing this. I found it noteworthy that this fail-state was reached on two different phones without any error messages from Magisk Manager itself. It seems to be thinking it's managing to do things that it demonstrably isn't managing to do. I remember being puzzled by how Magisk Manager would just silently fail to do anything useful unless it was able to get an Internet connection (so to those who like to root their phones BEFORE going online for the first time, there's no way to do so but also no notification provided) and I've now watched Magisk not only fail to update itself, but failing so badly that it actually somehow uninstalled itself or left behind an unworkable install, but without providing an error message so as to allow people to take corrective action before the reboot (in other words; fix the damage while they still had root).

I'm sure I'll get things worked out eventually, but my experience with the latest release seems to offer up a lot of late onset friction.
[Magisk] martyfender:
Did you try 256k or 1 meg? I'm not sure, but a reboot may be needed after changing this.
[Magisk] csrow:
It was originally set at 256k. I tried 64k as suggested in the thread. I did reboot after the change and the results were random.

I'm going to remain at 17.3 until the things sort out. It seems like it's better to wait on a major upgrade for a while because I also had problems with 17.0 update.
[Magisk] jenslody:
Did you try a clean install of v18 or latest canary ?
[Magisk] Tangib1e:
By the way ... how does one do this? I find that Magisk Manager is proffering updates as soon as they are available and actually refuses to operate without the latest files. Magisk Manager doesn't want to run on a phone that hasn't connected to the Internet, and once it has, Magisk Manager refuses to do anything until everything has been updated to the latest versions, at which point, things no longer work. How would you try to get 17.3 to work presently?
[Magisk] Hippie459MN:
Im using 17.3 still and it works just fine, with and without internet. I am using the latest Magisk Manager as well with 17.3. Magisk Manager does offer me updates but I just click "No Thank You". I did update to v18.0 but it slowed my phone down so bad. Not sure if it was v18 that cause it specifically or not but going back to 17.3 seemed to take care of it.

Maybe do a complete uninstall and than reinstall 17.3.
[Magisk] InsaneNutter:
Is anyone having the problem of Safteynet failing after a few hours?

I have a OnePlus 5T running LinageOS 15.1, before updating to 18.0 I never had any issues at all.

The only modules I have installed are MagiskHide Props Config and Emoji One.
[Magisk] jcmm11:
I haven't looked at the logs but how are you modifying system?

In TWRP? Via Magisk modules? Or just trying to use a root explorer and change it directly?

If the last - don't! Either of the first 2 methods I mentioned should work though. Using Magisk modules gives you more flexibility.
[Magisk] Deses:
Hi again! I did more testing and found something interesting...

First I factory reset my OP3T and installed the offending app. Working.

Install Magisk, Repackage it and MagiskHide the Bankinter app. Working.

Install and apply AdAway. Working.

Install App Systemizer Magisk Module. Working.

Install YouTube Vanced Magisk Module. Root Detected.

Remove Vanced Module and clear Bankinter's app data. Working again.

Same with greenify4Magisk. It starts detecting root when that module is installed. If i remove it, it lets me in again.

I guess that if Magisk can't hide its own modules... I'll have to make do without that bloody banking app.
[Magisk] panchogg:
It's happens again
[Magisk] an-_-dro:
with flashable zip and direct file explorer no different. always have that error everytime modifying system (debloating, replacing xml also will trigger this). this is some kind of protection inside kernel i gezz..
[Magisk] csrow:
Download a copy of 17.3

From the Magisk manager click "install" and then "restore image". Do not reboot.

Jump into TWRP recovery and install 17.3

Reboot.
[Magisk] candiesdoodle:
Those loosing root/ failing SN intermittently please do a clean install of v18.

It helped me - I had same issue when I upgraded via twrl from 17.3 to 18

Then I rolled back and used the "patch boot image" method.

Then just flashed the patched boot img in twrp. Had to disable and re-enable magiakhide... But it has stuck since then. No issues so far.
[Magisk] xunholyx:
It's something on your side, not Magisk's. I have Vanced and I'm not getting problems with my bank payment app.

That is on a Pixel 2XL though
[Magisk] spicediablo:
Safety net verification failure after fresh installing magisk 18. It was working initially but after some time, verification failure.... Anybody faced this?

Sent from Sagit
[Magisk] tripLr:
bootloop with 18

T710 lineageos bootloop upon upgrade from 17.x to 81
[Magisk] mayur.3.92:
Can confirm same, looks like history is repeating itself :rolleyes:
[Magisk] pero.mikic:
v18 SIM CARD and GPS problems

I have two Cubot Dinosaur. Only for playing and for this, they are great. With v18 the phones didn´t recognize the SIM card anymore and GPS didn´t work. First I was thinking, the mobile phones are damaged but than I go back to 17.1 and everything works fine again. Anyone the same problem?
[Magisk] Minotaur:
Suddenly getting no response from Magisk... the manager claims it's not installed (v18) and apps that need root aren't getting it. Tried reflashing the 18.0 zip file from twrp to no effect.
[Magisk] pranavpmanoj:
Is your Magisk Manager hidden?
[Magisk] Minotaur:
It is actually... I rolled back to 17.3 and the option to restore Magisk Manager is there
[Magisk] pranavpmanoj:
Restore it and then try upgrading.
[Magisk] Didgeridoohan:
I did another quick test and can confirm your findings, partly. The app in question does not react to Vanced when I tested, but if I have Greenify installed it does refuse to start, regardless if I install it regularly from the Play Store or by Greenify4Magisk. The bank likely has Greenify on their blacklist as an app that tells if your device is rooted or not (if you can't find root, look for the signs of root). There's nothing Magisk can do about that...
[Magisk] vipklaus:
Hdfc bank app not working after root...... I have already hide it from magisk manager..... Still not working..... Plz help......
[Magisk] chooks06:
Just a wild thought..

Is it possible that sudohide can hide greenify from the banking app?
[Magisk] Harlock1978:
Since I installed Magisk 18 all the app that were chosen in Magiskhide are not working anymore they are stuck on the opening screen and they close. If you open the menu to close the app in background these apps don't appear.

When I deactivate Magiskhide for them they are working again. From Magisk 15 until 17 I haven't had this problem.

The apps involved are may bank app and the app to check the train timetable and by ticket of Swiss
[Magisk] candiesdoodle:
Working for me

1. Disable and enable magiakhide

2. Hide magisk manager itself
[Magisk] mspasov:
Same here
[Magisk] rptb1:
Fairphone 2 with LineageOS+microG. Installing Magisk 18.0 in TWRP reports success, but does not install Manager. Installing Manager 6.1.0 separately (either before or after Magisk), it does not believe Magisk is installed. Any idea what to try?
[Magisk] Pkt_Lnt:
The Magisk Trouble Shooting Guide has many good ideas.

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] rptb1:
In my case, moving Magisk Manager from adopted to internal storage made it work.
[Magisk] Pkt_Lnt:
I really like when someone learns something new and solves it themselves. :good: :cool: :good:
[Magisk] Badger50:
Lord knows that's a tall order in and of itself for us old farts! :laugh:
[Magisk] GiBraiNe:
I have the same issue in my Essential PH1 latest android update but only one of 5 bank apps I use is not working (Citibanamex, a Mexican bank). Your workaround disabling the app in the magisk hide list works for me too (the app works but detects root).

I found out that if I disable my modules in magisk (pix3lify and lawnstep need to disable both, I also use substratum but that one can be enabled) the bank app works and does not recognize root successfully, mentioning it in case this helps to find root cause too.
[Magisk] Fallenwitcher:
I have the same problem. Magisk says: ctsProfile: False and Google Pay don't work. Also my Banking App detects root.

I flashed today the latest Los 15 build and the crt false error is till there after flashing magisk 18. The same error is also with 17.4...
[Magisk] Sutcliffe9:
Had to go back to to 17.1 as safetynet doesn't work in 18.?
[Magisk] Invisan:
So maybe someone here as the idea i need. I would like to install Magisk. I extracted the boot.img from the Payload.bin from and Update file. When trying to patch it with Magisk Manager i get the Message No boot Image magic found!

Link to the Google Drive Folder with the Boot.img and the Magisk Log are attached.

Guess there might be a Problem with the Img. So i also put the original Update File with the Payload.bin in the Folder as well.

Maybe someone is able to figure out whats the Problem.

https://drive.google.com/open?id=1THn6V0C3UW_qaqhkaLavldZzXuK3u74q

Kind Regards,

Invi
[Magisk] harshizle:
I'm trying to do the same but can't quite figure out how to go back to 17.4 or earlier. I've looked through the thread to no avail really. I'd appreciate it tremendously if you could link me to something that explains how to do so. Thanks!
[Magisk] pranavpmanoj:
Just download the flashable zip from here and flash via TWRP. It'll replace 18.
[Magisk] Ibuprophen:
I believe that the guidance to Downgrade, on the following post, still applies...

https://xdaforums.com/showthread.php?p=75710888

Though I could be wrong.

Good Luck!

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Commodore VIC-20.
[Magisk] slugsly:
I don't think this is true since I am running 0.37.1 and Magisk.
[Magisk] pharmdeon:
I do not think that this is true:confused: ... I am on 0.37.1 and Magisk and it is working perfectly fine (except for the update being a little buggy occasionally).
[Magisk] Triviox:
But, do you have xposed framework active? The problem is when you have xposed too.-
[Magisk] pharmdeon:
No I do not, but they stated it is detecting Magisk ... I do not think that is true (detecting Xposed as been stated many times)
[Magisk] bttcp12:
You are right. As some people has already stated it's xposed's fault. The last safetynet iteration detects Systemless Xposed, so if you have xposed installed and enabled PoGo 0.37.1 doesn't work.

For the time being people can disable Systemless Xposed in the app and reboot. Everything with Safetynet works ok that way.
[Magisk] 4RK4N:
cant confirm that either. been running 0.37.1 for 3 days til today arround lunch time. safetynet helper and safetynet playground both reported failure as of then. both successful before.

will try 0.37 and report back.

edit: 0.37.0 also is logging in forever. so nope. not working. its safetynet not the game. if 0.35 would have safetynet enabled it also wouldnt work
[Magisk] hammerhead2:
Affirmative.

0.37.1 here, on N910C, with magisk and phh su. I had an "authettication issue" today, and finally removed xposed. After this, the game runs smoothly.
[Magisk] JudgeDread11:
Do you know why your SE Linux is permissive?

Also try the same as your first attempt but clear dalvic and cache before you flash, not after. Or not at all.
[Magisk] Xerlan:
Hello,i tried,after a clean installation to disable Xposed and run pokemon go but it didn't work,my Selinux is setted on Permissive and i'm trying tu run it on my Note 3 N9005 With Phronesis ROM 6.5 (updated android 5.1.1),what can i do to run correctly Pokemon go?Thank you
[Magisk] AsturzioAugias:
I tried to downgrade pokèmon go to version 0.37.0, still not working with xposed active. With xposed disabled PoGo working, but safetyNet test fails
[Magisk] Triviox:
Same here; 0.37.1 and 0.37.0 dont work if xposed active. I'll back to 0.35 again, and wait for a fix :D
[Magisk] Äptiva:
Xposed is going to cause the fail. In on 0.37.1 and have no issues
[Magisk] origitat:
Can confirm. Had to disable xposed as well to get in. All is good now but This makes me worried.
[Magisk] macschwag14:
I'm new to Magisk and had a few questions that I didn't see in the FAQ.

1) Once I've installed Magisk on my stock-based custom rom following the directions, can I then flash custom kernels or does that trip SafetyNet? If it's only stock, I assume I cannot use the custom kernel baked into the rom, correct?

2) I saw that there is a Viper4Android Magisk module. Does this this mean that I cannot flash the non-Magisk version of Viper4Android because it will trip SafetyNet? If flashing the non-Magisk version is OK, is it also OK to install Viper4Android audio profiles or should I just use the program without profiles?
[Magisk] Kiid:
1. Flash the kernel before Magisk. That's in the directions in the OP

2. In my experience flashing the non-magisk version of V4A results in SafetyNet tripping, probably due to it altering /system in some way. Also the Magisk V4A doesn't work for everyone (ie: drivers not installed or no processing) though some have found fixes. You'll have to search this thread.
[Magisk] Galaxy Y User:
Sorry for my ignorance, but to install Magisk I need to:

- Revert to stock rom with stock boot image with no root

- Get CWM or TWRP to flash Magisk

- Flash Magisk installer and install Magisk manager apk

- To get root: flash phh root and install apk from playstore

Does Magisk come included with root and we can control it with Magisk manager, or do we have to flash other root like phh or SuperSu
[Magisk] 4RK4N:
magisk is a framework for systemless modifications like root. it has no root or anything like it included.

magisk modules are for that. using magisk framework. like phh's root zip.

so u need to flash phh's root zip after flashing magisk to have root.

with magisk manager apk u can turn root on and off on the fly. thats why u did all the zip flashing ^^

edit: u still need phh's superuser app from playstore to grant root access to apps. quite the same as with supersu's popup
[Magisk] westeight:
Just restored my beloved HTC M8 back to 100% Stock.

Now Android Pay will DEFINITELY work ... ;)
[Magisk] TheSaiyan:
Really? Almost every reply was answered except mine. I'm asking for help with the "unable to detect boot image" issue. I followed the instructions as they are in the OP, can't install Magisk. Nothing in google, nothing here. What do I have to do to get this working?????
[Magisk] Captain_Throwback:
Wait for v7. If it doesn't work after that, then post again.
[Magisk] tripLr:
Magisk should tell you where the backup is when its installed.
[Magisk] Annihlist:
Yes I have safetynet intermittent issues with v18. Using a Pixel 2 Xl. Had to roll back to 17.3 because Google Pay was borking. A reboot fixed it and then sporadically safetynet didn't pass after a while.
[Magisk] Fallenwitcher:
Switching back to 17.1 does not work for me. The cts error is still there. How can I fix it?

Heres the Magisk log.

08-12 23:58:01.378 736 736 I Magisk : ** Initializing Magisk
08-12 23:58:01.380 736 736 I Magisk : * Creating /sbin overlay
08-12 23:58:01.385 736 736 I Magisk : * Mounting mirrors
08-12 23:58:01.386 736 736 I Magisk : mount: /sbin/.core/mirror/system
08-12 23:58:01.386 736 736 I Magisk : link: /sbin/.core/mirror/vendor
08-12 23:58:01.387 736 736 I Magisk : bind_mount: /sbin/.core/mirror/bin
08-12 23:58:01.387 736 736 I Magisk : * Setting up internal busybox
08-12 23:58:01.478 743 743 I Magisk : Magisk v17.1(17100) logger started
08-12 23:58:01.478 739 739 I Magisk : Magisk v17.1(17100) daemon started
08-12 23:58:01.482 739 745 I Magisk : ** post-fs-data mode running
08-12 23:58:01.482 739 745 I Magisk : Create /data/adb/magisk.img with size 64M
08-12 23:58:01.538 739 745 I Magisk : * Mounting /data/adb/magisk.img
08-12 23:58:01.778 739 745 I Magisk : * Running post-fs-data.d scripts
08-12 23:58:01.778 739 745 I Magisk : * Running module post-fs-data scripts
08-12 23:58:01.778 739 745 I Magisk : * Loading modules
08-12 23:58:01.782 739 761 I Magisk : * Starting MagiskHide
08-12 23:58:01.782 739 761 I Magisk : hide_utils: Hiding sensitive props
08-12 23:58:01.782 739 761 I Magisk : hide_list add: [com.google.android.gms.unstable]
08-12 23:58:02.934 739 821 I Magisk : ** late_start service mode running
08-12 23:58:02.935 739 821 I Magisk : * Running service.d scripts
08-12 23:58:02.935 739 821 I Magisk : * Running module service scripts
12-13 06:15:44.442 4704 4704 E Magisk : readlink /proc/4651/cwd failed with 2: No such file or directory
12-13 06:15:44.445 4704 4704 E Magisk : write failed with 32: Broken pipe
12-13 06:15:52.718 4780 4780 E Magisk : resetprop: Initialize error
12-13 06:15:58.170 739 761 I Magisk : proc_monitor: com.google.android.gms.unstable
12-13 06:16:38.986 7990 7990 E Magisk : resetprop: Initialize error
[Magisk] spawnlives:
Sorry for the delay

Since this is a twrp issue and not to clutter up magisk thread with off topic issues I have start a new thread in your s7 device forum in Q&A section to better help you out. Called twrp issue

Link below

https://xdaforums.com/galaxy-s7/help/twrp-issue-t3878565
[Magisk] spambayes:
Lost Root after upgrading to v18.0

I'm having huge problems after updating to Magisk v18.0 and Magisk Manager v6.1.0.

Coming from Magisk v17.3 and Magisk Manager v.6.0.1, I did the upgrade through the Manager. The upgrade installation of both Magisk and Manager happened without any errors. Upon reboot, the first sign of trouble came when I tried to turn on Systemless Hosts in Adaway. Adaway froze and I had to force stop it. I attempted a few more times which resulted in the same outcome.

At this point I noticed that some root-enabled apps were not working properly, eg., the file manager could not read the external SD Card. I rebooted the phone and then used a root checker which could not find any evidence of root even though Magisk Manager appeared to be working and the Superuser list was populated with root apps. At the same time, new root apps do not trigger any superuser requests.

After another reboot, I checked with the root checker and it still could not detect root. Decided to revert to Magisk v17.3 and Manager v6.0.1. I uninstalled with the "Complete Uninstall" option in Manager and rebooted. Then rebooted again to TWRP and flashed v17.3 with no errors. Rebooted and installed Manager v.6.0.1.

However, root checker still does not detect root and root apps still fail to trigger superuser requests. Existing root apps no longer work and now the phone will not power off or reboot from the long-press power button menu. It will hang after reboot or power off option is chosen. The only way to reboot is to use the 3-button-press (Power+Menu+ Vol Up/Down).

I'm not sure what happened. Can anyone help?

Thanks.
[Magisk] Pkt_Lnt:
What is really needed to find out what is actually happening on the inside is logs. Think of it like getting an X-Ray, we cannot see what is broken inside from the outside, but logs can show it. Here is a guide: Asking for help/reporting bugs
[Magisk] xtremesystems:
i suppose it's known issue. i have performance problem on redmi note 5 [xiaomi.eu rom] rooted with magisk 18 [magisk manager 6.10]

Wysłane z mojego Redmi Note 5 przy użyciu Tapatalka
[Magisk] elimiriel:
Sorry I've already do rollback before log collecting, but I report issue here. On HTC 10, app+theme installation tasks, roots, and after-boot autostarting of apps(like LMT, Helix Engine) are stuck before erase all data of Google Play after each boot.

+After back to 18.0 with dirty rollack and install, I collected logs. Magisk log is clean, so I attach logcat to you. around 20:08, I did erasing data of Google Play.

I've discovered the origin. Not by magisk 18 itself, by one of modules I use.
[Magisk] Evilmonk100:
can i install magisk version 18 on magisk version 16 directly? or need to uninstall first v16 then reinstall v18? and for uninstallation of magisk v16 can i use latest uninstallation zip? plz reply.
[Magisk] Strephon Alkhalikoi:
Install it right on top of 16. No need to uninstall first, unless you want to.
[Magisk] beatschubser:
Has anyone managed to use Google Pay connected to PayPal? When I try to pay with it, my phone vibrates, but the terminals always say "Card not recognized".
[Magisk] LinuxNewb:
Magisk Hide no longer working for app in v18.0

[MENTION=4470081]topjohnwu[/MENTION] Recently upgraded from Magisk v17.1 to 18.0 on my Pixel2 and now a certain app I use daily, PingID, is no longer working with Magisk Hide.

In 17.1 after I hid prod.com.pingidentity.pingid the SU Access Denied toast message would not appear & I could properly authenticate, on both my OnePlus 5T & Pixel2

Now with 18.0 I am getting the SU Access Denied toast message (log snippet as example since the app blocks screeenshots) and Pixie was blocked since root was detected.

Please let me know if you'd like the logcat or if there's anything else I can do to help.
[Magisk] Spartacus500:
[MENTION=2764562]LinuxNewb[/MENTION]

v18 S7 Edge look
[Magisk] LinuxNewb:
Do you have a paired device already?

I cleared app data, uninstalled, re-installed and still get the Denied toast notification, which at one point kept spamming, and I had to force close the PingID app.

Android 9

Dec 5 '18 Security patch

Kirisakura Kernel 4.5.9

PS. Installed the RootBeer Sample app and it detected root even hidden. Did SafetyNet check in Magisk and it's failing both.

PPS. Ended up just restarting the phone and now it's passing SafetyNet in Magisk, RootBeer Sample, and PingID... Really odd behaviour!

PingID implements another check when authenticating to see if any display/lighting mods (f.lux, Pixel Off, etc...) are being used. I'm wondering if Magisk somehow got exposed, tripped, and led to the issue.
[Magisk] Angyone1:
Hello guys, magisk 18 working very well but I have a problem with the coin pop app... I hide it but the app show me a warning and then when I press ok the app stop working... Anyone know how fix it ? Thank you very much guys !
[Magisk] fast9000:
I just recently installed the PRESTO beta apk it's essentially a metro pass for subways and trains. The app used to crash on startup until I used magisk hide to hide the app but now it won't let me log in using my credentials. They're attempting to block rooted users from using the app anything else that I could do in magisk hide to make it work?
[Magisk] mrspeccy:
Hi,

I have an app that crashes despite being hidden in Magisk Hide; Magisk Manager is hidden too, Magisk 18.0. Logs reveal that the app crashes soon after the following warning:

type=1400 audit(0.0:9100): avc: denied { read } for name="enforce" dev="selinuxfs" ino=4 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:selinuxfs:s0 tclass=file permissive=0

So roughly the app tries to read selinux and seems to interpret the result as existence of Magisk. Can you help with a more thorough interpretation?
[Magisk] GradiusBR:
On last two days, pokemon go detect magisk and say incompatible device.

I tried to restore my phone to stockrom, re-root, install magisk 18, set magisk hide to pokemon but no success.

Game only works if uninstall Magisk Manager.

Also try to rollback to Magisk 16, with same effect, pokemon go detects Magisk Manager and no load game.