yashsingh1/xdaforums huggingface dataset:
[Magisk] SebaS-DG:
I don't know why or whatever the reason is, sometimes pokemon go detect my phone is modified, like it found the phone is rooted or something.

This Keep happening sometimes, and I just need clsoe and open the game.
[Magisk] yung40oz84:
Not sure if this is reported or know but if I click download or install a module from magisk manager 5.0.5 and 5.0.6 it downloads, then magisk FC. Then if I try to add the module it says this is not a magisk module. Here is log.
[Magisk] ferryry:
[HELP-MagiskManager v5.0.5 Error]

I was using Magisk v12.0 and MagiskManager v4.3.3, worked just fine (No prob with the installation, SafetyNet and MagiskHide didn't work). Then i saw the Magisk v13.2 and MagiskManager v5.0.5. I went to recovery, uninstalled the current Magisk and installed the newest one. I rebooted the system and installed the newest app. The app always crashed. I tried to re-installed the app but nothing changes. I tried to uninstalled the app, went to recovery, re-installed the magisk, rebooted the system, installed the app and still nothing changes. But if i went back to the earlier Magisk and the app, it went well.

Pls your advices. Sorry for my bad english and i hope you get what i'm talking about. Thank you for your cooperation.
[Magisk] espionage724:
+1, I've had this happen twice so far. Seems like it'll be fine for an hour, then all of a sudden PoGO reports it can't run on this device, and upon checking SafetyNet status, I fail both checks. Restarting the game doesn't help. Rebooting the device however does help (immediately after a reboot I can play PoGO and pass both SafetyNet checks).

I have no concrete proof this is because of Magisk nor do I really know why this would happen. I'm using a relatively stock install of LineageOS.
[Magisk] DanHakimi:
Alright, I'm lost. Please bear with me, I don't know which details actually matter.

I noticed Pokemon Go didn't just stop loading, but actually showed me a screen saying that my device was incompatible. I heard Magisk 13.1 was out, and assumed it got around the latest safetynet check, so I log in, I check safety net, sure enough it fails, and I go to update.

I think the first time I hit update, it might have said it was successful. I tried a few more times, but I think it only downloaded the update. At some point, it downloaded the update and rebooted... But it certainly hadn't updated.

I notice after a while that my root actually stopped working. I had Koush SuperUser for some reason -- was that wrong? I'm certain that I only installed what the Magisk threads told me to install, and I feel like that was phh at the time, but in the end, I see Koush's name in my SU app, so I guess that's what I have.

Magisk Manager showed SU as not working. And then, at some point, it showed it working again, but it says that I'm using "13/1:MAGISKSU (topjohnwu)." From what I read in the threads, that's the right one, and my magisk app seems to know that I want to use adaway, and I got a toast saying that adaway has root permissions now, but it can't do its thing.

I was sure that my magisk manager never got the 13.1 upgrade, so I went ahead and flashed the 13.1 zip it had downloaded (it still won't point me to a 13.2). I flashed it, rebooted, and... although it tells me I have magisksu 13.1 working, it still points out to me that Magisk v13.1 is available, and magisk is not installed (from the ****ing magisk manager, after I flashed the new version). Magisk manager is 4.3.3.

I need my phone tomorrow, and I need it on sunday, and I'm not going to spend a day sitting here, any time soon, resetting my phone to factory, rerooting, remagisking, and then setting everything up, once again, to what I've wanted it to be. But I'd rather not have to deal with ads until I get a chance to do that. Is there a way for me to fix this cluster**** without going nuclear, or is this a complete teardown?
[Magisk] digitman xxx:
Guys, i try a lot to Unroot my Preroted RR rom 6.0.1 as i have no alternative rom to my device yet. in order to get Magisk(Systemless) with osm0sis Script https://xdaforums.com/showpost.php?p=63615067

then try to extract boot.img from Rom zip and reflash it. it seems to success to unroot and already flash Magisk and yup got Magisk Manager on App drawer also can give apps root access by magisk. but Magisk itself and rom setting force closed everytime try open them So do u have an idea about why this happened or if i miss something here.?

using Latest Magisk 13.2

RR 6.0.1 rom

SM-G7102
[Magisk] suniluv:
Magisk Manager update (5.0.6) fixed the modules installation issue ?
[Magisk] NinjaBoyLao:
Dude, update the magisk manager app. the latest version of it is 5.0.6. please hit the thanks button if this helps you lol

---------- Post added at 04:54 AM ---------- Previous post was at 04:48 AM ----------

I'm on a stock rom on a moto x pure and i randomly fail and pass safetynet. i don't know what's causing it but i've performed a full and clean install (uninstall script from twrp, reboot, reboot to bootloader, fastboot flash stock boot.img, reboot, flash 13.2 in twrp) and i can't figure out what's going on. logs show magiskhide starting very reliably but ill occasionally get a break "-------beginning of crash" in between entries in the log. in my case, its affecting fe heroes and giving me that stupid 803-0001 error code. i can fix it and play the game, but it still crops up randomly. external safetynet checking apps always give matching results with what magisk gives, so i know i really am passing safetynet sometimes and not others.
[Magisk] Rohaq:
Seeing the same issue here on an HTC 10 running Viper 10 5.10.0

EDIT: Apparently there's a new version of Magisk Manager that was released since I downloaded it yesterday, I'll give that a go!

DOUBLE SECRET NINJA EDIT 2: Nope, I'm on 5.0.6, same issue. Nothing showing in the logs! :(
[Magisk] 7root:
Hi there. Don't know if this question was already asked (new to Magisk-related stuff), but do I need to unSU before flashing Magisk when I am switching from SuperSU? Or can I flash Magisk over SuperSU?

Also, will Magisk Hide work with Linux kernel 3.18.31 (ElementalX-OP3-3.05)?
[Magisk] teddy0209:
You have to unsu first... Magiskhide only supports magisksu... It should work on your device...
[Magisk] DodoGTA:
1. Do a full unroot from SuperSU app (Ask it to restore the stock boot image, but not the recovery image)

2. Yes
[Magisk] Mysterion1:
Here's the solution:

-> Go to TWRP

-> Wipe

-> Advanced Wipe

-> Select every partition and wipe it

-> Select System and repair filesystem. After that change filesystem to FAT. Once it's done change it back to the format it used to be before.

-> Repeat the last step with Data partition

-> Done! Now you can flash rom + magisk and magisk should work without any issues.

(This method worked for my M9 and my Nexus 7 II and can be used if you permanently lose root after second reboot or if you cannot install modules in magisk)

I hope that I could help you!
[Magisk] jenslody:
You need to fully remove any other root-solution before flashing Magisk 13.2.

SUperSU compatibility is temporarily removed and not (yet) back.

See also @Didgeridoohan's installation and troubleshooting tips for Magisk .
[Magisk] dastinger:
Yes I did. I also cleaned up the app's data, it didn't help.

Enviado do meu HTC 10 através de Tapatalk
[Magisk] HM13androfan:
Hello guys... Just a little question ... Doesn't Viper4Android work on Magisk V13.2... it has stopped processing after Magisk update on my ROM
[Magisk] DodoGTA:
Please attach a logcat: https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/
[Magisk] MKriiis:
Hi! I have Lenovo A536 with RR 5.8.3 (port) & TWRP 3.1.1. Magisk 13.1 & 13.2 not installs on my device. My recovery.log:
[Magisk] whalesplaho:
Try use adb method whether it ll work.....

Flash magisk uninstaller zip

Power off yur device

Reflash yur kernel

Reflash magisk zip 13.2

Reboot

Connect device with ADB mode

Remove Magisk Manager pre-installed app "adb.exe uninstall com.topjohnwu.magisk" without "

Install Magisk Manager latest app "adb.exe install MagiskManager-v5.0.6.apk"
[Magisk] dastinger:
Thanks mate, will try it and post back asap.

Edit: Flippin Tapatalk always adding the signature [emoji35]
[Magisk] DzikrRully:
Help me, I do downgrade to Magisk 12 & MagiskManager 4.3.3 cause I want use SuperSU. But I get lost SuperSU root access, I tried many times but still can't get root access from SuperSU.
[Magisk] Technical:
Does Magisk change the ramdisk?

I'm asking because using SuperSu I lost the ability to dualboot (http://xdaforums.com/showpost.php?p=64941117&postcount=1).

New (although MM version) Asus Zenfone 2 ZE551ML bootloader avoid dualbooting. I suspect it regards to ramdisk.
[Magisk] Artim_96:
remove superuser from /magsik (place a file called remove in /magisk/su), uninstall the app, reboot and install supersu
[Magisk] n9ntje:
So, at the risk of getting burned, I tried to get Magisk working on two different Roms on my Moto E (2015). Bootloader unlocked.

Followed the OP, installed phh from OP, installed phh from Play store.

First ROM is CM13, it didn't work at all

Second ROM is Slim ROM 6.0.1. I can toggle the SE Linux status on/off but the Root Status slides back when to toggle. I do get the " root access for magisk manager " from phh.

So. Anyone can help here?
[Magisk] :
I tried it on Stock 6.0.1 on Sony Xperia Z3C, bootloader unlocked.

Phone kept rebooting after a few seconds...
[Magisk] jhedfors:
Has anyone been able to use FlashFire with PHH Superuser? Suggestions?
[Magisk] havens1515:
You just need to toggle SE Linux policy in Magisk Manager. Make sure it's permissive for FlashFire to work. You can set it back afterwards.
[Magisk] jhedfors:
I stated in my post that I have already done this. Have you personally had this work for you?
[Magisk] Cinayet:
Is there any update plan for latest S7 Edge software? Seems like neither root and xposed is loaded
[Magisk] havens1515:
Yes, I have. You may need to swipe FF closed and reopen it after the toggle (if you opened it before toggling.) It must run its root check in OnCreate instead of OnResume
[Magisk] TCattd:
I have tried that. I know FlashFire runs with SELinux in permissive and can aquire root, but no operation finishes. If you try to flash any zip using FlashFire, screen goes black and the phone is stuck there until you hard reboot it. No matter how many minutes you wait at the black screen, the phone just don't get pass there.

N5x here, with Stock Nougat.

If i uninstall Magisk and flash SuperSu (Chainfire's version, non Magisk), then FlashFire works fine.
[Magisk] Zisi911:
guys if someone can help me please, i unrooted my phone , even reflashed to stock , when i flash from recovery the magisk always it seems that my device xperia z1 is bricked after i try to reboot and i always use flashtool to unbrick by flashing stock excluding the system. after that device starts it appears like the zip was flashed successfully, install the magisk apk, btw flashed the ssh's superuser for magisk, but it appears that device is not rooted at all and i cant toggle the mode. any help ?
[Magisk] cire27rn:
I will play it for enjoyment's sake
[Magisk] jhedfors:
+1.

This is exactly my experience.
[Magisk] NouNouXDA:
Hi,

I just wanted to say thank you for this. It works beautifully, with Xposed and everything, and I have got Pokémon Go up and running without a single issue!

I did not even have to reset my rom to stock! I just uninstalled root (I did it through the SuperSU settings, which has an Uninstall option) and Xposed (using my prior Xposed zip uninstaller) and then went ahead with the rest of your instructions. Works like a charm. (Screw you, Niantic. I am not a cheater.)

I was using the newest XtreStoLite rom on a Galaxy S6 (SM-G920F.)

For people that want to know whether their install worked, try the "SafetyNet Helper Sample" app on the Play Store with the Magisk root switch turned off.
[Magisk] SilverSix:
Ok, so... I'm on a Samsung Galaxy S3, and the latest stock available is 4.4.2. rip me. However, from what I've heard, and from searching the thread, you can flash Magisk even when on custom roms, correct?

I'm currently on Exodus 6.0.1, which is AOSP/Cyanogenmod based. The only tiny problem is that the flashables come with SuperSU built in. Would the following procedure be correct?

1. Full wipe (system/boot/cache/Dalvik)

2. Flash Exodus nightly

3. Manually delete SuperSU (assuming it's located on /system/xbin/su; will try to confirm with devs)

4. Flash Magisk

5. Flash SuperSU somehow (again, will ask the devs about this)

6. Flash other stuff (Xposed, APN fix, etc)

Also... once Magisk is installed, can we dirty flash roms with built in SuperSU and everything will be fine? or do we have to go through this process every time we have a new nightly build?

Thanks for your time!!

(Before I get heat for not searching the thread: I've done most of the research about these questions; I'm looking for more of a nod of approval. Just being 110% extra cautious because I'm not in the financial position to buy a new device in case this one gets bricked.)
[Magisk] stratonz:
I need some help: I've installed a custom kernel (boeffla) and Boeffla Config app doesn't work because it seems like it waits for root rights (that it has, using phh superuser). Some suggestions?

---------- Post added at 05:39 PM ---------- Previous post was at 05:36 PM ----------

Another problem: when I start my phone, I've always to enable root rights from developer configuration menu (also if it's already marked as app and adb). I don't know if it's related to the problem in my previous post...
[Magisk] sniper9911:
[/COLOR]

The app shows on the startup screen only granted permissions. After bootup you have to wait a bit, since the device still had some stuff to do before it had time to show the dialog to grant root rights. Otherwise take a look into the settings.

i have no granted permissions ..... tried to wait for too long (2hrs+) and nothing happened

i will try it again to make sure
[Magisk] alroger:
Of course custom ROMs.

3- yeah, gotta completly remove any signs of the ROM's SU. Check your ROM's thread for that and/or the SU's thread (like SuperSU's threads on how to completely remove)

5- no no no, why would you flash supersu again if you just removed it?? defeats the purpose of Magisk. For root, use a Magisk module - phh SU (the Magisk module, not the original).

Cheers.
[Magisk] tombriden:
Hi, the update script doesn't work if using KEEPVERITY as it still deletes verity_key which stops the rom from booting
[Magisk] SilverSix:
3. Sweet. I'll hop on to the Exodus G+ page to inquire about SuperSU.

5. Ok, that makes sense. Now... is there a chance that phh SU could create a conflict with the ROM?

Also, can I dirty flash nightlies (with a manual SuperSU removal, of course) after everything is all good to go? Or do I have to do this all again?

Thanks, m9! :D
[Magisk] 7root:
Thanks for your answer. But I have an interesting issue. Supersu fails to uninstall itself. What should I do? Can I use unSU I instead?

EDIT: just realized this might be the wrong thread, I will consult the SuperSU support thread.
[Magisk] DodoGTA:
Flash unSU to partially remove SuperSU, and then flash your custom kernel again to fully remove SuperSU
[Magisk] hendrali:
Somehow magisk 13.2 made Dirty Unicorns can't detect simcard after upgrading to the latest official DU rom. So i had to uninstall Magisk first using the latest uninstaller. Rebooted. And then reflash DU again. Simcard is detected again.
[Magisk] rfgamaral:
I've been running Magisk 12 without issues but ever since I upgraded (in-app) to v13.1 that I couldn't get Magisk to work (bootloops) with all the modules I used to have. Nothing I do seems to work and I have flashed the uninstaller and restored my boot + system image a couple of times. Every time I flash Magisk or install some modules, I get into a bootloop.

Right now I just finished flashing the latest uninstaller and restored once again the original boot + system image. Is there anything else I should restore before flashing Magisk 13.2?
[Magisk] DodoGTA:
Can you attach the recovery.log from Magisk v13.2 installation?
[Magisk] rfgamaral:
Where is that file located? But I'm probably in a state where I don't have it since I've restored everything back again to start over. I just need to know if I should do something else before attempting a new installation of Magisk 13.2.

EDIT: Just finished installing Magisk 13.2 again and it worked. Now I'm going to install the modules I used to have... Even with Magisk Manager v.5.0.6, modules fail to install. The app doesn't crash anymore, the files are downloaded but I think they are corrupt because I can't even manually install them (it gives an error).
[Magisk] DzikrRully:
Anyone have same problems?
[Magisk] ekksman:
You may Have to reflash ROM and SuperSU
[Magisk] Incuriousity:
Does anyone know have problem with magiskhide? My magiskhide indeed pass the safetynet check but when I open Fate/Grand Order it still detect root and gives me error 60. Anyone got solution for this?
[Magisk] DzikrRully:
Reflash full ROM or reflash clean boot image?
[Magisk] arrrow:
Does v4a work with the 13.x versions? I had it working fine until magisk got updated to 13.
[Magisk] ekksman:
Try the ROM 1st, dirty flash
[Magisk] tag68:
1. Are you sure Magisk 12 is compatible with SuperSU? My memory says it was compatible until 11.

2. Is there a special reason why you want to use SuperSU? Just curious what the advantage could be
[Magisk] DzikrRully:
Sure, I used 12 & SuperSU before update to 13.1
[Magisk] $!ngh:
My kernel doesn't have the mount namespace i am using kernel version 3.4.10 -ElementalX on my HTC ONE M7

wich kernel i should be using to bypass safetynet ?
[Magisk] jakito:
Hello, can someone help me with a crash?

Everytime I go in the section of root management in Magisk manager the app crashes. What log should I provide?

I'm in FreedomOS 10.3 on the OnePlus 3
[Magisk] rfgamaral:
I'm still having lots of issues and now I can't even revert to Magisk 12 where everything was working. I must be missing something... For now, I want to do this step-by-step instead of many things at once. For context, I have uninstalled Magisk and restored my boot and system image. Also cleared my cache and dalvik/ART cache, reboot and everything is fine.

Now, I have installed Magisk Manager v.5.0.6 and I get this:

Shouldn't ctsProfile be true also? It used to be before... So, for now, I just want to make sure I'm clean as possible. What am I missing? What do I still need to restore to make sure every SafetyNet check passes successfully?
[Magisk] woozie.2007:
Magisk error instalation

Hi everyone, can somebody help me to install magisk 13.2 vers? The only version that works for me is 11.6, but v.12 i can install but i haven't root and 13.2 i can't install, it gives me error 1 in twrp. I have moto xt1676 stock rom 7.0. I will atach recovery log. Thank you all
[Magisk] Einheit-101:
Very, very unstable... Randomly root stops working and the worst thing is that the xPosed module causes a bootloop.
[Magisk] DanHakimi:
****, man, even Pogo is working again. I thought I read we weren't getting around safetynet this time. Thanks!

Now, to find those ****ers at Google who took Magisk off the play store...
[Magisk] FartyParty:
Reinstall the manager, I had the same issue when it updated from V12 -> V13.
[Magisk] tool666schism:
Safety net failing again for anyone else? On 13.2. Core mode trick doesnt seem to resolve it either.

Edit: installed universal safetynet fix package and now I'm passing. Odd I never needed this before but whatever it's working.
[Magisk] Captain_Throwback:
If SafetyNet is passing, then the app uses additional checks to find root. Magisk Hide is doing its job.
[Magisk] godkingofcanada:
I'm going to share a few things I've learned in the hope it helps people. If you have SU and you try to install magisk it gets buggy, even if you remove SU sometimes it still acts up. If you used an app to edit your boot.img like dual boot patcher it will not work. I had magisk 12.0 and it would not let me upgrade. I used titanium to back up my apps. Wiped my phone n reinstalled the ROM and then magisk, and all went well. If stuck start from scratch. It has worked for me on two different phones with that method.
[Magisk] godkingofcanada:
It works fine if you do a fresh install of the ROM first.
[Magisk] godkingofcanada:
So did I. I can confirm it works.
[Magisk] prog-amateur:
Hi, on my side, since the update 13.1, Firefox crashes at start. Please find some information :

- Magisk 5.0.6, 13.2

- Meizu Pro 5 with ResurrectionRemix v5.8.3

Another person has the same issue (same model etc.). Thank you for your help.
[Magisk] nightauthor:
My post above links the exact software they are using to hide root in the Amazon Flex app.

Any help is appreciated
[Magisk] jenslody:
MagiskHide needs at least kernel 3.8.

---------- Post added at 04:47 PM ---------- Previous post was at 04:42 PM ----------

I don't see any attempt to install Magisk in the log.

It looks like TWRP itself does not start correctly.

Before this is fixed, flashing anything else will most likely not work.
[Magisk] marciorssilva:
OK, i tried to install Magisk 13.2 but i get error on google services..."google services stop working..." if i turn off magisk hide i don´t have the error but i can´t pass safetynet test...someone with same error...

LG G3-D851 with AOSP Extended 4.4.

Thanks
[Magisk] Didgeridoohan:
I think I saw you using the Universal SafetyNet fix module. Try uninstalling that and try again...

If you have installation issues post a recovery log from the failed installation.

If you're talking about SafetyNet you can't use Xposed. You'll have to disable it to pass SafetyNet. MagiskHide can't hide Xposed.

Are you positive this happens on v5.0.6? That version was released specifically to deal with that bug.

Have you tried with Magisk Manager v5.0.6? You'll find a link in the release thread.

Are you sure you're installing SuperSU systemlessly? Otherwise the Magisk installation script will remove it...

Clear data for the Manager.

You want to go completely stock? You'll have to also uninstall the Manager and relock your bootloader.

That recovery log is not from the installation. Try again and she the log straight after.

Try disabling MagiskHide. You probably have an issue with WebView... Check the FAQ in the release thread.
[Magisk] DzikrRully:
Yes, I'm sure. I'm installing SuperSU in systemless mode.
[Magisk] rfgamaral:
Not exactly sure what you are asking or suggesting... I'm already stock in the sense that I don't use any custom ROM. Yes, my bootloader is unlocked and I' m S-OFF (HTC 10 here) and I also have TWRP installed. Those are the only changes I've done to my device. Shouldn't SafetyNet pass with flying colors if the boot and system partitions are intact?

NOTE: As a reminder, I do not have Magisk installed for the time being, nor have I flashed anything else after restoring my boot/system image. What else do I need to get SafetyNet to pass all it's checks?
[Magisk] teddy0209:
Flash magisk, and activate magiskhide... That's all you need if you're using stock sense...
[Magisk] woozie.2007:
Thanks, maybe this one is good, i made it after trying to install
[Magisk] rfgamaral:
Not sure why it wasn't working before, but it is now, thank you :)

Another question though, probably a bit unrelated but this started to happening with all my magisk flashing and restores... I used to have a PIN prompt every time I rebooted my device and every time I launched TWRP, because my data is encrypted. This PIN prompt is now gone, it doesn't appear on either situation and TWRP mounts the data partition by default (it didn't before, it required my PIN). Is my data not encrypted now? I didn't change anything related to this, not sure why this started to happening. Thoughts?
[Magisk] admicos:
Here it is