yashsingh1/xdaforums huggingface dataset:
[Magisk] sk8223:
Looks like FGO stopped working with Magisk 19.2. Either that, or it's something to do with my device not being supported or LOS 16 (doubt it's the ROM). It worked yesterday but neither NA or JP work for me today. I did try the latest Canary build but it's not helping. Keeps detecting the device as rooted with error code 60 even though MagiskHide is enabled for both, and Magisk is hidden. I have other devices to play on, but I'm surprised it was working the first time I tried it.

EDIT: So it can't be the device model. I tried on my Le 2 (which is running an OEM ROM) and FGO JP works fine no problems. It has to be Magisk/FGO's hatred of custom ROMs.

Or... it could be my kernel? I am running a custom kernel, but yesterday I wasn't. Hmm. EDIT: Nope, flashing to the stock kernel didn't solve it.

EDIT: Problem solved, and it was so hilariously simple I'm laughing right now.

Thank you.

I didn't need to patch the kernel. Just had to make sure FGO sees my ROM as a stable ROM rather than a Nightly. Phew! Magisk is not at fault here.
[Magisk] svcopio:
Its installed on internal storage. Have no sdcard on the device yet
[Magisk] DawoodSahi:
Not able to flash magisk 19.2 on the latest OOS 9.0.6 on my oneplus 6. After flashing through TWRP, right after booting it shuts down automatically and boots back to TWRP.

Nvm, I'm dumb. Fixed
[Magisk] guest4711:
Without logs, details about your setup, etc. pp. it's impossible to help further. We don't know whats going on with your device..

To analyze someone would need a log starting with booting in core only mode until have used your cam and the same without core only mode.
[Magisk] Watanabe_You:
Thanks for the mini heart attack. No problem lol
[Magisk] 0ddj0b7:
I had to turn off magisk hide for one of my app. I received a popup from Google or the play store saying i needed to remove the app from system folder.

What's going on with that? Anyone else experience it?
[Magisk] YaPaY:
stuck at samsung logo

everything was working till update 19.2 now these versions stuck at samsung logo

19.2

19.1

works only 18.1 but I am getting FC if I go to ANdroid/settings

wipe dalvik cache doesnt help either I see only apps counting with "Android is starting" but nothing more.

I need help

phone s7 edge int exynos

rom black magic 6.0
[Magisk] hfam:
Pixel 2, Pie, June sec update, 19.1 >19.2 update worked flawlessly, no issues and no flaws. As always here, using full system image update method (remove -w from flash-all) provided by [MENTION=6842057]nathanchance[/MENTION]. Works every time!

As always, megathanks to [MENTION=4470081]topjohnwu[/MENTION] and the rest of the prolific crew here who bend over backwards to help anyone at all. You know who you are!

Lastly, MMs new look is awesome, excellent job!!
[Magisk] flaxx187:
since i installed the newest version directoly my wifi only works when i reboot my phone with flymode

i have pocophone f1
[Magisk] jasio2k:
Same here

I got exactly same problem with my phone, Resurrection Remix 7.1.2 [Sultanized] Unofficial. But the thing is I got two same phone one of them same rom same modules same FW and I getting vanishing modules,random reboots, or magisk not installed. Another phone same config same apps all works fine LoL.

Wird :/

Edited:

I haven't got much time to play within longer, so no logs @ moment because my wife need working phone :)

The thing is what I spotted is reflash stock Oxygen any version 7.x 8.x 9 give same results magisk not installed, vanishing modules after reboot, or just random reboots. Reflash phone using MSM Flash Tools (as bricked) give the same results. Then restore phone one more time and installed magisk 19.1 (also 18.1) and get same thing again on another phone all work fine. The only one difference was TWRP version my wife phone have 3.3.1-0 I using 3.2.3-1. When I got possibility to play with it again I post log and results.
[Magisk] sdz2:
Removing and reinstalling the Xposed module broke Magisk modules and I cannot remove them.

I recently removed the Xposed module, passed SafetyNet, upgraded the Netflix app from the Play Store, and reinstalled Xposed. That worked successfully.

Now my Magisk modules are all wonky. Xposed works. However, Emoji One and ViPER4Android stopped working. The emojis aren't replaced and ViPER is missing.

I tried removing them, but they stay stuck at: Module will be removed after reboot. I cannot remove them. Installing them again does not restore functionality. Also, mm could not remove them.

I deleted them from /data/adb, which removed them from Magisk. Then I reinstalled to the same behavior.

What should I try next?

Magisk 19.2 on Marshmallow
[Magisk] KitsuneFoxy:
Does anyone have the module that i think was called iOS 10 i think keyboard/typing sounds? When you typed it would play the ios sounds.

