Magisk General Support / Discussion

Search This thread

pndwal

Senior Member
It was not like that.

I was just answering the same questions over and over mentioning exact link for libencrypto and people asking me what I used ...
and I felt you only want to answer some questions as I had to ask more than once... 🙃
then I specifically wrote mods I use and still got questions for that it seemed to me like I am going in circles so I just asked if that was not understandable the first time? There was no frustration from my side...
But you hadn't clarified... maybe in your mind...
In my first post I wrote: "I am using Samsung Galaxy Note 20 Ultra 5G, Android 13 November update - original firmware rooted with Magisk + Universal Safetynet + Zygisk ..." - Not sure how more clear I could be than that
Since you're still not letting go of assumptions I'll explain further, despite it being a circular argument... 😝

If you check Google Pay discussion thread you'll see many members had USNF + added a mismatched fingerprint (globally applied) using MHPC long before @Displax's USNF mod w/ (partial) Play Integrity fix (which does the same thing but targets gms) even existed (and @Displax was watching these developments in that thread), and that many continue to use this setup... You DID NOT state you had @ Displax (targeted) mod EVEN WHEN ASKED, and as you said you used MHPC in conjunction with USNF it appeared that you were likely passing deviceIntegrity verdict this way, like many others... - Not sure how more clear I could be than that...
... I also wrote that in this setting I am using Netflix with no problems but other streaming apps are not working ... they only work with that additional mod which loweres the streaming to L3... Really not sure how more clear I could have been - maybe next time :)
I already covered why I wasn't sure you actually had L1 at that point since you never stated that plainly and you only said "Netflix is ok" (many users consider Netflix works fine w/ SD having never had L1 compatible hardware anyway)... Further, you didn't state how you were seeing "it goes to L3 with bad quality streams" despite my asking. (Thinking: 'perhaps you see L3 somewhere (where?) but never actually had L1 since streaming didn't even work w/o liboemcrypto-disabler mod')...
... I also wrote that in this setting I am using Netflix with no problems but other streaming apps are not working ... they only work with that additional mod which loweres the streaming to L3 which is basicly what that mode does...
Well that's not really the purpose of the mod...

Actually the mod simply masks liboemcrypto.so library, and L3 is just a consequence...

Apps can use liboemcrypto.so for decrypting both SD and HD streams, but the library is required for HD... Apps can fall back to other libraries where liboemcrypto.so doesn't exist but HD streaming will fail as will L1 security check...

It seems that affected apps are not allowing liboemcrypto.so use for ANY streaming and root detection (or possibly even detection that existing hardware for TEE decryption exists and should be used... Could be using model / other props with their own model whitelist too...) seems to be the likely reason to me... Ie. it's likely that these apps are simply restricting their use to SD decoding with older libraries (as liboemcrypto.so is primarily designed to decrypt HD content in secure TEE OS) rather than preventing apps from working on devices w/o hardware TEE...

Netflix does this too BTW, but relies wholly on Widevine certification since v5.0, making their approach much simpler...
... Really not sure how more clear I could have been - maybe next time :)
Those helping here often have information you aren't aware of and are looking at issues from a different angle... Which is really why you ask here in the first place...

Helpers shouldn't have to explain every reason for requesting information when analysing an issue; It's very helpful when members simply provide details of setup initially and further details as requested...

