yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_install_the_Magisk_Manager

Not much to do about it at the moment then I guess...
[Magisk] sam0658:
My friend, you are a legend. Just hiding Google services fixed it. Thankyou.

To help anyone who is struggling with the same thing, this is what worked for me:

Hide Magisk manager

Hide Barclays app in Magisk hide

Hide Google services framework in Magisk hide

Run Barclays app and deny root access permanently

Go to Barclays app info in android settings and clear app data

Run Barclays app again and allow access to phone permissions and the app should now run as normal ?
[Magisk] Peter_File:
Tank you very much, this did the trick. I googled and searched the forum but didn't think of looking it up in the didgeridooh. Feel a bit stupid now.
[Magisk] The War Profiteer:
Negative. The crash is highly relatable about a module I've installed, but by flashing the ROM, I meant I wiped everything and flashed again. I only used Viper4Android from Magisk repository. These logs are after uninstallation of the module by reflashing the zip, and as you can see it didn't get removed, and I was on the latest canary debug.
[Magisk] Piperman123:
Using Magisk with Sandboxes like Shelter?

I couldn't find much about using magisk and it's modules with things like shelter which use the work profile to sandbox things from your main account. I'm just wondering if you'd need to install the magisk manager in shelter to use it and any modules, if you wanted to install youtubevanced say? Same question with things like xPrivacy, or would installing a second instance of magisk and modules, sandboxed or not, cause some sort of conflict? I noticed the multiuser setting in magisk manager but I'm unsure how that would tie in with something that manages the work profile like shelter (and island, I think also works the same).

Magisk is awesome so far, loving it! Coming from xposed and it definitely feels far better.
[Magisk] Windowlicker001:
Thank you
[Magisk] martyfender:
Were you able to restore your rom with SPFT?
[Magisk] Mixedability:
I have stock ROM file/MTK drivers/latest SPFT on a memory stick and waiting to find someone who's a Windows user to agree to help. I've subscribed to Hovatek forum and found a step by step guide, so hopefully all will be well!

I'm grateful for your input as it's positivity has given me hope that it's not a hopeless situation....

I'll keep you informed :good:

---------- Post added at 09:39 PM ---------- Previous post was at 09:29 PM ----------

I have stock ROM file/MTK drivers/latest SPFT on a memory stick and waiting to find someone who's a Windows user to agree to help. I've subscribed to Hovatek forum and found a step by step guide, so hopefully all will be well!

I'm grateful for your input as it's positivity has given me hope that it's not a hopeless situation....

I'll keep you informed :good:
[Magisk] ManDone.vRs:
Yeah ... It's laggy on MIUI last version global .. Thanks anyway ☺️
[Magisk] Rafasama:
can i flash magisk v18 in oreo ?
[Magisk] martyfender:
Unless someone else here has personal experience with your device with that Android version, the only way to know is to try it and see. However, I recommend having a good backup or the rom available to reflash, if there are issues.

I recommend the latest Canary build, with the disclaimer that there can be new bugs in it on some devices. I have not encountered any major issues with it on my devices, but the results can vary.

Maybe someone with that device will provide input here, also.
[Magisk] Rafasama:
Oh The device is a Moto G5.. not a Moto E4 sorry for that.....do you know if its possible yet ?
[Magisk] Artim_96:
As long as you have a way to at least boot TWRP or flash a boot.img modified by Magisk manager there is no device limitation unless you explicitly read about it as long as it's running Android 4.4+. And since the G5 was launched way back in 2017 TWRP can't be a problem either.

And since I think the F2FS bug has been fixed there too it should run without the workaround module.

But in my experience, Magisk forgets to keep the keep-dm-verity on true. So you might want to run the following commands in TWRPs Terminal before installing Magisk:

echo KEEPVERITY=true >> /cache/.magisk
echo KEEPFORCEENCRYPT=true >> /cache/.magisk
[Magisk] martyfender:
Yes, others are using Magisk on the Moto G5.
[Magisk] Wolfcity:
It does, at least on my Moto G5+. You can flash also Disable_Dm-Verity_ForceEncrypt if you don't want /data to be reencrypted.

https://yadi.sk/d/HLr5vjnkA8gaqw

