yashsingh1/xdaforums huggingface dataset:
[Magisk] eliezerjk90:
Love that you have to use fingerprint first to change grant by fingerprint option in official update. However, I just think about something. With current configuration, theoretically someone other than me could just deny root access when prompted, open the superuser section in Magisk manager and then manually grant root.

So if your intention with fingerprint thing is to add security then surely it is a hole you need to address. Maybe you can lock the superuser section with a fingerprint or ask authentication every time root access is changed... It's completely okay though if the feature is only intended as convenience feature.
[Magisk] abdoh01:
my device is encrypted so any try to get log from adb never be successful and also it is stuck in lock screen so i cant get to magisk manager so i tried to delete lock screen after flashing stock rom and than flash magisk 17.1 so now it dont responding and no network so i have to got back to magisk until the problem is fixed

my phone is lg k10 lgk430dsy android 6.0 marshmallow
[Magisk] Aerocap:
Hi, if it can help I did as suggested by [MENTION=5270569]scorpionvert[/MENTION] to successfully install 17.0.

Used the uninstaller in TWRP, then flashed immediately the new Magisk. Everything is ok.
[Magisk] mkozal:
I didn't get bootloop but modules stopped working. Uninstalled Magisk using the uninstaller and tried again, still same. So what I did was uninstalled Magisk, dirty flashed the Rom and then it worked (at least for now). Alternatively you can go back to 16.0.
[Magisk] svyat:
The latest version of the Payback app (https://play.google.com/store/apps/details?id=de.payback.client.android) started detecting Magisk (tested with 16.0 and 17.1). Enabling Magisk Hide and hiding Magisk Manager does not help.

The previous version (https://www.apkmonk.com/download-ap...d/5_de.payback.client.android_2018-08-21.apk/) did not detect Magisk when Magisk Hide was enabled (hiding Magisk Manager was not necessary).

Any suggestions on how to make it work? Could the MagiskHide Props Config module help?
[Magisk] im-pulze:
Hey thanks! That worked. But I'm now without Magisk for now and considering to install Magisk 16.7.

Maybe the thing a few posts before is the issue? I've installed v5.9.0 and upgraded to 5.9.1 afterwards.

Probably this broke something
[Magisk] Mcha01:
Im getting bootloop on latest magisk 17

My device is g900v

Running RR nougat klte

With custom kernel

I revert back to version 16.7 (ibelive) it start to work again
[Magisk] im-pulze:
Ok for all of those who have a bootloop after installing 17.0 and upgrading to 17.1 to fix the bootloop, do the following:

- Go to recovery

- remove Magisk with the Magisk Uninstaller in the first post

- flash your rom ontop your current rom

- reboot

- go to recovery again

- flash the newest Magisk 17.1 and you're good to go!
[Magisk] dms-x:
Updated from 16 to 17.1

Hi developer,

I'll updated to 17.1 on my Samsung S8 (SM-G950F) on Android Oreo (8.0.0). And everytime my phone goes sleeping, after the screen went off the phone hangs. Only the hardware buttons and fingerprint reader are working.

The software buttons on the screen and the rest of the screen won't work anymore, till I restarted my phone..

I had some modules turned on. But now all modules are turned off and the phone still hangs when the screen goes off.

With the previous version (16) I didn't had those problems, can I go back to the previous version?

Kind regards,

Ilco.
[Magisk] Zielony360:
On OnePlus 3 after upgrading from OxygenOS 5.0.4 to 5.0.5 and Magisk from 16 to 17.1 Safetynet fails. Someone found a solution?

EDIT

For the moment it passes after reboot.
[Magisk] tygertim:
V17.1 hide no longer hides my Santander bank app.

No amount of uninstalling/reinstalling the app and clearing out the data stops the app from spotting that the phone is rooted. Any suggestions?
[Magisk] DS-1:
I can't install this: https://xdaforums.com/sho...58&postcount=1

I have a Lenovo P2 with lineageos 15.1 official and magisk 17.1.

It tells that magisk 14.0+ is required...is there any way to fix it?

Thanks!
[Magisk] Trex2017:
I'm not able to grant access to apps which use root ( 17.1 )

There is no prompt and even if I set default permission as allow it still not working , I'm on android nougat ( dot os ) compiled on my own from source I had this issue on 16.7

What to do
[Magisk] fidanzata:
all module doesn't work on 17.1 :confused:

Miss u 16.0
[Magisk] 501st:
since when i upgraded from magisk manager 5.8.3 to 5.9.0 the app is stuck on opening screen.

i can delete the app but every version i try to install it ended to be stopped at the opening.

i can't run uninstaller from recovery since my device is encrypted by default.

i don't have a full img of my rom.

a factory reset from an original rom with magisk still installed would be a problem?

thanks
[Magisk] Utini:
Since Magisk 17 I am getting the same error.

I updated to 17 which caused a bootloop.

Tried to flash Magisk 16 but didnt work.

Used uninstaller

Flashed Magisk 17

Had 2xMagisk App installed

So I uninstalled both and re-installed once.

Any idea what I could do to fix the error?
[Magisk] Jimnik:
Now that magisk updated I can't pass safetynet both CTS profile and basic integrity are faulse. It's strange because the update was mostly dedicated to fixing the new safetynet cheks (or so I've read)
[Magisk] Legoman6:
Magisk Manager has been updated to make the check against the new SafetyNet API that Google is now using. The

cause

of your device failing the basicIntegrity and ctsProfile checks are for different reasons.
[Magisk] meboy:
Pages and pages of errors

but no error logs in sight ..........

Wtf people.....
[Magisk] Rush82:
Could someone help me, please?
[Magisk] BustedFly:
New Payback App is working fine on S7 Edge with SM 2.8 and Magisk 17.1
[Magisk] Saswata Chakraborty:
Thanks buddy for taking your time to read my problem. I didn't get 5.9.0. I opened magisk and saw 5.9.1 and updated the app. Then I got the popup for v17.1, I ignored it and then I lost root access. Now I can't see "Direct Install" option in magisk manager. Surprisingly, even though I lost root access, my magisk modules are still showing in app list (although they are noy working). Normally when you uninstall magisk/unroot the device, all your magisk modules are gone automatically. topjohnwu should have given us a choice yo either upgrade to v17. 1 or stay to v16.0. But rather Magisk v16.0 is getting unrooted automatically.
[Magisk] Joangarc:
I have the same problem with Samsung S8+
[Magisk] Darke5tShad0w:
If you search or read back a few pages you will find your answer.

Hint that is no longer the newest version.
[Magisk] danzukuka:
i had the same problem, install this module and you're good to go

https://xdaforums.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435
[Magisk] Jithin0801:
I have a problem the Apps under magisk hide are crashing, Is there I am doing anything wrong and the sateynet is loading forever didnt get the result!!

Device: oneplus 6

OS: Oxygen OS 5.1.11
[Magisk] hecaex:
Nobody?
[MENTION=4470081]topjohnwu[/MENTION]
[Magisk] llucax:
Problems getting past v16

Hi, I used Magisk for a long while, but I never got past v16. I tried v16.x betas but there were very unstable for me, crashing apps, etc.

Now v17.1 is out and I'm also having troubles with it. The first install worked but all the MagiskHide config was gone, and while starting to hide magisk from most applications I had before, the phone re-booted and entered a boot loop. As far as I understood from the changelog, v17.1 shouldn't have problems with boot loops right? Even without uninstalling v16 before installing v17.1? After flashing the stock boot and the patched boot again, I managed to fix the loop a couple of times, but every time I added more apps to magiskhide, I got again into the re-boot + boot loop. So I decided to just uninstall Magisk and install v17.1 from scratch. Now I can't open MagiskManager, it just hangs on the splash screen with the mask. Also, opening any app that request root, they just hang on the root request.

Now if I flash my old boot image patched with Magisk v16, MagiskManager says Magisk is not installed anyway, so I can't get back to having Magisk on my phone.

Any ideas of what could be going on and how to fix it? This is an LG G6 Stock image V20b-EUR-XX (Android 8.0.0, 1 June 2018 security patch, kernel 3.18.71). I always use the patch boot image install method.

Thanks!
[Magisk] ldiomedi:
Nice.. where did you get it?
[Magisk] wertzPH:
my stock firmware comes with Permissive sepolicy, how can i retain everytime device boots? my unit behaves differently when it is set to Enforcing-including Pokemon GO not connecting to server.

thanks.
[Magisk] deedeeceleb:
4 posts above yours

Gesendet von meinem ONE A2003 mit Tapatalk
[Magisk] ldiomedi:
:D sorry.. my bad
[Magisk] westeight:
The Android Pay Tasker script for disabling root is -slightly- slower than AutoMagisk, but it also auto enables/disables NFC ... so overall it's more useful than AutoMagisk.

AutoMagisk is perfect for SafetyNet, Pokemon Go and Banking apps though :)
[Magisk] Xebazzztian:
The OP says it not work on moto devices, Idk if u are reading an updated OP in ur head... Anyway u are being so smart@ss telling me to read when u didn't read my post in first place?

Clap clap clap
[Magisk] westeight:
Just noticed further options:

:)
[Magisk] Aziziamran:
Cm12 issues

Hi there. I'm using Lenovo vibe Z K910L with custom rom CM12.1 (Lollipop).. I've tried to use magisk root method 2 times, with provided supersu, phh supersu, follow the instructions but it fails to boot up, stuck on bootloop & not even detect any internal data, shows 0MB on twrp recovery, then after almost 10 or 12 times reboot to recovery, it's work and detect my data & I've just restore my backup that I did earlier.. The question is, does it support any custom rom like cm12 or just stock rom? Because my sister phone is Samsung Galaxy S5 running stock Samsung Lollipop & I did the magisk root with phh supersu and it's work like charm.. More info, I've tried another method suggested to makes magisk running like delete su files from systems, fresh install with new custom rom but non of it works for me..
[Magisk] dimm0k:
why won't /data/system changes stick!!?
[Magisk] SpasilliumNexus:
LOL no. The OP says "generally."

Definition: In most cases. Not specific.

That does NOT mean all.
[Magisk] Robot76:
Deleted
[Magisk] Chrifister:
A friend of mine has Magisk, phh superuser, and systemless Xposed working on a Canadian S5 G900W8 on 6.0.1. build PD3. Started with stock ROM with wanams Xposed and cf auto root installed. These were the steps he took:

- download Magisk v6, it's uninstaller, the Magisk Manager app, and phh SuperUser from OP. Download xposed-v86.5-sdk23-topjohnwu.zip, it's uninstaller, and Material Design Xposed Installer app from the link for systemless Xposed in the OP

1. uninstall and delete all Xposed modules

2. uninstall cf auto root using the app and choose to restore boot.img

3. reboot to twrp

4. flash uninstaller for wanams Xposed

5. wipe cache/dalvik

6. reboot

7. uninstall wanams Xposed app installer, ROM is now clean

START FROM HERE FOR STOCK ROM WITH TWRP INSTALLED

8. reboot to twrp

9. flash Magisk v6

10. reboot and make sure it boots properly

11. reboot to twrp

12. flash phh SuperUser

13. reboot and make sure it boots properly

14. install phh SuperUser app from PlayStore

15. install Magisk Manager app

16. verify that Magisk Manager can toggle root and Android Pay and/or a recent popular app works with root unmounted

17. reboot to twrp

18. flash systemless Xposed

19. wipe cache/dalvik

20. reboot and make sure it boots properly

21. install Material Design Xposed Installer app

22. install Xposed modules

23. verify Android Pay and/or that recent popular app works

24. Pat yourself on the back and have a cold one, or 12

Things learned and/or read from this thread and the systemless Xposed thread:

- all traces of any previous root must be removed or root toggle will not work

- Magisk contains BusyBox so if you have it already, uninstall BusyBox from within its app and then uninstall the app

- you must have a stock boot.img so if you have cf auto root, make sure you tell it to restore it when uninstalling root

- the systemless Xposed link in the OP says somewhere it will work on Samsung if you're running Android 6.0.1 MM, well this particular S5 anyway

- first time Magisk was flashed, then reboot to twrp, then flash newest phh SuperUser from phh thread link in OP. Got Error 1 or something. Flashing SuperUser again succeeded but phone would only boot to download saying it couldn't boot properly or something. Not sure if because of newest phh SuperUser or because didn't boot up normally between flashing Magisk and SuperUser? Restore boot from twrp backup worked to reset boot.img to try again

Another friend is wondering about a Canadian S5 Neo G903W I think. Ruining Android 6.0.1 and has twrp, wanams Xposed, and cf auto root installed. I'll post back when he tries it.
[Magisk] Xebazzztian:
:eek:

Hide ur kids and ur women, the semantic police is here.
[Magisk] teddy0209:
Your problem maybe twrp, update it... And do not mount system as rw, that would break ota that's why the installer only mounts it as ro...

---------- Post added at 12:21 AM ---------- Previous post was at 12:19 AM ----------

Yes it will, so you have to rebump.
[Magisk] dimm0k:
any idea why changes i make to /data/system/packages.xml aren't sticking? even edited in twrp, but after booting in all those changes are gone
[Magisk] sk00bie:
Sadly this doesnt seem to work on my Samsung Galaxy tab 3 wifi version ( GT-P5210 )

The error is : "boot image not detected"

any ideas?

Many Thanks
[Magisk] DerpleNerple2000:
Gonna have to try this when Nexus 6 Nougat images finally arrive. I actually put it on a custom ROM that has some built in customization mods, which is why I believe AP is failing. Regardless, I do like this idea as a concept, but I notice that any changes done to the system, such as uninstalling system apps via Titanium, don't stick after reboot.

Also, when you mention "moto devices" as ones with issues, does this apply to the Nexus 6 as well or just phones like the Moto G/X/Z?
[Magisk] Comedy-:
I'm planning to run this on my S7 Edge SM-G935F. Is there a specific kernel I should use? I've had no luck so far and I saw a comment somewhere that a custom kernel is needed
[Magisk] StrykZ:
Anyone having issues with Bluetooth not turning on in n910u cm13?
[Magisk] Robot76:
Working fine on Xperia Z3C with advanced stock kernel...

[emoji7]

A.R.I.S.E.Numbers™ Z3C SLiMM3.2 EliteKernelV3 Phh.Superuser Substratum
[Magisk] elbi14:
After update to latest

Fingerprint scanner authentication cannot enabled
[Magisk] CarteNoir:
Having some trouble with 17.1 - after the update from 16.4, apps that are hidden via Magisk Hide now no longer open (immediately exit on opening from the launcher app drawer). I've tried a full/complete uninstall of Magisk and all modules, then a reinstall and I'm still having the issue. In particular, the Play Store seems to be one such app that won't cooperate with Magisk Hide. Pixel 2XL, Oreo 8.1 (July patch), Magisk 17.1 Stable + latest Magisk Manager app.

Magisk Log, Logcat.
[Magisk] @srmahunt:
After upgrading to magisk 17.1 i can't set fingerprint authentication for magisk. When i try to enable the toggle it says authentication failed, plz help.
[Magisk] Hopie:
Anyone uses the Sky go App? The dont start on Rooted Devices. I try with Magisk Hide. but the same.

any solution? thx
[Magisk] FullWipe:
Hi mates, after updating Magisk to the latest v.17.1, my fingerprint is totally broken with this warning --> "Fingerprint hardware not available"

I tried to revert to v.16.7 but the problem still remain.

Need some help...thanks ;)

