yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Yep.

With 22100 App Installed and 22103 Magisk Installed, Direct Install successfuly flashes / boots to 22100 (downgrades).

Just confirmed same behaviour patching prepatched 22103 w/ 22100.

Log:

Device platform: arm64-v8a

- Installing: 22.1 (22100)

- Copying image to cache

- Unpacking boot image

- Checking ramdisk status

- Magisk patched boot image detected

- Patching ramdisk

- Repacking boot image

****************************

Output file is written to

/storage/emulated/0/Download/magisk_patched-22100_2gXYx.img

****************************

- All done!

While Magisk App downgrade requires un-installation of newer app before installing a previous version on many devices (this may well depend on OS configuration), a Magisk Mask downgrade to a previous version can be done (patched) over an image prepatched with a newer version without issues.

Whatever is shown for App Installed will be flashed as Magisk Mask since first single-package version, 21402.*

Further, it seems the only basic prerequisite for Direct Installation is having root. (Nb. Some have even been able to gain full root privileges with Bootloader locked using Direct Install to update, after first gaining partial / temporary root through an exploit!)

* Nb. Post stand-alone builds (21402+), the update Channel NO LONGER determines Magisk Mask to flash. This is now set by App version installed.

Update Channel now only affects the App version shown as Latest (more specifically, Latest for selected channel), ie. App version to be installed if App Install (or Update) is selected.

Nb. Since Update Channel for public builds is set to Beta by default (only occurs if App is freshly insalled, not updated) users will see Stable build updates (Beta Channel points to Stable builds except where Beta is a later version) AS WELL as Updates to new Beta builds UNLESS channel is changed from default. - I'm guessing that in this event, many public Stable build users WON'T REALISE that they are actually updating to a Beta build.

This may all seem confusing / counterintuitive, especially for long time Magisk users, and there may well be better ways of implementing the new single-package builds. However, it ain't broke, and all works fine as described above.

Understanding the new single-package setup will hopefully allay confusion. 😬 PW
[Magisk] Didgeridoohan:
In most cases... I've also seen it go horribly wrong (although, that was a while ago now).
[Magisk] pndwal:
Oh!

User with query in this case was simply trying to downgrade from current Canary to Stable. (User was stuck attempting App 'downgrade' at that point however).

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

I've done such 'downgrades' several times recently (App, then Magisk Mask) with no issues using phone only (Direct Install method), but only between new single-package builds. Do you recommend avoiding this option?

Aside from issues resulting from failing to unhide Manager in older builds, what has gone wrong? PW
[Magisk] jenslody:
In many (most) roms you can not easily downgrade an app (only debug apps, if you force the downgrade, if I remember correctly).

But it can be safe to uninstall the app and reinstall a lower version, without lossing major stuf, just themeing and time-out, but not stuff stored in the database (as you surely know, but probably not all users).

It might fail if the version of the app is no longer compatible with the actual version of Magisk itself, this might happen if the downgraded app-version is too old.
[Magisk] pndwal:
Sure, as I said originally.

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

In post you cited, I observed that users query was originally regarding why he gets 'app not installed' moving from recent Canary Magisk App to Stable... but we were by then discussing using Direct Install method to flash Stable Magisk Mask with later Canary version installed, which is essentially a downgrade too (eg. patching 22100 Magisk to boot image already patched with 22103).

This is a totally different animal however! 🙂 PW
[Magisk] Didgeridoohan:
Like I said, in most cases there are no issues. And when I say "horribly wrong", I just mean that the downgrade failed and that I needed to restore a stock boot image/uninstall Magisk and start fresh, nothing major. For the inexperienced user it could mean a bit of a panic though and may result in them doing a full reset of the device and losing a bunch of data...

But, as also noted, it was a while since I've had that happen. I usually do test a lot and that of course raises the risk of things going wrong.

Generally it's pretty low risk to downgrade, especially if the releases are pretty close version-vise, but things can always go belly up when you least expect it. Backup, backup, backup...
[Magisk] Swamphound:
I can confirm webview manager module as being an issue. In Magisk Canary passing Safetynet but PayPal, Venmo, Chase, Synovus apps not working until I uninstalled the Webview Manager module by Androidacy. Without it all are working fine.
[Magisk] oz42:
Which version of Magisk for Android 10 was the last one with working Magisk Hide?

I have to ask because currently reporting bugs about Magisk Hide are being ignored. That's fine, this is a project that needs a lot of work and that is free for all of us.
[Magisk] HippoMan:
The latest official stable version is 22.1 (i.e., 22100). I'm using that successfully with Magisk Hide under Android 10. There is also a "canary" version: 22103. I assume that it also runs with Magisk Hide under Android 10, although I haven't tried it yet.
[Magisk] oz42:
My problem is:

SafetyNet failure and

there is no hide menu where I can tell which apps should be prevented to check for rooted devices. There is just one switch to enable/disable the hide function.
[Magisk] zgfg:
I understand that there are issues and that you may have problems with Magisk Hide but for the general way you ask I can answer the same way: For me, for my A11, the latest Canary 22103 works fine, incl. the Magisk Hide

Hence, something is missing in the question. Probably, at least, the particular phone and/or ROM and which Magisk hide issues

Brw, that's the main reason of issues: just imagine how many vendors, models, Android versions, stock and custom ROMs are in the use. Most of the issues are platform specific - reported by one or some, not reproducible for the most of the others
[Magisk] zgfg:
If SafetyNet fails with API error, that has been discussed in many posts the last days here, the cure is simple, install the latest Canary 22103 (or wait until it will be fixed in the upcoming new Stable relesse)

Magisk Hide can be turned on or off in the Settings, but there is separately a tab where you can select for which package and process it has to be enabled.

You can also use magiskhide command from terminal apps.

See the screenshots and read from the Magisk guides available from Github
[Magisk] oz42:
Thank you for your help! In fact, I am just installing LOS 18.1 on my Moto X4 payton with the latest stable Magisk. With LOS 17.1 and an older Magisk release, even Google Pay was working just fine.
[Magisk] mariodantas:
Hi Magisk fellows

I tried to patch the boot from an uis7862 TOPWAY platform (TS10) and I got the following results in log, I wonder if the image is properly rooted as I have "operation not permited" messages at the end of the log (see below)

Can anyone help me ?

- Device platform: arm64-v8a
- Installing: 22.1 (22100)
- Copying image to cache
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER [2]
KERNEL_SZ [17088524]
RAMDISK_SZ [779984]
SECOND_SZ [0]
RECOV_DTBO_SZ [0]
DTB_SZ [161521]
OS_VERSION [10.0.0]
OS_PATCH_LEVEL [2020-02]
PAGESIZE [2048]
NAME []
CMDLINE [console=ttyS1,115200n8 buildvariant=user]
CHECKSUM [c6a6e9730b232b3a64ea7d525ebaef1652164527000000000000000000000000]
- Unpacking boot image
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
VBMETA
- Checking ramdisk status
Loading cpio: [ramdisk.cpio]
- Stock boot image detected
- Patching ramdisk
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Create directory [overlay.d] (0750)
Create directory [overlay.d/sbin] (0750)
Add entry [overlay.d/sbin/magisk32.xz] (0644)
Add entry [overlay.d/sbin/magisk64.xz] (0644)
Patch with flag KEEPVERITY=[true] KEEPFORCEENCRYPT=[false]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [init] -> [.backup/init]
Record new entry: [overlay.d] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin/magisk32.xz] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin/magisk64.xz] -> [.backup/.rmlist]
Create directory [.backup] (0000)
Add entry [.backup/.magisk] (0000)
Dump cpio: [ramdisk.cpio]
Loading dtbs from [dtb]
Patch @ 00D2DB4C [736B69705F696E697472616D667300] -> [77616E745F696E697472616D667300]
- Repacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER [2]
KERNEL_SZ [17088524]
RAMDISK_SZ [779984]
SECOND_SZ [0]
RECOV_DTBO_SZ [0]
DTB_SZ [161521]
OS_VERSION [10.0.0]
OS_PATCH_LEVEL [2020-02]
PAGESIZE [2048]
NAME []
CMDLINE [console=ttyS1,115200n8 buildvariant=user]
CHECKSUM [c6a6e9730b232b3a64ea7d525ebaef1652164527000000000000000000000000]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
VBMETA
Repack to boot image: [new-boot.img]
HEADER_VER [2]
KERNEL_SZ [17088524]
RAMDISK_SZ [1089074]
SECOND_SZ [0]
RECOV_DTBO_SZ [0]
DTB_SZ [161521]
OS_VERSION [10.0.0]
OS_PATCH_LEVEL [2020-02]
PAGESIZE [2048]
NAME []
CMDLINE [console=ttyS1,115200n8 buildvariant=user]
CHECKSUM [38545adff81bd5131bce69d23a153b42a1ebb743000000000000000000000000]

