yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
That means it's likely that there's something about the module corrupting the Magisk image. Great find! :good: I'll test it out myself and see if I can replicate.

---------- Post added at 12:46 ---------- Previous post was at 12:42 ----------

Ok... Let's get back to business and try to ignore all the "Manager is crashing" posts. It's under investigation and will be fixed eventually!

I'm gonna backtrack a little. You said that "0" in /data/user was a file, not a folder, right? That's a huge clue!

I've seen that as well when I've been playing around with creating symlinks in a couple of modules, where the the file would be reported as a symlink to a directory, but you can't follow it to the source either through cd in terminal or a file explorer. I have no idea why it happens... My limited knowledge doesn't stretch that far. :laugh:

But, considering this, the last solution (that you didn't try) probably will work!
[Magisk] :
First of all, could you give me the link to the zip download for 13.3? I am running Magisk 13.0 now because when I tried to flash 13.1 root was broken, and it was basically not working. Even if I let the app do it for me, download and install it, it still wouldn't ekrk.

ARM64 CPU (Kirin), 13.0 was installed fine
[Magisk] zatoshi:
I have the same problem T_T
[Magisk] otonieru:
Actually,

Any modules, even updated one,

Will prevent the magisk manager to start

I tried with only module with v4 template

Still the magisk manager wont start
[Magisk] d3nni:
Same. Updated to 13.3 and Magisk just freeze when I try to open it.

Phone info:

Note 4 (G910F)

Android: 6.0.1

Rom: Aurora Note 7 port v20
[Magisk] :
Managed to flash it. 13.1 wouldn't work but I downloaded 13.3 through the app and installed and it works fine. But ctsProfile doesn't pass safety net. What can I do ?
[Magisk] Didgeridoohan:
Awesome! That means everything is working as it should. You've got something about your setup causing Google to not trust your device though... CTS profile matching is done against Google's servers and if your device doesn't match - you fail.

Check here for a bunch of things to try: https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
[Magisk] dusman13:
Perfectly working.
[Magisk] ademasp:
Where I can download Magisk manager 5.0.6?
[Magisk] ForgottenDude:
I apologize for a noobish question, but does a Magisk update ever lead to battery drain?

Ever since I updated Magisk today, the battery has been draining even when idle. Battery stats show that phone has been awake even while it is idle, WiFi, bluetooth, etc turned off.

I updated by first updating the Manager app through the notification and then updated Magisk itself through the app. (The new Flash sequence is cool!)
[Magisk] demonoidmaster:
As if i didn't try this with the latest uninstaller, fact is actually before i flashed v13.3 after i downloaded it from the thread along with the uninstaller i ran the uninstaller first then reflashed Magisk, rebooted, Magisk app opened once.. Went to its settings, flipped the switch on dark mode, app then froze and wouldn't open

Cleared cache and app data, open, no go

Uninstalled, went back to 5.0.6, no issues

Once again, as i said, 5.1.0 is quite broken

---------- Post added at 12:19 PM ---------- Previous post was at 12:18 PM ----------

Download v13.2 from the OP, open the zip, go to common, apk is there (though version is 5.0.5)
[Magisk] Didgeridoohan:
Or... You could just download it from GitHub: https://github.com/topjohnwu/MagiskManager/releases
[Magisk] demonoidmaster:
Yeah because obviously i did something wrong flashing the uninstaller then v13.3 right? Then opening the app once, having it freeze and then never opening again no matter what i did be it wiping it's app data and cache, uninstalling via twrp, etc?

Nah i think i know what I'm doing, using any other Magisk Manager version and it works fine asf, therefore it's some apk build issue, not an issue with my device or rom or magisk install or modules. I'm not some noob that's got no knowledge about Android and etc
[Magisk] shadavis08:
I'm curious did you update through the Magisk manager ? That's how I updated it myself with no issues. It first installed 13.3 then after a reboot said there was an update for manager and proceeded to up date. While everything went fine for me I never tried to install any modules either, as I don't need any. I'm just wondering if there is an issue with the zip download verses updating through Magisk?
[Magisk] beastobadness:
I am having the same issues as the above folks in that magisk 13.3 works with any other previous version of magisk manager apart from 5.1.0. It freezes on the flash screen, it seems that SU requests still seem to work.

Is there any way that a log can be taken from the magisk manager root file system without entering the app itself or via a third party app?
[Magisk] Artim_96:
Apkmirror, xda Labs...
[Magisk] n4m3less:
I have a same issues!magisk manager 5.1.0 not work (aftet update magisk to 13.3) but previous version works!
[Magisk] demonoidmaster:
So i decided to simply flash everything from scratch (rom + opengapps + debloat zip + jrummy busybox zip + magisk v13.3 + elementalx in that order without flashing any of the previous modules I've been using) since some guys on github was sayin it must be module related

Rebooted, Magisk installed but just to be sure i installed the 5.1.0 apk from his github, opened it and it works even after closing and reopening it
[Magisk] jenslody:
It's definitely not [MENTION=4544860]osm0sis[/MENTION]' busybox !.26.2), at least it works fine here on my J5.

Other modules I have installed: F-Droid Provileged Extension, Unified Hosts Adblock and Xposed Framework (SDK23).

SafetNet passes if Xposed is deactivated.

No problems with hanging Manager etc.

Expect the module installation issues described earlier by me.
[Magisk] demonoidmaster:
Alright so flashed these

• ART Optimization 1.4.1 \ √ ok

• Enable Doze for GMS v4 \ √ ok

• Emoji One 1.3 \ ∅ nope.jpg

Therefore once i flashed it it said success at the bottom of the verbose screen in Magisk, tried pressing reboot, nada, close? Nada. Force closed the app and tried opening it, nada

So Emoji One causes issues on 5.1.0 apk but not on 5.0.6 or prior apks

Tagging [MENTION=5479482]jerbear294[/MENTION]
[Magisk] el.musthofa:
Back to 5.0.6.

5.1.0 not working for my phone
[Magisk] streetsurfer:
Is there a compatible busybox to be systemless?
[Magisk] jenslody:
How did you install ?

It does not work for me through Manager, but through TWRP and with wiping Dalvik/Art-cache after installation.

---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------

Any chance you have installed an unofficial version before?

In any case, try to remove the old version before installing the new one.
[Magisk] Floydfire:
Ok thanks, I'm going to try now if it gives me issues (I'm on oneplus 3 with open beta 19)

