yashsingh1/xdaforums huggingface dataset:
[Magisk] Mrpookie:
Try to keep toggling magisk hide and force closing and opening magisk manager to see if you can get magisk hide to stick

---------- Post added at 02:37 AM ---------- Previous post was at 01:42 AM ----------

Regarding issue where ROM is unable to install apps with magisk hide enabled

After much searching I found this:

In nexus 5 forum question asked:

Anyway, I have just a single issue (which I'm not sure is ROM-related)

I tried to install Magisk (version 16 and 16.3 BETA) and I discovered that after that I couldn't install any apk at all and Play Store didn't let me install anything!

I have discovered this because in the logcat a line like this appeared:

Dev response:

Yup, it's because of the SDCardFS support. What I found in the old tree was backported for Nougat, and doesn't have all the features required by Oreo. Since I couldn't add directly on top of that, I reverted to regular FUSE-based operation (ro.sys.sdcardfs=false). Magisk must've somehow masked or overridden that prop. It will be fixed in the next CAF kernel build.

How can we fix?
[Magisk] Didgeridoohan:
[MENTION=8982083]Mrpookie[/MENTION] So, is your issue fixed if you set ro.sys.sdcardfs to false? You can use the "Custom props" function of my MagiskHide Props Config module to do it.
[Magisk] Feduz:
Same, everytime i close the app, magisk Hide turn off
[Magisk] EVNS:
It no fix the problem, I tried, keep no installing apps in play store.

I edit build.prop and put to false to.sys.sdcardfs=false
[Magisk] Captain_Throwback:
If one comes...

I think [MENTION=4470081]topjohnwu[/MENTION] needs to focus on getting v7 and the updated app with [MENTION=3400685]digitalhigh[/MENTION]'s help completed. Since there's a workaround for the updated SafetyNet detection already (disable Xposed & reboot), don't expect a fix to come for a while - at least not until after v7 is released and well-tested and working.
[Magisk] rgawenda:
I've hitting F5 for this thread more often than when I was on the Nexus wagon and a new Android version was released.

But he also said that school was starting so I'm remapping my F5 key to F6 and, as he stated, I'll be patient.
[Magisk] exodius48:
Already did, still get error on CTS

Actually i need magisk to play pokemon go too. :D
[Magisk] DerpleNerple2000:
That did the trick! Glad I could get my viper fix. Thanks so much.
[Magisk] westeight:
Passing SafetyNet...

Card added...

Able to add new cards...

But:
[Magisk] JaymzTA:
Just as an FYI, I do not have xposed installed.
[Magisk] Didgeridoohan:
Go to the Magisk Android Pay thread (look in OP) and you'll find your answer there.
[Magisk] westeight:
It was working yesterday. So, either my Tasker script (which requires root) is now being detected, or it's another issue.

Just tried manually disabling root With Magisk, then switching on NFC and adding a card. Works fine. Also passes SafetyNet. On this particular handset I don't have Xposed.

This time, no root detected but AP keeps telling me to hold the phone closer to the terminal.. :p
[Magisk] imatts:
I apologize, it wasnt my intention to be rude of course, I am just super anxious to play Pokemon Go on my new replacement xD
[Magisk] DerpleNerple2000:
I'm hearing safetynet was updated, causing Xposed to fail the check. Are you using Xposed?
[Magisk] SidneyD:
unsu.zip is for the removal of SuperSU. I've already successfully removed that. The problem I have is superuser.zip (re)creates /sbin/su every time I boot my phone in the read only filesystem rootfs.
[Magisk] HtHNightwolf:
Heard the same thing.

UnSU several times worked here

Supertoll gesendet mit Tapatalk
[Magisk] Ger$$on:
Same here

Enviado desde mi Redmi Note 3 Pro
[Magisk] habylab:
Just worked for me 10 minutes ago.
[Magisk] adhd_1977:
Will this work on galaxy S4 ve ,with touchwiz LP 5.0.1 ????
[Magisk] SidneyD:
Tried it anyway. No effect as I had already removed all traces of SuperSU.
[Magisk] JudgeDread11:
I don't know where you got your instructions but the magisk compatible xposed should be flashed after magisk itself as it uses magisk.

If you'd use an other xposed version it might be needed to flash before magisk, but that would defeat the whole purpose of magisk and systemless modding.

Also I'm not sure if it's possible to disable non systemless Xposed, which is required to pass safety net checks.

---------- Post added at 05:41 PM ---------- Previous post was at 05:39 PM ----------

Did you install the superuser app from the play store? Because you mention "magisk never prompted for root". It shouldn't the superuser Ao should.
[Magisk] DerpleNerple2000:
I'd still give disabling Xposed a shot, considering it seems to be the solution for many others.
[Magisk] HtHNightwolf:
Was for me too.

Supertoll gesendet mit Tapatalk
[Magisk] Mrpookie:
Thank you both, I will keep searching and trying whenever I have time. Does anyone know of other props that could be the cause?
[Magisk] bafforosso:
Hello,

to everyone using OnePlus phones running OxygenOS 9 and having issues with MagiskHide here is [MENTION=4470081]topjohnwu[/MENTION] 's recent tweet :

Direct link to Tweet

TL;DR: OOS 9 broken optimizations cause major issues with MagiskHide, flash custom ROM if you want to use it.
[Magisk] guest4711:
Hope you entered ro.sys.sdcardfs (latin letter r, not t)...
[Magisk] Pedro Bassou:
Missing module icons

I installed Magisk and it seems that everything is fine, I can successfully access and install the modules, the only problem is that when I restart the mobile phone does not appear any icon of the installed modules. Anyone know what can be happening? :confused:
[Magisk] EVNS:
Yep ro.
[Magisk] saccentekennedy:
Weird... Mine is working fine with Magisk hide
[Magisk] Squallo91:
Magisk 17.1 and systemless hosts problem

My Magisk seems not to work properly with Adaway. In Adaway "systemless hosts" is grayed out but I read somewhere to ignore that when ist is set in Magisk. Sometimes it works but only temporarily and the altered hosts file is gone after reboot. And most of the times, it doesn't and end with error. Newer v4 Adaway version says to try different path than system/etc because the partition is full (I don't think it's true). When I try different path, it says something about symlink not set.

I have my own hosts file so I don't neccesarily have to use Adaway. I want the alteration to stay and don't want to mess with system partition if possible. I can do that manually but I don't know where to paste my hosts file - where is the hosts file used by Magisk?

My current Android setup:

Huawei P9 Lite (VNS-L21C432), firmware ver. B504 (after install flashed B504's boot partition image patched by Magisk), Android 7.0 Nougat with EMUI 5.0.3. Used custom recovery (Elite_TWRP_3.1.1) to make a full backup, then flashed original recovery partition image. Magisk - v17.1, "systemless hosts" setting always on, tried with and without "core only mode"/"preserving AVB 2.0/dm-verity" (even when unchecked it is checked after reboot, normal?) - no difference. SafetyNet check - always correct. Root Checker app says I'm rooted.
[Magisk] cmo220:
I'm having this problem too on Pixel 3, running Pie, stock. It seems strange that this hasn't been mentioned more, or maybe my search skills suck.

Every time I hide magisk manager there are problems when I reboot. This is with 17.3 and the first few 17.4 builds. The latest 17.4 has the failed error after trying to hide magisk.

What logs should I submit to help with this, and when in the process should I run them, since it starts before a reboot and ends after. Thanks.
[Magisk] Klusio19:
I ATTACHED SHORT VIDEO TO SHOW YOU THIS. PLEASE LOOK:

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

I downloaded the newest Magisk version, then flashed it in TWRP. Booted to system, then downloaded newest Magisk Manager App. I run the app, and then it shows that I haven't got Magisk installed and it asks do I want to install .zip. I click no, then I refresh and it suddenly show that I HAVE Magisk. Then there is inf. about requires Additional Setup. I click yes and it shows setup failed. Why? Can someone help me?

ROM: LOS 16

GT-I9195

Sorry for English, I'm from Poland
[Magisk] mrlad:
Trying to install Magisk 17.1 on a Pixel 2 XL with TWRP 3.2.3.1. TWRP fails to install due to a signature verification failure on the ZIP file. I downloaded 17.1 from the official thread. Is this a known problem or a TWRP issue?
[Magisk] jenslody:
Magisk is signed with Johns key, not a test-key or any othe rkey known to TWRP. Therefore it fails verification.

Just turn the verification off and flash again. Signing with a public available test-key has no advantage, it just looks more secure.
[Magisk] newbcake:
I had Magisk working fine on Nougat, but after upgrading to Oreo today, it has SafetyNet problems.

On a fresh boot, it'll pass SafetyNet, but after about 1-3 minutes, it no longer passes unless I reboot.

---------- Post added at 07:02 PM ---------- Previous post was at 07:02 PM ----------

I had Magisk working fine on Nougat, but after upgrading to Oreo today, it has SafetyNet problems.

On a fresh boot, it'll pass SafetyNet, but after about 1-3 minutes, it no longer passes unless I reboot.
[Magisk] mordantly:
Upgrade method if original clean kernel not available... flash 17.1 over the top of 15?
[Magisk] jcmm11:
That should work just fine. Also do you have a file /data/stock_boot_<sha1 hash string>.img.gz? If so that contains a gzipped copy of the stock boot image from the last time Magisk was installed over stock.

The sha1 string is for the unzipped boot image.
[Magisk] husky69:
Got Magisk 17.3 running on my LG G6 with a modified stock ROM. Now after a while Magisk started claiming it wasn't I stalled and offers to do so.

After restarting the mobile it's working again, but will eventually start complaining again. Maybe it just crashed?

Anyone else having this problem? Hints on how to solve?
[Magisk] regularmen:
I'm trying to install Youtube Vanced module but for some reason the module isn't showing in Downloads menu and also some of the modules are missing (xposed, some audio mods, and my must have Doze GMS, etc.) Not every module tho, just some of it are missing. Tried the clear repo list, no avail. My other phone (Zenfone Max) showed just fine except this phone (Nokia 5) and also somewhat important, this phone is and can only use magisk 16.1 also running at stock rom. Anyone know what causes this?
[Magisk] bafforosso:
The modules you're talking about have been updated to the latest Magisk Module Template which is for Magisk v17+, this is why they don't appear for older Magisk versions (compatibility issues).

I guess you could try flashing those modules in recovery and see if they work (use your other phone to download them then transfer to the Nokia). Just a word of caution first : Nandroid backup your phone first in case of issue, be careful that the modules you want to install do not modify system partition directly (or removing them will not get you back to the state before install, check xda module specific thread for info) and you may want to install Magisk Manager for Recovery Mode to be able to disable a module from recovery in case one causes bootloop.

If it's only for YouTube Vanced you have alternatives :

Manually install root version

Install non-root version : only thing missing in this version is automatic opening of YouTube links in Vanced.
[Magisk] SimplyCity:
I used to had similar problems in the past with YT vanced module. Found, that in few specific situations, installing YT vanced destroys magisk img. Img just becomes to small for all your modules. YT vanced just did not extend magisk img properly. So, I use workaround from the time of that finding and issue is gone. So, if I may advice anything : go to magisk manager app and delete YT vanced module, then go to download section and download - not install, just download - magisk manager for recovery mode. Then reboot your phone to twrp, tap install and point to download folder, choose magisk manager for recovery mode you just downloaded in first step. After install go to twrp terminal and put that command: "/data/media/mm", hit enter. While in mm, chose "r" (like Resize) and enter new value for magisk img, let's say 160 mb. Confirm. Now you may reboot to check if modules you had b4 are all working. If yes, reboot to recovery, run mm and make sure your magisk img is big enough for YT vanced - simple math. If it is, just install YT vanced from recovery, and after that run mm again, choose "r" again and check how much free space left on magisk img. If there would be 0, that means something's wrong and you must do whole again, but I'm sure there will be value different then 0. Now you may use mm command again to decrease magisk img size, or not. :) good luck

I see wasn't first, anyway, decided to not delete my answer

Echoe[emoji769] team member / N8 Oreo
[Magisk] mordantly:
I will have to check. Rom has v13 or 15 stock. If not 17.1 can overwrite old version?
[Magisk] regularmen:
ah I see, so root version that is...

Simply, I can't install latest magisk in my nokia because what happen is much worse than a bootloop

the phone just won't turned on and you have only few seconds just trying to access the download mode or the phone died again

heh what a nightmare. do you know why or it's just wont work?
[Magisk] martyfender:
Was it charged before you did all of this?
[Magisk] vfkkdamp:
Recently, my Samsung Tab A 2016 got an update to 8.1.0 with updated bootloader, and since there is no twrp yet (seems abandoned), I tried to patch the boot image file and flashed it on odin. Flashed fine, but when booted back, it got verification error and device recommended to wipe to make it usable again. Is there any step that I can do to remove the verification/encryption without twrp? Thanks in advance.
[Magisk] martyfender:
Was encryption and verification unchecked in Magisk Manager before you patched your boot.img?
[Magisk] vfkkdamp:
I think it was checked, I might need to see it again. Gotta reflash the stock rom for now.
[Magisk] regularmen:
Yeah, like 70% charged.

I should have mentioned that nokia 5 community has advised not to install magisk 17.1 as it caused various problem such as stuck at bootloop, well at least it was reported by those who tried. And something you should know, officialy, we haven't got our bootloader unlocker yet (nokia 8 has had their unlocker so we still had to hope) and unlocking one requires a bit effort, someone managed to make root working (because how this phone made and supersu couldn't work) by using magisk and it's root embedded to twrp, maybe that's why it wouldn't work. Just my two cents
[Magisk] vfkkdamp:
A follow-up, I reflashed fully stock and then installed magisk with both encryption and dm-verity checked. Upon reboot I saw the same verification error and urged me to reset so I did. A couple of restarts, the tablet went back with welcome screen and went through steps to get into home screen. I reinstalled magisk manager after that, and it said installed magisk 17.1. But it popped up a dialogue saying it needed required additional setup. Clicked run and it said setup done but it kept popping up every time I open magisk manager. I also installed adaway to test the root functionality and it seemed working fine.

Any idea about the require additional setup?

edit: I tried to install some modules and it gave error "Unable to unzip the package." I tried to install busybox module from magisk manager and it installed fine but but it has no name on modules installed. Tried busybox from playstore and it couldn't even install, saying it can't verify the integrity.

edit2: Switching to magisk beta seemed to fix it. Patched boot with 17.3, flashed through odin, rebooted, same verification error screen. But instead I booted up on default recovery and wiped both data and cache. Device restarted with welcome screen, reinstalled magisk manager and it prompted additional setup. Pressed install and it went smoothly and I can install the modules back. Solved.
[Magisk] YLNdroid:
Hello everyone.

:)

