yashsingh1/xdaforums huggingface dataset:
[Magisk] callumbr1:
Use this busybox

https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer

And then flash this viper through TWRP

https://mega.nz/#!CV5wQYSa!i-V1UvJ_Lh9YoZDPN9rUUXuJNgXWcXRlhBE83fYH7e8

This all I had to do and it works flawless.

It should automatically install audio modification library in magisk but if it doesn't just install it manually.
[Magisk] dimm0k:
is it possible to use Magisk to replace a file in the root file system or is it limited to /system? would like to know before make changes...
[Magisk] scoliosis:
Using Magisk 13.3. Android Pay works no problem. I used Magisk Hide and selected Chase Pay but it still detects root. Same as the Concur app. Am I missing a step somewhere?
[Magisk] dimm0k:
the Chase app detects root?? I know when I used SuperSU I got the prompt to give Chase root and I denied it... with MagiskSU I never got that prompt.
[Magisk] Pkt_Lnt:
I just posted this a few posts above.

There are other ways apps detect root that Magisk can not help. Check Didgeridoohan's [GUIDE] Magisk and MagiskHide installation and troubleshooting (Magisk v13.3) look at post #4 Hiding root and passing Safety Net.
[Magisk] scoliosis:
The latest one does I guess. Just installed it and prevented login. The banking app doesn't care.

---------- Post added at 02:17 PM ---------- Previous post was at 02:14 PM ----------

Thanks, I did read those pages and wanted to double check that I didn't mess up adding apps to be hidden. Lord knows I've been away from this scene long enough to be a complete n00b again.
[Magisk] shirtsofbamboo:
I wish it worked that easily for me. I uninstalled the magisk viper and busybox modules, uninstalled the stericson busybox from the app store, and installed the busybox you suggested. Then I flashed the viper you suggested through TWRP. It shows in magisk as v1.4 (2.5.0.5). Opening the viper app still gives me the same error about busybox. And busybox is definitely installed and working at /system/xbin.

Do you know if there is a way to flash the driver manually through twrp? If so, where would I get the zip file?
[Magisk] Didgeridoohan:
Magic Mount is limited to /system and /vendor. You can use boot and module scripts to place files elsewhere...
[Magisk] Wolfcity:
Flash Magnum Opus from Arise. You can flash just core and viper 2.5.0.5 and the magisk compatibility module if you want to but there are many more soundmods worth investigating and the sound is amazing.
[Magisk] pehlm:
Possible a dumb question, but... here it is: having the phone unrooted with some custom ROM, is it possible to just hide the unlocked bootloader with Magisk but not using MagiskSU, thus let the device being without root? If it's possible how to do this? Thanks in advance!
[Magisk] Artim_96:
You can just disable root in Magisk manager
[Magisk] pehlm:
Thanks! Is SafetyNet passing or is it for example possible to download Netflix through Play Store if I just disable root in Magisk Manager?
[Magisk] crayg713:
Magisk without Custom recovery

Hi

Im a newbie to phone rooting, so pls forgive me for any stupid question I may ask.

I have rooted my phone before but never had to do anything advanced until now...

I need help creating the magisk boot.img as there seems to be no compatible custome recovery for my Samsung sm-j111. I have tried doing this via ADB using the instructions on the Magisk page but am struggling & encounter errors.

My phone is rooted, using termux & connected to windows machine.

Any help will be greatly appreciated
[Magisk] teddy0209:
I mean yes, any of the v13 works on MIUI... As for root hiding, you need universal hide from the safetynet fix module... Is that clearer?
[Magisk] Artim_96:
You have to pass SN and your ROM must support Goggles Widevine DRM
[Magisk] CommandAir:
Yep, all right. It's clear :)

Tried the SolarWarez sdk23 Magisk version for MIUI, but not really work.

What's the right order of flashing a complete system?

1. ROM

2.Kernel

3.Opengapps

4.Magisk 13.3

5.xposed-v87-sdk23 magisk-miui

6. Safetynet fix ??

Is above right?
[Magisk] Didgeridoohan:
If you post the ADB output with the errors someone might be able to help.
[Magisk] crayg713:
Thanks... by sheer luck I clicked a link to another thread & found a poster who had managed to get an unofficial twrp & it worked.

Just finished installing twrp, magisk & xposed.
[Magisk] teddy0209:
The steps should work fine... But I'm not sure about the xposed for MIUI, might need updating to work on v13 of magisk, I'm not sure, I can't test 'cause I'm on 7.0...

