yashsingh1/xdaforums huggingface dataset:
[Magisk] bialyikar:
Someone encountered the problem of accidentally losing SafetyNet.

After starting the phone, SafetyNet is restored, but after some time (from a few hours to several days) SafetyNet disappears without a reason. It does not matter the system version or the type of rom.

Currently I use:

Mi Note 2

Magisk 18

Miui 10.2 (8.12.6)
[Magisk] martyfender:
Did you try to hide the Magisk Manager, in settings? You may need to clear app data and cache in settings for the game, also, after hiding the MM. If that does not work, I suggest you look for answers in the Pogo thread.
[Magisk] FikriWildanNugraha:
FingerPrint Xiaomi Redmi 4x Santoni

after update to 18.0. my device fingerprint not working,for add or remove. . .
[Magisk] GradiusBR:
Hmmmm... you says... to hidde magisk in magisk hide? Now.... no tried... I reinstall, re-root and try, if success, i edit this post.
[Magisk] martyfender:
You hide it in Magisk Manager settings, not under Magisk Hide.
[Magisk] LinuxNewb:
Having this exact issue! Never had this happen on 17.1

Waited since my last post to check safetynet and both are failing again and apps being detected.
[Magisk] positivetourettes:
i just flash magisk 18 to my oreo rom on Moto G and i dont have any magisk at all lol
[Magisk] Skcyte:
Clean install 18.0, the root is working but everything else is broken or something. All module installed doesn't work.
[Magisk] panchogg:
Me too! Clean install and dirty install
[Magisk] rauleeros:
Yeah, latest version of magisk just put me in a boot loop (O+3T) Oxygen 4.5
[Magisk] martyfender:
There has been post, after post, without logs, device info, etc, so I would suggest you all start here first:

https://www.didgeridoohan.com/magisk/MagiskHelp

https://www.didgeridoohan.com/magisk/HomePage

https://xdaforums.com/showpost.php?p=78387493&postcount=29522
[Magisk] jcmm11:
Marty please. You mean you haven't installed the mind reading module yet? ??
[Magisk] martyfender:
When you build it, I will gladly install it!

---------- Post added at 09:40 PM ---------- Previous post was at 09:34 PM ----------

You need a kernel that supports mount namespace. Your kernel doesn't support mount namespace, according to the log and that may be the reason for your errors in it after that line.
[Magisk] spambayes:
Thanks for replying. I'm running stock 5.0.1 Rom and kernel. Installed and running Magisk since v15+ with the same setup. No change in firmware. Could you think of any other possible reasons?

I understand that mount namespace support affects Magiskhide but that doesn't matter to me. I need the root functions primarily.
[Magisk] martyfender:
Mount Namespace if primarily a requirement for Magisk Hide to work. So apparently Magisk worked for you with older versions.

Maybe someone else with more knowledge than me will have some idea. I don't believe you mentioned what your device is. You could also try the latest Canary build, but I'm not sure if that will help. Ultimately you may have to revert to one of the older Magisk versions.

Canary debug builds will provide more detailed logging, which may help [MENTION=4470081]topjohnwu[/MENTION] find the problem.
[Magisk] Skcyte:
Device: Redmi 2 / wt88047

ROM: LineageOS 14.1 (UNOFFICIAL)

Detail of problems: Clean install 18.0 after doing dirty upgrade and found one of my module doesn't work. After that all module installed doesn't work. For example, installing ViperFX, reboot, app is nowhere to be found. Installing systemless font doesn't work upon reboot. Scripts that is placed at service.d does not run unless I run it manually. MagiskHide is also does not pass the test, installing Safety Patch usually fix the issue but since the module does not works at all so that's that.

Log

