yashsingh1/xdaforums huggingface dataset:
[Magisk] evronetwork:
Hey, does anyone know how to delete magisk from my system?

I was playing with "Easy DPI Changer" and it F my phone a bit, now every reboot everything goes too big(super low res) then freeze and reboot to twrp at first and if I restart this again the same pattern

Removing Magisk would not give root permission to "Easy DPI Changer" so it won't F my phone and I'd be able to remove it and then re-flash magisk

Tried something called "mm-201904040.zip" which is support to disable or remove magisk but it itsn't for 20+ magisk version

P.S. Currently running MIUI 11(public beta) - Xiaomi Mi Mix 2S
[Magisk] Didgeridoohan:
[MENTION=4447997]evronetwork[/MENTION] You can always find the link to the latest uninstaller in the release thread:

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[Magisk] evronetwork:
Heheh, yeah true. I guess I was panicked, thx for the reminder :D

EDIT: sssssssssssssssssssssssssssssssssh ...resolution is still on, after the uninstall of magisk :(

EDIT2: Removing magisk brought up "Mi-Recovery 3.0" ..stock recovery, oh well good times I guess

P.S. Does anyone know how to fix the DPI/Resolution through TWRP(I'll try to flash TWRP) - It's so nice trying to save energy and manage to f things up :D
[Magisk] zgfg:
It highly depends on your device and Android version.

For some, there are no proper TWRP versions, for some (Android 10) Magisk goes to recovery (no more to boot) and there is no room for TWRP

Find more info in the Magisk Installation guides
[Magisk] evronetwork:
Well I have no TWRP, can't fastboot flash twrp and have no working phone ..just mi "recovery" and fastboot which doesn't work

and the MIUI which boots says the MIX gets the M 50 times bigger freeze and then reboot

I'm sad :(

EDIT: After 500x tries of fastboot tries, TWRP is back in play... damn that was scary, still have to find a way for that F up resolution/dpi (Data are encrypted but no password is asked so it's all gibberish so far but this is not an issue if I manage to boot to the OS itself, somehow) - On reboot it gets mi recovery, so there's that
[Magisk] 7wells:
Hello!

When trying different versions of Magisk, should one always use the latest Magisk uninstaller version or the uninstaller version that was available at the time when the Magisk version to be removed became available? In other words: Is it ok to always use the latest available Magisk uninstaller, irrespective of the Magisk version that is to be removed?

Is wiping dalvik/cache recommended or even necessary after every flash of Magisk and after every uninstallation of Magisk?

Thank you!

PS:

I was planning to try different Magisk versions and always using the latest (as of 05 Feb 2020) available Magisk uninstaller (20200110) for removal if it does not work. I always wiped dalvik/cache after flashing Magisk and after flashing/executing the uninstaller (not sure if this is needed or if this might even have unwanted side effects).

Now I wanted to present my results so far with flashing via official TWRP 3.3.1-0 (mako) on a Google Nexus 4 with Android 10/Q from this thread (the system runs flawlessly, but with Magisk there are problems, please see below):

20.3: no errors when flashing => rebooting to system => no Magisk installed (Magisk Manager shows no options regarding logs, so I cannot write more here)

20.2: no errors when flashing => rebooting stops with showing the "Google" logo for more then 1 minute. I guess that this is enough time to wait after the system was executed once without Magisk, or is it not?

20.1: same as with 20.2

However, I now found out that even after uninstalling and not installing another Magisk version, the system does not boot anymore, i.e. I see the "Google" logo for a while, then the device boots again (bootloop).

Please forgive me that I cannot share any logs with you.
[Magisk] rodken:
Flashing your stock boot.img in fastboot should get you back up and running. If that doesn't work you can flash factory image without the -w in fastboot without losing any of your data.

The easy way out is to just reflash Magisk in for the device to complete the boot process.
[Magisk] 7wells:
@rodken

Thanks for your hints! I will do this next time. I just started once more from scratch - since this is my old "test" phone, data loss is no problem, and flashing does not take too long.

Do you always wipe dalvik/cache after ROM and after Open GApps and after Magisk flashing? (and even after Magisk uninstallation?)

Should the system be started once before flashing Magisk or can ROM, Open GApps, and Magisk be flashed in a row?
[Magisk] rodken:
It is customary to wipe the Dalvik after flashing the ROM and in some cases, wiping the Dalvik and System albeit skipping data before Dirty Flashing, although there are a number of Custom ROMs that contain built-in scripts that will execute that command upon flashing. It might be considered overkill to wipe Dalvik after flashing the ROM and again after flashing Gapps.

Allow the system to boot once before flashing Magisk. I know folks who do not follow these instructions and flash everything at once and then complain about random reboots and UI issues.
[Magisk] 7wells:
[MENTION=2280127]rodken[/MENTION]

Ah, thanks, I will adhere to this/your recommendation. Obviously, I have not red the instructions properly enough, sorry. :o

Is it necessary to use the Magisk uninstaller when flashing back the original boot.img that I backed up via TWRP before?
[Magisk] rodken:
Not necessary.
[Magisk] RandomPooka:
Identical end results
[Magisk] 7wells:
Does Magisk work for some of you with Android 10/Q?

For me it doesn't on a Nexus 4 - bootloops. How can I log?
[Magisk] alecxs:
check your flag in vendor fstab.qcom is encryptable=footer or fileencryption=aes-256-xts
[Magisk] Artim_96:
It does on devices officially supporting Q like the Pixels.

Before reporting anything try fixing yourself like by forcing it to preserve dm-verity and forced encryption (if that's even part of your ROM) and ask in the ROMs thread.

Otherwise it's hard too help. Somewhere in data I think there used to be a file containing the kernel logs (probably called kmesg or something like that) that could containing helpful information of that early stage. but at least I don't have it on my 3a. But then Google changed the filesystem a lot since the Nexus 4.
[Magisk] JimZiii:
Is it possible to symlink my sd card to an internal storage folder with magisk bind and if so, how?

I've been looking for apps to do this for several days now and the few apps i found that did this either didn't work with magisk and needed chainfire's superSU or they just refused to create the symlink.

The file managers i found that had this feature all failed.

I could really use some help with this, if a module like rclone exists for local storage instead of cloud storage please let me know.

Thanks
[Magisk] wilsonhlacerda:
rclone Magisk module can use local storage.

fbind Magisk module. Check its thread here on XDA.

Apps2sd (by Vicky). Check its thread here on XDA.
[Magisk] rodken:
Did you start from a clean install when attempting to flash Magisk?

or:

1) Download the uninstaller ZIP.

2) Enter TWRP during the bootloop.

3) Uninstall using the uninstaller ZIP.

4) Boot to Android.

