yashsingh1/xdaforums huggingface dataset:
[Magisk] knpk13:
-_- answered multiple times

Just flash the last zip available (confirm that the thread title matches the build title). Magisk manager us included in the zip.
[Magisk] jt1998:
Use latest one, labeled in the title of the thread. Magisk manager installed when you flash the installation zip.
[Magisk] ThisWasATriumph:
Using Magisk Hide to hide Google Play Store and Play Services fixed this for me.
[Magisk] AravindhStanley:
I still couldn't pass safety net for some reason when Dolby Atmos rc6.5 c is installed as magisk module. I only use 3 modules, youtube background playback and audio modification library and atmos. Safety net passes with the first two but fails when I install atmos. I tried hiding the Playstore and Play services, but still in red. Help would be appreciated. Thank you.
[Magisk] sumitarora2:
I have latest v13 Magisk and safetynet check says the response is invalid ,please help
[Magisk] RafaBronX®:
Kinda off topic, but could someone explain me how to switch from SuperSU to Magisk? I've been trying to do that but I'm having some difficulties... :crying:
[Magisk] Link_of_Hyrule:
You don't need superSU any more completely uninstall it the app and make sure your rom is stock and flash the latest Magisk beta that'll install root and the Magisk Manager which includes super user.
[Magisk] Shen Ron:
Tried again to install after uninstalling v12 and same error but this time i flashed the mount magisk zip and it wotked but it still said that magisk wasn't installed when i checked in the app.
[Magisk] RafaBronX®:
The problem is that I'm using a rooted custom rom (BrokenOS) on my device, so I'm trying to get rid of SuperSu in order to use Magisk as my root manager. Can you help me into this quest? :fingers-crossed:
[Magisk] shad876:
So uh..guys what does this mean :confused:
[Magisk] shad876:
Nexus 5

AOSP 7.1.2

Blu spark kernel
[Magisk] Shen Ron:
It just means you can use magisk and all its glory and pass very simply safetynet detection for most apps that only looks at your device basic safetynet protection level
[Magisk] paed808:
turn magisk hide off and on and try again.
[Magisk] shad876:
Thanks but no effect..
[Magisk] Link_of_Hyrule:
The installer should remove supersu I'm pretty sure if not there's an unsu zip around on xda although I don't have a link to it sadly.
[Magisk] Nevermindthelabel:
I've got almost the same setup (OP3 and OB18 with Blu Spark) and everything is passing. Only thing I did differently was flash from 17 to 18, magisk and then kernel. Hope that helps. Passing with a few modules installed
[Magisk] crankiro97:
Ok, I wanted to flash Xtrememusic but I don't if it will trip safetynet on Magisk..
[Magisk] LazerL0rd:
I meant ARISE is FULL of useless libs that do nothing. Obviously some do work. But you can't just copy and paste love between devices.
[Magisk] sumitarora2:
I have latest v13 Magisk and safetynet check says the response is invalid ,i am using lineage os 14.1 (7.1.1 nougat) and my device is Samsung galaxy core prime ( sm-g360h ) and magisk manager version is 5.0.2
[Magisk] LazerL0rd:
It breaks with [MENTION=421177]ahiro[/MENTION]n viper stuff.
[Magisk] m_reyna_16:
Guys, I just flashed the latest beta and my snapchat nor my Gmail works... When I press on them all they do is "animate /flash" as if it is going to open and does nothing

Gmail works after activating core only mode and I'm sure snapchat also because it asks me for my login now, but of course I can't prove it works bc it detects root and doesn't let me login

