yashsingh1/xdaforums huggingface dataset:
[Magisk] Alucard1989pl:
I have issue in two Xiaomi phones. Every now and again restarts on Poco F1 and Redmi Note 6 Pro on MIUI 9.3.1 (dev) with stock and custom kernel with magisk 18.1.
[Magisk] Machine318:
Unlocked Bootloader Detected

I could be way off topic here but I have a single app (Unconnect 3.3.4) that is recognizing the unlocked bootloader on my OnePlus 5T OOS 9.0.4

The system is completely passing SafetyNet Checks, I am still encrypted. Magisk Advanced setting "Preserve force encryption" and "Preserve AVB 2.0/dm-verity" are enabled.

Magiskhide is limited to Banking, Games, Security sensitive and Select Google apps (Log attached)

So my question is, how to work around this? XPrivacyLua is not an option as Xposed does not support SDK 28, and I don't think EdXposed will work as it can't hook resources.
[Magisk] jcmm11:
Need a logcat for this type of problem.

If it's really recognizing the unlocked bootloader try a custom kernel rather than the stock kernel.
[Magisk] BrianN_Cols_OH:
Data wipe issue

Bumping this one - can someone help? I had it working previously.
[Magisk] brunori:
Install Magisk without losing /data

Tryed the zip instalation via TWRP on a Samsung SM-G570F with android 8 and encrypted /data. The instalation seams to be ok, excepct that it tries to mount /dada and fails. But after the restart, the phone shows a verification error message and aks for "format" (no way). So I had to reinstall the stock system.

Than I tried by instaling the magisk manager and patching the stock boot, but there is no "install" option to activate the patch function! (note: the phone is in airplane mode, as I don´t want it to access the internet).

What could be wrong? Remenber: I dont want to lose the /data
[Magisk] Machine318:
For the hell of it I tried XPrivacyLua solution... And it's working. I restricted it's ability to see other apps.
[Magisk] kotuamoalt:
U block is AWESOME!
[Magisk] bunny1796:
Hi... Am unable to flash zip from my local storage but i can able to install modules from repo.. Can anyone help resolving this issue.??
[Magisk] romulocarlos:
Hello all!

First of all, sorry if my question already have an answer. I look for what I want on search in this topic, but return too much results. So, here I go.

I want to use my job account on my Zenfone 2. It is using BORETS ROM with Magisk. The problem is: as the account is linked to G-Suite Services, the phone must be encrypted to have the account working. So, I tried to encrypt, but the process never ends. I left my phone for several hours and even with this amout of time, encryption never ends.

So, I saw an option on Magisk, "preserve forced encyption". Maybe this option is preventing my phone to be encrypted? What this option means (and the other too, "preserve avb"), please?

Thanks in advice!
[Magisk] Digital DJ:
Magisk Modules

How often are Magisk Modules updated? I'm particularly asking about the Kalinethunter Module v7.2 last updated on Feb 3, 2019. I'm hearing it doesn't work well with Android 9.0 and I'm trying to get it on my Google Pixel 2XL.
[Magisk] Badger50:
It's all according to the developer. Might have better luck contacting him :good:
[Magisk] SubZeroNexii:
I have this etoken app from my bank that I can't seem to hide root in any way shape or form.

This is the app: https://play.google.com/store/apps/details?id=com.eTokenBCR

I'm on lineageOS official on a Xiaomi Mi Mix 2s.

You can test the app just by running it. If it detects root it just opens on a screen saying that otherwise it doesn't.

If anyone has any idea what I can do I really appreciate it.
[Magisk] jenslody:
It works for me, when I add the app to the MagiskHide-list and hide the Manager by repackaging (see its settings).

But I use the latest canary-build, that might also be related.
[Magisk] Kachelistic:
MagiskHide not working well :

It seldom works correctly, but many times when I open hided apps(no matter what the app is), the app detects root. I don't know why this happens, but when I go Magisk Manager app and turn the MH switch off and on again, then the app stops detecting root.

