yashsingh1/xdaforums huggingface dataset:
[Magisk] mogantivenkatesh:
Apps like Titanium backup, Greenify, Luckypatcher are not able to get root accesss
[Magisk] infernix:
So 10 hours later, the same app (one of 3 banking apps) detected root again. I checked a bit closer now, there's no mention of magisk around the time I'm starting the banking app. No clue how it's detecting it. Also, it doesn't help to toggle magiskhide off and on for that app - i have to turn off and on magiskhide as general setting. After that it's not detecting root. I'm going to try to revert and see how it goes with pre v18/6.1.0.
[Magisk] dope77:
I posted about my problem yesterday, i saw that a lot are facing same problem after 18.0 update

(after the 18.0 update, magisk hide literally hides root from all apps even the non selected apps. The root prompt won't appear in any of the apps, Is there a reason behind this? The only thing i can do is turning magisk hide off, go to app and grant root permission then go to magisk and turn hide on. And after updating the apps that need root, they won't work, the only thing that make them work is go to magisk supersu, removing the updated app, again turn off magisk hide, go to app and grant permission, then turn hide on. 17.3 was stable more than 18.0 which also keep losing root, restarting device will make root work again)

---------- Post added at 02:31 PM ---------- Previous post was at 02:29 PM ----------

Go to magisk settings and turn magisk hide off, this solved my problem

---------- Post added at 02:33 PM ---------- Previous post was at 02:31 PM ----------
[Magisk] Oswald Boelcke:
You are using LP??? You won't get any support now or in future at least from my side! Don't know what others do... I personally hate cheating...

Please allow me to quote the Forum Rules partially as they are pretty clear:
[Magisk] DB126:
On the same page but there is a sizable segment that is unapologetic about the lack of a ethical/moral compass. Report offenders and move on.
[Magisk] zooorgie:
Yes it worked to reinstall TWRP.

Now I installer Supersu from Play Store.

Says Im not routed ?

How do I get routed again ?
[Magisk] martyfender:
This is a Magisk support thread. There other threads dedicated to SuperSU.
[Magisk] zooorgie:
You are correct

Please point me to the right one, I have a little hard to navigate here.

Its a big forum :)
[Magisk] martyfender:
https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
[Magisk] Badger50:
https://xdaforums.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703

Depending on your device, SU may not work anymore. Might be best to look into magisk. Also, don't use the SU from the play store :good:
[Magisk] liquidblue1985:
So I cannot seem to boot into the system after flashing the zip (Pixel 3 XL).

TWRP 3.2.3-3

Dec Update - PQ1A.181205.006

When I flash the Magisk-v18.0.zip file and reboot into system I get a bootloop. It eventually goes back to the unlock warning page. I can reboot into recovery and flash the uninstaller and get back into the system. Am I forgetting to flash something else?
[Magisk] shiuhsung:
Running into a problem with magisk update thru magisk manager. The process of update directly (recommend) method just hangs (or it froze?) there . Any pointers of how to update to v18? Thank you !

Pixel XL stock
[Magisk] martyfender:
I don't know if this will help, but see [MENTION=4470081]topjohnwu[/MENTION] 's twitter feed where on Dec. 4th, he recommended not having TWRP installed to A/B devices, but have your stock boot.img and stock recovery installed and temp boot TWRP from a PC to flash Magisk:

https://twitter.com/topjohnwu
[Magisk] demonoidmaster:
Ok but that's what it's supposed to do, it disables root and magisk, reinstalling itself as another randomly name generated app that once you press it it reinstalls magisk manager and reenables root

---------- Post added at 05:42 PM ---------- Previous post was at 05:38 PM ----------

Why the **** are you posting about supersu in a magisk thread? SUPERSU IS LONG DEAD, DEPRECATED. stop using it

Actually better yet, stay on a stock rom, don't diddle around with trying to get twrp installed and magisk etc etc if you have no idea what you're doing, either that or give your device to someone that knows what they're doing

---------- Post added at 05:46 PM ---------- Previous post was at 05:42 PM ----------

Don't matter supersu is dead, who in his right mind would use it now that it was sold to the chinese? We got magisk and now we even got in-kernel built in root that anyone can patch the commit to their kernel builds if they want the feature
[Magisk] davestuarts:
hi, all. Ive been running magisk for a while now, had no major problems.

Updated to v18 about a week ago, no problem till now. updated has Snapchat has kicked me out.

I rolled back snapchat, still the same issue.