****************************
Output file is written to
/storage/emulated/0/Download/magisk_patched-22100_qFyMC.img
****************************
cp: can't preserve ownership of 'busybox': Operation not permitted
cp: can't preserve ownership of 'magisk32': Operation not permitted
cp: can't preserve ownership of 'magisk64': Operation not permitted
cp: can't preserve ownership of 'magiskboot': Operation not permitted
cp: can't preserve ownership of 'magiskinit': Operation not permitted
- All done!

I'd like to heare from you before attempt to flash that boot image into my headunit

Cheers
[Magisk] pndwal:
You haven't hidden root from Chrome in MagiskHide list by any chance? (Or uninstalled Chrome?)

https://github.com/topjohnwu/Magisk/issues/595#issuecomment-420302656

www.twitter.com/topjohnwu/status/1039528958289760256

GENERAL RULE

Don't put more processes / apps in Hide List than needed

More on timing issues here also:

https://xdaforums.com/t/magisk-the-magic-mask-for-android.3473445/post-70363391

Also, check that Developer options, WebView Implementation shows Android System WebView. 👍 PW
[Magisk] pndwal:
Click 'Shield' icon on floating menu at bottom of screen, click MagiskHide at top. 👍 PW
[Magisk] pndwal:
Sure... Me when I first encountered 'System has been Destroyed'. 😳

Since understanding that this DOESN'T mean system partition, at least for Magisk flashing purposes, I now read 'Oh... boot image (or recovery image) got corrupted again... gotta reflash image file... again... sigh...' 😐

I concur

Sage advice... Cannot be overstated... PW
[Magisk] oz42:
Since now I have ignored the floating menu because usually it contains that "follow me on Twitter/Facebook/whatever" spam. A mental blind spot so to say. I had expected to see all settings in the settings menu.
[Magisk] pndwal:
If you mean Support Us menu it's not spam. Since John stopped commenting here, his Twitter is the only real way to keep up with comments on Magisk progress, and official documents / files are all on his GitHub - OctoPuss (cat) icon - ! Other 2 are for contributions if you wish.

But floating menu is different; Home, Shield (SuperUser / MagiskHide List), Bug (Logs), Puzzle piece (Modules) icons. 😉 PW
[Magisk] zgfg:
There is a separate button for Twitter 😁

But there is also a buttun for Github - don't ignore that one either because the Guides, Issues reporting, everything is there (not really here in this thread)
[Magisk] lhooipg:
Dear all,

I am new to this magisk thingy and have follow every single step to install it. I am unable to move forward due to it say the Magisk installed status is N/A. I've tried all the method that can find on the internet but still not working.

May I know how can I solve it and enjoy the Hide feature?

Btw, I am running android 6.0.1 on Samsung Galaxy Note 4 (SM-N910C).

Thank you.

Jeffrey
[Magisk] ChokingHazard91:
I know that it should work but after installing Xposed I end up in a bootloop, just like other people with a Note 4. Seems like the alt-version of Xposed and suhide don't work together. Also installing 86.2 alt and suhide ends up in a bootloop.
[Magisk] Sillik:
I confirm. Note 4 needs the "alt" version of Xposed, which doesn't work together with suhide.

EDIT: Apparently it is possible to get suhide and xposed working on Note 4, but without Magisk:

http://xdaforums.com/showpost.php?p=69074359&postcount=1975

Gonna try that tomorrow probably as I don't have the time today...
[Magisk] ChokingHazard91:
Thank you, I will try this later today.
[Magisk] KaMonsieur:
How to set SElinux to permissive in Magisk Manager 2.0?
[Magisk] Captain_Throwback:
You don't.
[Magisk] KaMonsieur:
But there was a toggle in older version of it? :confused:
[Magisk] Turbopuschel:
Unfortunately I don't get how to install and try out Magiskhide from Github. I tried installing the Magisk_master.zip in TWRP, didn't work because of no META-INF folder, according to the error message.

How can I try Magiskhide?
[Magisk] Captain_Throwback:
And now there isn't anymore. There also isn't a root toggle anymore.
[Magisk] Captain_Throwback:
If you don't know how to try it out, then you'll just have to wait.
[Magisk] KaMonsieur:
All right. Thank you.
[Magisk] Drefsab:
I saw that the root management was removed because you state that SuperSU and PHH have superior solutions, though trying SuHide 0.55 I've found that it doesnt hide from sky go but on v6 of Magisk it works fine. I've had to dig out urls for old apps and go back to them as your root toggle option is the only one that works for some apps.
[Magisk] Captain_Throwback:
What is the app you're referring to? I haven't found an app that suhide isn't working for. There may be something else going on with your device.
[Magisk] andrew2432:
Yup, 5.0, root toggle, how could in be any easier!!

