yashsingh1/xdaforums huggingface dataset:
[Magisk] abagm:
Thank you for your quick answer! I Just -mmmh - I am not on stock, I am running a Custom Rom; to flash all AP files means being forced to flash all the other stock rom files - as far as I understand the installation guide. Are you sure? I tried different apk and different zip - only the old magisk23 apk did finiish (direct method and patching img), no other apk did manage that. Maybe the attached logs are clearer than me to show the difference. I can get Magisk classic, AND i would like to understand WHY it fails to run everything POST-magisk classic
[Magisk] m0han:
could you please look at post #48711and tell me which?
[Magisk] zgfg:
Don't phone about True Phone Stub but your V4A version looks suspicious.

Most of the others I use(d) and they would not

Disable, reboot and check

I use another V4A - screenshot, it was (still is) available on the Repo and my phone never switches to Permissive (not even when playing)
[Magisk] m0han:
did that; still permissive. will try the v4a you mentioned.
[Magisk] Makishima:
Any way to pass SN with the latest Magisk Canary on Pixel 4a now that Riru and USNF do not work? I denied gms and gms.unstable and cleared storage etc. and it seems I pass the basic integrity check but not CTS.
[Magisk] pndwal:
Yeah, as I said, you must set both to get setns (setns now doing the job faster etc instead of isolated). With setns but without isolated, nothing is working. 😜 PW
[Magisk] pndwal:
Back to USNF 1.x series + MHPC Force Basic if affected by September Google server end changes.

Use test2 Shim-the-keystore USNF or other modified version for Samsung, Android 12 etc. PW
[Magisk] zgfg:
As I wrote, isolated without setns works excellent, I never had any problem

However, with isolated + setns (or just setns) the phone looses fluidity

Hence again, for me setns does not bring any value, but brings troubles (isolated does not and makes the job)

Hence excellent, you can quote the author (I read myself, too), but setns is no use for me
[Magisk] Makishima:
I flashed the test2 USNF module and it still fails. I'm unsure what the September Google server end changes are. I have stable Android 12 and it worked fine with the previous canary without zygisk + Riru + latest USNF, Google Pay and everything worked.
[Magisk] pndwal:
Which app?
[Magisk] pndwal:
Fix for September changes was added to 2.x, so if affected 1.x series incl. test versions may actually be working, but you will need MHPC fix in addition to see results. PW
[Magisk] pulpf:
thanks it seems to work.

i will try a payment tomorrow

root beer is not full, is this normal?

and magisk detector i don't know either? are there other modules needed?
[Magisk] pndwal:
Well I didn't say you had a problem.

My comment was to make other user aware that Isolated "feature is deprecated because it will unmount Magisk modified files for every isolated processes, and the unmounting time cannot be well controlled, which may cause some modules to not work", and that setns is a "Faster new way to hide Magisk in isolated processes" but "Requires config "isolated" is enabled."

Seems you may not be running any affected modules nor facing isolated process related unmounting of modified files, but clearly mileage varys depending on setup.

Thanks for observation about fluidity w/ setns. - Different responsiveness shows something is active at least even if slower, but issues Dev mentioned may be more concerning for some... I hadn't noticed fluidity issues personally. PW
[Magisk] pndwal:
Yup, it was a hurried / not fully considered reply. 🤪

I'm not a Sammy user so others will be better positioned to advise.

Seems John doesn't consider custom ROM variations on stock setup either.

Given the above, it seems you will need some of the sammy-specific methods since device is Android 9 LV. Eg, doubt you can use Fastboot, so must use Odin... I don't know if your custom Sammy ROM uses .tar files etc, or if "flash magisk_patched.tar as AP, together with BL, CP, and CSC (NOT HOME_CSC because we want to wipe data) from the original firmware" can be done with custom ROMs, but you may need to flash all ROM components (w/ patched boot image) in Odin incl. CSC or other method to wipe data for first root on Sammy (could be factory reset achieves same result w/ custom ROM?), I'm not sure.

Either way, look for clues to uniquely Sammy methods in John's instructions.

I'd read OP's in a few custom ROM threads for Sammy devices (information from threads for other models should help too); some are bound to give blow by blow root instructions... PW
[Magisk] Qnorsten:
Freja eid, a Swedish application.

Freja - Apps on Google Play

Identify yourself and others with a secure and easy-to-use digital identity app

play.google.com

