yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Sorry mate! 😬 ... Knew widgets go... All your photos turned up here, so don't worry... shall I send them back? 😝 ...

I assume modules got disabled?

Incidentally, a couple of times I was able to trigger Magisk 'Safe Mode key combo' detection (and disable modules) without triggering Safe Mode!... Perhaps there's a better way (altered key combo detection?) to disable modules only on boot; Magisk's key detection is fickle at best anyway, and may not work going forward...

Till then I recommend @huskydg's Bootloop Protector for any Magisk users updating OS.

... Really hope you find your photos mate... I'll do my best to send them back... 🤪 PW
[Magisk] zgfg:
As said, modules were disabled.

After several reboots, etc I got Gallery fully back (it was stranger I was able to see all photos in WhatsApp but not in Gallery)

Now, struggling with emotions, one time working, the other not 😷
[Magisk] Swordfishx86:
Samsung S10e, Magisk 24304 installed (recovery mode), root working fine.

Magisk App updated to 24306, fails everytime to directly update Magisk to 24306 on the bootrecovery-partition. Says it updated successfully but after a reboot still shows Magisk 24304 installed and the App keeps nagging about "Requires Additional Setup", which only leads to the usual update procedure.

Can I just select and patch a file? the boot.img? and then flash BL, AP, CP and HOME_CSC with the same FW-Version currently installed? where do I put the patched boot.img? back into the AP-archive? I'm usually not that lost, but the phone is finally set up to my likings and I want to avoid formatting data at all costs. Since everything is working as I like it, I even consider not updating at all :(
[Magisk] pndwal:
Bit confused - recovery mode means Magisk installed on recovery partition, not boot partition... Does your device have boot ramdisk (ramdisk = yes)?... Or does it have A/B partitions?

If ramdisk = no, could you have de-selected Recovery mode before taking direct install?

... Please answer above first. 😜 PW
[Magisk] Swordfishx86:
@pndwal The S10e doesn't use a ramdisk. It's usual procedure to install in recovery partition on these phones, yes. It might have happened that I forgot to tick the checkmark for recovery on one of my numerous attempts to update, but I am positive that I ticked the checkbox "recovery mode" on most if not all attempts to update Magisk. I'm not even sure I ever forgot to tick it. The last attempt was however with the checkmark set for sure.
[Magisk] pndwal:
Actually, you have this issue, marked as regression but not yet fixed:

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

Suggest you read / watch that thread, perhaps help with a fix...

Seems you can work-around by repatching AP tar...then flash Flash AP + BL + CP + HOME_CSC together per official instructions... Don't mess with discreet boot.img or recovery.img... this is Samsung. 😝 PW
[Magisk] Swordfishx86:
@pndwal thanks for pointing me to the bugreport. spot on! I'll try to patch AP and flash with odin in a few days and report back.
[Magisk] pndwal:
No boot ramdisk, but Magisk must be installed to a ramdisk, therefore on A only legacy SAR devices it must be installed in recovery ramdisk...

My confusion was due to your comment "Magisk App... fails everytime to directly update Magisk to 24306 directly on the boot-partition."

Yup, that would have accounted for it, but finding / seeing the above issue makes me certain you did it right. 😜 PW
[Magisk] Swordfishx86:
@pndwal I haven't had to mess with my S10e in quite some time. Last device I had the questionable honor of messing with was a Xiaomi Redmi Note 10 Pro. Thus my confusion. Fixed (edited) in my initial post. of course recovery, not boot.
[Magisk] lm089:
Sorry if this was asked before; I searched a bit but after a few pages I gave up.

Question (probably a bit basic, but anyways):

I understand that to install Magisk we should patch an existing boot image (just learned the hard way that it's a good idea to follow that rule :().

What I don't get is: how can I get that boot.img in the fist place? Are there tools to extract it from the ROM.zip? The A11 ROM.zips I'm looking at are all containing a file called "payload.bin", I guess it must be in there...

Or do I have to install the naked ROM first then somehow extract boot from there? Then again: how do I do it?
[Magisk] pndwal:
Official method is to extract from payload.bin if A11+ use it (some A11 ROMs don't) using Payload dumper; several posts here and in age of zygisk thread - search back... 😁

You can also do the latter if you have custom recovery; take 'nandriod' backup incl boot (or recovery) partition needed, locate backup and patch the boot(/recovery).win file. (Can rename to .img) 👀 PW
[Magisk] lm089:
I did ... successfully this time within the zygisk thread, and got it working (y)

Cool, didn't know that. I find a file called "boot.emmc.win", guess that's the one? Next time maybe...
[Magisk] pndwal:
Little checking: seems you have OnePlus 6... Seems that's an A/B legacy SAR device, so, some guesswork:

Magisk is installed to recovery ramdisk in boot partition (and so is TWRP); ie.

USES_RECOVERY_AS_BOOT. (Nb. this is NOT Recovery mode Magisk, which refers to ramdisk location in recovery partition.)

So, as you don't have Magisk in recovery (and I assume you don't have option for recovery partition backup in TWRP in any case), boot.emmc.win will be the one you need; make backup after OTA update. (Patch as is, or change extension; nb not all .win backups can be renamed or used as .img files, but boot images incl. boot.emmc.win and recovery.emmc.win can)... 👍 PW
[Magisk] ipdev:
A bit OT for the MHPC thread.

So I moved into the Magisk General thread to answer you. ;)

