yashsingh1/xdaforums huggingface dataset:
[Magisk] karnasw:
I have problem with Magisk 18.0. Sometimes SafetyNet passed, sometimes not. Everytime i'm in the shop and want to pay with Google Pay, I have to check is it working before go to cash register. There were no problem with Magisk 17.3. I'm using OpenKirin RROS 3.
[Magisk] habylab:
This is a known issue, open still on GitHub. Go back to 17.3 like I have. Note that some banking apps detect root still.
[Magisk] karnasw:
Thanks for info. I will wait for fix then.
[Magisk] cthulhu1987:
Nope, I don't have an SD card and Magisk doesn't install the Manager. :(
[Magisk] guest4711:
And what does happen if you try to install the apk by hand?
[Magisk] DriFtyZ:
Hey guys i have installed magisk sucessfully in my sdk27 sm-g920f and installed a couple of modules correctly but magisk does not load them and i cannot find them in the drawer. Can anyone help?
[Magisk] cthulhu1987:
It says Magisk isn't there.
[Magisk] monteie2016:
I am having and issue, of my own doing with Magisk. I am running Lineage OS 15.1. I have installed the Jan 30th nightly via TWRP. I installed it by deleting the Dalvik Cache, installing the zip, deleting the Dalvik Cache and booting. When I open up Magisk it has a check beside 'Latest Version v18.0' and an 'X' beside Magisk is not installed. When I click the Install it gives me the option to Download Only or Patch Boot Image File. The download would lead me to believe that an install may fix it but not confident enough to proceed. Is the fix simply to go back to TWRP and intstalling Magisk once again? I did some searching but I'm not coming across anything that I feel confident moving forward on. Any help would be appreciated.

Nexus 6p

TWRP 3.2.3-0

Magisk v18

Lineage OS 15.1 (Jan 30 Build)

Thanks.
[Magisk] guest4711:
Yes, after installation of a new rom version you have to reflash magisk usually.
[Magisk] monteie2016:
Thanks. Some questions.... Does an uninstall of Magisk have to be done prior to the install? Also... If I was to leave the phone in the state it is in and do a restore from a good, working system, would that solve this problem? The second question is just academic.

Thanks for the quick reply!

:good:
[Magisk] guest4711:
No, just go into recovery, flash magisk and reboot.

The uninstaller may be needed to remove all traces of magisk if you don't like to use it anymore (or if something went wrong as a 'last' option).
[Magisk] monteie2016:
Thanks again. That did it. I'll keep that in mind for next time.

:good:
[Magisk] jcmm11:
Solve which problem? Losing Magisk? Magisk is in the boot image. Restore a boot image from a system with working Magisk you'll have Magisk. Flash a stock/non-rooted boot image you won't have Magisk (although if you haven't run the uninstall you'll still have the db and img files etc that Magisk uses in /data/adb/)
[Magisk] cthulhu1987:
I finally did it! I used the Russian-UI TWRP, *didn't* allow write-access at the beginning so as not to brick the phone and then installed Magisk, rebooted, installed the Magisk Manager it all finally worked!! PRAISE THE SUN!!
[Magisk] lordlord6:
I have red wolf twrp, i am on magisk 16.3, magisk manager is on 6.1.0. (165) when i try to install directly version 18.0. i try to restart and then i can not restart. Then i need to do backup to start again. Help?
[Magisk] capscorn:
Anyone know module for resolve idle drain ? Im on Android 6.0
[Magisk] guest4711:
Perhaps some modules you use are not working with actual magisk. Boot into recovery, enable magisk core only mode. You may achieve this by opening advanced->terminal and entering

touch /cache/.disable_magisk

. Please not the dot before disable; the sign behind is an underline...

When rebooting afterwards magisk should be up and running, but all modules are disabled. In Magisk Manager you should then disable "core only mode" in settings, then update all modules and disable these without updates. (When the next reboot is succesful you may enable one more module, test by rebooting, until you know the culprit...)
[Magisk] lordlord6:
I did put magisk only core. How i delete and where all magisk name file?
[Magisk] guest4711:
Sorry, I don't get it.

If the question is how to delete/disable a module: Open MagiskManager, open settings, disable "Magisk Core Only Mode", open "Modules", uncheck each to disable... (or press the litterbox symbol to delete)
[Magisk] lordlord6:
I did disable magisk core only. But i see they put on posts, that you must delete all files with the name magisk on. What you know about it?
[Magisk] cuevasjose:
No puedo pasar la comprobación del safety net
[Magisk] martyfender:
This is an English only forum.

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

https://www.didgeridoohan.com/magisk/HomePage
[Magisk] guest4711:
Some apps try to detect that a phone has been rooted by searching for folders and files belonging to Magisk. As long as you don't have issues with these apps you don't need to care about it.
[Magisk] mankind_18:
can someone help me? i have three apps that detect if the phone is rooted or not, let's say it's bpjstku, ovo and vlive. the three of them won't work unless i use magiskhide. bpjstku and ovo work normally after i use magiskhide, but not with vlive. it say i cannot play video on rooted device..i'm using oreo 8.1.0 btw, if i remember correctly, when i was in 9.0.3 pie, it works.. hmm..
[Magisk] acspdx:
Can't install modules

I have a Moto E4 running Nougat 7.1.1 and an unaltered stock ROM. I was able to install Magisk and get systemless root, but I can't install any modules. The process always fails with this error:

mount /sbin/.magisk/block/loop09->/dev/tmp/magisk_img failed with 13: Permission denied

! /data/adb/magisk_merge.img mount failed...

! Installation failed

I tried downloading the module and installing the .zip file with TWRP, but after a reboot, Magisk didn't recognize it.

EDIT: Fixed! It was the F2FS bug. I

thought

I'd installed the workaround module before, but apparently it didn't take. After a second attempt to flash F2FS_Loopback_Bug_Workaround-2018.10.9.zip, modules were able to install properly.

EDIT: NOT FIXED! After another reboot, the F2FS workaround disappeared, and now module installation fails again!
[Magisk] Bakica:
Try the Canary build
[Magisk] acspdx:
Of what? Magisk or the workaround? (Link, please?)
[Magisk] guest4711:
Of Magisk. See https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337/post77549897
[Magisk] acspdx:
Well, that's definitely not the solution, as I couldn't get it to work even for a moment. I don't think the F2FS Loopback Bug Workaround can handle the latest Magisk.
[Magisk] Soul Spark:
where can I post Logs and Bug report??

I flashed Magisk 18.0 on my ASUS_X01AD (stock rom) and after the first reboot there is a constant bug report being generated after every boot.

So I thought I should post the bug report so dev can see whats the issue and correct it since ASUS_X01AD is new in market.

Thankx
[Magisk] amaroney55:
Hey i really appreciate you all at xda and magisk. I have learned so much so fast. I dont want to seem like i am complaining or anything. But i keep getting dupilcates of magisk. I have installed xposed could that be the reason.
[Magisk] Soul Spark:
ya that might be a good reason. I also had something like that when I had installed Xposed, so I removed it.
[Magisk] hyborian:
Not exposed I guess, because I get the same and I don't have exposed. I have Magisk set to hide itself and then it renames itself to plain Manager.

I think Magisk when updated just creates another one rather than try to unhide the other.

It's ok, though, after updating, I just open the one that has Manager as its name and the other one disappears.
[Magisk] harryruhr:
Magisk is not installed

Using Xiaomi Redmi 5 Plus (vince) with AOSP based Pie ROMs.

Already tried ArrowOS, crDroid and AOSPExtended. All ROMS have January 2019 security patch, always clean flashed.

Tried Magisk 17.2, 17.3, 18.0 and the current canary build

No errors during flashing

Magisk Manager always reports "Magisk is not installed"

/sbin/su is there, linked to /sbin/magisk

calling /sbin/su directly in a terminal fails with "permission denied".
[Magisk] jcmm11:
This will happen if the ROM has Magisk pre-installed which means the Magisk Manager apk is located in system/priv-app (or possibly app). Note that if you have 2 copies you don't get the benefit of hiding Manager, since a version with the original name still exists.

Although in your case, with the original disappearing, I wonder if it's a ghost image of some kind. What launcher are you using?
[Magisk] hyborian:
No, mine is not preinstalled, I prefer to use the Canary Release. All my phones with Magisk are MIUI ROMs, the rest are unrooted.

It disappears and I use Nova Launcher ... No problem with hiding as I can open banking or even the telco app that will warn against root. Ghost is a nice description for it. It happens rarely these days, more last time. Like in today's latest releases, 2 different Magisk Manager versions one after the other, no ghosts.

I never get that double on my phones where Magisk is not hidden though, only on hidden Magisk. Maybe on my ROM, it unhid Magisk first, updated it, then hid it again, but left the "ghost" icon.
[Magisk] Xx MOE:
cool thanks. In that case ill stick to the pokemon go 35 version and just not update it.
[Magisk] shovelgrill:
Only APK, other file is source code for people that have need to fix something or want to look. Also if dropdown menu say null then you cant modify quick tiles standard way in your rom. Tell me if you have issues with installing tile ;)
[Magisk] gk1984:
Can we maybe create a magisk Pokémon support thread and get this back on topic? I'd like to follow magisk but getting annoyed to look through 8 pages of the same damn questions that have already been answered for Pokémon players every morning when I wake up.
[Magisk] ammar18:
hello, i am new to this systemless mod or so, so apologize if im doing it wrong :D