https://m.apkpure.com/freja-eid-my-id-in-an-app/com.verisec.mobile.frejaeid

Any version after 8.5.0 will either crash or throw an error message on my rooted phone.
[Magisk] m0han:
i'm on the latest alpha. i have only gravitybox module in lsposed v1.6.2 (6152). screenshots of my other modules are here. i added setns and initrc, so i have isolated+setns+initrc now. on the github page i read initrc config would 'hide' the modified traces of init.rc. but, magisk detector continues to

show

init.rc has been modified by Magisk.
[Magisk] zgfg:
Delete Cache and Data for Magisk Detector and test again - once it helped me, but only for a short time

Important: Be aware that detecting init.tc modifications by Magisk Detector is not reliable (false-positive results):

Init.rc test failed · Issue #12 · canyie/Riru-MomoHider

Hi, I'm running on a miatoll phone running arrowos (andorid 11) and magisk 23.0 + Riru 26.1.1.r500 + Momohider 0.0.7. I've created the empty files in /data/adb/modules/riru_momohider/config app_zyg...

github.com

That has been mentioned here by @pndwall couple of times - search through the thread
[Magisk] m0han:
thanks. had done all that before posting. and, i'm hoping @Eng.Raman would respond if he has a different take on this.
[Magisk] Chandru123:
I'm on the latest alpha build. In my device OP8P, enabling Zygisk causes SN to fail and disabling it passes SN. Anything I'm doing wrong here.
[Magisk] pndwal:
Are you using USNF 2.x? These need Riru to work, and that is disabled in recent TJW and vvb2060 builds if Zygisk is enabled due to conflicts arising from last changes to make Zygisk compatible with LSPosed.

USNF 1.x series is working with Zygisk, but you may need MHPC Force Basic (or other) solution in addition. PW
[Magisk] Dwightsch:
Hey PW, thank you very much for your detailed explanation.

Considering what you said about the "Chain of trust" and the HWK TEE, I guess the possible solution would be a Google and Android thing not really a Magisk thing. I Don't understand why this HW key based Execution Environment isn't a one to many Design? Like each process could request from a central TEE to be allocated a virtual TEE which is Specific to the app and should the process ask for no modification, the environment would be encrypted and signed based on that HW key system so no other process or execution could mess with it? I mean there must be an alternative distributed implementation of safety which doesn't sit at the gateway of the os and environment. So even if someone wanted to use adb or whatever and empty my bank they couldn't but they could for example change some visual behaviour in my launcher or run some independent process.

I mean i know Microsoft is employing the same trusted environment concept with the new release for windows and TPM2 and other requirements, but i really really hope it doesn't enforce it how Google seems to want to.

Plus there really really should be other considerations to a "secure" design from Google's perspective! Like imagine a device which Huawei or some other dictator-funded company designs, Does Google really want the users stuck with the supposed "Trusted execution environment" there? That's a much scarier and more catastrophic outcome rather than a simple solution to suspend your banking services when you lose your phone or other actual solutions.

BTW i live in this hole called "iran" sadly. The funny thing is that there is really no concern for security like there would be for Gpay or PayPal or whatever sophisticated service, in local banking or other services here.

They are often very poorly designed with decade old bugs and caveats since they're designed by some exclusive government funded mostly incompetent groups and they get to enforce I don't have certain apps installed or certain modifications done! I mean even now some apps forced to be used for remote education or banking or other devices that you will need weather you like it or not without competitive alternatives, demand your device not to be rooted, not have apps like telegram or signal or waze or adguard or vpn services and... Since they're possibly threats to the dictatorship...

I mean I suppose that's the globalist concensus and the survivalist powers follow like Google or Microsoft or they're actually the Designers of these ideologies like our genius friends have been at apple for decades...

Idk, after all I gotta educate more on these matters and implementations before complaining but believe me, the consequences will be there.

Other than that I got nothing but respect for Mr Johnwu and other active members of the android development community. Most of you have done more good and offered choice and freedom and... Than you can possibly imagine.

Cheers
[Magisk] pndwal:
Can't give specific help, but this app perfectly demonstrates my points in post above; clearly it is developed with serious security concerns. I found this information:

Reasons:

This and more:

https://promon.co/security-news/mobile-eid-in-app-protection/

There are many methods security-centric apps utilise to detect modified environment. This wiki covers many:

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