I am not sure if you found a fix for this yet.

It has nothing to do with TWRP.

Netflix has issues at times but, they actually do not care if you are rooted or passing SafetyNet.

They will limit the account on insecure devices.

- Standard resolution.

- Some content may not be available (this is rare though) due to DRM rights.

You might be running into an issue with Widevine/DRM?

It took me a little time to find ianmacd's module thread since I did not remember the module name.

Not sure if it will work but, it is worth a try.

xdaThread - [Magisk] [Module] liboemcrypto disabler for DRM-protected content (Netflix, My5, etc) - Link

When I checked, Netflix does not have (-93) in their Help Center yet.

Netflix - Help Center (Search results) - WebSite - Link

Might be worth taking a look at some of the similar issues and try the suggested solutions.

Good Luck. (y)

Cheers. :cowboy:

PS.

I use Netflix on a Nexus 10 running Lineage 16.

No GApps, permissive SELinux, bootloader unlocked, unsigned debug rom.

For testing purposes, I normally have mine set even more insecure to grab logs.

Basically all the red flags for security. 🙃
[Magisk] Event_Horizon:
Thanks for bringing my issue here, actually I tried the liboemcrypto module, but didn't work either. Currently widevine security lvl is L1, it should be L3 after root I guess. my Device is certified & Netflix is available to download from Play Store.

No I still couldn't able to run Netflix, everytime I clicked on Netflix, it says the same -93, tried looking into Netflix support, it's says this error occurs due to Network Issue, that bogus bcoz I tried using it after locking bootloader & it worked. I'm pretty much sure it's because of bootloader unlock status, so looking for solution linked to that.

@topjohnwu Sir, could you please put some guiding light to it?
[Magisk] ipdev:
I only have a OnePlus 5T, 6T and N200.

All on latest stock OOS for the device.

I do not have a device running OOS 12 so I am not sure if there is some change in OOS that is affecting it.

More than likely it is a setting that needs to be cleared in the Netflix app or on the device.

I installed Netflix on my N200 to test.

I disabled all modules (except nano) and rebooted.​

Spoiler content hidden.

Logged into Netflix.

I tried 13 Reasons because I know that was one that had DRM issues with some devices.

No error/issues the random episode I picked plays fine.

I can scrub it back and forth along with quick skips forwards and backwards.

Logged out of Netflix.

Enabled the USNF module again and rebooted.

Spoiler content hidden.

Logged back into Netflix and continued watching the random 13 Reasons episode I picked the last time.

Still no error/issue.

Did you try clearing cache and data of the Netflix app?

Did you logout, uninstall and then reinstall the Netflix app?

That was just two examples from the Netflix's Help Center issues.

Any one else with a OnePlus 10 Plus (or OOS 12) have a similar issue?

This issue seems to have moved very quickly OT for even the Magisk General thread. ;)

Since I can not currently break Netflix on my devices, I am not sure how to fix it on yours. :confused:

Hopefully someone in this thread can guide you to an answer and/or a more appropriate thread.

You can also contact Netflix and ask them.

Maybe it is an easy fix and they can add it to their Help Center.

Please let me know when you solve it. ;)

Cheers. :cowboy:

PS.

The Properties of interest I note in my prop check.

ro.oem.key1

Some manufactures include this for unlock availability.​

ro.oem_unlock_supported

Value of 1 means the device can be unlocked.​

sys.oem_unlock_allowed

Value of 1 means 'OEM Unlock' has been enabled (toggled on) under developer option.​

Spoiler content hidden.
[Magisk] pndwal:
L1 is good; means root is hidden properly to whatever key attestation widevine polls (there are several possibilities) and HD video / streaming is supported since attestation is indicating video decryption and processing is occurring in TEE (Trusted Execution Environment).

