yashsingh1/xdaforums huggingface dataset:
[Magisk] master64nl:
I am on G950FXXU3CRGH. When I use Magisk v17.1 after while my screen crashes all the time. Also the S8_Data_mount_fix_Magisk_V3 wont work anymore. When you follow the steps for the fix you are unrooted when you boot for the first time. Than I get the problem that all the apps whom where in "Magisk hide" particularly the delegate banking apps wont work. Install the Magisk 17.1 zip and they can be installed again but than you have a data mount problem again.

So, something of Magisk is still around on the phone somewhere and influencing these apps.

Tried to go back on my latest back-up but that wont either, I can not use my sim card than. It seems once on the latest firmware, going back to an back-up running on an older firmware gives issues.

Only thing left is do a clean install of G950FXXU3CRGH and install latest TWRP with format data, get back without booting and install veryfyscript and get back without booting and install S8_Data_mount_fix_Magisk_V3 and reboot system. Installing Magisk 17.1 before the latest step does not do anything, so I left it out for now. Than get in TWRP and go to latest back-up and recover only data. So here I am without Magisk root but still when opening for example Samsung Health nagging me about the the phone is rooted. I have no clue how this come because I did not install Magisk.

But when I install Magisk, I have a problem that the phone crashes suddenly and the screen is not responding. Very irritating. So, is this problem known so far?
[Magisk] MacGyverLarisa:
Hi

I have a Lenovo ZUK Z2 with Bootleggers v3.0 rom. I have magisk 16.6 and then the 17.1 all work good without problem I update from magisk manager. Today I uninstall with the last magisk uninstaller because I want to try an .ehi file in http injector, but inside of http injector he say rooted device are not allowed. Why this?

Thanks for your job and sorry for my English
[Magisk] martyfender:
I see nothing in that recovery log about an attempt to flash magisk. After that last line in your recovery log you would see the magisk.zip listed and inflating it, unpacking boot image, patching it, repacking it, flashing it, etc.

Did you save that log in TWRP after flashing magisk, before you rebooted the device? Or did you save it after a reboot?

To save the log in twrp, hit the advanced button and there will be an option to save the log to your internal SD card at the top.
[Magisk] adinechin:
Hi, I was on Magisk 16.0 for some time on Lollipop, and the update to 17.1 was very complicated : I could not update through the manager like before. Is it normal ? When I updated to the latest manager, it said that Magisk was not installed, and when flashing the new zip it did not work.

I could not use the uninstall feature of the manager to remove v16 so I had to manually restore unpatched boot and then install 17.1 zip through recovery.
[Magisk] spleenandcigars:
So, in order to proper get the logs, i should flash magisk and without restarting get to Advanced and log, right?
[Magisk] whitewolf1608:
Hello, everyone on the forum :) If I write in the appropriate department is very sorry - but so far I have not found a department for Magisk Mask v 17.1. There was a forum topic about Magisk Mask v 17.1 here at this link

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 but this thread has already been closed.

I have LG G4 h815 with this Rom - em>

https://xdaforums.com/g4/development/rom-simplegx-rom-v1-0-29-jan-t3547009

I have a problem with rooting my device. Therefore, because the main thread about Magisk Mask 17.1 has been closed - going with the thought not to make additional mess on the forum I write about your problem here.

I've shared a link to the Magisk Mask 17.1 Album on the Google Photos server

https://photos.app.goo.gl/MZA2TVMPuKB3Yw2Z6

After launching the Magisk Mask 17.1 application, I choose the install option, then a window appears asking Do you want to install Magisk-v17.1 (17100) .zip now?

I choose from the lower menu in which I have three options - the install option, the orange string on the white background, the last from the right side of the screen

I get a window with choosing the method I choose the last one from the bottom. Direct Install (Recommend)

Then I get another window which flashes very fast - it is a window with a black background and white captions.

Unfortunately, this method will not get the Magisk Mask of my LG G4 h815 - Android 6.0 MarshMallow. Because, after a while, the error message appears, Magisk Manager has stopped.

I put in the screenshots on the server Google Photos Album named Magisk Mask 17.1

I am asking you with a very polite request, how can I root my LG G4 h815 with Magisk Mask 17.1?

I am asking you with a very kind request to help me.

Best regards, all who read my post :)

I would like to kindly answer whitewolf1608
[Magisk] martyfender:
Yes and I updated my post with more info.
[Magisk] jenslody:
Even if Magisk is really completely removed some apps complain, e.g. because of unlocked bootloader, enabled developer options, permissive selinux, "unsecure" props in build.prop (debuggable, etc.).