If you wish to persist, search back here for Riru-MomoHider and Riru-Unshare modules. The first may be most likely to help hide isolated processes.

I'd also try running with Magisk App (leave Magisk root) completely uninstalled (as a test) - some bank apps actually detect it even with App hidden! - report back here for pointers if this succeeds. PW
[Magisk] zgfg:
Well, I installed your app (I'm not Swedish) and went with no issues up to the point to send my e-mail to your Gvmnt - there I stopped, I did not want to proceed

I had no crash or warning that phone is rooted, no issues

- A11

- Magisk Custom 23010 e4eeb23e (latest, based on latest TJW Canary but with MagiskHide instead of DenyList)

- Zygisk: No

- MagiskHide

- Riru

- Riru-Momohider hiding su from path

- Riru-LSposed

- Hide My Applist

- MagiskHide: Freja-eID enabled

- Hide My Applist: hiding Magisk app, LSPosed, GravityBox-R, CustoMIUIzer from Freja-eID

Probably some of the settings were too-much, but that was my setup and I used my template hiding 'risky' apps in HMA module

When hiding in MagiskApp and HMA were configured, I rebooted (paranoia) and only then first time opened the previously installed Freja-eID

Ref. also to:
[Magisk] pndwal:
A Google executive (?) recently called Magisk / modding community 'white-hat'. Unfortunately cybercriminal communities are definitely not, and are on the rise. The consequences are already here. Banks etc are partners with Google at least for GPay purposes, and IOS is seen by many corporate players as the more secure (or the only secure) mobile platform, so it stands to reason Google is keen to offer bulletproof TEE attestation, and that is HWKA.

Alternatives could be debated, but this model has been persued for some years now, and we may or may not be close to seeing full deployment. - Google have a vested interest; clearly the model chosen is to keep a guard at the gate, wake him up and ensure he cannot fall asleep...

It will also allow users to have root + any other custom mods they like while ensuring app providers get accurate device status info. in SafetyNet, exactly what Google wants, so why persue another model?

Windows 11 TPM2 seems to be a very similar hardware based concept:

https://bgr.com/tech/how-to-check-windows-11-tpm-2-0-compatibility-on-your-pc/

Interesting it seems WSA doesn't (can't?) use this:

🤠 PW
[Magisk] abagm:
Rooting works with magisk 23. I would just like to understand WHY not with the other apps/zips - what exactly causes the difference? Samsung it is not, I guess. Never before I had problems rooting samsung, never needed to follow John Wus guide so far. Maybe there is no plausible explanation -mysteries of machines...🎃 Thanks anyway!
[Magisk] Eng.Raman:
As i experienced that it depends on which magisk version ( stable/alpha/canary/custom ) you have installed.

Most likely you will get the best test results with the version that has a DenyList / Zygisk off ( Especially alpha ).

My device passed all the test results even without DenyListed the Magisk Detector.

Yes but the test result shouldn't be "modified" all the time. It is normal to alter between ( modified / No modification ). Anyway on the latest alpha-a3eafdd2 my test result is ( No trace of modification found ) all the time ( It was checked since yesterday till now ).
[Magisk] m0han:
i've got stuff working fine as of now. latest alpha, isolated+setns+initrc... thanks, everyone.
[Magisk] rodomb:
How is possible to have MagiskHide in 23.0 version?
[Magisk] zgfg:
Please read again what I wrote:

"Magisk Custom 30010 e4eeb23e (latest, based on latest TJW Canary but with MagiskHide instead of DenyList)"

Ok, I made a typo, it had to be 23010

