yashsingh1/xdaforums huggingface dataset:
[Magisk] martyfender:
Usually system apps are installed in /system/priv-app.

There are some apps in the playstore that can convert a system app to a user app.

I use Apps2sd to move apps to a second, ext partition on my external SD card, but it has the feature to uninstall system apps and also to convert system apps to user apps and user apps to system apps. I have only used it to uninstall some apps I don't use, Google apps, that aren't system critical like Google Books, etc.
[Magisk] Didgeridoohan:
No need to uninstall anything, except for the troublesome modules, that is.

As long as you have access to TWRP (installed or just booting) you can easily uninstall modules. Take a look here for details:

https://www.didgeridoohan.com/magis...agisk_functionality_bootloop_loss_of_root_etc
[Magisk] jugoslavpetrovic:
Thanks, it booted somehow after hard reboot.

I will take a look at that link.
[Magisk] topstarnec:
Please have a look the attachment log file

Magisk 16 and 16.4 can't install on official lineage os 15.1 for MIDO (Xiaomi Redmi note4)

It said /vendor can't be mounted.

Thanks.
[Magisk] BillGoss:
See https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post76674961
[Magisk] shanishkag:
guys can you tell me how to install magisk through Odin i read the thread From original i cant get it correctly.. please simply explain to me to install.. im trying to install to s7 edge 8.0 without custom recovery
[Magisk] Didgeridoohan:
https://xdaforums.com/search/forum/5903?query=Mido mount vendor
[Magisk] debby_:
After upgrading LineageOS 15.1 to 20180528 on my cheeseburger (OnePlus 5), the device always boots into fastboot. When restoring the non-Magisk boot image in TWRP, everything is fine again. As soon as I install Magisk (v16.0 or v16.4), the phone only boots into fastboot mode.

It seems nobody else wrote about this so far?! Who has similar issues or know the cause of this?

+1
[Magisk] gothicVI:
There basically is a step for step explanation in op. So where exactly does is not work for you? Try to be more specific on what your issue is and what you did exactly.

Gesendet von meinem Moto G (5) Plus mit Tapatalk
[Magisk] shanishkag:
i just installed Oreo 8.0 this time i want to root without custom recovery. so i have the md5 file in my pc how could i find boot img.? even i find in this files it says boot.img.lz4 so can i use this file to magist to patch boot image and fash through ordin ?
[Magisk] simo6:
With the latest Sky Q app, despite i have checked it on the magisk hide section, it stll recognize im rooted and doesn't work..

Any ideas?

OnePlus 5; Los 15.1; Magisk 16.4; Sky Go Q pr14.2.0-600

Inviato dal mio ONEPLUS A5000 utilizzando Tapatalk
[Magisk] jenslody:
Hide/repackage MagiskManager (see its settings), clear the data of the app and try again.
[Magisk] Cheewawit_T:
No, I used to have one, the unified host adblock but I uninstalled it. Maybe it's YouTube Vanced? The other modules i have are ram management by crok and crossbreeder lite edition and bellota font.
[Magisk] Tautvydas:
Hello,

Tried various things, but just can't get modules to appear after install.

I'm using Essential PH1 8.1 June (I've done my research on dedicated rooting thread there), but can't seem to find solution.

Busybox, magisk permissive 1.2, Sysconfig patcher modules installed just fine.

After that, I'm trying to install youtubeVanced, ainur sauron, and gcam module...And it installs without errors, but just doesn't appear after reboot.

Thing is, I've always flashed modules in that order, and everything worked fine (I've tried uninstalling them all, then reinstalling, didn't work).

Though YTVanced worked after installing zip with .plz. Just dunno.

I'm using 180611 build by kantjer, his builds seemed to work best with essential ph1. Never had problems until now.

Attaching logcat specifically during ainur sauron module install, magisk install log of ainur sauron module, and magisk debug

