yashsingh1/xdaforums huggingface dataset:
[Magisk] Artim_96:
Since you have a Moto you might have this problem too.

You should look into the Moto forums to find a Magisk version that installs itself to /cache. At least there should have been one for the old F2FS bug.

Maybe topjohnwu can implement such a workaround together with a test that first tests if anything is working properly, otherwise logs for a ext4 partition to install itself to

---------- Post added at 10:48 PM ---------- Previous post was at 10:47 PM ----------

Yes. But maybe first of all, restore your boot.img, v13.3 seems to have some bugs there
[Magisk] wl03355609:
Just asking

I had magisk mount as systemless

Sometimes the manager stuck in FC

So I just flash the zip again then it work as charm

But I did that again and I think something is wrong

Pic attached below

Did it mount itself as system?
[Magisk] Didgeridoohan:
There's nothing wrong there...
[Magisk] wl03355609:
Whoops my fault

Didn't system need to be mount as system(RO)?
[Magisk] Didgeridoohan:
Yes. And that's what's happening... I don't see anything about mounting /system rw from your screenshot.
[Magisk] wl03355609:
So it's systemless anyway?

THX for your patience:crying:
[Magisk] Didgeridoohan:
No worries... And just to put your mind at ease, here's what's happening at that point of the installation script (note the ro):

ui_print "- Mounting /system, /vendor, /cache, /data"
mount -o ro /system 2>/dev/null
mount -o ro /vendor 2>/dev/null
mount /cache 2>/dev/null
mount /data 2>/dev/null
[Magisk] wl03355609:
Okay Thanks
[Magisk] kwanthenewbie:
Magisk forced close after I clicked the tab "Download".

Attached logs
[Magisk] Simonex16:
And how can I do that?I'm on LG g3 d855 fulmics 7.6 magisk 12.0 and Xposed framework 87(I repeat that just for sure)
[Magisk] Artim_96:
If you have TWRP boot into it and flash the image under /data. There should be a backup. But I don't know if that will work without bumping. If not go to your devices forum and find out how to bump it
[Magisk] woozie.2007:
One time after few days, the root disappear and the magisk manager force close, after restart all its ok. But i can't understand why the magisk manager force closed after few days....is a big mistery. Stock 7.0 moto g5

magisk 13.3 and manager 5.1.1

anybody knows why its happen?
[Magisk] Matt.Murdock:
I have a clean system installed, so I unlocked it, installed TWRP and flashed Magisk. It works for the apps, however I cannot get into /system. How come? I checked if the phone is rooted and it is, but when I try to enable root - e. g. in https://play.google.com/store/apps/details?id=com.rhmsoft.fm.hd&hl=cs this file manager, it says that my phone is not rooted.

I am clueless... what's wrong? I turned off hiding from apps, didn't help
[Magisk] Artim_96:
Not without logs. Next time you probably should boot to TWRP and get the Magisk logs from there
[Magisk] zelendel:
Use a different file explorer. Many have issues with touching the system partition due to not detecting root properly. Root Explorer has been the go to for many years for a reason.
[Magisk] affliction_emrah:
Hi guys,

Have an issue with my U11.

Unlocked my bootloader and then boot in twrp, didn't flash it to be able to have OTAs, mounted as read only and made full backup, then for achieving root privileges flashed Magisk and all went great.

Now, OTA arrived, booted in twrp again, restore everything but data, tried to flash OTA but it stucked at %24. Tried a few times, same... Tried to mount twrp as read only and restore that way but didn't allow me.

Any suggestion?

Thanks in advance
[Magisk] Simonex16:
Ok thanks i'll do that ;)
[Magisk] dtective:
Hi guys,

Any chance of getting Barclays working without uninstalling Magisk? I'm not sure how Barclays app is detecting Magisk package...

Are you both on Android O? If so, Android O has a new 'Verify Apps API' which it might be using to query the state of apps/detect 'harmful' apps (Magisk being listed as one).

It was mentioned at Google I/O 17: https://youtu.be/C9_ytg6MUP0?t=421

I'm using Android 8.0, Magisk 13.3, Magisk Manager 5.1.1, Barclays 1.48 - getting stuck at splash screen.
[Magisk] Artim_96:
No, every app can just get a list of installed apps. Verify apps is just Google's "Malware" detection which can't be used by other apps afaik and Magisk isn't listed as harmful, otherwise you'd get a warning upon installation
[Magisk] olivercervera:
lol for Magisk being a Harmful app according to Google.