Oneplus3T with RR Oreo.
[Magisk] pv979:
Same here: root works, but modules do not load...
[Magisk] danilo_jlle:
Magisk update error

Hi.

I'm trying to update Magisk v16 to v17. Already tried both from TWRP and Magisk Manager, and got an error.

Lineage OS 15 on a Lenovo Vibe phone.

Log file says:

- Copying image to cache
- Device platform: arm64-v8a
- Existing zip found
- Extracting files
boot_patch.sh[73]: can't create /proc/self/fd/: Is a directory
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
No boot image magic found!
boot_patch.sh[91]: can't create /proc/self/fd/: Is a directory
boot_patch.sh[91]: can't create /proc/self/fd/: Is a directory
! Installation failed
[Magisk] Johnn78:
You mean the modules ?

If yes, is it the same to install them from twrp ?

Will be appeared in the module list of magisk ur the installation has beeb made from twrp ?
[Magisk] dms-x:
Thanks for the people who gave solutions to solve the problem!

I downloaded version 16.7: https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 After that I'll deinstalled version 17.1, after the restart the phone came in a bootloop, then I'll flashed the older version (16.7) in Recovery mode in TWRP.

Now everything works fine again. The module to watch Netflix on a rooted phone works also, so for this moment my problem is solved and I'll stay by this version for the moment. (turned off updates).