Is / are there any module/s to disable the SMS-to-MMS conversion?

:confused: :fingers-crossed:
[Magisk] Nebrassy:
I have to ask again, is it possible to disable force encryption only using magisk and without modifying vendor?

I don't quite understand what disabling the preserve force encryption option does, after wiping data the system still encrypts it, the only way I saw was editing fstab in vendor

any ideas?
[Magisk] angelillom:
Please I need help, I have a Huawei P20 lite with Magisk and TWWR and I want to update the OTA, my question is someone who would do it if you could help me in the sense of being able to watch a video of how to do it or a not very complicated way since every time I wonder they send me to an address and I do not understand English because I use a Google translator

The case is whether it can be done without damaging the system

First of all THANK YOU and I hope the help to not spoil the Mobile

I repeat ..... THANK YOU
[Magisk] mordantly:
No such luck in /data. Flashed 17.1 over top. Boot loop. Cleared dalvik and cache before reboot also. May have been caused by an additional issue as root was no longer working for tibackup and unknown sources wouldn't let me reinstall magisk manager. All apks "installation failed." Then the boot loop happened so the rom is a goner.
[Magisk] martyfender:
[MENTION=9052274]vfkkdamp[/MENTION] If it was not clear, I intended for you to uncheck those options then try again.
[Magisk] bafforosso:
Why on earth do you need both SuperSU and Magisk?
[Magisk] Crystal Ahad:
[/COLOR]