Thanks for help!
[Magisk] Didgeridoohan:
[MENTION=1871792]Tautvydas[/MENTION] Try without the YouTube Vanced module (uninstall it), or reinstall it through recovery. There seems to be an issue with the current code and installing large modules like that one from the Manager. It's on the bugs list...
[Magisk] Tautvydas:
Thank you sir!

But the log's is mostly specifically for ainur sauron module, which is 4.8MB, does it still apply as large module?

Maybe the most logical way would be to reverse to older build of magisk?
[Magisk] Didgeridoohan:
The Ainur installation looks fine, but in your debug log I'm seeing signs of an issue I was troubleshooting myself yesterday. Related to the Vanced module... And that module is 60+ MB so I don't think there's an issue with 4.8.

You could try reverting to an older build or install the modules through recovery instead. The latter worked fine for me until there's been a fix.
[Magisk] Tautvydas:
Thank you. Last thing, could you pinpoint me to older magisk build version which didn't have all these problems? Didn't save kantjer's build which was working for me fully, and he doesn't keep an archive.
[Magisk] Didgeridoohan:
Not really... I haven't made any tests to see where the issue started showing. [MENTION=3306843]kantjer[/MENTION] has a build from 2 June. You could try that I guess...
[Magisk] rn4Nlos:
From the user of Redmi Note 4 (mido) of Lineage OS 14.1 here, we need your update for the Lineage OS 15.1 cause treble support is needed.
[Magisk] Strephon Alkhalikoi:
Magisk 16.4 works perfectly on my Pixel 2 XL, which has Treble. What exactly is the issue?
[Magisk] Didgeridoohan:
I saw your post in the snapshot thread. Just wanted to clarify (and I'm posting here not to clutter up that thread), since I'm not sure you understood me from the start. It has nothing to do with the Ainur module...

If you still have the Youtube module installed, it is very likely that it's the borked installation of that module that is still causing issues, preventing scripts from running and files to mount... If you've uninstalled it and things are still not working, you have a completely different issue than I've been describing. But, your debug log did show that you have the Vanced module installed, so I'm fairly sure that you'll see an improvement if you either uninstall Youtube Vanced, or reinstall it from recovery. Forget about Ainur, it's the Youtube module that's messing with you. :good:
[Magisk] Tautvydas:
Sorry mate! By posting on snapshot thread I didn't mean any disrespect, just thought we had the same issue, and it would benefit us both by asking kantjer directly.

And you were absolutely right! After removing Youtube Vanced, ainur module installed properly, and, as you've said, only problem is with bigger modules - tried to install gcam module, which is almost 145MB, same issue as with vanced.

Thanks again!
[Magisk] MenyaMenye:
Hello, I'm using a custom rom (RR) bundled with outdated magisk manager installed as system app. How can i remove it and install magisk manager as user app?
[Magisk] Jimdevl:
17:47:03.273 308 308 I Magisk : * Creating /sbin overlay

06-12 17:47:03.274 308 308 I Magisk : * Mounting mirrors

06-12 17:47:03.275 308 308 I Magisk : mount: /sbin/.core/mirror/system

06-12 17:47:03.275 308 308 I Magisk : link: /sbin/.core/mirror/vendor

06-12 17:47:03.276 308 308 I Magisk : bind_mount: /sbin/.core/mirror/bin

06-12 17:47:03.276 308 308 I Magisk : * Setting up internal busybox

06-12 17:47:03.290 308 308 I Magisk : Magisk v16.0(1600) daemon started

06-12 17:47:03.292 308 316 I Magisk : ** post-fs mode running

06-12 17:47:04.145 308 344 I Magisk : ** post-fs-data mode running

06-12 18:47:04.146 308 344 I Magisk : * Mounting /data/adb/magisk.img

06-12 18:47:04.174 308 344 E Magisk : mount /dev/block/loop0->/sbin/.core/img failed with 13: Permission denied

06-12 18:47:04.174 308 344 E Magisk : umount /sbin/.core/img failed with 22: Invalid argument

06-12 18:47:04.217 308 344 E Magisk : mount /dev/block/loop0->/sbin/.core/img failed with 13: Permission denied

06-12 18:47:04.218 308 344 I Magisk : * Running post-fs-data.d scripts

06-12 18:47:04.218 308 344 I Magisk : * Running module post-fs-data scripts

06-12 18:47:04.218 308 344 I Magisk : * Loading modules

06-12 18:47:04.218 308 350 I Magisk : * Starting MagiskHide

06-12 18:47:04.218 308 350 I Magisk : hide_utils: Hiding sensitive props

06-12 18:47:04.219 308 350 E Magisk : fopen: /sbin/.core/img/.core/hidelist failed with 2: No such file or directory

06-12 18:47:04.219 308 350 I Magisk : hide_list add: [com.google.android.gms.unstable]

06-12 18:47:04.237 308 350 I Magisk : proc_monitor: init ns=mnt:[4026531840]

06-12 18:47:05.177 308 521 I Magisk : ** late_start service mode running

06-12 18:47:05.178 308 521 I Magisk : * Running service.d scripts

06-12 18:47:05.178 308 521 I Magisk : * Running module service scripts

06-12 18:47:06.953 308 350 I Magisk : proc_monitor: zygote ns=mnt:[4026533926] zygote64 ns=mnt:[4026533927]

06-12 18:47:38.462 308 350 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=3046 ns=mnt:[4026533996])

