yashsingh1/xdaforums huggingface dataset:
[Magisk] J.Michael:
I have never enabled MagiskHide. I find I have an option enabled "Hide Magisk from various things" (under gear-wheel on main screen).

From shield-icon I get a MagiskHide button, it takes me to what looks like a list of all apps on my tablet. Each app has a right-pointing-arrow, no sign that any app has been "chosen". I followed the arrow on a few: Peacock seemed to have been selected, the next six had not; I stopped checking.

I am think I am running Magisk and Manager 20.3, refusing update to 22.1. (It was Canary when I downloaded it.)
[Magisk] zgfg:
If you never enabled MagiskHide, you could not pass SafetyNet

I don't think that Peacock should be chosen by defaul

But I was asking if you click on Google Play Services to expand all its activities, which of them are chosen by default - my screenshot in the previous post, I think I have one activity too many enabled (that is not neccessary) but I don't remember which one (once I played with them and didn't properly 'restore')
[Magisk] martyfender:
com.google.android.gms.unstable is normally the only one checked by default under Google Play Services in MagiskHide.
[Magisk] zgfg:
Thanks - but for the matter of fact (i e., I didn't expect) even without the whole Google Play Services it still passes SafetyNet for me
[Magisk] pndwal:
I've only ever seen the one process enabled by default: com.google.android.gms.unstable, which is Safety Net process. And I've only seen that one mentioned. Please see second link from here:

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

Also, this:

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

🙂 PW
[Magisk] zgfg:
Thanks. @martyfender also replied.

But regarding to SafetyNet, see my answer to him (right above your post) - ?!
[Magisk] pndwal:
Are you sure you disabled SN (com.google.android.gms.unstable) process?

Even with Google Play Services checkbox empty, process is still selected. It only happens this way for this one process, presumably because it is not manually selected. Indication is partial blue line that still appears for process. All processes are cleared if Google Play Services is checked, then unchecked, and no partial blue line remains.

For me, if all processes are removed, SN fail is immediate.

Also, Google Play Services is completely removed from MagiskHide list on closing / reopening. Unchecked Google Play Services is re-added to list ONLY after toggling off / on MagiskHide in settings (no reboot etc needed), again with SN process (only) selected. PW
[Magisk] zgfg:
I have completely removed Google Play Services (I left only two other apps but they have nothing with GPS)

- see the screenshot
[Magisk] Lvsitano:
That did work, after changing the Magisk app name, Ikea app stopped complaining. So they are detecting Magisk app.
[Magisk] pndwal:
Interesting. Mileage must vary. I just tried it, and SN fail was immediate on RN8T. PW
[Magisk] pndwal:
What happens if you disable all?... I wonder if MIUI process is affecting things? PW
[Magisk] zgfg:
I didn't try by removing all

But something else is interesting:

- I remove Google Play Services, exit Magisk app, re-enter and GPS is still disabled but SN passes

- I reboot and open Magisk, but GPS is now (auto) enabled again in Magisk, and with two (!) services:

com.google.android.gms

com.google.android.gms.unstable

Hence I'm not sure if GPS is really disabled when I remove it from the list but leave the MagiskHide option enabled
[Magisk] DiamondJohn:
The other option over using Magisk Hide, is to freeze & Hide an app.

Your post is confusing, as there are two of them, and, in a way upi are contradicting yourself. You say "I removed every module and I still get the lag unfortunately", but then list all the apps yu have hidden with Magisk. I understand that these two events/tests are most probably seperated by ti9me, but the post is unclear.

If you have lag after removing pdules, then, it sounds like Magisk is not the issue. Have you tried uninstalling Magisk itself, to check the lag? If its still there, then its obviously not Magisk, and you have another issue to investigate that will only be confused by looking into Magisk.
[Magisk] pndwal:
Some context:

He was actually answering my questions, and I'd asked about two unrelated possible causes of issue; modules - not apps - (incl. Systemless hosts), and hide list population. So the answers were unrelated.

I since asked about his OTA process also, as seems he may not have restored stock images to take update, so issue could relate to that. Yet to confirm.

Answer seems to eliminate first possible cause. I think the second, too many or inappropriate processes hidden from root, is a likely culprit as discussed, but he hasn't confirmed any test for this either as yet. 🙂 PW
[Magisk] pndwal:
I guess you're meaning root hidden from a GPS process (hide) is disabled (as opposed to a GPS process's access to root (unhide) is disabled).