01-03 06:46:21.313 233 233 I Magisk : * Creating /sbin overlay
01-03 06:46:21.388 235 235 I Magisk : Magisk v18.0(18000) daemon started
01-03 06:46:21.389 235 236 I Magisk : ** post-fs-data mode running
01-03 06:46:21.389 235 236 I Magisk : * Initializing Magisk environment
01-03 06:46:21.398 235 236 I Magisk : * Mounting mirrors
01-03 06:46:21.400 235 236 I Magisk : mount: /sbin/.magisk/mirror/system
01-03 06:46:21.400 235 236 I Magisk : link: /sbin/.magisk/mirror/vendor
01-03 06:46:21.400 235 236 I Magisk : bind_mount: /sbin/.magisk/mirror/bin
01-03 06:46:21.400 235 236 I Magisk : * Setting up internal busybox
01-03 06:46:21.460 241 241 I Magisk : Magisk v18.0(18000) logger started
01-03 06:46:21.531 235 236 I Magisk : * Mounting /data/adb/magisk.img
01-03 06:46:21.622 235 236 I Magisk : * Running post-fs-data.d scripts
01-03 06:46:21.623 235 236 I Magisk : post-fs-data.d: exec [99userinit.sh]
12-14 08:57:32.242 235 398 I Magisk : ** late_start service mode running
12-14 08:57:32.256 235 398 I Magisk : * Running service.d scripts
12-14 08:57:32.276 235 398 I Magisk : * Running module service scripts
12-14 08:57:32.276 235 398 I Magisk : ViPER4AndroidFX: exec [service.sh]
12-14 08:57:32.289 235 402 I Magisk : * Starting MagiskHide
12-14 08:57:32.289 235 402 I Magisk : hide_utils: Hiding sensitive props
12-14 08:57:32.290 235 402 I Magisk : hide_list: [com.google.android.gms/.droidguard.DroidGuardService]
12-14 08:58:17.863 235 402 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[5647] ns=[4026534846]
[Magisk] GradiusBR:
Repacked Magisk Manager with another name, and need clear dalvik and cache in TWRP , and clear data and cache on pokemon go app. Also deleted apk and zip used to install magisk from my external sdcard.

And... no work! Pokemon go continue to detect magisk manager and splash screen with "this device, os, or software is not compatible

I found problem.... Magisk update or install, create folder named Magisk Manager in internal storage, affer delete this folder, working!

Sugestion to developer! After update (or install) delete folder created in internal storage.

:laugh:
[Magisk] martyfender:
Yes, that is a folder left from a previous version of Magisk. Newer versions do not create it. I think the developer did not delete it because it gives the user a chance to save any important files to another location, such as the new default: Downloads. Sorry I did not mention it. I thought of it after I posted, but did not edit my post.

I still have that folder on 3 of my 5 devices, but it causes no problems for me since I don't use any apps that detect root except for Rootbeer Sample, which I have hidden to test Magisk Hide.
[Magisk] spambayes:
My device is a Samsung Note 3 N9005 on stock Lollipop 5.0.1 with TWRP recovery. I started with Magisk v13.3 and have since upgraded through each new version without issues until the latest v18.0 which brought about this perplexing problem. The last working version was v17.3, but as I've described, even rolling back to v17.3 now doesn't resolve the problem. The upgrade installation of v18.0 seems have made some persistent changes to my system that uninstalling and rolling back to v17.3 doesn't undo.

I'm at a loss as to what else to try besides the canary builds.
[Magisk] Didgeridoohan:
[MENTION=2084155]spambayes[/MENTION] Have you at any point made sure to restore your device's stock and untouched boot image? To make sure you're starting from a completely clean slate...
[Magisk] martyfender:
Have you thought about a clean install of your rom, followed by flashing Magisk?
[Magisk] zzzhead:
Would like to report, on oneplus 6 and oneplus 3, magiskhide does not work after some time. Apps able to detect root. On reboot it works for awhile.
[Magisk] Doomdiver:
Try turning Magisk hide off and on in the settings in Magisk Manager. It's still annoying but better than rebooting. I'm having the same issue on my 3T, logs don't seem to show any errors, and the time between it working and not working seems to vary. Sometimes it works all day sometimes it fails after half an hour.
[Magisk] spambayes:
If nothing else works, this would be the last resort. Just hoping I can get it working without a reinstallation of the rom.