No, we are not on Android O, I believe both on Android 7.1.x, but according to my logcat Barclays is indeed having a look at installed apps.

I miserably failed and gave up, but [MENTION=1095206]daleski75[/MENTION] may be able to help, he managed to get Barclays working by uninstalling Magisk Manager.

I will wait the next Magisk Release, it should include a temporary Magisk Manager Hide. I can't stay without the Manager anyway!

I was lucky enough to backup the apk of Barclays 1.42. It works by simply using Magisk Hide. I don't know for how long Barclays will allow it. I can send it to you if you'd like.
[Magisk] dtective:
Please read again. I'm talking about the Verify Apps API in Android O. It's now possible for other apps to do the same check, although I'm not saying that is what's being done.

I totally forgot to backup 1.42, so yes, please, that would be very helpful.
[Magisk] olivercervera:
Will send you a PM.
[Magisk] ascii024:
Hi, I'm using LineageOS with no Custom kernel Or any modification and I want to hide that from banking apps, never used it and don't have root, help me please :crying:
[Magisk] Didgeridoohan:
Are you asking for help on how to install Magisk? If so you'll find installation instructions in the release thread and also some info in the installation and troubleshooting guide.

If not... you'll have to be clearer with what it is you want help with.

There are many variables besides root and other modifications (Xposed, etc) an app might check for and deem that your device is unsafe. Unlocked bootloader, ro.build.tags set to test-keys, permissive SELinux, and so on...
[Magisk] ascii024:
I want to use the App from my bank and it doesn't Open because it says my devices system has been modified (obviously) and in a other thread they todo me to use magisk to hide it, since I've never used the App I installed it via TWRP but so far I don't Know how to proceed from there. Went to magisk hide and selected the App but it did nothing, don't Know if that the way to do it.
[Magisk] Didgeridoohan:
If you have Magisk installed and a functioning MagiskHide (test by running a SafetyNet test or by hiding root from a root app), adding the app to the Hide list should work. But, there are many apps that use methods of detection that we simply can't bypass.

What's the app in question? Post your Magisk log (you can save it from the log tab in the Manager).
[Magisk] ascii024:
Here is the log.
[Magisk] Didgeridoohan:
Everything looks fine. IIRC, I've seen other reports about Banamex's app not being fooled by MagiskHide...

Are you sure that MagiskHide is functioning properly on your device? Like I said earlier, test with a SafetyNet check in the Manager or add a root app to the Hide list and see if it can still detect root. Read through the troubleshooting guide I linked you earlier. It has a lot of tips like the ones I'm giving you now...
[Magisk] Artim_96:
Still, Magisk isn't listed as dangerous or even potentially dangerous, otherwise you'd see a warning by verify app. But apps where always able to see other apps. I think the only restriction there is that since N they aren't allowed to detect what's running. But they can still just look at a list of installed apps and as long as Google doesn't replace their VM with something like Docker which would make sharing between apps extremely cumbersome, or make the list of installed apps readable only by the system, that won't change
[Magisk] xAlejli:
Hello guys.

How to pass the SafetyNet check? It always fail.
[Magisk] shadow2483:
Will Pay money for assistance in Rooting LG Stylo 3 Plus Need help ASAP

I kindly need help in Rooting LG Stylo 3 plus I have Team Viewer Whoever is able to do this please Get back with me please and thank you
[Magisk] oreo27:
How's v14 working for everyone?
[Magisk] nathanchance:
All fine here on OOS 4.5.10
[Magisk] PraneethMv:
Installed. So far no issues. Pretty good. :p :D
[Magisk] woozie.2007:
i installed now, the root is ok, will see if safetynet pass and how stable is this version, i hope i will not loose the root randomly. Thank you very much
[Magisk] PraneethMv:
I'm getting v14.0 as latest. Yours is v13.6 :confused:
[Magisk] nathanchance:
I have the beta channel set which apparently hasn't been updated.
[Magisk] PraneethMv:
Oh. Ok thank you
[Magisk] spetrie:
I have version 1.46 if you like. It works fine with Magisk. I too am waiting for a solution for latest Barclays version.
[Magisk] dtective:
Yes, I'd appreciate if you could send that to me, please.