I just rebooted after manually hiding / unhiding SN process only, and after reboot still only have that one process selected. This is the same after enabling SN normally by toggle off / on and reboot.

As our devices are similar, I'm guessing your MIUI processes (hidden) are likely affecting defaults and SN test results. Also, I think you are on custom MIUI? I'm on stock, so this may (possibly) account for different handling. PW
[Magisk] ipdev:
@pndwal

It has been a few years since I looked into Xiaomi.eu

If I remember correctly, it was kind of an official unofficial rom.

From their forum.

Xiaomi.eu Vs Global Rom Differences - Xiaomi.eu - WebSite - Link

@zgfg

I haven't use an Xiaomi.eu rom in a while.

I thought they included all the work-a-round(s) to pass SafetyNet.

If you turn off MagiskHide and reboot, do you pass SafetyNet ?

I am wondering if they added the SafetyNet fix into the roms?

The eu builds should only fail due to bootloader status.

Cheers. :cowboy:
[Magisk] pndwal:
Not sure it was ever 'official' / officially endorsed, but you may be right... Bootloader cannot be relocked anyway, so FAIAP it's custom.

That seems likely to me too.

... And shouldn't with USNF. It has been added to many custom ROMs. Dev (Danny) provides 2 methods, easy for rom maintainers:

https://github.com/kdrag0n/safetynet-fix#rom-integration

It does appear Xiaomi.EU have done this with latest ROMs, but there are reports of issues. 👍 PW
[Magisk] J.Michael:
I have never tried to pass SafetyNet. I have no interest in SafetyNet. As far as I knew, I had not enabled MagiskHide. I certainly never told Magisk to hide from a particular app. I have no idea why Peacock showed up as selected.

Like I said, I'm using an old version of Magisk and Manager. My display does not look like yours. It does not make it easy to scan to see which apps are selected. The list does not include a flock of Google processes. The only entries with Google in their names are "Google Play Movies & TV" and "Google Play Music"; neither is selected.

A n d I just discovered the "Show system" button. Under "Google Play services" there are nine processes, only com.google.android.gms.unstable is selected.
[Magisk] zgfg:
They included like USNF into the ROM.

To install the ROM, Bootloader must be unlocked.

When ROM is installed but WITHOUT Magisk (before Magisk is installed), there is no root but it passes SafetyNet (although Bootloader is unlocked)

---

My yesterday tests were all with Magisk installed, MagiskHide option enabled, but by removing Google Play Services from the MagiskHide list.

Now I tested what you asked:

1) I turned off MagiskHide option in Magisk app settings.

I exited Magisk app and re-opened Magisk app.

MagiskHide tab was no more available.

I checked by terminal and magiskhide command, it confirmed (screenshot) that MagiskHide was disabled.

Then I checked SafetyNet in Magisk app, and it was still passing?!

I checked by two other SN checkers, and for both SafetyNet was still passing?!

2) Finally I rebooted the phone and SafetyNet was failing then (both Basic Integrity and CTS Profile) in Magisk app and the other two independent SN checkers - as expected (because Magisk was installed but MagiskHide turned off).

Hence I wonder about the results in (1). Although MagiskHide was disabled, it still acted like it was enabled and passed SafetyNet.

Only upon rebooting (2), it failed SN, as expected.

I thought that disabling MagiskHide takes full consequences immediately, not upon rebooting.

Magisk Canary 23001

PS:

Opposite direction:

Eventually, I re-enabled MagiskHide in Magisk app settings, DID NOT reboot, and SN was passing properly again, both in Magisk app and rwo independent SN checkers.

Here, rebooting was not neccessary (as expected)
[Magisk] zgfg:
@pndwal, you asked me to retest by having com.miui.securitycenter removed from the MagiskHide list.

I removed and rebooted (for clean start)

I entered again to my MagiskHide tab and disabled one by one processes for Google Play Services.

There was only Rootbeer Fresh left as enabled for Magisk Hide - screenshot 1.

The same was confirmed in terminal, by magiskhide ls command - screen**** 2

Then I checked and SafetyNet was passing in Magisk app and two independent SN checkers.

I double-checked, still only Rootbeer Fresh was in the Magisk Hide list

I rebooted and checked into the MagiskHide list again, but found the Google Play Services (auto) enabled there, both gms and gms.unstable processes - screenshots 3, 4.

(Of course, SafetyNet was passing)
[Magisk] zgfg:
Tested that scenario, too

Disabled all (user and system) in Magisk Hide list.

Hence MagiskHide option in Settings was still enabled but the list was empty - screenshots 1a, 1b, 1c

Restarted Magisk app and SafetyNet was still passing - double-checked MagiskHide, it was all as above.

SN also passing in two other SN checkers

Rebooted but found then Google Play Services (auto) enabled in MagiskHide list - screenshot 2a
[Magisk] pndwal:
Thanks.

I'd actually added that service to test too, and saw it made no difference.

I'm thinking your ROM may have unique functions. I understand official XiaomiEU is not pre-rooted. Take it you have official build, so shouldn't be pre-root.

Next, thinking that with USNF implementation, solution may check if user has root & if MagiskHide is on or off to handle inbuilt USNF / conflict (and possibly checks / locks MagiskHide on or off itself where root detected) but only on bootup...

This is pure speculation, and may explain SN pass on your device w/ MagiskHide off... but doesn't explain why your extra process is automatically checked... So I'm probably way off!... Does Magisk analyse system to select Google services to add to hide?

Bit of a puzzle! Beats me. 😜 PW
[Magisk] pndwal:
Mmm. Wonder if anyone else has com.google.android.gms auto enabled? PW
[Magisk] unknowndrop:
Does anyone know if snapchat works with magisk?
[Magisk] YLNdroid:
Hello Magisk users, I have a very naive question.

I have installed the latest version of the app on a Samsung Galaxy J5 (2016) SM-J510FN. Since Ramdisk info displays Yes, what image must I patch: boot or recovery?
[Magisk] pndwal:
Boot.

Click 'Octocat' (GitHub) symbol, bottom of home screen, then Installation Instruction under Useful links. 👍 PW
[Magisk] ipdev:
Thank you for checking. 🥳

I do not think turning MagiskHide off reverts the settings/changes.

I have the same issue since about a year (year and a half) ago on my main phone.

