yashsingh1/xdaforums huggingface dataset:
[Magisk] VD171:
Yes, all detections of the Momo app are really excessive.

But, some detections are really necessary.

I mean, some newbies and kids need to be avoided.
[Magisk] VD171:
Xiaomi Redmi Note 9:

Spoiler content hidden.

Spoiler content hidden.

Samsung Galaxy A10s (mediatek):

Spoiler content hidden.

Spoiler content hidden.

Samsung Galaxy A01 (snapdragon):

Spoiler content hidden.

Spoiler content hidden.
[Magisk] HippoMan:
Furthermore, all detections by banking apps, games, and all other apps, for that matter, are excessive. Oh, and that also includes all detections by Google itself.

This cat-and-mouse game that has been forced upon us is a huge waste of human productivity.
[Magisk] locolyric:
one of my banking app just update and it bypass the deny list .

i use the hide my apps modules ,it seems not working . xprivacylua method , failed too.

any move to hide it ?
[Magisk] zgfg:
SP Flash Tool is for MTK (only), isn't it?

And your Redmi Note 9 is MTK

I have two Xiaomi phones, but both with Snapdragons: Mi 9t and 11 Lite 5G NE

Anything similar possible to do with Xiaomi Flash Tool or one would need to go for EDL (it requires paid support)?
[Magisk] VD171:
For Snapdragon devices, I'm using fastboot only.

I'm not familiarized with Snapdragon devices.

I don't know how to write specific partitions to Snapdragon devices.

Snapdragon devices doesn't contain seccfg.

For snapdragon devices, the unlocked state of the bootloader resides in the partition

devinfo

.
[Magisk] VD171:
About snapdragon devices, I've found two softs, "EMMC Block Read Write V2.0" and "Qualcomm Premium Tool V2.4".

So, we can do same on snapdragon devices, just using the partition devinfo instead of seccfg.

But, at the moment, I neve tried no one of the softs.

Naija ROM - Database of Mobile Firmware (Flash File)

Naija ROM is one of the reputed Mobile Firmware Websites, providing 100% original (stock) firmware along with the Tools, USB Driver, and How-to install Manual.

naijarom.com
[Magisk] dr4go:
Do you know anything regarding Exynos' in that regard?
[Magisk] exis_tenz:
Guys, I'm overwhelmed by all the reactions and testing to my Cupra / Volkswagen app. As one said "I'd never buy a Volkswagen". No matter if you drive an Up or a Phaeton (between 10k USD and 70k USD) - image the factory decides to block your app (which IS a functionality to the car). Ridiculous.

Anyway. I have 2 devices, a OnePlus 7 pro (Qualcomm) and a OnePlus Nord 2 5G (Mediatek). Both have the same setup:

- Stock A10 (OnePlus 7 pro) and Stock A11 (OnePlus Nord 2 5G)

- Rooted with Magisk

* Zygisk

* Cupra app on deny-list but deny-list not enforced / activated

* Shamiko running

* Universal SafetyNex Fix 2.2.1 installed (I -DO- pass!!!)

* Zygisk LSPosed

--> in LSPosed have XPrivacyLua activated and blocked add-info and whatever more sounds reasonable

User VD171 managed to pass by the root-detection, but I still do not get HOW. I have all the settings as he suggest (only used the latest Shamiko 0.4.4) and the rest as above. VD171 suggest a few thing, there is one thing I do not understand. How to

DISABLE

Enforcing DenyList??? Where is that setting?

