yashsingh1/xdaforums huggingface dataset:
[Magisk] Badger50:
Flash the magisk zip after the custom kernel while your still rooted on the stock kernel in EXKM or FKM :good:
[Magisk] Kelynaw:
Moto G7 power 1955-5 metro variance loaded loaded with global firmware. Same here did direct install and got stuck in a loop, reflashed original boot and was back in. Tried reflashing last patched boot file since I've gotten no ots'a same result stuck in a loop
[Magisk] nenesse:
Same problem with S 7 Edge

Hi, I have exactly the same problem here with my Galaxy S 7 Edge. I don't know what should I do except stay with 20.1 .
[Magisk] Kelynaw:
20.1 file

I've looked around and I cant find a copy of 20.1? Could you shoot me a link please? My phone is nothing butt errors at the moment and I am trying really hard to not lose any data so a stock reflash isn't exactly desirable
[Magisk] nenesse:
Hi, you can find any version here and if you want 20.1, you can have it there.
[Magisk] Kelynaw:
thanks for the life of me I couldn't seem to find em. little brain fried today I guess.
[Magisk] jcmm11:
Report that to [MENTION=3428502]Freak07[/MENTION]. Kirisakura should keep root. If no TWRP how are you flashing Kirisakura?

In the meantime, like [MENTION=3730810]Badger50[/MENTION] said, whatever you're using try flashing Magisk immediately after Kirisakura, with no reboot first.
[Magisk] 15armitagem:
LG v20 H918 boot image lost

I tried updating to magisk v20.2 and my phone got stuck at fastboot. I've tried uninstalling and reinstalling magisk, but to no avail. I'm afraid I might be stuck with restoring the default opperating system kdz file and rooting again. Any advice? I'm new to this and I don't have a back up of my phone. I'd really like to get it booted up again as is. Please help.

Edit: okay, reading through the troubles others seem to be having with LG phones it seems like this post might be a solution. However, I have not found /data/magisk_backup_ and I'm starting to panic a little...

again, I have been able to get into TWRP, but every time I reboot it's back to fastboot. I can't seem to find a backup boot image. Is there some kind of search function I can run in hope that it would come up with boot.img.gz or am I really out of luck? is there a way I can back up from here to loose as little as possible?
[Magisk] martyfender:
I don't know lg phones, but if you have the stock firmware you can usually extract the stock boot.img from it, flash it in twrp and before rebooting, flash the older magisk.zip there.
[Magisk] Homeboy76:
https://www.didgeridoohan.com/magisk/HomePage
[Magisk] Zasnizas:
Updated to 20.2 on MSM xtended (10) so far, everything is going well no problem here
[Magisk] madyinwhich:
Hi,

I just did a fresh lineage install after a complete wipe incl. internal storage. I flashed with TWRP in the following order: Lineage OS, Magisk, Google Apps Pico. I have a S4 jfltexx. All seems to be ok so far but when I try to hide the Magisk Manager, the Manager app wth the new name appears in the app drawer but if I start the app the following message appears "Upgrade to full Magisk Manager to finish the setup. Download and install?" I press Ok. "Downloading...." appears and the app starts again with the same dialog. So that additional Download seems no to be possible. I never had this problem before. Maybe someone can ´help here. :confused:
[Magisk] Hiro Nakamura:
Facing the same problem here
[Magisk] Duck4Cover:
Same here.
[Magisk] JudgeDread11:
Not sure if you figured it out yet, but just in case.

Flash madurai from TWRP. TWRP allows you to switch allow first.
[Magisk] mithmag:
Magisk v20.2 didn't work on me either. First i deleted the magisk manager, then flash magisk uninstall (reboot), then flash v20.1(reboot)and re-install magisk manager. The problem has solved.
[Magisk] EnekoT2001:
I tried updating to magisk 20.2 from 20.1 and no matter what i do, i lose root, and magisk manager says "magisk is not installed". I tried updating with direct installation via magisk manager, with twrp, i tried uninstalling magisk and reinstalling it, i cant get it to work. I have a galaxy s7 edge with the ThunderStorm kernel.

