yashsingh1/xdaforums huggingface dataset:
[Magisk] mrmcshagbag:
Powered off and turned back on and still doesn't work for me. What else can we do to get it to work? Im going to clean flash an update of my ROM today and am wondering if I should use a different version of magisk. Need it to pass safety net for work apps. It was passing safety net ever since install just now started having problems with it.
[Magisk] AndrzejDwo:
Did you already provide logs to let someone actually help you?
[Magisk] dd805bb:
I got the latest canary on 19. Safetynet has never a problem for me on 17 and up. Hiding Google services frameworks and gms helped with my gpay and hiding specific apps. Safetynet can fail if any apps detect root and report back. I tried putting your name in search and found posts of yours from 2017. Nothing recently. Go canary. I was having issues on official. Canary, since I switched has worked great. I am also on a Pixel 3 XL. And have a Pixel and pixel XL. All work great with 19 canary. Also if you have a device with a/b partitions, make sure the inactive slot didn't keep magisk. If you take an OTA without uninstalling magisk first, you can and will leave magisk in the other slot. It will check it during boot and can create a fail.
[Magisk] xdauser'17:
could it be that magisk has some kinda caching mechanism? if it does, after uninstalling mod2 and rebooting, /system/etc/test.txt will now contain "1" (from mod3); then install mod2 again and reboot, it should still contain "1".
[Magisk] _litz:
Anyone having problems with v18.1 "showing as not installed" ?

Getting that repeatedly ... reboot, and all is well for around 24 hrs, then it goes "not installed" again.

Latest manager version, w/Magisk 18.1 on a Moto X Pure running stock 7.1.1.
[Magisk] MaFiBoSS:
Update:

I jumped from v18.1 (STABLE) to v19.0 (BETA) + Magisk Manager v7.1.0, and the TV Vodafone app its working again (need to close the MM in background). Only the PS4 Remote Play app, v2.8.0 continues to detect the root.

If upgrade the Magisk Manager to v7.1.1, can't pass the SafetyNet and the Magisk Hide not working properly (all apps detect root).

Just my feedback.
[Magisk] dd805bb:
How are people on 7.1.1 manager but on 17.1 or 18.1 and not showing an update? Official has been released. Also a lot of problems from just upgrading. TJW has put out different installation methods for devs on 19 and up. Also posted about 17.1 not working on the new installation methods. Read his Twitter. There is a link in magisk. Even if you don't have Twitter you can view it via a browser. Q&A on there to help a lot of people. Gpay was failing. I suggest going and finding that work around and apply that to any apps detecting root. Because this thread is clogged with simple fixes already out there. Most these posts are easy and or simple fixes with just being on the most current magisk the right way. Old modules from pre 19 don't work on 19. Installer is different and the whole repo is changing to that method by a certain date. 17.1 is old and outdated. 18.1 is getting there with the new ways. Catch up.
[Magisk] James_Oakley:
I've looked through his Twitter feed going back to before the (beta) release of 19.x, and can't find any tweets that specifically address the bootloop problems people are reporting on here, or how to solve problems with Google Pay. There's lots of Q&A for module devs, but nothing I could find for upgrading / installing the latest versions of Magisk. Which tweet in particular did you have in mind?
[Magisk] dd805bb:
IDK. But these look pretty interesting.. pretty much says what I wrote...
[Magisk] dd805bb:
Use any app in place of gpay. This will get apps to not recognize root. Data folder you will delete will be dependent on the app you are hiding. This has worked on gpay and any other app giving me ****.
[Magisk] dd805bb:
And bootloops are on you. No one will know or can know what you did to get a bootloops. Only you can achieve that. But Google search still works. And there are many many solutions out there. If you are on the newest manager and old magisk framework, best of luck. Information above says no way. I wouldn't mix managers and frameworks. Period. And since the newest installation for devs is changing, I would be on the latest that has all the fixes. Not an old version frameworks and newest supported manager.
[Magisk] Zilla0617:
Is there a way to update monthly security update while keeping root and modules intact? Currently I install factory image while removing -w but have to re-root my device and reinstall all my modules. Thanks