And anyone have an archive of modules anywhere?
[Magisk] GarlicBreadFox:
How is it that flashing magisk makes TWRP "persist" or "survive". What are the technicalities behind it? (e.g TWRP is installed in this but with magisk it persist by being installed in that).

To explain I followed a tutorial to root my Redmi Note 7 and it was recommended to flash magisk after initial boot/setup after a custom ROM, to make TWRP persist, if I understood correctly. Now I'm doing a tutorial for a Huawei Watch 2 that is a bit different and same, it says to flash magisk to make TWRP persist.

---------- Post added at 02:11 ---------- Previous post was at 02:11 ----------

How is it that flashing magisk makes TWRP "persist" or "survive". What are the technicalities behind it? (e.g TWRP is installed in this but with magisk it persist by being installed in that).

To explain I followed a tutorial to root my Redmi Note 7 and it was recommended to flash magisk after initial boot/setup after a custom ROM, to make TWRP persist, if I understood correctly. Now I'm doing a tutorial for a Huawei Watch 2 that is a bit different and same, it says to flash magisk to make TWRP persist.
[Magisk] wang4632:
latest 19.3 still not work on Sony xperia 10( model: I4193), caused bootloop, :(
[Magisk] Daytor:
EDIT: Resolved the isssue by reactivating magisk hide.
[Magisk] Razen657:
Mobile Network not available(cannot connect to mobile network) after updating to 19.3 (Xperia XZ, F8332)
[Magisk] vip5912:
Magisk 19.3 SafetyNet false

19.2 was true

Optimized Lineage 16.0 (Android 9)

Samsung Galaxy S4 i9505

Log: https://pastebin.com/mr2xXMRa

P.S. SOLVED

If SafetyNet starts failing after an update to either Magisk, the Manager or both it's usually fixed by toggling MagiskHide off and on

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet_fails_after_an_update
[Magisk] bohemist:
New Magisk update all good on OnePlus 6 with the latest OTA, 9.0.6 :good:
[Magisk] Didgeridoohan:
Basically the boot image needs to be patched to not replace TWRP with the stock recovery (something that is done by default on an unpatched system).

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet_fails_after_an_update
[Magisk] whoosename:
No issues here with Xperia XZ Premium G8141
[Magisk] ISoreo:
Magisk 19.3 restart randomly

i upgrade Magisk 19.2 -> 19.3 completely, since my device reboot around 2 minute my device will restart again until i turn off my device

now i restored image and reflash Magisk to 19.2 and problem about restart itself never happen again

Here is a log from Magisk that i already grab it

View attachment magisk_log.txt
[Magisk] heynando:
What's the procedure to update Magisk considering the method of installation was "image boot patching" ?

Should I repatch the boot image every time Magisk is updated? Or that's only necessary when flashing an OTA?
[Magisk] garylawwd:
Direct install.

It even has 'recommended' in brackets
[Magisk] vip5912:
"If SafetyNet starts failing after an update to either Magisk, the Manager or both it's usually fixed by toggling MagiskHide off and on" is working!

Thanks.
[Magisk] akxak:
Good morning... just installed Magisk 19.3 on my OP 6.

After successful reboot, various applications including MagiskManager stuck in the splash screen, many apps did not start at system start.

No modules are used, a reboot did not help.

Reverted to 19.2 which is running smooth.
[Magisk] Didgeridoohan:
Magisk log won't be much use for that...

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] ISoreo:
Grab this after flash 19.3 View attachment log.rar

[MENTION=4667597]Didgeridoohan[/MENTION] I restored magisk image and revert to 19.2, then upgrade to 19.3 and hooray the problem is clear! thanks for help sir about grab a logcat by using ADB thanks again
[Magisk] YaPaY:
unsupported/unknown image format

I am getting this error during installation 19.3

device s7 edge exynos
[Magisk] heynando:
So my Google pay is detecting root and I'm unable to use NFC to pay, I was using 19.2 then I updated to 19.3 but unfortunately the issue persisted. Magisk hide is activated, the package name of the manager has been obscured too, I did Mark NFC and Google Play services as well as Google pay inside Magisk hide. I also disabled third party apps that edit the hosts file but the module is still on.

All in vain it seems since it still managed to detect root. I want to debug this and go to the bottom of it. Help?

PS: The current configuration was enough to prevent root detection across all my bank apps except Google pay
[Magisk] garylawwd:
Theses a whole thread dedicated to Google play with magisk.

