yashsingh1/xdaforums huggingface dataset:
[Magisk] Pkt_Lnt:
No thanks. I have hearing loss so those modules mean nothing to me.

Check out this, looks like bad module ju-ju.

https://xdaforums.com/showpost.php?p=73082817&postcount=16773
[Magisk] sirwin44:
I cant get 13.3 to boot on my Samsung Tab A (t-280, andriod 5.1.1). It just hangs at boot screen. i can get 12.0 to boot using this method https://xdaforums.com/galaxy-tab-a/development/recovery-samsung-galaxy-tab-7-0-sm-t280-t3579291 where i had to flash a boot img. Do i have to flash an img for 13.3? if so where can i get it?
[Magisk] zerolam:
Updated to 13.3 with the same issue

Uploaded two videos for your reference

https://youtu.be/ggqk9nqIXRU

https://youtu.be/9xo_5zc_JUw
[Magisk] karthik km:
Latest updated magisk manager apk is not working at all ( version 5.1.0)

Its always not responding
[Magisk] Danny1976:
Same here. App open and won't load version 5.1.0.
[Magisk] majutsu:
Sadly, my phone still cant pass CTSprofile in 13.3.

(Resurrection remix N 5.8.3 - Vega iron 2)
[Magisk] ForgottenDude:
Working perfectly! (No freezes, even using Viper4Android)

Coming from 13.2. Updated the Manager first. Then tapped "Download & Install". It flashed Magisk 13.3 through Magisk itself. Tapped on reboot.

Rebooted and up and running in 10 seconds.

Redmi Note 4

AEX 4.4 (7.1.2)

Viper4Android Magisk Module by Topjhonwu
[Magisk] lalitjoshi06:
Without module Magisk manage 5.1 working but as I install dolby atmos (LeEco Le Pro3) module, its not working.

So I am using previous magisk manager with 13.3 version.
[Magisk] PFusion:
Is there anyway to get this version 13.3 working with a Google Pixel XL?

I've tried the unofficial version by goodwin+c but it's only v 13.0 and doesn't seem to work
[Magisk] lou2s:
Smooth update from 13.2 to 13.3 on Oneplus One.
[Magisk] yochananmarqos:
Of course it provides full root access. It sounds like something is borked on your end. All my root apps including Termux work just fine. I would do a clean install of Magisk.
[Magisk] boxguy1:
Guys I know this might have been asked but can some one tell me how to manually uninstall magisk modules
[Magisk] Xaif:
Try these to fix issue

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post73080027
[Magisk] ashmint:
Guys any fix on how to make the magiskmanager open after flashing 13.3, I even clean flashed my rom with 13.3. . The manager opens without any modules installed, but won't open if any modules are installed , I tried 5.1.0 manager and 5.0.4 ;/
[Magisk] karthik km:
Flash uninstaller of particular module via recovery

That's it
[Magisk] ashmint:
NVM it works when I use 5.0.6, so should I wait for a couple of days and then update to 5.1.0?
[Magisk] ForgottenDude:
Which modules, though? It is working for me even with Viper4Android module installed.
[Magisk] Angeloftheafterlife:
Same issues here on 5.10. I just completely removed magisk and reinstalled, but I'm still getting stuck at the splash screen. It looks to be an issue with the update service, according to logcat.

07-19 00:08:27.935 W/ActivityManager(1848): Activity pause timeout for ActivityRecord{add69bb u0 com.topjohnwu.magisk/.MainActivity t837}
...
07-19 00:08:32.834 E/JobServiceContext(1848): Time-out while trying to bind 804064a #u0a246/1 com.topjohnwu.magisk/.services.UpdateCheckService, dropping.

works fine on 5.04
[Magisk] braschlosan:
Hello I have a samsung galaxy tab s running android 6.0.1 with magisk 13.2 and it the update to 13.3 fails with an error. What can I do to resolve this?