Btw if i install magisk uninstaller.zip my installed modules also get uninstalled? maybe one of the modules i use isnt compatible with magisk 20.2 and it crashes? idk

For now, i think I'll stick with 20.1 (i have a backup, thanks twrp) and when 20.3+ gets released i'll try again.
[Magisk] Hiro Nakamura:
Is there a way to just install the obfuscated magisk apk?
[Magisk] haaffizzzz:
Tried to hide magisk manager in latest 7.5.0 update. It did work, but its stuck at the logo asking to upgrade to full magisk manager and showing either no thanks or install. I tried clicking install but the app force closed
[Magisk] ibigfire:
20.2 is borked for me as well, lost root when I upgraded to it. Reverted to 20.1 and all seems well again.
[Magisk] Ch3vr0n:
20.2 + 7.5 work fine on my pixel 3 xl
[Magisk] unexpected0ne:
I flashed Magisk 20.2 on OnePlus 6 Android 10 and it doesn't work. I think the phone can't build app's cache, because it's stuck on "Phone is starting...". If I forcefully reboot it, the apps are crashing and nothing works. I'll try the previous version maybe.

[edit] It works with 20.1
[Magisk] HippoMan:
Thank you very much for your reply.

I'm sorry, but I don't know what you mean by flashing "madurai" ... ???

Is that a spell-check error when "Magisk" was being typed? In any case, could you perhaps provide more details?

Again, what I want to accomplish is this ...

(1) Flash a new ROM via OTA

(2) Do something which does the equivalent of ...

*** Flashing the "A/B retention script"

*** "Install to inactive slot (after OTA)"

... and I want this to occur in a way where I can continue to use Magisk-v20.1

How would I accomplish this using TWRP?

To be clear, I know how to flash the ROM via TWRP or to flash via the OTA mechanism and then re-root by flashing Magisk. However, I specifically want to end up with the exact, same outcome that would occur if I flashed the A/B retention script and "Install to inactive slot" step.

PS: I'm using a OnePlus 7 Pro running the 10.3.0 OS version, and I'm using TWRP 3.3.1-70

Thank you very much.

.​
[Magisk] abalam:
Latest magisk running great on my oneplus 7t 10.0.7
[Magisk] abalam:
:svetius:
[Magisk] tlxxxsracer:
I've updated my Magisk manager and zip, before I was using Magisk hide so I could play PoGo. After updating and then trying to hide Magisk, after it installs it prompts "upgrade to full magisk managto finish the setup". Tap ok and magisk restarts and then says the same message over and over. Restarting the phone doesn't help. I've unrooted and re-rooted. Same issue. Running op7 pro latest stable magisk, OOS 10.3.
[Magisk] Dor71:
I have the same problem.
[Magisk] Hiro Nakamura:
Issue has appeared on github

https://github.com/topjohnwu/Magisk/issues/2211
[Magisk] ktmom:
I'm sure the "madurai" is an auto-correct for manually.

Many no longer install TWRP since at a minimum it creates additional complexities. For those of us who don't install, but might use TWRP, it's fastboot booted instead of installed.

I'm guessing the "A/B retention script" is osm0sis' TWRP Retention script/module to move TWRP to the inactive slot.

1) Do all of this manually in TWRP - I would expect the TWRP installer zip for you device flashes recovery to both slots like other devices - and flash the Magisk version zip you want in recovery.

2) You may be able to set the current manager to consider the v20.1 version an "update" by configuring the custom channel to use the v20.1 stable.json file. See the following posts to get the gist of a previous discussion.

The link to the 20.1 stable.json
[Magisk] HippoMan:
Thank you *very* much!

I have already tried doing this via "Do all this manually in TWRP", but I can't get it to succeed. Not sure why.

But your second suggestion is what I was hoping for: i.e., I want to treat 20.1 as the "latest" version, so I can make use of the standard "Install to inactive slot" functionality. I didn't know how to do that before, but now, I set up the custom channel with the URL to the 20.1 stable.json file you mentioned, and now Magisk indeed thinks that 20.1 is the version to flash when I use "Install to inactive slot". So this solves my problem.