By the way, you won't pass safetynet with active xposed, it needs to be disabled (It won't recompile if you use the xposed installer app to disable to avoid long boot up)...
[Magisk] Pkt_Lnt:
Nice tease, ask for help, then post you found the answer. Boo on you for not posting the solution or link here to help others, which is what XDA is all about. :(
[Magisk] shirtsofbamboo:
Thank you. Oddly, I'm still getting the same error from the viper4android apk that was installed by Magnum Opus! But worded just a bit differently. "Installation failed because busybox is not functioning properly. Try using Stericson's busybox or check if root access is available." So the 2.5.0.5 driver is not getting installed. busybox is in /system/xbin and root is defintely working.
[Magisk] Paschfire:
If you choose, click both Links available within my signature below.

One will navigate you directly into ARISE XDA Thread where you can find Support, the other will Link you to the various Telegram Chat Groups, ARISE Support Telegram would be a good place to start. ;)
[Magisk] ShadySquirrel:
Give Viper4Android module from my signature a shot, it's based on original topjohnwu's module, I just rewrote it for module template v4. Works for me on kiwi running Lineage OS, no driver installation is required.
[Magisk] navcar:
A tip to anyone experiencing high cpu usage of 'magisk_daemon' - the android logger may have been disabled, causing magisk to repeatedly loop whilst waiting for logd to start which never ends up happening. I recently applied someone's Kernel Auditor profile and tracked the busy cpu down to this. Turning the android logger back on fixes this :)
[Magisk] Phrozinsun:
Adb error

I'm new to the magisk and I have been trying to figure out how to make a new.boot.img though adb. I open the terminal and follow the steps given on 13.3 forum. I'm see that I'm have to do a extra step in between adb push META-INF....... line and adb shell "cd......." line, I have to manually add bin with a subfolder of busybox to the/data/local/tmp folder or I get mv: bad '../bin/busybox' : No such file or directory and along with that I get a ! Unable to extract zip file! above that. Phone is a SM-J320AZ rooted by kingroot, busybox is installed, adb has been giving root permissions and knox and frp have been disabled/frozen. There is no custom recovery for this phone( or nothing I found in three days of searching). Any help would be appreciated. (I do not believe I can add a image yet sorry:(
[Magisk] apih46:
magisk manager crash after charging on power off phone. i has tried clear data, reinstall magisk manager but still crash. i tried flash magisk through twrp again n it work. please fix this. [aosip android 7.1.2]
[Magisk] geoff2011:
Can someone please explain?

Hi,

I finally found the time to update my Galaxy Note 3 to RR 5.8.3, and the ROM comes with Magisk manager (Magisk v12) installed. Magisk manager tells me that Magisk v13.1 is available, so I click the update/install. Magisk 13.1 is downloaded, but not installed. I click the update/install a 2nd time, am asked if I want to install, I confirm. Nothing happens.

Is the install not functioning, and am I supposed to flash it manually using TWRP, or how do I please do this?

Thanks a lot
[Magisk] arrrow:
I can not get v4a working on any magisk version higher than 12.0. It just keeps saying status abnormal format unsupported etc. What I've tried so far: flash uninstaller, flash magisk, v4a zip, v4a magisk mod, audio mod lib zip. In that order. After booting v4a installs the driver, but apparently to no avail.

I am running lineage 14.1 and have the busybox app and v4a zip from the post on page 1835.

How can I get it to work?
[Magisk] romirom:
Magisk & ViperOne m8 6.1.0 - MotionLaunch

Hi,

I'm using ViperOne rom on my m8. I would like to move from preinstalled SuperSU to Magisk (root detection). I restored stock boot image, installed magisk zip, but then MotionLaunch just stopped working (i need it!). Found out, that the installer of ViperOne installs SuperSU systemlessly, and then copies some files into /data/su.img. I've compared su.img with those files and bare su.img generated by the SU inustaller - added files are: xbin folder (most likely busybox), su.d folder with 99venom script with setenforce 0 and some not important commands, etc folder with hosts file. What am i supposed to do to make MotionLaunch work with Magisk?

I've been fighting with it for over a week now, and can't find a solution... Could you help me?
[Magisk] bseos:
anyone have this installed on Android 8.0 Oreo? Is root successful?

edit: nevermind, I shouldn't be so lazy. I found the answer after a quick search within the thread:
[Magisk] p8tgames:
I dont know where to make bug reports, so if this is in the wrong place, feel free to delete this comment!

There is a bug in magisk 13. On my Moto g5 magisk cant Install through TWRP. (Only 11.6 works.) And in the app magisk can't find the boot Image path. This is annoying...

Thanks.