I assume MH function often turns off(not the switch in app goes off - it stays ON BUT doesn't work until I turn off and on again) so that I have to re-enable it, but not sure. Can this be fixed?

* It DOESN'T MEAN that MH cannot hide from certain apps ; it works but sometimes dies.

currently using Razer Phone 2, 8.1.0, Magisk 18.0&18.1, MM 17.0
[Magisk] scarline:
Today I updated to Magisk manager 7.0.0. It said, it will only work with the latest 18.1 version of Magisk. So I booted up recovery and deleted cache/dalvik, installed 18.1 and deleted cache dalvik cache again in TWRP (latest version). After reboot Magisk manager is not asking for root confirmation on root aps anymore. Also the UI has become unstable: "UI has Stopped Error" and I see various black screens before the UI of Android is apearing again. Any ideas? My plan so far would be to uninstall Magisk manager, uninstall Magisk and do a downgrade to manager 6.x and to Magisk 18.0. If 18 is not working 17 and other wise 16.7. ...
[Magisk] AndrzejDwo:
First thing to try is boot into recovery, flash Magisk uninstaller and flash latest Magisk. Do not wipe cache/dalvik. Boot into system and install latest Magisk Manager apk.

If you need more help then you need to provide more information about your device and logs.
[Magisk] scarline:
Why not wiping dalvik? I Just installed magisk 16.7 for testing purposes. Here the zip verification is no problem. At 18.1 it showed an error in TWRP. Is this a hint?
[Magisk] sq_dev:
Hi

actualy is an error in boot_patch.sh: [ -f extra ] && ./magiskboot dtb-patch extra && ui_print "- Removing dm(avb)-verity in extra-dtb"

commits from 08.03.2019

BR
[Magisk] scarline:
I did:

-booting to recovery twrp 3.2.3

-dalvik/cache clean

-install the latest uninstall package of magsik

-dalvik/cache clean

-install magsik 16.7

-dalvik/cache clean

-reboot to system

-install magisk manager 6.1.0

Now root is working again. Is there a way to find out what is causing the problem magisk manager? Can this be related to the zip-verfication error i described before? And can root cause the system UI crash or just the manager (with the new UI it has)?
[Magisk] jenslody:
Zip verification error is because John does not sign with a free availabke test-key anymore, which does not make sense anyway, even if most zip-files are signed this way, but with his real private-key which is not known by TWRP.

So that's not the problem.

Clean flash of Magisk might help.

Otherwise logs are needed to try to find a solution.
[Magisk] scarline:
I see, did not know about the zip key... For now 16.7 and 6.1 are working for me.
[Magisk] varefaz:
LG G6 Android 8.0 magisk hide doesn't work. Apps see my device as rooted. Version 18.0 and 18.1

Works only with version 17
[Magisk] Didgeridoohan:
There are known issues with MagiskHide on v18.0 and v18.1 (discussed a lot). Likely fixed for the next release.

Not without more details and installation logs (but my first guess would be that you're trying to install an outdated module).
[Magisk] martyfender:
On my devices, I never wipe the cache and dalvik cache after flashing Magisk any more. Doing that has caused problems for me that required a factory reset, because something in the data partition was corrupted.

I flash the magisk.zip, reboot, then if I need to wipe the caches, I reboot to TWRP again, then wipe them and it does not cause the issues for me. It may just be something strange in my device and rom that causes this though, I'm not sure.
[Magisk] scarline:
Would be strange... Maybe [MENTION=4470081]topjohnwu[/MENTION] can say better. Also about the 18.1 problem on angler.
[Magisk] jcmm11:
You don't have to run dalvik/cache clean at all, never mind 3 times. Dalvik only comes into play for apps installed to /system/, which Magisk doesn't do.
[Magisk] Edgio60:
Had to go back to 17.3. Works fine again now.
[Magisk] Didgeridoohan:
Barclays is one of those apps that use dependencies to detect root, mainly the phone app (com.android.dialer). Also adding that to the Hide list lets me open Barclays without issue (on Magisk Canary build 18114).
[Magisk] ashyx:
Barclays app works fine on my devices with the app hidden and magisk manager hidden.

However installing busybox causes it to fail.

It also sneakily attempts to gain root privelidges when first run. :p
[Magisk] Didgeridoohan:
Yup, but not when I have the phone app on the Hide list.
[Magisk] Ott_:
Magisk seems to be failing the CTS safteynet check on my Poco F1/Lineage 16 (march 7th nightly). I didn't install them all at once, I installed the lineage stuff, set up my phone, then flashed magisk from my phone. Would reflashing everything at once fix it?
[Magisk] JimSmith94:
I have run Magisk for a long time on my Pixel 2 XL without any problems. Today T-Mobile's free Lookout security app started flagging Magisk Manager as a threat as a "Root Enabler". Any idea why this just started today and how I can get rid of the message?
[Magisk] martyfender:
You might try to hide that app in MM, delete its app data and maybe reboot. If that doesn't work, you may need to hide MM in its settings.
[Magisk] Didgeridoohan:
https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228

Follow [MENTION=8126387]martyfender[/MENTION]'s advice, but if it still detects root it could be the "MagiskHide intermittent failure" bug in Magisk v18.0 and v18.1. Should be fixed in the next release (already fixed in the Canary releases).
[Magisk] rexsmith9886:
can anyone confirm if this app is opening after magiskhide enable?

https://play.google.com/store/apps/details?id=com.sbi.upi

For some reason it stopped working for me. I highly suspect my device could be the issue and not Magiskhide functionality.

https://i.imgur.com/cp7QDOf.jpg

My old nexus 5 is using SuperSu + suhide and tried in that phone and app works.
[Magisk] JimSmith94:
Weird, I hid the app but Lookout immediately flagged the newly downloaded version. I reverted back and the Safetynet check failed. I rebooted with the original version and haven't seen the warning message since.
[Magisk] papatzis:
Hi to all and sorry if this had been answered in previous posts because the thread so big and it not easy to find the answer.

I have a xiaomi note 4 nikel running miui 10, Magisk is running perfect thanks to the developer, I had some problem with a application that although I had it enable in magisk hide it was detecting magisk app, so I tried to hide magisk manager.

The app was recreated with a random name and it the app is working fine now, but in app drawer I see 2 magisk manager apps, the one that is working as is was working in the past and in superuser # menu I see a magisk manager that has root access disable, and the second magisk manager that is in the app drawer and I run it seems that magisk is not installed.

Is this normal when you hide magisk manager, 2 magisk manager applications are created with random name?

Both magisk and magisk manager are in the latest version

Thanks in advance
[Magisk] Didgeridoohan:
Can't test because of regional restrictions, but if suhide works the next Magisk release might work better. MagiskHide has been completely rewritten from scratch (twice) in the past couple of weeks, and the new implementation will use the same method as suhide. The current Canary release (18114) is using this, but if you want to try that keep in mind that it is prone to have bugs, since it's a bleeding edge build.

Does sound like the MagiskHide bug (although, it could also be that the updated app has improved root detection that the new MagiskHide hopefully will take care of). You shouldn't have to reboot though, it's enough to go to the Manager settings and toggle MagiskHide off and on again.

Not normal.

What are the names of the apps? The repackaged Manager should be named just "Manager" the original is "Magisk Manager". Which one is it that doesn't work?

If it's "Manager", that means the repackaging failed. Uninstall the repackaged Manager and try again. If it still fails we'll need at least a logcat to know what's going on.

If it's "Magisk Manager" that doesn't work, it means that the old Manager couldn't be uninstalled (usually happens if the Manager has been made into a system app somehow).
[Magisk] papatzis:
Hi thanks for the answer, both apps in the drawer are named "Manager" both had random package names

I tried to freeze the one with the problem all were working fine so I unistalled the this one , so I have now in the drawer 1 app "Manager" and all are still working fine .

I will try to see if there is a problem but so far everything is Ok.

That is why I asked you if this was normal.

Thanks again for your help.
[Magisk] Didgeridoohan:
There's no way for me to know how it happened, but for some reason you then had a repackaged Manager that hadn't gotten it's package name saved in the Magisk db. If that happens, that app can't be uninstalled automatically. If you've deleted the nonworking app, everything should be fine.
[Magisk] cridus:
Hi... I had the previous version of Magisk Manager and Magisk and I decided to finally update them... now every time after I boot up the phone, after like 15 seconds all apps in the background start crashing (many dialog popups appear) and then the phone reboots.

What's the best course of action to fix this? Should I uninstall Magisk with the uninstaller in recovery mode and reinstall it from scratch?

Thanks for the help.

Edit: Ok nevermind, I uninstalled and reinstalled it via recovery. I also had to uninstall and manually reinstall Magisk Manager because it wouldn't work properly.
[Magisk] p-walker:
Ok guys I am pretty sure something if off with the Magisk Systemless host module.

So far I had two OTA updates on my Xiamoi A2 lite that worked without problems (first one with magisk v18.0, sencond with 18.1)

However after the last update I activated the systemless hosts module.

This months update actually did not get installed as the update engine suddenly got a mismatching hash.

I only used adaway (and TB backup, but basically only adaway was used, which was fine before) thus I was interested in the systemless hosts module which would take care of reinstalling my modified host file if I got that right.

However all I can say that I had 2 OTAs working smoothless when systemless host module was deactivated, while at the same time adaway was working.

After activating the module my OTA failed. Not sure if it is a weird coincidence but maybe someone can look into that.
[Magisk] jlesteratkins:
Samsung galaxy grand prime

LOS 14.1

18.1 sends my phone into bootloop, I've tried through magisk manager, through twrp, tried completely uninstalling and everything and still bootloop, also my magiskmanager folder was deleted so now I'm stuck back on 16.7

Edit: I downloaded 17.3 and 18.0. 18.0 gives same bootloop, 17.3 boots but now I get a google play services keeps stopping error then afterwards a SU database is corrupt.... Flashes up and I can't read all of it before it dissapears
[Magisk] clambert11:
I had a similar issue. My Platform Tools were slightly dated. Once I reflashed the factory image again with the latest tools, Magisk worked just fine.
[Magisk] Didgeridoohan:
Did you make sure that systemless hosts is enabled in AdAway? If not, it'll modify /system.

I've not seen any indication of systemless hosts not working. It's quite easy to verify that it's magic mounted properly. Edit the file in the hosts module directory, and if the hosts file in /system/etc is altered as a result of that, things are working as they should.

Without logs it's hard to know what's going on...

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] DawoodSahi:
Magisk 18.1 randomly loses safetynet and fixes up on a reboot. Most probably the reason I've been getting banned on sc also. Any help?
[Magisk] guest4711:
It's a known issue with known fixes as you'll find by a simple search, e. g.:

* Use latest canary or unofficial builds.

* Switch MagisHide off and on again. No need to reboot.

* Go back to 17.3
[Magisk] Phoenix Wright:
I discovered a (serious) bug up to the latest stable, spent some time investigating it so I might as well say it here. Up to 18.1 modules are stored in a ext4 image. Given when the image is mounted it can't be resized, when you install a new module Magisk creates a new temporary image and copies the module to it. On reboot, it mounts both of them, calculates the used filesystem space for both, rounds the size and creates a third image where it copies everything into (from both images, starting with the bigger one). It seems though that the Linux kernel allocates 2% (or 4096 blocks) of all ext4 filesystems for its exclusive usage since around 3.10 (didn't check the exact release): https://lwn.net/Articles/546473 . On my Pixel 2 XL with 18.1, I incurred twice in a scenario where the magisk.img was around 98% full. I installed a new module which wasn't enough to go past the free space, so the third image was the same size as the original; Magisk then failed silently to copy files from the new/upgraded module (the files of the module were corrupted, either empty or truncated). I updated to 18.2 Canary just for this (18.2 drops ext4 images altogether).
[Magisk] p2nv:
Can anyone please tell me if it is possible to downgrade version of magisk and if so will it wipe anything?
[Magisk] jenslody:
In general you can downgrade, but that depends on the versions.
[Magisk] p-walker:
Oh I actually wasn't aware that it is needed to manually activate that option in adaway.

