yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Yes, that's preferred way: patching, renaming patched img to refer the firmware/ROM and Magisk version and keep them for some time in case something wrong turns out about the new patch

For the matter of fact, it's not easy to patch with an older version of Canary. Not imossible but one must be familiar with Github and better to have his own account on Github to be able to setup his own json pointing to that older Canary magisk-debug.zip

To patch with an older Stable is easier, but again one needs to be basically familiar with Github

So better prevent similar troubles by locally keeping some older versions of the patched images (last one you know that worked seemlesly)
[Magisk] HippoMan:
Which banking app? Sadly, some of these banking apps do additional checks, over and above SafetyNet checks. I use Chase, and their app does this. I pass SafetyNet, but that banking app still detects that I am rooted.

In cases like this, there is nothing that Magisk can do to help, unfortunately.
[Magisk] kevk60:
I have patched my boot image and fastboot booted the image, then direct install to get root. Did this with canary version. Is it safe to switch to beta version now that I'm rooted or is it recommended to stay on the canary version. Phone is a one plus 8t running 11.0.5.6 international version. Thanks.
[Magisk] Sid220:
I use Banca Mediolanum app, i pass Safetynet and use MagiskHide and everything was fine until version 21.2
[Magisk] guhvanoh:
If what you have does everything you want/need and more, stay with it. You only need to update if bugs are fixed or there are features implemented that you need. That and to test...
[Magisk] kevk60:
Thanks for the info. Appreciate it.
[Magisk] J.Michael:
Do you have "auto-update" turned off in Google Play settings?

I don't remember if Play Services shows up in list of apps with updates. If it does, I probably take it because at some point update refuses to work with outdated Services.

In Android Settings -> Apps, Play Services has a button to uninstall updates. Maybe you can use that.
[Magisk] HippoMan:
Hmm ... so maybe this could indeed be related to something that Magisk could fix, given that it worked under 20.4 but not now under 21.2. I assume that your banking app was not updated recently, correct?

Unfortunately, I don't know more than this.
[Magisk] Sid220:
You're right, the banking app has not been updated so the problem is related to Magisk but since is related to MagiskHide i opened a bug on Github but has been closed
[Magisk] porotikos:
hello. i have the same problem as above. today, revolut bank app got updated. and all of a sudden, my root is detected by the app, and closes after displaying a message i have a harmful phone. any ideas or help? magisk is working as should, passes all test and bank apps are hidden.

my other banking apps work fine
[Magisk] Sid220:
Which Magisk version you use? Have you updated it?
[Magisk] porotikos:
magisk 21.2

magisk manager 8.0.5(4802)

running

magiskHide props config 5.4.0-v113

universal safetynet fix 1.0.2 by kdragon

hardware off 1.1 by displax

if i am not mistaken iam up to date. this just happened... probably i am the first to report?
[Magisk] Sid220:
Have you updated the bank app before Magisk? Because my bank app detects root with Magisk 21.2 but not with Magisk 20.4 but i haven't updated the app
[Magisk] porotikos:
first i updated magisk 2 days ago, and then the revolut app got autoupdated today. if i go to a previous magisk version, then google pay wont work...

at this point i dont know what is to blame. if this can be fixed in magisk, i am happy to wait. i would like to know if anyone has any idea what is wrong though. thank you very very much. it is appreciated
[Magisk] Sid220:
IMHO i don't know if blaming the bank apps that use some other way to detect root or blaming some things gone wrong in Magisk. For my problem i'll try some future beta to see if the problem is addressed
[Magisk] angiotell:
Any fix for Google Pay with custom Android 11? Please
[Magisk] Snow_ball:
had this too. installed new 1.10 test 2 version and toggled magisk hide and that fixed it for me - all good again
[Magisk] porotikos:
you are refering to my revolut problem my friend?

i found the 1.10 test 2 version on github.

But isnt this for android 11 only?

i read that on android 10 it causes bootloop? and there was a specific version for android 10. is this test 2 version having and android 10 equivalent?

edit. i just saw that i am running the 1.10 version 2 that was made for android 10 and i face the problem...
[Magisk] zgfg:
Updated from Canary 21202 to 21203, but no good - Viper4Android shows Status Abnormal

That's why I never update directly nor flash through TWRP but patch an image and keep for a while - flashed my yesterday's 21202 patched and Status is back to Normal