Edit: on pixel 2xl
[Magisk] roles75:
After installing Magisk19 no reboot is possible! I'm only in the download mode. I install Magisk 18.1 put Magisk on Stable, and this action is an info to the developers.
[Magisk] iankelly2001:
You should be able to get into Recovery mode from the Download mode. On the Samsung Galaxy S5, whilst the phone is in Download mode, you can force the phone into Recovery by holding down VOLUME UP + HOME + POWER buttons together for at least 10 seconds until it comes out of download mode (the screen will eventually go blank before booting into TWRP). Or remove the battery, replace and use the same three button process above.
[Magisk] acoolfriday:
Guys, I have a huawei Mate 20 (HMA-L29) which doesn't have a compatible twrp recovery, as a result, I installed Magisk using the patched .img file downloaded from this post and everything works fine.

Today I installed a bad Magisk module and got a bootloop after reboot, I flashed back my stock recovery file and it revived without Magisk enabled. Now my problem is to remove those bad modules and re-enable Magisk, without root access or getting into twrp recovery.

As every time I enabled Magisk by flashing the patched img, it will enter bootloop mode again, even the Magisk Manager is uninstalled completely.
[Magisk] roles75:
As I come from the download mode I know, Thanks anyway. If I find time, I will try your guidance. Or the stable version appears ...
[Magisk] jcmm11:
Do you have adb access? What version of Magisk did you install?

Not sure if it'll work even with adb access. You'll probably need root within adb.
[Magisk] jcmm11:
You shouldn't need to reinstall modules no matter what. Although flashing the factory image while removing -w will require you to re-root. But all the modules are stored in /data/ so as long as that's intact, and you don't run the Magisk un-installer, they should remain.

As far as monthly updates see https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
[Magisk] acoolfriday:
Yes I tried creating a ".disable_magisk" file in /cache via adb shell but it was showing as permission denied.

I have v18.1 installed, nad Magisk Manager v7.1.1
[Magisk] jcmm11:
In that case I'm afraid you have to do a clean install and wipe data. You should be able to backup everything in /sdcard/ via adb. I might be able to come up with something for future use. Let me think about that.
[Magisk] acoolfriday:
Thanks for your reply, backing up my data now. I may have to stop trying new modules until we could have a solution for this case.
[Magisk] markoscekic:
Latest Magisk Manager doesnt see installed magisk 18.1 or 19

What could cause the problem?
[Magisk] James_Oakley:
Just to say - thank you for taking the time to type up all those pointers.

I'm not getting bootloops. But I am holding off upgrading from the 18.2 former canary build to the 19.0 beta, because I'm reading here of many people getting bootloops to resolve when they do precisely that. I may wait until 19 goes to Stable.
[Magisk] awadh730:
Hi

I faced a problem with flashing

Patched_boot.img created by magisk manager apk

Anyone can help?

The problem is the device show warning :

The system has been broken

Long press volume-down to shutdown

After flash the modified patched_boot.img.

ther is no custom recovery for my devices .
[Magisk] provolinoo:
I have a small question:

If I'm on Pixel 2 XL with latest stock android + magisk and I get a notification about ota update, can I go on with automatic update or it will fail?