Anybody know a solution or is this a known problem?
[Magisk] LazerL0rd:
I need viper for a convolver.
[Magisk] counterfeit187:
I have op3t and oos beta 9 also but I pass. It maybe the kernel?
[Magisk] MrBrady:
+1 glad to see I'm not the only one with Gmail issues. Works fine in Magisk 12. Nexus 6 running Dirty Unicorns.
[Magisk] Gerard15799:
I have an Asus Zenfone 2 laser running with RR 5.8.3..I flash the beta version and got this result for safety net. Attach here is also the log
[Magisk] iPusak Gaoq™:
Fully unroot SuperSu inside SuperSu apps itself then on extract boot.img from BrokenOS zip files and flash the boot.img in recovery before you flash Magisk...flashing boot.img is important because once you have flash SuperSU, it will modified boot.img so you need unmodified boot.img before you can flash Magisk...
[Magisk] sofir786:
It took my s6 g920f 40 minutes to finish the whole install process on the latest magisk beta build.
[Magisk] laupuy:
Hi,

You must flash rom, root then kernel in that order.

All is good here OP3, OpenBeta 18, Magisk v13(96f8efc) and latest blu_spark ;)
[Magisk] y11ohan:
Well I thought the video would be helpful to understand a little more. In this day and age, if every information is obsolete after a day, I am not meant to live in this world and be able to share what I want?
[Magisk] mikevb:
Stock Nexus 6, 7.1.1 (Build NBD92G)

Only passing SafetyNet without installing any modules (through Downloads tab in Magisk Manager). Installing a module (only tested Nexus 6 LED Enabler) makes both tests fail.
[Magisk] jenslody:
Sorry for not posting this, here it comes:

SM-J500FN (2015 I guess) with TWRP 3.1.1-0.

Latest stock (MM 6.0.1) J500FNXXS1BQD1 (DBT).

Most google and samsung stuff removed, but I guess that should not make a difference while flashing.

I reflashed the stock boot.img before flashing magisk, but the error was the same.
[Magisk] paed808:
There's no need to set permissive for Viper4Arise or Viper4Android.

Download this script https://pastebin.com/raw/YnEF5Utq , name it 50viper, put it in /system/etc/init.d , chmod it 755 , download universal init.d by "androguide.fr" from Google Play store

Then grant universal init.d root access and reboot

Boom. Viper works in SELinux enforcing mode
[Magisk] kongha:
Latest beta works well.. Moto x pure linageos 14.1

Thank you
[Magisk] revanmj:
FK Manager for Franco Kernels seems to have a problem with Magisk 13 - it gets root permissions but Kernel Settings screen or CPU Manager take long time to load. (before those panels were loaded instantly after opening them). They were working fine with Magisk 12 just few days ago (only Magisk version changed, Android, kernel and FK Managers versions are the same).

magisksu_log.txt is in the attachment, but I was unable to get "magisk_debug.txt" file as ADB returned an error when trying to get it:

remote object '/data/magisk_debug.txt' does not exist
[Magisk] Gerard15799:
Here is another results and log when I flash back my rom(clean flash) and I hide system ui....I dunno why basic integrity pass but not cts....
[Magisk] prathu30:
Safteynet works just fine but some Google apps are force closing
[Magisk] :
Guys. What do I have to do to.get BusyBox now?
[Magisk] dahawthorne:
I know that this is a one-liner and many people will not notice it, but there may be a few who are misled, so I'm adding this comment.

You have this back to front. Magisk (& SuperSU) works on the kernel/boot, so by flashing the kernel after rooting, you overwrite the root tweaks.

The correct order is ROM, kernel(boot), root.
[Magisk] MorpheusKiller:
Magisk-v13.0(96f8efc) not installing

Hi,

i get ERROR: 1 when trying to install latest Magisk-v13.0(96f8efc). installing Magisk-v13.0(a90e8b6) is working.

S7 Edge latest MM G935FXXU1BPLB build.
[Magisk] Choobilsky:
Same here; Axon 7 running RR
[Magisk] nathanchance:
I'm not pointing fingers at all, this is just a general message for threads like this.

People helping:

You really don't have to reply to every post. If you don't know the answer or the post isn't formatted/done properly, you can just ignore it and move on, the world will not end and nobody will judge you for ignoring the post. If you do decide to comment on it, assume they have no idea how things work here. Kindly explain they should search for their issue or use a service like Hastebin or Gist for logs. People are more likely to be open to suggestions that change behavior when it seems helpful rather than abrasive. [MENTION=4667597]Didgeridoohan[/MENTION] has always done a fantastic job of this in the Magisk forums.