Flashfire, a few system app movers, and some other things aren't compatible with magiskv6.
[Magisk] Drefsab:
Ask mentioned in my post the app is the Sky Go app, (https://play.google.com/store/apps/details?id=com.bskyb.skygo&hl=en_GB). This basically lets you watch any satilite tv channel you have a subscription for on your device. I installed the suhide setup the gui and set it to hide for the sky go app, restarted then loaded up the app. When I tried to watch content I got the lovely "sky go is not supported on rooted devices" message.

I tried phh's testing hide su an that also was detected, however using magisk v6 and use the root toggle it works fine. Don't get me wrong id love to get this working with the newer packages and have things like safetynet pass but the 1 app I really want to do this for is sky go the reas is just a would be nice to have.

---------- Post added at 03:59 PM ---------- Previous post was at 03:56 PM ----------

im using it on android 7 on my device, currently it works great where everything else to hide root from Sky Go doesnt work. Safetynet does fail but im not using android pay or any banking apps etc.
[Magisk] andrew2432:
Umm...it says not available in my country but neither are some other apps...should I disable location, perhaps make my location elsewhere before running? Obviously toggle root off. The game in question fails to authenticate my smg900p after unsu, magiskv7, phh255, no such hide for 5.0. But this TV app needs to work!!!
[Magisk] Drefsab:
Its only available in the UK to Sky TV customers, bascially its a value added service for customers to watch their content where ever they are. Its really good to be able to watch stuff on the move and keep the kids entertained but I use root for other apps I use so I have always been looking for an easy way to use this. Magisk v6's root toggle is the only thing that worked.
[Magisk] Mew:
Unicon doesn't work with Magisk v7

It worked previously with Magisk v6?

Any workarounds?

Says "No root detected" or something
[Magisk] Captain_Throwback:
Magisk doesn't provide root, so your issue isn't with Magisk :confused:.
[Magisk] Mew:
But I thought that's the root of the problem? (no pun intended)

It worked on Magisk v6 but not v7 which is why I'm confused.
[Magisk] Captain_Throwback:
Install a root method.
[Magisk] oz42:
What happens when you tap install?
[Magisk] pndwal:
Don't start with other docs, please read official Installation Instruction carefully, then ask here if anything is unclear or doesn't work.

Official Installation Instruction is accessed from Magisk main page on John Wu's GitHub (under Useful Links), where, I hope, you downloaded Magisk App.

From Magisk App, just click GitHub OctoPuss (cat) symbol on home screen.

If you have compatable TWRP (custom Recovery) for your device, you can follow Custom Recovery section (Nb. Magisk in Recovery is something different altogether, and won't apply to your 'legacy' device).

Otherwise, familiarise yourself with Patching Images section before proceeding. Nb. Depending on how your Sammy ROM package archives boot image, some of the information for newer SAR devices in Samsung section may be useful for you if using Patching method.

Read, read, read. Then proceed! 👍 PW

Edit: Seems from this:

https://xdaforums.com/t/magisk-22-n...0f-touchwiz-armeabi-v7a.4253113/post-84870675

that you may have actually tried flashing 22100 using TWRP... but it's not clear.

You really need to say what you have tried.

If you did flash (aside from installing App), did you have a previous version? Direct Update within App?

Please give us a clue if you are still facing issues. 🙂 PW
[Magisk] pndwal:
Latest Debug (Canary)

Changelog and Release Notes

https://github.com/topjohnwu/magisk-files/blob/56d4ca44e12927217ae761df0874e3cd7d05cea4/notes.md :

Magisk (fb8000b5) (22104)​

[App] Hide annoying errors in logs when hidden as stub

[App] Update stub implementation

[App] Some internal code refactoring

[App] Update snet extension implementation

Diffs to v22.1​

[App] Update snet extension. This fixes SafetyNet API errors.

[App] Fix a bug in the stub app that causes APK installation to fail

[App] Hide annoying errors in logs when hidden as stub

[General] Remove all pre Android 5.0 support

[MagiskPolicy] Remove unnecessary sepolicy rules

[General] Fix a C++ bug that causes undefined behavior

[MagiskHide] Update package and process name validation logic

May fix sundry issues with Magisk App! 👍 PW
[Magisk] maniacbb:
Hey could anyone tell me where i can find a trust file that i can remove Magisk via TWRP? I find some files in internet but not i official site. Could someone can help me?
[Magisk] Austinredstoner:
U can remove magisk directly in magisk itself

First open magisk app

Than click on uninstall magisk button in magisk app

Reboot than magisk is successfully uninstalled
[Magisk] ipdev:
Rename the Magisk APK file to uninstall.zip and flash it in TWRP.

From the official instuctions.

Magisk Installation - github.io - Uninstallation - Link

Personal Note:

You may also need to manually flash your rom's stock boot image.

Cheers. :cowboy:
[Magisk] lhooipg:
Hi, Thank you very much for the replied. Please refer to the this here for my feedback:

https://xdaforums.com/t/magisk-22-n...f-touchwiz-armeabi-v7a.4253113/#post-84870675

Do let me know where is more appropriate to post my issue so that I won't be consider spamming the forum...tqvm for the help.
[Magisk] pndwal:
Hi. It's fine to post here - this is Magisk General Support / Discussion after all! 🙂

Updates there are clear however.

Yes, Latest 2 Canary builds have fix for Magisk SafetyNet check error, which is not actually indicating a failed result, only an evaluation failure. SafetyNet is actually still passing if PlayStore Settings shows PlayProtect Device is certified result. (Read recent posts here.)

Question: When updating to 22.1 App, did you have Manager hidden? Unhiding is critical due to incompatibility between old Manager and new App, as per release notes.

If you didn't do this, you likely have two conflicting Magisk apps installed. 😬 PW
[Magisk] lhooipg:
Hi,

Question: When updating to 22.1 App, did you have Manager hidden? Unhiding is critical due to incompatibility between old Manager and new App, as per release notes.

Answer: No, I did not hide the Manager when updating to 22.1 App. After the updated and patched the app-debug.apk (Canary) then got the Installed: N/A.

Thank you.
[Magisk] lekiaM:
how to to use the extension snet.jar guys? to pass safetynet properly?
[Magisk] pndwal:
Install latest debug Canary Magisk (fixed), or wait for next public Stable / Beta.

Nb. Magisk (at least w/ Universal SafetyNet Fix module) is still passing SafetyNet fine.

Latest 2 Canary builds have fix for Magisk SafetyNet check error, which is not actually indicating a failed result, only an evaluation failure. SafetyNet is actually still passing if PlayStore Settings shows PlayProtect Device is certified result. (Read recent posts here.) PW
[Magisk] pndwal:
Ok.

There have been a number of issues raised on Magisk GitHub recently, relating to Android 6 (Marshmallow) problems, some closed due to insufficient information...

The OP of the thread you commented in had opened one for your Samsung Galaxy Note 4. It'ss still open:

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

You may wish to help /provide information / logs for your device there also if no-one else here has suggestions.

I think there may well be overlooked regressions in recent builds affecting your device, and likely other older devices also. 😐 PW
[Magisk] lhooipg:
ok, noted with thanks. Will go read through it and because I'm a new user at github I'm not able to post it.
[Magisk] pndwal:
Ah, yes; John has recently been frustrated by issues not following his template / instructions, which waste his valuable time. He recently restricted issues to colaborators only, then opened again, but apparently with restrictions.

Since the issue was opened by the OP of the XDA thread you commented in, you may be able to help there... 👍

I'm sure this will get needed attention, as that user is persistent. He's opened new issue (bug) reports regarding this at least three times now! PW
[Magisk] wtosta:
Hello.

After installing the latest canary channel Magisk APK, which helped to pass Safety Net check. But unfortunately I have observed the issue that any of banking apps refuse to authorize using the biometric fingerprint sensor, only the password. Have anyone noticed such strange behavior?

Best regards.

Witek
[Magisk] pndwal:
Is that a Samsung device? Universal SafetyNet fix installed? If so:

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

Otherwise, please give some details / clues! PW
[Magisk] wtosta:
Yes, I use Samsung S9 device indeed. I must have somehow missed thread about biometric issue. Thank you. I installed the mentioned Safety Net fix 2.0 test4, and biometric authorization began to work on the banking apps again. But Safety Net check in the Magisk app has changed from working basic evaltype into hardware, which doesn't work on rooted devices. Probably I have to wait until developers will be able to deal with all current problems.

Best regards,

Witek
[Magisk] dope77:
is there a guide on github about rooting emulators? (like bluestacks...)
[Magisk] saiki47:
When I updated the magisk app to 22.1, safetynet basic integrity and cts both are false now. Earlier with 22.0, it worked with magisk hide props config with universal safetynet fix. What to do now?
[Magisk] zgfg:
API error? (If yes, did you follow the previous conversation about the need to install Canary 22104 or to test with a third party SN checker)