XPrivacyLua also installed and almost anything that makes sense faked in that Cupra app too, without effect :-(
[Magisk] zgfg:
Ok, thx.

On Mi 9T, MIUI 12.5.2, A11, Snapdragon 730, I have devinfo, no seccfg but also no nvdata

devinfo would be both instead of seccfg and nvdata?

Attached Terminal screenshot from Mi 9T, and Blocks txt with the full output

PS:

Attached also blocks1.txt from Xiaomi 11 Lite 5G NE - (devinfo instead both nvdata and seccfg?)
[Magisk] dr4go:
twrp folder, usb debugging, oem toggled... could be so many things...
[Magisk] exis_tenz:
I've renamed TWRP-folder, tried USB-debugging, tried OEM-toggle (I'm not an expert, would say "user with experience" and the whole cloaking bootloader-thing is out of my league.

VD-Info tells me that on my OnePlus 7 pro my bootloader is locked, by the way, but it's not. On the OnePlus Nord 2 5G it's definitely unlocked, although I do not carry that device today.
[Magisk] VD171:
I have no ideia.

I suggest you to search about how to dump and write to eMMC on exynos.
[Magisk] VD171:
Nvdata is just where resides some infos, like "the device is locked? true/false".

But the partition seccfg really opens the door.

So, nvdata doesn't require any modification because it may change according to your actions.

(For an example, if you enable mock location on developer settings, something on nvdata changes from "false" to "true".)

Seccfg keeps unmodified forever even if you format data or update the firmware.

Seccfg modifies ONLY when bootloader is unlocked or relocked.

I mean, just unlock the bootloader, backup the partition devinfo, backup data, relock bootloader, format data and restore the partition devinfo.

Done, you got unlocked bootloader and kept oem untoggled.
[Magisk] zgfg:
When using Shamiko, Enforce DenyList must be off.

Setting as on the screenshot
[Magisk] exis_tenz:
Thanks, will test and try!
[Magisk] VD171:
1. Be sure you are rooted, try to grant root to any app and see if root is working perfectly.

2. ENABLE zygisk and DISABLE enforcing denylist.

3. Enable CUPRA processes in denylist. Remember to enable ALL processes, if there are more than one.

4. Install/enable shamiko module.

5. Reboot.

Done :)

Shamiko uses the same list of denylist.

So, shamiko is enabled only for processes enabled on denylist.
[Magisk] exis_tenz:
This is exactly my set-up (and has been all the time). I can't figure out why you can start this Cupra app without getting a "root detected" warning and I can't.
[Magisk] VD171:
Are you using a custom rom?

Is selinux enforcing?

Is mock location enabled?

Probably there are some other issues not covered by shamiko.
[Magisk] heinhuiz:
Did you try removing it from XPrivacyLua? Maybe it just detects an uncommon value, like an empty apps list or an Android id set to all zeroes...
[Magisk] VD171:
@heinhuiz is right, eventually XPrivacyLua hides more than the enough.
[Magisk] exis_tenz:
No, Stock Android 10 (OnePlus 7 Pro) and Stock Android 11 (OnePlus Nord 2 5G).

Selinux enforcing - I don't know what that is, out of my league, if you can tell me where to check that, I'll report back.

Mock location is not enabled - well - not for Cupra app. My navigation, maps, radar warners etc. all work fine.
[Magisk] VD171:
You can check selinux using my app VD Infos:

https://xdaforums.com/t/app-v1-10-vd-infos-package-com-vitaodoidao-vdinfos.4097379/
[Magisk] zgfg:
Terminal app, commands:

su

getenforce
[Magisk] VD171:
Checking selinux doesn't need root.

There are many ways for checking selinux, getenforce is not the best/recommended way on android.

My app VD Infos checks all ways for checking selinux, just try and see :)
[Magisk] VD171:
@exis_tenz as you can see, cupra app is working perfectly using shamiko & universal safetynet fix.
[Magisk] exis_tenz:
I suppose you take my car than ;-)

It keeps telling me it detected root. Have cleaned cache, rebooted, danced on my phone, nothing seems to do the trick.

Would it help if I send you an analyses of your VD-app?

Just to be sure: the app WORKS on my phone (after I tick the box to confirm I am rooted). The thing is, when the app DETECTS root, it works, but after the set-up it limits the options. That's why I want to hide root for it.

