yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
This is pretty risky.

On some phones (Huawei, at least), you must have both OEM (=FRP) and Bootloader unlocked for Fastboot.

With only Bootliader unlocked but FRP locked, Fastboot flash commands will fail.

Hence, if anything goes terribly wrong and user could no more boot either to System (to unlock OEM) or to TWRP (to restore last working set-up), he will be in big trouble - it can still be resolved but it requires deep hacking methods and tools, usually including to buy help from one or two 'dark' services (they can practicaly unlock Factory Reset Protection and Bootloader on stolen phones where OEM and Bootlick were never unlocked, and System is protected with pin/password, and Google account was not removed).

Not a comfortable situation. .
[Magisk] Didgeridoohan:
Thanks for the info, did not know that. Huawei is not exactly doing vanilla Android though, so do you know if it's the same on Google devices and other OEMs that more closely follow Google's version of the OS?
[Magisk] zgfg:
No, I don't know - this is why I wrote "at least on Huawei", but you can try on your phone, lock OEM (keep Bootloader unlocked) and from Fastboot try to flashTWRP or patched boot/ramdisk image (something that will not change or mess up anything if it succeeds) and check if Fastboot reports success or failure

And yeah, Huawei has no vanilla Android :)
[Magisk] Soccerdad91016:
I have the same question.

I am running Magisk 19.3 (19300) on a Samsung Galaxy Tab S3. While I have flashed TWRP and Magisk to root the device, I am not using a custom ROM. Running Android 8.0.0 with Samsung Experience 9.0 and Kernel 3.18.71-15759240 security patch April 1, 2019.

Currently I'm able to install Maas360 (version 6.60 from the Play Store) and then flag it in MagiskHide but the setup fails when trying to create a "work partition", I get a message that my OS has been tampered with even though it's not a custom ROM.
[Magisk] Soccerdad91016:
Can you hide root from Maas360 MDM Application?

I am running Magisk 19.3 (19300) on a Samsung Galaxy Tab S3. While I have flashed TWRP and Magisk to root the device, I am not using a custom ROM. Running Android 8.0.0 with Samsung Experience 9.0 and Kernel 3.18.71-15759240 security patch April 1, 2019.

Currently I'm able to install Maas360 (version 6.60 from Play Store) and then flag it in MagiskHide but the setup fails when trying to create a "work profile" I get a message that "The security policy prevents the creation of a work profile because a custom OS has been installed on this device" even though it's not a custom ROM (see above)

Looking at the logs (see attached) and I don't see much of anything that would help troubleshoot just two lines pasted here for convenience, first line is after I hide the app. Second line is when I run the setup that eventually fails.

07-16 14:42:25.267 605 18346 I Magisk : hide_list add: [com.fiberlink.maas360.android.control/com.fiberlink.maas360.android.control]

07-16 14:42:56.060 605 905 I Magisk : proc_monitor: [com.fiberlink.maas360.android.control] PID=[18513] UID=[10072]

Any help greatly appreciated. Though not the worst thing if I can't get work email on the device ;)
[Magisk] Soccerdad91016:
Adding a more detailed log file. This is after I enabled Improved Hiding using the HideMagisk Props Config module. I get the same result, even after a reboot.
[Magisk] foosoomin:
hi threadstarter developer,

I own a HTC U11 with Android 7.1.1

I just need to unlock bootloader, then flash TWRP, then flash Magisk 19.3 ?

Please enlighten :)
[Magisk] Ingan121:
It uses Knox, and it cannot be bypassed at all. However, you can switch to ROMs that don't include Knox. (like AOSP based ROMs)
[Magisk] JudgeDread11:
How to root your device is better and in your device thread. Different devices might require different procedures.
[Magisk] Syoenth:
Do you know if this issue happens on all Samsung recent devices or only this particular model?
[Magisk] zgfg:
Bug with blank Downloads was already fixed in Magisk Manager Canary build (latest MM Canary is v7.3.3 (228))

If you wish, google for XDA Magisk Canary and find the installation link and instructions in its OP post #1

Be aware that Canary channel provides pre-release builds (both for Magisk and MM), but many people use it (me too) because they are usually stable and it faster provides builds for bugs that are already fixed in the Magisk/MM Git source

In fact, you can only install MM Canary, and then switch in its Settings to Stable channel, and keep using the latest stable/official Magisk v19.3 (latest Magisk Canary is v19.4)
[Magisk] andy356:
Thanks! That's all I needed to know. :) I'll wait for the next update, no problem.
[Magisk] Johnn78:
What is the difference between Magisk & Magisk Canary ?
[Magisk] dope77:
flashing magisk on these devices breaks locksreen and samsung account