06-12 18:52:42.763 308 350 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=8051 ns=mnt:[4026533974])

06-12 18:55:01.866 8857 8857 I Magisk : Create /data/adb/magisk_merge.img with size 64M

06-12 18:55:01.987 8859 8859 E Magisk : mount /dev/block/loop1->/dev/tmp/magisk_img failed with 13: Permission denied
[Magisk] jenslody:
If you have TWRP it's quite easy:

first make sure you have uninstalled all updates of MagiskManager in "Settings -> apps",

boot into TWRP,

mount /system,

remove the "/system/{,priv-}app/MagiskManager" (or similar) folder,

reboot and install MagiskManager from announcement-thread.
[Magisk] cas239:
Having an issue with Magisk Hide settings not sticking. When I select a specific app in the list, then back out and go back in, the app in unselected.

I saw in a few threads about adding the hidelist file in /magisk/.core, but the file is there and set to 0644. I've even tried manually adding the app directory name to the file, with no success.

I do have Xposed installed (therefore SafetyNet fails), does that not allow Magisk Hide to work?
[Magisk] MenyaMenye:
I had thought about this, but wouldn't modify system partition via twrp breaks SafetyNet? Since magisk manager installed as system app??
[Magisk] Äptiva:
You need a kernel that supports gzip. I've managed to get it going on my d800 (trying to test on my vs980 as well) I have it running on my AT&T G2 with dorimanx using a modded ramdisk to remove his busybox. His busybox method doesn't allow this to work as intended and I was told "don't invent the wheel" so I guess I'll have to come up with a script to flash along side his kernel similar to the one blastagator used in the past.

G2 and G3 users for bump here is your method, but if your boot image isn't in gzip it will not work:

1. Flash your rom

2. Flash unSU script

3. Flash your kernel and pray it doesn't have busybox spidered into the ramrisk

4. Flash Magisk

5. Bump via script or use dd to pull, bump, and again dd to push the image. To the device

