yashsingh1/xdaforums huggingface dataset:
[Magisk] mfr122887:
https://xdaforums.com/showpost.php?p=74196515&postcount=4308

This process allows the module to show in Magisk pre-reboot and the Magisk hide list is writable. However, after a reboot the settings are wiped out.

Here's another log from a fresh install

10-23 18:37:33.056 443 443 I Magisk : Magisk v14.3(1437) daemon started
10-23 18:37:33.103 443 451 I Magisk : ** post-fs mode running
10-23 18:37:38.126 443 594 I Magisk : ** post-fs-data mode running
10-23 18:37:38.126 443 594 I Magisk : * Creating /sbin overlay
10-23 18:37:38.127 443 594 I Magisk : * Mounting mirrors
10-23 18:37:38.127 443 594 I Magisk : bind_mount: /system_root/system -> /dev/magisk/mirror/system
10-23 18:37:38.127 443 594 I Magisk : mount: /dev/block/dm-0 -> /dev/magisk/mirror/vendor
10-23 18:37:38.127 443 445 E Magisk : fopen: /cache/magisk.log failed with 1: Operation not permitted
10-23 18:37:38.127 443 594 I Magisk : bind_mount: /data/magisk -> /dev/magisk/mirror/bin
10-23 18:37:38.127 443 594 I Magisk : * Setting up internal busybox
10-23 18:37:38.224 443 594 I Magisk : Create /data/magisk.img with size 64M
10-23 18:37:48.262 601 601 I Magisk : Magisk v14.3(1437) daemon started
10-17 22:53:00.581 601 805 I Magisk : ** late_start service mode running
10-17 22:53:00.581 601 805 I Magisk : * Running service.d scripts
10-17 22:53:00.581 601 805 E Magisk : opendir: /magisk/.core/service.d failed with 2: No such file or directory
10-17 22:53:00.581 601 805 I Magisk : * Running module service scripts
10-17 22:54:35.797 4398 4398 I Magisk : Magisk v14.3(1437) daemon started
10-17 22:54:35.798 4398 4410 I Magisk : * Starting MagiskHide
10-17 22:54:35.798 4398 4410 I Magisk : hide_utils: Hiding sensitive props
10-17 22:54:35.798 4398 4410 E Magisk : fopen: /magisk/.core/hidelist failed with 2: No such file or directory
10-17 22:54:35.798 4398 4410 I Magisk : hide_list add: [com.google.android.gms.unstable]
10-17 22:54:35.933 4398 4410 E Magisk : fopen: /magisk/.core/hidelist failed with 2: No such file or directory
10-17 22:54:35.933 4398 4410 I Magisk : proc_monitor: init ns=mnt:[4026531840]
10-17 22:54:38.008 4398 4410 I Magisk : proc_monitor: zygote ns=mnt:[4026534252] zygote64 ns=mnt:[4026534243]
10-17 22:54:41.402 4398 4410 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=4654 ns=mnt:[4026534347])
10-17 22:55:08.160 4398 6392 I Magisk : hide_list add: [com.americanexpress.android.acctsvcs.us]
10-17 22:55:08.187 4398 6392 E Magisk : fopen: /magisk/.core/hidelist failed with 2: No such file or directory
[Magisk] Didgeridoohan:
That's unfortunately not a useful recovery log. You need to save it right after flashing something for it to show anything. It's especially useful with "Error 1", since that can mean many things...

Make sure that the Manager has storage permission, or uninstall 5.3.0 and install 5.4.0 manually (download from the release thread).

If MagiskHide otherwise works and you've added the app up the Hide list and also tried hiding the Manager but the app still can find root... Well... That's tricky, ain't it?

What app are we taking about here?
[Magisk] hajalie24:
Does anyone know why I can't boot into my phone's OS after flashing Magisk 14... I can boot fine with magisk 12. Despite Magisk 14 or 13.3 flashing just fine once I restart my phone it stays on the LineageOS boot animation indefinitely.