Others are trying to think outside the box on your behalf... Let them!...
Screenshots confirmed my setup and without Displax mod I could not pass safetynet
... I think you mean Play Integrity deviceIntegrity here(?)
with my previously mentioned setup of course but I get your fear of assumption now.
It's dangerous to assume anything when diagnosing issues on other's devices... This is actually a case in point: You CAN pass PI deviceIntegrity w/o Displax mod (as I've stated before)... You may not have tried/achieved that, but many do...
Thank you for your try to help me anyway, I appreciate it ... Will look for solution elswhere and hope.
All best on your quest... Hope something here was helpful... PW
 
Last edited:

Erfirya

Member
Aug 20, 2022
16
8
can someone help me with my disney+ app issue. so I have:
Xiaomi POCO X3 NFC
xiaomi.eu MIUI v13.0.1
Android 12
Magisk v25.2
USNF v2.3.1 (Displax mod)

my problem is I can't watch any of their content on FHD, it only shows up to HD quality even though I've subcribed to premium. I've tried logging in the same account on the same device model but w/ locked bootloader and stock rom and it has a FHD quality option. I've also added disney+ to denylist but the issue still persist. I've checked if my device is certified using Play Integrity API Checker (Nikolas Spiridakis). Here's the result:
so just an update. I finally found the solution for this. If you have a xiaomi.eu rom check this thread: https://xiaomi.eu/community/threads/widevine-l1-support.65671/ . If your device is supported for widevine L1 certificate renewal then you won't have a problem getting it back. mine was L3 before, but after doing this fix, I got it back up to L1. now I can watch FHD in my disney+ app. btw my device has unlocked bootloader and is rooted.
 
  • Like
Reactions: ipdev and pndwal

J.Michael

Recognized Contributor
Jan 20, 2018
1,523
1,621
Samsung Galaxy Tab A series
Too much to read 2000+pages. Where are you hiding the modules? I need them all and I'm sure they are in a box somewhere for me to root through. 😁
The modules are hidden where a number of posts say they are. There is a not-official-John-Wu repository. I remember the name "Orange Fox" -- it might be that; it might be something else entirely.

The thread search function is not entirely unusable. @IronTechmonkey has instructions in his signature. (I use a browser, and if I click enough I manage to select "This thread" when searching. The XDA app has bigger problems with searching.
 

Loustsoul

Senior Member
The modules are hidden where a number of posts say they are. There is a not-official-John-Wu repository. I remember the name "Orange Fox" -- it might be that; it might be something else entirely.

The thread search function is not entirely unusable. @IronTechmonkey has instructions in his signature. (I use a browser, and if I click enough I manage to select "This thread" when searching. The XDA app has bigger problems with searching.
In this thread?
 

Loustsoul

Senior Member
The modules are hidden where a number of posts say they are. There is a not-official-John-Wu repository. I remember the name "Orange Fox" -- it might be that; it might be something else entirely.

The thread search function is not entirely unusable. @IronTechmonkey has instructions in his signature. (I use a browser, and if I click enough I manage to select "This thread" when searching. The XDA app has bigger problems with searching.
I was just hoping that there was a library for modules so that I could learn more about them and how to use them. I used search and did not find an easy to understand answer. I then turned to you/this thread for help and support. I'm new to the magisk.
 

asripath

Senior Member
Jul 12, 2020
227
181
Redmi K20 Pro
I was just hoping that there was a library for modules so that I could learn more about them and how to use them. I used search and did not find an easy to understand answer. I then turned to you/this thread for help and support. I'm new to the magisk.

You could review

And use foxmm for module management
 

pndwal

Senior Member
so just an update. I finally found the solution for this. If you have a xiaomi.eu rom check this thread: https://xiaomi.eu/community/threads/widevine-l1-support.65671/ . If your device is supported for widevine L1 certificate renewal then you won't have a problem getting it back. mine was L3 before, but after doing this fix, I got it back up to L1. now I can watch FHD in my disney+ app. btw my device has unlocked bootloader and is rooted.
Haha... We've been discussing this very fix for broken Xiaomi updates (affects un-modded locked devices also) on last few pages!

That's why I asked you to "Check Widevine security level" originally! ... Expected you to use DRM Info app per the link, however you posted fingerprint payment menu which did seem to indicate you had L1... Guess you didn't...

Restoring L1 is generally the answer... Still not sure why @Drahy (on Sammy device, above) is having such difficulties even with L1...

Glad you stumbled on the late-MIUI Xiaomi inbuilt fix anyway...

Also, thanks for the excellent link:
https://xiaomi.eu/community/threads/widevine-l1-support.65671/
... it confirms a few things we were only speculating on here:

1) XiaomiEU custom MIUI seems to give native access to the menu for generating new keys / certificate (after keys are revoked), and

2) Xiaomi models w/ support for generating keys / certificate... Seems MTK model users and some others are out of luck... 😕 Extensive list given...

🤠 PW
 
Last edited:

rei20

Member
Sep 5, 2021
22
5
At the end of my wits.
OnePlus 8 pro OOS13 rooted
Netflix just hangs at logo
Latest github magisk, zydisk, USNF official, changed magysk name. Passing basic integrity

Uninstalled bloatware Netflix with systemless debloater and reintalled from play store. (First tried deleting all files with netflix on name with root explorer)

Only thing I can think is fox mmm not hidden (forgot the app that can hide other root related apps besides magisk)
Also haven't tried the japanese sounding magisk hider
 

Loustsoul

Senior Member
You could review

And use foxmm for module management
Thank you!!!
 

pndwal

Senior Member
My device seems to be supported. But, I didn't see any fix detailed there 🤔. Could you and @pndwal help me out?
As the links notes say, "Certificate renewal is done via Settings -> Passwords & security -> Fingerprint unlock -> Fingerprint payments -> Widevine (L1)": did you go there? (Assuming you have latest MIUI OS)...

I also linked to a post with fix incl. screenshots earlier... Can't recall exact model but principle is the same for all devices supported...

If the option doesn't exist in stock MIUI, I guess the note "This list includes only supported Android 10+ devices that either support Widevine L1 officially, or support it unofficially by Xiaomi.eu" means you can restore L1 certificate only by installing XiaomiEU for some devices on the list as they have added the option for these where official ROM hasn't...

Hope my interpretation is correct/helps! PW
 
  • Like
Reactions: m0han and 73sydney

pndwal

Senior Member
At the end of my wits.
OnePlus 8 pro OOS13 rooted
Netflix just hangs at logo
Latest github magisk, zydisk, USNF official, changed magysk name. Passing basic integrity

Uninstalled bloatware Netflix with systemless debloater and reintalled from play store. (First tried deleting all files with netflix on name with root explorer)

Only thing I can think is fox mmm not hidden (forgot the app that can hide other root related apps besides magisk)
Also haven't tried the japanese sounding magisk hider
Not sure why you have issue, but Netflix doesn't detect root or even require PI deviceIntegrity or SafetyNet since v5.0 AFAIK... It won't appear in Play Store w/o passing deviceIntegrity, but standard APK sideloaded works fine for most users even when not passing deviceIntegrity...

Nb. Some devices need passing PI deviceIntegrity to pass L1 certification, others don't... As long as they have L1 Widevine most users can stream HD but Netflix works fine W/ SD on L3 if L1 is absent...

You may have room issues, or something messed up or retained if you loaded unofficial Netflix etc... PW
 
  • Like
Reactions: 73sydney

Drahy

Senior Member
Apr 27, 2012
509
85
and I felt you only want to answer some questions as I had to ask more than once... 🙃

But you hadn't clarified... maybe in your mind...

Since you're still not letting go of assumptions I'll explain further, despite it being a circular argument... 😝

If you check Google Pay discussion thread you'll see many members had USNF + added a mismatched fingerprint (globally applied) using MHPC long before @Displax's USNF mod w/ (partial) Play Integrity fix (which does the same thing but targets gms) even existed (and @Displax was watching these developments in that thread), and that many continue to use this setup... You DID NOT state you had @ Displax (targeted) mod EVEN WHEN ASKED, and as you said you used MHPC in conjunction with USNF it appeared that you were likely passing deviceIntegrity verdict this way, like many others... - Not sure how more clear I could be than that...
I have never seen Samsung user with rooted original firmware on Android 13 passing Integrity checks without Displax with only using standard USNF and MHPC - I even read somewhere that creators of these mods stating it does not work for Samsung devices like that anymore and many others and definitelly an not for Android 13 in general. I believed this is common knowledge among people here so that is why it was not relevant for me to mention. But Ok it is possiblefor some maybe? :) Anyway I have this latest one from Displax https://github.com/Displax/safetynet-fix/releases/tag/v2.3.1-MOD_2.0

I already covered why I wasn't sure you actually had L1 at that point since you never stated that plainly and you only said "Netflix is ok" (many users consider Netflix works fine w/ SD having never had L1 compatible hardware anyway)... Further, you didn't state how you were seeing "it goes to L3 with bad quality streams" despite my asking. (Thinking: 'perhaps you see L3 somewhere (where?) but never actually had L1 since streaming didn't even work w/o liboemcrypto-disabler mod')...
Yes I never really said I really had L1 that is right but after you requested screens - they confirmed that and (as stated below) this waa not the problem of the circular questions really. So we can dismiss this L1 and L3 and stop talking about that as now it starts to feel going in circles.
Well that's not really the purpose of the mod...

Actually the mod simply masks liboemcrypto.so library, and L3 is just a consequence...
Yes I know that I just wanted to dismiss this as not relevant here - stressing that with this mod I can only achieve L3.
Apps can use liboemcrypto.so for decrypting both SD and HD streams, but the library is required for HD... Apps can fall back to other libraries where liboemcrypto.so doesn't exist but HD streaming will fail as will L1 security check...

It seems that affected apps are not allowing liboemcrypto.so use for ANY streaming and root detection (or possibly even detection that existing hardware for TEE decryption exists and should be used... Could be using model / other props with their own model whitelist too...) seems to be the likely reason to me... Ie. it's likely that these apps are simply restricting their use to SD decoding with older libraries (as liboemcrypto.so is primarily designed to decrypt HD content in secure TEE OS) rather than preventing apps from working on devices w/o hardware TEE...

Netflix does this too BTW, but relies wholly on Widevine certification since v5.0, making their approach much simpler...
Ok good to know thank you.
Those helping here often have information you aren't aware of and are looking at issues from a different angle... Which is really why you ask here in the first place...
And I get that and appreciate it.
Helpers shouldn't have to explain every reason for requesting information when analysing an issue; It's very helpful when members simply provide details of setup initially and further details as requested...
In this case I was just reffering to a reply from someone asking me which liboencrypt mod I used and even posted link to another similar mod even though I put a link there in my original post, not your questions...
Others are trying to think outside the box on your behalf... Let them!...

... I think you mean Play Integrity deviceIntegrity here(?)
Yes
It's dangerous to assume anything when diagnosing issues on other's devices... This is actually a case in point: You CAN pass PI deviceIntegrity w/o Displax mod (as I've stated before)... You may not have tried/achieved that, but many do...
Ok I didnt have this information - maybe some Samsung users with original firmare on A 13 can? OK, never seen any but maybe can and I get it now why you asked about that.
All best on your quest... Hope something here was helpful... PW
Thank you. I will try the option with the work profile as the last resort somehow to make it work...

I read some other topics in this section and some believe that doing these changes to pass Integrity checks many times over and over and trying to fogure out the cause could trigger something in the system only Clean install and wipe everything could resolve such issues like I have with my streaming apps so maybe I will try that as well if I find the time to install everything from scratch ...
 
  • Like
Reactions: ipdev

Erfirya

Member
Aug 20, 2022
16
8
My device seems to be supported. But, I didn't see any fix detailed there 🤔. Could you and @pndwal help me out?
follow this step:
* Certificate renewal is done via Settings -> Passwords & security -> Fingerprint unlock -> Fingerprint payments -> Widevine (L1)

if the widevine (L1) settings doesn't appear in your device, it may have to do with this:

Warnings for "debloaters":
* Uninstalling Xiaomi Cloud (com.miui.cloudservice) will cause the "Fingerprint payments" option to disappear.
* Uninstalling SoterService (com.tencent.soter.soterserver) will result in "Error -10009" when trying to request a new certificate.

so you have to reinstall/reactivate Xiaomi Cloud (com.miui.cloudservice) and SoterService (com.tencent.soter.soterserver).

after installing the 2 apps mentioned above, try to see if the widevine (L1) setting is back. if yes then click the 'certificate' button to renew/update your certification (after updating your certificate you have to reboot your device).
 

pupido

Senior Member
Apr 9, 2015
146
10
I stopped being interested in Magisk a few years ago, so I am not at all informed about the current situation. My old Note 9 has Magisk 23.0 (while the app has version 25.2) and EdXposed Manager 93.0.
I discovered a few days the Pixelify module and I would like to install it only I wanted to see if it is possible to do it with the current version of Magisk.
Also, I tried to update MagisK via its app but the update stops at version 23. Is this normal?
 

rei20

Member
Sep 5, 2021
22
5
At the end of my wits.
OnePlus 8 pro OOS13 rooted
Netflix just hangs at logo
Latest github magisk, zydisk, USNF official, changed magysk name. Passing basic integrity

Uninstalled bloatware Netflix with systemless debloater and reintalled from play store. (First tried deleting all files with netflix on name with root explorer)

Only thing I can think is fox mmm not hidden (forgot the app that can hide other root related apps besides magisk)
Also haven't tried the japanese sounding magisk hider
This was an upgrade to stock A13 from stock A12 with full data wipe after. As soon as bootloader unlocked, netflix said uou need to update and on google play said no version available. then after passing integrity and debloating Netflix+netflix activation I can install again from play store but just hangs at logo. Same thing sideloading from apk mirror

I did delete netflix.partner.activation app.

For now, can someone please tell how to hide root related apps?
not very keen on data wipe again
 
Last edited:

Top Liked Posts

  • 5
    Like I said I have been using Manger apps way too long to not refer to them as the Manager. 🙃

    The combination of app and on-device services (root) could be called Magisk The Gathering. :D:D:D
    4
    I think John did this:
    https://topjohnwu.github.io/Magisk/...agisk-manager-is-deadlong-live-the-magisk-app
    to clearly distinguish the old Manager which was just that, the Manager component, a "companion app" finishing with version 8.0.7, from the new Magisk app which is actually a complete Magisk package w/ the App (UI) part now necessarily in sync with the Magisk binaries and including "everything it needs within the APK itself, making installation a 100% offline process" incl. zip installers and now stub APK etc and starting wrapped with Magisk itself as version 22.0 (22000)...

    Magisk Manager is dead.
    Long live the Magisk app!


    😋 PW
    Like I said I have been using Manger apps way too long to not refer to them as the Manager. 🙃
    Instructions
    You can install/update phh's SuperUser in Magisk Manager's Download section
    If you have no root in the first place, please flash the zip in the attachment through custom recovery
    A root solution is part of a proper Magisk installation.
    After phh's SuperUser is installed, please install the SuperUser manager Application through the Play Store
    phh's SuperUser Manager
    Guess I am turning into the "Old Man".
    Next I will be yelling at kids to keep of my lawn. 🤪


    Cheers. :cowboy:
    3
    @meric57's screenshots show no Magisk with unhidden manager; Magisk with hidden manager

    I don't remember anyone ever talking about locating the hidden app in the app drawer and using it. I have been assuming that it would show Magisk installed -- the problem was always that the victim didn't realize he had two manager apps, I don't remember anyone saying that with two managers, both managers are disabled, only that the new, unhidden, manager did not communicate with the installed Magisk because the installed Magisk had somehow been co-opted by the manager that is now hidden.

    Maybe meaningless details. I do not feel that we have been told what @meric57 did, in exactly what order.
    As for competing managers.
    I was going off of memory from when it used to happen to me every now and then.

    Both the regular (not hidden) and hidden (renamed) would show Magisk N/A.

    All I had to do was uninstall one of them.
    Normally I uninstalled the hidden (renamed) one and rebooted.
    Then the regular (not hidden) one would show Magisk installed again. Then I could hide (rename) the manager again.
    It was hit or miss if I uninstalled the regular one and rebooted.
    Sometimes the hidden one would still show N/A. If so, then I had to uninstall it and reinstall the regular version again.
    Then hide (rename) the manager again.


    ---

    I wasted a bit of time tonight trying to get two Magisk manager apps to run currently.
    The best I got was an error with Magisk Stable v25.1 on my Pixel 4a.
    The initial hiding gave me issues with setting permissions and such.
    Once the hidden app was installed, the regular version was removed.
    The hidden version showed Magisk installed and active but, would keep throwing errors telling me to restore the Magisk app and hide again.
    So I did and no issues the second time around.​

    Cheers. :cowboy:

    Edit:
    @pndwal I did not read your last couple of posts before testing.
    When I have time (tomarrow) I will see if I can duplicate it. 🙃
    2
    Samsung compatibility

    Fix for Magisk on new A13 LV Samsung (S23 Ultra etc) devices coming soon!

    Add init_boot.img patching for Samsung tar firmware packages #6586 opened 6 hours ago by BlackMesa123Approved

    - Ckecks now passed, tested, ready to merge. 😋 ... Thanks @BlackMesa123 and @dr.ketan!

    👀 PW
    2
    The combination of app and on device services (root)could be called Magisk The Gathering. :D:D:D
    I always thought it best to try to understand / adapt to a Devs parlance / nomenclature if only to avoid reinventing the wheel, which could be considered a bad omen... If the Dev/creator wanted to reinvent the wheel however, I was happy to let 'em...

    But let's throw out convention; I'm with you guys... Let's go with the "Magisk The Gathering" app!... @ipdev's a Dead head and The Gathering has been described as 'coming off like a cheap mix between "The Omen" and "The Dead Zone".... Gotta work for all of us no? 😁 PW
  • 8
    Didge says Bye...

    I was very sorry to see yesterday's MHPC commits:
    1. Update FUNDING.yml
      Didgeridoohan committed yesterday

    2. Bye.
      Didgeridoohan committed yesterday
    and the update of @Didgeridoohan's OP in [MODULE] [DEPRECATED] MagiskHide Props Config - SafetyNet, prop edits, and more - v6.1.2 thread:
    MagiskHide Props Config v6.1.2

    Note: This project is dead, and has been for some time. I have not been involved in the Android modding scene for some time and I no longer have the energy to take it up again.

    If anyone feels like taking over give me a holler.
    This project was a mainstay of Magisk modification, giving John Wu's Magisk applet resetprop, an advanced system property manipulation utility, the terminal based UI that made prop manipulation accessible to Magisk users in general...

    Each option has been elegantly implemented to make what would otherwise be an arduous exercise involving user creation of custom boot scripts the no-brainer that we know so well!

    What a project, what a plethora of uses...

    @Didgeridoohan's Last post in that thread was back in February:
    Just popping in and letting everyone know I'm still alive.

    There are simply too many things going on outside the world of Android tinkering for me to be able to give XDA much attention at all. Once things settle down, and if I'm not entirely burnt out by then, I've got quite a lot of catching up to do. Can't give any kind of ETA, but I'm hoping for things clearing up before the end of February.

    Huge thanks to everyone answering questions and helping out...
    ... well clearly no clearing has occurred in Feb. or later... 🙁

    @Didgeridoohan's last XDA post, only weeks later, was a response regarding his officially endorsed comprehensive Magisk Troubleshooting Wiki:
    Everything about Magisk install and more can be found in this great guide by @Didgeridoohan .
    https://www.didgeridoohan.com/magisk/Magisk
    Thank you... With the slight caveat that it needs a serious update after the v24 release. I've just been too swamped IRL the past few months. Hopefully soon™.
    So no further updates to that either, but whatawiki!!! - Still a principle go-to for any non-lazy Magisk user w/ any issue!...

    ... So as a foreigner living in Didgeridooland, I'd like to wish the Didgeridoo man from Sweden all the very best with real life, and to thank him for such elegant contributions to the Magisk modding community...

    I hope you can visit Didgeridooland soon Sir! ... I have a boomerang with your name on it... 👍👏 PW
    6
    The caveat to this is if OEM Unlocking is enabled in Developer Options. I'm not sure if this is a bug; the Pixel devices can be flashed this way even on a locked bootloader.
    Are you referring to when using Android Flash Tool to flash? If this is the case, Android Flash Tool actually unlocks the bootloader (with the prerequisite that OEM Unlocking is enabled) during the process so it can flash the image. If, however, you flash an image via flash-all, for example, with OEM Unlocking enabled but with the bootloader still locked, you won't be able to flash the image.
    6
    Think you might be quoting the wrong person. The person I was responding to couldn't root their phone because their bootloader was locked.
    Sorry, it was @TheNixck . I am going through chemo therapy and I think I have one of the side effects: chemo brain lol!







    6
    kdragon has released an updated version (v2.4.0) of his USNF mod for his Patreon members. Hopefully will go public in a week or two.

    v2.4.0 (early access)

    Repository: kdrag0n/safetynet-fix · Tag: v2.4.0-ea · Commit: 2f18d85 · Released by: kdrag0n

    Highlights​

    • Play Integrity bypass without breaking device checks or causing other issues
    • Disabled use of hardware attestation on Pixel 7 and newer (@anirudhgupta109)

    Other changes​

    • Updated instructions for newer Android and Magisk versions
    • Better debugging for future development
    It's taken a while to find way to bypass Play Integrity that doesn't require spoofing the build fingerprint permanently, but I wanted to make sure this module doesn't cause any unnecessary breakage. Just like the original goal of Universal SafetyNet Fix, this minimizes adverse effects by spoofing dynamically at runtime only when necessary. Enjoy!
    Public release now available.

    6
    Hello, I need some help with spoofing sys.oem_unlock_allowed to 0.

    My banking app (Estonian Swedbank app "Swedbank Eestis," package name "com.swedbank") detects sys.oem_unlock_allowed if it is set to 1 and disables specific options in the app (like biometric login). I can confirm that it is sys.oem_unlock_allowed because setting it temporarily with resetprop -n sys.oem_unlock_allowed 0 and deleting the app data allowed me to use the blocked features. The app doesn't complain about root; hiding root with Zygisk works without issue.

    However, I am unsure what method I should use to safely spoof this value without bricking my device. Is it safe to use resetprop -n? Does it persist after a reboot? Should I use a different method entirely?

    I'm running:
    LineageOS 20-20230105-NIGHTLY-kebab on a OnePlus 8T KB2003
    Magisk 25.2
    Universal SafetyNet Fix 2.4.0
    Swedbank version 21440
    Passing SafetyNet with YASNAC
    I am also spoofing device fingerprint with MagiskHide Props Config to pass SafetyNet.

    I really appreciate any help you can provide.
    Ok, so as guessed in my yesterday's post/answer #54234, it seems that you could more-or-less achieve your wanted functionality - could you try please:

    1) Install the following module and reboot - all thanks to @huskydg for his interesting and excellent module:

    2) Go to:
    /data/adb/modules/magisk_proc_monitor

    and rename the original (dummy/template) dynmount.sh script to dynmount.bak,
    and replace that dynmount.sh with my customized script:

    My changes (customizations) in the script can be recognized as commented by CAPS LOCK comments

    How it works:

    myAPP=com.swedbank defines the package name for your Estonian Swedbank app

    myPROP=sys.oem_unlock_allowed defines the property you want to 'hide'/'un-hide'(corresponding to your Developer Options, OEM Unlock disable/enable switch)

    hidePROP=0 defines the 'hidden' property value (OEM Unlock disabled)
    unhidePROP=1 defines the 'un-hidden' property value (OEM Unlock enabled)

    You can redefine those variables (lines 24-32) if you need

    Eg, I did my own non-intrusive tests (still commented out in the script if somebody else wants to play) with MiXPlorer instead of your banking app:
    myAPP=com.mixplorer

    and by playing with a dummy prop:
    myPROP=my.test

    a)
    When module recognizes that your banking app $myAPP is pre-initializing,
    it will 'hide' $myPROP 'by setting to $hidePROP (lines 39-46)

    and you will see the notification like:
    "Hide my prop / com.swedbank, sys.oem_unlock_allowed=0"

    For this event to happen, the banking app $myAPP must be started, not brought back from background (kill and restart your app)

    b)
    Whenever the module recognizes that any other user app is pre-initializing AND that $myPROP was still 'hidden',
    it will 'un-hide' the prop by setting it back to $unhidePROP (lines 51-60)

    and you will see the notification like:
    "Un-hide my prop / com.xda.labs.play, sys.oem_unlock_allowed=1"

    All the $myPROP sitches are systemless - when you reboot, the prop will be back to its original/default value

    Issue/question:

    Of course, instead of monitoring while any other user app is initializing (case b),
    it would be better if the module could directly recognize when your banking app $myAPP gets closed (killed) and to 'un-hide' then the $myPROP property back

    However, I did not find how to recognize in the dynmount.sh script when an app is really closing and that's why I put the case b as described above

    Maybe the module's developer @huskydg could better customize the script dynmount.sh to more closely cover the original functionality as you needed:
    - 'hide' the $myPROP property only for the $myAPP application

    ---

    The really good and interesting thing with his module is that user can customize the provided default dynmount.sh script
    to catch-up events when particular app(s) are starting to dynamically apply certain changes (redefine certain properties, do particular mounts)

    Otherwise, one would need to develop his own Zygisk module, but there the Zygisk part must be coded in C (and recompiled),
    it cannot be made simply by scripting as here with his simple dynmount.sh script
  • 1091
    This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases.
    All information, including troubleshoot guides and notes, are in the Announcement Thread
    156
    Hello, I haven't given much support on XDA lately. It can be resulted from
    • University started and I have limited free time. In fact, I mostly develop during midnight
    • I live in Taiwan, which has large time zone differences between my European/American contributors/testers, which usually forces me to stay up late at night to discuss/test stuffs.
    • The new version is about to come, I don't want to spend effort on supporting old releases
    The planned update is delayed again and again, to some point I think I'll shed some light about what has been happening lately, also along with some announcements.

    New Forum!
    As you might have already discovered, Magisk got its own subforum on XDA! Many thanks to all the support you gave me, and much more information/features/support is about to come!
    **For developers supporting all the devices that are not using standard Android boot format, feel free to create threads in this section (actually, PLEASE do so) for your favorite devices after v7 is out. As I currently know, Asus devices require signing the boot image before flashing, and is model dependant; Sony devices seems to use ELF kernel that is unpatchable, or some has two ramdisks (inner + outer), both requires different workarounds; LG bootloader locked devices has to manually "BUMP" the boot image after flashing Magisk..... and there may be lots of other crazy boot image formats that haven't come up to my attention yet.
    It is impossible for me to support all these non-standard boot images, and I hope the community can collaborate to make Magisk running across all the devices. Overall, community collaboration is what XDA about :D

    The Pixel Phone
    Some of you might already know this news, that the next Pixel Phone right around the corner seems like it does not have ramdisk in boot image, which pretty much wrecked Magisk in all ways. However, it pretty much doomed root itself too. Kernel modifications is inevitable IMO, so I'll try to migrate my scripts to C programs that could possibly be included into the kernel itself. Note that I'm not familiar with linux kernel, I'm not even sure if my idea and concept is correct or not. But once the device is available, I think developers will find a way to bypass all the difficulties, and I'll do my best to learn things ;)

    Current Progress
    In the past month, I've spent quite some time learning SELinux, so that I can avoid using SuperSU's sepolicy patches. Thanks to the helps and tips from @phhusson and @Chainfire, I finally have a much clearer understanding of how SELinux works. The Magisk core parts (the scripts, boot image patches, new features, more supports) are actually done some time ago. What is causing all the delays is the Magisk Manager.
    To be completely honest, although I can code in Java without much issues, Magisk Manager is actually my first Android application, I had to reach out for assistance, and fortunately awesome developers like @DVDandroid and @digitalhigh contributed a lot, which makes the current Manager awesome.
    After the repo system and module management is mostly done, I was about to do some adjustments and release, but what we really done is decided to add another feature: auto-unroot with per-app settings. I decided to wait for it to be finished, and then do my adjustments. Due to reasons that'll be mentioned later, this feature will likely not be available for the next release (should come in future updates)

    Safety Net Disaster
    Those who are using Magisk for Safety Net bypass purposes must have known that Google recently updated the detection method of my Systemless Xposed. I still have no idea what Safety Net is detecting, so currently I cannot fix it on my side (also because I'm busy working on the next update). However, suhide developed by @Chainfire is able to hide Xposed and worked fine.
    However, only my Systemless Xposed v86.2, which is based on SuperSU's su.d, is supported using that method. v86.2 and v86.5 (latest, Magisk based) have nearly identical binaries, and the only difference is the path where the binaries are stored.
    I'm still not sure what's the real issue for it not being supported, I just hope it is not done intentionally.

    Conclusion
    Due to the fact that my Safety Net bypass is not 100% perfect now, I do not want to spend any more time waiting for auto-unroot to be polished. What I'm doing now is finishing up all the things I'd like to change in Magisk Manager (it has been a while since I last contributed to Manager, my fellow developers are doing all the heavy job), which might take a little more time, after that, packed with tons of information to be announced in Magisk Section, I'll release the long awaited update.

    Hope this lengthy post gives you the idea of the whole situation, and again thanks for all your support!!
    121
    Ah, some Chainfire bashing, I hope it is not too late for me to exercise additional villainy.

    First, let me make clear I have nothing against @topjohnwu, nor against Magisk. Magisk is an interesting project and it certainly displays @topjohnwu ingenuity and persistence. I don't doubt we will see more interesting things from his hands.

    -------------------------

    What has happened here is not all that dark and complicated, from either end. I returned from holidays, and someone pointed me at Magisk. My first thought: interesting!

    Among other things, the thread lists some issues with SuperSU, which in combination with the phrase The developer also requests users to not bug Chainfire with compatibility requests for SuperSU with Magisk from the portal article, raised my left eyebrow by nigh half an inch. The popular systemless xposed mod is apparently now based on it, and apparently it now no longer works with SuperSU, and apparently I'm not supposed to fix that, nor any of the other found issues. I found that a bit weird. So yes, I have told @topjohnwu that I was a bit surprised he was posting about issues with SuperSU without notifying me about them (I can't fix or help fix issues I'm not aware of, after all).

    He's also spreading a modified version of the SuperSU package, which is not all that uncommon, nor necessarily a problem. I have not looked into what he modified, I only ran a few quick tests on one of my devices, and found some commonly used commands run as root to be broken. I have informed him of this as well.

    It appears the tool of choice for Magisk is phh's Superuser, because of some of the mentioned issues with SuperSU. That's fine by itself, but fixing issues in that superuser by incorporating SuperSU's binaries into it is a somewhat questionable practise. After all, SuperSU is a commercial closed-source package that helps pay for my dinner, and superuser is a direct competitor. I have informed him that I was surprised he did this without asking for permission. I have expressed similar surprise on him spreading a modified version of LiveBoot (which helps pay for a snack now and then).
    @topjohnwu has also stated that Magisk's scripts are largely influenced by mine (I have not checked). Scripts based on mine are used all over the place on XDA, some people have crafted amazing things based on them, I have never made an issue of this (otherwise I would have just made them binaries). But yes, I have also stated to him that I don't think it's very nice to base something on one program, and then using that to (almost exclusively) push something directly competing with that program.

    tl;dr Towards @topjohnwu, I have:
    - expressed surprise he has issues getting Magisk to work with SuperSU, and has chosen not to inform me about those
    - expressed surprise he is using SuperSU binaries in a competing superuser without permission
    - expressed surprise he is posting a modified LiveBoot without permission
    - informed him of issues with the modified SuperSU he has posted
    - let him know I thought it wasn't very nice to be applying my scripts to benefit seemingly exclusively that same competing superuser

    To be crystal clear:
    - I have not asked for an apology
    - I have not asked for Magisk to be abandoned, neither the root hiding nor systemless module parts, and certainly not systemless xposed
    - I have not made an issue of any of this anywhere, until this post
    - I have not even specifically asked for anything to be taken down (though obviously in my opinion the other superuser package mixed with SuperSU's binaries, as well as the LiveBoot package, should go)
    - I have not reported this thread to XDA moderators for copyright violations or otherwise

    While my conversation with @topjohnwu may not win any awards for being friendly (though it may win some for brevity), I think all things considered my response has been rather mild. To be perfectly honest, until the apology post, I thought this was over with already. I think the apology post was triggered because I haven't replied to his last PM for a while - I was in the zone, it happens.

    To emphasize again, I have nothing against @topjohnwu, Magisk, or systemless xposed, and it is certainly not my goal to see any of them go. If it can be made to work together with SuperSU, great.

    I get it though: you think of something, you want to see if you can make it work, you finally get it to work, you publish it, it takes off - enthusiasm gets the better of you. Maybe in the rush some mistakes are made. That doesn't mean you have to just drop it and run. None of my stuff would make it past 0.1 if I stopped at the first big mistake :)

    Aside from said being in the zone coding, I usually regret actually responding to these sort of things the day after, which has made me hesitant to reply. Surprise me.
    76
    Thread temporarily closed so everyone sees this.

    The flood of "SafetyNet isn't working for me either!" posts are not helpful, at all. Please refrain from posting further, it will be looked into. Please do not forget that not passing SafetyNet is 100% NORMAL AND INTENDED when you have an unlocked booloader or running custom firmware. These are workarounds and they will be worked around in turn.

    The Flash
    Forum Moderator

    EDIT: Thread is reopened... I will be cleaning any SafetyNet posts for a while to keep the thread clean for real issues.
    75
    Hello everyone!

    I am aware that Google has updated Safety Net that makes Magisk itself a no go for Android Pay. In fact, I witnessed the change live while I am developing the new magiskhide, which should hide all Magisk modules and Magisk installed root.

    Google is serious about Safety Net now, clearly hunting down all possibility to run Xposed with Safety Net passed. I spend quite some time examining the new security measures last midnight, and fortunately it seems that it is possible to run Magisk and root along with Safety Net if no Xposed is running. I'm glad I removed the old root toggle at the right time lol, that is no longer feasible with the latest detection.

    So stay tuned for the next update, it will come with bug fixes, along with the new magiskhide to bypass that Safety Net.

    Google, how will a few systemless mods do any harm :p:p