6. Flash the magisk su package of choice (phh's worked for me)

7. Boot and install the superuser app for your choice and Magisk Manager
[Magisk] alroger:
There isn't any CM13 specific instructions... With CM13 everything should be straight forward. There can be tips specific to your hardware or version of CM13, in case it's not the offial ROM.

The other user had trouble with multirom, another subject completly.
[Magisk] Äptiva:
A lot of people not able to pass safetynet checks is due to their roms having busybox installed in /system/xbin or /system/bin.

IMO since Magisk uses a built in busybox, it should check for a busybox install during installation and nuke it.
[Magisk] tdurdenn:
Can I use safestrap to flash my 5.0.1 s4 verizon rom with root and a nk4 bootloader, then run a unsu script, then run magisk installer and magisk su zip then boot into it or does it not support 4.4.2 bootloader?
[Magisk] Captain_Throwback:
That isn't Magisk's job....

The next version of Magisk won't interfere with current Busybox installs. However if having Busybox somewhere is breaking SafetyNet, it'll be up to the user to remove it, as passing SafetyNet isn't the intent behind Magisk (just a happy side effect).
[Magisk] helpme plze:
Plse help

I ve got galAxy note 1 GT1-N7000

It s been rooted with TEAM WIN RECOVERY 3.0.2.0

and nightowl-cm13-2016080807-n700 zip

open-gaggs-arm6.0mirco 20160910 zip

I have tryed to hide this with your magisk-v6 zip

Using the install zip with the above team win recovery project your file instals correct but on the reboot it just sits on the

samsung galAxy note 1 GT1-N7000

page i then can not do any thing with the phone until i run odin and a kernel to wipe the phone

PLSE help what am i doing wrong Pokemon go is awaiting LOL
[Magisk] -Happy Feet-:
I use an other device and Rom/kernel.

Currently magisk running on advanced stock kernel. When I change the kernel Magisk still running?
[Magisk] malte180684:
For me it helped to uninstall busybox with the busybox app from the playstore.

After that everything went fine.

I didn't reflash the kernel so it couldn't reinstall busybox.
[Magisk] Äptiva:
While I agree, it should be Magisk's duty to REPLACE the built in busybox if it's going to use it's own version. That's just my opinion
[Magisk] Mr. Zero:
Please help... I have a Sony D5503 Z1 Compact rooted, dual recovery with android 5.1.1... I Unroot and flash the zip of magisk, but my bootloader is locked, now the phone doesn't show anything, so I decided to flash stock rom with flashtool, everithing OK, but when the phone is loading start a infinite bootloop.... what happened??? is my phone hard bricked? any solution?? please help me.
[Magisk] Captain_Throwback:
My point is that with the next version, both Busyboxes will be able to coexist without issues, so there's no need for it to be replaced. Magisk will continue using its own Busybox with the additional features it requires, and the other apps can use the ROM's Busybox.
[Magisk] b00tstrap:
Here you go...It seems to work as far as I can tell; I don't have a Nexus 5 so I can't test the speakers. But it installs and works for headphones. Note: I included the ViPER4Android driver, since letting the app install a driver violates the idea of being "systemless".

Nexus 5 ONLY
[Magisk] benengyj:
Did flashing this lock your bootloader or did you try flashing this on a phone with a locked bootloader? OP clearly states "This mod requires boot image modification, so unlocked bootloaders are required!"
[Magisk] StrykZ:
Everything is working fine for me but when i run the safety net check it fails on the CTS profile match test

I hear it's due to busybox being installed in xbin and bin on custom roms (running n910u cm13)

Does anyone know how to fix?

Thanks
[Magisk] Mr. Zero:
I flashed on a locked bootloader, is there a solution??
[Magisk] Ovrclck:
It's also working for me. At first it wasn't working and kept asking for driver install. Turns out I forgot to set the Selinux Status to Permissive. :good:
[Magisk] feeelx:
Everything works fine except this one module: "MW Manager". I use this module on my Samsung note 4 to be able to open any app in windowed mode. When I open MW manager now, I get a message saying Xposed Framework Not Installed. I am currently using the xposed-v86 5-arm-alt-sdk23-topjohnwu.zip on my 6.0.1.

Any help is appreciated. Thank you
[Magisk] alroger:
Where do you get that idea? No App should mess with other apps files. Who installs it is responsible for removing it. Be the ROM dev, or the app creator. Imagine if you install something new on your Windows PC, and this app replaces other Apps files? It would be CAOS!... ohhh Wait! It is! hauahuahuahahha
[Magisk] trevorcobb:
getting android pay error message as of the past 2-3 days with Magisk v6, installed 100% per the directions, and last week worked perfectly with zero issues. I can still play pokemon go v0.37 and safetynet helper app lights up green across the board. what am I missing?
[Magisk] bumpaneer:
Awesome work! Thanks for the preview.
[Magisk] jcmm11:
No. I modify /system all the time. Magisk will allow you to pass safety net. The biggest issue with modifying /system is that it no longer allows a person to take OTAs, but that's not applicable with a custom ROM.

With a custom ROM you're already using a modified /system, at least in comparison to stock.
[Magisk] MenyaMenye:
Thanks both of you, it works without any problem, cheers ?
[Magisk] akashsriram:
I can't use systemless support for adblocker even I even I enable the feature it's not working in adaway
[Magisk] SimplyCity:
Hi there. I had same problems. It looks like iytb Vanced can't resize Magisk image properly.

So, there is a module, useful one, called Magisk manager for recovery mode - a life saver in that case. If you can, flash it. If not - remove Magisk with Uninstaller, flash it again and mm module as very first one. Then reboot to recovery and run mm from terminal - you will find how-to in module description. Then select resize Magisk img and let it be 128 or 192 MB. Reboot and just then flash iytb. It will install just fine.

If you find any other module, which is actually installing fine, but broken after restart, most probably is that resizing Magisk img part needs to be fixed. If so - use mm, it is really problem solver.

:)