currently known devices are j6+ ,j4+

and probably the note 9 according to this : https://github.com/topjohnwu/Magisk/issues/1344

and check this: https://github.com/topjohnwu/Magisk/issues/1617
[Magisk] NoFear1183:
Could something be monitoring the ptrace status of zygote to determine if magisk is installed or not?

Before the implementation of Magisk hide using Zygote method, that PID remained open. Now with new method for hiding, Zygote PID is now being ptraced. So, an app simply checking Zygote ptrace status, could be enough to determine if Magisk is installed.

My thought is, is this how Netflix is detecting irregularities in system even while passing Safetynet?
[Magisk] davejimson:
Pls add dual sound mod :)
[Magisk] RandomPooka:
I'm not sure what developer you might need to ask about that, but this is the wrong place for module requests
[Magisk] aamnahid:
I got an issue with magiskhide.

When i'm going to open western union app in my samsung s5 (custom rom RR 7.0.2), its just close & saying rooted device. Even though i already used magiskhide...!
[Magisk] zgfg:
It has been discussed a lot/often in previous posts about some apps still detecting root although MagiskHide enforced (and SafetyNet passing)

You may try by hiding/repacking Magisk Manager (see its Settings), if it helps (some apps look for MM to proclaim that phone is rooted)

Search also fo discussions about RootBeer in this thread (app is available on Playstore, it explores various methods to detect root, and presents its results) and which steps are needed to successfully hide Magisk from RootBeer. RootBeer is an open source library, and other apps may include it to check if phone is rooted (maybe yours, too)
[Magisk] Didgeridoohan:
And apart from the above, you can find some further tips for hiding root here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] bhiga:
If you're using Magisk 19.3, try downgrading to Magisk 19.2 - I don't know why, but on my phone there's a difference. Toreba gives Connection Error -1103 on 19.3, but on 19.2 it's happy.

LATE EDIT: Disregard. Magisk 19.3's MagiskHide works fine - just needed to disable and re-enable MagiskHide after updating to 19.3 as Didgeridoohan's tips noted.
[Magisk] myjess:
Post deleted by me, cos I am stoopid

Who knew the phone had to be factory reset and blank to be able to install magisk.
[Magisk] duh1:
Appreciate the guess, and your consideration of this ongoing issue. When I turned off the option, a message came up making a positive reference to securing the device and now requiring a reboot to complete the action. Never saw that before on a developer option, and am hoping the reboot won't wipe the device or lose root, or make any other unwanted changes, or is that not possible...
[Magisk] Didgeridoohan:
It won't wipe the device. But you should of course always have a backup of any important data so you should be fine...

Did it have any effect?

Edit: to clarify, what is referenced is FRP (factory reset protection). If I remember correctly it's only enabled if that switch is set to off.
[Magisk] palmbeach05:
Just something i noticed, but i use seeder on my devices. I've been running pie with magisk canary builds. The latest release on that channel fixes issues with seeder, allowing services to be on upon bootup.
[Magisk] Syoenth:
I flashed the stock ROM on my J7 2015 and still, with Magisk 19.3 hidden and Magisk hide enabled, Pokemon detect that my phone is rooted, I fixed it by installing the Magisk Canary version, so far Pokémon Go hasn't detected Magisk
[Magisk] dd721411:
Did you hide also Google Play Store? BTW, Magisk Canary is working well for you so don't update or switch channels or anything else until PoGO f*cks up again. :D
[Magisk] w69:
Magisk not supporting my banking app

Need solution anybody??
[Magisk] Frostbiter:
I have oem unlocking turned off on my pixel 2 after rooting with magisk. I turned it off a while back to see if it was preventing me from receiving update and I'm still able to fastboot flash updates.

It doesn't fix the Netflix issue for me though, still shows up as incompatible despite the play store being certified.
[Magisk] palmbeach05:
Redflix tv is your fix
[Magisk] w69:
Magisk hide worked for specific app. Thanks.
[Magisk] zgfg:
Sorry, deleted
[Magisk] mercifool:
Since I upgrade my S10+ firmware to ASF3, my root has become partial, is there anyway to fix this? I can install stuff from Magisk repo, but i cannot remove system app and such. Please help, I'm using latest stable magisk.
[Magisk] kotuamoalt:
That sounds more like a work-around, rather than a fix?