If I keep stock recovery installed (instead of twrp) does the ota apply properly and magisk isn't removed?
[Magisk] dd805bb:
Depending on what device you have, sounds like you just installed magisk, which will knock out twrp even if it was installed before. I don't install twrp and fastboot boot it every time. Works better. Installing twrp and magisk I found causes problems in the long run of things. Twrp is great. And works. But no need to install unless you flash all day everyday. Then, in that case, just reinstall it. Should be fine if you had it before.
[Magisk] Strephon Alkhalikoi:
If you have TWRP installed you cannot take an OTA automatic update. You have to download the full OTA and flash it in TWRP. If TWRP isn't installed you should have no problem taking the OTA, but you will lose root as the OTA update flashes a new kernel.
[Magisk] jcmm11:
If you look closer most of those people are on a Samsung, so factor that in as well (don't know if you are or not). Might even be specific models. And if you had no problem with the Canary just before 19 you'll almost certainly have no issues with 19.

---------- Post added at 02:10 AM ---------- Previous post was at 02:05 AM ----------

I just posted this at the top of the page with your post https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
[Magisk] kotuamoalt:
That was the procedure that I used to get magisk 19.0 up and running on my Verizon S5. The only difference, is the file names you are using. If I am not mistaken, the canary builds are all variants of 18.x. 19.0 is a beta build because it is SO different from 18, that he labeled it as a beta build. And are "experimental" and "beta" not essentially the same thing? I'm pretty sure I used the same files you are referring to, but I likely renamed them to eliminate confusion, as I had been downloading a lot of different magisk files. Also, unless the module you are using is also updated, it will likely cause a problem.

Google Pay was declined on first use. I then deleted the card(s) on file and re-entered them.

ALL GOOD! :good:

EDIT: I am on build (1900)
[Magisk] :
And if he has a custom kernel installed on his Pixel 2 XL ?
[Magisk] martyfender:
No, look at:

https://github.com/topjohnwu/magisk_files/tree/master/canary_builds

The very latest Canary is v19, as seen in the notes.
[Magisk] Strephon Alkhalikoi:
It will be overwritten by the kernel included in the OTA. Unless Google does what Lenovo does for OTAs, in which case the OTA will outright fail.
[Magisk] kotuamoalt:
Magisk ver. 19.0 has caused Flashfire to no longer work. It sees that the phone is rooted, but cannot access any functions. Does anyone know if there will be a fix for this in a future release? As Flashfire is no longer in development, any fix would have to be on the magisk side.
[Magisk] dd805bb:
Best guide ever!! Listen to TJW. Wise man say, that was and is TJW. Seriously he has so much out there to find and get answers. He is awesome about giving detailed instructions. I read the read.me on all his stuff. Also he put comments on the releases. Just a heads up for everyone. Got time to tinker, well read what TJW says. And I guarantee us saying all this stuff to help, came from the Man himself, TJW.
[Magisk] DragonFire1024:
Flash fire was designed to only work with SuperSU. And not all versions of flash fire work for every rooted device with SuperSU. So it's a catch 22. The software is obsolete now, yet still serves an invaluable service to many devices. One has to ask if it's worth the time to do the work that goes into maintaining something as complicated and labor consuming.
[Magisk] kotuamoalt:
Flashfire was absolutely designed to work with magisk. It is the NEW (19.0) version that it does not work with. Was working fine 5 days ago. If it never works again, I can live with it. It was convenient, but not Irreplaceable.
[Magisk] James_Oakley:
Thanks for the encouragement. I'm on OnePlus 6T, which is full A/B unlike the Samsung. The Canary I'm using is 18.2.x.

So I'll wait till I've got time to recover if there's a problem, take full Titanium backup etc., and then give it a go.
[Magisk] DarkCorax:
Ive been waitting for long time face problem. Forces close when you open MagiskAPP then i tried to flashed beta v16.3 to 18.1.

After they release Magisk V19.0 My Samsung Galaxy Tab A7.0 (Unofficial LineageOS) seems perfectly fine

When i got encountered error 1 then i force flash backup Boot.img then flash again Magisk v19.0 done magisk app no more force close.

I can now install module latest compatible with magisk v17.0 to 19.0. Nicely done Devs
[Magisk] kotuamoalt:
That was a brutal read.

But I'm happy for you.
[Magisk] kamieniarz:
I have an issue with my OnePlus 6T OxygenOS 9.0.12, Magisk v18.1. I guess this issue is Magisk related

Phone randomly reboota with a soft boot loop of the OxygenOS (no need to type SIMcard PIN after reboot).

Is there any way to fix it?
[Magisk] martyfender:
I am on 5 Nextbook Ares 8A's, x86, Android 6.0.1 tablets. I have some of them on the latest Canary builds and other on unofficial builds.

On one of the devices where I have put the latest unoffical, v2019040201. I get this error in the magisk.log:

* Setting up internal busybox
execve /sbin/.magisk/busybox/busybox failed with 8: Exec format error

Logs are posted in the unoffical thread.

All modules I have installed are functional but they don't show up in modules or downloads in the Magisk Manager.

Does anyone have any idea what the above error means?

I asked in the unofficial thread but never received an answer.

Thanks
[Magisk] pacman00700:
Hi,

Any one use the latest uninstaller?

I used it to uninstall magisk and it also uninstalled TWRP and I couldn't boot to the o/s.

Am I doing something wrong?
[Magisk] guest4711:
Magisk fails to detect your system architekture. So it tries to use arm(32) binaries for your intel (x86) platform. This fails...
[Magisk] martyfender:
I suspected that as well, but if that is the case I don't think I would be able to execute it in the terminal at:

/sbin/.magisk/busybox/busybox

It is topjohnwu's version of busybox

Maybe [MENTION=4544860]osm0sis[/MENTION] has some idea about it?

Thanks
[Magisk] DarkCorax:
Here's my proof.
[Magisk] kotuamoalt:
No one asked you for any proof.

But great.
[Magisk] DarkCorax:
Here's my proof Beta Magisk v19.0 works Samsung Galaxy Tab A 7.0 Lineage OS :victory:
[Magisk] jcmm11:
Assuming that was you who posted on GitHub I gave you a possible hack there.
[Magisk] XtraWater:
Once the new version is available on the stable channel, make it sense to update it when on the device is running oreo 8.1?

In this case it's RR 6.2 final on a MI A1
[Magisk] provolinoo:
Thanks for the explaination :)