(Officially released here: https://zackptg5.com/android.php)

And as recommended above don't use magisk 18, use 18.1 or the latest canary build.
[Magisk] papin97:
ASK:

I installed Magisk 18.0 with success result (also installed some modules like busybox and YouTube Vanced). But if I try to install any font modification modules and restart my phone, it will bootloop.

Anyone know why this is happening? My phone has Flipfont, maybe that's why? (but I want to use the module instead because they offer more styles like condensed)

My phone is Asus Zenfone 2 ZE551ML.
[Magisk] jonners59:
Thanks guys.

It took many goes to make it work and 3 days including restoring the phone.... managed to achieve it.

HOWEVER something odd happened last night. I lost root and Magisk and can not reinstall Magisk.

After reinstating the last tweaks of reinstall i noticed there were two Magisk Managers. No idea how it duplicated. I took no notice, i booted in to recovery and wiped cash and delvik cash and rebooted. It wouldn't boot back, was stuck in a boot loop. I rebooted back to recovery wiped again and it booted ok. I then removed one of the Magisk Managers. Rebooted, but lost root. I then went into the remaining Magisk Manager it says Magisk not installed update agailable. I try to install, but it fails. Probably becasue i have now lost root.

I rebooted in to recovery and reinstalled Magisk... seemed ok, but once rebooted back into the phone it is still not rooted and Magisk Manager still says update available and Magisk not installed. Tried this many times.... I just can not reinstall Magisk ans recover root.

How do i reinstall, please?
[Magisk] Didgeridoohan:
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_not_installed
[Magisk] jonners59:
Thank you. That sorted it.

One quick question, since sorting out the encrypted /data issue caused by the Magisk built into the ROM, I have found that the phone is draining the battery at an alarming rate. 20%/hour, and that's not doing anything. Any ideas, please?
[Magisk] martyfender:
In a root teminal, you can find out what is using the most cpu time with the top command. I use the terminal app by jackpal. I found I had to use "busybox top", or "toybox top", in order for it to not constantly be refreshing and scrolling to the bottom, though. OS Monitor is a good app to view this in also.

I have to thank others in the Canary development thread who pointed this out.

What apps have you added to the Magisk Hide list. Despite what you have read, don't add all Google apps to the hidelist, especially Chrome and or Android System Webview. To many apps in the hidelist can cause problems. Normally you should only add apps that are detecting root and therefore won't work properly. Don't hide root apps.

However, there can be some special cases other than what I wrote above?
[Magisk] jonners59:
Thank you. DIdn't know that about hiding. I have hidden it from all apps except the ones I know need it. May need to look at that again. I wonder if we should be keeping a list of does and don'ts hide(?)
[Magisk] Borotes:
Google Pay and LastPass were detected with working Magisk Hide? Any suggestions?
[Magisk] boe323:
I'm having a really bad issue with safety net, both false with magisk safetnet , invalid response when magisk hide is enabled, any help to fix it will be apreciated
[Magisk] Jos_Hdez22:
I have the same problem, I have tried changing the fingerprint using magiskhide props but it is always the same result.

Sometimes after several restarts it works, but the next restart the problem returns.
[Magisk] luciferlul:
magisk doesn't work on redmi note 7 pro

I have unlocked bootloader.

and successfully installed twrp from https://xdaforums.com/redmi-note-7-pro/development/unofficial-3-2-3-redmi-note-6-pro-violet-t3912400

but when I install magisk always failed.

here is the recovery.log.

need help.
[Magisk] parag60288:
Awesome.

On latest Canary builds, even google pay is working flowlessly.

Thanks for suggestion.
[Magisk] Paz9:
i noticed some apps dont work if magisk manager is installed

i uninstalled magisk manager and the apps begin working again

so it seems apps are detecting magisk manager
[Magisk] wilsonhlacerda:
Try hiding itself on its menu (it'll get a random name. On app drawer it will be only "manager" )
[Magisk] Paz9:
not sure how i didnt see this setting

working perfect now! thanks!!
[Magisk] guest4711:
You did neither tell us which version of magisk you are using nor which modules you did install nor anything else.

So we need a crystal ball now. Try the newest canary build, clean data and cache of magisk manager.

If this does not solve your problem, see [MENTION=4667597]Didgeridoohan[/MENTION]'s famous trouble shooting guide: https://www.didgeridoohan.com/magisk/
[Magisk] hadisi:
My question is the same as yours. Is there a solution?
[Magisk] guest4711:
If you are using a firewall (e. g. afwall) allow internet access for Manager.

Otherwise download file manually (using any browser). Flash from recovery or using Manager's module interface (press the plus sign, select the zip just downloaded).
[Magisk] hadisi:
thank you for your reply.

The network I am using is normal. Download the magisk zip file through the installation in the manager. After the download is complete, the installation will report "Unable to check signature" with the recommended option.
[Magisk] Jean_85:
I had the same issue, and I was hiding a lot of apps. I read here to hide only the necessary ones.

After removing hide from all Play apps it started working again immediately

Inviato dal mio Poco F1 utilizzando Tapatalk
[Magisk] JaylanPHNX:
A few quick questions for those using the canary builds to get Pay working:

1) I know you're accepting a certain level of risk using those builds, but are there any major issues you're having that I should look out for?

2) Is it the zip labeled magisk-debug on his GitHub?