downloaded magisk v6 zip and flashed it but when i flash phh superuser root zip it says that magisk is not installed.

seeing at /data and /cache, there is no magisk.img (as stated in the flashing process), and now i dont have xposed and root access (it will be fine for me)

using samsung galaxy s4 gt i9500, lollipop 5.0.2 with twrp 3.0

here is the part where it fails to make the image

Creating /data/magisk.img
CANNOT LINK EXECUTABLE: could not load library "libext4_utils.so" needed by "make_ext4fs"; caused by empty/missing DT_HASH in "libext4_utils.so" (built with --hash-style=gnu?)
[Magisk] steveo17:
yes please! there is so much nonsense in this thread now that it makes it next to impossible to follow

hell pokemon go should just be abolished all together. most ridiculous game around.

there is already an xposed/android pay thread, please also put place all questions regarding those topics there as well
[Magisk] alroger:
Flash Magisk again, and pay attention if it really installs or gives you an error during installation. And then share the logs (see OP).
[Magisk] ammar18:
i flashed it like many times already...

cant get magisk.log since im unable to get to /cache (i fully unrooted the device), might root it back tomorrow
[Magisk] ammar18:
maybe recovery.log might be helpful.
[Magisk] alroger:
Yeah, it probably showed up during flashing, but you flashed phh right after it and didn't see it. There is a button in TWRP which allows you to see the text output, and in red should be:

- Repacking boot image
cat: can't open '/boottmp/new-boot.img': No such file or directory
- Flashing new boot image
dd: writing '/dev/block/mmcblk0p9': No space left on devicee

There is your problem. Search for you specific ROM/Device, it's not compatible. Maybe with another ROM or another boot.img... Read OP.
[Magisk] Depressed Man:
Some banks detect root but won't do anything. Others will detect root and block you from using the app. I believe Chase is the prior.
[Magisk] ammar18:
hmm ok, thanks btw for helping :D
[Magisk] hanschke:
SuperSU v2.76 (Magisk Version) will you update it to the latest release? I got the play store update too after installing this :angel:
[Magisk] xCRUTCIOx:
No one can help with this unable to get boot image error?
[Magisk] Mouse_exe:
SafetyNet keeps tripping for me whenever Xposed is installed. Even if I disable it in the Material Design Installer, and then reboot, it still fails. If I uninstall Xposed completely, it passes.

Potentially related, I'm unable to install the latest systemless version of Xposed, 86.5. This is the log I get when I try:

Installing zip file '/sdcard/Magisk/xposed-v86.5-sdk23-toptojnwu.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
******************************
Xposed framework installer zip
******************************
******************************
Powered by Magisk (@topjohnwu)
******************************
- Mounting /system(ro), /cache, /data
- Xposed version: 86.5 (Systemless by topjohnwu)
- Device platform: arm64
- /data/magisk.img detected!
Updater process ended with ERROR: 2
Error installing zip file '/sdcard/Magisk/xposed-v86.5-sdk23-toptojnwu.zip'
Updating partition details...
...done

