yashsingh1/xdaforums huggingface dataset:
[Magisk] battoniko:
Thx for your great job and for the time you took to explain the problem faced.

I'm on Lollipop (no update to marshmallow possible) with magisk and systemless xposedv86.5. Worked well until safetynet changed the systemless check.

Now 86.5 is not supported anymore so i'll stop using it and hope you'll find a way to solve it (if you have the time and decide its worth trying to solve the problem).

As of today, i dont know any workaround to this problem (suhide only works with Android 6+)...if you have knowledge of any workaround please let me know.

Whatever, big thanks and continue your great job!
[Magisk] Captain_Throwback:
Wrong thread.

But all you have to do is disable Xposed and reboot....
[Magisk] battoniko:
Yep, wrong thread indeed, my bad.

I know that i just have to disable xposed and reboot but i need xposed enabled.

Thanks anyway because i didnt mention it.
[Magisk] raleva:
Sorry man, where is the correct thread?? I think this would be ok :o
[Magisk] Son-j:
You may have flashed in improper order, mine worked.

0. Go to recovery

1. Magisk v6. Wipe

2. Phh-supersu. Wipe

3. Reboot to system.

4. Install magisk manager. Reboot to recovery

5. Super.unSu. Wipe. Reboot to system.

Voila! Toggles work. :)

I don't know if you can do everything in one go (while in recovery) before rebooting to system.
[Magisk] mrro82:
Is there a way to speed up the time it takes this app to"un-root" ? I ask because PlayStation Vue still sees it's rooted when I open it. Android Pay works great though. Just curious.
[Magisk] goodtimes50:
Android Pay seemed to work when viewing the app, and SafetyNet Helper shows that it passes, but AP failed when I tried it in a store today.
[Magisk] Krunk_Kracker:
Thanks for the reply! So I need to unsu.zip last?
[Magisk] greenys':
First. Clean dalvik & cache. Then try again. If you still get bootloops then you should do a dirty flash of your system: 1) download the latest rom package for your device 2) then opengapps 3) Magisk (but don't flash beta. Use stable only) 4) Cusrom kernel if you need. In this order.

If that won't work then clean wipe everything except for internal storage and external of you have. Repeat the steps above.

In case it still wouldn't work you might need to format data and wipe everything. Corrupted internal storage might cause some serious problems. But before doing that make sure to backup all the data you find important. Steps are same as previously. In my past 10 years of rooting this always solved my problems with bootloop or anything that had something to do with wrong boot.
[Magisk] Kyrat:
Hi, magisk hide doesn't work with Movistar Play app on galaxy tab s2 T710 with LOS 15.1
[Magisk] greenys':
Interestingly Magisk 19.0 loses root sometimes. Rarely like daily 1-2 times and the manager shows as if it wouldn't even be installed. After a reboot it's fine and dandy. Weird.
[Magisk] Didgeridoohan:
What if you just force close and reopen the Manager whenever it happens?
[Magisk] :
Unable to install the new update installation failed?
[Magisk] DinIslamJoy:
i just switched to another rom and everytjing is perfect now:)
[Magisk] Clandaries:
Is it possible to use Magisk on the new Android 9.0 for PX5? I have rooted it via ADB and now have root with SuperSU. But i would like to use Magist to use Xposed.

Regards
[Magisk] lipippo:
Sorry for not reading the 3283 pages of the thread, but, isn't magisk manager supposed to update magisk?

The documentation says ""If you already have Magisk installed, it is strongly recommended to upgrade directly via Magisk Manager".

I have magisk v17.1 installed, I open magisk manager, it prompts me to install MagiskManager v7.1.1(203), I consent, I open the new manager and it tells me it cannot work with magisk less than v18 :confused:

I installed an old version of MagiskManager (6.1.0 (165)) but I cannot find a way to update magisk within the application.
[Magisk] Didgeridoohan:
Download the Magisk zip and install it by selecting it through the the plus button on the Modules page of the Manager.
[Magisk] greenys':
Nothing. Still writes no Magisk is installed and apps lose root till reboot.
[Magisk] toti8430:
Hi John Wu. I have a special request. I need your own version of magisk to bypass the detection of the root or bootloader unlocked in the Google pay app. Until February I had no problem despite having the bootloader unlocked and magisk installed. Obviously Google itself has made settings to increase the security of the app itself. I am attaching a screen to the problem. I am available to make a generous PayPal donation.
[Magisk] jcmm11:
https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
[Magisk] valarenki:
Magisk on Note 3 N900v

Hello. I am having an issue rooting with Magisk on a Samsung Galaxy Note 3 N900V LTE model on Android 5.0 . Apparently this device has a bootloader that can only be unlocked via root. But from what I can read online for Magisk, it needs to be what you root with. I have successfully rooted, installed TWRP and Magisk Manager. I have attempted flashing a patched boot img and using TWRP to flash Magisk to the device along with a few other steps amounting in 2 days of troubleshooting. From what I can tell I believe I need to have an unlocked bootloader and non root but I can't figure out anyway to do so and have Magisk install successfully. Unfortunately it's an older phone so there isn't much documentation made recently on it.
[Magisk] Sammy336:
I need help on how to root my gionee s10 lite
[Magisk] sssarg:
I forgot to uninstall->restore images before I went ahead and installed the OTA update.

Is there a solution at this point to keep my root? Or should I just reboot to finish the update and then reinstall Magisk through a recovery? Will I keep my currently installed modules?

Device: OP 6T
[Magisk] guest4711:
Yes, the modules are kept. Hide list and root permissions, too. All data goes to /data/adb/ (on newer magisk versions) rsp. /sbin/core/.magisk
[Magisk] sssarg:
So what is the smoothest route to go back to a rooted phone from here? Reboot and finish the update, I suppose. Do I need to go recovery and install full OTA and flash magisk? Uninstall magisk and then reflash?

Edit: I just completed the install, and then installed twrp and magisk. Nothing fancy, though the youtube vanced module has disappeared from my app drawer. Disabling the module makes youtube to reappear. Enabling again and I find no youtube app again. Weird.
[Magisk] :
Nevermind... Easy solution!! [Fixed]
[Magisk] dspPunk:
Safety Net check is failing on latest oneplus 5 openbeta 30.

I am on latest magisk 19 (beta)

Can anyone help please?
[Magisk] bohemist:
I had the same isse recently when I updated my OP6 to 9.0.5

Wha I did was Disable and Re-enable Magisk Hide, then everything back to normal. SafetyNet passes.
[Magisk] Didgeridoohan:
So... Just for future reference, what was the fix?
[Magisk] :
Clean Reinstall worked for me!!
[Magisk] dimm0k:
any way to get more information on why a module is failing to install? the message I get is "! Installation failed". currently using Magisk v19.0 and all modules from the repo install fine except the custom module I have which simply inserts my VPN certificate into /system/etc/security/cacerts. it works fine using the module template from prior v19.0, but when I update the template to v19.0 it gives that message. I've downloaded the template from github and only put the system/etc/security/cacerts folder and file in. am I missing something?
[Magisk] Vibhav_G:
I flashed Magisk 19 from TWRP, had been using 18.1 previously. Worked fine, but after some time I rebooted and in Manager app it showed no magisk installed.
[Magisk] Ferr1s:
I had the same problem. Did u have any Module activated when flashing 19?

Gesendet von meinem Mi 8 mit Tapatalk
[Magisk] BillGoss:
Did you update the update-binary in the template as mentioned in https://topjohnwu.github.io/Magisk/guides.html?

"You will found out that META-INF/com/google/android/update-binary is a dummy file. If you are creating a module locally for personal usage or testing, download the latest installer module_installer.sh and replace update-binary with the script"
[Magisk] Simon1511:
I have a problem with magisk hide.

I cant activate it. It keeps disabled after I reopen the manager.

When trying to enable it with terminal it says that logcat is disabled. But how do I enable logcat?

Im on an A5 2017 with RR pie
[Magisk] garylawwd:
Dies it pass CTS profile check?