And your device-maintainer might have build Bootleggers with su enabled ( there's a conditional build-flag for this).
[Magisk] sbiricuda:
Hi again..

does anyone have any idea about how to get rid of the /vendor issue? :(

Looks like it's a common issue but I can't find any solution in previous threads (or they don't apply to HTC U12+).
[Magisk] krug3r:
Hello everyone :)

On my Samsung Galaxy S6 SM-G920F, I have tried to installed the v17.0 => boot loop ;(

i was mandatory to flash with Odin and my stock rom to recover my phone.

New try with Magisk v17.1, I've got an "error 2" but no loop :D \o/

[IMG="Screenshot Magisk 17.1 ERROR 2"]https://postimg.cc/image/j7dgq0843/[/IMG]

Any idea ?

Samsung Galaxy S6 SM-G920F

ROM : Stock G920FXXU6ERF5 XEF
[Magisk] spleenandcigars:
I did it again and made sure to check for the Magisk mentions in recovery.log. Hope this helps. Thanks for the information and the cordiality to help me out.
[Magisk] BengaliBhai:
My device was rooted . After restore my previous backup by TWRP it's fully unroot.

I was try to install magisk 17.1 but failed. I also try 17.0/ 16.7, failed (Samsung j700h 6.0.1)

How can I install Magisk by TWRP ?

:crying:
[Magisk] Rush82:
I was finally able to enter in recovery mode, uninstall magisk 17.0 and install magisk 17.1.

The method has been power and vol down till Lg logo, releasing all, then vol up and vol down.

My error was about not releasing vol down after first step.

Thanks to everyone for suggestions and apologizes for the amount of posts.
[Magisk] JimZiii:
I could really use some help. Yesterday I flashed the systemless version of xposed for 8.0 but I'm getting a bootloop. I'm able to flash my stock ramdisk to get the device to boot but as soon as I flash magisk it's back to the bootloop since the mod is still active.

Twrp cant decrypt my files so it's pretty much useless here. I don't really understand sideload so im not sure how much it can do, but I tried both xposed and magisk uninstaller with sideload with no luck. I tried mod uninstallers but they work the same way and they then need the terminal to work.

Tried disabling xposed through the app and magisk manager but i need active root to do that and every time I flash a patched boot file it's back to the bootloop. So I'm currently stuck.

I read that the mods are stored in data\magisk.img but I can only reach it with root and with root it can't boot.

Could this be fixed or should i just make a backup and factory reset
[Magisk] krug3r:
Uninstall magisk 17.0, how ?

thx
[Magisk] MacGyverLarisa:
If understand correctly or I need clean flash or I need stock ROM?
[Magisk] Didgeridoohan:
Adding all apps and services to the Hide list has

always

been a bad idea... Why so many users insist on doing it, I have no idea.

With Magisk v17.1, MagiskHide has been greatly improved and will now kill off more background processes associated with the app/service on the Hide list. This also means that if you keep adding important system processes to the Hide list (that have nothing to do on that list in the first place), you will get an unstable system with reboots and crashes as a result.

There might be a separate issue where some apps crash when on the Hide list (that do need to be on the Hide list because they do look for root and trigger if it's found), but that's under investigation.

I strongly suspect that many of the "bootloops" and issues with an unstable system that keep being reported are simply users adding a ton of unnecessary things to their Hide list.

Public Service Announcement:

Only add the bare minimum of apps and processes to the Hide list. If an app isn't detecting root or isn't used by another app to detect root, do NOT add it to the Hide list, especially if it's a system app/process. The chances are that it will mess up your device!

Edit: A slight clarification, since the question keep rising. It's not about the number of apps you put on the list, but about which apps you put on it. System apps and processes are generally a bad idea, etc...
[Magisk] jenslody:
In TWRP you should still be able to reach "/cache".

In TWRP go to "Advanced -> Terminal" and place a file called ".disable_magisk" in "/cache" by running

touch /cache/.disable_magisk

, note the dot in the file-name, it's mandatory.

After reboot Magisk runs in core-only mode with modules disabled, you can now disable or remove the xposed module.
[Magisk] :
I'm completely with you! I love every single word of your posting.

This thread has one of the worst SNR I've ever seen.

On the other hand: I don't expect it will help. If the people aren't willing to follow one of the most basic and simple xda rules (search before posting), why should they follow these additional rules?

If people ask for /sdcard/MagiskManager, this shows a lack of respect to [MENTION=4470081]topjohnwu[/MENTION] - otherwise they would have read the announcement of the Magisk version they're complaining about. If the question for /sdcard/MagiskManager comes up on the next page of your posting , this does not only show a lack of respect to your posting, it also shows people are not willing to search before posting, nor reading the announcement, nor reading - at least - the last 5 pages.

This is only for the moved download dir, if we count in all postings regarding modules not working (again: changed template is mentioned in the announcement), all postings lacking the bare minimum of information , all so called issue reports without logs and all pointless "me too" postings, this thread would have less then 50% of the postings.

I would be more then happy to be falsefied on this: this thread is lost. :(
[Magisk] jenslody:
I don't think so.

I just tried the http-injector from playstore and it indeed detects Magisk, even if it is on the hide list.

I only looked into the diagnostics-tab and it says "root:yes", but after repackaging MagiskManager with a random package-name ("Settings -> Hide the Manager") it no longer sees root.

You might need to clear cache and/or data of the app.

As written before, I only checked it in the diagnostics-tab of http-injector.
[Magisk] martyfender:
I may not be the best to diagnose this, but the flash looks normal to me. You never posted your device info. Is it a Pixel of some type, with Nougat or newer? Also have you checked your device forums for others flashing Magisk 17.1? You stated you get a bootloop after flashing and did you give it some time to confirm it is actually a bootloop. Sometimes when I flash Magisk my devices will be at the boot animation longer than normal.
[Magisk] MacGyverLarisa:
Thanks a lot I will flash again magisk and I will try.

Thanks my friend I flash magisk again. I follow your guide and hide the manager and http work properly. Thanks you very much.
[Magisk] TheUndertaker21:
Not on pie
[Magisk] :
- I posted logs.

- You're completely wrong if you expect me and other users to read:

And conclude that "modules disappear on reboot" is not a bug. Not to mention, I don't use FBE (file-based encryption) on my phone.
[Magisk] Didgeridoohan:
That is unfortunately nothing I can do anything about, since it has nothing to do with the module. This is also noted under "Known Issues" in both the OP and the module documentation...
[Magisk] TheUndertaker21:
Thanks but what about magisk no longer able to hide spay for the gear.

Worked on 16.8 but not the latest one.

I'm not sure if the dev will work on it since it's not so important
[Magisk] Rush82:
flash this(on twrp) to uninstall magisk:

https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-uninstaller-20180901.zip

to get magisk working flash this(on twrp):

https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip
[Magisk] spleenandcigars:
Oh, sorry. I have a Pixel XL with Android P. It was working perfectly on Oreo. I gave it time enough, waited untill it rebooted, actually. In the previous 16.7v i tried wiping cache before and/or after installing, tried formatting and starting from zero... And yet here we are.
[Magisk] master64nl:
I only have 7 apps on the hide list and still crashing.
[Magisk] :
Wow. You really got my point... Dude, I'm talking of a massive amount of postings missing logs.

If I would expecting this, I wouldn't need to call this thread lost.

I'm concluding that modules are effected by the update and mentioning currently broken modules over and over again isn't helpfull nor does it make the thread more informational.
[Magisk] Didgeridoohan:
Is the device or the apps crashing? What apps? Is it absolutely necessary that they're on the Hide list?
[Magisk] JimZiii:
I'm not at home so I can't fastboot the patched boot image right now but is it possible to flash it with twrp even tho twrp can't decrypt my storage? I think the encryption only includes \system, so it should be possible
[Magisk] master64nl:
Is the device or the apps crashing? What apps? Is it absolutely necessary that they're on the Hide list?

Because these appare nagging about rooted device and can not install fingerprint feature for example.

I am busy for two days now, mi wife is killing me. I can not get my installation right. Please help me out here.

Can you give me a step plan to get started from scratch because I am in a bootloop again so I have to start all over again.

I can not even install a custom rom. Get all red lines in TWRPwith warnings.

I say it is not by Magisk but it began after updating to 17.

So what shall I do?
[Magisk] jenslody:
"/data" is encrypted not /system and yes you should be able to flash the patched boot-image without problems.

I do that regularily until I get my TWRP fixed to decrypt my data again.
[Magisk] störte:
Hello

Just as an info for the guys on Fortnite.

With Magisk 17.1 it is working same as Pogo.

What i did is following

1 Hide Magisk Manager and change to core only and as well Magisk hide

2 Reboot

3 Under Magisk hide i hide Pogo and Fortnite and Fortnite Installer

4. Reboot

After that it worked
[Magisk] sh0w 0f:
Hi guys can you help me with my problem?

I installed the latest 17.1 but the modules are not working :(
[Magisk] geearf:
Hello,

I have a similar behavior as others have mentioned here.

I skipped 17.0 fearing issues and updated in the manager once I got 17.1 from 16.6. But the phone would only boot to recovery.

I've used the uninstaller and flashed it from TWRP, alas the result was the same.

Going back to 16.6 seems to have worked but I've lost all settings and modules :/

I'm using an Axon 7 on stock Nougat 7.1.
[Magisk] zhekozhekov:
Hi guys. I have been with Magisk v.16.0 until yesterday, when I lost totally root, updating the manager to the latest one.

I am with Xiaomi Mi A1, Oreo april patch.

I created the patched_boot.img thru the app, extracted to PC and flashed thru fastboot to slot B (my current slot).

Then thru the app direct-installed v17.1 (the recommended). Rebooted and...no Wifi.

Found in the forum here, that deleting p2p_supplicant.conf might help - no success.

Is there any other solution of the problem?

I still have v16 on file. Do you think downgrading to v16 and installing patched_boot.img from v.16 might bring back my Wifi?

A quick note: I don't have TWRP.

Many thanks.
[Magisk] JimZiii:
Thank you so much, worked great.
[Magisk] spicediablo:
Hi, I'm having issues with safety net after updating to magisk 17.1. Anybody encountered this problem?

Sent from Sagit
[Magisk] vandyman:
NO.

Sent from my Pixel 2
[Magisk] amit3880:
Does anyone have solution for this app 'Balckberry Work' with MagiskHide?

This app was working fine with Magisk but recently it has been updated and now its not working with Magisk installed. All other bank apps are working fine with Magisk but this app is not working now.

I am running unrooted just because so I can use this app and with release Magisk v 17.1 I was hoping it will work with this app but no luck.

https://play.google.com/store/apps/details?id=com.good.gcs&hl=en

I have now again uninstalled Magisk and the app is working however I would like to know if there are any solution.

I am ready to provide logs but for that I would be needing to install magisk again and collect. If anyone willing to help I will do that activity of installing and gathering the logs.

Thank you in advance.
[Magisk] Machi007:
Hello,

I just installed latest Magisk 17.1 on my ZTE Axon 7 Mini (stock 7.1 ROM) and it is not working. Phone boots into recovery every time. Magisk v16.7 works fine so there is some problem with this latest version. I hope it will be fixed soon.
[Magisk] jcmm11:
Note that if you're on a pixel + pie there's a new version of TWRP that should decrypt

https://www.xda-developers.com/twrp-decryption-google-pixel-pixel-2-android-pie/
[Magisk] Sandy Stark:
I got an error after installing the latest update of Magisk

I have installed patched_boot.img still its showing Magisk is not installed. Any solution for this without flashing patched boot once again?? :confused:
[Magisk] spicediablo:
Reverted to v16 with same modules and everything works fine...

Sent from Sagit
[Magisk] anz563:
https://drive.google.com/file/d/0B822OzP4wH8hanI4Mm9wdHFmRHM/view?usp=drivesdk
[Magisk] AndrOmega:
everybody with problems

please wait

version 17.2 will be released

:)
[Magisk] timebandi:
Since the latest stable update to 17.1, Magisk Hide stops working multiple times per day. A reboot fixes this problem.

Reverting back to 16.0 again :(
[Magisk] martyfender:
What is this: SafeInCloud.db?
[Magisk] fig404:
I have the bootloop issue after updating Magisk through TWRP, which caused my phone to unroot and unable to access TWRP again. Tried looking around for fixes, but found none that I can still do.

My android model is LG G3 D850

Attempted fastboot, but apparently my LG phone can only do that with root access

Booting to recovery brings me to the default 'Factory Reset' screen

However, I can access Download mode! Is there anything I can do via download mode?

EDIT: Turns out I had not lost TWRP! After deciding just to wipe my phone, selecting factory wipe in recovery mode brought me back to TWRP. Then I just copied ove rand flashed the Magisk Uninstaller zip and then flashed Magisk 17.1 works great and everything's back how I left it!
[Magisk] guest4711:
Enter recovery. Start Advanced - Terminal and enter

touch /cache/.disable_magisk

. Reboot. Magisk should start without modules. Enter MagiskManager. Disable "core only mode". Now you should see a menu entry for modules. Disable or uninstall xposed module. Reboot and enjoy.

.
[Magisk] Pfiou:
K-Settings not working after upgrading to 17.1

Hello,

Does anyone else has a problem with Advanced Settings from KangV on Magisk 17.1 ?

For me it briefly displays the app splash screen then immediately closes.

I tried to uninstall the app+ data then reinstalled it but no way.

This is annoying since many many settings are defined by this app and it's not possible to get access to them using standard settings.

Any idea ?
[Magisk] grantdb:
Would have been nice to know this especially since it's always been a bad idea.

On the uninstaller method I only had selected 3 or 4 apps when device crashed and bootloop then partial reset. So how many is bare minimum?

Thanks
[Magisk] ahmadshuib:
Hey bro, have you found the solution about grab driver?
[Magisk] paarnoutse:
At my device, after upgrading from Magisk 16.0 to 17.1 ANY app/process is able to check/find the SU Binary now, EVEN when the related app is set to hided in Magisk Hide (or added via the "magiskhide --add <name>" command).

Therefore ANY app - even all hided apps - can detect now that the device is rooted... :crying:

Previously (Magisk 16.0) '/sbin/su' was a symlink to '/root/<random_name>'

However, in Magisk 17.1 '/sbin/su' is just a symlink to '/sbin/magisk'

It can be found by any process, even when the related process/app is hided (shown when issuing the "magiskhide --ls" command).

As a result, apps like the Microsoft Intune Company Portal now detects that your device is rooted, Root Checker apps (even when hided) are now showing that your device is rooted, etc. Also SafetyNet checks are failing (eg. via the 'SafetyNet Helper Sample' app) for - as I guess - same reason (root detected).

Is this a general misbehavior in Magisk 17.1 for anyone?

Device:

OnePlus 5 running OxygenOS 5.1.5 (Android 8.1.0).
[Magisk] ISoreo:
Anyone have an issue about gps? i update to 17.1 and seem gps not working but 16.0 gps fully work
[Magisk] EinderJam:
I'm glad to see I'm not alone, but I didn't managed to fix it....

I'm wondering if flashing the latest uninstaller zip with TWRP and flash 17.1 after that would be enough (and safe). Has anyone an idea ?
[Magisk] Soumy1234:
I think it's a good idea. That's what I did. However, it will wipe ALL your modules so be prepared.
[Magisk] grantdb:
Read help pages

I found this page and I apologize for not reading before posting.

https://www.didgeridoohan.com/magisk/MagiskHide

Thank you
[Magisk] Soumy1234:
I have tried tinkering with Google Play Services as it kept crashing every time I checked SN and failed. I tried uninstalling, updating and hiding in MagiskHide. Now it crashes every 15-30 seconds and I lost Play Store verification. Can anyone help with this, please?
[Magisk] casouzaj:
I'm using kantjer's unofficial build. Everything is fine here. Regarding Intune, have you read this post of mine? https://xdaforums.com/apps/magisk/microsoft-intune-company-portal-t3611588/post77337823. Read page #17 of that thread, as well.
[Magisk] EinderJam:
Did you faced the same problem than me ? By the way, do I have to reboot/wipe some caches between uninstall and reinstall ? Speaking of modules, I didn't installed any, so no problem here.
[Magisk] Soumy1234:
I don't think I faced the same problem. I flashed 17.1 through TWRP but I couldn't get root, so I used the uninstall.zip.

No, you don't need to reboot and wipe caches. Just flash the uninstall, then reinstall and reboot.
[Magisk] paarnoutse:
Yes, the recommendation to add the additional entry in magiskhide is also part of Dreamer(3FM)'s Intune Hider module which I'm using. However, when Magisk Hider doesn't hide the SU Binary (even not for hided apps/processes), this - obviously - doesn't make any difference.

I'm reverted to Magisk 16.0 now, and all OK again. Didn't try Kantjer's build, but I guess bugfix versions of Magisk (17.2?) will be published soon...
[Magisk] Didgeridoohan:
Magisk v17.1 can hide root perfectly. And it doesn't matter that the su binary is a symlink to /sbin/magisk... As soon as MagiskHide is triggered it'll unmount those binaries so that any app looking for them will see nothing.

If apps are detecting root on your device, that simply means that MagiskHide isn't functioning, for whatever reason. Have you tried toggling it off and on again?

Edit: And if there's an actual issue, logs would be useful (or there likely won't be a fix).

---------- Post added at 21:27 ---------- Previous post was at 21:24 ----------

Technically, it's not about the number of apps on the list... It's about

which

apps you put on the list.