Had done that some time in version 15+ after a buggy release. After that there was no need since every update went smoothly.

Update:

After a series of regressing TWRP uninstall/install starting from v18, I have Magisk v17.0 working on my device. I then uninstalled that and installed the latest canary v18 build. As expected, it didn't work. But I hope the logs gathered would prove useful to [MENTION=4470081]topjohnwu[/MENTION] for debugging what went wrong and for a fix. After uninstalling v18 canary and going back to v17.0, Magisk is working again.

So something has broken between v17.0 and v18.0.
[Magisk] Didgeridoohan:
And did you, prior to installing v18+ restore a completely stock boot image? I'm not asking just because it's fun, but that there might actually be something with your boot image that has been altered so that things aren't working properly and a clean slate is necessary.

The only log I've seen you posting is a not so useful Magisk log from Magisk v17.3... You'd need to post a lot more for it to be of any help (installation logs, the Canary debug log, etc).

Edit: Saw your posted log now... Not a single su request in there and tons of errors. No idea if they're useful, but it's something. Do you also happen to have an installation log for v18?

---------- Post added at 09:28 ---------- Previous post was at 09:20 ----------

I've seen these reports of MagiskHide intermittently failing, but haven't been able to observe it myself yet. Now you say you have this problem on a OnePlus 3T, which happens to be the same device I'm using and I've been using the latest releases for some time before the release of Magisk v18.0 and haven't seen anything like it... Here's an opportunity to compare and figure this out. :good:

What is your setup?

I have a OP3T with OxygenOS 5.0.6, Franco Kernel r43 and always use the latest Magisk Canary debug build. I have a few Magisk modules installed, like ADB & Fastboot, App Systemizer, Busybox, F-Droid Privilieged Extension, MagiskHide Props Config, V4A FX, YouTube Vanced, and a few personal debloating and personalisation modules. I only have two apps/processes on my Hide list (only those apps that do detect root) appart from the default Play services, and I don't whitelist anything Magisk related in battery optimisation.

That's a start, let's see if we can figure something out...
[Magisk] Doomdiver:
I'm running HavokOS 20181211 and have not changed the kernel. The only module I've got is the OnePlus 3T front camera fix (which I can actually disable because my current version of GCam doesn't need it) as for Magisk Hide I've hidden Google Play Store, my 3 banking apps, a couple of apps I need for topping up some NFC cash cards, Google Pay, Pokemon Go, and a few apps from companies that have asked for root in the past that have no need for it. I'm currently on the stable v18 of Magisk, with Manager 16.1, I updated from 17.1 (I think, but can't be sure), which was the first version of Magisk I ever installed. Once that wasn't working I uninstalled Magisk and tried a clean install. I've not changed anything relating to Magisk in terms of optimisation.
[Magisk] Didgeridoohan:
So the major difference seems to be the OS. I wonder what about Havoc could be causing it... I don't really have the time to change ROM and stuff to test (and it's also my daily driver).
[Magisk] mrspeccy:
Banking app detects Magisk despite Magisk hide and hidden Manager

Hi,

since an update two days ago the following app is able to detect Magisk on Honor 10, EMUI 8, Magisk 18.0, despite the app being added to the Magisk hide list and Manager hidden:

https://play.google.com/store/apps/details?id=dk.bec.android.mb1.b00032.prod&hl=da

The previous version of the app (released early December) worked fine in this scenario.

If Magisk is uninstalled, the app runs fine again.

Magisk is also detected with earlier versions (17.1 and 17.3). A test on another phone (P9 lite, EMUI 5.1) revealed the same behavior: with Magisk installed the app detects root, without Magisk it runs. Logcat logs and Magisk logs are attached.

Note the following interesting lines in the logcat:

--------- beginning of crash
12-14 10:06:39.294 5994 6068 E AndroidRuntime: FATAL EXCEPTION:
12-14 10:06:39.294 5994 6068 E AndroidRuntime: Process: dk.bec.android.mb1.b00032.prod, PID: 5994
12-14 10:06:39.294 5994 6068 E AndroidRuntime: mvejbpsp.FOoSSDzS: 00
12-14 10:06:39.294 5994 6068 E AndroidRuntime: at mvejbpsp.kzVK78lg.BTbQGkaE(SourceFile:23)
12-14 10:06:39.294 5994 6068 E AndroidRuntime: at mvejbpsp.kzVK78lg.N6Qi3aCe(SourceFile:66)

5594 is the id of the banking app. What is mvejbpsp.FOoSSDzS etc? Is it the randomized names of Magisk processes? May it be that the app tries to communicate with Magisk's processes? Or uses a vulnerability in theses processes? Also, the randomized process (?) names are very long: could the app interpret the existence of such long names as sign of Magisk?
[Magisk] zzzhead:
I've Reverted to 17.3 already :)

Thanks for the suggestion, Im sure others have the same issue
[Magisk] zeroprobe:
[MENTION=4470081]topjohnwu[/MENTION]

Is there any way I can use an intent to open the Modules fragment of Magisk Manager, so I directly point users where to install a module?

Like a shortcut? At the moment I have it just opening the Magisk main activity.
[Magisk] Forever Alone:
Downloads are very slow through magisk module exactly like open GApps.
[Magisk] dope77:
Hey, after the 18.0 update, magisk hide literally hides root from all apps even the non selected apps. The root prompt won't appear in any of the apps, Is there a reason behind this? The only thing i can do is turning magisk hide off, go to app and grant root permission then go to magisk and turn hide on. And after updating the apps that need root, they won't work, the only thing that make them work is go to magisk supersu, removing the updated app, again turn off magisk hide, go to app and grant permission, then turn hide on. 17.3 was stable more than 18.0 which also keep losing root, restarting device will make root work again.
[Magisk] martyfender:
One thing you did not mention, was that you have xposed installed, according to the log you posted in the Canary thread. There are all kinds of java exceptions in that log, if i'm not mistaken.
[Magisk] paolo200:
I have the same problem
[Magisk] guest4711:
Your logs clearly tell us there are problems with your kernel (lacking some needed functionslity)

I Magisk : hide_list add: [com.google.android.gms.unstable]
07-19 00:10:31.239 256 273 E Magisk : proc_monitor: Your kernel doesn't support mount namespace :(

So you probably should look for another one.
[Magisk] martyfender:
Does anyone know if Magisk needs a mount namespace kernel for anything other than Magisk Hide. He said he did not need Magisk Hide, but I forgot to suggest that he try toggling the slider off in MM for Magisk Hide, to see if that helped.
[Magisk] nasedase:
I'm on Pixel with stock rom and my phone's audio stopped working. I tried uninstalling JamesDSP, installing the audio compatibility module, installed elemental X but nothing has fixed the issue thus far. When restarting the audio works perfectly for about five seconds then goes completely mute. No phone audio, no music, no call audio. Any suggestions?
[Magisk] Pkt_Lnt:
Yes, this from the Magisk Troubleshooting Guide:

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] Diaphotos:
I have rooted my S8 without custom recovery by patching boot.img with Magisk Manager and flashing it with ODIN. Updating Magisk to v18 worked flawlessly though :fingers-crossed:

I once flashed the stock boot.img and it resulted in a boot loop.

I thought this is what Magisk Manager does anyway, when uninstalling itself by recovering the backed up boot.img. But since I had to wipe my device after flashing the patched boot.img and thus losing the backup, I had to flash the stock boot.img myself, which went wrong :confused:
[Magisk] martyfender:
You could get a bootloop if you flashed stock, then rebooted, without flashing Magisk.zip after the boot. Img. First.
[Magisk] Diaphotos:
Since I have stock recovery, flashing Magisk.zip afterwards isn't possible either way, is it?
[Magisk] JimZiii:
i could really use some help, i installed the wrong module and i'm getting a bootloop. i tried starting with core features only by creating 'disable_magisk' (without the ' ) in /cache/ but my phone still wont boot. i'm on oreo 8.0 with twrp so i have no access to decryption so i can't reach the module files that way. tried a bunch of uninstall zips but the fail, they can't mount or unmount partitions it tells me before getting the error. found something called SUmount script which supposedly could mount the magisk module files to be accessible outside of the root but that refuses to install also.