The tablet is running this lightly modified Samsung rom if it matters https://xdaforums.com/galaxy-tab-s/development/marshmallow-rom-t3620522
[Magisk] FallenAngelII:
I'm on Samsung Galaxy S8+ (custom rom, Batman Rom 1.0). As of version 5.1.0, Magisk Manager will not go past the initial splash screen. It has nothing to do with 13.3 as I updated the app first before updating to 13.3. I had to manually flash 13.3. Magisk still works (I went from not being able to play Pokémon Go as of two days ago to being able to play it once I flashed 13.3), I just can't start the Manager.

Which is the 2nd to latest build? I'll just downgrade to it for now.
[Magisk] Snake-Plissken:
I just updated magisk and magisk manager and everything works just fine. I dont know if its allowed to ask here but is there a way to make the Entrust app work with magisk. It seems to use a different method of detecting root and not safety net. I can use android pay and pokemon but not entrust.

Any ideas?
[Magisk] chazarss:
Hi, magisk manager is not launching here as well
[Magisk] slssdhs:
magisk 5.10 cannot use :(

It stay at the mask screen and after a while system will notice me "magisk isn't responsing, do you want to close it?"

Please fix this issue, thank you very much!
[Magisk] joeriv:
Magsik manager is not working for me to.

For those who's magisk won't start do following steps:

1. Download magisk uninstaller

2. Download latest magisk zip 13.3 + latest manager

3. Uninstall magisk with the uninstaller in TWRP

4. Flash magisk 13.3 in TWRP

5. Reboot and install the latest manager

Reason magisk not working is the modules.

For me it was OG+Youtube causing this.

After trying to install the .zip magisk froze immediately (see screenshot)
[Magisk] Rom:
Same for me, and concerning my loggcat i don't know if it's really due to a module.
[Magisk] otonieru:
Well, just updated to 5.1.0

And it wont launch as well. Stuck on splash mask screen...
[Magisk] Darkaeluz:
Mine works fine, I don't have any module except for uncertified error fix

ROM: AICP Nougat 7.1.2
[Magisk] spoxxx:
S8 + Car HD rom magisk after the update does not work is not detected in the system. Just like the manager. Please fix it because I can not use android pay and properly with many programs
[Magisk] rhystagram:
Did you install the s8 duel speaker module by any chance?
[Magisk] kramer04:
Up
[Magisk] langithitam:
Hi [MENTION=4470081]topjohnwu[/MENTION]

i've tried to iflash magisk v13 using twrp on cm13 and it causing me bootlop. then i've flash the uninstaller android boot again, but it corrupt my android system.

i've tried to wipe cache dalvik, but still. the result ia lots of my app stop to working. is there a manual way to make fix this problem e.g using file manager in twrp?

my device is redmi note 1 lte

please dont gave me suggestion to flash my android...
[Magisk] teddy0209:
Try restoring boot.img via recovery... Remove the magisk.img in /data if it's still there...
[Magisk] Ramzh:
Installed the latest Magisk Manager, but when I start the app stays on the logo and reboots the device after a while.

I'm using HTC M8 on the latest rr
[Magisk] lulli1:
Thanks a lot for updating Magisk. Now safetyNet check works again on darkrom 7.1.2 LOS based.:good:
[Magisk] Pvcabr:
Had to reinstall magisk.

First recovery then flash the uninstall, after that flash the latest 13.3.zip.

Reboot and then install the flash manager 5.1.0
[Magisk] Rom:
For for your procedure, but it's remove the magisk modules u use also ?
[Magisk] machristoph:
I can confirm that on my Galaxy S7 Magisk Manager 5.1.0 got stuck on splash screen. Clearing data did not help. Uninstalled Magisk Manager and reinstalled 5.0.6 from apkmirror which seems to work now.

Did not yet install Magisk 13.3.

I read about others having similar problems with ARISE sound system installed. This could also be the issue here..
[Magisk] Angeloftheafterlife:
I also have arise sound system magisk module enabled and was having the same problems. Downgraded magisk manager for now. May try removing the module and re-up grading to see if that fixes it.
[Magisk] AtField:
can someone tell me why i get this error :"updater process ended with error: 255" if i try to flash a mod with a modified name in update-binary (i changed the name from your_mode_name to cerberus) instead if i flash the same zip, without the modified name it works?
[Magisk] toinux:
changing dpi

Hi, I followed the instructions to change dpi : /cache/magisk/dpi/post-fs.sh containing

#!/system/bin/sh
setprop ro.sf.lcd_density 340

I did chcon -R u:object_r:system_file:s0 on /etc/magisk but dmesg gives me this :

[ 3.997510] init: avc: denied { set } for property=sf.lcd_density scontext=u:r:toolbox:s0 tcontext=u:object_r:sf_lcd_density_prop:s0 tclass=property_service
[ 3.997605] init: property_set("ro.sf.lcd_density", "340") failed

I'm using sultan's CM 13 on my oneplus one.

Any idea ? Thanks.
[Magisk] Nomelas:
Uninstall everything, reflash kernel+system and the try again. If you use xposed you need to use a systemless one. The latest from topjohn is v86.5 and is compatible with magisk. These all work for me.

---------- Post added at 09:47 PM ---------- Previous post was at 09:45 PM ----------

Me too!
[Magisk] CRXed:
Thanks for your continued efforts!

Question: Would it be possible in the future to have Root/Xposed be disabled on a per-app basis?

I.e. disable/hide root and/or Xposed for that single app that you need? Not specifically talking about AP now, but it would be nice to not toggle switches or reboot to get an app, that checks for root/Xposed, working.
[Magisk] -Happy Feet-:
Hello

I have try to install it on my Xperia Z3 with Existenz ROM (Android 6.0.1). I Uninstall superuser but this fails maybe. I stuck at "uninstalling". Over the recovery I flashed all files but after reboot I have an broken Recovery and boot. Only fastboot works..

What is wrong?
[Magisk] felipemorais_:
I did.

I have a ASUS Zenfone 2, this were my steps:

1) went full stock