Just a heads up: Barclays app (version 1.48) still not working on Magisk 14/Magisk Manager 5.3.0, even with new 'Hide Magisk Manager' option or after uninstalling Magisk Manager manually.
[Magisk] i6rb:
Same here

☕
[Magisk] denzel09:
After last update something has been broken in my side. Previously all worked.

Now i have ctsProfile error and basicIntegrity error :(
[Magisk] ProtoKun7:
My Nexus 6P still passes SafetyNet on 14.0 but my Pixel C doesn't (neither did it on 13.6). Not sure what's stopping it; tried Core Only and still failed.

It's not as important on the C admittedly but I'd still like to get it to pass. This is after flashing the 8.0 images (minus wiping userdata) so I'm not sure what's getting in the way.

Uploaded a log I captured just now.

EDIT: Solved my own problem. Because I'd been having trouble before with looping into recovery (the culprit ended up being Magisk 13.3), I'd foregone the modified kernel; after flashing that too I'm getting all green again.
[Magisk] Didgeridoohan:
Toggle MagiskHide off/on, Magisk log, etc, etc...
[Magisk] chudy_85:
New version v14.0 work very good wit android 7 on huawei p9 with security path 1 August 2017. Thanks
[Magisk] Frankyfunkz:
I keep having the problem where some modules say "Module will be updated at next reboot", but after rebooting/power off+on/restart it will still say that.

Anyone know what the issue is? Google isnt giving me any help.
[Magisk] Didgeridoohan:
Have you updated to Magisk v14.0?

You might have to manually remove the "update" file in the module folders (or the entire module folder) under /magisk before you can get it working again (after updating Magisk, if you haven't already).
[Magisk] Frankyfunkz:
Yeah I'm on 14.0, all checks are green and safety net too.

Just the modules saying that.

Do I just delete the whole /update folder?

---------- Post added at 07:51 PM ---------- Previous post was at 07:48 PM ----------

I meant to say the update files in the module folders.
[Magisk] Chocklety Boyee:
Hey brother i flashed magisk xposed v87.2 and got stucked on boot logo ..is there any help so that i can use magisk 14 and latest xposed magisk??
[Magisk] Didgeridoohan:
Hm... That should have been fixed in v14.0...

Are the modules otherwise fully functioning and installed? But, yes, I was talking about the update file. If the module is otherwise working, just delete that file. If it isn't working, delete the whole module folder and try to install it again.
[Magisk] XyByDy:
what if all the steps have been tried and we're still getting failed SafetyNet with v14.0?
[Magisk] Didgeridoohan:
Logs or it didn't happen.
[Magisk] westeight:
The problem with the latest Barclays app (29th August) has nothing to do with Magisk. It's a bad update - read the comments on the Google Play Store.

Only solution: use the previous version of the Barclays app :cowboy:
[Magisk] XyByDy:
--------- beginning of main

I( 2627: 2627) Magisk v14.0(1400) daemon started

I( 2627: 2629) ** post-fs mode running

--------- beginning of system

I( 2627: 2652) ** post-fs-data mode running

I( 2627: 2652) * Mounting mirrors

I( 2627: 2652) mount: /dev/block/bootdevice/by-name/system -> /dev/magisk/mirror/system

I( 2627: 2652) link: /dev/magisk/mirror/system/vendor -> /dev/magisk/mirror/vendor

I( 2627: 2652) bind_mount: /dev/magisk/mirror/bin

I( 2627: 2652) Create /data/magisk.img with size 64M

I( 2627: 2652) * Mounting /data/magisk.img

I( 2627: 2652) * Running post-fs-data.d scripts

I( 2627: 2652) * Running module post-fs-data scripts

I( 2627: 2652) * Loading modules

I( 2627: 2660) * Starting MagiskHide

I( 2627: 2660) hide_utils: Hiding sensitive props

E( 2627: 2660) fopen: /magisk/.core/hidelist failed with 2: No such file or directory

I( 2627: 2660) hide_list add: [com.google.android.gms.unstable]

I( 2627: 2660) proc_monitor: init ns=mnt:[4026531840]

I( 2627: 3073) ** late_start service mode running

I( 2627: 3073) * Running service.d scripts

I( 2627: 3073) * Running module service scripts

I( 2627: 2660) proc_monitor: zygote ns=mnt:[4026534300] zygote64 ns=mnt:[4026534301]

I( 2627: 2660) proc_monitor: com.google.android.gms.unstable (PID=7685 ns=mnt:[4026534334])

I( 7690: 7690) hide_daemon: Permissive detected, hide the state

I( 7690: 7690) hide_utils: Re-linking /sbin

I( 2627: 2660) proc_monitor: com.google.android.gms.unstable (PID=8698 ns=mnt:[4026534334])

I( 8703: 8703) hide_daemon: Permissive detected, hide the state
[Magisk] Frankyfunkz:
The issue remains.

Deleted the modules' folders, rebooted. Installed a module to test (Greenify4Magisk), rebooted, same issue.
[Magisk] Didgeridoohan:
There seems to be an issue with your Magisk installation:

E( 2627: 2660) fopen: /magisk/.core/hidelist failed with 2: No such file or directory

Do you have a "hidelist" file in /magisk/.core?

Did MagiskHide work properly on your device prior to updating to v14.0?

Have you tried uninstalling and reinstalling Magisk?

What happens if you type the following in a terminal emulator:

su
magiskhide --disable
magiskhide --enable

---------- Post added at 21:15 ---------- Previous post was at 21:11 ----------

Could you upload a Magisk log from the reboot after installing a module, please.

And what happens if you install the module through recovery?
[Magisk] Chocklety Boyee:
How to grab logs? Can you plz let me know the exact steps plz..
[Magisk] XyByDy:
Well, everything seemed fine with the rom based on Android 41.2.A.7.35 and Magisk 13.3.

But I got failed SafetyNet after clean installation of the updated version of the same rom based on 41.2.A.7.53 with Magisk 13.6 and now v14.

I do have hidelist file on /magisk/.core path but maybe it was created after re-enabling magiskhide on terminal emulator.

Here's the new log file

--------- beginning of main

I( 2627: 2627) Magisk v14.0(1400) daemon started

I( 2627: 2629) ** post-fs mode running

--------- beginning of system

I( 2627: 2652) ** post-fs-data mode running

I( 2627: 2652) * Mounting mirrors

I( 2627: 2652) mount: /dev/block/bootdevice/by-name/system -> /dev/magisk/mirror/system

I( 2627: 2652) link: /dev/magisk/mirror/system/vendor -> /dev/magisk/mirror/vendor

I( 2627: 2652) bind_mount: /dev/magisk/mirror/bin

I( 2627: 2652) Create /data/magisk.img with size 64M

I( 2627: 2652) * Mounting /data/magisk.img

I( 2627: 2652) * Running post-fs-data.d scripts

I( 2627: 2652) * Running module post-fs-data scripts

I( 2627: 2652) * Loading modules

I( 2627: 2660) * Starting MagiskHide

I( 2627: 2660) hide_utils: Hiding sensitive props

E( 2627: 2660) fopen: /magisk/.core/hidelist failed with 2: No such file or directory

I( 2627: 2660) hide_list add: [com.google.android.gms.unstable]

I( 2627: 2660) proc_monitor: init ns=mnt:[4026531840]

I( 2627: 3073) ** late_start service mode running

I( 2627: 3073) * Running service.d scripts

I( 2627: 3073) * Running module service scripts

I( 2627: 2660) proc_monitor: zygote ns=mnt:[4026534300] zygote64 ns=mnt:[4026534301]

I( 2627: 2660) proc_monitor: com.google.android.gms.unstable (PID=7685 ns=mnt:[4026534334])

I( 7690: 7690) hide_daemon: Permissive detected, hide the state

I( 7690: 7690) hide_utils: Re-linking /sbin

I( 2627: 2660) proc_monitor: com.google.android.gms.unstable (PID=8698 ns=mnt:[4026534334])

I( 8703: 8703) hide_daemon: Permissive detected, hide the state

I( 2627: 2660) proc_monitor: com.google.android.gms.unstable (PID=10207 ns=mnt:[4026534323])

I(10219:10219) hide_daemon: Permissive detected, hide the state

I( 2627: 2660) proc_monitor: com.google.android.gms.unstable (PID=11769 ns=mnt:[4026534441])

I(11774:11774) hide_daemon: Permissive detected, hide the state

I( 2627:14676) * Stopping MagiskHide

I( 2627:14696) * Starting MagiskHide

I( 2627:14696) hide_utils: Hiding sensitive props

I( 2627:14696) hide_list: [com.google.android.gms.unstable]

I( 2627:14696) proc_monitor: init ns=mnt:[4026531840]

I( 2627:14696) proc_monitor: zygote ns=mnt:[4026534300] zygote64 ns=mnt:[4026534301]
[Magisk] zzudha:
please anyone tell me, who successfully installed magisk v14 with custom kernel? I'm stuck on samsung logo (powered by android) & not boot.

I use spacelemon battery extended v2.91.22 custom kernel & refined v3.7.6 custom Rom on Samsung galaxy note 4 n910h & I don't have stock boot.
[Magisk] verma.arun833:
Any chance to install magisk on locked bootloader on sony Xperia z3+ running stock 7.0 non rooted nd no recovery......just want to know ?
[Magisk] heri1978:
Updated v14.0, run good on my mega 6.3 lte, RROS 5.8.4, Security patch 5 August.
[Magisk] Pkt_Lnt:
Read "new installation method" in the v.14 release post.

https://xdaforums.com/showpost.php?p=73690093&postcount=29
[Magisk] Frankyfunkz:
Fixed it by flashing the zip files through TWRP. Thank you!
[Magisk] Artim_96:
No. You have to unlock the bootloader since you need to be able to fish a modified boot image. Only exception are Samsung devices since these can be flashed with ODIN... Which most likely will exclude the locked down is versions
[Magisk] Psy_Man:
Bootloop on Xiaomi Mi Note 2 with 14. Switched again to 13.3.
[Magisk] soder:
I'm on a OnePlus 3T. Had previous non beta version installed. Got notification about updating Magisk Manager and did it.

Then I said yes to install the new version of Magisk, and during boot the boot animation was laggy every 4 or 5 rotation of the animation.

I forced the phone to recovery and reflashed the ROM and also Magisk 14. Same problem happend.

Then reflashed the ROM again and then Magisk 13.3 and it booted normally.

Later I tried to install some module, but got errors.

Are the latest versions working?

/Söder
[Magisk] Didgeridoohan:
https://xdaforums.com/apps/magisk/guide-magisk-troubleshooting-t3641417 (section: "Asking for help")

And does it work now, after toggling hide in terminal? How about after another reboot (and what does the Magisk log look like after that)? Does v13.3 work on the updated ROM?

Logs or it didn't happen...

---------- Post added at 22:51 ---------- Previous post was at 22:48 ----------

I have Magisk v14.0 installed on my OP3T (OOS 4.1.7) with no issues. Have you tried a clean install of v14.0?
[Magisk] saccentekennedy:
Hey guys,

I'm on Magisk 13.3. I hadn't even noticed there had been new versions! Here's what's holding me back upgrading to 14... My modules... I'm not 100% sure they've been updated by their devs to the new module template.

At the moment, everything is working. Magisk hide... I'm able to use my banking apps and across Android pay. All my modules work (a discontinued Viper mod which works perfectly on my OP5, systemless substratum, deep buffer remover, Google dialler mod, stereo speaker for OP5 mod). Will upgrading likely break some or all of them if they're not using the new template?

Basically, is there any reason to upgrade of everything is working fine?
[Magisk] broomer68:
Happened the same to me tonight.

I am on open beta14, and have some modules installed. Reflashed 13.3 and things got running again.

Verstuurd vanaf mijn ONEPLUS A3003 met Tapatalk
[Magisk] nexbr:
I'm using the latest update 14.0, and any module I install I get "module will be updated on the next reboot" in red on the bottom of the module, I tried to fix by rebooting several times, the problem persists, I tried to search for a fix but no success, anybody can help me?

--------- beginning of main
I/Magisk ( 228): Magisk v14.0(1400) daemon started
I/Magisk ( 228): ** post-fs mode running
I/Magisk ( 228): ** post-fs-data mode running
I/Magisk ( 228): * Mounting mirrors
I/Magisk ( 228): mount: /dev/block/platform/mtk-msdc.0/by-name/system -> /dev/magisk/mirror/system
I/Magisk ( 228): link: /dev/magisk/mirror/system/vendor -> /dev/magisk/mirror/vendor
I/Magisk ( 228): bind_mount: /dev/magisk/mirror/bin
I/Magisk ( 228): * Mounting /data/magisk.img
I/Magisk ( 228): * Running post-fs-data.d scripts
I/Magisk ( 228): * Running module post-fs-data scripts
I/Magisk ( 228): * Loading modules
I/Magisk ( 228): * Starting MagiskHide
I/Magisk ( 228): hide_utils: Hiding sensitive props
I/Magisk ( 228): hide_list: [com.google.android.gms.unstable]
I/Magisk ( 228): proc_monitor: init ns=mnt:[4026531840]
--------- beginning of system
I/Magisk ( 228): proc_monitor: zygote ns=mnt:[4026534133]
I/Magisk ( 228): proc_monitor: com.google.android.gms.unstable (PID=3744 ns=mnt:[4026534149])
I/Magisk ( 3750): hide_utils: Re-linking /sbin
I/Magisk ( 228): proc_monitor: com.google.android.gms.unstable (PID=6611 ns=mnt:[4026534170])
I/Magisk ( 228): proc_monitor: com.google.android.gms.unstable (PID=7908 ns=mnt:[4026534346])
I/Magisk ( 228): proc_monitor: com.google.android.gms.unstable (PID=11946 ns=mnt:[4026534337])
[Magisk] 3lMghraby:
v14 breaks safety net for my device

hTC U11
[Magisk] jamy015:
Hey [MENTION=8369284]topjohnwu Magisk Queries[/MENTION] , do you have a different way to donate than PayPal? I would like to send some cash your way but unfortunately PayPal has blocked my account. (Creditcard? Bank transfer? Bitcoin?)
[Magisk] Dorisnov:
Anyone can't install MagiskManager 5.3.0? When I try to install says "damaged package".
[Magisk] KND19:
The same happens to me. Maybe it's Miui 9? I use the ROM 7.8.31.
[Magisk] 3lMghraby:
could you guys check wether safety net passes for you on v14 ?
[Magisk] The~Skater~187:
Upon upgrading from Magisk 13.3 to 14. I got stuck on Samsung splash screen. To fix this I rebooted into recovery, restored my backup. As soon as phone loaded I went into Magisk (13.3) disabled all modules I had loaded and reflashed Magisk (14) and started to re enable modules, rebooting in between each one, until I found the culprit that was keeping my phone from booting. Don't know if it will help anyone, but if your having bootloops, try what I did. I attached a picture to show which module was causing my bootloop issue, SD card write enabler.

My device setup is:

Samsung Galaxy S5 (Sprint/Kltespr)

Resurrection Remix (08/12/17) build

Boeffla Venom Kernel

CQD1 Firmware
[Magisk] akpe:
Passes for me, just tried

Στάλθηκε από το HTC 10 μου χρησιμοποιώντας Tapatalk
[Magisk] The~Skater~187:
I can confirm Safety Net passes here
[Magisk] Istvan_86:
SafetyNet Ok in OP 3T!!! Thanks!!!
[Magisk] jenslody:
If the module template is not updated it will not work on Samsung phones, because of hardcoded path to magisk below /data.

Samsung kernel does not allow apps running from below /data to execute other apps.

If old templates are used, it should still work from TWRP.
[Magisk] brian_h_kim:
v14.0 - updated from v13.0(96f8efc) - working on Pixel C [8.0.0 (OPR6.170623.010, Aug 2017)], including passing SafetyNet...
[Magisk] jenslody:
Same here on my J5 with MarshMallow.

My modified xposed still works, from TWRP or MagiskManager: https://xdaforums.com/showpost.php?p=73416017&postcount=2810

I will try to dig into it ,if I find the time.
[Magisk] Legendary Cryptid:
So if I'm to understand, restoring stock boot image with the new Magisk update doesn't get rid of your custom recovery, right?
[Magisk] mrceli:
do I have to uninstall magisk 13.3 first to upgrade or just upgrade from the manager?
[Magisk] martyn987:
So I'm using a Galaxy S7 edge from T-Mobile. I feel like I'm probably just blind and completely missing this information. But is my phone compatible with this? And if so, what are the steps and processes involved with installing it safely?