3) Do I need to install the canary manager app too?
[Magisk] Miustone:
Hey Folks. Can anyone tell Me if Magisk is able to handle a system.prop-like vendor.prop from a Module!? I would like to add values to the build.prop in Vendor and i actually don't know how, or if Magisk will able to do that. Thanks in advance for Your Tips!
[Magisk] milsabords:
A quick question to the experts.

Is it possible to patch the stock boot.img from a stock phone with the Manager on another device rooted by Magisk ?

I have an A9 Samsung Phone with stock Oreo, which is not supported by TWRP, and a Samsung A6 Tab under Pie Resurrection Remix, rooted by Magisk 8.1.
[Magisk] :
Latest stable loses safety net after phone is running for a while. Reboot fixes it.
[Magisk] Strephon Alkhalikoi:
Yes. Magisk will ask for the location of the boot image to be patched. The dicey part is whether or not Odin flashes the modified image to the A9.
[Magisk] ashyx:
It will, but why not just do it on the device in question? :confused:
[Magisk] Didgeridoohan:
Magisk doesn't edit any files. Whenever you use the system.prop file in a module it will simply load the new value instead of the one found in /system/build.prop, /vendor/build.prop, default.prop, or whatever other file the prop is loaded from, it won't touch any files.
[Magisk] Miustone:
I am aware, but i still don't know if Magisk is able to add Lines on the build.prop in /vendor... The Name "system.prop" suggests it is made for the build.prop in /system!? vendor.prop would mean to me it will be mounted/used in /vendor!? Treble has changed the way how build.prop are handled. I've seen that on Devices using GSI Images who are loading Vendor Build Props together with generic System Build Props to gain Support for a wide range of Devices. Editing the Vendor Prop is similar to System Prop editing but is mounted on different Points. So all i wanted to know was if Magisk can handle a vendor.prop File or if it needs further Edits for it...

Maybe can [MENTION=4470081]topjohnwu[/MENTION] clear that out!?

Best Regards:cowboy:
[Magisk] Didgeridoohan:
No... Stop talking about adding lines to or handling specific files. That does not happen.

Whatever prop and value you add in the module system.prop file will be loaded to memory by the resetprop tool at boot. It does not matter what file the prop is originally found in. It doesn't even matter if the prop exists at all to start with, resetprop will create it no matter what.
[Magisk] thezinq:
How to increase the size of magisk.img? Wich is probably stored in data/adb/magisk.img
[Magisk] Son-j:
Omg unSu worked! I can now manually toggle root status of my nexus 4. And I'm able to play pokemon go now. So happy thanks!
[Magisk] exodius48:
Are you using xposed to play pokemon go?
[Magisk] Son-j:
No. I'm just using the magical and the switch in its manager to play it
[Magisk] got2best:
Should be able to install zip.. make sure your on the Kernel that came with your ROM then flash the kernel you want over top. Make sure you have all your backups just in case it doesn't work well.
[Magisk] exodius48:
Ooh..

Normally pokemon go won't load if using xposed like me. If you just use magisk to turn on/off root, it will work.

---------- Post added at 09:31 AM ---------- Previous post was at 09:26 AM ----------