I thought that using the systemless host module would be enough. I thought if the hosts file is magic mounted properly you could easily edit /system/etc and it would just be the magic mounted version of it and not the actual host file, am I wrong?

If that is not the case it actually would make more sense if we had a adaway magisk module where this stuff is handled. I mean I had a short look into the adaway code and I think the whole logic there could break easily and their systemless host mode would probably not work anymore.

I heard there once was a hosts file module for Magisk which was discontinued in favor of adaway supporting Magisk, maybe that was a mistake...
[Magisk] p2nv:
I'm wanting to downgrade from 18.1 to 17.3 to fix the SC ban issues. Will it alter any apps like Google Pay in doing so? Could it cause bootloops or require clean install?
[Magisk] jcmm11:
First, this probably belongs in the AdAway thread.

Next, from what I've seen AdAway will automatically turn on Systemless mode of the Magisk module is installed. At least I couldn't get it to stick. I turn off AdAway Systemless mode, reboot, it's turned on again.

This actually makes since you are correct when you say "I thought if the hosts file is magic mounted properly you could easily edit /system/etc and it would just be the magic mounted version of it and not the actual host file, am I wrong?"
[Magisk] Didgeridoohan:
If you have a recent enough version of AdAway there shouldn't be any problems. It'll automatically enable the systemless option (as outlined by [MENTION=4487388]jcmm11[/MENTION] already). But, if you're using a version that doesn't enable it automatically, the app might mount /system rw and then it doesn't matter if you have the systemless hosts module installed or not, your system partition will be altered and an OTA will fail.
[Magisk] martyfender:
I have v 3.3 on 4 of my Android 6.0.1 devices and it works very well, but it has a bug where in it's preferences the systemless hosts option is greyed out, even though is is enabled.

