yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
In the past I used to patch on another device and it worked, but maybe differences were less - although still present:

Recently, with Magisk v24.1, I patched on Xiaomi Mi 9T, MIUI 12 5.2, A11 (davinci)

and flashed to Xiaomi 11 Lite 5G, MIUI 12 5.8, A11 (lisa) - with no problems and no bootloops

BUT:

Davinci was originally released as A9 device, it was and still is:

- SAR is not read-only for TWRP

- not A/B device and we with the separated Boot and Recovery (both only 32 MB)

- Magisk app "wrongly' declares as Ramdisk No, although while patching, it finds Ramdisk in boot.img

Lisa was recently released already with A11:

- SAR is fully read-only

- it's A/B device, and Recovery is integrated to Boot (both SHRP and Magisk install to boot.img of 128 MB

- Magisk app declares Lisa as Ramdisk Yes

Despite both being Xiaomi, with currently MIUI 12.5, A11, there are substantial differences in the Boot/Recovery/Ramdisk

And I was still able to patch on Davinci, boot.img from Lisa, with already installed SHRP into, adding Magisk - and when I flashed on Lisa everything (SHRP and Magisk) continued to work
[Magisk] pndwal:
Nb. This is not wrong... It shows OEM ramdisk = No as this is to indicate probable bootloader incompatibility with ramdisk in boot...

Simply indicating ramdisk = Yes where Magisk has 'manually' added ramdisk indicates nothing (would be a false flag / doing that would be wrong) because Magisk always adds basic ramdisk w/ initramfs when missing since:

https://github.com/topjohnwu/Magisk/commit/e72c6685edf81706617a3444575c4500b9b8fe6c

Whether or not ramdisk can function depends entirely on the bootloader...

https://topjohnwu.github.io/Magisk/boot.html#piecing-things-together

Actually Magisk doesn't 'find' ramdisk; it 'manually' adds it (as mentioned above) where OEM hasn't!

Worth nothing (fine point) that this is not officially SAR (except by 'Magisk's definition'!; And I notice John's now removed SAR status indication from Magisk App); it is officially 2SI however...

- 2SI Comes with OEM 'hybrid' ramdisk in boot partition whereas SAR A/B devices come with 'recovery' ramdisk in boot partition.

Further, 2SI will always boot into initramfs (ramdisk) and let userspace handle the rest of booting including deciding whether to boot into Android or recovery. Officially called "USES_RECOVERY_AS_BOOT". SAR lets the kernel pick whichever rootdir to use (ramdisk for recovery, or system for Android) based on information from the bootloader.

Very true...

Yup... And I have to agree it seems it can often work well... 😛

But users have reported that in some cases it hasn't... Just think the hazards of any unorthodox usage, or possible reasons for it not working, should be considered. 😜 PW
[Magisk] zgfg:
I have excluded the first part of your answer - I don't want to argue if Magisk app declaring Ramdisk No in that particular case is 'wromg' or not - and originally I did not write wromg but 'wromg'

But you must also admit that if it was not wromg or 'wrong', it is troublesome for many users

And it all depends how you define the types of devices, regarding the Ramdisk. Of course once we agree on TJW's definition, then the way how his app displays Ramdisk Yes or No becomes undoubtedly correct

But somebody could have defined things differently, and then not displaying No in that particular case - making the life easier for a number of users

---

But the point of my post was really in that second part, where you also agree that patching on device 1, the image from device 2, would OFTEN (and hence NOT ALWAYS) work

And that was exactly my intention yesterday to take a chance and to try to help to the user for whom (on his device), both Direct method and Patching failed with no useful logs to show what/how went wrong

Long story, long::)
[Magisk] pndwal:
Yeah, arguing is not the point... you / me / others are only trying to provide useful information here! 😛

I agree John could certainly be more clear, eg clarifying that 'Ramsisk' here is specific; ie. it's OEM (factory) ramdisk in boot partition only... Seems we're left with that task! 🤪