Maybe something for you too [MENTION=634959]jao[/MENTION]ngarc, or perhaps a other solution from the other replyers.. :good:
[Magisk] internetpilot:
I'm having a similar issue with my Moto G5S Plus and the Magisk update.

I was prompted to update Magisk Manager, and of course when I did it reported that Magisk was no longer installed. When I tap the install button to download and install Magisk 17.x regardless of which way I install it, I just end up with bootloops. I'm not trying to do anything special at all -- just want root on my currently stock Nougat ROM. I restored a few day old nandroid (lucky I had it -- I don't normally do a backup before updating Magisk Manager), and now I'm just ignoring the Magisk Manager update notifications.

I can't do the dirty flash trick with my ROM because I'm on stock.
[Magisk] wiidude22:
Working on Pixel 2 with magisk 17.1 on Pie 9.0. I did a clean flash of 9.0, booted up to the setup screen and immediately restarted and flashed magisk. Safety net passes and modules work.
[Magisk] sanju455:
Yeah!!!! Again safetynet pass started ..Hands up for Dev
[Magisk] guest4711:
Ask the dev of this module to update it. There are a lot of changes in Magisk which make the current versions incompatible to the old layout. (This is necessary because a lot of apps detect Magisk using the well known folders were Magisk did put his files into.)
[Magisk] johnb07:
I'm on s7 g930f using the galaxy project rom 2.4.0 a and the latest magisk 17.1 I've installed modules but they aren't appearing in my apps any help please ?
[Magisk] TheRealIntence:
Can't login into my Google account after the update. Login app will crash after I tried to login.
[Magisk] themrmotivator:
HTC u11+ installed 17.0 via twrp worked. Updated to 17.1 via twrp all good ?
[Magisk] johnb07:
Anybody else's installed modules not showing up in your apps or isit just me.