5) Download V19.4.

6) Reboot to TWRP and flash the V19.4.

7) Boot to Android.
[Magisk] 7wells:
Yes, I did a full format, installed Android 10, then Open GApps (nano). both from (official mako) TWRP, rebooted to the system, went through the initial setup process, rebooted to recovery (TWRP) and flashed Magisk. The 19.x were are told not to work with Android 10 at all (as far as I understood).

Meanwhile I have also tried Magisk canary and uploaded some logs there and following post. The system starts but the (canary) Magisk Manager tells me that Magisk is not installed.

I am really sorry for the cross-/double postings as a result of me not knowing where to exactly post this. Moderators and users, please bear with me. If it makes sense to merge some of my comments, please feel free doing so. I guess I will now rather stick to the Magisk canary channel thread.
[Magisk] dnlilas:
Hello,

I am with stock Android 7.1.1 and Magisk 14 with MagiskSU. Some banking applications detect root so I uninstall Magisk/MagiskSU flashing latest Magisk-uninstaller-20200110.zip in TWRP recovery. But Rootbeer app still shows my phone as rooted (SU exists, native root). In terminal, I can see that effectively /sbin/su is linked to magisk !

How can I completely uninstall everything related to magisk and root ?

Note : When I tried to flash the stock boot.img, then the phone hangs at bootloader (no boot to system).

Thanks in advance.
[Magisk] rodken:
1. Do see the "Magisk is not installed" error message with the X in a red circle?

2. Is Magisk Manager up to date?

3. Do you see toast messages that say that "Manager was denied superuser rights"?

Give 19.4 a whirl and report your findings. V19.4 Changelog.

Installation troubleshooting guide
[Magisk] 7wells:
[MENTION=2280127]rodken[/MENTION]