And there were EXTENSIVE discussions here about MagiskCustom and Magisk Alpha, derivatives of Magisk (hence not TJW's deliveries) where you can still use MagiskHide (and without Zygisk)

For example, you can find my post from cca 48 hrs ago, about testing exactly that same MagiskCustom e4eeb23e (and I'm still happily running that Magisk version)
[Magisk] V0latyle:
Is there a possibility that Magisk in its present configuration could be related to the device going into Rescue Party on certain devices running Android 12?

On the Pixel 4a, 5, 5a, and 6 series, dm-verity and vbmeta verification must be disabled in order to boot a patched boot image. This is only required on Android 12, and was the only requirement for permanent root on the 12 Beta.

However, with the 12 Stable release, we are seeing a new problem: with dm-verity and vbmeta verification disabled, the device will go into Rescue Party unless /data is wiped.

The only potential workaround for this, which seems to be hit or miss, is to sideload the OTA, then immediately enter fastboot and flash /vbmeta and /boot before rebooting post update.

This occurs regardless of version of Magisk used - 23000, 23001, 23010, 23011.

Any insights on this? I'm asking here because my understanding is that a corrupted ramdisk will send the device into Rescue Party. If vbmeta and stock boot image are flashed without any flags, the device will boot normally; interestingly, with stock vbmeta and boot, a patched boot image can be live booted via ADB for temporary root.
[Magisk] pndwal:
🤔 23.0 always had MagiskHide! PW
[Magisk] V0latyle:
Another question: Is there a way to clean up a Magisk install without root? For some reason, even though my boot image is patched, Magisk reports no root. I suspect a signature mismatch or possibly ramdisk issue.
[Magisk] zgfg:
Very simple hint (and asked/answered) almost every day:

Look for your previous Magisk app/mngr, specially if you did "Hide Magisk app/mngr" back then

Find it in apps drawer or Settings/apps and uninstall that old app - recall the name you gave it when hiding, default was Settings)

Then reboot (and if necessary reinstall the new Magisk app)

PS: If I understood you properly (your screenshots would help), i.e. if you wanted to say that Magisk app declares that Magisk is not installed (N/A)
[Magisk] V0latyle:
I did not hide the Magisk app; I believe I'm dealing with a ramdisk issue that's causing other problems on my device.

I ended up wiping due to those other problems so I guess it's moot for now
[Magisk] ipdev:
To add to V0latyle's post.

Pixel 4a [sunfish] has no issue updating and installing Magisk on Android 12.

The issue starts with Pixel 4a (5G) [bramble].

This is also the first Pixel using Boot Header v3.

Boot image header, version 3 - source.android - Link

Vendor boot header - source.android - Link​

The 3, 3a, and 4 series along with 4a are using header v2.

4a (5G), 5 and 5a are using header v3.

Just downloaded and checked.

6 and 6 Pro are using header v4.

I am not sure if that is the problem but, it is quite a distinguishing line between Pixels that have this issue with Magisk and those that do not on Android 12. 🙃

After a little more testing on my 5 [redfin], I will open an issue on GitHub.

Magisk - GitHub - Issues - Link

Cheers all. :cowboy:
[Magisk] ipdev:
Yes but, no. :whistle:

You need heighten (root) access to view and modify /data.

I have previous posts about manually removing Magisk.

From a rooted system.

Link

From custom (TWRP) recovery.

Link

TWRP is available for redfin. ;)

[RECOVERY] TWRP 3.5.0_10-0 - TeamWin Recovery Project [REDFIN] [TESTING] - [xdaThread] - Link

Cheers. :cowboy:
[Magisk] pndwal:
Yup: Just delete all /data/ adb directory content.

Use TWRP (could just Fastboot boot it), ADB etc. Worst case, factory reset will do it!

Image backups can be removed from /data (ie. magisk_backup_xxxxxxx etc) also.

App is simply uninstalled separately of course... PW

Edit: nice detailed links above. 😜
[Magisk] Didgeridoohan:
This is likely the source of your issue... The partitions can't be mounted properly, so no magic mounting can happen (no modules will be able to mount their files).

Why? Don't know... Possibly due to an incompatibility with your device.
[Magisk] pndwal:
Many fixes committed in last minutes:

https://github.com/topjohnwu/Magisk/commits/master

Eg. Canyie's - Fix init.rc path detection #4836 fixes:

- canary 23001: Installed "N/A" on Android 11 AOSP #4319

😛 PW
[Magisk] jnshk:
Thank you. While this is a little disappointing because the nature of the problem means there may be no simple fix, at least now I have an idea of why it doesn't behave as usual and I can start searching to see if anyone else has come across this issue and what (if any) solutions they came up with.
[Magisk] V0latyle:
Thank you, although TWRP does not work with Android 12; it just gets stuck at the TWRP screen and never gets to the unlock screen. 3.5.0_10 worked on the Android 11 bootloader but as soon as I updated it was no good.
[Magisk] V0latyle:
Is this a hardware thing or an Android thing? According to this link you provided, it seems to be particular to Android....which would make sense, because we never had an issue patching boot images on the 4a 5g, 5, or 5a on Android 11. This issue only started with Android 12.

Thank you for finding this by the way! Recognize!
[Magisk] Nekromantik:
Thanks