I was used Magisk and Super Su Separately so The Deffrence is Some module which are only available on Magisk and SuperSu System Root Has some Power to do Play with Android and it's very easy to use so some app which I couldn't find on Xposed . So the thing is I need some Specific Module for my Work and which are can not be find by one Root app.

thank you. It was good Question.
[Magisk] Didgeridoohan:
I'm confused... How are you expecting to use Magisk modules if Magisk isn't installed? True, there are couple of modules that are set up with doubled-up installation procedures and can install to /system of you're using SuperSU, but those are in minority. Just having the Magisk Manager installed won't make any difference, the Magisk infrastructure won't be available for modules to install to...

Magisk and SuperSU are different tools, pick one or the other for your purpose...
[Magisk] bafforosso:
I get the Magisk modules need but I don't understand exactly what you need SuperSU for that Magisk can't do.

My advice would be to try to get rid of SuperSU, because IMHO you have a very low probability of finding anyone that has need of both and who has a solution for you.

I think you would have better chances if you explain clearly what you need SuperSU for, so someone may have an idea how to get Magisk to do that instead.
[Magisk] martyfender:
I think you are only asking to have major problems and conflicts if you try to use SuperSu and Magisk together.
[Magisk] dope77:
Is it possible to disable verified boot from magisk? My device doesn't have any custom recoveries yet. It's already rooted with magisk patched boot.img. But I'm facing a lot of problems with the magisk, losing root, apps not working even after giving them root(they used to work perfectly earlier today), safety net was working properly but now it's failing. I'm planning ro reroot again but I'll have to reset the device bcz can't flash dm verify zip. So is it possible to disable verified boot from the boot.img before patching?
[Magisk] kerobrat:
I'm having this same problem - rooted pixel 3 xl, otherwise stock everything. Magisk works fine with modules and superuser and everything, but whenever I try the Hide Magisk Manager maneuver I wind up with it telling me I don't have magisk installed and I lose all magisk capabilities... All I can do at that point is uninstall/reinstall to get magisk working again...
[Magisk] brown1178:
After the last update of my bank's TAN service app (fiducia VR-Bank SecureGo), Magisk is detected and app closes. I already installed ProcGate app and applied the fix because my device was affected by the proc/ mounting issue. But my TAN app is still not working. Any additional steps needed? I already de- and reactivated all hide options for Magisk and magisk manager.
[Magisk] martyfender:
Did you clear the TAN apps cache and data?
[Magisk] brown1178:
Yes I did, and just to be shure I deinstalled and reinstalled the app
[Magisk] kf06925:
I also have my doubts about both working fine together.

