yashsingh1/xdaforums huggingface dataset:
[Magisk] dahawthorne:
"Not trusting" is too strong a way of putting it. It has worked for me in the past, but has also failed, so I prefer to have control over the new version by seeing exactly what it's doing so that I know how to fix whatever may go wrong.
[Magisk] theapuv:
After upgrading to magisk 18 saftey net check failed and magisk hide is not working anymore. Tried the troubleshooting tips in magisk wiki nothing worked. So I uninstalled magisk to roll back to 17.1 but was stuck at boot logo. Can not even get in to twrp recovery now. My device is lg v20.
[Magisk] chooks06:
I have a device on stock ROM. Using the recommended installation mode from MM always fails to update the version. Then I have to use the uninstaller and flash the zip via TWRP, then reauthorize all Root requests.

However, on another device running Lineage 15.1 (unofficial), no problem at all updating from the manager (after it was updated).

I guess different results require different methods.

Though I trust that it should work, I always have a habit of doing a full backup so that I can recover in case any issues crop up - that's my main reason for having a custom recovery.

Have a great weekend!
[Magisk] Mycroft2046:
I wasn't able to see the download button. I rebooted, reinstalled magisk manager, and rebooted again, and now it's fixed.
[Magisk] curiousrom:
I updated to Magisk v18 from v17.3 on haggertk's S5 G900M klte unofficial 16.0 Beta Build 2018-12-03 via updated Magisk Manager 6.1.0 & after success it offers to save the installation log which I attached to this post so you can see exactly what it did so that's one less reason for not using it. ;)

***
[Magisk] fed_xD:
I have a delay in root permission detection Since 17.3 on Miui 10 , in ver 18 , have a delay on detection too , ver 17.1 is working fine
[Magisk] ivocoelho:
Hey guys I tried updating magisk v18.0 and now the safety net is showing as false .. how to solve this issue??
[Magisk] IODroids:
PLease make a new topic for users from 18.x onwards. installations..

Tooo large topic.
[Magisk] Mischa42:
1+ on S8+ with CarHD Rom v21
[Magisk] ktmom:
Start with the troubleshooting guide linked in the 1st post of the release thread.

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
[Magisk] 20mark:
Same. OnePlus6.
[Magisk] theapuv:
I too had this problem. Also apps were detecting root with magisk hide on. I tried the troubleshooting tips n magisk wiki but it didnt worked. I uninstalled magisk 18 which resulted in my phone stuck at boot logo. Even recovery was not accessible. Had to flash stock rom again and installed magisk 17.1. Now everythig works including saftey net.
[Magisk] Adiker:
Does the latest build work with Fortnite ? I'm rocking 17.4 Canary build and Fortnite runs without a problem, but what about 18.0 ?
[Magisk] ivocoelho:
So what's the solution to that prob??
[Magisk] theapuv:
Better you not update. I dont use Fortnite. But my banking apps were able to detect root and exited after update to 18.0
[Magisk] Joangarc:
Same Samsung S8+
[Magisk] bmg002:
I just got into Oreo recently with miui 10 and updated to magisk version 18 and now magisk hide is not working anymore. I did a root check with root checker and it finds su even though root checker is in magisk hide.

Edit - if I setup and restart magisk hide then root checker stupid finding sure.
[Magisk] LinoX:
Error patching boot image with Magisk manager 6.1 and magisk 18.0.18000

Log below:

Direct install instead works.

File to patch is boot.img.lz4 (G950F-CRK1 kernel)
[Magisk] Nimueh:
Letting Magisk Manager update itself and then install the new update worked flawlessly on all 3 of my devices:

Honor View 10, Resurrection Remix Oreo

Samsung Galaxy Tab A 10.1, Resurrection Remix Oreo

Beelink Mini MXIII S905X TV box, Stock Marshmallow

All 3 still booting and functioning "within specified parameters" :victory: :good:

Thank you [MENTION=4470081]topjohnwu[/MENTION] :)
[Magisk] Deses:
Almost 3 months after jcmm11 replied, and after updating to 18.0 and testing the banking app again to no success, I got around getting logs.