Xiaomi.eu A11 beta
[Magisk] porotikos:
found a solution for the revolut problem in reddit. go to magisk app, and hide it (it is an option in settings). then reenable magisk hide for revolut. you are done!!!
[Magisk] Sid220:
Good for you, i already hidden Magisk Manager app
[Magisk] DiamondJohn:
I am going to *GUESS* that the playstore will update regardless of the auto updates setting, its too important/dangerous for google to allow you to not update it. I have never seen the playstore in the list of available updates, I think it updates at the very start of the playstore if there is one available; i.e. no chance to show in a list.

I built a play store detach method, and I have never tested it on the playstore (and actually excluded it in the first release) which has the GMS as an option to be detached. Might be worth a try. ==> TeMeFI
[Magisk] joaomconde:
can you please be more specific?
[Magisk] curiousrom:
Play Services Auto-Updates

Google Play & Google Services updates themselves automatically regardless if you chose Don't auto-update apps automatically or not in Google Play Store's settings & regardless if Play Store is at the foreground or not.

I observed the downloading of Play services in the notifications on both Galaxy S5 G900M LineageOS 17.1 klte + Open GApps Pico and on a S5 Mini with stock Samsung 6.0.1 with my Don't auto-update apps automatically setting.

Never saw Play Services in the list of apps with available updates in Play Store.

***
[Magisk] johnybravojr:
I had everything working using the earlier Carary Build. I updated to the latest Canary Build yesterday (direct install), and now many of my apps are force-closing, most banking apps are detecting root, and MagiskHide list is getting automatically unchecked. Everything's messed up now. Looks like this issue is with the Magisk update, and not with the updated banking apps. And lesson learned: don't try to fix what is not broken!
[Magisk] DiamondJohn:
Its CANARY! by definition its about fixing things so that tfuture functionality can be implemented. Possibly beta or stable would be a better choice. I personally am only on beta as I am on A11, otherwise I'd onl.y install stable.
[Magisk] zgfg:
Stable is now also on 21200 (same as Beta) and therefore as well good for A11
[Magisk] johnybravojr:
I'm aware of that, but in the past, I've had apps detecting root on stable versions of Magisk. So I switched to Canary, which solved the problems.
[Magisk] pndwal:
Universal SafetyNet Fix update:

NB. As Danny indicates here, MHPC remains a vital cog in Magisk's MH gearbox. PW
[Magisk] Sid220:
Can anyone please explain what is "mount namespace" option in Magisk and how can i set it?
[Magisk] potan:
i cannot hide magisk manager in miui 8.1.4.0 android 6.0 marshmallow,

the device Mi5

os miui 8.1.4.0 android 6.0

latest magisk 21.2

what i have try:

-clean install, no internet connnection turn off play protect and setenforce 0

-clean install, turn on internet connection, let gapps update to latest, turn off play protect and setenforce 0

-clean install, turn on internet connection, don't let gapps update to latest, turn off play protect and setenforce 0

can it be fixed? or some workaround?

after searching for a whole day most of i found fixed with setenforce 0 and turn off play protect.
[Magisk] Slim2none4u:
You serched for a day and didn't find this thread? https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/page-7#post-84299679
[Magisk] pndwal:
Latest Canary:

Jan 15

Magisk (04c53c35) (21203)

- Workaround f2fs bugs in Linux that causes bootloops

Magisk Manager (04c53c35) (4818)

- Update scripts for the said fix mentioned above

Jan 17

Magisk (2f5331ab) (21301)

- Sync with public release

Magisk Manager (2f5331ab) (4828)

- Sync with public release

Latest Beta / Stable:

Release Notes

2021.1.16 Magisk v21.3

Happy 2021! v21.3 adds a workaround for devices with buggy F2FS Linux kernel drivers. This F2FS bug may cause bootloops on many devices. Checkout the full v21.0 release notes if coming from older releases.

Magisk Changelog

v21.3

- [MagiskInit] Avoid mounting f2fs userdata as it may result in kernel crashes. This shall fix a lot of bootloops

- [MagiskBoot] Fix a minor header checksum bug for DHTB header and ASUS blob image formats

- [MagiskHide] Allowing hiding isolated processes if the mount namespace is separated

Magisk Manager Changelog

v8.0.5

- fix sepolicy rule copying

V8.0.6

- Minor UI changes

- Update internal scripts

👍 PW
[Magisk] Spartacus500:
After updating to the latest version of Magisk 21.3, I have a problem with the selected root stealth applications, they are hidden, but not checked in Magisk hide, and in the log such info:
[Magisk] zgfg:
With today's 21203 Viper4Android also does not work: Status Abnormal

I can simply reflash between my various saved patched boot images back and forth, last version of Magisk where V4A works is 21202

Anybody else here using V4A, and how is V4A for you?
[Magisk] thomas140:
I already faced this issue since 21.2.

Resolved by changing selinux status to permissive.