I rolled back magisk to v17.3. still the same issue.

following some older suggestions in these threads.

I uninstalled xposed. Rebooted. Hide snapchat in magisk. Reinstalled snapchat.

Still throwing me out.

I first thought it was a password issue, so changed it. So my titanium backup wont work (another suggestion i read).

I then installed SC on a unrooted phone. And login in to SC, no problem there.

I then rooted that phone, installed titanium. Created a new backup.

Transferred to my phone. Reinstalled the data with titanium.

SC logins in for a few seconds, then boots me out! Grrrr.

I did read a SC team message on the temp phone. Its said I am using a 3rd party app/plugin to use SC, which violates blah blah.

So, now I'm totally stuck and really dont want to unroot phone..or start from scratch.

Any ideas.

summary. Magisk 17.3

lastest snapchat

android 6.01

LG G5 - rooted

thanks
[Magisk] liquidblue1985:
That was totally it. 2 things just in case anyone else searches for this - ensure to not flash the twrp zip to fully modify the boot img and unselect the options to prompt installation when rebooting after flashing the magisk zip.

Thanks again!
[Magisk] davestuarts:
hi, all. Ive been running magisk for a while now, had no major problems.

Updated to v18 about a week ago, no problem till now. updated has Snapchat has kicked me out.

I rolled back snapchat, still the same issue.

I rolled back magisk to v17.3. still the same issue.

following some older suggestions in these threads.

I uninstalled xposed. Rebooted. Reinstalled snapchat. Hide snapchat in magisk.

Still throwing me out.

I first thought it was a password issue, so changed it. So my titanium backup wont work (another suggestion i read).

I then installed SC on a unrooted phone. And login in to SC, no problem there.

I then rooted that phone, installed titanium. Created a new backup.

Transferred to my phone. Reinstalled the data with titanium.

SC logins in for a few seconds, then boots me out! Grrrr.

I did read a SC team message on the temp phone. Its said I am using a 3rd party app/plugin to use SC, which violates blah blah.

So, now I'm totally stuck and really dont want to unroot phone..or start from scratch.

Any ideas.

summary. Magisk 17.3

lastest snapchat

android 6.01

LG G5 - rooted

thanks

UPDATE - fixed

My cts profile & basic integrity were failing.

applied MagiskHide Props Config module

applied saftypatch.

Problem solved. MagiskHide working, Hence Snapchat working.

Still keeping Magisk 17.3 installed for now.
[Magisk] gvsukids:
Pixel 3, losing network access after applying root via TWRP or manually patching boot.img. I'm on v18.0 also system UI has stopped. Remove root and everything normal.
[Magisk] jcmm11:
An install log from flashing Magisk may be helpful. You may also want to check the following threads:

https://xdaforums.com/pixel-3-xl/development/twrp-3-2-3-0-pixel-3-xl-t3861623

https://xdaforums.com/pixel-3-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3857195

If you want to run a custom kernel - personally I'm running Kirisakura and am happy with it so far.

https://xdaforums.com/pixel-3-xl/development/kernel-kirisakura-1-0-0-pixel-3-xl-aka-t3864563