I downloaded the latest canary apk and zip, intalled both and changed the distribution channel to canary in the settings and then I began testing to generate enough logs. I also recorded a video showing all the steps I did just in case you want to reproduce exactly what I did. https://www.youtube.com/watch?v=otswMq5bq_k

The offending app is com.bankinter.bkwallet. https://play.google.com/store/apps/details?id=com.bankinter.bkwallet

12-08 15:39:41.645 880 12075 I Magisk : hide_list rm: [com.bankinter.bkwallet]
12-08 15:39:43.140 880 12078 I Magisk : hide_list add: [com.bankinter.bkwallet]
12-08 15:39:44.759 12086 12086 D Magisk : hide_daemon: handling pid=[12080]
12-08 15:39:44.760 12086 12086 D Magisk : hide_utils: Cleaning magisk props
12-08 15:39:44.774 12086 12086 D Magisk : hide_daemon: Unmounted (/system/priv-app)
12-08 15:39:44.775 12086 12086 D Magisk : hide_daemon: Unmounted (/system/etc/permissions)
12-08 15:39:44.775 12086 12086 D Magisk : hide_daemon: Unmounted (/system/etc/sysconfig)
12-08 15:39:44.775 12086 12086 D Magisk : hide_daemon: Unmounted (/system/xbin)
12-08 15:39:44.775 12086 12086 D Magisk : hide_daemon: Unmounted (/sbin)
12-08 15:40:12.397 880 902 I Magisk : proc_monitor: com.bankinter.bkwallet/org.chromium.content.app.SandboxedProcessService0 PID=[12181] ns=[4026531840]
12-08 15:40:12.398 12248 12248 D Magisk : hide_daemon: handling pid=[12181]
12-08 15:40:12.398 12248 12248 D Magisk : hide_utils: Cleaning magisk props
12-08 15:40:14.285 880 902 I Magisk : proc_monitor: com.bankinter.bkwallet/.splash.SplashActivity PID=[12258] ns=[4026534387]
12-08 15:40:14.287 12264 12264 D Magisk : hide_daemon: handling pid=[12258]
12-08 15:40:14.287 12264 12264 D Magisk : hide_utils: Cleaning magisk props
12-08 15:40:14.300 12264 12264 D Magisk : hide_daemon: Unmounted (/system/priv-app)
12-08 15:40:14.300 12264 12264 D Magisk : hide_daemon: Unmounted (/system/etc/permissions)
12-08 15:40:14.300 12264 12264 D Magisk : hide_daemon: Unmounted (/system/etc/sysconfig)
12-08 15:40:14.300 12264 12264 D Magisk : hide_daemon: Unmounted (/system/xbin)
12-08 15:40:14.301 12264 12264 D Magisk : hide_daemon: Unmounted (/sbin)
12-08 15:40:14.302 12264 12264 D Magisk : hide_daemon: Unmounted (/system/app/YouTube)
12-08 15:40:25.913 880 902 I Magisk : proc_monitor: com.bankinter.bkwallet/org.chromium.content.app.SandboxedProcessService0 PID=[12318] ns=[4026531840]
12-08 15:40:25.919 12389 12389 D Magisk : hide_daemon: handling pid=[12318]
12-08 15:40:25.919 12389 12389 D Magisk : hide_utils: Cleaning magisk props
12-08 15:40:25.919 12389 12389 D Magisk : hide_utils: Cleaning magisk props

Full log is attached.
[Magisk] Deses:
Double posted, sorry!
[Magisk] ed33:
Anyone tried installing a custom kernel after installing 18. It seems to break ramdisk. Restored my boot, then reinstalled 17, I was then able to install kernel.
[Magisk] Vision:
Magisk v18 More information Xperia z5

Hi I read the information about version v18 what mean with that ... [General] Deprecate path /sbin/.core, please start using /sbin/.magisk

And how do that? I try delete manual the folder sbin/.core but after reboot my device create itself again
[Magisk] PMFRTT1:
Anyone else experiencing random crashes in magisk 18.0?
[Magisk] sofia848480:
Randomly has been crashed in magisk18.0. Restored my boot, and then reinstalled 17.3, I was then able to the install kernel.
[Magisk] BurnedDrake:
If I install or update a module and uncheck it before rebooting it stays deactivated, and always has. Maybe something is up with your Magisk install
[Magisk] jcmm11:
And were you running canary, as he was? Also where are your logs? If you expect things to be fixed you need to provide information to use to fix it. Things like:

phone

Android version/Rom

app causing the problem

and logs

Need
[Magisk] jcmm11:
If you're not creating modules and the relevant install scripts you don't need to worry about this
[Magisk] ken_ac:
Pixel 3 stuck on battery icon

Same problem with a Pixel 3, December update (Build PQ1A.181205.006), with latest builds of Magisk including v18.1-a54eaf53 and (stable) v18.0. If the phone is off, and then connected to a charger (or computer, etc.), the dim battery icon appears and never disappears. Clearly the phone is designed to execute a minimal "charging" routine which must be in the boot image. Apparently this routine gets caught in a loop when Magisk is installed. Uninstalling Magisk restores normal charging screen behavior.

Magisk Manager shows both "Preserve Force Encryption" and "Preserve ... dm-verity" as enabled.

Thanks for any help.
[Magisk] Vision:
Both sbin/.core and sbin/.magisk

Oh... Only download module from magisk manager and one not exist and install from internal memory.. And now.. Exist and the 2 folder.. Sbin/.core and sbin/.magisk. It's OK if 2 exist? Not take space? Because have the same inside
[Magisk] FuLygon:
do i need to reinstall custom kernel after every magisk update ? because topjohnwu say flashing custom kernel after flashing magisk, but in this case is updating magisk with custom kernel installed
[Magisk] Badger50:
Not if you update magisk from within the magisk app. Just updated myself about 3 hours ago, and custom kernel is still fine :good:
[Magisk] jenslody:
/sbin/.core is just a (temporary used) symlink to /sbin.magisk , so developers have time to fix their code for the new paths.

In other words, it does not use any space
[Magisk] WSZR:
What is the location of the magisk.apk application? I do not have an application after the last update. I can not install it myself. After flash magisk uninstaller and flash magisk, I still do not have an application.
[Magisk] habylab:
Magisk 18 breaks 4k recording on my OnePlus 6. After flashing, only change, it now can't record 4k.
[Magisk] n0j0e:
Strange.. ok, i will reset Magisk Manager and test

Sent with much love & Android. OnePlus 5T
[Magisk] Vision:
Aw.. Good news that
[Magisk] WSZR:
After the last update I do not have the Magisk Manager application and I can not install the application! Flash Magisk Uninstaller and flash version 17.3, 17.2 and 17.1 does not change anything, I still do not have an application! What should I do now? I do not see the application in the /data/app folder. I do not want to do wipe! I use Oneplus 5T.
[Magisk] wes'side:
After updating to 18.0, on my Samsung t800 running nougat 7.1, it broke my net lus texting and my YouTube vanced unroot version not connected to Magick, couldn't send texts, watching or refreshing looked like it wanted to work but didn't, I went ahead to test the fact an reinstall YouTube vanced, same problem, I went back to 17.1 magisk and it all worked fine, I also noticed a slight increase of battery consumption, that's on an aicp which has worked flawless until that new update. ??
[Magisk] ygb7:
Adway (3.3) is disabled after installing newest Magisk 18.0 (Stable) - Magisk-v18.0.zip on my ZTE Axon 7 (A2017U).

I went into Magic Manager | Settings and clicked on Systemless Host. It says "Systemless host support for Adblock apps. However Adway (3.3) is disabled after installing newest Magisk 18.0 (Stable).

WORKAROUND

This was all working fine on my ZTE Axon 7 before I upgrade to Magisk 18 tody. I was running Magisk 17.3 (Beta) - Magisk-v17.3.zip before I upgraded to Magisk 18.

