yashsingh1/xdaforums huggingface dataset:
[Magisk] kenbrownstone:
Guys how can I fix my v20 after flashing 14.0 My screen is non responsive..Only way with a mouse through the C port?
[Magisk] Didgeridoohan:
Make sure none of your installed modules have the placeholder file left in the system folder in the module directory (under /magisk). Magic Mounting new files to /system is proving to be a bad thing...

The placeholder file gets removed from the module when installing through the Manager Downloads section, but if you install a module manually and the module developer has left the file in the zip so that it mounts to /system you might get a bootloop. It's under investigation...
[Magisk] guest4711:
Installed 14.0 via magisk manager without problems over 13.7. S4 jfltexx, RR 5.8.4 @ nougat.

Problems with systemless hosts (showing "disabled" while active) are history now :good:

Thanks so much!
[Magisk] kishd:
Thought you might find this interesting. Playstore does not regard Magisk as harmful.
[Magisk] smartpr1v4t3:
I installed all modules from recovery and this are all "old" ones before version 14

I managed it to get it running v14 with clean installation, but as u said after installing modules with recovery it bootloops again.

Will try it next days with installing through manager
[Magisk] marisaleh:
you know that a lot of modules won't now install with

magisk v14, they need updating

for example, debloat and systemize won't install
[Magisk] kgb88:
I tried your modified xposed but it does not work. Just show erro cannot update permission then immediately reboot from twrp recovery
[Magisk] maximesharp:
Still bootloop on my Samsung SM-G901F, the last version that work is the V13.0(96f8efc).

I'm on LineageOS 14.1, with TWRP 3.1.1-1.

Can't add logcat files, here some links :

Without Magisk : https://goo.gl/84mUrd

With Magisk V13.0(96f8efc)(working) : https://goo.gl/FYzwDg

With Magisk (all versions after V13.0(96f8efc), not working) : https://goo.gl/kHsuDk
[Magisk] otaconremo:
I noticed something on v1400 regarding manager settings on syslemless host. It always disables when I restart my phone or when I cleared manager from tasks.

Is it just on my phone or everyone else's?

Log attached if this helps.
[Magisk] Bright09:
Having issues when trying to update to latest 14.0 I can't reboot in magisk after it installs
[Magisk] awakener777:
Thanks so much. This fixed my bootloop!
[Magisk] Didgeridoohan:
Oops... I was a little unclear (corrected the original post now).

What I meant to say it's that the placeholder file gets removed when you install a module from the Downloads section of the Manager. On a manual install, TWRP or from the Modules section of the Manager, it'll still be there. You'll need to remove the file from your module zips (or folder under /magisk, use Mount Magisk to access it in TWRP) if it's there.
[Magisk] jenslody:
Which device, android version, twrp version ?

Did you reboot after removing traces of xposed_xx in /magisk to see if it works correctly without xposed ?

Can you check for potential recovery logs in /cache ?
[Magisk] punkmonkey1984:
How can I flash the modified boot.img on a stock S7E? Can find a clear answer.
[Magisk] kwanthenewbie:
Better ask in your device forum
[Magisk] smartpr1v4t3:
thanks, ok i understand.

Is there a chance this will be fixed or is this necessary for all old modules?
[Magisk] Didgeridoohan:
It's under investigation... For now you're going to have to do this for any module where the module's creator has left this file in the module zip and automount enabled.
[Magisk] tmviet:
I've Resurrection Remix with Android 7.1.2 and magisk 13.6 , for me it's early install xposed modules on Nougat.
[Magisk] TheFixItMan:
Device - moto g5 cedric

Rom - LineageOS v 14.1

Magisk - v14.0

Twrp flash - successful

Magisk hide - failed

mount /dev/block/loop->/magisk failed with 13: Permission denied

logs in attachment
[Magisk] rgawenda:
About all the recent (v14) boot problems/failures:

After spending a full night trying to set it up, and many failed attempts, over a clean system (removing magisk files/directories and img, and flashing a clean stock image), I got one conclusion.

Xposed v87.2 module (new template), blocks my device (OPO) from booting, it'll stay forever at bootsplash (never got to bootanimation stage).

