yashsingh1/xdaforums huggingface dataset:
[Magisk] click2abubakar:
Thank you very much for the respons & confirmation. I pretty much figured out the same after googling for some time.

I have to use the Stock firmware, the only working solution I got to is to use the last Magisk released witout Zygisk.

Magisk 23 working fine for me, & am able to do hide root from banking & other apps.

Thanks once again.
[Magisk] pndwal:
Why can't you use current Magisk w/o Zygisk?... And please say why you need stock ROM... PW
[Magisk] click2abubakar:
I would need to hide Magisk from certain banking apps.

Can that be done without Zygisk in the current version?

I'd have loved to be on newer custom ROMs, but unfortunately after water damage, board (or something similar) had to be changed in my mobile phone. Although it shows my IMEI same as on my box, but IMEI has to be patched for the SIM to work.

The IMEI patch doesn't seem to work with custom ROMs. That's why I believe am stuck with stock firmware on this mobile.
[Magisk] zgfg:
There are zillions of posts how to attempt hiding the 'root', and it works for most of the banking and similar apps

In very short (I will not guide further bcs all that was really covered in so many posts - who is really interested should have search and read, even before asking), Zygisk, DenyList (not enforced), Shamiko, USNF mode, LSPosed + Hide My Apps

However, there is NO generic way that works for ALL banking apps. But one must try with this - and/or search in the posts for the particular app, does it require something more (like using Magisk Delta instead of TJW Magisk).or even something less complicated, or currently it's not broken yet
[Magisk] J.Michael:
Can you try installing the OS @pndwal suggested? And just return to stock if it doesn't work?

If you are not in a position to restore the current, working, system when a modification attempt fails, then you should not be trying to install Magisk.
[Magisk] pndwal:
Well you've got a point... w/o Zygisk-USNF you'd generally need Google Play Services droidguard process (aka SafetyNet process), com.google.android.gms.unstable, in denylist, and this requires working Zygisk too, as does using denylist as hidelist w/ Shamiko or DenylistUnmount modules... So we're gonna need something unusual...

Seems this module may be the answer:

https://github.com/HuskyDG/safetynet-integrity-fix

You don't need most of this modules functionality (fallback to basic attestation trigger and hardware verdict enforcement bypass triggers) as you don't have have a Hardware KA capable device... You do need an alternative to gms droidguard (SafetyNet) process in denylist however, and it seems this fork of USNF does/can hide root from this process itself (just like official zy-USNF) using Riru framework...

I'm guessing it should run (assuming you have Android 8) and fix SafetyNet and Play Integrity deviceIntegrity w/ Riru module installed for framework...

So the long answer is Yes, it probably can be done...

That's interesting... W/ new main board you'd have new IMEI number(s), S/N, and several other unique numbers, and these should simply work... I'm not understanding something here....

Do you mean no. on box for part, or for original phone?... Are you trying to use your original IMEI no. (numbers plural if dual SIM) for some reason?...

Can you give more info on what this patch does?... Can you link documentation for it?

Ta... 🙂 PW
[Magisk] click2abubakar:
For now I have everything woring fine with Magisk 23 installed.

It's a fairly old device, & so I believe that shouldn't be an issue though.

And as for the IMEI Patch, I'm not really sure what had to be changed in my mobile phone to get it working again.

I had a dual SIM Galaxy S7 edge (SM-G935FD), but after the repair work I've a Single SIM mobile (SM-G935F). The IMEI no. was the same as it was for the SIM Slot 1.

I've done a clean install using Odin, with NAND Erase & re-partitioning using the PIT file. The IMEI no. shows up fine when checked through *#06# or the Settings.

But the IMEI status is "NG" if checked using the code *#0011#. For the SIM to be working I've to root my phone & have a "IMEI Patch" done using a box/dongle (Z3X I believe).

Now I don't have that & for every time I've to get the IMEI patch I've to pay up a small amount. I've already got that done 4 times now :p