May not be bogus; seems this (network error message) may be your best clue to me...

I see you are Errorguy1991 on GitHub, and made this issue:

https://github.com/kdrag0n/safetynet-fix/issues/176

8 days ago... Yes, @kdrag0n will get to it, but he develops many projects / ROMs, utilities etc... and has a personal life... Please be patient!

It is possible this issue is USNF related, but you really need to demonstrate this... Have you checked behaviour of Netflix w/ USNF disabled (despite SafetyNet failing) for instance? Also, perhaps symptoms can be demonstrated to be comparable with issues currently getting attention (or lack of it) like this one?:

https://github.com/kdrag0n/safetynet-fix/issues/154

Other likely causes:

Not sure why you've added so many Google services in denylist! - This may well be causing issues; I am aware hiding Chrome broke webview for instance... Not sure what issues occur with your selection, but why do you need / risk anything Google other than GPay??

Also, selecting Netflix (without opening process view) selects only one default process for me (but I'm on Android 10), and this works fine! (*.playcore_missing_splits_activity processes aren't selected by default for me.)... You seem to have selected all possible processes for other apps too... Why?... Please deselect all but what you know you need!

Are you using any firewall, adblocker, VPN mods like wireguard or other network security protocols or mods (modules, apps) on your device?... These often block specific server access...

Have you tried disabling all modules except USNF (assuming OOS 12.1 is stock)?

Also, are you 100% sure your boot image (incl. kernel importantly) matches your current ROM? ... Those who take OTAs, then re-flash original Magisk-patched boot image sometimes have many issues especially with comms and other hardware, but sometimes only minor issues with mobile networks, wifi, bt etc...

This is doubtful; it doesn't affect other users.

He hasn't commented here in years... Highly unlikely he will comment now especially where methods to 'spoof/alter/manipulate non-Magisk related signals or traces to circumvent device state detection' are involved.

Hope this helps you. 🙂 PW
[Magisk] zgfg:
For @Event_Horizon, post 51610

I've seen comments that 'root is expected' to break L1' but I don't believe into that and I never had a problem with L1 due to Magisk (if root strictly and only means Magisk)

L1 depends on the paid certificate for the particular device. No certificate, then L1 downgrades to L3

However, when people say 'root' you never know what exactly they mean about

Under 'root' some may think of custom ROMs, some play with TWRP and affect partitions like Persist, etc (all that requires the unlocked Bootloader just like the Magisk/root, and for some of them it is the 'beginning of root').

Or they do in parallel couple of those moddings and then they say 'root' was a cause

I have two Xiaomi phones, both running A11 (previously A10 and even A9 with one od them), I have gone through the various version of Magisk (Stable, Canary, Alpha. Custom; v23, pre-v24, currently 24306)

I don't hide Magisk/root by any means from Netflix. I only pass SafetyNet (I could later disable USNF and test Netflix while not passing SafetyNet)

But what is important:

I actively watch Netflix, couple of times a week, and it always works with L1/FullHD (screenshots), and it was never, ever downgraded for me to L3 (and I never had any error in the Netflix app)