1a. Magisk Manager 7.5.0 (265) shows a question mark on a rounded red icon and right from it text "Magisk is not installed".

1b. Magisk Manager canary 7.5.2-ed58cf95 shows the blue mask and right from it text "Magisk is not installed".

2. See above - I used (alternatively, not in parallel) the most recent MM.

3. No, I do not see them, but as I have not tried any apps requesting root (incl. root checkers), I would not expect this. Actually, I have not tried any root-demanding apps, since MM tells me that Magisk is not installed. Maybe I should try to check if the problem is maybe "only" with the Manager?

"Give a whirl" means what? (sorry, I am not an English native speaker ;)) I guess you meant to try 19.4 (from the changelog I see that this version introduced Android 10 support). Thanks for your hints and also the link to the Installation troubleshooting guide from [MENTION=4667597]Didgeridoohan[/MENTION] - very helpful as well. I have started reading it.
[Magisk] 7wells:
:D Oh my, I learnt another useful function today - thank you. :)

Alright, I checked with a root checker and it tells me that my device is not rooted. This does not come as a surprise but it surely was good to check this. It could have been a problem with the Magisk Manager, but now it seems (from my humble point of view) that Magisk is indeed not properly (or not at all) installed. In the canary thread I uploaded a recovery.log and messages from dmesg.log that came during flashing Magisk 20.4 canary via TWRP. Maybe that is of help to somebody. I call it a day for today. :o
[Magisk] martyfender:
Have you tried the patched boot.img method of installing Magisk?
[Magisk] warrencoakley:
I sideload it in TWRP with adb. Works perfectly without having to patch the boot img.
[Magisk] DiamondJohn:
The following page by [MENTION=4667597]Didgeridoohan[/MENTION] has a section on logging.

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

Not sure if it mentions it, but if your in a boot loop, you will have to use recovery to get to the log.
[Magisk] JIJOK:
Hello, need a little help please. I have 5 magisk backups on root/data, need all of them ? none ? just the last one ?
[Magisk] ktmom:
Probably just the last one. Do you have a stock boot.img just in case?
[Magisk] JIJOK:
yes, also twrp backup
[Magisk] Naudiz:
I can confirm your problem. The issues came with some update of he app. TK somehow made the app more restrictive and I'm 99.9% positive that it's not an issue with Magisk. I'm on LOS, you're on Mokee... it might even be possible that TK is ruling out any custom rom, no matter if rooted or not.
[Magisk] rodken:
Now, that's an idea.
[Magisk] bunklung:
Anyone else have issues pulling down the Feb OTA for their Pixel 3? Typically it would say preparing update, then I would unroot.

I got the preparing update notice when I checked for updates, but then it reverted to no updates found. It's very odd.

Anyone else have this issue?
[Magisk] Callis:
I apologise if this is already covered I've run a few keywords through the thread and not stumbled on what I was looking for.

I have an LG G3, running a fresh new CM13 ROM. I want Magisk for banking and for Pokemon GO.

I first unrooted the rom using SuperSU which worked fine, skipping the SU binary update it requests as that soft-bricked the phone the first time. I then rebooted into TWRP and flashed Magisk, phh's superuser and the bootloader which is needed to bump the boot.img on the LG G3 which a few on the earlier posts with this phone have not done and thus encountered the blue/red LEDS and secure boot failures.

I then rebooted and downloaded phhs superuser from the app store and Magisk Manager.

My problem centres around the Magisk root toggle. Magisk Manager shows as rooted. I toggle and nothing happens. At all. After I installed Root Checker that validated root then the next time I toggled in Magisk, phh superuser acknowledged Magisk Manager requesting Superuser access which was granted. It is listed as allowed in phh superuser now. However the toggle still does nothing.

