yashsingh1/xdaforums huggingface dataset:
[Magisk] chooks06:
I've had problems with TC couple of years back on some devices, with paid add-ons.

Became sluggish cuz it didn't click with the ROM for that device.

Then I found another file manager way better than TC that suits my needs and fancy and is available here in XDA..

And it's free and working with the different ROMs on my devices and gets regular update.

I always say to my fellow Senior Citizens in my country when they started to get used to smartphones - phone is smart, user........?

BUT, I'll never call out an app as Amateurish unless I can build a better one and I'm just an old fuddy duddy learning how to root phones.

Magisk 19.1 running fine in my antiquated rooted devices (Galaxy Note 3 (Pixel Experience ROM 8.1.0), Galaxy Tab S 8.4 (AOSP 7.1.2)).

But I do notice that quite a lot of feedback especially from users on Pie and then again, more recent devices.

I would probably have the same problem if I'm on a newer device cuz things have changed....

I can't expect Dev to cater for everyone and every phone - we setup our phones differently.

I'm the amateur, but all is well and good.. Just need to get the basics right, whatever it is, for individual user..

If everything was working fine why change? That's up to the user.

Many nice peoples (plural, international) here have been more than ready to help - only those who need help... This is not a complaints department..

Hope one can find a solution to one's issues but it one just throw the blame to the app, then best of luck if that person can't be objective in stating the issues at hand or if logs can't be provided.

Have a great week ahead.

Cheers!

Edited - typo..
[Magisk] martyfender:
I use Mixplorer also and like it, but for day to day use I still prefer the simplicity of TC.
[Magisk] chooks06:
I agree with you mate! Just that it got sluggish (for me) so i decided to change.

After I got used to MiXplorer, I just stayed with it. Probably in idle mode..Lol.

I'm not saying TC is no good. It has it's strength.

Edit.. You're one of the nice people (there's others as well) who spends time helping out..

:cool:
[Magisk] microspock:
After update to v19.1, root logging disabled for tasker and automagic and everything is back to normal. Thanks a lot. :good:
[Magisk] Looki75:
Guys, check my post just few posts before yours.

I'm pretty sure this is the exact same cause I described... And there is a workaround...

Let us know.

Cheers
[Magisk] wozhere:
Well for multi file commands, Lan plugin (sees all my network drives folders & files), other plugins (Dropbox onedrive gdrive FTP usb-drives etc etc) nothing comes close to Total Commander. In fact not only it'ss the best file manager for me and many other coders, it's the best & most indispensable app for Android, "IMHO", I repeat for me and many devs/coders.

Many coders use it as the other graphic icon based chunky apps can't compete with multi file commands, filters, and other features. Can change colors, text/line sizes to fit more files on screen, select filters, etc etc. Nothing comes close for serious file management use. Coders who used NC on PCs and similar copies in the old days know what TC can do that others don't come close to.

I'm glad to see others are experiencing the same problem. The previous magisk was fine. Basically many coders use it for FAST MASS FILE COMMANDS, network access etc. I guess the devs know the issue well. It's probably happening with other apps too, if it's an old issue that just returned with this version and many have reported it before. There are many advanced features in Total Commander many do not get to use or see. But many devs do.

Anyway, Reporting a bug should not be answered with, hey use something else pal, use my favorite app. I hope this BUG can be fixed, again.

I disabled notifications for TC in magisk, not a problem for me, just trying to help with feedback.

Thanks to the devs for magisk again.
[Magisk] Azuritko:
Can you please upload somewhere all files that are needed? I have D5503 too and I am not sure how to update binary. If you can upload all modified files it will help me.
[Magisk] rgawenda:
Flashfire needs toggling selinux. DriveDroid works with phh's supersu without problem.

So you are unable to run DriveDroid, but my answer is futile as you're also unable to read, given that the FlashFire thing was posted many times in this thread.
[Magisk] Medel-Silver:
It works good for me.
[Magisk] AD2076:
I used Magisk on my Huawei P8, it works great with apps using SafetyNet check but it caused random freezes with any game.

My config:

Magisk 6

xposed-systemless 86.5

phh's systemless root.

Removing Magisk solved the random freezes.
[Magisk] lebeneur:
Hi !

First thanks for all this wonderfull job !

By witch way can I send you my LG G3 boot to help you fix magisk installation ?
[Magisk] toshi127k:
Okey but

Have you made a boot.img

