yashsingh1/xdaforums huggingface dataset:
[Magisk] jcmm11:
Do you have adb access? Can you write to /cache/

If yes create a file in /cache/ named .disable_magisk (note the leading period) i.e.

touch /cache/.disable_magisk

Then reboot and you'll be able to remove the problem module. If you can't write to cache then your only option at this stage maybe to use adb to backup /sdcard/ then factory reset the device.
[Magisk] Cwiara24:
I tried. Nothing of that. I tried to install rom again, but without a result. it looks like root does not want to uninstall and is in memory.
[Magisk] jcmm11:
Flash stock, unrooted, boot image. Then boot to recovery, delete anything in /data/adb/ and flash Magisk
[Magisk] prestodigiti:
Modules cause extreme stuttering and lag on my Pixel when switching between apps and it's driving me crazy. Tried magisk canary but to no avail. Enabling core only mode restores the smoothness to the device. Does anybody have an idea what the cause might be?
[Magisk] mdrda:
Thanks for the tip. Though I had ADB accessible at that stage when phone was stuck on boot animation, no luck writing to /cache - permission denied. "su" was not possible in shell because I did not previously grant ADB shell root permission. I sorted out the situation because I was just lucky. One boot in many resulted finally in success even with the bad module installed.

What if the file could be placed for instance in root of internal storage or SDCARD?

I can hear the argument that this feature could be misused by any user app having storage permission. But an attacker would not gain anything interesting. Well ok, I wouldn't want anybody playing this game with my device to disable magisk modules, so maybe this is a good scenario?

- Magisk Manager allows a recovery keyword to be set under Settings; hash will be saved in Magisk directory

- In case of need for recovery the device owner could place a plain-text file .disable_magisk containing that keyword (or in case of a paranoid owner just the hash of that keyword generated externally on a trusted device)

- Magisk looks for that file during boot, if found, hashes are compared, if match => Magisk skips loading of custom modules

This could be a day saver for anyone who for some reason cannot run custom recovery and has no chance to access root filesystem other than booting into a working rooted Android GUI.
[Magisk] jcmm11:
I notice you posted a github issue (at least I assume that was you). You should have checked the existing issues - see https://github.com/topjohnwu/Magisk/issues/1286

My response is currently the last one in that thread and gives you a possible hacky temporary solution until something better comes along.
[Magisk] basily:
Like, even just normally flashing an OTA? Really? I mean, how do normal non-xda people keep their phones running? Or is it the mere fact of having the bootloader unlocked and the phone rooted that increases the possibility of issues?
[Magisk] jcmm11:
If all you're doing is flashing OTAs and everything is stock beyond that, no custom ROMs, no custom kernels then you'll probably be okay. But if that's the case you may as well take the over the air OTA upgrade (if you're on an A/B device)

And that's what normal, non-XDA people do, they just take the upgrades the carrier provides for them.

Yes unlocked bootloader's and rooting do increase the risk somewhat - rooting more so since a root upgrade can, possibly, lead to a boot loop. You can minimize the risk, you can't eliminate it completely.
[Magisk] kerpert:
Hi, I tried to install magisk 18.1 and 19 on Google Nexus S (Crespo) with

MM https://xdaforums.com/nexus-s/development/m-crespo-sources-t3241846

and even with

OmniROM 4.4.4 https://androidfilehost.com/?w=files&flid=140296

In both cases got "unable to detect target image".
[Magisk] Tecalote:
Thank you very much - thats a pretty useful information :good:
[Magisk] basily:
Yeah, that's my problem. I don't receive OTA's for some reason.
[Magisk] mdrda:
Yes it was me and did not see yours. Same reasoning. I will look in to it, mark duplicate or otherwise resolve the dup submission.

Update: JohnWu resolved it for us. Marked as reference. I think it's fine, no more action needed. Also the good news is some sort of implementation is coming.
[Magisk] Strephon Alkhalikoi:
More than likely it's because you have an unlocked bootloader. I keep my P2XL unlocked and as a result have to manually flash a full OTA through TWRP every month, followed by TWRP, then Magisk. I would go so far as to say you must be completely stock (i e. no TWRP) to automatically update via OTA, as well as have a locked bootloader.
[Magisk] Ferr1s:
Hey guys. I m on a Xiaom Mi8 with lineage 16 and magisk. But NFC payment and some Banking Apps are not working. Is there a know issue with magisk hide? The Banking or payment Apps recognizes the unlocked and rooted phone. Or is it a phone specific Problem?