No issue after 21.3 also
[Magisk] curiousrom:
That's creating a major global security hole just to install a sound mod like Viper4Android . See SELinux (Security-Enhanced Linux) 🤪

***
[Magisk] Lughnasadh:
Still working for me on Magisk Beta 21.3. Previously I had installed through the Magisk Repo and when Beta 21.2 came out it broke it. I uninstalled that V4A version and reinstalled by just installing the apk (2.7.2.1) and it worked and is still working with 21.3. I also had JamesDSP, AML, and ACP installed prior to reinstalling the 2.7.2.1 apk.

Using Pixel 4 XL, stock Android 11 (January update).
[Magisk] Zeuszoos:
Hi,

I have Googled it and searched more, but I cannot find any definition of it and I'm wanting to apply the available update, but I don't know if I should check the following box or not during the update process:

"Preserve AVB 2.0/dm-verity checked"

What is that? What does it actually do?

Thanks!
[Magisk] lekiaM:
Can we downgrade magisk beta to stable? Without issues? 🤔
[Magisk] zgfg:
If you have your img patched by older version you can flash that older patched img and voila

If you swithch Update channel from Beta to Stable, you don't gain anything since both are now on v21.3

You probably want to go back v20.4 but I would not recommend flashing it over v21.x

In that case you should start with Magisk not installed and then do clean install of v20.4
[Magisk] lekiaM:
Thanks for your detailed explanation, i will not mess with V21.3👍🏻
[Magisk] IlyaKol:
For anyone Googling...

P5 here that was 'converted' to a P3a via MagiskHide Props Config. I then had to download safetynet-fix-v1.1.1 and hardwareoff_1.1 and install both of them to get tests to pass and GPay to start working again.

