yashsingh1/xdaforums huggingface dataset:
[Magisk] Nightf0x_007:
Yes yasnac both cts and integrity passes
[Magisk] pndwal:
Tried clearing data? PW
[Magisk] Nightf0x_007:
No actually, device not certified is not my main concern, the apps started detecting root is
[Magisk] pndwal:
Apps probably don't see 'device is not certified' (they poll Google servers for cryptographic attestation to SafetyNet directly) but they / their updates will likely not show in Play Store. This should be fixed simply by clearing Play Store data...

Likely you have Device not certified result as you broke SafetyNet fixes at some point recently, and Play Store caches the result for some time. (Play Store with reset and show Device is certified after varying lengths of time for many users if data is not cleared.)

If that has occurred, bank / other apps have likely similarly cached the broken SafetyNet result. (Google Pay does this.) They may or may not reset flags without deleting data, but the only way to eliminate this possibility is to clear their data also. You can try your luck just clearing cache, but data clearing is often needed, so you'll need to set up linked cards etc again...

Of course, this may also be the result of an app update (more sophisticated custom 'root' / 'jailbreak' detection etc), and there have been several reports of bank apps upgrading their detection methods recently. If this is the issue you may need other hiding solutions, but you'll still need to clear apps data w/ each attempt to determine if any solution works...