Gesendet von meinem Mi 8 mit Tapatalk
[Magisk] jcmm11:
No TWRP is correct. Magisk hides bootloader status though
[Magisk] Wolfcity:
I tried to update to magisk 19.0 a second time. The first time I updated directly from 18.1 in magisk manager and ended with the device rebooting into TWRP without an option to boot back into system. So I used magisk-uninstalller-20190204, flashed 18.1 afterwards without a reboot in between and the OS booted again.

Now I did a second attempt. Booted into TWRP and flashed magisk-uninstaller-20190328 (which may have been a fault as it's the latest build and probably just for uninstalling 19.0 and not for 18.x ?)

After trying to flash magisk19.zip I couldn't boot into system or TWRP at all, the device only booted into stock recovery fastboot mode, stays there and gave an error message about a corrupted/not reachable boot.img, Foolishly I don't remember the message exactly.

TWRP or OS weren't available anymore at this point.

I connected the device via usb to my pc and flashed my original boot.img with fastboot.

After that I was able to boot into the OS and TWRP was available again too.

Flashed magisk18.1 and my modules again using MM and everything was ok.

I did that procedure late at night (never a good idea) so I forgot to save the recovery last.log, the actual log only shows the flashing process of 18.1.

I would like to repeat this attempt, this time with proper debugging logs/screenshots and remembering the exact error message....;)

I intend using magisk uninstaller-20190204 this time and before I start over I wanted to ask if anything else except the recovery last.log is needed or may be helpful and also if someone can give me a hint to be more successful this time.

I did all that on my testing device:

Moto G 2014 (titan)

Aosp Extended 4.6 (Android 7.1.1)

Cerberus kernel 1.1
[Magisk] timg11:
Magisk 18.1 install on new Pixel 3: Failures in restoring backups

I'm a first time user of Magisk, previously using systemless root on a Note 4.

I'm setting up a new Pixel 3 (Android 9), and restoring backups from the Note 4 (Android 6.0.1).

I have successfully installed Magisk 18.1 and Magisk Manager 7.1.1 (203) using the Boot Image Patch method (no TWRP) .

I find that both of my backup and restore programs (Titanium Backup Pro and Rerware MyBackup Pro) are unable to restore to the Pixel 3.

I posted this question in the Pixel 3 forum.

The only post I found about the issue with MyBackup solved it by changing rooting methods, but it was with LineageOS.