Your better off asking there for a reply :good: https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703/page153
[Magisk] Ænimal:
Connecting to WiFi first did the trick form me..
[Magisk] Fentadroid:
Hello.

I've a Google Pixel 3a. Yesterday i've updated it with the OTA file through adb sideload.

Once rebooted, of course root was gone (TWRP not yet released).

I've picked up boot.img from current factory full image and patched with Magisk Manager.

As the previous ROM release i gave the usual

fastboot flash boot boot.img

boot.img is correctly pushed to the current active slot but when i reboot the phone i always got this screen.

Even if I push "Try Again", same result.

All i can do is fastboot flash back the original boot image and the phone is live again.

Tried also with magisk 19.2 and 19.3.

Is there anything i can do to underestand the reason why i cannot root the phone anymore? (at least without factory reset...)
[Magisk] Artim_96:
Which options did you set in manager?
[Magisk] kryshnakishore:
What modules do you use bro
[Magisk] Fentadroid:
The only option i can set is the Update Channel. (stable / beta).

Tried with 19.2 and 19.3, same result.

It doesn't work even if i try with the patched boot.img posted in 3a xda thread by a user.

Something is going wrong but i cannot underestand why it fails.

I tried to flash the ota again, the full factory rom without wipe data.

Every time it fails.....

With the previous ROM (March security update) i didn't have any problem. Now, after the update, there is no way to root again.
[Magisk] Artim_96:
No, on the main screen under advanced settings. Make sure both are enabled
[Magisk] Fentadroid:
I'm not rooted anymore, so i guess that's the reason i don't have any option on the main screen......
[Magisk] vandyman:
I am in the same boat as you are. I updated to the June update and tried the patched boot.img, but just get a boot loop..

I even installed tried the full factory update leaving the - w option on to wipe data. And I still get the boot loop. Odd....
[Magisk] Fentadroid:
Ok, so i guess that was not my fault..

Try

fastboot flash boot_a boot.img
fastboot flash boot_b boot.img

Using the original boot.img got from the factory full image.

than reboot to bootloader and switch off the phone.

If it fails and ask to try again........ try again....
[Magisk] Didgeridoohan:
That's been fixed (https://github.com/topjohnwu/Magisk/commit/fc26de48b283ec2d96e9580fc1384fad757421b6), but since there are still some blocking bugs with the current code for the Manager it won't be updated until that's taken care of.
[Magisk] Fentadroid:
Ok so i guess boot.img is not correctly patched.

We have no other ways to root now, TWRP has not yet been released....
[Magisk] cnjax:
19.3 working fine on my LG V20
[Magisk] vandyman:
I was thinking the boot.img was not patched as well.

Factory boot.img is 64 + MB and the patched IMG is 27 + MB. Very odd it would be less when patched...
[Magisk] lscambo13:
Hi,

I need some info about the Magisk repo but I couldn't find a place to ask my question. Please guide me if this is the right place.