---------- Post added at 07:37 AM ---------- Previous post was at 07:27 AM ----------

LOGS.

---------- Post added at 07:44 AM ---------- Previous post was at 07:37 AM ----------

I could be wrong, but I think this is your Google overlord's way of telling you that they do not want you rooting their devices. Again, I could be wrong. Statistically speaking, I probably am. :cyclops:
[Magisk] mercifool:
Hi, thanks in advance, Is this what you looking for?
[Magisk] Didgeridoohan:
There's no partial root... You likely have something else causing issues, like a Magisk module mounting a magic mask over /system/app, etc.

If you need help you need to give more details as to what you're doing and what the unexpected result is.

The log you posted isn't showing a stable Magisk release? Have you updated to Canary since this post, or where you just not sure what release you have installed?
[Magisk] mercifool:
When i try to remove system app it say successful but when i restart the phone it still there,
[Magisk] AndrzejDwo:
Because you remove it only from Magisk Mask. Try to remove apps from system/priv-app - it should be good, but all the apps you want to remove from system/app you need to do it from recovery level.

Cheers
[Magisk] mercifool:
It usually work for me when i use titanium backup
[Magisk] AndrzejDwo:
You can try also to use Magisk "core only" mode when you want to make changes in /system. This should work as well.

Cheers
[Magisk] mercifool:
I got no module, only have youtube vance lol
[Magisk] AndrzejDwo:
And Vanced is just enough, because it's in system/app :D

Tho you have a mask on /system/app :p
[Magisk] mercifool:
Tried core only mode. Didnt work. I manage to delete some app in the system/priv-app, but couldn't find most of the annoyjng app xD
[Magisk] AndrzejDwo:
Did you reboot after applying core only? What is your device?

Edit:

I think you have one of Samsung devices. Check this useful tool if it's compatible with your phone:

https://xdaforums.com/galaxy-s8/themes/4-2-18-extreme-aroma-based-debloater-s8-t3744608/page33
[Magisk] biscottoesse:
just to be sure, there is no way I can use the method of patched image unless I have my bootloader unlocked right ? because I jsut got a new Xiaomi and it seems I can't unlock the bootloader in the next 160h so I guess there is no way to root it for a while ? or I'm missing something ?
[Magisk] garylawwd:
No its only a week just wait.

Patience is truly a virtue nowadays
[Magisk] Artim_96:
Well, since it won't give you any space benefits, why don't you just build a Magisk module that replaces the apks with empty files? That way you'll have the same effect plus they can't come back through a system update
[Magisk] guest4711:
If you really want to delete files from /system try to delete them from /sbin/.magisk/mirror/system instead. After a reboot they should be history.. (Just verified: Adding files to mirror/system will make them available in TWRP in /system; deleting them from mirror/system will make them vanish even in TWRP.)
[Magisk] wilsonhlacerda:
This module already exists: Debloater

Another related and also useful one: App Systemizer
[Magisk] wilsonhlacerda:
First, on Magisk settings set it for Core Only, reboot and check if the bug is gone. If so, then is a problem of some module you are using.

Second, completely uninstall Magisk with the help of Uninstaller (or restore your nandroid backup done just before Magisk install), reboot and check if the bug is gone. If so, then is a problem of Magisk itself, but I really doubt it. If that's the case, logs may help developers.
[Magisk] elliwigy:
some apps might b installed in data partition if theyre not on vendor or system
[Magisk] elliwigy:
thats bcuz toggling the switch doesnt disable or enable bl unlock, it simply allows or denys the ability to bl unlock
[Magisk] fil3s:
I can't get magiskhide to hide my isp app. Kinda need it to pay my bill. Any ideas?

Using 19.3
[Magisk] zgfg:
Use eg AppInspector to find exact path for each application or service:

https://play.google.com/store/apps/details?id=bg.projectoria.appinspector
[Magisk] wilsonhlacerda:
So it is not a problem of Magisk. It is a problem of your ROM camera app.

It is common to have CM/LOS camera problems with Samsung devices. Probably your case. Check the thread of the ROM you are using. Maybe it is only an specific resolution or so (then a clear data of the camera app may help)

