yashsingh1/xdaforums huggingface dataset:
[Magisk] Dauntless:
The included build_module.py creates the magisk module by downloading the latest frida-server. I've attached the created module, but I removed frida_server64 due to file size. When using the python module, it's in there.

The log doesn't include anything weird:

--------- beginning of main
I( 242: 242) Magisk v14.0(1400) daemon started
I( 242: 244) ** post-fs mode running
--------- beginning of system
I( 242: 261) ** post-fs-data mode running
I( 242: 261) * Mounting mirrors
I( 242: 261) mount: /dev/block/platform/msm_sdcc.1/by-name/system -> /dev/magisk/mirror/system
I( 242: 261) link: /dev/magisk/mirror/system/vendor -> /dev/magisk/mirror/vendor
I( 242: 261) bind_mount: /dev/magisk/mirror/bin
I( 242: 261) * Mounting /data/magisk.img
I( 242: 261) Resize /data/magisk.img to 96M
I( 242: 261) * Running post-fs-data.d scripts
I( 242: 261) * Running module post-fs-data scripts
I( 242: 261) busybox: exec [post-fs-data.sh]
I( 242: 261) * Loading modules
I( 242: 261) busybox: constructing magic mount structure
I( 242: 261) MagiskFridaServer: constructing magic mount structure
I( 242: 261) bind_mount: /system/xbin
I( 242: 291) * Starting MagiskHide
I( 242: 291) hide_utils: Hiding sensitive props
I( 242: 291) hide_list: [com.google.android.gms.unstable]
I( 242: 291) proc_monitor: init ns=mnt:[4026531840]
I( 242: 406) ** late_start service mode running
I( 242: 406) * Running service.d scripts
I( 242: 406) * Running module service scripts
I( 242: 291) proc_monitor: zygote ns=mnt:[4026534382]
[Magisk] davidlikeandroid23:
It does not work but thanks , My device is Huawei P8 Lite Ale-L21
[Magisk] Didgeridoohan:
Cool! I didn't look to close at the rest of the files in there. Thank you for clarifying...

Anyway, I installed the module you posted and everything mounted just as it should. If the module doesn't mount properly on your device there's something going on with your Magisk installation. Are you positive that the files can't be found under /system/xbin?
[Magisk] Veid71:
I'm not sure tbh I used to be on the unofficial one I think I used to be on 13 then I switched to SU and suhide and I decided to switch back and give it a try again and now it's doin this, I've installed stock everything like 3 times just today alone lol but here my process on what I do,

Fastboot Stock google everything

Fastboot 3.1.1twrp img

Install 3.1.1 twrp, install my pure Nexus 7.1.2 rom

Reboot into it

Then reboot to twrp and flash my EX kernel reboot into rom and make sure it stuck

Go into twrp and flash magisk 14.3 (14.0 gives me the mounting system error)

Reboot and go into magisk and install the modules I want and reboot
[Magisk] Dauntless:
Thanks for troubleshooting with me.

hammerhead:/ $ su
hammerhead:/ # ls /system/xbin/fr*
/system/xbin/free /system/xbin/freeramdisk
hammerhead:/ # ls /magisk/*
/magisk/MagiskFridaServer:
auto_mount module.prop system

/magisk/busybox:
auto_mount module.prop post-fs-data.sh system

/magisk/lost+found:
hammerhead:/ # ls /system/xbin/busybox
/system/xbin/busybox

The busybox, however, is correctly mounted, as you can see.
[Magisk] yochananmarqos:
Try flashing the PureNexus boot.img, then try Magisk. If that's successful, then flash EX kernel & reboot.

For a clean install, I would flash stock Google images, then PureNexus, Magisk, EX kernel and then reboot. No need for all the multiple reboots, FYI.
[Magisk] Veid71:
ill try that, but i thought the EX kernel had to be flashed before magisk in order for magisk to stick?
[Magisk] Shtiff1:
Just curious on how you uninstalled superSU?
[Magisk] Veid71:
well i bootlooped my phone installing something from xposed so i deleted whatever it was and got back into my phone and it said xposed and SU wasnt installed even though they both showed up in my apps so i wound up just fastbooted the stock google firmwares and installed magisk and now i have this issue, but it shouldnt be because of SU because i fastbooted the original google firmwares right?

edit: even though i just reflashed everything to stock i looked in the file manager and i saw a file called root and supersu? how is that possible, i left the -w command in the flashall.bat file
[Magisk] onliner:
I have created my own module to change the font of my device, but every time i install it simply breaks the SafetyNet, instead if i install it directly on the system and then install Magisk, it works perfectly.