I'm on a Moto X Pure running 6.0.1, and I have TWRP 3.0.2-0. What confuses me the most is that two nights ago, I was able to install the latest systemless Xposed and pass SafetyNet without disabling and rebooting, before Google updated their server side. Yesterday I tried to reinstall Xposed to see if that would help, but it kept giving me the same error message I posted above.

I'm currently using systemless Xposed 85.6.
[Magisk] neo2x:
Magisk on Android Revolution HD

I have the Android Revolution HD custom ROM and would like to know if I will be able to install Magisk and hide root succesfully when using it.

Thanks in advance.
[Magisk] Artim_96:
Shouldn't be a problem. Otherwise just ask with details to problems
[Magisk] SidneyD:
It changed it to permissive on startup for me. :(

---------- Post added at 09:23 AM ---------- Previous post was at 09:20 AM ----------

Do you mean wipe the whole phone and reflash the ROM from scratch? Or is there a less drastic method to restore the original boot img?
[Magisk] westeight:
Last night I restored my trusty M8 back to 100% stock. It has no Internet access.

Just used Android Pay. Worked perfectly. No idea how it's actually authorising anything though as the phone is an internetless brick... :cowboy:

Going to slowly add Magisk, etc and see if something 'breaks'...
[Magisk] JudgeDread11:
You can flash only the boot image. Extract it from you stock rom if you don't have a backup.
[Magisk] DerpleNerple2000:
Looks like it has a bunch of modifications that mod the system partition (not 100%, just looks like it). I'd say make a nandroid backup and give it a shot. If it doesn't work, restore the backup. Make sure to remove SuperSU from within the app beforehand.
[Magisk] xunholyx:
It's probably detecting the Magisk Manager app. Hide it

Magisk Manager > settings > Hide Magisk Manager
[Magisk] habylab:
Done that already, still doesn't work. I don't think you've seen the github issue I've linked before. It works and then it doesn't, it's very inconsistent. 17.3 is fine.
[Magisk] xunholyx:
I wasn't replying to you, I was replying to mankind_18. I haven't looked into your issue.

Hiding MM might not be working for you, but it does work for others.
[Magisk] habylab:
Sorry, I'm tired and read this wrong.
[Magisk] DriFtyZ:
Hey guys i have installed magisk on my galaxy s6 (lineage os 15.1) and while magisk hide su etc work perfect and the installation of the modules is successful the modules do not load on boot for some strange reason i have provided the log below even tho i can't find any errors here.

Edit: It seems that i get a bad request error on xda while ttying to upload the log so im going to paste it here

02-03 02:57:41.045 3119 3119 I Magisk : ** Initializing Magisk

02-03 02:57:41.047 3119 3119 I Magisk : * Creating /sbin overlay

02-03 02:57:41.049 3119 3119 I Magisk : * Mounting mirrors

02-03 02:57:41.049 3119 3119 I Magisk : mount: /sbin/.core/mirror/system

02-03 02:57:41.049 3119 3119 I Magisk : link: /sbin/.core/mirror/vendor

02-03 02:57:41.049 3119 3119 I Magisk : bind_mount: /sbin/.core/mirror/bin

02-03 02:57:41.050 3119 3119 I Magisk : * Setting up internal busybox

02-03 02:57:41.108 3127 3127 I Magisk : Magisk v16.7(1671) logger started

02-03 02:57:41.109 3123 3123 I Magisk : Magisk v16.7(1671) daemon started

02-03 02:57:41.109 3123 3129 I Magisk : ** post-fs-data mode running

02-03 02:57:41.164 3123 3129 I Magisk : Upgrade/New module: xposed_27

02-03 02:57:41.164 3123 3129 I Magisk : Create /data/adb/tmp.img with size 96M

02-03 02:57:41.246 3123 3129 I Magisk : * Merging /data/adb/magisk_merge.img + /data/adb/magisk.img -> /data/adb/tmp.img

02-03 02:57:41.751 3123 3129 I Magisk : * Move /data/adb/tmp.img -> /data/adb/magisk.img

02-03 02:57:41.764 3123 3129 I Magisk : * Mounting /data/adb/magisk.img

02-03 02:57:41.791 3123 3129 I Magisk : * Running post-fs-data.d scripts

02-03 02:57:41.792 3123 3129 I Magisk : post-fs-data.d: exec [aml.sh]

02-03 02:57:41.797 3123 3129 I Magisk : * Running module post-fs-data scripts

02-03 02:57:41.797 3123 3129 I Magisk : dolbyatmos: exec [post-fs-data.sh]

02-03 02:57:51.617 3123 3310 I Magisk : ** late_start service mode running

02-03 02:57:51.619 3123 3310 I Magisk : * Running service.d scripts

02-03 02:57:51.619 3123 3310 I Magisk : * Running module service scripts

02-03 02:57:51.619 3123 3310 I Magisk : dolbyatmos: exec [service.sh]

02-03 02:57:55.033 3123 3310 I Magisk : ViPER4AndroidFX: exec [service.sh]
[Magisk] albyone:
Hi there,

Sorry for not replying sooner, but I wanted some time to test if the 'Hiding' setting would have any effect. I didn't realize you could hide the app, but I went ahead and set it as you suggested. I also completely uninstalled all the VMware AirWatch applications, waited a few days for Admins to clear my status, then reinstalled the apps, one by one, not opening them until I added them to the hidden list in Magisk.. For good measure, I deleted the app cache and data, then opened the apps and configured them. They seemed to work for about 7 to 10 days before I got the root alert. I did this 3 times over the course of about 30 days. I made sure that the Play Store auto update was turned off. It's the "Intelligent Hub" app that pops up the message and asks if I want to uninstall the remaining apps since they have been compromised ('root' detected).
[Magisk] Mattycaty87:
How do you hide Pokemon go or animal crossing pocket camp

Hi I was wondering how you hide Pokemon go and animal crossing pocket camp I've put it in magisk hide but it's not working do I have to use es manager to change a file
[Magisk] Viol8ter:
Uconnect is detecting ROOT

So the Uconnect app I spend ridiculously 15$ a month to have, just to start my truck in the winter detects ROOT!....Im just wondering if anyone has a possible work around other than Android oreo and the old app. I have tried the basics (hiding magisk, clearing cache, and reading other posts)..... I'm going to find the Uconnect support contact and bash them around a little for making us even think about this ****. LoL (Sorry It's just so lame):cool:
[Magisk] konfuzius4u:
Well probably the same procedure like it has to be with most banking apps. Hiding them with Magisk hide (which often is not enough) and then go to the general settings in Magisk and do repack Magisk with a new name. At least for my banking apps it did work that way. After the repack do first clear the cache of these apps before starting them. Eventually you will also have to delete their data and restart with re-entering their data.