Edit: Think its just the YouTube vanced black themed module think it needs a update v4a works
[Magisk] themrmotivator:
Huawei Mediapad M5 10 updated successfully to 17.1 via patched ramdisk image. ?
[Magisk] fosterqaz11:
Something strange happen to me today lol. I don't know why but all my apps requiring sn was working (Gpay too), though I'm using xposed. :eek: As we know, xposed don't work well with sn I was curious what was going on. So, to sure I run sn check, and as expected it was false. So, I went straight to Gpay again and tried to use the app, but this time I couldn't. :(

I don't know what happen to my phone for a while lol .
[Magisk] rafaeldamasceno:
Magisk v17.1 is causing my Vodafone Smart Ultra 6 to boot to recovery every time. v16.0 was working alright.
[Magisk] beardymarrow:
Working fine for me in the UK with magisk manager hidden.
[Magisk] :
Search (and/or read) before posting. Many people have mentioned that.

Since everybody has read the 17.0/17.1 announcement in the announcement thread carefully before updating, it should be common knowledge, that quite some (all? most? sadly only the ones you are using?[kidding - but not impossible ;) ]) modules need to merge the template changes.
[Magisk] aydinbahadir88:
It worked for me briefly, Mit Hide Props

---------- Post added at 02:15 PM ---------- Previous post was at 02:11 PM ----------