(I really hope this is the right place...)
[Magisk] Prototypefab:
Hi there, i'm having some troubles running magisk 13.x on Huawei mate S. i just updated to stock MM rom, and was trying to flash 13.3 magisk zip from twrp. the zip flash does not show any error, but when the phone reboots it boots into bootloader saying to restore phone, as it cannot load boot partition properly. the only way of fixind this is extracting the original boot.img from firmware and flashing that via fastboot (for some reason magisk uninstaller wouldn't work)

i've also tried the adb method with magisk 13.6, but when i flash the patched boot.img this is the output https://pastebin.com/Zp5pqZ4H

finally, i tried to flash magisk 12.0, and that works as intended, so what broke everything is definetly something in magisk 13.3

the only "relevant" log i can find (this is the magisk 12.0 log, saved from magiskmanager)

https://pastebin.com/mG27yAwV

edit: of course trying to update magisk from magiskmanager on 12.0 brings to the same bootloader screen
[Magisk] tattmann:
Hello all, I really need some help here. I am really brainfried and cant think straight. I have fought this phone for 5 days and finally got a rom flashed into my n910v, non rooted and non xposed version of the nseven build. I can NOT get magisk to pass safetynet at all. I have made sure no su binaries are left behind, it is a clean flash, tried the safetynet fix flash, I simply cant get it to work. I have a dying s5 (my daily driver till I get this note 4 fixed) with resurrection remix, it uses magisk flawlessly. I think it comes down to the fact that the rom is set to permissive selinux, but not sure. I downloaded a selinux toggler, but it doesnt seem to work. the rom is still set to permissive and magisk fails both basic integrity and cts profile. The rom as I stated is unrooted and no xposed. Can someone please help?

Nevermind all, I flashed a different kernel and it now works great! Thanks for this program!
[Magisk] Firdhaus81:
Dear advisors,

Iam using stock samsung note 4 SM-910G. Snapdragon 805. Android 6.0.1. Marshmallow. I need advise on to how to install magisk on my device. Can it be done? Appreciate on a step by step instruction on how do i install it. :cool:
[Magisk] Akhilesh S V:
Just flash Magisk 13.3 in recovery
[Magisk] Firdhaus81:
Do i flash after i root? I dont need to uninstall supersu first?
[Magisk] Firdhaus81:
So i rooted and everything. Installed magisk 13.3 vua magisk manager and i got this error.
[Magisk] Firdhaus81:
So i installed magisk manager 5.1.1 i tried installin magisk 13.3 and got this another error.
[Magisk] Didgeridoohan:
Are you trying this on v13.6 beta? ADB installation won't work on anything else. The method to install Magisk through ADB is in a beta stage and undergoing changes. I'd wait...

But, as a side note: I don't know if Magisk is able to remove Kingroot during installation. For the best result you might have to unroot first.

Logs or it didn't happen...

Yes. Try in TWRP. And don't forget to provide logs if it doesn't work.

Proper bug reports should go on GitHub. And include logs...

There are known issues with the G5. IIRC it has to do with a f2fs bug (please, someone correct me if I remember wrong).

Even though you can't see any errors in the recovery output there might be lots of useful information in the recovery log that you could provide...

Just to make sure: Did you first remove SuperSU, like you wrote about above? You'll have to.

The error you're seeing here is a Marshmallows specific bug that's been fixed in the current beta.
[Magisk] Akhilesh S V:
Uninstall Super SU and flash Magisk 13.3
[Magisk] Firdhaus81:
Thank you sir for replying. Now the thing is when i do a full unroot via supersu i will keep the custom recovery as the screenshot stats ill press no on it. But then when it does the unroot it somehow removes the twrp too which im unable to flash anything at all.
[Magisk] Firdhaus81:
Attached screenshot.
[Magisk] Firdhaus81:
So i managed to get twrp working after full unroot. I did a flash with 13.3, 13.5 & 13.6 beta all gives me error 1. I even flashed magisk uninstaller for each of the zips before installing them. Still the same. Am i doing anything wrong?
[Magisk] Firdhaus81:
Is there anything to do with my kernel? Attached kernel info.
[Magisk] munjeni:
[MENTION=4470081]topjohnwu[/MENTION] my trim area poc thread contain a lot of reports definitelly unrelated to my tool! Peoples reporting magisk isues in my thread, but thats not my tool problem, wrong thread. I had a deep look into diferencie between unmodified kernel rakdisk and one after magisk https://xdaforums.com/crossdevice-d...ad-drm-fix-t3552893/post73557687#post73557687 , I have found no isues related to magisk installation patching procedure, everything is patched corectly but we have found avc denials related to /vendor , some ramdisks uses vendor symlink instead of real vendor folder in ramdisk, ramdisks which have symlink vendor gets selinux denials and it cause boot loop. I am in hope you finaly do something about it. One guy provided kernel crash log, you can see ton of avc denials https://xdaforums.com/showpost.php?p=73518052&postcount=1592 , hope that help you to solve magisk isues on sony ramdisks. I have no needs for looking into this since I not using magisk but hope this help you.
[Magisk] Artim_96:
You have to give us the TWRP logs for that, they normally say more than it shows you. Go to /cache/recovery and get us the last_log (you probably have to rename it to last_log.txt to be able to upload it here)