People wanting help:

Please put some effort forward. Nobody wants to hoist you up with their own strength, you have to give some yourself to compensate. Search, read the OP, read the past few pages to see what the current conversation is. If there are multiple posts with your issue, either thank the post or just don't respond at all, a massive flood of posts on one topic makes it hard for people without that issue to receive help.

XDA is a wonderful place because of the people in it sharing this great hobby, let's not ruin it with semantics and attitudes :good:
[Magisk] alessio89g:
Has been removed Busybox in latest Magisk Beta (v13.0 96f8efc)?

I can't see it in its settings and if i try to type "busybox" in a terminal app I get a "not found" message.

I run Dirty Unicorns Nougat in a Nexus 5.
[Magisk] nathanchance:
System-wide Busybox has been removed in Magisk v13 due to various incompatibilities (it's still internally available for Magisk Manager functions). [MENTION=4544860]osm0sis[/MENTION]'s Busybox in his fantastic Odds and Ends thread is Magisk compatible and works like a charm.
[Magisk] muralidharpattar7:
No busy box with this package? How to install manually?
[Magisk] nathanchance:
Kind of ironic: https://xdaforums.com/showthread.php?p=72703821
[Magisk] alessio89g:
Thanks! :D

I can flash it via Magisk Manager, or I need to flash it via TWRP?
[Magisk] nathanchance:
Flash it in TWRP as it doesn't use the Magisk module format, given it supports Magisk, SuperSU, or standalone installation.
[Magisk] SacredDeviL666:
could either of you link me to the viper which you are referring for me to try and see if it gives same result as yours
[Magisk] Skittles9823:
With that busybox, is it possible to hide it from rootbeer?
[Magisk] nathanchance:
I don't know what that is but further questions regarding his Busybox should be directed to his thread, not here.
[Magisk] Skittles9823:
Okay. Sorry about that.
[Magisk] Zeghio:
Hello guys I'm having some troubles with Magisk. The last version seems to work okay: Root Works and Safety Net works too. The problem is that every time I try to install a module it gives me error all the time. I tried to reinstalled Magisk again but I still have the same problem. Also when I check the apps that have supersu access, Magisk manager says that I dont have any app using root.... Still the apps works correctly.

Im guessing its bug or something of Magisk Manager. Any clue?
[Magisk] jenslody:
There are many people having trouble to install latest magisk.

Error 1 in when trying to flash.

I merged a slightly modified update-binary and boot_flash.sh from b3da28e into 96f8efc and uploaded it to my server.

The modification is to workaround an issue if a 64-bit system is incorrectly detected if /system/lib64-folder exists and no 32-bit library searchpaths are set.

I did not test it on a "real" 64-bit system.

No warranty for anything as ususal.

https://rpm.jenslody.de/download/Magisk-v13.0(96f8efc).v2.zip

My server is currently down, due to technical problems of my hoster.

I attach a version of my modified zip, which also includes the fix of @tdunham for very slow loading (see: https://xdaforums.com/showpost.php?p=72730850&postcount=1425 ).

Better fix with actual update-binary (including the slow install fix), found by @Deic,see https://xdaforums.com/showpost.php?p=72734788&postcount=14

and use zip created by @Nodens from https://xdaforums.com/showpost.php?p=72734887&postcount=15
[Magisk] garthybarthy:
Hi,

I'm having trouble flashing the latest beta magisk files via twrp. It keeps getting stuck on constructing environment? I've tried flashing over v12 and using the uninstaller and doing a clean install also but neither works.

I own a Samsung S6 Flat, running Noble ROM V4.

Thanks.
[Magisk] sofir786:
It will install but for some reason takes a really long time, it took 45 minutes or so for it to install on mine, No idea why.
[Magisk] Doctor Zoidberg:
Have one question...

After install magisk v13 volte works but i have no icon.

Flash magisk 12 then i have a volte icon.

Anyone have the same problem ?
[Magisk] edzamber:
Same here.

[MENTION=4470081]topjohnwu[/MENTION]

Here is a log about 1 hour installation

https://xdaforums.com/showthread.php?p=72700087

Nothing special, only that install took 6629 seconds...
[Magisk] Wolfcity:
And even if half of the libraries are useless (I don't think so but I'm not a coder) the sound is awesome, I heard nothing better. Maybe it's bad coded but what counts for me is: SOUND. As long it causes no problems on my device (and it doesn't) and offers me such a great sound performance everything is ok by me.

And sorry for offtopic but It was a matter for me.
[Magisk] Pa-Jo:
On my Xiaomi Mi5s Plus after installation of Magisk v13 (96....) the Magisk Hide run into loop, it keeps unmounting and mounting every sec. I have no additionals modules installed and I can't pass SN and also gets integrity fail. Magisk can't hide root too. I'm running latest MIUI eu ROM on my device.
[Magisk] Tesla:
Anyone having trouble flashing the latest beta magisk and getting it to work correctly via twrp on Samsung phones?

Or is it working just fine?

I have hade some problems with previous betas on my Note 4 SM-N910F and wan't to know b4 flashing.

Please quote this in your answer.

//Tesla
[Magisk] CrEaTiiOn_187:
Flashed it on top of Magisk V12 wiped cache/dalvik and works just fine for me. I'm on S7 Edge.
[Magisk] android_htc:
This installs okay on my Samsung Galaxy Note 4 (32 bit) and passes SN. Thanks. [MENTION=4901223]Tesla[/MENTION] try this version
[Magisk] wrongway213:
Is that why we have such detailed auditing instructions - to show people, prove to them how much our stuff doesn't work?

Ah, ARISE would offer you that option without tripping SafetyNet.

So.. are you here for anything helpful, or just to make it a point to degrade the work of other members, when you have none to offer of your own to show how you'd improve it as opposed to just talking badly about our work?

[MENTION=7836278]LazerL0rd[/MENTION], this is simply bad form in a thread about Magisk. If you have an issue with our project, come to us - topjohnwu's hard work is not the place to air your personal issues with our work and advertise your opinion of it to all his users. Don't get me wrong - there's no place on XDA that's appropriate to just talk down the work of others just to do it. But a totally unrelated thread from another developer.. that's extremely rude. So please, come to us somewhere that you're not hijacking someone else's work to tell people how jealous you are more people use our mod than the one you're shamelessly trying to peddle by talking us down. We will be there, waiting, to discuss it with you - please do keep your grudge out of other threads and exercise some respect. Thanks :good:
[Magisk] laupuy:
Hi,

for stock kernel OK cause the root (supersu or magisk) will patch stock boot.img but in this case it's custom kernel aka blu_spark ;)

So: flash Rom (or stock kernel aka boot.img), Root then Custom Kernel

"Warning: If you come from other kernel or have any issues, you should dirty flash your ROM before flashing blu_spark zip to avoid problems.

Reflash ROM -> if you want root flash SuperSU or Magisk (default, no plugins) -> flash blu_spark."

source: https://xdaforums.com/oneplus-3/oneplus-3--3t-cross-device-development/kernel-t3404970

sorry for OT
[Magisk] HungLy:
I dont know if Xtrememusic would trip SafetyNet, sorry cant help you with that, but i can confirm Arise Sound Systems+V4Arise+Dolby Atmos passes it using Magisk v13.0 (a90e8b6) on OnePlus 3T OOS 4.1.5
[Magisk] chaostrodamis:
This might help. Flash it before you flash Magisk. It will remove other su methods.
[Magisk] HungLy:
Thank you [MENTION=4549135]paed808[/MENTION] !!

Didnt know about this and it worked as you suggested. :highfive:
[Magisk] atarek:
v13 Feedback

Hello All,

I want first of all to thank magisk project developers and contributors for there great effort.

I will list below my experience with magisk v13 it might be helpfull for anyone .

Brief history and info:

Mobile: samsung galaxy note 3 n9005.

Rom: nxteam-darklord-s7e-reborn

Kernel: phantom 1.2k-dev

Recovery: twrp materialized 2.8.7.0

I was using magisk v12 and manager v 3.4.4

Modules was working through manager.

Safety net was passing and magisk hide was working flawlessly

until google update so i decided to move for beta versions.

Below results for testing versions "b3da28e" "a90e8b6" "96f8efc"

"96f8efc"

Flashing in recovery through below error and this is full recovery log (View attachment 96f8efc_recovery.txt)

! Magisk image mount failed...
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/Software/Root/Magisk/Magisk-v13.0(96f8efc).zip'
Error flashing zip '/external_sd/Software/Root/Magisk/Magisk-v13.0(96f8efc).zip'

"a90e8b6"

there is no issues appears during flashing but after reboot magisk manager show that magisk is not installed as attatched screenshot also i posted recovery log and screenshot.(to whom interested in deep investigation).

special thanks for [MENTION=4929906]cafe-creme[/MENTION] for his support cause he figured a way posted here to use this version but it seems there is inconsistent bug in this version cause we have same device and kernel just diff. in ROM. this is beta software testing fun :)