Therefore, I re-installed Magisk 17.3 (Beta) - Magisk-v17.3.zip and everything works fine again. It seems like this is same behavior when Magisk 17 was released. I remember it disabled Adway also until Magisk 17.3 Beta was released.
[Magisk] casouzaj:
With Magisk stable v18.0, just like all recently recompiled to C++ Canary builds, in my Sony Z3 Compact phone, running CarbinROM 6.1, without changing any data, apps relying on Microsoft Intune app accuse that my phone is rooted. Again, I'm back to stable v17.1.
[Magisk] Zilla0617:
There's an issue with substratum and magisk 18, even after updating to latest substratum version 1011. I'm unable to delete previous theme overlays. Running rooted pixel 2xl on stock pie
[Magisk] Pkt_Lnt:
Already posts and dev version update available.

https://xdaforums.com/showpost.php?p=78369532&postcount=29334
[Magisk] Zilla0617:
I mentioned that I have the latest version of substratum 1011 (released today) and the issue remains, unless there's another version maybe 1012
[Magisk] Pkt_Lnt:
Then you need to post logs or there is no way to solve the issue either in Magisk or Substratum.
[Magisk] QuinNExotic:
Lost root access on Xiaomi Redmi Note 4x Mido on Magisk 18.0 upgrading from 17.1

Going back to 17.1 and everything is fine.
[Magisk] ajsonofgod:
Safety net is failing with this latest update on OnePlus 3.
[Magisk] Zilla0617:
How do I post logs kinda of new when it comes to this? Thanks
[Magisk] Pkt_Lnt:
Use this excellent resource:

Magisk and MagiskHide Installation and Troubleshooting guide - the evergrowing collection of Magisk tips and tricks

especially this section

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] spawnlives:
No problems with adaway ( ver. 4.0.12) for me on latest magisk version (18) on my s8. As it is basically treated as a module now did you Reboot your phone after tapping on systemless host in settings and checking in modules menu to see if it is installed and turned on.
[Magisk] FlavioV:
I'm in the same AdAway version as you (3.3) and it's working fine with Magisk 18.0 once the systemless hosts module is active. Didn't do anything else just updated from v17.1 and rebooted once more to install the module.

Moto MAXX (quark), RR-O v6.2.1
[Magisk] smileguy91:
Substratum's still broken after the update for me - any solutions?
[Magisk] n0j0e:
Maybe update AdAway to v4.0.12..

https://androidfilehost.com/?fid=11410963190603855470

Sent with much love & Android. OnePlus 5T
[Magisk] YouheiPlayer:
Re:Magisk General Support / Discussion by topjohnwu

Hello there, I am new here and maybe someone could explain

to me why did I just got a boot error after updating Magisk v18.0.

Using Huawei Y5 MYA-L22 6.0,

1st) I updated the Magisk Manager to the latest update within the app. Build 168 or something.

2nd) I installed the new version of v18, I didn't knew it wasn't compatible for my Android 6.0.

Procedure:

a) I installed it "Directly" because it has a 'recommended' button in its name.

b) I clicked Reboot button within the app after successfully updating without any errors.

3rd) The after effects:

The phone does not start to boot properly, at first it begin to show the 1st Logo Boot Img,

then restarts itself, leading to its own default boot image of huawei recovery.

I already installed TWRP from nemo2 3.1.1 and bootloader unlocked... I wonder why...

Will reflash it with my stock-official-rom later. UGH. Wasted... :confused:

P.S. I didn't installed any modules, it doesn't support my phone.
[Magisk] Badger50:
Check your play store. My substratum just updated about 10 minutes ago :good:
[Magisk] tsongming:
Using Magisk 18.0 on the Leeco Pro 3 X727

No issues with using any Magisk plugins, no issues with Adaway 4.0.11

No issues with Substratum.

For the people with substratum issues, compile the overlay, delete the substratum folder, reboot device.Recompile, apply, then it will work

