yashsingh1/xdaforums huggingface dataset:
[Magisk] hoangbk56:
Anyone show me how play 0.3.7 in my Sony Z1c???
[Magisk] Anonaru:
Absolutely zero problems getting everything to work on the HTC One M8 with the ICE M8 8.1.0 ROM and stock kernel! I expected things to go a bit rough since this isn't a fresh install and I had previously used other ROOT methods on it. Uninstalled them and threw all this in, didn't even try to mess up on me :D

Thanks for the awesome work!
[Magisk] d.calasans:
Hey, I own a XT1097 too, but every single time I tried to install magisk, I got the boot up error.

I've tried to install it on the stock ROM and on CM13 and it failed with both.

Did ou have the same problem? How did you solve it?
[Magisk] Kiid:
[MENTION=4470081]topjohnwu[/MENTION] is it possible to manually resize magisk.img while it's mounted? I want to manually add files to the /magisk folder but the space is maxxed out and won't resize automatically (I'm guessing it'll only do that when flashing from recovery with Magisk modules). I've had no success with creating modules but manually adding files to the /magisk folder works fine.
[Magisk] jaffa1980:
Ok so I've been reading up on this and I think I have it... Just to be sure before I brick my phone... This is a g4 and that can be a BIG deal lol.

So I install my rom (minus xposed, I know I can't get rid of root). Wipe. Boot up and Uninstall/unroot (or just flash unroot zip?). Flash magisk. Wipe. Flash root. Wipe. Flash xposed. Wipe. Flash unsu.zip. wipe and keep fingers crossed..... Does that about do it?

Lgg4 unlocked bootloader

6.01 imperium Rom v5 (soon to be v6 when I'll do this)

Thanks guys
[Magisk] topjohnwu:
It is not possible because the image is at use. However, there will be a way for you to install your own modules with Magisk Manager (without custom recovery), with any size in v7. A reboot will then enable the installed module.

The next template will be so easy that even people who only knows how to copy folders can create a module in a few minutes.

It is a bad idea to mess with the folders in Magisk directly, since they are most likely to be mounted and unable to modify. The best way is to update/add the files through a module install, either with recovery or in app (about to be released). That is also why the "modules" concept is introduced.
[Magisk] Rls4ever12:
Fixed probably not a developers way but I flashed magisk uninstaller, flashed SuperSU, flashed arise, rebooted to make sure it was working then flashed unsu, flashed magisk, flashed phh, rebooted and all is good.
[Magisk] Kiid:
Thank you for the response. Looking forward to v7 ??
[Magisk] wpan2002:
Device: OnePlus X E1005 (North America Model)

Operating System: CyanogenMod 13

Carrier: Rogers Communication

(Like Canadian Version of AT&T)

Location: Canada

SuperUser Application: PHH's SuperUser (Systemless TopJohnWu Version)

When I finished flashing following all of the steps nothing works when I open the app toggle off root the moment SuperUser grants access it turns back on the issue is same with Chainfire's SuperSU. (I reflash CM13 when I switch the Superuser applications to make sure there is no remaining files) it still doesn't work same results Toggle off then Root Granted then turns back on.

I googled it nothing... I searched up OnePlus X Magisk CM13 won't toggle.

---------- Post added at 09:58 PM ---------- Previous post was at 09:55 PM ----------

Please Learn how to read
[Magisk] Hyflex:
Would this work with CyanogenMod or does it have to be stock?

Also, can someone list the instructions?

I want xposed, viper4android (don't care what root, whatever one is "best")
[Magisk] joshuaw84:
OP has all the info you need for instructions, as for custom roms YMMV. I'm not on CM but suspect your answers lie within the thread already.
[Magisk] Hyflex:
I've read the first few posts several tonnes and I can't see the answers I am wanting, he specially mentions instructions for stock roms with root uninstalled.

I've used search and read lots of posts but there are tons of results because this thread is now 355 pages long...
[Magisk] joshuaw84:
The OP mentions stock roms because he cannot support every custom rom out there, that would be silly to take on. I'm running venomroms which is supped up sense rom with no issues. Like I said YMMV.

Just make sure to get rid of any root that comes packaged in the rom zip. You'll need a root that supports systemlessness (which are also in the OP) ?.
[Magisk] heslo.rb26:
This works PERFECTLY on my HTC10 running LeeDroids ROM and ElementalX kernel! Thanks so much for your hard work!

One question though, say a new version of LeeDroid is released, or a kernel for that matter... what steps do I need to take to update and keep Magisk still working?
[Magisk] ruifung:
Flash ROM / Kernel > Flash Magisk.
[Magisk] browny_amiga:
Bootloop after installing Xposed Framework via Magisk

Hi,

I have been using Magisk for a long time now successfully, but need the Xposed framework. After installing it, I get into a boot loop.

Disabling the module does not work, when flashing the mod disabler and then executing

uninmod in the TWRP terminal, I get:

/sbin/uninmod: line 41: setup_bb: not found

Magisk Module Uninstaller

magisk.img not mounted

So uninstalling Magisk fixes it again, but I cannot use Xposed without the Phone (a Galaxy Note 4, running Android 6.0.1) going into a boot loop.

Is there another solution? Is maybe the packaged version of Xposed the problem (inside Magisk), it says it is the official one packaged by topjohnwu, updated on Apr 30, 2019

This is with Magisk Version 19.1 and Xposed Framework Version v90-beta3
[Magisk] wilsonhlacerda:
Read my post (wilsonhlacerda) on page 807 here:

https://xdaforums.com/xposed/unofficial-systemless-xposed-t3388268/page807

There are also other tips on the following pages. But a notice: the Xposed on Magisk repository is the newest pack (and I'm using it as I wrote)....compare the dates inside zip if you want to be sure.
[Magisk] jcmm11:
For Magisk 19.1 there is no more magisk.img and you don't need uninmod. Just use file explorer to go to /data/adb/modules/ then delete the relevant folder.

To disable a mod simply create a file named "disable" in the relevant directory.

To disable all mods and boot Magisk in core only mode place a file named ".disable_magisk" in /cache/ or /data/cache/ (depending on your phone).
[Magisk] Redline:
Correct, though I switched to Canary after 19.0 came out and I was on stable 18.1, haven't had any issues.

You could try moving to Beta if you want a good mix of the newest fixes and stability.
[Magisk] BROKEN1981:
Where is that thread? I can't seem to find it. Updating to Magisk 19.1 causes bootloop and looking at how to fix that.
[Magisk] MattP410:
I've tried installing v19.1 numerous times on my Mediapad M3, and after rebooting I'm presented with a screen that says "please enter password to decrypt storage." This has never happened with any previous Magisk releases. On top of the fact that I'm prompted to enter a password, there's no keyboard to enter it. If I reboot to recovery and reinstall v18.1, everything is back to normal. Has anybody else experienced this, or have any ideas? Thanks in advance for for any responses!
[Magisk] zgfg:
You can enter decrypt or storage to the Search box (top-right) - the same issue was reported/discussed but so far only for Huawei phones with Nougat.
[Magisk] MattP410:
Thanks for the reply. It appears there's no fix for this yet. No biggie. I can use 18.1 until the next stable release comes out. It's good to know it's not just my device. Thanks!
[Magisk] levone1:
KEEPVERITY=false, and KEEPFORCEENCRYPT=false not working for me on latest stock security patch, (Sony XZ2c). Boxes keep being re-checked on boot... Using 18.1, and didn't change anything else...

Thanks
[Magisk] jcmm11:
To use those boxes you have to patch a kernel after selecting them. Otherwise there's options that go in /cache/ (/data/cache/) before flashing Magisk via TWRP. Don't remember details of the top of my head. See https://www.didgeridoohan.com/magisk/MagiskInstallationIssues for details
[Magisk] levone1:
Thanks. That's the same thing I had been going by. On previous rom version, (April patch), I could flash Magisk, reboot to recovery and use terminal, (or adb), and enter echo commands, and reboot, and they would both be unchecked. Now, on May patch, with fresh install and no other mods, (just TWRP and Magisk), it doesn't work. I have tried to echo .magisk file in /data, /cache, and /system, and I have tried to do it before and after flashing, but boxes always re-checked...
[Magisk] levone1:
Nvm - not sure what did it, but I just started all over, and tried again, and working now... Thanks
[Magisk] smart123123:
Crashing... I am having moto e4 plus(nicklaus).. with custom rom rescrrution remix....
[Magisk] Didgeridoohan:
What is crashing? You'll have to be more detailed than that when asking for aid...
[Magisk] smart123123:
Sir magisk app is crashing ... Specially after restart or while giving super user permission...
[Magisk] smith8ca:
I apologise if this has already been brought up. I did a few searches and couldn't find anything ...

I have a few apps that have been added to the Magisk Hide list (Outlook for example). It looks like Magisk Hide reinitializes every 5 or so minutes. If I have Outlook open when this happens, it force closes. Is anyone else experiencing this?
[Magisk] Didgeridoohan:
Magisk log won't show anything about that. You want a logcat:

https://didgeridoohan.com/magisk/MagiskHelp
[Magisk] guest4711:
Try cleaning cache and data of Manager app. This way you don't lose the permissions and your hide list, but you have to re-enter some settings probably.

If this does not help, it may be a problem with your magisk.db located in /data/adb

Stop Manager app and move the db out of the way (rename it to magisk.d.bkup e.g.) If this helps, it was a faulty database and you have to re-grant permissions and setup your hidelist. If not, you may restore your old database and try other suggestions.

Good luck!
[Magisk] smart123123:
This log file is just after the crash... Check it out...!!!
[Magisk] guest4711:
It does not show anything except the line "-- beginning of crash" at 2019-05-17 20" After that all was normal until end (2019-05-18 14:14). We neither know what did crash (if any) nor why. To investigate more we'd need the detailed log (from canary-logs-build) and your logcat.

Did you try the recommendations from my previous post ( https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post79543605 )?
[Magisk] Al-Bcherrany:
Hello need some help please, i rooted my A/B partitioned device by patching stock boot.img and flashing it via fastboot and it worked flawlessly, however i tried to unroot by restoring boot.img, complete uninstalled and it worked, but after restarting my device System UI kept crashing and phone became unresponsive and laggy, any insights on this ?
[Magisk] guest4711:
No insights, but probably wiping of cache and dalvik could help...
[Magisk] Al-Bcherrany:
The thing is mate i'm not using TWRP recovery, also with stock recovery there is no wipe cache and dalvik option, i tried also factory resetting my device but it's still there, so i had to flash again the patched img so i can use my device normally
[Magisk] guest4711:
Fastboot TWRP (not installing it) and wipe from there. Or by using ADB?
[Magisk] Al-Bcherrany:
By using fastboot ADB, no TWRP
[Magisk] smart123123:
So whats that... Com.android.google.gms.unstable!!!
[Magisk] FoOlKeN:
I have a problem when i try to root my Samsung A600fn (android 9)/magisk 18.1 with twrp after all process i cant connect to samsung account (processing failed toast), cant use fingerprint or facelunck and when i try to put a password or a Pin it request to confirm it but say its incorrect...But when i was on android 8.0 all works perfectly:rolleyes:help me pls
[Magisk] guest4711:
Thats a normal google service, beta version of google play service AFAIK. And root is hidden for it by default.
[Magisk] martyfender:
Actually, it is a component of the stable versions of Google Play Services, also.
[Magisk] smart123123:
So is it normal??
[Magisk] Didgeridoohan:
Yes. As has been stated already, the log you provided looks completely normal. And its also been stated that the log you've provided is the wrong one for the purpose...
[Magisk] smart123123:
Then how should i extract the crashing log...??
[Magisk] Didgeridoohan:
Look back to the answers posted to your query. I've already provided you with that answer.
[Magisk] Estebanium:
Hi there. I use LineageOS 16 on a Samsung Galaxy S7. Moreover I use NanoDroid that is a replacement for OpenGApps, which is installed systemlessly as a Magisk module.

I noticed that there are some problems with encryption and Magisk and I would like to ask if anyone has similar problems.

The problem started when I decided to encrypt my phone for security. This process was successful and at boot I was asked for a password. I entered my Pin and the phone booted successfully. However I noticed that all my modules were vanished that was a real problem, because all Google related Apps were crashing, because NanoDroid was now gone.

I turned the phone off and started it again. The modules came up, maybe just a restart was required.

The problem itself is not a big deal as it seems that a reboot can help to get the modules back, but if you use NanoDroid or MicroG in conjunction with Magisk this can lead to big problems.

I needed to reinstall a lot of apps, because reseting them didn't help. They still crashed at startup. So I would recommend to encrypt the device before using any Magisk module for better compatibility.
[Magisk] RigacciOrg:
Is Lazy Flasher (DM Verity Disabler) still required with Magisk v19.1?

I found several recipes on the net for installing TWRP + Magisk on my Xiaomi Redmi 6 phone. Many of these say to install a DM Verity Disabler (a.k.a. LazyFlasher). But I installed only TWRP 3.3.0 and Magisk 19.1. I can boot into System and into TWRP, su is working. Should I still install LazyFlasher?
[Magisk] kotuamoalt:
No.
[Magisk] scornacchia1:
Wifi on Samsung galaxy s9 plus

Hi i installed 18.1 on Samsung galaxy s9 plus and everithing was good but after i've updated to 19.1 Wifi doesn't work...
[Magisk] kotuamoalt:
This begs the question; Why are you not just using g apps?
[Magisk] Estebanium:
I don't want to use Google's Framework or at least try to avoid as much as possible of G's Framework. So I stick to NanoDroid.
[Magisk] kotuamoalt:
I'm sure you must have your reasons...
[Magisk] tcat007:
Just want to report an issue (5t). I'm on Derpfest rom. When trying to flash a custom kernel (Weeb, or any), phone boots to lockscreen, unlocking goes to "phone is starting" screen which never ends.

Can restore default boot partition and all is good.

Can uninstalled magisk (19.1), and all is good (with new kernel or default).

Can install magisk 18.1, and all is good.

Update to 19.1, and stuck on 'phone is starting'.
[Magisk] AndrzejDwo:
Grab logcat via ADB or boot script and include it into your issue report. For more info visit:

https://didgeridoohan.com/magisk/MagiskHelp
[Magisk] uudruid74:
That will help. It says it patchedbit, but flashing it gives a dead system, so maybe someone there knows what's up.
[Magisk] Held der Arbeit:
I can not flash Magisk 19.1 on the Teclast M20. It only works until 18.1. Is 19.1 not compatible with Oreo?
[Magisk] CobalTitan:
Hi, I was able to install Magisk v19.1 on my Galaxy S5 safely but reboot after for the second time, it is impossible to get any module afterwards. An mistake of accessibility file to the root decompressing prevented from the module. If return to v18.1 not problem.
[Magisk] guest4711:
No problem here with S5 on pie and magisk 19.2

Perhaps one of your modules is outdated/incompatible with current magisk? Try one by one to get the culprit...
[Magisk] chenrp:
Can't update from 18.1 to 19.1 on my hot pro plus andoid 7.1
[Magisk] garylawwd:
Use Magisk uninstaller and then flash 19.1 afterwards.

Just do it all in recovery
[Magisk] AndrzejDwo:
Hi! I was wondering lately if new versions of Magisk uninstaller are compatible with previous versions of Magisk. Because when there is new Magisk release there is also new uninstaller release. Should I always use it 1 to 1? Let's say that i'm on v18.1, and I would like to make a clean start with 19.1, then should I use only the uninstaller released with v18.1, or the one released with v19.1 is compatible as well.

Sorry for a mess, but it is very hard to me to describe it anyway simpler.

Just to be clear, I'm not having issues with Magisk, I'm on latest Canary and everything is fine. But I would like to know what are the dependencies between releases.

Thank you!

Cheers
[Magisk] kotuamoalt:
???

---------- Post added at 09:08 PM ---------- Previous post was at 09:07 PM ----------

The latest uninstaller should work on previous versions, also.

---------- Post added at 09:25 PM ---------- Previous post was at 09:08 PM ----------

It is.
[Magisk] demonoidmaster:
Ya **** is too old, that's why. Also modules can just be deleted (their folder) if ya go to /data/adb/modules and delete the modules folder or to be safe move it elsewhere (like say your internal storage)

Use magisk and Magisk•Taichi, also you'll need the Taichi app

---------- Post added at 10:47 PM ---------- Previous post was at 10:39 PM ----------

That's normal, GMS has various subs, Unstable is one of them and usually only runs if GMS is well a bit unstable, if it's selected in magiskhide (GMS as a whole) this entry will show up in the log along with other kinds
[Magisk] dope77:
The new dark mode is really horrible, can u plz bring the old one back?!
[Magisk] guest4711:
I love it.

De gustibus non est disputandum.
[Magisk] abdullahk6809:
Anyone help me,,,

Whenever I used Arcai.com Netcut app The Magisk Manager App donot open untill i reboot my phone on whatever rom i used after opening netcutapp magisk won't open/run until i reboot my phone...

Device:Nexus 6p Rom: Lineage OS 16 Unofficial

TIA.
[Magisk] nacos:
Is this a joke of some kind? Ever since the realease of 19.1 tons of people with different phones, running "older" Android versions have been complaining about it not installing or having boot loop issues. Version 19.2 has the absolute same problem on my Samsung S8 (SM-G950F): it appears to be going through all installation steps without any problems and yet after rebooting, it's reporting not install. As for those insisting these are fake reports, or isolated cases or that it miraculously works if only installed through recovery, please stop. It just doesn't. 18.1 is the last version that works on all phones that keep reporting this problem and it seems the devs are just content with the situation. Should we take this as the end of Magisk support for all phones running Android 7 and older? Is this by design?
[Magisk] smart123123:
Finally... Updated to 19.2 and till now no report of crash
[Magisk] AndrzejDwo:
My Samsung SM-A510F on Android 7.1.1 is running just fine with 19.2. It was fine also on 19.1, 19.0 and 18.1. Most of the issues I have seen here are with Xperia phones and phones based on MIUI. The rest of problems are most likely created by users.

Cheers
[Magisk] z-vet:
OK, so here's mine: I can't update, Magisk Manager stopped working after update. I tap on Update, the installer is asking if I want to update the Manager, I say yes, it installs and then refuses to open. After couple of tries I get a system message about the app that keeps crashing. What can I do to fix this issue?
[Magisk] zgfg:
Problems on Huawei and Honor phones with Android 7 were described and here with tickets opened on GitHub - fake reporting by v19.x password is needed for decrypting storage, then that storage was 'corrupted' and that user must do Factory reset.

But flashing v18.1 back and no problem with the storage, password, corruption whatsoever)

And still the same problem on Huawei P9 with Magisk v19.2
[Magisk] nacos:
I just tried installing 19.2 on my Samsung S8 (SM-G950F), running Android 7.0 and it has the same problem as 19.1. After reboot, Magisk Manager reports it as not installed. I tried every installation method - none works. 18.1 is the last version that works.
[Magisk] AndrzejDwo:
Mate, you know that I know that. And I didn't even say so. Those which you mentioned are of course known and reported issues. As I said - there are many problems with Xperia phones and MIUI based phones. The rest (of course not all) in my opinion are mostly created by users. Not only users which are not following instructions, but also those who are only complaining instead of providing proper info to let anyone help them.

How is it possible that you interpreted me this way? I know what Magisk's update looks like on your P9 running Android 7. And I know that you provided (or tried to, because of storage encryption issues) proper info about that.

---------- Post added at 03:30 PM ---------- Previous post was at 03:23 PM ----------

There is NO PROPER INFO coming from you if you want any kind of help. Do you know now what means that it's a user issue, should we all guess what is your phone configuration?

On my S8 SM-G950F running HadesRom v6 (Android PIE) I have no issues with 19.2.
[Magisk] nacos:
What would be the "proper info" you are looking for, other than Samsung S8 (SM-G950F), running stock Android 7.0, running perfectly fine on Magisk 18.1 and simply refusing to install 19.1 or 19.2?
[Magisk] smart123123:
Lol... Thats nt good to hear... Try uninstalling it completely.... Then download and install the zip file only not the app...and after reboot update the app....
[Magisk] AndrzejDwo:
Logs? Installation logs, recovery logs, boot logs? Info about your modules installed (maybe some are outdated), info about the way you update (clean or not), info about your android version (not only if it's 7, but is it stock or custom)? Man, if you would really want to solve your problem, you would already know how to report bugs/issues.

Edit: sorry didn't notice that you already stated it's stock.
[Magisk] nacos:
I do want to solve it but I'm also convinced that the culprit is the Magisk 19.1/19.2 rather than my phones. I have two identical S8, both same model SM-G950F, both running stock Android 7.0. I started fresh (no modules) on both, installed both directly from MM and after first failed attempt, tried installing the zip file from recovery.

On both I had the same result: after reboot I had to reinstall MM which reports that 19.2 is NOT installed. No modules are installed at this point. Are you still telling me that the problem is my BOTH phones? I don't have any logs, never created any. Furthermore, as soon as I go back into recovery, uninstall 19.1/19.2 and reinstall 18.1, miraculously, my both phones work again!

I also have Xposed framework 89 by rovo89.
[Magisk] AndrzejDwo:
[MENTION=624432]nacos[/MENTION] I didn't say that it's a problem with your phone, only that you provide not enough info. Take a look on the link that [MENTION=8126387]martyfender[/MENTION] posted right above you. You have all needed instructions on how to report issues there.
[Magisk] martyfender:
In the past I had asked the OP, (I assume [MENTION=4470081]topjohnwu[/MENTION]) to include a link in the OP of this thread for this:

https://www.didgeridoohan.com/magisk/MagiskHelp

But for what ever reason, it was ignored. It should in theory, be easy to do.

However, I do know that there will always be users that never read the OP and blindly post at the end of this thread, anyway.
[Magisk] Grennith:
Is the issue of `input` commands from other apps at SU level not being executed a known issue? Fails with both 19.1 and 19.2
[Magisk] guest4711:
How do you think the developer could fix it when neither having proper logs nor a device like yours to test it? Or do you want to spent him one of yours?
[Magisk] nacos:
Fair enough! If I decide to go again through this anguish, I'll try to provide logs. For now, I'll stick with 18.1.