2) flashed twrp recovery

3) flashed both magisk and phhsuperuser zip files

4) installed phhsuperuser app from PlayStore and Magisk Manager apk file

Then, when I open Magisk Manager it's like my phone is not rooted at all
[Magisk] Aakash Kaushal:
Well i tried to reinstall the magisk by uninstalling it....and yippie pokemon go is working now :laugh: but xposed is gone....i dont know why only one thing works either magisk or xposed
[Magisk] nozz93:
Hi, I hope you don't mind me asking but is there any progress for Sony devices? My Z1 Compact shows the same behavior on stock 5.1.1 ROM (not even Sony logo after rebooting, just red LED flashing) and on CM 12.1 (stuck on Sony logo). I can provide a boot image and more information if you want to take a look.
[Magisk] Nomelas:
You have the wrong xposed version installed. Uninstall it and install topjohn's one v86.5
[Magisk] chris9000:
Managed to verify root was working, phh su doesn't seem to behave. Seems to give me a blank screen. Can't use Magisk Manager properly as a result.

EDIT: Got it working

I think I found my problem from earlier. Beta build of 7.0 for 6P doesn't work at all. But it works just fine with stock 6.0.
[Magisk] Firebird3334:
Hi, I currently have the CM 13 ROM installed. This has a built in root. How do I get rid of the root?

P.S: I have very limited knowledge when it comes to all of this so please explain in layman's term.
[Magisk] smellz:
Have now done the following .

1. Cell unroot per SuperSU ( If only a short note, then the app closed )

2. boot into TWRP manually and flashed Magisk - v6

3. next phh 's systemless superuser ) with Super SU magisk version already tried )

4. Mobile launched new

5. After that, it will not boot - When loading only the LED that flashes red and I have to flash a new firmware ...

Anyone know what I'm doing wrong ?

Have a Sony Xperia Z3 D6603

gerooted and SuperSU ( 2.78 )

TWRP 3.0.2-0

Rom : PureX v5 ( Android 6.0.1 - 23.5.A.1.291 )

Locked Blootloader

would be great if he had a solution for me ...
[Magisk] 4RK4N:
huge thanks man. making pokemon go work again now that they have safetynet.