You can also try alternative cameras like gcam (if mod available for your device), open camera, and others from Google Play.
[Magisk] fil3s:
Thx a ton , unfortunate it didn't work on my Nokia 6.1 : (
[Magisk] tubekeeper:
My one plus 7 pro just upgraded to 5.10 Android 9 with google June safety patch, after install TWRP & the Magisk 1.9.3 ,the phone bootloop to TWRP, after uninstall magisk , it can boot up but no root, I also install the magisk 1.9.3 with patched img to my Mate 9 Android 9 with Google May safety patched img, the phone boot with recovery , it can't open all the app if boot in normal , the app can be open but phone is no root. How to fix the above problem
[Magisk] KevMetal:
for everyone with hiding issues some apks are now also checking if developer settings + oem unlock + adb are toggled to on ...some games in specific so toggle them all off in combo with other hiding practices amd try again.
[Magisk] Didgeridoohan:
That's very unspecific... Have you really tested everything, made sure that MagiskHide works properly on your device, that there are no procfs leaks, etc, etc?

If you post what app it is it might be possible for others to test (unless it's region locked, doesn't check for root until after you've logged in, etc). I kind of enjoy that particular pastime.

Each of which is covered in the link I posted...
[Magisk] fil3s:
Thanks!! But I tried it with no luck.

Good point I will double/triple check I have followed the steps in that link. This isthe app I'm having trouble with , but not to worry I can just use my Oppo for that app
[Magisk] Didgeridoohan:
I tested and can confirm it looks for Magisk and the Manager. It might also use UDS detection, but since I'm on the latest Canary release where that is circumvented I can't currently confirm or deny. There might also be other stuff that's more specific to your setup.

Tested on my OnePlus 3T, Android Pie, Magisk Canary v19.4 (19307), hidden Manager v7.3.3 (228). On this setup Magisk can hide from it just fine.
[Magisk] fil3s:
Yep. The canary build with hidden manager didn't work . I'm using stock Android one pie June patch. I'm out of ideas . Just thought I'd make a note of it here

Thankyou!!!
[Magisk] NoFear1183:
I don't think the new Magisk hide feature using Zygote is as great as it seems.

All an app needs to do is check the ptrace status of Zygote. If 0, magisk hide is disabled, which then allows for other methods to detect.

If Zygote ptrace status is anything other than 0, something is attached (not common) which also gives away the fact magisk (or something else requiring the ability to attach to Zygote) is installed.

Maybe I'm wrong on this... But in some of the apps I used, this is my findings immediately after updating to 19.*
[Magisk] Didgeridoohan:
Not possible without root. Could be possible on Android 6 and below, but there you can't fully hide root anyway.
[Magisk] Ferr1s:
Hi guys. I cant Update magisk via the app. It says unknown Image file. So i tried to Update via TWRP but the pincode question during TWRP startup doesn't appear and my device stays encrypted. I downloaded the 19.3 zip via App and from the Homepage but App says Installation failed cuz of unknown Image file. Any ideas?

Gesendet von meinem MI 8 mit Tapatalk
[Magisk] RandomPooka:
Have you tried disabling device security by setting your screen lock to swipe or no password before rebooting to twrp? That may help
[Magisk] NoFear1183:
I wasn't sure if apps had a non root method to see ptrace status or not. Thank you.
[Magisk] Ferr1s:
Problem solved. I could install latest TWRP via fastboot and magisk via sideload. All Works fine now

Gesendet von meinem MI 8 mit Tapatalk
[Magisk] mrrocketdog:
ok. noob here to magisk. but lovin it so far!! i have installed a magisk module via magisk manager v.7.3.2 on a zte axon 7 A2017U. asking for uninstall procedure as the module does not seem to be working on my device. i do have titanium backup installed if that helps. there is the module and an apk to accompany it. uninstall with tibu or is there a folder where i can delete it from? thank you for any help/guidance with this.

dave :)
[Magisk] palmbeach05:
Open magisk, open side menu, go to modules, uncheck the box and hit the trash can. Then reboot.
[Magisk] guest4711:
You should uninstall that module using MagiskManager (modules -> litterbox symbol).

If this is not possible you may delete it from /data/adb/modules
[Magisk] jcmm11:
Magisk Manager|three bar menu|modules section

Find the module in question, click on the garbage can, reboot

(Modules live in /data/adb/modules/, also accessible via /sbin/.magisk/modules/ you can often just delete the relevant folder from in there and reboot, but if you're not sure you're better off using the official method since that may go through some additional processing to make sure everything is correctly uninstalled)