Also What ROM to be used
[Magisk] ilfat12:
I know, but after starting the job phone goes to a black screen and then nothing happens. Have you checked whether it makes a backup? For me does not work with modified SuperSU and modified phh SU.

The same situation. It does not load any image.

No need to blah-blah. First try, then talk.
[Magisk] rgawenda:
First read at least first page of this thread.

Then, with the material currently *supported* here: Magisk's Xposed v86.5, Magisk's phh's supersu, DriveDroid works flawlessly.
[Magisk] ilfat12:
I know what magisk and what it's for.
[Magisk] Azuritko:
I want the step by step tutorial with links from you if you can do it and if you have time for that.

Actually I have stock ROM 4.4.4 rooted, with dual Recovery. I did that about 2 years ago.

I want to flash stock ROM 5.1.1 as you have. Where to download stock ROM? And how to unlock bootloader? I do not know where to get boot.img...... I need more detailed instructions.
[Magisk] Krunk_Kracker:
I've gone through the order again and did all of these things again, and still nothing, except now the Magisk toggles are greyed out now, instead of green.

Is MAgisk supposed to ask for root priveledges? because it never does for me.
[Magisk] dejitaruneko:
I had exactly that issue, solved it via using the Uninstaller for systemless Xposed. Wasn't using it for much, MinMinGuard, RootCloak, and Security Bypass. With Magisk having a root toggle figured I don't need the last two, and if ads bug me enough I can try one of the adblockers floating around on here.

Nexus 6p running PureNexus and the Ninja Kernel

Edit: After going back a few pages I see someone else said this... I really need to check which page I'm on when using the XDA app...
[Magisk] ilfat12:
Now once again I checked. DriveDroid does not work with Magisk and phh or SuperSU.
[Magisk] toshi127k:
OMG! here is developper's topic of magisk

your problem is not magisk's problem. I think that it is not permitted to discuss such a thing here

be following the topic is your help

http://xdaforums.com/showthread.php?t=2631291

sorry, friend
[Magisk] Germano.Mosconi:
I'm facing the same problem. I can't make FlashFire work with modified SuperSU and modified phh SU (even with SELinux toggled to Permissive).
[Magisk] rgawenda:
Well. Then I didn't just boot this Mac book into chrome OS right now :cool:
[Magisk] Germano.Mosconi:
We believe you, but the fact that it's working for you doesn't mean that it must work for everyone. I don't know about DriveDroid, but I'm pretty sure that FlashFire is not working for me (I tried different times with the same result, a black screen) while it's working for others.
[Magisk] ilfat12:
Someone else can check drivedroid with magisk? :)
[Magisk] hammerhead2:
Drivedroid fails to obtain root here. Magisk with phh root, no xposed.
[Magisk] ilfat12:
which version are you using? I use the beta 0.10.23
[Magisk] rock'n'rolla85:
Could you please add "hide module" option in download section?
[Magisk] Lord Sithek:
Xiaomi.eu MIUI 10, Magisk 19.1 works perfect :good: As for now no problems at all
[Magisk] kosiak07:
Fresh installed ROM Huawei P9 Lite C432 b504, bootloader unlocked, installed TWRP.