Hope the ticket you raise has someone find a fix :)
[Magisk] V0latyle:
@osm0sis my mistake, I didn't know if we had a particular place to address the Magisk + Android 12 issue. I will open a new thread so we can keep that on topic.
[Magisk] Vision:
Hi, i have Sony Xperia Z5 android 7.1.1, i try latest canary building look good until now, just the magisk app don't have the button for check safetynet why? And i get this reply, now what?
[Magisk] pndwal:
Have you tried just Fastboot booting (not flashing) it? PW
[Magisk] V0latyle:
Yes, that's the only way I've used TWRP ever since Android 11 came to the Pixel 2, as I remember there was some conflict between TWRP and Magisk in the ramdisk.
[Magisk] zgfg:
People, before 'reporting', read the Changelog, and please be up to date and follow what was already mentioned, debuted or announced here

Yes, new Canary DOES NOT include SafetyNet checker. Standalone checkers are available from Google Play

Sorry but please do not ask next question why MagiskHide is also gone

Who does not like, does not need to update. There are also other, alternative versions of Magisk

Personally, I'm not using this new Canary (I did test/use it for few days). And as long as there are alternatives, I don't think about anymore
[Magisk] pndwal:
Some notes re. how to pass:

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

New solution for checking:

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

🤠 PW
[Magisk] Vision:
Thanks for answer, Yeah i know, just ask because not for button but for can't pass safetynet, but here writes me some solutions, i try it now if work's
[Magisk] Vision:
Hi, for my Sony Xperia Z5, latest Magisk Canary the safetynet fail, but i extract manually the Universal SafetyNet Fix safetynet-fix-v2.0.0.zip by author kdrag0n only some parts see pictures, because can't flash via Magisk because the old 1.2.0 not support android 7.1.1 but the 2.0.0 support but with riru only but can't flash it for this extract manually and now pass safetynet net, first enable zygisk and enforce denylist and in the denylist put the Google play services options com.google.android.gms.unstable and com.google.android.gms, for my phone this work and i see the Netflix app again and say the device is certified again, and i think no need riru because latest canary have already inside the new zygote
[Magisk] pndwal:
https://github.com/kdrag0n/safetynet-fix

Xperia Z5 launched with Android 5.1.1

It therefore is too old to have hardware for Hardware TEE attestation, so never needed Universal SafetyNet Fix. 😜

You only need to manually add the Google Play Services SafetyNet process (com.google.android.gms.unstable) to denylist (assuming Magisk is in /sbin) that was formerly added by MagiskHide. 😛 PW
[Magisk] toolhas4degrees:
It would be nice if some of the people who make magisk modules find someone to make an app for repo that is going to be pulled
[Magisk] pndwal:
FWIW, John announced changes re. GitHub repo he plans to make but gave no ETA.

"State of Magisk: 2021" on Medium.

Looks like selection of 'trusted community members' to administer, maintain and organise the GitHub Repo is the real answer; a new 'app' won't enable modules to be vetted / added to official GitHub repo...

I'm assuming that John means to re-activate GitHub Repo in Magisk once the mooted administration of it is established.

Also, as a lower priority, users may eventually be able to set their own 'online Magisk module sources', ie custom Repos.

I think many agree with you that it would be nice to see these improvements sooner rather than later, but just glancing at new Magisk commits from time-to-time reveals how occupied John is with things Magisk of a more pressing nature ATM...

I'm sure John will deliver these slated changes / improvements in reasonable time, and perhaps sooner. - He has delivered on pretty much everything he has envisaged / disclosed as on his 'roadmap' to date! 😛 PW
[Magisk] toolhas4degrees:
His buddy in the alpha thread is doing most of the work right now
[Magisk] pndwal:
I don't agree; not a fair assessment at all. 😕

Previous year:

https://github.com/topjohnwu/Magisk/graphs/contributors?from=2020-10-30&to=2021-10-30&type=c

(Vvb2060 29% of number of TJW commits)

Previous 3 months (since returned from sabbatical 😉):

https://github.com/topjohnwu/Magisk/graphs/contributors?from=2021-07-30&to=2021-10-30&type=c

(Vvb2060 14% of number of TJW commits)

Great help no doubt. Different focus... And John has to vet all commits incl. authored by others. PW
[Magisk] toolhas4degrees:
He may just pass them to him at this point.
[Magisk] pndwal:
Wat?