I would recommend the v4.2.3 version, which I have on one of my devices and it also works very well. It is the preferred version for newer versions of Android, as I believe it fixes some bugs that the older v3.3 has with newer Android versions, if I am not mistaken. The newer version, v4+ requires that the host sources are https and I believe rejects http sources. I keep v3.3 on most of my devices because I can still us the Steven Black mirror: http://sbc.io/hosts/hosts and it still shows the dates of the sources. With v4+ I must use the githubusercontent https version of Steven Blacks hosts and it does not show the dates, just that it is up to date or needs to be updated. My personal preference is for the older user interface of v3.3.

See the Adaway xda thread for more info and help.
[Magisk] p-walker:
Oh yeah for sure, if it is only a problem on adaway site I will forward this. However I am still not certain what is going on. As you confirmed my understanding that the manual activation of systemless mode is not necessary I was sure if it's a problem with the built in hosts module, I don't understand much how the magic mount works technically but I thought there might be a possibility that the original hosts file is also altered if the magic mount does not get removed properly before installing the OTA.
[Magisk] adan..89lion:
Hi,

I'm using Asus Zenfone 5z and has been successfully using Magisk during the Oreo days. Recently, however, after upgrading to Pie and flashed Magisk with boot.img, the root works, and the previously (Oreo era) permitted apps still have the root permission, but there are no prompts for new apps. I have disabled the battery optimization for Magisk Manager and also excluded it from Mobile Manager (a RAM manager app for ASUS).