Echoe[emoji769] team member / N8 Oreo powered by EchoeAEL[emoji768]
[Magisk] Tautvydas:
Will try that, thanks lad!
[Magisk] martyfender:
That has been answered, many, many times in the adaway thread. Usually, the check box is unchecked and greyed out, but actually working. Search the adaway thread where you will find a development version link that fixes that cosmetic issue. The link for that version is not in the op of that thread it ls a 4. Version.
[Magisk] simplepinoi177:
For future reference, Magisk has an uninstaller that is probably simpler (less likely to make a mistake) and more thorough....

It's clearly even in this release page....
[Magisk] Didgeridoohan:
Unfortunately the uninstaller is useless in a case when a ROM creator foolishly have included the Manager as a system app. It's not designed for it, since the Manager isn't supposed to be a system app.

And that user didn't want to uninstall Magisk, just make the Manager a user app again, as it's supposed to be...
[Magisk] liamolua:
Hey, I would of posted logs but couldn't due to anything root related was crashing due to Magisk crashing when being asked for permissions or opening the app entirely.

Update:

Everything is working again, installed beta after a complete wipe of the phone and I refresh repo somewhat regularly and no crashes whatsoever. :):)
[Magisk] Didgeridoohan:
Good to hear. For future reference, you don't need root to grab a logcat through ADB.
[Magisk] liamolua:
Sighs, I'm a fool for forgetting about ADB. :D:D.
[Magisk] Kamil.Blaha:
Uninstaller not working?

Hi, Didgeridoohan.

I'm experiencing issues with Magisk - sometimes after restart I have no root (Magisk Manager says that Magisk is not installed). Another reboot fixes this problem. I wonder if it could be wrong installation. But, when I try to flash "Magisk-uninstaller-20180429.zip" (or "Magisk-uninstaller-20180328.zip") I get the "ERROR: 1" "Unable to mount...". What is wrong? What will happen if I would try to "uninstall" from "Magisk Manager 5.7.0"?

Thanks for help.
[Magisk] Didgeridoohan:
The recovery log might show more about the error, but you should be fine uninstalling from the Manager.
[Magisk] MenyaMenye:
Exactly, i tried to use the Uninstaller but it was unable to remove the manager since it's a system app.

Not only that, by installing the manager as system app, the hide magisk manager feature will result 2 magisk icons in launcher.
[Magisk] Didgeridoohan:
Yes, that's precisely why the Manager shouldn't be a system app. It breaks one of the core root hiding features...
[Magisk] simplepinoi177:
I may be woefully out of my element here and may be talking out of my @$$ here, and I have big doubts that this would work; but have you guys tried/considered trying to use Titanium Backup and "convert" it to a "user app"? Would that even be feasible or worth it/trying?