Edit: I see you solved the issue. FWIW you should be able to flash TWRP if you really want to (I haven't, although I may down the road. I tend to agree with topjohn on this though). Recommended way to do that is:

Start with a stock boot image. Then

- fastboot flash boot --slot all boot.img

- fastboot boot twrp.img

- Install twrp.zip

- Reboot recovery

- Install Magisk-18.0.zip

- Reboot system

-if you want to install a custom kernel do it after installing Magisk.

There is no longer a separate recovery partition. Recovery (stock or TWRP) is now part of the boot image. I think (not sure) that the current state of affairs means if you flash TWRP after Magisk you'll lose Magisk.

If you're having problems reflashing the stock kernel to both slots is always a good place to start.

---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------

Thanks for the logs. Very helpful.
[Magisk] gvsukids:
What logs?
[Magisk] jcmm11:
FYI the stable links don't work anymore. The SR5 links on chainfire's site are still working.
[Magisk] jenslody:
You know what irony is?

How do you expect any help without logs ?
[Magisk] gvsukids:
What logs do you want?
[Magisk] zooorgie:
The advice I have read is not to install Magisk after changing ROM.

Now I run Lineage 15.1

If not using Magisk (I guess I cant use them both)

From where should I install Supersu, if not from Google Play ?
[Magisk] jcmm11:
You got bad advice. There's no reason not to use Magisk after changing ROMs.

Lineage (afaik) has its own rooting solution so maybe that's why somebody said that.

As long as you completely remove any other rooting solution you should be able to install Magisk (assuming the phone isn't too ancient. Android 5+ I believe. Someone will correct me if I'm wrong). Recent lineage should be fine.

If you really want to try SuperSU there were links posted in response to you earlier. Use the beta thread. The stable links don't work any more.

---------- Post added at 01:25 AM ---------- Previous post was at 01:21 AM ----------

Magisk logs, logcat would be helpful. For what you describe probably a logcat would be more helpful but both can't hurt
[Magisk] gvsukids:
here are log in 2 parts
[Magisk] FlavioV:
LineageOS comes with its own root solution. If all you need is root you should be fine with it. But you'd need to find a separate app to deal with SafetyNet (some roms include a custom manager by default though). Magisk modules won't work without (wait for it...) Magisk either.

Regardless of your choice, if you want to use a different root solution (Magisk or SuperSU) it's recommended to flash the su removal addon first. You can find it on the official LineageOS downloads page. It works even in unofficial builds and LOS-based roms, just be sure to download the file that matches your system version (15.x for Oreo, 14.x for Nougat).
[Magisk] Thari.pt:
After magisk 18.0 update my device cannot detect root all new installed apps i go to magisk setting but all are correct i thing 18.0 update has a bug run in some devices please fix this bug

My device is lenovo a1000 android 5.0

Thank u sir.
[Magisk] spambayes:
I did try toggling MagiskHide On/Off and rebooting in between but that didn't change anything. I'm not sure if the mount namespace kernel is a requirement for basic root functionality of Magisk, but I would think not because I have been rooted with Magisk since v13.3, unless this is a requirement imposed in a later version.

---------- Post added at 07:11 AM ---------- Previous post was at 07:05 AM ----------

Yes. Xposed is installed. And the next step for me would have been to uninstall that had regressive trial-and-error of previous versions of Magisk failed. Fortunately, I was able to restore root after trying Magisk v17.0 so I'll leave Xposed alone for now.
[Magisk] MattP410:
Safety Net Failure

I just rooted my Mediapad M3 8.4 with Magisk v18.0, and at first passed the Safety Net with flying colors. The only thing I did differently on this device, as opposed to the numerous other devices I've passed the Safety Net on, was installed and attempted to use Apps2SD and Link2SD. I also partitioned my SD card to use these apps. I declined any request of the apps to modify my system files as well. I can think of no good reason why the Safety Net is all of sudden failing. Any advice or remedy would be greatly appreciated.
[Magisk] spambayes:
No, I have not restored a completely stock boot image - something to consider for an "if all else fails" scenario.

Unfortunately no. Didn't think of saving it because no errors occurred during installation.
[Magisk] martyfender:
From what I have been able to gather, it is only a requirement for Magisk Hide.

No one else has posted to the contrary.
[Magisk] :
Any tips on passing safetynet with Magisk 18 and unofficial LineageOS 16 on Oneplus 5? I get CTSProfile mismatch.

This rom already has the fingerprint set to a good one:

OnePlus/OnePlus5/OnePlus5:8.1.0/OPM1.171019.011/1808081927:user/release-keys

I use Franco Kernel. The issue was same for official 15.1. And also before flashing Franco and Magisk, I still got same mismatch.

If I flash Magisk 17.0, safetynet is passed with no issues at all. What has changed since then?

Edit:

Fixed with "magiskhide props config" -module!
[Magisk] peterlee928:
hi all. i am having an issue passing safetynet. any thoughts on how to fix?

-google pixel 2xl

-stock rom

-busybox by osmosis

-magisk 18.0 stable

i have tried dirty flashing the stock rom. also toggling magiskhide off and on. also installed mh props config and changed the fingerprint. bur any fix is temporary.
[Magisk] Bangdennoy:
Hide Magisk Feature Is Missing

I want to ask some question.

why my "hide magisk" feature is missing in my magisk.
[Magisk] martyfender:
https://www.didgeridoohan.com/magisk/MagiskHideHelp

https://www.didgeridoohan.com/magisk/MagiskHide
[Magisk] gvsukids:
Any luck?
[Magisk] Oswald Boelcke:
That was the first thing I did. I reported it but I couldn't refrain from speaking up and to tell this guy why no support by me can be expected.

This is a Magisk thread. Why did you install SuperSU? Do you try to run two root management applications in parallel? That won't work. My personal opinion: If your device is rooted, forget Supersu and simply flash Magisk v18.0 or any beta of your desire. Or follow @martyfender, @demonoidmaster and @Badger50 suggestions if you're more happy with Supersu.
[Magisk] Jaheen:
Magisk is doing a great job!

Now Phonepe has grown up and become more secure.

Magiskhide does its job well but yet, when trying to make payments via phonepe in other apps (flipkary, swiggy or zomato), transact fails.

Earlier, i faced this issue but at that time magiskhide helped me. Now on the phonepe v3.3.37, check bal & transaction does not work until magiskhide. Even though magiskhid, payments via phonepe does not work.
[Magisk] D3m0n1q_733rz:
Just a few small issues here and there

There seems to be a problem in the new v18 Magisk which causes a corruption in some boot roms. In particular, my Blu Life One X2 had its boot corrupted to the point that it couldn't even access the SD card in TWRP. Any boot backups from Magisk (and the entire Magisk folder) were unavailable on the system's ROM. Luckily, I kept a backup, so I was able to restore it. But you may want to take a small look at it to see if something had changed by mistake.

Also, there's a small, but annoying, bug in the Manager that crashes the manager when it tries to directly update Magisk through its automatic update procedure. What has worked as a work-around is installing the downloaded Magisk update in the module installation section. There was also a problem which would crash Magisk Manager almost immediately if the side menu wasn't opened directly after loading. So, it appears to be an error in the update code.

Thank you.
[Magisk] xunholyx:
It's in Magisk Manager's settings menu
[Magisk] infernix:
On v17.3/6.0.1 and my banking app doesn't detect root anymore. So there is definitely something different with v18 or v6.1.0.
[Magisk] martyfender:
I no longer trust the direct install method, as I have had too many times where I have had to restore a stock boot.img to get the system to boot again. I test Unofficial and Canary builds on 5 devices.

I now always flash through TWRP and never have any problems. Supposedly this was fixed some time back, but I still had it occur when choosing direct install. When this happened my system would only reboot to the bootloader screen with an error message. Back then, I provided logs in the unofficial thread.

To be honest, I have not attempted direct install since 18+ has been out to find out again.
[Magisk] deeppans:
[MENTION=4470081]topjohnwu[/MENTION] anf other please help me

After installing Magisk v18.0, I saw 2 versions Magisk manager. I lost permissions given to apps.

Can this happen 2 icons or versions of Magisk manager installed and having *different package name*?

One package name was having something like com.(some arbitrary string like) pvr.

When long pressed, one show shortcuts like Superuser, Modules, etc. But other was not showing anything like that.

Also when I opened Magisk manager, clicked Superuser or hide, a pop up came in asking "Magisk Manager" asking magisk manager root permission. Weird for me.

TIA
[Magisk] Wolfcity:
Have you by any chance hidden your Magisk manager before you updated magisk?

In this case I recommend a clean install of v18 by using latest magisk uninstaller
[Magisk] strangeFace:
I have exactly the same problem with Unity - based games. And not only me :

https://king4ng.wordpress.com/2018/05/16/error-when-playing-games-c8-users/

Hiding Magisk for those games doesn't help.

I'm attaching logs for two games: Desert Worms and Lara Croft Go.

Device: SM-T320 (Galaxy Tab Pro 8.4)

ROM: Resurrection Remix 5.8.5

Android 7.1.2

Magisk 18.0 and previous versions.
[Magisk] Astir95:
I'm trying to install Magisk v18 on my HTC 10 running LineageOS 16.0, but I cannot get it to work. The Magisk Manager keeps showing "Magisk is not installed.". I tried the two following installation methods, each with a stock boot image:

1) Reboot to TWRP recovery and flash the Magisk zip through ADB sideload.