I've looked for other similar questions in this thread and seeing the answers i start to believe that the culprit is my module, but I'm not entirely sure, nothing seems to be wrong with it.
[Magisk] H4X0R46:
Quick question, does Magisk still turn off forced encryption?
[Magisk] zairmalik:
Hi, I have a question. How do you obtain stock boot image dump? A newbie here.
[Magisk] Pkt_Lnt:
Extract from the stock / factory image
[Magisk] yochananmarqos:
No, it does not. The ramdisk modifications do not conflict with each other.
[Magisk] digitalhigh:
Holy hell, this thread is CRAZY. Whatever did I sign myself up for? :P

Got the online downloader almost ready to go, just about to toss a copy over to [MENTION=1162986]Captain_Throwback[/MENTION] for some testing. A few more small refinements I want to make quick, and then it'll be in [MENTION=4470081]topjohnwu[/MENTION]'s hands. Looking forward to the party. ;)
[Magisk] Apexpredator12:
Have I done something wrong, I have systemless xposed and systemless root, but apps still detect that I'm rooted any help?
[Magisk] westeight:
Can confirm that deleting system/xbin/su kills Phh functionality. It should only be deleted if present BEFORE installing Phh.

Did the following on a fresh HTC 10 today, to confirm it works 100%

1. Run UnSU, Magisk uninstaller and Xposed uninstaller

2. Manually remove the following SU fragments:

/su (delete all files in folder. The folder itself cannot be deleted)

/system/xbin (delete the file 'su')

/root

/supersu

3. Install Xposed .apk, install Phh .apk

4. Flash Magisk, Xposed and Phh SuperUser

:)
[Magisk] adrman:
Not to mention [MENTION=1162986]Captain_Throwback[/MENTION] is going to have to officially come out of "Retirement".

---------- Post added at 12:21 AM ---------- Previous post was at 12:21 AM ----------

Yes.
[Magisk] EdGe7x:
Got it working on T-mobile Samsung J7 (SM-J700T)

So these instructions also worked for me. So the secret ingredient here is Update-unSU.zip.

I basically had SuperSU installed and ran through steps 1, 2, 3, 4.2 - 7 on a stock T-mobile image.

Looks like Magisk just needs a little tweaking and it will be perfect.

Reading through every post is time consuming but you start to determine what info is good and what is junk. Then a gem of information jumps right at you... bam!
[Magisk] Äptiva:
For the LG G2 users reporting errors, please add your variant, rom, and kernel so I can continue testing on my own. I will likely be trying to fond a way to resurrect my vs980 as well for testing. I'm just trying to help and I'm not part of this project so we all know.

Edit:

So far I'm finding Magisk and the LG G2 d800's stock 30f kernel hate each other. Using multiple bump tools I couldn't get it going properly. I didn't pull dmesg or kmesg yet. Dorimanx LP kernel worked well. I was unable to turn SELinux support on it even with the dorimanx enable sel script(something I'm doing). Used phh superuser and gained root, able to toggle on and off. Android Pay not tested PokemonGo not working(can't say if rom or not I need a stock d800 LP rom).
[Magisk] Captain_Throwback:
We're all part of this project. That's the great thing about open source ;).
[Magisk] jorisw86:
Magisk toggle keeps on turning back on

Hi all,

Got everything working on my samsung s5 with cynogenmod 13.x supersu works magisk manager works. I can toggle selinux on or off. When i toggle root acces it goes off and a sec later on again how does this keep on happening?
[Magisk] wewenk:
I hope there is a way to get magisk installed on Locked bootloader device...
[Magisk] juss1fix:
Try removing Titanium Backup and/or ROM Manager and see if that works. Some of these programs keep their fingerprints on your phone and since they are entwined with SU then there can be lingering files depending on your setup. I am using a Moto X Pure with a custom stock rom. I tried doing this on CM13 MM at first but I was having the same issue as you. If you have neither of those installed then consider flashing stock and not logging into Google when you set up. Don't install anything but these files that way you eliminate any variables. You will be happy when that button sticks and "unmounted" pops up in green lettering.
[Magisk] Äptiva:
What device?
[Magisk] Nando_aot:
G2 D802/805

ROM: AICP 11 (MM)

Kernel: Stock as far I know.

I have removed the root and the game is working but I get security boot message when I do install Magisk.

Thank you
[Magisk] Astur13:
Me too, I get security boot message when I flash Magisk.