I've just been following your guys' posts last couple of days and was doing some TB stuff and it merely stuck out of my head.....
[Magisk] jcmm11:
Might work. Theoretically it should. For me it would be easier to just delete the system folder along with any dalvik-cache entries, then install the APK. But that's me.
[Magisk] luan165:
Hello friends. I would like the help of you to solve a problem that occurs to me with the magisk 14.5+, all versions above that do not let me use xposed, when I install I get stuck in the boot screen, having to uninstall the magisk to return to normal. I use the asus live G500TG with android 5.1.
[Magisk] teddy0209:
Have you tried using the latest magisk with the version in the repo/download section?

If you have, then you need to provide more details/logs...
[Magisk] luan165:
What logs? Where can I get them if installing the new versions does not start the smartphone?
[Magisk] BuffMcBigHuge:
Device: One Plus 6 v5.1.6

Magisk: 5.7.0 (115)

Version: v16.4

I am trying to install Busybox and Dolby Atmos, they install fine, but I'm getting "Module will be updated at next reboot" after subsequent reboots. I have YouTube Vanced successfully installed and active from before. Logs showing no errors.

Edit: I ended up solving my issue by simply reinstalling the Magsik modules one at a time and rebooting.
[Magisk] Didgeridoohan:
https://www.didgeridoohan.com/magisk/Magisk#hn_Module_will_be_updated_at_next_reboot
[Magisk] davidzam:
Updating magisk 16 to 16.4 its not posible for me:

Log:

- Device platform: armeabi-v7a

- Extracting files

- Patch boot/ramdisk image: /dev/block/mmcblk0p9

boot_patch.sh: boot_patch.sh: ./util_functions.sh: line 15: grep: Permission denied

./util_functions.sh: line 15: grep: Permission denied

boot_patch.sh: ./util_functions.sh: line 15: ps: Permission denied

boot_patch.sh: ./util_functions.sh: line 16: grep: Permission denied

boot_patch.sh: ./util_functions.sh: line 16: grep: Permission denied

boot_patch.sh: ./util_functions.sh: line 17: id: Permission denied

boot_patch.sh: ./util_functions.sh: line 17: grep: Permission denied

boot_patch.sh: line 75: chmod: Permission denied

boot_patch.sh: line 78: ./magiskinit: Permission denied

- Unpacking boot image

boot_patch.sh: eval: line 1: ./magiskboot: Permission denied

boot_patch.sh: eval: line 1: ./magiskboot: Permission denied

boot_patch.sh: eval: line 1: ./magiskboot: Permission denied

boot_patch.sh: line 163: rm: Permission denied

boot_patch.sh: eval: line 1: ./magiskboot: Permission denied

- Checking ramdisk status

- Patching ramdisk

- Repacking boot image

! Unable to repack boot image!

Failed!

! Installation failed

Enviado desde mi SM-G550T1 mediante Tapatalk

---------- Post added at 07:07 PM ---------- Previous post was at 06:35 PM ----------

Must I install the zip file downloaded by the module via twrp?

Enviado desde mi SM-G550T1 mediante Tapatalk
[Magisk] simplepinoi177:
If you were on the Pixel 2, I would say you probably had to fastboot unlock and unlock_critical....

Yes, or at least this is what I do on my Pixel 2 (download the .zip file, boot into TWRP, and "install" it...)
[Magisk] davidzam:
Thanks simplepinoi, updated using twrp. :good:
[Magisk] simplepinoi177:
Glad to see you got it worked out! I'm finding a lot of users on the "taimen" subs having a lot of issues patching images and manually flashing and/or using the app vs. installing using the installation .zip in TWRP. Going about it that way mounts everything for you, backups and flashes everything for you, and unmounts for you -- hence less chance running into issues....:good::highfive:
[Magisk] Pkt_Lnt:
That ain't no Taiman! :)

Use the Taptalk sig to search by model = Samsung Galaxy On5 (Metro PCS) [SM-G550T1]

https://xdaforums.com/samsung-galaxy-on5