Phone is a galaxy note 4 with LineageOS 14.1
[Magisk] k0m3n9:
it's here

It might probably found "/sbin/su".. because from attachment only "/sbin/su" exists & visible on my device after root via Magisk.
[Magisk] Mickyman:
Everything works like a charm here after updating to v14, magisk hide also works fine!
[Magisk] Didgeridoohan:
Yeah... No, I'm not gonna install that to test. :laugh:

MagiskHide should hide that though, so either your setup ain't working or it's looking for something else. Developer options enabled and/or USB debugging are two things that Magisk can't hide and that sometimes trigger things.
[Magisk] biribiribiri:
I am using pixel xl with stock oreo and magisk 14.3. I have a really weird problem. When I boot up my phone, safetynet works fine, but after a few hours, safetynet would fail and I have to reboot to get it working again. I don't see anything in the magisk log either. Does anyone have any idea why this might happen?
[Magisk] hopelives:
I'm using v12 and when I tried to update to v14 via Magisk Manager I got this screen and didn't apply update after reboot.
[Magisk] Wolfcity:
It seems another program like SuperSU for example has already patched your boot image. Extract stock boot.img out of your current ROM and flash it through twrp.

I would recommend to uninstall magisk 12 with the magisk uninstaller and install v14 from scratch.
[Magisk] DodoGTA:
Can you pull and attach the /cache/magisk.log file and a logcat (if it's possible to get it)?
[Magisk] hopelives:
Thank you but I guess I missed the part in which installation through Magisk Manager possible if you have v14+ part. I now tried to install via TWRP and still got some errors and didn't install v14.
[Magisk] veez21:
Logs would be helpful (recovery.log)
[Magisk] Didgeridoohan:
SuperSU compatibility was dropped with Magisk v13. If you have SuperSU installed you'll first have to do a complete unroot and also reinstall Magisk.

More details here:

https://xdaforums.com/apps/magisk/guide-magisk-troubleshooting-t3641417
[Magisk] hopelives:
So if I want to continue using both magisk and SuperSU then I must stick with the v12, right?

Before I tried to update magisk I attempted to install magisk4greenify module but it also returned with error. Was this because the magisk version? If so, it means no further update to any module including xposed framework via magisk manager doesn't it?
[Magisk] Didgeridoohan:
You're correct on all accounts.

If you want to use SuperSU you'll have to stick to Magisk v12, which in turn means that you won't be able to install any modules from the Magisk repo and will only be able to install modules that have been made with template v3 or earlier. There will also be no support for a Magisk version that old.

Move with the times, man... :p
[Magisk] hopelives:
Thank you mate. I installed Magisk to go on easy with Xposed so I need to consider the situation. It's hard to change good old habits. :)
[Magisk] ante0:
Any of you guys got Magisk running on Oreo (Huawei/OPO3/Maybe more)?

For some reason I now have partitions ramdisk_a and kernel_a instead of boot (Is this Android now or just Huawei?).

ramdisk_a doesn't contain everything required for systemless Magisk/SuperSU, and I saw someone posting that OPO3 had ramdisk files moved to /vendor?

It's just a beta for Mate9 so right now it doesn't matter, but once it's out of beta I'd love systemless instead of system install.

I'm going to investigate more as soon as I've downloaded update through HiSuite.

Edit: Alright. So fstab is present in /vendor/etc/.

sepolicy is not present in ramdisk, but it is in recovery_ramdisk. I wonder if I could just copy and paste it and see what happens :eek:
[Magisk] suirzes:
and whoom should i present it?
[Magisk] Pkt_Lnt:
Put it on cloud site and link it here with a tag for topjohnwu.

You can attach as a zip, but just *do not* copy and paste into a reply. please.

Thanks!
[Magisk] suirzes:
[MENTION=4470081]topjohnwu[/MENTION]

I get a bootloop after flashing systemless sposed.

SM-N950F, running 7.1.1, TWRP, Magisk 14.3.

View attachment logcat.rar
[Magisk] baskaflyfer:
Hi, magisk don't work on Oreo!!! But I did several tests and it work fine(including SafetyNet). I found a solution!!! I'm on OP3
[Magisk] Fif_:
That was a weird log format, in UCS-2?

Magisk seems to be working properly and installing the Xposed overlays, but Xposed never starts.
[Magisk] suirzes:
Mate, i have no idea what you mean by weird. Could you explain that in layman's words? Is it too short, or something? :)

All i did is follow all the https://github.com/rovo89/XposedBridge/wiki/Bugs#how-can-i-get-logs
[Magisk] maddler:
Hope not to upset you, but despite everything else working flawlessly, SafetyNet still fails on Oneplys 5 with 4.5.13 :)