So the best way seems to be keep TWRP recovery and flash full OTA + Magisk when a new update comes out

I assume this tutorial works with stock recovery only
[Magisk] jcmm11:
Stock recovery, stock kernel
[Magisk] jasonbiggs:
Anyone get Chase working with Google pay on version 19? For that matter couldn't even get it to work on version 18. Keeps detecting root. Thanks.
[Magisk] NYLimited:
Used to work fine on 18.1 till recently. Now it fails to work in stores. Have not had time to play with it.
[Magisk] James_Oakley:
Yep, seamless. :D

Just booted into TWRP, flashed Magisk 19.0 over the top of what I already had, and rebooted. Easy as pie. (OP6T)
[Magisk] bsports666:
Does anybody know how to completely uninstall magisk? Because when I try to uninstall and reboot my phone the phone stuck on boot... I would like to uninstall and fresh install again via twrp. Thanks for answer
[Magisk] Badger50:
Push the uninstall button usually always works for me. Then I also flash my stock boot.img to make sure since I have a A/B partitioned device.
[Magisk] psychoela:
Magisk : apk_install: /data/magisk.apk

04-03 17:13:22.064 904 904 I Magisk : apk_install: cmd: Can't find service: package

04-03 17:13:27.167 1862 1862 I Magisk : apk_install: cmd: Can't find service: package

04-03 17:13:32.238 2410 2410 I Magisk : apk_install: cmd: Can't find service: package

04-03 17:13:37.380 2849 2849 I Magisk : apk_install:

04-03 17:13:37.380 2849 2849 I Magisk : Exception occurred while executing:

04-03 17:13:37.380 2849 2849 I Magisk : java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.app.usage.StorageStatsManager.isQuotaSupported(java.lang.String)' on a null object reference