No longer working in CM13. :(
[Magisk] JudgeDread11:
Yes it's possible. Use the module template, and the example you've quoted. Add your lines to the right script and fill in the commented areas in the template. Just open every file in the template with notepad++ and see what it says.

---------- Post added at 03:43 AM ---------- Previous post was at 03:42 AM ----------

Read the op and wait patiently for v7

---------- Post added at 03:47 AM ---------- Previous post was at 03:43 AM ----------

Please take this discussion to the correct (viper 4 Android) tread.
[Magisk] Seanbest:
I flashed the kernel over Magisk and it worked fine. Thanks.
[Magisk] micksh:
I think I bricked my phone. I installed Magisk using this guide:

http://www.droidopinions.com/magisk-pokemon-go/

because it was the first I found and it was simple. Then I found this thread.

After I flashed Magisk.zip, SuperSu.zip and rebooted, phone screen is black and nothing happens. If I hold power button, phone vibrates once, but only if not connected to power.

I had root, so "Remove ANY kind of root" requirement was ignored. It's my fault.

Sony Z3 Compact, flashed Magisk over working pre-rooted Android 6.0.1 image. I didn't have Xposed.

Is there anything I can do to make my phone work again?
[Magisk] JudgeDread11:
You need to restore the original boot img. If you can't get into fastboot, with Sony you can try to use the repair option in PC companion.

From here on this discussion is more suited for your device forum.
[Magisk] Hurrdurrdurrdurr:
Do you still have access to Recovery Mode? if so then just restore a Nandroid backup you created -OR- if you didnt create a Nandroid backup (you should really as it saves you alot of hassle) just flash your Stock ROM and start from scratch
[Magisk] rochian_adrian:
Just flash stock kernel with flashtool. Or stock firmware with the same tool.
[Magisk] micksh:
No, can't boot to recovery. Black screen and that's it. One vibration if not connected to power, volume up/down ignored, then black screen.

Thanks, I will try to do that.

EDIT: Phone can't be recognized by PC, it seems. Anyway, will go to Sony forum tomorrow.
[Magisk] iamelton:
i would like to inquire about the relationship among Magisk, custom kernel, and SuperSU..

from OP, the flashing sequence of the 3 should be:

"custom kernel" -> "Magisk" -> "systemless SuperSU"..

but my previous knowledge of custom kernels and SuperSU tells me to flash in this sequence:

"SuperSU" -> "custom kernel"..

are both of them still held true? and is this the difference between "systemless SuperSU" and "SuperSU"?
[Magisk] Heart1010:
Can anyone with a working magisk please test if this online banking security app starts?

https://play.google.com/store/apps/details?id=de.fiducia.smartphone.android.securego.vr

If this app detects root it closes itself immediately after the start and the browser starts and shows a site which describes that root was found ... and so on.

Thanks a lot!
[Magisk] q1t1:
Doesn't work here...
[Magisk] nnaji_blaze:
Thanks Again [MENTION=3638617]iamelton[/MENTION] :), you saved me a huge pain.

I'll have to remove all and reflash all, got it :good:

I'll read the thread properly later, skimmed through earlier and I was actually planning to test the latest beta release by chainfire "SuperSU v2.78 SR1" to see if it would work okay with it.

Haven't done it yet though, this is all because Lucky patcher and a few other apps don't seem to work with Systemless root, so I will re-root with the Chainfires SU.
[Magisk] hammerhead2:
Here neither.
[Magisk] Heart1010:
Thank you both! So they must check "other things" to identify a "none standard / not rooted rom/phone" :confused:
[Magisk] syrakus:
I have Magisk installed and phh-superuser-17-magisk.zip installed and the app starts. I can login but I didn't register the app because I didn't use it.
[Magisk] martyfender:
This is from the Magisk documentation. Newer Canary versions do not use magisk.img any longer. I believe this applies to Magisk 18.1 and earlier:

In a terminal app with root (type su, enter, first)

For me, the new imageless Magisk in Canary builds is working very well.

I'm sure that some modules will have to be updated to work with it though.
[Magisk] thezinq:
Delete
[Magisk] Didgeridoohan:
Don't do this on a live and mounted system. It will cause issues... If you really want to fit larger files than can the current image size can accommodate, create a merge image (/data/adb/magisk_merge.img) that holds the files you want to add to the image (with all the proper paths, of course). When you reboot, Magisk will take care of merging that image to the main one. Or, you can do the resizing in TWRP, mount the image and move the files you want in there.

But, as already stated, the image approach has been ditched altogether (in the Canary builds and soon available in beta/stable).
[Magisk] thezinq:
I have also tried the canary build and that broke my flashlight and camera on my Mi A1 using Evolution X ROM
[Magisk] theOriginalSuperl2:
After flashing the Magisk zip in TWRP (with no errors shown), it appears successful, but Magisk Manager says it's not installed. I'm using my own Resurrection Remix build. What's going on?

EDIT: I flashed for the third time, to get logs, and it's working now...
[Magisk] sachin5555:
What to do if an app still find root access after disable that app through magisk hide ? Please help
[Magisk] Didgeridoohan:
Most likely also hide the Magisk Manager (look in the app settings). For more: https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] jeffshead:
THANKS! That fixed my issue.

It seems the latest version of the NFCU app now looks for the Magisk Manager app. With previous versions, just ticking the NFCU app in the hide list was enough.