"b3da28e"

thanks to [MENTION=3502310]kramer04[/MENTION] who pointed me to try this version i knew that it was released before google update and will not fix safety net & module detection issue but i gave it a try cause i want to achieve any success scenario with V.13.

it worked with no issues after flash in recovery it tested dirty and clean flash both worked. attached screenshots.

of course i'm not installing any module cause it will fail.

General notes:

Magisk manager is not installed automatically after flashing b3da28e or a90e8b6 in recovery.

Magisk manager v.5.0.2 log is always empty with magisk v.13 "b3da28e" .

If any one interested in any more info i could provide.

I'll appreciate any clarification regarding above general notes.

View attachment a90e8b6_recovery.txt
[Magisk] Windforce0511:
For Galaxy S6 users

Flashing latest beta through recovery took about one hour and twenty minutes to install. Now I have tried to flash new beta using Magisk Manager app and installation took about few seconds! Everything works great, including Safety net! :highfive:
[Magisk] dahawthorne:
Thanks for replying, but I'm still not clear. I see the comment that you mean ("Reflash ROM -> if you want root flash SuperSU or Magisk (default, no plugins) -> flash blu_spark."), and I've taken the liberty of engaging the dev [MENTION=3873953]eng.stk[/MENTION] in this reply - I hope that this isn't a breach of protocol, but as you probably gather my interest is in having clarity so that people can learn and avoid problems.