Not easy fighting big companies like Volkswagen :)
[Magisk] pndwal:
mmm. But bank apps are using 'excessive' detections for their own surety in the face of a SafetyNet API that Magisk, USNF module, Proton kernels etc have frankly (and easily) made a joke of.

Seems to me Momo's 'excesses' may equal the bank's 'excesses', or they will tomorrow... For instance I could hide 'root' from Sparkasse PushTAN app till recently, but now it detects it on my MIUI device. Other (non-MIUI) devices can still hide it easily.

One difference is that Shamiko is hiding Bootloader Unlock on these devices using Momo detection... Momo on my RN8T shows 'Bootloader Unlocked', whereas VD Infos says 'Bootloader: Locked'...

Yup, but way back in 2016 he said Safety Net is The Already Lost Cat-And-Mouse Game, so the game was apparently not hiding root (Shamiko's realm); it was subverting SafetyNet, or 'Googles security model' 😛, and banks were not the Cat... (Google was):

This game may well be as good as lost with inevitable HKA full deployment, but for now the game has changed, and the prowling Cats are the banks.

This is true, but bank apps are closed source... And (speaking of God) so are Momo Chiyoda and her nemesis Shamiko ('the demon girl next door', Shadow Mistresses Yuko Yoshida)... 🤔 PW
[Magisk] VD171:
SafetyNet can be fixed easily.

I have exactly 473 apps installed and NO one checks safetynet.

Yes, the game now at 2022 is hiding root. Just read v24.0 and v24.1 notes:

Releases · topjohnwu/Magisk

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

Any java app can be decompiled using reverse engineering.

It can be obfuscated, but if you have some time you can deobfuscate anything.

You just need time and dedication.

About "linux kernel is open source" I mean, you can build your own kernel and flash it to android :)
[Magisk] B3!CrAZy:
I have a weird problem - i can pass SafetyNet, banking apps are working, i can start google pay, BUT i can not add card. When i am trying to add card and i am about to do last step google pay is giving me "black screen"..nothing is happening and i can not click on anything and card is not added. What to do with this?
[Magisk] dboechat:
I've been trying to root my Galaxy S9+ Snapdragon for days now, without success. I do everything as explained in the tutorial, but my device just bootloops after flashing the patched AP file.

Any ideas?
[Magisk] pndwal:
Are you flashing AP file on its own?

What is your Android version?