i'm able to use my phone by fastboot flashing my original boot image but i cant fix this without root and with it i don't know how since i'm only getting bootloops and twrp barely working.
[Magisk] jenslody:
Do you have a dot in "/cache/.disable_magisk", otherwise it will not work.
[Magisk] JimZiii:
thank you so much, i completely forgot about the dot
[Magisk] martyfender:
Yes, you are right, I posted while on a break at work and didn't see that detail.
[Magisk] parkerlreed:
I found an older module I want to use but the update-binary looks for the magisk.img. That doesn't seem to be around anymore. Anybody know how I can get this to install?

https://github.com/willcast/alsa-ut...ter/META-INF/com/google/android/update-binary
[Magisk] jcmm11:
That one is pretty simple. You could even do it manually, without a zip. Post the entire zip and I'll fix it for you.

magisk.img does still exist, the path that should be used has changed though. (/magisk no longer exists)
[Magisk] tripLr:
Where is the original unlatched boot.IMG stored when magisk flashes? It says it backs it up.

From now on, I am saving my ROMs OEM boot image in a separate file, that's how I reverted. I had a kernel that I used and had to revert in twrp image flash
[Magisk] parkerlreed:
The zip is that repo. https://github.com/willcast/alsa-utils-systemless

Those are the contents. Thanks.
[Magisk] jcmm11:
It's gzipped in /data/stock_boot_<sha1 of extracted img>.img.gz
[Magisk] panchogg:
Testing with Hybrid Kernel 13
[Magisk] martyfender:
Magisk.img has been moved to /data/adb.

I don't know much about module creation, but it is based on a very old template, (v3) so I don't think there is any way it will work unless it is completely rewritten.
[Magisk] jcmm11:
Yeah I keep forgetting I need to go into desktop mode to download the entire repo.

Try the attached. It's untested, but should work (I hope l
[Magisk] infernix:
Haopened to me today on a stock Pixel 2 XL. Rather annoying because the banking app in question resets itself and have to register it again. Didn't happen before v18/6.1.0. Turning magisk hide off and on does seem to fix it, it isn't detecting root after that.
[Magisk] xunholyx:
I have the P2XL stock rooted as well, and I'm not having those problems with my banking app. Magisk Hide is working just like it always did for it.

I would suggest running the latest uninstall.zip in recovery, then re-flashing v18 again after.
[Magisk] parkerlreed:
Cheers! That worked.
[Magisk] martyfender:
I believe that there was a fix for any2kernel in one of the latest Canary builds, if I am not mistaken?
[Magisk] infernix:
Your banking app may not be using the same detection methods. The other 2 banking apps don't have this problem (and they also detect root without magiskhide).
[Magisk] pranavpmanoj:
I'm having trouble with MagiskHide. Whenever I turn it on, it no longer detects root. Have to reinstall Magisk Manager again. This problem started today morning. Does it have anything to do with BusyBox installation?
[Magisk] martyfender:
To be blunt, this has been posted, many, many times, on how to get help, we are not mind readers. You did not even bother to post your device info and Android version:

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] demonoidmaster:
Magiskhide hides apps from detecting root, so do you have any apps that are selected?
[Magisk] pranavpmanoj:
I'm sorry. I meant Hide Magisk Manager.
[Magisk] pix106:
[MENTION=4470081]topjohnwu[/MENTION] How can I help with french translation of magisk manager strings ? There are a few mistakes.
[Magisk] demonoidmaster:
Go in settings, there's a button for that, read the OP first for info on what that feature does before doing so
[Magisk] pranavpmanoj:
I have been using it for a long time now. Was working really well. As of today morning, I had installed installed BusyBox and suddenly, Hide Magisk Manager no longer detects root. I'm on Pixel Experience Pie for Sanders.
[Magisk] RebootDog:
MagiskHide can't hide root from com.shinhan.smartcaremgr (which is called SOL알리미 on google play store). Unhiding and hiding the app in MagiskHide didn't fix the issue.