Have you engaged 'Hide the Magisk app' in Magisk App settings? Tried uninstalling Magisk App (you won't lose Magisk settings, modules etc) to eliminate Magisk App detection? ( Many apps use tricks to detect even hidden / obfuscated Magisk App)... You may need this as well as M App hidden from your bank app using Hide My Applist LSPosed module. You may now need to hide other root apps (Titanium Backup etc) from your app this way also.

You may need different solutions also; banks are the new cats, and they're losing sleep trying to catch the mice...

Momo detection app will likely give good clues re. what 'root' traces an app may be able to detect on your device. (It won't show root apps etc being detected however.)

🤠 PW
[Magisk] TheShinyEnd:
Hi!,

So I updated my Pixel 6 Pro(was rooted; keeping root aswell) to the May update(sideloading) and before I've sideloaded the update, I have updated the magisk(Canary version) to the latest(24307 ??) version.

After I sideloaded the update, I rebooted the phone back into android and opened the magisk app.

I only see nothing; blank screen -- whenever opening using app icon I see the app icon -- I tried to reinstall using the canary version, uninstalling it using adb, removing its data. Failed attempt.

Now from my understanding I cannot use the stable and/or beta release since i'm on android 12 and only the canary version works with it.

how do I continue and get the app working again?

Fixed.
[Magisk] aleMarvel:
guys sometimes i lose check on play services in denied list.. is normal ? how i can resolve ? tx
[Magisk] pndwal:
magisk: Remove Play Services from DenyList

and

magisk: Remove Play Services from DenyList earlier

PW
[Magisk] zgfg:
Btw, I know very well that USNF removes GMS from DenyList - and we repeat that mantra every second day to a new newbie repeatedly asking the same (why GMS disappears from his DenyList) in one of the threads (Magisk, Zygisk, USNF or even MHCP)

But have you ever questioned yourself that statement from the USNF GitHub:

>> Zygisk module will never load if GMS is in the DenyList

Eg, I now made the following experiment:

- added GMS to DenyList

- removed post-fs-data.sh from /data/adb/modules/safetynet-fix

Now, of course, after reboot GMS is still in DenyList (bcs I removed the script in USNF module that removes GMS from DenyList)

But I don't see any problem with Zygisk:

- Magisk still shows Zygisk Yes

- Shamiko reports it's running in BlackList mode

- HMA (as Zygisk-LSPosed module) works happily

And most important, SafetyNet passes - that is, USNF 2.2 .1 still gelps me to successfully pass the CTS and SN

Screenshots attached

Note:

Tested on my Lisa with stock MIUI/A11 (not Davinci with Xiaomi.eu), hence on the phone where I really need USNF to pass CTS/SN

--

PS: If GMS in DenyList would really block Zygisk to load, then that problem shouuld pose with or without USNF

Hence I additionally disabled USNF and rebooted. Ofc, I was no more passing SN but Magisk was still showing Zygisk Yes, Shamiko looked ok and my Zygisk-LSPosed modules (HMA, Gravity and CustoMIUIzer) were still all working fine

At the end I tested even with Shamiko disabled, still I don't see how 'GMS in DenyList prevents Zygisk to load'?!

Or there was maybe a problem with an earlier version of Magisk/Zygisk, and/or with particular ROMs/devices
[Magisk] mordantly:
24.3, the module page doesn't have a repository. Some modules only availability is through the manager.
[Magisk] zgfg:
It has been removed already in Magisk v24 - please always consult Changelog to know what you are installing/upgrading

And relentlessly repeated here endless times to use eg Fox Magisk Module Manager app instead
[Magisk] mordantly:
I tend to not update when it works. I'll check out fox. Thanks.
[Magisk] pndwal:
I believe @kdragon is referring to this module, zy-USNF (as opposed to riru-USNF), not to Zygisk itself...

zygisk: Initial module implementation …

- Ported from Riru implementation

- Limited Java payload to com.google.android.gms.unstable as a fix for issues caused by model misdetection and flag provisioning

- Root companion process to serve classes.dex over socket

- Forces DenyList unmounting to pass basicIntegrity

2nd file line 168 here:

REGISTER_ZYGISK_MODULE(safetynetfix::SafetyNetFixModule)

Initial commit (reverted in favour of @osm0sis's improved method) note says: "The Zygisk module will never load

if

GMS is in the DenyList."

I think this is probably a matter of timing, and may differ per device... My guess is that execution order may be unpredictable; USNF may execute GMS hiding needed before denylist executes, and GMS is not in denylist in this case (even when previously added by user). If denylist executes first and user added GMS, it will be in denylist and prevent ZYGISK_MODULE(safetynetfix::SafetyNetFixModule) from loading without intervention...

It's only guesswork on my part, and experienced coders may well know better, but order of execution unpredictability may explain your result as well as the need for this mechanism.

Of course it didn't say 'Zygisk'... It said 'Zygisk module', as mentioned above...

😛 PW
[Magisk] andylam981:
hey guys, my banking app got updated and it is now able to detect my usage of magisk, despite I have it in my denylist, hid the app and have safetynet passed. Any idea? thanks!
[Magisk] pndwal:
Latest Official TJW debug Canary Magisk:​

Magisk (42e5f515) (24308)​

Several minor bug fixes

Diffs to v24.3​

[MagiskInit] Update 2SI implementation, significantly increase device compatibility (e.g. Sony Xperia devices)

[MagiskInit] Introduce new sepolicy injection mechanism

[MagiskInit] Support Oculus Go

[App] [MagiskSU] Properly support apps using shared UID

[MagiskSU] Fix a possible crash in magiskd

[Zygisk] Fix function hooking on devices running Android 12 with old kernels

[BusyBox] Add workaround for devices running old kernels

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

👍 PW
[Magisk] Jay1175:
Will doing an OTA update cause me to lose all my magisk modules and associated settings after I re-root?

Any way to back these things up?
[Magisk] aleMarvel:
what i must flash ? all two ?
[Magisk] zgfg:
Modules and Magisk database are on Data partition.

If your OTA (it depends on your device) does not require Factory reset (ie, wiping or formatting Data), you will not loose

However, after OTA you will not boot to Magisk since OTA will overwrite your patched img - but once you flash your new patched img, you will boot back to Magisk with your previous modules, etc

However, consider one potential problem - if some your old Magisk module is not compatible with the new system after OTA, booting to Magisk will not work - instead, you might end up with bootloop.

Hence, you should better disable (before OTA and everything) potentially problematic modules

As you can see, there is no generic answer (or telepathy and knowing what device and ROM you have and how you perform OTA, what modules you have and would they work upon OTA, etc)
[Magisk] J.Michael:
Magisk data is under "/data/adb". If the update does not force a wipe of "data", all of the Magisk data will still be there.

While you are rooted, you have access to "/data/adb". You can copy it wherever you like.

I don't think there is a "backup Magisk data" button.
[Magisk] Jay1175:
Thank you, I'm already on most recent magisk version flashing a new nightly build of lineageOS 19. I have the boot.img ready to patch and flash again after the OTA update, which won't clear my user data.

Just wanted to make sure I didn't have to back up modules in case they were completely removed if root was lost!
[Magisk] zgfg:
It should work then

Just consider that having a module like Smali, it may not be compatible with the new system and you should better disable it now

But if you have TWRP with access to Data, you can disable the module(s) even from TWRP and hence you can resolve that type of bootloop if/when it happens
[Magisk] CyanRose:
rappipay not works in my htc m9 with magdisk and mods of hide root
[Magisk] J.Michael:
Every time you think about how much you will hate losing something, you should back it up.

OTOH, you can probably download any module you misplace.

But please, don't ask what happened to the module repository in Magisk.
[Magisk] DiamondJohn:
One thing to be cautious of, is if any Magisk module is used to mount/install an app. The first time you boot after an OTA without Magisk will mean that that app wont exist, and android will delete/clean-up the orphaned data.
[Magisk] pndwal:
Sorry, I don't understand the question... flash all two what?? PW
[Magisk] theghostkill:
As there is no Fastboot Mode in Samsung, I can't use fastboot commands to disable dm-verity & Force Encryption

Magisk had this option in the past, but no longer exists.

So, how can I patch the AP_.tar file for my Samsung device to patch boot.img & vbmeta.img to install magisk as well as disabling dm-verity & Force Encryption?
[Magisk] pndwal:
FWIW:

Commits on May 7, 2022​

Fix app running without root

topjohnwu committed 43 minutes ago

Allow requesting root from non app process

topjohnwu committed 1 hour ago

(Should fix Canary build stopped working after today's fajita LOS update #5790 and more when release is built...)

👏 PW
[Magisk] RandomPooka:
I lost the custom update channel info for the canary builds when 24.x dropped. All I'm seeing in app is stable/beta. Can't seem to find the proper info for going BACK to canary anywhere either.

Would just downloading the canary manager apk from github restore that option?
[Magisk] lupastro82:
Hi, i tested a module for boot animation and work.

If i remove module restore previous boot animation.

So, there is a backup somewhere (so, i can create a module for replace a file without problem) or i need to make backup routine in module?

Some example please?

I just need to rename or delete a file if module is enabled, restore if is disabled.

Ty
[Magisk] pndwal:
Yup; if you mean to use Canary channel... Setting Canary in Custom Channel is a different matter... PW
[Magisk] Prof_Shekhar:
What is Cygisk? Is it modified version of Magisk? Is it better than Magisk? Cygisk support states that it includes Zygisk, MagiskHide, Denylist, SafetyNetChecker, Hide the Magisk app. Not much information is easily available on the net.

Appreciate if someone who has used or is using Cygisk can share some information/advantages/disadvantages of Cygisk over Magisk. Thanks.
[Magisk] Stillhard:
Or just use the 'debug' apk ;)
[Magisk] zgfg:
It was known as Custom Magisk by TheHitman7

The same day he renamed (and renamed the package name) he closed the project

Telegram channels can still be found but they are no more open for public

See:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-86715671

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-86717343

(Btw, I see that you read the first post, or at least liked it a month ago)
[Magisk] Prof_Shekhar:
@zgfg

Nice to hear from you after a long time. Appreciate your advice very much.

Will stick with my Magisk 24.3 and Lineage OS 19 1

A big thank you from me to @pndwal, @J.Michael and you for always helping me out.
[Magisk] ipdev:
When Magisk Denylist is Enforcing.

Magisk is unloaded as much as possible when a process in the Denylist is called.

If you include GMS, Magisk will be unloaded every time SafetyNet is checked.

The USNF module (all Zygisk modules) will be inactive during that time.

That is why the USNF module removes all GMS from the Denylist during early boot.

The next USNF release will only remove GMS if denylist is enforcing.

USNF - [GitHub] - post-fs-data​

Magisk Changelog [GitHub]- v24.0 - Link

[General] MagiskHide is removed from Magisk

[Zygisk] Introduce DenyList feature to revert Magisk features in user selected processes

State of Magisk: 2021 [Medium.com] - Link

Cheers. :cowboy:
[Magisk] Scientist07:
I was running lineageoOS 18.1 rooted with magisk. Updated to LOS 19.1 using the recommended guide (installed mindthegapps as well) and phone booted normally. Just had a quick look around then tried to root with magisk and ran into a bootloop after reboot.

The method I used to root was the same as how I did it with LOS 18. I downloaded the magisk apk, changed it to zip and sideloaded it using LOS recovery. There were no errors with the flashing and it completed in quick time.

How do I recover from this? I don't have any nandroid backups (stupid me) since I've had no use for them since I don't tinker with my phone much.

EDIT: Ended up installing LOS 19.1 from scratch. Now I just need a safe way to root it.

EDIT: I have a moto G7 power
[Magisk] pndwal:
Here's why:

https://twitter.com/i/web/status/1297833910320021504

Should be there still if compatible:

https://twitter.com/i/web/status/1297833911280492544

By using magiskboot tool:

https://twitter.com/i/web/status/1297833912714977280

Doc:

https://topjohnwu.github.io/Magisk/tools.html#magiskboot

🙃 PW
[Magisk] pndwal:
While Magisk modules can perform write operations where these are allowed, the usual implementation is simply to overlay the system at post-fs-data stage. ie. module files are 'magic mounted'.

This means nothing is actually replaced or overwritten, so no need for backup; 'changes' simply revert when module is disabled as you noted w/ module you tried.

Doc, samples:

- https://topjohnwu.github.io/Magisk/guides.html#magisk-modules

- https://topjohnwu.github.io/Magisk/guides.html#root-directory-overlay-system

👀 PW
[Magisk] pndwal:
You haven't said what device you have, but ss far as I know, there is no proper Android 12 compatible TWRP as yet, and sundry compatibility issues w/ custom recoveries is exactly why John says:

https://topjohnwu.github.io/Magisk/install.html#custom-recovery

...If you face any issues, please use the proper Patch Image method. 🙃 PW
[Magisk] Scientist07:
Sorry. I have a moto G7 Power. I used that method because I could not get the boot img from the LOS package. It's not like stock android where I can just unzip and get the boot.img file.
[Magisk] pndwal:
Yup, but @zgfg said USNF was working w/ GMS added, post-fs-data.sh removed from /data/adb/modules/safetynet-fix, and I believe w/ denylist enforcing (Shamiko disabled)... Unless he never enabled (enforced) denylist after disabling Shamiko. 😜

All modules? My understanding was that modifications are reverted only within a given process, per "Users will be able to assign a denylist of processes where Magisk denies further modifications and reverts all changes it had done."

My response was regarding why GMS in denylist (w/ denylist enforced) may not prevent USNF from working properly... My guess was / is that this is a matter of unpredictable timing for execution order...

🙃 PW
[Magisk] pndwal:
You just need to use a payload dumper app... PW
[Magisk] Scientist07:
I'm currently trying that but running into problems. Got python installed but running the commands gives the "cant open file...no such file" error. All the guides say something different about where you're supposed to place the payload dumper folder. I've never used this before.

EDIT: Just saw the payload dumper I downloaded has an easy way to do it instead of running commands. Did it that way and got the boot. Thanks a lot. Hopefully patching and flashing it should work for me.

EDIT:

Installation

The Magic Mask for Android

topjohnwu.github.io

I'm assuming if I were to use this instruction, I would:

copy boot image to my phone

download magisk app and use install option to patch it

copy over patched image to pc

flash it back to phone

It's been a while since I've used this method.

EDIT: Worked well
[Magisk] theghostkill:
Thanks for the info.

I can try this

But, I don't know how it's done. How do I create such a file, which format, etc? I have installed magisk, but no TWRP.
[Magisk] martyfender:
Why would you set these to true if you want to disable them?

You also usually need to delete data or factory reset for a new data partition to be created that is unencrypted.

I unencrypted my older Android 6 devices, but I believe it is no longer beneficial on modern versions.
[Magisk] theghostkill:
No, I want both to be FALSE only. But how can I do that? I have magisk installed already. I have TWRP but not flashed as I can't boot to system unless these values are false.
[Magisk] martyfender:
In the past,on my Android 6 devices, I used @osm0sis Android Image kitchen to remove these flags from a copy of my boot.img, patched it with Magisk and flashed it. I have not tried that on my newer Android devices.
[Magisk] zgfg:
Bootloop was likely caused by some module that was installed (for previous LOS/Android version) but no more compatible with the new

You had to pay attention and disable before upgrading.

Or (seems you have a working TWRP), you could disable the module(s) from TWRP upon the upgrade, when you observed the bootloop.

Btw, go to Magisk GitHub, read Wiki and section about resolving the bootloops caused by incompatible modules

Now, if your installation from scratch means wiping Data, then the Magisk database and modules (all at /data/adb) are deleted, and you can no more run into the bootloop caused by an old/left incompatible module
[Magisk] theghostkill:
I set both the values to FALSE in the boot.img, but now it's in bootloop.

Boot.img is extracted from patched AP_.tar file from Magisk.
[Magisk] pndwal:
Where did you get that?

File is .magisk and is plain text and can be placed alternatively in /data , /cache or /system with caveats especially for /system...

Seems this is reworked from @Didgeridoohan's wiki info here:

Installation Issues:Magisk and MagiskHide Installation and Troubleshooting guide

www.didgeridoohan.com

Scroll to Working with dm-verity and forced encryption section.

nb. The echo commands given will create the .magisk file with selected settings both using TWRP Terminal, or Terminal Emulator w/ root.

I'd be trying /cache personally...

Also, since these options don't appear in Magisk app for you, please say:

- what Sammy device you have.

- what your purpose in doing this is.

- why you think this may work without causing bootloop etc for you... PW
[Magisk] pndwal:
So John was right?!

https://twitter.com/i/web/status/1297833912714977280

😝 PW
[Magisk] pndwal:
Yup... Best to avoid MTP transfer...

Seems you have an A/B Legacy SAR device?

Nb. Bootloop could also be due to a module as @zgfg noted...

If you dirty-flashed ROM to restore system boot you may still need to disable modules. One way is simply to boot to safe mode (search for key combo for your device / OS), then reboot to system. (Works as long as Magisk Daemon detects key presses properly; this can fail for some Xiaomi devices...)

If this is your issue and you can disable modules w/ safe mode or other, you should then be sweet... PW
[Magisk] android_dan:
I have a Pixel 6 that had been rooted for some time with no issues. The last 3 or 4 times I've upgraded I, following the instructions posted @ pixel 6 xda, took OTA updates. The phone would take a couple of tries to reboot but eventually would without root. I would patch a boot file and flash it and all was good. Last update I downloaded an image, extracted the boot and patched it, upgraded, and flashed the patched boot. This now causes a bootloop no matter what I try. Flashing a non patched imaga solves the problem. Any ideas?

Also I've noticed magisk 24.3 has no uninstall option. Was this removed at some point?
[Magisk] zgfg:
Maybe a bootloop caused by a module that's no more compatible upon OTA

Did you read the posts from this morning?!

No matter if you upgraded Pixel and somebody else upgraded LOS
[Magisk] facet_:
Dear group of helpful specialists. For 3 years I have been using one rom on emui 9.1.0.120 on Huawei Mate 20 X. Immediately rotated. For 3 years, until Magisk 23, no reboots and problems, including google pay. I went through 24.3 and started the zigisk and from that moment the phone restarted randomly after launching any application. Sometimes it is quiet for an hour and sometimes every now and then. The worst thing is that sometimes it only reboots, but most often a restart causes a crash after restarting and the next restart causes all applications including settings to lose their settings. you have to configure everything from scratch. please help me, although the fault is on the side of the zigisk. The same magisk to 23 has never caused anything like this. I haven't installed safietyfix yet. I did ponkles and tested what causes the problem. The zigisk itself did nothing at the beginning but I configured enforce denylist and the reboots started. later turned on, the zygisk itself also caused a restart. Only after turning off the zygisk did the restart problem disappear, although it is still testing. Help please.
[Magisk] android_dan:
Only had one and uninstalled it before updating.
[Magisk] pndwal:
Any modules active?

What is configured in denylist? PW
[Magisk] pndwal:
Seems Pixel 6 issues w/ latest firmware was fixed w/ 24306 and sepolicy fixes / major changes.

Proposed:

New way to mock sepolicy: by controlling seclic #5690

Implemented:

Use LD_PRELOAD to intercept sepolicy on 2SI init

Try latest Canary.

Uninstall option is to restore images and / or remove Magisk config files (not the app)... it is only available when root is present therefore. 😉 PW
[Magisk] andrew2432:
[MENTION=1162986]Captain_Throwback[/MENTION]

Which safety net helper haha I have sample, it's all I saw in google?

I'm attempting with my full stock galaxy s5 soon, just using my g2 for testing.
[Magisk] Captain_Throwback:
https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground
[Magisk] andrew2432:
[MENTION=1162986]Captain_Throwback[/MENTION]

Sn passed on my g2! No pgo login on cm newest, lgd800 with lp bootloader

UPDATE: PASS SN, able to login snap chat, no pgo login...failed to authenticate. How's this happening??!!<<<<wrong thread for the last q...sorry!!!
[Magisk] Daemos:
I have an issue with magisk v8.

Everything works fine except for the fact I cannot get 'enable magisk hide' to stick. I can check the box, and reboot but it still is not enabled. Any solutions?
[Magisk] hokiealumnus:
You need to grant the Magisk app root access via phh's Superuser app.
[Magisk] negroxxx:
any user could install Xposed s6 and spend safetynet?
[Magisk] edyny1:
Here you go

https://cloud.tapatalk.com/s/58075889c6047/Magisk-v8_mod.zip

---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------

Ok cool
[Magisk] Ninoh-FOX:
Magisk v8 + xposed 86.6 + suhide + supersu 2.78 + root switch work with safetynet, so that xposed works with safetynet too (to me work fine)

Enviado desde mi E5603 mediante Tapatalk