---------- Post added at 12:43 PM ---------- Previous post was at 12:41 PM ----------

Maybe you shouldn't report that here, I guess the best would be if you open an issue at his GitHub page, there he will probably see it faster
[Magisk] koko115:
How often [MENTION=658468]topjohn[/MENTION]vu clone new modules to magisk repo ? Today i submitted new modules in github. But i see some modules submitted two weeks ago and still i dont see their in magisk app for download.
[Magisk] Firdhaus81:
Attached last log.
[Magisk] Artim_96:
Either there is something missing or you booted into TWRP after flashing Magisk, it's not showing that you even tried to flush anything.

Go to TWRP, flash Magisk again, wait for the error, boot to system and get it again and upload it
[Magisk] Firdhaus81:
I just flashed with that same error. Attached the log which i just did. Also attached the ss of the error in red.
[Magisk] Artim_96:
Very strange. The log shows absolutely nothing about a tried flashing.

Do you have also a file in that same folder that's just called log? If so, please update that one too. Otherwise, go to TWRP again and flash Magisk once more. But this time stay in TWRP, go to its file manager and there go to /tmp. There should the log file of the current session be located. Copy it somewhere on the internal storage or sdcard (in TWRP they are under /sdcard for internal storage and /external_sd for your SD card)

Btw: your screen says that your boot.img was patched by a different program. So either you forgot to uninstall something else or your ROM comes prerooted with systmless supersu and had a pre-patched boot.img. in that case you can't flash Magisk, you will need either a custom kernel with its own ramdisk not containing any such modification or a different custom ROM that is not prerooted that way
[Magisk] Firdhaus81:
Thanks artim. The thing is im not usin any ROMs its on stock. I have a log called recovery.log the thing is i cant seem to rename it to txt as it will rename recovery.txt.log. if its kernel then i gotta flash a kernel which is suited for magisk? Anyway ive attached my kernel info too.
[Magisk] Artim_96:
Kernel is not relevant as long as it's newer than 3.4.

Sadly that log also says absolutely nothing. It shows that TWRP is loading but no other action. No flashing
[Magisk] Firdhaus81:
Damn this is really weird. I dont know what am doin wrong here. As u can see i did flash.. hmm
[Magisk] Artim_96:
Anyway, TWRP already showed you that your boot.img is somehow compromised, do you should ask at your devices forum what could cause that
[Magisk] Firdhaus81:
Anyway i could default em back? This note 4 iam using ive never rooted it before. Just did last 2 days ago just to get magisk.
[Magisk] Firdhaus81:
Root check is showin am not rooted. But my internet, when i wanna do a secret mode it says iam rooted lol..
[Magisk] Artim_96:
Just get you firmware from sammobile, flash it through ODIN, flash TWRP through same and you should be able to flash Magisk
[Magisk] Firdhaus81:
Same firmware as iam usin now? Ok i could do that.
[Magisk] Artim_96:
First: what horrible browser are you using that cares about root or SN?

Second: have you added that browser to Magisk hide and rebooted? If so it's using a root detection methods that can't be worked around. Get rid of it

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

Of course.
[Magisk] Firdhaus81:
Lol.. that browser came with note 4 itself. I dont that magisk hide option.
[Magisk] Artim_96:
What a surprise... You have to get Magisk to work first of course...
[Magisk] Anas Rahman:
Can i flash it on an already rooted device with SuperSU installed? (sorry for such a noob query)
[Magisk] DenyDarko:
No.

You have to COMPLETELY remove every trace of superSU and restore your stock boot.img before attempting magisk installation.
[Magisk] Anas Rahman:
Magisk is not device specific, right? I mean the same zip works for every device?
[Magisk] DenyDarko:
Yes.
[Magisk] am2006:
hi

i have this problem when i try to install some models (Greenify, xposed, DOS4GMS,..), but some models work fine (emoji, busybox)

help please

Galaxy A5 (2017)

android Nougat 7.0

TWRP 3.0.2.0
[Magisk] MysteryMan105:
I can't seem to root my Huawei Nova for some reason.