My understanding, based on watching the install scripts as Magisk/SuperSU do their business and also from my experience of the results (i.e. a working root), is that the root process unpacks the boot image, tweaks the kernel in ways that I'm too inexperienced to understand, repacks and installs the rooted boot image.

It therefore doesn't make sense to me to tweak the ROM's native kernel and then to apply a new kernel over the top of it. Common sense (maybe not the best arbiter in a technical world) tells me that whatever work the root process has just performed has been lost.

Perhaps blu_spark has something which overrides this, or it may just be that I have misunderstood the root process - though given that I can't remember having any root problems I guess that I must be doing it right... :)

If any developer would like to clear up this question I'd be grateful, especially eng.stk, who would seem to be the ideal person to talk about blu_spark - a kernel I haven't yet tried, but about which I've heard nothing but praise.

(P.S. I'd thank you, but... "Sorry, you are limited to 8 thanks per day"... :))
[Magisk] helroz:
On the latest update, the "updater binary" is updated and when you have "Magisk image mount failed" - "ressource busy"

The "system" mount point is locked, not possible to mount or unmount "system" directory.

For unlock it you must reboot and magisk install only root.

But for many user (me too) in twrp the script don't work with this problem.

On older revision, no problem.

Edit:

***********************

* Magisk v13.0(96f8efc) Installer

************************

- Mounting /system(ro), /cache, /data

- Device platform: arm64

- Constructing environment

Archive: /dev/tmp/magisk/common/magisk.apk

inflating: lib/armeabi-v7a/libbusybox.so

unzip: invalid zip magic 000005AB

- /data/magisk.img detected!

ioctl LOOP_SET_FD failed: Device or resource busy

ioctl LOOP_SET_FD failed: Device or resource busy

ioctl LOOP_SET_FD failed: Device or resource busy

ioctl LOOP_SET_FD failed: Device or resource busy

ioctl LOOP_SET_FD failed: Device or resource busy

ioctl LOOP_SET_FD failed: Device or resource busy

ioctl LOOP_SET_FD failed: Device or resource busy

ioctl LOOP_SET_FD failed: Device or resource busy

! Magisk image mount failed...

Le processus Updater s'est terminé avec ERREUR: 1

I:Legacy property environment disabled.

Erreur lors de l'installation du fichier zip '/sdcard/Download/Magisk-v13.0(96f8efc).zip'

Mise à jour des informations de partition...

I:Data backup size is 12027MB, free: 33434MB.

I:Unable to mount '/usb-otg'

I:Actual block device: '', current file system: 'auto'

...terminé

I:Set page: 'flash_done'

I:operation_end - status=1

I:Set page: 'clear_vars'

I:Set page: 'install'

I:Set page: 'main'

I:Set page: 'clear_vars'

I:Set page: 'main2'

I:Set page: 'mount'

Failed to unmount '/system' (Device or resource busy)

Failed to unmount '/system' (Device or resource busy)
[Magisk] NeoZX58:
Mmm twrp from ganesh varma? Is the only that works form me.. Others fail on install magisk or have too much bugs..

You use stock for VOLTE or anything else? For me, the stock rom of J5 is so annoying, have more complexity for patch, modify or flash anything, also, the v12 of magisk have little problems to install in Samsung roms.. Maybe in v13 it's fixed but it's something to consider..

I think you have 2 options, reflash stock rom if anything of past installations broken anything, or maybe, move to custom rom, if it's based on aosp/los, magisk work well..
[Magisk] edzamber:
Yes, in that way its working.

But for dev like me witch want include Magisk into Rom zip via Aroma its not working.
[Magisk] Frosthaxx:
Was curious what happened to busybox option.also sony framework breaks safetynet.otherwise everything works as expected
[Magisk] GatorsUF:
Device: Nexus 6P on Android O DP3

The v13 beta seems to work for the most part and passes safetynet. Only issue is when I try to start greenify it can't get root privilege. After greenify fails the safetynet check fails. A reboot seems to make safetynet work again.

Same behavior noted with naptime.

Maybe naptime and greenify aren't compatible with Android O, but figured they would at least be able to get root access. I'll grab a log if I can figure out how.
[Magisk] Didgeridoohan:
https://xdaforums.com/showpost.php?p=72293984&postcount=20

And

https://xdaforums.com/showpost.php?p=72703821&postcount=1120
[Magisk] Choobilsky:
These are my ahrion modules, thanks for giving itva look
[Magisk] Tesla:
Thanks.

I had to reinstall my kernel, boot, install Magisk manager, boot to recovery, install Magisk-v13.0(96f8efc).v2.zip linked in this thread to get it to work.

No problems so far.

Magisk-v13.0(96f8efc).v2.zip

[IMG="Magisk-v13.0(96f8efc).v2"]http://i.imgur.com/57smHcW.jpg[/IMG]
[Magisk] kramer04:
Just an update as i can't install Magisk 96f8efc on my Samsung Galaxy Note 3 SM-N9005

I just swap Magisk Manager 96f8efc with 090e8b6.

So i've can pass safetynet and install modules.

I think it could work for Samsung devices and may be other devices
[Magisk] Jrhotrod:
How did you flash with the app? All Magisk Manager is letting me do is download & install 12.0, but I want the beta
[Magisk] tdunham:
You can't. Use custom recovery.