Gesendet von meinem ocn mit Tapatalk
[Magisk] 0ther:
Hi and sorry for my english

I've just upgrade Magisk stable from 17.1 to 18.0

I can confirm this bug: https://github.com/topjohnwu/Magisk/issues/884

I come back to 17.1 and no more problems at all
[Magisk] iLoveMuffinz:
So, I need a bit of help regarding SafetyNet. I am currently running Phhusson's Pie GSI and I can't get neither basic or cts to pass. I have a feeling this issue is quite common but I'm just a bit dumb and don't know what to do. Using Magisk Stable v18.0.
[Magisk] jcmm11:
Start here

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

https://www.didgeridoohan.com/magisk/HomePage
[Magisk] iLoveMuffinz:
Hmm, doesn't seem to provide information regarding my issue. Gave everything a good read and attempted all that was suitable..
[Magisk] akxak:
Downgrade to Magisk 17.x, Magisk 18 is known for severe problems with that, search this thread.

Unfortunately I have not seen any reaction of the developer on this significant issue yet.
[Magisk] Viol8ter:
I was able to open.

Thanks I was able to get it to open the manager hide worked, I swear I tried that. But I was able to get through. :good:
[Magisk] DriFtyZ:
Nvm I fixed it myself thanks to xda community who helped me out ?
[Magisk] Sourabh Gharde:
Just shifted from superSU to magisk manager. It seems to have slowed down my device.