If your problem is just the inability to download new Magisk modules, then you could try

1) just clearing the Repo Cache (Magisk Manager > Settings > General > Clear Repo Cache)

0r

2) if 1l doesn't help

clearing data for magisk manager (Settings > Apps > Magisk Manager > Storage > Clear Data)

This used to work for me when an older Magisk Manager didn't show me the modules.

After 2) you will need to apply settings again, e.g.for Magisk Hide...

I think it might still be better to list the modules you can't get via Magisk here 1st, however. Perhaps someone ran into the same issue before and has an idea how to do it without Super Su.
[Magisk] fleischbanane:
I have the same issue with version 18.17.7+. I use an old version (18.17.0) of the app which is working with Magisk Hide. I really miss the SMS TAN.
[Magisk] brown1178:
Can you please share the apk with me?

Found 18.17.0 in an older titanium Backup but still have the same issue. Have you reinstalled Magisk after applying ProcGate fix?

Reedit: forgot to select the app in Magisk Hide options after the downgrade. Now it works, thank's for the hint!
[Magisk] LuisFV97:
Thank you very much I was looking for a place where maybe you could listen to me .. and my question is DOES REALLY MAGISK EXIST FOR NOTE 4 Exynos N910C Marshmallow 6.0.1?
[Magisk] snbk97:
The game is string matching the package name of magisk manager, Go to settings, and press the hide Magisk Manager option, to repackage it with a different name. Also keep in mind that if you are using substratum to theme, you wont be able to theme magisk manager untill you restore it to original name.
[Magisk] kiwigi:
Hello Magisk'ers