Edit: ok, busybox by osm0sis works with the latest magisk, so it was arise for me that "broke" manager
[Magisk] Ricky17:
Magisk manager does not respond. Tried reinstalling. Didn't work.
[Magisk] mrps2:
Same thing here! After installation of the upgrade Magisk does not open, close or respond.

Ver. 5.0 works fine.
[Magisk] otonieru:
Am reverting to 13.2

13.3 with 5.1 manager simply wont work,,

Even with updated module,

It still stuck when opening.

And magisk hide wont even work either.

Tried clean install, but its the same

I guess, i'll wait until 13.4 or 5.1.1 or something,

Or until there's clear detail about the issue,

I think its module related indeed, but it also happening on module that already updated to v4 :silly:
[Magisk] SOCOM-HERO:
I'm having the same kind of issue with the 5.1. Used the uninstaller zip and rolled back to 13.2/5.0.5 because I couldn't install any versions once 5.1 was installed. It reset all my mods, but I got most of them back through the install process. Hope a fix comes down soon. Thanks for the amazing development on this mod!
[Magisk] Didgeridoohan:
There's also the option of using Magisk v13.3 with version 5.0.6 of the Manager...
[Magisk] tanago:
none of 13.* versions are working for me, I posted logs for every release and everytime no errors during flashing, magisk is not installed, root is not present, sony ric is confirmed disabled....