If not then Magisk hide wont work
[Magisk] Simon1511:
It does not pass cts AND basicIntegry

And yes it should work because that is what Magiskhide does
[Magisk] dimm0k:
this was definitely it!! thank you for the reminder! I had read it, but decided not to update to the latest template until weeks after... forgot about this section
[Magisk] MB1983:
Hello we can activate the VoLTE icon on the status bar?

Samsung S7 Android 8
[Magisk] Didgeridoohan:
That depends on how it was disabled in the first place... But, try updating to Magisk v19+ instead. If I understand correctly, logcat isn't necessary for MagiskHide anymore (although I haven't actually tested).
[Magisk] Simon1511:
Is there already a v19?

I thought v18.1 was the newest.

But thank you, I will try!
[Magisk] Didgeridoohan:
Magisk v19.0 is the current beta release, and then there's of course the Canary builds.
[Magisk] Simon1511:
Ok, with v19 I can enable Magiskhide and hide it, but basicIntegry and CTS are still false.

Also Play store shows not certified.

What am I doing wrong?
[Magisk] Didgeridoohan:
Play store is uncertified because of the SafetyNet failure. Have you tried rebooting after enabling Hide?

More troubleshooting tips:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_MagiskHide_Issues
[Magisk] dope77:
updated my phone to one ui ,cant get magisk to work.

tried flashing 18.1 ,19.0 through recovery , but always same message in manager (Magisk not installed)

also tried patching boot.img ,sane result

how to fix this?
[Magisk] AndrzejDwo:
You can try to fix this by providing more info, like logs, phone manufacturer and model, rom etc...
[Magisk] dope77:
galaxy j6+ running android pie 9.0 ,one ui version 1.0
[Magisk] AndrzejDwo:
I think that last recovery log after flashing Magisk would be useful.

You should find it in /cache/recovery/last_log
[Magisk] dope77:
kinda faced the same problem when i had oreo 8.1.0 and it was casued by defex (flashing magisk didnt patch it),androdef posted stock kernel wihthout defex and that fixed magisk problems in 8.1.0

idk if this is also caused by defex,will try to post log later
[Magisk] Simon1511:
Not yet, but I will do ;)
[Magisk] :
[MENTION=4470081]topjohnwu[/MENTION] If you don't mind me asking; what happened to magisk universal multirom?

It was such a simple idea that worked so beautifully. Some documentation on this would be nice. Or some info on how to get magisk >v14 working with the old multirom.

Your work has done so many wonders for my OnePlus one, but I cannot give up my old CM13 rom with its custom camera Hal. Some form of Multirom would solve all my issues, so I could come back to my CM13 rom every now and then to take good quality pictures and videos, then boot back to my primary secure ROM.

Many thanks from Seattle ?
[Magisk] Mr_Jat:
LG V30 Stuck on fastboot - Help!

Hi guys,

I had a custom rom flashed on my device.

Magisk 18.1 was installed upon it however it wasn't compatible with the latest version Havoc.

From advice taken posted in the forum, I rebooted into recovery and proceeded to flash the Magisk Uninstaller.

The uninstall zip flashed without any issues.

When the device rebooted, I was greeted with the fastboot screen.

I have tried to boot into recovery using the button combo however to no avail.

For some reason now the phone isn't being recognized as an LG rather an Alcatel. I can't seem to get the phone to be picked up with ADB. Different drivers have been forced in Windows however no go.

This is the same PC that was used to unlock the bootloader so I know that it should work (my other PC was unable to list the device to unlock the bootloader).

Any help regarding this matter would be greatly appreciated.

Regards,
[Magisk] martyfender:
The current Magisk has Samsung defex patches in it, unless your device has yet another variant of it that [MENTION=4470081]topjohnwu[/MENTION] has not seen yet. I would also suggest trying the latest Canary build, 19005.
[Magisk] BookCase:
Magisk says, "Not installed". I boot into TWRP and flash Magisk and it works for a while then says, "Not installed" again, randomly. I am using HTC U11 Life on latest Magisk Stable (18100).
[Magisk] Simon1511:
Another question:

Has anyone figured out how to use magisk with dualbootpatcher in data-slot-ROMs or how to install modules for it?
[Magisk] dope77:
Tried canary, no success

Tried patching boot.img ,tried fleshing 18.1 , 19.0 but always Magisk not installed
[Magisk] jenslody:
Did you check if MagiskManager is installed in external/adoptable memory ?

If yes, move it to internal.
[Magisk] dope77:
defex related issua, faced it when i had android 8.1.0 ,it was fixed bcz a developer removed defex and posted the kernel on xda

but now on android 9 it's not working at all
[Magisk] akxak:
I had the same on my OP 6 and the solution for me was to uninstall Magisk Manager. Magisk reinstalled it (coming from 17.2) and due to hiding Magisk Manager, I had Magisk Manager 6.x and 7.x at the same time causing that confusion.
[Magisk] lepicane1:
I'm on Syberia ROM for the mido and am getting the errors as per attached. Magisk works fine on Syberia build 0421 but after update to build 0427 fails CTC and basicintegrity.

Have tried uninstalling and installing Magisk again through TWRP, but can't pass SafetyNet on build 0427 of Syberia.

Can anyone tell me what the error (ptrace) relates to? I don't have this error in the Magisk log for Syberia build 0421.
[Magisk] Didgeridoohan:
Maybe you should ask the ROM developers what commits between 0421 she 0427 could affect ptrace (that's what's used to let Magisk detect that an app/process is starting).
[Magisk] lepicane1:
Thanks, I have. Thought I might ask here as well just in case.
[Magisk] Vhatillo:
Bug

Hello I have a bug after root what happens is that the root is fine But after restarting the phone does not recognize the locking pin Nor can the Samsung account be accessed My phone does not have twrp so you can only root Patched boot image My phone is a j810m with Android 9I do not know what I'm doing wrong because Android 8 can be done without any problem
[Magisk] JudgeDread11:
If Magisk is pre-installed, that means there is no stock boot.img to restore. So you should try to find and flash a stock boot image.
[Magisk] Rendering:
I am asking a question because I am a bit confused by official installation guide

I have a Xiaomi Redmi Note 5 with stock ROM (EMUI 9) and I want to both install Magisk and LineageOS on it.

So first step is to install Magisk, but in the guide there are various sections and I don't understand which one fits the bestto my needs:

Custom Recovery:If your device have custom recovery support, the easiest way is to install it through custom recoveries, such as TWRP.

my devices has not custom recovery support. Perhaps I can install Magisk after having installed TWRP+LineageOS?

Boot Image Patching: this seems to be the recommended way to install Magisk

EMIUI 9: what is this section about? People that want to keep their stock ROM?

Which of them should I follow? Thank you
[Magisk] JudgeDread11:
I would install TWRP, then lineageOS and then Magisk.

Assuming you are doing a clean install.

I think that guide is for installing on a running os.
[Magisk] takur69:
How to fix install magisk module Binary file for arm missing
[Magisk] Simon1511:
How can I install modules for a dual-booted ROM?

I have a second ROM in data slot with magisk installed. But how do I install modules for it?
[Magisk] Wolfie0827:
Magisk Manager error app has stopped.

Magisk Manager error app has stopped.

Phone: ZTE Zmax Pro (Z981)

Android: 6.1

Magisk: 16

Magisk Manager: 5.8.2