u should change the OP about the api part with tasker. i thought i needed the "use root" option in the "run shell" action settings. making disabling root work but not enabling it again coz no root. without the "use root" option on both actions everything works.
[Magisk] westeight:
Latest Pokemon Go works perfectly with Magisk / SafetyNet:
[Magisk] CrazyCypher:
Nice! :)

I know open source means a great thinig, but does that also mean that it will be easier for "them" to study it and prevent/detect it and again disable its use?
[Magisk] JimSmith94:
This tasker profile has been working well for me: http://xdaforums.com/showpost.php?p=68291750&postcount=836

I added more apps to the list by tapping on the App Selection list under the profile. That will bring up a list of apps that you can select or unselect.

I'm surprised that this profile isn't getting more exposure, as it works great!
[Magisk] SilverSix:
I AM SYSTEMLESS!!!! Million thanks to OP and to [MENTION=4101982]alroger[/MENTION] for answering my questions!!

Now, to a more serious question that feels dumb but I thought I'd ask anyway... When we remove root through Magisk Manager, will all Xposed modules cease to work? Or will they function normally?
[Magisk] Tesla:
Thank you so much. Great work m8. :good:

Works on my Note 3 N9005 with CM13 rom in sign.

:good::good::good::good::good:
[Magisk] napster113:
Mine still work fine
[Magisk] gmes78:
Root isn't working on my Zenfone 2 with Resurrection Remix.

I tried:

Flashed Resurrection Remix 5.7.3 and open gapps

Removed the su binaries from /system/bin and /system/xbin to avoid conflicts with phh's Superuser

Flashed Magisk, phh's Superuser and Viper4Android

Rebooted

The superuser app was not working at all and Magisk Manager couldn't turn off root or SELinux(probably because it didn't have root).

Then I tried setting SELinux to permissive with adb shell and the Superuser app started working, so it may be a problem with SELinux policies.
[Magisk] D-m-x:
Did anyone try that yet? Only thing I can say that I have a Shield Tablet without the Arise Module and Magisk Manager works fine, on my 6p however I'm also stick at the Splash Screen.
[Magisk] Timmmmaaahh!:
Same here on OnePlus One (latest official RR). I've captured three consecutive crashes in a logcat.

Edit: fixed after clearing app data (thus, resetting all root permissions).
[Magisk] smohanv:
I updated magisk 13.3 and also magisk manager 5.1.

I could not open magisk manager. Several apps requiring super user permissions are not working as magisk manager is not opening.

I could not uninstall new magisk manager 5.1 either. Finally, deleted magisk manager folder via twrp and restarted and installed magisk manager 5.0.6. Also flashed magisk 13.3. All is well.
[Magisk] Didgeridoohan:
Weird... I've flashed Pure Nexus a couple of times (yesterday, actually) on my Nexus 6 and haven't seen that when installing Magisk. Did you do a clean flash of the ROM?

Anyway... It shouldn't be an issue. It's just an information message that it's mounting /system read-write. And since you're using a custom ROM that won't be an issue.

What error? We're not mind readers. :p Lots and lots of logs, please.

I think you're going to ask your friend how he/she does it.

There are ways of using Xposed and passing SafetyNet, but it is not the easiest of processes. You'll need to use a combination of Magisk v12, a modded systemless Xposed version, SuperSU, suhide and have an Android security patch from no later than October 2016 (or apply some quite specific patches to your device). None of this belongs here though (I will not answer questions regarding this) and you can find all of this information in the SuperSU forums (suhide thread) and Xposed forums (topjohnwu's systemless Xposed thread).

That result means that MagiskHide is working on your device. I have written a bit about his in my guide here (look under "SafetyNet"): https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828

This can usually be fixed by clearing data for the Manager.

I just tested on my Nexus 6 with Magisk v13.3 and Manager 5.1.0. I can delete system apps perfectly fine with both FX and Titanium Backup... You might have some other issues with your setup.