Once with the original FW, then with LOS 19.1 (which didn't work), & then I reverted back to stock & rooted using the latest Magisk, but as with that the root hide didn't seem to be working, I had to go for Magisk 23 & then get it patched one last time.

And as of now this config. is working fine. I'm a little disappointed that I won't be able to flash my phone with a newer Custom ROM as then my SIM slot stops working. I couldn't find any info for such a case where such IMEI Patch has to be done & Custom ROM installation.
[Magisk] pndwal:
Do you mean N/A?

Thanks for clarifying... Very interesting repair, especially as Sim can't work with stock setup or without root... Take it it's done by a non-official repair techie...

Seems it's not a full repair and he/she had to work around damaged hardware; guess patch is to bypass bad Sim slot & spoof SM-G935F model (using an IMEI modification) to allow remaining slot to work... Could be more to it too...

I'd be looking to upgrade to newer device, but I understand you've invested a lot in that one... 🙃 PW
[Magisk] m0han:
Fox's Magisk Module Manager v1.0.1 is here. The .apk size keeps getting bigger; 4.77 to 30.5 MB over 2 updates.
[Magisk] rodken:
Seems to be an issue with the v.1.0.1 force closing even after installing the device specific architecture and the universal version(s).

-- Uninstalling, clearing cache and/or data to no avail.

-- Reverted back to v.0.6.8 until further notice.
[Magisk] m0han:
I'm curious to know why there is a huge increase in size of the .apk 0.6.7 » 0.6.8. Do you or anyone else know anything about this?
[Magisk] rodken:
I haven't taken that into account as of yet. You can check the contents of apk file easily. An apk file is simply a zip file with different extension. Just replace .apk with .zip and unzip it. Then differentiate the contents with your previous .apk file and find out what file makes the difference.
[Magisk] avalx:
Well this bothers me a lot:

"In addition, Androidacy has temporarily take over releases, code, and issues while @Fox2Code works on his health. We hope to have him back fully soon!"

I will stay with version 0.6.7 for the time being.
[Magisk] m0han:
Yeah. I'm still on v0.6.7.
[Magisk] Lughnasadh:
Yeah, on my Pixel 2 XL I couldn't install any version of 1.0.1 without it force closing. Also cleared cache and data. Only v.0.6.8 working on it so far.

On my Pixel 7 Pro, everything is fine with 1.0.1.
[Magisk] Astur_Torque:
Hi! why dont you put a button with "select all" in the denegation list?

Is faster select all and deselect the few apps you have with root than the contrary...
[Magisk] zgfg:
It's wrong approach "select all, deselect few"

User has to know which few only to select

But sorry, select (almost) all if you wish - good luck with that.

You can find/read previous posts about (here and in Magisk general thread)

Btw, no developer reads here on XDA. If you want to reach them, report to Magisk GitHub, Issues

Or switch to Magisk Delta - it provides a similar option but must be used with cautious
[Magisk] Astur_Torque:
Ok, let me explain...

If you want to ensure everything works well, you should deny almost all, only allow those apps that request root.. because nowadays Netflix, mcdonalds, and a lot of stupid-nothing-to-do with-security-apps don't work with unlock bootloader.

I wish it only work disabling just google wallet and google services framework.. but unfortunately is more effective to disable all posible
[Magisk] zgfg:
I have less than 20 checked, over 60 not.

With Show System apps would be (guessing) 120 not checked.

And with Show OS apps, (guessing again) 200 not checked.

Still minority to be checked
[Magisk] J.Michael:
The point is we have been warned that putting too many apps in list will cause problems, so selecting almost everything is *not* the easiest way. Of course, that warning may be outdated, or it may be a matter of it works perfectly well at what it is supposed to accomplish, but everything runs more slowly -- that may fit in your "easiest". By all means, try it and report your experience.
[Magisk] casouzaj:
I always put in hidelist (or denylist) every app for which I have an account (username and pasword), which happens to be a lot of apps. Never had any issues. Used TJW`s canary before. Now in Delta canary, for many months. Just my 2 cents...
[Magisk] Lughnasadh:
With the update today (v 1.0.2), I can now install FMM and use it without it force closing on my Pixel 2 XL. Still working on my Pixel 7 Pro as well.
[Magisk] 73sydney:
Because thats a terrible idea
[Magisk] huskydg:
Maybe off-topic here, can anyone who has rootfs device, test this commit and send magisk logs?

Refactor magic mount by unsharing magiskd by yujincheng08 · Pull Request #6445 · topjohnwu/Magisk

Previously, magic mount creates its own mirror devices and mount mirror mount points. With these mirror mount points, magic mount can get the original files and directory trees. However, some devic...

github.com
[Magisk] huskydg:
I test this commit and face bootloop. Anyone who has legacy SAR can test this commit?

Eliminate unnecessarily copy on magiskinit by yujincheng08 · Pull Request #6444 · topjohnwu/Magisk

This patch reuses the abused /data tmpfs for magisktmp

github.com
[Magisk] pndwal:
Perhaps you didn't do this w/ pre 24.x Magisk?...

There were definitely limitations due to MagiskHide reacting "too slow"...If Magisk Daemon was hiding too many processes (hidelist process monitor implementation used Zygote ptracing and required passive 'Scan zygote multiple times' etc) it could lead to unmounting not occuring in time when critical files like framework were Magic Mounted which in turn would break the SafetyNet checking process (Google Play Service FC), and that could never recover until a reboot (or full restart of Google Play Service):

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

I've also mentioned that I don't know if Zygisk fully overcomes this, but it seems that whether using Denylist or hiding modules like Shamiko (Nb. This doesn't use denylist which must not be enforced; it simply utilises the (inactive) denylist for convenience but uses it as a hidelist together with its own hiding implementation) we may now have active hijacking of app_processes (Zygote) using Zygisk and no such issues related to the original ptrace method:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87582235

I'd say Denylist most likely does actively 'hijack' app's zygote now (why wouldn't it with Zygisk available?) and that Zygisk based Shamiko etc. would be doing the same for hidelist implementations...

What you may be missing is that the purpose of denylist is NOT hiding root (although it necessary hides basic aspects of root by reverting/denying Magisk modifications in listed processes)...

It actually seems to be aimed at Devs who use Magisk as a development tool, eg for production devices incl. security research... John said:

This and more here:

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

Further:

https://topjohnwu.medium.com/state-of-magisk-2021-fe29fdaee458

This blog makes clear that DenyList was a complete repurposing of the "minor subset of the MagiskHide infrastructure" that remains, and that for our key man:

... What you need for proper root hiding is a proper HideList solution like Shamiko. (Nb. It uses Magisk DenyList's list only!... It is implemented as hidelist; it does NOT use Denylist framework/API.)

The first Shamiko builds offered via GitHub offered whitelist mode, (hides root from most apps by default if enabled) and readme.md notes for whitelist don't mention anything breaking in this mode, but does note a "significant performance and memory consumption" hit, and that it should only be used for testing:

Notwithstanding the caveats above, it seems Shamiko (proper root hiding) in Whitelist mode (hides root from most processes other than those granted superuser permission) may really be what you want... I'm guessing you'll have performance issues unless your device is modern/fast...

I haven't tried whitelist in Shamiko; please report your mileage if you do... 😃 PW
[Magisk] pndwal:
Do these commits break Magisk w/ 2SI devices?... Do CI builds work?

Nb. This one has been updated again since you posted. (Latest 5hrs old)... New CI build available too... PW
[Magisk] huskydg:
1. It seems only legacy SAR (tested with others)

2. it seems rootfs "/" can't bind mount (check my review)
[Magisk] amk316:
hello everyone

i am sorry for posting a banking app root problem.

but i think its a new way of detecting root.

after updating albilad bank app it added a new "zygote" service no mater what i do it find my root.

any suggestions please.

https://play.google.com/store/apps/details?id=com.BankAlBilad&hl=en&gl=US&pli=1
[Magisk] 73sydney:
Downloading to test now...

I really ought to start charging for this service....

What do you reckon @zgfg ...could make a few $ :)
[Magisk] 73sydney:
Update:

Tested using:

- Magisk (official) 25.2

- App in Deny List

- Shamiko (Deny List NOT enforced)

- App in Hide My Applist

Result: Unsuccessful and also its not just you

@zgfg may test for you under Magisk Delta if he feels like it
[Magisk] pndwal:
Seems fine for me w/ only denylist entry!

Xiaomi RN8T w/ A10 MIUI, Magisk Canary, Magisk App hidden, app in denylist (enforced)... and Play Integrity deviceIntegrity passing of course... 😝

So you wanna charge for that service?!...

I'm now offering tuition for a small fee... You can pay me by DinersCard, Visa, MasterCard American Express... I know it'll be American Express though... (Regards to Crispin, n glad he's finally out of hibernation)... 😁 PW
[Magisk] zgfg:
I may try over the wknd. Currently busy by watching The Playlist on Netflix. Then comes World Cup

Joke aside, I have managed to bypass MD* but I have troubles when rebooting, that's why I need to sustain from rebooting (like needed upon putting a 'banking' app under test to MagiskHide list and HMA)
[Magisk] AndrzejDwo:
You should pay us for reading your answers, not this one particular but most of them are like tl;dr stories, I thought of reading it to my kids for sleep as fairytales xD

cheers
[Magisk] pndwal:
Is that fair?...

I try to post relevant information that may not be generally understood (or even popular) here, and to present it clearly...

Can't help it if some don't wanna learn nuffin... PW
[Magisk] pndwal:
https://github.com/topjohnwu/Magisk/issues/6443#issue-1496561375

Official Magisk no longer includes proper root hiding, and issues related to hiding root from bank apps won't be entertained in GitHub issues... Please see this post (just the middle bit) for clarity (or don't... Your choice...):

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

... Also, you didn't read instructions about posting Magisk issues incl. Magisk version, logs etc...

Anyway, aside from taking Hide The Magisk app (possibly), adding in denylist and deviceIntegrity pass, this app needs a proper root hiding solution... Shamiko does the trick for me:

Xiaomi RN8T w/ A10 MIUI, Magisk Canary, Magisk App hidden, app in denylist (NOT enforced), Shamiko,... and Play Integrity deviceIntegrity passing of course... 🙂 PW
[Magisk] 73sydney:
I just retested using that setup (turned Shamiko off, Enforced Deny List), and made no difference here (though as previously mentioned my device shows SU, Busybox and Magisk File under Ruru (Abnormal Env)....maybe yours doesnt)

Is there a moneyback gaurantee on your Masters Degree In Applied Pedantry?

I bet you still accept payment using one of those credit card roller devices....

The Bear says hi, you just put him back on the map, he's so needy
[Magisk] mortenivar:
Yes, I was a little flippant about reading the instructions ...but sometimes flippancy pays off - you solved my problem! Shamiko did the trick. MitID is working now. Thank you very much, pndwal!
[Magisk] pndwal:
... You're really gonna pay, aren't you!(?)... You'll have to get ink off your card, but won't be sorry. 😜 Go cuddle ya bear mate... PW
[Magisk] zgfg:
I'm not gonna pay but my Ruru is clean except for not liking Accessibility services turned on - I don't like either but need for AndroidAuto
[Magisk] 73sydney:
As i suspected, youre not being detected on a few key things i am....must be the props on that wonky device of yours :)

Or mine :)

The Bear wants to say he is coming out of retirement for pre-Xmas coffee drinks next week at his local cafe in Darlinghurst, and one of the people invited has no idea he's making an appearance, he's looking forward to that.....twisted little b#$t@rd
[Magisk] pndwal:
But did you bypass the app detection?; I expect you will, but this was just to help the Style Master eliminate what doesn't matter...

And I do know some ways to clean mine further... Just don't wish to make manual edits... PW
[Magisk] pndwal:
Hope you can fix yours... Last time yours succeeded/ mine failed... Detection can be very much per device / OEM / android version... Realme seemed to have least issues, followed by OnePlus(?) very generally and traditionally speaking ...

😑 PW

(Better put other matters in the ponkle / tl;dr basket...)

Guess you two are twins then?...

At least supply more photos mate... 😆
[Magisk] 73sydney:
Oh you mean that day my S20+ was cleaner than your device, and i theorized the end of days was upon us? Fun times....

I dunno why i get flagged for SU, and Magisk files....(BusyBox yes, because i have that module installed), not that it stops anything i have from working...
[Magisk] pndwal:
They are...

@osm0sis Busybox NDK?... I have it too... PW
[Magisk] 73sydney:
Yeah, same BusyBox module, used it forever

Weird how you dont get flagged on that, i can toggle it off and pass...

Might be time to give Delta another bash and see what differences there are, i flip and flop every now and then
[Magisk] pedroandroid:
Hello guys!

Sorry to bother you with this problem too, but C6 bank added the zygote thing too, and I need this bank app. So I've tried everything in this morning and I couldn't find a way to bypass this. Can anybody help me please?

Appreciate!!!
[Magisk] casouzaj:
I don't use the C6 Bank app, but I have other banking apps installed, of which, the most annoying of all is Banco Pan, and all of them work. I have a Sony Xperia XZ2 phone, running LineageOS 20.0, rooted through Magisk Delta Canary. Zygisk and MagiskHide are turned on. SuList is turned off. All the processes from all the apps, for which I have to provide credentials to access them, are ticked in MagiskHide list. Besides, regarding PI tests, I have the latest USNF-mod and Shamiko v0.5.2 (120) - because the latest Shamiko causes general crashes for me - modules, and banking apps are also hidden by HMA.
[Magisk] AndrzejDwo:
i tried to launch it on my s21 running A13, without any luck unfortunately. my current setup is:

latest magisk canary,

shamiko,

hide my applist

Magisk app is hidden and your bank app is added to denylist which isn't enforced - it whines about device being insecure, after hiding my applist it doesn't even launch - FC's immediately.

I tried also with stable hidden magisk and forced denylist but it detects root as well.

Freezing Magisk with IceBox doesn't work either.

I'm out of ideas.

My device is certified, passes needed integrity checks and ruru can't find anything abnormal.

Let us know if you find any fix for this.

Cheers

btw, I have my bank and google wallet working just fine...
[Magisk] AndrzejDwo:
no luck for me with setup mentioned above 🤷
[Magisk] pedroandroid:
Maybe is something regarding twrp? Maybe this can identify the modified recovery? Bcs I cannot think in anything else.
[Magisk] pndwal:
... Is yours 1.34.1? PW
[Magisk] J.Michael:
Do you have USNF fix?

If you have TWRP, did you try renaming the TWRP directory?
[Magisk] AndrzejDwo:
yes, i have usnf mod by displax and twrp folder renamed to "1"
[Magisk] 73sydney:
yes

meanwhile just did the update to December on the Pixel 6 Pro

Plusses (thanks to @roirraW "edor" ehT posted method) -

easy:

Spoiler content hidden.

Minuses-

Lose Play Certification, which of course means i have to clear data, which means of course i have to reset the Watch 4 again...and of course Samsungs backup on Watch 4 is almost non-existent, so there goes an hour.....

Edit/update:

Other minuses (found and mentioned in newer post):

- Lose Wallet in notification pulldown - Google Play Services goes a bit screwy after clearing data to re-certify after new magisk patched image flash

- Lose ability to copy Google account to Watch 4 during Watch 4 reset up

So may as well just clean install....

Every month....
[Magisk] ipdev:
Turn on airplane mode before the update. 🤔

That should let you set up Magisk again before anything is checked/updated. 😉

I do mostly the same steps but, it depends on the device.

I have been bitten in the butt a few times by prepatching the boot image. 😉

- I normally patch the new image after booting the update (with airplane mode on).

- Then test boot (fastboot boot) the new patched image, if it works, then install using the direct install option.

- If I can not test boot it, I flash it and see what happens. 😁

---

If you want to go all in. 😛

Replace the -w in the flash-all script to --skip-reboot.

That will leave you in fastbootd (fastbootd mode) after the update finishes.

Simply add a line to reboot back to bootloader.

Then you can test boot or flash your prepatched image.

Make other changes (like before when we had to disable vbmeta on Pixel 4a 5G and above) before the initial boot of the update.

Example of updated flash-all script.

Pixel 7 - [ GitHub ] - Link

---

I finally got around to unlocking, rooting and updating my Pixel 7.

It has been in the pile on my desk for about two months now. 🤔

Bought it on when on sale since I also had some PlayStore credit to use or loose.🙃​

I ran the updates in order.

I did not jump from September to December.

I ran the Oct. and then Nov. updates.​

Since I have to patch the init_boot.img, I can not test boot (fastboot boot) it so...

All In. method.😛

I prepatched the new init_boot image and...

What ever happens happen. 🙃

If anyone wants to see the process I use on my Pixel 7.

Update Nov. -> Dec.

Pixel 7 - [ Pastbin ] - Link

Normally I do not list (or change to) the directories.

I did more for the example of what I was doing instead of just calling the directory and file.

Normally I use ../PullPixelBoot.sh and fastboot flash init_boot boot/magisk-25205-init_boot.img instead of changing directories or copy from one to the other for example.

I know some do not like PastBin but, I got use to using it years ago for reporting issues.

Mostly for a now retired "Moderator Emeritus / Senior Recognized Developer". 🙃​

Cheers all. :cowboy:

PS.

For reference.

The fastbootd (fastboot_d) mode (for the lack of a better description) is a low level recovery.

This mode allows flashing secure (critical) partitions that are not available to flash in bootloader.

Years ago..

Pixel 2XL, OnePlus 5T and some other devices supported unlock critical that allowed flashing secure (critical) in regular fastboot (bootloader).

This shift to fastbootd never made sense to me because what is more critical than being able to flash the actual bootloader. ¯\_(ツ)_/¯