It does not work for me

Xiaomi Redmi Note 5 Pro

Havoc OS 8.1

Root With Magisk 17.1
[Magisk] iamleeeeeeeeee:
Sucessfully flash 17.1 so far no bootloops or whatever. But when I tried to enable my fingerprint root authentication it says authentication failed. Why is that?
[Magisk] RichardEb:
Have you Tried to download the full Magisk package (not the update) from the forum and to Flash it with twrp? Worked for me.
[Magisk] unhappybirthday:
Yes, yes, and yes.
[Magisk] mannyvzla:
17.1 works fine on Samsung tablet, even safety net. On Xiaomi note 5 safety net fails and module I installed (viper4android) appears twice. Uninstalled everything and started from scratch but same results

Enviado desde mi SM-T550 mediante Tapatalk
[Magisk] Ghisy:
Hi,

I updated fine to 17.1 from 16 but it seems like my fingerprint sensor is not working properly since. I was able to register my fingerprints once but tried again and it says sensor is dirty (it's not).

Could it be the 17.1 update that's causing this?

Thanks.
[Magisk] :
You have misspelled: "I've proofen Magisk Hide is working." ;)

BTW: both of your logs are missing the initialisation phase of Magisk - everything else looks good (now, I know why... it's just because it's working... ;) ).
[Magisk] Terrigible:
I have the same problem, since a while back actually, but it is worse now on 17.1. Can someone tell me how I can grab a logcat while trying to unlock my phone?
[Magisk] meskafonas:
I have Huawei Nova with f2fs file system i guess. I can't install any of Magisk modules. I have read in forums that could be a problem of encryption? Please someone answer me ;)