debug_log here https://nxt.eth0.it/index.php/s/lxbeSbAw4b3Sx2x
[Magisk] dominj97:
Are you sure?
[Magisk] cubandanger05:
This happens to me often on lineage rom. Just hit the overview button ? on your navi bar and go back to the installation screen and the instal button won't be grayed out anymore
[Magisk] maddler:
Absolutel 100% positive.

Only difference I can see I'm on the 128/8G variant. But can't really see how that could make any difference.
[Magisk] dominj97:
What modules do you have?

Sent from my OP5
[Magisk] maddler:
No modules currently enabled. Just need sudo.
[Magisk] BrikHaus:
Hey Guys,

Need some advice. I have a Note 4, running Nameless ROM v6 (6.1.1 based) that I have previously had Root (SuperSU to Magisk) and

Xposed working just fine. I updated my SnapChat yesterday, and had to uninstall both to be able

to login. I am now attempting to re-install Magisk & Xposed, but I'm not having any luck.

I have a fresh Boot image in TWRP. (And a recent Nandroid backup)

My method has been to flash the fresh boot image, and then install Magisk via zip in TWRP.

It reports successfully patched, however I get stuck in boot, with a flashing 'Samsung' logo.

(I have left this run for an hour at a time, and around 3hrs last night. But it doesn't complete)

I will then re-flash my clean boot image, and it will Optimise Apps, and I will, after an hour

be back up again.

So I need help figuring why this isn't working. Previously I had SuperSU and Xposed installed

BEFORE I moved to Magisk. But I have read that I can install a systemless Xposed through Magisk.

But obviously Xposed requires root, which I can't get as Magisk gets stuck in a loop.

I have the latest Magisk apk installed, and the zip flash version is the latest 14.
[Magisk] storm68:
Magisk is also root.....
[Magisk] BrikHaus:
I know. But I can't get to System. I get stuck in boot.

That's my problem...
[Magisk] candiesdoodle:
What's the solution?

Pl share
[Magisk] BrikHaus:
I think I have it sorted. I had 'FolderMount' as a Magisk module.

I deleted /Data/Magisk.img and reflashed Magisk14.zip over a fresh boot image, and it seems to be progressing to the App Optimisation stage.

Fingers crossed.
[Magisk] Joe_6pak:
Still having problems installing Magisk (see my earlier post - #19911). I tried again last night with no luck. I did get a recovery log that may be of some help and it is attached. Thanks for all who tried to help - hopefully this will give you some more information.
[Magisk] teddy0209:
Isn't sudo a xposed module?
[Magisk] Didgeridoohan:
And you don't have any remnants of any other root solution, Xposed, etc...?

You might try a clean flash of your system. Since we know it should work, there's obviously something about your device that's gotten messed up.

Your device isn't compatible with Magisk, simple as that. Or rather, the boot image isn't (unknown ramdisk format). Try v14.3 beta, something might have updated. If that doesn't work, upload your boot image file and maybe [MENTION=4470081]topjohnwu[/MENTION] can take a look at it.

It's also possible that a custom kernel that replaces the ramdisk could fix it. But that would be a question for your device's forum (if there is one).
[Magisk] Sam Nakamura:
Magisk doesn't work on OOS with stock kernel - flashing a custom kernel and then Magisk should work though, blu_spark's is the first (and only yet to this point?) who released a OOS Oreo kernel yesterday, I think...

Not a OOS user but that's what I would try
[Magisk] candiesdoodle:
Nope. Even Blu spark doesn't play with magisk. Only SuperSU.

There r unstable workarounds out thrre. But [MENTION=7846474]baskaflyfer[/MENTION] seems to have a stable one.
[Magisk] ivivaitylin:
Hey guys. New magisk user here and been having a couple of problems with modules not appearing. Tried to search through the thread but maybe I wasn't searching for the right thing or something. Did find a few other people asking something similar but no actual answers. Anyway, my problem:

Recently took my Nexus 6p from stock marshmallow to the latest lineage to stock 7.1.2 and installed magisk for the first time. This was a little tricky because twrp didn't seem to stick and I kept having to install it through fastboot to actually get into it. But this also seems to be a known issue with magisk. Not a big problem though. Magisk installed and running fine, passing safetynet too. Install xposed, reboot, seems fine. Xposed modules installed without a problem. Install IYTB manually following the instructions in that module thread, reboot and now no modules appear in magisk. I've tried reinstalling the modules, even downloaded a new module through magisk but that doesn't appear after a reboot either. I've attached the magisk log, though there doesn't seem to be too much in there. I still have root working fine through magisk at least!

Also attached a screenshot of the main magisk page in case that helps.

Running a nexus 6p,stock 7.1.2 image from the Google page, magisk 14.0, magisk manager 5.4.0.

Thanks in advance, happy to answer any questions.
[Magisk] Didgeridoohan:
The Magisk image might be corrupted... Uninstalling Magisk and reinstalling should fix it.

Also, I'd actually consider trying v14.3 beta... There's been a lot of work done to improve stability. I'm using it as my daily driver on all my devices...
[Magisk] njascgil:
This thread is gigantic, so I'm not sure people will find this, but just in case this helps someone...

Using both the 9/9 and the 18/10 versions of Material Xposed Installed, I always had the message "framework is installed but not active" shown to me even if xposed kept working just fine.

I manage to solve the problem by deleting an extra (older) xposed folder from /magisk and rebooting.

Now, v88 (sdk23) version is correctly detected and shown as active.

It seems that Magisk Manager v5.30 or v5.40 (I'm not really sure which one) kept the xposed module v87.3 folder while upgrading the module to v88.
[Magisk] ivivaitylin:
Thanks, I'll give that a go. Would I need to uninstall any of the installed modules as well, or should the newly installed Magisk detect them automatically?

Edit: Booted to recovery, ran the uninstaller, wiped davik/cache, ran the installer. Back into android and still no modules. Going to just wipe everything and start from scratch again.
[Magisk] Didgeridoohan:
Ah yes... I believe this was mentioned by [MENTION=4470081]topjohnwu[/MENTION] in the release post for Xposed v88. The module name has changed (which is used to create the folder) so any previous version would have to be uninstalled...

When you run the uninstaller all modules are deleted. They are kept in the Magisk image, which is removed when you uninstall Magisk. All modules need to be reinstalled...
[Magisk] ivivaitylin:
You know, this is one of those things that seems really obvious in retrospect. I have no idea why I thought installed modules would persist through a complete Magisk uninstall!
[Magisk] innit:
hey guys, do you know if magisk hide and magisk modules can be used with super su from chainfire? will the safetynet pass or will it be triggered? thanks in advance
[Magisk] Didgeridoohan:
You should probably read through the release thread:

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

TL;DR: No.
[Magisk] innit:
well it doesn't answer any of my questions
[Magisk] Didgeridoohan:
But I did. Edit: And so does that thread if you keep reading...
[Magisk] DodoGTA:
https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/post69196610
[Magisk] maddler:
Nope, Magisk provides sudo. ;)
[Magisk] k0m3n9:
Hi.. are you talking abt Sudohide module for Magisk.. Would you kindly provide the link, coz I didnt found it in Magisk repo.. it's only exists in Systemless Xposed repo.

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

I didn't know about this.. on my KLTE running LOS 14.1 + Magisk 14.0.. It managed to update Systemless Xposed sdk 25 from 87.3 to 88.1 without problem. But on my J1 Ace Neo running deodexed stock rom lolli 511 + Magisk 14.3.. even fresh install Systemless Xposed sdk 22 88.0 giving bootloops. Using Magisk Mount deleted it's folder and installed back 87.3.
[Magisk] Didgeridoohan:
No such module for Magisk. I think he means superuser, su, root, etc...

I'm not entirely sure... Taking this from memory and I don't use Xposed.

Edit: I was partly right. :p It wasn't Xposed v88 that brought this change, it was v87.2.

https://xdaforums.com/showpost.php?p=73728137&postcount=4369
[Magisk] ivivaitylin:
Sorry, me again! Almost everything is working smoothly now, there's just one app I'm having trouble with. It's a payment app for a supermarket, you can put your card details into it and it displays a qr code on the screen that can be scanned to enter your loyalty card and pay at the same time. It checks root on startup, previously I'd been able to use rootcloak from Xposed when I'd been on marshmallow, but now I'm on magisk, hide doesn't seem to cut it.

As you can see from the log, I did some testing using a root checking app, and it does correctly hide root from that app when enabled/disabled like you would expect. Unfortunately I can't offer any more details on the way it checks to see if you are rooted, though given it didn't detect Xposed when I had it installed in system, I don't think having it systemless would cause this.

It asks for location and phone call permissions when you first start it up, but I tried to add these al to magisk (not sure if I got them all) but that didn't help.
[Magisk] dratsablive:
I read that latest Magisk supports Pixel A/B partioning. So is it safe to assume that it works with the Pixel 2 XL?
[Magisk] Didgeridoohan:
Many apps like that are really tricky. I can't test yours (wrong part of the world), but my test procedure usually looks like this:

Install app.

Make sure SafetyNet passes.

Add app to Hide list, together with anything that it asked permissions for (phone, etc).

Hide the Manager in the Manager settings.

Start the app.

If the above works, great! What I do then is to go backwards... Unhide the Manager - test app. If it still doesn't complain, I also remove it from the Hide list. If still works after that.... well everythings dandy, no? :D What I do then is to clear data for the app (or uninstall and reinstall) and try again. Sometimes an app only checks for root on the first start.

If an app finds root during the above procedure, I then proceed to add it to the Hide list and hide the Manager again to see if that changes anything. If the app still can find root I clear data for the app and start over. Some apps keep a record of having found root and won't start after that, even if Magisk is successfully hidden.

To figure an app out you can decompile the apk, use strace, etc. It's usually quite hard to figure out though...

It's safe to say that it might work, unless Google changed something, which they usually do, so it's probably not gonna work. :laugh:

If Magisk doesn't work out of the box on Pixel 2, it'll most likely will eventually.
[Magisk] ivivaitylin:
Thanks for the pointers, I'll give those things a go. I know the app doesn't use safetynet because I was able to use it previously on a supersu and xposed system with just rootcloak, so I certainly didn't pass safetynet back then.
[Magisk] K2silver:
Doing a CLEAN install for the second time on S7 W8 with Superman ROM 2.7 (which has been confirmed by the OP as passing SafetyNet and Certified on GooglePlay app)

When I boot into freshly installed system device is uncertified under GooglePlay app and Magisk is reporting ctsProfile: false ??

What has gone wrong? I am LOST

thanx for the feedback XDA :D

running Magisk 14.2
[Magisk] weeks101:
Just got my Pixel 2. Is there a write-up for installation yet?
[Magisk] Bingley:
.doh
[Magisk] daniel_loft:
I have a short suggestion! I don't seem to find any mention of something similar so here it is:

It would really be nice to have some sorting options in the Download section. Something similar to what Xposed has. This way one could find out the newly updated and, more importantly, the newly created modules.

Thanks for the great work!
[Magisk] nameback:
I'm having a very strange problem. When I have Magisk installed, using my camera makes the phone appear to shut right off. I have a 6P with stock everything, and TWRP installed, which I have eliminated as the issue. I'm running the factory 8.0 image with the Oct security patch. I have tried 14 and 14.3 and they both cause the same issue.

The weirdest part is that I am unable to restart my phone after it shuts off, it will not turn on until I plug it back in. I am using a brand new OEM replacement battery I installed last week.
[Magisk] Didgeridoohan:
That does sounds exactly like the regular 6P battery issue. The camera uses a lot of juice and a dodgy battery can't handle it... Maybe you got a dud with that battery replacement.

If you've confirmed that it only happens with Magisk installed, it might be that you've got some other process active with Magisk that pushes the battery over the edge in conjunction with the camera.

---------- Post added at 23:30 ---------- Previous post was at 23:23 ----------

If it's possible out of the box, the official installation instructions should do it.

Are you saying that there are no apps shown at all in the Hide list, as in there's nothing to select? Oreo permissions issue, maybe? I haven't looked into updating to Oreo yet...
[Magisk] GalaxyS3only:
In Lineage-Thread, i found somebody with the same problem and a workaround: if airplanemode is enabled there won't be a problem with doze...

[MENTION=4470081]topjohnwu[/MENTION] [MENTION=4667597]Didgeridoohan[/MENTION] they said i should tell u about this bug, cause its in magisk, so maybe u know a fix?

thx & greetz
[Magisk] GalaxyS3only:
my Log:
[Magisk] weeks101:
How do I get the stock boot image dump?
[Magisk] Oscar.Wilde:
Running 14.3 on my S8+ with Reno N8 port / Noto 211 Kernel and no matter how clean or thorough I reinstall/flash Magisk (with the ROM/with the kernel/Solo after setting up the former two), I keep getting Random Root Losses (btw... maybe I misunderstood something but the new "invincible" mode that should be restarting / keeping root alive, well NO root loss recovered itself so far. I was actually asking myself if I missed to check an option for it maybe?!).

Restarting solves this in 99% of the cases but needless to say it's really annoying and the randomness of the event does contribute to that even more. Sometimes it happens instantly after reboot, sometimes after hours....

Interestingly, the Magisk Manager shows 14.3 as latest version after a clean install/flash. After the first loss of root and reboot it suddenly shows 14.0 to be the latest version, next loss and reboot it's supposedly 14.3 again?!

I am actually surprised that I haven't seen a lot of root loss reports in this thread since the release of 14.3.

As well in the ROM as the Kernel Telegram group people confirm the issue on a frequent basis now.

Will add a log to this post as soon as the next loss comes up, I admit frustration has gotten the better of me and I didn't bother since the next reboot is only a *sigh/eyeroller* long....promise.

Modules installed: - Systemizer, Doze 1+ 2, F - Droid & Greenify Extensions, Viper 4 Arise Compatibility Module, Sysconfig Patcher.....

I'd say usual suspects.

No Xposed.

Am I (and the other dozens of fellas...) missing something?!
[Magisk] Didgeridoohan:
A logcat from when the problem occurs is necessary.

Wait for a factory image to be released or search how to do it with adb.

You're not missing anything. The invincible mode should work as far as restarting the daemon is concerned. You can test this by manually killing the daemon... Look in the Magisk log. The first number after the date and time is the one you want (look at the last line). Open up a terminal emulator and type:

su
kill [I]<number>[/I]

Now you should see in the log if the daemon restarted.

It's possible there are other issues going on for you. You know... Samsung doesn't do normal. :laugh: That log would be great for finding the issue.