In TWRP Flash magisk 19.1, after restart info that my storage is decrypted. Installed 18.1 no problems at all :(
[Magisk] raphytaffy:
After installing 19.1, I was facing a number of weird issues across apps. Maps would keep minimizing itself, Snapchat face scan would not work, and Clash Royale would hit a lag spike every now and then.

The only thing I changed was installing 19.1, so I removed it and sure enough all of the weird issues went away.

My question now is how can I completely remove all traces of 19.1 and install 18.1?

I have done the following:

Downloaded the factory image for my phone here.

Edited flash-all.sh to remove -w.

adb reboot bootloader

./flash-all.sh

Reboot phone.

adb reboot bootloader

fastboot boot twrp-3.2.3-1-marlin.img

Install > Magisk-v18.1.zip

Installation looks like it succeeds, but Magisk Manager is showing that it's not installed. Are there any additional steps to take?
[Magisk] wikm:
Nobady from Galaxy A7 2018 users have good installation of Magisk 19 or 19.1 on android Pie (most recent working Magisk is 18.1). There is shown in Magisk manager about Magisk 19.1 that is not installed too like [MENTION=2489389]raphytaffy[/MENTION] has.

.
[Magisk] Looki75:
This is due to the issue I mention here:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post79473036

Check my post.

There is a workaround, try it and report back.

Thanks
[Magisk] kotuamoalt:
Version 19.2 seems to be working well, with no issues so far. Google pay is working!
[Magisk] m1s3rys1gn4l:
which version of magisk working on 9.0 treble rom ?
[Magisk] raphytaffy:
Thanks! Your post confirmed what I suspected.

My issue is that Magisk 18.1 doesn't seem to be detected after uninstalling 19.1 and reinstalling 18.1. Looking for any clarification into the matter.

I'd rather not have to deal with disabling journaling and notifications for each root-enabled app with 19.1. Since 181. was working fine, I'd just like to go back to that until everything is sorted out.
[Magisk] Looki75:
I never reverted to a previous version...

Maybe you need to downgrade the app as well...
[Magisk] drezz2:
19.2?where? in the post says

Stable Magisk Version: v19.1

Beta Magisk Version: v19.1

dont know.. but.. if you flash the unistaller and flash again 18.1 not works?

I had made a backup just before with twrp and I restored it whole :silly:
[Magisk] kotuamoalt:
It is s Canary build, as is the manager I am using.
[Magisk] hfam:
Pixel 2 @ 18.1. Used full factory image method (May sec update full image) to update to 19.1 and MM 7.1.2, smooth as silk, everything works proper, no issues!

Thanks as always to everyone in this forum who offers selfless help to anyone who needs it. Thanks also to [MENTION=2820009]ahac85[/MENTION], you know why.

Best. Forum. Evar. Thanks all!!
[Magisk] drewski_1:
Bug reports need some logs.

If the dev can't reproduce, they need more info to go on.

As a coder / dev, you know this.
[Magisk] eliotargy:
Magisk manager 7.1.2 is not installing on my Galaxy Note 9. What's more it won't update through the 7.1.1 version. Is there something wrong with the new version? Installation goes as far as the screenshot and no further.
[Magisk] wozhere:
The post you quoted and the previous posts immediately before it state the issue is well known to the devs and it rears it's ugly head too as in previous versions.

It is not a new issue. It is a well known issue by the devs going to previous versions. They can fix it again, just like they did on previous occasions.
[Magisk] patriex:
Why I think not only magisk module but also magisk manager is also at fault here. Updating magisk manager first started problems for me that root getting detected.
[Magisk] martyfender:
Do you have your current manager hidden? If so, unhide it and try again. If your current version is one of the unofficial versions, the manager is signed with a different key and won't allow you to install a released or Canary build over it. If that is the case, uninstall your current version of the Manager, download the official version and install it.
[Magisk] Momotani-Hitoshi:
I installed 19.1 but it was glitching out cerberus & google maps.

How do I revert back to 18.1 from the magisk manager?
[Magisk] wozhere:
i know lots of people have been reporting different bugs over the last few pages with version 19.1.

The best option might be to wait for version 19.2 which might fix the various new bugs. Much easier than reverting to 18.x versions.

I think the devs were trying experimental features which backfired. I am sure they are aware. Might be a good idea to test these in beta releases and fix with feedback from beta users in future.
[Magisk] drewski_1:
I read it all. Thanks.
[Magisk] wozhere:
Easily reproducible generic bugs, as this is as other posters noted too and you ignored is best and fastest resolved on the dev's own device. Which they can do in a few seconds by installing the app if they don't have it already. This is not a device specific bug which is hard to replicate. Once a dev fixes this generic bug on his/her device, it is resolved for everyone, just as in previous versions WRT this specific recurring bug they're familiar with.
[Magisk] jenslody:
Please stop getting personal.

Why do you assume that an issue, that behaves like an already fixed one has the same causes ?

Unfortunately bug hunting is not as simple in most cases.

You say the dev can easily reproduce it and it's better for debugging to do it on his device.

That's correct in general, but as [MENTION=8126387]martyfender[/MENTION] he has the issue on one of his devices, while on three others (almost identical) it does not happen.

So it seems to be not so easy to reproduce.

Obviously John does not have such issues on his device(s), otherwise he would not have published this release.

Many others also have no problems with the apps they use (me included), so it is at least not a general issue.

And John can not install each and every software combination on each and every device (with lots of different roms) to reproduce such issues.

It's up to the community to help here and to fetch logs to make it possible to fix such a bug.

Everything else is a waste of the devs (and other users) time.
[Magisk] cls2:
Where can I get 19.2? MM on my phone doesn't show this update.
[Magisk] kotuamoalt:
It is in the "Canary' builds.
[Magisk] cls2:
thank you!
[Magisk] Redline:
Let's keep it on-topic, civil and productive here gents <3

Generally speaking, it's a lot more productive to spend your time providing any and all relevant logs a dev might request from you so they can get it fixed, as opposed to talking/bickering about what an issue might or might not be.
[Magisk] guest4711:
It's in ianmacd's unofficial builds. Enter https://raw.githubusercontent.com/ianmacd/MagiskBuilds/master/updates/ianmacd.json as update channel (MM -- settings -- update channel -- custom)
[Magisk] eliotargy:
I'm getting the exact same problem with my Galaxy note 9. Are there any replies to this question?

---------- Post added at 08:44 AM ---------- Previous post was at 08:24 AM ----------

Cheers. Did just that. All is well again.
[Magisk] Momotani-Hitoshi:
So there is no easy way to revert or roll back to a previous version? So in the future I should make a twrp nandroid and restore the boot.img to roll back?

I went ahead and dirty flashed to May update and re-installed 18.1

19.1 made google maps unusable which is important app.
[Magisk] AndrzejDwo:
As I know, you can easily roll back to previous versions by flashing your stock boot.img or kernel and installing Magisk from scratch. Another way is to have a backup of your patched boot.img and flash it back if something goes wrong.
[Magisk] wozhere:
Yes. Also as you see others reported the same bug I reported too.

Secondly there are other bugs reported over the last few pages too with this version. Just like you.

It's unfortunate you had to dirty flash.

The best option in future is not to flash a new version, read new posts here to see if there are bugs and then wait for a while and only then to flash the new version if no serious or numerous bugs reported.

Have a good week.
[Magisk] Gmx1987:
You tested this roll back... What if you have after booting a error SystemUI stooped only chance it's to push power off button flash boot.img or kernel didn't solved was still this same only way for me flash Rom
[Magisk] AndrzejDwo:
I didn't have that kind of problems with Magisk, so no, I didn't test it personally but my friend did with latest Magisk and it helped. With flashing previous patched boot.img he was able to roll back to 18.1 from 19.1 and 19.2 Canary. On his experience was based my previous post.

Edit: here is my old post with my own issues.

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post79221295

Edit2: about sys ui stopped, did you try to wipe dalvik/cache
[Magisk] JudgeDread11:
Of everybody take that advice there won't be any posts about potential bugs.

But it's good advice for those who are not experienced with making and restoring backups or problem solving and are not willing to experiment and learn.

IMHO those people shouldn't be rooting their devices.
[Magisk] Burgscheinkerkdeiktraast:
To avoid a hassle, I just recovered whole system from TWRP backup. No more Magisk updates :)
[Magisk] agplugged:
Hi everybody, first time I ever experienced any issue with magisk, couldn't find anything in here so I'm asking:

Pixel 2 xl, just flashed the latest May update and installed a custom kernel (latest Sultan build). Both twrp and sultan's installed alright, but magisk causes the device to shut down and boot to recovery after booting.

I used magisk 19.1 before updating to the may sec update.

Anyone experiencing this or has any idea on how to solve this problem? I'm currently on Sultan's and the May update without any problem whatsoever.

Tried:

Rebooting after each flash (update, twrp, kernel, magisk)

Flashing again after booting back to twrp

Thanks a lot guys!
[Magisk] wikm:
If there will be stable Magisk 19.2 - it should work on Galaxy A7 2018?
[Magisk] Ch3vr0n:
Of course at some point there's going to be a 19.2, and will it work? Well let's wait first until such a version exists shall we?
[Magisk] AndrzejDwo:
Guys, take a look at few pages back as the update started. How many complaints there are and WHERE ARE THE LOGS? How the DEV can possibly fix the issues of some, and make the app/installer reliable, if they are only complaining without any support. It's showing how selfish people are, counting on others to fix their problems.

Cheers
[Magisk] Nixer:
This is what I tried to highlight in my earlier posts. Although Doodgerihan says magisk backs up stock (read - pre-modification) boot or dtbo.img, it still can't be found by the uninstaller to restore.

I have tried to follow up but still not able to get an answer to following (may some support from TWRP guys as well) - how to obtain backup of pristine device partitions (and which ones to backup for successful recovery from botched up operations viz. magisk uninstall?

I had Samsung Galaxy S5 earlier and it worked beautifully with RR (or even stock) + TWRP + Magisk. I had backup copies of all partitions and could restore anything when needed. With 1+ 6T, things have become too difficult (probably due to a. encryption and b. A/B partitioning). Issues with Magisk uninstaller when not having TWRP means fresh install using MSM tool. Nothing in between.

I have a OTA pending but can't still gather enough courage to go through the upgrade process fearing issues during the upgrade and later when apps stop working due to root. rootbeer fresh results are scary and on top they have library that other apps can use to detect root. :(
[Magisk] diehard2013:
folks,

am I screweed?
[Magisk] KaMyKaSii:
You are not. Just re-enable it
[Magisk] diehard2013:
done.

I was concerned because I remember the very first time "oem unlock " is enabled, the system displays a warning and notifies it will reset the whole thing. I did not see that now.

note: had I rebooted with 'oem unlock' disabled, the devide would brick. corect?

thank you!
[Magisk] jcmm11:
Just so you know - at the moment 19.2 is identical to 19.1. The number difference is just to differentiate the Canary line from the stable line. They will not, of course, remain the same in the future.
[Magisk] Badger50:
I experienced the exact same thing. 19.1 was fine for April, but caused the twrp bootloop with the May update. Simple solution for me was to flash the magisk uninstaller.zip, followed by flashing the 18.1 magisk zip. Had to install all my modules again, but, meh, that's no big deal :good:
[Magisk] renegade:
Hi,

Thanks for the tip but unfortunately it did not work for me, I think the app utilizes "Promon" protection but the running the script did not solve the issue. It is still detecting root/Magisk. I think it is looking for something else running even after Magisk process is killed!
[Magisk] agplugged:
Likewise. It's a drag but I suppose it's better than staying unrooted. Hopefully this won't drag on to the next updates as well.
[Magisk] SkylinesHD:
Hello,

in magisk manager my download modules section dissapeared after i installed a modules and restarted.

I only have "modules "section but not download modules
[Magisk] guest4711:
Make sure you have an internet connection (and your firewall does not block Magisk Manager). Missing Download section occurs if MagiskManager cannot connect to github.
[Magisk] 23Six:
Sometimes the Magisk app won't even launch upon clicking. I'll have to access it using the quick shortcuts on my launcher or force close and reattempt. Common issue?
[Magisk] Ingan121:
Did you run the script in SSH session, not the normal terminal?

If so, try uninstalling Xposed, root-only apps, other superuser apps, warez apps, etc.
[Magisk] tech_head:
I have a bad build.prop in one of the slots (slot_a) with Magisk and it causes a bootloop.

The other slot (slot_b) is clean and I have no issue and boot fine.

How do I get rid of the bad build.ptop in the other slot_a so I can boot in that slot?

Both are identical except I was trying something with the build.prop have have no idea how to recover.

Never mind.

I flashed a virgin copy of the OS in the slot. - Resolved.
[Magisk] renegade:
Yes, even tried with a ssh client from my PC (Putty). Don't have Xposed, but have a few other apps as you mentioned except for warez. I could try testing uninstalling the stuff that might be detected but that's going to take a long time.

update: I updated my ROM today clean install only Magisk, still detecting!
[Magisk] jcmm11:
What phone? You physically replaced the build.prop in /system/etc/? (Why? You should have just done it systemlessly).

2 options - flash a factory image to slot_a. Replace the bad build.prop with a good one using TWRP.
[Magisk] Looki75:
I also noticed that since latest release.

This happens when the pagisk app is busy with giving root access to another app.
[Magisk] thekokii:
Is anybody experiencing some screen unlock lag with 19.1? When I press the power button and not swiping the lockscreen up but using my fingerprint to unlock, the screen hangs for a few secs after the clock slides up. This happens on every 3-5th time when I unlock.

Also if I want to uninstall the latest version to downgrade to 19.0 there won't be any issue? Because the manager pops up an encrypting dialog.

---------- Post added at 10:35 AM ---------- Previous post was at 10:35 AM ----------

Is anybody experiencing some screen unlock lag with 19.1? When I press the power button and not swiping the lockscreen up but using my fingerprint to unlock, the screen hangs for a few secs after the clock slides up. This happens on every 3-5th time when I unlock.

Also if I want to uninstall the latest version to downgrade to 19.0 there won't be any issue? Because the manager pops up an encrypting dialog.
[Magisk] ctsuresh:
Hi I have updated my magisk to 19.1. After update safety net shows API error. I tried to clear data in setting but I couldn't find magisk app listed in apps.

Pl help
[Magisk] SkylinesHD:
thank you. i turned on wifi and it worked.
[Magisk] martyfender:
Do you have the Magisk Manager hidden? If so, it will be renamed Manager.