But the issue here is that not displaying No (displaying Yes) for custom added ramdisk is meaningless as every device would show Ramdisk = Yes after the first attempt to install Magisk, whether successful or failed!

Magisk installation on most A-only SAR devices would still fail (Xiaomi being the notable exception) with no current indication of the issue, ie. there is no working ramdisk in boot partition! ... Not sure how this would make life easier... 🤔

As an indicator of Bootloader compatibility with Magisk in boot, this behaviour simply works as intended; Yes is a conclusive 'Compatible ramdisk exists in boot' while No means 'You'll have compatible ramdisk in recovery, and may be able to use Magisk's manually added (custom) ramdisk in boot'...

John also explained the difficulty confirming that custom ramdisk in boot will work when Ramdisk = No here:

https://github.com/topjohnwu/Magisk/issues/3239#issuecomment-703260778

Yes, must say that this was (well) worth a shot and may well have worked! - Very helpful!

Sorry if my points seemed to minimise your efforts in any way; not my intention at all... Actually, I'm sorry it didn't work also...

Really, intention was just to point out a possible reason for this failing... I agree real problem is far from clear; all we can do is catch some red herrings... They're pretty good fried! 😜

Keep up the good work! PW
[Magisk] zzz2002:
I am not sure what I am doing wrong.

Device = Samsung Galaxy s7 edge (sm-g935f)

software = LineageOS 19.1 (Lead Developer Ivan Meller)

Installed LineageOS + NikGapps.

works some minor glitches, they don"t affect operation mainly appearance.

If I run YASNAC it reports passes on both basis integrity and CTS profile. Rootbeer only reports test kets and dangerous props.

Installed Magisk 24.3.

YASNAC fails on both counts. Rootbeer report everything is bad. add apps to deny list, added gms and gms.unstable .

nothing I do works as expected.