2) Patch the LineageOS boot.img file through Magisk Manager, reboot to Download mode and fastboot flash boot the patched image.

No errors show in TWRP recovery or Dowload mode. What could be the reason Magisk is not being installed?
[Magisk] martyfender:
Don't use ADB sideload in TWRP, just click the install button on the main TWRP page, navigate to the Magisk.zip and select it, then swipe to install it. And, if this is not obvious, the magisk.zip must be on your device and not on your PC, like with ADB sideload.

Who told you to sideload it and not do the normal TWRP install?
[Magisk] jenslody:
Make sure the MagiskManager is not installed on adoptable/external storage.

If it is, move it to internal and try again.
[Magisk] ekowwillis:
Pixel XL stuck on charging screen

[MENTION=4470081]topjohnwu[/MENTION] there's this curious case where my Pixel XL doesn't charge when it's OFF after flashing Magisk but charges without Magisk.

It started from v16.0. and was resolved with v17.3(17302) but unfortunately v18.0 has introduced the problem again.
[Magisk] Astir95:
Could you ELI5 what the difference is between flashing in TWRP recovery of either a ADB sideloaded zip or a local zip file? Up to now I've always flashed using my computer and ADB sideload when in recovery (seamless install of LOS/Gapps), so it'd be good to know what the differences are between these two methods and whether there are downsides or risks.