Some websites have claimed that using root browser to delete system/bin/su (which I didn't have) and system/xbin/su (which I did have) fixes the issue. For me, sometimes this does nothing but most of the time it switches Magisk Manager to unrooted with the toggle option greyed out. This also removes "Apps only" and "Apps and ADB" from Root Access in developer Options. Rebooting resets anything done through root browser here.

Is there something I'm missing? I'm not using a stock LG rom because as stated previously, another thread reports LG stock roms do not work with Magisk. Besides, I love CM13 and run it on other devices and I'm not willing to give up root and xposed for stupid SafetyNet API passes.

I was going to progress to moving to suhide and Magisk so that I can get xposed back which I love whilst still having android pay, barclays and pokemon go working along with automagisk. With it not working at this point, there seemed little point in progressing further (or so I have assumed).

Any suggestions or insights are very much appreciated <3
[Magisk] alroger:
Well, that makes me conclude that there is something special with your device's TWRP. Maybe related to encryption or your bootloader.

Anyways flashing Magisk is quick and easy... Just like I have to do after every dirty / OTA update. No need to flash other modules, like root.
[Magisk] Didgeridoohan:
Yes, I was thinking along those lines as well. Seems like there are a few quirks with the N6 and Magisk. As an example: I've only seen N6 users reporting that setting density in build.prop through post-fs.sh does not work. And now this...
[Magisk] souleman:
After making a backup and a few days later, restoring from said backup, never had an issue with magisk. It survived both.

Any issues I've run into I'm 99? sure are related to modules, not magisk.
[Magisk] DzikrRully:
Please upload SuperSU 2.78 SR1 magisk version.
[Magisk] cadkey:
Lol. You think you're at the supermarket?
[Magisk] pavlo1c:
Magisk Manager not work on v4+, on 4.4.2 syntax error while parsing the package, any body have for 4.4.2 ?
[Magisk] Artim_96:
Who said it would work on Android 4? Only 5.0+
[Magisk] pavlo1c:
on top topic write:

>>Magisk Manager

>>v1.2 (Updated for Magisk v4+)
[Magisk] Artim_96:
Well, when you have any problems day what they are, otherwise no reasons for concerns
[Magisk] Didgeridoohan:
Magisk v4, not Android 4...
[Magisk] Turbopuschel:
That means the Manager App works with versions v4 or newer of Magisk.
[Magisk] souleman:
My point was that twrp backups were not causing issues like some people are stating. The problems I do have are in the proper threads. Titanium backup not uninstalling a system app has nothing to do with magisk, it appears to be a phh su issue.
[Magisk] Mince69Meat:
u quoted all that just to ask for a link that's going to change offten as it's still in testing when u can just add the forum that's about SuperSU 2.78+ testing to your favourites n keep upto date :o
[Magisk] pavlo1c:
Oh sorry, ok.

4.4.2 It will not support? :(
[Magisk] Artim_96:
The difference might be that you made a backup of a system with Magisk and restored the whole thing. The problems might have been that people tried restore from an older system that had an older version or even no Magisk.

The problems with TB are with SELinux, not with TB, they will occur on every system with Android 5.0+. TB can't properly Mount /system so it seems operations tampering with /system fail, but they don't. Just let TB run for a few minutes, then reboot. Then the changes should have succeeded.

But you should leave /system untouched, Magisk is running everything systemless (which means no changes are made to /system) for a reason. So if you tamper with /system I can't guarantee that Magisk still can hide root from Android Pay and stuff.

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

No. Never.
[Magisk] francyesco:
Is there a way to revert the patch to system verity and forceencrypt?

Are these that cause "response payload validation failed" on the safetynet helper app?
[Magisk] edale1:
Hello, I'm pretty new to Android, so forgive me if I ask any noob questions.

I recently tried to install Magisk 6.0 on my LG K7 (lg k330), and got stuck on the "Bootloader State: Bootloader Unlocked" screen.

Thankfully, I had made a backup with the TWRP M1 V5 Final (http://xdaforums.com/android/development/twrp-m1-lg-k7-t3462130) TWRP build, and recovery went smoothly.

From the currently known not working devices list:

I'm not sure if the LG K7 counts as one of these. The bootloader was locked originally, but was easily OEM unlocked...

Has anyone managed to get Magisk to work on an LG K7, or am I stuck waiting on Magisk v7 to play Pokemon Go again?
[Magisk] JuergenZ66:
Check with Root Validator from play store if there is another su binary
[Magisk] Echo_2000:
Guys i have to put bootanimation in cache right?

I have it in cache but it isn't working...
[Magisk] vandyman:
Yes,, I had to use the factory image with flash-all (without the - w) on my 3aXL.
[Magisk] bunklung:
Anyone else have to do the same process above? I have got a bit lazy and got comfortable with just using the OTA official process.

I wonder if I unroot before I check for updates will it try to prepare the update as normal?
[Magisk] seemebreakthis:
With old interface Magisk Manager, when you open "UBS Access", after a few seconds it will show the error message then quit.

With new interface Magisk Manager, "UBS Access" can be used.

Of course for both versions, I have enabled "hide Magisk Manager", and Magiskhide is enabled for "UBS Access".
[Magisk] dcarvil:
OTA worked fine for my Pixel 3 following https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md.
[Magisk] bunklung:
That's the same guide I have used. My issue is that the download won't even start. I have accidentally tried to apply an OTA before I unrooted, but that's not my issue.
[Magisk] Ch3vr0n:
My pixel 3 started prepping download too, then went back to no updates. Maybe google pulled the incremental ota, while leaving full ones and factory images. If I don't get it by Sunday, I'll probably flash the factory
[Magisk] marquelito:
It's ok for me, but I use an extra magisk hide zip. Changing permissions to uds file and making busybox hidded for apps that detect it. In order to work around snapchat ban. I don't know if [MENTION=4470081]topjohnwu[/MENTION] is aware of this issue. Use rootbeerfresh to know what is detected
[Magisk] cxvbxcbxcvbxcb:
Until yesterday I used 19.2 on a Oct-2019 LOS build. After Updating to a Feb-2020 build and 20.3, Ingress detects the root. Magisk Hide for Ingress is on, the manager app is renamed. I flashed 19.2 again, manager says magisk is not installed. then I used the flashable uninstaller, flashed 19.2 and removed the old manager version that was installed with it (and kept the current randomly renamed one). In emulated/0/ I even removed the magisk files from download folder and the com.randomname folder (within ./android/data or ./data, I'm not sure)

Did anything change from Oct build to Feb build? Did I miss to remove an indentifier of magisk?
[Magisk] amg314:
Try do the following:

1. Mark the target application in 'Magisk Hide'.

2. Rebuild Magisk Manager with a random package name.

3. Delete data (not cache) of the target application:

Settings --> Apps --> Target app --> Storage --> Clear Data
[Magisk] bunklung:
I gave up. I think Google pushed something in the January update or through Play Services which effects the ability to detect/flag root when trying to download the February update. Or something was flagged when it detected an off Magisk module or something? I went as far as restoring the image and disabling my modules. No luck.

So...

The frustrating thing is that I could not boot TWRP (FAILED (Status read failed (Too many links))) after I performed a stock recovery sideload of the full OTA. So I had to download the full update, extract boot, copy to the device, boot to stock Android, patch the boot in Magisk Manager, copy the file back to PC, boot to the bootloader, flash the modified boot. Ehhhhhhh. First world problems, I know.

Does anyone know if I will be able to restore my image since I used this workaround patch boot? Does Magisk even have my original image? I patched it, but where does it keep the original boot image? Can I just copy this over to X directory? I don't know if image restorals will even apply to me since I might not see an official OTA for a while that actually downloads. I assume I am some edge case.
[Magisk] ktmom:
Quoted from https://www.didgeridoohan.com/magisk/MagiskUninstallIssues
[Magisk] Ch3vr0n:
I doubt they pushed something. As to the 'too many links'. You're not connected to a USB 3 port are you? Took me a while to figure that one out for me, but the moment I swapped to a USB 2 port I'd boot twrp just fine. Didn't change anything else.

Note that due to the system-as-root implementation in Android 10, it won't go you any good. TWRP had yet to be updated with SAR support, I checked the TWRP site earlier. Last message on that still dates to around October last year I think.

I just sideloaded the ota, but couldn't find a way to extract the boot image from it (the payload.bin file), so grabbed the factory image, extracted the boot file and patched it with magisk on the device. Then fastboot flash and back up and running. Tough you can just flash the entire image and remove the -w flag from the flash-all file.

We'll see again in a month.
[Magisk] bunklung:
Perhaps it's because you have an XL? I did try USB 2.0, no luck. Does SAR have anything to do with mounting the encrypted partition? A while back the work around for running the Magisk install in TWRP, was to use adb sideload since you really didn't need to write to userdata. I think TWRP used a ramdisk for running the Magisk script.

Would this still apply today?
[Magisk] Ch3vr0n:
It has everything to do with accessing encrypted data. I suggest you read the TWRP announcement ok Android 10.