04-03 17:13:37.380 2849 2849 I Magisk :	at com.android.server.StorageManagerService.getAllocatableBytes(StorageManagerService.java:2916)

04-03 17:13:37.380 2849 2849 I Magisk :	at android.os.storage.StorageManager.getAllocatableBytes(StorageManager.java:1754)

04-03 17:13:37.380 2849 2849 I Magisk :	at com.android.internal.content.PackageHelper.resolveInstallVolume(PackageHelper.java:188)

04-03 17:13:37.380 2849 2849 I Magisk :	at com.android.internal.content.PackageHelper.resolveInstallVolume(PackageHelper.java:148)

04-03 17:13:37.380 2849 2849 I Magisk :	at com.android.internal.content.PackageHelper.resolveInstallVolume(PackageHelper.java:163)

04-03 17:13:37.380 2849 2849 I Magisk :	at com.android.server.pm.PackageInstallerService.createSessionInternal(PackageInstallerService.java:502)

04-03 17:13:37.380 2849 2849 I Magisk :	at com.android.server.pm.PackageInstallerService.createSession(PackageInstallerService.java:404)

04-03 17:13:37.380 2849 2849 I Magisk :	at com.android.server.pm.PackageManagerShellCommand.doCreateSession(PackageManagerShellCommand.java:2415)

04-03 17:13:37.380 2849 2849 I Magisk :	at com.android.server.pm.Pack

--------- beginning of crash

04-03 17:14:58.476 517 595 I Magisk : proc_monitor: [com.google.android.gms.unstable] PID=[8429] UID=[10011]

04-03 17:15:30.518 517 595 I Magisk : proc_monitor: [com.google.android.gms.unstable] PID=[10816] UID=[10011]

Please help anyone?:D
[Magisk] bsports666:
Thanks I was not know that I got to flash boot.IMG again after uninstall. Mybe that's why I got stuck at boot.
[Magisk] Badger50:
I've done it with and without the boot.img, however, as with anything android, YMMV :cool:
[Magisk] Strephon Alkhalikoi:
On our device (Pixel 2 XL), the order is OTA, TWRP, then Magisk. This is because of the recovery no longer being a separate partition but part of boot.img.
[Magisk] etillxd:
So, here are my TWRP logs, logcat didn't gave me any logs.

Recovery pastebin.com/TduuprvP

Kernel pastebin.com/hNEs5w1m

There's also a Github issue, maybe the others could post their logs there too?

github.com/topjohnwu/Magisk/issues/1271
[Magisk] jasonbiggs:
Yes. That's the uncertain part. Even though credit cards installed fine doesn't mean that when you are ready to pay it will work. Maybe Magisk v. 20 will outsmart the banks. Lol.
[Magisk] kotuamoalt:
Ver. 19 works fine.
[Magisk] yhjc:
After installing some mods on my OP6, my phone now thinks it's like half OnePlus 6 and half Pixel XL. Its happened before, I just can't figure out which module does this. Anyone know of my situation and a fix? Thanks
[Magisk] Didgeridoohan:
One of your modules is changing some props, sounds like. Start by listing your modules, otherwise it'll be impossible to know...
[Magisk] yhjc:
Yeah my bad haha

Adb fastboot

Ainur James

Ainur sauron

Android mic fix

Apt x for Oreo pie

Audio compat

Audio modify lib

Bash

BT stack audio

Busybox

Daydream enable

Encfs

Fdroid priveleged

Magisk recovery mode

Magisk hide prop

Nano

Oxymod

Ram management

Razer sound

Safety patch

Sudo

Sysconfig accent theme

Systemless hosts

Terminal mod

Volume steps

WiFi bonding

Xmlpak