ROM: CM13 Snapshot 20160820

Kernel: I didn't change it, I suppose that is CM stock Kernel

For now, there's no solution for G2 owners?
[Magisk] TapioH:
Finally got this program working. Page 203 had great solutions on the workaround.. I was missing Update-UnSU. Oh well. PoGo still wont run, no matter how i do it.. Two phones, neither works. Other is fresh CM13 with never active root. Other OPO with Nougat rom, fresh install. Magisk toggle works.
[Magisk] Chadwilliam1:
I really want to install this to get android pay working but I am confused.

I have a fully rooted s-off htc 10

I have viper rom 3.1.0 with ElementalX kernal.

Do I need to flash the stock kernal back before i flash Magisk? Can I use TWRP to flash Magisk?

I apologize if this is a redundant question but the more I read about it the more confused I get.
[Magisk] Nando_aot:
After removing the root my game back to work.... this is the "solution" for now..
[Magisk] Äptiva:
Are you rebumping your images after? Flash the mod then flash the bumper from this thread right behind it:

http://xdaforums.com/lg-g2/development/cbump-bump-current-boot-image-t3325186
[Magisk] conn2005:
"Eventually might lead to universal Multirom support for all devices (Concept only, haven't started to work on it yet)"

So if I'm using MultiRom 1.188 on my OnePlus One with Android 6.0.1, Magisk will not work at the moment?
[Magisk] Astur13:
But we lose all root posibilities, that's what I don't want. I prefer stay at pokemon version 0.35.0 and wait for a real solution :( Soon I hope

I've never bump anything xD but I'll try. Could you install Magisk with that method?
[Magisk] psycholyzern:
Seems that a few people having the same problem as me, which is cant toggle off root. Does anyone found the solution already?

---------- Post added at 09:00 AM ---------- Previous post was at 08:50 AM ----------

Please consider to not to quote the whole post in the future. It hurt so bad to phone user like me.
[Magisk] Veid71:
Do you know how I can uninstall it then? I can't seem to find an uninstaller for 2.82 SR5
[Magisk] yochananmarqos:
Uninstall what? SuperSU? No wonder you're having issues. Choose the Fully Unroot option from the SuperSU app and reboot.
[Magisk] Veid71:
i dont have the app to choose that option lol but i did just reflash it and choose to uninstall it, then i rebooted into twrp and still saw a supersu folder am i doing something wrong? or is it because i installed it as systemless?
[Magisk] yochananmarqos:
That's the TWRP supersu folder. If you're still having issues, flash osm0sis' unsu.zip.
[Magisk] Didgeridoohan:
Hm... What's the contents of /magisk/MagiskFridaServer/system?

I did note another thing... The module will completely clear out /system/xbin (it's added under REPLACE in config.sh). Is that the desired behavior?
[Magisk] Krendelrus:
I use this ROM on my HTC One M8 https://xdaforums.com/htc-one-m8/development/romthe-worlds-first100-m9-port-m8upload-t3064838. It comes pre-rooted with SuperSU. I can't install Magisk v14 on it because of the patched boot image (and there is no stock boot.img). Is there a way to install Magisk without the unmodified boot image?
[Magisk] Veid71:
Yeah I just used the osmosis unsu.zip it said it was removing magisk and SuperSU and to flash my rooms boot.img so I just reflashed to stock Google's images but I'm still getting the same issue as before modules won't show up in the modules section unless I manually move them from my SD card folder to my system folder and even then they disappear after I reboot this is the version I'm using it's the correct one right? https://www.google.com/amp/s/xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/amp/
[Magisk] jenslody:
Did you try it without the other font-modules enabled ?

It (your module) does not break safetynet on my phone.
[Magisk] Dauntless:
I modified that part myself for troubleshooting, but I think this is the golden tip! The only other module that's installed is a busybox module, and this one does have /system/xbin as a replace. Since all the busybox modules are indeed in /system/xbin, it looks like this module took priority. So maybe the /system/xbin is hard-replaced by busybox, overwriting any mount of the MagiskFrida module? (Although it could theoretically be mounted on top of busybox's /system/xbin, but I guess that's not how it works right now).

For my purpose, it doesn't really matter where frida-server is located on the device, as long as I can run it. Should I move frida-server to a different folder? If so, which folder would be ok?
[Magisk] mohammad.nomaan:
Hi

I have been trying to figure out the cause of non compatibility between Magisk & MTK devices

The test device is MT6592 running a custom RR 5.6.8 ROM (Android 6.0.1)

any suggestions are most welcome

Thnx
[Magisk] Didgeridoohan:
That would be it...

I would either remove the REPLACE feature of the busybox module (or if it clashes with another busybox installation simply move the replace part to that specific folder, not directly in xbin - sounds like a bad idea to completely clear out xbin), or combine the busybox and Frida modules into one.
[Magisk] Dauntless:
Final quick question: Are there any restrictions? Can I choose any folder in /system to mount to? I assume the only difference is that /system/xbin is (maybe) automatically added to the path, while others are not?

Thanks for the help! :)
[Magisk] Didgeridoohan:
You should be fine mounting the Frida files to another folder under /system. First thought is bin or sbin if not using xbin, but don't add them to the REPLACE function! :p You could also probably put them in their own folder under /system/etc, or something like that.

Only restriction, Magisk-wise, would be that you'll probably get a bootloop if you add any new folders or files directly to the root of /system (i.e. /system/FridaFiles).
[Magisk] Didgeridoohan:
Unfortunately no. Ask the developers for a Magisk alternative.
[Magisk] DodoGTA:
Dump boot.img of this ROM and upload it, so I can take a look at it and probably remove SuperSU from it
[Magisk] onliner:
Yes, I've tried it, but SafetyNet breaks after installing it, maybe it's something with my rom, thanks for trying it :).
[Magisk] Krendelrus:
Here is a zip archive containing boot.img from the ROM
[Magisk] Zepar7:
Can anyone plese tell me If magisk is working on Oreo
[Magisk] beavis5706:
Sorry I haven't got back on that been very busy. So anyhow I'm curious as to what state you want to see those files in. I ask because when I went to gather the files earlier the magisk.log was empty, I was unable to find magisk_debug.log (it's not in /data) and I got "413 Request Entity Too Large" error when trying to upload masigk.img.

So what state do you want to see them. Right after installing a "bad" module? After trying to uninstall a "bad" module?

I used quotes for "bad" module because they aren't actually bad. For some reason magsik is just putting the files in the wrong spot upon installation. This is easily fixed my taking the offending module from the /dev/target folder that magisk is creating, moving it to /magisk and rebooting. Now the "bad" module works perfectly.
[Magisk] Artim_96:
Of course it is
[Magisk] acultr:
yes but not in OOS Beta
[Magisk] weaver11b:
I have searched everywhere with no luck. I have had magisk working on pixel 2 xl for the past week, but viper4android appeared not to be working so i uninstalled it and was going to reinstall it; however when i went to install again i got an error stating:

/data/magisk_merge.img mount failed...

Failed!

Installation error!

I have attached a most recent log, tried clearing chache and data of magisk, rebooting, installing new kernel, etc. This also does the same exact error for trying to install any magisk module. I still have unified hosts adblock still working thru magisk and still retaining root. Just unable to install any modules. Any help would be most appreciated. Thanks!
[Magisk] DodoGTA:
Do you have this error when flashing modules in TWRP? If yes, then attach recovery.log
[Magisk] weaver11b:
No, TWRP won't load on the pixel 2 xl 8.0 November security patch. I just find it weird that it worked initially with no issues, able to install a couple modules, and then all of a sudden I get these errors.
[Magisk] DodoGTA:
I removed all traces of SuperSU from the boot image and attached it to this post (Extract it and flash it in TWRP)

DISCLAIMER

I'm not responsible for any issues that you might encounter after flashing this boot image
[Magisk] หนึ่งเดฟ:
11
[Magisk] DodoGTA:
What?
[Magisk] Didgeridoohan:
Well, the magisk_debug.log from after installing a "bad" module and rebooting, on a previously working setup would be nice. That, or since you say there's no debug log, a logcat from the same reboot.
[Magisk] jackulus:
Hi, I've got a question about impact of Google Play Store certification status on SN check. I've got a Huawei device (PRA-LX1), I've checked general directions from the [GUIDE] thread and at this point don't know why SN check doesn't pass. Magisk hide is working (checked on Root Checker), come modules too (V4A). I'm thinking of "uncertified" status in GPS options - could this be a reason ?

Here is my Magisk log:

https://pastebin.com/BZbSfKFz
[Magisk] beavis5706:
OK I went from working Magisk state, install Greenify4Magisk module via magisk manager and reboot into non working state. Im not too keen on logcats so I wasn't sure how long to let it go for. I let it run for about 10 minutes.

This problem only occurs when installing modules via magisk manager. Installing via TWRP works for all modules I've tested so far.
[Magisk] Didgeridoohan:
Your log doesn't have anything about MagiskHide at all. Is that the whole log? Huawei devices are known to disable a bunch of logging that MagiskHide needs. Look around your device's forums how to do that.

The Play Store uncertified status is not the cause of SafetyNet failing. It's a result of it...

The logcat would need to start recording as soon as your boot animation starts. Doesn't look like the one you've posted is from during boot.

The Magisk log is interesting, although quite empty. Does it always look like that or just when experiencing the issue?

Since it happens with the Manager only, a logcat saved during installing a module would also be interesting.
[Magisk] Veid71:
so as silly as it seems i somehow got it working by installing 14.2 instead of 14.3 or 14.0, i have no idea why it doesnt like 14.3but for whatever reason it didnt thank you for all the help you guys
[Magisk] kepetmania:
MagiskHide not working

Hi, this is my first post. so I'm sorry if I made some newbie mistakes. :D

I have lenovo a6000+ with android 5.0.2 and I've already installed magisk, but I think magiskhide is not working in my device cause when I check some app to be hidden and exit magiskhide then entering magiskhide again, it can not load the app and just loading endlessly. I've tried every troubleshooting method from magisk guide thread but nothing works, is anyone ever face the same problem as mine ? is there any solution to my problem ?

Thanks
[Magisk] Didgeridoohan:
That's... odd. Don't know if you'd dare you try, but what would happen if you now update to 14.3?

Logs would be nice. The magisk_debug.log that you'll find in /data should be enough, but the Magisk log you can save through the Manager might show something as well.
[Magisk] Krendelrus:
Thanks a lot DodoGTA! Magisk is now up and running on my One M8 (had some issues with MagiskSU at first but it's working good now)
[Magisk] y2klol:
Added log

Samsung A5 2017 (SM-A520F).

2017-10-31 Australia (Optus) 7.0 A520FXXS2BQJ1 A520FOPS2BQI1

Magisk 14.3

I installed magisk no problem and it passed the safetynet check (5-6 days ago). Poweramp went to check that I had a valid license and it kept returning an error. I checked magisk and now it no longer passes the safetynet. I recently download and installed ExSDCard module, so maybe that did something.
[Magisk] Phorze:
Can support for RK3288 (and possibly more) be added? Here's the incompatible image, tested with 14.3

https://drive.google.com/file/d/1Khz8dJM7tuLJktF7t0OLTqigPjIWo1t8
[Magisk] casouzaj:
Android 5.1 samtwatch

I have an old NO.1 D6 smartwatch, running Android 5.1. I tried Magisk v14.3, but Magisk Manager simply quits a couple of seconds after I try to download the proprietary software required to perform the SafetyNet tests. Only its icon remains in the apps drawer, for what I have to install Magisk through TWRP again. I tried the old v14.0 installer. Its associated Magisk Manager doesn't quit when the Safetynet popup windows comes up, but I'm unable to download the proprietary software, because the button to allow it, in that popup screen, is not visible in my watch's tiny square screen. The popup window slides a couple of pixels up and down, but the button doesn't come up. Any hints?
[Magisk] milomak:
Gave it a bash and I am able to hide Magisk from a Good for Enterprise
[Magisk] vettejock99:
I'd love to understand this as well. Most of my phones (Moto/LG) have guides that say to flash the no-verity-opt-encrypt type files, but I've been skipping that lately as I understood Magisk identifies and handles that fine. It's caused no problems I can tell, but I would feel better if someone can confirm flashing no-verity is usually not required anymore with Magisk.
[Magisk] beardymarrow:
Yes, magisk disables forced encryption and dm-verity, by default. You can choose to re enable them, but I'm not sure why anyone would need to.
[Magisk] Dodgexander:
I also have this problem, is there any way to get to the bottom of this?
[Magisk] Nikolaevich:
I have an issue with SafetyNet, it's just broken, and I try to repare it with the Universal SafetyNet Fix module, but is just the same, I'm using a LAOS 14.1 custom ROM with the magisk as system app in version 14.0, also magisk hide is active, any idea what I can do?
[Magisk] rockenx:
Hello guys i have a issue persist ,i used magisk latest on my One plus 2 device,i want to use netwrok spoofer application which is required root permission but it can't detect my magisk su so it says device it unrooted,

i found there is option in network spoofer app where i need to put su path to run this application,

so please tell me the magisk su path ...whic is need to run this application...