Pixel 3aXL, ABC Rom [ ezio84's GitHub manifest ]

Without MagiskHide enabled on boot, the Magisk patched boot image breaks SafetyNet.

It will pass if I enable and then disable MagiskHide after boot.

If I boot the stock (abc) boot image, I pass SafetyNet again.

OK, so this is new.

If you have Magisk renamed, it will prompt you to remove and install the full Magisk app.​

- See attached Screenshots.​

I am guessing it has to do with repacking and signing the boot image? :unsure:

When I have time, I will try to sign the magisk patched boot image with the same key I build abc with.

Cheers. :cowboy:
[Magisk] Barracuda77777:
I know this might be late, who ever built the rom had:

export WITH_SU=true in the .bashrc file.

I had the same issue with lineage 18.1 that I built, I commented the above in my .bashrc file and the warning is gone.
[Magisk] MegaSharkXDA:
Hi guys! Haven't installed Magisk in a couple of years and apparently now the recommended method is patching the boot.img file through the Magisk app.

Device: Samsung Galaxy i9100

Magisk: v22.1

Ramdisk: Yes

SAR: No

ROM: cm-11-20141115-SNAPSHOT-M12-i9100

Boot.img: Extracted from cm-11-20141115-SNAPSHOT-M12-i9100

When attempting to patch the boot.img file I always get an error:

Unsupported/Unknown image format

Installation failed

Any clues?

Thanks in advance!
[Magisk] zgfg:
Boot image means that file "boot.img" must be extracted from the ROM

However, check on Installation instructions on Github (link from the main Magisk window), there is a special section for Samsung (but only the newer Samsung phones)
[Magisk] MegaSharkXDA:
I used the boot.img extracted from the cm-11-20141115-SNAPSHOT-M12-i9100 ROM

This is not a newer Samsung phone and SAR is stated as NO
[Magisk] Didgeridoohan:
@MegaSharkXDA Any particular reason you're using v22.1? For all we know the issue you're seeing might already be fixed with v23...
[Magisk] MegaSharkXDA:
v23 isn't compatible with cm-11-20141115-SNAPSHOT-M12-i9100 (Kit Kat)
[Magisk] zgfg:
Have you tried with v21.4 (and by flashing through TWRP)
[Magisk] MegaSharkXDA:
Will try. Any significant changes from v21.4 onwards?

Any significant risks, since it's not the recommended method?
[Magisk] zgfg:
Patching and flashing became recommended mainly because of various types of the new SAR phones, where for some of them no appropriate TWRP versions were available.

I can use both methods on my phone but I prefer patching because if anything goes wrong (usually it does not although I immediately update Magisk to every new Canary), I can just flash my boot.img patched by the previous Magisk version and I will be back in business (formally, you can do similarly with TWRP but you must make regular back-ups)

And yes, there were substantial changes between Stable v21 4 and v22 (new GUI, Manager became Apk and that was not just a cosmetical change, patching was also supported earlier but it then became the main-stream, etc)

E.g., some users with older Huawei phones (although Oreo, not the very old Kit Kat) claim they cannot update to Magisk v22 or v23 (however, Magisk now explicitly states that Huawei phones are no more supporred)
[Magisk] MegaSharkXDA:
Tried installing Magisk v21.4 through CWM Recovery v6.0.5.1

Got an error:

Unable to repack boot image!

Unmounting partitions

Error in /storage/sdcard0/Magisk-v21.4.zip

(Status 1)

Installation aborted.
[Magisk] Didgeridoohan:
Ouch. Nothing newer available for the device?

Don't think CWM ever has been supported...
[Magisk] MegaSharkXDA:
Interestingly enough, Magisk v17 tells me that Lollipop is required lol. Will try upgrading to Android 6.0

I hate TWRP. But... so be it.
[Magisk] J.Michael:
I thought I had seen a release note saying that Magisk would now only support 5+. But I thought that note was much more recent than 17.
[Magisk] pndwal:
For your reference:

Samsung Galaxy S II I9100 XDA info:

https://xdaforums.com/c/samsung-galaxy-s-ii-i9100.1055/

https://xdaforums.com/f/galaxy-s-ii-android-development.1204/

I see Latest official LOS is 14.1 Android 7.1.2 N.

https://xdaforums.com/t/rom-i9100-official-7-1-2-lineageos-14-1.3555834/

https://lineageosroms.com/i9100/

Nb. I see a special script is needed to get Magisk root. (patches boot.img):

https://xdaforums.com/t/rom-i9100-official-7-1-2-lineageos-14-1.3555834/post-81655467

It does this:

https://xdaforums.com/t/rom-i9100-official-7-1-2-lineageos-14-1.3555834/post-81681141

I didn't see if anyone succeeded with script / Magisk in LOS 14.1. OP says it was first made for LOS 16.0.

In any case, you also have up to date unofficial LOS 18.1 Android 11.0.0 R from same dev!

https://xdaforums.com/t/rom-unofficial-11-0-0-r37-i9100-lineageos-18-1.4199759/

Latest is Build #7 2021-05-17 (too old?)

Included is optional Magisk-patched boot.img!

WOW; Galaxy S II support from Android 2.3.4 (Gingerbread) thru Android 11.0.0 (Red Velvet Cake). 😃 ...

I'd be moving to LOS 18.1 just for kicks! 😁 PW
[Magisk] kirknado18:
Im having a problem flashing magisk to the hp touchpad running evervolv android 9 pie. Twrp keeps giving error 1. Ive tried patched boot img but no boot partition in twrp to flash it too. Touchpad is dual boot with moboot 0.3.8. Web os recovery and twrp recovery only android is currently installed. JScullins toolbox is also flashed to boot. Need a way to flash Magisk to boot. Bootloader is a Sony Elf bootloader. Currently running SuperSu 2.82 Pseudo-Pro and it has limitations would like to flash magisk to it. Is their a way to flash magisk to a dual boot bootloader like moboot cus i sure cant flash Magisk through Flintman Twrp 3.2.1 yet SuperSu flashes with no issues cant understand why magisk doesnt and it doesnt matter whether flash is clean or dirty still gives error 1 or error 7 flash fails. There has been 0 information online as to how to flash magisk to hp touchpad running android. Imgs are ulmage. System is lmv.
[Magisk] pndwal:
Since you have root, do you get Direct Install option in Install menu?

Do you have ADB fastboot access from PC? As you seem to have successfully patched boot image, this would probably be your best bet for flashing it.

Also, this has been tried before. But probably this won't help:

https://github.com/topjohnwu/Magisk/issues/218 PW
[Magisk] kirknado18:
Yes i think so
[Magisk] kirknado18:
Ii can adb sideload from flintman twrp. How do i do it through adb fastboot and what am i flashing the magisk zip through fastboot? Which zip. Hp touchpad has moboot dual boot sony elf bootloader. Tried bootbridge too replaced install zip with magisk zip renamed it install.zip and flashed it got error.
[Magisk] pndwal:
I meant to flash Magisk-patched_boot.img. dId you try this w/ IMG files selected from TWRP?

For PC / fastboot method, it's as per official Installation Instruction. Link on Magisk GitHub home page.

Else, this:

https://xdaforums.com/t/rom-official-9-0-evervolv-for-hp-touchpad.3923512/post-82568537

😕 PW
[Magisk] pndwal:
Yeah, but support for Android > 4.2 (J [excl. 4.1] & K) was only added with Magisk 18.1 ('for fun'!); Versions < 17.3 needed Android > 5.0.

https://topjohnwu.github.io/Magisk/releases/18100.html

J & K was consigned to the 'to hard' basket with Magisk 23.0 (no fun anymore?):

https://topjohnwu.github.io/Magisk/releases/23000.html

So window was open to stray KitKats and JBs from Magisk 18.1 - 22.1

From Changelog Also:

https://topjohnwu.github.io/Magisk/changes.html 😉 PW
[Magisk] Berta Paneslowski:
Hi Community,

i think i have a problem with magisk.

Using Magisk in my Oneplus 5 with crdroid 7.6.

I had the Magisk app hidden and after updating Magisk the app icon was gone. Then I reinstalled the apk and since then it looks like this:

When I click on 'install' I am supposed to select a rar image or Odin file. No idea what is meant by this.

Can anyone help me? I'm afraid I'm going to brick my phone again.
[Magisk] Didgeridoohan:
Now there's your problem...

First of all, "error 1" means nothing without the accompanying error description. My guess though, based on the quote above, is that it's something along the lines of "boot image patched by other program":

https://www.didgeridoohan.com/magisk/Magisk#hn_Boot_image_patched_by_other_programs
[Magisk] Didgeridoohan:
That suggests that the hidden Magisk app is still installed and therefore the regular app you reinstalled isn't trusted and can't access Magisk.

Take a close look at your installed apps and make sure that it's not there somewhere. It'll have a generic Android icon and whatever name you've given it, or it could be named Manager or Settings depending on what version you had installed when hiding it.
[Magisk] pndwal:
Especially if coming from pre 22.0, needed to UnHide / restore Magisk Manager first:

https://topjohnwu.github.io/Magisk/releases/22000.html

Now simply need to remove hidden Manager app (search and find) as well as new App, then reinstall new App to overcome conflicts / initialise App properly.

Settings / modules etc are safe (don't run Uninstall options from within App or TWRP). PW
[Magisk] Berta Paneslowski:
Big big thanks!! I have found the app named Setting and now i have access to magisk again.:)

Again, very big thanks!
[Magisk] romilspm:
Thank you. I was using Samsung SM-g532g (J2 prime) and the problem was already solved. I tried to flash the Magisk v23.zip (the apk, renamed to zip fil) (in TWRP) but that did not help. I forgot what specifically I did but I did something that returned it to normal. For the time being, my magisk is functioning normal again. Thank you for responding to my question.
[Magisk] HippoMan:
This site sometimes totally hangs after "Post reply" is clicked. At that point, the site has to be reloaded, and it doesn't initially look like the post went through, so sometimes people repost and only discover afterwards that the original attempt also had been accepted.
[Magisk] zgfg:
It happens a lot last days. And XDA mumbles about broken Matrix and Neo
[Magisk] J.Michael:
I have seen it when clicking "Like", as well as when "Post reply". In both cases, if I reload the page I see it did what I wanted.

Still don't know why it calls me "Neo".
[Magisk] HippoMan:
It will become clear if you take the red pill. :)
[Magisk] Jiute:
Hi there.