Suggestions please
[Magisk] pndwal:
If it was passing, dev must spoof fingerprint (as it's a custom rom) and likely makes other prop changes in ROM, so I'm assuming it's not official LOS as their policy precludes this. (Magisk and hiding modules are needed with official LOS.)

It may be that Magisk itself makes changes that need additional hiding, I'm not sure, or may override some ROM changes for SafetyNet, or you may be running modules that break SafetyNet? - Any / which are running?

Further, you will likely have success with MHPC module, USNF module or both.

You likely don't need USNF as your release Android version is 6.x; generally only devices with RV 8.x and above have requisite Hardware Key Attestation components to enable hardware SafetyNet evaluation type.

So try simply loading MHPC unconfigired (adjusts sensitive prop values to values that won't be detected by default)... This may give you a pass, or fix basic Integrity.

If you now have basic Integrity passing only, you may need to configure MHPC using a terminal emulator app with a different fingerprint to pass CTS Profile match.

If you still haven't got basic Integrity pass, try loading USNF also; it does more than force fallback to Basic evaluation type. It adds back MagiskHide functionality incl. sensitive prop changes that can help on old devices...

Do tests above with no additional modules enabled...

Hope this helps. PW
[Magisk] zzz2002:
I seem to have fixed the problem by going back to Magisk release 24.0.

I had noticed that with release 24.3 Zygisk was "no" and stayed that way no matter what I did. I had assumed, mistakenly, that the problem was a "display" problem.

With 24.0 it seems to be working fine.

I am debating whether to move to 24.1 ...
[Magisk] pndwal:
Haha; zygisk modules / fixes broken!

Looks like you have this:

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

Watch this space; not fixed yet, Shana's on it and Canyie assigned 9 hrs ago...

Looks like 24.1 is ok, 24.2 broke things... Seems to be an Android 12 regression...

👀 PW
[Magisk] zzz2002:
next dumb ? where can I find MoMo
[Magisk] martyfender:
This is where I got it, but this link no longer works and takes you to the coolapk home page, I'm guessing in Chinese:

https://www.coolapk.com/apk/io.github.vvb2060.mahoshojo

It appears you have to use their app now which is, I assume in Chinese, which I can't read so here you go:

I have attached the last version that I downloaded from there in the past, 4.0.1:

However, I'm not sure if this kind attachment is allow to be posted here or not?
[Magisk] zzz2002:
Thanks very much. DLd and installed, it works, gave me a comparison to previous installs.
[Magisk] pndwal:
Catch 22... TG link is still working, but mods won't let us share that. 🙁 ... PW
[Magisk] Kiwi8:
Has anyone of you managed to get Zygisk mode working in Magisk 24.3, on an android 7 phone (mine is Huawei P9 btw)?

Also, will Universal SafetyNet Fix by kdrag0n support android 7 phones in the future or is it the end of the road for such phones?

Thank you all in advance.
[Magisk] AndDiSa:
@Kiwi8 yes, running fine on Nexus 7 (2012) with AOSP 7.1.2 build ... but I needed to patch the boot.img as neither TWRP installation nor direct installation is working with 24.3.
[Magisk] pndwal:
This issue seems to be for Android 12:

Zygisk fails to hook AndroidRuntime::setArgv0 #5604

Fix WIP:

Fix xhook cannot hook app_process #5623

It may / may not be your fix, but there are also several downstream fixes already pushed to fix selinux regressions for older devices:

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

Yup:

magisk: Allow limited installation on Android 7 and older …

Key attestation was introduced in Android 7.0, but Android 7.x doesn't

have InMemoryDexClassLoader so our Zygisk module is incompatible.

In general, users on such old versions of Android don't need to bypass

hardware-backed attestation (which isn't even applicable on Android 6

and older), so allow them to install the module without the Zygisk part.

Closes #156.

kdrag0n committed 8 days ago

👀 PW
[Magisk] VD171:
I wrote a guide about how to bypass the detection for unlocked bootloader.

Enjoy

https://xdaforums.com/t/guide-how-to-bypass-detection-for-unlocked-bootloader.4419159/
[Magisk] ragenstein1:
Hello. I am new to this world and could use some advice. I apologize if this is not the correct place to post this. Please direct me to a better thread if needed.

I am looking for advice/suggestions on Phones that cost under $400 (new or used), that have guided documentation for how to achieve the following:

- Unlock bootloader

- Root phone via Magisk (WITHOUT USING TWRP)

- Run these modules = LSPosed, SHAMIKO, XPrivacyLua, Universal SafetyNet Fix

I'm a bit overwhelmed trying to find a phone with the documentation/guides I need, so any help is appreciated. I'm not afraid of a challenge, but dont want to spend weeks trying to get a phone setup.

If anyone has suggestions on Phones with good guide/documentation that will GUARENTEED pass SafetyNet for banking apps, I would love to hear.
[Magisk] VD171:
I Love Xiaomi ♥️

Big company, cheap repairs, easy rooting.

All Xiaomi devices are "magisk-friendly" and "lsposed-friendly".

Certainly, mediatek devices are too easier for flashing than qualcomm snapdron.

But, fastboot is enough for both.

I prefer those have "red" in the name.

But, it's just a personal choice.
[Magisk] m0han:
pray, what are your devices? and, which among them is your daily driver? :)
[Magisk] VD171:
Actually I'm using Redmi Note 9 as my main device.

I have two Redmi Note 9, Redmi 9A, Galaxy A01, Galaxy A01 Core, Galaxy A10s, Galaxy J5, Galaxy J7 Exynos, Moto G4 Plus, Moto G5, Moto G5s, Moto G8 Plus, Moto One Macro and some others.

My mother has a Redmi Note 10, I consider the Redmi Note's model a good choice.

Certainly, Xiaomi was the easist brand for rooting. For Motorola and Samsung just some devices are allowed to unlock bootloader.
[Magisk] pndwal:
New Official TJW debug Canary Magisk:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86612093 👍 PW
[Magisk] vandyman:
Magisk Canary 24304 (P6). I had a continuous bootloop after doing a direct install.

After the fourth loop. When the screen shows the "push to pause". I held in the volume up button and my P6 booted up.

But the modules where disabled.

I just wanted to let everyone know what I did incase they have the same issue. I almost was going to flash the stock boot image.

Got lucky...
[Magisk] VD171:
If you are not sure if you need canary/alpha version, certainly you do NOT need it.

I suggest you to keep on stable version only.

Except if you know exactly what you are doing.
[Magisk] vandyman:
I have no clue on what you are asking or talking about.

I have been using Canary on my P6 since October 2022,because I can.

And I have been a tester since the Chainfire days.
[Magisk] exis_tenz:
Wow! You are a time-traveller!
[Magisk] Fishawy:
Same on my OnePlus 9 Pro. The "Magisk bootloop saver" module saved the day and disabled all modules without having to boot to safe mode.

Still, enabling any module after normal boot results in the same bootloop.

24303 was perfectly fine. Hopefully someone can look into that.

Edit: Same issue being reported on the main Magisk thread with particular modules. "Fullscreen/Immersive Gestures (Q-S)" in my case.

https://xdaforums.com/t/magisk-general-support-discussion.3432382/page-2560
[Magisk] Shazilsonu:
I have a problem with Zygisk.

When I was on Magisk Version 24.1 my Zygisk was ON and Pased Saftynet. When I Update Magisik to Version 24.3 (Latest Version)It Shows Zygisk= NO even in Magisk Section Zygisk is ON.

How I Fix this Problem.
[Magisk] ragenstein1:
Your the exact member I was hoping would comment! Thanks for the advice!! I found the phone I'm going to go with!
[Magisk] vandyman:
I have been back in time using the Clock works mods and Phil's root, if you can remember that far back.
[Magisk] guhvanoh:
Did you reboot to apply the changes?
[Magisk] thangjin207:
can i change widevine L3 to widevine L1 ?
[Magisk] pndwal:
But going forward is interesting!... What has happened to Magisk in October 2022?... to hiding mods?... SafetyNet evaluation types?... ... Putin? 😜 PW
[Magisk] vandyman:
LOL.. , the Matrix here on XDA needs an overhaul. Oh the Pixel 7 is awesome. No root needed anymore.

(after a little sleep and a new crystal ball. I am back to OCT 2021)....
[Magisk] zgfg:
L1 requires certificate for your particular device.

You should have it with the original firmware (unless it was a cheap device or firmware for some region where Netflix is blocked or so)

If you switched to custom ROM and lost L1, then that's the problem with that ROM

Generally, you cannot spoof L1 (it's only possible to downgrade from certified L1 to uncertified L3 - there is a module for, but I don't know who really needs that)
[Magisk] asripath:
Flash Xiaomi rom for your region for your device or xiaomi.eu for your device... retrieve from settings security fingerprint unlock payments L1 cert.
[Magisk] zgfg:
Yes, if @thangjin207 is Xiaomi user, with eu he should have L1
[Magisk] digger16309:
I'm not sure where to ask this so I'll try here since it is Magisk-related.

I upgraded from A11 to A12 FEB update on my Pixel 5. I'm rooted using Magisk 24.3 stable, Zygisk enabled, USNF, running Clean Slate kernel and a few different Magisk modules, including Addon Features for Pixel devices which modifies System UI. I did not upgrade to March because one of the modules won't work on the March update.

Even though I have automatic system updates on restart turned off in developer options, and I didn't physically accept an update, Google Play Services downloaded it anyway. System Update is now showing there is a 1.89GB update that will install on restart (thought I don't know if it will or not...see above developer options). I'd really love to delete that OTA but I can't find it. Short of that -