After a year of my S7 running perfectly I did again the same mistake. I did turned of the OEM lock in the developer options with an FRP lockdown.

I managed to get back without losing data or Apps though have the following problem(see below) with Magisk. I am a bit scared to boot into recovery(as I do not know which recovery it has after this flashing) after getting back from FRP.

Can someone tell me the safest way to install Magisk?
[Magisk] Mrpookie:
Most likely reflash twrp via Odin then boot to recovery to flash magisk. Just my thinking tho, maybe wait for someone more familiar with your situation
[Magisk] Strephon Alkhalikoi:
Your thinking is sound, as I would have told him the same thing, even though my experience is with the S4 rather than the S7.
[Magisk] kiwigi:
Thanks guys/ladies

I did that but an error came up(locked) so I now have to install from magisc manager with patched image....huh:confused:...
[Magisk] guest4711:
A locked bootloader would not allow booting a patched image... AFAIK.
[Magisk] dimm0k:
HELP! OG Google Pixel XL was running Magisk 17.1 without any problems until I went to install the Greenify module and now my device keeps rebooting itself never making it to the system. I can boot into recovery, but TWRP won't let me mount a USB OTG drive to uninstall Magisk or mount Magisk to remove the offending modules. any suggestion?
[Magisk] yochananmarqos:
See my Collection of Magisk Modules v2 thread under the Unchanged Modules heading for a few ways to uninstall modules from TWRP.
[Magisk] dimm0k:
this worked!! thank you!
[Magisk] bafforosso:
Glad you solved this. Check the [MODULE] Greenify4Magisk thread as the bootlooping issue on all Pixels on Pie is well known and there are alternative solution to get the same result. My take is, as a rule of thumb, you should always quickly check any module's respective thread before installing it to avoid this.