My module, (https://github.com/Magisk-Modules-Repo/DualSpeaker-X01BD-ZenfoneMaxProM2), seems to disappear from the Downloads tab (for everyone, not even searchable) in Magisk manager and comes back after sometime only to vanish again. A lot of users have faced this (including myself ?). Kindly look into this.
[Magisk] cerbero931:
On lg g6 boot loop on last update, then i force restar and boot ok.
[Magisk] belloni:
Hoping someone can help with my bricked phone - https://xdaforums.com/huawei-p20-pro/help/p20-pro-bricked-tried-everything-t3936563

Is this because I haven't flashed stock boot after being rooted with Magisk?!

I've tried flashing the uninstaller through TWRP but I get "Updater process ended with ERROR: 1"
[Magisk] Tombab:
Previously all updates since 18.1 have been successful and there's been no problems. But now after updating to 19.3 safetynet fails both tests. I have tried to reinstall and repackage manager but no help. I guess I'll try removing magisk and reinstall completely, unless I manage to brick my phone in the process lol. GT-I9505 + LOS 15.1
[Magisk] Didgeridoohan:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet_fails_after_an_update
[Magisk] maybeme2:
I downloaded the latest Magisk Manager (7.2.0) from the announcement thread link and installed it. But it does not have the 'Advanced Settings' section.

The instructions I'm following to root my phone

https://xdaforums.com/moto-g7/how-to/moto-g7-twrp-root-t3914112/page8

need the Advanced Settings to avoid bootloops.

([*] Make sure under advance setting both keep dm-verity and keep force encryption are checked, otherwise you may get stuck in a bootloop)

At my last effort to root my Moto G7 with Android 9, I did end up in a bootloop that finally required a phone reset and reinstallation of everything to get out of.

Is there something I need to do to access the Advanced Settings of the latest Magisk Manager in version 19.3?

Thank you.
[Magisk] Didgeridoohan:
https://xdaforums.com/apps/magisk/m...systemless-t3432382/post79669242#post79669242
[Magisk] mrsubway:
You'd need Magisk installed. I can't be of more help. I'm amazed how lucky I am. I'm on a rooted AT&T H931 capable of using the US998 firmware, and have had ZERO issue with Magisk, even the 19 variants. I would suggest this. Download Magisk 18.1. Flash in TWRP. If no bootloop, flash the 19.3 in Magisk Manager, NOT TWRP. I've done all my updates in the manager, and I've been fine. ??*♂️
[Magisk] aqsede:
Hi,

I have an issue right now with magisk latest v19.3

On OnePlus 6T v9.0.14 I just updated both the same time. At first there's is an issue of my phone quickly shutting down into recovery after booted (i can see power off dialog with pin and fingerprint sign) after several hours of trying I found a solution inside TWRP that say " FIX RECOVERY BOOTLOOP". But, sadly magisk is gone. Tried flashing magisk again, and same thing happened and I need to apply the twrp fix. I don't know if it's due to v19.3 and OOS V9.0.14. I'll try older magisk after this, since it's 5am and I was stuck at this for hours figuring up what to do.
[Magisk] chazall1:
Magisk-v19.3 running great here.

Thanks to all
[Magisk] hfam:
Pixel 2, Pie, June sec upd, 19.2 > 19.3 using full system image flash (remove -w), all working perfect.

As always, gracious thanks to TJW and everyone who makes Magisk so damned fantastic!
[Magisk] maybeme2:
I miswrote. It's Magisk Manager (7.2.0) that does not show the advanced settings to keep dm-verity and keep force encryption checked,

Also is it true that Magisk 19.3 does not patch boot.img for the Moto G7 correctly? Is there a version that does?

Thanks.
[Magisk] sdz2:
I can no longer install or remove Magisk modules. They are stuck on "Module will be removed on the next reboot."

I tried rebooting and removing from mm in TWRP Terminal.

Also, some Magisk modules don't work anymore. For example, Emoji One has been installed the whole time, but I see factory emojis. I cannot uninstall them to reinstall.

This occured after:

- Disable XPosed

- Pass SafetyNet

- Update Netflix app from PlayStore

- Enable Xposed

- Confirm Xposed modules work

Magisk 19.3 (also failed yesterday on 19.2)

Marshmallow
[Magisk] Axel85:
Hi , I have a strange problem with my tablet . I can root it with magisk but can't get magisk hide to work . The option simply won't stick after closing the app or reboot , and apps looking for root are not working . It's the first time I have this problem and I'm using it from the beginning of it's release . The rom is based on android 5.1.1 on nexus 10 , and it's named remix os 2.0 . Everything I've tried to make it hide didn't work and I'm going crazy . Can you help me?
[Magisk] Artim_96:
Well, you can always remove them by simply removing their folder.

But is the remove file set properly in the folder when you select remove?
[Magisk] sdz2:
When I remove the folder, it no longer appears in Magisk. When I redownload the module, it does not function and I cannot remove it from Magisk again.

Magisk manager does add and remove the remove file when I toggle the trash can icon, but the module remains after a reboot
[Magisk] wbedard:
I had the same issue you described, same phone, OS and Magisk version. I had a little think about what Magisk modules I've installed since my last OS update and I remembered one that specifically advised to uninstall it (which I obviously forgot about...) before doing an OS update because of possible bootloops. From a booted recovery (TWRP), I used the file manager to view the installed Magisk modules (/data/adb/modules) and simply deleted the folder of the suspect module. After that, the phone booted normally. Perhaps you have encountered a similar issue?

R/

wbedard
[Magisk] kryshnakishore:
Everything works fine but after some random time I loose root.. I need to reboot & reflash the zip to get root back to normal. Is there a fix?

Magisk 19.3

OnePlus 6, 9.0.6

Twrp blue spark 101

Blue spark r89 kernal
[Magisk] XtraWater:
19.3 running fine on Mi A1.
[Magisk] jcmm11:
Try https://xdaforums.com/apps/magisk/magisk-installed-workaround-t3908748
[Magisk] hfam:
Final Update:

All is well with 19.3 and Play Store. A series of coincidental fails with PS happened moments after updating successfully. Bottom line is PS was doing some eff'd up attempt to update Wear, an app which needed no updating, and was freezing up while it failed to sort itself out. Deleted Wear, reinstalled the kernel with 19.3, and it's working 100%.

MUCH LOVE to [MENTION=4487388]jcmm11[/MENTION] for taking time to explain that the kernel can be flashed from previous sec update versions (within the main version, of course) and "Magisk'd kernels". That saved me SO much time and grief!!

Original post:

Pixel 2, Pie, June sec upd, Magisk 19.3

Anyone else having Play Store issues? It just locks up. I have cleared cache, cleared storage, rebooted, power off/power on, uninstalled updates, and no matter what once it updates to current it freezes on start.

Not sure what to do at this point. Ideas?

UPDATE: I've managed to get, via uninstall updates", play store functioning fully, but it's back at version 13.x. It is showing all my apps, etc. I rolled the kernel back to 19.2, but haven't closed play store yet to let it update to 15.x. About to do that. I still suspect Magisk 19.3 as the culprit, I'll weigh back in when I know more. Meantime, anyone having a similar issue?

Update 2:. Got PS working with latest update on Magisk 19.2. I got an odd persist toast saying PS was checking for Wear updates, and it did nothing when selecting it. I did have Wear installed, no updates needed. Nuked the Wear app and after a moment PS came back to a weird "App Not Found" msg. Hit back, forced close, restarted it and it appears to be working now. About to flash kernel with 19.3 Magisk and confirm all is well.
[Magisk] GarlicBreadFox:
1. What is the difference between say, youtube vanced as a magisk module and apk version? Would both install to same location? I assume magisk module "safer"?

2. Where are the main repos configured or the sources for modules, could I add a custom one if I wanted? Or in short where does magisk vanilla gets the list of modules from (maybe the github repo magisk-modules?)
[Magisk] tftcamilo:
OP6T 9.0.14 Magisk 19.3 working fine. Before updating I uninstalled the Magisk modules, I rebooted in twrp, I uninstalled Magisk. Flash 9.0.14, flash zip twrp, reboot for recovery, flash Magisk 19.3
[Magisk] sagorahmmed1:
so many useful modules are removed in latest update, that's makes me feel bad...
[Magisk] danishajaz:
Hi, after installing 19.3 my phone does not boot. I'm a multirom user and it looks it 19.3 removes multirom somehow. After flashing multirom again I can boot again into my device but I can see I have 19.2 installed. Any solutions to install 19.3 as well as keep multirom? I'm using a oneplus 2
[Magisk] KitsuneFoxy:
Agreed, lost some modules for my old phone.
[Magisk] lohanchien:
Wondering if someone is familiar with the following issue. I installed 19.3 this morning and everything was fine until about an hour ago when I noticed I completely lost root. I rebooted into TWRP and updated TWRP to 3.3.0-1 and then installed Magisk again. On reboot I got the "your device is corrupt" message but pressing resume loads Android fine. Now I'm not sure if this was caused by Magisk or TWRP so I'm posting in both threads. What's curious is that this issue usually happens if you flash with old ADB versions on the pixel 3 but I didn't use ADB. Anyone familiar with this?
[Magisk] pankozin:
Upon installing magisk one oneplus 7 pro, charging screen phone off animation absent. The same was on oneplus 6,6t.
[Magisk] kotuamoalt:
Why not just upgrade using the direct install feature?

---------- Post added at 05:57 AM ---------- Previous post was at 05:50 AM ----------

Try deleting them in the "data/adb/modules" directory

---------- Post added at 05:59 AM ---------- Previous post was at 05:57 AM ----------

It does not sound like a TWRP issue to me. Unless you are booting into recovery, TWRP shouldn't have anything to do with it.
[Magisk] apollonaute:
Hello guys,

I encounter some issue with 19.3: after reboot, I can't "open" any app from my launcher.

I've got a standard OnePlus 6, with TWRP 3.3.1-2 and I tried to pass from Magisk 19.2 to 19.3.

I'a back in 19'2 now.
[Magisk] Didgeridoohan:
https://www.didgeridoohan.com/magisk/MagiskHelp

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

1 - One will be installed as a system app, the other as a user app. Both work good.

2 - If you just want to install your own custom module, you do that from the Modules section of the Manager (the "+" button). If you want to submit a module to the official repo:

https://github.com/Magisk-Modules-Repo/submission/blob/master/README.md

There's not been any removal of modules from the repo since the big purge a month ago.

Try clearing the repo cache in the Manager settings and then reloading the list.

https://github.com/topjohnwu/Magisk/issues/906

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] lohanchien:
Thanks but I was referring to the "device is corrupt" message not the issue of losing root. I'm aware there are other people having the issue of losing root and I'm already using the workaround module. And I did boot into recovery to install Magisk. Sorry I'm not sure I understand your statement.