See screenshot of themed Magisk Manager
[Magisk] Zilla0617:
Updated to which version of substratum?
[Magisk] Badger50:
1011 :good:
[Magisk] Zilla0617:
Oh ok that's the current I'm on and having issues with it
[Magisk] smileguy91:
Everything with Substratum is fine now except I am unable to uninstall any overlays, and pressing uninstall only disables an overlay :(
[Magisk] Zilla0617:
That's the same problem I have
[Magisk] martyfender:
The new systemless hosts is now a module and once you click on it in settings, you must reboot for it to be activated, just like any other module.
[Magisk] jcmm11:
Where are the
[Magisk] ireneusz.irzyk:
Mod Edit:

6. Do not post or request warez.

If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community.
[Magisk] zurik:
Hello, by making "Complete Uninstall" from Magisk Manager, I should get after that OTA updates or I need to flash the factory image again via Fastboot?
[Magisk] spicediablo:
I have the same problem too. Safety net check also failed. Roll back to 17.1 and still fails...

Sent from Sagit
[Magisk] Gungrave223:
Well thats tragic :crying:
[Magisk] adhd_1977:
Anyone ???
[Magisk] Mrcactuseater:
No.
[Magisk] JuergenZ66:
I am using LG G3 d855 with CM13. Everything works fine, no bootloop
[Magisk] Opticuhl:
Xposed + Suhide works fine with Safety Net. Remember that xposed is a little buggy (a few performance issues). Also make sure to use the version linked in the thread.
[Magisk] Dalamar666:
really? with xposed working?

Thanks for the info... time to nandroid and try suhide =/ ...
[Magisk] JuergenZ66:
I use this:

http://xdaforums.com/lg-g2/development/cbump-bump-current-boot-image-t3325186

follow the link, download is under Miscellaneous.

works fine on my G3.

the source is here

https://github.com/blastagator/cbump
[Magisk] chris9000:
Any chance you could give us a step-by-step on how to do this properly? Would love to be able to use xPosed without having to disable xPosed and reboot each time I want to use it.
[Magisk] Opticuhl:
The instructions are found in the Suhide OP and in the thread :). I would sum it up for you but I'm super busy atm.
[Magisk] PaxiFixii:
Pokemon Go

Hey guys.. I installed Magisk for pokemon go .. it worked ..But recently it stopped working (I THINK) .. Im still able to toggle and untoggle root like before .. But now it doesnt allow me to connect into the game. Gives error such as unable to authenticate or failed to login .. This usually means server issue .. I thought my account was banned aswell so i downloaded the 0.35 APK and tried.. Login was possible without any errors with my account still playable.. But when i redownloaded the 0.37 official or apk version.. it says unable to authenticate/failed to login like before.. PS : Early after the 0.37 update.. I downloaded magisk and i could play flawlessly without any issues.. Yesterday i had this problem awhile but today the whole day its like this.. Anyone knows whats wrong?
[Magisk] Nik1703:
Noob question -

I know Magisk does not require root, but - does Magisk work with the notoriously unrootable AT&T Galaxy S5? (Locked bootloader)
[Magisk] Didgeridoohan:
If you have Xposed installed, disable it.
[Magisk] Captain_Throwback:
Did you read the OP?
[Magisk] smint86:
Unfortunately I can confirm this. I'm not abled to log in anymore at all, using latest magisk and phh superuser. It does not show an error but refuses to connect to the server.

PokemonGO 0.37.1

With 0.35.0 I can login as expected (with or without root mounted in magisk manager).

/edit:

Sorry, did not read well. It's the safety net update, had to disable xposed.

Swyped via Tapatalk
[Magisk] Nik1703:
Ah, missed that line. Dammit. Oh well.
[Magisk] Kiid:
According to the reverse engineering thread in the PogoDev discord, 0.37.1 detects Magisk, downgrade to 0.37.0. Download it from apkmirror.. The playstore updates to 0.37.1
[Magisk] Nik1703:
sounds like a bandaid; what happens when 0.37.1 is mandatory?
[Magisk] DerpleNerple2000:
I installed automagisk and selected Android pay, and it works as intended. I'm using magisk, phh systemless root, and the viper module. Xposed is definitely the problem.
[Magisk] Kiid:
Well it's the only temporary fix I've found so far.. At least it'll work until the forced update comes along.. It's definitely a better fix than removing Magisk, xposed and root entirely..
[Magisk] habylab:
I'm using all of that too, as well as Viper. It can't be the problem entirely, as it works for me. Must be some bug that is being encountered.
[Magisk] ygb7:
RESOLVED - Adway (3.3) is disabled after installing newest Magisk 18.0 (Stable)

Thank you to all who replied to my post #29393 - Adway (3.3) is disabled after installing newest Magisk 18.0 (Stable) - Magisk-v18.0.zip on my ZTE Axon 7 (A2017U).