Edit: this thread is getting overrun by ninjas!
[Magisk] zgfg:
Although RedFlix partially worked few days (and I was able to watch some things from Netflix), now the last days (specially in the EU evening time when I could use it), it cannot connect to the server(s), no use ?
[Magisk] mrrocketdog:
okay magisk general support/discussion thread readers people , one more noob Q for the night. if i DL'd a magisk module to flash later where would i put said module for magisk mngr. to see so i can flash it? thank you for reading and any guidance you can provide.:good:
[Magisk] jcmm11:
Anywhere you want (Download works well)

When you go to flash (big + button on modules tab) you'll get a file picker to find the file.
[Magisk] Ryano89:
Edit.. nvm
[Magisk] zgfg:
Anywhere.

Open Modules, press the big red + sign at the bottom of the screen, navigate to the path and install your module
[Magisk] eierfrucht:
Hi guys, i'm having a problem exactly opposite to the one i used to have: now on my Honor 8 Pro (EMUI 9) the latest stable Magisk & Magisk Manager run just fine, the problem is that Magisk works some magic to always startup the device in Recovery mode, so that it actually boots into OS with Magisk enabled (replacing recovery_ramdrive is the only way to have Magisk installed on EMUI9)

I swear I used to do some tricky keypresses (like maybe Power + holding Volume Up for REALLY long) to actually boot into the stock recovery AFTER installing Magisk, but I can't remember what I've done... Obviously going to Magisk->Modules->ThreeDotMenu and choosing 'reboot into recovery' still results in 'normal' OS boot (+Magisk) and turning the device off then just powering on again results in 'normal' OS boot (+Magisk)...

I guess I can always revert to unpatched recovery_ramdisk in Magisk Manager (or flash it manually in fastboot mode) and things will get restored?
[Magisk] Didgeridoohan:
Not quite sure from your description what your issue is, but here's the Magisk documentation on the key presses you might be thinking about:

https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery
[Magisk] ale32thebest:
Hi, I'm having a problem with magisk hide not working for a mobile banking app ( https://play.google.com/store/apps/details?id=it.nexi.yap&hl=it ), I already tried the guide posted from [MENTION=4667597]Didgeridoohan[/MENTION] and other suggestion from him in similar threads on this subforum, I also tried magisk canary channel updates and repacked magisk manager, it still detects root, old version worked with just magisk hide, but with latest update it looks like they added more checks. I almost forgot, I have all green marks on RootbeerCheck and the app says i'm not rooted, the app version I'm having problems with is 1.10.2, for now i'm using an older apk and is working, but they may force me to update in future days, any help is highly appreciated (i hope a post here is better than a new thread just for this app)
[Magisk] eierfrucht:
That bit of documentation is outdated. In fact, my original problem was as stated in the manual: "For these devices, you will have to boot to recovery every time if you want Magisk." Then something was fixed in Magisk/Magisk Manager (I'm on Stable channel) and every time I boot the phone, I boot with Magisk enabled. That is, I always boot into ramdisk_recovery patched with Magisk which silently works its magic then kickstarts the OS. It doesn't matter if I just press Power On or use the Recovery key combination (Volume Up + Power On) -- I never make it into the stock recovery, but always land into the regular OS with Magisk enabled.

However, when I press Volume Down + Power On, I'm able to enter Fastboot Mode without issue.

Once I reflash the recovery_ramdisk partition with the regular, unpatched image, I'm able to enter the stock recovery by holding Volume Up + Power On. If I reflash recovery_ramdisk with TWRP, I'm able to enter TWRP by booting with Volume Up + Power On.

To illustrate the way it SHOULD be, let me quote the manual once again: "(OEM Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)" And I clearly remember that at some point back in time, I was able to boot into actual recovery just by keeping Volume Up pressed all the way through boot, while simultaneous brief pressing of Volume Up and Power On would result in a Magisk-enabled OS boot. This distinction between long and short Volume Up presses is no longer honored, so there's no way to enter the "actual recovery" at least for me. On the other hand, I no longer need to use a special key combo to boot with Magisk enabled, any kind of boot or reboot scenario -- save for Fastboot Mode key combo -- always lands me into a Magisk-enabled OS.

I just don't understand if this "you no longer need to press Volume Up to boot into Magisk" thing on EMUI9 and current Stable Magisk is a bug or a long-awaited fix to a well-known nuisance, but it looks more like the latter. Neither I understand if the loss of the ability to boot into the "actual recovery" is a trade-off resulting from that "fix", or a brand new bug.

If I really need to get into TWRP / Stock Recovery I can always reflash the corresponding image, but that's a bit tedious. Having a way to boot into both Magisk and Stock Recovery without fiddiling with fastboot would be really, really nice, and it used to be that way...