Latest OOS
[Magisk] Didgeridoohan:
My guess: Daydream Enabler (it changes a bunch of props to Pixel XL values).
[Magisk] S2kT68m:
Same here. Have you find any solution?
[Magisk] kotuamoalt:
Are we supposed to just guess which modules you have installed? Based on the minimal information you have supplied, I would recommend uninstalling the offending module.
[Magisk] James_Oakley:
No:
[Magisk] Artim_96:
I bet it's mask Magisk hide prop. It can change the device fingerprint, but some apps get the device information from somewhere else. The ones getting it from device fingerprint think you have a Pixel, the rest knows you have a OP 6.

Maybe it's even safety patch, since it's probably doing the same. You might want to use only Magisk hide prop or safety patch since I think both do the same and probably aren't that compatible with each other
[Magisk] yhjc:
Could be. If that's the case, I'll probably just leave it on to use vr. Thanks

---------- Post added at 07:58 AM ---------- Previous post was at 07:54 AM ----------

I'll try those too and Sys config accent theme cuz I know it changes prop too
[Magisk] Didgeridoohan:
I doubt it's either of those, since MagiskHide Props Config only changes the props you set (and I assume you would know if you had set props for a Pixel device) and Safetypatcher sets the fingerprint of a Huawei device.

Don't know which module "Sysconfig accent theme" is, but I couldn't find any matching module that sets any Pixel props.
[Magisk] yhjc:
Seems that was it. Just double checked by disabling, reboot > enabling, reboot > then disabling, reboot. It changed to OP6 > Pixel > now OP6 again. Now Im wondering if I should just leave it as Pixel so I can use my daydream... Either way thanks for your help.

Which mod between those two do you recommend?

Edit: Ive decided to keep magisk hide prop.

---------- Post added at 09:41 AM ---------- Previous post was at 09:30 AM ----------

So I know I should've listed them, but honestly I was just being lazy while hoping someone had known of a situation where a magisk mod changes phone's prop to Pixel XL. I couldn't find anything but I'm new to forums in general. Also your recommendation was the reason I asked, but I didn't know which module was offending. If you meant to uninstall magisk altogether, you should be more specific. I can't guess which module you're referring to. ;)
[Magisk] Digiladir:
One Plus 3T - SIM card disconnecting

Dear Community,

I started to have a problem with my SIM card. While playing, my phone got normally warm, but suddenly, the signal drop and phone lock itself. I have to make the gesture again and then sometimes it gets the signal back but usually, I have to restart or switch off and wait until it cools down. It seems to be connected with the temperature of the phone.

I have alreday tried to wipe cache and also chagne the SIM slot, nothing helped. Meanwhile, I had another problem with my phone, it was repaired and I had to root it again, so I have already done this again.

I have Magisk 18.1.(18100) installed. I'm using two modules:

HEVC+SM GC OP3&3T and OP5

OOS Native Call Recording Enabler

Thank you for your help!
[Magisk] Jannomag:
Nope, I deep fried my P10 by flashing wrong update files to get back to Oreo
[Magisk] :
How does it taste now ?
[Magisk] dope77:
Device certified and pass safety net but can't find any of the apps that need safetynet on play store (like netflix....)
[Magisk] danielbulan97:
Heye everybody, I found an app that magisk can't hide from, for now. Its a game that softlaunched today, it seems it has somewhat of a "security engine" since it lists that my phone is rooted and that magisk is the method of rooting (might just be the magisk manager package name) even with magisk hide enabled and repacking magisk manager under another package name.

Any thoughts on how to bypass it?

Name of the game: GiganticX
[Magisk] martyfender:
Did you try deleting the apps cache and data?

If that doesn't work, this guide lists other things to try. If the app is using the same technique that rootbeer fresh uses for detection, there is no known way to hide the app from root.

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

Where did you download the game? I don't see any games on the playstore by that name, just Gigantic. Maybe it is not available in the US?
[Magisk] danielbulan97:
It's a new game from ActionSquare, it's on the front page of apkpure and currently under a soft launch for 30 days for testing.

I tried pretty much everything I could see on the magiskhide page but to no avail, I even talked to the devs on Discord and they said that there is a pretty strict security system.