I also posted the log, it would be awesome if someone could help me.
[Magisk] DenyDarko:
Well... Enter recovery Flash the uninstaller (found attached in the 1st post of the release thread), reboot into recovery and flash 13.3 and test again.

PS: If same result give the beta 13.6 a try.
[Magisk] fubag:
i got an issue with a fresh install of lineageos 14.1

when I try to open SuperUser from within the manager, it keeps saying the application has stopped...

root is working on some apps, but app like Greenify gets denied and I can't enable it in Super User. Any suggestions? Tried reinstalling the manager and that didn't work.
[Magisk] DenyDarko:
No you haven't reinstalled as superuser data are there if some apps are allowed to use root.

Go to Settings and clear magisk manager app data.

Then reboot and try again
[Magisk] Firdhaus81:
Hi Artim,

Is there any way i could download the stock firmware faster in sammobile other than buyin premium? Or u got any other websites to recommend? Its taking ages in free download:eek:
[Magisk] BadBoyNDSU:
No magisk_debug.log found. Attached recovery.log.
[Magisk] Artim_96:
There actually is. Somewhere here on XDA is some software, that's discontinued but still working called SamFirm I think. If you find the thread you'll also find a look to the website they use to get the files from
[Magisk] crayg713:
Pls forgive me, was just so happy I got my phone working I didnt think to post the solution... Maybe if I had, I would've discovered the xposed causes boot loop, so need to find unofficial version for my Samsung.

Here is what I found / did:

1. Thanks to SaLiXeM, I got he unofficial TWRP for sm-j111f

link - http://1drv.ms/f/s!ApEHyHGYGLNEg9RD4ZByFQ1QjGEd2Q

2. I flashed my phone to the original stock I got from this thread "[ROOT][BOOT] SM-J111F / SM-J111M Samsung Galaxy J1 Ace"

3. put phone into odin mode & flashed the recovery.tar

4. after reboot, I copied the lastest magisk 13.3 to my phone storage as there is a wierd issue of not being able to see sdcard.

5. Booted into TWRP & flashed the magisk.zip

6. rebooted & installed magisk manager "downloaded from the magisk page"

7. Checked the safetynet worked & had root access due to v13.3 having magisksu bundled.

8. since xposed boot looped my phone, I wont include those steps as I now need to find a working version for Samsung.

If I manage to find a working version of xposed, I will paste it here.
[Magisk] SuperPavel:
Hello everyone

First, I present to you my apologies if this is not the right place to ask such a question.

I would like to be able to use Magisk, but it seems my current smartphone (Huawei Nova) is ill suited for that: I had a lot of difficulties to only install a working TWRP on it (there was problems with encrypted / unmountable partitions), and in the end I was glad I was able to undo the mess I created on it, by doing a clean install with a stock firmware. Following this, I am looking to get a smarpthone that would be "mod friendly": easy to toy with, and to install Magisk on. Since this would not be my main smartphone, I am looking to get such a smartphone for not too much money (would not mind if it was not brand new, for instance, or if it was not from the very last generation of smartphone). Would you happen to now which brand of smartphone would be compatible with those criteria? From what I understood, the OnePlus brand meets them. Would you agree with this? Would a OnePlus One be a good pick, in your opinion?

Have a nice day,

Pavel
[Magisk] crayg713:
Thanks again to

hernankano

, He gave the link to a working version of xposed for SM-J111F

http://xdaforums.com/show...2&postcount=19

I downloaded the zip & followed his instruction from his thread "[ROOT][BOOT] SM-J111F / SM-J111M Samsung Galaxy J1 Ace by hernankano".

I wasnt sure about fireflash, so I copied the xposed zip to my phone & used TWRP to flash from recovery.

No boot loops & xposed installer works perfectly.

Edit: xposed trips safetynet so need to find fix for this
[Magisk] :
Hey everyone.

I just reinstalled my phone from scratch and wanted to start using Magisk on this device too (I'm already succesfully using it on my Sony tablet).

Problem is: the Safetynet check keeps failing. (cts profile mismatch + basicintegrity: false)

I read somewhere on this forum there is a universal fix which I found amongst the modules for Magisk. But trying to install that causes the app to crash. ( I can briefly see the error message before the crash, which says Magisk is not active). In fact, every attempt to install any module causes a crash.

so here's what I did so far:

clean flash of Lineage 14.1

flashed openGapps

flashed Magisk

uninstalled Magisk (by flashing the uninstall zip)

reflash Magisk

device: LG G2 (d802)

TWRP recovery

Anyone who can help?
[Magisk] wiQbold:
I think there is a complete thread about saftynet errors.

Did you try to de-/activate USB-debugging? which magisk version you use for?