There is no such limitation. The only limitation might be that older apps can't recognise MagiskSU as a root solution, either because they don't recognise systemless root or that they use hardcoded paths to su. If that's the issue the app needs to be updated.

Other than that there should be no issues.

No idea. Capture a logcat from the crashes and someone might be able to tell...

You can roll back to an earlier version of the Manager, or boot to recovery and use the Magisk Mount script to mount the Magisk image to /magisk. Then you can use the recovery file manager to navigate to /magisk and delete the module.

If the suggestion by [MENTION=3615867]teddy0209[/MENTION], try dirty flashing your ROM.
[Magisk] cygery:
Thanks :)

Just wanted to let you know that the issue is still present in Magisk 13.3.
[Magisk] silvercat:
You should remove dual speaker module
[Magisk] Didgeridoohan:
Hm... I know for a fact [MENTION=4470081]topjohnwu[/MENTION] updated the root request que for v13.3 (and tested your app with it). And I've also tested it (Toggle Data 1.7.2.0, downloaded from your thread) on Magisk v13.3 (Manager 5.1.0) and it works perfectly (OnePlus 3T, OxygenOS 4.1.6).

MagiskSU won't log all the root requests, but it should work.
[Magisk] leoqaz12:
Failed to install Xposed Framework via Magisk Manager

First, Thanks for all developers, my HTC M9pw (TW) finally passed safetynet using Magisk v13.3 & Magisk Manager 5.1.0.

However, I can't download & install Xposed Framework (SDK23) via Magisk. Magisk Manager will crash after unzipping the downloaded file and cause install failure.

I've also tried to install unofficial systemless Xposed via TWRP. It can successfully install, but can't pass the safetynet after flashing it.

Thanks for helping^^
[Magisk] stewie2806:
To get Magisk to work for me:

[S7 G930F

Android 7.0

Ambasadii rom v18.0

tgp lite kernel v5.0.1]

•Download Magisk Unistaller, latest magisk 13.3 and magisk manager.

• Boot to recovery

• Flash the uninstaller

• Flash Magisk 13.3

• Wipe Delvik/cache

• Reboot and install the latest manager
[Magisk] Rom:
Same error but with an other magisk module (Greenify4magisk) @topjohnwu

After uninstall Magisk via the last zip uninstaller with TWRP and install Magisk 13.3 again, for me the second module installation stuck on the copied zip to the temp folder operation...
[Magisk] Didgeridoohan:
Of course not. Magisk can't hide Xposed... Disable it or uninstall to pass SafetyNet.

Edit: I posted a little something about his a few posts up.
[Magisk] Floydfire:
I think I found out what is the culprit for the manager don't working, after uninstall and reinstall I've noticed that with arise compatibility patch and/or busybox by osm0sis the app freeze. Removing those 2 fixed the app... So I'm guessing o can simply put the arise script in service.d and it'll work... The problem is busybox... Anyone knows a busybox magisk updated? Thanks.
[Magisk] mike.bss:
Updated to 13.3 and Magisk manager to 5.1. Still the Magisk manager is not opening!!!

--LG G5 H830

ANDROID 7.0

FULMICS ROM 3.3

MAGISK 13.3
[Magisk] SuperSandro2000:
Log Cat? OS Version? Phone? Something?
[Magisk] mike.bss:
Oh sorry forgot to provide info.

--LG G5 H830

ANDROID 7.0

FULMICS ROM 3.3

MAGISK 13.3
[Magisk] Rom:
So if i understand, we must uninstall the busibox framework and the compatibility patch right ?
[Magisk] Floydfire:
I don't know if they're both the cause of the issue if you want to try remove arise compatibility patch folder from magisk folder then reboot and try to open magisk.. of still doesn't work remove also the folder for busybox and reboot after that should work.. I didn't tested that way I've just removed both at the same time. For arise I think is enough to get the script in the folder and put it in the service.d folder in /magisk/.core and setting permissions 755. I've others module and the app works, I even pass safetynet l... So I guess the problem are the outdated modules...
[Magisk] cygery:
Thanks a lot for your tests :)