Despite John's statement in Installation Instruction page "If your Samsung device is NOT launched with Android 9.0 or higher, you are reading the wrong section", (yours launched W/ 8.0 Oreo), if you've updated to 10+ you device has actually been 'converted' from a boot-type 'Legacy ramdisk' to a '2SI ramdisk SAR' (as John calls it; Google doesn't call it SAR) device, and as such you should now be following the section for "Samsung (System-as-root)".

https://topjohnwu.github.io/Magisk/boot.html

This means (Assuming you do have Android 10+) you should be flashing all components mentioned incl. CSC, not just AP, for full data wipe with initial Magisk installation. Nb. "Never just flash only AP, or else Odin may shrink your /data filesystem size".

👀 PW
[Magisk] dboechat:
Thanks for your reply.

I'm on Android 10. Doing as said in the section for "Samsung (System-as-root)".

I can't root GSI roms either.
[Magisk] pndwal:
GSIs are not supported by John AFAIK... There's work being done by others however....

See

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

https://github.com/topjohnwu/Magisk/pull/5146

https://github.com/LSPosed/Magisk/commits/2si

PW
[Magisk] vandyman:
Magisk Canary 24301 is working well on my P6.

I see a lot of people are getting bootloops.

Is it because of using Magisk 24 on older devices? The last time I had a bootloop was back in Oct/Nov when starting out with the P6.
[Magisk] m0han:
i think bootloops/issues are reported by people using (stable) Magisk 24.3. maybe android version is also involved. i've upgraded to Canary Magisk (2c092ffd) (24301) without issues on poco x3 running aicp a11 rom.
[Magisk] zgfg:
Xiaomi Mi 9T

MIUI 12.5.2, A11

Magisk Canary 24201 updated to Stable 24300:

Patch and flash

Zygisk, Shamiko, LSyposed

Update went smoothly, no problem whatsoever on my side

PS: Now switched from Stable 24300 to Canary 24301 (usually, Stable 000 and Canary 001 are always equivalent), srill everything ok

---

PPS

Xiaomi 11 Lite 5G NE

MIUI 12.5.8, A11

A/B device with Ramdisk Recovery in Boot partition (no separate Recovery partition)

Magisk Canary 24201 updated to Canary 24301:

Patch and flash

Zygisk, Shamiko, LSyposed, USNF

Again, update went smoothly, no problem whatsoever on this phone either

---

PPPS: @pndwal, now indeed hiding& restoring works smooth again (MIUI)

Btw, I give permissions in advance (to avoid any surprise):

0 byte folder on MEGA

mega.nz

I keep MIUI Optimization as enabled by default
[Magisk] Nekromantik:
Anyone had any sucess with HSBC Kinetic Banking App working with Magisk?

Im using latest magisk with Zygisk and hidden Magisk manager but still the app says device modified.

I have a Pixel 6 Pro running A12.
[Magisk] Stillhard:
Latest Magisk Canary + USNF + Good old Shamiko v0.2.0-59 + LSPosed + own xposed module
[Magisk] Nekromantik:
you made a module?
[Magisk] Stillhard:
Yes, just for fun ;)
[Magisk] m0han:
good that you didn't run into issues (i didn't too). both your devices are on a11 (mine too). i also said "maybe android version is also involved". let's hear from a12 folks too.
[Magisk] Evle:
Can't get zgisk enabled !?
[Magisk] BillGoss:
Did you reboot the phone after enabling Zygisk?
[Magisk] lm089:
Hi all,

over the last 2 days I tried to update Magisk in two of my devices from 24.1 to 24.3 using the in-app update functions.

On device #1 (OnePlus6 with latest stock OOS /A11) ithe two-step update worked as expected.

On my old Sony XPeria Tablet Z (running LOS 16 / A9) the apk update worked. But trying to update Magisk itself (always using the default settings an choosing "direct installation") constantly fails telling me "Installation failed - Unable to detect target image" And that's it. Also nothing to that point in the Magisk log.

Magisk 24.1 is still running fine, I am rooted, zygisk and ramdisk are active (see screenshot). Any recommendations what I could do here? Should I start from scratch like uninstall then re-install?
[Magisk] Stillhard:
Good news? Get it from here
[Magisk] lm089:
Hmm - would you care to elaborate? Doesn't mean much to me, I'm afraid
[Magisk] Evle:
I did .
[Magisk] pndwal:
He means you can try test (actions run) build for Shana's new "Use /data as tmpfs mount point in 2SI setup" to inject magiskinit fix from unofficial service that bypasses need for user to have GitHub login.

If you wish to try this, I would read through the two linked issues addressed by this fix, log in and try test build officially hosted in artifacts for actions run here:

https://github.com/topjohnwu/Magisk/actions/runs/1976306281

However it seems this is a fix for devices using 2SI boot. Your older device would be converted to 2SI (two stage init) if updated to Android 10, but on Android 9 I believe device is still using legacy ramdisk boot, so I'm not confident fix is for you...

Have you tried to do initial patch / flash a boot image again?; Could be that your image backup, magisk db or something else has gotten messed up... PW
[Magisk] lm089:
Thanks for making this clear. I'll try what you suggested as soon as I find the time
[Magisk] lm089:
So I tried in various variations, but no success:

1. Patched then flashed boot.img from updated magisk.apk v 24300 incl. checked vbmeta > back at system I am constantly told that I need to reboot one more time to complete setup. This repeated no matter how often I reboot. Also zygisk is never active

2. Restored a recent backup with magisk 24.1. Then patched boot.img to v 24.1. Flashed that. Back at system everything is fine with v 24.1