This was the reason, thanks! Here I was thinking that apps in general are installed on the internal storage if there is free space. Has this never been the case, or did it change somewhere recently? (Android 8/9)
[Magisk] jenslody:
As far as I know, Android docs say, that internal storage should be used unless external is explicitely declarec in manifest-file.
[Magisk] Rooks:
It's strange to notify that my J6+ does not connect to PC (USB Device Not Recognized: Unknown USB Device(Device Descriptor Request Failed)) after flashing latest Magisk-v18.0(18000).zip file.

Also Odin does not show the device to be connected.
[Magisk] Invisan:
Has really no one a Idea whats wrong with the image? Or can have a look at it?
[Magisk] ilkaayy:
I'm on ResurrectionRemix Rom 8.1 Samsung galaxy s9+

Magisk v18.0

Installing a module doesn't work. It installs in a good way, I reboot and then nothing...

Tried multiple modules.

Magisk Basic mode is OFF.

On HighOnAndroid I saw a magisk for ResurrectionRemix Rom version just now. Do I replace the v18 with that one? If so, how?!

Can someone please help me

---------- Post added at 03:10 PM ---------- Previous post was at 03:10 PM ----------

I'm on ResurrectionRemix Rom 8.1 Samsung galaxy s9+

Magisk v18.0

Installing a module doesn't work. It installs in a good way, I reboot and then nothing...

Tried multiple modules.

Magisk Basic mode is OFF.

On HighOnAndroid I saw a magisk for ResurrectionRemix Rom version just now. Do I replace the v18 with that one? If so, how?!

Can someone please help me
[Magisk] martyfender:
Have you tried to download and install the modules through TWRP?
[Magisk] lazye53:
I have a strange problem. I'm using the Nubia Z17 NX563J.

I am a university student and the university I am a student is using the Eduroam system for wifi service. My problem; If I have a wifi connection when I flash magisk, but I can reach 5-10 kb / s, when I remove the magiski from my phone, my speed reaches 2.5 mb / s.

Please help me with this.

I would like to mention that I don't have the same difficulty in every wifi, and my wifi connection takes place smoothly.

---------- Post added at 12:22 AM ---------- Previous post was at 12:22 AM ----------

I have a strange problem. I'm using the Nubia Z17 NX563J.

I am a university student and the university I am a student is using the Eduroam system for wifi service. My problem; If I have a wifi connection when I flash magisk, but I can reach 5-10 kb / s, when I remove the magiski from my phone, my speed reaches 2.5 mb / s.

Please help me with this.

I would like to mention that I don't have the same difficulty in every wifi, and my wifi connection takes place smoothly.
[Magisk] martyfender:
I wonder if restoring stock boot/recovery, then temp booting twrp with fastboot, install Magisk, would solve that issue, also?

See [MENTION=4470081]topjohnwu[/MENTION] 's Twitter feed on Dec 4th as to why he recommends not installing TWRP.

https://mobile.twitter.com/topjohnwu
[Magisk] angelillom:
GRACIAS a todos de antemano ............

Tengo un Huawei P20 Lite android 8.0 con TWRP y Magisk 18.0 y quisiera saber como puedo instalar la ultima version de OTA , es decir la oficial que te manda el telefono pero no puedo por miedo a cargarme el sistema o el Root , el caso es que no encuentro ningun video y en Xda Developers si no escribes en Ingles nada y mire de utilizar el traductor y destroza las frases ... no se si me entiendes

PORFAVOR Ayuda y GRACIAS
[Magisk] Pkt_Lnt:
numero quattro

https://xdaforums.com/announcement.php?a=81
[Magisk] martyfender:
Sorry, but this is an English only forum. Ingles forum only.