13.3 is the same
[Magisk] 314mp:
10 was for 13.2 we have to wait for [MENTION=2461994]goodwin_c[/MENTION] to update the pixel version, or follow one of the tutorials for patching version 10.
[Magisk] otonieru:
Tried that mate, thx for the suggestion,

But with that combination, my SN wont pass

Now am on 13.2 with the resetprop fix
[Magisk] danilo_scala:
please how i get logcat? stranger i try install (flash) in recovery magisk 12 work , but magisk 13x no work , show not installed , no rooted, only show app isnstalled.
[Magisk] Rom:
You can use this app :good:

https://play.google.com/store/apps/details?id=com.nolanlawson.logcat&hl=fr
[Magisk] Didgeridoohan:
Not every device is compatible, unfortunately. Sounds like you have a compatibility issue and in that case your best bet is to post details, logs and a copy of your boot image to a relevant issue on GitHub (or open a new one if there isn't one already). Like [MENTION=4470081]topjohnwu[/MENTION] says: No boot image, no fix.

Ah, yes... The ever present SafetyNet... Honestly, I'm getting a bit sick of it. :D
[Magisk] shadavis08:
I would just delete manager 5.1 and install the 5.0.6 manager . try that .

I wonder if you guys are using the Magisk uninstaller that's supposed to be used before flashing the magisk zips or when have issues .
[Magisk] otonieru:
Yes, done that. I even fully uninstall magisk,

Remove any magisk leftover from /data/data and data/app

Install 13.3 , uninstall 5.1 and install 5.0.6

Module work, SN not

I kinda hate google for all this SN stuff
[Magisk] goodwin_c:
I have uploaded new v13.3 to my AFH - should bypass SN.
[Magisk] chjun90:
module.prop missing a blank line at last cause the stucking bug. Add a blank line in module.prop of every modules will fix the bug:fingers-crossed:
[Magisk] moore.bryan:
Sadly, it is an issue, as Magisk Hide fails to hide root from apps because root is detected. :(

First thing I did. ;)

After several wipes, I think I've discovered the culprit: TWRP.

After a complete wipe and flashing stock--the one from Google themselves--I flashed nothing but the latest TWRP (3.1.1-0) for the manta and then checked TWRP's own file manager. Low and behold, there's SuperSu in root--i.e., a folder named /supersu--containing the following files: 99SuperSUDaemon, chattr.pie, install-recovery.sh, install-supersu.sh, libsupol.so, su, Superuser.apk, and supolicy. Why in the world would TWRP be rooting my manta?

Thanks for all the help/suggestions!
[Magisk] tag68:
Please ignore this. It is only existing while TWRP is running. If you decide when starting/exiting TWRP that you want to install super su, it is copying from /supersu which is probably mount bind via some data from TWRP. Your problem has nothing to do with /supersu. At least not directly, if you let TWRP root your mobile using SuperSU when being asked despite trying to install Magisk, you do something wrong ;)
[Magisk] prisoner1969:
Magisk manager 5.1.0 freezing up on start. Reverted back to 5.0.6 worked for me.

---------- Post added at 02:28 PM ---------- Previous post was at 02:24 PM ----------

Went and tried this and that fixed the issue with 5.1.0
[Magisk] moore.bryan:
So, apps don't look for a folder named "supersu" in root to see if a device is rooted?
[Magisk] xRedDroidx:
Updated the Magisk app but i still can't update Magisk to 13.3 just like 13.2 it says installation error after i try to update, i tried updating in recovery too but same error. It says boot image patched by other programs and to restore stock boot image, so it means i have to flash my rom again?
[Magisk] otonieru:
WTF ? For real ?

So just another line at the end of the field ? Thats it ?

---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------

You only need to flash the stock kernel. Or any custom kernel, then flash magisk
[Magisk] Floydfire:
Wait what? How it could even be possible? D: I'm going to try it myself (I'm not saying that you're a liar I'm just speechless... How did you find out?)