3. Tried to update again > same result as above (1)

4. Tried to uninstall magisk from the app but I can't as I receive a "cannot mount /data" message

5. Tried to uninstall from recovery > same error

I give up. As long as 24.1 is working for me...
[Magisk] J.Michael:
What backup did you restore? If it was a backup of a system that had Magisk 24.1, why did you then patch a boot.img with Magisk 24.1?
[Magisk] pndwal:
Also, I'm still suspicious of your db, image backup etc...

If you delete all contents from /data/adb (can delete /data/magisk_backup_xxxxc folder(s) also, but don't uninstall the Magisk app) Magisk setup will be rebuilt on reboot. Nb. You'll need to note / reinstall any modules you need after this.

See if you can update app and take Direct Install to update Magisk successfully after this... If not, there may in fact be some regression / bug affecting your (very old!) device. PW
[Magisk] lm089:
Because direct install fails for whatever reason. See post above
[Magisk] pndwal:
What he's saying is that backup alone (assuming it includes boot image) should restore system with Magisk; He's asking why patch boot image already patched (restored from backup) w/ 24.1 Magisk... Or is it only a partial backup? PW
[Magisk] lm089:
Full backup was taken over the weekend, with an (apparently) fully working magisk 24.1 boot image

I did. Modules were only acc and safetynetfix. No probs to restore. There was a multitude of backups, though. I checked them, they wer all created last night when I had tried to flash my patched boot image[/QUOTE]

Unfortunately, still not working, direct install is giving me the same error as before. For the moment I don't care to redo the patched boot.img path,I doubt it'll work.

You're perfectly right, the device is very old, indeed (and I'm kinda proud of it). There's no real need for me right now to update. So many thx for your patience so far. I'll keep watching this
[Magisk] lm089:
It's a full backup with a working 24.1. You're right, I might as well stick with that version (see my other answer just posted 5 minutes ago)
[Magisk] m0han:
This post is targetted at A12 users mainly. But, all those capable of resolving such issues are welcome to help out. @zgfg, @pndwal, @Eng.Raman are a few names that spring to mind :D ;)

After I upgraded my phone OS to A12, the situation is as follows:

1. Applist Detector finds 'xposed hooks'

2. Magisk Detector says 'unexpected' for init.rc modifications

3. Oprek Detector finds 'Apps with Root/Xposed access'

4. Momo finds (i) 'xposed framework', (ii) 'data not encrypted', (iii) 'running custom rom' and (iv) 'bootloader unlocked'.

4 (ii) and (iv) should be accepted, I guess (data/device not encrypted now, bootloader is unlocked as before). 3 seems to have resolved on it's own after I flashed LSPosed-v1.7.2-6459-zygisk-release.zip this morning. I can't recall having done anything else.