My question(s) - what should I do with Magisk, if anything, to limit whatever damage this forced update may take (bootloops, unable to root, etc...) if it occurs on my next restart so I can avoid having to having to wipe data? If it forces me to take 12L, can I downgrade to 12 (Feb) without wiping?
[Magisk] locolyric:
i use hidemy app list , adding that specific banking app in the list, and it didn't detect any tricky move made by that banking app. too bad.
[Magisk] nacos:
That is correct! The XPosed module in itself cannot hide the root therefore, you need to add the bank app to the Zygisk in settings, under Configure Deny List. I would also recommend installing Shamiko Magisk module, instead of using the built in hiding mechanism (don't forget to disable Enforce Deny list if you have Shamiko installed).

To recap:

1. Install Shamiko and reboot

2. Configure Deny list in Zygisk and add your banking app

3. Disable Enforce Deny List in Zygisk settings.

4. Reboot and enjoy.
[Magisk] VD171:
The built-in mechanism does NOT hide root or magisk or magisk modules.

Just reverses Magisk's actions.

Even "without" magisk applied to an app, magisk keeps detectable.

Shamiko is the best solution for hiding root, magisk, magisk modules, xposed, lsposed and lsposed modules.

Enforcing denylist should be DISABLED.

Shamiko official website:

Releases · LSPosed/LSPosed.github.io

Contribute to LSPosed/LSPosed.github.io development by creating an account on GitHub.

github.com
[Magisk] locolyric:
on android 12, non of the above action can hide the root detection from this app below.

hongleongconnect

is a malaysian banking app.

But it can hide in android 11 with magisk v23.
[Magisk] nacos:
For this, and other similar reasons I'm still on Android 10. Up to date doesn't necessarily mean better, especially when Google is involved - I've learned this the hard way.
[Magisk] VD171:
If you want to avoid google, why are you using android?

I feel it some confusing.
[Magisk] hungtinglung:
let the pictures do the talking
[Magisk] nacos:
Because Linux phones are not yet mature and Apple is much worse than Google.

Remember, whenever you don't pay for a product, you are the product.
[Magisk] VD171:
You can hide root to this app just using shamiko.

This app is also detecting hooks (code injection).
[Magisk] VD171:
Remember, capitalism is not the only way.
[Magisk] ragenstein1:
Hello. I hope you can give me suggestions/advice.

I will not be working with a SIM card. Wifi only.

I would love to use Xiaomi phones like suggested to me but it is not possible. Xiaomi needs SIM card to unlock bootloader :(

I am looking for suggestions for phones under $400 (new or used) which I can:

- Unlock bootloader without SIM card

- Root phone via Magisk (WITHOUT USING TWRP)

- Run these modules = LSPosed, SHAMIKO, XPrivacyLua, Universal SafetyNet Fix
[Magisk] nacos:
Well, microG solved this dilema for me 😉😁
[Magisk] locolyric:
for my case it also work for awhile, and it detect my root without any sign.
[Magisk] VD171:
Finally, LSPosed is fully refactored to LSPlant !

LSPlant is the new ART hook framework for LSPosed !

I've updated LSPosed to v1.8.0 and everything is working perfectly using Magisk v24.3 :cool:

LSPosed v1.8.0

Changelog:

- Add a new feature to only allow module classloaders to access Xposed API

- Fix language switch

- Support Android 13 DP1 and DP2

- Fix icon creation and resource hooks on ZUI devices

- Improve cache performance in XposedHelpers (Thanks @RinOrz)

- Fix parasitic manager in Android 8.1

- Fix module deactivation after reboot in rare cases

- Fix resource cache since Android 11

- Fix the first invoke invalid of hooked static methods since Android 12

- Refactor to use LSPlant as ART hook framework

Release 1.8.0 · LSPosed/LSPosed

Changelog Add a new feature to only allow module classloaders to access Xposed API Fix language switch Support Android 13 DP1 and DP2 Fix icon creation and resource hooks on ZUI devices Improve ca...

github.com
[Magisk] nicoco19:
Good evening,

I need your help please, I have a galaxy s22 ultra and I plan to root it, so I will be blocked by apps that will automatically detect that I have ROOT access (banking apps and others) . I saw that Magisk Hide no longer exists, it was replaced by Zygisk + DenyList right?

To be able to use my banking application after rooting my phone, I install the Zygisk module and in DenyList I exclude my banking application, right?

I'm new to Zygisk and DenyList

thank you in advance for your help
[Magisk] martyfender:
As

Per xda rules, please use English.
[Magisk] nicoco19:
Good evening @martyfender ,

I need your help please, I have a galaxy s22 ultra and I plan to root it, so I will be blocked by apps that will automatically detect that I have ROOT access (banking apps and others) . I saw that Magisk Hide no longer exists, it was replaced by Zygisk + DenyList right?

To be able to use my banking application after rooting my phone, I install the Zygisk module and in DenyList I exclude my banking application, right?

I'm new to Zygisk and DenyList

thank you in advance for your help
[Magisk] pndwal:
Possibly Zygisk modules.

You'll need Universal SafetyNet Fix, possibly Shamiko. (Read readme.md in zip archive for both) 👍 PW
[Magisk] VD171:
Magisk Hide does not have a replacement.

Zygisk is a replacement for riru.

If you want to hide root, you should install the wonderful magisk module: SHAMIKO.

Remember to add processes to denylist and DISABLE enforcing denylist.

Shamiko uses the denylist for hiding root.

But, if you enable enforcing denylist this will revert all magisk actions, including Shamiko module.
[Magisk] martyfender:
By

This new version bootlooped until I shut down and started up again on one of my 2 Onn 8 Android 9 tablets. After that each boot takes forever.

I just did a fresh twrp restore of it last week.

Shamiko, lsposed, hide my applist, usnf are used to hide
[Magisk] exis_tenz:
Hi - great news! I just have one question that is maybe not 100% related to the new release but more in general. When first installing LSPosed it gives you the opportunity to make a shortcut, quite as an app-icon. I use Apex-Launcher (old version 3.4.5) and had a box ticked which doesn't allow new apps to get an icon on the homescreen, so I missed "the making of the icon". Although I presume that this setting is the cause.

Is there any way to re-trigger this, so that I can try again? Every time typing *#*#LSPosed#*#* in my dialer is ... well ... not comfortable.
[Magisk] Lughnasadh:
"The API key used by YASNAC has a quota of 10,000 times per day. If the quota is exhausted, you will see an error and you will not be able to use it until the quota is restored the next day."

Try another one in the meantime, such as SafetyNet Checker.
[Magisk] BillGoss:
I've had the same error after updating to 24.1. But I've also had it pass successfully, so the error seems to come and go.

I've also checked SafetyNet using SafetyNet Test (https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettest) and it fails saying "fail (can't access Google Play Services)".
[Magisk] Lughnasadh:
See my post above about YASNAC.

Try SafetyNet Checker. https://play.google.com/store/apps/details?id=com.flinkapps.safteynet&hl=en_US&gl=US
[Magisk] ipdev:
It seems like everyone is checking their SafetyNet status today for some reason. :unsure:

Just kidding. I know why. :ROFLMAO:

Quite a few SafetyNet check apps are hitting their daily limit. 🙃

Cheers all. :cowboy:

PS.

Root Check app is also maxed out for today.
[Magisk] tom1807:
PlayServices is not checked anymore, but all is working. Running A12 on the Pixel 6

Cheers

Tom
[Magisk] darkerm:
is there any way to make Riru work with zygisk? and Lsposed?
[Magisk] doniedogawa:
I just updated Magisk from version 23 to 24.1 directly from the app on my LG V20 Oreo stock rooted ROM. After restart, it crashed like the attached one.

Maybe Magisk 24+ doesn't compatible with the ROM?
[Magisk] zgfg:
AFAIK, USNF 2.2.1 takes care of GMS - somebody reported that he passed SN with USNF although he did not put GMS to DenyList
[Magisk] zgfg:
Again, Riru is not compatible with Zygisk.

Use Zygisk-LSPosed - please scroll back, read previous posts (e g., where from to download)