I'm going to put that JSON file into a URL on a web server that I control, so that I can always get to the file if I need it in the future.

Thank you again, very much!

.​
[Magisk] rafal7933:
Oneplus 6t 10.3.0 work great. :good:
[Magisk] newkydawg:
Was waiting to see someone's experience updating a Pixel 3 XL so thanks for posting. My process, for those wondering, was to disable/delete all modules, reboot and then update using Direct Install (recommended). I rebooted, installed Active Edge and Systemless Hosts modules, rebooted again and all is well. :good:
[Magisk] Ch3vr0n:
Besides default systemless hosts, I don't use any modules. So usually always works immediately and flawlessly. The only trouble I had was with the launch of Android 10 until magisk properly handled it. Since then, no issues whatsoever.
[Magisk] DiamondJohn:
The following is NOT a supported feature of Magisk, but in the previous version (20.1) I was able to see the Magisk logs by accessing the databases directly. For example, to get a summary of the root requests and the results, I could run the following.

if [ -f /sbin/.core/db-0/magisk.db ]; then
MAGISK_DB=/sbin/.core/db-0/magisk.db;
else
MAGISK_DB=/data/adb/magisk.db;
fi;

sqlite3 $MAGISK_DB -column -header "SELECT app_name, package_name
, COUNT(*) AS total_count
, SUM(CASE action WHEN 1 THEN 1 ELSE 0 END) AS allows
, SUM(CASE action WHEN 0 THEN 1 ELSE 0 END) AS disallows
, SUM(CASE action WHEN 0 THEN 0 WHEN 1 THEN 0 ELSE 1 END) AS unknown
, COUNT(DISTINCT from_pid) AS unique_pid_count, MIN(time) AS from_time, MAX(time) AS to_time, MAX(command) as example_cmd
FROM logs
GROUP BY package_name COLLATE NOCASE, app_name COLLATE NOCASE
ORDER BY COUNT(*) DESC, package_name COLLATE NOCASE ASC, app_name COLLATE NOCASE ASC
LIMIT 1000"

The database /data/adb/magisk.db appears to no longer have the root request and their results. Does anyone know where it has been moved to?
[Magisk] bark1234:
anyone??
[Magisk] Vuska:
Anyone can help please...

After i click hide magisk manager and then manager create a new magisk manager with other name as usual.... but if i open it... error appear .. even i click ok, its still appear same error.

Magisk manager 7.50

Magisk 20.2

Samsung S10+ SD with android Q.
[Magisk] MrPierc:
Hello, i use this tutorial from BostonDan (many thanks) from Septemeber 2019 until yesterday and all worked like a charm!

https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950

I use Latest weekly Rom + Magisk 19.4 (working always) + SQLite + Terminal like in #1 post. Everything works fine. I can add my Mastercard Bank card to Google Pay and i can pay in market. But i CANT add meal card (Edenred, mastercard).

I try Factory reset, i try Magisk 20.02 = but Magisk stop working and i must "Format data" in TWRP. Now Magisk 19.4 or 20.2 still no accept add meal card!

Thanks for advices!

– MI9SE, MIUI Rom Based on China Stable / Weekly builds (MIUI 11.2 by Xiaomi.eu 20.1.2 weekly).

– Android 10 QK1. 190828.002

– Security patch 2019-11-01
[Magisk] Greight:
I'm on Nougat. Today updated to the latest version (20.2) and suddenly noticed all the rooting had gone. Checked Magisk and saw the red message saying that Magisk is not installed. I tried to install via TWRP, but although the installation seems to be successful there, the same message appears again in Magisk manager. Any idea?
[Magisk] guhvanoh:
If you're getting segmentation faults, you've got serious problems. Could be anything. What's the temp like on the device when you're doing this? Have you got the correct version of everything? Is your hardware good?
[Magisk] Greight:
Just installed version 20.0 with Manager 7.4 and everything seems to be fine.
[Magisk] jcmm11:
Try /data/user_de/0/<package name>/databases/sulogs.db
[Magisk] DiamondJohn:
Woo-Hoo!