I'll try again with a clean reinstall and post my results.
[Magisk] Didgeridoohan:
[MENTION=4233428]Floydfire[/MENTION] [MENTION=5332893]Rom[/MENTION]

Easiest is to just downgrade to Manager 5.0.6 until there's an update (and there will be one).
[Magisk] Floydfire:
Yea thing is, as someone said the problem isn't with the manager itself but with the outdated modules at this point I think so maybe having updated modules is a better idea... I'll see later if I can make an updated module for arise (I think should be easy, maybe it's only the module.prop that cause issue so the fix can be easy..
[Magisk] Didgeridoohan:
Actually, it's probably a mix of the two...
[Magisk] Rom:
Hm hm ok i see, when i browse my magisk folder at ./ location, i have ".core .dap .EmojiOne-systemless (module) .lost+found" folders but no one busibox folder appear, or maybe this folder is located in other folder ? I don't know how busibox syntax and structure works on lasts Magisk releases.

About the Magisk modules compatibility, i think the same thing..

Heu ok but we cannot install manually an previous app version instead of the last or maybe this restriction was removed from Nougat..
[Magisk] Floydfire:
Ok so you don't have a busybox module, (magisk removed busybox since v12, I think) but it can be the dap module Which if I remember correctly is for Dolby atmos and also that wasn't update for latest template... Don't know about enojione if you don't want to remove any modules you can simply uninstall magisk manager and install 5.0.6 it'll work.
[Magisk] Didgeridoohan:
There's an easy solution to that... Uninstall 5.1.0 before installing 5.0.6. :laugh:
[Magisk] shadavis08:
Sounds like Magisk didn't install properly. I dont know where you started from and what youve done up to this point or haven't done. So I really can't say what the issue might be .

---------- Post added at 03:48 AM ---------- Previous post was at 03:40 AM ----------

You may need to start over with another full wipe and try again. Maybe something went wrong when you flashed pure nexus onto the tablet.

LG V20 h91810k WETA ROM XDA Premium
[Magisk] Complexityyz:
Magisk Manager Crashes when I enter su into a terminal.

Info: Nexus 6P Resurrection Remix 5.8.3 7.1.2 Magisk 13.3 & Magisk Manager 5.1.0 ElementalX kernel
[Magisk] 29988122:
Thank you for your replying - I understand the pain of answering questions, and I very appreciate all your efforts.

Now at least I have keywords to start with, which I didn't have before. Your post helped a lot.

Thank you!

P.S. sorry for the reply in your magisk hide thread, I was frustrated.
[Magisk] Rom:
Ah ok i understand..

Yep, Magisk modules devs would update their modules.. :good:

We have hear you we have hear you :highfive:;)

But after install several magisk modules........bootloop !! XD

So now i must flash the uninstaller, flash again last magisk zip, reboot, uninstall magisk manager app, install again the previous version and wait for an update from magisk modules devs ^^
[Magisk] Gerard15799:
Noob question... can I just leave magisk hide enable forever?
[Magisk] Einheit-101:
Xposed STILL causes bootloop and my phone only makes strange vibrations when pressing the power button.

Going back too Magisk 12, at least it worked. Android without xPosed is today almost as bad as an iPhone...
[Magisk] admicos:
So, I switched to Resurreciton Remix today, and now I can install Magisk modules (yay!)

It's either a compatibility issue with latest Lineage builds or I messed something up while I was on Lineage. Most likely the latter.
[Magisk] Didgeridoohan:
I'd say it's equally likely the former. I have no love for LOS... :p

Anyway, great to hear it works.
[Magisk] admicos:
Aaand i just found the reason why it doesn't work.

It was the iYTBP module.

It also caused the 2 TB magisk_merge.img issue.

So yeah. I'll also try to install that from recovery after doing a reinstall of Magisk.
[Magisk] CRYPTfromCATACOMBZ:
Hello folks, i have a little problem, can't update magisk manager. Have version 5.0.6, download via manager the latest one, but when i confirm update of app, it says "The package conflicts with an existing package by the same name"

How to solve it?

(Have Zenity RR rom)