Edit: wth it actually worked O.o
[Magisk] tag68:
Seems you did not understand. /supersu only exists while you're running TWRP. When booting the device it disappears. If some app looks for /supersu, it won't find it ...
[Magisk] chjun90:
I met the stucking bug. So i uninstall and reflash the magisk.then i want to install my modules back by magisk manager. but there are some modules i installed will cause stucking. then i go to root explorer and found those module.prop file all missing a blank line at last. Add one and the bug fixed.;)
[Magisk] Floydfire:
I did the same except I didn't thought that a line could fix the issue xD in fact I've just placed the script of arise module in service.d but now I can simply use that trick. Thanks man, that's a nice find you did... Still can't believe it xD
[Magisk] shadavis08:
You should tell magisk op about that
[Magisk] chazarss:
i cant belive but it fixed :eek:
[Magisk] crumble6:
Doesn't work with my arise module, it already has the blank line. :(
[Magisk] moore.bryan:
So, here are my steps:

Flash back to stock.

Enter stock install once.

Flash TWRP via fastboot and reboot TWRP once.

Flash PureNexus and boot into it once.

Flash Slimgapps and boot into PureNexus.

Install PS Vue Mobile and launch it; the app complains about not supporting rooted devices.

Enter TWRP and flash Magisk.

Boot into PureNexus, clear cache & data for PS Vue Mobile, launch Magisk Manager, select PS Vue Mobile for Magisk Hide.

Launch PS Vue Mobile and it still thinks I'm rooted.

So, to summarize, PS Vue Mobile thinks I'm rooted regardless of if I root or not. Huh?
[Magisk] xRedDroidx:
Lol it was that easy thanks dude it works now , Safetynet too i can play Fire Emblem again now :good:
[Magisk] PFusion:
Will Magisk 13.3 work on a Google Pixel? I have Pure Nexus installed with ElementalX kernel.

If it won't work is there anyway to get it working?
[Magisk] teddy0209:
It works, just tried the app for you... Force stop the app, and clear data...
[Magisk] langithitam:
Thanks [MENTION=3615867]teddy0209[/MENTION]! I'll try it :)
[Magisk] deepu458:
No Buddy, i just edited the ARISE+Magnum+Opus+20170718.zip with that addition line in the module.prop file and boom its working gr8 with Magisk Manager 5.1.0 and Magisk 13.3V.

Thanks Buddy, for finding it out. For me on Bacon with RR this Trick has worked for me.
[Magisk] dastinger:
I'm sorry for only getting back to you today but had a super busy few weeks. Just to let you know that it worked, thank you so much! I can now install modules and Android Pay works.
[Magisk] otonieru:
Damn it,

Cant believe that it was that simple,

You better tell [MENTION=4470081]topjohnwu[/MENTION] about this,

Since this is definitely doesnt worth the trouble, LoL

Meanwhile, i'll update all my module to have an extra blank line
[Magisk] satfan:
i need your urgent help please!!

i had a freeze at starting magisk manager in the splash screen, then i red that this seemed to be the solution for not starting:

Download the latest Magisk Uninstaller

Flash it via TWRP

Try installing the Magisk v13.3 on your device

Reboot your phone and install Magisk 5.1.0

Install the application and open it

You will find it is working fine now

After i uninstalled MAGISK with the zip everything worked, but right after that i tried to Flash v13.3 and there was an Error in TWRP.

i just rebootet an the s8 doesnt start anymore!!!

i am Stucking in the download Modus, i can get to the Menu where volume upbrings you to the flashing menü and volume down restarts phone!

WHAT TO Do now?? Please help, should i flash the Firmware again to start the Phone? Please help accu is draining at the Moment!

PLEASE!!!

SOLUTION