I keep on forgetting to check in user_de, whenever it actually IS:mad: thanks:good:
[Magisk] Didgeridoohan:
A call-out for all LG users experiencing issues with Magisk v20.2.

Thank you to those who tested the builds. This issue is now fixed upstream (Canary build 20202) and will of course be fixed in the next stable release.

If someone that uses an LG device could test the Canary builds since Magisk v20.1 and see where booting breaks that would make things a lot easier in figuring out what's wrong.

Here's download links for the Canary debug builds after Magisk v20.1 was released up until the current Canary (20201), sorted by release date. Start from the top and install them one by one (can be done from the Manager Modules section, use the "+" button, from TWRP, or your preferred method of choice) until you find the release that no longer boots. Once you have that info, please report back, directly here in the thread (please tag me if you do) or through PM. Thanks for your attention.
[Magisk] ktmom:
Try uninstalling then reinstalling Magisk manager.
[Magisk] jonners59:
I have a Samsung Galaxy S7 SM-G930F running Superman ROM. I have tried to upgrade my Magisk Manager and Magisk to the latest, yesterday but it has failed.

First tried via the Manager. The Manager updated, but Magisk wouldn't.

Then tried flashing the Magisk 20.2 via my recovery. Seemed to go OK, but when logged in it is not rooted and shows up as an upgrdae in red in the Manager - but again fails to install.

Tried uninstalling Manager and flashing via recovery - still did not work

Tried the Magisk-uninstall, then flashing and again the Magisk does not install.

Tried to install the apk for the Manager and now that won't install either....

Update. Just managed to install the Manager again using pak, but still not able to install the Magisk zip

GGGRRRR - HELP!
[Magisk] HippoMan:
Proper method for downgrading Magisk?

I'm running a OnePlus 7 Pro with OOS 10.3.0. Last week, I upgraded Magisk from v20.1 to v20.2, and I ran into problems. So I tried to downgrade back to v20.1 simply by going into TWRP and flashing Magisk-v20.1.zip. But then, I got into a boot loop and couldn't bring the system back up. I ended up having to go through a tedious unbricking exercise and reinstalling TWRP, v20.1, my OS, etc.

I am thinking of trying v20.3, but if it fails, I'd like to know the proper procedure for downgrading from v20.3 back to v20.1 that won't end up hosing my device.

Thank you in advance for any tips, pointers, and suggestions.

.​
[Magisk] frooB:
Xiaomi Mi 9T pro hiding Magics ends in "Upgrade to full Magisk Manager..."

Hello and a Happy New Year,

I just installed Magisk and Magisk Manager, all working fine.

But now I tried to hide Magisk Manager (tried "Mag.sk Manager" and "ManagerX") but after hiding it seems that it cannot find itself anymore somehow?!?

When I start the Manager after hiding again I get "Upgrade to full Magisk Manager to finish the setup. Download and install?".

If I uninstall Magisk Manager and reinstall it shows that Magisk is not running.

Any chance to get it work again is uninstalling and reinstall Magisk and Magisk Manager.

I'm running latest stable xiaomi.eu ROM 11.0.5.

Any idea what I'm doing wrong here?
[Magisk] Wolfcity:
Known issue, reported several times and on GitHub.

Wait for a fix, maybe downgrade to 20.1 until then.
[Magisk] frooB:
Thanks a lot for your answer!:good:

Couldn't find it with Google searching for the exact error message. I even cloned the repository and searched trough the source to get correct English error message since I used another language :eek:
[Magisk] jonners59:
Don't. I did that and ended up with more problems. Couldn't get the Manager back. Took a ages.....
[Magisk] ktmom:
If you have the manager hidden/obfuscated and then you try to update or remove it, you may well have trouble. But it's just an APK. There is no reason you should have trouble installing it provided you unhide before trying to remove.
[Magisk] scottyrick:
LG V20 H918: Stable up to and including 12/27 builds