Root Magisk 17.1 - OK

TWRP - OK
[Magisk] brainycaleb:
I get error trying to install version 17, 17.1 and even when I try to downgrade to v16, I still get an error. Im using TWRP 3.2.3.0 on official Lineage Os 15.1 Oreo for Samsung S5 G900F
[Magisk] Ghisy:
Hmm so I'm not the only one. It was working fine on 16. I would also like to send a log if possible.

What phone do you have? I have a Pixel 2 XL running stock Oreo with Magisk.
[Magisk] xunholyx:
Plug your phone into your PC and get into adb

enter adb devices to make sure you are connected (it'll show your serial# if you are)

then adb logcat -c (<---this will clear your logs)

then reproduce what you are wanting to get the logcat from (fingerprint sensor issue in this case)

then adb logcat -d > logcat.txt (this will dump the log into a file named logcat.txt in your adb/fastboot folder)
[Magisk] Ghisy:
[MENTION=4987085]xunholyx[/MENTION], thanks! Got a logcat. Fingerprint only didn't work once on this (of course, when trying to get a log, it worked better than usual!)

[MENTION=4470081]topjohnwu[/MENTION], logcat is attached!
[Magisk] :
:good:

If a relevant error occurs on initializing Magisk, -c throws this away. As long as we can't exclude a Magisk issue on initialisation, I would suggest to increase the log buffer size to 4 Mio., reboot, unlock and get the complete log. Once we can be sure the Magisk initialisation the -c is very usefull to keep the logcat to the minimum.
[Magisk] DroidJP:
As i am following this thread. I see that most are having serious issues with magisk. I thought magisk was a straightforward process. May i know what devices and setups most are using that is causing such issues?

I am on 17.1, safety net passing, no issues as of yet. Then again, hardly had to experience any of the issues from previous versions of magisk.

Just curious to why most are experiencing so many issues.