yashsingh1/xdaforums huggingface dataset:
[Magisk] Dylan Hameleers:
The restore on bootup... it gives a message saying couldnt acquire root acces... when i go into the magisk app it says no root installed... and after a minute or 2 it says magisksu
[Magisk] JLius:
Hi

I just flasht miui latest global dev rom on my redmi note 3 pro, flashed latest twrp, and flashed magisk v12. Root works without problem, but can't pass safety net (magisk cts profile mismatch). Any suggestions?
[Magisk] lepa71:
I'm having issues installing magisk on Nexus 10 running Scanno's Omni 6 rom. I had SupperSU root and uninsstalled it with full root, rebooted to twrp and ran magisk uninstaller. After that I dirty flashed Omni 6 again to get a original boot image. Booted to make sure that system is unrooted and rebooted back to twrp. Than flashed magisk v12.zip. Didn't get any errors, but when I look in Magisk manager, it says I have no root.

Any ideas?
[Magisk] dahawthorne:
The FAQ somewhere mentions that if you want Magisk on your device then you have to upload a copy of your boot image to GitHub. I don't believe that Magisk is an all-device system, it's device-specific, and as far as I can discover nobody, including me, has got it to work on the Nexus 10.
[Magisk] PhilD41:
So I wrote on here a month or two ago having issues with Magisk 12 on my Moto Z Play (unlocked). Root works just fine but Magisk Hide and modules are not functioning. The error I get in the log is as follows:

I am not exactly sure what the issue with the models was (they won't install). This leads me to believe it is a similar write access issue. Anyway, it was recommended to me to remove Magisk and try again. I did that with no change. Recently I ended up having to completely restore my phone with stock firmware to solve a bootloop. I ended up reflashing everything from the addison-user 7.0 NPNS25.137-24-1-4 5 stock firmware floating around. Full details are below:

Once this was complete and functioning I again booted into TWRP (addison 3.1.0) via the fastboot and flashed Magisk. And again, I am experiencing the same performance. Root works fine. MagiskHide will enable, but nothing will pass safetynet and I still have the above error in the log. Models won't install and if flashed through TWRP won't function.

Anyone have an idea what is wrong? Should I be using a different stock image for the Moto Z Play? is there an incompatibility with something in the addison image? I see others using Magisk just fine on this phone. I will ask in the Moto Z Play forum as well, but last time I was sent here as they all pointed to a Magisk issue. I just want to get it to work, modules more that MagiskHid, but both would be very helpful.

Thanks for any assistance you can provide!
[Magisk] Chocklety Boyee:
There is a magiskmodule to pass safety net on dev rom..
[Magisk] user2k10:
Same thing happens here with AFWall, it takes too long for Magisk su to become available at boot.
[Magisk] pehlm:
@Didgeridoohan or someone else with the right knowledge; is it safe to use external (not the inbuilt) BusyBox for Magisk v12.0. I know that BusyBox for v13 is removed but on the Magisk XDA site, @topjohnwu explains that "Many features in v12 are implemented to only work with that specific busybox bundled with Magisk.". So my question is can I safely use Stericson BusyBox with Magisk v12?
[Magisk] dahawthorne:
This looks like a problem with your particular devices/setup, since I have no such problem, and the fact that only 2 people are experiencing this...
[Magisk] Didgeridoohan:
It's perfectly safe to use whatever busybox you like. The worst thing that could happen is that your hamster will run backwards...
[Magisk] tag68:
Did you install the f2fs fix? Without it Magisk can not fully with on Moto Z Play. In Moto Z Play Nougat the loopback device for f2fs (being used for /data where Magisk lives) is partly fixed, but not fully. You may have overlooked this detail. Although I'm not sure how to do this: Usage of f2fs fix is correctly mentioned in every guide how to install Magisk on Z Play that I've seen on xda (that are many).
[Magisk] bundysoat:
How check this? Y web Playstore?

Thanks.
[Magisk] CM Wave:
I'm using f2fs on my Nexus 5. Could that be why Netflix refuses to run despite everything else working fine?
[Magisk] PhilD41:
Thank you, I will give that a try. I had not installed the f2fs since I had also ready may places that the March security patch fixed this. Apparently it was only a partial fix. I will go track that down and give it a go. I appreciate the detailed answer. This is the first I have found that it was not fixed. Granted I have been busy and not researching a lot.
[Magisk] Artim_96:
No, it's only a problem for Magisk itself. And if you use f2fs is on a custom ROM which is most likely completely fixed. If the problem would still exist Magisk shouldn't work at all and most likely cause a bootloop.

Of you completely pass SN and already added Netflix to Magisk hide, it process has to do with DRM. Fur all I know Netflix switched to Googles Widevine DRM. Maybe get DRM test and see if you actually have it built in
[Magisk] teddy0209:
Play Store settings...
[Magisk] CM Wave:
Thanks for the info! I downloaded the DRM Info app and it's telling me my phone supports Google Widevine Modular DRM. I really have no idea why Netflix is refusing to work. I feel like I've tried everything.
[Magisk] lepa71:
deleted
[Magisk] tag68:
Exactly. According to some user reading from the loopback device and therefore the install of Magisk now works, but (at least under some circumstances) the loopback device can't be written. This should be fine if f2fs fix is installed.

I don't know if some error occurs on install because of that partial fix and f2fs is needed before Magisk install, or if it is sufficient just to install f2fs fix now. Would guess the second. You may try.
[Magisk] ScaryBugThing:
I've been trying to get PHH Superuser to work as a manual replacement for MagiskSU with Magisk on a stock Axon 7, since MagiskSU fails to install. This involves Magisk, but also posted on PHH Superuser's thread just in case.

Background: Axon 7 has some problems with Magisk and installing Magisk directly from TWRP never results in MagiskSU actually installing. But using methods I catalog in this thread I am able to install Magisk Manager 12.0, install the separate current PHH Superuser, and pass SafetNet with MagiskHide. The PHH Superuser is in fact shown as "MagiskSU" in Magisk Manager, and listed as properly installed/rooted. The PHH Superuser APK manager also installs fine.

The issue is that after installing, trying to use any rooted app results in a notification window that "[App] is denied superuser rights." Even if I set PHH to grant root access or set it to prompt for access, there is no prompt or allowed notification, and eventually it just fails.

Since Magisk seems functional, I'm inferring the problem must be with the PHH Superuser root. However, a problem for Magisk is that it is not installing MagiskSU so this workaround could be avoided if it does that correctly. Any suggestions how to get a usable root to work with Magisk in this case?
[Magisk] Didgeridoohan:
No idea... I've never used dumpsys before and when I tried it right now on my Nexus 6 with Magisk v12 (MagiskSU) it worked without issue.

Is there any difference if you use a SafetyNet checker from the Play store?

Does Magisk Hide work? Add a root checker or root app to the Hide list and see if it can detect root. A Magisk log is also helpful when troubleshooting...

If I understand your post correctly you're not having the normal problem of Netflix not installing or showing up in the Play store. Correct? You have it installed but can't start it?

Netflix does not (yet) test for root in their app, so you probably have some other issue.

https://xdaforums.com/apps/magisk/xiaomi-safetynet-fix-t3600431

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828

---------- Post added at 08:59 ---------- Previous post was at 08:55 ----------

Have you tried one of the current unofficial beta snapshots? There's been a lot of changes to the code since v12.
[Magisk] Shen Ron:
Have you checked magisk manager for the superuser setting to grant root permissions?
[Magisk] bundysoat:
No buddy. Clear data in Gplay app?
[Magisk] boubaka:
Thank you for this work that allowed me to root my device :D

I don't know if this problem has been raised but let me explain

I use Magisk on an Honor 6X device BLN-L21 / B360 / Emui 5.0 / V7.0 / Booloader unlock / Root

Usually in the settings the fingerprint identification menu is accessible.

But if I check the Hide Magisk option and reboot the device the menu is not available :eek:

If i uncheck option the menu reappears...

Is it normal or not ?

Thanks for your help :good:
[Magisk] teddy0209:
Make sure you pass SN, then clear Play Store data... Wait a bit, might take a while before it shows the status again...
[Magisk] Artim_96:
Does it only say supported or does it actually show a version number and the rest of the information? Because for me it only shows supported but nothing else so I guess it's supported but not available. I don't know which part actually had to contain it, the OS or the app but if no version number or else can be shown is guess it is not there
[Magisk] bundysoat:
Clear data, safety net pass... Netflix continuous not working.
[Magisk] PhilD41:
I flashed the f2fs fix then reflashed Magisk and it worked perfectly. Thank you for the nudge in right direction.
[Magisk] teddy0209:
Does your device appear as certified on play store now?
[Magisk] bundysoat:
Yes, is right.
[Magisk] ScaryBugThing:
Yes, unfortunately. I have it set either to Prompt or Grant always, and it still just gives the error that permissions were denied.

---------- Post added at 02:27 PM ---------- Previous post was at 02:22 PM ----------

Thank you, no, I didn't know about these. Looks pretty straightforward, but to confirm:

I go to a clean install image with no root/magisk, then install the Magisk Manager 5.0 beta APK, and flash the same-date Magisk beta ZIP in TWRP? If it works as intended, I should not have to install a separate PHH Superuser, correct?
[Magisk] ScaryBugThing:
Magisk 20170520 worked. Thank you so much - man, I was up for 5 hours last night, and this solved it. Awesome!
[Magisk] CM Wave:
Yes, that's right. I can view it on the Play store and it instals just fine, it just doesn't run.

It just says supported, no other info.

Could this be an issue with the ROM I'm using? I'm on the latest SlimRoms 7.1.2 weekly.
[Magisk] Artim_96:
Sadly I have no idea. I would need to know how is supposed to look on an unchanged, stock ROM. And like I said, I don't know if the rest is just a module that the app brings song itself like the exoplayer or if it had to be fully built into the system
[Magisk] hjmrox:
Titanium Backup Restore with Magisk

I just migrated from AOSPA 6 to PureNexus 7.1.2_r8 with magisk root. I'm trying to restore app+data from Titanium Backup. TiBu just crashes when I try to open. Anyone having experience with this can advice me please?
[Magisk] Didgeridoohan:
I do not think you have an issue that Magisk can help with. Provided a logcat to your ROM's developer and hope they can find something.
[Magisk] Yooshaw:
Is your ROM using sdcardfs? I ask because a user on another ROM that had it enabled from a ROM update, disabled it, and apps like Mario Run started to work again.
[Magisk] Artim_96:
1. Besides Samsung there aren't that many using it (yet, maybe Google really adds it to O), chances are very low

2. Is Mario run even using any external DRM? Because I have the same problem, I can almost guarantee that sdcardfs is not available in any version of my ROM. And the only changes I know about in Netflix is the bad made exclusion of root users and the switch to Widevine DRM.

I googled a bit around, it's possible that it has to be included as a plug-in in the app but I'm not sure. But if he really passes SN, either there is a bug or Netflix searches for more than only SN
[Magisk] pancomido:
I am having a bit of trouble to pass Safety Net on MIUI.

If I start the daemon from the terminal it works. I read I could automate this by adding a script to something like Kernel Adiutor. But I'm not sure how to do that. I tried using the init.d settings adding the lines

su

sh /magisk/.core/magiskhide/enable

Same as I do on the terminal. But it doesn't work. any ideas?

Thanks!
[Magisk] Didgeridoohan:
Try adding "su -c" to the last line of the enable script. Like so:

(su -c $BINPATH/magiskhide --daemon)

It's been known to work with this issue.
[Magisk] Telperion:
Anyone with feedback on why this could be exhibiting such behavior: https://xdaforums.com/showpost.php?p=72355184&postcount=13662
[Magisk] Alucard:
I always ,on many decices i used ,got safetynet failed,but i can play pokemon go,is there a way to pass this and if not what are the problems i will face?
[Magisk] pancomido:
Thank you, Digeridoohan.

Should I add this to the script I mentioned or should this be the whole script? Also are the parentheses necessary?

I'll try to check if it works when I get back home. :)
[Magisk] teddy0209:
Add it to the enable script under /magisk/.core/magiskhide

Edit: don't add too many modules, you might lose root... ?
[Magisk] Rush94:
LoL its vierd but my safety net fails over and over.

The reason is magisk is unable to find mahiskhidelist and tried to edit it the whole directory is read-only even the magisk doesn't have access to write in that directory strange right?
[Magisk] teddy0209:
Anyone with more knowledge can take a look at this log?... It's from my test of the 0521 snapshot... Magiskhide does not start properly... All I see is the sqlite3... No output enabling via terminal... ???http://cloud.tapatalk.com/s/59224c0c91e0d/magisk.log.txt
[Magisk] pancomido:
Thanks, Teddy. So just to be clear.

I am doing this on Kernel Adiutor, on the init.d section, and I should create a new setting with the following content:

/magisk/.core/magiskhide
(su -c $BINPATH/magiskhide --daemon)

Is that correct? Thank you!

EDIT: ok, I understand now, I need to modify the enable file directly in the Magisk directory, instead of creating a script on Kernel Adiutor. I read I might lose root though if using this method. I'll check and see. Thanks!
[Magisk] darylzero:
please here is the error log from magisk for the nexus player on nogurt v7.1.2

magisk installed all good

safetynet passed

modules download and install BUT after reboot do not show in the module list hence not active

modules tested adsblock and dolby atmos mod

** Magisk post-fs mode running...

** Magisk post-fs-data mode running...

/data/magisk_merge.img found

/data/magisk.img found, attempt to merge

Expanding /data/magisk.img to 32M...

/dev/block/loop0 /data/magisk.img

/dev/block/loop1 /data/magisk_merge.img

Merging: magisk-foldermount

Merge complete

* Running post-fs-data.d

* Loading core props

* Preparing modules

* Stage 1: Mount system and vendor mirrors

* Stage 2: Mount dummy skeletons

* Stage 3: Mount module items

* Stage 4: Execute module scripts

* Stage 5: Mount mirrored items back to dummy

** Magisk late_start service mode running...

* Linking binaries to /sbin

* Starting MagiskSU

* Running service.d

* Starting MagiskHide

MagiskHide: Moving and re-linking /sbin binaries

MagiskHide: Removing dangerous read-only system props

MagiskHide: Killing com.google.android.gms.unstable

MagiskHide: Starting MagiskHide daemon

MagiskHide: Update process/package list:

MagiskHide: [com.google.android.gms.unstable]

Zygote(0) ns=mnt:[4026532358]

MagiskHide: com.google.android.gms.unstable(PID=2190 ns=mnt:[4026532404])

MagiskHide: Unmounted (/sbin)

MagiskHide: Unmounted (/magisk)

log is from inside magisk module log save section
[Magisk] teddy0209:
Exactly... Just don't add too many modules... I only keep my prop module for SN, and emoji... ?

---------- Post added at 04:29 AM ---------- Previous post was at 04:26 AM ----------

Try installing in recovery... For adblock, you need to activate systemless host in managers settings...
[Magisk] DallasBelt:
Maybe take a look to this thread:

https://xdaforums.com/android/general/guide-extreme-battery-life-t3095884

The OP recommends Greenify + Amplify + Power Nap (which can block wakelocks).
[Magisk] tsjanda:
Not sure if this is a bug or not but I have adaway installed and today when updating the hosts rebooting I find that in magisk app will no longer check for updates of itself get error no internet. However if I deselect systemless host in setting with the magisk app and reselect it it checks for update and all is well. As stated not sure this is by design or a bug when running adaway app. Here is the log

** Magisk post-fs mode running...

** Magisk post-fs-data mode running...

/data/magisk_merge.img found

/data/magisk.img found, attempt to merge

Expanding /data/magisk.img to 32M...

/dev/block/loop0 /data/magisk.img

/dev/block/loop1 /data/magisk_merge.img

Merging: unifiedhostsadblock

Merge complete

* Running post-fs-data.d

* Loading core props

* Preparing modules

Analyzing module: /magisk/unifiedhostsadblock

Replace with dummy: /system/bin

New file: /system/bin/hosts

* Stage 1: Mount system and vendor mirrors

* Stage 2: Mount dummy skeletons

* Stage 3: Mount module items

* Stage 4: Execute module scripts

* Stage 5: Mount mirrored items back to dummy

** Magisk late_start service mode running...

* Enabling systemless hosts file support

* Linking binaries to /sbin

* Starting MagiskSU

* Running service.d

* Starting MagiskHide

MagiskHide: Moving and re-linking /sbin binaries

MagiskHide: Removing dangerous read-only system props

MagiskHide: resetprop by nkk71 & topjohnwu

Initializing...

Modify data structure: 'ro.boot.flash.locked'='1'

Existing property: 'ro.boot.flash.locked'='0'

Recheck property: 'ro.boot.flash.locked'='1'

Done!

MagiskHide: Killing com.google.android.gms.unstable

MagiskHide: Killing com.android.vending

MagiskHide: Killing com.google.android.gsf

MagiskHide: Killing com.google.android.apps.paidtasks

MagiskHide: Starting MagiskHide daemon

MagiskHide: Update process/package list:

MagiskHide: [com.google.android.gms.unstable]

MagiskHide: [com.android.vending]

MagiskHide: [com.google.android.gsf]

MagiskHide: [com.google.android.apps.paidtasks]

Zygote(0) ns=mnt:[4026545139]

MagiskHide: com.android.vending(PID=4121 ns=mnt:[4026545255])

MagiskHide: Unmounted (/sbin)

MagiskHide: Unmounted (/system/bin)

MagiskHide: Unmounted (/magisk)

MagiskHide: Unmounted (/system/etc/hosts)

MagiskHide: com.google.android.gms.unstable(PID=4346 ns=mnt:[4026545200])

MagiskHide: Unmounted (/sbin)

MagiskHide: Unmounted (/system/bin)

MagiskHide: Unmounted (/magisk)

MagiskHide: Unmounted (/system/etc/hosts)

MagiskHide: com.google.android.apps.paidtasks(PID=4780 ns=mnt:[4026545238])

MagiskHide: Unmounted (/sbin)

MagiskHide: Unmounted (/system/bin)

MagiskHide: Unmounted (/magisk)

MagiskHide: Unmounted (/system/etc/hosts)

MagiskHide: com.google.android.gms.unstable(PID=5755 ns=mnt:[4026545218])

MagiskHide: Unmounted (/sbin)

MagiskHide: Unmounted (/system/bin)

MagiskHide: Unmounted (/magisk)

MagiskHide: Unmounted (/system/etc/hosts)
[Magisk] Slay1337pl:
I installed Xposed through Magisk and now my G3 is stuck in a bootloop. Is there any way to fix it from recovery?
[Magisk] veez21:
Mount magisk.img (here) and delete /magisk/xposed folder
[Magisk] Didgeridoohan:
From the time stamp it doesn't look like the sqlite error is related to Magisk Hide. I'd have to dig through the code a bit too know what it's about though.

Could you clear the log, do a SafetyNet check and check the log again?

Why are you using both AdAway and the Unified Hosts module?

I've never heard of that issue before. But the hosts file blocks urls, which would explain the lack of connection. Can't say why it started working again though. If it's reproducible you could do it while capturing a logcat (I find that a bowl of cream or some fresh salmon usually lures them out :laugh:).
[Magisk] Leechoonhwee:
--------- beginning of main

06-15 23:08:11.464 I/Magisk ( 421): Magisk v13.0 daemon started

06-15 23:08:11.464 I/Magisk ( 421): ** post-fs mode running

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

05-22 08:05:08.716 I/Magisk ( 421): ** late_start service mode running

05-22 16:05:08.718 I/Magisk ( 421): * Running service.d scripts

05-22 16:05:08.718 I/Magisk ( 421): * Running module service scripts

05-22 16:05:09.138 I/Magisk ( 421): ** post-fs-data mode running

05-22 16:05:09.472 I/Magisk ( 421): merge module xiaomi-safetynet-fix

05-22 16:05:09.522 I/Magisk ( 421): * Mounting /data/magisk.img

05-22 16:05:09.552 I/Magisk ( 421): * Running post-fs-data.d scripts

05-22 16:05:09.553 I/Magisk ( 421): * Loading modules

05-22 16:05:09.983 I/Magisk ( 421): * Running module post-fs-data scripts

05-22 16:05:09.984 I/Magisk ( 421): xiaomi-safetynet-fix: exec [post-fs-data.sh]

05-22 16:05:10.451 I/Magisk ( 421): * Starting MagiskHide

05-22 16:05:10.451 I/Magisk ( 421): hide_pre_proc: Hiding sensitive props

05-22 16:05:10.456 E/Magisk ( 421): resetprop: prop not found: [ro.boot.flash.locked]

05-22 16:05:10.456 E/Magisk ( 421): resetprop: prop not found: [ro.boot.warranty_bit]

05-22 16:05:10.456 E/Magisk ( 421): resetprop: prop not found: [ro.warranty_bit]

05-22 16:05:10.458 I/Magisk ( 421): hide_list: [com.google.android.gms.unstable]

05-22 16:05:10.486 I/Magisk ( 421): hide_list: [com.dbs.ideal]

05-22 16:05:10.508 E/Magisk ( 421): read failed with 3: No such process

05-22 16:05:10.508 I/Magisk ( 421): proc_monitor: init ns=mnt:[4026531840]

05-22 16:05:12.573 I/Magisk ( 421): proc_monitor: zygote (32-bit) ns=mnt:[4026534262] (64-bit) ns=mnt:[4026534261]

--------- beginning of crash

05-22 16:05:34.079 I/Magisk ( 2618): * Starting MagiskHide

05-22 16:06:43.482 I/Magisk ( 421): proc_monitor: com.google.android.gms.unstable (PID=4086 ns=mnt:[4026534405])

05-22 16:06:43.483 I/Magisk ( 1056): hide_daemon: Permissive detected, hide the state

05-22 16:06:43.483 I/Magisk ( 1056): hide_pre_proc: Re-linking /sbin

05-22 16:06:43.494 I/Magisk ( 1056): hide_daemon: Unmounted (/sbin)

05-22 16:06:43.498 I/Magisk ( 1056): hide_daemon: Unmounted (/magisk)

05-22 16:07:57.780 I/Magisk ( 421): proc_monitor: com.dbs.ideal (PID=5795 ns=mnt:[4026534398])

05-22 16:07:57.792 I/Magisk ( 1056): hide_daemon: Unmounted (/sbin)

05-22 16:07:57.793 I/Magisk ( 1056): hide_daemon: Unmounted (/magisk)

05-22 16:20:48.608 I/Magisk ( 421): hide_list add: [com.airfrov.airfrov]

05-22 16:21:00.966 I/Magisk ( 421): proc_monitor: com.airfrov.airfrov (PID=9795 ns=mnt:[4026534340])

05-22 16:21:00.968 I/Magisk ( 1056): hide_daemon: Unmounted (/sbin)

05-22 16:21:00.968 I/Magisk ( 1056): hide_daemon: Unmounted (/magisk)

05-22 16:23:31.475 E/Magisk (10719): read failed with 2: No such file or directory

05-22 16:23:48.502 E/Magisk (10796): read failed with 2: No such file or directory

05-22 16:24:14.876 I/Magisk ( 421): hide_list rm: [com.airfrov.airfrov]

Any idea what to do? It was working before and suddenly safety net failed
[Magisk] teddy0209:
Will install again later, I don't currently have twrp as I just took an ota...
[Magisk] yochananmarqos:
Check what Adaway is blocking when Magisk checks for updates.
[Magisk] ItzShadowz:
Discussion About safety net:

Since SafetyNet was updated a few months back which detects if the bootloader is unlocked or not, has anyone been able to use Android Pay recently (with Magisk + Magisk Hide and dm-verity disabled)?

Asking this so I don't embarrass myself when I try and pay with it to find out that it won't allow me to when I put my phone up to pay for stuff.

Back in the days of phh Superuser to play Pokémon Go, I could use Android Pay until I actually put my phone up to the chip&pin, where it then would then tell me that "My device is incompatible as it may be rooted/unlocked bootloader" or whatever.

I know this has been mentioned before, but with updates to both SafetyNet and Magisk I thought it was worth asking to see if Android Pay is working without any issues despite an unlocked bootloader and root.