Didgeirdoohan
[Magisk] pendgy:
[MENTION=4667597]Didgeridoohan[/MENTION]

Seems to be guy didn't tagged you in the right way :)

https://xdaforums.com/showpost.php?p=81398637&postcount=37756
[Magisk] gitzolinick:
I can't install last .zip update (20200) on Htc 10, LeeDroid oreo rom.

It doesn't give errors during flash (both from manager or twrp) but when i reboot it is not installed and root is lost.

Thanks for caring about it
[Magisk] bark1234:
Thanks Bro. My device is Mate 20X. Its a pretty powerful device, don't think any issue with temperature or anything.

Probably Magisk for emui10 is not ready yet, thats what i want confirmation on.
[Magisk] DiamondJohn:
Magisk Version: 20.2 upgraded from 19.3 (or whatever the previous stable one was)

ROM: Havoc OS Oreo - 32b

Phone: Samsung S4 GT-i9506

It appears that not all superuser grants nor deny's are being logged. even though logging is on. Confirmed by the fact it does log requests for some other apps.

Here are some screen images of the steps. There is a certificate issue with XDA, so I am running a little blind here with which image is which. sorry.

The setting for the app in question, showing LOGS are ON and so is ROOT.

The log before:

A ROOT request granted:

An action that definitely requires ROOT (ironically its actually is accessing the Magisk log dB directly through a shell script)

and after, with no log of the ROOT access:confused:

I have experienced that:

some apps do get logged.

I appear to have lost my history from before. this app had 000's of request prior

I also tested turning ROOT off for the app in question, forced a failed ROOT request, and nothing was in the logs

If I could provide further/better logging, please let me know.

The app tests for root using:

# Returns 0 (ie no error) if root is available and 1 if not
IS_ROOTED=$(su -c 'ls /data/data 2>/dev/null');
if [ $? -ne 0 ]; then
echo 1;
else
if [ "$IS_ROOTED" == "" ]; then
echo 1;
else
echo 0;
fi;
fi;
[Magisk] Pikkedonker:
Hia, Got the same Rom and Phone (latest TWRP) and the same thing happened to me!

Installed older magisk zips (18 and higher) and still the manager said "not installed".

Tried all kind of solutions...to no avail!

I ended up reinstalling the rom and leaving as is... if I find solution I'll post it here.

Good luck!
[Magisk] cooledi:
Hi all, how to i update magisk fromv20.1 to 20.2? Do i need to uninstall in twrp first?

Is it the same procedure for v19 to v20 as well, thx.
[Magisk] ISoreo:
What's your device bros? I think Magisk's app can direct install. if can't patch your boot.img with your magisk download and flash in TWRP
[Magisk] akilinaroho:
should I upgrade from 20.1 to 20.2? is it critical update?
[Magisk] ktmom:
If you're happy where you're at, wait awhile

---------- Post added at 11:52 ---------- Previous post was at 11:50 ----------

I think it's a good habit to disable modules before updating. Then if the module is behind development, you won't bootloop because of it.
[Magisk] Ch3vr0n:
Just received the januari ota for Pixel 3 xl. Standard ota procedure worked fine. Magisk installed and functional
[Magisk] rogers11:
Same here, Pixel 3a and Magisk 20.2. :good:
[Magisk] samep:
Update from Magisk 20.1 to 20.2 along with MM update went fine for me as well. I don't have to use the stub method to hide MM so I don't as long as that's true.

OTA to January Android 10 security update went just as expected with Magisk OTA update method (with Magisk 20.2).

Essential PH-1 on latest stock Magisk rooted Android 10...

I'm guessing it takes a while to see Google Play certified device? Or was that removed from latest Play update?

Edit: Yes, certified device status returned after a while.
[Magisk] shoey63:
I updated my Sony xz2 from pie to just released Q without a full wipe. Booted up fine. I then patched the Q boot image with Magisk and fastbooted it.

Big mistake.

