yashsingh1/xdaforums huggingface dataset:
[Magisk] demonoidmaster:
/data/app is where any user installed apps are, it's also where the play store, play services, etc will install an updated version of itself if there is one and use that instead of your system based one

---------- Post added at 03:29 AM ---------- Previous post was at 03:24 AM ----------

This is why devs who build roms shouldn't embed magisk inside the rom zip, if they stop updating their rom there's no point in having magisk in it vs simply linking the magisk dl thread to it instead

Besides magisk uses addon.d, if a rom post-install flashes magisk while the magisk script is already present in addon.d (either via normal magisk install or if you're updating your rom to a newer build), it'll fail to flash the boot img (hence why ever since topjohnwu introduced addon.d support in magisk, there is no need to add magisk to roms)

Also the fact that since roms that have magisk in it will put magisk manager in /system instead of how magisk installs itself in /data/app

---------- Post added at 03:46 AM ---------- Previous post was at 03:29 AM ----------

My advice, whatever rom you're using has magisk embedded in the zip, so just saying but to avoid any issues whenever you download an update to your rom, open up the zip file with Winrar (on android) and delete the folder called Magisk then press save it'll auto rezip the zip, do this for any future rom updates before you flash it.

After you're done download magisk zip from the main thread, wipe your /system and reinstall your rom using the fixed zip that doesn't have magisk in it, then mount /system, delete the magisk apk like you did already, then flash magisk the normal way

The issue with embedding magisk into a rom is that some devs forget that magisk now has an addon.d script , they don't remove the folder from the magisk zip before they put it inside their rom builds and because of it this happens

(If rom was installed once) Rom flash, finishes, then installs magisk, rom zip install is complete, then the addon.d script kicks in, trying to install magisk right after magisk was just flashed, which then ends up just failing, can't flash boot img, which then basically screws up your magisk install and device goes into bootloop (unless you do what i said in my fix above, always remove magisk from an rom that has it in them unless the rom builder specifies that he removes the magisk addon.d script from his rom builds)
[Magisk] bluenote73:
On my Axon 7 Magisk 15.3 passes safety net check, but 16, 16.1 and latest provides root but does not pass the safety net check.
[Magisk] Jaymin.0.1910:
You can use Terminal App Systemizer by [MENTION=7296895]veez21[/MENTION]
[Magisk] vMAC:
https://xdaforums.com/showthread.php?p=75722060#post75722060
[Magisk] NLBeev:
That shouldn't when embedded in another zip....
[Magisk] rnadomuc:
What apps are 'Magisk-aware' and are able to do things like uninstall system apps or otherwise manipulate the system folder?
[Magisk] gothicVI:
Terminal emulator, the file manager "mixplorer", adb, apps2sd

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[Magisk] Artim_96:
Well, the point of Magisk is to never actually change /system. You can simply search the system apps folder and file name and use Magisk to replace it with a random file.

Other than that, a terminal emulator is pretty much the only thing. If you want or apps to be able to write to /system, you need to mount it as rw in terminal. But that can lead to problems on devices shipped with Android 6.0+, that's why there is Magisk
[Magisk] Markeee:
Having a magisk issue I keep getting a theirs a magisk update available then it uninstalls magisk

it gives me the option to install from zip or patch image both don't work and i have to open twrp and reflash

This happened whether I'm running 1600 or 1610
[Magisk] der_Kief:
after testing a bit more i found out that the problems start as soon as i install fbind module

All the other moduules are OK.
[Magisk] Ibuprophen:
I've got a simple/quick question for those Magisk experts here... :rolleyes:

Quick Note: This question is not for me specifically but, just to understand something based upon another members question that got me curious.

First of all, the member has a Custom ROM installed that included it being pre-rooted with Magisk.

The question is...

If that member wanted to install XPosed, does having Magisk root require having to use Magisk XPosed?

I've got a limited working knowledge of Magisk (because it affects 2 of my developments) and I had thought that the above question was true because of Magisk's "Pseudo" way for handling Root, Xposed and SELinux (just to name a few).

Thank you all very much for your time and assistance with this clarification.

I only asked within this thread since it covered a few Magisk topics and didn't want to do a spam-like way of asking on multiple threads.

~~~~~~~~~~~~~~~

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[Magisk] dismembered3po:
Has there been any more on adding a PIN for granting SU access?

I'm about to hand off my current rooted phone to my wife, and. . .well, she has no idea. I'd like to keep that phone rooted, but keep her from accidentally granting root to something she shouldn't. I still would like to have this feature for myself in general, as well.
[Magisk] jenslody:
For the moment you can go to the managers settings and switch the default behaviour to deny root access.
[Magisk] Didgeridoohan:
There's nothing "pseudo" about the way Magisk handles root (or SELinux)... It grants superuser requests just like any root solution and works perfectly fine with regular Xposed.

You might be thinking of Magisk modules, that can alter /system or /vendor through a systemless inteface that doesn't touch the actual partitions. They're another part of Magisk... Check out the official docs. They're a pretty good read if you want to know how Magisk works.

Currently there's only fingerprint authentication for superuser access. As far as I know, implementing any other kind of PIN is not a priority at the moment. If you're worried you can just change "Automatic Response" in the Manager settings to "Deny". All apps that already have root access will still work, but any new requests will be automatically denied.
[Magisk] rnadomuc:
The poster above you recommended a couple apps that'll work. I gotta **** with the system's camera files.
[Magisk] dismembered3po:
Ahh. I forgot about that. That will still keep the existing permissions, I guess.
[Magisk] KageyamaOuda:
MagiskHide problems

Hello, I've just rooted my phone with Magisk and I'm having some trouble getting Magisk Hide to work. Every time I select an app to hide, then go back to another menu or exit the program, it's unselected as soon as I come back and the hide function doesn't work at all. I've tried reflashing the stock ROM and redoing the entire process of flashing the custom recovery (TWRP) then Magisk once again but nothing seems to work, and the phone does have root privileges as far as I could test.

While searching about it, I saw that some Motorola devices shipped with a faulty f2fs implementation or something that caused this problem. My cell phone, however, is not a Motorola device. It's a Samsung Galaxy J5 (2015), the exact model being J500M/DS. It's currently running Lollipop 6.0.1. Could anyone help me with this?
[Magisk] s.i.t.h.l.o.r.d:
Folks, I need your advice.

I have installed iYTBP as a Magisk module on my OnePlus 5 running the official OxygenOS 5.0.4 with stock recovery but Magisk root.

Still, either using the regular Youtube app or YouTube through the browser (Chrome, Firefox Focus,...), I cannot get background playback to work. What, apart from the Magisk module itself is there to do?
[Magisk] Wolfcity:
The f2fs loopback bug should not be your problem, it's in fact a problem between kernel and the f2fs formatted data partition so that the device isn't able to mount img files r/w. In almost all cases you are not able to install any modules then, magisk itself works.

I had a similar problem with magisk hide, everytime I removed magisk from recents the hide button toggled to off again. The problem solved itself, after several times of toggling back to on before and after reboots the setting stayed on. But I have to say that magisk hide was working normally when toggled to on.
[Magisk] Ibuprophen:
Thank you very much for your for your response! :thumbup:

I just wanted to be sure of this because I would HATE to state something misleading/incorrect to another member if I wasn't sure myself first.

~~~~~~~~~~~~~~~

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[Magisk] vavix:
For those who havve trouble hiding Chase Pay from root.

1. Make sure all checkmarks are green in SafetyNet

2. In settings, hide Magisk Manager

3. Clear Chase Pay data and cache

4. Log in again
[Magisk] Markeee:
Bump up for some advice ?
[Magisk] linux.alucard:
Not working on my device :(

RR6/mido
[Magisk] vavix:
some more info: I am on Pixel 2 XL and latest 8.1 build. if you have the Chase Banking app also, hide magisk from it as well.
[Magisk] KageyamaOuda:
I've been able to install modules without much problem, but Magisk Hide doesn't work when I check any of the applications that shoud be hidden even if I just put it on background, and then the box unchecks itself whenever I either update the list, select another option on the menu or close the program. I tried toggling it to on several times to no avail, and even rebooting the cell phone every time I did it a couple of times. Root Checker Basic still says I'm on root.

Strangely enough, I also haven't been able to remove Samsung bloatware easily. Titanium Backup supposedly removes them when I select to uninstall them but their icons remain on the menu and they come back to the list on Titanium Backup itself once I reboot the cell phone, Root App Deleter gives me a warning that I should root my phone even tough it's already rooted, and NoBloat seems to remove them at first glance but as soon as I close and reopen the app they're there again. Unsure if my phone is not properly rooted (even though Root Checker says it is) or if the bloatware is reinstalling itself.

I've already flashed the stock ROM then rerooted about two times and I might do it a third if needed but this problem is really making me pull my hair out. If anyone knows a fix, it would be greatly appreciated.
[Magisk] darkvoid_66:
Hi,

I've installed a ROM to my S6 that comes with Magisk version 14.2 and manager 5.3.5.

I'm getting notifications to update Magisk. I try to update: I press "Update Magisk Manager" I get a dialog "Do you want to install MagiskManager-v5.6.2.apk now?"

I press install, but nothing happens. No error, no message , no update.

Why can I fix this?
[Magisk] Didgeridoohan:
Providing a Magisk log is usually a good idea. Also take a look in /sbin/.core/img/.core if there's a file called hidelist and if it's writable. If not, create one.

About removing bloatware: your best option is using something like the terminal debloater. Magisk mounts a "mask" over your regular system partition and leaves your regular partition untouched. That's likely why apps return on a reboot.

---------- Post added at 11:06 ---------- Previous post was at 11:02 ----------

Start by asking your ROM creator to not include Magisk in the ROM. If they've added the Manager as a system app, this kind of stuff can happen, for example...

You can try to uninstall Magisk and the Manager and then install again.
[Magisk] linux.alucard:
Resurrection Remix 6 Oreo droid 8.1

Latest stable magisk 16

OTP Smart Bank app
[Magisk] JamesCaywood:
[IMG="magisk safetynet error ?"]http://i66.tinypic.com/xp3nty.png[/IMG]

Anyone got an ideal to fix this on nexus 6p android 6.0
[Magisk] Didgeridoohan:
Android 6.0!? Move with the times dude... :laugh:

Could be a number of things... If both fail I've found it's usually because of Xposed, or that you simply need to toggle MagiskHide off and on. More info on how to get MagiskHide to work here:

https://www.didgeridoohan.com/magisk

Likely culprits:

USB/ADB debugging

Developer options

Prop values in build.prop and default.prop (not the values loaded by MagiskHide, but the ones written in the file).

Other modifications on your device that Magisk can't hide.

More info:

https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot
[Magisk] Homeboy76:
Deleted :rolleyes:
[Magisk] NLBeev:
Nexus 6, unencrypted, Beltz 180314, pico openGapps.

Dirty flash over previous rom-version.

Reflash Magisk 1600. No issues, substratum themes kept.
[Magisk] linux.alucard:
Magisk log (otpdirekt)
[Magisk] JamesCaywood:
Okay ha I'd update but I don't have a laptop on me at this time I do have xpose but says it can't hide it and I don't wanna deleted I use it so I guess I don't need safety nets probably useless anyway lol
[Magisk] tsongming:
Boot into recovery and flash Magisk 16.1, and the issue will likely disappear.
[Magisk] Didgeridoohan:
Yeah, you've got the usual suspects of prop values in there (ro.build.type=userdebug, ro.build.tags=test-keys, ro.build.selinux=1). So if the app look for the file values, rather than the values loaded by MagiskHide, that might trigger it. There's also default.prop where the common triggering props are ro.debuggable=1 and ro.secure=0.

Uhm... Read again... He's got Xposed installed, reflashing Magisk won't help with that. SafetyNet will trigger...
[Magisk] prabs99:
I have hidden Magisk Manager and both Chase apps. Safetyney passed but Chase Pay recognizes the root.
[Magisk] vavix:
You may need to take some additional hiding steps. Check the magisk website hiding guide.
[Magisk] linux.alucard:
default.prop

ro.debuggable=1
ro.secure=1

Change the ro.secure=1 value to 0?
[Magisk] Didgeridoohan:
No. All the values I posted are triggering values. If you see those, they might need to be changed to "safe" values instead (0 -> 1, 1 -> 0, userdebug -> user, test-keys -> release-keys). To keep things systemless you'd need to do the build.prop edits with a Magisk module and any changes to default.prop will be reset on each reboot, so a boot script editing the file would be preferable.

Edit: Just to clarify, I have no idea if this will actually help. It's just one way that some apps detect a "rooted" device.
[Magisk] BigMatza:
Magisk Manager forgetting su permissions and preferences

Just upgraded from 14.2 to 16.0 (used TWRP uninstall/install method). Already had Magisk Manager 5.6.2 installed. After reboot, I installed it again for good measure. Apps requested su via toast prompts as if it was their first time. I dismissed that because of the Magisk upgrade. But after every subsequent reboot it happens all over again. Also, I noticed Manager defaults to its default prefs after reboot as well (fingerprint disabled, which I enable each time).

This is a first for me. Anyone else having this issue? How best to fix it?

Thanks!
[Magisk] Artim_96:
If you uninstalled Magisk and deny them root rights they'll all again every time since there is no ignore option in Magisk yet.

But if you mean it forgets your settings I think there is something wrong with your manager installation. Besides the fact that XPosed is the only tool I know of that let you install an app on s version that's already installed, if just uninstall it and install it again, maybe wipe cache and dalvik in-between.
[Magisk] Didgeridoohan:
As stated above, I believe a reinstall is in order. I just want to add that it's good to use the in-app uninstall feature (Uninstall - Uninstall App). After that you can reinstall the Manager (download the latest apk from the release thread).

If it still doesn't work after that, logs, logs, logs.
[Magisk] Markeee:
Magisk issue help needed

Running 1610 on Nephilim rom on a Nexus 6

I keep getting a popup saying

Magisk upgrade available magisk won't auto install the update looses root

Then I'm forced to re-flash in Twrp
[Magisk] demonoidmaster:
You didn't read what I said before did you? I said a prior dev who added magisk to his rom didn't remove addon.d magisk script from the magisk zip inside the rom zip
[Magisk] smartymcfly:
I was hoping someone can take a peek the following android system.img from a pixelbook to see if it there is anything I can try to get magisk running on it.

Android v 7.1.1

https://mega.nz/#!lE523CyK!O8KpCOrg67qnn5iB5CmufEL9msRLuUepz6swP3sk29E

If there is anything else I can do to help I will.
[Magisk] NLBeev:
Read it now. Sorry..
[Magisk] NLBeev:
Deleted
[Magisk] Didgeridoohan:
The system image is irrelevant. Magisk patches the boot image...

Start by letting the Manager patch the boot image (check the release thread for instructions). If that works without issues (upload an installation log if you're unsure) you can flash the patched image to your device. If that works, you're good to go. If it doesn't, all you have to do is to flash your stock boot image and the device should boot up fine.
[Magisk] semail00:
Hello,

greetings to all and thanks to the authors of this fantastic application.

I would like to install Magisk on my MI MIX 2 ( with rom Xiaomi EU oreo 8.3.8 ) but I would like to ask you or who can give me this information: once installed Magisk can cause interference or problems for payments with credit card applications or bank applications?

Thanks and Rgds
[Magisk] Artim_96:
Of course it can, depending on the detection methods of the banking apps. If they have methods to detect root that are more advanced than what Magisk can circumvent they'll stop working
[Magisk] BigMatza:
Appreciate the tip. Indeed I've already tried the complete uninstall/reinstall, via both recovery, and via Manager. I feel like I've tried every permutation possible (e.g uninstall/reinstall from TWRP with and without reboot between, via Manager, with another reboot before adding modules to see if that helps, not re-installing systemless Xposed, etc). I did notice a few more issues though:

I was also on Manager 5.3.5. If I upgrade to 5.6.2, and leave Magisk 14.2 as-is, the modules disappear from the list, and I get install errors on any attempts to reinstall them.

The "forgetfulness" of SU/prefs seems to be related to upgrading from 14.2 to 16.0 or 16.1. I have not yet tried 15. I may try 15, just to get the additional modules it offers.

Manager 5.6.2 DOES remember the MODULES, and lets me install new ones, but ONLY if I'm using 16.0. As stated above, Manager 5.6.2 does not appear to be compatible with 14.2.. at least on my phone (Axon 7).

I'll look into getting some logs uploaded if I can't figure it out on my own before then. FYI, I'm on the latest stock for the ZTE Axon 7.
[Magisk] smartymcfly:
Right. I sort of underatood that prior to posting it.

I was hoping someone knew where to look (what file) in tht system.image, that says where the boot image is at? Something I do not know.

SuperSU can be used to root, I was hoping Magisk could also be used. But there the automatic patvhes done by magisk manager do not work as is on pixelbook.
[Magisk] jenslody:
Logs ?

Self installed MagiskManager or pre-installed by the rom ?
[Magisk] semail00:
Thanks to your reply.

Is there a module to be activated to evade/hide Magisk for these applications or are there settings to be activated during installation?

Rgds
[Magisk] Artim_96:
It's all explained in the documentation. Plus the app is quite self explaining
[Magisk] BigMatza:
I've spent hours of trial-and-error today, and have some exciting new results on the SU/prefs forgetfulness issue. Take as a given that all of these trials were installed via recovery, by installing the uninstaller zip (latest one), and then installing the desired Magisk zip.

All versions through 15.3 work properly on my device. Note that I did not test 15.1 specifically because of the known dm-verity bug, which is a non-factor anyway.

16.0 is the first Magisk release that causes the SU/prefs to not be retained across a reboot. I was unable to effectively test 15.4 because the MagiskManager kept force-closing.

The issue appears to be related specifically to MagiskManager. v5.5.5, which comes with release 15.3, works fine. But if I upgrade the manager to v5.6.1, the issue starts upon the next reboot. I did not try v5.6.0, for the same reason I gave up on testing release 15.4.

About the issue itself, and contrary to my initial impression: The app prefs and SU statuses are not wiped completely on reboot. They are simply set back to the last saved state. I was able to confirm this by having SU statuses under v5.5.5. Then, after the upgrade to v5.6.1 (and reboot, for good measure), I added a new SU status, and removed an existing one. After another reboot, it was as it was before those two changes.

That's all I have for now. I'll be staying on 15.3/v5.5.5 until the issue gets worked out. I'll play around with it some more, once I figure out what logs I need to provide.
[Magisk] madbat99:
The settings are in magisk manager itself. You see them after installation. They are magisk hide. They work on some banking apps, not all. No there is not a list of working and not working. You just have to try it and see.
[Magisk] YoshiFan501:
I cannot install any modules at all on my pixel 2 xl all of the sudden. im getting an error on

/data/adb/magisk_merge.img to /dev/tmp/magisk_img

! /data/adb/magisk_merge.img mount failed

and i cant install the f2fs fix because theres no cache partition detected in twrp
[Magisk] martyfender:
Forgive me if I am wrong, but I thought the pixel 2 xl uses the ext4 file system, not f2fs.
[Magisk] YoshiFan501:
i checked and yea you're right on that. but i still dont know how to fix the issue sadly :(
[Magisk] yubimusubi:
Has anyone had problems with Animal Crossing Pocket Camp in the past day or two? I'm wondering if they changed detection because of the tournament...

Magisk Hide is set and Magisk is hidden - Chase Pay and Pokémon Go both work. I've tried core only mode, disabling developer tools, and removing"root" apps like Titanium Backup. The latest Pocket Camp app update was 3/6 but it stopped working for me within the past 24 hours or so.
[Magisk] Jaymin.0.1910:
Try, rebooting, it is likely to fix it
[Magisk] IBNobody:
I'm having the old "Magisk Hide Checkboxes won't stick" issue on my Sprint Galaxy Note 4 (910P). I am running fresh stock, latest FW (6.0.1/QI5). I am on Magisk 16.1 beta but saw the issue on 16.0.

Navigating to /magisk and /magisk/.core show these folders as empty. I tried creating a hidelist file, but that did not help.

I know this is solvable because there is a stock-ish rom /w stock kernel for the Sprint Note 4 with this all working.

Logcat: https://drive.google.com/file/d/1hN7cWds8EpUKA7TQJCUYydkblpzpa4TA/view?usp=sharing

Device Info: https://pastebin.com/ncWtnwU4

(I attempted to try the beta just for the debug logs according to Didgeridoohan's site, but I didn't see a debug log in /data/adb. And, of course, my MagiskManager "Magisk log" is empty.)
[Magisk] jak_drizzt:
Magisk and Sky Go IT

Hi, Jacopo from Italy.

Is it reasonable to ask here help for hiding from a specific app? (if not, where may i ask?)

I'm on a Samsung S8. Installed magisk from twrp, stock rom. Never installed xposed or busybox, no magisk module, magisk manager hidden.

Magiskhide works with everything (safetynet ok) except that damn sky go app. You can find it on apkmirror as "sky go per smartphone IT" v2.0.8.

How do they detect root? Is there any one that found a way around it or has any idea on what else to try?

Btw the sky go Q app, on the contrary, does works but unfortunately they block it if you use screen mirroring or use an hdmi.
[Magisk] beardymarrow:
Hide magisk manager and it'll work.
[Magisk] jak_drizzt:
Already tried

Maybe i've not explained it well but i've already hidden magisk manager but it still doesn't work :(

---------- Post added at 10:32 AM ---------- Previous post was at 10:28 AM ----------

Well, to be precise, the app opens and lets me see only skytg24. If i try to watch any other channels it gives you me the error 10088. And in various forums that error is associated with root detection