The log shows

su: request rejected (2000->0)

after I request the root permission.
[Magisk] jcmm11:
Latest AdAway now shows "up to date for X days" even for github.
[Magisk] martyfender:
Yes, I have 4.2.3 on one device and you are correct, but I want it on the opening page, just like 3.3. Now that I know this, it is no big deal to go to that second page, but since v3.3 still works on my other 4 devices, I may stay on it for them, however this is getting OT here, I believe.
[Magisk] dpsi:
So I tried again with Magisk 18.1 and manager 7.0 along with OOS 9.0.4 and gpay is working again.
[Magisk] rpsweb:
Hi I'm using version 18.1 / 7.0 but can no longer setup my card for Google Pay, it detects my phone is rooted
[Magisk] martyfender:
https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703

See post #5. If you have any problems, I would suggest asking on that thread.
[Magisk] bsports666:
Can anybody help me? I have install from Google play store application "go by train" and when I start application it say that my phone is rooted. So how to hide this? I try to hide with magisk hide option but not working? Thanks for support. Regards
[Magisk] TonikJDK:
After you hide it try clearing cache and data from the app. They often store that info.
[Magisk] Shavo6:
Hi all. I've been using magisk for a couple of years but never had similiar problem. I can't find anyone with similiar problem as well... I've updated yesterday my Oneplus 5T to OxygenOS 9.0.4. I've did dirty flash and boot to system. Then i reinstalled TWRP by ADB. And since this step everything was ok. Next i downloaded Magisk 18.1 zip in Magisk Manager and installed it by TWRP. Installation log was normal and succesful. Then i booted into system but right after i saw lockscreen, popup "shutting down" appeared (Exactly like this when you are shutting down the phone). And since this step i've got endless bootloop... Please, help me.
[Magisk] RyomaEchizen:
Hi i'm getting "SafetyNet API error" message [emoji17]
[Magisk] FlavioV:
Same here. My device still passes on SafetyNet as you can see, it's just the native check that doesn't work.

EDIT: nevermind, it's back
[Magisk] RyomaEchizen:
All works now

Enviado desde mi ONEPLUS A3000 mediante Tapatalk
[Magisk] martyfender:
You either have no internet access or the snet. Apk is not downloading.

https://www.didgeridoohan.com/magisk/MagiskHideSafetyNet
[Magisk] dvhttn:
OK. For some reason I've 'hidden' Google Play Services and now I can't uncheck it. It probably happned when I first installed 18.1 and found that safetynet was failing occasionally. Anyway, it's happened and wondered how I can take it off the 'Magisk hide' list? The other 3 apps can be switched at will but GPS stays checked. I'm now on the 18116 canary build.

Ta for any help.