So here is the solution for those of us with a S8 and the same Problem, Flashing the Firmware Base: G950FXXU1AQF7 with Odin i got to TWRP again and could restore my original Image, later i found out that also just flashing the originaly boot File also would have helped, but from my Point of you there are here no clear instructions how to uninstall MAGISK and install again, because the developer just mentioned to Flash in a side Sentence, for an internediate hard to find out if you dont read exactly!
[Magisk] moore.bryan:
Tried that. ?
[Magisk] otonieru:
Super thanks to this big hero [MENTION=5748727]chjun90[/MENTION]

Now 13.3 and 5.1.0 work fine with all my modules :highfive:

I think someone or a mod need to make advisory to all module creator to check their module.prop for that extra blank line
[Magisk] prisoner1969:
deleted
[Magisk] saccentekennedy:
I can confirm this works! The module.prop for deep buffer remover didn't have a blank line. I edited it. MagiskManager 5.1.0 now working with no problems! Amazeballs.
[Magisk] shadavis08:
You tried a different ROM
[Magisk] ju1da:
i passed my SN with that combination about 10 hours ago after several trying errors. I did also clear all data of playservice and playstore + reboot.

Now, it remains pass the SN.
[Magisk] satfan:
Aeh sorry which post im pretty nervous at the Moment... ??

THX
[Magisk] WyldOne91:
I just flashed your updated file for my Pixel XL and Magisk ces back saying it's not rooted and that Magisk isn't installed. I installed it 3 times. If I check immediately after it boots it's there, but then if I check again a couple minutes after it says nothing is installed.
[Magisk] lahceneamine:
All the "Template v4" have this extra line already.

I had only one module "Template v3" which didn't have this extra line, added it and everything works.

I guess the devs should update their modules to V4 in order to get rid of this bug.
[Magisk] Einheit-101:
I tried installing with manager, now I reverted to magisk 12 and its very fine, srsly i dont want to try again now, because I am 100% sure updating magisk to 13.x will bootloop again.
[Magisk] boxguy1:
No matter what magisk manger version I use I cant access the super user tab the app just force closes
[Magisk] teddy0209:
Then it must be detecting something else from your setup...
[Magisk] sirwin44:
anyone got any ideas? is it possible that i have to obtain a custom boot img?
[Magisk] KnightUK:
Magisk Manager 5.1.0 wont open for me at all on Fulmics7.6 rom for the LG G3, ive installed the v13.3 via recovery as it gave an error in the manager, rebooted and installed the latest manager as it told me to - now it just hangs at the Magisk splash screen and force closes after a period of time - im not sure where to go and what i should do here - keep seeing people mention module.prop but where do i find that - This is a fresh install of Fulmics 7.6 on my G3 nothing else installed.
[Magisk] otonieru:
Think is,

the difference between module prop v3 and v4, aside from the extra line, is only that the template number change from 3 to 4, most of us will overseeing that blank line in a normal situation

So, for dev who is away from PC like me, would update the module from our phone using archiver app by simply update the template value and update the new common and meta-inf folder, instead of replacing the whole module.prop file, since this way also works in the past,

But i guess, starting from now on, i need to be more cautious when updating my module
[Magisk] lahceneamine:
Just in case, I meant no offense to any dev :)
[Magisk] whalesplaho:
happy it works for yhu.....:victory::victory:
[Magisk] RedAntares20:
Guys I have a problem stupid but I want to report it.

Then it happens that in the V12 every day I had to revive the phone because it did not read the root, and I read it, but with the v13 i happened to me 2/3 times.