martyfender was right.

RESOLUTION

Once you install Magisk 18.0 (Stable) - Magisk-v18.0.zip

Launch Magic Manager | Settings and clicked on Systemless Host. It will say "Added Systemless host module" if successful.

REBOOT YOUR PHONE. As martyfender stated, you must reboot for it to be activated

This worked for me with Adway (3.3) and Magisk 18.0 (Stable) - Magisk-v18.0.zip on my ZTE Axon 7 (A2017U).
[Magisk] paarnoutse:
Same for me (OnePlus 5 running OxygenOS 5.1.7 - Android 8.1.0). Magisk Hide fails for *any* app in my hide list.

Magisk v18.0 not really stable yet... :(

Update 2018-12-10:

Magisk Hide not working (any app having access to '/sbin/su' etc.) seems to be a temporary issue, appearing after first reboot, and only when upgrading to Magisk v18 via Magisk Manager. Worked OK for non-Office apps again after a 2nd or 3rd reboot.

When using a Magisk Uninstall followed by an install of Magisk v18 plus Dreamer(3FM)'s Intune Hider module (all by flashing via TWRP), Magisk Hide basically worked after 1st boot.

HOWEVER, even then root was detected by Intune afterwards (although the hiding of other apps in my hidelist worked OK).
[Magisk] chooks06:
I had one app that detected root after I clean flashed Magisk 18.0 and setup the hide parameters like before.

I cleared the data of the affected app. On starting the app, it no longer detects root.

I'm on a Note 3 N9005 running Lineage 15.1.

Not sure if this method can work for others.
[Magisk] สุรินทร์ พลโธา:
It worck very well for me mi mix 2 xiaomi eu rom 10.2 v.8.12.6 thanks topjohnwu
[Magisk] Hemphiz:
Stable my arse
[Magisk] xunholyx:
Works great for me.

Patching boot.img didn't work. I had problems with that.

After flashing the latest uninstaller.zip and flashing v18 after a reboot in recovery instead, everything has been working as expected.

I'm not sure what method you used to update, but I would recommend using the same

(the reboot is probably not necessary after flashing the uninstall.zip, but that's what I always do)
[Magisk] Soumy1234:
I've been using Magisk for a while but suddenly whenever I reboot, most of my modules like greenify, xiaomi a2 camera and Dolby don't load. I have to reboot again to get them back and it's really annoying to keep setting greenify again. Is there a solution to this?
[Magisk] martyfender:
On my Nextbook Ares 8A's I have had a similar problem with direct install through many unofficial builds, so I quit using that method and it never fails when I flash it through TWRP. When what you described happened to me with the direct install, I had to first reflash my stock boot.img in TWRP, then flash the Magisk.zip.
[Magisk] xunholyx:
What device?

I won't have an answer for you ( I haven't been following along lately and haven't experienced issues myself), but that info is probably relevant.

Also, custom ROM or stock? Kernel? Other mods?
[Magisk] Nguyễn Thế Vinh:
How can this app keeps dettecting root ? I listed it in Magisk Hide and SafetyNet is still good

https://play.google.com/store/apps/...obile&pcampaignid=APPU_1_6qgMXKzpHdaiwAOqlZYo
[Magisk] pranavpmanoj:
You may have to hide Magisk Manager itself.

Open Magisk Manager>Settings>Hide Magisk Manager.
[Magisk] abdoh01:
Hi guys i flashed magisk v18 but it cause bootloop to my phone and i still need to flash v16.7 and than flash v17.3 i hope the problem be solved in next version

My phone is lg k10 ( k430dsy )

Android 6.0
[Magisk] DrJPepper:
I just did the "recommended" update option for the latest version (18.0 I think) and after restarting my phone, it is stuck in fastboot mode. As in where it tells you to pick power off or restart with a few fastboot commands listed on the screen. Problem is, none of my computers will recognize the phone. Can anyone assist in this? Google is being entirely unhelpful.
[Magisk] xunholyx:
Just a heads up for those that "liked/thanked" this post.

Don't do that.

The "thanks" goes to the original poster, not the Mod edit.