Does one need to unhide the Magisk Manager app if one needs to uninstall it when unrooting in order to update Android or can one leave it hidden and just flash the latest Magisk uninstaller zip?
[Magisk] Didgeridoohan:
The uninstaller is not able to uninstall a hidden Manager. It won't know what package name it has... Only thing that will happen though is that you'll have an orphan Manager installed that won't be able to do anything (just uninstall it).
[Magisk] apratul Vasu:
Hello, I'm using Moto G5s Plus with Android 9.0 custom ROM and after i flash magisk, my instant apps stop working, instead playstore opens a link in browser when i click on try now option, any solution? :confused:
[Magisk] thezinq:
Flashlight and camera is not working with Magisk v19.0
[Magisk] ashyx:
Is that on every Android device ever made then? Because you haven't actually given any specifics. :rolleyes:
[Magisk] thezinq:
Device: Mi A1

ROM: Evolution X

Magisk: 19.0

Edit: I fixed it:fingers-crossed:
[Magisk] dnsmo:
I just updated to v19 and lose boot on my SM-G900T with LOS 16 official build. Just want to report this, 18.1 is fine, I have to restore the boot.img from a backup for the phone to get back to normal. otherwise it keep going to download mode.
[Magisk] bunny1796:
Hi,after installing latest magisk manager v17.1 Google pay detects magisk. I tried to hide both manager and google pay.but still it detects magisk..Any help?
[Magisk] martyfender:
There is a thread dedicated to getting Google Pay to work with Magisk:

https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
[Magisk] rub1k:
Updated from stable 18.1 to beta 19.0 via Magisk Manager (direct update method or whatever it's called) and rebooted.

Got stuck on stock recovery screen, which was a bit scary.

Can't tell if TWRP is gone since I'm at work and can't check easily.

I rebooted one more time and it seems fine now; it booted all the way through to OS and I was even able to add my credit cards to Google Pay (couldn't using 18.1); will test in-store purchase later today but promising so far.

EDIT: LineageOS 15.1 on a Xiaomi MIX 2 (chiron) phone, forgot to mention.
[Magisk] cmo220:
Both work fine on Pixel 3 stock. Direct update method through Magisk Manager.
[Magisk] rognlorie:
Is there anybody that can make a charging animation mod for magisk that would work on op 6t?
[Magisk] bluenote73:
My Axon 7 running stock nougat just reboots to recovery with v19 beta as it did for 17.x and 18.x despite TJW saying it should be fixed in this closed github issue: https://github.com/topjohnwu/Magisk/issues/729?_pjax=#js-repo-pjax-container

Anybody can confirm or comment? I did not have the time to go to the ends of the earth installing, so it's possible I suppose if you nuke your phone and hunt down and remove the magisk directories manually ... ?
[Magisk] madbat99:
Read 3 posts up. Did you try to reboot again?
[Magisk] xsonymonx:
Same here with G900F and AEX 6.4 (Pie)

Back to 18.1 and all fine
[Magisk] kushpel:
I've also tried magisk v19, phone got stuck in download mode after reboot.

Samsung klte, official RR 6.0.2.
[Magisk] etillxd:
klte only booting Odin/download mode

I have an Galaxy S5/klte/SM-G900F running official lineageos 16.0.

I installed the 19.0 Beta and now when i reboot my phone i always get into odin/download mode.

I still can access recovery mode and when i uninstall magisk the phone boots normaly again.

Magisk 18.1 still works fine when i install that version.

If i can provide any logs that could help you just tell me how to get them (or send a link to a tutorial or smth.)

And sorry for my (maybe) terrible english. I'm german btw.
[Magisk] bluenote73:
That poster doesn't make mention of upgrading from 16.x or the problem being continuing, but I went back and tried anyways, and it doesn't make a difference. Thanks for the suggestion.
[Magisk] mrsubway:
Just a report. LG H931 converted to US998. 19 seems fine. Upgraded via Magisk Manager.
[Magisk] iankelly2001:
Exactly the same outcome when I try to install Magick v19.0 Beta on my Samsung Galaxy S5/KLTE/SM-G900F, this one running Resurrection Remix v7.0.1 [klte] (Android Pie). After flashing, the Samsung splash screen appears for approximately one minute, then the phone goes into Download (Odin) mode. I have had to return to Magisk v18.1, to get the phone to boot again.
[Magisk] AndrzejDwo:
Guys if you have problems with Magisk v19, and you stuck in download mode. Force your phone to reboot to recovery, reflash the kernel and then flash Magisk 19 again. After reboot you will need to install MM apk.