Is it my problem or even all of them?
[Magisk] Pvcabr:
The uninstall.zip removed them. No Problems
[Magisk] sdugoten:
I have the exact same problem on Xperia X Performance. Hang at splash screen. Developer please help.
[Magisk] dryness:
So, I completely uninstalled Magisk and Manager before doing anything. I deleted the existing /data/user/0, and created the symlink. I was able to navigate to /data/user/0 and /data/data through TWRP terminal, and both brought me to the same location (I didn't think to see where it led before deleting the existing entry, oops). I then installed Magisk 13.3 and Manager 5.1, and attempted to gain su once more. Unfortuantely, there is no change. :(

The magisksu_log still reports not being able to access the .db files.

I also (accidentally) went back to MagiskManager 4.3.3 (when the intent was 5.0.6) with Magisk 13.3 still installed, and was able to at least get root access - though Magisk Manager died immediately after I granted permission. And root did work - I was able to navigate to the databases directory successfully:

ailsa_ii:/ # ls -l /data/user/0/com.topjohnwu.magisk/databases
ls -l /data/user/0/com.topjohnwu.magisk/databases
total 144
-rw-rw---- 1 u0_a178 u0_a178 20480 2017-07-19 12:02 repo.db
-rw-rw---- 1 u0_a178 u0_a178 20480 2017-07-19 12:02 su.db
-rw-rw---- 1 u0_a178 u0_a178 32768 2017-07-19 12:17 su.db-shm
-rw-rw---- 1 u0_a178 u0_a178 0 2017-07-19 12:02 su.db-wal

The permission was not saved, and using su required me to re-grant permissions (despite being "forever") I've attached the magisksu_log_4.3.3 for that as well. But it appears that 4.3.3 granted su permission before writing to the database file, whereas 5.x writes to the db first before prompting. That doesn't change the fact that the app crashes, it only changes when it happens. So perhaps this is just muddling the waters.

I'll update the github issue with these results shortly.

Thanks again for taking the time to help.
[Magisk] theandroidguy:
Why safetynet is failing??????
[Magisk] sdugoten:
I wonder where to find module.prop in the file system?
[Magisk] teddy0209:
It's under /magisk/modulesfolder...
[Magisk] lover:
in /magisk/(module name)/module.prop

i would wait for a fix, for now reverting back to 5.0.6 will solve it
[Magisk] 2WildFirE:
No problem here
[Magisk] holozis_HUN:
Anyone?
[Magisk] DallasBelt:
Download the module through Magisk, then flash it with TWRP. It should work.
[Magisk] Istvan_86:
Really thanks for answer me, after the release of 13.3 I give it a new try on my Pixel C but now it´s even worst, not only the bootloop into TWRP it´s still here, now even if I flash the uuninstaller I never con go back to system, always bootlooping in TWRP.

About upload my boot image on GitHub I´m a bit confussed with that but if anyone can explain or point me where on GitHub I must upload my boot img, maybe I can do it without troubles.

Thanks again.
[Magisk] teddy0209:
For the v4a app, you need to download and install it seperately... Look at the modules description under download...
[Magisk] PraneethMv:
Updated the Magisk Manager to v5.1.0 through the existing manager itself(5.0.6). Freezes at the splash screen. Uninstalled Magisk through the latest uninstaller and flashed the Magisk v13.3 through twrp. Now, everything is working good, and guess what, SafetyNet also seems to have no problem. Yay! ( Although cts profile does show its false). :laugh::)
[Magisk] ForgottenDude:
Install apk from here.

https://www.androidfilehost.com/?fid=312978532265364193
[Magisk] wntjq69:
This is wierd.. 13.1 to 13.3 update fail

My rom is touchwiz based 6.0.1 custom rom.

And installer says it's only for 5.0+

No image cause this is my first post and imgur link is getting blocked.
[Magisk] theandroidguy:
But mine is failing
[Magisk] slssdhs:
thank you! I did what you said and it works for me, it's the issue of "host adblock":good::)
[Magisk] Didgeridoohan:
Reflash your ROM's boot image or dirty flash your ROM. That should do it...

No worries.

Did you try deleting and recreating the symlink while booted into the OS or only in TWRP? It probably gets reset on boot...

Edit: just so there are no mix-ups... Please make sure you have a backup before doing stuff like this... :laugh:

This is where you create GitHub issues: https://github.com/topjohnwu/Magisk/issues
[Magisk] term-x:
Same issue on Resurrection Remix on OP3