In A11, I was having GravityBox and HMA modules; yet there were no reports in any of the above apps regarding anything related to 'xposed'. No GravityBox yet on A12. My device/data was encrypted on A11 - so that 'not encrypted' message was not presented. But, my device was running a custom rom then, as now; however it was not reported by Momo. TBH, I can't figure out how to get 'all clear' in my current A12 setup. Any ideas? Thanks in advance.
[Magisk] pndwal:
Does seem more and more like a regression... It would get attention (in due course if not immediately) if you open an issue ticket (must submit logs using latest Canary; it's the debug version having verbose logging) as Magisk is supposed to support devices running Android 5.0+... I would open issue and wait... 😛 PW
[Magisk] lm089:
Just d/l'ed latest canary build from the github site. Before I start off, as I've never installed anything but official builds here: do I first have to uninstall the official apk, or can I just install the debug version over the existing one? Should I remove modules first? Anything else?
[Magisk] pndwal:
Canary is official, just debug, not 'public' version!

No, apk should install fine over public version; uses same (topjohnwu) signing... Just be sure to restore app if you chose 'Hide the Magisk app' from Magisk settings first... Modules should be fine since they're not apparently causing your issues... 👍 PW
[Magisk] Sonyislam:
My magisk also says no ramdisk but it works normally with all the modules i've installed, everything works fin..how to fix magisk ramdisk ...
[Magisk] zgfg:
If everything works fine do not bother that for (supposedly Xiaomi?) Magisk app says Ramdisk No

You cannot 'fix' on your side - it should be potentially fixed only in the ROM's boot.img or in Magisk (when it patches, it recognizes and says that Ramdisk was found but nevertheless it later displays in Magisk app as Ramdisk No)

You can open an Issue on Magisk GitHub but it will be probably shortly closed with a comment that your ROM/boot.img is not by standard or something like that

Again, don't bother with that detail

PS: I suppose you are not talking about "Zygisk No" but really about "Ramdisk No" as you wrote - small details may highly matter

"Zygisk No" would be a problem, though
[Magisk] lm089:
Alright, installed the debug / canary version now (running as 2c092ffd (24301)). Rebooted device, then hit the "update Magisk" button. Update failed, as it did before. The output after the failed update again is only the same 2 lines. Looking at Magisk's default log everything is as before,nothing extra. Am I looking at the wrong place?

Yes I'm aware that I'm supposed to post a bug report @ Magisk's git. But I'd be happy if I knew beforehand what to look for 😉
[Magisk] zgfg:
Sorry, didn't follow what was the original problem, just two cents:

If you go to report the Issue, you must be using the latest Canary (otherwise the bot closes your Issue with no word)

Magisk logs are in /data/cache, magisk.log and magisk log.bak files - but root is already required (or TWRP) to access
[Magisk] lm089:
Thanks. Found both under /cache. But content is extremely dim: only three lines in magisk.log. And, what's worse: every attempt to update Magisk still fails. So the log still runs as stable version v24.1 (24100). So it looks as if I was in a dead end then, as I cannot "prove" what is going wrong...
[Magisk] zgfg:
Hmm, you can try. Declare that you're upgrading to the latest Canary but it fails

Btw, do you have the boot img to patch (if not on Samsung), did you try to patch - does it also fail, and what it reports in the box?
[Magisk] lm089:
Maybe I should try, although I doubt that this is really worth it: it's a really old tablet device (got it late 2013), it's running on LOS 16/A9, and apparently it's no longer maintained (last update is 6 months old now). Magisk 24.1 is the last version that I could install and run.

Here's the beginning of this story:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/page-55#post-86568253

And here's what I tried in terms of patching boot image etc.:

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

Thanks again to anyone here trying to help
[Magisk] zgfg:
Pie should be still ok.

Can you zip your boot.img and attach (hopefully on your old device it's no bigger than maybe 16 MB) or put to the clouds and provide the link
[Magisk] lm089:
13.5 MB to be exact ;)
[Magisk] zgfg:
Here you come
[Magisk] lm089:
thanks! will give it a try tomorrow
[Magisk] lm089:
Thanks again for your effort, but that patched image got me into a bootloop right at the Sony logo. I'm back at restoring my last full backup (incl. M 24.1). - Time to go to bed, before I start making unrecoverable mistakes :D
[Magisk] pndwal:
I think patching images should be done on at least a similar device / Android version.

In this case boot image is from device w/ Android launch version 4.1.2, and even w/ running version 9.x, Magisk is still using legacy ramdisk to boot (not SAR or 2SI) and certainly device won't be compatible with ABI arm64-v8a detected...

I'm not certain of all the implications of patching on an unmatched device, but I know there are a number of cases in Magisk discussion thread where users got bootloops, even by pre-patching an OS update's boot image on the same device w/ Android x before taking the update to Android x+1 and flashing. Same users had success booting images patched from system w/ Android version matching running version for Magisk however...

Installation instructions assume patching using the same device, and I'm quite sure using a device with non matching ABI, boot type, etc, will be problematic, not to mention handling of per device configurations for compression, hexpatching, vbmeta, verity, forceencrypt etc . 😬 PW.