Trying to patch boot.img from latest release for Xiaomi A2 Lite V11.0.19.0 with no luck.

The patched file is created fine, but when used to boot the phone using platform.tools from the PC ist just hangs the boot process after security pattern.

I tried to boot the vanilla one from the PC and it runs fine.

Could it be any problem with magisk 23 and this last firmware release?

Waiting for you input.

Thanks
[Magisk] zgfg:
Have you patched with Recovery option unticked?

Did patching report an error in its window?

Try to re-patche the patched img to see would it report an error about the img file

You say you tried to boot with the patched img - are you doing

fastboot flash boot <patched-img>

or

fastboot boot <patched-img>
[Magisk] Jiute:
I patched the boot.img on the phone... i already had Magisk 23 installed... my phone got caught on a OTA update and lost Magisk... then i downloaded the V11.0.19.0 Fasboot IMG and got the boot.img from there.

After Patching the file i exported it to the PC and Fastbooted from there with fastboot boot <patched-img>.

And then i got the situation described... the boot just stales.

No errors were outputted on the patching process. It runs straight.
[Magisk] zgfg:
But what is the point of your command:

fastboot boot <Magisk-patched.img>

It will boot only one time to the system with Magisk

To really flash Magisk you must use the connand:

fastboot flash boot <Magisk-patched.img>

That means: flash the given img file to the Boot partition (command you are using means: Boot only one/next time with the given img file)

Further:

- Try to patch again and check if Magisk reports any error while patching (maybe something was wrong when patching the file)

- Maybe you have bootloop because of some Magisk module that you had before OTA (if you didn't wipe /data, particularly /data/adb/modules, that module(s) automatically activates when you boot now with Magisk - maybe that module was ok before OTA but now it causes bootloop)

In that second case you have three ways how to disable or remove your Magisk modules.

Go to Magisk Github, open Wiki and find a chapter right about disabling or removing Magisk modules (from TWRP, by booting to Android Safe mode or by use of an adb command)
[Magisk] Jiute:
Because i want to try the patched file first before i flash the phone one...

I always do it this way... i boot form the patched file from te pc and the i patch the boot directly on the phone after it has boot.

and i know the flashing option... i just dont want to brick my phone.