Magisk manager stops working during start screen. I have cleaned cache, Storage, tried uninstalling magisk and re-installing magisk (When I do this I can not boot into anything but TWRP, no system), Updating Magisk to 17 -18 (Again won't boot into anything but TWRP when I try that). Some times root seems to work for apps, but most times any app attempting root access will get the "Magisk Manager has stopped working" message and then closes.

Root check shows phone as rooted.

Not sure what else to try any help would be greatly appreciated.
[Magisk] RandomPooka:
How are you going to install TWRP if your device doesn't have custom recovery support? I'm curious. I can see how you could possibly use fastboot commands to either flash a ROM or flash a patched kernel to use Magisk. But .. TWRP is a custom recovery, and you are saying that you can't use custom recoveries.
[Magisk] shoey63:
You can't expect support using such an old version of magisk. Update it, and if that causes issues, provide logs.
[Magisk] Wolfie0827:
PLease read the message and you will see that I have tried. But then can not boot into system at all. and no logs when that happens.
[Magisk] maurce249:
anyone having issues with snapchat been block for few hour cause of third party or tweaking
[Magisk] kotuamoalt:
Finally! A new version that doesn't cause a bootloop! My Google pay was previously telling me that I needed to set up my cards to pay in stores, which had previously been done already. Now after launching the app, the message disappeared, so I suspect that Google pay is now working. Have to test that theory out, though.

EDIT: Google Pay verified working.
[Magisk] Rendering:
Yes my fault. I have another phone of the same model, but with already installed TWRP + LineageOS, and I simply installed the zip file from TWRP and after two failed boots, now everything works
[Magisk] DaveX2012:
Yeah what version are you using?
[Magisk] newkydawg:
Yes. We have a magisk thread for this:

https://xdaforums.com/apps/magisk/discussion-snapchat-locked-accounts-t3922880
[Magisk] alajas87:
no useable modules

installed magisk+appsystemizer but cant find icon from appsystemizer after reboot

i have installed:

Magisk Manager v7.1.1

Magisk 18.1

Module: App Systemizer (Terminal Emulator)

but i cant find an app or icon on the screen after rebooting my device.

Logfile data:

04-25 23:48:10.632 3182 3182 I Magisk : * Creating /sbin overlay

04-25 23:48:10.702 3186 3186 I Magisk : * Device API level: 26

04-25 23:48:10.702 3186 3186 I Magisk : Magisk v18.1(18100) daemon started

04-25 23:48:10.712 3186 3187 I Magisk : ** post-fs-data mode running

04-25 23:48:10.712 3186 3187 I Magisk : * Initializing Magisk environment

04-25 23:48:10.712 3186 3187 I Magisk : * Mounting mirrors

04-25 23:48:10.713 3186 3187 I Magisk : mount: /sbin/.magisk/mirror/system

04-25 23:48:10.713 3186 3187 I Magisk : link: /sbin/.magisk/mirror/vendor

04-25 23:48:10.713 3186 3187 I Magisk : bind_mount: /sbin/.magisk/mirror/bin

04-25 23:48:10.714 3186 3187 I Magisk : * Setting up internal busybox

04-25 23:48:10.748 3193 3193 I Magisk : Magisk v18.1(18100) logger started

04-25 23:48:10.779 3186 3187 I Magisk : * Running post-fs-data.d scripts

04-25 23:48:10.779 3186 3187 I Magisk : * Mounting /data/adb/magisk.img

04-25 23:48:10.811 3186 3187 I Magisk : * Running module post-fs-data scripts

04-25 23:48:10.811 3186 3187 I Magisk : * Loading modules

04-25 23:48:10.811 3186 3187 I Magisk : terminal_systemizer: constructing magic mount structure

04-25 23:48:10.812 3186 3187 I Magisk : terminal_debloater: constructing magic mount structure

04-25 23:48:10.812 3186 3187 I Magisk : mnt_tmpfs : /system/xbin

04-25 23:48:10.812 3186 3187 I Magisk : bind_mount: /system/xbin/systemize

04-25 23:48:10.812 3186 3187 I Magisk : bind_mount: /system/xbin/debloat

04-25 23:48:10.812 3186 3187 I Magisk : bind_mount: /system/xbin/cpustats

04-25 23:48:10.812 3186 3187 I Magisk : bind_mount: /system/xbin/jack_connect

04-25 23:48:10.812 3186 3187 I Magisk : bind_mount: /system/xbin/jack_disconnect

04-25 23:48:10.812 3186 3187 I Magisk : bind_mount: /system/xbin/jack_lsp

04-25 23:48:10.812 3186 3187 I Magisk : bind_mount: /system/xbin/jack_showtime

04-25 23:48:10.812 3186 3187 I Magisk : bind_mount: /system/xbin/jack_simple_client

04-25 23:48:10.812 3186 3187 I Magisk : bind_mount: /system/xbin/jack_transport

04-25 23:48:10.822 3186 3211 I Magisk : * Starting MagiskHide

04-25 23:48:10.822 3186 3211 I Magisk : hide_utils: Hiding sensitive props

04-25 23:48:10.825 3186 3211 I Magisk : hide_list: [com.google.android.gms/.droidguard.DroidGuardService]

04-25 23:48:11.903 3186 3414 I Magisk : ** late_start service mode running

04-25 23:48:11.904 3186 3414 I Magisk : * Running service.d scripts

04-25 23:48:11.904 3186 3414 I Magisk : * Running module service scripts

04-25 23:48:26.768 3186 3211 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[5681] ns=[4026535753]

04-25 23:50:47.650 3186 3211 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[12887] ns=[4026535714]

i also installed after this log file a lot of modules, but no one appears as a startable icon.
[Magisk] guest4711:
As its name should tell us: This module installs a script which could be called from terminal emulator, see its description and ReadMe.md

So no icon in app drawer ...
[Magisk] dynospectrum:
There is no GUI. Why are you installing things without knowing what they are?

Read the description.
[Magisk] Mitoastis:
system and vendor

Hey,

I'm looking into using ota updates on an lg V20. There was a warning to not modify System and vendor. I've installed rctd remover and greenify and was wondering if they would apply to that.

Thanks.
[Magisk] kewinhw:
Is it safe to install multiple modules at once before rebooting? Or is it necessary to reboot after each module
[Magisk] DanGLES3:
Yes it's safe,"installed" modules are queued them installed after a reboot
[Magisk] ctsuresh:
Hi I have updated my magisk to 19.0. Aafter update safety net shows API error. I tried to clear data in setting but I couldn't find magisk app listed in apps.

Pl help
[Magisk] dean15:
Met the following problem while running Magisk 18.1 on stock Huawei P9/Android 7: wpa_cli cannot connect to wpa_supplicant.

Found in dmesg that sepolicy blocks access to supplicant.

Wrote a rule: supolicy --live "allow wpa magisk unix_dgram_socket { sendto }" and all went OK. Unfortunately it works only until reboot.

Buit if I try to patch sepolicy file I get the following error:

target type magisk does not exist

Error in: allow wpa magisk unix_dgram_socket sendto

Is there a possibility to add new target type magisk through supolicy or write a rule using real target type, not magisk?
[Magisk] Artim_96:
By the definition of how Magisk works you can't end up touching /system or /vendor if you make all changes through Magisk modules and don't make stuff like letting /system mount as rw in TWRP
[Magisk] Mandeep Hundal:
Hi,

I'm using Samsung j7 prime, having one prob with magisk.

After flashing magisk zip magisk manger doesn't get installed.

Also, even if I install app manually after every reboot it shows magisk not installed in app.

In addition, after flashing magisk can't

Sign in organization's one drive or email address.
[Magisk] kotuamoalt:
What versions?
[Magisk] Simon1511:
Again I have a problem.

Im using magisk v19 beta and it broke my fingerprint sensor.

Before fingerprint worked perfectly, but after upgrading to v19 it only worked sometimes.

So I tried to re-add fingerprints, but now it says that there is no fingerprint sensor (it cant access the fingerprint hardware).

Does anyone knows how to fix this?
[Magisk] Mandeep Hundal:
18.1 and new,

After flashing it, I was unable to login one drive and email account of organization.

It wasn't in previous versions though. One more thing I recently upgraded to 8.1 version.
[Magisk] kotuamoalt:
Have you tried the latest Canary build? (19005)

---------- Post added at 11:26 PM ---------- Previous post was at 11:24 PM ----------

I recommend you try the latest Canary. Ver 19.0, Build 19005
[Magisk] Simon1511:
Thanks, I will try it out