I forgot to disable my modules which are for pie, not Q, so got into a bootloop.

Flashed stock boot image again and recovered. Only problem is I don't have root access to /data to delete the modules. No Q twrp yet and Pie twrp won't decrypt /data so that's not an option either

Anyone know how to patch the boot image with Magisk to boot in core only mode so I can remove the offending modules?
[Magisk] Pkt_Lnt:
Try the adb commands in the code box about half way down the page.

https://www.didgeridoohan.com/magisk/MagiskModuleIssues
[Magisk] grushnickij:
[MENTION=4667597]Didgeridoohan[/MENTION]

LG G6 h870 user here. Canary from nov 21st is the first to boot into fastboot. Nov 14th works.
[Magisk] Didgeridoohan:
Thank you for testing. That means that the issue already has been fixed upstream for your device. You can confirm this by installing the current Canary (build 20202).
[Magisk] VantuzProper:
Literally the worst root solution out there
[Magisk] MrFhenix:
WARNING

Samsung S9+ g9650 USERS DONT UPDATE

using version 19.300 UPDATED TO 20100 no problems WEEKS no problems

updated to 20200 and F#^$$ bricked phone

couldn't use even recovery MM or nothing

lost everything..

No Way of getting even LOGS

:(
[Magisk] guhvanoh:
I guess that means you've implemented your own and you're about to spam this thread with it?
[Magisk] VantuzProper:
No, that means that SuperSU is way better than this, but because of topjohnwu SuperSU is now dead and we have no alternative to magisk, which is the worst root solution ever made
[Magisk] grushnickij:
I can confirm, new Canary (build 20202) works on LG G6 H870.
[Magisk] Didgeridoohan:
I wasn't going to address your previous post, but since this statement is completely wrong I'll just add this:

SuperSU is dead because CCMT, Coding Code Mobile Technology LLC (and the company behind it), bought SuperSU and then simply abandoned it when they realised they couldn't make any money from it. Not because of [MENTION=4470081]topjohnwu[/MENTION]...

Please continue any further discussion on similar topics in a constructive manner.
[Magisk] N1ghtr08d:
I found a bug in 20.2 . If you want to hide magisk by replacing it with the "manager" app, when you complete the change from magisk manager to manager it attempts to download magisk on first opening of the app and that's where it constantly crashes and loops back to downloading magisk in the background again and again.

The only fix for this I've found is to flash 20.1 and make the change and then install the updates after you've switched over.
[Magisk] vandyman:
And they provided ZERO support when they acquired it from Chainfire.
[Magisk] virag2009:
I've also promlems installing Magisk 20.2 on my Galaxy S7 g930f with newest Galaxy Project Rom. Update Magisk 20.1 to 20.2 failed. Tried in Recovery, restart and ended in lost Magisk without root. Only solution was a clean installation of old Magisk 20.1 via Rom installer in revovery mode. So I will stay on 20.1 and wait.
[Magisk] jelbo:
So with the new way of making modules, am I supposed to write my own customize.sh script to set permissions on files? I'm new to this, but I want to do a simple file replace that needs specific permissions.
[Magisk] HippoMan:
With regard to my question, above, I'm wondering ... if I do a nandroid backup in TWRP of boot, system, and data, and if I then upgrade to Magisk-v20.3, could I then revert back to my current v20.1-based system simply by restoring the nandroid backup? Or does Magisk affect other partitions besides simply boot, system, and data?

The OnePlus 7 Pro is based on A/B boot-slot architecture, if that makes any difference.

Thank you.

.​
[Magisk] Didgeridoohan:
If you need anything more than the default permissions that the module installer script gives to files (644) you are going to have to add that to customize.sh, yes. But that's nothing new, it was the same with the previous module installation setup, you just for the same in the install.sh script...

Magisk specific variables and functions that can be used in the customize.sh file are described in the docs:

https://topjohnwu.github.io/Magisk/guides.html#customization

Magisk normally only touches boot (or recovery on A-only SAR devices) and data.
[Magisk] jelbo:
Thanks. I got it to work.