yashsingh1/xdaforums huggingface dataset:
[Magisk] JIJOK:
A little question here :D All zip modules can be flashed with twrp ?? Download it with magisk but install via twrp

thanx
[Magisk] zputnyq:
Yes, it can be flashed using twrp
[Magisk] Nixer:
On OP6T I did a magisk complete uninstall post which it went into boot loop as it did not find backed up boot image. This was really strange as somehow magisk uninstall expects that backed up boot.img (or dtbo) exist in /data.

Does anyone think this is a mistake/potential problem when the flash script itself deletes the backed up img files?

From https://github.com/topjohnwu/Magisk/blob/master/scripts/flash_script.sh @ line number 118 and 125.

@ line number 118

if [ -f stock_boot* ]; then

rm -f /data/stock_boot* 2>/dev/null

$DATA && mv stock_boot* /data

fi

AND then..

@ line number 125

if [ -f stock_dtbo* ]; then

rm -f /data/stock_dtbo* 2>/dev/null

$DATA && mv stock_dtbo* /data

fi

I had to use MSM tool to reinstall (and lose all data) as there was no boot image to revert to (and I didn't have TWRP to play around).

Any comments? Is boot image really backed up during magisk install? Should a (stock) boot image be taken before (re-)installing magisk?
[Magisk] Didgeridoohan:
Magisk creates a backup. The code you're looking at removes any old backup and then puts the new one in place:

$DATA && mv stock_boot* /data
[Magisk] daddylonglegs:
I have a question. Magisk hide works perfectly for me. Even with edXposed framework and GravityBox installed, it passes SafetyNet check! That is amazing!

Here's the weird thing: the Nintendo Online app still detects this somehow. As soon as I open it, it force closes because I am rooted. How is it that Android Pay, my banking apps, and Snapchat cannot detect root, but this stupid Nintendo Online chat app can? What is Nintendo doing? Is there any way I can get around it? I have the app blacklisted, I have it enabled in Magisk hide, and I have the Magisk Manager hidden. What trickery is Nintendo doing that only THEY can detect root/Xposed/Magisk?
[Magisk] Nixer:
Thanks [MENTION=4667597]Didgeridoohan[/MENTION]

But why is it that there is no file named /data/stock_(boot|dtbo)* ? Just checked via TWRP.
[Magisk] BHUSHAN7988:
Google pay for India also fails while registering and making payment but if I deny telephone permission to google play service it works fine

Try this

Reply if it helped
[Magisk] daddylonglegs:
Should I deny telephone permission to Google Play or to the Nintendo app?
[Magisk] Brakiss:
Pixel 3xl on April build. Google pay worked fine on previous beta, just upgraded to 19005 and broke my gpay.

Can I downgrade or am I screwed?
[Magisk] kotuamoalt:
You will have to uninstall, and then reinstall magisk. Have you tried deleting gpay app data?

I used Gpay yesterday using build 19005.
[Magisk] BHUSHAN7988:
"Google Play services"
[Magisk] Estebanium:
Hi there, after updating my finances app it detects my root even if I use Magisk Hide. Somehow Magisk is not able to hide busybox that I installed via Magisk Managers download repository. Any help would be appreciated.
[Magisk] Didgeridoohan:
The Busybox module from the Magisk repo does not install to /sbin, so you likely have leftovers from some old installation laying around.
[Magisk] Estebanium:
Thank you for reply. I newer installed a different edition than that. Unfortunately I tried to delete the folder in TWRP, but it is created every boot again. Is it possible to find out what is mounting that file there? I removed all root apps, so I have no idea what is messing with my OS..
[Magisk] daddylonglegs:
Thank you. I did that, rebooted, and still somehow the Nintendo Online app is detecting root
[Magisk] BHUSHAN7988:
Bad luck then buddy
[Magisk] zputnyq:
That left over probably come from/with the kernel you used. Maybe you can ask the kernel dev/read changelog of the kernel you used.
[Magisk] jcmm11:
What ROM are you running? Do you have a custom kernel installed? My guess (and it's only a guess) is that you're running a custom ROM with whatever kernel the ROM comes with and that that kernel is installing busybox on every boot.
[Magisk] zzz2002:
I found that I had to go to "Magisk hide" and check my banking app BEFORE opening for the first time.

My bank has two apps. For one them if it opened and found a problem it closed and must have set some flag as even after I had set Magisk it would not open. It had to be reinstalled before I could get it to work.

However Magisk did the job.
[Magisk] daddylonglegs:
I know but I think the Nintendo Online chat app should be investigated by Magisk devs because it detects root in some way that other apps aren't using, but might start using soon
[Magisk] Ingan121:
I got it running by Magisk 19005 (canary).
[Magisk] akxak:
The Nintendo app works on my mobile with Magisk 19 beta and it did with the 17.x
[Magisk] daddylonglegs:
Weird. Mine just force closes as soon as I open it. I wish I knew why. It's a Pixel on Pie.
[Magisk] Xdevillived666:
Hi folks, just a question : is blueline supported on Android q yet?
[Magisk] martyfender:
Magisk 19.1 stable has been released.
[Magisk] gkornaks:
Where's download folder in Magisk v19.1?
[Magisk] guest4711:
It's your usual folder, e.g. /storage/emulated/0/Download
[Magisk] akxak:
Did you try to delete the app's data (aka reinstall)? It might have stored somewhere that it once detected root...
[Magisk] wilsonhlacerda:
Have you hide Magisk Manager itself on its settings?

Have you deleted Busybox module zip (and others!) downloaded to you memory/sdcard after install? Some apps search for them and other files that may be related to root some how.

After doing all that (and other mitigations) have you uninstalled the bank app, rebooted and reinstalled it to try again? Do that.

By the way, Magisk v19.1 and new Manager have been just released. Try them.
[Magisk] gkornaks:
For some reason after updating to v19.1 I can't find magisk zip and MM apk in there?
[Magisk] VasiliyZ:
19.1 does not give root rights in the "vendor" section. In the "system" all is well. I install 18.1, root rights in the "vendor" section work.
[Magisk] smart123123:
05-02 01 : 41 : 46. 596 8723 8723 E AndroidRuntrme

java. Iang. Runti meException Unable to start

activity Componentlnfo{com. Android. settings/

com. Android. settings. Settings$MagiskActivity)

android. content. ActivityNotFoundException Unable

to find explicit activity class (com. Topjohnwu. Magisk/

com. Topjohnwu. Magisk. SplashActivity) ; have you

declared this activity in your Android Manifest. xml?

Can someone help me with this??
[Magisk] Pkt_Lnt:
Probably this -

https://xdaforums.com/showpost.php?p=79444923&postcount=51
[Magisk] XtraWater:
Just updated. MI A1 with RR 6.2. All good.
[Magisk] XtraWater:
What happen to modules which are not longer compatible with magisk 19? I use the RR mic low module. It's still installed and seems to work. But it disappeared from the download list.
[Magisk] plusminus_:
The files I had placed in /data/adb/magisk_simple/ are not mounted after flashing Magisk v19.1, but they were with v19.0. Otherwise everything is working beautifully. :D

Do I need to move the files to a folder within /data/adb/modules/?
[Magisk] Orito:
Just updated to 19100, however after install/reboot, it's detected, but if I close and reopen the app, it's never detected again.

Rebooted the device (OP6) to the same results. Thought I should reinstall, so I downloaded the zip, rebooted to recovery and flashed, but still getting the same.
[Magisk] doctor-who:
Latest reboot causing me random reboots, pls fix this
[Magisk] wilsonhlacerda:
Have to ask for developer (or anyone that can review the code) to update it and resubmit to repository as required by new Magisk v19+ structure.

This was announced 1 or 2 months ago that will happen. Now we have to push late developers/contributors.
[Magisk] XtraWater:
Thank you. Fortunately there is only 1 module, RR mic low, which I use and no longer is in the update list.

Is this module actually not longer working? Methinks it still works. Would magisk mark the module as incompatible?
[Magisk] wilsonhlacerda:
It should be working just because the update process of Magisk itself took care of it. If you unistall it you'll not be able to install it again. (Unless you downgrade Magisk, install its zip if you have it somewhere, and then update Magisk again.)

We have to ask developers of long time not updated modules to update them for Magisk v19+ . That's the path to go.
[Magisk] grigiotitan:
I have a Pixel 3 with android 9. With v19.0 and v19.1 i can't clear cache and user data of the app(Cache and user data of the app is always 0kb). I've returned to v 18. I have also a OG Pixel and I don't have problem with v19.1.
[Magisk] drezz2:
I just updated the manager, I have a question, in the services of google play, it appears marked com.google.android.gms.unstable I do not remember having marked it, does the application mark it by default?

before, could services be selected within an application? (I do not remember) now appears in some applications....... services to select individually in one app?

I just checked that I have a small problem with cerberus, I do not know if the problem is the manager or magisk, when I enter the application is continuously giving the root permission, in the record appears many times in a row "cerberus --allow-- xx: xx "with the same time, which makes it very slow, in addition the prompt remains continuously on screen, this with the previous version did not happen to me any idea what can be?
[Magisk] nurullah192:
Boot problem

New v19.1 problem boot sm-j330f my phone remained on the boot screen pls fix:(
[Magisk] Zafrkant:
Hi, thanks for great contribution.

I flashed v19.1 and after remote no root is detected. I'm using LOS 15.1, Mi Mix 2.
[Magisk] wilsonhlacerda:
Another approach you may have:

I have not inspected this module, but probably what it does is replace the mixer paths file for RR. Isn't it? Just open the zip for it and take a look. If so, if you don't mind to touch the real /system of your device (not systemless!) what you can do is manually replace the file yourself. Just copy it under TWRP file manager to /system/etc (backup your original file first!) or when booted copy it to /sbin/.magisk/mirror/system/etc/mixer_paths.xml Be sure its permission stay like original one (probably 644).

This way you'll have your device system already moded and no need of Magisk module anymore. But you'll have to apply this change every time you update/reinstall your RR.

---------- Post added at 11:41 PM ---------- Previous post was at 11:35 PM ----------

Run mm module under TWRP and set Magisk to core only. Then reboot to system. Try that.

If you don't have mm module previously installed, download its zip from XDA thread and flash it under TWRP.

---------- Post added at 11:46 PM ---------- Previous post was at 11:41 PM ----------

Magisk Hide: yes, that's default and the new way it works. You can fine tune it.

Superuser: I'm not sure if I understood your point, nevertheless just go to Magisk Manager settings and check Superuser apps, and other settings like toast, time,..
[Magisk] wongfeihung1984:
Hi there, I've just downloaded and installed the last version of magisk (v19) like I did all the other times but this time it failed.

Could something be kind enough and explain what I did wrong?

Thx
[Magisk] InfX:
Updated to Magisk v19.1, everything fine on my Nexus7, but getting "Magisk not installed" now on my SGS7-G930FD (7.0, near-stock). Temporarily did a dirty downgrade to v18.1 via TWRP as a workaround. Any proper solutions?
[Magisk] wongfeihung1984:
Same here...although I haven't installed the previous version via TWRP yet.

When I try to select and patch the file via it days I should select a .tar or .img file but the magisk.19 file is a zip file?
[Magisk] XtraWater:
It seems you're right. The zip archive contains system/etc/mixer_paths_tasha.xml

For now, I leave it as it is. I'm happy enough the magisk update didn't cause any bootloop or worse. However, I'll keep this in mind and might replace the file if there won't be an update by the developer of the module.

Thank your suggestion.
[Magisk] drezz2:
this is what I was referring to, I enter the app and the toast is continuously showing up (I have it in 10 seconds) but it is minutes ... it seems that it is continuously requesting permission, and the phone is very slow

I do not know how to solve it .. if the problem is from the manager or magisk and I have to go back to the previous version of the two or one (if its possible)
[Magisk] t-ryder:
Magisk Manager just showed an update for the app and magisk (to 19.1). Latest Pie stock ROM on Pixel 2 XL. Updated the app, then updated magisk using the app (recommended); unfixable bootloop.

This reminded me, that no matter how comfortable the manager app is, and usually it's all good with magisk... it is better to have an up to date complete backup.
[Magisk] wilsonhlacerda:
Well, what this shows is that Cerberus itself is asking for root continuously. Try stopping it, clearing its cache, them remove it from superuser on Magisk, then run Cerberus again.... so it ask for su for the 1o time and that gets registered again under Magisk.

Besides that I can only suggest to completely uninstall Cerberus, reboot, then install it again (from a trusted source....).

I myself have lots of root apps and after upgrading to Magisk v19 I'm not having any problems with them or Magisk su itself. But I don't have Cerberus.

---------- Post added at 12:18 AM ---------- Previous post was at 12:13 AM ----------

Backup always when playing with critical system stuff. Better a complete TWRP backup.

Concerning Magisk, also always have the MM module installed. Fortunately you're lucky and can do it under recovery yet:

Run mm module under TWRP and set Magisk to core only. Then reboot to system. Try that.

If you don't have mm module previously installed, download its zip from XDA thread and flash it under TWRP. Then run it on terminal per instructions: ./sdcard/mm
[Magisk] t-ryder:
Yeah, I know... backup before flashing. Well, my brain was in standby mode and ready to sleep. I flashed a factory image now and will try carbon ROM or something. :silly:

Thanks for the interesting hint though.
[Magisk] drezz2:
I just did it and the result is the same, with the previous version it did not happen to me, and Cerberus has not changed, true that with other apps it does not happen to me, but I do not understand what can be wrong
[Magisk] levone1:
Issue with latest update... I was using 18.1 steadily for quite some time, many modules installed, verity disabled, etc., and I got ota update notification today, so flashed it. Installation went fine, no errors, and updated zip and Magisk Manager. On reboot, Magisk shows 'not installed'. Tried again, and same. Tried to uninstall and downgrade zip and Manager, and same. I had a backup of system, data, and boot, and I restored the backup - still the same, 'not installed'. Tried wiping cache, etc., but no change. Flashing always shows successful patch, and no errors or issues, but now, no matter what I do, it always shows 'not installed'.

Sony Xperia XZ2 Compact, stock Pie.

Thanks for any help, and thanks for all your work.
[Magisk] richyg81:
updated from v18.1 to v19.1 but after reboot I get asked for "password to decrypt storage"

I have a PIN not a password and I couldn't even access any keyboard to try and enter it

I was able to flash v18.1 in twrp so I'm safe again for now.

In advanced settings I can see that the first option "preserve forced encryption" was ticked. I have no idea whether these should be ticked or not, but guessing not as my device is not encrypted.

Huawei EMUI 5.0.3 Android 7.0

any advice welcome thanks
[Magisk] Homeboy76:
Yes: QBeta DP2

Did you read this: https://xdaforums.com/showpost.php?p=79444923&postcount=51
[Magisk] nacos:
Same problem here. Samsung S8 (SM-G950F) running Android 7.0
[Magisk] wilsonhlacerda:
LOS14.1, Android N, no encryption, here. All fine.

Previously Magisk v19.0 and its Magisk Manager. Updated Magisk Manager first. Then from it updated directly (suggested) Magisk to v19.1. All fine. Running without errors as far as I could test Magisk, modules, Magisk Hide and Superuser.

Afterwards I got a problem with updating Xposed Systemless module (that was also updated today by John), but solved it. Details on the Xposed module thread.
[Magisk] nacos:
Same problem here. Samsung S8 (SM-G950F) running Android 7.0 however I was able to revert to 18.1 by uninstalling Magisk from recovery (use the official uninstaller), then reflashing Magisk 18.1. Unfortunately, in the process you'll lose all previously installed modules and you'll have to also reinstall Magisk Manager. Upon reboot you'll need to find, reinstall and reconfigure all your modules. :(
[Magisk] Zaben:
Xperia 10 Plus previously working with 18.1, direct installing 19.1 caused boot loop. Manually patching the boot image and then fastboot flash also causes boot loop. Fastboot flashing previously working 18.1 rooted boot image now shows "Magisk is not installed."

Edit: I3223 on Stock OEM Android 9 ROM ver 53.0.A.4.114
[Magisk] levone1:
Oh yeah, I forgot to mention - when I first installed through Magisk after ota notification, I also bootlooped on reboot, and a strange bootloop. It never even made it to the 'device unlocked' screen, but it was like a half-second screen flash loop over and over. Then I started using recovery to attempt flashing, and got the situation I described above...
[Magisk] Golf c:
No sir. New stable update does not support logical partitions. Just supports Q beta devices without logical partitions. Pixel 1+2

https://www.xda-developers.com/magisk-v19-1-stable-android-q-beta-2/
[Magisk] hammondegs:
Happy to report no issues updating to 19.1

S6 edge G925I, stock rom 7.0, ultimate kernel, debloated.

Everything works as it should including banking app.

Well done dev:good:
[Magisk] smart123123:
05-02 01 : 41 : 46. 596 8723 8723 E AndroidRuntrme

java. Iang. Runti meException Unable to start

activity Componentlnfo{com. Android. settings/

com. Android. settings. Settings$MagiskActivity)

android. content. ActivityNotFoundException Unable

to find explicit activity class (com. Topjohnwu. Magisk/

com. Topjohnwu. Magisk. SplashActivity) ; have you

declared this activity in your Android Manifest. xml?

Can someone help me with this??

Plz can anyone help??
[Magisk] ISoreo:
After Flash 19.1 i found something about Riru-core and Riru-EdXposed in my device and after reboot is stuck in splash screen, i decided to remove by using mm and suddenly it's work! so what's wrong for EdXposed and Riru-core because i never flash this module??
[Magisk] Homeboy76:
Thanks for the information on Q beta devices without logical partitions.
[Magisk] walkwitmeinhel:
Emui 9.1 cant boot in magisk 19.1 ..anyone have similar issue
[Magisk] TheMadRuffian:
I updated to Magisk 19.1 from Magisk 18.1 using the built in installation feature (the recommended one). On reboot, the apps started to freeze on opening and after a while no apps would open. I had to use the Magisk uninstaller and then root the phone again by flashing Magisk 19.1 zip from TWRP.

Device: Mi A1

Rom: Pie sGSI (April 5 security patch)
[Magisk] jdmst77:
I had a couple issues. I updated to 19.1 through the Magisk Manager app.

1. 1st boot hung at boot animation

Pulled the battery

Booted into TWRP

Wiped cache and dalvik

Flashed magisk zip

Rebooted system

2. 2nd boot booted but now shows a vendor image mismatch error for HUAWEICLT-L29. (Will attach screenshot later. Issues attaching on mobile)

LG G3 D851

LOS 15.1 Official

15.1-20190429-NIGHTLY-d851

EDIT:

Same error on another similar device:

LG G3 D851

RR Oreo Official

RR-O-v6.2.1-20181215-d851-Final
[Magisk] martyfender:
https://www.didgeridoohan.com/magisk/MagiskHelp

---------- Post added at 11:34 PM ---------- Previous post was at 11:32 PM ----------

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

---------- Post added at 11:56 PM ---------- Previous post was at 11:34 PM ----------

Did you follow the special instructions for EMUI 9+ devices here in the updated instructions?

https://topjohnwu.github.io/Magisk/install.html
[Magisk] Zaben:
This was in logcat after reverting to v18.1 which no longer works after attempting v19.1.

Device: Sony Xperia 10 Plus (I3223), Android 9 OEM ROM 53.0.A.4.114_R5A
[Magisk] pkn267:
I flashed v 19.1 after v 18.1 . But it fails in safety net. Now whenever I try flashing the v 18.1 it never gets flashed instead it shows magisk is not installed. Help
[Magisk] pero.mikic:
Same problem with my Samsung Galaxy S7 Android 7.0

I was using 18.1 steadily for quite some time, many modules installed, verity disabled, etc., and I got ota update notification today, so flashed it. Installation went fine, no errors, and updated zip and Magisk Manager. On reboot, Magisk shows 'not installed'. Tried again, and same. Tried to uninstall and downgrade zip and Manager, and same. Now back to 18.1 but have to install all modules again. :rolleyes:

The update on my Galaxy S6 Android 6.1 no problem.

The update on my HT one8 Android 6.1 no problem.

The update on my 2 Cubot Dinosaur Android 6.1 no problem.

Maybe an Android 7 Problem?
[Magisk] polygon21:
same exact problem, downloaded zip from both magisk manager and github, installed with latest twrp without any errors but ends up 'not installed' as well.. went back to 18.1 again...
[Magisk] Estebanium:
1. I am running Lineage OS 16 by Ivan_Meler with MoroKernel by morogoku

2. Yes this is my only assumption, because if I uninstall busybox with BusyBox by Stephen (Stericson) from Google Play Store it is reinstalled with the next boot. Magisk Hide is working fine as the test with RootBeer shows, but the existence of busybox at /sbin is what uncovers Magisk Hide.

I disabled all Magisk Modules (not uninstalled) to be sure, that busybox is not installed by a module. So the only thing left is the Kernel and the OS. Is it possible to track the source down, so is there any location that runs a script to install busybox, that I could check?
[Magisk] ZanyDreamer:
Xz2 compact bootloop with magisk 19.1

Hi all, just flash the stock rom version 52.0.a.8.25 on my xz2 compact and tried installing magisk through the manager and once i flash the patched boot.img from magisk 19.1 and im stock on a bootloop. I had to flash the stock img to get my phone working again. Anyone can help. Sorry I'm new to this if you need any other info just ask. Ps i dont have twrp didnt find working version for my phone.
[Magisk] pac213:
Can anyone share the disable encryption for magisk 19.1?
[Magisk] exadeci:
[MENTION=4470081]topjohnwu[/MENTION] Note 9 on Pie, up to date on both the manager and magisk install, the manager was in "Magisk hide".

I updated, the manage wasn't seeing 19.1 so I uninstalled it with the new uninstaller and installed 19.0 again, it wasn't seeing it either.

I had to uninstall the manager and re-install it again (the latest) for it to see 19.0 but 19.1 isn't seen again so I'm staying on 19.0 for now
[Magisk] Artim_96:
You can only disable force encryption in TWRP terminal:

echo KEEPFORCEENCRYPT=false>>/cache/.magisk

Before flashing