v87.1 works nicely with v14 (ICYMBI/YMMV/FWIW)
[Magisk] manos78:
Any solution for the lot of users (mainly with Motorola's) with this problem?

:crying:
[Magisk] Didgeridoohan:
That's a known issue with the G5. A faulty implementation of f2fs is the culprit.

There was a change in v14.0 to let MagiskHide function anyway, with certain restrictions (can't save the Hide list on a reboot). I don't see anything in your log about MagiskHide... Have you enabled Core only mode in the Manager settings and made sure MagiskHide is enabled?
[Magisk] TheFixItMan:
No other modules are installed

Both integrity & cts profile fail

If I just use the Linageos su then integrity passes if root is disabled in settings

Therefore I assume there is a problem with hiding root
[Magisk] Didgeridoohan:
Ok. But have you tried enabling the Core Only Mode in the Manager settings and rebooting?
[Magisk] kgirlx:
App Systemizer

Yes, can confirm, app systemizer user still using template 3, which I believe wont work with this magisk 14. Dev said he is busy so no idea if or when it will. I used it for BBS. Wish BBS worked without it.
[Magisk] TheFixItMan:
Yes

Integrity still fails so I'm assuming magisk hide is not working

If I remove magisk than integrity passes
[Magisk] kgb88:
HTC Butterfly 2 Android 6.0.1, twrp latest, I just got fresh magisk 14.0 install, so there is no xposed traces left in magisk. Flash your modified xposed and it immediately reboot into system but Magisk Manager disappeared. Reinstall Magisk Manager again and no loss of Magisk settings. Just xposed cannot be flashed
[Magisk] Didgeridoohan:
Ok... Let's try to get to the bottom of this. Was that log you posted earlier from when you have Core only mode and MagiskHide enabled? If not, make sure both are enabled, reboot and post the new log. I don't think it'll add anything, but if you could post magisk_debug.log from /data as well, just in case.

Also, you're using the "beta" version of v14.0, right. It'll have much more useful logs...
[Magisk] TheFixItMan:
Here are the logs using beta version v14.0 core only mode with magisk hide enabled
[Magisk] tmviet:
For me at rhis moment it's better magisk 13.6 and when ask for update choose NO.
[Magisk] kishd:
Did you wipe cache and dalvik after updating Magisk? I also had integrity tests fail until I wiped cache and dalvik.
[Magisk] TheFixItMan:
Flashed again on fresh Linageos & wiped cache art/dalvik after flashing zips - no effect - integrity still fails if magisk is installed

It's a magisk problem as it passes integrity if it's not installed which suggests it's not hiding root
[Magisk] bielie:
Its ok magisk 14.0 GT I9152 RR 5.8.4
[Magisk] AndroidDeveloperLB:
Oh I see there is an auto-update option. Never mind about it.

About the other issue, what I mean is that I use a custom kernel (ElementalX). I use it only for being able to double-tap to wake feature.

When I install a new version of Magisk, the kernel is gone as so does this feature. I have to manually flash it again after the update of Magisk.

What I'd like to do is to be able to avoid this.

I'd also like to ask if there is a way to create a shortcut to Magisk to go directly to the SU rules (of which apps to grant and which apps to block from root permission).

---------- Post added at 08:05 PM ---------- Previous post was at 08:05 PM ----------

About updates, ok.

About the kernel, I don't understand. See above to understand what I mean. Maybe you didn't understand what I meant.
[Magisk] whitehawk321:
Hi.. I i found one issue in mi note 4 when doing unistall with magisk unistaller not able to boot up.. Stuck at mi logo
[Magisk] cesarXP:
I found a error in my Redmi 3 Lineage 14.1

I can't install magisk modules
[Magisk] Didgeridoohan:
Hmm. I've never had an issue with a Magisk installation removing my custom kernel... If I remember correctly, EX uses anykernel and shouldn't be affected by Magisk. What order are you flashing kernel and Magisk? I'd recommend flashing the kernel first, if you're not doing that already.

The second part of my post you quoted was aimed at another user. It had nothing to do with your query.
[Magisk] otonieru:
Kernel/boot image will need to be patched by magisk on installation process,

There's a chance that magisk restoring your old boot upon installation,

Best exercise when flashing magisk, especially when updating is by flashing your kernel first, followed by magisk :)
[Magisk] jenslody:
I think I found the cause for the bootloop of xposed 87.2 from Magisk repo.

I have prepared patched/modified versions for all xposed zip's from repo for 14.4 and attach them here.

No guarantee for anything, so be sure to have a backup (as usual), especially not for functionality or stability.

The modification should only make it able to boot without the bootloop and for xposed to find the xposed.prop it needed.

The problem is, that xposed.prop is added to /system and adding files to the root of system can lead to a bootloop.

I moved it to /magisk in the installer and patched the app_process*-binaries to find it.

Be aware, that if you uninstall this version of xposed, it will not remove the xposed.prop .

And another important thing, nothing to do with my modifications: you should remove older xposed-modules before installing 87.2, because the naming of the modules-folder has changed from xposed to xposed_{sdk} (e.g. xposed_23).

@moderators: if it is not okay to attach such an amount of files, feel free to remove the attachements, but if possible send me message, I will upload them to my server in this case. But I prefer them to be attached here, because it's easier to see the download-count.

Edit:

There is one problem with this modification: Magisk lists xposed.prop as module, even if it is a file, not a folder, just because it's directly in /magisk.But this is a minor issue, I think, because the upload of the modified versions is done to test whether this is really the culprit for the bootloop and to give @topjohnwu the possibility to fix it in a less hackish way.

Edit 2:

Official xposed-module is updated, also is xpose-installer, look here for more details.
[Magisk] DodoGTA:
Create a directory called "MagiskManager" (without quotes) in your internal storage if it doesn't already exist
[Magisk] danilo_scala:
Magisk only 12 work(install and root but no work safety net , 13 and 14 no install and no work Xperia z5,?premium . I will send log, edit post
[Magisk] koraymers:
Can I dirty flash 87.2 sdk25 over 87

Now I can use magisk 14 with xposed 87 by purify OS without any error
[Magisk] lahceneamine:
Yes you can but it will mess up your device.

Your should uninstall your actual version first (you can leave xposed Installer)

But I don't understand something, if you already have the 87 working well, why would you change ?
[Magisk] koraymers:
Because of Ver 87.2

Is only fix on that build is compatible with magisk 1400?
[Magisk] k0m3n9:
I've installed this after updated to Magisk 14. No bootloop, unfortunately Xposed Installer by dvdandroid shows there's no Xposed Framework installed
[Magisk] jenslody:
I know this, but it seems to work anyway.

I have a fixed version on my system, but [MENTION=4470081]topjohnwu[/MENTION] already has a fix, that will be out soon.

So let's wait for it.
[Magisk] TheFixItMan:
It doesn't replace stock boot.img

Try flashing your stock/rom boot image

If it's a custom rom just take the boot.img from the rom zip & flash it normally with fastboot

For example

fastboot flash boot boot.img
[Magisk] jenslody:
Newest xposed 87.3 needs the just updated xposed installer by @DVDandroid from here.

If it is not (yet) visible on OP, click on Downloads-tab and get the newest version.
[Magisk] grabik.pk:
I can not install the module immediately after installing Magik 14!

It is necessary to boot into the system, only to install the module.

HOW CAN THIS BE CORRECTED?

/maigisk.img is only available after the system + (
[Magisk] bademjooon:
after update to magisk 14 i cant download any module on my mi5 same as busybox show (process error) only i can download madoule from web and flash on twrp to install!
[Magisk] Didgeridoohan:
Known issue. You're probably lacking the MagiskManager folder in the root of your internal storage. If so, create it manually and try again...
[Magisk] [iop]wah:
delete
[Magisk] bademjooon:
its worket thank you but now have another problem after install modules reboot bottom not work ! i think after install busy-box make this problem!
[Magisk] Didgeridoohan:
Another known issue with updating from v13.3. You'll have to clear data for the Manager.
[Magisk] uudruid74:
turn on the Core only mode to test. If that fixes it, you know its either a module or the hosts setting. Turn them off one by one until its fixed.
[Magisk] bademjooon:
im not upgrade from 13.3. install new rom and magisk 14 after install some modules reboot buttom not work and i must restart my phone with power key. its normal or make problems?
[Magisk] love4chat:
It worked with universal safetynet fix module!
[Magisk] huilun02:
Magisk manager prompted to upgrade to v14

Accepted upgrade, flash in TWRP no issues. On attempt to boot it gets stuck at boot animation. Had to flash back to 13.3 to get past boot. Manual flash to v14 in TWRP, still stuck on boot. Staying at 13.3 for now.

OP3T OOS4.1.6 ElementalX 3.07
[Magisk] DawoodSahi:
What xposed version are you using?
[Magisk] huilun02:
None
[Magisk] Didgeridoohan:
If you have any modules installed, before updating to v14.0, make sure that the system folder inside the module directory (under /magisk) doesn't contain the git placeholder file. With v14.0, if a module tries to Magic Mount any new files to the root of /system, your device won't boot... It's under investigation.
[Magisk] huilun02:
So v14 wont work as long as modules are installed?

Or do I just have to remove the git placeholder file and I get to keep my current modules when upgrading to v14? Thanks for the help.
[Magisk] Didgeridoohan:
It's only modules where the module creator have left the placeholder file in the zip that'll cause issues (or modules you download directly from GitHub and install manually). Any modules adding new files directly to the root of /system will cause issues.

Delete the placeholder file and you'll be good to go with all your modules intact.
[Magisk] jenslody:
Just remove the placeholder and to be sure, look if any module mounts a file, which is not present on the original rom, directly below /system.

Any new file mounted to the root of /system seems to lead to a bootloop.
[Magisk] davidk21770:
What file should I be looking for -- /magisk/plugin-name/system/.git?
[Magisk] jenslody:
It should be called 'placeholder', but as I wrote before any file directly in system (not in a folder), that not exists on the device already can cause a bootloop.

EDIT:

To make it clear adding a folder that does not exist can also cause a bootloop, just adding files to existing folders works without problems.
[Magisk] davidk21770:
Ah... Now I get it. Thanks!
[Magisk] Dylanballardlgv20:
For some reason now im getting cts passing and basic integretiy failing on safteynet. Isnt basic integriry checking for apps specifically?
[Magisk] Setialpha:
Not entirely true, adding new folders cause bootloop, too. For example add /system/share/anyfile will bootloop, too, as /system/share does not exist by default. [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] patster98:
Hey guys anyone on latest op3 open beta 23? After I flashed open beta and flashed magisk 14.0 some apps as snapchat or phoenix suddenly force close.. only way to fix this was stick with stock boot ImG and no magisk... Any ideas?
[Magisk] Setialpha:
Read the general support thread, it has that issue covered.
[Magisk] patster98:
Thanks mate!
[Magisk] Scudria:
I read the post and couldn't get snapchat to work

here's what I have tried

using magisk hide (and selecting snapchat) in addition to using magisk core only

clearing snapchat data

using universal magisk hide or some module name like that still didn't work (whether I enabled or disabled magisk hide)

I've done all of that WHILE PASSING SAFETYNET CHECK

snapchat still refuses to work.

anyhelp would be appericiated
[Magisk] :
I enable Systemless host in last version of magisk but after every reboot, it is disabled.. In 2 devices..

Erase data doesn't solve the problem. Any advice?

Thanks,
[Magisk] holozis_HUN:
I got processing error, any solution? when i want to downlaod modules via magisk app....
[Magisk] jenslody:
Thank you, I edited my post to make it more clear.

---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------

Does your internal storage have the MagiskManager-folder ?

If not, create it and try again.
[Magisk] guest4711:
Check, whether it's really disabled. I own two devices where it shows 'disabled' but it mounts the virtual hosts... You can see it e.g. in settings of 'AdAway' or in /magisk/.core/hosts

And the settings are stored correctly in /data/data/com.topjohnwu.magisk/shared_prefs/com.topjohnwu.magisk_preferences.xml :

<boolean name="hosts" value="true" />
[Magisk] patster98:
Can't seem to find the post anywhere.. could you please link me?
[Magisk] Scudria:
Search for the word snapchat in the post you'll find people having same problems and probable solutions .
[Magisk] TalkingWaterfall:
This should really get added to the FAQ in the start. Thanks for the help, it worked!
[Magisk] mystique47:
same here. oneplus 5, aicp rom
[Magisk] comfygnome:
Hey,

So I installed Magisk v14.0 (1400) and every time I try installing a module after it downloads it starts processing with the error following after "Process error"

Any ideas?

Running Cosmic Os 7.1.2
[Magisk] kuyakom:
Bug? I try to uninstall some modules but still exists in magisk manager and I can't click the delete icon any solution?
[Magisk] :
Thanks for this man.. You are write, it is enabled there..
[Magisk] SuperSandro2000:
Did you reboot?
[Magisk] mystique47:
solved! thank you really
[Magisk] tmviet:
I don't know if this will be hopefull for you.

I download magisk v.13.6 zip

I go to settings/stop magisk manager/disable .

After a/m Open the apk magisk and choose disinstall.

Reboot in recovery TWRP and flash magisk v.13.6 zip
[Magisk] kuyakom:
Of course.
[Magisk] Didgeridoohan:
Manually delete the module folders. You'll find 'em under /magisk.

The root cause of your issue is probably a bug with module template v4 that has been fixed with template 1400. If you keep getting the "Module will be updated at next reboot" message even after rebooting, install the module through recovery instead.
[Magisk] kuyakom:
I see. Thank you
[Magisk] Jmorenor:
Error Install patched_boot with ODIN

Hello,

I have a Samsung Galaxy Note 3 (N900A). at the moment of mounting the patched image of magisk ODIN shows me the following error:

https://drive.google.com/file/d/0B__Kn6Uw82PZVEVZU0x0NTI0ZGc/view?usp=sharing
[Magisk] oTeMpLo:
We all have same error :(
[Magisk] :
DELETED.

---------- Post added at 06:57 PM ---------- Previous post was at 06:56 PM ----------

Create a folder under SDCARD named "MagiskManager" that should fix your issue.

EDIT: Still works.
[Magisk] oTeMpLo:
Ok.. it really works..

What is workaround for "reboot never completes" bug?
[Magisk] Elie.Be:
Hello, i have a question..

what the advantage of "systemless host* in magisk setting? I mean, does it affect system to block ads which load more faster or even slower when executing (e.g loading web pages, etc)

I don't use any adblock apps.. Just edited the /system/etc/hosts file manually.

So what i should do.. enable the systemless host in magisk setting or don't have to? Thanks guys..
[Magisk] gothicVI:
As far as I understand the advantage is that you don't modify /system

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[Magisk] comfygnome:
I see. Thanks mate :good:
[Magisk] Elie.Be:
lol i know that.. that's why it called ''systemless" ;) But that don't answerd my questions.. thanks anyway
[Magisk] guest4711:
The functionality does not change when you enable or disabled systemless hosts - the processes use the systemless hostfile as it were located on /system/etc/ But when you update your ROM all your changes to a real hostfile are gone because it is overwritten by the default version (containing only 127.0.0.1 localhost) while the systemless hostfile would survive flashing a new ROM or wiping system...
[Magisk] Jmorenor:
Hi, I do not understand the instructions you give me. I do not have recovery, try installing with ODIN installation method. Maybe as the N900A model has the bootloader locked does not allow installing Magisk
[Magisk] Elie.Be:
Ok so thats it.. no specific advantage? that means no necessary to enable it, right? I'd just copy-paste the host file after installing new ROM then.

Thank you for your answer..i got it.
[Magisk] :
The bootloader is locked so you can't use magisk as locked bootloaders do not allow for modified boot images, and magisk modifies the boot image. The same issue occurs with my Galaxy S7 from sprint.
[Magisk] Didgeridoohan:
By that, do you mean that you're stuck on the splash screen (bootloop)? Make sure none of the modules you're installing are Magic Mounting any new files or folders to the root of /system. The most common culprit would be the placeholder file in the system folder of the module. Remove it from the zip before flashing or if you've already flashed the module and can't boot, flash the Mount Magisk zip in recovery, navigate to /magisk/<module name>/system and delete the file manually.
[Magisk] guest4711:
Right, if you don't depend on safety net then you could leave it disabled...
[Magisk] Didgeridoohan:
The main thing is that it's systemless, which brings another advantage you might not have considered:

As long as you don't wipe /data (where the Magisk image is stored), you won't have to copy-pasta the edited hosts file after a ROM upgrade... Flash and forget. :good:

Other than that it'll behave just like any other custom hosts file.
[Magisk] Elie.Be:
Thanks both for useful answers! I got it..

But wait, from what you just said, it is relate with safetynet also? Why is that? because a 'modified system'?

I've safetynet check passed within magisk manager (with systemless host disabled). I thought "magisk hide" did it, not systemless host thing, right?

I guess "unlocked bootloader" detection is the main problem for everything, isn't it?
[Magisk] Didgeridoohan:
Well... There is a possible check for a modified /system in the SafetyNet API. I've never seen it being used though... On one of my devices I've edited /system quite a lot and have always been able to pass SafetyNet.
[Magisk] tanfidzularus:
Please help. Seems my online banking app still detect magisk. The app won't open keep showing error message

"ER-R53 : msg_root. Already installed universal safety net fix.

Any work around to solve the problem?

Sorry do post
[Magisk] Artim_96:
Return to your stock ROM and quit using any modifications. Or quit using banking apps all together. It obviously had root detection beyond the understanding of Chainfire and topjohnwu, so they can't work around them.
[Magisk] eriuzz:
same here process error when try to install modules on resurect remix 7.1.2 and before that samething happen on Stock g4 mm
[Magisk] guest4711:
As mentioned a lot of times, you should create a folder under SDCARD named "MagiskManager". That should fix your issue.
[Magisk] Magdy Yassen:
Created The Folder And Still Same Problem Here !!
[Magisk] demonoidmaster:
I'm quite serious, Magisk 4.3.3 / v12 has no issues installing modules, never had an issue
[Magisk] Bryanx86:
Also works on angler, here's debug.log. had one issue with apps showing up in superuser in magisk app, but after rebooting everything was normal. S.i.Xrom, after flashing arise 5/24 with magisk module, had to re-grant superuser permissions.
[Magisk] Ubimo:
Latest magisk works on my Samsung Galaxy S7 edge with SuperMan rom 2.5.0. Module is working too. Although the log is very long and something is repeating itself. Is this normal?