Do these issues have anything to do with Magisk?
[Magisk] jcmm11:
Titanium works with Magisk, for sure. I suspect the problem is more moving from Android 6 to Android 9 and that there are incompatibilities in the data structure (although I don't remember details from 6) plus possibly ownership issues etc.

How many apps are we talking about here that you really need data restored for?
[Magisk] timg11:
There are probably about 20 apps that Google did not restore for various reasons. Some are no longer in the store, some were side-loaded, some the reason is unknown.

It is not just about the data - that is secondary.

The same problem occurs with an APK-only app restore.

Also, installing an app from the store onto the Pixel 3, backing it up, and then restoring it also fails. The restore process fails, and the app is gone after the process. In that case, the legacy OS version is completely out of picture, yet it still doesn't work. It is also strange that two different backup programs are failing on restore.
[Magisk] Cwiara24:
Did not work. I think I have to wait for a stable version ... I tried everything

regards
[Magisk] Darione90:
hi, there is a way (when i have magisk installed yet) when i reflash magisk to not allow to install magisk manager since is installed yet? because after reflashing from twrp and reboot i have 2 magisk manager installed
[Magisk] garylawwd:
You hid Magisk manager in its settings which gives the manager a different package name and when you flashed magisk again it thought you had no Magisk manager so it installed it again.
[Magisk] jcmm11:
Sideloaded apps should still get updated from the Play Store, although may not get autorestored if the most recent update was a sideload (not sure).

I can't tell you why the restore programs are failing, although a logcat would certainly help. From the sound of it though something strange is definitely going on.

I can tell you that if you go into the titanium backup directory you'll find, probably tar.gz but depends on compression method chosen in preferences, files for each app. One of those files contains the apk which you could extract and sideload. Another contains data, which you may be able to manually restore, have to try and see if it works and I wouldn't even bother trying except for apps where the data may be critical. Another file is text formatted "properties". Should be obvious which is the apk backup.
[Magisk] arpit1992:
Constantly getting Error downloading file (MagiskManager v7.1.1(203). Using pixel ROM on Moto G3 phone. Currently on Magisk version v18.1
[Magisk] Shotg1:
Latest magisk 19.0 and magisk manager i really don't know if the magisk manager didnt hide root permission,i bank app detected that my device is rootedpe there is fixed
[Magisk] android_smater:
Latest version, bank app (Imobile by icici) detect root
[Magisk] martyfender:
For any of you module authors who don't follow [MENTION=4470081]topjohnwu[/MENTION] 's twitter feed, he wrote this:

So I would suggest that you all update to the new template before he removes your modules!
[Magisk] Gourcuff14:
Hello. I'm having trouble running Viper4Android FX and Ainur Sauron on Magisk v19 and Manager 7.1.1 (203). It was working before with the Audio Mod Library module but now it just says abnormal in Viper. Is it update related? :eek: Thx
[Magisk] bafforosso:
Hello,

using Magisk v19 (19000), MM 7.1.1 (203) and V4A FX Magisk Module here and everything is working perfectly (Pixel 3 on Android 9).

Your issues seems module-related and not Magisk related so you should ask in the module specific threads :

Viper4Android FX Module

Ainur Sauron
[Magisk] timg11:
I flashed the April update for the Pixel 3 before installing Magisk. 9.0.0 (PQ2A.190405.003, Apr 2019)

Are there any known issues with Magisk and the April update? Does it work for anyone else?

What firmware are you using?
[Magisk] jcmm11:
Pixel 3 XL, stock 9.0.0 (PQ2A.190405.003, Apr 2019), Kirisakura kernel

Canary Magisk

It's working fine here (including Titanium)
[Magisk] zputnyq:
Tried magisk v19 but revert back to v18.1.

Magisk v19 successfully installed with no issue but then after booting was finished sim card wasn't detected.

Xperia M4 stock 6.0.1

Nautilus kernel.

My apology, I can't provide any logs for now, since this device is my daily driver.

Thanks before for everyone here.

I really appreciate it
[Magisk] timg11:
Did you install TWRP or did you use boot image patch?
[Magisk] jcmm11:
Boot TWRP using fastboot. Device recovery is stock
[Magisk] stab244:
OP3T on stock OOS 5.0.8. Just this morning I keep getting magisk not installed errors. I've tried reinstalling the ZIP for 18.1 in TWRP multiple times and it doesn't work still. Magisk manager app is 7.1.1 and being hidden with a random package name. Should I try flashing the base ROM to get rid of magisk patches and reflash magisk after?

Edit: fixed. Seems it had both the patched and non patched magisk manager installed and the non patched was taking control but I could only see the patched one in my apps list.
[Magisk] MasterPhW:
Did anyone got Magisk 18.1 or 19 working with the newest MIUI 10.3 9.3.28 rom on a MiMix2 (not S)? Always ends up in two tries to boot and then back to TWRP recovery.

Should I try a canary build?
[Magisk] Gourcuff14:
Hello. Thank you. My fault fix found sorry. yes to open/close option during install

https://xdaforums.com/showpost.php?p=79251694&postcount=4632
[Magisk] dwaipayan774:
Hello,

I have A Coolpad Y83-100 running A VibeUI Custom Rom based on MM. I have flashed Magisk V19 on it and the installation was successful , but on booting Magisk Manager shows that Magisk is Installed but Core Only Module is Enabled.I have tried disabling it , but it is re enabled after a reboot .Hence , I can't use any modules.

I can still use root and apps like Titanium Backup and Greenify works but I cant use Xposed (I have even tried Non-systemless version) or any other modules .

One thing to note that when my Phone was on the stock ROM , Magisk worked just fine.

OS:Android 6 SDK 23

CPU Variant: aarch64

ROM: VibeUI MM

Magisk Log: https://pastebin.com/z6B6rkVg
[Magisk] Flegmon:
Device: Samsung Galaxy J5 2016 (SM-J510FN)

I can't boot to system with v19 installed. It just throws me into recovery. Only way to boot to system is to use v18.1 or without magisk at all. I tried uninstalling before flashing v19.
[Magisk] garylawwd:
What version of android you running.

I have j5 2015 which has the same SOC and dont have any trouble.

Might be rom related and not a Magisk issue
[Magisk] xcodejps:
Hello. I have unlocked p smart 2019 but no matter what I do or what version Magisk I use i only get bootloop. POT-LX1 EMUI 9.0.1.152

Do Magisk support Kirin 710 chip? Thanks

Išsiųsta naudojantis POT-LX1 Tapatalk 4 Lt
[Magisk] Flegmon:
Xda bugged a little on my side and didn't save my edit. My fix was to just update the kernel but I'll still wait for the "full" release of v19 and stay on v18.1
[Magisk] garylawwd:
Latest stable of Magisk is v19 though

Edit: nope im wrong sorry
[Magisk] Digitarier:
no, the problem is, that the system tells me, that the SD card is 'damaged'. right before the Update i used the card normally with 'Total Commander'. no reboot or installation via TWRP helped :rolleyes:
[Magisk] Dims_Camper:
Hi guys, anyone using app called "Grab Driver" here? I've been running it with magisk v18.1 just fine but suddenly the app detects root from nowhere, i think because the app is updated frequently. Just updated to v19 to see if updating magisk helps, but no. It's still detects root. Does this app scans my entire storage to makes sure there's rooting method called magisk / root or something? Anyone can help? Thanks.

The app called "Grab Driver" bit.ly/2Z0vD04

Edit : i think by giving ".nomedia" on a folder where there's a file called magisk / root is kinda fixing the issue here.
[Magisk] asmen5:
The banking application (bri mobile) that I use still detects the root, even though it already uses hide magisk & hide magisk
[Magisk] Dims_Camper:
Try updating to magisk beta v19, it works fine here with that version.

Edit : also try to hide magisk manager and add the bri mobile app to magisk hide.
[Magisk] StonebridgeGr:
Hello there

Direct install option is missing , why. ?

P20 pro stock, stock recovery, last version of magisk manager
[Magisk] jenslody:
It should only be missing if MagiskManager detects the device as not rooted.
[Magisk] paschal MK:
I need itel 1406 rom update please
[Magisk] xunholyx:
This thread is the wrong place to look for it.
[Magisk] xcodejps:
Hi, Can somebody give me some insight why Magisk any version don't work with kirin 710 Huawei P Smart 2019 POT-LX1 ?? I always get bootloop no matter what patch options i use (force encryption, verity) If I hold vol up 2-3 times every bootloop and then stop pressing anything then huawei boots up but in safety mode where all apps are disabled and then i have to select what apps to delete.

Please help I am so hungry to root my device
[Magisk] StonebridgeGr:
hmm but i am trying to root it and missing, not just for me, for every user of this phone
[Magisk] garylawwd:
So you just have Magisk manager? You didnt actually install the zip?

You need to flash Magisk before you can do anything with it the manager isnt enough. It cant do a direct install due to missing root privelages.

You probably need to flash through fastboot on a computer
[Magisk] Sujalshah:
Permission popup only appear if my magisk manager is open in background. Otherwise it dont shows grant or deny popup in redmi note 4 (mido).
[Magisk] madbat99:
If you have root already, as owner, and want to share root with other users, look in settings. If you haven't rooted the device at all yet, and don't have TWRP, you need a copy of your boot.img. Then you can use magisk manager to patch it. Then flash the patched image with fastboot, or whatever tool is used for flashing img files on your device
[Magisk] martyfender:
I don't think he is referring to multi users, but to other owners of the same type of device?
[Magisk] SeasameG:
How do I update magisk to the latest version directly using the manager from a 1.6.0? I do not see any option in the 6.1.0 manager and 7.0.0 and up do not support 1.6.0.
[Magisk] Captain_Throwback:
Are you sure Xposed is completely removed or disabled? Because that's the main thing that would prevent the app from working, I bet. You may not have had a clean uninstall.
[Magisk] db77:
I try before, but return on SuperSu 2.76 Magisk to test.
[Magisk] hammerhead2:
Fair point.

But after brief check with fx explorer, also using search feature, I cannot detect any remains of xposed though.

Any specific locations I should go to?...
[Magisk] Captain_Throwback:
/magisk/xposed would be where it's installed, if you're using the Magisk version. Previous versions were in either su.img (mounted at /su/xposed) or xposed.img in /data.
[Magisk] hammerhead2:
That's exactly where I went.

Nope :)
[Magisk] Girish_J:
Ohh okay.. So putting fonts/file.ttf in system folder of template would work?

Edit: with proper permissions

Thanks
[Magisk] locolyric:
Yes ! i had xposed and it is very important to me , amplify and greenify is a must!

But everything work flawlessly before i flash another zip file !

I had no idea why a zip file will give me this result.

---------- Post added at 11:23 PM ---------- Previous post was at 11:12 PM ----------

Re-flash magisk doesn't help. I think i need to re-do the whole process to get magisk to work again.

Any idea why magisk doesn't work anymore ?
[Magisk] raleva:
For me works for two days, but know i witch off root on magisk but pokemon doesnt work... Any ideas??
[Magisk] an0n981:
Yes I have an idea, probably even the correct idea, but please ask your PoGo question in the PoGo Magisk thread.
[Magisk] skeleton1911:
deleted. all ok
[Magisk] Green_Arrow:
can't update

Hey, i have magisk installed in my nexus 6 but i can't update from 5.0 to 6.0 anymore, any advice. i have phh superuser as well
[Magisk] Galaxy Y User:
Does the uninstaller remove magisk completely or just partially?

I have this game called Fate Grand Order and it prevent rooted phone from playing it. Basically if it detect any kind of root or system modification access, even things like adb or developer mode, it automatically kicks you out of the game and send you to your default email app with an error code, in case of root it present code 60.

So I want to try Magisk to see whether or not it can be detected. I flashed just the installer and nothing else, and when I started the game it give me the error code for root. Tried to clear the cache/dalvik but still no effect. I decided to uninstall Magisk. But even after uninstalling and wiping cache/dalvik the game still detect that my phone have root for some reason. Is there a way to completely remove it?
[Magisk] got2best:
Precisely! The file name is notocoloremoji.ttf (android 7 idk if this changes per version) in system/ fonts .. I renamed the current file to "notocoloremojiold.ttf" and added the replacement. Then you have the old file if needed. I don't believe I had to change any permissions either. Just make sure the permissions match. Then restart after placing files using FX explorer .. thread I used http://xdaforums.com/general/general/mod-google-keyboard-unicode-9-10-emojis-t3348544/page1

Includes new emoji Unicode that will be added to iphone eventually

Sorry for off topic should probably use linked thread for further questions regarding emoji.
[Magisk] requiiiem:
anyone can adapt this v4a for nougat systemless?

http://androiding.how/install-viper4android-nougat/
[Magisk] JudgeDread11:
If that other zip modifies the system it will not pass safety net.

Don't use anything that modifies the system. Try to convert the other zip to an magisk module.

---------- Post added at 06:08 PM ---------- Previous post was at 06:06 PM ----------

As far as I know Magisk doesn't disable encryption. It should work with our without encryption.

---------- Post added at 06:14 PM ---------- Previous post was at 06:08 PM ----------

'Remove with SuperSU' seems to not always remove all traces of SuperSU. Before flashing phh's superuser check with trout verifier if there is anything left. Of there is anything remove it manually or use the unSU script.

---------- Post added at 06:15 PM ---------- Previous post was at 06:14 PM ----------

Did you Israel the USB drivers?
[Magisk] got2best:
Would it break magisk? Or not work? Tested already? Full backup and then install and see if anything breaks?
[Magisk] CooperBrick:
doesn' t work

when i toggle root toggle in magisk manager it automatically turns off. What to do?
[Magisk] Rls4ever12:
Flash unsu zip just google unsu zip XDA and you will find it
[Magisk] Iceyogurt:
Bug report: some files are not mounted.

I have been using the v4a-magisk.zip for nearly a month and everything works well. But today when i tried to make the overlay themes a magisk module, I found that files under /magisk/v4a/system/vendor/etc were not be mounted if /magisk/***/system/vendor/overlay appeared. Under this condition, only files under the latter directory will be mounted but not the former.
[Magisk] wolke7:
OK, removed su form my cyanogenmod 13 and all (incl AutoMagisk) works now like a charm. Thank you! :)
[Magisk] warrencoakley:
Go into Magisk settings at change to Beta or Custom. I'm using Carney. Give it a few minutes and it push the updates for you to install via your phone and not having to use TWRP.
[Magisk] Digitarier:
I got the full card access 'back'...unfortunately I had to downgrade to v18.1
[Magisk] tufyuma:
Error when installing on Android Q

getting error when trying to install Magisk on latest Q Build, on a Google Pixel XL

-failed to mount '/system' (invalid argument)

-failed to mount '/vendor' (invalid argument)

tired with v18, v19 and canary builds

tried uninstalling , it got the same error

tried installing latest Kirisakura-kernel (for P and Q) (it got the same error, but shows as installed in settings and it "saw" magisk was installed)

the only weird thing I might be doing, I haven't installed twrp I use the fastboot command with the latest version

fastboot boot twrp-3.2.3-1-marlin.img

thanks, any help would be appreciated!~
[Magisk] George_Bushels:
I get the same errors but it installs. For Q i am using Magisk-v18.2-e476c18c.

https://xdaforums.com/showpost.php?p=79271368&postcount=1282

You may need to uninstall magisk first. Use the latest uninstaller.
[Magisk] tufyuma:
I tried to uninstall (using the latest and beta), but I get the same error as when I try to install, Magisk Manager says it's not installed and I can't update my buildprop file, so i'm thinking it actually is not installed (or installed correctly).

I'll try the same version you did , when I get a few minutes.

Thanks!