Root Checker Basic(com.joeykrim.rootcheck) can't detect root when root is hidden from it in MagiskHide. The checker can detect root when root is not hidden from it in MagiskHide.

Device // Google Nexus 5

OS // LineageOS 14.1-20180607-NIGHTLY-hammerhead

Android version // 7.1.2

LineageOS API level // Guava (7)

Kernel version 3.4.0-g853158b

Android security patch level // May 5, 2018

Magisk Manager 6.1.0 (165)

Magisk 18.0

Log

12-15 15:38:59.877 166 187 I Magisk : proc_monitor: com.shinhan.smartcaremgr/com.shinhan.sswf.smail.activity.RootActivity PID=[22191] ns=[4026534292]
12-15 15:39:00.542 166 187 I Magisk : proc_monitor: com.ahnlab.v3mobileplus/.interfaces.AppInterfaceService PID=[22236] ns=[4026534314]
[Magisk] jenslody:
Might be related.

Which busybox do you use?

Logs?

Osm0sis systemless busybox-module is known to work flawlessly with Magisk.
[Magisk] zooorgie:
Install Magisk on previous roted phone with linage ?

I recently rooted with autoroot, then installed TWRP and then flashed Linage 15.1 on a Samsung Galaxy S5 (smg-900F)

Now I heard about Magisk...

How do I replace TWRP with Magisk, if its even possible after installed Lineage.

Because in description I read "you HAVE to make sure you haven’t modified /system (and /vendor if available) in any way."
[Magisk] Artim_96:
Magisk is a replacement for SuperSU and similar, it has nothing to do with TWRP (besides the fact that you use TWRP to install it in the beginning). But being on a custom ROM it's very difficult to let SafetyNet pass. And then you are on Lineage. That comes with root build in. So to use magisk you'll have to get rid of that in the first place... And hope that it's not included in the ramdisk, otherwise you'll need a custom kernel first.
[Magisk] jcmm11:
Magisk is not a TWRP replacement, it's a root method. To install, assuming you're not currently rooted, simply flash the Magisk zip via TWRP. When you do the install save the install log. If there's a problem with the install attach the install log and post here.

If you are currently rooted you'd have to completely remove the existing root first.

Since you're running a custom Rom you don't have to worry about not modifying system or vendor. That's only if you're running stock and you want to be able to take OTAs.

Edit: there be ninjas loose!
[Magisk] metaspook:
[MENTION=4470081]topjohnwu[/MENTION] Bro what about the "Magisk MultiROM" concept? is that deprecated?
[Magisk] mogantivenkatesh:
Hii. The latest version of magisk(18.0) is not working or giving root access to some apps. Help
[Magisk] Oswald Boelcke:
WHAT exactly isn't working? WHICH are the few apps without root access? Any logcat available?

This thread's OP refers to the Announcement Thread regarding troubleshoting guidance. Please allow me to partially quote its OP:

What are the results after your referred to the "Magisk and MagiskHide Installation and Troubleshooting guide", followed it and applied its recommendations?
[Magisk] zooorgie:
I guess I did something wrong, I runned Autoroot again, and TWRP dissapeared.

Looks like the old recovery now.

How do I get TWRP back ?

Edit:

Its back, I flashed TWRP with Odin again
[Magisk] Oswald Boelcke:
For whatever reason, I can't open the link you've attached. I assume it most likely to be a screenshot.

Did you try to flash TWRP again through ODIN? A tool like Flashfire or Flashify might also work.