Redmi 5a on PixelExperience for Redmi 5A custom ROM.

Takes longer to boot up and launcher takes a very long time to load the icons in app drawer after every bootup.

Magisk version 18.0 is installed and I see the lag in almost every app.

What should I do? Anything to reduce this or fix this problem

---------- Post added at 08:52 AM ---------- Previous post was at 08:52 AM ----------

Just shifted from superSU to magisk manager. It seems to have slowed down my device.

Redmi 5a on PixelExperience for Redmi 5A custom ROM.

Takes longer to boot up and launcher takes a very long time to load the icons in app drawer after every bootup.

Magisk version 18.0 is installed and I see the lag in almost every app.

What should I do? Anything to reduce this or fix this problem
[Magisk] dragos281993:
Well, if there are no MagiskHide improvements in the new release, I guess I'll stay on 17.3, which has successfully managed to keep root hidden from my banking app. Maybe next time.
[Magisk] kksatpathy:
Thanks
[Magisk] Maverick Jester:
So... updating to Magisk 18.1 via Magisk Manager 7.0 causes my device to land on a black screen saying No command. I'm using a Pixel 2 XL running the January 2019 update. Any thoughts?
[Magisk] AndrzejDwo:
I'd like to confirm that latest Magisk stable 18.1 and Magisk Manager 7.0 are working with direct update on Samsung SM-G950F Soldier9312s Pie-Beta-Rom 3.0.

Cheers
[Magisk] sliding_billy:
Same here on a Pixel 3 (I was going to do a PIxel 3XL after the little one). Myself and another on Twitter have the same issue. No word from topjohnwu yet.

Out of the no command loop running Magisk uninstaller from TWRP .img version in bootloader. I will try throwing the 18.1 file on the phone and installing/rerooting with that. Installing from the 18.1 .zip seems to have worked, but I'd rather not have to reinstall modules and grant SU permissions on the 3XL. so I will hold off while I get the 3 up and going normally.
[Magisk] IODroids:
18.1 works flawless on Redmi Note 4 mido.

Screenshots shared for reference.

Safety net fails as I have xposed installed.

If Stilton available please quote.
[Magisk] IODroids:
How did you turned on black UI ?
[Magisk] Maverick Jester:
Did the same thing to get out of that bootloop. I then went through the following procedures:

Updated Magisk via Magisk Manager v7.0.0: doesn't work, Magisk version remains at v18.0. Even if I flash the v18.1 zip manually, it doesn't update.

Uninstalled Magisk via TWRP, reinstalled the manager, installed Magisk via direct download, and it's still stuck on v18.0. Tried installing v18.1 via TWRP, doesn't update either.

Uninstalled Magisk via TWRP, rebooted, installed v18.1 via TWRP, rebooted, still updates to v18.0. I think the problem is the Magisk zip file.

EDIT: saw your edit that installing from the device worked. Didn't work for me, I'm still running v18.0. I'm annoyed that I also have to reinstall all my modules, but it is what it is.
[Magisk] AndrzejDwo:
Substratum swift black and dark mode in magisk settings.

Edit:

And of course night mode in android settings.