EDIT: I am on Jan. update with Magisk 2f5331ab (21301 and Manager 8.0.6 (4828) installed according to the manager.
[Magisk] thomas140:
I heard about safetynet fix, but not hardwareoff module. Do you have the link? Because I have some app like ocbc bank Singapore and some Singapore government apps still able to detect the root even thought it is CTS profile true.
[Magisk] zgfg:
[/QUOTE]

If you search in this thread you will find hardwareoff. It was developed by displax and later incorporated to MHPC as Force Basic (now removed from MHPC)

But guys, you can use MHPC, Edit custom prop and set ro.product.model to whatever value you want (that is essentially what hardwarwoff was doing) - but that fakes your phone model to something else and don't expect it would help to your banking app

If you already pass SafetyNet but banking app detects root, do your homework, go to Magisk Github, open Wiki, find and read the whole chapter about apps detecting root with hints how you can try to prevent

But that is the cat and mice game, there will be always a new app using a new trick detecting (or just guessing) the root
[Magisk] :
IF ANY ONE IS HAVING ISSUES WITH BANKING OR PAYPAL ETC APPS

Uninstall Bromite webview

Uninstall System Webview Switcher

In Magisk.

Install original system webview on Google Play

If you are still having problems, clone the app to skip native libaries & Hide root with

App Cloner - Official Home Page

Welcome to the official home page of App Cloner. App Cloner lets you create & install multiple copies of Android apps. App Cloner safeguards your privacy and identity when using mobile apps. App Cloner is the only multi-account app that creates true, independent, installable clones. Follow...

appcloner.app
[Magisk] pndwal:
The bleeding edge is moving fast! ...

Latest Canary:

5hrs ago

Magisk (f5c2d724) (21302)

- Add more details in logs

Magisk Manager (f5c2d724) (4829)

- Fix version string

1 HR ago

Magisk (b5b62e03) (21303)

- Fix magiskhide ls broken pipe issue

Magisk Manager (b5b62e03) (4831)

- Fix copySepolicyRules logic error

Anyone keeping up? 😃 PW
[Magisk] pndwal:
... But working on the bleeding edge... That might exact sweat, blood and tears!

---------------------------

Pinned Tweet

John Wu, 18h

New update: Magisk v21.3, along with Magisk Manager v8.0.6, directly to the stable channel! This release adds a workaround for a F2FS Linux kernel bug that caused widespread bootloops on many devices

John Wu, 7h

Android's fragmentation is getting on my nerves. ALL THE FREAKING TIME everything is working for me, and OF COURSE there is devices out there with features broken. ALWAYS. And sometimes just like the F2FS bug, it's not even my problem.

Seriously burnt out now, lost motivation

And these issues NEVER came to me before I release to the stable channel, as if beta and canary channels are a *@#£&;* joke

John Wu, 6h

PSA: EdXposed is removed from Magisk Repo due to consistent poor maintenance quality. The maintainer refuse to accept advices, and the one on the repo does not even work with the latest Riru version.

One day, one day I will bring back java code injection strong...

I will close down any issues reported to Magisk if you are using EdXposed. There are just too many issues, and if you chose to go that route, you are on your own. Don't expect me to spend time fixing some broken modules.

--------------------------

But we do appreciate your sacrifices John, and feel for you... Not sure about those bleedin' EdXposed modders though... (spare a thought). PW
[Magisk] zgfg:
Nice to have all those new versions but starting with Canary 21202 (hence present also in Stable 21.3), besides that I cannot use Viper4Android anymore, people from varios phones (me also) report never-ending Vanced YT installation issue

One can say, problems are not in Magisk, who cares, fix on the other sides but for the matter of fact, neither V4A nor Vanced changed - issues started with Magisk upgrades

Now I also jumped to the bandwagon of those reverting Magisk to have properly A11, V4A and YT Vanced, and ignoring all the shiny Magisk upgrades - don't change if it ain't broken
[Magisk] Didgeridoohan:
But if everyone just reverts to old Magisk releases, how will @topjohnwu receive the information needed for a possible fix?
[Magisk] Shished:
How can i convert random apk into system app with latest version of magisk and A11?
[Magisk] akxak:
Being on 21.2 and after getting the notification of Magisk 21.3 release, I tried to install it via Magisk Manager 8.0.6, which I updated this morning.

Tapping the update button, I selected "direct install (recommended)".

After confirming, Magisk Manager downloads 21.3 but stops in the screen "Download completed" and nothing more happens. There is no file in the designated download directory (in opposite to the "download only zip" option.

Any hints or more information necessary? I yet wait so I can dig out further information.

Later... when I try to install 21.3 manually, (first download, then install by selecting the file) MagiskManager reports "unsupported/unknown boot image format" and the installation fails.

- Device platform: arm64-v8a
- Magisk Manager: 8.0.6 (4826)
- Install target: 21.3 (21300)
- Copying image to cache
2026+0 records in
2026+0 records out
2074624 bytes (2.0MB) copied, 0.016579 seconds, 119.3MB/s
1381+1 records in
1381+1 records out
1415016 bytes (1.3MB) copied, 0.014024 seconds, 96.2MB/s
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.Q3AHqaD.X6Ko24Rr/install/boot.img]
! Unsupported/Unknown image format
! Installation failed
[Magisk] vfool:
Hello, i had an older version of magisk and yesterday did the upgrade to latest, after that with adguard on there are no internet connections. The internet gets back only if i disable adguard. Before the magisk upgrade was all ok.

Is there an explanation ?
[Magisk] pndwal:
... Don't know if I can keep up either!

Canary Updates:

3 hrs ago

Magisk (1f4c595c) (21304)

- Revert su -c to old behavior. Should fix a few root apps

2 hrs ago

Magisk (79140c76) (21305)

- Proper xxread and xwrite implementation

PW
[Magisk] asripath:
Looks like HE is in the ZONE

Let it flow...

maybe we can get lucky and

find a fix for the current safetynet woes.
[Magisk] asripath:
V4A and YTV did change to adopt to A11.

Aren't this A11 adoption issues ?

V4A and YTV do work with workarounds.

YTV with non-root installs &

V4A with non-root driver install and apk install such as

https://xdaforums.com/t/app-all-root-solutions-6-0-viper4android-fx-2-7.3774651/post-84229083
[Magisk] tqwzUX6fn39GZMEzSnDF:
How to delete that in Magisk?
[Magisk] KB!:
Just posting this here to try and help.

I have a Samsung S9+ G9650 rooted and running @Krog18 Note ROM.

I updated to Magisk 21.3 and my (root) Button Mapper app stopped working. I use it to turn the flashlight on and take screen shots.

I had to flash an older version of Magisk (20.4) to get the app to work again.

Not sure what the issue is, just wanted to post this here hoping it helps.
[Magisk] pndwal:
Yes, seems to be. Glad he's young and dedicated.

Hope he's not really zoning out though... I think he's just tired, but he does seem to feel let down by lack of constructive help.

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84305757

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84191513

This will be helping for sure:

Initial commit here:

https://github.com/topjohnwu/Magisk/commit/18340099b75b195a1fc375bf926bff785a7a18bf

I won't pretend to understand this CI (Continuous Integration) process, except that:

https://docs.gitlab.com/ee/ci/README.html

... but clearly John can use any help he can get, both from human coders and from automated processing.

BTW, what SafetyNet woes are you having? PW
[Magisk] Dante63:
I just updated my Samsung Galaxy Note 20 Ultra to 2021.1.16 Magisk v21.3 using direct install method...

Camera app no longer function, I thought it's hardware but it wasn't because all other apps can use the camera, could magisk be interfering with Samsung Camera App...?
[Magisk] pndwal:
Just wondering, are you using MHPC, USNF or other Magisk modules? PW
[Magisk] ecksdeeay:
I found a reinstall of the app with functional root bugs fixed issues and regranting ROOT
[Magisk] Dante63:
That's what I have, I appreciate if you can help me make it work again, I removed the camera app then installed it from Samsung store, I have the latest camera app:

I can't run camera app but I can access settings...

I'm also getting error for nearby service crashing...

All that happened after magisk update, what do I do...?
[Magisk] KB!:
Yes, I tried Uninstalling, clearing cache and data and reinstalling. No change.

Rolling back to Magisk 20.4 fixed the issue.

I was on Magisk 21.2 and the button mapper worked most of the time but it would stop from time to time and a reboot would make it start working again.
[Magisk] fubo73:
Magisk 21.4 released to fix root access from some app.
[Magisk] ironLink21:
Speaking of Magisk 21.4 I updated this morning and it looks like CTS is failing? I tried a few apps that usually fail with CTS like pokemon go and they start right up? I'm wondering if this is a false negative or something.
[Magisk] hayvan96:
Hi, I've upgraded Magisk to latest and it restarted automatically, now it doesn't go further than fastboot. I've adb flashed magisk uninstaller (Oneplus 6, Lineage OS 17), but it doesn't fix. Am I also supposed to flash boot.img, if so, where can I find It?
[Magisk] fubo73:
CTS is failing since a while, it was failing with 20.4. Check here
[Magisk] ironLink21:
The boot.img can be found from your ROM provider. Some providers add it into their zips some don't. You'll have to look at your specific ROM to be sure (I don't use Lineage so I can't tell you specifically) if your ROM provider doesn't have it in the zip then the easier way to go is to install the stock ROM for the phone and run Magisk on it. Magisk will create a copy of your boot.img and store that on the sdcard as well as a patched version of the boot.img that you can flash in recovery. Hope that helps
[Magisk] fubo73:
You must extract from full image that you are using or check in a backup folder of Magisk (I don't remember which one)
[Magisk] ironLink21:
Mine was passing on 21.3 though... Maybe it was an anomaly haha. I rooted with 21.2 (canary) it was passing. Upgraded via Magisk manager to 21.3 and it was passing. Upgraded again via the same way to 21.4 and it stopped passing so not sure what's up HAHA if it hasn't been passing.

Also your link just 404's
[Magisk] BrimoFan123:
I was using Magisk versions 19.1, 19.2, 20.4 patching ramdisk.img for my Huawei Mate 10 with LineageOS.

Always the result of patching was that the size of ramdisk.ing was shrinked from 16384 KB to around 8500 KB and the OS rooted successfully.

With Magisk versions 21.2 and 21.4 (21.3 not checked) result of patching ramdisk.img is unsuccessfull - size 16384 KB remain the same and flashing this patched ramdisk cause root is lost.
[Magisk] ndd53:
I don't think I've seen this issue yet: on my pixel 3XL, I tried installing manager 8.05, and got into a loop where I'm continually prompted to install the manager. this is happening for 8.05, 8.06, 8.07 and canary. if I start at 8.05, I can update to 8.07 but then the manager keeps prompting me to install 8.07. I tried reloading the system (without using the '-w' option), but that didn't help.
[Magisk] fubo73:
Fixed, thanks.
[Magisk] ironLink21:
Awesome! Thank you for providing that link I'll have to try that sometime this weekend. Thank you!
[Magisk] J.Michael:
dammit, it's not "12", it's "21", like your name
[Magisk] J.Michael:
How old is "older"?

Is "adguard" a Magisk module?

Module format changes over time, you might need to find a newer copy.
[Magisk] vfool:
I couple years old maybe, also adguard is the program from the com website not the module.

I have uninstalled latest and reinstalled 20.3 and everything is back to normal.
[Magisk] ironLink21:
Wow haha my dyslexia was sure shining with those posted wasn't it haha... Fixed haha thanks
[Magisk] KB!:
I just updated to 21.4 and everything appears to be functioning correctly now.

Thanks.
[Magisk] lekiaM:
Same here!
[Magisk] hayvan96:
I've tried some of the boot.img backedup by Magisk, and (of course), the latest one, which was backup from my latest LOS update, allowed me to reboot. Magisk being broken, I've then flashed latest LOS, gapps and 21.4 for Magisk, and all is back, working, without any data loss :)