On one phone I have stock Xiaomi MIUI, on the other Xiaomi.eu (let's say custom MIUI).

As said, Magisk on both of them.

I don't use custom/AOSP/CGI ROMs, and I used custom recoveries (various, on both phones) but only for back-ups, never for modifying (or even to restore) partitions like Persist or other that carry sensitive data for L1, IMEIs, MAC addresses or so

Ie, yes I have the unlocked Bootloader, I have Magisk, but I never did anything to affect the unique L1 certs that were issued for my phones (knowing that they cannot be replaced if ever deleted or anything)

PS: My DenyList attached, you can see that I only hide root from few app detectors and few 'real' apps that reported root. But nothing about Magisk and no Google apps (USNF takes care of Google Play Services, ie of SafetyNet)
[Magisk] zgfg:
Cont. for @Event_Horizon, post 51610:

As mentioned, I disabled now both Shamiko and USNF (and rebooted)

This means I had now:

- DenyList disabled

- Shamiko and USNF both disabled

That is, Magisk/root (with Zygisk, initrc modifications, etc) were all fully exposed, no more hidden at all!!!

Eg, (YASNAC) was failing, both Basic Integrity and CTS Profile

But I opened Netflix and watched the supplemental episode of The Billion Dollar Code, with no problem whatsoever

I also checked my Playback specification in Netflix, it was still exactly as in my previous post: L1/FullHD, Dolby Vision

Netflix does not care about the unlocked Bootloader and Magisk/root
[Magisk] m0han:
I don't use Netflix or any such app. I don't have robust connectivity where I usually am; 'no buffering' streaming is out of the question. Just checked using DRM Info app.
[Magisk] foongwk:
Strange for my case....N9005 ive flash according to steps given but had missed out framework portion and failed on safety net. Then i install through Magisp manager for framework 23 and it still failed even after rebooted. Next i delete it through Magisk manager again and rebooted and try safety net passed as per image.
[Magisk] cridtohs:
not working for me. Galaxy S7 Edge. Followed all instructions. SAfetyNet is detected - FAIL .. IF OP could post on first page in GREEN or RED lettering DETECTED or UNDETECTED would be nice

---------- Post added at 04:01 AM ---------- Previous post was at 03:58 AM ----------

Tried this, not working. Also this is extremely annoying that you dont paste links. At least point to the webpage or thread that these files are located if you dont want to link the files, which become outdated anyway if someone stumbles upon your thread haphazardly trying to get this to work again.
[Magisk] meangreenie:
Massively confused please help. On older versions there was a simple hide root button. But on v8 there isn't one, just the hide magisk in settings and reboot. I've done this but sky go app still detects root?

Please help i must be missing something
[Magisk] andrew2432:
Did magisk manager ask for superuser? If it didn't you gotta install phhsu apk/app not.just zip

[MENTION=4577747]zapahacks[/MENTION]:

Nice, any idea why mod2? I have galaxy s5...a bit different, v6 magisk that actually worked when v7 and v8 came out but a sn update broke it. I don't want to start from scratch but I'm gonna have to.
[Magisk] CryMasK:
Only 1 question, when I open the RootSwitch app, the "disable xposed" option said "it's not supported systemless xposed" and the toggle is disable(Can't click)

Any idea?

SOLVED. See my post #5203
[Magisk] stangri:
[MENTION=1162986]Captain_Throwback[/MENTION] hey man, since you're the local expert let me ask you something -- I have two modules which have system subfolder with priv-apps in them, but only one at a time works. Do you have any idea what's up? I'm on Nexus 6 with nbd90z, magisk8 and phh's superuser 259 if it matters. There's nothing of interest in the logs -- if one module loads the other one (or its system folder) doesn't even come up in the log.
[Magisk] izeeqo:
Hello everyone,

I have an LG G3 stock Android Marshmallow 6.0 with custom kernel, the bootloader of the LG G3 is mainly locked, no way to unlock. So, in the bootloader side,no problem. I have magisk v8 with xsetprop and the mod_v2, i have also phh superuser and safetynet pass successfully (attachment 1). Now i want to install xposed, when i install xposed v86.6, safetynet don't pass, it fails with a blue screen. I have tried to install the modules called "no check device" and "rootcloak" but always fail. Is there a way to bypass it with xposed please? Thanks.
[Magisk] cubandanger05:
As far as I know at this time you won't pass safetynet with xposed. You must disable it and reboot.
[Magisk] izeeqo:
Even if I disable Xposed, safetynet doesn't pass, I can't login on Snapchat
[Magisk] Captain_Throwback:
Did you add your app to the hide list?
[Magisk] Captain_Throwback:
Where are the zips? I can take a look. Also, please indicate whether both folders are being added to system, or if they're replacing existing folders.

Have you tried flashing the zip in recovery versus Magisk Manager and see if that makes a difference?
[Magisk] Captain_Throwback:
Xposed trips SafetyNet, unless you hide it with suhide + RootSwitch.
[Magisk] chrisg4:
I found a way to pass safety net

1. Clean install

2. Remove supersu

3. Flash magisk v8

3. Flash pph superuser v259

4. Install phh's superuser from playstore

5. Install magisk manager 2.1

6. Enable magiskhide

7. Safety net is green
[Magisk] negroxxx:
I have installed magisk v8 + PHH SuperSU

safetynet is green.

Xposed install and safetynet is blue.

Suhide install and rootswitch and remains blue.

rootswitch put in enabled but I can not put more on disabled. Any solution ?

I want to install Xposed
[Magisk] Captain_Throwback:
suhide doesn't work with phh's Superuser....so I'm not sure how you have that working at all.
[Magisk] andrew2432:
What's a blue screen mean?
[Magisk] henderjr:
Thanks for this!

After using some of the ideas in this post I have Xposed semi-working and passing SafetyNet on my Sprint Note 5. I already had Magisk working so I didn't use the mod2 version. I also couldn't get 86.2 to flash (not meant to work with PHH's superuser I don't think) but I was able to use Wanam's 86.1 Xposed for Samsung (arm64 version for my phone). Yes that's system xposed and not systemless. RootSwitch to toggle off Xposed and let it soft reboot. Xposed Installer reports yellow and at least a couple of my modules (xtouchwiz for example) didn't seem to work but PGO with Snorlax module does. Safetynet is green! Though since xposed only partially works it's not a perfect solution.
[Magisk] alexpower:
You can't use Pogo or Android pay and login snapchat fails

Gesendet von meinem HTC 10 mit Tapatalk
[Magisk] andrew2432:
Can anybody help with the magisk v8 mods?? I'm looking for the mod and mod2. Couldn't get the regular one working on the LG g2 d800 with lollipop
[Magisk] Captain_Throwback:
That you're using the wrong app to verify SafetyNet ;)

There is no official "mod 2" by [MENTION=4470081]topjohnwu[/MENTION]. The standard v8 version works fine, if installed correctly using the instructions.
[Magisk] pndwal:
Seems we're all 'lucky' Xiaomi users! 😜

Recommend Xiaomi users also never do dumb things like flash foreign persist however (as above), or luck may run out...

Also, it's wise to store backup of unique partitions

from device

, especially

persist

(and others?)... PW
[Magisk] zgfg:
Regarding to Persist, Xiaomi users claimed that even flashing the backed-up Persist partition did not fix L1 if Persist partition was previously messed up

And one more thing. Upon switching to Xiaomi.eu you still have DRM L1 showing in apps like Device Info, but it was not enough for Netflix. It was necessary to update the certificate through Fingerprint Payments
[Magisk] pndwal:
Well there may be other issues involved; some unlocked devices (especially Mi 9T it seems) / ROMs often don't have L1 without other mods like

https://xdaforums.com/t/magisk-widevine-l1-fix-for-miui-custom-roms-mi-9t-k20.3962506/

in addition, but I'm guessing persist should be properly fixed and do the trick if deviceis re-locked and stock fastboot ROM flashed. (I did read one comment about 9T not fixed this way, but seems user was still on custom EU ROM... before XiaomiEU's 5.12 L1 fix last year?)

.. If not, it seems there is the possibility of accessing / using 'persistbak' partition, but I haven't seen proof of concept...

(Other devices, Mi Note 10 Lite, Redmi Note 9S, Redmi Note 8 Pro, and the Poco F1 specifically, were affected by bad updates - apparently security patches? - that broke TEE for L1)

If other, can you give a reference to these claims?... Restoring device-specific persist back up has certainly worked on other devices... Perhaps additional partitions store device-specific codes on Xiaomi?

... Still, advice to 'mess with persist at your peril' seems good to me. - I certainly wouldn't want to try it without backups from device. 😬

Yeah, ta... I Saw references to this trick too.
[Magisk] zgfg:
The post you are referring to is very old, from 2019.

I'm talking about the instructions Xiaomi.eu provided last summer or so - and it did not require to install anything but just to update the certificate

Regarding to Mi 9 (T, T Pro, SE, plain 9), it was a known issue, discussed elsewhere, maybe mostly on particular TG channels for custom ROMs.

All those phones were released with proper L1 cert (at least if not bought with CN firmware).

And unlocking BL did not affect L1.

But some early custom ROMs (at that time for A10) messed up Persist partition (their installation procedure through TWRP) and users were later not able to fix it when they reinstalled stock firmware and even restored their original Persist (if they made Nandroid backup before switching to custom ROMs).

Some asked Xiaomi service for help but they refused, saying that they cannot re-certify the phone

Btw, I have Mi 9T and can guarantee you that originally, when I unlocked BL, it did not affect my DRM L1.

Later I switched to Xiaomi.eu and by one of their weeklies they screwed Netflix, but they fixed by one of the subsequent weeklies - only it was required to install the Fingerprint payment certificate
[Magisk] pndwal:
Old, but I think the only place I found where "Xiaomi users claimed that even flashing the backed-up Persist partition did not fix L1 if Persist partition was previously messed up"...

Interesting, thanks...

As a general rule, as I said though "Restoring device-specific persist back up has certainly worked on other devices... Perhaps additional partitions store device-specific codes on Xiaomi?

... Still, advice to 'mess with persist at your peril' seems good to me. - I certainly wouldn't want to try it without backups from device. 😬"

Yup - My RN8T remains on L1 also... PW
[Magisk] QuietMountains:
Had magisk hidden and all of a sudden I lost root. I had a non hidden magisk installed which won't let me install the same .img I used when originally rooting the phone.